Geographical area-oriented matter management method, device, equipment and storage medium

Abstract

The application provides a matter management method and device for a geographic area, equipment, a storage medium and a computer program product; the geographic area has a corresponding matter management unit, the geographic area is divided at least once to obtain at least two sub-areas, each sub-area corresponds to a sub-management unit, and the at least two sub-management units and the matter management unit constitute a management unit tree; the method comprises the following steps: receiving a target matter reported by a first object included in a target sub-management unit in the management unit tree; the target matter carries an object identifier of a management object corresponding to the target management unit; based on the object identifier of the management object, the target matter is sent to the management object; when a matter distribution request sent by the management object is received, the target matter is sent to a second object indicated by the matter distribution request, so that the second object processes the target matter; through the application, the rationalization management of matters in the geographic area can be realized, and the matter processing efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a method, apparatus, device, storage medium, and computer program product for managing matters in a geographical area. Background Technology

[0002] With the development of internet technology, online processing has gradually become the preferred method for handling matters within certain geographical areas. However, due to the multiple management levels and wide scope of these matters, the online processing involves numerous steps, complex data transmission paths, and low efficiency, for which no solution has yet been found in the relevant technologies. Summary of the Invention

[0003] This application provides a method, apparatus, device, storage medium, and computer program product for managing matters within a geographical area, which can achieve rational management of matters within a geographical area and improve the efficiency of matter processing.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a method for managing items in a geographical region. The geographical region has corresponding item management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. The method includes:

[0006] Receive the target item reported by the first object included in the target sub-management unit in the management unit tree;

[0007] The target item carries the object identifier of the management object corresponding to the target management unit, and the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit;

[0008] Based on the object identifier of the managed object, the target item is sent to the managed object;

[0009] When a task assignment request is received from the management object, the target task is sent to the second object indicated by the task assignment request, so that the second object can process the target task.

[0010] This application embodiment also provides a method for managing items in a geographical region, wherein the geographical region has corresponding item management units, the geographical region is divided at least once to obtain at least two sub-regions, each sub-region corresponds to a sub-management unit, and the at least two sub-units and the item management unit constitute a management unit tree; the method includes:

[0011] Present the task reporting interface, and present the reporting function items in the task reporting interface;

[0012] The reporting interface corresponds to the first object included in the target sub-management unit in the management unit tree;

[0013] Based on the aforementioned reporting interface, the input target item is received;

[0014] In response to a trigger operation for the reported function item, the target item is reported;

[0015] The target item carries the object identifier of the management object corresponding to the target management unit, and the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit;

[0016] The target item is used to send the target item to a second object for processing the target item via the management object.

[0017] This application embodiment also provides a device for managing items in a geographical region. The geographical region has corresponding item management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. The device includes:

[0018] The receiving module is used to receive target items reported by the first object included in the target sub-management unit in the management unit tree;

[0019] The target item carries the object identifier of the management object corresponding to the target management unit, and the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit;

[0020] The first sending module is used to send the target item to the managed object based on the object identifier of the managed object;

[0021] The second sending module is used to send the target item to the second object indicated by the item allocation request when it receives the item allocation request sent by the management object, so that the second object can process the target item.

[0022] In the above scheme, the receiving module is further configured to receive a creation request for the item management unit, wherein the creation request carries object identification information; in response to the creation request, based on the object identification information, the item management unit is created, and the object corresponding to the object identification information is determined to be the item management object of the item management unit.

[0023] In the above scheme, the receiving module is further configured to automatically create child nodes of the item management unit as the child management unit, with the item management unit as the parent node; wherein the number of child nodes is the same as the number of sub-regions.

[0024] In the above scheme, the receiving module is further configured to receive a child node creation request for any node in the management unit tree other than the item management unit; in response to the child node creation request, create a child node of the parent node as the sub-management unit, with the parent node as the parent node; wherein, the number of child nodes is the same as the number of target areas obtained by dividing the sub-regions corresponding to the node.

[0025] In the above scheme, the receiving module is further configured to receive a node editing request for any node in the management unit tree; wherein the node editing request carries editing information for the node, and the editing information includes at least one of: node association information, node object editing information, and node management object editing information; in response to the node editing request, the module performs corresponding editing operations on the node based on the editing information.

[0026] In the above scheme, the receiving module is further configured to receive a management object setting request for the target management unit; in response to the management object setting request, determine the target object indicated by the management object setting request as the management object corresponding to the target management unit; wherein the management object has the management authority of the target management unit.

[0027] In the above scheme, the receiving module is further configured to receive an object addition request for the target sub-management unit, the object addition request carrying the object identifier of the first object; in response to the object addition request, the first object is added to the target sub-management unit based on the object identifier of the first object.

[0028] In the above scheme, the receiving module is further configured to receive a reporting object setting request for the target sub-management unit, the reporting object setting request carrying the object identifier of the reporting object corresponding to the target sub-management unit; the object identifier of the reporting object is the node identifier corresponding to the target sub-management unit, or the node identifier corresponding to the parent node of the target sub-management unit; in response to the reporting object setting request, obtain the management object of the node corresponding to the object identifier of the reporting object in the management unit tree; set the management object of the node corresponding to the object identifier of the reporting object as the reporting object corresponding to the target sub-management unit; the receiving module is further configured to receive the target item reported by the first object included in the target sub-management unit in the management unit tree for the reporting object.

[0029] In the above scheme, the receiving module is further configured to receive an allocation object setting request for the managed object; wherein the allocation object setting request carries a unit identifier of a target unit, and the target unit is one of the management units included in the management unit tree and the target sub-management unit; in response to the allocation object setting request, based on the unit identifier, the objects included in the target unit are determined as candidate allocation objects corresponding to the managed object, and the candidate allocation objects include the second object; the receiving module is further configured to send the target item to the second object indicated by the item allocation request in the target unit when receiving an item allocation request sent by the managed object.

[0030] In the above scheme, the receiving module is further configured to receive a transfer object setting request for the second object; wherein, the transfer object setting request carries a unit identifier of the target unit, and the target unit is one of the management units included in the management unit tree and the target sub-management units; in response to the transfer object setting request, based on the unit identifier, the objects included in the target unit are determined as candidate transfer objects corresponding to the second object; wherein, the candidate transfer object is configured to receive the target matter transferred by the second object.

[0031] In the above scheme, the receiving module is further configured to receive a transfer request sent by the second object; in response to the transfer request, send the target item to the target object indicated by the transfer request among the candidate transfer objects, so that the target object can process the target item.

[0032] In the above scheme, the receiving module is further configured to receive a reporting message indicating that the target matter has been processed; and send a matter notification message to the target object to notify that the target matter has been processed; wherein the target object includes at least one of the first object and the management object.

[0033] In the above scheme, the receiving module is further configured to receive a notification message sent by the managed object, the notification message being used to instruct the expedited processing of the target matter; and to send the notification message to the second object.

[0034] This application embodiment also provides a device for managing items in a geographical region. The geographical region has corresponding item management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. The device includes:

[0035] The presentation module is used to present the event reporting interface and, within the event reporting interface, to present the reporting function items.

[0036] The reporting interface corresponds to the first object included in the target sub-management unit in the management unit tree;

[0037] The item receiving module is used to receive the input target item based on the item reporting interface;

[0038] The reporting module is used to report the target item in response to a trigger operation for the reporting function item;

[0039] The target item carries the object identifier of the management object corresponding to the target management unit, and the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit;

[0040] The target item is used to send the target item to a second object for processing the target item via the management object.

[0041] This application also provides an electronic device, including:

[0042] Memory, used to store executable instructions;

[0043] The processor, when executing executable instructions stored in the memory, implements the event management method for geographical regions provided in the embodiments of this application.

[0044] This application also provides a computer-readable storage medium storing executable instructions, which, when executed by a processor, implement the event management method for a geographical region provided in this application.

[0045] This application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the event management method for a geographic region provided in this application.

[0046] The embodiments of this application have the following beneficial effects:

[0047] For each geographical region, a corresponding item management unit is set up. By dividing the geographical region at least once, at least two sub-regions are obtained, and each sub-region is also set up with a corresponding sub-management unit. The at least two sub-management units and the item management unit together form a management unit tree.

[0048] Based on this, the first object included in the target sub-management unit in the management unit tree can report target matters to be handled. Since the target matter carries the object identifier of the management object corresponding to the target management unit, upon receiving the target matter, it can be sent to the management object of the target management unit based on the object identifier, so that the management object can allocate the target matter. Since the target management unit is one of the target sub-management unit and its parent node, the management object can be either the management object of the target sub-management unit or the management object of its parent node. When a matter allocation request is received from the management object, the target matter is sent to the second object indicated by the matter allocation request, so that the second object can process the target matter. That is, through the management unit tree composed of at least two sub-management units and the matter management unit, the reporting, allocation, and processing of target matters are realized. In this way, rational management of matters within a geographical area can be achieved, improving the efficiency of matter processing. Attached Figure Description

