Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.078  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4.2…   4.3…   4.4…   4.5…   4.5.2…   4.5.3…   4.5.4…   4.5.5…   4.5.6…   4.5.7…   4.5.8…   4.6…   4.6.2…   4.6.3…   4.6.7…   4.6.13…   5…   6…   6.5…   6.6…   7…   7.5…   8…   9…   10…   11…   12…   A… 
9 Mobility Management  9.1 Architecture  9.2 Description of CAMEL Subscriber Data  9.3 Procedures for Mobility management  9.4 Description of information flows  9.4.1 VLR or SGSN to gsmSCF information flows  9.4.2 SGSN to HLR information flows  9.4.3 VLR to HLR information flows  9.4.4 HLR to VLR or SGSN information flows 
...

 

9  Mobility Management  p. 670

9.1  Architecture  p. 670

9.1.1  Functional Entities used for CAMEL  p. 670

This subclause describes the functional architecture required to support Mobility Management in CAMEL. Figure 9.1-1 and Figure 9.1-2 show the functional entities involved in CAMEL support of Mobility Management. The architecture in the Figure 9.1-1 is applicable to the third phase of CAMEL or higher and the architecture in the Figure 9.1-2 is applicable to the fourth phase of CAMEL.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.1-1: Functional architecture for CS subscriber support of CAMEL
Figure 9.1-1: Functional architecture for CS subscriber support of CAMEL
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.1-2: Functional architecture for GPRS subscriber support of CAMEL
Figure 9.1-2: Functional architecture for GPRS subscriber support of CAMEL
(⇒ copy of original 3GPP image)
Up
gsmSCF:
see subclause 3.1.
HLR:
The HLR contains Mobility management CAMEL Subscription Information (M-CSI) for those CS subscribers that require CAMEL control of Mobility Management events and Mobility management GPRS CAMEL Subscription Information (MG-CSI) for those GPRS subscribers that require CAMEL control of Mobility Management events. M-CSI is sent to the VLR during the Location Update and Restore Data procedures or when M-CSI is modified in the HLR. The M-CSI is deleted in the VLR with the Delete Subscriber Data procedure. MG-CSI is sent to the SGSN during the GPRS Location Updating procedure or when MG-CSI is modified in the HLR. The MG-CSI is deleted in the SGSN with the Delete Subscriber Data procedure.
MS:
Mobile Station.
MSC:
see subclause 4.1.
VLR:
After having completed a Mobility Management event from a CS subscriber, the VLR may find it necessary to send a notification to the gsmSCF. The content of M-CSI indicates which Mobility Management events shall be reported to the gsmSCF.
SGSN:
After having completed a Mobility Management event from a GPRS subscriber, the SGSN may find it necessary to send a notification to the gsmSCF. The content of MG-CSI indicates which Mobility Management events shall be reported to the gsmSCF.
Up

9.1.2  Interfaces defined for CAMEL  p. 671

This subclause describes the different interfaces applicable to CAMEL control of Mobility Management events. It specifies on a high level the functions specific to CAMEL.

9.1.2.2  VLR - gsmSCF interface  p. 671

This interface is used by the VLR to send Mobility Management event notifications to the gsmSCF. When processing a mobility management event, the VLR may find it necessary to send a notification to the gsmSCF, depending on the presence of M-CSI for the subscriber and the contents of M-CSI.

9.1.2.3  SGSN - gsmSCF interface |R5|  p. 671

This interface is used by the SGSN to send Mobility Management event notifications to the gsmSCF. When processing a mobility management event, the SGSN may find it necessary to send a notification to the gsmSCF, depending on the presence of MG-CSI for the subscriber and the contents of MG-CSI.

9.2  Description of CAMEL Subscriber Data  p. 671

9.2.1  Mobility Management CAMEL Subscription Information (M-CSI)  p. 671

This subclause specifies the contents of the Mobility Management CAMEL Subscription Information (M-CSI).

9.2.1.1  Mobility Management Triggers  p. 671

This data indicates which Mobility Management events shall result in a notification to the gsmSCF. One or more events may be marked per subscriber. These events are:
  • Location update in the same VLR service area.
  • Location update to another VLR service area.
  • IMSI attach.
  • MS initiated IMSI detach (explicit detach).
  • Network initiated IMSI detach (implicit detach).

9.2.1.2  gsmSCF address  p. 671

This is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.

9.2.1.3  Service Key  p. 671

The Service Key is included in the notification information flow to the gsmSCF. It indicates to the gsmSCF which Service Logic shall be applied.

9.2.1.4  CSI state  p. 672

The CSI state indicates whether the M-CSI is active or not.

