Communication method and apparatus

Abstract

Embodiments of the present application relate to the field of communications, and provide a communication method and apparatus, for reducing the access duration of a terminal node in a carrier aggregation scenario, and improving the carrier management efficiency of a management node. The communication method comprises: determining a primary carrier and a secondary carrier of a terminal node among a plurality of aggregated carriers, wherein the terminal node is a user-side device in a communication domain; and on a first carrier, sending indication information to the terminal node, wherein the indication information is used for indicating the primary carrier and the secondary carrier configured for the terminal node, and the first carrier is one of the plurality of aggregated carriers.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 29, 2024, with application number 202410389186.8 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a communication method and device. Background Art

[0003] In short-range communication systems, when there is a need to increase transmission capacity, multiple carriers will be aggregated to support large-bandwidth transmission capabilities.

[0004] The SparkLink technology v1.0 system supports multi-carrier aggregation with aggregated bandwidths including 20 / 40 / 60 / 80 / 100 / 160 / 320 MHz. Each user can send information independently on each aggregated carrier.

[0005] When a user's terminal node accesses a carrier, it applies for access to each carrier one by one, resulting in low management and control efficiency of the carrier by the management node and a long access time for the terminal node. Summary of the Invention

[0006] The embodiments of the present application provide a communication method and apparatus for reducing the access duration of a terminal node and improving the management efficiency of a management node on a carrier in a carrier aggregation scenario.

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

[0008] In a first aspect, a communication method is provided, applied to a management node in a communication domain, where the communication domain utilizes multiple carriers using carrier aggregation (CA). The method may include: determining a primary carrier and a secondary carrier for a terminal node among the aggregated multiple carriers; the terminal node is a user-side device in the communication domain; and sending indication information to the terminal node on a first carrier, where the indication information is used to indicate the primary carrier and secondary carrier configured for the terminal node; the first carrier is one of the aggregated multiple carriers.

[0009] Through the solution provided in this application, the management node specifies the primary carrier and secondary carrier to the terminal node through indication information, which can avoid the terminal node attempting to access each carrier one by one, thereby shortening the time it takes for the terminal node to access the carrier; the management node can determine the primary carrier and secondary carrier to be configured for each terminal node based on factors such as network conditions, resource requirements, load configuration, and network configuration requirements, so that the management node can efficiently manage the carrier.

[0010] In addition, by configuring user-level primary and secondary carriers, when interference occurs in some of the multiple carriers, it does not affect the management node's configuration of users to use carriers that are not interfered with, thereby improving carrier utilization efficiency.

[0011] In a possible implementation, the primary carrier is used to execute access procedures, data service transmission, and configuration of high-layer signaling; and the secondary carrier is used to transmit intra-carrier control information and data service transmission.

[0012] In another possible implementation, the primary carrier is used to transmit one or more of the following information: information in a reaccess process, XRC configuration information, radio resource control (RRC) configuration information, broadcast information, synchronization information, system messages, link control information, data information, hybrid automatic repeat request (HARQ) information, automatic repeat request (ARQ) information, and channel measurement information. The secondary carrier is used to transmit one or more of the following information: broadcast information, synchronization information, system messages, link control information, data information, HARQ information, ARQ information, and channel measurement information.

[0013] Another possible implementation manner is sending the indication information to the terminal node on the first carrier, including: sending the indication information to the terminal node through high-layer signaling on the first carrier.

[0014] In another possible implementation manner, the above-mentioned high-layer signaling may include: RRC signaling, or XRC signaling.

[0015] In another possible implementation, the method provided in the present application may further include: establishing a connection with a terminal node on a primary carrier and a secondary carrier to implement communication with the terminal node.

[0016] In another possible implementation, the first carrier is the carrier to which the terminal node applies for access. When the terminal node initially accesses, it only needs to apply for access on the first carrier (any accessible carrier). The management node can implement the solution provided in this application and send the above-mentioned indication information to the terminal node on the first carrier. The terminal node does not need to request access in turn.

[0017] In another possible implementation, the first carrier is the current primary carrier of the terminal node. When the management node changes the primary carrier / secondary carrier of a terminal node, it only needs to indicate the changed primary carrier / secondary carrier on the first carrier (the current primary carrier), thereby achieving efficient management of the carrier by the management node.

[0018] In another possible implementation, the primary carrier and secondary carrier configured for the terminal node can be continuous or discrete in the frequency domain. When the primary carrier and secondary carrier are discrete in the frequency domain, flexibility in carrier scheduling in a carrier aggregation scenario is achieved.

[0019] In another possible implementation, the management node configures the primary carrier and secondary carrier at the user level. When interference occurs in some of the aggregated carriers, it does not affect the management node's configuration of users to use undisturbed carriers, thereby improving carrier utilization efficiency.

[0020] In one possible implementation, the method provided in this application may further include: the management node determining, based on the channel quality of the second carrier, a modulation mode to be used by the management node and the terminal node for exchanging information on the second carrier; the second carrier being one of the aggregated multiple carriers. Because users independently transmit services on each carrier in the primary / secondary carrier, the terminal node can determine a modulation mode appropriate for the carrier based on the channel quality of the individual carriers to achieve maximum system capacity.

[0021] The channel quality may be a signal-to-noise ratio or other parameters, which are not limited in this application.

[0022] In a second aspect, another communication method is provided, applied to a terminal node in a communication domain that uses multiple carriers using Carrier Availability (CA) technology. The method provided herein may include: receiving, on a first carrier, indication information from a management node in the communication domain, the indication information being used to indicate a primary carrier and a secondary carrier configured for the terminal node. The first carrier is one of multiple aggregated carriers. The terminal node establishes a connection with the management node on the primary carrier and the secondary carrier indicated by the indication information.

[0023] Through the solution provided in this application, the management node specifies the primary carrier and secondary carrier to the terminal node through indication information, which can avoid the terminal node attempting to access each carrier one by one, thereby shortening the time it takes for the terminal node to access the carrier; the management node can determine the primary carrier and secondary carrier to be configured for each terminal node based on factors such as network conditions, resource requirements, load configuration, and network configuration requirements, so that the management node can efficiently manage the carrier.

[0024] In one possible implementation, the method provided in this application may further include: the terminal node determining, based on the channel quality of the second carrier, a modulation mode to be used by the management node and the terminal node to exchange information on the second carrier; the second carrier being one of the primary carrier and / or the secondary carrier. Because users independently transmit services on each carrier in the primary / secondary carrier, the terminal node can determine a modulation mode appropriate for the carrier based on the channel quality of the individual carrier to achieve maximum system capacity.

[0025] The channel quality may be a signal-to-noise ratio or other parameters, which are not limited in this application.

[0026] In a possible implementation, the primary carrier is used to execute access procedures, data service transmission, and configuration of high-layer signaling; and the secondary carrier is used to transmit intra-carrier control information and data service transmission.

[0027] In another possible implementation, the primary carrier is used to transmit one or more of the following information: information in a re-access process, XRC configuration information, RRC configuration information, broadcast information, synchronization information, system messages, link control information, data information, HARQ information, ARQ information, and channel measurement information. The secondary carrier is used to transmit one or more of the following information: broadcast information, synchronization information, system messages, link control information, data information, HARQ information, ARQ information, and channel measurement information.

[0028] Another possible implementation manner is that the terminal node receives indication information from the management node in the communication domain on the first carrier, including: receiving the indication information on the first carrier through high-layer signaling.

[0029] In another possible implementation manner, the above-mentioned high-layer signaling may include: RRC signaling, or XRC signaling.

[0030] In another possible implementation, the first carrier is the carrier to which the terminal node applies for access. When the terminal node initially accesses, it only needs to apply for access on the first carrier (any accessible carrier). The management node can implement the solution provided in this application and send the above-mentioned indication information to the terminal node on the first carrier. The terminal node does not need to request access in turn.

[0031] In another possible implementation, the first carrier is the current primary carrier of the terminal node. When the management node changes the primary carrier / secondary carrier of a terminal node, it only needs to indicate the changed primary carrier / secondary carrier on the first carrier (the current primary carrier), thereby achieving efficient management of the carrier by the management node.

[0032] In another possible implementation, the primary carrier and secondary carrier configured for the terminal node can be continuous or discrete in the frequency domain. When the primary carrier and secondary carrier are discrete in the frequency domain, flexibility in carrier scheduling in a carrier aggregation scenario is achieved.

[0033] In another possible implementation, the management node configures the primary carrier and secondary carrier at the user level. When interference occurs in some of the aggregated carriers, it does not affect the management node's configuration of users to use undisturbed carriers, thereby improving carrier utilization efficiency.

[0034] In a third aspect, a communication device is provided for implementing star flash signal transmission. The communication domain in which the communication device is located adopts CA technology and uses multiple carriers. The communication device includes: a module for determining a primary carrier and a secondary carrier of a terminal node among the multiple carriers, and a module for sending indication information to the terminal node on a first carrier. The terminal node is a user-side device in the communication domain. The indication information is used to indicate the primary carrier and the secondary carrier; the first carrier is one of the multiple carriers.

[0035] In a possible implementation manner, the communication device further includes: a module for establishing a connection with the terminal node on the primary carrier and the secondary carrier.

[0036] In a possible implementation, the communication device further includes: a module for establishing a connection with a terminal node on a primary carrier and a secondary carrier.

[0037] In another possible implementation, the above-mentioned communication device is also used to realize the transmission of Bluetooth signals or WiFi signals, and at least one of the Star Flash module, Bluetooth module and WiFi module shares at least one of the radio frequency (RF) unit, modem unit, medium access control (MAC) unit and central processing unit (CPU).

[0038] In another possible implementation, the communication device is also used to realize the transmission of Bluetooth signals, but does not support the transmission of WiFi signals. The Star Flash module and the Bluetooth module are located in the same subsystem of the communication device, and the subsystem and the power management unit (PMU) are integrated in the communication device.

[0039] In another possible implementation, the communication device is also used to realize the transmission of Bluetooth signals or WiFi signals. At least one of the Bluetooth modules or WiFi modules coexists and communicates with the Star Flash module through different antennas, and the coexistence strategy is channel avoidance.

[0040] In another possible implementation, the communication device is further used to: determine the type of the opposite device and / or the service delay of the opposite device, and determine the link corresponding to the opposite device and / or the service for data transmission according to the link selection strategy.

