Communication network device, lawful interception system and lawful interception method

Abstract

A communications network device (100) hosting a Lawful Interception, LI, Management Function, ADMF, the communications network device comprising an interface circuit (102), a processor (104), and a memory (106) containing instructions (110) executable by the processor whereby the communications network device (100) is operable to: send an X1 request message to a Network Element, NE, to receive an X1 request message from the processor; the X1 request message is configured to request the NE to send state information of a field of an X1 GetAllDetail Response message to the LI ADMF (Advanced Dimethyl Formamide); and receiving an X1 response message including the requested state information from the NE.

Description

Technical Field

[0001] The present invention relates to a communication network device hosting a lawful interception management function (LI) ADMF, a communication network device hosting a network element (NE), a LI system in a communication network and a LI method. Background Art

[0002] The X1 interface is the Lawful Interception LI interface inside the Communication Service Provider CSP for management tasks. The X1 interface is defined in ETSI TS103 221-1 (e.g. v1.11.1): "Lawful Interception (LI); Part 1: Internal Network Interface X1 for Lawful Interception". The X1 interface is based on the communication between two entities, the CSP Administration Function (ADMF) and the Network Element NE implementing the interception. The X1 reference model is shown in Figure 1. A task is a continuous instance of interception performed at a single NE for a set of LI target identifiers identified by an X1 identifier, starting with an activation command and ending with a deactivation command or a termination failure.

[0003] LI standard solutions for fifth generation (5G) and later communication networks are required to use new ETSI standard (internal X and external H) interfaces. ETSI TS103 221-1 specifies the following requests from ADMF to network element NE and responses from NE in section 6.4:

[0004] GetTaskDetails: Request details of a single task

[0005] GetDestinationDetails: Request details for a single destination

[0006] GetNEStatus: Request the status of the NE itself

[0007] GetAllDetails: Requests details of all tasks, destinations, and the status of the NE itself

[0008] ListAllDetails: Requests the XIDs of all tasks and the DIDs of all destinations

[0009] GetAllDetails enables ADMF to obtain detailed information about the task status and event information that occurred during the task life cycle for each active task.

[0010] More and more ADMF systems support lawful interception in 5G using the ETSI TS103 221-1 X1 standard interface. Historically, among the LI ADMF functions, Audit & Synchronization is one of the most important functions, as it allows the ADMF to regularly check the consistency between the LI target list present in the NE and the LI target list present in the ADMF itself, and take action on any mismatch. ETSI TS103 221-1 provides the ADMF with a GetAllDetails request on X1 to implement the audit.

[0011] Since the current audit process can take a long time, it does not allow for frequent checks to enforce the completeness of the target list throughout the network. In the case of complex and large networks, a complete audit can take hours, so it cannot be used to determine possible discrepancies in the shortest possible time required by national regulations and customers. In addition, the current audit process requires a lot of computing resources, which affects the performance of the entire LI system. Summary of the invention

[0012] The aim is to achieve improved speed and performance of the Audit & Synchronization function of the Lawful Interception LI Management Function ADMF.

[0013] A first aspect provides a communication network device hosting a lawful interception LI management function ADMF. The communication network device comprises an interface circuit, a processor and a memory. The memory contains instructions executable by the processor, whereby the communication network device is operable to send an X1 request message to a network element NE and receive an X1 response message from the NE. The X1 request message is configured to request the NE to send status information of a field of an X1GetAllDetailsResponse message to the LI ADMF. The X1 response message from the NE includes the requested status information.

[0014] Therefore, the X1 request functionality is improved so that Audit & Sync within the LI system can only obtain necessary information. The ADMF hosted by the communication network can advantageously obtain status information about fields that would otherwise have to be provided in the GetAllDetailsResponse along with additional non-required information. This can enable more concise and faster retrieval of required information during Audit & Sync within the LI system, avoiding the use of X1 GetAllDetailsResponse. This can reduce the overall computational footprint and improve the performance of the LI system.

[0015] In an embodiment, the X1 request message is configured to request the NE to send the LI ADMF status information of a single field of an X1 GetAllDetailsResponse message. The ADMF hosted by the communication network is advantageously able to obtain status information about a single field, which would otherwise have to be provided in a GetAllDetailsResponse along with additional non-required information. This can enable a more concise and faster retrieval of required information during the Audit & Synchronization process within the LI system, avoiding the use of an X1 GetAllDetailsResponse. This can reduce the overall computational footprint and improve the performance of the LI system.

