CN101599955B - Method for two-way data transmission of cable TV network - Google Patents
Method for two-way data transmission of cable TV network Download PDFInfo
- Publication number
- CN101599955B CN101599955B CN200810114572A CN200810114572A CN101599955B CN 101599955 B CN101599955 B CN 101599955B CN 200810114572 A CN200810114572 A CN 200810114572A CN 200810114572 A CN200810114572 A CN 200810114572A CN 101599955 B CN101599955 B CN 101599955B
- Authority
- CN
- China
- Prior art keywords
- user side
- frame
- network
- data
- transmission
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention discloses a method for two-way data transmission of a cable TV network, belonging to the field of two-way data transmission protocols of cable TV networks. The method comprises the following steps: a user side registers towards a front end; the user side applies for adding a network after finishing the register; and the user side performs data transmission with the front end after adding the network. In the data transmission process of the user side and the front end, the front end sends a data token to the user side, and the user side sends data to the front end after receiving the data token, therefore, the method is easy to realize without measuring the distance and synchronizing the clocks of the front end and the user side.
Description
Technical field
The present invention relates to the two-way communication area of agreement of cable TV network, particularly a kind of method of cable TV network bidirectional data transfers.
Background technology
Existing cable TV network only can transmit tens cover simulation TV programme; These probably occupy the bandwidth resources of line TV network 1/3; 2/3 bandwidth resources are arranged approximately by idle, therefore how on cable TV network development other professionally become the inevitable problem that cable TV network development faces with value-added service.Present cable TV network generally all is HFC (the Hybrid Fiber Coaxial Network of star-tree topology; The coaxial mixing of one-way optical fiber) network; Because hfc plant is a unidirectional broadcast network; Can only carry out the One-to-All Broadcast business above that, transmitted in both directions therefore how to utilize hfc plant to carry out data becomes present research focus to improve bandwidth availability ratio.
Bilateral network modification scheme of the prior art mainly contains following several kinds: DOCSIS (Data-Over-Cable Service Interface Specification) scheme, HomePNA (Home Phoneline Networking Alliance) scheme, MOCA scheme and EPON (Multimedia over Coax Alliance) scheme etc.Wherein, the most ripe with the DOCSIS scheme again in these schemes, application scale is maximum.But the DOCSIS agreement is based on the tdma system of time slot, and it is synchronous to need periodically to carry out between front end and the user side timing, and has regularly increased the complexity of system design and realization synchronously; In addition, the QoS of DOCSIS agreement (Quality ofService, service quality) mechanism is also very complicated.
Summary of the invention
In order to reduce the complexity of cable TV two-way network MAC (Medium Access Control, medium access control) layer protocol, the invention provides a kind of method of cable TV network bidirectional data transfers.Said technical scheme is following:
A kind of method of cable TV network bidirectional data transfers, said method comprises:
The user side forward end is registered;
After said user side registration is accomplished, add network to said front end application;
After said user side adds network; After receiving the transmission invitation frame that said front end sends; Need send the priority of the formation of data based on said user side and send the request of data frame, carry the length of the data of the needs transmission in the formation that needs the transmission data in the said transmission request of data frame to said front end;
After said front end is received said transmission request of data frame; Return transmission request of data acknowledgement frame to said user side; And said transmission request of data frame is added bandwidth request queue carry out allocated bandwidth; Provide data token frame for then the user side that distributes, said data token frame comprises the byte number that said front end is the transmission data of said user side distribution;
After said user side is received the transmission request of data acknowledgement frame of said front end; Get into and wait for token status; And after receiving the data token frame that said front end sends; Send upstream data cascade frame based on the byte number in the said data token frame to said front end, said upstream data cascade frame comprises the data that said user side sends;
Said user side sends the frame that finishes to said front end after sending the data completion;
Said front end sends downlink data frame to said user side, and said downlink data frame comprises the data of said front end to said user side transmission;
Wherein, If waiting in said user side priority query in the process of data token frame has new business packet to arrive; Then, said user side sends to said front end to the total bytes of the said new business packet that arrives when receiving said data token frame through piggyback mechanism; Said front end carries out allocated bandwidth for it again, through the total bytes of the said user side of piggyback mechanism restriction to said front end transmission.
Said user side forward end is registered specifically and is comprised:
Front end regularly sends registration to all user sides and invites frame;
Unregistered user side sends registration request frame to said front end after receiving that frame is invited in said registration;
After said front end is received said registration request frame; Said unregistered user side is carried out authentication; Behind the authentication success, reply the accreditation verification frame to said unregistered user side, it is the logic number that said unregistered user side distributes that said accreditation verification frame comprises said front end;
After said unregistered user side is received said accreditation verification frame, check Media Access Control Address in the said accreditation verification frame whether with oneself Media Access Control Address coupling, if, then preserve the logic number that said front end distributes, accomplish registration
Saidly, said front end also comprises after sending registration request frame:
Said unregistered user side starts queued for log-on revertive clocking device;
When the value of said queued for log-on revertive clocking device during greater than preset timeout value; Said unregistered user side is no longer waited for the accreditation verification frame of said front end; And starting the processing that conflicts of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks.
Saidly add network to said front end application and specifically comprise:
Front end regularly sends transmission to all user sides and invites frame;
After the user side that does not add network receives that frame is invited in said transmission, send to said front end and to add the network requests frame;
After said front end is received said adding network requests frame, send adding network validation frame to the said user side that does not add network.
The said transmission to said front end also comprises after adding the network requests frame:
The said network revertive clocking devices to be added such as user side startup that do not add network;
When the value of network revertive clocking device to be added such as said during greater than preset timeout value; The said user side that does not add network is no longer waited for the adding network validation frame of said front end; And starting the processing that conflicts of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks.
Said user side carries out transfer of data with said front end and specifically comprises after adding network:
After said user side adds network; After receiving the transmission invitation frame that said front end sends; Need send the priority of the formation of data based on said user side and send the request of data frame, carry the data of the formation that needs the transmission data in the said transmission request of data frame to said front end;
After said front end is received said transmission request of data frame; Return transmission request of data acknowledgement frame to said user side; And said transmission request of data frame is added bandwidth request queue carry out allocated bandwidth; Provide data token frame for then the user side that distributes, said data token frame comprises the byte number that said front end is the transmission data of said user side distribution;
After said user side is received the transmission request of data acknowledgement frame of said front end; Get into and wait for token status; And after receiving the data token that said front end sends; Send upstream data cascade frame based on the byte number in the said data token to said front end, the defeated upstream data cascade frame of institute comprises the data of said user side transmission;
Said user side sends the frame that finishes to said front end after sending the data completion;
Said front end sends downlink data frame to said user side, and said downlink data frame comprises the data of said front end to said user side transmission.
Saidly, said front end also comprises after sending the request of data frame:
Request of data to be sent such as said user side startup is confirmed timer;
The value of confirming timer when request of data to be sent such as said is during greater than preset timeout value; Said user side is no longer waited for the transmission request of data acknowledgement frame of said front end; And starting processings that conflict of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks of band QoS differentiation.
Said user side also comprises after adding network:
After the user side that adds network need not transmit data, request exitted network, and detailed process is following:
Said user side sends the claim frame that exits network to said front end after receiving that frame is invited in the transmission of said front end transmission;
Said front end sends the acknowledgement frame that exits network to said user side after receiving the claim frame that exits network of said user side transmission;
After said user side is received the acknowledgement frame that exits network that said front end sends, the wait recoil state that exits network is changed into login state, exit network.
Saidly, said front end also comprises after sending the claim frame that exits network:
Said user side starts waits for the revertive clocking device that exits network;
When said wait exits network the value of revertive clocking device during greater than preset timeout value; Said user side is no longer waited for the acknowledgement frame that exits network of said front end; And starting the processing that conflicts of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks.
The beneficial effect of technical scheme provided by the invention is:
The embodiment of the invention of the present invention is sent data token through front end to user side in the transmission data procedures of user side and front end, after user side is received data token; Forward end is sent data again; Non-distance measuring does not need the clock synchronization between front end and the user side, realizes simple.
Description of drawings
Fig. 1 is the first half flow chart of the method for the cable TV network bidirectional data transfers that provides of the embodiment of the invention;
Fig. 2 is the latter half flow chart of the method for the cable TV network bidirectional data transfers that provides of the embodiment of the invention;
Fig. 3 is the user side state transition diagram that the embodiment of the invention provides;
Fig. 4 is the front end state transition diagram that the embodiment of the invention provides.
Embodiment
For making the object of the invention, technical scheme and advantage clearer, embodiment of the present invention is done to describe in detail further below in conjunction with accompanying drawing.
The embodiment of the invention is in the transmission data procedures of user side and front end; Send data token through front end to user side, after user side was received data token, forward end was sent data again; Thereby needing between the user side and front end in the prior art to have avoided range finding carry out clock synchronization, realized simple.
Embodiment
The embodiment of the invention provides a kind of method of cable TV network bidirectional data transfers, and this method comprises:
The user side forward end is registered;
After the user side registration was accomplished, the forward end application added network;
User side carries out transfer of data with front end after adding network.
Referring to Fig. 1 and Fig. 2, the embodiment of the invention provides a kind of method of cable TV network bidirectional data transfers, specifically comprises:
Step 101: front end regularly sends " frame is invited in registration " to all user sides.
Wherein, It is to invite timer to realize through the transmission registration of front end that front end regularly sends " frame is invited in registration " to user side; When sending value that registration invites timer greater than preset timeout value; Front end generates " frame is invited in registration ", and sends it to all user sides, will send registration after transmission finishes again and invite the value of timer to reset to the initial value of beginning.
Step 102: after user side is received " frame is invited in registration " of front end transmission, be in the user side of unregistered state, promptly unregistered user side forward end is sent " registration request frame ", and unregistered state is changed into the queued for log-on recoil state.
Wherein, it is that value according to the conflict resolution algorithm counter of user side decides that the user side forward end is sent " registration request frame ", and when the value of conflict resolution algorithm counter was 0, forward end was sent " registration request frame "; Otherwise forward end is not sent " registration request frame ", and the value of conflict resolution algorithm counter is subtracted 1.
In addition; After sending " registration request frame ", be in the queued for log-on recoil state for fear of user side for a long time; After user side sends " registration request frame ", start the queued for log-on revertive clocking device of user side, when the value of queued for log-on revertive clocking device during greater than preset timeout value; Thinking has data collision, adopts the processing that conflicts of the binary system index backward algorithm block.
Step 103: after front end is received " registration request frame " of user side transmission; Under the situation that is in the queued for log-on solicited status, the user side that sends " registration request frame " is carried out authentication; Be this user side assignment logic number behind the authentication success, and send it to user side through " accreditation verification frame ".
Further; Owing to network or other reason; Front end possibly can not receive " registration request frame " or " registration request frame " that just can receive user side for a long time that user side sends; For fear of the wait as long for of front end, can be set the maximum time that front end is waited for " registration request frame " of user side through the queued for log-on revertive clocking device of front end in this case, specific as follows:
Sent " frame is invited in registration " at front end after, start queued for log-on revertive clocking device;
When the value of queued for log-on revertive clocking device during greater than preset timeout value, front end will no longer be waited for " registration request frame " of user side.
Step 104: after user side is received " accreditation verification frame "; Under the situation that is in the queued for log-on recoil state, promptly unregistered user side checks that whether the MAC Address of " accreditation verification frame " the inside matees with own MAC Address, if; Then receive and be somebody's turn to do " accreditation verification frame "; Preserve the logic number that front end distributes, and the queued for log-on recoil state is changed into login state, accomplish registration.
User side can carry out the transmission of various transmission control frames with front end under registered state, for example registered but user side that do not add network can forward end sends " adding the network requests frame ", and request adds network; Add network and needed the user side of transmitting user data can forward end send " sending the request of data frame ", forward end transmission data; The user side that has added network and wanted to exit network can forward end send " claim frame exits network ", and request exits network.
Step 105: front end regularly sends " frame is invited in transmission " to all user sides.
Wherein, It is to invite timer to realize through the transmission transmission of front end that front end regularly sends " frame is invited in transmission " to user side; When sending value that transmission invites timer greater than preset timeout value; Front end generates " frame is invited in transmission ", and sends it to all user sides, will send transmission after transmission finishes again and invite the value of timer to reset to the initial value of beginning.
Step 106: after user side was received " frame is invited in transmission " of front end transmission, forward end was sent " adding the network requests frame " under registered situation, and with network recoil states to be added such as login state change into.
For fear of network recoil states to be added such as user side are in after sending " adding the network requests frame " for a long time; Further; Send " adding the network requests frame " at user side after, network revertive clocking devices to be added such as startups, when etc. the value of network timer to be added during greater than the timeout value preset; Thinking has data collision, then adopts the processing that conflicts of the binary system index backward algorithm block.
Step 107: after front end is received " adding the network requests frame " of user side transmission, under the situation of waiting for the transmission requests state, send " adding the network validation frame " to user side, and will wait for network recoil states to be added such as the transmission requests state changes into.
Further; Owing to network or other reason; Front end possibly can not receive " adding the network requests frame " or " the adding the network requests frame " that just can receive user side for a long time that user side sends; In this case, can be set the maximum time that front end is waited for user side " adding the network requests frame " through the wait transmission requests timer of front end, specific as follows:
Sent " frame is invited in transmission " at front end after, start and wait for the transmission requests timer;
When the value of waiting for the transmission requests timer during greater than preset timeout value, front end will no longer be waited for " adding the network requests frame " of user side.
Step 108: after user side is received " adding the network validation frame " of front end transmission; Under the situation that waits network recoil state to be added; To wait network recoil state to be added to change into the adding network state, user side could begin the transmission of application data in the adding network state.
Further, if user side overtime " add network validation frame " of not receiving front end, then thinking having conflict to take place, and then starts the processing that conflicts of user side conflict treatment mechanism.
Step 109: after user side adds network; The priority forward end of sending the formation of data according to the user side needs is sent " sending the request of data frame "; Carry the data of the formation that needs to send data in should " send request of data frame ", and will add network state and request of data affirmation state to be sent such as change into.
Wherein, after user side added network, the detailed process that the priority forward end of sending the formation of data according to the user side needs is sent " sending the request of data frame " was following:
User side end MAC layer is set up different data queues to different business types, corresponds respectively to the business data packet of the various priority that application layer produces;
After user side is received front end " frame is invited in transmission "; Check whether each data queue need send new data, if then generate " transmission request of data " frame; Encapsulate the length of new data, utilize the chance of " transmission is invited " to send to front end then; Further; If the same time, a user side had a plurality of data queues need send new data; Promptly need send a plurality of " sending the request of data frame "; Then according to priority order from high to low, send priority the highest " sending the request of data frame " earlier, receive " sending the request of data frame " of time priority of redispatching after " frame is invited in transmission " that front end sends by the time next time.
In addition; Confirm state for fear of request of data to be sent such as user side are in for a long time after sending " sending the request of data frame "; Send " sending the request of data frame " at user side after, request of data to be sent such as start and confirm timer, when etc. the value of request of data timer to be sent during greater than preset timeout value; Thinking has data collision, the binary system index backward algorithm that blocks that then adopts band QoS the to distinguish processing that conflicts.
Step 110: after front end is received " sending the request of data frame " of user side; Be under the situation of waiting for the transmission requests state; Send " sending the request of data acknowledgement frame " to user side, and the request of data formation that " the sending the request of data frame " that will receive adds corresponding priority is so that carry out allocated bandwidth to it.
Wherein, the front end bandwidth distribution mechanism is a kind of based on ratio P (0＜P＜1), and the allocated bandwidth that can according to priority transmit mechanism, and promptly can to account for the ratio except the remaining bandwidth of the professional shared bandwidth that is higher than its priority be P to certain priority service.For example, suppose that business has 0,1; 2 and 3 four priority, and 0 priority is the highest, then under normal circumstances; The ratio that limit priority 0 accounts for total bandwidth is P; Priority is that the ratio that 1 business accounts for remaining bandwidth except priority 0 is P, and priority is that the ratio that 2 business accounts for remaining bandwidth except priority 0,1 is P, and priority is that the ratio that 3 business accounts for last remaining bandwidth again is P; Further, be 0 business if there is not priority, then priority is that the ratio that 1 business can account for total bandwidth is P, the rest may be inferred.Four priority maybe be shared the bandwidth ratio respectively like following table 1 with shown in the table 2:
Table 1
| QoS | Account for the bandwidth ratio | QoS | Account for the bandwidth ratio |
| 0 | P | 0 | 0 |
| 1 | (1-P)P | 1 | P |
| 2 | (1-P-(1-P)P)P | 2 | (1-P)P |
| 3 | 1-P-(1-P)P-(1-P-(1-P)P)P | 3 | (1-P-(1-P)P)P |
Table 2
| QoS | Account for the bandwidth ratio | QoS | Account for the bandwidth ratio |
| 0 | 0 | 0 | 0 |
| 1 | 0 | 1 | 0 |
| 2 | P | 2 | 0 |
| 3 | 1-P | 3 | 1 |
Further; Owing to network or other reason; Front end possibly can not receive " sending the request of data frame " or " the sending the request of data frame " that just can receive user side for a long time that user side sends; In this case; Front end can be set through the wait transmission requests timer of front end wait for the maximum time of user side " sending the request of data frame ", front end is set in detailed process and the step 107 wait for that the process of maximum time of " adding network requests frame " of user side is similar, repeat no more here.
Step 111: user side will wait request of data affirmation state to be sent to change into and wait for the data token state after receiving " sending the request of data acknowledgement frame " of front end transmission.
Receive the long-time situation about waiting in " sending the request of data acknowledgement frame " back of front end less than data token for fear of the family; Further; Receive " sending the request of data acknowledgement frame " of front end at user side after; Start to wait for the data token timer,, then the data queue of request last time forward end is again sent " sending the request of data frame " when the value of waiting for the data token timer during greater than preset timeout value.
Step 112: front end is for after the user side that sends " sending the request of data frame " distributes bandwidth, to the user side granting " data token frame " that distributes bandwidth, should " data token frame " the inside have comprised user side and can send the byte number of data.
Step 113: after user side is received " data token frame " of front end transmission; Under the situation of waiting for the data token state; Byte number forward end according to " data token frame " the inside front end distributes is sent " sending upstream data cascade frame ", is somebody's turn to do in " sending upstream data cascade frame " to comprise the data that the user side forward end is sent.
Send in the data procedures at user side; When the business of different priorities clashes; The binary system index backward algorithm that blocks that adopts QoS to distinguish processings that conflict, promptly the business of different priorities selects different backoff values to carry out priority differentiation just when clashing.
In addition; If in the process of wait front end " data token frame ", have new business packet to arrive in user side priority query; Can send to front end to the total bytes of the new business packet that arrives through piggyback mechanism when then receiving " data token frame " at user side; Front end carries out allocated bandwidth for it again, has so just avoided conflict.But take too many bandwidth for fear of a user side, can be through the total bytes of the machine-processed limited subscriber end forward end transmission of piggyback.
In order to improve message transmission rate, further, can in a transmission opportunity, allow the transmission of a plurality of MAC Frames, promptly user side can be placed on a plurality of MAC Frames in the cascade frame and send.In this case,, front end need each mac frame in the cascade frame be extracted respectively after receiving.
Further, when front end is the not enough integer number of data frame of the byte number that distributes of user side, then send according to the minimum frame number less than allotment, remaining byte number sends when keeping front end reallocation next time together.
Step 114: after front end is received " the upstream data cascade frame " of user side transmission, be under the situation of waiting for the upstream data state, resolving and " upstream data cascade frame " to carry out data processing.
Further; " upstream data cascade frame " for fear of front end wait as long for user side; Can set the maximum time that front end is waited for " the upstream data cascade frame " of user side through waiting for user side upstream data timer; Send " data token frame " back at front end and started wait user side upstream data timer; When waiting for user side upstream data timer greater than preset timeout value, front end will no longer be waited for " the upstream data cascade frame " of user side, then carry out next step operation.
Step 115: user side sends after data finish, and forward end is sent " transmission finish frame ", and the notice front end can be provided next data token.
Step 116: after " transmission finish frame " that front end receives that user side sends, under the situation of waiting for the upstream data state, finish this transmitting uplink data, change idle condition over to, carry out next step operation.
Step 117: front end sends " downlink data frame " to user side, should " downlink data frame " comprise the data of front end to the user side transmission.
Step 118: after user side is received " downlink data frame " that front end sends, resolve should " downlink data frame ", carry out data processing.
In the present embodiment, step 109 to step 116 is the process of user side forward end transmission data, and step 117 to step 118 is the process of front end to user side end transmission data, does not have sequencing in the practical application.
Further, when the user side that adds network need not transmit data, can ask to exit network, detailed process is following:
User side add receive " frame is invited in transmission " that front end sends under the network state after, forward end is sent " claim frame exits network ", and will add network state and change into the wait recoil state that exits network;
After front end is received " claim frame exits network " of user side transmission, under the situation of waiting for the transmission requests state, send " acknowledgement frame exits network " to user side; Further; " claim frame exits network " for fear of front end wait as long for user side; With wait transmission requests timer be set the maximum time that front end is waited for " claim frame exits network " of user side through front end; Front end is set in detailed process and the step 107 waits for that the process of maximum time of " adding the network requests frame " of user side is similar, repeat no more here;
After user side is received " acknowledgement frame exits network " that front end sends, the wait recoil state that exits network is changed into login state, exit network." acknowledgement frame exits network " for fear of user side wait as long for front end; The revertive clocking device that can exit network through the wait of user side is provided with the maximum time that user side is waited for " acknowledgement frame exits network " of front end; After user side sends " claim frame exits network "; Start and wait for the revertive clocking device that exits network; When wait exits network revertive clocking device timer during greater than preset timeout value, thinking has data collision, then adopts the binary system index backward algorithm that the blocks processing that conflicts.
Referring to Fig. 3 and Fig. 4, be respectively the state transition diagram of user side and front end in the said method of present embodiment.
In addition; In the present embodiment in the timer of above-mentioned front end; If current have no timer expired; Then get into to provide the state of " data token ", the principle according to the percentage P of allocated bandwidth in the step 110 from " request of data " formation is taken out " the request of data frame " of corresponding formation, distributes byte number for it then and to respective user end granting " data token ".
Further, the timeout value of various timer can be set according to practical situations in the present embodiment.
The embodiment of the invention embodiment of the invention is in the transmission data procedures of user side and front end; Send data token through front end to user side, after user side was received data token, forward end was sent data again; Non-distance measuring; Do not need the clock synchronization between front end and the user side, realize simply, and can under the situation of band number of users few (64～128 user), obtain systematic function preferably.
The above is merely preferred embodiment of the present invention, and is in order to restriction the present invention, not all within spirit of the present invention and principle, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (8)
1. the method for a cable TV network bidirectional data transfers is characterized in that, said method comprises:
The user side forward end is registered;
After said user side registration is accomplished, add network to said front end application;
After said user side adds network; After receiving the transmission invitation frame that said front end sends; Need send the priority of the formation of data based on said user side and send the request of data frame, carry the length of the data of the needs transmission in the formation that needs the transmission data in the said transmission request of data frame to said front end;
After said front end is received said transmission request of data frame; Return transmission request of data acknowledgement frame to said user side; And said transmission request of data frame is added bandwidth request queue carry out allocated bandwidth; Provide data token frame for then the user side that distributes, said data token frame comprises the byte number that said front end is the transmission data of said user side distribution;
After said user side is received the transmission request of data acknowledgement frame of said front end; Get into and wait for token status; And after receiving the data token frame that said front end sends; Send upstream data cascade frame based on the byte number in the said data token frame to said front end, said upstream data cascade frame comprises the data that said user side sends;
Said user side sends the frame that finishes to said front end after sending the data completion;
Said front end sends downlink data frame to said user side, and said downlink data frame comprises the data of said front end to said user side transmission;
Wherein, If waiting in said user side priority query in the process of data token frame has new business packet to arrive; Then, said user side sends to said front end to the total bytes of the said new business packet that arrives when receiving said data token frame through piggyback mechanism; Said front end carries out allocated bandwidth for it again, through the total bytes of the said user side of piggyback mechanism restriction to said front end transmission.
2. the method for cable TV network bidirectional data transfers as claimed in claim 1 is characterized in that, said user side forward end is registered specifically and comprised:
Front end regularly sends registration to all user sides and invites frame;
Unregistered user side sends registration request frame to said front end after receiving that frame is invited in said registration;
After said front end is received said registration request frame; Said unregistered user side is carried out authentication; Behind the authentication success, reply the accreditation verification frame to said unregistered user side, it is the logic number that said unregistered user side distributes that said accreditation verification frame comprises said front end;
After said unregistered user side is received said accreditation verification frame, check Media Access Control Address in the said accreditation verification frame whether with oneself Media Access Control Address coupling, if, then preserve the logic number that said front end distributes, accomplish registration.
3. the method for cable TV network bidirectional data transfers as claimed in claim 2 is characterized in that, saidly after said front end sends registration request frame, also comprises:
Said unregistered user side starts queued for log-on revertive clocking device;
When the value of said queued for log-on revertive clocking device during greater than preset timeout value; Said unregistered user side is no longer waited for the accreditation verification frame of said front end; And starting the processing that conflicts of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks.
4. the method for cable TV network bidirectional data transfers as claimed in claim 1 is characterized in that, saidly adds network to said front end application and specifically comprises:
Front end regularly sends transmission to all user sides and invites frame;
After the user side that does not add network receives that frame is invited in said transmission, send to said front end and to add the network requests frame;
After said front end is received said adding network requests frame, send adding network validation frame to the said user side that does not add network.
5. the method for cable TV network bidirectional data transfers as claimed in claim 4 is characterized in that, the said transmission to said front end also comprises after adding the network requests frame:
The said network revertive clocking devices to be added such as user side startup that do not add network;
When the value of network revertive clocking device to be added such as said during greater than preset timeout value; The said user side that does not add network is no longer waited for the adding network validation frame of said front end; And starting the processing that conflicts of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks.
6. the method for cable TV network bidirectional data transfers as claimed in claim 1 is characterized in that, saidly after said front end sends the request of data frame, also comprises:
Request of data to be sent such as said user side startup is confirmed timer;
The value of confirming timer when request of data to be sent such as said is during greater than preset timeout value; Said user side is no longer waited for the transmission request of data acknowledgement frame of said front end; And starting processings that conflict of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks of band QoS differentiation.
7. the method for cable TV network bidirectional data transfers as claimed in claim 1 is characterized in that, said user side also comprises after adding network:
After the user side that adds network need not transmit data, request exitted network, and detailed process is following:
Said user side sends the claim frame that exits network to said front end after receiving that frame is invited in the transmission of said front end transmission;
Said front end sends the acknowledgement frame that exits network to said user side after receiving the claim frame that exits network of said user side transmission;
After said user side is received the acknowledgement frame that exits network that said front end sends, the wait recoil state that exits network is changed into login state, exit network.
8. the method for cable TV network bidirectional data transfers as claimed in claim 7 is characterized in that, saidly after said front end sends the claim frame that exits network, also comprises:
Said user side starts waits for the revertive clocking device that exits network;
When said wait exits network the value of revertive clocking device during greater than preset timeout value; Said user side is no longer waited for the acknowledgement frame that exits network of said front end; And starting the processing that conflicts of user side conflict treatment mechanism, said conflict treatment mechanism is the binary system index backward algorithm that blocks.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810114572A CN101599955B (en) | 2008-06-04 | 2008-06-04 | Method for two-way data transmission of cable TV network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810114572A CN101599955B (en) | 2008-06-04 | 2008-06-04 | Method for two-way data transmission of cable TV network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101599955A CN101599955A (en) | 2009-12-09 |
| CN101599955B true CN101599955B (en) | 2012-10-10 |
Family
ID=41421202
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810114572A Expired - Fee Related CN101599955B (en) | 2008-06-04 | 2008-06-04 | Method for two-way data transmission of cable TV network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101599955B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102201889B (en) * | 2010-03-23 | 2015-07-22 | 中兴通讯股份有限公司 | Processing method of notification configuration frame, transcoder and rate adaptation unit |
-
2008
- 2008-06-04 CN CN200810114572A patent/CN101599955B/en not_active Expired - Fee Related
Non-Patent Citations (1)
| Title |
|---|
| 关平.双向HFC网络中令牌总线接入方式研究.《中国优秀硕士学位论文》.2005, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101599955A (en) | 2009-12-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101236294B1 (en) | Collision avoidance media access method for shared networks | |
| US6108314A (en) | Method, subscriber device, wireless router, and communication system efficiently utilizing the receive/transmit switching time | |
| US5615212A (en) | Method, device and router for providing a contention-based reservation mechanism within a mini-slotted dynamic entry polling slot supporting multiple service classes | |
| US9641456B2 (en) | Apparatus and methods for reduction of transmission delay in a communication network | |
| US8018963B2 (en) | Systems for flexible wireless channel association | |
| CN102474883B (en) | In half random back method of wireless local network resource reservation | |
| JP5182964B2 (en) | Device for media access in contention network | |
| EP1357705A1 (en) | Adaptive synchronous media access protocol for shared media networks | |
| Bisdikian et al. | MLAP: A MAC level access protocol for the HFC 802.14 network | |
| CN100534068C (en) | Non-confliction on-demand multi-address access method | |
| US20090161687A1 (en) | Medium Access Control Method for Data Transmission Through CATV Access Network | |
| US8422450B2 (en) | Relaxed deterministic back-off method for medium access control | |
| EP1021001A3 (en) | Onboard control of demand assigned multiple access protocol for satellite ATM networks | |
| CN105721414B (en) | Multicast communication method | |
| GB2356325A (en) | Optimized random access scheme for a shared resource contention system | |
| WO2015103834A1 (en) | Method, device and system for realizing vlc dynamic access | |
| CN115413043A (en) | Data link self-organizing access control method based on control sequence | |
| CN100452745C (en) | Multi-address access method with the confliction decomposition | |
| CN101599955B (en) | Method for two-way data transmission of cable TV network | |
| JP2010252372A (en) | Device for media access in contention-based networks | |
| CN101632261A (en) | Full mesh rates transaction in the network | |
| JP2008211538A (en) | Schedular terminal | |
| WO2008001437A1 (en) | Media access control method | |
| US20060136591A1 (en) | Scheduler for a base station of a communications network and method of operating a scheduler | |
| CN115767736B (en) | Continuous time frame reservation method and system based on hybrid TDMA wireless ad hoc network |
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: 20121010 Termination date: 20180604 |