PHS MoU Document
B-IF0.50-02-TS
Title: Public Personal Handy-Phone System : Information Flow of PHS
Supplementary Service Information Flow of Public PHS
Roaming
Version: 02
Date: May 15, 1998
PHS MoU Classification: Unrestricted
List of contents:<Summary>
1. Abbreviations
2. Functional model of basic PHS roaming capability set
2.1 Function Model
2.2 Functional entity (FEs) pesentation
3. Information flows of basic PHS roaming capability set
3.1 Basic procedure
3.2 Mobility procedure
3.3 PS interaction procedure
3.4 Call handling procedure
3.5 Definition of individual information flow
4. Functional entity action
4.1 Functional entity FE1 (SDF (H) /SCF/CUSF)
4.2 Functional entity FE2 (SDF (Vnew) /SCF/CUSF)
4.3 Functional entity FE3 (SDF (Vpre))4.4 Functional entity FE4 (SCUAF/CUSF)
Annex A

Number of pages: 21

PHS MoU Group
c/o Association of Radio Industries and Businesses (ARIB)
14F, Nittochi Bldg., 4-1, Kasumigaseki 1-choume, Chiyoda-ku, Tokyo 100, Japan
TEL +81-3-5510-8599 FAX +81-3-3592-1103© PHS MoU Group1998

PHS MoU Document
B-IF0.50-02-TS
VersionHistory of Revised Versions
Date
Outline

01

02

EstablishedMay 15, 1998

Public Personal Handy-Phone System:

General Description of PHS-UUS- PHS-UUS Supplementary Service <Summary>Contents
1. Abbreviations................................................................................................................................

page1

2. Functional model of basic PHS roaming capability set ......................................................................

1

2.1 Functional model ..........................................................................................................................

1

2.2 Functional entity(FE)s presentation..............................................................................................

2

3. Information flows of basic PHS roaming capability set .....................................................................

2

3.1 Basic procedures...........................................................................................................................

5

3.1.1 Service profile transfer at the first location registration.......................................................

5

3.1.1.1 Outline......................................................................................................................

6

3.1.1.2 Information flow diagram.........................................................................................

6

3.1.2 Subsequent service profile transfer ......................................................................................

6

3.1.2.1 Outline......................................................................................................................

6

3.1.2.2 Information flow diagram.........................................................................................

7

3.2 Mobility procedures......................................................................................................................

7

3.2.1 Inter-network location registration .......................................................................................

7

3.2.1.1 Outline......................................................................................................................

7

3.2.1.2 Information flow diagram.........................................................................................

7

3.2.2 Deletion of information in the visited network.....................................................................

8

3.2.2.1 Outline......................................................................................................................

8

3.2.2.2 Information flow diagram.........................................................................................

8

3.3 PS interaction procedure...............................................................................................................

93.3.1 Location registration req. ind................................................................................................

93.3.1.1 Outline......................................................................................................................

93.3.1.2 Information flow diagram.........................................................................................

9

3.3.2 PS authentication..................................................................................................................

9

3.3.2.1 Outline......................................................................................................................

9

3.3.2.2 Information flow diagram.........................................................................................

9

3.3.3 Location registration resp. conf. ...........................................................................................

10

B-IF0.50-02-TSýýýýýL

3.3.3.1 Outline......................................................................................................................

10

3.3.3.2 Information flow diagram.........................................................................................

10

3.4 Call handling procedure................................................................................................................

11

3.4.1 PHS roaming number hunting ..............................................................................................

11

3.4.1.1 Outline......................................................................................................................

11

3.4.1.2 Information flow diagram.........................................................................................

11

3.5 Definition of individual information flow ....................................................................................

11

3.5.1 Relationship ra......................................................................................................................

11

3.5.1.1 Flow between SDF(Vnew)/SCF/CUSF and SDF(H) ...............................................

11

3.5.2 Relationship rb .....................................................................................................................

12

3.5.2.1 Flow between SDF(Vpre) and SDF(H)....................................................................

12

3.5.3 Relationship rc......................................................................................................................

13

3.5.3.1 Flow between SCUAF/CUSF and SDF(Vnew)/SCF/CUSF ....................................

13

4. Functional entity action ......................................................................................................................

13

4.1 Functional entity FE1(SDF(H)/SCF/CUSF) .................................................................................

13

4.2 Functional entity FE2(SDF(Vnew)/SCF/CUSF) ..........................................................................

15

4.3 Functional entity FE3(SDF(Vpre)) ...............................................................................................

16

4.4 Functional entity FE4(SCUAF/CUSF) .........................................................................................

16

