Mesh network commissioning
US-2015373750-A1 · Dec 24, 2015 · US
US9948722B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9948722-B2 |
| Application number | US-201314389485-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 9, 2013 |
| Priority date | Apr 10, 2012 |
| Publication date | Apr 17, 2018 |
| Grant date | Apr 17, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are a path computation element communication protocol (PCEP) session establishment method and device. The technical solution comprises: at a PCC or PCE node device side, before needing to establish a PCEP session, allocating a TCP connection communication end attribute to a PCC or a PCE at either end in the manner of static configuration/dynamic designation or election mechanism automatic allocation; or detecting whether to establish a TCP connection relationship, if not, actively connecting the opposite end, and if a plurality of TCP connection relationships has been established, simultaneously cutting off a plurality of connections at both ends, and reinitiating a TCP connection after waiting a random time respectively. The present invention achieves the establishment of a PCEP session in the multi-PCE cooperation computation scenario under the condition of meeting two constraint conditions which are specified by a protocol.
Opening claim text (preview).
The invention claimed is: 1. A method for establishing a Path Computation Element Communication Protocol (PCEP) session, comprising steps of: at a Path Computation Client (PCC) or a Path Computation Element (PCE) node equipment side, when it is required to establish a PCEP session between the PCC and another PCE or between the PCE and another PCC or another PCE, automatically allocating, via an electing mechanism, an attribute of the PCC or the PCE node equipment as a communicating end of a TCP connection for the PCEP session as a server or a client, when a requirement for triggering establishment of a PCEP session is met, first detecting whether there is an established TCP connection to a peer PCE or a peer PCC with which the PCEP session is to be established; when there is no established TCP connection, actively seeking, by the PCC or the PCE, a TCP connection to the peer as a client, and executing again, by the PCC or the PCE, the step of detecting whether there is an established TCP connection to a peer PCE or a peer PCC with which the PCEP session is to be established; when there is an established TCP connection, detecting whether there are multiple TCP connections established; when no more than one established TCP connection is detected and no PCEP session has been established with the peer PCE or the peer PCC, activating a flow of PCEP session establishment; otherwise when multiple TCP connections established are detected, simultaneously disconnecting the multiple TCP connections detected, and after waiting a random period of time, actively seeking, by the PCC or the PCE, a TCP connection to the peer as a client, and executing again, by the PCC or the PCE, the step of detecting whether there is an established TCP connection to a peer PCE or a peer PCC with which the PCEP session is to be established, wherein the electing mechanism comprises at least one of: of the PCC and the another PCE or of the PCE and the another PCC or the another PCE, electing a PCC or a PCE with a greater IP address as a server or a client; of the PCC and the another PCE or of the PCE and the another PCC or the another PCE, electing in an autonomous domain a PCC or a PCE with a greater area identifier as a server or a client; and of the PCC and the another PCE or of the PCE and the another PCC or the another PCE, electing a PCC or a PCE with a greater autonomous domain identifier as a server or a client. 2. The method according to claim 1 , wherein the requirement for triggering establishment of a PCEP session comprises at least a PCE node activation or a special event, wherein the special event comprises at least a timer event or a PCEP message event. 3. The method according to claim 1 , wherein after the multiple TCP connections detected are simultaneously disconnected, a PCC or a PCE at one end of one of the disconnected TCP connections determines a local random period of time, and waits the local random period of time before actively seeking the TCP connection to the peer.
Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] · CPC title
Multichannel or multilink protocols · CPC title
Centralised routing · CPC title
Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) · CPC title
specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.