Terminal deployment information management method and apparatus, and electronic device and storage medium

Abstract

Disclosed in the present invention are a terminal deployment information management method and apparatus, and an electronic device and a storage medium. The method comprises: in response to an access instruction of a target terminal, acquiring geographical location information and a type identifier of the target terminal; on the basis of the geographical location information, obtaining belonging region information of the target terminal; on the basis of the belonging region information, determining regional distribution information of the target terminal; on the basis of the type identifier, determining a module type of the target terminal; and on the basis of the module type, performing visualization processing on the regional distribution information. In the embodiments of the present invention, on the basis of geographical location information and a type identifier of a target terminal, regional distribution conditions of various terminals can be efficiently and accurately obtained. The embodiments of the present invention can obtain terminal distribution conditions efficiently and accurately, and can thus be widely applied to the technical field of data processing.

Description

Terminal deployment information management method, device, electronic device and storage medium Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a terminal deployment information management method, device, electronic device and storage medium. Background Art

[0002] Operator IoT platforms support a wide range of access terminals using various protocols, such as MQTT and LWM2M. Currently, the number of terminals accessing these platforms is increasing, but the platforms focus more on the status and number of access terminals. Terminal information reusability is poor, and it's impossible to intuitively access data from various terminals. Summary of the Invention

[0003] The present invention aims to solve at least one of the technical problems in the related art to a certain extent. To this end, the present invention provides a terminal deployment information management method, device, electronic device and storage medium, which can efficiently and accurately obtain terminal distribution information through terminal deployment information management.

[0004] In one aspect, an embodiment of the present invention provides a method for managing terminal deployment information, including:

[0005] In response to an access instruction from a target terminal, obtaining geographic location information and a type identifier of the target terminal;

[0006] Obtaining the region information of the target terminal according to the geographical location information;

[0007] Determine the regional distribution information of the target terminal according to the regional information;

[0008] Determine the module type of the target terminal according to the type identifier;

[0009] Based on the module type, the regional distribution information is visualized.

[0010] Optionally, in response to an access instruction from the target terminal, acquiring geographic location information and a type identifier of the target terminal includes:

[0011] In response to an access instruction when the target terminal logs into the platform, the geographical location information is obtained from a newly added field of the login message of the target terminal, and the type identifier is obtained based on the parsing of the login message.

[0012] Optionally, obtaining the region information of the target terminal according to the geographical location information includes:

[0013] Determine the geographical location of the target terminal according to the geographical location information;

[0014] Based on the geographic location, the area information of the target terminal is obtained in combination with the preset partition range.

[0015] Optionally, determining the regional distribution information of the target terminal according to the region information includes:

[0016] Based on the identification information of the target terminal, obtaining the target terminal's historical cache information;

[0017] The region information is compared with the cache information, and the region distribution information of the target terminal is determined based on the comparison result.

[0018] Optionally, determining regional distribution information of the target terminal according to the comparison result includes:

[0019] When the comparison result is inconsistent, the regional distribution information is determined according to the regional information, and the cache information is updated according to the regional information and the regional distribution information;

[0020] Alternatively, when the comparison result is consistent, the regional distribution information of the cached information is directly referenced.

[0021] Optionally, determining the regional distribution information of the target terminal according to the region information includes:

[0022] Through the perception protocol technology between terminals, the target terminal is used to perform collaborative perception to obtain a terminal list; the terminal list includes several other target terminals perceived by the target terminal;

[0023] Through collaborative sensing, the geographical location information of each target terminal in the terminal list is obtained, and the area information of each target terminal in the terminal list is obtained according to the geographical location information of each target terminal in the terminal list;

[0024] The regional distribution information of all target terminals is determined according to the region information to which all target terminals belong.

[0025] Optionally, based on the module type, the regional distribution information is visualized, including at least one of the following:

[0026] Visualize regional distribution information based on the dimensions corresponding to the module type;

[0027] Based on the module type, the regional distribution information of specific target terminals is visualized.

[0028] On the other hand, an embodiment of the present invention provides a terminal deployment information management device, including:

[0029] The first module is configured to obtain the geographic location information and type identifier of the target terminal in response to an access instruction of the target terminal;

[0030] The second module is used to obtain the area information of the target terminal according to the geographical location information;

[0031] The third module is used to determine the regional distribution information of the target terminal according to the region information;

[0032] A fourth module is used to determine the module type of the target terminal according to the type identifier;

[0033] The fifth module is used to visualize regional distribution information based on module type.

