Open APIs

Greetings everyone!

In TMF638 we have "startDate" and "endDate" fields for a Service. The description for the startDate - A date time (DateTime). Date when the service starts. For the "endDate" it's veri similar.

In TMF638, we have the "startDate" and "endDate" fields for a Service. The description for startDate is "a date time (DateTime). Date when the service starts". The description for "endDate" is very similar - "a date time (DateTime). Date when the service ends". But what is meant "service starts" and "service ends"?

Hi Yurii

My take on this would be that the is that:

• startDate is initial provisioning or activation date of the Service
• endDate is the date when the Service was disconnected or otherwise terminated

Hope it helps

Greetings everyone!

In TMF638 we have "startDate" and "endDate" fields for a Service. The description for the startDate - A date time (DateTime). Date when the service starts. For the "endDate" it's veri similar.

In TMF638, we have the "startDate" and "endDate" fields for a Service. The description for startDate is "a date time (DateTime). Date when the service starts". The description for "endDate" is very similar - "a date time (DateTime). Date when the service ends". But what is meant "service starts" and "service ends"?

Thanks Jonathan!

Therefore your suggestion is based on the lifecycle of Service, right? In this case, the "endDate" is understandable, as it is related to the "terminated" state of the Service. But "startDate" is still not clear. If I can somehow align the "startDate" of the Service with its "active" state, what is the initial provisioning date of the Service?

Hi Yurii

My take on this would be that the is that:

• startDate is initial provisioning or activation date of the Service
• endDate is the date when the Service was disconnected or otherwise terminated

Hope it helps

Greetings everyone!

In TMF638 we have "startDate" and "endDate" fields for a Service. The description for the startDate - A date time (DateTime). Date when the service starts. For the "endDate" it's veri similar.

In TMF638, we have the "startDate" and "endDate" fields for a Service. The description for startDate is "a date time (DateTime). Date when the service starts". The description for "endDate" is very similar - "a date time (DateTime). Date when the service ends". But what is meant "service starts" and "service ends"?

Actually with Intent we have been using the startDate and endDate for future actions / service creations. Meaning that if an service intent is needed e.g. for a week in 2 months time. Then we could use startDate and endDate. 

Any view on this?

Thanks Jonathan!

Therefore your suggestion is based on the lifecycle of Service, right? In this case, the "endDate" is understandable, as it is related to the "terminated" state of the Service. But "startDate" is still not clear. If I can somehow align the "startDate" of the Service with its "active" state, what is the initial provisioning date of the Service?

Hi Yurii

My take on this would be that the is that:

• startDate is initial provisioning or activation date of the Service
• endDate is the date when the Service was disconnected or otherwise terminated

Hope it helps

Greetings everyone!

In TMF638 we have "startDate" and "endDate" fields for a Service. The description for the startDate - A date time (DateTime). Date when the service starts. For the "endDate" it's veri similar.

In TMF638, we have the "startDate" and "endDate" fields for a Service. The description for startDate is "a date time (DateTime). Date when the service starts". The description for "endDate" is very similar - "a date time (DateTime). Date when the service ends". But what is meant "service starts" and "service ends"?

Hi Martin!

In TMF638 v4, it seems logical. But if we check TMF638 v5, we see that the "Service" resource has a sub-resource "Intent" with a field "validFor" ("A TimePeriod. A period of time, either as a deadline (endDateTime only), or startDateTime only, or both."). And at the same time, the "startDate" and "endDate" fields are still present on the "Service" resource.

But nevertheless with what exactly does "the service starts" mean?

Actually with Intent we have been using the startDate and endDate for future actions / service creations. Meaning that if an service intent is needed e.g. for a week in 2 months time. Then we could use startDate and endDate. 

Any view on this?

Thanks Jonathan!

Therefore your suggestion is based on the lifecycle of Service, right? In this case, the "endDate" is understandable, as it is related to the "terminated" state of the Service. But "startDate" is still not clear. If I can somehow align the "startDate" of the Service with its "active" state, what is the initial provisioning date of the Service?

Hi Yurii

My take on this would be that the is that:

• startDate is initial provisioning or activation date of the Service
• endDate is the date when the Service was disconnected or otherwise terminated

Hope it helps

Greetings everyone!

In TMF638 we have "startDate" and "endDate" fields for a Service. The description for the startDate - A date time (DateTime). Date when the service starts. For the "endDate" it's veri similar.

In TMF638, we have the "startDate" and "endDate" fields for a Service. The description for startDate is "a date time (DateTime). Date when the service starts". The description for "endDate" is very similar - "a date time (DateTime). Date when the service ends". But what is meant "service starts" and "service ends"?

> But nevertheless with what exactly does "the service starts" mean? 

if you need to have eg. private network in the future. So a timed order so that the service is activated only on the start date. Qualifications etc can be done earlier. 

Hi Martin!

In TMF638 v4, it seems logical. But if we check TMF638 v5, we see that the "Service" resource has a sub-resource "Intent" with a field "validFor" ("A TimePeriod. A period of time, either as a deadline (endDateTime only), or startDateTime only, or both."). And at the same time, the "startDate" and "endDate" fields are still present on the "Service" resource.

But nevertheless with what exactly does "the service starts" mean?

Actually with Intent we have been using the startDate and endDate for future actions / service creations. Meaning that if an service intent is needed e.g. for a week in 2 months time. Then we could use startDate and endDate. 

Any view on this?

Thanks Jonathan!

Therefore your suggestion is based on the lifecycle of Service, right? In this case, the "endDate" is understandable, as it is related to the "terminated" state of the Service. But "startDate" is still not clear. If I can somehow align the "startDate" of the Service with its "active" state, what is the initial provisioning date of the Service?

Hi Yurii

My take on this would be that the is that:

• startDate is initial provisioning or activation date of the Service
• endDate is the date when the Service was disconnected or otherwise terminated

Hope it helps

Greetings everyone!

In TMF638 we have "startDate" and "endDate" fields for a Service. The description for the startDate - A date time (DateTime). Date when the service starts. For the "endDate" it's veri similar.

In TMF638, we have the "startDate" and "endDate" fields for a Service. The description for startDate is "a date time (DateTime). Date when the service starts". The description for "endDate" is very similar - "a date time (DateTime). Date when the service ends". But what is meant "service starts" and "service ends"?