Map-based enterprise data acquisition method, apparatus and device, and storage medium

Abstract

The invention discloses a map-based enterprise data acquisition method, device and equipment and a storage medium, based on a map, information of enterprises in a target map acquisition range is effectively acquired and processed by calling a map API, and meanwhile, automatic and accurate mail pushing is further performed on the enterprises according to the acquired data, so that the user experience is improved. The marketing efficiency of the user is improved, the labor cost is reduced, and the technical problems that manual collection is low in efficiency and high in success rate, and meanwhile precise marketing and rapid pushing are difficult to achieve are solved.

Description

Technical Field

[0001] The present application relates to the field of data collection technology, and in particular to a map-based enterprise data collection method, device, equipment and storage medium. Background Art

[0002] For individuals, businesses, and enterprises, in the daily operation process, in order to expand business and acquire customers, they often need to collect target customers' email, phone number, address and other information. Currently, data query and collection are usually done manually, such as Internet query or query through information marked on maps.

[0003] The collection of enterprise data by manpower has the disadvantages of low efficiency and high success rate, and it is difficult to achieve technical problems such as precise marketing and rapid push. Summary of the invention

[0004] The present application provides a map-based enterprise data collection method, device, equipment and storage medium, which solves the technical problems that human data collection is inefficient and has high success rate, but is difficult to achieve precise marketing and rapid push.

[0005] In view of this, the first aspect of the present application provides a map-based enterprise data collection method, the method comprising:

[0006] Step S1, determining a target map acquisition range, wherein the target map acquisition range includes a target point and an acquisition radius;

[0007] Step S2: by calling the map API interface, all enterprise information within the collection radius is acquired based on the target point, and enterprise information collection data is generated;

[0008] Step S3: parsing the enterprise information collection data, and generating data collection results including several enterprises based on a preset display template.

[0009] Optionally, after step S2 and before step S3, the following steps are further included:

[0010] The enterprise information collection data is cleaned and converted to convert the enterprise information collection data into a target format.

[0011] Optionally, after converting the enterprise information collection data into a target format, the method further includes:

[0012] The enterprise information collection data in the target format is stored through a relational database or a NoSQL database.

[0013] Optionally, the step S1 specifically includes:

[0014] Determine the target map collection range according to the target point and collection radius input by the user, where the target point is a coordinate point, city name, longitude and latitude, or target address;

[0015] or

[0016] The target map collection range is determined according to the range circled by the user in a preset shape in the target map.

[0017] Optionally, after step S3, the following steps are further included:

[0018] The data collection results are displayed visually.

[0019] Optionally, after step S3, the following steps are further included:

[0020] The push email is edited according to the email information included in the data collection result, and the push email is pushed according to the email information.

[0021] Optionally, step S3 further includes:

[0022] If the enterprise information collection data obtained through analysis does not exist in the preset display template, the newly added data items are analyzed based on the NPL natural language technology, and a new classification display is performed in the preset display template.

[0023] A second aspect of the present application provides a map-based enterprise data collection device, the device comprising:

[0024] A range determination unit, used to determine a target map acquisition range, wherein the target map acquisition range includes a target point and an acquisition radius;

[0025] A collection unit, configured to obtain all enterprise information within the collection radius based on the target point by calling a map API interface, and generate enterprise information collection data;

[0026] The processing unit is used to parse the enterprise information collection data and generate data collection results containing several enterprises based on a preset display template.

[0027] Optionally, it also includes:

[0028] The pre-processing unit is used to clean and convert the enterprise information collection data, and convert the enterprise information collection data into a target format.

[0029] Optionally, it also includes:

[0030] The storage unit is used to store the enterprise information collection data in a target format through a relational database or a NoSQL database.

[0031] Optionally, the range determination unit is specifically configured to:

[0032] Determine the target map collection range according to the target point and collection radius input by the user, where the target point is a coordinate point, city name, longitude and latitude, or target address;

[0033] or

[0034] The target map collection range is determined according to the range circled by the user in a preset shape in the target map.

[0035] Optionally, it also includes:

[0036] The display unit is used to visually display the data collection results.

[0037] Optionally, it also includes:

[0038] The push unit is used to edit the push email according to the email information contained in the data collection result, and push the push email according to the email information.

[0039] Optionally, the processing unit is further configured to:

