name: TCP
full_form: Transmission Control Protocol
context: The control plane and user plane protocol stacks of the MBMS GW for interworking with BM-SC are illustrated in Figure 16j , Figure 16k and Figure 16l. The figures include the following protocols:
  -	The "Diameter" SGmb application, as specified in clause 20.
  -	The Control part of the Evolved GPRS Tunnelling Protocol for EPS, GTPv2-C, as specified in 3GPPÂ TSÂ 29.274Â [81].
  -	The User Datagram Protocol,UDP, as specified in IETFÂ RFCÂ 768Â [15].
  -	The Transmission Control Protocol, TCP, as specified in IETFÂ RFCÂ 793Â [18]
  -	The Stream Control Transmission Protocol, SCTP, as specified in IETFÂ RFCÂ 4960Â [109].
  -	The Packet Data Convergence Protocol, PDCP, as specified in 3GPPÂ TSÂ 25.323Â [107].
  -	The MBMS synchronisation protocol, SYNC, as specified in 3GPPÂ TSÂ 25.446Â [106].
  -	The Internet Protocol, IP.
  -	L1 and L2 transport protocols for IP (various options exist).
  Figure 16j: The control plane protocol stacks of MBMS GW for interworking with BM-SC
  Figure 16k: The user plane protocol stacks of MBMS GW for interworking with BM-SC for multicast
  Figure 16l: The user plane protocol stacks of MBMS GW for interworking with BM-SC for broadcast
  A BM-SC sends user plane data to an MBMS GW either by IP unicast (default), or by IP multicasting. Through the control plane communication a BM-SC provides an MBMS GW with necessary data, so that MBMS GW could forward the user plane data downlink either by multicast (default) or by unicast.
  PDCP is not used when the MBMS service is broadcasted in the E-UTRAN, refer to 3GPP TSÂ 36.331Â [94].
description: The TCP protocol is used in the control plane of the MBMS GW for interworking with BM-SC, as specified in IETF RFC 793.
explanation: Categorized as a Protocol because it manages data transfer and communication between network components.
biotag_Context: O,O,O,O,O,O,O,O,O,O,B-Service,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,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,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-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,B-Service,B-Network Function,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,O,B-Service,B-Network Function,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,B-Organization,O,O,O
biotag_Description: O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,B-Organization,B-Specification,O