Reviewed by GoLicense Technical Team ·
Last updated:
ZTE supplies telecommunications platforms spanning radio access, core networks, optical access, transport, and network operations. Selecting a ZTE License means identifying the software rights required for a particular platform and deployment. The equipment model, installed release, requested functionality, and existing entitlements all need to match the proposed order.
For an expansion, describe the current configuration and the change you want to make. For a renewal, provide the existing agreement and coverage dates. This helps separate a software entitlement requirement from a hardware, configuration, or infrastructure limitation.
- Portfolio areas: Mobile networks, optical access, transport, and management or orchestration.
- Scope: The specific software, functions, and permitted capacity defined in the proposal.
- Compatibility: Confirm the chassis or platform, boards, software release, and dependencies.
- Commercial model: Confirm the chargeable unit, validity, support, and renewal conditions for each item.
- Quotation inputs: Model, product codes, inventory identifiers, release, existing rights, and target configuration.
Request ZTE Pricing: Send the product model, software version, required feature or capacity change, and current entitlement information. Include an approved bill of materials where available.
Send your ZTE model, software version, and required feature or capacity change for an availability review and tailored quotation.
Which ZTE Software Coverage Do You Need?
Start with the part of the network being changed. These are scoping areas, not universal license editions or a promise that every hardware capability requires a separate purchase.
| Your Requirement | Platform Area to Evaluate | What to Confirm Before Ordering |
|---|---|---|
| Extend mobile radio functionality | Applicable ZTE RAN software | Radio and baseband models, technology, release, and feature prerequisites |
| Expand packet-core or voice services | Applicable core-network software | Network functions, deployment architecture, capacity definition, and resilience |
| Change optical-access services | Applicable PON OLT platform, such as ZXA10 C600 | Control and service boards, PON technology, uplinks, software support, and entitlement requirements |
| Add transport-network functions | Applicable IP or optical transport platform | Interfaces, forwarding resources, required protocols, and release compatibility |
| Extend operations or automation | Applicable network-management or orchestration software | Managed equipment, applications, integration interfaces, and permitted deployment scope |
The quotation should name the exact item being supplied and the technical outcome it supports. General platform capabilities are not a substitute for an edition- and release-specific entitlement check.
How ZTE Licensing Scope Is Defined
Do not assume that every product is licensed by user, device, port, or throughput. Request the metric and quantity definition for the selected software item, including how an expansion is calculated.
Keep hardware capability, installed software, configured resources, and purchased rights separate in your inventory. A system may support an architecture or interface without the existing deployment meeting every prerequisite for the proposed change.
Confirm whether rights are time-limited, tied to a particular installation, or subject to another agreement. Ask how replacements, software upgrades, and additional environments affect the entitlement before approving the order.
Ordering Guide and Optical-Access Example
Your ZTE License proposal should identify the software description, verified ordering code, target platform, quantity, chargeable unit, validity, and support. Do not construct a part number from the equipment name.
Example: Reviewing an OLT Service Expansion
Suppose an ISP wants to expand services on an installed ZXA10 C600 platform. ZTE describes this family as supporting multiple PON technologies and different service and uplink cards. That does not establish which changes are available on the ISP’s actual configuration.
- Record chassis, control-board, service-board, and software details.
- Define the requested PON technology, service scope, and uplink requirements.
- Check hardware, optics, terminal compatibility, and resource limits.
- Confirm whether the change requires software rights, hardware changes, configuration, or a combination.
- List only verified entitlement items in the final quotation.
This is a planning example, not a claim that a particular PON feature is separately licensed. The proposed configuration must be reviewed against the applicable product documentation.
Prepare These Details Before Ordering
Provide model and board information, release identifiers, current entitlement records, required functions, and intended capacity. State units and scope explicitly: a site count, managed-element count, and throughput requirement describe different things.
ZTE Pricing & Quote
Pricing depends on the selected software item, permitted scope, quantity, commercial term, and support or implementation requirements. No universal public price list was verified for this portfolio during the November 2026 review.
Ask the quotation to separate software from hardware, upgrades, deployment work, and support. Confirm currency, taxes, validity, delivery conditions, and recurring charges where applicable.
For expansions, identify existing rights that remain usable. For renewals, confirm whether the offer continues the same scope or changes the entitlement. Our How to Buy from GoLicense explains the quotation and order-confirmation process.
Buying, Delivery and Activation with GoLicense
1. Confirm the Configuration and Order Scope
Submit your inventory and requested change. Confirm compatibility, availability, supplied items, quantity, and prerequisites before accepting the proposal.
2. Confirm Ownership and Required Identifiers
Identify the organization, installation, and authorized technical contact. Confirm which equipment or deployment identifiers are required and how they should be submitted.
3. Receive and Verify the Entitlement
Compare the supplied information against the approved order: product, permitted deployment, feature or capacity scope, validity, and installation instructions. The quotation should specify delivery method, expected timeframe, and any customer actions needed.
4. Activate and Test the Approved Change
Use the official procedure for the exact platform and release. Confirm whether the process requires a license file, an entitlement service, or a product-specific management workflow. No single ZTE activation command should be assumed across the portfolio.
After activation and configuration, verify entitlement status, alarms, service availability, and the agreed performance measurements. Retain the change record and rollback plan until acceptance is complete.
Restricted Networks and Deployment Preparation
For isolated management environments, confirm the supported activation, entitlement-transfer, renewal, and update process before purchase. Establish any required connectivity or authorized support involvement.
Plan administrative access, backups, release compatibility, and the maintenance window. In redundant systems, confirm how the proposed change applies to active, standby, and recovery components rather than assuming a single entitlement covers every role.
Before You Order: Prerequisites and Common Mistakes
Pre-Order Checklist
- Identify the model, hardware inventory, and software release.
- Define the requested function or capacity change.
- Confirm existing rights and the proposed chargeable unit.
- Validate dependencies and management compatibility.
- Assign installation, delivery, and acceptance responsibilities.
- Prepare backup, rollback, and service-verification steps.
Common Buying and Activation Issues
Requesting only the brand: Specify the platform and desired outcome so the proposal can be checked technically.
Assuming software alone enables an upgrade: Validate boards, optics, interfaces, and resource limits before ordering.
Using an ambiguous capacity figure: State units, location, and whether the requirement is per element, interface, or service.
Overlooking management integration: Check that the operations platform supports the intended release and equipment.
Assuming rights transfer automatically: Confirm replacement and reissue conditions before changing hardware.
Planning a ZTE expansion or renewal? Send your inventory and required changes for a quotation.