Data management method and device of backpack system and storage medium

Abstract

The invention discloses a data management method and device of a backpack system and a storage medium, and belongs to the technical field of data management. The method comprises the steps of receiving a data acquisition request which comprises a globally unique identifier of a target data object, retrieving a central registry according to the globally unique identifier, determining a functional module responsible for managing the target data object, acquiring a standardized data access interface associated with the functional module, and accessing the target data object through the standardized data access interface. And initiating a detail acquisition operation for the target data object to a function module, and receiving and outputting detail information of the target data object returned by the function module. According to the application, the data content maintained by the knapsack system is adjusted from all article data to the access interface corresponding to the data, and the system coupling degree is reduced, so that the maintainability and expandability of the knapsack system are improved.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a data management method, device and storage medium for a backpack system. Background Technology

[0002] In related technologies, item data management solutions typically employ a centralized design. The system defines a large central item data table encompassing all attribute fields for all item types and establishes a unified backpack management system. Data for all item instances is stored within a single data model of this backpack system. When a query or operation is required on any item, the business logic must be initiated through this backpack system. Internally, the system first queries the item's type based on its identifier, and then executes the corresponding specific logic based on the type branch.

[0003] However, since the data structure and management logic of all items are concentrated within the backpack system, any changes to the item logic or attribute expansions belonging to a specific functional module, such as the character system or equipment system, require modifications to the core code and data table structure of the backpack system. In this situation, the backpack system's data management becomes complex, increasing the system maintenance burden.

[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a data management method, device and storage medium for a backpack system, which aims to solve the technical problems of complex data management and excessive maintenance burden of backpack systems.

[0006] To achieve the above objectives, this application provides a data management method for a backpack system, the method comprising the following steps: Receive a data acquisition request, wherein the request contains a globally unique identifier of the target data object; Based on the globally unique identifier, the central registry is retrieved to determine the functional module responsible for managing the target data object; Obtain the standardized data access interface associated with the functional module; Through the standardized data access interface, a detailed data object retrieval operation is initiated to the functional module; Receive and output the detailed information of the target data object returned by the functional module.

[0007] In one embodiment, the step of receiving a data acquisition request further includes a module identifier of the requester, and the step of retrieving the central registry based on the globally unique identifier to determine the functional module responsible for managing the target data object includes: Based on the module identifier of the requester, retrieve the first functional module identifier from the central registry; Based on the globally unique identifier, retrieve the second functional module identifier from the central registry; If the first functional module identifier is different from the second functional module identifier, the step of determining the functional module responsible for managing the target data object is executed.

[0008] In one embodiment, after the step of receiving and outputting the details of the target data object returned from the functional module, the method further includes: Based on a predefined general data structure, the received details information is formatted and encapsulated to generate the response data; The response data is returned to the party that initiated the data retrieval request.

[0009] In one embodiment, after the step of obtaining the standardized data access interface associated with the functional module, the method further includes: If the standardized data access interface is not found, obtain the globally unique identifier of the target data object and the failure reason identifier; Based on the globally unique identifier and the failure reason identifier, generate and return query failure response information.

[0010] In one embodiment, the coordinated data query method of the modular data architecture further includes: Receive a data update request, wherein the data update request includes at least one target globally unique identifier of the data object to be updated and the corresponding data to be updated; The central registry is retrieved based on the target globally unique identifier of the data object to be updated, and the target functional module of the data object to be updated is determined. Obtain the standardized data update interface associated with the target functional module; The data to be updated is distributed to the target functional module through the standardized data update interface, so that the target functional module can perform the data update action.

[0011] In one embodiment, before the step of receiving a data acquisition request, wherein the request contains a globally unique identifier of a target data object, the method further includes: Receive a registration request from at least one of the functional modules, wherein the registration request includes the globally unique identifier of the functional module and reference information of the standardized data access interface; Construct a correspondence between the globally unique identifier of the functional module and the reference information of the standardized data access interface, and record the correspondence in the interface mapping library; The step of obtaining the standardized data access interface associated with the determined functional module includes: Based on the identifier of the functional module, query the interface mapping library to obtain the reference information of the corresponding standardized data access interface, and access the standardized data access interface based on the reference information.

[0012] In one embodiment, the step of initiating a details retrieval operation to the functional module through the standardized data access interface includes: Based on the globally unique identifier, the local identifier of the target data object within the functional module is parsed from the central registry. The standardized data access interface is used to send a detailed information retrieval instruction containing the local identifier to the functional module.

[0013] In one embodiment, after the step of receiving a data acquisition request, wherein the request contains a globally unique identifier of a target data object, the method further includes: If the data acquisition request contains the globally unique identifiers of multiple target data objects, the globally unique identifiers are grouped based on the functional module; Based on each set of globally unique identifiers and the corresponding functional modules, obtain detailed information about the target data object; The detailed information returned by the different functional modules is aggregated to form an integrated response to the data acquisition request.

[0014] In addition, to achieve the above objectives, this application also provides a data management device for a backpack system, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the data management method for the backpack system as described above.

[0015] In addition, to achieve the above objectives, this application also provides a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the data management method of the backpack system as described above.

[0016] One or more technical solutions proposed in this application have at least the following technical effects: This application utilizes a backpack system to request data based on a globally unique identifier. By retrieving the central registry, it determines the module to which the target data object belongs, obtains the standardized data access interface provided by that module, and initiates a details retrieval operation through this interface. It then receives and outputs the details information processed and returned by the functional module itself. This transforms the data content maintained by the backpack system from all item data to the corresponding data access interface. Each functional module retrieves the corresponding data based on this access interface, requiring only the implementation of a unified access interface and the maintenance of its own data, thus improving maintainability and scalability. Attached Figure Description

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

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating the first embodiment of the data management method for the backpack system of this application; Figure 2 This is a schematic diagram of the backpack system architecture according to the first embodiment of this application; Figure 3 This is a flowchart illustrating the second embodiment of the data management method for the backpack system of this application; Figure 4 This is a flowchart illustrating the third embodiment of the data management method for the backpack system of this application; Figure 5 This is a flowchart illustrating the fourth embodiment of the data management method for the backpack system of this application; Figure 6 This is a flowchart illustrating the fifth embodiment of the data management method for the backpack system of this application; Figure 7 This is a schematic diagram of the structure of the data management device of the backpack system in the hardware operating environment involved in the embodiments of this application.

[0020] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0022] To better understand the above technical solutions, the following will provide a detailed explanation of the technical solutions in conjunction with the accompanying drawings and specific implementation methods.

