Design data processing method, device, equipment and medium

Abstract

The present application provides a method, apparatus, device, and medium for processing design data, which are applied to a design data processing system. The design data processing system provides an underlying data processing interface and a proxy service for proxying calls to the data processing interface. The design data processing method includes: responding to a user's product design operation in the design data processing system, calling a target interface for the product design operation request through a target proxy service, where the target interface belongs to the data processing interface, and the target proxy service is the proxy service corresponding to the target interface; recording the call of the target interface to obtain operation record information of the product design operation, wherein the operation record information is used for problem troubleshooting. Thus, by proxying and recording the call of the product design operation to the underlying data processing interface, accurate and reliable operation record information is obtained, and based on the operation record information, the efficiency of problem troubleshooting in the product design process is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for processing design data. Background Art

[0002] In the design data processing system, designers perform product design on the production side, such as furniture design and house interior layout design in the home design data processing system.

[0003] Currently, when designers encounter problems while designing products through data processing systems, they usually record the problems by taking screenshots or recording videos, and then feed the recorded problems back to people with design experience or developers who design data processing systems to seek solutions to the problems.

[0004] However, the data and data processing processes involved in designing a data processing system are diverse and the environment is very complex, resulting in low efficiency in troubleshooting using the above method. Summary of the Invention

[0005] The present application provides a design data processing method, apparatus, device and medium to solve the problem of low efficiency in troubleshooting during product design.

[0006] In the first aspect, an embodiment of the present application provides a method for processing design data, which is applied to a design data processing system. The design data processing system provides an underlying data processing interface and a proxy service for proxying calls to the data processing interface. The method for processing design data includes: responding to a user's product design operation in the design data processing system, calling the target interface called by the product design operation request through the target proxy service, the target interface belongs to the data processing interface, and the target proxy service is the proxy service corresponding to the target interface; recording the call of the target interface to obtain operation record information of the product design operation, wherein the operation record information is used for problem troubleshooting.

[0007] In a second aspect, an embodiment of the present application provides a design data processing device, which is applied to a design data processing system. The design data processing system provides one or more underlying data processing interfaces and a proxy service for proxying calls to the data processing interfaces. The design data processing device includes:

[0008] The calling unit is configured to call a target interface of the product design operation request through a target proxy service in response to a product design operation of the user in the design data processing system, wherein the target interface belongs to the data processing interface and the target proxy service is a proxy service corresponding to the target interface;

[0009] The recording unit is used to record the call of the target interface and obtain the operation record information of the product design operation, wherein the operation record information is used for problem troubleshooting.

[0010] On the third aspect, an embodiment of the present application provides a data processing method, which is applied to a data processing system. The data processing system provides an underlying data processing interface and a proxy service for proxying calls to the data processing interface. The data processing method includes: responding to user operations of the data processing system, calling the target interface called by the user operation request through the target proxy service, the target interface belongs to the data processing interface, and the target proxy service is the proxy service corresponding to the target interface; recording the call of the target interface to obtain operation record information of the user operation, wherein the operation record information is used for problem troubleshooting.

[0011] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the electronic device to execute the method for processing design data provided in the first aspect of the embodiment of the present application, and / or to enable the electronic device to execute the method for processing design data provided in the third aspect of the embodiment of the present application.

[0012] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, it implements the method for processing design data provided in the first aspect of the embodiment of the present application, and / or, when the computer program is executed by a processor, it implements the method for processing design data provided in the third aspect of the embodiment of the present application.

[0013] In an embodiment of the present application, the design data processing system is provided with an underlying data processing interface and a proxy service for proxying the call of the data interface. In response to the user's product design operation in the design processing system, the target interface requested to be called by the product design operation is called through the target proxy service. The target interface belongs to the data processing interface, and the target proxy service is the proxy service corresponding to the target interface. Afterwards, the call of the target interface is recorded to obtain the operation record information of the product design operation, and the operation record information is used for problem troubleshooting. Therefore, by proxying and recording the call of the data processing interface requested to be called by the product design operation, the accuracy of the operation record information of the product design operation is improved, and the operation record information reflects the underlying data processing process of the product design operation. Compared with taking screenshots or recording videos of problems that occur, the operation record information can provide more detailed, reliable, accurate and useful information for problem troubleshooting, which is conducive to improving the efficiency of problem troubleshooting. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0015] Figure 1 A schematic diagram of a scenario of a method for processing design data provided in an embodiment of the present application;

[0016] Figure 2 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 1 ;

[0017] Figure 3 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 2 ;

[0018] Figure 4 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 3 ;

[0019] Figure 5 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 4 ;

[0020] Figure 6 This is an example diagram of an operation record page in the design data processing method provided in an embodiment of the present application;

[0021] Figure 7a A schematic diagram of a process for recording product design operations in a design data processing method provided in an embodiment of the present application;

[0022] Figure 7b A schematic diagram of a process for restoring product design operations in a design data processing method provided in an embodiment of the present application;

[0023] Figure 8 A structural block diagram of a device for processing design data provided in an embodiment of the present application;

[0024] Figure 9 A flowchart of a data processing method provided in an embodiment of the present application;

[0025] Figure 10 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.

[0026] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0027] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0028] The terms "first," "second," "third," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, such that the embodiments of the application described herein can be practiced in orders other than those illustrated or described herein.

[0029] In addition, the terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not explicitly listed or inherent to such process, method, product or apparatus.

[0030] First, some of the terms used in the embodiments of this application are explained:

[0031] Design data processing system: This can be an online system with a visual user interface, allowing users to design multi-dimensional product structures and patterns. For example, users can design cabinets, tables, and floor plans in a home design editor. The design data processing system can be presented in the form of a webpage, website, or application client.

[0032] Product design operations: interactive operations used to design products, such as mouse dragging operations and command input operations on the visual operation interface of the design data processing system.

[0033] The underlying data processing interface provides data processing services. Upper-layer product design operations are transparent to the underlying data processing interface. In other words, the underlying data processing interface is independent of upper-layer product design operations, meaning it doesn't need to be frequently updated with changes in product design operations (such as the addition of new product design operations). This demonstrates the high controllability and stability of the underlying data processing interface within the design data processing system.

[0034] Proxy service for proxying calls to data processing interfaces: a functional function implemented through programming technology that is used to proxy the calling process of product design operations on data processing interfaces.

[0035] Serialization: Converts data to be stored and / or transmitted from its original data form into a data form (e.g., a string) that can be stored and / or transmitted (or is convenient for storage and / or transmission). Deserialization, therefore, is the process of restoring data from its serialized form back to its original form.

[0036] Product Data Management (PDM): A technology used to manage all product-related information (such as part information, configuration, documentation, electronic drawings, product structure, and permissions) and all product-related processes (including process definition and management). Implementing PDM can improve production efficiency, enhance the effectiveness of product lifecycle management, strengthen the efficient use of documents, drawings, and data, and standardize product design workflows.

[0037] Luban Software Development Kit (SDK): used to parse product design data exported from PDM (referred to as PDM data, such as product models and their constraint data) to achieve product visualization and design on the front end.

[0038] Luban interface: used to call the underlying service or underlying library for processing PDM data. All operations that process PDM data require calling the Luban interface.

