multiple data retrieval
in an order
Group Name: ARC WG
Source: SeungMyeong JEONG, KETI, [email protected]
Meeting Date: 2016-11-30
Agenda Item: TBD
Motivation
• wants to get a number of data instances in a
specific order
board
art1
art2
visualize
art3
…
© 2014 oneM2M Partners
2
Backgrounds
• Result Content and Filter Criteria
– xxx
req1 to RETRIEVE “board”
{ limit = 10,
Result Content = “child-resources” }
App
resp1
{ Content Status = partial,
Content Offset = 2,
representation of “art1” and “art2” resources }
art1
art2
Platform
art3
…
req2 to RIETRIEVE “board”
{ limit = 10, offset = 2, Result Content =
“child-resources” }
board
© 2014 oneM2M Partners
3
Problem
• no mechanism to indicate the order for
multiple resource retrieval
– xx
board
retrieve target (a)
latest
retrieve target (b)
oldest
from latest
art1
• creationTime: 13h00m
art2
• creationTime: 13h01m
art3
• creationTime: 13h02m
…
from oldest
artN
© 2014 oneM2M Partners
4
Proposal (1/3)
• for <latest> and <oldest> virtual resources
– the new virtualResource condition can be added
• to apply the other Filter Criteria conditions to virtual
resource functionalities
– e.g. multiple contentInstances from latest or oldest will be
applied
– Note that oneM2M does NOT explicitly say whether the Filter
Criteria applied to virtual resources or not
© 2014 oneM2M Partners
5
Proposal (2/3)
• for <container>/<contentInstance> resources
– the new order condition can be added to indicate
the order to apply retrieved resources
• optionally level info. can be added to limit the scope
– for <timeSeries>/<timeSeriesInstances> resources
• same as <container>/<contentInstance> except it has no
level sub-condition
© 2014 oneM2M Partners
6
Proposal (3/3)
• for <flexContainer>/<flexContainer> resources
– basically the same as container/contentInstance
– specialization type info (i.e. containerDefinition) is
also added
either
© 2014 oneM2M Partners
7