[0041] In another possible implementation, the communication device is also used to: determine the type of the peer device and / or the service delay of the peer device, including: determining the type of the peer device, the type of the peer device includes an audio device type or a non-audio device type; when the type of the peer device is an audio device type, determining the service delay of the peer device.

[0042] In another possible implementation, the link selection strategy includes: when the service delay is greater than a first value, establishing an asynchronous unicast link or an asynchronous multicast link before performing data transmission; or, when the service delay is less than the first value and greater than a second value, establishing an asynchronous unicast link or an asynchronous multicast link, achieving synchronization by adding timestamps to data packets, and then performing data transmission; or, when the service delay is less than the second value, first establishing an asynchronous unicast link, and then establishing a synchronous unicast link or a synchronous multicast link before performing data transmission.

[0043] In another possible implementation, the communication device is further configured to: determine the type of the peer device and / or the service delay of the peer device, and determine the frame format type corresponding to the type of the peer device and / or the service type of the peer device according to the frame format selection strategy. The frame format type includes Starflash Wireless Frame Type 1, Starflash Wireless Frame Type 2, Starflash Wireless Frame Type 3, or Starflash Wireless Frame Type 4.

[0044] In another possible implementation, the communication device is also used to: determine the type of the peer device and / or the service delay of the peer device, including: determining the type of the peer device, the type of the peer device includes an audio device type or a non-audio device type; when the type of the peer device is an audio device type, determining the service delay of the peer device.

[0045] In another possible implementation, the above-mentioned frame format selection strategy includes: when the service delay of the opposite device is less than the first duration, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 through physical layer parameter negotiation after the connection state; or, when the service delay of the opposite device is less than the first duration and the service anti-interference capability requirement is greater than the set threshold, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation after entering the connection state; or, when the type of the opposite device is a device that only supports Star Flash wireless frame type 1, or a device with a maximum transmission power greater than the first power threshold, selecting Star Flash wireless frame type 1 for broadcast access; or, when the service type of the opposite device is an Internet of Things (IOT) ultra-long-distance coverage service, when the distance between the opposite device and the communication device is greater than the first threshold, selecting Star Flash wireless frame type 4 for broadcast and connection, or, when the distance between the opposite device and the communication device is less than or equal to the first threshold, switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation.

[0046] In a fourth aspect, another communication device is provided, which is used to implement the transmission of star flash signals, and the communication domain in which the communication device is located adopts CA technology and uses multiple carriers. The communication device includes: a module for receiving indication information from a management node in the communication domain on a first carrier, and a module for establishing a connection with the management node on a primary carrier and a secondary carrier. The indication information is used to indicate the primary carrier and secondary carrier configured for the terminal node; the first carrier is one of the multiple carriers.

[0047] In one possible implementation, the communication device further includes: a module for determining, based on the channel quality of the second carrier, a modulation mode used by the management node and the terminal node to interact with information on the second carrier, where the second carrier is one of the main carrier and / or the auxiliary carrier.

[0048] In another possible implementation, the communication device is also used to realize the transmission of Bluetooth signals or WiFi signals, and at least one of the Star Flash module, Bluetooth module and WiFi module shares at least one of the RF unit, modem unit, MAC unit and CPU.

[0049] In another possible implementation, the communication device is also used to realize the transmission of Bluetooth signals, but does not support the transmission of WiFi signals. The Star Flash module and the Bluetooth module are located in the same subsystem of the communication device, and the subsystem and PMU are integrated in the communication device.

[0050] In another possible implementation, the communication device is also used to realize the transmission of Bluetooth signals or WiFi signals. At least one of the Bluetooth modules or WiFi modules coexists and communicates with the Star Flash module through different antennas, and the coexistence strategy is channel avoidance.

[0051] In another possible implementation, the communication device is further used to: determine the type of the opposite device and / or the service delay of the opposite device, and determine the link corresponding to the opposite device and / or the service for data transmission according to the link selection strategy.

[0052] In another possible implementation, the communication device is also used to: determine the type of the peer device and / or the service delay of the peer device, including: determining the type of the peer device, the type of the peer device includes an audio device type or a non-audio device type; when the type of the peer device is an audio device type, determining the service delay of the peer device.

[0053] In another possible implementation, the link selection strategy includes: when the service delay is greater than a first value, establishing an asynchronous unicast link or an asynchronous multicast link before performing data transmission; or, when the service delay is less than the first value and greater than a second value, establishing an asynchronous unicast link or an asynchronous multicast link, achieving synchronization by adding timestamps to data packets, and then performing data transmission; or, when the service delay is less than the second value, first establishing an asynchronous unicast link, and then establishing a synchronous unicast link or a synchronous multicast link before performing data transmission.

[0054] In another possible implementation, when the communication device is a non-audio device, the communication device is further configured to: transmit data via an asynchronous unicast or asynchronous multicast link.

[0055] In another possible implementation, the communication device is also used to: determine the type of the opposite device and / or the service delay of the opposite device, and determine the frame format type corresponding to the type of the opposite device and / or the service type of the opposite device according to the frame format selection strategy; wherein the frame format type includes Star Flash Wireless Frame Type 1, Star Flash Wireless Frame Type 2, Star Flash Wireless Frame Type 3 or Star Flash Wireless Frame Type 4.

[0056] In another possible implementation, the communication device is also used to: determine the type of the peer device and / or the service delay of the peer device, including: determining the type of the peer device, the type of the peer device includes an audio device type or a non-audio device type; when the type of the peer device is an audio device type, determining the service delay of the peer device.

[0057] In another possible implementation, the above-mentioned frame format selection strategy includes: when the service delay of the opposite device is less than the first duration, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 through physical layer parameter negotiation after the connection state; or, when the service delay of the opposite device is less than the first duration and the service anti-interference capability requirement is greater than the set threshold, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation after entering the connection state; or, when the type of the opposite device is a device that only supports Star Flash wireless frame type 1, or a device with a maximum transmission power greater than the first power threshold, selecting Star Flash wireless frame type 1 for broadcast access; or, when the service type of the opposite device is IOT ultra-long-distance coverage service, when the distance between the opposite device and the communication device is greater than the first threshold, selecting Star Flash wireless frame type 4 for broadcast and connection, or, when the distance between the opposite device and the communication device is less than or equal to the first threshold, switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation.

[0058] In another possible implementation, when the communication device is a non-audio device, the communication device is also used to: select Starflash wireless frame type 1 for broadcast access, and after entering the connection state, switch to Starflash wireless frame type 2 for data transmission through physical layer parameter negotiation.

[0059] In a fifth aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided. The communication device includes: a processor configured to implement the functions involved in any of the above aspects.

[0060] In one possible design, the communication device may further include a memory for storing necessary program instructions and data. A processor is coupled to the memory, and the processor is configured to execute the computer program or instructions stored in the memory, causing the communication device to perform the method described in any possible implementation of the first or second aspect.

[0061] In one possible design solution, the communication device described in the fifth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the fifth aspect to communicate with other communication devices.

[0062] In one possible design, the processor can be integrated with the memory.

[0063] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0064] In a sixth aspect, a communication device is provided, which includes a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor being used to implement the method described in any possible implementation method of the first aspect or the second aspect through a logic circuit or executing code instructions.

[0065] It can be understood that when the communication device provided in either the fifth aspect or the sixth aspect is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0066] In a seventh aspect, a communication chip is provided, in which instructions are stored. When the chip is run on a communication device, the method described in either the first aspect or the second aspect is implemented.

[0067] In an eighth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the first or second aspects above.

[0068] In a ninth aspect, a computer program product comprising instructions is provided, including computer program code, which enables the communication device to execute the method described in any one of the first or second aspects above when the computer program code is run on the communication device.

[0069] In a tenth aspect, a communication system is provided, comprising: a management node for implementing the method described in the first aspect above, and a terminal node for implementing the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] FIG1 is a schematic diagram of a scenario after aggregation of multiple carriers;

[0071] FIG2 is a schematic diagram of a carrier aggregation scenario of a Wi-Fi system;

[0072] FIG3 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0073] FIG4 is a flow chart of a communication method provided in an embodiment of the present application;

[0074] FIG5 is a flow chart of another communication method provided in an embodiment of the present application;

[0075] FIG6 is a schematic diagram of a process of allocating a primary / secondary carrier from a management node to a terminal node according to an embodiment of the present application;

[0076] FIG7 is a schematic diagram of a scenario in which a management node allocates a primary / secondary carrier to a terminal node according to an embodiment of the present application;

[0077] FIG8 is a schematic diagram of a chip architecture provided in an embodiment of the present application;

[0078] FIG9 is a schematic diagram of another chip architecture provided in an embodiment of the present application;

[0079] FIG10 is a schematic diagram of another chip architecture provided in an embodiment of the present application;

[0080] FIG11 is a schematic diagram of another chip architecture provided in an embodiment of the present application;

[0081] FIG12 is a schematic diagram of a chip module framework provided in an embodiment of the present application;

[0082] FIG13 is a schematic diagram of another chip module framework provided in an embodiment of the present application;

[0083] FIG14 is a schematic diagram of another chip module framework provided in an embodiment of the present application;

[0084] FIG15 is a schematic diagram of a framework of a software static policy provided in an embodiment of the present application;

[0085] FIG16 is a schematic diagram of a framework of a hardware time-division arbitration (PTA) strategy provided in an embodiment of the present application;

[0086] FIG17 is a schematic diagram of a link establishment process according to an embodiment of the present application;

[0087] FIG18 is a schematic diagram of another link establishment process provided in an embodiment of the present application;

[0088] FIG19 is a schematic diagram of another link establishment process provided in an embodiment of the present application;

[0089] FIG20 is a schematic diagram of a flow chart of another link establishment process provided in an embodiment of the present application;

[0090] FIG21 is a schematic diagram of another link establishment process provided in an embodiment of the present application;

[0091] FIG22 is a schematic diagram of another link establishment process provided in an embodiment of the present application;

[0092] FIG23 is a diagram of four different radio frame types defined in the Star Flash protocol;

[0093] FIG24 is a diagram illustrating an example of a frame format application in a scenario provided by an embodiment of the present application;

[0094] FIG25 is a diagram illustrating an example of a frame format application in another scenario provided by an embodiment of the present application;

