Question: In a SEAL architecture, when utilizing pre-established MBMS bearers for VAL service group communication sessions, what is an optional configuration for application-level control messages?
Option 1: Always share the same MBMS bearer as the vertical application level communications
Option 2: Use a dedicated unicast bearer for each user's control messages
Option 3: Utilize a pre-existing unicast bearer for all users' control messages in the group
Option 4: Employ a separate, distinct MBMS bearer due to differing bearer characteristic requirements
Explanation: This option is correct because SEAL architecture for VAL services recognizes that application-level control messages may have different bearer characteristic requirements. Using a separate MBMS bearer for control messages is an optional configuration, allowing tailored bearer characteristics (e.g., priority, QoS) to meet control messaging needs without impacting the main service communication bearer.