CN117119438A - Method, device, equipment and medium for processing software service - Google Patents
Method, device, equipment and medium for processing software service Download PDFInfo
- Publication number
- CN117119438A CN117119438A CN202310834436.XA CN202310834436A CN117119438A CN 117119438 A CN117119438 A CN 117119438A CN 202310834436 A CN202310834436 A CN 202310834436A CN 117119438 A CN117119438 A CN 117119438A
- Authority
- CN
- China
- Prior art keywords
- cluster instance
- software
- software service
- vehicle
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000004891 communication Methods 0.000 claims abstract description 93
- 238000012795 verification Methods 0.000 claims abstract description 21
- 238000003672 processing method Methods 0.000 claims abstract description 17
- 238000013475 authorization Methods 0.000 claims description 122
- 238000012545 processing Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 14
- 238000010586 diagram Methods 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- KLDZYURQCUYZBL-UHFFFAOYSA-N 2-[3-[(2-hydroxyphenyl)methylideneamino]propyliminomethyl]phenol Chemical compound OC1=CC=CC=C1C=NCCCN=CC1=CC=CC=C1O KLDZYURQCUYZBL-UHFFFAOYSA-N 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 201000001098 delayed sleep phase syndrome Diseases 0.000 description 1
- 208000033921 delayed sleep phase type circadian rhythm sleep disease Diseases 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a processing method, a device, equipment and a medium of software service, wherein the method comprises the following steps: receiving a software service request sent by a vehicle, wherein the software service request comprises a vehicle identifier and target software information of a requested service; if the vehicle identification passes the verification, determining a target cluster instance corresponding to the target software information, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform; and forwarding the software service request to the target cluster instance so that the target cluster instance provides a target software service for the vehicle. The problem of software authorization failure or inconsistency caused by replacement or upgrading of vehicle hardware equipment is avoided.
Description
Technical Field
The embodiment of the application relates to the technical field of processing of software services, in particular to a method, a device, equipment and a medium for processing the software services.
Background
The vehicle cloud communication refers to data interaction between a vehicle and a cloud platform, and is an important technology for realizing intelligent network-connected vehicles and intelligent traffic. Vehicle cloud communication involves a variety of software services, such as navigation, entertainment, remote control, vehicle management, etc., that require authorization and management of the user to ensure legitimate use and revenue of the software.
At present, the traditional software authorization method is to bind software and hardware equipment, but the method is not suitable for a vehicle cloud communication scene, and the vehicle can replace or upgrade the hardware equipment, so that the software authorization is invalid or inconsistent.
Disclosure of Invention
The application provides a processing method, a device, equipment and a medium of software service, which avoid the problem of invalid or inconsistent software authorization caused by the replacement or upgrading of vehicle hardware equipment.
In a first aspect, a method for processing a software service is provided, where the method is applied to a vehicle cloud communication platform, and includes:
receiving a software service request sent by a vehicle, wherein the software service request comprises a vehicle identifier and target software information of a requested service;
if the vehicle identification passes the verification, determining a target cluster instance corresponding to the target software information, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform;
and forwarding the software service request to the target cluster instance so that the target cluster instance provides a target software service for the vehicle.
In an alternative embodiment provided by the present application, the method further includes:
receiving a software authorization request sent by a cluster instance, wherein the software authorization request carries an authorization file and a unique identifier of the cluster instance, and the authorization file comprises software service information;
checking whether the unique identifier of the cluster instance passes or not;
if the verification of the unique identification of the cluster instance is passed, verifying whether the software service information is passed or not;
and if the software service information is checked to pass, authorizing the cluster instance to store the software corresponding to the software service information, and storing the software service information corresponding to the cluster instance in an authorization information table.
In an alternative embodiment provided by the present application, before receiving the software authorization request sent by the cluster instance, the method further includes:
receiving a unique cluster instance identifier sent by the cluster instance, wherein the unique cluster instance identifier is generated according to hardware information and software information of the cluster instance;
generating software service information corresponding to the unique cluster instance identifier, writing the unique cluster instance identifier and the corresponding software service information into an authorization file, and storing the authorization file corresponding to the cluster instance in a cluster instance authorization table;
and sending the authorization file to the cluster instance, so that the cluster instance sends a software authorization request to the vehicle cloud communication platform based on the authorization file.
In an optional embodiment of the present application, the generating software service information corresponding to the unique identifier of the cluster instance includes:
acquiring unauthorized software service information, wherein the software service information at least comprises a software service name, a software version, a software validity period and a software authorization quantity;
and generating software service information corresponding to the unique cluster instance identifier based on the unauthorized software service information.
In an optional embodiment provided by the present application, the checking whether the cluster instance unique identifier passes includes:
extracting a unique cluster instance identifier from the authorization file;
determining whether the unique identifier of the cluster instance extracted from the authorization file is consistent with the unique identifier of the cluster instance sent by the cluster instance;
and if the cluster instance unique identifiers are consistent, confirming and checking that the cluster instance unique identifiers pass.
In an alternative embodiment provided by the present application, the method further includes:
receiving an updated unique cluster instance identifier sent by the cluster instance, wherein the updated unique cluster instance identifier is generated according to hardware information and software information updated by the cluster instance;
acquiring an authorization file corresponding to the cluster instance based on the cluster instance authorization table, and replacing the original unique cluster instance identifier in the authorization file with the updated unique cluster instance identifier;
and sending the updated authorization file to the cluster instance, so that the cluster instance updates the locally stored authorization file.
In an alternative embodiment provided by the present application, the method further includes:
updating original software service information in the corresponding authorization file according to the updated software service information;
and sending the updated authorization file to the cluster instance, so that the cluster instance updates the locally stored authorization file.
In a second aspect, there is provided a processing apparatus for a software service, comprising:
the receiving module is used for receiving a software service request sent by a vehicle, wherein the software service request comprises a vehicle identifier and target software information of a requested service;
the determining module is used for determining a target cluster instance corresponding to the target software information if the vehicle identification passes the verification, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform;
and the forwarding module is used for forwarding the software service request to the target cluster instance so that the target cluster instance provides a target software service for the vehicle.
In a third aspect, there is provided an electronic device comprising: a processor and a memory for storing a computer program for invoking and running the computer program stored in the memory for performing a method of processing a software service as in the first aspect or in various implementations thereof.
In a fourth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to execute the processing method of the software service as in the first aspect or its respective implementation manner.
In a fifth aspect, a computer program product is provided, comprising computer program instructions for causing a computer to perform the method of processing a software service as in the first aspect or in various implementations thereof.
In a sixth aspect, a computer program is provided, the computer program causing a computer to execute the processing method of the software service as in the first aspect or in various implementations thereof.
According to the technical scheme provided by the application, the vehicle cloud communication platform receives a software service request sent by a vehicle, wherein the software service request comprises a vehicle identifier and target software information of a requested service; then checking the vehicle identification, if the vehicle identification passes the checking, determining a target cluster instance corresponding to the target software information, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform; and finally, the vehicle cloud communication platform forwards the software service request to the target cluster instance, so that the target cluster instance provides the target software service for the vehicle. Compared with the prior art that the software service is obtained through the mode of binding the software and the hardware, the method and the device provide the software service for the vehicle through the cluster instance authorized by the vehicle cloud communication platform, so that the problem of invalid or inconsistent software authorization caused by replacement or upgrading of the vehicle hardware equipment can be avoided.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a method for processing a software service according to an embodiment of the present application;
FIG. 2 is a flowchart of a method for authorizing a software service according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a processing device for a software service according to an embodiment of the present application;
fig. 4 is a schematic block diagram of an electronic device provided by an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a flowchart of a method for processing a software service according to an embodiment of the present application, where the method may include the following steps:
s110: the vehicle sends a software service request to the vehicle cloud communication platform, wherein the software service request comprises a vehicle identifier and target software information of the requested service.
The vehicle identifier is used for uniquely identifying the corresponding vehicle, and the vehicle identifier can be VIN (Vehicle Identification Number, vehicle identification code number); the target software information is information of a software service requested by the vehicle, and the target software information may be a plurality of software services, for example, the target software information may be software information such as navigation, entertainment, remote control, vehicle management, etc., which is not particularly limited in this embodiment.
S120: and the vehicle cloud communication platform verifies the vehicle identification.
Specifically, in this embodiment, a plurality of vehicle identifiers capable of authorizing software services are stored in the vehicle cloud communication platform, and after receiving a software service request sent by a vehicle, the vehicle cloud communication platform determines whether to pass the verification of the vehicle identifiers by querying whether the vehicle cloud communication platform locally stores the vehicle identifiers in the software service request. If the vehicle identifier in the software service request is stored in the vehicle cloud communication platform, the vehicle cloud communication platform verifies that the vehicle identifier passes; if the vehicle identification in the software service request is not stored in the vehicle cloud communication platform, the vehicle cloud communication platform verifies that the vehicle identification does not pass.
It should be noted that, after the vehicle identifier locally written in the vehicle cloud communication platform is preconfigured, for example, after a batch of vehicles are put into the market, if the batch of vehicles are authorized to use the a software service, the vehicle identifier of the batch of vehicles can be written in the vehicle cloud communication platform when the batch of vehicles leaves the factory, so that the vehicle cloud communication platform can verify that the vehicle identifier of the vehicle passes when the vehicle requests the a software service, and further ensure that the vehicle can use the a software service in a subsequent step.
In this embodiment, the vehicle identifier may be classified and stored in the vehicle cloud communication platform according to the type of the software information, so that after the vehicle cloud communication platform receives the software service request sent by the vehicle, it determines whether the vehicle identifier passes the verification from the vehicle identifier corresponding to the target software information by the vehicle cloud communication platform.
For example, vehicle identifications corresponding to software service A, software service B and software service C are stored in the vehicle cloud communication platform, after a software service request sent by a vehicle is acquired, target software information in the software service request is firstly acquired, if the target software service information is the software service A, whether the vehicle identification corresponding to the software service A in the vehicle cloud communication platform contains the vehicle identification in the software service request is inquired, and if the vehicle identification contains the vehicle identification, the verification of the vehicle identification is determined to be passed; if the vehicle identification verification is not included, determining that the vehicle identification verification is not passed.
S130: and if the vehicle identification passes the verification, determining a target cluster instance corresponding to the target software information, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform.
In this embodiment, the vehicle cloud communication platform corresponds to a plurality of cluster instances, and stored software is different between each cluster instance. Each cluster instance can request different software services from the vehicle cloud communication platform according to the needs of the cluster instance, and the software services are locally operated, namely, each cluster instance stores software authorized by the vehicle cloud communication platform.
The cluster instances refer to a group of mutually independent servers, and a large computer service system is formed by utilizing a high-speed communication network, and each cluster instance is an independent server running respective software services, such as vehicle identification, vehicle positioning, vehicle control and the like.
Specifically, in this embodiment, the target cluster instance corresponding to the target software information may be determined through the authorization information table, that is, the cluster instance corresponding to the target software information in the authorization information table is determined as the target cluster instance. The authorization information table stores software service information corresponding to the cluster instance. The authorization information table stores software service information corresponding to the cluster instance.
S140: and the vehicle cloud communication platform forwards the software service request to the target cluster instance.
S150: the target cluster instance provides a target software service for the vehicle.
In the embodiment, the binding of the software and the cluster instance can be realized through the vehicle cloud communication platform, so that illegal copying and use of the software are prevented, and the safety of the software is improved. Compared with the traditional software authorization method, the embodiment does not need to bind the software and the hardware equipment, and the problem of software authorization failure or inconsistency caused by replacement or upgrading of the hardware equipment is avoided.
The method for processing the software service provided by the embodiment of the application comprises the steps that firstly, a vehicle cloud communication platform receives a software service request sent by a vehicle, wherein the software service request comprises a vehicle identifier and target software information of a service request; then checking the vehicle identification, if the vehicle identification passes the checking, determining a target cluster instance corresponding to the target software information, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform; and finally, the vehicle cloud communication platform forwards the software service request to the target cluster instance, so that the target cluster instance provides the target software service for the vehicle. Compared with the prior art that the software service is obtained through the mode of binding the software and the hardware, the method and the device provide the software service for the vehicle through the cluster instance authorized by the vehicle cloud communication platform, so that the problem of invalid or inconsistent software authorization caused by replacement or upgrading of the vehicle hardware equipment can be avoided.
Fig. 2 is a flowchart of an authorization method for a software service according to an embodiment of the present application, including the following steps:
s210: and the cluster instance sends the unique identifier of the cluster instance to the vehicle cloud communication platform.
Wherein the cluster instance unique identification is generated from hardware information and software information of the cluster instance. The cluster instance sends the generated unique identifier of the cluster instance to the vehicle cloud communication platform as an identity credential, so that the vehicle cloud communication platform generates an authorization file according to the unique identifier of the cluster instance.
S220: the vehicle cloud communication platform generates software service information corresponding to the unique cluster instance identifier, writes the unique cluster instance identifier and the corresponding software service information into an authorization file, and stores the authorization file corresponding to the cluster instance in a cluster instance authorization table.
The software service information at least comprises a software service name, a software version, a software validity period and a software authorization quantity. In an optional embodiment of the present application, the generating software service information corresponding to the unique identifier of the cluster instance includes: acquiring unauthorized software service information; and generating software service information corresponding to the unique cluster instance identifier based on the unauthorized software service information.
For example, the vehicle cloud communication platform includes service software 1, service software 2 and service software 3, wherein the service software 1 and the service software 2 are authorized to the cluster instance 1 and the cluster instance 2 respectively, so that the cluster instance 1 and the cluster instance 2 can provide corresponding software services for the vehicle, after the vehicle cloud communication platform receives the unique identifier of the cluster instance sent by the cluster instance 3, unauthorized software service information (software service 3) is acquired, and then software service information corresponding to the cluster instance 3 is generated based on the software service information of the software service 3.
S230: and the vehicle cloud communication platform sends the authorization file to the cluster instance.
In an optional embodiment provided by the application, in order to ensure the transmission safety of the authorization file, the vehicle cloud communication platform needs to encrypt the authorization file, for example, an asymmetric encryption algorithm is used for encrypting the authorization file into a ciphertext and generating a digital signature. And then the encrypted authorization file and the digital signature are sent to the cluster instance, the cluster instance uses the public key to decrypt and verify the authorization file, and if the verification is passed, the authorization file is stored in the local of the cluster instance, so that the cluster instance sends a software authorization request to the vehicle cloud communication platform based on the authorization file.
Among other things, digital signatures are a technique for ensuring the security and integrity of an authorization document, which can be used to verify whether the source and content of the authorization document has been tampered with. The digital signature is generated by the vehicle cloud communication platform by using an asymmetric encryption algorithm, and comprises abstract information of the authorization file and a private key of the vehicle cloud communication platform. The cluster instance may verify the digital signature using the public key of the vehicle cloud communication platform, and if the verification passes, the authorization file is sent by the vehicle cloud communication platform and is not modified.
In the embodiment, an asymmetric encryption algorithm is used for encrypting and decrypting the authorization file, verifying the identity certificate of the cluster instance, and preventing the authorization file from being tampered or revealed and the vehicle cloud communication platform from being accessed or attacked maliciously. Therefore, the safety of the vehicle cloud communication platform and the user data can be ensured, and the loss or risk caused by the safety problem of the vehicle cloud communication is avoided.
S240: the cluster instance sends a software authorization request to the vehicle cloud communication platform based on the authorization file.
The software authorization request carries an authorization file and a unique cluster instance identifier, and the authorization file comprises software service information.
S250: the vehicle cloud communication platform checks whether the unique identification of the cluster instance passes.
In an optional embodiment provided by the present application, the checking whether the cluster instance unique identifier passes includes: extracting a unique cluster instance identifier from the authorization file; determining whether the unique identifier of the cluster instance extracted from the authorization file is consistent with the unique identifier of the cluster instance sent by the cluster instance; and if the cluster instance unique identifiers are consistent, confirming and checking that the cluster instance unique identifiers pass.
In this embodiment, after receiving the unique identifier of the cluster instance, the vehicle cloud communication platform compares the unique identifier with the unique identifier of the cluster instance in the authorization file to verify the validity and authority of the cluster instance. Specific: the vehicle cloud communication platform extracts the unique identifier of the cluster instance from the authorization file, the unique identifier of the cluster instance is generated by the vehicle cloud communication platform according to the hardware information and the software information of the cluster instance, the vehicle cloud communication platform receives the identity certificate sent by the cluster instance, the identity certificate is also the unique identifier of the cluster instance, but the cluster instance is generated according to the hardware information and the software information of the vehicle cloud communication platform, the vehicle cloud communication platform compares the two unique identifiers, if the two unique identifiers are completely consistent, the fact that the cluster instance is legal is indicated, and otherwise, the fact that the cluster instance is illegal is indicated.
S260: and if the vehicle cloud communication platform verifies that the unique identification of the cluster instance passes, verifying whether the software service information passes.
In this embodiment, it is checked whether the software service information passes through the cluster instance authorization table. Specifically, acquiring software service information in an authorization file from a software authorization request, acquiring the authorization file corresponding to a cluster instance from the authorization file including the software service information, extracting the software service information from the acquired authorization file, comparing whether the two pieces of software service information are consistent, and if the two pieces of software service information are consistent, checking that the software service information passes; if the two pieces of software service information are inconsistent, the verification of the software service information fails.
S270: if the vehicle cloud communication platform verifies that the software service information passes, the authorized cluster instance stores software corresponding to the software service information, and the authorized information table stores the software service information corresponding to the cluster instance.
In this embodiment, the software service information corresponding to the cluster instance is stored in the authorization information table, so as to ensure that after receiving the software service request sent by the vehicle, the target cluster instance corresponding to the target software information can be determined based on the authorization information table.
According to the method for authorizing the software service, the vehicle cloud communication platform generates the authorization file based on the unique identifier of the cluster instance and then sends the authorization file to the cluster instance, so that the cluster instance initiates a software authorization request to the vehicle cloud communication platform based on the authorization file, the vehicle cloud communication platform checks whether the unique identifier of the cluster instance and the software service information pass or not after receiving the software authorization request, and if the unique identifier of the cluster instance and the software service information pass, the cluster instance is authorized to store software corresponding to the software service information, and the cluster instance can provide corresponding software service for a vehicle. Because the binding of the software and the cluster instance can be realized through the vehicle cloud communication platform, compared with the traditional software authorization method, the embodiment does not need to bind the software and the hardware equipment, and the problem of software authorization failure or inconsistency caused by replacement or upgrading of the hardware equipment is avoided.
In an optional embodiment provided by the application, when software information and/or hardware information corresponding to a cluster instance change, for example, the cluster instance may change due to failure, upgrading, capacity expansion or capacity shrinkage and the like, the cluster instance needs to regenerate a unique cluster instance identifier according to new software information and/or hardware information, then the regenerated unique cluster instance identifier is sent to a vehicle cloud communication platform, and the vehicle cloud communication platform acquires an authorization file corresponding to the cluster instance based on a cluster instance authorization table and replaces the original unique cluster instance identifier in the authorization file with an updated unique cluster instance identifier; and sending the updated authorization file to the cluster instance, so that the cluster instance updates the locally stored authorization file.
In this embodiment, the unique identifier of the cluster instance in the authorization file is an identity for identifying the cluster instance, and is composed of hardware information and software information of the cluster instance. When the scale of a cluster instance changes, its hardware information or software information also changes, resulting in the failure of the original unique cluster instance identifier. In order to ensure that the cluster instance can continue to use the software service provided by the vehicle cloud communication platform, a new authorization file needs to be generated, which contains a new unique identifier of the cluster instance and corresponding software service information. The new authorization file replaces the old authorization file so that the cluster instance can adjust the usage of the software service according to the software service information in the new authorization file.
In another optional embodiment provided by the application, when the vehicle cloud communication platform needs to update the authorization file, for example, the vehicle cloud communication platform issues a new software service version, or the validity period of the software service is prolonged, or the authorization quantity of the software service is adjusted, corresponding information in the authorization file needs to be updated. And the vehicle cloud communication platform sends an update request to the cluster instance through the message queue, and attaches a new authorization file and a digital signature. After the cluster instance receives the update request, the public key is used for decrypting and verifying the new authorization file, if the verification is passed, the old authorization file stored locally is replaced, and the service condition of the software service is adjusted according to the software service information in the new authorization file.
In this embodiment, encryption after updating the authorization file is to ensure confidentiality and authorization of the authorization file, and prevent the authorization file from being tampered or revealed. The encrypted authorization file and the digital signature can be verified by an asymmetric encryption algorithm, and only the cluster instance with the public key can decrypt and use the authorization file.
Compared with the existing software authorization method, the embodiment does not need to store the authorization file on a local or remote server, but realizes timely acquisition and update of the authorization file and response to the state change of the cluster instance through a message queue and an event monitoring mechanism, thereby ensuring the continuous effectiveness of the software service. Therefore, the experience and satisfaction degree of the cloud communication users can be improved, and software service interruption or abnormality caused by expiration and invalidation of the authorization files can be avoided.
Fig. 3 is a schematic diagram of a processing device for a software service according to an embodiment of the present application. As shown in fig. 3, the apparatus includes:
a receiving module 301, configured to receive a software service request sent by a vehicle, where the software service request includes a vehicle identifier and target software information of a requested service;
the determining module 302 is configured to determine a target cluster instance corresponding to the target software information if the vehicle identifier passes the verification, where the target cluster instance stores target software authorized by the vehicle cloud communication platform;
and the forwarding module 303 is configured to forward the software service request to the target cluster instance, so that the target cluster instance provides a target software service for the vehicle.
In an optional embodiment provided by the present application, the receiving module 301 is further configured to receive a software authorization request sent by a cluster instance, where the software authorization request carries an authorization file and a unique identifier of the cluster instance, and the authorization file includes software service information;
a checking module 304, configured to check whether the unique identifier of the cluster instance passes; if the verification of the unique identification of the cluster instance is passed, verifying whether the software service information is passed or not;
and the authorization module 305 is configured to authorize the cluster instance to store software corresponding to the software service information if the software service information passes through the verification, and store the software service information corresponding to the cluster instance in an authorization information table.
In an optional embodiment provided by the present application, the receiving module 301 is further configured to receive a unique cluster instance identifier sent by the cluster instance, where the unique cluster instance identifier is generated according to hardware information and software information of the cluster instance;
the generating module 306 is configured to generate software service information corresponding to the unique identifier of the cluster instance, write the unique identifier of the cluster instance and the corresponding software service information into an authorization file, and store the authorization file corresponding to the cluster instance in a cluster instance authorization table;
and the sending module 307 is configured to send the authorization file to the cluster instance, so that the cluster instance sends a software authorization request to the cloud communication platform based on the authorization file.
In an alternative embodiment provided by the present application, the generating module 306 is specifically configured to:
acquiring unauthorized software service information, wherein the software service information at least comprises a software service name, a software version, a software validity period and a software authorization quantity;
and generating software service information corresponding to the unique cluster instance identifier based on the unauthorized software service information.
In an alternative embodiment provided by the present application, the verification module 304 is specifically configured to:
extracting a unique cluster instance identifier from the authorization file;
determining whether the unique identifier of the cluster instance extracted from the authorization file is consistent with the unique identifier of the cluster instance sent by the cluster instance;
and if the cluster instance unique identifiers are consistent, confirming and checking that the cluster instance unique identifiers pass.
In an optional embodiment provided by the present application, the receiving module 301 is further configured to receive an updated unique identifier of a cluster instance sent by the cluster instance, where the updated unique identifier of the cluster instance is generated according to updated hardware information and software information of the cluster instance; acquiring an authorization file corresponding to the cluster instance based on the cluster instance authorization table, and replacing the original unique cluster instance identifier in the authorization file with the updated unique cluster instance identifier;
the sending module 307 is further configured to send the updated authorization file to the cluster instance, so that the cluster instance updates the authorization file stored locally.
In an optional embodiment provided by the present application, the sending module 307 is further configured to update original software service information in the corresponding authorization file according to the updated software service information; and sending the updated authorization file to the cluster instance, so that the cluster instance updates the locally stored authorization file.
It should be understood that the apparatus embodiment and the processing method embodiment of the software service may correspond to each other, and similar descriptions may refer to the processing method embodiment of the software service. To avoid repetition, no further description is provided here. Specifically, the apparatus shown in fig. 3 may execute the embodiment of the processing method of the software service, and the foregoing and other operations and/or functions of each module in the apparatus are respectively for implementing corresponding flows in the processing method of the software service, which are not described herein for brevity.
The apparatus of the embodiments of the present application is described above in terms of functional modules with reference to the accompanying drawings. It should be understood that the functional module may be implemented in hardware, or may be implemented by instructions in software, or may be implemented by a combination of hardware and software modules. Specifically, each step of the processing method embodiment of the software service in the embodiment of the present application may be completed by an integrated logic circuit of hardware in a processor and/or an instruction in a software form, and the steps of the processing method of the software service disclosed in connection with the embodiment of the present application may be directly embodied and executed by a hardware decoding processor or may be completed by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in a well-established storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory, and the processor reads the information in the memory, and combines with the hardware to complete the steps in the processing method embodiment of the software service.
Fig. 4 is a schematic block diagram of an electronic device 400 provided by an embodiment of the application. As shown in fig. 4, the electronic device 400 may include: a processor 401, a memory 402. The electronic device 400 may also include one or more of a multimedia component 403, an input/output (I/O) interface 404, and a communication component 405.
Wherein the processor 401 is configured to control the overall operation of the electronic device 400 to perform all or part of the steps in the above-described processing method of the software service. The memory 402 is used to store various types of data to support operation at the electronic device 400, which may include, for example, instructions for any application or method operating on the electronic device 400, as well as application-related data, such as contact data, transceived messages, pictures, audio, video, and the like. The Memory 402 may be implemented by any type or combination of volatile or non-volatile Memory devices, such as static random access Memory (Static Random Access Memory, SRAM for short), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM for short), erasable programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM for short), programmable Read-Only Memory (Programmable Read-Only Memory, PROM for short), read-Only Memory (ROM for short), magnetic Memory, flash Memory, magnetic disk, or optical disk. The multimedia component 403 may include a screen and an audio component. Wherein the screen may be, for example, a touch screen, the audio component being for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in memory 402 or transmitted through communication component 405. The audio assembly further comprises at least one speaker for outputting audio signals. The I/O interface 404 provides an interface between the processor 401 and other interface modules, which may be a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 405 is used for wired or wireless communication between the electronic device 400 and other devices. Wireless communication, such as Wi-Fi, bluetooth, near field communication (Near Field Communication, NFC for short), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, etc., or one or a combination of more of them, is not limited herein. The corresponding communication component 405 may thus comprise: wi-Fi module, bluetooth module, NFC module, etc.
In an exemplary embodiment, the electronic device 400 may be implemented by one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), digital signal processors (Digital Signal Processor, abbreviated as DSP), digital signal processing devices (Digital Signal Processing Device, abbreviated as DSPD), programmable logic devices (Programmable Logic Device, abbreviated as PLD), field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), controllers, microcontrollers, microprocessors, or other electronic components for executing the processing methods of software services described above.
In another exemplary embodiment, a computer readable storage medium is also provided, comprising program instructions which, when executed by a processor, implement the steps of the method of processing a software service as described above. For example, the computer readable storage medium may be the memory 402 including program instructions described above, which are executable by the processor 401 of the electronic device 400 to perform the processing method of the software service described above.
In another exemplary embodiment, a computer readable storage medium is also provided, comprising program instructions which, when executed by a processor, implement the steps of the method of processing a software service as described above.
In another exemplary embodiment, a computer program product is also provided, comprising a computer program executable by a programmable apparatus, the computer program having code portions for performing the above-mentioned processing method of a software service when executed by the programmable apparatus.
In another exemplary embodiment, there is also provided a computer program that causes a computer to execute the processing method of the software service as described above.
Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.
The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, functional modules in various embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method for processing a software service, wherein the method is applied to a vehicle cloud communication platform, and the method comprises the following steps:
receiving a software service request sent by a vehicle, wherein the software service request comprises a vehicle identifier and target software information of a requested service;
if the vehicle identification passes the verification, determining a target cluster instance corresponding to the target software information, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform;
and forwarding the software service request to the target cluster instance so that the target cluster instance provides a target software service for the vehicle.
2. The method according to claim 1, wherein the method further comprises:
receiving a software authorization request sent by a cluster instance, wherein the software authorization request carries an authorization file and a unique identifier of the cluster instance, and the authorization file comprises software service information;
checking whether the unique identifier of the cluster instance passes or not;
if the verification of the unique identification of the cluster instance is passed, verifying whether the software service information is passed or not;
and if the software service information is checked to pass, authorizing the cluster instance to store the software corresponding to the software service information, and storing the software service information corresponding to the cluster instance in an authorization information table.
3. The method of claim 2, wherein prior to receiving the software authorization request sent by the cluster instance, the method further comprises:
receiving a unique cluster instance identifier sent by the cluster instance, wherein the unique cluster instance identifier is generated according to hardware information and software information of the cluster instance;
generating software service information corresponding to the unique cluster instance identifier, writing the unique cluster instance identifier and the corresponding software service information into an authorization file, and storing the authorization file corresponding to the cluster instance in a cluster instance authorization table;
and sending the authorization file to the cluster instance, so that the cluster instance sends a software authorization request to the vehicle cloud communication platform based on the authorization file.
4. A method according to claim 3, wherein said generating software service information corresponding to said cluster instance unique identification comprises:
acquiring unauthorized software service information, wherein the software service information at least comprises a software service name, a software version, a software validity period and a software authorization quantity;
and generating software service information corresponding to the unique cluster instance identifier based on the unauthorized software service information.
5. The method of claim 2, wherein the checking whether the cluster instance unique identification passes comprises:
extracting a unique cluster instance identifier from the authorization file;
determining whether the unique identifier of the cluster instance extracted from the authorization file is consistent with the unique identifier of the cluster instance sent by the cluster instance;
and if the cluster instance unique identifiers are consistent, confirming and checking that the cluster instance unique identifiers pass.
6. A method according to claim 3, characterized in that the method further comprises:
receiving an updated unique cluster instance identifier sent by the cluster instance, wherein the updated unique cluster instance identifier is generated according to hardware information and software information updated by the cluster instance;
acquiring an authorization file corresponding to the cluster instance based on the cluster instance authorization table, and replacing the original unique cluster instance identifier in the authorization file with the updated unique cluster instance identifier;
and sending the updated authorization file to the cluster instance, so that the cluster instance updates the locally stored authorization file.
7. A method according to claim 3, characterized in that the method further comprises:
updating original software service information in the corresponding authorization file according to the updated software service information;
and sending the updated authorization file to the cluster instance, so that the cluster instance updates the locally stored authorization file.
8. A processing apparatus for a software service, comprising:
the receiving module is used for receiving a software service request sent by a vehicle, wherein the software service request comprises a vehicle identifier and target software information of a requested service;
the determining module is used for determining a target cluster instance corresponding to the target software information if the vehicle identification passes the verification, wherein the target cluster instance stores target software authorized by the vehicle cloud communication platform;
and the forwarding module is used for forwarding the software service request to the target cluster instance so that the target cluster instance provides a target software service for the vehicle.
9. An electronic device, comprising:
a processor and a memory for storing a computer program, the processor being adapted to call and run the computer program stored in the memory to perform the method of processing a software service according to any of claims 1-7.
10. A computer-readable storage medium storing a computer program for causing a computer to execute the processing method of the software service according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310834436.XA CN117119438A (en) | 2023-07-07 | 2023-07-07 | Method, device, equipment and medium for processing software service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310834436.XA CN117119438A (en) | 2023-07-07 | 2023-07-07 | Method, device, equipment and medium for processing software service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117119438A true CN117119438A (en) | 2023-11-24 |
Family
ID=88793681
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310834436.XA Pending CN117119438A (en) | 2023-07-07 | 2023-07-07 | Method, device, equipment and medium for processing software service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117119438A (en) |
-
2023
- 2023-07-07 CN CN202310834436.XA patent/CN117119438A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7060362B2 (en) | Event certificate for electronic devices | |
| CN111275857B (en) | Control method of intelligent lock and intelligent lock | |
| US20200201988A1 (en) | IoT DEVICE MANAGED BASED ON BLOCK CHAIN, SYSTEM AND METHOD THEREOF | |
| CN112417379B (en) | Cluster license management method and device, authorization server and storage medium | |
| CN111082940B (en) | Internet of things equipment control method and device, computing equipment and storage medium | |
| JP6663032B2 (en) | In-vehicle gateway, key management device | |
| CN106878009B (en) | Key updating method and system | |
| CN113767386B (en) | Network node operating in a distributed network | |
| CN108696356B (en) | Block chain-based digital certificate deleting method, device and system | |
| EP4216077A1 (en) | Blockchain network-based method and apparatus for data processing, and computer device | |
| JP2009087035A (en) | Encryption client device, encryption package distribution system, encryption container distribution system, encryption management server device, solftware module management device and software module management program | |
| CN101340278A (en) | License management system and method | |
| CN110611657A (en) | File stream processing method, device and system based on block chain | |
| US11626998B2 (en) | Validated payload execution | |
| CN110730081B (en) | Block chain network-based certificate revocation method, related equipment and medium | |
| CN111786812A (en) | Node management method, node management device, computer equipment and storage medium | |
| CN113438205B (en) | Block chain data access control method, node and system | |
| CN113261253A (en) | Method and system for controlling release of resources | |
| CN112579125A (en) | Firmware upgrading method and device, electronic equipment and storage medium | |
| CN112131041A (en) | Method, apparatus and computer program product for managing data placement | |
| JP2023525576A (en) | Scope of control of authentication keys for software updates | |
| CN108429732B (en) | Method and system for acquiring resources | |
| CN117119438A (en) | Method, device, equipment and medium for processing software service | |
| CN116248746A (en) | MQTT-based data processing method, device and computer-readable storage medium | |
| CN111698299B (en) | Session object replication method, device, distributed micro-service architecture and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |