Object management method, apparatus, device, storage medium, and program product

Abstract

This disclosure provides an object management method, apparatus, device, storage medium, and program product, relating to the application of artificial intelligence technology in the vehicle field. The method includes: determining user needs; identifying target objects matching the user needs from an object knowledge base and displaying visual elements of the target objects; wherein the object knowledge base is configured as a database containing relationships between various objects; in response to a modification operation on the visual elements of the target object, identifying other objects associated with the target object based on the object knowledge base; and sending change notifications for the target object to the associated users of the other objects. This method allows users to express their search needs for development objects based on their requirements and displays target objects with visual elements, enabling users to intuitively understand and modify target objects, and promptly sending change notifications for target objects to other relevant users, avoiding development conflicts due to information opacity and reducing business operation risks.

Description

Technical Field

[0001] This disclosure relates to the application of artificial intelligence technology in the vehicle field, and more particularly to an object management method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the development of computer technology, business systems across industries are becoming increasingly complex, and the number of research and development objects is growing explosively. Optimizing object management processes is necessary to improve development efficiency and ensure the efficient development and stable operation of business systems during the development of business functions.

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The purpose of this disclosure is to provide an object management method, apparatus, device, storage medium, and program product.

[0005] According to a first aspect of the present disclosure, an object management method is provided, comprising: determining user needs; determining a target object matching the user needs from an object knowledge base, and displaying visual elements of the target object; wherein the object knowledge base is configured as a database containing relationships between various objects; in response to a modification operation on the visual elements of the target object, determining other objects associated with the target object according to the object knowledge base; and sending a change notification of the target object to the associated users of the other objects.

[0006] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects: This disclosure allows users to express their search needs for research and development objects based on their requirements, and can display target objects with visual elements, enabling users to intuitively understand and modify target objects. It also allows users to promptly send change notifications to other relevant users, ensuring that other users are aware of the target object modifications in a timely manner. This avoids research and development conflicts caused by a lack of transparency, helps avoid problems such as code incompatibility and functional conflicts in multi-person collaborative development projects, allows other relevant users to adjust their work in a timely manner, reduces business operation risks, and ensures the smooth progress of the project.

[0007] In some implementations, determining user needs includes: receiving a user's natural language requirement statement; wherein, determining a target object matching the user's requirement from an object knowledge base includes: extracting object features from the natural language requirement statement; wherein the object features include the object's structural and / or functional features; determining the semantic similarity between the object features and objects in the object knowledge base; and determining the target object based on similar objects whose semantic similarity exceeds a preset threshold.

[0008] In the above implementation, key entities in the natural language requirement statement can be extracted, focusing on the core content of the user's needs and avoiding interference from irrelevant information; and by calculating the semantic similarity between key entities and object descriptions, the limitations of surface text can be overcome, the semantic connotation can be deeply understood, and the target object matching the natural language requirement statement can be found more accurately.

[0009] In some implementations, determining the target object based on similar objects whose semantic similarity exceeds a preset threshold includes: displaying candidate visual elements based on similar objects whose semantic similarity exceeds the threshold; determining the target object based on a user's selection operation on the candidate visual elements; wherein the candidate visual elements are determined by at least one of the following: determining a first visual element corresponding to the similar object as the candidate visual element; determining associated objects in the object knowledge base that have an association relationship with the similar object in response to a user's association display operation or according to a preset display hierarchy; and determining a second visual element corresponding to the associated object as the candidate visual element.

[0010] In the above implementation, multiple candidate visual elements can be displayed based on similar objects, allowing users to make their own selections based on their actual needs. This ensures that the final selected target object better matches their actual needs, improving the accuracy and effectiveness of object management. It avoids biases caused by the system unilaterally determining the target object, providing users with a more participatory and autonomous object selection interaction method. Furthermore, it provides multiple ways to determine candidate visual elements, enabling users to understand objects related to their needs from multiple perspectives, avoiding limitations in selection due to insufficient information, and helping to make more appropriate decisions.

[0011] In some implementations, sending a change notification of the target object to the associated users of the other objects includes: determining the permission type of the associated users of the other objects; and sending a differentiated change notification of the target object to the associated users based on the permission type.

[0012] In the above implementation, the scope of information dissemination can be controlled by dividing permissions by type. It can also ensure that the information received by each associated user is relevant and necessary to their work, avoiding sending a large amount of irrelevant information to all users, reducing information interference, and enabling users to quickly focus on changes related to their permissions and responsibilities, thereby improving the accuracy and effectiveness of information transmission.

[0013] In some implementations, the permission type includes at least development permission and management permission; wherein, sending differentiated change notifications of the target object to the associated users according to the permission type includes: the object change notification sent to the associated users with development permission includes at least the parameter change details corresponding to the modification operation and the scheduling impact corresponding to the modification operation; the object change notification sent to the associated users with management permission includes at least the scheduling impact corresponding to the modification operation.

[0014] The above implementation provides a specific method for differentiated notifications based on different permission types. Developers can obtain detailed parameter change information for precise development and debugging; administrators can obtain scheduling impact information to make appropriate management decisions. This precise information delivery avoids information overload and interference from irrelevant information, improving the efficiency of users in handling changes.

[0015] In some embodiments, the method further includes: performing configuration operations on the visualization elements; the configuration operations include at least one of the following: dragging the visualization elements; configuring association relationships for multiple visualization elements by drawing lines; configuring association relationships for multiple visualization elements by selecting a type; configuring attribute parameters for a target object without configured parameters through the attribute panel of the visualization elements.

[0016] In the above implementation, users can configure target objects using visual operations such as dragging, drawing lines, and selecting types. This provides users with a way to configure visual element relationships without writing complex code or commands, simply through graphical interaction. Each object can also be equipped with an attribute panel, providing users with fine-grained configuration capabilities for target object attribute parameters. The multiple configuration operation methods and rich relationship types make this solution applicable to different domains and object management scenarios, improving overall development efficiency.

[0017] In some embodiments, the method further includes: constructing a model component in response to a configuration operation on the visualization element; this includes: performing consistency verification and / or integrity verification on the configured model component in response to a configuration operation on the visualization element; and constructing the model component in response to the verification passing; wherein the consistency verification includes at least one of the following: data format matching verification, interface parameter matching verification, and physical connection verification; and the integrity verification includes at least one of the following: required field checking, relationship integrity verification, and function coverage verification.

[0018] In the above implementation, users can intuitively understand and operate the target object, and conveniently, quickly and flexibly build model components to adapt to diverse business scenarios and different users' requirements for object management, thereby improving overall development efficiency. Furthermore, through comprehensive consistency and integrity verification, the model components can be verified in a timely manner before formally building them to ensure that the final model components meet the design specifications, reduce system failures and errors caused by component defects, and improve the stability and reliability of the system.

