Skip to content
camara
Get started
API Reference
Connectivityinsights
Subscriptions

Create a Connectivity insights subscription for a device

POST/connectivityinsights/subscriptions

Create a Connectivity insights subscription for a device

Header ParametersExpand Collapse
"x-correlator": optional string
Body ParametersJSONExpand Collapse
config: Config { subscriptionDetail, initialEvent, subscriptionExpireTime, subscriptionMaxEvents }

Implementation-specific configuration parameters needed by the subscription manager for acquiring events. In CAMARA we have predefined attributes like subscriptionExpireTime, subscriptionMaxEvents, initialEvent Specific event type attributes must be defined in subscriptionDetail Note: if a request is performed for several event type, all subscribed event will use same config parameters.

subscriptionDetail: object { applicationProfileId, device, applicationServer, applicationServerPorts }

The detail of the requested event subscription

applicationProfileId: string

Identifier for the Application Profile

formatuuid
device: object { ipv4Address, ipv6Address, networkAccessIdentifier, phoneNumber }

End-user equipment able to connect to a mobile network. Examples of devices include smartphones or IoT sensors/actuators. The developer can choose to provide the below specified device identifiers: * ipv4Address * ipv6Address * phoneNumber * networkAccessIdentifier NOTE1: the network operator might support only a subset of these options. The API invoker can provide multiple identifiers to be compatible across different network operators. In this case the identifiers MUST belong to the same device. NOTE2: as for this Commonalities release, we are enforcing that the networkAccessIdentifier is only part of the schema for future-proofing, and CAMARA does not currently allow its use. After the CAMARA meta-release work is concluded and the relevant issues are resolved, its use will need to be explicitly documented in the guidelines.

ipv4Address: optional object { privateAddress, publicAddress, publicPort }

The device should be identified by either the public (observed) IP address and port as seen by the application server, or the private (local) and any public (observed) IP addresses in use by the device (this information can be obtained by various means, for example from some DNS servers).

If the allocated and observed IP addresses are the same (i.e. NAT is not in use) then the same address should be specified for both publicAddress and privateAddress.

If NAT64 is in use, the device should be identified by its publicAddress and publicPort, or separately by its allocated IPv6 address (field ipv6Address of the Device object)

In all cases, publicAddress must be specified, along with at least one of either privateAddress or publicPort, dependent upon which is known. In general, mobile devices cannot be identified by their public IPv4 address alone.

privateAddress: optional string

A single IPv4 address with no subnet mask

formatipv4
publicAddress: optional string

A single IPv4 address with no subnet mask

formatipv4
publicPort: optional number

TCP or UDP port number

minimum0
maximum65535
ipv6Address: optional string

The device should be identified by the observed IPv6 address, or by any single IPv6 address from within the subnet allocated to the device (e.g. adding ::0 to the /64 prefix).

The session shall apply to all IP flows between the device subnet and the specified application server, unless further restricted by the optional parameters devicePorts or applicationServerPorts.

formatipv6
networkAccessIdentifier: optional string

A public identifier addressing a subscription in a mobile network. In 3GPP terminology, it corresponds to the GPSI formatted with the External Identifier ({Local Identifier}@{Domain Identifier}). Unlike the telephone number, the network access identifier is not subjected to portability ruling in force, and is individually managed by each operator.

phoneNumber: optional string

A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Number). In order to be globally unique it has to be formatted in international format, according to E.164 standard, prefixed with ’+’.

applicationServer: optional object { ipv4Address, ipv6Address }

A server hosting backend applications to deliver some business logic to clients.

The developer can choose to provide the below specified device identifiers:

  • ipv4Address
  • ipv6Address

The Operator will use this information to calculate the end to end network performance in scenarios where its feasible.

ipv4Address: optional string

IPv4 address may be specified in form <address/mask> as:

  • address - an IPv4 number in dotted-quad form 1.2.3.4. Only this exact IP number will match the flow control rule.
  • address/mask - an IP number as above with a mask width of the form 1.2.3.4/24. In this case, all IP numbers from 1.2.3.0 to 1.2.3.255 will match. The bit width MUST be valid for the IP version.
ipv6Address: optional string

