Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.128  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.7…   6…   6.2.2.2A…   6.2.3…   6.2.3.2.7…   6.2.3.3…   6.2.4…   6.3…   6.3.2.2A…   6.3.3…   6.3.3.2…   6.3.3.2.4…   6.3.3.2A…   7…   7.3…   7.3.3…   7.3.3.2.21…   7.3.3.2.42…   7.3.3.2.63…   7.3.4…   7.4…   7.4.3.8…   7.5…   7.6…   7.7…   7.7.4…   7.8…   7.8.4…   7.9…   7.10…   7.10.4…   7.11…   7.12…   7.13…   7.13.3…   7.13.3.4…   7.14…   7.15…   8…   A…   D…   E…   M…

 

7.8.4  LI for MSISDN-less MO SMSp. 269

7.8.4.1  Generation of xIRI LI_X2 at IRI-POI in SCEF over LI_X2p. 269

7.8.4.1.1  Generalp. 269
The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in clause 7.11.4.4 of TS 33.127, the details of which are described in the following clauses.
7.8.4.1.2  MSISDN-less MO SMSp. 269
The IRI-POI in the SCEF shall generate an xIRI containing a SCEFMSISDNLessMOSMS record when the IRI-POI present in the SCEF detects that a target UE has sent a MSISDN-less MO SMS to an SCS/AS.
Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected:
  • SCEF receives a SGd MO-Forward-Short-Message-Request (OFR) from an SM-SC with IMSI matching the target identifier (see clause 6.2.1 of TS 29.338).
  • SCEF sends a MsisdnLessMoSmsNotification to the SCS/AS with the External Identifier of the UE sending the MSISDN-less SMS (see clause 5.15 of TS 29.122).
Field name Value M/C/O
iMSIIMSI associated with the target UEC
externalIdentifierExternal Identifier in the form of username@realm and corresponding to the identity of the originating SMS partyC
terminatingSMSPartyIdentity of the SCS/AS receiving the SMSM
sMSSMS TPDUC
sourcePortport identifying the application of the target UE sending the MSISN-less MO SMSC
destinationPortport identifying the application of the SCS/AS which is the recipient of the MSISN-less MO SMSC
Up

7.8.4.2  Generation of IRI over LI_HI2p. 269

When an xIRI is received over LI_X2 from the IRI-POI in the SCEF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the SCEF event was observed (i.e. the timestamp field of the xIRI).
The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to Table 7.8.4-2.
IRI message Record type
SCEFMSISDNLessMOSMSREPORT
Up

7.8.5  LI for parameter provisioningp. 270

7.8.5.1  Generation of xIRI LI_X2 at IRI-POI in SCEF over LI_X2p. 270

7.8.5.1.1  Generalp. 270
The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in corresponding in clause 7.11.5.4 of TS 33.127, the details of which are described in the following clauses.
7.8.5.1.2  Communication pattern updatep. 270
The IRI-POI in the SCEF shall generate an xIRI containing an SCEFCommunicationPatternUpdate record when the IRI-POI present in the SCEF detects that an SCS/AS has updated the Communication pattern data.
Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected (See clause 5.10 of TS 29.122):
  • SCEF receives a request to provision the communication pattern parameters from an SCS/AS related to the target UE (PUT).
  • SCEF receives a request to delete the existing communication patterns parameters from an SCS/AS related to the target UE (DELETE).
  • SCEF returns a response (200 OK) containing the communication pattern parameters of the target UE to the querying SCS/AS (GET).
Field name Value M/C/O
mSISDNMSISDN of the target UE the communication pattern applies toC
externalIdentifierExternal Identifier of the target UE the communication pattern applies toC
periodicCommunicationIndicatorIdentifies whether UE communicates periodically or on demandO
communicationDurationTimeIndicates for how long the UE will normally stay in CM-Connected for data transmission expressed in secondsO
periodicTimeInterval Time of periodic communication in secondsO
scheduledCommunication TimeTime and day of the week when the UE is available for communication, as defined in TS 29.571O
scheduledCommunicationTypeIndicates that the Scheduled Communication Type is Downlink only or Uplink only or Bi-directionalO
stationaryIndicationIdentifies whether the UE is stationary or mobileO
batteryIndicationIdentifies power consumption criticality for the UE: if the UE is battery powered but the battery is not rechargeable/not replaceable, battery powered with rechargeable/replaceable battery, or not battery powered.O
trafficProfileIdentifies 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 transmissionO
expectedUEMovingTrajectoryIdentifies the UE's expected geographical movementO
expectedTimeAndDayOfWeekInTrajectoryIdentifies the time and day of week when the UE is expected to be at each location included in the Expected UE Moving TrajectoryO
sCSASIDSCS/AS identity requesting communication pattern updateM
validityTimeIdentifies when the expected UE behavior parameter set expires and shall be deleted. If absent, it indicates that there is no expiration time for this parameter setO
Up