[0016] In an embodiment, the X1 request message is configured to request the NE to send the LI ADMF status information of the ListOfTaskResponseDetails field of the X1GetAllDetailsResponse message. The communication network device can enable the LI ADMF to retrieve information about LI tasks active on the LI system, avoiding the use of the X1 GetAllDetailsResponse that will return additional non-needed information.

[0017] In an embodiment, the X1 request message is configured to request the NE to send TaskDetails of all tasks related to the NE's LI target list. The communication network device may enable the LI ADMF to retrieve the LI target list from the NE without using an X1 GetAllDetailsResponse which would return additional non-required information.

[0018] In an embodiment, the X1 request message is a GetAllTaskDetails request message. The communication network device advantageously operates using a new, more specific X1 request message. The GetAllTaskDetails request message enables the ADMF to retrieve all task details currently active on the NE.

[0019] In an embodiment, the X1 request message is configured to request the NE to send the LI ADMF status information of the ListOfDestinationResponseDetails field of the X1GetAllDetailsResponse message. The communication network device may enable the LI ADMF to retrieve information about the LI destinations active on the LI system, avoiding the use of the X1 GetAllDetailsResponse which would return additional unneeded information.

[0020] In an embodiment, the X1 request message is configured to request the NE to send DestinationDetails of all destinations associated with the NE's LI target list. The communication network device may enable the LIADMF to retrieve LI destination information from the NE without using an X1GetAllDetailsResponse which would return additional non-required information.

[0021] In an embodiment, the X1 request message is a GetAllDestinationDetails request message. The communication network device advantageously operates using a new, more specific X1 request message. The GetAllDestinationDetails request message enables the ADMF to retrieve all destination details currently active on the NE.

[0022] In an embodiment, the X1 request message is an X1 GetAllDetailsRequest message including a request parameter configured to request the NE to send status information with fewer fields than all fields of an X1GetAllDetailsResponse message to the LI ADMF. The communication network device advantageously operates using a modified version of the existing GetAllDetailsRequest message, which will cause the NE to return status information with fewer fields than in a standard full GetAllDetailsResponse. This can achieve a more concise and faster provision of required information during the audit & synchronization process within the LI system, avoiding the use of X1 GetAllDetailsResponse. This can reduce the overall computational footprint and improve the performance of the LI system.

[0023] In an embodiment, the request parameter is configured to request the NE to send status information of a single field of an X1GetAllDetailsResponse message to the LI ADMF.

[0024] In an embodiment, the request parameter is configured to request the NE to send status information of a ListOfTaskResponseDetails field of an X1GetAllDetailsResponse message to the LI ADMF.

[0025] In an embodiment, the request parameter is configured to request the NE to send status information of a ListOfDestinationResponseDetails field of an X1GetAllDetailsResponse message to the LI ADMF.

[0026] Corresponding embodiments and advantages also apply to the LI system and method described below.

[0027] A second aspect provides a communication network device hosting a network element NE. The communication network device comprises an interface circuit, a processor and a memory. The memory comprises instructions executable by the processor, whereby the communication network device is operable to receive an X1 request message from a lawful interception LI management function ADMF. The X1 request message is configured to request the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LI ADMF. The communication network device is also operable to obtain the status information from a data storage of the NE, and to send an X1 response message including the status information to the LI ADMF.

[0028] Thus, the X1 request functionality is improved so that Audit & Sync within the LI system can obtain only necessary information. The NE hosted by the communication network is advantageously operable to provide status information about fields that would otherwise have to be provided in a GetAllDetailsResponse along with additional non-required information. This can enable a more concise and faster provision of required information during Audit & Sync within the LI system, avoiding the use of an X1 GetAllDetailsResponse. This can reduce the overall computational footprint and improve the performance of the LI system.

[0029] In an embodiment, the X1 request message is configured to request the NE to send the LI ADMF status information of a single field of an X1 GetAllDetailsResponse message. The NE hosted by the communication network is advantageously operable to provide status information about a single field that would otherwise have to be provided in a GetAllDetailsResponse along with additional non-required information. This can enable a more concise and faster provision of required information during the Audit & Synchronization process within the LI system, avoiding the use of an X1 GetAllDetailsResponse. This can reduce the overall computational footprint and improve the performance of the LI system.

[0030] In an embodiment, the X1 request message is configured to request the NE to send the LI ADMF status information of the ListOfTaskResponseDetails field of an X1GetAllDetailsResponse message. The communication network device is advantageously operable to cause the NE to provide information about LI tasks active on the LI system, avoiding the use of an X1 GetAllDetailsResponse that returns additional unneeded information.

