WO2024041161A1 - 发送与接收信息的方法、通信装置及系统 - Google Patents

发送与接收信息的方法、通信装置及系统 Download PDF

Info

Publication number
WO2024041161A1
WO2024041161A1 PCT/CN2023/102513 CN2023102513W WO2024041161A1 WO 2024041161 A1 WO2024041161 A1 WO 2024041161A1 CN 2023102513 W CN2023102513 W CN 2023102513W WO 2024041161 A1 WO2024041161 A1 WO 2024041161A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
expected
access
indicate
response message
Prior art date
Application number
PCT/CN2023/102513
Other languages
English (en)
French (fr)
Inventor
王蓉
谢子晨
凡伟
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024041161A1 publication Critical patent/WO2024041161A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • the present application relates to the field of short-distance communications, and in particular to methods, communication devices and systems for sending and receiving information.
  • BT Bluetooth
  • devices in the communication system can be divided into advertisers and scanners.
  • the scanner receives the broadcast information sent by the broadcaster in the scan window, and then establishes a connection with the broadcaster.
  • the traditional Bluetooth protocol stipulates that the scanner serves as the master node (grant node, G node) and the broadcaster serves as the terminal node (terminal node, T node).
  • the G node manages the T node and is responsible for allocating air interface resources to the T node; the T node obeys the scheduling of the G node and uses the air interface resources allocated by the G node to communicate with the G node.
  • the scanner needs to ensure that the scanning window covers at least one advertising interval in order to receive the broadcast information from the broadcaster and complete the access.
  • the probability of the scanner receiving broadcast information becomes smaller due to the limited time resources allocated by the scanner for the scanning window, which results in a lower probability of the scanner accessing the broadcaster. If the broadcaster's broadcast frequency is increased, the probability of the scanner receiving the broadcast information can be increased, but this will cause the broadcaster's power consumption to increase. Therefore, how to enable the scanner to still complete the access normally when the scanner needs to access a large number of broadcasters is an issue that needs to be solved urgently.
  • the method, communication device and system for sending and receiving information provided by the embodiments of the present application can enable the scanner to still complete access normally even when the scanner needs to access a large number of broadcasters.
  • the first aspect provides a method for sending information.
  • the method can be executed by a first device, or by a component of the first device, such as a processor, a chip, or a chip system of the first device. It can also be executed by a capable Logic module or software implementation that implements all or part of the first device functions.
  • the following description takes the method being executed by the first device as an example.
  • the method includes: the first device generates a broadcast message and sends the broadcast message to the second device.
  • the broadcast message includes first indication information, and the first indication information is used to indicate a role expected by the first device.
  • the desired role of the first device is a master node (G node) or a terminal node (T node).
  • the broadcaster (first device) sends the role expected by the broadcaster to the scanner (second device) through the first indication information in the broadcast message
  • the scanner can be informed of the broadcaster's desired role when broadcasting access to the broadcaster.
  • the desired roles can then allow the broadcaster to become a G node and the scanner to become a T node. In this way, after the scanner becomes a T node, it does not need to use its own air interface resources to allocate corresponding air interface resources to the broadcaster.
  • the method further includes: the first device receiving an access request message from the second device, the access request message being used by the second device to request access to the first device ;
  • the first device sends an access response message to the second device, and the access response message is used to indicate the second device's access success or access failure.
  • the method further includes: when the first device does not receive an access request message from the second device within the first time resource, the first device determines The connection between the first device and the second device failed.
  • the first device can determine whether the connection between the first device and the second device is successful by identifying whether it receives an access request message from the second device within a set time.
  • the second aspect provides a method for receiving information.
  • the method can be executed by a second device, or by a component of the second device, such as a processor, chip, or chip system of the second device. It can also be executed by a capable Implement all or part of the second device functionality Functional logic module or software implementation.
  • the following description takes the method being executed by the second device as an example.
  • the method includes: the second device receives a broadcast message from the first device. Wherein, the broadcast message includes first indication information, and the first indication information is used to indicate a role expected by the first device.
  • the desired role of the first device is G node or T node.
  • the broadcaster first device
  • the scanner can be informed of the broadcaster's desired role when broadcasting access to the broadcaster.
  • the desired role can then allow the scanner to become a T node and the broadcaster to become a G node.
  • the scanner does not need to use its own air interface resources to allocate corresponding air interface resources to the broadcaster. This not only alleviates the problem of the scanner being connected.
  • a large number of broadcasts are sent, causing its own air interface resources to be in a high proportion state, so that the scanner can still complete the access normally after accessing a large number of broadcast parties.
  • the scanner's air interface resources are in a high proportion state, the scanning party The party can also access more broadcasts.
  • the method further includes: when the second device determines to request access to the first device according to the broadcast message, the second device sends a request to the first device within the first time resource. Send an access request message, the access request message is used by the second device to request access to the first device; the second device receives an access response message from the first device, the access response message is used to indicate that the second device has successfully accessed Or access failed.
  • the method further includes: when the second device does not receive an access response message from the first device within the second time resource, the second device determines The connection between the second device and the first device failed.
  • the second device can determine whether the connection between the first device and the second device is successful by identifying whether it receives an access response message from the first device within a set time.
  • the access request message includes second indication information
  • the second indication information is used to indicate the role expected by the second device.
  • the expected role of the second device is G node or T node. That is, in this embodiment of the present application, the first device can explicitly inform the second device of the role expected by the first device, and the second device can explicitly inform the first device of the role expected by the second device.
  • the access response message is used to instruct the second device to The role expected by the second device is successfully accessed.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles do not conflict, the second device can successfully access in its expected role.
  • the access response message is used to instruct the second device to use the third device.
  • the role expected by the second device is successfully accessed.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the desired roles conflict but the first device agrees to become a role other than the role expected by the first device, the second device can successfully access in its desired role.
  • the first device becomes T node. If the role expected by the first device and the role expected by the second device are both T nodes, and the access response message is used to indicate that the second device accesses successfully in the role expected by the second device, the first device becomes T node. If the role expected by the first device and the role expected by the second device are both T nodes, and the access response message is used to indicate that the second device successfully accesses in the role expected by the second device, the first device becomes a G node.
  • the access response message is used to instruct the second device to use the third device.
  • the second device failed to access the expected role.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device The expected roles conflict but the first device does not agree with the second device to become the role expected by the second device, then the second device fails to access in its expected role.
  • the access response message is used to indicate that the second device fails to access the first device in the role expected by the second device.
  • it may mean that the second device fails to access the first device in the role expected by the second device.
  • taking a role other than the role expected by the second device to access the first device is used as an example to illustrate that the second device fails to access the first device in a role expected by the second device. If the role expected by the first device and the role expected by the second device are both G nodes, the second device accesses the first device as a T node. If the role expected by the first device and the role expected by the second device are both T nodes, the second device accesses the first device as a G node.
  • the first indication information is also used to instruct the first device Whether the desired role is negotiable. Since the first indication information can clarify whether the role desired by the first device can be negotiated, the second device can determine whether to send an access request message to the first device according to the first indication information. For example, in the case where the role expected by the first device is the same as the role expected by the second device, and the first indication information indicates that the role expected by the first device is not negotiable, the second device may determine not to send an access request to the first device. information. In this way, signaling overhead and power consumption can be saved.
  • the first indication information may also be used to indicate the role that the first device expects the second device to be.
  • the first device can inform the second device of the role that the first device expects the second device to be when broadcasting access to the first device through the first indication information in the broadcast message.
  • the access request message includes third indication information, and the third indication information is used to indicate the role expected by the second device and whether the role expected by the second device is It is negotiable, wherein the desired role of the second device is G node or T node. That is, in this embodiment of the present application, the first device can explicitly inform the second device of the role expected by the first device and whether it is negotiable, and the second device can explicitly inform the first device of the role expected by the second device and whether it is negotiable.
  • the third indication information may also be used to indicate the role that the second device expects the first device to be.
  • the second device may inform the first device of the role that the second device expects the first device to be when establishing a connection with the second device through the third indication information in the access request message.
  • the access response message is used to instruct the second device to The role expected by the second device is successfully accessed.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles do not conflict, the second device can successfully access in its expected role.
  • the role expected by the second device is the same as the role expected by the first device, and the role expected by the first device is non-negotiable and the role expected by the second device is not negotiable.
  • the access response message is used to indicate that the second device has failed to access in the role expected by the second device.
  • the second device when the first device explicitly informs the second device of the role expected by the first device, and the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and the role expected by the first device and the role expected by the second device are non-negotiable, the second device fails to access in its expected role.
  • the role expected by the second device is the same as the role expected by the first device, and the role expected by the first device is non-negotiable and the role expected by the second device is non-negotiable. If the role is negotiable, the access response message is used to indicate that the second device has successfully accessed in a role other than the role expected by the second device.
  • the second device when the first device explicitly informs the second device of the role expected by the first device, and the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and the role expected by the first device is non-negotiable and the role expected by the second device is negotiable, the second device can successfully access in a role other than the role expected by the second device.
  • the role expected by the second device is the same as the role expected by the first device, and the role expected by the first device is negotiable and the role expected by the second device is negotiable.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and the first device's expected role is negotiable, the second device can successfully access in its expected role. Since the embodiment of the present application allows the scanner and the broadcaster to negotiate the GT role, the GT role setting during the access process is more flexible and can adapt to actual business needs.
  • the role expected by the second device is the same as the role expected by the first device, and the role expected by the first device is negotiable and the role expected by the second device is negotiable.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device, or the access response message is used to indicate that the second device uses a role other than the role expected by the second device. Access successful.
  • the second device when the first device explicitly informs the second device of the role expected by the first device, and the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and both the role expected by the first device and the role expected by the second device are negotiable, the second device can successfully access in its expected role, or the second device can successfully access in a role other than the role expected by the second device. The role is successfully connected.
  • the access request message when the desired role of the second device is the G node, the access request message further includes the first connection information.
  • the first connection information includes one or more of the following provided by the second device: local clock, time offset, access address, frequency hopping map, cyclic redundancy check CRC code initial value, connection state period, or connection Status timeout period.
  • the access response message when used to indicate that the second device has successfully accessed in the role of the terminal node, the access response message further includes a second Connection information.
  • the second connection information includes one or more of the following provided by the first device: local clock, time offset, access address, frequency hopping map, CRC code initial value, connection state period, or connection state timeout time.
  • a communication device for implementing the above method.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method.
  • the modules, units, or means can be implemented by hardware, software, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device is a Bluetooth chip or a first device.
  • the communication device includes: a transceiver and a processor; the processor is used to generate a broadcast message; the transceiver , used to send the broadcast message to the second device.
  • the broadcast message includes first indication information, and the first indication information is used to indicate the desired role of the communication device.
  • the desired role of the communication device is G node or T node.
  • the transceiver is also used to receive an access request message from the second device; the transceiver is also used to send an access response message to the second device.
  • the access request message is used by the second device to request access to the first device.
  • the access response message is used to indicate that the second device has successfully accessed or failed to access.
  • the access request message includes second indication information, and the second indication information is used to indicate the role expected by the second device.
  • the expected role of the second device is G node or T node.
  • the access response message is used to instruct the second device to use the role expected by the second device.
  • the role is successfully connected.
  • the access response message is used to instruct the second device to use the role expected by the second device.
  • the role is successfully connected.
  • the access response message is used to instruct the second device to use the role expected by the second device. Character access failed.
  • the first indication information is also used to indicate whether the role expected by the communication device is negotiable.
  • the access request message includes third indication information, and the third indication information is used to indicate the role expected by the second device and whether the role expected by the second device is negotiable.
  • the expected role of the second device is G node or T node.
  • the access response message is used to instruct the second device to use the role expected by the second device.
  • the role is successfully connected.
  • the role expected by the second device is the same as the role expected by the communication device, and the role expected by the communication device is non-negotiable and the role expected by the second device is non-negotiable.
  • the access response message is used to indicate that the second device fails to access in the role expected by the second device.
  • the role expected by the second device is the same as the role expected by the communication device, and the role expected by the communication device is non-negotiable and the role expected by the second device is negotiable.
  • the access response message is used to indicate that the second device has successfully accessed in a role other than the role expected by the second device.
  • the role expected by the second device is the same as the role expected by the communication device, and the role expected by the communication device is negotiable and the role expected by the second device is non-negotiable.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the role expected by the second device is the same as the role expected by the communication device, and the role expected by the communication device is negotiable and the role expected by the second device is negotiable.
  • the access response message is used to indicate that the second device has successfully accessed in a role expected by the second device, or the access response message is used to indicate that the second device has successfully accessed in a role other than the role expected by the second device.
  • the processor is also used to provide the transceiver with the first time If the access request message from the second device is not received in the source, it is determined that the connection between the communication device and the second device fails.
  • the access request message when the role expected by the second device is a G node, the access request message further includes first connection information, and the first connection information includes the information provided by the second device.
  • first connection information includes the information provided by the second device.
  • the access response message when used to indicate that the second device has successfully accessed in the role of T node, the access response message also includes second connection information.
  • the second connection information includes one or more of the following provided by the communication device: local clock, time offset, access address, frequency hopping map, CRC code initial value, connection state period, or connection state timeout time.
  • a communication device for implementing the above method.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method.
  • the modules, units, or means can be implemented by hardware, software, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device is a Bluetooth chip or a second device, and the communication device includes: a transceiver; and the transceiver is used to receive broadcast messages from the first device.
  • the broadcast message includes first indication information, and the first indication information is used to indicate a role expected by the first device.
  • the expected role of the first device is G node or T node.
  • the communication device further includes a processor; and the transceiver is further used to send a request to the first device when the processor determines to request access to the first device based on the broadcast message.
  • the device sends an access request message; the transceiver is also used to receive an access response message from the first device.
  • the access request message is used by the communication device to request access to the first device.
  • the access response message is used to indicate the communication device's access success or access failure.
  • the access request message includes second indication information, and the second indication information is used to indicate the desired role of the communication device.
  • the desired role of the communication device is G node or T node.
  • the access response message is used to instruct the communication device to use the role expected by the communication device.
  • the role is successfully connected.
  • the access response message is used to instruct the communication device to use the role expected by the communication device.
  • the role is successfully connected.
  • the access response message is used to instruct the communication device to use the role expected by the communication device. Character access failed.
  • the first indication information is also used to indicate whether the role expected by the first device is negotiable.
  • the access request message includes third indication information, and the third indication information is used to indicate the role expected by the communication device and whether the role expected by the communication device is negotiable.
  • the desired role of the communication device is G node or T node.
  • the access response message is used to instruct the communication device to use the role expected by the communication device.
  • the role is successfully connected.
  • the role expected by the communication device is the same as the role expected by the first device, and the role expected by the first device is non-negotiable and the role expected by the communication device is non-negotiable.
  • the access response message is used to indicate that the communication device fails to access in the role expected by the communication device.
  • the role expected by the communication device is the same as the role expected by the first device, and the role expected by the first device is non-negotiable and the role expected by the communication device is negotiable.
  • the access response message is used to indicate that the communication device has successfully accessed in a role other than the role expected by the communication device.
  • the role expected by the communication device is the same as the role expected by the first device, and the role expected by the first device is negotiable and the role expected by the communication device is non-negotiable.
  • the access response message is used to indicate that the communication device has successfully accessed in the role expected by the communication device.
  • the role expected by the communication device is the same as the role expected by the first device, and the role expected by the first device is negotiable and the role expected by the communication device is negotiable.
  • access should The response message is used to indicate that the communication device has successfully accessed in a role expected by the communication device, or the access response message is used to indicate that the communication device has successfully accessed in a role other than the role expected by the communication device.
  • the processor is further configured to determine if the transceiver does not receive an access response message from the first device within the second time resource. The connection between the communication device and the first device fails.
  • the access request message when the desired role of the communication device is a G node, the access request message further includes first connection information, and the first connection information includes the information provided by the communication device.
  • first connection information includes the information provided by the communication device.
  • the access response message when used to indicate that the communication device has successfully accessed in the role of T node, the access response message also includes second connection information.
  • the second connection information includes one or more of the following provided by the first device: local clock, time offset, access address, frequency hopping map, CRC code initial value, connection state period, or connection state timeout time.
  • a fifth aspect provides a communication system, including one or more communication devices described in the third aspect, and one or more communication devices described in the fourth aspect.
  • a sixth aspect provides a communication device, including: a processor; the processor is configured to be coupled to a memory, and after reading computer instructions stored in the memory, execute the method described in the first aspect according to the instructions.
  • the communication device further includes a memory; the memory is used to store computer instructions.
  • the communication device further includes a communication interface; the communication interface is used for the communication device to communicate with other equipment or devices.
  • the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc.
  • the communication device may be a chip or a chip system.
  • the communication device may be composed of a chip, or may include a chip and other discrete devices.
  • a computer-readable storage medium is provided. Instructions are stored in the computer-readable storage medium, and when run on a computer, the computer can execute the method described in the first or second aspect.
  • An eighth aspect provides a computer program product containing instructions that, when run on a computer, enable the computer to execute the method described in the first or second aspect.
  • Figure 1 is a schematic diagram of a broadcast scanning process provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of a broadcast access process provided by an embodiment of the present application.
  • Figure 3 is an architectural schematic diagram of a communication system provided by an embodiment of the present application.
  • Figure 4 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 5 is a schematic flowchart 1 of a method for sending and receiving information provided by an embodiment of the present application
  • Figure 6 is a schematic flow chart 2 of a method for sending and receiving information provided by an embodiment of the present application
  • Figure 7 is a schematic flow chart of a second device accessing a first device according to an embodiment of the present application.
  • Figure 8 is a schematic second structural diagram of a communication device provided by an embodiment of the present application.
  • Channel is the channel for message transmission between the broadcaster and the scanner. Scanners and broadcasters can operate in unlicensed frequency bands, such as industrial, scientific and medical (industrial scientific medical, ISM) bands. Taking the 2.4GHz frequency band (2400 ⁇ 2483.5MHz) in the ISM frequency band as an example, the 2.4GHz frequency band can be divided into 40 channels. The interval between two adjacent channels is 2MHz. Among them, the index range of the channel is 0 ⁇ 39, CH37 ⁇ CH39 are broadcast channels, and CH0 ⁇ CH36 are data channels. The relevant descriptions of the above 40 channels can be found in Table 1.
  • the broadcaster and the scanner may also work in other frequency bands, which are not specifically limited in the embodiment of the present application.
  • Broadcast access may refer to the process in which the scanner discovers the broadcaster through a broadcast message, initiates an access request to the broadcaster based on the broadcast message, and then establishes a connection with the broadcaster.
  • the “broadcaster” can also be called the “broadcaster” or “broadcast device”; the “scanner” can also be called the “scanner” or “access device”, which will be explained here uniformly and will not be used here. Repeat.
  • the broadcast message may include an extended broadcast packet (adv_ext_ind) and an extended data packet (aux_adv_ind).
  • the extended broadcast packet is used by the scanner to discover the broadcaster and the extended data packet.
  • the extension data packet may include capability information of the broadcaster for the scanner to determine whether to send an access request to the broadcaster.
  • the location of the extended data packet may include a channel for transmitting the extended data packet, a time domain resource and/or a frequency domain resource for receiving the extended data packet, etc. This embodiment of the present application does not specifically limit this.
  • the broadcaster's capability information may include one or more of the following: the modulation method supported by the broadcaster, the supported channel bandwidth, or whether channel coding is supported, etc. This is not the case in the embodiment of the present application. Specific limitations.
  • Figure 1 shows the broadcast scanning process.
  • the broadcaster sends extended broadcast packets within the broadcast interval.
  • the scanner can receive extended broadcast packets from the broadcaster in the scanning window.
  • the broadcaster can send extended broadcast packets on one or more broadcast channels. It can be understood that the scanner monitors whether it receives the extended data packet from the broadcaster within the scanning window, which can prevent the scanner from being in a monitoring state all the time, thereby saving the power consumption of the scanner.
  • the broadcaster can send extended broadcast packets on broadcast channel A, broadcast channel B, and broadcast channel C in sequence.
  • the broadcaster sends extended broadcast packet A on broadcast channel A, then the broadcaster sends extended broadcast packet B on broadcast channel B, and then the broadcaster sends extended broadcast packet C on broadcast channel C.
  • broadcast Channel A, broadcast channel B, and broadcast channel C can be any of the broadcast channels from CH37 to CH39 in Table 1 above. Since the three broadcast channels are at least 24MHz apart and the probability of being interfered at the same time is small, the three broadcast channels are The broadcast channel sends extended broadcast packets in turns to increase the probability that the scanner receives the extended broadcast packet.
  • the extended broadcast packet may carry an auxiliary pointer (auxiliary pointer, AuxPtr).
  • AuxPtr is used to indicate the location of the extension data packet.
  • AuxPtr1 in the extended broadcast packet A, AuxPtr2 in the extended broadcast packet B, and AuxPtr3 in the extended broadcast packet C all indicate the location where the scanner receives the extended data packet. In this way, the scanner can receive extension packets based on AuxPtr.
  • the broadcaster can send the extended broadcast packet on multiple broadcast intervals (only one broadcast interval is shown in Figure 1). Accordingly, the scanning window needs to cover at least one of the broadcast intervals so that the scanner can receive the extended broadcast packet from the broadcaster.
  • the broadcaster sends an extended data packet on data channel D.
  • the scanner receives the extended data packet from the broadcaster according to the position indicated by AuxPtr in the extended broadcast packet.
  • the data channel D can be any one of the data channels CH0 to CH36 in Table 1 above.
  • the scanner After the scanner receives the extended data packet from the broadcaster according to the position indicated by AuxPtr in the extended broadcast packet, as shown in Figure 2, the scanner sends an access request message (conn_req) to the broadcaster based on the information in the extended data packet. Accordingly, the broadcaster receives the access request message from the scanner. Afterwards, the broadcaster sends an access response message (conn_rsp) to the scanner based on the access request message. Accordingly, the scanner receives the access response message from the broadcaster. The access response message is used to indicate the scanner's access success or access failure. If the scanner accesses successfully, the scanner becomes the G node and the broadcaster becomes the T node.
  • the "access request message” may also be called a "connection request message”
  • the "access response message” may also be called an “access response message” or a “connection response message”, etc. , are explained uniformly here and will not be described in detail below.
  • the "extended broadcast packet” can also be called an "extended broadcast packet”
  • the "extended data packet” can also be called an “extended data packet”. They will be explained here uniformly and will not be described in detail below. .
  • Air interface resources include time domain resources and frequency domain resources. After the scanner becomes a G node, it needs to allocate certain air interface resources to the broadcaster (T node) to facilitate data interaction between the scanner and the broadcaster. That is to say, on the one hand, after the scanner accesses the broadcaster, part of the scanner's air interface resources will be occupied, and as the number of connected broadcasters increases, the scanner's air interface resources will be in a high proportion; on the other hand, after the scanner and the broadcaster establish a connection, they will interact with business data. If the interaction of business data takes up more air interface resources, it will also cause the scanner's air interface resources to be in a high proportion. However, the scanner's air interface resources are in a high proportion, causing the broadcast access solutions shown in Figures 1 and 2 to have the following problems:
  • the probability of the scanner accessing the broadcaster is low.
  • the time resources (window length) allocated by the scanner for the scanning window are limited and may not cover a broadcast interval, causing the scanner to receive from
  • the probability of the broadcaster's extended broadcast packets is reduced, and the scanner may need to open the scanning window multiple times to receive the extended broadcast packets, causing the scanner to be unable to access the broadcaster in time, affecting the user experience.
  • the number of broadcast parties that the scanner can access is limited.
  • the scanner's air interface resources are limited. When the scanner's air interface resources are in a high duty cycle state, the scanner may not have free air interface resources to allocate to the broadcaster, so the scanner cannot access the broadcaster.
  • embodiments of the present application provide a method for sending and receiving information, which can enable the scanner to still complete access normally when the scanner needs to access a large number of broadcasters, and when the scanner's air interface resources are in high occupation. Increase the number of access broadcasters compared to the state.
  • At least one of the following or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple .
  • words such as “first” and “second” are used to distinguish identical or similar items with basically the same functions and effects.
  • words such as “first” and “second” do not limit the number and execution order, and words such as “first” and “second” do not limit the number and execution order.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or explanations. Any embodiment or design described as “exemplary” or “such as” in the embodiments of the present application is not to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present related concepts in a concrete manner that is easier to understand.
  • "instruction” may include direct instruction and indirect instruction, and may also include explicit instruction and implicit instruction.
  • the information indicated by certain information (such as the information used to indicate the expected role of the first device and/or the second device as described below) is called information to be indicated.
  • the information to be indicated is indicated. There are many ways, for example but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated, etc.
  • the information to be indicated may also be indirectly indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance.
  • the indication of specific information can also be achieved by means of a pre-agreed (for example, protocol stipulated) arrangement order of each piece of information, thereby reducing the indication overhead to a certain extent.
  • G node may also be referred to as “G role”
  • T node may also be referred to as “T role”.
  • G node and G role can be expressed interchangeably
  • T node and T role can be expressed interchangeably. They are explained uniformly here and will not be described again below.
  • FIG. 3 it is a schematic architectural diagram of a communication system provided by an embodiment of the present application.
  • the communication system includes a first device and a second device.
  • the communication system may include multiple first devices and multiple second devices.
  • the communication system can be applied to scenarios such as vehicle battery management, Internet-of-things (IoT), and industrial control.
  • IoT Internet-of-things
  • the first device generates a broadcast message and sends the broadcast message to the second device.
  • the broadcast message includes first indication information, and the first indication information is used to indicate a role expected by the first device.
  • the expected role of the first device is G node or T node.
  • the broadcaster (first device) sends the role expected by the broadcaster to the scanner (second device) through the first indication information in the broadcast message
  • the scanner can be informed of the broadcaster's desired role when broadcasting access to the broadcaster.
  • the desired roles can then allow the broadcaster to become a G node and the scanner to become a T node. In this way, after the scanner becomes a T node, it does not need to use its own air interface resources to allocate corresponding air interface resources to the broadcaster.
  • the first device and the second device in this embodiment of the present application may refer to electronic devices with data transmission and reception processing capabilities, may include terminal devices, or may be chips included in the terminal devices.
  • the first device or the second device may be a car cockpit (cockpit domain) device, or a module in the car cockpit device, such as a cockpit domain controller (CDC), camera, screen, microphone, audio, electronics, etc.
  • CDC cockpit domain controller
  • the modules such as key, keyless entry or starter controller.
  • the first device and the second device may also be data transfer devices, such as network devices, routers, repeaters, bridges or switches.
  • the communication technology involved in this application may be a communication technology between terminal devices, a communication technology between a network device and a terminal device, or a communication technology between a network device and a network device.
  • the identities of the communication parties must be specifically limited and can support corresponding communication technologies and functions.
  • the terminal device in the embodiment of the present application can be various types of user equipment (UE), mobile phone (mobile phone), tablet computer (pad), desktop computer, headphones, speakers, etc.; it can also include Machine intelligence equipment, such as self-driving equipment, transportation safety equipment, and virtual reality (VR) terminal equipment equipment, augmented reality (AR) terminal equipment, machine type communication (MTC) equipment, industrial control equipment, remote medical equipment, smart grid equipment, smart City (smart city) equipment, smart home equipment, etc.; can also include wearable devices (such as smart watches, smart bracelets, pedometers, etc.) and so on.
  • Machine intelligence equipment such as self-driving equipment, transportation safety equipment, and virtual reality (VR) terminal equipment equipment, augmented reality (AR) terminal equipment, machine type communication (MTC) equipment, industrial control equipment, remote medical equipment, smart grid equipment, smart City (smart city) equipment, smart home equipment, etc.
  • MTC machine type communication
  • industrial control equipment remote medical equipment
  • smart grid equipment smart City (smart city) equipment
  • network devices in the embodiments of this application include but are not limited to: evolved node B (evolved node B, eNB), radio network controller (Radio Network Controller, RNC), node B (Node B, NB), Base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved node B, or Home node B, HNB), base band unit (BBU), Access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (transmission and reception point) in a wireless fidelity (WIFI) system, TRP), etc.
  • 5G such as gNB in the NR system, or transmission point (TRP or TP), one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or, also It can be a network node that constitutes a gNB or transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.
  • the first device is the broadcaster, but the first device can have the scanning function of the scanner; the second device is the scanner, but the second device can have the broadcast function of the broadcaster.
  • the implementation of this application The example does not specifically limit this.
  • the related functions of the first device or the second device in the embodiment of the present application may be implemented by one device, may be implemented by multiple devices together, or may be implemented by one or more functional modules within one device.
  • the embodiments of this application do not specifically limit this. It can be understood that the above functions can be either network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (for example, a cloud platform) Virtualization capabilities.
  • the related functions of the first device or the second device in the embodiment of the present application can be implemented through the communication device 400 in FIG. 4 .
  • Figure 4 shows a schematic structural diagram of a communication device 400 provided by an embodiment of the present application.
  • the communication device 400 may be a first device or a second device, or may be a chip or component used in the first device or the second device.
  • the communication device 400 includes a processor 401, a communication line 402, and at least one communication interface (Figure 4 is only an example of including a communication interface 404 and a processor 401 for illustration).
  • a memory 403 may also be included.
  • the processor 401 may be a CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application, for example: one or more microprocessors Processor (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).
  • DSP digital signal processor
  • FPGA field programmable gate array
  • Communication lines 402 may include pathways for connecting different components.
  • the communication interface 404 may be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, RAN, WLAN, etc.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 404 may also be a transceiver circuit located within the processor 401 to implement signal input and signal output of the processor.
  • the memory 403 may be a device with a storage function. For example, it can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or other types of things that can store information and instructions. Dynamic storage devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage ( Including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be stored by a computer. any other medium, but not limited to this.
  • the memory may exist independently and be connected to the processor through a communication line 402 . Memory can also be integrated with the processor.
  • the memory 403 is used to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 401 for execution.
  • the processor 401 is used to execute computer execution instructions stored in the memory 403, thereby implementing the method of sending and receiving information provided in the embodiment of the present application.
  • the processor 401 may also perform processing-related functions in the method of sending and receiving information provided in the following embodiments of this application, and the communication interface 404 is responsible for communicating with other devices or communication networks.
  • This application Example for this No specific limitation is made.
  • the computer-executed instructions in the embodiments of the present application may also be called application codes, which are not specifically limited in the embodiments of the present application.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4 .
  • the communication device 400 may include multiple processors, such as the processor 401 and the processor 407 in FIG. 4 .
  • processors may be a single-CPU processor or a multi-CPU processor.
  • a processor here may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the communication device 400 may also include an output device 405 and an input device 406.
  • Output device 405 communicates with processor 401 and can display information in a variety of ways.
  • the above-mentioned communication device 400 may be a general-purpose device or a special-purpose device.
  • the communication device 400 may be a Bluetooth headset, a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a vehicle-mounted terminal device, an embedded device, or a device having the functions shown in FIG. 4 Equipment of similar structure.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of communication device 400.
  • the names of the messages between the devices or the names of the parameters in the messages are just examples, and other names may also be used in specific implementations. This is not specifically limited in the embodiments of the present application. .
  • the method for sending and receiving information includes the following steps:
  • the first device generates a broadcast message.
  • the broadcast message includes first indication information, and the first indication information is used to indicate a role expected by the first device.
  • the expected role of the first device is G node or T node.
  • the first indication information may be a GT flag.
  • the GT flag may use a 1-bit symbol "0" to indicate that the first device's expected role is a T node, and a 1-bit symbol "1" to indicate that the first device's expected role is a G node.
  • the GT flag can use a 1-bit symbol "1” to indicate that the role expected by the first device is a T node, and a 1-bit symbol "0" to indicate that the role expected by the first device is a G node. This is not the case in the embodiment of the present application. Make specific limitations.
  • the first indication information may be information indicating that the first device requests to acquire and/or allocate air interface resources.
  • the first indication information is information used to instruct the first device to request to obtain air interface resources, it can be used to indicate that the role expected by the first device is a T node; or if the first indication information is empty, then it can be It is used to indicate that the role expected by the first device is a G node; or, if the first indication information is information used to indicate that the first device requests to allocate air interface resources to the accessed device, it can be used to indicate the role expected by the first device. is a G node; or, if the first indication information is empty, it can be used to indicate that the first device's expected role is a T node.
  • the first indication information may be information indicating capability information of the first device.
  • the capability information may be whether the first device supports allocating resources for the accessed device. If the capability information indicates that the first device supports allocating resources for the accessed device, the first indication information is used to instruct the first device.
  • the desired role is a G node; or, if the capability information indicates that resource allocation for the accessed device is not supported, the first indication information is used to indicate that the first device's desired role is a T node.
  • the first indication information may be information instructing the first device or the second device to configure a system management frame.
  • the first indication information is information indicating that the first device configures a system management frame
  • it can be used to indicate that the first device's desired role is a G node; or if the first indication information is information indicating that the second device configures a system management frame
  • the information can be used to indicate the first device's desired role as a T node.
  • the system management frame is used by G node to manage T node.
  • the first indication information may be information instructing the second device to send the first connection information, or information instructing the first device to send the second connection information.
  • the first connection information is the connection information provided by the second device that is required for the second device to access the first device.
  • the second connection information is the connection information provided by the first device that is required for the second device to access the first device. If the first instruction information is information instructing the second device to send the first connection information, Then it can be used to indicate that the role expected by the first device is a T node; or, if the first indication information is information instructing the first device to send the second connection information, it can be used to indicate that the role expected by the first device is a G node.
  • connection information required by the second device to access the first device may include but is not limited to: local clock, time offset, access address, frequency hopping map, cyclic redundancy check (Cyclic redundancy check, CRC) code initial value, connection state period, or connection state timeout time, etc.
  • the time offset may be used to indicate time resources for data transmission between the first device and the second device.
  • the frequency hopping map may be used to determine the frequency point at which the first device and the second device establish a connection.
  • the initial value of the CRC code is used for CRC calculation, and the CRC can be used to detect whether errors occur in the data transmitted between the first device and the second device.
  • the connection state cycle is the cycle of data transmission between the first device and the second device.
  • connection state timeout time may be used to indicate whether the connection between the first device and the second device is re-established. For example, if the first device does not receive data from the second device within the connection state timeout period, it means that the connection established between the first device and the second device is unstable and the connection needs to be re-established.
  • the first indication information may be a GT flag, thereby explicitly indicating the role expected by the first device.
  • the first indication information may be information indicating that the first device requests to acquire and/or allocate air interface resources, information indicating capability information of the first device, information indicating that the first device or the second device configures a system management frame, information indicating that the first device The second device sends information of the first connection information, or instructs the first device to send information of the second connection information, etc., thereby implicitly indicating the role expected by the first device, which is not specifically limited in the embodiment of the present application.
  • the first device sends a broadcast message to the second device. Accordingly, the second device receives the broadcast message from the first device.
  • the first device may send a broadcast message to the second device on one or more broadcast channels within the broadcast interval.
  • the second device may receive the broadcast message from the first device within the scanning window.
  • the broadcaster (first device) sends the role expected by the broadcaster to the scanner (second device) through the first indication information in the broadcast message
  • the scanner can be informed of the broadcaster's desired role when broadcasting access to the broadcaster.
  • the desired roles can then allow the broadcaster to become a G node and the scanner to become a T node.
  • the scanner does not need to use its own air interface resources to allocate corresponding air interface resources to the broadcaster.
  • This not only alleviates the high proportion of its own air interface resources caused by the second device accessing a large number of first devices. , so that the second device can still complete the access normally after accessing a large number of first devices, and when the air interface resources of the second device are in a high proportion, the second device can also access more first devices.
  • the actions of the first device in the above steps S501 to S502 can be executed by the processor 401 in the communication device 400 shown in FIG. 4 by calling the application code stored in the memory 403 to instruct the first device to execute.
  • the action of the second device can be executed by the processor 401 in the communication device 400 shown in FIG. 4 by calling the application code stored in the memory 403 to instruct the second device.
  • This embodiment does not impose any limitation on this.
  • the method for sending and receiving information provided by the embodiment of the present application may further include the following steps after step S502:
  • the second device determines to request access to the first device according to the broadcast message
  • the second device sends an access request message to the first device.
  • the access request message is used by the second device to request access to the first device.
  • the first device receives the access request message from the second device.
  • the second device when the second device determines to request access to the first device based on the broadcast message, the second device sends an access request message to the first device within the first time resource.
  • the incoming request message is used by the second device to request access to the first device.
  • the first device receives the access request message from the second device within the first time resource.
  • the first time resource may be determined by the first device. Accordingly, the broadcast message in step S501 indicates the first time resource. That is to say, the second device can determine the first time resource according to the broadcast message, so that the access request message can be sent to the first device within the first time resource.
  • the broadcast message may indicate the first time resource in a display manner.
  • the broadcast message may include the start time and end time of the first time resource.
  • the first time resource may also be negotiated in advance by the first device and the second device; or the first time resource may be agreed upon in the agreement, which is not specifically limited in the embodiment of the present application.
  • the process of the second device sending an access request message within the first time resource is described by taking the broadcast message including the extended broadcast packet as an example.
  • Figure 7 it is a schematic flow chart for the second device to access the first device.
  • the time interval between the starting time of the first time resource and the starting time of the first device sending the extension data packet is the offset of the access request.
  • the second device may send one or more access request messages within the first time resource.
  • the first device may receive the message from the first time resource within the first time resource. Access request message from the second device.
  • the first device sends an access response message to the second device.
  • the second device receives the access response message from the first device.
  • the access response message is used to indicate successful access or access failure of the second device.
  • the first device when the first device receives an access request message from the second device within the first time resource, the first device sends an access response message to the second device.
  • the first device may send the access response message within the second time resource.
  • the second device receives the access response message from the first device within the second time resource.
  • the second time resource may be determined by the second device.
  • the access request message may also indicate the second time resource. That is to say, the first device can determine the second time resource according to the access request message, so that the access response message can be sent to the second device within the second time resource.
  • the access request message may indicate the second time resource in a display manner.
  • the access request message may include the start time and end time of the second time resource.
  • the second time resource may also be negotiated in advance by the first device and the second device; or the second time resource may be agreed upon in the agreement, which is not specifically limited in the embodiment of the present application.
  • the time interval between the starting time when the first device sends the access response message and the starting time when the first device sends the extension data packet is the offset of the access response.
  • the offset of the access response is greater than the sum of the offset of the access request and the time length of the first time resource.
  • the access request message is used to indicate that the second device agrees to access the first device in a role other than the role expected by the first device.
  • the access response message is used to indicate that the second device has successfully accessed. That is to say, the second device can determine that after the first device and the second device establish a connection, the first device can assume the role expected by the first device.
  • the access request message includes second indication information, the second indication information being used to indicate a role expected by the second device.
  • the expected role of the second device is G node or T node. That is, in this embodiment of the present application, the first device can explicitly inform the second device of the role expected by the first device, and the second device can explicitly inform the first device of the role expected by the second device.
  • the second indication information is similar to the above-mentioned first indication information.
  • the second indication information may be a GT flag; or the second indication information may indicate that the second device requests to obtain and/or allocate air interface resources.
  • Information, information indicating capability information of the second device, information indicating the first device or the second device configures a system management frame, information indicating the second device sending the first connection information, or information indicating the first device sending the second connection information.
  • Information etc. For relevant description of the second indication information, please refer to the above description of the first indication information, and will not be described again here.
  • the access response message is used to indicate that the second device accesses successfully in the role expected by the second device.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles do not conflict, the second device can successfully access in its expected role.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the desired roles conflict but the first device agrees to become a role other than the role expected by the first device, the second device can successfully access in its desired role.
  • the access response message is used to indicate that the second device fails to access in the role expected by the second device.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device
  • the first device and the second device The expected roles conflict but the first device does not agree with the second device to become the role expected by the second device, then the second device fails to access in its expected role.
  • the first device may determine whether to allow the second device to access the first device in a role expected by the second device based on the actual application scenario.
  • the first device may determine, based on the service information, whether to allow the second device to access the first device in a role expected by the second device.
  • the business information may be indicated by the application. If the application indicates that the first device can only become a T node, and the role expected by the second device is a T node, the first device does not agree with the second device accessing the first device in the role expected by the second device. equipment.
  • the application may be an audio playback application, and the first device is an audio playback device. In this case, the first device can only become a T node.
  • the first device may determine, based on the hardware information, whether to allow the second device to access the first device in a role expected by the second device. For example, if the first device is an input device such as a keyboard, mouse, or stylus, the first device can only become a T node. When the second device's expected role is a T node, the first device does not agree with the second device's role as the second device. The role expected by the device accesses the first device.
  • the first device and the second device can indicate the role expected by the first device and the role expected by the second device through the first indication information and the second indication information, and the first device determines the role expected by the second device. Whether the second device can be successfully accessed in the role expected by the second device.
  • the access request message when the desired role of the second device is a G node, the access request message further includes the first connection information.
  • the first connection information includes one or more of the following provided by the second device: local clock, time offset, access address, frequency hopping map, CRC code initial value, connection state period, or connection state timeout time.
  • the access response message when the access response message is used to indicate that the second device successfully accesses in the role of T node, or when the access request message is used to indicate that the second device agrees to use the first
  • the access response message also includes second connection information
  • the second connection information includes the following provided by the first device One or more items: local clock, time offset, access address, frequency hopping map, initial value of CRC code, connection state period, or connection state timeout.
  • the first device when the access response message indicates that the second device has successfully accessed, and the first device becomes a G node and the second device is a T node, the first device sends system management to the second device. frame.
  • the time interval between the starting time when the first device sends the system management frame and the starting time when the first device sends the access response message is the offset of the system management frame.
  • the second device when the access response message indicates that the second device is successfully accessed, and the first device becomes a T node and the second device becomes a G node, the second device sends a system management frame to the first device. .
  • the time interval between the start time of the second device sending the system management frame and the start time of the first device sending the access response is the offset of the system management frame.
  • the second device (scanner) is allowed to become a T node
  • the first device (broadcaster) is allowed to become a G node
  • the air interface resources can not only alleviate the high proportion of air interface resources of the second device caused by accessing a large number of first devices, so that the second device can still complete the access normally after accessing a large number of first devices, but also When the air interface resources of the second device are in a high proportion, the second device can also access more first devices.
  • the broadcast message in this embodiment of the present application includes an extended broadcast packet and an extended data packet.
  • S502 may include:
  • the first device sends an extended broadcast packet to the second device on one or more broadcast channels within the broadcast interval, and sends an extended data packet to the second device on the data channel.
  • the second device receives the extended broadcast packet from the first device on one or more broadcast channels, and receives the extended data packet from the first device on the data channel.
  • the extended broadcast packet and/or the extended data packet may carry the first indication information.
  • S502a is similar to the solution shown in Figure 2 in the preamble of the specific embodiment.
  • the first device can sequentially send extended broadcast packets on broadcast channel A, broadcast channel B, and broadcast channel C, and send it on data channel D. Expansion data package.
  • S502a please refer to the solution shown in Figure 2 and will not be described again here.
  • AuxPtr may indicate the channel or frequency point where the extension data packet is located, the time domain resource for receiving the extension data packet, and physical layer information.
  • the time domain resources for receiving the extended data packet may include clock accuracy, clock unit, or time offset for receiving the extended data packet, etc.
  • the physical layer information may include the channel bandwidth used by the extended data packet, or the channel coding type, etc.
  • the channel bandwidth can be understood as the symbol rate, that is, the channel bandwidth can be understood as the number of symbols transmitted per unit time.
  • the channel bandwidth includes 1MHz, 2MHz, or 4MHz, which can be understood as the symbol rate includes 1M symbol/s (the number of symbols transmitted per second is 1M), 2M symbol/s, or 4M symbol/s.
  • the extension data packet may include identification information indicating a device that can request access to the first device and/or capability information of the first device.
  • the identification information of the device that can request access to the first device is used to identify the identity of the device that can request to establish a connection with the first device.
  • the identification information may include a device that can request access to the first device. media access control address (MAC) address.
  • MAC media access control address
  • the capability information of the first device may be used to indicate one or more of the following: a modulation mode supported by the first device, a channel bandwidth supported by the first device, whether the first device supports channel coding, or whether the first device supports The type of channel coding.
  • the modulation method supported by the first device may include a Gaussian frequency shift keying (GFSK) modulation method and/or a phase shift keying (PSK) modulation method, etc.
  • GFSK Gaussian frequency shift keying
  • PSK phase shift keying
  • the channel bandwidth supported by the first device may include the total channel bandwidth supported by the first device, and/or the channel bandwidth of each frequency hopping channel in the frequency hopping mode.
  • the types of channel coding supported by the first device include polar code coding, reed-solomon codes (RS) coding, or binary coded hollerith (BCH) coding, etc. , the embodiments of this application do not specifically limit this.
  • the actions of the first device in the above steps S501 to S504 can be executed by the processor 401 in the communication device 400 shown in FIG. 4 by calling the application code stored in the memory 403 to instruct the first device to execute.
  • the action of the second device can be executed by the processor 401 in the communication device 400 shown in FIG. 4 by calling the application code stored in the memory 403 to instruct the second device.
  • This embodiment does not impose any limitation on this.
  • the method of sending and receiving information provided by the embodiment of the present application further includes: When the second device determines based on the broadcast message that the second device cannot access the first device, the second device gives up sending the access request message to the first device. Further, in the case where the first device does not receive the access request message from the second device within the first time resource, the first device determines that the connection between the first device and the second device fails, and also gives up the request to the second device. The device sends an access response message.
  • the second device can inform the first device of a connection failure between the second device and the first device by not sending an access request. In this way, the overhead of subsequent access request messages and access response messages can be saved, and the energy of the first device and the second device can also be saved.
  • the first indication information is also used to indicate whether the role expected by the first device is negotiable. Since the first indication information can clarify whether the role desired by the first device can be negotiated, the second device can determine whether to send an access request message to the first device according to the first indication information. For example, in the case where the role expected by the first device is the same as the role expected by the second device, and the first indication information indicates that the role expected by the first device is not negotiable, the second device may determine not to send an access request to the first device. information. In this way, signaling overhead and power consumption can be saved.
  • the first indication information when the first indication information is also used to indicate whether the role expected by the first device is negotiable, the first indication information may be a GT flag.
  • the GT flag flag can be indicated using 2 bits, of which 1 bit is used to indicate the role expected by the first device, and the other bit is used to indicate whether the role expected by the first device is negotiable.
  • the high bit is used to indicate the role expected by the first device, and the low bit is used to indicate whether the role expected by the first device is negotiable; or, the low bit is used to indicate the role expected by the first device, and the high bit is used to indicate the role expected by the first device. Whether the device's expected role is negotiable.
  • a 1-bit symbol “0" indicates that the first device's expected role is a T node
  • a 1-bit symbol “1” indicates that the first device's expected role is a G node
  • a 1-bit symbol “1” is used to indicate that the first device's desired role is the T node
  • a 1-bit symbol “0” is used to indicate that the first device's desired role is a G node.
  • using a 1-bit symbol “0” indicates that the role expected by the first device is negotiable
  • using a 1-bit symbol "1” indicates that the role expected by the first device is non-negotiable.
  • a 1-bit symbol “1” is used to indicate that the role expected by the first device is negotiable, and a 1-bit symbol "0" is used to indicate that the role expected by the first device is non-negotiable. This embodiment of the present application does not specifically limit this.
  • the first indication information may be a combination of a GT flag and information indicating that the first device requests to acquire and/or allocate air interface resources; or, the first indication information may be a combination of a GT flag and information indicating that the first device requests to acquire and/or allocate air interface resources; A combination of capability information; alternatively, the first indication information may be a combination of a GT flag and information indicating that the first device or the second device configures a system management frame; or the first indication information may be a combination of a GT flag and information indicating that the second device configures a system management frame A combination of information for sending the first connection information; alternatively, the first indication information may be a combination of the GT flag and information for instructing the first device to send the second connection information.
  • the GT flag may be used to indicate whether the role expected by the first device is negotiable.
  • the GT flag may use a 1-bit symbol "0" to indicate that the role expected by the first device is negotiable, and use "1" to indicate that the role expected by the first device is non-negotiable; or, the symbol "1" may be used to indicate that the role expected by the first device is non-negotiable.
  • the role expected by a device is negotiable.
  • the symbol "0" indicates that the role expected by the first device is non-negotiable. This is not specifically limited in the embodiment of the present application.
  • the first indication information may be a combination of information indicating that the first device requests to acquire and allocate air interface resources and capability information of the first device; or, the first indication information may be an indication that the first device requests to acquire and allocate air interface resources.
  • the information indicating that the first device requests to acquire and allocate air interface resources may be used to indicate that the role expected by the first device is negotiable. Since the first device can both obtain air interface resources and allocate air interface resources, it can be indicated that the desired role of the first device is negotiable.
  • the access request message includes third indication information, and the third indication information is used to indicate the role expected by the second device and whether the role expected by the second device is negotiable. That is, in this embodiment of the present application, the first device can explicitly inform the second device of the role expected by the first device and whether it is negotiable, and the second device can explicitly inform the first device of the role expected by the second device and whether it is negotiable.
  • the principle of the third indication information is similar to the above-mentioned first indication information.
  • the third indication information may be a GT flag, which uses a 2-bit symbol to indicate the role expected by the second device and whether the role expected by the second device is negotiable.
  • GT flag which uses a 2-bit symbol to indicate the role expected by the second device and whether the role expected by the second device is negotiable.
  • the access response message is used to indicate that the second device accesses successfully in the role expected by the second device.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles do not conflict, the second device can successfully access in its expected role.
  • the access response message is used for Instructing the second device to fail to access in the role expected by the second device.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and the role expected by the first device and the role expected by the second device are non-negotiable, the second device fails to access in its expected role.
  • the access response message is used to indicate the third device.
  • the second device successfully accesses the device in a role other than the role expected by the second device.
  • the second device when the first device explicitly informs the second device of the role expected by the first device, and the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and the role expected by the first device is non-negotiable and the role expected by the second device is negotiable, the second device can successfully access in a role other than the role expected by the second device.
  • the access response message is used Instructing the second device to fail to access in the role expected by the second device.
  • the second device when the first device explicitly informs the second device of the role expected by the first device, and the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and the role expected by the first device is non-negotiable and the role expected by the second device is negotiable, the second device fails to access in the role expected by the second device.
  • the access response message is used to indicate the third device.
  • the second device successfully accesses in the role expected by the second device.
  • the first device explicitly informs the second device of the role expected by the first device
  • the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and the first device's expected role is negotiable, the second device can successfully access in its expected role. Since the embodiment of the present application allows the scanner and the broadcaster to negotiate the GT role, the GT role setting during the access process is more flexible and can adapt to actual business needs.
  • the access response message is used to indicate the third device.
  • the second device successfully accesses in a role expected by the second device, or the access response message is used to indicate that the second device successfully accesses in a role other than the role expected by the second device.
  • the first device when the first device explicitly informs the second device of the role expected by the first device, and the second device explicitly informs the first device of the role expected by the second device, if the first device and the second device If the expected roles conflict and both the role expected by the first device and the role expected by the second device are negotiable, the second device can successfully access in its expected role, or the second device can successfully access in a role other than the role expected by the second device.
  • the role access is successful, and the embodiment of this application does not specifically limit this.
  • the second device (scanner) is allowed to become a T node, and the first device (broadcaster) is allowed to become a G node, therefore after the scanner becomes a T node, it does not need to use its own air interface resources to allocate corresponding signals to the broadcaster.
  • the air interface resources can not only alleviate the high proportion of air interface resources of the second device caused by accessing a large number of first devices, so that the second device can still complete the access normally after accessing a large number of first devices, but also When the air interface resources of the second device are in a high proportion, the second device can also access more first devices.
  • the embodiment of the present application allows the second device to determine whether it agrees with the first device to become the role expected by the first device. Therefore, if the second device does not agree, the second device may not send an access request message to the first device. , which can reduce energy consumption and save network resource overhead.
  • the method of sending and receiving information provided by the embodiment of the present application further It includes: when the first device determines that the second device cannot access the first device according to the access request message, the first device gives up sending the access response message to the second device. Further, if the second device does not receive the access response message from the first device within the second time resource, the second device determines that the connection between the first device and the second device fails. That is to say, if the first device cannot accept the role expected by the second device, the first device may inform the second device of the failure of the connection between the first device and the second device by not sending an access response. In this way, network resources and energy overhead for sending access response messages can be saved.
  • both the first device and the second device in the above embodiment can adopt the architecture of the communication device 400 shown in Figure 4, therefore, the action of the first device in the above embodiment can be performed by the communication device shown in Figure 4.
  • the processor 401 in the communication device 400 calls the application program code stored in the memory 403 to instruct the first device to execute.
  • the actions of the second device in the above embodiment can be called by the processor 401 in the communication device 400 shown in Figure 4.
  • the stored application code is used to instruct the second device to execute, and this embodiment does not impose any limitation on this.
  • the methods and/or steps implemented by the first device can also be implemented by components (such as chips or circuits) that can be used in the first device; the methods and/or steps implemented by the second device can also be implemented by components (such as chips or circuits) that can be used in the first device. or steps, may also be implemented by components (such as chips or circuits) that can be used in the second device.
  • embodiments of the present application also provide a communication device, which is used to implement the above various methods.
  • the communication device may be the first device in the above method embodiment, or a device including the above first device, or a component that can be used in the first device; or the communication device may be the second device in the above method embodiment. , or a device that includes the above-mentioned second device, or a component that can be used in the second device.
  • the communication device includes corresponding hardware structures and/or software modules for performing each function.
  • Embodiments of the present application can divide the communication device into functional modules according to the above method embodiments.
  • each functional module can be divided corresponding 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 software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • FIG 8 shows a schematic structural diagram of a communication device 800.
  • Communication device 800 includes a transceiver 801 .
  • the transceiver 801 may also be called a transceiver unit to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver or a communication interface.
  • the communication device 800 may include a processor 802.
  • the processor 802 is used to generate a broadcast message; the transceiver 801 is used to send a broadcast message to the second device.
  • the broadcast message includes first indication information, and the first indication information is used to indicate a role expected by the first device.
  • the expected role of the first device is G node or T node.
  • the transceiver 801 is also used to receive an access request message from the second device; the transceiver 801 is also used to send an access response message to the second device.
  • the access request message is used by the second device to request access to the first device.
  • the access response message is used to indicate that the second device has successfully accessed or failed to access.
  • the access request message includes second indication information, and the second indication information is used to indicate a role expected by the second device.
  • the expected role of the second device is G node or T node.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message is used to indicate that the second device fails to access in the role expected by the second device.
  • the first indication information is also used to indicate whether the role expected by the first device is negotiable.
  • the access request message includes third indication information, and the third indication information is used to indicate a role expected by the second device and whether the role expected by the second device is negotiable.
  • the expected role of the second device is G node or T node.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message Used to indicate that the second device failed to access in the role expected by the second device.
  • the access response message Used to indicate that the second device has successfully accessed in a role other than the role expected by the second device.
  • the access response message Used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message It is used to indicate that the second device has successfully accessed in a role expected by the second device, or the access response message is used to indicate that the second device has successfully accessed in a role other than the role expected by the second device.
  • the processor 802 is also configured to determine whether the access request message from the second device is received by the transceiver 801 within the first time resource. The connection failed.
  • the access request message when the expected role of the second device is a G node, the access request message also includes first connection information, and the first connection information includes one or more of the following provided by the second device: Local clock, time offset, access address, frequency hopping map, initial value of CRC code, connection state period, or connection state timeout time.
  • the access response message when used to indicate that the second device has successfully accessed in the role of T node, the access response message also includes second connection information, and the second connection information includes the first device.
  • the second connection information includes the first device. Provide one or more of the following: local clock, time offset, access address, frequency hopping map, CRC code initial value, connection state period, or connection state timeout.
  • the transceiver 801 is used to receive broadcast messages from the first device.
  • the broadcast message includes first indication information, and the first indication information is used to indicate a role expected by the first device.
  • the expected role of the first device is G node or T node.
  • the transceiver 801 is also used to send an access request message to the first device when the processor 802 determines to request access to the first device based on the broadcast message; the transceiver 801 is also used to receive Access response message from the first device.
  • the access request message is used by the second device to request access to the first device.
  • the access response message is used to indicate successful access or access failure of the second device.
  • the access request message includes second indication information, and the second indication information is used to indicate a role expected by the second device.
  • the expected role of the second device is G node or T node.
  • the The incoming response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message is used to indicate that the second device fails to access in the role expected by the second device.
  • the first indication information is also used to indicate whether the role expected by the first device is negotiable.
  • the access request message includes third indication information, and the third indication information is used to indicate a role expected by the second device and whether the role expected by the second device is negotiable.
  • the expected role of the second device is G node or T node.
  • the access response message is used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message Used to indicate that the second device failed to access in the role expected by the second device.
  • the access response message Used to indicate that the second device has successfully accessed in a role other than the role expected by the second device.
  • the access response message Used to indicate that the second device has successfully accessed in the role expected by the second device.
  • the access response message It is used to indicate that the second device has successfully accessed in a role expected by the second device, or the access response message is used to indicate that the second device has successfully accessed in a role other than the role expected by the second device.
  • the processor 802 is also configured to determine whether the second device is connected to the first device when the transceiver 801 does not receive an access response message from the first device within the second time resource. The connection failed.
  • the access request message when the expected role of the second device is a G node, the access request message also includes first connection information, and the first connection information includes one or more of the following provided by the second device: Local clock, time offset, access address, frequency hopping map, initial value of CRC code, connection state period, or connection state timeout time.
  • the access response message when used to indicate that the second device has successfully accessed in the role of T node, the access response message also includes second connection information, and the second connection information includes the first device.
  • the second connection information includes the first device. Provide one or more of the following: local clock, time offset, access address, frequency hopping map, CRC code initial value, connection state period, or connection state timeout.
  • the communication device 800 is presented in the form of dividing various functional modules in an integrated manner.
  • a “module” here may refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuits, and/or other devices that may provide the above functions.
  • the communication device 800 is the first device or the second device in the above method embodiment, in a simple embodiment, those skilled in the art can imagine that the communication device 800 can adopt the communication device 400 shown in Figure 4 form.
  • the processor 401 or the processor 407 in the communication device 400 shown in FIG. 4 can cause the communication device 400 to execute the method of sending and receiving information in the above method embodiment by calling the computer execution instructions stored in the memory 403.
  • the function/implementation process of the processor 802 in Figure 8 can be implemented by the processor 401 or 407 in the communication device 400 shown in Figure 4 calling the computer execution instructions stored in the memory 403.
  • the function/implementation process of the transceiver 801 in FIG. 8 can be implemented by a communication module connected via the communication interface 404 in FIG. 4 .
  • the communication device 800 provided in this embodiment can perform the above-mentioned method of sending and receiving information, the technical effects it can obtain can be referred to the above-mentioned method embodiments, which will not be described again here.
  • the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built into an SoC (System on a Chip) or ASIC, or it can be an independent semiconductor chip.
  • SoC System on a Chip
  • ASIC Application Specific integrated circuit
  • the processor may further include necessary hardware accelerators, such as field programmable gate array (FPGA), PLD (programmable logic device) , or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD programmable logic device
  • the hardware can be a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, Any one or any combination of SoC, FPGA, PLD, dedicated digital circuits, hardware accelerators or non-integrated discrete devices, which can run the necessary software or not rely on software to perform the above method flow.
  • DSP digital signal processing
  • MCU microcontroller unit
  • embodiments of the present application also provide a chip system, including: at least one processor and an interface.
  • the at least one processor is coupled to the memory through the interface.
  • the at least one processor executes the computer program or instructions in the memory
  • the communication device further includes a memory.
  • the chip system may be composed of chips, or may include chips and other discrete devices, which is not specifically limited in the embodiments of the present application.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it 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.
  • computer program instructions When computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or include one or more data storage devices such as servers and data centers that can be integrated with the medium.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (SSD)), etc.

