WO1999049693A1 - Dynamic bandwidth management and rerouting - Google Patents
Dynamic bandwidth management and rerouting Download PDFInfo
- Publication number
- WO1999049693A1 WO1999049693A1 PCT/CA1999/000259 CA9900259W WO9949693A1 WO 1999049693 A1 WO1999049693 A1 WO 1999049693A1 CA 9900259 W CA9900259 W CA 9900259W WO 9949693 A1 WO9949693 A1 WO 9949693A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- connection
- rerouting
- resource
- active connection
- bandwidth
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0478—Provisions for broadband connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5619—Network Node Interface, e.g. tandem connections, transit switching
- H04L2012/5621—Virtual private network [VPN]; Private-network - network-interface (P-NNI)
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5625—Operations, administration and maintenance [OAM]
- H04L2012/5627—Fault tolerance and recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5629—Admission control
- H04L2012/5631—Resource management and allocation
- H04L2012/5632—Bandwidth allocation
- H04L2012/5634—In-call negotiation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0079—Operation or maintenance aspects
- H04Q2011/0081—Fault tolerance; Redundancy; Recovery; Reconfigurability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0086—Network resource allocation, dimensioning or optimisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
- H04Q11/0062—Network aspects
- H04Q2011/0088—Signalling aspects
Definitions
- the invention generally relates to a network resource management of ATM networks. In particular, it is directed to a technique of performing reroute procedures in the event of a bandwidth change request.
- the current ITU-T Q.2963.2 Recommendation (B-ISDN DSS2 Connection Modification - ATM Traffic Descriptor Modification by connection owner) provides the capability for the connection owner to initiate the MODIFY message to adjust the PCR (peak cell rate), SCR (sustainable cell rate) and MBS (?) dynamically on an active connection.
- IMA inverse multiplexing on ATM
- WATM wireless ATM
- ADSL asymmetric digital subscriber loop
- MPOA asymmetric digital subscriber loop
- the above referenced patent application introduces a new signalling capability to complement the ITU-T Q.2963.2 feature to manage connection bandwidth dynamically.
- the new capability defines a new information element called "dynamic bandwidth management option" in the existing "setup” message and allows the connection owner (i.e. the originator of the connection who initiates the "setup” message) to specify the dynamic bandwidth management option for point-to-point connections, and for the first party of the point-to-multipoint connections, during the connection establishment phase.
- the network or the called party have the need to adjust the bandwidth on an active connection, it can follow the specified bandwidth management option, if given, to initiate the proper action to deal with the changes.
- the network or the connection owner may perform certain maintenance procedures. For example, the connection owner may send a "modify" message on the connection to increase or reduce the bandwidth or such other characteristics of the connection. It is also possible that the connection may have to be rerouted to a new connection path with an adjusted bandwidth.
- maintenance actions taken in one domain are only effected within the same domain, because a different domain may have different maintenance procedures.
- Telecommunication connections often span more than one domain and a request for bandwidth adjustment must be considered differently for a proper maintenance action, whether or not the request originated within or outside the domain.
- One of many maintenance actions is rerouting a connection path, which is normally performed by the network.
- a connection path between a source node and a destination node span across one or more network domains and is made up of one or more connection segments involving one or more intermediate nodes.
- An edge-based rerouting is a rerouting mechanism which replaces a connection segment within a network domain starting from a source node of the domain and ending at a destination node of the domain.
- the network domain is a collection of nodes which participate in rerouting decisions and actions.
- Figure 1 shows a rerouting operation within the domain 10.
- a rerouting node 12 is a node which is responsible for establishing an alternative connection path 14 to a predetermined terminating node 16 which is called a rendezvous node.
- the rerouting node is the source node of the domain and the rendezvous node is the destination node of the domain.
- Figure 1 also show variety of intermediate nodes.
- An original path 18 must be rerouted because of a failed link 20 between two nodes, which will be called a rebounce node 22 and a blocking node 24, depending upon the direction of connection.
- a potential cross-over node 26 is also shown.
- edge-based rerouting There are two types of edge-based rerouting, e.g., "break-before-make” and “make-before-break”. They are also referred as “hard reroute” and “soft reroute.” respectively. “Hard reroute” can be used for connection recovery or priority control features. For other rerouting features such as path optimization and administrative rerouting etc., “soft reroute” is required.
- the rerouting node and rendezvous node participate in the connection control of a rerouting operation.
- a rerouting state machine is designed to run at each end of a connection segment to coordinate the protocol handshake.
- an agreement was made to allow one and only one rerouting operation to be executed in a switch for a connection at one time.
- the soft reroute operation may be interrupted by the hard reroute.
- Figure 2 shows an operation model of an edge-based rerouting between a rerouting node 30 and a rendezvous node 32.
- the rerouting state machine 34 is operating in parallel with the connection state machine at the edges of a PNNI network (domain) 36. Therefore, in some cases when a switch is performing a "soft reroute", up to three state machines may be running simultaneous to reroute a connection, e.g. two connection state machines (one for the incumbent connection 38 and one for the rerouting connection 40), and one rerouting machine.
- the rerouting connection in Figure 2 is going through a different interface than the incumbent one. However, it is possible that the rerouting connection resides at the same interface as the incumbent connection.
- the feature described herein is not designed solely for supporting the ITU-T Q.2963.2 feature. It is an useful capability to inform the connection owner as well as the network operator regarding a significant resource change demand in a network and whether or not the demand originated within the domain. As a result, a decision can be made to initiate a proper maintenance action or to continue/abort performing the action started so that the changes requested can be effectively dealt with.
- the invention resides in an ATM network which is composed of a plurality of domains.
- the invention is directed to a method of managing the resource demand of an active connection which spans one or more domains.
- the method comprises steps of performing a maintenance action at a maintenance node in one domain, receiving a resource change message at the maintenance node, the message indicating a resource change request; and deciding to continue performing the maintenance action in response to the resource change request based upon whether or not the resource change message originated outside the domain of the maintenance node.
- Figure 1 shows a known rerouting operation within a domain.
- Figure 2 shows an operation model of a known edge-based rerouting.
- Figure 3 is an overview of a bandwidth change indication message in an ATM environment.
- Figure 4 shows a format of a dynamic bandwidth management option IE.
- FIG. 3 is an example of the bandwidth change indication operation in an ATM network.
- an ATM network 40 contains a variety of nodes 42, 44, 46 and 48, each having a variety of capabilities.
- nodes 42 and 44 are shown to be holding an IMA virtual link.
- Different interfaces link different pair of nodes, one being defined by ATM Forum under PNNI (Public Network Network Interface).
- Interfaces between a customer and an ATM node are defined in UNI (User Network Interface). Therefore a calling party 50 and a called party 52 are linked with respective nodes through UNI.
- a path has been established between the calling party and the called party through nodes 48, 44, 42, and 46.
- the link between node 42 and 46 is shown as being of any kind.
- each node is able to initiate a "bandwidth change indication" message, when conditions warrant it.
- the connection owner In order to support this dynamic bandwidth change capability, the connection owner must include dynamic bandwidth management option information element in the "setup" request.
- the existing "setup" message is modified to include the-new information element (LE for short) to specify dynamic bandwidth management options that the network and the called party are allowed to call for.
- This IE is specified by the connection owner and is sent to the network or the called party in the "setup" message during the initial connection establishment phase.
- the IE informs them of the connection owner's desired dynamic bandwidth management options for point-to-point connections and for the first user of point-to-multipoint connections. Many options are possible but some typical options would allow the network or the called party to:
- the network and the called party for that connection can determine the type of management action to perform when they encounter circumstances that require modification in resources on the connection. If the resources to be altered are the bandwidth requirement, it may be accomplished by the connection bandwidth modify procedures or rerouting.
- the "bandwidth change indication" message permits these procedures be initiated by not only the connection owner but the network and the called party. If dynamic bandwidth management option IE is absent in the "setup" message, it implies that no specific management option is expected by the connection owner from the network or the called party. However, it does not imply that the network cannot perform its own desired maintenance.
- Any one or more of network elements located at any of the nodes shown in Figure 3 can initiate bandwidth change indication procedure as shown by numeral 54. It is done by sending to the connection owner a "bandwidth change indication" message. The connection owner then initiates connection modify procedures as shown by numeral 56.
- the "bandwidth change indication" message may contain one of the following IEs:
- a "bandwidth change indication" message contains another IE.
- This IE is an “external bandwidth change indicator”. This IE allows the dynamic bandwidth adjustment feature to interact with the edge-based rerouting feature more effectively.
- the “external bandwidth change indicator” LE is to indicate whether or not the "bandwidth change indication” message originated outside the network domain. It contains a single parameter called “external flag”. Currently, only a single value is defined for the external flag, “outside scope of edge-based”, which has the value "00000001". Of course other values for other circumstances are possible.
- the flag is set by the first rendezvous node which intercepts the "bandwidth change indication" message and supports the edge-based rerouting.
- a bandwidth change indication message calls for reduction or increase of bandwidth for the connection. How this message is handled by variety, of node along the connection path will be described below.
- a network node is the rendezvous node which receives the "bandwidth change indication" message from the direction of the called party, when it is in the process of performing the "soft reroute” operation, one of the following actions takes place: 1.
- the bandwidth change request is to reduce the bandwidth. In this case, the rendezvous node shall abort the "soft reroute” operation, and forward the "bandwidth change indication" message to upstream towards the calling party. 2.
- the bandwidth change request is to increase the bandwidth.
- the rendezvous node shall not forward the "bandwidth change indication" message to upstream towards the calling party until the rerouting operation is completed.
- the decision of whether queuing or discarding the "bandwidth change indication" message is local implementation dependent, and is not within the scope of this description.
- the network node is the rendezvous node which receives the "bandwidth change indication” message from the direction of the called party, when it is in the process of performing the "hard reroute” operation, it shall not forward the "bandwidth change indication” message to upstream towards the calling party until the connection is recovered.
- the decision of whether queuing or discarding the "bandwidth change indication” message is local implementation dependent, and is not within the scope of this description.
- the network node If the network node is the rendezvous node which is not performing any rerouting operation, it shall insert the external bandwidth change indicator information element, if not present, with the external flag set to "outside scope of edge-based" in the "bandwidth change indication" message.
- the connection owner may ignore the bandwidth change request and carry on the rerouting operation. It is because that the rerouting may be able to get around the trouble area. Otherwise, if the bandwidth change request is not within the rerouting domain (i.e. the external bandwidth change indicator is present), the network node may abort the "soft reroute" operation and forward the "bandwidth change indication" message towards the calling party.
- the network node may ignore the bandwidth change request and carry on the rerouting operation.
- the decision of whether queuing or discarding the "bandwidth change indication" message is local implementation dependent, and is not within the scope of this description.
- connection owner realizes that the request is generated within its own rerouting domain (i.e. within a single private network), and
- connection owner is also a rerouting node for the edge-based rerouting operation, it is possible that it is in the progress of performing the "soft reroute" operation when it receives the "bandwidth change indication" message.
- the following actions can be performed:
- bandwidth change request is to reduce the bandwidth.
- the bandwidth change request is within the rerouting domain (i.e. the absent of the external bandwidth change indicator IE)
- the connection owner may ignore the bandwidth change request and carry on the rerouting operation. It is because that the rerouting may be able to get around the trouble area.
- the connection owner may abort the "soft reroute” operation and may initiate the "modify request” message (i.e. ITU-T Q.2963 procedures). Otherwise, if the bandwidth change request is not within the rerouting domain and the new bandwidth requirement is not acceptable to the connection owner, the connection owner may clear the connection.
- bandwidth change request is to increase the bandwidth.
- the connection owner may ignore the bandwidth change request and carry on the rerouting operation.
- bandwidth change indication it is possible to have multiple "bandwidth change indication" messages sent from the network and the called party to the calling party. However, it is a local implementation decision at the connection owner to deal with these multiple indications.
- Ln ITU-T Q.2963, section 5.1 clearly states that one and only one modification can be requested by the connection owner at one time. Therefore, the connection owner may wish to buffer the indications in the sequence of which they arrive; or the connection owner may simply discard the subsequent indications until the current modification procedures are completed.
- Figure 4 shows a format of a dynamic bandwidth management option IE which will be modified to contain "external bandwidth change indicator as will be shown below.
- This message is sent by the Succeeding side and delivered to the Preceding side to indicate connection acceptance by the called party. See the table below for addition to the message.
- This message is used by the network or the called party to specify the required new bandwidth for the connection from the connection owner.
- the message is sent from the succeeding side to the preceding side.
- Table 7 Management option (octet 5)
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU29179/99A AU2917999A (en) | 1998-03-26 | 1999-03-25 | Dynamic bandwidth management and rerouting |
JP2000538534A JP2002516497A (en) | 1998-03-26 | 1999-03-25 | Dynamic bandwidth management and rerouting method |
EP99910060A EP1066733A1 (en) | 1998-03-26 | 1999-03-25 | Dynamic bandwidth management and rerouting |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2,233,395 | 1998-03-26 | ||
CA002233395A CA2233395A1 (en) | 1998-03-26 | 1998-03-26 | Dynamic bandwidth management and rerouting |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1999049693A1 true WO1999049693A1 (en) | 1999-09-30 |
Family
ID=4162258
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA1999/000259 WO1999049693A1 (en) | 1998-03-26 | 1999-03-25 | Dynamic bandwidth management and rerouting |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP1066733A1 (en) |
JP (1) | JP2002516497A (en) |
AU (1) | AU2917999A (en) |
CA (1) | CA2233395A1 (en) |
WO (1) | WO1999049693A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1246396A3 (en) * | 2001-03-28 | 2004-05-26 | Alcatel Canada Inc. | Method and apparatus for rerouting a connection in a data communication network based on a user connection monitoring function |
EP1530330A3 (en) * | 2003-11-04 | 2009-03-18 | Alcatel Lucent | Protected paths using DBR reroute paths |
EP1965530A4 (en) * | 2005-12-23 | 2016-10-19 | Zte Corp | A method for soft rerouting in optical network |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995028047A1 (en) * | 1994-04-08 | 1995-10-19 | Telefonaktiebolaget Lm Ericsson | A method and a system for distributed supervision of hardware |
-
1998
- 1998-03-26 CA CA002233395A patent/CA2233395A1/en not_active Abandoned
-
1999
- 1999-03-25 AU AU29179/99A patent/AU2917999A/en not_active Abandoned
- 1999-03-25 WO PCT/CA1999/000259 patent/WO1999049693A1/en not_active Application Discontinuation
- 1999-03-25 JP JP2000538534A patent/JP2002516497A/en active Pending
- 1999-03-25 EP EP99910060A patent/EP1066733A1/en not_active Withdrawn
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995028047A1 (en) * | 1994-04-08 | 1995-10-19 | Telefonaktiebolaget Lm Ericsson | A method and a system for distributed supervision of hardware |
Non-Patent Citations (4)
Title |
---|
HADAMA H ET AL: "VIRTUAL PATH RESTORATION TECHNIQUES BASED ON CENTRALIZED CONTROL FUNCTIONS", ELECTRONICS & COMMUNICATIONS IN JAPAN, PART I - COMMUNICATIONS, vol. 78, no. 3, 1 March 1995 (1995-03-01), pages 13 - 26, XP000527391, ISSN: 8756-6621 * |
JONES C K ET AL: "A FAST ATM REROUTING ALGORTHM FOR NETWORKS WITH UNRELIABLE LINKS", SERVING HUMANITY THROUGH COMMUNICATIONS. SUPERCOMM/ICC, NEW ORLEANS, MAY 1 - 5, 1994, vol. 1, 1 May 1994 (1994-05-01), INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, pages 91 - 95, XP000438889 * |
MARCO DE M ET AL: "BANDWIDTH RE-NEGOTIATION IN ATM NETWORKS FOR HIGH-SPEED COMPUTER COMMUNICATIONS", GLOBECOM '95. IEEE GLOBAL TELECOMMUNICATIONS CONFERENCE, SINGAPORE, NOV. 14 - 16, 1995, vol. 1, 14 November 1995 (1995-11-14), INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, pages 393 - 398, XP000621517, ISBN: 0-7803-2510-9 * |
YUAN R ET AL.: "A signaling and control architecture for mobility support in wireless ATM Networks", 1996 IEEE INTERNATIONAL CONFERENCE ON COMMUNICATIONS (ICC) , CONVERGING TECHNOLOGIES FOR TOMORROW'S APPLICATIONS, 23 June 1996 (1996-06-23) - 27 June 1996 (1996-06-27), Dallas, pages 478 - 484, XP002109515 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1246396A3 (en) * | 2001-03-28 | 2004-05-26 | Alcatel Canada Inc. | Method and apparatus for rerouting a connection in a data communication network based on a user connection monitoring function |
US8199649B2 (en) | 2001-03-28 | 2012-06-12 | Alcatel Lucent | Method and apparatus for rerouting a connection in a data communication network based on a user connection monitoring function |
EP1530330A3 (en) * | 2003-11-04 | 2009-03-18 | Alcatel Lucent | Protected paths using DBR reroute paths |
US7872966B2 (en) | 2003-11-04 | 2011-01-18 | Alcatel Lucent | Protected and high availability paths using DBR reroute paths |
EP1965530A4 (en) * | 2005-12-23 | 2016-10-19 | Zte Corp | A method for soft rerouting in optical network |
Also Published As
Publication number | Publication date |
---|---|
EP1066733A1 (en) | 2001-01-10 |
CA2233395A1 (en) | 1999-09-26 |
AU2917999A (en) | 1999-10-18 |
JP2002516497A (en) | 2002-06-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6275493B1 (en) | Method and apparatus for caching switched virtual circuits in an ATM network | |
EP1213881B1 (en) | System and a method for establishing a communication path on an ATM platform | |
US8018939B2 (en) | MPLS implementation of an ATM platform | |
US7088717B2 (en) | System and method of operating a communication network associated with an MPLS implementation of an ATM platform | |
EP0982899A2 (en) | Boundary device for performing a connection control at a boundary between two communications networks | |
WO1998034415A2 (en) | An architecture for lightweight signaling in atm networks | |
US6967927B1 (en) | Method of transmitting data flows over an ATM network and device for implementing the method | |
US6735176B1 (en) | Dynamic bandwidth management and rerouting | |
EP1449325A2 (en) | Method and system for a switched virtual circuit with virtual termination | |
US6891833B1 (en) | Elimination of premature blocking in communications networks | |
JP3261057B2 (en) | ATM switch and call admission priority control method | |
WO1999049693A1 (en) | Dynamic bandwidth management and rerouting | |
EP0978215A1 (en) | Resource management of an atm connection | |
JP3394430B2 (en) | Network systems and switches | |
JP4428775B2 (en) | Method and system for processing the release order of soft permanent connections | |
KR19980055541A (en) | How to set / release PVC dynamically in ATM network | |
KR100241885B1 (en) | Implementation method of soft pvc of atm network | |
JP3538018B2 (en) | Communication network | |
KR100198095B1 (en) | Virtual channel connection | |
JPH10322361A (en) | Signaling method, switching device, storage medium and network | |
Jones | ITU-T's internodal broadband signalling protocol | |
JP2000286869A (en) | Distributed control for service category request mapping | |
KR19980049366A (en) | How to Provide User-to-User Exchange Virtual Path Connection in Outgoing Relay Lines | |
Law et al. | Access Signalling | |
Gião et al. | Signaling system in B-ISDN |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 1999910060 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 1999910060 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1999910060 Country of ref document: EP |