[0049] Figure 1 This is a schematic diagram of the architecture of a geographical area-specific event management system 100 provided in an embodiment of this application;

[0050] Figure 2 This is a schematic diagram of the structure of an electronic device 500 that implements a method for managing matters in a geographical region, as provided in an embodiment of this application.

[0051] Figure 3 This is a flowchart illustrating the method for managing matters in a geographical area provided in an embodiment of this application;

[0052] Figure 4 This is a schematic diagram of the management unit tree structure provided in the embodiments of this application;

[0053] Figure 5 This is a flowchart illustrating the method for managing matters in a geographical area provided in an embodiment of this application;

[0054] Figure 6This is a schematic diagram of the configuration of the management unit provided in an embodiment of this application;

[0055] Figure 7 This is a schematic diagram of the configuration process for the reporting object provided in the embodiments of this application;

[0056] Figure 8 This is a schematic diagram of the configuration process of the item allocation object provided in the embodiments of this application;

[0057] Figure 9 This is a schematic diagram of the configuration process of the item allocation object provided in the embodiments of this application;

[0058] Figure 10 This is a schematic diagram of the configuration of the management unit provided in an embodiment of this application;

[0059] Figure 11 This is a schematic diagram showing the reporting of matters provided in the embodiments of this application;

[0060] Figure 12 This is a schematic diagram showing the assignment of items provided in an embodiment of this application;

[0061] Figure 13 This is a schematic diagram illustrating the transfer of matters provided in the embodiments of this application;

[0062] Figure 14 This is a schematic diagram showing the reporting of matters provided in the embodiments of this application;

[0063] Figure 15 This is a flowchart illustrating the process of a management unit object reporting a matter, as provided in the embodiments of this application.

[0064] Figure 16 This is a schematic diagram of the process for ordinary objects in the area managed by the management unit provided in this application embodiment to report matters. Detailed Implementation

[0065] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0066] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0067] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0068] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0069] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0070] 1) Client: An application that runs in a terminal to provide various services, such as a client that supports event processing.

[0071] 2) In response to, used to indicate the conditions or states on which the operation performed depends. When the conditions or states on which it depends are met, one or more operations performed may be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0072] This application provides a method, apparatus, device, storage medium, and computer program product for managing matters within a geographical area, which can achieve rational management of matters within a geographical area and improve the efficiency of matter processing.

[0073] The following describes the implementation scenario of the event management method for geographical regions provided in the embodiments of this application. See also Figure 1 , Figure 1 This is a schematic diagram of the architecture of a matter management system 100 for a geographical region provided in an embodiment of this application. The geographical region has a corresponding matter management unit. The geographical region is divided into at least two sub-regions at least once. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the matter management unit constitute a management unit tree.

[0074] To support an exemplary application, terminals 400-1, 400-2, and 400-3 are connected to server 200 via network 300. Network 300 can be a wide area network (WAN), a local area network (LAN), or a combination of both, and data transmission is achieved using wireless or wired links. Terminal 400-1 corresponds to the first object included in the target sub-management unit, terminal 400-2 corresponds to the second object, and terminal 400-3 corresponds to the management object corresponding to the target management unit. The target management unit is one of the target sub-management units and its parent node.

[0075] Terminal 400-1 (which may be configured with a client that supports event processing) is used to receive the target event input by the first object included in the target sub-management unit in the management unit tree; in response to the reporting instruction for the target event, it reports the target event to server 200;

[0076] Server 200 is used to receive the target item reported by terminal 400-1 of the first object; obtain the object identifier of the managed object by parsing the target item; and send the target item to terminal 400-3 of the managed object based on the object identifier of the managed object.

[0077] Terminal 400-3 (which can be configured with a client that supports event processing) is used to receive the target event sent by server 200 and send an event allocation request for the target event to server 200.

[0078] Server 200 is also used to receive a task assignment request sent by a managed object and send the target task to the terminal 400-2 of the second object indicated by the task assignment request;

[0079] Terminal 400-2 (which may be configured with a client that supports event processing) is used to receive and display the target event sent by the server so that a second object can process the target event.

[0080] In some embodiments, the event management method for geographical regions provided in this application can be implemented by various electronic devices. For example, it can be implemented by a terminal alone, by a server alone, or by a terminal and a server working together.

[0081] In some embodiments, the electronic device for implementing geographical area-specific event management provided in this application can be various types of terminal devices or servers. The server (e.g., server 200) can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The terminal (e.g., terminal 400-1) can be a smartphone, tablet, laptop, desktop computer, intelligent voice interaction device (e.g., smart speaker), smart home appliance (e.g., smart TV), smartwatch, in-vehicle terminal, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, and this application does not impose any limitations on this.

[0082] In some embodiments, the terminal or server can implement the geographical area-specific event management method provided in this application by running a computer program. For example, the computer program can be a native program or software module in an operating system; it can be a native application (APP), i.e., a program that needs to be installed in the operating system to run; it can also be a mini-program, i.e., a program that only needs to be downloaded to a browser environment to run; or it can be a mini-program that can be embedded in any APP. In short, the above-mentioned computer program can be any form of application, module, or plugin.

[0083] In some embodiments, multiple servers can form a blockchain, with each server being a node on the blockchain. Information connections can exist between each node in the blockchain, allowing for information transmission between nodes. Furthermore, the data (e.g., target items) related to the geographical area-specific event management method provided in this application embodiment can be stored on the blockchain.

[0084] The following describes an electronic device that implements a method for managing matters targeting a geographical region, as provided in an embodiment of this application. See also... Figure 2 , Figure 2 This is a schematic diagram of the structure of an electronic device 500 implementing a method for managing matters targeting a geographical region, as provided in an embodiment of this application. The electronic device 500 is used as an example. Figure 1Taking the server shown as an example, the electronic device 500 implementing the event management method for a geographical area provided in this application embodiment includes: at least one processor 510, a memory 550, at least one network interface 520, and a user interface 530. The various components in the electronic device 500 are coupled together via a bus system 540. It is understood that the bus system 540 is used to realize the connection and communication between these components. In addition to a data bus, the bus system 540 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 2 The general labeled all buses as Bus System 540.

[0085] The processor 510 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0086] The memory 550 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 550 may optionally include one or more storage devices physically located away from the processor 510.

[0087] The memory 550 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 550 described in this application embodiment is intended to include any suitable type of memory.

[0088] In some embodiments, memory 550 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0089] Operating system 551 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0090] The network communication module 552 is used to reach other computing devices via one or more (wired or wireless) network interfaces 520, exemplary network interfaces 520 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc.

[0091] In some embodiments, the event management device for geographical regions provided in this application can be implemented in software. Figure 2 A geographic area-specific event management device 553 is shown stored in memory 550. It can be software in the form of programs and plug-ins, including the following software modules: receiving module 5531, first sending module 5532 and second sending module 5533. These modules are logically related and can therefore be arbitrarily combined or further divided according to the functions they implement. The functions of each module will be described below.

[0092] In other embodiments, the geographical area-specific event management device provided in this application can be implemented using a combination of hardware and software. As an example, the geographical area-specific event management device provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the geographical area-specific event management method provided in this application. For example, the hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0093] The following describes the method for managing matters related to a geographical region provided in the embodiments of this application. The geographical region has corresponding matter management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit, and the at least two sub-management units and the matter management unit constitute a management unit tree. In practical applications, a corresponding matter management unit is set up for the geographical region. This matter management unit is used to manage matters within the geographical region, such as matters pending to be handled by users within the geographical region. In the embodiments of this application, the geographical region can be further divided. This division can be done once or multiple times to obtain at least two sub-regions. In actual implementation, each division can be a uniform division to obtain sub-regions of the same size. After dividing the geographical region at least once to obtain at least two sub-regions, a corresponding sub-management unit is set up for each sub-region. Thus, the at least two sub-management units and the matter management unit constitute a management unit tree. In actual implementation, the matter management unit can be the root node of the management unit tree, and the at least two sub-management units can be leaf nodes of the management unit tree.

[0094] In some embodiments, the event management method for geographical regions provided in this application can be implemented by various electronic devices. For example, it can be implemented by a terminal alone, by a server alone, or by a terminal and a server working together. For example, see server implementation. Figure 3 , Figure 3 This is a flowchart illustrating a method for managing events in a geographic area according to an embodiment of this application. The method for managing events in a geographic area according to an embodiment of this application includes:

[0095] Step 101: The server receives the target item reported by the first object included in the target sub-management unit in the management unit tree.

[0096] The target item carries the object identifier of the management object corresponding to the target management unit, which is one of the target sub-management units and the parent node of the target sub-management units.

[0097] It should be noted that this matter management unit can exist in the form of an enterprise, institution, organization, etc., used to manage matters in the aforementioned geographical area.

[0098] Here, when the first object included in the target sub-management unit in the management unit tree needs to report a target matter, the first object can input the target matter on its personal terminal and trigger a reporting instruction for the target matter. When the terminal of the first object receives the input target matter and the reporting instruction for the target matter, it reports the target matter to the server. For example, the target matter could be "The sewer pipe in Room 101, Unit 2, XX Community needs repair".

[0099] In practical implementation, the terminal of the first object can be equipped with a client, such as a client that supports task processing. When the terminal of the first object runs this client, the first object can input the target task on the running client and trigger a reporting command for the target task, thereby causing the terminal of the first object to report the target task to the server. At the same time, the server can be the backend server of the client that supports task processing.

[0100] When the server receives a target item reported by the first object (i.e., the terminal receiving the target item), it can parse the target item to obtain the object identifier of the management object corresponding to the target management unit carried by the target item. This management object has the management permissions of the target management unit, such as managing the objects included in the target management unit and the items reported by the objects included in the target management unit. The object identifier of the management object can be the object's name, ID, identity information, etc. Here, the target management unit can be the target sub-management unit where the first object is located, or it can be the parent node of the target sub-management unit where the first object is located, that is, the management unit above the target sub-management unit.

[0101] Step 102: Send the target item to the managed object based on the object identifier of the managed object.

[0102] Here, after obtaining the object identifier of the managed object, the server sends the target item to the managed object based on the object identifier, that is, the server sends the target item to the terminal of the managed object.

[0103] The managed object's terminal receives the target item sent by the server. In practical applications, when the managed object can process the target item, it can directly process it and, after completing the processing, report a completion notification message to the server.

[0104] Furthermore, the managed object can also assign target items to other objects, enabling those other objects to process the target items, thus achieving target item assignment. In this case, the managed object can trigger an item assignment instruction for the target item on its terminal. The terminal of the managed object responds to this instruction by sending an item assignment request for the target item to the server. In practice, this item assignment request can also carry the object identifier of the second object indicated by the item assignment request, allowing the server to determine the object indicated by the item assignment request based on the object identifier of the second object, thereby sending the target item to the second object indicated by the item assignment request.

[0105] Step 103: When a task assignment request is received from a managed object, the target task is sent to the second object indicated by the task assignment request so that the second object can process the target task.

[0106] Here, the server receives a task assignment request from the managed object (terminal), and sends the target task to the second object (terminal) indicated by the task assignment request. Upon receiving the target task, the second object (terminal) processes it. In practice, the server can parse the task assignment request to obtain the object identifier of the second object included in the request, and then, based on the object identifier, send the target task to the second object indicated by the request, so that the second object can process the target task.

[0107] In other embodiments, the managed object can also report the target matter to the superior management unit of the target management unit. For example, when a suitable second object cannot be assigned to the target matter, the target matter can be further reported to the superior management unit of the target management unit, that is, the parent node of the target management unit.

[0108] In some embodiments, before receiving a target item reported by a first object included in a target sub-management unit in a management unit tree, the server may create an item management unit in the following manner: receiving a creation request for the item management unit, wherein the creation request carries object identification information; in response to the creation request, creating an item management unit based on the object identification information, and determining that the object corresponding to the object identification information is the item management object of the item management unit.

[0109] In practical applications, when creating a task management unit, a user can trigger a creation command for the task management unit through a terminal, such as triggering the command on a client running on the terminal that supports task processing. In response to the creation command, the terminal sends a creation request for the task management unit to the server. This creation request can carry object identification information, such as the object's identity information, name, and company information (e.g., company name). Upon receiving the creation request, the server parses it to obtain the object identification information carried in the request. Simultaneously, in response to the creation request, the server creates the corresponding task management unit based on the object identification information and determines that the object corresponding to the object identification information is the task management object of the task management unit. This task management object has the management permissions for the task management unit and can also have management permissions for any node in the task management unit tree in which the task management unit resides.

[0110] It should be noted that the item management unit created above is the root node of the management unit tree. The at least two sub-management units that together with the item management unit form the management unit tree can be child nodes of the item management unit. Specifically, they can be first-level child nodes (i.e., child nodes with the item management unit as their parent node), second-level child nodes (i.e., child nodes with the first-level child nodes as their parent nodes)... N-level child nodes (i.e., child nodes with N-1-level child nodes as their parent nodes), where N is an integer greater than 1.

[0111] In some embodiments, after creating an item management unit, the server can create sub-management units of the item management unit in the following manner: automatically creating child nodes of the item management unit as sub-management units, with the item management unit as the parent node; wherein the number of child nodes is the same as the number of sub-regions.

[0112] In practical applications, after the server creates an item management unit, it can automatically create child nodes of the item management unit, using the item management unit as the parent node, and these child nodes will be used as child management units. In actual implementation, the number of child nodes can be a pre-set default number or the same as the number of sub-regions.

[0113] In other embodiments, after the server creates the item management unit, the sub-management units can also be created according to user needs. For example, the user can send a request to the server to create a sub-node for the item management unit through the terminal. After receiving the sub-node creation request, the server responds to the request by creating a sub-node of the item management unit with the item management unit as the parent node, and uses the created sub-node as the sub-management unit.

[0114] In some embodiments, the server can create a sub-management unit for any node other than the event management unit in the following manner: for any node in the management unit tree other than the event management unit, a request to create a sub-node for the node is received; in response to the request to create a sub-node, a child node of the parent node is created as a sub-management unit, with the node as the parent node; wherein, the number of child nodes is the same as the number of target regions obtained by dividing the sub-regions corresponding to the node.

[0115] Here, in addition to creating corresponding child nodes for the root node (i.e., the task management unit) in the management unit tree, corresponding child nodes can also be created for any sub-management unit (i.e., any node in the management unit tree other than the task management unit). In practical applications, for any node in the management unit tree other than the task management unit, (the managed object of that node or the task management object of the task management unit) can send a child node creation request for that node to the server through the terminal. After receiving the child node creation request, the server responds to the request by creating a child node with that node as the parent node, and also treats the created child node as a sub-management unit. The number of child nodes is the same as the number of target areas obtained by dividing the sub-regions corresponding to the node.

[0116] It should be noted that the item management unit is used to manage items included in a geographical region. When creating child nodes for the item management unit, the creation of child nodes is related to the division of the geographical region. For example, if the geographical region is divided once, the management unit tree with the item management unit as the root node will include two levels of nodes: the root node and the first-level child nodes with the item management unit as the parent node. If the geographical region is divided twice, the management unit tree with the item management unit as the root node will include three levels of nodes: the root node, the first-level child nodes with the item management unit as the parent node, and the second-level child nodes with the first-level child nodes as the parent node, and so on. This will not be elaborated further here.

[0117] As an example, see Figure 4 , Figure 4 This is a schematic diagram of the management unit tree structure provided in this application embodiment. Here, the geographical region is divided twice to obtain a management unit tree with the item management unit as the root node. Each node (i.e., management unit) in the management unit tree is represented by the parent node ID and the node ID. The item management unit (i.e., the root node) is represented by "parent node ID:0-node ID:1". The management unit tree with the item management unit as the root node includes three levels of nodes: the root node ("parent node ID:0-node ID:1"), first-level child nodes with the item management unit as the parent node (including "parent node ID:1-node ID:2", "parent node ID:1-node ID:3", "parent node ID:1-node ID:4"), and second-level child nodes with the first-level child nodes as the parent nodes (including "parent node ID:2-node ID:5", "parent node ID:2-node ID:6", "parent node ID:3-node ID:7", "parent node ID:4-node ID:8", "parent node ID:4-node ID:9").

[0118] In some embodiments, the server may edit any node in the management unit tree in the following manner: for any node in the management unit tree, receive a node edit request for the node; wherein the node edit request carries editing information for the node, and the editing information includes at least one of the following: node association information, node object editing information, and node management object editing information; in response to the node edit request, perform corresponding editing operations on the node based on the editing information.

[0119] In practical applications, users can edit any node in the management unit tree, such as its node information (e.g., node name, corresponding geographical region, number of personnel), the node's constituent objects, and the objects it manages. When the server receives a node edit request, it responds by performing the corresponding editing operation on the node based on the editing information carried in the request. For example, this editing information might be node association information; if the node name is changed from "Management Unit X" to "Management Unit Y," the server will change the node name from "Management Unit X" to "Management Unit Y" based on this information.