Landscapes

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

Abstract

本申请实施例提供发送与接收信息的方法、通信装置及系统，可以在扫描方需要接入大量广播方的情况下使得扫描方依然可以正常完成接入。方法包括：第一设备生成广播消息，并向第二设备发送该广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示第一设备期望的角色。该第一设备期望的角色为主控节点或终端节点。

Description

发送与接收信息的方法、通信装置及系统
本申请要求于2022年08月24日提交国家知识产权局、申请号为202211020745.5、申请名称为“发送与接收信息的方法、通信装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及短距离通信领域，尤其涉及发送与接收信息的方法、通信装置及系统。
背景技术
在蓝牙(bluetooth，BT)通信系统中，可以将通信系统中的设备分为广播方(advertiser)和扫描方(scanner)。其中，扫描方在扫描窗口(scan window)接收广播方发送的广播信息，进而与广播方建立连接。传统蓝牙协议规定，扫描方作为主控节点(grant node，G节点)，广播方作为终端节点(terminal node，T节点)。其中，G节点管理T节点，负责为T节点分配空口资源；T节点听从G节点的调度，使用G节点分配的空口资源与G节点进行通信。
目前，扫描方需保证扫描窗口至少覆盖一个广播间隔(advertising interval)才能接收到广播方的广播信息从而完成接入。然而，当扫描方需要接入大量广播方之后，由于扫描方为扫描窗口分配的时间资源有限，因此扫描方接收到广播信息的概率变小，从而会导致扫描方接入广播方的概率降低。如果提高广播方的广播频率，可以提高扫描方接收到广播信息的概率，但这样会导致广播方的功耗变大。因此，如何在扫描方需要接入大量广播方的情况下使得扫描方依然可以正常完成接入，是目前亟待解决的问题。
发明内容
本申请实施例提供的发送与接收信息的方法、通信装置及系统，可以在扫描方需要接入大量广播方的情况下使得扫描方依然可以正常完成接入。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供一种发送信息的方法，该方法可以由第一设备执行，也可以由第一设备的部件，例如第一设备的处理器、芯片、或芯片系统等执行，还可以由能实现全部或部分第一设备功能的逻辑模块或软件实现。以下以该方法由第一设备执行为例进行说明。该方法包括：第一设备生成广播消息，并向第二设备发送广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示第一设备期望的角色。该第一设备期望的角色为主控节点(G节点)或终端节点(T节点)。由于本申请实施例中，广播方(第一设备)通过广播消息中的第一指示信息向扫描方(第二设备)发送广播方期望的角色，可以告知扫描方广播接入广播方时广播方期望的角色，进而可以允许广播方成为G节点，扫描方成为T节点。这样，扫描方成为T节点之后，不需要使用自身的空口资源为广播方分配相应的空口资源，不仅可以缓解扫描方因接入大量广播方而导致自身空口资源处于高占比的状态，使得扫描方接入大量广播方之后依然可以正常完成接入，而且在扫描方的空口资源处于高占比状态的情况下，扫描方还可以接入更多的广播方。
结合上述第一方面，在一种可能的实现方式中，该方法还包括：第一设备接收来自第二设备的接入请求消息，该接入请求消息用于第二设备请求接入第一设备；第一设备向第二设备发送接入应答消息，该接入应答消息用于指示第二设备接入成功或接入失败。
结合上述第一方面，在一种可能的实现方式中，该方法还包括：在第一设备在第一时间资源内未接收到来自第二设备的接入请求消息的情况下，第一设备确定第一设备与第二设备之间连接失败。换言之，本申请实施例中，第一设备可以通过识别是否在设定时间内接收到来自第二设备的接入请求消息来确定第一设备与第二设备之间是否连接成功。
第二方面，提供一种接收信息的方法，该方法可以由第二设备执行，也可以由第二设备的部件，例如第二设备的处理器、芯片、或芯片系统等执行，还可以由能实现全部或部分第二设备功 能的逻辑模块或软件实现。以下以该方法由第二设备执行为例进行说明。该方法包括：第二设备接收来自第一设备的广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示第一设备期望的角色。该第一设备期望的角色为G节点或T节点。由于本申请实施例中，广播方(第一设备)通过广播消息中的第一指示信息向扫描方(第二设备)发送广播方期望的角色，可以告知扫描方广播接入广播方时广播方期望的角色，进而可以允许扫描方成为T节点，广播方成为G节点，这样扫描方成为T节点之后，不需要使用自身的空口资源为广播方分配相应的空口资源，不仅可以缓解扫描方因接入大量的广播发而导致自身空口资源处于高占比的状态，使得扫描方接入大量广播方之后依然可以正常完成接入，而且在扫描方的空口资源处于高占比状态的情况下，扫描方还可以接入更多的广播。
结合上述第二方面，在一种可能的实现方式中，该方法还包括：在第二设备根据广播消息确定请求接入第一设备的情况下，第二设备在第一时间资源内向第一设备发送接入请求消息，接入请求消息用于第二设备请求接入第一设备；第二设备接收来自第一设备的接入应答消息，该接入应答消息用于指示第二设备接入成功或者接入失败。
结合上述第二方面，在一种可能的实现方式中，该方法还包括：在第二设备在第二时间资源内未接收到来自第一设备的接入应答消息的情况下，第二设备确定第二设备与第一设备之间连接失败。换言之，本申请实施例中，第二设备可以通过识别是否在设定时间内接收到来自第一设备的接入应答消息来确定第一设备与第二设备之间是否连接成功。
结合上述第一方面或第二方面，在一种可能的实现方式中，接入请求消息包括第二指示信息，该第二指示信息用于指示第二设备期望的角色。其中，第二设备期望的角色为G节点或T节点。即，本申请实施例中，第一设备可以明确告知第二设备第一设备期望的角色，第二设备可以明确告知第一设备第二设备期望的角色。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色不冲突，则第二设备可以成功以自己期望的角色接入。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突但是第一设备同意成为第一设备期望的角色之外的角色，则第二设备可以成功地以自己期望的角色接入。
示例性的，若第一设备期望的角色和第二设备期望的角色均为G节点，并且接入应答消息用于指示第二设备以第二设备期望的角色接入成功，则第一设备成为T节点。若第一设备期望的角色和第二设备期望的角色均为T节点，并且接入应答消息用于指示第二设备以第二设备期望的角色接入成功，则第一设备成为G节点。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突但是第一设备不同意第二设备成为第二设备期望的角色，则第二设备以自己期望的角色接入失败。
可选地，接入应答消息用于指示第二设备以第二设备期望的角色接入失败可以是指第二设备接入第一设备失败；或者，可以是指第二设备以第二设备期望的角色之外的角色接入第一设备。
示例性的，以第二设备期望的角色之外的角色接入第一设备为例说明第二设备以第二设备期望的角色接入失败。若第一设备期望的角色和第二设备期望的角色均为G节点，则第二设备以T节点接入第一设备。若第一设备期望的角色和第二设备期望的角色均为T节点，则第二设备以G节点接入第一设备。
结合上述第一方面或第二方面，在一种可能的实现方式中，第一指示信息还用于指示第一设 备期望的角色是否可协商。由于第一指示信息可以明确第一设备期望的角色是否可以协商，因此第二设备可以根据第一指示信息确定是否向第一设备发送接入请求消息。例如，在第一设备期望的角色与第二设备期望的角色相同，且第一指示信息指示第一设备期望的角色不可协商的情况下，第二设备可以确定不向第一设备发送接入请求消息。如此，可以节省信令开销以及节省功耗。
结合上述第一方面或第二方面，在一种可能的实现方式中，第一指示信息还可以用于指示第一设备期望第二设备成为的角色。换言之，第一设备可以通过广播消息中的第一指示信息告知第二设备广播接入第一设备时第一设备期望第二设备成为的角色。
结合上述第一方面或第二方面，在一种可能的实现方式中，接入请求消息包括第三指示信息，第三指示信息用于指示第二设备期望的角色且第二设备期望的角色是否可协商，其中，第二设备期望的角色为G节点或T节点。即，本申请实施例中，第一设备可以明确告知第二设备第一设备期望的角色以及是否可协商，第二设备可以明确告知第一设备第二设备期望的角色以及是否可协商。
结合上述第一方面或第二方面，在一种可能的实现方式中，第三指示信息还可以用于指示第二设备期望第一设备成为的角色。换言之，第二设备可以通接入请求消息中的第三指示信息告知第一设备与第二设备建立连接时第二设备期望第一设备成为的角色。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色不冲突，则第二设备可以成功以自己期望的角色接入。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及所述第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色以及第二设备期望的角色不可协商，则第二设备以自己期望的角色接入失败。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色不可协商以及第二设备期望的角色可协商，则第二设备可以以第二设备期望的角色之外的角色接入成功。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色可协商，则第二设备可以成功以自己期望的角色接入。由于本申请实施例中允许扫描方与广播方之间对GT角色进行协商，使得接入过程中GT角色设置更灵活，可以适应实际业务的需求。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功，或者接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色以及第二设备期望的角色均可协商，则第二设备可以成功以自己期望的角色接入，或者第二设备可以以第二设备期望的角色之外的角色接入成功。
结合上述第一方面或第二方面，在一种可能的实现方式中，在第二设备期望的角色为G节点的情况下，接入请求消息还包括第一连接信息。其中，第一连接信息包括第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、循环冗余校验CRC码初始值、连接态周期、或者连接态超时时间。
结合上述第一方面或第二方面，在一种可能的实现方式中，在接入应答消息用于指示第二设备以终端节点的角色接入成功的情况下，接入应答消息还包括第二连接信息。其中，第二连接信息包括第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
第三方面，提供了一种通信装置用于实现上述方法。该通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
结合上述第三方面，在一种可能的实现方式中，该通信装置为蓝牙芯片或者第一设备，该通信装置包括：收发器和处理器；该处理器，用于生成广播消息；该收发器，用于向第二设备发送该广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示该通信装置期望的角色。该通信装置期望的角色为G节点或T节点。
结合上述第三方面，在一种可能的实现方式中，该收发器，还用于接收来自第二设备的接入请求消息；该收发器，还用于向第二设备发送接入应答消息。其中，接入请求消息用于第二设备请求接入第一设备。接入应答消息用于指示第二设备接入成功或者接入失败。
结合上述第三方面，在一种可能的实现方式中，接入请求消息包括第二指示信息，第二指示信息用于指示第二设备期望的角色。其中，第二设备期望的角色为G节点或T节点。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。
结合上述第三方面，在一种可能的实现方式中，第一指示信息还用于指示该通信装置期望的角色是否可协商。
结合上述第三方面，在一种可能的实现方式中，接入请求消息包括第三指示信息，第三指示信息用于指示第二设备期望的角色且第二设备期望的角色是否可协商。其中，第二设备期望的角色为G节点或T节点。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色相同，并且该通信装置期望的角色不可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色相同，并且该通信装置期望的角色不可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色相同，并且该通信装置期望的角色可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色与该通信装置期望的角色相同，并且该通信装置期望的角色可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功，或者接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。
结合上述第三方面，在一种可能的实现方式中，该处理器，还用于在该收发器在第一时间资 源内未接收到来自第二设备的接入请求消息的情况下，确定该通信装置与第二设备之间连接失败。
结合上述第三方面，在一种可能的实现方式中，在第二设备期望的角色为G节点的情况下，接入请求消息还包括第一连接信息，第一连接信息包括第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
结合上述第三方面，在一种可能的实现方式中，在接入应答消息用于指示第二设备以T节点的角色接入成功的情况下，接入应答消息还包括第二连接信息，第二连接信息包括该通信装置提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
其中，第三方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面的不同实现方式所带来的技术效果，此处不再赘述。
第四方面，提供了一种通信装置用于实现上述方法。该通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
结合上述第四方面，在一种可能的实现方式中，该通信装置为蓝牙芯片或者第二设备，该通信装置包括：收发器；该收发器，用于接收来自第一设备的广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示第一设备期望的角色。第一设备期望的角色为G节点或T节点。
结合上述第四方面，在一种可能的实现方式中，该通信装置还包括处理器；该收发器，还用在该处理器根据广播消息确定请求接入第一设备的情况下，向第一设备发送接入请求消息；该收发器，还用于接收来第一设备的接入应答消息。其中，接入请求消息用于该通信装置请求接入第一设备。该接入应答消息用于指示该通信装置接入成功或接入失败。
结合上述第四方面，在一种可能的实现方式中，接入请求消息包括第二指示信息，第二指示信息用于指示该通信装置期望的角色。其中，该通信装置期望的角色为G节点或T节点。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示该通信装置以该通信装置期望的角色接入成功。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示该通信装置以该通信装置期望的角色接入成功。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示该通信装置以该通信装置期望的角色接入失败。
结合上述第四方面，在一种可能的实现方式中，第一指示信息还用于指示第一设备期望的角色是否可协商。
结合上述第四方面，在一种可能的实现方式中，接入请求消息包括第三指示信息，第三指示信息用于指示该通信装置期望的角色且该通信装置期望的角色是否可协商。其中，该通信装置期望的角色为G节点或T节点。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示该通信装置以该通信装置期望的角色接入成功。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及该通信装置期望的角色不可协商的情况下，接入应答消息用于指示该通信装置以该通信装置期望的角色接入失败。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及该通信装置期望的角色可协商的情况下，接入应答消息用于指示该通信装置以该通信装置期望的角色之外的角色接入成功。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及该通信装置期望的角色不可协商的情况下，接入应答消息用于指示该通信装置以该通信装置期望的角色接入成功。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及该通信装置期望的角色可协商的情况下，接入应 答消息用于指示该通信装置以该通信装置期望的角色接入成功，或者接入应答消息用于指示该通信装置以该通信装置期望的角色之外的角色接入成功。
结合上述第四方面，在一种可能的实现方式中，该处理器，还用于在该收发器在第二时间资源内未接收到来自第一设备的接入应答消息的情况下，确定该通信装置与第一设备之间连接失败。
结合上述第四方面，在一种可能的实现方式中，在该通信装置期望的角色为G节点的情况下，接入请求消息还包括第一连接信息，第一连接信息包括该通信装置提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
结合上述第四方面，在一种可能的实现方式中，在接入应答消息用于指示该通信装置以T节点的角色接入成功的情况下，接入应答消息还包括第二连接信息，第二连接信息包括第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
其中，第四方面中任一种可能的实现方式所带来的技术效果可参见上述第二方面的不同实现方式所带来的技术效果，此处不再赘述。
第五方面，提供了一种通信系统，包括上述一个或多个上述第三方面所述的通信装置，以及一个或多个上述第四方面所述的通信装置。
第六方面，提供了一种通信装置，包括：处理器；该处理器用于与存储器耦合，并读取存储器中存储的计算机指令之后，根据该指令执行如上述第一方面所述的方法。
结合上述第六方面，在一种可能的实现方式中，通信装置还包括存储器；该存储器用于存储计算机指令。
结合上述第六方面，在一种可能的实现方式中，通信装置还包括通信接口；该通信接口用于该通信装置与其它设备或装置进行通信。示例性的，该通信接口可以为收发器、输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。
结合上述第六方面，在一种可能的实现方式中，该通信装置可以是芯片或芯片系统。其中，当该通信装置是芯片系统时，该通信装置可以由芯片构成，也可以包含芯片和其他分立器件。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面或第二方面所述的方法。
第八方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面或第二方面所述的方法。
其中，第五方面至第八方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面或第二方面的不同实现方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种广播扫描流程示意图；
图2为本申请实施例提供的一种广播接入流程示意图；
图3为本申请实施例提供的一种通信系统的架构示意图；
图4为本申请实施例提供的通信装置的结构示意图一；
图5为本申请实施例提供的一种发送与接收信息的方法流程示意图一；
图6为本申请实施例提供的一种发送与接收信息的方法流程示意图二；
图7为本申请实施例提供的一种第二设备接入第一设备的流程示意图；
图8为本申请实施例提供的通信装置的结构示意图二。
具体实施方式
为方便理解本申请实施例提供的技术方案，首先给出本申请相关技术或名词的简要介绍。简要介绍如下：
第一，信道
信道(channel，CH)为广播方与扫描方之间消息传输的通道。扫描方和广播方可以工作于非授权频段，例如工业、科学和医疗(industrial scientific medical，ISM)频段。以ISM频段中的2.4GHz频段(2400～2483.5MHz)为例，2.4GHz频段可以划分为40个信道，相邻两个信道的间隔 为2MHz。其中，信道的索引范围为0～39，CH37～CH39为广播信道，CH0～CH36为数据信道。上述40个信道的相关描述可以参见表一。
表一
本申请实施例中，广播方和扫描方还可以工作于其他频段，本申请实施例对此不作具体限定。
第二，广播接入
广播接入可以是指扫描方通过广播消息发现广播方，并根据广播消息向广播方发起接入请求，进而与广播方建立连接的过程。
需要说明的是，“广播方”还可以称为“广播端”或者“广播设备”；“扫描方”还可以称为“扫描端”或者“接入设备”，在此统一说明，以下不再赘述。
以蓝牙通信系统的扩展广播方式为例，广播消息可以包括拓展广播包(adv_ext_ind)和拓展数据包(aux_adv_ind)。其中，拓展广播包用于扫描方发现广播方，以及发现拓展数据包。拓展数据包可以包括广播方的能力信息，以用于扫描方确定是否向广播方发送接入请求。
应理解，本申请实施例中，拓展数据包的位置可以包括传输拓展数据包的信道、接收拓展数据包的时域资源和/或频域资源等，本申请实施例对此不做具体限定。
应理解，本申请实施例中，广播方的能力信息可以包括以下一项或多项：广播方支持的调制方式、支持的信道带宽、或者是否支持信道编码等，本申请实施例对此不做具体限定。
下面结合图1和图2，示例性说明广播接入流程。
图1示出了广播扫描流程。如图1所示，广播方在广播间隔内发送拓展广播包。相应地，扫描方可以在扫描窗口接收来自广播方的拓展广播包。其中，广播方可以在一个或多个广播信道上发送拓展广播包。可以理解，扫描方在扫描窗口内监听是否接收到来自广播方的拓展数据包，可以避免扫描方一直处于监听状态，进而节省扫描方的功耗。
以广播方在三个广播信道上发送拓展广播包为例，广播方可以在广播信道A、广播信道B、以及广播信道C上依次发送拓展广播包。其中，广播方在广播信道A上发送拓展广播包A，之后广播方在广播信道B上发送拓展广播包B，接着广播方在广播信道C上发送拓展广播包C。广播 信道A、广播信道B、以及广播信道C可以是上述表一中的CH37～CH39中的任意广播信道，由于三个广播信道之间至少间隔24MHz，同时被干扰的概率较小，因此在三个广播信道轮流发送拓展广播包可以提高扫描方接收到拓展广播包的概率。
可选地，本申请实施例中，拓展广播包可以携带辅助指针(auxiliary pointer，AuxPtr)。AuxPtr用于指示拓展数据包所在的位置。示例性的，拓展广播包A中的AuxPtr1、拓展广播包B中的AuxPtr2、以及拓展广播包C中的AuxPtr3均指示扫描方接收拓展数据包的位置。如此，扫描方可以根据AuxPtr接收拓展数据包。
可以理解，为提高扫描方接收到来自广播方的拓展广播包的概率，广播方可以在多个广播间隔上发送拓展广播包(图1仅示出一个广播间隔)。相应地，扫描窗口至少需要覆盖其中一个广播间隔，这样扫描方才能接收到来自广播方的拓展广播包。
进一步的，如图2所示，广播方在数据信道D上发送拓展数据包。相应地，扫描方根据拓展广播包中的AuxPtr指示的位置接收来自广播方的拓展数据包。其中，数据信道D可以是上述表一中CH0～CH36中任意一个数据信道。
在扫描方根据拓展广播包中的AuxPtr指示的位置接收来自广播方的拓展数据包之后，如图2所示，扫描方根据拓展数据包内的信息向广播方发送接入请求消息(conn_req)。相应地，广播方接收来自扫描方的接入请求消息。之后，广播方根据接入请求消息向扫描方发送接入应答消息(conn_rsp)。相应地，扫描方接收来自广播方的接入应答消息。其中，接入应答消息用于指示扫描方接入成功或接入失败。若扫描方接入成功，则扫描方成为G节点，广播方成为T节点。
需要说明的是，本申请实施例中，“接入请求消息”还可以称为“连接请求消息”，“接入应答消息”还可以称为“接入响应消息”或“连接响应消息”等，在此统一说明，以下不再赘述。
需要说明的是，本申请实施例中，“拓展广播包”还可以称为“扩展广播包”，“拓展数据包”还可以称为“扩展数据包”，在此统一说明，以下不再赘述。
第三，空口资源
空口资源包括时域资源和频域资源。扫描方成为G节点之后，需要为广播方(T节点)分配一定的空口资源，以便于扫描方与广播方进行数据交互。也就是说，一方面，扫描方接入广播方之后，扫描方的部分空口资源会被占用，进而随着接入的广播方数量增加，扫描方的空口资源处于高占比状态；另一方面，扫描方与广播方建立连接之后会进行业务数据的交互，若该业务数据的交互占用较多的空口资源，也会使得扫描方的空口资源处于高占比状态。然而，扫描方的空口资源处于高占比状态，使得图1和图2所示的广播接入方案存在以下问题：
一是扫描方接入广播方的概率低。如图1所示，在扫描方的空口资源处于高占空比状态的情况下，扫描方为扫描窗口分配的时间资源(窗长)有限，可能无法覆盖一个广播间隔，使得扫描方接收到来自广播方的拓展广播包的概率降低，扫描方可能需要多次开启扫描窗口才能接收到拓展广播包，导致扫描方无法及时接入广播方，影响用户体验。
二是扫描方接入的广播方的数量有限。扫描方的空口资源是有限的，在扫描方的空口资源处于高占空比状态的情况下，扫描方可能没有空闲的空口资源为广播方进行分配，因此扫描方无法接入广播方。
鉴于此，本申请实施例提供一种发送与接收信息的方法，可以在扫描方需要接入大量广播方的情况下使得扫描方依然可以正常完成接入，以及在扫描方的空口资源处于高占比状态的情况下提高接入广播方的数量。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的 技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
在本申请实施例中，“指示”可以包括直接指示和间接指示，也可以包括显式指示和隐式指示。将某一信息(如下文所述的用于指示第一设备和/或第二设备期望的角色的信息)所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
应理解，以下描述中“G节点”还可以称为“G角色”，“T节点”还可以称为“T角色”。换言之，“G节点”与“G角色”之间可以替换表述，“T节点”与“T角色”之间可以替换表述，在此统一说明，以下不再赘述。
此外，本申请实施例描述的通信架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着通信架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图3所示，为本申请实施例提供的一种通信系统的架构示意图。该通信系统包括第一设备和第二设备。其中，本申请实施例中，该通信系统可以包括多个第一设备和多个第二设备。该通信系统可以应用于车载电池管理、物联网(internet-of-things，IoT)、以及工业控制等场景。
一种可能的实现方式中，第一设备生成广播消息，并向第二设备发送广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示所述第一设备期望的角色。第一设备期望的角色为G节点或T节点。
上述方案的具体实现将在下述实施例中详细阐述，在此不再赘述。
由于本申请实施例中，广播方(第一设备)通过广播消息中的第一指示信息向扫描方(第二设备)发送广播方期望的角色，可以告知扫描方广播接入广播方时广播方期望的角色，进而可以允许广播方成为G节点，扫描方成为T节点。这样，扫描方成为T节点之后，不需要使用自身的空口资源为广播方分配相应的空口资源，不仅可以缓解扫描方因接入大量广播方而导致自身空口资源处于高占比的状态，使得扫描方接入大量广播方之后依然可以正常完成接入，而且在扫描方的空口资源处于高占比状态的情况下，扫描方还可以接入更多的广播方。
可选地，本申请实施例的第一设备和第二设备可以指具有数据收发处理能力的电子设备，可以包括终端设备，也可以是包含在终端设备中的芯片。例如，第一设备或第二设备可以为汽车座舱(cockpit domain)设备，或者汽车座舱设备中的一个模块，例如座舱域控制器(cockpit domain controller，CDC)、摄像头、屏幕、麦克风、音响、电子钥匙、无钥匙进入或启动控制器等模块中的一个或多个。在具体的实施例中，第一设备和第二设备还可以是数据中转设备，例如网络设备、路由器、中继器、桥接器或交换机。
可选地，本申请所涉及的通信技术可以是终端设备之间的通信技术，也可以是网络设备和终端设备之间的通信技术，还可以是网络设备和网络设备之间的通信技术，不具体限定通信双方的身份，能支持相应的通信技术和功能即可。
可选地，本申请实施例中的终端设备可以为各种类型的用户设备(user equipment，UE)、手机(mobile phone)、平板电脑(pad)、台式电脑、耳机、音响等；还可以包括机器智能设备，如无人驾驶(self driving)设备、运输安全(transportation safety)设备、虚拟现实(virtual reality，VR)终端设 备、增强现实(augmented reality，AR)终端设备、机器类型通信(machine type communication，MTC)设备、工业控制(industrial control)设备、远程医疗(remote medical)设备、智能电网(smart grid)设备、智慧城市(smart city)设备、智能家居设备等；还可以包括可穿戴设备(如智能手表，智能手环，计步器等)等等。
可选地，本申请实施例中的网络设备包括但不限于：演进型节点B(evolved node B，eNB)、无线网络控制器(Radio Network Controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved node B，或Home node B，HNB)、基带单元(base band unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，NR系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
需要说明，本申请实施例中，第一设备为广播方，但第一设备可以具备扫描方的扫描功能；第二设备为扫描方，但第二设备可以具备广播方的广播功能，本申请实施例对此不作具体限定。
可选地，本申请实施例中的第一设备或者第二设备的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的第一设备或者第二设备的相关功能可以通过图4中的通信装置400来实现。
图4所示为本申请实施例提供的通信装置400的结构示意图。通信装置400可以是第一设备或第二设备，也可以是应用于第一设备或第二设备中的芯片或者部件。
如图4所示，通信装置400包括处理器401，通信线路402，以及至少一个通信接口(图4中仅是示例性的以包括通信接口404，以及一个处理器401为例进行说明)，可选地还可以包括存储器403。
处理器401可以是一个CPU，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。
通信线路402可包括通路，用于连接不同组件。
通信接口404，可以是收发模块，用于与其他设备或通信网络通信，如以太网，RAN，WLAN等。例如，所述收发模块可以是收发器、收发机一类的装置。可选地，所述通信接口404也可以是位于处理器401内的收发电路，用以实现处理器的信号输入和信号输出。
存储器403可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路402与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器403用于存储执行本申请方案的计算机执行指令，并由处理器401来控制执行。处理器401用于执行存储器403中存储的计算机执行指令，从而实现本申请实施例中提供的发送与接收信息的方法。
或者，本申请实施例中，也可以是处理器401执行本申请下述实施例提供的发送与接收信息的方法中的处理相关的功能，通信接口404负责与其他设备或通信网络通信，本申请实施例对此 不作具体限定。
本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器401可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置400可以包括多个处理器，例如图4中的处理器401和处理器407。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，通信装置400还可以包括输出设备405和输入设备406。输出设备405和处理器401通信，可以以多种方式来显示信息。
上述的通信装置400可以是一个通用装置或者是一个专用装置。例如通信装置400可以是蓝牙耳机、台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端装置、车载终端装置、嵌入式设备或具有图4中类似结构的设备。本申请实施例不限定通信装置400的类型。
下面将结合图1至图4对本申请实施例提供的发送与接收信息的方法进行具体阐述。
需要说明的是，本申请下述实施例中各个设备之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
如图5所示，为本申请实施例提供的一种发送与接收信息的方法，该发送与接收信息的方法包括如下步骤：
S501、第一设备生成广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示所述第一设备期望的角色。第一设备期望的角色为G节点或T节点。
可选地，一种可能的实现方式中，第一指示信息可以是GT flag标志。示例性的，该GT flag标志可以使用1bit的符号“0”表示第一设备期望的角色为T节点，使用1bit的符号“1”表示第一设备期望的角色为G节点。或者，该GT flag标志可以使用1bit的符号“1”表示第一设备期望的角色为T节点，使用1bit的符号“0”表示第一设备期望的角色为G节点，本申请实施例对此不做具体限定。
或者，可选地，另一种可能的实现方式中，第一指示信息可以是指示第一设备请求获取和/或分配空口资源的信息。示例性的，若第一指示信息为用于指示第一设备请求获取空口资源的信息，则可以用于指示第一设备期望的角色为T节点；或者，若第一指示信息为空，则可以用于指示第一设备期望的角色为G节点；或者，若第一指示信息为用于指示第一设备请求为接入的设备分配空口资源的信息，则可以用于指示第一设备期望的角色为G节点；或者，若第一指示信息为空，则可以用于指示第一设备期望的角色为T节点。
或者，可选地，又一种可能的实现方式中，第一指示信息可以是指示第一设备的能力信息的信息。示例性的，该能力信息可以是第一设备是否支持为接入的设备分配资源，若该能力信息为第一设备支持为接入的设备分配资源，则第一指示信息用于指示第一设备期望的角色为G节点；或者，若该能力信息为不支持为接入的设备分配资源，则第一指示信息用于指示第一设备期望的角色为T节点。
或者，可选地，又一种可能的实现方式中，第一指示信息可以是指示第一设备或第二设备配置系统管理帧的信息。例如，若第一指示信息为指示第一设备配置系统管理帧的信息，则可以用于指示第一设备期望的角色为G节点；或者，若第一指示信息为指示第二设备配置系统管理帧的信息，则可以用于指示第一设备期望的角色为T节点。其中，系统管理帧用于G节点管理T节点。
或者，可选地，又一种可能的实现方式中，第一指示信息可以是指示第二设备发送第一连接信息的信息，或者指示第一设备发送第二连接信息的信息。其中，第一连接信息为第二设备提供的第二设备接入第一设备过程中所需要的连接信息。第二连接信息为第一设备提供的第二设备接入第一设备过程中所需要的连接信息。若第一指示信息为指示第二设备发送第一连接信息的信息， 则可以用于指示第一设备期望的角色为T节点；或者，若第一指示信息为指示第一设备发送第二连接信息的信息，则可以用于指示第一设备期望的角色为G节点。
示例性的，本申请实施例中，第二设备接入第一设备中所需要的连接信息可以包括但不限于：本地时钟、时间偏移、接入地址、跳频地图、循环冗余校验(cyclic redundancy check，CRC)码初始值、连接态周期、或者连接态超时时间等。其中，时间偏移可以用于指示第一设备与第二设备之间传输数据的时间资源。跳频地图可以用于确定第一设备和第二设备建立连接的频点。CRC码初始值用于CRC计算，CRC可以用于检测第一设备与第二设备之间传输的数据是否发生错误。连接态周期为第一设备与第二设备之间传输数据的周期。连接态超时时间可以用于指示第一设备与第二设备之间是否重新建立连接。例如，若第一设备在连接态超时时间内没有接收到来自第二设备的数据，则表示此次第一设备与第二设备之间建立的连接不稳定，需要重新建立连接。
也就是说，本申请实施例中，第一指示信息可以是GT flag标志，进而显式指示第一设备期望的角色。同时，第一指示信息可以是指示第一设备请求获取和/或分配空口资源的信息、指示第一设备的能力信息的信息、指示第一设备或第二设备配置系统管理帧的信息、指示第二设备发送第一连接信息的信息、或者指示第一设备发送第二连接信息的信息等，进而隐式指示第一设备期望的角色，本申请实施例对此不做具体限定。
S502、第一设备向第二设备发送广播消息。相应地，第二设备接收来自第一设备的广播消息。
可选地，本申请实施例中，第一设备可以在广播间隔内的一个或多个广播信道上向第二设备发送广播消息。相应地，第二设备可以在扫描窗口内接收来自第一设备的广播消息。
由于本申请实施例中，广播方(第一设备)通过广播消息中的第一指示信息向扫描方(第二设备)发送广播方期望的角色，可以告知扫描方广播接入广播方时广播方期望的角色，进而可以允许广播方成为G节点，扫描方成为T节点。这样，扫描方成为T节点之后，不需要使用自身的空口资源为广播方分配相应的空口资源，不仅可以缓解第二设备因接入大量的第一设备而导致自身空口资源处于高占比的状态，使得第二设备接入大量第一设备之后依然可以正常完成接入，而且在第二设备的空口资源处于高占比状态的情况下，第二设备还可以接入更多的第一设备。
其中，上述步骤S501～S502中第一设备的动作可以由图4所示的通信装置400中的处理器401调用存储器403中存储的应用程序代码以指令第一设备执行，上述步骤S501～S502中第二设备的动作可以由图4所示的通信装置400中的处理器401调用存储器403中存储的应用程序代码以指令第二设备执行，本实施例对此不作任何限制。
可选地，如图6所示，本申请实施例提供的发送与接收信息的方法，在步骤S502之后，还可以包括以下步骤：
S503、在第二设备根据广播消息确定请求接入第一设备的情况下，第二设备向第一设备发送接入请求消息，该接入请求消息用于第二设备请求接入第一设备。相应地，第一设备接收来自第二设备的接入请求消息。
或者，可选地，本申请实施例中，在第二设备根据广播消息确定请求接入第一设备的情况下，第二设备在第一时间资源内向第一设备发送接入请求消息，该接入请求消息用于第二设备请求接入第一设备。相应地，第一设备在第一时间资源内接收来自第二设备的接入请求消息。
可选地，本申请实施例中，第一时间资源可以是第一设备确定的。相应地，步骤S501中的广播消息指示第一时间资源。也就是说，第二设备可以根据广播消息确定第一时间资源，从而可以在第一时间资源内向第一设备发送接入请求消息。
可选地，本申请实施例中，广播消息可以通过显示方式指示第一时间资源。示例性的，广播消息可以包括第一时间资源的起始时刻和结束时刻。
或者，可选地，本申请实施例中，第一时间资源还可以是第一设备和第二设备提前协商好的；或者，协议约定第一时间资源，本申请实施例对此不作具体限定。
示例性的，以广播消息包括拓展广播包为例说明第二设备在第一时间资源内发送接入请求消息的流程。如图7所示，为第二设备接入第一设备的流程示意图。其中，第一时间资源的起始时刻与第一设备发送拓展数据包的起始时刻之间的时间间隔为接入请求的偏移量。第二设备可以在第一时间资源内发送一个或多个接入请求消息。相应地，第一设备可以在第一时间资源内接收来自 第二设备的接入请求消息。
S504、第一设备向第二设备发送接入应答消息。相应地，第二设备接收来自第一设备的接入应答消息。其中，接入应答消息用于指示第二设备接入成功或者接入失败。
或者，可选地，本申请实施例中，在第一设备在第一时间资源内接收到来自第二设备的接入请求消息的情况下，第一设备向第二设备发送接入应答消息。
可选地，第一设备可以在第二时间资源内发送接入应答消息。相应地，第二设备在第二时间资源内接收来自第一设备的接入应答消息。
可选地，本申请实施例中，第二时间资源可以是第二设备确定的。相应地，接入请求消息还可以指示第二时间资源。也就是说，第一设备可以根据接入请求消息确定第二时间资源，从而可以在第二时间资源内向第二设备发送接入应答消息。
可选地，接入请求消息可以通过显示方式指示第二时间资源。示例性的，接入请求消息可以包括第二时间资源的起始时刻和结束时刻。
或者，可选地，本申请实施例中，第二时间资源还可以是第一设备和第二设备提前协商好的；或者，协议约定第二时间资源，本申请实施例对此不作具体限定。
示例性的，再次参见图7，第一设备发送接入应答消息的起始时刻与第一设备发送拓展数据包的起始时刻之间的时间间隔为接入应答的偏移量。其中，接入应答的偏移量大于接入请求的偏移量与第一时间资源的时间长度之和。
可选地，本申请实施例中，接入请求消息用于指示第二设备同意以第一设备期望的角色之外的角色接入第一设备。相应地，接入应答消息用于指示第二设备接入成功。也就是说，第二设备可以确定第一设备和第二设备建立连接后，第一设备可以成为第一设备期望的角色。
或者，可选地，接入请求消息包括第二指示信息，该第二指示信息用于指示第二设备期望的角色。其中，第二设备期望的角色为G节点或T节点。即，本申请实施例中，第一设备可以明确告知第二设备第一设备期望的角色，第二设备可以明确告知第一设备第二设备期望的角色。
应理解，第二指示信息的具体形式与上述第一指示信息类似，例如第二指示信息可以是GT flag标志；或者，第二指示信息可以是指示第二设备请求获取和/或分配空口资源的信息、指示第二设备的能力信息的信息、指示第一设备或第二设备配置系统管理帧的信息、指示第二设备发送第一连接信息的信息、或者指示第一设备发送第二连接信息的信息等。第二指示信息的相关说明可以参见上述关于第一指示信息的描述，在此不再赘述。
可选地，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色不冲突，则第二设备可以成功以自己期望的角色接入。
可选地，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突但是第一设备同意成为第一设备期望的角色之外的角色，则第二设备可以成功以自己期望的角色接入。
或者，可选地，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突但是第一设备不同意第二设备成为第二设备期望的角色，则第二设备以自己期望的角色接入失败。
其中，第一设备可以根据实际应用场景确定是否同意第二设备以第二设备期望的角色接入第一设备。
示例性的，第一设备可以根据业务信息确定是否同意第二设备以第二设备期望的角色接入第一设备。业务信息可以是由应用(application)指示。若应用指示第一设备仅能成为T节点，在第二设备期望的角色为T节点的情况下，第一设备不同意第二设备以第二设备期望的角色接入第一 设备。例如，应用可以是音频播放应用，第一设备为音频播放设备，此时第一设备仅能成为T节点。
或者，示例性的，第一设备可以根据硬件信息确定是否同意第二设备以第二设备期望的角色接入第一设备。例如，第一设备为键盘、鼠标、手写笔等输入设备，第一设备仅能成为T节点，在第二设备期望的角色为T节点的情况下，第一设备不同意第二设备以第二设备期望的角色接入第一设备。
也就是说，第一设备与第二设备之间可以通过第一指示信息和第二指示信息对第一设备期望的角色和第二设备期望的角色进行指示，并由第一设备确定第二设备是否能够以第二设备期望的角色接入成功。
可选地，本申请实施例中，在第二设备期望的角色为G节点的情况下，接入请求消息还包括第一连接信息。其中，第一连接信息包括第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
可选地，本申请实施例中，在接入应答消息用于指示第二设备以T节点的角色接入成功的情况下，或者，在接入请求消息用于指示第二设备同意以第一设备期望的角色之外的角色接入第一设备，并且第一设备期望的角色为G节点的情况下，接入应答消息还包括第二连接信息，第二连接信息包括第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
示例性的，再次参见图7，在接入应答消息指示第二设备接入成功，且第一设备成为G节点以及第二设备为T节点的情况下，第一设备向第二设备发送系统管理帧。其中，第一设备发送系统管理帧的起始时刻与第一设备发送接入应答消息的起始时刻之间的时间间隔为系统管理帧的偏移量。或者，如图7所示，在接入应答消息指示第二设备接入成功，且第一设备成为T节点以及第二设备成为G节点的情况下，第二设备向第一设备发送系统管理帧。其中，第二设备发送系统管理帧的起始时刻与第一设备发送接入应答的起始时刻之间的时间间隔为系统管理帧的偏移量。
由于本申请实施例中，允许第二设备(扫描方)成为T节点，第一设备(广播方)成为G节点，因此扫描方成为T节点之后，不需要使用自身的空口资源为广播方分配相应的空口资源，不仅可以缓解第二设备因接入大量的第一设备而导致自身空口资源处于高占比的状态，使得第二设备接入大量第一设备之后依然可以正常完成接入，而且在第二设备的空口资源处于高占比状态的情况下，第二设备还可以接入更多的第一设备。
可选地，本申请实施例中的广播消息包括拓展广播包和拓展数据包。进一步的，S502可以包括：
S502a、第一设备在广播间隔内的一个或多个广播信道上向第二设备发送拓展广播包，以及在数据信道上向第二设备发送拓展数据包。相应地，第二设备在一个或多个广播信道上接收来自第一设备的拓展广播包，以及在数据信道上接收来自第一设备的拓展数据包。其中，拓展广播包和/或拓展数据包可以承载第一指示信息。
可以理解，S502a与具体实施例前序部分图2所示的方案类似，例如第一设备可以在广播信道A、广播信道B、以及广播信道C上依次发送拓展广播包，在数据信道D上发送拓展数据包。S502a的相关说明可以参见图2所示的方案，在此不再赘述。
可选地，本申请实施例中，AuxPtr可以指示拓展数据包所在的信道或频点、接收拓展数据包的时域资源、以及物理层信息等。接收拓展数据包的时域资源可以包括时钟精度、时钟单元、或者接收拓展数据包的时间偏移量等。物理层信息可以包括拓展数据包所使用的信道带宽、或者信道编码类型等。
应理解，在本申请实施例中，信道带宽可以理解为符号(symbol)速率，即信道带宽可以理解为单位时间内传输的符号数量。例如，信道带宽包括1MHz，2MHz，或者4MHz可以理解为符号速率包括1M symbol/s(每秒传输的symbol数为1M)，2M symbol/s，或者4M symbol/s。
可选地，本申请实施例中，拓展数据包可以包括用于指示可请求接入第一设备的设备的标识信息和/或第一设备的能力信息。其中，可请求接入第一设备的设备的标识信息用于标识可以请求与第一设备建立连接的设备的身份。示例性的，该标识信息可以包括可请求接入第一设备的设备 的媒体接入控制(media access control address，MAC)地址。
可选地，第一设备的能力信息可以用于指示以下一项或多项：第一设备支持的调制方式、第一设备支持的信道带宽、第一设备是否支持信道编码、或者第一设备支持的信道编码的类型。
示例性的，第一设备支持的调制方式可以包括高斯频移键控(gauss frequency shift keying，GFSK)调制方式和/或相移键控(phase shift keying，PSK)调制方式等。
示例性的，第一设备支持的信道带宽可以包括第一设备支持的总信道带宽，和/或跳频方式下每个跳频信道的信道带宽。
示例性的，第一设备支持的信道编码的类型包括polar码编码方式、里所码(reed-solomon codes，RS)编码方式、或者二进制的霍拉里斯代码(binary coded hollerith，BCH)编码方式等，本申请实施例对此不作具体限定。
其中，上述步骤S501～S504中第一设备的动作可以由图4所示的通信装置400中的处理器401调用存储器403中存储的应用程序代码以指令第一设备执行，上述步骤S501～S504中第二设备的动作可以由图4所示的通信装置400中的处理器401调用存储器403中存储的应用程序代码以指令第二设备执行，本实施例对此不作任何限制。
可选地，本申请实施例提供发送与接收信息的方法中，在第二设备接收来自第一设备的广播消息(步骤S502)之后，本申请实施例提供的发送与接收信息的方法还包括：在第二设备根据广播消息确定第二设备不能接入第一设备的情况下，第二设备放弃向第一设备发送接入请求消息。进一步的，在第一设备在第一时间资源内未接收到来自第二设备的接入请求消息的情况下，第一设备确定第一设备与第二设备之间连接失败，也放弃向第二设备发送接入应答消息。也就是说，若第二设备无法接受第一设备期望的角色，则第二设备可以通过不发送接入请求的方式告知第一设备第二设备与第一设备之间连接失败。如此，可以节省后续接入请求消息和接入应答消息的开销，也可以节省第一设备和第二设备的能量。
可选地，本申请实施例中，第一指示信息还用于指示第一设备期望的角色是否可协商。由于第一指示信息可以明确第一设备期望的角色是否可以协商，因此第二设备可以根据第一指示信息确定是否向第一设备发送接入请求消息。例如，在第一设备期望的角色与第二设备期望的角色相同，且第一指示信息指示第一设备期望的角色不可协商的情况下，第二设备可以确定不向第一设备发送接入请求消息。如此，可以节省信令开销以及节省功耗。
可选地，本申请实施例中，在第一指示信息还用于指示第一设备期望的角色是否可协商的情况下，第一指示信息可以是GT flag标志。示例性的，该GT flag标志可以使用2bit进行指示，其中1个比特用于指示第一设备期望的角色，另外一个比特用于指示第一设备期望的角色是否可协商。例如，高比特用于指示第一设备期望的角色，低比特用于指示第一设备期望的角色是否可协商；或者，低比特用于指示第一设备期望的角色，高比特用于指示第一设备期望的角色是否可协商。例如，使用1bit的符号“0”表示第一设备期望的角色为T节点，使用1bit的符号“1”表示第一设备期望的角色为G节点。或者，使用1bit的符号“1”表示第一设备期望的角色为T节点，使用1bit的符号“0”表示第一设备期望的角色为G节点。例如，使用1bit的符号“0”表示第一设备期望的角色可协商，使用1bit的符号“1”表示第一设备期望的角色不可协商。或者，使用1bit的符号“1”表示第一设备期望的角色可协商，使用1bit的符号“0”表示第一设备期望的角色不可协商，本申请实施例对此不做具体限定。
或者，可选地，第一指示信息可以是GT flag标志与指示第一设备请求获取和/或分配空口资源的信息的组合；或者，第一指示信息可以是GT flag标志与指示第一设备的能力信息的组合；或者，第一指示信息可以是GT flag标志与指示第一设备或第二设备配置系统管理帧的信息的组合；或者，第一指示信息可以是GT flag标志与指示第二设备发送第一连接信息的信息的组合；或者，第一指示信息可以是GT flag标志与指示第一设备发送第二连接信息的信息的组合。其中，GT flag标志可以用于表示第一设备期望的角色是否可协商。示例性的，该GT flag标志可以使用1bit的符号“0”表示第一设备期望的角色可协商，使用“1”表示第一设备期望的角色不可协商；或者，符号“1”用于表示第一设备期望的角色可协商，符号“0”表示第一设备期望的角色不可协商，本申请实施例对此不作具体限定。
或者，可选地，第一指示信息可以是指示第一设备请求获取和分配空口资源的信息与第一设备的能力信息的组合；或者，第一指示信息可以是指示第一设备请求获取和分配空口资源的信息与指示第一设备或第二设备配置系统管理帧的信息的组合；或者，第一指示信息可以是指示第一设备请求获取和分配空口资源的信息与指示第二设备发送第一连接信息的信息的组合；或者，第一指示信息可以是指示第一设备请求获取和分配空口资源的信息与指示第一设备发送第二连接信息的信息的组合。其中，指示第一设备请求获取和分配空口资源的信息可以用于表示第一设备期望的角色可协商。由于第一设备既可以获取空口资源，也可以分配空口资源，因此可以指示第一设备期望的角色可协商。
可选地，本申请实施例中，接入请求消息包括第三指示信息，第三指示信息用于指示第二设备期望的角色且第二设备期望的角色是否可协商。即，本申请实施例中，第一设备可以明确告知第二设备第一设备期望的角色以及是否可协商，第二设备可以明确告知第一设备第二设备期望的角色以及是否可协商。
应理解，第三指示信息的原理与上述第一指示信息类似，例如第三指示信息可以是GT flag标志，使用2bit的符号表示第二设备期望的角色和该第二设备期望的角色是否可协商。关于第三指示信息的相关说明，可以参见上述第一指示信息的相关介绍，在此不再赘述。
可选地，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色不冲突，则第二设备可以成功以自己期望的角色接入。
可选地，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及所述第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色以及第二设备期望的角色不可协商，则第二设备以自己期望的角色接入失败。
可选地，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色不可协商以及第二设备期望的角色可协商，则第二设备可以以第二设备期望的角色之外的角色接入成功。
或者，可选地，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色不可协商以及第二设备期望的角色可协商，则第二设备以第二设备期望的角色接入失败。
可选地，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色可协商，则第二设备可以成功以自己期望的角色接入。由于本申请实施例中允许扫描方与广播方之间对GT角色进行协商，使得接入过程中GT角色设置更灵活，可以适应实际业务的需求。
可选地，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功，或者接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。 换言之，本申请实施例中，在第一设备明确告知第二设备第一设备期望的角色，第二设备明确告知第一设备第二设备期望的角色的情况下，若第一设备与第二设备期望的角色冲突并且第一设备期望的角色以及第二设备期望的角色均可协商，则第二设备可以成功以自己期望的角色接入，或者第二设备可以以第二设备期望的角色之外的角色接入成功，本申请实施例对此不作具体限定。
由于本申请实施例中，允许第二设备(扫描方)成为T节点，第一设备(广播方)成为G节点，因此扫描方成为T节点之后，不需要使用自身的空口资源为广播方分配相应的空口资源，不仅可以缓解第二设备因接入大量的第一设备而导致自身空口资源处于高占比的状态，使得第二设备接入大量第一设备之后依然可以正常完成接入，而且在第二设备的空口资源处于高占比状态的情况下，第二设备还可以接入更多的第一设备。此外，本申请实施例中允许第二设备确定是否同意第一设备成为第一设备期望的角色，因此在第二设备不同意的情况下，第二设备可以不向第一设备发送接入请求消息，这样可以减少能量消耗和节省网络资源的开销。
可选地，本申请实施例提供发送与接收信息的方法中，在第一设备接收来自第二设备的接入请求消息(步骤S503)之后，本申请实施例提供的发送与接收信息的方法还包括：在第一设备根据接入请求消息确定第二设备不能接入第一设备的情况下，第一设备放弃向第二设备发送接入应答消息。进一步的，在第二设备在第二时间资源内未接收到来自第一设备的接入应答消息的情况下，第二设备确定第一设备与第二设备之间连接失败。也就是说，若第一设备无法接受第二设备期望的角色，则第一设备可以通过不发送接入应答的方式告知第二设备第一设备与第二设备之间连接失败。如此，可以节省发送接入应答消息的网络资源和能量开销。
其中，由于上述实施例中的第一设备和第二设备均可以采用如图4所示的通信装置400的架构，因此，上述实施例中第一设备的动作可以由图4所示的通信装置400中的处理器401调用存储器403中存储的应用程序代码以指令第一设备执行，上述实施例中第二设备的动作可以由图4所示的通信装置400中的处理器401调用存储器403中存储的应用程序代码以指令第二设备执行，本实施例对此不作任何限制。
可以理解的是，以上各个实施例中，由第一设备实现的方法和/或步骤，也可以由可用于第一设备的部件(例如芯片或者电路)实现；由第二设备实现的方法和/或步骤，也可以由可用于第二设备的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置用于实现上述各种方法。该通信装置可以为上述方法实施例中的第一设备，或者包含上述第一设备的装置，或者为可用于第一设备的部件；或者，该通信装置可以为上述方法实施例中的第二设备，或者包含上述第二设备的装置，或者为可用于第二设备的部件。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例中对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图8示出了一种通信装置800的结构示意图。通信装置800包括收发器801。所述收发器801，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机或者通信接口。可选地，该通信装置800可以包括处理器802。
以通信装置800为上述方法实施例中的第一设备为例，则：处理器802，用于生成广播消息；该收发器801，用于向第二设备发送广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示第一设备期望的角色。第一设备期望的角色为G节点或T节点。
一种可能的实现方式中，收发器801，还用于接收来自第二设备的接入请求消息；收发器801，还用于向第二设备发送接入应答消息。其中，接入请求消息用于第二设备请求接入第一设备。接入应答消息用于指示第二设备接入成功或者接入失败。
一种可能的实现方式中，接入请求消息包括第二指示信息，第二指示信息用于指示第二设备期望的角色。其中，第二设备期望的角色为G节点或T节点。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。
一种可能的实现方式中，第一指示信息还用于指示第一设备期望的角色是否可协商。
一种可能的实现方式中，接入请求消息包括第三指示信息，第三指示信息用于指示第二设备期望的角色且第二设备期望的角色是否可协商。其中，第二设备期望的角色为G节点或T节点。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功，或者接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。
一种可能的实现方式中，处理器802，还用于在收发器801在第一时间资源内未接收到来自第二设备的接入请求消息的情况下，确定第一设备与第二设备之间连接失败。
一种可能的实现方式中，在第二设备期望的角色为G节点的情况下，接入请求消息还包括第一连接信息，第一连接信息包括第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
一种可能的实现方式中，在接入应答消息用于指示第二设备以T节点的角色接入成功的情况下，接入应答消息还包括第二连接信息，第二连接信息包括第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
以通信装置800为上述方法实施例中的第二设备为例，则：收发器801，用于接收来自第一设备的广播消息。其中，广播消息包括第一指示信息，该第一指示信息用于指示第一设备期望的角色。第一设备期望的角色为G节点或T节点。
一种可能的实现方式中，收发器801，还用在处理器802根据广播消息确定请求接入第一设备的情况下，向第一设备发送接入请求消息；收发器801，还用于接收来第一设备的接入应答消息。其中，接入请求消息用于第二设备请求接入第一设备。该接入应答消息用于指示第二设备接入成功或接入失败。
一种可能的实现方式中，接入请求消息包括第二指示信息，第二指示信息用于指示第二设备期望的角色。其中，第二设备期望的角色为G节点或T节点。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接 入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。
一种可能的实现方式中，第一指示信息还用于指示第一设备期望的角色是否可协商。
一种可能的实现方式中，接入请求消息包括第三指示信息，第三指示信息用于指示第二设备期望的角色且第二设备期望的角色是否可协商。其中，第二设备期望的角色为G节点或T节点。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色不相同的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入失败。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色不可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色不可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功。
一种可能的实现方式中，在第二设备期望的角色与第一设备期望的角色相同，并且第一设备期望的角色可协商以及第二设备期望的角色可协商的情况下，接入应答消息用于指示第二设备以第二设备期望的角色接入成功，或者接入应答消息用于指示第二设备以第二设备期望的角色之外的角色接入成功。
一种可能的实现方式中，处理器802，还用于在收发器801在第二时间资源内未接收到来自第一设备的接入应答消息的情况下，确定第二设备与第一设备之间连接失败。
一种可能的实现方式中，在第二设备期望的角色为G节点的情况下，接入请求消息还包括第一连接信息，第一连接信息包括第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
一种可能的实现方式中，在接入应答消息用于指示第二设备以T节点的角色接入成功的情况下，接入应答消息还包括第二连接信息，第二连接信息包括第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该通信装置800以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
当通信装置800为上述方法实施例中的第一设备或第二设备时，在一个简单的实施例中，本领域的技术人员可以想到该通信装置800可以采用图4所示的通信装置400的形式。
比如，图4所示的通信装置400中的处理器401或处理器407可以通过调用存储器403中存储的计算机执行指令，使得通信装置400执行上述方法实施例中的发送与接收信息的方法。具体的，图8中的处理器802的功能/实现过程可以通过图4所示的通信装置400中的处理器401或407调用存储器403中存储的计算机执行指令来实现。图8中的收发器801的功能/实现过程可以通过经由图4中的通信接口404连接的通信模块来实现。
由于本实施例提供的通信装置800可执行上述发送与接收信息的方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
需要说明的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中， 处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上系统)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
可选的，本申请实施例还提供了一种芯片系统，包括：至少一个处理器和接口，该至少一个处理器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。在一种可能的实现方式中，该通信装置还包括存储器。可选的，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (61)

  1. 一种发送信息的方法，其特征在于，所述方法包括：
    第一设备生成广播消息，所述广播消息包括第一指示信息，所述第一指示信息用于指示所述第一设备期望的角色，其中，所述第一设备期望的角色为主控节点或终端节点；
    所述第一设备向第二设备发送所述广播消息。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一设备在第一时间资源内未接收到来自所述第二设备的接入请求消息的情况下，所述第一设备确定所述第一设备与所述第二设备之间连接失败，所述接入请求消息用于所述第二设备请求接入所述第一设备。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收来自所述第二设备的接入请求消息，所述接入请求消息用于所述第二设备请求接入所述第一设备；
    所述第一设备向所述第二设备发送接入应答消息，所述接入应答消息用于指示所述第二设备接入成功或者接入失败。
  4. 根据权利要求2或3所述的方法，其特征在于，所述接入请求消息包括第二指示信息，所述第二指示信息用于指示所述第二设备期望的角色，其中，所述第二设备期望的角色为所述主控节点或所述终端节点。
  5. 根据权利要求4所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色不相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  6. 根据权利要求4所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  7. 根据权利要求4所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入失败。
  8. 根据权利要求1-3中任一项所述的方法，其特征在于，所述第一指示信息还用于指示所述第一设备期望的角色是否可协商。
  9. 根据权利要求8所述的方法，其特征在于，所述接入请求消息包括第三指示信息，所述第三指示信息用于指示所述第二设备期望的角色且所述第二设备期望的角色是否可协商，其中，所述第二设备期望的角色为所述主控节点或所述终端节点。
  10. 根据权利要求9所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色不相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  11. 根据权利要求9所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述第二设备期望的角色不可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入失败；
    或者，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述第二设备期望的角色可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色之外的角色接入成功。
  12. 根据权利要求9所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述第二设备期望的角色不可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功；
    或者，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述第二设备期望的角色可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功，或者所述接入应答消息用于指示所述第二设备以所 述第二设备期望的角色之外的角色接入成功。
  13. 根据权利要求2-12中任一项所述的方法，其特征在于，在所述第二设备期望的角色为所述主控节点的情况下，
    所述接入请求消息还包括第一连接信息，所述第一连接信息包括所述第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、循环冗余校验CRC码初始值、连接态周期、或者连接态超时时间。
  14. 根据权利要求3-13中任一项所述的方法，其特征在于，在所述接入应答消息用于指示所述第二设备以所述终端节点的角色接入成功的情况下，
    所述接入应答消息还包括第二连接信息，所述第二连接信息包括所述第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
  15. 一种接收信息的方法，其特征在于，所述方法包括：
    第二设备接收来自第一设备的广播消息，所述广播消息包括第一指示信息，所述第一指示信息用于指示所述第一设备期望的角色，其中，所述第一设备期望的角色为主控节点或终端节点。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    在所述第二设备根据所述广播消息确定请求接入所述第一设备的情况下，所述第二设备向所述第一设备发送接入请求消息，所述接入请求消息用于所述第二设备请求接入所述第一设备；
    在所述第二设备在第二时间资源内未接收到来自所述第一设备的接入应答消息的情况下，所述第二设备确定所述第二设备与所述第一设备之间连接失败，所述接入应答消息用于指示所述第二设备接入成功或者接入失败。
  17. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    在所述第二设备根据所述广播消息确定请求接入所述第一设备的情况下，所述第二设备向所述第一设备发送接入请求消息，所述接入请求消息用于所述第二设备请求接入所述第一设备；
    所述第二设备接收来自所述第一设备的接入应答消息，所述接入应答消息用于指示所述第二设备接入成功或者接入失败。
  18. 根据权利要求16或17所述的方法，其特征在于，所述接入请求消息包括第二指示信息，所述第二指示信息用于指示所述第二设备期望的角色，其中，所述第二设备期望的角色为所述主控节点或所述终端节点。
  19. 根据权利要求18所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色不相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  20. 根据权利要求18所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  21. 根据权利要求18所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入失败。
  22. 根据权利要求15-17中任一项所述的方法，其特征在于，所述第一指示信息还用于指示所述第一设备期望的角色是否可协商。
  23. 根据权利要求22所述的方法，其特征在于，所述接入请求消息包括第三指示信息，所述第三指示信息用于指示所述第二设备期望的角色且所述第二设备期望的角色是否可协商，其中，所述第二设备期望的角色为所述主控节点或所述终端节点。
  24. 根据权利要求23所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色不相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  25. 根据权利要求23所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述第二设备期望的角色不可协商 的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入失败；
    或者，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述第二设备期望的角色可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望角色之外的角色接入成功。
  26. 根据权利要求23所述的方法，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述第二设备期望的角色不可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功；
    或者，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述第二设备期望的角色可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功，或者所述接入应答消息用于指示所述第二设备以所述第二设备期望角色之外的角色接入成功。
  27. 根据权利要求16-26中任一项所述的方法，其特征在于，在所述第二设备期望的角色为所述主控节点的情况下，
    所述接入请求消息还包括第一连接信息，所述第一连接信息包括所述第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、循环冗余校验CRC码初始值、连接态周期、或者连接态超时时间。
  28. 根据权利要求16-27中任一项所述的方法，其特征在于，在所述接入应答消息用于指示所述第二设备以所述终端节点的角色接入成功的情况下，
    所述接入应答消息还包括第二连接信息，所述第二连接信息包括所述第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
  29. 一种通信装置，其特征在于，包括：收发器和处理器；
    所述处理器，用于生成广播消息，所述广播消息包括第一指示信息，所述第一指示信息用于指示所述通信装置期望的角色，其中，所述通信装置期望的角色为主控节点或终端节点；
    所述收发器，用于向第二设备发送所述广播消息。
  30. 根据权利要求29所述的通信装置，其特征在于，所述处理器，还用于在第一时间资源内未接收到来自所述第二设备的接入请求消息的情况下，确定所述通信装置与所述第二设备之间连接失败，所述接入请求消息用于所述第二设备请求接入所述通信装置。
  31. 根据权利要求29所述的通信装置，其特征在于，所述收发器，还用于接收来自所述第二设备的接入请求消息，所述接入请求消息用于所述第二设备请求接入所述通信装置；所述收发器，还用于向所述第二设备发送接入应答消息，所述接入应答消息用于指示所述第二设备接入成功或者接入失败。
  32. 根据权利要求30或31所述的通信装置，其特征在于，所述接入请求消息包括第二指示信息，所述第二指示信息用于指示所述第二设备期望的角色，其中，所述第二设备期望的角色为所述主控节点或所述终端节点。
  33. 根据权利要求32所述的通信装置，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色不相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  34. 根据权利要求33所述的通信装置，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  35. 根据权利要求33所述的通信装置，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入失败。
  36. 根据权利要求29-31中任一项所述的通信装置，其特征在于，所述第一指示信息还用于指示所述第一设备期望的角色是否可协商。
  37. 根据权利要求36所述的通信装置，其特征在于，所述接入请求消息包括第三指示信息， 所述第三指示信息用于指示所述第二设备期望的角色且所述第二设备期望的角色是否可协商，其中，所述第二设备期望的角色为所述主控节点或所述终端节点。
  38. 根据权利要求37所述的通信装置，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色不相同的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功。
  39. 根据权利要求37所述的通信装置，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述第二设备期望的角色不可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入失败；
    或者，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述第二设备期望的角色可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色之外的角色接入成功。
  40. 根据权利要求37所述的通信装置，其特征在于，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述第二设备期望的角色不可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功；
    或者，在所述第二设备期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述第二设备期望的角色可协商的情况下，所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色接入成功，或者所述接入应答消息用于指示所述第二设备以所述第二设备期望的角色之外的角色接入成功。
  41. 根据权利要求30-40中任一项所述的通信装置，其特征在于，在所述第二设备期望的角色为所述主控节点的情况下，
    所述接入请求消息还包括第一连接信息，所述第一连接信息包括所述第二设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、循环冗余校验CRC码初始值、连接态周期、或者连接态超时时间。
  42. 根据权利要求31-41中任一项所述的通信装置，其特征在于，在所述接入应答消息用于指示所述第二设备以所述终端节点的角色接入成功的情况下，
    所述接入应答消息还包括第二连接信息，所述第二连接信息包括所述第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
  43. 一种通信装置，其特征在于，包括：收发器；
    所述收发器，用于接收来自第一设备的广播消息，所述广播消息包括第一指示信息，所述第一指示信息用于指示所述第一设备期望的角色，其中，所述第一设备期望的角色为主控节点或终端节点。
  44. 根据权利要求43所述的通信装置，其特征在于，所述通信装置还包括：处理器；
    所述收发器，还用于在所述处理器根据所述广播消息确定请求接入所述第一设备的情况下，向所述第一设备发送接入请求消息，所述接入请求消息用于所述通信装置请求接入所述第一设备；
    所述处理器，还用于在所述收发器在第二时间资源内未接收到来自所述第一设备的接入应答消息的情况下，确定所述通信装置与所述第一设备之间连接失败，所述接入应答消息用于指示所述通信装置接入成功或者接入失败。
  45. 根据权利要求43所述的通信装置，其特征在于，所述通信装置还包括：处理器；
    所述收发器，还用于在所述处理器根据所述广播消息确定请求接入所述第一设备的情况下，向所述第一设备发送接入请求消息，所述接入请求消息用于所述通信装置请求接入所述第一设备；
    所述收发器，还用于接收来自所述第一设备的接入应答消息，所述接入应答消息用于指示所述通信装置接入成功或者接入失败。
  46. 根据权利要求44或45所述的通信装置，其特征在于，所述接入请求消息包括第二指示信息，所述第二指示信息用于指示所述通信装置期望的角色，其中，所述通信装置期望的角色为所述主控节点或所述终端节点。
  47. 根据权利要求46所述的通信装置，其特征在于，在所述通信装置期望的角色与所述第一 设备期望的角色不相同的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望的角色接入成功。
  48. 根据权利要求46所述的通信装置，其特征在于，在所述通信装置期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望的角色接入成功。
  49. 根据权利要求46所述的通信装置，其特征在于，在所述通信装置期望的角色与所述第一设备期望的角色相同的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望的角色接入失败。
  50. 根据权利要求43-45中任一项所述的通信装置，其特征在于，所述第一指示信息还用于指示所述第一设备期望的角色是否可协商。
  51. 根据权利要求50所述的通信装置，其特征在于，所述接入请求消息包括第三指示信息，所述第三指示信息用于指示所述通信装置期望的角色且所述通信装置期望的角色是否可协商，其中，所述通信装置期望的角色为所述主控节点或所述终端节点。
  52. 根据权利要求51所述的通信装置，其特征在于，在所述通信装置期望的角色与所述第一设备期望的角色不相同的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望的角色接入成功。
  53. 根据权利要求51所述的通信装置，其特征在于，在所述通信装置期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述通信装置期望的角色不可协商的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望的角色接入失败；
    或者，在所述通信装置期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色不可协商以及所述通信装置期望的角色可协商的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望角色之外的角色接入成功。
  54. 根据权利要求51所述的通信装置，其特征在于，在所述通信装置期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述通信装置期望的角色不可协商的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望的角色接入成功；
    或者，在所述通信装置期望的角色与所述第一设备期望的角色相同，并且所述第一设备期望的角色可协商以及所述通信装置期望的角色可协商的情况下，所述接入应答消息用于指示所述通信装置以所述通信装置期望的角色接入成功，或者所述接入应答消息用于指示所述通信装置以所述通信装置期望角色之外的角色接入成功。
  55. 根据权利要求44-54中任一项所述的通信装置，其特征在于，在所述通信装置期望的角色为所述主控节点的情况下，
    所述接入请求消息还包括第一连接信息，所述第一连接信息包括所述通信装置提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、循环冗余校验CRC码初始值、连接态周期、或者连接态超时时间。
  56. 根据权利要求44-55中任一项所述的通信装置，其特征在于，在所述接入应答消息用于指示所述通信装置以所述终端节点的角色接入成功的情况下，
    所述接入应答消息还包括第二连接信息，所述第二连接信息包括所述第一设备提供的以下一项或多项：本地时钟、时间偏移、接入地址、跳频地图、CRC码初始值、连接态周期、或者连接态超时时间。
  57. 一种通信装置，其特征在于，包括：存储器以及与所述存储器耦合的处理器，所述存储器用于存储程序，所述处理器用于执行所述存储器存储的所述程序；当所述通信装置运行时，所述处理器运行所述程序，使得所述通信装置执行如权利要求1-14中任一项所述的发送信息的方法，或者使得所述通信装置执行如权利要求15-28中任一项所述的接收信息的方法。
  58. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质包括计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机执行如权利要求1-14中任一项所述的发送信息的方法，或者使得所述计算机执行如权利要求15-28中任一项所述的接收信息的方法。
  59. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行权利要 求1-14中任一项所述的发送信息的方法，或者使得所述计算机执行如权利要求15-28中任一项所述的接收信息的方法。
  60. 一种发送与接收信息的方法，其特征在于，所述方法包括：
    第一设备生成广播消息，所述广播消息包括第一指示信息，所述第一指示信息用于指示所述第一设备期望的角色，其中，所述第一设备期望的角色为主控节点或终端节点；
    所述第一设备向第二设备发送所述广播消息；
    所述第二设备接收来自所述第一设备的广播消息。
  61. 一种通信系统，其特征在于，所述通信系统包括：第一设备和第二设备，其中，所述第一设备用于执行如权利要求1-14中任一项所述的发送信息的方法，所述第二设备用于执行权利要求15-28中任一项所述的接收信息的方法。
