Communication method, device and system

Abstract

A communication method, apparatus and system, relating to the field of communications, for selecting a suitable / optimal synchronization source device from a plurality of management nodes, the method can be used for selecting a synchronization source device from a plurality of devices in a coverage area where a plurality of domains are located, and taking the plurality of devices including a second device and a first device as an example, the second device and the first device are used for selecting the synchronization source device from the plurality of devices. The method may comprise the following steps: a second device obtains first information comprising high and low domains of the second device, and sends the first information to a first device; and the first equipment receives the first information from the second equipment, and determines the synchronization source equipment for multi-domain synchronization according to the first information. The scheme of the invention can be widely applied to the fields of communication technology, artificial intelligence, Internet of Vehicles, smart home networking and the like.

Description

[0001] This application is a divisional application. The original application has the application number 202411150554.X and the original application date is August 20, 2024. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a communication method, apparatus, and system. Background Technology

[0003] Sparklink (or Nearlink) wireless communication system, often simply referred to as a Sparklink system, is a short-range wireless communication system. A Sparklink system can include grant nodes (G nodes) and terminal nodes (T nodes). When a Sparklink system has multiple grant nodes deployed in adjacent channels, adjacent-channel interference between these nodes can occur.

[0004] To solve the problem of adjacent channel interference mentioned above, it is necessary to select one management node from multiple management nodes. This management node can be called a synchronization source device. Other management nodes can synchronize their time / frequency with this synchronization source device to achieve time / frequency synchronization (or multi-domain synchronization) among the management nodes and avoid adjacent channel interference.

[0005] As can be seen from the above, how to select the synchronization source device from multiple management nodes is the primary problem to be solved in achieving multi-domain synchronization. Summary of the Invention

[0006] This application provides a communication method, apparatus, and system that can determine a suitable / optimal synchronization source device from multiple management nodes.

[0007] To achieve the above objectives, this application adopts the following technical solution:

[0008] Firstly, this application provides a communication method, which can be executed by a first device, such as a first management node, wherein the coverage area of ​​the first device includes multiple domains; the multiple domains correspond to multiple devices; unless otherwise specified, the "first device" in this application can refer to the first device itself, a component within the first device (e.g., a processor, radio frequency unit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first device. The method includes: receiving first information from a second device, including high- and low-level domains of the second device; and determining a source device for multi-domain synchronization based on the first information. The second device is a device within the multiple domains included in the coverage area of ​​the first device.

[0009] Based on the method described in the first aspect, the first device can determine the synchronization source device from the first device and the second device according to the feature of the low-level domain device to initiate multi-domain synchronization domain to the high-level domain device in the Star Flash protocol. Compared with point-to-point protocols based on IEEE 802.11, such as Wireless Direct Link (WDL), selecting the synchronization source device reduces both the latency and complexity of determining the synchronization source device.

[0010] In one possible design, the first information may also include one or more of the following parameters:

[0011] The coverage area of ​​the second device, the multi-domain synchronization feature version of the second device, the power supply type of the second device, the clock source type of the second device, or the identity information of the second device; wherein, the multi-domain synchronization feature version is used to indicate the underlying protocol version supported by the device; the power supply type is used to indicate the type of current, including AC or battery; the clock source type is used to indicate the clock source providing the clock signal, including a local crystal oscillator or a GPS satellite navigation system; the identity information of the second device is used to uniquely identify the second device.

[0012] Based on this possible design, the first device can determine the synchronization source device based on one or more of the following: the high / low level domain of the second device, the coverage range of the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, and the identity information of the second device. This allows the first device to determine a suitable / optimal synchronization source device based on various parameters of the second device.

[0013] In one possible design, the first device determining the synchronization source device based on the first information may include: the first device determining the synchronization source device based on at least one of the following: the high and low level domains of the first device, the coverage range of the first device, the multi-domain synchronization feature version of the first device, the power supply type of the first device, the clock source type of the first device, the identity information of the first device, and the first information from the second device.

[0014] Based on this possible design, the first device can determine the synchronization source device by comparing its own parameters with those of the second device.

[0015] In one possible design, the first device determining the synchronization source device based on the first information may include: the first device determining the synchronization source device based on the value of the parameter with higher priority in the first information; or, the first device determining the synchronization source device based on the weight of the parameter in the first information.

[0016] Based on this possible design, the first device can determine the synchronization source device in multiple ways, which improves the flexibility and applicability of the embodiments of this application.

[0017] In one possible design, the weights of the parameters in the first information are fixed, or the weights of the parameters in the first information are variable. Based on this possible design, the flexibility in selecting the weights of the parameters in the first information is improved.

[0018] In one possible design, the number of bits occupied by the specific values ​​of the parameters in the first information may be the same or different. Based on this possible design, the number of bits occupied by the specific values ​​of the parameters in the first information can be flexibly adjusted according to the specific communication scenario.

[0019] In one possible design, the high-priority parameters include a first parameter; the first device determines the synchronization source device based on the value of the high-priority parameter in the first information, which may include: the first device obtaining the value of the first parameter of the second device, and obtaining the value of the first parameter of the first device; if the value of the first parameter of the second device is greater than the value of the first parameter of the first device, the second device is used as the synchronization source device; if the value of the first parameter of the second device is less than the value of the first parameter of the first device, the first device is used as the synchronization source device.

[0020] Based on this possible design, the first device can compare the value of its own higher-priority first parameter with the value of the first parameter of the second device, and select the device with the larger value of the first parameter as the synchronization source device.

[0021] In one possible design, the first device determines the synchronization source device based on the weights of the parameters in the first information, which may include:

[0022] The first device calculates the first value of the second device by weighting the parameters of the second device according to the weights of the parameters, and calculates the first value of the first device by weighting the parameters of the first device; if the first value of the second device is greater than the first value of the first device, the second device is used as the synchronization source device; if the first value of the second device is less than the first value of the first device, the first device is used as the synchronization source device.

[0023] Based on this possible design, the first device can compare its own first value with the first value of the second device and use the device with the larger first value as the synchronization source device.

[0024] In one possible design, the identity information of the second device may include the identifier of the second device; or, the identity information of the second device may include the hash value of the identifier of the second device.

[0025] Based on this possible design, the identity information of the second device can include different information in different scenarios, which improves the flexibility of the embodiments of this application.

[0026] In one possible design, when the first information includes multiple bits, for example, 24 bits, 26 bits, or 32 bits, the identity information of the second device occupies the lower bits of the multiple bits; the specific values ​​of other parameters in the first information occupy the higher bits of the multiple bits.

[0027] In one possible design, for the first parameter in the first information, the method of the first aspect may further include: if the start bit of the bit corresponding to the first parameter is not the least significant bit, then perform a shift calculation on the multiple bits included in the first information, shifting the start bit of the bit corresponding to the first parameter to the least significant bit; and obtaining the value of the first parameter based on the shifted information bits.

[0028] Based on this possible design, the first device can obtain the values ​​of the parameters in the first information.

[0029] Secondly, this application provides a communication method that can be executed by a second device, such as a second management node. The coverage area of ​​the second device includes multiple domains; the multiple domains correspond to multiple devices. Unless otherwise specified, the term "second device" in this application can refer to the second device itself, a component within the second device (e.g., a processor, radio frequency unit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the second device. The method includes: acquiring first information and sending the first information to a first device. The first information is used to determine a synchronization source device; the synchronization source device is used for multi-domain synchronization; the first information includes high-level and low-level domains of the second device; the second device is a device among the multiple devices corresponding to multiple domains; and the synchronization source device is used for multi-domain synchronization.

[0030] Based on the method described in the second aspect, the first device can obtain first information including the high and low level domains of the second device, so that the first device can determine the synchronization source device from the first device and the second device according to the feature of the low level domain device to the high level domain device in the Star Flash protocol. Compared with point-to-point protocols based on IEEE 802.11, such as the WDL protocol, selecting the synchronization source device reduces both the latency and complexity of determining the synchronization source device.

[0031] In one possible design, the first information may also include one or more of the following parameters:

[0032] The coverage area of ​​the second device, the multi-domain synchronization feature version of the second device, the power supply type of the second device, the clock source type of the second device, or the identity information of the second device; wherein, the multi-domain synchronization feature version is used to indicate the underlying protocol version supported by the device; the power supply type is used to indicate the type of current, including AC or battery; the clock source type is used to indicate the clock source providing the clock signal, including a local crystal oscillator or a GPS satellite navigation system; the identity information of the second device is used to uniquely identify the second device.

[0033] Based on this possible design, the first device receives one or more of the following: the high and low level domains of the second device, the coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, and the identity information of the second device.

[0034] In one possible design, the weights of the parameters in the first information are fixed, or the weights of the parameters in the first information are variable. Based on this possible design, the flexibility in selecting the weights of the parameters in the first information is improved.

[0035] In one possible design, the number of bits occupied by the specific values ​​of the parameters in the first information may be the same or different. Based on this possible design, the number of bits occupied by the specific values ​​of the parameters in the first information can be flexibly adjusted according to the specific communication scenario.

[0036] In one possible design, the identity information of the second device may include the identifier of the second device; or, the identity information of the second device may include the hash value of the identifier of the second device.

[0037] Based on this possible design, the identity information of the second device can include different information in different scenarios, which improves the flexibility of the embodiments of this application.

[0038] Thirdly, this application provides a communication device for transmitting starburst signals. This communication device can be applied to the first device mentioned in the first aspect, such as a first management node, to achieve the functions performed by the first device. The communication device can be the first device, or it can be a chip, chip system, or system-on-a-chip of the first device. The communication device can execute the functions performed by the first device through hardware or through corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, a module for receiving first information from a second device; a module for determining a synchronization source device based on the first information. The coverage area of ​​the first device includes multiple domains; multiple domains correspond to multiple devices; the first information includes high-level and low-level domains of the second device; the second device is a device among the multiple devices corresponding to multiple domains; the synchronization source device is used for multi-domain synchronization.

[0039] Fourthly, this application provides a communication device for transmitting starburst signals. This communication device can be applied to the second device described in the second aspect, such as a second management node, to achieve the functions performed by the second device. The communication device can be the second device itself, or it can be a chip, chip system, or system-on-a-chip (SoC) of the second device. The communication device can execute the functions performed by the second device through hardware or through corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, a module for acquiring first information; a module for sending first information to the first device. The coverage area of ​​the second device includes multiple domains; multiple domains correspond to multiple devices; the first information is used to determine the synchronization source device; the first information includes the high and low level domains of the second device; the synchronization source device is used for multi-domain synchronization.

[0040] In conjunction with the third or fourth aspect above, in one possible design the communication device further includes a Bluetooth module for realizing Bluetooth signal transmission and / or a Wi-Fi module for realizing Wi-Fi signal transmission. One or more of the StarScan module, Bluetooth module or Wi-Fi module share at least one of the following: radio frequency (RF) unit, modem unit, media access control (MAC) unit, and central processing unit (CPU).

[0041] In conjunction with the third or fourth aspect above, in one possible design, the StarSignal module and the Wi-Fi module for realizing Wi-Fi signal transmission are located in different subsystems of the communication device. The subsystem of the StarSignal module and the subsystem of the Wi-Fi module are integrated in the communication device with at least one of the following: Bluetooth system, StarSignal Low Power SLE system, Global Navigation Satellite System (GNSS), Always On system, Power Management Unit (PMU), Clock Management Unit (CMU), Flash memory, application system, and audio system.

[0042] In conjunction with the third or fourth aspect above, in one possible design, the StarSignal module and the Wi-Fi module for implementing Wi-Fi signal transmission are located in the same subsystem of the communication device. The subsystems of the StarSignal module and the Wi-Fi module are integrated in the communication device with at least one of the following: Bluetooth system, StarSignal Low Energy (SLE) system, Global Navigation Satellite System (GNSS), Always On system, Power Management Unit (PMU), Clock Management Unit (CMU), Flash memory, application system, and audio system.

[0043] In conjunction with the third or fourth aspect above, in one possible design, the communication device further includes a Bluetooth module for realizing Bluetooth signal transmission and / or a Wi-Fi module for realizing Wi-Fi signal transmission. At least one of the Bluetooth module or Wi-Fi module and the star flash module coexist and communicate with each other through different antennas. The coexistence strategy includes at least one of the following: frequency division multiplexing, code division multiplexing, time division multiplexing, channel avoidance, or aggregation scheduling.

[0044] In conjunction with the third or fourth aspect above, in one possible design, the communication device further includes a Bluetooth module for implementing Bluetooth signal transmission and / or a Wi-Fi module for implementing Wi-Fi signal transmission. At least one of the Bluetooth module or Wi-Fi module and the star flash module coexist and communicate with each other through the same antenna. The coexistence strategy includes at least one of the following: frequency division multiplexing, code division multiplexing, time division multiplexing, software static strategy, or message transmission arbitration PTA strategy.

[0045] Fifthly, embodiments of this application provide a communication device, which includes one or more processors; the one or more processors are configured to run computer programs or instructions, such that when the one or more processors execute the computer instructions or instructions, the communication method described in any one of the first to second aspects is performed.

[0046] In one possible design, the communication device further includes one or more memories coupled to one or more processors, the memories used to store the aforementioned computer programs or instructions. In one possible implementation, the memories are located outside the communication device. In another possible implementation, the memories are located inside the communication device. In embodiments of this application, the processor and memory may also be integrated into a single device, i.e., the processor and memory may be integrated together. In one possible implementation, the communication device further includes a transceiver for receiving and / or transmitting information.

[0047] In one possible design, the communication device further includes one or more communication interfaces coupled to one or more processors, and the communication interfaces are used to communicate with other modules outside the communication device.

[0048] In a sixth aspect, embodiments of this application provide a communication device, which includes an interface circuit and a logic circuit; the interface circuit is used to input and / or output information; the logic circuit is used to execute the communication method as described in any one of the first to second aspects, and to process and / or generate information based on the information.

[0049] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing computer instructions or programs that, when executed on a computer, cause the communication method described in any one of the first to second aspects to be performed.

[0050] Eighthly, embodiments of this application provide a computer program product containing computer instructions that, when run on a computer, causes the communication method described in any one of the first to second aspects to be executed.

[0051] Ninthly, embodiments of this application provide a computer program that, when run on a computer, causes the communication method described in any one of the first to second aspects to be executed.

[0052] In a tenth aspect, embodiments of this application provide a chip, including: a processor coupled to a memory, the memory being used to store programs or instructions, wherein when the program or instructions are executed by the processor, a communication method as described in any one of the first to second aspects is executed.

[0053] The technical effects of any of the design methods in aspects five through ten are similar to those in aspects one through two, and will not be elaborated upon further.

[0054] Eleventhly, embodiments of this application provide a communication system, which may include a communication device for performing the method as described in the first aspect or any possible design of the first aspect, and a communication device for performing the method as described in the second aspect or any possible design of the second aspect. Attached Figure Description

[0055] Figure 1 This application provides a schematic diagram of the architecture of a star-flash wireless communication system.

[0056] Figure 2 This application provides a schematic diagram of the architecture of a star-flash system.

[0057] Figure 3 This is a schematic diagram of the architecture of another star flash system provided in the embodiments of this application;

[0058] Figure 4 This application provides a schematic diagram of the architecture of a communication system.

[0059] Figure 5 A schematic diagram of the architecture of a StarScan basic access SLB communication system provided in this application embodiment;

[0060] Figure 6A flowchart illustrating a communication method provided in an embodiment of this application;

[0061] Figure 7 A flowchart illustrating a communication method provided in an embodiment of this application;

[0062] Figure 8 A schematic diagram of a chip architecture provided for an embodiment of this application;

[0063] Figure 9 A schematic diagram of another chip architecture provided in an embodiment of this application;

[0064] Figure 10 A schematic diagram of another chip architecture provided in an embodiment of this application;

[0065] Figure 11 A schematic diagram of another chip architecture provided in an embodiment of this application;

[0066] Figure 12 A schematic diagram of the framework of a chip module provided in an embodiment of this application;

[0067] Figure 13 A schematic diagram of the framework of another chip module provided in an embodiment of this application;

[0068] Figure 14 A schematic diagram illustrating the framework of a software static strategy provided in an embodiment of this application;

[0069] Figure 15 A schematic diagram illustrating the framework of yet another software static strategy provided in an embodiment of this application;

[0070] Figure 16 A schematic diagram illustrating the framework of a hardware arbitration time-division (PTA) strategy provided in an embodiment of this application;

[0071] Figure 17 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0072] Figure 18 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0073] Figure 19 This is a schematic diagram of the composition of a communication device provided in an embodiment of this application. Detailed Implementation

[0074] Before introducing the embodiments of this application, some technical terms involved in the embodiments of this application will be explained. It should be noted that the following explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by the embodiments of this application.

[0075] Sparklink wireless communication technology is a short-range wireless communication technology used to carry out data interaction in application scenarios such as smart cars, smart homes, smart terminals, and smart manufacturing. Figure 1 This is a schematic diagram of the architecture of the StarScan wireless communication system, as shown below. Figure 1 As shown, the StarScan wireless communication system consists of three parts: the StarScan access layer, the basic service layer, and the basic application layer. The basic service layer and the basic application layer constitute the upper layer of StarScan. The StarScan access layer, also known as the StarScan lower layer, is used to enable the transmission and interaction of upper-layer service data between the management node (grant node, abbreviated as G node) and the terminal node (terminal node, abbreviated as T node) over the air interface. The G node provides access layer services such as connection management, resource allocation, and information security to the T nodes under its coverage.

[0076] Considering the diverse transmission requirements of business scenarios for short-range wireless communication, the SparkLink access layer currently provides two communication interfaces for the upper layer: SparkLink Basic (SLB) and SparkLink Low Energy (SLE). SLB employs multiple technologies, including ultra-short frames, multi-point synchronization, two-way authentication, fast interference coordination, two-way authentication encryption, and cross-layer scheduling optimization, to support business scenarios with transmission requirements such as low latency, high reliability, precise synchronization, high concurrency, and high security. SLE uses Polar channel coding to improve transmission reliability, reduce retransmissions, and save power. It also supports a maximum transmission bandwidth of 4MHz, a maximum of 8PSK modulation, one-to-many reliable multicast, and 4kHz short-latency interaction. While maximizing transmission efficiency, it fully considers energy-saving factors to support business scenarios with low power consumption requirements. SLB and SLE provide different transmission services for different business needs, complementing each other and continuously and smoothly evolving according to business requirements.

[0077] In a StarScan system with multiple management nodes, where these nodes are deployed on adjacent channels, there is a problem of adjacent-channel interference between the management nodes. For example, Figure 2 This is a schematic diagram of the architecture of a starburst system, such as... Figure 2 As shown, the Starflash system includes management node 0, management node 1, and management node 2. Management node 0 provides access services to terminal nodes 01 and 02, management node 1 provides access services to terminal node 11, and management node 2 provides access services to terminal node 21. Management nodes 0, 1, and 2 operate asynchronously, meaning their clock signals are not synchronized, and they transmit signals / data through multiplexed channels.

[0078] However, since management node 0 operates at a frequency f0 of 5785MHz with a bandwidth of 20MHz, management node 1 operates at a frequency f1 of 5765MHz with a bandwidth of 20MHz, and management node 2 operates at a frequency f2 of 5805MHz with a bandwidth of 20MHz, meaning management nodes 0, 1, and 2 are deployed in adjacent frequency bands, out-of-band signal leakage occurs when any of the three management nodes transmits signals / data. This leads to a decrease in the signal-to-interference-plus-noise ratio (SNR) of the terminal nodes under the management nodes. Taking management node 1 as an example, if the leaked signal strength is too large, management node 1 may not be able to occupy the wireless channel, and may even be unable to transmit signals / data with terminal node 11. Even if the leaked signal strength allows management node 1 to successfully occupy the wireless channel and transmit signals / data with terminal node 11, the interference signal from management node 0 will greatly reduce the SNR of terminal node 11, causing a decrease in the quality of service (QoS) of terminal node 11. SNR refers to the ratio of the strength of the received useful signal to the strength of the received interference signal (noise and interference).

[0079] One possible implementation is to avoid or reduce the problem of adjacent-channel interference between multiple management nodes by synchronizing the time / frequency of each management node in the multi-management node (or multi-domain synchronization).

[0080] For example, Figure 3 This is a schematic diagram of the architecture of a starburst system, such as... Figure 3 As shown, the Starflash system is deployed in a vehicle and includes management node 1, management node 2, terminal node 11, and terminal node 21. Management node 1 provides access services to terminal node 11, and management node 2 provides access services to terminal node 21. Using the two-dimensional location point of management node 1 as the reference origin, the two-dimensional location point of management node 2 is (-2.0, 1.0), the two-dimensional location point of terminal node 11 is (1.5, 1.0), and the two-dimensional location point of terminal node 21 is (0.5, -0.1). Furthermore, management node 1 operates at a frequency of 5785MHz with a bandwidth of 20MHz, and management node 2 operates at a frequency of 5805MHz with a bandwidth of 20MHz. The domain of management node 1 is domain 1, and the domain of management node 2 is domain 2. It is assumed that the maximum error vector magnitude (EVM) of the management nodes is 35dB.

[0081] One possible implementation is that management node 1 and management node 2 work asynchronously, that is, the time / frequency of management node 1 and management node 2 are not synchronized (or domain 1 and domain 2 are not synchronized), and the SNR1 of management node 1 and the SNR2 of management node 2 satisfy:

[0082]

[0083] Another possible implementation is that management node 1 and management node 2 work synchronously, that is, management node 1 and management node 2 are synchronized in time / frequency (or domain 1 and domain 2 are synchronized). In this case, the adjacent channel leakage energy is very small or even negligible, and the SNR1 of management node 1 and the SNR2 of management node 2 satisfy:

[0084]

[0085] As shown above, the SNR under synchronized domain 1 and domain 2 is significantly improved compared to the SNR under unsynchronized domain 1 and domain 2. Therefore, multi-domain synchronization can indeed effectively avoid or reduce adjacent channel interference.

[0086] To address the adjacent-channel interference issue through multi-domain synchronization, a management node needs to be selected from multiple management nodes. This management node can be called a synchronization source device. Other management nodes can synchronize their time / frequency with this synchronization source device to achieve time / frequency synchronization (or multi-domain synchronization) among the management nodes. Therefore, selecting a synchronization source device from multiple management nodes is the primary problem to be solved in achieving multi-domain synchronization.

[0087] In this application, the synchronization source device can be used to achieve multi-domain synchronization. For a description of the synchronization source device, please refer to S603.

[0088] In one example, a synchronization source device can be selected based on a dedicated IEEE 802.11-based point-to-point protocol, such as the Wireless Direct Link (WDL) protocol. Specifically, taking devices A and B as examples, both devices A and B support the WDL protocol. Device A continuously listens for synchronization frames sent by device B in the WDL protocol. It processes the transmission range and power level of the devices included in the synchronization frame to obtain a "synchronization source preference value" for device B. Device A compares its own "synchronization source preference value" with that of device B. If device A's "synchronization source preference value" is greater than device B's, device A selects itself as the synchronization source device, and device B initiates multi-domain synchronization with device A. If device A's "synchronization source preference value" is less than device B's, device A selects device B as the synchronization source device, and device A initiates multi-domain synchronization with device B. This maintains network efficiency and stability, ensuring a fair and transparent master device selection process.

[0089] The above method of selecting a synchronization source device based on the WDL protocol does not fully consider the characteristics of short-range wireless communication technology. For example, in the StarSpark protocol, devices in the lower-level domain initiate multi-domain synchronization domains to devices in the higher-level domain. That is, the time / frequency of the devices in the lower-level domain is aligned with the time / frequency of the devices in the higher-level domain. This makes the synchronization source device selected according to the WDL protocol in the StarSpark system not optimal.

[0090] In this application, a domain can also be referred to as a communication domain. A communication domain refers to the resources of the G-link and T-link of a management node in a communication system. A communication domain can also be referred to as a cell. Whether a device's domain is a high-level domain or a low-level domain is configured when the device leaves the factory.

[0091] In one example, according to the WDL protocol described above, if the "synchronization source preference value" of device A is determined to be greater than that of device B, and regardless of the high or low level domains of the devices, device A is selected as the synchronization source device, causing device B to initiate multi-domain synchronization to device A. However, if the domain of device A is a low-level domain and the domain of device B is a high-level domain, even if device A is selected according to the WDL protocol, its multi-domain synchronization capability is lower than that of device B, and multi-domain synchronization may not be achieved through device A. Therefore, the synchronization source device selected based on the WDL protocol is not optimal.

[0092] To select a suitable / optimal synchronization source device from multiple management nodes, this application provides a communication method. This method can be used to select a synchronization source device from multiple devices within the coverage area of ​​multiple domains. Taking multiple devices including a second device and a first device as an example, the method can include: the second device acquiring first information including the high and low domains of the second device and sending the first information to the first device; the first device receiving the first information from the second device and determining the synchronization source device for multi-domain synchronization based on the first information.

[0093] In this way, the first device can determine the synchronization source device from the first device and the second device based on the feature of the low-level domain device to initiate multi-domain synchronization domain to the high-level domain device in the Star Flash protocol. Compared with selecting the synchronization source device according to the WDL protocol, this reduces both the latency and complexity of determining the synchronization source device.

[0094] The communication method provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0095] The communication method provided in this application embodiment can be used in any communication system, such as a third-generation partnership project (3GPP) communication system, for example, a long-term evolution (LTE) system; or a fifth-generation (5G) mobile communication system, a hybrid LTE and 5G network system, a new radio (NR) system, a vehicle-to-everything (V2X) system, a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an internet of things (IoT) system, a narrow band internet of things (NB-IoT) system, enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), or enhanced machine-type communication. Communication (eMTC) and various types of future communication systems, including non-terrestrial network (NTN) systems (such as satellite communication systems), non-3GPP communication systems, etc., are not restricted.

[0096] The technical solutions of this application can be applied to, but are not limited to, short-range wireless communication systems and wireless communication systems that support longer-distance transmission (such as 1-18km, or over 18km) (such as the next-generation StarSpark wireless communication system). The short-range wireless communication system can include short-range wireless communication technology (also known as StarSpark 1.0 technology), which has advantages such as ultra-low latency, ultra-high reliability, and precise synchronization, making it suitable for applications in smart cars, smart homes, smart terminals, and smart manufacturing. For example, applications in smart car scenarios include: immersive in-vehicle sound field & noise reduction, wireless interactive projection, and 360-degree panoramic surround view, which can achieve an immersive interactive experience and improve vehicle safety.

[0097] Wireless communication systems that support longer transmission distances (e.g., 1–18 km) mainly include next-generation StarSpark wireless communication systems, such as StarSpark 2.0 and StarSpark 3.0. These systems are not only suitable for communication scenarios with low latency requirements, such as the aforementioned vehicle communication and industrial control scenarios, but also for communication scenarios with less stringent latency requirements.

[0098] In some possible implementations, the aforementioned communication system may be used in conjunction with mobile communication systems, such as, but not limited to, fourth-generation (4G) communication systems (e.g., Long Term Evolution (LTE) systems), fifth-generation (5G) communication systems (e.g., New Radio (NR) systems), and future mobile communication systems.

[0099] Figure 4 A schematic diagram of a communication system architecture provided in this application embodiment, such as... Figure 4 As shown, the communication system may include a first device and a second device. Figure 4 The coverage area of ​​the first device includes multiple domains, such as the domain of the first device and the domain of the second device; multiple domains correspond to multiple devices, such as the domain of the first device corresponding to the first device, and the domain of the second device corresponding to the second device; Figure 4 The second device can be any device other than the first device in multiple domains. For example, in a StarSpark system that includes multiple management nodes, the first device and the second device can be different management nodes among the multiple management nodes.

[0100] Figure 4 For example, consider a scenario where the coverage areas of the first device and the second device partially overlap. Optionally, Figure 4 The coverage area of ​​the first device may include the coverage area of ​​the second device, or, Figure 4 The coverage area of ​​the second device may include the coverage area of ​​the first device.

[0101] One possible implementation, Figure 4 The first and / or second devices in the system support the SLB communication system. Figure 5 This is a schematic diagram of the architecture of an SLB communication system provided in an embodiment of this application, as shown below. Figure 5 As shown, the communication system may include an application layer, a network and transport layer, and an access layer.

[0102] The application layer provides various business interfaces to support multiple business applications.

[0103] The network layer is responsible for routing, addressing, and networking.

[0104] The access layer can include the physical layer, media access layer, and link control layer. Furthermore, the media access layer and link control layer can form the data link layer. At the transmitting end, the media access layer, based on single-carrier or multi-carrier scheduled radio resources, multiplexes and encapsulates data from different logical channels to generate media access control layer protocol data units (MAC PDUs), and then passes these MAC PDUs down to the scheduled carriers for data transmission. The link control layer performs necessary numbering, segmentation, encryption, and integrity protection operations on the upper-layer service data (basic service layer data), and sends the generated link control layer protocol data units (LC PDUs) to the media access layer. The physical layer is responsible for handling signal transmission and reception and is the lowest layer of the communication system.

[0105] One possible implementation, Figure 4 The first and / or second device in the system can be a management node (G node for short range). A G node can be a node in a short-range wireless communication system that has resource scheduling functions and sends control information such as resource management information and / or data scheduling information.