[0120] In other embodiments, the edit information may also be deletion information for the corresponding node, that is, the edit information indicates the deletion of the corresponding node. When the server receives a node edit request carrying this edit information, it performs a deletion operation on the corresponding node.

[0121] In some embodiments, before receiving a target item reported by a first object included in a target sub-management unit in a management unit tree, the server may set the management object of the target management unit in the following manner: receiving a management object setting request for the target management unit; in response to the management object setting request, determining the target object indicated by the management object setting request as the management object corresponding to the target management unit; wherein the management object has the management permissions of the target management unit.

[0122] In practical applications, corresponding management objects can also be set for target management units. These management objects possess the management permissions of the target management unit, such as management permissions for unit objects within the target management unit and allocation permissions for items included in the target management unit. As an example, a user can trigger a management object setting command for a target management unit on a terminal. In response, the terminal sends a management object setting request for the target management unit, which may include the object identifier of the target object. Upon receiving the management object setting request, the server parses the request, obtains the object identifier of the target object carried in the request, and, based on this object identifier, identifies the target object indicated by the management object setting request as the management object corresponding to the target management unit, thus granting the target object the management permissions of the target management unit.

[0123] In some embodiments, before receiving a target item reported by a first object included in a target sub-management unit in the management unit tree, the server may add the first object to the target sub-management unit in the following manner: receiving an object addition request for the target sub-management unit, the object addition request carrying the object identifier of the first object; in response to the object addition request, adding the first object to the target sub-management unit based on the object identifier of the first object.

[0124] In practical applications, objects can also be added to sub-management units to place them within those units. Taking adding a first object to a target sub-management unit as an example, a user (e.g., the managed object of the target sub-management unit) triggers an object addition command on the terminal. In response, the terminal sends an object addition request to the server, carrying the object identifier of the first object. Upon receiving the object addition request, the server parses the request to obtain the object identifier of the first object and adds it to the target sub-management unit based on that identifier. This process adds the first object to the target sub-management unit.

[0125] In some embodiments, before receiving the target item reported by the first object included in the target sub-management unit in the management unit tree, the server may set the reporting object corresponding to the target sub-management unit in the following manner: receiving a reporting object setting request for the target sub-management unit, the reporting object setting request carrying the object identifier of the reporting object corresponding to the target sub-management unit; the object identifier of the reporting object is the node identifier corresponding to the target sub-management unit, or the node identifier corresponding to the parent node of the target sub-management unit; in response to the reporting object setting request, obtaining the management object of the node corresponding to the object identifier of the reporting object in the management unit tree; setting the management object of the node corresponding to the object identifier of the reporting object as the reporting object corresponding to the target sub-management unit;

[0126] Accordingly, the server can receive the target items reported by the first object included in the target sub-management unit in the management unit tree in the following way: for the reporting object, receive the target items reported by the first object included in the target sub-management unit in the management unit tree.

[0127] Here, a corresponding reporting object can also be set for the target sub-management unit. This reporting object is used to receive items reported by objects included in the target sub-management unit. In practical applications (such as the item management object of the item management unit, or the management object of the target sub-management unit), a reporting object setting instruction for the target sub-management unit can be triggered on the terminal. In response to this reporting object setting instruction, the terminal sends a reporting object setting request for the target sub-management unit to the server. When the server receives the reporting object setting request for the target sub-management unit, it responds to the request by parsing the reporting object setting request to obtain the object identifier of the reporting object. Based on the obtained object identifier of the reporting object, it obtains the management object of the node corresponding to the object identifier of the reporting object in the management unit tree; and sets the management object of the node corresponding to the object identifier of the reporting object as the reporting object corresponding to the target sub-management unit.

[0128] It should be noted that the object identifier of the reporting object can be the node identifier corresponding to the target sub-management unit; the object identifier of the reporting object can also be the node identifier corresponding to the parent node of the target sub-management unit. That is, the reporting object set for the target sub-management unit can be either the management object of the target sub-management unit or the management object of the parent node of the target sub-management unit. Based on this, the first object included in the target sub-management unit can report target matters to the reporting object set for the target sub-management unit, and the server receives the target matters reported by the first object included in the target sub-management unit in the management unit tree to the reporting object.

[0129] In some embodiments, before receiving a target item reported by a first object included in a target sub-management unit in the management unit tree, the server may set a candidate allocation object corresponding to the management object in the following manner: receiving an allocation object setting request for the management object; wherein the allocation object setting request carries a unit identifier of the target unit, and the target unit is one of the management units included in the management unit tree and the target sub-management unit; in response to the allocation object setting request, based on the unit identifier, determining the objects included in the target unit as candidate allocation objects corresponding to the management object, and the candidate allocation objects include a second object;

[0130] Accordingly, when a task assignment request is received from a managed object, the server can send the target task to the second object indicated by the task assignment request in the following manner: when a task assignment request is received from a managed object, the target task is sent to the second object indicated by the task assignment request in the target unit.

[0131] Here, corresponding candidate allocation objects can also be set for the managed objects of the target management unit. These candidate allocation objects include a second object, which is used by the management object to allocate target items. In practical applications (such as the item management object of an item management unit), the terminal can trigger an allocation object setting instruction for the management object. In response to this instruction, the terminal sends an allocation object setting request for the management object to the server. When the server receives the allocation object setting request, it responds by parsing the request to obtain the unit identifier of the target unit. Based on the obtained unit identifier, the objects included in the target unit are determined as candidate allocation objects corresponding to the management object.

[0132] It should be noted that the target unit can be any management unit included in the management unit tree (a management unit is the unit corresponding to any node in the management unit tree), that is, the target unit is any management unit included in the management unit tree; the target unit can also be the target sub-management unit where the first object is located.

[0133] Based on this, the managed object can assign the target item to the candidate allocation object included in the target unit. That is, when the server receives an item allocation request sent by the managed object, it sends the target item to the second object in the target unit that indicates the item allocation request.

[0134] In some embodiments, the server may set the candidate transfer object corresponding to the second object in the following manner: receiving a transfer object setting request for the second object; wherein the transfer object setting request carries a unit identifier of the target unit, which is one of the management units included in the management unit tree and the target sub-management units; in response to the transfer object setting request, determining the objects included in the target unit as candidate transfer objects corresponding to the second object based on the unit identifier; wherein the candidate transfer object is used to receive the target items transferred by the second object.

[0135] Here, a corresponding candidate transfer object can also be set for the second object that receives the target item. This candidate transfer object is used to receive the target item transferred by the second object. In practical applications (such as the item management object of the item management unit), a transfer object setting instruction for the second object can be triggered on the terminal. In response to the transfer object setting instruction, the terminal sends a transfer object setting request for the second object to the server. When the server receives the transfer object setting request for the second object, it responds to the transfer object setting request by parsing the transfer object setting request to obtain the unit identifier of the target unit. Based on the obtained unit identifier, the objects included in the target unit are determined as candidate transfer objects corresponding to the second object.

[0136] It should be noted that the target unit can be any management unit included in the management unit tree (a management unit is the unit corresponding to any node in the management unit tree), that is, the target unit is any management unit included in the management unit tree; the target unit can also be the target sub-management unit where the first object is located.

[0137] In some embodiments, after determining the objects included in the target unit as candidate transfer objects corresponding to the second object, the server can transfer the target item in the following manner: receiving a transfer request sent by the second object; in response to the transfer request, sending the target item to the target object indicated by the transfer request among the candidate transfer objects, so that the target object can process the target item.

[0138] After setting the candidate transfer objects corresponding to the second object based on the above embodiments, the second object can transfer the target item to the candidate transfer objects. In practical applications, the second object can trigger an item transfer instruction for the target item on its terminal. The second object's terminal responds to the item transfer instruction by sending an item transfer request for the target item to the server. Upon receiving the item transfer request from the second object, the server responds by parsing the request to obtain the object identifier of the target object, which belongs to the candidate transfer objects. Based on the object identifier of the target object, the server sends the target item to the target object (its terminal) indicated by the item transfer request, so that the target object can process the target item. After receiving the target item, the target object can then process it.

[0139] In some embodiments, after sending the target item to the second object indicating the item assignment request, the server may notify the target item of its completion progress by: receiving a reporting message indicating that the target item has been completed; and sending an item notification message to the target object to notify that the target item has been completed. The target object includes at least one of the first object and the management object.

[0140] In practical applications, once the target task is completed, a reporting message indicating that the target task has been completed can be sent to the server. For example, when a second object (or a transferee object receiving the target task from the second object) completes the target task, a completion instruction for the target task can be triggered through the terminal. In response to the completion instruction, the terminal sends a reporting message indicating that the target task has been completed to the server.