[0023] The main solution of this application embodiment is: receiving a data acquisition request, the request containing a globally unique identifier of the target data object; retrieving the central registry based on the globally unique identifier to determine the functional module responsible for managing the target data object; obtaining a standardized data access interface associated with the functional module; initiating a details acquisition operation for the target data object to the functional module through the standardized data access interface; and receiving and outputting the details information of the target data object returned by the functional module.

[0024] Existing item data management solutions typically employ a centralized design. The system defines a massive central item data table encompassing all attribute fields for all item types and establishes a unified backpack management system. All item instance data is stored within a single data model of this backpack system. When querying or manipulating any item, business logic must be initiated through this backpack system. Internally, the system first queries the item's type based on its identifier, then executes the corresponding specific logic based on the type branch. However, because all item data structures and management logic converge within the backpack system, any changes to item logic or attribute expansions belonging to specific functional modules, such as the character system or equipment system, require modifications to the backpack system's core code and data table structure. In this scenario, the backpack system's data management becomes cumbersome, increasing the system maintenance burden.

[0025] This application utilizes a backpack system to request data based on a globally unique identifier. By retrieving the central registry, it determines the module to which the target data object belongs, obtains the standardized data access interface provided by that module, and initiates a details retrieval operation through this interface. It then receives and outputs the details information processed and returned by the functional module itself. This transforms the data content maintained by the backpack system from all item data to the corresponding data access interface. Each functional module retrieves the corresponding data based on this access interface, requiring only the implementation of a unified access interface and the maintenance of its own data, thus improving maintainability and scalability.

[0026] To better understand the above technical solutions, exemplary embodiments of this application will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of this application and to fully convey the scope of this application to those skilled in the art.

[0027] It should be noted that the executing entity in this embodiment can be a backpack system, or a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device or data management device of the backpack system capable of the above functions. This embodiment does not specifically limit it. The following uses a backpack system as an example to describe this embodiment and the following embodiments.

[0028] Based on this, embodiments of this application provide a data management method for a backpack system, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the data management method for the backpack system of this application.

