hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.9 Migration
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.9.1 General
| Migration provides means for the MC service user to obtain MC services from a partner MC system. As the MC service client receives one or multiple user profiles for the MC service user from its primary MC system (as described in clause 10.1.4.3). Each user profile contains a list of partner MC systems that the user is permitted to migrate to, along with necessary access information to facilitate service authentication, hence, facilitate migration to the partner MC system.
MC service interconnection needs to be provided between MC systems that wish to provide migration of their MC service users.
Migration of MC service users between any two MC systems can be on a bilateral or unilateral basis.
NOTE 1: Whether migration is bilateral or unilateral between any two MC systems is left to business agreements between the two MC service providers, and is outside the scope of the present document.
Migration may be triggered by the primary MC system or may be requested by the MC service client due to its geographical changes.
Upon a successful service authorization for migration, i.e., once the MC service user is authorized to migrate to a partner MC system, its primary MC system marks the user as migrated, is informed of the target partner MC system, and records the corresponding MC service ID of the migrated user provided by the partner MC system. Further details are described in clause 10.6.3.
The functional alias of a migrated MC service user at a partner MC system, which is defined in the partner MC system, can be utilized as a target address in private communication as described in clause 10.16.3.
During migration of an MC service user to a partner MC system, media of the MC service user's calls may need to be routed to the MC service user's primary MC system e.g. for recording purposes.
NOTE 2: Recording of migrated users is out of the scope of this version of the present document.
Based on the choice of PLMN and IMS utilization (as described in clause 5.2.9.2 and clause 5.2.9.3), if the migration results in having the HSS-IMS and HSS-EPS to be across two different administrative domains, as in clause 9.2.2.1.4 and clause 9.2.2.1.6, then IMS features such as, e.g., T-ADS (3GPP TS 23.237 [10]) related to service continuity between on-network and UE-to-network relay as in annex B, NPLI (3GPP TS 23.228 [38]) related to lawful interception, and P-CSCF restoration (3GPP TS 23.380 [39]) are not supported.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.9.2 PLMN utilisation
| Migrated MC service users should utilize the PLMN used by the partner MC system to access MC services in the partner MC system, however, utilizing the PLMN used by the primary MC system is not precluded.
NOTE 1: The above recommendation ensures the security policy of the partner MC system is not compromised, the expected QCIs are used on the RAN, and ensures service‑level delay requirements are consistently met (which are especially at risk when the HPLMN of the primary MC system and HPLMN of the partner MC system are far apart from a geographical point of view).
NOTE 2: Whether the PLMN used by the partner MC systems or the PLMN used by the primary MC system is used to access MC services in partner MC systems is left to business agreements between MC service providers and is outside the scope of the present document.
MC service users enabled for migration shall be provisioned with configuration that specifies which PLMNs may be used to migrate to other MC systems.
If the PLMN used by a partner MC system is different from the PLMN used by the primary MC system (i.e. migrating MC service user starts using the PLMN used by the partner MC system), then:
- EPC‑level roaming (see subclause 5.2.2) is needed between the PLMN used by the primary MC system and PLMN used by the partner MC system; and
- the PLMN used by the partner MC system needs to enable local break-out for the APNs specified in subclause 5.2.7 that identify the PDNs of the partner MC system; and
- the EPS subscriptions of the PLMN used by the primary MC system utilized by the MC service users who are allowed to migrate to the partner MC system need to be provisioned with, and local break-out enabled for, the APNs specified in subclause 5.2.7 that identify the PDNs of the partner MC system.
If the PLMN used by the partner MC system and the PLMN used by the primary MC system are the same (i.e. migrating MC service user continues to use the PLMN used by the primary MC system), then:
- the EPS subscriptions of the PLMN used by the primary MC system utilized by the MC service users who are allowed to migrate to the partner MC system need to be provisioned with the APNs specified in subclause 5.2.7 that identify the PDNs of the partner MC system.
NOTE 3: Provisioning of APNs in all of the above includes provisioning of any needed access credentials e.g. PAP, CHAP.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.9.3 SIP core / IMS utilisation
| Migrated MC service users should utilise the SIP core / IMS of the partner MC system.
NOTE 1: The above recommendation ensures the security policy of the partner MC system is not compromised and ensures service‑level delay requirements are consistently met (which are especially at risk when the SIP core / IMS of the primary MC system and the SIP core / IMS of the partner MC system are far apart from a geographical point of view).
Where connectivity and security policies allow, the same SIP core / IMS can be utilised to connect to the primary MC system and one or more partner MC systems.
NOTE 2: Whether the same SIP core / IMS can be utilised to connect to the primary MC system and a partner MC system is left to business agreements between MC service providers, and is outside the scope of the present document.
For each partner MC system, MC service UEs of MC service users enabled for migration shall be provisioned with:
- configuration that controls whether the MC service UE shall connect to the SIP core / IMS of the primary MC system or a different SIP core / IMS (i.e. SIP core / IMS of the partner MC system); and
- where a different SIP core / IMS to the primary MC system's SIP core / IMS is to be connected to then the MC service UE shall also be configured with:
- configuration required for the MC service UE to access the SIP core / IMS; and
- credentials required for the MC service UE to register with the SIP core / IMS.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10 Interconnection
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10.1 General
| MC service interconnection allows a first set of MC service users who are receiving MC service from a first MC system to take part in communications with a second set of MC service users, where this second set of MC service users are receiving MC service from a second MC system, and where the second MC system is in a different trust domain to the first MC system.
NOTE: Assumptions for trust domains are described in subclause 5.1.2 of the present document.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10.2 Connectivity
| The MC service clients of the MC service users receiving MC service(s) from a first MC system and using MC service interconnection to take part in communication with MC service users in a second MC system require connectivity to only the identity management server in the second MC system.
IP connectivity is required between MC systems wishing to interconnect. The IP connectivity is used to carry the signalling and application plane protocols needed to provide MC service.
NOTE 1: The IP connectivity between interconnecting MC systems needs to provide appropriate performance (e.g. low packet latency) in order to meet MC service user performance requirements for the MC service.
NOTE 2: If IP connectivity between interconnecting MC systems is carried outside the trust domain of both MC systems, then there will need to be appropriate security measures applied. Such security measures are outside the scope of the present document.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10.3 Migration
| Interconnection may be used by a migrated MC service user who is receiving service from a partner MC system to take part in communication with MC service users in the primary MC system of that migrated MC service user.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10.4 Private calls
| Where private calls take place using interconnection between MC service users who are receiving MC service in different MC systems, the MC system providing MC service to the calling MC service user will provide the controlling function for the private call.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10.5 Group calls
| Where MC service users in a partner MC system of the group home MC system of an MC service group take part in group calls in that group, the group home MC system of the MC service group will provide the controlling function for the group call.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10.6 Group configuration
| A partner MC system may apply local configuration to an MC service group configuration received from the primary MC system (i.e. the group home MC system).
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.10.7 MC system topology hiding
| If an MC system requires internal network topology hiding, then this shall be achieved in the MC system by use of the following:
- proxies for signalling plane functions; and
- gateway MC service servers for application plane functions.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.11 Use of priorities
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.11.1 Requested priority
| The MC system may allow the MC service client to request the priority of a communication by selecting the corresponding priority level. The MC service server can enforce the selected priority level in determining the application priority for resource allocation during communication establishment.
The use of the requested priority may vary depending on MC service provider's policy.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.12 Recording and replay requirements
| The MC system may support recording and replay of group and private communications (media and the metadata) and metadata of non-communication activities (e.g., affiliation/de-affiliation, group management operations).
NOTE: The recording and replay of non-session based communications and non-communication activities is outside the scope of the present document.
An MC user shall be authenticated and authorized to initiate the recording operations.
An MC user shall be authenticated and authorized to initiate the replay operations.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.13 MC gateway UE requirements
| The MC gateway UE shall provide the capabilities to allow an MC service user utilizing a non-3GPP device, which may or may not host the MC clients, to access one or more MC services.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 5.2.14 Sharing administrative configuration between interconnected MC systems requirements
| The MC system may support the sharing of administrative configurations between the primary MC system and the partner MC system.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 6 Involved business relationships
| Based on the information in subclause 5.2.1 and subclause 5.2.2, figure 6-1 shows the business relationships that exist and that are needed to support a single MC service user.
Figure 6-1: Business relationships for MC services
The MC service user belongs to a single mission critical organization based on a MC service user agreement between the MC service user and the mission critical organization. The MC service user can have MC service user agreement and MC service arrangement directly with a single MC service provider.
The mission critical organization and the MC service provider can be part of the same organization, in which case the business relationship between the two is internal to a single organization. The mission critical organization can have MC service arrangements with several MC service providers. In this case, a MC service user of a mission critical organization is always served by only one MC service provider. The MC service provider can have MC service arrangements with several mission critical organizations. The MC service provider can have MC service user agreements and MC service arrangements with several MC service users.
The MC service provider and the home PLMN operator can be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The home PLMN operator can have PLMN operator service arrangements with multiple MC service providers and the MC service provider can have PLMN operator service arrangements with multiple home PLMN operators. As part of the PLMN operator service arrangement between the MC service provider and the home PLMN operator, PLMN subscription arrangements can be provided which allows the MC service UEs to register with home PLMN operator network.
The home PLMN operator can have PLMN roaming agreements with multiple visited PLMN operators and the visited PLMN operator can have PLMN roaming agreements with multiple home PLMN operators.
Where mutual aid operates between MC service providers, figure 6-2 shows the required additional relationship. An MC service user can only affiliate to groups of the partner MC service provider:
- if such a service provider agreement exists; or
- subject to authorisation for a specific group membership from the partner MC service provider.
Figure 6-2: Additional business relationships for mutual aid
The primary and partner MC service providers do not need to be served by the same home SIP core operator in order to support mutual communication and mutual aid when interconnection between the SIP cores is available.
An example of the usage of these business relationships is elaborated for two users, one resident on its primary MC service provider and one providing mutual aid within the same group:
User A is a user on MC service provider X in group M. The relationships are as follows:
a) user A has user configuration established with MC service provider X and forms part of group M;
b) user A uses a PLMN subscription arrangement with PLMN operator R provided by MC service provider X; and
c) MC service provider X has a PLMN operator service arrangement with PLMN operator R.
User B is a user on MC service provider Y and joins group M as part of a mutual aid:
a) user B has user configuration established with MC service provider Y and forms part of its own set of groups relating to MC service provider Y;
b) user B uses a PLMN subscription arrangement with PLMN operator S provided by MC service provider Y;
c) MC service provider Y has a PLMN operator service arrangement with PLMN operator S;
d) MC service provider Y has a service provider agreement with MC service provider X that allows user B to participate within group M; and
e) PLMN operator S has a PLMN roaming agreement with PLMN operator R allowing user B to roam to PLMN operator R.
NOTE: There is no requirement that the PLMN operator that user B roams to is the same PLMN operator that MC service provider X has a service arrangement with. It does however need to support one or more MC services capabilities, and provides service in the same geographic area as used by MC service provider X.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7 Functional model
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.1 General
| The functional model for the MC services architecture is defined as a series of planes to allow for the breakdown of the architectural description.
Further, each plane is expected to operate in an independent manner, providing services to the connected planes as and when requested by the connected plane, and requesting services from other planes as required.
As a consequence of this each plane should manage on its own behalf:
a) use of identities. Each plane is therefore responsible for the privacy of that plane's own identities; and
b) security for that plane. This does not preclude a plane requesting security services from another plane, but that is a decision made within the plane, as to whether to use offered security services or mechanisms within the plane itself.
NOTE: Terminology such as client and server are not meant to imply specific physical implementation of a functional entity.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.2 Description of the planes
| The following planes are identified:
a) application plane: The application plane provides all of the services (e.g. call control, floor control, video control, data control) required by the user together with the necessary functions to support MC service. It uses the services of the signalling control plane to support those requirements. For example, within the MCPTT service, the application plane also provides for the conferencing of media, and provision of tones and announcements; and
b) signalling control plane: The signalling control plane provides the necessary signalling support to establish the association of users involved in an MC service, such as an MCPTT call or other type of MC services. The signalling control plane also offers access to and control of services across MC services. The signalling control plane uses the services of the bearer plane.
Bearers supporting these planes are defined for LTE within 3GPP TS 23.401 [17]. The resource control that is needed to support these planes is defined within 3GPP TS 23.203 [8]. The application plane also relies on the use of multicast bearers established via procedures defined in 3GPP TS 23. 468 [18] and 3GPP TS 23.246 [11].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.3 Functional model description
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.3.1 On-network functional model
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.3.1.1 General
| Each MC service can be represented by an application plane functional model. The functional model across MC services may be similar but is described by the individual functional entities and reference points that belong to that MC service. Within the application plane for an MC service there is a common set of functions and reference points. The common set is shared across services. This common set of functions and reference points is known as the common services core.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.3.1.2 Functional model for an MC system
| Figure 7.3.1.2-1 shows the functional model for the application plane for an MC system.
Figure 7.3.1.2-1: Functional model for application plane for an MC system
The common services core functions and reference points shown in figure 7.3.1.2-1 are shared across each MC service. The description of the functions and reference points specific to an MC service is contained in the corresponding MC service TS.
NOTE 1: The ACM client and ACM server are not essential entities to enable MC services. The ACM client and ACM server are optional and only required if the administrative configuration management feature is deployed. In administrative configuration management case, only the UE of an authorized MC service user requires such an ACM client.
NOTE 2: The recording server, recording admin client and replay client and mass storage(s) are optional entities. They are not essential to enable MC services. The recording admin client and replay client can also be implemented in devices that do not contain MCPTT / MCData / MCVideo service clients and that are connected to the CSC and recording server using other communication networks than EPS. See subclause 7.3.1.3.
NOTE 3: The Le reference point is not an essential reference point to enable MC services. It is only required if location information of MC service UE(s) is obtained from the PLMN operator via the LCS.
In the model shown in figure 7.3.1.2-1, the following apply:
- A specific MC service server is an instantiation of a GCS AS in accordance with 3GPP TS 23.468 [18].
- The functional alias management client is an integrated functional entity of the configuration management client. The functional alias management client is described in subclause 7.4.2.2.12.
- The functional alias management server is an integrated functional entity of the configuration management server. The functional alias management server is described in subclause 7.4.2.2.13.
Figure 7.3.1.2-2 shows the functional model for the signalling control plane.
Figure 7.3.1.2-2: Functional model for signalling control plane
Figure 7.3.1.2-3 shows the relationships between the reference points of the application plane of an MC service server and the signalling plane.
Figure 7.3.1.2-3: Relationships between reference points of MC service application plane and signalling control planes
NOTE 4: Application plane reference point CSC-7 makes use of SIP-2 reference point when the group management servers are connected by a single SIP core. Where they are joined by more than one SIP core, CSC-7 also makes use of the SIP-3 reference point.
NOTE 5: For simplicity, the HTTP proxy, which provides the interconnection between HTTP-1, HTTP-2 and HTTP-3 reference points, is not shown in figure 7.3.1.2-3.
NOTE 6: CSC-5, CSC-15, REC-3, REC-4 and REC-5 make use of SIP-1 and SIP-2 reference point. For simplicity, this mapping relationship is not shown in figure 7.3.1.2-3.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.3.1.3 Functional model for Recording admin UE and Replay UE
| The recording admin and replay functions can be implemented also in UEs that are not MC service UE’s i.e. do not have the MCPTT / MCData / MCVideo clients.
A minimum set of MC common functions are required in such UEs. Two examples are presented in this clause, a “Recording admin UE” and a “Replay UE”.
Figure 7.3.1.3-1: Functional model for application plane of a Recording admin UE
Figure 7.3.1.3-2: Functional model for application plane of a Replay UE
NOTE: A recording admin client and a replay client can also be implemented in the same UE.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.3.2 Off-network functional model
| Figure 7.3.2-1 shows the functional model for off-network operation.
Figure 7.3.2-1: Functional model for MC service off-network operation
For a specific MC service, the description of off-network operation is contained in the corresponding MC service TS.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4 Functional entities description
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2 Application plane
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.1 General
| Entities within the application plane of an MC system provide application control and media specific functions to support one or more MC services.
For each MC service, the functional entities description is contained in the corresponding MC service TS.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2 Common services core
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.1 Configuration management client
| The configuration management client functional entity acts as the application user agent for configuration related transactions. The configuration management client interacts with the configuration management server and provides and receives configuration data.
The configuration management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane.
The configuration management client provides the functional alias management client functionality as described in subclause 7.4.2.2.12.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.2 Configuration management server (CMS)
| The configuration management server is a functional entity used to configure one or more MC service applications with non-group management MC service related information and configure data on the configuration management client. The configuration management server manages MC service configuration supported within the MC service provider.
The configuration management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane.
The configuration management server provides the functional alias management server functionality as described in subclause 7.4.2.2.13.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.3 Group management client
| The group management client functional entity acts as the application user agent for management of groups. A MC system maintains groups corresponding to one or more mission critical organizations. The group management client interacts with the group management server.
The group management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.4 Group management server (GMS)
| The group management server functional entity provides for management of groups supported within the MC service provider.
The group management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane.
All the group management clients supporting users belonging to a single group are required to use the same group management server for that group. A group management client supporting a user involved in multiple groups can have relationships with multiple group management servers.
The group management server manages media policy information for use by the UE for media processing.
The group management server manages group call policy information for use by the UE for both on-network and off-network group call control.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.5 Identity management client
| This functional entity acts as the application user agent for MC ID transactions. It interacts with the identity management server.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.6 Identity management server (IdMS)
| The identity management server is a functional entity that is capable of authenticating the MC ID. It contains the knowledge and means to do authentication by verifying the credentials supplied by the user.
The identity management server functional entity may reside in the same domain as the user's MC system.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.7 Key management client
| This functional entity acts as the application user agent for key management functions. It interacts with the key management server.
The functionality of the key management client is specified in 3GPP TS 33.180 [25].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.8 Key management server (KMS)
| The key management server is a functional entity that stores and provides security related information (e.g. encryption keys) to the key management client, group management server and MC service server(s) to achieve the security goals of confidentiality and integrity of media and signalling.
The functionality of the key management server is specified in 3GPP TS 33.180 [25].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.9 Location management client
| This functional entity acts as the application user agent for location management functions. It interacts with the location management server.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.10 Location management server (LMS)
| The location management server is a functional entity that receives and stores user location information, and provides user location information to the MC service server. The location management server may also acquire location information provided by PLMN operator (e.g. LCS).
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.11 Void
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.12 Functional alias management client
| The functional alias management client functional entity acts as the application user agent for management of functional aliases. The functional alias management client interacts with the functional alias management server.
The functional management client functional entity is supported by the signalling user agent and by the HTTP client functional entities of the signalling control plane.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.13 Functional alias management server
| The functional alias management server functional entity provides the configuration management of functional alias(es).
The functional alias management server functional entity is supported by the SIP AS and by the HTTP server functional entities of the signalling control plane.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.14 Void
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.2.15 Void
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.3 MC service
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.3.1 MC service client
| The MC service client functional entity acts as the user agent for all MC service transactions. For a specific MC service, the detailed description of functions of the MC service client is contained in the corresponding MC service TS.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.3.2 MC service server
| The MC service server functional entity provides centralised support for MC services.
The MC service server functional entity represents a specific instantiation of the GCS AS described in 3GPP TS 23.468 [18] to control multicast and unicast operations for group communications. For a specific MC service, the detailed description of the GCS AS role assumed by the MC service server is contained in the corresponding MC service TS.
The MC service server performs the functional alias controlling role for functional alias management including functional alias activation, deactivation, take over and interrogation. For a single functional alias, only one MC service server is specified as the functional alias controlling role. The detailed description of the functional alias controlling role assumed by the different MC service servers are contained in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] and 3GPP TS 23.282 [13].
The MC service server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.3.3 MC service user database
| This functional entity contains information of the MC service user profile associated with an MC service ID that is held by the MC service provider at the application plane. The MC service user profile is determined by the mission critical organization, the MC service provider, and potentially the MC service user.
Each MC service shall have a corresponding MC service user database i.e. MCPTT user database as defined in 3GPP TS 23.379 [16], MCVideo user database as defined in 3GPP TS 23.281 [12] and MCData user database as defined in 3GPP TS 23.282 [13]. These MC service user databases can be co-located.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.3.4 MC gateway server
| The MC gateway server provides support for interconnection between a primary MC system and a partner MC system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MC service servers in the partner MC system without needing to expose the MC service servers in the primary MC system outside the trusted domain of the primary MC system. It may be a role of an MC service server described in subclause 7.4.2.3.2 of the present document.
The MC gateway server is responsible for relaying signalling control messages and media between MC service servers in the interconnected MC systems.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.4 Recording and replay
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.4.1 Replay client
| The replay client is a functional entity that acts as the application user agent for replay services i.e. retrieving of recorded metadata and media from recording server(s) and replaying it. The replay client interacts with the recording server.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.4.2 Recording server
| The recording server is a functional entity that can receive and record communications metadata and media, relating to target users and target groups, from MC service servers. The recording server securely stores the recorded information into mass storage(s) and allows controlled access for replay/retrieve functions.
The security aspects of storing metadata and media into mass storage are specified in TS 33.180 [25].
The recording server functional entity is supported by the SIP AS functional entities of the signalling control plane.
The target users and/or groups for recording are set in the MC service user profile configuration data (A.3) and in the group configuration data (A.4). This can be done by an authorized recording admin user utilizing the CSC-4 reference point (user profiles) and CSC-2 reference point (group profiles).
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.4.3 Mass storage
| The recorded media and metadata are stored on mass storage(s). The storage solution is outside the scope of the present document.
NOTE: MC recording server and mass storage(s) can be co-located.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.4.4 Recording admin client
| The recording admin client is a functional entity that acts as the application user agent for recording admin services i.e. setting or modifying target users and target groups for recording. The recording admin client interacts with the configuration management server via configuration management client and with the group management server via group management client.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.5 Administrative Configuration Management
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.5.1 ACM client
| The ACM client is a functional entity that acts as the application user agent for an authorized user that is responsible for requesting, approving, and applying configurations between a primary MC system and partner MC system. These configurations include MC service user profile, group management, and associated system parameters. The administrative configuration management client interacts with the administrative configuration management server.
The ACM client functional entity is supported by the signalling user agent and by the HTTP client functional entities of the signalling control plane.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.2.5.2 ACM server
| The ACM server is a functional entity that provides the necessary capabilities to control and perform required transactions to exchange administrative configurations and/or information between partner MC system(s). ACM server has the following functions:
- Provides the temporary storage of configuration changes when requests are received from a partner MC system. The configuration changes include MC service user profile, group management configuration, and associated system parameters.
- Supports requests from the ACM client that result in exchanges with the partner MC system to share administrative configurations and information.
- Controls, processes, validates, accepts, forwards or rejects administrative configuration exchange based on a set of pre-defined rules and policies.
The administrative configuration management server functional entity is supported by the SIP AS and by the HTTP server functional entities of the signalling control plane.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3 Signalling control plane
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1 SIP entities
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.1 Signalling user agent
| This functional entity acts as the SIP user agent (both client and server) for all SIP transactions.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.2 SIP AS
| The SIP AS functional entity supports the following functions on behalf of the MC service:
- influencing and impacting the SIP session; and
- supporting event subscription and event notification.
NOTE: In the IM CN subsystem, this is provided by the Application Server as defined in 3GPP TS 23.002 [6].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.3 SIP core
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.3.1 General
| The SIP core contains a number of sub-entities responsible for registration, service selection and routing in the signalling control plane.
The SIP core shall be either:
1. compliant with 3GPP TS 23.228 [9], i.e. the SIP core is a 3GPP IP multimedia core network subsystem; or
2. a SIP core, which internally need not comply with the architecture of 3GPP TS 23.228 [9], but with the reference points that are defined in subclause 7.5.3 (if exposed), compliant to the reference points defined in 3GPP TS 23.002 [6].
The data related to the functions of the SIP core, e.g. for data for application service selection, the identity of the serving registrar or authentication related information may be provided by the PLMN operator responsible for the bearer plane. In this case, the SIP database that is the source of the data may be part of the HSS. Alternatively, this data may be provided by the MC service provider. In this case, the source of the data may be the MC service provider's SIP database.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.3.2 Local inbound / outbound proxy
| The local inbound / outbound proxy functional entity acts as both an inbound proxy and an outbound proxy for all SIP transactions. This functional entity can provide the following functions:
- NAT traversal;
- Resource control;
- Route/forward requests and responses to the user agents;
- SIP signalling security; and
- Depending on the PLMN operator policy, discovery and address resolution, including E.164 numbers.
NOTE: In the IM CN subsystem, this functional entity is provided by the P-CSCF as defined in 3GPP TS 23.228 [9].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.3.3 Registrar finder
| The registrar finder functional entity is responsible for:
a) Identifying the serving registrar / application service selection functional entity. The serving registrar / application service selection functional entity is identified using information provided either by the PLMN operator's own SIP database or the MC service provider's SIP database, and optionally using the PLMN operator's internal information e.g. network topology, registrar availability.
1) Registrar finder and registrar in the MC service provider domain: registrar finder in the MC service provider's domain uses the information from the MC service provider's SIP database to identify the serving registrar in the MC service provider domain.
2) Registrar finder and registrar in the PLMN operator domain: registrar finder uses information from PLMN operator's SIP database to identify the serving registrar in the PLMN operator domain.
3) Registrar finder in PLMN operator domain and registrar in MC service provider domain: registrar finder uses information from the MC service provider's SIP database to identify the serving registrar in the MC service provider domain.
NOTE 1: The need for the registrar finder is deployment specific e.g. a deployment that has only one registrar does not need the registrar finder and the related SIP database information.
b) Providing discovery and address resolution, including E.164 numbers.
NOTE 2: In the IM CN subsystem, this is provided by the I-CSCF as defined in 3GPP TS 23.228 [9].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.3.4 Registrar / application service selection
| The registrar / application service selection functional entity provides the following functions:
- Registrar function (with integral provision of a location server) and also acts as an inbound proxy (with access to the integral location server), and outbound proxy for all SIP transactions where application service selection is required. It registers the user and maintains the association of the location and identity of the user in a location service. It provides notifications of the registration states.
- Supports authentication for identities provided within SIP signalling. Both the registrar (with integral location server) and authentication functions are supported by access either to the public network's own SIP database or the MC service provider's SIP database.
- Can provide the application service selection for all SIP transactions, possibly based on application service selection information stored by either the public network's own SIP database or the MC service provider's SIP database.
- Performs SIP signalling security.
NOTE: In the IM CN subsystem, this is provided by the S-CSCF as defined in 3GPP TS 23.228 [9].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.1.4 Diameter proxy
| This functional entity acts as a proxy agent for Diameter messaging as specified in IETF RFC 6733 [26].
The Diameter proxy, when used on the AAA-2 interface may also be present in the SIP core / IMS.
NOTE: The number of instances of the Diameter proxy is deployment specific.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.2 SIP database
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.2.1 General
| The SIP database contains information concerning the SIP subscriptions and corresponding identity and authentication information required by the SIP core, and such information as application service selection.
In deployment scenarios where the PLMN operator provides the SIP core, this database is provided by the HSS.
In deployment scenarios where the MC service provider provides the SIP core, the SIP database may be provided by the MC service provider.
Access to the data residing in the SIP database is restricted to the SIP core entities that are specifically serving the subscriber/user whose data are stored, i.e. registrars and registrar finders can access SIP databases only when they are part of the same trust domain for the data being provided.
NOTE: The SIP database can be in a different network than the registrar finder since the trust domain for the criteria for registrar selection can be different than the trust domain for the signalling plane user identities.
The SIP database is responsible for storing the following user related information:
- signalling plane user identities: Numbering and addressing information;
- signalling plane security information: SIP core access control information for authentication and authorization;
- MC service UE Location information at inter-system level: the SIP database supports the user registration, and stores inter-system location information, etc.; and
- signalling plane subscription profile (including initial filter criteria).
The SIP database also generates signalling plane security information for mutual authentication, communication integrity check and ciphering.
Based on this information, the SIP database is also responsible to support the call control and session management entities of the SIP core.
The SIP database consists of the following functionalities:
- support for control functions of the SIP core such as the Registrar and Registrar finder. This is needed to enable subscriber usage of the SIP core services. This functionality is independent of the access network used to access the SIP core; and
- authentication functionality required by the SIP core to authenticate the MC service UE.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.2.2 SIP database logical functions
| The SIP database provides the following logical functions:
a) mobility management;
- provides the UE mobility through the SIP core.
b) registrar assignment support;
- provides to the registrar finder the required capabilities for MC services based on MC service provider requirements on a per-user basis, (e.g. whether a particular registrar within the PLMN operator's network (e.g. a registrar reserved for MC service use or a registrar in a secure location) or a registrar within the MC service provider network is assigned.
c) call and/or session establishment support;
- provides the call and/or session establishment procedures in the SIP core. For terminating traffic, it provides information on which registrar currently hosts the user.
d) user security information generation;
- provides generation of user authentication, integrity and ciphering data for the SIP core.
e) signalling plane security support;
- provides authentication procedures to access MC services by storing the generated data for authentication, integrity and ciphering at the signalling plane and by providing these data to the appropriate registrar.
f) user identification handling;
- provides the appropriate relations among all the identifiers uniquely determining the signalling plane identities in the SIP core e.g. IMS public identities.
g) access authorisation; and
- provides authorisation of the user for mobile access when requested by the registrar e.g. by checking that the user is allowed to roam to that visited network.
h) service authorisation support.
- provides basic authorisation for terminating call/session establishment and service invocation. The SIP database may update the registrar with filter criteria to trigger the MC service server(s).
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.3 HTTP entities
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.3.1 HTTP client
| This functional entity acts as the client for all hypertext transactions.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.3.2 HTTP proxy
| This functional entity acts as a proxy for hypertext transactions between the HTTP client and one or more HTTP servers. The HTTP proxy terminates a TLS session on HTTP-1 with the HTTP client of the MC service UE allowing the HTTP client to establish a single TLS session for hypertext transactions with multiple HTTP servers that are reachable by the HTTP proxy.
The HTTP proxy terminates the HTTP-3 reference point that lies between different HTTP proxies. It may provide a topology hiding function from HTTP entities outside the trust domain of the MC system.
The HTTP proxy is not used as part of CSC-1 interface. CSC-1 is a direct HTTP interface between the IdM client in the UE and the IdM server as specified in 3GPP TS 33.180 [25].
According to 3GPP TS 33.180 [25], either an HTTP proxy or a direct HTTP interface is used between the key management server and the key management client in the UE for CSC-8.
The HTTP proxy shall be in the same trust domain as the HTTP clients and HTTP servers that are located within a MC service provider's network. There can be multiple instances of an HTTP proxy e.g. one per trust domain.
NOTE: The number of instances of the HTTP proxy is deployment specific.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.4.3.3.3 HTTP server
| This functional entity acts as the HTTP server for all hypertext transactions.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5 Reference points
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.1 General reference point principle
| The protocols on any reference point that is exposed for MC service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in 3GPP TS 23.002 [6].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2 Application plane
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.1 General
| The reference points for the application plane of an MC service are described in the following subclauses.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.2 Reference point CSC-1 (between the identity management client and the identity management server)
| The CSC-1 reference point, which exists between the identity management client and the identity management server, provides for the authentication of the common services core to the MC service client, recording admin client and replay client and subsequent authentication of the user to the common services core on behalf of applications within the application plane.
CSC-1 is specified in 3GPP TS 33.180 [25].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.3 Reference point CSC-2 (between the group management client and the group management server for configuration while UE is on-network)
| The CSC-2 reference point, which exists between the group management client and the group management server, is used for MC service signalling for MC service data management of the MC service.
The CSC-2 reference point supports:
- Configuration of group related data at the group management client by the group management server; and
- Configuration of group related data at the group management server by the group management client.
The CSC-2 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The CSC-2 reference point shall use SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.4 Reference point CSC-3 (between the MC service server and the group management server)
| The CSC-3 reference point, which exists between the MC service server and the group management server, provides for the MC service server to obtain group information corresponding to the MC service. The CSC-3 reference point shall use HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The CSC-3 reference point shall use SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a MC service server and the group management server, are served by different SIP cores.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.5 Reference point CSC-4 (between the configuration management client and the configuration management server for configuration while UE is on-network)
| The CSC-4 reference point, which exists between the configuration management client and the configuration management server, provides the configuration information required for MC services while the MC service client is on-network.
The CSC-4 reference point supports:
- configuration of the MC service UE by the MC service; and
- configuration of the MC service application with the MC service related information that is not part of group management (e.g. policy information) by the MC service UE.
The CSC-4 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The CSC-4 reference point shall use SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.6 Reference point CSC-5 (between the MC service server and the configuration management server)
| The CSC-5 reference point, which exists between the MC service server and the configuration management server, provides for the MC service server to obtain non-group MC service related information (e.g. policy information). The CSC-5 reference point shall use HTTP-1 reference point and HTTP-2 reference point for transport and routing of non-subscription/notification related signalling. The CSC-5 reference point shall use SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a MC service server and the configuration management server, are served by different SIP cores.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.7 Reference point CSC-7 (between the group management servers)
| The CSC-7 reference point, which exists between group management servers, allows group management servers to handle group management related signalling in the same security domain. The CSC-7 reference point shall use the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling. The CSC-7 reference point shall use SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a pair of group management servers, are served by different SIP cores.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.8 Reference point CSC-8 (between the key management server and the key management client)
| The CSC-8 reference point, which exists between the key management server and the key management client, provides a means for the key management server to provide security related information (e.g. encryption keys) to the key management client.
The CSC-8 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of security related information to the key management client.
CSC-8 is specified in 3GPP TS 33.180 [25].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.9 Reference point CSC-9 (between the key management server and the MC service server)
| The CSC-9 reference point, which exists between the key management server and the MC service server, provides a means for the key management server to provide security related information (e.g. encryption keys) to the MC service server.
The CSC-9 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of security related information to the MC service server.
CSC-9 is specified in 3GPP TS 33.180 [25].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.10 Reference point CSC-10 (between the key management server and the group management server)
| The CSC-10 reference point, which exists between the key management server and the group management server, provides a means for the key management server to provide security related information (e.g. encryption keys) to the group management server.
The CSC-10 reference point shall use the HTTP-1 and HTTP-2 reference points and may use the HTTP-3 reference point for transport and routing of security related information to the group management server.
CSC-10 is specified in 3GPP TS 33.180 [25].
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.11 Reference point CSC-11 (between the configuration management client and the configuration management server for configuration while UE is off-network)
| The CSC-11 reference point, which exists between the configuration management client and the configuration management server, provides the configuration information required for MC services while the MC service client is off-network.
The CSC-11 reference point is the same as CSC-4 reference point except that CSC-11 does not support subscription/notification and therefore does not require the use of SIP-1 and SIP-2 reference points.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.12 Reference point CSC-12 (between the group management client and the group management server for configuration while UE is off-network)
| The CSC-12 reference point, which exists between the group management client and the group management server, is used for MC service application signalling for data management of the MC service.
The CSC-12 reference point is the same as CSC-2 reference point except that CSC-12 does not support subscription/notification and therefore does not require the use of SIP-1 and SIP-2 reference points.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.13 Reference point CSC-13 (between the configuration management server and the MC service user database)
| The CSC-13 reference point, which exists between the MC service user database and the configuration management server, is used for:
- the configuration management server to store the user profile data in the specific MC service user database; and
- the configuration management server to obtain the user profile from the specific MC service user database for further configuration in the MC service UE.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.14 Reference point CSC-14 (between the location management client and the location management server)
| The CSC-14 reference point, which exists between the location management client and the location management server, is used by the location management server to receive location information report from location management client.
The CSC-14 reference point uses SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling. The CSC-14 reference point uses the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.15 Reference point CSC-15 (between the location management server and the MC service server)
| The CSC-15 reference point, which exists between the location management server and the MC service server, is used by the MC service server to request and receive location information from location management server. This reference point is also utilized by the location management server to retrieve the group dynamic data (affiliation status) from the MC Service server for a specific MC Service Group ID as well as functional alias status for a specific functional alias.
The CSC-15 reference point uses SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling. The CSC-15 reference point uses the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.16 Reference point CSC-16 (between group management servers in different MC systems)
| The CSC-16 reference point, which exists between two group management servers in different MC systems in different security domains, is used by the group management servers to share group configuration information for MC service groups that can take part in interconnected MC service group calls.
The CSC-16 reference point uses the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling. The CSC-16 reference point uses SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.17 Reference point CSC-17 (between configuration management servers in different MC systems)
| The CSC-17 reference point, which exists between configuration management servers in different MC systems in different security domains, is used by the configuration management servers to share user configuration information for MC service users who are permitted to migrate between the MC systems.
The CSC-17 reference point uses the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.18 Void
| |
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.19 Reference point MCX-1 (between MC service servers)
| The MCX-1 reference point is defined between MC service servers, between MC service servers and MC gateway servers and between MC gateway servers. The MC service servers and MC gateway servers may be located within one MC system or in separate MC systems. Furthermore, the MC service servers may be of the same type or different types.
This MCX-1 reference point is used by MC service servers' coordination procedures (e.g. priority coordination). This reference point is not part of the common service core functionality.
NOTE 1: The MCX-1 corresponds to the MCPTT-3 (see reference 3GPP TS 23.379 [16]) when it is used between MCPTT servers, or between MCPTT server and the MC gateway server, or it corresponds to MCVideo-3 (see reference 3GPP TS 23.281 [4]) when it is used between MCVideo servers, or between MCVideo server and the MC gateway server, or it corresponds to MCData-3 (see reference 3GPP TS 23.282 [5]) when it is used between MCData servers, or between MCData server and MC gateway server.
NOTE 2: The MCX-1 corresponds to the MCPTT-10 (see reference 3GPP TS 23.379 [16]), MCVideo-10 (see reference 3GPP TS 23.281 [4]), or MCData-9 (see reference 3GPP TS 23.282 [5]) when it is used between MC gateway servers in different MCPTT, MCVideo, or MCData system, respectively.
|
6e6efd6b533ddddb98459a905863a4aa | 23.280 | 7.5.2.20 Reference point CSC-19 (between group management server and MC gateway server)
| The CSC-19 reference point, which exists between the group management server and MC gateway server is used by the group management server for subscription and notification signalling related to group configuration information that is shared between MC systems to permit interconnection of MC service group calls.
The CSC-19 reference point uses the SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. The SIP-3 reference point is used when a group management server and an MC gateway server, are served by different SIP cores.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.