Patent Description:
Lawful interception of traffic between communicating entities in a telecommunication network involves interaction between several functions in a core network that is part of the telecommunication network. For the purpose of the present disclosure, it is enough to mention an LI ADMF and a NE. As will be exemplified further in the detailed description below, an NE in the present context is an entity in the core network that is involved in the communication activity that is subject to LI.

Communication between entities in the core network, in a LI context, is subject to various standards in the form of technical specifications (TS) set by the European Telecommunications Standards Institute (ETSI). According to ETSI TS <NUM><NUM>-<NUM> (current version V1. <NUM>), the ADMF and the NE exchange messages between them on an X1 interface. The direction of the messages can be from the ADMF to the NE or vice versa, the first message in an exchange of messages being defined as a request message and a following message in the opposite direction being defined as a response message.

The exchanged messages can be one of several types of messages. Definition messages that are requests from the ADMF to the NE are used for starting, modifying and stopping tasks as well as for creating, modifying and removing destinations. Messages for getting information from the NE that are requests from the ADMF to the NE are used for getting information about a task, getting information about a destination, getting information about the NE status, getting information about all tasks, destinations and the NE status, and listing all tasks and destinations. Messages for reporting issues from the NE that are requests from the NE to the ADMF are used for reporting a task issue, reporting a destination issue and reporting an NE issue. A ping message is a connection testing message that is a request from either the NE to the ADMF or from the ADMF to the NE. Another connection testing message is a keepalive request from the ADMF to the NE.

In an exchange of messages, a response to a request shall be sent without undue delay and shall be sent within a time period TIME1 of receiving the request. The requester will wait a time period TIME2 (greater than TIME1) for a response and having not received a response within the time period TIME2, the request is considered without response, i.e. a timeout condition has occurred. Connection testing messages do not require any work by the receiver, which means that, if there are no connection problems, a connection testing request can be responded to immediately, without any timeout problem. Reporting issue from the NE messages may require work by the ADMF, but the response to send to the NE is only an acknowledgement (ACK) of the message reception, which means that it can be sent back by the ADMF to the NE immediately, without any timeout problem.

Definition messages and getting information from NE messages require some actions to perform by the NE and the response messages to the ADMF include the results of these actions, which means that it is possible that the NE cannot complete the requested actions within the time period TIME1. In case a definition message requires a longer time period than TIME1 to be completed, it is foreseen in the ETSI standard that, instead of an "OK - Acknowledged and Completed" response, an "OK - Acknowledged" response is sent back to the ADMF that means that the request has been received by the NE but it has not yet been completed by the NE. As soon as the requested action has been completed by the NE, a reporting issue from the NE message (task or destination issue) shall be sent to the ADMF to inform the ADMF about the final status (completed or unsuccessful) of the request.

Currently, the ETSI standard does not include a specification of any mechanism to allow the correct handling of getting information from NE messages for reporting a large amount of data that could cause timeout and transmission problems. For example, the number of tasks that are handled by an NE can be very high and creating a message response including information for all tasks can require a long time and generate a large amount of data to send in a response, causing timeout problems as well as causing congestion on a channel carrying an X1 interface. In case the ADMF applies a retry mechanism, after a timeout period has lapsed, the risk of creating a "loop" is high with an associated drawback that the X1 channel and the NE become congested.

In view of the above, an object of the present disclosure is to overcome drawbacks related to transmission of task related information from an NE to an ADMF. This object is achieved in a first aspect by a method performed by a computer system in a telecommunication network, the computer system hosting at least an LI ADMF and an NE.

The method of the first aspect comprises transmitting, by the ADMF to the NE via an X1 interface, a request for information pertaining to LI tasks that are associated with the NE. The request comprises a bulk indicator that indicates a procedure of transmission, from the NE to the ADMF, of said information pertaining to LI tasks. The information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE to the ADMF via the X1 interface using a corresponding one or several transmissions. The NE determines, based at least on the bulk indicator, whether or not transmission of said information pertaining to LI tasks is to be performed using the procedure of transmission indicated by the bulk indicator. If it is determined that transmission of said information pertaining to LI tasks is to be performed using the procedure of transmission indicated by the bulk indicator, the NE transmits, to the ADMF via the X1 interface using the procedure of transmission indicated by the bulk indicator, said information pertaining to LI tasks.