[0141] Upon receiving the report message, the server determines that the target matter has been completed. At this point, it notifies the relevant objects of the target matter, which include at least one of the reporting object (i.e., the first object) and the assigning object (i.e., the management object). In other words, the server sends a notification message to the target object (i.e., the relevant objects of the target matter) indicating that the target matter has been completed.

[0142] In some embodiments, after sending the target item to the second object indicating the item assignment request, the server can expedite the target item by: receiving an item notification message sent by the management object, which instructs to expedite the processing of the target item; and sending the item notification message to the second object.

[0143] In practical applications, after the managed object assigns a target task to a second object, during the processing of the target task, it can also send a task notification message to the server to instruct the second object to expedite the processing of the target task. When the server receives the task notification message instructing the second object to expedite the processing of the target task, it sends a task notification message to the second object (its terminal) to prompt the second object to expedite the processing of the target task.

[0144] Applying the above embodiments of this application, corresponding matter management units are set up for geographical areas, and at least two sub-regions are obtained by dividing the geographical area at least once, with each sub-region also having a corresponding sub-management unit. These at least two sub-management units and the matter management unit constitute a management unit tree. Based on this, the first object included in the target sub-management unit in the management unit tree can report target matters to be processed; since the target matter carries the object identifier of the management object corresponding to the target management unit, when the target matter is received, it can be sent to the management object of the target management unit based on the object identifier of the management object, so that the management object can allocate the target matter; since the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit, the management object can be either the management object of the target sub-management unit or the management object of the parent node of the target sub-management unit; when a matter allocation request sent by the management object is received, the target matter is sent to the second object indicated by the matter allocation request, so that the second object can process the target matter. That is, through the management unit tree composed of at least two sub-management units and the matter management unit, the reporting, allocation, and processing of target matters are realized. In this way, it is possible to achieve rational management of matters within a geographical area and improve the efficiency of handling matters.

[0145] The following describes the method for managing items in a geographical region provided in the embodiments of this application. Each geographical region has a corresponding item management unit. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit, and the at least two sub-management units and the item management unit constitute a management unit tree.

[0146] In some embodiments, the event management method for geographical regions provided in this application can be implemented by various electronic devices. For example, it can be implemented by a terminal alone, by a server alone, or by a terminal and a server working together. For example, see the documentation for terminal implementation. Figure 5 , Figure 5 This is a flowchart illustrating a method for managing events in a geographic area according to an embodiment of this application. The method for managing events in a geographic area according to an embodiment of this application includes:

[0147] Step 201: The terminal displays the item reporting interface and presents the reporting function items in the item reporting interface.

[0148] The reporting interface for this matter corresponds to the first object included in the target sub-management unit in the management unit tree. It should be noted that this matter management unit can exist in the form of an enterprise, institution, organization, etc., used to manage matters in the aforementioned geographical area; the first object can be a unit object included in the target sub-management unit (such as personnel belonging to the target sub-management unit), or it can be an ordinary object within the area managed by the target sub-management unit (such as personnel belonging to the area managed by the target sub-management unit but not belonging to the management unit tree).

[0149] In practical applications, this terminal can be equipped with a client, such as a client that supports task processing. When the terminal runs this client, it displays a task reporting interface, which corresponds to the first object included in the target sub-management unit in the management unit tree. When the first object included in the target sub-management unit needs to report a task, it can do so through the task reporting interface displayed on the terminal.

[0150] Additionally, a reporting function can be displayed on the item reporting interface to trigger a reporting instruction for the reported item. Upon receiving the reporting instruction, the terminal will send the item reported on the item reporting interface to the server, which can be a backend server of a client that supports item processing.

[0151] Step 202: Receive the target item input based on the item reporting interface.

[0152] In practical applications, after the terminal displays the item reporting interface, the target item to be reported can be entered in the item reporting interface. For example, the target item could be "The sewer pipe in Unit 2, Room 101 of XX Community needs repair". At this time, the terminal receives the target item entered by the first user based on the item reporting interface.

[0153] Step 203: In response to the triggered operation for the reporting function item, report the target item.

[0154] Among them, the target item carries the object identifier of the management object corresponding to the target management unit. The target management unit is one of the target sub-management unit and the parent node of the target sub-management unit.

[0155] Among them, the target item is used to send the target item to the management object and to the second object used to process the target item.

[0156] In practical applications, after the terminal receives the input target item, the first object can trigger a reporting instruction for the target item through the reporting function. When the terminal receives the trigger operation for the reporting function, it confirms that it has received the reporting instruction for the target item. At this time, the terminal sends the target item to the server. In actual implementation, the target item carries the object identifier of the managed object corresponding to the target management unit.

[0157] When the server receives a target item reported by the terminal of the first object, it can parse the target item to obtain the object identifier of the managed object corresponding to the target management unit carried by the target item. It should be noted that this managed object has the management permissions of the target management unit, such as managing the objects included in the target management unit and the items reported by the objects included in the target management unit. The object identifier of this managed object can be the object's name, ID, identity information, etc. Here, the target management unit can be the target sub-management unit where the first object is located, or it can be the parent node of the target sub-management unit where the first object is located, that is, the management unit above the target sub-management unit.

[0158] After obtaining the object identifier of the managed object, the server sends the target item to the managed object's terminal based on that object identifier. Upon receiving the target item from the server, the managed object's terminal can assign it to other objects for processing, thus achieving target item allocation.

[0159] In practice, the managed object can trigger a task allocation instruction for a target item on its personal terminal. In response, the managed object's terminal sends a task allocation request to the server. This request may also carry the object identifier of the second object indicated by the task allocation request, allowing the server to determine the object indicated by the task allocation request based on this object identifier and send the target item to the second object indicated by the task allocation request. Upon receiving the task allocation request from the managed object (its terminal), the server sends the target item to the second object (its terminal) indicated by the task allocation request. The second object (its terminal), upon receiving the target item, processes it.

[0160] Applying the above embodiments of this application, a corresponding item management unit is set up for a geographical area, and at least two sub-areas are obtained by dividing the geographical area at least once, and each sub-area is also set up with a corresponding sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. At the same time, an item reporting interface is provided for the objects included in the sub-management unit, and item reporting can be performed based on the item reporting interface and the reporting function items therein.

[0161] Based on this, the first object within the target sub-management unit in the management unit tree can report pending target matters through the matter reporting interface and reporting function. Since the target matter carries the object identifier of the management object corresponding to the target management unit, upon receiving the target matter, it can be sent to the management object of the target management unit based on the object identifier, allowing the management object to allocate the target matter. Because the target management unit is one of the target sub-management units and their parent nodes, the management object can be either the management object of the target sub-management unit or the management object of its parent node. When a matter allocation request is received from the management object, the target matter is sent to the second object indicated by the matter allocation request, allowing the second object to process the target matter. Thus, through the management unit tree composed of at least two sub-management units and the matter management unit, the reporting, allocation, and processing of target matters are realized. This enables rational management of matters within a geographical area and improves the efficiency of matter processing.

[0162] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario. First, the terms involved in this application will be explained, including:

[0163] 1) Multi-level management unit: This refers to the management unit tree described above, which includes multiple nodes (also called management units). In a scenario where items are managed for a specific geographical area, a corresponding item management unit can be set up for that geographical area (serving as the root node of the multi-level management unit). Simultaneously, the geographical area can be divided into several sub-regions, each corresponding to a sub-management unit (serving as a child node of the multi-level management unit). If a sub-region is further divided into several smaller sub-regions and corresponding sub-management units are set up, then these management units (including the item management unit and multiple sub-management units) constitute a multi-level management unit.

[0164] 2) Management object: A user who is assigned to a management unit (such as an event management object) and has management permissions for that management unit and its subordinate management units.

[0165] 3) Item management object: that is, the management object of the item management unit (root node) in the multi-level management unit.

[0166] 4) Unit objects of management units: Users assigned to a management unit (such as event management objects or management objects of a management unit). Management objects are a special type of unit object with management permissions.

[0167] The following describes the method for managing matters in a geographical region provided in the embodiments of this application.

[0168] First, the configuration management unit for the item management object.

[0169] See Figure 6 , Figure 6 This is a configuration diagram of the management unit provided in this application embodiment. Here, the item management object can access the configuration interface of all management units. Upon first use, management units 1, 2, and 3 will be initialized by default under the root node (i.e., the item management unit mentioned above). Simultaneously, by setting the item management object as the management object of the root node, the item management object can add sub-management units, add unit objects of management units, and edit management units.

[0170] Second, configure the reporting targets and processing permissions for the items under the item management system.

