CN116349258A - Synchronization method and synchronization device - Google Patents

Synchronization method and synchronization device Download PDF

Info

Publication number
CN116349258A
CN116349258A CN202180074935.2A CN202180074935A CN116349258A CN 116349258 A CN116349258 A CN 116349258A CN 202180074935 A CN202180074935 A CN 202180074935A CN 116349258 A CN116349258 A CN 116349258A
Authority
CN
China
Prior art keywords
bis
synchronization
big
information
target
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202180074935.2A
Other languages
Chinese (zh)
Inventor
董建利
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN116349258A publication Critical patent/CN116349258A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08User group management

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Abstract

The application relates to a synchronization method and synchronization equipment. The synchronization method comprises the following steps: the controller creates a synchronization request based on the broadcast synchronization group BIGs, and switches the synchronized broadcast synchronization stream BIS to the target BIS. According to the embodiment of the application, the synchronized BIS is switched to the target BIS by the controller based on the BIG creation synchronization request, so that the power consumption of synchronous receiving can be reduced and the synchronous switching time can be shortened in the BIS synchronous switching process.

Description

Synchronization method and synchronization device Technical Field
The present application relates to the field of communications, and more particularly, to a synchronization method and synchronization apparatus.
Background
Bluetooth low energy (Bluetooth Low Energy, BLE) is also called low-power Bluetooth, belongs to a personal area network technology, and can be used in the fields of medical care, sports and fitness, beacons, security protection, home entertainment and the like. In the bluetooth Core specification (Core Spec), which includes a broadcast synchronization group (Broadcast Isochronous Group, BIG), a BIG may include one or more broadcast synchronization streams (Broadcast Isochronous Stream, BIS). Consideration is required to reduce power consumption and time in the BIS synchronous switching process.
Disclosure of Invention
The embodiment of the application provides a synchronization method and synchronization equipment, which can reduce power consumption and switching time in the BIS synchronization switching process.
The embodiment of the application provides a synchronization method, which comprises the following steps:
the controller creates a synchronization request based on the broadcast synchronization group BIGs, and switches the synchronized broadcast synchronization stream BIS to the target BIS.
The embodiment of the application provides a synchronization method, which comprises the following steps:
the host transmits a BIG creation synchronization request to the controller to instruct the controller to switch the synchronized BIS to a target BIS based on the BIG creation synchronization request.
The embodiment of the application provides a synchronization device, which comprises:
and a control unit for creating a synchronization request based on the broadcast synchronization group BIG, and switching the synchronized broadcast synchronization stream BIS to the target BIS.
The embodiment of the application provides a synchronization device, which comprises:
and a transmitting unit for transmitting a BIG creation synchronization request to a controller to instruct the controller to switch the synchronized BIS to a target BIS based on the BIG creation synchronization request.
The embodiment of the application provides synchronous equipment, which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so that the synchronous device executes the synchronous method.
The embodiment of the application provides a chip for realizing the synchronization method.
Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the above-mentioned synchronization method.
The embodiments of the present application provide a computer-readable storage medium storing a computer program which, when executed by a device, causes the device to perform the above-described synchronization method.
Embodiments of the present application provide a computer program product comprising computer program instructions for causing a computer to perform the above-described synchronization method.
The embodiments of the present application provide a computer program which, when run on a computer, causes the computer to perform the above-described synchronization method.
According to the embodiment of the application, the synchronized BIS is switched to the target BIS by the controller based on the BIG creation synchronization request, so that the power consumption of synchronous receiving can be reduced and the synchronous switching time can be shortened in the BIS synchronous switching process.
Drawings
Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
Fig. 2 is a flowchart of the synchronization receiver initiating the BIS handover.
Fig. 3 is a schematic diagram of determining BIS/BIG timing using periodic broadcasting.
Fig. 4 is a schematic flow chart of a synchronization method according to an embodiment of the present application.
Fig. 5 is a schematic flow chart of a synchronization method according to another embodiment of the present application.
Fig. 6 is a schematic diagram of a process in which the controller completes BIS switching in example 1.
Fig. 7 is a flow chart of BIS switching in example 1.
Fig. 8 is a schematic diagram of a process in which the controller completes BIS switching in example 2.
Fig. 9 is a flow chart of BIS switching in example 2.
Fig. 10 is a schematic block diagram of a synchronization device according to an embodiment of the present application.
Fig. 11 is a schematic block diagram of a synchronization device according to another embodiment of the present application.
Fig. 12 is a schematic block diagram of a synchronization device according to another embodiment of the present application.
Fig. 13 is a schematic block diagram of a synchronization device according to another embodiment of the present application.
Fig. 14 is a schematic block diagram of a communication device according to an embodiment of the present application.
Fig. 15 is a schematic block diagram of a chip according to an embodiment of the present application.
Fig. 16 is a schematic block diagram of a communication system according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.
In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.
In BLE scenarios, BIG may be carried in bluetooth periodic broadcast (Periodic Advertising, PA). It is necessary to start the periodic broadcast before the BIG. The broadcast synchronizer (e.g., a synchronous broadcaster and/or synchronous receiver) also synchronizes to the bluetooth periodic broadcast first and then resynchronizes to the BIG/BIS via the periodic broadcast when synchronizing the BIG. For example, one BIG may contain a maximum of 31 BISs, each BIS may be used to deliver a corresponding audio stream, and BIG/BIS may provide a completely new audio broadcasting function for Bluetooth. As shown in fig. 1, the Master (Master) device activates a BIG comprising two BIS that transmit the left and right channels of audio, respectively. Two Slave (Slave) devices may synchronize to the BIG/BIS simultaneously, receiving the audio stream in the BIS.
In general, a broadcast transmitter may be referred to as a synchronous broadcaster (Isochronous Broadcaster) (or broadcast transmitter), and a broadcast synchronous receiver may be referred to as a synchronous receiver (Synchronized Receiver) (or synchronous receiver, synchronous broadcast receiver, etc.).
A typical application scenario for bluetooth broadcast audio is the support of multi-lingual audio streaming. For example, assume that one BIG contains 4 BIS. Wherein BIS1 and BIS2 respectively transmit left and right channels of Spanish (span), and BIS3 and BIS4 respectively transmit left and right channels of English (englist). The user may have a need to switch languages while enjoying audio. For example by switching from span to engish. At this time, BIS, which requires synchronization of the bluetooth headset device (i.e., synchronized Receiver) of the user, is switched from BIS1 and BIS2 to BIS3 and BIS4.
In one example, synchronization of BIS may be initiated by a Low Energy (LE) BIG creation synchronization command (Create Sync command), by which the number of BIS to be synchronized and the target BIS Index (Index) may be specified by Num_BIS and BIS [ i ].
See table 1 for an example of creating a synchronization command (Create Sync command) for a LEBIG:
TABLE 1
Figure PCTCN2021073163-APPB-000001
If the host issues a command with an allocated bit Handle, the controller returns an error code: command (Command Disallowed (0 x 0C)) is not allowed.
Since Synchronized Receiver, when the BIS synchronization switch is initiated, it is necessary to terminate the synchronization of the current BIS and then re-initiate the synchronization of the new target BIS. Fig. 2 is a flow chart of the initiation of BIS switching by the synchronization receiver (Synchronized Receiver). The synchronous receiver may include a Host (Host) and a Controller (Controller). The host may include an application Layer and the controller may include a Link Layer (LL). Specifically, the BIS switching process may include:
s11, a synchronous broadcaster (Isochronous Broadcaster) starts periodic broadcasting (StartPA).
S12. the synchronized broadcaster (Isochronous Broadcaster) initiates BIG (Start BIG) association with the periodic broadcast. For example: the activated BIGs include BIS1, BIS2, BIS 3 and BIS 4.
S13, the synchronous receiver host (Synchronized Receiver Host) sends a scanning (Scan) PA instruction to the controller, and the controller executes scanning.
S14, a synchronous receiver controller (Synchronized Receiver Controller) receives periodic broadcasts from a synchronous broadcaster. For example, the ACAD in the periodic broadcast aux_sync_ind carries BIG information (BIG info) (aux_sync_ IND ACAD with BIGInfo).
S15, the synchronous receiver host sends an LE BIG creation synchronous command (Create Sync cmd) to the synchronous receiver controller so that the synchronous receiver is synchronized to BIS1/BIS2 (Sync to BIS1/BIS 2).
In this way it is achieved that the synchronization receiver scans to the synchronization broadcaster PA (Sync to PA) and synchronizes to BIS (Sync with BIG) e.g. BIS1/BIS2 by means of the PA.
S16. BIS handover may be initiated by the synchronous receiver host.
S17, the synchronous receiver host sends an LE BIG stop synchronous command to the synchronous receiver controller (Terminate Sync cmd).
S18. the synchronous receiver controller returns a host controller interface (Host Controller interface, HCI) command complete event (Command Complete event) to the synchronous receiver host. In this case, the synchronous receiver stops synchronizing to BIS1/BIS2.
If the synchronization receiver has stopped PA synchronization with the synchronization broadcaster, S19 and S20 may be performed, again synchronizing to the PA. S21 may be performed if the synchronization receiver does not stop PA synchronization with the synchronization broadcaster.
S19, the synchronous receiver host scans the PA.
S20, the synchronous receiver controller receives periodic broadcasting from the synchronous broadcaster. Such as periodic broadcast: the ACAD in AUX_SYNC_IND carries BIGInfo.
S21. the Sync receiver host sends an LE BIG Create Sync command (Create Sync cmd) to the Sync receiver controller to synchronize the Sync receiver to BIS3/BIS4 (Sync to BIS3/BIS 4).
In this way it is achieved that the synchronization receiver scans again to the synchronization broadcaster PA (Sync to PA) and synchronizes with the BIG, e.g. BIS3/BIS4, by means of the PA.
As shown in fig. 3, the timing of BIG/BIS can be obtained by BIG fo carried in a periodic broadcast. For example, by periodically broadcasting BIGInfo carried by ACAD in AUX_SYNC_IND, BIG event (event) x+1 for the next period of BIG event x can be determined. BIGInfo may include BIG Offset (BIG_Offset), BIG Anchor Point (BIG Anchor Point), and the like. For example, the Offset Unit (Offset Unit) may be 30 μs (microseconds) or 300 μs. The BIG anchor is after a time indicated by BIG Offset (Time indicated by BIG _offset). The BIG anchor may be the starting point of BIG 1 in BIG event x+1. In addition, BIGInfo may further include information such as BIS interval (BIS_spacing) and the like for determining BIS events such as BIS1 and BIS 2.
Referring to the flow of BIS switching, the synchronization receiver (Synchronized Receiver) device needs to terminate the BIS currently having established synchronization before switching the BIS, and then re-synchronize the new BIS. This process requires the periodic broadcast of Synchronized Receiver and Isochronous Broadcaster devices to remain synchronized, resulting in wasted power consumption by the Receiver device. And, the Synchronized Receiver device, if stopping the synchronization with the periodic broadcast of the Isochronous Broadcaster device, then re-scans and synchronizes to the periodic broadcast of the broadmaster device and then to the new BIS. The process of scanning for synchronized periodic broadcasts is a relatively time consuming process, resulting in long BIS switching times and poor user experience.
Fig. 4 is a schematic flow chart diagram of a synchronization method 200 according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.
S210, the controller creates a synchronization request based on the broadcast synchronization group BIG, and switches the synchronized broadcast synchronization stream BIS to a target BIS.
The controller may be, for example, a controller of a synchronous receiver, see fig. 2. The controller may switch the synchronized broadcast synchronization stream BIS to the target BIS based on a BIG creation synchronization request from the host of the synchronization receiver. Wherein the synchronized broadcast synchronization stream BIS may comprise one or more BIS in one BIG, and in particular may comprise one or more BIS with which the synchronization receiver is synchronized with the synchronization broadcaster. The target BIS may also comprise one or more BIS, and in particular may comprise BIS that need to be switched to be synchronized with the synchronization receiver.
Optionally, the method further comprises: the controller receives the BIG creation synchronization request from a host.
Illustratively, the user may initiate a BIS switch by synchronizing the hosts of the receivers. The host sends a BIG create synchronization request to the controller. When the controller receives a BIG creation synchronization request from the host, the synchronized broadcast synchronization stream BIS is switched to a target BIS.
Optionally, the BIG creation synchronization request includes a BIG Handle big_handle, and the method further includes:
in the case where the BIG Handle has been used by the create BIG command, the controller returns an error message to the host.
Illustratively, the BIG_Handle included in the BIG creation synchronization request may be used by a create BIG command, such as LE Create BIG command. LE Create BIG command is a command used by the synchronized broadcaster to create a BIG. If a particular synchronous broadcaster has created a BIG using the BIG Handle, the synchronous receiver requests to continue to use the same BIG Handle to synchronize the BIG created by other synchronous broadcasters, the synchronous receiver controller returns an error message to the synchronous receiver host.
Optionally, the BIG creation synchronization request further includes target BIS information, and the controller switches the synchronized BIS to the target BIS based on the BIG creation synchronization request, including:
in the case where the BIG_Handle is not used by the create BIG command, the controller switches the synchronized BIS to the target BIS based on a BIG create synchronization request.
Optionally, the target BIS information includes: number of target BIS and/or parameter description.
For example, the number of target BIS included in the target BIS information may be N, and the parameter descriptions of the N BIS may be further included in the target BIS information.
Optionally, the controller creates the synchronization request based on the BIG, switches the synchronized BIG to the target BIG, and includes:
the controller obtains a target BIS set based on target BIS information included in the BIG creation synchronization request;
the controller obtains a first BIS set and a second BIS set based on the target BIS set and the synchronized BIS set; wherein the first BIS-set includes BIS-information present in the target BIS-set but not in the synchronized BIS-set, and the second BIS-set includes BIS-information present in the synchronized BIS-set but not in the target BIS-set;
the controller stops synchronizing the BIS identified by the BIS information of the second BIS set and starts to establish synchronization with the BIS identified by the BIS information of the first BIS set.
In the first mode, the controller may trigger a new switching logic based on the BIG creation synchronization request, and compare the BIS to be synchronized with the BIS to be synchronized, thereby completing BIS switching.
Illustratively, the BIS information included in the synchronized BIS sets of the synchronized receiver and the synchronized broadcaster are BIS1 and BIS2. The target BIS information included in the BIG creation synchronization request is BIS3 and BIS4, and the target BIS set includes BIS3 and BIS4. The controller compares the synchronized BIS set with the target BIS set, records BIS information BIS3 and BIS4 existing in the target BIS set but not in the synchronized BIS set into the first BIS set, and records BIS information BIS1 and BIS2 existing in the synchronized BIS set but not in the target BIS set into the second BIS set. Then, the controller stops synchronizing the BIS1 and BIS2 of the synchronized broadcasters in the second BIS set and starts to establish synchronization with the BIS3 and BIS4 of the synchronized broadcasters in the first BIS set.
Illustratively, the BIS information included in the synchronized BIS sets of the synchronized receiver and the synchronized broadcaster are BIS1, BIS2, and BIS3. The target BIS information included in the BIG creation synchronization request is BIS3, BIS4, BIS5, and BIS6. The controller compares the synchronized BIS set with the target BIS set, records BIS information BIS4, BIS5, and BIS6 existing in the target BIS set but not in the synchronized BIS set into the first BIS set, and records BIS information BIS1 and BIS2 existing in the synchronized BIS set but not in the target BIS set into the second BIS set. Then, the controller stops synchronizing the BIS1 and BIS2 of the synchronized broadcasters in the second BIS set and starts to establish synchronization with the BIS4, BIS5 and BIS6 of the synchronized broadcasters in the first BIS set.
Optionally, the BIG creation synchronization request further includes BIS information needed to stop synchronization.
Optionally, the BIS information requiring synchronization stop includes the number of BIS requiring synchronization stop and/or a parameter description.
Optionally, the controller creates the synchronization request based on the BIG, switches the synchronized BIG to the target BIG, and includes: the controller stops synchronizing the BIS identified by the BIS information requiring the synchronization stop and starts to establish synchronization for the BIS identified based on the target BIS information.
In the second mode, the controller may stop synchronizing the BIS identified by the BIS information to be synchronized included in the BIS creation synchronization request, and establish synchronization with the BIS identified by the target BIS information included in the BIS creation synchronization request, thereby completing BIS switching.
Optionally, the BIG creation synchronization request creates a synchronization command for a low power LE BIG.
Illustratively, in mode one, the BIG creation synchronization request may create a synchronization command for the LE BIG (LE BIG Create Sync command), or an enhanced LE BIG creation synchronization command (Enhanced LE BIG Create Sync command). For example, hci_le_big_create_sync. Creating a synchronous command based on the LE BIG or an enhanced LE BIG creates a synchronous command to change the switching logic of the controller. In the new switching logic, the controller can compare the BIS information needing to stop synchronization with the BIS information needing to establish synchronization, and then complete BIS switching.
Optionally, the BIG creation synchronization request creates a synchronization command for an LE BIG including BIS information requiring synchronization to be stopped.
Illustratively, in mode two, the BIG create sync request may create a modified version of the sync command for the LE BIG (LE BIG Create Sync command V). For example hci_le_big_create_sync_v2. Parameters related to BIS information requiring synchronization stop, such as the number of BIS requiring synchronization stop and a description of parameters of BIS requiring synchronization stop, may be newly added to the modified version of the LE BIG create synchronization command. The switching logic of the controller may be changed to complete the BIS switching based on the number of BIS requiring the synchronization to be stopped and the parameter description of the BIS requiring the synchronization to be stopped.
Optionally, the method further comprises:
the controller transmits a BIG synchronization result to the host, the BIG synchronization result including information of the BIS set which is out of synchronization.
Optionally, the information of the out-of-sync BIS set includes the number of out-of-sync BIS and/or the corresponding connection handle of the out-of-sync BIS.
Optionally, the BIG synchronization result is a Host Controller Interface (HCI) LE BIG synchronization establishment update event, and the HCI LE BIG synchronization establishment update event includes information of the out-of-sync BIS set.
Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-synchronization BIG set.
The manner in which the controller sends the BIG sync results to the host may include, for example, a variety of ways. One way is to modify the parameters in the HCI LE BIG synchronization setup event, and the modified version (HCI LE BIG Sync Established event v 2) of the HCI LE BIG synchronization setup event carries the information of the out-of-Sync BIS set, such as the number of out-of-Sync BIS and/or the connection handle corresponding to the out-of-Sync BIS, in the hci_le BIG sync_synchronized [ v2 ]. In another way, an HCI LE BIG synchronization establishment update event (LE BIG Sync Established update event) is newly added, and the information of the out-of-sync BIS set, such as the number of out-of-sync BIS and/or the connection handle corresponding to the out-of-sync BIS, is carried in the HCI LE BIG synchronization establishment update event.
Fig. 5 is a schematic flow chart diagram of a synchronization method 300 according to another embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.
And S310, the host sends a BIG creation synchronization request to the controller to instruct the controller to switch the synchronized BIS to a target BIS based on the BIG creation synchronization request.
Optionally, the BIG creation synchronization request includes a BIG Handle big_handle, and the method further includes: in the case where the BIG Handle has been used by the create BIG command, the host receives an error message from the controller.
Optionally, the BIG creation synchronization request further includes target BIS information.
Optionally, the target BIS information includes: number of target BIS and/or parameter description.
Optionally, the BIG creation synchronization request further includes BIS information needed to stop synchronization.
Optionally, the BIS information requiring synchronization stop includes the number of BIS requiring synchronization stop and/or a parameter description.
Optionally, the BIG creation synchronization request creates a synchronization command for a low power LE BIG.
Optionally, the BIG creation synchronization request creates a synchronization command for an LE BIG including BIS information requiring synchronization to be stopped.
Optionally, the method further comprises: the host receives a BIG synchronization result from the controller, the BIG synchronization result including information of the desynchronized BIS set.
Optionally, the information of the out-of-sync BIS set includes the number of out-of-sync BIS and/or the corresponding connection handle of the out-of-sync BIS.
Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment update event, where the HCI LE BIG synchronization establishment update event includes information of the out-of-synchronization BIS set.
Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-synchronization BIG set.
Specific examples of the method 300 for executing the host in this embodiment may be referred to the above description of the method 200 regarding the host of the synchronous receiver, and will not be repeated here for brevity.
The embodiment of the application provides a BLE BIS-based synchronization method, which can enhance LE BIG creation synchronization command (Create Sync command) so that equipment does not need to terminate BIG/BIS synchronization when the equipment is synchronized to BIG/BIS, and can directly complete synchronization switching of new BIS.
Example 1:
1. the enhanced LE BIG creates a synchronous command (Create Sync command). For example, an enhanced LE BIG Create synchronous command (Enhanced LE BIG Create Sync command) is set:
(1) Causing the controller to check the BIG Handle upon receipt of the command, and return an error code (error code) if the BIG Handle has been used by LE Create BIG command: invalid HCI command parameters (INVALID HCI COMMAND PARAMETERS) (0 x 12);
the controller checks the num_bis, BIS (es) described by the BIS [ i ] parameter:
num_bis, BIS [ i ] parameter description BIS Set is labeled bis_set_req,
the controller marks the BIS Set for which synchronization has been established currently exists as bis_set_synchronized, and may perform the steps of:
(a) If the BIS of the two sets are identical or BIS_set_req is contained in BIS_set_synchronized, the Controller returns an error code (error code): commands (Command Disallowed) that are not allowed (0 x 0C);
(b) If the BIS of the two sets is not the same:
the BIS Set that exists in BIS_set_req but does not exist in BIS_set_synchronized is marked as BIS_set_a;
the BIS Set that exists in BIS_set_synchronized but does not exist in BIS_set_req is marked as BIS_set_b;
the controller terminates synchronization of the BIS (if any) contained in the BIS Set b Set and starts to establish synchronization with the BIS contained in the BIS Set a Set.
2. Newly added LE BIG synchronization setup update event (Sync Established update event) or LE BIG step setup version v2 of event (HCI_LE_BIG_Sync_published [ v2 ]), the parameters in the event can be seen in Table 2:
TABLE 2
Figure PCTCN2021073163-APPB-000002
In the above table, num_bis_ Lost, connection _handle_lost [ i ] represents a set of BIS that are out of synchronization. Wherein num_bis_lost is the number of BIS out of sync, connection_handle_lost [ i ] is an array of Connection handles (Connection Handle), indicating the Connection handles corresponding to BIS out of sync.
Fig. 6 is a schematic diagram of a process of performing BIS switching by the controller, where the BIG includes two BISs. If the controller of the synchronous receiver is in sync with BIS1 and the controller starts BIS switching upon receipt of the enhanced LE BIG create sync command. In this example, it is from BIS1 to BIS2. Specifically, the anchor point of the BIS event of the next period x+1 of x may be determined based on the ISO interval. The controller creates a synchronization command (Enhanced LE BIG Create Sync command) in terms of enhanced LE BIG based on BIG Anchor (Anchor Point): the hci_le_big_create_sync performs BIS switching. After the controller performs the synchronization switching, the controller returns to the HCI LE BIG synchronization establishment event (hci_le_big_sync_ Established event) version v 2: HCI_LE_BIG_Sync_Established [ v2] to the host.
As shown in fig. 7, the overall flow of BIS switching includes:
s31, the synchronous broadcaster (Isochronous Broadcaster) starts periodic broadcasting (Start PA).
S32. the synchronized broadcaster enables BIG (Start BIG) to associate with the periodic broadcast. For example, 4 BIS are started: BIS1, BIS2, BIS3 and BIS4.
S33. the synchronous receiver host (Synchronized Receiver Host) sends an instruction to Scan (Scan) PA to the synchronous receiver controller, which performs the Scan.
S34, a synchronous receiver controller (Synchronized Receiver Controller) receives the periodic broadcast from the synchronous broadcaster. The ACAD in the periodic broadcast AUX_SYNC_IND carries BIG information (AUX_SYNC_ INDACAD with BIGInfo), for example.
S35, the host sends an enhanced LE BIG creation synchronization command to the controller, wherein the enhanced LE BIG creation synchronization command can carry: num_BIS 2, [ BIS1, BIS2] and the like. Num_bis:2 denotes that the number of BIS is2, [ BIS1, BIS2] denotes the parameter descriptions of BIS1 and BIS2 that need to establish synchronization.
Thus, the synchronization receiver (Synchronized Receiver) scans to the PA of the synchronization broadcaster and synchronizes to BIS (Sync with BIG) by means of the PA, for example: BIS1/BIS2.
S36, the application initiates a BIS switching request.
S37, the synchronous receiver host sends Enhanced LE BIG Create Sync command information which can include BIS3/BIS4 to the synchronous receiver controller. For example, the command may carry: num_BIS 2, [ BIS3, BIS4] and the like. Num_bis:2 denotes that the number of BIS is2, [ BIS3, BIS4] denotes the parameter descriptions of BIS1 and BIS2 that need to establish synchronization.
S38, after receiving the command, the controller processes according to the description of the command. For example, the synchronization of BIS1/BIS2 is stopped and the synchronization to BIS3/BIS4 is started.
Note that: the BIS switching can be performed according to the process diagram of the controller for performing BIS switching, i.e., fig. 6.
S39, the controller returns a v2 version (HCI_LE_BIG_Sync_estimated [ v2 ]) of the HCI LE BIG step establishment event to the host. The num_ BIS, connection _handle [ i ] included in this event is the set of BIS3/BIS4 for which synchronization is newly established, and num_bis_ Lost, connection _handle_lost [ i ] is the set of BIS1/BIS2 for which synchronization is stopped.
Example 2:
this example applies to the case where the synchronization receiver (Synchronized Receiver) device continues to maintain a synchronized state with the periodic broadcast of the synchronization broadcaster (Isochronous Broadcaster) device after synchronization is established with the BIG/BIS.
1. The newly added LE BIG creates a synchronization command (Create Sync command) version v 2:
(1) In this command, the num_bis_lost, bis_lost [ i ] parameter is newly added, indicating the set of BIS that the Host (Host) requests the Controller (Controller) to stop synchronization. See table 3.
TABLE 3 Table 3
Figure PCTCN2021073163-APPB-000003
Based on the parameters in the table, the controller, upon receipt of the command, checks the BIG Handle (big_handle), and if the big_handle has been used by the LE create BIG command (Create BIG command), the controller returns an HCI command parameter (INVALID HCI COMMAND PARAMETERS) with invalid error code (error code) (0 x 12);
The controller performs synchronization stopping on BIS information: the BIS information to be synchronized is obtained by stopping synchronization of a plurality of BISs represented by Num_BIS_Lost and BIS_Lost [ i ] parameters: the num_bis, BIS [ i ] parameters represent a plurality of BIS initiated syncs.
In addition, an LE BIG synchronization establishment update event (Sync Established update event) or an LE BIG synchronization establishment event (Sync Established event) version v2 (HCI_LE_BIG_Sync_established [ v2 ]). The parameters in the event may be referred to in table 2 in example 1, and are not described here. In Table 2, num_BIS_ Lost, connection _handle_Lost [ i ] represents the set of BIS that is out of sync. Wherein num_bis_lost is the number of BIS out of sync, connection_handle_lost [ i ] is an array of Connection handles (Connection Handle), indicating the Connection handles corresponding to BIS out of sync.
Fig. 8 is a schematic diagram of a process of performing BIS switching by the controller, where the BIG includes two BISs. If the controller of the synchronous receiver is in sync with BIS1 and the controller starts BIS switching upon receipt of the enhanced LE BIG create sync command. In this example, it is from BIS1 to BIS2. Specifically, the anchor point of the BIS event of the next period x+1 of x may be determined based on the ISO interval. The controller creates a synchronization command (Enhanced LE BIG Create Sync command) v2 version in terms of enhanced LE BIG based on BIG Anchor (Anchor Point): the HCI_LE_BIG_Create_Sync [ v2] performs BIS switching. After the controller performs the synchronization switching, the controller returns to the HCI LE BIG synchronization establishment event (hci_le_big_sync_ Established event) version v 2: HCI_LE_BIG_Sync_Established [ v2] to the host.
As shown in fig. 7, the overall flow of BIS switching includes: the BIS switching flow scheme may include:
s41. the synchronous broadcaster (Isochronous Broadcaster) starts periodic broadcast (Start PA).
S42, enabling the BIG to be associated with the periodical broadcasting by the synchronous broadcaster. For example, 4 BIS are started: BIS1, BIS2, BIS3 and BIS4.
S43. the synchronous receiver host (Synchronized Receiver Host) sends an instruction to the synchronous receiver controller to Scan (Scan) PA, and the synchronous receiver controller performs the Scan.
S44. a synchronous receiver controller (Synchronized Receiver Controller) receives the periodic broadcast from the synchronous broadcaster. The ACAD in the periodic broadcast AUX_SYNC_IND carries BIG information (AUX_SYNC_ INDACAD with BIGInfo), for example.
S45. the host sends an enhanced LE BIG creation synchronization command or LE BIG creation synchronization command v2 version (hci_le_big_create_sync [ v2 ]) to the controller. Wherein it can carry: num_BIS 2, [ BIS1, BIS2] and the like. Num_bis:2 denotes that the number of BIS is2, [ BIS1, BIS2] denotes the parameter descriptions of BIS1 and BIS2 that need to establish synchronization.
Thus, the synchronization receiver (Synchronized Receiver) scans to the PA of the synchronization broadcaster and synchronizes to BIS (Sync with BIG) by means of the PA, for example: BIS1/BIS2.
S46, the application initiates BIS switching request transmission.
S47, the synchronous receiver host transmits HCI_LE_ BIG Create Sync command [ v2] carrying parameters Num_BIS 2, [ BIS3/BIS4], num_BIS 2, [ BIS1/BIS2] to the synchronous receiver controller.
S48, after receiving the command, the controller processes, for example, stopping synchronizing BIS1/BIS2 and starting synchronizing to BIS3/BIS4 according to the description of the command.
In this example, the BIS switching may be performed according to a process diagram of the controller performing the BIS switching, i.e., fig. 8.
S49, the controller returns a v2 version (HCI_LE_BIG_Sync_estimated [ v2 ]) of the HCI LE BIG step establishment event to the host. The num_ BIS, connection _handle [ i ] included in this event is the set of BIS3/BIS4 for which synchronization is newly established, and num_bis_ Lost, connection _handle_lost [ i ] is the set of BIS1/BIS2 for which synchronization is stopped.
According to the embodiment of the application, the synchronous receiver (Synchronized Receiver) equipment is supported to directly complete the switching between different BISs under the condition of keeping synchronization with the BIG/BIS, so that the time for initiating BIS switching by a Host (Host) is shortened, the user experience is enhanced, and the delay of switching different audio frequencies is shortened. And Synchronized Receiver equipment can terminate synchronization of periodic broadcast after synchronizing with BIG/BIS, and BIS switching process does not depend on periodic broadcast, so that power consumption of Synchronized Receiver equipment is effectively reduced, and service time of the equipment can be prolonged.
Fig. 10 is a schematic block diagram of a synchronization device 400 according to an embodiment of the present application. The synchronization device 400 may include:
a control unit 410 for creating a synchronization request based on the broadcast synchronization group BIS, and switching the synchronized broadcast synchronization stream BIS to the target BIS.
Optionally, as shown in fig. 11, the synchronization device further includes: a receiving unit 420, configured to receive the BIG creation synchronization request from the host.
Optionally, the BIG creation synchronization request includes a BIG Handle big_handle, and the synchronization device further includes: a first sending unit 430, configured to return an error message to the host in a case where the big_handle is used by the create BIG command.
Optionally, the BIG creation synchronization request further includes target BIS information, the controller switches the synchronized BIS to the target BIS based on the BIG creation synchronization request, and the control unit is further configured to switch the synchronized BIS to the target BIS based on the BIG creation synchronization request if the BIG_handle is not used by the BIG creation command.
Optionally, the target BIS information includes: number of target BIS and/or parameter description.
Optionally, the control unit is further configured to:
creating target BIS information included in the synchronous request based on the BIG to obtain a target BIS set;
Obtaining a first BIS set and a second BIS set based on the target BIS set and the synchronized BIS set; wherein the first BIS-set includes BIS-information present in the target BIS-set but not in the synchronized BIS-set, and the second BIS-set includes BIS-information present in the synchronized BIS-set but not in the target BIS-set;
stopping synchronizing the BIS identified by the BIS information of the second BIS set and starting to establish synchronization with the BIS identified by the BIS information of the first BIS set.
Optionally, the BIG creation synchronization request further includes BIS information needed to stop synchronization.
Optionally, the BIS information requiring synchronization stop includes the number of BIS requiring synchronization stop and/or a parameter description.
Optionally, the control unit is further configured to stop synchronizing the BIS identified by the BIS information to be stopped, and start to establish synchronization for the BIS identified based on the target BIS information.
Optionally, the BIG creation synchronization request creates a synchronization command for a low power LE BIG.
Optionally, the BIG creation synchronization request creates a synchronization command for an LE BIG including BIS information requiring synchronization to be stopped.
Optionally, the synchronization device further includes: and a second transmitting unit 440 for transmitting a BIG synchronization result to the host, the BIG synchronization result including information of the BIG set that is out of synchronization.
Optionally, the information of the out-of-sync BIS set includes the number of out-of-sync BIS and/or the corresponding connection handle of the out-of-sync BIS.
Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment update event of the host controller interface, where the HCI LE BIG synchronization establishment update event includes information of the out-of-synchronization BIS set.
Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-synchronization BIG set.
The synchronization device 400 of the embodiment of the present application can implement the corresponding function of the controller of the synchronization receiver in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the synchronization device 400 can be referred to the corresponding description in the above method embodiments, and will not be repeated here. It should be noted that, the functions described in each module (sub-module, unit, or component, etc.) in the synchronization apparatus 400 of the application embodiment may be implemented by different modules (sub-module, unit, or component, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.).
Fig. 12 is a schematic block diagram of a synchronization device 500 according to another embodiment of the present application. The synchronization device 500 may include:
a transmitting unit 510 for transmitting a BIG creation synchronization request to the controller to instruct the controller to switch the synchronized BIS to a target BIS based on the BIG creation synchronization request.
Optionally, the BIG creation synchronization request includes a BIG Handle big_handle, as shown in fig. 13, and the synchronization device further includes: a first receiving unit 520 for receiving error information from the controller in case the big_handle has been used by the create BIG command.
Optionally, the BIG creation synchronization request further includes target BIS information.
Optionally, the target BIS information includes: number of target BIS and/or parameter description.
Optionally, the BIG creation synchronization request further includes BIS information needed to stop synchronization.
Optionally, the BIS information requiring synchronization stop includes the number of BIS requiring synchronization stop and/or a parameter description.
Optionally, the BIG creation synchronization request creates a synchronization command for a low power LE BIG.
Optionally, the BIG creation synchronization request creates a synchronization command for an LE BIG including BIS information requiring synchronization to be stopped.
Optionally, the synchronization device further includes: a second receiving unit 530 for receiving a BIG synchronization result from the controller, the BIG synchronization result including information of the BIG set that is out of synchronization.
Optionally, the information of the out-of-sync BIS set includes the number of out-of-sync BIS and/or the corresponding connection handle of the out-of-sync BIS.
Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment update event, where the HCI LE BIG synchronization establishment update event includes information of the out-of-synchronization BIS set.
Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-synchronization BIG set.
The synchronization device 500 of the embodiment of the present application can implement the corresponding function of the host of the synchronization receiver in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the synchronization device 500 can be referred to the corresponding description in the above method embodiments, and will not be repeated here. It should be noted that, the functions described in each module (sub-module, unit, or component, etc.) in the synchronization apparatus 500 of the application embodiment may be implemented by different modules (sub-module, unit, or component, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.).
Fig. 14 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 comprises a processor 610, which processor 610 may call and run a computer program from a memory to cause the communication device 600 to implement the methods in embodiments of the present application.
Optionally, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may invoke and run a computer program from the memory 620 to cause the communication device 600 to implement the method in the embodiments of the present application.
The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.
Optionally, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.
Optionally, the communication device 600 may be a host in the embodiments of the present application, and the communication device 600 may implement corresponding processes implemented by the host in the methods in the embodiments of the present application, which are not described herein for brevity.
Optionally, the communication device 600 may be a controller in the embodiments of the present application, and the communication device 600 may implement a corresponding flow implemented by the controller in each method in the embodiments of the present application, which is not described herein for brevity.
Fig. 15 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the methods of the embodiments of the present application.
Optionally, chip 700 may also include memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the methods performed by the controller or host in the embodiments of the present application.
Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.
Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.
Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.
Optionally, the chip may be applied to the host in the embodiments of the present application, and the chip may implement a corresponding flow implemented by the host in each method in the embodiments of the present application, which is not described herein for brevity.
Optionally, the chip may be applied to the controller in the embodiments of the present application, and the chip may implement a corresponding flow implemented by the controller in each method in the embodiments of the present application, which is not described herein for brevity.
The chips applied to the host and the controller may be the same chip or different chips.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
The processors mentioned above may be general purpose processors, digital signal processors (digital signal processor, DSP), off-the-shelf programmable gate arrays (field programmable gate array, FPGA), application specific integrated circuits (application specific integrated circuit, ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor.
The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).
It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
Fig. 16 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a controller 810 and a host 820.
And a controller 810 for switching the synchronized broadcast synchronization stream BIS to the target BIS based on the BIG creation synchronization request.
And a host 820 for transmitting a BIG creation synchronization request to the controller to instruct the controller to switch the synchronized BIS to a target BIS based on the BIG creation synchronization request.
Wherein the controller 810 may be used to implement the corresponding functions implemented by the controller in the above-described method, and the host 820 may be used to implement the corresponding functions implemented by the host in the above-described method. For brevity, the description is omitted here.
Alternatively, the controller 810 and the host 820 may be provided in the same synchronization device, e.g., a synchronization receiver.
Optionally, the system may further include: and the synchronous broadcaster establishes synchronization with a host of the synchronous receiver through a controller of the synchronous receiver.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part 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, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may 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 may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), or the like.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (64)

  1. A synchronization method, comprising:
    the controller creates a synchronization request based on the broadcast synchronization group BIGs, and switches the synchronized broadcast synchronization stream BIS to the target BIS.
  2. The method of claim 1, wherein the method further comprises:
    the controller receives the BIG creation synchronization request from a host.
  3. The method of claim 1 or 2, wherein the BIG creation synchronization request includes a BIG Handle, the method further comprising:
    in the case where the BIG Handle has been used by the create BIG command, the controller returns an error message to the host.
  4. The method of claim 3, wherein the BIG creation synchronization request further includes target BIS information, and the controller switches the synchronized BIS to the target BIS based on the BIG creation synchronization request, comprising:
    in the case where the BIG_Handle is not used by the create BIG command, the controller switches the synchronized BIS to the target BIS based on a BIG create synchronization request.
  5. The method of claim 4, wherein the target BIS information comprises: number of target BIS and/or parameter description.
  6. The method of any one of claims 1 to 5, wherein the controller creating a synchronization request based on the BIG, switching the synchronized BIS to the target BIS, comprises:
    the controller obtains a target BIS set based on target BIS information included in the BIG creation synchronization request;
    the controller obtains a first BIS set and a second BIS set based on the target BIS set and the synchronized BIS set; wherein the first BIS-set includes BIS-information present in the target BIS-set but not in the synchronized BIS-set, and the second BIS-set includes BIS-information present in the synchronized BIS-set but not in the target BIS-set;
    The controller stops synchronizing the BIS identified by the BIS information of the second BIS set and starts to establish synchronization with the BIS identified by the BIS information of the first BIS set.
  7. The method of any one of claims 1 to 5, wherein the BIG creation synchronization request further includes BIS information that needs to stop synchronization.
  8. The method of claim 7, wherein the BIS information requiring synchronization stop includes a number and/or a parameter description of BIS requiring synchronization stop.
  9. The method of claim 7 or 8, wherein the controller switches the synchronized BIS to the target BIS based on the BIG creation synchronization request, comprising:
    the controller stops synchronizing the BIS identified by the BIS information requiring the synchronization stop and starts to establish synchronization for the BIS identified based on the target BIS information.
  10. The method according to any of claims 1 to 6, wherein the BIG create synchronization request creates a synchronization command for a low power LE BIG.
  11. The method of any of claims 1 to 5, 7 to 9, wherein the BIG creation synchronization request creates a synchronization command for an LE BIG comprising BIS information that needs to stop synchronization.
  12. The method of any one of claims 1 to 11, wherein the method further comprises:
    the controller transmits a BIG synchronization result to the host, the BIG synchronization result including information of the BIS set which is out of synchronization.
  13. The method of claim 12, wherein the information of the out-of-sync BIS set comprises the number of out-of-sync BIS and/or the connection handle corresponding to the out-of-sync BIS.
  14. A method according to claim 12 or 13, wherein the BIG sync result is a host controller interface, HCI LE BIG sync setup update event, comprising information of the out of sync BIS set.
  15. The method according to claim 12 or 13, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment event comprising information of the out-of-synchronization BIS set.
  16. A synchronization method, comprising:
    the host transmits a BIG creation synchronization request to the controller to instruct the controller to switch the synchronized BIS to a target BIS based on the BIG creation synchronization request.
  17. The method of claim 16, wherein the BIG creation synchronization request includes a BIG Handle, the method further comprising:
    In the case where the BIG Handle has been used by the create BIG command, the host receives an error message from the controller.
  18. The method of claim 16 or 17, wherein the BIG creation synchronization request further includes target BIS information.
  19. The method of claim 18, wherein the target BIS information comprises: number of target BIS and/or parameter description.
  20. The method of any of claims 16 to 19, wherein the BIG creation synchronization request further includes BIS information that needs to stop synchronization.
  21. The method of claim 20, wherein the BIS information requiring synchronization stop includes a number of BIS requiring synchronization stop and/or a parameter description.
  22. The method according to any of claims 16 to 19, wherein the BIG create synchronization request creates a synchronization command for a low power LE BIG.
  23. A method according to any one of claims 16 to 22, wherein the BIG creation synchronization request creates a synchronization command for an LE BIG comprising BIS information that needs to cease synchronization.
  24. The method of any one of claims 16 to 23, wherein the method further comprises:
    the host receives a BIG synchronization result from the controller, the BIG synchronization result including information of the out-of-sync BIS set.
  25. The method of claim 24, wherein the information of the out-of-sync BIS set comprises the number of out-of-sync BIS and/or the connection handle corresponding to the out-of-sync BIS.
  26. The method according to claim 24 or 25, wherein the BIG sync result is an HCI LE BIG sync setup update event comprising information of the out-of-sync BIS set.
  27. The method of claim 24 or 25, wherein the BIG synchronization result is an HCI LE BIG synchronization setup event comprising information of the out-of-synchronization BIS set.
  28. A synchronization apparatus, comprising:
    and a control unit for creating a synchronization request based on the broadcast synchronization group BIG, and switching the synchronized broadcast synchronization stream BIS to the target BIS.
  29. The synchronization device of claim 28, wherein the synchronization device further comprises:
    and the receiving unit is used for receiving the BIG creation synchronization request from the host.
  30. The synchronization device of claim 28 or 29, wherein the BIG creation synchronization request includes a BIG Handle, the synchronization device further comprising: and the first sending unit is used for returning error information to the host computer under the condition that the BIG_handle is used by the BIG command.
  31. The synchronization apparatus of claim 30, wherein the BIG creation synchronization request further includes target BIS information, the controller switches the synchronized BIS to the target BIS based on the BIG creation synchronization request, and the control unit is further configured to switch the synchronized BIS to the target BIS based on the BIG creation synchronization request in a case that the BIG_handle is not used by the create BIG command.
  32. The synchronization device of claim 31, wherein the target BIS information comprises: number of target BIS and/or parameter description.
  33. The synchronization device according to any one of claims 28 to 32, wherein the control unit is further configured to:
    creating target BIS information included in the synchronous request based on the BIG to obtain a target BIS set;
    obtaining a first BIS set and a second BIS set based on the target BIS set and the synchronized BIS set; wherein the first BIS-set includes BIS-information present in the target BIS-set but not in the synchronized BIS-set, and the second BIS-set includes BIS-information present in the synchronized BIS-set but not in the target BIS-set;
    stopping synchronizing the BIS identified by the BIS information of the second BIS set and starting to establish synchronization with the BIS identified by the BIS information of the first BIS set.
  34. The synchronization device of any one of claims 28 to 32, wherein the BIG creation synchronization request further includes BIS information that needs to stop synchronization.
  35. The synchronization apparatus of claim 34, wherein the BIS information requiring synchronization stop includes a number of BIS requiring synchronization stop and/or a parameter description.
  36. The synchronization apparatus as claimed in claim 34 or 35, wherein the control unit is further for stopping synchronization of the BIS identified by the BIS information requiring synchronization stopping, and starting synchronization establishment of the BIS identified based on the target BIS information.
  37. A synchronization device according to any one of claims 28 to 33, wherein the BIG create synchronization request creates a synchronization command for a low power LE BIG.
  38. The synchronization device of any one of claims 28 to 32, 34 to 36, wherein the BIG creation synchronization request creates a synchronization command for an LE BIG comprising BIS information that needs to stop synchronization.
  39. The synchronization device of any one of claims 28 to 38, wherein the synchronization device further comprises: and a second transmitting unit for transmitting a BIG synchronization result to the host, wherein the BIG synchronization result comprises information of the BIS set which is out of synchronization.
  40. The synchronization device of claim 39, wherein the information of the out-of-synchronization BIS-set comprises a number of out-of-synchronization BIS-s and/or a connection handle corresponding to the out-of-synchronization BIS-s.
  41. A synchronization device as defined in claim 39 or 40, wherein the BIG synchronization result is a host controller interface HCI LE BIG synchronization setup update event comprising information of the out-of-sync BIS set.
  42. A synchronization device as claimed in claim 39 or 40, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment event comprising information of the out-of-synchronization BIS set.
  43. A synchronization apparatus, comprising:
    and a transmitting unit for transmitting a BIG creation synchronization request to a controller to instruct the controller to switch the synchronized BIS to a target BIS based on the BIG creation synchronization request.
  44. The synchronization device of claim 43, wherein the BIG creation synchronization request includes a BIG Handle BIG_Handle, the synchronization device further comprising: and a first receiving unit for receiving error information from the controller in case the big_handle has been used by the create BIG command.
  45. The synchronization apparatus of claim 43 or 44, wherein the BIG creation synchronization request further includes target BIS information.
  46. The synchronization device of claim 45, wherein the target BIS information comprises: number of target BIS and/or parameter description.
  47. The synchronization apparatus of any one of claims 43 to 46, wherein the BIG creation synchronization request further includes BIS information that needs to stop synchronization.
  48. The synchronization device of claim 47, wherein the BIS information requiring synchronization stop includes a number of BIS requiring synchronization stop and/or a parameter description.
  49. A synchronization device according to any one of claims 43 to 46, wherein the BIG create synchronization request creates a synchronization command for a low power LE BIG.
  50. A synchronization device according to any one of claims 43 to 49, wherein the BIG creation synchronization request creates a synchronization command for an LE BIG comprising BIS information that needs to cease synchronization.
  51. The synchronization device of any one of claims 43 to 50, wherein the synchronization device further comprises: and a second receiving unit for receiving a BIG synchronization result from the controller, the BIG synchronization result including information of the BIS set which is out of synchronization.
  52. The synchronization device of claim 51, wherein the information of the out-of-synchronization BIS-set comprises a number of out-of-synchronization BIS-s and/or a connection handle corresponding to the out-of-synchronization BIS-s.
  53. A synchronization device as claimed in claim 51 or 52, wherein the BIG synchronization result is an HCI LE BIG synchronization setup update event comprising information of the out-of-sync BIS set.
  54. The synchronization device of claim 51 or 52, wherein the BIG synchronization result is an HCI LE BIG synchronization setup event comprising information of the out-of-synchronization BIS set.
  55. A synchronization apparatus, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory to cause the synchronization device to perform the method of any of claims 1 to 15.
  56. A synchronization apparatus, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory to cause the synchronization device to perform the method of any of claims 16 to 27.
  57. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 15.
  58. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 16 to 27.
  59. A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1 to 15.
  60. A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 16 to 27.
  61. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 15.
  62. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 16 to 27.
  63. A computer program which causes a computer to perform the method of any one of claims 1 to 15.
  64. A computer program which causes a computer to perform the method of any of claims 16 to 27.
