Send or receive version information of the transport protocol

By sending a request for destination identifier and version information in the telecommunications network, the transmission protocol version between POI and MF is automatically selected, which solves the problem of mismatch in the protocol version in the prior art, realizes automatic data transmission configuration, and reduces cost and failure risks.

CN115668864BActive Publication Date: 2025-07-11TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202080101351.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-05-29
Publication Date
2025-07-11
Estimated Expiration
2040-05-29

AI Technical Summary

Technical Problem

In telecommunications networks, the prior art cannot automatically adapt to the transmission protocol version between POI and MF, resulting in errors or loss of data transmission, increasing installation and maintenance costs and failure risks.

Method used

By sending a request for destination identifier and version information on the X1 interface, the highest version transmission protocol supported between POI and MF is automatically selected to achieve fully automatic configuration and reduce manual configuration steps and error risks.

Benefits of technology

Avoid data transmission errors and losses, reduce operational expenses, reduce manual error risks during installation and upgrades, and enable automated protocol updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115668864B_ABST
    Figure CN115668864B_ABST
Patent Text Reader

Abstract

Receive, via the X1 interface, from the administrative function ADMF (108), a request associated with a destination to which the interception point POI (135) is to send the intercepted data via the X2 / X3 interface during a lawful interception. The request includes an identifier of the destination and version information that specifies at least one version of a transport protocol to be used by the POI to send the intercepted data to the identified destination. The POI determines whether the POI is capable of sending the intercepted data via the X2 / or X3 interface using a version of the protocol equal to one of the versions in the received version information. Compare the received version information with the version information available at the POI. Send a response via the X1 interface, the response indicating whether the POI is capable of sending the intercepted data via the X2 / X3 interface.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments herein relate to methods performed by a lawful interception management function in a telecommunication network, methods performed by an interception point in a network element in a telecommunication network, corresponding computer systems, computer programs, and carriers of such computer programs. Background Art

[0002] Lawful interception (LI) of traffic between communication entities in a telecommunication network involves interaction between several functions in a core network that is part of the telecommunication network. For the purposes of this disclosure, it is sufficient to mention some functions, such as a LI management function (ADMF), an interception point (POI) within a network element (NE), and a mediation function (MF). As will be further illustrated in the detailed description below, the NE in this context is an entity involved in the communication activities subject to LI in the core network.

[0003] In the context of LI, communication between entities in the core network follows various standards in the form of technical specifications (TS) set by the European Telecommunications Standards Institute (ETSI). According to ETSI TS103 221-1 V1.6.1 (hereinafter referred to as ETSI TS 103 221-1), commands are sent from the ADMF to the NE via the X1 interface as LI tasks, such as activation, modification, and deactivation tasks. The commands are sent using the message structure specified in ETSI TS 103 221-1, and the NE responds to the ADMF with a response message also specified in ETSI TS 103 221-1. During LI, according to ETSI TS 103 221-2 V1.1.1 (hereinafter referred to as ETSI TS 103 221-2), the POI in the NE sends interception data as an X2 / X3 protocol data unit (PDU) stream to the MF via the X2 and X3 interfaces.

[0004] The intercepted traffic is transferred by the POI in the NE to a destination specified in ETSI TS 103 221-1. Each destination is uniquely identified by a destination identifier (DID) and is processed independently of the details of the LI task. Each LI task is associated with one or more destinations. Destinations can be created and modified using specific messages, and it is related to the X2 and X3 transfer types (see Figure 1).

[0005] Since the messages exchanged via the X1 interface and the data transmissions via the X2 and X3 interfaces can also change in a non-backward compatible manner according to the evolution of the standard specifications, where the standard specifications require that there is also information about the version of the standard specification according to which the sending entity operates in the header of the messages and in the data sent via the X1 and X2 / X3 interfaces. The reason is that the recipient of the messages (NE or ADMF) and the recipient of the data (MF) will know which standard protocol version is to be used to read the messages and the data. Specifically, when sending via the X1 interface, the sending entity is required to send information about the version of the ETSI TS 103 221-1 standard used, while via the X2 and X3 interfaces, the sending entity is required to send information about the version of the ETSI TS 103 221-2 standard used.

[0006] From the perspective of the receiving entity, in the case where the message received via the X1 interface contains an unsupported version of the standard specification in the header, an error response message will be sent back to the sending entity. The error code 1020 "Unsupported version" is used, and the information element contains the version supported by the originating system (i.e., the entity sending back the error response message). In this way, the sending entity that sent the request message is notified that the protocol version is not supported by the receiving entity.

[0007] However, regarding the transmission via the X2 / X3 interface, in the case where the data received by the MF via the X2 and / or X3 interfaces contains an unsupported version of the standard specification in the header, the standard specifications do not require an error response message to be sent. This means that if the version of the standard specification used by the POI to send data via the X2 / X3 interface is not supported by the MF, the MF cannot notify the POI of this defect. This results in the POI being unable to perform any adaptation process to make the version of the standard specification used by the POI consistent with the version supported by the MF.

[0008] In addition, the POI using an unsupported version of the standard specification to send data to the MF via the X2 / X3 interface may cause the MF to be unable to send the X2 / X3 data to the law enforcement agency in the correct manner, which can lead to the data being misinterpreted and even discarded. In the prior art, the process of overcoming this drawback is to manually configure the POI in the NE to use a specific version of the standard specification for transmission via the X2 / X3 interface according to the version of the standard protocol supported by the MF. Summary of the Invention

[0009] In view of the above, an object of the present disclosure is to overcome the drawbacks associated with the transmission via the X2 and X3 interfaces. This object is achieved in a first aspect by a method performed by the LI ADMF in a telecommunication network.

[0010] The method of the first aspect includes: sending, via the X1 interface, a request associated with a destination to which the POI in the NE will send the intercepted data via the X2 and / or X3 interfaces during subsequent lawful interception. The request includes a destination identifier (DID) of the destination and version information that specifies at least one version of a transport protocol used by the POI to send the intercepted data to the destination identified by the DID via the X2 and / or X3 interfaces during subsequent lawful interception. The method further includes receiving, via the X1 interface, a response from the POI indicating whether the POI can use a version of the transport protocol equal to one of the versions in the sent version information to send the intercepted data via the X2 and / or X3 interfaces.

[0011] In other words, automatic protocol selection is performed via the X1 interface without any manual intervention. This method enables the exchange of data between the POI and the MF via the X2 and X3 interfaces using the highest version supported by both parties. This has the advantage that it avoids any intercepted data communicated via the X2 and X3 interfaces from being lost or misinterpreted. Moreover, it eliminates or at least reduces the need for manual configuration steps, which, like the cases requiring manual configuration in the prior art, increase the installation and maintenance costs and increase the risk of failures. Instead, the method of the first aspect provides a fully automatic configuration. For example, it is an enabler for deploying virtual network functions (VNF) implementations in a cloud scenario using, for example, a "one-click" configuration process. That is, the method of the first aspect reduces the operating expenses (OPEX) and reduces the risk of manual errors during installation and upgrade. Moreover, any protocol updates will be automatically reported between the entity POI / NE and the ADMF / MF without manual configuration, thereby eliminating or at least reducing the risk of manual errors.

[0012] In some embodiments, the received response specifies that the POI can use a version of the transport protocol equal to one of the versions in the sent version information to send the intercepted data via the X2 and / or X3 interfaces. In such an embodiment, the received response specifies the version of the transport protocol that the POI will use to send the intercepted data via the X2 and / or X3 interfaces.

[0013] In some embodiments, the received response specifies that the POI cannot use a version of the transport protocol equal to one of the versions in the sent version information to send the intercepted data via the X2 and / or X3 interfaces. In such an embodiment, the received response specifies the version of the transport protocol that the POI can use to send the intercepted data via the X2 and / or X3 interfaces.

