Internet of Vehicles APP test method and system, electronic equipment and medium

Abstract

The invention provides an Internet of Vehicles APP test method and system, an electronic device and a medium, and belongs to the technical field of Internet of Vehicles APP release test.The method comprises the steps that a gray level list is acquired, and the gray level list comprises preset user information for carrying out gray level release test on a target Internet of Vehicles APP and vehicle information corresponding to a user; sending the gray level list to a service gateway; the service gateway obtains user request information of logging in the target Internet of Vehicles APP in the gray level list; and according to the user request information of logging in the target Internet of Vehicles APP in the gray list, providing a gray business background service corresponding to the target Internet of Vehicles APP for the user logging in the target Internet of Vehicles APP in the gray list. The method is used for discovering problems in a small-scale user group by gradually deducing new versions during an Internet of Vehicles app release test, can repair the problems in time, avoids affecting wider users, can monitor feedback and behaviors of the users on the new versions in real time, and discovers and adjusts the problems in time.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking app release and testing technology, and in particular to a testing method, system, electronic device, and medium for vehicle networking apps. Background Technology

[0002] like Figure 1 As shown, the existing vehicle networking app release and testing process generally includes the following steps:

[0003] 1. Once the functionality has been verified in the test environment, it will be fully released to the production environment.

[0004] 2. Testers verify the newly added features in an online environment;

[0005] 3. After successful verification, publish the test report. This publication was successful.

[0006] 4. If verification fails, the content launched this time needs to be rolled back, the problem fixed, and then a full release for verification is required.

[0007] The existing technology for releasing and testing connected car apps has the following drawbacks:

[0008] a) This usually involves a full release, meaning all users receive the new version at the same time. This can lead to a wide-ranging impact if a problem occurs with the new version, potentially affecting the experience of all users.

[0009] b) It may focus more on functional verification and performance testing, rather than gradual rollout and user feedback collection;

[0010] c) Due to the full release, risk management is more difficult. If problems occur in the new version, more complex repair and rollback operations may be required.

[0011] d) The testing cycle may be long because all testing needs to be completed before the full release. Summary of the Invention

[0012] This invention aims to address at least one of the aforementioned problems in the prior art by proposing a testing method for connected vehicle apps based on a gray-scale testing framework. This method detects potential issues and reduces risks by gradually expanding the user base of a new version. This approach allows companies to test and optimize new versions without impacting a large number of users. The main objective is to ensure the stability and reliability of new features before their full rollout, using real-world testing to promptly identify and fix potential problems. By limiting the number of initial test users, the potential risks of the new version can be reduced, and a rapid rollback can be implemented once a problem is discovered, minimizing the impact on all users. Furthermore, the testing cycle can be shortened because feedback can be collected and adjustments made quickly.

[0013] In a first aspect, embodiments of the present invention provide a testing method for a vehicle-to-everything (V2X) app, comprising:

[0014] Obtain a gray-scale list, which includes preset user information for gray-scale release testing of the target vehicle networking APP and the vehicle information corresponding to the users;

[0015] Send the grayscale list to the business gateway;

[0016] Obtain user request information for logging into the target vehicle networking APP from the gray-scale list from the business gateway;

[0017] Based on the user request information from the gray-scale list to log in to the target vehicle networking APP, provide the gray-scale business backend service corresponding to the target vehicle networking APP to the users from the gray-scale list who log in to the target vehicle networking APP.

[0018] In a preferred embodiment, the grayscale business backend service retrieves underlying data shared with the normal business backend service for business processing.

[0019] In a preferred embodiment, the step of providing gray-scale business backend services corresponding to the target vehicle-to-everything (V2X) app to users in the gray-scale list who have logged into the target V2X app based on their login request information includes:

[0020] After the gray-scale business backend service completes the business processing, it will synchronize the business processing information to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list through the MQTT server. The MQTT server is the same MQTT server shared with the normal business backend service.

[0021] In a preferred embodiment, it further includes:

[0022] Send the grayscale list to the TBOX gateway;

[0023] Obtain the vehicle HTTP request information corresponding to the users who logged into the target vehicle networking APP from the gray list from the TBOX gateway;

[0024] Based on the HTTP request information of the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray list, provide the gray-scale business backend services of the target vehicle networking APP to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray list.

[0025] In a preferred embodiment, it further includes:

[0026] Send the graylist to the MQTT server;

[0027] Retrieve MQTT messages from the MQTT server for the vehicles corresponding to the users who have logged into the target connected vehicle app from the gray list.

[0028] Based on the MQTT messages of the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list, provide the gray-scale business backend services of the target vehicle networking APP to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list.

[0029] In a preferred embodiment, it further includes:

[0030] Obtain user request information for logging into the target vehicle networking APP from the non-grayscale list from the business gateway;

[0031] Based on the user request information in the non-grayscale list, provide the normal business backend services corresponding to the target vehicle networking APP to the users in the non-grayscale list.

[0032] In a preferred embodiment, the step of providing normal business backend services corresponding to the target vehicle networking APP to users in the non-grayscale list based on user request information in the non-grayscale list includes:

[0033] After the normal business backend service completes the business processing, it will synchronize the business processing information to the vehicle corresponding to the user in the non-grayscale list via the MQTT server.

[0034] In a preferred embodiment, it further includes:

[0035] Obtain vehicle HTTP request information corresponding to users who log in to the target vehicle networking APP from the non-grayscale list from the TBOX gateway;

[0036] Based on the HTTP request information of the vehicles corresponding to the users in the non-grayscale list, provide the normal business backend services of the target vehicle networking APP to the vehicles corresponding to the users in the non-grayscale list.

[0037] In a preferred embodiment, it further includes:

[0038] Retrieve MQTT messages from the MQTT server for the vehicles corresponding to users who have logged into the target connected vehicle app from the non-grayscale list.

[0039] Based on the MQTT messages of the vehicles corresponding to the users in the non-grayscale list, provide the normal business backend services of the target vehicle networking APP to the vehicles corresponding to the users in the non-grayscale list.

[0040] Secondly, embodiments of the present invention provide a testing system for a vehicle networking app, the system being capable of implementing any of the methods described in the first aspect, the system comprising:

[0041] The acquisition module is used to acquire a gray-scale list, which includes preset user information for gray-scale release testing of the target vehicle networking APP and the vehicle information corresponding to the user.

[0042] The sending module is used to send the grayscale list to the business gateway;

[0043] The receiving module is used to receive user request information for logging into the target vehicle networking APP from the gray list obtained from the business gateway;

[0044] The business processing module is used to provide gray-scale business backend services corresponding to the target vehicle-to-everything (V2X) app to users in the gray-scale list who log in to the target V2X app, based on their login request information.

[0045] Thirdly, embodiments of the present invention provide an electronic device, including:

[0046] One or more processors;

[0047] Memory, used to store one or more programs;

[0048] When the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described in the first aspect.

[0049] Fourthly, embodiments of the present invention provide a computer-readable medium storing a computer program that, when executed by a processor, implements the steps of any of the methods described in the first aspect.

[0050] Beneficial effects of this invention:

[0051] 1. Reduce risk: By rolling out new versions gradually, the risk of system crashes or performance issues caused by large-scale updates can be reduced.

[0052] 2. Early problem detection: Problems can be detected in a small group of users and fixed in a timely manner, avoiding impacting a wider range of users.

[0053] 3. User feedback collection: Canary releases allow developers to collect direct user feedback on new features, which helps to further optimize the product.

[0054] 4. Smooth transition: Users can gradually adapt to the new version, reducing discomfort caused by sudden changes.

[0055] 5. Real-time monitoring: Through canary releases, user feedback and behavior on the new version can be monitored in real time, allowing for timely identification and adjustment of issues.

[0056] 6. High user participation: User participation in the gray-scale release process can increase user acceptance of the new version and improve user satisfaction.

[0057] 7. Gradual Upgrade: Based on feedback from different user groups, the scope of new versions can be gradually expanded to ensure stability.

[0058] 8. Improve release efficiency: Compared to the traditional full release method, canary release can speed up software updates and improve release efficiency.

[0059] 9. Enhance user experience: By gradually expanding the user base of new versions, businesses can continuously optimize software performance and functionality, thereby enhancing the user experience. Attached Figure Description

[0060] Figure 1 A schematic diagram of the testing process for releasing an existing connected vehicle app.

[0061] Figure 2 This is a schematic diagram of the overall testing process for the vehicle networking APP provided in an embodiment of the present invention.