[0095] FIG26 is a diagram illustrating an example of a frame format application in another scenario provided by an embodiment of the present application;

[0096] FIG27 is a diagram illustrating an example of a frame format application in another scenario provided by an embodiment of the present application;

[0097] FIG28 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0098] FIG29 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0099] Figure 30 is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0100] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0101] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0102] At the same time, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0103] Finally, the network architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Ordinary technicians in this field can know that 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.

[0104] To facilitate understanding, some examples of concepts related to the embodiments of the present application are provided for reference.

[0105] A management node (grant node) may be a node that sends data scheduling information in a communication system and may be referred to as a G node.

[0106] A terminal node may be a node in a communication system that receives data scheduling information and sends data according to the data scheduling information, and may be referred to as a T-node.

[0107] The management node communication link (a communication link for transmission from the grant node to the terminal node) refers to the communication link from the management node to the terminal node. This link can carry data channels, control channels, broadcast channels, synchronization signals, and other information from the management node to the terminal node. It is called a G link. The symbols used for transmission on the G link are called G symbols.

[0108] The terminal node communication link (a communication link for transmission from a terminal node to a grant node) refers to the communication link from the terminal node to the management node. This link carries data channels, access channels, feedback signals, and other information from the terminal node to the management node, and is referred to as a T-link. The symbols used for T-link transmission are called T symbols.

[0109] A communication domain refers to the G-link and T-link resources of a management node in a communication system. A communication domain can also be called a cell.

[0110] The primary carrier (P-Carrier) is used to carry signaling and manage other carriers.

[0111] Secondary Carrier (S-Carrier) is a carrier used to extend bandwidth.

[0112] The technical solutions of the embodiments of the present application can be applied to, but not limited to, wireless short-range communication systems. Among them, vehicle-mounted wireless short-range communication technology (also known as Star Flash technology) has the advantages of ultra-low latency, ultra-high reliability, and precise synchronization, and is suitable for applications in scenarios such as smart cars, smart homes, smart terminals, and smart manufacturing. For example, applications in smart car scenarios include: immersive in-car sound field & noise reduction, wireless interactive projection, and 360-degree panoramic view, which can achieve an immersive interactive experience and improve vehicle safety.

[0113] In some possible implementations, the wireless short-range communication system can be used in combination with a mobile communication system, for example, the mobile communication system includes but is not limited to the fourth generation (4G) communication system (for example, the long term evolution (LTE) system), the fifth generation (5G) communication system (for example, the new radio (NR) system), and future mobile communication systems such as the sixth generation (6G) mobile communication system.

[0114] Carrier aggregation (CA) is a technology that combines multiple independent carrier channels to increase bandwidth, thereby improving data rates and capacity. Figure 1 shows the scenario of multiple carrier aggregation.

[0115] In a communication system using multi-carrier aggregation, it is necessary to manage the multi-carriers, for example, managing the aggregation mode of the multi-carriers, managing the access to the multi-carriers, managing the configuration of the multi-carriers, and exchanging multi-carrier information.

[0116] In the field of short-distance communication, both the Star Flash V1.0 system and the WIFI system use CA technology to improve bandwidth, which are described below.

[0117] The Starflash v1.0 system supports multi-carrier aggregation, and its aggregated bandwidth includes 20 / 40 / 60 / 80 / 100 / 160 / 320MHz. Each user sends information independently on each aggregated carrier. However, in the Starflash system, when accessing a carrier, the terminal node applies for access to each carrier one by one until access is successful, and then sends information independently on the carrier with successful access. The management node cannot efficiently control the number of accessed carriers and the terminal node cannot access the appropriate carrier. This process takes a long time for the terminal node to access. Moreover, after the terminal node accesses, the management node cannot efficiently change the carrier to which the terminal node accesses. Overall, the implementation complexity of multi-carrier aggregation in the Starflash V1.0 system is high.

[0118] The Wi-Fi system supports aggregation of multiple 20MHz carriers, with aggregated bandwidths of 20 / 40 / 80 / 160 / 320MHz. These aggregated carriers include a primary carrier. Control information, such as system broadcasts, is transmitted via the primary carrier, while data is transmitted on the primary carrier and other carriers. A schematic diagram of a carrier aggregation scenario in the Wi-Fi system is shown in Figure 2. However, the aggregation of multiple 20MHz carriers in the Wi-Fi system uses contiguous carrier aggregation, which is inflexible in scheduling. The carriers used by a terminal node must be contiguous with the primary carrier. For example, as shown in Figure 2 (c), if a terminal node uses three carriers, it can only use C2, C3, and C4, or C3, C4, and C1, or C4, C1, and C2. Furthermore, the Wi-Fi system configures a cell-level primary carrier. Control information for all terminal nodes in a communication domain is transmitted and received on the same primary carrier. The service-occupied frequencies must include the primary carrier. If the primary carrier is interfered with, other carriers, regardless of interference, cannot be used, resulting in low carrier utilization efficiency.

[0119] Based on this, the present application provides a communication method in which a management node determines the user-level primary and secondary carriers and notifies the terminal node via indication information, thereby enabling the management node to efficiently manage the aggregated multi-carriers. Terminal nodes no longer need to apply for access on a carrier-by-carrier basis, shortening the access time for terminal nodes. Furthermore, even if the primary carrier is interfered with, the management node can configure other carriers for use by the terminal node, providing strong anti-interference capabilities and improving carrier utilization.

[0120] The solution provided in this application can be applied to the communication system shown in Figure 3. As shown in Figure 3, the communication system may include a management node and a terminal node. Optionally, the management node in the embodiment of this application may be a node that sends data scheduling information to the vehicle-mounted wireless short-range communication system, and the terminal node in the embodiment of this application may be a node that receives data scheduling information from the vehicle-mounted wireless short-range communication system and sends data based on the data scheduling information. These are described here uniformly and will not be repeated below.

[0121] In the communication system shown in FIG3 , the number of management nodes and terminal nodes can be configured according to actual needs. FIG3 is only an illustration of a scenario and does not specifically limit the communication system.

[0122] Exemplarily, the communication system shown in FIG3 may be a star flash system.

[0123] Exemplarily, the management node is located on the network side of the above-mentioned communication system to help the terminal node achieve wireless access, and the device with wireless transceiver function may be provided in a chip or chip system of the device. The network device includes but is not limited to: base station, evolved NodeB (eNodeB), access point (AP), transmission reception point (TRP or transmission point, TP), next generation NodeB (gNB), next generation base station in the sixth generation (6G) mobile communication system, base station in future mobile communication system, or access point (AP) in wireless fidelity (Wi-Fi) system. The management node can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, an open radio access network (ORAN) or a wireless controller in a centralized radio access network (CRAN) scenario. The management node may also be one or a group of antenna panels (including multiple antenna panels) of a base station in the fifth generation (5G), or 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), or a radio unit (RU), or a roadside unit (RSU) with base station functions. Optionally, the management node may also be a server, a wearable device, a vehicle, or an onboard device. For example, a network device in vehicle-to-everything (V2X) technology may be an RSU. Optionally, the management node may also be a control device such as a central control panel 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 may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform). The management node in this application may also be a logical node, logical module or software that can implement all or part of the functions of the access network device.

[0124] The embodiment of the present application does not limit the form of the management node. The device used to implement the functions of the management node can be a management node; it can also be a device that can support the management node to implement the functions, such as a chip system. The device can be installed in the management node or used in conjunction with the management node.