[0014] In a further aspect, a method performed by a LI POI in a NE in a telecommunication network is provided. The method of this further aspect includes receiving, via an X1 interface, a request from a LI ADMF associated with a destination to which the POI will send intercepted data via an X2 and / or X3 interface during a subsequent lawful interception. The request includes a DID of the destination and version information that specifies at least one version of a transport protocol used by the POI to send the intercepted data to the destination identified by the DID via the X2 and / or X3 interface during the subsequent lawful interception. After receiving the request, the POI determines whether the POI is able to send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information. The determination includes comparing the received version information with version information already available in the POI that specifies at least one version of the transport protocol that the POI is able to use to send the intercepted data via the X2 and / or X3 interface. Then, a response is sent to the ADMF via the X1 interface, the response indicating whether the POI is able to send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information.

[0015] In some embodiments, it is determined that the POI is able to send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information. Such embodiments include determining the highest version of the transport protocol that the POI will use to send the intercepted data via the X2 and / or X3 interface. The determination utilizes the version information already available in the POI. The response sent then specifies that the POI will send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information, and the response sent also specifies the highest version of the transport protocol determined.

[0016] In some embodiments, it is determined that the POI is not able to send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information. Such embodiments include determining the highest version of the transport protocol that the POI is able to use to send the intercepted data via the X2 and / or X3 interface. The determination utilizes the version information already available in the POI. The response sent then specifies that the POI is not able to send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information, and the response sent also specifies the highest version of the transport protocol determined.

[0017] Requests sent by the ADMF and received by the POI can be a CreateDestinationRequest or a ModifyDestinationRequest in ETSI technical specification 103 221-1. Similarly, responses sent by the POI to the ADMF can be a CreateDestinationResponse or a ModifyDestinationResponse in ETSI technical specification 103 221-1, and in some embodiments, the response is an ErrorResponse in ETSI technical specification 103 221-1.

[0018] In yet another aspect, a computer system including a plurality of server blades is provided, each server blade including a processor and a memory, the memory containing instructions executable by the processor, whereby the computer system is operable to execute the method outlined above.

[0019] In yet another aspect, a computer program including instructions is provided, which when executed by at least one processor in a server blade in a computer system, causes the computer system to execute the method outlined above.

[0020] In yet another aspect, a carrier including the computer program as described above is provided, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer-readable storage medium.

[0021] These further aspects and embodiments of these further aspects provide the same effects and advantages as those outlined above in connection with the method of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1a-1b is a schematically illustrated block diagram of a LI system,

[0023] Figure 2a-2b is a flowchart of a method,

[0024] Figure 3a-3c is shown in Figure 2a-2b a signaling diagram of signals sent in the method shown, Figure 4 schematically illustrates a computer system, and

[0025] Figure 5a-5b schematically illustrates a corresponding computer system. DETAILED DESCRIPTION

[0026] Figure 1aA first functional representation of a telecommunications network 100 is schematically shown, including a core network 105 and an access network 103. In the access network 103, two communication entities are connected, namely a first communication entity 101 and a second communication entity 102. The access network may take the form of, for example, a 3GPP radio access network (RAN) or any other type of non-3GPP communication network connectable to the core network 105.

[0027] As will be recognized by those skilled in the art, the communication performed by the first communication entity 101 and the second communication entity 102 is achieved through a number of functional units in the access network 103 and the core network 105. For the sake of clarity of description, such functional units are not fully shown, but are only schematically represented and illustrated by a network element (NE) 107. In the context of 4G, the network element may be a mobility management entity (MME), a serving gateway (S-GW), a packet data network gateway (P-GW), etc. In the context of 5G, the network element 107 may take the form of, for example, 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 represented by the network element 107 in the core network 105 is that they may include a LI function in the form of an interception point (POI) 135. Thus, the POI 135 in Figure 1a is depicted as part of or embedded within the network element 107. However, the POI 135 may also be separated from the network element 107 with which it is associated. The core network 105 may be the core network of a serving network (SN), and the serving network (SN) may be a visited public land mobile network (VPLMN) or a home public land mobile network (HPLMN).

[0028] The core network 105 also includes an administrative function (ADMF) 108 and an intermediation and transfer function (MDF) 132 connected to a law enforcement agency (LEA) 131. Within the MDF 132, an intermediation function (MF) 133 and a transfer function (DF) 134 are configured to process the interception products and communication content (CC) received from the POI 135 in the form of interception-related information (IRI) and provide the IRI and CC to the LEA 131. The LEA 131 manages a law enforcement monitoring facility (LEMF) 136 that receives the IRI and CC from the DF 134.

