Enabling compatible destination set delivery types in lawful intercept

Abstract

Methods to enable compatible destination set delivery types to be performed by a Point of Intercept (POI) Function device and a Lawful Intercept Administration Function (LI ADMF) device and associated network nodes that can perform the same are disclosed The method includes receiving (302, 304), from a Lawful Intercept Administration Function, LI ADMF, (102), a request associated with a set of destinations (108), wherein the request comprises an indication of a delivery type of the set of destinations (108). If the DID delivery types of the destinations are compatible with the delivery type of the set of destinations (108), the method includes accepting (306, 308) the request and performing (306) an operation based on the request. If the DID delivery types are not compatible with the delivery type of the set of destinations (108), the method includes providing (310), to the LI ADMF (102), an error message.

Description

ENABLING COMPATIBLE DESTINATION SET DELIVERY TYPES IN LAWFULINTERCEPT Technical Field

[0001] The disclosure relates to methods enabling compatible destination set deliverytypes by Point of Intercept (POI) function devices and Lawful Intercept (LI)Administration Function (ADMF) devices. The disclosure also relates to network nodes configured to perform the same. Background

[0002] The ETSI TS 103 221-1 V1.16.1 (2024-01) standard defines thecommunication protocol between the Point of Intercept (POI) and the Lawful Intercept (LI) Administration Function (ADMF) node.

[0003] According to the clause 5.1.3 the Intercepted traffic is delivered by the NE toa Destination. Each Destination is uniquely identified by a Destination Identifier (DID) and is handled independently from details of the Task. DIDs can optionally be grouped with individual DID preference weightings as part of a Destination Set. Destination Sets specify an action, which defines how DIDs within the Destination Set are used; Destination Sets are uniquely identified by their Generic Object ID, which is referred to as the Destination Set Identifier (DSID) (annex E).

[0004] Each Task is associated with one or more Destinations or Destination Sets.Prior to associating a Task with a given DID or DSID, it is required that a Destination with the DID, or Destination Set with the DSID has already been created (as described in clause 6.3 and annex E).

[0005] The Destination Set is created based on generic object (clause 5.1.4) conceptmanaging general objects (see message definition clause 6.8).

[0006] The DestinationSetDetails Object is defined in clause E.2.2. In particular,when the DestinationSetType included within the DestinationSetDetails is "Redundant”, the POI will use the specified DIDs as a set of redundant end points. For each DID the "Preference" shall be defined within a Destination Set. Preference defines the DIDs order of use with the smallest integer indicating the most preferred DID(s). Should the most preferred DID(s) become unavailable the next preferred and available DID(s) shall be used.

[0007] Figure 1 shows an example of a task associated to a set of destinations or“Destination Sets” 108-1 of type “Redundant” and xIRI sent to the most indicatedpreferred DID (e.g., DID 110-1).

[0008] In Figure 1, the LI ADMF 102 can configure the POI 106 at the NetworkElement 104 with a one or more destination sets 108-1 and / or 108-2. Each of thedestination sets 108-1 or 108-2 can comprise a plurality of destinations 110-1 to 110-4for destination set for destination set 108-1, and destinations 110-5 to 110-8 for destination set 108-2. In the embodiment in Figure 1, the destination set 108-1 has a DestinationSetType (or delivery set type) set to redundant. In Figure 2 as an example, the set of destinations 108-1 has a delivery set type set to duplicate.

[0009] Where the DestinationSetType included within the DestinationSetDetails is"Duplicate", the NE will send copies of intercepted traffic to all DIDs within the set, preference shall not to be included where the DestinationSetDetails is of type "Duplicate.” Summary

[0010] An object of the invention is to prevent configuration errors that arise whenDestination Identity (DID) delivery types are incompatible with each other withindestination sets configured by a Lawful Intercept (LI) Administrative Function (ADMF) ata Point Of Intercept (POI) function device used for LI.