[0034] On the other hand, an embodiment of the present invention provides an electronic device, including: a processor and a memory; the memory is used to store programs; the processor executes the program to implement the above-mentioned terminal deployment information management method.

[0035] On the other hand, an embodiment of the present invention provides a computer storage medium storing a program executable by a processor. The program executable by the processor is used to implement the above-mentioned terminal deployment information management method when executed by the processor.

[0036] The embodiments of the present invention obtain the target terminal's geographic location information and type identifier in response to an access instruction from the target terminal; obtain the target terminal's region information based on the geographic location information; determine the target terminal's regional distribution information based on the region information; determine the target terminal's module type based on the type identifier; and visualize the regional distribution information based on the module type. Based on the target terminal's geographic location information and type identifier, the embodiments of the present invention can efficiently and accurately determine the regional distribution of various types of terminals. The embodiments of the present invention can efficiently and accurately determine terminal distribution information. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solution of the present invention and do not constitute a limitation to the technical solution of the present invention.

[0038] 1 is a schematic diagram of an implementation environment for terminal deployment information management provided by an embodiment of the present invention;

[0039] 2 is a schematic diagram of a process of a terminal deployment information management method provided by an embodiment of the present invention;

[0040] FIG3 is a schematic diagram of an expansion process of training an autoregressive integrated moving average model based on full data according to an embodiment of the present invention;

[0041] FIG4 is a schematic diagram of an Internet of Things system architecture of an application operation and maintenance monitoring system provided by an embodiment of the present invention;

[0042] FIG5 is a schematic diagram of the architecture of an operation and maintenance monitoring system provided by an embodiment of the present invention;

[0043] FIG6 is a schematic diagram of a data acquisition and calculation module architecture provided by an embodiment of the present invention;

[0044] FIG7 is a schematic diagram of the process of ARIMA modeling and prediction provided by an embodiment of the present invention;

[0045] 8 is a schematic structural diagram of a terminal deployment information management device provided by an embodiment of the present invention;

[0046] FIG9 is a schematic structural diagram of an electronic device provided by an embodiment of the present invention;

[0047] FIG10 is a block diagram of a computer system structure of an electronic device suitable for implementing an embodiment of the present invention, provided in accordance with an embodiment of the present invention. DETAILED DESCRIPTION

[0048] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0049] It should be noted that although the system diagrams illustrate functional module divisions and the flowcharts illustrate a logical sequence, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the system or the sequence in the flowcharts. The terms "first / S100," "second / S200," and the like in the specification, claims, and drawings are used to distinguish similar objects and are not necessarily intended to describe a specific sequence or precedence.

[0050] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present invention. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute a separate or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0051] To facilitate understanding of the technical solutions of the present invention, the following are some professional and technical terms that may appear in the embodiments of the present invention:

[0052] LOC: Location, geographic location information.

[0053] SDK: Software Development Kit, generally a collection of development tools used by software engineers to build applications for a specific software package, framework, hardware platform, operating system, or other framework. Software development tools broadly refer to a collection of documentation, examples, and tools that aid in the development of a specific type of software. A software development kit (SDK) is a collection of development tools used by software engineers to create applications for a specific software package, framework, hardware platform, or operating system. Typically, an SDK is used to develop applications for the Windows platform. It facilitates application creation through compilers, debuggers, and software frameworks. It can simply provide API files for a specific programming language, but it can also include complex hardware that can communicate with an embedded system. Typical tools include debugging and other utilities. SDKs often also include sample code, supporting technical notes, or other supporting documentation that clarifies underlying reference material.

[0054] MQTT (Message Queuing Telemetry Transport) is an ISO standard (ISO / IEC PRF 20922) for publishing and subscribing messaging. Operating on the TCP / IP protocol suite, it is designed for remote devices with low-performance hardware and poor network conditions, requiring a messaging middleware. MQTT is a client-server publish / subscribe messaging transport protocol. Its lightweight, simple, open, and easy-to-implement characteristics make it widely applicable, including in constrained environments such as machine-to-machine (M2M) communications and the Internet of Things (IoT). It is widely used in sensors communicating via satellite links, medical devices with occasional dial-up connections, smart homes, and other small devices.

[0055] LWM2M (Lightweight M2M), proposed by the Open Mobile Alliance (OMA), is a lightweight, standard, and universal IoT device management protocol for rapid deployment of client / server IoT services. LWM2M establishes a set of standards for IoT device management and applications, providing a lightweight, secure communication interface and an efficient data model to enable M2M device management and service support.

