CN113590884A

CN113590884A - Distributed data searching method and index file sharing method

Info

Publication number: CN113590884A
Application number: CN202010370734.4A
Authority: CN
Inventors: 郭颂; 高华江; 杜鸿雁
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-04-30
Filing date: 2020-04-30
Publication date: 2021-11-02
Also published as: CN114398320A

Abstract

The application belongs to the technical field of communication, and provides a distributed data searching method and an index file sharing method, wherein the distributed data searching method comprises the following steps: responding to the monitored index establishing event, and establishing an index file of metadata; the index establishing event is an event for establishing an index for the metadata; synchronizing the index files among different electronic devices creating a synchronization pipeline; responding to the monitored search event, searching a local synchronous index library to obtain a search result, wherein the synchronous index library comprises a local index file and index files of other electronic equipment; the other electronic equipment is electronic equipment except the local electronic equipment; and displaying the search result. The distributed search scheme does not need complex logics such as data synchronization, network access and the like, is simple in process, and improves efficiency.

Description

Distributed data searching method and index file sharing method

Technical Field

The present application belongs to the field of communications technologies, and in particular, to a distributed data search method and an index file sharing method.

Background

With the increasing maturity of digital information technology and terminal technology, full-text retrieval of information in electronic equipment is widely applied.

In addition, as the types and the number of electronic devices of consumers are gradually increased, the amount of data that can be stored in each electronic device is gradually increased, and the amount of data stored in each electronic device is not uniformly distributed, etc., the demand for finding data stored in different electronic devices, such as files, photos, videos, music, or various application data, etc., through a search function is more and more urgent.

At present, after the original data of different electronic devices are synchronized, or when the different electronic devices maintain network connection, the shared data of the different electronic devices can be searched.

It can be seen that the current technology needs to rely on complex logic such as data synchronization or network access.

Disclosure of Invention

The embodiment of the application provides a distributed data searching method and an index file sharing method, and can solve at least part of technical problems of the related technology.

In a first aspect, an embodiment of the present application provides a method for distributed data search, where the method includes:

responding to the monitored search event, searching a local synchronous index library to obtain a search result, wherein the synchronous index library comprises a local index file and index files of other electronic equipment; the other electronic equipment is electronic equipment except the local electronic equipment;

and displaying the search result.

The distributed data searching method provided by the embodiment of the first aspect is completed in the local computer, does not involve cross-equipment and cross-network, does not need complex logics such as network access and the like, is simple in process, and improves efficiency, so that user experience is improved.

In a possible implementation manner of the first aspect, the method further includes:

responding to the monitored index establishing event, and establishing an index file of metadata; the index establishing event is an event for establishing an index for the metadata;

the index files are synchronized among different electronic devices that create a synchronization pipeline.

In a possible implementation manner of the first aspect, in response to a monitored search event, a search interface is invoked, and a search component corresponding to the search interface searches a local synchronous index library to obtain a search result.

In one possible implementation manner of the first aspect, the search event is triggered according to a search condition input in the search interface. The search condition includes, but is not limited to, one or more combinations of sentences, keywords, pictures, and the like. The search interface may be a search interface in a system or application. The system comprises but not limited to an operating system of a mobile phone terminal such as an iOS or android system and the like, and further comprises an operating system of a non-mobile phone terminal such as Windows or Linux, and the application program comprises but not limited to a short message, a calendar, a memo, file management, a contact person and the like.

In a possible implementation manner of the first aspect, the distributed data search service may open a distributed search interface to a system and/or an application on the electronic device, so as to implement a distributed search function, facilitate user operations, and meanwhile, the scheme is easy to implement.

In a second aspect, an embodiment of the present application provides a method for sharing an index file, where the method includes:

In the method for sharing the index file provided by the embodiment of the second aspect, metadata or an original file does not need to be synchronized to different electronic devices, and only the index file needs to be synchronized to different electronic devices, so that on one hand, the transmission efficiency is greatly improved, and the storage burden is also reduced; on the other hand, after the index files are synchronized among different electronic devices, the content shared by other electronic devices can be searched on one electronic device, and the content can be searched under the offline state of other electronic devices, so that the searching efficiency is improved, and the searching experience of a user is also improved.

In a possible implementation manner of the second aspect, in response to the monitored index establishment event, an index interface is called, and the metadata is analyzed through an index component corresponding to the index interface, so as to establish an index file of the metadata.

In a possible implementation manner of the second aspect, a synchronization interface is called, and the index file is synchronized between the local machine and other electronic devices that create a synchronization pipeline with the local machine through a synchronization component corresponding to the synchronization interface.

In a possible implementation manner of the second aspect, the distributed data search service may open a distributed index interface and a synchronization interface to a system and/or an application on the electronic device, so as to implement synchronization of the index file between different electronic devices, without designing a complex data synchronization logic, and the scheme is easy to implement.