[0011] The present disclosure provides methods to enable compatible destination setdelivery types to be performed by a POI Function device and a LI ADMF device and associated network nodes that can perform the same. A new parameter that identifies a delivery type of the set of destinations can be provided, where destinations of the set of destinations each have respective DID delivery types. If the DID delivery types are compatible with the delivery type of the set of destinations the POI can accept a request from the LI ADMF, and if the DID delivery types are not compatible with the delivery type of the set of destinations, the POI function device can issue an error message. The LI ADMF, when providing a request to the POI function device, can also attempt to ensure that the DID delivery types and the delivery type of the set of destinations are compatible.

[0012] In an embodiment, a method is provided to enable compatible destination setdelivery types to be performed by a POI Function device and a LI ADMF device andassociated network nodes that can perform the same are disclosed. The method includes receiving from the LI ADMF, a request associated with a set of destinations (108), wherein the request comprises an indication of a delivery type of the set ofdestinations. If the DID delivery types or task delivery types of the request of thedestinations are compatible with the delivery type of the set of destinations, the method includes accepting the request and performing an operation based on the request. Ifthe DID delivery types or the task delivery types are not compatible with the deliverytype of the set of destinations, the method includes providing, to the LI ADMF, an error message.

[0013] In an embodiment, the DID delivery types are one of X2Only, X3Only orX2andX3. In another embodiment, the delivery type of the set of destinations is one ofX2Only, X3Only or X2andX3.

[0014] In an embodiment, a destination set type is at least one of Redundant orDuplicate.

[0015] In an embodiment, the request is a CreateObject or ModifyObject to define adestination set, and wherein the indication of the delivery type is a destination set delivery type. In such an embodiment, performing the operation comprises creating or modifying (306) a destination set based on the CreateObject or ModifyObject request.

[0016] In an embodiment the request is an ActivateTask or ModifyTask requestassociated with a task associated with the set of destinations (108), and the indication of the delivery type is a task delivery type. In such an embodiment, performing the operation comprises performing the task based on the ActivateTask or ModifyTask request. In an embodiment, the request is associated with a plurality of sets ofdestinations, and if the delivery type of the task is X2andX3 and the delivery types of afirst set of destinations are X2andX3, and the delivery types a second set of destinations are X2andX3, performing the task.

[0017] In an embodiment, the error message indicates to the LI ADMF (102) thatthere was an invalid combination of delivery type of the set of destinations and DIDdelivery types or delivery type of set of destinations and the task delivery types.

[0018] In an embodiment, a network node is provided that implements a POIfunction device that is configured to enable compatible destination set delivery types. The network node can include processing circuitry configured to cause the network node to perform the methods described above performed by the POI function device.

[0019] In an embodiment, a method is provided for enabling compatible destinationset delivery types performed by a LI ADMF, the method comprising providing, to a Point of Intercept, POI, Function device, a request associated with a set of destinations, wherein the request comprises an indication of a delivery type of the set of destinations, and wherein the set of destinations comprises a plurality of Destination Identities, DIDs, with respective DID delivery types, wherein the DID delivery types are compatible with the delivery type of the set of destinations.

[0020] In an embodiment, the DID delivery types are one of X2Only, X3Only orX2andX3. In another embodiment, the delivery type of the set of destinations is one ofX2Only, X3Only or X2andX3.

[0021] In an embodiment, the destination set type is at least one of Redundant orDuplicate.

[0022] In an embodiment, the request is a CreateObject or ModifyObject to define adestination set, and wherein the indication of the delivery type is a destination set delivery type. In another embodiment, the request is an ActivateTask or ModifyTask request associated with a task associated with the set of destinations, and the indication of the delivery type is a task delivery type.

[0023] In an embodiment, a network node is provided that implements a LI ADMFthat is configured to enable compatible destination set delivery types. The network node can include processing circuitry configured to cause the network node to perform the methods described above performed by the LI ADMF.

[0024] In an embodiment, a computer program is provided that comprisesinstructions which when executed on processing circuitry, cause the processing circuitry to carry out the methods described above. In an embodiment, a carrier containing the computer program is provided wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