9.2.1.5  Notification flag  p. 672

The notification flag indicates whether the change of the M-CSI shall trigger Notification on Change of Subscriber Data or not.

9.2.2  Mobility Management for GPRS CAMEL Subscription Information (MG-CSI) |R5|  p. 672

This subclause specifies the contents of the Mobility Management for GPRS CAMEL Subscription Information (MG-CSI).

9.2.2.1  Mobility Management Triggers  p. 672

This data indicates which Mobility Management events shall result in a notification to the gsmSCF. One or more events may be marked per subscriber. These events are:
  • Routeing area update of MS to a different SGSN service area (update from mew SGSN);
  • Routeing area update of MS to a different SGSN service area (disconnect by detach);
  • Routeing area update of MS within the same SGSN service area;
  • GPRS attach (e.g. MS switched on, successful routeing area update after network initiated transfer to "MS not reachable for paging");
  • MS-initiated GPRS detach (e.g. MS switched off);
  • Network-initiated GPRS detach.
  • Network-initiated transfer to the "not reachable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreachable).
Up

9.2.2.2  gsmSCF address  p. 672

This is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.

9.2.2.3  Service Key  p. 672

The Service Key is included in the notification information flow to the gsmSCF. It indicates to the gsmSCF which Service Logic shall be applied.

9.2.2.4  CSI state  p. 672

The CSI state indicates whether the MG-CSI is active or not.

9.2.2.5  Notification flag  p. 672

The notification flag indicates whether the change of the MG-CSI shall trigger Notification on Change of Subscriber Data or not.

9.2.3  gsmSCF address list for CSI |R5|  p. 672

The gsmSCF address list indicates the gsmSCF addresses to which Notification on Change of Subscriber Data shall be sent. This list is common to all CSI.

9.3  Procedures for Mobility management  p. 673

9.3.1  Procedures for Mobility management for CS subscriber  p. 673

The different procedures for Mobility Management are shown in Figures 9.2-1 to 9.2-5.
Figure 9.2-1: Location Update within a single VLR Service Area. (The VLR Service area may be in the HPLMN or in the VPLMN.);
Figure 9.2-2: Location Update from one VLR Service Area to another VLR Service Area. (Both VLR Service Areas are in the HPLMN or in the same VPLMN.);
Figure 9.2-3: Location Update from one PLMN to another PLMN;
  • update from HPLMN to VPLMN;
  • update from VPLMN to HPLMN;
  • update from one VPLMN to another VPLMN.
Figure 9.2-4: IMSI Detach (in HPLMN or in VPLMN);
  • explicit detach (the MS has been switched off by the subscriber);
  • implicit detach (the network has not received a periodic paging update from the MS and assumes that the MS is switched off or unreachable).
Figure 9.2-5: IMSI Attach (in HPLMN or in VPLMN);
  • attach (the MS has been switched on by the subscriber - subscription data is still available in the VLR, no location update is needed).
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.2-1: Location Update within a single VLR Service Area
Figure 9.2-1: Location Update within a single VLR Service Area
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.2-2: Location Update from one VLR Service Area to another VLR Service Area
Figure 9.2-2: Location Update from one VLR Service Area to another VLR Service Area
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.2-3: Location Update from one PLMN to another PLMN
Figure 9.2-3: Location Update from one PLMN to another PLMN
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.2-4: IMSI Detach (implicit/explicit)
Figure 9.2-4: IMSI Detach (implicit/explicit)
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.2-5: IMSI Attach
Figure 9.2-5: IMSI Attach
(⇒ copy of original 3GPP image)
Up
When a Mobility Management Event has taken place and the processing has been completed, then the VLR may find it necessary to send a notification to the gsmSCF. The processing of the Mobility Management event in the VLR is not suspended by the sending of the notification nor is it in any way affected by the notification.
The sending of a Mobility Management notification to gsmSCF is independent of other CAMEL subscription data for a subscriber. E.g. a subscriber may have M-CSI without O-CSI or VT-CSI.
The sending of a Mobility Management event notification is subscription based.
Refer to subclause 9.2.1 for a description of M-CSI and the different Mobility Management events that may lead to a notification to the gsmSCF.
Up

9.3.1.1  Procedure descriptions  p. 675

