Communication network device, legal tapping system, and legal tapping method

Abstract

A communication network device (100) that hosts a legal interception (LI) management function (ADMF) includes an interface circuit (102), a processor (104), and a memory (106). The memory includes instructions (110) executable by the processor, whereby the communication network device (100) is configured to send an X1 request message to a network element (NE) that requests the NE to send status information of fields of an X1 GetAllDetailsResponse message to the LI ADMF, and to receive from the NE an X1 response message including the requested status information.

Description

Technical Field

[0001] The present invention relates to a communication network device that hosts a Lawful Interception (LI) Administration Function (ADMF). The present invention further relates to a communication network device that hosts a Network Element (NE). The present invention further relates to an LI system and an LI method in a communication network.

Background Art

[0002] The X1 interface is a Lawful Interception (LI) interface within a Communication Service Provider (CSP) for management tasks. The X1 interface is defined in, for example, v1.11.1 of ETSI TS 103 221-1, "Lawful Interception (LI); Part 1: Internal network interface X1 for lawful interception". The X1 interface is based on the communication between two entities, a CSP Administration Function (ADMF) and a Network Element (NE) that performs interception. The X1 reference model is shown in FIG. 1. A task is a continuous instance of interception at a single NE that is executed for a set of LI target identifiers identified by an X1 identifier, starting from an activation command and ending with a deactivation command or a failure.

[0003] In LI standard solutions after the 5th generation (5G) communication network, it is required to use new ETSI standard (Internal X and External H) interfaces. ETSI TS 103 221-1 specifies the following requirements from the ADMF to the Network Element (NE) and the following responses from the NE in Clause 6.4. GetTaskDetails: Requests details of a single task GetDestinationDetails: Requests details of a single destination GetNEStatus: Requests the status of the NE itself GetAllDetails: Requests all details of tasks, destinations, and the status of the NE itself ListAllDetails: Requests the XID of all tasks and the DID of all destinations. GetAllDetails enables the ADMF to obtain, for each active task, detailed information regarding the status of the task and event information that occurred during the task's life cycle.

[0004] An increasing number of ADMF systems support lawful interception in 5G using the X1 standard interface of ETSI TS 103 221-1. Historically, Audit&Synch within the LI ADMF function has been one of the most important as it enables the ADMF to periodically check the consistency between the LI target lists existing in the NE and the ADMF itself and to handle any discrepancies if found. ETSI TS 103 221-1 provides the ADMF with a GetAllDetails request at X1 for performing audits.

[0005] Since the current auditing procedure can take a very long time, it is not possible to perform frequent checks to enforce the consistency of the target list across the network. In the case of complex and large-scale networks, a full audit can take several hours, making it unavailable for determining the likelihood of discrepancies within the minimum time required by national regulations or customers. Furthermore, the current auditing procedure requires a large amount of computing resources and affects the performance of the entire LI system. Summary of the Invention Problems to be Solved by the Invention

[0006] The objective is to enable an improved speed and performance of the Audit&Synch function of the Lawful Interception (LI) Management Function (ADMF). Means for Solving the Problems

[0007] A first aspect provides a communication network device that hosts a legal interception (LI) administrative function (ADMF). The communication network device comprises an interface circuit, a processor, and a memory. The memory has instructions executable by the processor, whereby the communication network device is operative 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 fields of an X1 GetAllDetailsResponse message to the LI ADMF. The X1 response message from the NE includes the requested status information.

[0008] Thereby, the X1 request function evolves such that Audit&Synch within the LI system can obtain only the information that is necessary. The ADMF hosted by the communication network can advantageously obtain status information regarding fields that would otherwise need to be provided within the GetAllDetailsResponse with additional unnecessary information. Thereby, it may be possible to avoid the use of the X1 GetAllDetailsResponse and obtain the information necessary in the Audit&Synch procedure within the LI system more concisely and quickly. This can reduce the overall computational footprint and improve the performance of the LI system.

[0009] In one embodiment, the X1 request message is configured to request the NE to send the status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF. The ADMF hosted by the communication network can advantageously obtain the status information regarding the single field that would otherwise need to be provided within the GetAllDetailsResponse along with additional unnecessary information. This can avoid the use of the X1 GetAllDetailsResponse and enable the LI system to obtain the information required in the Audit&Synch procedure more concisely and quickly. This can reduce the overall computational footprint and improve the performance of the LI system.