Annex A Information flow of call related case for roaming service ....................................................

17LLýýýýýB-IF0.50-02-TS

B-IF0.50-02-TS
Public Personal Handy-Phone System:
Information Flow of PHS Supplementary Service
Information Flow of Public PHS Roaming<Summary>
1. Relation with International Standards
This specification specifies information flow of PHS roaming based on TTC Standard JT-Q1218-a(PHS roaming capability set 2) which is based on the results of IN-CS2 in ITU-T SG11.

2. Difference from ITU-T Recommendation
The description of this portion is not provided because the study results of IN-CS2 in ITU-T SG11
have not been officially published yet.

3. References
TTC Standard JT-Q1218-a
PHS MoU Specification B-SV5.00, B-NW0.00, B-NW1.00, B-IF4.28

4. Items for Further Studynone

B-IF0.50-02-TSýýýýý(1)B-IF0.50-02-TS
Public Personal Handy-Phone System:
Information Flow of PHS Supplementary Service
Information Flow of Public PHS Roaming

1. Abbreviations
FE
FEA
IE
IF
IN
PE
PHS
SCF
CCF
CCAF
CUSF
SCUAF
SDF
SDF(H)SDF(Vnew)SDF(Vpre)
SDP
SSF
SSP
PS
CS

Functional Entity
Functional Entity Action
Information Element
Information FlowIntelligent Network
Physical Entity
Personal Handy-Phone System
Service Control Function
Call Control Function
Call Control Agent Function
Call Unrelated Service Function
Service Control User Agent Function
Service Data Function
Service Data Function in home network
Service Data Function in newly visited network
Service Data Function in previously visited network
Service Data Point
Service Switching Function
Service Switching Point
Personal Station
Cell Station

2. Functional model of basic PHS roaming capability set
This specification is basically applied to both CS type 1 and CS type 2 described in B-NW1.00
document. However, it is noted that as for CS type 1, PS authentication between PS/CS(FE4) and
newly visited network(FE2)/home network(FE1) is performed via IF2, while as for CS type 2, it isperformed via IFa.
There are some schemes for association of PHS roaming number to PS(s) as described in B-NW0.00
document, roaming number assignment method No.1 (one number per network) scheme and roaming
number assignment method No.2 (one temporary number at call origination to roaming PS) scheme
are supported in this specification. Furthermore, it mainly describes, location registration case forroaming and roaming number hunting case. Description of Information flow for call origination toroaming PS Including IF3 is provided in Annex A in this document.
2.1 Functional model
The functional entity(FE)s and information flow(IF)s serve as a basis for PHS roaming service andare described in B-SV5.00 document. The type of functional models addressed by this specification isshown in Figure 2-1/B-IF0.50 below.

B-IF0.50-02-TSýýýýý1

rc
FE4
SCUAF
/CUSF

FE1

FE2

rc

PS/CS

SDF(Vnew)/SCF/CUSF

Newly visited NWra

SDF(H)/SCF /CUSF

FE3

rb

Home NW

SDF(Vpre)Previously
Visited NW

Figure 2-1/B-IF0.50 Basic PHS roaming capability set functional model

2.2 Functional entity(FE)s presentation
The functional entities (FEs) have the following meaning in Figure 2-1/B-IF0.50.
FE1
FE2
FE3
FE4

SDF(H)/SCF/CUSF
SDF(Vnew)/SCF/CUSF
SDF(Vpre)SCUAF/CUSF

SDF/SCF/CUSF in home network
SDF/SCF/CUSF in newly visited network
SDF in previously visited network
SCUAF/CUSF in newly visited network or home network

In this specification, SCUAF and CUSF which represent PS and CS respectively are integrated as
FE4, and the information flow between these entities (that is IF1, air interface portion) is notprovided, because the same information flow as that between FE4 and FE2 (that is IF2) is utilized
between them. Further more, the information flow between the entities in FE1 and FE2 is notprovided, because the interface protocol specification of this portion is not scheduled at this time.
The relationship between FE2-FE1 is represented by relationship ra in the figure.
The relationship between FE3-FE1 is represented by relationship rb in the figure.
The relationship between FE4-FE2 (that is IF2) is represented by relationship rc in the figure.
The relationship between FE4-FE1 (that is IF2) is also represented by relationship rc in the figure.
Home network, newly visited network and previously visited network are modeled as independent
network. Authentication may be performed between FEs. Authentication between FEs is for further
study.
3. Information flows of basic PHS roaming capability set
The basic features for the basic PHS roaming capability set are described in this clause as various
operations. The PHS roaming processes are defined in B-NW1.00 document. This clause describes
the following four procedures considering the addition of FE4 related processes.
- Basic procedure- Mobility procedure- PS interaction procedure- Call handling procedure
PHS roaming procedures depend on conditions of public PS, the visited network and the home
network. Following 4 conditions should be considered.