[0029] In this embodiment, the data management method of the backpack system includes steps S10 to S40: Step S10: Receive a data acquisition request, the request containing a globally unique identifier of the target data object; Step S20: Based on the globally unique identifier, retrieve the central registry to determine the functional module responsible for managing the target data object; In this embodiment, the backpack system maintains a central registry, which contains the correspondence between globally unique identifiers and different functional modules. The globally unique identifier is a string identifier unique throughout the entire application or game project, used to unambiguously refer to a specific item instance; its composition is typically independent of any specific functional module. A data acquisition request is an instruction initiated by an external system or logic to the backpack system, which acts as the central coordinator, intending to obtain complete information about a specific item. The backpack system, as a service provider, continuously monitors its available standardized interfaces. When such an interface is invoked and a data acquisition request is received, it retrieves the globally unique identifier of the target item encapsulated within the data packet of the data acquisition request and invokes the corresponding query service.

[0030] Specifically, the backpack system provides an entry point for external data query services within its software architecture, such as a public application programming interface (API) function. When external code, such as the role system or user interface logic, needs to query detailed information about an item, it calls this entry function and passes in the globally unique identifier string of the target item as a parameter. The backpack system's server-side logic captures this call, parses the passed parameter string, and temporarily stores it as the target identifier for this query process, thus completing the reception and initialization of the request.

[0031] Furthermore, during the initialization phase, the backpack system loads a central registry into memory, forming a data structure that supports efficient key-value queries. When this step is executed, the system uses the target's globally unique identifier as the query key to search within this in-memory data structure. Upon successful retrieval, the value of the module identifier field, such as "EQUIP_SYSTEM," is extracted from the corresponding data entry. This field value explicitly identifies the functional module responsible for managing the target data object, thus completing the mapping from logical identifier to the physical management responsibility.

[0032] In one implementation, the backpack system architecture is as follows: Figure 2 As shown, Figure 2 This is a schematic diagram of the backpack system architecture involved in this embodiment. (Refer to...) Figure 2 BagSystem is the backpack system for managing all items. It directly manages general items without additional attributes and uses an interface to manage other system-specific items with additional attributes. ItemConfig is the backpack system item table, i.e., the central registry mentioned above. All items in the entire project are in this table. It configures uniqueId, module, itemId, and other common attributes such as name, description, and icon. uniqueId: string, a globally unique ID within the project. module: string, indicating which system module the item belongs to. itemId: int, the item ID under the system module, unique only within the system module, and does not need to be concerned with whether it is duplicated with IDs under other system modules. BagModel is the backpack system data layer, managing only general items. ItemBaseInfo is the base class for item data structure, containing uniqueId and num. num represents the number of useful items. ItemPb is the item data issued by the server. extra: byte[] is the extra data of the item, which can be parsed into the item protocol of the corresponding system. IBagOption is the query / update item interface. When querying / updating data not belonging to the system itself, the query / update functions in BagSystem are called, passing in the uniqueId. BagSystem first queries the ItemConfig table to obtain the module and itemId, and then calls the IBagOption function implemented by the module to query / update the item. The interface function signatures include the corresponding interfaces for querying and updating item data, where querying item data is ItemBaseInfo QueryItem(int itemId), and updating item data is void UpdateItemInfo(List <itempb>items).

[0033] The ItemConfig table serves as the central registry. Its core fields include a globally unique string identifier (uniqueId), a module field indicating the functional module to which an item belongs (as shown in the example "trng"), and a numeric identifier (itemId) unique only within the module. Under this architecture, BagSystem directly manages general items through its internal BagModel and ItemDict. Dedicated functional modules, such as the RoleModel and EquipModel, manage data structures that inherit from the common base class ItemBaseInfo and extend their own dedicated attributes (such as roleId, equipmentId, and quality). All functional modules must implement the unified FlagOption interface (providing QueryItem and UpdateItemInfo methods), enabling BagSystem to indirectly query or update data by calling the corresponding module's interface after determining the module to which an item belongs by querying the ItemConfig table. This achieves distributed and loosely coupled management of various item data throughout the system.

[0034] For example, taking a functional module-based role system, a BagModel is defined under BagSystem. A Dictionary is defined within BagModel.<int, RoleInfo> Manage character data. RoleInfo inherits from ItemBaseInfo and defines character-related fields. BagSystem implements the IBagOption interface. The RoleConfig character table contains the uniqueId and quantity of materials consumed when unlocking a character, as well as the equipment data configuration obtained when unlocking.

