TSG#24 Highlights

What is a Release? | What's in Release 5?| What's in Release 6?
| TSG T | TSG CN | TSG SA | TSG RAN

Previous Highlights: TSG#15  | TSG#16 | TSG#19 | TSG#20 | TSG#21 | TSG#22| TSG#23


Welcome!

Welcome to the latest edition of TSG Highlights! The aim is to provide you with a concise summary of the decisions and actions of the most recent 3GPP Technical Specification Group meetings held in June in Seoul, South Korea.

3GPP has five TSGs: CN (Core Network); RAN (Radio Access Network); T (Terminals); SA (Services and Systems Aspects); and GERAN (GSM EDGE Radio Access Network). This summary reports on the first four of these, as GERAN meetings take place separately from the other TSGs.

Please note, these summaries to do not constitute formal, approved reports of the meetings – they are opinions only and also may not be complete. They are offered for guidance only.


What's in Release 5?

For an overview of 3GPP Release 5 please have a look at this document which has been produced by the ETSI Mobile Competence Centre and which is a summary of all Release 5 Features>

What's in Release 6? What's the schedule? What follows that?

The expected contents of Release 6 (and even what lies beyond Release 6) can be found in the 3GPP workplan .

Back to top

TSG-CN (Core Network)

The TSG-CN meeting #24 took place in Seoul Korea, from 2nd – 3rd June 2004. A total of 56 participants were registered and 136 documents were presented.

Output:

Change Requests:

The number of Change Requests (CRs) to TSG-CN specifications approved is summarized in the following table:

Release
Total

Release 99

7

Release-4 CRs (Release-4 excluding Cat A)

21 (14)

Release-5 CRs (Release-5 excluding Cat A)

72 (61)

Release-6 CRs (Release-6 excluding Cat A)

186 (150)

Total CRs (Total excluding Cat A)

286 (225)

 

Work Items:

TSG-CN agreed one new  and one updated Work Item Description (WID):

Document
WID Title
Working Group (WG)
Release

NP-040245

[New] Gx for Flow Based Charging

CN3

Release-6

NP-040224

[Revised]  WLAN stage 3

CN4

Release-6

 

Specifications:

The following Technical Specifications/Reports (TS/TR) were noted for information by the plenary as being at least 50% complete.

Document
Title
WG
Release

NP-040195

24.147: Conferencing using IMS

CN1

Release-6

NP-040196

24.247: Messaging using IMS

CN1

Release-6

NP-040231

29.109: Generic Authentication Algorithm - Stage 3

CN2

Release-6

NP-040274

29.199-xy: Web Services API for OSA - Parlay X (multipart specification)

CN5

Release-6

NP-040243

29.209: Policy Control over Gq

CN3

Release-6

NP-040223

29.332: MGCF - IM Media Gateway (Mn)

CN4

Release-6

The following TS/TRs were approved and placed under change control.

Document
Title
WG
Release

NP-040194

TR 29.847, Conferencing based on SIP, SDP and other protocols; Functional models, information flows and protocol details

CN1

Release-6

NP-040289

TS 29.230, Diameter applications

CN4

Release-6

NP-040199

TR 24.841, Presence service based on Session Initiation Protocol (SIP); Functional models, information flows and protocol details

CN1

Release-6

NP-040200

TS 24.141, Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3

CN1

Release-6

 

Summary

SIP Related Issues: There was considerable progress in the SIP related areas of conferencing, messaging, and presence. Work continues with various specifications being either noted or approved.

WLAN Interworking: Work has progressed on WLAN interworking, however it has become clear that there is still much uncertainty with respect to scenario 3. In particular there are new interfaces such as Wg and Wp and a new normative annex in the stage 2 description that WG CN4 has not yet analysed. There is a high probability that the stage 3 work on these interfaces could slip past September. Discussions are needed with WG SA2 to decide which of these interfaces are mandatory and which can be postponed to a later release. Further discussion is required between WGs CN3 and CN4 on responsibility for the Wg interface, however for the time being, the responsibility remains with CN4.

Transfer of GUP specifications: TSGs CN and T agreed to the transfer of Generic User Profile (GUP) specifications 23.241 and 24.241 from WG T2 to CN4.
In addition a working arrangement has been established between the Liberty Alliance Project and 3GPP to allow 3GPP delegates access to required specifications and Liberty Alliance experts.