[0029] As mentioned above, the communication between entities occurs via the X1, X2, and X3 interfaces. That is, the ADMF 108 communicates with the POI 135 in the MF 133, DF 134, and NE 107 via the X1 interface. The POI 135 in the NE 107 communicates with the MF 133 via the X2 and X3 interfaces. The ADMF 108 also communicates with the LEA 131 via the HI1 interface, and the DF 134 communicates with the LEMF 136 in the LEA 131 via the HI2 and HI3 interfaces.

[0030] Figure 1b Figure 4 schematically shows a second functional representation of the telecommunications network 100. In this second functional representation, the telecommunications network 100 is at least partially implemented by virtualization functions executed on virtual nodes 110 that utilize the hardware server platform 170. The MF 133, DF 134, ADMF 108, NE 107, and POI 135 are implemented in the functional layer 130 of virtualized network functions (VNFs) executed in the virtual nodes 110 via the virtualization layer 120. For example, the virtual node 111 is a collection of software instructions and associated data 112 that those skilled in the art will recognize. The LEA 131 and its LEMF 136 are connected to the hardware platform 170 via the intermediate network 109, the details of which are outside the scope of this disclosure. Although not explicitly shown in Figure 1b Figure 4, the communication between entities via the X1, X2, X3, HI1, HI2, and HI3 interfaces occurs as described above in connection with Figure 1a Figure 3.

[0031] The ADMF 108, MF 133, DF 134, and POI 135, and the LEMF 136 can all be implemented as software installed in one or more hardware devices, all of which include processing and storage resources configured to implement and process LI information, as will be illustrated in detail below.

[0032] Now turning to Figure 2a-2b Figure 5 Figure 3a-3c and continuing to refer to Figure 1a-1b Figure 4, embodiments of methods in the telecommunications network 100 will be described in more detail. The embodiments will illustrate how the various functional units and interfaces described above can be enhanced to provide effects and advantages associated with the communication between the POI and the MF 133 and / or DF 134 via the X2 and X3 interfaces.

[0033] Figure 2a Figure 6 shows a method including actions performed by the ADMF 108 in the telecommunications network 100 introduced and described above in connection with Figure 1a-1b Figure 3:

[0034] Action 201

[0035] The ADMF 108 sends, via the X1 interface, a request 303 associated with destinations 133, 134 to the POI 135 in the NE, where the POI is to send the intercepted data to the destinations 133, 134 via the X2 and / or X3 interfaces during a subsequent lawful interception. The request 303 includes the DIDs of the destinations 133, 134 and version information that specifies at least one version of the transport protocol to be used by the POI 135 to send the intercepted data to the destinations 133, 134 identified by the DIDs via the X2 and / or X3 interfaces during a subsequent lawful interception.

[0036] Action 203

[0037] The ADMF 108 receives, via the X1 interface, a response 305 from the POI 135, the response 305 indicating whether the POI 135 can use a version of the transport protocol equal to one of the versions in the version information sent in action 201 to send the intercepted data via the X2 and / or X3 interfaces.

[0038] The response 305 received in action 203 can be a response 325 that specifies that the POI 135 can use a version of the transport protocol equal to one of the versions in the sent version information to send the intercepted data via the X2 and / or X3 interfaces. In this case, the received response 325 specifies the version of the transport protocol that the POI 135 is to use to send the intercepted data via the X2 and / or X3 interfaces.

[0039] On the other hand, the response 305 received in action 203 can be a response 335 that specifies that the POI 135 cannot use a version of the transport protocol equal to one of the versions in the sent version information to send the intercepted data via the X2 and / or X3 interfaces. In this case, the received response 335 specifies the version of the transport protocol that the POI 135 can use to send the intercepted data via the X2 and / or X3 interfaces.

[0040] Figure 2b A method is shown that includes actions corresponding to those performed by the ADMF 108 as described above and performed by the POI 135:

[0041] Action 251

