EP2941936B1 - Apparatus, system and method of lawful interception (li) in a cellular network - Google Patents

Apparatus, system and method of lawful interception (li) in a cellular network Download PDF

Info

Publication number
EP2941936B1
EP2941936B1 EP13870368.1A EP13870368A EP2941936B1 EP 2941936 B1 EP2941936 B1 EP 2941936B1 EP 13870368 A EP13870368 A EP 13870368A EP 2941936 B1 EP2941936 B1 EP 2941936B1
Authority
EP
European Patent Office
Prior art keywords
enb
node
content
lawful interception
user equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP13870368.1A
Other languages
German (de)
French (fr)
Other versions
EP2941936A1 (en
EP2941936A4 (en
Inventor
Alexander Sirotkin
Geng Wu
Achim Luft
Alexandre S. STOJANOVSKI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Publication of EP2941936A1 publication Critical patent/EP2941936A1/en
Publication of EP2941936A4 publication Critical patent/EP2941936A4/en
Application granted granted Critical
Publication of EP2941936B1 publication Critical patent/EP2941936B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H04B7/0486—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting taking channel rank into account
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • H04B7/0626—Channel coefficients, e.g. channel state information [CSI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • H04B7/0632—Channel quality parameters, e.g. channel quality indicator [CQI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0023—Interference mitigation or co-ordination
    • H04J11/005—Interference mitigation or co-ordination of intercell interference
    • H04J11/0053—Interference mitigation or co-ordination of intercell interference using co-ordinated multipoint transmission/reception
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
    • H04L63/304—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information intercepting circuit switched data communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/30—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information
    • H04L63/306—Network architectures or network communication protocols for network security for supporting lawful interception, monitoring or retaining of communications or communication related information intercepting packet switched data communications, e.g. Web, Internet or IMS communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0222—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave in packet switched networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/005—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by adjustment in the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/0055—Synchronisation arrangements determining timing error of reception due to propagation delay
    • H04W56/0095—Synchronisation arrangements determining timing error of reception due to propagation delay estimated based on signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Some embodiments described herein generally relate to apparatus, system and method of Lawful Interception (LI) in a cellular network.
  • LI Lawful Interception
  • Some communication networks may enable Lawful interception (LI), for example, for obtaining data, for example, communication network data, pursuant to lawful authority, e.g., for the purpose of analysis and/or evidence.
  • the obtained data may include, for example, signaling, network management information, and/or content of communications.
  • LI may be performed by an element of a core network, for example, a Gateway (GW), e.g., a Serving Gateway (S-GW) or a Packet-Data-Network (PDN) Gateway (P-GW).
  • GW Gateway
  • S-GW Serving Gateway
  • PDN Packet-Data-Network Gateway
  • the GW may be able to apply the LI to communications, which are processed and/or transferred by the GW. However, the GW may not be able to apply the LI to any other communications of the cellular network, which are not handled by the GW.
  • US 2011/0075557 A1 relates to a system and method for offloading selected data to an alternate communication network.
  • the offloading provides another route for selected packet traffic that can relieve the burden on a mobile operator's network, such as the backhaul and core networks.
  • a mobile operator's network such as the backhaul and core networks.
  • a offload gateway is provided that inspects packets and determines those packets to offload to an alternate network as well as providing mobility management to allow for seamless handoffs and gateway relocations.
  • US 20110096669 A1 relates to a method to enhance resolution of location information of a mobile user in an Evolved Packet communication System.
  • the system comprises a Mobility Management Entity that provides the user with at least one tracking area in which the user is able to move without location information being reported,
  • the method comprises the following steps: receiving to the Mobility Management Entity, a location activation message valid for the user; receiving to the Mobility Management Entity, a service request related to the user; detecting in the Mobility Management Entity, user location information with higher resolution than the at least one tracking area level resolution; and sending from the Mobility Management Entity, a monitoring message comprising high resolution information of the user's location within the at least one tracking area.
  • Discussions herein utilizing terms such as, for example, “processing”, “computing”, “calculating”, “determining”, “establishing”, “analyzing”, “checking”, or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.
  • processing may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.
  • plural and “a plurality”, as used herein, include, for example, “multiple” or “two or more”.
  • a plurality of items includes two or more items.
  • references to "one embodiment,” “an embodiment,” “demonstrative embodiment,” “various embodiments,” etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one embodiment” does not necessarily refer to the same embodiment, although it may.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a Smartphone device, a server computer, a handheld computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a cellular network, a cellular node, a Wireless Local Area Network (WLAN), a Multiple Input Multiple Output (MIMO) transceiver
  • Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing Long Term Evolution (LTE) specifications (including “TS 33.106 - 3G security; Lawful interception requirements” ; “TS 33.107 - 3G security; Lawful interception architecture and functions” ; “TS 23.401 - General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access” ; “TS 36.413 - Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)” ; “TS 36.423 - Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP); and “36.300 - Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2" )) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with
  • Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBeeTM, Ultra-Wideband (UWB), Global System for Mobile communication (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks
  • wireless device includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like.
  • a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer.
  • the term "wireless device” may optionally include a wireless service.
  • a wireless communication unit which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
  • Some demonstrative embodiments are described herein with respect to a LTE cellular system. However, other embodiments may be implemented in any other suitable cellular network, e.g., a 3G cellular network, a 4G cellular network, a 5G cellular network, a WiMax cellular network, and the like.
  • a 3G cellular network e.g., a 3G cellular network, a 4G cellular network, a 5G cellular network, a WiMax cellular network, and the like.
  • antenna may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays.
  • the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements.
  • the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
  • the antenna may include, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like.
  • the term "cell”, as used herein, may include a combination of network resources, for example, downlink and optionally uplink resources.
  • the resources may be controlled and/or allocated, for example, by a cellular node (also referred to as a "base station"), or the like.
  • the linking between a carrier frequency of the downlink resources and a carrier frequency of the uplink resources may be indicated in system information transmitted on the downlink resources.
  • FIG. 1 schematically illustrates a block diagram of a system 100, in accordance with some demonstrative embodiments.
  • system 100 may include one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums 108.
  • Wireless mediums 108 may include, for example, a radio channel, a cellular channel, an RF channel, a WLAN channel, a Wireless Fidelity (WiFi) channel, an IR channel, and the like.
  • One or more elements of system 100 may optionally be capable of communicating over any suitable wired communication links.
  • system 100 may include one or more cellular networks, e.g., including one or more cells controlled by one or more nodes, e.g., a node 104 and/or a node 106.
  • nodes e.g., a node 104 and/or a node 106.
  • nodes 104 and/or 106 may include an Evolved Node B (eNB).
  • nodes 104 and/or 106 may be configured to perform radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UEs and eNB radios, e.g., Dynamic allocation of resources to UEs in both uplink and downlink, header compression, link encryption of user data streams, packet routing of user data towards a destination, e.g., another eNB or an Evolved Packet Core (EPC), scheduling and/or transmitting paging messages, e.g., incoming calls and/or connection requests, broadcast information coordination, measurement reporting, and/or any other operations.
  • RRM radio resource management
  • radio bearer control radio admission control
  • access control access control
  • connection mobility management e.g., Dynamic allocation of resources to UEs in both uplink and downlink
  • resource scheduling between UEs and eNB radios e.g., Dynamic allocation
  • nodes 104 and/or 106 may include any other functionality and/or may perform the functionality of any other cellular node, e.g., a Node B (NB) or any other node or device.
  • NB Node B
  • node 104 may communicate with a User Equipment (UE) 102 via a cellular link.
  • UE 102 may include, for example, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a mobile internet device, a handheld computer, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a "Carry Small Live Large” (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an "Origami" device or computing device,
  • UE 102, node 104 and/or node 106 may include one or more wireless communication units to perform wireless communication between UE 102, node 104, node 106 and/or with one or more other wireless communication devices.
  • UE 102 may include a wireless communication unit 110 and/or nodes 104 and/or 106 may include a wireless communication unit 130.
  • wireless communication units 110 and 130 may include, or may be associated with, one or more antennas.
  • wireless communication unit 110 may be associated with at least two antennas, e.g., antennas 112 and 114; and/or wireless communication unit 130 may be associated with at least two antennas, e.g., antennas 132 and 134.
  • wireless communication units 110 and/or 130 may be associated with any other number of antennas.
  • antennas 112, 114, 132 and/or 134 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data.
  • antennas 112, 114,132 and/or 134 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays.
  • antennas 112, 114, 132 and/or 134 may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like.
  • antennas 112, 114, 132 and/or 134 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 112, 114, 132 and/or 134 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
  • wireless communication unit 130 may include one or more radios 142
  • wireless communication unit 110 may include one or more radios 143.
  • radios 142 and/or 143 may include one or more wireless transmitters, receivers and/or transceivers able to send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data.
  • radios 143 and/or 142 may include at least a cellular transceiver to communicate between US 102 and nodes 104 and/or 106 over a cellular link.
  • radios 142 and/or 143 may include a multiple input multiple output (MIMO) transmitters receivers system (not shown), which may be capable of performing antenna beamforming methods, if desired.
  • MIMO multiple input multiple output
  • radios 142 and/or 143 may include a turbo decoder and/or a turbo encoder (not shown) for encoding and/or decoding data bits into data symbols, if desired.
  • radios 142 and/or 143 may include OFDM and/or SC-FDMA modulators and/or demodulators (not shown) configured to communicate OFDM signals over downlink channels, e.g., between node 104 and UE 102, and SC-FDMA signals over uplink channels, e.g., between UE 102 and nodes 104 and/or 106.
  • system 100 may include one or more elements of a cellular network.
  • system 100 may also include a Mobility Management Entity (MME) 180.
  • MME Mobility Management Entity
  • MME 180 may be configured to perform network access control, for example, facilitating access of UE 102 to the cellular network. Additionally or alternatively, MME 180 may be configured to perform Mobility Management. Additionally or alternatively, MME 180 may be configured to perform tracking area management, e.g., by allocating and reallocating a tracking area identity list to a UE, e.g., UE 102. MME 180 may perform any other additional/and/or alternative functionality.
  • MME 180, node 104 and/or node 106 may include one or more communication units to perform communication between MME 180, node 104, node 106 and/or with one or more other cellular network devices, e.g., one or more Core Network (CN) devices.
  • MME 180 102 may include a communication unit 182
  • node 104 may include a communication unit 190
  • node 106 may include a communication unit 195.
  • wireless communication unit 130 and communication unit 190 may be implemented as separate elements of node 106. In other embodiments, one or more elements of wireless communication unit 130 may perform one or more functionalities of communication unit 190; and/or one or more elements of communication unit 190 may perform one or more functionalities of communication unit 130.
  • communication unit 182 may include one or more message senders (also referred to as “transmitters” (Tx)) 184 and/or one or more messages receivers ("receivers" (Rx)) 186; communication unit 190 may include one or more transmitters (Tx) 192 and/or one or more receivers (Rx) 194; and/or communication unit 195 may include one or more transmitters (Tx) 196 and/or one or more receivers (Rx) 197.
  • message senders also referred to as "transmitters” (Tx)
  • Rx messages receivers
  • communication unit 190 may include one or more transmitters (Tx) 192 and/or one or more receivers (Rx) 194
  • communication unit 195 may include one or more transmitters (Tx) 196 and/or one or more receivers (Rx) 197.
  • MME 180 may communicate with nodes 104 and/or 106 via one or more interface links, for example, S1 Application Protocol (S1AP or S1) links, e.g., SI-MME links 181.
  • S1AP S1 Application Protocol
  • messages senders 184, 192 and/or 196 may include S1AP message senders configured to send messages over the S1AP links; and/or receivers 186, 194 and/or 197 may include S1AP receivers configured to receive messages over the S1AP links.
  • nodes 104 and 106 may communicate via one or more interface links, for example, X2 Application protocol (X2 or X2AP) links 105.
  • message senders 184, 192 and/or 196 may include X2AP message senders configured to send messages over X2 links 105; and/or receivers 186, 194 and/or 197 may include X2AP receivers configured to receive messages over X2 links 105.
  • UE 102, node 104, node 106 and/or MME 180 may also include, for example, one or more of a processor 124, an input unit 116, an output unit 118, a memory unit 120, and a storage unit 122.
  • UE 102, node 104, node 106 and/or MME 180 may optionally include other suitable hardware components and/or software components.
  • some or all of the components of one or more of UE 102, node 104, node 106 and/or MME 180 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links.
  • components of one or more of UE 102, node 104, node 106 and/or MME 180 may be distributed among multiple or separate devices.
  • Processor 124 includes, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller.
  • Processor 124 executes instructions, for example, of an Operating System (OS) of UE 102, node 104, node 106 and/or MME 180 and/or of one or more suitable applications.
  • OS Operating System
  • Input unit 116 includes, for example, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device.
  • Output unit 118 includes, for example, a monitor, a screen, a touch-screen, a flat panel display, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices.
  • CTR Cathode Ray Tube
  • LCD Liquid Crystal Display
  • Memory unit 120 includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units.
  • Storage unit 122 includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units.
  • Memory unit 120 and/or storage unit 122 may store data processed by UE 102, node 104, node 106 and/or MME 180.
  • MME 180 may be configured to manage Lawful Interception (LI) within system 100.
  • MME 180 may receive LI configuration information to configure the LI, e.g., in accordance with LI requirements of a Law Enforcement Monitoring Facility (LEMF) 161.
  • LMF Law Enforcement Monitoring Facility
  • MME 180 may receive the LI configuration information from LEMF 161 via an Administration Function (ADMF) interface and/or any other interface.
  • ADMF Administration Function
  • the LI may be applied with respect to content communicated with UE 102, e.g., as described below.
  • one or more elements of system 100 may be configured to perform LI with respect to content processed by, transferred through and/or handled by the LI handling elements, e.g., as described below.
  • the LI handling elements may include at least one Core Network (CN) entity of the cellular network, which may be configured to perform LI with respect to content handled by, processed by and/or transferred by the CN entity.
  • CN Core Network
  • the CN entity may include a GW 167.
  • the GW 167 may interface, for example, between nodes 104 and/or 106 and one or more application servers 169, which may exchange content with UE 102, e.g., via nodes 104 and/or 106.
  • GW 167 may include a Serving Gateway (S-GW), a Packet-Data-Network (PDN) Gateway (P-GW), or any other GW.
  • S-GW Serving Gateway
  • PDN Packet-Data-Network Gateway
  • P-GW Packet-Data-Network Gateway
  • performing LI at GW 167 may not be enough to assure LI is performed with respect to all content communicated with UE 102, for example, if some of the content which is communicated with UE 102 is not handled by, processed by and/or transferred by GW 167, e.g., as described below.
  • a node e.g., node 104 and/or 106
  • a node my be configured to enable performing LI for one or more UEs, e.g., UE 102, connected to the node, as described below.
  • node 104 may be configured to receive an indication ("LI indication") that UE 102 is to be subject to LI and/or that node 104 is to enable LI for UE 102.
  • LI indication an indication that UE 102 is to be subject to LI and/or that node 104 is to enable LI for UE 102.
  • node 104 may receive the LI indication from a network entity, e.g., MME 180, for example, via an S1 link 181, e.g., as described below.
  • a network entity e.g., MME 180
  • S1 link 181 e.g., as described below.
  • node 104 may receive the LI indication from another node, e.g., node 106, for example, via X2 link 105, e.g., as described below.
  • node 104 may include a controller 144 configured to disable one or more operations with respect to content to be communicated with UE 102, for example, based on the Li indication, e.g., as described below.
  • the one or more operations may include operations ("LI disturbing operations"), which may affect and/or disturb an ability to apply LI to the content communicated with UE 102, e.g., as described below.
  • LI disturbing operations operations which may affect and/or disturb an ability to apply LI to the content communicated with UE 102, e.g., as described below.
  • disabling the one or more LI disturbing operations with respect to the content to be communicated with UE 102 may enable performing LI with respect to the content, e.g., as described below.
  • disabling the one or more LI disturbing operations with respect to the content to be communicated with UE 102 may enable ensuring that content which has not been subject to LI is not to be communicated with UE 102, e.g., as described below.
  • disabling the one or more LI disturbing operations with respect to the content to be communicated with UE 102 may enable informing a LI entity, e.g., LEMF 161 regarding content which communicated with UE 102, e.g., as described below.
  • a LI entity e.g., LEMF 161 regarding content which communicated with UE 102
  • node 104 may disable the one or more LI disturbing operations with respect to content communicated between node 104 and UE 102.
  • the content may include, for example, content, which has not been communicated via a CN entity and/or is not subject to LI by the CN entity, for example, a LI handling element, e.g., GW 167.
  • node 104 disables the one or more operations with respect to content communicated between node 104 and UE 102, and which has not be subject to LI by GW 167.
  • node 104 may be configured to perform edge caching, e.g., as described below.
  • node 104 may include at least one cache 145 to internally store content communicated with one or more UEs, for example, UE 102, e.g., content requested by UE 102 and/or content received from UE 102.
  • node 104 may retrieve the content from cache 145, for example, instead of retrieving the content from the CN, e.g., via GW 167.
  • node 104 may communicate the content retrieved from cache 145 to UE 102 and/or to one or more other UEs, e.g., upon receiving a request for content, which is stored in cache 145.
  • node 104 may utilize any other caching mechanism and/or algorithms, for example, proactive caching, to manage internal caching of content in cache 145.
  • the content retrieved from internal cache 145 of node 104 may not be subject to LI by the CN entity performing the LI, e.g., GW 167.
  • controller 144 may be configured to disable edge caching of content to be communicated with UE 102, for example, based on the LI indication, e.g., as described below.
  • node 104 may be configured to perform traffic offloading, for example, by communicating content via one or more routes, which do not involve the CN entity performing the LI, e.g., GW 167.
  • node 104 may be configured to communicate with a network, e.g., the Internet, directly or via any other route not involving the CN entity performing the LI.
  • node 104 may be able to communicate content between the Internet and UE 102, e.g., without the content being subject to LI by GW 167.
  • node 104 may be configured to perform the offloading according to a Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN) mechanism, or any other offloading mechanism.
  • IP Internet-Protocol
  • SIPTO Traffic Offload
  • LN Local Network
  • controller 144 may be configured to disable traffic offloading, e.g., SIPTO@LN or any other traffic offloading, of content to be communicated with UE 102, for example, based on the LI indication, e.g., as described below.
  • traffic offloading e.g., SIPTO@LN or any other traffic offloading
  • one or more elements of system 100 may be configured to enable notifying a node, e.g., node 104, that at least one UE connected to the node, e.g., UE 102, is subject to LI.
  • receiver 194 may be configured to receive a message including a LI Information Element (IE) indicating node 104 is to enable LI for one or more UEs connected to node 104, e.g., as described below.
  • IE LI Information Element
  • the LI IE may be sent by MME 180, e.g., by message sender 184, for example, via S1AP signaling, e.g., over S1 link 181.
  • the LI IE may be sent by node, e.g., by message sender 196, for example, via X2AP signaling, e.g., over X2 link 105.
  • controller 144 may be configured to take actions to make the content accessed by the UEs, which are subject to LI, available for LI.
  • the LI notification to node 104 may relate to one or more particular UEs, for example, to indicate that the one or more particular UEs are to be subject to LI, e.g., while one or more other UEs may not be subject to LI.
  • the LI IE may indicate that UE 102 is to be subject to LI, e.g., while one or more other UEs are not to be subject to LI.
  • controller 144 may disable, e.g., based on the LI IE, one or more operations with respect to content to be communicated with the one or more UEs, which are subject to LI.
  • the LI notification to node 104 may globally relate to all UEs connected to node 104, for example, to indicate all UEs connected to node 104 are to be subject to LI.
  • controller 144 may disable, e.g., based on the LI IE, one or more operations with respect to content to be communicated with all UEs connected to node 104.
  • the actions taken by controller 144 with respect to the UEs, which are indicated to be subject top LI may include, for example, disabling caching and/or offloading.
  • controller 144 may control node 104 to disable caching and/or offloading with respect to content to be communicated with UE 102, e.g., if the LI indication indicated that UE 102 is to be subject to LI.
  • controller 144 may, for example, control node 104 to communicate the content for UE 102 via GW 167, e.g., instead of retrieving the content from cache 145 and/or via the SIPTO@LN mechanism.
  • the actions taken by controller 144 with respect to the UEs, which are indicated to be subject to LI may include, for example, notifying one or more CN entities, e.g., GW 167, MME 180, the ADMF and/or any other network entity, about content accessed by the UE, which is indicated to be subject to LI.
  • CN entities e.g., GW 167, MME 180, the ADMF and/or any other network entity
  • the actions taken by controller 144 with respect to the UEs, which are indicated to be subject top LI may include any other additional or alternative action.
  • controller 144 may be configured to ensure that the one or more UEs, which are subject to LI, may not be able to detect the LI.
  • controller 144 may control node 104 to add a delay, e.g., when serving content from cache 145 to the UEs connected to node 104.
  • controller 144 may add the delay, for example, only when some of the UEs are subject to LI, e.g., while one or more other UEs are not subject to LI.
  • the LI may not affect normal operation of the node 104 in a manner apparent to UE 102.
  • MME 180 may receive LI configuration information defining one or more UEs, e.g., including UE 102, to be subject to LI.
  • MME 180 may receive the LI configuration information from LEMF 161, e.g., as described above.
  • MME 180 may be able to indicate to node 104 that LI is to be enabled with respect to the one or more UEs. For example, MME 180 may indicate to node 104 that node 104 is to disable one or more LI disturbing operations with respect to content to be communicated with the one or more UEs. In one example, MME 180 may indicate to node 104 that node 104 is to disable caching and/or offloading with respect to content to be communicated with the one or more UEs, e.g., as described above.
  • MME 180 may be able to indicate to node 104 that the LI disturbing operations are to be selectively disabled one a per-UE basis, e.g., by disabling the LI disturbing operations with respect to one or more UEs, while enabling the LI disturbing operations with respect to one or more other UEs.
  • MME 180 may send to node 104 a message including the LI IE with an identifier of a UE, e.g., an identifier of UE 102.
  • controller 144 may disable the LI disturbing operations with respect to content to be communicated with UE 102.
  • MME 180 may send the LI IE to node 104 as part of a UE Context Modification Request message.
  • the UE Context Modification Request message may be sent by MME 180 to provide to a node, e.g., node 104, UE context information changes with respect to a particular UE, e.g., UE 102.
  • the UE Context Modification Request message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether the particular UE is subject to LI, e.g., as follows: Table 1 IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.1.1 YES reject MME UE S1APID M 9.2.3.3 YES reject eNB UE S1APID M 9.2.3.4 YES reject Security Key O 9.2.1.41 A fresh KeNB is provided after performing a key-change on the fly procedure in the MME, see TS 33.401 [15] YES reject Subscriber Profile ID for RAT/Frequency priority O 9.2.1.39 YES ignore UE Aggregate Maximum Bit Rate O 9.2.1.20 YES ignore CS Fallback Indicator O 9.2.3.21 YES reject UE Security Capabilities O 9.2.1.40 YES reject CSG Membership Status O 9.2.1.73 YES ignore Registered LAI
  • the UE Context Modification Request message may include any other indication that the particular UE is to be subject to LI.
  • MME 180 may send the LI IE to node 104 as part of an Initial Context Setup Request Message.
  • the Initial Context Setup Request Message may be sent by MME 180 to request a node, e.g., node 104, to setup UE context with respect to a particular UE, e.g., UE 102.
  • the Initial Context Setup Request Message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether the particular UE is subject to LI, e.g., as follows: Table 2 IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3 YES reject eNB UE S1AP ID M 9.2.3.4 YES reject UE Aggregate Maximum Bit Rate M 9.2.1.20 YES reject E-RAB to Be Setup List 1 YES reject >E-RAB to Be Setup Item IEs 1 to ⁇ maxn oofE-RABs> EACH reject >>E-RAB ID M 9.2.1.2 - >>E-RAB Level QoS Parameters M 9.2.1.15 Includes necessary QoS parameters - >>Transport Layer Address M 9.2.2.1 - >>GTP-TEID M 9.2.2.2 - >>NAS-PDU
  • the Initial Context Setup Request Message may include any other indication that the particular UE is to be subject to LI.
  • the indication that the particular UE is to be subject to LI may be included as part of any other message or any other Information Element (IE).
  • IE Information Element
  • MME 180 may be able to indicate to node 104 that the LI disturbing operations are to be globally disabled one a per-node basis, e.g., by disabling the LI disturbing operations with respect all UEs connected to node 104.
  • MME 180 may send to node 104 a message including the LI IE including an indication that the LI disturbing operations are to be disabled with respect to content to be communicated with all UEs connected to node 104.
  • controller 144 may disable the LI disturbing operations with respect to content to be communicated with all UEs connected to node 104.
  • MME 180 may send the LI IE to node 104 as part of a MME Configuration Transfer Message.
  • the MME Configuration Transfer Message may be sent by MME 180 to transfer Radio Access Network (RAN) configuration information to node 104.
  • RAN Radio Access Network
  • the MME Configuration Transfer Message may include an IE, denoted "Lawful Interception", having a value set to indicate whether LI is to be enabled with respect to all UEs connected to the node addressed by the MME Configuration Transfer Message, e.g., as follows: Table 3 IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.1.1 YES ignore SON Configurati on Transfer O 9.2.3.26 YES ignore Lawful Interception O YES ignore
  • the MME Configuration Transfer Message may include any other indication that the UEs connected to the node are to be subject to LI.
  • the indication that the UEs connected to the node are subject to LI may be included as part of any other message or any other Information Element (IE).
  • IE Information Element
  • MME 180 may be able to indicate to node 104 that the LI disturbing operations are to be disabled for a particular UE upon handover of the particular UE to node 104.
  • UE 102 may be handed over to node 104, e.g., from node 106.
  • MME 180 may send to node 104 a message including the LI IE including an indication that the LI disturbing operations are to be disabled with respect to content to be communicated with UE 102, e.g., upon handover of UE 102 to node 104.
  • MME 180 may send the LI IE to node 104 as part of a Handover Request Message.
  • the Handover Request Message may be sent by MME 180 to node 104, e.g., to request the preparation of resources for handover of UE 102.
  • the Handover Request Message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether LI is to be enabled with respect to the particular UEs being handed over, e.g., as follows: Table 4 IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.1.1 YES reject MME UE S1AP ID M 9.2.3.3 YES reject Handover Type M 9.2.1.13 YES reject Cause M 9.2.1.3 YES ignore UE Aggregate Maximum Bit Rate M 9.2.1.20 YES reject E-RABs To Be Setup List 1 YES reject >E-RABs To Be Setup Item IEs 1 to ⁇ max noof E-RABs > EACH reject >>E-RAB ID M 9.2.1.2 - >>Transpo rt Layer Address M 9.2.2.1 - >>GTP-TEID M 9.2.2.2 To deliver UL PDUs - >>E-RAB Level QoS Para
  • the Handover Request Message may include any other indication that the UE being handed over is to be subject to LI.
  • the indication that the UE being handed over is subject to LI may be included as part of any other message or any other Information Element (IE).
  • IE Information Element
  • nodes 104 and 106 may communicate a message including the LI IE indicating node 104 is to enable LI of content corresponding to one or more UEs connected to node 104, e.g., as described below.
  • node 106 may transmit the LI IE as part of a handover of a UE from node 106 to node 104, e.g., to indicate the UE is to be subject to LI.
  • message sender 196 may send over X2 link 105 an X2AP message including an indication of a UE, e.g., UE 102, to be handed over from node 106 to node 104.
  • the X2AP message may include the LI IE to indicate that the UE is to be subject to LI.
  • receiver 194 may receive the X2AP message, and controller 144 may disable, based on the LI IE, one or more operations, e.g., edge caching and/or offloading, with respect to content to be communicated with the UE being handed over, e.g., UE 102.
  • one or more operations e.g., edge caching and/or offloading
  • node 106 may transmit the LI IE to node 104 as part of a Handover Request Message.
  • the Handover Request Message may be sent by node 106 to node 104, e.g., to request the preparation of resources for handover of UE 102.
  • the Handover Request Message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether LI is to be enabled with respect to the particular UEs being handed over, e.g., as follows: Table 5 IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality Message Type M 9.2.13 YES reject Old eNB UE X2AP ID M eNB UE X2AP ID 9.2.24 Allocated at the source eNB YES reject Cause M 9.2.6 YES ignore Target Cell ID M ECGI 9.2.14 YES reject GUMMEI M 9.2.16 YES reject UE Context Information 1 YES reject >MME UE S1AP ID M INTEGE R (0..2 32 -1) MME UE S1AP ID allocated at the MME - - >UE Security Capabilities M 9.2.29 - - >AS Security Information M 9.2.30 - - >UE Aggregate Maximum Bit Rate M
  • OCTET STRING Includes the RRC Handover Preparation Information message as defined in subclause 10.2.2 of TS 36.331 [9] - - >Handover Restriction List O 9.2.3 - - >Location Reporting Information O 9.2.21 Includes the necessary parameters for location reporting - - >Management Based MDT Allowed O 9.2.59 YES ignore >Management Based MDT PLMN List O MDT PLMN List 9.2.64 YES ignore UE History Information M 9.2.38 Same definition as in TS 36.413 [4] YES ignore Trace Activation O 9.2.2 YES ignore SRVCC Operation Possible O 9.2.33 YES ignore CSG Membership Status O 9.2.52 YES reject Mobility Information O BIT STRING (SIZE (32)) Information related to the handover; the source eNB provides it in order to enable later analysis of the conditions that led to a wrong HO. YES ignore Lawful Interception Enabled O YES ignore
  • the Handover Request Message may include any other indication that the UE being handed over is to be subject to LI.
  • the indication that the UE being handed over is subject to LI may be included as part of any other message or any other Information Element (IE).
  • IE Information Element
  • Fig. 2 schematically illustrates a method of lawful interception, in accordance with some demonstrative embodiments.
  • a wireless communication system e.g., system 100 ( Fig. 1 ); a node, e.g., node 104 ( Fig. 1 ) and/or node 106 ( Fig. 1 ); and MME, e.g., MME 180 ( Fig. 1 ); a communication unit, e.g., communication units 182, 190 and/or 1195 ( Fig. 1 ); and/or a controller, e.g., controller 144 ( Fig. 1 ).
  • a wireless communication system e.g., system 100 ( Fig. 1 ); a node, e.g., node 104 ( Fig. 1 ) and/or node 106 ( Fig. 1 ); and MME, e.g., MME 180 ( Fig. 1 ); a communication unit, e.g., communication units 182, 190 and/
  • the method may include communicating a message addressed to a cellular node, e.g., an eNB, over a cellular communication network, the message including a LI IE indicating that content corresponding to one or more UEs connected to the cellular node is to be subject to LI.
  • a cellular node e.g., an eNB
  • the method may include sending the message to the cellular node.
  • the method may include sending the message from an MME to the cellular node.
  • MME 180 ( Fig. 1 ) may send the message including the LI IE to node 104 ( Fig. 1 ), e.g., as described above.
  • the method may include transmitting the message from another cellular node to the cellular node.
  • node 106 may transmit the message including the LI IE to node 104 ( Fig. 1 ), e.g., as described above.
  • the message may include a handover request message including an indication of a UE to be handed over to the cellular node.
  • the method may include receiving the message by the cellular node.
  • node 104 ( Fig. 1 ) may receive the message including the LI IE, e.g., as described above.
  • the method may include disabling for the one or more UEs one or more operations, e.g., edge caching and/or traffic offloading, based on the LI IE.
  • controller 144 Fig. 1
  • the method may include selectively disabling one or more operations with respect to content corresponding to one or more UEs connected to the cellular node.
  • controller 145 may selectively disable, e.g., based on the LI IE, one or more LU disturbing operations, e.g., edge caching and/or offloading, with respect to content to be communicated with one or more particular UEs connected to node 104 ( Fig. 1 ), e.g., as described above.
  • the method may include disabling one or more operations with respect to content corresponding to all UEs connected to the cellular node.
  • controller 145 may disable, e.g., based on the LI IE, one or more LU disturbing operations, e.g., edge caching and/or offloading, with respect to content to be communicated with all UEs connected to node 104 ( Fig. 1 ), e.g., as described above.
  • Fig. 3 schematically illustrates a product of manufacture 300, in accordance with some demonstrative embodiments.
  • Product 300 may include a non-transitory machine-readable storage medium 302 to store logic 304, which may be used, for example, to perform at least part of the functionality of MME 180 ( Fig. 1 ), node 104 ( Fig. 1 ), node 106 ( Fig. 1 ), communication unit 182 ( Fig. 1 ), communication unit 190 ( Fig. 1 ), communication unit 195 ( Fig. 1 ), and/or controller 144 ( Fig. 1 ) and/or to perform one or more operations of the method of Fig 2 .
  • the phrase "non-transitory machine-readable medium” is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.
  • product 300 and/or machine-readable storage medium 302 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like.
  • machine-readable storage medium 302 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like.
  • RAM random access memory
  • DDR-DRAM Double-Data-Rate DRAM
  • SDRAM static RAM
  • ROM read-only memory
  • the computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.
  • a communication link e.g., a modem, radio or network connection.
  • logic 304 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein.
  • the machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.
  • logic 304 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like.
  • the instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • the instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function.
  • the instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

    TECHNICAL FIELD
  • Some embodiments described herein generally relate to apparatus, system and method of Lawful Interception (LI) in a cellular network.
    • BACKGROUND
  • Some communication networks may enable Lawful interception (LI), for example, for obtaining data, for example, communication network data, pursuant to lawful authority, e.g., for the purpose of analysis and/or evidence. The obtained data may include, for example, signaling, network management information, and/or content of communications.
  • In cellular networks, LI may be performed by an element of a core network, for example, a Gateway (GW), e.g., a Serving Gateway (S-GW) or a Packet-Data-Network (PDN) Gateway (P-GW).
  • In these cellular networks, the GW may be able to apply the LI to communications, which are processed and/or transferred by the GW. However, the GW may not be able to apply the LI to any other communications of the cellular network, which are not handled by the GW.
  • US 2011/0075557 A1 relates to a system and method for offloading selected data to an alternate communication network. The offloading provides another route for selected packet traffic that can relieve the burden on a mobile operator's network, such as the backhaul and core networks. As the proliferation of data rich content and increasingly more capable mobile devices has continued, the amount of data communicated over mobile operator's networks has exponentially increased. Upgrading the existing network that was designed for voice calls is not desirable or practical for many mobile operators. A offload gateway is provided that inspects packets and determines those packets to offload to an alternate network as well as providing mobility management to allow for seamless handoffs and gateway relocations.
  • US 20110096669 A1 relates to a method to enhance resolution of location information of a mobile user in an Evolved Packet communication System. The system comprises a Mobility Management Entity that provides the user with at least one tracking area in which the user is able to move without location information being reported, The method comprises the following steps: receiving to the Mobility Management Entity, a location activation message valid for the user; receiving to the Mobility Management Entity, a service request related to the user; detecting in the Mobility Management Entity, user location information with higher resolution than the at least one tracking area level resolution; and sending from the Mobility Management Entity, a monitoring message comprising high resolution information of the user's location within the at least one tracking area.
    • SUMMARY
  • The invention is defined by the subject matter of the independent claims. Advantageous embodiments of the invention are subject to the dependent claims.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • For simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity of presentation. Furthermore, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.
    • Fig. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative embodiments.
    • Fig. 2 is a schematic flow-chart illustration of a method of Lawful Interception (LI), in accordance with some demonstrative embodiments.
    • Fig. 3 is a schematic illustration of a product, in accordance with some demonstrative embodiments.
    DETAILED DESCRIPTION
  • In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by persons of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and/or circuits have not been described in detail so as not to obscure the discussion.
  • Discussions herein utilizing terms such as, for example, "processing", "computing", "calculating", "determining", "establishing", "analyzing", "checking", or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.
  • The terms "plurality" and "a plurality", as used herein, include, for example, "multiple" or "two or more". For example, "a plurality of items" includes two or more items.
  • References to "one embodiment," "an embodiment," "demonstrative embodiment," "various embodiments," etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase "in one embodiment" does not necessarily refer to the same embodiment, although it may.
  • As used herein, unless otherwise specified the use of the ordinal adjectives "first," "second," "third," etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a Smartphone device, a server computer, a handheld computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a cellular network, a cellular node, a Wireless Local Area Network (WLAN), a Multiple Input Multiple Output (MIMO) transceiver or device, a Single Input Multiple Output (SIMO) transceiver or device, a Multiple Input Single Output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, Digital Video Broadcast (DVB) devices or systems, multi-standard radio devices or systems, a wired or wireless handheld device, e.g., a Smartphone, a Wireless Application Protocol (WAP) device, vending machines, sell terminals, and the like.
  • Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing Long Term Evolution (LTE) specifications (including "TS 33.106 - 3G security; Lawful interception requirements"; "TS 33.107 - 3G security; Lawful interception architecture and functions"; "TS 23.401 - General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"; "TS 36.413 - Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)"; "TS 36.423 - Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP); and "36.300 - Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2")) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless-Gigabit-Alliance (WGA) specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHY Specification Version 1.1, April 2011, Final specification) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.11 standards (IEEE 802.11-2012, IEEE Standard for Information technology--Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, March 29, 2012), and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.16 standards (IEEE-Std 802.16, 2009 Edition, Air Interface for Fixed Broadband Wireless Access Systems; IEEE-Std 802.16e, 2005 Edition, Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands; amendment to IEEE Std 802.16-2009, developed by Task Group m) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing WirelessHD™ specifications and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.
  • Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBee™, Ultra-Wideband (UWB), Global System for Mobile communication (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE) cellular system, LTE advance cellular system, High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High-Speed Packet Access (HSPA), HSPA+, Single Carrier Radio Transmission Technology (1XRTT), Evolution-Data Optimized (EV-DO), Enhanced Data rates for GSM Evolution (EDGE), and the like. Other embodiments may be used in various other devices, systems and/or networks.
  • The term "wireless device", as used herein, includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative embodiments, a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer. In some demonstrative embodiments, the term "wireless device" may optionally include a wireless service.
  • The term "communicating" as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
  • Some demonstrative embodiments are described herein with respect to a LTE cellular system. However, other embodiments may be implemented in any other suitable cellular network, e.g., a 3G cellular network, a 4G cellular network, a 5G cellular network, a WiMax cellular network, and the like.
  • The term "antenna", as used herein, may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements. The antenna may include, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like.
  • The term "cell", as used herein, may include a combination of network resources, for example, downlink and optionally uplink resources. The resources may be controlled and/or allocated, for example, by a cellular node (also referred to as a "base station"), or the like. The linking between a carrier frequency of the downlink resources and a carrier frequency of the uplink resources may be indicated in system information transmitted on the downlink resources.
  • Reference is now made to Fig. 1, which schematically illustrates a block diagram of a system 100, in accordance with some demonstrative embodiments.
  • As shown in Fig. 1, in some demonstrative embodiments, system 100 may include one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums 108. Wireless mediums 108 may include, for example, a radio channel, a cellular channel, an RF channel, a WLAN channel, a Wireless Fidelity (WiFi) channel, an IR channel, and the like. One or more elements of system 100 may optionally be capable of communicating over any suitable wired communication links.
  • In some demonstrative embodiments, system 100 may include one or more cellular networks, e.g., including one or more cells controlled by one or more nodes, e.g., a node 104 and/or a node 106.
  • In some demonstrative embodiments, nodes 104 and/or 106 may include an Evolved Node B (eNB). For example, nodes 104 and/or 106 may be configured to perform radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UEs and eNB radios, e.g., Dynamic allocation of resources to UEs in both uplink and downlink, header compression, link encryption of user data streams, packet routing of user data towards a destination, e.g., another eNB or an Evolved Packet Core (EPC), scheduling and/or transmitting paging messages, e.g., incoming calls and/or connection requests, broadcast information coordination, measurement reporting, and/or any other operations.
  • In other embodiments, nodes 104 and/or 106 may include any other functionality and/or may perform the functionality of any other cellular node, e.g., a Node B (NB) or any other node or device.
  • In some demonstrative embodiments, node 104 may communicate with a User Equipment (UE) 102 via a cellular link. UE 102 may include, for example, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a mobile internet device, a handheld computer, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a "Carry Small Live Large" (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an "Origami" device or computing device, a video device, an audio device, an A/V device, a gaming device, a media player, a Smartphone, or the like.
  • In some demonstrative embodiments, UE 102, node 104 and/or node 106 may include one or more wireless communication units to perform wireless communication between UE 102, node 104, node 106 and/or with one or more other wireless communication devices. For example, UE 102 may include a wireless communication unit 110 and/or nodes 104 and/or 106 may include a wireless communication unit 130.
  • In some demonstrative embodiments, wireless communication units 110 and 130 may include, or may be associated with, one or more antennas. In one example, wireless communication unit 110 may be associated with at least two antennas, e.g., antennas 112 and 114; and/or wireless communication unit 130 may be associated with at least two antennas, e.g., antennas 132 and 134. In other embodiments, wireless communication units 110 and/or 130 may be associated with any other number of antennas.
  • In some demonstrative embodiments, antennas 112, 114, 132 and/or 134 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas 112, 114,132 and/or 134 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. For example, antennas 112, 114, 132 and/or 134 may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like.
  • In some embodiments, antennas 112, 114, 132 and/or 134 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 112, 114, 132 and/or 134 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
  • In some demonstrative embodiments, wireless communication unit 130 may include one or more radios 142, and/or wireless communication unit 110 may include one or more radios 143. For example, radios 142 and/or 143 may include one or more wireless transmitters, receivers and/or transceivers able to send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data.
  • In some demonstrative embodiments, radios 143 and/or 142 may include at least a cellular transceiver to communicate between US 102 and nodes 104 and/or 106 over a cellular link.
  • In some demonstrative embodiments, radios 142 and/or 143 may include a multiple input multiple output (MIMO) transmitters receivers system (not shown), which may be capable of performing antenna beamforming methods, if desired.
  • In some demonstrative embodiments, radios 142 and/or 143 may include a turbo decoder and/or a turbo encoder (not shown) for encoding and/or decoding data bits into data symbols, if desired.
  • In some demonstrative embodiments, radios 142 and/or 143 may include OFDM and/or SC-FDMA modulators and/or demodulators (not shown) configured to communicate OFDM signals over downlink channels, e.g., between node 104 and UE 102, and SC-FDMA signals over uplink channels, e.g., between UE 102 and nodes 104 and/or 106.
  • In some demonstrative embodiments, system 100 may include one or more elements of a cellular network. For example, system 100 may also include a Mobility Management Entity (MME) 180.
  • In some demonstrative embodiments, MME 180 may be configured to perform network access control, for example, facilitating access of UE 102 to the cellular network. Additionally or alternatively, MME 180 may be configured to perform Mobility Management. Additionally or alternatively, MME 180 may be configured to perform tracking area management, e.g., by allocating and reallocating a tracking area identity list to a UE, e.g., UE 102. MME 180 may perform any other additional/and/or alternative functionality.
  • In some demonstrative embodiments, MME 180, node 104 and/or node 106 may include one or more communication units to perform communication between MME 180, node 104, node 106 and/or with one or more other cellular network devices, e.g., one or more Core Network (CN) devices. For example, MME 180 102 may include a communication unit 182, node 104 may include a communication unit 190 and/or node 106 may include a communication unit 195.
  • In some demonstrative embodiments, wireless communication unit 130 and communication unit 190 may be implemented as separate elements of node 106. In other embodiments, one or more elements of wireless communication unit 130 may perform one or more functionalities of communication unit 190; and/or one or more elements of communication unit 190 may perform one or more functionalities of communication unit 130.
  • In some demonstrative embodiments, communication unit 182 may include one or more message senders (also referred to as "transmitters" (Tx)) 184 and/or one or more messages receivers ("receivers" (Rx)) 186; communication unit 190 may include one or more transmitters (Tx) 192 and/or one or more receivers (Rx) 194; and/or communication unit 195 may include one or more transmitters (Tx) 196 and/or one or more receivers (Rx) 197.
  • In some demonstrative embodiments, MME 180 may communicate with nodes 104 and/or 106 via one or more interface links, for example, S1 Application Protocol (S1AP or S1) links, e.g., SI-MME links 181. For example, messages senders 184, 192 and/or 196 may include S1AP message senders configured to send messages over the S1AP links; and/or receivers 186, 194 and/or 197 may include S1AP receivers configured to receive messages over the S1AP links.
  • In some demonstrative embodiments, nodes 104 and 106 may communicate via one or more interface links, for example, X2 Application protocol (X2 or X2AP) links 105. For example, message senders 184, 192 and/or 196 may include X2AP message senders configured to send messages over X2 links 105; and/or receivers 186, 194 and/or 197 may include X2AP receivers configured to receive messages over X2 links 105.
  • In some demonstrative embodiments, UE 102, node 104, node 106 and/or MME 180 may also include, for example, one or more of a processor 124, an input unit 116, an output unit 118, a memory unit 120, and a storage unit 122. UE 102, node 104, node 106 and/or MME 180 may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of one or more of UE 102, node 104, node 106 and/or MME 180 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of one or more of UE 102, node 104, node 106 and/or MME 180 may be distributed among multiple or separate devices.
  • Processor 124 includes, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller. Processor 124 executes instructions, for example, of an Operating System (OS) of UE 102, node 104, node 106 and/or MME 180 and/or of one or more suitable applications.
  • Input unit 116 includes, for example, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device. Output unit 118 includes, for example, a monitor, a screen, a touch-screen, a flat panel display, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices.
  • Memory unit 120 includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Storage unit 122 includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. Memory unit 120 and/or storage unit 122, for example, may store data processed by UE 102, node 104, node 106 and/or MME 180.
  • In some demonstrative embodiments, MME 180 may be configured to manage Lawful Interception (LI) within system 100. For example, MME 180 may receive LI configuration information to configure the LI, e.g., in accordance with LI requirements of a Law Enforcement Monitoring Facility (LEMF) 161. In one example, MME 180 may receive the LI configuration information from LEMF 161 via an Administration Function (ADMF) interface and/or any other interface.
  • In some demonstrative embodiments, the LI may be applied with respect to content communicated with UE 102, e.g., as described below.
  • In some demonstrative embodiments, one or more elements ("LI handling elements") of system 100 may be configured to perform LI with respect to content processed by, transferred through and/or handled by the LI handling elements, e.g., as described below.
  • In some demonstrative embodiments, the LI handling elements may include at least one Core Network (CN) entity of the cellular network, which may be configured to perform LI with respect to content handled by, processed by and/or transferred by the CN entity.
  • In some demonstrative embodiments, the CN entity may include a GW 167. The GW 167 may interface, for example, between nodes 104 and/or 106 and one or more application servers 169, which may exchange content with UE 102, e.g., via nodes 104 and/or 106. For example, GW 167 may include a Serving Gateway (S-GW), a Packet-Data-Network (PDN) Gateway (P-GW), or any other GW.
  • In some demonstrative embodiments, performing LI at GW 167 may not be enough to assure LI is performed with respect to all content communicated with UE 102, for example, if some of the content which is communicated with UE 102 is not handled by, processed by and/or transferred by GW 167, e.g., as described below.
  • In some demonstrative embodiments, a node, e.g., node 104 and/or 106, my be configured to enable performing LI for one or more UEs, e.g., UE 102, connected to the node, as described below.
  • In some demonstrative embodiments, node 104 may be configured to receive an indication ("LI indication") that UE 102 is to be subject to LI and/or that node 104 is to enable LI for UE 102.
  • In some demonstrative embodiments, node 104 may receive the LI indication from a network entity, e.g., MME 180, for example, via an S1 link 181, e.g., as described below.
  • In some demonstrative embodiments, node 104 may receive the LI indication from another node, e.g., node 106, for example, via X2 link 105, e.g., as described below.
  • In some demonstrative embodiments, node 104 may include a controller 144 configured to disable one or more operations with respect to content to be communicated with UE 102, for example, based on the Li indication, e.g., as described below.
  • In some demonstrative embodiments,, the one or more operations may include operations ("LI disturbing operations"), which may affect and/or disturb an ability to apply LI to the content communicated with UE 102, e.g., as described below.
  • In some demonstrative embodiments, disabling the one or more LI disturbing operations with respect to the content to be communicated with UE 102 may enable performing LI with respect to the content, e.g., as described below.
  • In one example, disabling the one or more LI disturbing operations with respect to the content to be communicated with UE 102 may enable ensuring that content which has not been subject to LI is not to be communicated with UE 102, e.g., as described below.
  • In another example, disabling the one or more LI disturbing operations with respect to the content to be communicated with UE 102 may enable informing a LI entity, e.g., LEMF 161 regarding content which communicated with UE 102, e.g., as described below.
  • In some demonstrative embodiments, node 104 may disable the one or more LI disturbing operations with respect to content communicated between node 104 and UE 102. The content may include, for example, content, which has not been communicated via a CN entity and/or is not subject to LI by the CN entity, for example, a LI handling element, e.g., GW 167. According to this example, node 104 disables the one or more operations with respect to content communicated between node 104 and UE 102, and which has not be subject to LI by GW 167.
  • In some demonstrative embodiments, node 104 may be configured to perform edge caching, e.g., as described below.
  • In some demonstrative embodiments, node 104 may include at least one cache 145 to internally store content communicated with one or more UEs, for example, UE 102, e.g., content requested by UE 102 and/or content received from UE 102.
  • In some demonstrative embodiments, node 104 may retrieve the content from cache 145, for example, instead of retrieving the content from the CN, e.g., via GW 167. In one example, node 104 may communicate the content retrieved from cache 145 to UE 102 and/or to one or more other UEs, e.g., upon receiving a request for content, which is stored in cache 145. In another example, node 104 may utilize any other caching mechanism and/or algorithms, for example, proactive caching, to manage internal caching of content in cache 145.
  • In some demonstrative embodiments, the content retrieved from internal cache 145 of node 104 may not be subject to LI by the CN entity performing the LI, e.g., GW 167.
  • In some demonstrative embodiments, controller 144 may be configured to disable edge caching of content to be communicated with UE 102, for example, based on the LI indication, e.g., as described below.
  • In some demonstrative embodiments, node 104 may be configured to perform traffic offloading, for example, by communicating content via one or more routes, which do not involve the CN entity performing the LI, e.g., GW 167.
  • For example, node 104 may be configured to communicate with a network, e.g., the Internet, directly or via any other route not involving the CN entity performing the LI. According to this example, node 104 may be able to communicate content between the Internet and UE 102, e.g., without the content being subject to LI by GW 167.
  • In one example, node 104 may be configured to perform the offloading according to a Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN) mechanism, or any other offloading mechanism.
  • In some demonstrative embodiments, controller 144 may be configured to disable traffic offloading, e.g., SIPTO@LN or any other traffic offloading, of content to be communicated with UE 102, for example, based on the LI indication, e.g., as described below.
  • In some demonstrative embodiments, one or more elements of system 100 may be configured to enable notifying a node, e.g., node 104, that at least one UE connected to the node, e.g., UE 102, is subject to LI.
  • In some demonstrative embodiments, receiver 194 may be configured to receive a message including a LI Information Element (IE) indicating node 104 is to enable LI for one or more UEs connected to node 104, e.g., as described below.
  • In some demonstrative embodiments, the LI IE may be sent by MME 180, e.g., by message sender 184, for example, via S1AP signaling, e.g., over S1 link 181.
  • In some demonstrative embodiments, the LI IE may be sent by node, e.g., by message sender 196, for example, via X2AP signaling, e.g., over X2 link 105.
  • In some demonstrative embodiments, controller 144 may be configured to take actions to make the content accessed by the UEs, which are subject to LI, available for LI.
  • In some demonstrative embodiments, the LI notification to node 104 may relate to one or more particular UEs, for example, to indicate that the one or more particular UEs are to be subject to LI, e.g., while one or more other UEs may not be subject to LI. In one example, the LI IE may indicate that UE 102 is to be subject to LI, e.g., while one or more other UEs are not to be subject to LI.
  • In some demonstrative embodiments, controller 144 may disable, e.g., based on the LI IE, one or more operations with respect to content to be communicated with the one or more UEs, which are subject to LI.
  • In some demonstrative embodiments, the LI notification to node 104 may globally relate to all UEs connected to node 104, for example, to indicate all UEs connected to node 104 are to be subject to LI.
  • In some demonstrative embodiments, controller 144 may disable, e.g., based on the LI IE, one or more operations with respect to content to be communicated with all UEs connected to node 104.
  • In some demonstrative embodiments, the actions taken by controller 144 with respect to the UEs, which are indicated to be subject top LI, may include, for example, disabling caching and/or offloading.
  • For example, controller 144 may control node 104 to disable caching and/or offloading with respect to content to be communicated with UE 102, e.g., if the LI indication indicated that UE 102 is to be subject to LI. According to this example, controller 144 may, for example, control node 104 to communicate the content for UE 102 via GW 167, e.g., instead of retrieving the content from cache 145 and/or via the SIPTO@LN mechanism.
  • In some demonstrative embodiments, the actions taken by controller 144 with respect to the UEs, which are indicated to be subject to LI, may include, for example, notifying one or more CN entities, e.g., GW 167, MME 180, the ADMF and/or any other network entity, about content accessed by the UE, which is indicated to be subject to LI.
  • In some demonstrative embodiments, the actions taken by controller 144 with respect to the UEs, which are indicated to be subject top LI, may include any other additional or alternative action.
  • In some demonstrative embodiments, controller 144 may be configured to ensure that the one or more UEs, which are subject to LI, may not be able to detect the LI.
  • In some demonstrative embodiments, controller 144 may control node 104 to add a delay, e.g., when serving content from cache 145 to the UEs connected to node 104. For example, controller 144 may add the delay, for example, only when some of the UEs are subject to LI, e.g., while one or more other UEs are not subject to LI. According to this example, the LI may not affect normal operation of the node 104 in a manner apparent to UE 102.
  • In some demonstrative embodiments, MME 180 may receive LI configuration information defining one or more UEs, e.g., including UE 102, to be subject to LI. For example, MME 180 may receive the LI configuration information from LEMF 161, e.g., as described above.
  • In some demonstrative embodiments, MME 180 may be able to indicate to node 104 that LI is to be enabled with respect to the one or more UEs. For example, MME 180 may indicate to node 104 that node 104 is to disable one or more LI disturbing operations with respect to content to be communicated with the one or more UEs. In one example, MME 180 may indicate to node 104 that node 104 is to disable caching and/or offloading with respect to content to be communicated with the one or more UEs, e.g., as described above.
  • In one embodiment, MME 180 may be able to indicate to node 104 that the LI disturbing operations are to be selectively disabled one a per-UE basis, e.g., by disabling the LI disturbing operations with respect to one or more UEs, while enabling the LI disturbing operations with respect to one or more other UEs.
  • For example, MME 180 may send to node 104 a message including the LI IE with an identifier of a UE, e.g., an identifier of UE 102. According to this example, controller 144 may disable the LI disturbing operations with respect to content to be communicated with UE 102.
  • In one example, MME 180 may send the LI IE to node 104 as part of a UE Context Modification Request message.
  • For example, the UE Context Modification Request message may be sent by MME 180 to provide to a node, e.g., node 104, UE context information changes with respect to a particular UE, e.g., UE 102.
  • In one example, the UE Context Modification Request message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether the particular UE is subject to LI, e.g., as follows: Table 1
    IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality
    Message Type M 9.2.1.1 YES reject
    MME UE S1APID M 9.2.3.3 YES reject
    eNB UE S1APID M 9.2.3.4 YES reject
    Security Key O 9.2.1.41 A fresh KeNB is provided after performing a key-change on the fly procedure in the MME, see TS 33.401 [15] YES reject
    Subscriber Profile ID for RAT/Frequency priority O 9.2.1.39 YES ignore
    UE Aggregate Maximum Bit Rate O 9.2.1.20 YES ignore
    CS Fallback Indicator O 9.2.3.21 YES reject
    UE Security Capabilities O 9.2.1.40 YES reject
    CSG Membership Status O 9.2.1.73 YES ignore
    Registered LAI O 9.2.3.1 YES ignore
    Lawful Interception Enabled O YES ignore
  • In other embodiments, the UE Context Modification Request message may include any other indication that the particular UE is to be subject to LI.
  • In another example, MME 180 may send the LI IE to node 104 as part of an Initial Context Setup Request Message.
  • For example, the Initial Context Setup Request Message may be sent by MME 180 to request a node, e.g., node 104, to setup UE context with respect to a particular UE, e.g., UE 102.
  • In one example, the Initial Context Setup Request Message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether the particular UE is subject to LI, e.g., as follows: Table 2
    IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality
    Message Type M 9.2.1.1 YES reject
    MME UE S1AP ID M 9.2.3.3 YES reject
    eNB UE S1AP ID M 9.2.3.4 YES reject
    UE Aggregate Maximum Bit Rate M 9.2.1.20 YES reject
    E-RAB to Be Setup List 1 YES reject
     >E-RAB to Be Setup Item IEs 1 to <maxn oofE-RABs> EACH reject
      >>E-RAB ID M 9.2.1.2 -
      >>E-RAB Level QoS Parameters M 9.2.1.15 Includes necessary QoS parameters -
      >>Transport Layer Address M 9.2.2.1 -
      >>GTP-TEID M 9.2.2.2 -
      >>NAS-PDU O 9.2.3.5 -
      >>Correlation ID O 9.2.2.80 YES ignore
    Lawful Interception Enabled O YES ignore
  • In other embodiments, the Initial Context Setup Request Message may include any other indication that the particular UE is to be subject to LI.
  • In other embodiments, the indication that the particular UE is to be subject to LI may be included as part of any other message or any other Information Element (IE).
  • In another embodiment, MME 180 may be able to indicate to node 104 that the LI disturbing operations are to be globally disabled one a per-node basis, e.g., by disabling the LI disturbing operations with respect all UEs connected to node 104.
  • For example, MME 180 may send to node 104 a message including the LI IE including an indication that the LI disturbing operations are to be disabled with respect to content to be communicated with all UEs connected to node 104. According to this example, controller 144 may disable the LI disturbing operations with respect to content to be communicated with all UEs connected to node 104.
  • In one example, MME 180 may send the LI IE to node 104 as part of a MME Configuration Transfer Message.
  • For example, the MME Configuration Transfer Message may be sent by MME 180 to transfer Radio Access Network (RAN) configuration information to node 104.
  • In one example, the MME Configuration Transfer Message may include an IE, denoted "Lawful Interception", having a value set to indicate whether LI is to be enabled with respect to all UEs connected to the node addressed by the MME Configuration Transfer Message, e.g., as follows: Table 3
    IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality
    Message Type M 9.2.1.1 YES ignore
    SON Configurati on Transfer O 9.2.3.26 YES ignore
    Lawful Interception O YES ignore
  • In other embodiments, the MME Configuration Transfer Message may include any other indication that the UEs connected to the node are to be subject to LI.
  • In other embodiments, the indication that the UEs connected to the node are subject to LI may be included as part of any other message or any other Information Element (IE).
  • In another embodiment, MME 180 may be able to indicate to node 104 that the LI disturbing operations are to be disabled for a particular UE upon handover of the particular UE to node 104.
  • For example, UE 102 may be handed over to node 104, e.g., from node 106. According to this example, MME 180 may send to node 104 a message including the LI IE including an indication that the LI disturbing operations are to be disabled with respect to content to be communicated with UE 102, e.g., upon handover of UE 102 to node 104.
  • In one example, MME 180 may send the LI IE to node 104 as part of a Handover Request Message.
  • For example, the Handover Request Message may be sent by MME 180 to node 104, e.g., to request the preparation of resources for handover of UE 102.
  • In one example, the Handover Request Message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether LI is to be enabled with respect to the particular UEs being handed over, e.g., as follows: Table 4
    IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality
    Message Type M 9.2.1.1 YES reject
    MME UE S1AP ID M 9.2.3.3 YES reject
    Handover Type M 9.2.1.13 YES reject
    Cause M 9.2.1.3 YES ignore
    UE Aggregate Maximum Bit Rate M 9.2.1.20 YES reject
    E-RABs To Be Setup List 1 YES reject
     >E-RABs To Be Setup Item IEs 1 to <max noof E-RABs > EACH reject
      >>E-RAB ID M 9.2.1.2 -
      >>Transpo rt Layer Address M 9.2.2.1 -
      >>GTP-TEID M 9.2.2.2 To deliver UL PDUs -
      >>E-RAB Level QoS Parameter s M 9.2.1.15 Includes necessary QoS parameters -
      >>Data Forwardin g Not Possible O 9.2.1.76 YES ignore
    Source to Target Transparent Container M 9.2.1.56 YES reject
    UE Security Capabilities M 9.2.1.40 YES reject
    Handover Restriction List O 9.2.1.22 YES ignore
    Trace Activation O 9.2.1.4 YES ignore
    Request Type O 9.2.1.34 YES ignore
    SRVCC Operation Possible O 9.2.1.58 YES ignore
    Security Context M 9.2.1.26 YES reject
    NAS Security Parameters to E-UTRAN C-iffromU TRANG ERAN 9.2.3.31 The eNB shall use this IE as specified in TS 33.401 [15]. YES reject
    CSG Id O 9.2.1.62 YES reject
    CSG Membership Status O 9.2.1.73 YES ignore
    GUMMEI O 9.2.3.9 This IE indicates the MME serving the UE YES ignore
    MME UE S1AP ID 2 O 9.2.3.3 This IE indicates the MME UE S1AP ID assigned by the MME YES ignore
    Management Based MDT Allowed O 9.2.1.83 YES ignore
    Lawful Interception Enabled O YES ignore
  • In other embodiments, the Handover Request Message may include any other indication that the UE being handed over is to be subject to LI.
  • In other embodiments, the indication that the UE being handed over is subject to LI may be included as part of any other message or any other Information Element (IE).
  • In some demonstrative embodiments, nodes 104 and 106 may communicate a message including the LI IE indicating node 104 is to enable LI of content corresponding to one or more UEs connected to node 104, e.g., as described below.
  • In some demonstrative embodiments, node 106 may transmit the LI IE as part of a handover of a UE from node 106 to node 104, e.g., to indicate the UE is to be subject to LI. For example, message sender 196 may send over X2 link 105 an X2AP message including an indication of a UE, e.g., UE 102, to be handed over from node 106 to node 104. The X2AP message may include the LI IE to indicate that the UE is to be subject to LI. According to this example, receiver 194 may receive the X2AP message, and controller 144 may disable, based on the LI IE, one or more operations, e.g., edge caching and/or offloading, with respect to content to be communicated with the UE being handed over, e.g., UE 102.
  • In one example, node 106 may transmit the LI IE to node 104 as part of a Handover Request Message.
  • For example, the Handover Request Message may be sent by node 106 to node 104, e.g., to request the preparation of resources for handover of UE 102.
  • In one example, the Handover Request Message may include an IE, denoted "Lawful Interception Enabled", having a value set to indicate whether LI is to be enabled with respect to the particular UEs being handed over, e.g., as follows: Table 5
    IE/Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality
    Message Type M 9.2.13 YES reject
    Old eNB UE X2AP ID M eNB UE X2AP ID 9.2.24 Allocated at the source eNB YES reject
    Cause M 9.2.6 YES ignore
    Target Cell ID M ECGI 9.2.14 YES reject
    GUMMEI M 9.2.16 YES reject
    UE Context Information 1 YES reject
    >MME UE S1AP ID M INTEGE R (0..232 -1) MME UE S1AP ID allocated at the MME - -
    >UE Security Capabilities M 9.2.29 - -
    >AS Security Information M 9.2.30 - -
    >UE Aggregate Maximum Bit Rate M 9.2.12 - -
    >Subscriber Profile ID for RAT/Frequency priority O 9.2.25 - -
    >E-RABs To Be Setup List 1 - -
    >>E-RABs To Be Setup Item 1 .. <max noof Beare rs> EACH ignore
    >>>E-RAB ID M 9.2.23 - -
    >>>E-RAB Level QoS Parameters M 9.2.9 Includes necessary QoS parameters - -
    >>>DL Forwarding O 9.2.5 - -
    >>>UL GTP Tunnel Endpoint M GTP Tunnel Endpoint 9.2.1 SGW endpoint of the S1 transport bearer. For delivery of UL PDUs. - -
    >RRC Context M OCTET STRING Includes the RRC Handover Preparation Information message as defined in subclause 10.2.2 of TS 36.331 [9] - -
    >Handover Restriction List O 9.2.3 - -
    >Location Reporting Information O 9.2.21 Includes the necessary parameters for location reporting - -
    >Management Based MDT Allowed O 9.2.59 YES ignore
    >Management Based MDT PLMN List O MDT PLMN List 9.2.64 YES ignore
    UE History Information M 9.2.38 Same definition as in TS 36.413 [4] YES ignore
    Trace Activation O 9.2.2 YES ignore
    SRVCC Operation Possible O 9.2.33 YES ignore
    CSG Membership Status O 9.2.52 YES reject
    Mobility Information O BIT STRING (SIZE (32)) Information related to the handover; the source eNB provides it in order to enable later analysis of the conditions that led to a wrong HO. YES ignore
    Lawful Interception Enabled O YES ignore
  • In other embodiments, the Handover Request Message may include any other indication that the UE being handed over is to be subject to LI.
  • In other embodiments, the indication that the UE being handed over is subject to LI may be included as part of any other message or any other Information Element (IE).
  • Reference is made to Fig. 2, which schematically illustrates a method of lawful interception, in accordance with some demonstrative embodiments. In some embodiments, one or more of the operations of the method of Fig. 2 may be performed by a wireless communication system e.g., system 100 (Fig. 1); a node, e.g., node 104 (Fig. 1) and/or node 106 (Fig. 1); and MME, e.g., MME 180 (Fig. 1); a communication unit, e.g., communication units 182, 190 and/or 1195 (Fig. 1); and/or a controller, e.g., controller 144 (Fig. 1).
  • As indicated at block 202, the method may include communicating a message addressed to a cellular node, e.g., an eNB, over a cellular communication network, the message including a LI IE indicating that content corresponding to one or more UEs connected to the cellular node is to be subject to LI.
  • As indicated at block 204, the method may include sending the message to the cellular node.
  • As indicated at block 206, the method may include sending the message from an MME to the cellular node. For example, MME 180 (Fig. 1) may send the message including the LI IE to node 104 (Fig. 1), e.g., as described above.
  • As indicated at block 208, the method may include transmitting the message from another cellular node to the cellular node. For example, node 106 (Fig. 1) may transmit the message including the LI IE to node 104 (Fig. 1), e.g., as described above. For example, the message may include a handover request message including an indication of a UE to be handed over to the cellular node.
  • As indicated at block 210, the method may include receiving the message by the cellular node. For example, node 104 (Fig. 1) may receive the message including the LI IE, e.g., as described above.
  • As indicated at block 212, the method may include disabling for the one or more UEs one or more operations, e.g., edge caching and/or traffic offloading, based on the LI IE. For example, controller 144 (Fig. 1) may disable, e.g., based on the LI IE, one or more LU disturbing operations, e.g., edge caching and/or offloading, with respect to content to be communicated with one or more UEs connected to node 104 (Fig. 1), e.g., as described above.
  • As indicated at block 214, the method may include selectively disabling one or more operations with respect to content corresponding to one or more UEs connected to the cellular node. For example, controller 145 (Fig. 1) may selectively disable, e.g., based on the LI IE, one or more LU disturbing operations, e.g., edge caching and/or offloading, with respect to content to be communicated with one or more particular UEs connected to node 104 (Fig. 1), e.g., as described above.
  • As indicated at block 216, the method may include disabling one or more operations with respect to content corresponding to all UEs connected to the cellular node. For example, controller 145 (Fig. 1) may disable, e.g., based on the LI IE, one or more LU disturbing operations, e.g., edge caching and/or offloading, with respect to content to be communicated with all UEs connected to node 104 (Fig. 1), e.g., as described above.
  • Reference is made to Fig. 3, which schematically illustrates a product of manufacture 300, in accordance with some demonstrative embodiments. Product 300 may include a non-transitory machine-readable storage medium 302 to store logic 304, which may be used, for example, to perform at least part of the functionality of MME 180 (Fig. 1), node 104 (Fig. 1), node 106 (Fig. 1), communication unit 182 (Fig. 1), communication unit 190 (Fig. 1), communication unit 195 (Fig. 1), and/or controller 144 (Fig. 1) and/or to perform one or more operations of the method of Fig 2. The phrase "non-transitory machine-readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.
  • In some demonstrative embodiments, product 300 and/or machine-readable storage medium 302 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine-readable storage medium 302 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like. The computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.
  • In some demonstrative embodiments, logic 304 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.
  • In some demonstrative embodiments, logic 304 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.
    • EXAMPLES
  • The following examples pertain to further embodiments.
    • Example 1 includes an Evolved Node B (eNB) comprising two or more antennas; a receiver to receive a message including a Lawful Interception (LI) Information Element (IE) indicating the eNB is to enable LI for one or more User Equipment (UEs) connected to the eNB; and a controller to disable, based on the LI IE, one or more operations with respect to content to be communicated with the one or more UEs.
    • Example 2 includes the subject matter of Example 1 and optionally, wherein the one or more operations comprise at least one operation selected from the group consisting of edge caching and traffic offloading.
    • Example 3 includes the subject matter of Example 2 and optionally, wherein the traffic offloading comprises Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN).
    • Example 4 includes the subject matter of any one of Examples 1-3 and optionally, wherein the content comprises content, for which LI cannot be performed by a network entity of a Core Network (CN).
    • Example 5 includes the subject matter of Example 4 and optionally, wherein the network entity comprises a Serving Gateway (S-GW) or a Packet Data Network (PDN) Gateway (P-GW).
    • Example 6 includes the subject matter of any one of Examples 1-5 and optionally, wherein the receiver is to receive the message from a Mobility Management Entity (MME).
    • Example 7 includes the subject matter of Example 6 and optionally, wherein the message comprises an identifier of a UE, and wherein the controller is to disable the one or more operations with respect to content to be communicated with the UE.
    • Example 8 includes the subject matter of Example 7 and optionally, wherein the message includes a UE context modification request message or an initial context setup request message.
    • Example 9 includes the subject matter of Example 6 and optionally, wherein based on the message the eNB is to disable the one or more operations with respect to content to be communicated with all UEs connected to the eNB.
    • Example 10 includes the subject matter of Example 9 and optionally, wherein the message comprises a MME configuration transfer message.
    • Example 11 includes the subject matter of Example 6 and optionally, wherein the message comprises a handover request message including an indication of a UE to be handed over to the eNB.
    • Example 12 includes the subject matter of any one of Examples 1-5 and optionally, wherein the receiver is to receive the message from another eNB.
    • Example 13 includes the subject matter of Example 12 and optionally, wherein the message comprises a handover request message from the other eNB, the handover request message including an identifier of a UE to be handed over from the other eNB to the eNB and to be enabled for LI.
    • Example 14 includes a cellular communication system comprising a first Evolved Node B (eNB) to transmit to a second eNB a handover request message including an indication of a User Equipment (UE) to be handed over from the first eNB to the second eNB, the message including a Lawful Interception (LI) Information Element (IE) indicating the second eNB is to enable LI of content to be communicated with the UE.
    • Example 15 includes the subject matter of Example 14 and optionally, wherein the content comprises content, for which LI cannot be performed by a network entity of a Core Network (CN).
    • Example 16 includes the subject matter of Example 15 and optionally, wherein the network entity comprises a Serving Gateway (S-GW) or a Packet Data Network PDN) Gateway (P-GW).
    • Example 17 includes the subject matter of any one of Examples 14-16 and optionally, wherein the IE is to indicate to the second eNB to disable for the UE one or more operations selected from the group consisting of edge caching and traffic offloading.
    • Example 18 includes the subject matter of Example 17 and optionally, wherein the traffic offloading comprises Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN).
    • Example 19 includes the subject matter of any one of Examples 14-18 and optionally, wherein the handover request message comprises an X2 Application Protocol (X2AP) message.
    • Example 20 includes a Mobility Management Entity (MME) comprising a message sender to send to an Evolved Node B (eNB) a message including a Lawful Interception (LI) Information Element (IE) indicating the eNB is to enable LI with respect to one or more User Equipment (UEs) connected to the eNB.
    • Example 21 includes the subject matter of Example 20 and optionally, wherein the LI IE is to indicate the eNB is to disable for the one or more UEs one or more operations selected from the group consisting of edge caching and traffic offloading.
    • Example 22 includes the subject matter of Example 21 and optionally, wherein the traffic offloading comprises Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN).
    • Example 23 includes the subject matter of any one of Examples 20-22 and optionally, wherein the message comprises an identifier of a UE to be subject to LI.
    • Example 24 includes the subject matter of Example 23 and optionally, wherein the message includes a UE context modification request message or an initial context setup request message.
    • Example 25 includes the subject matter of any one of Examples 20-22 and optionally, wherein the LI IE is to indicate that all UEs connected to the eNB are to be subject to LI.
    • Example 26 includes the subject matter of Example 25 and optionally, wherein the message comprises a MME configuration transfer message.
    • Example 27 includes the subject matter of any one of Examples 20-22 and optionally, wherein the message comprises a handover request message including an indication of a UE to be handed over to the eNB.
    • Example 28 includes a method comprising communicating a message addressed to an Evolved Node B (eNB) over a cellular communication network, the message including a Lawful Interception (LI) Information Element (IE) indicating that content corresponding to one or more User Equipment (UEs) connected to the eNB is to be subject to LI.
    • Example 29 includes the subject matter of Example 28 and optionally, comprising receiving the message by the eNB.
    • Example 30 includes the subject matter of Example 28 or 29 and optionally, wherein the content comprises content, for which LI cannot be performed by a network entity of a Core Network (CN)
    • Example 31 includes the subject matter of Example 30 and optionally, wherein the network entity comprises a Serving Gateway (S-GW) or a Packet Data Network (PDN) Gateway (P-GW).
    • Example 32 includes the subject matter of any one of Examples 29-31 and optionally, comprising disabling for the one or more UEs one or more operations selected from the group consisting of edge caching and traffic offloading.
    • Example 33 includes the subject matter of Example 32 and optionally, wherein the traffic offloading comprises Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN).
    • Example 34 includes the subject matter of any one of Examples 29-33 and optionally, comprising receiving the message from a Mobility Management Entity (MME).
    • Example 35 includes the subject matter of Example 34 and optionally, comprising disabling one or more operations with respect to content corresponding to all UEs connected to the eNB.
    • Example 36 includes the subject matter of Example 35 and optionally, wherein the message comprises a MME configuration transfer message.
    • Example 37 includes the subject matter of Example 28 and optionally, comprising sending the message from a Mobility Management Entity (MME) to the eNB.
    • Example 38 includes the subject matter of Example 34 or 37 and optionally, wherein the message comprises an identifier of a UE to be enabled for LI.
    • Example 39 includes the subject matter of Example 38 and optionally, wherein the message includes a UE context modification request message or an initial context setup request message.
    • Example 40 includes the subject matter of Example 34 or 37 and optionally, wherein the message comprises a handover request message including an indication of a UE to be handed over to the eNB.
    • Example 41 includes the subject matter of any one of Examples 29-33 and optionally, comprising receiving the message from another eNB.
    • Example 42 includes the subject matter of Example 28 and optionally, comprising transmitting the message from another eNB to the eNB.
    • Example 43 includes the subject matter of Example 41 or 42 and optionally, wherein the message comprises a handover request message from the other eNB, the handover request message including an identifier of a UE to be handed over from the other eNB to the eNB.
    • Example 44 includes a product including a non-transitory storage medium having stored thereon instructions that, when executed by a machine, result in communicating a message addressed to an Evolved Node B (eNB) over a cellular communication network, the message including a Lawful Interception (LI) Information Element (IE) indicating content corresponding to one or more User Equipment (UEs) connected to the eNB is to be subject to LI.
    • Example 45 includes the subject matter of Example 44 and optionally, wherein the instructions result in receiving the message by the eNB.
    • Example 46 includes the subject matter of Example 44 or 45 and optionally, wherein the content comprises content, for which LI cannot be performed by a network entity of a Core Network (CN).
    • Example 47 includes the subject matter of Example 46 and optionally, wherein the network entity comprises a Serving Gateway (S-GW) or a Packet Data Network (PDN) Gateway (P-GW).
    • Example 48 includes the subject matter of any one of Examples 45-47 and optionally, wherein the instructions result in disabling for the one or more UEs one or more operations selected from the group consisting of edge caching and traffic offloading.
    • Example 49 includes the subject matter of Example 48 and optionally, wherein the traffic offloading comprises Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN).
    • Example 50 includes the subject matter of any one of Examples 45-49 and optionally, wherein the instructions result in receiving the message from a Mobility Management Entity (MME).
    • Example 51 includes the subject matter of Example 50 and optionally, wherein the instructions result in disabling one or more operations with respect to content corresponding to all UEs connected to the eNB.
    • Example 52 includes the subject matter of Example 51 and optionally, wherein the message comprises a MME configuration transfer message.
    • Example 53 includes the subject matter of Example 44 and optionally, wherein the instructions result in sending the message from a Mobility Management Entity (MME) to the eNB.
    • Example 54 includes the subject matter of Example 50 or 53 and optionally, wherein the message comprises an identifier of a UE to be enabled for LI.
    • Example 55 includes the subject matter of Example 54 and optionally, wherein the message includes a UE context modification request message or an initial context setup request message.
    • Example 56 includes the subject matter of Example 50 or 53 and optionally, wherein the message comprises a handover request message including an indication of a UE to be handed over to the eNB.
    • Example 57 includes the subject matter of any one of Examples 45-49 and optionally, wherein the instructions result in receiving the message from another eNB.
    • Example 58 includes the subject matter of Example 44 and optionally, wherein the instructions result in transmitting the message from another eNB to the eNB.
    • Example 59 includes the subject matter of Example 57 or 58 and optionally, wherein the message comprises a handover request message from the other eNB, the handover request message including an identifier of a UE to be handed over from the other eNB to the eNB.
    • Example 60 includes an apparatus comprising means for communicating a message addressed to an Evolved Node B (eNB) over a cellular communication network, the message including a Lawful Interception (LI) Information Element (IE) indicating content corresponding to one or more User Equipment (UEs) connected to the eNB is to be subject to LI.
    • Example 61 includes the subject matter of Example 60 and optionally, comprising means for receiving the message by the eNB.
    • Example 62 includes the subject matter of Example 60 or 61 and optionally, wherein the content comprises content, for which LI cannot be performed by a network entity of a Core Network (CN).
    • Example 63 includes the subject matter of Example 62 and optionally, wherein the network entity comprises a Serving Gateway (S-GW) or a Packet Data Network (PDN) Gateway (P-GW).
    • Example 64 includes the subject matter of any one of Examples 61-63 and optionally, comprising means for disabling for the one or more UEs one or more operations selected from the group consisting of edge caching and traffic offloading.
    • Example 65 includes the subject matter of Example 64 and optionally, wherein the traffic offloading comprises Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN).
    • Example 66 includes the subject matter of any one of Examples 61-65 and optionally, comprising means for receiving the message from a Mobility Management Entity (MME).
    • Example 67 includes the subject matter of Example 66 and optionally, comprising means for disabling one or more operations with respect to content corresponding to all UEs connected to the eNB.
    • Example 68 includes the subject matter of Example 67 and optionally, wherein the message comprises a MME configuration transfer message.
    • Example 69 includes the subject matter of Example 60 and optionally, comprising means for sending the message from a Mobility Management Entity (MME) to the eNB.
    • Example 70 includes the subject matter of Example 66 or 69 and optionally, wherein the message comprises an identifier of a UE to be enabled for LI.
    • Example 71 includes the subject matter of Example 70 and optionally, wherein the message includes a UE context modification request message or an initial context setup request message.
    • Example 72 includes the subject matter of Example 66 or 69 and optionally, wherein the message comprises a handover request message including an indication of a UE to be handed over to the eNB.
    • Example 73 includes the subject matter of any one of Examples 61-65 and optionally, comprising means for receiving the message from another eNB.
    • Example 74 includes the subject matter of Example 60 and optionally, comprising means for transmitting the message from another eNB to the eNB.
    • Example 75 includes the subject matter of Example 73 or 74 and optionally, wherein the message comprises a handover request message from the other eNB, the handover request message including an identifier of a UE to be handed over from the other eNB to the eNB.
    • Example 76 includes a cellular node comprising one or more antennas; a receiver to receive a message including a Lawful Interception (LI) Information Element (IE) indicating the cellular node is to enable LI for one or more User Equipment (UEs) connected to the cellular node; and a controller to disable, based on the LI IE, one or more operations with respect to content to be communicated with the one or more UEs.
    • Example 77 includes the subject matter of Example 76 and optionally, wherein the one or more operations comprise at least one operation selected from the group consisting of edge caching and traffic offloading.
    • Example 78 includes the subject matter of Example 77 and optionally, wherein the traffic offloading comprises Selected Internet-Protocol (IP) Traffic Offload (SIPTO) at Local Network (SIPTO@LN).
    • Example 79 includes the subject matter of any one of Examples 76-78 and optionally, wherein the content comprises content, for which LI cannot be performed by a network entity of a Core Network (CN).
    • Example 80 includes the subject matter of Example 80 and optionally, wherein the network entity comprises a Serving Gateway (S-GW) or a Packet Data Network (PDN) Gateway (P-GW).
    • Example 81 includes the subject matter of any one of Examples 76-80 and optionally, wherein the receiver is to receive the message from a Mobility Management Entity (MME).
    • Example 82 includes the subject matter of Example 81 and optionally, wherein the message comprises an identifier of a UE, and wherein the controller is to disable the one or more operations with respect to content to be communicated with the UE.
    • Example 83 includes the subject matter of Example 82 and optionally, wherein the message includes a UE context modification request message or an initial context setup request message.
    • Example 84 includes the subject matter of Example 81 and optionally, wherein based on the message the cellular node is to disable the one or more operations with respect to content to be communicated with all UEs connected to the cellular node.
    • Example 85 includes the subject matter of Example 84 and optionally, wherein the message comprises a MME configuration transfer message.
    • Example 86 includes the subject matter of Example 81 and optionally, wherein the message comprises a handover request message including an indication of a UE to be handed over to the cellular node.
    • Example 87 includes the subject matter of any one of Examples 76-80 and optionally, wherein the receiver is to receive the message from another cellular node.
    • Example 88 includes the subject matter of Example 87 and optionally, wherein the message comprises a handover request message from the other cellular node, the handover request message including an identifier of a UE to be handed over from the other cellular node to the cellular node and to be enabled for LI.
  • Functions, operations, components and/or features described herein with reference to one or more embodiments, may be combined with, or may be utilized in combination with, one or more other functions, operations, components and/or features described herein with reference to one or more other embodiments, or vice versa.

