Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.289  Word version:  19.3.0

Top   Top   None   None   Next
0…   4…   4.7…   4.7.4…   4.8…   5…   5.4…   6…   6.3…   6.3.2…   7…   7.2.4…   7.3…   7.3.3…   7.3.3.2…   7.3.3.4…   7.3.3.5…   7.3.3.7…   7.3.3.8…   7.3.3.9…   7.3.3.10…   7.3.3.11…   7.3.3.12…   7.3.3.13…   7.4…   7.5…   7.6…   A…

 

0  Introductionp. 9

The use of 5GS to support MC services (i.e., MCPTT defined in TS 23.379, MCVideo defined in TS 23.281, MCData defined in TS 23.282) including common application plane and signalling plane entities is specified in the present document.
Each MC service supports several types of communications amongst the users (e.g. group communication, peer to peer communication). There are several general functions and entities (e.g. configuration, identity) which are used by the MC services. The general functional architecture to support MC services utilizes aspects of the IMS architecture specified in TS 23.228.
An MC service UE in the 5GS context obtains access to a MC service via 3GPP access (i.e., E-UTRA, 5G NR), wireless non-3GPP access (e.g. WLAN or Satellite) and/or wireline access using the 5GS architecture defined in TS 23.501. Certain MC service functions such as dispatch and administrative functions can be supported using MC service UEs with 3GPP access and non-3GPP wireless/wireline access. External applications usage of MC services can be enabled via 3GPP access and/or non-3GPP access.
Up

1  Scopep. 10

The present document specifies the use of the 5G System (5GS) considering common functional architecture, procedures and information flows needed to support mission critical services encompassing the common services core architecture.
The corresponding service requirements applied in TS 22.179, TS 22.280, TS 22.281, TS 22.282 and TS 22.289 also apply here.
The corresponding MC service specific procedures and information flows are defined in TS 23.280, TS 23.379, TS 23.281, TS 23.282 and TS 23.283.
The present document is applicable primarily to mission critical services using 3GPP access (5G NR and/or E-UTRA) and non-3GPP access (WLAN, Satellite and/or wireline) based on the 5GC architecture defined in TS 23.501, TS 23.247 and TS 23.304.
The common functional architecture to support mission critical services can be used for public safety applications and for general commercial applications e.g. utility companies and railways.
Up

2  Referencesp. 10

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.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[3]
TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[4]
TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[5]
TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[6]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[7]
TS 23.501: "System architecture for the 5G System (5GS)".
[8]
TS 23.002: "Network Architecture".
[9]
TS 23.503: "Policy and Charging Control Framework for the 5G System (5GS); Stage 2".
[10]
TS 23.502: "Procedures for the 5G System (5GS)".
[11]
TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
[12]
TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[13]
TS 22.281: "Mission Critical (MC) Video".
[14]
TS 22.282: "Mission Critical (MC) Data".
[15]
TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[16]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[17]
TS 23.304: "Proximity based Service (ProSe) in the 5G System (5GS); Stage 2".
[18]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[19]
TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[20]
TS 23.479: "UE MBMS APIs for Mission Critical Services".
[21]
TS 26.502: "5G Multicast-Broadcast User Service Architecture".
[22]
TS 22.289: "Mobile communication system for railways".
[23]
TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems".
[24]
RFC 9330:  "Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture".
[25]
RFC 6679:  "Explicit Congestion Notification (ECN) for RTP over UDP".
Up

3  Definitions of terms, symbols and abbreviationsp. 11

3.1  Termsp. 11

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
For the purposes of the present document, the following terms given in TS 23.280 apply:
MC service
MC service user
MC service UE
MC system
MC user
For the purposes of the present document, the following terms given in TS 23.247 apply:
MBS session
Broadcast MBS session
Multicast communication service
Multicast MBS session
Broadcast communication service
MBS service area
Up

3.2  Symbolsp. 11

Void.

3.3  Abbreviationsp. 11

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
ECN
Explicit Congestion Notification
L4S
Low Latency, Low Loss and Scalable Throughput
NPN
Non-Public Network
PNI-NPN
Public Network Integrated Non-Public Network
SNPN
Stand-alone Non-Public Network
NID
Network Identifier
Up

Up   Top   ToC