[0062] Figure 3 A flowchart illustrating a testing method for a vehicle networking APP provided in an embodiment of the present invention. Figure 1 .

[0063] Figure 4 A flowchart illustrating a testing method for a vehicle networking APP provided in an embodiment of the present invention. Figure 2 .

[0064] Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0065] To enable those skilled in the art to better understand the technical solutions of the present invention, exemplary embodiments of the present invention are described below in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0066] Where there is no conflict, the various embodiments of the present invention and the features thereof may be combined with each other.

[0067] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0068] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded. Terms such as “connected” or “linked” are not limited to physical or mechanical connections but can include electrical connections, whether direct or indirect.

[0069] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art and the invention, and will not be interpreted as having an idealized or overly formal meaning unless expressly so defined herein.

[0070] In the technical solution of this invention, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information all comply with relevant laws and regulations and do not violate public order and good morals. The use of user data in this technical solution follows relevant national laws and regulations (e.g., the "Information Security Technology - Personal Information Security Specification"). For example: appropriate measures are taken for personal information access control; restrictions are imposed on the display of personal information; the purpose of using personal information does not exceed the scope of direct or reasonable association; and explicit identity targeting is eliminated when using personal information to avoid precisely locating a specific individual.

[0071] In this invention, some technical terms have the following meanings:

[0072] MQTT, Message Queuing Telemetry Transport.

[0073] TBox, Telematics Box, is a vehicle-mounted remote information processing terminal.

[0074] MySQL is a disk-based relational database management system.

[0075] Redis is a memory-based key-value store.

[0076] Gray-scale testing and gray-scale release are software testing and release methods. Before the official release of a product or application, a specific group of people are selected to try it out. It involves testing and releasing on a small scale, gradually expanding the number of testers, collecting user feedback, and in order to discover and correct problems in a timely manner.

[0077] Canary release testing is an effective release strategy that can protect user experience, reduce the risk of new version releases, and improve product market responsiveness and user satisfaction. This invention is a testing method for connected vehicle apps based on a canary release testing framework.

[0078] like Figure 2 As shown, the overall testing process for the vehicle networking APP provided in this embodiment of the invention is as follows:

[0079] 1. Confirm the vehicle information that needs to be tested in the system, then add the vehicles that need to be tested to the gray release list, and also store the corresponding vehicle owner information in the gray release list.

[0080] 2. When a user logs into the mobile vehicle networking APP, the request sent to the cloud will first pass through the business gateway. The business gateway will obtain the user information from the gray list and filter the request. If the user meets the requirements of the gray list, the request will be processed by the gray business backend service; if the user does not meet the requirements of the gray list, the request will be forwarded to the normal business backend service according to the original logic.

[0081] 3. After the gray-scale business backend service and the normal business backend service have finished processing, if information needs to be synchronized to the vehicle, it will be directly synchronized to the vehicle for processing via MQTT.

[0082] 4. After the vehicle-side processing is completed, the HTTP request is sent to the TBOX gateway, and the MQTT message is published to the MQTT server.

[0083] 5. After receiving the vehicle-side request, the TBOX gateway checks whether the vehicle information requested in this request is saved in the previously configured grayscale vehicle list. If it is, the HTTP request information is forwarded to the grayscale business backend for processing; otherwise, it is forwarded to the normal business backend service for processing.

[0084] 6. After receiving the message from the vehicle, MQTT retrieves the list of vehicle information in the grayscale list. If the grayscale list contains the vehicle information for this message, the MQTT message is forwarded to the grayscale business backend service; otherwise, it is forwarded to the normal business backend service for processing.

[0085] In this embodiment of the invention, for ease of description, the following description uses a business service unit as the executing entity. The business service unit is used to obtain a grayscale list and provide grayscale business backend services to grayscale list users and vehicles. The executing entity can also be other electronic devices capable of performing the above functions.

[0086] Figure 3 This is a flowchart illustrating a testing method for a vehicle networking app provided in an embodiment of the present invention; as shown below. Figure 3 As shown, the method includes:

[0087] Obtain a gray-scale list, which includes preset information on users (vehicle owners) who are conducting gray-scale release tests on the target vehicle networking APP, as well as the vehicle information corresponding to the users;

[0088] Send the grayscale list to the business gateway;

[0089] Obtain user request information for logging into the target vehicle networking APP from the gray-scale list from the business gateway;

