Cross-domain data fusion method and related device

Abstract

The present application relates to a cross-domain data fusion method and related devices, including: determining at least one identity identifier of each customer based on customer source data in several systems, and storing the customer source data in several first function tables; classifying and storing the first function tables in several second function tables based on the identity identifier of each customer and the type information of each first function table, wherein the identity identifier corresponds to the type information; constructing a function table view of the database based on the several second function tables, wherein the function table view is used to obtain the customer source data of the customer based on the customer's identity identifier. The solution provided by the present application can integrate the customer data of each system into the database, realize unified data management, avoid inconsistency of customer data of each system, and improve data access efficiency.

Description

Technical Field

[0001] The present application relates to the technical field of data fusion, and in particular to a cross-domain data fusion method and related devices. Background Art

[0002] Traditionally, each field and organization independently collects, manages and analyzes its own data. However, this isolated data processing method has some problems. First, data between different fields and organizations cannot be effectively interacted and shared, which limits the comprehensive utilization of data. Second, due to the limitations of data sources, many problems cannot be fully and accurately solved.

[0003] In related technologies, when cross-domain data needs to be accessed and processed, authorization, data transfer and replication are required in multiple systems, resulting in inefficient data access and performance degradation, as well as data differences in various systems, leading to inconsistent data. Summary of the invention

[0004] In order to solve or partially solve the problems existing in the related technology, the present application provides a cross-domain data fusion method and related devices, which can integrate the customer data of each system into a database, realize unified data management, avoid inconsistency of customer data of each system, and improve data access efficiency.

[0005] The first aspect of the present application provides a cross-domain data fusion method, comprising determining at least one identity identifier of each customer based on customer source data in a plurality of systems, and storing the customer source data in a plurality of first function tables; classifying and storing the first function tables in a plurality of second function tables based on the identity identifier of each customer and the type information of each first function table; and constructing a function table view of the database based on the plurality of second function tables, wherein the function table view is used to obtain the customer source data of the customer based on the identity identifier of the customer.

[0006] In combination with the first aspect, in a possible implementation of the first aspect, before determining the identity of each customer based on the customer source data in several systems, it includes: receiving the customer source data of each of the systems, preprocessing the customer source data to obtain customer feature data corresponding to the customer source data; storing the customer feature data in a unified data table of data sources, wherein the unified data table of data sources includes the customer source data of each of the systems; and determining the identity of each of the customers from the customer source data based on the OneId mechanism.

[0007] In combination with the first aspect, in a possible implementation of the first aspect, the customer source data includes one or more of the customer's basic information, asset information, contact information, service information, identity information, contact information, taxpayer information, customer name, customer code, certificate type, and certificate number.

[0008] In combination with the first aspect, in a possible implementation of the first aspect, the classifying and storing the customer source data into several first function tables includes: storing the customer source data into several first function tables according to the data type of the customer source data, wherein the customer source data of each of the systems corresponds to at least one of the first function tables.

[0009] In combination with the first aspect, in a possible implementation manner of the first aspect, the category information of the first function table at least includes customer category, product category, and sales category.

[0010] In combination with the first aspect, in a possible implementation method of the first aspect, a CTGMQ message sent by the system is received, the CTGMQ message is parsed to obtain updated customer source data; and the customer source data in the second function table is updated based on the updated customer source data and the customer's identity.

[0011] The second aspect of the present application provides a cross-domain data fusion device, including a determination module, for determining at least one identity identifier of each customer based on customer source data in a plurality of systems, and storing the customer source data in a plurality of first function tables; a processing module, for classifying and storing the first function tables into a plurality of second function tables based on the identity identifier of each customer and the type information of each first function table, wherein the identity identifier corresponds to the type information; and a construction module, for constructing a function table view of the database based on the plurality of second function tables, wherein the function table view is used to obtain the customer source data of the customer based on the identity identifier of the customer.

[0012] In combination with the second aspect, in a possible implementation of the second aspect, the determination module is also used to receive a unified table of customer source data sources for each of the systems, wherein the unified table of customer source data sources includes the customer source data of the system; and based on the OneId mechanism, determine the identity of each of the customers from the customer source data.

[0013] In combination with the second aspect, in a possible implementation of the second aspect, the storage module is also used to store the customer source data in a plurality of first function tables according to the data type of the customer source data, wherein the customer source data of each of the systems corresponds to at least one first function table.

[0014] In combination with the second aspect, in a possible implementation of the second aspect, the processing module is also used to allocate several first function tables to the second function table according to the type information of the first function table corresponding to each of the systems and the identity of the customer, and the type information of the second function table is the same as the type information of the first function table.

