3GPP TSG CN Plenary Meeting #11, Palm Springs, U.S.

A 14th - 16th March 2001 Source: Title: Agenda item: Document for:
TSG CN WG1 CRs to Rel-4 on Work Item GPRS

Tdoc NP-010129

7.13
APPROVAL

Introduction:

This document contains 4 CRs on R99 Work Item ”GPRS”, that have been agreed by TSG CN WG1, and are forwarded to TSG CN Plenary meeting #11 for approval.

Spec
24.008 24.008 24.008 24.008

CR
359 360 366 367

Rev Doc-2nd-Level Phase
1 1 1 1 N1-010182 N1-010183 N1-010212 N1-010213 R99 Rel-4 R99 Rel-4

Subject
Connection re-establishment on forward handover without Iur Connection re-establishment on forward handover without Iur Clarification of TFT request during secondary PDP context activation Clarification of TFT request during secondary PDP context activation

Cat
F A F A

Ver_C
3.6.0 4.1.1 3.6.0 4.1.1

How to create CRs using this form: CR page 1 . The release cause “Directed signalling connection re-establishment” in the RRC CONNECTION RELEASE message is added was added in 25. The release cause distinguishes the case when a signalling connection shall be requested by the upper layers immediately after the RRC connection release. see bottom of this page or look at the pop-up text over the Proposed change affects: = symbols. R98 (Release 1998) C (Functional modification of feature) R99 (Release 1999) D (Editorial modification) REL-4 (Release 4) Detailed explanations of the above categories can REL-5 (Release 5) be found in 3GPP TR 21. A CR to 23. = = = X Other core specifications Test specifications O&M Specifications = 23. Reason for change: = A procedure needs to be defined for the NAS triggerred signalling connection reestablishment for the case when the UE enters a new cell but there is no Iur support to reach the SRNC. = (U)SIM ME/UE X Radio Access Network Core Network X = = Source: Work item code: = = Category: Title: Connection re-establishment on forward handover without Iur Lucent Technologies. Siemens. Beijing. Summary of change: = The NAS in the UE shall initiate a RAU when the release cause “Directed signalling connection re-establishment” in the RRC CONNECTION RELEASE message is received to re-establish a signalling connection.331 to identify this case. The RA update procedure will also trigger the release of any existing Iu connection from SGSN to old SRNC.060 Other comments: Changes to UTRAN specifications have already been approved. Consequences if not approved: Clauses affected: Other specs Affected: = Failure to deliver downlink packets to the UE after an RRC failure due to no Iur connection to the SRNC.060 will be presented at the next S2. Ericsson GPRS F = Release: = Date: 18/01/2001 R99 Use one of the following releases: Use one of the following categories: 2 (GSM Phase 2) F (essential correction) R96 (Release 1996) A (corresponds to a correction in an earlier release) R97 (Release 1997) B (Addition of feature).6.900.008 CR 359 = rev 1 = Current version: 3.0 = For HELP on using this form. China Tdoc N1-010182 CR-Form-v3 CHANGE REQUEST = 24.3GPP TSG-CN1 Meeting #15 15-19 January 2001.

look for the directory name with the latest date e.g. The symbols above marked closest to.htm. Below is a brief summary: 1) Fill out the above form. Delete those parts of the specification which are not relevant to the change request. 2000-09 contains the specifications resulting from the September 2000 TSG meetings. 3) With "track changes" disabled.org/3G_Specs/CRs. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes.3gpp. All 3GPP specifications can be downloaded from the 3GPP server under ftp://www. paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause containing the first piece of changed text.org/specs/ For the latest version. = contain pop-up help information about the field that they are 2) Obtain the latest version for the release of the specification to which the change is proposed. CR page 2 .Comprehensive information and tips about how to create CRs can be found at: http://www.3gpp.