2ýýýýýB-IF0.50-02-TS

(1) The case where public PS moved from the home network to the visited network
The outline of the sequence in the case where public PS in the home network moved to the visited
network and requests location registration for the first time is shown in Figure 3-1/B-IF0.50.

Location registration req. ind.

Service profile transfer
at the first location registration

PS authentication

Inter-network location registration

Location registration resp. conf.

End

Figure3-1/B-IF0.50

Basic PHS roaming procedure outline (a)Moreover, the sequence in the case where public PS doesn't request inter-network location
registration after the completion of service profile transfer at the first location registration is describedin Annex C of B-IF4.50 document.

(2) The case where public PS moved from the previously visited network to the newly visited network
The outline of the sequence in the case where public PS in the previously visited network moved to
the newly visited network and requests location registration for the first time is shown in Figure 32/B-IF0.50.

B-IF0.50-02-TSýýýýý3

Location registration req. ind.

Service profile transfer
at the first location registration

PS authentication

Inter-network location registration

Deletion of visited network information

Location registration resp. conf.

End
Figure3-2/B-IF0.50 Basic PHS roaming procedure outline (b)(3) The case where public PS moved to the home network
The outline of the sequence in the case where public PS in the visited network moved to the home
network and requests location registration for the first time is shown in Figure 3-3/B-IF0.50.
Location registration req. ind.

PS authentication

Deletion of visited network information

Location registration resp. conf.

End
Figure 3-3/B-IF0.50

Basic PHS roaming procedure outline (c)(4) The case where the consumption of authentication information for the public PS

4ýýýýýB-IF0.50-02-TS

The authentication information in SDF (Vnew) for the public PS is consumed in the PS authentication
which may be required in the procedure of call origination, call termination and handover. The
outline of the sequence in case of shortage of the authentication information in SDF (Vnew) for the
public PS which has registered the location in the visited network is shown in Figure 3-4/B-IF0.50.
PS authentication

Subsequent service profile transfer

End

Figure 3-4/B-IF0.50

Basic PHS roaming procedure outline (d)(5) The case where home network requires routing information to visited network in the scheme ofroaming number assignment method No.2.
The outline of the sequence in case where home network requires routing information to visited
network in the scheme of roaming number assignment method No.2 is shown in Figure 3-5/B-IF0.50.

PHS roaming number hunting

End

Figure 3-5/B-IF0.50 Basic PHS roaming procedure outline (e)In the procedure described in this specification, it is assumed that the visited network can identify thehome network of the roaming PS from the PHS number. It is also assumed that the agreement of
shadowing related to all roamable user has been established between SDF(Vnew/Vpre) in the visited
network and SDF(H) in the network. Only in case of subsequent service profile transfer procedure, it
is assumed that the agreement related to the PHS number has been established between SDF(Vnew)
in the visited network and SDF(H) in the network.

3.1 Basic procedures
3.1.1 Service profile transfer at the first location registration
In the procedure of service profile transfer at the first location registration, copying of the service
profile related to the PHS number from the home network to the visited network is performed in order

B-IF0.50-02-TSýýýýý5

that the visited network can offer services to the PS.
3.1.1.1 Outline
After the PS requests the PHS roaming service to the visited network, following procedures are
performed between SDF(Vnew) and SDF(H) in order to copy the service profile related to the PS
from the home network to the visited network.
(1) SDF(Vnew) requests to modify the entry information in SDF(H) related to the PHS number.
(2) The modification of the entry information in SDF(H) related to the PHS number triggers off thecopying.
(3) SDF(H) copies the PHS service profile related to the PHS number to SDF(Vnew).

3.1.1.2 Information flow diagram
The information flow diagram is shown in Figure 3-6/B-IF0.50.
FE2
SDF(Vnew)/SCF/CUSF
200

ra

FE1
SDF(h)

Authenticate
Authenticate Result

100

201
210

Chaining Request(for Modify Entry)
Chaining Result

110

211
202

End Authenticate
101
Authenticate

205

Update Copy
220

102

Authenticate Result
103
120

Update Copy Result
121
End Authenticate

104

206

Fig 3-6/B-IF0.50 Service profile transfer at the first location registration
3.1.2 Subsequent service profile transfer
In case of shortage of the authentication information for the PS located in the visited network,
copying of the authentication information related to the PHS number from the home network to thevisited network is performed by the procedure of subsequent service profile transfer,
3.1.2.1 Outline
The following procedures are performed between SDF(Vnew) and SDF(H) in order to copy the6ýýýýýB-IF0.50-02-TS

