WO2019183852A1 - 信息上报方法及装置、用户设备和计算机可读存储介质 - Google Patents

信息上报方法及装置、用户设备和计算机可读存储介质 Download PDF

Info

Publication number
WO2019183852A1
WO2019183852A1 PCT/CN2018/080950 CN2018080950W WO2019183852A1 WO 2019183852 A1 WO2019183852 A1 WO 2019183852A1 CN 2018080950 W CN2018080950 W CN 2018080950W WO 2019183852 A1 WO2019183852 A1 WO 2019183852A1
Authority
WO
WIPO (PCT)
Prior art keywords
integrity check
information
reporting
integrity
check failure
Prior art date
Application number
PCT/CN2018/080950
Other languages
English (en)
French (fr)
Inventor
江小威
Original Assignee
北京小米移动软件有限公司
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 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN201880000532.1A priority Critical patent/CN108496337B/zh
Priority to PCT/CN2018/080950 priority patent/WO2019183852A1/zh
Publication of WO2019183852A1 publication Critical patent/WO2019183852A1/zh
Priority to US17/017,602 priority patent/US11877155B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • 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
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to an information reporting method and apparatus, a user equipment, and a computer readable storage medium.
  • LTE Long Term Evolution
  • MDT Minimized Driving Test
  • MCG primary cell group
  • the present application discloses an information reporting method and apparatus, a user equipment, and a computer readable storage medium, so that the UE reports the integrity check related information to the network after the user plane data integrity verification fails. Help with network location issues.
  • an information reporting method is provided, which is applied to a user equipment UE, and the method includes:
  • the integrity check failure related information includes one or more of the following information: location information of the UE, and the failure indication type is integrity
  • the failure information and the integrity check failure information are reported in the trigger mode and the number of integrity check failures.
  • the method further includes:
  • the base station Receiving, by the base station, the first configuration information that is sent by the base station, where the first configuration information includes: configuring a DRB identifier that can trigger information related to the failure of the integrity check failure;
  • the triggering reports the integrity check failure related information including:
  • the triggering reports the integrity check failure related information, including one or more of the following:
  • the information about the integrity check failure is reported to be reported.
  • the first preset number of times is configured by the base station or agreed by the current system
  • the second preset number of times is configured by the base station, or is agreed by the current system, or configured for each UE, or configured for each DRB;
  • the third preset number of times and the first preset duration are configured by the base station, or are agreed by the current system, or configured for each UE;
  • the fourth preset number of times and the second preset duration are configured by the base station, or are agreed by the current system, or configured for each UE, or configured for each DRB.
  • the method further includes:
  • the integrity check failure related information can be reported again.
  • the suppression timer is configured by the base station or by the current system.
  • the method further includes:
  • an information reporting apparatus which is applied to a user equipment UE, and the apparatus includes:
  • the receiving verification module is configured to receive downlink data of the data bearer DRB that is enabled with the integrity protection function, and perform integrity verification on the downlink data of the DRB;
  • the triggering reporting module is configured to: if the receiving verification module fails to perform the integrity check, triggering the reporting of the integrity check failure related information, where the integrity verification failure related information includes one or more of the following information: Item: The location information of the UE, the failure indication type is the integrity check failure, the indication information of the triggering manner of the information about the integrity check failure report, and the number of times the integrity check failure occurs.
  • the apparatus further includes:
  • the first receiving module is configured to receive the first configuration information that is sent by the base station, where the first configuration information includes: configuring a DRB identifier that can trigger the information related to the failure of the integrity check failure;
  • the trigger reporting module is configured to: trigger the reporting integrity check failure related information according to the first configuration information received by the first receiving module.
  • the trigger reporting module includes one or more of the following submodules:
  • the first trigger reporting sub-module is configured to trigger the reporting of the integrity verification failure related information when the number of occurrences of the integrity check failure of the UE reaches a first preset number of times;
  • the second trigger reporting sub-module is configured to trigger the reporting of the integrity check failure related information when the number of occurrences of the integrity check failures for the same DRB reaches a second preset number of times;
  • the third trigger reporting sub-module is configured to trigger the reporting of the integrity check failure when the number of occurrences of the integrity check failure of the UE reaches a third preset number of times in the first preset duration information;
  • the fourth trigger reporting sub-module is configured to trigger the reporting of the integrity check failure when the number of occurrences of the integrity check failures for the same DRB reaches a fourth preset number of times within the second preset duration Related Information.
  • the first preset number of times is configured by the base station or agreed by the current system
  • the second preset number of times is configured by the base station, or is agreed by the current system, or configured for each UE, or configured for each DRB;
  • the third preset number of times and the first preset duration are configured by the base station, or are agreed by the current system, or configured for each UE;
  • the fourth preset number of times and the second preset duration are configured by the base station, or are agreed by the current system, or configured for each UE, or configured for each DRB.
  • the apparatus further includes:
  • the startup module is configured to start the set suppression timer after the trigger report module triggers reporting the integrity check failure related information
  • Stopping the reporting module configured to report the integrity verification failure related information before the suppression timer started by the startup module expires
  • the reporting module is configured to report the integrity check failure related information after the suppression timer started by the startup module expires.
  • the suppression timer is configured by the base station or by the current system.
  • the apparatus further includes:
  • the second receiving module is configured to receive second configuration information sent by the base station
  • the opening module is configured to perform an integrity protection function on the DRB of the configuration integrity protection function according to the second configuration information received by the second receiving module, so that the receiving verification module receives the DRB that performs the integrity protection function. Downstream data.
  • a user equipment including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the integrity check failure related information includes one or more of the following information: location information of the UE, and the failure indication type is integrity
  • the failure information and the integrity check failure information are reported in the trigger mode and the number of integrity check failures.
  • a computer readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the steps of the information reporting method described above.
  • the UE After receiving the downlink data of the DRB that is enabled with the integrity protection function, and performing integrity check on the downlink data of the DRB, and then triggering the integrity check failure information after the integrity check fails, the UE is in the user plane. After the data integrity check fails, the integrity check related information is reported to the network to help the network locate the problem.
  • FIG. 1 is a flowchart of an information reporting method according to an exemplary embodiment of the present application
  • FIG. 2 is a flowchart of another information reporting method according to an exemplary embodiment of the present application.
  • FIG. 3 is a flowchart of another information reporting method according to an exemplary embodiment of the present application.
  • FIG. 5 is a block diagram of an information reporting apparatus according to an exemplary embodiment
  • FIG. 6 is a block diagram of another information reporting apparatus according to an exemplary embodiment
  • FIG. 7 is a block diagram of another information reporting apparatus according to an exemplary embodiment.
  • FIG. 8 is a block diagram of another information reporting apparatus according to an exemplary embodiment.
  • FIG. 9 is a block diagram of another information reporting apparatus according to an exemplary embodiment.
  • FIG. 10 is a block diagram of an apparatus for information reporting, according to an exemplary embodiment.
  • FIG. 1 is a flowchart of an information reporting method according to an exemplary embodiment of the present application. The embodiment is described from the UE side. As shown in FIG. 1 , the information reporting method includes:
  • step S101 the downlink data of the data bearer (DRB) of the integrity protection function is received, and the integrity check of the downlink data of the DRB is performed.
  • DRB data bearer
  • step S102 if the integrity check fails, the information about the integrity check failure is reported, and the integrity check failure related information may include but is not limited to one or more of the following information: the location of the UE.
  • the information and the failure indication type are the integrity check failure, the integrity check failure, the indication information of the triggering manner, and the number of times the integrity check failure occurs.
  • the manner of triggering the information about the failure of the integrity check failure may be one or more of the following:
  • the first preset number of times is configured by the base station or by the current system.
  • the second preset number is configured by the base station, or is agreed by the current system, or configured for each UE, or configured for each DRB.
  • the third preset number of times and the first preset duration are configured by the base station, or are agreed by the current system, or configured for each UE.
  • the method 4) triggers the reporting of the integrity check failure related information if the number of occurrences of the integrity check failures for the same DRB reaches the fourth preset number of times in the second preset duration.
  • the fourth preset number of times and the second preset duration are configured by the base station, or are agreed by the current system, or configured for each UE, or configured for each DRB.
  • first preset number of times, the second preset number of times, the third preset number of times, and the fourth preset number of times may be the same or different.
  • the first preset duration and the second preset duration may be the same or different.
  • the embodiment can trigger the reporting of integrity check failure information in multiple manners, and the triggering manner is flexible.
  • the downlink data of the DRB that is enabled with the integrity protection function is received, and the integrity check of the downlink data of the DRB is performed, and then, after the integrity check fails, the information related to the integrity check failure is triggered to be implemented.
  • the UE reports the integrity check related information to the network to help the network locate problem.
  • FIG. 2 is a flowchart of another information reporting method according to an exemplary embodiment of the present application. As shown in FIG. 2, the method includes:
  • step S201 downlink data of the DRB that performs the integrity protection function is received, and integrity verification of the downlink data of the DRB is performed.
  • step S202 the first configuration information sent by the base station is received, where the first configuration information includes a DRB identifier (ID) configured to trigger information related to the reported integrity check failure.
  • ID DRB identifier
  • step S203 if the integrity check fails, the information related to the integrity check failure is triggered according to the first configuration information.
  • the integrity check failure related information may include, but is not limited to, one or more of the following information: location information of the UE, DRB ID, failure indication type, integrity check failure, integrity check failure related information The indication information of the trigger mode and the number of occurrences of the integrity check failure are reported.
  • the manner of triggering the information about the integrity check failure to be reported according to the first configuration information may be one or more of the modes 1) to 4) provided in the embodiment shown in FIG. 1 , and details are not described herein.
  • the first configuration information that is sent by the base station including the configuration of the DRB ID, which is configured to trigger the information about the failure of the integrity check failure, is configured to enable the UE to trigger the report of the integrity check failure according to the first configuration information.
  • FIG. 3 is a flowchart of another information reporting method according to an exemplary embodiment of the present application. As shown in FIG. 3, after the step S102, the method may further include:
  • step S103 after the integrity check failure related information is reported, the set suppression timer is started.
  • the suppression timer is configured by the base station or by the current system.
  • step S104 the integrity check failure related information can no longer be reported before the suppression timer expires.
  • step S105 after the suppression timer expires, the integrity check failure related information can be reported again.
  • the set suppression timer is started, and the information about the integrity check failure cannot be reported again before the suppression timer expires. After the suppression timer expires, The information about the integrity check failure can be reported again to reduce the number of times the UE reports and reduce the system energy consumption.
  • FIG. 4 is a signaling flowchart of an information reporting method according to an exemplary embodiment of the present application. As shown in FIG. 4, the method may include:
  • step S401 the base station sends second configuration information to the UE.
  • step S402 the UE receives the second configuration information sent by the base station, and starts the integrity protection function on the DRB configured with the integrity protection function according to the second configuration information.
  • step S403 the UE receives the downlink data of the DRB that turns on the integrity protection function, and performs integrity check on the downlink data of the DRB.
  • step S404 if the integrity check fails, the UE triggers reporting the integrity check failure related information.
  • the integrity check failure related information includes, but is not limited to, one or more of the following information: the location information of the UE, the DRB ID, the failure indication type is an integrity check failure, and the integrity check failure information is reported.
  • the indication of the trigger mode and the number of occurrences of the integrity check failure is reported.
  • the base station may send the related information to a Trace Collection Entity (TCE), and the data in the TCE is processed by a dedicated analysis platform. For example, draw a location map of the integrity check failure to locate the security attack area, and then go to the site to troubleshoot the problem.
  • TCE Trace Collection Entity
  • the UE may trigger the reporting of the integrity check failure information after the integrity check fails, so that the UE may go to the network after the user plane data integrity check fails. Report integrity check related information to help locate the network.
  • FIG. 5 is a block diagram of an information reporting apparatus, which may be located in a UE. As shown in FIG. 5, the apparatus includes: a receiving verification module 51 and a trigger reporting module 52, according to an exemplary embodiment.
  • the receiving check module 51 is configured to receive the downlink data of the data bearer DRB that is enabled with the integrity protection function, and perform integrity check on the downlink data of the DRB.
  • the triggering reporting module 52 is configured to trigger the reporting of the integrity check failure related information if the integrity check failure is performed by the receiving verification module 51.
  • the integrity check failure related information includes one or more of the following information: UE The location information, the failure indication type is the integrity check failure, the indication information of the triggering manner for reporting the integrity check failure, and the number of occurrences of the integrity check failure.
  • the downlink data of the DRB that is enabled with the integrity protection function is received, and the integrity check of the downlink data of the DRB is performed, and then, after the integrity check fails, the information related to the integrity check failure is triggered to be implemented.
  • the UE reports the integrity check related information to the network to help the network locate problem.
  • FIG. 6 is a block diagram of another information reporting apparatus according to an exemplary embodiment. As shown in FIG. 6, the apparatus may further include: a first receiving module 53 on the basis of the foregoing embodiment shown in FIG.
  • the first receiving module 53 is configured to receive the first configuration information sent by the base station, where the first configuration information includes a DRB identifier configured to trigger information related to the failure of the integrity check failure.
  • the trigger report module 52 can be configured to trigger the report integrity check failure related information according to the first configuration information received by the first receiving module 53.
  • the manner in which the triggering and reporting module 52 triggers the information about the integrity check failure to be reported according to the first configuration information may be one or more of the modes 1) to 4) provided in the embodiment shown in FIG. Do not repeat them.
  • the first configuration information that is sent by the base station including the configuration of the DRB ID, which is configured to trigger the information about the failure of the integrity check failure, is configured to enable the UE to trigger the report of the integrity check failure according to the first configuration information.
  • FIG. 7 is a block diagram of another information reporting apparatus according to an exemplary embodiment.
  • the trigger reporting module 52 may include the following one or The sub-modules are: a first trigger reporting sub-module 521, a second trigger reporting sub-module 522, a third trigger reporting sub-module 523, and a fourth trigger reporting sub-module 524.
  • the first trigger reporting sub-module 521 is configured to trigger the reporting of the integrity check failure related information when the number of occurrences of the integrity check failure of the UE reaches the first preset number of times.
  • the first preset number of times is configured by the base station or by the current system.
  • the second trigger reporting sub-module 522 is configured to trigger the reporting of the integrity check failure related information when the number of occurrences of the integrity check failure for the same DRB reaches a second preset number of times.
  • the second preset number is configured by the base station, or is agreed by the current system, or configured for each UE, or configured for each DRB.
  • the third trigger reporting sub-module 523 is configured to trigger the reporting of the integrity check failure related information when the number of occurrences of the integrity check failure of the UE reaches the third preset number of times within the first preset duration.
  • the third preset number of times and the first preset duration are configured by the base station, or are agreed by the current system, or configured for each UE.
  • the fourth trigger reporting sub-module 524 is configured to trigger the reporting of the integrity verification failure related information when the number of occurrences of the integrity check failures for the same DRB reaches a fourth predetermined number of times within the second preset duration.
  • the fourth preset number of times and the second preset duration are configured by the base station, or are agreed by the current system, or configured for each UE, or configured for each DRB.
  • first preset number of times, the second preset number of times, the third preset number of times, and the fourth preset number of times may be the same or different.
  • the first preset duration and the second preset duration may be the same or different.
  • the information related to the integrity check failure is triggered in multiple manners, and the triggering manner is flexible.
  • FIG. 8 is a block diagram of another information reporting apparatus according to an exemplary embodiment. As shown in FIG. 8 , on the basis of the embodiment shown in FIG. 5 , the apparatus may further include: starting the module 54 and stopping reporting. Module 55 and reporting module 56.
  • the startup module 54 is configured to initiate the set suppression timer after the trigger report module 52 triggers reporting an integrity check failure related information.
  • the suppression timer is configured by the base station or by the current system.
  • the stop reporting module 55 is configured to not report the integrity check failure related information until the suppression timer initiated by the startup module 54 times out.
  • the reporting module 56 is configured to report the integrity check failure related information again after the suppression timer initiated by the startup module 54 times out.
  • the set suppression timer is started, and the information about the integrity check failure cannot be reported again before the suppression timer expires. After the suppression timer expires, The information about the integrity check failure can be reported again to reduce the number of times the UE reports and reduce the system energy consumption.
  • FIG. 9 is a block diagram of another information reporting apparatus according to an exemplary embodiment. As shown in FIG. 9, on the basis of the foregoing embodiment shown in FIG. 5, the apparatus may further include: a second receiving module 57 and Module 58 is turned on.
  • the second receiving module 57 is configured to receive second configuration information sent by the base station.
  • the opening module 58 is configured to turn on the integrity protection function of the DRB configuring the integrity protection function according to the second configuration information received by the second receiving module 57, so as to receive the downlink data of the DRB that the verification module 51 receives the integrity protection function.
  • the base station may send the related information to a Trace Collection Entity (TCE), and the data in the TCE is processed by a dedicated analysis platform. For example, draw a location map of the integrity check failure to locate the security attack area, and then go to the site to troubleshoot the problem.
  • TCE Trace Collection Entity
  • the UE may trigger the reporting of the integrity check failure information after the integrity check fails, so that the UE may go to the network after the user plane data integrity check fails. Report integrity check related information to help locate the network.
  • FIG. 10 is a block diagram of an apparatus for information reporting, according to an exemplary embodiment.
  • the device 1000 can be a user device such as a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • apparatus 1000 can include one or more of the following components: processing component 1002, memory 1004, power component 1006, multimedia component 1008, audio component 1010, input/output (I/O) interface 1012, sensor component 1014, And a communication component 1016.
  • Processing component 1002 typically controls the overall operation of device 1000, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 1002 can include one or more processors 1020 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 1002 can include one or more modules to facilitate interaction between component 1002 and other components.
  • processing component 1002 can include a multimedia module to facilitate interaction between multimedia component 1008 and processing component 1002.
  • One of the processors 1020 in the processing component 1002 can be configured to:
  • the integrity check failure related information includes one or more of the following information: the location information of the UE, and the failure indication type is an integrity check failure.
  • the indication information of the triggering mode and the number of times the integrity check failure occurs are reported.
  • the memory 1004 is configured to store various types of data to support operation at the device 1000. Examples of such data include instructions for any application or method operating on device 1000, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 1004 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk
  • Optical Disk Optical Disk
  • Power component 1006 provides power to various components of device 1000.
  • Power component 1006 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1000.
  • the multimedia component 1008 includes a screen between the device 1000 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 1008 includes a front camera and/or a rear camera. When the device 1000 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 1010 is configured to output and/or input an audio signal.
  • the audio component 1010 includes a microphone (MIC) that is configured to receive an external audio signal when the device 1000 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 1004 or transmitted via communication component 1016.
  • the audio component 1010 also includes a speaker for outputting an audio signal.
  • the I/O interface 1012 provides an interface between the processing component 1002 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 1014 includes one or more sensors for providing device 1000 with various aspects of state assessment.
  • sensor assembly 1014 can detect an open/closed state of device 1000, a relative positioning of components, such as the display and keypad of device 1000, and sensor component 1014 can also detect a change in position of one component of device 1000 or device 1000. The presence or absence of contact by the user with the device 1000, the orientation of the device 1000 or acceleration/deceleration and temperature changes of the device 1000.
  • Sensor assembly 1014 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1014 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 1016 is configured to facilitate wired or wireless communication between device 1000 and other devices.
  • the device 1000 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • communication component 1016 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 1016 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • apparatus 1000 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 1004 comprising instructions executable by processor 1020 of apparatus 1000 to perform the above method.
  • the non-transitory computer readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