[0031] In an embodiment, the X1 request message is configured to request the NE to send TaskDetails of all tasks associated with the NE's LI target list. The communication network device is advantageously operable to cause the NE to respond to a specific request to provide the LI target list to the LI ADMF without using an X1GetAllDetailsResponse that returns additional non-required information.

[0032] In an embodiment, the X1 request message is a GetAllTaskDetails request message and the X1 response message is a GetAllTaskDetails response message. The communication network device is advantageously operable to cause the NE to respond to a new, more specific X1 request message. The GetAllTaskDetails request message advantageously causes the NE to provide only the details of all tasks currently active on the NE.

[0033] In an embodiment, the X1 request message is configured to request the NE to send the LI ADMF status information of the ListOfDestinationResponseDetails field of an X1GetAllDetailsResponse message. The communication network device is advantageously operable to cause the NE to provide information about LI destinations active on the LI system, avoiding the use of an X1 GetAllDetailsResponse that returns additional unneeded information.

[0034] In an embodiment, the X1 request message is configured to request the NE to send DestinationDetails of all destinations associated with the NE's LI target list. The communications network device is advantageously operable to cause the NE to provide LI destination information from the NE without using an X1GetAllDetailsResponse which returns additional non-required information.

[0035] In an embodiment, the X1 request message is a GetAllDestinationDetails request message and the X1 response message is a GetAllDestinationDetails response message. The communication network equipment is advantageously operable to cause the NE to respond to a new, more specific X1 request message. The GetAllDestinationDetails request message enables the ADMF to retrieve all destination details currently active on the NE.

[0036] In an embodiment, the X1 request message is an X1 GetAllDetailsRequest message including a request parameter configured to request the NE to send status information with fewer fields than all fields of an X1 GetAllDetailsResponse message to the LI ADMF. The communication network device is advantageously operable to cause the NE to respond to a modified version of an existing GetAllDetailsRequest message, which will cause the NE to return status information with fewer fields than in a standard full GetAllDetailsResponse. This can enable a more concise and faster provision of required information during the audit & synchronization process within the LI system, avoiding the use of an X1 GetAllDetailsResponse. This can reduce the overall computational footprint and improve the performance of the LI system.

[0037] In an embodiment, the request parameter is configured to request the NE to send the status information of a single field of the X1GetAllDetailsResponse message to the LI ADMF. This can achieve a more concise and faster provision of the required information during the audit & synchronization process within the LI system, avoiding the use of X1 GetAllDetailsResponse. This can reduce the overall computing footprint and improve the performance of the LI system.

[0038] In an embodiment, the request parameter is configured to request the NE to send the status information of the ListOfTaskResponseDetails field of an X1GetAllDetailsResponse message to the LI ADMF. The X1 response message is a GetAllTaskDetails response message. The communication network device is advantageously operable to cause the NE to respond to a modified version of an existing GetAllDetailsRequest message, which will cause the NE to return a list of LI tasks of the NE, rather than a standard full GetAllDetailsResponse.

[0039] In an embodiment, the request parameter is configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of an X1GetAllDetailsResponse message to the LI ADMF. The X1 response message is a GetAllDestinationDetails response message. The communication network device is advantageously operable to cause the NE to respond to a modified version of an existing GetAllDetailsRequest message, which will cause the NE to return a list of destinations of the NE, rather than a standard full GetAllDetailsResponse.

[0040] Corresponding embodiments and advantages also apply to the LI system and method described below.

[0041] A third aspect provides a lawful interception LI system 300, which includes a first communication network device hosting a lawful interception LI management function ADMF, and at least one second communication network device 200 hosting a network element NE. The first communication network device includes a first interface circuit, a first processor, and a first memory. The first memory contains instructions executable by the first processor, whereby the first communication network device is operable to send an X1 request message to the NE, and to receive an X1 response message from the NE. The X1 request message is configured to request the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LI ADMF. The X1 response message from the NE includes the requested status information. The second communication network device includes a second interface circuit, a second processor, and a second memory. The second memory contains instructions executable by the second processor, whereby the second communication network device is operable to receive the X1 request message from the LI ADMF. The X1 request message is configured to request the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LI ADMF. The communication network device is further operable to retrieve the state information from a data store of the NE, and to send an X1 response message including the state information to the LI ADMF.

[0042] A fourth aspect provides a method for lawful interception of LI in a communication network. The method includes the following operations at a LI management function ADMF: sending an X1 request message to a network element NE. The X1 request message is configured to request the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LI ADMF. The method also includes the following operations at a network element NE: receiving the X1 request message from the LI ADMF, obtaining the status information from a data storage of the NE, and sending an X1 response message including the status information to the LI ADMF. The method also includes the following operations at the LI ADMF: receiving the X1 response message including the requested status information from the NE.

