GotOpinion - User contributions [en]

My MediaWiki notes

2026-07-19T18:36:55Z

Paul: update from 1.43.1 to 1.46.0

== Getting started ==

* [https://meta.wikimedia.org/wiki/Help:Wikitext_examples Wikitext Examples]
* [https://meta.wikimedia.org/wiki/Help:Advanced_editing Wikitext Advanced Editing]
* [https://www.mediawiki.org/wiki/Help:Images Images help]
* [https://meta.wikimedia.org/wiki/Wiki_color_formatting_help Wiki color formatting help]
* [https://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]
* [https://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Manual:%24wgGroupPermissions wgGroupPermissions]
* [https://www.mediawiki.org/wiki/Backup MediaWiki backup]
* [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Lists List Manual Style]

== Resources ==

[[Preventing access]] in MediaWiki

[https://www.mediawiki.org/wiki/Extension:WikiEditor WikiEditor] extension

[https://www.mediawiki.org/wiki/Extension:WikiEditor/Toolbar_customization WikiEditor toolbar customization] (plan to add code, pre, and a few more buttons)

[http://www.mediawiki.org/wiki/Extension:HeadScript HeadScript] extension

Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== My upgrade notes ==

Before starting upgrade (2026-07):
<pre>MediaWiki 1.43.1
PHP 8.4.20 (cgi-fcgi)
ICU 74.2
MySQL 8.0.41-0ubuntu0.24.04.1</pre>After upgrade (2026-07):
{| class="wikitable"
|MediaWiki
|1.46.0
|-
|PHP
|8.4.20 (cgi-fcgi)
|-
|ICU
|74.2
|-
|MySQL
|8.0.41-0ubuntu0.24.04.1
|}

<pre># Upgrading MediaWiki 1.43 to 1.46
# Follow steps at https://www.mediawiki.org/wiki/Manual:Upgrading
# with deviations and notes below

# Go to wiki root directory (example uses wiki.gotopinion.info)
cd /home/<myusername>/wiki.gotopinion.info

# MediaWiki uses:
mysqldump --opt --user=wikidb_user --password wikidb --no-tablespaces wikidb > file.sql
mysqldump --opt --user=wikidb_user --password=wikidb_userpassword wikidb --no-tablespaces --xml > file.xml

# Dreamhost requires some extra parameters, command format I used
mysqldump --opt --user=wikidb_user --password --host=wikidb_host wikidb --no-tablespaces wikidb > mediawiki-1.43.1.sql
mysqldump --opt --user=wikidb_user --password --host=wikidb_host wikidb --no-tablespaces --xml > mediawiki-1.43.1.xml

# copy LocalSettings.php

cp wiki/LocalSettings.php LocalSettings.php.20260719.bak

# copy .htaccess
cp .htaccess .htaccess.bak

# Make a complete copy of current wiki directory
tar -cvzf mediawiki-1.43.1.tar.gz wiki/

# Download MediaWiki 1.46.0
wget https://releases.wikimedia.org/mediawiki/1.46/mediawiki-1.46.0.tar.gz

# untar and decompress file
tar xvfz mediawiki-1.46.0.tar.gz

# remove the file
rm mediawiki-1.46.0.tar.gz

# move previous wiki to new directory
mv wiki wiki_v1.43.1_old

# move new wiki files to wiki
mv mediawiki-1.46.0 wiki

# move LocalSettings.php from old to new
cp wiki_v1.43.1_old/LocalSettings.php wiki/

# move images from old to new
cp -r wiki_v1.43.1_old/images/* wiki/images/

# execute run.php script
/usr/local/php84/bin/php maintenance/run.php update.php</pre>

<center>[[Main Page|To Main Page]]</center>

My MediaWiki notes

2026-07-19T17:54:27Z

Paul: /* My upgrade notes */

Dreamhost

2026-07-19T17:02:58Z

Paul:

[https://panel.dreamhost.com/ Sign Up] for DreamHost Web ID.

[[Domain Name Registration Steps]]

[[Quicktime Streaming]]

== Dreamhost Mediawiki notes ==

If wiki in wiki directory and upgrading from 1.43.1

Copy wiki:

<pre>cp -r ./mediawiki-1.43.1/* ./wiki</pre>

Run update script from wiki directory:

<pre>php ./wiki/maintenance/run.php update</pre>

Dreamhost

2026-07-19T16:12:02Z

Paul: /* Dreamhost Mediawiki notes */

My MediaWiki notes

2026-07-19T15:51:25Z

Paul: /* My upgrade notes */

My MediaWiki notes

2026-07-19T15:50:51Z

Paul: /* My upgrade notes */

My MediaWiki notes

2026-07-19T15:50:06Z

Paul: added upgrade notes section

My Byobu notes

2026-07-19T15:47:01Z

Paul: /* Using Byobu */

== Byobu notes ==

These notes were originally taken while using Ubuntu Desktop 18.04.1 LTS.

Some notes were updated with Ubuntu Server 22.04.3.

=== Byobu resources ===

[https://www.digitalocean.com/community/tutorials/how-to-install-and-use-byobu-for-terminal-management-on-ubuntu-16-04 How to install and use Byobu for terminal management] on Ubuntu 16-04.

== Verify or install Byobu ==

Verify whether Byobu is installed (July 2026 result):

<pre>$ byobu --version
byobu version 6.11
tmux 3.4</pre>

If you do not get a version install Byobu with <code>sudo apt-get install byobu</code>

== Start Byobu at login ==

You can start Byobu manually every time you want to use Byobu or automatically at login.

To manually start Byobu type <code>byobu</code> at prompt.

To automatically start at login type <code>byobu-enable</code> at prompt.

<pre>$ byobu-enable

The Byobu window manager will be launched automatically at each text login.

To disable this behavior later, just run:
byobu-disable
</pre>

If you want to disable automatic use of Byobu type <code>byobu-disable</code> at prompt.

== Byobu help ==

Press Shift + F1.

Current help output
<pre>Byobu is a suite of enhancements to tmux, as a command line
tool providing live system status, dynamic window management,
and some convenient keybindings:

F1 * Used by X11 *
Shift-F1 Display this help
F2 Create a new window
Shift-F2 Create a horizontal split
Ctrl-F2 Create a vertical split
Ctrl-Shift-F2 Create a new session
F3/F4 Move focus among windows
Alt-Left/Right Move focus among windows
Alt-Up/Down Move focus among sessions
Shift-Left/Right/Up/Down Move focus among splits
Shift-F3/F4 Move focus among splits
Ctrl-F3/F4 Move a split
Ctrl-Shift-F3/F4 Move a window
Shift-Alt-Left/Right/Up/Down Resize a split
F5 Reload profile, refresh status
Alt-F5 Toggle UTF-8 support, refresh status
Shift-F5 Toggle through status lines
Ctrl-F5 Reconnect ssh/gpg/dbus sockets
Ctrl-Shift-F5 Change status bar's color randomly
F6 Detach session and then logout
Shift-F6 Detach session and do not logout
Alt-F6 Detach all clients but yourself
Ctrl-F6 Kill split in focus
F7 Enter scrollback history
Alt-PageUp/PageDown Enter and move through scrollback
Shift-F7 Save history to $BYOBU_RUN_DIR/printscreen
F8 Rename the current window
Ctrl-F8 Rename the current session
Shift-F8 Toggle through split arrangements
Alt-Shift-F8 Restore a split-pane layout
Ctrl-Shift-F8 Save the current split-pane layout
F9 Launch byobu-config window
Ctrl-F9 Enter command and run in all windows
Shift-F9 Enter command and run in all splits
Alt-F9 Toggle sending keyboard input to all splits
F10 * Used by X11 *
F11 * Used by X11 *
Alt-F11 Expand split to a full window
Shift-F11 Zoom into a split, zoom out of a split
Ctrl-F11 Join window into a vertical split
F12 Escape sequence
Shift-F12 Toggle on/off Byobu's keybindings
Alt-F12 Toggle on/off Byobu's mouse support
Ctrl-Shift-F12 Mondrian squares
(END)</pre>

== Using Byobu ==

To move tmux status bar on top of terminal window edit <code>.tmux.conf</code> file using one of the following commands.

Following modern XDG standard
<pre>$ echo "set-option -g status-position top" >> ~/.config/byobu/.tmux.conf</pre>

Legacy standard
<pre>$ echo "set-option -g status-position top" >> ~/.byobu/.tmux.conf</pre>

<center>[[Linux|To Linux]]</center>

My Byobu notes

2026-07-19T15:38:51Z

Paul: /* Verify or install Byobu */

== Byobu notes ==

These notes were originally taken while using Ubuntu Desktop 18.04.1 LTS.

Some notes were updated with Ubuntu Server 22.04.3.

=== Byobu resources ===

[https://www.digitalocean.com/community/tutorials/how-to-install-and-use-byobu-for-terminal-management-on-ubuntu-16-04 How to install and use Byobu for terminal management] on Ubuntu 16-04.

== Verify or install Byobu ==

Verify whether Byobu is installed (July 2026 result):

<pre>$ byobu --version
byobu version 6.11
tmux 3.4</pre>

If you do not get a version install Byobu with <code>sudo apt-get install byobu</code>

== Start Byobu at login ==

You can start Byobu manually every time you want to use Byobu or automatically at login.

To manually start Byobu type <code>byobu</code> at prompt.

To automatically start at login type <code>byobu-enable</code> at prompt.

<pre>$ byobu-enable

The Byobu window manager will be launched automatically at each text login.

To disable this behavior later, just run:
byobu-disable
</pre>

If you want to disable automatic use of Byobu type <code>byobu-disable</code> at prompt.

== Byobu help ==

Press Shift + F1.

Current help output
<pre>Byobu is a suite of enhancements to tmux, as a command line
tool providing live system status, dynamic window management,
and some convenient keybindings:

F1 * Used by X11 *
Shift-F1 Display this help
F2 Create a new window
Shift-F2 Create a horizontal split
Ctrl-F2 Create a vertical split
Ctrl-Shift-F2 Create a new session
F3/F4 Move focus among windows
Alt-Left/Right Move focus among windows
Alt-Up/Down Move focus among sessions
Shift-Left/Right/Up/Down Move focus among splits
Shift-F3/F4 Move focus among splits
Ctrl-F3/F4 Move a split
Ctrl-Shift-F3/F4 Move a window
Shift-Alt-Left/Right/Up/Down Resize a split
F5 Reload profile, refresh status
Alt-F5 Toggle UTF-8 support, refresh status
Shift-F5 Toggle through status lines
Ctrl-F5 Reconnect ssh/gpg/dbus sockets
Ctrl-Shift-F5 Change status bar's color randomly
F6 Detach session and then logout
Shift-F6 Detach session and do not logout
Alt-F6 Detach all clients but yourself
Ctrl-F6 Kill split in focus
F7 Enter scrollback history
Alt-PageUp/PageDown Enter and move through scrollback
Shift-F7 Save history to $BYOBU_RUN_DIR/printscreen
F8 Rename the current window
Ctrl-F8 Rename the current session
Shift-F8 Toggle through split arrangements
Alt-Shift-F8 Restore a split-pane layout
Ctrl-Shift-F8 Save the current split-pane layout
F9 Launch byobu-config window
Ctrl-F9 Enter command and run in all windows
Shift-F9 Enter command and run in all splits
Alt-F9 Toggle sending keyboard input to all splits
F10 * Used by X11 *
F11 * Used by X11 *
Alt-F11 Expand split to a full window
Shift-F11 Zoom into a split, zoom out of a split
Ctrl-F11 Join window into a vertical split
F12 Escape sequence
Shift-F12 Toggle on/off Byobu's keybindings
Alt-F12 Toggle on/off Byobu's mouse support
Ctrl-Shift-F12 Mondrian squares
(END)</pre>

== Using Byobu ==

Put tmux status bar on top of terminal window. Modify or create file ~/.byobu/.tmux.conf and put these commands in file:

<pre>set -g status-position top</pre>

<center>[[Linux|To Linux]]</center>

Ubuntu

2026-07-19T15:34:54Z

Paul: /* CLI Software Management */

== Shell commands ==

Enable root account (not recommended):
<pre>$sudo passwd root</pre>

Disable root account you lock root account:
<pre>$sudo passwd -l root</pre>

Want to use root @ console:
<pre>$sudo -i</pre>

[https://help.ubuntu.com/community/WindowsDualBoot Windows Dual Boot] page

[https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows Recovering Ubuntu After Windows Install]

[https://wiki.ubuntu.com/Grub2 Grub2] on Ubuntu wiki

[http://www.howtogeek.com/howto/43471/how-to-configure-the-linux-grub2-boot-menu-the-easy-way/ Grub2 GUI] Customizer

For support-related question you can use [https://answers.launchpad.net/ Launchpad]. You can also search the complete history of questions and answers.

[http://ubuntuforums.org/ Ubuntu web forums]

[http://ubuntuforums.org/showthread.php?t=1195275 Grub 2] basics

=== Enable SSH server ===

<code>apt-get install openssh-server</code>

[https://coderwall.com/p/yz-2_a/limit-ssh-access-by-ip-address Secure SSH server using /etc/hosts.allow]

=== Add a User ===

Example adding a user with username johndoe. Follow the instructions provided by the command.

<code>sudo adduser johndoe</code>

==== sudo group stuff ====

Add user to sudo group

<code>sudo usermod -aG sudo <USER_NAME></code>

Verify user belongs to sudo group

<code>groups <USER_NAME></code>

Verify sudo access

<code>su - <USER_NAME></code>

Remove user from sudo group

<code>sudo deluser <USER_NAME> sudo</code>

=== Networking utilities ===

See IP address information

<code>ip a</code>

==== Configure hostname ====

[https://linuxize.com/post/how-to-change-hostname-on-ubuntu-18-04/ How to change hostname on Ubuntu 18 04]

==== systemctl ====

Verify which processes run on Ubuntu 18.04 start up use <code>$ sudo systemctl list-unit-files</code>.

=== Check version of Ubuntu ===

One way:
<code>$ cat /etc/os-release</code>

Another way, ran this on 2026-07 before upgrading release:
<pre>$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy</pre>

== CLI Software Management ==

Synchronize package index from Internet. Location of repositories <code>/etc/apt/sources.list</code>
<pre>sudo apt update</pre>
Install newest versions of all software packages
<pre>sudo apt upgrade</pre>
Update distribution
<pre>sudo apt-get dist-upgrade</pre>
Install package (if already installed, will attempt to update package)
<pre>apt-get install package-name</pre>
List installed packages
<pre>apt list --installed</pre>

List installed packages that start with 'python'
<pre>$ apt list -a --installed python*</pre>

To upgrade Ubuntu release, see [https://ubuntu.com/server/docs/how-to-upgrade-your-release How To Upgrade Your Release]

Update packages and upgrade packages
<pre>sudo apt update && sudo apt upgrade -y</pre>

Remove unnecessary packages
<pre>sudo apt autoremove</pre>

Update, upgrade, and remove unused packages before updating Ubuntu release!
<pre>sudo do-release-upgrade</pre>

== Python on Ubuntu Notes ==

See [[ Python | My Python Notes]] for information not specific to Ubuntu and Python.

Verify Python 3 is installed
<pre>anon@hammerhead:~$ python --version

Command 'python' not found, but can be installed with:

sudo apt install python3
sudo apt install python
sudo apt install python-minimal

You also have python3 installed, you can run 'python3' instead.

anon@hammerhead:~$ python3 --version <----- Python 3 installed.
Python 3.6.7 <----- Version 3.6.7</pre>

Verify Python 3 PIP installed
<pre>$ pip3 --version
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6)</pre>

To install Python 3 PIP
<pre>$ sudo apt-get install -y python3-pip</pre>

I use Python virtual environments. Verify Python venv module is installed
<pre>$ apt list -a --installed *venv* <----- If nothing with Python 3 venv comes back then you most install venv module</pre>

To install Python 3 venv module
<pre>$ sudo apt-get install -y python3-venv</pre>

Create virtual environment. I keep my Python virtual environments in a single directory. To create directory <code>$ mkdir python-venv</code>

Switch do directory <code>$ cd python-venv/</code>

Create virtual environment
<pre>$ python3 -m venv udmey-django</pre>

Activate virtual environment
<pre>$ source udmey-django/bin/activate</pre>

Prompt changes to reflect virtual environment
<pre>(udmey-django) anon@hammerhead:~/python-venv$</pre>

Note: Within virtual environment, you can use the command python instead of python3, and pip instead of pip3.

Deactivate virtual environment and prompt returns to normal
<pre>$ deactivate</pre>

== mongoDB ==

[[My MongoDB notes]]

== PostgreSQL ==

=== Install PostgreSQL ===

<pre>$ sudo apt install postgresql postgresql-contrib
...
Success. You can now start the database server using:

/usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/main -l logfile start

Ver Cluster Port Status Owner Data directory Log file
10 main 5432 down postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
update-alternatives: using /usr/share/postgresql/10/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Setting up postgresql (10+190) ...
Setting up postgresql-contrib (10+190) ...
Processing triggers for systemd (237-3ubuntu10.11) ...
Processing triggers for ureadahead (0.100.0-20) ...</pre>

=== Use PostgreSQL ===

Switch to postgres account
<pre>sudo -i postgres</pre>
Access PostgreSQL prompt
<pre>psql</pre>
Exit PostgreSQL prompt
<pre>\q</pre>
Log directly into PostgreSQL prompt with postgres user
<pre>sudo -u postgres psql</pre>
Add user (username must be same as PostgreSQL role and database)
<pre>sudo adduser user_name</pre>
Check current connection information
<pre>\conninfo</pre>

While logged in as postgres user...

Create a new role. Use <code>man createuser</code> for more information.
<pre>createuser --interactive</pre>
Create new database
<pre>createdb db_name</pre>
Same user connect to different database
<pre>psql -d postgres</pre>

== Nginx ==

[[My Nginx notes]]

[https://www.tecmint.com/install-nginx-with-virtual-hosts-and-ssl-certificate/ Install Nginx with virtual hosts and SSL certificates]

== Apache 2 ==

=== Resources ===

[https://help.ubuntu.com/lts/serverguide/httpd.html Ubuntu server guide to HTTPD]

[https://help.ubuntu.com/community/OpenSSL#SSL_Certificates Ubuntu Open SSL guide]

[https://help.ubuntu.com/lts/serverguide/certificates-and-security.html.en Ubuntu Certificates and Security]

[http://tldp.org/HOWTO/SSL-Certificates-HOWTO/index.html SSL Certificate HOWTO] not Ubuntu specific

[https://stuff-things.net/2015/09/28/configuring-apache-for-ssl-client-certificate-authentication/ Configure Apache for SSL client certificate authentication]

=== Installation ===

Update all your software and install Apache 2

<pre># apt-get update
# apt-get upgrade
# apt install apache2</pre>

Verify Apache is running
<pre># systemctl status apache2
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: active (running) since Sun 2018-10-21 14:44:30 CDT; 11min ago
Main PID: 17131 (apache2)
Tasks: 55 (limit: 4181)
CGroup: /system.slice/apache2.service
├─17131 /usr/sbin/apache2 -k start
├─17132 /usr/sbin/apache2 -k start
└─17134 /usr/sbin/apache2 -k start

Oct 21 14:44:30 apu02 systemd[1]: Starting The Apache HTTP Server...
Oct 21 14:44:30 apu02 apachectl[17120]: AH00558: apache2: Could not reliably determine the server's
Oct 21 14:44:30 apu02 systemd[1]: Started The Apache HTTP Server.</pre>

=== Firewall ===

Update firewall to allow only port 443 (default HTTPS TCP port)

<pre># ufw app list
Available applications:
Apache
Apache Full
Apache Secure
OpenSSH

# ufw allow 'Apache Secure'

# ufw status verbose | grep 443
443/tcp (Apache Secure) ALLOW IN Anywhere
443/tcp (Apache Secure (v6)) ALLOW IN Anywhere (v6)</pre>

== Teamspeak 3 setup on Ubuntu 16.04 and 18.x via command line ==
Followed steps at [https://www.vultr.com/docs/how-to-install-teamspeak-3-server-on-ubuntu-16-04-64-bit How to install Teamspeak 3 server on Ubuntu 16.04 64-bit] to install Teamspeak 3 and get basic server running.

If you want to customize the server port follow next steps.

Install simple command-line program named [https://www.sqlite.org/cli.html sqlite3]. [https://www.sitepoint.com/getting-started-sqlite3-basic-commands/ How to use sqlite]

<pre>robot00@apu00:~$ sudo apt install sqlite3</pre>

Launch sqlite3 using Teamspeak 3 sqlite database file:

<pre>robot00@apu00:~$ sudo sqlite3 /home/teamspeak/ts3server.sqlitedb
SQLite version 3.11.0 2016-02-15 17:29:24
Enter ".help" for usage hints.</pre>

Update port command:

<pre>sqlite> update servers set server_port=<CUSTOM UDP Port>;</pre>

Restart Teamspeak 3 server

<pre>robot00@apu00:~$ systemctl restart teamspeak.service</pre>

Test your connection using the <CUSTOM UDP Port>

=== Upgrade Teamspeak3 server ===

[https://www.gazblog.com/2019/01/update-teamspeak-3-server-on-ubuntu-18-04/ original steps]

Login to SSH as root

Stop your current Teamspeak 3 Server <code>systemctl stop teamspeak.service</code>

Change to your teamspeak user <code>cd /home/teamspeak/;su teamspeak</code>

Download Teamspeak, extract it, update and tidy up.
<pre>wget https://files.teamspeak-services.com/releases/server/3.9.1/teamspeak3-server_linux_amd64-3.9.1.tar.bz2
tar xvfj teamspeak3-server_linux_amd64-3.9.1.tar.bz2
cd teamspeak3-server_linux_amd64
cp * -R /home/teamspeak
cd ..
rm -r teamspeak3-server_linux_amd64
rm teamspeak3-server_linux_amd64-3.9.1.tar.bz2</pre>

Return to root and start the Teamspeak server
<pre>exit
systemctl start teamspeak.service
</pre>

Check to make you can connect to Teamspeak 3 server

== Factorio Headless Setup ==

[[My Factorio Info]]

== Hardware ==

Identify video card:
<pre>paul@congo:~$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2)</pre>

Verify interface speed

<code>cat /sys/class/net/<interface>/speed</code>

replace <interface> with name of your NIC (e.g. eth0)

[[Ubuntu video card]]

=== Resizing logical volume ===

Background

A 2 TB SSD was physically installed in the system ox and after installation, the LVM used 100 GB.

Reference [https://community.spiceworks.com/topic/2325763-how-can-i-make-ubuntu-vg-ubuntu-lv-consume-the-entire-disk-space-available How To Make ubuntu-vg-ubuntu-lv Use 100% Free Disc Space]

<pre>anon@ox:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p3 ubuntu-vg lvm2 a-- <1.82t <1.72t

anon@ox:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wz--n- <1.82t <1.72t

anon@ox:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- 100.00g # <----------- This shows 100 GB and I want 1.8T.

anon@ox:~$ sudo lvresize -l +100%FREE /dev/ubuntu-vg/ubuntu-lv

Size of logical volume ubuntu-vg/ubuntu-lv changed from 100.00 GiB (25600 extents) to <1.82 TiB (476150 extents).
Logical volume ubuntu-vg/ubuntu-lv successfully resized.

anon@ox:~$ sudo resize2fs /dev/ubuntu-vg/ubuntu-lv

resize2fs 1.46.5 (30-Dec-2021)
Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
old_desc_blocks = 13, new_desc_blocks = 233
The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 487577600 (4k) blocks long.

anon@ox:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p3 ubuntu-vg lvm2 a-- <1.82t 0

anon@ox:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wz--n- <1.82t 0

anon@ox:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- <1.82t # <----------- This was 100 GB Size, now it's 1.8T.

anon@ox:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 6.3G 1.9M 6.3G 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 1.8T 37G 1.7T 3% / # <----------- This was 100 GB Size, now it's 1.8T.
tmpfs 32G 200K 32G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/nvme0n1p2 2.0G 252M 1.6G 14% /boot
/dev/nvme0n1p1 1.1G 6.1M 1.1G 1% /boot/efi
tmpfs 6.3G 4.0K 6.3G 1% /run/user/1001
tmpfs 6.3G 4.0K 6.3G 1% /run/user/1000</pre>

<center>[[Linux|To Linux]]</center>

Ubuntu

2026-07-19T15:32:15Z

Paul: /* Check version of Ubuntu */

== Shell commands ==

Enable root account (not recommended):
<pre>$sudo passwd root</pre>

Disable root account you lock root account:
<pre>$sudo passwd -l root</pre>

Want to use root @ console:
<pre>$sudo -i</pre>

[https://help.ubuntu.com/community/WindowsDualBoot Windows Dual Boot] page

[https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows Recovering Ubuntu After Windows Install]

[https://wiki.ubuntu.com/Grub2 Grub2] on Ubuntu wiki

[http://www.howtogeek.com/howto/43471/how-to-configure-the-linux-grub2-boot-menu-the-easy-way/ Grub2 GUI] Customizer

For support-related question you can use [https://answers.launchpad.net/ Launchpad]. You can also search the complete history of questions and answers.

[http://ubuntuforums.org/ Ubuntu web forums]

[http://ubuntuforums.org/showthread.php?t=1195275 Grub 2] basics

=== Enable SSH server ===

<code>apt-get install openssh-server</code>

[https://coderwall.com/p/yz-2_a/limit-ssh-access-by-ip-address Secure SSH server using /etc/hosts.allow]

=== Add a User ===

Example adding a user with username johndoe. Follow the instructions provided by the command.

<code>sudo adduser johndoe</code>

==== sudo group stuff ====

Add user to sudo group

<code>sudo usermod -aG sudo <USER_NAME></code>

Verify user belongs to sudo group

<code>groups <USER_NAME></code>

Verify sudo access

<code>su - <USER_NAME></code>

Remove user from sudo group

<code>sudo deluser <USER_NAME> sudo</code>

=== Networking utilities ===

See IP address information

<code>ip a</code>

==== Configure hostname ====

[https://linuxize.com/post/how-to-change-hostname-on-ubuntu-18-04/ How to change hostname on Ubuntu 18 04]

==== systemctl ====

Verify which processes run on Ubuntu 18.04 start up use <code>$ sudo systemctl list-unit-files</code>.

=== Check version of Ubuntu ===

One way:
<code>$ cat /etc/os-release</code>

Another way, ran this on 2026-07 before upgrading release:
<pre>$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy</pre>

== CLI Software Management ==

Synchronize package index from Internet. Location of repositories <code>/etc/apt/sources.list</code>
<pre>sudo apt update</pre>
Install newest versions of all software packages
<pre>sudo apt upgrade</pre>
Update distribution
<pre>sudo apt-get dist-upgrade</pre>
Install package (if already installed, will attempt to update package)
<pre>apt-get install package-name</pre>
List installed packages
<pre>apt list --installed</pre>

List installed packages that start with 'python'
<pre>$ apt list -a --installed python*</pre>

To upgrade Ubuntu release, see [https://ubuntu.com/server/docs/how-to-upgrade-your-release How To Upgrade Your Release]

== Python on Ubuntu Notes ==

See [[ Python | My Python Notes]] for information not specific to Ubuntu and Python.

Verify Python 3 is installed
<pre>anon@hammerhead:~$ python --version

Command 'python' not found, but can be installed with:

sudo apt install python3
sudo apt install python
sudo apt install python-minimal

You also have python3 installed, you can run 'python3' instead.

anon@hammerhead:~$ python3 --version <----- Python 3 installed.
Python 3.6.7 <----- Version 3.6.7</pre>

Verify Python 3 PIP installed
<pre>$ pip3 --version
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6)</pre>

To install Python 3 PIP
<pre>$ sudo apt-get install -y python3-pip</pre>

I use Python virtual environments. Verify Python venv module is installed
<pre>$ apt list -a --installed *venv* <----- If nothing with Python 3 venv comes back then you most install venv module</pre>

To install Python 3 venv module
<pre>$ sudo apt-get install -y python3-venv</pre>

Create virtual environment. I keep my Python virtual environments in a single directory. To create directory <code>$ mkdir python-venv</code>

Switch do directory <code>$ cd python-venv/</code>

Create virtual environment
<pre>$ python3 -m venv udmey-django</pre>

Activate virtual environment
<pre>$ source udmey-django/bin/activate</pre>

Prompt changes to reflect virtual environment
<pre>(udmey-django) anon@hammerhead:~/python-venv$</pre>

Note: Within virtual environment, you can use the command python instead of python3, and pip instead of pip3.

Deactivate virtual environment and prompt returns to normal
<pre>$ deactivate</pre>

== mongoDB ==

[[My MongoDB notes]]

== PostgreSQL ==

=== Install PostgreSQL ===

<pre>$ sudo apt install postgresql postgresql-contrib
...
Success. You can now start the database server using:

/usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/main -l logfile start

Ver Cluster Port Status Owner Data directory Log file
10 main 5432 down postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
update-alternatives: using /usr/share/postgresql/10/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Setting up postgresql (10+190) ...
Setting up postgresql-contrib (10+190) ...
Processing triggers for systemd (237-3ubuntu10.11) ...
Processing triggers for ureadahead (0.100.0-20) ...</pre>

=== Use PostgreSQL ===

Switch to postgres account
<pre>sudo -i postgres</pre>
Access PostgreSQL prompt
<pre>psql</pre>
Exit PostgreSQL prompt
<pre>\q</pre>
Log directly into PostgreSQL prompt with postgres user
<pre>sudo -u postgres psql</pre>
Add user (username must be same as PostgreSQL role and database)
<pre>sudo adduser user_name</pre>
Check current connection information
<pre>\conninfo</pre>

While logged in as postgres user...

Create a new role. Use <code>man createuser</code> for more information.
<pre>createuser --interactive</pre>
Create new database
<pre>createdb db_name</pre>
Same user connect to different database
<pre>psql -d postgres</pre>

== Nginx ==

[[My Nginx notes]]

[https://www.tecmint.com/install-nginx-with-virtual-hosts-and-ssl-certificate/ Install Nginx with virtual hosts and SSL certificates]

== Apache 2 ==

=== Resources ===

[https://help.ubuntu.com/lts/serverguide/httpd.html Ubuntu server guide to HTTPD]

[https://help.ubuntu.com/community/OpenSSL#SSL_Certificates Ubuntu Open SSL guide]

[https://help.ubuntu.com/lts/serverguide/certificates-and-security.html.en Ubuntu Certificates and Security]

[http://tldp.org/HOWTO/SSL-Certificates-HOWTO/index.html SSL Certificate HOWTO] not Ubuntu specific

[https://stuff-things.net/2015/09/28/configuring-apache-for-ssl-client-certificate-authentication/ Configure Apache for SSL client certificate authentication]

=== Installation ===

Update all your software and install Apache 2

<pre># apt-get update
# apt-get upgrade
# apt install apache2</pre>

Verify Apache is running
<pre># systemctl status apache2
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: active (running) since Sun 2018-10-21 14:44:30 CDT; 11min ago
Main PID: 17131 (apache2)
Tasks: 55 (limit: 4181)
CGroup: /system.slice/apache2.service
├─17131 /usr/sbin/apache2 -k start
├─17132 /usr/sbin/apache2 -k start
└─17134 /usr/sbin/apache2 -k start

Oct 21 14:44:30 apu02 systemd[1]: Starting The Apache HTTP Server...
Oct 21 14:44:30 apu02 apachectl[17120]: AH00558: apache2: Could not reliably determine the server's
Oct 21 14:44:30 apu02 systemd[1]: Started The Apache HTTP Server.</pre>

=== Firewall ===

Update firewall to allow only port 443 (default HTTPS TCP port)

<pre># ufw app list
Available applications:
Apache
Apache Full
Apache Secure
OpenSSH

# ufw allow 'Apache Secure'

# ufw status verbose | grep 443
443/tcp (Apache Secure) ALLOW IN Anywhere
443/tcp (Apache Secure (v6)) ALLOW IN Anywhere (v6)</pre>

== Teamspeak 3 setup on Ubuntu 16.04 and 18.x via command line ==
Followed steps at [https://www.vultr.com/docs/how-to-install-teamspeak-3-server-on-ubuntu-16-04-64-bit How to install Teamspeak 3 server on Ubuntu 16.04 64-bit] to install Teamspeak 3 and get basic server running.

If you want to customize the server port follow next steps.

Install simple command-line program named [https://www.sqlite.org/cli.html sqlite3]. [https://www.sitepoint.com/getting-started-sqlite3-basic-commands/ How to use sqlite]

<pre>robot00@apu00:~$ sudo apt install sqlite3</pre>

Launch sqlite3 using Teamspeak 3 sqlite database file:

<pre>robot00@apu00:~$ sudo sqlite3 /home/teamspeak/ts3server.sqlitedb
SQLite version 3.11.0 2016-02-15 17:29:24
Enter ".help" for usage hints.</pre>

Update port command:

<pre>sqlite> update servers set server_port=<CUSTOM UDP Port>;</pre>

Restart Teamspeak 3 server

<pre>robot00@apu00:~$ systemctl restart teamspeak.service</pre>

Test your connection using the <CUSTOM UDP Port>

=== Upgrade Teamspeak3 server ===

[https://www.gazblog.com/2019/01/update-teamspeak-3-server-on-ubuntu-18-04/ original steps]

Login to SSH as root

Stop your current Teamspeak 3 Server <code>systemctl stop teamspeak.service</code>

Change to your teamspeak user <code>cd /home/teamspeak/;su teamspeak</code>

Download Teamspeak, extract it, update and tidy up.
<pre>wget https://files.teamspeak-services.com/releases/server/3.9.1/teamspeak3-server_linux_amd64-3.9.1.tar.bz2
tar xvfj teamspeak3-server_linux_amd64-3.9.1.tar.bz2
cd teamspeak3-server_linux_amd64
cp * -R /home/teamspeak
cd ..
rm -r teamspeak3-server_linux_amd64
rm teamspeak3-server_linux_amd64-3.9.1.tar.bz2</pre>

Return to root and start the Teamspeak server
<pre>exit
systemctl start teamspeak.service
</pre>

Check to make you can connect to Teamspeak 3 server

== Factorio Headless Setup ==

[[My Factorio Info]]

== Hardware ==

Identify video card:
<pre>paul@congo:~$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2)</pre>

Verify interface speed

<code>cat /sys/class/net/<interface>/speed</code>

replace <interface> with name of your NIC (e.g. eth0)

[[Ubuntu video card]]

=== Resizing logical volume ===

Background

A 2 TB SSD was physically installed in the system ox and after installation, the LVM used 100 GB.

Reference [https://community.spiceworks.com/topic/2325763-how-can-i-make-ubuntu-vg-ubuntu-lv-consume-the-entire-disk-space-available How To Make ubuntu-vg-ubuntu-lv Use 100% Free Disc Space]

<pre>anon@ox:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p3 ubuntu-vg lvm2 a-- <1.82t <1.72t

anon@ox:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wz--n- <1.82t <1.72t

anon@ox:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- 100.00g # <----------- This shows 100 GB and I want 1.8T.

anon@ox:~$ sudo lvresize -l +100%FREE /dev/ubuntu-vg/ubuntu-lv

Size of logical volume ubuntu-vg/ubuntu-lv changed from 100.00 GiB (25600 extents) to <1.82 TiB (476150 extents).
Logical volume ubuntu-vg/ubuntu-lv successfully resized.

anon@ox:~$ sudo resize2fs /dev/ubuntu-vg/ubuntu-lv

resize2fs 1.46.5 (30-Dec-2021)
Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
old_desc_blocks = 13, new_desc_blocks = 233
The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 487577600 (4k) blocks long.

anon@ox:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p3 ubuntu-vg lvm2 a-- <1.82t 0

anon@ox:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wz--n- <1.82t 0

anon@ox:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- <1.82t # <----------- This was 100 GB Size, now it's 1.8T.

anon@ox:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 6.3G 1.9M 6.3G 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 1.8T 37G 1.7T 3% / # <----------- This was 100 GB Size, now it's 1.8T.
tmpfs 32G 200K 32G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/nvme0n1p2 2.0G 252M 1.6G 14% /boot
/dev/nvme0n1p1 1.1G 6.1M 1.1G 1% /boot/efi
tmpfs 6.3G 4.0K 6.3G 1% /run/user/1001
tmpfs 6.3G 4.0K 6.3G 1% /run/user/1000</pre>

<center>[[Linux|To Linux]]</center>

Ubuntu

2026-07-19T15:32:03Z

Paul: /* Check version of Ubuntu */

== Shell commands ==

Enable root account (not recommended):
<pre>$sudo passwd root</pre>

Disable root account you lock root account:
<pre>$sudo passwd -l root</pre>

Want to use root @ console:
<pre>$sudo -i</pre>

[https://help.ubuntu.com/community/WindowsDualBoot Windows Dual Boot] page

[https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows Recovering Ubuntu After Windows Install]

[https://wiki.ubuntu.com/Grub2 Grub2] on Ubuntu wiki

[http://www.howtogeek.com/howto/43471/how-to-configure-the-linux-grub2-boot-menu-the-easy-way/ Grub2 GUI] Customizer

For support-related question you can use [https://answers.launchpad.net/ Launchpad]. You can also search the complete history of questions and answers.

[http://ubuntuforums.org/ Ubuntu web forums]

[http://ubuntuforums.org/showthread.php?t=1195275 Grub 2] basics

=== Enable SSH server ===

<code>apt-get install openssh-server</code>

[https://coderwall.com/p/yz-2_a/limit-ssh-access-by-ip-address Secure SSH server using /etc/hosts.allow]

=== Add a User ===

Example adding a user with username johndoe. Follow the instructions provided by the command.

<code>sudo adduser johndoe</code>

==== sudo group stuff ====

Add user to sudo group

<code>sudo usermod -aG sudo <USER_NAME></code>

Verify user belongs to sudo group

<code>groups <USER_NAME></code>

Verify sudo access

<code>su - <USER_NAME></code>

Remove user from sudo group

<code>sudo deluser <USER_NAME> sudo</code>

=== Networking utilities ===

See IP address information

<code>ip a</code>

==== Configure hostname ====

[https://linuxize.com/post/how-to-change-hostname-on-ubuntu-18-04/ How to change hostname on Ubuntu 18 04]

==== systemctl ====

Verify which processes run on Ubuntu 18.04 start up use <code>$ sudo systemctl list-unit-files</code>.

=== Check version of Ubuntu ===

One way:
<code>$ cat /etc/os-release</code>

Another way, ran this on 2026-07 before upgrading release:
<pre>$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy</pre)

== CLI Software Management ==

Synchronize package index from Internet. Location of repositories <code>/etc/apt/sources.list</code>
<pre>sudo apt update</pre>
Install newest versions of all software packages
<pre>sudo apt upgrade</pre>
Update distribution
<pre>sudo apt-get dist-upgrade</pre>
Install package (if already installed, will attempt to update package)
<pre>apt-get install package-name</pre>
List installed packages
<pre>apt list --installed</pre>

List installed packages that start with 'python'
<pre>$ apt list -a --installed python*</pre>

To upgrade Ubuntu release, see [https://ubuntu.com/server/docs/how-to-upgrade-your-release How To Upgrade Your Release]

== Python on Ubuntu Notes ==

See [[ Python | My Python Notes]] for information not specific to Ubuntu and Python.

Verify Python 3 is installed
<pre>anon@hammerhead:~$ python --version

Command 'python' not found, but can be installed with:

sudo apt install python3
sudo apt install python
sudo apt install python-minimal

You also have python3 installed, you can run 'python3' instead.

anon@hammerhead:~$ python3 --version <----- Python 3 installed.
Python 3.6.7 <----- Version 3.6.7</pre>

Verify Python 3 PIP installed
<pre>$ pip3 --version
pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6)</pre>

To install Python 3 PIP
<pre>$ sudo apt-get install -y python3-pip</pre>

I use Python virtual environments. Verify Python venv module is installed
<pre>$ apt list -a --installed *venv* <----- If nothing with Python 3 venv comes back then you most install venv module</pre>

To install Python 3 venv module
<pre>$ sudo apt-get install -y python3-venv</pre>

Create virtual environment. I keep my Python virtual environments in a single directory. To create directory <code>$ mkdir python-venv</code>

Switch do directory <code>$ cd python-venv/</code>

Create virtual environment
<pre>$ python3 -m venv udmey-django</pre>

Activate virtual environment
<pre>$ source udmey-django/bin/activate</pre>

Prompt changes to reflect virtual environment
<pre>(udmey-django) anon@hammerhead:~/python-venv$</pre>

Note: Within virtual environment, you can use the command python instead of python3, and pip instead of pip3.

Deactivate virtual environment and prompt returns to normal
<pre>$ deactivate</pre>

== mongoDB ==

[[My MongoDB notes]]

== PostgreSQL ==

=== Install PostgreSQL ===

<pre>$ sudo apt install postgresql postgresql-contrib
...
Success. You can now start the database server using:

/usr/lib/postgresql/10/bin/pg_ctl -D /var/lib/postgresql/10/main -l logfile start

Ver Cluster Port Status Owner Data directory Log file
10 main 5432 down postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
update-alternatives: using /usr/share/postgresql/10/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
Setting up postgresql (10+190) ...
Setting up postgresql-contrib (10+190) ...
Processing triggers for systemd (237-3ubuntu10.11) ...
Processing triggers for ureadahead (0.100.0-20) ...</pre>

=== Use PostgreSQL ===

Switch to postgres account
<pre>sudo -i postgres</pre>
Access PostgreSQL prompt
<pre>psql</pre>
Exit PostgreSQL prompt
<pre>\q</pre>
Log directly into PostgreSQL prompt with postgres user
<pre>sudo -u postgres psql</pre>
Add user (username must be same as PostgreSQL role and database)
<pre>sudo adduser user_name</pre>
Check current connection information
<pre>\conninfo</pre>

While logged in as postgres user...

Create a new role. Use <code>man createuser</code> for more information.
<pre>createuser --interactive</pre>
Create new database
<pre>createdb db_name</pre>
Same user connect to different database
<pre>psql -d postgres</pre>

== Nginx ==

[[My Nginx notes]]

[https://www.tecmint.com/install-nginx-with-virtual-hosts-and-ssl-certificate/ Install Nginx with virtual hosts and SSL certificates]

== Apache 2 ==

=== Resources ===

[https://help.ubuntu.com/lts/serverguide/httpd.html Ubuntu server guide to HTTPD]

[https://help.ubuntu.com/community/OpenSSL#SSL_Certificates Ubuntu Open SSL guide]

[https://help.ubuntu.com/lts/serverguide/certificates-and-security.html.en Ubuntu Certificates and Security]

[http://tldp.org/HOWTO/SSL-Certificates-HOWTO/index.html SSL Certificate HOWTO] not Ubuntu specific

[https://stuff-things.net/2015/09/28/configuring-apache-for-ssl-client-certificate-authentication/ Configure Apache for SSL client certificate authentication]

=== Installation ===

Update all your software and install Apache 2

<pre># apt-get update
# apt-get upgrade
# apt install apache2</pre>

Verify Apache is running
<pre># systemctl status apache2
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: active (running) since Sun 2018-10-21 14:44:30 CDT; 11min ago
Main PID: 17131 (apache2)
Tasks: 55 (limit: 4181)
CGroup: /system.slice/apache2.service
├─17131 /usr/sbin/apache2 -k start
├─17132 /usr/sbin/apache2 -k start
└─17134 /usr/sbin/apache2 -k start

Oct 21 14:44:30 apu02 systemd[1]: Starting The Apache HTTP Server...
Oct 21 14:44:30 apu02 apachectl[17120]: AH00558: apache2: Could not reliably determine the server's
Oct 21 14:44:30 apu02 systemd[1]: Started The Apache HTTP Server.</pre>

=== Firewall ===

Update firewall to allow only port 443 (default HTTPS TCP port)

<pre># ufw app list
Available applications:
Apache
Apache Full
Apache Secure
OpenSSH

# ufw allow 'Apache Secure'

# ufw status verbose | grep 443
443/tcp (Apache Secure) ALLOW IN Anywhere
443/tcp (Apache Secure (v6)) ALLOW IN Anywhere (v6)</pre>

== Teamspeak 3 setup on Ubuntu 16.04 and 18.x via command line ==
Followed steps at [https://www.vultr.com/docs/how-to-install-teamspeak-3-server-on-ubuntu-16-04-64-bit How to install Teamspeak 3 server on Ubuntu 16.04 64-bit] to install Teamspeak 3 and get basic server running.

If you want to customize the server port follow next steps.

Install simple command-line program named [https://www.sqlite.org/cli.html sqlite3]. [https://www.sitepoint.com/getting-started-sqlite3-basic-commands/ How to use sqlite]

<pre>robot00@apu00:~$ sudo apt install sqlite3</pre>

Launch sqlite3 using Teamspeak 3 sqlite database file:

<pre>robot00@apu00:~$ sudo sqlite3 /home/teamspeak/ts3server.sqlitedb
SQLite version 3.11.0 2016-02-15 17:29:24
Enter ".help" for usage hints.</pre>

Update port command:

<pre>sqlite> update servers set server_port=<CUSTOM UDP Port>;</pre>

Restart Teamspeak 3 server

<pre>robot00@apu00:~$ systemctl restart teamspeak.service</pre>

Test your connection using the <CUSTOM UDP Port>

=== Upgrade Teamspeak3 server ===

[https://www.gazblog.com/2019/01/update-teamspeak-3-server-on-ubuntu-18-04/ original steps]

Login to SSH as root

Stop your current Teamspeak 3 Server <code>systemctl stop teamspeak.service</code>

Change to your teamspeak user <code>cd /home/teamspeak/;su teamspeak</code>

Download Teamspeak, extract it, update and tidy up.
<pre>wget https://files.teamspeak-services.com/releases/server/3.9.1/teamspeak3-server_linux_amd64-3.9.1.tar.bz2
tar xvfj teamspeak3-server_linux_amd64-3.9.1.tar.bz2
cd teamspeak3-server_linux_amd64
cp * -R /home/teamspeak
cd ..
rm -r teamspeak3-server_linux_amd64
rm teamspeak3-server_linux_amd64-3.9.1.tar.bz2</pre>

Return to root and start the Teamspeak server
<pre>exit
systemctl start teamspeak.service
</pre>

Check to make you can connect to Teamspeak 3 server

== Factorio Headless Setup ==

[[My Factorio Info]]

== Hardware ==

Identify video card:
<pre>paul@congo:~$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2)</pre>

Verify interface speed

<code>cat /sys/class/net/<interface>/speed</code>

replace <interface> with name of your NIC (e.g. eth0)

[[Ubuntu video card]]

=== Resizing logical volume ===

Background

A 2 TB SSD was physically installed in the system ox and after installation, the LVM used 100 GB.

Reference [https://community.spiceworks.com/topic/2325763-how-can-i-make-ubuntu-vg-ubuntu-lv-consume-the-entire-disk-space-available How To Make ubuntu-vg-ubuntu-lv Use 100% Free Disc Space]

<pre>anon@ox:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p3 ubuntu-vg lvm2 a-- <1.82t <1.72t

anon@ox:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wz--n- <1.82t <1.72t

anon@ox:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- 100.00g # <----------- This shows 100 GB and I want 1.8T.

anon@ox:~$ sudo lvresize -l +100%FREE /dev/ubuntu-vg/ubuntu-lv

Size of logical volume ubuntu-vg/ubuntu-lv changed from 100.00 GiB (25600 extents) to <1.82 TiB (476150 extents).
Logical volume ubuntu-vg/ubuntu-lv successfully resized.

anon@ox:~$ sudo resize2fs /dev/ubuntu-vg/ubuntu-lv

resize2fs 1.46.5 (30-Dec-2021)
Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
old_desc_blocks = 13, new_desc_blocks = 233
The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 487577600 (4k) blocks long.

anon@ox:~$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1p3 ubuntu-vg lvm2 a-- <1.82t 0

anon@ox:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wz--n- <1.82t 0

anon@ox:~$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- <1.82t # <----------- This was 100 GB Size, now it's 1.8T.

anon@ox:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 6.3G 1.9M 6.3G 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 1.8T 37G 1.7T 3% / # <----------- This was 100 GB Size, now it's 1.8T.
tmpfs 32G 200K 32G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/nvme0n1p2 2.0G 252M 1.6G 14% /boot
/dev/nvme0n1p1 1.1G 6.1M 1.1G 1% /boot/efi
tmpfs 6.3G 4.0K 6.3G 1% /run/user/1001
tmpfs 6.3G 4.0K 6.3G 1% /run/user/1000</pre>

<center>[[Linux|To Linux]]</center>

Minecraft

2026-06-20T14:08:11Z

Paul: remove old stuff

== Minecraft server view-distance and lag notes ==

If your processor, network connection, and RAM are sufficient then the bottle neck for performance is very likely server storage (hard drive or SSD) speed. You reduce server storage input/output (I/O) by reducing view-distance. View-distance determines how much of the Minecraft world a player sees (the fog in the distance is the cut off of view-distance). Raise view-distance and all players see farther (clients can reduce their view-distance in video options). Lower view-distange see closer. View-distance is used in the calculation of mob spawns, higher means increased mob numbers, lower produces less mob spawns. This section of information is about elimination of lag, skipping ticks, system time change, and server overload issues. Read on for more details.

Minecraft software: '''Minecraft server jar version 1.8.9 Vanilla (no mods)'''

Server operating system: Linux Fedora Core Release 23 64-bit

Server hardware specs:
* CPU: Intel Core i5-6600 6M Skylake Quad-Core 3.3 GHz
* Mobo: SABERTOOTH Z170 MARK 1
* RAM: 32GB (4x8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000)
* Video: Built-in Intel
* Drive: Samsung 950Pro SSD
* PSU: Coolmaster GX 750W

''The key to this setup is the very fast Samsung Pro 950 SSD (M.2 form factor using NVMe).''

I've been hosting a private friends / family vanilla Minecraft server since 2010. The server routinely supports 8 to 10 simultaneous connected users. Users are connected via Gigabit LAN and Gigabit WAN (Google Fiber 1Gbps synchronous).

The server jar file is launched with -Xmx1g -Xms1g arguments.

Operating system: Fedora Core Release 23 (use Linux based OS as server storage I/O is superior than Windows based OS).

After many hours of play testing / changing view-distance over the years with different server storage below are the settings that clients would experience zero lag.

* The server originally had a 7200 RPM hard disk drive. '''''view-distance set to 6 to avoid lag issues.'''''
* Switched to SATA connected SSD. '''''The view-distance set to 8 to avoid lag issues.'''''
* Switched to M.2 form NVMe SSD (Samsung Pro950). '''''The view-distance set to 16. No lag issues.'''''

Note that the above systems never had CPU or RAM issues.

To take advantage of OS having faster storage I/O and Minecraft server software I upgraded to Z170 chipset that supports booting to M.2 form factor SSD using NVMe (the Samsung Pro 950 256GB). The Minecraft directories and files are on the same partition as the OS (previous versions I used separate drives for OS and Minecraft).

I haven't tried a view-distance above 16 because everyone is really pleased with the results with one exception. The number of mob spawns is 2 to 3 times worse than before so nobody wants to have a higher view-distance for fear of even more mob spawning. Attacking pig man zombies with this hardware and software setup is very dangerous!

== Windows Operating System ==

My tips for running Minecraft on Windows machines.

* Update video driver
* Update Java software at [http://java.com Java] website
* Allocate more memory only if you get "out of memory errors"

=== Allocate More Memory to Minecraft ===

Thought I'd share my success at memory allocation changes with those who are interested.

'''Note:''' I only changed my memory allocations on my machine due to in-game memory crashes every 90 to 120 seconds when exploring outside. Once I allocated 768m I haven't had a memory crash. This memory allocation started happening to my machine since 1.7 beta.

I was trying various configurations to allocate memory but my command window would open up then immediately close or Java Virtual Machine (JVM) would not launch, etc.

I have Win7 Ultimate 64-bit, 12 GB RAM, with current version of Java installed.

I created a batch file & updated my PATH variable with directory of current Java version.

Batch file contains (use your own c:\path2minecraft.exe here):
<pre>javaw -Xms768m -jar "c:\minecraft\Minecraft.exe"</pre>

Added this to PATH (don't forget the semi-colon to separate this path from previous one):
<pre>;C:\Program Files (x86)\Java\jre7\bin</pre>

'''Add to PATH steps: For Win7 Ultimate I right click Computer > Properties > Advanced System Settings > Advanced Tab > Environmental Variables > System Variables > highlight PATH then click EDIT. Add semi-colon then PATH to current version of Java then press Okay.'''

''Side Note: The same machine runs minecraft flawless in Fedora Core 15 & 16 without memory modifications. Only the lack of Ventrilo support on Linux causes me to use Windows to run minecraft.''

I've read about other people starting minecraft.exe with -Xmx parameter but I could not get various options to work, even though I have 12 GB RAM.

== How-to Minecraft Guides ==

[[How To setup Minecraft server on Windows OS|How-to setup Minecraft server on Windows OS]]

[[How-to edit server.properties file on Linux]]

=== Backing up your Minecraft world ===

This guide is written for:
* Linux operating systems
* uses /minecraft for Minecraft's root directory
* starts and ends with Minecraft server running
* connected to Linux server via SSH
* connected to Minecraft server console
* using byobu open source text-based window manager and terminal multiplexer
* using Linux user anon with permissions on /minecraft and sub-directories and files
* backups are stored in /minecraft/backups
* removing old backups

Backup steps:
# Check no players are connected. Command: <code>/list</code>
# Save Minecraft world files. Command: <code>/save-all</code>
# Stop Minecraft server app. Command: <code>/stop</code>
# Switch to alternate terminal. Across the top of the SSH session, you will see <code>0:-*</code> for single terminal or <code>0:-* 1:--</code> for multiple terminals (the # represents each terminal, there can be many). The <code>*</code> indicates the terminal you are viewing. If single terminal, press F2 to create and switch to a new terminal. If multiple terminals, press F4 to move forward one terminal (F3 to move backward).
# Verify you are using anon user. Prompt should start with <code>anon@</code> on Ubuntu Linux. You can also type <code>whoami</code> and the return should be <code>anon</code>.
# Switch to Minecraft root directory. Command: <code>cd /minecraft</code>
# Show Minecraft worlds by listing directories and files in current directory. Command: <code>ls -l</code>
# Backup each world separately.
## We will backup a world called '''realms''' in this example. Note: You will use the world name that is applicable to your current backup, don't always use '''realms'''.
## You should see a '''realms''' directory from the previous command output.
## This command will archive (create single file) and compress simultaneously so each world backup will be of a single file.
## Use same command with different file names for each world backup.
## Command template: <code>tar -cvzf newFileNameYYYYMMDD.tar.gz fileOrDirectoryToArchiveAndCompress/</code> where newFileName=worldName, fileOrDirectoryToArchiveAndCompress=realms, YYYY=2022, MM=01, and DD=03 if current date is January 3, 2022.
## Command example: <code>tar -cvzf realms20220103.tar.gz realms/</code>
## The command should output the archival process and return to prompt when no errors are encountered.
# Validate new backup exists.
## Command: <code>ls -l</code>
## Verify a file exists matching your new file name, or <code>realms20220103.tar.gz</code> in our example.
# Do the archive and compress command for each Minecraft world you want to backup.
# Move backups to /minecraft/backups. Command: <code>mv ./*.tar.gz ./backups/</code>
# Validate backups are in /minecraft/backups. Command: <code>ls -l ./backups</code>
## You should see the backups you created in the output plus any pre-existing backups.
# Remove older backups when you have more than 3 of each world to save storage space.
## Only backup worlds that have been played on since last backup.
## Remove old backups. Command: <code>rm backups/water_world20220202.tar.gz</code> Copy and paste the file name after you type rm backups/ (highlight to copy and press middle mouse to paste should work) or use autocomplete (tab).
# Switch to Minecraft terminal. F3 to move backward or F4 to move forward.
# Start up Minecraft world like normal.

<center>[[Gaming|To Gaming]]</center>

Telecommunications info

2026-04-16T13:55:13Z

Paul: updated 103 120 scope

== NNI Task Force ==

[https://www.sipforum.org/activities/nni-task-force-introduction/ NNI Task Force Introduction]

== 3GPP SA3 Security ==

[https://www.3gpp.org/specifications-groups/sa-plenary/sa3-security SA3 - Security]

== [https://www.3gpp.org/specifications/79-specification-numbering 3GPP Standards] ==

[https://www.3gpp.org/specifications/79-specification-numbering 3GPP specification numbering]

[https://www.3gpp.org/DynaReport/status-report.htm 3GPP Specification Status Report]

=== Definition and abbreviations ===

See [[My 3GPP definition notes]] for definitions

See [[My 3GPP abbreviation notes]] for abbreviations

=== EPS and NR related standards with notes ===

[[My New Radio (NR) notes]]

{| class="wikitable sortable"
|-
! Standard # !! Title !! Notes
|-
| 22.011
| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service accessibility
| The purpose of 22.011 is to describe the service access procedures as presented to the user. Definitions and procedures are provided in 22.011 for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station, or User Equipment (UE).

[[My 3GPP TS 22.011 Notes]]
|-
| [https://www.3gpp.org/DynaReport/22261.htm 22.261] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service requirements for the 5G system;
Stage 1
|| Document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278.
|-
| 23.122 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|| Document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 and 3GPP TS 38.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 and 3GPP TS 38.331.
|-
| [https://www.3gpp.org/DynaReport/23271.htm 23.271] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Functional stage 2 description of Location Services (LCS)
(Release 16)
|| Document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers. Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 and TS 23.502 in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3577 23.273] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
5G System (5GS) Location Services (LCS);
Stage 2
|| V17.5.0 document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 and TS 22.071.
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access
(Release 17)
|| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.

[[My 3GPP 23.401 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
System architecture for the 5G System (5GS);
Stage 2
|| 5G core network

[[My 3GPP 23.501 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Procedures for the 5G System (5GS);
Stage 2
| V17.5.0 document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 and for the policy and charging control framework which is described in TS 23.503.

[[My 3GPP 23.502 Notes]]
|-
| 24.229 || Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 || P-Access-Network-Info values for "cgi-3gpp", "utran-cell-id-3gpp", "i-wlan-node-id", "dsl-location", "ci-3gpp2", "ci-3gpp2-femto" and "gstn-location" are defined in section 7.2A.4
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3370 24.501] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) protocol for 5G System (5GS);
Stage 3;
|| This present document specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for:
* mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and
* session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.
The 5GS mobility management (5GMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the NG radio access network (NG-RAN) and/or non-3GPP access network. The 5GMM protocol also provides control of security for the NAS protocols.

[[My 3GPP 24.501 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3371 24.502] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Access to the 3GPP 5G Core Network (5GCN)
via Non-3GPP Access Networks (N3AN);
Stage 3
|| This document specifies non-3GPP access network discovery and selection procedures, the access authorization procedure used for accessing non-3GPP access networks. These non-3GPP access networks can be trusted non-3GPP access networks, untrusted non-3GPP access networks or wireline access networks.
|-
| 29.503 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
5G System; Unified Data Management Services;
Stage 3
|| The document specifies the stage 3 protocol and data model for the Nudm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDM.

The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 and 3GPP TS 23.502.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 and 3GPP TS 29.501.
|-
| 29.279 || Universal Mobile Telecommunications System (UMTS); LTE; Mobile IPv4 (MIPv4) based mobility protocols; Stage 3 ||
|-
| [https://www.3gpp.org/DynaReport/29571.htm 29.571] || 5G System; Common Data Types for Service Based Interfaces; Stage 3 || The document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
|-
| [https://www.3gpp.org/DynaReport/33501.htm 33.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security architecture and procedures for 5G system
|| Document specifies the security architecture, i.e., the security features and the security mechanisms for the 5G System and the 5G Core, and the security procedures performed within the 5G System including the 5G Core and the 5G New Radio.

[[My 3GPP 33.501 notes]]
|-
| [https://www.3gpp.org/DynaReport/37340.htm 37.340] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA) and NR;
Multi-connectivity;
Stage 2
|| Document provides an overview of the multi-connectivity operation using E-UTRA and NR radio access technologies.
|-
| 38.300 || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2
|| This document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

[[My 3GPP 38.300 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38304.htm 38.304] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
User Equipment (UE) procedures in Idle mode and RRC Inactive state
|| Document specifies the Access Stratum (AS) part of the UE procedures in RRC_IDLE state (also called Idle mode) and RRC_INACTIVE state. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in TS 23.122.

[[My 3GPP TS 38.304 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3197 38.331] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
Radio Resource Control (RRC) protocol specification
(Release 17)
|| This document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN.
|-
| [https://www.3gpp.org/DynaReport/38401.htm 38.401] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description || Document describes the overall architecture of the NG-RAN, including interfaces NG, Xn and F1 interfaces and their interaction with the radio interface.

[[My 3GPP TS 38.401 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38413.htm 38.413] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP)(Release 16) || This document specifies the radio network layer signalling protocol for the NG interface. The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document. NGAP is developed in accordance to the general principles stated in TS 38.401 and TS 38.410.
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

== 3GPP/ETSI info ==

[https://www.etsi.org/technologies/5g ETSI 5G information page]

[https://www.etsi.org/technologies/lawful-interception ETSI Lawful Interception (LI) information page]

[https://www.etsi.org/committee/1403-li ETSI Technical Committee (TC) Lawful Interception information page] and contains list of latest publications

=== [https://www.etsi.org/standards ETSI Standards] ===

==== Lawful Interception or Related Standards ====

{| class="wikitable sortable"
|-
! ETSI Standard
! Title
! Notes
|-
| ETSI TS 102 232-1 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery || This document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. This document:
* specifies the modular approach used for specifying IP based handover interfaces;
* specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
* specifies protocols for the transfer of IRI and CC across the handover interfaces;
* specifies protocol profiles for the handover interface.

[[My 102 232-1 notes]]
|-
| ETSI TS 102 232-2 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services || This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.
|-
| ETSI TS 102 232-3 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services || This document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The study includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets.

The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1.

[[My 102 232-3 notes]]
|-
| ETSI TS 102 232-4 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services ||
|-
| ETSI TS 102 232-5 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services || Document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Real Time Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IPMM services as described by the Recommendations ITU-T H.323 and H.248-1.

The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1.

The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 and ETSI TS 101 671.
|-
| ETSI TS 102 232-6 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services ||
|-
| ETSI TS 102 232-7 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services ||
|-
| ETSI TR 102 528 || Lawful Interception (LI); Interception domain Architecture for IP networks || Document describes a high level reference architecture for supporting lawful interception in network operator (NWO) and communication service providers (SvP) domain for IP networks.

The document contains:
* A reference model in the network operator (NWO) and communication service provider (SvP) domain.
* A High level description of Internal Network Functions and Interfaces.
* Application of the reference model to voice and multimedia over IP services, data layer 3 and layer 2 services.
|-
| ETSI TS 103 221 || Lawful Interception (LI); Internal Network Interfaces || Part I (X1) and Part II (X2/X3) [[My TS 103 221-2 notes]]
|-
| ETSI TS 103 643 || Techniques for assurance of digital material used in legal proceedings ||
|-
| ETSI TS 101 671 & ETSI ES 201 671 || Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic || Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service.
* Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331.
* Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
|-
| ETSI TS 103 462 || Lawful Interception (LI); Inter LEMF Handover Interface ||
|-
| style="white-space: nowrap;" | ETSI TR 102 503 || Lawful Interception (LI); ASN.1 Object Identifiers in Lawful Interception and Retained data handling Specifications ||
|-
| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data || Document gives guidance for the delivery and associated issues of retained data of telecommunications and subscribers. It provides a set of requirements relating to handover interfaces for the retained traffic data and subscriber data by law enforcement and other authorized requesting authorities.

The present document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
Not all requirements necessarily apply in one individual nation.

These requirements may be used to derive specific network requirements and furthermore to standardize handover
interfaces.

The present document gives the requirements for the delivery of Retained Data (in line with ETSI TS 101 331 [1] for
LI).
|-
| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data || Document is based on requirements from ETSI TS 102 656.

The present document contains handover requirements and a handover specification for the data that is identified in
national legislations on Retained Data.

The present document considers both the requesting of retained data and the delivery of the results.

The present document defines an electronic interface. An informative annex describes how this interface may be adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.
|-
| ETSI TS 101 331 || Lawful Interception (LI); Requirements of Law Enforcement Agencies || Document gives guidance for lawful interception of telecommunications in the area of co-operation by network operators, access providers, and service providers. Document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
|-
| ETSI TS 103 707 || Lawful Interception (LI); Handover for messaging services over HTTP/XML || Document specifies the handover details to deliver messaging services for LI over HTTP/XML
|-
| ETSI TS 103 120 || Lawful Interception (LI); Interface for warrant information || Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception. Typically this interface would be used between on one side, a Communications Service Provider and on the other side, a Government or Law Enforcement Agency who is entitled to request a lawful action.

The present document is a specific and detailed example of one particular Warrantry interface for eWarrants.

The ETSI reference model for LI (ETSI TS 102 232-1) defines three interfaces between law enforcement and
CSPs, called HI-1, HI-2 and HI-3. The protocol defined in the present document is designed to provide a large part of
the functionality for HI-1. It is not designed to be used for HI-2 (delivery of intercept related information) or HI-3
(delivery of communications content). The protocol designed in the present document may also be used for interfaces
which require structured exchange of information relating to the establishment and management of Lawful Interception.
The general view is that the HI-1 concept can also be used for other legal actions than LI. For that reason, the present document could, besides LI, also be applied for retained data requests, seized data requests, data preservation orders and other similar legal requests.
|-
| ETSI TS 104 144 || Interface definition for the e-Evidence Regulation (EU) 2023/1543 for National Authorities and Service Providers || Document provides an interface definition for the e-Evidence Regulation (EU) 2023/1543, supporting National Authorities and Service Providers in understanding and complying with its requirements.
|-
| ETSI TS 103 280 || Lawful Interception (LI); Dictionary for common parameters || Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]
|-
| ETSI TS 103 690 || Lawful Interception (LI); eWarrant Interface || Document presents a high-level description of an interface mechanism - the eWarrant Interface - for receipt of requests for measures producing real-time or stored information by an issuing authority possessing lawful authorization to initiate such a request
|-
| || ||
|-
| || ||
|-
| || ||
|}

==== Other Standards ====

{| class="wikitable sortable"
|-
! 3GPP
! Title
! Notes
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729 23.003]
|| 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)
|| This document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system. IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator.

[[My 3GPP TS 23.003 notes]]
|-
| [https://www.3gpp.org/DynaReport/23228.htm 23.228]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 16)
|| This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. [[My 3GPP TS 23.228 Notes]]
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 16)
|| The document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1014 24.007]
| 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface signalling layer 3;
General aspects
(Release 17)
| 24.007 document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
This document also defines the principal architecture of the EPS NAS and 5GS NAS layer 3 protocol and their sublayers, including the message format applied by layer 3.

[[My 3GPP TS 24.007 Notes]]
|-
| 33.108 || UMTS; LTE; GSM; 3G Security; Handover interface for lawful interception (LI) || [[My TS 133 108 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3182 33.127] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Lawful Interception (LI) architecture and functions
|| This document specifies both the architectural and functional system requirements for Lawful Interception (LI) in 3GPP networks. The present document provides an LI architecture supporting both network layer based and service layer based Interception. National regulations determine the specific set of LI functional capabilities that are applicable to a specific 3GPP operator deployment.

[[My 33.127 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3183 33.128] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Protocol and procedures for Lawful Interception (LI);
Stage 3
|| This document specifies the protocols and procedures required to perform Lawful Interception within a 3GPP network. The present document addresses both internal interfaces used internally with a 3GPP network and external handover interfaces used to handover intercepted communications to law enforcement.

[[My 33.128 Notes]]
|}

== Standards related info ==

MCPTT ID parameter is defined in TS 23.280

[[My ATIS lawful interception standard notes]]

[[My lawful interception notes]]

== RFCs of interest ==

[https://tools.ietf.org/html/rfc3261 RFC 3261 SIP: Session Initiation Protocol]

[https://tools.ietf.org/html/rfc3455 RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)]

[https://tools.ietf.org/html/rfc7913 RFC 7913 P-Access-Network-Info ABNF Update]

[https://tools.ietf.org/html/rfc4984 RFC 4984 Report from the IAB Workshop on Routing and Addressing]

[https://tools.ietf.org/html/rfc6830 RFC 6830 The Locator/ID Separation Protocol (LISP)]

== National Requirements Resources ==

[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

== Case Examples ==

[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later.

Telecommunications info

2026-04-16T13:51:16Z

Paul: updated 102 656 and 102 657 scopes

== NNI Task Force ==

[https://www.sipforum.org/activities/nni-task-force-introduction/ NNI Task Force Introduction]

== 3GPP SA3 Security ==

[https://www.3gpp.org/specifications-groups/sa-plenary/sa3-security SA3 - Security]

== [https://www.3gpp.org/specifications/79-specification-numbering 3GPP Standards] ==

[https://www.3gpp.org/specifications/79-specification-numbering 3GPP specification numbering]

[https://www.3gpp.org/DynaReport/status-report.htm 3GPP Specification Status Report]

=== Definition and abbreviations ===

See [[My 3GPP definition notes]] for definitions

See [[My 3GPP abbreviation notes]] for abbreviations

=== EPS and NR related standards with notes ===

[[My New Radio (NR) notes]]

{| class="wikitable sortable"
|-
! Standard # !! Title !! Notes
|-
| 22.011
| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service accessibility
| The purpose of 22.011 is to describe the service access procedures as presented to the user. Definitions and procedures are provided in 22.011 for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station, or User Equipment (UE).

[[My 3GPP TS 22.011 Notes]]
|-
| [https://www.3gpp.org/DynaReport/22261.htm 22.261] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service requirements for the 5G system;
Stage 1
|| Document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278.
|-
| 23.122 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|| Document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 and 3GPP TS 38.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 and 3GPP TS 38.331.
|-
| [https://www.3gpp.org/DynaReport/23271.htm 23.271] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Functional stage 2 description of Location Services (LCS)
(Release 16)
|| Document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers. Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 and TS 23.502 in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3577 23.273] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
5G System (5GS) Location Services (LCS);
Stage 2
|| V17.5.0 document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 and TS 22.071.
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access
(Release 17)
|| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.

[[My 3GPP 23.401 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
System architecture for the 5G System (5GS);
Stage 2
|| 5G core network

[[My 3GPP 23.501 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Procedures for the 5G System (5GS);
Stage 2
| V17.5.0 document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 and for the policy and charging control framework which is described in TS 23.503.

[[My 3GPP 23.502 Notes]]
|-
| 24.229 || Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 || P-Access-Network-Info values for "cgi-3gpp", "utran-cell-id-3gpp", "i-wlan-node-id", "dsl-location", "ci-3gpp2", "ci-3gpp2-femto" and "gstn-location" are defined in section 7.2A.4
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3370 24.501] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) protocol for 5G System (5GS);
Stage 3;
|| This present document specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for:
* mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and
* session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.
The 5GS mobility management (5GMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the NG radio access network (NG-RAN) and/or non-3GPP access network. The 5GMM protocol also provides control of security for the NAS protocols.

[[My 3GPP 24.501 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3371 24.502] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Access to the 3GPP 5G Core Network (5GCN)
via Non-3GPP Access Networks (N3AN);
Stage 3
|| This document specifies non-3GPP access network discovery and selection procedures, the access authorization procedure used for accessing non-3GPP access networks. These non-3GPP access networks can be trusted non-3GPP access networks, untrusted non-3GPP access networks or wireline access networks.
|-
| 29.503 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
5G System; Unified Data Management Services;
Stage 3
|| The document specifies the stage 3 protocol and data model for the Nudm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDM.

The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 and 3GPP TS 23.502.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 and 3GPP TS 29.501.
|-
| 29.279 || Universal Mobile Telecommunications System (UMTS); LTE; Mobile IPv4 (MIPv4) based mobility protocols; Stage 3 ||
|-
| [https://www.3gpp.org/DynaReport/29571.htm 29.571] || 5G System; Common Data Types for Service Based Interfaces; Stage 3 || The document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
|-
| [https://www.3gpp.org/DynaReport/33501.htm 33.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security architecture and procedures for 5G system
|| Document specifies the security architecture, i.e., the security features and the security mechanisms for the 5G System and the 5G Core, and the security procedures performed within the 5G System including the 5G Core and the 5G New Radio.

[[My 3GPP 33.501 notes]]
|-
| [https://www.3gpp.org/DynaReport/37340.htm 37.340] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA) and NR;
Multi-connectivity;
Stage 2
|| Document provides an overview of the multi-connectivity operation using E-UTRA and NR radio access technologies.
|-
| 38.300 || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2
|| This document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

[[My 3GPP 38.300 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38304.htm 38.304] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
User Equipment (UE) procedures in Idle mode and RRC Inactive state
|| Document specifies the Access Stratum (AS) part of the UE procedures in RRC_IDLE state (also called Idle mode) and RRC_INACTIVE state. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in TS 23.122.

[[My 3GPP TS 38.304 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3197 38.331] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
Radio Resource Control (RRC) protocol specification
(Release 17)
|| This document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN.
|-
| [https://www.3gpp.org/DynaReport/38401.htm 38.401] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description || Document describes the overall architecture of the NG-RAN, including interfaces NG, Xn and F1 interfaces and their interaction with the radio interface.

[[My 3GPP TS 38.401 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38413.htm 38.413] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP)(Release 16) || This document specifies the radio network layer signalling protocol for the NG interface. The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document. NGAP is developed in accordance to the general principles stated in TS 38.401 and TS 38.410.
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

== 3GPP/ETSI info ==

[https://www.etsi.org/technologies/5g ETSI 5G information page]

[https://www.etsi.org/technologies/lawful-interception ETSI Lawful Interception (LI) information page]

[https://www.etsi.org/committee/1403-li ETSI Technical Committee (TC) Lawful Interception information page] and contains list of latest publications

=== [https://www.etsi.org/standards ETSI Standards] ===

==== Lawful Interception or Related Standards ====

{| class="wikitable sortable"
|-
! ETSI Standard
! Title
! Notes
|-
| ETSI TS 102 232-1 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery || This document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. This document:
* specifies the modular approach used for specifying IP based handover interfaces;
* specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
* specifies protocols for the transfer of IRI and CC across the handover interfaces;
* specifies protocol profiles for the handover interface.

[[My 102 232-1 notes]]
|-
| ETSI TS 102 232-2 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services || This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.
|-
| ETSI TS 102 232-3 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services || This document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The study includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets.

The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1.

[[My 102 232-3 notes]]
|-
| ETSI TS 102 232-4 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services ||
|-
| ETSI TS 102 232-5 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services || Document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Real Time Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IPMM services as described by the Recommendations ITU-T H.323 and H.248-1.

The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1.

The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 and ETSI TS 101 671.
|-
| ETSI TS 102 232-6 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services ||
|-
| ETSI TS 102 232-7 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services ||
|-
| ETSI TR 102 528 || Lawful Interception (LI); Interception domain Architecture for IP networks || Document describes a high level reference architecture for supporting lawful interception in network operator (NWO) and communication service providers (SvP) domain for IP networks.

The document contains:
* A reference model in the network operator (NWO) and communication service provider (SvP) domain.
* A High level description of Internal Network Functions and Interfaces.
* Application of the reference model to voice and multimedia over IP services, data layer 3 and layer 2 services.
|-
| ETSI TS 103 221 || Lawful Interception (LI); Internal Network Interfaces || Part I (X1) and Part II (X2/X3) [[My TS 103 221-2 notes]]
|-
| ETSI TS 103 643 || Techniques for assurance of digital material used in legal proceedings ||
|-
| ETSI TS 101 671 & ETSI ES 201 671 || Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic || Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service.
* Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331.
* Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
|-
| ETSI TS 103 462 || Lawful Interception (LI); Inter LEMF Handover Interface ||
|-
| style="white-space: nowrap;" | ETSI TR 102 503 || Lawful Interception (LI); ASN.1 Object Identifiers in Lawful Interception and Retained data handling Specifications ||
|-
| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data || Document gives guidance for the delivery and associated issues of retained data of telecommunications and subscribers. It provides a set of requirements relating to handover interfaces for the retained traffic data and subscriber data by law enforcement and other authorized requesting authorities.

The present document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
Not all requirements necessarily apply in one individual nation.

These requirements may be used to derive specific network requirements and furthermore to standardize handover
interfaces.

The present document gives the requirements for the delivery of Retained Data (in line with ETSI TS 101 331 [1] for
LI).
|-
| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data || Document is based on requirements from ETSI TS 102 656.

The present document contains handover requirements and a handover specification for the data that is identified in
national legislations on Retained Data.

The present document considers both the requesting of retained data and the delivery of the results.

The present document defines an electronic interface. An informative annex describes how this interface may be adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.
|-
| ETSI TS 101 331 || Lawful Interception (LI); Requirements of Law Enforcement Agencies || Document gives guidance for lawful interception of telecommunications in the area of co-operation by network operators, access providers, and service providers. Document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
|-
| ETSI TS 103 707 || Lawful Interception (LI); Handover for messaging services over HTTP/XML || Document specifies the handover details to deliver messaging services for LI over HTTP/XML
|-
| ETSI TS 103 120 || Lawful Interception (LI); Interface for warrant information || Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.
|-
| ETSI TS 104 144 || Interface definition for the e-Evidence Regulation (EU) 2023/1543 for National Authorities and Service Providers || Document provides an interface definition for the e-Evidence Regulation (EU) 2023/1543, supporting National Authorities and Service Providers in understanding and complying with its requirements.
|-
| ETSI TS 103 280 || Lawful Interception (LI); Dictionary for common parameters || Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]
|-
| ETSI TS 103 690 || Lawful Interception (LI); eWarrant Interface || Document presents a high-level description of an interface mechanism - the eWarrant Interface - for receipt of requests for measures producing real-time or stored information by an issuing authority possessing lawful authorization to initiate such a request
|-
| || ||
|-
| || ||
|-
| || ||
|}

==== Other Standards ====

{| class="wikitable sortable"
|-
! 3GPP
! Title
! Notes
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729 23.003]
|| 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)
|| This document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system. IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator.

[[My 3GPP TS 23.003 notes]]
|-
| [https://www.3gpp.org/DynaReport/23228.htm 23.228]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 16)
|| This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. [[My 3GPP TS 23.228 Notes]]
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 16)
|| The document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1014 24.007]
| 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface signalling layer 3;
General aspects
(Release 17)
| 24.007 document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
This document also defines the principal architecture of the EPS NAS and 5GS NAS layer 3 protocol and their sublayers, including the message format applied by layer 3.

[[My 3GPP TS 24.007 Notes]]
|-
| 33.108 || UMTS; LTE; GSM; 3G Security; Handover interface for lawful interception (LI) || [[My TS 133 108 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3182 33.127] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Lawful Interception (LI) architecture and functions
|| This document specifies both the architectural and functional system requirements for Lawful Interception (LI) in 3GPP networks. The present document provides an LI architecture supporting both network layer based and service layer based Interception. National regulations determine the specific set of LI functional capabilities that are applicable to a specific 3GPP operator deployment.

[[My 33.127 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3183 33.128] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Protocol and procedures for Lawful Interception (LI);
Stage 3
|| This document specifies the protocols and procedures required to perform Lawful Interception within a 3GPP network. The present document addresses both internal interfaces used internally with a 3GPP network and external handover interfaces used to handover intercepted communications to law enforcement.

[[My 33.128 Notes]]
|}

== Standards related info ==

MCPTT ID parameter is defined in TS 23.280

[[My ATIS lawful interception standard notes]]

[[My lawful interception notes]]

== RFCs of interest ==

[https://tools.ietf.org/html/rfc3261 RFC 3261 SIP: Session Initiation Protocol]

[https://tools.ietf.org/html/rfc3455 RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)]

[https://tools.ietf.org/html/rfc7913 RFC 7913 P-Access-Network-Info ABNF Update]

[https://tools.ietf.org/html/rfc4984 RFC 4984 Report from the IAB Workshop on Routing and Addressing]

[https://tools.ietf.org/html/rfc6830 RFC 6830 The Locator/ID Separation Protocol (LISP)]

== National Requirements Resources ==

[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

== Case Examples ==

[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later.

Personal Computer

2026-02-22T18:25:51Z

Paul: added printer section

Hardware, software and accessories that are used on personal computers.

I use [http://www.newegg.com/ NewEgg] for about 95% of my computer related purchases and [http://www.microcenter.com MicroCenter] and [http://www.amazon.com/ Amazon] for the remaining 5%. NewEgg service, price, and website interface leave the others in the dust.

== Household Personal Computers ==

When I remember I keep this up-to-date.

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Nickname
! Primary User
! CPU
! Memory
! Video Adapters
! Storage Devices
! Monitors
! Power Supply
! Motherboard
! Case
! Operating System
|-
| sourdough
| daddy
| i7-7700K Kaby Lake @ 4.2 GHz
| 32GB(2x16)
| Two EVGA GeForce GTX 1070 SC GAMING ACX 3.0 8GB (SLI)
| Intel SSD 600p + 1 TB HDD
| Three 23" Dell LCD + 1 Acer 23" accessory
| CORSAIR RM750X 750W 80 PLUS GOLD
| ASUS ROG STRIX Z270H
| Cooler Master HAF 912
| Win 10 64-bit
|-
| frog
| mommy
| AMD FX-6350 Six-Core @ 3.9GHz
| 16GB(4x4)
| One XFX R9-270X-CDFC Radeon R9 270X
| One Seagate 7200RPM 1TB HDD 64MB cache
| Acer G6 G246HLAbd 24" LED
| Corsair HX 850
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 912
| Win 10 64-bit
|-
| irish
| 13-year old daughter
| AMD FX-8350 Black Edition Vishera 8-Core @ 4.0GHz
| 32GB (4 x 8GB) DDR3 1866
| EVGA NVidia GTX 560Ti
| One Seagate 1TB 7200 RPM
| One 23" Dell LCD
| Corsair HX 750
| ASUS SABERTOOTH 990FX R2.0 AM3+ AMD 990FX
| Cooler Master HAF 922
| Win 10 64-bit
|-
| elephant
| 11-year old daughter
| i5-4690 @ 3.5 GHz
| 32GB(4x8)
| EVGA GeForce GTX 770 4GB
| One 2TB HDD
| Three 23" Dell LCD + 1 HP 23" accessory
| Corsair HX 1050
| ASUS Sabertooth Z97 Mark1
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit
|-
| spiderman
| 8-year old son
| AMD FX-8150 Quad-core @ 3.6GHz
| 16GB(4x4)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| Western Digital 1TB HDD
| One 23" Dell LCD
| Corsair HX 850
| MSI 990FXA-GD80 V2
| generic
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| koala
| 6-year old son
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB (4x8)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| One 1TB HDD
| One 23" Dell LCD
| XFX PRO850W XXX Edition Semi-Modular
| ASUS SABERTOOTH 990FX R2.0
| Silverstone
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| shark
| daddy
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB(4x8)
| Two XFX FX-785A-CDFC Radeon HD 7850 2GB (Eyefinity @ 5760 x 1080)
| Samsung 256GB SDD
| Three 23" Dell LCD (Eyefinity)
| Corsair HX 1050
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit & Linux Mint w/MATE
|-
| hammerhead
| daddy
| Intel Core i5-6600 6M Skylake Quad-Core 3.3 GHz
| 32GB (4x8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000)
| Built-In Intel
| Samsung 950Pro SSD
| Acer H6 H236HL 23"
| Coolmaster GX 750W
| SABERTOOTH Z170 MARK 1
| Antec full tower
| Linux Fedora Core Release 23 64-bit
|-
| steamnuc
| daddy
| Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
| 16GB (2 x 8GB 260Pin SO-DIMM DDR4 2133)
| Intel Iris Plus Graphics 650
| Samsung 950Pro SSD
| Headless
| Built-in
| Built-in
| NUC7I7BNH
| Linux Ubuntu 20.04.6 LTS
|}

== Home Network ==

=== WAN connectivity ===

Our house uses both Verizon Fios at 2 Gbps synchronous Internet.

=== LAN connectivity ===

Our house has a 1 Gbps wired network over Unshielded Twisted Pair (UTP) CAT5E and CAT6E cabling.

=== Printer ===

Canon Color imageCLASS MF665Cdw

== Software ==

=== Office Suite ===

[http://www.libreoffice.org/ Libre Office]

=== Image or graphic tools ===

Use [https://imagemagick.org/ ImageMagick®] to create, edit, compose, or convert bitmap images. It can read and write images in a variety of formats (over 200) including PNG, JPEG, GIF, HEIC, TIFF, DPX, EXR, WebP, Postscript, PDF, and SVG. Use ImageMagick to resize, flip, mirror, rotate, distort, shear and transform images, adjust image colors, apply various special effects, or draw text, lines, polygons, ellipses and Bézier curves.

ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under a derived Apache 2.0 license.

ImageMagick utilizes multiple computational threads to increase performance and can read, process, or write mega-, giga-, or tera-pixel image sizes.

==== Vector graphics ====

[https://inkscape.org/en/about/ Inkscape] is professional quality vector graphics software that runs on Windows, Mac OS X and GNU/Linux. It is used by design professionals and hobbyists worldwide, for creating a wide variety of graphics such as illustrations, icons, logos, diagrams, maps and web graphics. Inkscape uses the W3C open standard SVG (Scalable Vector Graphics) as its native format, and is free and open-source software.

=== CD / DVD Burning software ===

To burn data and audio CD / DVDs I use [http://cdburnerxp.se/ CD BurnerXP].

To create personal copies of protected DVDs that I have purchased I use [http://www.1clickdvdcopy.com/1clickdvdcopypro.asp 1ClickDVDCopy Pro] ($79 fee) and [http://www.dvd43.com/ DVD43], a free decrypter.

=== Multimedia software ===

[http://www.videolan.org/vlc/ VLC] - the cross-platform media player and streaming server.

VLC media player is a highly portable multimedia player for various audio and video formats (MPEG-1, MPEG-2, MPEG-4, DivX, mp3, ogg, ...) as well as DVDs, VCDs, and various streaming protocols. It can also be used as a server to stream in unicast or multicast in IPv4 or IPv6 on a high-bandwidth network.

==== Video Capture ====

[http://www.fraps.com/ Fraps] is a universal Windows application that can be used with games using DirectX or OpenGL graphic technology. In its current form Fraps performs many tasks and can best be described as:
* Benchmarking Software
* Screen Capture Software
* Realtime Video Capture Software

==== Video Editing ====

[https://www.mp4joiner.org/en/ MP4Tools] is a collection of cross-platform free tools to manipulate MP4 files. It contains following applications:

*MP4Joiner is a free application that allows join multiple MP4 files into one without reencoding and without quality loss.
*MP4Splitter is a free application that allows split a MP4 file in multiple files without reencoding and without quality loss

MP4Tools is Open Source Software and is completely free.

[http://www.freemake.com/ Freemake] offers freeware in the truest sense of the word: no feature or time limitations, no hidden costs. Download and use our free Video Converter, Video Downloader, Audio Converter and Free Music Box! Convert video free to AVI, MP4, WMV, MKV, FLV, 3GP, MPEG, DVD, Blu-ray, MP3, iPod, iPhone, iPad, PSP, Android, Nokia, Samsung, BlackBerry with [http://www.freemake.com/free_video_converter/ Free Video Converter]. Convert audio free to MP3, WMA, WAV, FLAC, AAC, M4A, OGG, convert audio to MP3 player, iPod, iPhone, iPad, PSP, and more with our [http://www.freemake.com/free_audio_converter/ Free Audio Converter].

<pre>I like FreeMake products as the software is simple to use & their site provides video tutorials.
Their products work, have lots of features, & no hidden spyware or adware.</pre>

[http://www.tmpgenc.net/en/index.html TMPGEnc] converts *.AVI files to MPEG1, the format which is used in VideoCDs. Using a variety of options in TMPGEnc, you can compress your video file in high quality.

TMPGEnc enables you to adjust bitrate, quantize matrix, GOP structure, interlacing and many other parameters so that you can create the most appropriate movie file depending on your needs.

[http://www.virtualdub.org/ Virtualdub]is a video capture/processing utility for 32-bit and 64-bit Windows platforms (98/ME/NT4/2000/XP/Vista/7), licensed under the GNU General Public License (GPL). It lacks the editing power of a general-purpose editor such as Adobe Premiere, but is streamlined for fast linear operations over video. It has batch-processing capabilities for processing large numbers of files and can be extended with third-party video filters.

=== Communications Software ===

==== Browser and E-mail ====

[http://www.mozilla.com/en-US/ Firefox and Thunderbird]

[[My Thunderbird Notes]]

===== Firefox add-ons =====

FireFTP

Download Status Bar

[http://www.zotero.org/ Zotero] is a free, easy-to-use Firefox extension to help you collect, manage, cite, and share your research sources. It lives right where you do your work—in the web browser itself.

==== Torrent ====

[http://www.qbittorrent.org/ qBittorrent] project aims to provide a '''free software''' alternative to µtorrent. Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).

==== Java ====

[http://www.java.com/en/download/manual.jsp Java]

==== FTP clients ====

[http://filezilla-project.org/ Filezilla]

==== VoIP clients ====

[http://www.ventrilo.com/ Ventrillo]

[http://www.goteamspeak.com/ TeamSpeak]

==== IRC client ====

[http://hexchat.github.io/index.html HexChat]

==== SSHv2 & SFTP ====

I switched to [https://www.bitvise.com/ssh-client Bitvise SSH client] for SSH client. I like some of the features Bitvise offers. [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty] is a free SSHv2 program. You can also get SecureFTP program from same site.

[http://www.mremoteng.org/ mRemoteNG] is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager. mRemoteNG adds bug fixes and new features to mRemote.

eRemoteNG allows you to view all of your remote connections in a simple yet powerful tabbed interface.

mRemoteNG supports the following protocols:
* RDP (Remote Desktop/Terminal Server)
* VNC (Virtual Network Computing)
* ICA (Citrix Independent Computing Architecture)
* SSH (Secure Shell version 1 & 2)
* Telnet (TELecommunication NETwork)
* HTTP/HTTPS (Hypertext Transfer Protocol)
* rlogin
* Raw Socket Connections

==== Tunnelier ====

[http://www.bitvise.com/tunnelier Bitvise Tunnelier]

=== Utilities ===

==== Console utilities ====

[https://cmder.net/ Cmder] is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.

[https://conemu.github.io/ ConEmu-Maximus5] aims to be handy, comprehensive, fast and reliable terminal window where you may host any console application developed either for WinAPI (cmd, powershell, far) or Unix PTY (cygwin, msys, wsl bash).

[https://github.com/cmderdev/cmder/wiki/How-to-start-Cmder-from-anywhere Steps to put Cmder in your environment variable]

==== eBook ====

[http://calibre-ebook.com/about calibre] is a free and open source e-book library management application developed by users of e-books for users of e-books. It has a cornucopia of features divided into the following main categories:

* Library Management
* E-book conversion
* Syncing to e-book reader devices
* Downloading news from the web and converting it into e-book form
* Comprehensive e-book viewer
* Content server for online access to your book collection

==== Screen Capture ====

In December of 2017 I switched my entire family over to [http://getgreenshot.org/ Greenshot] for screen capture software. With each new version of SnagIt the user interface kept getting worse. Not only is Greenshot free I actually like using it more than SnagIt. I have been using TechSmith's SnagIt for many years and with each newer version of SnagIt I had to buy another copy and the program got worse due to added complexity and bloat.

[https://www.techsmith.com/snagit.html Snagit] by TechSmith

'''Note on Snagit version 12.4.1''' I noticed a TechSmith Uploader Service taking up 1.7 MB of RAM. I contacted TechSmith support and explained what the service did and how to remove it.

'''Purpose:''' The TechSmith Uploader Service is used when Snagit is integrated with TechSmith Relay, which is an Enterprise service that we offer. The service is designed to run in the background and not be visible to the user.

'''Removal:''' Remove TechSmith Uploader Service by browsing to C:\Program Files (x86)\Common Files\TechSmith Shared\Uploader on your computer. Right click on the "UninstallAndRemoveUploader.cmd" file and choose Run as administrator. Once that is done reboot your machine.

==== Password manager ====

[http://keepass.info/ Keepass] is a free open source password manager, which helps you to manage your passwords in a secure way. You can put all your passwords in one database, which is locked with one master key or a key file. So you only have to remember one single master password or select the key file to unlock the whole database. The databases are encrypted using the best and most secure encryption algorithms currently known (AES and Twofish). For more information, see the [http://keepass.info/features.html features page].

==== PDF Viewer & Printer ====

[http://www.foxitsoftware.com/pdf/rd_intro.php Foxit Reader] Foxit Reader is a free PDF document viewer and printer, with incredible small size (only 2.55 M download size), breezing-fast launch speed and rich feature set. Foxit Reader supports Windows Me/2000/XP/2003/Vista. Its core function is compatible with PDF Standard 1.7.

==== Compression ====

===== Open Source =====

[http://peazip.sourceforge.net/ Peazip] Note: Ensure you read install directions carefully to avoid extra software (crapware?)

===== Closed source =====
[http://www.rarlab.com/ WinRAR]

==== Backup ====

MozBackup is a simple utility for creating backups of Mozilla Firefox, Mozilla Thunderbird, Mozilla Sunbird, Flock, SeaMonkey, Mozilla Suite, Spicebird and Netscape profiles.

[http://mozbackup.jasnapaka.com/ MozBackup]

==== Hardware Monitor ====

[http://www.almico.com/speedfan.php SpeedFan] is a program that monitors voltages, fan speeds and temperatures in computers with hardware monitor chips. SpeedFan can even access S.M.A.R.T. info for those hard disks that support this feature and show hard disk temperatures too, if supported.

==== GPU Utilities ====

[http://www.radeonpro.info/en-US/ RadeonPro]

==== HASH utilities ====

Use [https://wiki.gotopinion.info/wiki/index.php?title=Windows_Operating_System#HASH_in_PowerShell PowerShell built-in command]

Command line [https://kanguru.zendesk.com/entries/21747773-SHA256-Checksum-Utility SHA256 Checksum Utility] for Windows

=== Voxel utilities ===

[https://ephtracy.github.io/index.html MagicaVoxel] is a free lightweight 8-bit voxel art editor and GPU based interactive path tracing render-er.

[https://ephtracy.github.io/index.html?page=mv_controls MagicaVoxel] keyboard shortcuts.

===== Tutorials =====

[https://www.megavoxels.com/2019/08/magicavoxel-3d-art-tutorial-for.html MagicaVoxel 3D Art Tutorial for Beginners]

== Accessories ==

=== Mouse pads ===

[http://www.xtracpads.com/ XTracPads]
<pre>Prefer Xtracpads</pre>

[http://www.ratpadz.com/ RatPadz]
<pre>Second choice is RatPadz. Over the years my Ratpadz start to fail
as the surface becomes worn & smooth in areas which impacts laser mouse
movement</pre>

=== To Go ===

[http://www.geargrip.com/index.php Gear Grip]

Personal Computer

2026-02-22T18:25:18Z

Paul: /* LAN connectivity */

Hardware, software and accessories that are used on personal computers.

I use [http://www.newegg.com/ NewEgg] for about 95% of my computer related purchases and [http://www.microcenter.com MicroCenter] and [http://www.amazon.com/ Amazon] for the remaining 5%. NewEgg service, price, and website interface leave the others in the dust.

== Household Personal Computers ==

When I remember I keep this up-to-date.

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Nickname
! Primary User
! CPU
! Memory
! Video Adapters
! Storage Devices
! Monitors
! Power Supply
! Motherboard
! Case
! Operating System
|-
| sourdough
| daddy
| i7-7700K Kaby Lake @ 4.2 GHz
| 32GB(2x16)
| Two EVGA GeForce GTX 1070 SC GAMING ACX 3.0 8GB (SLI)
| Intel SSD 600p + 1 TB HDD
| Three 23" Dell LCD + 1 Acer 23" accessory
| CORSAIR RM750X 750W 80 PLUS GOLD
| ASUS ROG STRIX Z270H
| Cooler Master HAF 912
| Win 10 64-bit
|-
| frog
| mommy
| AMD FX-6350 Six-Core @ 3.9GHz
| 16GB(4x4)
| One XFX R9-270X-CDFC Radeon R9 270X
| One Seagate 7200RPM 1TB HDD 64MB cache
| Acer G6 G246HLAbd 24" LED
| Corsair HX 850
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 912
| Win 10 64-bit
|-
| irish
| 13-year old daughter
| AMD FX-8350 Black Edition Vishera 8-Core @ 4.0GHz
| 32GB (4 x 8GB) DDR3 1866
| EVGA NVidia GTX 560Ti
| One Seagate 1TB 7200 RPM
| One 23" Dell LCD
| Corsair HX 750
| ASUS SABERTOOTH 990FX R2.0 AM3+ AMD 990FX
| Cooler Master HAF 922
| Win 10 64-bit
|-
| elephant
| 11-year old daughter
| i5-4690 @ 3.5 GHz
| 32GB(4x8)
| EVGA GeForce GTX 770 4GB
| One 2TB HDD
| Three 23" Dell LCD + 1 HP 23" accessory
| Corsair HX 1050
| ASUS Sabertooth Z97 Mark1
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit
|-
| spiderman
| 8-year old son
| AMD FX-8150 Quad-core @ 3.6GHz
| 16GB(4x4)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| Western Digital 1TB HDD
| One 23" Dell LCD
| Corsair HX 850
| MSI 990FXA-GD80 V2
| generic
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| koala
| 6-year old son
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB (4x8)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| One 1TB HDD
| One 23" Dell LCD
| XFX PRO850W XXX Edition Semi-Modular
| ASUS SABERTOOTH 990FX R2.0
| Silverstone
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| shark
| daddy
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB(4x8)
| Two XFX FX-785A-CDFC Radeon HD 7850 2GB (Eyefinity @ 5760 x 1080)
| Samsung 256GB SDD
| Three 23" Dell LCD (Eyefinity)
| Corsair HX 1050
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit & Linux Mint w/MATE
|-
| hammerhead
| daddy
| Intel Core i5-6600 6M Skylake Quad-Core 3.3 GHz
| 32GB (4x8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000)
| Built-In Intel
| Samsung 950Pro SSD
| Acer H6 H236HL 23"
| Coolmaster GX 750W
| SABERTOOTH Z170 MARK 1
| Antec full tower
| Linux Fedora Core Release 23 64-bit
|-
| steamnuc
| daddy
| Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
| 16GB (2 x 8GB 260Pin SO-DIMM DDR4 2133)
| Intel Iris Plus Graphics 650
| Samsung 950Pro SSD
| Headless
| Built-in
| Built-in
| NUC7I7BNH
| Linux Ubuntu 20.04.6 LTS
|}

== Home Network ==

=== WAN connectivity ===

Our house uses both Verizon Fios at 2 Gbps synchronous Internet.

=== LAN connectivity ===

Our house has a 1 Gbps wired network over Unshielded Twisted Pair (UTP) CAT5E and CAT6E cabling.

== Software ==

=== Office Suite ===

[http://www.libreoffice.org/ Libre Office]

=== Image or graphic tools ===

Use [https://imagemagick.org/ ImageMagick®] to create, edit, compose, or convert bitmap images. It can read and write images in a variety of formats (over 200) including PNG, JPEG, GIF, HEIC, TIFF, DPX, EXR, WebP, Postscript, PDF, and SVG. Use ImageMagick to resize, flip, mirror, rotate, distort, shear and transform images, adjust image colors, apply various special effects, or draw text, lines, polygons, ellipses and Bézier curves.

ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under a derived Apache 2.0 license.

ImageMagick utilizes multiple computational threads to increase performance and can read, process, or write mega-, giga-, or tera-pixel image sizes.

==== Vector graphics ====

[https://inkscape.org/en/about/ Inkscape] is professional quality vector graphics software that runs on Windows, Mac OS X and GNU/Linux. It is used by design professionals and hobbyists worldwide, for creating a wide variety of graphics such as illustrations, icons, logos, diagrams, maps and web graphics. Inkscape uses the W3C open standard SVG (Scalable Vector Graphics) as its native format, and is free and open-source software.

=== CD / DVD Burning software ===

To burn data and audio CD / DVDs I use [http://cdburnerxp.se/ CD BurnerXP].

To create personal copies of protected DVDs that I have purchased I use [http://www.1clickdvdcopy.com/1clickdvdcopypro.asp 1ClickDVDCopy Pro] ($79 fee) and [http://www.dvd43.com/ DVD43], a free decrypter.

=== Multimedia software ===

[http://www.videolan.org/vlc/ VLC] - the cross-platform media player and streaming server.

VLC media player is a highly portable multimedia player for various audio and video formats (MPEG-1, MPEG-2, MPEG-4, DivX, mp3, ogg, ...) as well as DVDs, VCDs, and various streaming protocols. It can also be used as a server to stream in unicast or multicast in IPv4 or IPv6 on a high-bandwidth network.

==== Video Capture ====

[http://www.fraps.com/ Fraps] is a universal Windows application that can be used with games using DirectX or OpenGL graphic technology. In its current form Fraps performs many tasks and can best be described as:
* Benchmarking Software
* Screen Capture Software
* Realtime Video Capture Software

==== Video Editing ====

[https://www.mp4joiner.org/en/ MP4Tools] is a collection of cross-platform free tools to manipulate MP4 files. It contains following applications:

*MP4Joiner is a free application that allows join multiple MP4 files into one without reencoding and without quality loss.
*MP4Splitter is a free application that allows split a MP4 file in multiple files without reencoding and without quality loss

MP4Tools is Open Source Software and is completely free.

[http://www.freemake.com/ Freemake] offers freeware in the truest sense of the word: no feature or time limitations, no hidden costs. Download and use our free Video Converter, Video Downloader, Audio Converter and Free Music Box! Convert video free to AVI, MP4, WMV, MKV, FLV, 3GP, MPEG, DVD, Blu-ray, MP3, iPod, iPhone, iPad, PSP, Android, Nokia, Samsung, BlackBerry with [http://www.freemake.com/free_video_converter/ Free Video Converter]. Convert audio free to MP3, WMA, WAV, FLAC, AAC, M4A, OGG, convert audio to MP3 player, iPod, iPhone, iPad, PSP, and more with our [http://www.freemake.com/free_audio_converter/ Free Audio Converter].

<pre>I like FreeMake products as the software is simple to use & their site provides video tutorials.
Their products work, have lots of features, & no hidden spyware or adware.</pre>

[http://www.tmpgenc.net/en/index.html TMPGEnc] converts *.AVI files to MPEG1, the format which is used in VideoCDs. Using a variety of options in TMPGEnc, you can compress your video file in high quality.

TMPGEnc enables you to adjust bitrate, quantize matrix, GOP structure, interlacing and many other parameters so that you can create the most appropriate movie file depending on your needs.

[http://www.virtualdub.org/ Virtualdub]is a video capture/processing utility for 32-bit and 64-bit Windows platforms (98/ME/NT4/2000/XP/Vista/7), licensed under the GNU General Public License (GPL). It lacks the editing power of a general-purpose editor such as Adobe Premiere, but is streamlined for fast linear operations over video. It has batch-processing capabilities for processing large numbers of files and can be extended with third-party video filters.

=== Communications Software ===

==== Browser and E-mail ====

[http://www.mozilla.com/en-US/ Firefox and Thunderbird]

[[My Thunderbird Notes]]

===== Firefox add-ons =====

FireFTP

Download Status Bar

[http://www.zotero.org/ Zotero] is a free, easy-to-use Firefox extension to help you collect, manage, cite, and share your research sources. It lives right where you do your work—in the web browser itself.

==== Torrent ====

[http://www.qbittorrent.org/ qBittorrent] project aims to provide a '''free software''' alternative to µtorrent. Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).

==== Java ====

[http://www.java.com/en/download/manual.jsp Java]

==== FTP clients ====

[http://filezilla-project.org/ Filezilla]

==== VoIP clients ====

[http://www.ventrilo.com/ Ventrillo]

[http://www.goteamspeak.com/ TeamSpeak]

==== IRC client ====

[http://hexchat.github.io/index.html HexChat]

==== SSHv2 & SFTP ====

I switched to [https://www.bitvise.com/ssh-client Bitvise SSH client] for SSH client. I like some of the features Bitvise offers. [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty] is a free SSHv2 program. You can also get SecureFTP program from same site.

[http://www.mremoteng.org/ mRemoteNG] is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager. mRemoteNG adds bug fixes and new features to mRemote.

eRemoteNG allows you to view all of your remote connections in a simple yet powerful tabbed interface.

mRemoteNG supports the following protocols:
* RDP (Remote Desktop/Terminal Server)
* VNC (Virtual Network Computing)
* ICA (Citrix Independent Computing Architecture)
* SSH (Secure Shell version 1 & 2)
* Telnet (TELecommunication NETwork)
* HTTP/HTTPS (Hypertext Transfer Protocol)
* rlogin
* Raw Socket Connections

==== Tunnelier ====

[http://www.bitvise.com/tunnelier Bitvise Tunnelier]

=== Utilities ===

==== Console utilities ====

[https://cmder.net/ Cmder] is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.

[https://conemu.github.io/ ConEmu-Maximus5] aims to be handy, comprehensive, fast and reliable terminal window where you may host any console application developed either for WinAPI (cmd, powershell, far) or Unix PTY (cygwin, msys, wsl bash).

[https://github.com/cmderdev/cmder/wiki/How-to-start-Cmder-from-anywhere Steps to put Cmder in your environment variable]

==== eBook ====

[http://calibre-ebook.com/about calibre] is a free and open source e-book library management application developed by users of e-books for users of e-books. It has a cornucopia of features divided into the following main categories:

* Library Management
* E-book conversion
* Syncing to e-book reader devices
* Downloading news from the web and converting it into e-book form
* Comprehensive e-book viewer
* Content server for online access to your book collection

==== Screen Capture ====

In December of 2017 I switched my entire family over to [http://getgreenshot.org/ Greenshot] for screen capture software. With each new version of SnagIt the user interface kept getting worse. Not only is Greenshot free I actually like using it more than SnagIt. I have been using TechSmith's SnagIt for many years and with each newer version of SnagIt I had to buy another copy and the program got worse due to added complexity and bloat.

[https://www.techsmith.com/snagit.html Snagit] by TechSmith

'''Note on Snagit version 12.4.1''' I noticed a TechSmith Uploader Service taking up 1.7 MB of RAM. I contacted TechSmith support and explained what the service did and how to remove it.

'''Purpose:''' The TechSmith Uploader Service is used when Snagit is integrated with TechSmith Relay, which is an Enterprise service that we offer. The service is designed to run in the background and not be visible to the user.

'''Removal:''' Remove TechSmith Uploader Service by browsing to C:\Program Files (x86)\Common Files\TechSmith Shared\Uploader on your computer. Right click on the "UninstallAndRemoveUploader.cmd" file and choose Run as administrator. Once that is done reboot your machine.

==== Password manager ====

[http://keepass.info/ Keepass] is a free open source password manager, which helps you to manage your passwords in a secure way. You can put all your passwords in one database, which is locked with one master key or a key file. So you only have to remember one single master password or select the key file to unlock the whole database. The databases are encrypted using the best and most secure encryption algorithms currently known (AES and Twofish). For more information, see the [http://keepass.info/features.html features page].

==== PDF Viewer & Printer ====

[http://www.foxitsoftware.com/pdf/rd_intro.php Foxit Reader] Foxit Reader is a free PDF document viewer and printer, with incredible small size (only 2.55 M download size), breezing-fast launch speed and rich feature set. Foxit Reader supports Windows Me/2000/XP/2003/Vista. Its core function is compatible with PDF Standard 1.7.

==== Compression ====

===== Open Source =====

[http://peazip.sourceforge.net/ Peazip] Note: Ensure you read install directions carefully to avoid extra software (crapware?)

===== Closed source =====
[http://www.rarlab.com/ WinRAR]

==== Backup ====

MozBackup is a simple utility for creating backups of Mozilla Firefox, Mozilla Thunderbird, Mozilla Sunbird, Flock, SeaMonkey, Mozilla Suite, Spicebird and Netscape profiles.

[http://mozbackup.jasnapaka.com/ MozBackup]

==== Hardware Monitor ====

[http://www.almico.com/speedfan.php SpeedFan] is a program that monitors voltages, fan speeds and temperatures in computers with hardware monitor chips. SpeedFan can even access S.M.A.R.T. info for those hard disks that support this feature and show hard disk temperatures too, if supported.

==== GPU Utilities ====

[http://www.radeonpro.info/en-US/ RadeonPro]

==== HASH utilities ====

Use [https://wiki.gotopinion.info/wiki/index.php?title=Windows_Operating_System#HASH_in_PowerShell PowerShell built-in command]

Command line [https://kanguru.zendesk.com/entries/21747773-SHA256-Checksum-Utility SHA256 Checksum Utility] for Windows

=== Voxel utilities ===

[https://ephtracy.github.io/index.html MagicaVoxel] is a free lightweight 8-bit voxel art editor and GPU based interactive path tracing render-er.

[https://ephtracy.github.io/index.html?page=mv_controls MagicaVoxel] keyboard shortcuts.

===== Tutorials =====

[https://www.megavoxels.com/2019/08/magicavoxel-3d-art-tutorial-for.html MagicaVoxel 3D Art Tutorial for Beginners]

== Accessories ==

=== Mouse pads ===

[http://www.xtracpads.com/ XTracPads]
<pre>Prefer Xtracpads</pre>

[http://www.ratpadz.com/ RatPadz]
<pre>Second choice is RatPadz. Over the years my Ratpadz start to fail
as the surface becomes worn & smooth in areas which impacts laser mouse
movement</pre>

=== To Go ===

[http://www.geargrip.com/index.php Gear Grip]

Personal Computer

2026-02-22T18:24:39Z

Paul: removed Old notes regarding some computer issues clause

Hardware, software and accessories that are used on personal computers.

I use [http://www.newegg.com/ NewEgg] for about 95% of my computer related purchases and [http://www.microcenter.com MicroCenter] and [http://www.amazon.com/ Amazon] for the remaining 5%. NewEgg service, price, and website interface leave the others in the dust.

== Household Personal Computers ==

When I remember I keep this up-to-date.

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Nickname
! Primary User
! CPU
! Memory
! Video Adapters
! Storage Devices
! Monitors
! Power Supply
! Motherboard
! Case
! Operating System
|-
| sourdough
| daddy
| i7-7700K Kaby Lake @ 4.2 GHz
| 32GB(2x16)
| Two EVGA GeForce GTX 1070 SC GAMING ACX 3.0 8GB (SLI)
| Intel SSD 600p + 1 TB HDD
| Three 23" Dell LCD + 1 Acer 23" accessory
| CORSAIR RM750X 750W 80 PLUS GOLD
| ASUS ROG STRIX Z270H
| Cooler Master HAF 912
| Win 10 64-bit
|-
| frog
| mommy
| AMD FX-6350 Six-Core @ 3.9GHz
| 16GB(4x4)
| One XFX R9-270X-CDFC Radeon R9 270X
| One Seagate 7200RPM 1TB HDD 64MB cache
| Acer G6 G246HLAbd 24" LED
| Corsair HX 850
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 912
| Win 10 64-bit
|-
| irish
| 13-year old daughter
| AMD FX-8350 Black Edition Vishera 8-Core @ 4.0GHz
| 32GB (4 x 8GB) DDR3 1866
| EVGA NVidia GTX 560Ti
| One Seagate 1TB 7200 RPM
| One 23" Dell LCD
| Corsair HX 750
| ASUS SABERTOOTH 990FX R2.0 AM3+ AMD 990FX
| Cooler Master HAF 922
| Win 10 64-bit
|-
| elephant
| 11-year old daughter
| i5-4690 @ 3.5 GHz
| 32GB(4x8)
| EVGA GeForce GTX 770 4GB
| One 2TB HDD
| Three 23" Dell LCD + 1 HP 23" accessory
| Corsair HX 1050
| ASUS Sabertooth Z97 Mark1
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit
|-
| spiderman
| 8-year old son
| AMD FX-8150 Quad-core @ 3.6GHz
| 16GB(4x4)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| Western Digital 1TB HDD
| One 23" Dell LCD
| Corsair HX 850
| MSI 990FXA-GD80 V2
| generic
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| koala
| 6-year old son
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB (4x8)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| One 1TB HDD
| One 23" Dell LCD
| XFX PRO850W XXX Edition Semi-Modular
| ASUS SABERTOOTH 990FX R2.0
| Silverstone
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| shark
| daddy
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB(4x8)
| Two XFX FX-785A-CDFC Radeon HD 7850 2GB (Eyefinity @ 5760 x 1080)
| Samsung 256GB SDD
| Three 23" Dell LCD (Eyefinity)
| Corsair HX 1050
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit & Linux Mint w/MATE
|-
| hammerhead
| daddy
| Intel Core i5-6600 6M Skylake Quad-Core 3.3 GHz
| 32GB (4x8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000)
| Built-In Intel
| Samsung 950Pro SSD
| Acer H6 H236HL 23"
| Coolmaster GX 750W
| SABERTOOTH Z170 MARK 1
| Antec full tower
| Linux Fedora Core Release 23 64-bit
|-
| steamnuc
| daddy
| Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
| 16GB (2 x 8GB 260Pin SO-DIMM DDR4 2133)
| Intel Iris Plus Graphics 650
| Samsung 950Pro SSD
| Headless
| Built-in
| Built-in
| NUC7I7BNH
| Linux Ubuntu 20.04.6 LTS
|}

== Home Network ==

=== WAN connectivity ===

Our house uses both Verizon Fios at 2 Gbps synchronous Internet.

=== LAN connectivity ===

Our house has a 1 Gbps wired network over Unshielded Twisted Pair (UTP) CAT5E with face plates installed in various rooms. The wires connect to a 24-port patch panel. The 24-port patch panel connects to a 24-port non-managed Gigabit switch.

== Software ==

=== Office Suite ===

[http://www.libreoffice.org/ Libre Office]

=== Image or graphic tools ===

Use [https://imagemagick.org/ ImageMagick®] to create, edit, compose, or convert bitmap images. It can read and write images in a variety of formats (over 200) including PNG, JPEG, GIF, HEIC, TIFF, DPX, EXR, WebP, Postscript, PDF, and SVG. Use ImageMagick to resize, flip, mirror, rotate, distort, shear and transform images, adjust image colors, apply various special effects, or draw text, lines, polygons, ellipses and Bézier curves.

ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under a derived Apache 2.0 license.

ImageMagick utilizes multiple computational threads to increase performance and can read, process, or write mega-, giga-, or tera-pixel image sizes.

==== Vector graphics ====

[https://inkscape.org/en/about/ Inkscape] is professional quality vector graphics software that runs on Windows, Mac OS X and GNU/Linux. It is used by design professionals and hobbyists worldwide, for creating a wide variety of graphics such as illustrations, icons, logos, diagrams, maps and web graphics. Inkscape uses the W3C open standard SVG (Scalable Vector Graphics) as its native format, and is free and open-source software.

=== CD / DVD Burning software ===

To burn data and audio CD / DVDs I use [http://cdburnerxp.se/ CD BurnerXP].

To create personal copies of protected DVDs that I have purchased I use [http://www.1clickdvdcopy.com/1clickdvdcopypro.asp 1ClickDVDCopy Pro] ($79 fee) and [http://www.dvd43.com/ DVD43], a free decrypter.

=== Multimedia software ===

[http://www.videolan.org/vlc/ VLC] - the cross-platform media player and streaming server.

VLC media player is a highly portable multimedia player for various audio and video formats (MPEG-1, MPEG-2, MPEG-4, DivX, mp3, ogg, ...) as well as DVDs, VCDs, and various streaming protocols. It can also be used as a server to stream in unicast or multicast in IPv4 or IPv6 on a high-bandwidth network.

==== Video Capture ====

[http://www.fraps.com/ Fraps] is a universal Windows application that can be used with games using DirectX or OpenGL graphic technology. In its current form Fraps performs many tasks and can best be described as:
* Benchmarking Software
* Screen Capture Software
* Realtime Video Capture Software

==== Video Editing ====

[https://www.mp4joiner.org/en/ MP4Tools] is a collection of cross-platform free tools to manipulate MP4 files. It contains following applications:

*MP4Joiner is a free application that allows join multiple MP4 files into one without reencoding and without quality loss.
*MP4Splitter is a free application that allows split a MP4 file in multiple files without reencoding and without quality loss

MP4Tools is Open Source Software and is completely free.

[http://www.freemake.com/ Freemake] offers freeware in the truest sense of the word: no feature or time limitations, no hidden costs. Download and use our free Video Converter, Video Downloader, Audio Converter and Free Music Box! Convert video free to AVI, MP4, WMV, MKV, FLV, 3GP, MPEG, DVD, Blu-ray, MP3, iPod, iPhone, iPad, PSP, Android, Nokia, Samsung, BlackBerry with [http://www.freemake.com/free_video_converter/ Free Video Converter]. Convert audio free to MP3, WMA, WAV, FLAC, AAC, M4A, OGG, convert audio to MP3 player, iPod, iPhone, iPad, PSP, and more with our [http://www.freemake.com/free_audio_converter/ Free Audio Converter].

<pre>I like FreeMake products as the software is simple to use & their site provides video tutorials.
Their products work, have lots of features, & no hidden spyware or adware.</pre>

[http://www.tmpgenc.net/en/index.html TMPGEnc] converts *.AVI files to MPEG1, the format which is used in VideoCDs. Using a variety of options in TMPGEnc, you can compress your video file in high quality.

TMPGEnc enables you to adjust bitrate, quantize matrix, GOP structure, interlacing and many other parameters so that you can create the most appropriate movie file depending on your needs.

[http://www.virtualdub.org/ Virtualdub]is a video capture/processing utility for 32-bit and 64-bit Windows platforms (98/ME/NT4/2000/XP/Vista/7), licensed under the GNU General Public License (GPL). It lacks the editing power of a general-purpose editor such as Adobe Premiere, but is streamlined for fast linear operations over video. It has batch-processing capabilities for processing large numbers of files and can be extended with third-party video filters.

=== Communications Software ===

==== Browser and E-mail ====

[http://www.mozilla.com/en-US/ Firefox and Thunderbird]

[[My Thunderbird Notes]]

===== Firefox add-ons =====

FireFTP

Download Status Bar

[http://www.zotero.org/ Zotero] is a free, easy-to-use Firefox extension to help you collect, manage, cite, and share your research sources. It lives right where you do your work—in the web browser itself.

==== Torrent ====

[http://www.qbittorrent.org/ qBittorrent] project aims to provide a '''free software''' alternative to µtorrent. Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).

==== Java ====

[http://www.java.com/en/download/manual.jsp Java]

==== FTP clients ====

[http://filezilla-project.org/ Filezilla]

==== VoIP clients ====

[http://www.ventrilo.com/ Ventrillo]

[http://www.goteamspeak.com/ TeamSpeak]

==== IRC client ====

[http://hexchat.github.io/index.html HexChat]

==== SSHv2 & SFTP ====

I switched to [https://www.bitvise.com/ssh-client Bitvise SSH client] for SSH client. I like some of the features Bitvise offers. [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty] is a free SSHv2 program. You can also get SecureFTP program from same site.

[http://www.mremoteng.org/ mRemoteNG] is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager. mRemoteNG adds bug fixes and new features to mRemote.

eRemoteNG allows you to view all of your remote connections in a simple yet powerful tabbed interface.

mRemoteNG supports the following protocols:
* RDP (Remote Desktop/Terminal Server)
* VNC (Virtual Network Computing)
* ICA (Citrix Independent Computing Architecture)
* SSH (Secure Shell version 1 & 2)
* Telnet (TELecommunication NETwork)
* HTTP/HTTPS (Hypertext Transfer Protocol)
* rlogin
* Raw Socket Connections

==== Tunnelier ====

[http://www.bitvise.com/tunnelier Bitvise Tunnelier]

=== Utilities ===

==== Console utilities ====

[https://cmder.net/ Cmder] is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.

[https://conemu.github.io/ ConEmu-Maximus5] aims to be handy, comprehensive, fast and reliable terminal window where you may host any console application developed either for WinAPI (cmd, powershell, far) or Unix PTY (cygwin, msys, wsl bash).

[https://github.com/cmderdev/cmder/wiki/How-to-start-Cmder-from-anywhere Steps to put Cmder in your environment variable]

==== eBook ====

[http://calibre-ebook.com/about calibre] is a free and open source e-book library management application developed by users of e-books for users of e-books. It has a cornucopia of features divided into the following main categories:

* Library Management
* E-book conversion
* Syncing to e-book reader devices
* Downloading news from the web and converting it into e-book form
* Comprehensive e-book viewer
* Content server for online access to your book collection

==== Screen Capture ====

In December of 2017 I switched my entire family over to [http://getgreenshot.org/ Greenshot] for screen capture software. With each new version of SnagIt the user interface kept getting worse. Not only is Greenshot free I actually like using it more than SnagIt. I have been using TechSmith's SnagIt for many years and with each newer version of SnagIt I had to buy another copy and the program got worse due to added complexity and bloat.

[https://www.techsmith.com/snagit.html Snagit] by TechSmith

'''Note on Snagit version 12.4.1''' I noticed a TechSmith Uploader Service taking up 1.7 MB of RAM. I contacted TechSmith support and explained what the service did and how to remove it.

'''Purpose:''' The TechSmith Uploader Service is used when Snagit is integrated with TechSmith Relay, which is an Enterprise service that we offer. The service is designed to run in the background and not be visible to the user.

'''Removal:''' Remove TechSmith Uploader Service by browsing to C:\Program Files (x86)\Common Files\TechSmith Shared\Uploader on your computer. Right click on the "UninstallAndRemoveUploader.cmd" file and choose Run as administrator. Once that is done reboot your machine.

==== Password manager ====

[http://keepass.info/ Keepass] is a free open source password manager, which helps you to manage your passwords in a secure way. You can put all your passwords in one database, which is locked with one master key or a key file. So you only have to remember one single master password or select the key file to unlock the whole database. The databases are encrypted using the best and most secure encryption algorithms currently known (AES and Twofish). For more information, see the [http://keepass.info/features.html features page].

==== PDF Viewer & Printer ====

[http://www.foxitsoftware.com/pdf/rd_intro.php Foxit Reader] Foxit Reader is a free PDF document viewer and printer, with incredible small size (only 2.55 M download size), breezing-fast launch speed and rich feature set. Foxit Reader supports Windows Me/2000/XP/2003/Vista. Its core function is compatible with PDF Standard 1.7.

==== Compression ====

===== Open Source =====

[http://peazip.sourceforge.net/ Peazip] Note: Ensure you read install directions carefully to avoid extra software (crapware?)

===== Closed source =====
[http://www.rarlab.com/ WinRAR]

==== Backup ====

MozBackup is a simple utility for creating backups of Mozilla Firefox, Mozilla Thunderbird, Mozilla Sunbird, Flock, SeaMonkey, Mozilla Suite, Spicebird and Netscape profiles.

[http://mozbackup.jasnapaka.com/ MozBackup]

==== Hardware Monitor ====

[http://www.almico.com/speedfan.php SpeedFan] is a program that monitors voltages, fan speeds and temperatures in computers with hardware monitor chips. SpeedFan can even access S.M.A.R.T. info for those hard disks that support this feature and show hard disk temperatures too, if supported.

==== GPU Utilities ====

[http://www.radeonpro.info/en-US/ RadeonPro]

==== HASH utilities ====

Use [https://wiki.gotopinion.info/wiki/index.php?title=Windows_Operating_System#HASH_in_PowerShell PowerShell built-in command]

Command line [https://kanguru.zendesk.com/entries/21747773-SHA256-Checksum-Utility SHA256 Checksum Utility] for Windows

=== Voxel utilities ===

[https://ephtracy.github.io/index.html MagicaVoxel] is a free lightweight 8-bit voxel art editor and GPU based interactive path tracing render-er.

[https://ephtracy.github.io/index.html?page=mv_controls MagicaVoxel] keyboard shortcuts.

===== Tutorials =====

[https://www.megavoxels.com/2019/08/magicavoxel-3d-art-tutorial-for.html MagicaVoxel 3D Art Tutorial for Beginners]

== Accessories ==

=== Mouse pads ===

[http://www.xtracpads.com/ XTracPads]
<pre>Prefer Xtracpads</pre>

[http://www.ratpadz.com/ RatPadz]
<pre>Second choice is RatPadz. Over the years my Ratpadz start to fail
as the surface becomes worn & smooth in areas which impacts laser mouse
movement</pre>

=== To Go ===

[http://www.geargrip.com/index.php Gear Grip]

Personal Computer

2026-02-22T18:24:11Z

Paul: /* WAN connectivity */

Hardware, software and accessories that are used on personal computers.

I use [http://www.newegg.com/ NewEgg] for about 95% of my computer related purchases and [http://www.microcenter.com MicroCenter] and [http://www.amazon.com/ Amazon] for the remaining 5%. NewEgg service, price, and website interface leave the others in the dust.

== Household Personal Computers ==

When I remember I keep this up-to-date.

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Nickname
! Primary User
! CPU
! Memory
! Video Adapters
! Storage Devices
! Monitors
! Power Supply
! Motherboard
! Case
! Operating System
|-
| sourdough
| daddy
| i7-7700K Kaby Lake @ 4.2 GHz
| 32GB(2x16)
| Two EVGA GeForce GTX 1070 SC GAMING ACX 3.0 8GB (SLI)
| Intel SSD 600p + 1 TB HDD
| Three 23" Dell LCD + 1 Acer 23" accessory
| CORSAIR RM750X 750W 80 PLUS GOLD
| ASUS ROG STRIX Z270H
| Cooler Master HAF 912
| Win 10 64-bit
|-
| frog
| mommy
| AMD FX-6350 Six-Core @ 3.9GHz
| 16GB(4x4)
| One XFX R9-270X-CDFC Radeon R9 270X
| One Seagate 7200RPM 1TB HDD 64MB cache
| Acer G6 G246HLAbd 24" LED
| Corsair HX 850
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 912
| Win 10 64-bit
|-
| irish
| 13-year old daughter
| AMD FX-8350 Black Edition Vishera 8-Core @ 4.0GHz
| 32GB (4 x 8GB) DDR3 1866
| EVGA NVidia GTX 560Ti
| One Seagate 1TB 7200 RPM
| One 23" Dell LCD
| Corsair HX 750
| ASUS SABERTOOTH 990FX R2.0 AM3+ AMD 990FX
| Cooler Master HAF 922
| Win 10 64-bit
|-
| elephant
| 11-year old daughter
| i5-4690 @ 3.5 GHz
| 32GB(4x8)
| EVGA GeForce GTX 770 4GB
| One 2TB HDD
| Three 23" Dell LCD + 1 HP 23" accessory
| Corsair HX 1050
| ASUS Sabertooth Z97 Mark1
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit
|-
| spiderman
| 8-year old son
| AMD FX-8150 Quad-core @ 3.6GHz
| 16GB(4x4)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| Western Digital 1TB HDD
| One 23" Dell LCD
| Corsair HX 850
| MSI 990FXA-GD80 V2
| generic
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| koala
| 6-year old son
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB (4x8)
| One XFX FX-785A-CDFC Radeon HD 7850 2GB
| One 1TB HDD
| One 23" Dell LCD
| XFX PRO850W XXX Edition Semi-Modular
| ASUS SABERTOOTH 990FX R2.0
| Silverstone
| Win 10 64-bit & Linux Mint w/Cinnamon
|-
| shark
| daddy
| AMD FX-8150 Eight-Core @ 3.6GHz
| 32GB(4x8)
| Two XFX FX-785A-CDFC Radeon HD 7850 2GB (Eyefinity @ 5760 x 1080)
| Samsung 256GB SDD
| Three 23" Dell LCD (Eyefinity)
| Corsair HX 1050
| ASUS SABERTOOTH 990FX R2.0
| Cooler Master HAF 932 Advanced RC-932-KKN5-GP
| Win 10 64-bit & Linux Mint w/MATE
|-
| hammerhead
| daddy
| Intel Core i5-6600 6M Skylake Quad-Core 3.3 GHz
| 32GB (4x8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000)
| Built-In Intel
| Samsung 950Pro SSD
| Acer H6 H236HL 23"
| Coolmaster GX 750W
| SABERTOOTH Z170 MARK 1
| Antec full tower
| Linux Fedora Core Release 23 64-bit
|-
| steamnuc
| daddy
| Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
| 16GB (2 x 8GB 260Pin SO-DIMM DDR4 2133)
| Intel Iris Plus Graphics 650
| Samsung 950Pro SSD
| Headless
| Built-in
| Built-in
| NUC7I7BNH
| Linux Ubuntu 20.04.6 LTS
|}

== Home Network ==

=== WAN connectivity ===

Our house uses both Verizon Fios at 2 Gbps synchronous Internet.

=== LAN connectivity ===

Our house has a 1 Gbps wired network over Unshielded Twisted Pair (UTP) CAT5E with face plates installed in various rooms. The wires connect to a 24-port patch panel. The 24-port patch panel connects to a 24-port non-managed Gigabit switch.

== Old notes regarding some computer issues ==

=== Marvell 91xx Config ATA Device ===

'''Issue:'''

BIOS defaults to IDE Mode and I changed to AHCI Mode. Windows found standard AHCI 1.0 Serial ATA Controller and ATA Channel 0 through 7. The Marvell driver failed and I got a "No driver found" for Marvell 91xx Config ATA Device.

'''Screen capture (no driver):'''

[[File:marvellNoDriver.png]]

'''Fix:'''

I downloaded Marvell 91XX Controller Beta Driver V1.2.0.1002 for Windows 32/64bit Vista & 32/64bit Windows 7.(WHQL) Beta Version 1.2.0.1002 from [http://support.asus.com/Download/Options.aspx ASUS support] page then installed it. Windows 7 did not even require a reboot and drive has been found.

'''Screen capture (driver installed):'''

[[File:marvellDriverInstalled.png]]

[http://www.intel.com/p/en_US/support/highlights/dsktpboards/dx48bt2 Intel DX48BT2] motherboard support site

== Software ==

=== Office Suite ===

[http://www.libreoffice.org/ Libre Office]

=== Image or graphic tools ===

Use [https://imagemagick.org/ ImageMagick®] to create, edit, compose, or convert bitmap images. It can read and write images in a variety of formats (over 200) including PNG, JPEG, GIF, HEIC, TIFF, DPX, EXR, WebP, Postscript, PDF, and SVG. Use ImageMagick to resize, flip, mirror, rotate, distort, shear and transform images, adjust image colors, apply various special effects, or draw text, lines, polygons, ellipses and Bézier curves.

ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under a derived Apache 2.0 license.

ImageMagick utilizes multiple computational threads to increase performance and can read, process, or write mega-, giga-, or tera-pixel image sizes.

==== Vector graphics ====

[https://inkscape.org/en/about/ Inkscape] is professional quality vector graphics software that runs on Windows, Mac OS X and GNU/Linux. It is used by design professionals and hobbyists worldwide, for creating a wide variety of graphics such as illustrations, icons, logos, diagrams, maps and web graphics. Inkscape uses the W3C open standard SVG (Scalable Vector Graphics) as its native format, and is free and open-source software.

=== CD / DVD Burning software ===

To burn data and audio CD / DVDs I use [http://cdburnerxp.se/ CD BurnerXP].

To create personal copies of protected DVDs that I have purchased I use [http://www.1clickdvdcopy.com/1clickdvdcopypro.asp 1ClickDVDCopy Pro] ($79 fee) and [http://www.dvd43.com/ DVD43], a free decrypter.

=== Multimedia software ===

[http://www.videolan.org/vlc/ VLC] - the cross-platform media player and streaming server.

VLC media player is a highly portable multimedia player for various audio and video formats (MPEG-1, MPEG-2, MPEG-4, DivX, mp3, ogg, ...) as well as DVDs, VCDs, and various streaming protocols. It can also be used as a server to stream in unicast or multicast in IPv4 or IPv6 on a high-bandwidth network.

==== Video Capture ====

[http://www.fraps.com/ Fraps] is a universal Windows application that can be used with games using DirectX or OpenGL graphic technology. In its current form Fraps performs many tasks and can best be described as:
* Benchmarking Software
* Screen Capture Software
* Realtime Video Capture Software

==== Video Editing ====

[https://www.mp4joiner.org/en/ MP4Tools] is a collection of cross-platform free tools to manipulate MP4 files. It contains following applications:

*MP4Joiner is a free application that allows join multiple MP4 files into one without reencoding and without quality loss.
*MP4Splitter is a free application that allows split a MP4 file in multiple files without reencoding and without quality loss

MP4Tools is Open Source Software and is completely free.

[http://www.freemake.com/ Freemake] offers freeware in the truest sense of the word: no feature or time limitations, no hidden costs. Download and use our free Video Converter, Video Downloader, Audio Converter and Free Music Box! Convert video free to AVI, MP4, WMV, MKV, FLV, 3GP, MPEG, DVD, Blu-ray, MP3, iPod, iPhone, iPad, PSP, Android, Nokia, Samsung, BlackBerry with [http://www.freemake.com/free_video_converter/ Free Video Converter]. Convert audio free to MP3, WMA, WAV, FLAC, AAC, M4A, OGG, convert audio to MP3 player, iPod, iPhone, iPad, PSP, and more with our [http://www.freemake.com/free_audio_converter/ Free Audio Converter].

<pre>I like FreeMake products as the software is simple to use & their site provides video tutorials.
Their products work, have lots of features, & no hidden spyware or adware.</pre>

[http://www.tmpgenc.net/en/index.html TMPGEnc] converts *.AVI files to MPEG1, the format which is used in VideoCDs. Using a variety of options in TMPGEnc, you can compress your video file in high quality.

TMPGEnc enables you to adjust bitrate, quantize matrix, GOP structure, interlacing and many other parameters so that you can create the most appropriate movie file depending on your needs.

[http://www.virtualdub.org/ Virtualdub]is a video capture/processing utility for 32-bit and 64-bit Windows platforms (98/ME/NT4/2000/XP/Vista/7), licensed under the GNU General Public License (GPL). It lacks the editing power of a general-purpose editor such as Adobe Premiere, but is streamlined for fast linear operations over video. It has batch-processing capabilities for processing large numbers of files and can be extended with third-party video filters.

=== Communications Software ===

==== Browser and E-mail ====

[http://www.mozilla.com/en-US/ Firefox and Thunderbird]

[[My Thunderbird Notes]]

===== Firefox add-ons =====

FireFTP

Download Status Bar

[http://www.zotero.org/ Zotero] is a free, easy-to-use Firefox extension to help you collect, manage, cite, and share your research sources. It lives right where you do your work—in the web browser itself.

==== Torrent ====

[http://www.qbittorrent.org/ qBittorrent] project aims to provide a '''free software''' alternative to µtorrent. Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).

==== Java ====

[http://www.java.com/en/download/manual.jsp Java]

==== FTP clients ====

[http://filezilla-project.org/ Filezilla]

==== VoIP clients ====

[http://www.ventrilo.com/ Ventrillo]

[http://www.goteamspeak.com/ TeamSpeak]

==== IRC client ====

[http://hexchat.github.io/index.html HexChat]

==== SSHv2 & SFTP ====

I switched to [https://www.bitvise.com/ssh-client Bitvise SSH client] for SSH client. I like some of the features Bitvise offers. [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty] is a free SSHv2 program. You can also get SecureFTP program from same site.

[http://www.mremoteng.org/ mRemoteNG] is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager. mRemoteNG adds bug fixes and new features to mRemote.

eRemoteNG allows you to view all of your remote connections in a simple yet powerful tabbed interface.

mRemoteNG supports the following protocols:
* RDP (Remote Desktop/Terminal Server)
* VNC (Virtual Network Computing)
* ICA (Citrix Independent Computing Architecture)
* SSH (Secure Shell version 1 & 2)
* Telnet (TELecommunication NETwork)
* HTTP/HTTPS (Hypertext Transfer Protocol)
* rlogin
* Raw Socket Connections

==== Tunnelier ====

[http://www.bitvise.com/tunnelier Bitvise Tunnelier]

=== Utilities ===

==== Console utilities ====

[https://cmder.net/ Cmder] is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.

[https://conemu.github.io/ ConEmu-Maximus5] aims to be handy, comprehensive, fast and reliable terminal window where you may host any console application developed either for WinAPI (cmd, powershell, far) or Unix PTY (cygwin, msys, wsl bash).

[https://github.com/cmderdev/cmder/wiki/How-to-start-Cmder-from-anywhere Steps to put Cmder in your environment variable]

==== eBook ====

[http://calibre-ebook.com/about calibre] is a free and open source e-book library management application developed by users of e-books for users of e-books. It has a cornucopia of features divided into the following main categories:

* Library Management
* E-book conversion
* Syncing to e-book reader devices
* Downloading news from the web and converting it into e-book form
* Comprehensive e-book viewer
* Content server for online access to your book collection

==== Screen Capture ====

In December of 2017 I switched my entire family over to [http://getgreenshot.org/ Greenshot] for screen capture software. With each new version of SnagIt the user interface kept getting worse. Not only is Greenshot free I actually like using it more than SnagIt. I have been using TechSmith's SnagIt for many years and with each newer version of SnagIt I had to buy another copy and the program got worse due to added complexity and bloat.

[https://www.techsmith.com/snagit.html Snagit] by TechSmith

'''Note on Snagit version 12.4.1''' I noticed a TechSmith Uploader Service taking up 1.7 MB of RAM. I contacted TechSmith support and explained what the service did and how to remove it.

'''Purpose:''' The TechSmith Uploader Service is used when Snagit is integrated with TechSmith Relay, which is an Enterprise service that we offer. The service is designed to run in the background and not be visible to the user.

'''Removal:''' Remove TechSmith Uploader Service by browsing to C:\Program Files (x86)\Common Files\TechSmith Shared\Uploader on your computer. Right click on the "UninstallAndRemoveUploader.cmd" file and choose Run as administrator. Once that is done reboot your machine.

==== Password manager ====

[http://keepass.info/ Keepass] is a free open source password manager, which helps you to manage your passwords in a secure way. You can put all your passwords in one database, which is locked with one master key or a key file. So you only have to remember one single master password or select the key file to unlock the whole database. The databases are encrypted using the best and most secure encryption algorithms currently known (AES and Twofish). For more information, see the [http://keepass.info/features.html features page].

==== PDF Viewer & Printer ====

[http://www.foxitsoftware.com/pdf/rd_intro.php Foxit Reader] Foxit Reader is a free PDF document viewer and printer, with incredible small size (only 2.55 M download size), breezing-fast launch speed and rich feature set. Foxit Reader supports Windows Me/2000/XP/2003/Vista. Its core function is compatible with PDF Standard 1.7.

==== Compression ====

===== Open Source =====

[http://peazip.sourceforge.net/ Peazip] Note: Ensure you read install directions carefully to avoid extra software (crapware?)

===== Closed source =====
[http://www.rarlab.com/ WinRAR]

==== Backup ====

MozBackup is a simple utility for creating backups of Mozilla Firefox, Mozilla Thunderbird, Mozilla Sunbird, Flock, SeaMonkey, Mozilla Suite, Spicebird and Netscape profiles.

[http://mozbackup.jasnapaka.com/ MozBackup]

==== Hardware Monitor ====

[http://www.almico.com/speedfan.php SpeedFan] is a program that monitors voltages, fan speeds and temperatures in computers with hardware monitor chips. SpeedFan can even access S.M.A.R.T. info for those hard disks that support this feature and show hard disk temperatures too, if supported.

==== GPU Utilities ====

[http://www.radeonpro.info/en-US/ RadeonPro]

==== HASH utilities ====

Use [https://wiki.gotopinion.info/wiki/index.php?title=Windows_Operating_System#HASH_in_PowerShell PowerShell built-in command]

Command line [https://kanguru.zendesk.com/entries/21747773-SHA256-Checksum-Utility SHA256 Checksum Utility] for Windows

=== Voxel utilities ===

[https://ephtracy.github.io/index.html MagicaVoxel] is a free lightweight 8-bit voxel art editor and GPU based interactive path tracing render-er.

[https://ephtracy.github.io/index.html?page=mv_controls MagicaVoxel] keyboard shortcuts.

===== Tutorials =====

[https://www.megavoxels.com/2019/08/magicavoxel-3d-art-tutorial-for.html MagicaVoxel 3D Art Tutorial for Beginners]

== Accessories ==

=== Mouse pads ===

[http://www.xtracpads.com/ XTracPads]
<pre>Prefer Xtracpads</pre>

[http://www.ratpadz.com/ RatPadz]
<pre>Second choice is RatPadz. Over the years my Ratpadz start to fail
as the surface becomes worn & smooth in areas which impacts laser mouse
movement</pre>

=== To Go ===

[http://www.geargrip.com/index.php Gear Grip]

Recipes

2026-02-22T00:42:11Z

Paul:

A collection of recipes that I use.

[[Saladmaster recipes]]

[[Slow Cooker recipes]]

[[One Pot recipes]]

[https://cafedelites.com/easy-buttermilk-cornbread/ Cornbread]

[https://hurstbeans.com/recipes/slow-cooker-ham-and-beans Ham and beans]

[http://www.recipezaar.com/Alfredo-Sauce-64196 Alfredo Sauce]

=== [http://allrecipes.com/Recipe/Alfredo-Sauce-2/Detail.aspx Alfredo Sauce]===
Ingredients:

* 1/2 cup butter
* 8 ounces cream cheese
* 8 ounces half-and-half cream
* 1/4 cup parmesan cheese
* 1 teaspoon garlic powder
* black pepper (to taste)

Directions
# Melt butter in sauce pan
# Add cream cheese and whisk as you add half-and-half
# Whisk until smooth adding cheese, garlic powder and pepper.
# Simmer until heated through

[[Hungarian Goulash]] with noodles

[[Knedliky]] from Czech cookbook

[https://www.bonappetit.com/recipe/master-buttermilk-brine Master buttermilk brine]

[[Knedliky Czech Dumplings]] from Czech family recipe

[[Flaky Biscuit]]

[[Enchiladas]]

[http://allrecipes.com/Recipe/JPs-Big-Daddy-Biscuits/Detail.aspx JP's Big Daddy Biscuits]

[https://dinnerthendessert.com/ground-beef-cabbage-soup/ Ground beef and cabbage soup]

<center>[[Main Page]]</center>

One Pot recipes

2026-02-22T00:41:12Z

Paul:

== Lentils and Rice ==
[https://cardamomandtea.com/36/lentils-and-rice/ Source]
* 1 pound lentils (brown or green)
* 1 cup basmati rice
* 1/4 cup extra virgin olive oil
* 1 small onion, diced
* 3 cups boiling water
* 2 teaspoons kosher salt

# Rinse the lentils and sort through them for little pebbles. Add enough water to cover the lentils and rice by about 3 inches.
# Turn the heat to high. Once the pot of water and lentils comes to a boil, turn the heat to medium and boil uncovered for about 10 to 15 minutes.
# While the lentils are cooking, rinse the rice until the water runs clear and set it aside.
# Start testing the lentils for doneness before the 10 minute mark. The lentils are ready once they are unpleasantly al dente. You should be able to chew one (it should be somewhat soft and no longer hard in the center), but it should still be gritty and mealy.
# Once the lentils are ready, strain them and rinse them until the water runs clear.
# Use a damp paper towel to wipe down the sides of the pot that you cooked the lentils in until the scum is completely gone.
# Add the olive oil to the pot, turn the heat to medium and add the diced onion. Cook, stirring occasionally, until the onion softens (about 5 minutes).
# Add the lentils back into the pot, along with the rinsed rice, kosher salt, and 3 cups boiling water. Stir together and shake everything out into an even layer.
# Turn the heat to high. Once the water comes back up to a boil, cover, lower the heat to low, and cook for 15 minutes. Do not look inside the pot while the lentils and rice are cooking. If you do look, absolutely do not stir.
# Once 15 minutes have passed, open the lid, do not stir the lentils and rice, and take a taste. If they taste done, cover, continue to heat for another 30 seconds, and then turn the heat off, keeping them covered.
# Keep the pot covered for another 10 to 15 minutes after you’ve turned off the heat.
# After 10 minutes of resting, fluff the lentils and rice with a fork and serve.

<center>[[Recipes|To Recipes]]</center>

One Pot recipes

2026-02-22T00:41:04Z

Paul:

One Pot recipes

2026-02-15T18:58:17Z

Paul: added header

One Pot recipes

2026-02-15T03:30:16Z

Paul: initial page

Lentils and Rice [https://cardamomandtea.com/36/lentils-and-rice/ Source]
* 1 pound lentils (brown or green)
* 1 cup basmati rice
* 1/4 cup extra virgin olive oil
* 1 small onion, diced
* 3 cups boiling water
* 2 teaspoons kosher salt

# Rinse the lentils and sort through them for little pebbles. Add enough water to cover the lentils and rice by about 3 inches.
# Turn the heat to high. Once the pot of water and lentils comes to a boil, turn the heat to medium and boil uncovered for about 10 to 15 minutes.
# While the lentils are cooking, rinse the rice until the water runs clear and set it aside.
# Start testing the lentils for doneness before the 10 minute mark. The lentils are ready once they are unpleasantly al dente. You should be able to chew one (it should be somewhat soft and no longer hard in the center), but it should still be gritty and mealy.
# Once the lentils are ready, strain them and rinse them until the water runs clear.
# Use a damp paper towel to wipe down the sides of the pot that you cooked the lentils in until the scum is completely gone.
# Add the olive oil to the pot, turn the heat to medium and add the diced onion. Cook, stirring occasionally, until the onion softens (about 5 minutes).
# Add the lentils back into the pot, along with the rinsed rice, kosher salt, and 3 cups boiling water. Stir together and shake everything out into an even layer.
# Turn the heat to high. Once the water comes back up to a boil, cover, lower the heat to low, and cook for 15 minutes. Do not look inside the pot while the lentils and rice are cooking. If you do look, absolutely do not stir.
# Once 15 minutes have passed, open the lid, do not stir the lentils and rice, and take a taste. If they taste done, cover, continue to heat for another 30 seconds, and then turn the heat off, keeping them covered.
# Keep the pot covered for another 10 to 15 minutes after you’ve turned off the heat.
# After 10 minutes of resting, fluff the lentils and rice with a fork and serve.

Recipes

2026-02-15T03:00:46Z

Paul: added one pot recipes

A collection of recipes that I use.

[[Saladmaster recipes]]

[[Slow Cooker recipes]]

[[One Pot recipes]]

[http://www.recipezaar.com/Alfredo-Sauce-64196 Alfredo Sauce]

=== [http://allrecipes.com/Recipe/Alfredo-Sauce-2/Detail.aspx Alfredo Sauce]===
Ingredients:

* 1/2 cup butter
* 8 ounces cream cheese
* 8 ounces half-and-half cream
* 1/4 cup parmesan cheese
* 1 teaspoon garlic powder
* black pepper (to taste)

Directions
# Melt butter in sauce pan
# Add cream cheese and whisk as you add half-and-half
# Whisk until smooth adding cheese, garlic powder and pepper.
# Simmer until heated through

[[Hungarian Goulash]] with noodles

[[Knedliky]] from Czech cookbook

[https://www.bonappetit.com/recipe/master-buttermilk-brine Master buttermilk brine]

[[Knedliky Czech Dumplings]] from Czech family recipe

[[Flaky Biscuit]]

[[Enchiladas]]

[http://allrecipes.com/Recipe/JPs-Big-Daddy-Biscuits/Detail.aspx JP's Big Daddy Biscuits]

[https://dinnerthendessert.com/ground-beef-cabbage-soup/ Ground beef and cabbage soup]

<center>[[Main Page]]</center>

Telecommunications info

2026-02-03T17:43:42Z

Paul: added 104 144

== NNI Task Force ==

[https://www.sipforum.org/activities/nni-task-force-introduction/ NNI Task Force Introduction]

== 3GPP SA3 Security ==

[https://www.3gpp.org/specifications-groups/sa-plenary/sa3-security SA3 - Security]

== [https://www.3gpp.org/specifications/79-specification-numbering 3GPP Standards] ==

[https://www.3gpp.org/specifications/79-specification-numbering 3GPP specification numbering]

[https://www.3gpp.org/DynaReport/status-report.htm 3GPP Specification Status Report]

=== Definition and abbreviations ===

See [[My 3GPP definition notes]] for definitions

See [[My 3GPP abbreviation notes]] for abbreviations

=== EPS and NR related standards with notes ===

[[My New Radio (NR) notes]]

{| class="wikitable sortable"
|-
! Standard # !! Title !! Notes
|-
| 22.011
| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service accessibility
| The purpose of 22.011 is to describe the service access procedures as presented to the user. Definitions and procedures are provided in 22.011 for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station, or User Equipment (UE).

[[My 3GPP TS 22.011 Notes]]
|-
| [https://www.3gpp.org/DynaReport/22261.htm 22.261] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service requirements for the 5G system;
Stage 1
|| Document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278.
|-
| 23.122 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|| Document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 and 3GPP TS 38.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 and 3GPP TS 38.331.
|-
| [https://www.3gpp.org/DynaReport/23271.htm 23.271] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Functional stage 2 description of Location Services (LCS)
(Release 16)
|| Document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers. Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 and TS 23.502 in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3577 23.273] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
5G System (5GS) Location Services (LCS);
Stage 2
|| V17.5.0 document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 and TS 22.071.
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access
(Release 17)
|| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.

[[My 3GPP 23.401 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
System architecture for the 5G System (5GS);
Stage 2
|| 5G core network

[[My 3GPP 23.501 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Procedures for the 5G System (5GS);
Stage 2
| V17.5.0 document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 and for the policy and charging control framework which is described in TS 23.503.

[[My 3GPP 23.502 Notes]]
|-
| 24.229 || Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 || P-Access-Network-Info values for "cgi-3gpp", "utran-cell-id-3gpp", "i-wlan-node-id", "dsl-location", "ci-3gpp2", "ci-3gpp2-femto" and "gstn-location" are defined in section 7.2A.4
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3370 24.501] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) protocol for 5G System (5GS);
Stage 3;
|| This present document specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for:
* mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and
* session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.
The 5GS mobility management (5GMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the NG radio access network (NG-RAN) and/or non-3GPP access network. The 5GMM protocol also provides control of security for the NAS protocols.

[[My 3GPP 24.501 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3371 24.502] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Access to the 3GPP 5G Core Network (5GCN)
via Non-3GPP Access Networks (N3AN);
Stage 3
|| This document specifies non-3GPP access network discovery and selection procedures, the access authorization procedure used for accessing non-3GPP access networks. These non-3GPP access networks can be trusted non-3GPP access networks, untrusted non-3GPP access networks or wireline access networks.
|-
| 29.503 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
5G System; Unified Data Management Services;
Stage 3
|| The document specifies the stage 3 protocol and data model for the Nudm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDM.

The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 and 3GPP TS 23.502.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 and 3GPP TS 29.501.
|-
| 29.279 || Universal Mobile Telecommunications System (UMTS); LTE; Mobile IPv4 (MIPv4) based mobility protocols; Stage 3 ||
|-
| [https://www.3gpp.org/DynaReport/29571.htm 29.571] || 5G System; Common Data Types for Service Based Interfaces; Stage 3 || The document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
|-
| [https://www.3gpp.org/DynaReport/33501.htm 33.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security architecture and procedures for 5G system
|| Document specifies the security architecture, i.e., the security features and the security mechanisms for the 5G System and the 5G Core, and the security procedures performed within the 5G System including the 5G Core and the 5G New Radio.

[[My 3GPP 33.501 notes]]
|-
| [https://www.3gpp.org/DynaReport/37340.htm 37.340] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA) and NR;
Multi-connectivity;
Stage 2
|| Document provides an overview of the multi-connectivity operation using E-UTRA and NR radio access technologies.
|-
| 38.300 || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2
|| This document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

[[My 3GPP 38.300 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38304.htm 38.304] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
User Equipment (UE) procedures in Idle mode and RRC Inactive state
|| Document specifies the Access Stratum (AS) part of the UE procedures in RRC_IDLE state (also called Idle mode) and RRC_INACTIVE state. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in TS 23.122.

[[My 3GPP TS 38.304 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3197 38.331] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
Radio Resource Control (RRC) protocol specification
(Release 17)
|| This document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN.
|-
| [https://www.3gpp.org/DynaReport/38401.htm 38.401] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description || Document describes the overall architecture of the NG-RAN, including interfaces NG, Xn and F1 interfaces and their interaction with the radio interface.

[[My 3GPP TS 38.401 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38413.htm 38.413] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP)(Release 16) || This document specifies the radio network layer signalling protocol for the NG interface. The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document. NGAP is developed in accordance to the general principles stated in TS 38.401 and TS 38.410.
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

== 3GPP/ETSI info ==

[https://www.etsi.org/technologies/5g ETSI 5G information page]

[https://www.etsi.org/technologies/lawful-interception ETSI Lawful Interception (LI) information page]

[https://www.etsi.org/committee/1403-li ETSI Technical Committee (TC) Lawful Interception information page] and contains list of latest publications

=== [https://www.etsi.org/standards ETSI Standards] ===

==== Lawful Interception or Related Standards ====

{| class="wikitable sortable"
|-
! ETSI Standard
! Title
! Notes
|-
| ETSI TS 102 232-1 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery || This document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. This document:
* specifies the modular approach used for specifying IP based handover interfaces;
* specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
* specifies protocols for the transfer of IRI and CC across the handover interfaces;
* specifies protocol profiles for the handover interface.

[[My 102 232-1 notes]]
|-
| ETSI TS 102 232-2 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services || This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.
|-
| ETSI TS 102 232-3 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services || This document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The study includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets.

The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1.

[[My 102 232-3 notes]]
|-
| ETSI TS 102 232-4 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services ||
|-
| ETSI TS 102 232-5 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services || Document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Real Time Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IPMM services as described by the Recommendations ITU-T H.323 and H.248-1.

The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1.

The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 and ETSI TS 101 671.
|-
| ETSI TS 102 232-6 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services ||
|-
| ETSI TS 102 232-7 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services ||
|-
| ETSI TR 102 528 || Lawful Interception (LI); Interception domain Architecture for IP networks || Document describes a high level reference architecture for supporting lawful interception in network operator (NWO) and communication service providers (SvP) domain for IP networks.

The document contains:
* A reference model in the network operator (NWO) and communication service provider (SvP) domain.
* A High level description of Internal Network Functions and Interfaces.
* Application of the reference model to voice and multimedia over IP services, data layer 3 and layer 2 services.
|-
| ETSI TS 103 221 || Lawful Interception (LI); Internal Network Interfaces || Part I (X1) and Part II (X2/X3) [[My TS 103 221-2 notes]]
|-
| ETSI TS 103 643 || Techniques for assurance of digital material used in legal proceedings ||
|-
| ETSI TS 101 671 & ETSI ES 201 671 || Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic || Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service.
* Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331.
* Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
|-
| ETSI TS 103 462 || Lawful Interception (LI); Inter LEMF Handover Interface ||
|-
| style="white-space: nowrap;" | ETSI TR 102 503 || Lawful Interception (LI); ASN.1 Object Identifiers in Lawful Interception and Retained data handling Specifications ||
|-
| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data ||
|-
| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data ||
|-
| ETSI TS 101 331 || Lawful Interception (LI); Requirements of Law Enforcement Agencies || Document gives guidance for lawful interception of telecommunications in the area of co-operation by network operators, access providers, and service providers. Document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
|-
| ETSI TS 103 707 || Lawful Interception (LI); Handover for messaging services over HTTP/XML || Document specifies the handover details to deliver messaging services for LI over HTTP/XML
|-
| ETSI TS 103 120 || Lawful Interception (LI); Interface for warrant information || Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.
|-
| ETSI TS 104 144 || Interface definition for the e-Evidence Regulation (EU) 2023/1543 for National Authorities and Service Providers || Document provides an interface definition for the e-Evidence Regulation (EU) 2023/1543, supporting National Authorities and Service Providers in understanding and complying with its requirements.
|-
| ETSI TS 103 280 || Lawful Interception (LI); Dictionary for common parameters || Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]
|-
| ETSI TS 103 690 || Lawful Interception (LI); eWarrant Interface || Document presents a high-level description of an interface mechanism - the eWarrant Interface - for receipt of requests for measures producing real-time or stored information by an issuing authority possessing lawful authorization to initiate such a request
|-
| || ||
|-
| || ||
|-
| || ||
|}

==== Other Standards ====

{| class="wikitable sortable"
|-
! 3GPP
! Title
! Notes
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729 23.003]
|| 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)
|| This document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system. IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator.

[[My 3GPP TS 23.003 notes]]
|-
| [https://www.3gpp.org/DynaReport/23228.htm 23.228]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 16)
|| This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. [[My 3GPP TS 23.228 Notes]]
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 16)
|| The document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1014 24.007]
| 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface signalling layer 3;
General aspects
(Release 17)
| 24.007 document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
This document also defines the principal architecture of the EPS NAS and 5GS NAS layer 3 protocol and their sublayers, including the message format applied by layer 3.

[[My 3GPP TS 24.007 Notes]]
|-
| 33.108 || UMTS; LTE; GSM; 3G Security; Handover interface for lawful interception (LI) || [[My TS 133 108 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3182 33.127] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Lawful Interception (LI) architecture and functions
|| This document specifies both the architectural and functional system requirements for Lawful Interception (LI) in 3GPP networks. The present document provides an LI architecture supporting both network layer based and service layer based Interception. National regulations determine the specific set of LI functional capabilities that are applicable to a specific 3GPP operator deployment.

[[My 33.127 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3183 33.128] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Protocol and procedures for Lawful Interception (LI);
Stage 3
|| This document specifies the protocols and procedures required to perform Lawful Interception within a 3GPP network. The present document addresses both internal interfaces used internally with a 3GPP network and external handover interfaces used to handover intercepted communications to law enforcement.

[[My 33.128 Notes]]
|}

== Standards related info ==

MCPTT ID parameter is defined in TS 23.280

[[My ATIS lawful interception standard notes]]

[[My lawful interception notes]]

== RFCs of interest ==

[https://tools.ietf.org/html/rfc3261 RFC 3261 SIP: Session Initiation Protocol]

[https://tools.ietf.org/html/rfc3455 RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)]

[https://tools.ietf.org/html/rfc7913 RFC 7913 P-Access-Network-Info ABNF Update]

[https://tools.ietf.org/html/rfc4984 RFC 4984 Report from the IAB Workshop on Routing and Addressing]

[https://tools.ietf.org/html/rfc6830 RFC 6830 The Locator/ID Separation Protocol (LISP)]

== National Requirements Resources ==

[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

== Case Examples ==

[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later.

Interesting sites

2025-12-17T16:37:39Z

Paul: /* Visual data */

== Libertarian ==

[https://reason.com/reasontv/2018/09/20/robot-lawyer-fights-fines-fees-red-tape Robot lawyer fights fines, fees, and red tape]

== Fonts and Colors ==

[https://www.dafont.com/ DaFont] is a collection of fonts

[https://www.1001fonts.com/ 1001 Fonts]

[https://www.colorhexa.com/ Colorhexa]

[https://github.com/anomal/RainbowVis-JS RainbowVis] is a JavaScript library for colour data visualization. Easily map numbers to a smooth-transitioning colour legend.

== Visual data ==

[https://datavizproject.com/ Data Viz Project] is a website trying to present all relevant data visualizations, so you can find the right visualization and get inspired on how to make them.

[https://www.ferdio.com/ Ferdio] is an infographic agency and they add value to data and information and transform it into captivating visuals.

[https://www.cdse.edu/Training/Security-Posters/ Security Posters] with wonderful art

== Open Street Map ==

[http://www.openstreetmap.org/index.html OpenStreetMap] is a free worldwide map, created by people like you.

[https://osmlab.github.io/show-me-the-way/ Show Me the Way] shows real edits to OpenStreetMap from across the globe.

[https://mapforenvironment.org/ Map for Environment]

[http://map.openseamap.org/ Open Sea Map]

Blog titled [https://opensource.com/article/17/8/openstreetmap 13 amazing maps to celebrate 13 years of OpenStreetMap]

[https://leafletjs.com/ Leaflet] is the leading open-source JavaScript library for mobile-friendly interactive maps. Weighing just about 38 KB of JS, it has all the mapping features most developers ever need.

[https://openlayers.org/ OpenLayers] makes it easy to put a dynamic map in any web page. It can display map tiles, vector data and markers loaded from any source. OpenLayers has been developed to further the use of geographic information of all kinds. It is completely free, Open Source JavaScript, released under the 2-clause BSD License (also known as the FreeBSD).

== Sites with maps ==

[https://www.visionofhumanity.org/maps/#/ Vision of Humanity Global Peace Index] (GPI)

== Service sites ==

[http://www.sightseven.com/ Sight Seven] is a Toronto video production company providing corporate, commercial & event video services.

[https://vimeo.com/ Vimeo]

[https://www.youtube.com YouTube]

[https://donotpay.com/ Do Not Pay]

== Food ==

The [https://www.cornucopia.org/ Cornucopia Institute], through research and investigations on agricultural and food issues, provides needed information to family farmers, consumers and other stakeholders in the good food movement and to the media. We support economic justice for the family-scale farming community – partnered with consumers – backing ecologically produced local, organic and authentic food.

== Crowd funding related sites ==

[https://www.kickstarter.com/blog/before-you-work-with-a-marketing-service-consider-this Before you work with a marketing service consider this]

== Open Collective ==

[https://opencollective.com/ Open Collective]

== History ==

[https://www.bighistoryproject.com/ Big History] examines our past, explains our present, and imagines our future. It's a story about us. An idea that arose from a desire to go beyond specialized and self-contained fields of study to grasp history as a whole.

== Others ==

[http://www.free-energy.ws/index.html Free Energy research]

[http://www.overunity.com/ Over Unity] the International Open Source Free Energy Research Forum

[http://www.storyofstuff.org/movies-all/story-of-cap-trade/ Story of Cap and Trade]

[http://iconmonstr.com/ Iconmonstr] Free simple icons for your next project.

[http://www.gnu.org/philosophy/open-source-misses-the-point.html Open Source misses the point]

[https://www.howtocallabroad.com/ How to call abroad]

[https://piazza.com/ Piazza] is an incredibly easy, completely free Q&A platform. Save time and help students learn using the power of community

[https://www.writethedocs.org/ Write the Docs] is a global community of people who care about documentation.

Information about banning [https://autonomousweapons.org/ autonomous weapons]

[http://www.goodcountry.org/ The Good Country]

[https://www.genome.gov/human-genome-project/Timeline-of-Events Timeline of Genome project events]

[https://ipi.media/programmes/death-watch/ IPI’s Death Watch] lists journalists and media staff whose deaths have been linked to journalism. The Death Watch includes names of journalists who were deliberately targeted because of their profession – either because of their reporting or simply because they were journalists – as well as those who lost their lives while on assignment

== Location stuff ==

[https://wigle.net/ All the networks. Found by Everyone.]

== Animal stuff ==

=== Insects ===

[https://aeon.co/videos/how-insects-become-airborne-slowed-down-to-a-speed-the-human-eye-can-appreciate How insects become airborne] videos

=== Sharks ===

[https://www.ocearch.org/tracker/ Ocearch Tracker] to see great white, and other, shark locations globally.

== National Security Agency/Central Security Service ==

[https://www.nsa.gov/Press-Room/Cybersecurity-Advisories-Guidance/ NSA Cybersecurity Advisories & Guidance]

<center>[[Main Page | To Main Page]]</center>

Telecommunications info

2025-11-28T17:20:23Z

Paul: /* Case Examples */

== NNI Task Force ==

[https://www.sipforum.org/activities/nni-task-force-introduction/ NNI Task Force Introduction]

== 3GPP SA3 Security ==

[https://www.3gpp.org/specifications-groups/sa-plenary/sa3-security SA3 - Security]

== [https://www.3gpp.org/specifications/79-specification-numbering 3GPP Standards] ==

[https://www.3gpp.org/specifications/79-specification-numbering 3GPP specification numbering]

[https://www.3gpp.org/DynaReport/status-report.htm 3GPP Specification Status Report]

=== Definition and abbreviations ===

See [[My 3GPP definition notes]] for definitions

See [[My 3GPP abbreviation notes]] for abbreviations

=== EPS and NR related standards with notes ===

[[My New Radio (NR) notes]]

{| class="wikitable sortable"
|-
! Standard # !! Title !! Notes
|-
| 22.011
| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service accessibility
| The purpose of 22.011 is to describe the service access procedures as presented to the user. Definitions and procedures are provided in 22.011 for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station, or User Equipment (UE).

[[My 3GPP TS 22.011 Notes]]
|-
| [https://www.3gpp.org/DynaReport/22261.htm 22.261] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service requirements for the 5G system;
Stage 1
|| Document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278.
|-
| 23.122 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|| Document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 and 3GPP TS 38.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 and 3GPP TS 38.331.
|-
| [https://www.3gpp.org/DynaReport/23271.htm 23.271] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Functional stage 2 description of Location Services (LCS)
(Release 16)
|| Document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers. Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 and TS 23.502 in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3577 23.273] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
5G System (5GS) Location Services (LCS);
Stage 2
|| V17.5.0 document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 and TS 22.071.
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access
(Release 17)
|| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.

[[My 3GPP 23.401 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
System architecture for the 5G System (5GS);
Stage 2
|| 5G core network

[[My 3GPP 23.501 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Procedures for the 5G System (5GS);
Stage 2
| V17.5.0 document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 and for the policy and charging control framework which is described in TS 23.503.

[[My 3GPP 23.502 Notes]]
|-
| 24.229 || Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 || P-Access-Network-Info values for "cgi-3gpp", "utran-cell-id-3gpp", "i-wlan-node-id", "dsl-location", "ci-3gpp2", "ci-3gpp2-femto" and "gstn-location" are defined in section 7.2A.4
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3370 24.501] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) protocol for 5G System (5GS);
Stage 3;
|| This present document specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for:
* mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and
* session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.
The 5GS mobility management (5GMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the NG radio access network (NG-RAN) and/or non-3GPP access network. The 5GMM protocol also provides control of security for the NAS protocols.

[[My 3GPP 24.501 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3371 24.502] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Access to the 3GPP 5G Core Network (5GCN)
via Non-3GPP Access Networks (N3AN);
Stage 3
|| This document specifies non-3GPP access network discovery and selection procedures, the access authorization procedure used for accessing non-3GPP access networks. These non-3GPP access networks can be trusted non-3GPP access networks, untrusted non-3GPP access networks or wireline access networks.
|-
| 29.503 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
5G System; Unified Data Management Services;
Stage 3
|| The document specifies the stage 3 protocol and data model for the Nudm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDM.

The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 and 3GPP TS 23.502.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 and 3GPP TS 29.501.
|-
| 29.279 || Universal Mobile Telecommunications System (UMTS); LTE; Mobile IPv4 (MIPv4) based mobility protocols; Stage 3 ||
|-
| [https://www.3gpp.org/DynaReport/29571.htm 29.571] || 5G System; Common Data Types for Service Based Interfaces; Stage 3 || The document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
|-
| [https://www.3gpp.org/DynaReport/33501.htm 33.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security architecture and procedures for 5G system
|| Document specifies the security architecture, i.e., the security features and the security mechanisms for the 5G System and the 5G Core, and the security procedures performed within the 5G System including the 5G Core and the 5G New Radio.

[[My 3GPP 33.501 notes]]
|-
| [https://www.3gpp.org/DynaReport/37340.htm 37.340] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA) and NR;
Multi-connectivity;
Stage 2
|| Document provides an overview of the multi-connectivity operation using E-UTRA and NR radio access technologies.
|-
| 38.300 || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2
|| This document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

[[My 3GPP 38.300 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38304.htm 38.304] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
User Equipment (UE) procedures in Idle mode and RRC Inactive state
|| Document specifies the Access Stratum (AS) part of the UE procedures in RRC_IDLE state (also called Idle mode) and RRC_INACTIVE state. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in TS 23.122.

[[My 3GPP TS 38.304 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3197 38.331] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
Radio Resource Control (RRC) protocol specification
(Release 17)
|| This document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN.
|-
| [https://www.3gpp.org/DynaReport/38401.htm 38.401] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description || Document describes the overall architecture of the NG-RAN, including interfaces NG, Xn and F1 interfaces and their interaction with the radio interface.

[[My 3GPP TS 38.401 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38413.htm 38.413] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP)(Release 16) || This document specifies the radio network layer signalling protocol for the NG interface. The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document. NGAP is developed in accordance to the general principles stated in TS 38.401 and TS 38.410.
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

== 3GPP/ETSI info ==

[https://www.etsi.org/technologies/5g ETSI 5G information page]

[https://www.etsi.org/technologies/lawful-interception ETSI Lawful Interception (LI) information page]

[https://www.etsi.org/committee/1403-li ETSI Technical Committee (TC) Lawful Interception information page] and contains list of latest publications

=== [https://www.etsi.org/standards ETSI Standards] ===

==== Lawful Interception or Related Standards ====

{| class="wikitable sortable"
|-
! ETSI Standard
! Title
! Notes
|-
| ETSI TS 102 232-1 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery || This document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. This document:
* specifies the modular approach used for specifying IP based handover interfaces;
* specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
* specifies protocols for the transfer of IRI and CC across the handover interfaces;
* specifies protocol profiles for the handover interface.

[[My 102 232-1 notes]]
|-
| ETSI TS 102 232-2 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services || This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.
|-
| ETSI TS 102 232-3 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services || This document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The study includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets.

The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1.

[[My 102 232-3 notes]]
|-
| ETSI TS 102 232-4 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services ||
|-
| ETSI TS 102 232-5 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services || Document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Real Time Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IPMM services as described by the Recommendations ITU-T H.323 and H.248-1.

The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1.

The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 and ETSI TS 101 671.
|-
| ETSI TS 102 232-6 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services ||
|-
| ETSI TS 102 232-7 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services ||
|-
| ETSI TR 102 528 || Lawful Interception (LI); Interception domain Architecture for IP networks || Document describes a high level reference architecture for supporting lawful interception in network operator (NWO) and communication service providers (SvP) domain for IP networks.

The document contains:
* A reference model in the network operator (NWO) and communication service provider (SvP) domain.
* A High level description of Internal Network Functions and Interfaces.
* Application of the reference model to voice and multimedia over IP services, data layer 3 and layer 2 services.
|-
| ETSI TS 103 221 || Lawful Interception (LI); Internal Network Interfaces || Part I (X1) and Part II (X2/X3) [[My TS 103 221-2 notes]]
|-
| ETSI TS 103 643 || Techniques for assurance of digital material used in legal proceedings ||
|-
| ETSI TS 101 671 & ETSI ES 201 671 || Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic || Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service.
* Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331.
* Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
|-
| ETSI TS 103 462 || Lawful Interception (LI); Inter LEMF Handover Interface ||
|-
| style="white-space: nowrap;" | ETSI TR 102 503 || Lawful Interception (LI); ASN.1 Object Identifiers in Lawful Interception and Retained data handling Specifications ||
|-
| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data ||
|-
| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data ||
|-
| ETSI TS 101 331 || Lawful Interception (LI); Requirements of Law Enforcement Agencies || Document gives guidance for lawful interception of telecommunications in the area of co-operation by network operators, access providers, and service providers. Document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
|-
| ETSI TS 103 707 || Lawful Interception (LI); Handover for messaging services over HTTP/XML || Document specifies the handover details to deliver messaging services for LI over HTTP/XML
|-
| ETSI TS 103 120 || Lawful Interception (LI); Interface for warrant information || Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.
|-
| ETSI TS 103 280 || Lawful Interception (LI); Dictionary for common parameters || Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]
|-
| ETSI TS 103 690 || Lawful Interception (LI); eWarrant Interface || Document presents a high-level description of an interface mechanism - the eWarrant Interface - for receipt of requests for measures producing real-time or stored information by an issuing authority possessing lawful authorization to initiate such a request
|-
| || ||
|-
| || ||
|-
| || ||
|}

==== Other Standards ====

{| class="wikitable sortable"
|-
! 3GPP
! Title
! Notes
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729 23.003]
|| 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)
|| This document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system. IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator.

[[My 3GPP TS 23.003 notes]]
|-
| [https://www.3gpp.org/DynaReport/23228.htm 23.228]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 16)
|| This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. [[My 3GPP TS 23.228 Notes]]
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 16)
|| The document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1014 24.007]
| 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface signalling layer 3;
General aspects
(Release 17)
| 24.007 document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
This document also defines the principal architecture of the EPS NAS and 5GS NAS layer 3 protocol and their sublayers, including the message format applied by layer 3.

[[My 3GPP TS 24.007 Notes]]
|-
| 33.108 || UMTS; LTE; GSM; 3G Security; Handover interface for lawful interception (LI) || [[My TS 133 108 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3182 33.127] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Lawful Interception (LI) architecture and functions
|| This document specifies both the architectural and functional system requirements for Lawful Interception (LI) in 3GPP networks. The present document provides an LI architecture supporting both network layer based and service layer based Interception. National regulations determine the specific set of LI functional capabilities that are applicable to a specific 3GPP operator deployment.

[[My 33.127 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3183 33.128] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Protocol and procedures for Lawful Interception (LI);
Stage 3
|| This document specifies the protocols and procedures required to perform Lawful Interception within a 3GPP network. The present document addresses both internal interfaces used internally with a 3GPP network and external handover interfaces used to handover intercepted communications to law enforcement.

[[My 33.128 Notes]]
|}

== Standards related info ==

MCPTT ID parameter is defined in TS 23.280

[[My ATIS lawful interception standard notes]]

[[My lawful interception notes]]

== RFCs of interest ==

[https://tools.ietf.org/html/rfc3261 RFC 3261 SIP: Session Initiation Protocol]

[https://tools.ietf.org/html/rfc3455 RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)]

[https://tools.ietf.org/html/rfc7913 RFC 7913 P-Access-Network-Info ABNF Update]

[https://tools.ietf.org/html/rfc4984 RFC 4984 Report from the IAB Workshop on Routing and Addressing]

[https://tools.ietf.org/html/rfc6830 RFC 6830 The Locator/ID Separation Protocol (LISP)]

== National Requirements Resources ==

[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

== Case Examples ==

[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later.

Telecommunications info

2025-11-28T16:21:31Z

Paul: added case examples

== NNI Task Force ==

[https://www.sipforum.org/activities/nni-task-force-introduction/ NNI Task Force Introduction]

== 3GPP SA3 Security ==

[https://www.3gpp.org/specifications-groups/sa-plenary/sa3-security SA3 - Security]

== [https://www.3gpp.org/specifications/79-specification-numbering 3GPP Standards] ==

[https://www.3gpp.org/specifications/79-specification-numbering 3GPP specification numbering]

[https://www.3gpp.org/DynaReport/status-report.htm 3GPP Specification Status Report]

=== Definition and abbreviations ===

See [[My 3GPP definition notes]] for definitions

See [[My 3GPP abbreviation notes]] for abbreviations

=== EPS and NR related standards with notes ===

[[My New Radio (NR) notes]]

{| class="wikitable sortable"
|-
! Standard # !! Title !! Notes
|-
| 22.011
| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service accessibility
| The purpose of 22.011 is to describe the service access procedures as presented to the user. Definitions and procedures are provided in 22.011 for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station, or User Equipment (UE).

[[My 3GPP TS 22.011 Notes]]
|-
| [https://www.3gpp.org/DynaReport/22261.htm 22.261] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service requirements for the 5G system;
Stage 1
|| Document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278.
|-
| 23.122 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|| Document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 and 3GPP TS 38.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 and 3GPP TS 38.331.
|-
| [https://www.3gpp.org/DynaReport/23271.htm 23.271] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Functional stage 2 description of Location Services (LCS)
(Release 16)
|| Document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers. Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 and TS 23.502 in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3577 23.273] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
5G System (5GS) Location Services (LCS);
Stage 2
|| V17.5.0 document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 and TS 22.071.
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access
(Release 17)
|| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.

[[My 3GPP 23.401 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
System architecture for the 5G System (5GS);
Stage 2
|| 5G core network

[[My 3GPP 23.501 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Procedures for the 5G System (5GS);
Stage 2
| V17.5.0 document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 and for the policy and charging control framework which is described in TS 23.503.

[[My 3GPP 23.502 Notes]]
|-
| 24.229 || Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 || P-Access-Network-Info values for "cgi-3gpp", "utran-cell-id-3gpp", "i-wlan-node-id", "dsl-location", "ci-3gpp2", "ci-3gpp2-femto" and "gstn-location" are defined in section 7.2A.4
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3370 24.501] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) protocol for 5G System (5GS);
Stage 3;
|| This present document specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for:
* mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and
* session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.
The 5GS mobility management (5GMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the NG radio access network (NG-RAN) and/or non-3GPP access network. The 5GMM protocol also provides control of security for the NAS protocols.

[[My 3GPP 24.501 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3371 24.502] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Access to the 3GPP 5G Core Network (5GCN)
via Non-3GPP Access Networks (N3AN);
Stage 3
|| This document specifies non-3GPP access network discovery and selection procedures, the access authorization procedure used for accessing non-3GPP access networks. These non-3GPP access networks can be trusted non-3GPP access networks, untrusted non-3GPP access networks or wireline access networks.
|-
| 29.503 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
5G System; Unified Data Management Services;
Stage 3
|| The document specifies the stage 3 protocol and data model for the Nudm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDM.

The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 and 3GPP TS 23.502.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 and 3GPP TS 29.501.
|-
| 29.279 || Universal Mobile Telecommunications System (UMTS); LTE; Mobile IPv4 (MIPv4) based mobility protocols; Stage 3 ||
|-
| [https://www.3gpp.org/DynaReport/29571.htm 29.571] || 5G System; Common Data Types for Service Based Interfaces; Stage 3 || The document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
|-
| [https://www.3gpp.org/DynaReport/33501.htm 33.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security architecture and procedures for 5G system
|| Document specifies the security architecture, i.e., the security features and the security mechanisms for the 5G System and the 5G Core, and the security procedures performed within the 5G System including the 5G Core and the 5G New Radio.

[[My 3GPP 33.501 notes]]
|-
| [https://www.3gpp.org/DynaReport/37340.htm 37.340] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA) and NR;
Multi-connectivity;
Stage 2
|| Document provides an overview of the multi-connectivity operation using E-UTRA and NR radio access technologies.
|-
| 38.300 || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2
|| This document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

[[My 3GPP 38.300 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38304.htm 38.304] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
User Equipment (UE) procedures in Idle mode and RRC Inactive state
|| Document specifies the Access Stratum (AS) part of the UE procedures in RRC_IDLE state (also called Idle mode) and RRC_INACTIVE state. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in TS 23.122.

[[My 3GPP TS 38.304 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3197 38.331] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
Radio Resource Control (RRC) protocol specification
(Release 17)
|| This document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN.
|-
| [https://www.3gpp.org/DynaReport/38401.htm 38.401] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description || Document describes the overall architecture of the NG-RAN, including interfaces NG, Xn and F1 interfaces and their interaction with the radio interface.

[[My 3GPP TS 38.401 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38413.htm 38.413] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP)(Release 16) || This document specifies the radio network layer signalling protocol for the NG interface. The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document. NGAP is developed in accordance to the general principles stated in TS 38.401 and TS 38.410.
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

== 3GPP/ETSI info ==

[https://www.etsi.org/technologies/5g ETSI 5G information page]

[https://www.etsi.org/technologies/lawful-interception ETSI Lawful Interception (LI) information page]

[https://www.etsi.org/committee/1403-li ETSI Technical Committee (TC) Lawful Interception information page] and contains list of latest publications

=== [https://www.etsi.org/standards ETSI Standards] ===

==== Lawful Interception or Related Standards ====

{| class="wikitable sortable"
|-
! ETSI Standard
! Title
! Notes
|-
| ETSI TS 102 232-1 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery || This document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. This document:
* specifies the modular approach used for specifying IP based handover interfaces;
* specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
* specifies protocols for the transfer of IRI and CC across the handover interfaces;
* specifies protocol profiles for the handover interface.

[[My 102 232-1 notes]]
|-
| ETSI TS 102 232-2 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services || This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.
|-
| ETSI TS 102 232-3 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services || This document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The study includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets.

The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1.

[[My 102 232-3 notes]]
|-
| ETSI TS 102 232-4 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services ||
|-
| ETSI TS 102 232-5 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services || Document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Real Time Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IPMM services as described by the Recommendations ITU-T H.323 and H.248-1.

The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1.

The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 and ETSI TS 101 671.
|-
| ETSI TS 102 232-6 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services ||
|-
| ETSI TS 102 232-7 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services ||
|-
| ETSI TR 102 528 || Lawful Interception (LI); Interception domain Architecture for IP networks || Document describes a high level reference architecture for supporting lawful interception in network operator (NWO) and communication service providers (SvP) domain for IP networks.

The document contains:
* A reference model in the network operator (NWO) and communication service provider (SvP) domain.
* A High level description of Internal Network Functions and Interfaces.
* Application of the reference model to voice and multimedia over IP services, data layer 3 and layer 2 services.
|-
| ETSI TS 103 221 || Lawful Interception (LI); Internal Network Interfaces || Part I (X1) and Part II (X2/X3) [[My TS 103 221-2 notes]]
|-
| ETSI TS 103 643 || Techniques for assurance of digital material used in legal proceedings ||
|-
| ETSI TS 101 671 & ETSI ES 201 671 || Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic || Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service.
* Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331.
* Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
|-
| ETSI TS 103 462 || Lawful Interception (LI); Inter LEMF Handover Interface ||
|-
| style="white-space: nowrap;" | ETSI TR 102 503 || Lawful Interception (LI); ASN.1 Object Identifiers in Lawful Interception and Retained data handling Specifications ||
|-
| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data ||
|-
| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data ||
|-
| ETSI TS 101 331 || Lawful Interception (LI); Requirements of Law Enforcement Agencies || Document gives guidance for lawful interception of telecommunications in the area of co-operation by network operators, access providers, and service providers. Document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
|-
| ETSI TS 103 707 || Lawful Interception (LI); Handover for messaging services over HTTP/XML || Document specifies the handover details to deliver messaging services for LI over HTTP/XML
|-
| ETSI TS 103 120 || Lawful Interception (LI); Interface for warrant information || Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.
|-
| ETSI TS 103 280 || Lawful Interception (LI); Dictionary for common parameters || Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]
|-
| ETSI TS 103 690 || Lawful Interception (LI); eWarrant Interface || Document presents a high-level description of an interface mechanism - the eWarrant Interface - for receipt of requests for measures producing real-time or stored information by an issuing authority possessing lawful authorization to initiate such a request
|-
| || ||
|-
| || ||
|-
| || ||
|}

==== Other Standards ====

{| class="wikitable sortable"
|-
! 3GPP
! Title
! Notes
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729 23.003]
|| 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)
|| This document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system. IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator.

[[My 3GPP TS 23.003 notes]]
|-
| [https://www.3gpp.org/DynaReport/23228.htm 23.228]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 16)
|| This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. [[My 3GPP TS 23.228 Notes]]
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 16)
|| The document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1014 24.007]
| 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface signalling layer 3;
General aspects
(Release 17)
| 24.007 document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
This document also defines the principal architecture of the EPS NAS and 5GS NAS layer 3 protocol and their sublayers, including the message format applied by layer 3.

[[My 3GPP TS 24.007 Notes]]
|-
| 33.108 || UMTS; LTE; GSM; 3G Security; Handover interface for lawful interception (LI) || [[My TS 133 108 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3182 33.127] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Lawful Interception (LI) architecture and functions
|| This document specifies both the architectural and functional system requirements for Lawful Interception (LI) in 3GPP networks. The present document provides an LI architecture supporting both network layer based and service layer based Interception. National regulations determine the specific set of LI functional capabilities that are applicable to a specific 3GPP operator deployment.

[[My 33.127 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3183 33.128] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Protocol and procedures for Lawful Interception (LI);
Stage 3
|| This document specifies the protocols and procedures required to perform Lawful Interception within a 3GPP network. The present document addresses both internal interfaces used internally with a 3GPP network and external handover interfaces used to handover intercepted communications to law enforcement.

[[My 33.128 Notes]]
|}

== Standards related info ==

MCPTT ID parameter is defined in TS 23.280

[[My ATIS lawful interception standard notes]]

[[My lawful interception notes]]

== RFCs of interest ==

[https://tools.ietf.org/html/rfc3261 RFC 3261 SIP: Session Initiation Protocol]

[https://tools.ietf.org/html/rfc3455 RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)]

[https://tools.ietf.org/html/rfc7913 RFC 7913 P-Access-Network-Info ABNF Update]

[https://tools.ietf.org/html/rfc4984 RFC 4984 Report from the IAB Workshop on Routing and Addressing]

[https://tools.ietf.org/html/rfc6830 RFC 6830 The Locator/ID Separation Protocol (LISP)]

== National Requirements Resources ==

[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

== Case Examples ==

[https://www.youtube.com/watch?v=DHS4nhdkfbM A Phone Helped Parents Find Their Daughter's Body] Verizon Wireless had authorization to release records, but didn't share the data until four days later. Why?

My TR TKÜV Notes

2025-08-07T03:26:27Z

Paul: initial page creation

My Notes from edition 8.3 English (draft)

== Scope ==

The Technical Guideline (TR TKÜV) sets out technical specifications implementing legal measures for telecommunications surveillance, cooperation in technical identification measures for mobile terminals and information provision.

See spec for additional details.

== Content ==

Edition 8.3 differs from 8.2 by including further developments in ETSI TS 103 120 for the transmission of orders from authorized bodies of obligated telecommunication companies.

Edition 8.3 includes four Parts (A, B, C, and X):
* '''Part A. Technical implementation of legal measures for telecommunications surveillance''' This section describes the technical details of the surveillance equipment and the required technical characteristics of recording lines.
* '''Part B. Technical implementation of legal measures for information provision''' This section contains the technical details of the facilities for retrieving user, inventory and traffic data and in particular the optional procedure for transmitting the copy of the order to implement measures.
* '''Part C. Technical implementation of the legal obligation to cooperate in technical identification measures for mobile terminals''' This section contains the technical provisions enabling use of the technical means of the authorised agencies in public mobile networks to find certain information from mobile terminals and provide automated information on the identifiers temporarily and permanently assigned in a mobile network.
* '''Part X. Information Annex''' This informative section contains the planned further changes to the TR TKÜV which are to form the basis for a discussion of the next edition, supplementary information relating to Parts A and B of this edition, regulations for the registration and certification authority TKÜV-CA and a history of the previous editions of the TR TKÜV.

== Definitions ==

'''§ 3.1 Telecommunications content (content of communication, CC)''' The part of telecommunication under surveillance that contains the content of communication exchanged between users or their terminals (such as voice, email or IP traffic).

'''§ 3.2 Intercept-related information (IRI)''' Data to be provided as per § 7 TKÜV on the further circumstances of the telecommunication under surveillance. These data must be provided even if the telecommunications content is not successfully transmitted (e.g. user busy).

'''§ 3.3 Surveillance copy''' According to Section 2(14) TKÜV, the duplicate of the telecommunication under surveillance to be transmitted (CC and IRI).

'''§ 3.4 Internet gateway''' The transmission route that serves for direct user-specific access to the Internet as per Section 2(12) in conjunction with Section 3(2) (first sentence) (3) TKÜV.

'''§ 3.5 OP telecommunications system -(OPT-S)''' As a general rule, the Obligated Party’s Telecommunications System is the origin of the telecommunication on the line under surveillance (LuS) for outgoing traffic and its destination for incoming traffic (such as subscriber exchange, UMS, email server).

'''§ 3.6 Transmission network''' The network used to transmit the surveillance copy from the OPTS to the authorised agency (CC and/or IRI).

'''§ 3.7 Concept''' Documents as per Section 170(1)(4)(a) TKG (TODO: get reference and add it here)

== Abbreviations ==

{| class="wikitable sortable"
|+ Abbreviations
|-
! Abbreviation !! Meaning
|-
| 3GPP || [https://www.3gpp.org/ Third Generation Partnership Program]
|-
| 5G || 5th Generation Mobile Network (note: add 3GPP-based)
|-
| ACL || Access Control List
|-
| ASCII || American National Standard Code for Information Exchange
|-
| ASN.1 || Abstract Syntax Notation One
|-
| BC || Bearer Capability
|-
| bS || Authorized Agency
|-
| BSI || Federal Office for Information Security
|-
| BSIG || Act on Federal Office for Information Security
|-
| BSS || Base Station Subsystem
|-
| CA || Certificate Authority
|-
| CC || Content of Communications (Nutzinformationen)
|-
| CIN || Communication Identity Number (Zuordnungsnummer)
|-
| DCF77 || Time signal transmitter ‘Mainflingen’ on the frequency 77.5 kHz, via which the official time generated by the National Metrology Institute of Germany [PTB] is broadcast
|-
| DF || Delivery Function (zum Beispiel DF2, DF3)
|-
| DTD || Document Type Definition
|-
| ESB || Specification of the electronic interface for information and connection data requests and telecommunications surveillance and tracking
|-
| ETSI || European Telecommunications Standards Institute
|-
| FTP || File Transfer Protocol
|-
| GLI || Global Line Identifier
|-
| GLIC || GPRS Lawful Interception Correlation
|-
| GPRS || General Packet Radio Service
|-
| GSM || General System for Mobile Communications
|-
| GUTI || Globally Unique Temporary UE Identity
|-
| HI || Handover Interface
|-
| HLC || High Layer Compatibility
|-
| HTTP || Hypertext Transfer Protocol
|-
| HTTP/TLS || HTTP via TLS (secure HTTP)
|-
| IMAP || Internet Message Access Protocol
|-
| IMEI || International Mobile Equipment Identity
|-
| IMPI || IP Multimedia Private Identity
|-
| IMPU || IP Multimedia Public Identity
|-
| IMS || IP Multimedia Subsystem
|-
| IMSI || Internatinal Mobile Subscriber Identity
|-
| IN || Intelligent Network
|-
| IP || Internet Protocol
|-
| IRI || Intercept-Related Information (event data)
|-
| ITU-T || International Telecommunication Union - Telecommunication Standardization Sector
|-
| JVEG || Judical Renumeration & Compensation Act
|-
| LD || Lawful Disclosure
|-
| LDAP || Lightweight Directory Access Protocol
|-
| LDID || Lawful Disclosure IDentifier
|-
| LEA || Law Enforcement Agency
|-
| LI || Lawful Interception
|-
| LI_HIQR || Lawful Interception Handover Interface Query Response
|-
| LIID || Lawful Interception IDentifier
|-
| LTE || Long Term Evolution
|-
| MMS || Multimedia Messaging Service
|-
| MSC || Mobile Switching Center
|-
| MSISDN || Mobile Subscriber ISDN Number
|-
| NCI || NR Cell Identity
|-
| N9 || Connection between UPF and UPF according to 3GPP TS 23.501
|-
| N32 || Connection between two SEPPs
|-
| NEID || Network Element Identifier
|-
| NI-ICS || Number-independent Interpersonal Communication Services
|-
| NR || New Radio
|-
| OID || Object Identifier
|-
| PEI || Permanent Equipment Identifier
|-
| PKI || Public Key Infrastructure
|-
| POP3 || Post Office Protocol 3
|-
| PTB || National Metrology Institute of Germany
|-
| ROSE || Remote Operations Service Element
|-
| RTCP || Real-time Transport Control Protocol
|-
| RTP || Real-time Transport Protocol
|-
| SEPP || Security Edge Protection Proxy
|-
| SIP || Session Initiation Protocol
|-
| SMS || Short Message Service
|-
| SMTP || Simple Mail Transfer Protocol
|-
| SUCI || Subscription Concealed Identifier
|-
| SUPI || Subscription Permanent Identifier
|-
| TCP || Transport Control Protocol
|-
| OPTS || Obligated Party’s Telecommunication System [TKA-V]
|-
| TKG || Telecommunications Act
|-
| TKÜV || Telecommunications Surveillance Ordinance
|-
| TKÜV-CA || Registration and certification authority of the Federal Network Agency
|-
| TLS || Transport Layer Security
|-
| TDDDG || Telecommunications Digital Services Data Protection Act
|-
| UMS || Unified Messaging System
|-
| UMTS || Universal Mobile Telecommunications System
|-
| UPF || User Plane Function
|-
| URI || Uniform Resource Identifier
|-
| URL || Uniform Resource Locator
|-
| UTC || Coordinated Universal Time (literally Universel Temps Coordonné) (UTC)
|-
| UTF-8 || 8-bit Unicode Transformation Format (RFC 3629, ISO 10646)
|-
| UTM || Universal Transversal Mercator Projection (coordinates)
|-
| VoIP || Voice over IP
|-
| VoLTE || Voice over LTE
|-
| VoNR || Voice over New Radio (neue Funkschnittstelle bei 5G)
|-
| VMS || Voice Mail System
|-
| VPN || Virtual Private Network
|-
| WGS || World Geographic System
|-
| XML || Extensible Markup Language
|-
| züA || Line or identifier under surveillance [zu überwachender Anschluss]
|}

== Part A ==

== Part B ==

== Part C ==

== Part X ==

[[My German LI notes|To My My German LI notes]]

My German LI notes

2025-08-07T02:26:52Z

Paul:

[https://www.gesetze-im-internet.de/tkg_2021/__170.html Section 170 of Telecommunications Act (TKG)]

[https://www.gesetze-im-internet.de/tk_v_2005/BJNR313600005.html Ordinance on the technical and organizational implementation of measures for the surveillance of telecommunications (Telekommunikations-Übersicherungsverordnung - TKÜV)]

[https://www.bundesnetzagentur.de/DE/Fachthemen/Telekommunikation/OeffentlicheSicherheit/Ueberwachung_Auskunftsert/TR_TKUEV/node.html TR TKÜV] download

[[My TR TKÜV Notes]]

<center>[[Telecommunications info | To Telecommunications info]]</center>

Telecommunications info

2025-08-06T19:17:45Z

Paul: /* National Requirements Resources */

== NNI Task Force ==

[https://www.sipforum.org/activities/nni-task-force-introduction/ NNI Task Force Introduction]

== 3GPP SA3 Security ==

[https://www.3gpp.org/specifications-groups/sa-plenary/sa3-security SA3 - Security]

== [https://www.3gpp.org/specifications/79-specification-numbering 3GPP Standards] ==

[https://www.3gpp.org/specifications/79-specification-numbering 3GPP specification numbering]

[https://www.3gpp.org/DynaReport/status-report.htm 3GPP Specification Status Report]

=== Definition and abbreviations ===

See [[My 3GPP definition notes]] for definitions

See [[My 3GPP abbreviation notes]] for abbreviations

=== EPS and NR related standards with notes ===

[[My New Radio (NR) notes]]

{| class="wikitable sortable"
|-
! Standard # !! Title !! Notes
|-
| 22.011
| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service accessibility
| The purpose of 22.011 is to describe the service access procedures as presented to the user. Definitions and procedures are provided in 22.011 for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station, or User Equipment (UE).

[[My 3GPP TS 22.011 Notes]]
|-
| [https://www.3gpp.org/DynaReport/22261.htm 22.261] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service requirements for the 5G system;
Stage 1
|| Document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278.
|-
| 23.122 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|| Document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 and 3GPP TS 38.304. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 and 3GPP TS 38.331.
|-
| [https://www.3gpp.org/DynaReport/23271.htm 23.271] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Functional stage 2 description of Location Services (LCS)
(Release 16)
|| Document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers. Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 and TS 23.502 in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3577 23.273] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
5G System (5GS) Location Services (LCS);
Stage 2
|| V17.5.0 document specifies the stage 2 of the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs), NF services and procedures, to meet the service requirements defined in TS 22.261 and TS 22.071.
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access
(Release 17)
|| This document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.

[[My 3GPP 23.401 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144 23.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
System architecture for the 5G System (5GS);
Stage 2
|| 5G core network

[[My 3GPP 23.501 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145 23.502] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Procedures for the 5G System (5GS);
Stage 2
| V17.5.0 document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 and for the policy and charging control framework which is described in TS 23.503.

[[My 3GPP 23.502 Notes]]
|-
| 24.229 || Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 || P-Access-Network-Info values for "cgi-3gpp", "utran-cell-id-3gpp", "i-wlan-node-id", "dsl-location", "ci-3gpp2", "ci-3gpp2-femto" and "gstn-location" are defined in section 7.2A.4
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3370 24.501] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Non-Access-Stratum (NAS) protocol for 5G System (5GS);
Stage 3;
|| This present document specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for:
* mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and
* session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.
The 5GS mobility management (5GMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the NG radio access network (NG-RAN) and/or non-3GPP access network. The 5GMM protocol also provides control of security for the NAS protocols.

[[My 3GPP 24.501 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3371 24.502] || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Access to the 3GPP 5G Core Network (5GCN)
via Non-3GPP Access Networks (N3AN);
Stage 3
|| This document specifies non-3GPP access network discovery and selection procedures, the access authorization procedure used for accessing non-3GPP access networks. These non-3GPP access networks can be trusted non-3GPP access networks, untrusted non-3GPP access networks or wireline access networks.
|-
| 29.503 || 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
5G System; Unified Data Management Services;
Stage 3
|| The document specifies the stage 3 protocol and data model for the Nudm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDM.

The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 and 3GPP TS 23.502.

The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 and 3GPP TS 29.501.
|-
| 29.279 || Universal Mobile Telecommunications System (UMTS); LTE; Mobile IPv4 (MIPv4) based mobility protocols; Stage 3 ||
|-
| [https://www.3gpp.org/DynaReport/29571.htm 29.571] || 5G System; Common Data Types for Service Based Interfaces; Stage 3 || The document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
|-
| [https://www.3gpp.org/DynaReport/33501.htm 33.501] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security architecture and procedures for 5G system
|| Document specifies the security architecture, i.e., the security features and the security mechanisms for the 5G System and the 5G Core, and the security procedures performed within the 5G System including the 5G Core and the 5G New Radio.

[[My 3GPP 33.501 notes]]
|-
| [https://www.3gpp.org/DynaReport/37340.htm 37.340] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA) and NR;
Multi-connectivity;
Stage 2
|| Document provides an overview of the multi-connectivity operation using E-UTRA and NR radio access technologies.
|-
| 38.300 || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2
|| This document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

[[My 3GPP 38.300 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38304.htm 38.304] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
User Equipment (UE) procedures in Idle mode and RRC Inactive state
|| Document specifies the Access Stratum (AS) part of the UE procedures in RRC_IDLE state (also called Idle mode) and RRC_INACTIVE state. The non-access stratum (NAS) part of Idle mode procedures and processes is specified in TS 23.122.

[[My 3GPP TS 38.304 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3197 38.331] || 3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
Radio Resource Control (RRC) protocol specification
(Release 17)
|| This document specifies the Radio Resource Control protocol for the radio interface between UE and NG-RAN.
|-
| [https://www.3gpp.org/DynaReport/38401.htm 38.401] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description || Document describes the overall architecture of the NG-RAN, including interfaces NG, Xn and F1 interfaces and their interaction with the radio interface.

[[My 3GPP TS 38.401 Notes]]
|-
| [https://www.3gpp.org/DynaReport/38413.htm 38.413] || 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP)(Release 16) || This document specifies the radio network layer signalling protocol for the NG interface. The NG Application Protocol (NGAP) supports the functions of the NG interface by signalling procedures defined in this document. NGAP is developed in accordance to the general principles stated in TS 38.401 and TS 38.410.
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|-
| Example || Example || Example
|}

== 3GPP/ETSI info ==

[https://www.etsi.org/technologies/5g ETSI 5G information page]

[https://www.etsi.org/technologies/lawful-interception ETSI Lawful Interception (LI) information page]

[https://www.etsi.org/committee/1403-li ETSI Technical Committee (TC) Lawful Interception information page] and contains list of latest publications

=== [https://www.etsi.org/standards ETSI Standards] ===

==== Lawful Interception or Related Standards ====

{| class="wikitable sortable"
|-
! ETSI Standard
! Title
! Notes
|-
| ETSI TS 102 232-1 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery || This document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. This document:
* specifies the modular approach used for specifying IP based handover interfaces;
* specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
* specifies protocols for the transfer of IRI and CC across the handover interfaces;
* specifies protocol profiles for the handover interface.

[[My 102 232-1 notes]]
|-
| ETSI TS 102 232-2 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services || This document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include: email, unified messaging and chat applications. See 102-232-1 for stage 3.
|-
| ETSI TS 102 232-3 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services || This document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The study includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets.

The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1.

[[My 102 232-3 notes]]
|-
| ETSI TS 102 232-4 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services ||
|-
| ETSI TS 102 232-5 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services || Document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Real Time Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IPMM services as described by the Recommendations ITU-T H.323 and H.248-1.

The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1.

The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 and ETSI TS 101 671.
|-
| ETSI TS 102 232-6 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services ||
|-
| ETSI TS 102 232-7 || Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services ||
|-
| ETSI TR 102 528 || Lawful Interception (LI); Interception domain Architecture for IP networks || Document describes a high level reference architecture for supporting lawful interception in network operator (NWO) and communication service providers (SvP) domain for IP networks.

The document contains:
* A reference model in the network operator (NWO) and communication service provider (SvP) domain.
* A High level description of Internal Network Functions and Interfaces.
* Application of the reference model to voice and multimedia over IP services, data layer 3 and layer 2 services.
|-
| ETSI TS 103 221 || Lawful Interception (LI); Internal Network Interfaces || Part I (X1) and Part II (X2/X3) [[My TS 103 221-2 notes]]
|-
| ETSI TS 103 643 || Techniques for assurance of digital material used in legal proceedings ||
|-
| ETSI TS 101 671 & ETSI ES 201 671 || Lawful Interception (LI); Handover interface for the lawful interception of telecommunications traffic || Document is step 3 of a three-step approach to describe a generic Handover Interface (HI) for the provision of lawful interception from a Network Operator, an Access Provider or a Service Provider (NWO/AP/SvP) to the Law Enforcement Agencies (LEAs). The provision of lawful interception is a requirement of national law, which is usually mandatory for the operation of any telecommunication service.
* Step 1 contains the requirements for lawful interception from a users (LEAs) point of view and is published in ETSI TS 101 331.
* Step 2 describes the derived network functions and the general architecture (or functional model) and is published in ETSI ES 201 158.
|-
| ETSI TS 103 462 || Lawful Interception (LI); Inter LEMF Handover Interface ||
|-
| style="white-space: nowrap;" | ETSI TR 102 503 || Lawful Interception (LI); ASN.1 Object Identifiers in Lawful Interception and Retained data handling Specifications ||
|-
| ETSI TS 102 656 || Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Retained Data ||
|-
| ETSI TS 102 657 || Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data ||
|-
| ETSI TS 101 331 || Lawful Interception (LI); Requirements of Law Enforcement Agencies || Document gives guidance for lawful interception of telecommunications in the area of co-operation by network operators, access providers, and service providers. Document describes the requirements from a Law Enforcement Agency's (LEA's) point of view.
|-
| ETSI TS 103 707 || Lawful Interception (LI); Handover for messaging services over HTTP/XML || Document specifies the handover details to deliver messaging services for LI over HTTP/XML
|-
| ETSI TS 103 120 || Lawful Interception (LI); Interface for warrant information || Document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception.
|-
| ETSI TS 103 280 || Lawful Interception (LI); Dictionary for common parameters || Document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. [[My ETSI TS 103 280 notes]]
|-
| ETSI TS 103 690 || Lawful Interception (LI); eWarrant Interface || Document presents a high-level description of an interface mechanism - the eWarrant Interface - for receipt of requests for measures producing real-time or stored information by an issuing authority possessing lawful authorization to initiate such a request
|-
| || ||
|-
| || ||
|-
| || ||
|}

==== Other Standards ====

{| class="wikitable sortable"
|-
! 3GPP
! Title
! Notes
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729 23.003]
|| 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)
|| This document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system. IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator.

[[My 3GPP TS 23.003 notes]]
|-
| [https://www.3gpp.org/DynaReport/23228.htm 23.228]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 16)
|| This document defines the stage-2 service description for the IP Multimedia Core Network Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. [[My 3GPP TS 23.228 Notes]]
|-
| [https://www.3gpp.org/DynaReport/23401.htm 23.401]
|| 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 16)
|| The document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1014 24.007]
| 3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface signalling layer 3;
General aspects
(Release 17)
| 24.007 document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
This document also defines the principal architecture of the EPS NAS and 5GS NAS layer 3 protocol and their sublayers, including the message format applied by layer 3.

[[My 3GPP TS 24.007 Notes]]
|-
| 33.108 || UMTS; LTE; GSM; 3G Security; Handover interface for lawful interception (LI) || [[My TS 133 108 notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3182 33.127] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Lawful Interception (LI) architecture and functions
|| This document specifies both the architectural and functional system requirements for Lawful Interception (LI) in 3GPP networks. The present document provides an LI architecture supporting both network layer based and service layer based Interception. National regulations determine the specific set of LI functional capabilities that are applicable to a specific 3GPP operator deployment.

[[My 33.127 Notes]]
|-
| [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3183 33.128] || 3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Security;
Protocol and procedures for Lawful Interception (LI);
Stage 3
|| This document specifies the protocols and procedures required to perform Lawful Interception within a 3GPP network. The present document addresses both internal interfaces used internally with a 3GPP network and external handover interfaces used to handover intercepted communications to law enforcement.

[[My 33.128 Notes]]
|}

== Standards related info ==

MCPTT ID parameter is defined in TS 23.280

[[My ATIS lawful interception standard notes]]

[[My lawful interception notes]]

== RFCs of interest ==

[https://tools.ietf.org/html/rfc3261 RFC 3261 SIP: Session Initiation Protocol]

[https://tools.ietf.org/html/rfc3455 RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)]

[https://tools.ietf.org/html/rfc7913 RFC 7913 P-Access-Network-Info ABNF Update]

[https://tools.ietf.org/html/rfc4984 RFC 4984 Report from the IAB Workshop on Routing and Addressing]

[https://tools.ietf.org/html/rfc6830 RFC 6830 The Locator/ID Separation Protocol (LISP)]

== National Requirements Resources ==

[https://www.bundesnetzagentur.de/EN/Areas/Telecommunications/ServicerProviderObligation/PublicSafety/Intercepts/start.html German ], see TR TKÜV. See [[My German LI notes]]

My lawful interception notes

2025-08-06T19:15:41Z

Paul: /* ADMF/MDF Manufacturers */

== ADMF/MDF Manufacturers ==

Here are some:
* Allied Associates International
* Aqsacom
* Cognyte
* EVE
* [https://g2klabs.com/ G2K]
* Matison
* SS8
* Utimaco
* BAE

== LEMF Manufacturers ==

Here are some:

* Cognyte
* [https://www.lawfulinterception.com/ EVE]
* [https://gladiator-forensics.com/ Gladiator Forensics]
* [https://www.jsitelecom.com/ JSI]
* [https://www.penlink.com/ PenLink]
* [https://www.sytechcorp.com/ SyTech]

== LI Testing ==

Here are some:

* [https://segron.com/ Segron]

== ETSI Handover (HI) notes ==

[[My ETSI HI via IP based network notes]]

== 5G notes ==

[[My 5G lawful interception notes]]

== 4G notes ==

[[My 4G lawful interception notes]]

== 33 106 ==
Source: 3GPP TS 33.106 V16.0.0 (2020-07)

5.1.2 General principles

...<pre>For interception, there needs to be a means of identifying the target, correspondent and initiator and related parties of any targeted communication. A means shall exist for the operator to intercept communications based on long term or permanent identifiers associated with a target service or equipment, as identified by the LEA. To achieve interception, the operator may need to translate these into further associated identifiers, in order to identify the data to be intercepted. Target identities used for interception for each domain and service are target service and equipment associated with target use or any derived IDs from such elements that are to be defined in TS 33.107 [9] and TS 33.108 [10]. Examples of these identities are IMSI, MSISDN, NAI, Tel URI, SIP URI, for the target service and IMEI, MAC for the equipment.</pre>
...<pre>National regulations may require that an operator is able to intercept any communication passing through its network based on any visible identity not connected to the operator network. It shall be based on a match between this target identity and identity type (e.g. IMPU) with the detected party fields. This identity is referred as a Non-Local Identity.</pre>

== RFCs ==

[https://tools.ietf.org/html/rfc3924 Cisco Architecture for Lawful Intercept in IP Networks]

[https://tools.ietf.org/html/rfc7348 RFC 7348: Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks]

[https://www.rfc-editor.org/rfc/rfc5503.html#page-21 RFC 5503 PacketCable Distributed Call Signaling Architecture] contains P-DCS-LAES, PacketCable-Distributed Call Signaling-Lawfully Authorized Electronic Surveillance, extension.

<center>[[Telecommunications info|To Telecommunications info]]</center>

My Factorio Info

2025-07-18T05:24:58Z

Paul: /* Factorio Headless Setup */

My Factorio Info

2025-07-18T05:23:22Z

Paul:

My Factorio Info

2025-07-18T05:06:22Z

Paul:

== Factorio Headless Setup ==

Updated 2025/07/17

'''These steps were done with Ubuntu 22.04.5 LTS'''

Resources:
* [https://wiki.factorio.com/Multiplayer Multiplayer Factorio wiki]
* Stable [https://factorio.com/get-download/stable/headless/linux64 Factorio headless] server

Check that your version of glibc is >= 2.18 using <code>ldd --version</code>

<pre>$ ldd --version
ldd (Ubuntu GLIBC 2.35-0ubuntu3.7) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.</pre>

Output of ldd command confirms glibc version >2.18.

Switch to <code>$ cd /opt</code> directory and download latest Factorio stable headless version (2.0.60 as of this writing)

<pre>$ sudo wget https://factorio.com/get-download/stable/headless/linux64</pre>

Rename file to match version (1.1.87 in this example)
<pre>$ sudo mv linux64 factorio-headless_linux_1.1.110.tar.xz</pre>

Extract archived and zipped file
<pre>$ sudo tar -xJf factorio-headless_linux_2.0.60.tar.xz
anon@ox:/opt$ ls -l
total 55376
drwxr-xr-x 8 factorio factorio 4096 Jul 18 05:05 factorio
-rw-r--r-- 1 root root 56693436 Jul 10 10:05 factorio-headless_linux_2.0.60.tar.xz</pre>

Remove file (save space, you can always download the file again, if needed) using <code>sudo rm <filename.tar.xz></code>

Add a new user to run factorio and assign ownership of <code>/opt/factorio</code> directory to same user
<pre>$ sudo useradd factorio
$ sudo chown -R factorio:factorio /opt/factorio/</pre>

Verify permissions show factorio for both user and group with <code>ls -ld /opt/factorio</code>
<pre>$ ls -ld /opt/factorio/
drwxr-xr-x 4 factorio factorio 4096 May 4 17:07 /opt/factorio/</pre>

Test Factorio binary by switching to factorio user then start server
<pre>robot01@apu01:/opt$ sudo su - factorio
No directory, logging in with HOME=/
$</pre>

As factorio user create <code>/opt/factorio/</code> saves directory. I used saves directory.
<pre>$ mkdir /opt/factorio/saves</pre>

Start server and look for something like "File /savename does not exist."
<pre>$ /opt/factorio/bin/x64/factorio --start-server savename
0.000 2024-05-04 17:53:44; Factorio 1.1.107 (build 62234, linux64, headless)
0.020 Operating system: Linux (Ubuntu 22.04)
0.020 Program arguments: "/opt/factorio/bin/x64/factorio" "--start-server" "savename"
0.020 Config path: /opt/factorio/config/config.ini
0.020 Read data path: /opt/factorio/data
0.020 Write data path: /opt/factorio [1763296/1874134MB]
0.020 Binaries path: /opt/factorio/bin
0.024 System info: [CPU: 13th Gen Intel(R) Core(TM) i9-13900K, 32 cores, RAM: 64055 MB]
0.024 Environment: DISPLAY=<unset> WAYLAND_DISPLAY=<unset> DESKTOP_SESSION=<unset> XDG_SESSION_DESKTOP=<unset> XDG_CURRENT_DESKTOP=<unset> __GL_FSAA_MODE=<unset> __GL_LOG_MAX_ANISO=<unset> __GL_SYNC_TO_VBLANK=<unset> __GL_SORT_FBCONFIGS=<unset> __GL_YIELD=<unset>
0.024 Running in headless mode
0.046 Loading mod core 0.0.0 (data.lua)
0.062 Loading mod base 1.1.107 (data.lua)
0.152 Loading mod base 1.1.107 (data-updates.lua)
0.182 Checksum for core: 607699937
0.182 Checksum of base: 1054619811
0.277 Prototype list checksum: 3034860339
0.299 Info PlayerData.cpp:78: Local player-data.json unavailable
0.299 Info PlayerData.cpp:83: Cloud player-data.json unavailable
0.301 Factorio initialised
0.302 Info ServerSynchronizer.cpp:29: nextHeartbeatSequenceNumber(0) initialized Synchronizer nextTickClosureTick(0).
0.302 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(Ready) to(PreparedToHostGame)
0.302 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(PreparedToHostGame) to(CreatingGame)
0.304 Loading map /opt/factorio/savename
0.305 Error ServerMultiplayerManager.cpp:92: MultiplayerManager failed: "File /opt/factorio/savename does not exist."
0.305 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(CreatingGame) to(InitializationFailed)
0.305 Info CommandLineMultiplayer.cpp:219: Exit point.
0.306 Info ServerMultiplayerManager.cpp:154: Quitting multiplayer connection.
0.306 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(InitializationFailed) to(Closed)
0.321 Info UDPSocket.cpp:233: Closing socket
0.322 Goodbye</pre>

At this point you can load up saved games or create some games.

== Publish game on Factorio matching server ==

Copy /opt/factorio/data/server-settings.example.json to /opt/factorio/data/server-settings.json.

<pre>$ sudo cp /opt/factorio/data/server-settings.example.json /opt/factorio/data/server-settings.json</pre>

Edit appropriate server-settings.json values.

I used _comment_token versus password value. The appropriate value is located in %appdata%\Factorio\player-data.json under the key name "service-token". The service-token is populated after you've browsed the multiplayer servers via your Factorio game client.

My player-data.json for user "anon" on Windows was located at C:\Users\anon\AppData\Roaming\Factorio.

Make any changes to config ini
<pre>robot01@apu01:/opt/factorio$ sudo vi /opt/factorio/config/config.ini</pre>

=== Update headless server ===

download latest headless version

unzip and untar

<pre>sudo tar -xJf linux64</pre>

change permissions to your dedicated factorio user

<pre>sudo chown -R factorio:factorio factorio</pre>

launch game, example with saved game called "spoon.zip":

<pre>/opt/factorio/bin/x64/factorio --start-server /opt/factorio/saves/spoon.zip</pre>

== Updating Factorio ==

# Download the latest copy of the headless server using the steps above.
# Move and rename the headless server following the steps above.
# Assign ownership of <code>/opt/factorio</code> directory to factorio user used above.

[[Gaming]]

My Factorio Info

2025-07-18T04:41:48Z

Paul:

== Factorio Headless Setup ==

Updated 2025/07/17

'''These steps were done with Ubuntu 22.04.5 LTS'''

Resources:
* [https://wiki.factorio.com/Multiplayer Multiplayer Factorio wiki]
* Stable [https://factorio.com/get-download/stable/headless/linux64 Factorio headless] server
** I opted out of buying Space Age, the content and reviews didn't seem to match my interests. So I used <code>https://www.factorio.com/get-download/1.1.110/headless/linux64</code> for latest version base Factorio.

Check that your version of glibc is >= 2.18 using <code>ldd --version</code>

<pre>$ ldd --version
ldd (Ubuntu GLIBC 2.35-0ubuntu3.7) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.</pre>

Output of ldd command confirms glibc version >2.18.

Switch to <code>$ cd /opt</code> directory and download latest Factorio stable headless version (1.1.110 as of this writing)

<pre>$ sudo wget https://www.factorio.com/get-download/1.1.110/headless/linux64
[sudo] password for anon:
--2025-07-18 04:28:18-- https://www.factorio.com/get-download/1.1.110/headless/linux64
Resolving www.factorio.com (www.factorio.com)... 2606:4700:20::ac43:47c5, 2606:4700:20::681a:e58, 2606:4700:20::681a:f58, ...
Connecting to www.factorio.com (www.factorio.com)|2606:4700:20::ac43:47c5|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.factorio.com/releases/1.1.110_01j5dt7yvjeynsrerwqh7za3dc/factorio_headless_x64_1.1.110.tar.xz?secure=4waQAG5E3DK9ebGk11tyWg,1752820099 [following]
--2025-07-18 04:28:19-- https://dl.factorio.com/releases/1.1.110_01j5dt7yvjeynsrerwqh7za3dc/factorio_headless_x64_1.1.110.tar.xz?secure=4waQAG5E3DK9ebGk11tyWg,1752820099
Resolving dl.factorio.com (dl.factorio.com)... 2a02:6ea0:f900::3, 109.61.86.69
Connecting to dl.factorio.com (dl.factorio.com)|2a02:6ea0:f900::3|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 57187836 (55M) [application/octet-stream]
Saving to: ‘linux64’

linux64 100%[=================================================>] 54.54M 24.9MB/s in 2.2s

2025-07-18 04:28:21 (24.9 MB/s) - ‘linux64’ saved [57187836/57187836]</pre>

Rename file to match version (1.1.87 in this example)
<pre>$ sudo mv linux64 factorio-headless_linux_1.1.110.tar.xz</pre>

Extract archived and zipped file
<pre>$ sudo tar -xJf factorio-headless_linux_1.1.110.tar.xz
$ ls -l
total 55852
drwxr-xr-x 8 factorio factorio 4096 Jul 18 04:30 factorio
-rw-r--r-- 1 root root 57187836 Aug 16 2024 factorio-headless_linux_1.1.110.tar.xz</pre>

Remove file (save space, you can always download the file again, if needed) using <code>sudo rm <filename.tar.xz></code>

Add a new user to run factorio and assign ownership of <code>/opt/factorio</code> directory to same user
<pre>$ sudo useradd factorio
$ sudo chown -R factorio:factorio /opt/factorio/</pre>

Verify permissions show factorio for both user and group with <code>ls -ld /opt/factorio</code>
<pre>$ ls -ld /opt/factorio/
drwxr-xr-x 4 factorio factorio 4096 May 4 17:07 /opt/factorio/</pre>

Test Factorio binary by switching to factorio user then start server
<pre>robot01@apu01:/opt$ sudo su - factorio
No directory, logging in with HOME=/
$</pre>

As factorio user create <code>/opt/factorio/</code> saves directory. I used saves directory.
<pre>$ mkdir /opt/factorio/saves</pre>

Start server and look for something like "File /savename does not exist."
<pre>$ /opt/factorio/bin/x64/factorio --start-server savename
0.000 2024-05-04 17:53:44; Factorio 1.1.107 (build 62234, linux64, headless)
0.020 Operating system: Linux (Ubuntu 22.04)
0.020 Program arguments: "/opt/factorio/bin/x64/factorio" "--start-server" "savename"
0.020 Config path: /opt/factorio/config/config.ini
0.020 Read data path: /opt/factorio/data
0.020 Write data path: /opt/factorio [1763296/1874134MB]
0.020 Binaries path: /opt/factorio/bin
0.024 System info: [CPU: 13th Gen Intel(R) Core(TM) i9-13900K, 32 cores, RAM: 64055 MB]
0.024 Environment: DISPLAY=<unset> WAYLAND_DISPLAY=<unset> DESKTOP_SESSION=<unset> XDG_SESSION_DESKTOP=<unset> XDG_CURRENT_DESKTOP=<unset> __GL_FSAA_MODE=<unset> __GL_LOG_MAX_ANISO=<unset> __GL_SYNC_TO_VBLANK=<unset> __GL_SORT_FBCONFIGS=<unset> __GL_YIELD=<unset>
0.024 Running in headless mode
0.046 Loading mod core 0.0.0 (data.lua)
0.062 Loading mod base 1.1.107 (data.lua)
0.152 Loading mod base 1.1.107 (data-updates.lua)
0.182 Checksum for core: 607699937
0.182 Checksum of base: 1054619811
0.277 Prototype list checksum: 3034860339
0.299 Info PlayerData.cpp:78: Local player-data.json unavailable
0.299 Info PlayerData.cpp:83: Cloud player-data.json unavailable
0.301 Factorio initialised
0.302 Info ServerSynchronizer.cpp:29: nextHeartbeatSequenceNumber(0) initialized Synchronizer nextTickClosureTick(0).
0.302 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(Ready) to(PreparedToHostGame)
0.302 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(PreparedToHostGame) to(CreatingGame)
0.304 Loading map /opt/factorio/savename
0.305 Error ServerMultiplayerManager.cpp:92: MultiplayerManager failed: "File /opt/factorio/savename does not exist."
0.305 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(CreatingGame) to(InitializationFailed)
0.305 Info CommandLineMultiplayer.cpp:219: Exit point.
0.306 Info ServerMultiplayerManager.cpp:154: Quitting multiplayer connection.
0.306 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(InitializationFailed) to(Closed)
0.321 Info UDPSocket.cpp:233: Closing socket
0.322 Goodbye</pre>

At this point you can load up saved games or create some games.

== Publish game on Factorio matching server ==

Copy /opt/factorio/data/server-settings.example.json to /opt/factorio/data/server-settings.json.

<pre>$ sudo cp /opt/factorio/data/server-settings.example.json /opt/factorio/data/server-settings.json</pre>

Edit appropriate server-settings.json values.

I used _comment_token versus password value. The appropriate value is located in %appdata%\Factorio\player-data.json under the key name "service-token". The service-token is populated after you've browsed the multiplayer servers via your Factorio game client.

My player-data.json for user "anon" on Windows was located at C:\Users\anon\AppData\Roaming\Factorio.

Make any changes to config ini
<pre>robot01@apu01:/opt/factorio$ sudo vi /opt/factorio/config/config.ini</pre>

=== Update headless server ===

download latest headless version

unzip and untar

<pre>sudo tar -xJf linux64</pre>

change permissions to your dedicated factorio user

<pre>sudo chown -R factorio:factorio factorio</pre>

launch game, example with saved game called "spoon.zip":

<pre>/opt/factorio/bin/x64/factorio --start-server /opt/factorio/saves/spoon.zip</pre>

== Updating Factorio ==

# Download the latest copy of the headless server using the steps above.
# Move and rename the headless server following the steps above.
# Assign ownership of <code>/opt/factorio</code> directory to factorio user used above.

[[Gaming]]

My Factorio Info

2025-07-18T04:12:19Z

Paul: added updating section

== Factorio Headless Setup ==

Updated 2025/07/17

'''These steps were done with Ubuntu 22.04.5 LTS'''

Resources:
* [https://wiki.factorio.com/Multiplayer Multiplayer Factorio wiki]
* Stable [https://factorio.com/get-download/stable/headless/linux64 Factorio headless] server

Check that your version of glibc is >= 2.18 using <code>ldd --version</code>

<pre>$ ldd --version
ldd (Ubuntu GLIBC 2.35-0ubuntu3.7) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.</pre>

Output of ldd command confirms glibc version >2.18.

Switch to <code>$ cd /opt</code> directory and download latest Factorio stable headless version (factorio-headless_linux_2.0.60.tar.xz as of this writing)

<pre>$ sudo wget https://factorio.com/get-download/stable/headless/linux64
[sudo] password for anon:
--2025-07-18 04:05:32-- https://factorio.com/get-download/stable/headless/linux64
Resolving factorio.com (factorio.com)... 2606:4700:20::ac43:47c5, 2606:4700:20::681a:f58, 2606:4700:20::681a:e58, ...
Connecting to factorio.com (factorio.com)|2606:4700:20::ac43:47c5|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://dl.factorio.com/releases/2.0.60_01jzstqsxke8ps56mn0dey7p0n/factorio-headless_linux_2.0.60.tar.xz?secure=SjqildnfMJuxr6sjrEH0Fw,1752818732 [following]
--2025-07-18 04:05:32-- https://dl.factorio.com/releases/2.0.60_01jzstqsxke8ps56mn0dey7p0n/factorio-headless_linux_2.0.60.tar.xz?secure=SjqildnfMJuxr6sjrEH0Fw,1752818732
Resolving dl.factorio.com (dl.factorio.com)... 2a02:6ea0:f900::3, 109.61.86.69
Connecting to dl.factorio.com (dl.factorio.com)|2a02:6ea0:f900::3|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 56693436 (54M) [application/octet-stream]
Saving to: ‘linux64’

linux64 100%[=================================================>] 54.07M 54.1MB/s in 1.0s

2025-07-18 04:05:33 (54.1 MB/s) - ‘linux64’ saved [56693436/56693436]</pre>

Rename file to match version (1.1.87 in this example)
<pre>$ sudo mv linux64 factorio-headless_linux_2.0.60.tar.xz</pre>

Extract archived and zipped file
<pre>$ sudo tar -xJf factorio-headless_linux_2.0.60.tar.xz
$ ls -l
total 55832
drwxr-xr-x 4 root root 4096 May 4 17:07 factorio
-rw-r--r-- 1 root root 57164752 Apr 11 13:40 factorio_headless_x64_1.1.107.tar.xz</pre>

Remove file (save space, you can always download the file again, if needed)
<pre>robot01@apu01:/opt$ sudo rm factorio-headless_linux_2.0.60.tar.xz</pre>

Add a new user to run factorio and assign ownership of <code>/opt/factorio</code> directory to same user
<pre>$ sudo useradd factorio
$ sudo chown -R factorio:factorio /opt/factorio/</pre>

Verify permissions show factorio for both user and group with <code>ls -ld /opt/factorio</code>
<pre>$ ls -ld /opt/factorio/
drwxr-xr-x 4 factorio factorio 4096 May 4 17:07 /opt/factorio/</pre>

Test Factorio binary by switching to factorio user then start server
<pre>robot01@apu01:/opt$ sudo su - factorio
No directory, logging in with HOME=/
$</pre>

As factorio user create <code>/opt/factorio/</code> saves directory. I used saves directory.
<pre>$ mkdir /opt/factorio/saves</pre>

Start server and look for something like "File /savename does not exist."
<pre>$ /opt/factorio/bin/x64/factorio --start-server savename
0.000 2024-05-04 17:53:44; Factorio 1.1.107 (build 62234, linux64, headless)
0.020 Operating system: Linux (Ubuntu 22.04)
0.020 Program arguments: "/opt/factorio/bin/x64/factorio" "--start-server" "savename"
0.020 Config path: /opt/factorio/config/config.ini
0.020 Read data path: /opt/factorio/data
0.020 Write data path: /opt/factorio [1763296/1874134MB]
0.020 Binaries path: /opt/factorio/bin
0.024 System info: [CPU: 13th Gen Intel(R) Core(TM) i9-13900K, 32 cores, RAM: 64055 MB]
0.024 Environment: DISPLAY=<unset> WAYLAND_DISPLAY=<unset> DESKTOP_SESSION=<unset> XDG_SESSION_DESKTOP=<unset> XDG_CURRENT_DESKTOP=<unset> __GL_FSAA_MODE=<unset> __GL_LOG_MAX_ANISO=<unset> __GL_SYNC_TO_VBLANK=<unset> __GL_SORT_FBCONFIGS=<unset> __GL_YIELD=<unset>
0.024 Running in headless mode
0.046 Loading mod core 0.0.0 (data.lua)
0.062 Loading mod base 1.1.107 (data.lua)
0.152 Loading mod base 1.1.107 (data-updates.lua)
0.182 Checksum for core: 607699937
0.182 Checksum of base: 1054619811
0.277 Prototype list checksum: 3034860339
0.299 Info PlayerData.cpp:78: Local player-data.json unavailable
0.299 Info PlayerData.cpp:83: Cloud player-data.json unavailable
0.301 Factorio initialised
0.302 Info ServerSynchronizer.cpp:29: nextHeartbeatSequenceNumber(0) initialized Synchronizer nextTickClosureTick(0).
0.302 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(Ready) to(PreparedToHostGame)
0.302 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(PreparedToHostGame) to(CreatingGame)
0.304 Loading map /opt/factorio/savename
0.305 Error ServerMultiplayerManager.cpp:92: MultiplayerManager failed: "File /opt/factorio/savename does not exist."
0.305 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(CreatingGame) to(InitializationFailed)
0.305 Info CommandLineMultiplayer.cpp:219: Exit point.
0.306 Info ServerMultiplayerManager.cpp:154: Quitting multiplayer connection.
0.306 Info ServerMultiplayerManager.cpp:814: updateTick(4294967295) changing state from(InitializationFailed) to(Closed)
0.321 Info UDPSocket.cpp:233: Closing socket
0.322 Goodbye</pre>

At this point you can load up saved games or create some games.

== Publish game on Factorio matching server ==

Copy /opt/factorio/data/server-settings.example.json to /opt/factorio/data/server-settings.json.

<pre>$ sudo cp /opt/factorio/data/server-settings.example.json /opt/factorio/data/server-settings.json</pre>

Edit appropriate server-settings.json values.

I used _comment_token versus password value. The appropriate value is located in %appdata%\Factorio\player-data.json under the key name "service-token". The service-token is populated after you've browsed the multiplayer servers via your Factorio game client.

My player-data.json for user "anon" on Windows was located at C:\Users\anon\AppData\Roaming\Factorio.

Make any changes to config ini
<pre>robot01@apu01:/opt/factorio$ sudo vi /opt/factorio/config/config.ini</pre>

=== Update headless server ===

download latest headless version

unzip and untar

<pre>sudo tar -xJf linux64</pre>

change permissions to your dedicated factorio user

<pre>sudo chown -R factorio:factorio factorio</pre>

launch game, example with saved game called "spoon.zip":

<pre>/opt/factorio/bin/x64/factorio --start-server /opt/factorio/saves/spoon.zip</pre>

== Updating Factorio ==

# Download the latest copy of the headless server using the steps above.
# Move and rename the headless server following the steps above.
# Assign ownership of <code>/opt/factorio</code> directory to factorio user used above.

[[Gaming]]

My Satisfactory Info

2025-07-06T20:34:49Z

Paul:

== Satisfactory dedicated server setup overview ==

These steps were created using Ubuntu 22.04.5 LTS and Satisfactory dedicated server 1.1

== Resources ==

[https://satisfactory.wiki.gg/wiki/Dedicated_servers Official Satisfactory wiki page on dedicated server]

== Install Satisfactory dedicated server files ==

To install, I used the following command with my steam user:

<code>steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous +app_update 1690800 validate +quit</code>

== Setup port forwarding & firewall ==

Configured firewall to port forward 7777 for UDP and 8888 for TCP.

No need to update my firewall rules on Ubuntu server.

== Start server ==

Follow directions on official wiki, they worked great.

== Saved Game files ==

~/.config/Epic/FactoryGame/Saved/SaveGames

and

~/.config/Epic/FactoryGame/Saved/SaveGames_backup

== Server log files ==

~/SatisfactoryDedicatedServer/FactoryGame/Saved/Logs

<center>[[Gaming|To my gaming notes]]</center>

My 102 232-1 notes

2025-06-24T23:49:18Z

Paul: added ASN.1

102 232-1 specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks.

102 232-1 document:
* specifies the modular approach used for specifying IP based handover interfaces;
* specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
* specifies protocols for the transfer of IRI and CC across the handover interfaces;
* specifies protocol profiles for the handover interface.

3GPP TS 33.128 V18.0.0 specifies to use ETSI TS 102 232-1 and ETSI TS 102 232-7 for LI_HI2 and LI_HI3 (reference Table 4.3-1)

== ASN.1 ==

<pre>LI-PS-PDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version38(38)}

DEFINITIONS IMPLICIT TAGS ::=

BEGIN

IMPORTS
-- Any of the IMPORTs may be commented out if they are not used (see clause A.3)

-- from ETSI TS 103 280 [44]
LIID
FROM Common-Parameters
{itu-t(0) identified-organization(4) etsi(0) common-parameters(3280) version251(251)}

-- previously from ETSI TS 101 671 [4]; now provided with this specification
IRI-Parameters,
IRIsContent,
Location,
Network-Element-Identifier
FROM HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version18(18)}

-- previously from ETSI TS 101 671 [4]; now provided with this specification
HI1-Operation
FROM HI1NotificationOperations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi1(0) notificationOperations(1) version7(7)}

-- from ETSI TS 102 232-2 [5]
EmailCC,
EmailIRI,
MessagingCC,
MessagingMMCC,
MessagingIRI
FROM EmailPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) email(2) version20(20)}

-- from ETSI TS 102 232-3 [6]
IPCC,
IPIRI,
IPIRIOnly,
IPIRIPacketReport
FROM IPAccessPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPAccess(3) version17(17)}

-- from ETSI TS 102 232-4 [32]
L2CC,
L2IRI,
L2IRIOnly
FROM L2AccessPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) l2Access(4) version9(9)}

-- from ETSI TS 102 232-5 [37]
IPMMCC,
IPMMIRI
FROM IPMultimediaPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPMultimedia(5) version16(16)}

-- from ETSI TS 102 232-6 [36]
PstnIsdnCC,
PstnIsdnIRI
FROM PstnIsdnPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) pstnIsdn(6) version6(6)}

-- from 3GPP TS 33.108 [9]
IRI-Parameters,
UmtsIRIsContent,
CorrelationValues,
Location
FROM UmtsHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi2(1)}
-- The relevant module (including the 3GPP release and version number) needs
-- to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
IRI-Parameters,
UmtsCS-IRIsContent
FROM UmtsCS-HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi2CS(3)}
-- The relevant module (including the 3GPP release and version number) needs
-- to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
IRI-Parameters,
EpsIRIsContent,
EPSLocation
FROM EpsHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi2eps(8)}
-- The relevant module (including the 3GPP release and version number) needs
-- to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
IRI-Parameters,
ConfIRIsContent
FROM CONFHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi2conf(10)}
-- The relevant module (including the 3GPP release and version number) needs
-- to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
IRI-Parameters,
ProSeIRIsContent
FROM ProSeHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi2prose (15)}
-- The relevant module (including the 3GPP release and version number) needs
-- to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
IRI-Parameters,
GcseIRIsContent
FROM GCSEHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi2gcse(13)}
-- The relevant module (including the 3GPP release and version number) needs
-- to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
CC-PDU
FROM Umts-HI3-PS
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3(2)}
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
CC-PDU
FROM Eps-HI3-PS
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3eps(9)}
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
Conf-CC-PDU
FROM CONF-HI3-IMS
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3conf(11)}
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
Voip-CC-PDU
FROM VoIP-HI3-IMS
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3voip(12)}
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
Gcse-CC-PDU
FROM GCSE-HI3
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3gcse(14)}
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.

-- from 3GPP TS 33.108 [9]
ThreeGPP-HI1-Operation
FROM ThreeGPP-HI1NotificationOperations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi1(0) notificationOperations(1)}
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.
-- TS 101 671 HI1 and 3GPP HI1 are related to the same functionality but are
-- corresponding to different implementations and exclusive usage each other.
-- The implementation depends of national regulations or LEA/CSP negotiations.
-- 3GPP HI1 may be used with other services/networks than 3GPP's one.

-- from 3GPP TS 33.108 [9]
CSvoice-CC-PDU
FROM CSvoice-HI3-IP
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) hi3CSvoice(18)}
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.
-- The implementation of the CS domain delivery in IP have to be based on 3GPP TS 33.108 [9].

-- from ETSI TS 101 909-20-1 [33]
TARGETACTIVITYMONITOR-1,
TTRAFFIC,
CTTRAFFIC
FROM TS101909201
{itu-t(0) identified-organization(4) etsi(0) ts101909(1909) part20(20) subpart1(1) interceptVersion(0)}

-- from ETSI TS 101 909-20-2 [34]
TARGETACTIVITYMONITOR,
TTRAFFIC,
CTTRAFFIC
FROM TS101909202
{itu-t(0) identified-organization(4) etsi(0) ts101909(1909) part20(20) subpart2(2) interceptVersion(0)}

-- from ETSI TS 103 462 [45]
ILHIPayload
FROM ILHIPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) informationHandover(4) ilhi(0) ilhiPdu(0) version2(2)}
-- This import is only used for the handover between LEMFs.

-- from 3GPP TS 33.128 [46]
LINotificationPayload,
IRIPayload,
CCPayload,
UserLocation
FROM TS33128Payloads
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) threeGPP(4) ts33128(19)};
-- The relevant module (including the 3GPP release and version number)
-- needs to be chosen when compiling the application.

-- end of IMPORTS

-- =============================
-- Object Identifier Definitions
-- =============================

lawfulInterceptDomainId OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2)}

li-psDomainId OBJECT IDENTIFIER ::= {lawfulInterceptDomainId li-ps(5) genHeader(1) version38(38)}

-- ====================
-- Top-level definition
-- ====================

PS-PDU ::= SEQUENCE
{
pSHeader [1] PSHeader,
payload [2] Payload
}

PSHeader ::= SEQUENCE
{
li-psDomainId [0] OBJECT IDENTIFIER,
lawfulInterceptionIdentifier [1] LawfulInterceptionIdentifier,
-- As of ASN.1 version 26 this parameter is included from ETSI TS 103 280 [44]
authorizationCountryCode [2] PrintableString (SIZE (2)) OPTIONAL,
-- see clause 5.2.3
communicationIdentifier [3] CommunicationIdentifier,
sequenceNumber [4] INTEGER (0..4294967295),
timeStamp [5] GeneralizedTime OPTIONAL,
-- see clause 5.2.6
...,
interceptionPointID [6] PrintableString (SIZE (1..8)) OPTIONAL,
-- see clause 5.2.11
microSecondTimeStamp [7] MicroSecondTimeStamp OPTIONAL,
timeStampQualifier [8] TimeStampQualifier OPTIONAL,
extendedInterceptionPointID [9] OCTET STRING (SIZE (1..65535)) OPTIONAL,
-- see clause 5.2.13
networkFunctionIdentifier [10] OCTET STRING (SIZE (1..65535)) OPTIONAL
-- see clause 5.2.14
}

Payload ::= CHOICE
{
iRIPayloadSequence [0] SEQUENCE OF IRIPayload,
cCPayloadSequence [1] SEQUENCE OF CCPayload,
-- Clause 6.2.3 explains how to include more than one payload in the same PDU
tRIPayload [2] TRIPayload,
...,
hI1-Operation [3] HI1NotificationOperations.HI1-Operation,
encryptionContainer [4] EncryptionContainer,
threeGPP-HI1-Operation [5] ThreeGPP-HI1NotificationOperations.ThreeGPP-HI1-Operation,
-- This structure may be functionally redundant with hI1-Operation previously from ETSI TS 101 671 [4]
iLHIPayload [6] SEQUENCE OF ILHIPDU.ILHIPayload,
-- For typical use cases see ETSI TS 103 462 [45]
hI4Payload [7] SEQUENCE OF HI4Payload
}

TimeStampQualifier ::= ENUMERATED
{
unknown(0),
timeOfInterception(1),
timeOfMediation(2),
...,
timeOfAggregation(3)
}

HI4Payload ::= CHOICE
{
threeGPP-LI-Notification [1] TS33128Payloads.LINotificationPayload,
...
}

-- ====================================
-- Items contained within the PS-Header
-- ====================================

CommunicationIdentifier ::= SEQUENCE
{
networkIdentifier [0] NetworkIdentifier,
communicationIdentityNumber [1] INTEGER (0..4294967295) OPTIONAL,
-- in case of transport of HI1 messages not required
-- Mandatory for CC and IRI, with certain exceptions (see clause 5.2.4)
deliveryCountryCode [2] PrintableString (SIZE (2)) OPTIONAL,
-- see clause 5.2.4
...,
cINExtension [3] UmtsHI2Operations.CorrelationValues OPTIONAL
-- To be used when a single INTEGER is not sufficient to identify
-- a particular session (see clause 5.2.4)
}

NetworkIdentifier ::= SEQUENCE
{
operatorIdentifier [0] OCTET STRING (SIZE(1..16)),
networkElementIdentifier [1] OCTET STRING (SIZE(1..16)) OPTIONAL,
...,
eTSI671NEID [2] HI2Operations.Network-Element-Identifier OPTIONAL
-- For network element identifier, use either networkElementIdentifier or eTSI671NEID
}

-- ==========================
-- Definitions for CC Payload
-- ==========================

CCPayload ::= SEQUENCE
{
payloadDirection [0] PayloadDirection OPTIONAL,
timeStamp [1] GeneralizedTime OPTIONAL,
-- For aggregated payloads (see clause 6.2.3)
cCContents [2] CCContents,
...,
microSecondTimeStamp [3] MicroSecondTimeStamp OPTIONAL,
-- For aggregated payloads (see clause 6.2.3)
timeStampQualifier [4] TimeStampQualifier OPTIONAL
}

PayloadDirection ::= ENUMERATED
{
fromTarget(0),
toTarget(1),
...,
indeterminate(2),
-- Indication that the direction was indeterminate
combined(3),
-- Indication applicable to some services that the traffic is actually a combination
-- of To and From
notapplicable(4)
-- Indication that direction of interceptable service does not make sense
}

CCContents ::= CHOICE
-- Any of these choices may be commented out if they are not being used, see clause A.3
{
-- tag [0] deprecated in version15, ETSI TS 102 232-1 V3.3.1 (2013-02)
emailCC [1] EmailPDU.EmailCC,
iPCC [2] IPAccessPDU.IPCC,
-- tag [3] not used
uMTSCC [4] OCTET STRING,
...,
-- tag [5] deprecated in version15, ETSI TS 102 232-1 V3.3.1 (2013-02)
l2CC [6] L2AccessPDU.L2CC,
tTRAFFIC-1 [7] TS101909201.TTRAFFIC,
cTTRAFFIC-1 [8] TS101909201.CTTRAFFIC,
tTRAFFIC-2 [9] TS101909202.TTRAFFIC,
cTTRAFFIC-2 [10] TS101909202.CTTRAFFIC,
pstnIsdnCC [11] PstnIsdnPDU.PstnIsdnCC,
iPMMCC [12] IPMultimediaPDU.IPMMCC,
-- tag [13] deprecated in version32, ETSI TS 102 232-1 V3.24.1 (2021-07)
messagingCC [14] EmailPDU.MessagingCC,
ePSCC [15] OCTET STRING,
uMTSCC-CC-PDU [16] Umts-HI3-PS.CC-PDU,
ePSCC-CC-PDU [17] Eps-HI3-PS.CC-PDU,
messagingMMCC [18] EmailPDU.MessagingMMCC,
confCC-CC-PDU [19] CONF-HI3-IMS.Conf-CC-PDU,
voipCC-CC-PDU [20] VoIP-HI3-IMS.Voip-CC-PDU,
gcseCC-CC-PDU [21] GCSE-HI3.Gcse-CC-PDU,
cSvoice-CC-PDU [22] CSvoice-HI3-IP.CSvoice-CC-PDU,
threeGPP33128DefinedCC [23] OCTET STRING (CONTAINING TS33128Payloads.CCPayload)
}

MicroSecondTimeStamp ::= SEQUENCE
{
seconds [0] INTEGER (0..18446744073709551615),
-- number of seconds since 1970-1-1 00:00Z also known as unix time epoch
microSeconds [1] INTEGER (0..999999),
...
}

-- ===========================
-- Definitions for IRI Payload
-- ===========================

IRIPayload ::= SEQUENCE
{
iRIType [0] IRIType OPTIONAL,
-- See clause 5.2.10
timeStamp [1] GeneralizedTime OPTIONAL,
-- For aggregated payloads (see clause 6.2.3)
iRIContents [2] IRIContents,
...,
microSecondTimeStamp [3] MicroSecondTimeStamp OPTIONAL,
-- For aggregated payloads (see clause 6.2.3)
timeStampQualifier [4] TimeStampQualifier OPTIONAL,
sessionDirection [5] PayloadDirection OPTIONAL,
-- If the sessionDirection field is to be used for a given service then
-- the exact meaning and use of the field will be described in the
-- relevant service-specific details
payloadDirection [6] PayloadDirection OPTIONAL
-- If the payloadDirection field is to be used for a given service then
-- the exact meaning and use of the field will be described in the
-- relevant service-specific details
}

IRIType ::= ENUMERATED
{
iRI-Begin(1),
iRI-End(2),
iRI-Continue(3),
iRI-Report(4)
}

IRIContents ::= CHOICE
-- Any of these choices may be commented out if they are not being used (see clause A.3)
{
-- tag [0] deprecated in version15, ETSI TS 102 232-1 V3.3.1 (2013-02)
emailIRI [1] EmailPDU.EmailIRI,
iPIRI [2] IPAccessPDU.IPIRI,
iPIRIOnly [3] IPAccessPDU.IPIRIOnly,
uMTSIRI [4] UMTSIRI,
eTSI671IRI [5] ETSI671IRI,
...,
l2IRI [6] L2AccessPDU.L2IRI,
l2IRIOnly [7] L2AccessPDU.L2IRIOnly,
tARGETACTIVITYMONITOR-1 [8] TS101909201.TARGETACTIVITYMONITOR-1,
tARGETACTIVITYMONITOR-2 [9] TS101909202.TARGETACTIVITYMONITOR,
pstnIsdnIRI [10] PstnIsdnPDU.PstnIsdnIRI,
iPMMIRI [11] IPMultimediaPDU.IPMMIRI,
-- tag [12] deprecated in version32, ETSI TS 102 232-1 V3.24.1 (2021-07)
-- tag [13] deprecated in version32, ETSI TS 102 232-1 V3.24.1 (2021-07)
messagingIRI [14] EmailPDU.MessagingIRI,
ePSIRI [15] EPSIRI,
confIRI [16] ConfIRI,
proseIRI [17] ProSeIRI,
gcseIRI [18] GcseIRI,
threeGPP33128DefinedIRI [19] OCTET STRING (CONTAINING TS33128Payloads.IRIPayload),
iPIRIPacketReport [20] IPAccessPDU.IPIRIPacketReport
}

UMTSIRI ::= CHOICE
-- This structure may be commented out if not used
{
iRI-Parameters [0] UmtsHI2Operations.IRI-Parameters,
umtsIRIsContent [1] UmtsHI2Operations.UmtsIRIsContent,
...,
iRI-CS-Parameters [2] UmtsCS-HI2Operations.IRI-Parameters,
umtsCS-IRIsContent [3] UmtsCS-HI2Operations.UmtsCS-IRIsContent
}

ETSI671IRI ::= CHOICE
-- This structure may be commented out if not used
{
iRI-Parameters [0] HI2Operations.IRI-Parameters,
iRIsContent [1] HI2Operations.IRIsContent,
...
}

EPSIRI ::= CHOICE
-- This structure may be commented out if not used
{
iRI-EPS-Parameters [0] EpsHI2Operations.IRI-Parameters,
epsIRIsContent [1] EpsHI2Operations.EpsIRIsContent,
...
}

ConfIRI ::= CHOICE
-- This structure may be commented out if not used
{
iRI-Conf-Parameters [0] CONFHI2Operations.IRI-Parameters,
confIRIsContent [1] CONFHI2Operations.ConfIRIsContent,
...
}

ProSeIRI ::= CHOICE
-- This structure may be commented out if not used
{
iRI-ProSe-Parameters [0] ProSeHI2Operations.IRI-Parameters,
proseIRIsContent [1] ProSeHI2Operations.ProSeIRIsContent,
...
}

GcseIRI ::= CHOICE
-- This structure may be commented out if not used
{
iRI-Gcse-Parameters [0] GCSEHI2Operations.IRI-Parameters,
gcseIRIsContent [1] GCSEHI2Operations.GcseIRIsContent,
...
}

-- ===========================
-- Definitions for TRI Payload
-- ===========================

TRIPayload ::= CHOICE
{
integrityCheck [0] IntegrityCheck,
testPDU [1] NULL,
paddingPDU [2] OCTET STRING,
-- Undefined contents (will be discarded)
keep-alive [3] NULL,
keep-aliveResponse [4] NULL,
firstSegmentFlag [5] NULL,
lastSegmentFlag [6] NULL,
...,
cINReset [7] NULL,
operatorLeaMessage [8] OperatorLeaMessage,
optionRequest [9] OptionRequest,
optionResponse [10] OptionResponse,
optionComplete [11] NULL,
pDUAcknowledgementRequest [12] NULL,
pDUAcknowledgementResponse [13] NULL
}

IntegrityCheck ::= SEQUENCE
{
includedSequenceNumbers [0] SEQUENCE OF INTEGER (0..4294967295),
-- gives the order the PDUs were processed
checkType [1] CheckType,
dataType [2] DataType OPTIONAL,
-- From version5(5) the dataType is mandatory for hashes and for signatures
-- (see clause 7.2.3)
checkValue [3] OCTET STRING,
-- Network byte order
-- If checkValue contains a signature, the octet string field space may be
-- used to insert the appropriate ASN.1 DER or BER encoded structure for the
-- DSS/DSA signature as described in IETF RFC 3279 [43], clause 2.2.2.
...,
hashAlgorithm [4] HashAlgorithm OPTIONAL,
-- Clarifies the hash function if checkType is hash(1).
-- If used, it shall be present for each checkType hash(1).
signatureAlgorithm [5] SignatureAlgorithm OPTIONAL
-- Clarifies the signature algorithm if checkType is signature(2).
-- If used, it shall be present for each checkType signature(2).
}

CheckType ::= ENUMERATED
{
hash(1),
-- hash value
signature(2),
-- DSS/DSA signature
...
}

DataType ::= ENUMERATED
{
iRI(1),
cC(2),
...,
iLHI(3)
}

HashAlgorithm ::= ENUMERATED
{
sHA-1(1),
-- Included for legacy/migration purposes only, not to be used for new implementations
sHA-256(2),
sHA-384(3),
sHA-512(4),
...
}

SignatureAlgorithm ::= ENUMERATED
{
dSA(1),
-- Included for legacy/migration purposes only, not to be used for new implementations
eCDSA(2),
edDSA(3),
...
}

Option ::= CHOICE
{
pDUAcknowledgement [0] NULL,
...
}

OptionRequest ::= SEQUENCE
{
requestedOptions [0] SEQUENCE OF Option,
...
}

OptionResponse ::= SEQUENCE
{
acceptedOptions [0] SEQUENCE OF Option,
declinedOptions [1] SEQUENCE OF Option,
...
}

-- ==================================
-- Definitions for OperatorLeaMessage
-- ==================================

OperatorLeaMessage ::= SEQUENCE
{
messagePriority [0] OperatorLeaMessagePriority,
message [1] OCTET STRING (SIZE(1..255)),
...
}

OperatorLeaMessagePriority ::= ENUMERATED
{
error(1),
-- reporting of error conditions that have impact on the quality of the
-- intercepted data
informational(2),
-- reporting of conditions that will not have direct impact on the quality of
-- the intercepted data
...
}

-- ===================================
-- Definitions for EncryptionContainer
-- ===================================

EncryptionContainer ::= SEQUENCE
{
encryptionType [0] EncryptionType,
encryptedPayload [1] OCTET STRING,
-- once decrypted, it can be interpreted as EncryptedPayload
...,
encryptedPayloadType [2] EncryptedPayloadType OPTIONAL
}

EncryptionType ::= ENUMERATED
{
none(1),
-- No encryption is applied.
national-option(2),
-- Use this option when an encryption scheme is negotiated on a national level
aES-192-CBC(3),
-- The Advanced Encryption Standard using a 192 bit key in CBC mode
aES-256-CBC(4),
-- The Advanced Encryption Standard using a 256 bit key in CBC mode
blowfish-192-CBC(5),
-- Blowfish (www.schneier.com/blowfish.html) using a 192 bit key in CBC mode
blowfish-256-CBC(6),
-- Blowfish using a 256 bit key in CBC mode
threedes-cbc(7),
-- Triple-DES using a 192 bit key in CBC mode
...
}

EncryptedPayload ::= SEQUENCE
{
byteCounter [0] INTEGER (0..18446744073709551615),
-- The sum of the sizes of all PDUs before this PDU.
-- It is initialized with the unixTime (number of seconds since 01-01-1970)
-- multiplied by 2^32 at first use.
-- Where N is sequencenumber of the n-th PDU in transfer, and size(PDU(N))
-- as defined in annex G:
-- IF N > 0 THEN
-- PDU[N].byteCounter = PDU[N-1].byteCounter + size(PDU[N-1])
-- ELSE
-- PDU[N].byteCounter = ( unixTime(now) << 32 )
-- ENDIF
payload [1] Payload,
...
}

EncryptedPayloadType ::= ENUMERATED
{
unknown(1),
part2(2),
-- encrypted payload is ETSI TS 102 232-2 [5]
part3(3),
-- encrypted payload is ETSI TS 102 232-3 [6]
part4(4),
-- encrypted payload is ETSI TS 102 232-4 [32]
part5(5),
-- encrypted payload is ETSI TS 102 232-5 [37]
part6(6),
-- encrypted payload is ETSI TS 102 232-6 [36]
part7(7),
-- encrypted payload is ETSI TS 102 232-7 [38]
...,
part1(8)
-- encrypted payload is ETSI TS 102 232-1 (the present document)
}

-- ===================================
-- Common Parameters
-- ===================================

Location ::= SEQUENCE
-- This is a common parameter, the use of this parameter is described in clause 4.5
{
umtsHI2Location [0] UmtsHI2Operations.Location OPTIONAL,
epsLocation [1] EpsHI2Operations.EPSLocation OPTIONAL,
...,
wlanLocationAttributes [2] WlanLocationAttributes OPTIONAL,
eTSI671HI2Location [3] HI2Operations.Location OPTIONAL,
threeGPP33128UserLocation [4] TS33128Payloads.UserLocation OPTIONAL
}

WlanLocationAttributes ::= SEQUENCE
{
wlanAPMACAddress [0] OCTET STRING (SIZE(6)) OPTIONAL,
-- 48-bit (6 octet) MAC address of the WLAN access point derived from the BSSID
...
}

IPAddress ::= SEQUENCE
-- This parameter was previously imported from ETSI TS 101 671 [4] but has been copied
-- to ETSI TS 102 232-1 (the present document). It is not recommended to use this parameter in
-- future change requests. Suggested approach is to use a parameter from ETSI TS 103 280 [44]
-- instead.
{
iP-type [1] ENUMERATED
{
iPV4(0),
iPV6(1),
...
},
iP-value [2] IP-value,
iP-assignment [3] ENUMERATED
{
static(1),
-- The static coding shall be used to report a static address.
dynamic(2),
-- The dynamic coding shall be used to report a dynamically allocated address.
notKnown(3),
-- The notKnown coding shall be used to report other than static or dynamically
-- allocated IP addresses.
...
} OPTIONAL,
...,
iPv6PrefixLength [4] INTEGER (1..128) OPTIONAL,
-- Indicates the length of the prefix delegated by the CSP to the subscriber
-- example: 60 if IP address is "2001:db8:0:85a3::ac1f:8001/60"
-- Mandatory in case where the iP-value contains an IPv6 binary value
iPv4SubnetMask [5] OCTET STRING (SIZE(4)) OPTIONAL,
-- For IPv4 addresses, this indicates the subnet mask to be applied to the iP-value field.
-- The subnet mask is intended to be presented as a binary value, e.g. "ff ff ff f8" to
-- represent the dotted-decimal subnet mask of "255.255.255.248" corresponding to
-- a /29 CIDR-format subnet mask
iP-NAT-translated [6] BOOLEAN OPTIONAL
-- If TRUE then NAT translated, if FALSE then not NAT translated.
-- If absent, IPAddress may or may not be NAT translated.
}

IP-value ::= CHOICE
{
iPBinaryAddress [1] OCTET STRING (SIZE(4..16)),
-- In case of IPv6, the Prefix Length is provided by the "iPv6PrefixLength"
-- In case of IPv4, the netmask is provided by the "iPv4SubnetMask"
iPTextAddress [2] IA5String (SIZE(7..45)),
-- In case of IPv6, the delivered iPTextAddress field could include a complete
-- single IPv6-Address or an IPv6-Prefix for a subnetwork on the target side.
-- In case of IPv4, the delivered iPTextAddress field could include a single
-- IPv4 address or an IPv4address/netmask, for example "192.168.1.1" or "192.168.1.1/24"
...
}

LawfulInterceptionIdentifier ::= Common-Parameters.LIID
-- LIID is a common parameter imported from ETSI TS 103 280 [44].
-- It is redefined as LawfulInterceptionIdentifier in this
-- module to preserve the original type name during the
-- removal of imports from ETSI TS 101 671 [4].

END -- end of LI-PS-PDU</pre>

<center>[[Telecommunications info|To Telecommunications info]]</center>

My 102 232-3 notes

2025-06-24T22:02:09Z

Paul: /* IRI events § 6.1 */

My notes on ETSI TS 102 232-3

Version 3.13.1 (2024-01) was used as basis.

== Internet Access Service (IAS) § 4.1 ==

Figure 1 Internet access diagram

[[File:102-232-3 V3.8.1 Figure1.png|alt=102-232-3 V3.8.1 Figure 1 Internet access diagram|102-232-3 V3.8.1 Figure 1 Internet access diagram]]

== Lawful Interception Requirements § 4.3 ==

=== Result of interceptions § 4.3.2 ===

The network operator, access provider or service provider shall provide Intercept Related Information (IRI), in relation to each target service:
<ol type="a">
<li>When an attempt is made to access the access network.</li>
<li>When an access to the access network is permitted.</li>
<li>When an access to the access network is not permitted.</li>
<li>On change of status (e.g. in the access network).</li>
<li>On change of location (this can be related or unrelated to the communication or at all times when the apparatus is switched on).</li>
</ol>

The IRI shall contain:
<ol type="a">
<li>Identities used by or associated with the target identity (e.g. dial-in calling line number and called line number, access server identity, Ethernet addresses, access device identifier).</li>
<li>Details of services used and their associated parameters.</li>
<li>Information relating to status.</li>
<li>Timestamps.</li>
</ol>

Content of Communication (CC) shall be provided for every IP datagram sent through the IAP's network that:
<ol type="a">
<li>Has the target's IP address as the IP source address.</li>
<li>Has the target's IP address as the IP destination address.</li>
</ol>

The CC Content of communication shall contain:
<ol type="a">
<li>A stream of octets for every captured datagram, containing a copy of the datagram from layer 3 upwards.</li>
</ol>
:NOTE: Due to the possibility of IP source address spoofing, the fact that an intercepted packet has the target's IP address as the IP source address does not guarantee that the packet was transmitted by the target; i.e. an intercept in place at the interface connected to the target may not include packets originating from other users spoofing the target's IP address and will not include packets from the actual target that contain a spoofed IP address.

=== Intercept related information § 4.3.3 ===

Intercept Related Information (IRI) shall be conveyed to the LEMF in messages, or IRI data records, respectively. Four types of IRI records are defined:

# IRI-BEGIN record at the first event of a communication attempt, opening the IRI transaction.
# IRI-END record at the end of a communication attempt, closing the IRI transaction.
# IRI-CONTINUE record at any time during a communication attempt within the IRI transaction.
# IRI-REPORT record used in general for non-communication related events.

For a description of the use and purpose of the various IRI records refer to ETSI TS 102 232-1.

== IRI events § 6.1 ==

TODO: Insert Figure 6 state diagram for an Internet session and events depicted.

== ASN.1 ==

<pre>IPAccessPDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) iPAccess(3) version17(17)}

DEFINITIONS IMPLICIT TAGS ::=
BEGIN

IMPORTS
-- from ETSI TS 102 232-1 [2]
IPAddress,
Location
FROM LI-PS-PDU
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) li-ps(5) genHeader(1) version37(37)};

-- ============================
-- Object Identifier Definition
-- ============================

iPAccessPDUObjId RELATIVE-OID ::= {li-ps(5) iPAccess(3) version17(17)}
iPIRIObjId RELATIVE-OID ::= {iPAccessPDUObjId iRI(1)}
iPCCObjId RELATIVE-OID ::= {iPAccessPDUObjId cC(2)}
iPIRIOnlyObjId RELATIVE-OID ::= {iPAccessPDUObjId iRIOnly(3)}

-- definitions are relative to
-- {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2)}

-- ==========================
-- IP Communications Contents
-- ==========================

IPCC ::= SEQUENCE
{
iPCCObjId [0] RELATIVE-OID,
iPCCContents [1] IPCCContents
}

IPCCContents ::= CHOICE
{
iPPackets [0] OCTET STRING,
...,
iPTruncatedPacket [1] IPTruncatedPacket
}

IPTruncatedPacket ::= SEQUENCE
{
truncatedPacket [0] OCTET STRING,
originalLength [1] INTEGER OPTIONAL,
...
}

-- ===================================================
-- Intercept-related information for general IP-Access
-- ===================================================

IPIRI ::= SEQUENCE
{
iPIRIObjId [0] RELATIVE-OID,
iPIRIContents [1] IPIRIContents,
...
}

IPIRIContents ::= SEQUENCE
{
accessEventType [0] AccessEventType,
targetUsername [1] OCTET STRING,
-- in ASCII-characters
internetAccessType [2] InternetAccessType,
iPVersion [3] IPVersion,
targetIPAddress [4] LI-PS-PDU.IPAddress OPTIONAL,
-- IP address may not be available in case of failed logon attempts.
-- If it is available, it must be sent.
-- This field will carry the first IPv4 or IPv6 target IP address with or without
-- subnet. Use of this field is fully described in section 6.2.1.
targetNetworkID [5] UTF8String (SIZE (1..20)) OPTIONAL,
-- Target network ID (e.g. MAC address, PSTN number)
targetCPEID [6] UTF8String (SIZE (1..128)) OPTIONAL,
-- CPEID (e.g. Relay Agent info, computer name)
targetLocation [7] UTF8String (SIZE (1..64)) OPTIONAL,
-- When internetAccessType is Wireless LAN, this field should contain a string which
-- uniquely identifies the wireless accesspoint within the SvP domain
-- New implementations are encouraged to use the location [24] parameter where possible.
pOPPortNumber [8] INTEGER (0..4294967295) OPTIONAL,
-- The POP port number used by the target
callBackNumber [9] UTF8String (SIZE (1..20)) OPTIONAL,
-- The number used to call-back the target
startTime [10] GeneralizedTime OPTIONAL,
-- The start date-time of the session or lease
endTime [11] GeneralizedTime OPTIONAL,
-- The actual end date-time of the session or lease
endReason [12] EndReason OPTIONAL,
-- The reason for the session to end
octetsReceived [13] INTEGER (0..18446744073709551615) OPTIONAL,
-- The number of octets the target received
octetsTransmitted [14] INTEGER (0..18446744073709551615) OPTIONAL,
-- The number of octets the target transmitted
rawAAAData [15] OCTET STRING OPTIONAL,
-- Content of the raw AAA record
...,
expectedEndTime [16] GeneralizedTime OPTIONAL,
-- The expected end date-time of the session or lease
pOPPhoneNumber [17] UTF8String (SIZE (1..20)) OPTIONAL,
-- The phone number dialed by the target for dial-up
pOPIdentifier [18] IPIRIIDType OPTIONAL,
-- The identifier or name of the POP
pOPIPAddress [19] LI-PS-PDU.IPAddress OPTIONAL,
-- The IP address of the POP
nationalIPIRIParameters [20] NationalIPIRIParameters OPTIONAL,
-- National IP IRI Parameters
additionalIPAddress [21] LI-PS-PDU.IPAddress OPTIONAL,
-- This field will carry the first IPv6 target IP address with or without prefix when the
-- iPVersion parameter is set to iPV4andV6.
-- Use of this field is fully described in section 6.2.1
authenticationType [22] AuthenticationType OPTIONAL,
-- Field used to identify the authentication type to assist with LEMF data validation
otherTargetIdentifiers [23] SEQUENCE OF OtherTargetIdentifiers OPTIONAL,
-- This parameter will carry the second and subsequent IPv4 or IPv6 target IP addresses
-- It is used when multiple subnet/prefix ranges are assigned to a target service.
-- Use of this field is fully described in section 6.2.1
location [24] LI-PS-PDU.Location OPTIONAL,
-- The location associated with the target
pOPPortID [25] OCTET STRING OPTIONAL,
-- This field will carry the NAS-Port-ID as defined in RFC 2869 [17]:
-- This parameter shall be populated with the RADIUS value.
framedRoutes [26] SEQUENCE OF FramedRoute OPTIONAL
-- It is used to list all the available Framed Route and Framed IPv6 Route information

}

AccessEventType ::= ENUMERATED
{
accessAttempt(0),
-- A target requests access to the IAS
accessAccept(1),
-- IAS access is granted to the target, the session begins
accessReject(2),
-- IAS access is refused to the target
accessFailed(3),
-- The accessAttempt timed-out or failed otherwise
sessionStart(4),
-- A target starts using the IAS; not in use anymore from version 4(4)
sessionEnd(5),
-- A target stops using the IAS; not in use anymore from version 4(4)
interimUpdate(6),
-- Intermediate status report on service status or usage
...,
startOfInterceptionWithSessionActive(7),
-- LI is started on a target who already has an active session
accessEnd(8),
-- A target stops using the IAS, the session ends
endOfInterceptionWithSessionActive(9),
-- LI is ended on a target who still has an active session
unknown(10)
}

InternetAccessType ::= ENUMERATED
{
undefined(0),
dialUp(1),
-- IAS via DialUp access
xDSL(2),
-- IAS via DSL access
cableModem(3),
-- IAS via Cable access
lAN(4),
-- IAS via LAN access
...,
wirelessLAN(5),
-- IAS via Wireless LAN access
fTTx(6),
-- IAS via Fiber access
wIMAX-HIPERMAN(7),
-- IAS via WIMAX/HIPERMAN (fixed access)
satellite(8),
-- IAS via Satellite access
-- (when it is not covered by any 3GPP or ETSI mobile Lawful Interception specifications)
wireless-other(9)
-- IAS via other type of Wireless access
-- (when it is not covered by any 3GPP or ETSI mobile Lawful Interception specifications)
}

IPVersion ::= ENUMERATED
{
iPV4(1),
-- The IPv4 protocol is used
iPV6(2),
-- The IPv6 protocol is used
iPV4andV6(3),
-- The IPv4 and IPv6 protocols are used
...
}

EndReason ::= ENUMERATED
{
undefined(0),
regularLogoff(1),
-- The target logged off
connectionLoss(2),
-- The connection was lost
connectionTimeout(3),
-- The connection timed-out
leaseExpired(4),
-- The DHCP lease expired
...
}

IPIRIIDType ::= CHOICE
{
printableIDType [0] UTF8String (SIZE (1..128)),
-- For printable userIDs, such as the Radius username, phonenumbers
macAddressType [1] OCTET STRING (SIZE (6)),
-- For MAC address types, raw binary format as in RFC 2132 [15]
ipAddressType [2] LI-PS-PDU.IPAddress,
-- For IP address types
...
}

NationalIPIRIParameters ::= SEQUENCE
{
countryCode [1] PrintableString (SIZE (2)),
-- Country Code according to ISO 3166-1 [16],
-- the country to which the parameters inserted after the extension marker apply.
...
-- In case a given country wants to use additional national parameters according to its law,
-- these national parameters should be defined using the ASN.1 syntax and added after the
-- extension marker (...).
-- It is recommended that "version parameter" and "vendor identification parameter" are
-- included in the national parameters definition. Vendor identifications can be
-- retrieved from the IANA web site (see Annex E Bibliography). Besides, it is recommended
-- to avoid using tags from 240 to 255 in a formal type definition.
}

AuthenticationType ::= ENUMERATED
{
unknown(0),
-- AAA function for the target service is unknown
static(1),
-- The target service is assigned a static IP address & no AAA expected
radiusAAA(2),
-- AAA function for the target service is provided by RADIUS
dhcpAAA(3),
-- AAA function for the target service is provided by DHCP
diameterAAA(4),
-- AAA function for the target service is provided by DIAMETER
...
}

OtherTargetIdentifiers ::= CHOICE
{
-- Additional target identifiers associated with the target service
-- This list is extensible to accommodate other target identifiers which
-- may be required in future.
iPAddress [0] LI-PS-PDU.IPAddress,
-- IPAddress imported from TS 102 232 [2].
-- This can be an IPv4 address (with or without a subnet range defined) or
-- an IPv6 address (with or without a prefix range defined).
...
}

FramedRoute ::= CHOICE
{
-- Additional Framed Route prefix information associated with the target service

framedRoute [0] OCTET STRING,
-- This could contain an IPv4 as well as IPv6 FramedRoute information
-- including additional information such Gateway address and
-- one or more metrics in texual format.
-- This parameter shall be populated with the RADIUS value.
...
}

-- =====================================================
-- Intercept-related information for IRI-Only intercepts
-- =====================================================

IPIRIOnly ::= SEQUENCE
{
iPIRIOnlyObjId [0] RELATIVE-OID,
iPInformation [1] IPInformation,
protocolInformation [2] ProtocolInformation,
iPAggregatedNbrOfPackets [3] INTEGER OPTIONAL,
iPAggregatedNbrOfBytes [4] INTEGER OPTIONAL,
...,
pDSRInformation [5] PDSRInformation OPTIONAL
}

IPInformation ::= CHOICE
{
iPv4Information [0] IPv4Information,
iPv6Information [1] IPv6Information
}

ProtocolInformation ::= CHOICE
{
none [0] NULL,
-- No layer 4 protocol information is provided
tCPInformation [1] TCPInformation,
uDPInformation [2] UDPInformation,
...
}

IPv4Information ::= SEQUENCE
{
headerLength [0] OCTET STRING OPTIONAL,
typeOfService [1] OCTET STRING OPTIONAL,
totalLength [2] OCTET STRING (SIZE (2))OPTIONAL,
identification [3] OCTET STRING (SIZE (2))OPTIONAL,
fragment [4] OCTET STRING (SIZE (2))OPTIONAL,
ttl [5] OCTET STRING OPTIONAL,
protocol [6] OCTET STRING OPTIONAL,
headerChecksum [7] OCTET STRING (SIZE (2))OPTIONAL,
source [8] OCTET STRING (SIZE (4)),
destination [9] OCTET STRING (SIZE (4)),
options [10] OCTET STRING (SIZE (0..40))OPTIONAL
}

IPv6Information ::= SEQUENCE
{
trafficClass [0] OCTET STRING OPTIONAL,
flowLabel [1] OCTET STRING (SIZE (20))OPTIONAL,
payloadLength [2] OCTET STRING (SIZE (4))OPTIONAL,
nextHeader [3] OCTET STRING OPTIONAL,
hopLimit [4] OCTET STRING OPTIONAL,
source [5] OCTET STRING (SIZE (16)),
destination [6] OCTET STRING (SIZE (16))
}

TCPInformation ::= SEQUENCE
{
sourcePort [0] OCTET STRING (SIZE (2))OPTIONAL,
destinationPort [1] OCTET STRING (SIZE (2))OPTIONAL,
sequenceNumber [2] OCTET STRING (SIZE (4))OPTIONAL,
ackNumber [3] OCTET STRING (SIZE (4))OPTIONAL,
dataOffset [4] BIT STRING (SIZE (4))OPTIONAL,
-- First 4 bits
controlBits [5] BIT STRING (SIZE (6))OPTIONAL,
-- Last 6 bits
windowSize [6] OCTET STRING (SIZE (2))OPTIONAL,
checkSum [7] OCTET STRING (SIZE (2))OPTIONAL,
urgentPointer [8] OCTET STRING (SIZE (2))OPTIONAL,
options [9] OCTET STRING (SIZE (0..40))OPTIONAL
}

UDPInformation ::= SEQUENCE
{
sourcePort [0] OCTET STRING (SIZE (2))OPTIONAL,
destinationPort [1] OCTET STRING (SIZE (2))OPTIONAL,
length [2] OCTET STRING (SIZE (2))OPTIONAL,
checkSum [3] OCTET STRING (SIZE (2))OPTIONAL
}

PDSRInformation::= SEQUENCE
{
summaryTrigger [0] PDSRSummaryTrigger,
firstPacketTimestamp [1] GeneralizedTime,
lastPacketTimestamp [2] GeneralizedTime,
packetCount [3] INTEGER,
byteCount [4] INTEGER,
...
}

PDSRSummaryTrigger ::= ENUMERATED
{
startOfFlow(0),
timerExpiry(1),
packetCount(2),
byteCount(3),
endOfFlow(4),
...
}

END -- end of IPAccessPDU</pre>

<center>[[Telecommunications info | To Telecommunications info]]</center>

My ATIS lawful interception standard notes

2025-06-24T21:57:19Z

Paul: /* My Annex A ASN.1 Definition Notes */

== ATIS-1000013.v2.2015 ==

Document title is "Lawfully Authorized Electronic Surveillance (LAES) for Internet Access and Services, Version 2"

=== Internet Access & Services (IAS) Model § 4.1 ===

Registration (Reg) is defined as any service provider authentication or login process required of subject to gain Internet access.

Resource (Res) is defined as reserving required resources necessary to grant subject access to Internet. This may include layer three addresses and bandwidth.

Packet Transfer (PT) is defined as communicating layer three IP packets to and from the Internet. Layer one and two networks do not perform PT-F.

[[File:ATIS-IAS-Model.png|alt=ATIS Internet Access Services Model|ATIS Internet Access Services Model]]

=== Communications Identifying Information (CmII) messages ===

Can be categorized as Access Associated CmII (AACmII) and Content Associated CmII (CACmII)

== Mapping of Surveillance Events § 5.4 ==

{| class="wikitable sortable"
|+ LAES Events & Associated Functions

|-
! IAS Functions !! LAES Events Reported
|-
| Registration Function (Reg-F) (reports AACmII) ||
* Access Attempt
* Access Accepted
* Access Failed
* Access Session End
* Access Rejected
* Access Signaling Message Report
|-
| Resource Function (Res-F) (reports AACmII) ||
* Packet Data Session Start
* Packet Data Session Failed
* Packet Data Session End
* Packet Data Session Already Established
|-
| Packet Transfer Function (PT-F) (reports CACmII) ||
* Packet Data Header Report
* Packet Data Summary Report
|}

== CmII Messages § 6.2 ==

See spec for details of each message.

== CmC Deilvery APDU § 6.3 ==

See spec for details.

== My Annex A ASN.1 Definition Notes ==

=== Events with location ===

These events have location defined as tag [8]:

* Access Session End
* Packet Data Session Start
* Packet Data Session End
* Packet Data Session Already Established

Access Accept has location defined as tag [9].

=== ASN.1 definition of Location ===

<pre>Location ::= SET OF SEQUENCE {
locationType [0] UTF8String,
location [1] UTF8String
}</pre>

== ATIS-1000678.v4.2020 ==

== ATIS-0700005.v002 ==

<center>[[Telecommunications info|To Telecommunications info]]</center>

My ATIS lawful interception standard notes

2025-06-24T21:34:07Z

Paul: /* My Annex A ASN.1 Definition Notes */

== ATIS-1000013.v2.2015 ==

Document title is "Lawfully Authorized Electronic Surveillance (LAES) for Internet Access and Services, Version 2"

=== Internet Access & Services (IAS) Model § 4.1 ===

Registration (Reg) is defined as any service provider authentication or login process required of subject to gain Internet access.

Resource (Res) is defined as reserving required resources necessary to grant subject access to Internet. This may include layer three addresses and bandwidth.

Packet Transfer (PT) is defined as communicating layer three IP packets to and from the Internet. Layer one and two networks do not perform PT-F.

[[File:ATIS-IAS-Model.png|alt=ATIS Internet Access Services Model|ATIS Internet Access Services Model]]

=== Communications Identifying Information (CmII) messages ===

Can be categorized as Access Associated CmII (AACmII) and Content Associated CmII (CACmII)

== Mapping of Surveillance Events § 5.4 ==

{| class="wikitable sortable"
|+ LAES Events & Associated Functions

|-
! IAS Functions !! LAES Events Reported
|-
| Registration Function (Reg-F) (reports AACmII) ||
* Access Attempt
* Access Accepted
* Access Failed
* Access Session End
* Access Rejected
* Access Signaling Message Report
|-
| Resource Function (Res-F) (reports AACmII) ||
* Packet Data Session Start
* Packet Data Session Failed
* Packet Data Session End
* Packet Data Session Already Established
|-
| Packet Transfer Function (PT-F) (reports CACmII) ||
* Packet Data Header Report
* Packet Data Summary Report
|}

== CmII Messages § 6.2 ==

See spec for details of each message.

== CmC Deilvery APDU § 6.3 ==

See spec for details.

== My Annex A ASN.1 Definition Notes ==

These events have location defined as tag [8]:

* Access Session End
* Packet Data Session Start
* Packet Data Session End
* Packet Data Session Already Established

Access Accept has location defined as tag [9].

== ATIS-1000678.v4.2020 ==

== ATIS-0700005.v002 ==

<center>[[Telecommunications info|To Telecommunications info]]</center>

My ATIS lawful interception standard notes

2025-06-24T21:33:54Z

Paul: /* CmC Deilvery APDU § 6.3 */

== ATIS-1000013.v2.2015 ==

Document title is "Lawfully Authorized Electronic Surveillance (LAES) for Internet Access and Services, Version 2"

=== Internet Access & Services (IAS) Model § 4.1 ===

Registration (Reg) is defined as any service provider authentication or login process required of subject to gain Internet access.

Resource (Res) is defined as reserving required resources necessary to grant subject access to Internet. This may include layer three addresses and bandwidth.

Packet Transfer (PT) is defined as communicating layer three IP packets to and from the Internet. Layer one and two networks do not perform PT-F.

[[File:ATIS-IAS-Model.png|alt=ATIS Internet Access Services Model|ATIS Internet Access Services Model]]

=== Communications Identifying Information (CmII) messages ===

Can be categorized as Access Associated CmII (AACmII) and Content Associated CmII (CACmII)

== Mapping of Surveillance Events § 5.4 ==

{| class="wikitable sortable"
|+ LAES Events & Associated Functions

|-
! IAS Functions !! LAES Events Reported
|-
| Registration Function (Reg-F) (reports AACmII) ||
* Access Attempt
* Access Accepted
* Access Failed
* Access Session End
* Access Rejected
* Access Signaling Message Report
|-
| Resource Function (Res-F) (reports AACmII) ||
* Packet Data Session Start
* Packet Data Session Failed
* Packet Data Session End
* Packet Data Session Already Established
|-
| Packet Transfer Function (PT-F) (reports CACmII) ||
* Packet Data Header Report
* Packet Data Summary Report
|}

== CmII Messages § 6.2 ==

See spec for details of each message.

== CmC Deilvery APDU § 6.3 ==

See spec for details.

== My Annex A ASN.1 Definition Notes ==

These events have location defined as tag [8].

* Access Session End
* Packet Data Session Start
* Packet Data Session End
* Packet Data Session Already Established

Access Accept has location defined as tag [9].

== ATIS-1000678.v4.2020 ==

== ATIS-0700005.v002 ==

<center>[[Telecommunications info|To Telecommunications info]]</center>

My ATIS lawful interception standard notes

2025-06-24T21:27:41Z

Paul: /* ATIS-1000013.v2.2015 */

== ATIS-1000013.v2.2015 ==

Document title is "Lawfully Authorized Electronic Surveillance (LAES) for Internet Access and Services, Version 2"

=== Internet Access & Services (IAS) Model § 4.1 ===

Registration (Reg) is defined as any service provider authentication or login process required of subject to gain Internet access.

Resource (Res) is defined as reserving required resources necessary to grant subject access to Internet. This may include layer three addresses and bandwidth.

Packet Transfer (PT) is defined as communicating layer three IP packets to and from the Internet. Layer one and two networks do not perform PT-F.

[[File:ATIS-IAS-Model.png|alt=ATIS Internet Access Services Model|ATIS Internet Access Services Model]]

=== Communications Identifying Information (CmII) messages ===

Can be categorized as Access Associated CmII (AACmII) and Content Associated CmII (CACmII)

== Mapping of Surveillance Events § 5.4 ==

{| class="wikitable sortable"
|+ LAES Events & Associated Functions

|-
! IAS Functions !! LAES Events Reported
|-
| Registration Function (Reg-F) (reports AACmII) ||
* Access Attempt
* Access Accepted
* Access Failed
* Access Session End
* Access Rejected
* Access Signaling Message Report
|-
| Resource Function (Res-F) (reports AACmII) ||
* Packet Data Session Start
* Packet Data Session Failed
* Packet Data Session End
* Packet Data Session Already Established
|-
| Packet Transfer Function (PT-F) (reports CACmII) ||
* Packet Data Header Report
* Packet Data Summary Report
|}

== CmII Messages § 6.2 ==

See spec for details of each message.

== CmC Deilvery APDU § 6.3 ==

See spec for details.

<center>[[Telecommunications info|To Telecommunications info]]</center>

== ATIS-1000678.v4.2020 ==

== ATIS-0700005.v002 ==

<center>[[Telecommunications info|To Telecommunications info]]</center>

File:ATIS-IAS-Model.png

2025-06-24T20:41:26Z

Paul:

ATIS Internet Access Services Model

My ATIS lawful interception standard notes

2025-06-24T20:39:30Z

Paul: /* ATIS-1000013.v2.2015 */

== ATIS-1000013.v2.2015 ==

Document title is "Lawfully Authorized Electronic Surveillance (LAES) for Internet Access and Services, Version 2"

=== Communications Identifying Information (CmII) messages ===

Can be categorized as Access Associated CmII (AACmII) and Content Associated CmII (CACmII)

* Access Attempt
* Access Accepted
* Access Failed
* Access Session End
* Access Rejected
* Access Signaling Message Report
* Packet Data Session Start
* Packet Data Session Failed
* Packet Data Session End
* Packet Data Session Already Established
* Packet Data Header Report
* Packet Data Summary Report

=== CmC ===

CmC Delivery APDU

== ATIS-1000678.v4.2020 ==

== ATIS-0700005.v002 ==

<center>[[Telecommunications info|To Telecommunications info]]</center>

My Satisfactory Info

2025-06-14T16:43:00Z

Paul: /* Links */

My Satisfactory Info

2025-06-14T16:42:42Z

Paul: /* Start server */

== Satisfactory dedicated server setup overview ==

These steps were created using Ubuntu 22.04.5 LTS and Satisfactory dedicated server 1.1

== Resources ==

[https://satisfactory.wiki.gg/wiki/Dedicated_servers Official Satisfactory wiki page on dedicated server]

== Install Satisfactory dedicated server files ==

To install, I used the following command with my steam user:

<code>steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous +app_update 1690800 validate +quit</code>

== Setup port forwarding & firewall ==

Configured firewall to port forward 7777 for UDP and 8888 for TCP.

No need to update my firewall rules on Ubuntu server.

== Start server ==

Follow directions on official wiki, they worked great.

== Links ==

<center>[[Gaming|To my gaming notes]]</center>

My Satisfactory Info

2025-06-14T16:41:08Z

Paul: initial page creation