Initial setup steps

This page describes the initial setup steps required to use Telecom Subscriber Insights.

Create a new network configuration

If necessary, do the following to create a new network configuration:

  1. Contact your Google sales representative to request access to the Google ISP Portal.
  2. After you have access, go to the Google ISP Portal and create a new network configuration.
  3. Enter the required information in the Google ISP Portal.
  4. Click Submit.

    Note the carrier ID or network ID that the Google ISP Portal displays when you submit your network configuration.

  5. Share the following with Google:

    • Carrier ID or network ID
    • Autonomous system number (ASN)
    • Mobile country code (MCC)
    • Mobile network code (MNC)

    We use this information to register your carrier with Google Traffic Application Function. For more information, see Getting Started with Mobile Data Plan Sharing.

Set up a CPID endpoint

Establish a carrier plan identifier (CPID) endpoint. You have two options for establishing a CPID endpoint:

  • Google can set up the CPID server as part of the Telecom Subscriber Insights deployment. If you choose this option, you don't need to deploy the CPID endpoint within your domain. However, you configure your packet gateway to enrich the HTTP header of the CPID endpoint in a later step.

  • You implement the CPID endpoint. If you choose this option, you need to deploy a CPID generation server. Every time a new CPID is generated, you publish the updated CPID to a Pub/Sub topic. We share the Pub/Sub topic with you when we deploy your Telecom Subscriber Insights instance.

Discuss with your sales representative which option works best for your situation.

For more information, see Establishing CPID.

Accept your Google Cloud project

We deploy the following Telecom Subscriber Insights components and then transfer the project ownership to you:

  • Data plan agent endpoint
  • CPID endpoint, if you requested that we create one for you
  • Pub/Sub endpoints for real-time data ingestion
  • Cloud Storage buckets for batched data ingestion
  • Data pipelines for ingesting the following customer records:
    • Usage
    • Account summary
  • Machine learning (ML) pipelines for data processing and model training
  • Continuous integration/continuous delivery (CI/CD) pipelines based on Cloud Build
  • Monitoring dashboards
  • Looker templates

When the Google Cloud project is ready for your acceptance, we send you an email.

To accept the project from the Google-owned organization, do the following:

  1. As an organization policy administrator, select your organization in the project selector. For more information, see Introduction to the Organization Policy Service.

  2. In the Google Cloud console, go to the Organization policies page.

    Go to Organization policies

  3. Click Select, and then select the organization policy to update. The Organization policies page displays a list of organization policy constraints that are available.

  4. In the Filter search field, enter constraints/resourcemanager.allowedImportSources.

  5. In the filtered results, click Allowed Sources for Importing Resources, and then click Manage policy.

  6. Click Edit, and then on the Edit policy page in the Applies to section, select Customize.

  7. In the Policy enforcement section, select Replace.

  8. In the Rules section, click Add Rule.

  9. For Policy values, choose Custom.

  10. For Policy type, choose Allow.

  11. In the Policy values box, enter under:organizations/ORGANIZATION_ID.

    Replace ORGANIZATION_ID with the organization identity value shared by Google.

  12. Click Done.

Migrate the Google Cloud project into your organization

  1. Run the following command to enable your Google Cloud engineer to help move the project:

    gcloud resource-manager folders add-iam-policy-binding FOLDER_OR_ORG_ID \

    Replace the following:

    • FOLDER_OR_ORG_ID: your folder ID or organization ID

    • CLOUD_ENGINEER_ID: the cloud engineer user ID

  2. Share the email address of your Google Cloud engineer with us so that we can assign required permissions and hand off the Google Cloud project.

  3. Run the following command to move the Google Cloud project:

    gcloud beta projects move PROJECT_ID \

    Replace the following:

    • PROJECT_ID: the ID of the project that you're moving; we provide you this value

    • DESTINATION_TYPE: one of either organization or folder

    • DESTINATION_ID: the destination organization ID or folder ID

  4. Change your billing account.

    To update the billing account for the Google Cloud project that we provided to you, see Change the Cloud Billing account linked to a project.

What's next

  • To pull the latest script updates and apply the updates to your project, see Apply script updates.