CT49 Report 110

Third Generation Partnership Project (3GPP)
DRAFT Meeting Report

for
TSG CT WGT
meeting: CT#49
San Antonio, US, 15/09/2010 to 17/09/2010
this draft: Sunday, (2010-09-19) 15:30 [date/time according to secretary's PC time zone setting]
0
1
2
3
4
4.1
4.2
5
5.1
5.2
5.3
6
6.1
6.2
6.3
6.4
7
7.1
7.2
8
9
10
11
11.1
11.2
11.3
11.4
11.5
11.6
11.7
11.8
11.9
11.10
11.11
11.12
All Agenda Items.................................................................................................................................................

Opening of the meeting.......................................................................................................................................
Approval of the agenda and registration of new documents...............................................................................
IPR Declarations..................................................................................................................................................
Reports from CT meetings and other groups.......................................................................................................
Report from last CT meeting.........................................................................................................................
Reports from other groups.............................................................................................................................
Liaison statements...............................................................................................................................................
From 3GPP WGs............................................................................................................................................
From other groups........................................................................................................................................
Outgoing liaisons.........................................................................................................................................
Reports from TSG-CT working groups.............................................................................................................
Reporting from TSG-CT WG1....................................................................................................................
Technical votes..................................................................................................................................................
Working Agreements....................................................................................................................................
Other technical items lacking consensus.....................................................................................................
Release 5 & earlier: Approval of contributions on any work item....................................................................
Release 6............................................................................................................................................................
Release 7............................................................................................................................................................
Release 8............................................................................................................................................................
Support of (G)MSC-S (G)MSC-S Nc Interface based on the SIP-I protocol [SIP_Nc]...........................
CT aspects of System Architecture Evolution [SAES]................................................................................
Multimedia Priority Service [PRIOR].........................................................................................................
Contact Manager for 3GPP UICC applications [eUPHBOOK]..................................................................
Enhancements for VGCS Applications [EVA]............................................................................................
Personal Network Management [PNM].......................................................................................................
OSA Rel-8 [OSA8]......................................................................................................................................
IMS Stage-3 IETF Protocol Alignment [IMSProtoc2]................................................................................
System enhancements for interconnection interfaces between two IMSs [FBI2-TISP2-c1,FBI2IOPSI]..........................................................................................................................................................
IMS enhancements for support of packet cable access [PktCbl].................................................................
OAM&P 8 [OAM8].....................................................................................................................................
Support of Overlap Signalling [Overlap-C3]...............................................................................................
11.13
11.14
11.15
11.16
11.17
11.18
11.19
11.20
11.21
11.22
11.23
11.24
11.25
11.26
11.27
11.28
11.29
11.30
11.31
11.32
11.33
11.34
11.35
11.36
11.37
11.38
11.39
11.40
11.41
11.42
11.43
11.44
11.45
11.46
12
12.1
12.2
12.3
12.4
12.5
12.6
12.7
12.8
12.9
12.10
12.11
12.12
12.13
12.14
12.15
12.16
12.17
12.18
12.19
12.20
12.21
Conferencing Enhancement for Mp interface [eMp]...................................................................................

Customized Alerting Tone (CAT) [CAT_SS]...............................................................................................
Maintenance of TISPAN Release 2 [MAINT_R2]......................................................................................
NGN IMS Supplementary Services; Call Completion on Busy Subscriber (CCBS), Call Completion
No Reply (CCNR) [CCBS_NR]..................................................................................................................
Definition of Communication Wait Service [CW].......................................................................................
NASS Bundled Authentication [NBA]........................................................................................................
MGCF interworking between UUS and SIP [UUSIW]...............................................................................
Paging Permission with Access Control Requirements for CT1 [PPACR].................................................
Media Server Control using the IP Multimedia (IM) Core Network (CN) system [MRFC,
MRFC_TS]..................................................................................................................................................
Definition of 3GPP UICC services over the new high-speed interface [UICCHS].....................................
Interworking between User-to-User Signaling (UUS) and SIP [UUSIW]..................................................
I-WLAN Network Selection Principle (NSP) [IWLANNSP].....................................................................
IMS System enhancements for corporate network access [IMS_Corp]......................................................
3GPP2 Input to Common IMS [CIMS_3GPP2]..........................................................................................
IMS Multimedia Telephony and Supplementary Services [IMSTSS, FA, REDOC_TIS-C1,
REDOC_TIS-C3, REDOC_TIS-C4]...........................................................................................................
Core Network Impacts for A-Interface Over IP [AoIP]...............................................................................
Domain Name System Procedures for Evolved Packet System [SAES-DEPS]..........................................
IMS Restoration Procedures [IMS-RP].......................................................................................................
eCall Transfer data [EDATA].......................................................................................................................
IMS Service Continuity [IMS-Cont]...........................................................................................................
Earthquake and Tsunami Warning System [ETWS]....................................................................................
IMS Centralized Service Control (ICSRA) [ICSRA]..................................................................................
Mobility between 3GPP-WLAN Interworking and 3GPP Systems [IWLAN_Mob]..................................
CS Fallback in EPS [SAES-CSFB].............................................................................................................
Service-Level Interworking for Messaging Services [MESSIW]................................................................
Encoding formats, transport formats and media description signalling for interworking, QoE, and
other enhancements to MTSI-MHI [MTSI_eMHI].....................................................................................
Customized alerting tone (CAT) service in 3GPP CS domain [CAT-3G_CS].............................................
IMS AS service data descriptions for AS interoperability [IMS_ASIO].....................................................
Stage 3 for SRVCC [SAES_SRVCC]..........................................................................................................
CSG and idle mode mobility for LTE Home eNodeB [HomeNB-LTE]......................................................
CSG and idle mode mobility for 3G Home eNodeB [HomeNB-3G]..........................................................
IWF between MAP based and Diameter based interfaces [SAES-MAP2Diam].........................................
(Small) Technical Enhancements and Improvements for Rel-8 [TEI8].......................................................
Any other Rel-8 Work item or Study item...................................................................................................
Rel-9..................................................................................................................................................................
Stage 3 Enhancements of IMS CAT Supplementary Service [eCAT-SS]....................................................
(Small) Technical Enhancements and Improvements for Rel-9 [TEI9].......................................................
User Data Convergence [UDC-CN]............................................................................................................
Support of Personal Area Networks and Enhancements to Personal Network Management
[PAN_EPNM]..............................................................................................................................................
IMS Services Centralization and Continuity [IMS_SCC-ICS_I1]..............................................................
CS-IBCF and CS-TrGW definition in 3GPP specifications [CS-IBCF]......................................................
IMS IBCF TrGW definitions in 3GPP (Ix interface) [IMS_IBCF]..........................................................
Value added services for SMS interface and signaling flow [VAS4SMS]..................................................
IMS ALGCF IMA-MGW definitions in 3GPP (Iq interface) [IMS_ACCF]............................................
Completion of IMS Restoration Procedures [eIMS_RP].............................................................................
Control Plane LCS in the EPC [LCS_EPS-CPS].........................................................................................
CN aspects of Local Call Local Switch [LCLS-CN]...................................................................................
MBMS support in EPS [MBMS_EPS]........................................................................................................
Operational description of the Inter-IMS Network to Network Interface [II-NNI].....................................
SRVCC support for IMS Emergency Calls [IMS_EMER_GPRS_EPS-SRVCC].......................................
Public Warning System [PWS-St3].............................................................................................................
Enhancements to IMS Centralized Services [IMS_SCC-ICS]....................................................................
IMS Service Continuity Enhancements: Service, Policy, Interactions and Inter UE Transfer
[IMS_SCC-SPI]...........................................................................................................................................
Support for IMS Emergency Calls over GPRS and EPS [IMS_EMER_GPRS_EPS]................................
Service Specific Access Control [SSAC].....................................................................................................
Customized Ringing Signal [CRS]..............................................................................................................
12.22
12.23
12.24
12.25
12.26
12.27
12.28
12.29
13
13.1
13.2
13.3
13.4
13.5
13.6
13.7
13.8
13.9
13.10
13.11
13.12
13.13
14
14.1
14.2
15
15.1
15.2
15.3
15.4
15.5
16
16.1
16.2
16.3
17
18
19
Enhancements for Completion of Communications Supplementary Service [eMMTel-CC]......................

Multiple PDN to the Same APN for PMIP-based Interfaces [MUPSAP]...................................................
Support of Home NB and Home eNB enhancements [EHNB]...................................................................
IMS Media Plane Security [MEDIASEC]...................................................................................................
Access Network Discovery and Selection Enhancements [eANDSF]........................................................
Definition of Ml interface for Control Plane LCS [EMC2].........................................................................
PCC Enhancements [PCC-Enh]...................................................................................................................
Any other Rel-9 Work item or Study item Study item.................................................................................
Release 10..........................................................................................................................................................
IP-SM-GW enhancements for CPM-SMS Interworking.............................................................................
IMS Stage-3 IETF Protocol Alignment [IMSProtoc4]................................................................................
Call Completion on Not Logged-in.............................................................................................................
IP-SM-GW enhancements for CPM-SMS Interworking.............................................................................
Enhanced User Data Convergence (UDC) Model.......................................................................................
Stage 3 for Local IP Access.........................................................................................................................
Further improvements of II-NNI Stage 3 based on operational feedback and evolution of other
specifications................................................................................................................................................
Optimal Media Routeing..............................................................................................................................
IP Flow Mobility and seamless WLAN offload...........................................................................................
AT Commands for IMS-configuration.........................................................................................................
Selected IP Traffic Offload..........................................................................................................................
Any other Rel-10 Work item or Study item.................................................................................................
Rel-10 work planning...................................................................................................................................
Approval of WIDs.............................................................................................................................................
Revised WIDs..............................................................................................................................................
New WIDs....................................................................................................................................................
TSG CT work organization................................................................................................................................
Principles for work organization within CT................................................................................................
Terms of Reference......................................................................................................................................
Support Arrangements.................................................................................................................................
Working methods.........................................................................................................................................
Future Meeting Schedule.............................................................................................................................
Specification in TSG-CT domain......................................................................................................................
Specification status......................................................................................................................................
3GPP TS/TR for information.......................................................................................................................
3GPP TS/TR for approval............................................................................................................................
Review of 3GPP Work Plan...............................................................................................................................
Any other business.............................................................................................................................................
Close of Meeting...............................................................................................................................................
Note: Hyperlinks to tdocs will work only if the present report is in a subdirectory named "report" and the tdocs
themselves are in a parallel subdirectory names "docs".
All Agenda Items
Opening of the meeting
Approval of the agenda and registration of new documents
CP-100432 CT Agenda
Source: CT Chairman
Decision:
The document was Revised to CP-100433.
CP-100433 Proposed allocation of documents to agenda items

Source: CT Chairman
(Replaces CP-100432)
Decision:
CP-100434 Allocation of documents to agenda items for CT#49: status on Wednesday morning
Source: Vice Chairman
Abstract:
Chairman Mr. Hannu Hietalahti opened the meeting on Wednesday 15th September 09:00. Ms. Luisa Marchetto of
AT&T (ATIS) welcomed the delegates to San Antonio on behalf of the hosts the North American Friends of 3GPP and
wished TSG CT a successful meeting.
CT Chairman reminded the delegates to
Register to meetings they attend
Pick up their badge
Sign the attendance sheet
MCC or chairman will not do this for you and the attendance list cannot be changed after the meeting is closed
CT Chairman reminded that the members should take note that they are hereby invited:
To investigate in their company whether their company does own IPRs which are, or are likely to become Essential in
respect of the work of the Technical Specification Group.
To notify the Chairman, or the Director-General of their respective Organizational Partners, of all potential IPRs that
their company may own, by means of the IPR Statement and the Licensing declaration forms
The meeting was chaired by Mr. Hannu Hietalahti, (Chairman, Nokia). Additional support was provided by Ms. Luisa
Marchetto (Vice Chairman, AT&T), Mr. Rouzbeh Farhoumand (Vice Chairman, Huawei), Mr. Adrian Neal (Vice
Chairman, Vodafone) and Mr. Kimmo Kymlinen (CT Secretary, MCC).
Decision:
CP-100435 Allocation of documents to agenda items for CT#49: status on Wednesday evening
Decision:
CP-100436 Allocation of documents to agenda items for CT#49: status on Thursday evening
Decision:
CP-100437 Allocation of documents to agenda items for CT#49: status After the Thursday
Decision:
CP-100651 Allocation of documents to agenda items for CT#49: status After the meeting
Decision:
The document was Noted.
IPR Declarations
Reports from CT meetings and other groups
4.1
Report from last CT meeting
CP-100438 CT#48 meeting report for approval

Source: MCC
Decision:
CP-100617 CT#48 meeting report for approval

Source: MCC
Decision:
4.2
The document was Approved.
Reports from other groups
CP-100439 IETF status report

Source: CT Chairman
Abstract:
Teleconferences
-
3GPP internal telco on the 28th of September 2010
3GPP IETF telco to be agreed right after the above 3GPP internal telco
Rel-6 dependencies
-
All clear, Rel-6 was removed from the dependency document
Rel-7 dependencies
-
No milestones
Rel-8 dependencies
-
3 New RFCs
1 draft has gone to IESG evaluation
3 new dependencies identified
Rel-9 dependencies
-
1 draft approved by IESG
1 new addition to the list
Rel-10 dependencies
-
1 new draft identified
Critical Rel-7 dependencies:

draft-drage-sipping-rfc3455bis
-
Should proceed as AD sponsored draft
New version needed
draft-ietf-sipcore-location-conveyance
-
Discussion on how the interim nodes add their location information
draft-drage-sipping-service-identification
-
IESG evaluation
Revised based on comments received in IETF #78 but still no progress
draft-patel-ecrit-sos-parameter is in AD evaluation
Agreed to proceed as AD sponsored document
3GPP only needs an indication of special registration
Discussion on the use case still going on
Critical Rel-8 dependencies:

draft-ietf-bliss-call-completion
-
The editor still needs to progress the work in IETF
draft-ietf-mmusic-ice-tcp was added recently

-
What is the real 3GPP use case of this draft?
draft-ietf-sipcore-keep
-
Recently updated in September 2010
draft-ietf-sipcore-199
-
New draft, already in IESG approval
Rel-9 dependencies:
draft-ietf-mattson-mikey-ticket
-
Approved by IESG
draft-ietf-dawes-dispatch-mediasec-parameter
-
Needed for IMS media security
Rel-10 dependencies:
draft-ietf-mext-nemo-pd
-
New addition to the list
Progress since previous TSGs:

New RFCs:
-
draft-ietf-mext-binding-revocation (RFC 5846)
draft-ietf-netlmm-grekey-option (RFC 5845)
draft-ietf-netlmm-pmipv6-heartbeat (RFC 5847)
Approved by IESG and now in RFC editors queue:

-
draft-mattson-mikey-ticket
IESG evaluation started:

-
draft-das-mipshop-andsf-dhcp-options
3GPP actions required:

-
draft-ietf-sipcore-location-conveyance
The real need to add location information along the path?
and how to encode it?
The following critical drafts are followed by TSG CT action points:

-
draft-drage-sipping-rfc3455bis (Keith Drage / ALU)
draft-drage-sipping-service-identification (Keith Drage / ALU)
draft-ietf-patel-ecrit-sos-parameter (Milan Patel / InterDigital)
draft-ietf-bliss-call-completion (Roland Jesske / DT)
draft-ietf-mmusic-ice-tcp (Hannu Hietalahti / Atle Monrad)
Discussion:
It was commented that "draft-drage-sipping-service-identification" is on progress. RFC should be published in near
future.
Decision:
5
5.1
Liaison statements
From 3GPP WGs
CP-100527 Reply LS on Addition of PSTN-ISDN Emulation Support to AoC Service

Source: TSG CT WG1
Abstract:
CT1 asks SA5 to consider using references in 3GPP TS 32.280 to ETSI TS 183 043 to avoid any inconsistent
duplicated solutions in 3GPP and ETSI TISPAN.
Decision:
CP-100528 LS on CSG Change Reporting Support Indication

Source: TSG CT WG4
Abstract:
TSG CT action is needed, to consider the CT4 CRs in the light of SA2 feedback (if any).
CT4 have considered the use of separate flags to user location information change reporting and CSG information
change reporting an essential correction on Rel-9.
SA2 is requested to confirm or correct this assumption and CT4 have already provided two CRs based on this
assumption in CP-100453 can be approved as it stands.
Decision:
CP-100529 MSISDN relationship with C-MSISDN

Source: TSG CT WG4
Abstract:
TSG CT action is needed, to consider the CT4 CRs in the light of SA2 feedback (if any).
CT4 is asking SA2 to determine whether C-MSISDN is the same as MSISDN for CS access. If it is the same, then CT4
would also need to know whether C-MSISDN in multi-numbering scenario is equal to basic MSISDN or any MSISDN
for CS access? The current CT4 CRs C4-102157 and C4-102419 are valid, unless objection is heard from SA2.
The related CRs are in CP-100448 and 455.
If CP-100448 and 455 are not approved, then 522 can be approved as they stand.
Decision:
CP-100533 LS on direct stage 3 work for NIMTC functionality

Source: TSG SA WG1
Abstract:
CT and the CT WGs are requested to study the NIMTC functionality of Rel-10 and give feedback to the next SA1
meeting on the feasibility of candidate items in Rel-10 time frame:
PS only subscription with or without MSISDN
Remote MTC device configuration without MSISDN
Discussion:
Alcatel-Lucent commented that incoming LS from SA2 in CP-100607 is related to this topic.
Decision:
CP-100534 Reply LS to LS on Remote Access CPNs

Source: TSG SA WG1
Abstract:
For information to TSG CT.
SA1 have decided that they need to consider the Remote Access requirements before 3GPP continues with the work.
SA1 request also ETSI TISPAN input.
Decision:
CP-100535 Reply LS on I1 and Gm

Source: TSG SA WG2
Abstract:
SA2 have clarified that the I1 interface is to be used only when Gm is not available. This is how it was already before,
but CT1 was asking for clarification which SA2 make in their CR that is attached.
Discussion:
CT1 chairman commented that all CT1 specifications are inline with the LS.
Decision:
The document was Agreed.
CP-100537 LS on co-ordination of SDO input to ITU-T Q.1741.7

Source: TSG SA
Abstract:
This LS was sent as the result of ITU-T request for input to Q.1741.7 corresponding to 3GPP Rel-9.
Decision:
CP-100565 LS on Progress of the Local Call Local Switch Feasibility Study

Source: CT4
Abstract:
The required TSG CT action is to review and decide on the CT4 output TR 23.889 and proposed updates on it.
Discussion:
There was no reply from GERAN or SA3 LI.
It was clarified that CT4 agreed to start at next meeting with normative work. CT4 further agreed that when
incorporating content of the TR into normative specifications, any identified errors will only be corrected in the TS. To
speed up the work it is not intended to do maintenance on the TR.
CT Plenary confirmed CT4 proposal with understanding that some errors will be corrected related to optional solutions
only in 3GPP TS and TR if approved in this Plenary will not be maintained.
Decision:
CP-100607 LS on Release 10 NIMTC Conclusion

Source: TSG SA WG2
Abstract:
For TSG CT action (in the WGs?)
SA2 have found out that it is not possible to complete all stage 2 issues for WI NIMTC. In order to stabilize Rel-10 they
have therefore included the initial feature set that they believe to be possible in Rel-10 time frame:
Common Service Requirements: Addressing, Identifiers, Overload and Congestion Control, Subscription Control
MTC Features: Monitoring, Low Mobility, Time Control
NIMTC work is expected to continue in Rel-11.

Discussion:
CT WGs were request to do related stage 3 work (indicated in CP-100533) before March 2011 without changing the
schedule.
CT4 Chairman commented that WID on NIMTC was approved in CT#48.
It was agreed that detailed reply should be sent from CT1/CT4 WG meeting in October.
CT WGs need to have clear guidance of related work before CT#50. The topics which can not be covered or seen
technically visible before March 2011 shall be postponed to Rel-11. Also NIMTC work is expected to continue in Rel11.
Decision:
CP-100610 LS on Mobile Wireless access systems providing telecommunications for a large number of
ubiquitous sensors and/or actuators scattered over wide areas in the land mobile service
Source: TSG RAN
Abstract:
TSG CT is kindly asked to review the attached document RP-100871 and to provide to 3GPP RAN their endorsement or
required modifications before the end of TSG RAN #49 (i.e. by Thursday 16th September). The document will then be
submitted to SA#49.
Decision:
CP-100616 LS on Schedule, Structure, and Deliverables toward the completion of the first Release of Rec.
ITU-R M.[IMT.RSPEC]
Source: TSG RAN
Decision:
5.2
From other groups
CP-100530 Liaison Regarding MSF SAE/LTE Interoperability Event

Source: MultiService Forum (MSF)
Abstract:
MultService Forum (MSF) report from their SAE/LTE interoperability event. They also inform 3GPP of planned further
steps and request 3GPP feedback on additional scenarios and interfaces that deserve priority in testing.
Discussion:
CT Plenary agreed that all individual members are request give their comments directly to MSF.
Decision:
CP-100531 Consent of Recommendation G.9971 Requirements of transport functions in IP home

networks
Source: ITU-T Study Group 15
Abstract:
ITU-T SG15 has agreed the new draft recommendation G.9971 Requirements of transport functions in IP home
networks.
Decision:
CP-100532 LS to 3GPP CT1 on mechanism to disable SIGCOMP.

Source: GSMA RILTE #8
Abstract:
GSMA requests a mechanism to disable SigComp for high bandwidth access technologies, such as LTE.
Discussion:
CT1 Chairman clarified that the corresponding CRs are provided for approval in CP-100519.
Alcatel-Lucent had some concern in last CT1 meeting that proposed solution has the implication that it could increases
the signalling in existing visited networks with no control by the visited Network Operator. The justification for
disabling SigComp comes from the high bandwidth RAT like LTE, but the CRs are written so that the disabling of
SigComp, if done, affects all RATs.
Decision:
CP-100536 Reply LS on AT Commands for UICC interaction

Source: SCP
Abstract:
ETSI SCP acknowledges the start of new WID on AT commands for UICC interaction and request for updates on major
milestones in this work.
Discussion:
CT1 Chairman clarified that the work shall be done in TS 27.007.
CT1 was requested to share further information with SCP as necessary as the work progresses.
Decision:
CP-100538 LIAISON TO EXTERNAL ORGANIZATIONS ON THE SCHEDULE AND TECHNICAL

AND ADMINISTRATIVE INPUTS FOR THE COMPLETION OF THE FIRST RELEASE OF
RECOMMENDATION ITU-R M.[
Source: ITU Working Party 5D
Abstract:
This LS has an impact on Rel-10 schedule. Based on the ITU-R target dates TSG RAN needs to aim at freezing their
part of the Rel-10 in March 2011 and to avoid non-backwards compatible changes after June 2011. The schedule of the
whole Rel-10 should be aligned with that.
It is up to TSG SA to determine the release schedule, but if this foreseen schedule is seen problematic for TSG CT, then
we should raise our concerns now and report to TSG SA.
Decision:
5.3
Outgoing liaisons
CP-100618 Reply LS on Schedule, Structure, and Deliverables toward the completion of the first Release
of Rec. ITU-R M.[IMT.RSPEC]
Source: CT Chairman
Abstract:
CT Plenary asks TSG RAN and TSG SA to
use a list of CN specifications drawn with the above criteria as the basis for the TSG CT part of M.[IMT.RPSEC]
and to inform TSG CT of the process that will be used to consolidate the TSG input into 3GPP deliverable.
Decision:
CP-100622 Reply LS on Mobile Wireless access systems providing telecommunications for a large number
of ubiquitous sensors and/or actuators scattered over wide areas in the land mobile service
Source: Telecom Italia
Discussion:
The revised text was rephrased under the bullet list.
Decision:
CP-100629 LS on LCLS
Source: Ericsson
Decision:
CP-100630 Reply LS on Mobile Wireless access systems providing telecommunications for a large number
of ubiquitous sensors and/or actuators scattered over wide areas in the land mobile service
Source: Telecom Italia
Decision:
CP-100643 Reply LS on Schedule, Structure, and Deliverables toward the completion of the first Release
of Rec. ITU-R M.[IMT.RSPEC]
Source: CT Chairman
Decision:
Source: Ericsson
Discussion:
The action section needs to be rephrased and CT#50 meeting date and location need to be fixed.
Decision:
Source: Ericsson
Abstract:
TSG CT has approved the TR 23.889 feasibility study on Local Call Local Switch with one sustained objection.
CT Plenary agreed that the following issues are considered still open and need to be further studied by CT4 and
GERAN 2:
1. Whether the LCLS-Correlation Request IE may be specified as an optional IE.
2. Whether a BSS implementation may ignore the LCLS Correlation Request IE and always perform call leg correlation
3. SID frame transmission through the CN for LCLS connections
CT plenary asks CT4 and GERAN2 to conclude on these issues during the normative specification work.
Discussion:
TSG CT has approved the TR 23.889 feasibility study on Local Call Local Switch with one sustained objection.
GERAN 2:
Decision:
6
6.1
Reports from TSG-CT working groups

Reporting from TSG-CT WG1
CP-100476 CT1 Chairman report

Source: CT1 Chairman
Abstract:
CT1 has had two meetings since CT #48, CT1#65 which was collocated with CT4 in Dublin and CT1#66 collocated
with CT3 and CT4 in Xian. During the meeting in Dublin, CT1 had no official joint sessions, while during the meeting
in Xian the group had a joint session with CT4 on Correction of MME/SGSN Node Type Indication for mapping LAC
to GUTI, on HLR overload and on RP-OA modification in SMS-Router.
CT1 has also for this plenary very few CRs for pre-release 8. Also for Rel-8 the trend with less CRs continue, which is a
good sign and indicates stability. For Rel-9, the amount of CRs is also modest for a release that just has been frozen.
The effort to remove the remaining editors notes in the frozen releases is however still not completed. Rel-10 progress
is according to schedule for most WIs. For several of the work items, it is obvious that conference calls and other offline activities secure that the progress as well as the quality of the CRs provided to the meeting is good. The WIrapporteurs do a very good job between the meetings to secure progress.
CT1 has agreed two new WIDs and endorsed the CT1-aspects of three CT-wide WIDs from CT4. For Rel-10, the work
plan gives a good overview of the work that is needed and shows good progress for completion by March 2011. The
creation of the Rel-10 versions of the specifications has clearly moved some focus away from correction of minor flaws
in the frozen releases.
The group split at CT1#65 and CT1#66 both times for 3 days and handled legacy & SAE in parallel with pure IMSissues. During CT1#65, the group also split to handle inhibition of ACL (Allowed CSG List) under the WI EHNB-CT1.
As SA1 has changed the service requirements, CT1 has not been able to conclude on this Rel-9 WI yet.
Discussion:
CT1 indicates they are on track with completion of Rel-10 work by March 2011.
CT1 Chairman clarified that all work on Rel-9 is now completed, except for an outstanding issue for EHNB-CT1. The
reason for the missing 5% is that the group failed to agree the stage 3 details for the late requirement from SA1 in
CT1#65. At CT1#66, it was commented that the requirements from SA1 were modified, leading to again putting the
completion on this on hold. The issue will be revisited and hopefully agreed at CT1#67 or CT1#68 in order to complete
the work at CT#50. Telco has been set up to align stage 3 with the latest CSG stage 1 requirements that are now well
understood.
It was found out that no LCLS work is required in CT1, so that can be marked as complete.
SA5 CR numbers were not available at the time of CT1, so the formal CR linkage in the CT1 CRs that depend on those
SA5 CRs is broken and would theoretically require revision of those CT1 CRs in TSG CT when the CR numbers of the
related SA5 CRs become available. Since the WGs are now working more in parallel than they used to in the past very
long releases, this is becoming more important now.
CT Chairman thanked CT1 their good work during this Plenary period.
Decision:
CP-100477 C1-65 meeting report

Source: MCC
Decision:
CP-100478 draft C1-66 meeting report

Source: MCC
Decision:
6.2
CP-100539 CT3 Status Report to CT Plenary

Source: CT3
Abstract:
Since the last TSG CT plenary, the following meeting has taken place:
CT3#59
23-27 August 2010, Xian, CHINA
We had a normal workload this time (324 documents handled) and the meeting could be closed around 14:30 on
Friday.
During the meeting there was a breakout session on PCC topics chaired by Vice-Chairman Qiao Weihua.
Major problems/controversial issues
None.
Major achievements
97 CRs agreed.
CT3 work on three Rel-10 work items completed:
o PCRF Restoration (TR 29.816 submitted for plenary approval).

o CPM-SMS message interworking.
o Call Completion Not Logged in.
2 new Rel-10 WIDs were endorsed.
Discussion:
This Study Item is aiming to study failure and restoration aspects of the PCRF and the related communication
infrastructure. The work on the TR has progressed well, and is submitted to this plenary for approval. An LS was sent to
CT4 to ask for stage 2 requirements for PCRF Restoration.
CT Plenary agreed that when principles are agreed in CT4 then CT3 can follow the principle.
The first 3 Rel-10 WIDs are already completed
PCRF restoration
CPM-SMS message interworking
Call Completion Not Logged in
No Rel-10 WIs were indicated at this point of being in danger of not being completed by March 2011.
Decision:
CP-100540 Draft Report from CT3#59

Source: CT3
Decision:
6.3
CP-100440 CT4 Status Report

Abstract:
CT4 have had two meeting since the last CT plenary meeting. The meeting CT4#49bis was held in Dublin, Ireland from
28th June - 2nd July 2010 kindly hosted by European friends of 3GPP and CT4#50 was held in Xian, China kindly
hosted by Huawei.
Release 10
Local call local switch (LCLS)
CT4 made good progress on the technical report on LCLS TR 23.889. The TR 23.889 v 1.5.0 (CP 100474) is seen as
completed and therefore sent for approval. This version of the TR is again send to GERAN2 and SA3LI for final
checking and to provide comments (see LS C4-102411).
CT4 discussed and updated the LCLS WID CP 100470. We agreed to start at our next meeting with normative work. We
further agreed that when incorporating content of the TR into normative specifications, any identified errors will only
be corrected in the TS. To speed up the work it is not intended to do maintenance on the TR.
User Data Convergence (UDC)
CT4 started the work on the 3 new Rel-10 WIDs. The documents provided on these topics were discussed and proved
very controversial
UDC data model
On the UDC data model we started the work on the TR29.935 the new version is available in C4-102423 and agreed as
basis for future work.
UDC evolution
The TR on UDC evolution the new version is available in C4-102424 and agreed as basis for future work.
Enhanced UDC
On enhanced UDC, CT4 had one CR which was discussed and then postponed to the next meeting..
SIPTO
CT4 started the work on SIPTO and agreed a first set of CRs, which are provided in CP-10465 for approval.
LIPA
CT4 started the work on LIPA but did not provide any CRs for approval at this time.
MME restart
CT4 had a discussion on the possible problems which might occur when an MME restarts and loses all his data. In this
case, UE cannot receive incoming packet from external network and cause loss of terminating call in voice service over
LTE. CT4 also discussed some CRs which provided solutions for this problem. CT4 agreed that MME may certainly
fail, but this is not a frequent occasion. This does not meet the criteria for a FASMO, therefore no enhancement was
agreed for Release 8 or 9. Furthermore, CT4 agreed to start working on a TR to analyse the issue of node failure in
detail. The new SID is provided in CP 100473 for approval.
Notification of supported features between peer GTP-C entities
For MAP and Diameter based interfaces, CT4 has introduced a generic framework for dynamic feature discovery. Those
functionalities allow the introduction of features which are not backward compatible. For GTP based interfaces, this had
not been introduced so far. We agreed on a CR to support this dynamic feature discovery also for GTPv2 based
interfaces (see CP-100469).
Any other topics for Release 10
CT4 agreed enhancements and corrections in the following areas:
CP-100466
Enhancements to IMS set1
CP-100522
Enhancements to IMS set2
CP-100468
Enhancements to SMS
CP-100469
Enhancements to GTP
Questions for advice and decision

The drafting guidelines require the usage of the Telelogic SDL tool for SDLs. In the past, licenses for the tool were
provided via ETSI for a limited time. IBM, who is now the owner of the Tool, has stopped this year the provision of
license for a limited time limit. ETSI is working on a work around. Some delegates got the information how this work
around should work but it still does not work. For some delegates, the workaround does not work because their
company policy does not allow them to have administration rights on their laptop. So those delegates who had a license
until June and finalised their CRs within this time period provided CRs using the SDL tool. Those who were not able to
get a license and did not manage to get the workaround running have used Visio to draw their SDLs. CT4 ask to change
the drafting rules to allow Visio for drawing SDLs. One argument to use the output files of SDL tool to generate
machine readable code. At least none of the companies present at the meeting seem to make use of this functionality.
Discussion:
LCLS is seen to still require a lot of work to get it completed by March 2011. The TR 23.889 is seen as sufficiently
stable for the normative work and to save time, CT4 intends to concentrate fully on the normative work and not
maintain the TR any more.
User Data Convergence (UDC) has proved very controversial.
Rel-9 corrections are now being considered more strictly on the basis on whether they are really essential or not.
FASMO corrections only.
Question on how to overcome the tool problem that has now been detected in the use of limited licences to use the
Telelogic SDL too that has been used in the formal SDL description part of some CT4 specifications. None of the
companies participating CT4 were using the automatic generation of machine readable code feature of the Telelogic
tool. Telelogic also supports automatic syntax checking of the diagrams which Visio does not.
Some solution is required urgently to solve this problem. Until a real solution can be identified, an interim workaround
allowing the delegates to document their CRs using Visio and MCC implementing the approved CRs using Telelogic.
It was agreed that CT Plenary recommends to SA Plenary to accept CR in CP-100572 which allow WGs to use
Microsoft Visio for drafting SDLs.
The latest SA2 meeting was after all the CT WGs so the output of that meeting is not analysed yet.
Decision:
CP-100441 CT4 meeting reports after CT#48

Source: MCC
Decision:
6.4
CP-100583 Chairman's status report for CT6#54

Decision:
CP-100584 Draft report of CT6#54

Source: MCC
Decision:
CP-100611 Chairman's status report for CT6#54

Abstract:
TSG CT WG6 #56
24 - 27 August 2010
Venice, Italy
(hosted by European Friends of 3GPP in Telecom Italia premises)
TSG CT6#125-LTE testing adhoc
05 August 2010
Conference call
CT WG6#56 was attended by 23 delegates
117 new documents processed
4 postponed documents processed
6 LSs were received
4 LSs were sent
29 CRs were agreed
3 CRs were rejected

12 CRs postponed
4 new WIDs agreed
1 revised WID
Referencing of ETSI TC SCP specifications
Complete set of specifications updated for Rel-7 and Rel-8.
Rel-9 missing (except TS 31.101 and TS 31.111)
Action for next meeting to finalise Rel-9
Update of test specs (TS 31.121 and TS 31.124) agreed (C6-100392, C6-100393 found in CP-100592)
Referencing of 3GPP2 specifications
Action item from CT plenary to check all specifications and update references to specific versions
Only one change required (TS 31.102) (C6-100387 found in CP-100587)
Release 8
Test interworking of LTE Terminals with the USIM (SAES-USIM_LTE-Test) (03/2010)
Completeness: 95%
Some test cases related to NMR in PROVIDE LOCAL INFORMATION could not be solved, as related CRs to TS
31.111 could not be agreed at CT6#56 and were postponed
WID updated (C6-100406) to reflect shift in time
Release 10
Study on UCC access to IMS (IMS-UICC) (12/2010)
Completeness: 15%
Skeleton for TR 31.828 agreed
First proposal discussed
Ad-hoc meeting (conference call) scheduled for 15 October. Invitation to CT6, CT1, CT4 and SA2
Discussion:
With the completion of ETSI SCP reference updates, Rel-7 and Rel-8 specifications are now stable also for the UICC
interface implementation. Rel-9 work has been started, with the intention to complete in the next TSG cycle.
Update of 3GPP2 references is also complete, with just one CR required.
UICC Call control for IMS as the new WI was seen to require good progress to make it complete by March 2011 but all
other CT6 work was seen to be well on track for completion in Rel-10 time frame.
Decision:
7
7.1
Technical votes
Working Agreements
No discussion in this meeting.
7.2
Other technical items lacking consensus
Release 5 & earlier: Approval of contributions on any work item
CP-100591 4 CRs against TS 51.010-4 for TEI4 (and mirrors)

Source: CT6
Discussion:
CR C6-100364 and C6-100397 are taken out from CP-100591 since the error in CR cover page.
C6-100364 revised in CP-100619
C6-100397 revised in CP-100620
The rest fo the CRs are approved.
Decision:
CP-100619 Essential correction of test 27.22.4.9.3

51.010-4 CR-0070 rev 2 (Rel-4) v..
Source: Sagem Orga
Discussion:
This CR is taken out from CP-100591 because of error in causes affected.
Decision:
CP-100620 Essential correction of test 27.22.4.9.3

31.124 CR-0221 rev 2 (Rel-9) v..
Source: Sagem Orga
Discussion:
This CR is taken out from CP-100591 because of an error in causes affected.
Decision:
Release 6
10 Release 7
CP-100442 Corrections on IMS
Source: CT4
Decision:
CP-100481 CR pack on EMC1

Source: CT1
Discussion:
Qualcomm commented that a CR 24.229-3253 is drafted against a wrong specification version.
C1-103386 is revised to CP-100621. On the other hand RIM challenged if this is a frequent and serious misoperation
for Rel-7.
All the other CRs are approved.
Decision:
CP-100482 CR pack on FBI

Source: CT1
Decision:
CP-100483 CR pack on ServID

Source: CT1
Decision:
CP-100484 CR pack on VCC

Source: CT1
Decision:
CP-100541 CRs on IMS-CS Interworking (Rel-7 and mirrors)

Source: CT3
Decision:
CP-100542 CRs on IMS-IP Interworking (Rel-7 and mirrors)

Source: CT3
Decision:
CP-100543 CRs on PCC (Rel-7 and mirrors)

Source: CT3
Decision:
CP-100594 1 CR against TS 31.111 for TEI7

Source: CT6
Discussion:
CT6 Chairman clarified that CT6 will provide missing Rel-8 and Rel-9 CRs in CT#50. Rel-8 and Rel-9 CRs contain
also other changes which could not be agreed in the last CT6 meeting.
Decision:
CP-100605 CRs on IMS-IP Interworking (Rel-7 and mirrors)

Source: CT3
Discussion:
CR revision numbers were not changed since only a CR package cover page was corrected.
Decision:
CP-100621 Correction of Stage 3 misalignment with Stage 1 and Stage 2 on use of SIP 380 response.
24.229 CR-3253 rev 3 (Rel-7) v..
Source: Ericsson
Decision:
11 Release 8
11.1 Support of (G)MSC-S (G)MSC-S Nc Interface based on the SIP-I
protocol [SIP_Nc]
11.2 CT aspects of System Architecture Evolution [SAES]

CP-100443 Corrections on SAE/LTE set 1
Source: CT4
Discussion:
It was reminded that exact subclauses should be used on CR cover page (clauses affected) instead of general ones.
Decision:
CP-100444 Correction on GTP set 1

Source: CT4
Decision:
CP-100445 Correction on GTP set 2

Source: CT4
Decision:
CP-100485 CR pack on SAES

Source: CT1
Decision:
CP-100523 Correction on GTP set 3 SAES

Source: CT4
Abstract:
SA2 did not agree their CRs related with this CT4 CR pack in their last meeting because lack of time. The missing CRs
have been input directly to TSG SA in SP-100459.
Discussion:
CR is conditionally approved.
Decision:
CP-100544 CRs on SAES (Rel-8 and mirrors)

Source: CT3
Discussion:
C3-100814, C3-100815, C3-100816 and C3-100817 clauses affected are missing.
C3-100814 is revised to CP-100623
The other CRs are approved
Decision:
CP-100576 NAS Cause Code values

29.272 CR-0274 rev 2 (Rel-8) v..
Source: Motorola
Decision:
CP-100577 NAS Cause Code values

29.272 CR-0275 rev 2 (Rel-9) v..
Source: Motorola
Decision:
CP-100579 Corrections on SAE/LTE set 2

Source: CT4
Discussion:
CRs are revised in CP-100576 and CP-100577.
Decision:
CP-100623 3GPP References to 3GPP2 specifications

29.213 CR-0271 rev 1 (-) v..
Source: Ericsson
Decision:

29.213 CR-0272 rev 1 (Rel-9) v..
Source: Ericsson
Decision:

29.214 CR-0146 rev 1 (Rel-8) v..
Source: Ericsson
Decision:

29.214 CR-0147 rev 1 (Rel-9) v..
Source: Ericsson
Decision:
11.3 Multimedia Priority Service [PRIOR]

11.4 Contact Manager for 3GPP UICC applications [eUPHBOOK]

11.5 Enhancements for VGCS Applications [EVA]

11.6 Personal Network Management [PNM]

11.7 OSA Rel-8 [OSA8]

11.8 IMS Stage-3 IETF Protocol Alignment [IMSProtoc2]

CP-100486 CR pack on IMSProtoc2
Source: CT1
Decision:
11.9 System enhancements for interconnection interfaces between two IMSs

[FBI2-TISP2-c1,FBI2-IOPSI]
CP-100545 CRs on the Inter-IMS NNI (Rel-8 and mirrors)
Source: CT3
Decision:
11.10 IMS enhancements for support of packet cable access [PktCbl]

CP-100487 CR pack on PktCbl-Intw
Source: CT1
Decision:
11.11 OAM&P 8 [OAM8]

11.12 Support of Overlap Signalling [Overlap-C3]

11.13 Conferencing Enhancement for Mp interface [eMp]

11.14 Customized Alerting Tone (CAT) [CAT_SS]

11.15 Maintenance of TISPAN Release 2 [MAINT_R2]

CP-100488 CR pack on MAINT_R2
Source: CT1
Decision:
11.16 NGN IMS Supplementary Services; Call Completion on Busy

Subscriber (CCBS), Call Completion No Reply (CCNR) [CCBS_NR]
CP-100489 CR pack on CCBS-CCNR
Source: CT1
Decision:
CP-100546 CRs on CCBS/CCNR Interworking (Rel-8 and mirror)

Source: CT3
Decision:
11.17 Definition of Communication Wait Service [CW]

11.18 NASS Bundled Authentication [NBA]

11.19 MGCF interworking between UUS and SIP [UUSIW]

11.20 Paging Permission with Access Control Requirements for CT1 [PPACR]
11.21 Media Server Control using the IP Multimedia (IM) Core Network (CN)
system [MRFC, MRFC_TS]
11.22 Definition of 3GPP UICC services over the new high-speed interface
[UICCHS]
11.23 Interworking between User-to-User Signaling (UUS) and SIP [UUSIW]

11.24 I-WLAN Network Selection Principle (NSP) [IWLANNSP]

CP-100490 CR pack on IWLANNSP
Source: CT1
Decision:
11.25 IMS System enhancements for corporate network access [IMS_Corp]

11.26 3GPP2 Input to Common IMS [CIMS_3GPP2]
11.27 IMS Multimedia Telephony and Supplementary Services [IMSTSS, FA,
REDOC_TIS-C1, REDOC_TIS-C3, REDOC_TIS-C4]
CP-100526 CR pack on REDOC_TIS-C1
Source: CT1
Decision:
11.28 Core Network Impacts for A-Interface Over IP [AoIP]

11.29 Domain Name System Procedures for Evolved Packet System [SAESDEPS]
11.30 IMS Restoration Procedures [IMS-RP]

11.31 eCall Transfer data [EDATA]

CP-100491 CR pack on eData pack 1
Source: CT1
Decision:
CP-100492 CR pack on eData pack 2

Source: CT1
Discussion:
Alcatel-Lucent objected the CR pack based on their view that the CRs were not essential. After this single objection it
was asked again whether anyone else shares the same concern. Nobody else objected, so the CRs were approved despite
sustained objection from Alcatel-Lucent.
Decision:
11.32 IMS Service Continuity [IMS-Cont]

CP-100493 CR pack on IMS-Cont
Source: CT1
Discussion:
CP-100493 contains a set of CRs to TS 24.237 in C1-103377 and C1-103378 that must be conditionally approved on
the condition that the corresponding CRs to TS 23.237 (CR# 0299 and #0300) are approved at SA#49. It can be noted
that the Rel-8 CR to 23.237 (#0299) failed to be agreed at the SA2 #80.
SA2 believed that proposed Rel-8 change is not an essential.
CT Plenary rejected CR 24.237-0326r1.
CT Plenary conditionally approved 24.237-0327r1.
The rest of the CRs are approved.
Decision:
11.33 Earthquake and Tsunami Warning System [ETWS]

CP-100446 Correction on ETWS
Source: CT4
Decision:
11.34 IMS Centralized Service Control (ICSRA) [ICSRA]

CP-100494 CR pack on ICSRA
Source: CT1
Decision:
11.35 Mobility between 3GPP-WLAN Interworking and 3GPP Systems

[IWLAN_Mob]
11.36 CS Fallback in EPS [SAES-CSFB]

CP-100495 CR pack on SAES-CSFB pack 1
Source: CT1
Discussion:
The CR-pack in CP-100495 contains a set of CRs to 29.118 in C1-102577, C1-102578 and C1-102579 that must be
conditionally approved on the condition that the corresponding CR to TS 29.274 (CR # 0704 and #0705) are approved.
C1-102580 CR 24.301-0630r5 contains editorial error "capabilities" exist twice in the table 4.3.2.2.1. CR needs to be
revised.
C1-102580 is revised to CP-100627.
The rest of the CRs are approved since CP-100445 was approved earlier.
Decision:
CP-100496 CR pack on SAES-CSFB pack 2

Source: CT1
Decision:
CP-100627 Corrections and additions to UE mode of operation selection

24.301 CR-0630 rev 6 (Rel-8) v..
Source: Ericsson
Discussion:
This CR was taken out from the CR pack CP-100495.
Decision:
11.37 Service-Level Interworking for Messaging Services [MESSIW]

11.38 Encoding formats, transport formats and media description signalling for
interworking, QoE, and other enhancements to MTSI-MHI [MTSI_eMHI]
11.39 Customized alerting tone (CAT) service in 3GPP CS domain [CAT3G_CS]

11.40 IMS AS service data descriptions for AS interoperability [IMS_ASIO]

11.41 Stage 3 for SRVCC [SAES_SRVCC]

CP-100497 CR pack on SAES-SRVCC
Source: CT1
Decision:
11.42 CSG and idle mode mobility for LTE Home eNodeB [HomeNB-LTE]
CP-100498 CR pack on HomeNB-LTE, HomeNB-3G
Source: CT1
Decision:
CP-100606 Correcting DDF of allowed CSG list MO

24.285 CR-0021 (Rel-10) v..
Source: Samsung
Discussion:
The CR pack for the Rel-8 and Rel-9 CRs is CP-100498. The Rel-10 CR is an exact mirror of the Rel-8 and Rel-9 CRs.
Decision:
11.43 CSG and idle mode mobility for 3G Home eNodeB [HomeNB-3G]
11.44 IWF between MAP based and Diameter based interfaces [SAESMAP2Diam]
11.45 (Small) Technical Enhancements and Improvements for Rel-8 [TEI8]

CP-100447 Correction on IMS
Source: CT4
Decision:
CP-100448 Corrections on Support of C-MSISDN over Sh

Source: CT4
Abstract:
Depends on SA2 reply to CP-100529
Discussion:
CT4 kindly asked SA2 to provide an LS response to CT#49 if there is any relevant information to be considered by
CT4. SA2 postponed the LS to next SA2 meeting. This means CRs need to send back to CT4.
Decision:
The document was Postponed.
CP-100449 Correction on CAMEL

Source: CT4
Decision:
CP-100450 Correction on CS domain

Source: CT4
Decision:
CP-100499 CR pack on TEI8

Source: CT1
Discussion:
In CP-100499, the CRs in C1-103394 and C1-103395 to TS 24.647 must be conditionally approved on the condition
that the corresponding CRs to TS 32.280 TS 32280 Correction of AoC UNI Protocol Mapping (The SA5 CR-number
will be assigned by SA plenary) are approved at SA#49.
C1-103395 is not intended to be part of Rel-10, so Rel-10 version of the TS needs to be created before the
implementation of this CR which should remain in Rel-9 only.
The following CRs shall be revised because a wrong WI code was used.
Also following CRs with condition shall be revised because a wrong WI code was used.
C1-103394 is revised to CP-100637 and conditionally approved.
C1-103395 is revised to CP-100638 and conditionally approved.
Decision:
CP-100585 4 CRs against TS 31.102 and 31.103 for TEI8: USIM and ISIM support of SMS over IP
Source: CT6
Decision:
CP-100586 3 CRs against TS 31.102 for TEI8

Source: CT6
Decision:
CP-100631 Reading MCID information on originating user side

24.516 CR-0003 rev 2 (Rel-8) v..
Source: Ericsson
Discussion:
This CR was taken out from CP-100499 because of a wrong WI code.
Decision:

24.616 CR-0009 rev 2 (Rel-8) v..
Source: Ericsson
Discussion:
Decision:

24.616 CR-0010 rev 2 (Rel-9) v..
Source: Ericsson
Discussion:
Decision:
CP-100634 Removing editor's note about signalling outage

24.604 CR-0048 rev 1 (Rel-8) v..
Source: Ericsson
Discussion:
Decision:
CP-100635 Removing editor's note about signalling outage

24.604 CR-0049 rev 1 (Rel-9) v..
Source: Ericsson
Discussion:
Decision:
CP-100637 Correction of AoC UNI Protocol Mapping

24.647 CR-0014 rev 3 (Rel-8) v..
Source: Ericsson
Discussion:
This CR must be conditionally approved on the condition that the corresponding CRs to TS 32.280 TS 32280
Correction of AoC UNI Protocol Mapping (The SA5 CR-number will be assigned by SA plenary) are approved at
SA#49.
Decision:
CP-100638 Correction of AoC UNI Protocol Mapping

24.647 CR-0015 rev 3 (Rel-9) v..
Source: Ericsson
Discussion:
This CR must be conditionally approved on the condition that the corresponding CRs to TS 32.280 TS 32280
Correction of AoC UNI Protocol Mapping (The SA5 CR-number will be assigned by SA plenary) are approved at
SA#49.
Decision:
11.46 Any other Rel-8 Work item or Study item

CP-100500 CR pack on IMS-Sec
Source: CT1
Decision:
CP-100547 CRs on IMS-CS Interworking (Rel-8 and mirrors)

Source: CT3
Decision:
CP-100548 CRs on PCC (Rel-8 and mirror)

Source: CT3
Decision:
12 Rel-9
12.1 Stage 3 Enhancements of IMS CAT Supplementary Service [eCAT-SS]
12.2 (Small) Technical Enhancements and Improvements for Rel-9 [TEI9]

CP-100451 Corrections to GTP set 1
Source: CT4
Discussion:
RIM commented that a NOTE2 contains a normative requirement which should be clarified.
CT4 Vice Chairman commented that in the last CT4 meeting it was agreed that the NOTE2 shall be changed as a
normative text. The CR was agreed without presentation in CT4#50 and it seems the source of the CR missed this
agreed correction.
CR 29.274-727r1 C4-102398 shall be taken out from the CR pack and will be send out from CT4 mailing list for
clarification.
Decision:

Source: CT4
Decision:
CP-100453 Corrections on Change reporting support indicator

Source: CT4
Discussion:
It was clarified that SA2 discussed CT4 LS and agreed the proposed changes by CT4.
Decision:
CP-100454 Corrections on IMS

Source: CT4
Decision:
CP-100455 Corrections on C-MSISDN

Source: CT4
Discussion:
See comments on CP-100448.
Decision:
CP-100456 Corrections on restoration and restart in EPC

Source: CT4
Decision:
CP-100457 Corrections in the area of EPC

Source: CT4
Decision:
CP-100458 Corrections to CS domain

Source: CT4
Decision:
CP-100501 CR pack on TEI9

Source: CT1
Discussion:
The CR-pack in CP-100501 contains a set of CRs in C1-103353 and C1-103354 to TS 24.229 that must be
conditionally approved on the condition that the corresponding CR to TS 29.228 (CR # 0493) is approved.
CT4 Vice Chairman clarified that CRs for 29.228 were approved in CP-100447.
Decision:
CP-100549 CRs on TEI for Rel-9

Source: CT3
Discussion:
Since RAN2 has approved to remove functionality these CRs will fail.
Decision:

29.274 CR-0691 rev 1 (Rel-9) v..
Source: CT4
Discussion:
RAN2 CR RP-100851 removed the functionality, which means C4-101849 is rejected.
Decision:
The document was Rejected.
CP-100578 Clarification for Create Session Response

29.274 CR-0690 rev 5 (Rel-9) v..
Source: Motorola
Decision:
The document was Withdrawn.

Source: CT4
Discussion:
This CT4 CR is proposed for revision in CP-100578, but that company contribution CP-100578 was withdrawn during
the meeting.
Decision:

Source: CT6
Decision:

Source: CT6
Decision:

Source: CT6
Discussion:
It was clarified that proposed change affect for all test equipments. That is the reason why all the checkboxes for
"Proposed change affects:" are ticked.
Decision:
CP-100592 2 CRs against TS 31.121 and 31.124 for TEI9: update of TC SCP references
Source: CT6
Decision:

Source: CT6
Decision:

Source: CT6
Decision:
CP-100636 Correction to condition of sending Context Acknowledge message

29.274 CR-0727 rev 2 (Rel-9) v..
Source: Nokia Siemens Networks
Discussion:
This CR was taken out from the CR pack CP-100451.
CR is sent out to CT4 reflector for clarification if NOTE2 should be changed as a normative text.
It was clarified that in NOTE2 "shall be" is changed as "is".
Decision:
12.3 User Data Convergence [UDC-CN]

CP-100459 Corrections on UDC
Source: CT4
Decision:
12.4 Support of Personal Area Networks and Enhancements to Personal

Network Management [PAN_EPNM]
CP-100502 CR pack on PAN_EPNM
Source: CT1
Decision:
12.5 IMS Services Centralization and Continuity [IMS_SCC-ICS_I1]

CP-100503 CR pack on IMS_SCC-ICS_I1
Source: CT1
Decision:
12.6 CS-IBCF and CS-TrGW definition in 3GPP specifications [CS-IBCF]

CP-100550 CRs on the Ix-CS Interface
Source: CT3
Decision:
12.7 IMS IBCF TrGW definitions in 3GPP (Ix interface) [IMS_IBCF]

CP-100460 Corrections on Ix interface
Source: CT4
Decision:
CP-100551 CRs on the Ix-IMS Interface

Source: CT3
Decision:
12.8 Value added services for SMS interface and signaling flow [VAS4SMS]
12.9 IMS ALGCF IMA-MGW definitions in 3GPP (Iq interface) [IMS_ACCF]

CP-100461 Corrections on Iq interface
Source: CT4
Decision:
12.10Completion of IMS Restoration Procedures [eIMS_RP]

CP-100462 Corrections on IMS Restoration
Source: CT4
Decision:
12.11 Control Plane LCS in the EPC [LCS_EPS-CPS]

CP-100463 Corrections on Control plane LCS in the EPC
Source: CT4
Decision:
12.12CN aspects of Local Call Local Switch [LCLS-CN]

12.13MBMS support in EPS [MBMS_EPS]

CP-100552 CRs on MBMS Support in EPS
Source: CT3
Decision:
12.14Operational description of the Inter-IMS Network to Network Interface

[II-NNI]
CP-100553 CRs on the Inter-IMS NNI (Rel-9 and mirrors)
Source: CT3
Decision:
12.15SRVCC support for IMS Emergency Calls [IMS_EMER_GPRS_EPSSRVCC]

12.16Public Warning System [PWS-St3]

CP-100504 CR pack on PWS-St3
Source: CT1
Decision:
12.17Enhancements to IMS Centralized Services [IMS_SCC-ICS]

12.18IMS Service Continuity Enhancements: Service, Policy, Interactions and

Inter UE Transfer [IMS_SCC-SPI]
CP-100505 CR pack on IMS_SCC-SPI
Source: CT1
Decision:
12.19Support for IMS Emergency Calls over GPRS and EPS

[IMS_EMER_GPRS_EPS]
CP-100506 CR pack on IMS_EMER_GPRS_EPS
Source: CT1
Discussion:
CT1 approved CR C1-102900 needs to be revised since it clashes with other CR.
The other CRs are approved.
Decision:
CP-100652 Emergency registration in HPLMN

24.229 CR-3205 rev 3 (Rel-10) v..
Source: Ericsson
Discussion:
This CR is taken out from CP-100506 because of collision.
Decision:
12.20Service Specific Access Control [SSAC]

12.21Customized Ringing Signal [CRS]

12.22Enhancements for Completion of Communications Supplementary

Service [eMMTel-CC]
12.23Multiple PDN to the Same APN for PMIP-based Interfaces [MUPSAP]

12.24Support of Home NB and Home eNB enhancements [EHNB]

CP-100507 CR pack on EHNB-GERAN
Source: CT1
Decision:
CP-100521 CR pack on EHNB-CT1

Source: CT1
Decision:
12.25IMS Media Plane Security [MEDIASEC]

CP-100508 CR pack on MEDIASEC_CORE
Source: CT1
Decision:
12.26Access Network Discovery and Selection Enhancements [eANDSF]

CP-100509 CR pack on eANDSF
Source: CT1
Decision:
12.27Definition of Ml interface for Control Plane LCS [EMC2]

12.28PCC Enhancements [PCC-Enh]

CP-100464 Corrections on PCC
Source: CT4
Decision:
CP-100554 CRs on PCC Enhancements

Source: CT3
Decision:
12.29Any other Rel-9 Work item or Study item Study item

Source: CT1
Decision:
CP-100555 CR on CS Architecture Split

Source: CT3
Decision:
CP-100556 CR on Interworking with External SIP-I Networks

Source: CT3
Decision:
CP-100557 Interworking with SIP-I based CS Domain and other Networks

Source: CT3
Decision:
CP-100558 CRs on APN-AMBR support in GPRS

Source: CT3
Decision:
CP-100589 1 CR against TS 31.121 for SAES-USIM_LTE-Test

Source: CT6
Decision:
CP-100597 3 CRs against TS 31.124 for SAES-USIM_LTE-Test

Source: CT6
Decision:
CP-100613 3 CRs against TS 31.124 for SAES-USIM_LTE-Test

Source: CT6
Decision:
13 Release 10
13.1 IP-SM-GW enhancements for CPM-SMS Interworking
CP-100560 CRs on CPM-SMS Interworking
Source: CT3
Decision:
13.2 IMS Stage-3 IETF Protocol Alignment [IMSProtoc4]

Source: CT1
Discussion:
Consequences if not approved need to be added in following TSG CT1 agreed CRs C1-102834, C1-102838 and C1102839.
Decision:
CP-100639 Alignment with RFC 5552

24.229 CR-3176 rev 3 (Rel-10) v..
Source: Ericsson
Decision:
CP-100640 Handling of aliases URIs

24.229 CR-3180 rev 3 (Rel-10) v..
Source: Ericsson
Decision:
CP-100641 Structure of the Request URI sent by a UE

24.229 CR-3181 rev 3 (Rel-10) v..
Source: Ericsson
Decision:
13.3 Call Completion on Not Logged-in

CP-100512 CR pack on CCNL
Source: CT1
Decision:
CP-100559
CRs on Call Completion Not Logged in

Source: CT3
Decision:
13.4 IP-SM-GW enhancements for CPM-SMS Interworking

13.5 Enhanced User Data Convergence (UDC) Model

13.6 Stage 3 for Local IP Access

13.7 Further improvements of II-NNI Stage 3 based on operational feedback

and evolution of other specifications
CP-100562 CRs on the Inter-IMS NNI (Rel-10)
Source: CT3
Decision:
CP-100614 CRs on the Inter-IMS NNI (Rel-10)

Source: CT3
Decision:
13.8 Optimal Media Routeing

13.9 IP Flow Mobility and seamless WLAN offload

CP-100513 CR pack on IFOM-CT
Source: CT1
Decision:
CP-100561 CRs on PCC Support for IFOM

Source: CT3
Decision:
13.10AT Commands for IMS-configuration

13.11 Selected IP Traffic Offload

CP-100465 Enhancements related to Selected IP Traffic Offload
Source: CT4
Decision:
CP-100514 CR pack on SIPTO

Source: CT1
Decision:
13.12Any other Rel-10 Work item or Study item

CP-100466 Enhancements to IMS
Source: CT4
Decision:
CP-100467 Enhancements to CAMEL

Source: CT4
Discussion:
29.002-0979r1 (C4-102267) is revised in company contribution CP-100608.
CT4 agreed CR 23078-0836 (C4-102266) is approved.
Decision:
CP-100468 Enhancements to SMS

Source: CT4
Decision:
CP-100469 Enhancements to GTP

Source: CT4
Decision:
CP-100515 CR pack on AT_UICC

Source: CT1
Discussion:
CT1 agreed CR C1-103420 is revised in CP-100571.
Decision:
CP-100516 CR pack on eAoC

Source: CT1
Discussion:
In CP-100516, the CR in C1-103396 to TS 24.647 must be conditionally approved on the condition that the
corresponding CRs to TS 32.280 Correction of Annex C2 (The SA5 CR-number will be assigned by SA plenary) are
approved at SA#49.
Decision:
CP-100517 CR pack on TEI10 pack 1

Source: CT1
Discussion:
In CP-100517, C1-103546 to TS 24.301 must be conditionally approved on the condition that the corresponding stage 2
CR to TS 36.331 (CR # 0449) is approved. It can be noted that the RAN-CR failed to be agreed at the RAN WGmeeting.
It was agreed that C1-103546 shall be taken out from CR pack and send back to CT1.
C1-103546 is postponed.
Decision:

Source: CT1
Decision:

Source: CT1
Decision:

Source: CT1
Discussion:
C1-102750 needs to be revised because the causes affected needs to be clarified.
The other CRs are approved.
Decision:
CP-100522 Enhancements to IMS

Source: CT4
Decision:
CP-100524 Add Timezone IE in Gs Location Update Request

29.018 CR-0063 rev 5 (Rel-10) v..
Source: Alcatel-Lucent/
Decision:

29.018 CR-0063 rev 4 (-) v..
Source: CT1
Decision:
CP-100563 CRs on TEI for Rel-10

Source: CT3
Decision:
CP-100571 USAT over AT

27.007 CR-0249 rev 4 (Rel-10) v..
Source: Ericsson, ST-Ericsson, Giesecke & Devrient, Incard
Discussion:
This CR is revison of CT1 agreed CR C1-103420 which is in CR pack CP-100515.
Can be approved only on condition that the corresponding WID is also approved.
Decision:

29.018 CR-0063 rev 6 (Rel-10) v..
Source: Alcatel-Lucent/
Decision:

Source: CT6
Decision:
CP-100603 Corrections related to non-3GPP access

Source: CT4
Decision:
CP-100608 Addition of SS codes to the ATSI and ATM procedures

29.002 CR-0979 rev 2 (-) v..
Source: Vodafone
Discussion:
his CR replaces CT4 agreed CR (C4-102267) in CP-100467 since a small mistake was noticed after CT4#50.
Decision:

Source: CT1
Discussion:
There was no need to revise the whole CR pack. Only one CR from CR pack CP-100520 (C1-102450) is revised in CP100642. The rest of the CRs in CP-100520 were approved.
Decision:
The document was Withdrawn.
CP-100642 Maximum number of packet filters

24.008 CR-1579 rev 2 (Rel-10) v..
Source: Ericsson
Discussion:
This CR is taken out from the CR pack CP-100520 because of some error in cover page.
Decision:
13.13Rel-10 work planning
14 Approval of WIDs
14.1 Revised WIDs
CP-100470 Local Call Local Switch
Source: CT4
Abstract:
Document the normative core network impacts to the MSC-S, MGW and associated core network interfaces to support
the solution as detailed in the technical report in order to support the requirements for LCLS. Initial focus shall be to
standardise the LCLS fundamental functionality as below:
Ability to (re-)Establish Local Call Local Switch (LCLS Negotiation)
Call Leg Correlation
Signalling on A-interface (Stage 2 Call Flows only)
Signalling within Core Network
Impact to User Plane
Lawful Intercept
Ability to break LCLS
Additional standardisation of impacts to supplementary services and existing features may be considered to be
standardised, if the LCLS fundamental functionality is complete and sufficient time permits before closing this Work
Item.
Additional standardisation of an optional H.248 package to notify the MGW that the call is a local call local switch
may be considered to be standardised, if the LCLS fundamental functionality is complete and sufficient time permits
before closing this Work Item.
Additional standardisation of an enhanced solution for mid-call tones/announcements may be considered to be
standardised, if the LCLS fundamental functionality is complete and sufficient time permits before closing this Work
Item.
Discussion:
A new TS number will be 3GPP TS 23.284.

Decision:
CP-100598 Updated description of the testing the interworking of LTE Terminals with the USIM
Source: CT6
Decision:
CP-100609 Updated WID on UDC Data Model

Source: CT4
Abstract:
3GPP TS 23.335 has specified UDC architecture defining a new Ud interface between Front-Ends (FEs) and the User
Data Repository (UDR) as well as procedures and signalling flows over the interface. 3GPP TS 29.335 has specified the
stage 3 of the Ud interface between the FEs and the UDR. Details related to the data model used with LDAP (e.g.
directory tree) are still outside the scope of the present version of this specification and full interoperability between
UDR and FEs from different vendors is not guaranteed. Also the integration of IMS AS user data into the UDR has to
be studied, as these data are currently stored as transparent data by the HSS but conveyed over the Sh interface based on
partial specification in 3GPP TS 29.364.
Discussion:
In order to guarantee interoperability between FEs and UDR from different vendors and, consequently, the success of
UDC systems, it is needed to define the reference data model for specific applications (i.e. HSS, HLR, AuC, IMS AS),
that means:
1) Define the subset of HLR/HSS interfaces and related user data to include in the reference model.
2) Define the IMS AS user data related to MMTel services especially those having CS equivalents.
3) Define the UDC reference data model for the user data identified in 1) and 2).
Decision:
14.2 New WIDs

CP-100471 S2b Mobility based on GTP
Source: CT4
Abstract:
The increased data demand, caused by the increased use of 3rd party applications and Internet browsing is creating
interest for new operator tools to lower the cost of providing data services. The increased availability of WLAN radio
in many terminals and WLAN access networks in many geographical locations provide means to achieve this goal.
WLAN RAT frequently happens to be associated with "untrusted" non-3GPP access. Network-based mobility between
E-UTRAN and untrusted non-3GPP accesses is provided by the S2b interface defined in 3GPP TS 23.402. This
interface is based on PMIPv6.
With real EPS deployments approaching the time to be going live, it is now recognized it will be beneficial to also allow
a GTP option for S2b network based mobility as this would simplify the architecture and operations of EPS networks
supporting 3GPP and non-3GPP accesses by using a single mobility protocol.
This Work item aims at specifying the stage 3 procedures and protocol to support the stage 2 requirements defined for
S2b mobility based on GTP.
Discussion:
Classification of WI and linked work items needs to be corrected since this is building block under SA2 WI.
Decision:
CP-100472 Enabling Coder Selection and Rate Adaptation for UTRAN and E-UTRAN for Load Adaptive
Applications, CN impacts
Source: CT4
Abstract:
The feasibility study in SA2 for Enabling Codec Selection and Rate Adaptation for UTRAN and E-UTRAN for Load
Adaptive Applications (TR 23.860) has been concluded and has outlined possible new procedures for CN nodes to
support Explicit Congestion Notification (ECN) for voice and video as currently defined for MTSI voice applications in
3G TS 26.114. In order to fully support the ECN for RTP traffic and interwork with CS rate control the IMS MGWs and
MGW Controllers need to be updated.
The objective of this work is to investigate and specify the stage 3 protocol aspects to support ECN as defined in TS
26.114 within IMS and also interworking scenarios between IMS and CS. The stage 3 impacts are based primarily on
section TR 23.860 clause 6.4. Proposed enhancements are:
Support of Explicit Congestion Notification (ECN) by IMS Core Network entities (e.g., MGCF/MGW, IBCF/TrGW
etc) including updates to H.248 profiles to support ECN and its associated parameters. (IMS ALG/IMS-AGW excluded)
IMS ALG/AGW support for forwarding ECN bits
Support of RTP/AVPF and SDPCapNeg (where not already supported) by IMS CN nodes
Interworking of adaptation requests from MTSI client and CS network (including ICS and SRVCC) by IMS MGW
and CS MGWs
Interworking with non-ECN IP networks
Interworking with non 3GPP ECN network or terminal
Decision:
CP-100473 Study on Node Restoration in EPS

Source: CT4
Abstract:
The node in the EPS should have the high reliability, but occasional restart or failure due to various reasons may be
unavoidable. When looking at the network, the connectivity between the nodes can also cause additional problems.
Although in Rel-8 and Rel-9 there are basic mechanisms for the node recoveries and restorations, problems were found
with these mechanisms especially the case where the IMS is introduced and an EPC node such as MME has restarted
(in such case, the call cannot be received for UE for which the restarted EPC node served). In order to resolve such
problem, it is needed to perform a further feasibility study of the possible enhancements for existing mechanisms and/or
new mechanism to make sure the EPS network can provide reliable service.
This study item proposes to study the behaviour of nodes in EPS upon restart/failure of network elements or failure of
the communication links between them, and analyze solutions that ensure no degradation of the service to the UE.
This Study Item will consider any necessary operational protocol recovery mechanisms in the EPS in order to achieve
end to end system recovery. The study item will address the following points:
-
list the different network failure scenarios to be analyzed for EPC nodes: MME, SGSN, SGW and PGW
identify precisely the problems resulting from the current definition of the standards
analyze possible solutions
conclude on potential enhancements to the standards (depending on gains vs complexity)
Discussion:
A new TR number for this study is 3GPP TR 23.857.
In this point it is difficult to indicate if a normative work can be done on Rel-10 time frame. It depends
Decision:
CP-100479 WID on Advice of Charge (AoC) service support enhancements (Stage 3)

Source: CT1
Abstract:
Operators require several additional enhancements to the existing AoC features. To fulfil these requirements, SA5 is
working on a feature work item for AoC Service Support Enhancements (WID 470047, 3GPP TS 32.280) which is
based on SA1 requirements (3GPP TS 22.115, 3GPP TS 22.173 and 3GPP TS 22.024).
The following impact on TS 24.647 needs to be considered:
- Addition of Charge Advice Information (CAI) elements as well as volume charging elements which are supported
by 3GPP TS 32.280 and TS 32.299.
- Enhancements needed for transmission of AoC Cost information by AoC-D and AoC-E Corrections. The Type of
charging information (3GPP TS 24.647) shall either be subtotal charges or total charges which is obviously not
the same as proposed by 3GPP TS 32.280 and 3GPP TS 32.299.
- Enhancements for transmission of AoC Tariff Information of the XML schema in 3GPP TS 24.647 for AoC
information model and AoC UNI is needed.
- Legacy protocol items which are not supported by NGN/IMS are not applicable in mapping tables in 3GPP TS
32.280. Because they are no longer needed for IMS, these values could be also marked as not applicable from 3GPP TS
24.647.
Implement new AoC features and apply modifications in CT1 3GPP TS 24.647.
- Addition of Charge Advice Information (CAI) elements and volume charging elements as specified in 3GPP TS
32.280 and 3GPP TS 32.299 for IMS in 3GPP TS 24.647.
-
Add volume charging elements as specified in 3GPP TS 32.280 and 3GPP TS 32.299 for IMS in 3GPP TS 24.647.
Enhancements for transmission of AoC Cost information by AoC-D and AoC-E in 3GPP TS 24.647.
Enhancements for transmission of AoC Tariff Information of the XML schema in 3GPP TS 24.647.
Not supported legacy protocol items shall be marked as not applicable from 3GPP TS 24.647.
All enhancements and new AoC features shall be compatible to existing frozen releases and any duplicated solutions in
3GPP and ETSI TISPAN shall be avoided.
Discussion:
Ericsson commented that the related approved CR in CP-100516 should use the same WI than this WID.
Decision:
CP-100480 WID on AT Commands for UICC interaction

Source: CT1
Abstract:
In a configuration where the UICC is connected to a modem the Card Application Toolkit (CAT) protocol defined in
ETSI TS 102 223 and 3GPP TS 31.111 cannot be fully utilised because it ends at the modem and does not reach the
entities with access to the resources targeted by the protocol (like display and keyboard). As a consequence CAT
commands like DISPLAY TEXT, PLAY TONE or GET INPUT cannot be used in this configuration.
Note: Work on the topic has started in ETSI SCP by defining requirements, use cases and definitions for the extended
AT commands (see ETSI TS 102 412 v10.0.0). As CT1 is responsible for the AT command standard TS 27.007 it is
proposed to continue this work in CT1.
This work item will extend 3GPP TS 27.007 to define AT commands for the exchange of CAT commands between the
UICC and an entity connected to a modem and for the registration with the modem of such services which a connected
entity can perform.
It will also cover an extension that will enable CAT commands to be directly addressed to an entity connected to a
modem.
In addition, enhancements to 3GPP TS 27.007 on management of the PIN code (Command +CPIN) are considered, in
order to reflect the PIN management defined in ETSI TS 102 221.
In order to avoid using generic file access command and to provide quick access to information, the definition of a
dedicated command in order to access the ICCID of the UICC is required.
The functionality intended to be added to 3GPP TS 27.007 will be introduced through the regular 3GPP CR procedure,
and at completion of the work item an acknowledgement from ETSI SCP will be requested.
Discussion:
It was requested if there are any linkage between CT1 WID and CT6 WID,
CT6 Chairman clarified that related CT6 work item target is to clarify the use of AT commands specified by CT1. There
are no direct linkage and the based on discussion in CT#48 two separate WID is needed.
After discussion it was agreed that the work split between CT1 and CT6 is identified.
It was seen that some of the proposed justifications are not needed.
Decision:
CP-100581 CT wide WID for eMPS stage3

Source: NTT DOCOMO, Ericsson, Telcordia, NEC, KDDI
Decision:
CP-100599 USAT access over modem interface

Source: CT6
Decision:
CP-100600 IMS CALL CONTROL

Source: CT6
Abstract:
It is stated in USAT requirements TS22.038 sec 8.2 that
"The communication control capability applies to all mobile originated requests independent of the applicable data
exchange capability. Explicitly it applies to voice calls, IMS based communications and all services listed in the section
USAT data exchange capabilities requirements".
IMS communication capability have to be taken into account, and all use cases from the operators to use call control
capability also apply to IMS communications (Voice call over IMS, multimedia telephony, etc.). User experience may
be the same, whatever the underlying data exchange technology is used.
The objective of this work item is to define a Call Control mechanism based on ISIM/USIM, which will apply to IMS
based communications. The Call Control mechanism will allow to initiate, terminate, allow, bar or modify IMS based
communications. The Call Control mechanism shall take into account the case where the called IMPU is a SIP URI or a
tel URI.
Discussion:
It was asked whether the USAT changes would be also applicable on ISIM.
22.038 connection control stage 1 does already cover the UICC initiated CS calls, but it is already known that the
corresponding IMS procedures for UICC initiated calls have substantial challenges and a separate study item has been
started to analyse those.
CT Plenary agreed that the objectives need to be clarified because of possibility of misunderstanding.
CT Plenary agreed that this WI must not proceed to normative work in UICC call initiation area before the study is
completed and the problems related with call initiation are solved.
Decision:
CP-100601 Introduction of Smart Card Web Server launch pads functionality

Source: CT6
Abstract:
In 3GPP Smart Card Web Server is used as a building block to create services such as Contact Manager (TS 31.220).
Nevertheless it is sometimes difficult for the user to get easy access to this feature, as the functions to start the SCWS
are somewhere placed in MEs MMI. It would be beneficial if the user could get easy and immediate access to SCWS
services. An example of a possible solution could be the feature called launch pad, introduced in ETSI TS 102 221
V9.1.0. This feature enables the user to launch a Smart Card Web Server session directly from the ME menu. It could be
useful to introduce also in 3GPP the same feature.
The objective of this Work Item is to define a solution which allows the user to launch Smart Card Web Server services
directly from the ME MMI with just one click.
Discussion:
It was seen that the objectives should be reworded.
CT plenary had some concerns that WID tries to specify MMI which is not usually done in 3GPP.
WID was postponed out of this meeting after the discussion.
Decision:
CP-100602 Testing the interworking of ISIM Terminals with the IP Multimedia Subsystem
Source: CT6
Abstract:
Development of conformance test for Rel-8 and onwards terminals with IMS support based on the use of the IP
Multimedia Services Identity Module (ISIM) application.
The objective of this work item proposal is the evaluation of existing test cases and when appropriate specification of
test cases to verify terminal interworking with the ISIM application and USIM application toolkit (USAT) on the UICC
and the IP Multimedia Subsystem, especially in combination with the E-UTRA/EPC. Therefore the ISIM application
specification TS 31.103, the USIM application toolkit specification TS 31.111 and the IP multimedia call control
protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) specification TS 24.229 are
considered in this WI to ensure that the terminal is acting on the network side according to the parameters specified on
the ISIM and vice versa. For IMS related USIM/USAT tests the existing test specifications TS 31.121 and TS 31.124
are reused and will be extended where appropriate.
Evaluation of features and available tests to ensure the correct support of the following features (the list is not
exhaustive):
-
Handling of User IDs stored on the ISIM
Usage of Home Domain Name as stored on the ISIM
Handling of P-CSCF addresses as stored on the ISIM
Evaluation of tests and definition/adaptation of test cases to ensure the correct support of the following features
-
Support of IMS with USIM/ISIM interworking: Short Message Service storage on USIM
Support of IMS in USAT: Send Short Message, SMS-PP Data Download
Decision:

Abstract:
The stage2 aspect of eMPS has developed in stage2 and it enables the network to provide the means for the priority
handling of IMS based multimedia services, EPS bearer services and CS Fallback with regard to LTE/EPC.
The general mechanism provided by stage2 eMPS are:
-
For IMS based multimedia service and EPS bearer services,
Allocate resources for signaling and media with priority based on subscribed priority or based on priority indicated
by service signaling.
For a terminating IMS session over LTE, a mechanism for the network to detect priority of the session and treat it
with priority.
-
For CS Fallback,
Priority handling of originating and terminating voice call from a service user and enable the target UE to establish
the AS and NAS connection to fall-back to the GERAN/UTRAN/1xRTT.
Impacted stage2 specifications are TS 23.401, TS 23.203, TS 23.228 and TS 23.272 and relevant stage3 specification
work is needed.
The objective of this work item is to specify the stage3 aspect of eMPS according to stage 2 changes, some example
impacts are as follows;
-
update S6a interface for supporting eMPS (for CSFB, IMS, EPS bearer),
update S11 interface for supporting eMPS (for IMS),
update Sh interface for supporting eMPS (for IMS),
update SIP/SDP protocol for supporting eMPS (for IMS),
update Cx interface for supporting eMPS (IMS),
update the organization of subscriber data (for CSFB, IMS, EPS bearer),
update Rx interface for supporting eMPS (for IMS)
SPR data and PCRF interaction (IMS),
S102 impacts
Decision:
CP-100612 USAT access over modem interface

Source: CT6
Abstract:
Mobile modems are becoming a significant sector of the mobile communications market. The architecture is based on
three entities: the modem, the UICC with a USIM/ISIM and supporting USAT and the entity connected to the modem.
This connected entity may be a PC or a Machine to Machine device. Currently support for USAT in these entities is
being limited by the lack of standards defining how USAT should be extended to applications running in the connected
entity through the interface between the modem and the connected entity.
The intention is to make use of features defined by ETSI SCP for the Card Application Toolkit (CAT) for this purpose.
This work item will define the necessary extensions in USAT to support applications running in connected entities.
This includes extensions of the USAT as defined in TS 31.111 to allow applications in UICCs that support the USAT
functionality over the modem interface feature:
-
to discover the support of the feature by the modem via the Terminal profile
to discover the individual terminal profiles for the modem and the connected entity.
to select whether each USAT command shall be sent to the modem or a connected entity
to be notified when connected entities initiate their session with the modem.
to indicate to the modem that the USAT application has no pending activity with the connected entity.
to identify multiple connected entities and direct communication individually
to authenticate connected entities
to encrypt/decrypt the data that is exchanged between the USAT application and a connected entity
to check the integrity of the data that is exchanged between the USAT application and a connected entity.
Discussion:
Qualcomm clarified that the use cases are not clear enough. Qualcomm would prefer to postpone WID until the use
cases in 3GPP are specified.
It was seen by several companies that stage 1 service requirements are needed before WID can be approved.
Decision:
The document was Rejected.
CP-100644 S2b Mobility based on GTP

Source: CT4
Decision:
CP-100645 WID on Advice of Charge (AoC) service support enhancements (Stage 3)

Source: CT1
Abstract:
Operators require several additional enhancements to the existing AoC features. To fulfil these requirements, SA5 is
working on a feature work item for AoC Service Support Enhancements (WID 470047, 3GPP TS 32.280) which is
based on SA1 requirements (3GPP TS 22.115, 3GPP TS 22.173 and 3GPP TS 22.024).
The following impact on TS 24.647 needs to be considered:
- Addition of Charge Advice Information (CAI) elements as well as volume charging elements which are supported
by 3GPP TS 32.280 and TS 32.299.
- Enhancements needed for transmission of AoC Cost information by AoC-D and AoC-E Corrections. The Type of
charging information (3GPP TS 24.647) shall either be subtotal charges or total charges which is obviously not
the same as proposed by 3GPP TS 32.280 and 3GPP TS 32.299.
- Enhancements for transmission of AoC Tariff Information of the XML schema in 3GPP TS 24.647 for AoC
information model and AoC UNI is needed.
- Legacy protocol items which are not supported by NGN/IMS are not applicable in mapping tables in 3GPP TS
32.280. Because they are no longer needed for IMS, these values could be also marked as not applicable from 3GPP TS
24.647.
Implement new AoC features and apply modifications in CT1 3GPP TS 24.647.
- Addition of Charge Advice Information (CAI) elements and volume charging elements as specified in 3GPP TS
32.280 and 3GPP TS 32.299 for IMS in 3GPP TS 24.647.
-
Add volume charging elements as specified in 3GPP TS 32.280 and 3GPP TS 32.299 for IMS in 3GPP TS 24.647.
Enhancements for transmission of AoC Cost information by AoC-D and AoC-E in 3GPP TS 24.647.
Enhancements for transmission of AoC Tariff Information of the XML schema in 3GPP TS 24.647.
Not supported legacy protocol items shall be marked as not applicable from 3GPP TS 24.647.
All enhancements and new AoC features shall be compatible to existing frozen releases and any duplicated solutions in
3GPP and ETSI TISPAN shall be avoided.
Decision:
CP-100646 WID on AT Commands for UICC interaction

Source: CT1
Decision:
CP-100647 IMS CALL CONTROL

Source: CT6
Decision:

Decision:

Abstract:
The stage2 aspects of eMPS have been completed enabling the LTE/EPC network to provide the means for the priority
handling of IMS based multimedia services, EPS bearer services, and CS Fallback.
The general mechanism provided by stage2 eMPS are:
-
For IMS based multimedia services and EPS bearer services,
Allocate resources for signaling and media with priority based on subscribed priority or based on priority indicated
by service signaling.
For a terminating IMS session over LTE, a mechanism for the network to detect priority of the session and treat it
with priority.
-
For CS Fallback,
Priority handling of originating and terminating voice call from a service user and enable the target UE to establish
the AS and NAS connection to fall-back to the GERAN/UTRAN/1xRTT.
The impacted stage2 specifications for eMPS are TS 23.401, TS 23.203, TS 23.228 and TS 23.272. The relevant stage3
specification work is needed.
The objective of this work item is to specify the stage3 aspects of eMPS according to stage 2 requirements. Some
example impacts are as follows;
-
update S6a interface for supporting eMPS (for CSFB, IMS, EPS bearer),
update S11 interface for supporting eMPS (for IMS),
update Sh interface for supporting eMPS (for IMS),
update SIP/SDP protocol for supporting eMPS (for IMS),
update Cx interface for supporting eMPS (for IMS),
update the organization of subscriber data (for CSFB, IMS, EPS bearer),
update Rx interface for supporting eMPS (for IMS)
SPR data and PCRF interaction (for IMS),
S102 impacts
Decision:
15 TSG CT work organization

15.1 Principles for work organization within CT
15.2 Terms of Reference

15.3 Support Arrangements

CP-100573 Support Team report
Source: MCC
Decision:
15.4 Working methods

CP-100572 CRs to 21,801 (3GPP drafting rules)
21.801 v..
Source: MCC
Abstract:
This CR on 3GPP Drafting Rules TR 21.801 is under TSG SA control and distributed for TSG CT review and
comments.
Discussion:
CR 21.801-0028 changes Annex H supported file formats and the proposed change allows to use MS Visio for drafting
informal SDL diagrams.
CR 21.801-0029 CT Plenary agreed that including an entire document to a TS or TR as an attached zip file should not
be encouraged
Detailed comments were given but the principle of all CRs were supported by TSG CT. The final approval of the CRs
shall be done in SA#49.
Decision:
15.5 Future Meeting Schedule

16 Specification in TSG-CT domain

16.1 Specification status
16.2 3GPP TS/TR for information

16.3 3GPP TS/TR for approval

CP-100474 3GPP TR 23.889 v2.0.0 on Local Call Local Switch System Impacts
Source: CT4
Decision:
Source: Vodafone
Discussion:
It was agreed that CT4 should not spend more time in maintenance of 3GPP TR 23.889 any more, but to concentrate on
the normative work instead. CT Plenary confirmed CT4 proposal with understanding that some errors will be corrected
related to optional solutions only in 3GPP TS.
Ericsson supports the proposed editorial changes made but objects to the specific text that Ericsson requests to be
deleted by CP-100628.
Ericssons understanding of the agreed compromise is that the checks of the encapsulated BSS ID are options and shall
not impose any mandatory behaviour on other nodes, specifically the BSS. This means that a BSS can ignore any
correlation result from such checks, with no restrictions. Currently the TR includes restrictions on this which is not
acceptable to Ericsson.
Since the default behaviour without any of these options is that the BSS must always correlate the call legs when it
receives a GCR this means that the Correlation Request IE is optional and a default behaviour can be specified for the
BSSAP protocol this means there is no reason to mandate the inclusion of LCLS-Correlation-Request IE in the protocol
messages.
The TR contains text in Clause 12.6 indicating that a BSS may send SID frames and that this has no impact on the
MGW. Ericsson objects to this text as it is not correct. There is no technical justification for sending SID frames for a
LCLS connection and it is not correct that it has no impact to the CN. There are proposed optimisations in the TR for
removal of MGW pooled resources and optimised inter-BSS handover that would prevent SID frames from being
transmitted end to end and therefore without any technical reason to send SID frames this should not be permitted and
certainly not endorsed in the standards. If this text is left in the TR due to objections from other companies to remove it
then Ericsson claims that this aspect of the TR is not Approved by consensus and can have no basis for future normative
work.
The document was Revised to CP-100628 to attempt to include the minimum acceptable changes to approve the TR
based on issues raised in CP-100582.
GERAN 2:
Some companies would have preferred to take the version in CP-100628 as the way forward, but they did not object to
the approval of this version. Since Ericsson remained the only company that sustained their objection, the document
was approved.
Decision:
CP-100564 (TR 29.816, V 2.0.0) Study on PCRF failure and restoration

Source: CT3
Abstract:
The present document contains the results of the study on PCRF failure and restoration.
Target failure and recovery scenarios are detailed; the following scenarios are addressed (incl. roaming):
- Single PCRF deployment (covering also the equivalent scenario of multiple PCRFs with a fixed assignment of
PCRFs);
-
Multiple PCRFs and the DRA is used;
PCRF node failures of different type (e.g. complete outage, loss of dynamic data) and the aspect of reliability in
signaling connections will be studied.
Functional requirements for solutions to handle such cases in a standardized way are defined, considering the network
elements PCRF, PCEF, BBERF, AF and DRA and taking operators preferences into account (e.g. minimal impact on
user experience versus maximal control/minimum risk for the operator).
The study describes the potential solutions, which include procedures and signalling between PCRF and other PCC
related network nodes, and procedures and signalling between Diameter clients (i.e. PCEF/BBERF/AF) and the DRA.
Per solution the impacted 3GPP specifications and the necessary changes therein are listed.
The study report finally evaluates the solutions and draws conclusions with respect to the type of solutions and their
feasibility in terms of implementation effort/complexity.
Discussion:
CT3 Chairman commented that TR contains lot of valuable information for CT4 when they will reply to CT3 LS.
It was commented that the TR does not yet make a choice between the 9 identified solutions and that will be CT3 task
in the future meeting.
Decision:
CP-100582 Pseudo-CR on LCLS optional solutions and conclusions

23.889 v..
Source: Ericsson
Abstract:
The changes in this document do not overlap with those made in CP-100475, so it appears that this pseudo-CR could
apply on either the WG agreed TR in CP-100474 or the revision provided by the editor in 475.
Despite that fact that the TR is informative and does not enforce any specific normative specification during discussion
on the potential Normative protocol definitions in GERAN2#47 it appears that the above optionality is disputed. Since
this is the crux of the compromise that has enabled CT4 to propose the TR for approval it is imperative that all aspects
of the compromise and therefore options in the conclusions are clearly stated in the TR. This P-CR aims to make this
crystal clear and therefore avoid any further discussion at the next WG meetings which would naturally delay the
progress of any normative work.
Additionally some statements were included in the TR which are incorrect or have subsequently been clarified by
GERAN2 and as such should not be included in the TR if it is to be approved by CT plenary.
For example one proposal in the TR is that SID frames may be required to be sent on the user plane while a call is in
LCLS. CT4 concluded that this was not required by CT4 and asked GERAN2 to indicate if there was any need for this
from the BSS perspective. Companies proposing that this was needed could not convince the meeting that this was
needed.
Discussion:
Vodafone supports the proposed changes because of increased optionality.
Huawei and ZTE objected to the approval of the proposed pseudo-CR and requested the discussion to take place in the
WG as part of the normative discussions, and that the 3GPP TR 23.889 is approved as already agreed by the WG.
Decision:
Source: Ericsson
Discussion:
The main open items that could not be agreed and where no recommendation can be made but more CT4 work is
needed are
Correlation, which entity decides whether to do it or not and based on what signaling?
SID frames handling
Informal show of hands indicated exactly the same support for both versions CP-100475 and CP-100628 as the
preferred solution.
When CT Chairman asked how many delegates could live with the two versions, one after another, many delegates
indicated they could have either version, but there was slight majority in favour of CP-100475.
Ericsson indicated that they objected to the approval of CP-100475 due to the specific aspects raised above.
Decision:
17 Review of 3GPP Work Plan

CP-100566 3GPP Work Plan review at Plenary #49
Source: MCC
Abstract:
Release 7 ongoing
GERAN Testing
- 53087
HUGE - MS Conformance Test (target Mar 2011)
- 53088
REDHOT - MS Conformance Tests
(target Nov 2010)
RAN Testing
- 490000 Conformance Test Aspects Multiple Band and Multiple Frequency operation for LCR TDD
Release 8 ongoing
GERAN Studies
- 50590
MUROS - Multi-User Reusing-One-Slot (TR 45.914) started Nov 2007
CT6 Testing
- 420018 Test interworking of LTE Terminals with the USIM
- 490015 Test interworking of ISIM terminals with IP Multimedia Subsystem
GERAN Testing
- 54583
Testing for GELTE
RAN5 Conformance Test Aspects

- 490000 Conformance Test Aspects Paging Permission with Access Control (PPAC)
Release 9
- Stage 1 completed Dec 2008
SA1 exception concluded Jun 2009
- Stage 2 completed Jun 2009
SA2 exceptions concluded Sep 2009
- Stage 3 completed Dec 2009

(see next slide)
2 GERAN exceptions to Sep 2010
- RAN ASN.1 frozen Mar 2010
Release 9 ongoing
CT
- 450003 CT1 aspects - Support of Home NB and Home eNB enhancements
(need to complete new Requirement from SA1)
GERAN
- 38004
A-GNSS Testing Procedures
- 420002 Voice services over Adaptive Multi-user channels on One Slot

- 420004
VAMOS Stage 3
- 420005
VAMOS Radio Performance Requirements
GERAN Testing
- 490005 VAMOS - MS conformance testing
RAN5 Conformance Test Aspects

- 470017 Support for IMS Emergency Calls over LTE
- 470018 Positioning Support for LTE
- 440007 UMTS/LTE in 800 MHz for Europe
- 480029 Conformance Test Aspects - CT1 aspects of IMS Emergency Calls over GPRS and EPS
- 490000 Conformance Test Aspects Home NB enhancements for FDD
- 490000 Conformance Test Aspects Combination of DC-HSDPA with MIMO
- 490000 UE Conformance Test Aspects Enhanced Dual-layer transmission for LTE TDD
Release 10
- Stage 1 completed Mar 2010 SA1 exceptions completed Jun 2010
- Stage 2 freezing Sep 2010
No exception request so far
- Stage 3 freezing target Mar 2011

RAN time plan considering ITU-R IMT-Advanced schedule (RP-091000), i.e. Stage 3 submission by WP 5D meeting
#10 in Feb 2011:
- RAN Stage 3 approval and functional freeze
- ASN.1 freeze
Dec 2010 => Mar 2010 ?
Mar/Jun 2011 ?
Release 11
- Stage 1 freezing target To Be Defined
- Stage 2 freezing target
- Stage 3 freezing target
Discussion:
CT1 chairman commented that for CT1 part for TIGHTER (id 480002) GERAN has also made some work on this
topic, but CT1 were not informed of TIGHTER achievements. Same also with Support of multi-operator (id 490001).
The coordination between CT and GERAN needs to be improved in the future.
Huawei commented that Study on Policy and charging Rules Function (PCRF) failure and restoration (id 450001) is not
completed even indicated in WP presentation since there are some open issues on stage 2 level.
CT3 chairman clarified that it was agreed to stop study and go to normative work as soon as stage 2 is clarified by CT4.
CT3 has send a LS to CT4 for clarification of stage 2 requirements. The solution shall be selected during normative
work.
CT Plenary concluded that almost all CT related WI on Rel-9 are done. CT Chairman shall report that the only Rel-9
task in CT area that is not complete is HNB/CSG, which has gone down from 100% to 95% due to recently added new
requirements from SA.
Decision:
CP-100567 Standardization of Machine-type Communications

Source: MCC
Decision:
CP-100568 3GPP Green activities / Energy Saving

Source: MCC
Decision:
CP-100569 3GPP work items on HN(e)B and SON

Source: MCC
Decision:
CP-100570 3GPP Releases Descriptions R99 to Rel-11

Source: MCC
Decision:
CP-100653 3GPP Work Plan review at Plenary #49

Source: MCC
Decision:
18 Any other business

SA on block approval experiment:
In CT#49 block approval experimented on Rel-10 CRs only. The chairman was requested to ask for approval of
individual documents, instead of approval of all documents within each agenda item. It was seen useful to identify in
advance which documents might be sensitive. It was seen that not much time was saved in the meeting but it was agreed
to continue block approval in CT#50 and the experiment is extended to release 9. It was requested to keep the revisions
together with the original document (in the document allocation list) since it makes the document tracking easier.
Open Action Points after the previous Plenary CT#48

[AP 01/CT48] Action point: for Mr. Nigel Berry to check status of draft-drage-sipping-rfc3455bis.
- New RFC is required based on latest 24.229 to bring IETF up to date. Low priority on Keith Drages agenda
but anyone can take this on to update the RFC appropriately with a new one. 3GPP is currently covered by TS
24.229 anyway, hence lack of urgency. Any volunteers who want to take this on to bring this up to date?
[AP 02/CT48] Action point: for Mr Milan Patel (will be informed by CT Chairman) to check status of draft-ietf-patelecrit-sos-parameter.
- The document has been discussed in IETF #78 and there seems to be still a problem with what is the meaning
of the emergency registration. 3GPP only needs some indication on special registration for access control and
policy control purposes. Also in case of 3GPP access the UE must always perform emergency registration,
even when it with valid security credentials
[AP 03/CT48] Action point: for Mr. Dieter Jacobsohn to check status of draft-ietf-bliss-call-completion.
- This is in WG for last call. He work is basically done.
[AP 04/CT48] Action point: for Mr. Hannu Hietalahti to check status of draft-ietf-mmusic-ice-tcp.
- IETF #78 asked what is the real 3GPP use case for this draft. CT1 was requested to share information what is
the use case for this draft in CT. This information should be provided to IETF reflector.
- The authors have made a new version (-09) submitted on September 2nd. CT1 needs to check if the new
version has any impacts for CT1 work.
[AP 05/CT48] Action point: for Mr. Nigel Berry to check status of draft-drage-sipping-service-identification.
- With the latest revisions made during IETF #78, the draft has now been approved by IESG.
- New Draft has been provided by Mr. Keith Drage to deal with the comments. It's been through IESG review
however one AD has made a minor comment that a dummy Service ID should be provided in the Draft. This
has been rebutted as all this is already defined in 24.229 but the AD is abstaining as part of the acceptance.
19 Close of Meeting
The Chairman thanked the hosts, the North American Friends of 3GPP, for the meeting arrangements, the delegates and
the vice Chairmen Ms. Luisa Marchetto (Vice Chairman, AT&T), Mr. Rouzbeh Farhoumand (Vice Chairman, Huawei),
Mr. Adrian Neil (Vice Chairman, Vodafone) for running this challenging meeting with long meeting days. Chairman
thanked the Secretary of the meeting, Mr. Kimmo. Kymlinen, MCC, for taking the minutes of this meeting. Chairman
also gave special thanks to delegates to solve contentious issues smoothly to finish a meeting before lunch time on
Friday.
The meeting was closed on Friday17 th September 2010 11:58 local time.
Report prepared by: Kimmo Kymalainen/MCC

CT49 Report 110

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CT49 Report 110

Uploaded by

Copyright:

Available Formats

Third Generation Partnership Project (3GPP)

DRAFT Meeting Report

All Agenda Items.................................................................................................................................................

Conferencing Enhancement for Mp interface [eMp]...................................................................................

Enhancements for Completion of Communications Supplementary Service [eMMTel-CC]......................

All Agenda Items

Opening of the meeting

Approval of the agenda and registration of new documents

The document was Revised to CP-100433.

CP-100433 Proposed allocation of documents to agenda items

The document was Revised to CP-100434.

CT Chairman reminded the delegates to

Register to meetings they attend

Pick up their badge

Sign the attendance sheet

The document was Revised to CP-100435.

The document was Revised to CP-100436.

The document was Revised to CP-100437.

The document was Revised to CP-100651.

The document was Noted.

Reports from CT meetings and other groups

Report from last CT meeting

CP-100438 CT#48 meeting report for approval

The document was Revised to CP-100617.

CP-100617 CT#48 meeting report for approval

The document was Approved.

Reports from other groups

CP-100439 IETF status report

3GPP internal telco on the 28th of September 2010

All clear, Rel-6 was removed from the dependency document

1 draft has gone to IESG evaluation

3 new dependencies identified

1 draft approved by IESG

1 new addition to the list

1 new draft identified

Critical Rel-7 dependencies:

Should proceed as AD sponsored draft

New version needed

Discussion on how the interim nodes add their location information

Revised based on comments received in IETF #78 but still no progress

Agreed to proceed as AD sponsored document

3GPP only needs an indication of special registration

Discussion on the use case still going on

Critical Rel-8 dependencies:

The editor still needs to progress the work in IETF

draft-ietf-mmusic-ice-tcp was added recently

What is the real 3GPP use case of this draft?

Recently updated in September 2010

New draft, already in IESG approval

Needed for IMS media security

New addition to the list

Progress since previous TSGs:

draft-ietf-mext-binding-revocation (RFC 5846)

draft-ietf-netlmm-grekey-option (RFC 5845)

draft-ietf-netlmm-pmipv6-heartbeat (RFC 5847)

Approved by IESG and now in RFC editors queue:

IESG evaluation started:

3GPP actions required:

The real need to add location information along the path?

and how to encode it?

The following critical drafts are followed by TSG CT action points:

draft-drage-sipping-rfc3455bis (Keith Drage / ALU)

draft-drage-sipping-service-identification (Keith Drage / ALU)

draft-ietf-patel-ecrit-sos-parameter (Milan Patel / InterDigital)