[0015] In combination with the second aspect, in a possible implementation of the second aspect, the processing module is also used to receive a CTGMQ message sent by the system, parse the CTGMQ message to obtain updated customer source data; and update the customer source data in the second function table according to the updated customer source data and the customer's identity.

[0016] A third aspect of the present application provides an electronic device, including:

[0017] Processor; and

[0018] The memory stores executable codes thereon, and when the executable codes are executed by the processor, the processor is caused to execute the method as described above.

[0019] A fourth aspect of the present application provides a computer-readable storage medium having executable code stored thereon. When the executable code is executed by a processor of an electronic device, the processor is caused to execute the method as described above.

[0020] A fifth aspect of the present application provides a computer program product, comprising: a computer program / instruction that implements the above-mentioned method when executed by a processor.

[0021] The technical solution provided by this application may have the following beneficial effects:

[0022] The present application discloses a cross-domain data fusion method and related devices, including determining at least one identity identifier of each customer based on customer source data in a plurality of systems, and storing the customer source data in a plurality of first function tables; classifying and storing the first function tables in a plurality of second function tables based on the identity identifier of each customer and the type information of each first function table, wherein the identity identifier corresponds to the type information; constructing a function table view of a database based on the plurality of second function tables, wherein the function table view is used to obtain the customer source data of the customer based on the customer identity identifier, and can integrate the customer data of each system into the database, thereby realizing unified data management, avoiding inconsistency in the customer data of each system, and improving data access efficiency.

[0023] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The above and other objects, features and advantages of the present application will become more apparent by describing in more detail exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0025] Figure 1 It is a flowchart of a cross-domain data fusion method shown in an embodiment of the present application;

[0026] Figure 2 is a schematic diagram of the structure of a cross-domain data fusion device shown in an embodiment of the present application;

[0027] Figure 3 It is a schematic diagram of the structure of an electronic device shown in an embodiment of the present application. DETAILED DESCRIPTION

[0028] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0029] The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit this application. The singular forms of "a", "an", and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in this article refers to and includes any or all possible combinations of one or more associated listed items.

[0030] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0031] Traditionally, each field and organization independently collects, manages and analyzes its own data. However, this isolated data processing method has some problems. First, data between different fields and organizations cannot be effectively interacted and shared, which limits the comprehensive utilization of data. Second, due to the limitations of data sources, many problems cannot be fully and accurately solved.

[0032] In the telecommunications industry, customer data is scattered in the M domain, B domain, and O domain. Each domain stores different aspects of customer data, such as the CRM system has basic customer information, the billing system has customer consumption data, and the service activation system has customer activation data. Among these different data, some selected data are connected in series, such as CRM and billing can be connected in series through customers, mobile phone numbers, sales product instances, and accounts, and CRM and service activation can be connected in series through orders. These data used for connection exist in the systems of each domain, but once the source system of the data is modified and the downstream related systems are not synchronized in time, data differences will occur. The phenomenon displayed is that the customer data found by customers in different channels is inconsistent, which causes customer complaints.

[0033] In related technologies, when cross-domain data needs to be accessed and processed, authorization, data transfer and replication are required in multiple systems, resulting in inefficient data access and performance degradation, as well as data differences in various systems, leading to inconsistent data.

[0034] In response to the above problems, the embodiments of the present application provide a cross-domain data fusion method and related devices, which can integrate the customer data of each system into a database, realize unified data management, avoid inconsistency in customer data of each system, and improve data access efficiency.

[0035] The technical solution of the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0036] Figure 1 It is a flow chart of the cross-domain data fusion method shown in an embodiment of the present application.

[0037] See also Figure 1 , a cross-domain data fusion method, comprising:

[0038] S110: Determine at least one identity identifier of each customer based on customer source data in a plurality of systems, and store the customer source data in a plurality of first function tables.

[0039] Specifically, the database can extract relevant data from customer source data based on different customer source data of several systems, and determine the identity of each customer based on the relevant data of each customer. Each customer can have at least one identity, and the identity can be used to classify and store the customer's data in different second function tables.