[0042] POI 135 receives request 303 associated with destinations 133, 134 from the ADMF via interface X1, where POI 135 will send the intercepted data to destinations 133, 134 via interfaces X2 and / or X3 during subsequent lawful interception. Request 303 includes the DID of destinations 133, 134 and version information that specifies at least one version of the transport protocol to be used by POI 135 to send the intercepted data to destinations 133, 134 identified by the DID via interfaces X2 and / or X3 during subsequent lawful interception.

[0043] Action 253

[0044] Then, POI 135 determines whether POI 135 can send the intercepted data via interfaces X2 and / or X3 using a version of the transport protocol equal to one of the versions in the received version information. This determination includes comparing the received version information with the version information already available in POI 135 that specifies at least one version of the transport protocol that POI 135 can use to send the intercepted data via interfaces X2 and / or X3.

[0045] Action 257

[0046] Then, POI 135 sends response 305 to the ADMF (108) via interface X1, and this response 305 indicates whether POI 135 can send the intercepted data via interfaces X2 and / or X3 using a version of the transport protocol equal to one of the versions in the received version information.

[0047] If it is determined in action 253 that POI 135 can send the intercepted data via interfaces X2 and / or X3 using a version of the transport protocol equal to one of the versions in the received version information, then the method further includes determination action 255 of determining the highest version of the transport protocol that POI 135 will use to send the intercepted data via interfaces X2 and / or X3. This determination action 255 utilizes the version information already available in POI 135. The response 305 sent in action 257 is then response 325 that specifies that POI 135 will send the intercepted data via interfaces X2 and / or X3 using a version of the transport protocol equal to one of the versions in the received version information. Moreover, the response 325 sent in action 257 also specifies the highest version of the transport protocol determined in action 255.

[0048] On the other hand, if it is determined in operation 253 that POI 135 cannot send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information, then determination operation 255 determines the highest version of the transport protocol that POI 135 can use to send the intercepted data via the X2 and / or X3 interface, and the determination in operation 255 utilizes the version information already available in POI 135. The response 305 sent in operation 257 is then a response 335 that specifies that POI 135 cannot send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information. Also, the response 335 sent in operation 257 specifies the highest version of the transport protocol determined in operation 255.

[0049] The request 303 sent by the ADMF 108 in operation 201 and received by the POI 135 in operation 251 may be a CreateDestinationRequest or a ModifyDestinationRequest in ETSI technical specification 103 221-1. Then, such a request may require adding a field (such as "List of DIDProtocolVersions") to the destination details as explained in Table 14 of ETSI technical specification 103 221-1:

[0050]

[0051] Then, the actual CreateDestinationRequest can be implemented as follows:

[0052]

[0053] As those skilled in the art will recognize, the ModifyDestinationRequest will include a pattern similar to the CreateDestinationRequest illustrated above.

[0054] Similarly, the response 325 sent by the POI 135 in operation 257 and received by the ADMF 108 in operation 203 may be a CreateDestinationResponse or a ModifyDestinationResponse in ETSI technical specification 103 221-1. Such a response will include a pattern similar to the CreateDestinationRequest illustrated above. That is:

[0055]

[0056] Then, it may be necessary to add a field (e.g., "List of DIDProtocolVersions") to the destination details as explained in Tables 13 and 17 of ETSI Technical Specification 103 221-1:

[0057]

[0058] It should be noted that the response may also follow the pattern of the prior art CreateDestinationResponse or ModifyDestinationResponse.

[0059] In the case where POI 135 cannot send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information, the response 305 may be the response 335, which may be the ErrorResponse in ETSI Technical Specification 103 221-1. Such an error response may include patterns such as:

[0060]

[0061] Then, such an error response may be required to add an error code and a field (e.g., "UnsupportedDIDProtocolVersion") to the error code as explained in Table 46 of ETSI Technical Specification 103 221-1 (note that 6030 is an example of a possible new error code to be used, and any value starting from 6000 is acceptable):

[0062]

[0063] Now turning to Figure 4 and continuing to refer to FIGS. 1-3, the computer system 400 will be described in detail. The computer network 400, which may correspond to at least a portion of the telecommunications system 100, includes a plurality of server blades 411, which include a processor 402 and a memory 404. The memory 404 contains instructions executable by the processor 402, whereby the computer system 400 is operable to:

[0064] - Send, via the X1 interface, a request associated with a destination to an interception point (POI) in a network element (NE), where the POI is to send the intercepted data to the destination via the X2 and / or X3 interface during a subsequent lawful interception, and the request includes:

[0065] - The destination identifier (DID) of the destination,

[0066] - Version information that specifies at least one version of the transport protocol for use by the POI to send the intercepted data to the destination identified by the DID via the X2 and / or X3 interfaces during subsequent lawful interception, and

[0067] - Receive a response from the POI via the X1 interface indicating whether the POI is able to send the intercepted data via the X2 and / or X3 interfaces using a version of the transport protocol equal to one of the versions in the sent version information.

[0068] Instructions executable by the processor 402 may be software in the form of a computer program 443. The computer program 443 may be contained in or by a carrier 442 that provides the computer program 443 to the memory 404 and the processor 402. The carrier 442 may take any suitable form, including an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0069] In some embodiments, the computer system 400 is operable such that the received response specifies that the POI is able to send the intercepted data via the X2 and / or X3 interfaces using a version of the transport protocol equal to one of the versions in the sent version information, and is configured such that the received response specifies the version of the transport protocol that the POI will use to send the intercepted data via the X2 and / or X3 interfaces.

[0070] In some embodiments, the computer system 400 is operable such that the received response specifies that the POI is not able to send the intercepted data via the X2 and / or X3 interfaces using a version of the transport protocol equal to one of the versions in the sent version information, and is configured such that the received response specifies the version of the transport protocol that the POI is able to use to send the intercepted data via the X2 and / or X3 interfaces.

[0071] Continuing reference Figure 4 And continuing to refer to FIGS. 1-3, the computer system 400 will be described in detail. A computer network 400 that may correspond to at least a portion of the telecommunications system 100 includes a plurality of server blades 411 that include a processor 402 and a memory 404. The memory 404 contains instructions executable by the processor 402, whereby the computer system 400 is operable to:

[0072] - Receive, via the X1 interface, a request from the LI management function (ADMF) associated with the destination to which the POI will send the intercepted data via the X2 and / or X3 interfaces during subsequent lawful interception, where the request includes:

[0073] - A destination identifier (DID) of the destination, and

[0074] - Version information that specifies at least one version of the transport protocol used by the POI to send the intercepted data to the destination identified by the DID via the X2 and / or X3 interfaces during subsequent legal interceptions.

[0075] - Determine whether the POI can use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interfaces, the determination including comparing the received version information with the version information already available in the POI that specifies at least one version of the transport protocol that the POI can use to send the intercepted data via the X2 and / or X3 interfaces, and

[0076] - Send a response to the ADMF via the X1 interface, the response indicating whether the POI can use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interfaces.

[0077] Instructions executable by the processor 402 can be software in the form of a computer program 443. The computer program 443 can be contained in or contained by a carrier 442, and the carrier 442 can provide the computer program 443 to the memory 404 and the processor 402. The carrier 442 can take any suitable form, including an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0078] In some embodiments, the computer system 400 is operable such that it is determined that the POI can use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interfaces, and is further operable to:

[0079] - Determine the highest version of the transport protocol that the POI will use to send the intercepted data via the X2 and / or X3 interfaces, the determination utilizing the version information already available in the POI, and being operable such that:

[0080] - The sent response specifies that the POI will use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interfaces, and

[0081] - The sent response specifies the determined highest version of the transport protocol.

[0082] In some embodiments, the computer system 400 is operable such that it is determined that the POI cannot use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interfaces, and is further operable to:

[0083] - Determine the highest version of the transport protocol that the POI can use to send the intercepted data via the X2 and / or X3 interface, the determination utilizing the version information already available in the POI, and being operable to cause:

[0084] - The response sent specifies that the POI cannot use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interface, and

[0085] - The response sent specifies the highest version of the transport protocol determined.

[0086] In some embodiments, the computer system 400 is operable such that the request is one of: in the European Telecommunications Standards Institute (ETSI) Technical Specification 103 221-1:

[0087] - CreateDestinationRequest, or

[0088] - ModifyDestinationRequest.