Claims (13)

  1. An Evolved Node B, eNB, (104) comprising:
    a receiver (130, 190) configured to receive a handover request message from another eNB (106), the handover request message including an identifier of a user equipment (102) to be handed over from the other eNB (106) to said eNB (104) and a lawful interception information element indicating said eNB (104) is to enable lawful interception for said user equipment (102) to be handed over to said eNB (104); and
    a controller (144) configured to disable, based on said lawful interception information element, one or more operations with respect to content to be communicated with the user equipment (102).
  2. The eNB (104) of claim 1, wherein said one or more operations comprise at least one operation selected from the group consisting of edge caching and traffic offloading.
  3. The eNB (104) of claim 2, wherein said traffic offloading comprises selected IP traffic offload at local network, SIPTO@LN.
  4. The eNB (104) of any one of claims 1-3, wherein said content comprises content, for which lawful interception cannot be performed by a network entity of a core network.
  5. An eNB (104) by comprising: a transmitter (130, 190) configured to transmit to another eNB (106) a handover request message including an indication of a user equipment (102) to be handed over from said eNB (104) to said other eNB (106), said message including a lawful interception information element indicating said other eNB (106) is to enable lawful interception of content to be communicated with said user equipment (102).
  6. The eNB (104) of claim 5, wherein said information element indicates to said other eNB (106) to disable for said user equipment (102) one or more operations selected from the group consisting of edge caching and traffic offloading.
  7. The eNB (104) of claim 6, wherein said traffic offloading comprises selected IP traffic offload at local network, SIPTO@LN.
  8. The eNB (104) of any one of claims 5-7, wherein said handover request message comprises an X2 Application Protocol message.
  9. A method comprising the step of: communicating, from another eNB (106), a handover request message addressed to an eNB (104), the handover request message including an identifier of a user equipment (102) to be handed over from the other eNB (106) to said eNB (104) and a lawful interception information element indicating that content corresponding to a user equipment (102) connected to said eNB (104) is to be subject to lawful interception.
  10. The method of claim 9 further comprising the steps of:
    receiving said message by said eNB (104); and
    disabling, by said eNB (104) and based on said lawful interception information element, one or more operations with respect to content to be communicated with the user equipment (102)
  11. The method of any one of claim 9 or 10 further comprising the step of disabling for the user equipment (102) one or more operations selected from the group consisting of edge caching and traffic offloading.
  12. A non-transitory storage medium having stored thereon instructions that, when executed by an eNB (104) , cause the eNB (104) to:
    receive a handover request message from another eNB (106), the handover request message including an identifier of a user equipment (102) to be handed over from the other eNB (106) to said eNB (104) and a lawful interception information element indicating said eNB (104) is to enable lawful interception for said user equipment (102) to be handed over to said eNB (104); and
    disable, based on said lawful interception information element, one or more operations with respect to content to be communicated with the user equipment (102).
  13. A non-transitory storage medium having stored thereon instructions that, when executed by another eNB (106), cause the other eNB (106) to: communicate a handover request message addressed to an eNB (104), the handover request message including an identifier of a user equipment (102) to be handed over from the other eNB (106) to said eNB (104) and a lawful interception information element indicating that content corresponding to a user equipment (102) connected to said eNB (104) is to be subject to lawful interception.