[0039] In the design data processing system, there are two ways to record product design operations:

[0040] In one approach, designers record problems by taking screenshots or recording videos, and then feed the recorded problems back to relevant personnel. However, this approach requires manual recording, and the data and data processing processes involved in designing data processing systems are diverse (for example, the design data processing system needs to access various PDMs related to product production on the production side). The environment is very complex, and simple screenshots or recorded videos cannot accurately reflect the underlying data processing process, resulting in low problem troubleshooting efficiency.

[0041] Another approach involves providing a tool for recording product design operations within the design data processing system. However, this tool is highly dependent on the design data processing system, and therefore, the product design operations. After the design data processing system is updated, the tool may be unable to record some product design operations. For example, after a new product design operation is developed within the design data processing system, the tool may be unable to record the newly developed product design operation. Another example is that after the design data processing system is updated, the tool may be unable to record the product design operations that it could record before the update. Consequently, this approach reduces the efficiency and reliability of troubleshooting.

[0042] In order to solve the above problems, an embodiment of the present application proposes a method for processing design data, which is applied to a design data processing system, and the design data processing system provides an underlying data processing interface and a proxy service for proxying the call of the data processing interface. In this method, the accuracy of the operation record information of the product design operation is improved by proxying and recording the call of the data processing interface by the proxy service. At the same time, the reliability and stability of the recording of the product design operation are improved by utilizing the characteristics that all product design operations need to call the underlying data processing interface, and utilizing the controllability and stability of the underlying data processing interface. The operation record information of the product design operation can be used for problem troubleshooting. On the one hand, more design cases can be provided for problem troubleshooting based on the operation record information. On the other hand, since the operation record information of the product design operation reflects the interface call process of the product design operation, regression testing for problem troubleshooting can be implemented based on the operation record information, which can reduce the workload of regression testing and improve the efficiency and reliability of problem troubleshooting.

[0043] For example, Figure 1 Schematic diagram of a scenario of a method for processing design data provided in an embodiment of the present application. Figure 1As shown, a design data processing system runs on the data processing device. This system provides an underlying data processing interface and a proxy service for proxying calls to the data processing interface. When a user performs a product design operation on the design data processing system, the proxy service calls the data processing interface requested by the product design operation and records the calls to generate operation log information. This operation log information can be used for troubleshooting.

[0044] The data processing device may be a terminal. The terminal may be a personal digital assistant (PDA), a handheld device with wireless communication capabilities (such as a smartphone or tablet), a computing device (such as a personal computer (PC)), an in-vehicle device, a wearable device (such as a smart watch or smart bracelet), or a smart home device (such as a smart display device). Figure 1 Take PC as an example.

[0045] The above is only an exemplary application scenario. The embodiment of the present application can be applied to the operation record of any data processing system on the Internet, such as recording document editing operations on a document editing system, recording drawing operations on a drawing system, etc.

[0046] The technical solution of the present application is described in detail below through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0047] refer to Figure 2 , Figure 2 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 1 .like Figure 2 As shown, the design data processing method includes:

[0048] S201, in response to a user performing a product design operation in a design data processing system, calling a target interface of a product design operation request through a target proxy service.

[0049] The proxy service is located in the design data processing system. In the design data processing system, a bottom-level data processing interface and a proxy service for proxying the call to the bottom-level data processing interface are provided. In the design data processing system, there may be one or more bottom-level data processing interfaces. Among the multiple bottom-level data processing interfaces, a corresponding proxy service can be provided for each data processing interface, and corresponding proxy services can also be provided for some data processing interfaces (such as data processing interfaces with more complex data processing processes or data processing interfaces with higher error rates).

[0050] Among multiple underlying data processing interfaces, a proxy service can be provided for each data processing interface, that is, the data processing interface and the proxy service correspond one to one; a shared proxy service can also be provided for all data processing interfaces, that is, the shared proxy service is used to proxy the calls of all data processing interfaces; a proxy service can also be provided for each data processing interface in the data processing interface of the first part, and a shared proxy service can be provided for all data processing interfaces in the data processing interface of the second part, so as to improve the accuracy of the proxy service in proxying the calls of the data processing interfaces, wherein the calling process of different data processing interfaces in the data processing interface of the first part is the same, and the calling process of different data processing interfaces in the data processing interface of the second part is different.

[0051] Among them, the target interface belongs to the data processing interface. Specifically, the target interface refers to the data processing interface called by the user's product design operation request; the target proxy service is the proxy service corresponding to the target interface. Specifically, the target proxy service is a proxy service used to proxy the call of the target interface.

[0052] A product design operation can call one or more target interfaces. For example, in the visual operation interface of the design data processing system, the product design operation of adding a partition to a cabinet calls the data processing interface for calculating the partition size and the data processing interface for calculating the partition position.

[0053] On a design data processing system, product design operations can be performed by either users or process automation software robots. These operations can trigger calls to corresponding data processing interfaces, and proxy services can passively receive or actively monitor these calls. For example, when a user performs product design operation A on a design data processing system, this triggers a call to data processing interface B. Proxy service C, which acts as a proxy for the call to data processing interface B, passively receives or actively monitors this call.

[0054] In this embodiment, in response to the user's product design operation in designing a data processing system, a call instruction to the target interface of the product design operation is triggered. After receiving the call instruction, the target proxy service corresponding to the target interface responds to the call instruction and calls the target interface.

[0055] S202, recording the call of the target interface to obtain operation record information of the product design operation, which is used for problem troubleshooting.

[0056] Among them, the operation record information of the product design operation can be used to troubleshoot problems arising from the product design operation, problems arising from other product design operations, problems caused by factors other than product design operations (such as data errors, equipment abnormalities), and problems arising from the same product design operation performed at different times.

[0057] For example, a user performs a product design operation A on a design data processing system before an update and obtains operation record information D for product design operation A. A user performs a product design operation A on a design data processing system after an update and obtains operation record information E for product design operation A. By comparing operation record information D with operation record information E, problems with product design operation A before and / or after the design data processing system is updated can be identified. If there were no problems with product design operation A before the design data processing system was updated, but there were problems with product design operation A after the design data processing system was updated, problems with product design operation A after the design data processing system was updated can be identified by comparing operation record information D with operation record information E. If there were no problems with product design operation A after the design data processing system was updated, but there were problems with product design operation A before the design data processing system was updated, problems with product design operation A before the design data processing system was updated can be identified by comparing operation record information D with operation record information E.

[0058] The updating of the design data processing system includes the iteration of the front-end version of the design data processing system and / or the updating of the back-end data of the design data processing system.

[0059] In this embodiment, in the target proxy service, the call of the product design operation to the target interface can be recorded from the start of the call of the target interface to the end of the call of the target interface, and the operation record information of the product design operation can be obtained. Among them, when recording the call of the product design operation to the target interface, the data involved in the call of the target interface can be recorded, and the event that the product design operation calls the target interface can also be recorded (for example, recording "product design operation A calls data processing interface B"). Therefore, the operation record information of the product design operation can reflect the calling process of the product design operation to one or more target interfaces, and then reflect the underlying data processing process of the product design operation. Troubleshooting based on the operation record information of the product design operation can improve the efficiency and reliability of problem troubleshooting.