[0171] (1) Configure the reporting object corresponding to the newly created item: See Figure 7 , Figure 7 This is a schematic diagram of the configuration process for the reporting object provided in this application embodiment. Here, the terminal displays the function item "Member Creates New Item Report to", used to configure the reporting object, such as... Figure 7 As shown in (1); in response to the trigger operation of "Report new items created by members", the selectable reporting objects are displayed, including the management objects of the current management unit and the management objects of the superior management unit, such as Figure 7 As shown in (2).

[0172] a) When the management object of the current management unit is selected, the member will report the new item to the management object of the current management unit where the member is located; b) When the management object of the superior management unit is selected, the member will report the new item to the management object of the superior management unit of the current management unit where the member is located.

[0173] (2) Item assignment objects for configuration management objects: See Figure 8 , Figure 8 This is a schematic diagram of the configuration process for the task assignment object provided in an embodiment of this application. Here, the terminal displays the function item "The person in charge can assign / transfer events to" for configuring the task assignment object, such as... Figure 8 As shown in (1); in response to a trigger operation for "the person in charge can assign / transfer events to", the available task assignment objects are displayed, including the unit objects of all management units and the unit objects of the management units managed by the managed object, such as Figure 8 As shown in (2).

[0174] a) When selecting all management units' unit objects, the management objects of a management unit can assign the target items reported by the unit objects to all management units when transferring or distributing them; b) When selecting the unit objects of the management units managed by a management object, the management objects of a management unit can assign the target items reported by the unit objects to the unit objects of the management units they manage when transferring or distributing them.

[0175] (3) Item transfer objects for the configuration management unit's unit objects: See Figure 9 , Figure 9 This is a schematic diagram of the configuration process for the task assignment object provided in an embodiment of this application. Here, the terminal displays the function item "Member can transfer events to" for configuring the task assignment object, such as... Figure 9 As shown in (1); in response to the trigger operation for "Member can transfer events to", the available transfer objects are displayed, including the unit objects of all management units and the unit objects of the current management unit, such as Figure 9 As shown in (2).

[0176] a) When selecting a unit object from all management units, the unit object of the management unit can transfer the assigned target item to any unit object within all management units; b) When selecting a unit object within the current management unit, the unit object of the management unit can transfer the assigned target item to other unit objects within the current management unit.

[0177] Third, the management unit configures the management objects of the management unit.

[0178] See Figure 10 , Figure 10 This is a schematic diagram of the configuration of the management unit provided in the embodiment of this application. Here, the management object W can only enter the configuration interface of the management unit 1 it manages. The management object W can add sub-management units, add unit objects, and edit management units in the management unit 1 it manages.

[0179] Fourth, the reporting of matters by unit objects within the management unit.

[0180] See Figure 11 , Figure 11 This is a schematic diagram illustrating the reporting of events provided in an embodiment of this application. Here, as... Figure 11 As shown in (1), the unit object of the management unit can directly report the created target item as completed, that is, by selecting the "Report as Completed" function item; or report the created target item to the management object of the management unit, that is, by selecting the "Report to Management Object" function item. Here, the reported management object can be the management object of the management unit where it is located, or it can be the management object of the superior management unit where it is located, which can be based on Figure 7 The configuration of the reporting object is determined. For example... Figure 11 As shown in (2), when a unit object of a management unit creates a target item to be reported, the reporting source can be selected from the management unit where it is located and the subordinate management unit of the management unit.

[0181] See Figure 12 , Figure 12 This is a schematic diagram illustrating the task allocation provided in an embodiment of this application. Here, for the target task reported by the unit object of the management unit, the management object can choose to continue reporting upwards, that is, through... Figure 12 The "Report Upward" function shown in the image is implemented; or, it allows for the assignment of target items, i.e., through... Figure 12 The "Assign Items" function shown indicates which item the target item corresponds to and which item can be assigned to based on. Figure 8 The configuration decision of the task allocation object.

[0182] See Figure 13 , Figure 13 This is a schematic diagram illustrating the transfer of tasks provided in an embodiment of this application. Here, for the target task assigned by the management object, the unit object can choose to transfer it to other objects, that is, through... Figure 13 The "Transfer Items" function shown indicates which item can be transferred to based on the target item. Figure 9 The configuration decision for transferring matters to the object; or the unit object can directly complete the target matter, that is, through... Figure 13 When the "I have completed" function is enabled, a notification message will be sent to both the managed object and the person who reported the target matter to indicate that the processing of the target matter has been completed.

[0183] Fifth, the reporting of matters concerning ordinary objects within the area managed by the management unit.

[0184] See Figure 14 , Figure 14 This is a schematic diagram illustrating the reporting of matters according to an embodiment of this application. Here, ordinary objects within the area managed by the management unit can report matters through a matter reporting mini-program. Specifically, 1) the unit objects of the management unit can share the matter reporting mini-program or its QR code with ordinary objects in an instant messaging application, allowing ordinary objects to access the mini-program and report matters, such as... Figure 14 As shown in (1)-(2); 2) Ordinary objects can also obtain the reporting applet in the instant messaging application session by @Resident Assistant Robot, such as Figure 14As shown in (3); 3) After receiving the reported target matter, the unit object of the management unit can perform operations such as reporting upwards, transferring, assigning, and completing; 4) After the target matter is processed, the ordinary object can be notified of the processing result of the target matter through the session of the instant messaging application.

[0185] Sixth, the structure of multi-level management units.

[0186] See Figure 4 Each management unit's identifier consists of a parent node ID and a management unit ID. The parent node ID is used to associate with the ID of the next higher-level management unit. Each management unit can also be associated with multiple sub-management units, thus facilitating the organization into a multi-level management unit structure. The highest-level management unit is the root node of the entire management unit tree, and its parent node ID is 0.

[0187] Because multi-level management units have configurations for reporting, transferring, and assigning data from non-full management units, different management objects and unit objects may only see a portion of the management unit tree. In actual implementation, the visible portions of the management units for different management objects and unit objects can be marked. For example... Figure 4 As shown, the managed objects in management unit 4 (i.e., the node with "parent node ID: 1, node ID: 4") can only see management units 4, 8 (i.e., the nodes with "parent node ID: 4, node ID: 8"), and 9 (i.e., the nodes with "parent node ID: 4, node ID: 9"). Unit objects configured in management units 2 (i.e., the nodes with "parent node ID: 1, node ID: 2"), 3 (i.e., the nodes with "parent node ID: 1, node ID: 3"), and 7 (i.e., the nodes with "parent node ID: 3, node ID: 7"), such as those configured in management unit 2, cannot see management units 5 (i.e., the nodes with "parent node ID: 2, node ID: 5") and 6 (i.e., the nodes with "parent node ID: 2, node ID: 6") when reporting items; they can only report to management unit 2.

[0188] Seventh, the process for unit objects within the management unit to report matters. See [link / reference]. Figure 15 , Figure 15 This is a flowchart illustrating the process of a management unit object reporting a matter, as provided in this application embodiment, including:

[0189] 1) Unit object A retrieves the marked management unit tree from the multi-level management unit server;

[0190] 2) The server for multi-level management units returns the marked management unit tree;

[0191] 3) Unit object A selects the management unit that needs to be reported from the marked management unit tree and inputs the target item;

[0192] 4) Unit object A can directly report the target item as completed;

[0193] 5) Unit object A can also report target items to the management object of the management unit through the server of the multi-level management unit; specifically, it can report to the management object of its own management unit or the management object of the superior management unit, depending on the configuration of the management object.

[0194] 6) After receiving the reported target item, the management object of the management unit can set the target item as completed after the target item has been processed;

[0195] 7) When the server of a multi-level management unit receives a completion notification for a target matter, it pushes the completion notification to unit object A.

[0196] 8) If a managed object cannot handle a target matter, it can assign it to unit object B for processing;

[0197] 9) Once management unit B has completed its processing, the target item can be marked as completed;

[0198] 10) When the server of a multi-level management unit receives a completion notification for a target matter, it pushes the completion notification to unit object A and the managed object.

[0199] Eighth, the process for reporting matters to ordinary entities within the management unit's area. See [link / reference] Figure 16 , Figure 16 This is a flowchart illustrating the process of a regular object in the area managed by the management unit provided in this application embodiment reporting a matter, including:

[0200] 1) Ordinary users fill in the basic information of the target item to be reported through the item reporting mini-program and submit it to the server of the item reporting mini-program;

[0201] 2) The mini-program's server sends the target item to the server of the multi-level management unit;

[0202] 3) The server of the multi-level management unit sends the target item to unit object A;

[0203] 4) Unit object A retrieves the marked management unit tree from the multi-level management unit server;

[0204] 5) The server for multi-level management units returns the marked management unit tree;

[0205] 6) After receiving the target item, unit object A will randomly select a marked management unit where it is located. Unit object A can be changed to other marked management units as needed.

