Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.116  Word version:  18.0.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 5

The present document specifies the stage 2 description of the Super-Charger that provides a mechanism to reduce the signalling traffic associated with mobility.

2  Referencesp. 5

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 21.905: "3G Vocabulary".
[2]
TR 23.912: "Technical Report on Super-Charger".
[3]
TS 23.007: "Restoration Procedures".
[4]
TS 23.008: "Organisation of Subscriber Data".
[5]
TS 23.012: "Location Management Procedures".
[6]
TS 23.016: "Subscriber Data Management: Stage 2".
[7]
TS 23.040: "Technical Realisation of the Short Message Service (SMS); Point-To-Point (PP)".
[8]
TS 23.060: "General Packet Radio Service; Stage 2".
[9]
TS 29.002: "Mobile Application Part (MAP)".
[10]
TS 23.018: "Basic call handling; Technical realization".
Up

3  Definitions and abbreviationsp. 5

3.1  Definitionsp. 5

For the purposes of the present document the following terms and definitions apply.
Procedure Calls to stage 2.
Super-Charged Network:
UMTS network in which the Super-Charger mechanism is being used to optimise mobility management signalling
Network Entity:
either an MSC/VLR, SGSN or UMSC
Serving Network Entity:
network entity to which the mobile station is attached
Previous Network Entity:
network entity to which the mobile station was attached prior to the serving network entity

3.2  Abbreviationsp. 5

Abbreviations used in the present document are listed in GSM 01.04.

4  Information flowsp. 6

In a Super-Charged network subscription data is retained by the previous network entity when the subscriber roams to a new network entity.
When a subscriber performs location updating in a Super-Charged network the HLR shall only cancel the subscription information at the previous network entity if it does not support the Super-Charger functionality except in the conditions described in clause 5.2.3.0. If the network entity to which the subscriber has roamed has retained subscription data from a previous visit then the HLR shall only send subscription data to the network entity if the retained subscription data is not consistent with the data stored by the HLR. If the HLR does not send subscription data to the serving network entity it shall treat the retained subscription data as valid.
Up

4.1  Location Updating in a Super-Charged Networkp. 6

4.1.1  CS-domain Location Updating in a serving network entity that does not have subscription datap. 6

When a Super-Charged network entity receives a request to perform a location update for a subscriber for whom there is no record, the network entity shall initiate the location updating procedures as described in TS 23.012.
The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality:
  • if the previous network entity does not support the Super-Charger functionality then the HLR shall respond to the location updating request as described in TS 23.012;
  • if the previous network entity supports the Super-Charger functionality then the HLR shall respond to the location updating request as described in TS 23.012 but shall not cancel the location information at the previous network entity except in the conditions described in clause 5.2.3.0.
Copy of original 3GPP image for 3GPP TS 23.116, Fig. 1: Information flow for an inter-node location update in a Super-Charged network for the case when the serving network entity does not have subscription data for the requesting mobile station
Up

4.1.2  CS-domain Location Updating in a network entity that has retained subscription datap. 7

When a Super-Charged network entity receives a request to perform a location update for a subscriber for whom subscription data has been retained, the network entity shall initiate the location updating procedures as described in TS 23.012.
The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality:
  • if the previous network entity does not support the Super-Charger functionality then the HLR shall cancel the location information at the previous network entity as described in TS 23.012.
  • if the previous network entity supports the Super-Charger functionality then the HLR shall not cancel the location information at the previous network entity except in the conditions described in clause 5.2.3.0.
The Super-Charged HLR shall determine whether the subscription data retained by the serving network entity is consistent with the subscription data stored in the HLR:
  • if the subscription data is consistent then the HLR shall not send subscription data to the serving network entity as part of the location updating;
  • if the subscription data is not consistent then the HLR shall respond to the location updating request as described in TS 23.012.
Copy of original 3GPP image for 3GPP TS 23.116, Fig. 2: Information flow for an inter-node location update in a Super-Charged network for the case when the serving network entity has retained subscription data for the requesting mobile station
Up

4.1.3  PS-domain Location Updating in a network entity that does not have subscription datap. 8

When a Super-Charged network entity receives a request to perform a routeing area update or attach for a subscriber for whom there is no record, the network entity shall initiate the location updating procedures as described in TS 23.012.
The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality:
  • if the previous network entity does not support the Super-Charger functionality then the HLR shall respond to the location updating request as described in TS 23.012;
  • if the previous network entity supports the Super-Charger functionality then the HLR shall respond to the location updating request as described in TS 23.012 but shall not cancel the location information at the previous network entity.
Copy of original 3GPP image for 3GPP TS 23.116, Fig. 3: Information flow for an inter-node routeing area update or attach in a Super-Charged network for the case when the serving network entity does not have subscription data for the requesting mobile station
Up

4.1.4  PS-domain Location Updating in a network entity that has retained subscription datap. 9

When a Super-Charged network entity receives a request to perform a routeing area update or attach for a subscriber for whom subscription data has been retained, the network entity shall initiate the location updating procedures as described in TS 23.012.
The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality:
  • if the previous network entity does not support the Super-Charger functionality then the HLR shall cancel the location information as described in TS 23.012;
  • if the previous network entity supports the Super-Charger functionality then the HLR shall not cancel the location information.
The Super-Charged HLR shall determine whether the subscription data retained by the serving network entity is consistent with the subscription data stored in the HLR:
  • if the subscription data is consistent then the HLR shall not send subscription data to the serving network entity as part of the location updating procedures;
  • if the subscription data is not consistent then the HLR shall respond to the location updating request as described in TS 23.012.
Copy of original 3GPP image for 3GPP TS 23.116, Fig. 4: Information flow for an inter-node routeing area update or attach in a Super-Charged network for the case when the serving network entity has retained subscription data for the requesting mobile station
Up
Up

Up   Top   ToC