[0056] It is understandable that the terminal deployment information management method provided in the embodiment of the present invention can be applied to any computer device with data processing and computing capabilities, and this computer device can be various terminals or servers. When the computer device in the embodiment is a server, the server is an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Optionally, the terminal is a smart phone, tablet computer, laptop computer, desktop computer, etc., but is not limited to this.

[0057] FIG1 is a schematic diagram of an implementation environment provided by an embodiment of the present invention. Referring to FIG1 , the implementation environment includes at least one terminal 102 and a server 101. The terminal 102 and the server 101 can be connected to a network wirelessly or wired to complete data transmission and exchange.

[0058] Server 101 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0059] In addition, server 101 can also be a node server in a blockchain network. Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm.

[0060] The terminal 102 may be a smart phone, tablet computer, laptop computer, desktop computer, smart speaker, smart watch, etc., but is not limited thereto. The terminal 102 and the server 101 may be connected directly or indirectly via wired or wireless communication, which is not limited in this embodiment of the present invention.

[0061] Exemplarily based on the implementation environment shown in FIG1 , an embodiment of the present invention provides a terminal deployment information management method. The following description will be given using the example of the terminal deployment information management method being applied to the server 101. It is understandable that the terminal deployment information management method can also be applied to the terminal 102.

[0062] Referring to Figure 2, which is a flowchart of a terminal deployment information management method applied to a server according to an embodiment of the present invention, the execution subject of the terminal deployment information management method can be any of the aforementioned computer devices (including a server or a terminal). Referring to Figure 2, the method includes the following steps:

[0063] S100, in response to an access instruction from a target terminal, obtaining geographic location information and a type identifier of the target terminal;

[0064] It should be noted that, in some embodiments, step S100 may include: in response to an access instruction when the target terminal logs into the platform, obtaining geographic location information from a newly added field of a login message of the target terminal, and obtaining a type identifier based on parsing the login message.

[0065] For example, in some specific embodiments, after the terminal is powered on or restarted to attach to the network successfully, a new LOC (geographic location information) field is added to the login message when the terminal logs into the platform to report the area information to which the current terminal belongs (NB\CAT1\CAT4\REDCAP terminal: CID\LAC\TAI, etc.).

[0066] S200, obtaining the region information of the target terminal according to the geographical location information;

[0067] It should be noted that, in some embodiments, step S200 may include: determining the geographical location of the target terminal according to the geographical location information; and obtaining the area information of the target terminal based on the geographical location and in combination with a preset partition range.

[0068] For example, in some specific embodiments, the geographic location (eg, longitude and latitude) of the target terminal can be determined based on geographic location information, and then compared with a preset partition range to determine which partition range the terminal's geographic location falls into, thereby determining the area information.

[0069] S300, determining regional distribution information of the target terminal according to the region information;

[0070] It should be noted that, in some embodiments, step S300 may include: obtaining historical cache information of the target terminal based on identification information of the target terminal; comparing the region information with the cache information, and determining the regional distribution information of the target terminal according to the comparison result.

[0071] Among them, in some embodiments, determining the regional distribution information of the target terminal based on the comparison result may include: when the comparison result is inconsistent, determining the regional distribution information based on the area information, and updating the cache information based on the area information and the regional distribution information; or, when the comparison result is consistent, directly referencing the regional distribution information of the cache information.

[0072] For example, in some specific embodiments, after receiving the area information reported by the terminal, it is compared with the corresponding cache information to obtain comparison information; if the comparison information is judged to be consistent, there is no need to update the area distribution information; if the comparison information is judged to be inconsistent, the cache information is updated and based on the latest area information.

[0073] It should also be noted that in some embodiments, as shown in Figure 3, step S300 may include: S301, through the perception protocol technology between terminals, using the target terminal to perform collaborative perception to obtain a terminal list; the terminal list includes several other target terminals perceived by the target terminal; S302, through collaborative perception, obtaining the geographic location information of each target terminal in the terminal list, and obtaining the area information of each target terminal in the terminal list based on the geographic location information of each target terminal in the terminal list; S303, determining the regional distribution information of all target terminals based on the area information of all target terminals.

[0074] For example, in some specific embodiments, the type of perception protocol between the terminal and its coordinated terminals is not limited, and the "perception protocol" technology between the terminals, such as Bluetooth Low Energy (BLE), WIFI Scan, RFID, Zigbee, sensors, NFC, etc., is used to perceive each other. Through collaborative perception, the geographic location information of the distribution of batch terminal SDKs in the current area can be obtained. The specific geographic information of the device (not base station information) can be collected using the network or module.

