5.10 Communication Pattern parameters provisioning procedure

23.6823GPPArchitecture enhancements to facilitate communications with packet data networks and applicationsRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.10.1 Communication Pattern parameters

A set of Communication Pattern (CP) parameters is defined in the table below. All CP parameters are optional.

These CP parameters are specific for a UE or a group of UEs. Sets of these CP parameters are provided by the SCEF to the HSS which distributes them to the corresponding MME with relevant subscriber data. These CP parameter sets may be related to both PDN connection(s) and SMS transmission. The MME considers the sets of CP parameters (e.g. by merging per CP parameter if multiple sets are present), before using the parameters. Each CP parameter set shall have an associated validity time. The validity time indicates when the CP parameter set expires and shall be deleted by the HSS/MME. The validity time may be set to a value indicating that the particular CP parameter set has no expiration time. When the validity time expires, the involved nodes (SCEF, HSS, and MME) autonomously delete the associated CP parameter set with no additional signalling between the involved nodes.

NOTE 1: It is expected that the format of validity time, to be defined by Stage 3, is defined in a manner which allows SCEF, HSS and MME/SGSN to consistently and uniformly interpret the expiration of the associated CP parameters set.

Table 5.10.1-1: CP parameters

CP parameter	Description
1) Periodic communication indicator	Identifies whether the UE communicates periodically or not, e.g. only on demand. [optional]
2) Communication duration time	Duration interval time of periodic communication [optional, may be used together with 1)] Example: 5 minutes
3) Periodic time	Interval Time of periodic communication [optional, may be used together with 1)] Example: every hour
4) Scheduled communication time	Time zone and Day of the week when the UE is available for communication [optional] Example: Time: 13:00-20:00, Day: Monday
5) Stationary indication	Identifies whether the UE is stationary or mobile [optional]
6) Battery indication	Identifies power consumption criticality for the UE: if the UE is battery powered with not rechargeable/not replaceable battery, battery powered with rechargeable/replaceable battery, or not battery powered. [optional]
X) Traffic Profile	Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), multiple packets transmission. [optional]

NOTE 2: The Traffic Profile is provided to the eNB for optimisation of RAN resources and how it is used is specified in TS 23.401 [7].

5.10.2 Communication Pattern parameters provisioning to the MME

Figure 5.10.2-1: Signalling sequence for provisioning of CP Parameters

1. The SCS/AS sends an Update Request (External Identifier or MSISDN or External Group Identifier, SCS/AS Identifier, CP parameter Set Id(s), CP parameter set(s), validity time(s), CP parameter Set Id(s) for Deletion, MTC Provider Information) message to the SCEF. The CP parameter set(s) include the parameters defined in Table 5.10.1-1. A CP parameter Set Id is assigned to each CP parameter set by the SCS/AS.

NOTE 1: The SCS/AS uses this procedure to add, change or delete some or all of the CP parameter sets of the UE, e.g. if the AS is aware that the UE has started or stopped moving for a significant time period, especially if the AS is instructing the UE to do so, then the SCS/AS provides the corresponding CP parameter set(s) and its validity time(s) as well their CP parameter Set Id(s) to the SCEF. If the SCS/AS wants to perform deletion of a previously configured CP parameter set(s) together with configuring a new CP parameter set(s), then it shall include both the new CP parameter set(s), and CP parameter Set Id(s) for Deletion representing the CP parameter set(s) which requires cancellation. If the SCS/AS wants to only perform deletion of a previously configured CP parameter set(s), then it shall include CP parameter Set Id(s) for Deletion.

2. The SCEF checks if the SCS/AS is authorised to send CP requests to the UE or to each UE in the identified group. The SCEF filters and the selects the CP parameter set(s) for add/modify/delete based on operator policy or configuration. The SCEF does not check for potential overlapping of CP parameters if there are multiple CP parameter set(s) for the UE, but this is handled in the MME.

In this release, to avoid receiving CP parameter sets from multiple SCEFs that might be overlapping, the HSS shall accept CP parameter sets from only a single SCEF for a given UE.