[0043] A fifth aspect provides a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the steps of the above-mentioned method of lawful interception in a communication network.

[0044] Embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] FIG1 is a block diagram showing a prior art lawful interception LI system;

[0046] Figure 2 is a block diagram illustrating an embodiment of a communication network device hosting a LI management function ADMF;

[0047] Figure 3 is a block diagram illustrating an embodiment of a communication network device hosting a network element NE;

[0048] Figure 4 is a block diagram illustrating an embodiment of a LI system;

[0049] Figure 5 is a flow chart illustrating an embodiment of the method steps; and

[0050] Figures 6 to 9 is a signaling diagram illustrating the exchange of signals in an embodiment of the method steps. DETAILED DESCRIPTION

[0051] The same reference numerals will be used for corresponding features in the different embodiments.

[0052] refer to Figure 2, an embodiment provides a communication network device 100 hosting a lawful interception LI management function ADMF. The communication network device 100 includes an interface circuit 102, a processor 104, and a memory 106. The memory 106 contains instructions 110 executable by the processor 104, whereby the communication network device 100 is operable to send an X1 request message to a network element NE, and receive an X1 response message from the NE. The X1 request message is configured to request the NE to send status information of a field of an X1GetAllDetailsResponse message to the LI ADMF. The X1 response message from the NE includes the requested status information.

[0053] The standard X1GetAllDetailsResponse message is defined in Table 31 of Section 6.4.5.1 of ETSI TS103 221-1 (eg, v1.11.1) as including the following fields: NEStatusDetails; ListOfTaskResponseDetails; and ListOfDestinationResponseDetails.

[0054] In an embodiment, the X1 request message is configured to request the NE to send status information of a single field of an X1GetAllDetailsResponse message to the LI ADMF.

[0055] In an embodiment, the X1 request message is configured to request the NE to send status information of the ListOfTaskResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF.

[0056] In an embodiment, the X1 request message is configured to request the NE to send TaskDetails of all tasks related to the NE's LI target list.

[0057] In an embodiment, the X1 request message is a GetAllTaskDetails request message. The ADMF may use the GetAllTaskDetails request to retrieve all details of the LI tasks currently active on the NE (i.e., tasks that have been previously activated by the NE) from the NE, as defined in Section 6.2.1.2 ("TaskDetails") of ETSI TS103 221-1 (e.g., v1.11.1).

[0058] The GetAllTaskDetails request message has a standard X1 message details structure as defined in Table 1 of Section 6.1 of ETSI TS103 221-1 (eg, v1.11.1). In addition to indicating the information in Table 1, the GetAllTaskDetails request shall also indicate the type of request being made. No additional fields are required.

[0059] In an embodiment, the X1 request message is configured to request the NE to send status information of the ListOfDestinationResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF.

[0060] In an embodiment, the X1 request message is configured to request the NE to send the DestinationDetails of all destinations associated with the NE's LI target list.

[0061] In an embodiment, the X1 request message is a GetAllDestinationDetails request message. The ADMF may use the GetAllDestinationDetails request to retrieve from the NE all details of the destinations currently active at the NE (i.e., destinations that have been previously activated by the NE), as defined in Section 6.3.1.2 ("Destinationdetails") of ETSI TS103 221-1 (e.g., v1.11.1).

[0062] The GetAllDestinationDetails request message has a standard X1 message details structure as defined in Table 1 of Section 6.1 of ETSI TS103 221-1 (eg, v1.11.1). In addition to indicating the information in Table 1, the GetAllDestinationDetails request shall also indicate the type of request being made. No additional fields are required.

[0063] In an embodiment, the X1 request message is an X1 GetAllDetailsRequest message including a request parameter configured to request the NE to send status information having fewer fields than all fields of an X1 GetAllDetailsResponse message to the LI ADMF.

[0064] The standard X1GetAllDetailsResponse message is defined in Table 31 of Section 6.4.5.1 of ETSI TS103 221-1 (eg, v1.11.1) as including the following fields: NEStatusDetails; ListOfTaskResponseDetails; and ListOfDestinationResponseDetails. The request parameters may be configured to request the NE to send status information for one or both of these fields.

[0065] In an embodiment, the request parameter is configured to request the NE to send status information of a single field of the X1GetAllDetailsResponse message to the LI ADMF.

