hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.18 Search folder
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.18.1 General
| The message store client can search stored folder(s) with certain criteria. This procedure allows the message store client to look for folder(s) that meet certain criteria such as when the folder is created. This procedure provides the message store client the ability to locate a specific folder(s) matching the search ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.18.2 Procedure
| The procedure in figure 7.13.3.18.2-1 describes the case when a message store client searches and retrieves relevant stored objects from the MCData message store.
Pre-conditions:
1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figu... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.19 Retrieve folder content
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.19.1 General
| An MCData user can retrieve the content of a folder in the user's message store account. This procedure allows the message store client to retrieve the specific folder's content from the MCData message store.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.19.2 Procedure
| The procedure in figure 7.13.3.19.2-1 describes the case when a message store client retrieves the content of a specific folder in the MCData message store.
Pre-conditions:
1. A successful authentication and authorization have been performed between the message store client and the MCData message store.
Figure 7.1... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.20 Store file contents distributed using HTTP
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.20.1 General
| An MCData user can store the received file content in his message store account. This procedure allows the message store client to request the MCData message store to retrieve the file from the media storage function of MCData content server and store into MCData message store account of the user.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.3.20.2 Procedure for storing the file – receiver side
| The procedure in figure 7.13.3.20.3-1 describes the case when a message store client requests the MCData message store to retrieve the file from media storage function of MCData content server and store into MCData message store account of the user.
Pre-conditions:
1. A successful authentication and authorization hav... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.4 Generic outgoing SDS procedure with MCData message store
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.4.1 General
| When a MCData user is supported with MCData message store all his outgoing communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.4.2 Procedure
| The procedure in figure 7.13.4.2-1 describes the generic SDS service where MCData message store is supported.
Pre-conditions:
1. MCData user has an account created with MCData message store.
2. The configuration to store the MCData communication in MCData message store is enabled for the MCData user.
3. MCData use... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.5 Generic incoming SDS procedure with MCData message store
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.5.1 General
| When a MCData user is supported with MCData message store all his incoming communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.5.2 Procedure
| The procedure in figure 7.13.5.2-1 describes the generic SDS service where MCData message store is supported.
Pre-conditions:
1. MCData user has an account created with MCData message store.
3. The configuration to store the MCData communication in MCData message store is enabled for the MCData user.
3. MCData use... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.6 Interconnection and migration with MCData message store
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.6.1 Interconnection
| There is no interconnection of MCData message stores, as there are no defined reference points providing connection between message stores in different MCData systems.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.13.6.2 Migration
| A migrated MCData user may be provided with access to a local message store by the partner MCData system of the migrated MCData user. The MCData user is identified by the MCData ID used in the partner MCData system by that migrated MCData user in order to access the message store. There is no connection between this me... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14 IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.1 General
| IP data shall be exchanged between two or more data hosts. The MCData client as the link between data host and MC system enables the exchange of IP Data. For addressing the corresponding MCData users either MCData ID or the functional alias can be used independently of each other. The MCData server provides the mechani... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2 IP connectivity for on-network
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1 Information flows for IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.1 MCData IPcon point-to-point request (MCData client to MCData server)
| Table 7.14.2.1.1-1 describes the information flow of the MCData IPcon point-to-point request sent from the MCData client to the MCData server.
Table 7.14.2.1.1-1: MCData IPcon point-to-point request (MCData client to MCData server)
Information element
Status
Description
MCData ID
M
The MCData identity of the ori... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.2 MCData IPcon point-to-point response
| Table 7.14.2.1.2-1 describes the information content of the MCData IPcon point-to-point response as answer to MCData IPcon point-to-point request.
Table 7.14.2.1.2-1: MCData IPcon point-to-point response
Information element
Status
Description
MCData ID
M
The MCData identity of the targeted MCData user.
MCData I... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.3 MCData remote IPcon point-to-point request
| Table 7.14.2.1.3-1 describes the information flow of the MCData remote IPcon point-to-point request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Table 7.14.2.1.3-1: MCData remote IPcon point-to-point request
Information element
Status
Description
MC... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.4 MCData remote IPcon point-to-point response
| Table 7.14.2.1.4-1 describes the information content of the MCData remote IPcon point-to-point response as answer to MCData remote IPcon point-to-point request.
Table 7.14.2.1.4-1: MCData remote IPcon point-to-point response
Information element
Status
Description
MCData ID asked
M
The MCData identity of the aske... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.5 MCData remote IPcon point-to-point tear down request
| Table 7.14.2.1.5-1 describes the information flow of the MCData remote IPcon point-to-point tear down request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Table 7.14.2.1.5-1: MCData remote IPcon point-to-point tear down request
Information element
Sta... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.6 MCData remote IPcon point-to-point tear down response
| Table 7.14.2.1.6-1 describes the information content of the MCData remote IPcon point-to-point tear down response as answer to MCData remote IPcon point-to-point tear down request.
Table 7.14.2.1.6-1: MCData remote IPcon point-to-point tear down response
Information element
Status
Description
MCData ID asked
M
T... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.7 MCData remote IPcon point-to-point application priority change request
| Table 7.14.2.1.7-1 describes the information flow of the MCData remote IPcon point-to-point application priority change request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Table 7.14.2.1.7-1: MCData remote IPcon point-to-point application priority chan... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.1.8 MCData remote IPcon point-to-point application priority change response
| Table 7.14.2.1.8-1 describes the information content of the MCData remote IPcon point-to-point application priority change response as answer to MCData remote IPcon point-to-point application priority change request.
Table 7.14.2.1.8-1: MCData remote IPcon point-to-point application priority change response
Informati... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.2 IP connectivity point-to-point MCData transport service
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.2.1 General
| IP connectivity service capabilities enables MCData unaware data hosts to use usual MCData service capabilities, e.g. data communication between them. This subclause describes the establishment of a point-to-point connection between two IP connectivity clients using the media plane for IP Data transmission. The target ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.2.2 Procedure
| The procedure in figure 7.14.2.2.2-1 describes the case where an IP connectivity capable MCData client is initiating a point-to-point IP connectivity with another IP connectivity capable MCData client.
Pre-conditions:
- The total data volume limit, e.g. daily time limit or total data volume per day does not restrict ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.3 Remote initiated point-to-point IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.3.1 General
| The MCData service shall support mechanisms that allow an authorized MCData user to trigger remotely the establishment of a point-to-point IP connectivity service. This encompasses the procedure of a remote MCData user that addresses the establishment of an IP connectivity between the requested MCData client and the de... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.3.2 Procedure
| The procedure in figure 7.14.2.3.2-1 describes the case where an authorised MCData user triggers remotely the establishment of a point-to-point IP connectivity connection between two other MCData users, required MCData user that establish IP connectivity session to the targeted MCData user.
Pre-conditions:
- The MCDa... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.4 MCData user remote initiated tear down point-to-point IP connectivity
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.4.1 General
| The MCData service shall support mechanisms that allow an authorized MCData user to tear down remotely an established point-to-point IP connectivity. This encompasses the procedure of a remote MCData user that addresses the tear down of an IP connectivity between the requested MCData client and the destination MCData c... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.4.2 Procedure
| The procedure in figure 7.14.2.4.2-1 describes the case where an authorised MCData user triggers remotely the tear down of a point-to-point IP connectivity connection between two other MCData users, the asked MCData user that tear down IP connectivity session to the targeted MCData user.
Pre-conditions:
- The point-t... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.5 Remote initiated point-to-point IP connectivity application priority change
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.5.1 General
| The MCData service shall support mechanisms that allow an authorized MCData user to trigger remotely the adaptation of a point-to-point IP connectivity data bearer service priority. This encompasses the procedure of a remote MCData user that addresses the priority change of a point-to-point IP connectivity between the ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.5.2 Procedure
| The procedure in figure 7.14.2.5.2-1 describes the case where an authorised MCData user triggers remotely the priority change of a point-to-point IP connectivity connection between two other MCData users.
Pre-conditions:
- Optionally, the MCData client 1 may have activated a functional alias to be used.
- A point-to... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.6 Group standalone IP connectivity using media plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.6.1 General
| IP connectivity service capabilities enables authorized MCData unaware data host to use usual MCData service capabilities, e.g. data communication among them. This subclause describes the establishment of a group standalone IP connectivity to a selected MCData group results in affiliated group members exchanging IP dat... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.14.2.6.2 Procedure
| The procedure in figure 7.14.2.6.2-1 describes the case where an IP connectivity capable MCData client is initiating group standalone MCData IP connectivity communication session with an MCData group for exchanging IP Data between group participants using MCData IPcon-2 reference point.
Pre-conditions:
- MCData clien... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.15 Location information (on-network)
| The MCData system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [5], utilising the CSC-14 reference point between the location management client and location management server and the CSC‑15 reference point between the MCData server and location management server.
- The MC s... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.16 Use of ProSe capabilities in off-network MCData communications
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.16.1 General
| When an MCData user using a ProSe-enabled UE wants to communicate with a specific MCData group or MCData user using ProSe capabilities, the MCData client enables the use of the ProSe layer procedures for public safety, as specified in 3GPP TS 23.303 [7].
For an off-network MCData group communication, the MCData clien... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.16.2 Procedures
| The off-network MCData communication procedures using the ProSe capabilities are described within the corresponding clauses of each MCData capability, e.g. SDS procedures for off-network are described in clause 7.4.3 and file distribution procedures for off-network are described in clause 7.5.3.
7.17 Ad hoc group data... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.1 General
| This subclause contains procedures for ad hoc group data communication across a single MCData system for both SDS and FD services, and associated functions such as emergency data communication, Imminent peril data communication and others.
The ad hoc group data communications can use the participants list provided by... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.2 Common Information flows
| 7.17.2.1 Ad hoc group data session request (MCData client – MCData server)
Table 7.17.2.1-1 describes the information flow ad hoc group data session request from the MCData client to the MCData server.
Table 7.17.2.1-1: Ad hoc group data session request information elements
Information Element
Status
Description
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.3.2.4 Modifying of ad hoc group data communication participants by the MCData server
| Figure 7.17.3.2.4-1 below illustrates the MCData server modifying the ad hoc group data communication participants procedure involving multiple MCData systems.
Pre-conditions:
1. The MCData user at MCData client 1 is authorized to initiate ad hoc group data communication.
2. The MCData server 1 of the primary and M... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.1 General
| This subclause contains procedures for ad hoc group short data service data communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjuction with the procedures defined in this subclause. Other common procedures specified in the 7.17.3 are used at any time after ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.2 Information flows for short data service specific
| Table 7.17.4.2-1 describes the information elements that are specific to short data service and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. These information elements are included when an Ad hoc group data session request s... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.3.1 General
| The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.3.2 Procedure
| The procedure in figure 7.17.4.3.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request.
Pre-conditions:
1. As defined in the subclause 7.17.3.1... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.4.1 General
| The initiation of Ad hoc group SDS session results in ad hoc group participants exchanging SDS data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.4.4.2 Procedure
| The procedure in figure 7.17.4.4.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData ad hoc group for exchanging SDS data transactions between the ad hoc group participants, with or without disposition request.
Pre-conditions:
1. As defined in the Common Ad hoc grou... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.1 General
| This subclause contains procedures for ad hoc group file distribution communication across a single MCData system, and uses the common procedures defined in the subclause 7.17.3 in conjuction with the procedures defined in this subclause. Other common procedures specified in the 7.17.3 are used at any time after Ad hoc... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.2 Information flows for file distribution specific
| Table 7.17.5.2-1 describes the information elements that are specific to file distribution and are used along with the common information flows defined in the subclause 7.17.2 for the Ad hoc group short data service data communication. These information elements are included when an Ad hoc group data session request se... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.3.1 General
| The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging SDS data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.3.2 Procedure
| The procedure in figure 7.17.5.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request.
Pre-conditions:
1. As defined in the Common Ad hoc group data communication procedures of ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.4.1 General
| The initiation of Ad hoc group standalone FD using media plane results in ad hoc group participants exchanging FD data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.5.4.2 Procedure
| The procedure in figure 7.17.5.4.2-1 describes the case where an MCData user is initiating ad hoc group standalone data communication for sending file to multiple MCData users, with or without download completed report request.
Pre-conditions:
1. As defined in the Common Ad hoc group data communication procedures of ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6 Ad hoc group standalone short data service using signalling control plane
| |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.1 Information flows
| 7.17.6.1.1 Determine ad hoc group request (MCData client – MCData server)
Table 7.17.6.1.1-1 describes the information flow for the Determine ad hoc group request sent from the MCData client to the MCData server.
Table 7.17.6.1.1-1: Determine ad hoc group request (MCData client – MCData server)
Information element
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.3.1 General
| The initiation of Ad hoc group standalone short data service using signalling control plane results in ad hoc group members from single MCData system receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.3.2 Procedure
| The procedure in figure 7.17.6.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone short data service using signalling control plane with or without disposition request.
Pre-conditions:
1. MCData users on MCData clients 1 to n belong to the same MCData system and are already registered... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.4.1 General
| The initiation of Ad hoc group standalone short data service using signalling control plane results in ad hoc group members from multiple MCData system receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.6.4.2 Procedure
| The procedure in figure 7.17.6.4.2-1 describes the case where an MCData user is initiating ad hoc group standalone short data service using signalling control plane with or without disposition request.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MCData systems s... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.1 Information flows
| 7.17.7.1.1 Ad hoc group standalone FD request (MCData client – MCData server)
Table 7.17.7.1.1-1 describes the information flow for the Ad hoc group standalone FD request sent from the MCData client to the MCData server.
Table 7.17.7.1.1-1: Ad hoc group standalone FD request
Information element
Status
Description
... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.2.1 General
| The initiation of Ad hoc group standalone file distribution using HTTP results in ad hoc group members from single MCData system receiving the file data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.2.2 Procedure
| The procedure in figure 7.17.7.2.2-1 describes the case where an MCData user is initiating ad hoc group standalone file distribution to multiple MCData users, with or without download completed report request from the MCData user.
Pre-conditions:
1. The MCData users on MCData clients 1 to n belong to the same MCData ... |
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.3.1 General
| The initiation of Ad hoc group standalone file distribution using HTTP results in ad hoc group members from multiple MCData system receiving the file data.
|
30497b4d3b4268dfe046b8ed41cd63fb | 23.282 | 7.17.7.3.2 Procedure
| The procedure in figure 7.17.7.3.2-1 describes the case where an MCData user is initiating ad hoc group standalone file distribution to multiple MCData users, with or without download completed report request from the MCData user.
Pre-conditions:
1. The security aspects of sharing the user information between primary... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 1 Scope
| The objective of this technical specification is to specify interworking between MC systems and LMR systems that satisfy the MCPTT requirements in 3GPP TS 22.179 [3], MCCoRe requirements in 3GPP TS 22.280 [2] and the MCData requirements (SDS only) in 3GPP TS 22.282 [4].
The present document refers to an InterWorking F... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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.
-... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 3 Definitions, symbols and abbreviations
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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].
End‑to‑End Encryption: encryption that is applied by an originating termi... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 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].
E2EE End-to-End Encryption
IWF InterWorking Function
KEK Key E... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 4 Introduction
| Mission critical users currently employ a wide range of LMR mission critical Push To Talk services, and associated data capabilities where available.
The present document describes the architecture to support the interworking between the MC system and the LMR system to satisfy interworking requirements specified in 3G... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 5 Assumptions and architectural requirements
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 5.1 Key management
| Interworking requirements for key management for encrypted interworking include:
a) a mechanism to securely (i.e. authenticity, integrity, confidentiality) share an LMR E2EE traffic key for a private call sessions between a party in an MCPTT system and a party in the LMR system;
b) a mechanism to securely convey to g... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 5.2 Packet format
| Each LMR technology defines its own packet format for voice media transmission. For interworking sessions, there might be cases where LMR formatted media is required to be transferred between the IWF and LMR aware MCPTT clients. An example of such a case is where E2EE is used and thus the IWF is not able to decrypt the... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 6 Involved business relationships
| No business relationships have been identified.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7 Functional model
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.1 General
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.2 Functional model description
| Figure 7.2‑1 shows the functional model for the application plane for interworking between MC systems and LMR systems. Functional entities and interfaces depicted on the right-hand side of the IWF‑x interfaces are defined in 3GPP TS 23.280 [5], 3GPP TS 23.379 [7], and 3GPP TS 23.282 [6].
Figure 7.2-1: Functional mod... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.3 Functional entities description
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.3.1 IWF
| The IWF supports most of the functionality of peer MCPTT and MCData systems, with some differences, as specified in the present document. The IWF supports any necessary protocol translation and identity mapping between the MC systems and the IWF. The internal function of the IWF is out of scope of the present document.... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4 Reference points
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.1 Reference point IWF‑1 (between the IWF and the MCPTT server)
| The IWF‑1 reference point, which exists between the IWF and the MCPTT server, provides peer to peer interconnection between an LMR system and the MCPTT system. IWF‑1 supports a subset of MCPTT‑3 as defined in 3GPP TS 23.379 [7], with some differences, as specified in the present document. The IWF‑1 interface is support... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.2 Reference point IWF‑2 (between the IWF and the MCData server)
| The IWF‑2 reference point, which exists between the IWF and the MCData server, provides SDS interconnection between an LMR system and the MCData system. IWF‑2 supports a subset of the functionality of MCData‑SDS‑1 and MCData‑SDS‑2, as defined in 3GPP TS 23.282 [6] with some differences, as specified in the present docu... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.3 Reference point IWF‑3 (between the IWF and the group management server)
| The IWF‑3 reference point, which exists between the IWF and the group management server, provides group management interconnection between an LMR system and the MC system. IWF‑3 is based upon CSC‑16, as defined in 3GPP TS 23.280 [5] with some differences, as specified in the present document.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 7.4.4 Reference point IWF‑4 (between the IWF and the LMS)
| The IWF‑4 reference point, which exists between the IWF and the LMS, provides location information exchange between an LMR system and the MC system. Support of the IWF-4 reference point is optional, since there is no guarantee that the interworked LMR system can support location information.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 8 Identities
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 8.1 Identity mapping
| The IWF provides centralised support for interworking between an MCPTT or MCData system and an LMR system. In MCPTT systems, the identity of an LMR user is provided as an MCPTT ID, and the identity of an LMR group is provided as an MCPTT group ID, which can be used by the IWF to derive the corresponding identities used... |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 9 Application of functional model to deployments
| No applications of functional model to deployments have been identified.
|
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10 Procedures and information flows
| |
b222c2facf93ba50ceb04ea3111d14d8 | 23.283 | 10.1 Affiliation
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.