[0025] In an embodiment, the methods described above ensure that only compatibleDIDs are grouped together. This prevents the configurations errors that occur when incompatibles DIDs are mistakenly associated. Another advantage provided by the methods described herein is that the consistency related to the Delivery Types is increased, avoiding potential issues in data routing due to delivery types discrepancies. The techniques described herein ensure that all DIDs within a Destination Set havecompatible delivery types. For instance, if the primary DID is for ‘X2Only’, the secondary DID, which acts for example as a fallback, must also be for ‘X2Only’.

[0026] Another advantage is with error handling, in case of any inconsistency, suchas a mismatch in delivery types within a DID lists, the system will reject the request and provide a specific error code and reason. This not only prevents the activation of flawed interception tasks but also enables faster troubleshooting. The proposed enhancement of adding a “DestinationSetDeliveryType” to the ADMF’s protocol contributes to a morerobust, consistent, and efficient LI system with an enhanced error management andreduced computational burden (when processing Intercept Related Information (xIRI)and Content of Communication (xCC) deliveries) leading to reduced energyconsumption. Brief of the

[0027] The accompanying drawing figures incorporated in and forming a part of thisspecification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0028] Figure 1 is a block diagram of an implementation of redundant destination setidentifiers according to some embodiments of the present disclosure;

[0029] Figure 2 is a block diagram of an implementation of duplicate destination setidentifiers according to some embodiments of the present disclosure;

[0030] Figure 3 is a message sequence chart of a method for enabling compatibledestination set delivery types by Point of Intercept (POI) function devices and LawfulIntercept (LI) Administration Function (ADMF) devices according to some embodiments of the present disclosure;

[0031] Figure 4 is a schematic block diagram of a network node according to someembodiments of the present disclosure;

[0032] Figure 5 is a schematic block diagram that illustrates a virtualizedembodiment of the network node of Figure 4 according to some embodiments of the present disclosure; and

[0033] Figure 6 is a schematic block diagram of the network node of Figure 4according to some other embodiments of the present disclosure.Detailed Description

[0034] The embodiments set forth below represent information to enable thoseskilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0035] Network Node: As used herein, a “network node” can be any type ofapparatus / device in a core network or any apparatus / device that implements a corenetwork function. Some examples of a core network node include a computer or serverhost for e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P- GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementingan Access and Mobility Management Function (AMF), a User Plane Function (UPF), aSession Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like. In the following description, when stating that any of these functions, such as Point of Intercept (POI) function device or Lawful Intercept (LI) Administration Function (ADMF) device, perform an action, such as receiving / matching / performing / configuring then it is to be understood that it is in practice the network node / computer / server host / POI function device / LI ADMF device that hosts the POI and ADMF, respectively, that performs the action.