[0075] S400: Determine the module type of the target terminal according to the type identifier;

[0076] For example, in some specific embodiments, the module type OPT identifier of the current terminal can be parsed when the terminal is connected, and the corresponding device can be parsed as an NB customized module, an MQTT customized module, an MQTT non-customized module, or other modules.

[0077] S500: Visualize the regional distribution information based on the module type.

[0078] It should be noted that, in some embodiments, step S500 may include at least one of the following: visualizing the regional distribution information based on the dimension corresponding to the module type; and visualizing the regional distribution information of the specific target terminal based on the module type.

[0079] For example, in some specific embodiments, regional distribution information can be displayed based on the module type dimension, and terminals using self-developed SDKs can be parsed. The platform side obtains regional distribution information of terminals using self-developed SDKs from the information statistics module and displays it to users.

[0080] In order to explain the principle of the technical solution of the present invention in detail, the overall process of the present invention is described below in combination with some specific embodiments. It is easy to understand that the following is an explanation of the technical principle of the present invention and cannot be regarded as a limitation of the present invention.

[0081] First of all, it should be noted that the operator's Internet of Things platform can support a wide range of access terminals, with multiple access protocols, such as MQTT, LWM2M, etc. In order to further support and expand the development of telecommunications Internet of Things services, an embodiment of the present invention provides a terminal deployment information management method that can automatically display the regional distribution of terminal SDKs on the platform side. The regional distribution of NB customized terminals, MQTT customized terminals, MQTT non-customized terminals and other terminals connected to the CTWING platform (an Internet of Things platform) can be displayed on the platform side, so that the platform side can automatically display the regional distribution of telecommunications terminal SDK usage, which is of great significance to telecommunications groups in equipment management and equipment deployment.

[0082] The number of terminals connecting to operators' IoT platforms is increasing, but the regional distribution of terminals using self-developed SDKs has not yet been analyzed. Currently, the platform focuses more on the status and number of connected terminals, and has not yet compiled statistics on the regions where self-developed SDK terminals are located.

[0083] In some specific embodiments, the present invention adds a terminal SDK regional distribution information statistics module to the CTWING platform, enabling the platform to automatically display and present the regional distribution of terminals developed by China Telecom's own SDKs. The SDKs involved include: SDKs accessed via the MQTT protocol; and NB SDKs accessed via the LWM2M protocol.

[0084] As shown in FIG4 , a scenario architecture for application of an embodiment of the present invention is shown. The process of terminal deployment information management in an embodiment of the present invention is as follows:

[0085] After the terminal is powered on or restarted to attach to the network successfully, a new LOC (geographic location information) field is added to the login message when the terminal logs into the platform to report the area information (NB\CAT1\CAT4\REDCAP terminal: CID\LAC\TAI, etc.) to which the current terminal (and the list of terminals collaboratively perceived by the current terminal) belongs.

[0086] As shown in Figure 5, the types of perception protocols between terminals and their collaborative terminals are not restricted. Terminals can sense each other using "perception protocol" technologies such as Bluetooth Low Energy (BLE), Wi-Fi Scan, RFID, Zigbee, sensors, and NFC. Through collaborative perception, geographic location information for the distribution of batch terminal SDKs in the current region can be obtained. Specific device geographic information (not base station information) is collected using the network or module.

[0087] After receiving the area information reported by the terminal, the information statistics module compares it with the corresponding cache information to obtain comparison information; if the comparison information is consistent, there is no need to update the area distribution information; if the comparison information is inconsistent, the cache information is updated and displayed based on the latest area information.

[0088] At the same time, when the device is connected, the information statistics module parses the module type OPT identifier of the current terminal and parses the corresponding device into NB customized module, MQTT customized module, MQTT non-customized module and other modules, thereby displaying regional distribution information based on the module type dimension.

[0089] The information statistics module parses out the terminals that use the self-developed SDK. The platform side obtains the regional distribution information of the terminals that use the self-developed SDK from the information statistics module and displays it to the user.

[0090] For example, in some specific embodiments, as shown in FIG6 , an embodiment of the present invention further provides a system, by which terminal deployment information management can be realized as shown in FIG6 ; the system mainly includes: a terminal SDK, an Internet of Things platform (CTWING platform), and a terminal SDK regional distribution information statistics module.