[0040] If the enterprise information collection data obtained through analysis does not exist in the preset display template, the newly added data items are analyzed based on the NPL natural language technology, and a new classification display is performed in the preset display template.

[0041] A third aspect of the present application provides a map-based enterprise data collection device, the device comprising a processor and a memory:

[0042] The memory is used to store program code and transmit the program code to the processor;

[0043] The processor is used to execute the steps of the method for map-based enterprise data collection as described in the first aspect according to the instructions in the program code.

[0044] A fourth aspect of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store program code, and the program code is used to execute the method described in the first aspect above.

[0045] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0046] In the present application, a map-based enterprise data collection method, device, equipment and storage medium are provided. Based on the map, the map API is called to effectively collect and process information for enterprises within the target map collection range. At the same time, the enterprises are further automatically and accurately emailed based on the collected data, thereby improving the user's marketing efficiency and reducing labor costs. This solves the technical problem that human collection is inefficient, has high success rate, and is difficult to achieve accurate marketing and rapid push. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 A method flow chart of a map-based enterprise data collection method in an embodiment of the present application;

[0048] Figure 2 This is a schematic diagram of the structure of a map-based enterprise data collection device in an embodiment of the present application;

[0049] Figure 3 It is a structural diagram of a map-based enterprise data collection device in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0051] The present application designs a map-based enterprise data collection method, device, equipment and storage medium, which solves the technical problems that human data collection is inefficient and has high success rate, but is difficult to achieve precise marketing and rapid push.

[0052] For easier understanding, see Figure 1 , Figure 1 : is a method flow chart of the map-based enterprise data collection method in an embodiment of the present application, such as Figure 1 As shown, specifically:

[0053] Step S1, determining the target map acquisition range, the target map acquisition range includes the target point and the acquisition radius;

[0054] It should be noted that user input: allows users to define the target point by entering coordinate points, city names, longitude and latitude or specific addresses.

[0055] Interface interaction: Provides a map interface that allows users to define the collection range by dragging or drawing preset shapes (such as circles and rectangles).

[0056] Parameter settings: Users can set the collection radius and define the geographical scope of the search.

[0057] Step S2: by calling the map API interface, all enterprise information within the collection radius is obtained based on the target point, and enterprise information collection data is generated;

[0058] It should be noted that API selection: choose the appropriate map service API according to your needs, such as Google Maps API, Bing Maps API, etc.

[0059] Request construction: Build an API request, including parameters such as target point and collection radius.

[0060] Data acquisition: Send requests and receive enterprise information data returned by the API.

[0061] Furthermore, API parameter optimization: According to the API documentation, optimize the request parameters to improve the accuracy and efficiency of data acquisition.

[0062] Error handling: Implement error handling mechanisms, such as retry logic or error prompts when a request fails.

[0063] Data Caching: Consider implementing a data caching strategy to reduce the number of requests to your API and improve response speed.

[0064] Step S3: parse the enterprise information collection data and generate data collection results containing several enterprises based on a preset display template.

[0065] It should be noted that data parsing: parse the data returned by the API to extract key information, such as company name, address, contact information, etc. Data parsing tool: use JSON parser or XML parser to parse according to the returned data format.

[0066] Template application: Format the parsed data according to the preset display template. Template engine: Use the template engine to dynamically generate display templates to improve the customizability of the results.

[0067] Result generation: Generate a collection result list containing several enterprises.

[0068] Furthermore, after step S2 and before step S3, the following steps are further included:

[0069] Perform data cleaning and conversion on enterprise information collection data, and convert the enterprise information collection data into the target format.

[0070] It should be noted that data validation: checks the completeness and accuracy of data, such as verifying email format, phone number, etc. Automation script: writes automation scripts for data cleaning, such as removing duplicate records, correcting format errors, etc.

[0071] Data conversion: Convert data into a unified format for subsequent processing and storage.

[0072] Specifically:

[0073] First, analyze the data format returned by the API in detail, including data structure, field name, and data type.

[0074] Based on the data format returned by the API, adjust the preset template to match the new data structure. This may include adding, deleting, or modifying fields in the template.

[0075] Create a mapping process to map the data fields returned by the API to the fields required by the template. This may require writing custom conversion logic.

[0076] Design an intermediate data model that is compatible with the data format returned by the API and the preset template. Then, convert the API data into the intermediate model, and then convert it from the intermediate model to the format required by the template.