CN202180074935.2A 2021-01-21 2021-01-21 Synchronization method and synchronization device Pending CN116349258A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/073163 WO2022155862A1 (en) 2021-01-21 2021-01-21 Synchronization method and synchronization device

Publications (1)

Publication Number Publication Date
CN116349258A true CN116349258A (en) 2023-06-27

Family

ID=82548312

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202180074935.2A Pending CN116349258A (en) 2021-01-21 2021-01-21 Synchronization method and synchronization device

Country Status (2)

Country Link
CN (1) CN116349258A (en)
WO (1) WO2022155862A1 (en)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI574518B (en) * 2015-01-08 2017-03-11 緯創資通股份有限公司 Ble transmitting equipment, ble receiving equipment, and methods thereof
CN106658377B (en) * 2016-12-26 2020-04-14 广州立功科技股份有限公司 Communication method and device of low-power-consumption Bluetooth
US11216051B2 (en) * 2019-04-24 2022-01-04 Qualcomm Incorporated Smart socket power monitoring and coordination
CN112188415B (en) * 2020-09-27 2021-11-26 展讯半导体(成都)有限公司 Low-power-consumption Bluetooth synchronous data streaming transmission method and device

Also Published As

Publication number Publication date
WO2022155862A1 (en) 2022-07-28