本公开是关于一种信息上报方法及装置、用户设备和计算机可读存储介质。其中，信息上报方法包括：接收开启完整性保护功能的数据承载DRB的下行数据，并对DRB的下行数据进行完整性校验；若完整性校验失败，则触发上报完整性校验失败相关信息，该完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。本公开实施例可以实现UE在用户面数据完整性校验失败后，向网络上报完整性校验相关信息，以帮助网络定位问题。

Description

信息上报方法及装置、用户设备和计算机可读存储介质 技术领域
本公开涉及通信技术领域，尤其涉及一种信息上报方法及装置、用户设备和计算机可读存储介质。
背景技术
随着无线通信技术的飞速发展，长期演进(Long Term Evolution，简称LTE)引入最小化路测(Minimized Driving Test，简称MDT)技术来帮助网络排查问题。最小化路测技术支持空闲态和连接态。对于连接态用户设备(UE)，网络可以配置UE在进行测量上报时，同时上报UE的位置信息来帮助网络了解各个位置的信号质量。同时，连接态UE在发生主小区组(Master Cell Group，简称MCG)无线链路失败(Radio Link Failure)，切换失败时也需要上报位置信息。
在LTE***中，仅针对控制面做完整性保护，在新空口(NR)中，引入了针对用户面数据的完整性保护功能。但用户面数据完整性校验可能会失败，而失败后如何操作是需要解决的一个技术问题。
发明内容
有鉴于此，本申请公开了一种信息上报方法及装置、用户设备和计算机可读存储介质，以实现UE在用户面数据完整性校验失败后，向网络上报完整性校验相关信息，以便帮助网络定位问题。
根据本公开实施例的第一方面，提供一种信息上报方法，应用于用户设备UE，所述方法包括：
接收开启完整性保护功能的数据承载DRB的下行数据，并对所述DRB的下行数据进行完整性校验；
若完整性校验失败，则触发上报完整性校验失败相关信息，所述完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
在一实施例中，所述方法还包括：
接收基站发送的第一配置信息，所述第一配置信息包括配置能够触发上报完整性校验失败相关信息的DRB标识；
所述触发上报完整性校验失败相关信息，包括：
根据所述第一配置信息触发上报完整性校验失败相关信息。
在一实施例中，所述触发上报完整性校验失败相关信息，包括以下一项或几项：
若所述UE的所述完整性校验失败发生次数累计达到第一预设次数，则触发上报所述完整性校验失败相关信息；
若针对同一个DRB的所述完整性校验失败发生次数累计达到第二预设次数，则触发上报所述完整性校验失败相关信息；
若在第一预设时长内所述UE的所述完整性校验失败发生次数累计达到第三预设次数，则触发上报所述完整性校验失败相关信息；
若在第二预设时长内针对同一个DRB的所述完整性校验失败发生次数累计达到第四预设次数，则触发上报所述完整性校验失败相关信息。
在一实施例中，所述第一预设次数由基站配置或由当前***约定；
所述第二预设次数由所述基站配置，或者由所述当前***约定，或者针对每个UE配置，或者针对每个DRB配置；
所述第三预设次数和所述第一预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置；
所述第四预设次数和所述第二预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
在一实施例中，所述方法还包括：
在上报一次所述完整性校验失败相关信息之后，启动设置的抑制定时器；
在所述抑制定时器超时之前，不能再上报所述完整性校验失败相关信息；
在所述抑制定时器超时之后，能够再上报所述完整性校验失败相关信息。
在一实施例中，所述抑制定时器由基站配置或由当前***约定。
在一实施例中，所述方法还包括：
接收基站发送的第二配置信息；
根据所述第二配置信息对配置完整性保护功能的DRB开启完整性保护功能。
根据本公开实施例的第二方面，提供一种信息上报装置，应用于用户设备UE，所述装置包括：
接收校验模块，被配置为接收开启完整性保护功能的数据承载DRB的下行数据，并对所述DRB的下行数据进行完整性校验；
触发上报模块，被配置为若所述接收校验模块进行完整性校验失败，则触发上报完整性校验失败相关信息，所述完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
在一实施例中，所述装置还包括：
第一接收模块，被配置为接收基站发送的第一配置信息，所述第一配置信息包括配置能够触发上报完整性校验失败相关信息的DRB标识；
所述触发上报模块，被配置为：根据所述第一接收模块接收的所述第一配置信息触发上报完整性校验失败相关信息。
在一实施例中，所述触发上报模块包括以下一个或几个子模块：
第一触发上报子模块，被配置为当所述UE的所述完整性校验失败发生次数累计达到第一预设次数时，触发上报所述完整性校验失败相关信息；
第二触发上报子模块，被配置为当针对同一个DRB的所述完整性校验失败发生次数累计达到第二预设次数时，触发上报所述完整性校验失败相关信息；
第三触发上报子模块，被配置为当在第一预设时长内所述UE的所述完整性校验失败发生次数累计达到第三预设次数时，触发上报所述完整性校验失败相关信息；
第四触发上报子模块，被配置为当在第二预设时长内针对同一个DRB的所述完整性校验失败发生次数累计达到第四预设次数时，触发上报所述完整性校验失败相关信息。
在一实施例中，所述第一预设次数由基站配置或由当前***约定；
所述第二预设次数由所述基站配置，或者由所述当前***约定，或者针对每个UE配置， 或者针对每个DRB配置；
所述第三预设次数和所述第一预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置；
所述第四预设次数和所述第二预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
在一实施例中，所述装置还包括：
启动模块，被配置为在所述触发上报模块触发上报一次所述完整性校验失败相关信息之后，启动设置的抑制定时器；
停止上报模块，被配置为在所述启动模块启动的所述抑制定时器超时之前，不能再上报所述完整性校验失败相关信息；
上报模块，被配置为在所述启动模块启动的所述抑制定时器超时之后，能够再上报所述完整性校验失败相关信息。
在一实施例中，所述抑制定时器由基站配置或由当前***约定。
在一实施例中，所述装置还包括：
第二接收模块，被配置为接收基站发送的第二配置信息；
开启模块，被配置为根据所述第二接收模块接收的所述第二配置信息对配置完整性保护功能的DRB开启完整性保护功能，以便所述接收校验模块接收开启完整性保护功能的DRB的下行数据。
根据本公开实施例的第三方面，提供一种用户设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收开启完整性保护功能的数据承载DRB的下行数据，并对所述DRB的下行数据进行完整性校验；
若完整性校验失败，则触发上报完整性校验失败相关信息，所述完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
根据本公开实施例的第四方面，提供一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现上述的信息上报方法的步骤。
本公开的实施例提供的技术方案可以包括以下有益效果：
通过接收开启完整性保护功能的DRB的下行数据，并对DRB的下行数据进行完整性校验，然后在完整性校验失败后，触发上报完整性校验失败相关信息，以实现UE在用户面数据完整性校验失败后，向网络上报完整性校验相关信息，以帮助网络定位问题。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
图1是本申请一示例性实施例示出的一种信息上报方法的流程图；
图2是本申请一示例性实施例示出的另一种信息上报方法的流程图；
图3是本申请一示例性实施例示出的另一种信息上报方法的流程图；
图4是本申请一示例性实施例示出的一种信息上报方法的信令流程图；
图5是根据一示例性实施例示出的一种信息上报装置的框图；
图6是根据一示例性实施例示出的另一种信息上报装置的框图；
图7是根据一示例性实施例示出的另一种信息上报装置的框图；
图8是根据一示例性实施例示出的另一种信息上报装置的框图；
图9是根据一示例性实施例示出的另一种信息上报装置的框图；
图10是根据一示例性实施例示出的一种适用于信息上报装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书 中所详述的、本发明的一些方面相一致的装置和方法的例子。
图1是本申请一示例性实施例示出的一种信息上报方法的流程图，该实施例从UE侧进行描述，如图1所示，该信息上报方法包括：
在步骤S101中，接收开启完整性保护功能的数据承载(DRB)的下行数据，并对DRB的下行数据进行完整性校验。
在步骤S102中，若完整性校验失败，则触发上报完整性校验失败相关信息，该完整性校验失败相关信息可以包括但不局限于以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
其中，触发上报完整性校验失败相关信息的方式可以为以下方式中的一种或几种：
方式1)若UE的完整性校验失败发生次数累计达到第一预设次数，则触发上报完整性校验失败相关信息。
其中，第一预设次数由基站配置或由当前***约定。
方式2)若针对同一个DRB的完整性校验失败发生次数累计达到第二预设次数，则触发上报完整性校验失败相关信息。
其中，第二预设次数由基站配置，或者由当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
方式3)若在第一预设时长内UE的完整性校验失败发生次数累计达到第三预设次数，则触发上报完整性校验失败相关信息。
其中，第三预设次数和第一预设时长由基站配置，或者由当前***约定，或者针对每个UE配置。
方式4)若在第二预设时长内针对同一个DRB的完整性校验失败发生次数累计达到第四预设次数，则触发上报完整性校验失败相关信息。
其中，第四预设次数和第二预设时长由基站配置，或者由当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
需要说明的是，上述第一预设次数、第二预设次数、第三预设次数和第四预设次数可以相同，也可以不同。第一预设时长和第二预设时长可以相同，也可以不同。
由此可见，该实施例可以采用多种方式触发上报完整性校验失败相关信息，触发方式灵活多样。
上述实施例，通过接收开启完整性保护功能的DRB的下行数据，并对DRB的下行数据进行完整性校验，然后在完整性校验失败后，触发上报完整性校验失败相关信息，以实现UE在用户面数据完整性校验失败后，向网络上报完整性校验相关信息，以帮助网络定位问题。
图2是本申请一示例性实施例示出的另一种信息上报方法的流程图，如图2所示，该方法包括：
在步骤S201中，接收开启完整性保护功能的DRB的下行数据，并对DRB的下行数据进行完整性校验。
在步骤S202中，接收基站发送的第一配置信息，该第一配置信息包括配置能够触发上报完整性校验失败相关信息的DRB标识(ID)。
在步骤S203中，若完整性校验失败，则根据第一配置信息触发上报完整性校验失败相关信息。
其中，完整性校验失败相关信息可以包括但不局限于以下信息中的一项或多项：UE的位置信息、DRB ID、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
其中，根据第一配置信息触发上报完整性校验失败相关信息的方式可以为图1所示实施例中提供的方式1)至方式4)中的一种或几种，此处不赘述。
上述实施例，通过接收基站发送的包括配置能够触发上报完整性校验失败相关信息的DRB ID的第一配置信息，使得UE可以根据第一配置信息触发上报完整性校验失败相关信息，以帮助网络定位问题。
图3是本申请一示例性实施例示出的另一种信息上报方法的流程图，如图3所示，在上述步骤S102之后，该方法还可以包括：
在步骤S103中，在上报一次完整性校验失败相关信息之后，启动设置的抑制定时器。
其中，抑制定时器由基站配置或由当前***约定。
在步骤S104中，在抑制定时器超时之前，不能再上报完整性校验失败相关信息。
在步骤S105中，在抑制定时器超时之后，能够再上报完整性校验失败相关信息。
上述实施例，通过在上报一次完整性校验失败相关信息之后，启动设置的抑制定时器，并在抑制定时器超时之前，不能再上报完整性校验失败相关信息，在抑制定时器超时之后，能够再上报完整性校验失败相关信息，以减少UE的上报次数，减少***能耗。
图4是本申请一示例性实施例示出的一种信息上报方法的信令流程图，如图4所示，该方法可以包括：
在步骤S401中，基站向UE发送第二配置信息。
在步骤S402中，UE接收基站发送的第二配置信息，并根据第二配置信息对配置完整性保护功能的DRB开启完整性保护功能。
在步骤S403中，UE接收开启完整性保护功能的DRB的下行数据，并对DRB的下行数据进行完整性校验。
在步骤S404中，若完整性校验失败，则UE触发上报完整性校验失败相关信息。
其中，完整性校验失败相关信息包括但不局限于以下信息中的一项或多项：UE的位置信息、DRB ID、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
在该实施例中，基站接收UE上报的完整性校验失败相关信息后，可以将相关信息发给跟踪收集实体(Trace Collection Entity，TCE)，并由专门的分析平台来处理TCE中的数据，例如，画出完整性校验失败发生位置图，从而定位出安全攻击区域，进而可以去现场排查该问题。
上述实施例，通过基站和UE之间的交互，使得UE可以在完整性校验失败后，触发上报完整性校验失败相关信息，以实现UE在用户面数据完整性校验失败后，向网络上报完整性校验相关信息，以帮助网络定位问题。
图5是根据一示例性实施例示出的一种信息上报装置的框图，该装置可以位于UE中，如图5所示，该装置包括：接收校验模块51和触发上报模块52。
接收校验模块51被配置为接收开启完整性保护功能的数据承载DRB的下行数据，并对DRB的下行数据进行完整性校验。
触发上报模块52被配置为若接收校验模块51进行完整性校验失败，则触发上报完整性校验失败相关信息，完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和 完整性校验失败发生次数。
上述实施例，通过接收开启完整性保护功能的DRB的下行数据，并对DRB的下行数据进行完整性校验，然后在完整性校验失败后，触发上报完整性校验失败相关信息，以实现UE在用户面数据完整性校验失败后，向网络上报完整性校验相关信息，以帮助网络定位问题。
图6是根据一示例性实施例示出的另一种信息上报装置的框图，如图6所示，在上述图5所示实施例的基础上，该装置还可以包括：第一接收模块53。
第一接收模块53被配置为接收基站发送的第一配置信息，该第一配置信息包括配置能够触发上报完整性校验失败相关信息的DRB标识。
触发上报模块52可以被配置为：根据第一接收模块53接收的第一配置信息触发上报完整性校验失败相关信息。
其中，触发上报模块52根据第一配置信息触发上报完整性校验失败相关信息的方式可以为图1所示实施例中提供的方式1)至方式4)中的一种或几种，此处不赘述。
上述实施例，通过接收基站发送的包括配置能够触发上报完整性校验失败相关信息的DRB ID的第一配置信息，使得UE可以根据第一配置信息触发上报完整性校验失败相关信息，以帮助网络定位问题。
图7是根据一示例性实施例示出的另一种信息上报装置的框图，如图7所示，在上述图5或图6所示实施例的基础上，触发上报模块52可以包括以下一个或几个子模块：第一触发上报子模块521、第二触发上报子模块522、第三触发上报子模块523和第四触发上报子模块524。
第一触发上报子模块521被配置为当UE的完整性校验失败发生次数累计达到第一预设次数时，触发上报完整性校验失败相关信息。
其中，第一预设次数由基站配置或由当前***约定。
第二触发上报子模块522被配置为当针对同一个DRB的完整性校验失败发生次数累计达到第二预设次数时，触发上报完整性校验失败相关信息。
其中，第二预设次数由基站配置，或者由当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
第三触发上报子模块523被配置为当在第一预设时长内UE的完整性校验失败发生次数累计达到第三预设次数时，触发上报完整性校验失败相关信息。
其中，第三预设次数和第一预设时长由基站配置，或者由当前***约定，或者针对每个UE配置。
第四触发上报子模块524被配置为当在第二预设时长内针对同一个DRB的完整性校验失败发生次数累计达到第四预设次数时，触发上报完整性校验失败相关信息。
其中，第四预设次数和第二预设时长由基站配置，或者由当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
需要说明的是，上述第一预设次数、第二预设次数、第三预设次数和第四预设次数可以相同，也可以不同。第一预设时长和第二预设时长可以相同，也可以不同。
上述实施例，可以采用多种方式触发上报完整性校验失败相关信息，触发方式灵活多样。
图8是根据一示例性实施例示出的另一种信息上报装置的框图，如图8所示，在上述图5所示实施例的基础上，该装置还可以包括：启动模块54、停止上报模块55和上报模块56。
启动模块54被配置为在触发上报模块52触发上报一次完整性校验失败相关信息之后，启动设置的抑制定时器。
其中，抑制定时器由基站配置或由当前***约定。
停止上报模块55被配置为在启动模块54启动的抑制定时器超时之前，不能再上报完整性校验失败相关信息。
上报模块56被配置为在启动模块54启动的抑制定时器超时之后，能够再上报完整性校验失败相关信息。
上述实施例，通过在上报一次完整性校验失败相关信息之后，启动设置的抑制定时器，并在抑制定时器超时之前，不能再上报完整性校验失败相关信息，在抑制定时器超时之后，能够再上报完整性校验失败相关信息，以减少UE的上报次数，减少***能耗。
图9是根据一示例性实施例示出的另一种信息上报装置的框图，如图9所示，在上述图5所示实施例的基础上，该装置还可以包括：第二接收模块57和开启模块58。
第二接收模块57被配置为接收基站发送的第二配置信息。
开启模块58被配置为根据第二接收模块57接收的第二配置信息对配置完整性保护功能的DRB开启完整性保护功能，以便接收校验模块51接收开启完整性保护功能的DRB的下 行数据。
在该实施例中，基站接收UE上报的完整性校验失败相关信息后，可以将相关信息发给跟踪收集实体(Trace Collection Entity，TCE)，并由专门的分析平台来处理TCE中的数据，例如，画出完整性校验失败发生位置图，从而定位出安全攻击区域，进而可以去现场排查该问题。
上述实施例，通过基站和UE之间的交互，使得UE可以在完整性校验失败后，触发上报完整性校验失败相关信息，以实现UE在用户面数据完整性校验失败后，向网络上报完整性校验相关信息，以帮助网络定位问题。
图10是根据一示例性实施例示出的一种适用于信息上报装置的框图。例如，装置1000可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等用户设备。
参照图10，装置1000可以包括以下一个或多个组件：处理组件1002，存储器1004，电源组件1006，多媒体组件1008，音频组件1010，输入/输出(I/O)的接口1012，传感器组件1014，以及通信组件1016。
处理组件1002通常控制装置1000的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理元件1002可以包括一个或多个处理器1020来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1002可以包括一个或多个模块，便于处理组件1002和其他组件之间的交互。例如，处理部件1002可以包括多媒体模块，以方便多媒体组件1008和处理组件1002之间的交互。
处理组件1002中的其中一个处理器1020可以被配置为：
接收开启完整性保护功能的数据承载DRB的下行数据，并对DRB的下行数据进行完整性校验；
若完整性校验失败，则触发上报完整性校验失败相关信息，完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
存储器1004被配置为存储各种类型的数据以支持在设备1000的操作。这些数据的示例包括用于在装置1000上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可 擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1006为装置1000的各种组件提供电力。电源组件1006可以包括电源管理***，一个或多个电源，及其他与为装置1000生成、管理和分配电力相关联的组件。
多媒体组件1008包括在装置1000和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1008包括一个前置摄像头和/或后置摄像头。当设备1000处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜***或具有焦距和光学变焦能力。
音频组件1010被配置为输出和/或输入音频信号。例如，音频组件1010包括一个麦克风(MIC)，当装置1000处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1004或经由通信组件1016发送。在一些实施例中，音频组件1010还包括一个扬声器，用于输出音频信号。
I/O接口1012为处理组件1002和***接口模块之间提供接口，上述***接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1014包括一个或多个传感器，用于为装置1000提供各个方面的状态评估。例如，传感器组件1014可以检测到设备1000的打开/关闭状态，组件的相对定位，例如所述组件为装置1000的显示器和小键盘，传感器组件1014还可以检测装置1000或装置1000一个组件的位置改变，用户与装置1000接触的存在或不存在，装置1000方位或加速/减速和装置1000的温度变化。传感器组件1014可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1014还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1014还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1016被配置为便于装置1000和其他设备之间有线或无线方式的通信。装置1000可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性 实施例中，通信部件1016经由广播信道接收来自外部广播管理***的广播信号或广播相关信息。在一个示例性实施例中，所述通信部件1016还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1000可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1004，上述指令可由装置1000的处理器1020执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (16)

  1. 一种信息上报方法，其特征在于，应用于用户设备UE，所述方法包括：
    接收开启完整性保护功能的数据承载DRB的下行数据，并对所述DRB的下行数据进行完整性校验；
    若完整性校验失败，则触发上报完整性校验失败相关信息，所述完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收基站发送的第一配置信息，所述第一配置信息包括配置能够触发上报完整性校验失败相关信息的DRB标识；
    所述触发上报完整性校验失败相关信息，包括：
    根据所述第一配置信息触发上报完整性校验失败相关信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述触发上报完整性校验失败相关信息，包括以下一项或几项：
    若所述UE的所述完整性校验失败发生次数累计达到第一预设次数，则触发上报所述完整性校验失败相关信息；
    若针对同一个DRB的所述完整性校验失败发生次数累计达到第二预设次数，则触发上报所述完整性校验失败相关信息；
    若在第一预设时长内所述UE的所述完整性校验失败发生次数累计达到第三预设次数，则触发上报所述完整性校验失败相关信息；
    若在第二预设时长内针对同一个DRB的所述完整性校验失败发生次数累计达到第四预设次数，则触发上报所述完整性校验失败相关信息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一预设次数由基站配置或由当前***约定；
    所述第二预设次数由所述基站配置，或者由所述当前***约定，或者针对每个UE配置，或者针对每个DRB配置；
    所述第三预设次数和所述第一预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置；
    所述第四预设次数和所述第二预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
  5. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在上报一次所述完整性校验失败相关信息之后，启动设置的抑制定时器；
    在所述抑制定时器超时之前，不能再上报所述完整性校验失败相关信息；
    在所述抑制定时器超时之后，能够再上报所述完整性校验失败相关信息。
  6. 根据权利要求5所述的方法，其特征在于，所述抑制定时器由基站配置或由当前***约定。
  7. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收基站发送的第二配置信息；
    根据所述第二配置信息对配置完整性保护功能的DRB开启完整性保护功能。
  8. 一种信息上报装置，其特征在于，应用于用户设备UE，所述装置包括：
    接收校验模块，被配置为接收开启完整性保护功能的数据承载DRB的下行数据，并对所述DRB的下行数据进行完整性校验；
    触发上报模块，被配置为若所述接收校验模块进行完整性校验失败，则触发上报完整性校验失败相关信息，所述完整性校验失败相关信息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
  9. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    第一接收模块，被配置为接收基站发送的第一配置信息，所述第一配置信息包括配置能够触发上报完整性校验失败相关信息的DRB标识；
    所述触发上报模块，被配置为：根据所述第一接收模块接收的所述第一配置信息触发上报完整性校验失败相关信息。
  10. 根据权利要求8或9所述的装置，其特征在于，所述触发上报模块包括以下一个或几个子模块：
    第一触发上报子模块，被配置为当所述UE的所述完整性校验失败发生次数累计达到第一预设次数时，触发上报所述完整性校验失败相关信息；
    第二触发上报子模块，被配置为当针对同一个DRB的所述完整性校验失败发生次数累计达到第二预设次数时，触发上报所述完整性校验失败相关信息；
    第三触发上报子模块，被配置为当在第一预设时长内所述UE的所述完整性校验失败发生次数累计达到第三预设次数时，触发上报所述完整性校验失败相关信息；
    第四触发上报子模块，被配置为当在第二预设时长内针对同一个DRB的所述完整性校验 失败发生次数累计达到第四预设次数时，触发上报所述完整性校验失败相关信息。
  11. 根据权利要求10所述的装置，其特征在于，所述第一预设次数由基站配置或由当前***约定；
    所述第二预设次数由所述基站配置，或者由所述当前***约定，或者针对每个UE配置，或者针对每个DRB配置；
    所述第三预设次数和所述第一预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置；
    所述第四预设次数和所述第二预设时长由所述基站配置，或者由所述当前***约定，或者针对每个UE配置，或者针对每个DRB配置。
  12. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    启动模块，被配置为在所述触发上报模块触发上报一次所述完整性校验失败相关信息之后，启动设置的抑制定时器；
    停止上报模块，被配置为在所述启动模块启动的所述抑制定时器超时之前，不能再上报所述完整性校验失败相关信息；
    上报模块，被配置为在所述启动模块启动的所述抑制定时器超时之后，能够再上报所述完整性校验失败相关信息。
  13. 根据权利要求12所述的装置，其特征在于，所述抑制定时器由基站配置或由当前***约定。
  14. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    第二接收模块，被配置为接收基站发送的第二配置信息；
    开启模块，被配置为根据所述第二接收模块接收的所述第二配置信息对配置完整性保护功能的DRB开启完整性保护功能，以便所述接收校验模块接收开启完整性保护功能的DRB的下行数据。
  15. 一种用户设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收开启完整性保护功能的数据承载DRB的下行数据，并对所述DRB的下行数据进行完整性校验；
    若完整性校验失败，则触发上报完整性校验失败相关信息，所述完整性校验失败相关信 息包括以下信息中的一项或多项：UE的位置信息、失败指示类型为完整性校验失败、完整性校验失败相关信息上报触发方式的指示信息和完整性校验失败发生次数。
  16. 一种计算机可读存储介质，其上存储有计算机指令，其特征在于，该指令被处理器执行时实现权利要求1-7任一项所述的信息上报方法的步骤。
