docs: rename LAN-I to EC (Enterprise Connect) across all guides

Swisscom LAN-I has been replaced by Enterprise Connect. Update all
references in REST API Guide, RADIUS Gateway Guide and glossary.
Link the term to the official Swisscom Enterprise Connect product page.

Author: phaupt

docs/radius-interface-gateway-guide/deployment.md

@@ -36,7 +36,7 @@ Connectivity must be allowed as follows:
 
 - **RADIUS** (UDP/1812) — Requests from your NAS (e.g. VPN server) to the RIG application (or the UDP network load balancer that forwards the requests to the RIG application nodes).
 - **LDAPS** (TCP/636) — From the RIG application to your LDAP server.
-- **HTTPS** (TCP/443) — From the RIG application to the Mobile ID API endpoint at `mobileid.swisscom.com` (Internet) or `195.65.233.218` (LAN-I).
+- **HTTPS** (TCP/443) — From the RIG application to the Mobile ID API endpoint at `mobileid.swisscom.com` (Internet) or `195.65.233.218` ([EC](https://www.swisscom.ch/en/business/enterprise/offer/wireline/enterprise-connect.html)).
 - **REDIS** (TCP/6379) — Between the RIG application nodes and the Redis database cluster.
 - **HTTP** (TCP/80) — Local connectivity for the Docker health check (optional).
 
@@ -109,7 +109,7 @@ At least the following parameters must be updated in the env file:
   base64 -w 0 <MyKey.pfx>
   ```
 
-- **`Schnittstellen__MobileIdClient__Host`** — This shall be the Mobile ID API endpoint, which is either `https://mobileid.swisscom.com` (Internet) or `https://195.65.233.218` (LAN-I).
+- **`Schnittstellen__MobileIdClient__Host`** — This shall be the Mobile ID API endpoint, which is either `https://mobileid.swisscom.com` (Internet) or `https://195.65.233.218` (EC).
 
 ## Docker Compose
 
@@ -132,7 +132,7 @@ At least the following parameters must be updated in the YAML file:
   base64 -w 0 <MyKey.pfx>
   ```
 
-- **`Schnittstellen__MobileIdClient__Host`** — This shall be the Mobile ID API endpoint, which is either `https://mobileid.swisscom.com` (Internet) or `https://195.65.233.218` (LAN-I).
+- **`Schnittstellen__MobileIdClient__Host`** — This shall be the Mobile ID API endpoint, which is either `https://mobileid.swisscom.com` (Internet) or `https://195.65.233.218` (EC).
 
 How to spin up using Docker Compose — make sure that both `docker-compose.yml` and `nginx.conf` exist in the same directory before you run the command below:
 

docs/rest-api-guide/app-provider-client-integration.md

@@ -7,7 +7,7 @@ This chapter describes how an Application Provider (AP) integrates its backend w
 Before using the Swisscom Mobile ID web service, some initial provisioning steps are required.
 
 1. **The Mobile ID customer (your company) has an agreement with Swisscom:**
-   - **Connectivity** (Internet or LAN-I) between the **AP** and **Mobile ID** has been established.
+   - **Connectivity** (Internet or [EC](https://www.swisscom.ch/en/business/enterprise/offer/wireline/enterprise-connect.html)) between the **AP** and **Mobile ID** has been established.
    - The customer has delivered the **X.509 client certificate** to Swisscom (see [Create X509 Client Certificates](/rest-api-guide/create-client-certs.md)).
 
 ::: warning Firewall Whitelisting
@@ -22,17 +22,40 @@ The AP’s public source IP address (or range) must be whitelisted in the **Swis
 
 ## Endpoint Address
 
-The Swisscom Mobile ID web service is accessible through LAN-I or the Internet. If not otherwise specified, use the following default access details.
+The Swisscom Mobile ID web service is accessible through EC ([Enterprise Connect](https://www.swisscom.ch/en/business/enterprise/offer/wireline/enterprise-connect.html)) or the Internet. If not otherwise specified, use the following default access details.
 
 
 | Environment       | URL                                   |
 |-------------------|----------------------------------------|
 | **Internet**      | [https://mobileid.swisscom.com](https://mobileid.swisscom.com) |
-| **Swisscom LAN-I** | [https://195.65.233.218](https://195.65.233.218) |
+| **Swisscom EC** | [https://195.65.233.218](https://195.65.233.218) |
 
 ### Overview Access
 
-![interconnection-backend](/img/interconnection-backend.png)
+```mermaid
+flowchart LR
+  subgraph CE[Customer Environment]
+    direction TB
+    AP[AP_ID<br/>Application Provider]
+  end
+
+  FW1{{Firewall}}
+  INTERNET((Internet))
+  EC((EC))
+  FW2{{Firewall}}
+
+  subgraph ME[Mobile ID Backend]
+    direction TB
+    MSS[MSS Platform<br/>Mobile Signature Service]
+  end
+
+  AP --- FW1
+  FW1 --- INTERNET
+  FW1 --- EC
+  INTERNET --- FW2
+  EC --- FW2
+  FW2 --- MSS
+  ```
 
 ::: info
 For accessing the service endpoints the Mobile ID customer can choose between SOAP or RESTful endpoints.

docs/rest-api-guide/health-status.md

@@ -3,7 +3,7 @@
 The Mobile ID Health Status Service is a microservice for retrieving health state details about the MobileID authentication service.
 
 - **Based on**: Real end-to-end authentication tests, checked every few minutes
-- **Scope**: Different telecommunications providers, IP+ and LAN-i endpoints, and the geofencing service
+- **Scope**: Different telecommunications providers, IP+ and EC endpoints, and the geofencing service
 - **Cost**: Free of charge
 
 For more information, please visit https://digital.swisscom.com/products/mobile-id

docs/rest-api-guide/introduction.md

@@ -17,7 +17,7 @@ It is suitable for various system landscapes and meets strict regulatory require
 | **DTBD** | *Data-To-Be-Displayed* — message displayed on the mobile phone (authentication context). |
 | **DTBS** | *Data-To-Be-Signed* — equal to DTBD; the data that will be signed with the Mobile ID signing key. |
 | **JSON** | JavaScript Object Notation — text-based open standard data interchange format. |
-| **LAN-I** | Swisscom LAN-Interconnect Service (Enterprise WAN). |
+| **EC** | Swisscom [Enterprise Connect](https://www.swisscom.ch/en/business/enterprise/offer/wireline/enterprise-connect.html) (replaces the former LAN-Interconnect). |
 | **MID** | Mobile ID platform providing the mobile signature service. |
 | **MNO** | Mobile Network Operator — also called wireless service provider or carrier. |
 | **MSISDN** | Number uniquely identifying a mobile subscription in a GSM/UMTS network. |

docs/rest-api-guide/troubleshooting.md

@@ -71,7 +71,7 @@ Most initial integration issues are related to the TLS/mTLS connection setup. Un
 
 **Solutions:**
 - Use the standard endpoint URL `https://mobileid.swisscom.com` (see [Integration Steps — Endpoint Address](/rest-api-guide/app-provider-client-integration#endpoint-address)).
-- If connecting via Swisscom LAN-I, ensure hostname verification is configured for the LAN-I endpoint.
+- If connecting via Swisscom EC, ensure hostname verification is configured for the EC endpoint.
 
 ### Server Certificate Not Trusted