Entity positioning method, device, equipment and readable storage medium

Abstract

The present application discloses an entity positioning method, apparatus, device, and readable storage medium, relating to the field of computer technology. The method comprises acquiring personnel entity data, equipment entity data, and spatial entity data; constructing a relationship graph based on the personnel entity data, equipment entity data, and spatial entity data, wherein the relationship graph includes a first relationship graph, a second relationship graph, and a third relationship graph, wherein the first relationship graph is used to indicate the allocation relationship between the personnel entity data and the equipment entity data, the second relationship graph is used to indicate the positional relationship between the personnel entity data and the spatial entity data, and the third relationship graph is used to indicate the positional relationship between the equipment entity data and the spatial entity data; and implementing a positioning function based on the relationship graph, wherein the positioning function is used to locate a target entity, and combines the connection between the personnel entity and the spatial entity and the equipment entity within the building to improve information utilization while improving the positioning efficiency of the target entity.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computers, and in particular to an entity positioning method, apparatus, device, and readable storage medium. Background Art

[0002] Digital twins mainly use the information of physical equipment to make digital object mapping, and apply three-dimensional reconstruction technology to achieve the purpose of digitizing specific scenes or specific objects. It can provide a solid foundation for the management and development of smart buildings and is the cornerstone for realizing building visualization and digitization.

[0003] In current building management systems, the relationship between space and equipment is usually pre-stored, and attention is paid to the installation location of the equipment while using the space; when determining whether a person is inside the building, indoor positioning is usually used to determine it.

[0004] However, in the related art, only a coarse-dimensional positioning result is obtained, the information utilization rate is low, the accuracy of the personnel positioning result is low, and it is impossible to effectively troubleshoot the equipment. Summary of the Invention

[0005] The embodiments of the present application provide an entity positioning method, apparatus, device, and readable storage medium, which improve information utilization while also improving the accuracy of personnel and equipment positioning. The technical solution is as follows:

[0006] In one aspect, a method for locating an entity is provided, the method comprising:

[0007] Acquire personnel entity data, equipment entity data, and space entity data, wherein the personnel entity data includes personnel structure, the equipment entity data includes equipment structure, and the space entity data includes space distribution;

[0008] constructing a relationship graph based on the person entity data, the device entity data, and the space entity data, wherein the relationship graph includes a first relationship graph, a second relationship graph, and a third relationship graph, wherein the first relationship graph is used to indicate an allocation relationship between the person entity data and the device entity data, the second relationship graph is used to indicate a positional relationship between the person entity data and the space entity data, and the third relationship graph is used to indicate a positional relationship between the device entity data and the space entity data;

[0009] A positioning function is implemented based on the relationship graph, and the positioning function is used to locate the target entity.

[0010] In another aspect, an entity positioning device is provided, the device comprising:

[0011] An acquisition module, configured to acquire personnel entity data, equipment entity data, and space entity data, wherein the personnel entity data includes personnel structure, the equipment entity data includes equipment structure, and the space entity data includes space distribution;

[0012] a construction module, configured to construct a relationship graph based on the person entity data, the device entity data, and the space entity data, wherein the relationship graph includes a first relationship graph, a second relationship graph, and a third relationship graph, wherein the first relationship graph is configured to indicate an allocation relationship between the person entity data and the device entity data, the second relationship graph is configured to indicate a positional relationship between the person entity data and the space entity data, and the third relationship graph is configured to indicate a positional relationship between the device entity data and the space entity data;

[0013] A positioning module is used to implement a positioning function based on the relationship graph, and the positioning function is used to locate the target entity.

[0014] On the other hand, a computer device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set, or an instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the entity positioning method as described in any of the above-mentioned embodiments of the present application.

[0015] On the other hand, a computer-readable storage medium is provided, wherein the storage medium stores at least one instruction, at least one program, a code set, or an instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the entity positioning method as described in any of the above-mentioned embodiments of the present application.

[0016] In another aspect, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer to perform the entity location method described in any of the above embodiments of the present application.

[0017] The beneficial effects of the technical solutions provided in the embodiments of the present application include at least:

[0018] Through the relationship between personnel entities, equipment entities and space entities, personnel entities, equipment entities and space entities are associated to build a relationship diagram between each of them. The target entity is then positioned through this relationship diagram, avoiding the problem in related technologies that only focuses on the positional relationship between equipment entities and space entities, while ignoring the connection between personnel entities and space entities and equipment entities inside the building. This effectively improves the utilization rate of information. When using this relationship diagram for positioning, the content of a personnel entity using a certain equipment entity in a certain space entity can be obtained in a timely manner, thereby improving the positioning efficiency of the target entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0020] Figure 1 This is a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application;

[0021] Figure 2 is a flow chart of an entity positioning method provided by an exemplary embodiment of the present application;

[0022] Figure 3 is a schematic diagram of a relationship diagram provided by an exemplary embodiment of the present application;

[0023] Figure 4 is a flow chart of an entity positioning method provided by another exemplary embodiment of the present application;

[0024] Figure 5 is based on Figure 4 The illustrated embodiment provides a flowchart of human entity positioning;

[0025] Figure 6 is based on Figure 5 The illustrated embodiment provides a schematic diagram of spatial convergence;

[0026] Figure 7 is a flow chart of an entity positioning method provided by another exemplary embodiment of the present application;

[0027] Figure 8 is based on Figure 7 A schematic diagram of a device providing an alarm message in accordance with an embodiment of the present invention is shown;

[0028] Figure 9 is based on Figure 7 A flowchart of a method for locating a faulty device provided in the illustrated embodiment;

[0029] Figure 10 is a structural block diagram of an entity positioning device provided by an exemplary embodiment of the present application;

[0030] Figure 11 is a structural block diagram of an entity positioning device provided by another exemplary embodiment of the present application;

[0031] Figure 12 is a structural block diagram of an entity positioning device provided by another exemplary embodiment of the present application;

[0032] Figure 13 This is a structural block diagram of a server provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0034] First, the application scenarios of the embodiments provided in this application are briefly introduced:

