name: KSISRVCC
full_form: Key Set Identifier for Single Radio Voice Continuity
context: Figure 6.2.2: Key derivation of 5G to UTRAN CS during SRVCC with direct interface between AMF and MSC server 1. The gNB sends Handover Required message to the AMF. 2. The AMF derives CKSRVCC||IKSRVCC using the KAMF key and the current downlink 5G NAS COUNT of the current 5G security context. 3. The AMF assigns the value of ngKSI to the KSISRVCC (maps ngKSI to KSISRVCC) and transfers the CKSRVCC||IKSRVCC and the UE security capability to the MSC server via PS to CS HO request message. 4. The MSC server sends the PS to CS HO response message to the AMF. 5. The AMF sends the HO command to the gNB, in which includes the security parameters in step 3. 6. The gNB sends the HO command to the UE, in which includes the security parameters in step 5. 7. When the UE receives the message, it derives the CKSRVCC||IKSRVCC using the KAMF key and the current downlink 5G NAS COUNT. If the SRVCC handover is not completed successfully, the new mapped CKSRVCC, IKSRVCC and KSISRVCC cannot be used. The MSC
description: KSISRVCC (Key Set Identifier for Single Radio Voice Continuity) is a parameter used in the context of SRVCC (Single Radio Voice Continuity) handovers between 5G and UTRAN CS networks. It is derived from the ngKSI (Next Generation Key Set Identifier) and is used to map the security parameters, specifically CKSRVCC and IKSRVCC, during the handover procedure.
explanation: The description explicitly states that KSISRVCC is a parameter used in SRVCC handovers.  Its role is to facilitate secure communication by transferring security parameters between networks.
section_title: 6.2.2	Solution details
biotag_Context: O,O,O,O,O,B-Technology,O,B-Network,B-Mode,O,B-Technology,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,B-Network Function,O,B-Procedure,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O,O,O,O,B-Technology,B-Protocol,O,O,O,O,B-Technology,O,O,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network Function,O,O,B-Mode,O,B-Mode,B-Procedure,O,O,O,O,B-Network Function,O,O,O,B-Mode,O,B-Mode,B-Procedure,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Technology,B-Protocol,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,B-Network Function
biotag_Description: B-Parameter,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,B-Technology,O,B-Network,B-Mode,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O