[0077] Write custom parsing functions or scripts to handle inconsistent data formats. These functions can extract, transform, and format data to conform to template requirements.

[0078] Use existing data conversion tools or libraries, such as JSON converter, XML converter, or ETL (Extract, Transform, Load) tools, to handle data format inconsistencies.

[0079] If the data structure returned by the API changes frequently, you can consider implementing a dynamic template generation system that can automatically adjust the template according to the actual structure of the data.

[0080] Implement an error handling mechanism during parsing and conversion to provide clear error information and take appropriate remedial measures when encountering data formats that do not conform to the expected format.

[0081] If the template is customized by users, provide a user feedback mechanism to allow users to report data formatting issues and make adjustments based on their feedback.

[0082] Update documentation and examples to reflect changes in data formats and new template adaptation methods to ensure users can understand and use the adjusted system.

[0083] Maintain data template versions so that when the API data format is updated, you can fall back to the old version of the template or gradually migrate to the new template.

[0084] Furthermore, after converting the enterprise information collection data into the target format, it also includes:

[0085] The enterprise information collection data is stored in the target format through a relational database or a NoSQL database.

[0086] It should be noted that database selection: choose a suitable database system based on data structure and query requirements.

[0087] Data import: Import the cleaned and converted data into the database.

[0088] Furthermore, step S1 is specifically as follows:

[0089] Determine the target map collection range based on the target point and collection radius input by the user. The target point is a coordinate point, city name, longitude and latitude, or target address;

[0090] or

[0091] The target map collection range is determined according to the range circled by the user in a preset shape in the target map.

[0092] It should be noted that user input: allows users to define the target point by entering coordinate points, city names, longitude and latitude or specific addresses.

[0093] Interface interaction: Provides a map interface that allows users to define the collection range by dragging or drawing preset shapes (such as circles and rectangles).

[0094] Parameter settings: Users can set the collection radius and define the geographical scope of the search.

[0095] Furthermore, after step S3, the following steps are further included:

[0096] Visualize the data collection results.

[0097] It should be noted that interface design is to design the user interface to display the map view and list view of the collection results. Specifically, you can use chart libraries (such as D3.js, Highcharts) to create interactive charts to display the collection results. You can also use the visualization function of the map service API to display the collection results in the form of geographic information.

[0098] Interactive functions: Provide search, filtering and sorting functions to enhance user experience.

[0099] Furthermore, after step S3, the following steps are further included:

[0100] The push email is edited and processed according to the email address information contained in the data collection results, and the push email is pushed according to the email address information.

[0101] It should be noted that email editing: based on the email information in the collection results, use the email template to edit the content.

[0102] Email sending: Use email service API, such as SMTP or third-party email services, to send emails in batches.

[0103] Furthermore, step S3 also includes:

[0104] If the enterprise information collection data obtained through analysis does not exist in the preset display template, the newly added data items are analyzed based on the NPL natural language technology, and a new classification display is performed in the preset display template.

[0105] It should be noted that data item analysis: uses NLP technology to analyze data items in newly collected enterprise information.

[0106] Template update: Based on the analysis results, a new category display is added to the preset display template.

[0107] Specifically:

[0108] Use NLP technology to conduct in-depth analysis of collected corporate information to identify key data items and potential marketing opportunities.

[0109] Based on the results of NLP analysis, customers are segmented into different groups, each with similar characteristics or needs.

[0110] Using the information obtained from NLP analysis, we customize email content for each customer group to ensure that the email content is highly relevant to the customer's interests and needs.

[0111] Use the dynamic content feature in email templates to automatically populate email content based on specific characteristics of your customers.

[0112] Tailor your email subject lines to increase open rates based on your customers’ interests and behaviors.

[0113] The overall process of enterprise data collection is as follows:

[0114] The user enters the target point and collection radius through the interface, or circles the range on the map.

[0115] The software constructs an API request based on user input and sends it.

[0116] Receive enterprise information data returned by the API and perform data cleansing and conversion (if necessary).

[0117] Parse the data and apply preset templates to generate collection results.

[0118] Store the results to a database (if required).

[0119] The acquisition results are displayed on the user interface, and visualization and interaction functions are provided.

[0120] Edit and send emails according to user needs.

[0121] Use NLP techniques to optimize display templates (if needed).

[0122] See also Figure 2 , Figure 2 Schematic diagram of the structure of the map-based enterprise data collection device in the embodiment of the present application. Figure 2 As shown, specifically:

[0123] A range determination unit 201 is used to determine a target map acquisition range, where the target map acquisition range includes a target point and an acquisition radius;

[0124] It should be noted that user input: allows users to define the target point by entering coordinate points, city names, longitude and latitude or specific addresses.

[0125] Interface interaction: Provides a map interface that allows users to define the collection range by dragging or drawing preset shapes (such as circles and rectangles).

[0126] Parameter settings: Users can set the collection radius and define the geographical scope of the search.

[0127] The collection unit 202 is used to obtain all enterprise information within the collection radius based on the target point by calling the map API interface, and generate enterprise information collection data;

[0128] It should be noted that API selection: choose the appropriate map service API according to your needs, such as Google Maps API, Bing Maps API, etc.

[0129] Request construction: Build an API request, including parameters such as target point and collection radius.

[0130] Data acquisition: Send requests and receive enterprise information data returned by the API.

[0131] Furthermore, API parameter optimization: According to the API documentation, optimize the request parameters to improve the accuracy and efficiency of data acquisition.

[0132] Error handling: Implement error handling mechanisms, such as retry logic or error prompts when a request fails.

[0133] Data Caching: Consider implementing a data caching strategy to reduce the number of requests to your API and improve response speed.

[0134] The processing unit 203 is used to parse the enterprise information collection data and generate data collection results including several enterprises based on a preset display template.

[0135] It should be noted that data parsing: parse the data returned by the API to extract key information, such as company name, address, contact information, etc. Data parsing tool: use JSON parser or XML parser to parse according to the returned data format.

[0136] Template application: Format the parsed data according to the preset display template. Template engine: Use the template engine to dynamically generate display templates to improve the customizability of the results.

[0137] Result generation: Generate a collection result list containing several enterprises.

[0138] Furthermore, it also includes:

[0139] The pre-processing unit is used to clean and convert the enterprise information collection data and convert the enterprise information collection data into a target format.

[0140] It should be noted that data validation: checks the completeness and accuracy of data, such as verifying email format, phone number, etc. Automation script: writes automation scripts for data cleaning, such as removing duplicate records, correcting format errors, etc.

[0141] Data conversion: Convert data into a unified format for subsequent processing and storage.

[0142] Specifically:

[0143] First, analyze the data format returned by the API in detail, including data structure, field name, and data type.

[0144] Based on the data format returned by the API, adjust the preset template to match the new data structure. This may include adding, deleting, or modifying fields in the template.

[0145] Create a mapping process to map the data fields returned by the API to the fields required by the template. This may require writing custom conversion logic.

[0146] Design an intermediate data model that is compatible with the data format returned by the API and the preset template. Then, convert the API data into the intermediate model, and then convert it from the intermediate model to the format required by the template.

[0147] Write custom parsing functions or scripts to handle inconsistent data formats. These functions can extract, transform, and format data to conform to template requirements.

[0148] Use existing data conversion tools or libraries, such as JSON converter, XML converter, or ETL (Extract, Transform, Load) tools, to handle data format inconsistencies.

[0149] If the data structure returned by the API changes frequently, you can consider implementing a dynamic template generation system that can automatically adjust the template according to the actual structure of the data.

[0150] Implement an error handling mechanism during parsing and conversion to provide clear error information and take appropriate remedial measures when encountering data formats that do not conform to the expected format.

[0151] If the template is customized by users, provide a user feedback mechanism to allow users to report data formatting issues and make adjustments based on their feedback.

[0152] Update documentation and examples to reflect changes in data formats and new template adaptation methods to ensure users can understand and use the adjusted system.

[0153] Maintain data template versions so that when the API data format is updated, you can fall back to the old version of the template or gradually migrate to the new template.

[0154] Furthermore, it also includes:

[0155] The storage unit is used to store the enterprise information collection data in a target format through a relational database or a NoSQL database.

[0156] It should be noted that database selection: choose a suitable database system based on data structure and query requirements.

[0157] Data import: Import the cleaned and converted data into the database.

[0158] Further, the range determination unit 201 is specifically used for:

[0159] Determine the target map collection range based on the target point and collection radius input by the user. The target point is a coordinate point, city name, longitude and latitude, or target address;

[0160] or

[0161] The target map collection range is determined according to the range circled by the user in a preset shape in the target map.