In a third aspect, an embodiment of the present application provides a method for distributed data search, where the method includes:

responding to the monitored search event, and searching the local index library and/or the distributed file system to obtain a search result; the local index library comprises index files which are not required to be synchronized by the local index library; the distributed file system comprises an index file which needs to be synchronized by a local computer;

and displaying the search result.

Compared with the first aspect, the distributed data search method provided by the embodiment of the third aspect has the advantages that the synchronization of the index file is not required to be realized independently, the cross-device access of the index file can be realized only by the distributed file system, and the design of complicated logics such as data synchronization, network access and the like is not required.

In a possible implementation manner of the third aspect, the method further includes:

if the metadata belongs to local metadata which does not need to be synchronized, storing an index file of the metadata to a local index database; and if the metadata belongs to the distributed metadata needing synchronization, storing the index file of the metadata to a distributed file system.

In a possible implementation manner of the third aspect, in response to a monitored search event, a search interface is invoked, and a search component corresponding to the search interface searches a local index repository and/or a distributed file system to obtain a search result.

In a possible implementation manner of the third aspect, the service application only needs to access a simple interface, so that the cross-device distributed search can be realized, and the scheme of the application is easy to implement.

In a fourth aspect, an embodiment of the present application provides a method for sharing an index file, where the method includes:

Compared with the second aspect, the distributed data search method provided by the embodiment of the fourth aspect has the advantages that the synchronization of the index file is not required to be realized independently, the cross-device access of the index file can be realized only by the distributed file system, and the complex logics such as data synchronization, network access and the like are not required to be designed.

In a possible implementation manner of the fourth aspect, in response to the monitored index establishment event, an index interface is called, and the metadata is analyzed through an index component corresponding to the index interface, so as to establish an index file of the metadata.

In a possible implementation manner of the fourth aspect, the service application only needs to access a simple interface, so that the cross-device distributed search can be realized, and the scheme of the application is easy to implement.

In a fifth aspect, an embodiment of the present application provides a distributed data search service system, which includes four layers, where the four layers are respectively: the system comprises an application program layer, a distributed search interface, a distributed search service and an index file;

the distributed search interface comprises an index interface, a search interface and a synchronous interface;

the distributed search service comprises an indexing component, a search component, and a synchronization component, corresponding to the distributed search interface;

the index file comprises a synchronous index library, and the synchronous index library comprises a local index file and index files synchronized with other electronic equipment; the other electronic equipment is other than the local electronic equipment;

the index component is used for analyzing metadata of the local computer and establishing an index file of the local computer;

the synchronization component is used for synchronizing the index file of the local machine and the index files of other electronic devices between the other electronic devices which create a synchronization pipeline with the local machine;

and the searching component is used for searching the synchronous index library according to the searching condition to obtain a searching result.

In a sixth aspect, an embodiment of the present application provides a distributed data search service system, which includes four layers, where the four layers are respectively: the system comprises an application program layer, a distributed search interface, a distributed search service and an index file;

the distributed search interface comprises an index interface and a search interface;

the distributed search service comprises an indexing component and a search component corresponding to the distributed search interface;

the index file comprises a local index library and a distributed file system, the local index library comprises index files which do not need to be synchronized by the local computer, and the distributed file system comprises index files which need to be synchronized by the local computer;

the index component is used for analyzing metadata of the local computer and establishing an index file of the local computer; if the metadata belongs to local metadata which does not need to be synchronized, storing an index file of the metadata to the local index database; if the metadata belongs to distributed metadata needing synchronization, storing an index file of the metadata to the distributed file system;

the search component is used for searching the local index library and/or the distributed file system according to the search condition to obtain a search result.

In a possible implementation manner of any one of the fifth aspect and the sixth aspect, the distributed search interface further includes a configuration interface, and correspondingly, the distributed search service further includes a configuration component.

The configuration component is used for setting one or more of synchronization parameters, search parameters, synchronization strategies, search strategies, storage positions and the like by a user.

In a possible implementation manner of any one of the fifth aspect and the sixth aspect, a user can set various parameters in a user-defined manner, so that the method and the device can be applied to different application scenarios, meet different user requirements, and further improve user experience.

In a seventh aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor, when executing the computer program, causes the electronic device to implement the method according to any one of the first aspect and possible implementations of the first aspect, or implement the method according to any one of the second aspect and possible implementations of the second aspect, or implement the method according to any one of the third aspect and possible implementations of the third aspect, or implement the method according to any one of the fourth aspect and possible implementations of the fourth aspect.

In an eighth aspect, the present application provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, implements the method according to any one of the first aspect and possible implementations of the first aspect, or implements the method according to any one of the second aspect and possible implementations of the second aspect, or implements the method according to any one of the third aspect and possible implementations of the third aspect, or implements the method according to any one of the fourth aspect and possible implementations of the fourth aspect.