[0091] The data processing flow of the information statistics module is shown in Figure 7. The terminal SDK regional distribution information statistics module includes a data module: completing data analysis and regional information statistics; a comparison module: completing comparison with the corresponding cache information; and a display module: completing regional information display.

[0092] In summary, the present invention adds a statistical regional information module to the operator's IoT platform, which can collect regional information statistics for terminals connected to the Telecom CTWING platform using the self-developed SDK. The terminal market can expand its market business based on the statistical data, thereby better supporting and broadening the future development of terminal business. In order to cope with the access of massive terminals, the platform's data processing performance and data processing capabilities are improved, thereby achieving a more reasonable allocation and deployment of IoT terminals; compared with the existing technology, the present invention has at least the following beneficial effects:

[0093] 1. The terminal market is severely fragmented. The present invention can perform SDK regional deployment statistics for various types of terminals, and utilize collaborative sensing technology between terminals to achieve the goal of having one terminal report the SDK regional deployment of batch terminals.

[0094] 2. The platform has added a new regional information statistics module, which can collect regional information statistics for terminals connected to the Telecom CTWING platform using the self-developed SDK. The terminal market can expand its market business based on the statistical information, thereby better supporting and broadening the future development of terminal business.

[0095] On the other hand, as shown in Figure 8, an embodiment of the present invention provides a terminal deployment information management device 800, including: a first module 810, used to obtain the geographic location information and type identification of the target terminal in response to the access instruction of the target terminal; a second module 820, used to obtain the area information of the target terminal based on the geographic location information; a third module 830, used to determine the regional distribution information of the target terminal based on the area information; a fourth module 840, used to determine the module type of the target terminal based on the type identification; and a fifth module 850, used to visualize the regional distribution information based on the module type.

[0096] The contents of the method embodiments of the present invention are all applicable to the device embodiments. The functions specifically implemented by the device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0097] On the other hand, as shown in FIG9 , an embodiment of the present invention further provides an electronic device 900 , which includes at least one processor 910 and at least one memory 920 for storing at least one program; taking a processor 910 and a memory 920 as an example.

[0098] The processor 910 and the memory 920 may be connected via a bus or other means.

[0099] The memory 920 is a non-transient computer-readable storage medium that can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory 920 may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 920 may optionally include a memory remotely located relative to the processor, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0100] The electronic device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one location or distributed across multiple network units. Some or all of these modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0101] Specifically, FIG10 schematically shows a block diagram of a computer system structure of an electronic device for implementing an embodiment of the present invention.

[0102] It should be noted that the computer system 1000 of the electronic device shown in FIG10 is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0103] As shown in Figure 10, the computer system 1000 includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1002 or the program loaded from the storage part 1008 into the random access memory (RAM) 1003. Various programs and data required for system operation are also stored in the random access memory 1003. The CPU 1001, the read-only memory 1002, and the random access memory 1003 are connected to each other via a bus 1004. An input / output interface 1005 (i.e., an I / O interface) is also connected to the bus 1004.

[0104] The following components are connected to the input / output interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 1008 including a hard disk; and a communication section 1009 including a network interface card such as a local area network card or a modem. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the input / output interface 1005 as needed. Removable media 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1010 as needed, so that computer programs read therefrom can be installed into the storage section 1008 as needed.

[0105] In particular, according to embodiments of the present invention, the processes described in the various method flow charts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for executing the methods shown in the flow charts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1009 and / or installed from removable media 1011. When executed by central processing unit 1001, the computer program performs the various functions defined in the system of the present invention.

[0106] It should be noted that the computer-readable medium shown in the embodiments of the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present invention, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0107] The contents of the method embodiments of the present invention are all applicable to the system embodiments. The functions specifically implemented by the system embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above methods.

[0108] Another aspect of an embodiment of the present invention further provides a computer-readable storage medium, wherein the storage medium stores a program, and the program is executed by a processor to implement the above method.

[0109] The contents of the method embodiments of the present invention are all applicable to the computer-readable storage medium embodiments. The functions specifically implemented by the computer-readable storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0110] The present invention also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the above method.

[0111] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the above-mentioned module, program segment, or a part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0112] It should be noted that although several modules of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to an embodiment of the present invention, the features and functions of two or more modules or units described above can be concretized in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0113] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present invention.

[0114] In some optional embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the boxes can sometimes be executed in reverse order. In addition, the embodiment presented and described in the flow chart of the present invention is provided in an exemplary manner for the purpose of providing a more comprehensive understanding of the technology. The disclosed method is not limited to the operation and logic flow presented herein. Optional embodiments are contemplated in which the order of the various operations is changed and the sub-operations described as a part of a larger operation are performed independently.