[0162] It should be noted that user input: allows users to define the target point by entering coordinate points, city names, longitude and latitude or specific addresses.

[0163] Interface interaction: Provides a map interface that allows users to define the collection range by dragging or drawing preset shapes (such as circles and rectangles).

[0164] Parameter settings: Users can set the collection radius and define the geographical scope of the search.

[0165] Furthermore, it also includes:

[0166] The display unit is used to visualize the data collection results.

[0167] It should be noted that interface design is to design the user interface to display the map view and list view of the collection results. Specifically, you can use chart libraries (such as D3.js, Highcharts) to create interactive charts to display the collection results. You can also use the visualization function of the map service API to display the collection results in the form of geographic information.

[0168] Interactive functions: Provide search, filtering and sorting functions to enhance user experience.

[0169] Furthermore, the processing unit 203 is further configured to:

[0170] The push email is edited and processed according to the email address information contained in the data collection results, and the push email is pushed according to the email address information.

[0171] It should be noted that email editing: based on the email information in the collection results, use the email template to edit the content.

[0172] Email sending: Use email service API, such as SMTP or third-party email services, to send emails in batches.

[0173] Furthermore, the processing unit 203 is further configured to:

[0174] If the enterprise information collection data obtained through analysis does not exist in the preset display template, the newly added data items are analyzed based on the NPL natural language technology, and a new classification display is performed in the preset display template.

[0175] It should be noted that data item analysis: uses NLP technology to analyze data items in newly collected enterprise information.

[0176] Template update: Based on the analysis results, a new category display is added to the preset display template.

[0177] Specifically:

[0178] Use NLP technology to conduct in-depth analysis of collected corporate information to identify key data items and potential marketing opportunities.

[0179] Based on the results of NLP analysis, customers are segmented into different groups, each with similar characteristics or needs.

[0180] Using the information obtained from NLP analysis, we customize email content for each customer group to ensure that the email content is highly relevant to the customer's interests and needs.

[0181] Use the dynamic content feature in email templates to automatically populate email content based on specific characteristics of your customers.

[0182] Tailor your email subject lines to increase open rates based on your customers’ interests and behaviors.

[0183] The overall process of enterprise data collection is as follows:

[0184] The user enters the target point and collection radius through the interface, or circles the range on the map.

[0185] The software constructs an API request based on user input and sends it.

[0186] Receive enterprise information data returned by the API and perform data cleansing and conversion (if necessary).

[0187] Parse the data and apply preset templates to generate collection results.

[0188] Store the results to a database (if required).

[0189] The acquisition results are displayed on the user interface, and visualization and interaction functions are provided.

[0190] Edit and send emails according to user needs.

[0191] Use NLP techniques to optimize display templates (if needed).

[0192] The present application embodiment also provides another map-based enterprise data collection device, such as Figure 3 For the sake of convenience, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the method part of the embodiments of the present application. The terminal can be any terminal device including a mobile phone, a tablet computer, a personal digital assistant (English full name: Personal Digital Assistant, English abbreviation: PDA), a sales terminal (English full name: Point of Sales, English abbreviation: POS), a car computer, etc., taking the terminal as a mobile phone as an example:

[0193] Figure 3FIG. 1 is a block diagram showing a partial structure of a mobile phone related to a terminal provided in an embodiment of the present application. Figure 3 The mobile phone includes: a radio frequency (RF) circuit 1010, a memory 1020, an input unit 1030, a display unit 1040, a sensor 1050, an audio circuit 1060, a wireless fidelity (WiFi) module 1070, a processor 1080, and a power supply 1090. Those skilled in the art can understand that Figure 3 The mobile phone structure shown in the figure does not constitute a limitation on the mobile phone, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0194] Combine the following Figure 3 A detailed introduction to the various components of the mobile phone:

[0195] The RF circuit 1010 can be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 1080 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 1010 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (full name: Low Noise Amplifier, English abbreviation: LNA), a duplexer, etc. In addition, the RF circuit 1010 can also communicate with the network and other devices through wireless communication. The above-mentioned wireless communications can use any communication standard or protocol, including but not limited to Global System of Mobile communications (Global System of Mobile communication, English abbreviation: GSM), General Packet Radio Service (General Packet Radio Service, GPRS), Code Division Multiple Access (Code Division Multiple Access, English abbreviation: CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (Long Term Evolution, English abbreviation: LTE), e-mail, Short Messaging Service (SMS), etc.

[0196] The memory 1020 can be used to store software programs and modules. The processor 1080 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1020. The memory 1020 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 1020 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0197] The input unit 1030 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile phone. Specifically, the input unit 1030 may include a touch panel 1031 and other input devices 1032. The touch panel 1031, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 1031 or near the touch panel 1031 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch panel 1031 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 1080, and can receive and execute the command sent by the processor 1080. In addition, the touch panel 1031 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1031, the input unit 1030 may further include other input devices 1032. Specifically, the other input devices 1032 may include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

