New device software data processing method and system, computer device and storage medium

Abstract

The application is suitable for the technical field of data processing, and provides a new device software data processing method and system, a computer device and a storage medium, which are used for reducing the repetitive work of new device software data processing and improving the production efficiency of the intelligent television as a new device. The method mainly comprises the following steps: determining a target component module of a new device, wherein the target component module comprises X old modules same as a verified device and Y new modules, X is a positive integer greater than 0, and Y is a positive integer greater than or equal to 0; obtaining old module software data corresponding to the X old modules same as the verified device from a preset database; receiving new module software data corresponding to the Y new modules; and synthesizing the X old module software data and the Y new module software data into target software data corresponding to the new device.

Description

Technical Field

[0001] This application belongs to the field of data processing technology, and in particular relates to a new device software data processing method, system, computer device and storage medium. Background Technology

[0002] As smart TV technology continues to develop, users have increasingly personalized needs for its functions. For example, some users want their smart TVs for video calls or video conferencing with friends and colleagues, others want a better video viewing experience, and still others want a superior audio experience. Because manufacturing a single smart TV that meets the functional needs of most users is too expensive, and in many cases, users don't need to pay for features they rarely or never use, smart TV manufacturers, based on production cost considerations, offer different models to meet the diverse needs of users, allowing them to choose the model that best suits their requirements.

[0003] In the existing technology, smart TV manufacturers treat different models of TVs as a new type of device. Each new device requires manual configuration and writing of a corresponding set of software data so that the software data can be entered and tested after the new device is assembled, thereby enabling the smart TV that passes the test to have the functions claimed by the corresponding model.

[0004] However, different models of smart TVs share some common functions and have some unique functions. The software data for implementing these common functions needs to be repeatedly configured and processed in different models of the same type of smart TV. Moreover, a considerable number of unique functions exist in multiple models of smart TVs. The software data for implementing these unique functions also needs to be repeatedly configured and processed in these models of smart TVs, resulting in excessive repetitive work and low production efficiency of smart TVs. Summary of the Invention

[0005] The purpose of this application is to provide a new device software data processing method, system, computer device, and storage medium, which aims to reduce repetitive work in new device software data processing and improve the production efficiency of smart TVs as new devices.

[0006] In a first aspect, this application provides a novel device software data processing method, comprising:

[0007] The target component modules of the new device are determined, including: X old modules identical to those of the verified device, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0.

[0008] Retrieve X copies of the old module software data corresponding to the old module, identical to the verified device, from the preset database;

[0009] Receive Y copies of the new module software data corresponding to the new module;

[0010] The X copies of the old module software data and the Y copies of the new module software data are combined to form the target software data corresponding to the new device.

[0011] Optionally, after combining X copies of the old module software data and Y copies of the new module software data to synthesize the target software data corresponding to the new device, the method further includes:

[0012] The target software data of the new device is tested;

[0013] If the target software data passes the test, then the target software data will be used as the target production software data for the new equipment.

[0014] If the target software data fails the test, then the test-failed module software data in the target software data is marked.

[0015] Optionally, after identifying the module software data in the target software data that failed the test, the method further includes:

[0016] Receive updates to the software data of the failed test module to obtain new software data;

[0017] Trigger the execution of the step of testing the target software data of the new device.

[0018] Optionally, before combining X copies of the old module software data and Y copies of the new module software data to synthesize the target software data corresponding to the new device, the method further includes:

[0019] Determine whether the target component module meets the hardware foundation to support a specific target function. The hardware foundation for the specific target function requires the cooperation of two or more component modules. The component modules include one or more of the old module and the new module.

[0020] If the target component module meets the hardware requirements to support a specific target function, an identifier is generated indicating that the new device meets the specific target function.

[0021] Optionally, after generating an identifier that the new device satisfies the specific target function, the method further includes:

[0022] Determine the number H of existing specific software data for achieving the specific target function for the old equipment that has been put into closed-loop mass production; where H is a positive integer greater than 0.

[0023] From the H existing specific software data, determine one set of specific software data corresponding to the new device that is required to achieve the specific target function.

[0024] Optionally, retrieving X copies of the old module software data corresponding to the old module, identical to the verified device, from a preset database includes:

[0025] Determine the target functions that each of the aforementioned legacy modules needs to implement;

[0026] Determine the number K of existing legacy module software data that implements the target function corresponding to the legacy module that has been put into closed-loop mass production, where K is a positive integer greater than 0;

[0027] From the K existing legacy module software data sets, determine one set of legacy module software data corresponding to the legacy module required to achieve the target function.