PCT/CN2018/080950 2018-03-28 2018-03-28 信息上报方法及装置、用户设备和计算机可读存储介质 WO2019183852A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201880000532.1A CN108496337B (zh) 2018-03-28 2018-03-28 信息上报方法及装置、用户设备和计算机可读存储介质
PCT/CN2018/080950 WO2019183852A1 (zh) 2018-03-28 2018-03-28 信息上报方法及装置、用户设备和计算机可读存储介质
US17/017,602 US11877155B2 (en) 2018-03-28 2020-09-10 Method of performing integrity verification on downlink data of DRB and reporting information, user equipment and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/080950 WO2019183852A1 (zh) 2018-03-28 2018-03-28 信息上报方法及装置、用户设备和计算机可读存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/017,602 Continuation US11877155B2 (en) 2018-03-28 2020-09-10 Method of performing integrity verification on downlink data of DRB and reporting information, user equipment and computer readable storage medium

Publications (1)

Publication Number Publication Date
WO2019183852A1 true WO2019183852A1 (zh) 2019-10-03

Family

ID=63343574

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/080950 WO2019183852A1 (zh) 2018-03-28 2018-03-28 信息上报方法及装置、用户设备和计算机可读存储介质

Country Status (3)

Country Link
US (1) US11877155B2 (zh)
CN (1) CN108496337B (zh)
WO (1) WO2019183852A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4149133A4 (en) * 2020-05-29 2023-10-04 Vivo Mobile Communication Co., Ltd. METHOD AND DEVICE FOR PROCESSING DOWNLINK DATA AND TERMINAL DEVICE

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116319052B (zh) * 2023-04-10 2024-04-09 国网湖南省电力有限公司 一种量测数据的完整性校验方法及***、电子设备、介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102379137A (zh) * 2009-04-20 2012-03-14 华为技术有限公司 一种对消息完整性保护检查失败的处理方法、设备和***
US20170118680A1 (en) * 2015-10-21 2017-04-27 Verizon Patent And Licensing Inc. Extend long term evolution connected state coverage

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8195991B2 (en) * 2008-06-20 2012-06-05 Qualcomm Incorporated Handling of integrity check failure in a wireless communication system
CN102300335B (zh) * 2010-06-22 2016-12-21 中兴通讯股份有限公司 一种处理无线链路错误的方法及装置
WO2012060565A2 (en) * 2010-11-04 2012-05-10 Lg Electronics Inc. Method and apparatus for reconfiguring connection to base station at relay node in a wireless communication system
CN102142942B (zh) * 2011-04-01 2017-02-08 中兴通讯股份有限公司 一种中继节点***中的数据处理方法及***
WO2013101083A1 (en) * 2011-12-29 2013-07-04 Intel Corporation An apparatus for hardware accelerated runtime integrity measurement
CN107750064B (zh) * 2012-11-13 2020-08-14 华为技术有限公司 传输数据的方法、基站和用户设备
US9772252B2 (en) * 2013-02-27 2017-09-26 Ethicon, Inc. Leakage detection in a medical device
US20150281278A1 (en) * 2014-03-28 2015-10-01 Southern California Edison System For Securing Electric Power Grid Operations From Cyber-Attack
CN113645618B (zh) * 2015-08-20 2022-05-17 北京三星通信技术研究有限公司 一种ue的接入、切换和加密控制的方法与设备
EP3485574A4 (en) * 2016-07-15 2020-10-14 Chippewa Data Control LLC PROCEDURES AND ARCHITECTURE FOR CRITICAL SYSTEMS WITH THE USE OF MULTICENTRIC ORTHOGONAL TOPOLOGY AND PERVASIVE RULE-DRIVEN DATA AND CONTROL CODING
US10552640B2 (en) * 2017-03-08 2020-02-04 Quantum Corporation In-situ data verification for the cloud
KR102377138B1 (ko) * 2017-06-16 2022-03-23 삼성전자 주식회사 차세대 이동 통신 시스템에서 빠르게 주파수 측정 결과를 보고하는 방법 및 장치
CN110741701B (zh) * 2017-08-04 2022-03-11 荣耀终端有限公司 数据无线承载标识的获取方法和基站
CN108401525B (zh) * 2017-12-25 2020-12-04 北京小米移动软件有限公司 功率余量报告传输方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102379137A (zh) * 2009-04-20 2012-03-14 华为技术有限公司 一种对消息完整性保护检查失败的处理方法、设备和***
US20170118680A1 (en) * 2015-10-21 2017-04-27 Verizon Patent And Licensing Inc. Extend long term evolution connected state coverage

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
OPPO: "Discussion on DRB IP failure handling and data recovery", 3GPP TSG-RAN2#101 R2-1801799, 2 March 2018 (2018-03-02), XP051398996 *
VIVO: "Behavior on DRB IP check failure", 3GPP TSG-RAN WG2 #101 R2-1802077, 2 March 2018 (2018-03-02), XP051399825 *
VIVO: "Behavior on DRB IP check failure", 3GPP TSG-RAN WG2 MEETING #100 R2-1712755, 1 December 2017 (2017-12-01), XP051371658 *
VIVO: "Behavior on DRB IP check failure", 3GPP TSG-RAN WG2 NR AD HOC 1801 R2-1800861, 26 January 2018 (2018-01-26), XP051386385 *
ZTE CORPORATION: "DRB integrity check failure handling", 3GPP TSG-RAN WG2 MEETING #101 R2-1803967, 2 March 2018 (2018-03-02), XP051401004 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4149133A4 (en) * 2020-05-29 2023-10-04 Vivo Mobile Communication Co., Ltd. METHOD AND DEVICE FOR PROCESSING DOWNLINK DATA AND TERMINAL DEVICE