IPv6 address may be specified in form <address/mask> as:

  • address - The /128 subnet is optional for single addresses:
    • 2001:db8:85a3:8d3:1319:8a2e:370:7344
    • 2001:db8:85a3:8d3:1319:8a2e:370:7344/128
  • address/mask - an IP v6 number with a mask:
    • 2001:db8:85a3:8d3::0/64
    • 2001:db8:85a3:8d3::/64
applicationServerPorts: optional object { ports, ranges }

Specification of several TCP or UDP ports

ports: optional array of number

Array of TCP or UDP ports

ranges: optional array of object { from, to }

Range of TCP or UDP ports

from: number

TCP or UDP port number

minimum0
maximum65535
to: number

TCP or UDP port number

minimum0
maximum65535
initialEvent: optional boolean

Set to true by API consumer if consumer wants to get an event as soon as the subscription is created and current situation reflects event request.

subscriptionExpireTime: optional string

The subscription expiration time (in date-time format) requested by the API consumer. Up to API project decision to keep it. It must follow RFC 3339 and must have time zone.

formatdate-time
subscriptionMaxEvents: optional number

Identifies the maximum number of event reports to be generated (>=1) requested by the API consumer - Once this number is reached, the subscription ends. Note on combined usage of initialEvent and subscriptionMaxEvents: If an event is triggered following initialEvent set to true, this event will be counted towards subscriptionMaxEvents.

minimum1
protocol: Protocol

Identifier of a delivery protocol. Only HTTP is allowed for now

One of the following:
"HTTP"
"MQTT3"
"MQTT5"
"AMQP"
"NATS"
"KAFKA"
sink: string

The address to which events shall be delivered using the selected protocol.

formaturi
types: array of EventType

Camara Event types eligible to be delivered by this subscription.

sinkCredential: optional object { credentialType }

A sink credential provides authentication or authorization information

credentialType: "PLAIN" or "ACCESSTOKEN" or "REFRESHTOKEN"

The type of the credential. Note: Type of the credential - MUST be set to ACCESSTOKEN for now

One of the following:
"PLAIN"
"ACCESSTOKEN"
"REFRESHTOKEN"
ReturnsExpand Collapse
Subscription object { config, protocol, sink, 5 more }

Represents a event-type subscription.

config: Config { subscriptionDetail, initialEvent, subscriptionExpireTime, subscriptionMaxEvents }

Implementation-specific configuration parameters needed by the subscription manager for acquiring events. In CAMARA we have predefined attributes like subscriptionExpireTime, subscriptionMaxEvents, initialEvent Specific event type attributes must be defined in subscriptionDetail Note: if a request is performed for several event type, all subscribed event will use same config parameters.

subscriptionDetail: object { applicationProfileId, device, applicationServer, applicationServerPorts }

The detail of the requested event subscription

applicationProfileId: string

Identifier for the Application Profile

formatuuid
device: object { ipv4Address, ipv6Address, networkAccessIdentifier, phoneNumber }

End-user equipment able to connect to a mobile network. Examples of devices include smartphones or IoT sensors/actuators. The developer can choose to provide the below specified device identifiers: * ipv4Address * ipv6Address * phoneNumber * networkAccessIdentifier NOTE1: the network operator might support only a subset of these options. The API invoker can provide multiple identifiers to be compatible across different network operators. In this case the identifiers MUST belong to the same device. NOTE2: as for this Commonalities release, we are enforcing that the networkAccessIdentifier is only part of the schema for future-proofing, and CAMARA does not currently allow its use. After the CAMARA meta-release work is concluded and the relevant issues are resolved, its use will need to be explicitly documented in the guidelines.

ipv4Address: optional object { privateAddress, publicAddress, publicPort }

The device should be identified by either the public (observed) IP address and port as seen by the application server, or the private (local) and any public (observed) IP addresses in use by the device (this information can be obtained by various means, for example from some DNS servers).

If the allocated and observed IP addresses are the same (i.e. NAT is not in use) then the same address should be specified for both publicAddress and privateAddress.

If NAT64 is in use, the device should be identified by its publicAddress and publicPort, or separately by its allocated IPv6 address (field ipv6Address of the Device object)