[0028] Optionally, the execution of each step can be visualized.

[0029] Secondly, this application discloses a novel device software data processing system, comprising:

[0030] A determining unit is used to determine the target component modules of the new device. The target component modules include: X old modules that are the same as those of the verified device, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0.

[0031] The acquisition unit is used to acquire X copies of the old module software data corresponding to the old module that are identical to the verified device from a preset database.

[0032] The receiving unit is used to receive Y copies of the new module software data corresponding to the new module;

[0033] The synthesis unit is used to synthesize the target software data corresponding to the new device by combining X copies of the old module software data and Y copies of the new module software data.

[0034] Optionally, the system further includes:

[0035] A testing unit is used to test the target software data of the new device;

[0036] As a unit, it is used to use the target software data as the target production software data of the new device if the target software data passes the test;

[0037] The marking unit is used to mark the test-failed module software data in the target software data if the target software data fails the test.

[0038] Optionally, the system further includes:

[0039] The receiving unit is also used to receive updates to the software data of the failed test module, and obtain new software data for the module.

[0040] A triggering unit is used to trigger the execution of a step to test the target software data of the new device.

[0041] Optionally, the system further includes:

[0042] The judgment unit is used to determine whether the target component module meets the hardware foundation for supporting a specific target function. The hardware foundation for the specific target function requires the cooperation of two or more component modules. The component modules include one or more of the old module and the new module.

[0043] The generation unit is used to generate an identifier that the new device satisfies the specific target function if the target component module meets the hardware requirements for supporting the specific target function.

[0044] Optionally, the system further includes:

[0045] The determining unit is further configured to determine the number H of existing specific software data for achieving the specific target function of the old equipment that has been mass-produced in a closed loop, where H is a positive integer greater than 0;

[0046] The determining unit is further configured to determine, from the H copies of the existing specific software data, a copy of the specific software data required for the new device to achieve the specific target function.

[0047] Optionally, when the acquisition unit retrieves X copies of the old module software data corresponding to the old module that are identical to the verified device from the preset database, it is specifically used for:

[0048] Determine the target functions that each of the aforementioned legacy modules needs to implement;

[0049] Determine the number K of existing legacy module software data that implements the target function corresponding to the legacy module that has been put into closed-loop mass production, where K is a positive integer greater than 0;

[0050] From the K existing legacy module software data sets, determine one set of legacy module software data corresponding to the legacy module required to achieve the target function.

[0051] Optionally, the execution of each step can be visualized.

[0052] Thirdly, this application provides a computer device, comprising:

[0053] Processor, memory, bus, input / output interfaces, network interfaces;

[0054] The processor is connected to the memory, the input / output interface, and the network interface via the bus;

[0055] The memory stores a program;

[0056] When the processor executes the program stored in the memory, it implements the new device software data processing method as described in any of the first aspects above.

[0057] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the novel device software data processing method as described in any of the first aspects above.

[0058] Fifthly, this application provides a computer program product that, when executed on a computer, causes the computer to perform the novel device software data processing method as described in any of the first aspects above.

[0059] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0060] The new device software data processing method of this application first determines the target component modules of the new device, which include: X old modules identical to those of the verified device, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0, thus identifying the existing old modules of the new device; then, it retrieves the old module software data corresponding to the X old modules identical to those of the verified device from a preset database, and receives the new module software data corresponding to the Y new modules, thereby assembling the software data required for the target component modules of the new device; finally, it synthesizes the X old module software data and the Y new module software data into the target software data corresponding to the new device. By simply inputting the target software data into the new device, the new device can possess the functions claimed by the corresponding model. Furthermore, since the old module software data that performs the same functions for different models of new devices does not need to be repeatedly configured and written, repetitive work can be reduced, thereby improving the production efficiency of smart TVs. Attached Figure Description

[0061] Figure 1 This is a schematic flowchart of an embodiment of the new device software data processing method of this application;

[0062] Figure 2 This is a schematic flowchart of another embodiment of the new device software data processing method of this application;

[0063] Figure 3 This is a schematic diagram of the structure of an embodiment of the new device software data processing system of this application;

[0064] Figure 4 This is a schematic diagram of another embodiment of the new device software data processing system of this application;

[0065] Figure 5 This is a schematic diagram of the structure of one embodiment of the computer device of this application. Detailed Implementation