[0206] 7) Unit object A can directly report the target item as completed. The server of the multi-level management unit will send feedback to the item reporting applet to inform the target item that it has been completed.

[0207] 8) Unit object A can also report target items to the management object of the management unit through the server of the multi-level management unit; specifically, depending on the configuration of the management object, it can be reported to the management object of its own management unit or the management object of the superior management unit.

[0208] 9) After receiving the reported target item, the management object of the management unit can set the target item as completed after the target item has been processed;

[0209] 10) When the server of the multi-level management unit receives a completion notification for the target item, it pushes the completion notification to unit object A and at the same time pushes the completion notification to the item reporting applet.

[0210] 11) If a management object cannot handle a target matter, it can assign it to unit object B for handling. If unit object B takes a long time to handle the matter, the management object can also send a reminder notice.

[0211] 12) Once management unit B has completed its processing, the target item can be marked as completed.

[0212] 13) When the server of the multi-level management unit receives a completion notification for the target item, it pushes the completion notification to unit object A and the managed object, and at the same time pushes the completion notification to the item reporting applet.

[0213] By applying the above embodiments of this application, the multi-level management unit structure effectively organizes the reporting process of matters, enabling rational management of matters within a geographical area and improving the efficiency of matter processing.

[0214] It is understood that in the embodiments of this application, data related to user information (such as object identifiers) and target matters are involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0215] The following continues to describe the exemplary structure of the geographical area-specific event management device 553 provided in this application embodiment as a software module. In some embodiments, such as... Figure 2 As shown, the software modules stored in the geographic area-specific event management device 553 in the memory 550 may include:

[0216] The receiving module 5531 is configured to receive a target item reported by a first object included in the target sub-management unit in the management unit tree; wherein the target item carries the object identifier of the management object corresponding to the target management unit, and the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit; the first sending module 5532 is configured to send the target item to the management object based on the object identifier of the management object; the second sending module 5533 is configured to send the target item to the second object indicated by the item allocation request when a item allocation request is received from the management object, so that the second object can process the target item.

[0217] In some embodiments, the receiving module 5531 is further configured to receive a creation request for the item management unit, wherein the creation request carries object identification information; in response to the creation request, based on the object identification information, create the item management unit, and determine that the object corresponding to the object identification information is the item management object of the item management unit.

[0218] In some embodiments, the receiving module 5531 is further configured to automatically create child nodes of the item management unit as the child management unit, with the item management unit as the parent node; wherein the number of child nodes is the same as the number of sub-regions.

[0219] In some embodiments, the receiving module 5531 is further configured to receive a child node creation request for any node in the management unit tree other than the item management unit; in response to the child node creation request, create a child node of the parent node as the sub-management unit, with the parent node as the parent node; wherein the number of child nodes is the same as the number of target areas obtained by dividing the sub-region corresponding to the node.

[0220] In some embodiments, the receiving module 5531 is further configured to receive a node editing request for any node in the management unit tree; wherein the node editing request carries editing information for the node, and the editing information includes at least one of node association information, node object editing information, and node management object editing information; in response to the node editing request, the receiving module performs a corresponding editing operation on the node based on the editing information.

[0221] In some embodiments, the receiving module 5531 is further configured to receive a management object setting request for the target management unit; in response to the management object setting request, determine the target object indicated by the management object setting request as the management object corresponding to the target management unit; wherein the management object has the management permissions of the target management unit.

[0222] In some embodiments, the receiving module 5531 is further configured to receive an object addition request for the target sub-management unit, the object addition request carrying an object identifier of the first object; in response to the object addition request, the first object is added to the target sub-management unit based on the object identifier of the first object.

[0223] In some embodiments, the receiving module 5531 is further configured to receive a reporting object setting request for the target sub-management unit, the reporting object setting request carrying an object identifier of the reporting object corresponding to the target sub-management unit; the object identifier of the reporting object is a node identifier corresponding to the target sub-management unit or a node identifier corresponding to the parent node of the target sub-management unit; in response to the reporting object setting request, obtain the management object of the node corresponding to the object identifier of the reporting object in the management unit tree; set the management object of the node corresponding to the object identifier of the reporting object as the reporting object corresponding to the target sub-management unit; the receiving module 5531 is further configured to receive, for the reporting object, the target item reported by the first object included in the target sub-management unit in the management unit tree.

[0224] In some embodiments, the receiving module 5531 is further configured to receive an allocation object setting request for the managed object; wherein the allocation object setting request carries a unit identifier of a target unit, the target unit being one of the management units included in the management unit tree and the target sub-management unit; in response to the allocation object setting request, based on the unit identifier, the objects included in the target unit are determined as candidate allocation objects corresponding to the managed object, the candidate allocation objects including the second object; the receiving module 5531 is further configured to, when receiving an item allocation request sent by the managed object, send the target item to the second object indicated by the item allocation request in the target unit.

[0225] In some embodiments, the receiving module 5531 is further configured to receive a transfer object setting request for the second object; wherein the transfer object setting request carries a unit identifier of a target unit, the target unit being one of the management units included in the management unit tree and the target sub-management units; in response to the transfer object setting request, based on the unit identifier, the objects included in the target unit are determined as candidate transfer objects corresponding to the second object; wherein the candidate transfer object is configured to receive the target matter transferred by the second object.

[0226] In some embodiments, the receiving module 5531 is further configured to receive a transfer request sent by the second object; in response to the transfer request, send the target item to the target object indicated by the transfer request among the candidate transfer objects, so that the target object processes the target item.

[0227] In some embodiments, the receiving module 5531 is further configured to receive a reporting message indicating that the target matter has been processed; and send a matter notification message to the target object to notify that the target matter has been processed; wherein the target object includes at least one of the first object and the management object.

[0228] In some embodiments, the receiving module 5531 is further configured to receive a notification message sent by the management object, the notification message being used to instruct the expedited processing of the target matter; and to send the notification message to the second object.

[0229] Applying the above embodiments of this application, corresponding matter management units are set up for geographical areas, and at least two sub-regions are obtained by dividing the geographical area at least once, with each sub-region also having a corresponding sub-management unit. These at least two sub-management units and the matter management unit constitute a management unit tree. Based on this, the first object included in the target sub-management unit in the management unit tree can report target matters to be processed; since the target matter carries the object identifier of the management object corresponding to the target management unit, when the target matter is received, it can be sent to the management object of the target management unit based on the object identifier of the management object, so that the management object can allocate the target matter; since the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit, the management object can be either the management object of the target sub-management unit or the management object of the parent node of the target sub-management unit; when a matter allocation request sent by the management object is received, the target matter is sent to the second object indicated by the matter allocation request, so that the second object can process the target matter. That is, through the management unit tree composed of at least two sub-management units and the matter management unit, the reporting, allocation, and processing of target matters are realized. In this way, it is possible to achieve rational management of matters within a geographical area and improve the efficiency of handling matters.

[0230] This application embodiment also provides a device for managing items in a geographical region. The geographical region has corresponding item management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. The device includes:

[0231] A presentation module is used to present a matter reporting interface and, within the matter reporting interface, to present reporting function items; wherein, the matter reporting interface corresponds to a first object included in the target sub-management unit in the management unit tree; a matter receiving module is used to receive the input target matter based on the matter reporting interface; a reporting module is used to report the target matter in response to a trigger operation on the reporting function item; wherein, the target matter carries the object identifier of the management object corresponding to the target management unit, and the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit; wherein, the target matter is used to be sent via the management object to a second object for processing the target matter.

[0232] Applying the above embodiments of this application, a corresponding item management unit is set up for a geographical area, and at least two sub-areas are obtained by dividing the geographical area at least once, and each sub-area is also set up with a corresponding sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. At the same time, an item reporting interface is provided for the objects included in the sub-management unit, and item reporting can be performed based on the item reporting interface and the reporting function items therein.

[0233] Based on this, the first object within the target sub-management unit in the management unit tree can report pending target matters through the matter reporting interface and reporting function. Since the target matter carries the object identifier of the management object corresponding to the target management unit, upon receiving the target matter, it can be sent to the management object of the target management unit based on the object identifier, allowing the management object to allocate the target matter. Because the target management unit is one of the target sub-management units and their parent nodes, the management object can be either the management object of the target sub-management unit or the management object of its parent node. When a matter allocation request is received from the management object, the target matter is sent to the second object indicated by the matter allocation request, allowing the second object to process the target matter. Thus, through the management unit tree composed of at least two sub-management units and the matter management unit, the reporting, allocation, and processing of target matters are realized. This enables rational management of matters within a geographical area and improves the efficiency of matter processing.

[0234] This application also provides a computer program product or computer program that includes 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 device to perform the event management method for a geographic region provided in this application.