In other words, a request from the ADMF to the NE of information pertaining to LI tasks that the NE is associated with is provided with a new indicator. This new indicator, i.e. the bulk indicator, specifies for the NE to apply an indicated transmission procedure when providing the requested information to the ADMF. This is advantageous in that it enables the ADMF and the NE to perform an exchange of messages for providing a large amount of task information from the NE to the ADMF without risking a timeout or risking a congestion of a channel carrying the X1 interface between the ADMF and the NE. That is, the expression "bulk" indicator is used in order to accentuate that a distinct mass or portion of entities, especially a large mass or portion of information, is handled by the method.

In a further aspect, there is provided a computer system comprising a processor and a memory, said memory containing instructions executable by said processor whereby said computer system is operative to perform the method.

The bulk indicator may have a first value, in which cases the determining by the NE comprises determining that said information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE.

In such cases, the NE may determine a number of bulks of information for transmission of said information pertaining to LI tasks. The transmitting by the NE <NUM> to the ADMF via the X1 interface may then comprise transmitting a response comprising a confirmation that subsequent transmissions will comprise a respective bulk of information from said information pertaining to LI tasks, transmitting zero or more requests comprising a respective bulk of information from said information pertaining to LI tasks and comprising a confirmation that at least one further bulk of information from said information pertaining to LI tasks will be transmitted, and transmitting a request comprising a last bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

The bulk indicator may have a second value, in which cases the determining by the NE comprises determining that said information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE.

In such cases, the NE determines that a number of bulks of information for transmission of said information pertaining to LI tasks is one, and the transmitting by the NE to the ADMF via the interface may comprise transmitting a response comprising one bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted. In other cases, the NE may determine a number of bulks of information for transmission of said information pertaining to LI tasks. The transmitting by the NE to the ADMF via the X1 interface may then comprise transmitting a response comprising a first bulk of information from said information pertaining to LI tasks and comprising a confirmation that at least one further bulk of information from said information pertaining to LI tasks will be transmitted, transmitting zero or more requests comprising a respective bulk of information from said information pertaining to LI tasks and comprising a confirmation that at least one further bulk of information from said information pertaining to LI tasks will be transmitted, and transmitting a request comprising a last bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

The bulk indicator may have a third value, in which cases the determining by the NE comprises determining that said information pertaining to LI tasks is to be kept in one bulk of information for transmission by the NE. Such cases further comprise transmitting, by the NE to the ADMF via the X1 interface, a response comprising one bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

Furthermore, the transmitting of a request by the ADMF to the NE via the X1 interface may comprise transmitting any of a GetAlIDetailsRequest message and a ListAllDetailsRequest message as specified in technical specification <NUM><NUM>-<NUM> V1. <NUM> by the ETSI.

Similarly, any transmitting of a response by the NE to the ADMF via the X1 interface may comprise transmitting any of a GetAlIDetailsResponse message and a ListAlIDetailsResponse message as specified in technical specification <NUM><NUM>-<NUM> V1. <NUM> by the ETSI.

Also, any transmitting of a request by the NE to the ADMF via the X1 interface may comprise transmitting a BulkAllDetailsRequest message.

In other words, such a BulkAllDetailsRequest message is a new message introduced as a consequence of the need for overcoming the drawbacks of prior art standard as defined in technical specification <NUM><NUM>-<NUM> V1. <NUM> by the ETSI. Needless to say, such an addition of a new message to technical specification <NUM><NUM>-<NUM> V1. <NUM> may involve naming the message differently, remembering that the essence of adding a new message is that of further enhancing the method of transmitting large amounts of data from the NE to the ADMF.

These further aspects and embodiments of these further aspects provide the same effects and advantages as summarized above in connection with the method of the first aspect.

<FIG> schematically illustrates a first functional representation of a telecommunication network <NUM> comprising a core network <NUM> and an access network <NUM> in which two communicating entities, a first communicating entity <NUM> and a second communicating entity <NUM> are connected. The access network may, e.g., be in the form of a 3GPP radio access network (RAN) or any other type of non-3GPP communication network that may connect to the core network <NUM>, which may be e.g. an Evolved Packet Core (EPC), a <NUM> core network (5GC) or any future core network in which the skilled person would understand that the methods and arrangements described herein can be implemented in.

