Fiware：订阅期限何时开始计算？
Fiware: when does the subscription duration count starts?
认购时长是从经纪人发送通知的最近时间开始计算，还是从实体发布其价值的最近时间开始计算？
如果从broker发送通知的最晚时间算起，是否意味着ONTIMEINTERVAL订阅永远不会过期？
谢谢并致以最诚挚的问候。
订阅的持续时间（对于 NGSIv1 订阅）从创建它的那一刻开始（或更新持续时间）。如本 piece of documenation:
中所述
expiration = current-time + duration
ONTIMEINTERVAL 订阅在这方面与 ONCHANGE 订阅行为相同。但是，您不应使用 ONTIMEINTERVAL，因为 they are deprecated:
ONTIMEINTERVAL subscriptions are deprecated since Orion 0.26.0 (removed in Orion 1.0.0). ONTIMEINTERVAL subscriptions have several problems (introduce state in CB, thus making horizontal scaling configuration much harder, and makes it difficult to introduce pagination/filtering). Actually, they aren't really needed, as any use case based on ONTIMEINTERVAL notification can be converted to an equivalent use case in which the receptor runs queryContext at the same frequency (and taking advantage of the features of queryContext, such as pagination or filtering).
认购时长是从经纪人发送通知的最近时间开始计算，还是从实体发布其价值的最近时间开始计算？ 如果从broker发送通知的最晚时间算起，是否意味着ONTIMEINTERVAL订阅永远不会过期？
谢谢并致以最诚挚的问候。
订阅的持续时间（对于 NGSIv1 订阅）从创建它的那一刻开始（或更新持续时间）。如本 piece of documenation:
中所述expiration = current-time + duration
ONTIMEINTERVAL 订阅在这方面与 ONCHANGE 订阅行为相同。但是，您不应使用 ONTIMEINTERVAL，因为 they are deprecated:
ONTIMEINTERVAL subscriptions are deprecated since Orion 0.26.0 (removed in Orion 1.0.0). ONTIMEINTERVAL subscriptions have several problems (introduce state in CB, thus making horizontal scaling configuration much harder, and makes it difficult to introduce pagination/filtering). Actually, they aren't really needed, as any use case based on ONTIMEINTERVAL notification can be converted to an equivalent use case in which the receptor runs queryContext at the same frequency (and taking advantage of the features of queryContext, such as pagination or filtering).