[0036] Note that the description given herein focuses on a Third GenerationPartnership Project (3GPP) cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0037] Note that the description given herein focuses on a 3GPP cellularcommunications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0038] Various problems with the current existing techniques described in thebackground are that when the Lawful Intercept Administration Function (LI ADMF) creates a Destination Set object using the “CreateObjectRequest” message, a list of associated Destination IDs (DIDs) shall be specified. According to the ETSI TS 103221- 1 Annex E2.2 LI ADMF is allowed to include DIDs with discordant delivery type (e.g.: one DID delivery type is X2Only while the other is X3Only.

[0039] The Destination Set identified by a Destination Set Identifier (DSID) (e.g., theidentifier of a set of destinations) can be associated to a Task. It is not clearly indicated by the ETSI TS 103221-1 if and how to verify consistency between the Task DeliveryType and associated Destination Set. In managing a task associated with one or moreDestinationSet, there could be a potential inconsistency between the Task DestinationType and the nature of DIDs inside the DestinationSet. The POI Delivery Function cannot be able to send X2 or X3 samples because no appropriate destinations are associated to the task which Intercept Related Information (xIRI) and Content of Communication (xCC) are part of.

[0040] The proposed solution is to introduce a new parameter “DestinationSetDelivery Type” into DestinationSet structure of ETSI X1, to validate the DestinationSetObject. Additionally, a new ActivateTask / ModifyTask error is introduced. It shall beused when a Task creation is rejected due to an invalid combination of DeliveryTypeand Destination Sets specified.

[0041] Various embodiments disclosed herein provide for a method to enablecompatible destination set delivery types to be performed by a Point of Intercept (POI) Function device and a Lawful Intercept Administration Function (LI ADMF) device and associated network nodes that can perform the same. A new parameter that identifies a delivery type of the set of destinations can be provided, where destinations of the set of destinations each have respective Destination Identity (DID) delivery types. If theDID delivery types are compatible with the delivery type of the set of destinations thePOI can accept a request from the LI ADMF, and if the DID delivery types are not compatible with the delivery type of the set of destinations, the POI function device can issue an error message. The LI ADMF, when providing a request to the POI function device, can also attempt to ensure that the DID delivery types and the delivery type of the set of destinations are compatible.

[0042] In an embodiment, the methods described above ensure that only compatibleDIDs are grouped together. This prevents the configurations errors that occur when incompatibles DIDs are mistakenly associated. Another advantage provided by themethods described herein is that the consistency related to the Delivery Types isincreased, avoiding potential issues in data routing due to delivery types discrepancies. The techniques described herein ensure that all DIDs within a Destination Set have compatible delivery types. For instance, if the primary DID is for ‘X2Only’, the secondary DID, which acts for example as a fallback, must also be for ‘X2Only’.

[0043] Another advantage is with error handling, in case of any inconsistency, suchas a mismatch in delivery types within a DID lists, the system will reject the request and provide a specific error code and reason. This not only prevents the activation of flawed interception tasks but also enables faster troubleshooting. The proposed enhancement of adding a “DestinationSetDeliveryType” to the ADMF’s protocol contributes to a more robust, consistent and efficient LI system with an enhanced error management and reduced computational burden (when processing xIRI and xCC deliveries) leading to reduced energy consumption.

[0044] At clause 5.1.3 of the standard ETSI TS 103 221-1 V1.16.1 (2024-01) it isspecified how to associate a task to one or more destinations as follows: “Each Task is associated with one or more Destinations or Destination Sets. Prior to associating a Task with a given DID or DSID, it is required that a Destination with the DID, or Destination Set with the DSID has already been created (as described in clause 6.3 and annex E).

[0045] The DestinationSetDetails object at clause E2.2 Table.1 is proposed to beupdated adding the following new field: Field Description Format M / O / CStatement of whether to deliver X2 Enumerated DestinationSetDeliveryType and / or X3 to all destinations included invalue - oneM the Destination Set of "X2Only", "X3Only" and "X2andX3"

[0046] Similarly, a new ActivateTask / Modify Task error is proposed to be included atclause 6.7 Table 46.Error code Error Description SuggestedInformation Elements Invalid combination of DeliveryType and 3060 Destination Sets specified

[0047] Likewise, The TS_103_221_DestinationSet.xsd is proposed to be updated asfollows with the new text underlined:<?xml version="1.0" encoding="UTF-8"?><xs:schema xmlns:xs="http: / / www.w3.org / 2001 / XMLSchema" xmlns="http: / / uri.etsi.org / 03221 / X1 / 2017 / 10 / DestinationSet" xmlns:x1="http: / / uri.etsi.org / 03221 / X1 / 2017 / 10"xmlns:etsi103280="http: / / uri.etsi.org / 03280 / common / 2017 / 07" targetNamespace="http: / / uri.etsi.org / 03221 / X1 / 2017 / 10 / DestinationSet" elementFormDefault="qualified" version="1.11.1"> <xs:import namespace="http: / / uri.etsi.org / 03280 / common / 2017 / 07" / ><xs:import namespace="http: / / uri.etsi.org / 03221 / X1 / 2017 / 10" / ><!-- Message containers --><xs:complexType name="DestinationSetDetails"><xs:complexContent> <xs:extension base="x1:GenericObject"><xs:sequence> <xs:element name="friendlyName" type="xs:string" minOccurs="0" / ><xs:element name="listOfAssociatedDIDs" type="ListOfAssociatedDIDs" / <xs:element name="destinationSetDetailsExtension" type="DestinationSetDetailsExtension" minOccurs="0" maxOccurs="unbounded" / ><xs:element name="destinationSetType" type="DestinationSetType" / ><xs:element name="destinationSetdeliveryType" type="DestinationSetDeliveryType" / > < / xs:sequence> < / xs:extension> < / xs:complexContent> < / xs:complexType> <xs:complexType name="ListOfAssociatedDIDs"><xs:sequence> <xs:element name="AssociatedDID" type="AssociatedDID" minOccurs="0" maxOccurs="unbounded" / > < / xs:sequence> < / xs:complexType> <xs:complexType name="AssociatedDID"><xs:sequence> <xs:element name="dId" type="x1:DId" / ><xs:element name="preference" type="xs:integer" / >< / xs:sequence> < / xs:complexType> <xs:complexType name="DestinationSetDetailsExtension"><xs:complexContent> <xs:extension base="x1:Extension" / >< / xs:complexContent> < / xs:complexType> <xs:simpleType name="DestinationSetType"><xs:restriction base="xs:string"><xs:enumeration value="Redundant" / ><xs:enumeration value="Duplicate" / >< / xs:restriction> < / xs:simpleType> <xs:simpleType name=" DestinationSetDeliveryType DeliveryType"> <xs:restriction base="xs:string"> <xs:enumeration value="X2Only" / > <xs:enumeration value="X3Only" / > <xs:enumeration value="X2andX3" / > < / xs:restriction> < / xs:simpleType> < / xs:schema>

[0048] When a CreateObject or ModifyObject for Destination Set is requested, thefollowing business logic should be applied.

[0049] If the DestinationSetDeliveryType (DSDT or also referred to as “delivery typeof the set of destinations” herein) into request is X2Only and all DIDs delivery types areX2Only and / or X2andX3, the request should be accepted. Otherwise, the request shouldnot be accepted and an error code 8500 / 8510 “Invalid combination of Destination setDelivery Type and Destinations specified” should be sent back to the LI ADMF.

[0050] If the DSDT in the request is X3Only and all destinations are X3Only and / orX2andX3, the request should be accepted by the POI function. Otherwise, the requestshould not be accepted and an error code 8500 / 8510 “Invalid combination ofDestination set Delivery Type and Destinations specified” should be sent back.

[0051] When an ActivateTask or ModifyTask is requested with associatedDestinationSet / Destinations into ListOfDIDs, the following business logic should be applied.

[0052] If the Task delivery type in the request X2Only and / or X2andX3 the requestshould be accepted. Otherwise, if the DSDT in the request is X3Only, the request shouldnot be accepted and an error code 3060 “Invalid combination of Delivery Type andDestination Sets specified” should be sent back.

[0053] If the Task delivery type in the request is X3Only and the delivery types of theof the DestinationSets are X3Only and / or X2andX3 the request should be accepted.Otherwise, the request should not be accepted and an error code 3060 “Invalidcombination of Delivery Type and Destination Sets specified” should be sent back.

[0054] If the Task delivery type in the request is X2andX3 and there is at least oneDestinationSet with a delivery type of X2andX3 or at least two DestinationSets with adelivery type of X2Only and X3Only the request should be accepted. Otherwise, therequest should not be accepted and the new error code 3060 “Invalid combination ofDelivery Type and Destination Sets specified” should be sent back.

[0055] To illustrate these embodiments, Figure 3 shows a message sequence chartof a method for enabling compatible destination set delivery types by Point of Intercept(POI) function devices and Lawful Intercept (LI) Administration Function (ADMF) devices according to some embodiments of the present disclosure. It is to beappreciated that the ordering of the steps in the message sequence chart is not limiting,and that different steps can occur in different orders in various embodiments.

[0056] The flowchart at Figure 3 can begin at either step 302 or step 304 where themethod generally includes receiving, from a LI ADMF 102, a request associated with aset of destinations 108 wherein the request comprises an indication of a delivery type ofthe set of destinations 108 (e.g., X2Only, X3Only, X2andX3) and wherein the set ofdestinations 108 comprises a plurality of DIDs 110 with respective DID delivery types (e.g., X2Only, X3Only, X2andX3).

[0057] If the DID delivery types are compatible with the delivery type of the set ofdestinations (e.g., according to the logic described above), the method can include accepting the request and performing an operation based on the request. If the request is a CreateObject or ModifyObject request such as in step 302, POI 106 can create or modify the destination set at 306 based on the CreateObject or ModifyObject request.

[0058] Alternatively, the request can be an ActivateTask or ModifyTask request as instep 304, where the request associated with a task associated with the set of destinations 108, and the indication of the delivery type is a task delivery type. In thatcase, the performing the operation includes performing at step 308 the task based onthe ActivateTask or ModifyTask request.

[0059] In an embodiment, the request is associated with a plurality of sets ofdestinations, and if the delivery type of the task 108 is X2andX3and the DID delivery types of DIDs 110 of a first set of destinations 108-1 are X2andX3, and the DID delivery types of DIDs 110 of a second set of destinations 108-2 are X2andX3, the method includes performing the task at step 308.

[0060] If the DID delivery types are not compatible with the delivery type of the setof destinations 108, at step 310-1, the POI 106 provides an error message to the LI ADMF 102

[0061] If the task delivery types are not compatible with the delivery type of the setof destinations 108, at step 310-2, the POI 106 provides an error message to the LI ADMF 102. The type of error message is determined according to the logic described above. In an embodiment, the error message indicates to the LI ADMF 102 that there was an invalid combination of delivery type and destination sets.

[0062] In an embodiment, the destination set delivery type is at least one ofRedundant or Duplicate.

[0063] Figure 4 is a schematic block diagram of a network node 400 according tosome embodiments of the present disclosure. Optional features are represented bydashed boxes. The network node 400 may be, for example, a network node thatimplements all or part of the functionality of the LI ADMF 102, or POI function device106 as described herein. As illustrated, the network node 400 includes a control system402 that includes one or more processors 404 (e.g., Central Processing Units (CPUs),Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays(FPGAs), and / or the like), memory / computer readable storage medium 406, and anetwork interface 408. The one or more processors 404 are also referred to herein asprocessing circuitry.

[0064] The one or more processors 404 operate to provide one or more functions ofa network node 400 as described herein. In some embodiments, the function(s) areimplemented in one or more computer programs 410 that are stored, e.g., in thecomputer readable storage medium 406 and executed by the one or more processors404.

[0065] Figure 5 is a schematic block diagram that illustrates a virtualizedembodiment of the network node 400 according to some embodiments of the presentdisclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0066] As used herein, a “virtualized” network node is an implementation of thenetwork node 400 in which at least a portion of the functionality of the network node400 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, thenetwork node 400 may include the control system 402 and / or the one or more radiounits 410, as described above. The control system 402 may be connected to the radiounit(s) 410 via, for example, an optical cable or the like. The network node 400includes one or more processing nodes 500 coupled to or included as part of anetwork(s) 502. If present, the control system 402 or the radio unit(s) are connected tothe processing node(s) 500 via the network 502. Each processing node 500 includesone or more processors 504 (e.g., CPUs, ASICs, FPGAs, and / or the like),memory / computer readable storage medium 506, and a network interface 508.

