name: SIP
full_form: Session Initiation Protocol
context: to "0" for the first PDCP SDU received from lower layer; - the DL_Receive PDCP SN shall be incremented by "1" for the next PDCP SDU received from lower layer. - in the UTRAN: - the DL_Send PDCP SN should be set to "0" for the first PDCP SDU submitted to lower layer; - the DL_Send PDCP SN should be incremented by "1" for the next PDCP SDU submitted to lower layer. Additionally, if lossless SRNS relocation is supported by the UE, for each radio bearer configured to support "lossless SRNS relocation or lossless DL RLC PDU size change" as specified in [1], PDCP sequence numbers are applied: - in the UE: - the UL_Send PDCP SN shall be set to "0" for the first PDCP SDU submitted to lower layer; - the UL_Send PDCP SN shall be incremented by "1" for the next PDCP SDU submitted to lower layer; - in the UTRAN: - the UL_Receive PDCP SN should be set to "0" for the first PDCP SDU received from lower layer; - the UL_Receive PDCP SN should be incremented by "1" for the next PDCP SDU received from
description: The Session Initiation Protocol (SIP) is used for establishing, modifying, and terminating real-time communication sessions over IP networks. In the context of 3GPP TS 25.862, SIP traffic is optimized on Radio Access Bearers (RABs) to ensure low delay and loss of SIP packets.
explanation: SIP is classified as a Protocol because it defines rules and procedures for initiating and managing communication sessions. The text explicitly mentions SIP traffic and its optimization on RABs, indicating its role as a signaling protocol.
section_title: 4.4.3	Signaling RAB for SIP
biotag_Context: O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Connection,B-Protocol,B-Connection,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Organization,B-Specification,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O