PCT/CN2023/102513 2022-08-24 2023-06-26 发送与接收信息的方法、通信装置及系统 WO2024041161A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211020745.5 2022-08-24
CN202211020745.5A CN117641257A (zh) 2022-08-24 2022-08-24 发送与接收信息的方法、通信装置及系统

Publications (1)

Publication Number Publication Date
WO2024041161A1 true WO2024041161A1 (zh) 2024-02-29

Family

ID=90012389

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/102513 WO2024041161A1 (zh) 2022-08-24 2023-06-26 发送与接收信息的方法、通信装置及系统

Country Status (2)

Country Link
CN (1) CN117641257A (zh)
WO (1) WO2024041161A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130195079A1 (en) * 2010-02-11 2013-08-01 Fujitsu Limited Contention-based uplink data transmission method, apparatus and system
CN104396338A (zh) * 2012-03-19 2015-03-04 泰科消防及安全有限公司 用于具有低占空比的终端节点的大型wsn的可扩展协议
CN113055978A (zh) * 2021-05-31 2021-06-29 北京理工大学 通信接入方法、装置、设备和可读存储介质
CN114338267A (zh) * 2021-12-21 2022-04-12 北京东土科技股份有限公司 多管理节点的维护方法、装置、设备、总线网络及介质
CN114449602A (zh) * 2022-01-27 2022-05-06 深圳Tcl新技术有限公司 切换方法、存储介质及无线通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130195079A1 (en) * 2010-02-11 2013-08-01 Fujitsu Limited Contention-based uplink data transmission method, apparatus and system
CN104396338A (zh) * 2012-03-19 2015-03-04 泰科消防及安全有限公司 用于具有低占空比的终端节点的大型wsn的可扩展协议
CN113055978A (zh) * 2021-05-31 2021-06-29 北京理工大学 通信接入方法、装置、设备和可读存储介质
CN114338267A (zh) * 2021-12-21 2022-04-12 北京东土科技股份有限公司 多管理节点的维护方法、装置、设备、总线网络及介质
CN114449602A (zh) * 2022-01-27 2022-05-06 深圳Tcl新技术有限公司 切换方法、存储介质及无线通信装置