[0019] In some implementations, the object management method further includes: updating the object associations in the object knowledge base according to the associations in response to the configuration operation containing configuration associations.

[0020] In the above implementation, the object knowledge base can be updated in a timely manner based on the relationships in the configuration operations, ensuring that the object relationships in the knowledge base remain synchronized with the actual configuration and always reflect the latest state of relationships between objects. This avoids errors in object matching and retrieval caused by the knowledge base lagging behind actual applications, providing reliable data support for the system's object management based on the knowledge base, and ensuring the accuracy and effectiveness of object management.

[0021] According to a second aspect of the present disclosure, an object management apparatus is provided, comprising: a requirement determination unit for determining user requirements; an object determination unit for determining a target object matching the user requirements from an object knowledge base and displaying visual elements of the target object; wherein the object knowledge base is configured as a database containing relationships between various objects; a modification determination unit for determining other objects associated with the target object based on the object knowledge base in response to a modification operation on the visual elements of the target object; and a notification unit for sending a change notification of the target object to users associated with the other objects.

[0022] In some implementations, the requirement determination unit determines user requirements by: receiving a user's natural language requirement statement; wherein, the object determination unit determines a target object matching the user's requirement from an object knowledge base by: extracting object features from the natural language requirement statement; wherein the object features include the object's structure and / or functional features; determining the semantic similarity between the object features and objects in the object knowledge base; and determining the target object based on similar objects whose semantic similarity exceeds a preset threshold.

[0023] In some implementations, the object determination unit determines the target object based on similar objects whose semantic similarity exceeds a preset threshold, including: displaying candidate visual elements based on similar objects whose semantic similarity exceeds the threshold; determining the target object based on the user's selection operation on the candidate visual elements; wherein the candidate visual elements are determined by at least one of the following: determining a first visual element corresponding to the similar object as the candidate visual element; determining associated objects in the object knowledge base that have an association relationship with the similar object in response to the user's association display operation or according to a preset display hierarchy; and determining a second visual element corresponding to the associated object as the candidate visual element.

[0024] In some implementations, the notification unit sends a change notification of the target object to the associated users of the other object, including: determining the permission type of the associated users of the other object; and sending a differentiated change notification of the target object to the associated users according to the permission type.

[0025] In some implementations, the permission type includes at least development permission and management permission; wherein, the notification unit sends differentiated change notifications of the target object to the associated users according to the permission type, including: the object change notification sent to the associated users with development permission includes at least the parameter change details corresponding to the modification operation and the scheduling impact corresponding to the modification operation; the object change notification sent to the associated users with management permission includes at least the scheduling impact corresponding to the modification operation.

[0026] In some embodiments, the object management device further includes a configuration unit for: performing configuration operations on the visual elements; the configuration operations include at least one of the following: dragging the visual elements; configuring association relationships for multiple visual elements by drawing lines; configuring association relationships for multiple visual elements by selecting a type; and configuring attribute parameters for target objects without configured parameters through the attribute panel of the visual elements.

[0027] In some implementations, the configuration unit is further configured to: construct a model component in response to a configuration operation on the visualization element; this includes: performing consistency verification and / or integrity verification on the configured model component in response to a configuration operation on the visualization element; and constructing the model component in response to the verification passing; wherein the consistency verification includes at least one of the following: data format matching verification, interface parameter matching verification, and physical connection verification; and the integrity verification includes at least one of the following: required field checking, relationship integrity verification, and function coverage verification.

[0028] In some embodiments, the object management device further includes an update unit for: updating the object associations in the object knowledge base according to the associations in response to the configuration operation containing configuration associations.

[0029] According to a third aspect of the present disclosure, an electronic device is provided, characterized in that it includes: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to implement the object management method described above.

[0030] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, wherein when instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is enabled to execute an object management method, the method comprising: receiving a natural language requirement statement; determining a target object matching the natural language requirement statement from an object knowledge base and displaying visual elements of the target object; and constructing a model component in response to a configuration operation on the visual elements.

[0031] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the object management method described above.

[0032] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0033] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0034] Figure 1 This is a flowchart illustrating an object management method according to some embodiments of the present disclosure.

[0035] Figure 2 This is a flowchart illustrating the determination of a target object in an object management method according to some embodiments of the present disclosure.

[0036] Figure 3 This is a flowchart illustrating the determination of a target object in another object management method according to some embodiments of the present disclosure.

[0037] Figure 4 This is a flowchart illustrating yet another object management method according to some embodiments of the present disclosure.

[0038] Figure 5 This is a block diagram illustrating an object management device according to some embodiments of the present disclosure.

[0039] Figure 6 This is a block diagram illustrating an apparatus for object management according to some embodiments of the present disclosure. Detailed Implementation

[0040] Exemplary embodiments of this disclosure will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings denote the same or similar elements unless otherwise indicated. Various changes, modifications, and equivalents of the methods, apparatus, and / or systems described herein will become apparent upon understanding this disclosure. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but can be changed as will become apparent upon understanding this disclosure, except for operations that must be performed in a particular order. Furthermore, for clarity and brevity, descriptions of features known in the art may be omitted.

[0041] The flowchart shown in the attached diagram is merely an illustrative example and does not necessarily include all content and steps, nor does it necessarily have to be executed in the described order or in the order of the step numbers. For example, some steps can be broken down, while others can be combined or partially combined, and multiple steps can have their order interchanged or be executed simultaneously. Therefore, the actual execution order may change depending on the actual situation.

[0042] The embodiments described below, which are examples of some of the embodiments of this disclosure, do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0043] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0044] Figure 1 This is a flowchart illustrating an object management method according to some embodiments of the present disclosure, such as... Figure 1As shown, the object management method can be applied to electronic devices, including but not limited to smartphones, tablets, wearable devices, desktop computers, laptops, smart speakers, and other terminal devices. It can also include server-side components such as local servers and cloud servers, which can be deployed on a single computer or a cluster of multiple computers. The object management method may include the following steps.

[0045] In step S110, user requirements are determined.

[0046] In this embodiment of the disclosure, user requirements can be requirements for objects. These objects can be development objects that may be used during the development process, such as signal objects or functional objects. Requirements for objects may include, for example, viewing object information, modifying object information, or using objects for modeling. Here, "user" refers to a person who can use the object management system / platform.

[0047] For example, a user can enter "view vehicle door lock remote control function" to express their desire to locate and view the relevant R&D objects for this function.

[0048] This step allows users to input their needs for an object using natural language, without needing to use a specific programming language or complex operating instructions. This lowers the barrier to entry and makes it easy for non-technical personnel to express their needs.

[0049] In step S120, a target object matching the user's needs is determined from the object knowledge base, and the visual elements of the target object are displayed; wherein, the object knowledge base is configured as a database containing the relationships between various objects.

[0050] In this embodiment of the disclosure, the object knowledge base can be a database that stores information related to multiple objects, including object names or descriptions, object attributes, hierarchical relationships between objects, dependencies between objects, and the functional scenarios in which the objects are applied. The object knowledge base can serve as the basis for matching target objects, providing rich object resources.

[0051] User requirements can include the target object or descriptive information describing the target object. Based on the user requirements, a search and matching process can be performed in an object knowledge base to find the target object that meets the user's needs. The target object can then be presented to the user intuitively using visual elements, facilitating quick understanding and identification. Visual elements can take the form of graphics, icons, cards, etc., representing the object. Different types of objects can have different styles of visual elements; for example, after finding a signal object, it can be displayed to the user as a signal-style visual element.

[0052] Step S130: In response to the modification operation of the visualization elements of the target object, other objects associated with the target object are determined according to the object knowledge base.

[0053] In this embodiment of the disclosure, when a user initiates a modification operation on a visual element, subsequent processing can be triggered. This step demonstrates real-time response capabilities, enabling timely capture of the user's operational intent and providing a starting point for a series of subsequent processes based on the modification operation. The modification of the visual element can be achieved by modifying the attribute parameters of the target object through the attribute panel corresponding to the visual element, or by modifying the association relationship between the target object and other objects.

[0054] After modifying the target object, objects in the object knowledge base that have hierarchical and dependency relationships with the target object can be identified as other objects associated with the target object.

[0055] In an exemplary embodiment, a distributed lock mechanism can be used to control concurrent modification operations on the same target object, ensuring that only one user can modify an object at a time, thus avoiding data conflicts.

[0056] In an exemplary embodiment, a modification record can also be generated in response to a modification operation on a visual element. The modification record may include at least: a modification timestamp, changed content, and a user identifier that performed the modification operation. Version control can also be implemented based on the modification record, for example, generating a version identifier for each modification record and storing a snapshot of the object knowledge base after the modification, so that users can quickly revert to previous versions based on the version identifier.

[0057] For example, when the interface parameters of an SOA service are modified, the modification time can be recorded as "year, month, day, and time", the modifier as "A", the parameters before modification as "input parameter A: integer type, output parameter B: string type", and the parameters after modification as "input parameter A: floating-point type, output parameter B: array type", etc. This allows developers to trace and compare the changes when needed later, understand the evolution of the design, and reduce the risk of conflicts caused by inconsistent information during the development process.

[0058] Step S140: Send a change notification of the target object to the associated users of the other objects.

[0059] In this embodiment of the disclosure, after identifying other objects associated with the target object, the associated user information of these other objects can be obtained, and object change notifications can be sent to these users. This step ensures that relevant users can be informed of changes to objects in the system in a timely manner, so that they can make corresponding adjustments and processes based on the changes.

[0060] As can be seen from the above steps, the object management method provided in this disclosure allows users to express their search needs for development objects based on their own requirements. Target objects can be displayed using visual elements, enabling users to intuitively understand and modify them. Furthermore, it allows for timely notification of changes to target objects to other relevant users, ensuring they are aware of the modifications and preventing development conflicts due to information asymmetry. This helps avoid code incompatibility and functional conflicts in collaborative development projects, allowing other relevant users to adjust their work accordingly, reducing business operation risks, and ensuring the smooth progress of the project.

[0061] In some embodiments of this disclosure, determining user needs includes: receiving a user's natural language request statement.

[0062] In this embodiment of the disclosure, the natural language requirement statement can be an input method in which the user describes their requirements using natural language. The user can describe their needs for the object by inputting the natural language requirement statement through voice or text. This step allows users to express their search needs for research and development objects in a natural language manner, lowering the user threshold and enabling users with different technical backgrounds to easily interact with the system.

[0063] Figure 2 This is a flowchart illustrating the determination of a target object in an object management method according to some embodiments of the present disclosure.

[0064] In some embodiments of this disclosure, determining a target object that matches the user's needs from an object knowledge base may include the following steps.

[0065] Step S210: Extract object features from the natural language requirement statement; wherein the object features include the object's structure and / or functional features.

[0066] In this embodiment of the disclosure, the object-related information in the natural language requirement statement can be object features. Object features can be descriptions of the object's structure or function, such as key entities used to describe structural characteristics or structural types, or key entities used to describe functional characteristics or functional types. Key entities can be core words in the natural language requirement statement, such as nouns, verbs, noun phrases, verb phrases, etc. These words or phrases can help the system understand the user's core needs and are used in subsequent steps to perform semantic matching with objects to find target objects that meet the user's needs.

[0067] In an exemplary embodiment, natural language processing techniques (such as word segmentation, part-of-speech tagging, and named entity recognition) can be used to extract key entities. For example, for the statement "to realize the remote control function of vehicle door locks", word segmentation technology can be used to split the sentence into words such as "realize", "vehicle door locks", "remote control", and "function". Part-of-speech tagging can be used to determine the part of speech of each word, such as "vehicle door locks" being a noun, "remote control" being a verb phrase, "realize" being a general verb, and "function" being an abstract noun. Predefined stop words can be used to filter "realize" and "function" to reduce redundant information, and named entity recognition technology can be used to identify "vehicle door locks" and "remote control" as key entities.

[0068] In an exemplary embodiment, the split key entities can also be combined to generate more key entities. For example, "vehicle door lock" and "remote control" can be combined to obtain a new key entity "vehicle door lock remote control".

[0069] Part-of-speech tagging (e.g., nouns, verbs, adjectives) helps identify the grammatical structure of sentences and distinguish between subjects, predicates, and objects. For example, in the sentence "to realize remote control of vehicle door locks," part-of-speech tagging clarifies that "vehicle door locks" is a noun phrase (subject) and "remote control" is a verb phrase (predicate), thus helping to understand the core logic of the sentence. Furthermore, part-of-speech tagging aids in semantic disambiguation, clarifying the part of speech and meaning of the same word in different contexts. For instance, "run" can be both a verb (to operate) and a noun (trip); part-of-speech tagging avoids ambiguity and ensures accurate extraction of key entities.

[0070] Step S220: Determine the semantic similarity between the object features and the objects in the object knowledge base.

[0071] In this embodiment, a semantic matching algorithm can be used to compare the extracted key entities with the relevant descriptive information of each object in the object knowledge base, and calculate the semantic similarity between them. The relevant descriptive information of the objects may include, for example, the object's name, type, attributes, functions, application scenarios, etc. Semantic similarity reflects the degree of matching between user needs and objects in the knowledge base; the higher the value, the stronger the semantic connection between the two.