[0060] In an embodiment of the present application, on a design data processing system, a proxy service is used to proxy and record the calls of product design operations to corresponding data processing interfaces, thereby recording product design operations and obtaining operation record information of product design operations, thereby improving the accuracy of the operation record information. Since the data processing interface is a bottom-level interface with the characteristics of stability and reliability, the recording of product design operations also has stability and reliability, thereby improving the reliability of the operation record information. Therefore, based on accurate, reliable operation record information that can reflect the process of product design operations calling the data processing interface, the efficiency and reliability of problem troubleshooting can be effectively improved.

[0061] In some embodiments, the invocation of the target interface involves at least one of the following data: a call parameter used by the product design operation to invoke the target interface, a call result of the target interface, and an interface identifier of the target interface. In this case, a possible implementation of S202 includes determining operation record information of the product design operation based on at least one of the call parameter used by the product design operation to invoke the target interface, the call result of the target interface, and the interface identifier of the target interface.

[0062] Among them, considering that the product design operation may call multiple target interfaces, the interface identifier of the target interface can be used to distinguish the target interface called by the product design operation, thereby improving the data clarity and accuracy of the operation record information of the product design operation. The interface identifier of the data processing interface may include at least one of the interface name, class name, and function name of the target interface. The calling parameter used by the product design operation to call the target interface refers to the parameter value passed to the target interface in the call of the product design operation to the target interface. For example, when the product design operation of adding a partition in the cabinet calls the data processing interface for calculating the position of the partition, the cabinet position is passed to the data processing interface. The calling result of the target interface refers to the processing result obtained after the underlying service or underlying library corresponding to the target interface is called for data processing. For example, when the data processing interface is the underlying interface for calculating the position of the partition, the calling result of the data processing interface is the partition position.

[0063] In this implementation, if the data involved in the call of the target interface includes the call parameters of the product design operation used to call the target interface, the operation record information of the target operation can be obtained by recording the call parameters, such as determining that the operation record information of the product design operation includes the call parameters; and / or, if the data involved in the call of the target interface includes the call result of the target interface, the operation record information of the product design operation can be obtained by recording the call result, such as determining that the operation record information of the product design operation includes the call result; and / or, if the data involved in the call of the target interface includes the interface identifier of the target interface, the operation record information of the product design operation can be obtained by recording the interface identifier, such as determining that the operation record information of the product design operation includes the interface identifier.

[0064] Furthermore, data required to be recorded when calling a data processing interface can also be pre-set. Based on the data required to be recorded when calling the target interface and the data actually involved in the target interface call, the target interface call is recorded to obtain operation record information for the product design operation. For example, if the target interface call result is required to be recorded, and the target interface call also involves the target interface call result, the product design operation operation record information can be determined based on the target interface call result.

[0065] refer to Figure 3 , Figure 3 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 2 .like Figure 3 As shown, the design data processing method includes:

[0066] S301, in response to the user's product design operation in the design data processing system, calls the target interface called by the product design operation request through the target proxy service, and the data involved in the call of the target interface include at least one of the following: the calling parameters used by the product design operation to call the target interface, the calling result of the target interface, and the interface identifier of the target interface.

[0067] The implementation principle and technical effects of S301 may refer to the aforementioned embodiments and will not be described in detail.

[0068] S302, obtaining operation record information of the product design operation by serializing at least one of the call parameters, the call result, and the interface identifier.

[0069] In this embodiment, when the data involved in the call of the target interface includes at least one of the call parameters used by the product design operation to call the target interface, the call result of the target interface, and the interface identifier of the target interface, considering that the data types of the call parameters, the call result, and the interface identifier may be inconvenient to store and / or transmit, at least one of the call parameters, the call result, and the interface identifier is serialized in the proxy service to obtain the serialized result of the call parameters, the serialized result of the call result, and / or the serialized result of the interface identifier. Among them, the serialized result of the call parameters, the serialized result of the call result, and / or the serialized result of the interface identifier are easy to store and / or transmit. Afterwards, in the proxy service, it is determined that the operation record information of the product design operation includes at least one of the serialized result of the call parameters, the serialized result of the call result, and the serialized result of the interface identifier.

[0070] After obtaining the operation log information of the product design operation, the operation log information of the product design operation can be stored so that the operation log information can be used for troubleshooting at any time. For example, the operation log information can be stored in the object storage service (OSS) of the design data processing system or elsewhere.

[0071] In one possible implementation, the serialization processing of the call parameter includes: if the data type of the call parameter is an entity type, determining the serialization result of the call parameter to be the index value of the call parameter; or, if the data type of the call parameter is an attribute type, determining the serialization result of the call parameter to be the attribute name corresponding to the call parameter and the index value of the product entity to which the call parameter belongs; or, if the data type of the call parameter is a numeric type, determining the serialization result of the call parameter to be the call parameter; or, if the data type of the call parameter is a mixed type, traversing and serializing the data in the call parameter to obtain the serialization result of the call parameter. Thus, based on the data type of the call parameter, the call parameter is serialized in a targeted and appropriate manner, thereby improving the accuracy of the serialization processing of the call operation.

[0072] Entity types can also be understood as product types. For example, in a home design data processing system, entity types might include cabinets, tables, partitions, and lamps. Attribute types refer to the attributes of an entity, such as the material and dimensions of a cabinet. Numeric types refer to numbers, such as decimal or binary. Mixed types refer to call parameters containing multiple types of data, such as object structures or array interfaces, which contain both entity-type and attribute-type data.

[0073] In this implementation, considering that the type of the call parameter used by the product design operation to call the data processing interface can be any of entity type, attribute type, value type, and mixed type, in order to improve the accuracy of serialization of the call parameter, different serialization processing methods can be used for different types of call parameters, as follows:

[0074] In the case where the data type of the calling parameter is an entity type, the calling parameter is a product entity. For example, the calling parameter is a parameter indicating the product entity of a cabinet, such as the full English name of the cabinet. In the product entity set, each product entity corresponds to a unique index value, wherein the index value of the product entity is used to indicate the position of the product entity in the product entity set. For example, multiple product entities in the product entity set form a tree structure, and the index value of the product indicates the position of the product entity in the tree structure. Therefore, in the case where the data type of the calling parameter is an entity type, the index value of the calling parameter can be determined, and the serialization result of the calling parameter can be determined as the index value of the calling parameter.

[0075] When the data type of a call parameter is an attribute type, the call parameter is an attribute value of a product entity. For example, the call parameter is the size of a cabinet product entity. In order to ensure that the serialization result of the call parameter can reflect which attribute of which product entity the call parameter corresponds to, during the serialization process of the call parameter, the serialization result of the call parameter can be determined as the attribute name corresponding to the call parameter and the index value of the product entity to which the call parameter belongs.

[0076] When the data type of the calling parameter is a numeric type, since the data of the numeric type itself belongs to the string type and is easy to store, the serialization result of the calling parameter can be determined to be the calling parameter itself. That is, when the data type of the calling parameter is a numeric type, there is no need to serialize the calling parameter, and the calling parameter itself can be directly recorded.