authentication information from the home network to the visited network.
(1) SDF(Vnew) requests of SDF(H) to copy the authentication information.
(2) SDF(H) carries out the copy to SDF(Vnew).
3.1.2.2 Information flow diagram
The information flow diagram is shown in Figure 3-7/B-IF0.50.
FE2
SDF(Vnew)/SCF/CUSF

ra

FE1
SDF(H)

Authenticate

200

Authenticate Result

100

201
230

Copy Request
Copy Result

130

231
End Authenticate

202

101

Fig 3-7/B-IF0.50

Subsequent service profile transfer

3.2 Mobility procedures
3.2.1 Inter-network location registration
In the procedure of inter-network location registration, the visited network requests of the home
network to modify the information identifying visited network of the roaming PS in order that the call
can terminate to the PS.
3.2.1.1 Outline
The following procedures are performed between SDF(Vnew) and SDF(H) for inter-network location
registration.
(1) SDF(Vnew) requests of SDF(H) to modify the information identifying visited network of the PHS
number(2) SDF(H) carries out the modification of the information.
3.2.1.2 Information flow diagram
The information flow diagram is shown in Figure 3-8/B-IF0.50.

B-IF0.50-02-TSýýýýý7

FE2
ra

SDF(Vnew)/SCF/CUSF

FE1
SDF(H)

Authenticate

200

Authenticate Result

100

201
210

Chaining Request(for Modify Entry)
110

Chaining Result
211
202

End Authenticate
101

Fig 3-8/B-IF0.50

Inter-network location registration

3.2.2 Deletion of information in the visited network
In this procedure, deletion of the information related to the PHS number in the visited network whichis requested by the home network is performed.
3.2.2.1 Outline
The following procedures are performed between SDF(Vpre) and SDF(H) for deletion of informationin the visited network.
(1) SDF(H) in the home network requests of SDF(Vpre) in the previously visited network to delete
the information related to the PHS number.
(2) SDF(Vpre) in the previously visited network follows the request and carries out the deletion of theinformation related to the PHS number.
3.2.2.2 Information flow diagram
The information flow diagram is shown in Figure 3-9/B-IF0.50.
FE1
SDF(H)105

rb

FE3
SDF(Vpre)Authenticate
Authenticate Result

305

106
122

Update Copy
Update Copy Result

320

123
107

End Authenticate
306

Fig 3-9/B-IF0.50

8ýýýýýB-IF0.50-02-TS

Deletion of information in the visited network3.3 PS interaction procedure
3.3.1 Location registration req. ind.
In the procedure of location registration req. ind., SCUAF/CUSF in the PS/CS requests location
registration of the PS to SDF(Vnew)/SCF/CUSF in newly visited network or to SDF(H)/SCF/CUSF
in home network.
3.3.1.1 Outline
The following procedure is performed between SCUAF/CUSF and SDF(Vnew)/SCF/CUSF or
between SCUAF/CUSF and SDF(H)/SCF/CUSF for location registration req. ind..
(1) SCUAF/CUSF in the PS/CS requests location registration of the PS to SDF(Vnew)/SCF/CUSF in
newly visited network or to SDF(H)/SCF/CUSF in home network.
3.3.1.2 Information flow diagram
The information flow diagram is shown in Figure 3-10/B-IF0.50.
In this figure, FE2 which contains SDF(Vnew)/SCF/CUSF is replaced by FE1 which contains
SDF(H)/SCF/CUSF in case of location registration in the home network.
FE4rc

SCUAF/CUSF
400

FE2SDF(Vnew)/SCF/CUSF

Location Registration req. ind.
240

Fig 3-10/B-IF0.50

Location Registration req. ind.

3.3.2 PS authentication
The procedure for PS authentication is performed for the purpose of confirming the visiting PS.
3.3.2.1 Outline
The following procedure is performed between SDF(Vnew)/SCF/CUSF in newly visited network and
SCUAF/CUSF in the PS/CS or between SDF(H)/SCF/CUSF in home network and SCUAF/CUSF in
the PS/CS for PS authentication.
(1) SDF(Vnew)/SCF/CUSF in newly visited network or SDF(H)/SCF/CUSF in home network
requests PS authentication to SCUAF/CUSF in the PS/CS.
(2) SCUAF/CUSF in the PS/CS responds to the request by sending PS authentication result toSDF(Vnew)/SCF/CUSF in newly visited network or SDF(H)/SCF/CUSF in home network.
3.3.2.2 Information flow diagram
The information flow diagram is shown in Figure 3-11/B-IF0.50.