- - - Section 4.7.18. This procedure is used by GPRS MSs in MS operation modes A or B. if the network operates in network operation mode I. The routing area updating attempt counter shall be reset when: a GPRS attach procedure is successfully completed. The routing area updating attempt counter shall be incremented as specified in section 4. see Section 4.1 describes the routing area updating procedures for updating the routing area only. UMTS to GSM and for GSM to UMTS intersystem change. IMSI attach for non-GPRS services when the MS is IMSI attached for GPRS services.7. The combined routing area updating procedure used to update both the routing and location area is described in section 4. ** Next Modification ** 4.7. The routing area updating procedure is always initiated by the MS. see section 4. The Force to standby information element shall be ignored by the MS. or periodic routing area updating.7.7.2.331. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS or for GPRS and non-GPRS services independent of the network operation mode.1.1. The network shall always indicate Force to standby not indicated in the Force to standby information element.7.2.5. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services if the network operates in network operation mode II or III. 4.7. specific actions shall be performed. then the MS shall enter PMM-IDLE mode and initiate immediately a normal routing area update procedure (the use of normal or combined procedure depends on the network operation mode in the current serving cell) regardless whether the routing area has been changed since the last update or not.5 - Routing area updating procedure This procedure is used for: normal routing area updating to update the registration of the actual routing area of an MS in the network. Depending on the value of the routing area updating attempt counter. To limit the number of subsequently rejected routing area update attempts. in GSM.5. CR page 3 .4 Handling of Force to standby in UMTS (UMTS only) Force to standby is not applicable for UMTS.5. in UMTS. or a routing area updating procedure is successfully completed. see GSM 04.5.2.4.2.5 RA Update procedure for Signalling Connection Re-establishment (UMTS only) When the MS receives an indication from the lower layers that the RRC connection has been released with cause “Directed signalling connection re-establishment”. resuming GPRS services when the RR sublayer indicated a resumption failure after dedicated mode was left. to re-synchronize the PMM mode of MS and network after RRC connection release with cause “Directed signalling connection re-establishment”.7. combined routing area updating to update the registration of the actual routing and location area of an MS in the network. This procedure is used by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services provided that the network operates in network operation mode I. a routing area updating attempt counter is introduced.5. see TS 25.7. It is only invoked in state GMM-REGISTERED.

Note: The re-establishment of the radio bearers of active PDP contexts is done as described in section “Service Request procedure”. or at request from registration function. ** Next Modification ** 4.2. the routing and location area identification are broadcast on the broadcast channel(s) or sent to the MS via the PS signaling connection. GSM. expiry of timer T3302. Aborted GMM procedures shall be repeated after the combined routing area updating procedure has been successfully performed. if the MS is in state GMM-REGISTERED and if the network operates in network operation mode I: when a GPRS MS that is IMSI attached for GPRS and non-GPRS services detects a change of the routing area in state GMM-REGISTERED and MM-IDLE. in UMTS.5. user data reception shall be possible. A combined routing area updating procedure shall abort any ongoing GMM procedure. User data transmission in the network shall not be suspended during the routing area updating procedure. to re-synchronize the PMM mode of MS and network after RRC connection release with cause “Directed signalling connection re-establishment”.7. User data transmission in the network shall be suspended during the routing area updating procedure.and additionally when the MS is in substate ATTEMPTING-TO-UPDATE: a new routing area is entered.1). In UMTS.5. when a GPRS MS that is IMSI attached for GPRS services wants to perform an IMSI attach for non-GPRS services. In UMTS.1. or. see Section 4. as well as a list of "forbidden location areas for regional provision of service".2. the routing and location area identification are broadcast on the broadcast channel(s).4. in which case the update type IE shall be set to "Combined RA/LA updating with IMSI attach". Aborted GMM procedures may be repeated after the combined routing area updating procedure has been successfully CR page 4 . The handling of these lists is described in section 4. when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this UE. In. after a CM SERVICE REJECT message with cause value #4 is received by the mobile station (see section 4. user data transmission in the MS shall be suspended during the routing area updating procedure. if a new P-TMSI is assigned.1. In GSM.5. A combined routing area updating procedure shall abort any ongoing GMM procedure. The mobile equipment shall contain a list of "forbidden location areas for roaming". In UMTS. The ROUTING AREA UPDATE REQUEST message shall always be the first message sent from the MS in the new routing area after routing area change.7. user data transmission and reception in the MS shall not be suspended during the routing area updating procedure. the network shall progress the routing area update procedure as normal and release the previous PS signalling connection when the routing area update procedure has been accepted by the network. after termination of a non-GPRS service via non-GPRS channels to update the association if the MS has changed the LA during that non-GPRS service transaction.1 Combined routing area updating procedure initiation The combined routing area updating procedure is initiated only by a GPRS MS operating in MS operation modes A or B.