[0066] In an embodiment, the request parameter is configured to request the NE to send status information of the ListOfTaskResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF.

[0067] In an embodiment, the request parameters are configured to request the NE to send TaskDetails of all tasks related to the NE's LI target list.

[0068] In an embodiment, the request parameter is configured to request the NE to send status information of the ListOfDestinationResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF.

[0069] In an embodiment, the request parameters are configured to request the NE to send the DestinationDetails of all destinations associated with the NE's LI target list.

[0070] See also Figure 3 , an embodiment provides a communication network device 200 hosting a network element NE. The communication network device includes an interface circuit 202, a processor 204 and a memory 206. The memory 206 contains instructions 210 executable by the processor 204, whereby the communication network device 200 is operable to receive an X1 request message from a LI ADMF. The X1 request message is configured to request the NE to send status information of a field of an X1 GetAllDetailsResponse message to the LI ADMF. The communication network device 200 is also operable to obtain status information from a data storage of the NE, and to send an X1 response message including the requested status information to the LI ADMF.

[0071] In an embodiment, the X1 request message is configured to request the NE to send status information of a single field of an X1GetAllDetailsResponse message to the LI ADMF.

[0072] In an embodiment, the X1 request message is configured to request the NE to send status information of the ListOfTaskResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF.

[0073] In an embodiment, the X1 request message is configured to request the NE to send TaskDetails of all tasks related to the NE's LI target list.

[0074] In an embodiment, the X1 request message is a GetAllTaskDetails request message, as described above, and the X1 response message is a GetAllTaskDetails response message.

[0075] The GetAllTaskDetails response message has a standard X1 message details structure as defined in Table 1 of Section 6.1 of ETSI TS103 221-1 (e.g., v1.11.1). In addition to including the information in Table 1, the GetAllTaskDetails response shall also include the ListOfTaskDetails field as defined in the following table "GetAllTaskDetailsResponse":

[0076] Table: GetAllTaskDetailsResponse

[0077]

[0078] As defined in Section 6.2.1.1 and Section 6.2.1.2 of ETSI TS103 221-1, TaskDetails are target and intercept details. The TaskDetails structure is defined in Table 4 of ETSI TS103 221-1:

[0079] Table 4: TaskDetails

[0080]

[0081] X2 is an interface for sending intercepted signaling, and X3 is an interface for sending intercepted content. Both X2 and X3 are specified in ETSI TS103 221-2 (eg, v1.5.1).

[0082] In an embodiment, the X1 request message is configured to request the NE to send status information of the ListOfDestinationResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF.

[0083] In an embodiment, the X1 request message is configured to request the NE to send the DestinationDetails of all destinations associated with the NE's LI target list.

[0084] In an embodiment, the X1 request message is a GetAllDestinationDetails request message, and the X1 response message is a GetAllDestinationDetails response message.

[0085] The GetAllDestinationDetails response message has a standard X1 message details structure as defined in Table 1 of Section 6.1 of ETSI TS103 221-1 (e.g., v1.11.1). In addition to including the information in Table 1, the GetAllDestinationDetails response shall also include the ListOfDestinationDetails field as defined in the following table "GetAllDestinationDetailsResponse":

[0086] Table: GetAllDestinationDetailsResponse

[0087]

[0088] As defined in Section 6.3.1.2 of ETSI TS103 221-1, DestinationDetails relates to the delivery of information from the NE to the destination. Any further onward forwarding of the data is handled by other management, mediation or delivery functions (outside the scope of ETSI TS103 221-1). The DestinationDetails structure is defined in Table 14 of ETSI TS103 221-1:

[0089] Table 14: DestinationDetails

[0090]

[0091] In an embodiment, the X1 request message is an X1 GetAllDetailsRequest message including a request parameter configured to request the NE to send status information having fewer fields than all fields of an X1 GetAllDetailsResponse message to the LI ADMF.

[0092] ETSI TS103 221-1 defines the standard GetAllDetailsRequest in Table 30 of Section 6.4.5.1 as not including request parameters. The X1 GetAllDetailsRequest message of this embodiment is a new version of the standard GetAllDetailsRequest as defined in Table 30A below:

[0093] Table 30A: GetAllDetailsRequest

[0094]

[0095] Table 30B: InfoRequestDetails

[0096]

[0097] Table 30C: TaskStatus

[0098]

[0099] The new GetAllDetailsRequest message request parameters may be configured to include one or both of the InfoRequestDetails, and if the request parameters include the InfoTasksRequestDetails, the request parameters may be further configured to indicate whether the response should include a TaskStatus.