[0035] Optionally, the data acquisition request received by the backpack system also includes a module identifier of the requester for verification, so that the backpack system can retrieve a first functional module identifier in the central registry based on the module identifier of the requester, and retrieve a second functional module identifier in the central registry based on the globally unique identifier. If the first functional module identifier and the second functional module identifier are different, the step of determining the functional module responsible for managing the target data object is executed.

[0036] Optionally, the BagSystem can also directly manage generic items that do not contain additional attributes. Specifically, BagSystem defines a BagModel to store these generic items and implements the IBagOption interface for querying / updating the IBagOption interface.

[0037] Step S30: Obtain the standardized data access interface associated with the functional module; Step S40: Initiate a details retrieval operation for the target data object to the functional module through the standardized data access interface; In this embodiment, the standardized data access interface is an access interface provided by the functional module that stores the required data. The backpack system can use this standardized data access interface to send an information query request for the target data object, including a globally unique identifier, to the functional module, thereby initiating a detailed retrieval operation for the target data object.

[0038] Optionally, the backpack system parses the local identifier of the target data object within the functional module from the central registry based on the globally unique identifier, and sends a detailed retrieval instruction containing the local identifier to the functional module through a standardized data access interface.

[0039] As an optional implementation, the central registry is implemented in memory as a dictionary set, where the keys are globally unique identifier strings and the values ​​are corresponding functional module identifier strings. This step involves performing a lookup operation on this dictionary to retrieve the value using the key.

[0040] As an alternative implementation, each entry in the central registry contains more information, including a globally unique identifier, a functional module identifier, and a local identifier used by the item within the corresponding functional module, in addition to the globally unique identifier and the functional module identifier. When the backpack system searches using the globally unique identifier, it can simultaneously obtain the functional module identifier and the local identifier within the module. This approach combines route lookup and parameter parsing, improving the efficiency of subsequent steps.

[0041] For example, the backpack system provides the `ItemBaseInfo QueryItemAny(string uniqueId)` interface for other systems to query item data. This interface can query data from any system. First, it reads the `ItemConfig` table to obtain the `module` and `itemId`. Based on the `module`, it retrieves the corresponding system, passes the `itemId` to the `QueryItem` interface implemented by that system, and then obtains the item data. It also provides `void UpdateItemInfoAny(List<ItemId>)`. <itempb>The `items` interface updates item data for other systems. This interface can update item data in any system. First, it iterates through `items`, reads the `ItemConfig` table for each item, obtains the `module` and `itemId`, retrieves the corresponding system based on the `module`, passes the `itemId` to the `UpdateItemInfo` interface implemented by the system, converts the `extra` data in `ItemPb` into its own system protocol data within the system, and updates the item data in the system.

[0042] Step S50: Receive and output the detailed information of the target data object returned by the functional module.

[0043] In this embodiment, the detailed information is a data object generated by the target functional module based on its internal data state, conforming to the standardized data access interface return value convention, and includes the attribute information of the target data object. The knapsack system outputs this detailed information as the final response to the initial data acquisition request to the request initiator.

[0044] Optionally, the backpack system uses a predefined general data structure to format and encapsulate the received details, generate response data, and return the response data to the party that initiated the data retrieval request.

[0045] For example, taking the role system as a functional module, when a user clicks on the role unlocking function, the role system's role unlocking function interface is called, and the role ID is passed in. The role system checks the consumption, reads the RoleConfig table to get the uniqueId and quantity of the consumed material, calls the BagSystem's QueryItemAny interface to get the quantity of the material item held, and at the same time determines whether the material is sufficient.

[0046] This application embodiment utilizes a backpack system to request data based on a globally unique identifier. By retrieving the central registry, it determines the module to which the target data object belongs, obtains the standardized data access interface provided by that module, and initiates a details retrieval operation through this interface. It receives and outputs the details information processed and returned by the functional module itself. This changes the data content maintained by the backpack system from all item data to the access interface for corresponding data. Each functional module retrieves the corresponding data based on this access interface, requiring only the implementation of a unified access interface and maintenance of its own data, thus improving maintainability and scalability.

[0047] Based on the same inventive concept, this application also provides a second embodiment, referring to... Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the data management method for the backpack system of this application.