[0035] In traditional building relationship systems, only the binary correspondence between spatial entities and equipment entities is of concern. That is, the equipment entity is located in a certain spatial entity, and the spatial entity is served by a certain equipment entity. There is a lack of a three-way combination with the human entity. This solution includes the following defects: it does not take into account the location of the human entity in the smart building. If the human entity is to be positioned, active positioning or passive positioning must be adopted. Active positioning includes Bluetooth positioning, WiFi positioning, optical positioning, etc., and passive positioning includes UWB positioning, geomagnetic positioning, RFID positioning, etc. However, whether active or passive positioning is implemented for the human entity, only one-dimensional data is combined. It is impossible to combine the device entity data in the smart building to determine the final precise spatial location, and the collected device entity data cannot be maximized.

[0036] In addition, the recovery time object (RTO) is also an important indicator for measuring the intelligence level of smart buildings. When faced with a failure in a device entity within a smart building, the device entities that issue alarm information are generally collected, and these faulty device entities are summarized and sent to the operation and maintenance personnel. The operation and maintenance personnel repair the faulty device entities based on the summarized information. This results in the inability to obtain relevant information about the faulty device entity in a timely manner after the device entity fails, let alone filter out the device entity information corresponding to the fault source device that actually caused the failure from the device entities in the alarm information. Therefore, how to locate the fault source device as quickly as possible through technical means and shorten the RTO is also an issue that the operation and maintenance management of smart buildings is concerned about and needs to be solved urgently.

[0037] Next, the implementation environment of the entity positioning method provided by this application is described. Figure 1 This is a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application. Figure 1 As shown, the implementation environment includes a terminal 110 and a server 120, and the terminal 110 and the server 120 are connected via a communication network 130, and the communication network 130 can be implemented as a wireless network or a wired network;

[0038] Optionally, the terminal 110 is provided with an application or web page system for information entry, and the terminal user uniformly inputs the internal relationships corresponding to the device entity data, personnel entity data, and space entity data into the terminal 110, that is, the terminal 110 manages and uniformly processes the device entity data, personnel entity data, and space entity data; optionally, the terminal 110 stores the above three entity data locally or uploads them to the digital twin database through the server 120. The embodiment of the present application does not limit this. The terminal 110 or the digital twin database stores the device entity data, personnel entity data, and space entity data. In the embodiment of the present application, all personnel included in the personnel entity data correspond to a terminal device that uniquely identifies their own identity. All personnel use the terminal device to complete their own personnel information. The personnel information includes but is not limited to name, gender, position, and department. The terminal 110 updates the personnel entity data based on all received personnel information and completes the personnel information and personnel structure.

[0039] Optionally, the server 120 directly obtains pre-stored personnel entity data, device entity data and spatial entity data from the terminal 110, and constructs a relationship graph based on the above three types of entity data. The relationship graph includes a first relationship graph, a second relationship graph and a third relationship graph, wherein the first relationship graph is used to represent the allocation relationship between personnel entity data and device entity data, the second relationship graph is used to represent the first positional relationship between personnel entity data and spatial entity data, and the third relationship graph is used to represent the second positional relationship between device entity data and spatial entity data. The relationship graph is stored in the digital twin database for subsequent entity positioning process.

[0040] Optionally, the server 120 receives the personnel entity data, device entity data, and space entity data uploaded by the terminal, constructs a relationship graph based on the above three entity data, and directly stores the relationship graph in the digital twin database.

[0041] It is worth noting that the above-mentioned terminal 110 can be implemented as a mobile terminal such as a mobile phone, a tablet computer, a wearable device, a portable laptop computer, etc., or can be implemented as a terminal such as a desktop computer, an electronic game console, etc., and the embodiments of the present application are not limited to this.

[0042] The above-mentioned server 120 can be implemented as a single server or as a server cluster composed of multiple servers. The above-mentioned server 120 can be implemented as a physical server or as a cloud server, which is not limited in the embodiment of the present application.

[0043] In conjunction with the introduction of the above application scenarios and implementation environments, the entity positioning method involved in the embodiments of the present application is described. Figure 2 This is a flow chart of an entity positioning method provided by an exemplary embodiment of the present application. The method can be executed by a terminal or a server. In the embodiment of the present application, the method is described in terms of its application to a server. Figure 3 As shown, the method includes:

[0044] Step 201: Acquire personnel entity data, equipment entity data, and space entity data.

[0045] Personnel entity data is used to indicate the personnel information and personnel structure corresponding to all personnel entities in the smart building. The personnel information includes the name, gender, position, department, and other information of all personnel. Optionally, the personnel information of all personnel in the smart building is stored in the personnel information table, and the personnel information can be queried later by typing keywords. The personnel structure is used to indicate the internal relationship between personnel entities in the smart building. The internal relationship can be expressed as a superior-subordinate relationship. The superior-subordinate relationship can be determined by position information, or it can be determined based on the superior-subordinate relationship and the department information of the personnel, and implemented as a management relationship. However, whether it is a superior-subordinate relationship or a management relationship, the relationship between personnel can be represented in the form of a binary tuple, or in the form of other tuples or tree structures. This application does not limit this. For example, the smart building includes personnel A, personnel B, personnel C, and personnel D. Personnel A to personnel D all belong to the administrative department, and personnel A is the superior of personnel B, personnel C, and personnel D. The final personnel structure can be realized as (personnel A, personnel B), (personnel A, personnel C), and (personnel A, personnel D), which is used to indicate that personnel A is the superior of personnel B, personnel C, and personnel D who belong to the same department.

[0046] Optionally, the operation and maintenance personnel collect the personnel information corresponding to all personnel entities in the smart building and store all the personnel information in the digital twin database. Optionally, the server can build a personnel twin subsystem in the digital twin database based on all the personnel information. The personnel twin subsystem stores the personnel information and personnel structure corresponding to all personnel entities. The personnel structure can be determined by the position, department, and actual personnel structure in the personnel information. This application does not limit this.

[0047] Optionally, operations personnel can collect personnel information corresponding to all personnel entities in the following ways:

[0048] First, the collected personnel information is sent to all personnel in the smart building in the form of a link. The link can be pushed by department or individual. Personnel in the smart building complete the completion of their personal information by clicking on the link. The operation and maintenance personnel build personnel entity data based on the content in the link. The personnel entity data can be implemented as an independent personnel twin subsystem.

[0049] Second, the personnel information is entered through the information collection platform / system. The personnel in the smart building log in to the platform / system and enter their corresponding personnel information in the corresponding personnel information collection module.

[0050] Third, through quick applications / applications, all personnel in the smart building can click on the quick application for collecting personnel information or install the application for collecting personnel information, and complete their corresponding personnel information in the corresponding interface of the application.

[0051] Device entity data is used to indicate the device information and device structure within a smart building. The device information includes the names, functions, and information about the personnel who manage the device. The device structure indicates the hierarchical relationship between device entities. This hierarchical relationship can be implemented as an upstream-downstream relationship. This upstream-downstream relationship can be reflected on the same device entity or between different device entities. This is not limited in this application. When a device entity fails, some upstream device entities fail because of a failure in a downstream device entity related to the device entity. The device structure is stored in the device entity data, and the source of the failure can be screened based on the device structure to ultimately determine the device entity that is the source of the failure.

[0052] Optionally, the operation and maintenance personnel uniformly enter the device information corresponding to all device entities in the smart building and the upstream and downstream relationships between the device entities, and store the device information and the upstream and downstream relationships between the device entities in the digital twin database. Optionally, the server can build a device twin subsystem in the digital twin database based on the device information and the upstream and downstream relationships between the device entities.

[0053] Spatial entity data is used to indicate the spatial distribution within a smart building. The spatial distribution can reflect the inclusion relationship between spatial entities. In an embodiment of the present application, the equipment entity can be operated based on the personnel entity, and then the spatial entity can be spatially converged to finally determine the specific position of the personnel entity in the spatial entity.

[0054] Optionally, the digital twin database stores the entire spatial distribution within the smart building, and the operation and maintenance personnel upload the corresponding inclusion relationships between each spatial entity to the digital twin database for storage. It can be stored in the digital twin database in the form of tuples / multiples / tree structure diagrams / topological structure diagrams. For example, the operation and maintenance personnel upload the spatial inclusion relationships corresponding to the porch, laboratory, office area and leisure area, where the laboratory contains the porch, and the office area contains the laboratory. The operation and maintenance personnel upload the corresponding information of (porch, laboratory) and (laboratory, office area), and determine the spatial entity data based on the information. The spatial entity data can be implemented as a spatial twin subsystem in the digital twin subsystem.

[0055] In an embodiment of the present application, the server obtains personnel entity data, device entity data, and space entity data from the digital twin database, obtains personnel entity data from the personnel twin subsystem, obtains device entity data from the device twin subsystem, and obtains space entity data from the space twin subsystem.

[0056] Step 202: construct a relationship graph based on the personnel entity data, the equipment entity data, and the space entity data. The relationship graph includes a first relationship graph, a second relationship graph, and a third relationship graph.

[0057] Optionally, the first relationship diagram in the relationship diagram is used to represent the allocation relationship between personnel entity data and device entity data, the second relationship diagram is used to represent the positional relationship between personnel entity data and spatial entity data, and the third relationship diagram is used to represent the positional relationship between device entity data and spatial entity data.

[0058] For details, please see Figure 3 , Figure 3 A schematic diagram of a relationship diagram provided in an embodiment of the present application is shown, which includes an inclusion relationship within spatial entity data, a management relationship within personnel entity data, and an upstream and downstream relationship within device entity data. It also includes an allocation relationship between personnel entity data and device entity data, a first position relationship between personnel entity data and spatial entity data, and a second position relationship between device entity data and spatial entity data. The allocation relationship is specifically reflected in that the personnel entity operates (Operate in) the device entity, and the device entity is allocated (Allocated by) to the personnel entity; the first position relationship is specifically implemented as the personnel entity is located (Located in) in the spatial entity, and the spatial entity is occupied (Occupied by) by the personnel entity; the second position relationship is specifically implemented as the device entity is located (Located in) in the spatial entity, and the spatial entity is served (Served by) by the personnel entity. By) equipment entity, in this embodiment, the expression [Entity 1 <- (Handle) -> Entity 2] is used to represent the relationship between Entity 1 and Entity 2, Entity 1 and Entity 2 are any one of Personnel Entity, Equipment Entity and Space Entity, Handle is expressed as any one of Containment Relationship, Management Relationship, Upstream and Downstream Relationship, Located, Acted, Occupied, Assigned, and Operation, for example, Personnel-(Operation) -> Equipment, Equipment-(Assigned to) -> Personnel, Personnel-(Located) -> Space, Space-(Occupied to) -> Personnel, Equipment <-(Upstream and Downstream) -> Equipment, Space <-(Contains) -> Space, Personnel <-(Management) -> Personnel, etc., specifically Figure 1The relationship diagram in the figure represents the relationship between entity 1 and entity 2. In addition, the entity expression [entity 1 <- (Handle) -> entity 2] can also be used to indicate that entity 1 has a relationship to entity 2, and entity 2 also has a relationship pointing to entity 1. For example, the fan coil unit (FCU) panel is located in porch A, and conference room 1 is served by FCU 2.

[0059] The above relationship graph can also be described using a Resource Description Framework (RDF) graphical database, where nodes represent entities and directed lines represent relationships between entities.

[0060] Optionally, the server stores the relationship diagram in the digital twin database. If there is a change in the internal relationship or external association relationship of the personnel entity, equipment entity, or space entity, the relationship between the entities (any one of the personnel entity, equipment entity, or space entity) in the digital twin database is updated periodically.

[0061] Step 203: Implement the positioning function based on the relationship graph.

[0062] Optionally, the person entity may be directly located based on the established relationship graph. For a specific location process, please refer to the content of the following embodiment, which will not be described in detail here.

[0063] Optionally, based on the hierarchical relationship within the device entity data in the established relationship diagram, the faulty device entities that repeatedly issue alarm information can be removed, and finally the fault source device can be accurately located, and the fault source device information can be sent to the account corresponding to the designated personnel entity, prompting the personnel entity to repair the fault source device. For the specific process of locating the fault source device, please refer to the contents of the following embodiment, which will not be described in detail here.

[0064] It is worth noting that the entity positioning method provided in the embodiment of the present application can also be applied to other fields, and used in scenarios of positioning human entities and device entities, which is not limited in the present application.

[0065] To sum up, the entity positioning method provided in the embodiment of the present application associates personnel entities, equipment entities and space entities through the relationships among personnel entities, equipment entities and space entities, constructs a relationship diagram between each of them, and subsequently completes the positioning of the target entity through the relationship diagram, avoiding the related technology that only focuses on the positional relationship between equipment entities and space entities, while ignoring the connection between personnel entities and space entities and equipment entities inside the building, effectively improving the utilization rate of information. When using the relationship diagram for positioning, the content of personnel entities using a certain equipment entity in a certain space entity can be obtained in time, thereby improving the positioning efficiency of the target entity.

[0066] With the widespread adoption of mobile and intelligent devices within intelligent buildings, the spatial location of human entities within these buildings has become crucial information. Based on the location of human entities, we can determine which device entities are operational and which spatial entities (spatial regions) they affect. We can also determine the specific spatial entity (spatial region) where the human entity is located based on whether the device entity is triggered. The collection of human entity location data is often driven by specific business needs. A single positioning technology cannot effectively combine the data of device entities and spatial entities within intelligent buildings with the data of human entities to obtain specific location data.

[0067] Therefore, the embodiment of the present application can also use the entity positioning method provided in the embodiment of the present application to locate the target person, build a relationship graph based on the person entity data, device entity data and space entity data, and converge the spatial area corresponding to the device entity triggered by the person entity according to the relationship graph, thereby obtaining the final spatial result (position result). For details, please refer to Figure 4 , Figure 4 This is a flowchart of locating a target person provided by an exemplary embodiment of the present application. The method can be applied to a terminal or a server. The present application is described by applying it to a server. Figure 4 As shown, the method includes:

[0068] Step 401: Receive a feedback sequence.

[0069] From the above embodiments, it can be concluded that the relationship between the device entity and the space entity is stored in the relationship diagram. The device entity is located in the space entity and affects the area corresponding to the space entity. For example, taking a company as an example, a lobby access control (device entity) is generally set up when entering the company. The lobby access control corresponds to the entire area of the company. It can also be understood that when a personnel entity operates the lobby access control to complete the clocking in or face scanning to enter the company, it means that the personnel entity is located in the company. When the personnel entity goes to the office area to clock in, the position corresponding to the personnel entity converges from the entire company area to the office area.

[0070] Optionally, the target person operates different device entities in the intelligent building, and the device entities operated by the target person send feedback information to the server in sequence, where the feedback information is used to indicate that the target person has triggered the device entity.

[0071] The server receives feedback information uploaded by the device entity in sequence, where the device entity is the device entity operated in sequence by the target person; optionally, the server generates a unique feedback information sequence corresponding to the target person based on the feedback information uploaded by the device entity, where the feedback information sequence stores the order of the device entities operated by the target person in chronological order.

[0072] Step 402: Based on the feedback sequence, determine the spatial entity sequence corresponding to the sequence of the target person operating the device entity through the relationship diagram.

[0073] Optionally, the server determines the spatial entity (spatial area) corresponding to each device that uploads feedback information in turn based on the positional relationship between the device entity and the spatial entity represented by the second relationship graph in the constructed relationship graph, and determines the spatial entity sequence corresponding to the target person based on the feedback information sequence and the spatial entity corresponding to the device entity.

[0074] Optionally, the server may store the spatial entity sequence in the personnel entity data, and may determine the active area, effective working hours, etc. of the target person based on the spatial entity sequence of the target person within a specified time period.

[0075] Step 403: Position the target person based on the spatial entity sequence.

[0076] Optionally, the server receives a positioning request for the target person, determines a sequence of device entities operated by the target person in chronological order according to the positioning request, and determines a sequence of spatial entities corresponding to the target person based on a second relationship graph in the relationship graph.

[0077] The server determines the spatial entity (spatial area) where the target person is located based on the spatial entity sequence, and generates a positioning result corresponding to the target person.

[0078] The server can feed back any one of the device entity sequence, space entity sequence or positioning result corresponding to the target person to the terminal.

[0079] In the above process, the relationship diagram is stored in the digital twin database for explanation. For details, please refer to Figure 5 , Figure 5 is based on Figure 4 The flowchart of the embodiment shown provides a flow chart of the person entity positioning, which is described by applying the method to the server. Figure 5 As shown, the method includes:

[0080] Step 501: determine in sequence whether the device entity has any feedback results.

[0081] Optionally, when the device entity receives an operation corresponding to a human entity, the device entity responds to the operation, determines the human entity corresponding to the operation, and uploads the feedback result corresponding to the human entity to the server. The device can be implemented as access control, face PAD, Bluetooth positioning, etc.

[0082] This step is the same as the process of step 401 and will not be repeated here.

[0083] Step 502: Obtain the space corresponding to the device entity from the digital twin database.

[0084] A relationship diagram is stored in the digital twin database, which includes personnel entity data, space entity data, equipment entity data, a first relationship diagram, a second relationship diagram, and a third relationship diagram. The space corresponding to the equipment entity that sends the feedback result is determined based on the second relationship diagram.

[0085] This step is the same as the process of step 402 and will not be repeated here.

[0086] Step 503: Write the space group sequence.

[0087] The spaces corresponding to the device entities sending the feedback results are written into the space group sequence (space1, space2, space3, ...) in chronological order.

[0088] This step is the same as the process of step 402 and will not be repeated here.

[0089] Step 504: Analyze the space-space relationship from the digital twin database to obtain the final space result.

[0090] Based on the spatial group sequence corresponding to the target person, the server analyzes the spatial entity data (used to characterize the inclusion relationship between spatial entities) from the digital twin database to obtain the final spatial result. The spatial result can be the result corresponding to the smallest spatial area in the spatial group sequence, or it can be the spatial entity corresponding to the device entity most recently operated by the target person. This application does not limit this.