EP13870368.1A 2013-01-03 2013-10-14 Apparatus, system and method of lawful interception (li) in a cellular network Active EP2941936B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201361748706P 2013-01-03 2013-01-03
PCT/US2013/064756 WO2014107208A1 (en) 2013-01-03 2013-10-14 Apparatus, system and method of lawful interception (li) in a cellular network

Publications (3)

Publication Number Publication Date
EP2941936A1 EP2941936A1 (en) 2015-11-11
EP2941936A4 EP2941936A4 (en) 2016-09-28
EP2941936B1 true EP2941936B1 (en) 2019-09-11

Family

ID=66168941

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13870368.1A Active EP2941936B1 (en) 2013-01-03 2013-10-14 Apparatus, system and method of lawful interception (li) in a cellular network

Country Status (3)

Country Link
US (1) US10009813B2 (en)
EP (1) EP2941936B1 (en)
WO (1) WO2014107208A1 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100417973C (en) * 2001-09-13 2008-09-10 陈振华 Method and apparatus for digital image exposure on photo sensitive material
EP2920918B1 (en) * 2012-11-15 2019-06-19 Telefonaktiebolaget LM Ericsson (publ) Method for providing a law enforcement agency with sampled content of communications
JP6117986B2 (en) * 2013-04-05 2017-04-19 ノキア ソリューションズ アンド ネットワークス オサケユキチュア Avoiding key mismatch in security handling of multiple frequency bands
US9277429B2 (en) * 2013-08-06 2016-03-01 Cellos Software Ltd. Monitoring probe for identifying a user plane identifier of a user device
US10298714B2 (en) 2014-06-11 2019-05-21 Convida Wireless, Llc Mapping service for local content redirection
JP2019110354A (en) * 2016-04-25 2019-07-04 株式会社Ｎｔｔドコモ Exchange and communication method
EP3582478A4 (en) * 2017-02-28 2019-12-18 Huawei Technologies Co., Ltd. Lawful interception method, device, and system
CN108696895B (en) * 2017-04-07 2020-10-09 华为技术有限公司 Resource acquisition method, device and system
EP3744116A1 (en) * 2018-01-26 2020-12-02 Nokia Technologies OY Lawful interception using service-based interfaces in communication systems
JP7283868B2 (en) * 2018-08-10 2023-05-30 シャープ株式会社 User device, control device, and communication control method
US10798635B2 (en) * 2018-12-03 2020-10-06 At&T Intellectual Property I, L.P. Mobile edge computing for data network traffic

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6963739B2 (en) 2002-10-21 2005-11-08 Motorola, Inc. Method and apparatus for providing information intercept in an ad-hoc wireless network
GB0407347D0 (en) 2004-03-31 2004-05-05 Nokia Corp Monitoring quality of service in a wireless communications network
US8289924B2 (en) 2006-08-24 2012-10-16 Panasonic Corporation Communication system, communication method, radio terminal, radio relay device, and control device
CN101548488B (en) 2006-12-07 2012-10-24 三菱电机株式会社 Radio communication system, radio terminal station, radio base station, and radio communication method
EP2152032B1 (en) 2008-08-07 2012-10-03 Nokia Siemens Networks OY Providing lawful intercept information at a network element being assigned to a cell of a mobile telecommunication network
US8437741B2 (en) 2008-12-19 2013-05-07 Tecore Intelligent network access controller and method
US8190119B2 (en) 2009-03-03 2012-05-29 E3 Llc System and method for direct communication between wireless communication devices
CN102422703B (en) 2009-03-12 2014-09-17 诺基亚通信公司 Device-to-device communication
US9351340B2 (en) 2009-04-08 2016-05-24 Nokia Technologies Oy Apparatus and method for mode selection for device-to-device communications
US8213360B2 (en) 2009-04-29 2012-07-03 Nokia Corporation Apparatus and method for flexible switching between device-to-device communication mode and cellular communication mode
US8831014B2 (en) * 2009-09-26 2014-09-09 Cisco Technology, Inc. Providing services at a communication network edge
WO2011049499A1 (en) 2009-10-23 2011-04-28 Telefonaktiebolaget L M Ericsson (Publ) Li reporting of updated location information for eps
AU2010313987B2 (en) * 2009-11-02 2014-05-08 Lg Electronics Inc. NAT traversal for local IP access
KR101173628B1 (en) 2009-11-20 2012-08-13 경북대학교 산학협력단 Ad-hoc wireless instant messenger system and service security method thereof
US8588109B2 (en) 2009-12-11 2013-11-19 Verizon Patent And Licensing Inc. Integrated lawful intercept for internet protocol multimedia subsystem (IMS) over evolved packet core (EPC)
US9628579B2 (en) * 2010-05-13 2017-04-18 Futurewei Technologies, Inc. System, apparatus for content delivery for internet traffic and methods thereof
US20120294163A1 (en) 2011-05-19 2012-11-22 Renesas Mobile Corporation Apparatus and Method for Direct Device-to-Device Communication in a Mobile Communication System
JP5803696B2 (en) * 2012-01-25 2015-11-04 富士通株式会社 Network system, offload apparatus, and user identification information acquisition method for offload apparatus
US20130203380A1 (en) 2012-02-05 2013-08-08 Institute For Information Industry Network device, core network, direct mode communication system and lawful interception method thereof
US9240881B2 (en) 2012-04-30 2016-01-19 Alcatel Lucent Secure communications for computing devices utilizing proximity services
US10045357B2 (en) 2012-05-15 2018-08-07 Telefonaktiebolaget Lm Ericsson (Publ) Interference management for network assisted device-to-device communication
EP2856734A1 (en) * 2012-06-04 2015-04-08 Interdigital Patent Holdings, Inc. Lawful interception for local selected ip traffic offload and local ip access performed at a non-core gateway
EP2912866B1 (en) 2012-10-29 2019-04-17 Koninklijke KPN N.V. Intercepting device-to-device communication
US9072027B2 (en) 2012-12-07 2015-06-30 Alcatel Lucent Methods and apparatuses for facilitating D2D bearer switching
US9532213B2 (en) 2013-01-17 2016-12-27 Intel IP Corporation Lawful interception for device-to-device (D2D) communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP2941936A1 (en) 2015-11-11
US20150016413A1 (en) 2015-01-15
EP2941936A4 (en) 2016-09-28
US10009813B2 (en) 2018-06-26
WO2014107208A1 (en) 2014-07-10

