CN100450009C - Method for distributing universal label of network node - Google Patents
Method for distributing universal label of network node Download PDFInfo
- Publication number
- CN100450009C CN100450009C CNB031269753A CN03126975A CN100450009C CN 100450009 C CN100450009 C CN 100450009C CN B031269753 A CNB031269753 A CN B031269753A CN 03126975 A CN03126975 A CN 03126975A CN 100450009 C CN100450009 C CN 100450009C
- Authority
- CN
- China
- Prior art keywords
- label
- label distribution
- distribution server
- equipment
- server
- 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
- 238000000034 method Methods 0.000 title claims description 12
- 230000000737 periodic effect Effects 0.000 claims description 4
- 238000005538 encapsulation Methods 0.000 claims description 3
- 238000007689 inspection Methods 0.000 claims description 2
- 230000003068 static effect Effects 0.000 claims description 2
- 238000012360 testing method Methods 0.000 claims description 2
- 238000012546 transfer Methods 0.000 claims description 2
- 238000004891 communication Methods 0.000 abstract description 7
- 230000005540 biological transmission Effects 0.000 description 6
- 238000011084 recovery Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
Landscapes
- Computer And Data Communications (AREA)
Abstract
The present invention relates to a protocol for allocating universal labels among network nodes, which belongs to the field of communication. The universal labels are arbitrary identification such as MPLS labels, IP addresses, any ID, etc.; a. a client/server mode is adopted; b. an operation mode of dynamically automatically allocating labels of a label allocating algorithm is adopted as a request-response mode; a label allocating requirement is unique in the whole network or a sub network; one network node can be allocated with a plurality of labels; one network can also have a plurality of label spaces.
Description
Technical field:
The present invention relates between the network node of the communications field, carry out the protocol method that general label is distributed.
Background technology:
In data communication field, usually need be for each node allocation identification in the network, so that the location of communication object.For example each node has an IP address at least. perhaps need to distribute a unique sign for each communication port in the node, when communication, need only like this and specify the purpose sign, datagram just can arrive correct destination interface, from the efficient of communication with the utilization of resources situation when realizing, as long as the sign of port does not need 4 bytes to identify, may be 1～2 byte.Because a network node can have a plurality of ports, so require agreement to distribute any a plurality of label for each node neatly.As a kind of general label distributorship agreement, should have a plurality of realization examples in one network simultaneously, the Label space of these example allocation can be different.
The object of the present invention is to provide a kind of network node universal tag distribution method.
Summary of the invention:
The embodiment of the invention provides a kind of network node universal tag distribution method, comprising:
A, employing Client:
Allow the label distribution server be bound on certain equipment, after specifying a label distribution server, this label distribution server periodically customer equipment of all on the whole network is given notice, inform the new device address of the label distribution server on this network, each equipment label distribution if desired then sends the label request to this label distribution server;
For the normal down machine of label distribution server, then reassign new equipment as the label distribution server by webmaster, the information transfer of distributing labels of being preserved on the old label distribution server to new label distribution server, give notice with periodic again all customer equipments on the whole network of stylish label distribution server, inform the new device address of the label distribution server on this network;
For label distribution server exception down machine, promptly because mistake or unusual appears suddenly in equipment, the label of having distributed to equipment is unaffected, still can use, only the label distribution server can not be the devices allocation label of applying label at this moment again, and adopt the mode of static manual configuration label that the equipment that needs label is carried out label distribution this moment;
The dynamic auto distributing labels mode of operation of b, label distribution algorithm is a request-response mode:
When the client needs distributing labels, then send label request applying label and distribute to the label distribution server, start the one-period timer simultaneously; The label distribution server uses the customer equipment label distribution situation in the label collision testing mechanism inspection network after obtaining its request, reply to this equipment for the client who asks distributes the label of an available non-conflict and issues then; If the client does not receive replying of label distribution server ticket distribution in the time cycle of described cycle timer, then restart described cycle timer and resend the label distribution request, reply up to the label distribution that obtains described label distribution server; If continuous 3 overtime also not the receiving of described cycle timer are replied, then start another timer, and at described timer expiry and client when not receiving that yet the label distribution of label distribution server is replied, whether client's requester network topology is searched described label distribution server and is existed; If exist, then resend the label distribution request, and restart described cycle timer, reply up to the label distribution that obtains described label distribution server; The encapsulation that in described label distribution request, adds sequence number; If the client sends and do not receive after the described label distribution request and reply, just use identical sequence number to send described label distribution request always and can change sequence number up to receiving to reply; If twice of described label distribution server or repeatedly receive the label distribution request that the client sends, then check the sequence number in the described label distribution request earlier, and sequence number is corresponding and distribute to the label of this equipment therewith, if sequence number is identical, then the label of distributing to the client according to described sequence number is resend to described client, otherwise distribute new label and send to described client for described client; To consider also that in addition label reclaims, when the distributed labels on equipment is determined not re-use, reclaim this label and equipment that it is redistributed to other uses.Alternatively, described device address is an IP address of equipment.
Execution mode:
1, label distribution process:
The realization of dynamic auto distributing labels is behind startup of server, by server all customer equipment send server address notification on the whole network, informs the IP address of this server of customer equipment.When each customer equipment needs label distribution, just send the label distribution request to server, start one-period timer (time cycle is 15 seconds) simultaneously, if in 15 second time, do not receive replying of server ticket distribution, then resend the label distribution request, also do not receive for 3 times and to reply if send continuously, then start a timer of 1 minute, wait for that the inquiry topology is searched the Device IP that whether has server after 1 minute, if exist, then restart cycles transmission request package 3 times, so repeat to reply up to the label distribution that obtains server.In order to prevent that server from having issued label distribution and having replied, but equipment is not also received and is replied and send request to server, and occur server be same equipment send twice or repeatedly label distribution reply, and distributed twice or the repeatedly situation generation of label, when device-to-server sends the label request, in request package, add the encapsulation of sequence number.If equipment transmission request is received do not reply, just use identical sequence number to send request always and just can change sequence number (mode of a random number adding system clock value of realization employing of sequence number) up to receiving to reply.If twice of server or repeatedly receive the label request package that sends from same M equipment, then check the request sequence number in the bag earlier, and sequence number is corresponding and distribute to the label of this equipment therewith, if sequence number is identical, then the label of distributing to this equipment according to this sequence number is inserted the equipment that sends in the bag again, otherwise send to equipment for it distributes new label value.
2, the process of given server:
The server of label distribution can be specified, and has three kinds of situations when issuing the given server order:
1), the given server for the first time of the equipment on the network, promptly also not have appearance to carry out the situation of label distribution by server before;
2), had the server (this moment is available) of label distribution on the network, webmaster is specified the situation of new server again;
3), had the server (this moment is unavailable, the down machine) of label distribution on the network, webmaster is specified the situation of new server again;
For first kind of situation, the equipment send server notice of then appointed server on the whole network, the Device IP of notification server if equipment need carry out label distribution, then sends the label distribution request to server.Start 3 minutes cycle timer simultaneously, regularly inquire about topology information, the devices advertise server apparatus IP information on the whole network.
For second kind of situation, then new server (being called Server2) is checked the Device IP of the server of preserving on the equipment of own place earlier, send new server set notice and tag library transmission request to old server (being called Serverl), start one-period timer (time cycle is 15 seconds) simultaneously, to be used for the transmission request in cycle before receiving the replying of Serverl.When Serverl receives this request, then the own tag information base of being safeguarded is sent to new server, put the server sign non-simultaneously.Receiving that new server S erver2's replys the back the own tag information base deletion of being safeguarded.New server S erver2 receive the tag library of legacy server send reply before, all equipment send server update notification on the whole network until the just equipment dispatch order on the whole network of replying of receiving legacy server, is not informed the equipment lP of new server.
The third situation is the continuity of second kind of situation, promptly not receiving in new continuous 3 cycles of server that the tag library of legacy server transmits replys, then promptly think legacy server down machine, then all devices send server update notification on the whole network and tag information base transmit request, require the Device IP of server that each equipment change is preserved, and the label information that is handed down to it retransferred to new server, start 15 seconds cycle timers simultaneously, before in 5 time cycles, not collecting the label information of neat all devices, do not process for the label distribution request package of receiving, abandon quietly.If in the cycle of regulation, do not receive replying of certain equipment, then think and no longer consider its label information by this equipment down, begin that the label request is sent label distribution and reply.
So comprehensive above three kinds of situations, after server is designated, before whole network equipment send server notice, check the Device IP of legacy server earlier, if existing then asking to periodic send server update notification of legacy server and tag library transmission (is the saving resource, be placed in the bag and send), if not receiving the label transmission of legacy server in the cycle of regulation replys, then more again on the whole network the request of transmitting of the send server update notification of all equipment periodic and label (for saving resource, be placed in the bag and send), before the label information of collecting neat all devices, do not process for the label distribution request package of receiving, abandon quietly; If new appointed equipment is preserved old server for empty, then directly can carry out label distribution and issue replying to the label request.
3, the removal process of label
When certain customer equipment no longer needs certain label, (for example to remove and descend), customer equipment sends a label to server and reclaims request package and start 15 seconds cycle timer, server is deleted these label values of distributing to this equipment from tag library, can distribute to other equipment (if only distributing labels and label that not responsible recovery does not re-use then finally the situation that label uses or overflows can occur) later on.Reply back timeing closing device in the recovery of receiving server, otherwise resend the recovery request package, reply until receiving.
Claims (2)
1, a kind of network node universal tag distribution method is characterized in that:
A, employing Client:
Allow the label distribution server be bound on certain equipment, after specifying a label distribution server, this label distribution server periodically customer equipment of all on the whole network is given notice, inform the new device address of the label distribution server on this network, each equipment label distribution if desired then sends the label request to this label distribution server;
For the normal down machine of label distribution server, then reassign new equipment as the label distribution server by webmaster, the information transfer of distributing labels of being preserved on the old label distribution server to new label distribution server, give notice with periodic again all customer equipments on the whole network of stylish label distribution server, inform the new device address of the label distribution server on this network;
For label distribution server exception down machine, promptly because mistake or unusual appears suddenly in equipment, the label of having distributed to equipment is unaffected, still can use, only the label distribution server can not be the devices allocation label of applying label at this moment again, and adopt the mode of static manual configuration label that the equipment that needs label is carried out label distribution this moment;
The dynamic auto distributing labels mode of operation of b, label distribution algorithm is a request-response mode:
When the client needs distributing labels, then send label request applying label and distribute to the label distribution server, start the one-period timer simultaneously; The label distribution server uses the customer equipment label distribution situation in the label collision testing mechanism inspection network after obtaining its request, reply to this equipment for the client who asks distributes the label of an available non-conflict and issues then; If the client does not receive replying of label distribution server ticket distribution in the time cycle of described cycle timer, then restart described cycle timer and resend the label distribution request, reply up to the label distribution that obtains described label distribution server; If continuous 3 overtime also not the receiving of described cycle timer are replied, then start another timer, and at described timer expiry and client when not receiving that yet the label distribution of label distribution server is replied, whether client's requester network topology is searched described label distribution server and is existed; If exist, then resend the label distribution request, and restart described cycle timer, reply up to the label distribution that obtains described label distribution server; The encapsulation that in described label distribution request, adds sequence number; If the client sends and do not receive after the described label distribution request and reply, just use identical sequence number to send described label distribution request always and can change sequence number up to receiving to reply; If twice of described label distribution server or repeatedly receive the label distribution request that the client sends, then check the sequence number in the described label distribution request earlier, and sequence number is corresponding and distribute to the label of this equipment therewith, if sequence number is identical, then the label of distributing to the client according to described sequence number is resend to described client, otherwise distribute new label and send to described client for described client; To consider also that in addition label reclaims, when the distributed labels on equipment is determined not re-use, reclaim this label and equipment that it is redistributed to other uses.
2, the method for claim 1 is characterized in that: described device address is an IP address of equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031269753A CN100450009C (en) | 2003-06-17 | 2003-06-17 | Method for distributing universal label of network node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031269753A CN100450009C (en) | 2003-06-17 | 2003-06-17 | Method for distributing universal label of network node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1567824A CN1567824A (en) | 2005-01-19 |
| CN100450009C true CN100450009C (en) | 2009-01-07 |
Family
ID=34469139
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB031269753A Expired - Fee Related CN100450009C (en) | 2003-06-17 | 2003-06-17 | Method for distributing universal label of network node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100450009C (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101064674B (en) * | 2006-04-29 | 2010-12-08 | 华为技术有限公司 | A Multicast MPLS Label Assignment Method |
| CN100563217C (en) | 2006-06-09 | 2009-11-25 | 华为技术有限公司 | Solve the method and system of label collision |
| EP2477361B1 (en) | 2009-09-11 | 2016-03-02 | Huawei Technologies Co., Ltd. | Ip address automatic assignment method, equipment and system |
| CN103401694B (en) * | 2013-05-09 | 2017-06-27 | 瑞斯康达科技发展股份有限公司 | A kind of method and system for realizing node administration |
| CN112214300B (en) * | 2020-10-12 | 2024-05-17 | 北京泽石科技有限公司 | Method and device for processing command timeout and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0896494A2 (en) * | 1997-08-08 | 1999-02-10 | Kabushiki Kaisha Toshiba | Scheme for label switched path loop detection at node device |
| WO2002021399A1 (en) * | 2000-09-08 | 2002-03-14 | United States Postal Service | Automated requesting system |
| CN1411199A (en) * | 2002-11-07 | 2003-04-16 | 上海交通大学 | Content safe monitoring system based on digital label and its method |
-
2003
- 2003-06-17 CN CNB031269753A patent/CN100450009C/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0896494A2 (en) * | 1997-08-08 | 1999-02-10 | Kabushiki Kaisha Toshiba | Scheme for label switched path loop detection at node device |
| WO2002021399A1 (en) * | 2000-09-08 | 2002-03-14 | United States Postal Service | Automated requesting system |
| CN1411199A (en) * | 2002-11-07 | 2003-04-16 | 上海交通大学 | Content safe monitoring system based on digital label and its method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1567824A (en) | 2005-01-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101951417B (en) | Method, system and trunk equipment for assigning multiple server addresses | |
| US5991828A (en) | System for automatically connecting portable device to network using network environment information including domain name of naming device and community name of network management protocol | |
| JP3901806B2 (en) | Information management system and secondary server | |
| US20010005858A1 (en) | Automatic address distributing system | |
| CN111091429A (en) | Electronic bill identification distribution method and device and electronic bill generation system | |
| CN105393617B (en) | The distribution and use of transmission unit in network | |
| KR970701465A (en) | A DATA STORAGE DEVICE | |
| EP2939401B1 (en) | Method for guaranteeing service continuity in a telecommunication network and system thereof | |
| CN114070822B (en) | Kubernetes Overlay IP address management method | |
| CN101355594A (en) | Method for detecting address conflict when distributing IP address | |
| CN102027732A (en) | Providing access over an ip network to a server application program | |
| CN102244690A (en) | Address allocation method and system of dynamic host configuration protocol (DHCP) as well as client side and servers of same | |
| CN106464745A (en) | Dns server, client and data synchronization method | |
| CN104601702A (en) | Cluster remote procedure call method and system | |
| CN103327130B (en) | Method, terminal and system that MAC Address is multiplexed | |
| CN100334855C (en) | Method to allocate protocol relay address table and server address pool for synchronization dynamic host machine | |
| CN100450009C (en) | Method for distributing universal label of network node | |
| CN102769911B (en) | A kind of advertising of route message method and device | |
| CN102664971A (en) | Network address resource managing method and system and external address resource server | |
| CN112565475B (en) | Ip address allocation method for adding new node in container cluster service layer | |
| CN102025797A (en) | Address prefix processing method, device, system and network equipment | |
| CN104009961A (en) | PPPoE session ID distribution method and equipment thereof | |
| CN101611378A (en) | Be used to provide passive automatic configuration method, computer product and device | |
| CN105592485B (en) | A method of it is acquired in real time based on SNMP network management protocol and handles message | |
| CN104639379A (en) | Proxy testing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: HUAWEI TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: GANGWAN NETWORK CO., LTD. Effective date: 20060922 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20060922 Address after: 518129 Bantian HUAWEI headquarters office, Longgang District, Guangdong, Shenzhen Applicant after: Huawei Technologies Co., Ltd. Address before: 100871, No. 21 West Third Ring Road, Beijing, Haidian District, Long Ling Building, 13 floor Applicant before: Harbour Networks Holdings Limited |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: HUAWEI DIGIT TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: HUAWEI TECHNOLOGY CO LTD Effective date: 20120104 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518129 SHENZHEN, GUANGDONG PROVINCE TO: 100085 HAIDIAN, BEIJING |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20120104 Address after: 100085 Beijing, Haidian District on the road, No. 3 Patentee after: Huawei Digit Technology Co., Ltd. Address before: 518129 Bantian HUAWEI headquarters office, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090107 Termination date: 20150617 |
|
| EXPY | Termination of patent right or utility model |