A GPRS MS in MS operation mode A shall initiate the combined routing area updating procedure with IMSI attach after the circuit-switched transaction has been released if a GPRS attach was performed during the circuit-switched transaction and provided that the network operates in network operation mode I. The value of the update type IE in the message shall indicate "combined RA/LA updating".performed. A GPRS MS in MS operation modes A or B that is in an ongoing circuit-switched transaction. CR page 5 . if the MS has changed the RA during the circuit-switched transaction and if the network operates in network operation mode I. it may set a follow-on request pending indicator on. A GPRS MS in MS operation mode A shall perform the normal routing area update procedure during an ongoing circuit-switched transaction. shall initiate the combined routing area updating procedure after the circuit-switched transaction has been released. starts timer T3330 and changes to state GMM-ROUTING-UPDATING-INITIATED and MM LOCATION UPDATING PENDING. if the MS wishes to prolong the established PS signalling connection after the normal routing area updating procedure when it is served under UMTS area. Note: The re-establishment of the radio bearers of active PDP contexts is done as described in section “Service Request procedure”. the value of the update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "combined RA/LA updating with IMSI attach". The ROUTING AREA UPDATE REQUEST message shall always be the first GMM message sent from the MS in the new routing area after routing area change. when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this UE. If for the last attempt to update the registration of the location area a MM specific procedure was performed. In UMTS. Furthermore the MS shall include the TMSI status IE if no valid TMSI is available. In UMTS. the network shall progress the routing area update procedure as normal and release the previous PS signalling connection when the routing area update procedure has been accepted by the network . To initiate a combined routing area updating procedure the MS sends the message ROUTING AREA UPDATE REQUEST to the network.

4.1 = For HELP on using this form. The release cause “Directed signalling connection re-establishment” in the RRC CONNECTION RELEASE message is added was added in 25. R98 (Release 1998) C (Functional modification of feature) R99 (Release 1999) D (Editorial modification) REL-4 (Release 4) Detailed explanations of the above categories can REL-5 (Release 5) be found in 3GPP TR 21.060 will be presented at the next S2. A CR to 23.2. China Tdoc N1-010183 CR-Form-v3 CHANGE REQUEST = 24.2. Ericsson GPRS A = Release: = Date: 12/01/2001 REL-4 Use one of the following releases: Use one of the following categories: 2 (GSM Phase 2) F (essential correction) R96 (Release 1996) A (corresponds to a correction in an earlier release) R97 (Release 1997) B (Addition of feature). = = = 4.7. Reason for change: = A procedure needs to be defined for the NAS triggerred signalling connection reestablishment for the case when the UE enters a new cell but there is no Iur support to reach the SRNC. Siemens. Summary of change: = The NAS in the UE shall initiate a RAU when the release cause “Directed signalling connection re-establishment” in the RRC CONNECTION RELEASE message is received to re-establish a signalling connection.5.3GPP TSG-CN1 Meeting #15 15-19 January 2001.5. 4.060 Other comments: Changes to UTRAN specifications have already been approved. The release cause distinguishes the case when a signalling connection shall be requested by the upper layers immediately after the RRC connection release. The RA update procedure will also trigger the release of any existing Iu connection from SGSN to old SRNC.008 CR 360 = rev 1 = Current version: 4. = (U)SIM ME/UE X Radio Access Network Core Network X = = Source: Work item code: = = Category: Title: Connection re-establishment on forward handover without Iur Lucent Technologies. Consequences if not approved: Clauses affected: Other specs affected: = Failure to deliver downlink packets to the UE after an RRC failure due to no Iur connection to the SRNC.1 X Other core specifications Test specifications O&M Specifications = 23. Beijing. see bottom of this page or look at the pop-up text over the Proposed change affects: = symbols.5.331 to identify this case. How to create CRs using this form: CR page 1 .900.1.7.7.

org/specs/ For the latest version.htm. The symbols above marked closest to.3gpp.Comprehensive information and tips about how to create CRs can be found at: http://www. CR page 2 . look for the directory name with the latest date e.org/3G_Specs/CRs.g. paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause containing the first piece of changed text. Below is a brief summary: 1) Fill out the above form. = contain pop-up help information about the field that they are 2) Obtain the latest version for the release of the specification to which the change is proposed.3gpp. 2000-09 contains the specifications resulting from the September 2000 TSG meetings. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes. All 3GPP specifications can be downloaded from the 3GPP server under ftp://www. Delete those parts of the specification which are not relevant to the change request. 3) With "track changes" disabled.