[0091] For illustration, see Figure 6 The spatial convergence diagram shown in Figure 5The entire spatial distribution of the smart building shown is used to locate human entities. The smart building is equipped with facial recognition (access control machine) 601, card access control machine 602 and conference room face PAD 603. All devices in the smart building are embedded with Bluetooth positioning modules. When the target person operates the Bluetooth positioning device 604, the device 604 sends feedback results to the server. The server performs Bluetooth positioning on the Bluetooth positioning device 604 based on the feedback results and obtains the spatial area or specific location area corresponding to the Bluetooth positioning device 604. The target person first triggers the office building face recognition access control machine 601, and the face recognition access control machine 601 sends the feedback result to the server. The server writes the spatial entity corresponding to the face recognition access control machine 601 into the spatial group sequence (company). The spatial group sequence (company) first recognizes and converges to the action area 1. Before no other device uploads the feedback result, the target person can be located at any position within the action area 1. Subsequently, the target person triggers the card access control machine 602, and the card access control machine 602 sends the feedback result to the server. The server writes the spatial entity corresponding to the card access control machine 602 into the spatial group sequence (company, office area). The recognition area of the spatial group sequence (company, office area) further converges to the action area 2. Before no other device in the office area uploads the feedback result, the target person can be located at any position within the action area 2; subsequently, the target person triggers the conference room face PAD 603, and the conference room face PAD 603 feedbacks the result When sent to the server, the server writes the spatial entity corresponding to the conference room face PAD603 into the spatial group sequence (company, office area, office A), and the recognition area of the spatial group sequence (company, office area, office A) further converges to the action area 3. Before other devices in office A upload feedback results, the target person can be located at any position within the action area 3; when the target person subsequently uses the Bluetooth positioning device 604, the Bluetooth positioning device 604 sends the feedback result to the server, and the server writes the spatial entity corresponding to the Bluetooth positioning device 604 into the spatial group sequence (company, office area, office A, device A). The recognition area of the spatial group sequence (company, office area, office A, device A) further converges to the action area 4, and finally determines that the target person is at the position corresponding to device A. The server feeds back the convergence result (target person, device A) to the terminal, and the convergence result is used to indicate that the target person is at the position corresponding to device A.

[0092] Optionally, the convergence process of the above-mentioned identification area can also be performed based on other traffic data to achieve a solution of gradually narrowing the location range of the target person.

[0093] To sum up, the entity positioning method provided in the embodiment of the present application associates personnel entities, equipment entities and space entities through the relationships among personnel entities, equipment entities and space entities, constructs a relationship diagram between each of them, and subsequently completes the positioning of the target entity through the relationship diagram, avoiding the related technology that only focuses on the positional relationship between equipment entities and space entities, while ignoring the connection between personnel entities and space entities and equipment entities inside the building, effectively improving the utilization rate of information. When using the relationship diagram for positioning, the content of personnel entities using a certain equipment entity in a certain space entity can be obtained in time, thereby improving the positioning efficiency of the target entity.

[0094] In an embodiment of the present application, the corresponding space group sequence is obtained by the information fed back by the device entity after the human entity triggers the device entity. The space group sequence is the spatial convergence order corresponding to the human entity, and the spatial area corresponding to the human entity in the space group sequence is finally determined, thereby solving the problem that the human entity cannot be positioned inside the building and improving the efficiency of human entity positioning.

[0095] In the embodiment of the present application, when the target entity includes a target device, the relationship diagram constructed in the above embodiment can also be used to locate the faulty device. For details, see Figure 7 , Figure 7 This is a flowchart of a target device positioning method provided by an exemplary embodiment of the present application. The method can be applied to a terminal or a server. The present application is described in detail by applying the method to a server. Figure 7 As shown, the method includes:

[0096] Step 701: Receive alarm information uploaded by the target device.

[0097] All devices in the smart building are managed by the operation and maintenance personnel, or the devices are divided into areas and assigned to different personnel entities for management. This application does not limit this. When a device fails, an alarm message is sent to the server. For example, see Figure 8 The schematic diagram of the device sending an alarm message shown in the figure includes device A, device B, device C and device D in the device cluster 801. Device A sends an alarm message 802, device B sends an alarm message 803, device C sends an alarm message 804, and device D sends an alarm message 805. The server determines a first faulty device list based on the alarm information, and the first faulty device list includes at least one target device that sends the alarm message.

[0098] Step 702: Determine the fault source device corresponding to the target device based on the alarm information and the relationship diagram.

[0099] The server stores device entity data, which includes the hierarchical relationship between devices. The hierarchical relationship is represented by upstream and downstream relationships. Figure 8 For illustration, device C is the upstream device of device B, device B is the upstream device of device A, and device D is a separate device with no downstream device or upstream device corresponding to it.

[0100] In this embodiment, when a target device fails, a chain reaction may cause the upstream device corresponding to the target device to also fail. For example, Figure 8 In this example, when device A experiences a power outage, the outage directly affects its upstream devices B and C, causing power outages. In related technologies, the server needs to send fault information corresponding to devices A, B, and C to the management staff, who then repairs devices A, B, and C. However, the faults in devices B and C are actually caused by device A. Therefore, it is only necessary to identify the source device (device A) that caused the fault, remove the alarm information from devices B and C, and send only the fault information corresponding to device A to the management staff for repair.

[0101] Optionally, the server removes faulty devices that repeatedly issue alarm information from the first faulty device list based on the hierarchical relationship corresponding to the device entity data in the relationship diagram, and obtains a second faulty device list. Optionally, the second faulty device list includes all fault source devices that cause the fault.

[0102] For example Figure 8 Device cluster 801 includes devices A, B, C, and D. Alarm 1 is captured, corresponding to fault X on device A (fault X is included in alarm information 802). Alarm 2 is captured, corresponding to fault Y on device B (fault Y is included in alarm information 802). Fault Y is caused by fault X on device A. In this case, device A is actually the fault source device. The server removes alarm 2 sent by device B and only retains fault X corresponding to device A.

[0103] Step 703: Determine the person entity corresponding to the fault source device based on the relationship graph.