[0100] In an embodiment, the request parameter is configured to request the NE to send the status information of a single field of the X1GetAllDetailsResponse message to the LI ADMF. This can be achieved by configuring the request parameter to include a single field in the fields of Table 30B.

[0101] In an embodiment, the request parameter is configured to request the NE to send the status information of the ListOfTaskResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF. As indicated in Table 30B, this can be achieved by including the request parameter InfoTasksRequestDetails. The X1 response message can be a GetAllTaskDetails response message, as described above.

[0102] In an embodiment, the request parameter is configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the X1GetAllDetailsResponse message to the LI ADMF. As indicated in Table 30B, this can be achieved by including the request parameter InfoDestinationRequestDetails. The X1 response message can be a GetAllDestinationDetails response message, as described above.

[0103] Reference Figure 4 , the embodiment provides a LI system 300, which includes the first communication network device 100 hosting the LI ADMF as described above and at least one second communication network device 200 hosting the network element NE as described above.

[0104] The embodiment provides a method 400 for LI in a communication network, such as Figure 5 As shown. The method comprises the following operations. At the LI ADMF, an X1 request message is sent 402 to a network element NE. The X1 request message is configured to request the NE to send the status information of the fields of the X1 GetAllDetailsResponse message to the LIADMF. At the NE, the X1 request message is received 404 from the LI ADMF, the requested status information is obtained 406 from the data storage of the NE, and an X1 response message including the requested status information is sent 408 to the LI ADMF. At the LI ADMF, an X1 response message including the requested status information is received 410 from the NE.

[0105] Figure 6 Shows Figure 4 The signaling within the LI system comprises the steps of a method of LI in a communication network according to an embodiment.

[0106] ADMF 100 sends a GetAllTaskDetailsRequest message 502 as described above to NE 200 over the X1 interface. There is currently no LI task activated at the NE, and the NE sends a GetAllTaskDetailsResponse message 504 back to the ADMF, which contains an empty ListOfTaskDetails field:

[0107] ListOfTaskDetails:[]

[0108] Now assume that the ADMF 100 creates a destination with a DID of 4zb6d9f8-ej88-4890-953f-1c48fef91d9c. It then activates several tasks using the X1 interface. The ADMF sends a first ActivateTaskRequest message 506 to the NE, which includes the following task information:

[0109] XID:3ab6d9f8-ed88-4090-953f-1c48fef91d9c

[0110] TargetIdentifiers:[460230123001,460230123002]

[0111] DeliveryType:X2

[0112] ListOfDIDs:[4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0113] NE 200 sends back a first ActivateTaskResponse message 508 to ADMF to confirm the activation of the task. ADMF then sends a second ActivateTaskRequest message 510 to NE, which contains the following task information:

[0114] XID:9hkgd4a1-ed88-4090-953f-1c48fef91d9c

[0115] TargetIdentifiers:[460230123006]

[0116] DeliveryType:X2

[0117] ListOfDIDs:[4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0118] NE 200 sends back a second ActivateTaskResponse message 512 to ADMF to confirm the activation of the task. When ADMF sends a second GetAllTaskDetailsRequest message 514 to NE 200, NE responds back to ADMF with a GetAllTaskDetailsResponse message 516, which contains the following information about the currently active task:

[0119] ListOfTaskDetails:[

[0120] TaskDetails:

[0121] XID:3ab6d9f8-ed88-4090-953f-1c48fef91d9c

[0122] TargetIdentifiers:[460230123001,460230123002]

[0123] DeliveryType:X2

[0124] ListOfDIDs:[4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0125] },

[0126] TaskDetails:

[0127] XID:9hkgd4a1-ed88-4090-953f-1c48fef91d9c

[0128] TargetIdentifiers:[460230123006]

[0129] DeliveryType:X2

[0130] ListOfDIDs:[4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0131] } ]

[0133] Figure 7 Shows Figure 4The signaling within the LI system comprises the steps of a method of LI in a communication network according to an embodiment.

[0134] The ADMF 100 sends a GetAllDestinationDetailsRequest message 602 as described above to the NE 200 over the X1 interface. Currently there is no LI destination created at the NE, the NE sends back a GetAllDestinationDetailsResponse message 604 to the ADMF, which contains an empty ListOfDestinationDetails field:

[0135] ListOfDestinationDetails:[]

[0136] The ADMF 100 then creates two destinations at the NE using the X1 interface. The ADMF sends a first CreateDestinationRequest message 606 to the NE, which includes the following destination information:

[0137] DID:3ab6d9f8-ed88-4090-953f-1c48fef91d9c