[0198] The display unit 1040 can be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 1040 may include a display panel 1041. Optionally, the display panel 1041 may be configured in the form of a liquid crystal display (full name in English: Liquid Crystal Display, English abbreviation: LCD), an organic light-emitting diode (full name in English: Organic Light-Emitting Diode, English abbreviation: OLED), etc. Further, the touch panel 1031 may cover the display panel 1041. When the touch panel 1031 detects a touch operation on or near it, it is transmitted to the processor 1080 to determine the type of touch event. Subsequently, the processor 1080 provides a corresponding visual output on the display panel 1041 according to the type of touch event. Although in Figure 3 In the embodiment, the touch panel 1031 and the display panel 1041 are used as two independent components to realize the input and output functions of the mobile phone, but in some embodiments, the touch panel 1031 and the display panel 1041 can be integrated to realize the input and output functions of the mobile phone.

[0199] The mobile phone may also include at least one sensor 1050, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1041 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1041 and / or the backlight when the mobile phone is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0200] The audio circuit 1060, the speaker 1061, and the microphone 1062 can provide an audio interface between the user and the mobile phone. The audio circuit 1060 can transmit the received audio data to the speaker 1061 after converting the received audio data into an electrical signal, which is converted into a sound signal for output; on the other hand, the microphone 1062 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1060 and converted into audio data, and then the audio data is output to the processor 1080 for processing, and then sent to another mobile phone through the RF circuit 1010, or the audio data is output to the memory 1020 for further processing.

[0201] WiFi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages and access streaming media through the WiFi module 1070. It provides users with wireless broadband Internet access. Figure 3 A WiFi module 1070 is shown, but it is understandable that it is not an essential component of the mobile phone and can be omitted as needed without changing the essence of the invention.

[0202] The processor 1080 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and / or modules stored in the memory 1020 and calling data stored in the memory 1020, it executes various functions of the mobile phone and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 1080 may include one or more processing units; preferably, the processor 1080 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 1080.

[0203] The mobile phone also includes a power supply 1090 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 1080 through a power management system, so that the power management system can manage functions such as charging, discharging, and power consumption.

[0204] Although not shown, the mobile phone may also include a camera, a Bluetooth module, etc., which will not be described in detail here.

[0205] In the embodiment of the present application, the processor 1080 included in the terminal also has the following functions:

[0206] Step S1, determining the target map acquisition range, the target map acquisition range includes the target point and the acquisition radius;

[0207] It should be noted that user input: allows users to define the target point by entering coordinate points, city names, longitude and latitude or specific addresses.

[0208] Interface interaction: Provides a map interface that allows users to define the collection range by dragging or drawing preset shapes (such as circles and rectangles).

[0209] Parameter settings: Users can set the collection radius and define the geographical scope of the search.

[0210] Step S2: by calling the map API interface, all enterprise information within the collection radius is obtained based on the target point, and enterprise information collection data is generated;

[0211] It should be noted that API selection: choose the appropriate map service API according to your needs, such as Google Maps API, Bing Maps API, etc.

[0212] Request construction: Build an API request, including parameters such as target point and collection radius.

[0213] Data acquisition: Send requests and receive enterprise information data returned by the API.

[0214] Furthermore, API parameter optimization: According to the API documentation, optimize the request parameters to improve the accuracy and efficiency of data acquisition.

[0215] Error handling: Implement error handling mechanisms, such as retry logic or error prompts when a request fails.

[0216] Data Caching: Consider implementing a data caching strategy to reduce the number of requests to your API and improve response speed.

[0217] Step S3: parse the enterprise information collection data and generate data collection results containing several enterprises based on a preset display template.

[0218] It should be noted that data parsing: parse the data returned by the API to extract key information, such as company name, address, contact information, etc. Data parsing tool: use JSON parser or XML parser to parse according to the returned data format.

