name: 3GPP TS 23.007
full_form: 3GPP Technical Specification 23.007
context: The BM-SC initiates the MBMS heartbeat procedure to detect a SGmb path failure or the restart of the MBMS GW as specified in 3GPP TSÂ 23.007Â [104].
  Figure 20.3.5.1: MBMS Heartbeat procedure initiated by the BM-SC
  1.	The BM-SC sends an RAR message to the MBMS GW and indicates this is a heartbeart request. The BM-SC also includes the Restart-Counter AVP set to its local restart counter.
  2.	The MBMS GW sends an RAA message to the BM-SC to acknowledge the heartbeat request. The MBMS GW also includes the Restart-Counter AVP set to its local restart counter.
  The MBMS GW initiates the MBMS heartbeat procedure to detect a SGmb path failure or the restart of the BM-SC as specified in 3GPP TSÂ 23.007Â [104].
  Figure 20.3.5.2: MBMS Heartbeat procedure initiated by the MBMS GW
  1.	The MBMS GW sends an RAR message to the BM-SC and indicates this is a heartbeart request. The MBMS GW also includes the Restart-Counter AVP set to its local restart counter.
  2.	The BM-SC sends an RAA message to the MBMS GW to acknowledge the heartbeat request. The BM-SC also includes the Restart-Counter AVP set to its local restart counter.
  In the context of this procedure, the Diameter session shall be implicitly terminated, i.e. the client (server) shall behave as if the Auth-Session-State AVP was set to the value NO_STATE_MAINTAINED (1), as described in IETFÂ RFCÂ 6733Â [111]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request.
  NOTE:	The Auth-Session-State AVP is not included in the RAR/RAA message as this is not permitted by the Diameter base protocol. See IETFÂ RFCÂ 6733Â [111].
description: This specification provides details on the MBMS heartbeat procedure and its implementation.
explanation: Categorized as a Specification because it outlines key technical requirements for the MBMS system.
biotag_Context: O,B-Network Function,O,O,B-Service,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,B-Organization,O,O,O,O,O,B-Service,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Message,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,B-Message,O,O,O,B-Network Function,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,B-Service,O,O,O,O,O,B-Interface,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Organization,O,O,O,O,O,B-Service,O,O,O,O,O,B-Service,B-Network Function,O,O,B-Service,B-Network Function,O,O,B-Message,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Service,B-Network Function,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Message,O,O,O,B-Service,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Message,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-Message,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-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,O,O,O,O,O,B-Service,O,O,O,O,O