Data sending method and system, electronic device and storage medium
By establishing data identification and regional protocol processing on the POS terminal, a data acquisition strategy is generated, which solves the problems of high system deployment costs and maintenance difficulties caused by different regional protocols, and realizes a unified data collection scheme.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHENZHEN XINGUODU TECH
- Filing Date
- 2023-06-15
- Publication Date
- 2026-06-16
Smart Images

Figure CN116828048B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a data transmission method, system, electronic device and storage medium. Background Technology
[0002] When electronic products complete card payments via NFC (Near Field Communication) through POS software installed on a POS terminal (Point of Sale Terminal), data collection according to regional protocols is required to ensure smooth transaction processing. However, since regional protocols often differ across regions, the required data also varies. Current technologies that deploy systems tailored to different regional protocols are not only costly to develop but also hinder unified maintenance. Summary of the Invention
[0003] The main objective of this application is to provide a data transmission method, system, electronic device, and storage medium that can reduce system development costs and decrease system maintenance difficulty.
[0004] To achieve the above objectives, a first aspect of this application proposes a data transmission method applied to a backend management terminal, the method comprising:
[0005] An initial dataset is established, and the data items in the initial dataset are preprocessed to attach data identifiers to the data items. Based on the data identifiers, the data items are categorized into corresponding object tags. In response to a policy acquisition request from a POS terminal, a first region where the POS terminal is located and the corresponding regional protocol are determined. According to the regional protocol, data items in the object tags are enabled or disabled, and a data acquisition policy is generated based on the enabled and disabled data items. The data acquisition policy is then sent to the POS terminal so that the POS terminal can collect data items according to the data acquisition policy.
[0006] According to some embodiments of this application, the step of establishing an initial dataset, preprocessing the data items in the initial dataset to attach data identifiers to the data items, and classifying the data items into corresponding object labels based on the data identifiers includes: establishing an initial dataset and adjusting the format of the data items in the dataset according to a preset format; identifying the formatted data items to obtain data item identifiers corresponding to each data item; obtaining object label partitioning rules; and classifying the data items into corresponding object labels based on the partitioning rules and the data item identifiers.
[0007] According to some embodiments of this application, the step of enabling or disabling data items in the object tag according to the regional protocol, and generating a data acquisition strategy based on the obtained enabled and disabled data items, includes: generating target data identifiers for enabled and disabled data items according to the regional protocol; searching for the enabled and disabled data items in the object tag according to the target data identifiers; enabling the enabled data items, disabling the disabled data items, and summarizing the obtained enabled and disabled data items to generate a data acquisition strategy; wherein the enabled data items are allowed to be accessed in the POS terminal, and the disabled data items are prohibited from being accessed in the POS terminal.
[0008] According to some embodiments of this application, after generating the data acquisition strategy, the method further includes: saving the data acquisition strategy and establishing a mapping relationship between the data acquisition strategy and the first region, so that when a data acquisition strategy acquisition request sent by the POS terminal is received, the data acquisition strategy can be directly invoked through the mapping relationship; and periodically maintaining and updating the data acquisition strategy corresponding to the first region.
[0009] According to some embodiments of this application, the method further includes: based on the policy acquisition request, checking whether a data acquisition policy corresponding to the first region is stored locally; if the data acquisition policy corresponding to the first region is found, sending the data acquisition policy to the POS terminal.
[0010] According to some embodiments of this application, the backend management terminal is configured with a default data acquisition strategy, and the method further includes: if the location information transmitted by the POS terminal is not received, then the default data acquisition strategy is sent to the POS terminal; or, if the data acquisition strategy acquisition request sent by the POS terminal does not include the regional protocol corresponding to the first region, then the default data acquisition strategy is sent to the POS terminal.
[0011] To achieve the above objectives, a second aspect of this application provides a data transmission method applied to a POS terminal. The method includes: responding to a target dataset acquisition instruction, acquiring the terminal's execution permissions, the location information of the terminal in a first region, and the regional protocol corresponding to the first region; sending a policy acquisition request to a backend management terminal, so that the backend management terminal enables or disables data items in the object tag according to the regional protocol, thereby generating a data acquisition policy; wherein the policy acquisition request includes the location information of the first region and the regional protocol corresponding to the first region; receiving the data acquisition policy, collecting target data items according to the data acquisition policy, and generating a target dataset based on the collected target data items; and uploading the target dataset to the backend management terminal.
[0012] To achieve the above objectives, a third aspect of this application provides a data transmission system applied to a backend management terminal. The system includes: a preprocessing module, configured to establish an initial dataset, preprocess data items in the initial dataset to attach data identifiers to the data items, and classify the data items into corresponding object tags based on the data identifiers; a regional protocol acquisition module, configured to respond to a policy acquisition request from a POS terminal, determine a first region where the POS terminal is located and the regional protocol corresponding to the first region; a data acquisition policy generation module, configured to enable or disable data items in the object tags according to the regional protocol, and generate a data acquisition policy based on the obtained enabled and disabled data items; and a data item collection module, configured to distribute the data acquisition policy to the POS terminal, so that the POS terminal collects data items according to the data acquisition policy.
[0013] To achieve the above objectives, a fourth aspect of the present application provides an electronic device, the electronic device including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method described in the first aspect of the embodiment.
[0014] To achieve the above objectives, a fifth aspect of the present application provides a storage medium, which is a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in the first aspect of the present application.
[0015] The data transmission method, system, electronic device, and storage medium proposed in this application establish an initial dataset, preprocess the data items in the initial dataset to attach data identifiers to the data items, and classify the data items into corresponding object tags based on the data identifiers. Responding to a policy acquisition request from a POS terminal, the system determines the first region where the POS terminal is located and the corresponding regional protocol. Based on the regional protocol, it enables or disables the data items in the object tags, generates a data acquisition policy based on the enabled and disabled data items, and sends the data acquisition policy to the POS terminal so that the POS terminal can collect data items according to the policy. This allows all regions to share a single system. The system can generate corresponding data acquisition policies based on the regional protocols of different regions, and the POS terminal directly collects data items according to the data acquisition policy. Therefore, it is unnecessary to deploy the system specifically for different regions based on their regional protocols, reducing system development costs and maintenance difficulty. Attached Figure Description
[0016] Figure 1 This is a schematic diagram of the structure of the data transmission system provided in the embodiments of this application;
[0017] Figure 2 This is a flowchart of the data transmission method provided in the embodiments of this application;
[0018] Figure 3 This is a display diagram of data items in the backend management interface.
[0019] Figure 4 yes Figure 2 The flowchart of step S101 in the text;
[0020] Figure 5 yes Figure 2 The flowchart of step S103 in the process;
[0021] Figure 6 This is one of the flowcharts following the generation of the data acquisition strategy;
[0022] Figure 7 This is one of the flowcharts for the data sending method;
[0023] Figure 8 This is a flowchart of a data transmission method provided in another embodiment of this application;
[0024] Figure 9 This is a flowchart illustrating an overall scheme of an embodiment of this application;
[0025] Figure 10 This is a schematic diagram of the functional modules of the data transmission system provided in the embodiments of this application;
[0026] Figure 11 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0027] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0028] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.
[0029] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.
[0030] When electronic products use NFC (Near Field Communication) to complete card payments via a POS terminal (Point of Sale Terminal), data collection according to regional protocols is required to ensure smooth transaction processing. Because NFC technology has a wide range of applications, different regions have different regulations and standards for its use. Therefore, to ensure NFC compatibility and reliability in different regions, data collection and processing need to be performed according to the regional protocols of each region. However, due to the differences in regional protocols, the data that needs to be collected also varies. This necessitates that technical personnel deploy and develop systems specifically according to the regulations and standards of different regions, increasing the difficulty and cost of development. Furthermore, the fact that regulations and standards in different regions can change at any time also presents a significant challenge to unified maintenance.
[0031] Based on this, embodiments of this application provide a data transmission method, system, electronic device, and storage medium that can generate corresponding data acquisition strategies according to the regional protocols of different regions. The POS terminal directly collects data items according to the data acquisition strategies. Therefore, it is not necessary to deploy the system specifically for different regions according to the regional protocols of different regions, which reduces the development cost of the system and reduces the maintenance difficulty of the system.
[0032] The data transmission method, system, electronic device, and storage medium provided in this application are specifically described through the following embodiments. First, the data transmission system in this application is described.
[0033] Please refer to Figure 1 In some embodiments, the data transmission system includes a data acquisition strategy forming module 101, a data acquisition strategy issuing module 102, a processing module 103, a dataset uploading module 104, and a storage module 105.
[0034] In some embodiments, the processing module 103 can be the nerve center and command center of the data transmission system. The processing module 103 can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions. In some embodiments, the processing module 103 can control the data acquisition strategy forming module 101 to generate data acquisition strategies according to the regional protocols of each region, and can control the data acquisition strategy distribution module 102 to distribute the data acquisition strategies to the POS terminal. After the POS terminal aggregates the collected data items into a dataset, the dataset is then uploaded to the backend management terminal through the dataset upload module 104.
[0035] In some embodiments, the storage module 105 can store instructions or data that the processing module 103 has just used or that are used repeatedly. If the processing module 103 needs to use the instruction or data again, it can directly retrieve it from the storage module 105, thereby avoiding repeated access, reducing the waiting time of the processing module 103, and thus improving the efficiency of the system. In some embodiments, the storage module can also store the generated data acquisition strategies corresponding to each region, so that when the corresponding region requests a data acquisition strategy again, the corresponding strategy can be directly sent to the POS terminal.
[0036] The data transmission method in this application can be described through the following embodiments.
[0037] It should be noted that in all specific embodiments of this application, when processing data related to user identity or characteristics, such as user information, user behavior data, user historical data, and user location information, user permission or consent is obtained first. For example, when obtaining user data access requests, user permission or consent is always obtained first. Furthermore, the collection, use, and processing of this data comply with relevant laws, regulations, and standards. In addition, when embodiments of this application need to obtain sensitive personal information of users, separate permission or consent from the user is obtained through pop-ups or redirection to a confirmation page. Only after obtaining the user's separate permission or consent is the necessary user-related data for the normal operation of embodiments of this application obtained.
[0038] Figure 2 This is an optional flowchart of the data sending method provided in the embodiments of this application. The method is applied to the backend management terminal. Figure 2 The method may include, but is not limited to, steps S101 to S104.
[0039] Step S101: Establish an initial dataset, preprocess the data items in the initial dataset to attach data identifiers to the data items, and classify the data items into the corresponding object labels according to the data identifiers;
[0040] Step S102: In response to the data acquisition strategy acquisition request of the POS terminal, determine the first region where the POS terminal is located and the region protocol corresponding to the first region;
[0041] Step S103: According to the regional protocol, enable or disable the data items in the object label, and generate a data acquisition strategy based on the enabled and disabled data items.
[0042] Step S104: The data acquisition strategy is sent to the POS terminal so that the POS terminal can collect data items according to the data acquisition strategy.
[0043] In some embodiments, a POS terminal refers to a point-of-sale (POS) terminal. A POS terminal, equipped with POS software, can replace a traditional POS machine and perform data collection. In some embodiments, NFC (Near Field Communication) refers to a wireless communication technology commonly used in mobile payments. It is understood that a POS terminal can implement NFC payment functionality by connecting to an NFC card reader. Specifically, when a customer uses a bank card or electronic device with NFC information to pay, they only need to place the card or electronic device near the POS terminal to complete the payment process. In some embodiments, the POS terminal communicates with an NFC card reader to read payment information from the customer's card or mobile phone and complete the payment.
[0044] In some embodiments, the back-end management terminal is built on and controlled by the data transmission system. In some embodiments, POS terminals in different regions share a single back-end management terminal. The back-end management terminal can process regional protocols, generate data acquisition strategies based on these protocols, and then distribute these strategies to the POS terminals. In some embodiments, the back-end management terminal can also view sales data, transaction volume, customer information, etc., based on the datasets sent by the POS terminals, for business analysis and decision-making. In some embodiments, the back-end management terminal can generate various statistical reports based on the datasets sent by the POS terminals, such as turnover, sales revenue, and customer numbers.
[0045] In some embodiments, the initial dataset is a collection formed by summarizing all data items related to the regional protocols across all regions. It is understood that since data items in most regional protocols often overlap, all collected data items can be labeled with data identifiers. In some embodiments, data identifiers can include transaction amount, transaction time, transaction location, transaction method, name, mobile phone number, ID card number, bank card number, Alipay account, WeChat Pay account, POS machine model, device serial number, operating system version, system logs, and exception information. Furthermore, data items can also be identified using Arabic numerals or English letters, such as labeling the transaction amount as 1 and the transaction time as 2, or labeling the transaction amount as A and the transaction time as B, etc.
[0046] In some embodiments, data items can be categorized into corresponding object tags based on data identifiers. In some embodiments, data items can be identified hierarchically or by category. For example, the following methods can be used: different types of data items can be categorized into corresponding object tags, such as transaction data, personal information, account information, device information, etc. In some embodiments, for specific data items under each category, such as transaction amount, transaction time, transaction location, etc., under transaction data, object tags can be used. In some embodiments, personal information such as name, mobile phone number, and ID card number can be categorized into the personal information object tag. In some embodiments, data items related to the POS machine itself, such as device number and operating system version under device information, can also be categorized under the corresponding object tag for the POS machine. It is understood that by classifying data items using data identifiers and object tags, different types of data items can be more clearly understood, thereby better protecting user privacy. Simultaneously, it also facilitates the system in quickly finding relevant data items based on regional policies.
[0047] In some embodiments, the first region can be any region divided according to geographical location, including cross-regional division, cross-city division, cross-provincial division, or cross-country division, etc., and this application embodiment does not impose specific limitations in this regard. In some embodiments, the back-end management terminal can respond to the data acquisition policy request of the POS terminal. Since the data acquisition policy request includes the location information of the first region where the POS terminal is located and the regional protocol corresponding to the first region, the first region where the POS terminal is located and the regional protocol corresponding to the first region can be determined according to the data acquisition policy request.
[0048] In some embodiments, a regional protocol is a document instructing a website or mobile application (in this application, a POS terminal) how to collect and use data items. In some embodiments, the POS terminal can enable or disable data items in object tags according to the regional protocol, and generate a data acquisition strategy based on the enabled and disabled data items. For example, if the regional protocol of the first region allows the acquisition of transaction time and name but prohibits the acquisition of operating system version, then the backend management terminal can find the corresponding data item based on the object tag and manage the enabling or disabling of the data item according to the regional protocol. For example, the corresponding object tag can be found through the regional protocol. For instance, if the object tag for transaction time is transaction data, then the transaction data can be found, and the transaction time can be enabled within the transaction data; in some embodiments, if the object tag for name is personal information, then the personal information can be found, and the name can be enabled within the personal information; in some embodiments, if the object tag for operating system version is device information, then the device information can be found, and the operating system version can be enabled within the device information. Understandably, in the final generated data acquisition strategy, if a corresponding data item is enabled, the POS terminal can collect data for that data item; if the corresponding data item is disabled, the POS terminal will prohibit data collection for that data item. It is also understood that regardless of whether the backend management terminal enables or disables a data item, the operation is based on the regional protocol.
[0049] Furthermore, the backend management system can search for all data items within the object's regional protocol based on the object's tag, and enable or disable the corresponding data items according to the regional protocol, ultimately generating a data acquisition policy. In some embodiments, a universal tag can also be set, which includes data items that are allowed to be accessed in all regional protocols. In this case, no additional enabling or disabling processing is required when generating the data acquisition policy.
[0050] In some embodiments, after the back-end management terminal sends a data acquisition strategy to the POS terminal, the POS terminal can collect data items according to the data acquisition strategy, and then summarize the collected data items as the target dataset for uploading.
[0051] Please refer to Figure 3 The backend management system can maintain and manage the target dataset sent by the POS terminal. Furthermore, it can place data items under the same data item identifier and display the corresponding data item's area, whether the data item is enabled or disabled, etc.
[0052] Understandably, the back-end management terminal can back up data based on the target dataset sent by the POS terminal to prevent data loss. In some embodiments, the back-end management terminal can perform statistical analysis on the dataset. In some embodiments, the POS terminal can support data sharing among multiple devices; after the collected data is sent to the back-end management terminal, data synchronization can be achieved, facilitating data sharing among multiple terminal devices.
[0053] The data transmission method, system, electronic device, and storage medium proposed in this application establish an initial dataset, preprocess the data items in the initial dataset to attach data identifiers to the data items, and classify the data items into corresponding object tags based on the data identifiers. Responding to a policy acquisition request from a POS terminal, the system determines the first region where the POS terminal is located and the corresponding regional protocol. Based on the regional protocol, it enables or disables the data items in the object tags, generates a data acquisition policy based on the enabled and disabled data items, and sends the data acquisition policy to the POS terminal so that the POS terminal can collect data items according to the policy. This allows all regions to share a single system. The system can generate corresponding data acquisition policies based on the regional protocols of different regions, and the POS terminal directly collects data items according to the data acquisition policy. Therefore, it is unnecessary to deploy the system specifically for different regions based on their regional protocols, reducing system development costs and maintenance difficulty.
[0054] Please refer to Figure 4 Step S101 includes, but is not limited to, steps S201 to S204:
[0055] Step S201: Establish an initial dataset and adjust the format of the data items in the dataset according to a preset format;
[0056] Step S202: Identify the data items after format adjustment to obtain the data item identifiers corresponding to each data item;
[0057] Step S203: Obtain the classification rules for object labels;
[0058] Step S204: According to the partitioning rules and data item identifiers, classify the data items into the corresponding object labels.
[0059] In some embodiments, the back-end management terminal can collect data based on regional policies for all regions and extract data items related to those policies. It is understood that in a POS terminal, data items in the initial dataset may originate from multiple regions and have significantly different formats; for example, the language of the regional policy may differ for each region, such as Chinese, English, or other languages. It is also understood that, to facilitate the processing of these data items, the POS terminal allows users to adjust the format of the data items according to preset formats. In some embodiments, rules can be set to ensure that all data items conform to the same format requirements. For example, the language of various regional protocols can be unified, such as setting all to English or Chinese. In some embodiments, the display format of data items can be set, such as setting currency amounts to display only two decimal places, or setting the date format to year-month-day. This allows the back-end management terminal and the POS terminal to process this data more efficiently and reduces the possibility of errors.
[0060] In some embodiments, the formatted data items can be identified to obtain data item identifiers corresponding to each data item. For example, each data item can be numbered, and the number can be Arabic numerals or English letters, such as identifying the transaction amount as 1 and the transaction time as 2, or identifying the transaction amount as A and the transaction time as B, etc. It is understood that the data item identifiers corresponding to data items are not limited to the above-mentioned identification methods, and this application embodiment will not elaborate on them.
[0061] In some embodiments, segmentation rules can be set, which can be categorization rules, such as setting segmentation rules for name-based object tag retrieval. Based on the segmentation rules and data item identifiers, data items are categorized into corresponding object tags. Specifically, data items such as transaction amount, transaction time, and transaction location can be defined and assigned to the object tags for transaction data. In some embodiments, names, mobile phone numbers, and ID card numbers can be assigned to the object tags for personal information.
[0062] Please refer to Figure 5 In some embodiments, step S103 includes, but is not limited to, steps S301 to S303:
[0063] Step S301: Generate target data identifiers for enabled and disabled data items according to the regional protocol;
[0064] Step S302: Based on the target data identifier, locate the enabled data item and disabled data item in the object label;
[0065] Step S303: Enable the enabled data items, disable the disabled data items, and summarize the enabled and disabled data items to generate a data acquisition strategy; wherein, enabled data items are allowed to be accessed in the POS terminal, and disabled data items are prohibited from being accessed in the POS terminal.
[0066] In some embodiments, data items contained in the regional protocol, such as transaction amount, name, etc., can be extracted, and keywords of the regional protocol can be extracted, such as data items that prohibit the collection of transaction amount, data items that allow the collection of name, etc., and the data items can be enabled or disabled based on these keywords.
[0067] In some embodiments, the backend management terminal can determine whether a data item is enabled or disabled based on the data items and keywords mentioned in the regional protocol. After the determination is completed, the corresponding target data identifier is added, such as the transaction amount identifier being 1 and the transaction time identifier being 2. It is understood that the target data identifier should correspond one-to-one with the data identifier of the data item in the object label for easy retrieval.
[0068] In some embodiments, based on a data identifier, such as 1, the corresponding data item can be quickly located in the object label, and the data item can be enabled or disabled. After enabling or disabling all data items involved in the regional protocol, all designed data items are summarized to generate a data acquisition strategy.
[0069] Understandably, enabled data items are allowed access in the POS terminal, while disabled data items are prohibited from access. In other words, the POS terminal can access the enabled data items according to its data acquisition strategy, while refraining from accessing the designed disabled data items. It can then aggregate all the collected enabled data items to generate a target dataset, which is then sent to the backend management system.
[0070] Please refer to Figure 6 After generating the data acquisition strategy, steps S401 to S402 are also included:
[0071] Step S401: Save the data acquisition strategy and establish a mapping relationship between the data acquisition strategy and the first area, so that when a data acquisition strategy acquisition request is received from the POS terminal, the data acquisition strategy can be directly invoked through the mapping relationship;
[0072] Step S402: Regularly maintain and update the data acquisition strategy corresponding to the first region.
[0073] In some embodiments, after generating a data acquisition strategy on the backend management terminal, the data acquisition strategy can be locally saved while being sent to the POS terminal, and a mapping relationship between the data acquisition strategy and the first region can be established. For example, after establishing the mapping relationship between the data acquisition strategy and region A, when the POS terminal subsequently initiates a request to obtain the data acquisition strategy for region A, the backend management terminal can directly send the locally saved data acquisition strategy request for region A, without having to regenerate the data acquisition strategy according to the regional policy.
[0074] In some embodiments, the backend management system can periodically maintain and update the data acquisition strategy corresponding to the first region. If the regional protocol of the first region is updated, the data acquisition strategy can be adjusted according to the updated part. For example, if the original regional protocol allowed the collection of names, and the updated regional protocol prohibits the collection of names, then the corresponding data acquisition strategy must also be adjusted accordingly, setting the name data item to prohibit acquisition.
[0075] Please refer to Figure 7 In some embodiments, the data transmission method further includes steps S501 to S502:
[0076] Step S501: Based on the policy acquisition request, check whether the data acquisition policy corresponding to the first region is stored locally;
[0077] Step S502: If the data acquisition strategy corresponding to the first region is found, the data acquisition strategy is sent to the POS terminal.
[0078] In some embodiments, after receiving a data acquisition strategy request from a POS terminal, the backend management terminal can check whether the data acquisition strategy corresponding to the first region is stored locally, based on the regional protocol. If the corresponding data acquisition strategy is found locally, it is directly sent to the POS terminal.
[0079] If no data acquisition strategy is found for the first region, a data acquisition strategy is generated based on the region protocol sent by the POS terminal and then sent to the POS terminal.
[0080] In some embodiments, the backend management terminal is configured with a default data acquisition strategy, and the data sending method further includes:
[0081] If the location information transmitted by the POS terminal is not received, the default data acquisition strategy will be sent to the POS terminal.
[0082] Alternatively, if the data acquisition policy request sent by the POS terminal does not include the regional protocol corresponding to the first region, the default data acquisition policy will be sent to the POS terminal.
[0083] In some embodiments, the back-end management terminal is configured with a default data acquisition strategy. The default data acquisition strategy is the strategy issued to the POS terminal when the back-end management terminal is unable to generate a new data acquisition strategy based on the existing data.
[0084] In some embodiments, when the POS terminal does not carry the location information of the first region in the data acquisition policy acquisition request, the back-end management terminal will send a default data acquisition policy to the POS terminal because the region protocol of the corresponding first region cannot be obtained based on the location information.
[0085] In some embodiments, if no regional protocol is set for the first region, it means that all data acquisition strategies apply to the first region. Therefore, the back-end management terminal can directly send the default data acquisition strategy to the POS terminal.
[0086] Please refer to Figure 8 , Figure 8 Another data transmission method is proposed for use in POS terminals, including but not limited to steps S601 to S604:
[0087] Step S601: In response to the target dataset acquisition instruction, acquire the location information of the terminal in the first region and the region protocol corresponding to the first region;
[0088] Step S602: Send a policy acquisition request to the backend management terminal so that the backend management terminal can enable or disable the data items in the object tag according to the regional protocol and generate a data acquisition policy; wherein, the policy acquisition request includes the location information of the first region and the regional protocol corresponding to the first region;
[0089] Step S603: Receive the data acquisition strategy, collect the target data items according to the data acquisition strategy, and generate the target dataset based on the collected target data items;
[0090] Step S604: Upload the target dataset to the backend management terminal.
[0091] In some embodiments, the terminal can be any electronic device that supports NFC payment. In some embodiments, when NFC is brought close to the terminal, the terminal's sensing area quickly senses the NFC transaction instruction, thereby activating the POS terminal and sending a target dataset acquisition instruction to the POS terminal. In some embodiments, after receiving the target dataset acquisition instruction, the POS terminal first obtains execution permission for subsequent data collection. In some embodiments, the POS terminal also needs to obtain the location information corresponding to the first area where the terminal is located. Specifically, if the terminal has GPS (Global Positioning System) functionality, the POS terminal can obtain its current location information via GPS. In some embodiments, the POS terminal can obtain location information by querying the IP (Internet Protocol) address of the network to which the terminal is connected. In some embodiments, the terminal can obtain its location information by scanning surrounding WIFI (Wireless Fidelity) signals and synchronizing the location information to the POS terminal, etc.
[0092] In some embodiments, since the data acquisition strategy is generated based on the regional protocol, it is necessary to obtain the regional protocol of the first region. In some embodiments, the first region can be directly searched based on the location information of the first region.
[0093] In some embodiments, after obtaining the location information of the first region and the regional protocol corresponding to the first region, the POS terminal sends a policy acquisition request to the back-end management terminal so that the back-end management terminal can enable or disable the data items in the object tag according to the regional protocol. That is, it can determine whether the data items should be enabled or disabled according to the requirements of the regional protocol.
[0094] In some embodiments, based on the data item identifier, such as name identifier 1, the corresponding object tag can be found based on 1, and the data items in the object tag can be mapped one-to-one with the regional protocol, so that the backend management terminal can enable or disable the target data item more quickly.
[0095] In some embodiments, a data acquisition policy is generated after the back-end management terminal enables or disables all data items related to the regional protocols. It is understood that the data acquisition policy includes all data items that instruct the POS terminal to enable or disable.
[0096] In some embodiments, after receiving a data acquisition strategy, the POS terminal collects data items according to the strategy. For example, enabled data items are collected, while disabled data items are not. All collected enabled data items are then aggregated as target data items to generate a target dataset. In some embodiments, after generating the target dataset, the POS terminal sends the target dataset to the backend management terminal.
[0097] In some embodiments, for areas where location information cannot be obtained, or areas where no regional protocol is set, it is not necessary to send a data acquisition strategy request to the backend management terminal; the default dataset can be uploaded directly. Alternatively, after the default data acquisition strategy is issued by the backend management terminal, data items can be collected to obtain the default dataset, and then the dataset can be uploaded.
[0098] Please refer to Figure 9 This application combines Figure 9 A general embodiment of the technical solution is provided. In some embodiments, after receiving a request from the POS terminal to obtain a data acquisition strategy, the backend management terminal determines whether the request includes the upload of location information for a first region. If the request does not include the upload of location information for the first region, the default data acquisition strategy of the POS terminal is applied. Alternatively, if the request includes the upload of location information for the first region, the region to which the first region belongs is determined.
[0099] Furthermore, after obtaining the location information of the first region, the backend management terminal can check if a data acquisition strategy with a mapping relationship to the first region exists locally. If a corresponding data acquisition strategy exists locally, it is directly sent to the POS terminal. If no corresponding data acquisition strategy exists locally, the data items in the object tag are enabled or disabled according to the regional protocol corresponding to the first region. This process continues until all regional protocols involved in the regional protocol have been processed. Based on the processing results, a data acquisition strategy is generated and sent to the POS terminal.
[0100] Furthermore, after the data acquisition strategy is sent from the back-end management terminal to the POS terminal, the POS terminal will collect and process the enabled data items according to the data acquisition strategy, and will not collect or process the disabled data items. After the POS terminal has collected all the data items required to be enabled by the data acquisition strategy, it will summarize the data items to form the target dataset and upload it to the back-end management terminal.
[0101] It is understood that the data transmission method proposed in this application is not limited to the above embodiments. The method proposed in this application does not require separate system deployment according to different regional protocols, which reduces the cost and difficulty of system deployment and facilitates unified maintenance of the system in the future.
[0102] Furthermore, the backend management system can also store historical data acquisition strategies for each region locally. This allows for convenient and direct invocation of the data acquisition strategies in the future, eliminating the need for repeated generation, saving system resources, and accelerating the distribution of data acquisition strategies.
[0103] Please refer to Figure 10 In some embodiments, this application proposes a data transmission system applied to a backend management terminal, the system comprising:
[0104] The preprocessing module 1001 is used to establish an initial dataset, preprocess the data items in the initial dataset to attach data identifiers to the data items, and classify the data items into the corresponding object labels according to the data identifiers.
[0105] The regional protocol acquisition module 1002 is used to respond to the policy acquisition request of the POS terminal and determine the first region where the POS terminal is located and the regional protocol corresponding to the first region.
[0106] The data acquisition strategy generation module 1003 is used to enable or disable data items in the object label according to the regional protocol, and generate a data acquisition strategy based on the enabled and disabled data items.
[0107] The data item acquisition module 1004 is used to send the data acquisition strategy to the POS terminal so that the POS terminal can collect data items according to the data acquisition strategy.
[0108] In some embodiments, a POS terminal refers to a point-of-sale (POS) terminal. A POS terminal, equipped with POS software, can replace a traditional POS machine and perform data collection. In some embodiments, NFC (Near Field Communication) refers to a wireless communication technology commonly used in mobile payments. It is understood that a POS terminal can implement NFC payment functionality by connecting to an NFC card reader. Specifically, when a customer uses a bank card or electronic device with NFC information to pay, they only need to place the card or electronic device near the POS terminal to complete the payment process. In some embodiments, the POS terminal communicates with an NFC card reader to read payment information from the customer's card or mobile phone and complete the payment.
[0109] In some embodiments, the back-end management terminal is built on and controlled by the data transmission system. In some embodiments, POS terminals in different regions share a single back-end management terminal. The back-end management terminal can process regional protocols, generate data acquisition strategies based on these protocols, and then distribute these strategies to the POS terminals. In some embodiments, the back-end management terminal can also view sales data, transaction volume, customer information, etc., based on the datasets sent by the POS terminals, for business analysis and decision-making. In some embodiments, the back-end management terminal can generate various statistical reports based on the datasets sent by the POS terminals, such as turnover, sales revenue, and customer numbers.
[0110] In some embodiments, the initial dataset is a collection formed by summarizing all data items related to the regional protocols across all regions. It is understood that since data items in most regional protocols often overlap, all collected data items can be labeled with data identifiers. In some embodiments, data identifiers can include transaction amount, transaction time, transaction location, transaction method, name, mobile phone number, ID card number, bank card number, Alipay account, WeChat Pay account, POS machine model, device serial number, operating system version, system logs, and exception information. Furthermore, data items can also be identified using Arabic numerals or English letters, such as labeling the transaction amount as 1 and the transaction time as 2, or labeling the transaction amount as A and the transaction time as B, etc.
[0111] In some embodiments, data items can be categorized into corresponding object tags based on data identifiers. In some embodiments, data items can be identified hierarchically or by category. For example, the following methods can be used: different types of data items can be categorized into corresponding object tags, such as transaction data, personal information, account information, device information, etc. In some embodiments, for specific data items under each category, such as transaction amount, transaction time, transaction location, etc., under transaction data, object tags can be used. In some embodiments, personal information such as name, mobile phone number, and ID card number can be categorized into the personal information object tag. In some embodiments, data items related to the POS machine itself, such as device number and operating system version under device information, can also be categorized under the corresponding object tag for the POS machine. It is understood that by classifying data items using data identifiers and object tags, different types of data items can be more clearly understood, thereby better protecting user privacy. Simultaneously, it also facilitates the system in quickly finding relevant data items based on regional policies.
[0112] In some embodiments, the first region can be any region divided according to geographical location, including cross-regional division, cross-city division, cross-provincial division, or cross-country division, etc., and this application embodiment does not impose specific limitations in this regard. In some embodiments, the back-end management terminal can respond to the data acquisition policy request of the POS terminal. Since the data acquisition policy request includes the location information of the first region where the POS terminal is located and the regional protocol corresponding to the first region, the first region where the POS terminal is located and the regional protocol corresponding to the first region can be determined according to the data acquisition policy request.
[0113] In some embodiments, a regional protocol is a document instructing a website or mobile application (in this application, a POS terminal) how to collect and use data items. In some embodiments, the POS terminal can enable or disable data items in object tags according to the regional protocol, and generate a data acquisition strategy based on the enabled and disabled data items. For example, if the regional protocol of the first region allows the acquisition of transaction time and name but prohibits the acquisition of operating system version, then the backend management terminal can find the corresponding data item based on the object tag and manage the enabling or disabling of the data item according to the regional protocol. For example, the corresponding object tag can be found through the regional protocol. For instance, if the object tag for transaction time is transaction data, then the transaction data can be found, and the transaction time can be enabled within the transaction data; in some embodiments, if the object tag for name is personal information, then the personal information can be found, and the name can be enabled within the personal information; in some embodiments, if the object tag for operating system version is device information, then the device information can be found, and the operating system version can be enabled within the device information. Understandably, in the final generated data acquisition strategy, if a corresponding data item is enabled, the POS terminal can collect data for that data item; if the corresponding data item is disabled, the POS terminal will prohibit data collection for that data item. It is also understood that regardless of whether the backend management terminal enables or disables a data item, the operation is based on the regional protocol.
[0114] Furthermore, the backend management system can search for all data items within the object's regional protocol based on the object's tag, and enable or disable the corresponding data items according to the regional protocol, ultimately generating a data acquisition policy. In some embodiments, a universal tag can also be set, which includes data items that are allowed to be accessed in all regional protocols. In this case, no additional enabling or disabling processing is required when generating the data acquisition policy.
[0115] In some embodiments, after the back-end management terminal sends a data acquisition strategy to the POS terminal, the POS terminal can collect data items according to the data acquisition strategy, and then summarize the collected data items as the target dataset for uploading.
[0116] Please refer to Figure 3 The backend management system can maintain and manage the target dataset sent by the POS terminal. Furthermore, it can place data items under the same data item identifier and display the corresponding data item's area, whether the data item is enabled or disabled, etc.
[0117] Understandably, the back-end management terminal can back up data based on the target dataset sent by the POS terminal to prevent data loss. In some embodiments, the back-end management terminal can perform statistical analysis on the dataset. In some embodiments, the POS terminal can support data sharing among multiple devices; after the collected data is sent to the back-end management terminal, data synchronization can be achieved, facilitating data sharing among multiple terminal devices.
[0118] The data transmission method, system, electronic device, and storage medium proposed in this application establish an initial dataset, preprocess the data items in the initial dataset to attach data identifiers to the data items, and classify the data items into corresponding object tags based on the data identifiers. Responding to a policy acquisition request from a POS terminal, the system determines the first region where the POS terminal is located and the corresponding regional protocol. Based on the regional protocol, it enables or disables the data items in the object tags, generates a data acquisition policy based on the enabled and disabled data items, and sends the data acquisition policy to the POS terminal so that the POS terminal can collect data items according to the policy. This allows all regions to share a single system. The system can generate corresponding data acquisition policies based on the regional protocols of different regions, and the POS terminal directly collects data items according to the data acquisition policy. Therefore, it is unnecessary to deploy the system specifically for different regions based on their regional protocols, reducing system development costs and maintenance difficulty.
[0119] The specific implementation of this data transmission system is basically the same as the specific embodiments of the data transmission method described above, and will not be repeated here. Subject to meeting the requirements of the embodiments of this application, the data transmission system may also be equipped with other functional modules to implement the data transmission method described above.
[0120] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described data transmission method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.
[0121] Please see Figure 11 , Figure 11 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes:
[0122] The processor 1101 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.
[0123] The memory 1102 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1102 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1102 and is called and executed by the processor 1101 using the data transmission method of the embodiments of this application.
[0124] Input / output interface 1103 is used to implement information input and output;
[0125] The communication interface 1104 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).
[0126] Bus 1105 transmits information between various components of the device (e.g., processor 1101, memory 1102, input / output interface 1103, and communication interface 1104);
[0127] The processor 1101, memory 1102, input / output interface 1103 and communication interface 1104 are connected to each other within the device via bus 1105.
[0128] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described data transmission method.
[0129] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
[0130] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
[0131] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.
[0132] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0133] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.
[0134] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0135] It should be understood that in this application, "at least one" and "several" refer to one or more, and "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer 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 represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0136] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.
[0137] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0138] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0139] If the integrated unit is implemented as 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 this application, in essence, 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. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0140] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.
Claims
1. A data transmission method, characterized in that, Applied to the backend management terminal, the method includes: An initial dataset is established, and the data items in the initial dataset are preprocessed to attach data identifiers to the data items. Based on the data identifiers, the data items are classified into the corresponding object labels. In response to the data acquisition strategy acquisition request of the POS terminal, the first region where the POS terminal is located and the region protocol corresponding to the first region are determined. According to the regional protocol, the data items in the object tag are enabled or disabled, and the data acquisition strategy is generated based on the enabled and disabled data items. The data acquisition strategy is sent to the POS terminal so that the POS terminal can collect data items according to the data acquisition strategy.
2. The data transmission method according to claim 1, characterized in that, The process of establishing an initial dataset, preprocessing the data items in the initial dataset to attach data identifiers to the data items, and classifying the data items into corresponding object labels based on the data identifiers includes: An initial dataset is created, and the format of the data items in the initial dataset is adjusted according to a preset format; The data items after format adjustment are identified to obtain the data item identifiers corresponding to each data item. Obtain the rules for dividing object tags; Based on the classification rules and the data item identifier, the data item is categorized into the corresponding object label.
3. The data transmission method according to claim 1, characterized in that, The step of enabling or disabling data items in the object tag according to the regional protocol, and generating the data acquisition strategy based on the obtained enabled and disabled data items, includes: Based on the regional protocol, generate target data identifiers for enabled and disabled data items; Based on the target data identifier, locate the enabled data item and the disabled data item in the object label; The enabled data items are enabled, the disabled data items are disabled, and the enabled and disabled data items are summarized to generate the data acquisition strategy; wherein the enabled data items are allowed to be accessed in the POS terminal, and the disabled data items are prohibited from being accessed in the POS terminal.
4. The data transmission method according to claim 3, characterized in that, After generating the data acquisition strategy, the method further includes: The data acquisition strategy is saved, and a mapping relationship between the data acquisition strategy and the first area is established so that when a data acquisition strategy acquisition request is received from the POS terminal, the data acquisition strategy is invoked through the mapping relationship. The data acquisition strategy corresponding to the first region shall be maintained and updated regularly.
5. The data transmission method according to claim 1, characterized in that, The method further includes: Based on the acquisition request, check whether the data acquisition strategy corresponding to the first region is stored locally; If the data acquisition strategy corresponding to the first region is found, the data acquisition strategy is sent to the POS terminal.
6. The data transmission method according to claim 1, characterized in that, The backend management terminal has a default data acquisition strategy, and the method further includes: If the location information transmitted by the POS terminal is not received, the default data acquisition strategy is sent to the POS terminal. Alternatively, if the data acquisition strategy request sent by the POS terminal does not include the regional protocol corresponding to the first region, then the default data acquisition strategy is sent to the POS terminal.
7. A data transmission method, characterized in that, Applied to a POS terminal, the method includes: In response to the target dataset acquisition instruction, the location information of the POS terminal in the first region and the region protocol corresponding to the first region are acquired. A policy retrieval request is sent to the backend management terminal, enabling the backend management terminal to enable or disable data items in the object tags according to the regional protocol corresponding to the first region, and generate a data retrieval policy based on the obtained enabled and disabled data items; wherein, the policy retrieval request includes the location information of the first region and the regional protocol corresponding to the first region, the object tags corresponding to the data items are determined by the backend management terminal based on the data identifier of the data items, the data identifier of the data items is established by the backend management terminal in an initial dataset, and the data items in the initial dataset are preprocessed and then appended, the enabled data items are allowed to be accessed in the POS terminal, and the disabled data items are prohibited from being accessed in the POS terminal; Receive the data acquisition strategy, collect target data items according to the data acquisition strategy, and generate a target dataset based on the collected target data items; Upload the target dataset to the backend management terminal.
8. A data transmission system, characterized in that, The system, applied to the backend management interface, includes: The preprocessing module is used to establish an initial dataset, preprocess the data items in the initial dataset to attach data identifiers to the data items, and classify the data items into corresponding object labels based on the data identifiers. The regional protocol acquisition module is used to determine the first region where the POS terminal is located and the regional protocol corresponding to the first region in response to the data acquisition strategy acquisition request of the POS terminal. The data acquisition strategy generation module is used to enable or disable data items in the object tag according to the regional protocol, and generate the data acquisition strategy based on the obtained enabled and disabled data items; The data item acquisition module is used to send the data acquisition strategy to the POS terminal so that the POS terminal can acquire data items according to the data acquisition strategy.
9. An electronic device, characterized in that, The electronic device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the data transmission method of the POS terminal according to any one of claims 1 to 7.
10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the data transmission method of the POS terminal according to any one of claims 1 to 7.