[0219] Template application: Format the parsed data according to the preset display template. Template engine: Use the template engine to dynamically generate display templates to improve the customizability of the results.

[0220] Result generation: Generate a collection result list containing several enterprises.

[0221] Furthermore, after step S2 and before step S3, the following steps are further included:

[0222] Perform data cleaning and conversion on enterprise information collection data, and convert the enterprise information collection data into the target format.

[0223] It should be noted that data validation: checks the completeness and accuracy of data, such as verifying email format, phone number, etc. Automation script: writes automation scripts for data cleaning, such as removing duplicate records, correcting format errors, etc.

[0224] Data conversion: Convert data into a unified format for subsequent processing and storage.

[0225] Furthermore, after converting the enterprise information collection data into the target format, it also includes:

[0226] The enterprise information collection data is stored in the target format through a relational database or a NoSQL database.

[0227] It should be noted that database selection: choose a suitable database system based on data structure and query requirements.

[0228] Data import: Import the cleaned and converted data into the database.

[0229] Specifically:

[0230] First, analyze the data format returned by the API in detail, including data structure, field name, and data type.

[0231] Based on the data format returned by the API, adjust the preset template to match the new data structure. This may include adding, deleting, or modifying fields in the template.

[0232] Create a mapping process to map the data fields returned by the API to the fields required by the template. This may require writing custom conversion logic.

[0233] Design an intermediate data model that is compatible with the data format returned by the API and the preset template. Then, convert the API data into the intermediate model, and then convert it from the intermediate model to the format required by the template.

[0234] Write custom parsing functions or scripts to handle inconsistent data formats. These functions can extract, transform, and format data to conform to template requirements.

[0235] Use existing data conversion tools or libraries, such as JSON converter, XML converter, or ETL (Extract, Transform, Load) tools, to handle data format inconsistencies.

[0236] If the data structure returned by the API changes frequently, you can consider implementing a dynamic template generation system that can automatically adjust the template according to the actual structure of the data.

[0237] Implement an error handling mechanism during parsing and conversion to provide clear error information and take appropriate remedial measures when encountering data formats that do not conform to the expected format.

[0238] If the template is customized by users, provide a user feedback mechanism to allow users to report data formatting issues and make adjustments based on their feedback.

[0239] Update documentation and examples to reflect changes in data formats and new template adaptation methods to ensure users can understand and use the adjusted system.

[0240] Maintain data template versions so that when the API data format is updated, you can fall back to the old version of the template or gradually migrate to the new template.

[0241] Furthermore, step S1 is specifically as follows:

[0242] Determine the target map collection range based on the target point and collection radius input by the user. The target point is a coordinate point, city name, longitude and latitude, or target address;

[0243] or

[0244] The target map collection range is determined according to the range circled by the user in a preset shape in the target map.

[0245] It should be noted that user input: allows users to define the target point by entering coordinate points, city names, longitude and latitude or specific addresses.

[0246] Interface interaction: Provides a map interface that allows users to define the collection range by dragging or drawing preset shapes (such as circles and rectangles).

[0247] Parameter settings: Users can set the collection radius and define the geographical scope of the search.

[0248] Furthermore, after step S3, the following steps are further included:

[0249] Visualize the data collection results.

[0250] It should be noted that interface design is to design the user interface to display the map view and list view of the collection results. Specifically, you can use chart libraries (such as D3.js, Highcharts) to create interactive charts to display the collection results. You can also use the visualization function of the map service API to display the collection results in the form of geographic information.

[0251] Interactive functions: Provide search, filtering and sorting functions to enhance user experience.

[0252] Furthermore, after step S3, the following steps are further included:

[0253] The push email is edited and processed according to the email address information contained in the data collection results, and the push email is pushed according to the email address information.

[0254] It should be noted that email editing: based on the email information in the collection results, use the email template to edit the content.

[0255] Email sending: Use email service API, such as SMTP or third-party email services, to send emails in batches.

[0256] Furthermore, step S3 also includes:

[0257] If the enterprise information collection data obtained through analysis does not exist in the preset display template, the newly added data items are analyzed based on the NPL natural language technology, and a new classification display is performed in the preset display template.

[0258] It should be noted that data item analysis: uses NLP technology to analyze data items in newly collected enterprise information.

[0259] Template update: Based on the analysis results, a new category display is added to the preset display template.