[0104] The relationship graph stored in the server includes a first relationship graph, and a personnel entity corresponding to the fault source device is determined according to the first relationship graph. The personnel entity is used to represent a person who manages the fault source device.

[0105] Step 704: Send an alarm to the account corresponding to the person entity.

[0106] Optionally, the server can determine a personnel list based on the personnel structure between personnel entity data and the management relationship between equipment entities and personnel entities. The personnel list is used to represent at least one person who manages the fault source equipment. The personnel list can be determined based on the personnel structure. For example, the fault source equipment is managed by personnel A, personnel A is managed by personnel C, and personnel C is managed by personnel D. The server obtains the personnel list (personnel A, personnel B, personnel C, personnel D) based on the relationship; or the fault source equipment is managed by personnel A, and personnel B, personnel C and personnel A are all personnel used to repair faults, and personnel D is the superior of personnel A, personnel B, and personnel C. The server obtains the personnel list [personnel A, (personnel B, personnel C), personnel D] based on the relationship.

[0107] Optionally, within a specified time period, if the fault source device is not repaired, the server sends an alarm prompt to the corresponding accounts of the personnel in the personnel list in sequence based on the personnel list, and the personnel repair the fault source device according to the alarm prompt.

[0108] In the above process, the relationship diagram is stored in the digital twin database for explanation. For details, please refer to Figure 9 , Figure 9 is based on Figure 7 The flowchart of the device entity positioning provided in the embodiment shown is explained by applying the method to a server. Figure 9 As shown, the method includes:

[0109] Step 901: A fault is detected (alarm a, alarm b, ..., alarm n).

[0110] The server receives alarm information (alarm a, alarm b, . . . , alarm n) sent by the device where the fault occurs, and generates a first fault list based on the alarm information.

[0111] This step is the same as the process of step 701 and will not be repeated here.

[0112] Step 902: Locate each device that has issued a fault alarm.

[0113] The server determines the device from the digital twin database based on the fault alarm information.

[0114] This step is the same as the process of step 701 and will not be repeated here.

[0115] Step 903: Analyze the root cause of the fault from the digital twin database.

[0116] Optionally, the server obtains information about the device that issued the alarm from the digital twin database, and analyzes the cause of the fault based on the hierarchical relationship between the devices in the device entity data.

[0117] This step is the same as the process of step 702 and will not be repeated here.

[0118] Step 904: Remove duplicate alarms.

[0119] Based on the analysis result in step 903, the devices that repeatedly issue alarm information are eliminated to determine the fault source device that caused the fault.

[0120] This step is the same as the process of step 702 and will not be repeated here.

[0121] Step 905: Push the alarm to the relevant manager based on the relationship between the alarm device and the person to whom it belongs.

[0122] The relationship graph stored in the server includes a first relationship graph, and a personnel entity corresponding to the fault source device is determined according to the first relationship graph. The personnel entity is used to represent a person who manages the fault source device.

[0123] Optionally, the server can determine a personnel list based on the personnel structure between personnel entity data and the management relationship between the device entity and the personnel entity. The personnel list is used to represent at least one person who manages the fault source device. The personnel list can be determined based on the personnel structure.

[0124] This step is the same as the process of step 703 and step 704, and will not be repeated here.

[0125] To sum up, the entity positioning method provided in the embodiment of the present application associates personnel entities, equipment entities and space entities through the relationships among personnel entities, equipment entities and space entities, constructs a relationship diagram between each of them, and subsequently completes the positioning of the target entity through the relationship diagram, avoiding the related technology that only focuses on the positional relationship between equipment entities and space entities, while ignoring the connection between personnel entities and space entities and equipment entities inside the building, effectively improving the utilization rate of information. When using the relationship diagram for positioning, the content of personnel entities using a certain equipment entity in a certain space entity can be obtained in time, thereby improving the positioning efficiency of the target entity.

[0126] In an embodiment of the present application, when multiple equipment entities fail and issue alarm information, the equipment entity data in the relationship diagram is analyzed and the equipment entities that repeatedly issue alarm information are eliminated, and the fault source equipment that caused the failure is finally determined. The personnel entity corresponding to the fault source equipment is sent an alarm prompt according to the first relationship diagram in the relationship diagram, thereby shortening the RTO and improving the efficiency of locating the faulty equipment. In the case where the failure of the fault source equipment causes other equipment entities to also fail, it can effectively troubleshoot and eliminate duplicate alarms, thereby improving the efficiency of fault investigation.

[0127] Figure 10This is a structural block diagram of an entity positioning device provided by an exemplary embodiment of the present application. Figure 10 As shown, the device includes: an acquisition module 1010, a construction module 1020 and a positioning module 1030;

[0128] An acquisition module 1010 is configured to acquire personnel entity data, equipment entity data, and space entity data, wherein the personnel entity data includes personnel structure, the equipment entity data includes equipment structure, and the space entity data includes space distribution;

[0129] A construction module 1020 is configured to construct a relationship graph based on the person entity data, the device entity data, and the space entity data, wherein the relationship graph includes a first relationship graph, a second relationship graph, and a third relationship graph, wherein the first relationship graph is used to indicate an allocation relationship between the person entity data and the device entity data, the second relationship graph is used to indicate a positional relationship between the person entity data and the space entity data, and the third relationship graph is used to indicate a positional relationship between the device entity data and the space entity data;

[0130] The positioning module 1030 is configured to implement a positioning function based on the relationship graph, wherein the positioning function is used to locate the target entity.

[0131] To sum up, the entity positioning device provided in the embodiment of the present application associates personnel entities, equipment entities and space entities through the relationship between personnel entities, equipment entities and space entities, constructs a relationship diagram between each of them, and subsequently completes the positioning of the target entity through the relationship diagram, avoiding the related technology that only focuses on the positional relationship between equipment entities and space entities, while ignoring the connection between personnel entities and space entities and equipment entities inside the building, effectively improving the utilization rate of information, and when using the relationship diagram for positioning, it is possible to timely obtain the content of a personnel entity using a certain equipment entity in a certain space entity, thereby improving the positioning efficiency of the target entity.