[0066] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0067] This embodiment uses a smart TV as an example to illustrate the new device. It is understood that in practical applications, the new device can also be a set-top box, mobile phone, computer, or other electronic device that requires software data to achieve control or certain functions. The software data in this embodiment can be an operating system (Android system, HarmonyOS system, iOS system, etc.), hardware driver software (sound card driver, graphics card driver, network card driver, etc.), functional expansion software data (audio amplifier parameters, brightness curve of picture quality, local backlight adjustment parameters of screen, etc.). Here, there is no limitation on the software data of the new device or the type of electronic device of the new device.

[0068] In existing technologies, manufacturers treat all new equipment models as a single category. If each category requires a separate, manually configured software dataset, it leads to excessive software versions, making management difficult and reducing development efficiency. This embodiment addresses this by using a single software dataset for models with identical motherboard module chip platforms, chip models, and minimal functional differences. The dataset is then separated to differentiate between different models. While sharing the same software, the separated data is used to distinguish between them. Different separated data is updated for each model to achieve model differentiation. The software then configures the corresponding functions to be enabled or disabled based on the separated data for each model, achieving visibility, efficiency, accuracy, and convenience. This eliminates the tedious process of repeatedly modifying separated data and optimizes the separated data management process.

[0069] Please see Figure 1 One embodiment of the new device software data processing method of this application includes:

[0070] 101. Determine the target component modules of the new equipment. The target component modules include: X old modules that are the same as those of the verified equipment, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0.

[0071] New equipment typically refers to a new model of equipment that a manufacturer has initiated a new project to produce. For example, a new model of smart TV might be a new device. The target components of a smart TV could include: a motherboard module, a sound playback module, a screen display module, a network communication module, a power supply module, etc. Some of these target components could be modules already in mass production (i.e., verified devices) that are used in older devices. Other components could be new modules that are different from any older device, or they could be modules used in other older devices.

[0072] 102. Retrieve the old module software data corresponding to X old modules with the same verified devices from the preset database.

[0073] It should be noted that this embodiment requires collecting and storing all software data from historically mass-produced and verified devices in a preset database for selection; that is, it is based on the software data of historically mass-produced and verified devices. Since the new device in this embodiment has X copies of old modules, this step can directly retrieve the old module software data corresponding to the X copies of old modules identical to those of the verified device from the preset database, reducing repetitive work in reconfiguration. For example, if the new device is a smart TV, and the motherboard module, sound playback module, screen display module, etc., in the smart TV are old modules, then the old module software data of the old modules can be queried and obtained from the preset database.

[0074] 103. Receive Y copies of new module software data corresponding to the new module.

[0075] If a new device includes Y new modules (meaning modules not used in any of the older devices), the device manufacturer needs to write corresponding software data for each new module in the new device to enable the new module's driver and cross-module functionality. For example, if the new device is a smart TV, and the camera module, microphone module, etc., are new modules, then the user needs to upload the new module's software data for selection.

[0076] 104. Combine X copies of old module software data with Y copies of new module software data to create the target software data corresponding to the new device.

[0077] By combining the X sets of old module software data obtained in step 102 and the Y sets of new module software data obtained in step 103, the target software data corresponding to the new device is synthesized. This completes the collection of the target software data required for the target components of the new device, enabling the new device to perform its basic functions. The target software data only needs to be entered into the target components of the new device. Furthermore, since the old module software data that performs the same function does not need to be repeatedly configured and written for different models of new devices, repetitive work can be reduced when enabling old modules on different models of new devices, thereby improving the production efficiency of smart TVs.

[0078] Please see Figure 2 Another embodiment of the new device software data processing method of this application includes:

[0079] 201. Determine the target components of the new equipment. The target components include: X copies of the old modules that are the same as those of the verified equipment, and Y copies of the new modules.

[0080] The execution of this step is the same as described above. Figure 1 Step 101 in the embodiment is similar, and the repeated parts will not be described again here.

[0081] 202. Obtain X copies of the old module software data corresponding to the old module that are identical to the verified device from the preset database.

[0082] The execution of this step is the same as described above. Figure 1 Step 102 in the embodiment is similar, and the repeated parts will not be described again here.

[0083] Specifically, this step involves determining the target function that each old module in the new device needs to achieve, and then determining the number K of existing old module software data in the preset database that corresponds to the target function of the old module that has been in closed-loop mass production. That is, there are K versions of existing old module software data that achieve the target function, where K is a positive integer greater than 0. Then, from the K existing old module software data, determine one set of old module software data that corresponds to the old module that achieves the target function. Usually, this step involves obtaining the latest version of the old module software data that corresponds to the old module that achieves the target function.