[0010] In one embodiment, the X1 request message is configured to request the NE to send the status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF. The communication network device can avoid the use of the X1 GetAllDetailsResponse that returns additional unnecessary information and enable the LI ADMF to obtain information regarding the LI tasks active in the LI system.

[0011] In one embodiment, the X1 request message is configured to request the NE to send the TaskDetails of all tasks related to the LI target list of the NE. The communication network device can enable the LI ADMF to obtain the LI target list from the NE without using the X1 GetAllDetailsResponse that returns additional unnecessary information.

[0012] In one embodiment, the X1 request message is a GetAllTaskDetails request message. The communication network device advantageously operates using the new, more specific X1 request message. With the GetAllTaskDetails request message, the ADMF can obtain all the details of the tasks currently active at the NE.

[0013] In one embodiment, the X1 request message is configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF. The communication network device can avoid using the X1 GetAllDetailsResponse that returns additional unnecessary information, enabling the LI ADMF to obtain information about the LI destinations active in the LI system.

[0014] In one embodiment, the X1 request message is configured to request the NE to send the DestinationDetails of all destinations related to the LI target list of the NE. The communication network device can enable the LI ADMF to obtain LI destination information from the NE without using the X1 GetAllDetailsResponse that returns additional unnecessary information.

[0015] In one embodiment, the X1 request message is a GetAllDestinationDetails request message. The communication network device advantageously operates using the new, more specific X1 request message. With the GetAllDestinationDetails request message, the ADMF can obtain all the destination details currently active at the NE.

[0016] In one embodiment, the X1 request message is an X1 GetAllDetailsRequest message that includes request parameters configured to request the NE to send status information of fewer fields than all the fields of the X1 GetAllDetailsResponse message to the LI ADMF. The communication network device advantageously operates using a modified version of the existing GetAllDetailsRequest message, thereby causing the NE to return status information of fewer fields than a standard full GetAllDetailsResponse to the NE. This can avoid the use of the X1 GetAllDetailsResponse and provide the information required in the Audit&Synch procedure within the LI system more concisely and quickly. This can reduce the overall computational footprint and improve the performance of the LI system.

[0017] In one embodiment, the request parameters are configured to request the NE to send status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0018] In one embodiment, the request parameters are configured to request the NE to send status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0019] In one embodiment, the request parameters are configured to request the NE to send status information of the ListOfDestinationResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0020] The corresponding embodiments and advantages also apply to the LI systems and methods described below.

[0021] The second aspect provides a communication network device that hosts a network element (NE). The communication network device includes an interface circuit, a processor, and a memory. The memory has instructions executable by the processor, whereby the communication network device operates to receive an X1 request message from a lawful interception (LI) administrative 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 further operates to obtain status information from a data store of the NE and send an X1 response message including the status information to the LI ADMF.

[0022] Thereby, the X1 request function evolves, and as a result, Audit&Synch within the LI system can obtain only the necessary information. The NE hosted by the communication network is advantageously operable to provide status information regarding fields that would otherwise need to be provided in the GetAllDetailsResponse with additional unnecessary information. This can avoid the use of the X1 GetAllDetailsResponse and enable a more concise and rapid provision of the information required in the Audit&Synch procedure within the LI system. This can reduce the overall computational footprint and improve the performance of the LI system.

[0023] In one embodiment, the X1 request message is configured to request the NE to send the status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF. The NE hosted by the communication network is advantageously operable to provide the status information regarding a single field that would otherwise need to be provided within the GetAllDetailsResponse along with additional unnecessary information. This can avoid the use of the X1 GetAllDetailsResponse and enable a more concise and rapid provision of the information required in the Audit&Synch procedure within the LI system. This can reduce the overall computational footprint and improve the performance of the LI system.

[0024] In one embodiment, the X1 request message is configured to request the NE to send the status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF. The communication network device is advantageously operable to avoid the use of the X1 GetAllDetailsResponse that returns additional unnecessary information and cause the NE to provide information regarding active LI tasks on the LI system.

[0025] In one embodiment, the X1 request message is configured to request the NE to send the TaskDetails of all tasks related to the LI target list of the NE. The communication network device is advantageously operable to cause the NE to respond to a specific request for providing the LI target list to the LI ADMF without using the X1 GetAllDetailsResponse that returns additional unnecessary information.

[0026] In one 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 the newly more specific X1 request message. The GetAllTaskDetails request message advantageously causes the NE to provide only all of the details of the tasks currently active at the NE.

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

[0028] In one embodiment, the X1 request message is configured to request the NE to send the DestinationDetails of all destinations related to the NE's LI target list. The communication network device is advantageously operable to cause the NE to provide LI destination information from the NE without using an X1 GetAllDetailsResponse that returns additional unnecessary information.

[0029] In one embodiment, the X1 request message is a GetAllDestinationDetails request message, and the X1 response message is a GetAllDestinationDetails response message. The communication network device is advantageously operable to cause the NE to respond to the newly more specific X1 request message. With the GetAllDestinationDetails request message, the ADMF can obtain all of the currently active destination details at the NE.

[0030] In one embodiment, the X1 request message is an X1 GetAllDetailsRequest message that includes request parameters configured to request the NE to send status information of fewer fields than all the fields of the X1 GetAllDetailsResponse message to the LI ADMF. The communication network device is advantageously operable to cause the NE to respond with a modified version of the existing GetAllDetailsRequest message, thereby causing the NE to return status information of fewer fields than a standard full GetAllDetailsResponse. This can avoid the use of the X1 GetAllDetailsResponse and enable a more concise and rapid provision of the information required in the Audit&Synch procedure within the LI system. This can reduce the overall computational footprint and improve the performance of the LI system.

[0031] In one embodiment, the request parameters are configured to request the NE to send status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF. This can avoid the use of the X1 GetAllDetailsResponse and enable a more concise and rapid provision of the information required in the Audit&Synch procedure within the LI system. This can reduce the overall computational footprint and improve the performance of the LI system.

[0032] In one embodiment, the request parameter is configured to request the NE to send the status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF. The X1 response message is the GetAllTaskDetails response message. The communication network device is advantageously operable to cause the NE to respond to a modified version of the existing GetAllDetailsRequest message, thereby causing the NE to return the NE's LI task list to the NE instead of the standard full GetAllDetailsResponse.

[0033] In one embodiment, the request parameter is configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF. The X1 response message is the GetAllDestinationDetails response message. The communication network device is advantageously operable to cause the NE to respond to a modified version of the existing GetAllDetailsRequest message, thereby causing the NE to return the NE's destination list to the NE instead of the standard full GetAllDetailsResponse.

[0034] The corresponding embodiments and advantages also apply to the LI systems and methods described below.

[0035] A third aspect provides a lawfully intercepted (LI) system 300 comprising a first communication network device hosting a lawfully intercepted (LI) management function (ADMF), and at least one second communication network device 200 hosting a network element (NE). The first communication network device comprises a first interface circuit, a first processor, and a first memory. The first memory has instructions executable by the first processor, whereby the first communication network device is operative to send an X1 request message to the 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 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 comprises a second interface circuit, a second processor, and a second memory. The second memory has instructions executable by the second processor, whereby the second communication network device is operative 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 operative to obtain the status information from a data store of the NE and send an X1 response message including the status information to the LI ADMF.

[0036] The fourth aspect provides a legal interception (LI) method in a communication network. The method includes an operation of transmitting an X1 request message from a LI management function (ADMF) to a network element (NE). The X1 request message is configured to request the NE to transmit status information of fields of an X1 GetAllDetailsResponse message to the LI ADMF. The method further includes, in the network element (NE), operations of receiving the X1 request message from the LI ADMF, obtaining status information from a data store of the NE, and transmitting an X1 response message including the status information to the LI ADMF. The method further includes an operation of receiving, at the LI ADMF, the X1 response message including the requested status information from the NE.

[0037] The fifth aspect provides a computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform the steps of the above-described legal interception method in a communication network.

[0038] Embodiments of the present invention will be described by way of example only with reference to the accompanying drawings.

Brief Description of the Drawings

[0039]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

[0040] The same reference numbers are used for corresponding functions in different embodiments.

[0041] Referring to FIG. 2, an embodiment provides a communication network device 100 that hosts a Lawful Interception (LI) Administration and Management Function (ADMF). The communication network device 100 includes an interface circuit 102, a processor 104, and a memory 106. The memory 106 has instructions 110 executable by the processor 104, whereby the communication network device 100 is operative 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 the status information of the fields of the X1 GetAllDetailsResponse message to the LI ADMF. The X1 response message from the NE includes the requested status information.

[0042] The standard X1 GetAllDetailsResponse message is defined in clause 6.4.5.1, table 31 of ETSI TS 103 221-1, for example v1.11.1, to include the following fields: NEStatusDetails, ListOfTaskResponseDetails, and ListOfDestinationResponseDetails.

[0043] In one embodiment, the X1 request message is configured to request the NE to send the status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0044] In one embodiment, the X1 request message is configured to request the NE to send the status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

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

[0046] In one embodiment, the X1 request message is a GetAllTaskDetails request message. As defined in, for example, clause 6.2.1.2 ("TaskDetails") of ETSI TS 103 221-1 v1.11.1, the ADMF can use the GetAllTaskDetails request to obtain from the NE all details of the LI tasks currently active at the NE, i.e., the tasks previously activated by the NE.

[0047] The GetAllTaskDetails request message has the standard X1 message detail structure defined in, for example, clause 6.1, table 1 of ETSI TS 103 221-1 v1.11.1. In addition to the information in table 1, the GetAllTaskDetails request must indicate the type of request being made. No additional fields are required.

[0048] In one embodiment, the X1 request message is configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0049] In one embodiment, the X1 request message is configured to request the NE to send the DestinationDetails of all destinations related to the LI target list of the NE.

[0050] In one embodiment, the X1 request message is a GetAllDestinationDetails request message. As defined in, for example, clause 6.3.1.2 ("DestinationDetails") of ETSI TS 103 221-1, v1.11.1, the ADMF can use the GetAllDestinationDetails request to obtain from the NE all details of the destinations that are currently active at the NE, i.e., the destinations that have been previously activated by the NE.

[0051] The GetAllDestinationDetails request message has the standard X1 message detailed structure defined in, for example, clause 6.1, Table 1 of ETSI TS 103 221-1, v1.11.1. In addition to the information in Table 1, the GetAllDestinationDetails request must indicate the type of request being made. No additional fields are required.

[0052] In one embodiment, the X1 request message is an X1 GetAllDetailsRequest message that includes request parameters configured to request the NE to send to the LI ADMF the status information of fewer fields than all the fields of the X1 GetAllDetailsResponse message.

[0053] The standard X1 GetAllDetailsResponse message is defined in clause 6.4.5.1, table 31 of ETSI TS 103 221-1, for example v1.11.1, to include the following fields: NEStatusDetails; ListOfTaskResponseDetails; and ListOfDestinationResponseDetails. The request parameters can be configured to request the NE to send the status information of one or two of these fields.

[0054] In one embodiment, the request parameters are configured to request the NE to send the status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0055] In one embodiment, the request parameters are configured to request the NE to send the status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0056] In one embodiment, the request parameters are configured to request the NE to send the TaskDetails of all tasks related to the LI target list of the NE.

[0057] In one embodiment, the request parameters are configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0058] In one embodiment, the request parameters are configured to request the NE to send the DestinationDetails of all destinations related to the LI target list of the NE.

[0059] Referring to FIG. 3, an embodiment provides a communication network device 200 that hosts a network element (NE). The communication network device includes an interface circuit 202, a processor 204, and a memory 206. The memory 206 has instructions 210 executable by the processor 204, whereby the communication network device 200 is operative to receive an X1 request message from the LI ADMF. The X1 request message is configured to request the NE to send status information of fields of the X1 GetAllDetailsResponse message to the LI ADMF. The communication network device 200 is further operative to obtain status information from the data store of the NE and send an X1 response message including the requested status information to the LI ADMF.

[0060] In one embodiment, the X1 request message is configured to request the NE to send status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0061] In one embodiment, the X1 request message is configured to request the NE to send status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0062] In one embodiment, the X1 request message is configured to request the NE to send TaskDetails of all tasks related to the LI target list of the NE to the LI ADMF.

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

[0064] The GetAllTaskDetails response message has the standard X1 message detailed structure defined in, for example, clause 6.1, Table 1 of ETSI TS 103 221-1, version v1.11.1. In addition to the information in Table 1, the GetAllTaskDetails response shall include the ListOfTaskDetails field defined in the following table "GetAllTaskDetailsResponse".

[0065] [Table 1]

[0066] As defined in clauses 6.2.1.1 and 6.2.1.2 of ETSI TS 103 221-1, TaskDetails are the details of the target and interception. The TaskDetails structure is defined in Table 4 of ETSI TS 103 221-1.

[0067] [Table 2]

[0068] X2 is the interface used to send intercepted signaling, and X3 is the interface used to send intercepted content. Both X2 and X3 are specified in, for example, version v1.5.1 of ETSI TS 103 221-2.

[0069] In one embodiment, the X1 request message is configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF.

[0070] In one embodiment, the X1 request message is configured to request the NE to send the DestinationDetails of all destinations related to the NE's LI target list.

[0071] In one embodiment, the X1 request message is a GetAllDestinationDetails request message, and the X1 response message is a GetAllDestinationDetails response message.

[0072] The GetAllDestinationDetails response message has the standard X1 message detailed structure defined in Clause 6.1, Table 1 of ETSI TS 103 221-1, for example v1.11.1. In addition to the information in Table 1, the GetAllDestinationDetails response shall include the ListOfDestinationDetails field defined in the following Table "GetAllDestinationDetailsResponse".

[0073] [Table 3]

[0074] As defined in Clause 6.3.1.2 of ETSI TS 103 221-1, DestinationDetails is related to the delivery of information from the NE to the destination. Further transfer of the data is processed by other management, mediation, or delivery functions (outside the scope of ETSI TS 103 221-1). The DestinationDetails structure is defined in Table 14 of ETSI TS 103 221-1.

[0075] [Table 4]

[0076] In one embodiment, the X1 request message is an X1 GetAllDetailsRequest message that includes request parameters configured to request the LI ADMF to send status information of fields fewer than all fields of the X1 GetAllDetailsResponse message to the NE.

[0077] ETSI TS 103 221-1 defines a standard GetAllDetailsRequest without request parameters in clause 6.4.5.1, table 30. The X1 GetAllDetailsRequest message of this embodiment is a new version of this standard GetAllDetailsRequest as defined in table 30A below.

[0078]

Table 5

[0079]

Table 6

[0080]

Table 7

[0081] The request parameters of the new GetAllDetailsRequest message can be configured to include one or two InfoRequestDetails. When the request parameters include InfoTasksRequestDetails, the request parameters can be further configured to indicate whether the response must include TaskStatus.

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

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

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

[0085] Referring to FIG. 4, an embodiment provides an LI system 300 including a first communication network device 100 that hosts the LI ADMF as described above, and at least one second communication network device 200 that hosts a network element (NE) as described above.

[0086] Embodiments provide a method 400 for LI in a communication network as shown in FIG. 5. The method includes 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 LI ADMF. At the NE, the X1 request message is received (404) from the LI ADMF, the requested status information is obtained (406) from the NE's data store, 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.

[0087] FIG. 6 shows the signaling within the LI system of FIG. 4 and includes steps of a method for LI in a communication network according to an embodiment.

[0088] As described above, the ADMF 100 sends a GetAllTaskDetailsRequest message 502 to the NE 200 on the X1 interface. Since there are no currently activated LI tasks at the NE, the NE returns a GetAllTaskDetailsResponse message 504 including an empty ListOfTaskDetails field: ListOfTaskDetails: [] to the ADMF.

[0089] Here, assume that the ADMF 100 creates a destination for DID 4zb6d9f8 - ej88 - 4890 - 953f - 1c48fef91d9c. Next, the ADMF 100 activates several tasks using the X1 interface. The ADMF sends a first ActivateTaskRequest message 506 including the following task information to the NE. XID: 3ab6d9f8 - ed88 - 4090 - 953f - 1c48fef91d9c TargetIdentifiers: [460230123001, 460230123002] DeliveryType: X2 ListOfDIDs: [4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0090] NE200 returns the first ActivateTaskResponse message 508 that confirms the activation of the task to the ADMF. Next, the ADMF sends a second ActivateTaskRequest message 510 containing the following task information to the NE. XID: 9hkgd4a1-ed88-4090-953f-1c48fef91d9c TargetIdentifiers: [460230123006] DeliveryType: X2 ListOfDIDs: [4zb6d9f8-ej88-4890-953f-1c48fef91d9c]

