Communication method and related equipment
By using queue management module address information in electronic devices, the module files of wearable devices are automatically downloaded and installed, which solves the complex user operations and realizes an efficient module installation process.
Patent Information
- Application Number
- CN202510614607.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-13
- Publication Date
- 2025-08-26
AI Technical Summary
When users install multiple module files on wearable devices, the operation is complicated and takes up a long time, and the prior art has failed to effectively simplify the installation process.
By using the address information of the queue management module in electronic devices, the download and installation process of module files is automatically executed, and the first-in-first-out characteristics of the queue ensure that the module is installed in the order specified by the user, decoupling the installation process and user operations.
It reduces the complexity and time consumption of user operations, simplifies the installation process of module files, improves installation efficiency, and meets user installation needs.
Smart Images

Figure CN120540667A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and in particular to a communication method and related equipment. Background Art
[0002] Wearable devices such as smart bracelets and smart watches are comfortable to wear and integrate multiple functions, making them widely popular. However, due to their small size and limited storage resources, the number of modules that can be installed in a wearable device is restricted. Users can operate on the wearable device to instruct it to retrieve and install module files. Alternatively, users can operate on an electronic device such as a mobile phone to send the module file to the wearable device and instruct the wearable device to install the module file.
[0003] When a user uses an electronic device to install multiple module files on a wearable device, the user needs to manually click to install each module file one by one, and other operations cannot be performed during the installation process, which makes the user's operation complicated and time-consuming. Summary of the Invention
[0004] The embodiments of the present application provide a communication method and related devices that can reduce the complexity of user processing.
[0005] In a first aspect, a communication method is provided, which is applied to a first electronic device, the method comprising: upon receiving an installation operation from a user, adding address information of each module in at least one module indicated by the installation operation in a first queue; reading the earliest added address information from the first queue, deleting the earliest added address information in the first queue, and performing a first operation based on the read address information until no address information exists in the first queue, the first operation based on the i-th address information read from the first queue comprising: sending the i-th address information to a server; receiving the i-th module file sent by the server according to the i-th address information; sending i-th installation information to the wearable device, the i-th installation information including the i-th module file, the i-th installation information instructing the wearable device to install the i-th module file, where i is a positive integer.
[0006] In some possible implementations, the first operation based on the i-th address information also includes: after sending the i-th installation information to the wearable device, receiving the i-th installation completion information sent by the wearable device, the i-th installation completion information is sent when the wearable device completes the installation of the i-th module file; the operation of sending the i+1-th installation information to the wearable device in the first operation based on the i+1-th address information is performed when the i-th installation completion information is received.
[0007] In some possible implementations, the first operation based on the (i+1)th address information is performed upon receiving the (i)th installation completion information.
[0008] In some possible implementations, the i-th address information in the first queue is deleted upon receiving the i-th installation completion information.
[0009] In some possible implementations, the earliest added address information is read from the first queue, the earliest added address information in the first queue is deleted, and a first operation is performed based on the read address information until no address information exists in the first queue. It also includes: after sending the i-th module file to the wearable device, deleting the i-th address information in the first queue, reading the i+1th address information from the first queue, and performing the first operation based on the i+1th address information to the server and receiving the i+1th module file sent by the server.
[0010] In some possible implementations, the method further includes: upon receiving the first operation, determining whether the first queue exists in the first electronic device; if the first queue does not exist in the first electronic device, creating the first queue; and if all address information in the first queue is deleted, destroying the first queue.
[0011] In some possible implementations, different modules represent different watch face interfaces.
[0012] In a second aspect, a communication device is provided, comprising units for executing the method of the first aspect or any possible implementation of the first aspect. The device may be an electronic device or a chip within an electronic device.
[0013] In a third aspect, an electronic device is provided, comprising a memory and a processor, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the electronic device executes the method of the first aspect or any possible implementation method of the first aspect.
[0014] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed, the method in the above-mentioned first aspect or any possible implementation of the first aspect is executed.
[0015] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes computer program instructions. When the computer program instructions are executed, the method in the above-mentioned first aspect or any possible implementation of the first aspect is executed.
[0016] In a sixth aspect, an embodiment of the present application provides a chip comprising a processor and a data interface, wherein the processor reads instructions stored in a memory through the data interface to implement the method in the above-mentioned first aspect or any possible implementation method of the first aspect.
[0017] Compared with the prior art, the present embodiment has the following advantages: when a user triggers an installation operation, the first queue manages the address information of the module indicated by the installation operation and executes the installation process for the module file determined by the server based on the address information. This decouples the installation process from the user operation, eliminating the need for the user to wait for the completion of one module file transfer before manually triggering the transfer of another module file. This reduces the complexity of user operations and shortens the time it takes. The first-in-first-out feature of the queue ensures that the modules are installed in the order specified by the user, better meeting user needs. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1 It is a schematic diagram of a communication system;
[0019] Figure 2 is a schematic flow chart of a communication method provided in an embodiment of the present application;
[0020] Figure 3 It is a schematic diagram of a graphical user interface;
[0021] Figure 4 It is a schematic diagram of a data structure;
[0022] Figure 5 is a schematic flow chart of a communication method provided in an embodiment of the present application;
[0023] Figure 6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0024] Figure 7 This is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0025] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.
[0026] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.
[0027] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections thereof.
[0028] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
[0029] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.
[0030] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized.
[0031] Wearable devices such as smart bracelets and smart watches are comfortable to wear and integrate multiple functions, making them widely popular.
[0032] Wearable devices are small in size and have limited storage resources, limiting the number of module files they can store. Wearable devices can download and install module files from a server based on user instructions. However, wearable device displays are typically small, making them less convenient for users to operate.
[0033] For example, wearable devices can support users changing watch face interfaces. Different watch face interfaces can highlight different information. Users can change watch faces to suit their mood, occasion, or style, showcasing their unique personality. A module file can be a watch face file. Different watch face interfaces can correspond to different watch face files. After installing a watch face file, the electronic device can run the watch face file to display the watch face interface corresponding to the watch face file.
[0034] Figure 1 A communication system includes a first electronic device 110, a wearable device 120, and a server 130. A communication connection exists between the first electronic device 110 and the wearable device 120. A storage communication connection exists between the first electronic device 110 and the server 130. The first electronic device may be, for example, a smartphone.
[0035] The user can install the app on the first electronic device 110. In response to the user's installation operation, the first electronic device 110 can send a download request to the server 120. The download request instructs the server to send the target watch face file indicating the installation operation to the electronic device. After receiving the target watch face file from the server 130, the first electronic device 110 can send the target watch face file to the wearable device 120 and instruct the wearable device 120 to install the target watch face file.
[0036] However, if the user needs to install multiple watch face files on the wearable device 120, it is necessary to download and transfer the target watch face file of each installation operation instruction to the wearable device 120, and then perform other installation operations on the first electronic device to instruct the first electronic device to download and transfer other watch face files. The operations performed by the user on the first electronic device 110 are relatively complicated.
[0037] In order to solve the above problems, an embodiment of the present application provides a communication method that can reduce the complexity of user operations.
[0038] Figure 2 This is a schematic flowchart of a communication method provided in an embodiment of the present application. Figure 2 The method shown can be applied in a communication system. The communication system may include a first electronic device, a wearable device, and a server.
[0039] The software system of the first electronic device can adopt a layered architecture. This layered architecture divides the software into several layers, each with clear roles and divisions of labor. Layers communicate with each other via software interfaces. The software system of an electronic device may include an application layer, an application framework layer, an Android runtime and system libraries, and a driver layer. The software system of an electronic device can be understood as the software system of the processor in the electronic device.
[0040] The application layer can include a series of application packages, such as the first app. The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions. The application framework layer may include management services.
[0041] The first electronic device may further include a first queue, a first communication module, and a second communication module. Each of the first communication module and the second communication module as a whole may not directly correspond to a specific layer of the operating system (such as the kernel layer, the system library, etc.). The communication module can generally be understood as an independent component or subsystem, including parts located at multiple layers in the Android system. The first communication module may, for example, be a mobile communication module. The second communication module may, for example, be a wireless communication module, such as a Bluetooth (BT) module.
[0042] The electronic device may further include a memory such as a Flash memory and a cache. The first storage unit and the second storage unit may be located in the cache. The third storage unit may be located in the Flash memory.
[0043] Step S201: The first APP receives the user's installation operation.
[0044] The user's installation operation may indicate at least one module. The user's installation operation may include selecting the at least one module. The user's installation operation may be performed on a graphical user interface (GUI) displayed on an electronic device. A GUI provides a way for a user to interact with a computer application through graphical elements (such as windows, icons, menus, and buttons).
[0045] Electronic devices can display Figure 3 The application interface 310 shown in FIG. Application interface 310 may be an interface provided by the first application. Application interface 310 includes a module icon 311 for each of the multiple modules, a selection control 312 corresponding to each module, and an installation control 320. The selection control 312 corresponding to each module is used to indicate whether the module corresponding to the module control is selected.
[0046] The user's installation operation may include a user selecting a module and clicking an installation control 320. The user may click a selection control 312 corresponding to a module to select or deselect the module corresponding to the selection control 312. The user clicking the selection control 312 to select the module corresponding to the selection control 312 may be understood as the user selecting the module corresponding to the selection control 312.
[0047] When it is detected that the user can click the installation control 320 , the first APP may proceed to step S202 .
[0048] Step S202: The first APP determines whether a first queue exists in the first electronic device.
[0049] If the first electronic device has a first queue, the first APP may proceed to step S205 to step S206. If the first electronic device does not have a first queue, the first APP may proceed to step S203.
[0050] Step S203: The first APP sends a queue request to the management service.
[0051] In the case of receiving the queue request sent by the first APP, the management service may proceed to step S204.
[0052] Step S204: The management service creates a first queue.
[0053] A queue is a linear data structure that follows the FIFO (First-In-First-Out) principle. Figure 4 As shown, the electronic device can add elements to the tail of the queue, view and / or remove elements at the head of the queue, and can also determine the number of elements in the queue or whether the queue is empty.
[0054] After the first APP creates the first queue in the management service, it can perform steps S205 to S206.
[0055] In step S205 , the first APP adds the watch face file information of at least one watch face indicated by the installation operation to the first queue.
[0056] The first APP can add the watch face file information of the at least one watch face to the end of the first queue.
[0057] The watch face file information of each watch face may include the watch face identification (ID) and download address, etc.
[0058] Step S206: The first APP sends a download request to the first communication module.
[0059] The download request instructs the first communication module to read a dial file information in the first queue and obtain the dial file according to the dial file information.
[0060] In the case of receiving the download request sent by the first APP, the first communication module may perform steps S207 to S208.
[0061] Step S207: The first communication module reads a dial file information in the first queue.
[0062] Step S208: The first communication module sends a watch face file request to the server indicated by the watch face file information.
[0063] The server indicated by the dial file information can be understood as the server indicated by the download address.
[0064] The watch face file request instructs the server to send the watch face file indicated by the watch face file information to the first electronic device.
[0065] When the server receives the dial file request sent by the first communication module, step S209 may be performed.
[0066] Step S209: The server sends the watch face file indicated by the watch face file information to the first communication module.
[0067] When the first communication module completes receiving the dial file sent by the server, step S210 can be performed.
[0068] Step S210: The first communication module sends download completion information to the first APP.
[0069] When the first APP receives the download completion information sent by the first communication module, it can proceed to step S211.
[0070] Step S211: The first APP sends a transmission request to the second communication module.
[0071] The transmission request instructs the second communication module to send the watch face file to the wearable device. In the case of receiving the transmission request sent by the first APP, the second communication module can proceed to step S212.
[0072] Step S212: The second communication module sends the watch face file to the wearable device.
[0073] When the wearable device completes receiving the watch face file sent by the second communication module, step S213 may be performed.
[0074] Step S213: The wearable device sends a reception completion message to the second communication module.
[0075] When the second communication module receives the reception completion information sent by the wearable device, step S214 may be performed.
[0076] Step S214: The second communication module sends a transmission completion message to the first APP.
[0077] When the wearable device completes receiving the dial file sent by the second communication module, the dial file can be installed. When the wearable device completes installing the dial file, step S215 can be performed.
[0078] Step S215: The wearable device sends installation completion information to the second communication module.
[0079] When the second communication module receives the installation completion information sent by the wearable device, step S216 may be performed.
[0080] Step S216: The second communication module sends an installation completion message to the first APP.
[0081] When the first APP receives the installation completion information sent by the second communication module, the first APP may proceed to step S217.
[0082] Step S217: The first APP deletes a watch face file information in the first queue.
[0083] The first APP's deletion of the dial file information in the first queue can be understood as removing a dial file information at the head of the first queue.
[0084] After the first communication module receives the download request sent by the first APP in step S206 , the first communication module may proceed to step S218 .
[0085] Step S218: The first communication module determines whether the head of the first queue changes.
[0086] For example, after receiving the download request sent by the first APP in step S206, the first communication module may monitor whether the head of the first queue changes.
[0087] When the head of the first queue changes, the first communication module may proceed to step S219.
[0088] Step S219: The first communication module determines whether the first queue is empty.
[0089] If the first communication module determines that the first queue is empty, the first communication module may not perform subsequent processing. If the first communication module determines that the first queue is not empty, the first communication module may perform step S207 again, so that the first electronic device downloads the watch face file corresponding to the new watch face information at the head of the first queue from the server and transmits the watch face file to the wearable device.
[0090] For example, the management service may determine whether the first queue head changes and whether the first queue is empty. If the first queue is not empty, the management service may send a download request to the first communication module so that the first communication module may perform step S207 again.
[0091] Alternatively, after performing step S217 , the first APP may determine whether the first queue is empty. If it is determined that the first queue is not empty, the first APP may perform step S206 again.
[0092] For example, during the process of the first communication module receiving the watch face file, the first communication module may send the progress of receiving the watch face file to the first app. The first app may generate a download progress graphic, and the interface provided by the first app may include the download progress graphic. The download progress graphic may indicate the progress of the first communication module receiving the watch face file. The progress of the first communication module receiving the watch face file can be understood as the percentage of the data received by the first communication module in the watch face file.
[0093] During the process of the second communication module transmitting the watch face file to the wearable device, the second communication module may send the progress of the watch face file transmission to the first app. The first app may generate a transmission progress graphic, and the interface provided by the first app may include the transmission progress graphic. The download progress graphic may indicate the progress of the watch face file transmission by the second communication module. The progress of the watch face file transmission by the second communication module can be understood as the percentage of the data sent by the second communication module to the watch face file.
[0094] Figure 2 Taking the dial as an example, the various steps performed by the first electronic device when the user operates the first electronic device are described. Figure 5 The method shown is implemented.
[0095] Figure 5 This is a schematic flow chart of a communication method provided in an embodiment of the present application. The execution subject of the method provided in an embodiment of the present application can be a first electronic device, or a software / hardware module capable of image acquisition in the first electronic device. For ease of explanation, the following embodiments are described using the first electronic device as an example.
[0096] Figure 5 The illustrated method may include steps S510 to S520.
[0097] Step S510: When an installation operation is received from a user, address information of each module in at least one module indicated by the installation operation is added to a first queue.
[0098] The installation operation may indicate one or more modules. If the installation operation indicates multiple modules, the installation operation may include a user selecting each of the multiple modules. When adding the address information of multiple modules to the first queue, the address information of each module may be added to the first queue in the order of the selection operation corresponding to each module. This allows the first electronic device and the wearable device to process the module files in a more consistent order with user needs.
[0099] Upon receiving the user's installation operation, the first electronic device may further determine whether the first queue exists. If the first queue exists, the address information of the module indicated by the installation operation may be added to the first queue. If the first queue does not exist, the first queue may be created, and after the first queue is created, the address information of the module indicated by the installation operation may be added to the first queue.
[0100] The address information of each module indicates a path of a module file storing the module in the server.
[0101] Step S520, read the earliest added address information from the first queue, delete the earliest added address information in the first queue, and perform a first operation on the read address information until there is no address information in the first queue, and the first operation for the i-th address information read from the first queue includes: sending the i-th address information to the server; receiving the i-th module file sent by the server according to the i-th address information; sending i-th installation information to the wearable device, the i-th installation information including the i-th module file, the i-th installation information instructing the wearable device to install the i-th module file, i is a positive integer.
[0102] After reading the earliest added address information from the first queue, deleting the address information from the first queue can be performed immediately after reading the address information, or after receiving the module file sent by the server based on the address information, or after sending the module file corresponding to the address information to the wearable device, or after the wearable device completes installation of the module file corresponding to the address information. The module file corresponding to the address information is the module file sent by the server based on the address information.
[0103] Wearable devices have limited processing and storage capabilities. To reduce resource contention and improve system stability, you can install the next module file after the wearable device has completed the installation of the previous module file.
[0104] The first operation for the i-th address information may further include, after sending the i-th installation information to the wearable device, receiving the i-th installation completion information sent by the wearable device. The i-th installation completion information is sent when the wearable device completes installation of the i-th module file. In the first operation for the i+1-th address information, the operation of sending the i+1-th installation information to the wearable device may be performed after receiving the i-th installation completion information.
[0105] In some embodiments, upon receiving the i-th installation completion information, a first operation on the (i+1)-th address information may be performed.
[0106] After the processing of one address information is completed, the next address information will be processed. The processing flow is simple and the reliability is high.
[0107] For example, the i-th address information in the first queue is deleted when the i-th installation completion information is received.
[0108] By deleting the i-th address information in the first queue when receiving the i-th installation completion information, and reasonably setting the deletion time of the address information at the head of the first queue, it is possible to ensure that after the wearable device completes the installation of a certain module file, the next module file will be sent to the wearable device. The processing flow is simple and the reliability is high.
[0109] In other embodiments, there is no need to wait for the wearable device to complete the installation of the i-th module file. While the wearable device is receiving or installing a certain module file, the first electronic device may receive other module files.
[0110] For example, after receiving the i-th module file sent by the server, the first electronic device can delete the i-th address information in the first queue, read the i+1-th address information in the first queue, send the i+1-th address information to the server, and receive the i+1-th module file sent by the server.
[0111] While a wearable device is receiving or installing a module file, the first electronic device can retrieve other module files in preparation for sending them to the wearable device. After the wearable device completes installing one module file, the first electronic device can send the next module file to the wearable device, reducing the total time it takes to install multiple module files.
[0112] For another example, after sending the i-th module file to the wearable device, the i-th address information in the first queue can be deleted, and the i+1-th address information in the first queue can be read, and the i+1-th address information can be sent to the server, and the i+1-th module file sent by the server can be received.
[0113] While a wearable device is installing a module file, the first electronic device is allowed to obtain the next module file in preparation for sending it to the wearable device. Furthermore, while obtaining the next module file, all other module files obtained from the server in the first electronic device are already sent to the wearable device, thus avoiding the module files from occupying a large amount of storage space on the first electronic device. Specifically, while the first electronic device is assisting the wearable device in module installation, the storage space occupied by the first electronic device is minimized.
[0114] When all the address information in the first queue is deleted, the first queue can be destroyed to avoid long-term occupation of the resources of the first electronic device by the assistance for installing the module file on the wearable device, and reduce the impact of the assistance for installing the module file on the first electronic device.
[0115] According to the above solution, when a user triggers an installation operation, the first queue manages the address information of the module indicated by the installation operation and executes the installation process for the module file determined by the server based on the address information. This decouples the installation process from the user operation, eliminating the need for the user to wait for the transfer of one module file to complete before triggering the transfer of another module file, thus reducing the complexity of user operations. The queue's first-in-first-out feature ensures that the modules are installed in the order specified by the user, better meeting user needs.
[0116] Combined with the above Figures 1 to 5 , describes the communication method of the embodiment of the present application in detail, and will be combined with Figure 6 and Figure 7 , describes the device embodiment of the present application in detail. It should be understood that the parameter updating device in the embodiment of the present application can execute the various parameter updating methods in the aforementioned embodiment of the present application, that is, the specific working processes of the following various products can refer to the corresponding processes in the aforementioned method embodiments.
[0117] Figure 6 6 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The parameter updating device 500 may include a processing unit 610 and an acquiring unit 620.
[0118] The acquisition unit 620 is used to acquire the user's installation operation.
[0119] The processing unit 610 is configured to add address information of each module in the at least one module indicated by the installation operation to the first queue.
[0120] The processing unit 610 is further configured to read the earliest added address information from the first queue, delete the earliest added address information in the first queue, and perform a first operation based on the read address information until no address information exists in the first queue.
[0121] The first operation based on the i-th address information read from the first queue includes: sending the i-th address information to the server; receiving the i-th module file sent by the server according to the i-th address information; sending i-th installation information to the wearable device, the i-th installation information including the i-th module file, the i-th installation information instructing the wearable device to install the i-th module file, where i is a positive integer.
[0122] Optionally, the processing unit 610 is further used to receive an i-th installation completion message sent by the wearable device after sending the i-th installation information to the wearable device, where the i-th installation completion message is sent when the wearable device completes the installation of the i-th module file.
[0123] The operation of sending the (i+1)th installation information to the wearable device in the first operation based on the (i+1)th address information is performed when the (i)th installation completion information is received.
[0124] Optionally, the processing unit 610 is further configured to perform the first operation based on the (i+1)th address information upon receiving the (i)th installation completion information.
[0125] Optionally, the i-th address information in the first queue is deleted when the i-th installation completion information is received.
[0126] Optionally, the processing unit 610 is also used to, after sending the i-th module file to the wearable device, delete the i-th address information in the first queue, read the i+1-th address information from the first queue, and execute the first operation based on the i+1-th address information to send the i+1-th address information to the server and receive the i+1-th module file sent by the server.
[0127] Optionally, the processing unit 610 is further configured to, upon receiving the first operation, determine whether the first queue exists in the first electronic device.
[0128] The processing unit 610 is further configured to create the first queue if the first queue does not exist in the first electronic device.
[0129] The processing unit 610 is further configured to destroy the first queue when all address information in the first queue is deleted.
[0130] Optionally, different modules represent different watch face interfaces.
[0131] It should be noted that the parameter updating device 500 is implemented in the form of a functional unit. The term "unit" here can be implemented in the form of software and / or hardware, and is not specifically limited to this.
[0132] For example, a "unit" may be a software program, a hardware circuit, or a combination of the two that implements the aforementioned functionality. The hardware circuit may include an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor) and memory for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components that support the described functionality.
[0133] Therefore, the units of each example described in the embodiments of this application can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0134] Figure 7 Schematic diagram of the structure of an electronic device 700 provided in an embodiment of the present application. Figure 7 As shown, the electronic device 700 of this embodiment includes: at least one processor 701 ( Figure 7 Only one processor is shown), a memory 702, and a computer program 703 stored in the memory 702 and executable on the at least one processor 701, wherein the processor 701 implements the steps of any of the above method embodiments when executing the computer program 703.
[0135] Those skilled in the art will understand that Figure 7 This is merely an example of the electronic device 700 and does not constitute a limitation on the electronic device 700 . The electronic device 700 may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.
[0136] The processor 701 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor.
[0137] In some embodiments, the memory 702 may be an internal storage unit of the electronic device 700, such as a hard disk or memory of the electronic device 700. In other embodiments, the memory 702 may also be an external storage device of the electronic device 700, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. equipped on the electronic device 700. Furthermore, the memory 702 may include both an internal storage unit of the electronic device 700 and an external storage device. The memory 702 is used to store an operating system, application programs, a boot loader, data, and other programs, such as the program code of the computer program. The memory 702 may also be used to temporarily store data that has been output or is about to be output.
[0138] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment section and will not be repeated here.
[0139] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.
[0140] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any of the above method embodiments can be implemented.
[0141] An embodiment of the present application provides a computer program product, which can implement any of the above method embodiments when the computer program product is running.
[0142] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process of the above-mentioned method embodiment by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium can at least include: any entity or device capable of carrying computer program code to the camera / terminal device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium. For example, a USB flash drive, mobile hard drive, magnetic disk, or optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals or telecommunication signals.
[0143] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0144] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0145] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0146] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0147] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.
Claims
1. A communication method, characterized in that: Applied to a first electronic device, the method includes: In the case of receiving an installation operation from the user, adding address information of each module in the at least one module indicated by the installation operation to the first queue; Reading the earliest added address information from the first queue, deleting the earliest added address information in the first queue, and performing a first operation based on the read address information until no address information exists in the first queue, the first operation based on the i-th address information read from the first queue includes: Sending the i-th address information to the server; receiving an i-th module file sent by the server according to the i-th address information; Sending an i-th installation message to the wearable device, where the i-th installation message includes the i-th module file, and the i-th installation message instructs the wearable device to install the i-th module file, where i is a positive integer.
2. The method according to claim 1, characterized in that The first operation based on the i-th address information read from the first queue further includes: After sending the i-th installation information to the wearable device, receiving i-th installation completion information sent by the wearable device, where the i-th installation completion information is sent when the wearable device completes installation of the i-th module file; The operation of sending the (i+1)th installation information to the wearable device in the first operation based on the (i+1)th address information is performed when the (i)th installation completion information is received.
3. The method according to claim 2, characterized in that The first operation based on the (i+1)th address information is performed when the (i)th installation completion information is received.
4. The method according to claim 3, characterized in that The i-th address information in the first queue is deleted when the i-th installation completion information is received.
5. The method according to claim 2, characterized in that The method further comprises: reading the earliest added address information from the first queue, deleting the earliest added address information in the first queue, and performing a first operation based on the read address information until no address information exists in the first queue; After sending the i-th module file to the wearable device, the i-th address information in the first queue is deleted, the i+1-th address information is read from the first queue, and the operation of sending the i+1-th address information to the server and receiving the i+1-th module file sent by the server is performed in the first operation based on the i+1-th address information.
6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Upon receiving the first operation, determining whether the first queue exists in the first electronic device; If the first queue does not exist in the first electronic device, create the first queue; When all address information in the first queue is deleted, the first queue is destroyed.
7. The method according to any one of claims 1 to 5, characterized in that Different modules represent different watch face interfaces.
8. An electronic device, characterized in that: The electronic device comprises a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the electronic device executes the method according to any one of claims 1 to 7.
9. A chip, characterized in that: The system comprises a processor and a data interface, wherein the processor reads instructions stored in a memory through the data interface to implement the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program for implementing the method according to any one of claims 1 to 7.