[0260] Specifically:

[0261] Use NLP technology to conduct in-depth analysis of collected corporate information to identify key data items and potential marketing opportunities.

[0262] Based on the results of NLP analysis, customers are segmented into different groups, each with similar characteristics or needs.

[0263] Using the information obtained from NLP analysis, we customize email content for each customer group to ensure that the email content is highly relevant to the customer's interests and needs.

[0264] Use the dynamic content feature in email templates to automatically populate email content based on specific characteristics of your customers.

[0265] Tailor your email subject lines to increase open rates based on your customers’ interests and behaviors.

[0266] The overall process of enterprise data collection is as follows:

[0267] The user enters the target point and collection radius through the interface, or circles the range on the map.

[0268] The software constructs an API request based on user input and sends it.

[0269] Receive enterprise information data returned by the API and perform data cleansing and conversion (if necessary).

[0270] Parse the data and apply preset templates to generate collection results.

[0271] Store the results to a database (if required).

[0272] The acquisition results are displayed on the user interface, and visualization and interaction functions are provided.

[0273] Edit and send emails according to user needs.

[0274] Use NLP techniques to optimize display templates (if needed).

[0275] An embodiment of the present application also provides a computer-readable storage medium for storing program code, wherein the program code is used to execute any one of the implementation methods of a map-based enterprise data collection method described in the aforementioned embodiments.

[0276] In the embodiments of the present application, a map-based enterprise data collection method, device, equipment and storage medium are provided. Based on the map, the map API is called to effectively collect and process information for enterprises within the target map collection range. At the same time, the enterprises are further automatically and accurately emailed based on the collected data, thereby improving the user's marketing efficiency and reducing labor costs. This solves the technical problem that human collection is inefficient, has high success rate, and is difficult to achieve accurate marketing and rapid push.

[0277] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0278] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0279] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0280] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0281] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0282] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0283] If the integrated unit 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 application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (full name in English: Read-Only Memory, English abbreviation: ROM), random access memory (full name in English: Random Access Memory, English abbreviation: RAM), disk or optical disk and other media that can store program codes.

[0284] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A map-based enterprise data collection method, characterized in that: include: Step S1, determining a target map acquisition range, wherein the target map acquisition range includes a target point and an acquisition radius; Step S2: by calling the map API interface, all enterprise information within the collection radius is acquired based on the target point, and enterprise information collection data is generated; Step S3: parsing the enterprise information collection data, and generating data collection results including several enterprises based on a preset display template.

2. The data collection method according to claim 1, characterized in that: After step S2 and before step S3, the following further includes: The enterprise information collection data is cleaned and converted to convert the enterprise information collection data into a target format.

3. The data collection method according to claim 2, characterized in that: After converting the enterprise information collection data into a target format, the following step further includes: The enterprise information collection data in the target format is stored through a relational database or a NoSQL database.

4. The data collection method according to claim 1, characterized in that: The step S1 is specifically as follows: Determine the target map collection range according to the target point and collection radius input by the user, where the target point is a coordinate point, city name, longitude and latitude, or target address; or The target map collection range is determined according to the range circled by the user in a preset shape in the target map.

5. The data collection method according to claim 1, characterized in that: After step S3, the following steps are also included: The data collection results are displayed visually.

6. The data collection method according to claim 1, characterized in that: After step S3, the following steps are also included: The push email is edited according to the email information included in the data collection result, and the push email is pushed according to the email information.

7. The data collection method according to claim 1, characterized in that: The step S3 also includes: If the enterprise information collection data obtained through analysis does not exist in the preset display template, the newly added data items are analyzed based on the NPL natural language technology, and a new classification display is performed in the preset display template.

8. A data acquisition device, characterized in that: include: A range determination unit, used to determine a target map acquisition range, wherein the target map acquisition range includes a target point and an acquisition radius; A collection unit, configured to obtain all enterprise information within the collection radius based on the target point by calling a map API interface, and generate enterprise information collection data; The processing unit is used to parse the enterprise information collection data and generate data collection results containing several enterprises based on a preset display template.

9. A map-based enterprise data collection device, characterized in that: The device comprises a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the map-based enterprise data collection method according to any one of claims 1 to 7 according to the instructions in the program code.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store program codes, and the program codes are used to execute the map-based enterprise data collection method according to any one of claims 1 to 7.

Images