[0091] NE200 returns the second ActivateTaskResponse message 512 that confirms the activation of the task to the ADMF. When the ADMF sends the second GetAllTaskDetailsRequest message 514 to NE200, the NE responds by returning a GetAllTaskDetailsResponse message 516 containing the following information about the currently active tasks to the ADMF. ListOfTaskDetails: TaskDetails: { XID: 3ab6d9f8-ed88-4090-953f-1c48fef91d9c TargetIdentifiers: [460230123001, 460230123002] DeliveryType: X2 ListOfDIDs: [4zb6d9f8-ej88-4890-953f-1c48fef91d9c]}, TaskDetails: { XID: 9hkgd4a1-ed88-4090-953f-1c48fef91d9c TargetIdentifiers: [460230123006] DeliveryType: X2 ListOfDIDs: [4zb6d9f8-ej88-4890-953f-1c48fef91d9c] }

[0092] Figure 7 shows the signaling within the LI system of FIG. 4 and includes steps of the method of LI in a communication network according to an embodiment.

[0093] As described above, the ADMF100 sends the GetAllDestinationDetailsRequest message 602 to the NE200 on the X1 interface. Since there is no currently created LI destination in the NE, the NE returns an empty ListOfDestinationDetails field: ListOfDestinationDetails:[] in the GetAllDestinationDetailsResponse message 604 to the ADMF.

[0094] Next, the ADMF100 creates two destinations in the NE using the X1 interface. The ADMF sends the first CreateDestinationRequest message 606 containing the following destination information to the NE. DID: 3ab6d9f8-ed88-4090-953f-1c48fef91d9c FriendlyName: 'First destination' DeliveryType: X2 DeliveryAddress: 10.0.30.10:3000

[0095] ​NE200 returns the first ActivateDestinationResponse message 608 that verifies the creation of the destination to the ADMF. Next, the ADMF sends the second CreateDestinationRequest message 610 containing the following destination information to the NE. DID: 1tf8h2k3-ed88-4090-953f-1c48fef91d9c FriendlyName: 'Second destination' DeliveryType: X2 DeliveryAddress: 10.0.30.60:3000

[0096] NE200 returns the second ActivateDestinationResponse message 612 that verifies the creation of the destination to the ADMF. When the ADMF sends the second GetAllDestinationDetailsRequest message 614 to NE200, the NE responds by returning a GetAllDestinationDetailsResponse message 616 containing the following information about the currently created destinations to the ADMF. ListOfDestinationDetails: DestinationDetails: { DID: 3ab6d9f8-ed88-4090-953f-1c48fef91d9c FriendlyName: 'First destination' DeliveryType: X2 DeliveryAddress: 10.0.30.10:3000 }, DestinationDetails: { DID: 1tf8h2k3-ed88-4090-953f-1c48fef91d9c FriendlyName: 'Second destination' DeliveryType: X2 DeliveryAddress: 10.0.30.60:3000 }

[0097] Figure 8 shows the signaling within the LI system of FIG. 4 and includes steps of the method of LI in a communication network according to an embodiment.

[0098] As described above, the ADMF100 sends the GetAllDetailsRequest message 702 to the NE200 on the X1 interface. The GetAllDetailsRequest message includes the request parameter field InfoTasksRequestDetails. The NE responds by sending the GetAllTaskDetailsResponse message 704 including the following information about the currently active tasks that were previously activated to the ADMF, as described above. ListOfTaskDetails: TaskDetails: { XID: 3ab6d9f8-ed88-4090-953f-1c48fef91d9c TargetIdentifiers: [460230123001, 460230123002] DeliveryType: X2 ListOfDIDs: [4zb6d9f8-ej88-4890-953f-1c48fef91d9c] }, TaskDetails: { XID: 9hkgd4a1-ed88-4090-953f-1c48fef91d9c TargetIdentifiers: [460230123006] DeliveryType: X2 ListOfDIDs: [4zb6d9f8-ej88-4890-953f-1c48fef91d9c] }

[0099] ​​FIG. 9 shows the signaling within the LI system of FIG. 4 and includes steps of the LI method in a communication network according to an embodiment.

