WO2016163989A1

WO2016163989A1 - Method and apparatus for data relay and instant admission

Info

Publication number: WO2016163989A1
Application number: PCT/US2015/024606
Authority: WO
Inventors: Changwen Liu
Original assignee: Entropic Communications, Inc.
Priority date: 2015-04-07
Filing date: 2015-04-07
Publication date: 2016-10-13

Abstract

Systems and methods for providing rapid admission to a network, for new nodes and nodes coming out of a reduced power mode. Nodes can begin accessing the data plane of the network prior to establishing active PHY profiles for all links in the network. The Network Coordinator can relay data between a newly admitted node and an existing node where there is no active PHY profile for the link between the newly admitted node and the existing node.

Description

METHOD AND APPARATUS FOR DATA RELAY AND INSTANT ADMISSION

Technical Field

[0001] The disclosed method and apparatus relates to networking and more particularly to means for quickly establishing communications between nodes of a MoCA network.

BACKGROUND

[0002] It is common today for people to share information and entertainment content

throughout their homes over networks that connect various devices within the home. For example, many people share entertainment content through a local area network (LAN) fashioned as a "mesh network". A mesh network provides a connection between nodes of the network, whereby each node can communicate with each other node of the network. One such network is the well-known MoCA network which operates in accordance with an industry standard known as MoCA 2.0 published by the Multimedia over Coax Alliance (MoCA^®).

[0003] FIG. 1 is a simplified illustration of a home 100 that has a MoCA network 106. In the example shown in FIG. 1, the MoCA network 106 has four nodes 1 10, 1 12, 1 14, 1 16. The nodes of the network 106 are all coupled to a coaxial cable that serves as a medium 128. Typically, the medium 128 within a home 100 is coupled to all four of the nodes 1 10, 1 12, 1 14, 1 16 of the network.

[0004] When a new node (NN) is to be added to the network, an Admission Process is

implemented. The Admission Process is well defined and requires several steps to be completed before the NN can access the data plane (i.e., send or receive content to or from another node in the network).

[0005] FIG. 2 is a simplified illustration of a MoCA network 106 in which a NN 201 is implementing an Admission Process to form an expanded network 203. Once formed, the expanded network 203 will include each of the nodes 110, 112, 1 14, 1 16 of the network 106 plus the NN 201. FIG. 3 is a flow diagram of the Admission Process. During the Admission Process, the network will reside in one of five Link Control States. Initially, the NC 1 10 receives an Admission Request 301 from the NN 201. In response, the NC 1 10 moves the network 106 into a "Begin Node Admission" Link Control State. In the Begin Node Admission Link Control State, the NC 110 sends an Admission Response message 303. The NN 201 and each additional Existing Node (EN) 305 in the network sends a Link Acknowledgement message 307. The NN can send NN Probe Transmission Requests 309 for slots (i.e., time allocated by the NC 1 10) in which probes 31 1 are to be transmitted between the NC 110 and the NN 201. Probes 311 are then sent between the NN 201 and the NC 1 10 in response to the NN's requests 309. The NC 1 10 can send NC Probe Transmission Requests 313 to the NN 201. The NC 1 10 responds by sending probes 315 to the NN 201 and scheduling probes 315 to be sent by the NN 201 to the NC 1 10.

[0006] After fulfilling all of the NC's probe requests, Error Vector Magnitude (EVM) Probes 317 are sent from the NC 1 10 to the NN 201. In response, the NN 201 sends an EVM Probe Report 319 to the NC 1 10. Once the NC 1 10 and the NN 201 have exchanged the probes 311, 315, 319, the NC 1 10 generates a Greatest Common Denominator (GCD) EVM probe distribution report 321. The NC 1 10 sends the new GCD EVM distribution report 321 to the NN 201. Upon successfully receiving the report 321, the NN 201 responds to the NC 201 by sending a Link Acknowledgement message 323. If the NC 110 has up to date information regarding the links between the NC and each of the ENs 305 in the network, the NC 1 10 also sends the same new GCD EVM probe distribution report 325 to each of the ENs 305 of the network. Each EN 305 will respond by sending a Link Acknowledgement message 327.

[0007] At this point in the Admission Process, Media Access Plans (MAPs) 329 can be sent by the NC 1 10 using the new GCD MAP PHY profile. However, to complete the Admission Process and return the network to the Steady State Link Control State, the NN 201 still needs to exchange probes with each of the ENs 305 to characterize the links between the NN and each EN 305 in the network.

[0008] FIG. 4 is a flow diagram of the messages that are sent by the NN 201, NC 110 and the ENs 305 to characterize the links between the NN 201 and each of the ENs 305 to complete the Admission Process. Until this process is complete, the NN 201 cannot access the data plane (i.e., send any content over the network). The NC 1 10 moves the network into a "NN TX Probe State" by sending a MAP 401 in which the LINK_STATE is set to NN TX Probe State to the NN 201 and all ENs 305 on the network. Once in the NN TX Probe State, the NN sends an initial power control message 403 to the NC 1 10 and to each EN 305. In response, each EN 305 sends an initial power control response 405 to the NN 201. The NC 110 also sends an initial power control response 407 to the NN 201. The NN 201 sends an initial power control acknowledgement 409, 411 to each EN 305 and to the NC 1 10. Once the power levels are established, the NN 201 sends EVM probes 413 to each of the nodes 110, 305.

[0009] Once the NN 201 has sent EVM probes to each node 110, 305, the NN 201 sends an EVM Probes Report Request to the NC 110. The NC 110 responds to the report request 415 by broadcasting an EVM Probes Report Request 417 to the ENs 305 in the network. The NC 110 sends an EVM Probe Report 419 to the NN 201. In addition, the NC 1 10 receives an EVM Probe Report 421 from each EN 305. In response to the NC 110 receiving an EVM Probe Reports 421, the NC 110 sends a copy of each EVM Probe Report 423 to the NN 201. Once each EN 305 and the NC 1 10 have provided an EVM Probe Report 421, 423 to the NN 201, the network can advance from the NN TX Probe State to the NN RX Probe State.

[0010] In the NN RX Probe State, the NN 201, NC 1 10 and each EN 305 will go through a similar process whereby the characteristics of the link from each EN 305 to the NN 201 is determined by the NN 201 receiving probes one at a time from each EN 305, generating an EVM probe report for each EN 305 and sending the report to the NC 1 10. The NC 1 10 then sends the report to each EN 305. As each EN 305 completes the exchange of probes, it sends a Reservation Request (RR) message to the NC (not shown) including a

NEXT_LINK_STATE field that is set to "New Node GCD Distribution State" to complete the NN RX Probe State. When all of the ENs have sent such an RR message, the network moves to the New Node GCD Distribution State.

[001 1] In the New Node GCD Distribution State, each node, NN 201 or EN 305, generates a GCD Probe Distribution Report and distributes the report to each EN 305 and the NN via NC relay. As each node receives a relayed GCD Probe Distribution Report from another node, the receiving node will send an acknowledgement to the sending node. When a node has received an acknowledgement from the NN and each of the ENs in the network, it sends a RR reporting "Begin PHY Profile State". When the NN and all of the EN's have reported such an RR, the NC 110 will move the network to the Begin PHY Profile State at which time, each of the nodes, ENs 305, NC 110 and NN 201 will activate and begin using the newly computed PHY profiles. The NC 110 can then move the network to the Steady State Link Control State and the Admission Procedure is complete. [0012] The Admission Procedure, including the large number of probe exchanges that must take place and the generation and distribution of the reports generated as a consequence of the probes, take a relatively long time. In addition to an NN 201 being added to the network, this process also takes place whenever a node put in a reduced power state also rejoins the network. Therefore, it can take a relatively long time for a NN 201 that was in a reduced power state to be readmitted to the network and become able once again to access the data plane to communicate with the other ENs 305. However, without each EN 305 having an accurate PHY profile to determine the proper modulation to be used to communicate over the data plane with the NN 201 that is coming back from a reduced power state, it is impossible to communicate with the NN 201.

[0013] Accordingly, there is presently a need for a method and apparatus by which a new node can be admitted to a MoCA network quickly to allow the new node to more rapidly to communicate with other existing nodes in the network.

SUMMARY

[0014] Various embodiments are presented which allow a new node (NN) or a node rejoining the network from a reduced power state to gain rapid admission to the network and access to the data plane of the network to communicate information between the NN and Existing Nodes (ENs) on the network. A new node may be a node that was previously admitted to a network and which, after admission, entered a reduced power state.

[0015] In accordance with one embodiment of the disclosed method and apparatus, a NN sends an Admission Request to a Network Coordinator (NC) and receives an Admission response in return. The NN receives probes from the NC. The NN uses the probes to generate a probe report and send the report to the NC. The NC generates a new GCD (Greatest Common Denominator) Probe Distribution Report out of the received probe report from the NN and sends it to the NN. The NC sends a New GCD Probe Distribution Report to each EN. In one embodiment, the NC then starts sending Media Access Plans (MAPs) over the network using the new GCD PHY profile indicated by the New GCD Probe Distribution Report. The NN sends probes to the NC and receives a Probe report from the NC. The NC will then move the network to a Steady State Link Control State, completing the Admission Process.

[0016] Having used the probe exchange to characterize the link between the NN and the NC in both directions, the NC can move the network into a Link Control State, commonly referred to as "Steady State". The NN can communicate with the NC over the data plane once the network is in the Steady State in both directions. However, even though the NN has completed the Admission Process and the network is in the Steady State, the NN cannot yet communicate directly with other ENs for which there is no PHY profile characterizing the links between the NN and the EN. However, in one embodiment of the disclosed method and apparatus, the NN can send content to the NC that is intended to be communicated from the NN to an intended receiving EN. In one embodiment, a newly admitted EN can make a reservation request to send content to an intended receiving EN for which the newly admitted EN does not yet have a PHY profile. It will be understood throughout the disclosure that "newly" does not indicate that most recently. However, the newly admitted EN may in some cases be the most recently admitted node. The status of a node transitions from NN to EN when the Admission Procedure is complete. The receiving EN may have joined the network either earlier or later than the newly admitted EN. The NC will respond by granting the RR for a communication between the newly admitted node and the NC rather than the intended receiving EN. The newly admitted node will then send the content to the NC. The NC can then send/relay the content to the intended receiving EN. In one embodiment, a confirmation is sent from the intended receiving EN to the NC. The NC will then send a corresponding confirmation to the newly admitted NN indicating safe receipt of the content by the intended receiving EN.

