hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 3 Definition of terms, symbols and abbreviations | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 3.1 Terms | For the purposes of the present document, the following terms apply: base64url: base64 encoding using the URL- and filename-safe character set as defined in IETF RFC 4648 [i.13] Section 5, without trailing padding per IETF RFC 4648 [i.13], Section 3.2 NOTE See also IETF RFC 7515 [29], Appendix C. Communications Service... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 3.2 Symbols | Void. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Access Provider API Application Programming Interface APN Access Point Name ASN Abstract Syntax Notation CC Content of Communication CGI Cell Global ID CIDR Classless InterDomain Routing CSP Communication Service Provider CSPID Communicatio... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 4 Structure and model | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 4.1 Structure of the standard | The present document defines an interface and data structures that can be used to enable electronic warrant and tasking information to be exchanged. The processes for creating, approving and implementing a warrant are national matters. The present document does not attempt to dictate or define these processes, but prov... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 4.2 Structure of the present document | Clause 5 defines how messages are exchanged in the messaging protocol. National Processes Data definitions for Warrant / Tasking information Messaging protocol Transport and transport security Physical/network infrastructure Defined in the present document Not defined in the present document ETSI ETSI TS 103 120 V1.22.... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 4.3 Reference model | The present document defines an interface between two participants. Figure 4.2: Reference model for WI interface The process of approving or enacting a warrant will often involve more than two participants. Multi-party or multi-step interactions can, by national agreement, be composed of multiple two-party interactions... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 5 Message Exchange | HI-1 defines two roles in an HI-1 communication: • The Sender generates a Request Message and transmits it. • The Receiver receives the Request Message, processes it, and returns a Response Message to the Sender. HI-1 message exchange therefore follows a simple Request-Response pattern between Sender and Receiver. Figu... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6 Message Structure | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.1 Overview | The high-level structure for HI-1 Request and Response messages is shown in figure 6.1. Figure 6.1: High-level message structure Sender Receiver Request Message Response Message Message Header Request Payload Action Request GET / CREATE / UPDATE / LIST Object Identifier Object Action Request … Action Request Top level ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.2 MessageHeader | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.2.1 Overview | Every HI-1 Message shall contain a MessageHeader structure that is the same for all messages and contains basic routing and identification information. If a Receiver receives a message containing a MessageHeader that does not follow the format and rules given in this clause, the Receiver shall reject the entire message... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.2.2 Structure | Table 6.1 shows the structure of every valid MessageHeader within an HI-1 message. Table 6.1: MessageHeader Field Format Description M/C/O SenderIdentifier EndpointID (see clause 6.2.4 for details) Nationally unique identifier and country code, sufficient to uniquely identify the Sender node in the message exchange. Se... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.2.3 Version | The Version structure indicates the version of the present document that should be used to interpret this message, as well as identifying the relevant national profile version that should be used. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 21 Table 6.2: Version Field Format Description M/C/O ETSIVersion ShortString (see ET... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.2.4 EndpointID | An EndpointID is used to provide a nationally unique identifier for a Sender or Receiver. Table 6.3: EndpointID Field Format Description M/C/O CountryCode ISOCountryCode (see ETSI TS 103 280 [7], clause 6.28) giving 3166-1 alpha-2 code Two-letter country code for the country. The reserved Country Code XX shall be used ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.2.5 Transaction Identifiers | The Transaction Identifier is a UUID in IETF RFC 9562 [3] canonical form used within a MessageHeader that uniquely identifies a particular HI-1 message exchange between a particular Sender and Receiver. As such, the Transaction Identifier is unique for a pair of Request and Response messages. Senders are responsible fo... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.3 Message Payload | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.3.1 Overview | Every HI-1 Message shall contain a Message Payload structure. A Request Message shall contain a Request Payload, while a Response message shall contain a Response payload. For a definition of Request and Response messages, see clause 5. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.3.2 Request Payload | A Request Payload contains the information sent from a Sender to Receiver. It consists of a collection of Action Requests (see clause 6.4.2). To improve processing efficiency and responsiveness, it is recommended that Action Requests in a Request Payload be limited to a single related set of objects, e.g. an Authorisat... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.3.3 Response Payload | A Response Payload contains information sent back from a Receiver to a Sender, in response to a Request Message. The result of processing multiple Action Requests in a given Request message shall be as if they were processed in order of Action Identifier (see clause 6.4.4). On receiving an Action Unsuccessful response,... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4 Action Request and Responses | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.1 Overview | Clause 6.4 defines a set of verbs to aid the two parties in creating, updating, exchanging and reporting on the HI-1 Objects. It does not dictate business processes that vary nationally. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.2 Action Requests | Each Action Request in the Request Payload shall be assigned an Action Identifier (see clause 6.4.4). Each Action Request appears in ascending order of the Action Identifier. An Action Request shall be one of the following "verbs". ETSI ETSI TS 103 120 V1.22.1 (2026-03) 23 Table 6.4: Action Request types Verb Descripti... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.3 Action Responses | A response message sent from a Receiver to a Sender describes the legibility of the Request message received. An Action Response is generated for each Action Request provided in a Request, providing the Request Message as a whole could be understood. Each Action Response contains an Action Identifier that correlates wi... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.4 Action Identifiers | Action Identifiers are used in Message Payloads, within Action Requests and Action Responses. The Action Identifier correlates an Action Request and Action Response between a given Sender and Receiver. Action Identifiers are generated by the Sender. The Action Identifier shall be a zero-based integer counter that is un... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.5 GET | A GET Request represents a request for the Receiver to return a particular HI-1 Object. A GET Request shall have the following parameters. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 24 Table 6.6: GET Request fields Field Format Description M/C/O Identifier ObjectIdentifier (see clause 7.1.2) Uniquely identifies the HI-1 Ob... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.6 CREATE | A CREATE Request represents a request for the Receiver to create a new HI-1 Object. A CREATE Request shall have the following parameters. Table 6.8: CREATE Request fields Field Format Description M/C/O HI1Object HI1Object (see clause 7.1) Representation of the HI-1 Object to be created by the Receiver. M The Receiver s... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.7 UPDATE | An UPDATE Request represents a request for the Receiver to update values in an existing HI-1 Object. An UPDATE Request shall have the following parameters. Table 6.10: UPDATE Request fields Field Format Description M/C/O HI1Object HI1Object (see clause 7.1) Representation of the HI-1 Object to be updated by the Receive... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.8 LIST | A LIST Request represents a request for the Receiver to list records of HI-1 Object identifiers that the Sender is permitted to have knowledge of, optionally depending on the type requested. Although no business processes are defined in the present document, the Receiver is responsible for listing only the identifiers ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.9 Action Unsuccessful Information | The Receiver shall respond to unsuccessful requests with an Action Unsuccessful Information structure with the following parameters. Table 6.15: Action Unsuccessful Information fields Field Format Description M/C/O ErrorCode Integer Integer code specifying the type of error. M ErrorInformation LongString (see ETSI TS 1... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.10 DELIVER | A DELIVER Request represents a mechanism to deliver information in response to a lawful request represented by another HI-1 Object, for example where a LEA creates an LDTaskObject and the CSP discloses data by sending one or more DeliveryObject(s). A DELIVER Request shall have the following parameters. Table 6.16: DELI... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.11 GETCSPCONFIG | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.11.1 Overview | A GETCSPCONFIG Request represents a request to retrieve information about the capabilities of a CSP. It allows querying the dictionaries supported by the CSP, the workflow endpoints supported by the CSP, the permitted formats for targets, and the services or products that can be requested for LI, LD, or LP for a given ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.11.2 TargetFormatTypeDefinitions | The TargetFormatTypeDefinitions defines the FormatType values (see clauses 8.2.6.3 and 8.3.5.4) owned by this CSP. TargetFormatTypeDefinitions has the following structure. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 29 Table 6.19: TargetFormatTypeDefinitions Field Format Description M/C/O FormatOwner ShortString (see ETSI T... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.11.3 TargetingConfiguration | The TargetingConfiguration defines the valid format types for LITask, LDTask, or LPTask Objects sent to the CSP. It also defines the valid services associated with that format type. TargetingConfiguration has the following structure. Table 6.21: TargetingConfiguration Field Format Description M/C/O FormatOwner ShortStr... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.11.4 SupportedLIWorkflowEndpoint | Including a SupportedLIWorkflowEndpoint in the SupportedLIWorkflowEndpoints field indicates that the CSP supports that endpoint. See clause H.5 for LI Workflow Profile Endpoints and their restrictions. The CSP shall specify an entry associated with a given endpoint at most once. The SupportedLIWorkflowEndpoint has the ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.11.5 SupportedLPWorkflowEndpoint | Including a SupportedLPWorkflowEndpoint in the SupportedLPWorkflowEndpoints field indicates that the CSP supports that endpoint. See clause H.6 for LP Workflow Profile Endpoints and their restrictions. The CSP shall specify an entry associated with a given endpoint at most once. The SupportedLPWorkflowEndpoint has the ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 6.4.11.6 SupportedLDWorkflowEndpoint | Including a SupportedLDWorkflowEndpoint in the SupportedLDWorkflowEndpoints field indicates that the CSP supports that endpoint. The CSP shall specify an entry associated with a given endpoint at most once. The SupportedLDWorkflowEndpoint has the following structure. Table 6.26: SupportedLDWorkflowEndpoint Field Format... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7 Data Definitions | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1 HI1Object | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1.1 Overview | HI1Objects represent the current state of a particular national process. The relevant national profile shall specify which fields are required for a particular HI1Object to be valid within the relevant national processes. All HI1Objects have the following top-level structure. Table 7.1: HI1Object Field Format Descripti... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1.2 ObjectIdentifier | An ObjectIdentifier is an identifier that is used to uniquely identify and refer to a particular HI1Object. To follow RESTful principles, an HI1Object should be identified by a persistent identifier to refer to or locate the HI1Object. This identifier is essential to the automated handling and management of the lifecyc... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1.3 Generation | The Generation parameter indicates how many times the HI1Object has been changed or updated. The Receiver shall set the Generation of an HI1Object to 1 when it is created. A Sender shall not specify the Generation as part of a CREATE Request, and a Receiver shall return an Action Unsuccessful Information response if it... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1.4 AssociatedObjects | The AssociatedObjects field gives a list of other HI1Objects which are related or associated in some way with this HI1Object. Examples include TaskObjects associated with an AuthorisationObject or DocumentObjects associated with an AuthorisationObject or TaskObject. Table 7.2: AssociatedObjects Field Format Description... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1.5 LastChanged | The LastChanged field indicates the date and time that the HI1Object was last changed, either as a result of an HI-1 Action, or as the result of local activity at the Receiver (e.g. local operator intervention, or a change of workflow state). This field shall be set by the Receiver when an HI1Object is first created, a... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1.6 NationalHandlingParameters | The NationalHandlingParameters structure is provided to allow the relevant national profile to specify nationally-specific handling information (e.g. routing information or security labelling). The format and use of the NationalHandlingParameters structure shall be defined in the relevant national profile. ETSI ETSI TS... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.1.7 GenericContactDetails | The GenericContactDetails structure gives contact details of a point of contact, role or other entity. The GenericContactDetails structure is described in table 7.2a below. Table 7.2a: GenericContactDetails Field Format Description Name LongString (see ETSI TS 103 280 [7], clause 6.30) Alternate name or other identifie... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2 AuthorisationObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.1 Overview | An AuthorisationObject represents the state of an authorisation - that is, a legal instrument by which legal action is permitted. It has the following fields (following the categories defined in ETSI TR 103 690 [i.1]). Table 7.3: AuthorisationObject Field Format Description Reference AuthorisationReference LongString (... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.2 AuthorisationReference | The AuthorisationReference field provides a nationally defined reference for the Authorisation. This is provided to allow correlation with non-HI1 processes. The format and permissible values for the AuthorisationReference field shall be defined by the relevant national profile. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.3 AuthorisationLegalType | The AuthorisationLegalType field indicates the type and legal basis for the Authorisation. Examples include references to the relevant legal code or statutory purpose. Given as an AuthorisationLegalType DictionaryEntry. The valid set of values for this field is likely to be closely coupled to national legislation. It i... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.4 AuthorisationPriority | The AuthorisationPriority field gives an indication of the priority of the authorisation. Usage is for national agreement. The meaning of a given priority shall be specified by the national profile. The AuthorisationPriority, if used, shall be given as an AuthorisationPriority DictionaryEntry. The AuthorisationPriority... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.5 AuthorisationStatus | The AuthorisationStatus field indicates the current status of the authorisation as determined by the Receiver. A Sender shall not attempt to set the AuthorisationStatus as part of a CREATE or UPDATE Request, and a Receiver shall return an Action Unsuccessful Information response if it attempts to. The Status field prov... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.6 AuthorisationDesiredStatus | The AuthorisationDesiredStatus field indicates the current status of the authorisation as determined by the Sender. Given as an AuthorisationDesiredStatus Dictionary Entry. The AuthorisationDesiredStatus Dictionary is defined in table 7.7 (see annex F for more details on Dictionaries). ETSI ETSI TS 103 120 V1.22.1 (202... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.7 AuthorisationTimespan | The AuthorisationTimespan field gives the period of time for which the authorisation is valid. This may not necessarily be the time that the legal action is active. The timestamps shall include a time-zone specifier. Table 7.8: AuthorisationTimespan Field Format Description StartTime QualifiedDateTime (see ETSI TS 103 ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.8 AuthorisationCSPID | The AuthorisationCSPID field gives a list of globally unique CSP Identifiers that identify the CSPs required to implement the authorisation. In some jurisdictions, authorisations may be required to be specific to an identified CSP. In those cases, this field may become a required field for Authorisation Objects to be v... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.9 AuthorisationCreationTimestamp | The AuthorisationCreationTimestamp field indicates the time that the authorisation was created. The timestamp shall include a time-zone specifier. If necessary, the precise meaning of this field should be clarified by the relevant national profile. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.10 AuthorisationServedTimestamp | The AuthorisationServedTimestamp indicates the time that the authorisation was served on the CSP. The timestamp shall include a timezone specifier. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.11 AuthorisationApprovalDetails | The AuthorisationApprovalDetails field provides details of who approved the Authorisation. See annex E for further details. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 37 |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.12 AuthorisationFlags | The AuthorisationFlags field allows a set of multiple flags to be associated with the Authorisation Object. Each flag is given as an AuthorisationFlag Dictionary Entry. If a flag is present in the Flags field, then the meaning given as part of that flag's definition shall be taken to apply. The AuthorisationFlag Dictio... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.13 AuthorisationJurisdiction | The AuthorisationJurisdiction field indicates the relevant jurisdiction for the Authorisation, given as a human-readable free text field. The presence and precise usage of this field is subject to the relevant profile. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.14 AuthorisationTypeOfCase | Informative for the CSP, to give an indication of the type of case involved. The LEA may choose not to use it or may choose "not specified" if they wish not to provide a classification. Given as an AuthorisationTypeOfCase DictionaryEntry. The present document defines the dictionary shown in table 7.10. Other dictionari... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.15 AuthorisationLegalEntity | The AuthorisationLegalEntity field provides an indication of the specific legal or procedural entity that the Authorisation is being used to seek assistance from. Examples include the specific subsidiary or department of a commercial company. Table 7.11: Void |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.2.16 AuthorisationManualInformation | The AuthorisationManualInformation field provides any additional human-readable information regarding the Authorisation. This field shall only be used if required information cannot be contained in any other field. CSPs and LEAs should be aware that the information carried in this field cannot be guaranteed to be machi... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3 DocumentObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.1 Overview | A DocumentObject represents a particular legal document or instrument related to a given AuthorisationObject or TaskObject. Examples may include the original warrant documentation, or subsequent modification or renewal documents. The DocumentObject has the following fields. Table 7.12: DocumentObject Field Format Descr... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.2 DocumentReference | The DocumentReference field gives a nationally-defined reference for the Document. This is provided to allow correlation with non-electronic processes. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.3 DocumentName | The DocumentName field allows a nationally defined name for the Document to be specified. The permissible values and format of this field shall be specified by the relevant national profile. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.4 DocumentStatus | The DocumentStatus field gives the status of the Document as determined by the Receiver. A Sender shall not attempt to set the DocumentStatus as part of a CREATE or UPDATE Request, and a Receiver shall return an Action Unsuccessful Information response if the Sender attempts to do so. The Status field provides a key me... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.5 DocumentDesiredStatus | The DocumentDesiredStatus field gives the status of the Document as specified by the Sender. Given as a DocumentDesiredStatus Dictionary Entry. The DocumentDesiredStatus Dictionary is defined in table 7.14 (see annex F for more details on Dictionaries). ETSI ETSI TS 103 120 V1.22.1 (2026-03) 40 Table 7.14: DocumentDesi... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.6 DocumentTimespan | The DocumentTimespan field gives the period of time for which the Document is valid. The precise meaning may depend on the type of document being represented. The timestamps shall include a timezone specifier. Table 7.15: DocumentTimespan Field Format Description StartTime QualifiedDateTime (see ETSI TS 103 280 [7], cl... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.7 DocumentType | Indicates the type of document that this Document Object represents. Given as a DocumentType DictionaryEntry. The DocumentType Dictionary is defined below (see annex F for more details on Dictionaries). Since each jurisdiction is likely to have its own particular set of documents, it is expected that most national prof... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.8 DocumentProperties | A list of key-value pairs that define additional properties of the Document in a machine-readable manner. Permissible property types shall be specified in a dictionary defined by the relevant national profile. Table 7.17: DocumentProperty Field Format Description PropertyType Dictionary entry (see below) Type of the pr... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.9 DocumentBody | Binary representation of the original paper documentation (e.g. TIFF or JPEG). Table 7.18: DocumentBody Field Format Description Contents Binary data, represented in base64 encoding Binary representation of the original paper authorisation documentation. ContentType ShortString (see ETSI TS 103 280 [7], clause 6.29) co... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.3.10 DocumentSignature | The DocumentSignature field gives approval details for the Document represented by the Document Object. This may include signature information. The DocumentSignature field is specified using the ApprovalDetails structure. See annex E for more details. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4 NotificationObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4.1 Overview | The NotificationObject is a means for a Receiver to notify a Sender of any change or update to an HI1Object or set of HI1Objects that was not due to a direct HI-1 Action from the Sender. Such changes may occur for a number of reasons, for example local user interaction at the Receiver. The use of NotificationObjects is... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4.2 NotificationDetails | The NotificationDetails field shall carry human-readable information regarding the nature of the notification (for example, a summary of any changes, or the reason for the notification). A Receiver shall ignore any attempt by a Sender to UPDATE the value of the Notification details field. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4.3 NotificationType | The NotificationType field indicates the type of Notification being given. It is given as a NotificationType Dictionary Entry. The NotificationType Dictionary is defined in table 7.20 (see annex F for more details on Dictionaries). Since the list of notification types is tightly coupled to national processes and workfl... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4.4 NewNotification | The NewNotification flag is used to indicate whether the notification is new, and therefore whether it should be returned in a query for New Notifications (see clause 6.4.8). When a Receiver creates a new NotificationObject, the NewNotification flag shall be set to True. The NewNotification Flag may be set to False, th... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4.5 NotificationTimestamp | The NotificationTimestamp field shall be set by the Receiver to the time at which the notification event occurred. The Receiver shall ignore any attempt by a Sender to UPDATE the value of the NotificationTimestamp field. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4.6 NationalNotificationParameters | The use and definition of the NationalNotificationParameters structure is for national agreement. See annex G. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.4.7 StatusOfAssociatedObjects | The StatusOfAssociatedObjects field can be used to inform the Sender of an HI1Object or set of HI1Objects that the status of these objects has changed to value given by this field to avoid that Sender has to send a GET Message to retrieve the new status value. The values are defined in the dictionaries for the status v... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.5 TrafficPolicyObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.5.1 Overview | The TrafficPolicyObject represents a policy from an LEA which is to be applied to the intercepted materials as part of an LITaskObject. An LEA may associate multiple TrafficPolicyObjects to an LITaskObject, using the LITaskObject's ListOfTrafficPolicyReferences field (see clauses 8.2.1 and 8.2.13). A change to a traffi... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.5.2 Order | TrafficRuleReferences are considered in ascending order according to the Order field. If all of the criteria listed in the TrafficRuleObject referenced by the ObjectIdentifier field are matched (see clause 7.6.2), then the action described in the referenced TrafficRuleObject's Action field is taken (see clause 7.6.3) a... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6 TrafficRuleObject | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.1 Overview | Table 7.23: TrafficRuleObject Field Format Description Reference M/C/O Criteria List of TrafficCriteria List of rule criteria all of which shall match for this rule to apply. Clause 7.6.2 M Action TrafficAction Dictionary Entry The action to take with matching criteria. Clause 7.6.3 M Parameters ActionParameters Parame... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2 TrafficCriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.1 Overview | The TrafficCriteria structure defines whether a TrafficRule applies to a particular piece of intercepted traffic or not. If multiple TrafficCriteria are given, they are logically ANDed together - that is, the intercepted traffic shall match all of them in order for the TrafficRule to be considered matching. |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.2 IPPolicyCriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.2.1 Overview | IPPolicyCriteria is one type of TrafficCriteria. The IPPolicyCriteria structure defines a set of IP based criteria which can be used to determine if a rule applies. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 45 Table 7.24: IPPolicyCriteria Field Format Description Reference M/C/O IPProtocol IPProtocol IP Protocol of the tr... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.2.2 BothDirections | The presence of the BothDirections field indicates that packets matching in both directions match the criteria. If the BothDirections field is present, the packet is considered a match if either: • all of the SourceIPRange, SourcePortRange, DestinationIPRange, and DestinationPortRange IPPolicyCriteria that are present ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.3 MobileAccessPolicyCriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.3.1 Overview | MobileAccessPolicyCriteria defines a criterion based on the APN or DNN of a particular traffic flow. Table 7.24a: MobileAccessPolicyCriteria Field Format Description Reference M/C/O APN APN Network Identifier Match traffic sent to or from the specified APN. Presentation format specified in 3GPP TS 23.003 [i.6], clause ... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.4 EthernetPolicyCriteria | |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 7.6.2.4.1 Overview | EthernetPolicyCriteria is one type of TrafficCriteria. The EthernetPolicyCriteria structure defines a set of Ethernet based criteria which can be used to determine if a rule applies. ETSI ETSI TS 103 120 V1.22.1 (2026-03) 46 Table 7.24b: EthernetPolicyCriteria Field Format Description Reference M/C/O SourceMACAddress M... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.