[0084] 203. Receive Y copies of new module software data corresponding to the new module.

[0085] The execution of this step is the same as described above. Figure 1 Step 103 in the embodiment is similar, and the repeated parts will not be described again here.

[0086] 204. Determine whether the target component module meets the hardware requirements to support the specific target function. If the target component module meets the hardware requirements to support the specific target function, proceed to step 205. If the target component module does not meet the hardware requirements to support the specific target function, the specific target function should not be added or should be ignored.

[0087] Understandably, if each target module of a new device has its own corresponding software data, control and functionality of each module can be achieved by inputting that software data. For example, when the new device is a smart TV, the smart TV's audio playback module, screen display module, network communication module, and other modules can achieve audio playback, video display, and network communication control functions by inputting corresponding software data. However, some specific target functions require multiple specific target modules as a foundation, and the software data for that specific target function must be implanted into the specific target modules that the new device needs to cooperate with in order to achieve them. For example, when the new device is a smart TV, specific target functions could be Dolby Atmos, video calling, etc. Dolby Atmos requires the smart TV's display module, multi-channel audio playback module, etc., to cooperate with the specific target function's software data in order to achieve it; video calling requires the smart TV's audio playback module, communication module, camera module, screen display module, etc., to cooperate with the specific target function's software data in order to achieve it.

[0088] Based on the above understanding, this step, after steps 202 and 203, can further determine whether the target components of the new device meet the hardware requirements to support a specific target function (such as Dolby Atmos, video call function, etc.). If the target components meet the hardware requirements to support the specific target function, it proves that the new device can obtain the specific target function by deploying software data. If the target components do not meet the hardware requirements to support the specific target function, it proves that even if the new device deploys the software data for the specific target function, it is impossible to obtain the specific target function. Therefore, in this case, adding the specific target function is not allowed or is ignored, reducing the expenditure of storage space and computing power.

[0089] 205. Generate an identifier for new equipment that meets specific target functions.

[0090] If step 204 determines that the target component module meets the hardware foundation to support the specific target function, the new device can obtain the specific target function by deploying software data. This step then generates an identifier that the new device meets the specific target function. This identifier can be visually displayed to the operator so as to inform them in a timely manner and provide a basis for decision-making.

[0091] 206. Determine the amount H of existing specific software data for achieving specific target functions for old equipment that has been put into closed-loop mass production.

[0092] It should be noted that the preset database stores different versions of existing specific software data for older, closed-loop mass-produced devices that can achieve different specific target functions. There may be H versions of the existing specific software data in the preset database used to achieve the specific target function in step 205, where H is a positive integer greater than 0. For example, the specific target function is the video call function of a smart TV, and the video call function has H versions of specific software data. This step needs to determine the number H of existing specific software data for achieving the specific target function for older, closed-loop mass-produced devices from the preset database.

[0093] 207. From H existing specific software data, determine one set of specific software data required for a new device to achieve a specific target function.

[0094] From the H existing specific software data determined in step 206, determine one specific software data corresponding to the new device to achieve a specific target function. Usually, the latest version of the specific software data corresponding to the specific target function is selected.

[0095] 208. Combine X copies of old module software data, Y copies of new module software data, and the specific software data required for the new device to achieve a specific target function into the target software data corresponding to the new device.

[0096] The X sets of old module software data obtained in step 202, the Y sets of new module software data obtained in step 203, and the specific software data for achieving specific target functions obtained in step 207 are combined to form the target software data corresponding to the new device. This achieves the goal of gathering the target software data required for the target components of the new device and the specific target functions that the new device needs to achieve. All the functions that the new device needs to claim to achieve can be realized simply by entering the target software data into the target components of the new device. Furthermore, since the old module software data that achieves the same function between different models of new devices does not need to be repeatedly configured and written, repetitive work can be reduced when the old modules are enabled in different models of new devices, thereby improving the production efficiency of smart TVs.

[0097] 209. Test the target software data of the new equipment.

[0098] To further ensure the reliability of the target software data for the new equipment in step 208, this step requires software functionality testing and hardware functionality verification before the target software data for the new equipment is officially put into production. This is to verify the ability of the target software data to perform all the claimed functions on the new equipment.

[0099] In other embodiments, the target software data of the new device can be submitted to a Git data warehouse so that personnel involved in determining the software data of each target component module of the new device can easily perform data testing and data verification. If adjustments are needed, they can also be configured through the visual editing interface of the Git data warehouse and synchronized to the target software data file of the new device.

