hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.1.2 Procedure for pre-created MBS session and MBS session announcement
| Pre-conditions:
- The MC service server has decided to use an MBS session for MC service group communications associated to a certain MC service group based on transport only mode.
- The MC service server has performed MB-SMF discovery and selection either directly or indirectly, via NEF/MBSF, unless the correspondin... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.1.3 Procedure for dynamic MBS sessions
| In this scenario, the group communication is already taken place and a unicast PDU session is utilized for MC DL transmission. When the MC service server decides to use an MBS session for the transmission under consideration, the MC service server interacts with 5GC to reserve the necessary network resources.
NOTE 1:... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.2 Request for updating MBS resources for group communications
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.2.1 General
| The MC service server can create one or several MBS sessions based on certain service requirements (e.g., QoS profile), a certain service area, or the activity status of multicast MBS sessions. However, during the life cycle of the MBS sessions, the MC service server may need to update the sessions to meet emerging nee... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.2.2 Procedure for updating MBS resources without dynamic PCC rule
| The procedure shown in figure 7.3.3.2.2-1 presents an MBS session update procedure triggered by the MC service server (either directly to the MB-SMF, or indirectly via NEF/MBSF). Within the update request, either the service requirements, MBS service area, activity status of multicast MBS session, or all three are done... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.2.3 Procedure for updating MBS resources with dynamic PCC rule
| The procedure shown in figure 7.3.3.2.3-1 presents an MBS session update procedure triggered by the MC service server to the 5GC, either directly or via NEF/MBSF. Based on the required updates to be done, the MC service server needs to interact with the MB-SMF to update the MBS service area and multicast activity statu... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.3 MBS session deletion request
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.3.1 General
| The MC service server can decide to release a certain MBS session once it is no longer further utilized for the associated MC service group communication, e.g., the MC service group is no longer active, the MC media transmission is over and no further MC media to be delivered, group communication is terminated. The MBS... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.3.2 Procedure
| The procedure in figure 7.3.3.3.2-1 describes the MBS session deletion aspects for group communication.
Pre-conditions:
- MC service clients 1 to n are attached to the 5GS, registered and affiliated to the same active MC service group.
- An MBS session is configured to address the corresponding MC service group w... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.4 Request to activate / de-activate multicast MBS sessions
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.4.1 General
| In case of multicast MBS sessions, the members affiliated to a certain MC group need to initiate a UE session join request towards the 5GC in order to receive the MC media sent via the associated MBS session. The UE session join request enables the reservation of NG-RAN resources for the members of the MC group. Howeve... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.4.2 Multicast MBS session activation procedure
| The procedure shown in figure 7.3.3.4.2-1 presents the multicast MBS session activation procedure triggered by the MC service server.
Pre-conditions:
- MC service clients are attached to the 5GS, registered and affiliated to the same MC service group X.
- The MC service server has directly performed (or via NEF/MB... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.4.3 Multicast MBS session de-activation procedure
| The procedure shown in figure 7.3.3.4.3-1 presents the multicast MBS session activation procedure triggered by the MC service server.
Pre-conditions:
- MC service clients are attached to the 5GS, registered and affiliated to the same MC service group X.
- The MC service server has directly performed (or via NEF/MB... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.5 MC service group media transmissions over 5G MBS sessions
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.5.1 General
| The MC service server can decide to configure an MBS session per MC service group to transmit the media related to the corresponding MC service group communications. Such group communications can comprise different service requirements. For that, multicast and broadcast MBS sessions need to be configured with multiple ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.5.2 Procedure
| The procedure in figure 7.3.3.5.2-1 describes how media related to a specific group communication can be distributed over a configured MBS session which consist of multiple QoS flows, i.e. addressing different service requirements. The procedure is applicable for both the pre-created MBS session case as described in cl... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.6 Aplication level control signalling over 5G MBS sessions
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.6.1 Description
| The MC service server may use an 5G MBS session for application level control signalling. An 5G bearer for application level control signalling is typically used for the purposes beyond the benefit for using 5G for resource efficiency, e.g. for improved MC service performance (KPIs), handling of high load scenarios.
S... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.6.2 Procedure
| The procedure in figure 7.3.3.6.2-1 shows only one of the receiving MC service clients using an 5G MBS session.
Figure 7.3.3.6.2-1: Use of 5G MBS for application-level control signalling
1. The MC service server determines to create MBS session for application-level control signalling, The creation of the 5G MBS se... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.7 Multi-server MBS session coordination
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.7.1 General
| The motivation and principle of supporting Multi-server MBS session coordination is exactly similar to Multi-server eMBMS bearer coordination as described in 3GPP TS 23.280 [3].
NOTE: The procedures in clause 7.3.3.7.2 are only used when MBS session sharing between multiple MC service servers is required. It is implem... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.7.2 Procedures
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.7.2.1 MBS Session coordination independent of media
| The procedure in this sub clause applies to both multicast and broadcast MBS session. The principle and pre-condition are similar with eMBMS bearer coordination as defined in 3GPP TS 23.280 [3].
This procedure is used when two or more MC service servers are serving users in the same area and are configured to share 5G... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.7.2.2 MBS session coordination within one group call
| The procedure in this subclause applies to both multicast MBS session and broadcast MBS session.
The principle is similar to eMBMS bearer coordination within one group call as the following:
- It may be used when two MC service servers are serving users in the same area and are configured to share MBS sessions for th... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8 Service continuity between 5G MBS delivery and unicast delivery
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.1 General
| This clause addresses the issue of MC service media delivery over MBS session, specifically, to maintain the service continuity when switching between 5G MBS delivery and unicast delivery.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.2 Service continuity for broadcast MBS session
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.2.1 General
| The MC service client reports the broadcast reception quality to the MC service server which is used to make the decision whether to use the unicast delivery to the MC service UE(s) which are suffering bad broadcast reception quality due to e.g., move out of the broadcast service area.
An MC service client monitors t... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.2.2 Procedures
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.2.2.1 Service continuity from broadcast to unicast
| The procedure in figure 7.3.3.8.2.2.1-1 illustrates the UE which is receiving media via broadcast MBS session is switched to unicast delivery because the UE suffers from bad broadcast reception quality due to e.g., moving out of the broadcast service area. It shows only one of the receiving MC service clients receiving... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.2.2.2 Service continuity from unicast to broadcast
| The procedure in figure 7.3.3.8.2.2.2-1 illustrates the UE receiving media via unicast delivery being switched to broadcast MBS session as the UE enters the broadcast service area where the NG-RAN is broadcasting the MC service media of the ongoing group communication. The MC service client now is able to receive the b... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.3 Service continuity for multicast MBS session
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.3.1 General
| The MC service server may also switch between multicast and unicast by utilizing application layer mechanisms similar to switching between broadcast and unicast as specified in clause 7.3.3.8.2. If indicated in the MBS session announcement information, the MC service client reports the monitoring state (i.e., the recep... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.4 Path switch between MBS session and 5G ProSe UE-to-network relay
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.4.1 General
| The MC service communications over 5G ProSe UE-to-network relay is supported for unicast delivery.
NOTE: In this release of the specification, service continuity is supported for unicast PDU session over 5G ProSe UE-to-network relay, however it is not yet supported for multicast/broadcast MBS sessions for MC service c... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.4.2 Path switch procedure from MBS session to a 5G ProSe UE-to-network relay
| This clause describes the procedures for path switch from MBS session to a 5G ProSe UE-to-network relay.
Figure 7.3.3.8.4.2-1 illustrates the path switch procedure from MBS session to a 5G ProSe UE-to-network relay.
Figure 7.3.3.8.4.2-1: Path switch from MBS session to a 5G ProSe UE-to-network relay.
1. The DL med... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.8.4.3 Path switch from a 5G ProSe UE-to-network relay to MBS session
| This clause describes the procedure for path switch from a 5G ProSe UE-to-network relay to MBS session.
Figure 7.3.3.8.4.3-1 illustrates path switch from a 5G ProSe UE-to-network relay to MBS session.
Figure 7.3.3.8.4.3-1 Path switch from a 5G ProSe UE-to-network relay to MBS session.
1. The remote MC service clie... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.9 MC service inter-system switching between 5G and LTE
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.9.1 General
| When working in transport only mode, the MC service server guides the MC service clients throughout the MC media transmission for switching between the LTE and 5G systems. For this purpose, the location management client sends location related information to the location management server, similar to the one defined in... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.9.2 Inter-system switching from 5G MBS session to LTE eMBMS bearer
| The procedure provided in figure 7.3.3.9.2-1 describes how the MC service server handles inter-system switching when the MC service UE switches from 5G to LTE network, where the MC service server is able to provide the MC services to the clients over eMBMS bearer(s).
Pre-conditions:
- MC service clients are attached... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.9.3 Inter-system switching from 5G MBS session to LTE unicast bearer
| The procedure provided in figure 7.3.3.9.3-1 describes how the MC service server handles inter-system switching when the MC service UE switches from 5G to LTE network, where the MC service server is unable to provide the MC services to the client over eMBMS bearer.
Pre-conditions:
- MC service clients are attached ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.9.4 Inter-system switching from LTE eMBMS to 5G MBS session
| The procedure provided in figure 7.3.3.9.4-1 describes how the MC service server handles inter-system switching when the MC service UE switches from LTE network to 5G, where the MC service server is able to provide the MC services to the client over 5G MBS sessions (either broadcast or multicast).
Pre-conditions:
-... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.9.5 Inter-system switching from LTE eMBMS to 5G unicast PDU session
| The procedure provided in figure 7.3.3.9.5-1 describes how the MC service server handles inter-system switching when the MC service UE switches from LTE network to 5G, where the MC service server is able to provide the MC services to the client over 5G MBS sessions (either broadcast or multicast).
Pre-conditions:
-... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10 MBS transmission in MCPTT
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.1 General
| MCPTT server can determine to use 5G MBS for the transmission of downlink media for different types of MCPTT group calls.
The application layer signalling such as the floor control messages, application layer paging messages may be transmitted along with the MC media over the same MBS session however with different Q... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.2 Call connect and disconnect over MBS session procedures
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.2.1 General
| MBS session can be used for MCPTT group calls. One MBS session may be not permanently associated to one specific group or group call.
NOTE: It is implementation-specific that one MBS session can be re-assigned to different groups, or is associated to only one group.
The procedure in clause 7.3.3.10.2 requires that t... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.2.2 Procedure
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.2.2.1 Group call connect over MBS session
| Pre-conditions:
- The MCPTT clients 1 to n are attached to the 5GS, registered and affiliated to the same MCPTT group X.
- The MCPTT server has directly performed (or via NEF/MBSF) an MB-SMF discovery and selection, unless the corresponding information is locally configured.
- The MCPTT server has decided to use a... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.2.2.2 Group call disconnect from MBS session
| Figure 7.3.3.10.2.2.2-1 presents the procedure for a group communication call disconnect over broadcast and multicast MBS sessions.
Figure 7.3.3.10.2.2.2-1: Group call disconnect over broadcast and multicast MBS sessions.
1. The MC group communication is taking place over the associated MBS session. MCPTT client 1 ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.3 Enhanced MCPTT group call setup procedure with 5MBS
| Enhanced MCPTT group call setup procedure with eMBMS bearer is specified in clause 10.10.6 of 3GPP TS 23.379 [6]. When using mission critical services over 5G MBS, the application paging message transported over 5G MBS session should also be supported.
The related procedures and information flow are as specified in 3G... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.10.4 Downlink media transmission with 5MBS
| The MCPTT service shall support the procedure for using pre-created MBS session, or dynamic MBS session as specified clause 7.3.3.1.
MCPTT may use MBS session for the different types of MCPTT group calls. Both pre-arranged group calls and chat group calls can use the pre-created 5G MBS session for distributing the me... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11 MBS transmission in MCVideo
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.1 General
| MCVideo server can determine to use 5G MBS for the transmission of DL link media for different types of MCVideo group calls.
The application layer signalling such as the transmit media request and transmit media granted messages, may be transmitted along with the MC media over the same MBS session however with differe... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.2 Call connect and disconnect over MBS session procedures
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.2.1 General
| MBS session can be used for MCVideo group calls. One MBS session may not be permanently associated to one specific group or group call.
NOTE: It is implementation-specific that one MBS session can be re-assigned to different groups, or is associated to only one group.
The procedure in clause 7.3.3.11.2.2 requires th... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.2.2 Procedure
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.2.2.1 Group call connect over MBS session
| Figure 7.3.3.11.2.2.1-1 presents the procedure for a group communication, in specific, video call connects over either broadcast or multicast MBS sessions.
Pre-conditions:
- The MCVideo clients 1 to n are attached to the 5GS, registered and affiliated to the same MCVideo group X.
- The MCVideo server has directly... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.2.2.2 Group call disconnect from MBS session
| Figure 7.3.3.11.2.2.2-1 presents the procedure for a group call disconnect over broadcast and multicast MBS sessions.
Figure 7.3.3.11.2.2.2-1: Group call disconnect from MBS session
1. The MC group call is taking place over the associated MBS session. MCVideo client 1 is sending the MC media over a unicast PDU sess... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.3 Switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer for MCVideo
| The MCVideo service shall support the procedure for switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer and LTE unicast bearer as specified in clause 7.3.3.8 and clause 7.3.3.9 with the following clarifications:
- The MC service client is the MCVideo client;
- The MC service server is the MCVid... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.11.4 DL media transmission with 5MBS for MCVideo
| The MCViedo service shall support the procedure for using pre-created MBS session, or dynamic MBS session as specified clause 7.3.3.1.
MCVideo may use pre-created MBS session for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the pre-created MBS session for distr... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12 MBS transmission in MCData
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.1 General
| The procedures and information flows for Short data service and file distribution of MC Data group are defined in 3GPP TS 23.282 [5].
When using 5G MBS, MCData server can determine to use either pre-created MBS session or dynamic MBS session as defined in clause 7.3.3.1 for the transmission of DL link media for differ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.2 Usage of MBS session for MCData
| The MCData service shall support the procedure for using pre-created MBS session or dynamic MBS session as specified in Clause 7.3.3.1 with the following clarifications:
- The MC service client is the MCData client;
- The MC service server is the MCData server; and
- The MC service ID is the MCData ID.
When using t... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.3 Switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer for MCData
| The MCData service shall support the procedure for switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer or eMBMS bearer as specified in clause 7.3.3.8 and clause 7.3.3.9 with the following clarifications:
- The MC service client is the MCData client;
- The MC service serv... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.4 Group communication connect and disconnect over MBS session procedures
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.4.1 General
| MBS session can be used for MCData group communication. One MBS session may be not permanently associated to one specific group or group communication.
NOTE: It is implementation-specific that one MBS session can be re-assigned to different groups, or is associated to only one group.
The procedure in clause 7.3.3.12... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.4.2 Procedure
| The procedure specified in this clause is applicable (for the group communication establishment) for Group standalone short data service using media plane as described in clause 7.4.2.6 in 3GPP TS 23.282 [5] and for Group short data service session as described in clause 7.4.2.7 in 3GPP TS 23.282 [5].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.4.2.1 Group communication connect over MBS session
| Pre-conditions:
- The MCData clients 1 to n are attached to the 5GS, registered and affiliated to the same MCData group X.
- The MCData server has directly performed (or via NEF/MBSF) an MB-SMF discovery and selection, unless the corresponding information is locally configured.
- The MCData server has decided to u... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.4.2.2 Group communication disconnect from MBS session
| Figure 7.3.3.12.4.2.2-1 presents the procedure for a group communication disconnect over broadcast and multicast MBS sessions.
Figure 7.3.3.12.4.2.2-1: Group communication disconnect over broadcast and multicast MBS sessions.
1. The MC group communication is taking place over the associated MBS session. MCData clie... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.12.5 Downlink media transmission with 5MBS
| The MCData service shall support the procedure for using pre-established MBS session, or dynamic MBS session as specified in clause 7.3.3.1.
MCData may use MBS session for the different types of sub-services. Both SDS and FD can use the pre-established MBS session or dynamic MBS session for distributing the data.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.13 Use of FEC to protect 5G MBS transmissions
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.13.1 General
| Application layer FEC can be used to recover the packet losses when delivering a MC service over 5G MBS, to reach its required level of QoS.
The support of FEC is optional for the MC service servers and MC service clients. FEC can be optionally applied by the MBSTF, if required by the MC service server (as specified i... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.13.2 FEC encoding by the MBSTF
| In this procedure, depicted in figure 7.3.3.13.2-1, the MC service server asks the MBSF/MBSTF to apply FEC to a set of media, transported by a 5G MBS session, using the Setup FEC request.
This procedure can be applied when using pre-created MBS session and session announcement (as specified in clause 7.3.3.1.2) or usi... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.4 Support of Multicast MBS session reception in RRC_INACTIVE state
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.4.1 General
| Multicast MBS reception in RRC_INACTIVE mode enables a higher number of UEs in a cell to participate in public safety group calls using MBS sessions. The MC service server may indicate to the 3GPP core network that a UE is preferred to be kept in RRC_CONNECTED state when the related MBS session which the UE joined is a... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.4.2 Provisioning of the MBS assistance information
| After the MC service server has obtained the MBS Session ID of a multicast MBS Session via the TMGI allocation or the MBS session creation procedure, and the MBS session is mapped to a certain MC group, the MC service server may provision the MBS assistance information of a UE to the 5GC as described in 3GPP TS 23.247 ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.4 MC services over 5GS supporting EPS interworking
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.4.1 General
| MC services over a 5G system supporting EPS interworking are provided to 5GS/EPS capable MC service UEs as defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], and 3GPP TS 23.503 [9].
This clause describes procedures related to the support of MC services over a 5G system with EPS interworking.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.4.2 Inter-system mobility
| As specified in 3GPP TS 23.501 [7], a dedicated user plane anchor point, i.e. UPF + PGW-U function, is defined for interworking between 5GS and EPS. This enables that the network can directly handle PDU sessions (in 5GS) and PDN connections (in EPS) associated to MC service sessions of an MC service UE during inter-sys... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.4.3 Network notifications of EPS interworking related events
| In the case of MC services provided over a 5GS supporting EPS interworking, the MC service server may not be able to identify whether an MC service UE is registered on 5GS or EPS. Therefore, the MC service server can subscribe/unsubscribe to receive notifications of specific events from the network. These notifications... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5 Enhancements for Location management over 5GS
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.1 General
| In addition to the location management functions defined in 3GPP TS 23.280 [3], the location management system over 5GS shall support the following enhancement:
- Inter-system RAT changes event triggering and report as described in clause 7.3.3.9.1.
- Serving and neighbouring 5G NR Cell Global Identifiers (NCGI) as o... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.2 Information flows for location information
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.2.1 General
| In this clause, only those information flows which requires enhancement to 3GPP TS 23.280 [3] for MC services over 5G specific are included.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.2.2 Location reporting configuration
| Table 7.5.2.2-1 describes the information flow from the location management server to the location management client for the location reporting configuration.
Compared to that is defined in 3GPP TS 23.280 [3], the following changes are made:
- Allowing the location management server to configure location reporting by... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.2.3 Location information report
| Table 7.5.2.3-1 describes the information flow from the location management client to the location management server for the location information reporting.
Compared to that is defined in 3GPP TS 23.280 [3], the following changes are made:
- Allowing the location management client to report the the inter-RAT informat... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.3 Procedure
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.3.1 General
| In this clause, only the procedure which requires enhancement to 3GPP TS 23.280 [3] for MC services over 5G specific are included.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.5.3.2 Event-triggered location reporting procedure
| NOTE 1: This procedure is valid for single MC system operation only.
The location management server provides location reporting configuration to the location management clients, indicating what information the location management server expects and what events will trigger the sending of this information to the locati... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.6 MC service over 5G ProSe
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.6.1 Off network group communication for MC service
| The procedures and information flows used in 3GPP TS 23.280 [3], 3GPP TS 23.379 [6], 3GPP TS 23.281 [4], and 3GPP TS 23.282 [5] are reused for Off network group communication for MC service over 5G ProSe with following differences:
- The ProSe discovery Group ID is not used for off-network group communication via 5G P... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.6.2 Off-network private communication
| The procedures and information flows used in 3GPP TS 23.280 [3], 3GPP TS 23.379 [6], 3GPP TS 23.281 [4], and 3GPP TS 23.282 [5] are reused for off‑network private communication for MC service over 5G ProSe with following differences:
- PPPP (ProSe Per-Packet Priority) is replaced with PQI, as specified in 3GPP TS 23.3... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.6.3 Use of 5G ProSe UE-to-network relay
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.6.3.1 5G ProSe UE-to-network relay service authorization
| The MC service shall support the capability for 5G ProSe UE-to-network relay to restrict the relayed group communication on a per group basis by using the relay service codes corresponding to the group.
5G ProSe (as specified in 3GPP TS 23.304 [17]) supports layer 2 UE-to-network relay and layer 3 UE-to-network relay.... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.6.3.2 UE-to-network relay MC service
| The 5G ProSe UE-to-network relay provides a layer 2 or layer 3 routing service (as specified in 3GPP TS 23.304 [17]) for a 5G ProSe remote UE, when the MC service user on the 5G ProSe remote UE requires to access the MC service via a 5G ProSe UE-to-network relay.
The application layer signalling for the MC service use... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.7 MCVideo enhancement with ECN marking for L4S
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.7.1 General
| These clauses specify the procedure for the MCVideo communication (e.g., video pull from server) enhancement with ECN marking for L4S (L4S is defined in IETF RFC 9330 [24]).
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.7.2 Information flows
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.7.2.1 L4S feedback report
| Table 7.7.2.1-1 defines the L4S feedback report from MCVideo client to MCVideo server to provide DL L4S feedback information, and from the MCVideo server to the MCVideo client to provide UL L4S feedback information.
Table 7.7.2.1-1: L4S ECN feedback report
Information element
Status
Description
MCVideo ID
M
Ide... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.