1. MinitorEvent(UE_Reachability)
Group Name: ARC
Source: Echo, Huawei, Yulan Lu, China Telecom, Shuling Wang,China
Meeting Date:
Agenda Item: 3GPP interworking

2. 3GPP Power Saving Mode
Power Savings Mode allows a UE to move in and out of a deep sleep state.
When the UE is in the “deep sleep” state, it does not listen to the paging channel.
The UE periodically leaves the “deep sleep” state, enters a connected mode, and then enters an “active time” where it listens to the paging channel.
How long the UE stays in connected mode depends on if it has MO data to send.
From TS : “A UE in PSM is not immediately reachable for mobile terminating services. A UE using PSM is available for mobile terminating services during the time it is in connected mode and for the period of an Active Time that is after the connected mode. The connected mode is caused by a mobile originated event like data transfer or signalling, e.g. after a periodic TAU/RAU procedure.”
Note: If the UE has data to send, it is free to leave the power savings mode at any time. It’s active timer will re-start when it is done sending data.
Active Time
Power Saving Mode
Active Time
Power Saving Mode
Connected
Mode
UE is listening to the paging channel.
The UE is not listening to the paging channel. 2

3. oneM2M <schedule>
The <schedule> resource contains scheduling information. The usage of the <schedule> resource is slightly different depending on the associated resource type, such as follows:
A child <schedule> resource of the <CSEBase> and <remoteCSE> resources shall indicate the time periods when the CSE can send and receive the request.
A child <schedule> resource of the <AE> resource shall indicate the time periods when the application of a node can be accessed.
Active Time
Power Saving Mode
End Time of Schedule
Next Start Time of Schedule
Start Time of Schedule
Interval of Schedule 3

4. Resource <schedule> updating
Indicates whether <schedule> is synchronized with underlying network or registrar CSE. Possible values are:
NotSync: Not synchronized with Underlying Network or registrar CSE
SyncWithUnderlyingNetwork: Synchronized with the underlying network. For example, if it is 3GPP network it indicates the schedule of an ASN/MN-CSE or ADN-AE hosted on the UE is synchronized with the 3GPP network. This means the start time of <schedule> is the same as the targeted UE changes to idle mode status.
SyncWithCSE: Synchronized with registrar CSE schedule. It is only used for the <schedule> resource of <AE>. 4

5. Service Flow-ASN/MN-CSE or ADN-AE Creates the <schedule> in IN-CSE
<CSEBase>
<CSEBase>/<AE>
Create
<remoteCSE>
<schedule>
<scheduleAnnc>
syncIndicator
NotSync
syncIndicator
NotSync 5

6. Service Flow-IN-CSE Synchronizes <schedule> from 3GPP network
<CSEBase>
<CSEBase>/<AE>
<remoteCSE>
Update
<schedule>
<scheduleAnnc>
syncIndicator:
SyncWithUnderlyingNetwork
syncIndicator:
SyncWithUnderlyingNetwork
Active Time
Power Saving Mode
End Time of Schedule
Next Start Time of Schedule
Start Time of Schedule
Interval of Schedule
Next End Time of Schedule 6

7. Service Flow-IN-CSE Stops synchronizing <schedule> from 3GPP network
<CSEBase>
<CSEBase>/<AE>
<remoteCSE>
Update
<schedule>
<scheduleAnnc>
syncIndicator:
NotSync
syncIndicator:
NotSync 7

8. Service Flow- Targeting UE when <schedule> synchronized with Network
End Time of Schedule
Next Start Time of Schedule
Interval of Schedule
Start Time of Schedule
Active Time
Power Saving Mode
Active Time
CASE A:
IN-CSE sends the request to the UE directly
CASE B: Operation Execution Time or Request Expiration Timestamp are earlier than next Start time
IN-CSE sends response with error result
CASE C: Operation Execution Time or Request Expiration Timestamp are later than next Start time
IN-CSE buffers the message and sends message when UE is reachable again 8

9. Service Flow- Targeting UE when the <schedule> not synchronized with Network
When syncIndicator of <schedule> of target ASN/MN-CSE or ADN-AE is NotSync or absent, this procedure is no change from the basic procedure in clause of TS-0001. 9

10. Thanks for your listening! Q & A