[0089] In some embodiments, the computer system 400 is operable such that the response is one of: in the ETSI Technical Specification 103 221-1:

[0090] - CreateDestinationResponse, or

[0091] - ModifyDestinationResponse.

[0092] In some embodiments, the computer system 400 is operable such that the response is ErrorResponse in the ETSI Technical Specification 103 221-1.

[0093] Now turning to Figure 5a and continuing to refer to FIG. 1- Figure 4 , the computer system 500 will be described in detail. The computer system 500 includes:

[0094] - A sending module (501) configured to send, via the X1 interface, a request associated with a destination to which the POI in the network element (NE) will send the intercepted data via the X2 and / or X3 interface during subsequent lawful interception, wherein the request includes:

[0095] - A destination identifier (DID) of the destination,

[0096] - Version information that specifies at least one version of the transport protocol to be used by the POI to send the intercepted data to the destination identified by the DID via the X2 and / or X3 interfaces during subsequent lawful interception, and

[0097] - A receiving module (503) configured to receive, via the X1 interface, a response from the POI indicating whether the POI is able to use a version of the transport protocol equal to one of the versions in the sent version information to send the intercepted data via the X2 and / or X3 interfaces.

[0098] The computer system 500 may include other modules configured to perform in a manner similar to, for example, the computer system 400 described above in conjunction with Figure 4 described.

[0099] Now turning to Figure 5b and continuing to refer to FIG. 1 - Figure 4 , the computer system 550 will be described in detail. The computer system 550 includes:

[0100] - A receiving module (551) configured to receive, via the X1 interface, a request from the LI management function (ADMF) associated with the destination to which the POI will send the intercepted data via the X2 and / or X3 interfaces during subsequent lawful interception, wherein the request includes:

[0101] - The destination identifier (DID) of the destination, and

[0102] - Version information that specifies at least one version of the transport protocol to be used by the POI to send the intercepted data to the destination identified by the DID via the X2 and / or X3 interfaces during subsequent lawful interception,

[0103] - A determination module (553) configured to determine whether the POI is able to use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interfaces, the determination including comparing the received version information with the version information already available in the POI that specifies at least one version of the transport protocol that the POI is able to use to send the intercepted data via the X2 and / or X3 interfaces, and

[0104] - A sending module (555) configured to send, via the X1 interface, a response to the ADMF indicating whether the POI is able to use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interfaces.

[0105] The computer system 550 may include other modules configured to perform in a manner similar to, for example, the above in conjunction with Figure 4Execute in a similar manner to the described computer system 400.

Claims

1. A method performed by a Lawful Interception LI Management Function ADMF (108) in a telecommunications network (100), the method comprising: - Sending (201) a request (303) associated with a destination (133, 134) to an Interception Point POI (135) in a network element NE (107) via an X1 interface, wherein the POI (135) is to send the intercepted data to the destination (133, 134) via an X2 and / or X3 interface during a subsequent lawful interception, wherein the request (303) comprises: - A Destination Identifier DID of the destination (133, 134), - Version information specifying at least one version of a transport protocol to be used by the POI (135) to send the intercepted data to the destination (133, 134) identified by the DID via the X2 and / or X3 interface during the subsequent lawful interception, and - Receiving (203) a response (305) from the POI (135) via the X1 interface, the response (305) indicating that the POI (135) cannot send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the sent version information.

2. The method according to claim 1, wherein: - The received response (305, 325) specifies that the POI (135) can send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the sent version information, and - The received response (305, 325) specifies the version of the transport protocol that the POI (135) is to use to send the intercepted data via the X2 and / or X3 interface.

3. The method according to claim 1, wherein: - The received response (305, 335) specifies that the POI (135) cannot send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the sent version information, and - The received response (305, 335) specifies the version of the transport protocol that the POI (135) can use to send the intercepted data via the X2 and / or X3 interface.

4. The method according to any one of claims 1 to 3, wherein, The request (303) is one of the following in the European Telecommunications Standards Institute ETSI Technical Specification 103 221-1: - CreateDestinationRequest, or - ModifyDestinationRequest.