In a ninth aspect, an embodiment of the present application provides a computer program product, which, when run on an electronic device, causes the electronic device to perform the method described in any one of the foregoing possible implementations of the first aspect and the first aspect, or perform the method described in any one of the foregoing possible implementations of the second aspect and the second aspect, or perform the method described in any one of the foregoing possible implementations of the third aspect and the third aspect, or perform the method described in any one of the foregoing possible implementations of the fourth aspect and the fourth aspect.

It is to be understood that the beneficial effects of the above fifth to ninth aspects can be seen from the related descriptions of the above first to fourth aspects.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic hardware structure diagram of an electronic device according to an embodiment of the present application;

FIG. 2A is a diagram of a software architecture provided by an embodiment of the present application;

FIG. 2B is a diagram illustrating a software architecture of a distributed data search service provided by an embodiment of the present application;

FIG. 2C is a schematic diagram of a software architecture for a distributed data search service provided by another embodiment of the present application;

FIG. 3A is a schematic flow chart diagram illustrating a distributed data search method according to an embodiment of the present application;

FIG. 3B is a flowchart illustrating a distributed data search method according to an embodiment of the present application;

FIG. 4A is a schematic flow chart diagram illustrating a distributed data search method according to another embodiment of the present application;

fig. 4B is a flowchart illustrating a distributed data search method according to another embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be noted that, in the case of conflict, the embodiments and features of the embodiments in the present application may be combined with each other,

the terminology used in the following examples is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of this application and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, such as "one or more", unless the context clearly indicates otherwise.

It should also be understood that in the embodiments of the present application, "a plurality" and "one or more" mean one, two or more; "and/or" describes the association relationship of the associated objects, indicating that three relationships may exist; for example, a and/or B, may represent: a alone, both A and B, and B alone, where A, B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

The terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when.. or" upon "or" in response to a determination "or" in response to a detection ".

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

In order to explain the technical means of the present application, the following description will be given by way of specific examples.

For example, different electronic devices may back up respective data to the cloud server through the internet, and then synchronize data from other electronic devices, which is backed up to the cloud server, to the local computer, so as to implement data sharing of different electronic devices, and thus implement data search from other electronic devices in the local computer.

According to the scheme, synchronization of the internet cloud is relied on, on one hand, different electronic equipment needs to log in by using the same account, and different account numbers cannot directly search shared data of other electronic equipment; on the other hand, all the contents can be searched only after all the data files of other electronic devices are synchronized to the local computer, and the storage space of the local computer is wasted.

For another example, different electronic devices may be directly networked through a short-distance communication technology, such as Bluetooth (BT) or wireless fidelity (Wi-Fi) technology, and rely on temporary networking to complete peer-to-peer file transfer to implement data sharing, so that data from other electronic devices may be searched locally.

The scheme needs the local machine to synchronize the data file of the opposite terminal equipment point to point, and the local machine can search the opposite terminal data after the transmission is finished. This solution still relies on the synchronization of metadata or original files, and the native device does not have the capability to directly search for data of the peer device.

For another example, after different electronic devices form a local area network through Wi-Fi technology, the local device may browse a folder of an opposite device through a method related to a File Transfer Protocol (FTP) Protocol.

The scheme needs to keep network connection, only supports the browsing of files layer by layer, has low searching speed, can only search file names and cannot perform full-text retrieval.

Therefore, in the prior art, complicated logics such as data synchronization and network access are needed to realize data search of different electronic devices.

In view of the defects of the prior art, the application provides a synchronization method of index files and a distributed data search method, service application only needs to access a simple interface, and cross-device distributed data search can be achieved without depending on complex logics such as data synchronization and network access.

The index file synchronization (or sharing) method and the distributed data search method provided by the embodiment of the application are suitable for the conditions of cross-device index file synchronization and data search. The index file synchronization method and the distributed data search method can be applied to electronic equipment, the index file synchronization method can be executed by an index file synchronization device configured on the electronic equipment, and the distributed data search method can be executed by a distributed data search device configured on the electronic equipment. The index file synchronizing device and the distributed data searching device can be realized by software and/or hardware of the electronic equipment.

Electronic devices to which embodiments of the present application are applicable may include, but are not limited to: the mobile phone, the tablet computer, the wearable device, the vehicle-mounted device (or car), the Augmented Reality (AR)/Virtual Reality (VR) device, the notebook computer, the ultra-mobile personal computer (UMPC), the netbook, the Personal Digital Assistant (PDA), the smart screen, the television set-top box, the television, the smart sound, the earphone, and the like. The embodiment of the present application does not set any limit to the specific type of the electronic device.