[0017] In one embodiment of the disclosed method and apparatus, the NC will perform a Link Maintenance Operation (LMO) during which probes are sent from the newly admitted EN to each of the other nodes in the network, including each of the ENs for which the newly admitted EN does not yet have a PHY profile, and the probe reports are sent from these receiving nodes to the newly admitted EN. Once the LMO has been performed by an intended receiving EN, the NC can grant the RR by the newly admitted EN to send content to the intended receiving EN directly without NC relay.

[0018] In one embodiment of the disclosed method and apparatus, the NC can evaluate an RR sent by any source EN. In the case in which the RR is a request for resources to send content to any destination EN, the NC can determine from the evaluation that it would be more efficient for the source EN to send the content to the NC and then the NC to send/relay the content to the destination EN. This may be determined to be true even if there is a current PHY profile between the source EN and destination EN. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The disclosed method and apparatus, in accordance with one or more various

embodiments, is described with reference to the following figures. The drawings are provided for purposes of illustration only and merely depict examples of some embodiments of the disclosed method and apparatus. These drawings are provided to facilitate the reader's understanding of the disclosed method and apparatus. They should not be considered to limit the breadth, scope, or applicability of the claimed invention. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale.

[0020] FIG. 1 is a simplified illustration of a home having a MoCA a network.

[0021] FIG. 2 is a simplified illustration of a MoCA network in which a NN is implementing an Admission Process to form an expanded network.

[0022] FIG. 3 is a flow diagram of the Admission Process.

[0023] FIG. 4 is a flow diagram of the messages that are sent by the NN, NC and the ENs to characterize the links between the NN and each of the ENs to complete the Admission Process.

[0024] FIG. 5 a logical block diagram of a node of a network, in accordance with the

presently disclosed method and apparatus.

[0025] FIG. 6 is a simplified flowchart of the process implemented by a node 500 in the role of a New Node (NN) when power is first applied.

[0026] FIG. 7 is a process flow diagram showing the messages that are communicated as part of the Admission Process in accordance with one embodiment of the disclosed method and apparatus.

[0027] FIG. 8 is a process flow diagram showing the process used to send information from a newly admitted EN 801 to an intended destination EN.

[0028] FIG. 9 is a process flow diagram of yet another embodiment, in which it is possible for the NC to determine that a route over a direct link between in Ingress Node and an Egress Node 904 is more inefficient than a route through the NC.

[0029] FIG. 10 is an illustration of an Ingress Node 903, an Egress Node 904 and an NC 907 within a network 1000. [0030] FIG. 1 1 is a simplified block diagram of the hardware used to implement a network node 500 in accordance with one embodiment of the disclosed method and apparatus.

[0031] The figures are not intended to be exhaustive or to limit the claimed invention to the precise form disclosed. It should be understood that the disclosed method and apparatus can be practiced with modification and alteration, and that the invention should be limited only by the claims and the equivalents thereof.

DETAILED DESCRIPTION

[0032] FIG. 5 is a logical block diagram of a node 500 of a network, in accordance with the presently disclosed method and apparatus. Nodes may function in a manner that is appropriate to the role that node is currently playing. For example, a node 500 can assume the role of the Network Coordinator (NC), a New Node (NN) or an Existing Node (EN). The functions of each node are disclosed below in order to understand how the node 500 functions in its role in accordance with the present disclosed method and apparatus.

[0033] The node 500 essentially uses the well-known seven layer Open System

Interconnection model (OSI). Accordingly, the node 500 comprises a physical layer 502 which is responsible for controlling the physical interface to the medium, including transmitting signals over the medium (e.g., coaxial cable). A Data Link Layer (DLL) 504 includes several sub-layers, such as an Ethernet Convergence Layer (ECL) 506, Link Layer Control (LLC) 508, Media Access Control (MAC) 510, the details of which are not necessary for an understanding of the presently disclosed method and apparatus and are well-known to those skilled in the art. The DLL 504 is responsible for controlling the high layer operation of the physical layer and determining the timing and management of messages to be transmitted and received. Accordingly, the DLL 504 works with the physical layer 502 to perform the functions noted in FIGs. 3-7. In one embodiment of the disclosed method and apparatus, the DLL 504 is implemented by the execution of software running on at least one processor.