1.2. combined routing area updating to update the registration of the actual routing and location area of an MS in the network.18.2.7.1 describes the routing area updating procedures for updating the routing area only. The routing area updating attempt counter shall be reset when: a GPRS attach procedure is successfully completed. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services if the network operates in network operation mode II or III. This procedure is used by GPRS MSs in MS operation mode C and by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS or for GPRS and non-GPRS services independent of the network operation mode. a routing area updating attempt counter is introduced.7. or periodic routing area updating. see GSM 04.331. ** Next Modification ** 4. To limit the number of subsequently rejected routing area update attempts. The Force to standby information element shall be ignored by the MS.2.7. then the MS shall enter PMM-IDLE mode and initiate immediately a normal routing area update procedure (the use of normal or combined procedure depends on the network operation mode in the current serving cell) regardless whether the routing area has been changed since the last update or not. see Section 4. - - - Section 4. see TS 25. in GSM. 4.5 RA Update procedure for Signalling Connection Re-establishment (UMTS only) When the MS receives an indication from the lower layers that the RRC connection has been released with cause “Directed signalling connection re-establishment”. UMTS to GSM and for GSM to UMTS intersystem change.4. in UMTS.2.5.5.5.7. if the network operates in network operation mode I.7.1. This procedure is used by GPRS MSs in MS operation modes A or B.5.4 Handling of Force to standby in UMTS (UMTS only) Force to standby is not applicable for UMTS.7. This procedure is used by GPRS MSs in MS operation modes A or B that are IMSI attached for GPRS and non-GPRS services provided that the network operates in network operation mode I. or a routing area updating procedure is successfully completed.5 - Routing area updating procedure This procedure is used for: normal routing area updating to update the registration of the actual routing area of an MS in the network. resuming GPRS services when the RR sublayer indicated a resumption failure after dedicated mode was left.5. specific actions shall be performed. The network shall always indicate Force to standby not indicated in the Force to standby information element. to re-synchronize the PMM mode of MS and network after RRC connection release with cause “Directed signalling connection re-establishment”. IMSI attach for non-GPRS services when the MS is IMSI attached for GPRS services. Depending on the value of the routing area updating attempt counter.7. The routing area updating procedure is always initiated by the MS.7. The combined routing area updating procedure used to update both the routing and location area is described in section 4.7. It is only invoked in state GMM-REGISTERED. The routing area updating attempt counter shall be incremented as specified in section 4. see section 4. CR page 3 .

4. after a CM SERVICE REJECT message with cause value #4 is received by the mobile station (see section 4. user data reception shall be possible. to re-synchronize the PMM mode of MS and network after RRC connection release with cause “Directed signalling connection re-establishment”. if a new P-TMSI is assigned. In UMTS. Aborted GMM procedures may be repeated after the combined routing area updating procedure has been successfully CR page 4 . Note: The re-establishment of the radio bearers of active PDP contexts is done as described in section “Service Request procedure”. the routing and location area identification are broadcast on the broadcast channel(s).7. The ROUTING AREA UPDATE REQUEST message shall always be the first message sent from the MS in the new routing area after routing area change. if the MS is in state GMM-REGISTERED and if the network operates in network operation mode I: when a GPRS MS that is IMSI attached for GPRS and non-GPRS services detects a change of the routing area in state GMM-REGISTERED and MM-IDLE. the network shall progress the routing area update procedure as normal and release the previous PS signalling connection when the routing area update procedure has been accepted by the network. A combined routing area updating procedure shall abort any ongoing GMM procedure. ** Next Modification ** 4.5. in UMTS. GSM. Aborted GMM procedures shall be repeated after the combined routing area updating procedure has been successfully performed. expiry of timer T3302.5.5. after termination of a non-GPRS service via non-GPRS channels to update the association if the MS has changed the LA during that non-GPRS service transaction.2. In GSM.1 Combined routing area updating procedure initiation The combined routing area updating procedure is initiated only by a GPRS MS operating in MS operation modes A or B.1. The handling of these lists is described in section 4.and additionally when the MS is in substate ATTEMPTING-TO-UPDATE: a new routing area is entered.1). or at request from registration function. user data transmission in the MS shall be suspended during the routing area updating procedure. in which case the update type IE shall be set to "Combined RA/LA updating with IMSI attach". In UMTS. The mobile equipment shall contain a list of "forbidden location areas for roaming". A combined routing area updating procedure shall abort any ongoing GMM procedure. when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this UE. User data transmission in the network shall not be suspended during the routing area updating procedure. user data transmission and reception in the MS shall not be suspended during the routing area updating procedure. the routing and location area identification are broadcast on the broadcast channel(s) or sent to the MS via the PS signaling connection. or. see Section 4. when a GPRS MS that is IMSI attached for GPRS services wants to perform an IMSI attach for non-GPRS services.1. as well as a list of "forbidden location areas for regional provision of service". In UMTS.7. User data transmission in the network shall be suspended during the routing area updating procedure. In.2.

