hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6.5 Alarm Indication
| Table 6.6.5.1: Elementary procedure Alarm Indication
Name:
AlarmIndication
Code:
0x07
Issued by:
Secondary device
Procedure class:
2
DownloadMode state:
No
Power mode:
Low
Table 6.6.5.2: Initiating message parameters and format for Alarm Indication
Number
Length
Type
Description
2 i – 1
1 octet
Un... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6.6 Set Device Data
| Table 6.6.6.1: Elementary procedure Set Device Data
Name:
SetDeviceData
Code:
0x0E
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.6.6.2: Initiating message parameters and format for Set Device Data
Number
Length
Type
Description
1
1 octet
Unsigned integ... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6.7 Get Device Data
| Table 6.6.7.1: Elementary procedure Get Device Data
Name:
GetDeviceData
Code:
0x0F
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.6.7.2: Initiating message parameters and format for Get Device Data
Number
Length
Type
Description
1
1 octet
Unsigned integ... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7 Multi-antenna elementary procedures
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.1 Antenna Calibrate
| Table 6.7.1.1: Elementary procedure Antenna Calibrate
Name:
AntennaCalibrate
Code:
0x80
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
High
Table 6.7.1.2: Initiating message parameters and format for Antenna Calibrate
Number
Length
Type
Description
1
1 octet
Unsign... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.2 Antenna Set Tilt
| Table 6.7.2.1: Elementary procedure Antenna Set Tilt
Name:
AntennaSetTilt
Code:
0x81
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
High
Table 6.7.2.2: Initiating message parameters and format for Antenna Set Tilt
Number
Length
Type
Description
1
1 octet
Unsigned i... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.3 Antenna Get Tilt
| Table 6.7.3.1: Elementary procedure Antenna Get Tilt
Name:
AntennaGetTilt
Code:
0x82
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.7.3.2: Initiating message parameters and format for Antenna Get Tilt
Number
Length
Type
Description
1
1 octet
Unsigned in... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.4 Antenna Set Device Data
| Table 6.7.4.1: Elementary procedure Antenna Set Device Data
Name:
AntennaSetDeviceData
Code:
0x83
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.7.4.2: Initiating message parameters and format for Antenna Set Device Data
Number
Length
Type
Description
1
... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.5 Antenna Get Device Data
| Table 6.7.5.1: Elementary procedure Antenna Get Device Data
Name:
AntennaGetDeviceData
Code:
0x84
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.7.5.2: Initiating message parameters and format for Antenna Get Device Data
Number
Length
Type
Description
1
... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.6 Antenna Alarm Indication
| Table 6.7.6.1: Elementary procedure Antenna Alarm Indication
Name:
AntennaAlarmIndication
Code:
0x85
Issued by:
Secondary device
Procedure class:
2
DownloadMode state:
No
Power mode:
Low
Table 6.7.6.2: Initiating message parameters and format for Antenna Alarm Indication
Number
Length
Type
Descriptio... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.7 Antenna Clear Active Alarms
| Table 6.7.7.1: Elementary procedure Antenna Clear Active Alarms
Name:
AntennaClearActiveAlarms
Code:
0x86
Issued by:
Secondary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.7.7.2: Initiating message parameters and format for Antenna Clear Active Alarms
Number
Length
Type
De... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.8 Antenna Get Alarm Status
| Table 6.7.8.1: Elementary procedure Antenna Get Alarm Status
Name:
AntennaGetAlarmStatus
Code:
0x87
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.7.8.2: Initiating message parameters and format for Antenna Get Alarm Status
Number
Length
Type
Description
... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.9 Antenna Get Number Of Antennas
| Table 6.7.9.1: Elementary procedure Antenna Get Number Of Antennas
Name:
AntennaGetNumberOfAntennas
Code:
0x88
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.7.9.2: Initiating message parameters and format for Antenna Get Number Of Antennas
Number
Length
Ty... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.7.10 Antenna Send Configuration Data
| Table 6.7.10.1: Elementary procedure Antenna Send Configuration Data
Name:
AntennaSendConfigurationData
Code:
0x89
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.7.10.2: Initiating message parameters and format for Antenna Send Configuration Data
Number
Leng... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 7 Unknown elementary procedures
| Void.
Annex A (normative):
Return codes for secondary devices
Table A.1: Return Codes for Secondary Devices
Code
Meaning
Alarm
DownloadMode state
0x00
OK
Normal response
X
0x02
Motor Jam
Motor cannot move
X
0x03
ActuatorJam
Actuator jam has been detected. No movement of the actuator, but moveme... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 1 Scope
| Editor's note: clean up the scope in each part.
The present document is one of a multi-part TS, and contains objectives, requirements and test cases that are specific to the Lawful Interception elements of a 3GPP network: Administration Function (ADMF), Point of Interception (POI), Triggering Function (TF), Location A... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 3.2 Symbols
| Void.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4 Overview
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.1 Introduction
| Editor's Note: Many of these should probably make their way to 33.129-1.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.1.1 Overall requirements
| Security requirements for NF-embedded LI functions include requirements derived from LI-specific security functional requirements in relevant specifications (e.g. TS 33.126 [5], TS 33.127 [6] and TS 33.128 [7]), the security requirements described as common to the LI system as described in TS 33.129-1 [8] as well as se... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.1.2 Prerequisites for testing
| Editor's Note: This probably needs to get listed in each relevant test.
There are multiple privilege levels in the network. At a minimum, there are at least two:
- Lawful Interception privileged
- Non-LI privileged administrator
- Non-administrator.
Deployments in the field may split access more granularly, but th... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.1.3 Use of tools in testing
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.1.4 Documentation requirements
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.1.5 Requirements list
| The following TS 33.126 requirements are tested in the present document:
TS 33.126 R6.6-30: The CSP shall ensure that non-authorized personnel or processes (including automated or Artificial Intelligence based systems) that are part of the service cannot detect that interception is taking place.
Editor's Note: This s... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2 Security functional requirements and related test cases specific to NF-embedded LI functions
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.1 Introduction
| The present clause describes the security functional requirements and the corresponding test cases for NF-embedded LI functions. The proposed security requirements are classified in two groups:
- Security functional requirements derived from TS 33.501 and detailed in clause 4.2.2.
- General security functional requir... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2 Security functional requirements on NF-embedded LI functions deriving from 3GPP specifications and related test cases
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.1 General
| The general approach in TS 33.129-1 [8] clause 4.2.2 applies to NF-embedded LI functions. The relevant requirements and test cases for the product class of the NF in which the LI function is embedded also apply. Unless otherwise specified, the requirements and test cases in TS 33.117 [2] clause 4.2.2.3 related to SBA /... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.2 LI LI_Xn HTTP connection disallowed
| Requirement Name: Undetectability by Non-Authorized Parties.
Requirement Reference: TS 33.126 R6.6-30.
Requirement Description: The CSP shall ensure that non-authorized personnel or processes (including automated or Artificial Intelligence based systems) that are part of the service cannot detect that interception is... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.3 LI LI_Xn TLS protection verification
| Editor's Note: Is there a way to verify the layer 3/4 handshake only, without using any meaningful application layer message as a first step - using a simple testing harness/simulator, that doesn't necessarily have any layer 7/app layer knowledge.
Requirement Name: Undetectability by Non-Authorized Parties.
Requireme... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.4 LI LI_Xn HTTP connection disallowed
| Editor's Note: Is there a way to verify the layer 3/4 handshake only, without using any meaningful application layer message as a first step - using a simple testing harness/simulator, that doesn't necessarily have any layer 7/app layer knowledge.
Requirement Name: Undetectability by Non-Authorized Parties.
Requireme... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.5 Credential affinity
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.6 Credential expiry
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.7 Credential chain of trust
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.8 Credential binding
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.2.9 Element of LI binding
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3 Technical baseline
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.1 Introduction
| Clause 4.2.3 provides baseline technical requirements.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2 Protecting data and information
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.1 Protecting data and information – general
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.1.1 Introduction
| The tests listed in TS 33.129-1 [8] clause 4.2.3.2 shall be applied. The following sub-clauses contain additional tests or clarifications which specifically apply for NF-embedded LI functions.
Editor's Note: We may be good to remove these clauses pending an audit of the tests in TS 33.129-1 [8] to ensure they are suff... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.1.2 A crypto inventory exists
| Editor's Note: This test may be equivalent to the test in TS 33.129-1 [8] clause 4.2.3.2.1.2. If it is, remove this test.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.1.3 Replaceable crypto modules
| Editor's Note: This test may be equivalent to the test in TS 33.129-1 [8] clause 4.2.3.2.1.3. If it is, remove this test.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.1.4 Replaceable crypto methods
| Editor's Note: This test may be equivalent to the test in TS 33.129-1 [8] clause 4.2.3.2.1.4. If it is, remove this test.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2 Protecting data and information – unauthorized viewing
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2.1 Introduction
| The tests listed in TS 33.129-1 [8] clause 4.2.3.2.2 shall be applied with the additions and clarifications included in the following sub-clauses.
Editor's Note: Following the audit of 33.129, it seems that most of these tests belong here.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2.2 General-purpose logs cannot contain LI data
| Editor's Note: This test may be equivalent to the test in TS 33.129-1 [8] clause 4.2.3.2.2.2. If it is, remove this test.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2.3 General-purpose logs cannot contain LI data (comms?)
| Editor's Note: This test may be equivalent to the test in TS 33.129-1 [8] clause 4.2.3.2.2.3. If it is, remove this test.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2.4 LI logging is segregated from non-LI logging
| Editor's Note: This test may be equivalent to the test in TS 33.129-1 [8] clause 4.2.3.2.2.4. If it is, remove this test.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2.5 LI target leak, log leak
| Editor's Note: This test may be equivalent to the test in TS 33.129-1 [8] clause 4.2.3.2.2.5. If it is, remove this test.
Requirement Name: Undetectability by Non-Authorized Parties.
Requirement Reference: TS 33.126 R6.6-30.
Requirement Description: The CSP shall ensure that non-authorized personnel or processes (in... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2.6 LI target leak, config
| Requirement Name: Undetectability by Non-Authorized Parties.
Requirement Reference: TS 33.126 R6.6-30.
Requirement Description: The CSP shall ensure that non-authorized personnel or processes (including automated or Artificial Intelligence based systems) that are part of the service cannot detect that interception is... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.2.7 CPU utilisation observation by VI admin
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.3 Protecting data and information in storage
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.3.1 Introduction
| The tests listed in TS 33.129-1 [8] clause 4.2.3.2.3 shall be applied with the additions and clarifications included in the following sub-clauses.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.4 Protecting data and information in transfer
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.4.1 Introduction
| The tests listed in TS 33.129-1 [8] clause 4.2.3.2.4 shall be applied with the additions and clarifications included in the following sub-clauses.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.2.5 Logging access to personal data
| The tests listed in TS 33.129-1 [8] clause 4.2.3.2.4 shall be applied with the additions and clarifications included in the following sub-clauses.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.3 Protecting availability and integrity
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.3.1 Introduction
| The tests listed in TS 33.129-1 [8] clause 4.2.3.3 shall be applied with the additions and clarifications included in the following sub-clauses.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.4 Authentication and authorization
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.4.1 Introduction
| The tests listed in TS 33.129-1 [8] clause 4.2.3.4 shall be applied with the additions and clarifications included in the following sub-clauses.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.4.2 Logging of failed authentication attempts
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.4.3 No non-LI accounts
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.4.4 Unique credentials
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.4.5 System hardening of VM accounts
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.5 Protecting sessions
| There are no NF-embedded LI function-specific additions to clause 4.2.3.5 of TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.6 Logging
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.6.1 Introduction
| The following addition and clarifications to clause 4.2.3.6 of TS 33.129-1 [8] apply for NF-embedded LI functions.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.6.2 Mandatory log-disabling alarms
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.3.6.3 Loud logs
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.4 Operating Systems
| There are no NF-embedded LI function-specific additions to clause 4.2.4 of TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.5 Web Servers
| There are no NF-embedded LI function-specific additions to clause 4.2.5 of TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.2.6 Network Devices
| There are no NF Embedded LI Function-specific additions to clause 4.2.6 of TS 33.1129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3 Adaptations of hardening requirements and related test cases specific to NF-embedded LI functions
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.1 General
| This clause specifies the NF-embedded LI function-specific adaptations of hardening requirements and related test cases.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.2 Technical baseline
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.2.1 Introduction
| The following additions to clause 4.3.2 in TS 33.129-1 [8] apply for NF-embedded LI functions.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.2.2 Third-party components are up-to-date
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.3 Operating systems
| There are no NF Embedded LI Function-specific additions to clause 4.3.3 in TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.4 Web servers
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.4.1 Introduction
| The following additions to clause 4.3.4 in TS 33.129-1 [8] apply for NF-embedded LI functions.
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.4.2 Only POST allowed (for Xn)
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.4.3 Third-party components are up-to-date
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.5 Network devices
| There are no NF Embedded LI Function-specific additions to clause 4.3.5 in TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.3.6 Network functions in service-based architecture
| There are no NF Embedded LI Function-specific additions to clause 4.3.6 in TS 33.117 [2].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.4 Adaptations of basic vulnerability testing requirements and related test cases specific to NF-embedded LI functions
| |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.4.1 General
| There are no LI specific additions to clause 4.4.1 of TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.4.2 Port Scanning
| There are no LI specific additions to clause 4.4.2 of TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.4.3 Vulnerability scanning
| There are no LI specific additions to clause 4.4.3 of TS 33.129-1 [8].
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 4.4.4 Robustness and fuzz testing
| The test cases under clause 4.4.4 of TS 33.129-1 [8] are applicable to NF-embedded LI functions.
According to clause 4.4.4 of TS 33.117 [2], the transport protocols available on the interfaces providing IP-based protocols need to be robustness tested. Following TCP/IP layer model and considering all the protocols over... |
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 5 Additional Tests
| Editor's Note: This clause will contain tests that are not directly traceable to TS 33.126 requirements
|
fe4e1c5a6f6b77970023a159fb0f020c | 33.129-2 | 5.1 COMMON New Requirement Test Name
|
Annex <A> (normative):
<Normative annex for a Technical Specification>
Start each annex on a new page.
Annexes are labelled A, B, C, etc. and designated either "normative" or "informative" depending on their content.
Normative annexes only to appear in Technical Specifications. Use style "Heading 8".
Annex <... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 1 Scope
| The present document contains objectives, requirements and test cases that are specific to the Lawful Interception (LI) elements of a 3GPP network.
The present document refers to TS 33.117 [2] and formulates specific adaptions of the requirements and test cases given there, as well as specifying additional requirement... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 2 References
| Editor's Note: 1) English vs American spelling (e.g. "artefacts" vs "artifacts"), 2) full stops in lists.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number... |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 3 Definitions of terms, symbols and abbreviations
| |
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
|
a8e35547135823fb19e74805f967dfe3 | 33.129-1 | 3.2 Symbols
| Void.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.