Transfer of OSA Stage 2: WG SA2 has also recommended the transfer of the Open Service Access (OSA) stage 2 (23.127). No decision was taken at the TSG-CN#24 meeting. WG CN5 will need to take a position whether to accept this work and to liaise with WG SA2.

Close of CN2: CN formally closed WG CN2 and transferred its responsibilities to CN4. CN2 was thanked for its contribution to GSM in general and CAMEL specifically, and a plaque commending CN2 for its contributions was presented at TSG-SA#24. The plaque will be displayed at the MCC offices. Revised CN4 Terms of Reference were approved refreshing the description of responsibilities and expanding its scope (document NP-040233).

Input to ITU-T SSG : ITU-T Special Study Group (SSG) has requested early input on Release 6 from 3GPP, however TSG-CN recommends that Q.1741.4 (the 3G "Roadmap" maintained by the SSG) be based upon the output of the December 2004 TSGs. The response is in document NP-040290.

Activities by WG:

The following are the actions requested by the TSG-CN and TSG-SA plenaries for the CN Working Groups. Fulfilment is of course dependent on the supporting companies introducing the appropriate contributions into the WGs.

All the active CN WGs were requested to prepare a list of those items that will not be completed by the next TSG-CN meeting (CN#25) and to indicate when the likely completion date is.  If there is optional functionality whose deletion could affect the completion date, this should be indicated also.

CN1:

CRs clarifying the use of Radio Access Technology (RAT) in background scan were approved. The CRs can be found in NP-040202. The corresponding WG SA1 CRs were approved. However, two conditional WG SA1 CRs on the identification of Frequency Division Duplex (FDD) and Time Division Duplex (TDD) in Public Land Mobile Network (PLMN) selector lists (22.011 CR059) and Mobile Behaviour when performing periodic network selection attempts in uncoordinated networks (22.011 CR065) were rejected.

There was controversy with a WG SA1 CR which indicated that Service Set Identifier (SSID) selection was out of scope of PLMN selection. Some companies then opposed the WG CN1 use of SSID operator and user preference lists. In the end a compromise CR was approved in SP-040475 which is silent on the use of SSID and permits CN1 to continue with its current assumptions.

A WG SA1 WID for a feasibility study on the behaviour of multi-system User Equipments (UEs) was approved (SP-040306). In addition, a response Liaison Statement was sent to IEEE 802.21 identifying the 3GPP working groups dealing with handover. IEEE 802.21 plans to address the topic of multi-system handover, and WG CN1 should be aware of this ongoing work.

Companies were urged to bring in contributions related to IP Multimedia System (IMS) local services or to indicate that there is no interest in progressing this issue.

CN2:

WG CN2 work was transferred to CN4. TSG-CN thanked CN2 for their contributions to both GSM and UMTS.

CN3:

A WID for Rx is expected from WG CN3 at CN#25.

CN4:

WG SA3 had reactivated the MapSec work (SP-040280). This work includes the Ze interface which TSG-CN had earlier deleted due to lack of interest. It was concluded that WG CN4 should not reintroduce a stage 3 WID into TSG-CN unless there is clear evidence that there are companies which will actively progress this work. CN4 should also consider what work can be accomplished in the Release-6 timeframe as there may be measures such as work on the map protection profile that require less work than the Ze interface.

CN5:

WG CN5 was tasked to bring Release-6 CRs to next meeting.

CN5 will determine if it wishes to take responsibility for Technical Specification TS 23.127 (Virtual Home Environment Stage 2 description) and will liaise as necessary with SA2 (and CN) on this.

Companies were urged to consider providing a rapporteur for SIP presence mapping.

Input from WG SA1 on the Generic User Profile (GUP) was requested at SA. It was indicated that if no input was received, this item would be dropped from Release-6.

Back to top

TSG-RAN (Radio Access Network)

Technical Specification Group (TSG) RAN meeting #24 took place in Seoul, Korea, between Wednesday 2 and Friday 4 June 2004. 91 participants registered and 121 documents were presented.

The approved Change Requests (CRs) to TSG-RAN specifications are summarized in the following table:  

Working Group
Release  
WG1  
WG2
WG3
WG4
Total
Release 99   8 2 10
Release 4 CRs (Release 4 excluding Cat A)   14 (7) 7 (7) 21 (14)
Release 5 CRs (Release 5 excluding Cat A)   2 (2) 39 (30) 23 (23) 15 (8) 79 (63)
Release 6 CRs (Release 6 excluding Cat A) 6 (4) 45 (9) 39 (16) 28 (19) 118 (48)
Total CRs (Total excluding Cat A)   8 (6) 106 (54)  62 (39) 52 (36) 228 (135)

A preliminary agreement was reached on a date and location for the proposed workshop on RAN future evolution: 2 -3 November in Toronto, Canada.

Discussions about Working Group (WG) meetings for year 2005 noted that the reduction of the number of official meetings has spawned a number of ad-hoc and bis meetings, which in fact maintains the number of travels but complicates the year planning for the participants. The WG1 chairman noted that 6 would be the right number of meetings for his group in 2005, WGs 3 and 4 each foresaw 4 meetings, whilst the prospect for WG2 could not yet be provided.

Release 99, Release 4 & Release 5

A problem related to User Equipments (UEs) in the market that seem not support the CELL/URA_PCH states was presented. TSG-RAN was asked if it could be solved with the Early UE handling procedure, but it found very difficult to analyse the issue given the limited information disclosed. However, on a first approach, the problem doesn't seem to fall into the Early UE category; it seems rather the case of equipment not compliant with the specifications as support for those states is mandatory in Release '99.

WG1 had been requested to study the High-Speed Downlink Packet Access (HSDPA) reconfiguration issue discussed in the last TSG-RAN. WG1 concluded that the infrequency of occurrence of the problem identified does not justify the complexity required.

It was confirmed that Release 5 Abstract Syntax Notation No. 1 (ASN.1) is frozen from June 2004.

WG4 had agreed on a requirement for the UE power back off when the High Speed Dedicated Physical Control Channel (HS-DPCCH) is transmitted. The CRs were presented to TSG-RAN for Release 5 and Release 6. Release 5 was approved without further comments, but objections were received concerning Release 6 since the introduction of Enhanced Uplink in that Release would need future modification of the requirement, to take into account the sending of a new channelization code. It was agreed that WG4, together with WG1, will analyse the implications of having Release '99 channels + HS-DPCCH + Enhanced Dedicated Channel (EDCH) in Release 6 (document RP-040251).

The Internet Protocol- Asynchronous Transfer Mode (IP-ATM) interworking debate was solved without the need of a vote. A set of CRs had been agreed off-line by the companies involved in the discussion and was approved without objections.

Release 6 and beyond

The following Work Items (WI)/Study Items (SI) were closed at the meeting:

Under WI "Performance Requirements of Receive Diversity for HSDPA", the need to signal the enhanced performance as a UE capability was considered at length. The last WG4 meeting had concluded that this was not necessary, but several companies requested in RAN that the admission control aspects are taken into consideration in the analysis. WG4 will look at the issue again, with the help of WG2 expertise in the area.

TR 25.802 " Remote Control of Electrical Tilting Antennas" was presented for information (RP-040185).

It was noted that WG4 may need to produce requirements for the particular combination of channels and parameters that MBMS uses, although the existing MBMS WI Description & schedule does not take this into account. September is the completion date for WG1 work on MBMS, but WG2 & WG3 will need at least 3 additional months.

TSG-RAN could not agree whether Network Sharing should be a mandatory feature for Release 6 UEs. As it is a service requirement issue, the discussion should take place in TSG-SA.

The Study on Radio link performance enhancements, which focus on HSDPA enhancements, was considered completed by WG1 and its rapporteur. Two WI proposals based on the Study were presented, for Channel Quality Indicator (CQI) enhancements and for Acknowledgement/ Negative Acknowledgement (ACK/NACK) enhancements. Some companies believed that the gains found in WG1 with the first technique did not justify the additional complexity and the proposal was rejected. For the second, it was argued that the coverage improvement claimed had not been proved in WG1. It was agreed finally that the Study phase would be kept open for 3 additional months in order to clarify in WG1 the benefits of the ACK/NACK enhancement. The related TR 25.899 "HSDPA enhancements" was approved and put under change control.

A new WI for "Inclusion of Uplink TDOA (Time Difference of Arrival) UE positioning method in the UTRAN specifications" was proposed. It was agreed that a Study phase should proceed, and WG1 & WG2 were asked to produce a Description Sheet for approval at next RAN.

  Back to top

TSG-T (Terminals)  

  At its meeting in June 2004 in Seoul, Korea, Technical Specification Group TSG-T has been working on the maintenance of the existing Releases, and has continued work on Release 6. Work on testing always follows the main specification task, and this is so for User Equipment (UE) testing, which is ongoing for Release 99, Release 4, and for Release 5 (see the "Testing" section below).

Maintenance work was performed on the existing Releases of Multimedia Messaging Services (MMS) specifications and some new functionality has been added to Release 6. MMS Release 6 will add new functionality to the existing MMS standard in several areas which will further enhance the user experience. The functional enhancement approved at this meeting is the option for a Value Added Service Provider to define delivery conditions which have to be met for message submission by the Multimedia Messaging Service Centre (MMSC) - e.g. taking roaming conditions into account. Further work on MMS is ongoing in the following areas: Operator Specific Services, IMS Deferred Messaging, Multiple Relay/Servers, Application ID, reference points MM1, MM4, MM7 enhancements.

It was agreed to transfer the work on Generic User Profile (GUP) to TSG-CN (Core Networks). The part of the GUP work which was handled by Working Group (WG) T2 will now be continued by WG CN4 which has already been responsible for several GUP specifications. The transfer includes Technical Specification TS 23.241 Generic User Profile (GUP) – Stage 2; Data Description Method and TS 24.241 GUP Common objects. GUP will provide easy access and sharing of end-user profile data, including data about the user's devices, services enabled, billing arrangements, address, calendar and preferences. This will lead to better service experience for the user.

Again some new functionality was introduced for the Short Message Service (SMS): The Voice Mail Information has been enhanced allowing voice mail systems to convey via SMS to the user enhanced information regarding voice mail messages and voice mail box status such as a list of voice messages, the time a particular voice message was left, who it was from – if known, message duration etc.

T2 presented to TSG-T its reply to a questionnaire on the need for national co-ordination for the allocation of short codes for SMS, MMS and Unstructured Supplementary Service Data (USSD) recently issued by the CEPT Electronic Communications Committee and presented this to TSG-T. TSG-T forwarded it to TSG-SA (Services & System Aspects) to discuss the matter together with a Liaison Statement from WG SA1 to SA on this topic. No further action was taken by TSG-T and it is up to individual members to convey this document to CEPT.

Several Change Requests (CR) were approved on (Universal) Subscriber Identity Module (SIM/USIM) related subjects. A list of features was introduced in the USIM to support Wireless Local Area network (WLAN).

Voice Groups Call Services (VGCS) requires the support of VGCS key derivation in the USIM. The new Release-6 requirements for Voice Group Call Service (storage of ciphering algorithm identifiers, key derivation, and secure key storage) have been fulfilled and the corresponding CR approved.

The request to Display Multimedia Messages from the USIM has been postponed until WG T3 receives a clarification from WG SA1 on the service requirement.

Creation of the Release-5 USIM Application Test Specification (TS31.121) was postponed to a WG T3 adhoc meeting. T3 needs guidance on whether Elementary File EF_KC has to be stored on the USIM when accessing a GPRS/EDGE Radio Access Network (GERAN).

Voltage class update for mini-UICC (UMTS Integrated Circuit Card) is under discussion in WG T3.

Testing

Progress was reported on the area of Tree & Tabular Combined Notation (TTCN) test case development. The high pace of TTCN test case approvals has been maintained. 90 GCF (Global Certification Forum) Batch 1 test cases completed, 73 GCF Batch 2 test cases completed, 42 GCF Batch 3 test cases completed. 

The proportion of complete Radio Resource Management (RRM) tests is approximately 70%. A number of outstanding RRM test cases was noted in WG T1: completion within 3 months is necessary for subsequent validation/ approval by the Global Certification Forum, GCF, before the end of 2004.

The first Assisted-GPS (A-GPS) test cases (prose) were approved.

Good progress on High Speed Downlink Packet Access (HSDPA) was reported:

90% completed for the FDD RF testing area

50% completed for the FDD protocol testing area

Low Chip Rate Time Division Duplex (LCR TDD): The TD-SCDMA Industry Alliance (TDIA) is now supplying 4 experts on a voluntary basis to work alongside Task Force TF 160 to develop LCR TDD TTCN. TSG-T endorsed WG T1's proposal to a 2003 underspend of 68K Euros to contract CCSA/TDIA companies resources to support LCR TDD work. The expectation is that 90 – 100 tests will be coded by December 2004, and TDIA representatives are hoping that more WG T1 resources will be used to develop LCR TDD TTCN test cases in 2005.

WG T1 has produced an Internal Working Document (iWD) that identifies those tests that it cannot verify due to circumstances beyond its control. The GCF has agreed to use the iWD. This is significant in the calculation of batch completion from both a verification and GCF validation point of view. Currently there are four batch 2 test cases in the iWD.

Estimated completion date of all GCF high priority tests is November 5th, 2004.

TSG-T endorsed WG T1’s proposal to use 6 man months of resources to co-fund the Release and Configuration Manager (RCM) in 2005, as in 2004, conditional on next year's budget being approved.

  Back to top

 TSG-SA

Work Management

The TSG-SA#24 meeting in June 2004 concluded the discussion started some months ago on “Early implementation” -or how to freeze a given Feature to allow its implementation when the corresponding Release is not yet frozen (document SP-040235). The main decisions were to add a field “Candidate for Early Implementation” in the Work Item Description form (WID) and to create an 800-series “Early Implementation Technical Report” as a guide for early implementations. The Technical Report (TR) can be converted to the 900-series or a new numbering scheme may be introduced later on if needed. A Change Request (CR) to the 3GPP Working Procedures (TR 21.900) was provided to reflect this. TSG-SA also decided to add a column in the 3GPP Work Plan to flag the features that are candidates for early implementation.

The Working Procedures were also modified to state that target dates should be set for the freezing of each individual stage on all non-frozen releases: typically at time of freezing of stage n in Release x, the target date of stage n+1 of Release x should be set.

A snapshot of all the 3GPP work was provided in the Work Plan slide review (SP-040480), with a pre-identification of the content of Release 6, which will be officially defined by September.

TSG-SA noted clarifications on the handling of “Technically Motivated Work Items”, explaining that new Features do not necessarily respond to or anticipate a market demand but can be justified just from a technical point of view. In such cases they would not involve Working Group (WG) SA1.

Mr. Takashi Koshimizu, NTT DoCoMo, was appointed as TSG-SA Vice Chairman.

Cooperation with external fora

The TSG-noted TSG-CN's response to ITU-T about Release-6 specifications (see TSG-CN highlights).

Documents were tabled presenting the 3GPP and Open Mobile Alliance (OMA) perspectives of dependencies between OMA and 3GPP (documents SP-040420 and SP-040232). For future meetings, SA will use the 3GPP Work Plan with the OMA tasks identified accordingly. Informal contacts will be established between the 3GPP Work Plan manager and the chair of the OMA Release Planning and Management Committee so that the information on dependencies and work progress can be updated before relevant meetings.

A Liaison Statement to IEEE 802.21 provided information about 3GPP WGs with which there should be co-operation in future, given that the IEEE 802.21 technology will include handover capability. The major milestones for IEEE 802.21 are: completion of the system requirements by August, intended publication of the final standard by March 2006.

Other LSs were from:

WG progress

SA1

Working Group SA1 is working on the following issues: Messaging; Location Services (LCS); IP Multimedia Services (IMS); Wireless LAN (I-WLAN); Generic User Profile (GUP); Priority Services and Multimedia Broadcast and Multicast Services (MBMS).

The main discussion under SA1 concerned the PLMN selection and background scan, in particular on whether the Radio Access Technology (RAT) has to be taken into account or not for the selection process. The conclusion is unchanged, i.e. the RATs have to be distinguished but only up to a certain point (e.g. between UTRAN and GERAN but not between UTRAN’s modes: FDD, TDD high rate and TDD low rate). It was however noted that this might be needed later, when it could then be difficult to introduce these selection criteria.

A CEPT Electronic Communications Committee (ECC) consultation about the use of short codes for SMS, MMS and USSD and the reaction to this by WG T2 was noted (see TSG-T highlights).

New SA1 Work Items (WI) were approved by TSG-SA: “Selective Disabling of UE Capabilities” (previously presented as “Network Protection against Virus Infected Mobiles”); “All-IP Network Feasibility Study”; “Enhancements of Voice Group Call Service (VGCS) in public networks” (VGCS differs from Push to talk over cellular (PoC) in that the latter does not support encryption, emergency services, etc.); “A-GNSS (Assisted Global Navigation Satellite Systems) concept to extend A-GPS (Assisted Global Positioning System) to include GALILEO”; “LCS (Location Services) for 3GPP Interworking WLAN”. This will be part of LCS enhancements 3, to be created (LCS enhancements 2 is for Release 6).

A WI for “Multi system mobile stations”, to define how a multi system UE should perform system selection and network operator selection between the supported systems, was noted. A Feasibility Study will be conducted first.

A WI “Network Selection Preferred List” was presented to address the problem of the current network selection procedure leading to a roaming UE selecting a network with which the HPLMN does not have a GPRS roaming agreement, even though there is a network available with GPRS roaming agreement in place. Because of objections, this WI was not accepted.

It was agreed to have a new Feature being “Feasibility Study on IMS with real time services deployments” with two children Building Blocks: “Feasibility Study on IMS services using CS bearers” and “Combining CS calls and IMS sessions”). These are to address how to handle simultaneously a CS call correlated to an IMS session (e.g. whether the CS call or the IMS session is established first, and/or whether all the media components are established at call/session establishment or added afterwards).  