[0072] In an exemplary embodiment, the semantic matching algorithm can be a cosine similarity algorithm to calculate the similarity between the extracted key entities and the relevant descriptive information of the objects. Specifically, the relevant descriptive information of the key entities and objects can be converted into vector form using a word vector model, and then the similarity between the two can be calculated using the cosine similarity formula.

[0073] Step S230: Determine the target object based on similar objects whose semantic similarity exceeds a preset threshold.

[0074] In this embodiment, the preset threshold can be a value determined based on actual needs or historical statistical data, such as 0.8 or 0.7, serving as a dividing line for determining whether an object meets user needs. Objects with semantic similarity exceeding this threshold can be included in the selection scope of target objects, ensuring that the selected objects have a high degree of fit with user needs.

[0075] For example, for the input "vehicle door lock remote control function", the cosine similarity between "vehicle door lock", "remote control", "vehicle door lock remote control" and the descriptions of each object in the knowledge base can be calculated separately. Assuming that the semantic similarity between "vehicle door lock signal object" and the key entity "vehicle door lock", the semantic similarity between "remote control service component object" and the key entity "remote control", and the semantic similarity between "door lock control unit object" and the key entity "vehicle door lock remote control" exceed the threshold, then "vehicle door lock signal object", "remote control service component object" and "door lock control unit object" can be identified as similar objects, and then the target object can be determined based on the similar objects.

[0076] Through the embodiments of this disclosure, key entities in natural language requirement statements can be extracted, focusing on the core content of user needs and avoiding interference from irrelevant information; and by calculating the semantic similarity between key entities and object descriptions, the limitations of surface text can be overcome, and the semantic connotation can be deeply understood, thereby finding the target object that matches the natural language requirement statement more accurately.

[0077] Figure 3 This is a flowchart illustrating the determination of a target object in another object management method according to some embodiments of the present disclosure.

[0078] In this embodiment of the disclosure, Figure 3 The method flow shown includes any one or any combination of steps S310, S320, S330, and S340, wherein steps S310 and S320 are respectively related to... Figure 2 Steps S210 and S220 in the method flow shown correspond to each other and will not be repeated here.

[0079] In some embodiments of this disclosure, in Figure 2 Based on the method for determining the target object in the object management method shown, Figure 3 The method flow shown may also include the following steps.

[0080] Step S330: Display candidate visual elements based on similar objects whose semantic similarity exceeds a threshold.

[0081] In this embodiment of the disclosure, after filtering out similar objects that meet the threshold through semantic similarity calculation, candidate visual elements for display can be determined based on these similar objects to intuitively present target object candidates that may meet the user's needs. For example, when a user's request statement matches multiple signal objects, the visual elements of the signal styles corresponding to each of these signal objects can be displayed to the user as candidate visual elements.

[0082] In an exemplary embodiment, the displayed visual elements may include the object's name, attribute information, or function.

[0083] Step S340: Determine the target object based on the user's selection operation of the candidate visual elements.

[0084] In this embodiment of the disclosure, the user can browse the displayed candidate visual elements and select the candidate visual elements that meet the requirements according to the actual viewing or development needs (such as simple and intuitive operations such as clicking, dragging, and checking). The system can determine the object corresponding to the candidate visual element selected by the user as the final target object, thus completing the process of accurately determining the target object required by the user from multiple candidate objects.

[0085] Through the embodiments of this disclosure, multiple candidate visual elements can be displayed based on similar objects, allowing users to make their own choices based on their actual needs. This ensures that the final selected target object is more in line with their real needs, improves the accuracy and effectiveness of object management, and avoids the deviation caused by the system unilaterally determining the target object. It provides users with a more participatory and autonomous interactive way of determining objects.

[0086] In some embodiments of this disclosure, the candidate visualization element is determined by at least one of the following: determining a first visualization element corresponding to the similar object as the candidate visualization element; determining an associated object in the object knowledge base that has an association relationship with the similar object in response to a user's association display operation or according to a preset display level; and determining a second visualization element corresponding to the associated object as the candidate visualization element.

[0087] In this embodiment of the disclosure, after filtering out similar objects whose semantic similarity exceeds the threshold, the original visual elements (i.e., the first visual elements) corresponding to these similar objects can be directly displayed to the user as candidate visual elements to quickly present object information that directly matches the user's needs, allowing the user to intuitively understand the preliminary matching and filtering results.

[0088] In this embodiment, when browsing visual elements of similar objects, users can actively trigger association display operations, such as right-clicking or long-pressing a specific button (e.g., the "View Related Objects" button), to trigger the system to display related objects of the similar objects. Other objects associated with similar objects can be determined based on the relationships between objects in the object knowledge base. By supporting users to actively initiate association display operations, users are given the right to independently explore object association information. Users can selectively obtain related object information according to their needs and questions, increasing user initiative and participation in the object selection process and making the interaction more personalized.

[0089] For example, if a user performs a contextualization operation on a signal object, it can display second visual elements of other objects (i.e., related objects) that have a one-level relationship with that signal object. The user can also perform contextualization operations on the second visual elements to further display the second visual elements of the related objects of other objects. These second visual elements can all be selected by the user as candidate visual elements.

[0090] In exemplary embodiments, the relationships between objects can include, for example, hierarchical relationships, dependency relationships, and similar extension relationships. Hierarchical relationships can refer to objects being organized and arranged according to a certain hierarchical structure, presenting a superior-subordinate or inclusive relationship. For example, a "vehicle braking control system" can contain various signal objects, service component objects, or control unit objects; therefore, the "vehicle braking control system" and signal objects have a hierarchical relationship. Dependency relationships indicate that the normal operation or functional realization of one object depends on the existence, operation, or data of another object. For example, an "air conditioning control unit object" needs to rely on a "temperature sensor signal object" for regulation; therefore, the "air conditioning control unit object" and the "temperature sensor signal object" have a dependency relationship. Similar extension relationships can refer to a relationship between objects in an object knowledge base that have the same or similar types and functions. These objects are similar in basic attributes and functions, but differ in certain specific parameters, performance indicators, or application scenarios. Establishing similar extension relationships allows users to easily compare, select, and expand applications within the same type of object. For example, sensor signals of the same type with different transmission frequencies can have similar extension relationships.

[0091] In an exemplary embodiment, in the interface that displays similar objects and their corresponding associated objects, symbols and / or lines can also be used to indicate that there is an association between objects, and different styles of symbols and / or lines can be used to represent different relationships between objects. For example, curly braces and arrows can be used together to represent hierarchical relationships, arrows can be used to represent dependency relationships, dashed lines can represent similar extension relationships, and lines with text labels can represent hierarchical relationships, etc.