[0034] FIG. 6 is a simplified flowchart of the process implemented by a node 500 in the role of a New Node (NN) when power is first applied. This process is also followed by a node that was previously admitted, but is rejoining the network after entering a reduced power state. In one embodiment of the disclosed method and apparatus, the network is formed when a NN is connected to the medium (typically a coaxial cable installed in a home or other facility) and the NN is "Powered up" (STEP 601). After initialization/power up, the NN performs a network search of each of its supported bands (i.e., the frequencies that the node is capable of using to communicate with other nodes). The NN will perform the network search procedure to determine whether any other node is already operating on the medium in a supported band. The NN does this by listening for a Beacon message (hereafter, referred to simply as a Beacon for the sake of brevity) (STEP 603). If the NN fails to detect a Beacon, the NN 601 will form a new network and begin transmitting Beacons if its own while waiting for another NN to attempt to join its network (STEP 605).

[0035] In one embodiment, networks formed on the medium can have network privacy enabled. If privacy is enabled for the network, the node needs to have the password. If an NC is already operating on the medium on which the NN is listening, the NC sends a Beacon. The NC continues to send Beacons and carries on with normal operation of the network. When the NN detects the Beacon from the NC (STEP 603), the NN determines from information contained within the Beacon when to send a Discovery Request message. The NN then sends a Discovery Request message to the NC (STEP 607).

[0036] In response to the Discovery Request message, the NC sends a Discovery Response message. Information conveyed in the pre-admission discovery messages is not relevant to the presently disclosed method and apparatus and is known to those skilled in the art. After having exchanged the Discovery Request message and receiving a Discovery Response message (STEP 609), the NN will transmit an Admission Request message (STEP 61 1) during an Admission Control Frame (ACF) Slot scheduled by the NC in response to receiving the Discovery Response message. Upon receipt of the Admission Request message, the NC prepares and transmits an Admission Response message. The Admission Response message includes information regarding all of the ENs within the network.

[0037] After receipt of the Admission Response message, the NN will begin the process of exchanging probes with the NC to build a characterization of the paths between the NN and the NC (STEP 615). The process of exchanging probes to characterize a MoCA network is well known to those skilled in the art.

[0038] After exchanging the probes and associated probe reports, the NN admission is complete STEP (617). The network advances to Steady State. The Node is no longer referred to as a NN, but rather is then referred to as a "newly admitted EN". The status of a node transitions from NN to EN when the Admission Procedure is complete.

[0039] FIG. 7 is a process flow diagram showing the messages that are communicated as part of the Admission Process in accordance with one embodiment of the disclosed method and apparatus. The Admission Process follows the messaging sequence performed in a conventional MoCA 2.0 Admission Process. However, in one embodiment of the disclosed method and apparatus, the Admission Process ends after the NC 701 sends an EVM Probe Report 703.

[0040] In one embodiment, a NN 705 starts the Admission Process by sending an Admission Request message 707 to an NC 701. In one such embodiment, the NN 705 indicates whether the admission process should conform to a rapid admission process or not. If not, then the admission process requires the links between the NN 705 and each of the other ENs of the network to be completely characterized and a PHY profile be activated for each link to the NN 705 and from the NN 705 before the admission process is complete and the NN can be admitted to access the data plane (i.e., communicate data to another node on the network). Alternatively, in one embodiment, if the Admission Request indicates that the NN 705 is to be admitted using the rapid admission process, then the Admission Process is completed upon attaining a PHY profile for the link between the NN 705 and the NC 701. Once the admission process is completed, the NN 701 becomes a newly admitted EN and can access the data plane, as will be described in greater detail below.

[0041] A PHY profile provides information derived by transmission and reception of probes between nodes. The information in the PHY profile indicates the power levels and modulation schemes that should be used on a particular link. A PHY profile is active when all of the information to determine the power level and modulation scheme to be used in transmitting data to an egress node has been attained and is available.

[0042] The NC 701 responds to the Admission Request message by sending an Admission Response 709 to the NN 705 and each of the ENs 711 in the network. The NN 705 and each EN 71 1 send a Link Acknowledgement 713 to the NC 701. The NC 701 then sends EVM probes 715 to the NN 705. The NN 705 uses the probes 715 to generate a Probe Report 717, which the NN 705 sends to the NC 701. The NC 701 activates the reported unicast PHY profile contained in the Report 717. The NC 701 also generates a New GCD Probe Distribution Report 719 and sends it to the NN 705. The NN 705 responds with a Link Acknowledgement 721 indicating successful receipt of the New GCD Probe Distribution Report 719.

[0043] Upon receipt of the acknowledgement 721, the NC 701 sends a copy of the New GCD Probe Distribution Report 723 to each of the ENs 71 1. Each EN 711 sends a Link Acknowledgement 725 back to the NC 701. Upon receiving a Link Acknowledgement from each of the ENs 711, the NC 701 activates the distributed GCD PHY profiles and starts broadcasting MAPs 727 using the new GCD PHY profile. The NN 705 completes the characterization of the link from the NN 705 to the NC 701 by sending Probe transmissions 729 to the NC 701. The NC 701 then sends an EVM Probe Report 703 based on the received EVM Probes 729. If the NN has requested a rapid admission process, then the NC 701 moves the network to Steady State, completing the Admission Process.