Similar Documents

Publication Publication Date Title
US11503534B2 (en) Method and apparatus for controlling network access
US11218951B2 (en) Method and apparatus for obtaining and transmitting system information
CN101137043B (en) Method, system and device for switching stream media channel and altering broadcast media
US10462759B2 (en) System and method for clock synchronization on a wireless network
CN103957218A (en) Shared media playing method and system
EP2945337A2 (en) Method, system and server for service switching
EP3091785B1 (en) Network selection method and user equipment
CN109005438B (en) Video playing method and device
WO2018024027A1 (en) Resource allocation and request initiating method and device for non-contention based random access
KR102566550B1 (en) Method of display playback synchronization of digital contents in multiple connected devices and apparatus using the same
US20220124435A1 (en) Earphone upgrade method, earphone assembly, upgrade device and non-transitory computer readable storage medium
US8307121B2 (en) Method and a type of transmit and receive ends for data synchronization
EP4192054A1 (en) Method for splitting end-to-end qos requirement information, terminal, and network side device
JP7196105B2 (en) Downlink control channel resource determination method, apparatus, user equipment and base station
US12004106B2 (en) Sidelink synchronization update
CN116349258A (en) Synchronization method and synchronization device
WO2020062611A1 (en) Emergency call receiving method, device, system and electronic equipment
WO2022242340A1 (en) Methods and apparatus for broadcasting and receiving bluetooth data packet, terminal, and storage medium
WO2022246838A1 (en) Indoor positioning method and apparatus, and device and storage medium
CN105682010B (en) Bluetooth connection control method, device and playback equipment in audio frequency broadcast system
EP4018743A1 (en) Setting a different bwp earlier in a connection establishment process to a wireless network by a ue when transitioning from an idle or inactive state
US20230156851A1 (en) Message sending method and apparatus, message receiving method and apparatus, and communication device
US20230262794A1 (en) Method for establishing connected state, terminal, core network function, and access network device
US11381951B2 (en) Wireless Bluetooth (BT) audio output system and control method thereof
RU2646369C2 (en) Method and device of communication of backup line for package data processing

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination