8 PUA procedures

25.4703GPPRelease 17TSUTRAN Iuh Interface PCAP User Adaption (PUA) signalling

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.1 Elementary Procedures

Table 1 summarizes the EPs.

Table 1; Elementary procedures

Elementary Procedure	Message
Connect	CONNECT
Direct Transfer	DIRECT TRANSFER
Disconnect	DISCONNECT
Connectionless Transfer	CONNECTIONLESS TRANSFER
Error Indication	ERROR INDICATION

8.2 Connect

8.2.1 General

The HNB can initiate this procedure to establish a Signalling Connection and carry a PCAP message.

8.2.2 Successful Operation

Figure 8.2.2-1: Connect procedure – successful operation

This procedure is used to carry the first PCAP message from the HNB to the HNB-GW.

If the SAS Indicator IE is included the HNB-GW may use to select a SAS for connection.

Additional information is provided to enable the HNB-GW to trigger the establishment of a new Signalling Connection between HNB and HNB-GW, which is directly mapped to the Iupc Signalling Connection the PCAP message refers to.

NOTE: The Context ID is used as the Iupc Signalling Connection identifier in the corresponding PCAP messages.

8.3 Direct Transfer

8.3.1 General

This procedure is initiated by either the HNB or HNB-GW to transport a PCAP message between the two nodes.

8.3.2 Successful Operation (HNB-GW Originated)

Figure 8.3.2-1: Direct Transfer procedure – successful operation

This procedure is used to carry any downlink connection-oriented PCAP message defined in TS 25.453 [2] from the HNB-GW to the HNB.

8.3.3 Successful Operation (HNB Originated)

Figure 8.3.3-1: Direct Transfer procedure – successful operation

This procedure is used to carry any uplink connection-oriented PCAP message defined in TS 25.453 [2], except those carried in CONNECT or DISCONNECT messages, from the HNB to the HNB-GW.

8.3.4 Abnormal Conditions

–

8.4 Disconnect

8.4.1 General

This procedure is normally initiated by the HNB to terminate a Signalling Connection between the HNB and HNB-GW, but may be initiated by the HNB-GW to close a refused connection or if an existing connection is released (e.g. for error reasons) by the SAS or HNB-GW.

8.4.2 Successful Operation (HNB Originated)

Figure 8.4.2-1: Disconnect procedure

This procedure is used to release a signalling connection between the HNB and HNB-GW and may carry the last PCAP (TS 25.453 [2]) uplink connection-oriented message of a given Signalling Connection to the HNB-GW over the Iuh interface. This procedure may also be used to indicate error conditions at the HNB. This procedure will indicate the cause of the termination in the Cause IE.

8.4.3 Successful Operation (HNB-GW Originated)

Figure 8.4.3-1: Disconnect procedure

This procedure is used to close a given Signalling Connection between the HNB and the HNB-GW over the Iuh interface. This procedure will indicate the cause of the termination in the Cause IE.

8.5 Connectionless Transfer

8.5.1 General

This procedure is initiated by either the HNB or the HNB-GW to transfer connectionless PCAP messages between the HNB and HNB-GW.

8.5.2 Successful Operation (HNB-GW Originated)

Figure 8.5.2-1: Connectionless Transfer procedure to HNB

This procedure is used to carry any downlink connectionless PCAP message defined in TS 25.453 [2] from the HNB-GW to the HNB.

8.5.3 Successful Operation (HNB Originated)

Figure 8.5.3-1: Connectionless Transfer procedure to HNB-GW

This procedure is used to carry any uplink connectionless PCAP message defined in TS 25.453 [2] from the HNB to the HNB-GW. If the SAS Indicator IE is included the HNB-GW may use to select a SAS as the destination of the message.

8.5.4 Abnormal Conditions

–

8.6 Error Indication

8.6.1 General

The Error Indication procedure is initiated by either HNB or HNB-GW to report detected errors in one incoming message.

8.6.2 Successful Operation

Figure 8.6.2-1 Error Indication HNB Originated, Successful Operation

Figure 8.6.2-2 Error Indication HNB-GW Originated, Successful Operation