TSGs and WGs are encouraged to liaise directly with the relevant technical bodies within the 3GPP and Partners as appropriate. A liaison statement shall clearly communicate what is expected from the receiver, i.e., which parts are for information, which questions are expected to be clarified and by whom (especially if there are multiple receivers), and also when an answer is needed, e.g., when is the next meeting of the group sending the liaison statement.
3GPP maintains a list of external organizations with which 3GPP has exchanged liaisons.
This page is maintained by the Liaison co-ordinator
Incoming liaisons targeted for the next meeting.
| CT | SA | RAN | GERAN |
|---|---|---|---|
| CT Plenary | SA Plenary | RAN Plenary | GERAN Plenary |
| CT WG1 | SA WG1 | RAN WG1 | GERAN WG1 |
| CT WG3 | SA WG2 | RAN WG2 | GERAN WG2 |
| CT WG4 | SA WG3 | RAN WG3 | GERAN WG3 |
| CT WG6 | SA WG4 | RAN WG4 | |
| SA WG5 | RAN WG5 |
Note: If you get an error page this means no incoming liaisons for that meeting received yet.
Outgoing liaisons result from last meeting.
| CT | SA | RAN | GERAN |
|---|---|---|---|
| CT Plenary | SA Plenary | RAN Plenary | GERAN Plenary |
| CT WG1 | SA WG1 | RAN WG1 | GERAN WG1 |
| CT WG3 | SA WG2 | RAN WG2 | GERAN WG2 |
| CT WG4 | SA WG3 | RAN WG3 | GERAN WG3 |
| CT WG6 | SA WG4 | RAN WG4 | |
| SA WG5 | RAN WG5 |
Note: If you get an error page this means no outcoming liaisons from that meeting.