9.3.1.1.1  Procedure Set_Notification_Type |R5|  p. 675
This procedure is called from process Update_Location_VLR in TS 23.012. It checks the information element 'Location Update Type', which the VLR receives from the MSC via MAP_UPDATE_LOCATION_AREA service. This element identifies the type of Location Update requested by the mobile station.
The possible values of this parameter are specified in TS 24.008.
The type of Location Update that was requested by the mobile station determines which Mobility Management notification information flow shall be sent to the gsmSCF.
The values 'Periodic Updating' and 'Reserved' shall not lead to a Mobility Management notification to the gsmSCF.
(not reproduced yet)
Figure 9.3-1a: Procedure Set_Notification_Type (sheet 1)
Up
9.3.1.1.2  Procedure Notify_gsmSCF |R5|  p. 677
This procedure is called from the process 'Update_Location_Area_VLR' and process 'Detach_IMSI_VLR' in TS 23.012. It is also called from the process 'Update_Location_VLR' in TS 29.002.
The calling process passes on the variable 'Notify' to the procedure 'Notify_gsmSCF'. This variable indicates which Mobility Management notification may be necessary to be sent to the gsmSCF. If this variable has a value NULL, then no notification shall be sent to the gsmSCF.
If a notification may be necessary to be sent to the gsmSCF, then the procedure checks the presence of M-CSI.
  • If M-CSI is present and the Mobility Management event indicated in the variable 'Notify' is marked in M-CSI, then a notification shall be sent to the gsmSCF.
  • If M-CSI is not present or the Mobility Management event indicated in the variable 'Notify' is not marked in M-CSI, then no notification shall be sent to the gsmSCF.
(not reproduced yet)
Figure 9.3-1: Procedure Notify_gsmSCF (sheet 1)
Up

9.3.2  Procedures for Mobility management for GPRS subscriber |R5|  p. 679

The different procedures for Mobility Management are shown in Figures 9.4-1 to 9.4-5.
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.4-1: Routeing Area Update within SGSN Service Area
Figure 9.4-1: Routeing Area Update within SGSN Service Area
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.4-2: Routeing Area Update from one SGSN Service Area to another SGSN Service Area
Figure 9.4-2: Routeing Area Update from one SGSN Service Area to another SGSN Service Area
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.4-3: Routeing Area Update from one PLMN to another PLMN
Figure 9.4-3: Routeing Area Update from one PLMN to another PLMN
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.4-4: Attach of MS
Figure 9.4-4: Attach of MS
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.078, Fig. 9.4-5: GPRS detach
Figure 9.4-5: GPRS detach
(⇒ copy of original 3GPP image)
Up
When a Mobility Management Event has taken place and the processing has been completed, then the SGSN may have to send a notification to the gsmSCF.
The sending of a Mobility Management notification to gsmSCF is independent of other CAMEL subscription data for a subscriber. E.g. a subscriber may have MG-CSI without GPRS-CSI.
The sending of a Mobility Management event notification is subscription based.
Refer to subclause 9.2.2 for a description of MG-CSI and the different Mobility Management events that may lead to a notification to the gsmSCF.
Up

9.3.2.1  Procedure CAMEL_PS_Notification  p. 680

This procedure is called from processes in TS 23.060. When this procedure is called, it checks the presence of MG-CSI. If there is no MG-CSI, then no notification is sent to the gsmSCF.
(not reproduced yet)
Figure 9.5-1: Procedure CAMEL_PS_Notification (sheet 1)
Up
(not reproduced yet)
Figure 9.6-1: Procedure Set_PS_Notification_Type (sheet 1)
Up
(not reproduced yet)
Figure 9.7-1: Procedure Notify_PS_gsmSCF (sheet 1)
Up

9.4  Description of information flows  p. 684

This subclause contains the detailed description of the information flows used by CAMEL for Mobility Management control.
Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Specific conditions (S), mutually Exclusive (E), Optional (O) or not applicable (-) for each different entity involved: VLR (VLR) and SGSN (SGSN) where distinction is applicable. If the IEs in one Table apply in both VLR and SGSN, then the IEs are marked in the "Status" column.
An 'M' IE shall always be included. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. When a set of 'E' IEs is shown in the definition of an Information Flow or compound IE, only one of those IEs may be included. An 'O' IE may be included or omitted as required by the service logic. A '-' IE shall always be omitted. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol.
The following principles apply for the handling of the IEs by the receiving entity:
  • The gsmSCF may silently discard any IE which it does not functionally support;
  • The VLR shall functionally support all IEs which can be sent to it;
  • The SGSN shall functionally support all IEs which can be sent to it.
Up

9.4.1  VLR or SGSN to gsmSCF information flows  p. 684

9.4.1.1  Mobility Management event Notification  p. 684