[0077] In the case where the data type of the calling parameter is a mixed type, such as an object type or an array type, the data contained in the calling parameter can be traversed one by one, and serialization processing can be performed on the traversed data to obtain the serialization result of the traversed data. Thereafter, based on the serialization results of all the data contained in the calling parameter, the serialization result of the calling parameter can be combined. In the process of serializing the traversed data, it can be determined whether the data type of the traversed data is an entity type, an attribute type, a numerical type, or a mixed type. According to the data type of the traversed data, the serialization processing method corresponding to the data type is adopted to serialize the traversed data to obtain the serialization result of the traversed data.

[0078] In the process of serializing the call result of the target interface, the call result can be serialized by referring to the serialization method of the call parameters, which will not be described in detail here.

[0079] During the serialization process of the interface identifier of the target interface, if the data type of the interface identifier of the target interface is a string type, the serialization result of the interface identifier can be determined to be the interface identifier itself; otherwise, the interface identifier of the target interface can be mapped to a unique string, and the serialization result of the interface identifier can be determined to be the string corresponding to the interface identifier after mapping.

[0080] In the embodiment of the present application, a proxy service is used on the design data processing system to proxy the calls of product design operations to the target interface, and the call parameters, call results, and interface identifiers of the target interface are serialized to obtain operation record information of the product design operations. This improves the accuracy, stability, and reliability of the operation record information, and makes the operation record information easier to store and transmit, thereby improving the efficiency, reliability, and convenience of problem troubleshooting on the design data processing system.

[0081] Based on any of the foregoing embodiments, optionally, the data involved in the call of the target interface includes the time information of the target interface call. At this time, another possible implementation of S202 includes: obtaining operation record information by recording the time information of the target interface call. A possible implementation of S302 includes: serializing at least one of the call parameters, the call result, and the interface identifier to obtain the serialization result of the call parameters, the serialization result of the call result, and / or the serialization processing result of the interface identifier; obtaining the operation record information of the product design operation based on at least one of the serialization result of the call parameters, the serialization result of the call result, the serialization processing result of the interface identifier, and the time information of the target interface call. Thereby, the operation record information is further enriched, and the efficiency and reliability of problem troubleshooting when the operation record information is used for problem troubleshooting are improved.

[0082] The time information of the target interface call may include at least one of the following: the start time of the target interface call, the end time of the target interface call, and the duration of the target interface call. The start time of the target interface call may be the moment when the user's product design operation is detected, or the moment when the product design operation triggers the call instruction to the data processing interface, or the moment when the target proxy service starts calling the target interface. The end time of the target interface call may be the time when the call result of the target interface is obtained. The duration of the target interface call may be the time difference between the start time and the end time of the target interface call.

[0083] In this optional method, in the possible implementation method of S202, the operation record information may include the time information of the product design operation calling the target interface; in the possible implementation method of S203, the operation record information may include at least one of the serialization results of the call parameters, the serialization results of the call results, and the serialization processing results of the interface identifier when the product design operation calls the target interface, and may also include the time information of the product design operation calling the target interface.

[0084] refer to Figure 4 , Figure 4 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 3 .like Figure 4 As shown, the design data processing method includes:

[0085] S401, in response to a user performing a product design operation in a design data processing system, calling a target interface of a product design operation request through a target proxy service.

[0086] S402, record the call of the target interface and obtain the operation record information of the product design operation.

[0087] Among them, the implementation principles and technical effects of S401 and S402 can refer to the aforementioned embodiments, for example, refer to the description of S201 and S202, or refer to the description of S301 and S302, and will not be repeated here.

[0088] S403, restoring the product design operation according to the operation record information of the product design operation, so as to troubleshoot the problem by means of operation restoration.

[0089] In this embodiment, the product design operation can be restored by restoring the calls to all target interfaces called by the product design operation. Therefore, during the implementation process, in response to the request to restore the product design operation, the operation record information of the product design operation can be obtained. Based on the operation record information of the product design operation, all target interfaces called by the product design operation can be re-called to restore the product design operation. Problems can be troubleshooted through the restoration of the product design operation, that is, problem troubleshooting can be performed through regression testing.

[0090] The request to restore a product design operation can be triggered by a user, for example, by clicking a "regression test" button on the visual operation interface of the design data processing system. Alternatively, the request to restore a product design operation can be automatically triggered by the design data processing system. For example, when the design data processing system detects a problem with a product design operation, it can search the database for operation records of the product design operation. If so, it can obtain the operation records of the product design operation and restore the operation based on the operation records to troubleshoot the problem.

[0091] Among them, S402 and S403 can be executed on the same device or on different devices, that is, the process of proxying and recording the underlying interface call of the product design operation through the proxy service to obtain the operation record information, and the process of restoring the product design operation based on the operation record information of the product design operation can be executed on the same device or on different devices. For example, user U1 performs a product design operation on device Q1, and the design data processing system on device Q1 generates the operation record information of the product design operation. User U1 shares the operation record information of the product design operation to the cloud through device Q1. User U2 obtains the operation record information of the product design operation from the cloud on device Q2, and based on the operation record information of the product design operation, re-calls the target interface called by the product design operation to restore the product design operation.

[0092] Optionally, in addition to restoring the entire product design operation, you can also restore the calls to individual target interfaces invoked by the product design operation. For example, you can retrieve the operation log information related to the calls to the individual target interfaces from the operation log information of the product design operation, and then re-call the individual target interfaces based on the operation log information related to the calls to the individual target interfaces. This improves the flexibility of restoring calls to the target interfaces and enhances the flexibility of troubleshooting.

[0093] Optionally, since the product design operation can call one or more target interfaces, the product design operation can correspond to one or more operation record information. The problem troubleshooting process may include: obtaining an operation record information from the operation record information of the product design operation according to the recording order of the operation record information of the product design operation. For the convenience of distinction, the operation record information will be referred to as the target information in the future; based on the target information, the target interface corresponding to the target information is re-called; according to the target information (reflecting the call status of the target interface originally called) and the call status of the target interface re-called, the problem is troubleshooted; after the problem is troubleshooted based on the target information, the target information can be deleted or marked as troubleshooted; determining whether there is unchecked operation record information in the operation record information of the product design operation; if there is unchecked operation record information in the operation record information of the product design operation, continuing to traverse the unchecked operation record information of the product design operation, and performing the above operation on the traversed operation record information until all the operation record information of the product design operation is deleted or marked as troubleshooted. Thereby, the efficiency of problem troubleshooting is improved, and the omission of operation record information is avoided, thereby improving the accuracy of problem troubleshooting.

[0094] In an embodiment of the present application, on a design data processing system, a proxy service is used to proxy and record the call of a target interface for a product design operation, and operation record information of the product design operation is obtained. Based on the operation record information of the product design operation, the target interface is re-called to realize the restoration of the product design operation, so that problem troubleshooting is performed by restoring the product design operation, thereby improving the efficiency, reliability and convenience of problem troubleshooting.

[0095] In some embodiments, the invocation of the target interface involves at least one of the following data: the invocation parameters used by the product design operation to invoke the target interface, the invocation result of the target interface, and the interface identifier of the target interface. In this case, a possible implementation of S403 includes restoring the product design operation based on data related to at least one of the invocation parameters used by the product design operation to invoke the target interface, the invocation result of the target interface, and the interface identifier of the target interface in the operation record information of the product design operation. Thus, by providing more information, the accuracy of restoring the product design operation is improved, thereby improving the accuracy of troubleshooting.