Fig. 1 shows a schematic structural diagram of an electronic device 100.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K via an I2C interface, such that the processor 110 and the touch sensor 180K communicate via an I2C bus interface to implement the touch functionality of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture functionality of electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transmit data between the electronic device 100 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It should be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only an illustration, and does not limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs), such as Wi-Fi networks, BT, Global Navigation Satellite Systems (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, with N being a positive integer greater than 1.

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100 can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (such as audio data, phone book, etc.) created during use of the electronic device 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 100 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic apparatus 100 receives a call or voice information, it can receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic apparatus 100 may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 180B may be used to determine the motion attitude of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., the x, y, and z axes) may be determined by gyroscope sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects a shake angle of the electronic device 100, calculates a distance to be compensated for by the lens module according to the shake angle, and allows the lens to counteract the shake of the electronic device 100 through a reverse movement, thereby achieving anti-shake. The gyroscope sensor 180B may also be used for navigation, somatosensory gaming scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 180C.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip holster using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the electronic device 100 is stationary. The method can also be used for recognizing the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, electronic device 100 may utilize range sensor 180F to range for fast focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light to the outside through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there are no objects near the electronic device 100. The electronic device 100 can utilize the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear for talking, so as to automatically turn off the screen to achieve the purpose of saving power. The proximity light sensor 180G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense the ambient light level. Electronic device 100 may adaptively adjust the brightness of display screen 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 can utilize the collected fingerprint characteristics to unlock the fingerprint, access the application lock, photograph the fingerprint, answer an incoming call with the fingerprint, and so on.

The temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 implements a temperature processing strategy using the temperature detected by temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 performs a reduction in performance of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 100 heats the battery 142 when the temperature is below another threshold to avoid the low temperature causing the electronic device 100 to shut down abnormally. In other embodiments, when the temperature is lower than a further threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown due to low temperature.

The touch sensor 180K is also called a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device 100, different from the position of the display screen 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 180M may acquire a vibration signal of the human vocal part vibrating the bone mass. The bone conduction sensor 180M may also contact the human pulse to receive the blood pressure pulsation signal. In some embodiments, the bone conduction sensor 180M may also be disposed in a headset, integrated into a bone conduction headset. The audio module 170 may analyze a voice signal based on the vibration signal of the bone mass vibrated by the sound part acquired by the bone conduction sensor 180M, so as to implement a voice function. The application processor can analyze heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M, so as to realize the heart rate detection function.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be brought into and out of contact with the electronic apparatus 100 by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

There are many software architecture modes of the electronic device 100, which may include the following: a layered architecture, an event-driven architecture, a micro-core architecture (also called a plug-in architecture), a micro-service architecture, or a cloud architecture.

The embodiment of the present application takes a layered architecture as an example, and exemplifies a software architecture of the electronic device 100.

The layered architecture divides the software into several horizontal layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface.

Fig. 2A is a diagram illustrating a software architecture of the electronic device 100 according to an embodiment of the present disclosure. As shown in fig. 2A, the software architecture is divided into five layers, which are from top to bottom: presentation layer (presentation), business logic layer (business), service layer (service), persistence layer (persistence), and database (database).

Wherein the presentation layer (presentation) may comprise a series of application packages that are responsible for the visual and interactive interaction with the user through the user interface.

And the business layer (business) is used for realizing business logic.

Service layer (service) for providing some common interfaces required by different business logic.

A persistence layer (persistence) for providing data. For example, SQL statements may be placed in the persistence layer.

A database (database) for storing data.

One characteristic of the hierarchical architecture is the separation of concerns (separation of centers). The components in a layer are only responsible for the logic of the layer. The partitioning of components makes it easy for them to implement their own roles and responsibilities, and is also easier to develop, test manage and maintain.

The database is invoked through the business layer even though the business layer does not handle the business rules, which is called hierarchical isolation, which requires such redundancy in the hierarchical architecture. For some functions, if the database is directly accessible from the presentation layer, any subsequent changes to the database will affect the business and presentation layers.

The layered framework uses the layered opening and closing principle. If a layer is closed, every request goes through the layer. Conversely, if the layer is open (open), the request can bypass this layer, going directly to the next layer.

Hierarchical isolation is beneficial to reducing the complexity of the entire application. Certain functions do not need to pass through each layer, and the implementation can be simplified according to the layered opening and closing principle.

It should be noted that each horizontal layer can be divided into more detailed layers.

It should also be noted that fig. 2A is only an exemplary illustration, and the software architecture may be a more complex or simpler layered architecture according to different practical requirements.

For example, in other embodiments, the database shown in FIG. 2A may be replaced with an index library or file. That is, the way of persisting data is not only in the form of a database, but also in the form of a file; for example, the storage mode of the index is not necessarily a database, and may be some index files conforming to the technical format of full-text index (or called inverted index).

For another example, in some other embodiments, the service layer and the service layer shown in fig. 2A may be integrated into one service layer, and the integrated service layer is a carrier for providing an internal implementation logic of a functional interface to the outside, which provides both an interface and a service logic.

Fig. 2B is a diagram illustrating a software architecture of a distributed data search service implemented on the electronic device 100 according to an embodiment of the present application. The distributed data search service may open a distributed search interface to the system and/or application.

