Private Mobile

Private Mobile

Search form

Search

Search

Products Industries Insights Solutions

Wireless
Internet
Offers
Network Services Internet of Things
Voice
Cybersecurity

Support center
Contact us

Home

Mobility services

Mobile remote access

AT&T Private Mobile Connection

Talk to a business expert
866.945.8251

Benefits

Options

Features

FAQ

Resources

Maximize your WAN
Extend your WAN infrastructure to mobile end points

Customer deployments
Effortless, clientless solutions for mobile devices

Security features
A layered approach to security

How do I know if this is a good solution for me?

I don’t have wireline connection available, is AT&T Private Mobile Connection an option?

How does this product support financial institutions?

Resources
Access for everywhere you work

To get sales help from a Business Solutions specialist, please complete this form.

Yes, please send me the latest news and offers for AT&T Business solutions.

Wireless coverage map
Shop the virtual store
Find a store
News
About AT&T
Sitemap

Private wireless network solution that extends your WAN infrastructure to mobile end points. Designed specifically for enterprise and FirstNet customers.
Customer private network extension into the cellular network.
Enables the extension of existing private network into the cellular network. Flexible IP addressing options (public, private, dynamic, static, customer or AT&T provided).
Flexibility in connectivity options
Variety of network connectivity options with AT&T VPN services – MPLS or IPSec.
Customizable standards-based security enhancement (private IP, firewall options, access control, traffic isolation).
Connectivity in hard to reach locations
Enablement and connectivity of mobile workers and locations that are hard to reach.
Diversity options for enterprise connections and redundancy in AT&T radio and core network elements. True redundancy in back-up deployments.
Extend the enterprise network to the mobile worker and provide access to Internet based applications. Custom access point names (APNs) allow mobile users to access Enterprise LAN on any mobile network.
Connect tracking equipment, point of sales devices, vending machines, alarm or telemetry devices that “push or pull” data to the enterprise LAN.
AT&T provides mobile connections as a fully redundant failover for wireline connections (AVPNs, MIS) allowing enterprises to maintain business continuity.
If you rely on wireline connection, AT&T Private Mobile Connection is great as it has automatic failover for mission critical applications when a cable cut or outage is detected. It enables business to continue while the wireline solution is being restored.
Yes, it offer cost-effective connectivity for low-bandwidth transactional applications from virtually any location via the AT&T network. It’s an excellent solution for temporary deployments.
It supports wireless ATM machines, providing backup of applications with wireline connectivity.
AT&T business experts are available M - F 7am - 7pm CT
Please fix the below request info form errors
We are committed to protecting your privacy .
Thank you for contacting us about AT&T Private Mobile Connection. An AT&T Representative will contact you shortly to provide any additional information and answer any questions.
Your feedback will help us to improve AT&T Business so you continue to have a great experience when visiting us!
This survey is conducted by an independent company ForeSee for AT&T.
© AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T intellectual property and/or AT&T affiliated companies. All other marks are the property of their respective owners.
AT&T uses necessary cookies and similar technologies to make our sites work for you. We offer additional cookies to enhance your
experience, improve our sites, or offer specific services on your request. This data gives AT&T feedback on how you use our products
and services, helps us develop promotional and marketing materials relevant to you, and allows us to connect you with appropriate
content from third parties. You can read more about the cookies we use in our AT&T Most of World Website User Notice .
A wide variety of vendors off device security solutions, AT&T partners with those vendors to provide the device security solution that works best with the enterprise’s application and network deployment.
Provides encryption of the enterprise's data traffic that's exchanged between a device and our mobility network (128-bit encryption on the 3G and 4G LTE network).
Segments the enterprise’s mobile data traffic in the core network by using individual Layer 2 tunnels to route the traffic to AT&T National Data Centers. The traffic is aggregated and further isolated per enterprise at these data centers via the use of individual Layer 2 virtual LANs and virtual routing and forwarding instances.
Employs fully geo-redundant data centers that will divert wireless traffic to other data centers in the case of a link or data center outage.
High-speed support HSPA+ (14.4Mb and 21.1Mb) and LTE support.
Implementation in 4 geo redundant AT&T Mobility Data Centers (Concord, CA, Alpharetta, GA (VTC-11), Houston, TX; Arlington, VA).
Port Address Translation (PAT) support for internet access.
New AT&T VPN transport (>10GigE) in all AT&T Private Mobile Connections – LTE service zones. Higher speed interconnects from mobility to customer’s enterprise network. Support for larger static-IP APN deployments.
Evolution of the existing self service systems (Premier) for LTE, giving customers greater control and flexibility over IP assignments and EOD provisioning/billing systems.