[0096] Among them, the calling parameters, calling results and interface identifiers can refer to the above embodiments and will not be repeated here.

[0097] In this implementation, if the data involved in the call of the target interface includes the call parameters used by the product design operation to call the target interface, the call parameters can be obtained based on the data related to the call parameters in the operation record information of the product design operation, and the call parameters can be passed to the target interface to re-call the target interface; and / or, if the data involved in the call of the target interface includes the call result of the target interface, the call result can be obtained based on the data related to the call result in the operation record information of the product design operation, and the call result can be used to compare with the call result after the target interface is re-called to improve the accuracy of problem troubleshooting; and / or, if the data involved in the call of the target interface includes the interface identifier of the target interface, the interface identifier can be obtained based on the data related to the interface identifier in the operation record information of the product design operation, and the target interface to be re-called is determined according to the interface identifier, and the target interface is re-called to improve the accuracy of re-calling the target interface and the accuracy of restoring the product design operation, especially when the product design operation calls multiple target interfaces, the accuracy of restoring the product design operation is improved.

[0098] refer to Figure 5 , Figure 5 Schematic diagram of the process of processing design data provided in the embodiment of the present application Figure 4 .like Figure 5 As shown, the design data processing method includes:

[0099] S501, in response to the user's product design operation in the design data processing system, calls the target interface requested by the product design operation through the target proxy service, and the data involved in the call of the target interface include at least one of the following: the calling parameters used by the product design operation to call the target interface, the calling result of the target interface, and the interface identifier of the target interface.

[0100] S502, by serializing at least one of the call parameters, call results, and interface identifiers, the operation record information of the product design operation is obtained, and the operation record information includes at least one of the following: the serialization result of the call parameters, the serialization result of the call result, and the serialization result of the interface identifier.

[0101] The implementation principles and technical effects of S501 and S502 may refer to the aforementioned embodiments, such as S301 and S302, and will not be described in detail.

[0102] S503: Deserialize the operation record information to obtain a deserialization result.

[0103] The deserialization of the operation record information includes at least one of the following: deserialization of the serialization result of the call parameters, deserialization of the serialization result of the call result, and deserialization of the serialization result of the interface identifier. The deserialization result includes at least one of the following: the call parameters, the call result, and the interface identifier. The call parameters, call result, and interface identifier can be referred to the description of the previous embodiment and are not repeated here.

[0104] In this embodiment, when recording the product design operation, in order to facilitate the storage and / or transmission of data, at least one of the call parameters used by the product design operation to call the target interface, the call result of the target interface, and the interface identifier of the target interface is serialized. Therefore, when restoring the product design operation based on the operation record information of the product design operation, the operation record information can be deserialized first, that is, the operation record information is converted from a string type to its original type before serialization. Therefore, after deserialization, a deserialization result containing at least one of the data among the call parameters used by the product design operation to call the target interface, the call result of the target interface, and the interface identifier of the target interface can be obtained.

[0105] Specifically, in the operation record information of the product design operation, the deserialization operation may include: deserializing the serialization result of the call parameters used by the product design operation to call the target interface to obtain the call parameters; and / or, deserializing the serialization result of the call result of the target interface to obtain the call result; and / or, deserializing the serialization result of the interface identifier of the target interface to obtain the interface identifier.

[0106] In a possible implementation, the deserialization processing of the call parameter includes: if the data type of the call parameter is an entity type, then according to the serialization result of the call parameter, the call parameter is determined in multiple product entities according to the serialization result of the call parameter, wherein the serialization result of the call parameter is the index value corresponding to the call parameter; or, if the data type of the call parameter is an attribute type, then according to the serialization result of the call parameter, the call parameter is determined in the attribute values ​​of multiple product entities, wherein the serialization result of the call parameter is the attribute name corresponding to the call parameter and the index value of the product entity to which the call parameter belongs; or, if the data type of the call parameter is a numerical type, then the call parameter is determined to be the serialization result of the call parameter; or, if the data type of the call parameter is a mixed type, then the serialization result of the data in the call parameter is traversed and deserialized to obtain the call parameter. Thus, based on the data type of the call parameter, the call parameter is serialized and the serialization result of the call parameter is deserialized in a targeted and appropriate manner, thereby improving the accuracy of the serialization and deserialization of the call operation.

[0107] Among them, the entity type, attribute type, value type and mixed type can refer to the description of the above embodiment and will not be repeated here.

[0108] In this implementation, considering that the type of the call parameter used by the product design operation to call the data processing interface can be any of entity type, attribute type, numerical type, and mixed type, in order to improve the accuracy of serialization processing of the call parameter, different serialization processing methods can be used for different types of call parameters. Similarly, based on the serialization processing method of the call parameter, the corresponding deserialization processing method should be used to restore the call parameter. Among them, the serialization processing of the call parameter can refer to the above embodiment and will not be repeated here. The deserialization processing of the call parameter is as follows:

[0109] When the data type of the calling parameter is an entity type, since the serialization result of the calling parameter during the serialization process is the index value corresponding to the calling parameter, during the deserialization process, the calling parameter can be determined in multiple product entities (that is, in the product entity set) based on the serialization result of the calling parameter, that is, based on the index value corresponding to the calling parameter.

[0110] When the data type of the call parameter is an attribute type, since the serialization result of the call parameter during serialization processing is the attribute name of the call parameter and the index value of the product entity to which the call parameter belongs, the call parameter can be determined from the attribute values ​​of multiple product entities based on the serialization result of the call parameter during deserialization processing. Specifically, based on the index value of the product entity to which the call parameter belongs in the serialization result of the call parameter, the product entity to which the call parameter belongs is determined from the multiple product entities, and among the multiple attribute values ​​of the product entity to which the call parameter belongs, the attribute value corresponding to the attribute name of the call parameter is determined, and the call parameter is determined to be the attribute value.

[0111] When the data type of the calling parameter is a numeric type, since the serialization result of the calling parameter during serialization is the calling parameter itself (that is, the numeric type calling parameter is not serialized), the calling parameter can be determined as the serialization result of the calling parameter during deserialization.

[0112] When the data type of the call parameter is a mixed type, since the data contained in the call parameter is traversed one by one during the serialization process, and the traversed data is serialized to obtain the serialization result of the traversed data, the serialization result of the call parameter is obtained by combining the serialization results of all the data contained in the call parameter. Therefore, during the deserialization process, the serialization results of the data in the call parameter can be traversed one by one, and the traversed serialization results are deserialized to finally obtain the call parameter. Specifically, when the traversed serialization result is deserialized, it can be determined whether the original data type of the traversed serialization result is an entity type, an attribute type, a numerical type, or a mixed type. According to the original data type of the traversed serialization result, the deserialization processing method corresponding to the original data type is used to deserialize the traversed serialization result. Among them, the deserialization processing methods corresponding to the entity type, attribute type, numerical type, and mixed type can refer to the specific process of deserializing the serialization result of the call parameter when the data type of the call parameter is an entity type, an attribute type, a numerical type, or a mixed type.