[0100] 210. If the target software data passes the test, the target software data shall be used as the target production software data for the new equipment.

[0101] 211. If the target software data fails the test, mark the test failure module software data in the target software data.

[0102] If the target software data in step 209 fails to achieve all the claimed functions in the new device environment, the target software data is considered to have failed the test. This step then needs to mark the test-failed module software data in the target software data for manual intervention to make corrections.

[0103] 212. Receive updates to the software data of modules that failed the test and obtain new software data for those modules.

[0104] The system receives and updates the test-failed module software data marked as failing the test in step 211 to obtain the updated version of the new module software data. Then, it re-triggers the execution of step 209, repeating the process until the test is passed.

[0105] In another embodiment, the novel device software data processing method of this application... Figure 1 , Figure 2 Each step of the implementation can be visualized so that operators can understand the current status and the operation process, thereby improving efficiency.

[0106] The above embodiments describe the new device software data processing method of this application. The new device software data processing system of this application is described below. Please refer to [link / reference]. Figure 3 An embodiment of the new device software data processing system includes:

[0107] The determining unit 301 is used to determine the target component modules of the new device. The target component modules include: X old modules that are the same as those of the verified device, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0.

[0108] The acquisition unit 302 is used to acquire X copies of the old module software data corresponding to the old module that are identical to the verified device from a preset database;

[0109] The receiving unit 303 is used to receive Y copies of the new module software data corresponding to the new module;

[0110] Synthesis unit 304 is used to synthesize the target software data corresponding to the new device by combining X copies of the old module software data and Y copies of the new module software data.

[0111] The operation performed by the new device software data processing system in this application is the same as described above. Figure 1 The operations performed in the embodiments are similar and will not be described again here.

[0112] Please see Figure 4 Another embodiment of the new device software data processing system includes:

[0113] The determining unit 401 is used to determine the target component modules of the new device. The target component modules include: X old modules that are the same as those of the verified device, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0.

[0114] The acquisition unit 402 is used to acquire X copies of the old module software data corresponding to the old module that are identical to the verified device from a preset database;

[0115] The receiving unit 403 is used to receive Y copies of the new module software data corresponding to the new module;

[0116] Synthesis unit 404 is used to synthesize the target software data corresponding to the new device by combining X copies of the old module software data and Y copies of the new module software data.

[0117] Optionally, the system further includes:

[0118] Test unit 405 is used to test the target software data of the new device;

[0119] As unit 406, if the target software data passes the test, the target software data is used as the target production software data of the new device;

[0120] The marking unit 407 is used to mark the test-failed module software data in the target software data if the target software data fails the test.

[0121] Optionally, the system further includes:

[0122] The receiving unit 403 is also used to receive updates to the test-failed module software data to obtain new module software data;

[0123] Triggering unit 408 is used to trigger the execution of the step of testing the target software data of the new device.

[0124] Optionally, the system further includes:

[0125] The judgment unit 409 is used to determine whether the target component module meets the hardware foundation for supporting a specific target function. The hardware foundation for the specific target function requires the cooperation of two or more component modules. The component modules include one or more of the old module and the new module.

[0126] The generation unit 410 is used to generate an identifier that the new device meets the specific target function if the target component module meets the hardware foundation for supporting the specific target function.

[0127] Optionally, the system further includes:

[0128] The determining unit 401 is further configured to determine the number H of existing specific software data for achieving the specific target function of the old equipment that has been mass-produced in a closed loop, wherein H is a positive integer greater than 0;

[0129] The determining unit 401 is further configured to determine from the H copies of the existing specific software data a copy of the specific software data required for the new device to achieve the specific target function.

[0130] Optionally, when the acquisition unit 402 acquires X copies of the old module software data corresponding to the old module that are identical to the verified device from the preset database, it is specifically used for:

[0131] Determine the target functions that each of the aforementioned legacy modules needs to implement;

[0132] Determine the number K of existing legacy module software data that implements the target function corresponding to the legacy module that has been put into closed-loop mass production, where K is a positive integer greater than 0;

[0133] From the K existing legacy module software data sets, determine one set of legacy module software data corresponding to the legacy module required to achieve the target function.

[0134] Optionally, the execution of each step can be visualized.

[0135] The operation performed by the new device software data processing system in this application is the same as described above. Figure 2 The operations performed in the embodiments are similar and will not be described again here.

[0136] The computer device in the embodiments of this application is described below. Please refer to [link / reference]. Figure 5 One embodiment of the computer device in this application includes:

[0137] The computer device 500 may include one or more central processing units (CPUs) 501 and memory 502, wherein the memory 502 stores one or more application programs or data. The memory 502 is volatile or persistent storage. The program stored in the memory 502 may include one or more modules, each module including a series of instruction operations on the computer device. Furthermore, the processor 501 may be configured to communicate with the memory 502 and execute the series of instruction operations stored in the memory 502 on the computer device 500. The computer device 500 may also include one or more wireless network interfaces 503, one or more input / output interfaces 504, and / or one or more operating systems, such as Windows Server, Mac OS, Unix, Linux, FreeBSD, etc. The processor 501 can execute the aforementioned... Figure 1 or Figure 2 The specific operations performed in the illustrated embodiment will not be described in detail here.

[0138] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes: USB flash drive, mobile hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, and other media capable of storing program code.

[0139] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A novel device software data processing method, characterized in that, include: The target component modules of the new device are determined, including: X old modules identical to those of the verified device, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0. Retrieve X copies of the old module software data corresponding to the old module, identical to the verified device, from the preset database; Receive Y copies of the new module software data corresponding to the new module; Combine X copies of the old module software data with Y copies of the new module software data to create the target software data corresponding to the new device; Before combining X copies of the old module software data and Y copies of the new module software data to synthesize the target software data corresponding to the new device, the method further includes: Determine whether the target component module meets the hardware foundation to support a specific target function. The hardware foundation for the specific target function requires the cooperation of two or more component modules. The component modules include one or more of the old module and the new module. If the target component module meets the hardware requirements to support a specific target function, an identifier is generated indicating that the new device meets the specific target function. If the target component module does not meet the hardware requirements to support a specific target function, the addition of that specific target function is not allowed or is ignored.

2. The new device software data processing method according to claim 1, characterized in that, After combining X copies of the old module software data and Y copies of the new module software data to form the target software data corresponding to the new device, the method further includes: The target software data of the new device is tested; If the target software data passes the test, then the target software data will be used as the target production software data for the new equipment. If the target software data fails the test, then the test-failed module software data in the target software data is marked.

3. The new device software data processing method according to claim 2, characterized in that, After identifying the module software data that failed the test in the target software data, the method further includes: Receive updates to the software data of the failed test module to obtain new software data; Trigger the execution of the step of testing the target software data of the new device.

4. The new device software data processing method according to claim 1, characterized in that, After generating an identifier that the new device satisfies the specific target function, the method further includes: Determine the number H of existing specific software data for achieving the specific target function for the old equipment that has been put into closed-loop mass production; where H is a positive integer greater than 0. From the H existing specific software data, determine one set of specific software data corresponding to the new device that is required to achieve the specific target function.

5. The new device software data processing method according to claim 1, characterized in that, Retrieving X copies of the old module software data corresponding to the old module, identical to the verified device, from the preset database includes: Determine the target functions that each of the aforementioned legacy modules needs to implement; Determine the number K of existing legacy module software data that implements the target function corresponding to the legacy module that has been put into closed-loop mass production, where K is a positive integer greater than 0; From the K existing legacy module software data sets, determine one set of legacy module software data corresponding to the legacy module required to achieve the target function.

6. The new device software data processing method according to any one of claims 1 to 5, characterized in that, The execution of each step is visualized.

7. A novel equipment software data processing system, characterized in that, include: A determining unit is used to determine the target component modules of the new device. The target component modules include: X old modules that are the same as those of the verified device, and Y new modules, where X is a positive integer greater than 0 and Y is a positive integer greater than or equal to 0. The acquisition unit is used to acquire X copies of the old module software data corresponding to the old module that are identical to the verified device from a preset database. The receiving unit is used to receive Y copies of the new module software data corresponding to the new module; A synthesis unit is used to synthesize X copies of the old module software data and Y copies of the new module software data into target software data corresponding to the new device; The system also includes: The judgment unit is used to determine whether the target component module meets the hardware foundation for supporting a specific target function. The hardware foundation for the specific target function requires the cooperation of two or more component modules. The component modules include one or more of the old module and the new module. The generation unit is used to generate an identifier that the new device satisfies the specific target function if the target component module meets the hardware requirements for supporting the specific target function.

8. A computer device, characterized in that, include: Processor, memory, bus, input / output interfaces, network interfaces; The processor is connected to the memory, the input / output interface, and the network interface via the bus; The memory stores a program; When the processor executes the program stored in the memory, it implements the new device software data processing method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the novel device software data processing method as described in any one of claims 1 to 6.

Images