[0090] Based on the user request information from the gray-scale list to log in to the target vehicle networking APP, provide the gray-scale business backend service corresponding to the target vehicle networking APP to the users from the gray-scale list who log in to the target vehicle networking APP.

[0091] In some embodiments, the grayscale business backend service retrieves underlying data shared with the normal business backend service for business processing.

[0092] In some embodiments, the underlying data includes: data from the MySQL system and data from the Redis system.

[0093] In some embodiments, such as Figure 4 As shown, the step of providing gray-scale business backend services corresponding to the target vehicle-to-everything (V2X) app to users in the gray-scale list who have logged into the target V2X app based on their login request information includes:

[0094] After the gray-scale business backend service completes the business processing, it will synchronize the business processing information to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list via the MQTT server.

[0095] In some embodiments, the MQTT server is an MQTT server shared with normal business backend services.

[0096] In some embodiments, it also includes:

[0097] Send the grayscale list to the TBOX gateway;

[0098] Obtain the vehicle HTTP request information corresponding to the users who logged into the target vehicle networking APP from the gray list from the TBOX gateway;

[0099] Based on the HTTP request information of the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray list, provide the gray-scale business backend services of the target vehicle networking APP to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray list.

[0100] In some embodiments, it also includes:

[0101] Send the graylist to the MQTT server;

[0102] Retrieve MQTT messages from the MQTT server for the vehicles corresponding to the users who have logged into the target connected vehicle app from the gray list.

[0103] Based on the MQTT messages of the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list, provide the gray-scale business backend services of the target vehicle networking APP to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list.

[0104] In some embodiments, it also includes:

[0105] Obtain user request information for logging into the target vehicle networking APP from the non-grayscale list from the business gateway;

[0106] Based on the user request information in the non-grayscale list, provide the normal business backend services corresponding to the target vehicle networking APP to the users in the non-grayscale list.

[0107] In some embodiments, the step of providing normal business backend services corresponding to the target vehicle networking APP to users in the non-grayscale list based on user request information in the non-grayscale list includes:

[0108] After the normal business backend service completes the business processing, it will synchronize the business processing information to the vehicle corresponding to the user in the non-grayscale list via the MQTT server.

[0109] In some embodiments, it also includes:

[0110] Obtain vehicle HTTP request information corresponding to users who log in to the target vehicle networking APP from the non-grayscale list from the TBOX gateway;

[0111] Based on the HTTP request information of the vehicles corresponding to the users in the non-grayscale list, provide the normal business backend services of the target vehicle networking APP to the vehicles corresponding to the users in the non-grayscale list.

[0112] In some embodiments, it also includes:

[0113] Retrieve MQTT messages from the MQTT server for the vehicles corresponding to users who have logged into the target connected vehicle app from the non-grayscale list.

[0114] Based on the MQTT messages of the vehicles corresponding to the users in the non-grayscale list, provide the normal business backend services of the target vehicle networking APP to the vehicles corresponding to the users in the non-grayscale list.

[0115] Based on the same inventive concept, embodiments of the present invention also provide a testing system for vehicle networking apps, the system being capable of implementing any of the methods described in the above embodiments, the system comprising:

[0116] The acquisition module is used to acquire a gray-scale list, which includes preset user information for gray-scale release testing of the target vehicle networking APP and the vehicle information corresponding to the user.

[0117] The sending module is used to send the grayscale list to the business gateway;

[0118] The receiving module is used to receive user request information for logging into the target vehicle networking APP from the gray list obtained from the business gateway;

[0119] The business processing module is used to provide gray-scale business backend services corresponding to the target vehicle-to-everything (V2X) app to users in the gray-scale list who log in to the target V2X app, based on their login request information.

[0120] Based on the same inventive concept, embodiments of the present invention also provide an electronic device. Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Figure 5 As shown, an embodiment of the present invention provides an electronic device including: one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement any of the methods described in the above embodiments; the one or more I / O interfaces 103 are connected between the processor and the memory, configured to enable information interaction between the processor and the memory.

[0121] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus).

[0122] In some embodiments, the processor 101, memory 102, and I / O interface 103 are interconnected via bus 104, and thus connected to other components of the computing device.

[0123] In some embodiments, the one or more processors 101 include a field-programmable gate array.

