Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.012  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   4.1.1.2   4.1.2…   4.1.2.1a   4.1.2.2   4.1.2.3   4.1.2.4…   4.1.2.6…   4.1.2.8…   4.1.2.10…   4.1.3…   4.1.3.2   4.1.3.3…   4.1.4…   4.2   4.2A   4.3   4.4…

 

4.1.2.6  Procedure Activate_Tracing_VLRp. 33

The procedure Check_Parameters is specified in TS 23.018.
Copy of original 3GPP image for 3GPP TS 23.012, Fig. 4.1.2.6-1: (sheet 1 of 1) Procedure Activate_Tracing_VLR
Up

4.1.2.7  Process Send_Identification_PVLRp. 33

Sheet 1: The procedure Check_Parameters is specified in TS 23.018.
Sheet 1: Decision "IuFlex applied?" distinguishes whether or not the PVLR applies "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" as described in TS 23.236. If this feature is applied, the VLR shall extract the NRI from the TMSI and attempt to derive the VLR address of the VLR where the subscriber was previously registered, denoted in the following as the "real PVLR".
Sheet 1: Decision "Result = success?" distinguishes whether the NRI could be successfully converted into the "real PVLR" address. In case of successful conversion, the PVLR shall relay the received Send_Identification message to the "real PVLR" as specified in TS 23.236. The new VLR and the "real PVLR" shall not perceive that relaying is being performed, i.e. they shall not notice the presence of the relaying node. The actual mechanism used to perform the relay is an implementation choice. A possible mechanism is described in clause 4.1.2.9.
Sheet 1: If supported by the VLR, the "Subscriber data dormant" flag shall be set to true to reflect that the MS has moved outside the VLR area. A VLR not supporting this flag shall behave as if the flag is set to false.
Copy of original 3GPP image for 3GPP TS 23.012, Fig. 4.1.2.7-1: (sheet 1 of 1) Process Send_Identification_PVLR
Up

Up   Top   ToC