[0044] It will be understood by those skilled in the art that other probes could be exchanged between the NN 705 and NC 701 to characterize the channel between them. By ending the Admission Process before generating PHY profiles for the links between the NN 705 and each of the ENs 71 1, the Admission Process is significantly shortened.

[0045] Once the Admission Process is complete and the network is in the Link Control State = Steady State, the NN 705 can send a RR to the NC 701 to schedule either transmission of a unicast data or a broadcast data. In one embodiment, the newly admitted EN 705 sends the data to the NC 701 as a unicast data 731. The NC 701 will then relay the data 733 to the intended destination EN 711 or broadcast the data if the data is for

broadcasting. Several alternative embodiments can be implemented to allow the NN 705 to communicate to the NC 701 that the NN 705 has data that it would like to send to one or more of the ENs 71 1 in the network. The EN 711 can send data frames 735 to the NC 701 that are intended for the NN 705. The NC 701 will then relay the data frames 737 to the NN 705.

[0046] FIG. 8 is a process flow diagram showing the process used to send information from a newly admitted EN 801 to an intended destination EN 803. In one embodiment, the newly admitted EN 801 sends a reservation request 805 to the NC 807 asking for a transmission from the newly admitted EN 801 to the NC 807. When appropriate based on the rules of inclusion provided by the network, the NC 807 sends a MAP 809 that schedules the transmission in the next appropriate MAP cycle. The newly admitted EN 801 then sends the data 811 (such as an MPDU) to the NC 807. The data indicates in the destination field that the data is intended for the destination EN 803. In response, the NC 807 sends a MAP 813 scheduling transmission of the data from the NC 807 to the intended destination node 803 in the next appropriate MAP cycle. The NC 807 then sends the data 815 to the intended destination EN 803. In one embodiment of the disclosed method and apparatus, upon the request of the newly admitted EN 801 as signaled in the data packet headers, the intended destination EN 803 returns an acknowledgement 817 signaling to the NC 807 that the data packets were successfully received. The NC 807 then relays the acknowledgement to the newly admitted EN 801 either in MAP or unicast it to EN801 directly. The newly admitted EN 801 waits for the acknowledgement before completing the transmission.

[0047] In an alternative embodiment, the NC 807 receives a RR 805 from the newly admitted EN. The RR 805 identifies the intended destination EN 803 as the destination for the transmission being requested. The NC 807 recognizes that there is no PHY profile yet established for the link between the newly admitted EN and the destination EN 803. Therefore, since there is no PHY profile yet established for the requested transmission of data from the newly admitted EN 801 to the destination EN 803, the NC 807 will schedule resources for the newly admitted EN 705 to send the data intended for the destination EN 803 to the NC 807. Once the NC 807 receives the data, the NC 807 relays the data to the EN 803. In one embodiment, the NC 807 sends a MAP 813 that schedules the transmission in the next appropriate MAP cycle.

[0048] In one embodiment of the disclosed method and apparatus, at an appropriate time after the newly admitted EN 801 has completed the admission procedure and can access the data plane, the NC 807 schedules a Link Maintenance Operation (LMO). During the LMO, the NC 807 schedules probes to be sent from the newly admitted EN 801 to each of the other nodes in the network. Probe reports are generated by receiving nodes based on the received probes. In addition, PHY profiles indicating the power levels and modulation schemes to be used for communications from the newly admitted EN 801 to each of the other nodes, including EN 803, are generated and implemented. Once the LMO has been completed, RRs submitted by the new admitted EN 801 to schedule transmissions directly to other ENs 803 in the system can be granted. In one embodiment, as a PHY profile is completed for the link between the newly admitted EN 801 and another EN 803, the NC 807 will become aware of the existence of the PHY profile. The NC 807 activates the PHY profile to allow the newly admitted EN 801 to access the data plane to communicate with each EN 803 for which such an active PHY profile exists. Accordingly, in one such embodiment, it is possible for the newly admitted EN 801 to communicate over the network with some of the ENs 803 directly, before an active PHY profile is available for other ENs 803.

[0049] FIG. 9 is a process flow diagram of yet another embodiment, in which it is possible for the NC 907 to determine that a route over a direct link between in Ingress Node 903 and an Egress Node 904 is more inefficient than a route through the NC 907. In one such embodiment, a RR to schedule a transmission from the Ingress Node 903 to the Egress Node 904 may not be granted. Rather, the NC 907 will establish a link through the NC 907 by which the Ingress Node 903 sends data to the NC 907. The NC 907 then relays the data to the Egress Node 904. In one such embodiment, the Ingress Node 903 sends an RR 905 to the NC 907. The NC 907 determines from the RR 905 that the Ingress Node 903 has data for delivery to the Egress Node 904. The NC 907 responds by sending a MAP 909 to schedule a transmission of the data from the Ingress Node 903 to the NC 907 in the next appropriate MAP cycle. The Ingress Node 903 sends the data 91 1 to the NC 907 at the scheduled time. The NC 907 then sends a MAP 913 to schedule a transmission from the NC 907 to the Egress Node 904. The NC 907 then sends the data 915 received by the NC 907 and intended for the Egress Node 904 to the Egress Node 904. In one embodiment, upon the request of the Ingress Node 903 as signaled in one or more of the headers of the data 915, the Egress Node 904 sends an Acknowledgement 917 to the NC 907 to signal the successful receipt of the data. The NC 907 then relays the