[0125] A terminal node is a device, equipment, module, chip or chip system with transceiver functions. The terminal node may also be called 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 device, user agent or user device. The terminal nodes in the embodiments of the present application may be mobile phones, cellular phones, smart phones, tablet computers, wireless data cards, personal digital assistants (PDAs), wireless modems, handheld devices (handsets), laptop computers, machine type communication (MTC) terminals, computers with wireless transceiver functions, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home appliances (e.g., refrigerators, televisions, air conditioners, electric meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in unmanned driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, roadside units with terminal functions, etc. The terminal node of the present application may also be an onboard module, onboard module, onboard component, onboard chip or onboard unit built into a vehicle as one or more components or units. The terminal node may also be other devices with terminal functions. For example, the terminal node may also be a device that functions as a terminal in device-to-device (D2D) communication.

[0126] The embodiments of this application do not limit the form of terminal nodes. The device used to implement the functions of the terminal node can be a terminal node; it can also be a device that can support the terminal node to implement 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.

[0127] Exemplarily, the management node or the terminal node may be an audio or video device, such as a microphone (eg, a headset, a live broadcast microphone, or other), a stylus, and the like.

[0128] Exemplarily, the management node or terminal node may be a non-audio or video device, such as a keyboard, a mouse, a toothbrush, and the like.

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

[0130] The scheme provided by the embodiment of the present application will be specifically described below with reference to the accompanying drawings. The scheme provided by the present application can be applied to the interaction process between the management node and the terminal node in the communication domain, and the communication domain adopts CA technology to use multiple carriers. Of course, the subject that executes the management node action in the method can also be a device / module in the management node, such as a chip, processor, processing unit, etc. in the management node; the subject that executes the terminal node action in the method can also be a device / module in the terminal node, such as a chip, processor, processing unit, etc. in the terminal node, and the embodiment of the present application does not make specific limitations on this.

[0131] It should be noted that the interaction process between the management node and each terminal node in the communication domain is the same. The following embodiments of this application take the interaction process between the management node and a terminal node as an example to describe the solution provided by this application.

[0132] As shown in FIG4 , the communication method provided in this embodiment of the present application may include:

[0133] S401: A management node determines a primary carrier and a secondary carrier of a terminal node from among multiple aggregated carriers.

[0134] The terminal node is a user-side device in the communication domain.

[0135] In a possible implementation, in S401 , the management node may determine a primary carrier and a secondary carrier for each terminal node, where the determined primary carrier and secondary carrier are user-level.

[0136] Illustratively, the primary carrier and the secondary carrier of different terminal nodes in a communication domain may be the same or different, which is not limited in this embodiment of the present application.

[0137] In one possible implementation, the management node may determine the primary carrier and secondary carrier of the current terminal node based on the current traffic volume of each aggregated carrier and the load balancing principle. Of course, the load balancing principle can be configured according to actual needs.

[0138] In one possible implementation, the management node may select carriers from the aggregated multiple carriers in a preset order as primary carriers for different terminal nodes. The preset order may be from smallest to largest center frequency, from largest to smallest center frequency, or other order, which is not limited in this embodiment of the present application.

[0139] Of course, the specific scheme for the management node to determine the primary carrier and secondary carrier of the terminal node, as a scheme for the management node to manage the carrier, can be configured according to actual needs. The embodiments of the present application are not limited to this. The above-listed implementation methods are only examples and do not constitute specific limitations.

[0140] In a possible implementation, the primary carrier is used to execute access procedures, data service transmission, and configuration of high-layer signaling, while the secondary carrier is used to transmit intra-carrier control information and data service transmission.

[0141] Exemplarily, the primary carrier is used to transmit one or more of the following information: information in the re-access process, XRC configuration information, RRC configuration information, broadcast information, synchronization information, system messages, link control information, data information (information when transmitting service data), HARQ information, ARQ information, and channel measurement information.

[0142] Exemplarily, the secondary carrier is used to transmit one or more of the following information: broadcast information, synchronization information, system message, link control information, data information, HARQ, ARQ, and channel measurement information.

[0143] Of course, the content of the information transmitted by the primary carrier / secondary carrier can be configured according to actual needs and is not limited to the above example.

[0144] In a possible implementation, the primary carrier and the secondary carrier may be continuous or discrete in the frequency domain.

[0145] S402: The management node sends indication information to the terminal node on the first carrier, where the indication information is used to indicate the determined primary carrier and secondary carrier.

[0146] The first carrier is one of the multiple carriers.

[0147] In a possible implementation, the indication information may include identification information of the primary carrier and the secondary carrier allocated to the terminal node, determined by the management node in S401.

[0148] The identification information of the carrier may be serial number information or other information, which is used to uniquely indicate the carrier. The embodiment of the present application does not limit the content of the identification information of the carrier.

[0149] In one possible implementation, the management node in S402 may send indication information to the terminal node via high-layer signaling on the first carrier. Specifically, the indication information may be carried in the high-layer signaling for transmission. The embodiment of the present application does not limit the specific location of the indication information in the high-layer signaling and may be configured according to actual needs.

[0150] Exemplarily, the high-layer signaling may include: RRC signaling, or XRC signaling. Of course, the high-layer signaling used to transmit the indication information may also be other, which is not limited in the embodiment of the present application.

[0151] Furthermore, in different scenarios, the content of the first carrier of the indication information sent by the management node is different, which will be described below in detail.

[0152] Case 1: In the scenario of initial access of a terminal node, the first carrier is the carrier to which the terminal node applies for access.

[0153] Case 2: In the scenario of changing the primary / secondary carrier, the first carrier is the current primary carrier of the terminal node.

[0154] S403: The terminal node receives instruction information from the management node on the first carrier.

[0155] The indication information received by the terminal node in S403 is the indication information sent by the management node in S402. The content and sending method of the indication information are not described in detail here.

[0156] The first carrier has been described in detail in S402 and will not be repeated here.

[0157] In a possible implementation, in S403 , the terminal node receives indication information from the management node via high-layer signaling on the first carrier.

[0158] S404: The terminal node establishes a connection with the management node on the primary carrier and the secondary carrier.

[0159] Specifically, after S403, the terminal node has obtained the main carrier and secondary carrier allocated to it by the management node (including new allocation in the initial access scenario, or reallocation in the change scenario). In S404, the terminal node establishes a connection with the management node on the main carrier and secondary carrier indicated by the above indication information (the main carrier and secondary carrier allocated to it by the management node) to facilitate subsequent communication between the two.

[0160] It should be understood that the terminal node establishes a connection with the management node on the primary carrier and the secondary carrier, which means that the terminal node and the management node establish a connection between the two through interaction. The embodiment of the present application will not elaborate on the process of establishing the connection.

[0161] Through the solution provided in the embodiment of the present application, the management node specifies the primary carrier and secondary carrier to the terminal node through indication information, which can avoid the terminal node attempting to access each carrier, thereby shortening the time it takes for the terminal node to access the carrier; the management node can efficiently manage the carrier based on factors such as network conditions, resource requirements, and load configuration.

[0162] In addition, by configuring user-level primary and secondary carriers, when interference occurs in some of the multiple carriers, it does not affect the management node's configuration of users to use carriers that are not interfered with, thereby improving carrier utilization efficiency.

[0163] Furthermore, when multiple carriers are aggregated, if the management node and the terminal node use the same constellation point modulation scheme when exchanging information on each carrier, when the channel quality of each carrier differs (e.g., a significant difference in signal-to-noise ratio), each carrier cannot obtain a modulation scheme that matches the channel, and maximum system capacity cannot be achieved. Based on this, the method provided in the embodiment of the present application also includes a process for determining the modulation mode of the carrier based on the channel quality.

[0164] Illustratively, as shown in FIG5 , the communication method provided in the embodiment of the present application may further include the process of S405 .

[0165] S405: The management node or the terminal node determines, according to the channel quality of the second carrier, a modulation mode used by the management node and the terminal node to exchange information on the second carrier.

[0166] In a possible implementation, if S405 is executed by the management node, the second carrier may be one of the aggregated multiple carriers.

[0167] In another possible implementation, if S405 is executed by the terminal node, the second carrier may be a primary carrier and / or a secondary carrier.

[0168] Of course, the content of the second carrier can be configured according to actual needs. The second carrier can be one or more, so as to achieve the maximum system capacity of the second carrier by using a modulation mode that matches the channel quality of the second carrier.

[0169] Exemplarily, channel quality is a parameter used to describe channel performance. For example, channel quality may be a signal-to-noise ratio or other parameters, which are not limited in the embodiments of the present application.

[0170] Exemplarily, the modulation mode may include, but is not limited to: multiple amplitude shift keying (MASK) modulation, multiple phase shift keying (MPSK) modulation, multiple quadrature amplitude modulation (MQAM) modulation or others.

[0171] In one possible implementation, different modulation modes corresponding to different channel qualities can be configured according to network requirements. In S405, the management node or the terminal node determines the modulation mode corresponding to the channel quality of the second carrier, which is used as the modulation mode used by the management node and the terminal node to exchange information on the second carrier.

[0172] In another possible implementation, a mapping model of channel quality and modulation mode can be configured. In S405, the management node or terminal node substitutes the channel quality of the second carrier into the mapping model to obtain the modulation mode used by the management node and the terminal node to interact with information on the second carrier.

[0173] Of course, the specific implementation process of determining the modulation mode based on channel quality can be deployed according to actual needs, and the embodiments of the present application do not specifically limit this process.

[0174] The following describes the solution provided in this application through examples.

[0175] In a multi-carrier aggregation scenario, the communication systems of the management node and the terminal nodes operate on multiple aggregated carriers. The management node (G node) allocates user-level primary and secondary carriers to the terminal nodes (T nodes). The G node configures a primary and secondary carrier for each T node. That is, the primary and secondary carriers of each T node can be the same or different. In the network, after different T nodes access the same or different carriers of the G node, the G node allocates the corresponding primary and secondary carriers to each T node, and each T node transmits services on its own primary and secondary carriers.

[0176] The primary carrier (P-carrier) is user-level and is responsible for the access process, RRC configuration (including RRC for users on secondary carriers), and service data transmission. Terminal nodes must establish a permanent connection with the P-carrier, over which services may or may not be transmitted. The secondary carrier (S-carrier) is also user-level and is combined with the P-carrier to carry out intra-carrier control information transmission and data service transmission.

[0177] Exemplarily, the process of the management node allocating the primary / secondary carrier to the terminal node may include the following steps 1 to 3:

[0178] Step 1: The T node applies for access on any carrier.

[0179] As shown in FIG6 , in the process of the management node allocating the primary / secondary carrier to the terminal node, the T1 node applies for access on the #j carrier, and the T2 node applies for access on the #m carrier.

[0180] Step 2: Node G allocates a primary carrier and a secondary carrier to node T on the access carrier.

[0181] As shown in Figure 6, node G determines to allocate the main carrier Cp and the secondary carrier Cq to node T1, and indicates the main carrier Cp and the secondary carrier Cq to node T1 on carrier #j; node G determines to allocate the main carrier Ck and the secondary carrier Cn to node T2, and indicates the main carrier Ck and the secondary carrier Cn to node T2 on carrier #m.

[0182] Step 3: The T node transmits services on the allocated primary / secondary carrier.

[0183] As shown in FIG6 , the T1 node sends and receives data with the G node on the carriers Cp and Cq; the T2 node sends and receives data with the G node on the carriers Ck and Cn.

[0184] The scenario corresponding to the process shown in FIG6 , ie, the scenario in which the management node allocates the primary / secondary carrier to the terminal node, is shown in FIG7 .

[0185] After steps 1 to 3 above, user data transmitted between the G node and the T node is independently transmitted on multiple carriers. The G node or the T node can determine the modulation mode of the user on each carrier according to the channel quality of each carrier.

[0186] The information carried by the primary / secondary carrier is exemplified below. Various channels / information can be transmitted on the primary / secondary carrier according to the contents shown in Table 1.

[0187] Table 1

[0188] The following describes the solutions provided in the embodiments of this application in different scenarios.

[0189] Scenario 1: Initial access scenario. The multi-carrier access process may include the following steps:

[0190] Step a: The T node randomly scans available frequency points and applies for initial access on a carrier that is allowed to be accessed (the carrier to which access is applied).

[0191] The carrier to which the T node applies for access may be the first carrier scanned and allowed to be accessed, which more effectively saves the access time of the terminal node.

[0192] Step b: The T node receives a communication domain system message of the carrier to which access is requested, and determines whether access is to be made on the current carrier.

[0193] Specifically, the T-node determines whether the carrier it is requesting access meets its service transmission requirements based on the communication domain system information of the carrier it is requesting access to. If so, the T-node attempts access. If the carrier does not meet the access requirements (for example, the access subcarrier width does not meet the specification requirements), the T-node repeats steps a and b with a different carrier until access is successful on a carrier.

[0194] Step c: After successfully accessing a certain carrier, the G node allocates a primary carrier and a secondary carrier to the T node on the carrier to which the access is successful.

[0195] The specific allocation process is as described in the above embodiment and will not be repeated here.

[0196] Scenario 2: Re-access scenario (e.g., the connection between the T-node and the G-node is interrupted or for other reasons, requiring re-access). The multi-carrier access process may include: the T-node first accesses the designated primary carrier (the primary carrier used before the connection was interrupted). If access is unsuccessful, the T-node then applies for access according to the initial access scenario (Scenario 1 above) and the multi-carrier access process. If access is successful on the original primary carrier, the T-node and the G-node resume communication on the original primary carrier / secondary carrier.

[0197] Scenario 3: In the scenario where the T node has been connected, the management node changes the primary carrier / secondary carrier of the T node based on the network status. The process includes: the G node first determines the changed primary carrier / secondary carrier. The G node has a currently connected P-carrier and sends an indication message to the T node through high-layer signaling. The indication message indicates the changed P-carrier and S-carrier. The T node changes the P-carrier and S-carrier according to the indication message. After that, it establishes a connection with the G node on the changed P-carrier and S-carrier to transmit service data.

[0198] For example, the solution provided in this application can be applied to the Star Flash system, and of course can also be applied to other communication systems, which is not limited to the embodiments of this application.

[0199] As described in the above embodiments, through the solution provided by this application, the management node can flexibly configure and change the main / auxiliary carriers of each terminal node, which can better adapt to changes in cell traffic and user traffic demand, and realize efficient management of the carriers by the management node.

[0200] In one possible implementation, the solution provided in the embodiment of the present application can be applied to a star flash system.

[0201] In the embodiments of the present application, Bluetooth (BT) and Bluetooth low energy (BLE) may refer to each other. Sparklink or nearlink may both be overlapping networking modes for multiple piconets, and may both use the 2.4 GHz frequency band and frequency hopping technology, with similar features. Sparklink low energy (SLE), Sparklink basic (SLB), or Sparklink position (SLP) may also refer to each other.

[0202] Some embodiments of the solutions provided by this application are introduced below.

[0203] Example 1:

[0204] Both Bluetooth (BT) and SparkLink (or NearLink) can form overlapping piconets. Both utilize the 2.4 GHz frequency band and frequency hopping technology, sharing similarities. This allows for the reuse of some modules, saving chip cost, area, and power consumption. This allows for a high degree of chip resource reuse and rapid iteration across multiple chips.

[0205] BLE and SLE can share a set of radio frequency architecture and channels. As shown in Figure 8, a chip architecture schematic diagram is provided for an embodiment of the present application. As can be seen from Figure 8, through design, it is possible to achieve resource sharing of the central processing unit (CPU), radio frequency (RF) unit), analog baseband (ABB) unit, or modem, and reuse of some modules of the media access control (MAC) layer, thereby saving chip area, reducing chip cost and power consumption. As shown in Figure 9, another chip architecture schematic diagram is provided for an embodiment of the present application. As can be seen from Figure 9, the MAC units of BT, SLE and wireless fidelity (WIFI) are implemented independently, and the RF units and Modem units of each mode are all shared. As shown in Figure 10, another chip architecture schematic diagram is provided for an embodiment of the present application. As can be seen from Figure 10, the MAC units of BT, SLE and WIFI are implemented independently, and the Modems of BT, SLE and WIFI are also implemented independently, and the RF units of each mode are all shared. As shown in Figure 11, another chip architecture schematic diagram is provided for an embodiment of the present application. As shown in Figure 11, the MAC units of BT, SLE, and WIFI are implemented independently. Some modes, such as BT and SLE, share the same modem. Other modes, such as WIFI, have their own independent modem implementations, and all RFs are shared.

