WO2012138083A2 - Appareil et procédé pour effectuer une révocation de consentement d'utilisateur à une réduction au minimum des tests de mesure de qualité de service en communication sans fil - Google Patents

Appareil et procédé pour effectuer une révocation de consentement d'utilisateur à une réduction au minimum des tests de mesure de qualité de service en communication sans fil Download PDF

Info

Publication number
WO2012138083A2
WO2012138083A2 PCT/KR2012/002439 KR2012002439W WO2012138083A2 WO 2012138083 A2 WO2012138083 A2 WO 2012138083A2 KR 2012002439 W KR2012002439 W KR 2012002439W WO 2012138083 A2 WO2012138083 A2 WO 2012138083A2
Authority
WO
WIPO (PCT)
Prior art keywords
mdt
user consent
enb
log
revocation
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.)
Ceased
Application number
PCT/KR2012/002439
Other languages
English (en)
Other versions
WO2012138083A3 (fr
Inventor
Myung Cheul Jung
Ki Bum Kwon
Jae Hyun Ahn
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.)
Pantech Co Ltd
Original Assignee
Pantech Co Ltd
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 Pantech Co Ltd filed Critical Pantech Co Ltd
Publication of WO2012138083A2 publication Critical patent/WO2012138083A2/fr
Publication of WO2012138083A3 publication Critical patent/WO2012138083A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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