Acknowledgement 919 to the Ingress Node 903 via MAP to signal to the Ingress Node 903 the successful delivery to the Egress Node 904.

[0050] FIG. 10 is an illustration of an Ingress Node 903, an Egress Node 904 and an NC 907 within a network 1000. In accordance with one embodiment of the disclosed method and apparatus, when the following inequality is true, the NC 907 relays the data from the Ingress Node 803 to the Egress Node 904:

M M M

P Ir,NC R,Νϋ NC,E R ^■NC,E -< P_ItE + IFG R

[0051] Where: ΡΙ,Ε is the duration of the data preamble of the data when being sent directly from the Ingress Node 803 to the Egress Node 804;

IFG is the duration of the interframe gap used between data;

M is the size of the data in bits;

¾,Nc is the data rate when the data is being sent from the Ingress Node 903 to the NC 907;

PI,NC is the duration of the data preamble of the data when being sent from the Ingress Node 903 to the NC 907;

PNC,E is the duration of the data preamble of the data when being sent from the NC 907 to the Egress Node 903; and

RNC,E is the data rate when the data is being sent from the Ingress Node 903 to the NC 907.

[0052] Accordingly, when the amount of time required to transmit the data directly from the Ingress Node 903 to the Egress Node 904 is greater than the time required to transmit the data from the Ingress Node 903 to the NC 907 plus the time required to transmit the data from the NC 907 to the Egress Node 904, the data will be relayed by the NC 907. In one embodiment, the determination as to when to relay data through the NC 907 can be made by the NC 907. Alternatively, the Ingress Node 903 can request that the NC 907 relay the data.

[0053] FIG. 1 1 is a simplified block diagram of the hardware used to implement a network node 500 in accordance with one embodiment of the disclosed method and apparatus. The node 500 comprises at least one processor 1 100, a memory 1102, and a PHY 1 104. The memory 1102 is coupled to the processor 1 100. The PHY 1 104 includes an RF front end 1106. The PHY may also include a processor (not shown) that performs functions associated with the PHY 1104. Alternatively, some control functions of the PHY 1104 may be performed by the processor 1 100. In an alternative embodiment, the node 500 may have several processors that work together or independently. The processor 1 100 reads program code from the memory 1102 and executes the code to perform the functions of the DLL 504. In an alternative embodiment, the processor 1 100 also implements the upper layers 512. In one embodiment, a management entity 514 (see FIGURE 5) is implemented by the processor 1 100. In yet another embodiment, the management entity 514 is not co-located with the DLL 504. In one such embodiment, the management entity 514 is implemented using a different processor or multiple processors. Likewise, in one embodiment, the upper layers 512 are not co-located with the DLL 504. It should be clear that the particular physical layout of the logical components is not significant to the disclosed method and apparatus, so long as the disclosed functionality is possible.

[0054] Although the disclosed method and apparatus is described above in terms of various examples of embodiments and implementations, it should be understood that the particular features, aspects and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described. Thus, the breadth and scope of the claimed invention should not be limited by any of the examples provided in describing the above disclosed embodiments.

[0055] Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term "including" should be read as meaning "including, without limitation" or the like; the term "example" is used to provide examples of instances of the item in discussion, not an exhaustive or limiting list thereof; the terms "a" or "an" should be read as meaning "at least one," "one or more" or the like; and adjectives such as "conventional," "traditional," "normal," "standard," "known" and terms of similar meaning should not be construed as limiting the item described to a given time period or to an item available as of a given time, but instead should be read to encompass conventional, traditional, normal, or standard technologies that may be available or known now or at any time in the future. Likewise, where this document refers to technologies that would be apparent or known to one of ordinary skill in the art, such technologies encompass those apparent or known to the skilled artisan now or at any time in the future.

[0056] A group of items linked with the conjunction "and" should not be read as requiring that each and every one of those items be present in the grouping, but rather should be read as "and/or" unless expressly stated otherwise. Similarly, a group of items linked with the conjunction "or" should not be read as requiring mutual exclusivity among that group, but rather should also be read as "and/or" unless expressly stated otherwise.

Furthermore, although items, elements or components of the disclosed method and apparatus may be described or claimed in the singular, the plural is contemplated to be within the scope thereof unless limitation to the singular is explicitly stated.

[0057] The presence of broadening words and phrases such as "one or more," "at least," "but not limited to" or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. The use of the term "module" does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations.

[0058] Additionally, the various embodiments set forth herein are described with the aid of block diagrams, flow charts and other illustrations. As will become apparent to one of ordinary skill in the art after reading this document, the illustrated embodiments and their various alternatives can be implemented without confinement to the illustrated examples. For example, block diagrams and their accompanying description should not be construed as mandating a particular architecture or configuration.

Claims

Claims What is claimed is:

1. A method for admitting a new node (NN) 705, 801 to a network, including: a) generating and activating a PHY profile for a link between the NN 705, 801 and a Network Coordinator (NC) 701, 807 prior to generating a PHY profile for links between the NN 705, 801 and any ENs 71 1, 803 within the network; b) completing a rapid admission process and transitioning the status of the NN 705, 801 to the status of a newly admitted EN 705, 801 ; c) sending data 731, 811 intended for a destination EN 71 1, 803 from the newly admitted EN 705, 801 to the NC 701, 807, when there is no active PHY profile for the link between the NN 705, 801 and the destination EN 71 1, 803 and there is an active PHY profile for the link between the NC 701, 807 and the newly admitted EN 705, 801; and d) sending the data 733, 815 from the NC 701, 807 to the destination EN 71 1, 803.

2. The method of Claim 1, wherein the network is a MoCA network.

3. The method of Claim 1, wherein the NN is rejoining the network after having been in a reduced power state.

4. The method of Claim 1, further including: a) sending an acknowledgement from the destination EN 71 1, 803 to the NC 701, 807 to signal successful reception of the data 733, 815 at the destination EN 71 1, 803; and b) sending acknowledgement from the NC 701 , 807 to the newly admitted EN 705, 801 to signal to the newly admitted EN 705, 801 that the data 733, 815 was successfully received by the destination EN 71 1, 803.

5. The method of Claim 1, wherein sending the data from the newly admitted EN 705, 801 to the NC 701, 807 includes: a) sending a reservation request (RR) 805 from the newly admitted EN 705, 801 to the NC 701, 807 to request that the NC 701, 807 schedule a transmission over the network from the newly admitted EN 705, 801, the RR 805 identifying the destination EN 711, 803 as the intended destination for the transmission; and b) the NC 701, 807 scheduling a transmission from the newly admitted EN 705, 801 to the NC 701, 807 in response to receiving the RR 805 from the newly admitted EN 705, 801 ; and c) sending the data 731, 81 1 from the newly admitted EN 705, 801 to the NC 701, 807 at the time the NC 701, 807 scheduled for the transmission from the newly admitted EN 705, 801 to the NC 701, 807.

6. The method of Claim 5, wherein sending the data 733, 815 from the NC 701, 807 to the destination EN 71 1, 803 includes: a) the NC 701, 807 scheduling a transmission from the NC 701, 807 to the destination EN 71 1, 803; and b) the NC 701, 807 sending the data 733, 815 to the destination EN 71 1, 803 at the time the NC 701, 807 scheduled for the transmission from the NC 701, 807.

7. The method of Claim 1, further including receiving an indication from the NN 705, 801 to perform a rapid admission process and wherein the NN 705, 801 can only perform the following before a PHY profile has been activated for each node in the network, if the NN 705, 801 sent an indication to perform the rapid admission process: a) complete the rapid admission process; b) transition to a newly admitted EN 705, 801; and c) send data 733, 815 to a node other than the NC 701, 807.

8. A method for sending data over a MoCA network, the method comprising: a) determining that the amount of time required to send data directly from an Ingress Node 903 to an Egress Node 904 is greater than the amount of time required to send the data from the Ingress Node 903 to a network coordinator (NC) and from the NC 907 to the Egress Node 904; and b) in response to the determination, sending a reservation request (RR) 805 to the NC 907 requesting the NC 907 to schedule a transmission from the Ingress Node 903 to the NC 907, the RR 805 indicating a Egress Node 904 other than the NC 907 for the data to be sent in the transmission.

9. The method of Claim 8, further including receiving an acknowledgment 919 from the NC 907 that the data was successfully received by the Egress Node 904.

10. A method for sending data over a MoCA network, the method comprising: a) receiving a reservation request (RR) 805 from an Ingress Node 903 requesting to schedule a transmission from the Ingress Node 903 to an Egress Node 904; b) determining that the amount of time required to send data directly from the Ingress Node 903 to the Egress Node 904 is greater than the amount of time required to send the data from the Ingress Node 903 to a Network Coordinator (NC) 907 plus the time to send the data from the NC 907 to the Egress Node 904; c) in response to the determination, sending a MAP 909 scheduling a

transmission from the Ingress Node 903 to the NC 907; d) in response to receiving the data 91 1 from the Ingress Node 903, sending a MAP 913 scheduling a transmission from the NC 907 to the Egress Node 904; and e) sending the data to the Egress Node 904 at the time indicated by the MAP 913.

1 1. A node within a communication network, the node comprising: a) physical layer (PHY) 1 104 having an output that receives and sends

information over a medium 128; and b) a processor 1 100 coupled to the PHY 1104, the processor 1 100 being programmed to: i. instruct the PHY 1 104 to send an admission request requesting rapid admission to the network; ii. instruct the PHY 1104 to exchange probes 715, 729 with a Network Coordinator (NC) 711, 803; iii. activate a PHY profile for a link between the node and the NC 71 1, 803 prior exchanging probes 715, 729 with other nodes for links between the node and any other nodes within the network; iv. complete a rapid admission process and transition the status of the node from NN to EN prior to exchanging probes 715, 729 with other nodes; and v. instruct the PHY 1 104 to send data intended for a destination EN 71 1, 803 to the NC 71 1, 803, when there is no active PHY profile for the link between the NN and the destination EN 711, 803 and there is an active PHY profile for the link between the NC 71 1, 803 and the EN.