The software architecture of the distributed data search service shown in fig. 2B is divided into four layers, which are from top to bottom: an Application (APP) layer, a distributed search interface, a distributed search service, and an index file.

The application layer, the presentation layer depicted in FIG. 2A, may comprise a series of application packages.

As shown in fig. 2B, the application package may include short message, calendar, memo, file management, contacts, and other applications.

The distributed search interface and distributed search service may be placed at the service layer shown in FIG. 2A.

As shown in fig. 2B, the distributed search interface includes indexing, searching, synchronization, and configuration. Correspondingly, the distributed search service includes an indexing component, a search component, a synchronization component, and a configuration component.

The index component can be used for analyzing data and establishing full-text index of the local data.

The synchronization component can be employed to synchronize full-text indexes of data among disparate electronic devices.

The search component can be operative to search shared data of disparate electronic devices.

The configuration component may be used for a user to set one or more of synchronization parameters, search parameters, synchronization policies, search policies, storage locations, and the like.

Synchronization parameters include, but are not limited to: at least one of a synchronization object and a synchronization method. The synchronization object refers to whether synchronization is required, including but not limited to: it may be specified by the user that certain services (e.g., short messages, contacts, notes, etc.) may be synchronized, while other services (e.g., instant chat tools, etc.) may not be synchronized; it may also be specified by the user that certain types of data (e.g., photos and videos) may be synchronized, while the remaining types of data (e.g., network links or application installation packages, etc.) may not be synchronized, and so on. Synchronization methods include, but are not limited to: and automatic synchronization, namely, synchronization after confirmation by a user, active synchronization to opposite-end equipment or passive synchronization to opposite-end equipment and the like. For example, actively synchronizing to the peer device includes actively sending a full-text index of the synchronization data to the peer device, and passively synchronizing to the peer device includes sending a full-text index of the synchronization data to the peer device in response to a synchronization data acquisition request of the peer device.

The search parameters include one or more of conditions that trigger a search event, search objects, and the like. The search object refers to a search range, for example, searching an index library or the like.

The synchronization strategy includes whether encryption and decryption are needed in the process of sending the full text index of the synchronization data to the opposite terminal equipment. More generally, some services may be specified by the user to synchronize data automatically, while the rest of the services require user confirmation to synchronize data.

The search strategy includes how many search results are displayed, etc.

The storage location includes one or more of a storage location of the local index file, a storage location of the local index file that does not need to be synchronized, a storage location of the local index file that needs to be synchronized, a storage location of the index file from other electronic devices, and the like.

The index file may be placed at the level of the database shown in FIG. 2A. The index file includes a native index, and index files for other electronic devices. An index repository may be established to store index files.

The device A and the device B are connected with the same network, or a short-distance sharing network is established, or the devices log in by adopting the same account number, and the two devices share respective data. As shown in fig. 2B, the index file stored in device a includes the native index and the index of device B. The index file stored in device B includes the native index and the index of device a.

It should be understood that fig. 2B is only an exemplary illustration, and the software architecture may be a more complex or simpler layered architecture according to different practical requirements.

In the embodiment of the application, a device a and a device B establish a sharing group or log in by using the same account, if the device a shares a file 1 and the device B shares a file 2, after establishing and synchronizing an index file through a distributed data search service, the device a can search the file 2 of the device B on the local computer, and the device B can search the file 1 of the device a on the local computer. Therefore, according to the scheme provided by the embodiment of the application, metadata or original files do not need to be synchronized to opposite-end equipment, and the burden of data transmission and data storage is greatly reduced.

Fig. 2C is a diagram illustrating a software architecture of a distributed data search service implemented on the electronic device 100 according to an embodiment of the present application. The distributed data search service may open a distributed search interface to the system and/or application.

The software architecture of the distributed data search service shown in fig. 2C is divided into four layers, which are from top to bottom: an Application (APP) layer, a distributed search interface, a distributed search service, and an index file.

As shown in fig. 2C, the application package may include short message, calendar, memo, file management, contacts, and other applications.

As shown in fig. 2C, the distributed search interface includes indexing, searching, and configuration. Correspondingly, the distributed search service comprises an indexing component and a search component configuration component.

The index file comprises a local index library and a distributed index library, the distributed index library is established on a distributed file system, the local index library comprises index files which do not need to be synchronized by a local machine, and the distributed index library comprises index files which need to be synchronized by the local machine;

the index component can be used for analyzing data and establishing full-text index of the local data. And storing the index files which do not need to be synchronized by the local machine to a local index library, and storing the index files which need to be synchronized by the local machine to a distributed index library.

The search component can be operative to search the shared data of the different electronic devices in the local index repository and the distributed index repository.

It should be understood that fig. 2C is only an exemplary illustration, and the software architecture may be a more complex or simpler layered architecture according to different practical requirements.

