hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.1 Transmission control during an MCVideo session
| Figure 7.7.1.3.1-1 describes the procedure for transmission control between the transmission control participant and the transmission control server during an MCVideo session. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (c... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.2 Reception control during an MCVideo session
| Figure 7.7.1.3.2-1 describes the procedure for the reception control between the transmission control participant and the transmission control server during an MCVideo session. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.3 Transmission revoke during an MCVideo session
| Figure 7.7.1.3.3-1 describes the procedure for transmission revoke during an MCVideo session. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server
2. Transmission control is established b... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.4 Queue position during an MCVideo session
| Figure 7.7.1.3.4-1 describes the procedure where the transmission control is conducted for the MCVideo session already established between MCVideo clients (with transmit media granted to transmission control participant B) and server (with a revoke determination at transmission control server). Only two UEs involved in... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.5 Transmit media request cancellation from the video transmission queue
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.5.1 Transmit media request cancellation from the queue – MCVideo user initiated
| Figure 7.7.1.3.5.1-1 illustrates the procedure for transmit media request cancellation from the video transmission queue initiated by the MCVideo user. The MCVideo user may be an authorized user who has rights to cancel the transmit media requests of other MCVideo users, whose transmit media requests are in video trans... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.5.2 Transmit media request cancellation from the queue - transmission control server initiated
| Figure 7.7.1.3.5.2-1 illustrates the procedure for transmit media request cancellation from the queue initiated by the transmission control server. Only two UEs involved in the session are shown for the simplicity.
Pre-conditions:
- It is assumed that transmission control participant B has been granted the permission... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.6 End a media transmission during an MCVideo session
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.6.1 End a media transmission – MCVideo user initiated
| Figure 7.7.1.3.6.1-1 describes the procedure for ending a media transmission during an MCVideo session by a MCVideo user. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server
2. Transmiss... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.6.2 End a media transmission – transmission control server initiated
| Figure 7.7.1.3.6.2-1 describes the procedure for ending a media transmission during an MCVideo session by the transmission control server. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo ser... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.6.3 End a media transmission – remote MCVideo user initiated
| Figure 7.7.1.3.6.3-1 describes the procedure for ending a media transmission during an MCVideo session by a remote MCVideo user. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server
2. Tr... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.7 Remotely initiated media transmission during an MCVideo session
| Figure 7.7.1.3.7-1 describes the procedure for remotely initiated media transmission during an MCVideo session by an authorized user. Only two UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server
... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.1.3.8 Transmission idle during an MCVideo session
| During silence, i.e., when no video transmission is ongoing, the transmission control server may send the transmission idle message to all transmission participants from time to time. The transmission control server sends the transmission idle message in the beginning of silence.
Figure 7.7.1.3.8-1 describes the proce... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2 Off-network transmission control
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.1 General
| The procedure is for providing transmission control to MCVideo UE in an off-network case. Transmission control is performed by using transmission control information flows between the transmission control participant and the transmission control arbitrator. The transmission control arbitrator is a member MCVideo UE of ... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2 Information flows for off-network transmission control
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2.1 Transmission request
| Table 7.7.2.2.1-1 describes the information flow for the transmission request sent by a transmission participant to request for the transmission permission. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.1-1: Transmission request
Information element
Status
Description
MCVideo ID
M
The ident... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2.2 Transmission granted
| Table 7.7.2.2.2-1 describes the information flow for the transmission granted sent by the transmission arbitrator, to indicate that a request for transmission is granted and media may be transmitted. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.2-1: Transmission granted
Information element
St... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2.3 Transmission release
| Table 7.7.2.2.3-1 describes the information flow for transmission release sent by the transmission participant, to indicate that the media transmission is complete and transmission permission is released. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.3-1: Transmission release
Information elemen... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2.4 Transmission rejected
| Table 7.7.2.2.4-1 describes the information flow for transmission rejected sent by the transmission arbitrator, to indicate that a request for the transmission is rejected. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.4-1: Transmission rejected
Information element
Status
Description
MCVideo... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2.5 Transmission revoked
| Table 7.7.2.2.5-1 describes the information flow for transmission revoked sent by the transmission arbitrator, to indicate that the transmission permission, that was earlier granted, is revoked. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.5-1: Transmission revoked
Information element
Status
... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2.6 Transmission arbitration taken
| Table 7.7.2.2.6-1 describes the information flow for transmission taken sent by the transmission participant, to indicate that the transmission participant has taken the responsibility of transmission arbitration. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.6-1: Transmission arbitration taken
... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.2.7 Transmission arbitration release
| Table 7.7.2.2.7-1 describes the information flow for transmission arbitration release sent by the transmission arbitrator, to indicate that the responsibility of transmission arbitration is released. This information flow is sent in unicast or broadcast.
Table 7.7.2.2.7-1: Transmission arbitration release
Information... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.3 Initializing transmission control – single arbitrator approach
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.3-1 describes procedures for transmission participants when an MCVideo client initializes transmission control. The MCVideo client sends a transmission request to detect presence of a transmission arbitrator. If the MCVideo client does not r... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.4 Transmission permission granted
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.4-1 describes procedures for transmission participants when an MCVideo client requests for transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitrat... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.5 Transmission permission rejected
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.5-1 describes procedures for transmission participants when an MCVideo client requests for transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitrat... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.6 Releasing transmission permission
| This subclause is applicable in both the single arbitrator and self arbitration approaches.
Figure 7.7.2.6-1 describes procedures for transmission participants when an MCVideo client releases transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses t... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.7 Transmission override
| This subclause is applicable in the single arbitrator in the approach.
Figure 7.7.2.7-1 describes procedures for transmission participants when an MCVideo client authorized to override, requests for transmission permission.
The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving resp... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.8 Transmission override (revoke self)
| This subclause is applicable in the single arbitrator approach.
NOTE: Transmission override in the self arbitration approach is implementation specific.
Figure 7.7.2.8-1 describes procedures for transmission participants when an MCVideo client authorized to override, requests for transmission permission.
The MCVide... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.9 Transmission arbitration release
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.9.1 Transmission arbitration release
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.9.1-1 describes procedures for an MCVideo client to release transmission arbitration. There is no other MCVideo client to which transmission arbitration can be delegated.
Pre-conditions:
1. An off-network group communication has been esta... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.9.2 Transmission arbitration release with delegation
| This subclause is applicable only in single arbitrator approach.
Figure 7.7.2.9.2-1 describes procedures for an MCVideo client to release transmission arbitration. There are other MCVideo clients currently transmitting to which transmission arbitration can be delegated.
Pre-conditions:
1. An off-network group commu... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.7.2.10 Simultaneous transmission requests
| This subclause is applicable in both the single arbitrator and self arbitration approaches.
Figure 7.7.2.10-1 describes procedures for transmission participants when simultaneous transmission requests are generated when more than one MCVideo client initializes transmission control.
Figure 7.7.2.10-1 shows the expect... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.8 MCVideo service configuration
| The MCVideo service shall support the procedures and related information flows as specified in subclause 10.1 of 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server;
- The MC service ID is the MCVideo ID; and
- The MC ser... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.9 Affiliation and de-affiliation to/from MCVideo group(s)
| The MCVideo service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server;
- The MC service group is the MCVideo group;
- The MC s... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10 Use of MBMS transmission (on-network)
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.1 Information flows for MBMS Transmission
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.1.1 General
| Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [6].
|
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.1.2 MapGroupToBearer
| Table 7.10.1.2-1 describes the information flow to associate a MCVideo group call to a MBMS bearer. It is sent from the MCVideo server to the MCVideo client.
Table 7.10.1.2-1: MapGroupToBearer
Information element
Status
Description
MCVideo group ID
M
This element identifies the MCVideo group, in which the call... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.1.3 UnmapGroupFromBearer
| Table 7.10.1.3-1 describes the information flow to disconnect a MCVideo group call from a MBMS bearer. It is sent from the MCVideo server to the MCVideo client.
Table 7.10.1.3-1: UnmapGroupFromBearer
Information element
Status
Description
MCVideo group ID
M
This element identifies the MCVideo group which will no... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.2 Use of pre-established MBMS bearers
| The MCVideo service shall support the procedure for using pre-established MBMS bearers as specified 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server; and
- The MC service ID is the MCVideo ID.
The MCVideo service shall... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.3 Use of dynamic MBMS bearer establishment
| The MCVideo service shall support the procedure for using dynamic MBMS bearers as specified 3GPP TS 23.280 [6] with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVideo server; and
- The MC service ID is the MCVideo ID.
The MCVideo service shall use the... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.4 Video call connect and disconnect over MBMS
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.4.1 General
| MBMS bearer can be used for MCVideo group calls. One MBMS bearer is not permanently associated to one specific group or group call. Before sending media packets of a group call over MBMS bearer, the MCVideo server shall send the association information between group call and the MBMS bearer. The group call setup proced... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.4.2 Procedure
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.4.2.1 Call connect over MBMS
| In figure 7.10.4.2.1-1 the MCVideo client 1 is the client that initiate an MCVideo chat group call and also the transmitting client. MCVideo client 1 may, but does not have to be in an MBMS service area. The MCVideo client 2 and MCVideo client 3 represents MCVideo clients receiving the MCVideo call over an MBMS bearer.... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.10.4.2.2 Call disconnect over MBMS
| Figure 7.10.4.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCVideo server to the MCVideo clients to indicate that the MCVideo group call is being dissociated from the MBMS bearer.
Figure 7.10.4.2.2-1: Chat group call disconnect on MBMS bearer
1. An MCVideo group call is ... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.11 Void
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.12 User authentication and authorization for MCVideo service
| NOTE: Flow 7.12-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [14] defines the specific user authentication and authorization architecture required by the MCVideo service in order to realize the MCVideo user authentication and authorization requirements as defined in 3GPP TS 22.280 [2].
... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.13 Support for multiple devices
| An MCVideo user may be authorized to use the MCVideo service from multiple MCVideo UEs as per the procedure in subclause 7.12.
If an MCVideo server receives a service authorization request for an MCVideo user who is previously MCVideo service authorized on another MCVideo UE, then the MCVideo server shall process thi... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.14 Location information (on-network)
| The MCVideo system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [6], utilising the CSC-14 reference point between the location management client and location management server and the CSC‑15 reference point between the MCVideo server and location management server.
- The MC... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.15 MCVideo resource management (on-network)
| Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [6].
|
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.16 MCVideo client query
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.16.1 General
| The MCVideo client query is used by an authorized MCVideo client to retrieve the characteristics of the MCVideo clients in an area with certain criteria. The query criteria may be a set of capabilities, or category tags, or a mix of such criterions, etc.
|
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.16.2 Information flows for MCVideo client query
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.16.2.1 MCVideo client query request
| Table 7.16.2.1-1 describes the information flow for the MCVideo client query request from MCVideo client to MCVideo sever.
Table 7.16.2.1-1: MCVideo client query request
Information Element
Status
Description
MCVideo ID
M
The identity of the MCVideo user requesting MCVideo client query
Location information
M
... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.16.2.2 MCVideo client query response
| Table 7.16.2.2-1 describes the information flow for the MCVideo client query response from the MCVideo server to the MCVideo client.
Table 7.16.2.2-1: MCVideo client query response
Information Element
Status
Description
MCVideo ID list
O
The MCVideo clients that fulfil the query criteria
|
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.16.3 MCVideo client query procedure
| Figure 7.16.3-1 describes the procedure for MCVideo client query in on-network. This procedure is applicable to query the MCVideo clients belonging to the same MCVideo system as the requesting MCVideo user.
Pre-conditions:
1. The video capabilities have been collected at MCVideo server during the update MCVideo capa... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17 MCVideo adaptation during MCVideo communication
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.1 General
| The MCVideo adaption is used by an authorized MCVideo client to automatically change the video communication parameters including codec, resolution etc. according to the network conditions changes detected through such as packet loss or packet delay.
|
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.2 Information flows for MCVideo adaptation
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.2.1 MCVideo communication parameter update request
| Table 7.17.2.1-1 describes the information flow for the MCVideo communication parameter update request from MCVideo client to MCVideo sever and from MCVideo server to MCVideo client.
Table 7.17.2.1-1: MCVideo communication parameter update request
Information Element
Status
Description
MCVideo ID
M
The identity ... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.2.2 MCVideo communication parameter update response
| Table 7.17.2.2-1 describes the information flow for the MCVideo communication parameter update response from the MCVideo server to the MCVideo client and from MCVideo client to MCVideo server.
Table 7.17.2.2-1: MCVideo communication parameter update response
Information Element
Status
Description
Result
M
Indic... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.3 MCVideo adaptation procedure
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.3.1 MCVideo adaptation during group communication procedure – transmitting client triggered
| Figure 7.17.3.1-1 describes the procedure for transmitting MCVideo client triggered MCVideo communication parameters update in on-network. For simplicity, only one receiving user is shown in the figure. This procedure is applicable to only one MCVideo transmitting user during the MCVideo group call, e.g., broadcast gro... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.3.2 MCVideo adaptation during group communication procedure – receiving user triggered
| Figure 7.17.3.2-1 describes the procedure for MCVideo server initiated MCVideo communication parameters update in on-network. For simplicity, only one receiving user is shown in the figure. This procedure is applicable to only one MCVideo transmitting user during the MCVideo group call e.g., broadcast group call.
Pre... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.3.3 MCVideo adaptation during private communication procedure – transmitting client triggered
| Figure 7.17.3.3-1 describes the procedure for transmitting MCVideo client initiated MCVideo communication parameters update in on-network. This procedure is applicable to the video push and video pull.
Pre-conditions:
1. The private communication is ongoing between MCVideo cient 1 and MCVideo client 2, and MCVideo c... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.17.3.4 MCVideo adaptation during group communication procedure – receiving user triggered
| Figure 7.17.3.4-1 describes the procedure for receiving user initiated MCVideo communication parameters update in on-network. This procedure is applicable in video push and video pull.
Pre-conditions:
1. The private communication is ongoing between MCVideo cient 1 and MCVideo client 2, and the MCVideo client 1 is re... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.18 Use of ProSe capabilities in off-network MCVideo communications
| |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.18.1 General
| When an MCVideo user using a ProSe-enabled UE wants to communicate with a specific MCVideo group or MCVideo user using ProSe capabilities, the MCVideo client enables the use of the ProSe layer procedures for public safety, as specified in 3GPP TS 23.303 [7].
For an off-network MCVideo group communication, the MCVideo... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.18.2 Procedures
| The off-network MCVideo communication procedures using the ProSe capabilities are described within the corresponding clauses of each MCVideo capability, e.g. group communication procedures for off-network are described in clause 7.1.3 and private communication procedures for off-network are described in clause 7.2.3.
... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.1 General
| This subclause contains procedures for ad hoc group call across one or more MCVideo systems, and associated functions such as emergency call, Imminent peril call, broadcast call and others.
The ad hoc group calls can use the participants list provided by either an initiator of the call or MCVideo server. The MCVideo s... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.2 Information flows
| 7.19.2.1 Ad hoc group call request (MCVideo client – MCVideo server)
Table 7.19.2.1-1 describes the information flow ad hoc group call request from the MCVideo client to the MCVideo server.
Table 7.19.2.1-1 Ad hoc group call request information elements
Information Element
Status
Description
MCVideo ID
M
The MC... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.2.3 Void
| 7.19.2.3a Ad hoc group call request (MCVideo server – MCVideo server)
Table 7.19.2.3a-1 describes the information flow ad hoc group call request between the MCVideo servers.
Table 7.19.2.3a-1 Ad hoc group call request information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of the... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.2.6 Void
| 7.19.2.6a Ad hoc group call response (MCVideo server – MCVideo server)
Table 7.19.2.6a-1 describes the information flow ad hoc group call response between the MCVideo servers.
Table 7.19.2.6a-1: Ad hoc group call response information elements
Information Element
Status
Description
MCVideo ID
M
The MCVideo ID of... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.2.15 Ad hoc group call add user notification (MCVideo server – MCVideo server)
| Table 7.19.2.15 -1 describes the information flow Ad hoc group call add user notification from one MCVideo server to another MCVideo server. This notification is to provide the list of MCVideo IDs meeting the criteria specified in the ad hoc group communication get userlist request from one MCVideo server to another MC... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.2.16 Ad hoc group call remove user notification (MCVideo server – MCVideo server)
| Table 7.19.2.16 -1 describes the information flow Ad hoc group call remove user notification from one MCVideo server to another MCVideo server. This notification is to provide the list of MCVideo IDs no longer meeting the criteria specified in the ad hoc group communication get userlist request from one MCVideo server ... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.2.17 Ad hoc group call release notification (MCVideo server – MCVideo server)
| Table 7.19.2.17 -1 describes the information flow Ad hoc group call release notification from one MCVideo server to another MCVideo server. This notification is to indicate to stop evaluating the criteria to determine the participants list if another MCVideo server is having the criteria specified in the ad hoc group c... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.3 Procedures
| 7.19.3.1 Ad hoc group call procedures in single MCVideo system
7.19.3.1.1 Ad hoc group call setup
Figure 7.19.3.1.1-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user.
Pre-conditions:
1. The authorized user at MCVideo client 1 wants to invite MCVideo users at MCVideo client 2,... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.3.2 Ad hoc group call involving multiple MC systems
| 7.19.3.2.1 Ad hoc group call setup – Participants list determined by the MCVideo server
Figure 7.19.3.2.1-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user wherein the list of participants is determined by the MCVideo server based on the criteria received from the MCVideo client... |
83a712535bfb31cfb14bd881dfea8730 | 23.281 | 7.19.3.2.2 Modification of ad hoc group call participants by the MCVideo server
| Figure 7.19.3.2.2-1 below illustrates the MCVideo server modifying the ad hoc group call participants procedure involving multiple MCVideo systems.
Pre-conditions:
1. The MCVideo user at MCVideo client 1 is authorized to initiate ad hoc group call.
2. The MCVideo server 1 of the primary and MCVideo server 2 of the ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 1 Scope
| This document specifies the functional architecture, procedures and information flows needed to support the Mission Critical Data (MCData) services. MCData is a suite of services which utilizes the common functional architecture defined in 3GPP TS 23.280 [5] to support MC services over LTE including the common services... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 3 Definitions, symbols and abbreviations
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Auto-receive: A mechanism where data smaller than a configured size thres... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
DS Data Streaming
E2EE End to End Encryption
FD File Distribut... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 4 Introduction
| The MCData service suite provides a set of generic capabilities and specific services to enable one-to-one and group data communications between MCData users.
The MCData architecture utilises the common functional architecture to support mission critical services over LTE defined in 3GPP TS 23.280 [5] and aspects of ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5 Architectural requirements
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.1 Transmission control
| The MCData service supports the ability to transmit SDS messages automatically towards the selected recipient user (private communication) or members of the selected MCData group. The MCData server may still reject the sent message (e.g. if there is no authority to send).
For MCData types other than SDS using signall... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.2 Reception control
| The MCData service shall support the ability to receive small amounts of data automatically. The MCData service may store data waiting for delivery in a temporary store, and notify availability to the receiving MCData users, i.e. deferred delivery. The data which is temporarily stored may be configured with "time to li... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.3 Short Data Service capability
| The MCData service shall support SDS capability for one-to-one and group communications.
The SDS capability shall support messages with a maximum payload of at least 1000 bytes. The supported message types shall include text, binary, or hyperlinks. Multiple message types may be interleaved within in a single message p... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.4 File distribution capability
| The MCData service shall support distribution of files for one-to-one and group communications.
The MCData service shall allow the MCData user to send a file or a URL of a file to another MCData user. The source of the file can originate either from an MCData client or from a network functional entity. The generated ... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.5 Data streaming capability
| The MCData service may support data streaming capability for one-to-one and group communications.
The MCData service may allow the MCData user to send a data stream or a URL of a data stream to another MCData user. The source of the data stream can originate either from an MCData client or from a network functional en... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.6 MCData group affiliation and MCData group de-affiliation
| MCData groups may be configured with one or more MCData sub-services (e.g. SDS, FD, DS) as specified within the MCData service. When an MCData user affiliates to an MCData group, the MCData user is affiliated to each of those MCData sub-services configured in the MCData group. The list of MCData sub-services configured... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.7 Conversation management
| The conversation management:
1. shall include a service indication for conversation management in each SDS and FD transaction.
2. may be comprised of SDS transactions or FD transactions or a combination of both.
3. shall include a conversation identifier in each SDS and FD transaction.
4. shall treat conversation... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.8 Bearer management
| |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.8.1 General
| The MCData UE shall use the APNs as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5]. The MCData UE shall use the MC services APN as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5] for the SIP-1 reference point.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.8.2 EPS bearer considerations
| The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [5] shall apply.
|
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.8.3 EPS unicast bearer considerations for MCData
| For an MCData session request, resources shall be requested utilising interaction with dynamic PCC. The MCData system shall request resources over Rx to a PCRF. The dedicated bearer for MCData media shall utilise the QCI value of 70 (as specified in 3GPP TS 23.203 [14]). The request of resources over Rx shall include a... |
ddade5e6357aaccc98ab6d7041f12c18 | 23.282 | 5.8.4 MBMS bearer management
| The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [5].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.