[0235] This application also provides a computer-readable storage medium storing executable instructions, which, when executed by a processor, will cause the processor to execute the event management method for a geographic region provided in this application.

[0236] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0237] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0238] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0239] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0240] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method of managing matters with respect to a geographic area, characterized by, The geographical region has corresponding item management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. The method includes: A reporting object setting request is received for a target sub-management unit in the management unit tree, wherein the reporting object setting request carries the object identifier of the reporting object corresponding to the target sub-management unit, and the object identifier of the reporting object is the node identifier corresponding to the target sub-management unit or the node identifier corresponding to the parent node of the target sub-management unit; In response to the reporting object setting request, the management object of the node corresponding to the object identifier of the reporting object in the management unit tree is obtained, and the management object of the node corresponding to the object identifier of the reporting object is set as the reporting object corresponding to the target sub-management unit; For the reporting object, the target item reported by the first object included in the target sub-management unit in the management unit tree is received; The target item carries the object identifier of the management object corresponding to the target management unit. The target management unit is one of the target sub-management unit and the parent node of the target sub-management unit. The target sub-management unit is included in at least a portion of the management unit tree visible to the first object. A request to set an allocation object for the managed object is received, wherein the request carries a unit identifier of the target unit, and the target unit is one of the management units included in the management unit tree and the target sub-management unit; In response to the allocation object setting request, based on the unit identifier, the objects included in the target unit are determined as candidate allocation objects corresponding to the management object, wherein the candidate allocation objects include a second object; Based on the object identifier of the managed object, the target item is sent to the managed object; When a task assignment request is received from the management object, the target task is sent to the second object indicated by the task assignment request in the target unit, so that the second object can process the target task.

2. The method of claim 1, wherein, Before receiving the target item reported by the first object included in the target sub-management unit in the management unit tree, the method further includes: A creation request for the item management unit is received, wherein the creation request carries object identification information; In response to the creation request, the item management unit is created based on the object identification information, and the object corresponding to the object identification information is determined as the item management object of the item management unit.

3. The method of claim 2, wherein, After creating the item management unit, the method further includes: Using the aforementioned task management unit as the parent node, child nodes of the aforementioned task management unit are automatically created, serving as the child management units; The number of child nodes is the same as the number of sub-regions.

4. The method of claim 1, wherein, The method further includes: For any node in the management unit tree other than the item management unit, a request to create a child node for that node is received; In response to the child node creation request, a child node of the parent node is created, which serves as the child management unit; The number of child nodes is the same as the number of target regions obtained by dividing the sub-regions corresponding to the nodes.

5. The method of claim 1, wherein, The method further includes: For any node in the management unit tree, a node edit request for that node is received; The node editing request carries editing information for the node, which includes at least one of the following: node association information, node object editing information, and node management object editing information; In response to the node editing request, the corresponding editing operation is performed on the node based on the editing information.

6. The method of claim 1, wherein, Before receiving the target item reported by the first object included in the target sub-management unit in the management unit tree, the method further includes: A request to set the management object for the target management unit has been received; In response to the management object setting request, the target object indicated by the management object setting request is determined as the management object corresponding to the target management unit; The management object has the management authority of the target management unit.

7. The method as described in claim 1, characterized in that, Before receiving the target item reported by the first object included in the target sub-management unit in the management unit tree, the method further includes: A request to add an object to the target sub-management unit is received, the object addition request carrying the object identifier of the first object; In response to the object addition request, the first object is added to the target sub-management unit based on the object identifier of the first object.

8. The method as described in claim 1, characterized in that, The method further includes: Received a request to set up a transfer object for the second object; The transfer object is set to carry the unit identifier of the target unit, and the target unit is one of the management units included in the management unit tree and the target sub-management unit; In response to the transfer object setting request, based on the unit identifier, the objects included in the target unit are determined as candidate transfer objects corresponding to the second object; The candidate transfer object is used to receive the target matter transferred by the second object.

9. The method as described in claim 8, characterized in that, After determining the objects included in the target unit as candidate transfer objects corresponding to the second object, the method further includes: Received a request for item transfer from the second object; In response to the transfer request, the target item is sent to the target object indicated by the transfer request among the candidate transfer objects, so that the target object can process the target item.

10. The method as described in claim 1, characterized in that, After sending the target item to the second object in the target unit that indicates the item allocation request, the method further includes: Receive a reporting message indicating that the target matter has been processed and completed; Send a notification message to the target object to inform it that the target matter has been processed. The target object includes at least one of the first object and the managed object.

11. The method as described in claim 1, characterized in that, After sending the target item to the second object in the target unit that indicates the item allocation request, the method further includes: The system receives a notification message from the managed object, which instructs the system to expedite the processing of the target matter. Send the notification message to the second object.

12. A method for managing matters within a geographical area, characterized in that, The geographical region has corresponding item management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the item management unit constitute a management unit tree. The method includes: Present the task reporting interface, and present the reporting function items in the task reporting interface; The item reporting interface corresponds to the first object included in the target sub-management unit in the management unit tree, and the target sub-management unit is included in at least a portion of the management unit tree visible to the first object; Based on the aforementioned reporting interface, the input target item is received; In response to a trigger operation for the reporting function item, the target item is reported for the reporting object. The reporting object is set by obtaining the management object of the node corresponding to the object identifier of the reporting object in the management unit tree in response to a reporting object setting request for the target sub-management unit. The reporting object setting request carries the object identifier of the reporting object corresponding to the target sub-management unit. The object identifier of the reporting object is the node identifier corresponding to the target sub-management unit or the node identifier corresponding to the parent node of the target sub-management unit. The target item carries the object identifier of the management object corresponding to the target management unit, and the target management unit is one of the target sub-management unit and the parent node of the target sub-management unit; The target item is used to send the target item to a second object for processing the target item via the management object. The second object is included in the candidate allocation object corresponding to the management object. The candidate allocation object is determined based on the objects included in the target unit in response to the allocation object setting request for the management object. The allocation object setting request carries the unit identifier of the target unit. The target unit is one of the management units included in the management unit tree and the target sub-management units.

13. A device for managing matters in a geographical area, characterized in that, The geographical region has corresponding task management units. The geographical region is divided at least once to obtain at least two sub-regions. Each sub-region corresponds to a sub-management unit. The at least two sub-management units and the task management unit constitute a management unit tree. The device includes: The receiving module is configured to receive a reporting object setting request for a target sub-management unit in the management unit tree, wherein the reporting object setting request carries an object identifier of the reporting object corresponding to the target sub-management unit, and the object identifier of the reporting object is either a node identifier corresponding to the target sub-management unit or a node identifier corresponding to the parent node of the target sub-management unit; in response to the reporting object setting request, the module obtains the management object of the node corresponding to the object identifier of the reporting object in the management unit tree, and sets the management object of the node corresponding to the object identifier of the reporting object as the reporting object corresponding to the target sub-management unit; and for the reporting object, receives the target items reported by the first object included in the target sub-management unit in the management unit tree. The target item carries the object identifier of the management object corresponding to the target management unit. The target management unit is one of the target sub-management unit and the parent node of the target sub-management unit. The target sub-management unit is included in at least a portion of the management unit tree visible to the first object. The receiving module is further configured to receive an allocation object setting request for the managed object, wherein the allocation object setting request carries a unit identifier of a target unit, and the target unit is one of the management units included in the management unit tree and the target sub-management units; in response to the allocation object setting request, based on the unit identifier, the objects included in the target unit are determined as candidate allocation objects corresponding to the managed object, wherein the candidate allocation objects include a second object; The first sending module is used to send the target item to the managed object based on the object identifier of the managed object; The second sending module is used to send the target item to the second object indicated by the item allocation request in the target unit when it receives the item allocation request sent by the management object, so that the second object can process the target item.

14. The apparatus as claimed in claim 13, characterized in that, The receiving module is further configured to receive a creation request for the item management unit, wherein the creation request carries object identification information; in response to the creation request, based on the object identification information, create the item management unit, and determine that the object corresponding to the object identification information is the item management object of the item management unit.

15. The apparatus as claimed in claim 13, characterized in that, The receiving module is further configured to automatically create child nodes of the item management unit as the child management unit, with the item management unit as the parent node; wherein the number of child nodes is the same as the number of sub-regions.

16. An electronic device, characterized in that, The electronic device includes: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the event management method for a geographic region as described in any one of claims 1 to 12.

17. A computer-readable storage medium storing executable instructions, characterized in that, When the executable instructions are executed by the processor, they implement the event management method for a geographic region as described in any one of claims 1 to 12.

18. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the processor, they implement the event management method for a geographic region as described in any one of claims 1 to 12.

Images