12. The node of Claim 11, wherein the node is a MoCA node.

13. The node of Claim 11, wherein the processor 1 100 is further programmed to wait for the PHY 1104 to receive an acknowledgement from the NC 701, 807 that the data intended for the destination EN 71 1, 803 was successfully received by the destination EN 711, 803 before completing the transmission.

14. The node of Claim 11, wherein the process is further programmed to: a) instruct the PHY 1104 to send a reservation request (RR) 805 to the NC 701, 807 to request that the NC 701, 807 schedule a transmission over the network from the node, the RR 805 identifying the destination EN 711, 803 as the intended destination for the transmission; b) receiving from the PHY 1104 a MAP 809 sent to the node from the NC 701, 807; c) instructing the PHY 1104 to send data to the NC 701, 807 in response to receiving a MAP 809 in which the node is scheduled to send the data to the NC 701, 807.

15. A node within a communication network, the node comprising: a) physical layer (PHY) 1 104 having an output that receives and sends

information over a medium 128; and b) a processor 1 100 coupled to the PHY 1104, the processor 1 100 being

programmed to: i. function as the network coordinator (NC) 701, 807; ii. receive an admission request 707 from the PHY 1 104; iii. in response to receipt of the admission request 707, determining that a new node (NN) 705, 801 that transmitted the admission request is requesting rapid admission to the network; iv. instruct the PHY 1104 to exchange probes 715, 729 with the NN 705, 801; v. determine a PHY profile for the link between the NN 705, 801 and the NC 701, 807; vi. activate the PHY profile; vii. receive from the PHY 1104 a reservation request (RR) 805 from the NN 705, 801 prior to activating a PHY profile for links between the NN 705, 801 and the other nodes of the network; viii. in response to the RR 805, instructing the PHY 1104 to send a MAP 809 scheduling the NN 705, 801 to send data intended for the destination node to the NC 701, 807; ix. receiving from the PHY 1104 the data sent from the NN 705, 801 ; x. instructing the PHY 1 104 to send a MAP 813 scheduling the data to be sent to the destination node; and xi. sending the data to the destination node 711, 803, at the time indicated by the MAP 813.

16. The node of Claim 15, the processor 1 100 further programmed to receive from the PHY 1104, an acknowledgement that the data was received from the destination node 71 1, 803.

17. The node of Claim 16, the processor 1 100 further programmed to instruct the PHY

1104 to send an acknowledgment to the 705, 801 indicating successful receipt of the data by the destination node in response to the acknowledgement from the destination node 71 1, 803.

18. The node of Claim 15, wherein the RR 805 requests a transmission to be scheduled for sending data from the NN 705, 801 to a destination node and wherein the processor 1100 is further programmed to recognize that there is no active PHY profile for the link between the NN 705, 801 and the destination node 711, 803.

19. The node of Claim 15, wherein the RR 805 requests a transmission to be scheduled for sending data from the NN 705, 801 to the NC 701, 807, the RR 805 indicating that the destination of the data to be sent is a destination node other than the NC 701, 807.

20. A node within a MoCA network, the node comprising: a) physical layer (PHY) 1 104 having an output that receives and sends

programmed to: i. determine that the amount of time required to send data directly from an Ingress Node 903 to an Egress Node 904 is greater than the amount of time required to send the data from the Ingress Node 903 to a network coordinator (NC) 907 and from the NC 907 to the Egress Node 904; and ii. in response to the determination, instruct the PHY 1104 to send a reservation request (RR) 805 to the NC 907 requesting the NC 907 to schedule a transmission from the Ingress Node 903 to the NC 907, the RR 805 indicating a destination node other than the NC 907 to which data of the transmission is to be sent.

21. The node of Claim 20, wherein the processor 1100 is further programmed to receive from the PHY 1 104 an acknowledgment sent from the NC 907 that the data was successfully received by the Egress Node 904.

22. A node within a MoCA network, the node comprising: a) physical layer (PHY) 1 104 having an output that receives and sends

programmed to: i. receive from the PHY 1104 a reservation request (RR) 805 received from a source node 801 requesting to schedule a transmission from the source node 801 to a destination node 803; ii. determine that the amount of time required to send data directly from the source node 801 to the destination node 803 is greater than the amount of time required to send the data from the source node 801 to a Network Coordinator (NC) 807 plus the time to send the data from the NC 807 to the destination node 803; iii. in response to the determination, instruct the PHY 1104 to send a MAP 809 scheduling a transmission from the source node 801 to the NC 807; iv. in response to receiving the data from the source node 801, instruct the PHY 1 104 to send a MAP 813 scheduling a transmission from the NC 807 to the destination node 803; and instruct the PHY 1104 to send the data to the source node 801 at the time indicated by the MAP 813.