CR page 1

ETSI SCP WG3 Meeting #10
Sophia Antipolis, France, 20-23 January 2004 / Tdoc SCP3-040023
EP SCP CR-Form-v1.5.0
CHANGE REQUEST
[H1] / 102 223 / CR / [H2]rev / - / [H3]Current version: / 5.4.0 / [H4]
For HELPon using this form, see bottom of this page or look at the pop-up text over the [H5]symbols.
Proposed change affects:[H6] / smart card / X / terminal / server / network
entity
Title:[H7] / Inconsistancies in the description of the Call Connected event and in the length of the UICC/terminal interface transport level
Source:[H8] / WG3
Work item name: [H9] / Date: [H10] / 22-01-2004
Category:[H11] / A / Release: [H12] / REL-5
Use one of the following categories:
F (essential correction)
A (corresponds to a correction in an earlier release)
B (Addition of feature),
C (Functional modification of feature)
D (Editorial modification)
Detailed explanations of the above categories can
be found in 3GPP TR 21.900. / Use one of the following releases:
R99(Release 1999)
REL-4(Release 4)
REL-5(Release 5)
REL-6(Release 6)
REL-7(Release 7)
Reason for change:[H13] / In the procedure description of the Call Connected event, an incoming call is linked to a MO call, and an outgoing call linked to a MT call
The length of the UICC/terminal interface transport level is wrong.
Summary of change:[H14] / MO corrected to MT for incoming calls.
MT corrected to MO for outgoing calls.
Length corrected.
Consequences if [H15]
not approved: / Inconsistancies will remain
New tag value defined within the CR? / If ticked, add document number of related CR to TS 101 220:
Clauses affected:[H16] / 7.5.2.1, 8.59
Other specs[H17] / Other core specifications[H18]
affected: / Test specifications
Other comments:[H19]

EP SCP CR template V 1.5.0CR page 1Claus Dietze/MCC

1

7.5.2Call connected event

7.5.2.1Procedure

If the call connected event is part of the current event list (as set-up by the last SET UP EVENT LIST command, see clause 6.4.16), then when the terminal receives an incoming call connect message (in the case of an MO MT call), or when the terminal sends an outgoing call connect message (in the case of an MT MO call), the terminal shall inform the UICC that this has occurred, by using the ENVELOPE (EVENT DOWNLOAD - call connected) command as in clause 7.5.2.2.

[...]

8.59UICC/terminal interface transport level

This clause applies if class "e" is supported.

Byte(s) / Description / Length
1 / UICC/terminal interface transport level tag / 1
2 / Length (X+1)= ‘03’ / 1
3 / Transport protocol type / 1
4 to 5 / Port number / 2
  • Coding of the Transport protocol type:

-'01': UDP (as defined in RFC 768[9]);

-'02': TCP (as defined in RFC 793[10]);

-all other values are reserved.

  • Coding of the Port number:

-integer.

ETSI

[H1]1 Enter the specification number in this box. For example, 101 220. Do not prefix the number with anything . i.e. do not use "TS".

[H2]1 Enter the CR number here. This number is allocated by the WG and the ETSI support team.

[H3]1 Enter the revision number of the CR here. If it is the first version, use a "-".

[H4]1 Enter the version of the specification here. This number is the version of the specification to which the CR will be applied if it is approved. Make sure that the latest version of the specification (of the relevant release) is used when creating the CR. If unsure what the latest version is, go to .

[H5]1 For help on how to fill out a field, place the mouse pointer over the special symbol closest to the field in question.

[H6]1 Mark one or more of the boxes with an X.

[H7]1 Enter a concise description of the subject matter of the CR. It should be no longer than one line.

[H8]1 Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source.

[H9]1 Enter the title of the related work item which is applicable to the change. This field is mandatory for category F, B & C CRs for release 4 and later.

[H10]1 Enter the date on which the CR was last revised.

[H11]1 Enter a single letter corresponding to the most appropriate category listed below. For more detailed help on interpreting these categories, see the Technical Report 21.900 "3GPP working methods".

[H12]1 Enter a single release code from the list below.

[H13]1 Enter text which explains why the change is necessary.

[H14]1 Enter text which describes the most important components of the change. i.e. How the change is made.

[H15]1 Enter here the consequences if this CR was to be rejected. It is necessary to complete this section only if the CR is of category "F" (i.e. essential correction).

[H16]1 Enter each the number of each clause which contains changes.

[H17]1 Enter an X in the box if any other specifications are affected by this change.

[H18]1 List here the specifications which are affected or the CRs which are linked.

[H19]1 Enter any other information which may be needed by the group being requested to approve the CR. This could include special conditions for it's approval which are not listed anywhere else above.