Table of contents

Exit focus mode

Light

Dark

High contrast

Light

Dark

High contrast

This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This article introduces the key physical components of a private mobile network deployed through Azure Private 5G Core Preview. It also details the resources you'll use to manage the private mobile network through Azure.
Each private mobile network contains one or more sites . A site is a physical enterprise location (for example, Contoso Corporation's Chicago Factory) that will provide coverage for user equipment (UEs). The following diagram shows the main components of a single site.
Each site contains an Azure Stack Edge device that hosts a packet core instance , which is deployed using Azure Private 5G Core. The packet core instance is a cloud-native implementation of the 3GPP standards-defined 5G Next Generation Core (5G NGC or 5GC).
When you add a site to your private mobile network, you'll create a Kubernetes cluster on the Azure Stack Edge device. This serves as the platform for the packet core instance.
Each packet core instance connects to a radio access network (RAN) to provide coverage for UEs. You'll source your RAN from a third party.
The following diagram shows the key resources you'll use to manage your private mobile network through Azure.
The mobile network resource represents the private mobile network as a whole.
Each SIM resource represents a physical SIM or eSIM. The physical SIMs and eSIMs are used by UEs that will be served by the private mobile network.
SIM group resources serve as containers for SIM resources and allow you to sort SIMs into categories for easier management. Each SIM must be a member of a SIM group, but can't be a member of more than one. If you only have a small number of SIMs, you may want to add them all to the same SIM group. Alternatively, you can create multiple SIM groups to sort your SIMs. For example, you could categorize your SIMs by their purpose (such as SIMs used by specific UE types like cameras or cellphones), or by their on-site location.
SIM policy resources are a key component of Azure Private 5G Core's customizable policy control, which allows you to provide flexible traffic handling. You can determine exactly how your packet core instance applies quality of service (QoS) characteristics to service data flows (SDFs) to meet your deployment's needs. You can also use policy control to block or limit certain flows.
Each SIM policy defines a set of policies and interoperability settings. You'll need to assign a SIM policy to a SIM before the UE using that SIM can access the private mobile network.
A SIM policy will also reference one or more services . Each service is a representation of a set of QoS characteristics that you want to offer to UEs on SDFs that match particular properties, such as their destination, or the protocol used. You can also use services to limit or block particular SDFs based on these properties.
For detailed information on policy control, see Policy control .
The mobile network site and packet core resources allow you to manage the sites in your private mobile network and the packet core instances that run in them.
Each attached data network resource allows you to manage how its associated packet core instance will connect to the data network.

Table of contents

Exit focus mode

Light

Dark

High contrast

Light

Dark

High contrast

This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In this how-to guide, you'll carry out each of the tasks you need to complete before you can deploy a private mobile network using Azure Private 5G Core Preview.
Contact your trials engineer and ask them to register your Azure subscription for access to Azure Private 5G Core. If you don't already have a trials engineer and are interested in trialing Azure Private 5G Core, contact your Microsoft account team, or express your interest through the partner registration form .
Once your trials engineer has confirmed your access, register the Mobile Network resource provider (Microsoft.MobileNetwork) for your subscription, as described in Azure resource providers and types .
Choose whether each site in the private mobile network should provide coverage for 5G or 4G user equipment (UEs). A single site can't support 5G and 4G UEs simultaneously. If you're deploying multiple sites, you can choose to have some sites support 5G UEs and others support 4G UEs.
Azure Private 5G Core requires a management network, access network, and data network. These networks can all be part of the same, larger network, or they can be separate. The approach you use depends on your traffic separation requirements.
For each of these networks, allocate a subnet and then identify the listed IP addresses. If you're deploying multiple sites, you'll need to collect this information for each site.
Azure Private 5G Core supports the following IP address allocation methods for UEs.
Dynamic. Dynamic IP address allocation automatically assigns a new IP address to a UE each time it connects to the private mobile network.
Static. Static IP address allocation ensures that a UE receives the same IP address every time it connects to the private mobile network. This is useful when you want Internet of Things (IoT) applications to be able to consistently connect to the same device. For example, you may configure a video analysis application with the IP addresses of the cameras providing video streams. If these cameras have static IP addresses, you won't need to reconfigure the video analysis application with new IP addresses each time the cameras restart. You'll allocate static IP addresses to a UE as part of provisioning its SIM .
You can choose to support one or both of these methods for each site in your private mobile network.
For each site you're deploying, do the following:
Decide which IP address allocation methods you want to support.
For each method you want to support, identify an IP address pool from which IP addresses can be allocated to UEs. You'll need to provide each IP address pool in CIDR notation.
If you decide to support both methods for a particular site, ensure that the IP address pools are of the same size and don't overlap.
Decide whether you want to enable Network Address and Port Translation (NAPT) for the data network. NAPT allows you to translate a large pool of private IP addresses for UEs to a small number of public IP addresses. The translation is performed at the point where traffic enters the data network, maximizing the utility of a limited supply of public IP addresses.
For each site you're deploying, do the following.
The following table contains the ports you need to open for Azure Private 5G Core local access. This includes local management access and control plane signaling.
Do the following for each site you want to add to your private mobile network. Detailed instructions for how to carry out each step are included in the Detailed instructions column where applicable.
You can now collect the information you'll need to deploy your own private mobile network.
Access to local monitoring tools (packet core dashboards and distributed tracing).
Control plane access signaling (N2 interface). Only required for 5G deployments.
Control plane access signaling (S1-MME interface). Only required for 4G deployments.
Access network user plane data (N3 interface for 5G, S1-U for 4G).
Data network user plane data (N6 interface for 5G, SGi for 4G).
Complete the Azure Stack Edge Pro deployment checklist.
Order and prepare your Azure Stack Edge Pro device.
Rack and cable your Azure Stack Edge Pro device. When carrying out this procedure, you must ensure that the device has its ports connected as follows: - Port 5 - access network - Port 6 - data network Additionally, you must have a port connected to your management network. You can choose any port from 2 to 4.
Connect to your Azure Stack Edge Pro device using the local web UI.
Configure the network for your Azure Stack Edge Pro device. When carrying out the Enable compute network step of this procedure, ensure you use the port you've connected to your management network.
Configure a name, DNS name, and (optionally) time settings.
Configure certificates for your Azure Stack Edge Pro device.
Activate your Azure Stack Edge Pro device.
Run the diagnostics tests for the Azure Stack Edge Pro device in the local web UI, and verify they all pass. You may see a warning about a disconnected, unused port. You should fix the issue if the warning relates to any of these ports: - Port 5. - Port 6. - The port you chose to connect to the management network in Step 3. For all other ports, you can ignore the warning. If there are any errors, resolve them before continuing with the remaining steps. This includes any errors related to invalid gateways on unused ports. In this case, either delete the gateway IP address or set it to a valid gateway for the subnet.
Deploy an Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on your Azure Stack Edge Pro device. At the end of this step, the Kubernetes cluster will be connected to Az
Wall Penetration
Cum Oral Sex
Chubby Mature

Private Mobile

Report Page