[0048] In this embodiment, the data management method of the backpack system further includes steps S31-S32: Step S31: If no standardized data access interface is found, obtain the globally unique identifier of the target data object and the failure reason identifier; Step S32: Generate and return query failure response information based on the globally unique identifier and the failure reason identifier.

[0049] In this embodiment, if the backpack system fails to obtain a valid standardized data access interface, it determines that the information retrieval of the target data object has failed. The backpack system obtains the globally unique identifier of the target data object and the failure reason identifier, and fills in a preset response text template based on the globally unique identifier and the failure reason identifier to generate and return query failure response information.

[0050] Specifically, after the backpack system executes the step of obtaining the standardized data access interface, it immediately verifies the result. Verification includes checking whether the returned interface reference is a valid object, or whether the corresponding functional module identifier could not be found when querying the interface mapping library. If the verification fails, it is determined that standard communication with the target functional module cannot be established. The system records the globally unique identifier of the target data object involved in the current request, and matches and obtains the corresponding failure reason identifier based on the specific circumstances of the verification failure. According to a preset response format, the system encapsulates the globally unique identifier and the failure reason identifier into a complete error response data packet. After this data packet is generated, the backpack system immediately terminates the current query process and returns this error response as the final result to the original request initiator, without executing subsequent details retrieval and information output steps.

[0051] Since the system described in Embodiment 2 of this application is a system used to implement the method of Embodiment 1 of this application, those skilled in the art can understand the specific structure and variations of the system based on the method described in Embodiment 1 of this application, and therefore will not be described again here. All systems used in the method of Embodiment 1 of this application fall within the scope of protection of this application.

[0052] Based on the same inventive concept, this application also provides a third embodiment, referring to... Figure 4 , Figure 4 This is a flowchart illustrating the third embodiment of the data management method for the backpack system of this application.

[0053] In this embodiment, the data management method of the backpack system further includes steps S61 to S64: Step S61: Receive a data update request, wherein the data update request includes at least one target globally unique identifier of the data object to be updated and the corresponding data to be updated; Step S62: Retrieve the central registry based on the target globally unique identifier of the data object to be updated, and determine the target functional module of the data object to be updated; Step S63: Obtain the standardized data update interface associated with the target functional module; Step S64: Distribute the data to be updated to the target functional module through the standardized data update interface, so that the target functional module can perform the data update action.

[0054] In this embodiment, the backpack system receives update requests initiated from external sources. These requests contain one or more items consisting of a globally unique target identifier and its corresponding data to be updated. For each item in the request, the backpack system uses its globally unique target identifier as the key to retrieve data from the central registry, thereby identifying the target functional module responsible for managing that item. Based on the identifiers of these target functional modules, the backpack system retrieves the standardized data update interface instances registered by each module from its maintained interface directory. The backpack system groups and aggregates all items to be updated belonging to the same target functional module and distributes the aggregated update data list to that module in one go by calling its update interface. Each functional module, within its interface implementation, is responsible for parsing the received data, performing business validations, and ultimately updating its own managed data model.

[0055] For example, taking the role system as a functional module, when the system receives an upgrade request for the role from the user, it executes a request callback, returning the new role data RolePb and the changed item data List. <itempb>Use RolePb to update the character data in RoleModel, and the list of changed item data. <itempb>The BagSystem's UpdateItemInfoAny method is called to update the acquired items.

[0056] Since the system described in Embodiment 3 of this application is a system used to implement the method of Embodiment 1 of this application, those skilled in the art can understand the specific structure and variations of the system based on the method described in Embodiment 1 of this application, and therefore will not be described again here. All systems used in the method of Embodiment 1 of this application fall within the scope of protection of this application.

[0057] Based on the same inventive concept, this application also provides a fourth embodiment, referring to... Figure 5 , Figure 5 This is a flowchart illustrating the fourth embodiment of the data management method for the backpack system of this application.

[0058] In this embodiment, the data management method of the backpack system further includes steps S01-S02: Step S01: Receive a registration request from at least one of the functional modules, wherein the registration request includes the globally unique identifier of the functional module and the reference information of the standardized data access interface; Step S02: Construct the correspondence between the globally unique identifier of the functional module and the reference information of the standardized data access interface, and record the correspondence in the interface mapping library; In this embodiment, during the system startup phase, the backpack system waits for or actively notifies each functional module to register. Each functional module, including the backpack system itself, the character system, the equipment system, etc., sends a registration request to the backpack system. After receiving these requests, the backpack system extracts the globally unique identifier of the sending functional module and a reference to the standardized data access interface provided by that module, such as an object instance that implements the IBagOption interface, from each request. The backpack system stores the correspondence in a persistent data structure, such as a global dictionary, using the functional module identifier as the key and the interface reference as the value, thereby forming an interface mapping library containing a central registry.

