How RedCap Support works
Workflow
![]() Note |
For this feature to work
|
These stages explain the process of RedCap support on SMF:
-
RedCap PDU Session Establishment: A RedCap UE sends a PDU Session Establishment Request to AMF.
Upon receiving the request, AMF sends a PDU Session SM Context Request to SMF and sets the ratType IE as RedCap in the message.
-
Subscription, Policy Creation, and Charging Data requests: SMF receives the ratType IE as RedCap from AMF and forwards it to UDM, PCF, and CHF for subscription, policy creation, and charging data requests respectively.
-
BAR creation during N4 Session Establishment: The buffering duration and packet count for HLCOM are communicated from the SMF to the UPF using Buffering Action Rules (BARs) as defined in the 3GPP TS 29.244 specification.
SMF sends the N4 Session Establishment Request to the UPF including the ratType IE as RedCap. SMF also creates an empty BAR and associates it to the FARs during N4 Session Establishment.
-
UE's entry in the Idle mode: SMF instructs the UPF to buffer when the UE moves to idle state. SMF sends an N4 Session Modification Request to UPF with UpdateBAR IE containing these IEs:
Table 2. Buffering IEs in UpdateBAR IE Buffering IE
Description
DDND (Downlink Data Notification Delay)
The UP function supports the buffering parameter "Downlink Data Notification Delay (DDND)". SBPC (Suggested Buffering Packets Count)
The UP function supports the "Suggested Buffering Packets Count (SBPC)" is present, when the UP function indicates the support of the feature UL/DL Buffering Control (UDBC).
UPF sends the Downlink Data Notification to SMF.
-
UE's exit from the Idle mode: SMF sends an N1 N2 Transfer Request to AMF. SMF sets the extBufSupport IE (Extended Buffering Support) to true in the N2 PDU Setup Request message to indicate extended buffering support to AMF based on configuration and based on the UPF support.
SMF does not set extBufSupport to true in case of paging for a control plane message.
As the UE is unreachable, the AMF sends a PDUSessionResourceSetupRequestTransfer Response message to SMF including the status code and cause as 504: UE_NOT_REACHABLE. SMF also receives a maxWaitingTime IE (Estimated Maximum Waiting Time) in the N1N2MsgTxfrErrDetail IE. SMF starts the maxWaitingTime IE timer and stores the flow information for retry.
SMF sends the N4 Modification Request with UpdateBAR with "DL Buffering Duration (DBD)" same as the estimated maximum wait time and "DL Buffering Suggested Packet Count (DBPC)" from the configuration, if the UPF has indicated the support for DBDM.
For more details on the configuration, see the Configure buffering values for HLCOM RedCap sessions section.
Limitations
These are the known limitations of Reduced Capability support on SMF:
-
17.x compliance profile is required for nsmf-pdusession, npcf-smpolicycontrol, and chf-convergedcharging services.
-
16.9.x compliance profile is required for namf-comm services.
-
SMF supports the extended buffering (HLCOM) functionality only for the RedCap RatType and not for other RatTypes.
-
SMF supports the extended buffering only for Idle mode exit due to data trigger.
-
The RedCap PDU Session Establishment is not supported for roaming calls.
-
UPF selection based on HLCOM supported feature bits is not supported.
-
The AMF selection or discovery for namf-comm service based on HLCOM is not supported.
-
SMF will cap the DBD value to a lower value in case of encoding restrictions on the N4 interface.
-
The ratType label with NR_REDCAP value is not supported for policy_msg_processing_status stats.
Standards compliance
SMF supports 3GPP compliance profile version 17.5.0 for the service nsmf-pdusession.