[0132] Figure 11 is a structural block diagram of an entity positioning device provided by another exemplary embodiment of the present application, wherein when the target entity includes a target person, such as Figure 11 As shown, the device further includes:

[0133] The receiving module 1040 is configured to receive a feedback information sequence, where the feedback information sequence is used to indicate a sequence in which the target person operates a device entity;

[0134] A determination module 1050 is configured to determine, based on the feedback information sequence and through the relationship graph, a spatial entity sequence corresponding to a sequence of device entities operated by the target person;

[0135] The positioning module 1030 is further configured to locate the target person based on the spatial entity sequence.

[0136] In an optional embodiment, if Figure 11 As shown, the device further includes:

[0137] The receiving module 1040 is further configured to sequentially receive feedback information uploaded by device entities, where the device entities are sequentially operated by the target personnel;

[0138] The generating module 1060 is configured to generate the feedback information sequence based on the feedback information received in sequence.

[0139] In an optional embodiment, if Figure 11 As shown, the determination module 1050 is further used to sequentially determine the spatial entities corresponding to the device entities corresponding to the feedback information in the relationship diagram; and determine the spatial entity sequence corresponding to the spatial entity based on the order of the feedback information sequence.

[0140] To sum up, the entity positioning device provided in the embodiment of the present application associates personnel entities, equipment entities and space entities through the relationship between personnel entities, equipment entities and space entities, constructs a relationship diagram between each of them, and subsequently completes the positioning of the target entity through the relationship diagram, avoiding the related technology that only focuses on the positional relationship between equipment entities and space entities, while ignoring the connection between personnel entities and space entities and equipment entities inside the building, effectively improving the utilization rate of information, and when using the relationship diagram for positioning, it is possible to timely obtain the content of a personnel entity using a certain equipment entity in a certain space entity, thereby improving the positioning efficiency of the target entity.

[0141] In this embodiment, in the embodiment of the present application, the corresponding space group sequence is obtained by the information fed back by the device entity after the human entity triggers the device entity. The space group sequence is the spatial convergence order corresponding to the human entity, and the spatial area corresponding to the human entity in the space group sequence is finally determined, thereby solving the problem that the human entity cannot be accurately positioned inside the building and improving the efficiency of human entity positioning.

[0142] Figure 12 is a structural block diagram of an entity positioning device provided by another exemplary embodiment of the present application, wherein when the target entity includes a target device, such as Figure 12 As shown, the device further includes:

[0143] The receiving module 1040 is further configured to receive alarm information uploaded by the target device, where the alarm information indicates an operational failure of the target device;

[0144] The determining module 1050 is further configured to determine a fault source device corresponding to the target device based on the alarm information and the relationship diagram;

[0145] The determining module 1050 is further configured to determine a person entity corresponding to the fault source device based on the relationship diagram;

[0146] The sending module 1070 is used to send an alarm prompt to the account corresponding to the person entity.

[0147] In an optional embodiment, the relationship diagram further includes a hierarchical relationship between device entities, and the determination module 1050 is further configured to determine the fault source device corresponding to the target device based on the hierarchical relationship between the device entities.

[0148] In an optional embodiment, the determining module 1050 is further configured to determine a first faulty device list based on the alarm information, where the first faulty device list includes at least one target device that issues the alarm information;

[0149] The determining module 1050 is further configured to remove the faulty devices that repeatedly send alarm information from the first faulty device list based on the relationship diagram, and obtain a second faulty device list;

[0150] The determining module 1050 is further configured to determine the fault source device corresponding to the target device based on the second faulty device list.

[0151] To sum up, the entity positioning device provided in the embodiment of the present application associates personnel entities, equipment entities and space entities through the relationship between personnel entities, equipment entities and space entities, constructs a relationship diagram between each of them, and subsequently completes the positioning of the target entity through the relationship diagram, avoiding the related technology that only focuses on the positional relationship between equipment entities and space entities, while ignoring the connection between personnel entities and space entities and equipment entities inside the building, effectively improving the utilization rate of information, and when using the relationship diagram for positioning, it is possible to timely obtain the content of a personnel entity using a certain equipment entity in a certain space entity, thereby improving the positioning efficiency of the target entity.

[0152] In an embodiment of the present application, when multiple equipment entities fail and issue alarm information, the equipment entity data in the relationship diagram is analyzed and the equipment entities that repeatedly issue alarm information are eliminated, and the fault source equipment that caused the failure is finally determined. The personnel entity corresponding to the fault source equipment is sent an alarm prompt according to the first relationship diagram in the relationship diagram, thereby shortening the RTO and improving the efficiency of locating the faulty equipment. In the case where the failure of the fault source equipment causes other equipment entities to also fail, it can effectively troubleshoot and eliminate duplicate alarms, thereby improving the efficiency of fault investigation.

[0153] It should be noted that the entity locating device provided in the above embodiment is merely an example of the division of the aforementioned functional modules. In actual applications, the aforementioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the entity locating device provided in the above embodiment and the entity locating method embodiment are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0154] It can be understood that in the specific implementation of this application, related data such as human entity data, device entity data, and personnel entity data are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use, and processing of relevant data must comply with relevant laws, regulations, and standards of relevant countries and regions.

[0155] Figure 13 A schematic diagram of the structure of a server provided by an exemplary embodiment of the present application is shown. The server may be Figure 1 Specifically:

[0156] The server 120 includes a central processing unit (CPU) 1301, a system memory 1304 including a random access memory (RAM) 1302 and a read-only memory (ROM) 1303, and a system bus 1305 connecting the system memory 1304 and the CPU 1301. The server 120 also includes a basic input / output system (I / O system) 1306 that facilitates information transfer between various components within the computer, and a mass storage device 1307 for storing an operating system 1313, application programs 1314, and other program modules 1315.

[0157] The basic input / output system 1306 includes a display 1308 for displaying information and an input device 1309, such as a mouse and keyboard, for user input. Both the display 1308 and the input device 1309 are connected to the central processing unit 1301 via an input / output controller 1310 connected to the system bus 1305. The basic input / output system 1306 may also include an input / output controller 1310 for receiving and processing input from a variety of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1310 also provides output to a display screen, printer, or other types of output devices.