[0059] Optionally, when the backpack system obtains the standardized data access interface associated with a defined functional module, it will query the interface mapping library based on the identifier of the functional module to obtain the reference information of the corresponding standardized data access interface, and access the standardized data access interface based on the reference information.

[0060] This embodiment constructs an interface mapping library through a dynamic registration mechanism, so that the backpack system does not need to hardcode the dependencies of all modules at compile time. It only needs to implement the standard interface and complete the registration at startup to automatically integrate into the existing coordination system, thereby improving the scalability and pluggability of the entire architecture.

[0061] Since the system described in Embodiment 4 of this application is a system used to implement the method of Embodiment 1 of this application, those skilled in the art can understand the specific structure and variations of the system based on the method described in Embodiment 1 of this application, and therefore will not be described again here. All systems used in the method of Embodiment 1 of this application fall within the scope of protection of this application.

[0062] Based on the same inventive concept, this application also provides a fifth embodiment, referring to... Figure 6 , Figure 6 This is a flowchart illustrating the fifth embodiment of the data management method for the backpack system of this application.

[0063] In this embodiment, the data management method of the backpack system further includes steps S11 to S13: Step S11: If the data acquisition request contains the globally unique identifiers of multiple target data objects, group the globally unique identifiers based on the functional module; Step S12: Based on each set of globally unique identifiers and the corresponding functional modules, obtain detailed information about the target data object; Step S13: Aggregate the detailed information returned by the different functional modules to form an integrated response to the data acquisition request.

[0064] In this embodiment, depending on the different external application environments, the data acquisition request received by the backpack system may be a composite request containing the acquisition needs of multiple target data objects, which includes multiple globally unique identifiers.

[0065] Specifically, when the knapsack system receives a data retrieval request containing multiple globally unique identifiers, it determines the functional module to which each identifier belongs. The system divides all identifiers into several groups according to their respective functional modules, with each group containing a batch of identifiers that need to be queried from the same functional module. For each group, the knapsack system obtains the standardized data access interface of that module once and initiates a batch query through this interface, passing in all identifiers within that group or their corresponding internal local identifiers. After processing these batch requests in parallel or serially, each functional module returns a batch of detailed information. The knapsack system collects the returned results from all groups and, according to the order of the identifiers in the original request or a predefined rule, organizes and aggregates these results into a unified list, outputting this list as the final integrated response to the requester.

[0066] Since the system described in Embodiment 5 of this application is a system used to implement the method of Embodiment 1 of this application, those skilled in the art can understand the specific structure and variations of the system based on the method described in Embodiment 1 of this application, and therefore will not be described again here. All systems used in the method of Embodiment 1 of this application fall within the scope of protection of this application.

[0067] This application provides a data management device for a backpack system, the 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, the instructions being executed by the at least one processor to enable the at least one processor to perform the data management method of the backpack system in the first embodiment described above.

[0068] The following is for reference. Figure 7 The diagram illustrates a structural schematic of a data management device suitable for implementing a backpack system according to embodiments of this application. The data management device for the backpack system in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The data management device of the backpack system shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0069] like Figure 7 As shown, the data management device of the backpack system may include a processing unit 1001 (e.g., a core processor, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. The random access memory 1004 also stores various programs and data required for the operation of the backpack system's data management device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the backpack system's data management device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows a backpack system's data management device with various systems, it should be understood that implementing or having all the systems shown is not required. More or fewer systems can be implemented alternatively.

[0070] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0071] The data management device for the backpack system provided in this application, employing the data management method for the backpack system in the above embodiments, can solve the technical problems of complex data management and excessive maintenance burden in backpack systems. Compared with the prior art, the beneficial effects of the data management device for the backpack system provided in this application are the same as those of the data management method for the backpack system provided in the above embodiments, and other technical features in the data management device for the backpack system are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0072] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0073] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0074] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the data management method of the backpack system in the above embodiments.

[0075] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0076] The aforementioned computer-readable storage medium may be included in the data management device of the backpack system; or it may exist independently and not be assembled into the data management device of the backpack system.