[0100] As described above, the ADMF100 sends the GetAllDetailsRequest message 802 to the NE200 on the X1 interface. The GetAllDetailsRequest message includes the request parameter field InfoDestinationRequestDetails. The NE responds by sending the GetAllDestinationDetailsResponse message 804 including the following information about the previously created and currently created destinations to the ADMF as described above. ListOfDestinationDetails: DestinationDetails: { DID: 3ab6d9f8-ed88-4090-953f-1c48fef91d9c FriendlyName: 'First destination' DeliveryType: X2 DeliveryAddress: 10.0.30.10:3000 }, DestinationDetails: { DID: 1tf8h2k3-ed88-4090-953f-1c48fef91d9c FriendlyName: 'Second destination' DeliveryType: X2 DeliveryAddress: 10.0.30.60:3000 }

[0101] When executed by at least one processor, the embodiment provides a computer program 108 including instructions for causing the at least one processor to execute the steps of method 400.

[0102] ​The embodiment provides a computer program 208 that, when executed by at least one processor, includes instructions that cause the at least one processor to perform the steps of method 400.

Claims

1. A communication network device (100) that hosts a legal interception (LI) management function (ADMF), the communication network device comprising an interface circuit (102), a processor (104), and a memory (106), the memory including instructions (110) executable by the processor, whereby the communication network device (100) is configured to: - Send an X1 request message to the network element (NE) requesting the NE to send status information of a field of an X1 GetAllDetailsResponse message to the LI ADMF; - Receive an X1 response message from the NE including the requested status information. A communication network device that operates as described above.

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 the 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 related to the LI target list of the NE.

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, The X1 request message is a communication network device configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the 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 the DestinationDetails of all destinations related to the LI target list of the NE, a communication network device.

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

9. The communication network device according to claim 1, wherein the X1 request message is an X1 GetAllDetailsRequest message including request parameters configured to request the NE to send the status information of fields fewer than all of the fields of the X1 GetAllDetailsResponse message to the LI ADMF.

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

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

12. The communication network device according to claim 10, The request parameter is configured to request the NE to send the status information of the ListOfDestinationResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF, and the X1 response message is a GetAllDestinationDetails response message, a communication network device. A communication network device (200) that hosts a network element (NE), the communication network device comprising an interface circuit (202), a processor (204), and a memory (206), the memory including instructions (210) executable by the processor, whereby the communication network device (200) - Receiving from a lawful interception (LI) management function (ADMF) an X1 request message configured to request the NE to send the status information of a field of the X1 GetAllDetailsResponse message to the LI ADMF; - Obtaining the status information from a data store of the NE; - Sending an X1 response message including the status information to the LI ADMF; operates to perform. A communication network device. The communication network device according to claim 13, wherein the X1 request message is configured to request the NE to send the status information of a single field of the X1 GetAllDetailsResponse message to the LI ADMF. A communication network device. The communication network device according to claim 14, wherein the X1 request message is configured to request the NE to send the status information of the ListOfTaskResponseDetails field of the X1 GetAllDetailsResponse message to the LI ADMF. A communication network device. The communication network device according to claim 15, wherein the X1 request message is configured to request the NE to send the TaskDetails of all tasks related to the LI target list of the NE. A communication network device. ​ ​ ​ ​ ​ 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, the communication network device.

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

19. The communication network device according to claim 18, wherein the X1 request message is configured to request the NE to transmit DestinationDetails of all destinations related to the LI target list of the NE, the communication network device.

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, the communication network device.

21. The communication network device according to claim 13, wherein the X1 request message is an X1 GetAllDetailsRequest message including request parameters configured to request the NE to transmit status information of fields fewer than all of the fields of the X1 GetAllDetailsResponse message to the LI ADMF, the communication network device.

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

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

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

25. A lawful interception (LI) system (300), comprising A first communication network device (100) that hosts a lawful interception (LI) management function (ADMF) according to any one of claims 1 to 12, and At least one second communication network device (200) that hosts a network element (NE) according to any one of claims 13 to 24, and An LI system comprising the same.

26. A lawful interception (LI) method (400) in a communication network, comprising In the LI management function (ADMF): - Sending (402) to the NE an X1 request message configured to request the NE to send the status information of the fields of the X1 GetAllDetailsResponse message to the LI ADMF, and In the network element (NE): - Receiving (404) the X1 request message from the LI ADMF, and - Obtaining (406) the status information from the data store of the NE, and - Sending (408) an X1 response message including the status information to the LI ADMF, and In the LI ADMF, - Receiving (410) from the NE the X1 response message including the requested status information, and A method including the same.

27. A computer program (108, 208) that, when executed by at least one processor, causes the at least one processor to execute the method according to claim 26.

Images