SA2

Three Technical Reports were presented for information (Version 1.0.0): TR 23.898  “Access Class Barring and Overload Protection”, TR 23.979  "3GPP enablers for OMA PoC Services" and TR 23.801  "Potential Mechanisms for CS Domain Video and Voice Service Improvements".

One TR and two Technical Specifications (TS) were presented for approval (Version 2.0.0): TR 23.977  "Bandwidth and Resource Savings and Speech Enhancements for CS Networks (BARS)"  TS 23.251  "Network Sharing" and TR 23.981  "Interworking aspects and migration scenarios for IPv4 based IMS Implementations".

Five WIDs were updated, and two new ones were presented: "E2E QoS Enhancements" and "IMS Enhancements for NGN".

SA2 proposed the transfer of OSA Stage 2 (TS 23.127) to WG CN5, subject to CN5 agreement. A possible need for further work on security issues was identified.  

SA3

SA3 is currently working on Lawful interception, IMS security, Network domain security: IP layer (one CR), Network domain security: authentication framework (three CRs), UTRAN access security, GERAN access security, Generic authentication architecture (GAA): lot of activities, WLAN inter-working security, MBMS security, Presence security.

SA4

Codec selection for MMS: the two codecs in competition were AMR WB+ and enhanced aacPlus. SA4 was tasked to draft two change requests (CRs) to the MMS codec and formats specification (TS 26.140), one CR for each of the competing codec. These CRs are to be drafted such that there is no requirement that a terminal supporting decoding by one of the codecs shall also support encoding by that codec, and it shall be clearly indicated for which scenario (type of content, bit rate etc.) each codec is recommended. The CRs will be presented to TSG-SA when the specifications for these two codecs are completed and approved. SA will then decide whether to approve both, only one or none of the CRs.

