Get the Best Information for Your Region by Switching to the Aeris India Site.

Based on your location, we recommend switching to the Aeris Europe website. There you will find information about Aeris' IoT connectivity services unique to your region.

Get the Best Information for Your Region by Switching to the Aeris Europe Site.

Based on your location, we recommend switching to the Aeris Europe website. There you will find information about Aeris' IoT connectivity services unique to your region.

You can always switch back by using the Switch Regions menu at the top of the website.

Blog

Aeris Connectivity Customers Can Use Google Cloud Platform to Analyze Near Real-Time Usage Data

New Features

Google Cloud Platform (GCP) provides a robust platform for running enterprise analytics workloads. Today, we are making it possible for Aeris connectivity customers to analyze near-real-time usage data in GCP, gleaning insights above and beyond those readily displayed in Aeris’ connectivity management portal, AerPort.

For example, customers can analyze usage data streamed into GCP to:

  • Automatically identify network-ready devices, and then use that status as a trigger for over-the-air (OTA) firmware updates, reducing the cost and time-to-completion for those updates; or to
  • Automatically identify devices that haven’t connected over a particular time period (e.g., within the last two hours or the last 10 days).

Who is this feature for? This new feature is for customers who are using Aeris Fusion North America LTE/LTE-M or Aeris Fusion Global LTE, have their own GCP account, and want to use GCP to perform analytics.

What kinds of data does this feature make available? The data streamed into GCP are packet start, packet stop, packet continued, and details of the location update, location cancel, and registration purge records for all devices.

Events are published in cloud events format (https://github.com/cloudevents/spec)

HSS feed data follows specifications defined in 3GPP TS 29.272, for Update-Location-Answer (in Section 7.2.4), Cancel-Location-Answer (in Section 7.2.8), and Purge-UE-Answer (in Section 7.2.14) Commands.  User is directed to that specification document for further information.

Packet gateway (PGW) feed data for Start, Stop, and Continued records have the following field formats:

Field#    Field information:

1              recordType

2              imsi

3              Pgw Address

4              chargingID

5              servingNodeAddress

6              apnName

7              pdpPDNType

8              servedPDPPDNAddress

9              dynamicAddressFlag

10           recordOpeningTime

11           duration

12           causeForRecClosing

13           diagnostics

14           recordSequenceNumber

15           nodeID

16           localSequenceNumber

17           apnSelectionMode

18           servedMSISDN

19           chargingCharacteristics

20           chChSelectionMode

21           servingNodePLMNID

22           servedIMEISV

23           RATType

24           mSTimeZone

25           userLocInfo

26           ratingGroup

27           chargingRuleBaseName

28           resultCode

29           localSequenceNumber

30           timeOfFirstUse

31           timeOfLastUse

32           timeUsage

33           serviceConditionChange

34           qoSInformationNeg

35           dataVolUplink

36           dataVolDownlink

37           timeOfReport

38           failureHandlingContinue

39           serviceIdentifier

40           userLocInfo

41           servingNodeType

42           servedMNNAI

43           pGWPLMNIdentifier

44           startTime

45           stopTime

46           pDNConnectionID

47           acctStatusType

How much does this feature cost? Aeris does not charge customers for using this feature. Google, however, will apply standard rates for use of various GCP services. Please refer to Google Cloud for pricing.

For more information on how Aeris and Google work together, contact Aeris today.