Similar Documents

Publication Publication Date Title
EP2941936B1 (en) Apparatus, system and method of lawful interception (li) in a cellular network
US11082890B2 (en) Method, system and apparatus of wireless local area network (WLAN) communication in conjunction with cellular communication
US10292180B2 (en) Apparatus, system and method of communicating non-cellular access network information over a cellular network
US10306460B2 (en) Establishment of connection to the internet
KR102342278B1 (en) Failure handling method, switching method, terminal device, and network device
US9392519B2 (en) Apparatus, system and method of tunneling data radio bearers via a wireless local area network link
EP3092845B1 (en) Apparatus, system and method of providing offloadability information to a user-equipment (ue)
US20140099957A1 (en) Method, apparatus and system of membership verification
US20150181565A1 (en) Apparatus, system and method of triggering a wireless-local-area-network (wlan) action of a user equipment (ue)
US9467926B2 (en) Apparatus, method, and system of establishing a connection between a cellular node and a core network

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20150603

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20160826

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/14 20090101ALN20160822BHEP

Ipc: H04W 12/02 20090101ALI20160822BHEP

Ipc: H04L 29/06 20060101AFI20160822BHEP

Ipc: H04W 88/06 20090101ALN20160822BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602013060528

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0088080000

Ipc: H04L0029060000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 12/02 20090101ALI20190415BHEP

Ipc: H04L 29/06 20060101AFI20190415BHEP

Ipc: H04W 88/06 20090101ALN20190415BHEP

Ipc: H04W 36/00 20090101ALN20190415BHEP

INTG Intention to grant announced

Effective date: 20190506

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1179961

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190915

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602013060528

Country of ref document: DE

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191211

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191212

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1179961

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190911

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200113

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200224

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013060528

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: PD

Owner name: APPLE INC.; US

Free format text: DETAILS ASSIGNMENT: CHANGE OF OWNER(S), ASSIGNMENT; FORMER OWNER NAME: INTEL CORPORATION

Effective date: 20200527

Ref country code: DE

Ref legal event code: R081

Ref document number: 602013060528

Country of ref document: DE

Owner name: APPLE INC., CUPERTINO, US

Free format text: FORMER OWNER: INTEL CORPORATION, SANTA CLARA, CALIF., US

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG2D Information on lapse in contracting state deleted

Ref country code: IS

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191014

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191031

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200112

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20191031

26N No opposition filed

Effective date: 20200615

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191014

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20131014

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602013060528

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190911

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230526

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230830

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240829

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20240909

Year of fee payment: 12

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20240917

Year of fee payment: 12