[0113] In the process of deserializing the serialized result of the call result, the deserialization method of the serialized result of the call parameter can be referred to, and the serialized result of the call result can be deserialized to obtain the call result, which will not be described in detail here.

[0114] In the process of deserializing the serialization result of the interface identifier, if the data type of the interface identifier is a string type, the interface identifier can be determined as the deserialization result of the interface identifier; otherwise, the interface identifier can be determined as the identification information corresponding to the deserialization result of the interface identifier, wherein the serialization result of the interface identifier is the string corresponding to the interface identifier after mapping.

[0115] S504. Recall the target interface according to the deserialization result to restore the product design operation.

[0116] In this embodiment, the deserialization result includes the call parameters used by the product design operation to call the target interface, the call result of the target interface, and / or the interface identifier of the target interface. Based on the call parameters, the call result, and / or the interface identifier of the target interface, the target interface is re-called to restore the product design operation. The specific process of re-calling the data processing interface can be referred to the above embodiment and will not be repeated here.

[0117] In an embodiment of the present application, on a design data processing system, a proxy service is used to proxy and record the calls of product design operations to corresponding target interfaces, thereby obtaining operation record information of the product design operations. Based on the operation record information of the product design operations, the target interface calls are restored for use in troubleshooting, thereby improving the efficiency, reliability, and convenience of troubleshooting. Specifically, during the recording process, the data involved in the calls to the target interface are serialized to obtain operation record information. During the restoration process, the operation record information is deserialized to improve the data storage and / or transmission effect when recording and restoring the product design operations, thereby enabling more operation record information to be stored more accurately and reliably, thereby improving the reliability and accuracy of troubleshooting based on the operation record information.

[0118] Based on any of the foregoing embodiments, optionally, on the design data processing system, the underlying data processing interface is a Luban interface, and the proxy service that proxies the call to the data processing interface is a decorator added to the Luban interface. The decorator is executed at the start and end of the call of the Luban interface: at the start of the Luban interface call, the decorator corresponding to the Luban interface can call the Luban interface in response to the call request for the Luban interface, and record the start information (the start information may include at least one of the following: start time, interface identifier, call parameters); at the end of the Luban interface call, the decorator corresponding to the Luban interface can obtain the call result output by the Luban interface, feed the call result back to the upper-level product design operation or the upper-level product display (such as displaying the drawn product on the visual interface), and record the end information (the end information may include the end time and / or the call result). In this way, based on the start information and end information recorded by the decorator, the operation record information of the product design operation is obtained.

[0119] Based on any of the foregoing embodiments, optionally, after determining the operation record information of the product design operation, the operation record information of the product design operation is output; or, after determining the operation record information of the product design operation, if the product design process to which the product design operation belongs is completed, the operation record information of the product design operation is output; or, in response to a request to output the operation record information of the product design operation, the operation record information of the product design operation is output. Thus, the operation record information is provided to the user in a timely manner for viewing, thereby improving the user experience.

[0120] Among them, the product design process may include one or more product design operations, and any of the aforementioned embodiments can be used to record each product design operation in the product design process to obtain operation record information of each product design operation, and the operation record information of each product design operation constitutes the record information of the data processing process of the entire product design process.

[0121] Outputting the operation record information of the product design operation includes: displaying an operation record page on the design data processing system, and displaying the operation record information of the product design operation on the operation record page. Thus, through the page display method, the clarity of the operation record information is improved, the display effect of the operation record information is improved, and the efficiency of problem troubleshooting is improved.

[0122] refer to Figure 6 , Figure 6 This is an example diagram of an operation record page in the design data processing method provided in the embodiment of the present application. Figure 6 As shown, the operation record page includes an instruction display area. Since the product design operation may call one or more target interfaces, that is, trigger call instructions for one or more target interfaces, in order to improve the orderliness of the display of the operation record information of the product design operation, an instruction statistics table can be provided in the instruction display area. In the instruction statistics table, the call instructions of the product design operation on the target interface are sorted according to the call time sequence, so that the call instructions triggered by the product design operation on the operation record page are clear at a glance. Among them, the instruction statistics table can include one or more call instructions triggered by the product design operation.

[0123] Optional, such as Figure 6 As shown, in the instruction statistics table, for each instruction, the instruction sequence number, instruction identifier, instruction time and the number of instruction formula calculations can be displayed, so as to improve the information adequacy of the display of the call instruction, and further improve the information adequacy of the operation record information. Among them, the instruction sequence number can be obtained by sorting the call instructions of the target interface of the product design operation, the instruction identifier can include the interface identifier of the target interface corresponding to the call instruction and / or the call parameters of the target interface corresponding to the call instruction, the instruction time can be the time consumed for calling the target interface corresponding to the call instruction, and the number of instruction formula calculations can also be recorded in the process of calling the target interface in response to the call instruction, or can be obtained according to the preset formula calculation number corresponding to the target interface. In addition, in the instruction statistics table, the instruction execution result of each instruction can also be displayed ( Figure 6 The instruction execution result is the calling result of the target interface.

[0124] Optionally, the instruction display area can also display the call instructions of the product design operation to the target interface through statistical charts, thereby increasing the diversity of the display methods of the operation record information and improving the clarity of the display of the operation record information, thereby helping to improve the efficiency of problem troubleshooting. Figure 6As shown, in the instruction display area, three pie charts are used to respectively display: the proportion of the time consumed by each instruction in the total time consumed by product design operations, the proportion of the number of executions of each instruction in the total number of executions of all instructions, and the proportion of the number of formula calculations of each instruction in the total number of formula calculations of all instructions.

[0125] Optional, such as Figure 6 As shown, the operation log page also displays a basic information area, which can be used to display basic information related to the product design operation, such as the start time, end time, and identification information of the product design. This allows users to obtain more information while viewing the operation log information. When troubleshooting, users can know which product design the operation log information comes from, providing more information for troubleshooting.

[0126] As an example, refer to Figure 7a , Figure 7a This is a flow chart of recording product design operations in the design data processing method provided in the embodiment of the present application. Figure 7a As shown, when a designer begins designing, they perform product design operations on the design data processing system. The proxy service serializes the interface calls for these product design operations and then records the serialized results. If the design is not yet complete, the above process continues for the designer's next product design operation until the design is complete, resulting in operation record information for one or more product design operations.

[0127] Among them, Figure 7aAs shown, in the process of serializing the interface call process of the product design operation, first, in response to the start of the target interface call, the interface identifier of the target interface is serialized (i.e., serialization is performed); then, the start time of the target interface call is recorded. After that, the call parameters of the target interface are serialized. In the serialization of the call parameters, the data type of the call parameter is determined. If the data type of the call parameter is an entity type, it means that the call parameter is a product entity, and the serialization result of the call parameter is determined to be the index corresponding to the call parameter, wherein different product entities may correspond to different product indexes; if the data type of the call parameter is an attribute type, it means that the call parameter is an attribute value of the product entity, and the serialization result of the call parameter is determined to be the attribute name corresponding to the call parameter and the index of the product entity to which the call parameter belongs; if the entity type of the call parameter is a numerical type, the numerical type of the call parameter is determined to be the call parameter itself; if the entity type of the call parameter is a mixed type, the data in the call parameter is traversed and the traversed data are serialized one by one according to the same type judgment process. For details, please refer to the aforementioned embodiment and will not be repeated here. Afterwards, in response to the target interface calling being completed, the target interface calling end time is recorded, and it is determined whether to record the calling result of the target interface, and if so, the calling result is recorded. Finally, the operation record information is obtained.

[0128] As an example, refer to Figure 7b , Figure 7b This is a flow chart of restoring product design operations in the design data processing method provided in the embodiment of the present application. Figure 7b As shown, when the product design operation starts to be restored, an operation record information can be obtained from the operation record information of the product design operation, and the serialization result of the interface identifier in the operation record information is deserialized to obtain the interface identifier, and the serialization result of the call parameter in the operation information is deserialized to obtain the call parameter. Afterwards, the target interface is re-called according to the interface identifier and the call parameter, and the problem is troubleshooted according to the call result of the re-call of the target interface. For example, the problem is troubleshooted by comparing the call result of the re-call of the target interface with the call result of the target interface in the operation record information. After the problem is troubleshooted, the operation record information can be deleted. Determine whether there is still operation record information for the product design operation. If so, continue to obtain the next operation record information and repeat the above operation until there is no operation record information for the product design operation.

[0129] refer to Figure 8 , Figure 8This is a structural block diagram of a design data processing device 80 provided in an embodiment of the present application. The design data processing device 80 can be applied to a design data processing system, which provides one or more underlying data processing interfaces and a proxy service for proxying the calls to the data processing interfaces. Figure 8 As shown, the design data processing device 80 provided in the embodiment of the present application includes: a calling unit 81 and a recording unit 82, wherein:

[0130] The calling unit 81 is configured to call the target interface of the product design operation request through the target proxy service in response to the user's product design operation in the design data processing system, where the target interface is a data processing interface and the target proxy service is a proxy service corresponding to the target interface;

[0131] The recording unit 82 is used to record the call of the target interface and obtain the operation record information of the product design operation, wherein the operation record information is used for problem troubleshooting.

[0132] In one embodiment of the present application, the call of the target interface involves at least one of the following data: the calling parameters of the product design operation used to call the target interface, the calling result of the target interface, and the interface identifier of the target interface. The recording unit 82 is specifically used to obtain operation record information by serializing at least one of the calling parameters, calling results, and interface identifiers.

[0133] In one embodiment of the present application, in the serialization processing of the call parameter, the recording unit 82 is specifically used to: if the data type of the call parameter is an entity type, determine the serialization result of the call parameter as the index value of the call parameter; or, if the data type of the call parameter is an attribute type, determine the serialization result of the call parameter as the attribute name corresponding to the call parameter and the index value of the product entity to which the call parameter belongs; or, if the data type of the call parameter is a numerical type, determine the serialization result of the call parameter as the call parameter; or, if the data type of the call parameter is a mixed type, traverse and serialize the data in the call parameter to obtain the serialization result of the call parameter.

[0134] In one embodiment of the present application, the data involved in the call of the target interface includes time information of the call of the target interface, and the recording unit 82 is specifically used to obtain operation record information by recording the time information.

[0135] In one embodiment of the present application, the design data processing device 80 further includes: a restoration unit 83 for restoring the product design operation according to the operation record information, so as to perform problem troubleshooting by calling the restoration operation.

[0136] In one embodiment of the present application, the call of the target interface involves at least one of the following data: the call parameters of the product design operation used to call the target interface, the call result of the target interface, and the interface identifier of the target interface. The operation record information includes at least one of the following: the serialization result of the call parameters, the serialization result of the call result, and the serialization result of the interface identifier. The restoration unit 83 is specifically used to: deserialize the operation record information to obtain a deserialization result; and re-call the target interface based on the deserialization result; wherein the deserialization processing of the operation record information includes at least one of the following: deserialization processing of the serialization result of the call parameters, deserialization processing of the serialization result of the call result, and deserialization processing of the serialization result of the interface identifier. The deserialization result includes at least one of the following: call parameters, call result, and interface identifier.

[0137] In one embodiment of the present application, in the deserialization processing of the serialization result of the call parameter, the restoration unit 83 is specifically used to: if the data type of the call parameter is an entity type, then according to the serialization result of the call parameter, determine the call parameter in multiple product entities, wherein the serialization result of the call parameter is the index value of the call parameter; or, if the data type of the call parameter is an attribute type, then according to the serialization result of the call parameter, determine the call parameter in the attribute values ​​of multiple product entities, wherein the serialization result of the call parameter is the attribute name corresponding to the call parameter and the index value of the product entity to which the call parameter belongs; or, if the data type of the call parameter is a numerical type, determine the call parameter as the serialization result of the call parameter; or, if the data type of the call parameter is a mixed type, traverse and deserialize the serialization result of the data in the call parameter to obtain the call parameter.

[0138] The design data processing device provided in the embodiment of the present application is used to execute the technical solution in any of the above method embodiments. Its implementation principle and technical effects are similar and will not be repeated here.

[0139] In addition to the user's product design operations, the embodiments of the present application can also be applied to record other user operations and can also be applied to restore other user operations. In other words, the embodiments of the present application can be applied to a data processing system that provides an underlying data processing interface and a proxy service for proxying the call of the data processing interface. In the data processing system, the embodiments of the present application can record user operations and even restore user operations. The details are as follows:

[0140] refer to Figure 9 , Figure 9 A flow chart of the data processing method provided in the embodiment of the present application is shown as follows: Figure 9 As shown, the data processing method includes:

[0141] S901, in response to a user operation of a data processing system, calling a target interface requested by the user operation through a target proxy service, where the target interface belongs to a data processing interface and the target proxy service is a proxy service corresponding to the target interface.

[0142] S902, recording the call of the target interface to obtain operation record information of the user operation, wherein the operation record information is used for problem troubleshooting.

[0143] The user operation can be the product design operation of the aforementioned embodiment. In this case, the implementation principles and technical effects of S901 and S902 can refer to the aforementioned embodiment. The user operation can also be other operations besides product design operations, such as user document editing operations, interactive operations with music playback pages, web browsing operations, etc. On the data processing system, the user operation still requires calling the underlying data processing interface. In this case, the implementation principles and technical effects of S901 and S902 can also refer to the aforementioned embodiment. Therefore, the implementation principles and technical effects of S901 and S902 will not be elaborated here.

[0144] In the embodiments of the present application, a proxy service is used on a data processing system to proxy and record user operations that call corresponding data processing interfaces, thereby recording user operations and obtaining operation log information of user operations, thereby improving the accuracy and reliability of the operation log information. Therefore, based on accurate and reliable operation log information that can reflect the process of user operations calling data processing interfaces, the efficiency and reliability of problem troubleshooting can be effectively improved.

[0145] Figure 10 100, the electronic device 100 of the embodiment of the present application may include: at least one processor 101 ( Figure 10 Only one processor is shown); and a memory 102 in communication with the at least one processor. Memory 102 stores instructions executable by at least one processor 101, and the instructions are executed by at least one processor 101 to enable electronic device 100 to implement the technical solution of any of the aforementioned method embodiments.

[0146] Optionally, the memory 102 may be independent or integrated with the processor 101 .

[0147] When the memory 102 is a device independent of the processor 101 , the electronic device 100 further includes a bus 103 for connecting the memory 102 and the processor 101 .

[0148] Optionally, the electronic device 100 is a mobile terminal.

[0149] The electronic device provided in the embodiments of the present application can execute the technical solution of any of the aforementioned method embodiments, and its implementation principles and technical effects are similar, which will not be repeated here.

[0150] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, it is used to implement the technical solution in any of the aforementioned method embodiments.

[0151] An embodiment of the present application provides a computer program product, including a computer program, which implements the technical solution of any of the aforementioned method embodiments when executed by a processor.

[0152] An embodiment of the present application further provides a chip, including: a processing module and a communication interface, wherein the processing module can execute the technical solution in the aforementioned method embodiment.

[0153] Furthermore, the chip also includes a storage module (such as a memory), the storage module is used to store instructions, the processing module is used to execute the instructions stored in the storage module, and the execution of the instructions stored in the storage module enables the processing module to execute the technical solution in the aforementioned method embodiment.

[0154] It should be understood that the processor described above may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), or application-specific integrated circuits (ASICs). A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the present invention may be directly executed by a hardware processor or by a combination of hardware and software modules within the processor.

