通信人家园
标题: IMS GCF测试如何通过看case procedure来得知哪些field/IE必须带 - Part1 [查看完整版帖子] [打印本页]
时间: 2019-3-24 15:35
作者: yyh19820713
标题: IMS GCF测试如何通过看case procedure来得知哪些field/IE必须带 - Part1
本帖最后由 yyh19820713 于 2019-3-24 15:36 编辑
在做GCF的IMS测试时，有时遇到IE mismatch或messageinvalid这样的错误，但是如果打印不全，就不知道到底mismatch在哪里或者哪个IE导致invalid了。有时mismatch的IE太多，就不知道哪个真正matters.
根本方法是查看这个case的详细步骤，看到底哪个IE必须要带，哪个IE不需要。
以IMS emergency registration/call的case 19.5.1为例，现在34.229-1里找到test procedure：
--------------clip--------------
19.5.1 New initial emergencyregistration / UE obtains from the serving IP-CAN an IP address different thanthe IP address used for the emergency registrationTest procedure
applicablefor a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)
1-15) UE executes the procedures described in TS 36.508 [94] table 4.5A.4.3-1 steps 1 to 15 for EPS emergency bearer context activation, IMS emergencyregistration and subsequent IMS emergency speech call establishment with PSAP
16) Call isreleased on the UE. SS waits for the UE tosend a BYE request.
17) SS responds to the BYE request with valid 200 OK response.
Expected sequence
| Step |
Direction
|
Message
|
Comment
|
|
UE
|
SS
|
|
|
| 1 |
|
User initiates an emergency call
|
|
| 2-10 |
|
Steps defined in annex C.20 followed by the steps defined in annex C.22
|
IMS emergency registration by the UE followed by IMS emergency call setup with PSAP. Referred from 36.508 [94] table 4.5A.4.3-1 for a UE with E-UTRA support.
|
| 11 |
|
void
|
|
| 12 |
|
void
|
|
| 13-17 |
|
Steps defined in annex C.32
|
Make the UE release the call including EPS Bearer Deactivation procedure according to TS 36.508 [94] subclause 4.5A.15.
|
|
|
|
|
|
--------------clip--------------
测试步骤里提到具体步骤在C.20,C.22,C.32,其中C.20是注册的步骤，我们以C.20为例：
--------------clip--------------
C.20 GenericTest Procedure for IMS emergency registrationTest procedure:
1) SS waits for the UE to send an initial REGISTER request.
2) The SS responds to the initial REGISTER request with avalid 401 Unauthorized response.
3) TheSS waits for the UE to set up a temporary set of security associations and tosend another REGISTER request over those security associations.
4) TheSS responds to the second REGISTER request with valid 200 OK response, sentover the same temporary set of security associations that the UE used forsending the REGISTER request.
Expected sequence:
| Step |
Direction
|
Message
|
Comment
|
|
UE
|
SS
|
|
|
| 1 |
à
|
REGISTER
|
The UE sends initial IMS emergency registration
|
| 2 |
ß
|
401 Unauthorized
|
The SS responds with a valid AKAv1-MD5 authentication challenge and security mechanisms supported by the network.
|
| 3 |
à
|
REGISTER
|
The UE completes the security negotiation procedures, sets up a temporary set of SAs and uses those for sending another REGISTER with AKAv1-MD5 credentials.
|
| 4 |
ß
|
200 OK
|
The SS responds with 200 OK.
|
|
|
|
|
|
Specific Message Contents:
REGISTER (Step 1)
Use thedefault message “REGISTER” in annex A.1.1 with condition A1 "Initial unprotected REGISTER"and condition A7 “Initial IMS emergencyregistration” simultaneously applying.
The contents of From and To headers of the REGISTERrequest shall be according to condition A7.
REGISTER (Step 3)
Use the default message “REGISTER” in annexA.1.1 with condition A2 "Subsequent REGISTER sent over securityassociations" and condition A7 “Initial IMS emergency registration”simultaneously applying.
The contentsof From and To headers of the REGISTER request shall be according to conditionA7.
200 OK for REGISTER (Step 4)
Use the default message “200 OK forREGISTER” in annex A.1.3 with condition A3 “Response for an emergencyregistration”.
--------------clip--------------
| 通信人家园 (https://www.txrjy.com/) |
Powered by C114 |