[0124] Based on the same inventive concept, embodiments of the present invention also provide a computer-readable medium. This computer-readable medium stores a computer program, wherein, when executed by a processor, the program implements the steps of any of the methods described in the above embodiments. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

[0125] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).

[0126] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0127] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0128] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing state information from the computer-readable program instructions. This electronic circuitry can execute the computer-readable program instructions to implement various aspects of the invention.

[0129] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0130] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0131] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0132] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0133] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0134] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A testing method for a vehicle networking app, characterized in that, include: Obtain a gray-scale list, which includes preset user information for gray-scale release testing of the target vehicle networking APP and the vehicle information corresponding to the users; Send the grayscale list to the business gateway; Obtain user request information for logging into the target vehicle networking APP from the gray-scale list from the business gateway; Based on the user request information from the gray-scale list to log in to the target vehicle networking APP, provide the gray-scale business backend service corresponding to the target vehicle networking APP to the users from the gray-scale list who log in to the target vehicle networking APP.

2. The method according to claim 1, characterized in that, The gray-scale business backend service retrieves underlying data shared with the normal business backend service for business processing.

3. The method according to claim 1 or 2, characterized in that, The step of providing gray-scale business backend services corresponding to the target vehicle-to-everything (V2X) app to users in the gray-scale list who have logged into the target V2X app based on their login request information includes: After the gray-scale business backend service completes the business processing, it will synchronize the business processing information to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list through the MQTT server. The MQTT server is the same MQTT server shared with the normal business backend service.

4. The method according to claim 3, characterized in that, Also includes: Send the grayscale list to the TBOX gateway; Obtain the vehicle HTTP request information corresponding to the users who logged into the target vehicle networking APP from the gray list from the TBOX gateway; Based on the HTTP request information of the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray list, provide the gray-scale business backend services of the target vehicle networking APP to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray list.

5. The method according to claim 3, characterized in that, Also includes: Send the graylist to the MQTT server; Retrieve MQTT messages from the MQTT server for the vehicles corresponding to the users who have logged into the target connected vehicle app from the gray list. Based on the MQTT messages of the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list, provide the gray-scale business backend services of the target vehicle networking APP to the vehicles corresponding to the users who logged into the target vehicle networking APP in the gray-scale list.

6. The method according to claim 1 or 2, characterized in that, Also includes: Obtain user request information for logging into the target vehicle networking APP from the non-grayscale list from the business gateway; Based on the user request information in the non-grayscale list, provide the normal business backend services corresponding to the target vehicle networking APP to the users in the non-grayscale list.

7. The method according to claim 6, characterized in that, The step of providing the normal business backend service corresponding to the target vehicle networking APP to users in the non-grayscale list based on user request information includes: After the normal business backend service completes the business processing, it will synchronize the business processing information to the vehicle corresponding to the user in the non-grayscale list via the MQTT server.

8. The method according to claim 7, characterized in that, Also includes: Obtain vehicle HTTP request information corresponding to users who log in to the target vehicle networking APP from the non-grayscale list from the TBOX gateway; Based on the HTTP request information of the vehicles corresponding to the users in the non-grayscale list, provide the normal business backend services of the target vehicle networking APP to the vehicles corresponding to the users in the non-grayscale list.

9. The method according to claim 7, characterized in that, Also includes: Retrieve MQTT messages from the MQTT server for the vehicles corresponding to users who have logged into the target connected vehicle app from the non-grayscale list. Based on the MQTT messages of the vehicles corresponding to the users in the non-grayscale list, provide the normal business backend services of the target vehicle networking APP to the vehicles corresponding to the users in the non-grayscale list.

10. A testing system for a vehicle networking app, characterized in that, The system is capable of implementing the method as described in any one of claims 1 to 9, and the system comprises: The acquisition module is used to acquire a gray-scale list, which includes preset user information for gray-scale release testing of the target vehicle networking APP and the vehicle information corresponding to the user. The sending module is used to send the grayscale list to the business gateway; The receiving module is used to receive user request information for logging into the target vehicle networking APP from the gray list obtained from the business gateway; The business processing module is used to provide gray-scale business backend services corresponding to the target vehicle-to-everything (V2X) app to users in the gray-scale list who log in to the target V2X app, based on their login request information.

11. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1 to 9.

12. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 9.

Images