B-IF0.50-02-TSýýýýý9In this figure, FE2 which contains SDF(Vnew)/SCF/CUSF is replaced by FE1 which contains
SDF(H)/SCF/CUSF in case of location registration in the home network.

FE4
SCUAF/CUSF

rc
PS Authenticate
PS Authenticate Result

401

FE2
SDF(Vnew)/SCF/CUSF
241242

Fig 3-11/B-IF0.50 PS authentication

3.3.3 Location registration resp. conf.
In this procedure, SDF(Vnew)/SCF/CUSF in newly visited network or SDF(H)/SCF/CUSF in home
network responds to the location registration request from SCUAF/CUSF in the PS/CS.
3.3.3.1 Outline
The following procedure is performed between SDF(Vnew)/SCF/CUSF and SCUAF/CUSF or
between SDF(H)/SCF/CUSF and SCUAF/CUSF for location registration resp. cof..
(1) SDF(Vnew)/SCF/CUSF in newly visited network or SDF(H)/SCF/CUSF in home network
responds to the location registration request from SCUAF/CUSF in the PS/CS.
3.3.3.2 Information flow diagram
The information flow diagram is shown in Figure 3-12/B-IF0.50.
In this figure, FE2 which contains SDF(Vnew)/SCF/CUSF is replaced by FE1 which contains
SDF(H)/SCF/CUSF in case of location registration in the home network.

FE4
SCUAF/CUSF

rc
Location Registration resp. conf.

402

Fig 3-12/B-IF0.50 Location registration resp. conf.

3.4 Call handling procedure10ýýýýýB-IF0.50-02-TS

FE2
SDF(Vnew)/SCF/CUSF
243

3.4.1 PHS roaming number hunting
In this procedure, PHS roaming number hunting which home network requests to visited network is
performed, when call to roaming PS is originated.
This procedure is used in the case of roaming number assignment method No.2.
3.4.1.1 Outline
The following procedures are performed between SDF(H) and SDF(Vnew) for hunting PHS roaming
number in the visited network.
(1) SDF(H) in the home network requests of SDF(Vnew) in the newly visited network to hunt a PHS
roaming number and to make relationship between the PHS roaming number and the PHS number.
(2) SDF(Vnew) in the newly visited network follows the request and carries out hunting of a PHS
roaming number and making relationship between the PHS roaming number and the PHS number
3.4.1.2 Information flow diagram
The information flow diagram is shown in Figure 3-13/B-IF0.50.
FE1

FE2
SDF(Vnew)ra

SDF(H)/SCF

Authenticate

102

Authenticate Result

205

103
111

Chaining Request(for Execute)212

Chaining Result
112
104

End Authenticate
206

Fig 3-13/B-IF0.50

PHS roaming number hunting

3.5 Definition of individual information flow
In the following definition of individual information flow, mandatory information element (IE) is
indicated as "M". The meaning of individual IE related to ra and rb is shown in B-IF4.28 document.
3.5.1 Relationship ra3.5.1.1 Flow between SDF(Vnew)/SCF/CUSF and SDF(H)
Authenticate
Information element:

Authentication Information

M

Authenticate Result
Information element:

Authentication Information

M

B-IF0.50-02-TSýýýýý11

Chaining Request
Information element:

Chained Argument
M
Security Parameters
M
IE description:
Chained Argument may contain PHS roaming number in case where it
is applied for ‘Modify Entry’ operation in inter-network location registration information flows.

Chaining Result
Information element:

Chained Result
M
Security Parameters
M
IE description:
Chained Result may contain PHS roaming number in case where it isapplied for ‘Execute’ operation in PHS roaming number hunting information flows.

Copy Request
Information element:

Replication Area
Maintained Part
Update Mode
Update Strategy
MasterM
M
M
M
M

Copy Result
Information element:

Replicated Data

M

Update Copy
Information element:

Refreshed Information

M

Update Copy Result
Information element:

none

End Authenticate
Information element:none

3.5.2 Relationship rb
3.5.2.1 Flow between SDF(Vpre) and SDF(H)
Authenticate
Information element:

Authentication Information

M

Authenticate Result
Information element:

Authentication Information

M

Update Copy
Information element:

Refreshed Information

M

Update Copy Result
Information element:

none

End Authenticate
Information element:none

3.5.3 Relationship rc
3.5.3.1 Flow between SCUAF/CUSF and SDF(Vnew)/SCF/CUSF

12ýýýýýB-IF0.50-02-TS