[0106] For example, the management node (G node) is located on the network side of the aforementioned communication system, used to help terminal nodes achieve wireless access, and is a device with wireless transceiver capabilities or a chip or chip system that can be set in the device. This management node includes, but is not limited to: network devices, access network devices, access network nodes, radio access network (RAN) nodes, RAN entities or access nodes, base stations, evolved NodeBs (eNodeBs), access points (APs), transmission reception points (TRPs or transmission points (TPs), next-generation NodeBs (gNBs), next-generation base stations in future mobile communication systems, base stations in future mobile communication systems, or access points (APs) in wireless fidelity (Wi-Fi) systems. The management node can be a macro base station, micro base station or indoor station, relay node or donor node, an open radio access network (ORAN), or a wireless controller in a centralized radio access network (CRAN) scenario. The management node can also be one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or it can be a network node constituting a gNB, TRP, TP, or transmission measurement function (TMF), such as a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), a radio unit (RU), or a roadside unit (RSU) with base station functionality. Optionally, the management node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the management node in vehicle-to-everything (V2X) technology can be an RSU. Optionally, the management node can also be a control unit in autonomous driving, a central controller in a smart factory / smart home, or a handheld or automatic control remote sensor for flight equipment. Optionally, the management node can also be a control device such as a central control or control panel, such as a drone controller or a control unit in industrial control.All or part of the functions of the management node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The management node in this application can also be a logical node, logical module, or software capable of implementing all or part of the management node functions.

[0107] In this application embodiment, the form of the management node is not limited. The device used to implement the function of the management node can be the management node itself; it can also be a device that supports the management node in implementing this function, such as a chip system. The device can be installed in the management node or used in conjunction with the management node.

[0108] Optional, Figure 4 The communication system shown may also include a third device ( Figure 4 (not shown in the image) Figure 4 The first and / or second devices provide access layer services such as connection management, resource allocation, and information security to the third device.

[0109] One possible implementation, Figure 4 The third device can be a terminal node (T node). A T node is a node in a short-range wireless communication system that receives control information such as resource management information and / or data scheduling information sent by a G node, and performs data transmission or reception based on this control information. For ease of description, the short-range protocol in this disclosure is referred to as the Starflash protocol.

[0110] For example, a terminal node (T node) is a device, equipment, module, chip, or chip system with transceiver functions. The terminal node may also be referred to as terminal equipment, user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminal nodes in the embodiments of this application can be mobile phones, cellular phones, smartphones, tablets, mice, remote controls, styluses, set-top boxes, routers, cameras, screens, smart screens, wireless data cards, personal digital assistant computers (PDAs), wireless modems, handsets, laptop computers, smartwatches, smart bracelets, wireless headphones, electronic whiteboards, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, washing machines, rice cookers, table lamps, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, and transportation security. Wireless terminals in various applications include those related to safety, smart cities, smart homes, in-vehicle terminals, in-vehicle screens, in-vehicle audio systems, car keys, roadside units (RSUs) with terminal functions, and flying equipment (e.g., intelligent robots, hot air balloons, drones, airplanes). The terminal node in this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit integrated into a vehicle as one or more components or units. The terminal node can also be other devices with terminal functions; for example, it can be a device that performs terminal functions in device-to-device (D2D) communication.

[0111] The embodiments of this application do not limit the device form of the terminal. The device used to implement the function of the terminal node can be the terminal node itself; it can also be a device that supports the terminal node in implementing the function, such as a chip system. The device can be installed in the terminal node or used in conjunction with the terminal node. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0112] In the StarScan protocol corresponding to StarScan technology, there are uplink and downlink transmissions between the aforementioned G node and T node. Uplink transmission is achieved through the T link, which is the link between the T node and the G node, and can also be called the uplink. Downlink transmission is achieved through the G link, which is the link between the G node and the T node, and can also be called the downlink.

[0113] In this embodiment, the communication device has wireless communication capabilities and can be configured with multiple antennas. These multiple antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals. Additionally, each communication device also includes a transmitter chain and a receiver chain. Those skilled in the art will understand that these chains may include multiple components related to signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, or antennas). The communication device can be a network device or a terminal device, and there is no limitation thereto.

[0114] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0115] It should be noted that the system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0116] The following is combined Figure 4 The communication system shown is illustrated using the interaction between communication devices as an example to describe the communication method provided in the embodiments of this application. It should be noted that in the following embodiments of this application, the message names, parameter names, or information names between communication devices are merely examples, and may be other names in other embodiments. The method provided in this application does not specifically limit these names.

[0117] It is understood that in the embodiments of this application, each communication device may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessary to execute all the operations in the embodiments of this application.

[0118] It is understood that this application uses a communication device as an example to illustrate the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the communication device in this application can also be executed by a module (e.g., a chip, chip system, or processor) applied to the communication device, or it can be implemented by a logic node, logic module, or software that can implement all or part of the functions of the communication device.

[0119] The communication method provided in the embodiments of this application will be described below. Figure 6 As shown, the method may include the following steps:

[0120] S601: The second device acquires the first information.

[0121] The coverage area of ​​the second device includes multiple domains, and each domain corresponds to multiple devices. These multiple devices may include the first device, the second device, and other devices such as a third device, a fourth device, etc. Any of these multiple devices can perform the actions performed by the second device in this application, such as acquiring and sending first information, and performing the actions performed by the first device, such as the first device receiving the first information and determining the synchronization source device based on the first information. This application uses the first and second devices as examples for description; the actions performed by other devices can be referred to the actions performed by the first and second devices and will not be elaborated further.

[0122] Optional, with Figure 6 The method shown is applied to Figure 4 Taking the system shown as an example, the second device is... Figure 4 The second device in the communication system shown has a coverage area that includes the domain of the first device and the domain of the second device.

[0123] The first information may include parameters of the second device used to indicate the synchronization capability of the second device, such as high-level and low-level fields of the second device. The high-level and low-level fields of the second device may indicate that the field of the second device is a high-level field, or the high-level and low-level fields of the second device may indicate that the field of the second device is a low-level field.

[0124] In this application, the parameters used to indicate the synchronization capability of a device may be referred to as device synchronization capability parameters or device parameters, without limitation. For ease of description, this application uses device parameters as parameters used to indicate the synchronization capability of a device. Optionally, in addition to including the high and low level domains of the device, the device parameters may also include at least one of the following: the coverage area of ​​the device, the version of the multi-domain synchronization feature of the device, the power supply type of the device, the clock source type of the device, or the identification information of the device. For example, taking the device as a second device, the parameters of the second device may also include one or more of the following parameters: the coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, or the identification information of the second device. These parameters may also be included in the first information.

[0125] Optionally, the parameters of the second device can be obtained based on the configuration information of the second device. For example, the coverage area of ​​the second device can be determined based on the transmission power of the second device, the power supply type of the second device can be obtained from the power supply configuration of the second device, the clock source type of the second device can be obtained from the clock configuration of the second device, and the identity information of the second device can be obtained from the identity configuration of the second device. In this application, the parameters of the second device being included in the first information can be understood as the specific values ​​of the parameters of the second device being included in the first information. For example, the specific values ​​of the parameters of the second device can be converted into binary bits, and the converted binary bits are carried in the first information. Optionally, the first information includes one or more bits. For example, the first information may include one bit, which can be used to indicate the high-level and low-level fields of the second device. For example, when the value of the bit is 1, it indicates the high-level field, and when the value of the bit is 0, it indicates the low-level field, or when the value of the bit is 0, it indicates the high-level field, and when the value of the bit is 1, it indicates the low-level field. Or, the first information may include 24, 26, or 32 bits, etc., which are bits obtained after binary conversion of the values ​​of multiple types of parameters of multiple second devices.

[0126] In this application, when the first information includes multiple types of parameters of the second device, the bit position or field occupied by the binary bits corresponding to the specific values ​​of the parameters of the second device in the first information is not limited. In other words, it is not limited to which position the multiple types of parameters of the second device are specifically included in the first information. Furthermore, the number of bits occupied by the specific values ​​of the parameters in the first information can be the same or different.

[0127] For example, the parameters of the second device include the high and low level fields of the second device, the identity information of the second device, and one or more other parameters. The first information includes multiple bits, with the identity information of the second device occupying the low bits of the multiple bits; the specific values ​​of the other parameters in the first information, excluding the identity information, occupy the high bits of the multiple bits. Alternatively, the identity information of the second device occupies the high bits of the multiple bits; the specific values ​​of the other parameters in the first information, excluding the identity information, occupy the low bits of the multiple bits, without restriction.

[0128] For example, the first information may include 10 bits, and the parameters in the first information include: the high and low level domains of the second device, the coverage range of the second device, the multi-domain synchronization feature version of the second device, the power supply type of the second device, and the clock source type of the second device; wherein, the specific value of any parameter in the first information occupies the same number of bits, which is 2 bits.

[0129] For example, the first information may include 26 bits. The parameters in the first information include five categories of parameters: the high and low level domains of the second device, the coverage area of ​​the second device, the multi-domain synchronization feature version of the second device, the power supply type of the second device, and the clock source type of the second device. It also includes the identity information of the second device. Among them, the specific value of the identity information of the second device occupies 16 bits, and the specific values ​​of the other five categories of parameters occupy 2 bits. Alternatively, the specific value of the identity information of the second device occupies 16 bits, the power supply type of the second device, the clock source type of the second device, and the specific values ​​in the high and low level domains of the second device each occupy 1 bit; the specific values ​​of the coverage area of ​​the second device and the multi-domain synchronization feature version of the second device each occupy 2 bits. For example, taking the parameters of the second device occupying fields in the first information as an example, suppose the first information includes the high and low level domains of the second device, the coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, and the identity information of the second device. The first information includes six fields, and each parameter of the second device occupies one field. In one example, the high and low level domains of the second device, the coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, and the identity information of the second device occupy the first to sixth fields of the first information in sequence. Or, in another example, the coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, the high and low level domains of the second device, and the identity information of the second device occupy the first to sixth fields of the first information in sequence.

[0130] In this application, the high-level and low-level domains of a device include either a high-level domain or a low-level domain. For example, the domains of a device may be configured when the device leaves the factory, or they may be updated after the device leaves the factory. For example, in a vehicle communication system, the high-level domain may refer to devices related to vehicle control, while the low-level domain may refer to devices related to the entertainment system.

[0131] In this application, there are no restrictions on the method of indicating the coverage range of the device. For example, the coverage range of the device can be indicated directly or indirectly. For instance, in the case of directly indicating the coverage range, the coverage range is a specific value of the device's coverage range. Alternatively, in the case of indirectly indicating the coverage range, the coverage range is the device's current operating frequency band; the lower the operating frequency band, the larger the coverage range. Or, in the case of indirectly indicating the coverage range, the coverage range is the device's transmission power; the higher the transmission power, the larger the coverage range.

[0132] In this application, the multi-domain synchronization feature version of the device is used to indicate the underlying protocol version supported by the device, such as the StarSignal SLB access technology protocol version. The StarSignal SLB access technology protocol version can include StarSignal Basic Access Technology SLB Protocol 1.0 or future versions of the StarSignal Basic Access Technology SLB Protocol. Future versions of the StarSignal Basic Access Technology SLB Protocol refer to StarSignal Basic Access Technology SLB Protocol versions after StarSignal Basic Access Technology SLB Protocol 1.0, such as StarSignal Basic Access Technology SLB Protocol 2.0, StarSignal Basic Access Technology SLB Protocol 1.0 Enhanced Version, etc.

[0133] In this application, the power supply type of the device is used to indicate the type of current, which includes AC or battery.

[0134] In this application, the clock source type of the device is used to indicate the clock source that provides the clock signal, and the clock source includes a local crystal oscillator or a global positioning system (GPS).

[0135] In this application, the device's identity information is used to uniquely identify the device. Optionally, the device's identity information may include the device's identifier, or it may include a hash value of the device's identifier. One possible implementation is that the device's identifier is the device's data link layer identifier. The hash value of the device's identifier is a fixed-length data value corresponding to the device's identifier. For example, the device supports... Figure 5In the case of the SLB communication system shown, the device identifier is the Layer 2 ID of the data link layer in the device's SLB communication system, which is used to uniquely identify the device. The specific value of this identifier occupies 48 bits. Assuming that the fixed length of the hash value is 16 bits, the hash value of the device identifier is the 16-bit data corresponding to the data link layer ID of the device's SLB communication system.

[0136] This application does not restrict the method for obtaining the hash value of the device identifier. For example, the hash value of the device identifier can be obtained by performing a modulo operation on the device identifier. Alternatively, a typical hash algorithm can be used to process the device identifier to obtain the hash value of the device identifier.

[0137] S602: The second device sends first information to the first device, and the first device receives the first information from the second device.

[0138] The second device can periodically or triggerively send the first information to the first device. For example, the second device can periodically send the first information to the first device in a broadcast manner; or, the second device can send the first information to the first device after receiving a request instruction to send the first information.

[0139] S603: The first device determines the synchronization source device based on the first information.

[0140] In this context, the synchronization source device refers to one of multiple devices corresponding to multiple domains, to which other devices synchronize their time / frequency. The synchronization source device in this application may also have other names, such as master device or master synchronization device; however, this application does not specifically limit its name.

[0141] In one example, the first information includes the high and low level fields of the second device, and the first device determining the synchronization source device based on the first information may include: the first device determining the synchronization source device based on the high and low level fields of the second device and the high and low level fields of the second device.

[0142] Specifically, if the high-low level field of the first device indicates that the domain of the first device is a high-level domain, and the high-low level field of the second device in the first information indicates that the domain of the second device is a low-level domain, then the first device is determined to be the synchronization source device. If the high-low level field of the first device indicates that the domain of the first device is a low-level domain, and the high-low level field of the second device in the first information indicates that the domain of the second device is a high-level domain, then the second device is determined to be the synchronization source device. Optionally, if the domains of the first device and the domains of the second device have the same level, then the first device can determine the synchronization source device based on the parameters in the first information excluding the high-low level field of the second device.

[0143] In another example, the first information includes the high and low level domains of the second device, and may also include other parameters, such as the coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, and at least one of the identity information of the second device. The first device determines the synchronization source device based on the first information, which may include either of the following two methods:

[0144] Method 1: The first device determines the synchronization source device based on the parameters with higher priority in the first information.

[0145] Specifically, the first device can acquire a high-priority parameter (which can be called the first parameter), and determine the synchronization source device based on this high-priority parameter of the first device and the high-priority parameter of the second device. For example, if the value of the first parameter of the second device is greater than the value of the first parameter of the first device, the second device is used as the synchronization source device; if the value of the first parameter of the second device is less than the value of the first parameter of the first device, the first device is used as the synchronization source device.

[0146] It should be understood that if the values ​​of the higher-priority parameter of the first device and the second device are the same, then the second-highest priority parameter is obtained, and the synchronization source device is determined based on the second-highest priority parameter of the first device and the second-highest priority parameter of the second device. If the values ​​of the second-highest priority parameter are also the same, then the next-lower priority parameter is obtained, and the synchronization source parameter is determined based on the next-lower priority parameter of the first device and the second device.

[0147] In this application, the priority of device parameters can be set as needed, either through negotiation among multiple devices or predefined by a protocol, without restriction. For example, the priority of device parameters from high to low can be ordered as follows: device high-low domain > device clock source type > coverage area of ​​the second device > version of the multi-domain synchronization feature of the second device > power supply type of the second device > identity information of the second device.

[0148] For example, the priority of device parameters, from high to low, is as follows: device high-low domain > second device clock source type > second device coverage > second device identity information > second device multi-domain synchronization feature version > second device power supply type.

[0149] For example, prioritizing the device's high / low level domains > device's clock source type > second device's coverage area > second device's multi-domain synchronization feature version > second device's power supply type > second device's identity information, we can first obtain the values ​​of the second device's high / low level domains, compare them with the high / low level domains of the first and second devices. If the high / low level domain value is the first value, the device's domain is a high-level domain; if the high / low level domain value is the second value, the device's domain is a low-level domain. The first value is greater than the second value. If the high / low level domain value of the second device in the first information is... If the value is equal to the value of the high-low priority field of the first device, then compare the value of the clock source type of the second device in the first information with the value of the clock source type of the first device; if the value of the clock source type of the second device in the first information is equal to the value of the clock source type of the first device, then compare the value of the coverage area of ​​the second device in the first information with the value of the coverage area of ​​the first device; and so on, until the value of the lower priority parameter in the first information is different from the value of the lower priority parameter of the first device, then the device with the larger value of the lower priority parameter in the first device and the second device is taken as the synchronization source device.

[0150] It should be understood that when the high-low level field of a device is the highest priority, the way the first device determines the synchronization source device based on the high-low level field of the second device and the high-low level field of the second device is the same as the way the synchronization source device is determined in the example above where the first information only includes the high-low level field of the second device, and will not be described again.

[0151] Method 2: The first device determines the synchronization source device based on the weights of the parameters in the first information.

[0152] Specifically, the first device can determine the first value of the second device by weighting the parameters of the second device according to the weights of the parameters in the first information, and determine the first value of the first device by weighting the parameters of the first device; if the first value of the second device is greater than the first value of the first device, the second device is used as the synchronization source device; if the first value of the second device is less than the first value of the first device, the first device is used as the synchronization source device.

[0153] In this context, the parameters used by the first device to calculate the first value are of the same type as the parameters used by the second device to calculate the second value, and the weights of the same type of parameters in the first and second devices are the same. In other words, the calculation method / formula used to calculate the first value of the first device and the second value of the second device are the same, but the specific values ​​of the parameters in the calculation method / formula are different depending on the device.

[0154] Optionally, taking the equipment parameters including the six parameters P1-P6 as an example, the calculation method / formula is as follows: Formula (1):

[0155] The first value of the device = w1*P1 + w2*P2 + w3*P3 + w4*P4 + w5*P5 + P6 (Formula 1)

[0156] In the formula, Pi is the value of the i-th parameter, w1 is the weight of parameter P1, w2 is the weight of parameter P2, w3 is the weight of parameter P3, w4 is the weight of parameter P4, and w5 is the weight of parameter P5. Optionally, taking the second device as an example, and the second device includes the six parameters P1-P6, the value of the i-th parameter can be obtained by parsing the bits included in the first information. Specifically, the bits occupied by the i-th parameter can be shifted so that the starting bit of the bit corresponding to the i-th parameter is the least significant bit. The shifted bit value is converted to decimal to obtain the value of the i-th parameter. The value of each of the six parameters is obtained in this way. The six values ​​obtained are substituted into formula (1) to obtain the first value of the device.

[0157] For example, taking the first information as including the six parameters P1-P6 of the second device, which include the device's identity information (the hash value of the device's identifier), the hash value of the device's identifier occupies the lower 16 bits of the first information, and the remaining five parameters occupy the upper 10 bits, with each parameter occupying two bits, then for the i-th parameter among the five parameters, the specific value of the i-th parameter can be obtained by right shifting it by 16 + 2*(5-i) bits. Specifically, the first value of the second device can be obtained by referring to the following formula (2):

[0158] The first value of the device = (P1>>24)+(P2>>22)+(P3>>20)+(P4>>18)+(P5>>16)+P6 Formula (2)

[0159] As can be seen from the above formula (2), each parameter is shifted to obtain the number of binary bits for each parameter. The number of binary bits for each parameter is then converted into a decimal integer to obtain the value of each parameter.

[0160] Alternatively, the parameters not in the low-order bits can be converted to decimal to obtain their initial values. The initial values ​​of each parameter are then weighted and rounded to obtain a weighted value. This weighted value is then converted to binary bits and shifted. The shifted binary bits are then converted to decimal integers to obtain the sum of the values ​​of the parameters not in the low-order bits. Finally, the sum of the values ​​of the parameters not in the low-order bits is added to the values ​​of the parameters in the low-order bits to obtain the first value of the device.

[0161] For example, taking the first information as including the six parameters P1-P6 of the second device, which include the device's identity information, the device's identity information is the hash value of the device's identifier, the hash value of the device's identifier occupies the lower 16 bits of the first information, and the remaining five parameters occupy the upper 10 bits in sequence, with each parameter occupying two bits, then for the i-th parameter among the five parameters, a decimal conversion can be performed to obtain the initial value corresponding to the i-th parameter. The initial values ​​of each of the five parameters are weighted and rounded to obtain a weighted value. This weighted value is converted into binary bits and shifted right by 16 bits. The shifted binary bits are converted into decimal integers to obtain the sum of the values ​​of parameters P1-P5. This sum is added to P6 to obtain the first value of the second device. Specifically, the first value of the second device can be obtained by referring to the following formula (3):

[0162] The first value of the device = [w1*P1+w2*P2+w3*P3+w4*P4+w5*P5]>>16+P6 Formula (3)

[0163] As can be seen from the above formula (3), the initial values ​​of each parameter in parameters P1-P5 are weighted and then shifted to obtain the sum of the values ​​of parameters P1-P5. This sum is then added to P6 to obtain the first value of the device.

[0164] The weights of the parameters in the first information can be fixed; or the weights of the parameters in the first information can be variable.

[0165] For example, when the weights of the parameters in the first information are fixed, these weights can be predefined by the protocol; when the weights of the parameters in the first information are variable, they can be determined based on the specific communication scenario. For instance, in a StarFlash system, the high-low domain of the second device has the highest weight in the first information, while the weights of other parameters in the first information are less than the weights of the high-low domain of the second device, and the weights of the other parameters in the first information are greater than 0. Alternatively, in a Wi-Fi system, the weights of all parameters in the first information are the same, i.e., the weight of each parameter in the first information is 0.6.

[0166] Optionally, if the weights of the parameters in the first information are variable, the second device can send the weights of the parameters in the first information to the first device so that the first device can determine the synchronization source device based on the first information.

[0167] For example, the first information includes the high and low level domains of the second device and the clock source type of the second device. The weight of the high and low level domains of the second device is weight 1, and the weight of the clock source type of the second device is weight 2. The first device can calculate the first value of the second device by weighting the specific values ​​of the high and low level domains of the second device and the specific values ​​of the clock source type of the second device according to weight 1 and weight 2. Furthermore, the first device can calculate the first value of the first device by weighting the specific values ​​of the high and low level domains of the first device and the specific values ​​of the clock source type of the first device according to weight 1 and weight 2.

[0168] Furthermore, this application does not limit the way in which the first device obtains the values ​​of the parameters in the first information; specific implementations are described below.

[0169] In one possible implementation, for the first parameter in the first information, if the starting bit of the binary bits corresponding to the first parameter is the least significant bit, then the binary bits corresponding to the first parameter are converted into a decimal integer to obtain the value of the first parameter. For example, if the binary bits corresponding to the first parameter in the first information are 10, and the binary bits corresponding to the first parameter 10 are distributed starting from the least significant bit, that is, 0 is located in the least significant bit and 1 is located in the most significant bit, then the binary bits corresponding to the first parameter 10 are converted into a decimal integer 2, and the value of the first parameter is 2.

[0170] In another possible implementation, for the first parameter in the first information, if the starting bit of the binary bit corresponding to the first parameter is not the least significant bit, then the shift calculation is performed on the multiple binary bits included in the first information, and the starting bit of the binary bit corresponding to the first parameter is shifted to the least significant bit; further, the value of the first parameter is obtained based on the shifted information bits.

[0171] Furthermore, this application does not limit the method by which the first device obtains the weights of the parameters in the first information. For example, the first device may periodically or trigger the acquisition of the weights of the parameters in the first information. For example, the second device may periodically broadcast the weights of the parameters in the first information, or the first device may send a request message to the second device to request the weights of the parameters in the first information, and the second device, in response to the request message, sends the weights of the parameters in the first information to the first device.

[0172] based on Figure 6The method shown includes multiple domains within the coverage area of ​​the first device, with each domain corresponding to multiple devices. The first device can determine whether it can be a synchronization source device based on the high / low level domains of the second device in the first information. The second device is one of the multiple devices corresponding to the aforementioned multiple domains. For example, the high / low level domains of the second device in the first information indicate that the second device's domain is a low-level domain. If the first device's domain is a high-level domain, then the first device can determine that it can be a synchronization source device. In this way, the first device can combine the feature of the StarSpark protocol—where devices in low-level domains initiate multi-domain synchronization to devices in high-level domains—with the determination of the synchronization source device to identify the synchronization source device from the first device and the second device. Compared to the first device selecting the synchronization source device based on the WDL protocol, this method reduces both the latency and complexity of determining the synchronization source device.

[0173] Optionally, in scenarios where multi-domain synchronization is disabled, the aforementioned devices may not need to synchronize with other devices, such as when the multi-domain synchronization feature is turned off. Therefore, in scenarios where multi-domain synchronization is enabled, the aforementioned devices need to enable their multi-domain synchronization feature to determine the synchronization source device and achieve time / frequency synchronization with the synchronization source device.

[0174] The following is based on Figure 4 In the communication system shown, taking the first device as the first management node and the second device as the second management node as an example, the coverage area of ​​the first management node includes the domain of the first management node and the domain of the second management node. The domain of the first management node corresponds to the first management node, and the domain of the second management node corresponds to the second management node. The following will combine... Figure 7 right Figure 6 The communication method shown will be introduced.

[0175] The communication method provided in the embodiments of this application will be described below. Figure 7 As shown, the method may include the following steps:

[0176] S701: The first management node triggers a scan of the synchronization source device.

[0177] The synchronization source device can be found in the above description, and will not be repeated here.

[0178] The scanning methods for the synchronization source device triggered by the first management node may include: the first management node triggering the scanning of the synchronization source device when its system is powered on, or the first management node triggering the scanning of the synchronization source when the synchronization source device is lost.

[0179] S702: The first management node performs the discovery of the synchronization source device.

[0180] The discovery of synchronization source devices by the first management node may include: after the first management node triggers the scanning of synchronization source devices, it scans multiple frequency points to discover the domains of the first management node and the second management node within the coverage area of ​​the first management node, and triggers the second management node to send first information to the first management node.

[0181] S703: In response to the discovery of the synchronization source device, the second management node obtains the first information.

[0182] The second management node is Figure 6 The method shown is an example of a second device, so the relevant description of the second management node obtaining the first information can be found in S601, and will not be repeated here.

[0183] S704: The second management node sends the first information to the first management node, and the first management node receives the first information from the second management node.

[0184] The first management node is Figure 6 In the method shown, the first device is an example, and the second management node is... Figure 6 This is an example of a second device in the method shown, therefore the relevant description of S704 can be found in S602, and will not be repeated here.

[0185] In one possible scenario, after the second management node obtains the first information, it broadcasts the first information to the first management node. Correspondingly, the first management node can receive the first information from the second management node through the broadcast information.

[0186] S705: The first management node determines the synchronization source device based on the first information.

[0187] For a detailed description of S705, please refer to S603, which will not be repeated here.

[0188] S706: The first management node synchronizes time / frequency with the second management node.

[0189] S706 is an optional execution step. If the synchronization source device determined by the first management node in S705 is the second management node, step S706 is executed to achieve time / frequency synchronization (or multi-domain synchronization) between the first management node and the synchronization source device.

[0190] Understandably, after the time / frequency of the first management node is synchronized with the time / frequency of the second management node, it is still necessary to periodically or non-periodically check whether the first management node is still synchronized with the second management node to ensure that the first management node can maintain a multi-domain synchronized state with the second management node.

[0191] Optionally, after the time / frequency of the first management node is synchronized with the time / frequency of the second management node, the first management node can notify the terminal nodes under the first management node of the time / frequency information of the second management node, so that the terminal nodes under the first management node can keep synchronized with the first management node.

[0192] Optionally, the specific notification method adopted by the first management node may be: the first management node carries the time / frequency information of the second management node in a system message and sends the system message to the terminal nodes under the first management node. Alternatively, the first management node carries the time / frequency information of the second management node in an Extended Resource Control (XRC) signaling message and sends the XRC signaling message to the terminal nodes under the first management node.

[0193] S707: The second management node synchronizes time / frequency with the first management node.

[0194] S707 is an optional execution step. If the synchronization source device determined by the first management node in S705 is the first management node, step S707 is executed to achieve time / frequency synchronization (or multi-domain synchronization) between the second management node and the synchronization source device.

[0195] Understandably, after the time / frequency of the second management node is synchronized with that of the first management node, it is still necessary to periodically or non-periodically check whether the second management node is still synchronized with the first management node to ensure that the second management node can maintain a multi-domain synchronized state with the first management node.

[0196] Optionally, after the time / frequency of the second management node is synchronized with that of the first management node, the second management node can notify the terminal nodes under the second management node of the time / frequency information of the first management node, so that the terminal nodes under the second management node can keep synchronized with the second management node.

[0197] Optionally, the specific notification method adopted by the second management node can be: the second management node carries the time / frequency information of the first management node in a system message and sends the system message to the terminal nodes under the second management node. Alternatively, the second management node carries the time / frequency information of the first management node in an Extended Resource Control (XRC) signaling message and sends the XRC signaling message to the terminal nodes under the second management node. Figure 7The communication method shown allows the first management node in the StarSpark system to determine whether it can be a synchronization source device based on the high / low level domains of the second management node in the first information. The second management node is a device among multiple devices corresponding to multiple domains within the coverage area of ​​the first management node. For example, if the high / low level domains of the second management node in the first information indicate that the domain of the second device is a low-level domain and the domain of the first management node is a high-level domain, then the first management node can determine that it can be a synchronization source device; if the high / low level domains of the second management node in the first information indicate that the domain of the second device is a high-level domain and the domain of the first management node is a low-level domain, then the first management node can determine that the second management node can be a synchronization source device. In this way, the first management node can combine the feature of low-level domain devices in the StarSpark protocol initiating multi-domain synchronization to high-level domain devices with the determination of the synchronization source device to determine the synchronization source device from the first and second management nodes. Compared to the first management node selecting the synchronization source device according to the WDL protocol, this reduces both the latency and complexity of determining the synchronization source device.

[0198] Based on the above description of the determination of the synchronization source device, in one possible implementation, the solution provided in this application embodiment is applicable to at least one of wireless communications such as Bluetooth (BT) communication, Sparklink (or Nearlink) communication, and Wi-Fi communication. In this application embodiment, BT and Bluetooth Low Energy (BLE) can refer to each other. Sparklink can include at least one of the following: Sparklink Low Energy (SLE), Sparklink Basic (SLB), or Sparklink Position (SLP). In this application embodiment, Sparklink and Sparklink Low Energy (SLE), Sparklink Basic (SLB), or Sparklink Position (SLP) can refer to each other.

[0199] The following describes some embodiments of the solution provided in this application.

[0200] Example 1:

[0201] Bluetooth (BT), Wi-Fi, and SparkLink (or NearLink) can all use the 2.4GHz or 5GHz frequency bands and have similarities. Some modules can be reused, thus saving chip cost, area, and power consumption. Chip resources can be highly reused, allowing for rapid iteration of multiple chips.

[0202] Wi-Fi and SLB can share a single RF architecture and path. For example... Figure 8 The diagram shown is a schematic representation of a chip architecture provided in an embodiment of this application. Figure 8 It is known that through design, resources such as central processing unit (CPU), radio frequency (RF) unit, analog baseband (ABB) unit, or modem can be shared, and some modules of media access control (MAC) layer can be reused, thereby saving chip area and reducing chip cost and power consumption.

[0203] like Figure 9 The diagram shown is a schematic representation of another chip architecture provided in an embodiment of this application. Figure 9 It is known that the MAC units of BT, SLB and Wireless Fidelity (Wi-Fi) are implemented independently, while the RF units and Modem units of each mode are all shared.

[0204] like Figure 10 The diagram shown is a schematic representation of another chip architecture provided in an embodiment of this application. Figure 10 It can be seen that the MAC units of BT, SLB and Wi-Fi are implemented independently, and the Modems of BT, SLB and Wi-Fi are also implemented independently, while the RF units of each mode are all shared.

[0205] like Figure 11 The diagram shown is a schematic representation of another chip architecture provided in an embodiment of this application. Figure 11 It can be seen that the MAC units of BT, SLB and Wi-Fi are implemented independently. Some modes, such as Wi-Fi and SLB, share the same modem, while other modes, such as BT, have their modems implemented independently. All modes share the same RF.

[0206] Example 2:

[0207] The StarSpark chip can be manufactured using 14 / 28 / 40nm processes and packaged in chip-size packages (CSP), ball grid arrays (BGA), and quad flat no-lead (QFN) formats, employing either internal or external flash memory. Depending on the application scenario, at least one of the following subsystems can be integrated onto a single chip: power management unit (PMU), clock management unit (CMU), active optical network (AON), wireless local area network (WLAN), or BT, StarSpark, global navigation satellite system (GNSS), application (APP), and audio. This minimizes area, maximizes functionality, and improves performance and reliability.

[0208] This application provides a chip design approach where the stroboscopic subsystem is integrated with other subsystems onto a single chip. Depending on the product, the chip's subsystems can be tailored and combined, and the different subsystems are connected via a bus.

[0209] like Figure 12 The diagram shown is a schematic representation of a chip module framework provided in an embodiment of this application. Figure 12 It is understood that for products requiring BT or GNSS functional modules, and simultaneously needing to connect to Wi-Fi and satellite flash devices, Wi-Fi and SLB can be separated into different systems, and then combined with at least one of the following on a single chip: BT System, SLE System, GNSS System, Always On System, PMU, CMU, Flash memory, APP System, and Audio System. Different subsystems are connected via a bus.

[0210] like Figure 13 As shown, this is a schematic diagram of another chip module framework provided in an embodiment of this application. Figure 13It is known that, in some embodiments, in order to save area and cost, Wi-Fi and SLB can be combined into one subsystem, and then combined with at least one of the following on a chip: BT System, SLE System, GNSS System, Always On System, PMU, CMU, Flash memory, APP System, AudioSystem, etc., with different subsystems connected to each other via a bus.

[0211] Example 3:

[0212] The Wi-Fi / SLB 2.4GHz band operates in the 2412–2472MHz range, while the BT / BLE / SLE band operates in the 2402–2480MHz range, which may cause mutual interference. Within the same core, SLB and Wi-Fi can allocate service time slots through software scheduling; however, there is a lack of unified scheduling for SLB and Wi-Fi / BT / BLE / SLE on different cores.

[0213] This application provides a communication coexistence scheme for SLB / Wi-Fi / SLE / BT / BLE. Based on whether SLB and Wi-Fi / SLE / BT / BLE share an antenna, the coexistence scenario is divided into coexistence with different antennas (using different antennas) and coexistence with the same antenna (using the same antenna), and different coexistence strategies are given.

[0214] For the coexistence of different antennas, if SLB and Wi-Fi coexist, it can be ensured that the transmit and receive frequencies of SLB and Wi-Fi are different (i.e., frequency division multiplexing). The software can handle this from the aspects of code division multiplexing, service cycle, and interval (i.e., frequency division multiplexing). If SLB and SLE / BT / BLE coexist, and the isolation requirement cannot be met, it is necessary to avoid the channels where SLE / BT / BLE is located (i.e., channel avoidance) to reduce the impact of SLE / BT / BLE. At the same time, an aggregation scheduling mechanism can be added to aggregate and centrally send SLE / BT / BLE data packets (i.e., aggregation scheduling) to reduce the probability of interference from SLE / BT / BLE.

[0215] For shared antenna coexistence, software static strategies or hardware arbitration time-division strategies (such as packet traffic arbitration, PTA) can be used. Frequency division multiplexing, code division multiplexing, and time division multiplexing can also be employed. The advantages of software static strategies are: low hardware requirements, minimal software modifications, and no dynamic radio frequency (RF) switching (such as RF recovery). The advantages of PTA strategies are: faster service state switching and finer granularity of switching time. Packet traffic arbitration (PTA) can also be called data packet traffic arbitration.

[0216] Taking the coexistence of SLB and SLE / BT / BLE as an example, such as Figure 14 The diagram shown is a framework illustration of a software static strategy provided in an embodiment of this application. Figure 14 As can be seen, the software static strategy can include: after SLB starts, the software configures the host to notify SLE / BT / BLE to exit the current RF path. In this scenario, SLE / BT / BLE can check the SLB startup flag, and the software can be configured to switch from the current RF path to another RF path. The chip needs to support software-configured switching.

[0217] Taking the coexistence of SLB and Wi-Fi as an example, such as Figure 15 The diagram shown is a framework illustration of a software static strategy provided in an embodiment of this application. Figure 15 As can be seen, the software static strategy can include: after SLB starts, the software configures the host to notify Wi-Fi to exit the current RF path. In this scenario, Wi-Fi can check the SLB startup flag, and the software can be configured to switch from the current RF path to another RF path. The chip needs to support software-configured switching.

[0218] For example, such as Figure 16 The diagram shown illustrates a hardware arbitration time-division (PTA) strategy framework provided in an embodiment of this application. The PTA can use an arbitrator to determine whether one or more of the following—SLB / Wi-Fi / SLE / BT / BLE—use radio frequency (RF) and the RF occupancy status. For example, if the SLB needs to use RF, it can request access from the arbitrator. The arbitrator can then decide whether the SLB is allowed to use RF based on its access request, access policy, and actual occupancy status. The PTA architecture can be a two-line, three-line, or four-line architecture, etc., and can be designed and configured according to business requirements. Figure 16 As can be seen, the hardware arbitration time division (PTA) strategy includes time division of any combination of transmit (TX) and receive (RX) signals from each party in SLB / Wi-Fi / SLE / BT / BLE. The PTA module can transmit the occupancy status of the RF channel to each party, using different level signals to indicate that the RF channel is occupied by one or more of SLB / Wi-Fi / SLE / BT / BLE. This level signal is used to notify the software or hardware to perform the corresponding processing. Different services can also be assigned different PTA priorities, with higher-priority services able to preempt air interface resources.

[0219] The foregoing mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various devices. It is understood that each device, such as the first device, the second device, etc., includes corresponding hardware structures and / or software modules for executing each function in order to achieve the above-mentioned functions. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0220] This application embodiment can group the first device, second device, etc., into functional modules according to the above method example. For example, each functional group can correspond to a functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the grouping of modules in this application embodiment is illustrative and only represents one logical functional grouping. In actual implementation, there may be other grouping methods.

[0221] Figure 17 A structural diagram of a communication device 1700 is shown. This communication device 1700 can be used to perform the functions of the first device involved in the above embodiments; the coverage area of ​​the first device may include multiple domains; the multiple domains correspond to multiple devices. As one possible implementation, Figure 17 The communication device 1700 shown includes: a transceiver unit 1701 and a processing unit 1702;

[0222] The transceiver unit 1701 is used to receive first information from the second device, the first information including high and low level fields of the second device; the second device is a device among multiple devices corresponding to multiple fields. For example, the transceiver unit 1701 can support the communication device 1700 to execute S602, or the transceiver unit 1701 can support the communication device 1700 to execute S704.

[0223] Processing unit 1702 is configured to determine a synchronization source device based on first information; the synchronization source device is used for multi-domain synchronization. For example, processing unit 1702 may support communication device 1700 in executing S603, or processing unit 1702 may support communication device 1700 in executing S604.

[0224] The descriptions of the first information, the high and low level domains of the second device, the synchronization source device, and multi-domain synchronization can be found in the above method embodiments.

[0225] Specifically, the above Figure 6 and Figure 7 All relevant content regarding each step involved in the first device in the illustrated method embodiment can be referenced from the functional description of the corresponding functional module, and will not be repeated here. The communication device 1700 is used to execute... Figure 6 or Figure 7 The first device in the communication method shown can perform the same function as the communication method described above, thus achieving the same effect.

[0226] Figure 18 A structural diagram of a communication device 1800 is shown. This communication device 1800 can be used to perform the functions of the second device involved in the above embodiments; the coverage area of ​​the second device may include multiple domains; the multiple domains correspond to multiple devices. As one possible implementation, Figure 18 The communication device 1800 shown includes: a processing unit 1801 and a transceiver unit 1802;

[0227] The processing unit 1801 is used to acquire first information; the first information may include the high and low level domains of the second device; for example, the processing unit 1801 may support the communication device 1800 to execute S601, or the processing unit 1801 may support the communication device 1800 to execute S703.

[0228] The transceiver unit 1802 is used to send first information to the first device; the first information is used by the first device to determine the synchronization source device, the synchronization source device is used for multi-domain synchronization, and the first device is a device among multiple devices corresponding to multiple domains. For example, the transceiver unit 1802 can support the communication device 1800 to execute S602, or the transceiver unit 1802 can support the communication device 1800 to execute S704.