[0067] In this example, functions 510 of the network node 400 described herein areimplemented at the one or more processing nodes 500 or distributed across the one ormore processing nodes 500 and the control system 402 in any desired manner. Insome particular embodiments, some or all of the functions 510 of the network node 400described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 500. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 500 and the control system 402 is used in order to carry out at least some of the desired functions 510. Notably, insome embodiments, the control system 402 may not be included, in which case theradio unit(s) 410 communicate directly with the processing node(s) 500 via anappropriate network interface(s).

[0068] In some embodiments, a computer program including instructions which,when executed by at least one processor, causes the at least one processor to carry outthe functionality of network node 400 or a node (e.g., a processing node 500)implementing one or more of the functions 510 of the network node 400 in a virtualenvironment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0069] Figure 6 is a schematic block diagram of the network node 400 according tosome other embodiments of the present disclosure. The network node 400 includesone or more modules LI ADMF 102 or POI 106, each of which is implemented insoftware. The modules LI ADMF 102 or POI 106 provide the functionality of thenetwork node 400 described herein. This discussion is equally applicable to theprocessing node 500 of Figure 5 where the modules LI ADMF 102 or POI 106 may beimplemented at one of the processing nodes 500 or distributed across multipleprocessing nodes 500 and / or distributed across the processing node(s) 500 and thecontrol system 402.

