diff --git a/docs/DESPLIEGUES/INSTALAR open5gs CURSO2025_2026.md b/docs/DESPLIEGUES/INSTALAR open5gs CURSO2025_2026.md new file mode 100644 index 0000000..6db9557 --- /dev/null +++ b/docs/DESPLIEGUES/INSTALAR open5gs CURSO2025_2026.md @@ -0,0 +1,86 @@ +***INSTALAR open5gs CURSO2025/2026*** +\*\*Si la máquina la creamos en proxmox confirmar que Processor→Type→host +1-Instalamos docker y portainer +Accedemos a [https://github.com/Tknika/5g-kutxa-ansible/tree/portainer](https://github.com/Tknika/5g-kutxa-ansible/tree/portainer) +Ejecutamos los pasos indicados: + Instalamos ansible: sudo apt update && sudo apt install \-y ansible git + Instalamos docker y portainer: +sudo ansible-pull \-U https://github.com/Tknika/5g-kutxa-ansible.git \--checkout portainer \-i localhost, +reboot(para meterlo en el grupo) +Comprobamos que está correcto: docker ps o https://localhost:9443 + +2-Instalamos open5gs +Accedemos: [https://github.com/herlesupreeth/docker\_open5gs](https://github.com/herlesupreeth/docker_open5gs) + +Descargamos su repositorio: +Instalar git: sudo apt install git +Clonamos repositorio: git clone [https://github.com/herlesupreeth/docker\_open5gs](https://github.com/herlesupreeth/docker_open5gs) + +Descargamos las imágenes: (En este caso solamente open5gs, no descargamos IMS…) +docker pull ghcr.io/herlesupreeth/docker\_open5gs:master +docker tag ghcr.io/herlesupreeth/docker\_open5gs:master docker\_open5gs + +docker pull ghcr.io/herlesupreeth/docker\_grafana:master +docker tag ghcr.io/herlesupreeth/docker\_grafana:master docker\_grafana + +docker pull ghcr.io/herlesupreeth/docker\_metrics:master +docker tag ghcr.io/herlesupreeth/docker\_metrics:master docker\_metrics + +Levantamos el docker compose que necesitemos: +1- Accedemos al .env para realizar los cambios necesarios: +MNC, MCC, TAC +DOCKER\_HOST\_IP: La IP del PC donde estamos realizando la instalación +Para aplicar los cambios: Guardar y ejecutar: +set \-a +source .env +2-Para levantar un 5G completo levantaremos el fichero sa-deploy.yaml: + docker compose \-f sa-deploy.yaml up \-d +Comprobamos que está correcto: Acceder a portainer y visualizar todos los contenedores levantados. + +***ROAMING open5gs CURSO2025/2026*** + +Para poder trabajar con varias radios en la misma aula: +Trabajamos con el core y la radio en un PLMN(Ej. 00110\) pero nos conectamos con un movil en la 00101 + +1-Conectamos core y radio (PLMN:00110) +2-Agregamos en webui el usuario: 00101 … +3-Configuramos el nrf.yaml: +![][image1] + +***SEPARAR UPF open5gs CURSO2025/2026*** + +PC dónde teníamos el UPF instalado: +1-Copiamos el fichero sa-deploy.yaml y le llamamos core-sinUPF.yaml +En el fichero core-sinUPF.yaml: + +- Comentamos o borramos toda la parte de upf: +- Agregamos “ports” “"8805:8805/udp” en el SMF + +EN el fichero .env: + +- DOCKER\_HOST\_IP=IP del core +- UPF\_IP=IP del UPF +- UPF\_ADVERTISE\_IP=IP del UPF + +Levantamos el docker compose que necesitemos: + docker compose \-f core-sinUPF.yaml up \-d + +PC dónde tendremos el UPF instalado: +1-Copiamos el fichero sa-deploy.yaml y le llamamos UPF2.yaml +En el fichero UPF2.yaml: + +- Comentamos o borramos todo menos la parte de upf: +- En network lo ponemos modo host +- Borramos la parte de sysctls: + +En el fichero .env: + +- DOCKER\_HOST\_IP=IP del UPF +- UPF\_IP=IP del UPF +- UPF\_ADVERTISE\_IP=IP del UPF +- SMF\_IP=IP del core + +Levantamos el docker compose que necesitemos: + docker compose \-f UPF2.yaml up \-d + +[image1]: img/open5gs_image1.png \ No newline at end of file diff --git a/docs/DESPLIEGUES/Pasos a realizar_Comandos_NETWORK SLICING.md b/docs/DESPLIEGUES/Pasos a realizar_Comandos_NETWORK SLICING.md new file mode 100644 index 0000000..b86f2aa --- /dev/null +++ b/docs/DESPLIEGUES/Pasos a realizar_Comandos_NETWORK SLICING.md @@ -0,0 +1,102 @@ +# NETWORK SLICING + +SST= Qué es +SD= Quién es + +| Valor SST | Nombre | Descripción | +| :---- | :---- | :---- | +| **1** | **eMBB** | Banda ancha móvil mejorada (lo que usas para **Internet**). | +| **2** | **URLLC** | Comunicaciones de ultra-baja latencia (coches autónomos, cirugía remota). | +| **3** | **MIoT** | Internet de las cosas masivo (sensores de ciudades inteligentes). | +| **4** | **V2X** | Vehículo con todo (comunicaciones viales). | +| **5** | **HMTC** | Comunicaciones tipo máquina de alto rendimiento. | + +Vamos a utilizar 2 SSTs pero podríamos usar el mismo SST y cambiar el SD. +Vamos a realizar 3 prácticas: + +1. **Velocidad y Ancho de Banda** +2. **Latencia (Tiempo de respuesta)** +3. **Seguridad** + +**1\. Velocidad y Ancho de Banda** +Para lograr que cada "rodaja" tenga capacidades de rendimiento distintas, debes configurar los parámetros de QoS (Quality of Service) y AMBR (Aggregate Maximum Bit Rate) dentro del núcleo de Open5GS. + +En el repositorio de herlesupreeth, los archivos YAML ya separan el tráfico por SMF/UPF, pero la "magia" de las velocidades se define en la base de datos del suscriptor (HSS/UDM) a través de la WebUI. + +1\. Diferenciar Ancho de Banda (AMBR) + +El AMBR limita la velocidad máxima total del usuario para esa sesión PDU. Para tu caso: + +* Slice Internet: Configura un APN-AMBR alto en Downlink (ej. 100 Mbps) y moderado en Uplink (ej. 20 Mbps). +* Slice Private (Streaming): Configura un APN-AMBR con prioridad en el Uplink (ej. 50 Mbps de subida) para soportar el flujo de las cámaras. + +Cómo hacerlo: + +En la Open5GS WebUI, edita el suscriptor y en la sección de Slices, añade dos configuraciones de sesión distintas para cada S-NSSAI (SST/SD): + +* Slice 1 (Internet): SST 1-\> AMBR DL: 100Mbps, UL: 20Mbps. +* Slice 2 (Private): SST 1-\> AMBR DL: 10Mbps, UL: 50Mbps. + +**Al hacerlo desde webui no me funciona, entro en la consola de UPF y ejecuto:** + +tc qdisc add dev ogstun root tbf rate 5mbit burst 32kbit lat 400ms + +Consigo limitar: *Limitamos el tráfico que va hacia el móvil (Downlink) a 5Mbps para que se note el cambio* +*\# 'ogstun' es la interfaz de túnel de Open5GS* +**Si borro e inicializo el contenedor deja de tener efecto la limitación.** + +**2\. Latencia (Tiempo de respuesta)** + +**Diferenciar Latencia y Prioridad (5QI)** + +La latencia se gestiona mediante el identificador 5QI (5G QoS Identifier). Cada valor de 5QI tiene estandarizados retardos máximos y prioridades: + +* Internet: Usa 5QI 9 (Tráfico por defecto, retardo admisible de 300ms). +* Private/Streaming: Usa 5QI 4 (Garantizado, ideal para video streaming con retardo de 150ms) o incluso 5QI 1 si quieres simular servicios de misión crítica. + +***Implementación:*** +*Creamos dos casos el de APN internet (uso “normal”) y el de APN private (uso “Video Streaming”)* +Paso 1: Configuración de Señalización (WebUI) +Primero, definiremos los perfiles en el Core para que el móvil "sepa" qué tipo de tráfico está cursando. + +1. Accede a la Open5GS WebUI. +2. En el suscriptor (IMSI) de tus móviles, busca la sección de Slices: +1. Slice Internet (SST:1): En la configuración de la sesión PDU, asegúrate de que el 5QI sea 9\. Este es el valor Non-GBR (prioridad baja) estándar para internet. +2. Slice Private (SST:2): Cambia el 5QI a 4\. Este valor indica a la red que es tráfico de Video Streaming (Buffered) con mayor prioridad y menores requisitos de retardo. + +Paso 2: Implementación de Latencia Real (UPF) +Como vimos, la Baicells y los móviles podrían ignorar el 5QI a nivel físico. Para que el alumno vea la diferencia al hacer un ping, aplicaremos el retardo en el UPF. +Accedemos a la consola del contenedor del upf-internet: +tc qdisc add dev ogstun root netem delay 100ms 10ms +Accedemos a la consola del contenedor del upf-private: +tc qdisc add dev ogstun root netem delay 5ms + +Paso 3: Verificación en el Curso (Móviles Reales) +***Prueba de Latencia (Ping):*** + +* Desde el móvil en Slice Internet: ping 8.8.8.8 -\> Deberían ver latencias de \>150ms. +* Desde el móvil en Slice Private: ping 8.8.8.8 -\> Deberían ver latencias mucho menores (la base de la radio \+ 5ms). + +***Explicación:*** + +* En una red comercial, el 5QI 4 le diría a la Baicells que ese móvil tiene prioridad en la cola de radio frente al de 5QI 9\. +* Al no tener un "Scheduler" activo en la radio que respete esto, el UPF con tc netem es nuestra herramienta para emular ese comportamiento de red extremo a extremo. + +**3\. Aislamiento de Red (Seguridad del Slice)** + +El objetivo es que el Móvil 1 (Internet) navegue “por todo el mundo” o zona que definamos, mientras que el Móvil 2 (Private) esté "atrapado" en un entorno seguro donde solo puede ver la cámara de streaming. + +En el repositorio de Herle, cada slice tiene su propio contenedor UPF. Esto nos permite aplicar reglas de firewall (iptables) de forma independiente. + +| Slice | Política de Seguridad | Resultado esperado | +| :---- | :---- | :---- | +| **Internet** | Open Policy | Navegación libre (Google, YouTube, etc.) | +| **Private** | Walled Garden | **Solo** acceso a la IP de la Cámara / Servidor. | + +En el contenedor upf-private, bloquea el acceso a una IP externa (ej. Google) pero permite el acceso a tu servidor local de cámaras: +bash +*\# Dentro del contenedor upf-private* +iptables \-A FORWARD \-d 8.8.8.8 \-j DROP + +El alumno verá que el móvil en el slice de internet puede hacer ping 8.8.8.8, pero el móvil en el slice de cámaras no, aunque ambos estén conectados a la misma antena Baicells. + diff --git a/docs/DESPLIEGUES/img/open5gs_image1.png b/docs/DESPLIEGUES/img/open5gs_image1.png new file mode 100644 index 0000000..7998561 Binary files /dev/null and b/docs/DESPLIEGUES/img/open5gs_image1.png differ diff --git "a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/Instalaci\303\263n y configuraci\303\263n de la SDR Pluto y Soft Satsagen.md" "b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/Instalaci\303\263n y configuraci\303\263n de la SDR Pluto y Soft Satsagen.md" new file mode 100644 index 0000000..f1f0366 --- /dev/null +++ "b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/Instalaci\303\263n y configuraci\303\263n de la SDR Pluto y Soft Satsagen.md" @@ -0,0 +1,93 @@ + + +**Manual de instalación y configuración de la SDR Pluto y Soft Satsagen** + +**Instalación de la SDR Pluto para uso con Windows:** + +En primer lugar, antes de conectar la SDr al PC será necesario instalar los drivers: +Driver para windows: +[**PlutoSDR-M2k-USB-Drivers.exe**](https://github.com/analogdevicesinc/plutosdr-m2k-drivers-win/releases/download/v0.9/PlutoSDR-M2k-USB-Drivers.exe) + +Una vez instalados los drivers, se conecta la SDR al PC y comprobamos que Windows reconoce el dispositivo y lo identifica. + +**Instalación del sofware Satsagen para uso con Windows:** + +Se procede a la descarga del software de la página: + +[**http://www.albfer.com/satsagen-download-page/\#content**](http://www.albfer.com/satsagen-download-page/#content) + +Y a continuación se ejecuta el instalador: + +**![][image1]** + +Se procede a su encendido (Pulsar “Power” y después “Spectrum”): + +**![][image2]** + +**![][image3]** + +**Ampliación de frecuencias hasta 6GHz:** + +1. Si aún no lo tiene, descargue el software de emulación de terminal PuTTY de [putty.org](http://putty.org/) . +2. Conecte su PlutoSDR en el puerto USB. +3. Abra el Administrador de dispositivos de Windows y expanda la entrada Puertos (COM y LPT). Tome nota de qué puerto COM está utilizando la consola serie PlutoSDR. En la captura de pantalla, el nuestro está usando COM7. Cierre el administrador de dispositivos después. + +![][image4] + +4. Abra PuTTY y seleccione el botón 'serie'. +5. En 'Línea serie', escriba el puerto COM que está utilizando PlutoSDR. En nuestro caso escribimos COM7. + + ![][image5] +6. Presiona Abrir y deberías ser recibido con una pantalla de inicio de sesión. + +7. Inicie sesión con las credenciales de usuario: root, contraseña: analog. + +![][image6] + +**¿Cómo conocer la versión?.** Escribimos por comando: + +**\#fw\_printenv attr\_name** + +respuesta: attr\_name=compatible + +**\# fw\_printenv attr\_val** + +**respuesta: attr\_val=ad9364** + +![][image7] + +![][image8] +Para cambiarlo a otra opción (ad9361 por ejemplo): +\# **fw\_setenv attr\_name compatible** +\# **fw\_setenv attr\_val ad9361** + +**BÚSQUEDA DE FRECUENCIAS EN EL ESPECTRO:** +Búsqueda de la radio o otra cosa: + +Búsqueda de wifi en 2,4GHz: + +![][image9] + +Búsqueda de wifi en 5GHz: + +![][image10] + +[image1]: img/image1.png + +[image2]: img/image2.png + +[image3]: img/image3.png + +[image4]: img/image4.png + +[image5]: img/image5.png + +[image6]: img/image6.png + +[image7]: img/image7.png + +[image8]: img/image8.png + +[image9]: img/image9.png + +[image10]: img/image10.png \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image1.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image1.png new file mode 100644 index 0000000..784f711 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image1.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image10.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image10.png new file mode 100644 index 0000000..1263537 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image10.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image2.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image2.png new file mode 100644 index 0000000..76a35af Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image2.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image3.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image3.png new file mode 100644 index 0000000..d8800d2 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image3.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image4.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image4.png new file mode 100644 index 0000000..9b5e2c5 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image4.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image5.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image5.png new file mode 100644 index 0000000..394f864 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image5.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image6.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image6.png new file mode 100644 index 0000000..a9b6228 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image6.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image7.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image7.png new file mode 100644 index 0000000..b60d5a0 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image7.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image8.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image8.png new file mode 100644 index 0000000..2f6d790 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image8.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image9.png b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image9.png new file mode 100644 index 0000000..ef484a8 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL ANALIZADOR DE ESPECTRO/img/image9.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/CONFIGURAR LAS SIMs DE OPEN-CELL.md b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/CONFIGURAR LAS SIMs DE OPEN-CELL.md new file mode 100644 index 0000000..c9da4f8 --- /dev/null +++ b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/CONFIGURAR LAS SIMs DE OPEN-CELL.md @@ -0,0 +1,49 @@ + +**CONFIGURACIÓN DE LAS SIMs DE OPEN-CELL** + +Visitamos la web con el siguiente enlace: + +[https://open-cells.com/](https://open-cells.com/) + +[https://open-cells.com/index.php/sim-cards/](https://open-cells.com/index.php/sim-cards/) + +Con el desarrollo de la siguiente aplicación se puede leer/escribir en la SIM: +![][image1] + +Accedemos a la siguiente página web para buscar al final de ella el enlace para la descarga del programa (source code): + +[https://open-cells.com/index.php/uiccsim-programing/](https://open-cells.com/index.php/uiccsim-programing/) + +A continuación vamos a la carpeta de “descargas” y descomprimimos el fichero para tener el ejecutable. +![][image2]A continuación abrimos un “terminal”, nos movemos hasta la carpeta que contiene el fichero ejecutable y ponemos: + +**sudo ./program\_uicc** + +Se produce un error con la última versión de la aplicación (si instalamos la versión 2.5 no ocurre). + +Seguimos con el tutorial. Insertamos el lector/grabador con una SIM y procedemos a leerla: +**sudo DEBUG=y ./program\_uicc** + +Se puede consultar la ayuda en línea mediante el comando: +sudo ./program\_uicc \--help + +Una configuración típica sería: + +sudo ./program\_uicc \--adm 12345678 \--imsi 208920100001101 \--isdn 00000001 \--acc 0001 \--key 6874736969202073796d4b2079650a73 \--opc 504f20634f6320504f50206363500a4f \--spn "OpenCells01" \--authenticate \--noreadafter + +Es importante el parámetro “adm” que es el valor de 8 dígitos que viene grabada en la propia SIM de forma visual: + +P**ara corregir el error**: ./program\_uicc: /lib/x86\_64-linux-gnu/libstdc++.so.6: version \`GLIBCXX\_3.4.29' not found (required by ./program\_uicc) + +sudo add-apt-repository ppa:ubuntu-toolchain-r/test +sudo apt-get update +sudo apt-get install gcc-4.9 +sudo apt-get upgrade libstdc++6 +After this is complete, make sure to run the following: +sudo apt-get dist-upgrade +Also, make sure to confirm the necessary dependencies are installed for the right GLIBCXX version. +strings /usr/lib/x86\_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX + +[image1]: img/opencell_image1.png + +[image2]: img/opencell_image2.png \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/CONFIGURAR LAS SIMs DE SYSMOCOM.md b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/CONFIGURAR LAS SIMs DE SYSMOCOM.md new file mode 100644 index 0000000..90bb480 --- /dev/null +++ b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/CONFIGURAR LAS SIMs DE SYSMOCOM.md @@ -0,0 +1,37 @@ + +**CONFIGURACIÓN DE LAS SIMs DE SYSMOCOM** + + Pasos para instalar el programa pySIM ([https://github.com/osmocom/pysim](https://github.com/osmocom/pysim)): + +* Descargamos el código fuente a una carpeta local (en el ordenador en el que vayamos a conectar el lector de tarjetas SIM por USB): + * git clone [https://github.com/osmocom/pysim](https://github.com/osmocom/pysim) +* Nos movemos a la carpeta correspondiente: + * cd pysim +* Creamos un entorno virtual de Python (Virtual Environment) para aislar las dependencias y lo activamos: + * sudo apt-get install \--no-install-recommends pcscd libpcsclite-dev python3 python3-setuptools python3-pyscard python3-pip + * sudo apt install python3.8-venv + * python3 \-m venv venv + * source venv/bin/activate + * Nos aseguramos de que aparece el entorno activado (venv entre paréntesis) ![][image1] +* Instalamos las dependencias definidas por el proyecto en el fichero requirements.txt: + * pip install \-r requirements.txt +* Ejecutamos la shell del programa + * ./pySim-shell.py \-p 0 (el parámetro 0 es importante si se tiene más de un lector conectado en el ordenador) +* Antes de nada, vamos a verificar que el ADM de la SIM introducida es la correcta: + * verify\_adm 38235251 + * Si el comando no devuelve a nada, es que el ADM es correcto + + + OPCIONES PARA PROGRAMAR: + + [https://osmocom.org/projects/pysim/wiki/PySim-prog](https://osmocom.org/projects/pysim/wiki/PySim-prog) + + + apt install python3.12-venv + + + + + + +[image1]: img/sysmocom_image1.png \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/opencell_image1.png b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/opencell_image1.png new file mode 100644 index 0000000..40056b8 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/opencell_image1.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/opencell_image2.png b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/opencell_image2.png new file mode 100644 index 0000000..900a2a4 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/opencell_image2.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/sysmocom_image1.png b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/sysmocom_image1.png new file mode 100644 index 0000000..0ebcd65 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL CONFIGURAR SIMs/img/sysmocom_image1.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/Data Sheet Stellar227 gNB .md b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/Data Sheet Stellar227 gNB .md new file mode 100644 index 0000000..ca10465 --- /dev/null +++ b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/Data Sheet Stellar227 gNB .md @@ -0,0 +1,224 @@ +**Stellar227** + +Indoor 5G Base Station Datasheet ![][image1]![][image2] +![][image3]![][image4] + +**INTRODUCTION** + +The Baicells Stellar227 is an advanced indoor 5G Sub 6G integrated base station (gNB), which is designed and developed based on Qualcomm 5G SoC solution. This 2x250mW gNB is low power, subminiature and easy to maintenance. + +This product helps operators to enhance the coverage performance of 5G networks effectively, improve the capacity of 5G networks and eliminate the blind district, meanwhile it also can help to reduce the system power consumption. + +This product comes with a standard one-year warranty; an extended warranty is available.s +**HIGHLIGHTS** + +*NOTE: Features can vary based on model or region.* • Standard NR Band n78/n41/n48 +• Comply with 3GPP Release 15 and Release 16 • GUI-based local and remote Web management • Supports 100MHz bandwidth per cell • Peak rate: Up to DL 850Mbps\* and UL 600Mbps • Supports 128 RRC connected users per cell • Supports Stand Alone (SA) mode + +• Supports F1 setting\* + +• Supports SCTP control (IKE SCTP) + +• Supports embedded 5G core network (HaloB) • Integrated small cell form factor for quick and easy installation + +• Supports flexible xHaul + +• Highly secured with equipment certification against potential intrusion risk + +• Supports TR-069 network management interface • Lower power consumption, which reduces OPEX \* Planned for future release + +www.baicells.com | 400-108-0167 | contact@baicells.com | BaiBNQ\_2.5.x | Document version: 01 +**Stellar227** + +Indoor 5G Base Station Datasheet + +**TECHNOLOGY** + +Standard 5G NR TDD (3GPP R15 & R16 compliant) + +TDD UL/DL Configuration 5ms periodicity (μ=1): DDDDD+DDSUU + +5ms periodicity (μ=1): DDDDD+SUUUU\* + +2.5ms dual periodicity (μ=1): DDDSU+DDSUU + +2.5ms single periodicity (μ=1): DDDSU\*, DSUUU + +Frequency Band n41 (2496 MHz – 2690 MHz) + +n48 (3550 MHz – 3700 MHz) + +n78 (3300 MHz – 3800 MHz) + +Channel Bandwidth n41: 100MHz + +n48: 10/20/30/40MHz + +n78: 10/20/30/40/50/60/80/90/100MHz + +Multiplexing 2x2 MIMO (DL) + +Security Radio: SNOW 3G/AES-128 + +Backhaul: IPsec (X.509 AES-128, AES-256, SHA-128, SHA-256) + +\* Planned for future release + +**INTERFACE** + +Ethernet Interface 1 x RJ-45 Ethernet interface (1 GE) + +1 x 1GE optical interface (SFP) or 10GE optical interface (SFP+) + +Power Supply 12VDC/POE++ + +Protocols Used IPv4, UDP, TCP, ICMP, NTP, SSH, IPsec, TR-069, HTTP/HTTPs, DHCP Network Management IPv4, HTTP/HTTPs, TR-069, SSH, Embedded EPC + +VLAN/VxLAN\* 802.IQ/VxLAN + +LED Indicators 4 x status LED + +PWR/ACT/RUN/ALM + +RF Antenna Embedded omni antenna or 2T2R external high gain antenna with SMA connectors + +GPS Antenna External GPS antenna, SMA connector + +\* Planned for future release + +**PERFORMANCE** + +| 100 MHz | DL (Mbps) | +| :---- | ----- | +| 5ms periodicity (DDDDD+DDSUU, 6:4:4) | 850 | + +Peak Data Rate UL (Mbps) with UL256QAM + +210 + +www.baicells.com | 400-108-0167 | contact@baicells.com | BaiBNQ\_2.5.x | Document version: 01 +**Stellar227** + +Indoor 5G Base Station Datasheet + +| 5ms periodicity (DDDDD+SUUUU, 6:4:4)\* | 525 | +| :---- | :---- | +| 2.5ms dual periodicity (DDDSU+DDSUU, 10:2:2) | 720 | +| 2.5ms single periodicity (DDDSU, 10:2:2)\* | 850 | +| 2.5ms single periodicity (DSUUU, 10:2:2) | 380 | + +400 + +330 + +210 + +600 + +User Capacity Up to 128 RRC connected users + +Maximum Deployment Range 2000m2 + +Latency Round-trip delay (RTD) less than 10 milliseconds Receive Sensitivity \-92 dBm (per channel) + +Modulation UL: MCS0 (QPSK) to MCS27 (256QAM) + +DL: MCS0 (QPSK) to MCS27 (256QAM) + +Transmit Power Range 0 to 24 dBm per channel (combined 27dBm, configurable) (1 dB interval) Quality of Service Nine-level priority indicated by QoS Class Identifiers (QCI) ARQ/HARQ Supported + +Synchronization GPS/NL/1588v2 + +**FEATURES** + +Voice VoNR/EPS-FB + +SON\* Self-Organizing Network + +• Automatic Neighbor Relation (ANR) + +• PCI confliction detection + +Traffic Offload Local breakout + +Maintenance • Local/Remote Web maintenance + +• Online status management + +• Performance statistics + +• Fault management + +• Local/Remote software upgrade + +• Logging + +• Connectivity diagnosis + +• Auto startup + +www.baicells.com | 400-108-0167 | contact@baicells.com | BaiBNQ\_2.5.x | Document version: 01 +**Stellar227** + +Indoor 5G Base Station Datasheet + +**LINK BUDGET** + +VSWR \<= 1.5 + +EIRP Antenna gain \= 4 dBi + +EIRP= (27+4)dBm/100MHz + +Power Control UL Open-loop/Closed-loop Power Control, DL Power Allocation (3GPP TS 38.213 compliant)\* + +\* Planned for future release + +**PHYSICAL** + +Surge Suppression Yes + +Power Interface Lightning Protection +Differential mode: ±10 KA Common mode: ±20 KA + +MTBF ≥ 150000 hours + +MTTR ≤ 1 hour + +Ingress Protection Rating IP30 + +Operating Temperature \-5°C to 45°C + +Storage Temperature \-20°C to 65°C + +Humidity 15% to 85% RH + +Atmospheric Pressure 70 kPa to 106 kPa + +Power Consumption Maximum 30W + +Weight \< 2.4 lbs/ 1.1kg + +Dimensions (HxWxD) 7.9 X 7.9 X 1.9 inches / 200 X 200 X 49 millimeters + +Installation Ceiling, wall or T-bar mount + +**GLOBAL PART NUMBERS** + +BSC7078A227 Stellar227 indoor 5G NR TDD gNB – n78(3300MHz-3800MHz),2T2R,2\*250mW, 12VDC/POE++, internal antenna, 1\*RJ45+1\*(GE/10GE)OPT) + +BSC7041A227 Stellar227 indoor 5G NR TDD gNB – n41(2496 MHz-2690 MHz),2T2R,2\*250mW, 12VDC/POE++, internal antenna, 1\*RJ45+1\*(GE/10GE)OPT) + +BSC7048A227 Stellar227 indoor 5G NR TDD gNB – n48(3550 MHz \-3700 MHz),2T2R,2\*250mW, 12VDC/POE++, internal antenna, 1\*RJ45+1\*(GE/10GE)OPT) + +NOTE: Customized versions can be requested. + +www.baicells.com | 400-108-0167 | contact@baicells.com | BaiBNQ\_2.5.x | Document version: 01 + +[image1]: img/datasheet_image1.png + +[image2]: img/datasheet_image2.png + +[image3]: img/datasheet_image3.png + +[image4]: img/datasheet_image4.png \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/MANUAL BAICELLS 5G.docx.md b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/MANUAL BAICELLS 5G.docx.md new file mode 100644 index 0000000..fff885b --- /dev/null +++ b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/MANUAL BAICELLS 5G.docx.md @@ -0,0 +1,68 @@ +**MANUAL** + +**[1\. Configuración inicial: 2](#configuración-inicial:)** + +[**2\. Información básica: 2**](#información-básica:) + +[**3\. Configuración: 3**](#configuración:) + +[3.1 Configuración radio 3](#3.1-configuración-radio) + +[3.2 Configuración conexión a core 3](#3.2-configuración-conexión-a-core) + +1. # **Configuración inicial:** {#configuración-inicial:} + +Para acceder a la radio desde la LAN: accedemos desde 192.168.150.7 +Configuramos la WAN \-\> DHCP y recibimos una IP del router: 192.168.168.225 +(podemos acceder desde nuestra red por esta IP también) +**![][image1]** + +2. # **Información básica:** {#información-básica:} + +Acceso rápido para el estado del gNB y de los UE conectados. + +**![][image2]** + +3. # **Configuración:** {#configuración:} + +## ***3.1 Configuración radio*** {#3.1-configuración-radio} + +Para configurar la radio accedemos a “Quick Setting” +![][image3] + +Configurar parámetros radio y del gNB + +* Banda de trabajo +* Ancho de banda +* Frecuencia (ARFCN) +* PCI: Physical Cell ID + +## ***3.2 Configuración conexión a core*** {#3.2-configuración-conexión-a-core} + +Para configurar la conexión con el core: +NR Setting → Advanced → CU +![][image4] + +1- Egtpu Local IP: Agregamos la IP de la radio +2- Le damos al “+” y conbfiguramos:![][image5] +AMF IP: IP del core +NGAP Local IP: IP de la radio +PLMN: Elegimos la misma que tenemos en el core. +\*Si no aparece tendremos que ir a pestaña PLMN +Open→ Add +Aquí también podemos configurar los slices +![][image6] + +*Podemos comprobar la conexión en la pestaña “Basic info”* + +[image1]: img/manual_image1.png + +[image2]: img/manual_image2.png + +[image3]: img/manual_image3.png + +[image4]: img/manual_image4.png + +[image5]: img/manual_image5.png + +[image6]: img/manual_image6.png \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/Manual OFICIAL gNB Baicells - Stellar227 Indoor Installation Guide.md b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/Manual OFICIAL gNB Baicells - Stellar227 Indoor Installation Guide.md new file mode 100644 index 0000000..8f84e7e --- /dev/null +++ b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/Manual OFICIAL gNB Baicells - Stellar227 Indoor Installation Guide.md @@ -0,0 +1,377 @@ +**Stellar227** + +Indoor 2x250mW gNB **Installation Guide** + +All rights reserved © Baicells Technologies Co., Ltd. Document version: 01 + +**About This Document** +**![][image1]** + +This document is intended for personnel who will be installing the Baicells Stellar227 Indoor 2x250mW gNB product. The product overview is followed by the procedures for properly installing. Please be advised that only personnel with the appropriate electrical skills and experience should install this device. + +**Copyright Notice** + +Baicells Technologies, Inc., copyrights the information in this document. No part of this document may be reproduced in any form or means without the prior written consent of Baicells Technologies, Inc. + +**Disclaimer** + +The information in this document is subject to change at any time without notice. For more information, please consult with a Baicells technical engineer or the support team. + +**Disposal of Electronic and Electrical Waste** + +Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product. + +**Revision Record** + +| Date | Version | Description | +| ----- | ----- | ----- | +| 30 Dec., 2023 | 01 | Initial Released. | +| | | | +| | | | + +**Contact Us** + +| | Baicells Technologies Co., Ltd. | Baicells Technologies North America, Inc. | +| ----- | ----- | ----- | +| | China | North America | +| Address | 9-10F, 1st Bldg., No.81BeiqingRoad, Haidian District, Beijing, China | 555 Republic Dr., \#200, Plano, TX 75074, USA | +| Phone | 400-108-0167 | \+1-888-502-5585 | +| Email | contact@Baicells.com or support@Baicells.com | sales\_na@Baicells.com or support\_na@Baicells.com | +| Website | www.Baicells.com | https://na.Baicells.com | + +![][image2] + +**Safety Information** + +For the safety of installation personnel and for the protection of the equipment from damage, please read all safety warnings. If you have any questions concerning the warnings, before installing or powering on the base station contact the Baicells support team. + +![][image3]**Warning ![][image4]**IMPORTANT SAFETY INSTRUCTIONS + +This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. + +![][image5]**Warning ![][image6]**Read the installation instructions before you connect the system to its power source. + +![][image7]**Warning ![][image8]**Installation of the equipment must comply with local and national electrical codes. + +![][image9]**Warning ![][image10]**This product relies on the existing building or structure for short-circuit (overcurrent) protection. Ensure that the protective device is rated no greater than 20A. ![][image11]**Warning ![][image12]**Do not operate this wireless network device near unshielded blasting caps or in an explosive environment unless the device has been modified and qualified for such use. + +Table of Contents +![][image13] + +1\. Overview..................................................................................................................1 ![][image14]Introduction ................................................................................................................ 1 Highlights..................................................................................................................... 1 Appearance ................................................................................................................. 2 Technical Specification................................................................................................ 3 + +1.4.1 Technology .......................................................................................................... 3 1.4.2 Interface .............................................................................................................. 3 1.4.3 Performance........................................................................................................ 4 1.4.4 Features............................................................................................................... 5 1.4.5 Link Budget.......................................................................................................... 5 1.4.6 Physical................................................................................................................ 5 +2\. Installation Preparation ..........................................................................................7 Packing List.................................................................................................................. 7 Support Materials...................................................................................................... 7 Installation Tools....................................................................................................... 7 Construction Safety..................................................................................................... 7 Installation Environment............................................................................................. 8 +3\. Installation................................................................................................................9 Ceiling or Wall Mounting ............................................................................................ 9 Connect Cables..........................................................................................................10 Power on to Check LED Status..................................................................................11 + +List of Figures + +Figure 1-1 Stellar227 Appearance ............................................................................2 + +List of Tables + +Table 1-1 Stellar227 Interface Description ................................................................2 Table 1-2 Stellar227 Interface Indicators...................................................................2 Table 2-1 Supporting Materials .................................................................................7 + +**1.Overview** + +Introduction + +The Baicells Stellar227 is an advanced indoor 5G Sub-6G integrated base station (gNB), which is designed and developed based on Qualcomm 5G SoC solution. This 2x250mW gNB is low power, subminiature and easy to maintenance. + +This product helps operators to enhance the coverage performance of 5G networks effectively, improve the capacity of 5G networks and eliminate the blind district, meanwhile it also can help to reduce the system power consumption. + +Highlights + +• Standard NR Band n78/n41/n48 + +• Comply with 3GPP Release 15 and Release 16 + +• GUI-based local and remote Web management + +• Supports 100MHz bandwidth per cell + +• Peak rate: Up to DL 850Mbps\* and UL 600Mbps + +• Supports 128 RRC connected users per cell + +• Supports Stand Alone (SA) mode + +• Supports F1 setting\* + +• Supports SCTP control (IKE SCTP) + +• Supports embedded 5G core network (HaloB) + +• Integrated small cell form factor for quick and easy installation • Supports flexible xHaul + +• Highly secured with equipment certification against potential intrusion risk • Supports TR-069 network management interface + +• Lower power consumption, which reduces OPEX + +\* Planned for future release + +1 + +Appearance + +The appearance of Stellar227 is shown in Figure 1-1. + +Figure 1-1 Stellar227 Appearance + + + +The Stellar227 interfaces are described in Table 1-1. + +Table 1-1 Stellar227 Interface Description + +| Interface | Description | +| ----- | ----- | +| PWR | 12VDC power supply interface | +| LAN | RJ-45 interface (GE), used for initial configuration or maintenance during device operation | +| WAN/POE++ | RJ-45 interface (GE), used for data backhaul and PoE++ power supply, complied with IEEE 802.3bt standard. | +| SFP | Optical interface (SFP) 0, used for data backhaul | +| GPS | External GPS antenna interface 1, SMA (F) connector | +| RST | Power reset button | +| ANT0 | (optional) External antenna interface 0, SMA (F) connector | +| ANT1 | (optional) External antenna interface 1, SMA (F) connector | + +The Stellar227 interface indicators are described in Table 1-2. + +Table 1-2 Stellar227 Interface Indicators + +| Identity | Color | Status | Description | +| ----: | ----: | ----: | :---: | + +2 + +| PWR | Green | Steady ON | (Reserved) | +| :---- | :---- | ----- | :---- | +| RUN | Green | Steady ON | The power supply is normal. | +| | | Fast flash: 0.125s on,0.125s off | The device is starting up. | +| | | | Slow flash: 1s on, 1s off The device is operating normally. | +| | | OFF | No power supply or device fault. | +| ACT | Green | Steady ON | The cell is active. | +| | | Slow flash: 1s on, 1s off The cell is deactivated. | | +| ALM | Red | Steady ON | The device is fault. | +| | | OFF | No alarm. | + +Technical Specification + +**1.4.1 Technology** + +| Item | Description | +| ----- | ----- | +| Standard | 5G NR TDD (3GPP R15 & R16 compliant) | +| TDD UL/DL Configuration | 5ms periodicity (μ=1): DDDDD+DDSUU 5ms periodicity (μ=1): DDDDD+SUUUU\* 2.5ms dual periodicity (μ=1): DDDSU+DDSUU 2.5ms single periodicity (μ=1): DDDSU\*, DSUUU | +| Frequency Band | n41 (2496 MHz – 2690 MHz) n48 (3550 MHz – 3700 MHz) n78 (3300 MHz – 3800 MHz) | +| Channel Bandwidth | n41: 100MHz n48: 10/20/30/40MHz n78: 10/20/30/40/50/60/80/90/100MHz | +| Multiplexing | 2x2 MIMO (DL) | +| Security | Radio: SNOW 3G/AES-128 Backhaul: IPsec (X.509 AES-128, AES-256, SHA-128, SHA-256) | + +**1.4.2 Interface** + +| Item | Description | +| ----- | ----- | +| Ethernet Interface | 2 x RJ-45 Ethernet interface (1 GE) 1 x 1GE optical interface (SFP) 1 x 10GE optical interface (SFP+) | + +3 + +| Item | Description | +| ----- | ----- | +| Power Supply | 12VDC/POE++ | +| Protocols Used | IPv4, UDP, TCP, ICMP, NTP, SSH, IPsec, TR-069, HTTP/HTTPs, DHCP | +| Network Management | IPv4, HTTP/HTTPs, TR-069, SSH, Embedded EPC | +| VLAN/VxLAN\* | 802.IQ/VxLAN | +| LED Indicators | 4 x status LED PWR/ACT/RUN/ALM | +| RF Antenna | Embedded omni antenna or 2T2R external high gain antenna with SMA connectors | +| GPS Antenna | External GPS antenna, SMA connector | + +**1.4.3 Performance** + +| Item | Description | | | +| ----- | ----- | :---: | :---: | +| Peak Data Rate | 100 MHz | DL (Mbps) | UL (Mbps) | +| | 5ms periodicity (DDDDD+DDSUU ,6:4:4) | 810 | 210 | +| | 5ms periodicity (DDDDD+SUUUU ,6:4:4)\* | 525 | 400 | +| | 2.5ms dual periodicity (DDDSU+DDSUU, 10:2:2) | 720 | 330 | +| | 2.5ms single periodicity (DDDSU, 10:2:2)\* | 850 | 210 | +| | 2.5ms single periodicity (DSUUU, 10:2:2) | 380 | 600 | +| User Capacity | Up to 128 RRC connected users | | | +| MAX Deployment Range | 2000 m2 | | | +| Latency | Round-trip delay (RTD) less than 10 milliseconds | | | +| Receive Sensitivity | \-92 dBm (per channel) | | | +| Modulation | UL: MCS0 (QPSK) to MCS27 (256QAM) DL: MCS0 (QPSK) to MCS27 (256QAM) | | | +| Transmit Power Range | 0 to 24 dBm per channel (combined 27dBm, configurable) (1 dB interval) | | | +| Quality of Service | Nine-level priority indicated by QoS Class Identifiers (QCI) | | | +| ARQ/HARQ | Supported | | | +| Synchronization | GPS/NL/1588v2 | | | + +**NOTE**: The test method of receiving sensitivity is proposed by the 3GPP TS 36.104, which is based on + +4 + +5MHz bandwidth, FRC A1-3 in Annex A.1 (QPSK, R=1/3, 25RB) standard. + +\* Planned for future release + +**1.4.4 Features** + +| Item | Description | +| ----- | ----- | +| Voice | VoNR/EPS-FB | +| SON | Self-Organizing Network • Automatic Neighbor Relation (ANR) • PCI confliction detection | +| Traffic Offload | Local breakout | +| Maintenance | • Local/Remote Web maintenance • Online status management • Performance statistics • Fault management • Local/Remote software upgrade • Logging • Connectivity diagnosis • Auto startup | + +**1.4.5 Link Budget** + +| Item | Description | +| ----- | ----- | +| VSWR | \<= 1.5 | +| EIRP | Antenna gain \= 4 dBi ERIP= (27+4)dBm/100MHz | +| Power Control | UL Open-loop/Closed-loop Power Control, DL Power Allocation (3GPP TS 38.213 compliant)\* | + +\* Planned for future release + +**1.4.6 Physical** + +| Item | Description | +| ----- | ----- | +| Surge Suppression | Yes | +| Power Interface Lightning Protection | Differential mode: ±10 KA Common mode: ±20 KA | +| MTBF | ≥ 150000 hours | +| MTTR | ≤ 1 hour | +| Ingress Protection | IP30 | + +5 + +| Item | Description | +| ----- | ----- | +| Rating | | +| Operating Temperature | \-5°C to 45°C | +| Storage Temperature | \-20°C to 65°C | +| Humidity | 15% to 85% RH | +| Atmospheric Pressure | 70 kPa to 106 kPa | +| Power Consumption | Maximum 30W | +| Weight | \< 2.4 lbs/ 1.1kg | +| Dimensions (HxWxD) | 7.9 x 7.9 x 1.9 inches / 200 x 200 x 49 millimeters | +| Installation | Ceiling or wall mount | + +6 + +**2.Installation Preparation** + +Packing List + +Before opening the box, make sure the package is in good condition, undamaged and not wet. During the unpacking, avoid potential damaging impacts from hits or excessive force. + +Once unpacked, check the contents to see if they are consistent with the packing list. Support Materials + +In addition to industry standard tools, you will need the materials described in Table 2-1 during the installation. + +Table 2-1 Supporting Materials + +| Item | Figure | Description | +| ----- | :---: | ----- | +| Optical fiber | | Optical fiber (armor) It is suggested that the diameter of the cable is 7± 1mm. | +| Ethernet cable | | Outdoor CAT6, shorter than 100 meters (\~109 yards) It is suggested that the diameter of the cable is 7± 1mm. | + +**NOTE:** Other accessories have been packed in the packing box. + +Installation Tools + +The following standard tools may be needed during the installation. + +| | | | | +| :---: | :---: | :---: | :---: | +| Marker pen | Percussion drill | Cross screw driver | hammer | + +**NOTE:** Other accessories have been packed in the packing box. + +Construction Safety + +1\. The installation personnel must master the basic safe operation knowledge, through the training, and having the corresponding qualifications. + +7 + +2\. Before installation, the installation personnel must be prepared with safety protection, such as: safety helmet, safety belt, reflective clothing, gloves, and safety shoes, etc. + +3\. Before installation, the installation personnel must cross-check each other to ensure above preparations have done. + +Installation Environment + +To get the signal coverage effect best, please place the Neutrino base station in an unobstructed space. + +8 + +**3.Installation** + +Ceiling or Wall Mounting + +**Attention:** + +• The thickness of ceiling is not less than 18mm, and bearing more than 5kgs. If the strength is not suitable, the device maybe fall off. + +• If the ceiling is made of unstable material, such as gypsum, this ceiling installation is not recommended. If the device must be installed on ceiling due to environment restriction, add one layer better panel under screws to make sure the device is fastness. + +Here take mounting on wall as an example, mounting on ceiling is the same as it. + +1\. Put the bracket against the wall and mark the position, and then drill three holes. Later install expansion pipe, bracket and tighten with screws. + +2\. Install four screw bolts on the back of the gNB and tighten these screw bolts. + +3\. Install the bracket on the back of the gNB with screws and tighten these screws. + +9 + +4\. Put the gNB from top to bottom along the slot and push it to the bottom, and then clamp the spring sheet. + +Connect Cables + +1\. Connect power adaptor to **PWR** port and the other end connects to AC power. + +2\. Connect Ethernet cable to **WAN/POE++** port and the other end connects to the web client. + +When the installation site has POE switch, the POE++ supply can be adopted. + +The POE switch should meet the POE++ requirements for the BT protocol, with a power of 30 watts or higher. + +3\. Connect optical fiber to **SFP** port and the other end connects to the gateway device. + +4\. (optional) Connect **ANT0/ANT1** to external antenna with SMA connector. By default, the built-in antennas are used. + +10 + +Power on to Check LED Status + +Power on the gNB, and wait a few minutes while the gNB boots up. Per the previous Table 1-2 in “1.3 Appearance”, check that the LED indicators are lighting as expected. + +11 + +[image1]: img/oficial_image1.png + +[image2]: img/oficial_image2.png + +[image3]: img/oficial_image3.png + +[image4]: img/oficial_image4.png + +[image5]: img/oficial_image5.png + +[image6]: img/oficial_image6.png + +[image7]: img/oficial_image7.png + +[image8]: img/oficial_image8.png + +[image9]: img/oficial_image9.png + +[image10]: img/oficial_image10.png + +[image11]: img/oficial_image11.png + +[image12]: img/oficial_image12.png + +[image13]: img/oficial_image13.png + +[image14]: img/oficial_image14.png \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image1.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image1.png new file mode 100644 index 0000000..531257b Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image1.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image2.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image2.png new file mode 100644 index 0000000..278282e Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image2.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image3.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image3.png new file mode 100644 index 0000000..dbd4f4f Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image3.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image4.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image4.png new file mode 100644 index 0000000..0168415 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/datasheet_image4.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image1.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image1.png new file mode 100644 index 0000000..105fd0c Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image1.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image2.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image2.png new file mode 100644 index 0000000..efe9514 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image2.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image3.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image3.png new file mode 100644 index 0000000..3c34c13 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image3.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image4.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image4.png new file mode 100644 index 0000000..0c805f1 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image4.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image5.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image5.png new file mode 100644 index 0000000..a99b765 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image5.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image6.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image6.png new file mode 100644 index 0000000..57ef5ab Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/manual_image6.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image1.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image1.png new file mode 100644 index 0000000..9b7f14d Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image1.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image10.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image10.png new file mode 100644 index 0000000..b884717 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image10.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image11.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image11.png new file mode 100644 index 0000000..1f969a8 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image11.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image12.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image12.png new file mode 100644 index 0000000..b884717 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image12.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image13.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image13.png new file mode 100644 index 0000000..9b7f14d Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image13.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image14.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image14.png new file mode 100644 index 0000000..eae3ab3 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image14.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image2.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image2.png new file mode 100644 index 0000000..9b7f14d Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image2.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image3.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image3.png new file mode 100644 index 0000000..1f969a8 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image3.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image4.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image4.png new file mode 100644 index 0000000..b884717 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image4.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image5.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image5.png new file mode 100644 index 0000000..1f969a8 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image5.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image6.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image6.png new file mode 100644 index 0000000..b884717 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image6.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image7.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image7.png new file mode 100644 index 0000000..1f969a8 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image7.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image8.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image8.png new file mode 100644 index 0000000..b884717 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image8.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image9.png b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image9.png new file mode 100644 index 0000000..1f969a8 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/BAICELLS-gNB/img/oficial_image9.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/MANUAL VANKOM 5G.md b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/MANUAL VANKOM 5G.md new file mode 100644 index 0000000..5e754e2 --- /dev/null +++ b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/MANUAL VANKOM 5G.md @@ -0,0 +1,73 @@ +# MANUAL VANKOM 5G + +## Índice + +- [MANUAL VANKOM 5G](#manual-vankom-5g) + - [Índice](#índice) + - [1. Configuración inicial](#1-configuración-inicial) + - [2. Información básica](#2-información-básica) + - [3. Configuración](#3-configuración) + - [3.1 Configuración conexión a core](#31-configuración-conexión-a-core) + - [3.2 Configuración celda](#32-configuración-celda) + +--- + +## 1. Configuración inicial + +Para acceder a la radio desde la LAN: accedemos desde `172.20.50.1` + +*Connect the computer to the GE interface of the base station, enter +the 172.20.50.1 (default) address in the browser to enter the LMT login +page; You can also log in by connecting the computer to the optical port +and entering the optical port address. +On the login page, you can click [Verification Code] to switch, fill +in the correct user name, password, and verification code, and click [Login] +to enter the LMT system, as shown in the figure.* + +- **Account:** admin +- **Password:** lmt_2023 + +Configuramos la WAN: + +![Configuración WAN](img/image1.png) + +--- + +## 2. Información básica + +En "Home" tenemos el estado del gNB y los datos de la celda. + +![Home gNB](img/image2.png) + +--- + +## 3. Configuración + +### 3.1 Configuración conexión a core + +Para configurar la radio accedemos a "Quick Setup" y "Guided Mode" + +- **eGTPU:** Ponemos la IP de la radio +- **AMF IP:** Ponemos la IP del core + +![Configuración core](img/image3.png) + +### 3.2 Configuración celda + +**Paso 3:** + +Podemos modificar: PCI, PLMN, SST y SD, TAC… + +> ⚠️ **Importante:** PLMN y TAC deben coincidir con los del Core +> ⚠️ `SD ffffff` es el slice que lleva por defecto + +![Configuración celda paso 3](img/image4.png) + +**Paso 4:** + +Configurar parámetros radio y del gNB: + +- Ancho de banda +- Frecuencia + +![Configuración radio paso 4](img/image5.png) \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/Manual OFICIAL Vankom gNB-vkScell-g3 v1.0.md b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/Manual OFICIAL Vankom gNB-vkScell-g3 v1.0.md new file mode 100644 index 0000000..238e6d3 --- /dev/null +++ b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/Manual OFICIAL Vankom gNB-vkScell-g3 v1.0.md @@ -0,0 +1,898 @@ +![][image1] + +vkScell-g3 5G Pico gNodeB Manual + +All rights reserved + +Vankom Technology Co., Ltd. + +This material and all contents contained therein are the property of Vankom Technology Co., Ltd. (Vankom) and are protected by the laws of the People's Republic of China and applicable international conventions on copyright. Without the written authorization of Vankom Technology Co., Ltd., no one shall copy, disseminate, distribute, modify or otherwise use part or all of the contents of this material in any form, and violators will be held liable according to law. + +Template Number: Version: V1.0.0 implemented on September 3, 2020 + +I +![][image2] + +Table of Contents + +1 Introduction ............................................................................................................................................ 1 + +![][image3]Introduction ..................................................................................................................................1 ![][image4]Explanation of terms.....................................................................................................................1 ![][image5]Readers..........................................................................................................................................1 2 Product Introduction............................................................................................................................... 1 + +![][image6]Introduction to the device.............................................................................................................1 2.1.1 API description ................................................................................................................1 2.1.2 Introduction to the indicator...........................................................................................2 + +![][image7]Key skill indicators.........................................................................................................................3 3 Instructions for base station operation................................................................................................... 4 + +![][image8]Base station provisioning process.................................................................................................4 3.1.1 Parametric planning ........................................................................................................4 3.1.2 Hardware connection checks..........................................................................................4 3.1.3 The device is powered on................................................................................................5 3.1.4 Base station parameter configuration.............................................................................5 3.1.5 Device restart..................................................................................................................9 3.1.6 Cell status inquiry..........................................................................................................10 +![][image9]Commonly used function configurations....................................................................................10 3.2.1 Maximum transmit power modified .............................................................................10 3.2.2 Software version upgrades............................................................................................11 3.2.3 Neighbors are added.....................................................................................................11 4 Instructions for using the LMT interface ............................................................................................... 18 + +![][image10]LMT landing page........................................................................................................................18 ![][image11]system .........................................................................................................................................18 4.2.1 The menu bar collapses/expands with the current page position................................18 4.2.2 Customize the device name ..........................................................................................19 4.2.3 The operating status of the device................................................................................19 4.2.4 SSH..................................................................................................................................20 4.2.5 Restart your device........................................................................................................20 4.2.6 Download the how-to ...................................................................................................21 4.2.7 Change your password..................................................................................................21 4.2.8 Restart LMT ...................................................................................................................22 4.2.9 Sign out .........................................................................................................................22 ![][image12]Overview .....................................................................................................................................23 4.3.1 Device resource usage...................................................................................................23 4.3.2 The operating status of the device................................................................................24 4.3.3 Board temperature........................................................................................................24 4.3.4 GPS information .............................................................................................................24 4.3.5 Alarm information.........................................................................................................25 4.3.6 Base station information...............................................................................................25 4.3.7 The running status of the PLF/RAN/OAM service ..........................................................26 4.3.8 Base station capabilities................................................................................................26 + +I +![][image13] + +4.3.9 Community information................................................................................................26 ![][image14]Real-time information.................................................................................................................27 4.4.1 Operational status.........................................................................................................27 ![][image15]Rapid provisioning.......................................................................................................................28 4.5.1 Quick start.....................................................................................................................28 4.5.2 Quick search..................................................................................................................31 4.5.3 Common configurations................................................................................................32 Configuration management........................................................................................................32 4.6.1 Basic configuration........................................................................................................32 4.6.2 Security configuration ...................................................................................................34 4.6.3 QOS.................................................................................................................................35 4.6.4 base station...................................................................................................................36 4.6.5 Parameter comparison..................................................................................................39 Software management................................................................................................................40 4.7.1 Base station upgrades...................................................................................................40 4.7.2 Version switching ..........................................................................................................42 Community management ...........................................................................................................42 4.8.1 Community information................................................................................................42 4.8.2 Community initiation process.......................................................................................43 4.8.3 Cell configuration ..........................................................................................................44 Neighborhood management.......................................................................................................44 4.9.1 Neighborhood information ...........................................................................................44 4.9.2 Neighborhood configuration.........................................................................................44 Alarm management ..................................................................................................................45 Performance management .......................................................................................................46 4.11.1 counter........................................................................................................................46 4.11.2 KPI.................................................................................................................................47 4.11.3 Real-time counting ......................................................................................................47 Log management.......................................................................................................................48 4.12.1 Base station logs..........................................................................................................48 4.12.2 System logs..................................................................................................................49 System administration...............................................................................................................49 4.13.1 Scheduled tasks...........................................................................................................49 4.13.2 Parameter Authorization (Administrator) ...................................................................50 4.13.3 Role Authorization (Administrator).............................................................................50 4.13.4 User Management (Administrator).............................................................................51 4.13.5 System configuration...................................................................................................51 + +I + +1 preface + +Introduction + +This manual describes the equipment appearance, functional characteristics, configuration, and maintenance operation methods of the base station. The common problems that may be encountered are also explained in the annotations, providing technical guidance for operators to correctly use, install, open and maintain the equipment. + +Explanation of terms + +table 1Explanation of terms + +| name | interpretation | remark | +| ----- | ----: | ----- | +| LMT | Maintain the terminal locally | | +| OAM | Operation and maintenance management | | +| WITH | Centralized unit | | +| Of the | Distribution units | | +| PHY | Physical layer | | +| PLF | platform | | +| 5GC | Core network | | +| PLMN | Public Land Mobile Network | | +| TAC | Track region codes | | +| Slice\_SST | Slice type | | +| Slice\_SD | 切片差分器（Slice Differentiato） | | + +Readers + +This book is suitable for: + +⚫ Engineering and technical personnel + +⚫ Open the commissioning personnel + +⚫ Operation and maintenance personnel + +⚫ Version testers + +2 Product Introduction + +Introduction to the device + +2.1.1 API description + +Figure 1 shows the interface diagram of the 5G integrated base station + +**1** / **55** + +fig 1Base station interface diagram +Table 2 describes the interfaces of 5G integrated base stations. + +table 2Base station interface description + +| seri al numb er | interface | Description of the interface and its functions | +| ----- | ----- | ----- | +| 1 | ANT1/2/3/4 | The external antenna interface corresponds to 4 antennas respectively, and the configuration of 2 antennas can only be connected to 1 and 4 ports. | +| 2 | PWR-12VDC | Power interface, 4 DC 12V power inputs | +| 3 | GE | Gigabit electrical port, which can be used as a return port or LMT interface | +| 4 | SFP1 | 10GE optical port, backhaul interface, connected to the core network | +| 5 | SFP2 | 10GE optical port, reserved for expansion | +| 6 | USB | Support USB2.0 | +| 7 | TST | / | + +//GE 端口默认 IP 172.20.50.1 + +2.1.2 Introduction to the indicator + + fig 2Schematic diagram of the indicator light +Table 3 describes the base station interfaces. + +table 3Description of the base station indicator + +| Silk screen name | type | color | state | illustrate | use | +| :---: | ----- | ----- | ----- | ----- | ----- | +| POWER | power supply | green | extinguish | There is no power input | Power status indication | +| | | | The green | There is a power input | | + +**2** / **55** + +| | Light | | light is always on | | | +| ----- | ----- | ----- | ----- | ----- | ----- | +| RUN/ALM | The status of the entire machine Light | Green/Red Bicolor | The green light is solid or flashing | Solid on: The cell is running normally, flashing: Slow flashing in cell activation: Out in cell configuration: The cell is abnormal | | +| | | | Flash red fast or slowly | High-level alerts flash fast Low-level alarms flash slowly | Indication of the operating status of the system | +| ACT/LINK1 | Fiber link status indicator | green | extinguish | The internal link was not successfully established | SPF0 link status indication | +| | | | The green light is always on | The internal link is established normally | | +| ACT/LINK2 | Fiber link status indicator | green | extinguish | The internal link was not successfully established | SPF1 link status indication | +| | | | The green light is always on | The internal link is established normally | | + +Key skill indicators + +The main skill indicators of the integrated base station are as follows: table 4Base station specifications + +| serial number | The name of the metric | Metric values | +| ----- | ----- | ----- | +| 1 | Frequency bands are supported | 5G N41/N78 | +| 2 | Carrier fan capacity | One 100MHz 4T4R cell or two 100MHz 2T2R cells are supported | +| 3 | The number of users in the cell | Each cell supports no less than 64 active users and no less than 200 RRC connected users. | +| 4 | Channel bandwidth is supported | IBW 100MHz, carrier bandwidth supports 20MHz, 40MHz, 50MHz, 60MHz, 80MHz, 100MHz | +| 5 | Maximum transmit power | 4 channels, 250mW per channel | +| 6 | Device synchronization mode | IEEE1588v2 clock synchronization is supported | + +**3** / **55** + +| 7 | size | 306mm\*234mm\*67mm (length \* width \* height). | +| :---- | :---- | :---- | +| 8 | weight | 3.6kg | +| 9 | Power supply mode | Quad DC 12V Supply, Voltage Range ± 10% | +| 10 | antenna | External antennas | +| 11 | Operating temperature | Long-term working temperature: \-40°C\~+50°C | +| 12 | Operating relative humidity | 10％～95％ | + +3 Instructions for use of base station operation All changes to the parameters in this section must be restarted to take effect. +Base station provisioning process + +3.1.1 Parametric planning + +Table 4 lists the parameters required for base station activation. table 5Parameter planning table + +| Parametric planning | | +| ----- | ----- | +| The name of the parameter | illustrate | +| IP address of the base station service | eGTPU-IP 地址、NGAP-IP 地址,与核心网 N2/N3 可进行 ping 通。 | +| Frequency of work | Frequency of community work | +| Working bandwidth | Cell operating bandwidth | +| Frame structure | Cell working frame structure | +| Antenna mode | 2T2R/4T4R/2T2R-KS（天线复制模式） | +| PLMN | Consistent with the core network | +| PCI | Physical cell identification | +| TAC | Cell tracking area code | +| NG interface IP | IP address of the core network AMF | + +3.1.2 Hardware connection checks + +As shown in Figure 3, check the wiring of the device before powering on to ensure that the line connection is correct, as follows: a) Check the power connection to + +ensure that the power cord is properly connected to the DC 12V power module and that the connection is tightened and not loose. + +**4** / **55** + +b) Check the connection of the antenna port + +to ensure that the RF port of the base station is connected to the antenna and ensure that the connection is not loose. + +c) Check the 1588 to + +make sure that the optical port is connected to a clock server and that the clock signal can be synchronized. + +d) Optical port inspection + +Make sure that optical port 1 is connected to the core network or is on the same switch as the core network, and the optical module rate is 10 Gbit/s. + +3.1.3 The device is powered on + +When the hardware connection check is completed, the device can be powered on (DC12V), and the base station can be started after 3 minutes of power-on, and the power indicator is always on. +3.1.4 Base station parameter configuration + +3.1.4.1 login + +Connect the computer to the GE interface of the base station, enter the 172.20.50.1 (default) address in the browser to enter the LMT login page; You can also log in by connecting the computer to the optical port and entering the optical port address + +On the login page, you can click \[Verification Code\] to switch, fill in the correct user name, password, and verification code, and click \[Login\] to enter the LMT system, as shown in the figure. + +Account: admin + +Password: lmt\_2023 + +**5** / **55** + +3.1.4.2 Modify the IP address of the base station + +After logging in to LMT, click \[Configuration Management\] \-- \[Basic Configuration\] \-- change the eth0 address to Chapter 3.1.1 to plan the IP address of the base station business, if you need to add multiple IPs, click \[addresses\] \-- click \[+\] to add, and then click \[Save\]. + +3.1.4.3 Frequency/frame structure/channel number configuration + +After logging in to LMT, click \[Quick Configuration\] \-- \[Quick Station Opening\] \-- click \[cell 333\] \--- select the frequency, frame structure and +**6** / **55** + +number of antennas \-- and then click \[Open Station\]. + +The following table describes the number of antennas: + +2T2R：1、4 port TX and RX + +4T4R：1、2、3、4 port TX and RX + +2T2R-KS: 1 or 2 channels to 3 or 4 channels (antenna connection 1, 2 or 2 or 4\) + +3.1.4.4 Clock modifications + +After logging in to LMT, click \[Quick Configuration\] \-- \[Quick Station Opening\] \-- click \[Base Station Parameters\] \-- configure \[Clock Source Configuration\] to 0 \-- and then click \[Open Station\]. + + Parameter description: + +0：1588 + +1: GNSS (not supported by this device) + +2:Freerun + +3.1.4.5 NG transport configuration + +After logging in to LMT, click \[Quick Configuration\] \-- \[Quick Site Opening\] \-- Click \[Base Station Parameters\] \-- CU\_eGTPU-IP Address, CU\_NGAP-IP Address, CU\_XNAP-IP Address, and AMF Server Address to the + +**7** / **55** + +address planned in Chapter 3.1.1 \-- and then click \[Open Site\]. If the N2 and N3 addresses of the core network are different, follow this step.CU\_eGTPU + +Click \[Quick Configuration\] \-- \[Quick Search\] \-- fill in IPInterfaceIPAddress in the search box, then click the Enter key, modify the IP according to the response shown below, and then click \[Save and Deliver\]. +3.1.4.6 PLMN configuration + +After logging in to LMT, click \[Quick Opening\] \-- \[Operator ID\] \-- Modify PLMN that is consistent with the core network \-- Click \[Open Site\]. **8** / **55** + +3.1.4.7 TAC configuration + +After logging in to LMT, click \[Quick Opening\] \-- \[Important Parameters of the Community\] \-- \[Basic Configuration\] \-- Modify the code of the 5GS tracking area to be consistent with the core network \-- click \[Open Site\]. + +3.1.4.8 Slice configuration + +After logging in to LMT, click \[Quick Opening\] \-- \[Network Slicing\] \- \- Modify the Slice\_SST and Slice\_SD to be consistent with the core network \-- click \[Open Site\]. + +3.1.5 Device restart + +After the parameters are configured, restart the device for the + +parameters to take effect. + +After logging in to LMT, click \[Overview\] \-- click \[Restart Device\] \- \- click \[OK\]. + +**9** / **55** + +3.1.6 Cell status inquiry +After logging in to LMT, click \[Overview\] \-- \[Community Information\] to view the running status of the community, and if it is activated, the community will be established successfully. + +Commonly used function configurations + +3.2.1 Maximum transmit power modified + +After logging in to LMT, click \[Quick Configuration\] \-- \[Common Configuration\] \-- enter the power to be modified in the power value (the unit is dbm, and it will be automatically calculated as W after input) \-- and then click \[Save\]. + +**10** / **55** + +3.2.2 Software version upgrades + +After logging in to LMT, click \[Software Management\] \-- \[Base Station Upgrade\] \-- Click \[Upload File\] to upload the upgrade package \-- click \[OK\] \-- if the cell is in a fault state before the upgrade, the rollback policy should be turned off \-- click \[Upgrade\]. + +Rollback policy: If the detection cell is not activated after the + +upgrade, the version will be rolled back. + +During the restart phase of the upgrade process, you need to wait for the restart to complete the automatic connection on the current page, or you can manually refresh it later. + +3.2.3 Neighbors are added + +Measurement Event Interpretation: + +A1: The service cell is better than a certain threshold, and the measurement is turned off, and the unit is dBm + +A2: If the service cell is below a certain threshold, open the measurement, in dbm + +A3: The adjacent cell is better than the current service cell by a + +**11** / **55** + +certain value, which is mostly used for co-frequency switching, and the unit is db + +A4: The adjacent cell is better than a certain threshold, and it is mostly used for different frequency switching, in dbm + +A5: The service cell is lower than a certain threshold, and the adjacent cell is better than a certain threshold, which is mostly used for frequency switching, unit dBm + +B1: The adjacent area of the different system is better than a certain threshold, and it is mostly used for the switching of different systems, in dbm + +B2: The service cell is lower than a certain threshold value, and the adjacent cell of the different system is better than a certain threshold value, which is mostly used for different frequency switching, unit dBm 3.2.3.1 Measure switch configuration + +1\> Turn on the A1/A2 measurement switch: + +After logging in to LMT, click \[Configuration Management\] \-- \[Base Station\] \-- \[CU\] \-- \[Power Control Information\] \-- \[Default Measurement Parameter Configuration during UE Initial Access\] \-- Change \[A1 Measurement Switch\] and \[A2 Measurement Switch Configuration\] to 1 \-- + +click \[Save and Issue\]. + +2\> Turn on the A3 measurement switch of the same frequency: + +Simultaneous frequency switching changes this configuration; After logging in to LMT, click \[Configuration Management\] \-- \[Base Station\] \-- \[CU\] \-- \[Power Control Information\] \-- \[Default Measurement +**12** / **55** + +Parameter Configuration during UE Initial Access\] \-- Change \[Same + +Frequency A3 Measurement Switch\] to 1 \-- Click \[Save and Issue\]. 3\> Turn on the A4 measurement switch: + +Change this configuration if the frequency is switched; + +After logging in to LMT, click \[Configuration Management\] \-- \[Base Station\] \-- \[CU\] \-- \[Power Control Information\] \-- \[Measurement Parameter Configuration after A2 Measurement Received\] \-- Change \[Frequency A4 Measurement Switch\] to 1 \-- Click \[Save and Issue\]. +3.2.3.2 Measurement configuration + +1\> Measurement Configuration: + +The default can be used for co-frequency measurement; + +The cross-frequency measurement configuration is as follows: After logging in to LMT, click \[Neighborhood Management\] \-- \[Neighborhood Management\] \--\[Linkage Area Configuration\]-- \[MeasControlLsit\]--\[MeasContro\[name=meas1\]\]-- + +\[InterFreq\[InterFreq\[MeasContro\[name=meas1\]\]--\[InterFreq\[InterFreq-- + +**13** / **55** + +Click \[+\] \- fill in the ssb frequency, subcarrier spacing, and BAND of the adjacent cell \- click \[OK\]. + +(Multiple transience measurements can be added) + +2\> Measurement Event Thresholds: + +Log in to LMT and click \[Neighborhood Management\] \-- \[Neighborhood Configuration\]--\[MeasControlLsit\]--\[MeasContro\[name=meas1\]\]-- \[EventConfig\]--\[A1Event\]--点击\[TriggerQuantityThreshold\]-- Configure the corresponding event type according to the event type enabled in conjunction with the measurement switch, and set the corresponding value for \[ThresholdRSRP\]. + +ThresholdRSRP Parameter definition: 156 minus this parameter is the + +absolute value dbm + +**14** / **55** + +Example: + +A1 Event Configuration: + +If ThresholdRSRP is set to 81, the corresponding threshold value is 156-81=75 dBm. + +3.2.3.3 Add neighbors + +3\> To add a co-frequency neighbor: + +a) Log in to LMT and click \[Neighborhood Management\] \-- \[Neighborhood Configuration\]--\[NeighborList\]--\[IntraFreqCell\]--Click \[+\] \-- Fill in the neighboring area PLMN,CID,SCS,PCI,TAC — Click OK. +**15** / **55** + +b) Configure BAND + +Click on the neighbors that have been added—click\[NRTDDInfo\]-- \[NRFreqBandList\]--\[NRFreqBandItem\]-- Modify the band value \- Click \[Save & Deliver\]. +c) Configure the SSB frequency + +Click on the added neighborhood—click \[MTC\]--\[MeasTimingItem\]-- modify the ssb frequency—click \[Save and Deliver\]. +d) Multiple PLMNs can be added to the same frequency neighborhood Click on the added neighborhood—click \[+\] \- fill in PLMN \- click \[OK\]. + +**16** / **55** + +4\> To add a frequency neighbor: + +a) Log in to LMT and click \[Neighborhood Management\] \-- \[Neighborhood Configuration\]--\[NeighborList\]--\[InterFreqCell\]--点击\[+\]-- Fill in the neighboring cell’s PLMN, CID, SSB frequency number,SCS, PCI,TAC,BAND — Click OK. +**17** / **55** + +4 Instructions for using the LMT interface + +In the operation instructions, the login user is the administrator permission, and the system can support the current mainstream browsers including Chrome 85 or above (recommended), Edge85 or above, and Firefox 79 or above. +LMT landing page + +Enter the correct management port (default 172.20.50.1) or optical port address in the browser to enter the LMT login page. + +On the login page, you can click \[Verification Code\] to switch, fill in the correct user name, password, and verification code, and click \[Login\] to enter the LMT system, as shown in the figure. + +Account: admin + +Password: lmt\_2023 + +system + +4.2.1 The menu bar collapses/expands with the current page position + +The left side of the system is the operation menu, you can click the button in the lower left corner \[Collapse/Expand\] menu bar; The upper right corner is the title of the current main page, which is automatically updated with page switching. As shown in Fig. + +**18** / **55** + +4.2.2 Customize the device name + +The middle part is the current device name, you can click \[Name\] to enter the editing mode (the maximum custom name is 20 characters), as shown in the figure. +4.2.3 The operating status of the device + +The right side of the device name displays the current running status of the device, you can click Refresh, and it supports automatic refresh configuration, configuration location: \[System Management/System Configuration \-- Auto Refresh/Base Station Status\] + +**19** / **55** + +4.2.4 SSH + +The upper right corner of the system is the global operation button, + +click \[SSH\] to enter the command line mode, as shown in the figure. + +4.2.5 Restart your device + +Click \[Restart device\] to automatically identify the current restart type, click restart and wait on the current page, and the system can be automatically connected after the restart is successful. + +**20** / **55** + +4.2.6 Download the how-to + +Click \[Current User\] and drop down menu \[Operation Instructions\] to download the current version of the operation instructions to the local computer. +4.2.7 Change your password + +Click \[Change Password\], you can enter the original password/new password and click \[OK\] to change the password, and you need to log in again after changing the password. + +**21** / **55** + +4.2.8 Restart LMT + +Click Restart LMT and Confirm to restart LMT. + +4.2.9 Sign out + +Click Sign Out and Confirm to log out of the current user login status. + +**22** / **55** + +Overview + +On the overview page, the device running status, alarm information, base station information, 5GC running status, UPF running status, PLF running status, RAN running status, OAM running status, base station capability, and cell information are displayed as follows. +4.3.1 Device resource usage + +Display and update the CPU, memory (hover over \[Memory Usage\] to display the total memory, used memory, and available memory), disk usage, and change trend in real time, as shown in the figure, click \[View Details\] to jump to the real-time information details page, and display the CPU usage + +by core (please refer to the 2.4 Real-time Information section).**23** / **55** + +4.3.2 The operating status of the device + +The device information, startup time, and running duration are + +displayed, as shown in the figure. + +4.3.3 Board temperature + +Display and update the board temperature and trend in real time, as + +shown in the figure. + +4.3.4 GPS information + +Display GPS information, including: latitude and longitude, altitude, signal strength, as shown in the figure. + +**24** / **55** + +4.3.5 Alarm information + +To display the statistics of the four levels of alarms that are currently active, click Refresh Information to manually refresh the statistics (see 2.13 System Management/System Configuration for automatic refresh configuration), and click View Details to jump to the alarm information details page (see 2.10 Alarm Management), as shown in the figure. +4.3.6 Base station information + +Displays the basic information of the current base station, including the serial number, hardware version, software version, and clock source information, as shown in the figure. + +**25** / **55** + +4.3.7 The running status of the PLF/RAN/OAM service Display the PLF/RAN/OAM running status, startup time, and running duration, click the Refresh Status button to refresh the current running status, and click the Start/Stop button to start and stop the corresponding service, as shown in the figure. + +4.3.8 Base station capabilities + +The specific capabilities of the current base station are displayed, + +as shown in the figure. + +4.3.9 Community information + +Displays all cells of the current device, and supports manual refresh + +**26** / **55** + +of the cell running status, as shown in the figure. + +Real-time information + +4.4.1 Operational status + +Display and update base station information in real time: RRC access success rate, number of UEs, antenna RSSI, board temperature, support for custom update frequency, configuration location \[system management/system configuration \-- automatic refresh/real-time information/base station information\]; + +Display and update device information in real time: CPU core usage, memory usage, update frequency 1s; + +As shown in Fig. + +**27** / **55** + +Rapid provisioning + +4.5.1 Quick start + +4.5.1.1 Parameter modification/site opening + +After the corresponding parameter device value column is modified, click \[Changed Parameters\] to view the current modified parameters, click the \[Delete\] button to delete the modifications, restore the parameter values, and after all the modified parameters are verified, click \[Open + +Station\] and \[Confirm\] to save and distribute, as shown in the figure. + +**28** / **55** + +4.5.1.2 Modify associated parameters + +After the main parameters of the associated parameters are modified, other parameters in the same group are automatically synchronized to the modified state, and the non-primary parameters can be modified separately + +again, as shown in the figure. + +4.5.1.3 Export the template + +Click Export Template to export all the parameters of the current fast website as a template .xlsx format file, as shown in the figure. + +**29** / **55** + +4.5.1.4 Import parameters + +After modifying the required device values in the export template, click \[Import Parameters\], select the file and click \[OK\] to perform the correct parameter import, the imported parameters will automatically match the modified values and update them on the page, and then click \[Open Site\] + +to send them after checking that they are correct. + +4.5.1.5 Site opening guidance + +Menu: \[Quick Configuration/Quick Station Opening\] + +You can quickly switch/configure the main parameters through the navigation items, including: base station basic information, network management information, and each cell parameter, as shown in the figure. + +**30** / **55** + +4.5.2 Quick search + +Menu: \[Quick Configuration/Quick Search\] + +4.5.2.1 Parametric search + +Support parameter name fuzzy search, can be automatically prompted according to the input character, \[Enter\] or click the \[Search\] button to perform the search, the results will highlight the keyword (up to 64 search results are displayed, more results need to be re-searched with precise search conditions), as shown in the figure. + +4.5.2.2 Modify & Save + +The modification and saving of search parameters are the same as those in 2.5.1. +4.5.2.3 Parameter positioning + +Click Parameter Name to automatically jump to the specific configuration structure of the parameter under configuration management, as shown in the figure. + +**31** / **55** + +4.5.3 Common configurations + +It supports modifying the power value of the cell, \[Enter\] or clicking \[Save\] (the save button will automatically appear after the power value is modified) to send it, as shown in the figure. + +Configuration management +4.6.1 Basic configuration + +4.6.1.1 Network configuration + +Menu: \[Configuration Management/Basic Configuration\] + +Display the current network configuration, hover over each node, and display the operation items supported by the node; + +Click the node to modify it, and click the icon on the right to perform + +**32** / **55** + +related operations, as shown in the figure. + +4.6.1.2 Time zone configuration + +Menu: \[Configuration Management/Basic Configuration\] + +The time zone can be modified, as shown in the figure. + +**33** / **55** + +4.6.2 Security configuration + +4.6.2.1 Generic configuration + +Menu: \[System Administration/Security Configuration\] + +Support to display the status, display and modify the pre-shared key, ConfigDeploy, and switches, and click \[Confirm\] to modify the switch after + +toggling the \[Switch\] state, as shown in the figure. + +Click \[Configuration\] to modify the pre-shared key/ConfigDeploy, and + +click \[Save and Deliver\] to perform the delivery operation, as shown in + +the figure. + +4.6.2.2 Channel configuration + +Displays all channel configuration information, supports adding and deleting channels, and modifies channel parameters, as shown in the figure. + +**34** / **55** + +4.6.3 QOS + +MENU: \[CONFIGURATION MANAGEMENT/QOS\] + +4.6.3.1 Key messages + +THE MAIN QOS INFORMATION OF EACH CELL IS DISPLAYED IN THE FORM OF A LIST OF CELLS, AS SHOWN IN THE FIGURE. +4.6.3.2 QOS CONFIGURATION + +CLICK THE \[QOS CONFIGURATION\] BUTTON ON THE "MAIN INFORMATION" INTERFACE TO SWITCH TO THE QOS DETAILED PARAMETER CONFIGURATION INTERFACE, CLICK THE \[ADD\] BUTTON ABOVE THE CONFIGURATION STRUCTURE TREE TO PERFORM ADD, AND CLICK THE \[DELETE\] BUTTON ON THE RIGHT SIDE OF THE QOS NODE OF + +**35** / **55** + +THE CONFIGURATION STRUCTURE TREE TO DELETE IT, AND THE MODIFICATION OPERATION IS THE SAME AS 2.5.1 QUICK OPENING OF THE SITE, AS SHOWN IN THE + +FIGURE. + +4.6.4 base station + +4.6.4.1 Profiles + +Menu: \[Configuration Management/Base Station/Configuration File\] Displays all configuration files of the current base station. Upload file: Click Upload File, select the configuration file and click OK to perform the upload, as shown in the figure. + +➢ Export File: Click \[Export File\] to export the current configuration of the device, as shown in the +**36** / **55** + +figure; + +➢ Add a note: Click the \[Edit\] button in the comment column to customize the note information for + +the specified profile, and click \[OK\] to submit, as shown in the figure; + +➢ Import configuration file: Click the \[Import\] button to import the specified configuration for the + +device, as shown in the figure, you **need to wait for the service to restart after the prompt message is completed before proceeding with other operations**; + +➢ Download the configuration file: Click the \[Download\] button to download the specified configuration file to the local computer, as shown in the figure. + +➢ Delete a profile: Click the \[Delete\] button to delete the specified profile, as shown in the figure. + +**37** / **55** + +4.6.4.2 OAM + +Menu: \[Configuration Management/Base Station/OAM\] + +Parameter information can be displayed by category, and the parameters of CU, DU, PHY, PLF, and OAMCFG can be saved and delivered in a unified manner (the modification and delivery operations are the same as those in 2.5.1 Quick Start), and the main view of the classification and the main view of the parameter list can be switched, as shown in the figure. +Click Parameter Name to view the parameter definition information, as shown in the figure. + +**38** / **55** + +4.6.4.3 WITH + +菜单：\[配置管理/基站/CU\] + +The operation is the same as OAM. + +4.6.4.4 Of the + +Menu: \[Configuration Management/Base Station/DU\] + +The operation is the same as OAM. + +4.6.4.5 PLF + +Menu: \[Configuration Management/Base Station/PLF\] + +The operation is the same as OAM. + +4.6.4.6 OAMCFG + +Menu: \[Configuration Management/Base Station/OAMCFG\] + +The operation is the same as OAM. + +4.6.5 Parameter comparison + +Menu: \[Configuration Management/Parameter Comparison\] + +To display the list of uploaded profiles, you can edit notes/download/delete, click the \[Compare\] button to compare the parameter differences between the selected profiles and the current device, wait for the comparison to be completed, and display the list of differences by parameter category (filter by category is supported), as shown in the figure. + +**39** / **55** + +Software management + +4.7.1 Base station upgrades + +Menu: \[Software Management/Base Station Upgrade\] + +Displays the current software version and all upgrade file information, and supports modifying the rollback policy and uploading the upgrade file, as shown in the figure. + +**40** / **55** + +Click \[Upgrade\] and \[Confirm\] to execute the upgrade file, as shown in the figure, and display the real-time upgrade progress when the upgrade is executed. + +During the restart phase of the upgrade process, you need to wait for the restart to complete the automatic connection on the current page, or you can manually refresh it later. + +Specify the upgrade file, click \[Delete\] and \[Confirm\] to delete the upgrade file, as shown in the figure. + +**41** / **55** + +4.7.2 Version switching + +Menu: \[Software Management/Version Switching\] + +Displays the version information of all installed software of the current base station, identifies the conflicting version and the current version, and supports version switching, deletion, and information refresh, as shown in the figure. +Community management + +Menu: \[Community Management\] + +4.8.1 Community information + +Displays all the basic information of the community. + +➢ Create a community: Click \[Create Community\], enter the cell name, and click \[Confirm\] to create + +the community, as shown in the figure; + +**42** / **55** + +➢ Update Template: Click \[Update Template\], select the template community and \[Confirm\] execution, as shown in the figure; + +➢ Refresh the cell running status: Click the \[Refresh\] button to re-obtain the cell running status; ➢ Activation/deactivation: Click the \[Activate\]/\[Deactivate\] button of the designated cell to perform the activation/deactivation operation; + +➢ Cell configuration: Click the \[Configuration\] button of the designated cell to jump to the cell configuration page (see the next section on cell configuration); + +➢ Delete the cell: Click the \[Delete\] button and \[Confirm\] to delete the cell. + +4.8.2 Community initiation process + +Click on the cell list/current running status to view the cell startup process, as shown in the figure. +**43** / **55** + +4.8.3 Cell configuration + +Click the \[Configuration\] button of the specified community to jump to the cell configuration page, you can modify the corresponding parameters, and execute the save and delivery (the operation is the same as 2.5.1 to quickly open the station), as shown in the figure. + +Neighborhood management +Menu: \[Neighborhood Management\] + +4.9.1 Neighborhood information + +To display the 5G/4G neighborhood information under each cell, click \[Neighborhood Configuration\] to jump to the neighborhood configuration page, + +as shown in the figure. + +4.9.2 Neighborhood configuration + +Display the parameters of the neighborhood, support modify/save the + +**44** / **55** + +delivery (the same as 2.5.1 quick site opening), and support add/delete, where add is to add sub-parameters, and delete is to delete this level of + +parameters, as shown in the figure. + +You can select a template cell and update the template, as shown in + +the figure. + +Alarm management + +Menu: \[Alarm Management\] + +Displays the current active alarms, historical alarms, and event alarm information, and the automatic update cycle can be configured (please refer to 2.13 System Management/System Configuration for automatic refresh configuration), supports manual refresh, and supports clicking \[Alarm Number\] to view the alarm knowledge base, as shown in the figure. + +**45** / **55** + +Performance management + +4.11.1 counter + +Menu: \[Performance Management/Counter\] + +All counter groups are displayed, you can select counter groups, view the corresponding counter data by category, and export all/manually refresh, as shown in the figure. + +**46** / **55** + +4.11.2 KPI + +Menu: \[Performance Management/KPI\] + +View KPIs by category, support export all/manual refresh, as shown in the figure. + +4.11.3 Real-time counting + +Menu: \[Performance Management/Real-Time Counting\] + +The count information is updated in real time, and the auto-refresh frequency can be modified (for details about the auto-refresh configuration, see 2.13 System Management/System Configuration), as shown in the figure. + +**47** / **55** + +Log management + +4.12.1 Base station logs + +Menu: \[Log Management/Base Station Log\] + +Displays the base station logs of the current version and previous versions. + +It contains logs such as CU and DU, and displays the total size of logs in the current category, the folder where the current logs are located, and the list of all logs. + +Support fuzzy search by name in the current display list; 支持修改 CU/DU/OAM/PHY 日志级别; + +Support deleting/batch deletion of log files (folders); + +Support online viewing/downloading of log files; + +As shown in Fig. + +**48** / **55** + +4.12.2 System logs +Menu: \[Log Management/System Log\] + +The system logs are displayed, and the logs of the operation are the same as the base station, as shown in the figure. + +System administration + +4.13.1 Scheduled tasks + +Menu: \[System Administration/Scheduled Tasks\] + +Displays the scheduled task file of the current device, which can be edited/diff/saved, as shown in the figure. + +**49** / **55** + +4.13.2 Parameter Authorization (Administrator) Menu: \[System Management/Parameter Authorization\] + +As shown in the figure, you can edit the visible/writable status of parameters in the Configuration Administrator role, check multiple boxes to determine whether the parameters are visible, and configure whether the + +parameters are writable by using the writable switch. + +**Note: After the system is deployed, the administrator needs to authorize the parameters first, and then the configuration administrator and the common user can perform normal operations.** 4.13.3 Role Authorization (Administrator) + +Menu: \[System Administration/Role Authorization\] + +All user roles and corresponding operation permissions are displayed, and administrators can modify and configure administrator permissions, as + +**50** / **55** + +shown in the figure. + +4.13.4 User Management (Administrator) + +Menu: \[System Administration/User Management\] + +Displays all user information of the current system, supports adding/deleting users (the current user cannot be deleted), and resetting the password, as shown in the figure, in which you need to log in again after resetting the current user password. + +4.13.5 System configuration + +Global configuration is supported: + +➢ Alarms, real-time information/base station information, real-time performance counting, cell operation status, base station status (top row), service status (overview page) refresh frequency; ➢ Parameter list display column (whether to display the parameter path name/English name); ➢ The overview page displays the service items; +As shown in Fig. + +**51** / **55** + +**52** / **55** + +[image1]: + +[image2]: + +[image3]: + +[image4]: + +[image5]: + +[image6]: + +[image7]: + +[image8]: + +[image9]: + +[image10]: + +[image11]: + +[image12]: + +[image13]: + +[image14]: + +[image15]: \ No newline at end of file diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image1.png b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image1.png new file mode 100644 index 0000000..f814333 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image1.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image2.png b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image2.png new file mode 100644 index 0000000..c9bfc9b Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image2.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image3.png b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image3.png new file mode 100644 index 0000000..19f6891 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image3.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image4.png b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image4.png new file mode 100644 index 0000000..07cf403 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image4.png differ diff --git a/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image5.png b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image5.png new file mode 100644 index 0000000..7d59f29 Binary files /dev/null and b/docs/MANUALES DE USUARIO/MANUAL gNB/VANKOM-gNB/img/image5.png differ diff --git "a/docs/RETOS/RETO1_ Configuraci\303\263n de red 5G_EiTB.docx.md" "b/docs/RETOS/RETO1_ Configuraci\303\263n de red 5G_EiTB.docx.md" new file mode 100644 index 0000000..ab79f78 --- /dev/null +++ "b/docs/RETOS/RETO1_ Configuraci\303\263n de red 5G_EiTB.docx.md" @@ -0,0 +1,233 @@ + + +**CURSO INSTALACIÓN Y CONFIGURACIÓN DE REDES 5G** + +**“Caso de uso: Red privada 5G en las instalaciones de EiTB (Donosti)”** + +**Situación:** + +EiTB quiere sustituir su red WiFi tradicional por una **red privada 5G** con el objetivo de: + +* Evitar interferencias. +* Garantizar calidad de servicio. +* Disponer de control total sobre usuarios y dispositivos. +* Preparar la infraestructura para servicios críticos de comunicación y vídeo. + +La red se desplegará inicialmente en una de sus instalaciones (sede / fábrica) en Donostia. + +**Servicios iniciales:** +La red debe dar servicio, al menos, a los siguientes dispositivos: + +* **Terminal 1:** + Teléfono móvil de un trabajador de EiTB. + Uso: acceso a Internet y aplicaciones internas de gestión. +* **Terminal 2:** + Router 5G o cámara IP conectada a la red privada. + Uso: videovigilancia dentro de la red de EiTB. + +![][image1] +**Imagen:** Red privada 5G para eitb Donosti + +## **Arquitectura de la red** + +La red privada 5G estará compuesta por los siguientes elementos: + +* **Core 5G (Open5GS)** + Incluye funciones de control y usuario (AMF, SMF, UPF, etc.). + +* **Radio gNB** + Proporciona cobertura radio 5G dentro de las instalaciones. + +* **Dispositivo de red (Mikrotik)** + Encargado de: + * Salida a red local / Internet. + * NAT y encaminamiento. + + +* **OpenCell \+ SIMs** + Para la gestión y provisión de identidades de usuario (UEs). + +* **Equipos cliente (UEs)** + Teléfono móvil y router/cámara 5G. + +## **Desarrollo del entrenamiento 05** + +Partiendo del equipamiento proporcionado (Core 5G, radio gNB, dispositivos de red y terminales de cliente), se procederá a la **instalación y configuración de una red privada celular 5G**, asegurando que todos los elementos queden integrados correctamente dentro de la red del cliente (EiTB). + +Cada grupo deberá configurar una red con **parámetros propios**, que la identifiquen de manera única y eviten interferencias con otras redes. + +## **Parámetros de configuración** + +### **EQUIPO 1** + +### **Parámetros a configurar en el Core 5G** + +* **Nombre del Operador:** +* **PLMN:** + * **MCC:** + * **MNC:** +* **TAC (Tracking Area Code):** + +### **Parámetros a configurar en la radio gNB** + +* **Modo dúplex:** +* **Ancho de banda:** +* **ARFCN:** +* **Subframe Assignment:** +* **Sector ID / PCI** (valor entre 0 – 553): +* **gNB ID (hexadecimal):** +* **Potencia de transmisión:** +* **PLMN:** +* **TAC:** + +## + +## + +## + +## + +## + +## **Se pide** + +### **1\. Esquema de red** + +Realiza un **esquema lógico sencillo** en el que se indiquen: + +* Elementos que intervienen en la red privada 5G. +* Conexiones entre ellos. +* Parámetros de red principales asociados a cada elemento. + +**Resultado esperado:** +Un mapa lógico claro de la red privada 5G de EiTB. (**Tabla I**) + +### **2\. Configuración de la red** + +Configura la red privada celular 5G utilizando los parámetros listados anteriormente: + +* Core 5G. +* Radio gNB. +* SIMs. +* Dispositivos clientes. + +### **3\. Verificación de funcionamiento** + +Comprueba el funcionamiento de la red privada 5G desde el lado del cliente haciendo uso de las herramientas necesarias: + +* Analizador espectral. +* Aplicaciones del terminal. +* Test de velocidad. +* Ping / traceroute. +* Logs del Core 5G. + +### **4\. Medidas de rendimiento** + +Realiza una **tabla de resultados** con: + +* Velocidades de subida y bajada. +* Latencia medida. + + +Posteriormente: + +* Modifica el **ancho de banda**. +* Modifica el **subframe assignment** + . + +Vuelve a medir y compara resultados. + +### **5\. Gestión de SIMs** + +* Crea una **nueva SIM** para la red privada 5G. +* Regístrala correctamente en el Core 5G. + + +**Pregunta:** + +* ¿Qué **APN** has configurado para esta red privada? + +## + +## + +## + +## **¿Qué pasa si…?** + +Analiza y documenta el comportamiento de la red en los siguientes casos: + +1. **Cambiamos solo el TAC o el PLMN** en: + + * El Core 5G. + * La radio gNB. + + Mostrar y explicar el fallo resultante. + +2. **Paramos el contenedor del UPF** + + * ¿Qué ocurre con el tráfico de datos? + * ¿El terminal sigue registrado en red? + +3. **Nos desplazamos fuera de cobertura** + + * ¿Cómo responde la red? + * ¿Qué mensajes aparecen en el Core? + +## **EXTRA – Documentación para el cliente** + +Elabora una **documentación final para EiTB**, que incluya como mínimo: + +### **PORTADA** + +* Nombre del proyecto. +* Cliente. +* Fecha. +* Equipo responsable. + + +### **ÍNDICE** + +### **INSTALACIÓN DE LA RED PRIVADA** + +* Descripción general. +* Datos técnicos necesarios para el cliente. +* Parámetros configurados. + + +### **CAMBIOS EN LA CONFIGURACIÓN** + +* Posibles modificaciones para mejorar velocidades. +* Ajustes según el uso final: + * Móviles. + * Cámaras. + * Routers. + +### **CONCLUSIONES** + +* UEs conectados. +* Rendimiento observado. +* Troubleshooting básico. + +## **Enlaces de consulta** + +[**https://5g-tools.com/**](https://5g-tools.com/) + +[**https://www.cellmapper.net/enbid?lang=es**](https://www.cellmapper.net/enbid?lang=es) + +| Elementos de la red privada Celular 5G |   | | | | +| :---- | ----- | :---- | ----- | :---- | +| **Sistema radiante** |   | | | | +| **RRU (Unidad de radio remota)** |   | | | | +| **BBU (Unidad de banda base)** |   | | | | +| **Core de la red** |   | | | | +| **Identificación de las Ips de la red privada celular 5G** | ** ** | | | | +| **Elemento** | **IP** | **Máscara** | **Puerta de enlace** | **DNS** | +| **gNB** |   |   |   |   | +| **Host del Core-físico** |   |   |   |   | +| **Core 5G** |   |   |   |   | +| **UPF** | | | | | +| **Terminal móvil** |   |   |   |   | + +[image1]: img/reto1_image1.png \ No newline at end of file diff --git a/docs/RETOS/RETO2_ Streaming_EiTB_UPF separado.docx.md b/docs/RETOS/RETO2_ Streaming_EiTB_UPF separado.docx.md new file mode 100644 index 0000000..b769947 --- /dev/null +++ b/docs/RETOS/RETO2_ Streaming_EiTB_UPF separado.docx.md @@ -0,0 +1,211 @@ + + +**CURSO INSTALACIÓN Y CONFIGURACIÓN DE REDES 5G** + +**“Caso de uso:** +**Retransmisión de eventos deportivos: gNB y UPF en San Mamés, Core en EiTB (Donostia)”** + +**Situación:** + +EiTB no solo produce contenidos en sus instalaciones, sino que también realiza **retransmisiones deportivas en directo**, por ejemplo partidos de fútbol en San Mamés. + +En este escenario aparecen nuevos requisitos técnicos: + +* Necesidad de **baja latencia** para vídeo en tiempo real. +* Elevado tráfico de subida (uplink). +* Evitar que todo el tráfico de usuario tenga que volver al Core central. +* Mayor resiliencia y escalabilidad de la red. + +Para cumplir estos requisitos, EiTB decide **separar el plano de control y el plano de usuario**, desplegando el **User Plane Function (UPF)** cerca del evento deportivo. + +**Servicios del escenario:** +La red debe dar servicio, al menos, a: + +* **Terminal 1:** + Móvil del personal técnico del estadio. + Uso: comunicaciones y acceso a servicios corporativos. +* **Terminal 2:** + Cámara de vídeo / router 5G para retransmisión en directo. + Uso: streaming de vídeo hacia la infraestructura de producción. + +![][image1] +**Imagen:** Red privada 5G para streaming deportivo + +## + +## + +## + +## **Arquitectura de la red** + +La red 5G se distribuye geográficamente del siguiente modo: + +* **Core 5G (Open5GS sin UPF)** + Ubicación: instalaciones de EiTB en Donostia. + Funciones de control: + + * AMF + * SMF + * AUSF + * UDM + * NRF +* **UPF (Open5GS)** + Ubicación: San Mamés (edge). + Función: encaminamiento del tráfico de usuario. + +* **Radio gNB** + Ubicación: San Mamés. + Proporciona cobertura radio en el estadio. + +* **VPN (Mikrotik)** + Interconecta: + + * Core 5G ↔ UPF + de forma segura a través de red IP. + +## **Desarrollo del entrenamiento** + +A partir de una red privada 5G ya funcional (Día 1), se procederá a: + +* Separar el **User Plane Function (UPF)** del Core. +* Desplegar el UPF en una **ubicación remota**. +* Asegurar la conectividad mediante una VPN. +* Verificar el impacto de esta arquitectura en la latencia y el rendimiento. + +## **Parámetros de configuración** + +### **EQUIPO 1 – Core 5G (sin UPF)** + +## Parámetros principales a revisar y adaptar: + +* ## Dirección IP del Core. + +* ## Interfaces N2 y N4. + +* ## Asociación con SMF. + +* ## Eliminación del UPF local. + +* ## Definición de UPF remoto (IP, N4). + +## + +### **EQUIPO 2 – UPF remoto** + +* ## Dirección IP del UPF. + +* ## Interfaz N4 hacia el SMF. + +* ## Interfaz N3 hacia el gNB. + +* ## Enrutamiento del tráfico de usuario. + +* ## Salida hacia red local / Internet. + +### **Parámetros a configurar en la VPN (Mikrotik)** + +* ## Dirección IP local y remota. + +* ## Tipo de VPN (IPsec / WireGuard). + +* ## Rutas estáticas: + + * ## Core ↔ UPF + + * ## UPF ↔ gNB + +* ## Comprobación de conectividad IP extremo a extremo. + +### **Parámetros a revisar en la radio gNB** + +* ## Dirección IP del AMF + +* ## PLMN. + +* ## TAC. + +* ## gNB ID. + +* ## Asociaciones N2 / N3. + +### **1\. Esquema de red distribuida** + +Realiza un **esquema lógico** donde se represente: + +* Core 5G centralizado. +* UPF en el edge. +* gNB remoto. +* VPN entre sedes. +* Flujo del plano de control y del plano de usuario. + +**Resultado esperado:** + Diagrama claro que muestre la separación CP / UP. + +### **2\. Separación del UPF** + +Configura la red para que: + +* El Core 5G deje de manejar tráfico de usuario. +* El UPF remoto gestione el tráfico de datos. + + . + +### **3\. Verificación de funcionamiento** + +Comprobar: + +* Registro correcto del UE en red (NAS, AMF). +* Establecimiento de sesión PDU. +* Paso de tráfico IP a través del UPF remoto. + +Herramientas recomendadas: + +* Logs del Core y del UPF. +* Ping desde el UE. +* Traceroute. +* Capturas de tráfico. + +### **4\. Análisis de rendimiento y latencia** + +* Medir latencia y velocidad con: + * UPF cercano (edge). +* Comparar con: + * UPF centralizado (Día 1). + +Registrar resultados en una **tabla comparativa**. + +## **¿Qué pasa si…?** + +Analiza y documenta el comportamiento de la red en los siguientes casos: + +1. **Se pierde la VPN entre Core y UPF** + * ¿El UE sigue registrado? + * ¿Hay tráfico de datos? +2. **Se detiene el UPF remoto** + * ¿Qué ocurre con la sesión PDU? + * ¿Qué mensajes aparecen en el SMF? +3. **El gNB apunta a un UPF incorrecto** + * ¿Se registra el UE? + * ¿Hay conectividad IP? +4. **Aumenta la latencia entre Core y UPF** + * Impacto en el servicio. + * Servicios más afectados (vídeo vs datos). + +## **Conclusiones** + +Responder y justificar: + +* ¿Por qué es clave separar el UPF en escenarios de eventos? +* ¿Qué ventajas aporta una arquitectura distribuida? +* ¿Qué servicios se benefician más del edge computing? + +## **EXTRA** + +* Implementar un **radioenlace** (o simulación de enlace limitado) entre Core y UPF. +* Repetir las pruebas observando el impacto en: + * Throughput. + * Latencia. + * Calidad del vídeo. + +[image1]: img/reto2_image1.png \ No newline at end of file diff --git a/docs/RETOS/RETO3_ Network Slicing_EiTB.docx.md b/docs/RETOS/RETO3_ Network Slicing_EiTB.docx.md new file mode 100644 index 0000000..535cae9 --- /dev/null +++ b/docs/RETOS/RETO3_ Network Slicing_EiTB.docx.md @@ -0,0 +1,219 @@ + + +**CURSO INSTALACIÓN Y CONFIGURACIÓN DE REDES 5G** + +**“Caso de uso:Servicios diferenciados mediante Network Slicing en un evento deportivo de EiTB ”** + +## **Situación** + +Durante la retransmisión de un evento deportivo (por ejemplo, un partido de fútbol), EiTB necesita dar servicio a **distintos tipos de usuarios y aplicaciones** sobre la **misma infraestructura 5G**, pero con **requisitos muy diferentes**. +Algunos servicios son críticos y deben garantizar: + +* Baja latencia. +* Alta prioridad. +* Ancho de banda asegurado. + +Otros servicios pueden funcionar con: + +* Prioridad baja. +* Mejores esfuerzos (*best effort*). + +Para resolver este problema, EiTB implanta **Network Slicing** en su red privada 5G. + +## **Servicios del escenario** + +Se definen al menos **dos slices lógicos** sobre la red 5G existente: + +### **Slice 1 – *Staff / Internet corporativo*** + +* Usuarios: personal técnico y de producción. +* Dispositivos: móviles. +* Servicios: + * Acceso a Internet. + * Aplicaciones corporativas. +* Prioridad: media / baja. + + + ### **Slice 2 – *Producción de vídeo*** + +* Usuarios: cámaras y equipos de retransmisión. +* Dispositivos: routers 5G, cámaras IP. +* Servicios: + * Streaming de vídeo. + * Acceso a servidores internos de EiTB. +* Prioridad: alta. +* Baja latencia. +* Uplink priorizado. + ![][image1] + +**Imagen:** Red privada 5G con diferentes slices + +## **Arquitectura de la red** + +La arquitectura es una evolución directa de la del **Día 2**: + +* **Core 5G (Open5GS)** + * Funciones de control. + * Gestión de slices (S-NSSAI). + * Asociación SIM–slice. +* **UPF(s)** + * UPF compartido o UPF dedicado por slice. + * Políticas de tráfico diferenciadas. +* **gNB único** + * Emite una única red radio. + * Transporta múltiples slices simultáneamente. +* **SIMs configuradas por slice** + * Cada SIM se asocia a un APN y un slice específico. + + +## **Desarrollo del entrenamiento** + +Partiendo de la red con **UPF distribuido** ya operativa: + +* Se crearán **múltiples slices lógicos**. +* Se asignarán **distintos perfiles de servicio**. +* Se validará que: + * Dos UEs conectados a la misma celda. + * Reciben un comportamiento de red distinto. + + +## **Conceptos clave a trabajar** + +## Antes de iniciar la práctica, se introducirán los siguientes conceptos: + +* ## Network Slicing en 5G. + +* ## S-NSSAI: + + * ## SST (Slice/Service Type). + + * ## SD (Slice Differentiator). + +* ## Relación entre: + + * ## Slice. + + * ## APN. + + * ## UPF. + +* ## QoS y prioridades: + + * ## 5QI. + + * ## AMBR. + + * ## Políticas de tráfico. + + + +## **Parámetros de configuración** + +| Slice 1 – Staff / Internet Nombre del slice: Staff SST: SD: APN: AMBR: QoS / 5QI: | Slice 2 – Producción de vídeo Nombre del slice: Video SST: SD: APN: AMBR: QoS / 5QI: | +| :---- | :---- | + +## + +## + +## **Se pide:** + +### + +### **1\. Esquema de Network Slicing** + +Realiza un **esquema lógico** que muestre: + +* Un único gNB. +* Múltiples slices. +* Diferentes APNs. +* Asociación SIM → Slice → UPF. + +**Resultado esperado:** + Esquema claro de slicing sobre red privada 5G. + +### **2\. Creación de slices** + +Configura en el Core 5G: + +* Dos slices distintos. +* Identificados mediante S-NSSAI. +* Asociados a diferentes APNs. + +### **3\. Configuración de SIMs** + +* Crear o modificar SIMs existentes. +* Asociar cada SIM a: + * Un APN concreto. + * Un slice específico. + +**Preguntas:** + +* ¿Puede una SIM acceder a más de un slice? +* ¿Qué ocurre si el APN es incorrecto? + +### **4\. Verificación de funcionamiento** + +Para cada slice: + +* Comprobar registro en red. +* Establecimiento de sesión PDU. +* Acceso a servicios permitidos. + +Herramientas: + +* Test de velocidad. +* Ping. +* Acceso a servicios internos. +* Logs del Core y UPF. + +### **5\. Comparativa de rendimiento** + +Crear una **tabla comparativa** entre slices: + +* Velocidad (DL / UL). +* Latencia. +* Pérdida de paquetes. +* Acceso a recursos. + +## **¿Qué pasa si…?** + +Analiza y documenta: + +1. **Una SIM intenta usar un APN de otro slice** +2. **Se elimina un slice del Core** +3. **Dos slices comparten el mismo UPF** +4. **Un slice no tiene salida a Internet** +5. **Se degrada la prioridad del slice de vídeo** + +Explicar el impacto en el servicio percibido. + +## **Casos de uso industriales y empresariales** + +Relacionar lo aprendido con escenarios reales: + +* Producción audiovisual. +* Industria 4.0. +* Puertos y logística. +* Smart cities. +* Redes privadas empresariales. + +## **Conclusiones** + +Responder y justificar: + +* ¿Qué aporta Network Slicing frente a una red única? +* ¿Qué servicios se benefician más? +* ¿Por qué es clave para redes privadas 5G? + +## **EXTRA** + +* Implementar un **tercer slice**: + * IoT / sensores. + * Ancho de banda mínimo. + * Prioridad baja. +* Simular congestión en un slice y observar: + * Impacto en el resto. + * Aislamiento entre servicios. + +[image1]: img/reto3_image1.png \ No newline at end of file diff --git "a/docs/RETOS/RETO4_ Configuraci\303\263n de red 4Gmd" "b/docs/RETOS/RETO4_ Configuraci\303\263n de red 4Gmd" new file mode 100644 index 0000000..056dd67 --- /dev/null +++ "b/docs/RETOS/RETO4_ Configuraci\303\263n de red 4Gmd" @@ -0,0 +1,120 @@ + + +**CURSO INSTALACIÓN Y CONFIGURACIÓN DE REDES 5G** + +**“Configuración y comprobación de funcionamiento de una red privada 4G”** + +**Situación:** + +Se pretende **configurar y comprobar** el funcionamiento de una **red privada 4G** para un cliente que quiere cambiar su sistema inalámbrico basado en tecnología Wifi por otro que trabaje en frecuencias licenciadas para evitar cualquier mal funcionamiento por interferencias de otros servicios. + +![][image1] +**Imagen:** Red privada virtual 4G en fábrica de Renault desplegada por Telefónica + +**Desarrollo del entrenamiento:** + +Partiendo del equipamiento del Core, la radio eNB y los dispositivos de red y del terminal a entregar al cliente, se va a proceder a configurar los equipos para que se integren dentro de la red del cliente con una serie de parámetros que la identifiquen de forma única. + +Los parámetros a configurar se recogen en el siguiente cuadro: + +**EQUIPO1:** + +1. **Parámetros a configurar en el Core 4G:** +* **Nombre del Operador:** +* **PLMN:** + * **MCC**: + * **MNC:** +* **TAC:** + + +2. **Parámetros a configurar en la radio eNB:** + +* **Modo duplex:** +* **Ancho de banda:** +* **EARFCN:** +* **Subframe Assigment:** +* **Sector ID \= PCI (value between 0 – 553):** +* **eNB ID (hex)=** +* **ECI (value between 0 – 65535):** +* **Potencia:** +* **PLMN:** +* **TAC** + +**Se pide:** + +1. **Haz un esquema (mapa lógico sencillo) indicando los elementos que intervienen en la red privada celular 4G y sus correspondientes parámetros de red. *(TABLA I*)** + +2. **Cumplimentar los apartados indicados en la tabla adjunta con los valores recogidos con las apps. *(TABLA II)*** + +3. **Configurar la red privada celular 4G con los parámetros listados anteriormente.** + +4. **Comprueba el funcionamiento de la red privada celular 4G desde el lado del cliente haciendo uso de las herramientas necesarias para ello (Analizador espectral, Apps, test de velocidad, etc …)** + +5. **Realizar una tabla con las velocidades conseguidas, tras las modificaciones del ancho de banda y del subframe.** + +6. **Crear una nueva SIM para nuestra nueva red privada** + * **¿Qué APN has configurado?** + +7. **¿Qué pasa si….** + * **Cambiamos solo el TAC o PLMN en la radio/core? Mostrar el fallo** + * **Paramos el contenedor del SGWU?** + * **Nos movemos y perdemos cobertura?** + +8. **Realizar una SIM con mismo MCC pero diferente MNC: Analiza que nos indica el móvil** + + + +**EXTRA: Elaborar una documentación completa para el cliente, que tenga los siguientes apartados:** +**PORTADA** +**ÍNDICE** +**INSTALACIÓN DE LA RED PRIVADA: Datos necesarios para el cliente** +**CAMBIOS EN LA CONFIGURACIÓN: Posibles modificaciones para mejora de velocidades, dependiendo del uso final.** +**CONCLUSIONES: UEs conectados, troubleshooting** + +**Enlaces de consulta:** +[**https://5g-tools.com/4g-lte-cell-id-eci-calculator/**](https://5g-tools.com/4g-lte-cell-id-eci-calculator/) +[**https://www.cellmapper.net/enbid?lang=es**](https://www.cellmapper.net/enbid?lang=es) + +**CURSO INSTALACIÓN Y CONFIGURACIÓN DE REDES 5G** + +*Tabla I* + +| Elementos de la red privada Celular 4G |   | | | | +| :---- | ----- | :---- | ----- | :---- | +| **Sistema radiante** |   | | | | +| **RRU (Unidad de radio remota)** |   | | | | +| **BBU (Unidad de banda base)** |   | | | | +| **Core de la red** |   | | | | +| **Identificación de las Ips de la red privada celular 4G** | ** ** | | | | +| **Elemento** | **IP** | **Máscara** | **Puerta de enlace** | **DNS** | +| **eNB** |   |   |   |   | +| **Host del Core-físico** |   |   |   |   | +| **Core 4G** |   |   |   |   | +| **Terminal móvil** |   |   |   |   | + +| Datos del Operador | | | | | +| ----- | ----- | ----- | ----- | ----- | +| **Operador** | **MCC** | **MNC** | | | +| ** ** | ** ** | ** ** | | | +| **Datos de la celda a la que está conectado el terminal** | | | | | +| **Tipo de celda/Tecnología** | **TAC** | **ECI** | **eNB ID** | **Physical Cell ID (PCI)** | +| ** ** | ** ** | ** ** | ** ** | ** ** | +| **EARFCN DOWN/UP** | **FREQ DOWN/UP** | **BANDA** | **FDD/TDD** | | +| ** ** | ** ** | ** ** | ** ** | | +| **Parámetros de Radiofrecuencia** | | | | | +| **RSSI** | **RSRP** | **RSRQ** | **SINR** | **ASU** | +| ** ** | ** ** | ** ** | ** ** | ** ** | +| **Posicionamiento terminal** | | | | | +| **Latitud** | **Longitud** | | | | +| ** ** | ** ** | | | | +| **Posicionamiento torre** | | | | | +| **Latitud** | **Longitud** | | | | +| ** ** | ** ** | | | | +| **Rendimiento de la red privada celular** | | | | | +| **Velocidad del downlink** | **Velocidad del uplink** | **Tiempo del ping** | **Jitter** | | +|   |   |   |   | | +| **Otros parámetros importantes** | | | | | +| **APN** | ** ** | | | | +| **IMSI** | ** ** | | | | + +[image1]: img/reto4_image1.png \ No newline at end of file diff --git a/docs/RETOS/img/reto1_image1.png b/docs/RETOS/img/reto1_image1.png new file mode 100644 index 0000000..d68dbab Binary files /dev/null and b/docs/RETOS/img/reto1_image1.png differ diff --git a/docs/RETOS/img/reto2_image1.png b/docs/RETOS/img/reto2_image1.png new file mode 100644 index 0000000..cf7977e Binary files /dev/null and b/docs/RETOS/img/reto2_image1.png differ diff --git a/docs/RETOS/img/reto3_image1.png b/docs/RETOS/img/reto3_image1.png new file mode 100644 index 0000000..14d3bb7 Binary files /dev/null and b/docs/RETOS/img/reto3_image1.png differ diff --git a/docs/RETOS/img/reto4_image1.png b/docs/RETOS/img/reto4_image1.png new file mode 100644 index 0000000..894acba Binary files /dev/null and b/docs/RETOS/img/reto4_image1.png differ diff --git a/docs/index.md b/docs/index.md index dd6974f..6ad34a2 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1 +1,6 @@ -# Welcome \ No newline at end of file +# ONGI ETORRI +Integración de las redes 5G en FPEuskadi y uso de la nube para mejorar el desarrollo de aplicaciones. +Enlace página web Tknika: + +[TKNIKA COMUNICACIONES 5G](https://tknika.eus/cont/proyectos/comunicaciones-y-computacion-en-la-nube/) +