9 Roles for PN redirection

24.2593GPPPersonal Network Management (PNM)Release 17Stage 3TS

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

9.1 Introduction

The PN redirection redirects sessions containing in the Request-URI the address of any UEs of a PN to the default UE or the default PNE other than a PN UE of the same PN as described in 3GPP TS 22.259 [2] and in 3GPP TS 23.259 [15].

9.2 PN UE

There is no PNM specific requirement for the PN UE redirection.

Upon receiving a SIP INVITE request containing in the Request-URI the address of a PNE, the UE shall forward the SIP INVITE request to the PNE via the PAN internal interface.

NOTE: The PAN internal interface is out of scope of this document.

9.3 PNM application

9.3.1 PN UE redirection procedure in the IM CN subsystem

When the PNM AS receives an initial request containing in the Request-URI the address of a UE or a PNE other than a PN UE that exists in the PN configuration due to the terminating initial filter criteria, the PNM AS shall verify if the address in the Request-URI exists in a <RedirectingUserID> element in the PN configuration. If there is a matching <RedirectingUserID> element the PNM AS shall send an initial request of the same SIP Method on a new dialog to the URI contained in the <RedirectedUserID> element. The PNM AS then routes the initial request based on the standard call setup procedures as specified in 3GPP TS 24.229 [3].

NOTE: The PNM AS is triggered first by forming the initial filter criteria in the S-CSCF.

The PNM AS shall include in the request the following:

a) a Request-URI set to the SIP URI contained in the <RedirectedUserID> element (e.g. a public user identity or a GRUU);

b) a From header set to the SIP URI of the PNM AS;

c) a To header set to the URI contained in the <RedirectedUserID> element;

d) a P-Asserted-Identity header set to the contents of the P-Asserted-Identity header in the original initial request;

e) a Contact header set to the IP address or FQDN of the PNM AS;

f) a Supported header containing the option tags from the original initial request with the addition of the option tag "histinfo";

g) a History-Info header that includes as the Targeted-to-URI the URI from the Request-URI of the original initial request, and as the next branch index URI, the contents of the Request-URI of this request.

h) a Accept-Contact header with a g.3gpp.pne-id media feature tag containing the PNE identifier or media feature tag containing the requested device capabilites along with the parameters "require" and "explicit".

If the PNM AS receives in response a 4xx, 5xx or 6xx response, and there exist more <RedirectedUserID> elements in the PN configuration which have not had the request forwarded to them yet, then the PNM AS shall send an initial request of the same SIP Method on a new dialog to the URI of the UE or the PNE other than a PN UEcontained in the next lower priority <PNController> element as above.

Otherwise, if there does not exist more <RedirectedUserID> elements in the PN configuration which have not had the request forwarded to them yet, then the PNM AS shall forward the response back towards the originator of the initial request.

If the PNM AS receives in response a 200 (OK) response, the PNM AS shall forward the response back towards the originator of the initial request.

9.3.2 PN UE redirection procedure in the CS domain

When the PNM application receives an indication that the gsmSCF has received a CAMEL IDP relating to a terminating call, the PNM application shall:

1) check if the re-direction is applicable for the call on the basis of service key and called party number received in CAMEL IDP message.

2) if the call is not subject to re-direction, cause the gsmSCF to respond with a CAMEL CONTINUE and no further PNM specific procedures are performed on this call.

3) if the call is subject to re-direction, retrieve the Destination Routing Address.

4) if the call is subject to re-direction, cause the gsmSCF to respond with a CAMEL CONNECT message with the Destination Routing Address set to the MSISDN of default UE.

When the PNM application receives an indication that the gsmSCF has received a EventReportBCSM message indicating that the default UE cannot setup the session/call, the PNM application shall:

1) retrive the Destination Routing Address of the other UE of the next lower priority based on the PN-configuration.

2) cause the gsmSCF to respond with a CAMEL CONNECT message with the Destination Routing Address set to the MSISDN of the selected UE.

3) if there are no more UEs selected for redirection, cause the gsmSCF to respond with a CAMEL CONTINUE and no further PNM specific procedures are performed on this call.