The value of the update type IE in the message shall indicate "combined RA/LA updating". starts timer T3330 and changes to state GMM-ROUTING-UPDATING-INITIATED and MM LOCATION UPDATING PENDING. A GPRS MS in MS operation modes A or B that is in an ongoing circuit-switched transaction. the value of the update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "combined RA/LA updating with IMSI attach". If for the last attempt to update the registration of the location area a MM specific procedure was performed. A GPRS MS in MS operation mode A shall initiate the combined routing area updating procedure with IMSI attach after the circuit-switched transaction has been released if a GPRS attach was performed during the circuit-switched transaction and provided that the network operates in network operation mode I. Furthermore the MS shall include the TMSI status IE if no valid TMSI is available. The ROUTING AREA UPDATE REQUEST message shall always be the first GMM message sent from the MS in the new routing area after routing area change. shall initiate the combined routing area updating procedure after the circuit-switched transaction has been released. it may set a follow-on request pending indicator on. To initiate a combined routing area updating procedure the MS sends the message ROUTING AREA UPDATE REQUEST to the network. if the MS has changed the RA during the circuit-switched transaction and if the network operates in network operation mode I. if the MS wishes to prolong the established PS signalling connection after the normal routing area updating procedure when it is served under UMTS area. A GPRS MS in MS operation mode A shall perform the normal routing area update procedure during an ongoing circuit-switched transaction. when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this UE. CR page 5 . In UMTS. In UMTS.performed. the network shall progress the routing area update procedure as normal and release the previous PS signalling connection when the routing area update procedure has been accepted by the network . Note: The re-establishment of the radio bearers of active PDP contexts is done as described in section “Service Request procedure”.

3.1. 2001 Tdoc CR-Form-v3 CHANGE REQUEST = 24. Lucent Technologies UK GPRS F = Release: = Date: 2001-01-17 R99 Use one of the following releases: Use one of the following categories: 2 (GSM Phase 2) F (essential correction) R96 (Release 1996) A (corresponds to a correction in an earlier release) R97 (Release 1997) B (Addition of feature). Therefore.0 = For HELP on using this form.3GPP TSG CN1 Meeting #15 N1-010186212 Beijing. It is acceptable for all active PDP contexts to have an associated. = (U)SIM ME/UE X Radio Access Network Core Network X = = Source: Work item code: = = Category: Title: Clarification of TFT request during secondary PDP context activation.008 CR 366 = rev 1 = Current version: 3. R98 (Release 1998) C (Functional modification of feature) R99 (Release 1999) D (Editorial modification) REL-4 (Release 4) Detailed explanations of the above categories can REL-5 (Release 5) be found in 3GPP TR 21.008 secondary PDP context activation procedure to indicate when secondary PDP contexts require TFT requests. clause 6. At most one PDP context associated with the same PDP address may exist at any time with no TFT assigned to it'. whether a secondary PDP context requests a TFT. see bottom of this page or look at the pop-up text over the Proposed change affects: = symbols. Reason for change: = Confusion could exist with regard to secondary PDP contexts requiring Traffic Flow Templates. individual TFT or for all but one PDP context to have an associated TFT.6. at activation. Summary of change: = Amend the text in 24.060 Other comments: A CR to 23. How to create CRs using this form: CR page 1 .2 X Other core specifications Test specifications O&M Specifications = = = = 23.060 will be presented at the next S2. is dependent upon whether a PDP context without a TFT already exists for the particular PDP address. 'Each PDP context may be associated with a TFT.060 states. Consequences if not approved: Clauses affected: Other specs affected: = MS may request a TFT during secondary PDP context activation procedure when not explicitly required.900. China 15-22 January. 3G TS 23.