[0070] Any appropriate steps, methods, features, functions, or benefits disclosedherein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to executeprogram code stored in memory, which may include one or several types of memorysuch as Read Only Memory (ROM), Random Access Memory (RAM), cache memory,flash memory devices, optical storage devices, etc. Program code stored in memoryincludes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0071] While processes in the figures may show a particular order of operationsperformed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0072] Those skilled in the art will recognize improvements and modifications to theembodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims 1. A method for enabling compatible destination set delivery types performed by a Point of Intercept, POI, Function device (106), the method comprising: receiving (302, 304), from a Lawful Intercept Administration Function, LI ADMF, (102), a request associated with a set of destinations (108), wherein the request comprises an indication of a delivery type of the set of destinations (108), and wherein the set of destinations (108) comprises a plurality of Destination Identities, DIDs, (110) with respective DID delivery types; if the DID delivery types or task delivery types of the request are compatible withthe delivery type of the set of destinations (108), accepting (306, 308) the request andperforming an operation based on the request; andif the DID delivery types or the task delivery types are not compatible with the delivery type of the set of destinations (108), providing (310), to the LI ADMF (102), an error message.

2. The method of claim 1, wherein the DID delivery types are one of:X2Only; X3Only; or X2andX3.

3. The method of any of claims 1 to 2, wherein the delivery type of the set ofdestinations (108) is one of: X2Only; X3Only; or X2andX3.

