name: MR-DC
full_form: Multi-Radio Dual Connectivity
context: In TS 33.501 [4], NGEN-DC and NE-DC are defined as two possible MR-DC scenarios. In these cases, eNB and gNB are used in dual connectivity. Rel.15 solution in MR-DC scenarios in TS 33.501[4] specify that, depending on the MR-DC scenario being used and the security policy at the time of PDU session establishment, the PDU session may either be rejected, the integrity protection in 5G Uu interface implicitly disabled, or the offload to SN is not allowed. The following cases summarize this behaviour according to TS 33.501[4]: 1. NGEN-DC scenario (CN=5GC, eNB=MN, gNB=SN) a. If the UP security policy indicates UP integrity protection is "required", then the MN (MeNB) rejects the PDU session because the MN being an eNB does not support UP IP. b. If the UP security policy indicates UP integrity protection is "preferred", then the MN (MeNB) always deactivates UP IP. The SN (SgNB) always deactivates the UP IP of any PDU session terminated at the SN. This is because MN being an eNB does not
description: Multi-Radio Dual Connectivity (MR-DC) enables dual connectivity scenarios like NGEN-DC and NE-DC in 5G networks by using different radio access technologies simultaneously. It involves specific security policies and configurations for PDU sessions.
explanation: MR-DC is classified as a Technology because it's a standard defining how telecommunications operate, specifically enabling dual connectivity in 5G networks. Its technical specifications and behaviors, as described in 3GPP TS 33.853, solidify its classification.
section_title: 5.4.1	Issue description
biotag_Context: O,B-Specification,O,O,B-Technology,O,B-Technology,O,O,O,O,O,B-Technology,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,B-Technology,O,O,B-Specification,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Technology,B-Interface,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Technology,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,O,B-Connection,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,B-Message,O,O,O,O,B-Protocol,B-Protocol,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O
biotag_Description: B-Technology,I-Technology,I-Technology,O,O,O,O,O,O,B-Technology,O,B-Technology,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O