[0092] In this embodiment, display hierarchy rules can be pre-defined, and when displaying similar objects, objects with related relationships can be automatically identified according to the hierarchy rules. This allows users to not only see objects that directly match their needs but also obtain information about other related objects, helping to more comprehensively meet their object selection requirements.

[0093] For example, you can set the number of levels for displaying relationships. If you set the number of levels to 0, you can only display the visual elements corresponding to the similar objects themselves. If you set the number of levels to 1, you can display the visual elements of the similar objects and the related objects that have one level of relationship with the similar objects. If you set the number of levels to 2, you can display the visual elements of the similar objects, the first-level related objects that have one level of relationship with the similar objects, and the second-level related objects that have another level of relationship with the first-level related objects.

[0094] Different association display rules can also be set. For example, you can set it to display associated objects with any relationship, or you can set it to display associated objects with a specific relationship. When there are multiple levels of association display, you can also set different association display rules for different levels. For example, you can set the first level to display objects that have a hierarchical relationship with similar objects, the second level to display objects that have a dependency relationship with similar objects, and so on.

[0095] This disclosure provides multiple ways to determine candidate visualization elements, which can support the display of similar objects that directly match user needs, and can also support the mining and display of associated objects to provide users with richer and more comprehensive object information. This allows users to understand objects related to their needs from multiple perspectives, avoids the limitation of choices due to insufficient information, and helps to make more appropriate decisions.

[0096] In some embodiments of this disclosure, sending a change notification of the target object to an associated user of the other object includes: determining the permission type of the associated user of the other object; and sending a differentiated change notification of the target object to the associated user based on the permission type.

[0097] In this embodiment of the disclosure, after identifying other objects associated with the target object, the permission information of the users associated with these other objects can be queried. Permission types can cover multiple dimensions, such as read permissions, developer permissions, and administrative permissions. Different permission types can reflect the different ranges of a user's capabilities to operate on and access system objects.

[0098] It allows for customized notifications of object changes to users with different access levels. For example, for users with one type of access, the notification content can be more detailed and comprehensive, including technical details of the changes and their impact on the overall system architecture; while for users with another type of access, the notification content can focus on the impact of the changes on business functions or user experience. This differentiated notification approach ensures that each user receives information appropriate to their permissions and needs.

[0099] Through the embodiments of this disclosure, the scope of information dissemination can be controlled by dividing permissions by type. It can also ensure that the information received by each associated user is relevant and necessary to their work, avoiding the sending of a large amount of irrelevant information to all users, reducing information interference, and enabling users to quickly focus on changes related to their permissions and responsibilities, thereby improving the accuracy and effectiveness of information transmission.

[0100] In some embodiments of this disclosure, the permission types include at least development permissions and management permissions; wherein, sending differentiated change notifications of the target object to the associated users according to the permission type includes: the object change notification sent to the associated users with development permissions includes at least the parameter change details corresponding to the modification operation and the scheduling impact corresponding to the modification operation; the object change notification sent to the associated users with management permissions includes at least the scheduling impact corresponding to the modification operation.

[0101] In this embodiment of the disclosure, users with development permissions are responsible for specific technical work such as the development, modification, and maintenance of objects; users with management permissions focus on the management and coordination of the overall project, resources, and personnel. This different permission allocation forms the basis for differentiated notifications.

[0102] For associated users with development privileges, the object change notification sent can include details of parameter changes and scheduling impacts corresponding to the modification operation. The parameter change details can list the parameter changes of the target object before and after the modification, such as data type, interface parameters, and attribute values; the scheduling impacts can show the impact of the modification operation on system scheduling, task execution order, resource allocation, etc., helping developers understand the changes so they can make corresponding code adjustments and feature adaptations.

[0103] For associated users with administrative privileges, the object change notifications can include the scheduling impact of the modification operation. Administrative users can focus on the macro-level impact of the modification operation on overall project progress, resource allocation, team collaboration, and other aspects. Information on the scheduling impact allows them to promptly assess the consequences of the change and make appropriate management decisions.

[0104] In an exemplary embodiment, the scheduling impact of a modification operation can be predicted using historical statistical data, or the scheduling impact of a modification operation can be output using a trained neural network model.

[0105] In an exemplary embodiment, the permission type may also include read permission, which can send a notification to associated users with read permission that the target object has been modified, and can also support associated users with read permission to view the specific parameter change details independently.

[0106] This disclosure provides a specific method for differentiated notifications based on different permission types. Developers can obtain detailed parameter change information for precise development and debugging; administrators can obtain scheduling impact information to make appropriate management decisions. This precise information delivery avoids information overload and interference from irrelevant information, improving the efficiency of users in handling changes.

[0107] In some embodiments of this disclosure, the method further includes: performing configuration operations on the visualization elements; the configuration operations include at least one of the following: dragging the visualization elements; configuring association relationships for multiple visualization elements by drawing connections; configuring association relationships for multiple visualization elements by selecting a type; wherein the association relationships include at least dependency relationships and containment relationships; configuring attribute parameters for target objects without configured parameters through the attribute panel of the visualization elements.

[0108] In this embodiment, users can directly drag and drop visual elements using a mouse or touch device to move and rearrange them on the interface. This operation gives users a high degree of freedom, allowing them to flexibly adjust the position of visual elements according to their needs and preferences, creating a visual interface that conforms to their cognitive habits and business logic. For example, when building a control system, users can place multiple highly related objects in the same area, or drag important objects to a prominent position for easy viewing and management.

[0109] In this embodiment of the disclosure, users can directly use drawing tools to draw lines connecting different visual elements on the interface to clarify the relationships between elements (i.e., between objects). For example, lines corresponding to dependencies can be drawn to indicate that the operation of one object depends on data or functions provided by another object. By drawing lines, information such as dependencies, inclusion relationships, call relationships, and data flow between different objects can be clearly presented.

[0110] In this embodiment, multiple relationship types (such as dependency, containment, etc.) can be provided, allowing users to quickly configure relationships between multiple visual elements by selecting the appropriate type. This method is simple to operate and can be used to quickly establish logical relationships between elements. For example, when building a system architecture model, the user can select "containment" to quickly and accurately set a parent module object to contain multiple child module objects as visual elements.

[0111] In this embodiment of the disclosure, each visual element can display a corresponding attribute panel, which can show various configurable parameters of the corresponding object. For target objects that have not yet been configured with parameters, users can input the corresponding parameter values ​​in the attribute panel according to actual needs, thereby improving the attributes and functions of the target object.

[0112] This disclosure provides a method for users to model objects using visual operations such as dragging, drawing lines, and selecting types. It offers a way to configure and model elements without writing complex code or commands, relying solely on simple graphical interaction. Furthermore, each object can be equipped with an attribute panel, providing users with fine-grained configuration capabilities for target object attribute parameters. The multiple configuration methods and rich relationship types make this solution applicable to different domains and object management scenarios, improving overall development efficiency.