4. The method of any of claims 1 to 3, wherein a destination set type is at least oneof Redundant or Duplicate.

5. The method of any of claims 3 to 4, wherein the request is a CreateObject orModifyObject to define a destination set, and wherein the indication of the delivery type is a destination set delivery type.

6. The method of claim 5, wherein performing the operation comprises creating ormodifying (306) a destination set based on the CreateObject or ModifyObject request.

7. The method of any of claims 3 to 4, wherein the request is an ActivateTask orModifyTask (304) request associated with a task associated with the set of destinations (108), and the indication of the delivery type is a task delivery type.

8. The method of claim 7, wherein performing the operation comprises performing(308) the task based on the ActivateTask or ModifyTask request.

9. The method of any of claims 7 to 8, wherein the request is associated with aplurality of sets of destinations, and if the delivery type of the task is X2andX3 and thedelivery types of a first set of destinations (108-1) are X2andX3, and the delivery types a second set of destinations (108-2) are X2andX3, performing (308) the task.

10. The method of any of claims 1 to 9, wherein the error message indicates to theLI ADMF (102) that there was an invalid combination of delivery type of the set ofdestinations and DID delivery types or delivery type of set of destinations and the taskdelivery types.

11. A network node (400) that implements a Point of Intercept, POI, Function device(106) that is configured to enable compatible destination set delivery types, the network node (400) comprising processing circuitry (404) configured to cause the network node (400) to: receive (302, 304), from a Lawful Intercept Administration Function, LI ADMF, (102), a request associated with a set of destinations (108), wherein the request comprises an indication of a delivery type of the set of destinations (108), and wherein the set of destinations (108) comprises a plurality of Destination Identities, DIDs, (110) with respective DID delivery types; if the DID delivery types or task delivery types of the request are compatible withthe delivery type of the set of destinations (108), accept (306, 308) the request and performing (306) an operation based on the request; andif the DID delivery types or task delivery types are not compatible with thedelivery type of the set of destinations (108), provide (310), to the LI ADMF (102), an error message.

12. The network node (400) of claim 11, wherein the DID delivery types are one of:X2Only; X3Only; or X2andX3.

13. The network node (400) of any of claims 11 to 12, wherein the delivery type ofthe set of destinations (108) is one of: X2Only; X3Only; or X2andX3.