Also Published As

Publication number Publication date
CN108496337B (zh) 2021-08-17
US11877155B2 (en) 2024-01-16
CN108496337A (zh) 2018-09-04
US20200413263A1 (en) 2020-12-31

Similar Documents

Publication Publication Date Title
WO2019183857A1 (zh) 信息传输方法和信息传输装置
US10123196B2 (en) Method and device for alarm triggering
WO2019183881A1 (zh) 信息上报方法及装置和基于带宽部分的操作方法及装置
WO2018195752A1 (zh) 缓存状态的上报方法及装置
WO2016192323A1 (zh) 视频通信方法及装置
WO2020147042A1 (zh) Lbt失败的处理方法和lbt失败的处理装置
EP3136699A1 (en) Method and device for connecting external equipment
CN109314913B (zh) 接入控制限制方法及装置
US11558494B2 (en) Method and apparatus for processing data, user equipment and computer-readable storage medium
WO2016155231A1 (zh) 网络接入方法及装置
US11991691B2 (en) Method and apparatus for sending scheduling request
WO2019218366A1 (zh) 前导码和调度请求的发送方法及装置
US11832120B2 (en) Information recording method and information recording apparatus
US11910442B2 (en) Random access control method and random access control device
WO2019104542A1 (zh) 控制移动终端使用网络的方法及装置、基站和用户设备
US11877155B2 (en) Method of performing integrity verification on downlink data of DRB and reporting information, user equipment and computer readable storage medium
US11968716B2 (en) Information configuration methods, and information reporting methods, base station, and user equipment
WO2019183853A1 (zh) 信息上报、配置方法及装置、用户设备和基站
EP3806544B1 (en) Ac restriction method and device
WO2020237506A1 (zh) 信息配置方法及装置、业务处理方法及装置和基站
WO2020087440A1 (zh) 竞争的随机接入方法和装置
WO2019153236A1 (zh) 将终端与待接入的核心网建立连接的的方法、装置和***
WO2019183763A1 (zh) 信息记录方法和信息记录装置
US20210120480A1 (en) Access control (ac) barring method and apparatus
CN109451844B (zh) 功率余量报告传输方法和装置

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

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

Country of ref document: EP

Kind code of ref document: A1