# US 10,313,267 B2 · Method and apparatus for implementing traffic flags for large service groups > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,313,267 B2 - Document ID: US10313267B2 - Status: Granted - Kind: B2 - Application number: 15/903,778 - Filed: 2018-02-23 - Published: 2018-07-19 - Granted: 2019-06-04 - Earliest claimed: 2012-03-21 - Assignees: Entropic Communications, Inc. - Applicants: Entropic Communications, LLC - Inventors: Changwen Liu; David Barr; Michail Tsatsanis - Web page: https://patentgrep.com/patent/US10313267B2 ## CPC - H04L 47/828: {Allocation of resources per group of connections, e.g. per group of users} - H04L 12/2838: {Distribution of signals within a home automation network, e.g. involving splitting/multiplexing signals to/from different paths (adaptations of television systems for transmission by electric cable for domestic distribution H04N7/106; hybrid transport H04L12/6418; home network arrangements specially adapted for distribution of digital video signals H04N7/24)} - H04L 12/2861: {Point-to-multipoint connection from the data network to the subscribers} - H04L 47/31: by tagging of packets, e.g. using discard eligibility [DE] bits - H04L 47/41: by acting on aggregated flows or links - H04L 5/0091: {Signalling for the administration of the divided path, e.g. signalling of configuration information} - H04L 2012/284: {characterised by the type of medium used} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract The use of traffic flag symbols allows a large number of CPEs to transmit traffic notifications to a network controller. In some such embodiments, hundreds of CPEs simultaneously transmit traffic flags on different subcarriers of a channel. For example, in a MoCA2 based access network, up to 480 CPEs can transmit flags in only 5 μs in the 100 MHz-wide channel. ## Claims ### Claim 1 A network node, comprising: a receiver configured to receive an indication of an assigned subcarrier from a network controller; and a transmitter configured to transmit a traffic symbol on the assigned subcarrier, wherein the traffic symbol comprises a traffic flag that indicates whether the network node has upstream traffic to send to the network controller, the traffic flag being transmitted simultaneously with another traffic flag on another assigned subcarrier, and wherein the network controller schedules a reservation request based on the traffic flag, and wherein the traffic flag indicates a number of symbols requested to be scheduled. ### Claim 2 (depends on 1) The network node of claim 1, wherein the receiver is operable to receive a scheduled time for a reservation request in response to the traffic flag. ### Claim 3 (depends on 1) The network node of claim 1, wherein the receiver is operable to receive a scheduled time for uplink data in response to the traffic flag. ### Claim 4 (depends on 1) The network node of claim 1, wherein the network controller is operable to schedule upstream traffic based on the traffic flag. ### Claim 5 (depends on 1) The network node of claim 1, wherein the traffic flag comprises two or more bits. ### Claim 6 (depends on 1) The network node of claim 1, wherein the traffic flag indicates a buffer fullness. ### Claim 7 (depends on 1) The network node of claim 1, wherein the traffic flag comprises an acknowledgement of a receipt of a data packet. ### Claim 8 (depends on 1) The network node of claim 1, wherein the network controller is operable to assign multiple subcarriers to the network node. ### Claim 9 A network node, comprising: a receiver configured to receive an indication of an assigned subcarrier from a network controller; and a transmitter configured to transmit a traffic symbol on the assigned subcarrier, wherein the traffic symbol comprises a traffic flag that indicates whether the network node has upstream traffic to send to the network controller, the traffic flag being transmitted simultaneously with another traffic flag on another assigned subcarrier, and wherein the traffic flag indicates a buffer fullness, wherein the traffic flag indicates a number of symbols requested to be scheduled. ### Claim 10 (depends on 9) The network node of claim 9, wherein the receiver is operable to receive a scheduled time for a reservation request in response to the traffic flag. ### Claim 11 (depends on 9) The network node of claim 9, wherein the receiver is operable to receive a scheduled time for uplink data in response to the traffic flag. ### Claim 12 (depends on 9) The network node of claim 9, wherein the network controller is operable to schedule upstream traffic based on the traffic flag. ### Claim 13 (depends on 9) The network node of claim 9, wherein the traffic flag comprises two or more bits. ### Claim 14 (depends on 9) The network node of claim 9, wherein the network controller is operable to schedule a reservation request based on the traffic flag. ### Claim 15 (depends on 9) The network node of claim 9, wherein the traffic flag comprises an acknowledgement of a receipt of a data packet. ### Claim 16 (depends on 9) The network node of claim 9, wherein the network controller is operable to assign multiple subcarriers to the network node. ### Claim 17 A network node, comprising: a receiver configured to receive an indication of an assigned subcarrier from a network controller; and a transmitter configured to transmit a traffic symbol on the assigned subcarrier, wherein the traffic symbol comprises a traffic flag that indicates whether the network node has upstream traffic to send to the network controller, the traffic flag being transmitted simultaneously with another traffic flag on another assigned subcarrier, and wherein the traffic flag indicates a number of symbols requested to be scheduled. ### Claim 18 (depends on 17) The network node of claim 17, wherein the receiver is operable to receive a scheduled time for a reservation request in response to the traffic flag. ### Claim 19 (depends on 17) The network node of claim 17, wherein the receiver is operable to receive a scheduled time for uplink data in response to the traffic flag. ### Claim 20 (depends on 17) The network node of claim 17, wherein the network controller is operable to schedule upstream traffic based on the traffic flag. ### Claim 21 (depends on 17) The network node of claim 17, wherein the traffic flag comprises two or more bits. ### Claim 22 (depends on 17) The network node of claim 17, wherein the traffic flag indicates a buffer fullness. ### Claim 23 (depends on 17) The network node of claim 17, wherein the network controller is operable to schedule a reservation request based on the traffic flag. ### Claim 24 (depends on 17) The network node of claim 17, wherein the traffic flag comprises an acknowledgement of a receipt of a data packet. ### Claim 25 (depends on 17) The network node of claim 17, wherein the network controller is operable to assign multiple subcarriers to the network node.