[0155] The memory may include a high-speed RAM memory, and may also include non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk.

[0156] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be classified into address buses, data buses, and control buses. For ease of illustration, the buses in the drawings of this application are not limited to just one bus or just one type of bus.

[0157] The storage medium may be implemented by any type of volatile or non-volatile memory device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0158] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an application-specific integrated circuit (ASIC). Of course, the processor and storage medium can also exist as discrete components in an electronic device.

[0159] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for processing design data, characterized in that: Applied to a design data processing system, the design data processing system provides an underlying data processing interface and a proxy service for proxying the call of the data processing interface. The design data processing method includes: In response to a product design operation of the user in the design data processing system, calling a target interface called by the product design operation request through a target proxy service, the target interface belonging to the data processing interface, and the target proxy service being a proxy service corresponding to the target interface; Recording the calling process of the target interface by the product design operation through the target proxy service to obtain operation record information of the product design operation, wherein the operation record information is used for problem troubleshooting; Restoring the product design operation according to the operation record information to troubleshoot the problem by restoring the operation; The calling of the target interface involves at least one of the following data: a calling parameter used by the product design operation to call the target interface, a calling result of the target interface, and an interface identifier of the target interface. The recording of the calling of the target interface to obtain the operation record information of the product design operation includes: The operation record information is obtained by serializing at least one of the call parameters, the call result, and the interface identifier.

2. The method for processing design data according to claim 1, wherein: The serialization processing of the call parameters includes: If the data type of the calling parameter is an entity type, determining that the serialization result of the calling parameter is the index value of the calling parameter; Alternatively, if the data type of the call parameter is an attribute type, determining that the serialization result of the call parameter is the attribute name corresponding to the call parameter and the index value of the product entity to which the call parameter belongs; Alternatively, if the data type of the calling parameter is a numerical type, determining the serialization result of the calling parameter to be the calling parameter; Alternatively, if the data type of the calling parameter is a mixed type, the data in the calling parameter is traversed and serialized to obtain a serialization result of the calling parameter.

3. The method for processing design data according to claim 1 or 2, characterized in that: The data involved in the call of the target interface also includes time information of the call of the target interface. The recording of the call of the target interface to obtain the operation record information of the product design operation also includes: The operation record information is obtained by recording the time information.

4. The method for processing design data according to claim 1, wherein: The calling of the target interface involves at least one of the following data: the calling parameters used by the product design operation to call the target interface, the calling result of the target interface, and the interface identifier of the target interface; the operation record information includes at least one of the following: the serialization result of the calling parameters, the serialization result of the calling result, and the serialization result of the interface identifier; and restoring the product design operation based on the operation record information includes: Deserialize the operation record information to obtain a deserialization result; Recall the target interface according to the deserialization result; Among them, the deserialization processing of the operation record information includes at least one of the following: deserialization processing of the serialization result of the call parameter, deserialization processing of the serialization result of the call result, and deserialization processing of the serialization result of the interface identifier, and the deserialization result includes at least one of the following: the call parameter, the call result, and the interface identifier.

5. The method for processing design data according to claim 4, wherein: The deserialization processing of the serialization result of the calling parameter includes: If the data type of the calling parameter is an entity type, determining the calling parameter in a plurality of product entities according to a serialization result of the calling parameter, wherein the serialization result of the calling parameter is an index value of the calling parameter; Alternatively, if the data type of the call parameter is an attribute type, the call parameter is determined from the attribute values ​​of multiple product entities according to the serialization result of the call parameter, wherein the serialization result of the call parameter is the attribute name corresponding to the call parameter and the index value of the product entity to which the call parameter belongs; Alternatively, if the data type of the calling parameter is a numerical type, determining that the calling parameter is a serialization result of the calling parameter; Alternatively, if the data type of the calling parameter is a mixed type, the serialization result of the data in the calling parameter is traversed and deserialized to obtain the calling parameter.

6. A design data processing device, characterized in that: Applied to a design data processing system, the design data processing system provides one or more underlying data processing interfaces and a proxy service for proxying the calls to the data processing interfaces, and the design data processing device includes: A calling unit, configured to call a target interface of the product design operation request through a target proxy service in response to a product design operation by a user in the design data processing system, wherein the target interface belongs to the data processing interface and the target proxy service is a proxy service corresponding to the target interface; a recording unit, configured to record, through the target proxy service, the process of calling the target interface by the product design operation, and obtain operation record information of the product design operation, wherein the operation record information is used for troubleshooting; A restoration unit, configured to restore the product design operation according to the operation record information, so as to troubleshoot the problem by restoring the operation; The calling of the target interface involves at least one of the following data: the calling parameters of the product design operation used to call the target interface, the calling result of the target interface, and the interface identifier of the target interface. The recording unit is specifically used to obtain the operation record information by serializing at least one of the calling parameters, the calling result, and the interface identifier.

7. A data processing method, characterized in that: Applied to a data processing system, the data processing system provides an underlying data processing interface and a proxy service for proxying calls to the data processing interface, the data processing method includes: In response to a user's product design operation on the data processing system, calling a target interface called by the user operation request through a target proxy service, the target interface belonging to the data processing interface, and the target proxy service being a proxy service corresponding to the target interface; Recording the calling process of the target interface by the product design operation through the target proxy service to obtain operation record information of the user operation, wherein the operation record information is used for problem troubleshooting; Restoring the product design operation according to the operation record information to troubleshoot the problem by restoring the operation; The calling of the target interface involves at least one of the following data: a calling parameter used by the product design operation to call the target interface, a calling result of the target interface, and an interface identifier of the target interface. The recording of the calling process of the product design operation on the target interface to obtain the operation record information of the user operation includes: The operation record information is obtained by serializing at least one of the call parameters, the call result, and the interface identifier.

8. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the electronic device to execute the design data processing method described in any one of claims 1 to 5, and / or to enable the electronic device to execute the data processing method described in claim 7.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for processing design data according to any one of claims 1 to 5 is implemented, and / or when the computer program is executed by a processor, the method for processing data according to claim 7 is implemented.

Images