hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.1.1.7 MBS Session Update with PCC
| For local multicast services and location dependent multicast services, the AF may perform a Service Announcement towards UEs to update the MBS service area before the MBS Session Update procedure is started or after the MBS Session Update procedure is completed.
Figure 7.1.1.7-1: MBS Session Update with PCC
1-2. S... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.1.2 MB-SMF discovery and selection for multicast/broadcast session
| To facilitate the MB-SMF discovery/selection for one multicast/broadcast MBS session, the following mechanism is used:
- The MB-SMF registers its capability related to Multicast/Broadcast Service session management (e.g. S-NSSAI(s) and the associated NSI ID(s) (if available), DNN(s), TMGI range, service area) as part ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.1.3 MB-UPF discovery and selection for multicast/broadcast session
| The selection and reselection of the MB-UPF are performed by the MB-SMF by considering MB-UPF deployment. For the local Broadcast/Multicast MBS session and location dependent MBS session, the service area is taken into consideration for MB-UPF selection.
MB-SMF may be locally configured with the information about the ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2 MBS procedures for multicast Session
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.1 MBS join and Session establishment procedure
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.1.1 General
| MBS Session Join procedure is used by UEs to inform the 5GC of the UE interest in joining a multicast MBS session. The first accepted UE join request will trigger the multicast MBS session establishment towards the NG-RAN and the UE.
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.1.2 Establishment of a PDU Session that can be associated with multicast session(s)
| The PDU Session associated with Multicast MBS session(s) (i.e. the associated PDU Session) is established using the procedures as specified in TS 23.502 [6] clause 4.3.2.2 with the following differences:
NOTE 1: The DNN and S-NSSAI are used to establish the PDU session which can carry the operations related to Multica... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.1.3 Multicast session join and session establishment procedure
| The following steps are executed before the UE requests to join the MBS session:
- The MBS Session may have been created in the 5GC (see clause 7.1.1 for details).
- The UE registers in the PLMN or SNPN and may have established a PDU session that can be associated with multicast session(s).
- The UE has known at lea... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.1.4 Establishment of shared delivery toward RAN node
| In the following cases, the shared tunnel for shared delivery is established between the NG-RAN and MB-UPF:
- The first UE is included in the context of the MBS session in the NG-RAN.
NOTE 1: When the multicast MBS session is inactive, if there is at least one UE joining the multicast MBS session is in RRC_CONNECTED ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.2 Multicast MBS Session leave and Multicast MBS Session release procedure
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.2.1 General
| This clause describes Multicast MBS Session leave requested by the UE or by the network. This clause also describes Multicast MBS Session release.
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.2.2 Multicast Session leave requested by the UE
| When the UE determines to leave the Multicast MBS session, it shall send PDU session Modification request to inform the 5GC the leaving operation. The Figure 7.2.2.2-1 describes the procedure.
Figure 7.2.2.2-1: UE initiated Multicast MBS Session leave
1. The UE sends the PDU Session Modification Request when the UE... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.2.3 Multicast session leave requested by the network or MBS session release
| This procedure applies to the following scenarios:
1. When the MB-SMF decides to release an MBS Session:
- based on a request from the AF (directly or via the NEF/MBSF);
In this scenario, the MB-SMF notifies the SMF of multicast session release, and the SMF initiates procedures to remove all joined UEs from the MBS... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.2.4 Release of shared delivery toward RAN node
| In the following case, the shared delivery tunnel may be released between NG-RAN and MB-UPF:
- The last UE is excluded from the context of the multicast MBS session in the NG-RAN node;
- Handover to the target NG-RAN when the UE is the last UE for this multicast MBS session in the source NG-RAN node during handover p... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3 Mobility Procedures for MBS
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.1 General
| UE may move from one NG-RAN node to another NG-RAN node after UE has joined the MB Session. There are various mobility scenarios possible, depending on whether one of the involved NG-RAN nodes supports MBS.
During an active MBS Session, mobility between an NG-RAN supporting MBS and an NG-RAN node not supporting MBS re... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.2 Xn based handover from MBS supporting NG-RAN node
| This clause describes an Xn based handover with MBS traffic delivered to the UE at the source NG-RAN node supporting MBS.
Figure 7.2.3.2-1: Xn based handover with MBS Session
The following additions apply compared to clause 4.9.1.2 of TS 23.502 [6]:
Before Handover:
The source NG RAN has been provided with MBS Se... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.3 N2 based handover from MBS supporting NG-RAN node
| This clause describes the N2 based handover with MBS traffic delivered to the UE at the source NG-RAN node supporting MBS.
Figure 7.2.3.3-1: N2 based handover with MBS Session
The following additions apply compared to clause 4.9.1.3 of TS 23.502 [6]):
1. Source NG-RAN to S-AMF: Handover Required (RAN container (MB... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.4 Xn/N2 based handover from non-MBS supporting NG-RAN node
| When the UE has joined the multicast MBS session and the source NG-RAN node does not support MBS, the 5GC Individual MBS traffic delivery method is used for the multicast MBS session data delivery. When the Xn/N2 based handover procedure is triggered, the UE is handed over to the target NG-RAN node per existing Xn /N2 ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.5 Minimization of data loss
| To minimize data loss of a multicast MBS session during the handover procedure the following functions apply:
- For each MBS QoS flow, the MB-UPF adds a sequence number in each data packet of the MBS session sent by the MB-UPF and forwarded to all related NG-RAN nodes and UPFs via GTP-U tunnel. When the UPF forwards t... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.6 Xn/N2 based handover for inactive MBS session
| If the MBS session is in Inactive state, the following differences apply as compared to the handover procedures for the MBS session in Active state:
- The target NG-RAN is provided with the MBS session ID, but is not provided with Active MBS Session Information by the source NG-RAN as specified in TS 38.423 [24] and i... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.7 Connection Resume in RRC_INACTIVE procedure
| If an MBS session is in Inactive state, the UE may be in CM-CONNECTED with RRC_INACTIVE state. If an MBS Session is in Active state, the UE may also be in CM-CONNECTED with RRC_INACTIVE state as specified in clause 16.10.5.2 of TS 38.300 [9].
The UE may resume the connection in a different NG-RAN node as specified in ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.8 Mobility procedures to enable delivery of multicast MBS session data to UEs in RRC_INACTIVE state
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.8.1 General
| The procedures in clauses 7.2.3.2, 7.2.3.3, 7.2.3.4, 7.2.3.6 and 7.2.3.7 apply with the following additions:
- During Xn handover, if the target NG-RAN node support MBS multicast with reception in RRC_INACTIVE state, it indicates to the SMF in the N2 SM information in the Path Switch Request message that it supports M... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.8.2 Mobility of UE in RRC_INACTIVE state receiving MBS data within RNA
| When a UE in RRC_INACTIVE state is receiving ongoing MBS session data and moves to a new cell within the RNA, the UE may receive the MBS session data in RRC_INACTIVE state or resume the connection as specified in TS 38.300 [9].
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.8.3 Mobility of UE in RRC_INACTIVE state receiving MBS data out of RNA and within RA
| When a UE in RRC_INACTIVE state is receiving multicast MBS session data, if the UE moves out of the RNA and within the RA, the UE resumes the connection in the same way as specified in clause 7.2.3.7.
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.3.8.4 Mobility of UE in RRC_INACTIVE state receiving MBS data out of RA
| When the UE in RRC_INACTIVE receiving multicast MBS session data, if the UE moves out of the RA, the UE initiates the Mobility Registration Update procedure to activate the associated PDU session(s) as specified in clause 4.2.2.2.2 of TS 23.502 [6]. Hence the shared delivery (if not already established) or the individu... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4 Support of Local multicast service and Location dependent multicast service
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.1 General
| The clause captures the procedural enhancement to support Location dependent MBS service and the Local MBS service described in clause 6.2.
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2 Support of location dependent multicast service
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.0 Creation for location dependent MBS session
| For location dependent MBS, the MBS session creation procedure is performed as defined in clause 7.1.1.2 with the following additions and difference:
- Multiple AFs may start the same Multicast MBS session with different content in different MBS service areas. The AF (or NEF/MBSF if involved) selects MB-SMF for differ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.1 UE join location dependent Multicast MBS session and establishment procedure
| The location dependent multicast session join and establishment procedure is performed as defined in clause 7.2.1 with the following additions:
- The location dependent Multicast MBS session is created as described in clause 7.2.4.2.0.
- The UE may have information about the location dependent multicast service inclu... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.2 Void
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.3 Handover procedure
| The Handover procedure for the UE is performed as defined in clause 7.2.3.2, 7.2.3.3, and 7.2.3.4 with the following additions:
- If the UE is receiving multicast data corresponding to the MBS Session ID and Area Session ID via the 5GC Shared MBS traffic delivery from cells served by the Source NG-RAN before the hando... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.4 Activation of location dependent MBS session
| When the location dependent MBS session is activated, the MBS session is activated in the whole MBS service area of the MBS session. It is not supported that the same MBS session is in Active state in one MBS service area but in Inactive state in another MBS service area.
NOTE: As an exception, if the MBS session cont... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.5 UE location change handling within the same NG-RAN node between cells belonging to different MBS service areas during Individual delivery
| If UE has moved out of the MBS service area corresponding to the original Area Session ID, the SMF checks whether UE is in MBS service area corresponding to a new Area Session ID within the same MBS session:
- For the case UE is out of the original MBS service area but in another MBS service area of the MBS session:
... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.6 UE location change handling by SMF
| When the SMF receives a notification about a UE location change or is becoming aware of a UE location change (e.g. during handover, Mobility Registration Update and Service Request procedures), the SMF checks whether the new UE location is inside or outside all MBS service areas of the location dependent MBS session:
... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.7 UE mobility within the same NG-RAN between cells belonging to different MBS service areas for shared delivery
| When the UE moves from one service area to another served by the same NG-RAN, the NG-RAN node that supports MBS handles content switching due to mobility between service areas it serves without interaction with SMF. If it is the first that UE enters a new location area the RAN node requests shared delivery from the MB-... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.8 Void
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.2.9 Connection Resume procedure
| The Connection Resume procedure for the UE is performed as defined in clause 7.2.3.7 with the following additions:
- For an MBS-supporting target NG RAN
- The target RAN node obtains MBS session information including an area session ID from the source RAN node (during the connection retrieval) or the SMF and initiate... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3 Support of local MBS for multicast
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.1 Local MBS service area information provided by AF
| For local multicast services, the MBS service area information is provided to the UE and the 5GC as specified in clauses 7.1.1.2 and 7.1.1.3 with the following differences and clarifications:
- For the Service Announcement, MBS service area information is included unless it is preconfigured.
- When performing the MBS... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.2 Multicast session join and session establishment procedure for local MBS
| For the case that the multicast service is only available within a limited area, the UEs outside the MBS service area are not allowed to join the multicast service.
The Multicast MBS session join and session establishment for multicast service available within a limited area are performed as specified in clause 7.2.1.... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.3 Handover procedure with local MBS session
| The Handover procedure for the UE is performed as defined in clause 7.2.3 with the following additions:
- If the UE is camping at the Source RAN node and receiving multicast data corresponding to the MBS Session ID via the 5GC Shared MBS traffic delivery before the Handover, for Xn based handover in clause 7.2.3.2, th... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.4 Activation of local MBS session
| For the local MBS session activation, the differences comparing to the procedure defined in clause 7.2.5.2 are as below.
- The SMF invokes Namf_MT_EnableGroupReachability service operation to AMF, which include the MBS service area associated with the MBS session.
- For the UE in CM-IDLE state, when the AMF triggers ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.5 UE location change handling by SMF
| When the SMF receives a notification about a UE location change or is becoming aware of a UE location change (e.g. during handover, Mobility Registration Update and Service Request procedures), the SMF checks whether the new UE location is inside or outside the MBS service area of the MBS session.
- For the case UE is... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.6 UE mobility within the same NG-RAN between cells in or out of the MBS service area
| If UE mobility can happen within the same NG-RAN between cells in or out of the service area,
- The NG-RAN detects whether the UE is IN or OUT of an MBS service area and notifies the SMF if the UE moves in or out of the MBS service area.
NOTE: When the UE joins, the SMF subscribes to the "Area Of Interest" event (see... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.7 Void
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.4.3.8 Connection Resume procedure with local MBS session
| The Connection Resume procedure for the UE is performed as defined in clause 7.2.3.7 with the following additions:
- The source RAN, if supporting MBS and if the MBS session is active, provides MBS service area to the target RAN during the UE Context Retrieval procedure;
- An MBS supporting target RAN then applies th... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.5 MBS session activation and deactivation
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.5.1 General
| MBS Session activation procedure is for multicast only. MBS Session activation procedure is triggered by MB-SMF, when it receives the notification from MB-UPF for the downlink MBS DL data, or when it receives the request directly from AF or via NEF. The MBS Session activation procedure is used for activating the resour... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.5.2 MBS session activation procedure
| The following can trigger the MBS session activation procedure:
- AF requests MB-SMF to activate the MBS session;
- MB-UPF receives the multicast data and notifies MB-SMF.
Figure 7.2.5.2-1: MBS session activation procedure
In this procedure, steps 11 to 15 are executed if the MB-SMF finds out there are shared tun... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.5.3 MBS session deactivation procedure
|
Figure 7.2.5.3-1: MBS session deactivation procedure
In this procedure, steps 3 to 4 and steps 5 to 9 are executed in parallel.
1. The procedure may be triggered by the following events:
- When MB-UPF detects there is no data receives for the MBS Session, MB-UPF sends MB-N4 Notification (N4 Session ID) to the MB-S... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.6 Multicast session update procedure
| Multicast MBS session update procedure is invoked by the AF to update the service requirement (result in multicast QoS parameters update and/or multicast QoS flow addition/removal) and/or MBS Service Area for an ongoing Multicast MBS session.
If the MBSF acts as the MBS security function for multicast as defined in TS... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.7 Void
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.8 Service request procedure
| If the multicast MBS session is in Inactive state, the UE can go to CM-IDLE state or the user plane of the associated PDU Session may be deactivated even when the UE is in CM-CONNECTED state. When user plane of the associated PDU session is activated again, the SMF sends the MBS session information to NG-RAN during Ser... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.9 AF provisioning multicast MBS Session Authorization information
| The AF provisions the multicast MBS session authorization information for multicast MBS sessions that are not open to "any UE". The procedure specified in clause 4.15.6.2 of TS 23.502 [6] is reused with the following enhancements:
- The AF may provision the MBS Session Authorization information to the 5GC. The MBS Ses... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.2.10 Multicast MBS procedures for UEs using power saving functions
| For a UE using power saving function to receive multicast MBS Session data, the following applies:
- For an multicast MBS session, a UE needs to join the multicast session as defined in clause 7.2.1.3 prior to MBS data reception. To join the multicast session, the UE needs to be in RRC_CONNECTED state. The UE may sele... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3 MBS procedures for broadcast Session
| NOTE: The interactions between the MBSF, the MBSTF and the AF, for example file delivery and HTTP adaptive streaming, will be defined in TS 26.502 [18] and TS 26.517 [22].
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.1 MBS Session Start for Broadcast
| The Broadcast MBS Session Start follows the common procedure specified in clause 7.1.1.2 or clause 7.1.1.3, which consist of TMGI Allocation and MBS Session Create. It is possible for AF to allocate TMGI once but create the MBS Session for multiple times. A combined procedure to perform both TMGI allocation and MBS Ses... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 0 Based on OAM configuration, RAN nodes announce in SIBs over the radio interface information about the MBS FSA IDs and frequencies of neighbouring cells.
| 1. To establish broadcast MBS session, the AF performs TMGI allocation and MBS session creation as specified in clause 7.1.1.2 or 7.1.1.3. The MBS service type indicates to be broadcast service. The MBS FSA ID(s) of a broadcast MBS session are communicated in the service announcement towards the UE. The UE compares tho... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.2 MBS Session Release for Broadcast
| The MBS Session Release for broadcast follows the MBS Session Deletion (e.g. TMGI De-allocation and MBS Session Deletion) so that resource for shared MBS delivery is released. It is possible for AF to stop MBS Session but keep TMGI allocated.
Figure 7.3.2-1: MBS Session Release for Broadcast
1. The AF/AS may stop t... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.3 MBS Session Update for Broadcast
| The MBS Session Update for broadcast is used by the AF to update the broadcast area or service requirements of the MBS Session which may lead to addition of new MBS QoS Flow(s), removal of existing MBS QoS Flow(s) or update of existing MBS QoS Flow(s).
Figure 7.3.3-1: MBS Session Update for Broadcast
1. The AF star... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.4 Support for Location dependent Broadcast Service
| The clause describes procedures to support the Location dependent broadcast service as described in clause 6.2.
The MBS session creation procedure is performed as defined in clause 7.1.1.2 with the following additions:
- Multiple AFs may start the same Broadcast MBS session with different content in different MBS ser... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.5 MBS Session Delivery Status Indication for Broadcast
| The MBS Session Delivery Status Indication for broadcast is used by the MB-SMF to notify the AF/AS of conditions affecting the delivery of the MBS session (e.g. MBS session created, MBS session terminated, etc.). The occurrence of the indicated condition may have been detected at the MB-SMF or may have been reported to... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.6 Broadcast MBS Session Release Require
| When NG-RAN is not able continue to provide the Broadcast MBS Session, e.g. due to lack of radio resources, NG-RAN may initiate Broadcast Session Release Require procedure.
Figure 7.3.6-1: Broadcast MBS Session Release Require
1. If NG-RAN cannot continue to provide the Broadcast MBS session, e.g. due to lack of ra... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.7 Transport change for resource sharing across broadcast MBS Sessions during network sharing
| The procedure in this clause is performed when one of the following events occur and resource sharing across broadcast MBS Sessions in network sharing as specified in clause 6.18 is applied:
- When a broadcast MBS session, from which the shared NG-RAN receives a DL MBS data stream, is released, and the NG-RAN node det... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.3.8 Broadcast MBS procedures for UEs using power saving functions
| For a UE using power saving function to receive broadcast MBS Session data, the following apply:
- If a UE is in RRC_CONNECTED mode due to other reasons at the start time or the scheduled activation times, the UE follows normal connected mode procedures.
- If a UE is in RRC_IDLE state and reachable (e.g. in active ti... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.4 MBS procedures for inter System Mobility
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.4.1 Inter-system mobility with interworking at service layer
| For inter-system mobility with interworking at service layer, i.e. the same multicast service is provided via eMBMS in E-UTRAN and MBS, the UE is instructed to switch between MBS and eMBMS:
NOTE 1: The source network can be configured with the frequencies where the same service is provided in the target network, i.e. ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.5 MBS procedures for Group Message Delivery
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.5.1 Group Message Delivery via MBS Broadcast
|
Figure 7.5.1-1: Group Message Delivery via MBS Broadcast
NOTE 1: The steps in this clause for group message delivery to the UE(s) follow the procedures specified in TS 26.502 [18], where the NEF acts as an MBS Application Provider.
1. The AF sends Nnef_MBSGroupMsgDelivery_Create Request to the NEF. The Request mess... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.5.2 Modification of previously submitted Group message
|
Figure 7.5.2-1: Modify Group Message Delivery via MBS Broadcast
NOTE: The steps in this clause for modification of group message delivery to the UE(s) follow the procedures specified in TS 26.502 [18], where the NEF acts as an MBS Application Provider.
1. The AF sends Nnef_MBSGroupMsgDelivery_Update Request to the ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 7.5.3 Cancellation of previously submitted Group message
|
Figure 7.5.3-1: Cancelling Group Message Delivery via MBS Broadcast
NOTE: The steps in this clause for cancelling the group message delivery to the UE(s) follow the procedures specified in TS 26.502 [18] where the NEF acts as an MBS Application Provider.
1. The AF sends Nnef_MBSGroupMsgDelivery_Delete Request (Grou... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 8 Control and user plane stacks
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 8.1 Control plane for Multicast and Broadcast services
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 8.1.1 General
| The control plane protocol stacks for Multicast and Broadcast service between NG-RAN and MB-SMF is defined in the clause 8.1.1 and the other control plane protocol stacks for Multicast and Broadcast service are defined in the TS 23.501 [5] clause 8.2.
The control plane protocols for N4mb reference point between MB-SMF... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 8.1.2 NG-RAN – MB-SMF
|
Legend:
- N2 SM information: This is the subset of NG-AP information that the AMF transparently relays between the NG-RAN and the MB-SMF, and is included in the NG-AP messages and the N11mb related messages, where the NG-RAN node has MBS capability and in this Release the NG-RAN is a 3GPP NR.
Figure 8.1.1-1: Cont... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 8.2 User plane for Multicast and Broadcast services
| The User plane protocol stack for PDU session which handles the multicast operation is same with the PDU session user plane Protocol Stack defined in the TS 23.501 [5] clause 8.3.1.
The user plane protocol stack for MBS session in case of shared delivery is described in Figure 8.2-1 and Figure 8.2-2. In Figure 8.2-1, ... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9 Network Function Services
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1 MB-SMF Services
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.1 General
| The following table illustrates the MB-SMF Services for MBS.
Table 9.1.1-1: NF services provided by MB-SMF
Service Name
Service Operations
Operation
Semantics
Example Consumer (s)
Nmbsmf_TMGI
Allocate
Request/Response
NEF, MBSF, AF
Deallocate
Request/Response
NEF, MBSF, AF
ContextStatusSubscribe
SM... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.2 Nmbsmf_TMGI service
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.2.1 General
| Service description: NF Service Consumer can use this service to request the allocation of TMGIs and release allocated TMGIs.
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.2.2 Nmbsmf_TMGI_Allocate service operation
| Service operation name: Nmbsmf_TMGI_Allocate
Description: This service is used by the NF Service Consumer to request the allocation of TMGI(s) or request to refresh previously allocated TMGI(s).
Inputs, Required: Number of TMGIs.
Inputs, Optional: TMGI(s) for which the expiry time is to be extended).
Outputs, Requi... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.2.3 Nmbsmf_TMGI_Deallocate service operation
| Service operation name: Nmbsmf_TMGI_Deallocate
Description: NF Service Consumer can use this service to request the release of TMGI(s).
Inputs, Required: TMGI(s).
Inputs, Optional: None.
Outputs, Required: Success or not.
Outputs, Optional: None.
|
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3 Nmbsmf_MBSSession service
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.1 General
| Service description: The following are the key functionalities of this NF service:
- (between AMF or SMF and MB-SMF) For multicast, NF Service Consumer can use this service to request the reception of MBS data or to terminate the reception of MBS data of a Multicast MBS session, or for a location dependent Multicast M... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.2 Nmbsmf_MBSSession_ContextUpdate service operation
| Service operation name: Nmbsmf_MBSSession_ContextUpdate
Description: NF Service Consumer can use this service to request or terminate the reception of data of a multicast session, or for a location dependent MBS session, related to the part of the MBS session within a service area.
Inputs, Required: MBS Session ID, i... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.3 Nmbsmf_MBSSession_ContextStatusSubscribe service operation
| Service operation name: Nmbsmf_MBSSession_ContextStatusSubscribe
Description: Service Consumer NF can use this service operation to request information (e.g. QoS information) about a multicast session and to subscribe to notification of events about the multicast session context.
Inputs, Required: MBS Session ID, Not... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.4 Nmbsmf_MBSSession_ContextStatusNotify service operation
| Service operation name: Nmbsmf_MBSSession_ContextStatusNotify
Description: This service operation, which is applicable to multicast MBS session, is used by the MB-SMF to notify its consumers about events of an MBS Session, or for a location dependent MBS session, related to a service area change.
Inputs, Required: MB... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.5 Nmbsmf_MBSSession_ContextStatusUnsubscribe service operation
| Service operation name: Nmbsmf_MBSSession_ContextStatusUnsubscribe
Description: This service operation, which is applicable to multicast MBS session, is used by the consumer to unsubscribe to notifications about MBS context events.
Inputs, Required: MBS Session ID.
Inputs, Optional: None.
Outputs, Required: Operati... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.6 Nmbsmf_MBSSession_Create service operation
| Service operation name: Nmbsmf_MBSSession_Create
Description: Create a new multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. Optionally subscribe to notifications for this MBS session.
Input, Required: MBS Session ID (SSM or TMGI) or TM... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.7 Nmbsmf_MBSSession_Update service operation
| Service operation name: Nmbsmf_MBSSession_Update
Description: Update the established multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area, e.g. QoS update.
Input, Required: MBS Session ID.
Input, Optional: MBS Service Information (as defin... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.8 Nmbsmf_MBSSession_Delete service operation
| Service operation name: Nmbsmf_MBSSession_Delete
Description: Release the multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. The MBS session is deleted and the subscription (if any) to notifications about events related to the status of t... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.9 Nmbsmf_MBSSession_StatusNotify service operation
| Service operation name: Nmbsmf_MBSSession_StatusNotify
Description: This service operation is used by the MB-SMF to notify its consumers about the status change of the MBS session, or for a location dependent MBS session, of the part of the MBS session within a service area.
Input, Required: MBS Session ID, Event ID.... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.10 Nmbsmf_MBSSession_StatusSubscribe service operation
| Service operation name: Nmbsmf_MBSSession_StatusSubscribe
Description: This service operation is used by the NF service consumer (e.g. NEF, MBSF, AF) to subscribe notification about events related to the status of the MBS session, or for a location dependent MBS session, the part of the MBS session within a service ar... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.1.3.11 Nmbsmf_MBSSession_StatusUnsubscribe service operation
| Service operation name: Nmbsmf_MBSSession_StatusUnsubscribe
Description: This service operation, is used by the NF service consumer (e.g. NEF, MBSF, AF) to unsubscribe to notification about events related to the status of the MBS session, or for a location dependent MBS session, the part of the MBS session within a se... |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.2 PCF Services
| |
c00f9f04ddf564fe9fb933d959f62295 | 23.247 | 9.2.1 General
| The following table illustrates the PCF Services for MBS.
Table 9.2.1-1: NF services provided by PCF for MBS
Service Name
Service Operations
Operation
Semantics
Example Consumer (s)
Npcf_MBSPolicyControl
Create
Request/Response
MB-SMF
Update
Request/Response
MB-SMF
Delete
Request/Response
MB-SMF
Np... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.