Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.284  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   5   6…   6.3…   6.3.2   6.3.3   6.3.4   6.3.5   7…   7.2.4…   7.2.4.2   7.2.4.3   7.2.4.4   7.2.4.5   7.2.4.6   7.3…   7.3.4…   7.3.4.2   7.3.4.3   7.3.4.4   8…   8.2.3   8.3…   8.3.2   8.4…   8.4.1.1.7…   8.4.1.2…   8.4.2…   8.4.2.2…   8.4.5…   8.4.5.6   8.4.5.7   8.4.5.8…   9…   13…   13.4…   13.4.3…   13.4.4…   13.5…   13.6…   13.7…   14…   16…   A…   A.2… 
7 Call Clearing and LCLS Break/Re-establishment  7.1 Call Clearing  7.2 LCLS Break  7.2.1 MSC server Initiated  7.2.2 BSS Initiated  7.2.3 Intermediate Node/GMSC Server Initiated 
...

 

7  Call Clearing and LCLS Break/Re-establishment  p. 46

7.1  Call Clearing  p. 46

The call clearing procedures shall be performed in accordance with TS 23.205 for a BICC based CS core network and in accordance with TS 23.231 for a SIP-I based CS core network.

7.2  LCLS Break  p. 46

7.2.1  MSC server Initiated  p. 46

7.2.1.1  Principles  p. 46

When the MSC server determines that local switching should be disconnected:
  • it shall send a LCLS Status Change Request message indicating disconnection preparation through the Core Network.
  • on receipt of a LCLS Status Change Request Acknowledge message indicating disconnection preparation with a Result code indicating LCLS Status Change Request accepted the MSC server shall send a LCLS-Connection-Control message indicating LCLS break to the associated BSS.
On receipt of the LCLS Status Change Request message indicating disconnection preparation the MSC server shall:
  • send a LCLS break request immediately to the associated BSS, and
  • when the acknowledge message is received from the BSS, the MSC server shall return the LCLS Status Change Request Acknowledge message indicating disconnection preparation and a Result code indicating LCLS Status Change Request accepted.
The BSS needs to receive the LCLS break request on both call legs before releasing local switching.
Up

7.2.1.2  MSC server actions  p. 47

When the MSC server determines that local switching should be disconnected it shall send to the succeeding (or preceding) node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination.
On the reception of the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted, the MSC server shall send to the BSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". At reception of the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" if the same LCLS Status Update message was not already received from the succeeding (or preceding) node.
When the MSC server receives the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" it shall send to the BSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination. On reception of the LCLS-Connect-Control Acknowledge message the MSC server shall send to the preceding (or succeeding) node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted.
When the LCLS-Connect-Control Acknowledge or the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" is received, the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" if the same LCLS Status Update message was not already received from the succeeding (or preceding) node.
Up

7.2.1.3  GMSC server actions  p. 47

On receipt of the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" from the preceding (or succeeding) node, the GMSC Server shall forward message to the succeeding (or preceding) node.
The GMSC Server shall forward the received LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE indicating LCLS Status Change Request accepted.
On receipt of the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" from the preceding (or succeeding) node:
  • the GMSC Server shall forward the message to the succeeding (or preceding) node if the same request was not already received from the succeeding (or preceding) node.
  • the GMSC Server shall not forward the message if the same request was already received from the succeeding (or preceding) node.
Up

7.2.1.4  BSS actions  p. 47

On receipt of the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS" the following applies:
  • if the request was received for only one call leg associated to the LCLS call, the BSS shall not break the local switching. The BSS shall only send the LCLS-Connect-Control Acknowledge message to the MSC server with LCLS-BSS-Status indicating LCLS is still established.
  • if the request was received for both call legs associated to the LCLS call, the BSS shall break local switching and shall report the LCLS disconnection on both call legs by sending:
    • the LCLS-Connect-Control Acknowledge message to the MSC server and
    • the LCLS-Notification message to the far end MSC server which previously requested LCLS release for the associated leg.
Up

7.2.2  BSS Initiated  p. 48

7.2.2.1  Principles  p. 48