[0113] In an exemplary embodiment, the user may also manually select the target object precisely from the object knowledge base for modeling, or may create a new object, configure its attribute parameters, and then use it for modeling. This disclosure does not limit this.

[0114] In some embodiments of this disclosure, the type of the target object includes at least one of the following: signal object, service component object, control unit object, and system object; wherein, the attribute parameters configured for a signal object without configured parameters include at least one of the following: data type and transmission frequency; the attribute parameters configured for a service component object without configured parameters include at least one of the following: service interface, input parameters, output parameters, and invocation method; and the attribute parameters configured for a control unit object without configured parameters include at least one of the following: microcontroller model, memory size, peripheral interface, and data processing strategy.

[0115] In this embodiment of the disclosure, different types of objects perform different functions in the system, and clear object classification helps to carry out targeted configuration processing based on object characteristics.

[0116] In this context, a service component object can be an SOA (Service-Oriented Architecture) service, a technology that encapsulates software functionality into independent, reusable service modules. These modules enable communication and collaboration between different functional units through standardized interfaces. For example, remote control functionality in the automotive field can be abstracted as an SOA service, allowing other modules to control door locks by calling this service without directly relying on the underlying hardware or code.

[0117] The control unit can be an ECU (Electronic Control Unit), a microcomputer composed of a microprocessor, memory, input / output interfaces, etc. It can receive sensor signals and output control commands to achieve precise control of other controllable systems. For example, in the automotive field, an ECU can precisely control systems such as the engine, transmission, and body electronics. The ECU can analyze throttle position sensor signals to adjust the fuel injection quantity to optimize engine performance.

[0118] For signal objects without configured parameters, attributes such as data type and transmission frequency can be configured. Data type determines the format of the information carried by the signal, such as numeric, character, integer, floating-point, or Boolean values, and determines the range and precision of information the signal can represent. Transmission frequency specifies the number of times the signal is transmitted per unit time, affecting the signal's real-time performance and data volume. By configuring these parameters, the characteristics of the signal object can be precisely defined to meet the actual business needs for signal transmission.

[0119] For service component objects without configured parameters, attributes such as service interface, input parameters, output parameters, and invocation method can be configured. The service interface is used for interaction and communication with other objects; it defines the channel for the service component to interact with the outside world and clarifies the functions that can be invoked. Input parameters are the data content required for the service component to run, and output parameters are the results of service processing. Configuring input and output parameters ensures that the service component's function calls have clear data specifications. The invocation method determines how the service is triggered, such as synchronous or asynchronous calls. By configuring these parameters, the functionality and usage of the service component can be clearly defined.

[0120] For control unit objects without configured parameters, attributes such as microcontroller model, memory size, peripheral interfaces, and data processing strategies can be configured. The microcontroller model affects the control unit's computing power and functionality; memory size determines data storage and processing capabilities; peripheral interfaces are used to connect to external devices, defining the connection method and capability between the control unit and external devices, such as serial ports, parallel ports, and USB interfaces; the data processing strategy specifies the logic and methods for data processing to achieve the corresponding control functions, and the data processing strategy can be written method functions, microprograms, etc. These parameter configurations make the control unit object more closely suited to actual application scenarios, enabling the control unit to meet specific control requirements.

[0121] Through the embodiments of this disclosure, the type of the target object can be clearly identified, and corresponding attribute parameters can be configured for different types of objects. This helps to flexibly adjust and expand the attributes of the object according to actual needs. Furthermore, the clear attribute parameter configuration makes the functions and characteristics of each component / object used by the system clearer, which facilitates the maintenance and management of the system by developers and maintenance personnel.

[0122] In some embodiments of this disclosure, the method further includes: constructing a model component in response to a configuration operation on the visualization element.

[0123] In this embodiment of the disclosure, users are allowed to directly configure visual elements, such as adjusting parameters and modifying attributes. Users can configure visual elements of one or more target objects and establish relationships between these target objects by manipulating these visual elements to construct model components that meet specific user needs and achieve personalized customization.

[0124] The model components can be applied to relevant business scenarios or system development to meet users' R&D needs.

[0125] This embodiment enables users to intuitively understand and manipulate target objects, and to build model components conveniently, quickly, and flexibly, adapting to diverse business scenarios and different users' requirements for object management, thereby improving overall development efficiency.

[0126] Figure 4 This is a flowchart illustrating yet another object management method according to some embodiments of the present disclosure.

[0127] In this embodiment of the disclosure, Figure 4 The object management method shown includes any one or any combination of steps S410, S420, S430, and S440, wherein steps S410 and S420 are respectively related to... Figure 1 Steps S110 and S120 in the object management method shown correspond to each other and will not be repeated here.

[0128] In some embodiments of this disclosure, in Figure 1 Based on the object management method shown, Figure 4 The object management method shown may also include the following steps.

[0129] Step S430: In response to the configuration operation of the visualization element, perform consistency verification and / or integrity verification on the configured model component; wherein, the consistency verification includes at least one of the following: data format matching verification, interface parameter matching verification, physical connection verification; the integrity verification includes at least one of the following: required field check, relationship integrity verification, functional coverage verification.

[0130] In this embodiment of the disclosure, after the user configures the corresponding object using visual elements, the configured model components can be verified for consistency and / or integrity. This step demonstrates rigorous control over the configuration results, setting up a quality verification checkpoint before building the model components, avoiding problems in subsequent model components due to configuration errors, and improving the stability and reliability of the system.

[0131] Among them, consistency verification can be used to check the compatibility and matching degree between different parts of the model components, ensuring that there are no conflicts in data, interfaces, etc. during interaction and operation; integrity verification can be used to check whether the model components contain all the necessary elements, ensuring the complete implementation of functions.

[0132] In an exemplary embodiment, for data format matching verification in conformance verification, it can be checked whether the signal attributes (such as data type and transmission frequency) are consistent with the requirements; for example, the "digital" type of the sensor signal must be compatible with the configuration of the ECU input pins. For interface parameter matching verification, it can be verified whether the input and output parameters are consistent with the caller's requirements; for example, the output parameters of the control command must conform to the parsing protocol of the receiving ECU to avoid functional failure due to data format errors. For physical connection verification, it can be verified whether the signal transmission path is consistent with the actual wiring harness connection; for example, the camera signal must be correctly routed to the designated input channel of the autonomous driving domain controller.