5. The method according to any one of claims 1 to 3, wherein The response (305, 325) is one of the following in the ETSI Technical Specification 103 221-1: - CreateDestinationResponse, or - ModifyDestinationResponse.

6. The method according to claim 1 or 3, wherein The response (305, 335) is an ErrorResponse as defined in ETSI Technical Specification 103 221-1.

7. A method performed by a Lawful Interception Interception Point of Interest (POI) (135) in a Network Element NE (107) in a telecommunication network (100), the method comprising: - receiving (251) via an X1 interface from a Lawful Interception Administration and Management Function (ADMF) (108) a request (303) associated with a destination (133, 134), wherein the POI (135) is to send intercepted data to the destination (133, 134) via an X2 and / or X3 interface during a subsequent lawful interception, and wherein the request (303) comprises: - a Destination Identifier (DID) of the destination (133, 134), and - version information specifying at least one version of a transport protocol to be used by the POI (135) to send the intercepted data to the destination (133, 134) identified by the DID via the X2 and / or X3 interface during the subsequent lawful interception, - determining (253) whether the POI (135) can use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interface, the determining (253) comprising: comparing the received version information with version information already available in the POI (135), the version information already available in the POI (135) specifying at least one version of a transport protocol that the POI (135) can use to send the intercepted data via the X2 and / or X3 interface, and - sending (257) via the X1 interface to the ADMF (108) a response (305) indicating that the POI (135) cannot use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interface.

8. The method according to claim 7, wherein: - it is determined (253) that the POI (135) can use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interface, and the method further comprises: - determining (255) the highest version of the transport protocol that the POI (135) is to use to send the intercepted data via the X2 and / or X3 interface, the determining (255) using the version information already available in the POI (135), and wherein: - the sent response (305, 325) specifies that the POI (135) is to use a version of the transport protocol equal to one of the versions in the received version information to send the intercepted data via the X2 and / or X3 interface, and - the sent response (305, 325) specifies the highest version of the transport protocol so determined (255).

9. The method according to claim 7, wherein: - It is determined (253) that the POI (135) cannot send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information, and the method further includes: - It is determined (255) the highest version of the transport protocol that the POI (135) can use to send the intercepted data via the X2 and / or X3 interface, the determination (255) making use of the version information already available in the POI (135), and wherein: - The response (305, 335) sent specifies that the POI (135) cannot send the intercepted data via the X2 and / or X3 interface using a version of the transport protocol equal to one of the versions in the received version information, and - The response (305, 335) sent specifies the highest version of the transport protocol determined (255).

10. The method according to any one of claims 7 to 9, wherein The request (303) is one of the following in the European Telecommunications Standards Institute ETSI Technical Specification 103 221-1: - CreateDestinationRequest, or - ModifyDestinationRequest.

11. The method according to any one of claims 7 to 9, wherein The response (305, 325) is one of the following in the ETSI Technical Specification 103 221-1: - CreateDestinationResponse, or - ModifyDestinationResponse.

12. The method according to claim 7 or 9, wherein, The response (305, 335) is ErrorResponse in the ETSI Technical Specification 103221-1.

13. A computer system (400) includes a plurality of server blades (411), each server blade (411) including a processor (402) and a memory (404), the memory (404) containing instructions executable by the processor (402), whereby the computer system (400) is operable to execute the method according to any one of claims 1 to 6.

14. A computer system (400) includes a plurality of server blades (411), each server blade (411) including a processor (402) and a memory (404), the memory (404) containing instructions executable by the processor (402), whereby the computer system (400) is operable to execute the method according to any one of claims 7 to 9.

15. A computer-readable storage medium includes a computer program (443), which when executed on at least one processor (402) in a server blade (411) of a computer system (400) causes the computer system (400) to execute the method according to any one of claims 1 to 6.

16. A computer-readable storage medium, comprising a computer program (443), which, when executed on at least one processor (402) in a server blade (411) in a computer system (400), causes the computer system (400) to perform the method according to any one of claims 7 to 9.

Citation Information

Patent Citations

  • System, Apparatus for Content Delivery for Internet Traffic and Methods Thereof

    US20110280216A1

  • Method and Apparatus for Receiving Information From a Communications Network

    US20140233384A1