2000-09 contains the specifications resulting from the September 2000 TSG meetings. look for the directory name with the latest date e. Below is a brief summary: 1) Fill out the above form.Comprehensive information and tips about how to create CRs can be found at: http://www.org/3G_Specs/CRs.3gpp. CR page 2 . 3) With "track changes" disabled. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes.htm. Delete those parts of the specification which are not relevant to the change request. The symbols above marked closest to.g. All 3GPP specifications can be downloaded from the 3GPP server under ftp://www.3gpp. = contain pop-up help information about the field that they are 2) Obtain the latest version for the release of the specification to which the change is proposed. paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause containing the first piece of changed text.org/specs/ For the latest version.

Release 1999 3 3GPP TS 24.5. 3GPP .3. Secondary PDP Context Activation Procedure The purpose of this procedure is to establish an additional PDP context between the MS and the network for a specific Traffic Flow Template (TFT) and QoS profile on a specific NSAPI. for the particular PDP address.1.2. a different QoS profile and TFT shall be requested. when one or more PDP contexts has/have already been established for the particular PDP address. For each of these PDP contexts.1. The MS shall include a request for a TFT if a PDP context without a TFT is presently active.008 V3.0 (2000-07) 6.3 Session Management procedures 6.

008 CR 367 = rev 1 = Current version: 4. 2001 Tdoc CR-Form-v3 CHANGE REQUEST = 24.060 Other comments: A CR to 23. is dependent upon whether a PDP context without a TFT already exists for the particular PDP address.008 secondary PDP context activation procedure to indicate when secondary PDP contexts require TFT requests.900. individual TFT or for all but one PDP context to have an associated TFT.1. At most one PDP context associated with the same PDP address may exist at any time with no TFT assigned to it'.1 = For HELP on using this form. clause 6.3. Lucent Technologies UK GPRS A F = Release: = Date: 2001-01-17 REL-4 Use one of the following releases: Use one of the following categories: 2 (GSM Phase 2) F (essential correction) R96 (Release 1996) A (corresponds to a correction in an earlier release) R97 (Release 1997) B (Addition of feature). Summary of change: = Amend the text in 24. 3G TS 23. China 15-22 January. Therefore. 'Each PDP context may be associated with a TFT.2 X Other core specifications Test specifications O&M Specifications = = = = 23. at activation. see bottom of this page or look at the pop-up text over the Proposed change affects: = symbols. R98 (Release 1998) C (Functional modification of feature) R99 (Release 1999) D (Editorial modification) REL-4 (Release 4) Detailed explanations of the above categories can REL-5 (Release 5) be found in 3GPP TR 21. Consequences if not approved: Clauses affected: Other specs affected: = MS may request a TFT during secondary PDP context activation procedure when not explicitly required.1.3GPP TSG CN1 Meeting #15 N1-010187213 Beijing.060 states. whether a secondary PDP context requests a TFT. Reason for change: = Confusion could exist with regard to secondary PDP contexts requiring Traffic Flow Templates. How to create CRs using this form: CR page 1 . = (U)SIM ME/UE X Radio Access Network Core Network X = = Source: Work item code: = = Category: Title: Clarification of TFT request during secondary PDP context activation.060 will be presented at the next S2. It is acceptable for all active PDP contexts to have an associated.

look for the directory name with the latest date e. paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause containing the first piece of changed text. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes. All 3GPP specifications can be downloaded from the 3GPP server under ftp://www.org/specs/ For the latest version.Comprehensive information and tips about how to create CRs can be found at: http://www. Below is a brief summary: 1) Fill out the above form.3gpp. 3) With "track changes" disabled.htm. The symbols above marked closest to. Delete those parts of the specification which are not relevant to the change request. 2000-09 contains the specifications resulting from the September 2000 TSG meetings.3gpp. CR page 2 .g.org/3G_Specs/CRs. = contain pop-up help information about the field that they are 2) Obtain the latest version for the release of the specification to which the change is proposed.

5. For each of these PDP contexts.0 (2000-07) 6.3 Session Management procedures 6. for the particular PDP address. a different QoS profile and TFT shall be requested.Release 1999 3 3GPP TS 24.008 V3. when one or more PDP contexts has/have already been established for the particular PDP address. Secondary PDP Context Activation Procedure The purpose of this procedure is to establish an additional PDP context between the MS and the network for a specific Traffic Flow Template (TFT) and QoS profile on a specific NSAPI.1. 3GPP .3.1. The MS shall include a request for a TFT if a PDP context without a TFT is presently active.2.

Sign up to vote on this title
UsefulNot useful