[0138] FriendlyName:'First destination'

[0139] DeliveryType:X2

[0140] DeliveryAddress:10.0.30.10:3000

[0141] NE 200 sends back a first ActivateDestinationResponse message 608 to ADMF to confirm the creation of the destination. ADMF then sends a second CreateDestinationRequest message 610 to NE, which contains the following destination information:

[0142] DID:1tf8h2k3-ed88-4090-953f-1c48fef91d9c

[0143] FriendlyName:'Second destination'

[0144] DeliveryType:X2

[0145] DeliveryAddress:10.0.30.60:3000

[0146] NE 200 sends a second ActivateDestinationResponse message 612 back to ADMF to confirm the creation of the destination. When ADMF sends a second GetAllDestinationDetailsRequest message 614 to NE 200, NE responds to ADMF with a GetAllDestinationDetailsResponse message 616, which contains the following information about the currently created destination:

[0147] ListOfDestinationDetails:[

[0148] DestinationDetails:

[0149] DID:3ab6d9f8-ed88-4090-953f-1c48fef91d9c

[0150] FriendlyName:'First destination'

[0151] DeliveryType:X2

[0152] DeliveryAddress:10.0.30.10:3000

[0153] },

[0154] DestinationDetails:

[0155] DID:1tf8h2k3-ed88-4090-953f-1c48fef91d9c

[0156] FriendlyName:'Second destination'

[0157] DeliveryType:X2

[0158] DeliveryAddress:10.0.30.60:3000

[0159] } ]

[0161] Figure 8 Shows Figure 4 The signaling within the LI system comprises the steps of a method of LI in a communication network according to an embodiment.

[0162] ADMF 100 sends GetAllDetailsRequest message 702 as described above to NE 200 over X1 interface. GetAllDetailsRequest message includes request parameter field InfoTasksRequestDetails. NE responds by sending GetAllTaskDetailsResponse message 704 to ADMF, which contains the following information about the currently active task (task that has been previously activated as described above):

[0163] ListOfTaskDetails:[

[0164] TaskDetails:

[0165] XID:3ab6d9f8-ed88-4090-953f-1c48fef91d9c

[0166] TargetIdentifiers:[460230123001,460230123002]

[0167] DeliveryType:X2

[0168] ListOfDIDs:[4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0169] },

[0170] TaskDetails:

[0171] XID:9hkgd4a1-ed88-4090-953f-1c48fef91d9c

[0172] TargetIdentifiers:[460230123006]

[0173] DeliveryType:X2

[0174] ListOfDIDs:[4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0175] } ]

[0177] Fig. 9 Shows Figure 4 The signaling within the LI system comprises the steps of a method of LI in a communication network according to an embodiment.

[0178] ADMF 100 sends the GetAllDetailsRequest message 802 as described above to NE 200 on the X1 interface. The GetAllDetailsRequest message includes a request parameter field InfoDestinationRequestDetails. NE responds to ADMF with a GetAllDestinationDetailsResponse message 804, which includes the following information about the currently created destination (the destination previously created as described above):

[0179] ListOfDestinationDetails:[

[0180] DestinationDetails:

[0181] DID:3ab6d9f8-ed88-4090-953f-1c48fef91d9c

[0182] FriendlyName:'First destination'

[0183] DeliveryType:X2

[0184] DeliveryAddress:10.0.30.10:3000

[0185] },

[0186] DestinationDetails:

[0187] DID:1tf8h2k3-ed88-4090-953f-1c48fef91d9c

[0188] FriendlyName:'Second destination'

[0189] DeliveryType:X2

[0190] DeliveryAddress:10.0.30.60:3000

[0191] } ]

[0193] An embodiment provides a computer program 108 comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the steps of the method 400 .

[0194] An embodiment provides a computer program 208 comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the steps of the method 400 .

Claims

1. A communication network device (100) hosting a lawful interception management function (LI) ADMF, the communication network device comprising an interface circuit (102), a processor (104) and a memory (106), the memory containing instructions (110) executable by the processor, whereby the communication network device (100) is operable to: - sending an X1 request message to a network element NE, wherein the X1 request message is configured to request the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LIADMF; and - receiving an X1 response message from the NE including the requested status information.

2. The communication network device according to claim 1, wherein: The X1 request message is configured to request the NE to send status information of a single field of an X1 GetAllDetailsResponse message to the LI ADMF.

3. The communication network device according to claim 2, wherein: The X1 request message is configured to request the NE to send status information of a ListOfTaskResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF.