9.4.1.1.1  Description  p. 684
This IF is generated by the VLR or SGSN to notify the gsmSCF of a Mobility Management event.
9.4.1.1.2  Information Elements  p. 684
Information element name VLR SGSN Description
Event MetMMThis IE indicates the type of Mobility Management event that lead to the notification. Refer to subclause 9.2.1.1 for the CS subscriber and subclause 9.2.2.1 for the GPRS subscriber.
Service KeyMMThis IE indicates the Service Logic that the gsmSCF shall apply.
IMSIMMThis IE identifies the mobile subscriber to whom the Mobility Event applies.
Basic MSISDNMMThis IE identifies the mobile subscriber to whom the Mobility Event applies.
Location Information for CS subscriberC-This IE is described in a Table below.
This IE indicates the current location of the MS.
Location Information for GPRS subscriber-CThis IE indicates the current location of the MS which is equivalent to the location info SGSN IE in subclause 7.6.1.2.
Supported CAMEL PhasesMMThis IE indicates the CAMEL Phases that are supported by the sending entity (VMSC/VLR or SGSN) in which the MS is registered after the mobility management event.
Offered CAMEL4 FunctionalitiesM-This IE is described in subclause 4.6.1.8.
It indicates the CAMEL phase 4 functionalities offered by the VMSC/VLR.
Location Information for CS subscriber is defined in TS 23.018. The following differences apply:
Information element name Status Description
Service area IDC,ESee TS 23.018.
Cell IDC,ESee TS 23.018.
VLR NumberMSee TS 23.018.
Current Location Retrieved-Not applicable
Location area IDC,ESee TS 23.003.
Selected LSA IdentitySThis IE indicates the LSA identity associated with the current position of the MS. It shall be present if the LSA ID in the subscriber data matches the LSA ID of the current cell. In the case of multiple matches the LSA ID with the highest priority it shall be present. See TS 43.073.
User CSG InformationCSee TS 23.060.
E-UTRAN Cell IDC,ESee TS 23.018.
Tracking area IDC,ESee TS 23.018.
Up

9.4.2  SGSN to HLR information flows  p. 685

9.4.2.1  Update GPRS Location  p. 685

See subclause 6.6.4.2.

9.4.3  VLR to HLR information flows |R5|  p. 685

9.4.3.1  Update Location  p. 685

See subclause 4.6.8.3.

9.4.3.2  Restore Data  p. 685

See subclause 4.6.8.4.

9.4.4  HLR to VLR or SGSN information flows |R5|  p. 685

9.4.4.1  Delete Subscriber Data  p. 685

9.4.4.1.1  Description  p. 685
This IF is used by an HLR to delete CAMEL subscription data from a VLR or SGSN. It is specified in TS 29.002.
9.4.4.1.2  Information Elements  p. 685
The Delete Subscriber Data IF contains the following CAMEL specific information elements for Mobility Management:
Information element name VLR SGSN Description
CAMEL Subscription Info WithdrawOOThis IE identifies that all CSIs shall be deleted from the subscriber data in VLR or SGSN.
Specific CSI WithdrawOOThis IE is used to indicate that only M-CSI or MG-CSI shall be deleted from the VLR or SGSN respectively. It should not be present when CAMEL Subscription Info Withdraw is present.
Up

9.4.4.2  Insert Subscriber Data  p. 686

9.4.4.2.1  Description  p. 686
This IF is used by an HLR to update a VLR or SGSN with certain subscriber data. This IF is specified in TS 29.002.
9.4.4.2.2  Information Elements  p. 686
Insert Subscriber Data contains the following CAMEL specific information elements for Mobility Management:
Information element name VLR SGSN Description
M-CSIO-This IE identifies the CS subscriber as having mobility management notification services. It contains the events that shall be reported, the gsmSCF Address and the Service Key.
MG-CSI-OThis IE identifies the GPRS subscriber as having mobility management notification services. It contains the events that shall be reported, the gsmSCF Address and the Service Key.
M-CSI contains the following information elements:
Information element name Status Description
GsmSCF AddressMThis IE is described in subclause 9.2.1.
Service KeyMThis IE is described in subclause 9.2.1.
Mobility Management TriggersMThis IE indicates which Mobility Management events shall be reported to the gsmSCF. It shall contain one or more of the following elements:
  • Location update in the same VLR service area
  • Location update to another VLR service area
  • IMSI attach
  • MS initiated IMSI detach (explicit detach)
  • Network initiated IMSI detach (implicit detach)
MG-CSI contains the following information elements:
Information element name Status Description
GsmSCF AddressMThis IE is described in subclause 9.2.2.
Service KeyMThis IE is described in subclause 9.2.2.
Mobility Management TriggersMThis IE is described in subclause 9.2.2.
Up

Up   Top   ToC