CN101632268A - Parameterized quality of service architecture in the network - Google Patents
Parameterized quality of service architecture in the network Download PDFInfo
- Publication number
- CN101632268A CN101632268A CN200880007820A CN200880007820A CN101632268A CN 101632268 A CN101632268 A CN 101632268A CN 200880007820 A CN200880007820 A CN 200880007820A CN 200880007820 A CN200880007820 A CN 200880007820A CN 101632268 A CN101632268 A CN 101632268A
- Authority
- CN
- China
- Prior art keywords
- node
- network
- service quality
- stream
- response
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
A kind of communication system and method may further comprise the steps: first request that receives is to initiate guaranteed service quality stream in network; Ask to a plurality of node broadcasts second that are connected to network from network coordinator; And reception is from first response to second request of at least one Ingress node.This method also comprises second response to second request of reception from least one Egress node, indicates this at least one Egress node whether to have available resources to receive this guaranteed service quality stream; And if this at least one Ingress node have available resources with transmit should guaranteed service quality stream and this at least one Egress node have available resources and should guaranteed service quality flow to receive, then be this guaranteed service quality flow distribution resource.
Description
Priority request
The application requires in the U.S. Provisional Application 60/900 of submission on February 6th, 2007,206, the U.S. Provisional Application of submitting on February 14th, 2,007 60/901,564, the U.S. Provisional Application of submitting on May 4th, 2,007 60/927,613, the U.S. Provisional Application of submitting on February 14th, 2,007 60/901,563, the U.S. Provisional Application of submitting on May 4th, 2,007 60/927,766, the U.S. Provisional Application of submitting on May 4th, 2,007 60/927,636, and the U.S. Provisional Application of submitting on May 21st, 2,007 60/931,314 priority, more than each piece provisional application all include in this by quoting.
Open field
Method and apparatus of the present disclosure relates to the communication protocol in the network, relates in particular to the quality-of-service protocol in the network.
Background
Except computer, home network generally includes polytype subscriber's equipment that is configured to send by home network subscriber's service now.Subscriber's service comprises by home network sends such as multimedias such as stream audio and stream videos to subscriber's equipment, and wherein multimedia is presented to the user at subscriber's equipment place.Along with the increase of the number of available subscriber service, the number that is connected to the equipment of home network is also increasing.The increase of the number of service and equipment can increase the complexity of the coordination between the network node, because each node may be produced at different time by different manufacturers.Having emerged some home intranet technology promotes simple home network solution and utilizes the existing network infrastructure that may exist in many families attempting.For example, home telephone network alliance (HPNA) makes the user to connect up the Connected Home computer by using existing telephone and coaxial cable in the family.Enable the equipment utilization frequency spectrum different with the employed frequency spectrum of phone of HPNA with fax.Be not to use existing telephone and coaxial cable wiring, plug-in alliance of family (
Power Alliance) utilize the existing power wiring in the family to create home network.
A problem be that the network bandwidth significantly reduces because of the bigger variation of the imaginary loading in family's power wiring and the socket easily.
In addition, these technology also can have problems when realizing correctly with the mutual network equipment of other network equipments.The deployment of the more novel device of the service that these problems may be developed after restriction under the situation that has outmoded (tradition) equipment provides.Emerging multimedia over Coax Alliance (MoCA) standard architecture affects this problem in the following areas: (1) network behavior dynamically to device assignment " network coordinator " (NC) role so that optimize performance, (2) traffic of every other node in known only promising NC role's the equipment ability dispatch network, and (3) form complete mesh network architecture between any equipment and peer-to-peer thereof.
Share in many potential application under the situation of same digital network, various application must be competed identical finite bandwidth, make distribution problem complicated more.Other prior application degradations that may cause shared network such as the high-throughput download bandwidth intensive application.When these other application need high quality-of-services, this result is difficult to accept.
Proposed the various solutions of head it off, be usually directed to the high-level network controller or have senior should being used for priority is set for the packet in the network or data traffic.And Intelligent Network Element needs high rated output, and therefore more expensive than their needs.At last, it is unpractical that the complicated network equipment is used for family's use, because most consumers does not possess the technical ability or the experience of configuration computer network.
Open general introduction
In one embodiment, a kind of communication means may further comprise the steps: (1) receives first request to initiate guaranteed quality of service data stream in network; (2) ask to a plurality of node broadcasts second that are connected to network from NC; And (3) receive first response to second request from least one Ingress node.Second request is based on first request, and whether first at least one Ingress node of response indication has available resources to transmit this guaranteed service quality stream.This method also comprises second response to second request of reception from least one Egress node; And if should (a bit) Ingress node have available resources should guaranteed service quality stream and should (a bit) Egress node have available resources and flow to transmit with this guaranteed service quality of reception, then be this guaranteed service quality flow distribution resource.
In another embodiment, a kind of system comprises physical interface that is connected to coordination network and the service quality module that is coupled to this physical interface.This physical interface is configured to transmit and receive message by coordination network.This service quality module is configured to by the one or more guaranteed service quality streams of many articles of the 2nd layer of message access in coordination network.
The accompanying drawing summary
The embodiment of Fig. 1 diagram network architecture.
Fig. 2 is the diagrammatic sketch that illustrates according to two L2ME periods of wave of the embodiment of Fig. 1.
Fig. 3 diagram is according to the block diagram of the L2ME frame of the embodiment of Fig. 1.
Fig. 4 is the block diagram according to the 2nd layer management entity transaction protocol of an embodiment.
The embodiment of Fig. 5 diagram parameterized quality of service network architecture.
Fig. 6 diagram converts TSpec XML to the decision tree of the L2ME of QSpec.
Fig. 7 is the diagrammatic sketch that illustrates according to establishment/renewal affairs of the embodiment of Fig. 5.
Fig. 8 is the diagrammatic sketch that illustrates according to the deletion affairs of the embodiment of Fig. 5.
Fig. 9 is the diagrammatic sketch that illustrates according to the tabulation affairs of the embodiment of Fig. 5.
Figure 10 is the diagrammatic sketch that illustrates according to the inquiry transaction of the embodiment of Fig. 5.
Figure 11 is the diagrammatic sketch that illustrates according to the care of transaction of the embodiment of Fig. 5.
General view
Shown in open herein and Fig. 5 and following a kind of system of description in more detail comprise the physical interface 512 that is connected to such as coordination networks 502 such as MoCA 1.1 networks, such as multimedia over Coax Alliance (MoCA) PHY layer.Physical interface 512 is configured to transmit and receive message by coordination network 502.This system also comprises service quality (QoS) manager 520 that is connected to the 2nd layer management entity (L2ME) 516.QoS manager 520 is configured to by being flowed by the one or more guaranteed quality of service data of many articles the 2nd layer message access in coordination network 502 of L2ME 516 management, for example the unidirectional traffic flow of (trap equipment) from single Ingress node (source device) to one or more Egress nodes.
A kind of network architecture disclosed herein is supported the parameterized quality of service (pQoS) in the managed network.In enabling the network of pQoS, the data flow in the network can include assurance (parametrization) and/or the data flow of doing the best.Guarantee that guaranteed (parametrization) stream is on defined at least one performance class of predefined parameter of the stream set up in the following access that goes through (foundation) process.If parametrization stream does not have data to transmit during its time slot, then can make the time slot that keeps for this parametrization stream can be used for other stream.Shown in Fig. 6 and in the following disclosed structure of describing in more detail, transmit QoS such as nodes 604 such as c link data link layers to network coordinator (NC) node 606 and initiate request to initiate to have the guaranteed service quality stream of at least one mass parameter.NC 606 comprises the 2nd layer of request initiating at least one parameter of request from this QoS to all node 604,608 broadcasting.The a plurality of nodes 608 that comprise Ingress node 508 and Egress node 510 transmit the response to this broadcast request, and whether its indication Ingress node 508 has available resources is transmitted this stream and Egress node 510 and whether have resource and receive this stream.If the response of receiving indication Ingress node and Egress node 508,510 have resource separately and set up this stream, then NC node 606 indicates these nodes 608 to promise to undertake resource to this stream to these a plurality of node 608 broadcasts.
Describe in detail
This description of each embodiment is intended to come together in conjunction with the accompanying drawings read, and accompanying drawing will be considered to the part of whole written description.
Each embodiment relates generally to device, system, method and the framework in order to the rudimentary information receiving and transmitting framework in the network enabled.Some embodiment promote the 2nd layer of information receiving and transmitting so that can carry out low-cost and high-speed management to the resource in the network, thereby ensure distributing multimedia data in existing home network (such as, video/audio, recreation, image, general data and interactive services) ability.
Each embodiment is convenient to make home intranet equipment to oversimplify, thus their easier uses and have cost efficiency.In other words, home network disposes should be simpler, thereby the domestic consumer needn't handle complicated configuration menu or need the higher level knowledge of computer network.Each embodiment is also by realizing not needing the rudimentary digital transport frame of high rated output amount to solve configuration and cost problem.This rudimentary framework can be considered to the expansion of medium access control (MAC) sublayer or physics (PHY) network layer, and is called as " the 2nd layer of information receiving and transmitting framework ".
The 2nd layer of information receiving and transmitting can be implemented in the diverse network, wherein owing to the introducing of node or remove and the evolution of network signal ability is shared and consulted frequency spectrum.In certain embodiments, network is the cooperative type network with network coordinator (NC) of the communication between some equipment of coordinating to be connected to network.Coordination is to reach to the time slot that the network equipment distributes these equipment therebetween can transmit or receive MAC message, detection and data by NC.Be connected to cooperative type network of network equipment and can comprise managed equipment and not managed equipment.The example of these networks comprises according to cable network or wireless home network on the coaxial network of multimedia over Coax Alliance (MoCA) standard, " multiple twin " line.Each embodiment is described to realize with 8 in the network or 16 nodes in this article.Yet other embodiment can include expansion in to realize the node of any number in diverse network.In addition, each embodiment can comprise having in order to support the end user to use and because of the 2nd layer of information receiving and transmitting framework of the different service of supplier and system, the method and apparatus of agreement.
Referring now to the 2nd layer management entity (L2ME) framework and the information receiving and transmitting agreement that are used for digital network each embodiment is described.Some embodiment support application layer-triggered transactions, such as, but not limited to, UPnP (UPnP) service quality and IEEE stream reservation protocol (SRP).The 2nd layer of information receiving and transmitting agreement can realize in network such as abilities such as parameterized quality of service (pQoS) affairs.Notice that L2ME may be different with the interface between the application layer.
Fig. 1 diagram has the cooperative type mesh network architecture 100 of a plurality of network nodes 104,106,108,110 that are connected to network 102.Network node 106 is NC nodes and is illustrated as disposing PHY layer 112, media access control sublayer 114 and L2ME 116.Notice that any network node can have a plurality of physical interfaces and can realize upper-layer functionality (for example, TCP/IP, UDP etc.).Network node 104 is to enter node (EN).In the node 104,108 and 110 each is also configurable L2ME 116.
L2ME ripple agreement
L2ME ripple agreement provides reliable transmission service by generating a plurality of periods of wave for the L2ME transaction protocol.The L2ME ripple comprises one or more L2ME period of wave.Comprise that message from NC to one or more nodes transmits and receive the respective response to this message from these one or more nodes period of wave.When NC node 106 to all nodes 104,108,110 broadcasting that are connected to network 102 during such as specific payload such as requests, begin period of wave.In one embodiment, NC node 106 at first became 3 classifications with all node-classifications in ripple _ node mask (nodemask) field (following description in more detail) before initiating period of wave.The node of first category (" classification 1 node ") comprise also not the request L2ME frame that NC node 106 sends the cycle _ the node mask field in the network node of appointment.The node of second classification (" classification 2 nodes ") comprise the request L2ME frame that NC node 106 sends the cycle _ identify in the node mask field but NC node 106 is not received the network node of response as yet from it.The node of the 3rd classification (" classification 3 nodes ") comprises that NC node 106 received the network node of response L2ME frame from it.
After NC node 106 classified as classification 1,2 or 3 nodes with in the network node 104,108,110 each rightly, NC node 106 was according to following guilding principle structure cycle _ node mask.At first, if having 3 or more multi-class 1 node, then NC node 106 with the cycle _ the bit of respective number in the node mask is made as " 1 ".If have 3 or more multi-class 1 node, the cycle _ the node mask in the number of the set bit of NC node 106 may be less than the sum of classification 1 node, but be no less than 3 bits.For example, if there are 5 classification 1 nodes, then NC node 106 can with the cycle _ 3,4 or 5 bits in the node mask are made as " 1 ".Secondly, if having 3 or more multi-class 2 nodes, then NC node 106 with the cycle _ be made as " 1 " corresponding to 3 of classification 2 nodes or more bits in the node mask.The 3rd, if there is not classification 1 node, if perhaps the cycle _ all be set as " 1 " corresponding to all bits of classification 1 node in the node mask, then NC node 106 with the cycle _ be made as " 1 " corresponding to the bit of classification 2 nodes in the node mask.At last, NC node 106 can with the cycle _ the node mask in as NC node 106 can from its receive response and not the bit more than the interrupt network service like that be made as " 1 ".In case generated the cycle _ the node mask, NC node 106 just by broadcasting comprise this cycle _ the L2ME message of node mask initiates period of wave.
Finish during timer expiration when NC node 106 some or all from node 104,108,110 are received such as corresponding payload such as responses or at the NC node period of wave.For example, NC node 106 transmits message and starts its timer subsequently.If receive from the cycle _ some or all response message in the network node that identifies in the node mask before the timer of NC node 106 arrive T21 (for example, 20 milliseconds), even then NC node 106 is not received response message as yet, finish period of wave.Notice that T21 is that NC node 106 transmits request L2ME frames and is requested node and transmits the maximum that responds between the L2ME frame accordingly and can allow the time interval.When in the node that identifies in the ripple _ node mask field of effective load each had all responded, L2ME completed successfully period of wave.In another way, if network node 104,108,110 all is classified into classification 3 nodes before the timer of NC node 106 arrives T21, then success period of wave.Perhaps, if NC node 106 do not receive from its NC node 106 transmitted the cycle _ corresponding bits in the node mask is set as the response L2ME frame of classification 2 nodes of " 1 ", then period of wave unsuccessful, or i.e. failure.If failure period of wave, then NC node 106 is not by only receiving that from it those nodes of response L2ME frame send multicast message and come the repetitive wave cycle to NC node 106.Note, in one embodiment, come the repetitive wave cycle, treat multicast message in the same manner with broadcast at sending multicast message by node to not response.NC node 106 will be finished the period of wave of being dispatched before creating new period of wave for any node of not receiving response from it.
Fig. 2 is the example that the L2ME ripple diagrammatic sketch 200 of two periods of wave 214,216 is shown.When NC node 206 with node ID=2 when all nodes 202,204,208,210,212 broadcasting that are connected to network 102 have the message of payload, initiated for first period of wave 214.In this example, payload comprises node _ bit-masks 011011, wherein node corresponding to node ID=0 of rightmost.The payload that comprises from the ripple _ ACK of node 202,204,208 and 210 is received in 206 expectations of this bit-masks indication NC node.As shown in Figure 2, before NC node 206 timer expiration, NC node 206 is only received the response L2ME frame from node 202,204 and 208, and from the response L2ME frame of node 210 or lose or do not receive.The expiration of timer finished for first period of wave 214 in the NC node 206, did not establish affairs but finish this.
Because NC node 206 is not received response L2ME frame from node 210 as yet, so NC node 206 sends another request L2ME frame to node 210, thereby initiates for second period of wave 216.The request that sends to node 210 also sends to node 212, and comprises requesting node 210 and the 212 node _ bit-masks 110000 to NC node 206 transmission ripple ACK.Received by NC node 206 from the response L2ME frame of node 210 and 212 is follow-up, thereby finish period of wave 216.
The L2ME transaction protocol
The L2ME transaction protocol is to use a plurality of L2ME ripples to reach the higher sublayer agreement of the affairs of network range among the L2ME.Generally speaking, all L2ME affairs all comprise j+1 ripple (j=0 wherein, 1,2...), and start by EN or NC node.EN can be based on the end user and use any network node of initiating the L2ME affairs, comprises the NC node.In the end in the L2ME ripple, the result who is asked returns to EN by the NC node.When requested network node provided its final response, the L2ME affairs were finished.In one embodiment, in network, have only L2ME affairs to be performed at any given time or co-pending.For the L2ME ripple of failure, the NC node action that the result causes depends on concrete L2ME transaction types and ripple numbering.
Generally speaking, during affairs all L2ME transaction message can be classified into 3 different classes of.These message are classified as follows: submit to (1); (2) request; And (3) response.Do not use the node of L2ME message can abandon these message simply such as conventional node that does not dispose L2ME etc.The node that does not dispose L2ME can receive L2ME message, because L2ME message is embedded in original MAC information receiving and transmitting framework.An example of Fig. 3 diagram mac frame 300.Mac frame 300 comprises mac header 302, MAC payload 304 and MAC payload Cyclic Redundancy Check 310.The L2ME frame is embedded in the MAC payload 304 and comprises L2ME header 306 and L2ME payload 308.
Submit L2ME message to
Submit to L2ME message will use the request of initiating and be carried into the NC node, can initiate L2ME ripple affairs at NC node place from EN.Each stage that EN runs affairs usually, and the NC node is responsible for broadcast request, collects the response of each node and is provided transaction results to the EN that has transmitted this submission message.An example of L2ME frame format is submitted in following table 1 diagram to, and this frame format comprises submits L2ME frame header and payload to.
Table 1-submits the L2ME message format to
Submit to L2ME frame header to comprise that 8 enter _ affairs _ id field.Enter _ affairs _ id field is the affairs ID that enters node, it starts from " 1 " and sends to the NC node at every turn submits to message just to increase progressively.When not having EN, EN_ affairs _ ID=0 value is preserved for the NC node.Come from and submit to any L2ME affairs of message can comprise these affairs ID.Note, enter node ID and affairs ID the combination uniqueness each the L2ME affairs in the marked network, be triggered thereby make EN can know its affairs.In addition, overtime if EN waits for that affairs begin, uniqueness ground each affairs of sign make EN can discern and cancel any trial that the NC node will begin affairs.The composition and the length of L2ME_ payload field depend on concrete supplier _ ID, affairs _ type and affairs _ sub-type field.Supplier _ ID submits and asks to indicate in the L2ME message 16 bit fields of using the various field of these message because of the supplier strange land to.For example, the supplier that the assigns _ ID scope of the quick communication of entropy (Entropic Communications) be 0x0010 to 0x001F, and value 0x0000 is assigned to MoCA to 0x000F.The length of L2ME_ payload field can be shorter than or equal L_SUB_MAX (length _ submission _ maximum).Also note to have identical one group of supplier _ ID, affairs _ type and affairs _ sub-type field with submission and the request message that given L2ME affairs are associated.
Request L2ME message
During transaction Wave, the NC node is to all node broadcasts request L2ME frame messages.The NC node has been received among the embodiment who submits message to therein, and the NC node will be broadcasted request L2ME frame message as the result who submits message to.In some cases, as described below when the NC node serves as EN, do not transmit and submit to message and NC node to initiate affairs by representing it oneself to send request L2ME frame message.For example, when the NC node is initiated management transaction, do not need to submit the L2ME frame to, and affairs begin with request L2ME frame.The result of the affairs that each node that request L2ME frame message is received in expection is all asked in payload with the NC node responds the NC node.Table 2 illustrates request L2ME frame message header and payload format, and it is similar to submits L2ME frame format, wherein not shown mac header to.
Table 2-request L2ME frame message form
In this message, enter _ node _ ID is replicated in and initiate submits message to.If request message is derived from the L2ME affairs such as no EN such as NC management transactions, then enter _ node _ affairs _ nonsensical and this field value of ID is reset " 0 ".If this is a L2ME ripple, then ripple _ node mask value equals to submit to message.In the last L2ME ripple of affairs, the value of this field comprises this group node that will be the part of postwave.Otherwise, this group node that responds is provided among the participation _ next one _ Bob spy of ripple _ node mask value corresponding to request formerly.The cycle _ the node mask is the bit-masks of node, wherein each bit position is corresponding to node ID (that is, bit 0 value is corresponding to node ID=0).If be set up with the corresponding bit of each node---the NC node instructs this node that response is provided when receiving request message.In addition, request message comprises ripple _ mode field, its indicate previous period of wave be the failure or complete successfully.Notice that the value that allows in ripple _ mode field is 0,1,2 and 4, and if response _ failure and/or NC_ cancellation _ failure bit be set, then this is the last L2ME ripple of affairs, and any follow-up ripple can comprise the L2ME_ payload field of the affairs of failing.
Be used for L2ME ripple (except ripple 0) response frame payload usually by cascade formerly prewave form from the response of each node.The following formation of cascade: when response L2ME frame when given node arrives at the NC node, its payload is invested the end of response queue at NC node place.Then, the length of payload is write in the data structure that is called catalogue, and transmit the ID of this node.When the NC node was ready to send next one request L2ME frame, its length with catalogue was put into catalogue _ length field, and this catalogue is copied to the initial of payload, and subsequently response queue is copied in the remainder of payload.
Catalogue length in the payload portions of catalogue _ length field indication request L2ME frame message.The L2ME_ payload field of in request L2ME frame message, using have 4 kinds dissimilar, as follows:
1. if this is a L2ME ripple of given affairs, then the L2ME_ payload of the first kind is identical with the payload of submitting message to.The length of this L2ME_ payload field can be less than or equal to L_SUB_MAX, and L_SUB_MAX is the maximum number of the byte in the submission L2ME frame payload of cascade.
As shown in following table 3 from second ripple of affairs ripple to the end, the request L2ME frame payload of second type is sent to the participation node as report from the NC node.L2ME_ payload field comprises catalogue and the response _ data field that has from 16 clauses and subclauses of 2 byte entries of each node, and it is to participate in the cascade of the elongated response L2ME frame of L2ME node from each that response is provided in the prewave formerly.This catalogue makes receiving node can decode from the L2ME response of all nodes.
Table 3-request " cascade " L2ME frame payload form
3. the L2ME_ payload of the 3rd type is wherein to respond _ fail the situation that bit or NC_ failure bit is set as the failure L2ME affairs of " 1 ".The NC node in the end transmits 0 length payload in the request message of L2ME ripple.
4. the L2ME_ payload of the 4th type is used to support some specific L2ME affairs, such as parameterized quality of service.In this payload, the catalogue _ length in the request L2ME frame header is not used, and the response of all nodes of NC node processing is to produce customization claim frame payload.The form of L2ME_ payload field defines in specific L2ME affairs.Notice that the claim frame of no payload comprises the type-iii reserved field of 64 bits.
Response L2ME message format
Response L2ME frame format is as shown in following table 4.When each L2ME ripple finishes, there is the node of L2ME transaction-capable to send response L2ME frame to NC node clean culture ground from each.In certain embodiments, the NC node can be configured to receive simultaneously a plurality of (for example, 3 or the more) response from being requested node.
Table 4-response L2ME frame format
Response L2ME message comprises response _ mode field, and its indication is requested the responsive state of the node that responds in next or period of wave at last.In addition, response _ mode field makes EN can cancel it by sending that submission message is initiated to the NC node but the overtime affairs of wait-for-response message.
Receive any L2ME transaction message if enable the network node of L2ME with unidentified supplier _ ID, affairs _ type or affairs _ subtype field value that goes out, then this node can in response frame, will respond _ mode field is made as " 0 ", and the NC node can these affairs with incoming wave in get rid of this node.In any response, be provided with in ripple _ node mask that the EN of participation _ special field of last _ Bob and any other node can be included in postwave.
The general view of L2ME affairs
The L2ME affairs can be initiated in several ways, although can carry out only L2ME affairs at any given time usually in network.In one embodiment, the L2ME affairs can be initiated by EN, and EN can be any node that is connected to network.For example, EN can be the MoCA network node that is connected to computer.Computer may be attached to the application that internet and operation are communicated by letter by means of upper-layer protocol interface more.In this configuration, computer can monitor whole M oCA network as agency's (following description in more detail) to carry out the L2ME information receiving and transmitting by the affairs that generate in response to application in the computer with this EN.
With reference to figure 4, an example of the affairs of EN initiation is described now.Fig. 4 diagram is by the block diagram of an example of the L2ME affairs 400 of EN 402 initiations.When the request of receiving from senior application, EN 402 generates and submits L2ME message to and send it to NC node 404.NC node 404 receives this submission message and initiates a L2ME ripple by broadcasting and the request message that the submission message that is received from EN 402 has similar header, and promptly the L2ME ripple 0.This request message is broadcast to each in the specified node that the L2ME ability is arranged 406,408,410 of ripple _ node mask field of comprising in payload.If this request is sent to the node of no L2ME ability, then this node is ignored this message simply.
Request L2ME frame message also is sent to EN 402, describes its reason now.When receiving request message, EN 402 verifies this affairs by the just suitable field in the request header is compared with its value of using in the submission header.If these are worth coupling, then affairs are with processed.Yet may have L2ME affairs in the network is not some examples of the EN 402 nearest affairs of being asked.This circumstances is destroyed in the submission message that EN 402 is transmitted, do not received by NC node 404 or occur when being permitted by NC node 404.If the affairs of being initiated not are the L2ME affairs of nearest request, then EN 402 can by in response, will carry out _ enter _ cancel bit to be made as " 1 " and to cancel this affairs.Receive from its of EN 402 carry out _ enter _ cancel the response that bit is set as " 1 " when, NC node 404 will not send more L2ME ripples in these affairs, but can initiate another L2ME affairs immediately.
Suppose that these L2ME affairs are not cancelled by EN 402, then requested have the node of L2ME transaction-capable to send response messages to NC node 404, and whether its payload indication they select to participate in the next one (a plurality of) ripple of these affairs.If for example these affairs are can not to flow by support parameter QoS in order to parametrization QoS affairs and this node of creating new argument QoS stream, then this node can select not participate in ripple in the future.Node can by will participate in _ next one _ Bob is ad hoc selects to participate in this web transactions for " 1 ", and can by will participate in _ next one _ Bob is ad hoc to be that " 0 " is selected not participate in.In follow-up L2ME ripple, the 404 common cascades as described above of NC node generate request L2ME frame payload from all responses of first prewave.NC node 404 sends to this request message the node of having asked to participate in working as prewave subsequently.Notice that for something affair embodiment, the NC node may produce different, non-concatenated Request message payload according to the response payload of receiving.These affairs continue, and arrive the maximum numbering of submitting ripple specified in the L2ME message to until the NC node.When arriving the maximum numbering of this affairs medium wave, NC node 404 sends postwave, and it comprises the request L2ME frame message to EN 402.
Yet, if NC node 404 is received to have by oneself its participation _ next one _ Bob spy of all nodes of L2ME ability and is set as the response of " 0 " and has EN 402, then NC node 404 can be skipped intermediate wave and the synthetic just suitable request payload in these affairs.If originally will use cascade to come the request to create payload, then NC node 404 is filled into catalogue _ node _ ID=0xFF in all clauses and subclauses of catalogue, and the request of synthesizing can make affairs _ ripple _ numbering be set to postwave rightly.
In a plurality of L2ME affairs, after every other node had responded, NC node 404 can only ask EN 402 to provide response to its request message.This response of finishing the L2ME ripple in the various affairs guarantee EN402 notify its use these affairs finish before these L2ME affairs finish fully.In other L2ME affairs, these affairs are just finished when a plurality of nodes (comprising EN 402) send request and receive response from each node until NC node 404.
In some instances, whole L2ME affairs may be made mistakes.This circumstances is for example occurring under the following situation: (1) L2ME fails period of wave; (2) number of executed L2ME ripple is less than the expection total number of L2ME ripple indicated in affairs _ last _ ripple _ number field in initiate submitting L2ME message in the given affairs; And (3) L2ME affairs are initiated by EN.In one embodiment, if the failure of L2ME affairs, then NC node 404 sends the new L2ME ripple that is called as affairs failure ripple.This ripple notice is owing to the failure of previous L2ME ripple stops this affairs.This affairs failure ripple is initiated by the NC node 404 that sends request L2ME frame header, and as defined in last table 2, its ripple _ mode field is made as " 4 ", and ripple _ node mask makes its bit corresponding to EN402 be set as " 1 ".In addition, request L2ME frame is 0 long payload as described above.When receiving this request, EN 402 sends the as above response L2ME frame shown in the table 4.
In another embodiment, NC node 404 can spontaneously be initiated the L2ME affairs has the L2ME transaction-capable with other which nodes of informing network node.But the affairs that these NC nodes are initiated carry out and are designed to reaching network operation by providing with the interoperability manipulation of tradition or other compatible nodes usually in single ripple.The L2ME ripple affairs of being initiated by the NC node have following characteristic usually:
1. in order to define the ripple duration, the NC node should the cycle _ comprise at least 3 nodes in the node mask field;
2. if the NC node is not received in NC_ is overtime from the intended response that is requested node, then the NC node supposes that this response no longer is pendent;
3. before every other node had been required to send for the first time its response, NC node not requesting node retransmitted its response; And
4. in the T21 of second request, fail to provide any node of response (under requested situation) to cause the failure of L2ME ripple.
Ripple _ node mask field indication is identified as this group node of the node of having enabled the L2ME affairs by NC node 404.If node is by 404 identifications of NC node, then it uses 0 length response message to respond according to following table 5 and finishes this affairs.
Table 5-enables the response frame form of L2ME
Parameterized quality of service architecture
An embodiment of network parameter service quality (pQoS) section is described now.Notice that home network can comprise a plurality of pQoS sections, such as 802.11 sections of coaxial network, MoCA section and IEEE.The pQoS section can be to share any networking node cluster of identical PHY and MAC layer, and it guarantees that the stream that enters network at the Ingress node place will guarantee to arrive at one or more Egress nodes with pQoS.It is to provide the guarantee of predetermined data rate at least for the data communication from the Ingress node to the Egress node that pQoS guarantees.In one embodiment, each pQoS section has its oneself ID, and this ID is the MAC Address of NC node normally.How upper strata pQoS logic entity can stride some pQoS sections foundation streams if can being configured to regulation.Notice that the all-network node is all worked usually in identical pQoS section.
Usually, network can be divided into 3 classifications: (1) legacy network, such as the network of no L2ME affairs or pQoS function; (2) enabled the network of parametrization QoS; And (3) have forbidden the network of parametrization QoS.Any network node of operating in the network of having enabled L2ME has under the situation of operating in the network of other legacy equipments at this node and will turn round as legacy equipment.In one embodiment, each network node has L2ME and pQoS ability.
In certain embodiments, if any in the network node do not supported pQoS, then pQoS is with disabled.For example, add the network enabled pQoS if there is the node of pQoS ability, then this network will be ended to support pQoS, and will stop to create new pQoS and flow and all have the pQoS ability until the all-network node.If network node attempts creating new stream, then will set up the network node transmission error messages of this new stream to request.In addition, pQoS stream will no longer be guaranteed, and grouping will be used as the prioritization traffic or the traffic of doing the best is treated.
Yet, if thereby the node deviated from network that does not have a pQoS ability only stays the node of pQoS ability, and network is scalable and enable the pQoS transmission.When upgrading to pQoS, prioritization stream will be upgraded by Ingress node until as described below to renewal the time still as prioritization stream.
With reference to figure 5, an embodiment based on the pQoS framework of L2ME framework will be described now.The parametrization QoS network architecture 500 comprises the network 502 with a plurality of nodes 504,506,508,510.Network 502 can be the cooperative type network, comprises coaxial network, mesh network or wireless network according to the MoCA standard.In one embodiment, each in some nodes 504,506,508,510 has PHY layer 512, media access control sublayer 514 and L2ME 516.In UPnP service quality environment, L2ME 516 and QoS device service 518 interfaces.In non-UPnP environment, L2ME and the just suitable quality of service applications entity (not shown) interface that is used for Service Quality Management.L2ME 516 also be configured to as following explain in more detail will be adapted to the 2nd layer of compatible message from the message of higher layer applications.
Some nodes 504,506,508,510 also dispose high-rise ability, and it comprises QoS device service 518, the service 520 of QoS manager and qos policy retainer service 522.QoS device service 518 receives the action invocation from QoS manager service 520, and the result that will move reports to QoS manager service 520.QoS equipment 518 is with oneself or by utilizing low layer to carry out action via L2ME 516.
As shown in Figure 5, node 504 is to enter node, and node 506 is NC nodes.Node 508 and 510 is respectively Ingress node and Egress node.Note in any network 502, may having a plurality of Egress nodes 510.Suppose that end user's application need for example is used for from Ingress node 508 to Egress node the specific bandwidth of 510 video flowing.Traffic flow is shown to have usually from Ingress node 508 to Egress node the flow of 510 way flow.The end user uses and knows Ingress node 508, Egress node 510 and flowing content usually.The end user uses the traffic specification (TSpec XML) that may also know content.
TSpec XML can comprise the various parameters of bandwidth, grouping size, stand-by period and the loss tolerance of describing stream.In the bandwidth parameter some comprise average data rate, peak-data rates and maximum burst size.The grouping size parameter can be specified minimum and largest packet size, and nominal packet size.The stand-by period parameter comprises that maximum delay changes and minimum and maximum service intervals.
In the pQoS environment and as shown in Figure 6, L2ME 606 is suitable for converting TSpec XML to the 2nd layer of special-purpose QSpec.L2ME 606 can by simply with TSpec XML as QSpec, select some parameters of TSpec XML be used for QSpec and ignore other parameters or select some parameters of TSpec XML and convert these parameters to the QSpec form to come from TSpec XML conversion QSpec.Some comprised COS in the QSpec parameter, peak-data rates, average data rate and maximum, minimum and nominal packet size.
End user's application construction traffic descriptor and to ask QoS manager 520 be that the stream of being asked is provided with required QoS resource.The traffic descriptor can comprise that the traffic ID of the source that defines video flowing and trap information, TSpec XML and other relevant informations is to provide parametrization QoS.Represent the QoS manager 520 request qos policy retainer services 522 of end user's using action as traffic descriptor to provide proper strategy of fitting for the video flowing of being asked with describing.Be provided for the just suitable strategy of the video flowing of being asked to QoS manager 520 as the qos policy retainer service 522 of the storeroom of the qos policy of network 502.This strategy can be used for being provided with the relative importance of traffic stream.User's importance numbering is used to guarantee the most important traffic flow of user is received respective priority to Internet resources.Based on this strategy, QoS manager 520 configuration QoS device service 518, thus make Ingress node 508 and Egress node 510 can handle the new video flow.Notice that qos policy retainer 522 and 520 services of QoS manager can reside on any node 504,506,508,510 or reside on another parametrization QoS section.
The cost of pQoS stream
Before the pQoS stream in access or renewal network, whether whether NC node 506 must decision can permit specific stream request, for example have sufficient Internet resources to use.NC node 506 was made about whether answering the decision of access stream originally by the one-tenth of at first determining pQoS stream.Stream cost (CF) is in order to supporting the tolerance of the specific bandwidth that given pQoS stream is required, and in the crack _ express in the time field (that is, the crack time, wherein the crack time is the linear module that equals 20ns).Notice that in one embodiment, the primary bandwidth unit is time slot but not transfer rate (for example mbit/).Yet in alternative embodiment, CF provides as transfer rate.
For each establishment or renewal pQoS stream affairs (following definition in more detail), CF can periodically be calculated by Ingress node 508.NC node 506 can use this CF to calculate to decide whether allow the pQoS stream of being asked in the network.CF (multiple of crack _ time/second) can followingly calculate:
Wherein,
Table 6-formula (1) parameter list
| Parameter name | Describe |
| ??N pps | The sum of grouping that per second transmits |
| ??T min | The minimum packet size transmission time |
| ??L p | Comprise the block length (byte) that RS fills |
| ??OFDM b | Every OFDM symbol bits number based on the PHY distribution that is used to transmit |
| ??T CP | Circulating prefix-length (multiple of crack _ time) |
| ??T FFT | The IFFT/FFT cycle (multiple of crack _ time) |
| ??T IFG | The IFG cycle (multiple of crack _ time) |
| ??L pRE | The length of per minute group preamble (multiple of crack _ time) |
N
PPSMAX is the number of OFDM (OFDM) code element of each grouping, wherein
Be the round-up integer of X, it multiply by OFDM Baud Length (multiple of crack _ time/second).Notice that the length of OFDM code element depends on the network channel characteristic.After the per minute group is added preamble length and interframe gap (IFG) length, N
PPSMAX multiply by the sum of grouping that per second transmits, and the latter is given divided by nominal packet size by peak packet rate.The cost of all of each Ingress node 508 existing stream N (no packet aggregation) is provided by following formula:
In order to make Ingress node 508 accept new stream, its maximum available bandwidth must be more than or equal to the cost of current stream and new stream.This condition is provided by following formula:
Formula (3)
In case Ingress node has been accepted new pQoS stream, NC node 506 should judge whether the cost---cost that comprises new pQoS stream---of all the gathering pQoS streams on all nodes is less than or equal to maximum total available network bandwidth.M node arranged in the hypothetical network, and then total available network bandwidth must meet the following conditions:
BW wherein
NCIt is the overall network bandwidth.In certain embodiments, total available bandwidth of pQoS service deducts 80% behind the cost of all expenses in the network for the overall network bandwidth, and all expenses can comprise all controlling links groupings, reservation request, access control and survey.If formula (4) is true, then the new pQoS of NC node 506 accesses flows to network.If formula (4) is not true, then following available stream bandwidth (AFBQ) is asked and returned to NC node 506 refusal streams:
In order to make the NC node accept new stream, the node capacity of each in Ingress node 508 and the Egress node 510 must be more than or equal to the cost of existing stream that passes through this node and new stream.This condition is provided by following formula:
Residue node capacity (residue _ node _ capacity) is left side and right side poor of formula (6), and is one of NC node 506 employed bandwidth correlation criterions before permitting specific stream establishment or renewal.Since the primary bandwidth of pQoS stream require be one-period (for example, 1ms) the number of required time slot, and, therefore need conversion to come definite required grouping number that flows for bandwidth value and the simple mapping between the timeslot number on the data link layer of number mbit/are not to be flat-footed because of OFDM modulation and bit load.In order to find out the equivalent maximum number that divides into groups in the data isl cycle and the size (in bit) of each grouping, the phase needs as follows in the poorest situation bandwidth at data link layer upper reaches weekly:
The maximum number of QSpec_ peak-data rates=grouping * QSpec_ largest packet size formula (4)
Wherein,
QSpec_ peak-data rates and to convert time slot to be that NC is the data link layer bandwidth that stream keeps;
QSpec_ largest packet size=TSpec_ largest packet size+Ethernet packet overhead;
TSpec_ peak-data rates on the 1ms is not to be that the TSpec_ peak-data rates of 1ms is calculated from its time unit.
Chronomere's parameter allows the standard of the token bucket TSpec XML of traffic source alive can mate its traffic generative process.Whether chronomere's parameter also provides convenience available regardless of transmission information to extract token bucket TSpec XML from prerecord or conventional contents with flexible way.For example, for the video content through mpeg encoded of no transmission information, peak-data rates can be designated as the interior max. number of bits of frame of video divided by the frame of video duration.In this way, chronomere is the frame of video interval of being determined by video frame rate.If medium are pcm audios for example, then chronomere can equal the inverse of its sampling rate.For the content that is furnished with such as transmission information such as RTP, the resolution that is defaulted as the RTP time stamp of 90KHz is generally used for specifying TSpec XML.Chronomere among the TSpec XML does not match unrare by the determined chronomere of work clock speed of the bottom link that is used to transmit traffic flow, and may need to change the token bucket TSpec XML with the appointment of different time unit.
According to the definition of the peak-data rates in the Token Bucket Scheme, in any interval [t1, t0], { maximum number bits that the traffic source of p} generates is for any t for r, b by having characteristic
1-t
0〉=TU
TSPECCan not surpass p (t
1-t
0).Therefore, at any interval [t
1-t
0] in the maximum data rate or the peak-data rates that record can not surpass
Similarly, according to the definition of the maximum burst size in the Token Bucket Scheme, at any interval [t
1-t
0], { the maximal bit amount that the traffic source of p} generates is for any t for r, b by having characteristic
1-t
0〉=TU
TSPECCan not surpass r (t
1-t
0)+b.At any interval [t
1-t
0] in the maximum data rate or the peak-data rates that record can not surpass
Therefore, make up above two constraints, for by work (oper) clock rate c
OperThe TU that determines
Oper(＞TU
TSPEC) any time unit, with work clock speed c
OperThe peak-data rates that records (is denoted as p
Oper) provide by following formula:
Parametrization QoS flows assurance
PQoS stream guarantees to mean that the network of enabling pQoS is at CF and be no more than under the situation of available network bandwidth and can support to flow.This means new pQoS stream will be not can be by in the access network, unless can both support peak-data rates/nominal packet size (N of flowing at any given time
Pps).Notice that the peak packet rate transient state that enters that any in Ingress node 508 or the NC node 506 can permit flowing surpasses peak-data rates/nominal data size that network can be supported.
In one embodiment, NC node 506 can guarantee to reserve for the prioritization traffic part of total bandwidth, and the remainder of traffic is used for the parametrization traffic.For example, NC node 506 can be the prioritization traffic and reserves 20% of overall network bandwidth, and the residue of bandwidth 80% is reserved to the parametrization traffic.The parametrization traffic comprises asynchronous flow amount traffic and asynchronous data traffic.For example asynchronous flow traffic such as video flow need be to the knowledge of the average data rate of this flow.Therefore, QoS manager 520 can be asked access or be obtained information about the bandwidth of asynchronous flow traffic.If the prioritization bandwidth is unavailable because of heavy network load, this flow will be not can be by access, and source (Ingress node 508) can be attempted sending this traffic as the asynchronous data traffic subsequently.The QSpec of asynchronous flow traffic comprises service type parameters and largest packet size parameter.
For example asynchronous data traffic such as file transfer be to its do not have require or the traffic of measurable bandwidth.The asynchronous data traffic also can comprise traffic as possible, does not for example have the traffic of the VLAN label of its priority of indication.In one embodiment, do the best traffic not by access process described below.Network control and flow management traffic are considered to the prioritization traffic usually.Yet, need therein in some application of short and measurable stand-by period, network control and flow management traffic can be by structuring to use parametrization stream bandwidth (for example, pull-mode (pull-mode) DVR playback or DTCP position constraint wherein are defined as 7ms the two-way time of management exchange).Perhaps, network control and flow management traffic can be taken as the asynchronous traffic of high priority and treat.When coming as the asynchronous traffic of high priority biding one's time, the bandwidth of reserving for the prioritization traffic should be greater than network management and the required bandwidth of traffic management traffic, thereby these administrative messags can in time be sent out.
For pQoS stream bandwidth on demand the time, all nodes can be made as 0x3 with the precedence field in data/control reservation request element frame, as shown in following table 7.The scheduling of each stream in NC node 506 coordination networks 502.Network level is supported 3 kinds of priority: (1) comprises the high priority of network and traffic management; (2) comprise the medium priority of asynchronous flow; And (3) comprise the low priority such as the asynchronous traffic of no priority tags such as the traffic of doing the best.When Scheduling Flow, NC node 506 is dispatched pQoS stream on the first in first out basis.In one embodiment, these pQoS streams were scheduled before any non-pQoS stream is scheduled.
Table 7-has the data/control reservation request element frame format through the revision precedence field
| Field | Length | Purposes |
| Frame _ subtype | 4 bits | Ask 0x6-link acknowledgement 0x7-reservation 0x8-periodicity link packet 0x9-power to control 0xA-power control response 0xB-power control affirmation if frame _ type=control 0x0-type i/III detection report 0x1-reservation 0x2-reservation 0x3-key distribution 0x4-dynamic key is distributed 0x5-type i/III detection report |
| If the control of 0xC-power is upgraded the 0xD-topological structure and is upgraded 0xE-unicast mac address notice 0xF-reservation frame _ type=Ethernet transmission 0x0=Ethernet _ grouping | ||
| Frame _ type | 4 bits | The transmission of 0x2=control 0x3=Ethernet |
| Purpose | 8 bits | The node ID of destination node |
| PHY_ distributes | 8 bits | The every other value of 5: 0 0x2=diversity modes of 7: 6 00= |
| Request _ ID | 8 bits | The sequence number that is associated with request. |
| Parameter | 12 bits | Keep |
| Priority | 4 bits | If if frame _ type=control 0x0 frame _ type=Ethernet transmission 0x0-low priority 0x1-medium priority 0x2-high priority 0x3-parameterized quality of service stream |
| Duration | 16 bits | In the required transmission time of the multiple of crack _ time |
Some pQoS streams can be variable bit-rate (VBR) stream.Because the peak-data rates of VBR stream is used its Mean Speed greater than its Mean Speed and stream in long duration, so the signal portion of parametrization stream bandwidth may not used by this stream.For making the bandwidth maximization, make the not utilized bandwidth of VBR stream can be used for asynchronous traffic.Therefore, actual asynchronous bandwidth has two components usually: the predetermined fraction of (1) asynchronous traffic, and (2) are from the part of parametrization stream bandwidth withdrawal.
Parametrization QoS affairs
In the embodiment shown in Fig. 5, parametrization QoS affairs can or be initiated by NC node 506 or by entering node 504.The affairs that EN initiates generally include 2 pQoS ripples, and usually with clean culture send to NC node 506 submission message initiate.Importantly, note another pQoS section that EN 504 inputs may come automatic network 502 outsides.When receiving submission message, NC node 506 is usually by beginning first ripple to all-network node 504,508,510 broadcast request message to require returning specific pQoS stream information.In second ripple, NC node 506 is broadcasted the information that is received from from the response of network node usually in first ripple.
On the contrary, the pQoS affairs of being initiated by NC node 506 only comprise single pQoS ripple usually.This pQoS ripple with request specific action takes place to all node 504,508,510 broadcast request message by NC node 506 initiates.This ripple is finished when NC node 506 each from be requested network node 504,508,510 is received response.
Each that obtains in the support pQoS stream can transmit in clean culture or broadcasting stream.Notice that the multicast stream in a certain network is that the broadcasting stream of 0x3f is handled as Egress node ID wherein normally.Broadcasting stream is the pQoS stream that the all-network node in network transmits.Connect if Ingress node 508 or Egress node 510 disconnect from network 502, then NC node 506 can be deleted unicast stream.On the contrary, for the network topology structure reason, unless when Ingress node 508 when network disconnects, otherwise do not delete broadcasting stream usually.
Create and undated parameter QoS stream affairs
With reference to figure 7, an example of the establishment/renewal affairs according to the embodiment shown in Fig. 5 will be described now.The purpose of establishment or renewal affairs is to create new pQoS stream as illustrated in fig. 5 or upgrade the pQoS stream attribute between Ingress node 508 and Egress node 510.At first, QoS manager 520 receive Ingress nodes 508 and Egress node 510 both and on the flow path of QoS device service 518 IP and the MAC Address of each QoS equipment.QoS manager 520 compares until finding the path to determine the path of pQoS stream by the MAC Address of arrived at MAC value that QoS device service 518 is reported and Ingress node 508 and Egress node 510 subsequently.
Table 8-is used to submission L2ME header and the payload format creating/upgrade
PQoS stream can be identified by stream ID.In one embodiment, stream ID is a multicast purpose MAC ethernet address, and is grouped on the pQoS stream and is routed.Label-value (TV) field has maximum 24 different pQoS clauses and subclauses.Each pQoS TV clauses and subclauses comprises 8 bit label field, succeeded by 24 bit label value fields.Table 9 illustrates the example of the pQoS list of labels of TV clauses and subclauses.Notice that label " 0 " is indicated current TV, and any follow-up TV clauses and subclauses can be left in the basket.These extraneous peak value _ data _ rate value can be read as the special case of not creating stream in order to the inquiry available bandwidth.Lease _ the time field indicates Ingress node 508 (as shown in Figure 5) after this can stop the traffic that is associated is treated and discharged as pQoS stream the duration of the resource that is associated with this stream.
The label that defines of table 9-TV clauses and subclauses
| The TAG name | Label # | Label value is described |
| The TV end of list (EOL) | ?0 | Ignore |
| Peak value _ data _ rate | ?2 | 0-0xFFFFFE; Peak-data rates (kb/s) 0xFFFFFF=only is used for inquiry and does not create or upgrade pQoS stream; |
| Nominal _ grouping _ size | ??9 | Nominal packet size (byte)-essential; Referring to |
| Lease _ time | ??20 | Lease the time (second)-can choose wantonly (acquiescence=0; Forever) |
| Keep | Every other | Keep for using in the future; The MoCA-1.1 node is ignored |
In one embodiment, the pQoS affairs are initiated when NC node 506 is received submission message from EN 704.Notice that EN 704 can submit message in response to using such as QoS device service 518 (as shown in Figure 5) contour level to send.After the submission message of receiving from EN 704, NC node 706 transmits request message to all nodes 704,708 that are connected to network, begins first ripple (ripple 0) 710 by this.First ripple 710 is used to notify all-network node 704,708 to create about the pQoS stream that is proposed or upgrades affairs, and collects from the tolerance about current flow distribution of these nodes.
When receiving request L2ME message, Ingress node 508 and Egress node 510 (both all as shown in Figure 5) use TSpec XML value to calculate the required time slot of stream and from the required resource of each node, such as system bus bandwidth and memory.Each requested node can respond NC node 706 to finish a L2ME ripple with the response L2ME frame of the gathering cost of indicating existing pQoS stream.Note, if node is received request L2ME frame and do not relate to this stream that then it ignores this message simply.An example that is used for creating/upgrade the response message format of affairs is specified in following table 10.Note, if NC node 706 is not received response L2ME frame from Ingress node 508 or Egress node 510 in the interval in preset time, then NC node 706 was incited somebody to action again broadcast request L2ME message nearly for several times, for example 3 times before message is treated as failure.
Table 10-is used to the response L2ME message format (ripple 0) creating/upgrade
Each is requested node 704,708 by calculate to remove this node wherein be the new stream of Ingress node or upgrade the having now of all existing streams the stream _ TPS values and generate and respond the L2ME frame payload.This value is by calculating each stream use formula (1).Node 704,708 also calculates existing _ PPS value of all the existing streams except that new stream or renewal stream.Existing _ the PPS value is the peak-data rates/nominal packet size sum of each stream.In addition, node 704,708 assesses the cost _ the new cost in crack _ time/second that flows or upgrade stream of TPS value conduct according to formula (1).The value of corresponding peak value _ data _ rate=0 is excluded.If the convection current throughput (bps) inlet or Egress node restriction arranged, then node 704,708 calculate in bps residue node capacity (residue _ node _ capacity), and use rejection _ code field (capacity of node defines) to identify reason.An example of the form of the response L2ME frame of ripple 1 is shown in the following table 15.
Exist node wherein may not fulfil some sights of the request that NC node 706 sent.In these cases, node sends rejection _ code.The example of rejection _ code is shown in the following table 11.If one or more for true in the following statement of the TV collection of receiving about NC node 706 then send invalid _ TV:
1. peak value _ data _ rate does not exist.
2. nominal _ grouping _ size does not exist.
Nominal _ grouping _ sizes values＜64B or＞1518B.
Table 11-can accept the denial code value list
| The denial code name | Value | Describe |
| Rejection _ code _ inlet _ OK | ?1 | Node is Ingress node (establishment and renewal are flowed both) |
| Rejection _ code _ non-inlet _ OK | ?2 | Node is not Ingress node and can't help fluid stopping establishment or renewal |
| Rejection _ code _ stream _ existence | ?3 | There has been the establishment (only being used for creating stream) of stream-node rejection same stream on the node |
| Rejection _ code _ deficiency _ inlet _ BW | ?4 | Ingress node has bandwidth (BW) restriction, has stoped as specifying ground to create stream (create and upgrade stream both) |
| Rejection _ code _ deficiency _ outlet _ BW | ?5 | Keep |
| Rejection _ code _ mistake _ many _ stream | ?6 | Node has had too much existing stream and (only has been used for more |
| New stream) | ||
| Rejection _ code _ invalid _ stream _ ID | ?7 | The stream ID that is asked can not be by Ingress node as service quality stream ID-(only being used for creating stream) |
| Rejection _ code _ invalid _ TV | ?8 | |
| Rejection _ code _ invalid _ node _ ID | ?9 | It is invalid that node ID becomes during network operation |
| Rejection _ code _ lease _ expire | ?10 | Only upgrade |
Before NC node 706 can be initiated second ripple (ripple 1) 712, it need determine to create or whether the result that upgrades affairs is provided non-bandwidth related causes to be rejected because of node to asking stream by (1), (2) because of bandwidth constraints is rejected, or (3) are allowed to the stream resource to promise to undertake as to be asked.
Show the relevant denial code of the non-bandwidth of 12-and return reason
| The denial code name | Non-bandwidth is return _ the reason name |
| Rejection _ code _ stream _ existence | Return _ reason _ stream _ existence |
| Rejection _ code _ mistake _ many _ stream | Return _ reason _ mistake _ many _ flow |
| Not _ generation _ sign indicating number nothing _ effect stream _ ID determines | Return _ reason _ invalid _ stream _ ID |
| Rejection _ code _ invalid _ TV | Return _ reason _ invalid _ tv |
| Rejection _ code _ invalid _ node _ ID | Return _ reason _ invalid _ node _ id |
| Rejection _ code _ lease _ expire | Return _ reason _ lease _ expire |
If any node returns one of rejection _ code of listing in the table 12, then the request of ripple 1 comprises accordingly and returns _ reason.If a node does not return rejection _ code _ inlet _ OK, then the request of ripple 1 comprises returning shown in the following table 14 _ reason _ stream _ not _ find.
1. assemble TPS-from existing _ TPS of all nodes with cost _ TPS value sum can be less than service quality _ TPS_MAX.
2. assemble existing _ PPS and the N of PPS-from all nodes
PpsThe value sum can be less than service quality _ PPS_MAX.
3. residue _ node _ the capability value at inlet or Egress node place of inlet or Egress node capacity-returned can be more than or equal to the stream peak value _ data _ rate of being asked.
Can be if NC node 706 is determined to creating or upgrading affairs and promise to undertake the stream resource of being asked, then its in ripple 1 to participate in node send have 0 length payload request L2ME frame to promise to undertake institute's requested resource.
If any failure in these bandwidth correlation criterions, the but (value of threshold value _ BPS) of the maximum _ peak value _ data _ rate in the payload of NC node 706 computation requests frames then.Maximum _ peak value _ data _ rate be can successful maximum can allow to flow peak value _ data _ rate (bps).NC node 706 also can be specified the most restrictive criterion by returning one of reason below selecting:
1. return _ reason _ deficiency _ inlet _ BW,
2. return _ reason _ deficiency _ outlet _ BW,
3. return _ reason _ deficiency _ gathering _ BW,
4. return _ reason _ deficiency _ gathering _ PPS.
Second ripple, 712 notice nodes create or upgrade the decision of affairs about stream.If create or upgrade affairs and fail in first ripple 710, then NC node 706 can be used for the request L2ME frame of second ripple 712 according to following table 13 transmissions, wherein threshold value _ BPS value only at above 4 return _ reason is defined.Notice that if upgrade the affairs failure, then existing pQoS stream is still adhered to its current TS pec XML parameter.
Table 13-be used to the to fail request L2ME frame payload (ripple 1) of establishment/renewal
Table 14-can accept to return _ the cause value tabulation
| Return _ the reason name | Value | Describe |
| Return _ reason _ stream _ existence | ?3 | Creating affairs specifies the inlet of stream to fail because of node has served as |
| Return _ reason _ deficiency _ inlet _ bw | ?4 | Stream can not be created because of the not enough bandwidth on the Ingress node data path; NC provides the maximum feasible data bandwidth |
| Return _ reason _ deficiency _ outlet _ BW | ?5 | Stream can not be created because of the not enough bandwidth on the Egress node data path; NC provides the maximum feasible data bandwidth |
| Return _ reason _ mistake _ many _ flow | ?6 | Inlet or Egress node can not add stream |
| Return _ reason _ invalid _ stream _ ID | ?7 | The stream ID that asks is kept by node |
| Return _ reason _ invalid _ TV | ?8 | Node can not accept to receive TV |
| Return _ reason _ invalid _ node _ ID | ??9 | It is invalid that node ID becomes during network operation |
| Return _ reason _ lease _ expire | ??10 | Upgrading affairs fails because of deleted stream from network |
| Return _ reason _ stream _ not _ find | ??16 | The failure of renewal affairs |
| Return _ reason _ deficiency _ gathering _ TPS | ??17 | ??MoCA TMDeficiency stream bandwidth on the network |
| Return _ reason _ deficiency _ gathering _ pps | ??18 | ??MoCA TMNot enough packets/second on the network |
When receiving that in second ripple 712 when successfully creating 0 length request of affairs, the Ingress node 504 (shown in Fig. 5) of this stream can be promised to undertake institute's requested resource.Each node 704,708 available response message format responds, and an one example is shown in the following table 15.In the end ripple 814 is in the ripple 2, and NC 806 notice EN 804 are about the result of establishment/renewal affairs.
Table 15-is used to the response L2ME message format (ripple 1) creating/upgrade
Deletion parameterized quality of service stream affairs
The purpose of deletion service quality stream affairs is the specific pQoS stream between one group of inlet 508 of removal and outlet 510 nodes (shown in Fig. 5).With reference to figure 8, an example according to the deletion pQoS affairs 800 of the embodiment shown in Fig. 5 will be described now.Deletion pQoS stream affairs 800 comprise 3 L2ME ripples 810,812,814.Affairs send to NC node 806 at EN 804 submits to message to begin when specifying deleted stream ID.An example of deletion message format is shown in the following table 16.
Table 16-is used to delete the submission L2ME message format of affairs
Which pQoS stream and resource first ripple (ripple 0), the 810 notice all-network nodes 804,808 of deletion affairs 800 about deleting.NC node 806 uses based on the request message format of submitting message to and initiates first ripple 810 to all nodes 804,808.Whether node 804,808 available response message respond, indicate them to have and the resource that deleted stream is associated.
Response L2ME header and payload (ripple 0) that table 17-is used to delete
During second ripple 812 was ripple 1, the stream resource was deleted.NC node 806 uses request message format to initiate second ripple 812 with the cascade response from first ripple 810.Second ripple 812 be in the ripple 1 employed response message format in an example of message format in response shown in the following table 18.Each node 804,808 responds with response frame in second ripple 812, by the stream deletion is indicated in bit 31 set of deleting in the field in the payload portions of frame.
The response L2ME payload (ripple 1) that table 18-is used to delete
At the 3rd ripple 814 is in the ripple 2, and NC node 806 notice EN 804 ask stream deleted.The 3rd ripple 814 uses request message format to respond with the cascade from second ripple 812 by NC node 806 and initiates.Deletion affairs 800 are requested to finish when node 808 provides final response as shown in following table 19 at EN 804 and any other.
Table 19-response L2ME header and payload format (ripple 2)
List parameter service quality stream affairs
Tabulation pQoS stream affairs make the stream tabulation of any network node in can both retrieval network.With reference to figure 9, an example according to the tabulation pQoS affairs 900 of the embodiment shown in Fig. 5 will be described now.These affairs generally include 2 L2ME ripples 910,912, and initiate when NC node 906 sends submission message with the form according to following table 20 at EN 904.Each node 904,906,908 is configured to safeguard its logical table from the inlet stream of 0 serial number.The order of the element in this table only just changes when creating or delete stream.Thus, remote node can which clauses and subclauses makes up complete stream tabulation for first in the logical table by selecting.
The submission L2ME frame format that table 20-is used to tabulate
At first ripple 910 is in the ripple 0, the QoS stream of NC node 906 notice nodes 904,908 which scope of inquiry.NC node 906 uses initiates first ripple 910 based on the request message format of the submission message that is received from EN 804.Request message is sent to the node 908 that response may be provided.The node of being inquired about 908 can respond with the response message format according to following table 21.Returning in the payload portions of tabulation _ response frame _ flow _ ID comprises the tabulation of pQoS stream, start from node stream _ beginning _ index and up to as stream _ maximum _ return specified max-flow to number.Notice that the stream refresh counter increases progressively when the number of stream changes.For the purpose of these affairs, suppose that node keeps the logical table of inlet stream, wherein each element is assigned from 0 index to the maximum numbering of wanting deleted stream.
Table 21-response L2ME frame payload form (ripple 0)
At second ripple 912 is in the ripple 1, the aggregate list that NC node 906 notice EN 904 and any other node 908 interested flow about the pQoS that finds in first ripple 910.NC node 906 uses request message format to initiate second ripple 912 with the cascade response from first ripple 910.Tabulation affairs 900 are finished when NC node 906 sends its last response as shown in following table 22 at all nodes 904,908 interested.
The request L2ME message format (ripple 1) that table 22-is used to tabulate
Query argument service quality stream affairs
The purpose of inquiry pQoS stream affairs is to retrieve the attribute of specific stream ID.With reference to Figure 10, an example according to the inquiry pQoS affairs 1000 of the embodiment shown in Fig. 5 will be described now.Inquiry pQoS affairs 1000 comprise two periods of wave 1010,1012, and send to NC node 1006 at EN 1004 and to submit to message to begin when specifying the stream ID of concrete pQoS stream.
The submission L2ME frame format that table 23-is used to inquire about
Table 23-is if find stream, the response L2ME payload (ripple 0) that is used to inquire about
At second ripple 1012 is in the ripple 1, and Query Result is transferred into EN 1004 and to interested any other node 1008 of these results.NC node 1006 uses request L2ME message format to initiate second ripple with the cascade response from first ripple 1010.Inquiry transaction 1000 is finished when NC node 1006 sends its last response frame as shown in following table 24 at node 1004,1008 interested.
The response L2ME message format (ripple 1) that table 24-is used to inquire about
Maintenance parameters service quality stream affairs
Safeguard the pQoS affairs can be used for periodically assessing whether exist be used for the abundant Internet resources of the pQoS that promises to undertake stream.With reference to Figure 11, the example safeguarding pQoS affairs 1100 according to the embodiment shown in Fig. 5 will be described now.Safeguard that pQoS affairs 1100 can send these affairs at T22 (T6/5) to T6 by NC node 1106 and finish between second, wherein T6 can be 25 or 50 seconds.In addition, NC node 106 can send this affairs at the T22 (T6/5) after the new node of enabling L2MEpQoS adds network 502 second.Care of transaction 1100 comprises two L2ME ripples 1110,1112, and does not need to submit to message, because these affairs are triggered by NC node 1106.
It is ripple 0 and care of transaction 1100 that NC node 1106 is initiated first ripple 1110 by the transmission request message, and an example of request message is shown in the following table 25.Request message requires all nodes 1104,1108 that the information of measuring about its current flow distribution is provided.
The request L2ME frame format (ripple 0) that table 25-is used to safeguard
Each is requested node 1104,108 and sends it at first ripple 1110 and have the response message of payload format as shown in Table 26, existing _ TPS and existing _ PPS values of all existing streams that to specify this node wherein be Ingress node.
The response L2ME payload format (ripple 0) that table 26-is used to safeguard
1. ripple _ state=1
2. catalogue _ length=0x10
3. affairs _ ripple _ numbering=1
If the gathering of all pQoS streams is promised to undertake that excessively then NC node 1106 is made as " 1 " with excessive _ promise field in the request message of second ripple 1012.Each node 1104,1108 can send message to its application layer, notifies the pQoS stream resource of its this network not to be guaranteed.
The request L2ME payload message format (ripple 1) that table 27-is used to safeguard
| Field | Length | Purposes |
| Excessively _ promise to undertake | 32 bits | If pQoS stream is excessively promised to undertake then is made as ' 1 '; Otherwise ' 0 ' |
| Keep | 32 bits | 0x0; Type-iii |
| Keep | 32 bits | 0x0; Type-iii |
Care of transaction 1100 is finished when NC node 1106 sends its response frame as shown in following table 28 at each node 1104,1108.
The response L2ME message format (ripple 1) that table 28-is used to safeguard
Except embodiment described above, disclosed method and apparatus can be implemented by the form that computer implemented process and being used to is put into practice the device of these processes.Method and apparatus disclosed herein also can be by being included in such as floppy disk, read-only memory (ROM), CD-ROM, hard-drive, " ZIP
TM" the form of program code in the tangible medium such as high density rigid driving, DVD-ROM, flash drive or any other computer-readable recording medium implements; wherein when computer program code was loaded in the computer and is carried out by it, this computer became the device that is used to put into practice disclosed method and system.No matter method and apparatus disclosed herein also can be by for example being to be stored in the storage medium, still to be loaded in the computer and/or to be implemented by the form of the computer program code of its execution, wherein when computer program code was loaded in the computer and is carried out by it, this computer became the device that is used to put into practice disclosed method and apparatus.When being implemented on general processor, computer program code segments is configured to create dedicated logic circuit with processor.
Although disclosed method and system is described according to the mode of the embodiment that is used as example, be not defined to this.On the contrary, claims should be broadly construed to comprise other distortion and the embodiment of disclosed method and system, and those skilled in the art can make these distortion and embodiment and not break away from the scope and the boundary of the equivalence techniques scheme of this method and system.
Claims (29)
1. communication means comprises:
To the request of a plurality of node broadcasts that are connected to network to the guaranteed service quality stream the network, described a plurality of nodes comprise at least one Ingress node and at least one Egress node from network coordinator;
Reception is from first response to described request of described at least one Ingress node, and whether described at least one Ingress node of the described first response indication has available resources to transmit described guaranteed service quality stream;
Reception indicates described at least one Egress node whether to have available resources to receive described guaranteed service quality stream from second response to described request of described at least one Egress node; And
If described at least one Ingress node has available resources and has available resources to receive described guaranteed service quality stream to transmit described guaranteed service quality stream and described at least one Egress node, then is described guaranteed service quality flow distribution resource.
2. communication means as claimed in claim 1 is characterized in that, also is included in described network coordinator and receives submission message, and wherein said request is to broadcast from described network coordinator as the result of the described submission message of receiving.
3. communication means as claimed in claim 1 is characterized in that, enters node and separates with described Ingress node and described Egress node.
4. communication means as claimed in claim 2 is characterized in that, the described submission message and second request are the 2nd layer of message.
5. communication means as claimed in claim 1 is characterized in that, and is further comprising the steps of:
Reception is from the cost of the described stream of access of Ingress node, and the described cost of wherein said stream is a part based on the number of existing stream in the described network.
6. communication means as claimed in claim 1 is characterized in that, if described first response of receiving comprises time slot or grouping size information, then described Ingress node can be supported described guaranteed service quality stream.
7. communication means as claimed in claim 1 is characterized in that, can not support described guaranteed service quality stream if described first response of receiving comprises bandwidth information, then described Ingress node.
8. communication means as claimed in claim 1 is characterized in that, if described second response of receiving comprises time slot or grouping size information, then described Egress node can be supported described guaranteed service quality stream.
9. communication means as claimed in claim 1 is characterized in that, can not support described guaranteed service quality stream if described second response of receiving comprises bandwidth information, then described Egress node.
10. communication means as claimed in claim 2 is characterized in that, and is further comprising the steps of:
If described guaranteed service quality stream can not be created then transmit unicast messages to entering node, described unicast messages comprises maximum common bandwidth available on the described network.
11. communication means as claimed in claim 1 is characterized in that, and is further comprising the steps of:
If described network coordinator defines sufficient Internet resources and supports described guaranteed service quality stream, then from described network coordinator to all-network node broadcasts message.
12. communication means as claimed in claim 10 is characterized in that, when receiving described broadcast, described network node is promised to undertake Internet resources to described guaranteed service quality stream.
13. a coding has the machinable medium of program code, wherein when described program code was carried out by processor, described processor was carried out the method that may further comprise the steps:
To the request of a plurality of node broadcasts that are connected to network to the guaranteed service quality stream the network, described a plurality of nodes comprise at least one Ingress node and at least one Egress node from network coordinator;
Reception is from first response to described request of described at least one Ingress node, and whether described at least one Ingress node of the described first response indication has available resources to transmit described guaranteed service quality stream;
Reception indicates described at least one Egress node whether to have available resources to receive described guaranteed service quality stream from second response to described request of described at least one Egress node; And
If described at least one Ingress node has available resources and has available resources to receive described guaranteed service quality stream to transmit described guaranteed service quality stream and described at least one Egress node, then is described guaranteed service quality flow distribution resource.
14. machinable medium as claimed in claim 13 is characterized in that, also is included in described network coordinator and receives submission message, wherein said request is to broadcast from described network coordinator as the result of the described submission message of receiving.
15. machinable medium as claimed in claim 13 is characterized in that, first request transmits by entering node.
16. machinable medium as claimed in claim 13 is characterized in that, if described first response of receiving comprises time slot or grouping size information, then described Ingress node can support parameter service quality stream.
17. machinable medium as claimed in claim 13 is characterized in that, if described second response of receiving comprises bandwidth information, then described Egress node can not support parameter service quality stream.
18. machine readable media as claimed in claim 13 is characterized in that, and is further comprising the steps of:
Determine whether to support in the described network described guaranteed service quality stream at described network coordinator place based on the network bandwidth information that is received from network node.
19. machinable medium as claimed in claim 16 is characterized in that, the described network bandwidth information of receiving comprises the cost that flows described in the described network.
20. machine readable media as claimed in claim 16 is characterized in that, and is further comprising the steps of:
If be described guaranteed service quality flow distribution resource, then from described network coordinator to all-network node broadcasts message.
21. machinable medium as claimed in claim 18 is characterized in that, when receiving described broadcast, described network node is promised to undertake Internet resources to described parameterized quality of service stream.
22. machinable medium as claimed in claim 12 is characterized in that, described first and second requests are the 2nd layer of message.
23. a system comprises:
Be connected to the physical interface of coordination network, described physical interface is configured to transmit and receive message by described coordination network; And
Be coupled to the service quality module of described physical interface, described service quality module is configured to by the one or more guaranteed service quality streams of many articles the 2nd layer message access in described coordination network.
24. system as claimed in claim 21 is characterized in that, described service quality module is coupled to described physical interface by L2ME.
25. system as claimed in claim 21 is characterized in that, described service quality module is configured to receive the message from a plurality of nodes that are connected to described coordination network.
26. system as claimed in claim 21 is characterized in that, described coordination network is a coaxial network.
27. system as claimed in claim 21 is characterized in that, described coordination network is a wireless network.
28. a system comprises:
Be connected to the network of network telegon, described network coordinator is configured to the request of a plurality of node broadcasts to the guaranteed service quality stream in the described network;
Be connected at least one Ingress node of described network, described at least one Ingress node is configured to transmit first response to described network coordinator, and whether described at least one Ingress node of the described first response indication has available resources to transmit described guaranteed service quality stream;
Be connected at least one Egress node of described network, described at least one Egress node is configured to transmit second response to described network coordinator, and whether described at least one Egress node of the described second response indication has available resources to receive described guaranteed service quality stream;
Having available resources and have available resources to receive described service quality stream to transmit described service quality stream and described at least one Egress node if wherein said network coordinator also is configured to described at least one Ingress node, then is described guaranteed service quality flow distribution resource.
29. system as claimed in claim 28 is characterized in that, described network coordinator also is configured to broadcast described request as receiving from the result of the submission message that enters node.
Applications Claiming Priority (15)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US90020607P | 2007-02-06 | 2007-02-06 | |
| US60/900,206 | 2007-02-06 | ||
| US90156307P | 2007-02-14 | 2007-02-14 | |
| US90156407P | 2007-02-14 | 2007-02-14 | |
| US60/901,563 | 2007-02-14 | ||
| US60/901,564 | 2007-02-14 | ||
| US92761307P | 2007-05-04 | 2007-05-04 | |
| US92776607P | 2007-05-04 | 2007-05-04 | |
| US92763607P | 2007-05-04 | 2007-05-04 | |
| US60/927,613 | 2007-05-04 | ||
| US60/927,636 | 2007-05-04 | ||
| US60/927,766 | 2007-05-04 | ||
| US93131407P | 2007-05-21 | 2007-05-21 | |
| US60/931,314 | 2007-05-21 | ||
| PCT/US2008/053222 WO2008098083A2 (en) | 2007-02-06 | 2008-02-06 | Parameterized quality of service architecture in a network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101632268A true CN101632268A (en) | 2010-01-20 |
| CN101632268B CN101632268B (en) | 2014-12-03 |
Family
ID=41576402
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008800078403A Expired - Fee Related CN101632261B (en) | 2007-02-06 | 2008-02-06 | Full mesh rates transaction in a network |
| CN200880007820.6A Expired - Fee Related CN101632268B (en) | 2007-02-06 | 2008-02-06 | Parameterized quality of service architecture in a network |
| CN200880007920A Pending CN101632259A (en) | 2007-02-06 | 2008-02-06 | The 2nd layer management entity information receiving and transmitting framework in the network |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008800078403A Expired - Fee Related CN101632261B (en) | 2007-02-06 | 2008-02-06 | Full mesh rates transaction in a network |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200880007920A Pending CN101632259A (en) | 2007-02-06 | 2008-02-06 | The 2nd layer management entity information receiving and transmitting framework in the network |
Country Status (1)
| Country | Link |
|---|---|
| CN (3) | CN101632261B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103548326A (en) * | 2011-03-30 | 2014-01-29 | 熵敏通讯公司 | Method and apparatus for quality-of-service (QoS) management |
| TWI467961B (en) * | 2010-10-04 | 2015-01-01 | Broadcom Corp | Systems and methods for providing service("srv") node selection |
| US8942250B2 (en) | 2009-10-07 | 2015-01-27 | Broadcom Corporation | Systems and methods for providing service (“SRV”) node selection |
| CN108702339A (en) * | 2016-04-01 | 2018-10-23 | 英特尔公司 | Technology in structure framework for being throttled based on service quality |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7013339B2 (en) * | 1998-07-06 | 2006-03-14 | Sony Corporation | Method to control a network device in a network comprising several devices |
| JP2001053925A (en) * | 1999-08-10 | 2001-02-23 | Matsushita Graphic Communication Systems Inc | Communication controller and serial bus managing device |
| US20030005130A1 (en) * | 2001-06-29 | 2003-01-02 | Cheng Doreen Yining | Audio-video management in UPnP |
| CN1173544C (en) * | 2001-07-09 | 2004-10-27 | 北京艺盛网联科技有限公司 | Coaxial long-distance Ethernet connection method and its equipment |
| SE524696C2 (en) * | 2002-10-30 | 2004-09-21 | Operax Ab | Network resource allocation method for Internet protocol network, involves allocating network resources individually for requested network resource reservation and updating usage history statistics |
| CN100505639C (en) * | 2005-01-12 | 2009-06-24 | 华为技术有限公司 | Method of implementing resource application for multi-service streams |
-
2008
- 2008-02-06 CN CN2008800078403A patent/CN101632261B/en not_active Expired - Fee Related
- 2008-02-06 CN CN200880007820.6A patent/CN101632268B/en not_active Expired - Fee Related
- 2008-02-06 CN CN200880007920A patent/CN101632259A/en active Pending
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8942250B2 (en) | 2009-10-07 | 2015-01-27 | Broadcom Corporation | Systems and methods for providing service (“SRV”) node selection |
| TWI467961B (en) * | 2010-10-04 | 2015-01-01 | Broadcom Corp | Systems and methods for providing service("srv") node selection |
| CN103548326A (en) * | 2011-03-30 | 2014-01-29 | 熵敏通讯公司 | Method and apparatus for quality-of-service (QoS) management |
| CN108702339A (en) * | 2016-04-01 | 2018-10-23 | 英特尔公司 | Technology in structure framework for being throttled based on service quality |
| US11343177B2 (en) | 2016-04-01 | 2022-05-24 | Intel Corporation | Technologies for quality of service based throttling in fabric architectures |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101632261B (en) | 2013-09-18 |
| CN101632259A (en) | 2010-01-20 |
| CN101632268B (en) | 2014-12-03 |
| CN101632261A (en) | 2010-01-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101632266B (en) | Parameterized quality of service in a network | |
| JP5168699B2 (en) | Parameterized quality of service architecture in networks | |
| CN114389946B (en) | Network configuration management method for TSN switch | |
| CN101641917B (en) | Network resource negotiation | |
| CN1674576B (en) | Method for transmitting strategic information inter-network equipment | |
| CN101053208B (en) | Wideband protocol | |
| CN103201984B (en) | For the system and method for the dynamic-configuration of the overlay network based on ISN memory | |
| CN101895413B (en) | Control management of voice-over ip parameters | |
| CN101783758B (en) | Family coaxial network MAC layer data transmission method based on service differentiation | |
| CN110519119A (en) | Bandwidth management method, device and storage medium based on view networking | |
| CN109151058A (en) | A kind of data transmission method and device | |
| CN109768963A (en) | A kind of meeting unlatching method and system based on view networking | |
| CN109474715A (en) | A kind of resource allocation method and device based on view networking | |
| CN101632268B (en) | Parameterized quality of service architecture in a network | |
| WO2009103192A1 (en) | A resource allocation method and a resource release method | |
| CN109151519A (en) | A kind of configuration distribution method and system based on view networking | |
| CN101471872A (en) | Method and device for processing network resource data and resource accommodation control subsystem | |
| CN109121017A (en) | A kind of view intranet network method for evaluating quality and device | |
| CN101237374A (en) | Self-adapted multi-hop time division multiplexing dispatching method | |
| CN101494587A (en) | Method for processing packet network tunnel and communication system as well as relevant equipment | |
| CN110493191A (en) | Windows platform data forwarding method, device, electronic equipment and readable storage medium storing program for executing | |
| CN110139059A (en) | A kind of distribution method and device regarding networked resources | |
| CN109600567A (en) | A kind of processing method and system of video conference | |
| CN109819209A (en) | A kind of system, method and apparatus that monitoring resource is transferred | |
| CN110162357A (en) | Depending on the transmission progress display methods and system of networking files |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20141203 Termination date: 20170206 |