Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑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…

 

9  Compatibility Issuesp. 131

None; this feature is backward compatible with existing features and earlier releases.

10  General (G)MSC server-MGW Proceduresp. 131

LCLS does not modify the general (G)MSC server-MGW procedures as shown in TS 23.205.

11  Identitiesp. 131

11.1  Generalp. 131

The Identities defined in TS 23.205 for BICC based CS Core network and in TS 23.231 for SIP-I with the following additions.

11.2  Global Call Referencep. 131

The Global Call Reference (GCR) IE is derived from the ITU-T Global Call Reference parameter (defined by ITU-T Q.1902.3 [5]).
The Global Call Reference (GCR) information element is a combination of a Network ID field, a Node ID field and a Call Reference ID field. The Call Reference ID field for LCLS is defined to contain a unique call ID.
If the serving radio access is GERAN the Call Reference ID subfield created by originating MSC server contains a unique call ID and the originating BSS ID which is a unique identifier of a Base Station Subsystem (BSS) Node within an operator's network.
The complete parameter layout is specified in TS 29.205.
The GCR is exchanged on the Nc and A interfaces to globally identify the call.
Up

12  Operational Aspectsp. 131

12.1  Chargingp. 131

No impact.

Up   Top   ToC