4. The communication network device according to claim 3, wherein: The X1 request message is configured to request the NE to send TaskDetails of all tasks associated with the NE's LI target list.

5. The communication network device according to claim 4, wherein: The X1 request message is a GetAllTaskDetails request message.

6. The communication network device according to claim 2, wherein: The X1 request message is configured to request the NE to send status information of a ListOfDestinationResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF.

7. The communication network device according to claim 6, wherein: The X1 request message is configured to request the NE to send DestinationDetails of all destinations associated with the NE's LI target list.

8. The communication network device according to claim 7, wherein: The X1 request message is a GetAllDestinationDetails request message.

9. The communication network device according to claim 1, wherein: The X1 request message is an X1GetAllDetailsRequest message including a request parameter, and the request parameter is configured to request the NE to send status information having fewer fields than all fields of an X1GetAllDetailsResponse message to the LI ADMF.

10. The communication network device according to claim 9, wherein: The request parameter is configured to request the NE to send status information of a single field of an X1 GetAllDetailsResponse message to the LI ADMF.

11. The communication network device according to claim 10, wherein: The request parameter is configured to request the NE to send status information of a ListOfTaskResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF, and wherein the X1 response message is a GetAllTaskDetails response message.

12. The communication network device according to claim 10, wherein: The request parameter is configured to request the NE to send status information of a ListOfDestinationResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF, and wherein the X1 response message is a GetAllDestinationDetails response message.

13. A communication network device (200) hosting a network element (NE), the communication network device comprising an interface circuit (202), a processor (204) and a memory (206), the memory containing instructions (210) executable by the processor, whereby the communication network device (200) is operable to: - receiving an X1 request message from a Lawful Interception LI Management Function ADMF, the X1 request message being configured to request the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LI ADMF; - obtaining said state information from a data store of said NE; and - Sending an X1 response message including the status information to the LI ADMF.

14. The communication network device according to claim 13, wherein: The X1 request message is configured to request the NE to send status information of a single field of an X1 GetAllDetailsResponse message to the LI ADMF.

15. The communication network device according to claim 14, wherein: The X1 request message is configured to request the NE to send status information of a ListOfTaskResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF.

16. The communication network device according to claim 15, wherein: The X1 request message is configured to request the NE to send TaskDetails of all tasks associated with the NE's LI target list.

17. The communication network device according to claim 16, wherein: The X1 request message is a GetAllTaskDetails request message, and the X1 response message is a GetAllTaskDetails response message.

18. The communication network device according to claim 14, wherein: The X1 request message is configured to request the NE to send status information of a ListOfDestinationResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF.

19. The communication network device according to claim 18, wherein: The X1 request message is configured to request the NE to send DestinationDetails of all destinations associated with the NE's LI target list.

20. The communication network device according to claim 9, wherein: The X1 request message is a GetAllDestinationDetails request message, and the X1 response message is a GetAllDestinationDetails response message.

21. The communication network device according to claim 13, wherein: The X1 request message is an X1GetAllDetailsRequest message including a request parameter, and the request parameter is configured to request the NE to send status information having fewer fields than all fields of an X1GetAllDetailsResponse message to the LI ADMF.

22. The communication network device according to claim 21, wherein: The request parameter is configured to request the NE to send status information of a single field of an X1 GetAllDetailsResponse message to the LI ADMF.

23. The communication network device according to claim 22, wherein: The request parameter is configured to request the NE to send status information of a ListOfTaskResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF, and wherein the X1 response message is a GetAllTaskDetails response message.

24. The communication network device according to claim 22, wherein: The request parameter is configured to request the NE to send status information of a ListOfDestinationResponseDetails field of an X1 GetAllDetailsResponse message to the LI ADMF, and wherein the X1 response message is a GetAllDestinationDetails response message.

25. A lawful interception (LI) system (300), comprising: A first communication network device (100) hosting a Lawful Interception (LI) Management Function (ADMF) according to any one of claims 1 to 12; as well as At least one second communication network device (200) hosting a network element NE according to any one of claims 13 to 24.

26. A method (400) for lawful interception (LI) in a communication network, the method comprising the following operations: At the LI management function ADMF: - sending (402) an X1 request message to a network element NE, the X1 request message being configured to request the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LIADMF; At the network element NE: - receiving (404) the X1 request message from the LI ADMF; - retrieving (406) said state information from a data store of said NE; and - sending (408) an X1 response message including the status information to the LI ADMF; and At the LI ADMF: - receiving (410) said X1 response message including the requested status information from said NE.

27. A computer program (108, 208) comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to claim 26.

Images