[0229] The descriptions of the first information, the high and low level domains of the second device, the synchronization source device, and multi-domain synchronization can be found in the above method embodiments.

[0230] Specifically, the above Figure 6 and Figure 7 All relevant content regarding each step involved in the second device in the illustrated method embodiment can be referenced from the functional description of the corresponding functional module, and will not be repeated here. The communication device 1800 is used to execute... Figure 6 or Figure 7 The second device in the communication method shown can achieve the same effect as the communication method described above.

[0231] The aforementioned processing unit can be a processing module, a processor, or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. A processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. A transceiver unit can be a communication module, a transceiver circuit, or a communication interface, etc. Any of the aforementioned communication devices can also include a storage unit for storing the program code and data of any communication device. The storage unit can be a storage module or a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication devices 1700 and 1800 involved in the embodiments of this application can be... Figure 19 The communication device 1900 shown. For example, the first device and the second device mentioned above can be adopted. Figure 19 The shown composition or includes Figure 19 The components shown. Figure 19 This is a schematic diagram of the composition of a communication device 1900 provided in an embodiment of this application, as shown below. Figure 19 As shown, the communication device 1900 may include a processor 1901, and optionally, may also include a communication line 1902 and a communication interface 1903.

[0232] Furthermore, the communication device 1900 may also include a memory 1904. The processor 1901, the memory 1904, and the communication interface 1903 can be connected via a communication line 1902.

[0233] The processor 1901 can be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 1901 can also be other communication devices with processing capabilities, such as circuits, devices, or software modules.

[0234] Communication line 1902 is used to transmit information between the components included in communication device 1900.

[0235] Communication interface 1903 is used for communication with other devices or other communication networks. These other communication networks can be Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. Communication interface 1903 can be a radio frequency module, transceiver, or any communication device capable of communication. This application embodiment uses a radio frequency module as an example to illustrate communication interface 1903. The radio frequency module can include an antenna, radio frequency circuitry, etc., and the radio frequency circuitry can include a radio frequency integrated chip, a power amplifier, etc.

[0236] Memory 1904 is used to store instructions. These instructions can be computer programs.

[0237] The memory 1904 can be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions; it can also be a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage, magnetic disk storage media or other magnetic storage devices. Optical disc storage includes compressed optical discs, laser discs, optical discs, universal digital discs, Blu-ray discs, etc.

[0238] It should be noted that the memory 1904 can exist independently of the processor 1901, or it can be integrated with the processor 1901. The memory 1904 can be used to store instructions, program code, or some data, etc. The memory 1904 can be located inside or outside the communication device 1900, without limitation. The processor 1901 is used to execute the instructions stored in the memory 1904 to implement the communication method provided in the following embodiments of this application.

[0239] In one example, processor 1901 may include one or more CPUs, for example Figure 19 CPU0 and CPU1 in the CPU.

[0240] As an optional implementation, the communication device 1900 includes multiple processors, for example, besides Figure 19 In addition to processor 1901, it may also include processor 1907.

[0241] As an optional implementation, the communication device 1900 also includes an output device 1905 and an input device 1906. The input device 1906 is a keyboard, mouse, microphone, or joystick, etc., and the output device 1905 is a display screen, speaker, etc.

[0242] It should be noted that the communication device 1900 can be a desktop computer, laptop computer, network server, mobile phone, tablet computer, wireless terminal, embedded device, chip system, or something similar. Figure 19 Equipment with a similar structure. Furthermore... Figure 19 The structural composition shown does not constitute a limitation on the communication device, except... Figure 19 In addition to the components shown, the communication device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0243] In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.

[0244] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be a communication device of any of the foregoing embodiments, such as an internal storage unit including a data transmission end and / or a data receiving end, such as a hard disk or memory of the first or second device. The computer-readable storage medium can also be an external storage device of the communication device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the first or second device. Further, the computer-readable storage medium can include both the internal storage unit and the external storage device of the communication device. The computer-readable storage medium is used to store the computer program and other programs and data required by the communication device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0245] It should be understood that the collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution of this application all comply with relevant laws and regulations and do not violate public order and good morals. For example, in the technical solution of this application, the processing of user personal information is carried out with the user's authorization; this will not be repeated below.

[0246] It should be noted that the terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0247] It should be understood that in this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0248] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A. For example, B can be determined based on A. It should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information. Furthermore, the term "connection" in the embodiments of this application refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices, and the embodiments of this application do not impose any limitations on this.

[0249] Unless otherwise specified, the term "transmission" in the embodiments of this application refers to bidirectional transmission, encompassing the actions of sending and / or receiving. Specifically, "transmission" in the embodiments of this application includes sending data, receiving data, or both sending and receiving data. In other words, data transmission here includes uplink and / or downlink data transmission. Data may include channels and / or signals; uplink data transmission refers to uplink channel and / or uplink signal transmission, and downlink data transmission refers to downlink channel and / or downlink signal transmission. The terms "network" and "system" in the embodiments of this application refer to the same concept; a communication system is a communication network.

[0250] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the grouping of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0251] In the several embodiments provided in this application, it should be understood that the disclosed communication devices and methods can be implemented in other ways. For example, the communication device embodiments described above are merely illustrative. For instance, the grouping of modules or units is only a logical functional grouping, and in actual implementation, there may be other grouping methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.

[0252] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0253] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0254] 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 readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device, such as a microcontroller, chip, or processor, to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media for storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0255] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A first device, characterized in that, The coverage area of ​​the first device includes multiple domains; each domain corresponds to a multiple device; the first device includes a transceiver module and a processing module. The transceiver module is used to receive first information from the second device, the first information including high and low level fields of the second device; the second device is a device among the multiple devices corresponding to the multiple fields; The processing module is used to determine the synchronization source device based on the first information; the synchronization source device is used for multi-domain synchronization.

2. The first device according to claim 1, characterized in that, The first information also includes one or more of the following parameters: The coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, or the identity information of the second device; The multi-domain synchronization feature version is used to indicate the underlying protocol version supported by the device; The power supply type is used to indicate the type of current, which includes AC or battery; The clock source type is used to indicate the clock source that provides the clock signal, and the clock source includes a local crystal oscillator or a GPS satellite navigation system; The identity information of the second device is used to uniquely identify the second device.

3. The first device according to claim 1 or 2, characterized in that, include: The processing module is configured to determine the synchronization source device based on at least one of the following: the high and low level domains of the first device, the coverage range of the first device, the multi-domain synchronization feature version of the first device, the power supply type of the first device, the clock source type of the first device, the identity information of the first device, and the first information.

4. The first device according to any one of claims 1-3, characterized in that, include: The processing module is used to determine the synchronization source device based on the value of the parameter with higher priority in the first information; or, The processing module is used to determine the synchronization source device based on the weights of the parameters in the first information.

5. The first device according to any one of claims 1-4, characterized in that, The weights of the parameters in the first information are fixed; or, The weights of the parameters in the first information are variable.

6. The first device according to any one of claims 1-5, characterized in that, The specific values ​​of the parameters in the first information may occupy the same or different number of bits.

7. The first device according to any one of claims 4-6, characterized in that, The high-priority parameters include the first parameter; the first device includes: The processing module is used to obtain the value of the first parameter of the second device; The processing module is used to obtain the value of the first parameter of the first device; When the value of the first parameter of the second device is greater than the value of the first parameter of the first device, the processing module is used to use the second device as the synchronization source device; when the value of the first parameter of the second device is less than the value of the first parameter of the first device, the processing module is used to use the first device as the synchronization source device.

8. The first device according to any one of claims 4-6, characterized in that, include: The processing module is used to calculate a first value of the second device by weighted calculation of the parameters of the second device according to the weight of the parameters, and to calculate a first value of the first device by weighted calculation of the parameters of the first device. If the first value of the second device is greater than the first value of the first device, the processing module is used to use the second device as the synchronization source device; If the first value of the second device is less than the first value of the first device, the processing module is used to use the first device as the synchronization source device.

9. The first device according to any one of claims 2-8, characterized in that, The identity information of the second device includes the identifier of the second device; or, The identity information of the second device includes the hash value of the identifier of the second device.

10. The first device according to any one of claims 2-9, characterized in that, When the first information includes multiple bits, the identity information of the second device occupies the low bits of the multiple bits; the specific values ​​of other parameters in the first information occupy the high bits of the multiple bits.

11. The first device according to claim 7, characterized in that, Regarding the first parameter in the first information, the processing module is further configured to: If the start bit of the bit corresponding to the first parameter is not the least significant bit, then a shift calculation is performed on the multiple bits included in the first information, shifting the start bit of the bit corresponding to the first parameter to the least significant bit. The value of the first parameter is obtained based on the shifted information bits.

12. A second device, characterized in that, The coverage area of ​​the second device includes multiple domains; each domain corresponds to a multiple device; the second device includes a processing module and a transceiver module. The processing module is used to acquire first information; the first information includes the high and low level domains of the second device; The transceiver module is used to send the first information to the first device. The first information is used by the first device to determine the synchronization source device. The synchronization source device is used for multi-domain synchronization. The first device is a device among the multiple devices corresponding to the multiple domains.

13. The second device according to claim 12, characterized in that, The first information also includes one or more of the following parameters: The coverage area of ​​the second device, the version of the multi-domain synchronization feature of the second device, the power supply type of the second device, the clock source type of the second device, or the identity information of the second device; The multi-domain synchronization feature version is used to indicate the underlying protocol version supported by the device; The power supply type is used to indicate the type of current, which includes AC or battery; The clock source type is used to indicate the clock source that provides the clock signal, and the clock source includes a local crystal oscillator or a GPS satellite navigation system; The identity information of the second device is used to uniquely identify the second device.

14. The second device according to claim 12 or 13, characterized in that, The identity information of the second device includes the identifier of the second device; or, The identity information of the second device includes the hash value of the identifier of the second device.

15. The second device according to any one of claims 12-14, characterized in that, The weights of the parameters in the first information are fixed; or, The weights of the parameters in the first information are variable.

16. The second device according to any one of claims 12-15, characterized in that, The specific values ​​of the parameters in the first information may occupy the same or different number of bits.

Images