Standards Conformance⚓︎
Expeto Edge (xCore) and Expeto Gateway (xRouter) are assessed item by item against the 37 3GPP and IETF specifications their network functions implement, covering the 5G System, the Evolved Packet System and the subscriber-data, security and Diameter specifications both depend on. Each statement lists every assessed clause with its normative status and the platform's support, following the conventions of a 3GPP Implementation Conformance Statement.
Support is recorded as Supported, Partial (the remark states what is and is not supported), Not supported or Not applicable. Not applicable is used only for items in an area the platform does not provide; the areas are listed under Reading the statements and in How Expeto tests, and each such item names its area. Capabilities the network function software implements beyond an Expeto deployment's default configuration are published separately under Additional network function capabilities.
The tables give, for each specification, the version assessed and the number of mandatory items by support value. Each statement records the date of its assessment and is generated from a structured source; statements are refreshed when the assessed network function changes. Specifications under Statements in preparation are being assessed and are not yet published.
5G System (5GC)⚓︎
| Specification | Title | Version | Mandatory | Supported | Partial | Not supported | Not applicable |
|---|---|---|---|---|---|---|---|
| TS 23.501 | System architecture for the 5G System (5GS) | 17.11.0 | 95 | 56 | 37 | 2 | 0 |
| TS 23.502 | Procedures for the 5G System (5GS) | 17.11.0 | 97 | 74 | 20 | 2 | 1 |
| TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS) | 17.12.0 | 431 | 327 | 65 | 35 | 4 |
| TS 29.244 | Interface between the Control Plane and the User Plane Nodes | 17.9.0 | 94 | 58 | 36 | 0 | 0 |
| TS 29.281 | General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) | 17.4.0 | 18 | 12 | 6 | 0 | 0 |
| TS 29.500 | 5G System; Technical Realization of Service Based Architecture; Stage 3 | 15.5.0 | 40 | 19 | 11 | 7 | 3 |
| TS 29.502 | 5G System; Session Management Services | 17.12.0 | 72 | 44 | 7 | 14 | 7 |
| TS 29.510 | Network Function Repository Services | 17.11.0 | 66 | 47 | 19 | 0 | 0 |
| TS 29.518 | 5G System; Access and Mobility Management Services | 17.11.0 | 77 | 49 | 27 | 0 | 1 |
| TS 33.501 | Security architecture and procedures for 5G System | 16.5.0 | 82 | 40 | 26 | 6 | 10 |
| TS 38.413 | NG Application Protocol (NGAP) | 17.6.0 | 27 | 26 | 0 | 1 | 0 |
Evolved Packet System (EPC)⚓︎
| Specification | Title | Version | Mandatory | Supported | Partial | Not supported | Not applicable |
|---|---|---|---|---|---|---|---|
| TS 23.003 | Numbering, addressing and identification | 15.3.0 | 25 | 25 | 0 | 0 | 0 |
| TS 23.007 | Restoration Procedures | 15.0.0 | 11 | 11 | 0 | 0 | 0 |
| TS 23.008 | Organization of Subscriber Data | 15.3.0 | 36 | 36 | 0 | 0 | 0 |
| TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | 15.3.0 | 98 | 92 | 3 | 1 | 2 |
| TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS) | 15.2.0 | 428 | 428 | 0 | 0 | 0 |
| TS 29.060 | GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | 15.2.0 | 99 | 99 | 0 | 0 | 0 |
| TS 29.272 (MME role) | MME and SGSN related interfaces based on Diameter protocol | 15.3.0 | 135 | 134 | 0 | 1 | 0 |
| TS 29.274 | Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | 15.3.0 | 155 | 155 | 0 | 0 | 0 |
| TS 36.412 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 signalling transport | 14.0.0 | 5 | 5 | 0 | 0 | 0 |
| TS 36.413 | S1 Application Protocol (S1AP) | 15.1.0 | 259 | 259 | 0 | 0 | 0 |
Subscriber data, security and Diameter⚓︎
| Specification | Title | Version | Mandatory | Supported | Partial | Not supported | Not applicable |
|---|---|---|---|---|---|---|---|
| TS 29.002 | Mobile Application Part (MAP) specification | 12.8.0 | 1 | 1 | 0 | 0 | 0 |
| TS 29.272 (HSS role) | MME and SGSN related interfaces based on Diameter protocol | 15.10.0 | 127 | 123 | 4 | 0 | 0 |
| TS 33.102 | 3G Security; Security architecture | 12.8.0 | 9 | 7 | 1 | 0 | 1 |
| TS 35.205 | 3G Security; Specification of the MILENAGE algorithm set: General | 12.8.0 | 3 | 3 | 0 | 0 | 0 |
| TS 35.206 | 3G Security; Specification of the MILENAGE algorithm set: Algorithm specification | 12.8.0 | 15 | 15 | 0 | 0 | 0 |
| RFC 6733 | Diameter Base Protocol | – | 72 | 72 | 0 | 0 | 0 |
Additional network function capabilities⚓︎
The network function software implements the specifications below beyond what an Expeto deployment configures by default, and the statements record that implementation. They are published so that a Mobile Network Operator planning to use one of them can see what the software provides; enabling any of them is configuration work that Expeto Product Support scopes and carries out with the MNO.
| Specification | Title | Version | Mandatory | Supported | Partial | Not supported | Not applicable |
|---|---|---|---|---|---|---|---|
| TS 23.272 | Circuit Switched (CS) fallback in Evolved Packet System (EPS) | 15.0.0 | 17 | 17 | 0 | 0 | 0 |
| TS 23.273 | 5G System (5GS) Location Services (LCS); Stage 2 | 17.11.0 | 34 | 15 | 4 | 15 | 0 |
| TS 29.118 | MME – VLR SGs interface specification | 15.2.0 | 37 | 37 | 0 | 0 | 0 |
| TS 29.168 | Cell Broadcast Centre interfaces with the Evolved Packet Core (SBc) | 14.2.0 | 45 | 45 | 0 | 0 | 0 |
| TS 29.171 | LCS Application Protocol (LCS-AP) between the MME and E-SMLC (SLs) | 14.2.0 | 40 | 40 | 0 | 0 | 0 |
| TS 29.172 | Evolved Packet Core LCS Protocol (ELP) between GMLC and MME (SLg) | 14.2.0 | 43 | 43 | 0 | 0 | 0 |
| TS 29.273 | 3GPP EPS AAA interfaces | 15.4.0 | 61 | 61 | 0 | 0 | 0 |
| TS 32.421 | Subscriber and equipment trace; Trace concepts and requirements | 14.0.0 | 10 | 10 | 0 | 0 | 0 |
| TS 32.422 | Subscriber and equipment trace; Trace control and configuration management | 15.0.0 | 29 | 29 | 0 | 0 | 0 |
| TS 32.423 | Subscriber and equipment trace; Trace data definition and management | 14.0.0 | 9 | 9 | 0 | 0 | 0 |
| TS 33.107 | Lawful interception architecture and functions | 15.1.0 | 12 | 12 | 0 | 0 | 0 |
Statements in preparation⚓︎
These specifications are being assessed. A statement is published once every item carries a support value.
| Specification | Title | Group | Status |
|---|---|---|---|
| TS 29.338 | Diameter based protocols to support SMS capable MMEs | Subscriber data, security and Diameter | S6c is supported per the HSS product documentation; the SGd statement needs the SMSC documentation. |
| TS 29.503 | Unified Data Management Services; Stage 3 | 5G System (5GC) | Unified Data Management Services; seven service-level items are assessed and the item-level assessment needs the UDM documentation. |
| TS 29.504 | Unified Data Repository Services; Stage 3 | 5G System (5GC) | Unified Data Repository Services; the item-level assessment needs the UDR documentation. |
| TS 29.509 | Authentication Server Services; Stage 3 | 5G System (5GC) | Authentication Server Services; most items are not yet assessed and the AUSF documentation is needed to complete them. |
Reading the statements⚓︎
| Status | Meaning |
|---|---|
| Mandatory | The specification requires the capability. |
| Conditional | The specification requires the capability when a stated condition applies. |
| Optional | The specification leaves the capability to the implementation. |
Clauses that carry no conformance requirement (scope, references, definitions, descriptive text) are counted on each statement and not listed.
| Support | Meaning |
|---|---|
| Supported | The capability is implemented as the specification requires. |
| Partial | The capability is implemented in part; the remark states what is and is not supported. |
| Not supported | The capability is not implemented in the current release. |
| Not applicable | The item belongs to an area the platform does not provide; the area is named in the cell and listed below. |
Areas the platform does not provide (items in them are marked Not applicable):
- voice services (VoLTE, VoNR, IMS);
- emergency services;
- network slice-specific authentication and authorization (NSSAA);
- SMS on the private radio path (SMS is tested on the public radio path, where the Expeto SMSC in xRouter serves it);
- mobility between the 4G and 5G cores of a site over the N26 interface (a combined core interworks without N26);
- non-3GPP access to the 4G and 5G cores;
- power-saving modes (eDRX, PSM);
- dynamic policy control through a PCF (N7, N15), policy being applied from the subscription profile instead;
- a Network Slice Selection Function, the AMF granting the subscribed S-NSSAIs instead;
- the visited-network side of a roaming split (V-SMF, I-SMF, V-PCF, N32), roaming subscribers being served from the home side over S6a, S8 and Gp.
Roles and peers the platform does not take (items that only concern them are marked Not applicable):
- parameters that only an SGSN or a combined MME/SGSN sends or stores;
- transfer of a UE context between AMFs (a site runs a single AMF);
- N1 and N2 information subscriptions and notifications for other consumers (LMF, NEF, SMSF).
Additional capabilities of the network function software, configured on request (their statements are published under Additional network function capabilities):
- circuit-switched fallback and the SGs interface;
- cell broadcast (SBc);
- location services (SLs, SLg, 5G LCS);
- lawful interception;
- subscriber and equipment trace;
- EPS AAA interfaces for non-3GPP access (SWx, STa, SWm, SWa, S6b).