A similar identification will be required of the scenarios (type of content, bit rate etc) for which a codec is recommended should be made for the case of packet switched streaming. It is expected that the codecs to be used for MBMS would be the codecs already used for other applications, or a subset hereof.

One TR and three TSs were approved (Version 2.0.0): TR 26.935 "Packet Switched Conversational Multimedia Applications; Performance Characterisation of Default Codecs"; TS 26.245 "Transparent end-to-end packet switched streaming service (PSS); Timed text format"; TS 26.246  "Transparent end-to-end packet switched streaming service (PSS); 3GPP SMIL Language Profile"; TS 26.243 "ANSI C code for the Fixed-Point Distributed Speech Recognition Extended Advanced Front-end".

The following were presented for information (version 1.0.0):

·         TS 26.401 "General description"; TS 26.402 "Additional decoder tools"; TS 26.403 "Encoder specification; Advanced Audio Coding (AAC) part"; TS 26.404 "Encoder specification; Spectral Band Replication (SBR) part"; TS 26.405 "Encoder specification; Parametric stereo part"; TS 26.410 "ANSI-C code".

The following Release 6 Work Items were approved:

SA5

Four TSs were approved: TS 32.171 “Subscription Management (SuM) resources Integration Reference Point (IRP); Requirements”; TS 32.342 “File Transfer (FT) IRP: Information Service (IS)”; TS 32.352 “Communication Surveillance (CS) IRP: IS”; TS 32.353 on “CS IRP: Common Object Request Broker Architecture (CORBA) Solution Set (SS)”.

The following were presented for information: TS 32.741 “Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) IRP: Requirements”; TS 32.742 “CM; STN interface NRM IRP IS”; TR 32.804 “Telecommunication management; Control of Remote Electrical Tilting (RET) antennas; Requirements”; TS 32.431 “Performance measurement collection IRP: Requirements”.