[0133] In an exemplary embodiment, the mandatory field check in integrity verification can examine whether the model contains all critical objects (such as signals, SOA services, and ECUs). For example, if an autonomous driving system model lacks camera signals or decision-making SOA services, it will result in functional deficiencies. For relationship integrity verification, the completeness of the relationships between objects can be checked. For example, an ECU object must establish a connection with its corresponding signal object; otherwise, data interaction cannot be achieved. For functional coverage verification, the model can be checked whether it covers all required scenarios. For example, the remote control function for vehicle door locks must simultaneously include signal transmission, SOA service calls, and ECU execution logic for the necessary scenarios.

[0134] In an exemplary embodiment, consistency verification may be set only, integrity verification may be set only, or both consistency verification and integrity verification may be set simultaneously, depending on the design requirements of the model.

[0135] Step S440: In response to the successful verification, construct the model component.

[0136] In this embodiment, once all the pre-defined verifications have passed, the model component can be formally built and put into use or integrated into the system. This step ensures that the built model component is of high quality and can operate normally, reducing the workload of subsequent debugging and repair, and improving development efficiency.

[0137] Through the embodiments disclosed herein, comprehensive consistency and integrity verification can be performed to verify whether there are any problems with the model components in terms of data format, interface parameters, connection relationships, and functional implementation before formally building the model components. This ensures that the final built model components meet the design specifications, reduces system failures and errors caused by defects in the components themselves, and improves the stability and reliability of the system.

[0138] In some embodiments of this disclosure, the object management method further includes: updating the object associations in the object knowledge base according to the associations in response to the configuration operation containing configuration associations.

[0139] In this embodiment of the disclosure, when there is a behavior in the configuration operation that configures the relationship between multiple visual elements (such as configuring the dependency or containment relationship by drawing lines, selecting the type), the update of the object knowledge base can be triggered.

[0140] Specifically, it can retrieve user-configured relationship information and update the relationships between corresponding objects in the object knowledge base based on this information. Newly configured relationships between objects are recorded in the object knowledge base, overwriting or supplementing existing relationship information, ensuring that the object knowledge base always reflects the latest state of object relationships.

[0141] In an exemplary embodiment, the hierarchical relationships between objects configured for model components can be stored using a tree structure, and the dependencies between objects can be stored using a linked list structure. Tree and linked list structures clearly represent the relationships between objects, facilitating quick querying and updates.

[0142] Through the embodiments disclosed herein, the object knowledge base can be updated in a timely manner based on the relationships in the configuration operations, ensuring that the object relationships in the knowledge base remain synchronized with the actual configuration and always reflect the latest state of relationships between objects. This avoids errors in object matching and retrieval caused by the knowledge base lagging behind actual applications, providing reliable data support for the system's object management based on the knowledge base, and guaranteeing the accuracy and effectiveness of object management.

[0143] It should be noted that the above figures are merely illustrative representations of the processes included in methods according to some embodiments of this disclosure, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0144] The following are embodiments of the apparatus disclosed herein, which can be used to execute embodiments of the method disclosed herein. For details not disclosed in the apparatus embodiments of this disclosure, please refer to the embodiments of the method disclosed herein.

[0145] Figure 5 This is a block diagram illustrating an object management device according to some embodiments of the present disclosure. (Refer to...) Figure 6 The device includes: a demand determination unit 501, an object determination unit 502, a modification determination unit 503, a notification unit 504, a configuration unit 505, and an update unit 506.

[0146] The requirement determination unit 501 is used to determine user requirements; the object determination unit 502 is used to determine a target object matching the user requirements from an object knowledge base and display the visual elements of the target object; wherein, the object knowledge base is configured as a database containing the relationships between various objects; the modification determination unit 503 is used to determine other objects associated with the target object based on the object knowledge base in response to a modification operation on the visual elements of the target object; and the notification unit 504 is used to send a change notification of the target object to the users associated with the other objects via the object determination unit 502.

[0147] In some implementations, the requirement determination unit 501 determines user requirements by receiving a user's natural language requirement statement; wherein, the object determination unit 502 determines a target object matching the user requirement from an object knowledge base by: extracting object features from the natural language requirement statement; wherein the object features include the object's structure and / or functional features; determining the semantic similarity between the object features and objects in the object knowledge base; and determining the target object based on similar objects whose semantic similarity exceeds a preset threshold.

[0148] In some implementations, the object determination unit 502 determines the target object based on similar objects whose semantic similarity exceeds a preset threshold, including: displaying candidate visual elements based on similar objects whose semantic similarity exceeds the threshold; determining the target object based on the user's selection operation on the candidate visual elements; wherein the candidate visual elements are determined by at least one of the following: determining a first visual element corresponding to the similar object as the candidate visual element; determining an associated object in the object knowledge base that has an association relationship with the similar object in response to the user's association display operation or according to a preset display hierarchy; and determining a second visual element corresponding to the associated object as the candidate visual element.

[0149] In some implementations, the notification unit 504 sends a change notification of the target object to the associated users of the other objects, including: determining the permission type of the associated users of the other objects; and sending a differentiated change notification of the target object to the associated users according to the permission type.

[0150] In some implementations, the permission types include at least development permissions and management permissions; wherein, the notification unit 504 sends differentiated change notifications of the target object to the associated users according to the permission types, including: the object change notification sent to the associated users with development permissions includes at least the parameter change details corresponding to the modification operation and the scheduling impact corresponding to the modification operation; the object change notification sent to the associated users with management permissions includes at least the scheduling impact corresponding to the modification operation.

[0151] In some embodiments, the object management device further includes a configuration unit 505, configured to: perform configuration operations on the visual elements; the configuration operations include at least one of the following: dragging the visual elements; configuring association relationships for multiple visual elements by drawing lines; configuring association relationships for multiple visual elements by selecting a type; and configuring attribute parameters for target objects without configured parameters through the attribute panel of the visual elements.

[0152] In some embodiments, the configuration unit 505 is further configured to: construct a model component in response to a configuration operation on the visualization element; this includes: performing consistency verification and / or integrity verification on the configured model component in response to a configuration operation on the visualization element; and constructing the model component in response to the verification passing; wherein the consistency verification includes at least one of the following: data format matching verification, interface parameter matching verification, and physical connection verification; and the integrity verification includes at least one of the following: required field check, relationship integrity verification, and function coverage verification.

[0153] In some embodiments of this disclosure, the update unit 506 is configured to: update the object association in the object knowledge base according to the association in response to the configuration operation including configuration association.

[0154] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0155] Figure 6 This is a block diagram illustrating an apparatus 600 for object management according to some embodiments of the present disclosure. For example, apparatus 600 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0156] Reference Figure 6 The device 600 may include one or more of the following components: a processing component 602, a memory 604, a power component 606, a multimedia component 608, an audio component 610, an input / output (I / O) interface 612, a sensor component 614, and a communication component 616.