In some embodiments of the present application, different electronic devices constitute a distributed file system, for example, device a and device B constitute a distributed file system. After the distributed index file is established in the distributed file system through the distributed data search service, the device A can search the file 2 of the device B through the distributed file system in the local machine, and the device B can search the file 1 of the device A through the distributed file system in the local machine. Therefore, according to the scheme provided by the embodiment of the application, metadata or original files do not need to be synchronized to opposite-end equipment, the burden of data transmission and data storage is greatly reduced, the service application only needs to access a simple interface, cross-equipment distributed search can be achieved through a distributed file system, and complex logics such as data synchronization and network access do not need to be achieved.

The flow of implementing the embodiments of the present application is described next by two non-limiting examples.

Fig. 3A and fig. 3B are flow charts illustrating an implementation of a distributed data search method according to an embodiment of the present application. Referring to fig. 3A and 3B, before performing the distributed data search, the index file needs to be shared among different electronic devices, for example, the index file of device a is shared with device B, and the index file of device B is shared with device a. The sharing process of the index file, the process of distributed search and the implementation principle will be described in detail with reference to fig. 3A and 3B.

The sharing process of the index file is introduced first. The sharing process of the index file comprises the following steps:

s310, calling an index interface, analyzing the metadata through an index component corresponding to the index interface, and establishing an index file of the metadata.

In the embodiment of the present application, an index interface is provided for calling a service APP, where the service APP includes but is not limited to: short messages, calendars, memos, file management, contacts, etc. It should be noted that, more generally, the service APP including the search function is all applicable to the technical solution provided in the embodiment of the present application.

In an embodiment of the present application, in response to a monitored index establishment event, an index interface is called, metadata is analyzed through an index component corresponding to the index interface, and an index file of the metadata is established.

The index event refers to an event that the electronic equipment calls an index interface, analyzes metadata through an index component corresponding to the index interface, and establishes an index file of the metadata. The indexing event is typically triggered autonomously by the electronic device when it listens that a triggering condition is met, including, but not limited to, the electronic device adding new metadata. The new metadata includes, but is not limited to: the newly shot images or videos of the electronic equipment and the newly received files comprise short messages, audios or audios and the like.

When the electronic equipment monitors an index establishing event, an index interface is called in response to the monitored index establishing event, metadata transmitted by a service is analyzed through an index component corresponding to the index interface, and an index file of the metadata is established.

And S320, calling a synchronous interface, and synchronizing the index files among different electronic devices through the synchronous components corresponding to the synchronous interface.

As described above, in the embodiment of the present application, the configuration component may be used for setting the synchronization parameter and/or the synchronization policy, etc. by the user.

In one embodiment of the present application, the situation of automatically synchronizing data is set by a user or by default. In this case, different electronic devices establish a sharing group or log in by using the same user account, and since the distributed search service can create a synchronization pipeline, after an index file of metadata is established, a synchronization interface can be called, and the index file is synchronized among the different electronic devices through a synchronization component corresponding to the synchronization interface.

In one embodiment of the present application, user confirmation is required to synchronize data. In this case, different electronic devices establish a sharing group or log in by using the same user account, and since the distributed search service can create a synchronization pipeline, after an index file of metadata is created, the electronic devices can pop up a user confirmation interface, and after the user confirms that data can be shared, the synchronization interface can be called, and the index file is synchronized among the different electronic devices creating the synchronization pipeline through a synchronization component corresponding to the synchronization interface.

As shown in fig. 3A, the device a and the device B establish a sharing group or log in by using the same user account, the index file of the device a is synchronized to the device B, and the index file of the device B is synchronized to the device a, thereby realizing index synchronization between different devices.

In an embodiment of the application, after different electronic devices access a network, an index file is transmitted through a socket network channel, so that the index file is synchronized among the different electronic devices.

After the index files are synchronized among different electronic devices, cross-device distributed search can be achieved. The flow of the distributed search then continues as described in connection with fig. 3A and 3B.

S330, responding to the monitored search event, calling a search interface, and searching a synchronous index library through a search component to obtain a search result, wherein the synchronous index library comprises index files of the local device and index files of other electronic equipment.

In the embodiment of the application, the search event refers to an event that the electronic device calls a search interface and searches a synchronous index library through a search component corresponding to the search interface to obtain a search result. The search event is generally triggered by a user performing a preset operation on a search interface provided by the electronic device, where the preset operation includes an operation of inputting a search condition. The search condition includes, but is not limited to, one or more combinations of sentences, keywords, pictures, and the like. The search result refers to a search result that meets the search condition. The preset operations include, but are not limited to: the cursor control operation comprises the cursor control operation performed through a keyboard, and/or a mouse, and/or a remote control stick, and/or a track ball, and/or an operation stick, and/or a touch panel, and the like. The embodiment of the present application does not limit the manner of triggering the search event.

