Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.503  Word version:  18.4.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   6.1.2…   6.1.2.4…   6.1.3…   6.1.3.6…   6.1.3.18…   6.1.3.21…   6.1.4…   6.2…   6.2.2…   6.3…   6.4…   6.6…   A…   C   D…

 

C (Normative)  Support for Application Functions supporting Rx interface |R16|p. 165

To allow the 5G system to interwork with AFs related to existing services, e.g. IMS based services as described in TS 23.228, Mission Critical Push To Talk services as described in TS 23.179, the PCF shall support the corresponding IMS procedures defined in the main body of this TS via Rx interface. This facilitates the migration from EPC to 5GC without requiring these AFs to upgrade to support the Npcf_PolicyAuthorization services in Rel-16.
Reproduction of 3GPP TS 23.503, Fig. C-1: Interworking between 5G Policy framework and AFs supporting Rx interface
Up
Session Binding applies for PDU Sessions of IP type only.
The functionality described for Multimedia Priority Services (clause 6.1.3.11) and Mission Critical service (clause 6.1.3.19) applies via Rx interface.
In order to support IMS Emergency services over Rx interface, in addition to the functional description in clause 6.1.3.10, the following applies: The PCF shall provide the IMEI and the subscriber identifiers (IMSI, MSISDN) (if available), received from the SMF at PDU Session establishment, if so requested by the P-CSCF. The PCF derives the IMEI from the PEI, the IMSI from the SUPI and the MSISDN from the GPSI.
Any AF using Rx, such as P-CSCF, the BSF determines the selected PCF address according to the information included in the incoming Rx requests and the information stored at the BSF. The BSF is able to proxy or redirect Rx requests targeting an IP address of a UE to the selected PCF.
The following event reporting is supported over Rx interface:
Event Description Availability for Rx Session
PLMN Identifier NotificationThe PLMN identifier where the UE is currently located.Yes
Change of Access TypeThe Access Type and, if applicable, the RAT Type of the PDU Session has changed.Yes
EPS fallbackEPS fallback is initiatedYes
Signalling path statusThe status of the resources related to the signalling traffic of the AF session.Yes
Access Network Charging Correlation InformationThe Access Network Charging Correlation Information of the resources allocated for the AF session.Yes
Access Network Information NotificationThe user location and/or timezone when the PDU Session has changed in relation to the AF session.Yes
Reporting Usage for Sponsored Data ConnectivityThe usage threshold provided by the AF has been reached; or the AF session is terminated.Yes
Resource allocation statusThe status of the resources related to the AF session (established/released).Yes
QoS targets can no longer (or can again) be fulfilledThe QoS targets can no longer (or can again) be fulfilled by the network for (a part of) the AF session.No
Out of creditCredit is no longer available.Yes
Up

Up   Top   ToC