In all cases, publicAddress must be specified, along with at least one of either privateAddress or publicPort, dependent upon which is known. In general, mobile devices cannot be identified by their public IPv4 address alone.

privateAddress: optional string

A single IPv4 address with no subnet mask

formatipv4
publicAddress: optional string

A single IPv4 address with no subnet mask

formatipv4
publicPort: optional number

TCP or UDP port number

minimum0
maximum65535
ipv6Address: optional string

The device should be identified by the observed IPv6 address, or by any single IPv6 address from within the subnet allocated to the device (e.g. adding ::0 to the /64 prefix).

The session shall apply to all IP flows between the device subnet and the specified application server, unless further restricted by the optional parameters devicePorts or applicationServerPorts.

formatipv6
networkAccessIdentifier: optional string

A public identifier addressing a subscription in a mobile network. In 3GPP terminology, it corresponds to the GPSI formatted with the External Identifier ({Local Identifier}@{Domain Identifier}). Unlike the telephone number, the network access identifier is not subjected to portability ruling in force, and is individually managed by each operator.

phoneNumber: optional string

A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Number). In order to be globally unique it has to be formatted in international format, according to E.164 standard, prefixed with ’+’.

applicationServer: optional object { ipv4Address, ipv6Address }

A server hosting backend applications to deliver some business logic to clients.

The developer can choose to provide the below specified device identifiers:

  • ipv4Address
  • ipv6Address

The Operator will use this information to calculate the end to end network performance in scenarios where its feasible.

ipv4Address: optional string

IPv4 address may be specified in form <address/mask> as:

  • address - an IPv4 number in dotted-quad form 1.2.3.4. Only this exact IP number will match the flow control rule.
  • address/mask - an IP number as above with a mask width of the form 1.2.3.4/24. In this case, all IP numbers from 1.2.3.0 to 1.2.3.255 will match. The bit width MUST be valid for the IP version.
ipv6Address: optional string

IPv6 address may be specified in form <address/mask> as:

  • address - The /128 subnet is optional for single addresses:
    • 2001:db8:85a3:8d3:1319:8a2e:370:7344
    • 2001:db8:85a3:8d3:1319:8a2e:370:7344/128
  • address/mask - an IP v6 number with a mask:
    • 2001:db8:85a3:8d3::0/64
    • 2001:db8:85a3:8d3::/64
applicationServerPorts: optional object { ports, ranges }

Specification of several TCP or UDP ports

ports: optional array of number

Array of TCP or UDP ports

ranges: optional array of object { from, to }

Range of TCP or UDP ports

from: number

TCP or UDP port number

minimum0
maximum65535
to: number

TCP or UDP port number

minimum0
maximum65535
initialEvent: optional boolean

Set to true by API consumer if consumer wants to get an event as soon as the subscription is created and current situation reflects event request.

subscriptionExpireTime: optional string

The subscription expiration time (in date-time format) requested by the API consumer. Up to API project decision to keep it. It must follow RFC 3339 and must have time zone.

formatdate-time
subscriptionMaxEvents: optional number

Identifies the maximum number of event reports to be generated (>=1) requested by the API consumer - Once this number is reached, the subscription ends. Note on combined usage of initialEvent and subscriptionMaxEvents: If an event is triggered following initialEvent set to true, this event will be counted towards subscriptionMaxEvents.

minimum1
protocol: Protocol

Identifier of a delivery protocol. Only HTTP is allowed for now

One of the following:
"HTTP"
"MQTT3"
"MQTT5"
"AMQP"
"NATS"
"KAFKA"
sink: string

The address to which events shall be delivered using the selected protocol.

formaturi
startsAt: string

Date when the event subscription will begin/began It must follow RFC 3339 and must have time zone.

formatdate-time
types: array of EventType

Camara Event types eligible to be delivered by this subscription.

expiresAt: optional string

Date when the event subscription will expire. Only provided when subscriptionExpireTime is indicated by API client or Telco Operator has specific policy about that. It must follow RFC 3339 and must have time zone.

formatdate-time
status: optional "ACTIVATION_REQUESTED" or "ACTIVE" or "EXPIRED" or 2 more