When the electronic equipment monitors the search event, the electronic equipment responds to the monitored search event and calls a search interface to search a local synchronous index library through a search component. The synchronous index library comprises index files of the local electronic equipment and index files of other electronic equipment. The other electronic devices are electronic devices other than the local device. Since the local synchronous index library comprises the index file of the local electronic device and the index files of other electronic devices, the search results of other electronic devices can be obtained locally.

It should be noted that, in other embodiments of the present application, as described above, the configuration component may be used for setting the search parameters and the search policy, etc. by the user. The user can set the search range according to actual requirements through the configuration component, for example, the local index file in the synchronous index library or the index file of other electronic equipment is searched, or both the local index file and the index file of other electronic equipment are searched, and the like. This is not limited by the present application.

And S340, displaying the search result.

And the searching component feeds back the searching result after obtaining the searching result meeting the searching condition by searching the synchronous index library, and displays the searching result through the display interface.

According to the scheme provided by the embodiment of the application, on one hand, metadata or original files do not need to be synchronized to opposite-end equipment, only the index files need to be synchronized to the opposite-end equipment, and the size of the index files is about 30% of that of the original data, so that the transmission efficiency is greatly improved, and the storage burden is also reduced. On the other hand, the interface of the local machine is called during searching, cross-equipment and cross-network are not involved, complicated logics such as network access and the like are not needed, the process is simple, the distributed searching experience is completely consistent with the local machine, the efficiency is improved, and therefore the user experience is improved. On the other hand, after the index file is synchronized, even if other electronic devices are offline, the data of the offline devices can be searched in a distributed mode.

Fig. 4A and 4B are flow charts illustrating an implementation of another distributed data searching method according to an embodiment of the present application.

Fig. 4A and 4B are flow charts illustrating an implementation of a distributed data search method according to an embodiment of the present application. Referring to fig. 4A and 4B, before performing the distributed data search, the index file needs to be shared among different electronic devices, for example, the index file of device a is shared with device B, and the index file of device B is shared with device a. The sharing process of the index file, the process of distributed search and the implementation principle will be described in detail with reference to fig. 4A and 4B.

and S410, calling an index interface, analyzing the metadata through an index component corresponding to the index interface, and establishing an index file of the metadata.

The index event refers to an event that the electronic equipment calls an index interface, analyzes metadata through an index component corresponding to the index interface, and establishes an index file of the metadata. The indexing event is typically triggered autonomously by the electronic device when it listens that a triggering condition is met, including, but not limited to, the electronic device adding new metadata. The new metadata refers to metadata that the historical index event does not cover. Including but not limited to: the newly shot images or videos of the electronic equipment and the newly received files comprise short messages, audios or audios and the like.

S420, if the metadata belong to local metadata, storing an index file of the metadata to a local index library; and if the metadata belongs to the distributed metadata, storing the index file of the metadata to the distributed file system.

The local metadata refers to metadata which does not need to synchronize the index file, and the distributed metadata refers to metadata which needs to synchronize the index file.

As previously mentioned, in the embodiments of the present application, the configuration component may be used for a user to set a synchronization object and/or a storage location, etc. Therefore, in the embodiment of the application, the synchronization object is determined through user settings or default settings of a system, and it can be further determined whether the metadata belongs to local metadata or distributed metadata, and if the metadata belongs to the local metadata, the index file of the metadata is stored in the local index library; and if the metadata belongs to the distributed metadata, storing the index file of the metadata to the distributed file system.

Distributed file system means that the physical storage resources managed by the file system are not necessarily directly connected to the local node, but are connected to the node (which may be understood simply as a computer) via a computer network. The design of a distributed file system is based on client and server schemas. A typical network may include multiple servers for access by multiple users. In addition, the peer-to-peer nature allows some systems to play dual roles as client and server. For example, a user may publish (or otherwise be referred to as sharing or synchronizing) a directory that allows other clients to access, and once accessed, the directory appears to the clients as if a local drive were used.

In an embodiment of the application, a distributed index library is established in a distributed file system, and the distributed index library comprises a local distributed index file. A distributed index file is an index file that requires synchronized metadata.

The embodiment shown in fig. 4A and 4B is different from the embodiment shown in fig. 3A and 3B in that the synchronization of the index files is not separately implemented, that is, the index files do not need to be separately synchronized by the synchronization component, but the sharing of the index files among different electronic devices is implemented by relying on a distributed file system.

As previously mentioned, the configuration component can also be used for user setting of synchronization patterns and the like.

In an embodiment of the present application, the situation of automatically synchronizing distributed metadata is set by a user setting or a system default setting. In this case, after the index file of the metadata is created, if the metadata belongs to the distributed metadata, the index file of the metadata is stored in the distributed file system.

In an embodiment of the present application, user confirmation is required to synchronize the distributed metadata. In this case, after the index file of the metadata is created, if the metadata belongs to the distributed metadata, the electronic device may pop up a user confirmation interface, and after the user confirms that the distributed metadata can be shared, the index file of the metadata is stored in the distributed file system.

