IP Library › Granted Patent US 12,244,525
Granted Patent B2
US 12,244,525 · App. 18/527,690 · Granted Mar 4, 2025

Information transmission method and network device

Inventors: Xiao Han (Shenzhen, CN); Changfeng Ding (Chengdu, CN); Xuming Fang (Chengdu, CN); Yan Long (Chengdu, CN); Mengyao Ma (Shenzhen, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04L5/0035H04B7/0617H04W48/12H04W72/0446H04W72/20H04W72/23H04W76/11
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,244,525
App. No.
18/527,690
Granted
Mar 4, 2025
Kind
B2
Abstract

An information transmission method and a network device, the network device including a transceiver, a processor, and a non-transitory storage medium storing a computer program for execution by the processor. The computer program includes instructions to receive a first frame through the receiver, where an extended schedule element of the first frame has a field indicating communication between network devices is supported, and where the extended schedule element further has a source association identifier and a destination association identifier, and control the transceiver to transmit information to a first network device when both the first network device and the network device support communication between network devices, where a value of the source association identifier and a value of the destination association identifier are each 0.

Claims (31)

1. A first network device, comprising:

a transceiver;

a processor; and

a non-transitory storage medium storing a computer program for execution by the processor, the computer program including instructions to:

cause the transceiver to send a first frame, wherein an extended schedule element of the first frame comprises a field indicating communication between network devices is supported, wherein the extended schedule element further comprises a source association identifier and a destination association identifier; and

control the transceiver to transmit information to a second network device when both the first network device and the second network device support communication between network devices, wherein a value of the source association identifier and a value of the destination association identifier are each 0.

2. The first network device according to claim 1 , wherein the field indicating the communication between the network devices is supported comprises at least one location in the first frame that is an allocation type field in an allocation control field in an allocation field in the extended schedule element.

3. The first network device according to claim 1 , wherein the source association identifier indicates a source network device identifier, and wherein the destination association identifier indicates a target network device identifier.

4. The first network device according to claim 1 , wherein the extended schedule element comprises a 1-byte element identifier field, a 1-byte length field, and n allocation fields, each allocation field of the n allocation fields has 15 bytes, and wherein each allocation field of the n allocation fields includes a 2-byte allocation control field, a 2-byte beamforming control field, a 1-byte source association identifier field, a 1-byte destination association identifier field, a 4-byte allocation start field, a 2-byte allocation block duration field, a 1-byte numbers of blocks subfield, and a 2-byte allocation block period field.

5. The first network device according to claim 4 , wherein the 2-byte allocation control field comprises a 4-bit allocation identifier field, a 3-bit allocation type field, a 1-bit pseudo-static field, a 1-bit truncatable field, a 1-bit extendable field, a 1-bit personal basic service set active field, a 1-bit low power single carrier used field, a B12 bit and a 3-bit reserved bit.

6. The first network device according to claim 5 , wherein the field indicating the communication between the network devices is supported comprises the 3-bit allocation type field and the B12 bit.

7. The first network device according to claim 1 , wherein the first frame is sent to the second network device.

8. A method, comprising:

sending, by a first network device, a first frame, wherein an extended schedule element of the first frame comprises a field indicating communication between network devices is supported, and wherein the extended schedule element further comprises a source association identifier and a destination association identifier; and

transmitting, by the first network device, information to a second network device when both the first network device and the second network device support communication between network devices, wherein a value of the source association identifier and a value of the destination association identifier are each 0.

9. The method according to claim 8 , wherein the field indicating the communication between the network devices is supported comprises at least one location in the first frame that is an allocation type field in an allocation control field in an allocation field in the extended schedule element.

10. The method according to claim 8 , wherein the source association identifier indicates a source network device identifier, and wherein the destination association identifier indicates a target network device identifier.

11. The method according to claim 8 , wherein the extended schedule element comprises a 1-byte element identifier field, a 1-byte length field, and n allocation fields, wherein each allocation field of the n allocation fields has 15 bytes, wherein each allocation field includes a 2-byte allocation control field, a 2-byte beamforming control field, a 1-byte source association identifier field, a 1-byte destination association identifier field, a 4-byte allocation start field, a 2-byte allocation block duration field, a 1-byte numbers of blocks subfield, and a 2-byte allocation block period field.

12. The method according to claim 11 , wherein the 2-byte allocation control field comprises a 4-bit allocation identifier field, a 3-bit allocation type field, a 1-bit pseudo-static field, a 1-bit truncatable field, a 1-bit extendable field, a 1-bit personal basic service set active field, a 1-bit low power single carrier used field, a B12 bit and a 3-bit reserved bit.

13. The method according to claim 12 , wherein the field indicating the communication between the network devices is supported comprises the 3-bit allocation type field and the B12 bit.

14. The method according to claim 8 , wherein the first frame is sent to the second network device.

15. A device, comprising:

a processor;

wherein the processor is coupled with a non-transitory storage medium storing a computer program for execution by the processor, the computer program including instructions causing the device to:

output a first frame, wherein an extended schedule element of the first frame comprises a field indicating communication between network devices is supported, wherein the extended schedule element further comprises a source association identifier and a destination association identifier; and

exchange information with a second network device when both a first network device and the second network device support communication between network devices, wherein a value of the source association identifier and a value of the destination association identifier are each 0, and wherein the first network device comprises the device.

16. The device according to claim 15 , wherein the field indicating the communication between the network devices is supported comprises at least one location in the first frame that is an allocation type field in an allocation control field in an allocation field in the extended schedule element.

17. The device according to claim 15 , wherein the source association identifier indicates a source network device identifier, and wherein the destination association identifier indicates a target network device identifier.

18. The device according to claim 15 , wherein the extended schedule element comprises a 1-byte element identifier field, a 1-byte length field, and n allocation fields, each allocation field of the n allocation fields has 15 bytes, and wherein each allocation field of the n allocation fields includes a 2-byte allocation control field, a 2-byte beamforming control field, a 1-byte source association identifier field, a 1-byte destination association identifier field, a 4-byte allocation start field, a 2-byte allocation block duration field, a 1-byte numbers of blocks subfield, and a 2-byte allocation block period field.

19. The device according to claim 18 , wherein the 2-byte allocation control field comprises a 4-bit allocation identifier field, a 3-bit allocation type field, a 1-bit pseudo-static field, a 1-bit truncatable field, a 1-bit extendable field, a 1-bit personal basic service set active field, a 1-bit low power single carrier used field, a B12 bit and a 3-bit reserved bit.

20. The device according to claim 19 , wherein the field indicating the communication between the network devices is supported comprises the 3-bit allocation type field and the B12 bit.

Priority Claims (1)
CN 201710691261.6 · Aug 14, 2017 · national
Continuity (4)
Continuation 17873472 · Jul 26, 2022
Continuation 16790044 · Feb 13, 2020
Continuation PCTCN2018096321 · Jul 19, 2018
Related Publication 20240106586A1 · Mar 28, 2024
References Cited (33)
US 8072947B2 · Cho et al. · 2011 [cited by applicant]
US 10623981B2 · Lin et al. · 2020 [cited by applicant]
US 11233732B2 · Che et al. · 2022 [cited by applicant]
US 11457333B2 · Adachi · 2022 [cited by applicant]
US 20110110340A1 · Lakkis · 2011 [cited by applicant]
US 20130176993A1 · Trainin et al. · 2013 [cited by applicant]
US 20150098388A1 · Fang · 2015 [cited by examiner]
US 20150282063A1 · Patil et al. · 2015 [cited by applicant]
US 20160135115A1 · Patil et al. · 2016 [cited by applicant]
US 20160249349A1 · Trainin et al. · 2016 [cited by applicant]
US 20160323925A1 · Alanen · 2016 [cited by examiner]
US 20170094693A1 · Law et al. · 2017 [cited by applicant]
US 20170201992A1 · Cordeiro et al. · 2017 [cited by applicant]
CN 1829177A · 2006 [cited by applicant]
CN 1855867A · 2006 [cited by applicant]
CN 101331439A · 2008 [cited by applicant]
CN 102256356A · 2011 [cited by applicant]
CN 104041169A · 2014 [cited by applicant]
CN 106102127A · 2016 [cited by applicant]
CN 106134257A · 2016 [cited by applicant]
CN 106717053A · 2017 [cited by applicant]
CN 106936713A · 2017 [cited by applicant]
CN 104770033B · 2019 [cited by applicant]
EP 2932613B1 · 2016 [cited by applicant]
WO 2014028730A1 · 2014 [cited by applicant]
WO 2015038175A1 · 2015 [cited by applicant]
WO 2017008044A1 · 2017 [cited by applicant]
WO 2017043911A1 · 2017 [cited by applicant]
WO 2017043912A1 · 2017 [cited by applicant]
“Draft Standard for Information Technology Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Phy… [cited by applicant]
IEEE Standards Association, “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” IEEE Computer Society, IEEE Std 802.11-2016 (Revision of IEEE Std 802.11-2012), Dec. 7, 2016, 3534… [cited by applicant]
IEEE Standards Association, “Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 3: Enhancements for Very High Throughput in the 60 GHz Band,” IEEE Computer Society, IEEE… [cited by applicant]
Sun, R. et al., “IEEE 802.11 TGay Use Cases,” IEEE 802.11-2015/0625r4, Jul. 2017, 30 pages. [cited by applicant]