[0040] Specifically, the database can extract relevant data from different customer source data of each system in the M domain, B domain and O domain, and determine the identity of each customer based on the relevant data of each customer. There can be several systems distributed in the M domain, B domain and O domain; M domain: refers to the management domain, which is the data domain of the management support system, storing location information, such as crowd flow trajectory, map information, etc. The management support system (MSS) includes all non-core business processes required to support the enterprise, covering the formulation of corporate strategy and development direction, enterprise risk management, audit management, public publicity and image management, financial and asset management, human resource management, knowledge and R&D management, shareholder and external relationship management, procurement management, enterprise performance evaluation, government policies and laws, etc.; B domain: refers to the business domain, which is the data domain of the business support system, storing user data and business data, such as user consumption habits, terminal information, ARPU grouping, business content, business audience, etc. The business support system (BSS) mainly implements the management of telecommunication services, telecommunication rates, telecommunication marketing, as well as the management and service process of customers. The main systems it contains include: CRM system, billing system, customer service system, accounting system, settlement system and business analysis system, etc.; O domain: refers to the operation domain, which is the data domain of the operation support system, storing network data, such as signaling, alarms, faults, network resources, etc. The operation support system (OSS) is mainly a backend support system for resources (network, equipment, computing system), including service activation system, professional network management system, integrated network management system, resource management system, service guarantee system, etc., providing support means for reliable, secure and stable operation of the network.

[0041] In one possible implementation, customer source data of each system is received, and the customer source data is preprocessed to obtain customer characteristic data corresponding to the customer source data; the customer characteristic data is stored in a unified data table of data sources, and the unified data table of data sources includes the customer source data of each system; based on the OneId mechanism, the identity of each customer is determined from the customer source data.

[0042] Specifically, after receiving the customer source data from each system, the customer source data can be preprocessed to obtain customer characteristic data corresponding to the customer source data, and the customer characteristic data can be stored in a unified data table of data sources. The unified data table of data sources may include multiple columns, for example, a primary information section, a secondary information section, information items, a data source system, a data collection frequency, and a data source path. The primary information section may include: customer basic information, customer asset information, customer contact information, customer service information, etc.; the secondary information section may include customer data subcategories, such as customer basic information includes: customer identity information, customer contact information, customer taxpayer information, etc.; information items refer to customer characteristic data of data subcategories, such as customer identity information includes: customer name, customer code, customer ID type, customer ID number, etc.; the data source system refers to the specific system name of the customer source data source; the data collection frequency refers to the collection frequency of customer source data, such as timed collection; the data source path refers to which menu path under the source system.

[0043] Specifically, the OneId mechanism can be used to allow each customer to have multiple identity identifiers. The identity identifier can be a UID identifier, and the identity identifier can correspond to the category information of the first function table. For example, when the customer's identity identifier is a customer identifier, it can correspond to the customer class of the category information of the first function table; when the customer's identity identifier is a product identifier, it can correspond to the product class of the category information of the first function table; when the customer's identity identifier is a sales product identifier, it can correspond to the sales product category of the category information of the first function table. Each identity identifier can correspond to a UID identifier.

[0044] In one possible implementation, the customer source data includes one or more of the customer's basic information, asset information, contact information, service information, identity information, contact information, taxpayer information, customer name, customer code, certificate type, and certificate number. The customer characteristic data in the customer source data contained in each system may be the same or different. For example, system 1 contains information such as the customer's basic information, asset information, contact information, service information, etc., and system 2 contains information such as the customer's name, customer code, certificate type, certificate number, etc.

[0045] Specifically, the first function table may have multiple rows and columns, and the customer source data may be classified and stored in the first function table according to the customer's identity identifier. The first function table may include category information, and the category information may be classification information of the customer source data contained in the first function table. For example, the category information may be customer category, product category, or sales category. When the category information of the first function table is customer category, the first function table may include the customer's basic information, customer contact information, etc., and the customer's identity identifier is the customer identifier; when the category information of the first function table is product category, the first function table may include the product information, ancillary product information, and product equipment information in the customer's customer asset information, and the customer's identity identifier is the product identifier; when the category information of the first function table is sales category, the first function table may include the customer's sales product information, sales product parameter information, and a sales product object list, and the customer's identity identifier is the sales product identifier.

[0046] In a possible implementation, the customer source data is stored in several first function tables according to the data type of the customer source data, wherein the customer source data of each system corresponds to at least one first function table, and the customer data types can be divided into multiple types, for example, the data types may include customer category, product category, and sales category, and the data with the data type of customer category in the customer source data can be stored in the first function table with the category information of customer category.

[0047] Specifically, the customer source data of each system may be stored in a plurality of first function tables respectively, and when the customer source data is needed, it may be directly obtained from the first function table.

[0048] S120: Classify and store the first function tables into a plurality of second function tables according to the identity identifier of each customer and the type information of each first function table.

[0049] Specifically, the first function table can be classified according to the category information of the first function table to obtain several second function tables. For example, the first function table whose category information is all customer class can be classified into the second function table. The category information of the second function table can be customer class, and can include all first function tables whose category information is customer class.

[0050] In a possible implementation manner, the category information of the first function table at least includes customer category, product category, and sales category.

[0051] Specifically, the second function table may include a first function table with the same type of information, and the first function table may be a first function table with different types of information from different systems. Through the second function table, it is possible to quickly obtain in which first function table the customer's required data is located, and obtain the customer's required data from the first function table.

[0052] S130: constructing a function table view of the database according to the plurality of second function tables, where the function table view is used to obtain the customer source data of the customer according to the customer's identity identifier.

[0053] Specifically, based on several second function tables, a function table view of data can be constructed. The function table view can query the type information of each second function table and each first function table contained in each function table, and obtain the customer source data of each system through the first function table.

[0054] In a possible implementation, a CTGMQ message sent by a receiving system is parsed to obtain updated customer source data; and the customer source data in the second function table is updated according to the updated customer source data and the customer's identity.

[0055] Specifically, after receiving the CTGMQ message, the CTGMQ message can be parsed, and the parsed CTGMQ message can be cleaned to remove invalid data, and based on the identity information of each customer, the customer source data contained in the parsed CTGMQ message can be updated in the second function table to obtain the latest customer source data of each customer in each system.

[0056] CTGMQ message is a distributed message service based on RocketMQ. In Master-Slave mode, CTGMQ realizes automatic master-slave switching of Broker through Raft master election mechanism of NameServer, ensuring the consistency and non-loss of messages. Each system sends messages to the database through CTGMQ messages, which can improve the accuracy and transmission efficiency of messages.

[0057] Specifically, when a customer needs to query certain information, after receiving the customer's query information, the database can locate it in the function table view according to the type of information that needs to be queried, and then determine which type the second data table contains, and then query the first data table where the information is located in the second data table, extract the information from the first data table, and send it to the customer.

[0058] A cross-domain data fusion method of the present application includes determining at least one identity identifier of each customer based on customer source data in several systems, and storing the customer source data in several first function tables; classifying and storing the first function tables in several second function tables based on the identity identifier of each customer and the type information of each first function table, wherein the identity identifier corresponds to the type information; constructing a function table view of a database based on the several second function tables, wherein the function table view is used to obtain the customer source data of the customer based on the customer's identity identifier, and can integrate the customer data of each system into the database, thereby realizing unified data management, avoiding inconsistency in the customer data of each system, and improving data access efficiency.

[0059] Corresponding to the aforementioned application function implementation method embodiment, the present application also provides a cross-domain data fusion device, an electronic device and corresponding embodiments.

[0060] Figure 2 It is a schematic diagram of the structure of a cross-domain data fusion device shown in an embodiment of the present application.

[0061] See also Figure 2 , a cross-domain data fusion device 200, comprising:

[0062] The determination module 210 is used to determine at least one identity identifier of each customer based on customer source data in a plurality of systems, and store the customer source data in a plurality of first function tables.

[0063] Specifically, the database can extract relevant data from the customer source data based on different customer source data of several systems, and determine the identity of each customer based on the relevant data of each customer, so that each customer has a unique identity.

[0064] In a possible implementation, the determination module 210 is also used to receive customer source data from each system, pre-process the customer source data, and obtain customer characteristic data corresponding to the customer source data; store the customer characteristic data in a unified data table of data sources, the unified data table of data sources includes the customer source data of each system; and determine at least one identity identifier of each customer from the customer source data based on the OneId mechanism.

[0065] Specifically, the first function table may have multiple rows and columns, and the customer source data may be classified and stored according to the customer's identity identifier.

[0066] In a possible implementation, the storage module 220 is also used to obtain customer source data of each customer in different systems according to the identity of each customer; and classify and store the customer source data into several first function tables according to the data type of the customer source data, wherein the customer source data of each system corresponds to at least one first function table.

[0067] The processing module 220 is used to classify and store the first function tables into a plurality of second function tables according to the identity identifier of each customer and the category information of each first function table, wherein the identity identifier corresponds to the category information.

[0068] Specifically, the first function table can be classified according to the category information of the first function table to obtain several second function tables. For example, the first function table whose category information is all customer class can be classified into the second function table. The category information of the second function table can be customer class, and can include all first function tables whose category information is customer class.

[0069] In a possible implementation, the processing module 230 is also used to receive a CTGMQ message sent by the system, parse the CTGMQ message to obtain updated customer source data; and update the customer source data in the first function table according to the updated customer source data and the customer's identity.