[0077] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by the data management device of the backpack system, the data management device of the backpack system causes the following: to receive a data acquisition request, the request containing a globally unique identifier of the target data object; to retrieve the central registry based on the globally unique identifier, to determine the functional module responsible for managing the target data object; to obtain a standardized data access interface associated with the functional module; to initiate a details acquisition operation for the target data object to the functional module through the standardized data access interface; and to receive and output the details information of the target data object returned by the functional module.

[0078] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

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

[0080] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0081] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the data management method of the backpack system described above. This solves the technical problem of complex data management and excessive maintenance burden in backpack systems. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the data management method of the backpack system provided in the above embodiments, and will not be elaborated upon here.

[0082] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.< / itempb> < / itempb> < / itempb> < / itempb>

Claims

1. A data management method for a backpack system, characterized in that, The method includes the following steps: Receive a data acquisition request, wherein the request contains a globally unique identifier of the target data object; Based on the globally unique identifier, the central registry is retrieved to determine the functional module responsible for managing the target data object; Obtain the standardized data access interface associated with the functional module; Through the standardized data access interface, a detailed data object retrieval operation is initiated to the functional module; Receive and output the detailed information of the target data object returned by the functional module.

2. The method according to claim 1, characterized in that, In the step of receiving a data acquisition request, the data acquisition request further includes the module identifier of the requester, and the step of retrieving the central registry based on the globally unique identifier to determine the functional module responsible for managing the target data object includes: Based on the module identifier of the requester, retrieve the first functional module identifier from the central registry; Based on the globally unique identifier, retrieve the second functional module identifier from the central registry; If the first functional module identifier is different from the second functional module identifier, the step of determining the functional module responsible for managing the target data object is executed.

3. The method according to claim 1, characterized in that, After the step of receiving and outputting the detailed information of the target data object returned from the functional module, the method further includes: Based on a predefined general data structure, the received details information is formatted and encapsulated to generate the response data; The response data is returned to the party that initiated the data retrieval request.

4. The method according to claim 1, characterized in that, Following the step of obtaining the standardized data access interface associated with the functional module, the method further includes: If the standardized data access interface is not found, obtain the globally unique identifier of the target data object and the failure reason identifier; Based on the globally unique identifier and the failure reason identifier, generate and return query failure response information.

5. The method according to claim 1, characterized in that, The coordinated data query method of the modular data architecture also includes: Receive a data update request, wherein the data update request includes at least one target globally unique identifier of the data object to be updated and the corresponding data to be updated; The central registry is retrieved based on the target globally unique identifier of the data object to be updated, and the target functional module of the data object to be updated is determined. Obtain the standardized data update interface associated with the target functional module; The data to be updated is distributed to the target functional module through the standardized data update interface, so that the target functional module can perform the data update action.

6. The method according to claim 1, characterized in that, Before the step of receiving a data acquisition request, wherein the request contains a globally unique identifier of the target data object, the method further includes: Receive a registration request from at least one of the functional modules, wherein the registration request includes the globally unique identifier of the functional module and reference information of the standardized data access interface; Construct a correspondence between the globally unique identifier of the functional module and the reference information of the standardized data access interface, and record the correspondence in the interface mapping library; The step of obtaining the standardized data access interface associated with the determined functional module includes: Based on the identifier of the functional module, query the interface mapping library to obtain the reference information of the corresponding standardized data access interface, and access the standardized data access interface based on the reference information.

7. The method according to claim 1, characterized in that, The steps of initiating a details retrieval operation to the functional module through the standardized data access interface include: Based on the globally unique identifier, the local identifier of the target data object within the functional module is parsed from the central registry. The standardized data access interface is used to send a detailed information retrieval instruction containing the local identifier to the functional module.

8. The method according to claim 1, characterized in that, After the step of receiving a data acquisition request, wherein the request contains a globally unique identifier of the target data object, the method further includes: If the data acquisition request contains the globally unique identifiers of multiple target data objects, the globally unique identifiers are grouped based on the functional module; Based on each set of globally unique identifiers and the corresponding functional modules, obtain detailed information about the target data object; The detailed information returned by the different functional modules is aggregated to form an integrated response to the data acquisition request.

9. A data management device for a backpack system, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the data management method for the backpack system as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the data management method of the backpack system as described in any one of claims 1 to 8.

Images