When the BSS determines that local switching should be disconnected it may:
  • immediately break local switching and then inform the Core Network, or
  • first request the Core Network to prepare for LCLS break and on the reception of LCLS break request on both call legs the BSS breaks local switching.

7.2.2.2  Immediate LCLS break  p. 48

7.2.2.2.1  BSS actions  p. 48
When the BSS determines that local switching should be disconnected it shall immediately break local switching. The BSS shall report the LCLS disconnection by sending the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to both MSC servers associated to the LCLS call.
7.2.2.2.2  MSC server actions  p. 48
At reception of the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" if the same LCLS Status Update message was not already received from the succeeding (or preceding) node. If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination.
Up
7.2.2.2.3  GMSC server actions  p. 48
On receipt of the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" from the preceding (or succeeding) node:
  • the GMSC Server shall forward the message to the succeeding (or preceding) node if the same request was not already received from the succeeding (or preceding) node.
  • the GMSC Server shall not forward the message if the same request was already received from the succeeding (or preceding) node.

7.2.2.3  BSS Requesting LCLS Release from Core Network  p. 48

7.2.2.3.1  BSS actions  p. 48
When the BSS determines that local switching should be disconnected but the LCLS release should be ordered from the Core Network the BSS shall request the LCLS disconnection by sending the LCLS-Notification message with a LCLS-Break-Request IE to both MSC servers associated to the LCLS call.
On receipt of the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS" the BSS shall apply the procedure described in clause 7.2.1.4.
Up
7.2.2.3.2  MSC server actions  p. 49
At reception of the LCLS-Notification message with LCLS-Break-Request IE the MSC server shall send to the succeeding (or preceding) node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination.
On the reception of the LCLS Status Change Request message with the LCLS-Status-Change IE indicating LCLS disconnection preparation, the MSC server shall apply the procedure described in clause 7.2.1.2 with the following exception:
  • on the reception of the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted the MSC server shall not request the LCLS break if it already requested due to the reception of the LCLS Status Change Request message from the succeeding (or preceding) node.
Up
7.2.2.3.3  GMSC server actions  p. 49
The GMSC server shall perform the same actions as described in clause 7.2.1.3.

7.2.3  Intermediate Node/GMSC Server Initiated  p. 49

7.2.3.1  Principles  p. 49

When an intermediate node or a GMSC server determines that local switching should be disconnected it shall send the LCLS Status Change Request message indicating disconnection preparation to the preceding and to the succeeding node.
On receipt of LCLS Status Change Request message indicating disconnection preparation the originating or terminating MSC server shall send LCLS break request immediately to the associated BSS. When the acknowledge message is received from the BSS, the MSC server shall return LCLS Status Change Request Acknowledge message indicating disconnection preparation and a Result code indicating LCLS Status Change Request was accepted.
The BSS needs to receive the LCLS break request on both call legs before releasing local switching.
Up

7.2.3.2  Intermediate Node/GMSC server actions  p. 49

When an intermediate node or a GMSC server determines that local switching should be disconnected it shall send the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" to the preceding and to the succeeding node.
The intermediate node or the GMSC Server not initiating the LCLS break shall forward the received LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation".
On receipt of the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request was accepted from the preceding (or succeeding) node, the intermediate node or the GMSC Server not initiating the LCLS break shall forward message to the succeeding (or preceding) node.
On receipt of the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" from the preceding (or succeeding) node:
  • the intermediate node or the GMSC Server not initiating the LCLS break shall forward the message to the succeeding (or preceding) node.
  • the intermediate node or the GMSC Server initiating the LCLS break shall not forward the message.
Up

7.2.3.3  MSC server actions  p. 49

When the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" is received from the succeeding (or preceding) node, the MSC Server shall send to the BSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination.
If the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration" is received, the MSC server shall send to the preceding (or succeeding) node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted.
At reception of the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected".
At reception of the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", after sending the LCLS Status Change Request Acknowledge message, the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected".
Up

7.2.3.4  BSS actions  p. 50

The BSS shall perform the same actions as described in clause 7.2.1.4.

Up   Top   ToC