sawg2meeting#107s2-150134rev2.docVIP

SA WG2 Meeting #107 S2-150134rev2 26 - 30 January 2015, Sorrento, Italy (revision of S2-150134) CR-Form-v11.1 CHANGE REQUEST 23.060 CR 1947 rev - Current version: 12.7.0 For HELP on using this form: comprehensive instructions can be found at /Change-Requests. Proposed change affects: UICC apps ME Radio Access Network Core Network X Title: Clarify handling of MS Info Change Reporting Action at change of Serving Node for an UE. Source to WG: Alcatel-Lucent, Alcatel-Lucent ShangHai Bell Source to TSG: SA2 Work item code: CNO_ULI Date: 2015-02-04 Category: F Release: Rel-12 Use one of the following categories:F (correction)A (mirror corresponding to a change in an earlier release)B (addition of feature), C (functional modification of feature)D (editorial modification) Detailed explanations of the above categories canbe found in 3GPP TR 21.900. Use one of the following releases:Rel-8 (Release 8)Rel-9 (Release 9)Rel-10 (Release 10)Rel-11 (Release 11)Rel-12 (Release 12)Rel-13 (Release 13)Rel-14 (Release 14) Reason for change: At change of Serving Node (MME/SGSN), the old serving Node provides the new serving node with on-going requirements (e.g. MS Info Change Reporting Action) for Location reporting received previously from the PGW. It is unclear whether this transfer is sufficient for the Location reporting procedure to go on (after the change of Serving Node) or whether the PGW should resend the Location reporting requirements. In case of mobility between LTE and 2G/3G, different RAT specific values of Change Reporting Action are used (refer to 29.274 § 8.61) for LTE and for 2G/3G and it makes sense to assume that a SGSN/MME does not take into account values of “Change Reporting Action that it is not meant to understand. This interpretation is also supported by TS 23.203 Table A.4.3-2 which states that: Location change (routeing area) and Location change (CGI/SAI) are triggers that are used for GERAN/UTRAN