WO2012136245A1 - Prise en compte de la confidentialité lors de l'utilisation d'une minimisation de tests de couverture radio (mdt) basée sur une zone - Google Patents

Prise en compte de la confidentialité lors de l'utilisation d'une minimisation de tests de couverture radio (mdt) basée sur une zone Download PDF

Info

Publication number
WO2012136245A1
WO2012136245A1 PCT/EP2011/055210 EP2011055210W WO2012136245A1 WO 2012136245 A1 WO2012136245 A1 WO 2012136245A1 EP 2011055210 W EP2011055210 W EP 2011055210W WO 2012136245 A1 WO2012136245 A1 WO 2012136245A1
Authority
WO
WIPO (PCT)
Prior art keywords
area
value
counter
threshold value
network
Prior art date
Application number
PCT/EP2011/055210
Other languages
English (en)
Inventor
Gyula Bodog
Silke Holtmanns
Ulrich Dropmann
Original Assignee
Nokia Siemens Networks Oy
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 Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2011/055210 priority Critical patent/WO2012136245A1/fr
Publication of WO2012136245A1 publication Critical patent/WO2012136245A1/fr

Links

Classifications

    • 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
    • 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
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the exemplary and non-limiting embodiments of this invention relate generally to wireless communications net- works, and more particularly to minimization of drive- tests.
  • MDT drive-tests
  • MDT data provides the network operator with valuable information on the network performance, thus reducing the need for separate drive-tests ter ⁇ minals .
  • a method for maintaining a threshold value regarding a minimum number of user terminals in a predefined area of a network determining a value of a counter regarding a number of active user terminals currently located in said area; comparing the threshold value and the value of the counter; wherein if, based on the comparing, it is found out that the value of the counter is below the threshold value, the method comprises defin ⁇ ing that the activation of a minimization of drive-tests function is not allowed in said area.
  • an apparatus configured to main ⁇ tain a threshold value regarding a minimum number of user terminals in a predefined area of a network; determine a value of a counter regarding a number of active user terminals currently located in said area; compare the thresh- old value and the value of the counter; wherein if, based on the comparing, it is found out that the value of the counter is below the threshold value, the apparatus is configured to define that the activation of a minimization of drive-tests function is not allowed in said area.
  • a computer-readable storage me ⁇ dium embodying a program of instructions executable by a processor to perform actions directed toward maintaining, in a network apparatus, a threshold value regarding a minimum number of user terminals in a predefined area of a network; determining, in the network apparatus, a value of a counter regarding a number of active user terminals currently located in said area; comparing, in the network ap ⁇ paratus, the threshold value and the value of the counter; wherein if, based on the comparing, it is found out that the value of the counter is below the threshold value, the method comprises defining, in the network apparatus, that the activation of a minimization of drive-tests function is not allowed in said area.
  • Figure 1 shows a simplified block diagram illus- trating an exemplary system architecture
  • Figure 2 shows a simplified block diagram illus ⁇ trating exemplary apparatuses
  • Figure 3 shows a messaging diagram illustrating an exemplary messaging event according to an exemplary em- bodiment
  • Figure 4 shows a schematic diagram of a flow chart according to an exemplary embodiment.
  • MDT data collection may be carried out on a user terminal having a certain IMSI or IMEI number (or some other device identifier) , for a specific area, or for a combination of these.
  • IMSI or IMEI number or some other device identifier
  • the selection of the user terminal is carried out, for example, on the basis of certain user terminal capabilities (e.g. memory capacity, battery capacity, GPS module availability, logging support, and/or general MDT specific signalling support) .
  • 3GPP For signalling-based MDT, it has already been agreed that user consent information is added as part of the sub ⁇ scription data in a home subscriber server (HSS) .
  • HSS home subscriber server
  • signalling-based MDT When signalling-based MDT is started for a spe- cific IMSI or IMEI to improve the network service for an individual user, the user consent information is checked and the MDT activation continues only when the user consent is available. It should be noted that the signalling- based MDT focuses to improve the network for an individual user; hence, in that situation, it is clear that the user is identifiable.
  • one option is to provide a subscriber ID to the MDT record only when there is a user consent available, otherwise the MDT data is anonymous.
  • Another option is to transfer the user consent information to the radio network, and when the radio network selects suitable UEs for MDT participation, the radio network also takes the user consent information into account. This has a strong impact on the network and also the user may not understand the difference between area MDT and signalling MDT.
  • data on an individual user cannot be identified with MDT management functionality, if a "sufficient amount" of measurement data is accumulated and personal information like the user identity is removed. Instead, the individual user data that may identify the user or his location, is then hidden by the crowd even if the node processing the MDT data has received further information from other nodes, and the user privacy may thus be protected.
  • An exemplary embodi ⁇ ment outlines a method how to protect the user privacy by ensuring that there is a sufficient amount of measurement data, and what is to be done when the user moves in/out of the location area, routing area, and/or tracking area.
  • a counter is imple ⁇ mented to eNB/RNC, which counter shows the number of users in a cell.
  • the counter is updated when a user leaves the cell or joins the cell, i.e. joining and/or leaving the cell triggers a change to the counter.
  • the counter may also be implemented with a status inspection, i.e. by checking the amount of active users in the area periodically, e.g. every 5 second or so.
  • a threshold is defined, which threshold may be configured by OAM directly to eNB/RNC according to local privacy legislation and is set by a regulator. If the number of users in the cell ex- ceeds the threshold, eNB/RNC may activate MDT for the us ⁇ ers in the cell. If the threshold is not reached (i.e. the number of users in the cell is below the threshold) , then no drive-test data is collected and MDT is not activated for the users in the cell.
  • the collected MDT data may be anonymized to not include any temporary or perma ⁇ nent subscriber IDs.
  • the data may be stored in a union of data to avoid that by matching different sets of data one could trace a user.
  • MDT data is collected from at least a certain number of users.
  • a certain user is available in that lo ⁇ cation .
  • a counter is imple ⁇ mented in eNB/RNC.
  • An attribute is defined in a UTRAN/E- UTRAN network resource model, which attribute defines the threshold. This attribute is configurable from the network management system.
  • the threshold parameter is added as an additional parameter to the MDT activation pa ⁇ rameters for the management-based MDT.
  • an ad ⁇ ditional attribute may be needed in an act ivateTraceJob operation in a traceIRP functionality.
  • an exemplary embodiment relates to privacy handling in management-based MDT.
  • management-based MDT to ensure the user privacy, a data collection big enough is required.
  • An exemplary embodiment technically ensures that the MDT data is collected for a certain (at least a minimum) number of users to ensure user privacy.
  • a counter in eNB/RNC configurable by network management allows to determine whether the minimum number of users is to participate the MDT session, i.e. whether the data to be collected from the terminals is sufficiently anonymous.
  • An attribute re ⁇ siding in eNB/RNC does not require a chain of interfaces, and it enables providing sufficient data anonymity.
  • the counter may not only be used to count the number of active users in the area, but the counter may also be used to count the number of active users that have GPS (active) in the area.
  • the present invention is applicable to any user terminal, server, corresponding component, and/or to any communication system or any combination of different communication systems that support a minimization of drive- tests (MDT) functionality.
  • the communication system may be a fixed communication system or a wireless communication system or a communication system utilizing both fixed net- works and wireless networks.
  • the protocols used, the specifications of communication systems, servers and user terminals, especially in wireless communication develop rapidly. Such development may require extra changes to an embodiment. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate, not to restrict, the embodiment.
  • the radio system is based on LTE network elements.
  • the invention de- scribed in these examples is not limited to the LTE radio systems but can also be implemented in other radio sys ⁇ tems, such as UMTS (universal mobile telecommunications system) , GSM, EDGE, WCDMA, bluetooth network, WLAN or other mobile or wireless network.
  • the presented solution may be applied between user equipment belonging to different but compatible systems such as LTE and UMTS.
  • Figure 1 is a simplified sys- tern architecture only showing some elements and functional entities, all being logical units whose implementation may differ from what is shown.
  • the connections shown in Figure 1 are logical connections; the actual physical connections may be different. It is apparent to a person skilled in the art that the systems also comprise other functions and structures. It should be appreciated that the functions, structures, elements, and protocols used in or for wire ⁇ less communication are irrelevant to the actual invention. Therefore, they need not be discussed in more detail here.
  • the exemplary radio system of Figure 1 comprises a network node 101.
  • the network node 101 may include e.g. an operations, administrations and maintenance (OAM) node, or any other network element or a combination of network elements.
  • the network node 101 is connected to a radio net- work node 102.
  • the radio network node 102 may include e.g. a radio network controller (RNC) , base station, access point, enhanced node B (eNB) or any other radio network element or a combination of radio network elements.
  • RNC radio network controller
  • eNB enhanced node B
  • the network node 101 and the radio network node 102 are con ⁇ nected to each other via a connection 103 or via one or more further network elements.
  • the radio net ⁇ work node 102 that may also be called eNB/RNC (enhanced node B/radio network controller) of the radio system hosts the functions for radio resource management in a public land mobile network.
  • Figure 1 shows one or more user equipment 104 located in the service area of the radio network node 102.
  • the user equipment refers to a portable computing device, and it may also be referred to as a user terminal.
  • Such computing devices include wireless mobile communication devices operating with or without a sub- scriber identification module (SIM) in hardware or in software, including, but not limited to, the following types of devices: mobile phone, smart-phone, personal digital assistant (PDA), handset, laptop computer.
  • SIM sub- scriber identification module
  • the user equipment 104 is capable of connecting to the radio network node 102 via a connection 105.
  • Figure 1 only illustrates a simplified example.
  • the net-work may include more base stations and radio network controllers, and more cells may be formed by the base stations.
  • the networks of two or more operators may overlap, the sizes and form of the cells may vary from what is depicted in Figure 1, etc.
  • the communication sys ⁇ tem may also be able to communicate with other networks, such as a public switched telephone network.
  • the embodi- ments are not, however, restricted to the network given above as an example, but a person skilled in the art may apply the solution to other communication networks provided with the necessary properties.
  • the con ⁇ nections between different network elements may be real- ized with internet protocol (IP) connections.
  • Figure 2 illustrates examples of apparatuses ac ⁇ cording to embodiments of the invention.
  • IP internet protocol
  • Figure 2 shows a user equipment 104 located in the area of the radio net ⁇ work node or eNB/RNC 102.
  • the user equipment is configured to be in connection with the radio network node 102.
  • the user equipment or UE 104 comprises a controller 201 opera ⁇ tionally connected to a memory 202 and a transceiver 203.
  • the controller 201 controls the operation of the user equipment 104.
  • the memory 202 is configured to store soft- ware and data.
  • the transceiver 203 is configured to set up and maintain a wireless connection to the radio network node 102.
  • the transceiver is operationally connected to a set of antenna ports 204 connected to an antenna arrange ⁇ ment 205.
  • the antenna arrangement 205 may comprise a set of antennas.
  • the number of antennas may be one to four, for example.
  • the number of antennas is not limited to any particular number.
  • the user equipment 104 may also comprise various other components, such as a user interface, camera, and media player. They are not displayed in the figure due to simplicity.
  • the radio network node or eNB/RNC 102 comprises a controller 206 operationally con ⁇ nected to a memory 207 and a transceiver 208.
  • the control ⁇ ler 206 controls the operation of the radio network node 102.
  • the memory 207 is configured to store software and data.
  • the transceiver 208 is configured to set up and maintain a wireless connection to the user equipment 104 within the service area of the radio network node 102.
  • the transceiver 208 is operationally connected to an antenna arrangement 209.
  • the antenna arrangement may comprise a set of antennas.
  • the number of antennas may be two to four, for example.
  • the number of antennas is not limited to any particular number.
  • the radio network node may be operationally connected (directly or indirectly) to an ⁇ other network element 101 of the communication system.
  • the network element 101 may be an operations, administrations and maintenance (OAM) node, a home location register (HLR) , visitor location register (VLR) , MSC server (MSS), a mobile switching centre (MSC) , serving GPRS support node, MME (mobility management entity) , a base station controller (BSC), a gateway, or a server, for example.
  • OAM operations, administrations and maintenance
  • HLR home location register
  • VLR visitor location register
  • MSC server MSC server
  • MSC mobile switching centre
  • serving GPRS support node MME (mobility management entity)
  • BSC base station
  • the network node 102 may be connected to more than one network element.
  • the network node 102 may comprise an interface 210 configured to set up and maintain connections with the network elements.
  • the network element or OAM 101 may com ⁇ prise a controller 211 and a memory 212 configured to store software and data and an interface 213 configured to be in connection with the network node 102.
  • the network element 101 may be operationally connected (directly or indirectly) to another network element of the communica ⁇ tion system.
  • the embodiments are not, however, restricted to the network given above as an example, but a person skilled in the art may apply the solution to other commu ⁇ nication networks provided with the necessary properties.
  • the connections between different network elements may be realized with internet protocol (IP) con- nections.
  • IP internet protocol
  • the memory may include volatile and/or non ⁇ volatile memory and typically stores content, data, or the like.
  • the memory may store computer program code such as software applications (for example for the detector unit and/or for the adjuster unit) or operating systems, information, data, content, or the like for the processor to perform steps associated with operation of the apparatus in accordance with embodiments.
  • the memory may be, for example, random access memory (RAM) , a hard drive, or other fixed data memory or storage device. Fur ⁇ ther, the memory, or part of it, may be removable memory detachably connected to the apparatus.
  • an apparatus implementing one or more functions of a corresponding mobile entity described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of a corresponding apparatus described with an embodiment and it may comprise separate means for each separate function, or means may be configured to perform two or more func- tions.
  • these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combina ⁇ tions thereof.
  • implementation can be through modules (e.g., procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in any suitable, proces ⁇ sor/computer-readable data storage medium(s) or memory unit(s) or article (s) of manufacture and executed by one or more processors/computers.
  • the data storage medium or the memory unit may be implemented within the proces ⁇ sor/computer or external to the processor/computer, in which case it can be communicatively coupled to the proc ⁇ essor/computer via various means as is known in the art.
  • User equipment may refer to any user communication device.
  • a term "user equipment” as used herein may refer to any device having a communication capability, such as a wireless mobile terminal, a PDA, tablet, a smart phone, a personal computer (PC) , a laptop computer, a desktop com ⁇ puter, etc.
  • the wireless communication termi- nal may be an UMTS or GSM/EDGE smart mobile terminal hav ⁇ ing wireless modem.
  • the application capabilities of the device according to various embodiments of the inven ⁇ tion may include native applications available in the ter ⁇ minal, or subsequently installed applications by the user or operator or other entity.
  • the operations, administra ⁇ tions and maintenance node may be implemented in any net ⁇ work element, such as a server.
  • an appa- ratus 102 which may comprise e.g. an enhanced node-B/radio network controller (eNB/RNC) , receives, in step 302, a threshold value transmitted 301 from a network node 101 such as an operations, administrations and maintenance (OAM) node.
  • the received threshold value may be stored 302 in a memory by the apparatus 102.
  • the appa- ratus receives 304 signalling from one or more active user terminals 104 located in the area of the apparatus 102.
  • the apparatus 102 is able to determine 304 the number of active user terminals in a predefined area of the network (the predefined area may comprise e.g. a cell, a location area, a routing area and/or a tracking area) .
  • the signalling 303 may comprise e.g. location update signalling and/or some other call setup/session setup signalling between the user terminals 104 and the apparatus 102.
  • the terminal may send the MDT measurements on its own initiative or the terminal may be triggered by the network to send the MDT measurements.
  • the apparatus is configured determine a value of a counter (which counter value is updated 304 by the apparatus 102 when a user terminal enters and/or leaves the area) .
  • the counter may also be implemented by using a sampling method, i.e. the apparatus may be confi ⁇ gured to check the number of active UEs or connections pe ⁇ riodically (in predetermined time intervals, e.g. every 5 second) .
  • a threshold value is set by the operator and de ⁇ fined by local legislation/regulator.
  • the apparatus is configured to compare the threshold value and the value of the counter.
  • the apparatus is configured to define 304 that activation of a minimization of drive-tests function is not allowed in the area in question (i.e. the number of user terminals located in the area is too low, which jeop ⁇ ardizes the anonymity/privacy of the user terminals; thus, minimization of drive-tests function is not allowed at that time in said area e.g. due to legislative privacy re- quirements) .
  • the apparatus may define 304 that the activation of a minimization of drive-tests function is allowed in said area.
  • the apparatus is configured to store the updated threshold value and perform the compar ⁇ ing and defining steps by using the updated threshold value.
  • the apparatus 102 is configured to store the updated counter value and perform the comparing and defining steps by using the updated counter value and the latest thresh ⁇ old value. The apparatus is thus able to decline drive- tests whenever the number of the active user terminals in the area is lower than the threshold value defined for that area.
  • "Active" user terminals herein may refer to user terminals that have an on-going call and/or session, or that are in a standby/idle mode.
  • FIG. 4 is a flow chart illustrating a non- limiting embodiment of the invention.
  • the ap ⁇ paratus 102 receives the threshold value from the network element 101.
  • the apparatus 102 may store the threshold value in a memory.
  • the apparatus 102 receive signalling from one or more active user termi- nals 104 located in the area of the apparatus 102.
  • the apparatus 102 determines, based on the received signalling, the number of active user terminals 104 in the predefined area.
  • the apparatus 102 deter ⁇ mines, based on the number of the user terminals 104 in the predefined area, the value of the UE counter.
  • the counter may not only be used to count the number of active users in the area, but the counter may also be used to count the number of active users that have GPS (active) in the area.
  • the apparatus 102 compares the threshold value and the value of the counter. If, based on the comparing, it is found out that the value of the counter is below the threshold value, the apparatus 102 is configured to define, in step 407, that the activation of the minimization of drive-tests function is not allowed in the area. If, based on the comparing, it is found out that the value of the counter exceeds the threshold value or equals to the threshold value, the apparatus 102 defines, in step 408, that the activation of the minimization of drive-tests function is allowed in the area.
  • the apparatus 102 When/if the threshold value is updated by OAM, the apparatus 102 re- ceives, in step 409, the updated threshold value, and re- performs the steps 402 to 407/408 by using the updated threshold value.
  • the apparatus 102 receives, in step 410, corresponding signalling, and re-performs the steps 404 to 407/408 by using the updated counter value.
  • MDT drive tests
  • An exemplary embodiment enables protecting the privacy of the user location against direct extraction and against at ⁇ tempts to determine the user's location by combining in ⁇ formation.
  • signalling and management MDT may be made.
  • the collected data may be criti ⁇ cally reviewed and the collection of data for the network management purpose may be minimized.
  • the minimization of drive-tests (MDT) functional ⁇ ities include different trace types signalling trace and management trace: signalling MDT is mainly used to im- prove/troubleshoot services of one specific sub ⁇ scriber/user based on radio measurements; management or area MDT is based on radio measurements to improve the ra ⁇ dio network performance for a specific area. They may be deployed together or independently of each other, i.e. an operator may deploy management MDT without deploying sig ⁇ nalling MDT and the other way around. The usage may also depend on the use cases within an operator. For example, after a customer complaint, operator may use signalling MDT, while for optimizing the network or checking the network coverage after new capacity expansion/cell installa ⁇ tion, the operator may use management MDT.
  • the collected data sets are differentiated for two modes: device con ⁇ nected mode also called immediate MDT, and logged MDT mode (i.e. when the terminal is in an idle mode) .
  • device con ⁇ nected mode also called immediate MDT
  • logged MDT mode i.e. when the terminal is in an idle mode.
  • the following information is collected for management based MDT.
  • logged MDT the following data is collected:
  • RSCP received signal code power
  • RSSI received signal strength indicator
  • eNB when UE goes to an idle mode, eNB deletes any context, but the logging ability re ⁇ sides purely in UE .
  • information which is available in UE may be stored in its memory as logged data for MDT pur ⁇ poses.
  • UE reads broadcasted system information and searches for a suitable cell even if UE is in the idle mode. If a suitable cell is found UE "camps on" this cell. Therefore, UE knows the cell-ID (even though UE does not have dedicated connection to the cell) .
  • MDT does not require a specific action from the network to get detailed location information (more detailed than the cell-ID) .
  • the intention of MDT is to provide the best data to the opera- tor to support the operator in improving the network service i.e. potentially GPS. But there needs to be an active GPS modem (not only present, but also activated) .
  • UE may get geographical coordinates based on user plane posi- tioning flow (a positioning server and client reside on the application layer and communicate over a packet data connection) but without radio access network assistance. This is possible if UE does not have an active dedicated connection to the network.
  • the MDT data gathered and ob- tained in the idle mode is not immediately communicated to eNB . If UE connects to eNB at the same point, UE indicates that it has logged some MDT data that eNB may decide to retrieve .
  • the data flow may be as follows.
  • the UE measure ⁇ ments are transferred to eNB/RNC.
  • eNB/RNC forwards them to a management entity that is called TCE .
  • TCE pairs the measurements with subscriber identities based (re ⁇ ceived from MME) on a trace reference (TR) and a trace re- cording session reference (TRSR) embedded in each report sent to TCE by the network entities.
  • TR trace reference
  • TRSR trace re- cording session reference
  • the collected data is differentiated based on trace reference.
  • the trace recording session reference is allocated for each connec ⁇ tion separately, that is used to correlate the data that belongs to one MDT session.
  • a logging area may be configured, which may be taken into account before investigating privacy risks.
  • UE logs measurements as long as it is within the configured logging area.
  • the scope of the logging area may include one of: 1) a list of 32 global cell identities; if this list is configured, UE only logs measurements when camping in any of these cells, 2) a list of 8 TAs or 8 LAs or 8 RAs . If this list is con ⁇ figured, UE only logs measurements when camping in any cell belonging to the preconfigured TA/LA/RAs. If no area scope is configured, the configuration is valid in the en ⁇ tire MDT PLMN of UE, i.e. UE logs measurements throughout MDT PLMN.
  • a concern is the GPS coordinate of the user. It should be noted, that there is no user identity collected. So there is no possibility to identify an individual user directly. The combination with time, may allow some deduction, i.e. an unknown person is living here, but there is no individ- ual user identifier for this person to link the user to other measurements (e.g. if you have a trajectory, and are able to associate one point on the trajectory with a known user, e.g. his home, then you know the movements of the user) . Another issue is the tracking of a user using the point on a trajectory. Again, it is anonymous tracking, since the individual measurements have no identifier, the tracking of a user is made impossible.
  • the threshold may be seen in relation to the size of the area (if you have quite fine-grained location data and time, then, assuming a certain user speed, you may have a software trying to map out trajectories; the degree of privacy protection may depend on the effort an attacker is willing to spend; these aspects may be taken into account here when deter- mining a threshold value (as with the number of users that have to be present in an area) so that privacy may be con ⁇ sidered guaranteed for practical purposes) .
  • a solution to hide individual data in a larger crowd of k may be re ⁇ ferred to as k-anonymity or optimal k-anonymization .
  • trace reference cannot be associated to any subscriber as that identifies the trace session, which is for one or a set of cells.
  • MDT management may be deployed in an area where just few users are present.
  • One approach is to add a blan- ket user consent information element for the management MDT as it is today.
  • the reason may be that there are different data elements handled and the level privacy impact of signalling MDT is larger than for man- agement based MDT .
  • the unlikely case of a single user in an MDT measurement area might raise the concern.
  • the "management based MDT consent” information ele ⁇ ment may be set to "yes" in certain areas for all sub- scribers.
  • Another approach is to remove not needed data, remove user identifiers from the network protocols, prevent collection of identifiers that allows data combination in addition then combining data sets to a larger set making the identification of an individual device impossible.
  • a function in eNB may be used to measure the number of active users for layer 2 measurements. This function may also be utilized here to prevent potential user tracking for the unlikely case, that there is only one or very few users in a certain measurement area. In other words, this function allows one to set a threshold value and the management MDT function is only activated, when the threshold is reached.
  • a more fine grained approach is used (than asking for a "white-card" user consent), including minimizing data collection, making an individual user no-recognizable in the crowd, improving the service for the user, preventing that an operator has to contact his legacy users, preventing investments to be made without being able to improve the network, keeping this feature in Release 10.
  • a method comprising performing, in a network apparatus, the method steps of maintaining a threshold value regarding a minimum number of user terminals in a predefined area of a network; determining a value of a counter regarding a number of active user terminals cur- rently located in said area; comparing the threshold value and the value of the counter; wherein if, based on the comparing, it is found out that the value of the counter is below the threshold value, the method comprises defin ⁇ ing that the activation of a minimization of drive-tests function is not allowed in said area.
  • the method comprises defining, in the network apparatus, that activation of a minimization of drive-tests function is allowed in said area.
  • the method comprises defining that collecting drive-test data on the user terminals is allowed in said area.
  • a method wherein if the value of the counter is below the threshold the method comprises defin ⁇ ing that collecting drive-test data on the user terminals is not allowed in said area.
  • a method comprising updating the thresh- old value in response to recognising a predefined event in the network apparatus .
  • the predefined event comprises receiving an update message from an operations, administrations and maintenance node, the message including information on an updated threshold value.
  • a method comprising refraining from performing drive-tests on the user terminals in said area when the number of user terminals in said area is too low.
  • a method comprising updating the value of the counter when the number of user terminals in said area changes.
  • a method comprising updating the value of the counter when a user terminal leaves and/or enters said area.
  • said area comprises a network cell, a location area, a routing area and/or a tracking area.
  • an apparatus configured to maintain a threshold value regarding a minimum number of user terminals in a predefined area of a network; determine a value of a counter regarding a number of active user terminals currently located in said area; compare the threshold value and the value of the counter; wherein if, based on the comparing, it is found out that the value of the counter is below the threshold value, the apparatus is configured to define that the activation of a minimization of drive-tests function is not allowed in said area.
  • an apparatus wherein if, based on the comparing, it is found out that the value of the counter exceeds the threshold value or equals to the threshold value, the apparatus is configured to define that activa- tion of a minimization of drive-tests function is allowed in said area.
  • an apparatus wherein if the value of the counter exceeds or equals to the threshold value the apparatus is configured to define that collecting drive- test data on the user terminals is allowed in said area.
  • an apparatus wherein if the value of the counter is below the threshold the apparatus is con ⁇ figured to define that collecting drive-test data on the user terminals is not allowed in said area.
  • an apparatus configured to update the threshold value in response to recognising a predefined event in the apparatus .
  • an apparatus configured to refrain from performing drive-tests on the user terminals in said area when the number of user terminals in said area is too low.
  • an apparatus configured to update the value of the counter when the number of user terminals in said area changes.
  • an apparatus configured to update the value of the counter when a user terminal leaves and/or enters said area.
  • an apparatus configured to update the value of the counter periodically.
  • a computer-readable storage medium embo ⁇ dying a program of instructions executable by a processor to perform actions directed toward maintaining, in a net ⁇ work apparatus, a threshold value regarding a minimum num- ber of user terminals in a predefined area of a network; determining, in the network apparatus, a value of a counter regarding a number of active user terminals currently located in said area; comparing, in the network ap- paratus, the threshold value and the value of the counter; wherein if, based on the comparing, it is found out that the value of the counter is below the threshold value, the method comprises defining, in the network apparatus, that the activation of a minimization of drive-tests function is not allowed in said area.
  • the steps/points, signalling messages and related functions de-scribed above in Figures 1 to 4 are in no ab ⁇ solute chronological order, and some of the steps/points may be performed simultaneously or in an order differing from the given one. Other functions can also be executed between the steps/points or within the steps/points and other signalling messages sent between the illustrated messages. Some of the steps/points or part of the steps/points can also be left out or replaced by a corre- sponding step/point or part of the step/point.
  • the appara ⁇ tus operations illustrate a procedure that may be imple ⁇ mented in one or more physical or logical entities.
  • the signalling messages are only exemplary and may even comprise several separate messages for transmitting the same information. In addition, the messages may also contain other information.
  • UTRAN UMTS terrestrial radio access network E-UTRAN enhanced UMTS terrestrial radio access network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé consistant à garder (402), dans un appareil de réseau, une valeur de seuil concernant un nombre minimum de terminaux utilisateur dans une zone prédéfinie d'un réseau. L'appareil détermine (404) une valeur d'un compteur concernant un nombre de terminaux utilisateur actifs couramment situés dans ladite zone, et compare (405) la valeur de seuil et la valeur du compteur. S'il est trouvé (406) par la comparaison que la valeur du compteur est inférieure à la valeur de seuil, le procédé consiste à définir (407), dans l'appareil de réseau, que l'activation d'une fonction de minimisation de tests de couverture radio n'est pas autorisée dans ladite zone.