As the skilled person will realize, communication performed by the first and second communicating entities <NUM>, <NUM> is enabled by several functional units in both the access network <NUM> and the core network <NUM>. For the sake of clarity of description, such functional units are not illustrated in full but only schematically represented and exemplified by a network element (NE) <NUM> that, in a <NUM> context (e.g. 3GPP Evolved Packet System (EPS), may be a mobility management entity (MME), a serving gateway (S-GW), a packet data network gateway (P-GW) etc. In a <NUM> context, the network element <NUM> may, e.g., be in the form of a policy control function (PCF), a user data management function (UDM), an Access and Mobility Management Function (AMF) or a session management function (SMF) etc. The network element may even be an SMS-Function (SMSF).

A common characteristic of such functional units, as represented by network element <NUM>, in the core network <NUM> is that they may comprise LI functionality in the form of a point of interception (POI) <NUM>. The POI <NUM> is in <FIG> thus depicted as being a part of the network element <NUM> or being embedded therein, but the POI <NUM> may also be separate from the network element <NUM> with which it is associated. The core network <NUM> may be the core network of a serving network (SN), which may be a Visited Public Land Mobile Network (VPLMN) or a Home Public Land Mobile Network (HPLMN).

The core network <NUM> also comprises an administrative function (ADMF) <NUM> (also called LI ADMF) and a mediation and delivery function (MDF) <NUM> that connects to a law enforcement agency (LEA) <NUM>. Within the MDF <NUM> a mediation function (MF) <NUM> and a delivery function (DF) <NUM> are configured to handle an intercept product in the form of intercept related information (IRI) and content of communication (CC) received from the POI <NUM> and provide the IRI and CC to the LEA <NUM>. The LEA <NUM> manages a LEA communication device in the form of a law enforcement monitoring facility (LEMF) <NUM>, which receives IRI and CC from the DF <NUM>.

Communication between the entities in the telecommunication system <NUM> takes place via X1, X2, X3, and HI1, HI2 and HI3 interfaces. That is, the ADMF <NUM> communicates with the MF <NUM>, DF <NUM>, the POI <NUM> and the NE <NUM> via the X1 interface. The POI <NUM> in the NE <NUM> communicates with the MF <NUM> via the X2 and X3 interfaces. The ADMF <NUM> also communicates with the LEA <NUM> via an HI1 interface, and the DF <NUM> communicates with the LEMF <NUM> in the LEA <NUM> via HI2 and HI3 interfaces.

<FIG> schematically illustrates the telecommunication network <NUM> as it is realized using hardware wherein virtual network functions (VNF) are executed on virtual nodes <NUM> that utilize a hardware server platform <NUM>. The MF <NUM>, the DF <NUM>, the ADMF <NUM>, the NE <NUM> and the POI <NUM> are realized in a functional layer <NUM> of VNFs that execute in the virtual nodes <NUM> via a virtualization layer <NUM>. For example, a virtual node <NUM> is a collection of software instructions as well as associated data <NUM> as the skilled person will realize. The LEA <NUM> with its LEMF <NUM> is connected to the hardware platform <NUM> via an intermediate network <NUM>, the details of which are outside the scope of the present disclosure. Although not explicitly illustrated in <FIG>, communication between entities via the X1, X2, X3, H!<NUM>, HI2 and HI3 interfaces take place as described above in connection with <FIG>.

Turning now to the flowcharts illustrated in <FIG> and the signalling diagrams illustrated in <FIG>, and with continued reference to <FIG>, embodiments of methods in the telecommunication network <NUM> will be described in some more detail. The embodiments will exemplify how the various functional units and the X1 interface described above may be enhanced in order to provide the effect and advantages associated with transmission of task related information from a NE to an ADMF.

<FIG> and <FIG> illustrate a method that comprises actions performed by a computer system in a telecommunication network <NUM>, said computer system hosting at least the ADMF <NUM> and the NE <NUM> introduced and described above in connection with <FIG>:.

The ADMF <NUM> transmits, to the NE <NUM> via an X1 interface, a request <NUM> for information pertaining to LI tasks that are associated with the NE <NUM>. The request comprises a bulk indicator that indicates a procedure of transmission, from the NE <NUM> to the ADMF <NUM>, of said information pertaining to LI tasks.

In some embodiments, the bulk indicator indicates that the information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE <NUM> to the ADMF <NUM> via the X1 interface using a corresponding one or several transmissions.

The NE <NUM> determines, based at least on the bulk indicator, whether or not transmission of said information pertaining to LI tasks is to be performed using the procedure of transmission indicated by the bulk indicator.

If it is determined, in action <NUM>, that transmission of said information pertaining to LI tasks is to be performed using the procedure of transmission indicated by the bulk indicator, the NE <NUM> transmits, to the ADMF <NUM> via the X1 interface using the procedure of transmission indicated by the bulk indicator, said information pertaining to LI tasks.

In some embodiments, where the bulk indicator transmitted by the ADMF <NUM> in action <NUM> has a first value, the determining by the NE <NUM> in action <NUM> comprises determining that said information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE <NUM>.

As illustrated in <FIG>, such embodiments may comprise an action <NUM> where the NE <NUM> determines a number of bulks of information for transmission of said information pertaining to LI tasks. In these embodiments, the transmitting by the NE <NUM> to the ADMF <NUM> via the X1 interface in action <NUM> may comprise the actions:.

The NE <NUM> transmits a response <NUM> comprising a confirmation that subsequent transmissions will comprise a respective bulk of information from said information pertaining to LI tasks.

The NE <NUM> transmits zero or more requests <NUM> comprising a respective bulk of information from said information pertaining to LI tasks and comprising a confirmation that at least one further bulk of information from said information pertaining to LI tasks will be transmitted.

In other words, in the case that the NE <NUM> determines, in action <NUM>, that the number of bulks of information for transmission is only one, then action <NUM> will not be performed.

The NE <NUM> transmits a request <NUM> comprising a last bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

In some embodiments, the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface in action <NUM> comprises transmitting information specifying a maximum bulk size of a bulk of information for transmission from the NE <NUM> to the ADMF <NUM>. In such embodiments, any transmitting in actions <NUM> and <NUM> of a request <NUM>, <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a bulk of information from said information pertaining to LI tasks comprises transmitting each respective bulk of information using a bulk size that is less than or equal to said maximum bulk size.

In some embodiments, the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface in action <NUM> comprises transmitting information identifying the request transmitted by the ADMF <NUM>. In such embodiments, any transmitting in actions <NUM> and <NUM> of a request <NUM>, <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a bulk of information from said information pertaining to LI tasks comprises transmitting the information identifying the request <NUM> transmitted from the ADMF <NUM>.

In some embodiments, where the bulk indicator transmitted by the ADMF <NUM> in action <NUM> has a second value, the determining by the NE <NUM> in action <NUM> comprises determining that said information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE <NUM>.

As illustrated in <FIG> and <FIG>, the NE <NUM> determines in an action <NUM> that the number of bulks of information for transmission of said information pertaining to LI tasks is one. In such embodiments the transmitting by the NE <NUM> in action <NUM> may comprise an action <NUM> where the NE <NUM> transmits a response <NUM> comprising one bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

In some embodiments, the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface in action <NUM> comprises transmitting information specifying a maximum bulk size of a bulk of information for transmission from the NE <NUM> to the ADMF <NUM>. In such embodiments, the transmitting in action <NUM> of a response <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface may comprise a bulk of information from said information pertaining to LI tasks comprises transmitting the one bulk of information using a bulk size that is less than or equal to said maximum bulk size.

As illustrated in <FIG> and <FIG> and continuing with embodiments where the bulk indicator transmitted by the ADMF <NUM> in action <NUM> has a second value, some embodiments comprise an action <NUM> where the NE <NUM> determines a number of bulks of information for transmission of said information pertaining to LI tasks. In these embodiments, the transmitting by the NE <NUM> to the ADMF <NUM> via the X1 interface in action <NUM> may comprise the actions:.

The NE <NUM> transmits a response <NUM> comprising a first bulk of information from said information pertaining to LI tasks and comprising a confirmation that at least one further bulk of information from said information pertaining to LI tasks will be transmitted.

In other words, in the case that the NE <NUM> determines, in action <NUM>, that the number of bulks of information for transmission is only two, then action <NUM> will not be performed.

The NE <NUM> transmits a request <NUM> comprising a last bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted. It is to be noted that, in case all information pertaining to LI tasks has been already transmitted in action <NUM>, the transmitting in action <NUM> will comprise only the confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

In some embodiments, the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface in action <NUM> comprises transmitting information specifying a maximum bulk size of a bulk of information for transmission from the NE <NUM> to the ADMF <NUM>. In such embodiments, the transmitting in action <NUM> of a response <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a first bulk of information from said information pertaining to LI tasks comprises transmitting the first bulk of information using a bulk size that is less than or equal to said maximum bulk size. Also, in such embodiments, any transmitting in actions <NUM> and <NUM> of a request <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a bulk of information from said information pertaining to LI tasks comprises transmitting each respective bulk of information using a bulk size that is less than or equal to said maximum bulk size.

In some embodiments, the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface in action <NUM> comprises transmitting information identifying the request transmitted by the ADMF <NUM>. In such embodiments, any transmitting in actions <NUM> and <NUM> of a request <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface of a bulk of information from said information pertaining to LI tasks comprises transmitting the information identifying the request transmitted from the ADMF <NUM>.

In some embodiments, where the bulk indicator transmitted by the ADMF <NUM> in action <NUM> has a third value, the determining by the NE <NUM> in action <NUM> comprises determining that said information pertaining to LI tasks is to be kept in one bulk of information for transmission by the NE <NUM>. As illustrated in <FIG> and <FIG>, such embodiments comprise an action <NUM> where the NE <NUM> transmits to the ADMF <NUM> via the X1 interface, a response <NUM> comprising one bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

As will be described below and further illustrating the effects and advantages of these embodiments, the transmitting in action <NUM> of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface may comprise transmitting any of a GetAlIDetailsRequest message and a ListAlIDetailsRequest message as specified in technical specification (TS) <NUM><NUM>-<NUM> V1. <NUM> by ETSI. Similarly, any transmitting in actions <NUM>, <NUM>, <NUM> and <NUM> of a response <NUM>, <NUM>, <NUM> and <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface may comprise transmitting any of a GetAIIDetailsResponse message and a ListAlIDetailsResponse message as specified in TS <NUM><NUM>-<NUM> V1. <NUM> by the ETSI.

Similarly, any transmitting in actions <NUM>, <NUM>, <NUM> and <NUM> of a request <NUM>, <NUM>, <NUM> and <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface may comprise transmitting a BulkAllDetailsRequest message.

Specifically, with regard to such additions to TS <NUM><NUM>-<NUM> V1. <NUM>, the GetAIIDetailsRequest and ListAllDetailsRequest messages may be provided three new optional fields for bulk handling of information pertaining to LI tasks that the NE <NUM> is handling. A corresponding new optional field in GetAIIDetailsResponse and ListAIIDetailsResponse messages that the NE <NUM> transmits to the ADMF <NUM> is also provided. Also, a new message, for example denoted BulkAllDetails, transmitted by the NE <NUM> to the ADMF <NUM> is added to TS <NUM><NUM>-<NUM> V1.

For example, TS <NUM><NUM>-<NUM> V1. <NUM> may be completed by addition of three new fields in Table <NUM> "GetAIIDetailsRequest" in clause <NUM>. <NUM> and in Table <NUM> "ListAIIDetailsRequest" in clause <NUM>. <NUM> in TS <NUM><NUM>-<NUM> V1. <NUM> as shown herein in table <NUM>.

In table <NUM>, as well as in other tables herein, "M/C/O" is an abbreviation for "Mandatory/Conditional/Optional" and the format UUIDv4 refers to the version <NUM> universally unique identifier (UUID) as defined in Internet engineering task force (IETF) request for comments (RFC) <NUM>. The content of the UseBulk field is the bulk indicator included in the request as discussed above in connection with action <NUM>. As such, the first value of the bulk indicator is "MustUseBulk", the second value is "CanUseBulk" and the third value is "DoNotUseBulk".

In case the UseBulk field is not present in the GetAIIDetailsRequest or ListAlIDetailsRequest (which would be the case if the ADMF <NUM> does not support the additions as described herein), it means that the ADMF <NUM> does not handle transmission in bulks as described, which in turn means that the NE <NUM> must operate according to prior art. The NE <NUM> should operate according to prior art also in case the field UseBulk is present with the third value DoNotUseBulk.

In case the UseBulk field in a GetAIIDetailsRequest or ListAlIDetailsRequest message is present with the first or second values, i.e. MustUseBulk or CanUseBulk, then also the fields BulkSize and Requestld may be in the message transmitted by the ADMF <NUM> in action <NUM>. BulkSize indicates the maximum amount of data that can be inserted in a single bulk message. If BulkSize is not present, it may mean that the ADMF <NUM> can handle bulk messages of any data; in such a case the NE <NUM> may decide whether or not data shall be transmitted in one or more bulk messages. The Requestld is the identifier that the NE <NUM> returns to the ADMF <NUM> in subsequent bulk messages.

From a point of view of the NE <NUM>, at reception of a GetAIIDetailsRequest or ListAlIDetailsRequest message the NE <NUM>, if it is not configured to support the additions to TS <NUM><NUM>-<NUM> V1. <NUM> described herein, the NE <NUM> does not read the additional field UseBulk and, consequently, the NE <NUM> operates according to prior art and transmits a response <NUM> as illustrated in <FIG>. The same applies if the NE <NUM> is configured to support the new additions to TS <NUM><NUM>-<NUM> V1. <NUM> described herein but the UseBulk field is missing or present with value DoNotUseBulk.

In case the GetAIIDetailsRequest or ListAllDetailsRequest message contains UseBulk field with a MustUseBulk value, the NE <NUM> must immediately respond to the ADMF <NUM>, without inserting any data in the response message. All data, i.e. the requested information pertaining to LI tasks, will be included in one or more bulk messages as described in some detail herein. If instead the GetAIIDetailsRequest or ListAlIDetailsRequest message contains a UseBulk field with a CanUseBulk value, the NE <NUM> may decide if it is to start inserting data in the response message or immediately answer to the ADMF <NUM>, without inserting any data in the response message. If data are inserted in the response message, the NE <NUM> must not exceed the BulkSize and to send the answer within the TIME1 period.

With regard to the response transmitted by the NE <NUM> to a GetAIIDetailsRequest message, TS <NUM><NUM>-<NUM> V1. <NUM> may be completed by addition of a new optional field in Table <NUM> GetAIIDetailsResponse in clause <NUM>. <NUM> in TS <NUM><NUM>-<NUM> V1. <NUM> as shown herein in table <NUM>.

The already existing fields NEStatusDetails, ListOfΓaskResponseDetails, and ListOfDestinationResponseDetails change from M (Mandatory) to C (Conditional).

Similarly, with regard to the response transmitted by the NE <NUM> to a ListAlIDetailsRequest message, TS <NUM><NUM>-<NUM> V1. <NUM> may be completed by addition of a new optional field in Table <NUM> ListAIIDetailsResponse in clause <NUM>. <NUM> in TS <NUM><NUM>-<NUM> V1. <NUM> as shown herein in table <NUM>.

The already existing fields ListOfXlDs and ListOfDlDs change from M (Mandatory) to C (Conditional).

In case the NE <NUM> is not configured to support the additions to TS <NUM><NUM>-<NUM> V1. <NUM> as described herein, the added RequestStatus field is not present in the response transmitted by the NE <NUM>, and the message is handled according to prior art. The ADMF <NUM> must then consider that the RequestStatus field has a value of Completed.

With regard to the added message, herein named BulkAllDetails, it has a direction such that it is transmitted by the NE <NUM> to the ADMF <NUM> and it is used to provide all or part of the data requested by the ADMF <NUM> with GetAlIDetails and ListAlIDetails messages.

The BulkAIIDetailsRequest message, transmitted by the NE <NUM> to the ADMF <NUM>, comprises the fields of table <NUM> herein. Three fields (NEStatusDetails, ListOfTaskResponseDetails and ListOfDestinationResponseDetails) are inherited from the GetAlIDetailsResponse message and two fields (ListOfXIDs and ListOfDIDs) are inherited from the ListAlIDetailsResponse message, both of which are discussed above.

A response message, transmitted by the ADMF <NUM> to the NE <NUM>, may be named BulkAlIDetailsResponse and comprising the field according to table <NUM> herein.

The NE <NUM> inserts, in the BulkAIIDetailsRequest message transmitted to the ADMF <NUM>, data according to the BulkSize requested by the ADMF <NUM> in the request transmitted in action <NUM>. During the insertion of data, when the amount of data reaches an amount corresponding to the value of BulkSize, the bulk message (i.e. the message named herein BulkAllDetailsRequest) is transmitted to the ADMF <NUM>. As illustrated in table <NUM> herein, in the BulkAIIDetailsRequest message information is also inserted regarding the Requestld message, the number of the Bulk message (i.e. MessageSequence having values <NUM>, <NUM> and so on), the type of messages (i.e. GetAlIDetails or ListAllDetails) that initially requested the bulk and an indication if this is the last message, i.e. Completed meaning that all data has been inserted or that other messages will follow as indicated by Ongoing.

The ADMF <NUM>, having received a BulkAllDetailsRequest message, checks the sequence number (MessageSequence) and the RequestId with RequestMessageType in order to verify whether or not the received BulkAIIDetailsRequest message is expected and that no message has been lost. After that, the ADMF <NUM> transmits to the NE <NUM> a BulkAlIDetailsResponse message and starts handling the received data. If the RequestStatus of the received BulkAlIDetailsRequest has the value Ongoing, the ADMF <NUM> determines that further BulkAIIDetailsRequest messages will arrive with the same RequestId.

Turning now to <FIG>, and with continued reference to <FIG>, a computer system <NUM> will be described in some detail. The computer system <NUM>, which may correspond to at least part of the telecommunication network <NUM>, comprises at least a processor <NUM> and a memory <NUM>. The memory <NUM> contains instructions executable by the processor <NUM> whereby the computer system <NUM> is operative to:.

In some embodiments, the computer system <NUM> comprises one or more compute hosts <NUM>, said one or more compute hosts <NUM> comprising at least a processor <NUM> and a memory <NUM>.

The instructions that are executable by the processor <NUM> may be software in the form of a computer program <NUM>. The computer program <NUM> may be contained in or by a carrier <NUM>, which may provide the computer program <NUM> to the memory <NUM> and processor <NUM>. The carrier <NUM> may be in any suitable form including an electronic signal, an optical signal, a radio signal or a computer readable storage medium.

In some embodiments, the computer system <NUM> is operative such that the bulk indicator indicates that the information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE <NUM> to the ADMF <NUM> via the X1 interface using a corresponding one or several transmissions.

In some embodiments, the computer system <NUM> is operative such that the bulk indicator has a first value and the determining by the NE <NUM> comprises determining that said information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE <NUM>.

In some embodiments, the computer system <NUM> is operative to determine, by the NE <NUM>, a number of bulks of information for transmission of said information pertaining to LI tasks, and wherein the computer system <NUM> is operative such that the transmitting by the NE <NUM> to the ADMF <NUM> via the X1 interface comprises:.

In some embodiments, the computer system <NUM> is operative such that the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface comprises transmitting information specifying a maximum bulk size of a bulk of information for transmission from the NE <NUM> to the ADMF <NUM>, and operative such that any transmitting of a request <NUM>, <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a bulk of information from said information pertaining to LI tasks comprises transmitting each respective bulk of information using a bulk size that is less than or equal to said maximum bulk size.

In some embodiments, the computer system <NUM> is operative such that the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface comprises transmitting information identifying the request transmitted by the ADMF <NUM>, and operative such that any transmitting of a request <NUM>, <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a bulk of information from said information pertaining to LI tasks comprises transmitting the information identifying the request <NUM> transmitted from the ADMF <NUM>.

In some embodiments, the computer system <NUM> is operative such that the bulk indicator has a second value and the determining by the NE <NUM> comprises determining that said information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE <NUM>.

In some embodiments, the computer system <NUM> is operative to determine, by the NE <NUM>, that a number of bulks of information for transmission of said information pertaining to LI tasks is one, and operative such that the transmitting by the NE <NUM> to the ADMF <NUM> via the X1 interface comprises transmitting a response <NUM> comprising one bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

In some embodiments, the computer system <NUM> is operative such that the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface comprises transmitting information specifying a maximum bulk size of a bulk of information for transmission from the NE <NUM> to the ADMF <NUM>, and operative such that the transmitting of a response <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a bulk of information from said information pertaining to LI tasks comprises transmitting the one bulk of information using a bulk size that is less than or equal to said maximum bulk size.

In some embodiments, the computer system <NUM> is operative such that the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface comprises transmitting information specifying a maximum bulk size of a bulk of information for transmission from the NE <NUM> to the ADMF <NUM>, and operative such that the transmitting of a response <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a first bulk of information from said information pertaining to LI tasks comprises transmitting the first bulk of information using a bulk size that is less than or equal to said maximum bulk size, and operative such that any transmitting of a request <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a bulk of information from said information pertaining to LI tasks comprises transmitting each respective bulk of information using a bulk size that is less than or equal to said maximum bulk size.

In some embodiments, the computer system <NUM> is operative such that the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface comprises transmitting information identifying the request transmitted by the ADMF <NUM>, and operative such that the transmitting of a response <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprising a first bulk of information from said information pertaining to LI tasks comprises transmitting the information identifying the request transmitted from the ADMF <NUM>, and operative such that any transmitting of a request <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface of a bulk of information from said information pertaining to LI tasks comprises transmitting the information identifying the request transmitted from the ADMF <NUM>.

In some embodiments, the computer system <NUM> is operative such that the bulk indicator has a third value, and operative such that the determining by the NE <NUM> comprises determining that said information pertaining to LI tasks is to be kept in one bulk of information for transmission by the NE <NUM>, and wherein the computer system <NUM> is operative to transmit, by the NE <NUM> to the ADMF <NUM> via the X1 interface, a response <NUM> comprising one bulk of information from said information pertaining to LI tasks and comprising a confirmation that a last bulk of information from said information pertaining to LI tasks has been transmitted.

In some embodiments, the computer system <NUM> is operative such that the transmitting of a request <NUM> by the ADMF <NUM> to the NE <NUM> via the X1 interface comprises transmitting any of a GetAlIDetailsRequest message and a ListAllDetailsRequest message as specified in technical specification <NUM><NUM>-<NUM> V1. <NUM> by the European Telecommunications Standards Institute, ETSI.

In some embodiments, the computer system <NUM> is operative such that any transmitting of a response <NUM>, <NUM>, <NUM>, <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprises transmitting any of a GetAlIDetailsResponse message and a ListAlIDetailsResponse message as specified in technical specification <NUM><NUM>-<NUM> V1. <NUM> by the ETSI.

In some embodiments, the computer system <NUM> is operative such that any transmitting of a request <NUM>, <NUM>, <NUM>, <NUM> by the NE <NUM> to the ADMF <NUM> via the X1 interface comprises transmitting a BulkAIIDetailsRequest message.

Turning now to <FIG>, and with continued reference to <FIG>, a computer system <NUM> will be described in some detail. The computer system <NUM> comprises:.

Claim 1:
A method performed by a computer system (<NUM>) in a telecommunication network (<NUM>), said computer system (<NUM>) hosting at least a lawful interception, LI, administrative function, ADMF, (<NUM>) and a network element, NE, (<NUM>), the method comprising:
- transmitting (<NUM>), by the ADMF (<NUM>) to the NE (<NUM>) via an X1 interface, a request (<NUM>) for information pertaining to LI tasks that are associated with the NE (<NUM>), said request comprising a bulk indicator that indicates a procedure of transmission, from the NE (<NUM>) to the ADMF (<NUM>), of said information pertaining to LI tasks and that said information pertaining to LI tasks is to be kept in one bulk or split into several bulks of information for transmission by the NE (<NUM>) to the ADMF (<NUM>) via the X1 interface using a corresponding one or several transmissions,
- determining (<NUM>), by the NE (<NUM>) based at least on the bulk indicator, whether or not transmission of said information pertaining to LI tasks is to be performed using the procedure of transmission indicated by the bulk indicator, and
- if it is determined that transmission of said information pertaining to LI tasks is to be performed using the procedure of transmission indicated by the bulk indicator, transmitting (<NUM>), by the NE (<NUM>) to the ADMF (<NUM>) via the X1 interface using the procedure of transmission indicated by the bulk indicator, said information pertaining to LI tasks.