[0115] In addition, although the present invention is described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in separate physical devices or software modules. It will also be understood that a detailed discussion of the actual implementation of each module is not necessary for understanding the present invention. More specifically, given the properties, functions, and internal relationships of the various functional modules in the devices disclosed herein, the actual implementation of the module will be understood within the ordinary skill of an engineer. Therefore, a person skilled in the art will be able to implement the present invention as set forth in the claims using ordinary skill without undue experimentation. It will also be understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0116] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, and other media that can store program code.

[0117] The logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution apparatus, device, or apparatus (e.g., a computer-based apparatus, a device including a processor, or other apparatus that can fetch instructions from and execute instructions on an instruction execution apparatus, device, or apparatus). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution apparatus, device, or apparatus.

[0118] More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic devices), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering, or processing in another suitable manner as necessary, and then stored in a computer memory.

[0119] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution device. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0120] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0121] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to the embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the claims and their equivalents.

[0122] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the embodiments. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A method for managing terminal deployment information, characterized in that, including: Upon receiving an access instruction from a target terminal, obtaining the geographical location information and type identifier of the target terminal; Obtaining the regional information to which the target terminal belongs based on the geographical location information; Determining the regional distribution information of the target terminal based on the regional information; Determining the module type of the target terminal based on the type identifier; Performing visualization processing on the regional distribution information based on the module type.

2. The method for managing terminal deployment information according to claim 1, wherein The step of, upon receiving an access instruction from a target terminal, obtaining the geographical location information and type identifier of the target terminal, includes: Upon receiving an access instruction when the target terminal logs in to the platform, obtaining the geographical location information from a new field in the login message of the target terminal, and parsing the type identifier based on the login message.

3. The terminal deployment information management method according to claim 1, wherein The step of obtaining the regional information to which the target terminal belongs based on the geographical location information, includes: Determining the geographical location where the target terminal is located based on the geographical location information; Based on the geographical location, obtaining the regional information of the target terminal by combining a preset partition range.

4. The terminal deployment information management method according to claim 1, wherein The step of determining the regional distribution information of the target terminal based on the regional information, includes: Based on the identification information of the target terminal, obtaining the historical cache information of the target terminal; Comparing the regional information with the cache information, and determining the regional distribution information of the target terminal according to the comparison result.

5. The terminal deployment information management method according to claim 4, wherein The step of determining the regional distribution information of the target terminal according to the comparison result, includes: When the comparison result is inconsistent, determining the regional distribution information according to the regional information, and updating the cache information according to the regional information and the regional distribution information; Or, when the comparison result is consistent, directly referring to the regional distribution information in the cache information.

6. The terminal deployment information management method according to claim 1, wherein The step of determining the regional distribution information of the target terminal based on the regional information, includes: Through the perception protocol technology between terminals, using the target terminal to perform collaborative perception to obtain a list of terminals; the list of terminals includes a number of other target terminals perceived by the target terminal; Through the collaborative perception, obtaining the geographical location information of each target terminal in the list of terminals, and obtaining the regional information to which each target terminal in the list of terminals belongs based on the geographical location information of each target terminal in the list of terminals; Determining the regional distribution information of all target terminals based on the regional information of all target terminals.

7. The method for managing terminal deployment information according to claim 1, wherein The step of performing visualization processing on the regional distribution information based on the module type includes at least one of the following: Performing visualization processing on the regional distribution information based on the dimension corresponding to the module type; Performing visualization processing on the regional distribution information of a specific target terminal based on the module type.

8. A terminal deployment information management device, characterized in that, including: A first module for, upon receiving an access instruction from a target terminal, obtaining the geographical location information and type identifier of the target terminal; A second module for obtaining the regional information to which the target terminal belongs based on the geographical location information; A third module for determining the regional distribution information of the target terminal based on the regional information; The fourth module is configured to determine the module type of the target terminal according to the type identifier; The fifth module is configured to perform visualization processing on the area distribution information based on the module type.

9. An electronic device, characterized in that, It includes a processor and a memory; The memory is used to store programs; The processor executes the program to implement the method according to any one of claims 1 to 7.

10. A computer storage medium storing a program executable by a processor, characterized in that, The program executable by the processor, when executed by the processor, is used to implement the method according to any one of claims 1 to 7.

Images