7.8.5.2  Generation of IRI over LI_HI2p. 271

When an xIRI is received over LI_X2 from the IRI-POI in the SCEF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the SCEF event was observed (i.e. the timestamp field of the xIRI).
The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to Table 7.8.5-2.
IRI message Record type
SCEFCommunicationPatternUpdateREPORT
Up

7.8.6  LI for AS session with QoSp. 271

7.8.6.1  Generation of xIRI at IRI-POI in SCEF over LI_X2p. 271

7.8.6.1.1  Generalp. 271
The IRI-POI present in the SCEF shall send the xIRIs over LI_X2 for each of the events listed in clause 7.11.6.4 of TS 33.127, the details of which are described in the following clauses.
7.8.6.1.2  AS session with QoS provisionp. 271
The IRI-POI in the SCEF shall generate an xIRI containing a SCEFASSessionWithQoSProvision record when the IRI-POI present in the SCEF detects that an SCS/AS has requested the SCEF to provide, update or revoke a specific QoS for an AS session.
Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected (see clauses 5.14 of TS 29.122):
  • SCEF returns an On-demand QoS Response in response to On-demand QoS Request received from an SCS/AS to create (POST)/update (PUT or PATCH)/revoke (DELETE) a specific QoS for an AS session related to a target UE.
Field name Value M/C/O
mSISDNMSISDN of the target UE the AS session with required QoS applies to, if available (see NOTE).C
externalIdentifierExternal Identifier of the target UE the AS session with required QoS applies to, if available (see NOTE).C
sCSASIDSCS/AS identity requesting AS session with required QoS..M
aSSessionWithQoSOpTypeType of operation for AS session with required QoS : POST to provision, PUT and PATCH to update and DELETE to revoke.M
aSSessionWithQoSSubscription Includes an ASSessionWithQoSSubscription resource according to clause A.14 of TS 29.122. The SBIReference for this parameter shall be populated with 'TS29122_AsSessionWithQoS.yaml#/­components/­­schemas/­AsSessionWithQoSSubscription'. Present only if the aSSessionWithQoSOpType is set to "POST" or "PUT". C
aSSessionWithQoSSubscriptionPatch Includes a ASSessionWithQoSSubscriptionPatch resource according to clause A.14 of TS 29.122. The SBIReference for this parameter shall be populated with 'TS29122_AsSessionWithQoS.yaml#/­­­components/­­schemas/­AsSessionWithQoSSubscriptionPatch'. Present only if the aSSessionWithQoSOpType is set to "PATCH". C
aSSessionWithQoSResponseCodeIdentifies the response code associated to the ASSessionWithQoS operation executed by the SCEF.M
NOTE:
At least one of the MSISDN or External Identifier fields shall be present.
Up
7.8.6.1.3  AS session with QoS notificationp. 272
The IRI-POI in the SCEF shall generate an xIRI containing a SCEFASSessionWithQoSNotification record when the IRI-POI present in the SCEF detects that the SCEF has notified the SCS/AS about changes in the transmission resource status of the AS session.
Accordingly, the IRI-POI in the SCEF generates the xIRI when any of the following events is detected (see clauses 5.14 of TS 29.122):
  • SCEF receives a Status information Response in response to Status information Request (POST) sent to SCS/AS to notify changes in the transmission resource status of an AS session associated with the target UE.
Field name Value M/C/O
mSISDNMSISDN of the target UE the AS session with required QoS applies to, if available (see NOTE).C
externalIdentifierExternal Identifier of the target UE the AS session with required QoS applies to, if available (see NOTE).C
userPlaneNotificationData Includes a userPlaneNotificationData resource according to clause A.14 of TS 29.122. The SBIReference for this parameter shall be populated with 'TS29122_AsSessionWithQoS.yaml#/components/schemas/ UserPlaneNotificationData'. M
aSSessionWithQoSResponseCodeIdentifies the response code returned by SCS/AS associated to the ASSessionWithQoS notification sent by SCEF to SCS/AS.M
NOTE:
At least one of the MSISDN or External Identifier fields shall be present.
Up

7.8.6.2  Generation of IRI over LI_HI2p. 272

When an xIRI is received over LI_X2 from the IRI-POI in the SCEF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the SCEF event was observed (i.e. the timestamp field of the xIRI).
The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to Table 7.8.6.2-1.
IRI message Record type
SCEFASSessionWithQoSProvisionREPORT
SCEFASSessionWithQoSNotificationREPORT
Up

Up   Top   ToC