Also Published As

Publication number Publication date
CN117641257A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
WO2020088688A1 (zh) 资源配置方法及装置
WO2020221093A1 (zh) 搜索空间的监测、配置方法及装置
JP6691875B2 (ja) 端末装置、基地局装置、および、方法
WO2022246803A1 (zh) 接入方法及通信装置
US11405961B2 (en) Wireless communication method and apparatus
EP4192082A1 (en) Communication method, apparatus and system
WO2020143490A1 (zh) 通信方法及装置
AU2018407841A1 (en) Data transmission control method and related product
JP7480417B2 (ja) 補助情報送信方法、受信方法、装置、端末及びネットワーク側機器
WO2024067687A1 (zh) 信息传输方法、第一通信节点、第二通信节点及存储介质
CN111669835A (zh) 通信的方法、装置及系统
WO2021012997A1 (zh) 一种信息传输方法、装置及通信设备
WO2020221313A1 (zh) 通信方法及装置
WO2024041161A1 (zh) 发送与接收信息的方法、通信装置及系统
WO2023273743A1 (zh) 一种侧行通信方法及装置
WO2019095783A1 (zh) 一种同步块与寻呼调度信令关联方法、指示方法及装置
WO2022187996A1 (zh) 一种资源调控方法
WO2017114218A1 (zh) 资源划分方法及装置
WO2022027594A1 (zh) 一种通信方法及通信装置
WO2021088062A1 (zh) 一种通信方法及装置
WO2021134447A1 (zh) 一种通信方法及装置
WO2021056595A1 (zh) 一种通信方法及装置
CN113939019A (zh) 通信方法及通信设备
WO2023272444A1 (zh) 一种通信方法及其通信装置
WO2023232007A1 (zh) 信号传输方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23856253

Country of ref document: EP

Kind code of ref document: A1