[0206] Example 2:

[0207] SLE chips can be manufactured using 14 / 28 / 40nm processes and packaged in chip size packages (CSP), ball grid array (BGA), and quad flat no-lead (QFN), with either internal or external flash memory. Depending on the application scenario, at least one of the following subsystems, including a power management unit (PMU), clock management unit (CMU), active optical network (AON), wireless local area network (WLAN) or Bluetooth, SLE, global navigation satellite system (GNSS), application (APP), and audio, can be integrated onto a single chip, minimizing area, maximizing functionality, and improving performance and reliability.

[0208] The present application provides a chip design method in which the SLE and other subsystems are integrated on a single chip. The subsystems of the chip can be tailored and combined according to different products, and different subsystems are connected via a bus.

[0209] As shown in Figure 12, a schematic diagram of a chip module framework provided by an embodiment of the present application is shown. As shown in Figure 12, for products that require functional modules such as WIFI or GNSS and need to connect to Bluetooth and Star Flash devices, BT and SLE can be divided into different systems, and then combined with WIFI System, GNSS System, Always On System, PMU, CMU, Flash memory, etc. on a single chip. Different subsystems are connected through a bus.

[0210] Figure 13 shows another schematic diagram of a chip module framework provided by an embodiment of the present application. As shown in Figure 13, for devices that do not require functional modules such as Wi-Fi or GNSS but require audio functions, in order to save area and cost, BLE and SLE can be combined into one subsystem, which can then be combined with the App System, Audio System, Always On System, PMU, CMU, Flash, etc. on a single chip. Different subsystems are connected via a bus.

[0211] Figure 14 shows another schematic diagram of a chip module framework provided by an embodiment of the present application. As shown in Figure 14, for devices that do not require functional modules such as Wi-Fi or GNSS, nor audio functions, to save space and cost, BLE and SLE can be combined into one subsystem, which can then be combined with the Always On System, CMU, PMU, Flash, etc. on a single chip, with the different subsystems connected via a bus.

[0212] Example 3:

[0213] The WiFi 2.4G frequency band is 2412-2472MHz, while the BT / BLE / SLE frequency band is 2402-2480MHz, potentially interfering with each other. SLE and BT / BLE within the same core can be allocated service time slots through software scheduling, but SLE and BT / BLE / WiFi on different cores lack unified scheduling.

[0214] The embodiment of the present application provides a coexistence solution for SLE / BT / BLE / WIFI. Depending on whether SLE and BT / BLE / WIFI share the same antenna, the coexistence scenario is divided into different antenna coexistence (using different antennas) and shared antenna coexistence (using the same antenna), and different coexistence strategies are given.

[0215] For heterogeneous antenna coexistence, if SLE and BT / BLE coexist, the transmit and receive frequencies of SLE and BT / BLE can be kept different (i.e., frequency division multiplexing). The software can handle this based on the frequency hopping sequence (i.e., code division multiplexing), service cycle, and interval (i.e., time division multiplexing). If SLE and Wi-Fi coexist, if isolation cannot meet the requirements, it is necessary to avoid the WLAN channel (i.e., channel avoidance) to reduce the impact of WLAN. At the same time, a cluster scheduling mechanism can be added to aggregate and send Wi-Fi packets (i.e., cluster scheduling) to reduce the probability of WLAN interference.

[0216] For coexistence using the same antenna, either a software static strategy or a hardware packet traffic arbitration (PTA) strategy can be used. The advantages of the software static strategy include minimal hardware requirements, minimal software modifications, and no dynamic radio frequency (RF) switching (such as RF recovery). The advantages of the PTA strategy include faster service state switching and finer switching time granularity.

[0217] Taking the coexistence of SLE and Wi-Fi as an example, Figure 15 shows a schematic diagram of the framework of a software static policy provided in an embodiment of the present application. As can be seen from Figure 15, the software static policy may include: after SLE is started, the host (HOST) is configured through software to notify Wi-Fi to exit the current RF path. In this scenario, Wi-Fi can check the SLE startup flag, and the software can set it to switch from the current RF path to another RF path. The chip needs to support software-set switching.

[0218] Exemplarily, as shown in FIG16, a schematic diagram of the framework of a hardware arbitration time division (PTA) strategy provided in an embodiment of the present application is provided. As can be seen from FIG16, the hardware arbitration time division (PTA) strategy includes: any combination of transmission (TX) and reception (RX) of each party is time-divided, and the PTA module will transmit the occupancy status of the radio frequency channel to each party respectively, using different level signals to indicate that the radio frequency channel is occupied by SLE / BT / BLE / WIFI, and this signal is used to notify the software or hardware to perform the corresponding processing. Different services can also set different PTA priorities, and high-priority services can seize air interface resources.

[0219] Example 4:

[0220] The Star Flash standard defines asynchronous and synchronous data links. Asynchronous links are divided into asynchronous unicast and multicast, and synchronous links are divided into synchronous unicast, multicast, and broadcast. This embodiment of the application designs a set of SLE link selection schemes based on the different real-time data requirements of different products. By connecting different devices in different scenarios, different data links can be used to support the needs of different product application scenarios.

[0221] Figure 17 is a schematic diagram of a link establishment process according to an embodiment of the present application. As shown in Figure 17, after the T node sends a broadcast packet to the G node, the G node sends a scan access request to the T node. Furthermore, after the T node sends a scan access response to the G node, an asynchronous unicast link is established between the G node and the T node, and data is transmitted over the established asynchronous unicast link.

[0222] Figure 18 is a schematic diagram of another link establishment process provided by an embodiment of the present application. As shown in Figure 18, after the T node sends a broadcast packet to the G node, the G node sends a scan access request to the T node. Furthermore, after the T node sends a scan access response to the G node, an asynchronous multicast link is established between the G node and the T node, and data is transmitted over the established asynchronous multicast link.

[0223] For products (such as non-audio devices such as keyboards, mice, and styluses) or services that do not require real-time data (i.e., the service delay of the product or service is greater than the first value), an asynchronous unicast link as shown in Figure 17 or an asynchronous multicast link as shown in Figure 18 can be established for data transmission.

[0224] Figure 19 is a schematic diagram of another link establishment process provided by an embodiment of the present application. As shown in Figure 19, after the T node sends a broadcast packet to the G node, the G node sends a scan access request to the T node. Furthermore, after the T node sends a scan access response to the G node, the G node and the T node first establish an asynchronous unicast link, and then establish a synchronous unicast link, and data is transmitted over the established synchronous unicast link.

[0225] Figure 20 is a schematic diagram of another link establishment process provided by an embodiment of the present application. As shown in Figure 20, after the T node sends a broadcast packet to the G node, the G node sends a scan access request to the T node. Furthermore, after the T node sends a scan access response to the G node, the G node and the T node first establish an asynchronous unicast link, then establish a synchronous multicast link, and transmit data over the established synchronous multicast link.