Current status of the subscription - Management of Subscription State engine is not mandatory for now. Note not all statuses may be considered to be implemented. Details:

  • ACTIVATION_REQUESTED: Subscription creation (POST) is triggered but subscription creation process is not finished yet.
  • ACTIVE: Subscription creation process is completed. Subscription is fully operative.
  • DEACTIVE: Subscription is temporarily inactive, but its workflow logic is not deleted.
  • EXPIRED: Subscription is ended (no longer active). This status applies when subscription is ended due to SUBSCRIPTION_EXPIRED or ACCESS_TOKEN_EXPIRED event.
  • DELETED: Subscription is ended as deleted (no longer active). This status applies when subscription information is kept (i.e. subscription workflow is no longer active but its metainformation is kept).
One of the following:
"ACTIVATION_REQUESTED"
"ACTIVE"
"EXPIRED"
"DEACTIVE"
"DELETED"
subscriptionId: optional string

When this information is contained within an event notification, it SHALL be referred to as subscriptionId as per the Commonalities Event Notification Model.

Create a Connectivity insights subscription for a device

curl https://api.example.com/camara/connectivityinsights/subscriptions \
    -H 'Content-Type: application/json' \
    -H "Authorization: Bearer $CAMARA_BEARER_TOKEN" \
    -d '{
          "config": {
            "subscriptionDetail": {
              "applicationProfileId": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
              "device": {}
            }
          },
          "protocol": "HTTP",
          "sink": "https://endpoint.example.com/sink",
          "types": [
            "org.camaraproject.connectivity-insights-subscriptions.v0.network-quality"
          ]
        }'
{
  "config": {
    "subscriptionDetail": {
      "applicationProfileId": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
      "device": {
        "ipv4Address": {
          "privateAddress": "84.125.93.10",
          "publicAddress": "84.125.93.10",
          "publicPort": 59765
        },
        "ipv6Address": "2001:db8:85a3:8d3:1319:8a2e:370:7344",
        "networkAccessIdentifier": "123456789@domain.com",
        "phoneNumber": "+123456789"
      },
      "applicationServer": {
        "ipv4Address": "192.168.0.1/24",
        "ipv6Address": "2001:db8:85a3:8d3:1319:8a2e:370:7344"
      },
      "applicationServerPorts": {
        "ports": [
          5060,
          5070
        ],
        "ranges": [
          {
            "from": 5010,
            "to": 5020
          }
        ]
      }
    },
    "initialEvent": true,
    "subscriptionExpireTime": "2023-07-03T12:27:08.312Z",
    "subscriptionMaxEvents": 5
  },
  "protocol": "HTTP",
  "sink": "https://endpoint.example.com/sink",
  "startsAt": "2023-07-03T12:27:08.312Z",
  "types": [
    "org.camaraproject.connectivity-insights-subscriptions.v0.network-quality"
  ],
  "expiresAt": "2023-07-03T12:27:08.312Z",
  "status": "ACTIVATION_REQUESTED",
  "subscriptionId": "qs15-h556-rt89-1298"
}
{
  "status": 400,
  "code": "INVALID_ARGUMENT",
  "message": "Client specified an invalid argument, request body or query param."
}
{
  "status": 400,
  "code": "OUT_OF_RANGE",
  "message": "Client specified an invalid range."
}
{
  "status": 400,
  "code": "INVALID_PROTOCOL",
  "message": "Only HTTP is supported"
}
{
  "status": 400,
  "code": "INVALID_CREDENTIAL",
  "message": "Only Access token is supported"
}
{
  "status": 400,
  "code": "INVALID_TOKEN",
  "message": "Only bearer token is supported"
}
{
  "status": 400,
  "code": "INVALID_SINK",
  "message": "sink not valid for the specified protocol"
}
{
  "status": 401,
  "code": "UNAUTHENTICATED",
  "message": "Request not authenticated due to missing, invalid, or expired credentials. A new authentication is required."
}
{
  "status": 403,
  "code": "PERMISSION_DENIED",
  "message": "Client does not have sufficient permissions to perform this action."
}
{
  "status": 403,
  "code": "SUBSCRIPTION_MISMATCH",
  "message": "Inconsistent access token for requested events subscription"
}
{
  "status": 409,
  "code": "ABORTED",
  "message": "Concurrency conflict."
}
{
  "status": 409,
  "code": "ALREADY_EXISTS",
  "message": "The resource that a client tried to create already exists."
}
{
  "status": 422,
  "code": "SERVICE_NOT_APPLICABLE",
  "message": "The service is not available for the provided identifier."
}
{
  "status": 422,
  "code": "MISSING_IDENTIFIER",
  "message": "The device cannot be identified."
}
{
  "status": 422,
  "code": "UNNECESSARY_IDENTIFIER",
  "message": "The device is already identified by the access token."
}
{
  "status": 429,
  "code": "QUOTA_EXCEEDED",
  "message": "Out of resource quota."
}
{
  "status": 429,
  "code": "TOO_MANY_REQUESTS",
  "message": "Rate limit reached."
}
Returns Examples
{
  "config": {
    "subscriptionDetail": {
      "applicationProfileId": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
      "device": {
        "ipv4Address": {
          "privateAddress": "84.125.93.10",
          "publicAddress": "84.125.93.10",
          "publicPort": 59765
        },
        "ipv6Address": "2001:db8:85a3:8d3:1319:8a2e:370:7344",
        "networkAccessIdentifier": "123456789@domain.com",
        "phoneNumber": "+123456789"
      },
      "applicationServer": {
        "ipv4Address": "192.168.0.1/24",
        "ipv6Address": "2001:db8:85a3:8d3:1319:8a2e:370:7344"
      },
      "applicationServerPorts": {
        "ports": [
          5060,
          5070
        ],
        "ranges": [
          {
            "from": 5010,
            "to": 5020
          }
        ]
      }
    },
    "initialEvent": true,
    "subscriptionExpireTime": "2023-07-03T12:27:08.312Z",
    "subscriptionMaxEvents": 5
  },
  "protocol": "HTTP",
  "sink": "https://endpoint.example.com/sink",
  "startsAt": "2023-07-03T12:27:08.312Z",
  "types": [
    "org.camaraproject.connectivity-insights-subscriptions.v0.network-quality"
  ],
  "expiresAt": "2023-07-03T12:27:08.312Z",
  "status": "ACTIVATION_REQUESTED",
  "subscriptionId": "qs15-h556-rt89-1298"
}
{
  "status": 400,
  "code": "INVALID_ARGUMENT",
  "message": "Client specified an invalid argument, request body or query param."
}
{
  "status": 400,
  "code": "OUT_OF_RANGE",
  "message": "Client specified an invalid range."
}
{
  "status": 400,
  "code": "INVALID_PROTOCOL",
  "message": "Only HTTP is supported"
}
{
  "status": 400,
  "code": "INVALID_CREDENTIAL",
  "message": "Only Access token is supported"
}
{
  "status": 400,
  "code": "INVALID_TOKEN",
  "message": "Only bearer token is supported"
}
{
  "status": 400,
  "code": "INVALID_SINK",
  "message": "sink not valid for the specified protocol"
}
{
  "status": 401,
  "code": "UNAUTHENTICATED",
  "message": "Request not authenticated due to missing, invalid, or expired credentials. A new authentication is required."
}
{
  "status": 403,
  "code": "PERMISSION_DENIED",
  "message": "Client does not have sufficient permissions to perform this action."
}
{
  "status": 403,
  "code": "SUBSCRIPTION_MISMATCH",
  "message": "Inconsistent access token for requested events subscription"
}
{
  "status": 409,
  "code": "ABORTED",
  "message": "Concurrency conflict."
}
{
  "status": 409,
  "code": "ALREADY_EXISTS",
  "message": "The resource that a client tried to create already exists."
}
{
  "status": 422,
  "code": "SERVICE_NOT_APPLICABLE",
  "message": "The service is not available for the provided identifier."
}
{
  "status": 422,
  "code": "MISSING_IDENTIFIER",
  "message": "The device cannot be identified."
}
{
  "status": 422,
  "code": "UNNECESSARY_IDENTIFIER",
  "message": "The device is already identified by the access token."
}
{
  "status": 429,
  "code": "QUOTA_EXCEEDED",
  "message": "Out of resource quota."
}
{
  "status": 429,
  "code": "TOO_MANY_REQUESTS",
  "message": "Rate limit reached."
}