14. The network node (400) of any of claims 11 to 13, wherein a destination set typeis at least one of Redundant or Duplicate.

15. The network node (400) of any of claims 13 to 14, wherein the request is aCreateObject or ModifyObject to define a destination set, and wherein the indication ofthe delivery type is a destination set delivery type.

16. The network node (400) of claim 15, wherein the operation comprises creation or modification (306) of a destination set based on the CreateObject or ModifyObject request.

17. The network node (400) of any of claims 13 to 14, wherein the request is anActivateTask or ModifyTask request associated with a task associated with the set of destinations (108), and the indication of the delivery type is a task delivery type.

18. The network node (400) of claim 17, wherein the operation comprisesperformance (308) of the task based on the ActivateTask or ModifyTask request.

19. The network node (400) of any of claims 17 to 18, wherein the request isassociated with a plurality of sets of destinations, and if the task delivery type isX2andX3 and the delivery type of the first set of destinations (108-1) are X2Only, andthe delivery type of a second set of destinations (108-2) are X3Only, performing (308)the task.

20. The network node (400) of any of claims 11 to 19, wherein the error messageindicates to the LI ADMF (102) that there was an invalid combination of delivery type ofthe set of destinations and DID delivery types or delivery type of set of destinations andthe task delivery types.

21. A method for enabling compatible destination set delivery types performed by aLawful Intercept Administration Function, LI ADMF, (102) the method comprising: providing (302, 308), to a Point of Intercept, POI, Function device (106), a request associated with a set of destinations (108), wherein the request comprises an indication of a delivery type of the set of destinations (108), and wherein the set ofdestinations (108) comprises a plurality of Destination Identities, DIDs, (110) withrespective DID delivery types, wherein the DID delivery types are compatible with the delivery type of the set of destinations (108).

22. The method of claim 21, wherein the DID delivery types are one of:X2Only; X3Only; or X2andX3.

23. The method of any of claims 21 to 22, wherein the delivery type of the set ofdestinations (108) is one of: X2Only; X3Only; or X2andX3.

24. The method of any of claims 21 to 23, wherein the destination set delivery typeis at least one of Redundant or Duplicate.

25. The method of any of claims 23 to 24, wherein the request is a CreateObject orModifyObject to define a destination set, and wherein the indication of the delivery type is a destination set delivery type.

26. The method of any of claims 23 to 24, wherein the request is an ActivateTask orModifyTask request associated with a task associated with the set of destinations (108), and the indication of the delivery type is a task delivery type.

27. A network node (400) that implements a Lawful Intercept AdministrationFunction, LI ADMF, (102) that is configured to enable compatible destination set delivery types, the network node (400) comprising processing circuitry (404) configured to cause the network node (400) to: provide (302, 308), to a Point of Intercept, POI, Function device (106), a requestassociated with a set of destinations (108), wherein the request comprises an indication of a delivery type of the set of destinations (108), and wherein the set of destinations (108) comprises a plurality of Destination Identities, DIDs, (110) with respective DID delivery types, wherein the DID delivery types are compatible with the delivery type of the set of destinations (108).

28. The network node (400) of claim 27, wherein the DID delivery types are one of:X2Only; X3Only; or X2andX3.

29. The network node (400) of any of claims 27 to 28, wherein the delivery type ofthe set of destinations (108) is one of: X2Only; X3Only; or X2andX3.

30. The network node (400) of any of claims 27 to 29, wherein the destination setdelivery type is at least one of Redundant or Duplicate.

31. The network node (400) of any of claims 29 to 30, wherein the request is aCreateObject or ModifyObject to define a destination set, and wherein the indication of the delivery type is a destination set delivery type.

32. The network node (400) of any of claims 29 to 30, wherein the request is anActivateTask or ModifyTask request associated with a task associated with the set of destinations (108), and the indication of the delivery type is a task delivery type.

33. A computer program (410) comprising instructions which, when executed on processing circuitry (404), cause the processing circuitry (404) to carry out the method according to any of claims 1 to 10 and 21 to 26.

34. A carrier containing the computer program (410) of claim 33, wherein the carrieris one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (406).

Images