PCT/EP2011/055210 2011-04-04 2011-04-04 Prise en compte de la confidentialité lors de l'utilisation d'une minimisation de tests de couverture radio (mdt) basée sur une zone WO2012136245A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/055210 WO2012136245A1 (fr) 2011-04-04 2011-04-04 Prise en compte de la confidentialité lors de l'utilisation d'une minimisation de tests de couverture radio (mdt) basée sur une zone

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2011/055210 WO2012136245A1 (fr) 2011-04-04 2011-04-04 Prise en compte de la confidentialité lors de l'utilisation d'une minimisation de tests de couverture radio (mdt) basée sur une zone

Publications (1)

Publication Number Publication Date
WO2012136245A1 true WO2012136245A1 (fr) 2012-10-11

Family

ID=44625786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2011/055210 WO2012136245A1 (fr) 2011-04-04 2011-04-04 Prise en compte de la confidentialité lors de l'utilisation d'une minimisation de tests de couverture radio (mdt) basée sur une zone

Country Status (1)

Country Link
WO (1) WO2012136245A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013135874A1 (fr) * 2012-03-16 2013-09-19 Nokia Siemens Networks Oy Optimisation de la collecte de données basée sur le nombre d'équipements d'utilisateur qui rapportent les données et/ou sur le nombre d'échantillons de données rapportées, en vue d'exécuter une minimisation des essais de conduite (mdt)
CN103796217A (zh) * 2012-10-26 2014-05-14 中国移动通信集团设计院有限公司 一种基于路测数据的预测区域划分方法及装置
EP2866484A1 (fr) * 2013-10-24 2015-04-29 Telefónica Germany GmbH & Co. OHG Procédé d'anonymisation de données recueillies à l'intérieur d'un réseau de communication mobile
CN108401502A (zh) * 2018-02-06 2018-08-14 北京小米移动软件有限公司 测量配置方法及装置
CN108521876A (zh) * 2018-03-27 2018-09-11 北京小米移动软件有限公司 蓝牙设备的测量方法及装置
WO2019209463A1 (fr) 2018-04-27 2019-10-31 T-Mobile Usa, Inc. Agrégation de données de cellule de réseau pour traiter la confidentialité de l'utilisateur
US20220369114A1 (en) * 2019-10-01 2022-11-17 Ntt Docomo, Inc. Base station and measurement method

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NOKIA SIEMENS NETWORKS: "3GPP TSG SA Meeting #51, SP-110186, CR 0107 for 32.422 rev3", 18 March 2011 (2011-03-18), pages 1 - 3, XP002666131, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_51/Docs/> [retrieved on 20111220] *
NOKIA SIEMENS NETWORKS: "3GPP TSG SA Meeting #51, SP-110187, Considerations about user consent in case of area or management based MDT activation", 3GPP, no. Kansas City, USA, 21.-23.03.2011, 20 March 2011 (2011-03-20), pages 1 - 2, XP002666130, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_51/Docs/> [retrieved on 20111220] *
SA WG3: "3GPP TSG-SA WG3 Meeting #62, S3-110185, Reply LS on MDT user involvement", 3GPP DRAFT; S3-110185, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. San Diego, USA; 20110228, 16 February 2011 (2011-02-16), XP050530289 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013135874A1 (fr) * 2012-03-16 2013-09-19 Nokia Siemens Networks Oy Optimisation de la collecte de données basée sur le nombre d'équipements d'utilisateur qui rapportent les données et/ou sur le nombre d'échantillons de données rapportées, en vue d'exécuter une minimisation des essais de conduite (mdt)
CN103796217A (zh) * 2012-10-26 2014-05-14 中国移动通信集团设计院有限公司 一种基于路测数据的预测区域划分方法及装置
US10762237B2 (en) 2013-10-24 2020-09-01 Telefónica Germany GmbH & Co. OHG Method for anonymization of data collected within a mobile communication network
EP2866484A1 (fr) * 2013-10-24 2015-04-29 Telefónica Germany GmbH & Co. OHG Procédé d'anonymisation de données recueillies à l'intérieur d'un réseau de communication mobile
WO2015058860A1 (fr) * 2013-10-24 2015-04-30 Telefónica Germany GmbH & Co. OHG Procédé d'anonymisation de données collectées sur un réseau de communications mobiles
CN108401502A (zh) * 2018-02-06 2018-08-14 北京小米移动软件有限公司 测量配置方法及装置
US11395172B2 (en) 2018-02-06 2022-07-19 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for configuring measurement
US11368869B2 (en) 2018-03-27 2022-06-21 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for measuring bluetooth device
CN108521876B (zh) * 2018-03-27 2022-07-08 北京小米移动软件有限公司 蓝牙设备的测量方法及装置
CN108521876A (zh) * 2018-03-27 2018-09-11 北京小米移动软件有限公司 蓝牙设备的测量方法及装置
EP3777274A4 (fr) * 2018-04-27 2021-12-22 T-Mobile USA, Inc. Agrégation de données de cellule de réseau pour traiter la confidentialité de l'utilisateur
WO2019209463A1 (fr) 2018-04-27 2019-10-31 T-Mobile Usa, Inc. Agrégation de données de cellule de réseau pour traiter la confidentialité de l'utilisateur
US20220369114A1 (en) * 2019-10-01 2022-11-17 Ntt Docomo, Inc. Base station and measurement method