[0158] The mass storage device 1307 is connected to the central processing unit 1301 through a mass storage controller (not shown) connected to the system bus 1305. The mass storage device 1307 and its associated computer-readable media provide non-volatile storage for the server 120. In other words, the mass storage device 1307 may include computer-readable media (not shown) such as a hard disk or a compact disc read-only memory (CD-ROM) drive.

[0159] Without loss of generality, computer-readable media may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include RAM, ROM, Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other solid-state storage devices, CD-ROM, Digital Versatile Disc (DVD) or other optical storage, tape cassettes, magnetic tape, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that computer storage media are not limited to the above. The above-mentioned system memory 1304 and mass storage device 1307 can be collectively referred to as memory.

[0160] According to various embodiments of the present application, the server 120 may also be connected to a remote computer on a network such as the Internet for operation. That is, the server 120 may be connected to the network 1312 via the network interface unit 1311 connected to the system bus 1305, or the network interface unit 1311 may be used to connect to other types of networks or remote computer systems (not shown).

[0161] The memory also includes one or more programs, which are stored in the memory and configured to be executed by the CPU.

[0162] An embodiment of the present application also provides a computer device, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the entity positioning method provided by the above-mentioned method embodiments.

[0163] An embodiment of the present application also provides a computer-readable storage medium, which stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor to implement the entity positioning method provided by the above-mentioned method embodiments.

[0164] Optionally, the computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a solid-state drive (SSD), a regular hard disk, or an optical disk. Among them, the random access memory may include a resistance random access memory (ReRAM) and a dynamic random access memory (DRAM). The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0165] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

[0166] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for locating an entity, characterized in that: The method comprises: Acquire personnel entity data, equipment entity data, and space entity data, wherein the personnel entity data includes personnel structure, the equipment entity data includes equipment structure, and the space entity data includes space distribution; constructing a relationship graph based on the person entity data, the device entity data, and the space entity data, wherein the relationship graph includes a first relationship graph, a second relationship graph, and a third relationship graph, wherein the first relationship graph is used to indicate an allocation relationship between the person entity data and the device entity data, the second relationship graph is used to indicate a positional relationship between the person entity data and the space entity data, and the third relationship graph is used to indicate a positional relationship between the device entity data and the space entity data; Implementing a positioning function based on the relationship graph, wherein the positioning function is used to locate the target entity; Wherein, in the case where the target entity includes a target person, a feedback information sequence is received, the feedback information sequence is a sequence composed of at least two feedback information for indicating that the target person operates a device entity, and the feedback information is used to indicate that the target person triggers the device entity; based on the feedback information sequence, a spatial entity sequence corresponding to the sequence of the target person operating the device entity is determined through the relationship graph; and the target person is positioned based on the spatial entity sequence.

2. The method according to claim 1, characterized in that The receiving feedback information sequence includes: receiving feedback information uploaded by device entities in sequence, wherein the device entities are device entities operated in sequence by the target personnel; The feedback information sequence is generated based on the feedback information received in sequence.

3. The method according to claim 2, characterized in that The determining, based on the feedback information sequence and through the relationship graph, a spatial entity sequence corresponding to a sequence of device entities operated by the target person includes: sequentially determining the spatial entities corresponding to the device entities corresponding to the feedback information in the relationship graph; The spatial entity sequence corresponding to the spatial entity is determined based on the order of the feedback information sequence.

4. The method according to claim 1, wherein The target entity includes a target device; The positioning function is implemented based on the relationship graph, and the positioning function is used to locate the target entity, including: receiving alarm information uploaded by the target device, wherein the alarm information is used to indicate an operating failure of the target device; Determine the fault source device corresponding to the target device based on the alarm information and the relationship diagram; Determine the person entity corresponding to the fault source device based on the relationship graph; Send an alert to the account corresponding to the person entity.

5. The method according to claim 4, characterized in that The relationship diagram also includes the hierarchical relationship between device entities; The determining the fault source device corresponding to the target device based on the alarm information and the relationship diagram includes: The fault source device corresponding to the target device is determined based on the hierarchical relationship between the device entities.

6. The method according to claim 5, characterized in that The determining the fault source device corresponding to the target device based on the hierarchical relationship between the device entities includes: Determine a first faulty device list based on the alarm information, where the first faulty device list includes at least one target device that issues the alarm information; Based on the relationship graph, remove the faulty devices that repeatedly send alarm information from the first faulty device list, and obtain a second faulty device list; Based on the second faulty device list, a faulty source device corresponding to the target device is determined.

7. A physical positioning device, characterized in that: The device comprises: An acquisition module, configured to acquire personnel entity data, equipment entity data, and space entity data, wherein the personnel entity data includes personnel structure, the equipment entity data includes equipment structure, and the space entity data includes space distribution; a construction module, configured to construct a relationship graph based on the person entity data, the device entity data, and the space entity data, wherein the relationship graph includes a first relationship graph, a second relationship graph, and a third relationship graph, wherein the first relationship graph is configured to indicate an allocation relationship between the person entity data and the device entity data, the second relationship graph is configured to indicate a positional relationship between the person entity data and the space entity data, and the third relationship graph is configured to indicate a positional relationship between the device entity data and the space entity data; A positioning module, configured to implement a positioning function based on the relationship graph, wherein the positioning function is used to locate a target entity; Wherein, in the case where the target entity includes a target person, a feedback information sequence is received, the feedback information sequence is a sequence composed of at least two feedback information for indicating that the target person operates a device entity, and the feedback information is used to indicate that the target person triggers the device entity; based on the feedback information sequence, a spatial entity sequence corresponding to the sequence of the target person operating the device entity is determined through the relationship graph; and the target person is positioned based on the spatial entity sequence.

8. A computer device, characterized in that: The computer device includes a processor and a memory, wherein the memory stores at least one program, and the at least one program is loaded and executed by the processor to implement the entity positioning method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that The storage medium stores at least one program, and the at least one program is loaded and executed by the processor to implement the entity positioning method according to any one of claims 1 to 6.

Images