name: CR
full_form: Connection Release
context: Each involved node is configured with the connections that need to be setup. ASP 1 ASP 2 SG SEP (Primary) (Backup) |------Establish SCTP Association------| |-Estab. SCTP Assoc-| |--Align SS7 link---| Each IP SEP declares to the SG that it is running. +----------------ASP Up----------------> <--------------ASP Up Ack--------------+ +------ASP Up-------> <---ASP Up Ack------+ The Primary IP SEP declares to the SG that it is active. The SG notifies all IP SEPs. +-------------ASP Active---------------> <----------ASP Active Ack--------------+ <----------NTFY (ASP Active)-----------+ <-NTFY (ASP Active)-+ The SG represents the availability of ASP 1 to the SEP. +--------SSA--------> The SEP declares its availability to the SG. Similarly, the SG informs the active ASP of the availability of the SEP as dictated by SGs concerned list. N.B. The SG maps the SS7 address of the SEP to an IP address, which the SG knows ASP 1 will understand. <--------SSA--------+
description: CR stands for Change Request or Connection Release in the context of 3GPP specifications. It refers to a specific type of document or proposal that suggests changes, additions, or modifications to existing technical specifications. In this context, CR is used to introduce new features, such as MIMO (Multiple Input Multiple Output), into various specifications like UE Capability, MAC, RRC, and others.
explanation: The provided context lists several Change Requests (CRs) related to introducing MIMO in different specifications. The mention of 'TS25.xxx CR xxxx' format indicates that these are specific change requests within the 3GPP technical specification documents. Therefore, based on this context, CR is classified as Miscellaneous because it does not fit into other predefined categories but plays a crucial role in the development and modification of telecommunications standards.
section_title: 2	References
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,B-Miscellaneous,O,B-Network Function,B-Network Function,O,O,O,B-Protocol,O,O,B-Protocol,O,O,B-Protocol,O,O,B-Protocol,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Miscellaneous,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,B-Network Function,O,B-Miscellaneous,O,O,O,O
biotag_Description: B-Parameter,O,O,B-Message,I-Message,O,B-Miscellaneous,I-Miscellaneous,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O