Hi Olivier,
Following is my reply for both Sasken and R& S comments.
Regards
Jitendra
=======================================
Thanks Pankaj and Risya for the comments on 14.4.3.
MCC 160 accepts all the Sasken and R & S comments with just following one exception.
1) Implementation for Sasken’s comment 1 will be done differently than that suggested by R & S.
MCC 160 Solution : Radio Bearer Setup message will be corrected as per 34.108 before sending Radio Bearer Setup message.
Best Regards,
MCC 160
Jitendra Kumar Sahu,
ETSI, MCC 160.
Ph: +33 4 92 94 43 82
Cell : + 33 6 74 16 90 18
-----Original
Message-----
From: Rishi
Theivendran [mailto:Rishya.Theivendran@RSUK.ROHDE-SCHWARZ.COM]
Sent: 01 March 2004 10:30
To: 3GPP_TSG_T_WG1_SIG
Subject: Re: R&S submits GCF P2 RAB
14.4.3 test case for email approval
Dear
Pankaj,
Thank you for the kind
comments, pls. find our response below in blue:
Regards,
Rishya
Theivendran.
|
|
"Pankaj Gupta" <pankajg@sasken.com> 25/02/2004 05:47 AM |
|
Dear
Rishya,
Please find SASKEN comments for the test case 14.4.3 submitted
for email approval.
1. As per 34.108 for Radio Bearer Setup message in
case of FACH to FACH transition the value of New C-RNTI IE should be '1010 1010
1010 1010'.
In TTCN it is set as '0000 0000 0000
0001'.
>> In principle,
we do agree to the change as it is true that the default contents in 34108
states this value for FACH.
However
this change will imply the addition of a local reconfiguration
(ts_CMAC_New_RNTI_Reconf) after the RAB setup
message as the SS needs
to be reconfigured to use this new value as well. And also this change will
affect to all FACH
test cases in all ATS
(the ones that use ts_SS_CreateCellFACH).
Therefore we kindly ask
the MCC 160 team to decide on this issue.
2. In the
current TTCN implementation RAB is configured for Interactive type. However as
per 34.123-1 it can be of Background type also.
>> we do agree
but we would prefer to have "two tests inside one" as in most of the PS test
cases controlled by the pics/pixit
"pc_interactive" and
"pc_background".
3. At Row 5 test step
ts_CalculateActTime is called. However as the Activation Time IE is set as OMIT
in Radio Bearer Setup for this test case,
thus this
test step call is redundant.
>>
Agreed. This test step is not needed anymore after WA#RAB4200 and
WA#RAB4260.
4. TTCN Editiorial
Correction: Purpose information is not correct in the TTCN.
In TTCN it is
written as:
"To verify establishment
and data transfer of reference radio bearer configuration as specified in TS
34.108, clauses 6.10.2.4.3.2 and 6.10.2.4.4.1 for the case when three SCCPCHs
are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the
PCH and both the second and third SCCPCHs carry the FACH for
Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/
BCCH"
However as per 34.123-1 it
should be:
"To verify establishment
and data transfer of reference radio bearer configuration as specified in TS
34.108, clauses 6.10.2.4.3.3 and 6.10.2.4.4.1 for the case when one SCCPCH is
used in this SYSTEM INFORMATION (BCCH) configuration. The SCCPCH carries the
PCH, the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on
CCCH/ DCCH/ BCCH.
To be able to test the downlink radio bearer using the UE
loopback function, the reference radio bearer configuration according to TS
34.108, clause 6.10.2.4.4.1 (Interactive/Background 32 kbps PS RAB + SRB for
CCCH + SRB for DCCH on PRACH) is used in uplink"
>> We do
agree.
Please let us know your
comments.
Regards,
Pankaj Gupta
" Consistency is the name
of game,
Try! success will be yours
"
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Pankaj Gupta,
Senior Software Engineer,
CTS, NBU,
Sasken
Communication Technologies Limited
139/25, Ring Road, Domlur
Bangalore -
560071 India
Email: pankajg@sasken.com
Tel: + 91 80 25355501 Extn:
8131
Fax: + 91 80 25351133
URL:
www.sasken.com
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
-----
Original Message -----
From: Rishi Theivendran
To:
3GPP_TSG_T_WG1_SIG@LIST.ETSI.ORG
Sent: Monday, February 23, 2004 10:18
PM
Subject: R&S submits GCF P2 RAB 14.4.3 test case for email
approval
Dear T1/SIG
Colleagues,
Rohde & Schwarz submits GCF package 2 RAB test case
14.4.3 for approval:
T1s040047 R&S: CR to 34.123-3 V340 to introduce
test case 14.4.3
T1s040048 R&S: Supporting information for approval of
14.4.3
The test case passed on our 3G SS with the Nokia 7600 &
Ericsson U100 UE
with Integrity enabled and Ciphering
disabled.
Please note the approval deadline for this test case should be
08/03/04
(2 weeks), as it was verified using two UEs.
The above
mentioned CRs would be available on the 3GPP server shortly.
Best
regards,
Rishya Theivendran***********************************************************************
PLEASE
VISIT US AT STAND E13B, AT 3GSM WORLD CONGRESS 2004,
CANNES.
********************************************************************
SASKEN
BUSINESS DISCLAIMER
This message may contain confidential, proprietary or
legally Privileged information. In case you are not the original intended
Recipient of the message, you must not, directly or indirectly, use, Disclose,
distribute, print, or copy any part of this message and you are requested to
delete it and inform the sender. Any views expressed in this message are those
of the individual sender unless otherwise stated. Nothing contained in this
message shall be construed as an offer or acceptance of any offer by Sasken
Communication Technologies Limited ("Sasken") unless sent with that express
intent and with due authority of Sasken. Sasken has taken enough precautions to
prevent the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this
email.
***********************************************************************