[0070] The construction module 230 is used to construct a function table view of the database according to the plurality of second function tables, and the function table view is used to obtain the customer source data of the customer according to the customer's identity identifier.

[0071] Specifically, based on several second function tables, a function table view of data can be constructed. The function table view can query the type information of each second function table and each first function table contained in each function table, and obtain the customer source data of each system through the first function table.

[0072] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated again here.

[0073] Figure 3 It is a schematic diagram of the structure of an electronic device shown in an embodiment of the present application.

[0074] See also Figure 3 , the electronic device 300 includes a memory 310 and a processor 320.

[0075] The processor 320 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0076] The memory 310 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. Among them, ROM can store static data or instructions required by the processor 320 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even after the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as a permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as a dynamic random access memory. The system memory may store some or all instructions and data required by the processor at run time. In addition, the memory 310 may include any combination of computer-readable storage media, including various types of semiconductor storage chips (such as DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks may also be used. In some embodiments, the memory 310 may include a readable and / or writable removable storage device, such as a laser disc (CD), a read-only digital versatile disc (such as a DVD-ROM, a double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (such as an SD card, a mini SD card, a Micro-SD card, etc.), a magnetic floppy disk, etc. Computer-readable storage media do not include carrier waves and transient electronic signals transmitted wirelessly or wired.

[0077] The memory 310 stores executable codes, and when the executable codes are processed by the processor 320 , the processor 320 can execute part or all of the methods described above.

[0078] In addition, the method according to the present application may also be implemented as a computer program or a computer program product, which includes computer program code instructions for executing some or all of the steps in the above method of the present application.

[0079] Alternatively, the present application can also be implemented as a computer-readable storage medium (or non-transitory machine-readable storage medium or machine-readable storage medium) on which executable code (or computer program or computer instruction code) is stored. When the executable code (or computer program or computer instruction code) is executed by a processor of an electronic device (or server, etc.), the processor executes part or all of the steps of the above-mentioned method according to the present application.

[0080] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A cross-domain data fusion method, characterized in that: Applied to databases, including: Determine at least one identity identifier of each customer based on customer source data in a plurality of systems, and store the customer source data in a plurality of first function tables; Classify and store the first function tables into a plurality of second function tables according to the identity identifier of each of the customers and the type information of each of the first function tables, wherein the identity identifier corresponds to the type information; A function table view of the database is constructed according to the plurality of the second function tables, and the function table view is used to obtain the customer source data of the customer according to the identity identifier of the customer.

2. The method according to claim 1, characterized in that Before determining at least one identity identifier of each customer based on the customer source data in the plurality of systems, the method includes: Receiving customer source data of each of the systems, preprocessing the customer source data, and obtaining customer feature data corresponding to the customer source data; storing the customer feature data in a unified data table of data sources, wherein the unified data table of data sources includes the customer source data of each of the systems; Based on the OneId mechanism, at least one identity identifier of each of the customers is determined from the customer source data.

3. The method according to claim 2, characterized in that The customer source data includes one or more of the customer's basic information, asset information, contact information, service information, identity information, contact information, taxpayer information, customer name, customer code, certificate type, and certificate number.

4. The method according to claim 1, characterized in that: The step of classifying and storing the customer source data into a plurality of first function tables includes: According to the data type of the customer source data, the customer source data is stored in a plurality of the first function tables, wherein the customer source data of each of the systems corresponds to at least one of the first function tables.

5. The method according to claim 1, characterized in that: The category information of the first function table at least includes customer category, product category, and sales category.

6. The method according to claim 4, characterized in that Also includes: Receiving a CTGMQ message sent by the system, parsing the CTGMQ message, and obtaining updated customer source data; The customer source data in the second function table is updated according to the updated customer source data and the customer's identity.

7. A cross-domain data fusion device, characterized in that: include: A determination module, configured to determine at least one identity identifier of each customer based on customer source data in a plurality of systems, and store the customer source data in a plurality of first function tables; a processing module, configured to classify and store the first function tables into a plurality of second function tables according to the identity identifier of each of the customers and the type information of each of the first function tables, wherein the identity identifier corresponds to the type information; A construction module is used to construct a function table view of the database according to a plurality of the second function tables, and the function table view is used to obtain the customer source data of the customer according to the identity identifier of the customer.

8. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: include: processor; as well as A memory having executable codes stored thereon, which, when executed by the processor, causes the processor to execute the method according to any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: An executable code is stored thereon, and when the executable code is executed by a processor of an electronic device, the processor is caused to execute the method as claimed in any one of claims 1 to 6.

Images