Similar Documents

Publication Publication Date Title
US9510203B2 (en) Network entity, communication device, mobile communication device and method thereof
RU2601835C2 (ru) Способ и система сбора данных результатов измерений для терминала
US9462529B2 (en) Method and apparatus for accounting of cell related data
US8577360B2 (en) UE-based MDT measuring and reporting in a cellular radio access network
WO2014077658A1 (fr) Procédé de rapport de mesure dans un système de communication sans fil et dispositif destiné à fonctionner selon ledit procédé
US9451477B2 (en) Method and system for implementing drive test
TWI675604B (zh) 通訊裝置，基礎結構設備，行動通訊網路及方法
WO2012136245A1 (fr) Prise en compte de la confidentialité lors de l&#39;utilisation d&#39;une minimisation de tests de couverture radio (mdt) basée sur une zone
KR102038001B1 (ko) 무선 통신 시스템에서 보고 방법 및 이를 지원하는 장치
EP3197202B1 (fr) Procédé et dispositif de création de rapport de qualité de réception de signal de référence
US20130083667A1 (en) Accessibility Measurements
US20170339589A1 (en) Network-Controlled Terminal Data Call Performance Testing
CN103458429A (zh) 一种最小化路测方法及网络管理系统及基站
CN103024769A (zh) 一种检查最小化路测配置的方法及网络设备
WO2016161771A1 (fr) Procédé et dispositif de réduction au minium de test d&#39;entraînement
WO2021203316A1 (fr) Gestion de signal de référence d&#39;affaiblissement le long du trajet
Sørseth Location disclosure in lte networks by using imsi catcher
US11405853B2 (en) Server, communication system, and performance measurement method
CN105284149B (zh) 用户设备、网络设备和日志最小化路测测量方法
CN110798852B (zh) 一种自组网的增强方法和终端设备
CN103874083A (zh) 一种评测多系统无线信号共覆盖的方法和系统
WO2013051984A1 (fr) Mesures d&#39;accessibilité

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11713736

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11713736

Country of ref document: EP

Kind code of ref document: A1