[0226] For products (such as audio devices such as headphones and microphones) or services with real-time data requirements (that is, the service delay of the product or service is less than the second value), as shown in Figure 19 or Figure 20, an asynchronous unicast link can be established first, and then a synchronous unicast link or a synchronous multicast link can be established for data transmission.

[0227] Figure 21 is a schematic diagram of another link establishment process provided by an embodiment of the present application. As shown in Figure 21, after the T node sends a broadcast packet to the G node, the G node sends a scan access request to the T node. Furthermore, after the T node sends a scan access response to the G node, an asynchronous unicast link is established between the G node and the T node, and data transmission is performed after synchronization is achieved by adding timestamps to the data packets.

[0228] Figure 22 is a schematic diagram of another link establishment process provided by an embodiment of the present application. As shown in Figure 22, after the T node sends a broadcast packet to the G node, the G node sends a scan access request to the T node. Furthermore, after the T node sends a scan access response to the G node, an asynchronous multicast link is established between the G node and the T node, and data transmission is performed after synchronization is achieved by adding timestamps to the data packets.

[0229] For products (such as audio devices such as headsets and live microphones) or services that have data real-time requirements but not particularly high real-time requirements (that is, the service delay of the product or service is less than the first value and greater than the second value), asynchronous unicast or asynchronous multicast links can also be established to achieve synchronization by adding timestamps to data packets.

[0230] Embodiment 5:

[0231] As shown in Figure 23, the StarFlash protocol defines four different radio frame types. Each frame format corresponds to different sensitivity, frame length, modulation mode, and synchronization sequence. Physical layer parameter negotiation can be used to select different frame formats in different scenarios to maximize performance benefits. The following provides examples of selecting different frame formats in different scenarios.

[0232] As shown in Figure 24, an example of a frame format application in a scenario provided by an embodiment of the present application is shown. For low-latency products (such as keyboards, mice, styluses, toothbrushes, microphones, etc.) or business scenarios (i.e., the service latency of the product or business is less than the first duration), frame format 1 is selected for broadcast access, and after entering the connected state, it is switched to frame format 2 through physical layer parameter negotiation.

[0233] As shown in Figure 25, an example of frame format application in another scenario provided by an embodiment of the present application is shown. Among them, for products (such as mobile phones, headphone audio) or business scenarios that have both low latency (i.e., the service delay of the product or service is less than the first duration) and anti-interference demands (i.e., the anti-interference capability of the product or service is required to be greater than a set threshold), frame format 1 is selected for broadcast access, and after entering the connected state, it is switched to frame format 2 or frame format 3 through physical layer parameter negotiation.

[0234] As shown in Figure 26, an example of frame format application in another scenario provided by an embodiment of the present application is shown. For extremely low-cost devices that only support Gaussian frequency shift keying (GFSK) frame format (GFSK has a higher maximum transmit power than phase shift keying (PSK)), or devices that are sensitive to maximum transmit power (i.e., the maximum transmit power must be greater than a first power threshold), frame format 1 is selected for broadcast access, and no frame format switching is performed subsequently.

[0235] As shown in Figure 27, an example of frame format application in another scenario provided by an embodiment of the present application is shown. For the ultra-long-distance coverage scenario of the Internet of Things (IoT), frame format 4 is selected for broadcasting and connection. When the distance is shortened, frame format 2 or 3 can be switched through physical layer parameter negotiation. Otherwise, frame format 4 is maintained.

[0236] It should be noted that the frame format one in the embodiment of the present application can also be called the frame format corresponding to the Star Flash Wireless Frame Type 1, the frame format two in the embodiment of the present application can also be called the frame format corresponding to the Star Flash Wireless Frame Type 2, the frame format three in the embodiment of the present application can also be called the frame format corresponding to the Star Flash Wireless Frame Type 3, and the frame format four in the embodiment of the present application can also be called the frame format corresponding to the Star Flash Wireless Frame Type 4.

[0237] In each of the above embodiments, the methods and / or steps implemented by the management node may also be implemented by components that can be used for the management node (e.g., a processor, chip, chip system, circuit, logic module, or software); the methods and / or steps implemented by the terminal node may also be implemented by components that can be used for the management node (e.g., a processor, chip, chip system, circuit, logic module, or software).

[0238] The above mainly introduces the solution provided by this application. Accordingly, this application also provides a communication device, which is used to implement the various methods in the above method embodiments. The communication device can be the management node in the above method embodiments, or a device including a management node, or a component that can be used for a management node, such as a chip or a chip system. Alternatively, the communication device can be the terminal node in the above method embodiments, or a device including a terminal node, or a component that can be used for a terminal node, such as a chip or a chip system.

[0239] In some embodiments, in order to implement the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0240] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0241] In some embodiments, the present application further provides a communication device 280 for implementing the transmission of star flash signals, wherein the communication domain in which the communication device 280 is located uses multiple carriers using CA technology. The communication device 290 may include: a module for determining the primary carrier and secondary carrier of a terminal node among multiple carriers, and a module for sending indication information to the terminal node on a first carrier. The terminal node is a user-side device in the communication domain. The indication information is used to indicate the primary carrier and secondary carrier; the first carrier is one of the multiple carriers.

[0242] In a possible implementation, the communication device 280 may further include: a module for establishing a connection with a terminal node on a primary carrier and a secondary carrier.

[0243] In a possible implementation, the communication device further includes: a module for establishing a connection with a terminal node on a primary carrier and a secondary carrier.

[0244] Optionally, as shown in FIG28 , the module for determining the primary carrier and secondary carrier of the terminal node among multiple carriers may be a processing module 2801, and the module for sending indication information to the terminal node on the first carrier may be a communication module 2802. Similarly, the module for establishing a connection with the terminal node on the primary carrier and the secondary carrier may be a processing module 2801, and the module for establishing a connection with the terminal node on the primary carrier and the secondary carrier may be a processing module 2801.

[0245] The communication module and processing module in the embodiment of the present application can be deployed in the Star Flash module, Bluetooth module or WiFi module at the same time; or, the communication module in the embodiment of the present application can be deployed in the Star Flash module, Bluetooth module or WiFi module, and the processing module in the embodiment of the present application can be deployed in other modules of the module where the processing module is located; or, the processing module in the embodiment of the present application can be deployed in the Star Flash module, Bluetooth module or WiFi module, and the communication module in the embodiment of the present application can be deployed in other modules of the module where the processing module is located. The embodiment of the present application does not make specific limitations on this.

[0246] In another possible implementation, the above-mentioned communication device 280 is also used to realize the transmission of Bluetooth signals or WiFi signals, and at least one of the Star Flash module, Bluetooth module and WiFi module shares at least one of the RF unit, modem unit, MAC unit and CPU.

[0247] In another possible implementation, the communication device 280 is also used to realize the transmission of Bluetooth signals, but does not support the transmission of WiFi signals. The Star Flash module and the Bluetooth module are located in the same subsystem of the communication device 280, and the subsystem and PMU are integrated in the communication device 280.

[0248] In another possible implementation, the communication device 280 is also used to realize the transmission of Bluetooth signals or WiFi signals. At least one of the Bluetooth modules or WiFi modules coexists and communicates with the Star Flash module through different antennas, and the coexistence strategy is channel avoidance.

[0249] In another possible implementation, the communication device 280 is further used to determine the type of the opposite device and / or the service delay of the opposite device, and determine the link corresponding to the opposite device and / or the service for data transmission according to the link selection strategy.

[0250] In another possible implementation, the communication device 280 is also used to: determine the type of the opposite device and / or the service delay of the opposite device, including: determining the type of the opposite device, the type of the opposite device includes an audio device type or a non-audio device type; when the type of the opposite device is an audio device type, determining the service delay of the opposite device.

[0251] In another possible implementation, the link selection strategy includes: when the service delay is greater than a first value, establishing an asynchronous unicast link or an asynchronous multicast link before performing data transmission; or, when the service delay is less than the first value and greater than a second value, establishing an asynchronous unicast link or an asynchronous multicast link, achieving synchronization by adding timestamps to data packets, and then performing data transmission; or, when the service delay is less than the second value, first establishing an asynchronous unicast link, and then establishing a synchronous unicast link or a synchronous multicast link before performing data transmission.

[0252] In another possible implementation, the communication device 280 is further configured to determine the type of the peer device and / or the service latency of the peer device, and determine, based on a frame format selection strategy, a frame format type corresponding to the type of the peer device and / or the service type of the peer device. The frame format types include Starflash Wireless Frame Type 1, Starflash Wireless Frame Type 2, Starflash Wireless Frame Type 3, or Starflash Wireless Frame Type 4.

[0253] In another possible implementation, the communication device 280 is also used to: determine the type of the opposite device and / or the service delay of the opposite device, including: determining the type of the opposite device, the type of the opposite device includes an audio device type or a non-audio device type; when the type of the opposite device is an audio device type, determining the service delay of the opposite device.

[0254] In another possible implementation, the above-mentioned frame format selection strategy includes: when the service delay of the opposite device is less than the first duration, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 through physical layer parameter negotiation after the connection state; or, when the service delay of the opposite device is less than the first duration and the service anti-interference capability requirement is greater than the set threshold, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation after entering the connection state; or, when the type of the opposite device is a device that only supports Star Flash wireless frame type 1, or a device with a maximum transmission power greater than the first power threshold, selecting Star Flash wireless frame type 1 for broadcast access; or, when the service type of the opposite device is IOT ultra-long-distance coverage service, when the distance between the opposite device and the communication device is greater than the first threshold, selecting Star Flash wireless frame type 4 for broadcast and connection, or, when the distance between the opposite device and the communication device is less than or equal to the first threshold, switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation.

[0255] In some embodiments, the present application further provides a communication device 290 for implementing the transmission of star flash signals, wherein the communication domain in which the communication device 290 is located adopts CA technology and uses multiple carriers. The communication device 290 may include: a module for receiving indication information from a management node in the communication domain on a first carrier, and a module for establishing a connection with the management node on a primary carrier and a secondary carrier. The indication information is used to indicate the primary carrier and secondary carrier configured for the terminal node; the first carrier is one of the multiple carriers.

[0256] In one possible implementation, the communication device 290 may further include: a module for determining the modulation mode used by the management node and the terminal node to interact with information on the second carrier based on the channel quality of the second carrier, where the second carrier is one of the main carrier and / or auxiliary carrier.

