name: 3GPP TS 23.285
full_form: 3GPP Technical Specification 23.285
context: The BM-SC initiates the MBMS session start procedure when it is ready to send data. This informs the MBMS GW of the imminent start of the transmission and MBMS session attributes are provided to the MBMS GWs included in the list of downstream nodes in BM-SC. The bearer plane is allocated.
  BM-SC and MBMS GW shall at least support IP unicast encapsulation of IP multicast datagrams, which shall be default mode of sending user plane data. BM-SC may support IP multicast encapsulation of user plane IP multicast datagrams and MBMS GW also may support this mode of operation.
  Figure 20.3.1.1: MBMS Session Start procedure
  1.	The BM-SC sends an RAR message to indicate the impending start of the transmission and to provide the session attributes to the MBMS GWs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. BM-SC may indicate to MBMS GW that BM-SC supports sending the user plane IP multicast data without IP unicast encapsulation. In such case BM-SC shall send multicast source address as specified by IETF RFC 4604Â [73] and IETF RFC 4607Â [74] and the user plane multicast destination address.
  If IP unicast mode is used, the BM-SC shall also require the MBMS GW to select one UDP port for the reception of the user plane data for the related MBMS service (identified by TMGI and Flow ID).
  The BM-SC may also indicate its intent to use IP multicast encapsulation of IP multicast datagrams across Sgi-mb. In this case, the BM-SC shall specify an Sgi-mb (transport) destination multicast IP address associated with the MBMS bearer context, as well as the source UDP port. The inclusion of these data shall mean IP multicast encapsulation of IP multicast datagram is the only offered multicast mode over Sgi-mb. The destination UDP port for IP multicast transport shall be fixed as port number 927. The BM-SC shall also specify the (transport) multicast source address.
  The BM-SC shall indicate the M1 interface information of local MBMS information as specified in 3GPPÂ TSÂ 23.285Â [112] if the BM-SC determines to use the local MBMS information.
  2.	The MBMS GW creates an MBMS Bearer Context, stores the session attributes in the MBMS Bearer Context, initiates session start procedure towards the MMEs/SGSNs in its list of MBMS control plane nodes and sends an RAA message to the BM-SC. In case MBMS GW receives BM-SC multicast source address, which indicates BM-SC support for both modes of sending user plane data, MBMS GW decides in which mode MBMS GW shall receive the user plane data. In case MBMS GW decides to receive unicast encapsulated data, then MBMS GW shall send own IP address for user plane to BM-SC and the MBMS GW shall also indicate the UDP port on which the user plane data shall be received. In case MBMS GW decides to receive IP multicast packets, then MBMS GW shall join the multicast group as specified by IETF RFC 4604Â [73] and IETF RFC 4607Â [74], and indicate to BM-SC about the decision. In case MBMS GW decides to use M1 interface information of local MBMS information, the MBMS GW skips the allocation procedure for IP multicast distribution.
  If configured, the MBMS GW sends the RAA message after receiving the first session start response (when positive) message from any MME.
description: BM-SC uses M1 interface information of local MBMS information as specified in 3GPP TS 23.285.
explanation: Categorized as a Specification because it outlines technical requirements for local MBMS operations.
biotag_Context: O,B-Network Function,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Service,B-Network Function,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,B-Network Function,O,O,B-Message,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,B-Service,O,O,B-Network Function,O,O,O,B-Service,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Network Function,O,O,O,O,B-Service,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Interface,O,O,O,B-Protocol,O,O,O,O,B-Service,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Service,O,O,O,B-Service,B-Network Function,O,O,B-Service,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,B-Service,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,B-Network Function,O,O,B-Service,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,B-Protocol,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,B-Organization,B-Specification,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,O,B-Service,O,O,B-Service,B-Network Function,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Service,B-Network Function,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Network Function,O,O,O,O,O,O,B-Service,O,O,O,O,B-Organization,B-Specification,O