Location Registration req. ind.
Information element:
PHS NumberM
IE description:
The meaning of PHS Number is shown in B-SV5.00 document.
PS Authenticate
Information element:
PS Authentication InformationM
IE description:
PS Authentication Information contains information needed to performthe required type of authentication for PS.
PS Authenticate Result
Information element:
PS Authentication InformationM
IE description:
PS Authentication Information contains information used in providing
results of the authentication for PS.
Location Registration resp. conf.
Information element:noneM

4. Functional entity action
The functional entity action (FEA) can be referred by the number of the functional entity row in theinformation flow diagram. The figure number relevant to FEA is indicated in brackets [ ] which
follows the FEA number.
The FEA number is coded by three digits and the first digit relates to the FE number in which FEA isactivated. The 2nd and 3rd digits do not have specific meaning.
In this clause it is assumed that the SDF Data Manager represents a root of the request, while there are
two cases; one is that SDF Data Manager itself is the initiator, the other is that it is requested by otherentities. Distinction of these cases is for further study.
4.1 Functional entity FE1(SDF(H)/SCF/CUSF)
FEA:100[3-6, 3-7, 3-8]
- Receive and react to Authenticate from SDF(Vnew).
- Bind the association with SDF(Vnew).
- Formulate and send Authenticate Result to SDF(Vnew).
FEA:101[3-6, 3-7, 3-8]
- Receive and react to End Authenticate from SDF(Vnew).
- Unbind the association with SDF(Vnew).
FEA:102[3-6, 3-13]- Receive and react to a request from SDF Data Manager .
- Formulate and send Authenticate to SDF(Vnew) to bind the association with SDF(Vnew).
FEA:103[3-6, 3-13]- Receive and react to Authenticate Result from SDF(Vnew).
- Bind the association with SDF(Vnew).
FEA:104[3-6, 3-13]- Receive and react to a request from SDF Data Manager.
- Formulate and send End Authenticate to SDF(Vnew) to unbind the association with SDF(Vnew).

B-IF0.50-02-TSýýýýý13

- Unbind the association with SDF(Vnew).
FEA:105[3-9]- Receive and react to a request from SDF Data Manager .
- Formulate and send Authenticate to SDF(Vpre) to bind the association with SDF(Vpre).
FEA:106[3-9]- Receive and react to Authenticate Result from SDF(Vpre).
- Bind the association with SDF(Vpre).
FEA:107[3-9]- Receive and react to a request from SDF Data Manager .
- Formulate and send End Authenticate to SDF(Vpre) to unbind the association with SDF(Vpre).
- Unbind the association with SDF(Vpre).
FEA:110[3-6, 3-8]
- Receive and react to Chaining Request from SDF(Vnew).
- Updates the information for location related to the PHS number.
- Formulate and send Chaining Result to SDF(Vnew).
FEA:111[3-13]- Receive and react to a request from SDF Data Manager .
- Formulate and send Chaining Request to SDF(Vnew) to hunt a PHS roaming number and toassociate it to the PHS number.
FEA:112[3-13]- Receive and react to Chaining Result from SDF(Vnew).
FEA:120[3-6]- Receive and react to a request from SDF Data Manager .
- Extracts the PHS roaming service profile related to the PHS number.
- Formulate and send Update Copy to SDF(Vnew).
FEA:121[3-6]- Receive and react to Update Copy Result from SDF(Vnew).
FEA:122[3-9]- Receive and react to a request from SDF Data Manager .
- Formulate and send Update Copy to SDF(Vpre) for deleting the roaming service profile related to
the PHS number from SDF(Vpre).
FEA:123[3-9]- Receive and react to Update Copy Result from SDF(Vpre).
FEA:130[3-7]- Receive and react to Copy Request from SDF(Vnew).
- Extracts the authentication information related to the PHS number.
- Formulate and send Copy Result to SDF(Vnew).
note
FEA:240[3-10], FEA:241[3-11], FEA:242[3-11] and FEA:243[3-12] in FE2 are also performed in
FE1 in case of location registration in home network.

14ýýýýýB-IF0.50-02-TS

4.2 Functional entity FE2(SDF(Vnew)/SCF/CUSF)
FEA:200[3-6,3-7, 3-8]
- Receive and react to a request from SDF Data Manager .
- Formulate and send Authenticate to SDF(H) to bind the association with SDF(H).
FEA:201[3-6,3-7, 3-8]
- Receive and react to Authenticate Result from SDF(H).
- Bind the association with SDF(H).
FEA:202[3-6,3-7, 3-8]
- Receive and react to a request from SDF Data Manager .
- Formulate and send End Authenticate to SDF(H) to unbind the association with SDF(H).
- Unbind the association with SDF(H).
FEA:205[3-6, 3-13]- Receive and react to Authenticate from SDF(H).
- Bind the association with SDF(H).
- Formulate and send Authenticate Result to SDF(H).
FEA:206[3-6, 3-13]- Receive and react to End Authenticate from SDF(H).
- Unbind the association with SDF(H).
FEA:210[3-6, 3-8]
- Receive and react to a request from SDF Data Manager .
- Formulate and send Chaining Request to SDF(H) to update the information for location related to
the PHS number.
FEA:211[3-6, 3-8]
- Receive and react to Chaining Result from SDF(H).
FEA:212[3-13]- Receive and react to Chaining Request from SDF(H).
- Hunt a PHS roaming number and associate it to the PHS number.
- Formulate and send Chaining Result to SDF(H).
FEA:220[3-6]- Receive and react to Update Copy from SDF(H).
- Store the copy of the roaming service profile related to the PHS number.
- Formulate and send Update Copy Result to SDF(H).
FEA:230[3-7]- Receive and react to a request from SDF Data Manager .
- Formulate and send Copy Request to SDF(H) to get the authentication information related to the
PHS number.
FEA:231[3-7]- Receive and react to Copy Result from SDF(H).
- Store the copy of the information for authentication related to the PHS number .

B-IF0.50-02-TSýýýýý15

FEA:240[3-10]- Receive and react to Location Registration ind. from SCUAF/CUSF.
FEA:241[3-11]- Formulate and send PS Authenticate to SCUAF/CUSF.
FEA:242[.3-11]- Receive and react to PS Authenticate Result from SCUAF/CUSF.
FEA:243[3-12]- Formulate and send Location Registration resp. to SCUAF/CUSF.
4.3 Functional entity FE3(SDF(Vpre))FEA:305[3-7]- Receive and react to Authenticate from SDF(H).
- Bind the association with SDF(H).
- Formulate and send Authenticate Result to SDF(H).
FEA:306[3-9]- Receive and react to End Authenticate from SDF(H).
- Unbind the association with SDF(H).
FEA:320[3-9]- Receive and react to Update Copy from SDF(H).
- Delete the roaming service profile related to the PHS number from SDF(Vpre).
- Formulate and send Update Copy Result to SDF(H).
4.4 Functional entity FE4(SCUAF/CUSF)
FEA:400[3-10]- Formulate and send Location Registration req. to SDF(Vnew)/SCF/CUSF or SDF(H)/SCF/CUSF.
FEA:401[3-11]- Receive and react to PS Authenticate from SDF(Vnew)/SCF/CUSF or SDF(H)/SCF/CUSF.
- Formulate and send PS Authenticate Result to SDF(Vnew)/SCF/CUSF or SDF(H)/SCF/CUSF.
FEA:402[3-12]- Receive and react to Location Registration conf. from SDF(Vnew)/SCF/CUSF or
SDF(H)/SCF/CUSF.

16ýýýýýB-IF0.50-02-TS

toAnnex A Information flow of call related case for roaming service

1. Introduction
This annex provides information flow of call related case for roaming service briefly. It covers bothroaming number assignment method No.1 scheme and roaming number assignment method No.2
scheme.
2. Call origination from roaming PS
The same functional model and information flow as those of call origination from PS of non-roaming
state are applied.
3. Call origination to roaming PS
3.1 Functional model
Functional model for call origination to roaming PS is shown in Figure A-1/B-IF0.50.

)(ì6'+õ+ô

&&$)Uì &&)Uë

2ULJLQDWLQJ 2ULJLQDWLQJ
8VHU
1HWZRUN&&)

7UDQVLW1HWZRUNý$

Uë

î6&)
î66)
î&&)

+RPH
1HWZRUN

)(ë

UD

Uë

&&)

6'+õ9QHZôUë

7UDQVLW1HWZRUNý%

î6&)
î66)
î&&)

Uê &&$)

9LVLWHG
1HWZRUN

î&&)

&6î36

Figure A-1/B-IF0.50 Functional model for call origination to roaming PS

Definition of the functional entities FE1 and FE2 is the same as that in the main body of thisdocument. Moreover, definitions and descriptions of the basic call handling related portion of figure
a-1/B-IF0.50 (CCAF/CCF and relationship r1/r2/r3 etc.) are shown in ITU-T Recommendation Q.71.
3.2 Information flows
3.2.1 In the case of roaming number assignment method No.1 scheme
Information flows in case of roaming number assignment method No.1 scheme are shown in figure A2/B-IF0.50.

B-IF0.50-02-TSýýýýý17)(ì6')õ+ô

&&$) Uì &&)Note 1
SETUP
req. ind.
PROCEEDING

req. ind.

Uë

&&)

Uë

î6&)
î66)
î&&)

)(ë

UD Note 5Uë&&)6')õ9QHZô

Uë

î6&)
î66)
î&&)

Uê &&$)
î&&)

Note 2
Note 1
SETUP
req. ind.

Note 1
SETUP
req. ind.

Note 3
SETUP
req. ind.

Note 3
SETUP
req. ind.

Note 4
SETUP
req. ind.
PS AUTH
AUTH.RESULTREPORT(alerting)

REPORT(alerting)

REPORT
req. ind.

req. ind.
SETUP
resp. conf.
DISCONNECT
req. ind.
RELEASEreq. ind.

SETUP
resp. conf.

RELEASEreq. ind.
RELEASE
resp. conf.

RELEASE
resp. conf.

REPORT
req. ind.
SETUP
resp. conf.

RELEASEreq. ind.
RELEASE
resp. conf.

REPORT
req. ind.
SETUP
resp. conf.

RELEASEreq. ind.
RELEASE
resp. conf.

REPORT
req. ind.
SETUP
resp. conf.

req. ind.

SETUP
resp. conf.
CONNECTED
req. ind.

RELEASEreq. ind.
RELEASE
resp. conf.

DISCONNECT
req. ind.
RELEASEreq. ind.
RELEASE
resp. conf.

Figure A-2/B-IF0.50 In case of roaming number assignment method No.1 scheme

Note 1: PHS number contained in called number information element of SETUP req. ind.is used toroute call to the home network.
Note 2: PHS roaming number is obtained by converting PHS number in SDF(H).
Note 3: PHS roaming number contained in called number information element of SETUP req. ind.isused to route call to the visited network. PHS number is conveyed using additional
information of SETUP req. ind..

18ýýýýýB-IF0.50-02-TS

Note 4: PHS number contained in ‘called number’ information element of SETUP req. ind.is used toterminate call to the roaming PS.
Note 5: Relationship ra is not applied in case of roaming number assignment method No.1 scheme.

3.2.2 In the case of roaming number assignment method No.2 scheme
Information flows in case of roaming number assignment method No.2 scheme are shown in figure A3/B-IF0.50.

B-IF0.50-02-TSýýýýý19)(ì6')õ+ô

&&$) Uì &&)Note 1
SETUP
req. ind.
PROCEEDING

req. ind.

Uë&&)

Note 1
SETUP
req. ind.

Uë

î6&)
î66)
î&&)

)(ë

UD

Uë

&&)

6')õ9QHZô

Uë

î6&)
î66)
î&&)

Uê &&$)
î&&)

Note 1
SETUP
req. ind.
Note 2Authenticate
Authenticate Result
Chaining Request (for Execute)
Chaining Result
End Authenticate

Note 3
SETUP
req. ind.

Note 3
SETUP
req. ind.

Note 4
SETUP
req. ind.
PS AUTH
AUTH.RESULTREPORT(alerting)

REPORT(alerting)req. ind.
SETUP
resp. conf.
DISCONNECT
req. ind.
RELEASEreq. ind.

REPORT
req. ind.
SETUP
resp. conf.

RELEASEreq. ind.
RELEASE
resp. conf.

RELEASE
resp. conf.

REPORT
req. ind.
SETUP
resp. conf.

RELEASEreq. ind.
RELEASE
resp. conf.

REPORT
req. ind.
SETUP
resp. conf.

RELEASEreq. ind.
RELEASE
resp. conf.

REPORT
req. ind.
SETUP
resp. conf.

req. ind.
SETUP
resp. conf.
CONNECTED
req. ind.

RELEASEreq. ind.
RELEASE
resp. conf.

DISCONNECT
req. ind.
RELEASEreq. ind.
RELEASE
resp. conf.

Figure A-3/B-IF0.50 In case of roaming number assignment method No.2 scheme

20ýýýýýB-IF0.50-02-TS

Note 1: PHS number contained in called number information element of SETUP req. ind.is used toroute call to the home network.
Note 2: PHS roaming number is obtained through the information flows between SDF(H) andSDF(Vnew) (relationship ra). Detail flows are shown in the main body of this specification.
Note 3: PHS roaming number contained in called number information element of SETUP req. ind.isused to route call to the visited network. It also used to identify the PS (PHS number).
Note 4: PHS number contained in ‘called number’ information element of SETUP req. ind.is used toterminate call to the roaming PS.

B-IF0.50-02-TSýýýýý21