[0257] Optionally, as shown in Figure 29, the module for receiving indication information from the management node in the communication domain on the first carrier may be a communication module 2901, and the module for establishing a connection with the management node on the primary carrier and the secondary carrier may be a processing module 2902. Similarly, the module for determining, based on the channel quality of the second carrier, the modulation mode used by the management node and the terminal node to exchange information on the second carrier may be the processing module 2902.

[0258] The communication module and processing module in the embodiment of the present application can be deployed in the Star Flash module, Bluetooth module or WiFi module at the same time; or, the communication module in the embodiment of the present application can be deployed in the Star Flash module, Bluetooth module or WiFi module, and the processing module in the embodiment of the present application can be deployed in other modules of the module where the processing module is located; or, the processing module in the embodiment of the present application can be deployed in the Star Flash module, Bluetooth module or WiFi module, and the communication module in the embodiment of the present application can be deployed in other modules of the module where the processing module is located. The embodiment of the present application does not make specific limitations on this.

[0259] In another possible implementation, the communication device 290 is also used to realize the transmission of Bluetooth signals or WiFi signals, and at least one of the Star Flash module, Bluetooth module and WiFi module shares at least one of the RF unit, modem unit, MAC unit and CPU.

[0260] In another possible implementation, the communication device 290 is also used to realize the transmission of Bluetooth signals, but does not support the transmission of WiFi signals. The Star Flash module and the Bluetooth module are located in the same subsystem of the communication device 290, and the subsystem and PMU are integrated in the communication device 290.

[0261] In another possible implementation, the communication device 290 is also used to realize the transmission of Bluetooth signals or WiFi signals. At least one of the Bluetooth modules or WiFi modules coexists and communicates with the Star Flash module through different antennas, and the coexistence strategy is channel avoidance.

[0262] In another possible implementation, the communication device 290 is further used to determine the type of the opposite device and / or the service delay of the opposite device, and determine the link corresponding to the opposite device and / or the service for data transmission according to the link selection strategy.

[0263] In another possible implementation, the communication device 290 is also used to: determine the type of the opposite device and / or the service delay of the opposite device, including: determining the type of the opposite device, the type of the opposite device includes an audio device type or a non-audio device type; when the type of the opposite device is an audio device type, determining the service delay of the opposite device.

[0264] In another possible implementation, the link selection strategy includes: when the service delay is greater than a first value, establishing an asynchronous unicast link or an asynchronous multicast link before performing data transmission; or, when the service delay is less than the first value and greater than a second value, establishing an asynchronous unicast link or an asynchronous multicast link, achieving synchronization by adding timestamps to data packets, and then performing data transmission; or, when the service delay is less than the second value, first establishing an asynchronous unicast link, and then establishing a synchronous unicast link or a synchronous multicast link before performing data transmission.

[0265] In another possible implementation, when the communication device 290 is a non-audio device, the communication device 290 is further configured to: transmit data via an asynchronous unicast or asynchronous multicast link.

[0266] In another possible implementation, the communication device 290 is also used to: determine the type of the opposite device and / or the service delay of the opposite device, and determine the frame format type corresponding to the type of the opposite device and / or the service type of the opposite device according to the frame format selection strategy; wherein the frame format type includes Star Flash Wireless Frame Type 1, Star Flash Wireless Frame Type 2, Star Flash Wireless Frame Type 3 or Star Flash Wireless Frame Type 4.

[0267] In another possible implementation, the communication device 290 is also used to: determine the type of the opposite device and / or the service delay of the opposite device, including: determining the type of the opposite device, the type of the opposite device includes an audio device type or a non-audio device type; when the type of the opposite device is an audio device type, determining the service delay of the opposite device.

[0268] In another possible implementation, the above-mentioned frame format selection strategy includes: when the service delay of the opposite device is less than the first duration, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 through physical layer parameter negotiation after the connection state; or, when the service delay of the opposite device is less than the first duration and the service anti-interference capability requirement is greater than the set threshold, selecting Star Flash wireless frame type 1 for broadcast access, and switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation after entering the connection state; or, when the type of the opposite device is a device that only supports Star Flash wireless frame type 1, or a device with a maximum transmission power greater than the first power threshold, selecting Star Flash wireless frame type 1 for broadcast access; or, when the service type of the opposite device is IOT ultra-long-distance coverage service, when the distance between the opposite device and the communication device is greater than the first threshold, selecting Star Flash wireless frame type 4 for broadcast and connection, or, when the distance between the opposite device and the communication device is less than or equal to the first threshold, switching to Star Flash wireless frame type 2 or Star Flash wireless frame type 3 through physical layer parameter negotiation.

[0269] In another possible implementation, when the communication device 290 is a non-audio device, the communication device 290 is also used to: select Star Flash wireless frame type 1 for broadcast access, and after entering the connection state, switch to Star Flash wireless frame type 2 for data transmission through physical layer parameter negotiation.

[0270] An embodiment of the present application provides a schematic structural diagram of a communication device 300. As shown in Figure 30, the communication device 300 may include a processor 3001, a bus 3002, a communication interface 3003, and a memory 3004. The processor 3001, the memory 3004, and the communication interface 3003 communicate with each other via the bus 3002. The communication device 300 may be the aforementioned management node or terminal node. It should be understood that this application does not limit the number of processors and memories in the communication device 300.

[0271] Bus 3002 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG30 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 3002 may include a path for transmitting information between the various components of communication device 300 (e.g., memory 3004, processor 3001, and communication interface 3003).

[0272] The processor 3001 may include any one or more processors such as a CPU, a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0273] The memory 3004 may include a volatile memory, such as a random access memory (RAM). The processor 3001 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0274] The communication interface 3003 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the communication device 300 and other devices or a communication network.

[0275] The memory 3004 stores executable program codes, and the processor 3001 executes the executable program codes to respectively implement the functions of the management node or the terminal node in the aforementioned method embodiment. That is, the memory 3004 stores instructions for executing the aforementioned communication method.

[0276] On the other hand, an embodiment of the present application further provides a computer program product comprising instructions, including computer program code, which, when the computer program code runs on a communication device, enables the communication device to execute the method described in any of the above embodiments.

[0277] In another aspect, embodiments of the present application further provide a computer-readable storage medium storing a computer program or instruction that, when executed on a communication device, enables the communication device to execute the method described in any of the above embodiments.

[0278] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0279] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0280] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0281] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0282] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0283] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0284] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or an access network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a random access memory RAM, a magnetic disk, or an optical disk.

[0285] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0286] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: Applied to a management node in a communication domain, the communication domain adopts carrier aggregation (CA) technology to use multiple carriers, the method comprising: Determining a primary carrier and a secondary carrier of a terminal node among the multiple carriers; the terminal node is a user-side device in the communication domain; Indication information is sent to the terminal node on a first carrier, where the indication information is used to indicate the primary carrier and the secondary carrier; the first carrier is one of the multiple carriers.

2. The method according to claim 1, characterized in that The primary carrier is used to execute access procedures, data service transmission, and configuration of high-layer signaling; the secondary carrier is used to transmit intra-carrier control information and data service transmission.

3. The method according to claim 1 or 2, characterized in that The primary carrier is used to transmit one or more of the following information: information in the re-access process, XRC configuration information, RRC configuration information, broadcast information, synchronization information, system messages, link control information, data information, hybrid automatic repeat request HARQ information, automatic repeat request ARQ information, and channel measurement information; The secondary carrier is used to transmit one or more of the following information: broadcast information, synchronization information, system message, link control information, data information, HARQ information, ARQ information, and channel measurement information.

4. The method according to any one of claims 1 to 3, characterized in that The sending indication information to the terminal node on the first carrier includes: The indication information is sent to the terminal node through high-layer signaling on the first carrier.

5. The method according to claim 4, characterized in that The high-level signaling includes: Radio Resource Control (RRC) signaling, or XRC signaling.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: A connection is established with the terminal node on the primary carrier and the secondary carrier.

7. The method according to any one of claims 1 to 6, characterized in that The first carrier is a carrier to which the terminal node applies for access, or the first carrier is a current primary carrier of the terminal node.

8. The method according to any one of claims 1 to 7, characterized in that The primary carrier and the secondary carrier are user-grade.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Determine, according to the channel quality of the second carrier, a modulation mode used by the management node and the terminal node to exchange information on the second carrier; the second carrier is one of the multiple carriers.

10. A communication method, characterized in that: Applied to a terminal node in a communication domain, the communication domain adopts carrier aggregation (CA) technology to use multiple carriers, the method comprising: receiving, on a first carrier, indication information from a management node in the communication domain, the indication information being used to indicate a primary carrier and a secondary carrier configured for the terminal node; the first carrier being one of the multiple carriers; A connection is established with the management node on the primary carrier and the secondary carrier.

11. The method according to claim 10, characterized in that The primary carrier is used to execute access procedures, data service transmission, and configuration of high-layer signaling; the secondary carrier is used to transmit intra-carrier control information and data service transmission.

12. The method according to claim 11, characterized in that The primary carrier is used to transmit one or more of the following information: information in the re-access process, XRC configuration information, RRC configuration information, broadcast information, synchronization information, system messages, link control information, data information, hybrid automatic repeat request HARQ information, automatic repeat request ARQ information, and channel measurement information; The secondary carrier is used to transmit one or more of the following information: broadcast information, synchronization information, system message, link control information, data information, HARQ information, ARQ information, and channel measurement information.

13. The method according to any one of claims 10 to 12, characterized in that: The receiving, on the first carrier, indication information from the management node in the communication domain includes: The indication information is received on the first carrier through higher layer signaling.

14. The method according to claim 13, characterized in that The high-level signaling includes: Radio Resource Control (RRC) signaling, or XRC signaling.

15. The method according to any one of claims 10 to 14, characterized in that: The first carrier is a carrier to which the terminal node applies for access, or the first carrier is a current primary carrier of the terminal node.

16. The method according to any one of claims 10 to 15, characterized in that: The primary carrier and the secondary carrier are user-grade.

17. The method according to any one of claims 10 to 16, characterized in that: The method further comprises: Determine, according to the channel quality of the second carrier, a modulation mode used by the management node and the terminal node to exchange information on the second carrier; the second carrier is one of the primary carrier and / or the secondary carrier.