After the distributed index file is stored in the distributed file system, the electronic equipment is accessed to the network, and cross-equipment access can be realized through the distributed file system. The flow of the distributed search then continues as described in connection with fig. 4A and 4B.

And S430, responding to the monitored search event, calling a search interface, and searching the local index library and/or the distributed file system through the search component to obtain a search result.

In the embodiment of the application, the event search refers to an event that the electronic device calls a search interface, and searches the local index library and/or the distributed index library through a search component corresponding to the search interface to obtain a search result.

The search event is generally triggered by a user performing a preset operation on a search interface provided by the electronic device, where the preset operation includes an operation of inputting a search condition. The search condition includes, but is not limited to, one or more combinations of sentences, keywords, pictures, and the like. The search result refers to a search result that meets the search condition. The preset operations include, but are not limited to: the cursor control operation comprises the cursor control operation performed through a keyboard, and/or a mouse, and/or a remote control stick, and/or a track ball, and/or an operation stick, and/or a touch panel, and the like. The embodiment of the present application does not limit the manner of triggering the search event.

When the electronic equipment monitors the search event, the electronic equipment responds to the monitored search event, calls a search interface, and searches the local index library and/or the distributed file system through the search component to obtain a search result.

It is noted that, as mentioned above, the configuration component may be used by a user to set a search object, which may be a local index repository and/or a distributed file system.

After the distributed index file is stored in the distributed file system, if the search object comprises the distributed file system, the electronic device is required to access the network, and cross-device access can be realized through the distributed file system, otherwise, the distributed index file of the local device can only be accessed in the distributed file system, but the distributed index files of other electronic devices cannot be accessed.

S440, displaying the search result.

And after the search component obtains the search result meeting the search condition, feeding back the search result, and displaying the search result through a display interface.

According to the scheme provided by the embodiment of the application, on one hand, metadata or original files do not need to be synchronized to opposite-end equipment, and index files do not need to be synchronized to opposite-end equipment, so that the burden of data transmission and data storage is greatly reduced. On the other hand, cross-device distributed search can be achieved by calling an interface of the local computer during search, complex logics such as network access and the like do not need to be achieved, the process is simple, the distributed search experience is completely consistent with the local computer, the efficiency is improved, and therefore the user experience is improved.

The embodiment of the present application further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program, so that the electronic device can implement the steps in the above method embodiments.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments may be implemented.

Embodiments of the present application provide a computer program product, which, when running on an electronic device, causes the electronic device to perform the steps in the above-mentioned method embodiments.

Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/electronic device, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunication signals, and software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed electronic device and method may be implemented in other ways. For example, the above-described electronic device embodiments are merely illustrative. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A method of distributed data searching, comprising:

synchronizing the index files among different electronic devices creating a synchronization pipeline;

and displaying the search result.

2. The method of claim 1, wherein creating an index file of metadata in response to the monitored indexing event comprises:

responding to the monitored index establishing event, calling an index interface, analyzing metadata through an index component corresponding to the index interface, and establishing an index file of the metadata;

the synchronizing the index file among the different electronic devices creating the synchronization pipeline includes:

and calling a synchronous interface, and synchronizing the index file between the local machine and other electronic equipment establishing a synchronous pipeline with the local machine through a synchronous component corresponding to the synchronous interface.

3. The method of claim 1 or 2, wherein searching the local synchronous index library for search results in response to the intercepted search event comprises:

and responding to the monitored search event, calling a search interface, and searching a local synchronous index library through a search component corresponding to the search interface to obtain a search result.

4. A method of distributed data searching, comprising:

and displaying the search result.

5. A method for sharing an index file, comprising:

6. A method of distributed data searching, comprising:

if the metadata belongs to local metadata which does not need to be synchronized, storing an index file of the metadata to a local index database; if the metadata belongs to distributed metadata needing synchronization, storing an index file of the metadata to a distributed file system;

and displaying the search result.

7. The method of claim 6, wherein creating an index file of metadata in response to the monitored indexing event comprises:

and responding to the monitored index establishing event, calling an index interface, analyzing the metadata through an index component corresponding to the index interface, and establishing an index file of the metadata.

8. The method of claim 6 or 7, wherein searching the local index repository and/or the distributed file system for search results in response to the intercepted search event comprises:

and responding to the monitored search event, calling a search interface, and searching a local index library and/or a distributed file system through a search component corresponding to the search interface to obtain a search result.

9. A method of distributed data searching, comprising:

and displaying the search result.

10. A method for sharing an index file, comprising:

11. The distributed data search service system is characterized by comprising four layers, wherein the four layers are respectively as follows: the system comprises an application program layer, a distributed search interface, a distributed search service and an index file;

12. The distributed data search service system is characterized by comprising four layers, wherein the four layers are respectively as follows: the system comprises an application program layer, a distributed search interface, a distributed search service and an index file;