Abstract: Technology for a radio access network (RAN) node that is operable to report user plane congestion (UPCON) is disclosed. The RAN node may include computer circuitry configured to receive, from a Core Network (CN), an information element (IE) including UPCON related Policy and Control Charging (PCC) information. The RAN node may identify a location of an UPCON event, at the RAN node, based on an UPCON event trigger included in the UPCON related PCC information. The RAN node may report Radio Access Network Congestion Information (RCI) about the UPCON event to one or more network elements in the CN.

Abstract: Technology for as radio access network (RAN) node that is operable to report user plane congestion (UPCON) is disclosed. The RAN node may include computer circuitry configured to receive, from a Core Network (CN), an information element (IE) including UPCON related Policy and Control Charging (PCC) information. The RAN node may identify a location of an UPCON event, at the RAN node, based on an UPCON event trigger included in the UPCON related PCC information. The RAN node may report Radio Access Network Congestion Information (RCI) about the UPCON event to one or more network elements in the CN.

Abstract: Technology for reporting radio access network (RAN) user plane congestion (UPCON) is disclosed. In an example, a core network (CN) device can include computer circuitry configured to: receive an UPCON event report using an UPCON container that includes a congestion situation indicator to indicate a UPCON situation; and change an UPCON process based on the congestion situation indicator. The core network device can include a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a policy and charging enforcement function (PCEF), a policy and charging rules function (PCEF), a serving general packet radio service (GPRS) support node (SGSN), a gateway GPRS support node (GGSN), an access network discovery and selection function (ANDSF), an operation and maintenance (O&M) subsystem, an UPCON server, a proxy, or a standalone function entity.