Reviewed by GoLicense Technical Team ·
Last updated:
An Ericsson License provides the software rights defined for a particular Ericsson product, feature, or capacity scope. Ericsson’s telecom portfolio includes radio access networks (RAN), mobile transport, core networks, and network-management software. The correct entitlement depends on the equipment, software release, required functionality, and commercial agreement.
For a new deployment, expansion, or renewal, start with the exact platform and business requirement. Include the installed configuration and existing entitlements so compatibility and order scope can be checked before purchase.
- Portfolio areas: RAN software, transport, core-network software, and management or automation.
- Scope: Product-specific features, capacity, subscriptions, or other rights stated in the offer.
- Compatibility: Confirm equipment, release, dependencies, and management support.
- Purchase type: New entitlement, expansion, renewal, or an approved change to existing coverage.
- Quotation inputs: Product codes, inventory, software versions, current rights, and target configuration.
Request Ericsson Pricing: Send your platform or model, software release, required feature or capacity change, and existing order references. Include a bill of materials if available.
Send your Ericsson platform, software release, and required features or capacity to request a scoped quotation.
Which Ericsson Software Entitlement Do You Need?
Identify the network domain first. The following is a selection guide, not a list of universal license editions or guaranteed orderable bundles.
| Your Requirement | Portfolio Area to Evaluate | What to Confirm Before Ordering |
|---|---|---|
| Add radio-network functionality | Ericsson Radio System software | RAN Compute and radio compatibility, release, feature dependencies, and deployment scope |
| Evaluate differentiated connectivity, efficiency, or advanced RAN capabilities | Applicable 5G Advanced software subscriptions | Selected subscription, network prerequisites, eligible footprint, and term |
| Expand microwave transport capacity | Applicable MINI-LINK software or capacity options | Installed radios, modem configuration, channel bandwidth, existing capacity, and target performance |
| Extend packet-core services | Applicable core-network software | Network functions, deployment platform, capacity definition, resilience, and integration |
| Manage radio, transport, and core infrastructure | Ericsson Network Manager and applicable automation software | Managed technologies, node integrations, release compatibility, and required applications |
Keep each requested entitlement tied to a technical objective: a named function, a defined capacity increase, or an agreed management scope.
How Ericsson Licensing Scope Is Defined
There is no single per-user, per-device, or bandwidth metric that can safely be applied across the Ericsson portfolio. Ask the quotation to define the chargeable unit, quantity, term, and usage rights for each line item.
Ericsson publicly offers subscription packages for 5G Advanced software. That does not establish the licensing model for every RAN, core, transport, or management product. Confirm whether the proposed rights are time-limited, capacity-related, or governed by another product-specific agreement.
Distinguish hardware capability, installed software, configured capacity, and licensed rights. A platform capable of a feature may still require a supported release, additional hardware, configuration changes, or a separate entitlement.
Ordering Guide and Expansion Example
The bill of materials should specify the exact software item, target platform, quantity and metric, release prerequisites, validity, and support scope. Verify part numbers against the proposed configuration; do not infer an order code from the product name alone.
Example: Reviewing a MINI-LINK Capacity Expansion
Suppose a network team wants more throughput on an existing microwave hop. First record the equipment at both ends, software versions, enabled capacity, channel plan, and measured utilization.
- Determine whether the constraint is licensed capacity, radio configuration, available spectrum, or hardware.
- Validate the proposed modulation, channel, or carrier configuration against the installed platform.
- Identify any required software rights and hardware changes in the quotation.
- Agree on acceptance tests for throughput, errors, and service availability.
Ericsson describes software-enabled expansion on compatible MINI-LINK equipment, but a license alone cannot overcome every radio or spectrum constraint. Final scope requires a review of the actual hop.
Prepare These Details Before Ordering
Provide product names and codes, inventory identifiers, software releases, current entitlement information, and the target configuration. For capacity changes, state the current and required capacity with units. For renewals, include existing agreement dates and coverage.
Ericsson License Pricing & Quote
Pricing depends on the specific product, feature or capacity scope, quantity, contract conditions, and support or integration requirements. No portfolio-wide public price range was verified during the November 2026 review.
Request a quotation that separates software rights from hardware, implementation, upgrades, and support. Confirm currency, taxes, offer validity, delivery conditions, and any recurring commitments.
For an expansion, ask what usable existing rights have been taken into account. For a renewal, confirm whether the offer continues the same scope or changes the permitted use. Our How to Buy from GoLicense explains the quotation and order-confirmation process.
Buying, Delivery and Activation with GoLicense
1. Confirm the Technical and Commercial Scope
Submit the required configuration and existing inventory. Confirm compatibility, available supply, software item descriptions, quantities, support, and any prerequisites before approving the order.
2. Confirm the Deployment and Delivery Details
Identify the organization, network environment, and authorized technical contact. Confirm which platform identifiers or customer references are needed and how entitlement information will be delivered.
3. Receive and Verify the Supplied Rights
Compare the delivery with the approved order. Check the product, applicable platform, feature or capacity scope, validity, and supplied installation instructions. The quotation should state the actual delivery timeframe and when it begins.
4. Activate and Validate in a Planned Change Window
Follow the documented workflow for the exact product and release. The required license file, entitlement procedure, management tool, or configuration action must be confirmed for that deployment; a universal Ericsson activation command should not be assumed.
After the change, verify entitlement status, enabled functionality, alarms, and the agreed service KPIs. Record the result and retain the approved rollback plan before closing the change.
Restricted Networks and Product Prerequisites
For isolated management networks, confirm the supported entitlement-transfer, activation, and renewal process before purchase. Establish whether any part of the workflow needs access to an external service or an authorized support channel.
Review hardware support, software dependencies, management compatibility, and resilience requirements. For transport changes, validate both ends of the link and the radio plan. For RAN or core changes, define the affected footprint and service acceptance criteria.
Before You Order: Prerequisites and Common Mistakes
Pre-Order Checklist
- Identify the product, release, and requested functionality.
- Separate current rights from desired capacity or feature changes.
- Confirm chargeable units, quantities, and term.
- Validate hardware and software prerequisites.
- Assign delivery, installation, and acceptance responsibilities.
- Prepare a change window, backup, rollback, and test plan.
Common Buying and Activation Issues
Requesting only a brand name: Supply the exact platform and intended change so a technically relevant offer can be prepared.
Confusing equipment support with enabled rights: Verify that both compatibility and entitlement requirements are satisfied.
Overlooking dependencies: Review the release and any prerequisite functions before purchasing the requested feature.
Treating a capacity number as self-explanatory: Specify units, scope, and whether the requirement applies to a link, platform, or service.
Assuming hardware replacement preserves entitlements automatically: Confirm the permitted transfer or replacement process before changing equipment.
Planning an expansion or renewal? Send your Ericsson requirements for an availability and pricing review.