Definitions

  • the present invention relates to wireless communication technology and, more particularly, to a method and apparatus for performing user consent revocation for a Minimization Driving Test (hereinafter referred to as an ‘MDT’).
  • MDT Minimization Driving Test
  • a wireless communication network In order to improve the capability of a wireless communication system, a wireless communication network must always take the improvements of throughput, frequency efficiency, mobility, coverage, and Multimedia Broadcast/Multimedia Service (MBMS) into consideration. With the development of wireless communication technology, factors affecting a wireless communication network have also been greatly changed.
  • MBMS Multimedia Broadcast/Multimedia Service
  • a wireless communication system typically uses one bandwidth in order to transmit data.
  • a different bandwidth is used in each of mobile communication generations.
  • the 2 nd generation wireless communication system uses a bandwidth of 200 KHz to 1.25 MHz
  • the 3 rd generation wireless communication system uses a bandwidth of 5 MHz to 10 MHz.
  • the bandwidth of the recent Long Term Evolution (LTE) or IEEE 802.16m of the 3 rd Generation Partnership Project (3GPP) is extending up to 20 MHz or higher.
  • a service provider In order to effectively operate a mobile communication system, a service provider must take several conditions into consideration according to environments. More particularly, a service provider must take how insufficient frequency resources will be used as described above, how degree a base station will have a cell radius when the base station is configured, and to what extent will the frequency requirements of a cell be set into consideration.
  • a service provider In order to effectively operate a system while maintaining high Quality of Service (QoS), a service provider needs to check a network coverage environment (e.g., a traffic quality state and a signal transmission/reception state within a cell) of a network locally.
  • a network coverage environment e.g., a traffic quality state and a signal transmission/reception state within a cell
  • An object of the present invention is to provide an apparatus and method for performing user consent revocation for an MDT in wireless communication technology.
  • Yet another object of the present invention is to provide an apparatus and method, wherein UE can stop performing an MDT and effectively manage resources necessary for the operation of the UE in a situation where it is difficult for the UE to perform the MDT or when the UE does not want to perform the MDT.
  • Still another object of the present invention is to provide an apparatus and method, wherein UE can take necessary measures in an evolved-NodeB (eNB) or a network by taking a reason of consent revocation into consideration when the UE revokes consent to an MDT.
  • eNB evolved-NodeB
  • Still yet another object of the present invention is to provide an apparatus and method for transmitting and receiving a user consent revocation reason for an MDT in wireless communication technology.
  • Still another object of the present invention is to provide transmission/reception apparatuses and transmission/reception methods for guaranteeing efficiency of a log report for an MDT in wireless communication technology.
  • the UE may determine to revoke the user consent to the MDT when available memory is smaller than predetermined reference memory.
  • the user consent revocation message may comprise a cause value of available memory shortage as the reason of the user consent revocation.
  • the UE may determine to revoke the user consent to the MDT when a remaining battery amount is smaller than a predetermined reference battery amount.
  • the user consent revocation message may comprise a cause value of battery shortage as the reason of the user consent revocation.
  • the method may further comprise determining whether log disposal processing is necessary, wherein if the log disposal processing is determined to be necessary, the UE may clear the stored MDT log although the MDT log fetch request message or the MDT log clear instruction message is not received from the eNB.
  • the UE may transmit the stored MDT log to the eNB and clear the stored MDT log when the MDT log fetch request message is received from the eNB, and the UE may clear the stored MDT log when the MDT log clear instruction message is received.
  • a method of an eNB processing revocation of user consent to an MDT comprising receiving user consent status information about UE from a network and changing a user consent status of the UE based on the user consent status information, wherein if an instruction for the UE is included in the user consent status information, the eNB may transmit a request message or an instruction message according to the instruction to the UE.
  • the eNB may transmit an MDT log fetch request message to the UE. If the user consent status information of the UE instructs the revocation of the user consent to the MDT and information on a reason of the user consent revocation of the UE is included in the user consent status information, the eNB may transmit an instruction, corresponding to the reason, to the UE. If the reason of the user consent revocation of the UE is memory shortage, the eNB may transmit an MDT log clear instruction, together with a log fetch request message, to the UE.
  • the eNB may transmit an MDT log fetch request message to the UE.
  • the eNB may change the user consent status of the UE based on the user consent status information of the UE and may receive an MDT log from the UE, and when the UE performs handover and releases a connection with the eNB, the eNB may change the user consent status of the UE based on the user consent status information of the UE.
  • UE supporting an MDT comprising a controller for controlling the execution of the MDT and generating an MDT log, a transceiver for transmitting or receiving pieces of information about the execution of the MDT including the MDT log, and memory for storing some or all of the pieces of information about the execution of the MDT including the MDT log.
  • the controller may transmit a user consent revocation message and information about a reason of the user consent revocation to a network and stop performing the MDT, when an MDT log fetch request message is received from an eNB, the controller may transmit the MDT log stored in the memory to the eNB through the transceiver and clear the MDT log stored in the memory, and when an MDT log clear instruction message is received from the eNB, the controller may clear the MDT log stored in the memory.
  • an eNB supporting an MDT comprising a controller for controlling the execution of an MDT, a transceiver for transmitting and receiving pieces of information about the execution of the MDT, and memory for storing some or all of the pieces of information about the execution of the MDT.
  • the controller may change a user consent status of the UE based on the user consent status information, and when an instruction for the UE is included in the user consent status information, the controller may transmit a request message or an instruction message according to the instruction to the UE through the transceiver.
  • a method of a network side processing user consent revocation for an MDT comprising receiving a user consent revocation message including a reason of the user consent revocation from UE, changing user consent status information of the UE based on the user consent revocation message, and transmitting a user consent status information message, including the changed user consent status information, to the serving cell eNB of the UE.
  • the user consent status information message may include an instruction for enabling the UE to handle the reason of the user consent revocation or a cause value corresponding to the reason of the user consent revocation.
  • a network node supporting an MDT comprising a transceiver for receiving information about a user consent revocation procedure for the execution of the MDT of UE, memory for storing information about the UE and an eNB accessing the network node, and a controller for changing a user consent status regarding the execution of the MDT of the UE based on the information about the user consent revocation procedure regarding the execution of the MDT, received from the UE.
  • the controller may transmit a user consent status information message, including the changed user consent status information, to the serving cell eNB of the UE.
  • the user consent status information message may include an instruction for enabling the UE to handle a reason of user consent revocation or a cause value corresponding to the reason of the user consent revocation.
  • the UE may revoke the consent to the execution of the MDT and may stop performing the MDT or may not start performing the MDT. Accordingly, there is an advantage in that resources necessary for the operation of UE can be effectively managed.
  • an eNB or network can rapidly take necessary measures by taking a reason of the consent revocation into consideration. Furthermore, in accordance with the present invention, UE or an eNB or both or a network may take necessary measures by taking an MDT user consent revocation reason of the UE into consideration. Accordingly, a result according to the execution of an MDT may be utilized or resources necessary for the operation of UE can be effectively managed.
  • FIG. 1 is a conceptual diagram schematically showing a concept of a driving test for measuring wireless traffic quality or coverage or both by using a vehicle in a system to which the present invention is applied;
  • FIG. 3 is a flowchart schematically illustrating an example of an MDT configuration method in a system to which the present invention is applied;
  • FIG. 4 is a conceptual diagram schematically showing an example in which a log is configured in a periodic MDT in a system to which the present invention is applied;
  • FIG. 5 is a flowchart schematically illustrating a method of configuring an event-triggered MDT in a system to which the present invention is applied;
  • FIG. 6 is a conceptual diagram schematically showing an example in which a log is written in a mixed method of a periodic method and an event-triggered method in a system to which the present invention is applied;
  • FIG. 7 is a flowchart schematically illustrating an example in which the consent information of UE about the execution of an MDT is transmitted between an eNB and an MME;
  • FIG. 8 is a flowchart schematically illustrating the revocation of the user consent of UE to the execution of an MDT in a system to which the present invention is applied;
  • FIG. 9 is a flowchart schematically illustrating an embodiment in which a user consent revocation procedure is performed by taking a user consent revocation reason for the execution of an MDT into consideration in a system to which the present invention is applied;
  • FIG. 11 is a flowchart schematically illustrating yet another embodiment in which a user consent revocation procedure is performed by taking a user consent revocation reason for the execution of an MDT into consideration when UE performs handover in a system to which the present invention is applied;
  • FIG. 12 is a flowchart schematically illustrating a user consent revocation procedure performed by UE in a system to which the present invention is applied;
  • FIG. 13 is a flowchart schematically illustrating a user consent revocation procedure performed by a network in a system to which the present invention is applied;
  • FIG. 14 is a flowchart schematically illustrating a user consent revocation procedure performed by an eNB in a system to which the present invention is applied.
  • FIG. 15 is a block diagram schematically illustrating the construction each of the subjects of operations in a system to which the present invention is applied.
  • the focus of the description is a wireless communication network.
  • Tasks performed in the wireless communication network may be performed in a process in which a system (e.g., a base station) managing the wireless communication network controls the wireless communication network and sending data or may be performed in UE combined with the wireless communication network.
  • a system e.g., a base station
  • the wireless communication system to which the present invention is applied may have a 3GPP LTE/LTE-A network structure.
  • An Evolved-UMTS Terrestrial Radio Access Network includes a Base Station (BS) that provides a control plane and a user plane to the UE.
  • BS Base Station
  • the UE may be fixed or mobile and may also be called another terminology, such as a Mobile Station (MS), a User Terminal (UT), a Subscriber Station at step SS), a Mobile Terminal (MT), or a Wireless Device.
  • the BS refers to a fixed station which communicates with the UE, and it may also be called another terminology, such as an eNB, a Base Transceiver System (BTS), an access point.
  • the BS is hereinafter called an ‘eNB’.
  • An interface for transmitting user traffic or control traffic may be used between eNBs.
  • eNBs may be interconnected through an X2 interface.
  • an eNB may be connected to an Evolved Packet Core (EPC) through an S1 interface (more specifically, a Mobility Management Entity (MME) through an S1-MME and a Serving GateWay at step S-GW) through an S1-U).
  • EPC Evolved Packet Core
  • S1 interface more specifically, a Mobility Management Entity (MME) through an S1-MME and a Serving GateWay at step S-GW
  • MME Mobility Management Entity
  • S-GW Serving GateWay at step S-GW
  • a network service provider when constructing a wireless communication network, a network service provider optimizes an eNB or a network, such as or a cell environment, by checking the wireless traffic quality of UE or whether UE is out of coverage related to a cell radius or checking a coverage hold.
  • the network service provider may measure data for a network communication environment by utilizing the UE. For example, in order to check the intensity of a signal, the network service provider may effectively handle situations by checking a position where the UE can perform communication or checking a position where the UE is unable to perform communication owing to the attenuation of a signal.
  • the network service provider may use a measurement value related to traffic quality, including the signal intensity of an eNB.
  • FIG. 1 is a conceptual diagram schematically showing a concept of a driving test for measuring wireless traffic quality or coverage or both by using a vehicle in a system to which the present invention is applied.
  • a network service provider, etc. moves within the constructed traffic region of an eNB 100 (i.e., a cell) using a vehicle 710.
  • the vehicle 110 collects the traffic quality of the constructed traffic region by using UE, etc. mounted on the vehicle while moving all possible places within the cell.
  • the traffic quality within the cell is changed by various factors, such as the positions of buildings 130 or a geographical high and low within the cell. For example, there may be areas 140 and 150 where traffic is possible, and there may be a traffic shadow area 160. Furthermore, from among the areas where traffic is possible, there may be the area 140 where the traffic quality is good and the area 150 where the traffic quality is bad.
  • the traffic quality may be different depending on the distance from the eNB 100. For example, it may be expected that the area 140 where the traffic quality is good has a better traffic quality in terms of transmission power because it is closer to the eNB 100 than the area 150 where the traffic quality is bad. As described above, however, the traffic quality or a call status is influenced by various factors. When a geographical influence, such as the buildings 130, is taken into consideration, an actual traffic quality for each area may be different from an expected traffic quality. For example, an area may be the traffic shadow area 160 although the area is placed between the buildings and not far from the eNB 100.
  • a method of measuring traffic quality for a communication environment within a network i.e., a method of measuring the traffic quality within the network while minimizing a driving test (i.e., an MDT)) without measuring the traffic quality while directly moving all possible areas within a cell by using a vehicle, etc. may be taken into consideration.
  • the MDT may be divided into a periodic MDT and an event-triggered MDT depending on a method of performing measurement.
  • UE measures network communication quality and writes, stores, and manages a log in a predetermined period during a predetermined duration.
  • the log may be called information related to communication environments, such as the signal intensity of a serving cell or a neighbor cell, a position where the signal is measured, and the time when the signal is measured which are measured by UE and accumulated in memory.
  • the UE may continue to accumulate a log whenever the UE measures the state of a wireless communication environment as a new log form.
  • UE may report, to a network or an eNB, that the UE now has a log accumulated through the execution of an MDT. If UE is requested to report information about a log from a network or an eNB, the UE may transmit the log information to the network or the eNB.
  • UE performs MDT measurement when a triggering event is generated.
  • UE may perform MDT measurement and write a log according to a predetermined rule or instruction.
  • UE may perform MDT measurement and write a log only when there is an explicit request from a network although the triggering event is generated.
  • the MDT may be divided into an Immediate MDT (IMDT) and a Logged MDT (LMDT) depending on a mode in which measurement is performed.
  • IMDT Immediate MDT
  • LMDT Logged MDT
  • UE receives an MDT configuration in an RRC_CONNECTED mode.
  • UE in the RRC_CONNECTED mode may perform measurement based on an MDT configuration in a predetermined period. Furthermore, UE in the RRC_CONNECTED mode may perform measurement when a triggering event is generated according to an instruction of an eNB or a predetermined rule.
  • the UE may log the result of the measurement. For example, UE may log the result of measurement when a Radio Link Failure (RLF) occurs.
  • the UE may inform an eNB that the UE can report the log.
  • the eNB may check that the UE can report an MDT based on the received log.
  • RLF Radio Link Failure
  • UE in an RRC_IDLE mode may perform measurement at specific periods based on an MDT configuration. For example, UE may perform measurement based on an MDT configuration in a period set by a multiple of the 'On Duration' period of DRX. Furthermore, UE may perform measurement when a triggering event is generated according to an instruction of an eNB or a predetermined rule.
  • UE that has performed measurement based on an MDT configuration logs the result of the measurement.
  • UE in the RRC_IDLE mode may access a cell through, for example, a selection/reselection process.
  • the UE may inform an eNB that the UE can report a log in the process of accessing the cell.
  • the eNB may check that the UE can perform an MDT report based on the received log.
  • the eNB may request the MDT report from the UE. For example, an eNB may transmit an information request message, including a message requesting an MDT report. When the MDT report request message is received, UE may report MDT log information to the eNB.
  • the MDT may also be divided into a signaling-based MDTn and a management-based MDT depending on a method of selecting UE that will perform an MDT.
  • a network side selects UE that will perform an MDT by performing signaling to each UE and performs an MDT configuration so that the UE can perform the MDT.
  • the term ‘network side’ includes network elements necessary for the selection of MDT UE and an MDT configuration, such as an Operation, Administration, and Maintenance (OAM) server, a Mobility Management Entity (MME), and a Home Subscriber Server (HSS).
  • OAM Operation, Administration, and Maintenance
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • the network side may check whether UE is UE that has consented to the execution of an MDT based on user consent status information about the UE and select UE that will perform an MDT, from among UEs that have consented to the execution of an MDT. Furthermore, in a process of selecting UE that will perform the execution of an MDT, the capability, etc. of the UE may be taken into consideration.
  • the user consent status information is reserved by an OAM server, an MME, or an HSS and may be checked from information.
  • the network side selects the UE that will perform an MDT, from among UEs within a specific area or a specific cell, and performs an MDT configuration so that the selected UE can perform the MDT.
  • an MDT is performed within a specific area or a specific cell selected by the network side.
  • the network side transfers information about a user consent status to an eNB, and the eNB checks whether UE can perform an MDT so that the UE can perform the MDT.
  • FIG. 2 is a conceptual diagram schematically showing an example in which a network communication environment (i.e., wireless traffic quality or coverage or both) is measured using an MDT in a system to which the present invention is applied.
  • a network communication environment i.e., wireless traffic quality or coverage or both
  • a wireless communication environment and a coverage situation can be checked while minimizing the measurement of traffic quality performed within a cell through direct movement within the cell, based on information about communication quality in several positions within the cell where each UE performs measurement and reports the result of the measurement.
  • an area where UE can perform communication an area where it is difficult for UE to perform communication owing to the attenuation of a signal, an area where UE is unable to perform communication, and so on within a cell can be checked by utilizing values measured by UEs scattered in several areas.
  • a vehicle 110 for measurement has only to move along a minimum path 160 by utilizing a number of UEs 200 scattered within a cell.
  • measurement for a wireless environment is performed by a number of UEs at several places within the cell.
  • Each of the UEs may measure a wireless environment at a current position according to an MDT configuration.
  • the UE may continue to accumulate a log whenever the status of a wireless communication environment is measured and store the log as a new log form.
  • the UE may report, to an eNB, that the UE now has a log accumulated through the execution of an MDT.
  • the UE may transmit the log information to the eNB.
  • FIG. 3 is a flowchart schematically illustrating an example of an MDT configuration method in a system to which the present invention is applied.
  • an eNB configures an MDT configuration parameter at step S310.
  • the MDT configuration parameter may include the object of MDT measurement, the duration of MDT measurement, the period of MDT measurement, a method of reporting a log, a period during which a log is reported, the time of an eNB, and so on.
  • the MDT configuration parameter may further include a parameter related to a type of a triggering event.
  • an eNB may configure the object to be measured by UE through a parameter related to the object of MDT measurement.
  • the object of MDT measurement may be limited to the signal quality of a serving cell or may be configured to include even the intensity of a signal that is transmitted from an eNB within a neighbor cell according to circumstances.
  • An eNB may set a duration in which MDT measurement is performed and the period of MDT measurement performed during the duration through a parameter related to the duration and period of MDT measurement.
  • the MDT measurement may be set to be periodically performed during a specific duration at specific intervals or the MDT measurement may be set so that it is performed during a specific duration after a triggering event is generated and then finished.
  • An eNB may configure a method of transferring the result of MDT measurement from UE to a network through a parameter related to a method of reporting a log.
  • the UE may report the log information to the eNB.
  • the eNB may configure that how UE will process log information. For example, UE may be configured to report log information to an eNB or to periodically report log information to an eNB at specific intervals although there is no explicit request from the eNB after a lapse of specific period since MDT measurement is started.
  • An eNB may configure a period during which log information is reported through a parameter related to the report period of a log.
  • the eNB may perform an MDT for each of the objects of MDT measurement and differently configure the period during which log information is reported for every object.
  • an eNB may set the period during which log information is reported so that a log regarding some of the objects of MDT measurement is periodically reported and a log regarding some of the objects is reported only when there is an explicit request from the eNB.
  • An eNB may configure a reference time regarding an MDT measurement value through a parameter related to the time of the eNB.
  • the parameters regarding the MDT configuration may be configured in various ways depending on the optimization of a network in addition to the above parameters.
  • the existing MDT configuration parameters may be modified or cleared or new MDT configuration parameters may be added to the existing MDT configuration parameters.
  • An eNB transmits an MDT log configuration request message to UE at step S320.
  • the MDT log configuration request message may include information about an MDT configuration value that is stored in the UE.
  • the MDT log configuration request message may further include information necessary to perform MDT measurement.
  • the MDT log configuration request message may include an indicator to initiate MDT measurement.
  • the MDT log configuration message may be an indicator to initiate MDT measurement.
  • the MDT log configuration message may be configured based on an MDT configuration parameter.
  • the UE receives the MDT log configuration request message from the eNB and starts an MDT at step S330.
  • a configuration necessary to perform the MDT may be performed based on MDT configuration information included in the MDT log configuration request message.
  • the eNB requests an MDT log fetch from the UE at step S340.
  • the eNB may request the MDT log fetch from the UE in a predetermined period or may request the MDT log fetch from the UE in each period different from the MDT period of the UE. If an MDT log is aperiodically necessary, the eNB may request the MDT log fetch from the UE.
  • the UE that has received the MDT log fetch request from the eNB reports a written MDT log to the eNB at step S350.
  • the UE transfers the MDT log to the eNB only when the eNB requests an MDT log information report
  • the present invention is not limited to the example.
  • the UE may report the MDT log to the eNB although the eNB does not make an explicit MDT log fetch request depending on a predetermined condition.
  • an eNB configures an MDT configuration parameter
  • an entity placed over an eNB may configure an MDT configuration parameter, and the eNB may transmit an MDT log configuration request to UE based on the MDT configuration parameter.
  • FIG. 4 is a conceptual diagram schematically showing an example in which a log is configured in the periodic MDT in a system to which the present invention is applied.
  • UE measures a network communication environment at each of measurement time points T 1 to T 5 in an MDT measurement period T M during an MDT measurement duration T on .
  • the MDT measurement duration or the MDT measurement period or both are the configuration parameters of the periodic MDT and may be configured by an eNB or a network.
  • the MDT measurement period T M is set to be a multiple of a paging Discontinuous Reception (DRX) cycle T d .
  • DRX paging Discontinuous Reception
  • the DRX function corresponds to a Continuous Packet Connectivity (CPC) function supported in HSPA, etc.
  • CPC Continuous Packet Connectivity
  • UE monitors downlink control signaling in one subframe in each DRX cycle, but maintains a sleep mode in other subframes.
  • the DRX cycle may be utilized as one reference for configuring an MDT measurement period.
  • the UE measures a network communication environment based on the MDT configuration and writes a log based on measured information.
  • a log continues to be accumulated for every measurement and stored in the UE as a new log form.
  • a log number Log #1 according to a measurement time point may be indicated in the log in order to distinguish logs from each other, and the log may include a value for the measured wireless communication environment, a timestamp for the time when the wireless communication environment was measured, information about a position where the wireless communication environment was measured, and so on.
  • a log is illustrated to include a measurement value, a timestamp, and position information for a wireless communication environment, the log may include various pieces of information according to circumstances.
  • the event-triggered MDT may be used.
  • FIG. 5 is a flowchart schematically illustrating a method of configuring the event-triggered MDT in a system to which the present invention is applied.
  • Triggering events for MDT measurement may be various.
  • An eNB may select a necessary triggering event from the triggering events.
  • the update of position information by UE, a change in the status of a network measured by UE, a failure in a UE operation or an eNB operation, and so on may be taken into consideration as an event that may be used in the event-triggered MDT.
  • the eNB transmits an MDT log configuration request message to UE at step S520.
  • the MDT log configuration request message may include an event-triggered MDT configuration message.
  • the MDT log configuration request message may further include information necessary to perform MDT measurement.
  • the MDT log configuration request message may further include an indicator that enables event-triggered MDT measurement to be started.
  • the MDT log configuration request message may be an indicator that enables event-triggered MDT measurement to be started.
  • the event-triggered MDT configuration parameter may be included in a message different from the MDT log configuration message and be then transmitted to UE, or a message including only the event-triggered MDT configuration parameter may be configured and then transmitted to the UE.
  • an eNB may separately inform the UE of information about the transmission according to circumstances.
  • the UE receives the MDT log configuration request message from the eNB and starts an MDT at step S530.
  • the MDT log configuration request message includes a parameter related to the event-triggered MDT configuration, and the UE may configure an MDT log environment based on the parameter related to the event-triggered MDT configuration.
  • UE may report an MDT log to an eNB after a lapse of some time since the UE performs MDT measurement although the eNB does not make an explicit MDT log fetch request depending on a predetermined condition.
  • FIG. 6 is a conceptual diagram schematically showing an example in which a log is written in a mixed method of the periodic method and the event-triggered method in a system to which the present invention is applied.
  • UE may measure a network communication environment based on a periodic MDT configuration at each of measurement time points T 1 to T 5 in an MDT measurement period T M during an MDT measurement duration T on .
  • a duration in which MDT measurement is periodically performed or a period during which the MDT measurement is performed may be configured in the form of a periodic MDT configuration parameter.
  • the duration in which MDT measurement is periodically performed or the period during which the MDT measurement is performed may be configured in various ways according to circumstances.
  • the measurement period T M of the periodic MDT is set to a multiple of the paging DRX cycle T d .
  • the UE may measure a network communication environment, etc. based on a periodic MDT configuration and may write a log (i.e., measurement information).
  • a log continues to be accumulated whenever measurement is performed and then stored in the UE as a new log form.
  • the log may include a value for the measured wireless communication environment, a timestamp for the time when the wireless communication environment was measured, information about a position where the wireless communication environment was measured, etc. along with a log number Log #1 for distinguishing logs when measurement was performed from each other.
  • a log is illustrated to include a measurement value, a timestamp, and position information for a wireless communication environment has been described, but the present invention is not limited to the example.
  • the log may include various pieces of information according to circumstances.
  • UE may measure a network communication environment based on an event-triggered MDT configuration and may write a log for the measured network communication environment.
  • the log may be differently configured according to types of triggering events.
  • a log for an event-triggered MDT may include the position information about the UE and a timestamp when a network communication environment was measured, as shown in FIG. 6.
  • UE may write, store, manage, and report the log for the periodic MDT and the log for the event-triggered MDT based on different configurations. Furthermore, UE may write, store, manage, and report the log for the periodic MDT and the log for the event-triggered MDT based on some or all of configurations according to circumstances.
  • UE may report log information to the network.
  • UE may report log information to the network.
  • UE may report log information to the network.
  • UE may report log information to the network.
  • UE may report log information to the network.
  • UE is operated with limited resources (e.g., limited battery and memory). If power available for UE is insufficient, the execution of an MDT may cause a problem in the operation of UE. In particular, in the LMDT, battery consumption must be minimized in order for UE in the RRC_IDLE mode to be operated for a necessary wait time. Furthermore, in a situation where the memory of UE is insufficient, it may be necessary to minimize the usage of memory so that memory shortage is not caused owing to logs accumulated in an MDT execution process.
  • limited resources e.g., limited battery and memory.
  • UE that has consented to the execution of an MDT may revoke consent the execution of an MDT.
  • the specific UE has to previously inform a network side, selecting UE that will perform the MDT, that the specific UE can perform the MDT through a process of consenting to the execution of the MDT.
  • UE may perform a higher procedure, such as subscription, and a network side may obtain information about whether the UE is UE that may participate in an MDT based on the subscription.
  • the information about subscription may be managed by the network side (e.g., a Home Subscriber Server (HSS) or other core network nodes).
  • HSS Home Subscriber Server
  • the network side transfers information about whether specific UE has consent to the execution of the MDT from the network node, such as an OAM server, an MME, or an HSS, to an eNB.
  • the network node such as an OAM server, an MME, or an HSS
  • the user consent information about the execution of the MDT by the UE may be transferred in various ways from the network side to the eNB.
  • the information about consent to the execution of the MDT by the UE may be transferred from the network side to the eNB based on a Subscriber Profile ID (hereinafter referred to as an ‘SPID’) for Radio Access Technology (RAT)/Frequency Selection Priority (FSP).
  • SPID Subscriber Profile ID
  • the SPID Information Element (IE) for RAT/FSP is used to define a camp characteristic in the IDLE mode and to control inter-RAT/inter-frequency handover in an active mode.
  • the SPID IE may be included in an initial context setup request message and transferred from a network side to an eNB.
  • ‘User consent to the execution of an MDT’ is hereinafter simply referred to as ‘user consent’, for convenience of description.
  • FIG. 7 is a flowchart schematically illustrating an example in which user consent information by UE is transmitted between an eNB and an MME.
  • FIG. 7 shows an example of a method in which information about the user consent of UE is transferred from the MME to the eNB.
  • the information about the user consent of the UE may be included in an initial context setup request message and transferred from the MME to the eNB.
  • the MME transmits the initial context setup message to the eNB at step S710.
  • the initial context setup message may include a trace activation IE, a handover restriction list IE which may include information about roaming, an area, or access restriction, a UE radio capability IE, an SPID IE, a CS fallback indicator IE, and so on.
  • the information about the user consent of the UE is included in the SPID IE and transmitted.
  • the SPID ID is information or IE that may be transmitted from a network side, an MME, an HSS, or an OAM server to an eNB.
  • the transmitted SPID may be configured as in Table 1.
  • the SPID is mandatory (M) information, and it indicates a profile corresponding to a written integer.
  • the SPID may index user information through handover or Initial Direct Transfer (IDT) when UE newly accesses a core network.
  • IDTT Initial Direct Transfer
  • the SPID may index information, such as a mobility profile or a service usage profile.
  • the SPID may index a profile, including relevant information, through an indicated value (i.e., integer).
  • An eNB may obtain necessary information by checking a profile indexed by the received SPID. Accordingly, an MME may transfer information about the user consent of UE to the eNB so that the SPID can index a profile including information about the user consent of the UE. The eNB may check that the UE performs an MDT by checking that a user consent status is 'consent' in the profile of MDT-related information indexed by the SPID.
  • a network side may transfer the information about user consent, obtained from the UE, to the eNB through a message in which UE-specific information is transmitted within a scope of the technical spirit of the present invention.
  • the user consent revocation of UE is described below.
  • UE may no longer perform an MDT or may not initiate the execution of the MDT, although the UE has consent to the execution of the MDT. For example, the remaining battery power of UE is insufficient to perform an MDT, or the available memory of UE is insufficient owing to an MDT log written according to the execution of the MDT.
  • the UE performs a user consent revocation procedure.
  • the user consent revocation procedure includes a series of operations in which UE revokes consent to the execution of an MDT and stops performing the MDT or does not start performing the MDT.
  • a case in which UE revokes user consent may be divided into a case in which the UE is now performing an MDT and a case before the UE performs the MDT according to the state in which the MDT is performed.
  • a cause that the UE revokes user consent and stops performing the MDT when the UE now performs the MDT may be various.
  • a representative case may include a case in which the available memory of the UE is a specific level or less and a case in which the remaining battery amount of the UE is a specific level or less.
  • the UE In case of available memory, in order for UE to be normally operated, the UE must have available memory of a specific level or higher. If available memory is reduced to a specific level or less owing to an MDT log written by the execution of an MDT, it is necessary to stop performing the MDT or to transmit or clear MDT logs, making the available memory insufficient, with consideration taken of memory having the least level necessary to perform a normal operation.
  • UE needs to maintain the remaining battery power of a specific level for a normal operation.
  • the battery must be maintained for a long time. Accordingly, if it is difficult for UE to maintain the remaining battery power of a level necessary for a normal operation, the UE has to stop performing an MDT and reduce power consumption.
  • the UE may check available memory and the remaining battery amount and then determine that it will be better not to perform the MDT in order for the UE to be normally operation. In this case, the UE may need to reduce power consumption and revoke the user consent in order to maintain available memory.
  • the UE may compare current available memory with a predetermined reference value M threshold . If the available memory is smaller than the predetermined reference value, the UE may determine to revoke the user consent. In this case, the UE may perform a user consent revocation procedure in order to stop performing the MDT or may not start performing the MDT.
  • the UE may compare the remaining battery amount with a predetermined reference value B threshold . If the remaining battery amount is smaller than the predetermined reference value, the UE may determine to revoke the user consent. In this case, the UE may perform a user consent revocation procedure in order to stop performing the MDT or may not start performing the MDT
  • the user consent revocation procedure includes that a higher protocol or application, such as a Non Access Stratum (NAS) layer), revokes UE consent to the execution of an MDT. More specifically, a higher protocol or application, such as an NAS layer, may instruct that an MDT-related procedure, regarding UE that has revoked user consent, through an Access Stratum (AS) layer protocol.
  • NAS Non Access Stratum
  • AS Access Stratum
  • the user consent revocation procedure includes an operation of UE transferring a message, indicating that user consent to the execution of an MDT is revoked, to a network side (e.g., an MME, an HSS, an OAM server, an eNB, or a network node such as an NB).
  • a network side e.g., an MME, an HSS, an OAM server, an eNB, or a network node such as an NB.
  • the network side may update user consent status information about the UE from 'user consent' to 'user non-consent'.
  • FIG. 8 is a flowchart schematically illustrating a user consent revocation procedure by UE in a system to which the present invention is applied.
  • the UE transmits a user consent revocation message to a network at step S810.
  • the network may be an MME, an OAM server, or an HSS.
  • the user consent revocation message is the message of an NAS layer or an application layer. Accordingly, an eNB capable of checking only an Access Stratum (AS) message simply transfers the user consent revocation message to the network side. That is, the user consent revocation procedure is performed in the NAS protocol or application of UE, and it does not influence the operation of an AS in such as way as to directly change a configuration for the execution of an MDT by the UE between the UE and the eNB.
  • AS Access Stratum
  • the user consent revocation message transmitted by the UE may include the UE ID, the MDT consent revocation indicator, etc. of the UE.
  • the network updates user consent status information about the MDT of the UE at step S820.
  • the network may update the user consent status information about the UE that has transmitted the user consent revocation message from a 'user consent' state to a 'user non-consent' state.
  • the network transmits the changed user consent status information to the eNB as will be described later. For example, as described above, if the user consent status information is transmitted to the eNB through an SPID, the network may configure the SPID so that an index of the SPID is mapped to a profile regarding user consent status information ‘user non-consent'.
  • a profile regarding user consent status information ‘user consent' is mapped when an index value indicated by the SPID is 1 and a profile regarding user consent status information ‘user non-consent' is mapped when an index value indicated by the SPID is 2.
  • the network may change the index value of the SPID regarding the user consent status information of the UE from 1 to 2. Accordingly, the eNB that has received the SPID checks necessary information in the profile regarding user consent status information ‘user non-consent' mapped in the index value 2, as will be described later.
  • the network may configure the profile regarding user consent status information ‘user non-consent' so that the profile includes information necessary for the eNB to revoke the MDT procedure regarding the UE, such as the UE ID, the MDT consent revocation indicator, etc. of the UE that has transmitted the user consent revocation message.
  • the network transmits the updated user consent status information about the UE that has transmitted the user consent revocation message to the eNB at step S830.
  • the updated user consent status information may be included in the user consent status information message and then transmitted.
  • the user consent status information message transmitted from the network to the eNB may be an initial context setup request message, as described above.
  • the user consent status information message may be a message through which an updated user consent status is transferred to the eNB or may be a message through which only information indicating that a user consent status has changed is transferred to the eNB.
  • the network may configure a profile mapped to the changed user consent status and transmit the configured profile along with the SPID. For example, it is assumed that a profile regarding user consent status information ‘user consent' is mapped when an index value indicated by the SPID is 1 and a profile regarding user consent status information ‘user non-consent' is mapped when an index value indicated by the SPID is 2.
  • the network may transmit the SPID in which the index value of the user consent status information about the UE is 2 and the profile regarding user consent status information ‘user non-consent’ at the same time.
  • the profile regarding user consent status information includes information necessary for the eNB to perform a procedure related to an MDT based on the user consent status of UE (i.e., user consent or user non-consent).
  • the eNB In response to the user consent status information message, the eNB updates the user consent status information about the UE at step S840.
  • the eNB that has received the user consent status information message from the network changes the existing user consent status information based on the user consent status information of the UE included in the user consent status information message.
  • the eNB changes a current user consent status into the other user consent status. For example, regarding UE that has transmitted a user consent revocation message to a network, the user consent status of the UE, now owned by an eNB, will be 'user consent'. Accordingly, the eNB changes the user consent status of the UE into 'user non-consent'.
  • the eNB may check a profile matched with an index regarding the user consent status information of the SPID and update the user consent status information based on the checked profile information. For example, it is assumed that a profile regarding user consent status information ‘user consent’ is mapped when an index value indicated by the SPID is 1 and a profile regarding user consent status information ‘user non-consent’ is mapped when an index value indicated by the SPID is 2. If the index value of the SPID transmitted by the network is 2, the eNB may obtain the user consent status information ‘user non-consent’ about UE by checking the mapped profiled. The eNB may change the user consent status of the UE into 'user non-consent' based on the obtained user consent status information.
  • an eNB may determine whether to change a user consent status based on only the index value of an SPID and change the user consent status of UE according to a predetermined rule.
  • a method of checking a reason of the revocation and utilizing the reason may be taken into consideration. For example, if UE transmits a user consent revocation message, together with a user consent revocation reason, to a network, the network may take additional measures based on the user consent revocation reason. For example, in the case in which a user consent revocation reason is memory shortage, when UE transmits a user consent revocation message together with the reason or transmits the user consent revocation message, including the reason, to a network, the network may check the user consent revocation reason (i.e., memory shortage) and take necessary measures against an MDT log that causes the memory shortage of the UE.
  • a user consent revocation reason i.e., memory shortage
  • FIG. 9 is a flowchart schematically illustrating an embodiment in which a user consent revocation procedure is performed by taking a user consent revocation reason into consideration in a system to which the present invention is applied.
  • An example in which the user consent revocation reason is memory shortage is described with reference to FIG. 9, for convenience of description.
  • the user consent revocation procedure in the UE may be started in a higher layer (e.g., an NAS or application).
  • the NAS or application does not influence an AS layer.
  • the NAS or application implemented in one UE may inform the AS layer of the MDT user consent revocation situation of a higher layer and request the AS layer to stop the MDT-related operation. For example, UE that has checked a problem in the battery or memory may request an AS layer implemented therein to stop the MDT-related operation.
  • the UE may continue to perform the MDT-related operation during the time configured in relation to the MDT.
  • a network may know that the UE has revoked user consent based on a user consent revocation message and that the UE continues to perform the MDT-related operation based on the MDT-related configuration set in the UE.
  • the network may transmit a message, instructing that the MDT-related operation be stopped, to the UE.
  • the user consent revocation message may include the UE ID, the MDT consent revocation indicator, etc. of the UE.
  • a reason of user consent revocation may include memory shortage, battery shortage, etc.
  • a cause value corresponding to the user consent revocation reason may be previously determined between UE and a network and between the UE and an eNB. Accordingly, the UE may inform the network and the eNB that what is a reason of user consent revocation by transmitting a relevant cause value to the network.
  • the UE may transmit a user consent revocation message or a cause value for a reason of user consent revocation, including information indicating that there is an MDT log written by performing an MDT, to the network.
  • the network In response to the user consent revocation message received from the UE, the network updates user consent status information about the UE at step S920. Unlike in FIG. 8, the network also receives the user consent revocation reason (i.e., a cause value) from the UE.
  • the user consent revocation reason i.e., a cause value
  • the MDT log may be removed from the memory. If not, it is necessary to take measures in order to remove the MDT log from the memory of the UE by transmitting or clearing the MDT log.
  • the network transmits an instruction for taking necessary measures based on the user consent revocation reason, together with updated user consent status information about the UE that has transmitted the user consent revocation message, to an eNB at step S930.
  • the updated user consent status information may be included in the user consent status information message and then transmitted.
  • the user consent status information message transmitted from the network to the eNB, as described above, may be an initial context setup request message.
  • the network may transmit the user consent status information through an SPID.
  • the network may transmit an MDT log fetch instruction to the eNB so that the eNB reports MDT log information to the UE as relevant measures.
  • the MDT log fetch instruction may be included in the user consent status information message and then transmitted to the eNB.
  • the eNB may change the user consent status of the UE at step S940.
  • the eNB may change a current user consent status to the other user consent status. For example, regarding UE that has transmitted a user consent revocation message to a network, the user consent status of the UE, now owned by an eNB, will be 'user consent'. Accordingly, the eNB changes the user consent status of the UE into 'user non-consent'.
  • the eNB may check a profile mapped to an index regarding the user consent status information of the SPID and update the user consent status information based on the checked profile information. For this, the eNB may determine whether the user consent status has changed based on only the index value of the SPID and may change the user consent status of the UE according to a predetermined rule.
  • the eNB may transmit an MDT log fetch request message to the UE that has transmitted the user consent revocation message at step S950.
  • the MDT log fetch request message transmitted by the eNB may be a message UEInformationRequest that requests information about the UE.
  • the eNB is informed that the eNB does not need to report an MDT log for a predetermined MDT log duration and may use a log after the log duration is finished (i.e., log available indication).
  • the UE reports the MDT log.
  • the UE may transmit the user consent revocation message to the network, but may no longer perform the MDT-related operation. Accordingly, if necessary measures (e.g., the MDT log fetch request) do not exist, the UE may store the MDT log in the memory for a specific time (e.g., 48 hours) (unless the UE is switched off or the written MDT log). This is not a preferred one in the management of memory, in particular, the UE having insufficient available memory.
  • necessary measures e.g., the MDT log fetch request
  • the UE may store the MDT log in the memory for a specific time (e.g., 48 hours) (unless the UE is switched off or the written MDT log). This is not a preferred one in the management of memory, in particular, the UE having insufficient available memory.
  • the UE In response to the MDT log fetch request message, the UE writes an MDT log, stores the MDT log in the memory, and reports the MDT log to the eNB using an MDT log report message at step S960.
  • the MDT log report message transmitted from the UE to the eNB is a response message UEInformationResponse to the message UEInformationRequest.
  • the UE may clear the MDT log from the memory because it has reported the stored MDT log to the eNB.
  • a network and an eNB may request or instruct UE to clear an MDT log so that the UE can solve memory shortage without requesting the UE to perform MDT log fetch.
  • FIG. 10 is a flowchart schematically illustrating another embodiment in which a user consent revocation procedure is performed by taking a user consent revocation reason into consideration in a system to which the present invention is applied.
  • An example in which a user consent revocation reason is memory shortage is described with reference to FIG. 10, for convenience of description.
  • FIG. 10 the same contents as those of FIG. 9 will be simply described or a description thereof will be omitted, for convenience of description.
  • UE transmits a user consent revocation message to a network at step S1010.
  • the UE transmits the user consent revocation message together with a user consent revocation reason.
  • the user consent revocation message may include information about the user consent revocation reason.
  • the UE After transmitting the user consent revocation message to the network, the UE by itself may take necessary measures according to the user consent revocation reason. If the user consent revocation reason is memory shortage, the UE may clear MDT log stored in its memory at step S1020. The UE can additionally secure available memory by clearing the MDT log without waiting for a detailed instruction or request from the network and an eNB.
  • the necessary measures taken by the UE may be previously determined between the UE and the network/eNB. If the necessary measures taken by the UE may be previously determined between the UE and the network/eNB, whether the UE will wait for an instruction or request from the network/eNB or whether the UE by itself will take necessary measures may be determined according to a user consent revocation reason.
  • the network updates user consent status information about the UE at step S1030.
  • the network may determine that the UE by itself may take necessary measures based on the user consent revocation reason received from the UE at step S1010. For example, the network may determine that the user consent revocation reason received from the UE is memory shortage and that the UE may clear the stored MDT log in order to solve memory shortage.
  • the network transmits the updated user consent status information message for the UE that has transmitted the user consent revocation message to the eNB at step S1040.
  • the network does not need to transmit necessary measures (e.g., an MDT log fetch instruction) to the eNB because the network determines that the UE by itself will take necessary measures.
  • the eNB may change user consent status information about the UE at step S1050.
  • FIG. 11 is a flowchart schematically illustrating yet another embodiment in which a user consent revocation procedure is performed by taking a user consent revocation reason into consideration when UE performs handover in a system to which the present invention is applied.
  • An example in which a user consent revocation reason is memory shortage is described with reference to FIG. 11, for convenience of description.
  • FIG. 11 the same contents as those of FIGS. 9 and 10 will be simply described or a description thereof will be omitted, for convenience of description.
  • the UE transmits a user consent revocation message to a network at step S1110. At this time, the UE transmits the user consent revocation message together with a user consent revocation reason.
  • the user consent revocation message may include information about the user consent revocation reason.
  • the network In response to the user consent revocation message received from the UE, the network updates user consent status information about the UE at step S1120. The network also receives the user consent revocation reason from the UE.
  • the UE moves from a Source eNB (hereinafter referred to as an ‘SeNB’) to a Target eNB (hereinafter referred to as an ‘TeNB’) in the IDLE mode and then accesses the network in the CONNECTED mode.
  • the UE accesses the TeNB.
  • the network transmits the user consent status information about the UE to the TeNB at step S1130.
  • the network transmits an MDT log fetch instruction to the TeNB.
  • the TeNB transmits an MDT log fetch request message to the UE, as will be described later.
  • the network may also transmit the user consent status information to the SeNB at step S1140. Although the UE has performed handover from the SeNB to the TeNB when the user consent status information is transmitted, the user consent status information about the UE is shared by the SeNB and the TeNB. Accordingly, the user consent status information may be subsequently used. Furthermore, the network may also transmit the MDT log fetch instruction to the SeNB. In response to the MDT log fetch instruction, the SeNB may determine that the UE writes an MDT log by performing an MDT within the cell of the SeNB and reports the MDT log to the TeNB and the TeNB will have the MDT log.
  • the TeNB may change the user consent status information about the UE at step S1150.
  • the SeNB may change the user consent status information about the UE at step S1160. Accordingly, the SeNB can update the user consent status information about the UE into the latest information and subsequently utilize the latest information.
  • the TeNB may transmit the MDT log fetch request message to the UE that has transmitted the user consent revocation message at step S1170.
  • the MDT log fetch request message transmitted by the TeNB may be a message UEInformationRequest that requests information about the UE as described above.
  • the UE In response to the MDT log fetch request message, the UE writes an MDT log within the cell of the SeNB, stores the MDT log in memory, and reports the MDT log to the TeNB at step S1180.
  • the MDT log report message transmitted from the UE to the TeNB may be a message UEInformationResponse as described above.
  • the UE may clear the MDT log from the memory by reporting the stored MDT log to the TeNB.
  • the present invention may also be applied to an example in which UE by itself takes necessary measures and at this time, the UE performs handover.
  • the UE may transmit the user consent revocation message to the network and take necessary measures (e.g., clearing an MDT log stored in the memory), as described above with reference to FIG. 10, without the step S1170 of the TeNB sending the log fetch request message and the step S1180 of the UE reporting the MDT log. Accordingly, the network does not need to transmit the MDT log fetch instruction to each of the SeNB and the TeNB.
  • the user consent status information may be transmitted to the SeNB so that the SeNB can update the user consent status information. If the user consent status information does not need to be updated, the user consent status information may not be transmitted to the SeNB. If the user consent status information needs to be updated (e.g., the UE may return back to the SeNB or it is expected that the updated of the user consent status information about the UE is not easy from another network), the step S1140 of sending the user consent status information so that the user consent status information can be updated may be preferably performed.
  • FIG. 12 is a flowchart schematically illustrating a user consent revocation procedure performed by UE in a system to which the present invention is applied.
  • the UE that has consented to the execution of an MDT determines whether to stop performing the MDT or not to start performing the MDT at step S1210.
  • the UE determines whether a situation in which the MDT cannot be performed has occurred and stops performing the MDT or does not start performing the MDT according to a result of the determination.
  • the UE may stop the MDT or may determine not to start the MDT (hereinafter referred to as an ‘MDT stop decision').
  • MDT stop decision' the UE compares current available memory with predetermined reference memory M threshold . If, as a result of the comparison, the current available memory is smaller than the predetermined reference memory, the UE may make an MDT stop decision.
  • the UE may compare the remaining battery amount with a predetermined reference battery amount B threshold . If, as a result of the comparison, the remaining battery amount is smaller than the reference battery amount, the UE may make an MDT stop decision.
  • the UE transmits a user consent revocation message to a network at step S1220.
  • the UE transmits a user consent revocation reason together with the user consent revocation message.
  • the user consent revocation reason may be included in the user consent revocation message and then transmitted.
  • the user consent revocation message is the NAS protocol or application message of the UE.
  • An eNB simply transfers the user consent revocation message to a network side.
  • the network to which the user consent revocation message is transmitted may be an MME, an OAM server, or an HSS.
  • the UE may determine whether it needs a processing instruction or request from the network/eNB at step S1230. Whether the processing instruction or request from the network/eNB is necessary might have been previously determined between the UE and the network/eNB or might have been previously determined according to a user consent revocation reason.
  • the UE may take necessary measures. For example, if available memory is insufficient, the UE may clear MDT logs stored in its memory at step S1240.
  • the UE receives an instruction or request for taking necessary measures from the eNB. For example, if the user consent revocation reason is available memory shortage, the UE may receive an MDT log fetch request message from the eNB at step S1250.
  • the UE takes measures based on the instruction or request received from the eNB. For example, in response to the MDT log fetch request message received from the eNB, the UE may write an MDT log by performing an MDT, store the MDT log in the memory, and report the MDT log to the eNB at step S1260. The UE that has reported the MDT log may further secure available memory by deleting the MDT log from the memory.
  • FIG. 13 is a flowchart schematically illustrating a user consent revocation procedure performed by a network in a system to which the present invention is applied.
  • the network receives a user consent revocation message from UE at step S1310.
  • the network receives a user consent revocation reason together with the user consent revocation message.
  • the user consent revocation reason may be included in the user consent revocation message.
  • the network updates user consent status information about the UE at step S1320. Accordingly, the user consent status information of the UE is changed from 'user consent' to 'user non-consent'.
  • the network may determine whether the UE by itself takes necessary measures related to the user consent revocation reason at step S1330.
  • the necessary measures related to the user consent revocation reason are measures for solving the user consent revocation reason (i.e., a cause of a problem in the normal operation of the UE (i.e., a reason of MDT stop decision) to the utmost. For example, if the user consent revocation reason is memory shortage, the necessary measures may be an operation of deleting MDT logs stored in the memory of the UE.
  • Whether the UE by itself will take the necessary measures might have been previously determined between the UE and the network/eNB. Whether the UE by itself will take the necessary measures might have been collectively determined for all user consent revocation reasons. In some embodiments, whether the UE by itself will take the necessary measures might have been determined for every user consent revocation reason. In this case, the network may determine whether the UE by itself will take the necessary measures based on the user consent revocation reason.
  • the network determines that the UE by itself will take the necessary measures, the network transmits the updated user consent status information about the UE to the eNB at step S1340. At this time, the network may transmit the user consent revocation reason of the UE, together with the updated user consent status information, to the eNB.
  • the updated user consent status information may be included in a user consent status information message and then transmitted.
  • the user consent status information message transmitted from the network to the eNB, as described above, may be an initial context setup request message.
  • the user consent status information message may include the updated user consent status information by itself or may include only information indicating that the user consent status has changed.
  • the updated user consent status information may be transferred through an SPID.
  • the network may configure a profile mapped to the changed user consent status and transmit the configured profile together with the SPID.
  • the network may configure the SPID so that the index of the SPID is mapped to a profile regarding user consent status information ‘user non-consent’.
  • the network may configure the profile regarding user consent status information ‘user non-consent’ so that information necessary for the eNB to stop an MDT procedure, such as the UE ID, the MDT consent revocation indicator, etc. of the UE that has transmitted the user consent revocation message, is included in the profile regarding user consent status information ‘user non-consent’.
  • the network may transmit an instruction/request regarding the necessary measures, in addition to the user consent status information message, to the eNB at step S1350.
  • the network may also transmit the user consent revocation reason of the UE, together with the user consent status information message, to the eNB.
  • the necessary measures may be different according to a user consent revocation reason as described above. If the user consent revocation reason is memory shortage, the network may transmit an MDT log fetch instruction to the eNB as the necessary measures (e.g., so that an MDT log is reported). If the network determines that the MDT log has only to be cleared without the MDT log report as described above, the network may instruct or request the eNB so the UE immediately clears the MDT log.
  • FIG. 14 is a flowchart schematically illustrating a user consent revocation procedure performed by an eNB in a system to which the present invention is applied.
  • the eNB receives a user consent status information message for UE from a network at step S1410.
  • the network may be an MME, an OAM server, or an HSS may be.
  • the user consent status information message transmitted from the network to the eNB may be an initial context setup request message.
  • the user consent status information message may include only updated user consent status information by itself and may include only information indicating that a user consent status has changed.
  • the updated user consent status information may be transferred through an SPID included in the context setup request message.
  • the index of the SPID may be mapped to a profile regarding user consent status information ‘user non-consent’.
  • the profile to which the index of the SPID is mapped may include information that is necessary for the eNB to stop an MDT procedure regarding the UE, such as the UE ID, the MDT consent revocation indicator, etc. of the UE that has transmitted the user consent revocation message.
  • the eNB updates user consent status information about the UE based on the received user consent status information at step S1420. Accordingly, the user consent status information of the UE that has transmitted the user consent revocation message may be changed from 'user consent' to 'user non-consent'.
  • the eNB determines whether an MDT log fetch instruction is included in the received user consent status information message or the MDT log fetch instruction, together with the user consent status information message, has been received at step S1430.
  • the MDT log fetch instruction instructs the UE to transmit an MDT log that is written and stored in the UE.
  • the procedure in the eNB is finished at S1420 of updating the user consent status information of the UE.
  • the eNB receives an MDT log report message including an MDT log report written by the UE and stored in the memory of the UE at step S1450.
  • the MDT log report message transmitted from the UE to the eNB is a response UEInformationResponse to the message UEInformationRequest.
  • the UE may clear the MDT log stored in the memory by reporting the stored MDT log to the eNB.
  • MDT log fetch is requested as an example of necessary measures when a user consent revocation reason is memory shortage.
  • the UE may be instructed or requested to clear the MDT log instead of requesting the UE to perform MDT log fetch so that the UE solves memory shortage.
  • the eNB may change the user consent status information of the UE regarding the execution of an MDT based on the received user consent status information, check the user consent revocation reason (i.e., a cause value), and transmit the measures against memory shortage (i.e., an MDT log fetch request or an instruction to clear an MDT log) to the UE.
  • the user consent revocation reason i.e., a cause value
  • the measures against memory shortage i.e., an MDT log fetch request or an instruction to clear an MDT log
  • the measures taken by the UE by itself might have been previously determined between the UE and the eNB/the network. If the measures taken by the UE by itself might have been previously determined between the UE and the eNB/the network, the network does not need to transmit the user consent revocation reason (i.e., a cause value) to the eNB, and the eNB may change only the user consent status information of the UE without taking the necessary measures according to a predetermined rule or change only the user consent status information of the UE by checking that the user consent revocation reason (i.e., a cause value) has not received from the network.
  • the user consent revocation reason i.e., a cause value
  • the network may check the user consent revocation reason (i.e., a cause value) transmitted by the UE and may transmit an instruction necessary for the eNB or the user consent revocation reason (i.e., a cause value) only when the UE by itself does not take the measures as a result of the check.
  • the eNB may check whether the instruction or the user consent revocation reason (i.e., a cause value) has been received from the network and transmit an instruction/request, corresponding to the instruction, or an instruction/request, corresponding to the user consent revocation reason (i.e., a cause value), to the UE.
  • FIG. 15 is a block diagram schematically illustrating the construction of each of the subjects of operations in a system to which the present invention is applied.
  • the UE 1500 includes a transceiver 1505, memory 1510, and a controller 1515.
  • the UE 1500 transmits and receives necessary information through the transceiver 1505.
  • the transceiver 1505 may transmit an MDT log, a user consent revocation message regarding the execution of an MDT, etc. to an eNB/network.
  • the memory 1510 may store configuration information necessary to perform an MDT, an MDT log written by performing the MDT, predetermined reference values M threshold , B threshold necessary to make an MDT stop decision, and so on.
  • the controller 1515 is connected to the transceiver 1505 and the memory 1510 and is configured to control the transceiver 1505 and the memory 1510.
  • the controller 1515 of the UE 1510 controls the above procedures of the present invention so that the procedures are performed.
  • the controller 1515 may perform an MDT based on an MDT configuration, write an MDT log, and transmit the MDT log through the transceiver 1505.
  • the controller 1515 may make an MDT stop decision.
  • the controller 1515 may determine whether to stop performing an MDT by comparing the available memory and the remaining battery amount of the UE with respective predetermined reference values.
  • the controller 1515 may directly transmit a user consent revocation message regarding the execution of the MDT to a network through the transceiver 1505 or may transmit the user consent revocation message to the network through an eNB.
  • the controller 1515 may take necessary measures in order to solve a problem that has caused a user consent revocation reason (e.g., memory shortage or battery shortage) according to an instruction or request from a network 1560 or an eNB 1530 or both.
  • the controller 1515 may determine that the UE 1500 by itself will take necessary measures according to a predetermined rule. In this case, the controller 1515 may take the necessary measures without waiting for the instruction or request from the network 1560 or the eNB 1530 or both.
  • the eNB 1530 includes a transceiver 1535, memory 1540, and a controller 1545.
  • the eNB 1530 may transmit and receive information to and from the UE 1500 or the network 1560 or both through the transceiver 1535.
  • the transceiver 1535 transfers a user consent revocation message regarding the execution of an MDT, received from the UE 1500, to the network 1560.
  • the memory 1540 may store a configuration for the execution of an MDT, an MDT log received from UE, user consent status information about the execution of an MDT for each UE, and so on.
  • the controller 1545 is connected to the transceiver 1535 and the memory 1540 and is configured to control the transceiver 1535 and the memory 1540.
  • the controller 1545 may change user consent status information about the UE 1500 based on user consent status information received from the network 1560. Furthermore, the controller 1545 may transfer an instruction or request necessary to perform a procedure, required by the UE 1500, to the UE 1500 through the transceiver 1535 according to circumstances or according to an instruction of the network 1560.
  • the network 1560 includes a transceiver 1565, memory 1570, and a controller 1575.
  • the network 1560 may be an MME, an OAM server, or an HSS.
  • a 'network node' i.e., an MME, an OAM server, or an HSS
  • the network 1560 may transmit and receive necessary information through the transceiver 1565.
  • the transceiver 1565 may receive a user consent revocation message regarding the execution of an MDT by the UE 1500.
  • the transceiver 1565 may transmit information messages necessary for a user consent revocation procedure regarding the execution of an MDT.
  • the memory 1570 may store pieces of information about eNBs and UEs connected to the network 1560. For example, the memory 1570 may store user consent status information regarding the execution of an MDT for every UE.
  • the controller 1575 is connected to the transceiver 1565 and the memory 1570 and is configured to control the transceiver 1565 and the memory 1570.
  • the controller 1575 may change user consent status information about the UE 1500 in response to a user consent revocation message regarding the execution of an MDT, received from the UE 1500.
  • the controller 1575 may determine what necessary measures are necessary for the UE 1500 based on a user consent revocation reason received from the UE 1500.
  • the controller 1575 may configure a message in order to transfer information, changed according to the user consent revocation of the UE 1500, to the eNB 1530 and transmit the configured message to the eNB 1530 through the transceiver 1565. Furthermore, if the controller 1575 determines that necessary measures need to be taken by the UE 1500, the controller 1575 may configure an instruction to be transmitted to the eNB 1560 so that the UE 1500 may take the necessary measures and transmit the configured instruction to the eNB 1560 through the transceiver 1565.
  • the system to which the present invention is applied has been illustrated to be composed of one UE, one eNB, and one network node, but this is for convenience of description.
  • a plurality of UEs and a plurality of eNBs may exist for one network node.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)

Abstract

La présente invention porte sur un procédé de révocation d'un consentement d'un utilisateur à une réduction au minimum des tests de mesure de qualité de service (MDT) et sur un appareil l'utilisant. Le procédé consiste, s'il est déterminé qu'un consentement d'un utilisateur à une MDT doit être révoqué, à transmettre un message de révocation de consentement d'utilisateur et des informations concernant une raison de la révocation du consentement de l'utilisateur à un réseau et à arrêter d'effectuer la MDT ; et à recevoir un message de requête d'extraction de journal MDT ou un message d'instruction d'effacement de journal MDT en provenance d'un nœud B évolué (eNB). En outre, lorsque le message de requête d'extraction de journal MDT est reçu, un équipement utilisateur (UE) transmet un journal MDT, stocké en mémoire, à l'eNB et efface le journal MDT stocké, et lorsque le message d'instruction d'effacement de journal MDT est reçu, l'UE efface le journal MDT stocké.
PCT/KR2012/002439 2011-04-02 2012-04-02 Appareil et procédé pour effectuer une révocation de consentement d'utilisateur à une réduction au minimum des tests de mesure de qualité de service en communication sans fil Ceased WO2012138083A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020110030441A KR20120111837A (ko) 2011-04-02 2011-04-02 운전 시험 최소화에 대한 사용자 동의 취소 장치 및 방법
KR10-2011-0030441 2011-04-02

Publications (2)

Publication Number Publication Date
WO2012138083A2 true WO2012138083A2 (fr) 2012-10-11
WO2012138083A3 WO2012138083A3 (fr) 2013-01-10

Family

ID=46969649

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/002439 Ceased WO2012138083A2 (fr) 2011-04-02 2012-04-02 Appareil et procédé pour effectuer une révocation de consentement d'utilisateur à une réduction au minimum des tests de mesure de qualité de service en communication sans fil

Country Status (2)

Country Link
KR (1) KR20120111837A (fr)
WO (1) WO2012138083A2 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014101518A1 (fr) * 2012-12-26 2014-07-03 中兴通讯股份有限公司 Procédé et dispositif de localisation au moyen d'un essai de conduite
WO2015115782A1 (fr) * 2014-01-30 2015-08-06 Lg Electronics Inc. Procédé et appareil de prise en charge de réduction à un minimum de tests de couverture radio de partage de réseau d'accès radio dans un système de communication sans fil
WO2015115825A1 (fr) * 2014-01-29 2015-08-06 Lg Electronics Inc. Procédé et appareil de transmission de message de compte-rendu dans un système de communications sans fil
US10349299B2 (en) 2015-03-23 2019-07-09 Telefonaktiebolaget Lm Ericsson (Publ) Technique for controlling minimizing of drive tests log tracing of user equipment in idle mode
WO2020222689A1 (fr) * 2019-04-30 2020-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Procédés se rapportant à des configurations mdt et dispositifs associés
WO2022005379A1 (fr) * 2020-06-30 2022-01-06 Telefonaktiebolaget Lm Ericsson (Publ) Contrôle réseau amélioré de rapports de mesure de qualité d'expérience (qoe) par un équipement utilisateur
EP3860188A4 (fr) * 2018-09-28 2022-07-06 ZTE Corporation Cliquez sur ce lien avec le bouton droit de la souris pour le conserver dans vos signets
EP4111764A4 (fr) * 2021-05-10 2023-01-04 Apple Inc. Révocation et modification de consentement de l'utilisateur
CN115769171A (zh) * 2020-07-07 2023-03-07 诺基亚技术有限公司 Ml ue性能和无能力

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
'Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification' 3GPP STANDARD TS 36.331, VERSION 8.13.0. March 2011, *
'Evolved Universal Terrestrial Radio Access (E-UTRA); Study on Minimization of Drive-Tests in Next Generation Networks' 3GPP STANDARD TS 36.805, VERSION 9.0.0 December 2009, *
'Subscriber and Equipment trace; Trace Control and Configuration Management' 3GPP STANDARD TS 32.422, VERSION 10.3.0 March 2011, *
'Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2' 3GPP STANDARD TS 37.320, VERSION 10.0.0 December 2010, *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9581680B2 (en) 2012-12-26 2017-02-28 Zte Corporation Positioning method and device for drive test
WO2014101518A1 (fr) * 2012-12-26 2014-07-03 中兴通讯股份有限公司 Procédé et dispositif de localisation au moyen d'un essai de conduite
WO2015115825A1 (fr) * 2014-01-29 2015-08-06 Lg Electronics Inc. Procédé et appareil de transmission de message de compte-rendu dans un système de communications sans fil
WO2015115782A1 (fr) * 2014-01-30 2015-08-06 Lg Electronics Inc. Procédé et appareil de prise en charge de réduction à un minimum de tests de couverture radio de partage de réseau d'accès radio dans un système de communication sans fil
US9888403B2 (en) 2014-01-30 2018-02-06 Lg Electronics Inc. Method and apparatus for supporting minimization of drive tests for radio access network sharing in wireless communication system
US10349299B2 (en) 2015-03-23 2019-07-09 Telefonaktiebolaget Lm Ericsson (Publ) Technique for controlling minimizing of drive tests log tracing of user equipment in idle mode
EP3860188A4 (fr) * 2018-09-28 2022-07-06 ZTE Corporation Cliquez sur ce lien avec le bouton droit de la souris pour le conserver dans vos signets
WO2020222689A1 (fr) * 2019-04-30 2020-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Procédés se rapportant à des configurations mdt et dispositifs associés
WO2022005379A1 (fr) * 2020-06-30 2022-01-06 Telefonaktiebolaget Lm Ericsson (Publ) Contrôle réseau amélioré de rapports de mesure de qualité d'expérience (qoe) par un équipement utilisateur
US12506667B2 (en) 2020-06-30 2025-12-23 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced network control over quality-of-experience (QoE) measurement reports by user equipment
CN115769171A (zh) * 2020-07-07 2023-03-07 诺基亚技术有限公司 Ml ue性能和无能力
EP4111764A4 (fr) * 2021-05-10 2023-01-04 Apple Inc. Révocation et modification de consentement de l'utilisateur
US12284719B2 (en) 2021-05-10 2025-04-22 Apple Inc. Revocation and modification of user consent

Also Published As

Publication number Publication date
WO2012138083A3 (fr) 2013-01-10
KR20120111837A (ko) 2012-10-11

Similar Documents

Publication Publication Date Title
WO2012138083A2 (fr) Appareil et procédé pour effectuer une révocation de consentement d'utilisateur à une réduction au minimum des tests de mesure de qualité de service en communication sans fil
KR101376262B1 (ko) 무선 통신 시스템, 무선 통신 방법, 무선국, 제어국, 및 프로그램을 저장하는 컴퓨터 판독 가능한 기록 매체
JP7261834B2 (ja) 無線通信システムにおけるモビリティ管理方法及び装置
US10390270B2 (en) Communications system
CN101931984B (zh) 一种路测测量的方法、用户设备及基站
CN102293031B (zh) 在无线通信系统中报告集合的测量的方法
KR101439725B1 (ko) 캐리어 집성 시스템에서의 측정 작업 처리 방법 및 시스템
US12550008B2 (en) Communication method and apparatus
US11963148B2 (en) User equipment operating mode control
JP6633779B2 (ja) 無線端末、プロセッサ、及び方法
EP2677807B1 (fr) Procédé de commande d'un équipement utilisateur permettant d'effectuer des mesures, équipement et système associés
JP2017038410A (ja) 無線通信システムにおけるｍｂｍｓ情報報告方法及びそれをサポートする装置
CN104662948A (zh) 用于流量热点测量的通信设备、移动终端和方法
US10021607B2 (en) Measurement configuration processing method and device
WO2016095549A1 (fr) Procédé et dispositif de mise en œuvre de rapport de défaillance d'établissement de connexion de cellule et support d'informations
KR20190039270A (ko) 단말의 이동성 패턴을 관리하는 방법 및 장치
KR102646347B1 (ko) Mdt 측정 로그 전송 방법, 단말기 및 판독가능한 저장 매체
KR20130060194A (ko) 무선링크 실패 정보의 처리 방법 및 시스템
KR102051851B1 (ko) 이동통신 시스템에서 단말 접속 제어 장치 및 그 방법
WO2012093875A2 (fr) Procédé d'essai de commande de minimalisation et appareil utilisant celui-ci
WO2012083703A1 (fr) Procédé et système de mesure de relation de cellules voisines
CN102547826B (zh) 邻区测量信息的上报方法及系统、终端设备
CN121844596A (zh) 配置用于收集和报告与漫游网络相关联的数据的ue
CN120786638A (zh) 资源配置方法、装置、存储介质及程序产品
KR20120048858A (ko) 무선 통신 시스템에서 운전 시험 최소화를 수행하는 장치 및 방법

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: 12767406

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12767406

Country of ref document: EP

Kind code of ref document: A2