[0157] Processing component 602 typically controls the overall operation of device 600, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 602 may include one or more modules to facilitate interaction between processing component 602 and other components. For example, processing component 602 may include a multimedia module to facilitate interaction between multimedia component 608 and processing component 602.

[0158] Memory 604 is configured to store various types of data to support the operation of device 600. Examples of this data include instructions for any application or method operating on device 600, contact data, phonebook data, messages, pictures, videos, etc. Memory 604 can be implemented by any type of volatile or non-volatile storage 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.

[0159] The power supply component 606 provides power to the various components of the device 600. The power supply component 606 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device 600.

[0160] Multimedia component 608 includes a screen that provides an output interface between the device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 608 includes a front-facing camera and / or a rear-facing camera. When the device 600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0161] Audio component 610 is configured to output and / or input audio signals. For example, audio component 610 includes a microphone (MIC) configured to receive external audio signals when device 600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 604 or transmitted via communication component 616. In some embodiments, audio component 610 also includes a speaker for outputting audio signals.

[0162] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0163] Sensor assembly 614 includes one or more sensors for providing status assessments of various aspects of device 600. For example, sensor assembly 614 may detect the on / off state of device 600, the relative positioning of components such as the display and keypad of device 600, changes in the position of device 600 or a component of device 600, the presence or absence of user contact with device 600, the orientation or acceleration / deceleration of device 600, and temperature changes of device 600. Sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 614 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0164] Communication component 616 is configured to facilitate wired or wireless communication between device 600 and other devices. Device 600 can access wireless networks based on communication standards, such as WiFi, 3G, 4G, 5G, other communication standards, or combinations thereof. In some embodiments of this disclosure, communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In some embodiments of this disclosure, communication component 616 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0165] In some embodiments of this disclosure, the apparatus 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0166] In some embodiments of this disclosure, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions that can be executed by a processor 620 of device 600 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0167] A non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to execute an object management method, the method comprising: receiving a natural language requirement statement; determining a target object matching the natural language requirement statement from an object knowledge base and displaying visual elements of the target object; and constructing model components in response to configuration operations on the visual elements.

[0168] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0169] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. An object management method characterized by comprising: include: Determine user needs; The system identifies target objects that match the user's needs from an object knowledge base and displays the visual elements of the target objects; wherein the object knowledge base is configured as a database containing the relationships between various R&D objects, and the R&D objects include signal objects and / or functional objects; In response to a modification operation on the visual elements of the target object, other objects associated with the target object are determined based on the object knowledge base; wherein, the modification operation includes modifying the attribute parameters of the target object, and / or modifying the association relationship between the target object and other objects; Send a change notification for the target object to the associated users of the other objects.

2. The method of claim 1, wherein, The step of determining user needs includes: receiving a user's natural language requirement statement; wherein, the step of determining a target object matching the user's requirement from an object knowledge base includes: Extract object features from the natural language requirement statement; wherein, the object features include the object's structural and / or functional features; Determine the semantic similarity between the object features and objects in the object knowledge base; The target object is determined based on similar objects whose semantic similarity exceeds a preset threshold.

3. The method of claim 2, wherein, Determining the target object based on similar objects whose semantic similarity exceeds a preset threshold includes: Based on similar objects whose semantic similarity exceeds a threshold, candidate visualization elements are displayed. The target object is determined based on the user's selection of the candidate visual elements; The candidate visualization elements are determined by at least one of the following: The first visual element corresponding to the similar object is determined as the candidate visual element; In response to the user's associated display operation or according to the preset display hierarchy, determine the associated objects of the similar objects in the object knowledge base; and determine the second visualization element corresponding to the associated object as the candidate visualization element.

4. The method of claim 1, wherein, Sending the change notification of the target object to the associated users of the other objects includes: Determine the permission types of the associated users of the other objects; Based on the permission type, send differentiated change notifications for the target object to the associated user.

5. The method of claim 4, wherein, The permission types include at least development permissions and management permissions; wherein, sending differentiated change notifications for the target object to the associated user based on the permission type includes: The object change notification sent to the associated user with development privileges shall include at least the parameter change details corresponding to the modification operation and the scheduling impact corresponding to the modification operation; The object change notification sent to the associated user with management privileges shall include at least the scheduling impact corresponding to the modification operation.

6. The method of claim 1, wherein, The method further includes: performing configuration operations on the visualization elements; the configuration operations include at least one of the following: Drag and drop the visual elements; Configure relationships between multiple visual elements by drawing connecting lines; Configure relationships between multiple visualization elements by selecting a type; Configure attribute parameters for target objects that have not been configured with parameters through the attribute panel of the visual element.

7. The method of claim 6, wherein, The method further includes: constructing a model component in response to a configuration operation on the visualization element; which includes: In response to the configuration operation of the visualization element, perform consistency verification and / or integrity verification on the configured model components; In response to the successful verification, the model components are constructed; The consistency verification includes at least one of the following: data format matching verification, interface parameter matching verification, and physical connection verification; the integrity verification includes at least one of the following: required field check, relationship integrity verification, and function coverage verification.

8. The method of claim 6, wherein, The method further includes: In response to the configuration operation including configuration associations, the object associations in the object knowledge base are updated according to the associations.

9. An object management apparatus characterized by comprising: include: The requirement determination unit is used to determine user requirements; An object determination unit is used to determine a target object that matches the user's needs from an object knowledge base and to display the visual elements of the target object; wherein, the object knowledge base is configured as a database containing the relationships between various R&D objects, and the R&D objects include signal objects and / or functional objects; The modification determination unit is configured to, in response to a modification operation on the visual elements of the target object, determine other objects associated with the target object based on the object knowledge base; wherein the modification operation includes modifying the attribute parameters of the target object and / or modifying the association relationship between the target object and other objects; The notification unit is used to send a change notification of the target object to the associated users of the other objects.

10. The apparatus of claim 9, wherein, The requirement determination unit determines user requirements by: receiving the user's natural language requirement statement; wherein, the object determination unit determines target objects matching the user's requirements from an object knowledge base, including: Extract object features from the natural language requirement statement; wherein, the object features include the object's structural and / or functional features; Determine the semantic similarity between the object features and objects in the object knowledge base; The target object is determined based on similar objects whose semantic similarity exceeds a preset threshold.

11. The apparatus of claim 9, wherein, The notification unit sends a change notification of the target object to the associated users of the other objects, including: Determine the permission types of the associated users of the other objects; Based on the permission type, send differentiated change notifications for the target object to the associated user.

12. An electronic device, comprising: include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the steps of the method according to any one of claims 1-8.

13. A non-transitory computer-readable storage medium, wherein when instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is enabled to perform the steps of the method according to any one of claims 1-8.

14. A computer program product comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-8.

Images