18. A communication device, characterized in that: The communication device is used to realize the transmission of star flash signals. The communication domain where the communication device is located adopts carrier aggregation CA technology to use multiple carriers. The communication device includes: a module for determining a primary carrier and a secondary carrier of a terminal node among the multiple carriers, the terminal node being a user-side device in the communication domain; A module for sending indication information to the terminal node on a first carrier; the indication information is used to indicate the primary carrier and the secondary carrier; the first carrier is one of the multiple carriers.

19. The communication device according to claim 18, wherein: The communication device further includes: A module for establishing a connection with the terminal node on the primary carrier and the secondary carrier.

20. The communication device according to claim 18 or 19, characterized in that The communication device further includes: A module for determining, based on the channel quality of a second carrier, a modulation mode used by a management node and a terminal node to exchange information on the second carrier; the second carrier is one of the multiple carriers.

21. The communication device according to any one of claims 18 to 20, characterized in that: The communication device is also used to realize the transmission of Bluetooth signals or WiFi signals, and at least one module among the Star Flash module, the Bluetooth module and the WiFi module shares a radio frequency RF unit.

22. The communication device according to any one of claims 18 to 21, characterized in that: The communication device is also used to realize the transmission of Bluetooth signals, but does not support the transmission of WiFi signals. The Star Flash module and the Bluetooth module are located in the same subsystem of the communication device, and the subsystem and the power management module PMU are integrated in the communication device.

23. The communication device according to any one of claims 18 to 22, characterized in that: The communication device is also used to realize the transmission of Bluetooth signals or WiFi signals. At least one of the Bluetooth module or WiFi module and the Star Flash module coexist and communicate through different antennas, and the coexistence strategy is channel avoidance.

24. The communication device according to any one of claims 18 to 23, characterized in that The communication device is further configured to determine the type of the opposite device and / or the service delay of the opposite device, and determine the link corresponding to the opposite device and / or the service for data transmission according to a link selection strategy.

25. The communication device according to claim 24, characterized in that The communication device is further configured to determine a type of an opposite-end device and / or a service delay of the opposite-end device, including: Determining a type of a peer device, where the type of the peer device includes an audio device type or a non-audio device type; In a case where the type of the opposite-end device is the audio device type, a service delay of the opposite-end device is determined.

26. The communication device according to claim 24 or 25, characterized in that The link selection strategy includes: When the service delay is greater than the first value, establishing an asynchronous unicast link or an asynchronous multicast link and then performing data transmission; or When the service delay is less than the first value and greater than the second value, the asynchronous unicast link or the asynchronous multicast link is established, and data transmission is performed after synchronization is achieved by adding timestamps to data packets; or When the service delay is less than the second value, the asynchronous unicast link is established first, and then the synchronous unicast link or the synchronous multicast link is established to perform data transmission.

27. The communication device according to any one of claims 18 to 26, characterized in that The communication device is also used to: determine the type of the opposite device and / or the service delay of the opposite device, and determine the frame format type corresponding to the type of the opposite device and / or the service type of the opposite device according to the frame format selection strategy; wherein the frame format type includes Star Flash Wireless Frame Type 1, Star Flash Wireless Frame Type 2, Star Flash Wireless Frame Type 3 or Star Flash Wireless Frame Type 4.

28. The communication device according to claim 27, wherein: The communication device is further configured to determine a type of an opposite-end device and / or a service delay of the opposite-end device, including: Determining a type of a peer device, where the type of the peer device includes an audio device type or a non-audio device type; In a case where the type of the opposite-end device is the audio device type, a service delay of the opposite-end device is determined.

29. The communication device according to claim 27 or 28, characterized in that The frame format selection strategy includes: When the service delay of the opposite device is less than the first duration, select the Star Flash wireless frame type 1 for broadcast access, and switch to the Star Flash wireless frame type 2 through physical layer parameter negotiation after the connection state; or When the service delay of the opposite device is less than the first duration and the service anti-interference capability requirement is greater than the set threshold, the Star Flash wireless frame type 1 is selected for broadcast access, and after entering the connected state, the Star Flash wireless frame type 2 or the Star Flash wireless frame type 3 is switched through physical layer parameter negotiation; or When the type of the opposite device is a device that only supports the Starflash wireless frame type 1, or a device whose maximum transmit power is greater than a first power threshold, select the Starflash wireless frame type 1 for broadcast access; or In the case where the service type of the opposite device is the Internet of Things (IoT) ultra-long-distance coverage service, when the distance between the opposite device and the communication device is greater than a first threshold, the Starflash wireless frame type 4 is selected for broadcasting and connection, or, when the distance between the opposite device and the communication device is less than or equal to the first threshold, the Starflash wireless frame type 2 or the Starflash wireless frame type 3 is switched through physical layer parameter negotiation.

30. A communication device, characterized in that: The communication device is used to realize the transmission of star flash signals. The communication domain where the communication device is located adopts carrier aggregation CA technology to use multiple carriers. The communication device includes: a module configured to receive, on a first carrier, indication information from a management node in the communication domain, the indication information being used to indicate a primary carrier and a secondary carrier configured for the terminal node; the first carrier being one of the multiple carriers; A module for establishing a connection with the management node on the primary carrier and the secondary carrier.

31. The communication device according to claim 30, wherein: The communication device further includes: A module for determining, based on a channel quality of a second carrier, a modulation mode used by the management node and the terminal node to exchange information on the second carrier, where the second carrier is one of the primary carrier and / or the secondary carrier.

32. The communication device according to claim 30 or 31, characterized in that The communication device is also used to realize the transmission of Bluetooth signals or WiFi signals, and at least one module among the Star Flash module, the Bluetooth module and the WiFi module shares a radio frequency RF unit.

33. The communication device according to any one of claims 30 to 32, characterized in that: The communication device is also used to realize the transmission of Bluetooth signals, but does not support the transmission of WiFi signals. The Star Flash module and the Bluetooth module are located in the same subsystem of the communication device, and the subsystem and the power management module PMU are integrated in the communication device.

34. The communication device according to any one of claims 30 to 33, characterized in that The communication device is also used to realize the transmission of Bluetooth signals or WiFi signals. At least one of the Bluetooth module or WiFi module and the Star Flash module coexist and communicate through different antennas, and the coexistence strategy is channel avoidance.

35. The communication device according to any one of claims 30 to 34, characterized in that The communication device is further configured to determine the type of the opposite device and / or the service delay of the opposite device, and determine the link corresponding to the opposite device and / or the service for data transmission according to a link selection strategy.

36. The communication device according to claim 35, characterized in that The communication device is further configured to determine a type of an opposite-end device and / or a service delay of the opposite-end device, including: Determining a type of a peer device, where the type of the peer device includes an audio device type or a non-audio device type; In a case where the type of the opposite-end device is the audio device type, a service delay of the opposite-end device is determined.

37. The communication device according to claim 35 or 36, characterized in that The link selection strategy includes: When the service delay is greater than the first value, establishing an asynchronous unicast link or an asynchronous multicast link and then performing data transmission; or When the service delay is less than the first value and greater than the second value, the asynchronous unicast link or the asynchronous multicast link is established, and data transmission is performed after synchronization is achieved by adding timestamps to data packets; or When the service delay is less than the second value, the asynchronous unicast link is established first, and then the synchronous unicast link or the synchronous multicast link is established to perform data transmission.

38. The communication device according to any one of claims 30 to 33, characterized in that In the case that the communication device is a non-audio device, the communication device is further configured to: transmit data via an asynchronous unicast or asynchronous multicast link.

39. The communication device according to any one of claims 30 to 38, characterized in that The communication device is also used to: determine the type of the opposite device and / or the service delay of the opposite device, and determine the frame format type corresponding to the type of the opposite device and / or the service type of the opposite device according to the frame format selection strategy; wherein the frame format type includes Star Flash Wireless Frame Type 1, Star Flash Wireless Frame Type 2, Star Flash Wireless Frame Type 3 or Star Flash Wireless Frame Type 4.

40. The communication device according to claim 39, wherein: The communication device is further configured to determine a type of an opposite-end device and / or a service delay of the opposite-end device, including: Determining a type of a peer device, where the type of the peer device includes an audio device type or a non-audio device type; In a case where the type of the opposite-end device is the audio device type, a service delay of the opposite-end device is determined.

41. The communication device according to claim 39 or 40, characterized in that The frame format selection strategy includes: When the service delay of the opposite device is less than the first duration, select the Star Flash wireless frame type 1 for broadcast access, and switch to the Star Flash wireless frame type 2 through physical layer parameter negotiation after the connection state; or When the service delay of the opposite device is less than the first duration and the service anti-interference capability requirement is greater than the set threshold, the Star Flash wireless frame type 1 is selected for broadcast access, and after entering the connected state, the Star Flash wireless frame type 2 or the Star Flash wireless frame type 3 is switched through physical layer parameter negotiation; or When the type of the opposite device is a device that only supports the Starflash wireless frame type 1, or a device whose maximum transmit power is greater than a first power threshold, select the Starflash wireless frame type 1 for broadcast access; or In the case where the service type of the opposite device is the Internet of Things (IoT) ultra-long-distance coverage service, when the distance between the opposite device and the communication device is greater than a first threshold, the Starflash wireless frame type 4 is selected for broadcasting and connection, or, when the distance between the opposite device and the communication device is less than or equal to the first threshold, the Starflash wireless frame type 2 or the Starflash wireless frame type 3 is switched through physical layer parameter negotiation.

42. The communication device according to any one of claims 30 to 36, characterized in that When the communication device is a non-audio device, the communication device is also used to: select Star Flash wireless frame type 1 for broadcast access, and after entering the connection state, switch to Star Flash wireless frame type 2 for data transmission through physical layer parameter negotiation.

43. A communication device, characterized in that include: processor; The processor is configured to execute a computer program or instruction so that the method according to any one of claims 1 to 9 or claims 10 to 17 is implemented.

44. A communication chip, characterized in that: Instructions are stored therein, and when the chip is run on a communication device, the method according to any one of claims 1 to 9 or claims 10 to 17 is implemented.

45. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 9 or claims 10 to 17 is implemented.

46. ​​A computer program product, characterized in that The device comprises a computer program code, and when the computer program code is run on a communication device, the communication device implements the method according to any one of claims 1 to 9 or claims 10 to 17.

Images