3. The SCEF sends Update CP Parameter Request (External Identifier or MSISDN or External Group Identifier, SCEF Reference ID(s), SCEF Address, CP parameter set(s), validity time(s), SCEF Reference ID(s) for Deletion, MTC Provider Information) message to the HSS for delivering the selected CP parameter set(s) per UE. There may be multiple CP parameter sets included in this message where each CP parameter set for addition or modification has been determined to be non-overlapping with other CP parameter sets either included in the message or already provisioned for a given UE. The SCEF derives the SCEF Reference ID(s) for CP parameter sets to be sent to the HSS based on the CP parameter Set Id(s) from the SCS/AS.

NOTE 2: A request for deletion of a CP parameter set from the SCS/AS may result in a request for modification of the non-overlapping CP parameter set by the SCEF.

NOTE 3: The MTC Provider Information in step 1 is an optional parameter. The SCEF should validate the provided MTC Provider Information and may override it to an SCEF selected MTC Provider Information based on configuration. How the SCEF determines the MTC Provider Information, if not present in step 1, is left to implementation (e.g. based on the requesting SCS/AS)

4. The HSS examines the Update CP Parameter Request message, e.g. with regard to the existence of External Identifier or MSISSN or External Group Identifier. If the check fails, the HSS immediately sends a response message back to the SCEF following step 5. The HSS resolves the External Identifier or MSISDN to an IMSI or resolves the External Group Identifier to an IMSI-Group Identifier and stores the CP parameter set(s) and their validity time(s) as part of UE subscription data identified by the IMSI or IMSI-Group Identifier, so that the CP parameter set(s) can be forwarded to the serving MME(s) when the serving MME(s) are changed due to the mobility of the UE.

The HSS determines that a stored CP parameters set is to be modified by the fact that the SCEF Reference ID associated with the CP parameters set matches an SCEF Reference ID for a CP parameters set already stored for a given UE. If the HSS determines that an existing CP parameter set is to be modified, the HSS discards the already stored CP parameter set and stores the new CP parameter set and validity time under the same SCEF Reference ID.

The HSS stores a new CP parameter set along with the associated SCEF Reference ID and validity time.

If CP parameters sets are to be deleted, the HSS removes the CP parameters sets from the subscription.

If the validity time for a CP parameter set stored in the HSS expires, the HSS autonomously deletes the associated CP parameter set with no additional signalling.

NOTE 3: The CP parameter set(s) are not provided to the SGSN.

NOTE 4: The HSS does not need to validate the content of the stored CP parameters set(s).

5. The HSS sends Update CP Parameter Response (SCEF Reference ID, Cause) message to the SCEF. The cause value indicates successful subscription update or the reason of failed subscription update.

6. The SCEF sends the Update Response (CP parameter Set Id(s), Cause(s)) message to inform the SCS/AS whether the provision of the CP parameter set(s) was successful.

7. The HSS initiates an Insert Subscription Data procedure for each UE to send the CP parameter set(s) with the corresponding validity time(s), SCEF Reference ID(s), and SCEF Reference ID(s) for Deletion to the MME. Optionally, the HSS allocates a Provider-Group-ID (different from the IMSI-Group-Id) based on the MTC Provider Information and sends it to the MME to assist the serving node(s) when selecting and differentiating configurations for a given MTC Service Provider (e.g. to delete the CP Set Id(s) for a specific MTC Service Provider at the MME).

The MME determines that a stored CP parameters set is to be modified by the fact that the SCEF Reference ID associated with the CP parameters set matches an SCEF Reference ID for a CP parameters set already stored for the UE. If the MME determines that an existing CP parameter set is to be modified, the MME discards the already stored CP parameter set and stores the received CP parameter set with the associated validity time in the UE’s (E)MM context under the same SCEF Reference ID.

The MME stores a new CP parameter set along with the associated SCEF Reference ID and validity time. The MME may use the CP parameter set(s) as described in TS 23.401 [7].

If CP parameter sets are to be deleted, the MME removes the CP parameter sets from the subscription.

If the validity time for a CP parameter set stored in the MME expires, the MME autonomously deletes the associated CP parameter set with no additional signalling.