WO2020147436A1 - 上报能力信息的方法、设备及系统 - Google Patents

上报能力信息的方法、设备及系统 Download PDF

Info

Publication number
WO2020147436A1
WO2020147436A1 PCT/CN2019/121713 CN2019121713W WO2020147436A1 WO 2020147436 A1 WO2020147436 A1 WO 2020147436A1 CN 2019121713 W CN2019121713 W CN 2019121713W WO 2020147436 A1 WO2020147436 A1 WO 2020147436A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
capability
rohc
cell
access network
Prior art date
Application number
PCT/CN2019/121713
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 维沃移动通信有限公司
Publication of WO2020147436A1 publication Critical patent/WO2020147436A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]

Definitions

  • the embodiments of the present disclosure relate to the field of communication technologies, and in particular, to a method, device, and system for reporting capability information.
  • a long-term evolution voice bearer Voice over Long-Term Evolution, VOLTE
  • network equipment such as a base station
  • UE user equipment
  • ROHC Robust Header Compression
  • the base station and the UE can set the ROHC configuration to the ROHC off state, thereby triggering the network equipment and the UE to stop using the ROHC protocol to transmit data.
  • the UE when the UE re-configures the ROHC, the UE needs to re-access its serving cell (that is, the cell that the UE accessed before re-configures the ROHC), that is, the UE needs to initiate random access to the base station.
  • PRACH format 4 PRACH format 4's preamble code is preamble format 4
  • this random access format initiates random access to the base station
  • the anti-noise and anti-interference ability of random access signals using PRACH format 4 is usually It is poor, so the base station may not be able to receive the random access signal, so that the UE fails to initiate random access to the base station, and thus the wireless communication link in the VOLTE network cannot be recovered.
  • the embodiments of the present disclosure provide a method, device, and system for reporting capability information, so as to solve the problem that the UE fails to initiate random access to the base station, which causes the wireless communication link in the VOLTE network to be unable to recover.
  • the embodiments of the present disclosure provide a method for reporting capability information, which is applied to a user equipment UE.
  • the method includes: acquiring preamble sequence information for the UE to access an access network device; and according to the preamble sequence Information, determine the capability information of the UE, the capability information is used to indicate whether the UE supports the robust header compression ROHC capability; the capability information is sent to the access network device.
  • the embodiments of the present disclosure provide a method for reporting capability information, which is applied to an access network device.
  • the method includes: receiving capability information from a user equipment UE, the capability information being used to indicate whether the UE supports robust header compression ROHC Capability, the capability information is determined by the UE according to the preamble sequence information, and the preamble sequence information is used for the UE to access the access network device.
  • the embodiments of the present disclosure also provide a user equipment UE.
  • the UE includes: an acquiring module, a determining module, and a sending module; the acquiring module is used to acquire preamble sequence information, and the preamble sequence information is used for UE access Network access equipment; determining module, used to determine UE capability information according to the preamble sequence information acquired by the acquiring module, the capability information is used to indicate whether the UE supports the robust header compression ROHC capability; the sending module is used to send information to the access network The device sends the capability information determined by the determining module.
  • the embodiments of the present disclosure also provide an access network device.
  • the access network device includes: a receiving module; and a receiving module for receiving capability information from a user equipment UE, the capability information being used to indicate whether the UE Supporting robust header compression ROHC capability, the capability information is determined by the UE according to the preamble sequence information, and the preamble sequence information is used for the UE to access the access network device.
  • the embodiments of the present disclosure provide a user equipment UE, including a processor, a memory, and a computer program stored on the memory and running on the processor.
  • the computer program is executed by the processor to achieve Steps of the method for reporting capability information described in the first aspect.
  • the embodiments of the present disclosure provide an access network device, including a processor, a memory, and a computer program stored on the memory and running on the processor.
  • the computer program is executed when the processor is executed. The steps of the method for reporting capability information as described in the second aspect.
  • the embodiments of the present disclosure provide a communication system that includes the user equipment UE described in the third aspect and the access network device described in the fourth aspect; or the communication system includes the communication system described in the fifth aspect.
  • the embodiments of the present disclosure provide a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the report as described in the first aspect or the second aspect is implemented.
  • the steps of the method of capability information are described in the first aspect or the second aspect.
  • the capability information of the UE can be determined, that is, whether the UE supports the ROHC capability; and then the capability information is sent to the access network device.
  • the UE can update its ROHC capability and timely report the ROHC capability to network equipment such as access network equipment.
  • the UE can determine that it does not support the ROHC capability, so that the UE and the access network equipment are closed ROHC In order to prevent the UE and the access network equipment from turning off the ROHC and causing the RLF in the VOLTE network to appear prematurely and unable to recover, thereby reducing the probability of the UE’s VOLTE call interruption timeout and automatic hanging up.
  • the probability of random access failure in the random access format such as PRACH format 4
  • Figure 1 is a schematic diagram of events and thresholds that cause wireless communication link failure and recovery
  • FIG. 2 is a schematic diagram of the architecture of a possible communication system provided by an embodiment of the present disclosure
  • FIG. 3 is one of the schematic flowcharts of a method for reporting capability information provided by an embodiment of the disclosure
  • FIG. 4 is a second schematic flowchart of a method for reporting capability information provided by an embodiment of the disclosure.
  • FIG. 5 is the third schematic flowchart of a method for reporting capability information provided by an embodiment of the disclosure.
  • FIG. 6 is a fourth schematic flowchart of a method for reporting capability information provided by an embodiment of the disclosure.
  • FIG. 7 is the fifth schematic flowchart of a method for reporting capability information provided by an embodiment of the disclosure.
  • FIG. 8 is a schematic structural diagram of a possible UE provided by an embodiment of the disclosure.
  • FIG. 9 is a schematic structural diagram of a possible access network device provided by an embodiment of the disclosure.
  • FIG. 10 is a schematic diagram of a hardware structure of a UE provided by an embodiment of the disclosure.
  • FIG. 11 is a schematic diagram of the hardware structure of an access network device provided by an embodiment of the disclosure.
  • User equipment user equipment, UE
  • ROHC Robust Header Compression
  • Reference signal receiving power Reference Signal Receiving Power, RSRP
  • SINR Signal to Interference plus Noise Ratio
  • RSSI Received Signal Strength Indication
  • TAI Tracking Area identity
  • Public Land Mobile Network Public Land Mobile Network, PLMN
  • Radio Resource Control Radio Resource Control, RRC
  • Packet Data Convergence Protocol Packet Data Convergence Protocol, PDCP
  • Radio link control Radio link Control (Radio link Control, RLC);
  • LTE Long Term Evolution
  • VOLTE Long-Term Evolution Voice Bearer
  • PRACH Physical Random Access Channel
  • Random Access Channel Random Access Channel
  • Physical Broadcast Channel Physical Broadcast Channel (Physical Broadcast Channel, PBCH);
  • CCCH Common Control Channel
  • Physical Downlink Shared Channel Physical Downlink Shared channel (Physical Downlink Shared channel, PDSCH);
  • Master Information Block Master Information Block, MIB
  • SIB System Information Blocks
  • MAC Media Access Control
  • TDD Time Division Duplexing
  • Global Positioning System Global Positioning System, GPS
  • Global Navigation Satellite System Global Navigation Satellite System, GNSS
  • WI-FI Wireless-Fidelity
  • wifi Wireless-Fidelity
  • time advanced time advanced
  • PCI Physical Cell Identifier
  • IP Internet Protocol Address
  • RTP Real-time Transport Protocol
  • Machine to Machine (Machine to Machine, M2M);
  • Enhanced Mobile Internet enhanced Mobile Broadband, eMBB
  • Ultra-high reliability and ultra-low latency communication (ultra Reliable & Row Ratency Communication, uRLLC);
  • Mobility management entity Mobility Management Entity, MME
  • Serving Gateway Serving Gateway (Serving Gateway, S-GW);
  • PDN-GW Packet Data Network Gateway
  • TRP Transmission and Reception Point
  • GSM Global System for Mobile Communication
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Station
  • WCDMA Wideband Code Division Multiple Access
  • Cloud Radio Access Network Cloud Radio Access Network, CRAN
  • Radio Access Network (RAN);
  • PCS Personal Communication Service
  • SIP Session Initiation Protocol
  • Wireless Local Loop Wireless Local Loop
  • WLL Wireless Local Loop
  • GPU Graphics Processing Unit
  • Liquid crystal display Liquid Crystal Display, LCD
  • PCI Peripheral Component Interconnect
  • Extended Industry Standard Architecture Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA);
  • OLED Organic Light-Emitting Diode
  • ROM Read-Only Memory
  • Random Access Memory Random Access Memory
  • the ROHC protocol operates at the PDCP layer, and its basic idea is to use the time correlation of the data packet header to perform compression coding, thereby reducing overhead.
  • the headers of data packets are very similar, so the ROHC protocol can significantly improve the efficiency of data transmission.
  • whether the UE supports ROHC or not is a UE capability.
  • the ROHC protocol introduces the concept of Profile.
  • the ROHC protocol has formulated a unique Profile ID (identity identifier, or identity) corresponding to each information header type.
  • the Profile ID of the IP/RTP information header type is Profile 0x0002.
  • whether the UE supports the ROHC capability refers to whether the UE supports the capability of compressing each type of information header defined in the ROHC protocol.
  • the Profile ID of each information header type corresponds to a Boolean data. The value of the Boolean data is true, indicating that the UE supports compression processing of the information header of the information header; the value of the Boolean data is false, indicating The UE does not support compression processing of the header of this header type.
  • the base station generally configures ROHC for the UE, that is, header compression.
  • the base station can issue RRC reconfiguration signaling to the UE to trigger the UE to close the ROHC configuration , And randomly access to the base station again.
  • the UE randomly accesses the base station and fails, it will cause the RLF in the VOLTE network to appear prematurely and cannot be recovered, which will cause the UE's VOLTE call interruption to time out and automatically hang up.
  • ROHC involves data integrity verification at the PDCP layer. Therefore, in order to ensure the consistency of the network (such as the access network device in the network) and the UE at the time when the ROHC is turned off, the access network device can trigger the UE to turn off the ROHC.
  • PRACH format 0 to PRACH format 4 In LTE, five random access formats from PRACH format 0 to PRACH format 4 are defined. Among them, format 0 to 3 use 839 long ZC (Zadoff-chu) sequences, and format 4 uses 139 long ZC sequences. Specifically, as shown in Table 1, the random access preamble sequence length (Random access preamble sequence length) table, the above-mentioned PRACH format 0 to PRACH format 4, the preamble (Preamble format) of the five random access formats are respectively Preamble format 0 ⁇ 4.
  • Table 1 the random access preamble sequence length (Random access preamble sequence length) table, the above-mentioned PRACH format 0 to PRACH format 4, the preamble (Preamble format) of the five random access formats are respectively Preamble format 0 ⁇ 4.
  • Preamble format (preamble) NZC 0-3 839 4 139
  • the base station needs to perform correlation operations when detecting the RACH signal (the uplink signal sent to the base station during the random access process of the UE, which may be referred to as a random access signal); the longer the ZC sequence length, the higher the detection sensitivity. Therefore, it is obvious that the anti-noise and interference ability of the signal using PRACH format 4 is obviously weaker than that of the other 4 types of random access preamble signals. It is generally believed that the detection sensitivity of PRACH format 4 is 8 decibels (Decibe, dB). In this way, the base station may not be able to monitor the RACH signal using PRACH format 4.
  • the RACH signal the uplink signal sent to the base station during the random access process of the UE, which may be referred to as a random access signal
  • the longer the ZC sequence length the higher the detection sensitivity. Therefore, it is obvious that the anti-noise and interference ability of the signal using PRACH format 4 is obviously weaker than that of the other 4 types of random access preamble signals. It is
  • the random access format of the UE is configured as PRACH format 4, compared to PRACH format 0, since the length of the ZC sequence corresponding to the preamble sequence information is shortened, the number of time-domain symbols of the RACH resource is greatly reduced, and the SINR sensitivity performance is reduced. The difference is about 7-8dB.
  • ROHC protocol can be used to transmit data in the wireless communication link configured with ROHC.
  • Figure 1 it is a schematic diagram of events and thresholds that cause wireless communication link failure and recovery.
  • Event 1 ROHC unpacking failed.
  • the base station and the UE when the base station and the UE fail to transmit data, either the base station or the UE serves as the data receiver and sends a negative acknowledgement (NACK) to the ROHC data packet sender. Based on this, the base station and the UE can turn off ROHC.
  • the UE when the UE performs ROHC shutdown, the UE needs to randomly access the base station. Since the random access signal initiated by the UE using PRACH format 4 has poor anti-noise and anti-interference capabilities, the base station may not be able to receive the random access signal, causing the UE to fail to initiate random access to the base station, thereby triggering the wireless communication link The road fails. Subsequently, because the UE fails in random access, or the cell measurement corresponding to the UE cannot meet the S criterion, the wireless communication link in the VOLTE network cannot be quickly restored.
  • NACK negative acknowledgement
  • Event 2 The physical layer synchronization signal reception strength is weak, or the uplink retransmission is too much, etc., trigger the physical layer to decide out of synchronization, and then cause the wireless communication link in the VOLTE network to fail. Subsequently, since the cell measurement corresponding to the UE cannot meet the S criterion, the wireless communication link in the VOLTE network cannot be quickly restored.
  • Event 3 In the cell search, after the UE detects a new cell that meets the S criterion, it can randomly access the cell to complete the recovery of the VOLTE network wireless communication link.
  • the trigger threshold of event 2 (K2 shown in FIG. 1) is lower than the trigger threshold of event 1 degree (K1 shown in FIG. 1).
  • the trigger threshold of event 1 degree K1 shown in FIG. 1
  • the UE In the LTE network, the UE needs to report the UE capability (such as ROHC capability) when it accesses the network for the first time (ie, the UE accesses the base station). Thereafter, the UE capability can be used as a type of UE context (Context) and stored in the core network device.
  • the base station can obtain the UE Information about the UE’s capabilities. Specifically, the base station can obtain the UE capability information of the UE in the following two ways: a) or b):
  • the base station obtains the UE context from the core network equipment, and then obtains the UE capability;
  • the base station requests the UE to report the UE capability again by sending a capability request to the UE.
  • the UE can modify its own capabilities.
  • the specific process of modifying its own capabilities includes the following steps A and B:
  • Step A The UE temporarily disconnects from the network (that is, makes the UE in an idle state) by reporting a detach message (such as detach) to the network (such as a core network device). At this time, the core network device can delete the detach signal after receiving the detach signaling.
  • a detach message such as detach
  • the core network device can delete the detach signal after receiving the detach signaling.
  • Step B The UE requests to reattach to the network (ie reattach to the core network device) by initiating random access. And report the UE capability when attaching to the network (for example, report capability information used to indicate whether the UE supports ROHC capability).
  • A/B can mean A or B
  • the "and/or” in this article is only an association relationship describing associated objects, which means that there may be three A relationship, for example, A and/or B, can mean that: A alone exists, A and B exist at the same time, and B exists alone.
  • Multiple means two or more than two.
  • first and second in the specification and claims of the present disclosure are used to distinguish different objects, rather than to describe a specific order of objects.
  • the preamble sequence information of the first type and the preamble sequence information of the second type are used to distinguish different preamble sequence information, rather than to describe the specific order of the preamble sequence information.
  • the technical solutions provided by the embodiments of the present disclosure can be applied to various communication systems, for example, 5G communication systems, future evolution systems (such as LTE communication systems, VOLTE communication systems, etc.), or multiple communication convergence systems, and so on. It can include multiple application scenarios, such as M2M, D2M, macro and micro communications, eMBB, uRLLC, and mMTC scenarios. These scenarios include but are not limited to: communication between UE and UE, or communication between network equipment and network equipment, or communication between network equipment and UE, etc.
  • the embodiments of the present disclosure can be applied to the communication between the network equipment and the UE in the VOLTE communication system, or the communication between the UE and the UE, or the communication between the network equipment and the network equipment, or the subsequent evolution version communication system related equipment Communication between.
  • Fig. 2 shows a schematic diagram of a possible structure of a communication system involved in an embodiment of the present disclosure.
  • the communication system includes at least one core network device 21 (only one is shown in Figure 2), an access network device 22 connected to each core network device 21 (only one is shown in Figure 2), And one or more UEs 23 connected to each access network device 22.
  • the aforementioned core network device 21 may include a control plane device and a user plane device.
  • the control plane equipment may include MME
  • the user plane equipment may include S-GW and PDN-GW.
  • the MME can be used for mobility management, session management, network element selection, and user bearer information storage.
  • S-GW has functions such as session management, routing and data forwarding, service quality control, charging, and information storage.
  • PDN-GW can be used for IP address allocation, session management, routing, data forwarding, quality of service control, charging, policy and charging execution, etc.
  • the aforementioned access network device 22 may be a TRP, a relay station, or an access point.
  • the access network equipment 22 is specifically a BTS in a GSM or CDMA network, and may also be an NB (NodeB) in WCDMA, or an eNB or eNodeB (evolutional NodeB) in LTE.
  • the access network device 22 may also be a wireless controller in a CRAN scenario.
  • the access network device 22 may also be a network side device in a 5G communication system or a network side device in a future evolution network, such as a base station gNG in a 5G communication system.
  • the UE 23 may be a wireless UE or a wired UE.
  • the wireless UE may be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless communication function, a computing device, or other processing connected to a wireless modem Equipment, in-vehicle equipment, wearable equipment, UE in the future 5G network or UE in the future evolved PLMN network, etc.
  • the wireless UE can communicate with one or more core networks via the RAN.
  • the wireless UE can be a mobile terminal, such as a mobile phone (or “cellular” phone) and a computer with a mobile terminal.
  • Wireless terminals can also be mobile devices, UE terminal, access terminal, wireless communication equipment, terminal unit, terminal station, mobile station (Mobile Station), mobile station (Mobile), remote station (Remote Station), remote station, remote terminal (Remote terminal), subscriber unit ( Subscriber Unit, Subscriber Station, User Agent, Terminal Device, etc.
  • FIG. 2 shows that the UE is a mobile phone as an example.
  • the method for reporting capability information provided by the embodiment of the present disclosure will be described in detail below with reference to the flowchart of the method for reporting capability information shown in FIG. 3.
  • the logical sequence of the method for reporting capability information provided by the embodiments of the present disclosure is shown in the method flowchart, in some cases, the steps shown or described may be performed in a different order.
  • the method for reporting capability information shown in FIG. 3 may include step 301 to step 303:
  • Step 301 The UE obtains preamble sequence information, which is used by the UE to access the access network equipment.
  • the preamble sequence information may be preamble sequence information indicating one of the above PRACH format 0 to PRACH format 3.
  • the UE may obtain the preamble sequence information through the system broadcast it receives.
  • the preamble sequence information is the preamble sequence information used by the current UE to initiate random access to the access network device.
  • the UE may receive system messages broadcast by an access network device (such as a base station).
  • the system message includes the main system message MIB transmitted in the PBCH, and other system messages (SIB) transmitted in the CCCH through the PDSCH, specifically including system information block 1 (SIB-1), system information block 2 (SIB- 2)...System Information Block N (SIB-N) and so on.
  • SIB-1 system information block 1
  • SIB- 2 system information block 2
  • SIB-N System Information Block N
  • the preamble sequence information appears in SIB-2
  • the UE reads the SIB-2 to obtain the current preamble sequence information.
  • the domain name of the preamble sequence information in SIB-2 is called "prach-ConfigIndex", and its format in SIB-2 is as follows:
  • the protocol defines that when the value of "prach-ConfigIndex" is 48-57, it means that the random access format indicated by the preamble sequence information is PRACH format 4; in other cases, the preamble sequence The format is PRACH format 0-3.
  • the value of the aforementioned "prach-ConfigIndex" is 53, indicating that the random access format indicated by the current preamble sequence information is PRACH format 4.
  • Step 302 The UE determines the capability information of the UE according to the preamble sequence information, and the capability information is used to indicate whether the UE supports ROHC capability.
  • the access network equipment successfully receives the random access signal.
  • the probability is high, so the probability of successful random access initiated by the UE using any random access format in PRACH format 0 to PRACH format 3 is high.
  • the access network device may not be able to receive the random access signal, so that the UE initiates random access to the access network device. Access failure, that is, the random access initiated by the UE using the random access format of PRACH format 4 has a low probability of success.
  • the UE when the preamble sequence information indicates any one of PRACH format 0 to PRACH format 3, the UE may determine that it supports ROHC capability; that is, the aforementioned UE capability information may be used to indicate the UE Support ROHC capability.
  • the UE may determine that it does not support ROHC capability, that is, the aforementioned UE capability information may be used to indicate that the UE does not support ROHC capability.
  • the UE can determine that it supports the ROHC capability.
  • Step 303 The UE sends the capability information of the UE to the access network device.
  • the UE after the UE re-determines its ROHC capabilities and other capabilities, it can trigger the reporting of the UE capabilities to the network side. Specifically, the UE may send its capability information to the access network device.
  • the access network device can receive the aforementioned UE capability information from the UE.
  • the access network device may perform ROHC configuration on the UE according to the capability information of the UE, such as triggering the UE to turn off ROHC.
  • the UE and the access network equipment and other network equipment will not use the ROHC protocol to transmit data, that is, the UE and the access network equipment are in the ROHC state closed .
  • the access network equipment will not trigger the UE to execute the process of turning off ROHC, that is, the UE does not need to reconfigure ROHC to turn off ROHC, so the UE does not need to go offline and initiate random access, thus avoiding random access by the UE Failure causes the RLF in the VOLTE network to appear prematurely and cannot be recovered, thereby reducing the problem of UE's VOLTE call interruption, timeout, and automatic hang-up.
  • the method for reporting capability information can obtain preamble sequence information, and determine the capability information of the UE based on the preamble sequence information, that is, determine whether the UE supports ROHC capability; Send the capability information.
  • the UE can update its ROHC capability and timely report the ROHC capability to network equipment such as access network equipment.
  • the UE can determine that it does not support the ROHC capability, so that the UE and the access network equipment are closed ROHC In order to prevent the UE and the access network equipment from turning off the ROHC and causing the RLF in the VOLTE network to appear prematurely and unable to recover, thereby reducing the probability of the UE’s VOLTE call interruption timeout and automatic hanging up.
  • the probability of random access failure in the random access format such as PRACH format 4
  • the method for reporting capability information may further include the following steps 401 to 403 after the above S303:
  • Step 401 The access network device determines ROHC configuration information according to the capability information of the UE.
  • the access network device may receive the capability information from the UE.
  • the capability information of the UE can be used to trigger the access network device to perform ROHC configuration on the UE. Specifically, after the access network device receives the capability information from the UE, it can generate the aforementioned ROHC configuration information according to the capability information to trigger the UE to modify the ROHC configuration.
  • the ROHC configuration information may be used to instruct the UE to enable ROHC.
  • the ROHC configuration information can be used to instruct the UE to turn off ROHC.
  • Step 402 The access network device sends ROHC configuration information to the UE.
  • the UE can receive the ROHC configuration information from the UE.
  • Step 403 The UE configures the communication link of the UE according to the ROHC configuration information.
  • the UE when the ROHC configuration information instructs the UE to enable ROHC, the UE can use the ROHC protocol to transmit data with network equipment such as access network equipment. Specifically, the UE may configure its ROHC communication link to use the ROHC protocol to transmit data.
  • the UE may receive ROHC configuration information from the access network device, and the ROHC configuration information is determined according to the capability information, so the UE may use the ROHC configuration information to configure the UE
  • the communication link conforms to the ROHC capability of the UE.
  • the ROHC configuration information may instruct the UE to turn off ROHC. Therefore, even if the communication quality of the subsequent wireless communication link is poor, the random access initiated after the UE turns off the ROHC again will not fail.
  • step 302 may be implemented through step 302a or step 302b:
  • Step 302a When the preamble sequence information is the first type of preamble sequence information, the UE determines that the capability information of the UE is used to indicate that the UE supports ROHC capability.
  • the foregoing first type of preamble sequence information may be preamble sequence information indicating one random access format in the foregoing PRACH format 0 to PRACH format 3.
  • Step 302b When the preamble sequence information is the second type of preamble sequence information, the UE determines the capability information of the UE according to the auxiliary information.
  • the aforementioned second type of preamble sequence information may be preamble sequence information indicating the aforementioned PRACH format 4, a random access format.
  • the UE may first determine whether the currently acquired preamble sequence information is the first type of preamble sequence information or the second type of preamble sequence information.
  • auxiliary information in the embodiments of the present disclosure may be information used to indicate the network environment where the UE is located.
  • the network environment where the UE is located is better, indicating that the UE can support ROHC capabilities and successfully transmit data through the ROHC protocol, such as successfully transmitting data compressed through the ROHC protocol.
  • the UE is in a poor network environment, indicating that the UE may not support ROHC capability. At this time, the UE does not need to successfully transmit data through the ROHC protocol to avoid failure in transmitting data compressed through the ROHC protocol.
  • step 302b may be implemented through step 302b-1 or step 302b-2:
  • Step 302b-1 When the auxiliary information meets the first condition, the UE determines that the capability information of the UE is used to indicate that the UE supports ROHC capability.
  • Step 302b-2 When the auxiliary information does not meet the first condition, the UE determines that the capability information of the UE is used to indicate that the UE does not support ROHC capability.
  • the auxiliary information satisfies the first condition, indicating that the UE is in a better network environment, and the communication quality of the UE's wireless communication link may be better at this time; otherwise, the auxiliary information does not meet the first condition, indicating that the UE is located The network environment is poor, and at this time, the communication quality of the wireless communication link of the UE may be poor.
  • the UE may first determine whether the currently acquired auxiliary information satisfies the first condition.
  • the UE determines that it supports ROHC capability, so that the UE and the access network equipment are in a ROHC-enabled state.
  • the preamble sequence information is the second type of preamble sequence information, that is, the probability of random access failure in the random access format indicated by the preamble sequence information is high
  • the UE determines that it does not support the ROHC capability, so that the UE and the access network equipment are in a state where the ROHC is turned off.
  • step 302b-1 may be specifically implemented by the following step 302b-1a:
  • Step 302b-1a When the first information satisfies the first condition corresponding to the first information, the UE determines that the capability information of the UE is used to indicate that the UE supports ROHC capability, and the first information is any piece of information in the auxiliary information.
  • step 302b-2 may be specifically implemented by the following step 302b-2a:
  • Steps 302b-2a In the case that each item of the auxiliary information does not satisfy the corresponding first condition, the UE determines that the capability information of the UE is used to indicate that the UE does not support the ROHC capability.
  • step 302b-1 may be specifically implemented by the following steps 302b-1b:
  • Steps 302b-1b When the second information satisfies the first condition corresponding to the second information, the UE determines that the capability information of the UE is used to indicate that the UE supports ROHC capability, and the second information is each piece of information in the auxiliary information.
  • step 302b-2 may be specifically implemented through the following steps 302b-2b:
  • Steps 302b-2b When any item of auxiliary information does not satisfy the corresponding first condition, the UE determines that the capability information of the UE is used to indicate that the UE does not support ROHC capability.
  • the method for reporting capability information provided in the embodiments of the present disclosure may be applied to the following scenario 1 and/or scenario 2:
  • Scenario 1 The UE is in a disconnected state.
  • the UE being in a disconnected state may refer to a state where the UE is camped on a certain cell.
  • Scenario 2 The UE is in a connected state.
  • the UE being in the connected state may refer to the state where the UE is accessing a certain cell.
  • the auxiliary information may include at least one of the following auxiliary information 1 to auxiliary information 4.
  • the first condition may include at least one of the following conditions 1 to 4. Among them, one item of auxiliary information corresponds to one first condition.
  • the first cell is the cell where the UE resides.
  • the current network environment of the UE may be the network coverage of the current location of the UE.
  • the auxiliary information 2 the RSRQ of the first cell; correspondingly, the first condition corresponding to the auxiliary information 2 is condition 2: the RSRQ of the first cell is greater than or equal to the second threshold.
  • the auxiliary information 4 the RSSI of the first cell; correspondingly, the first condition corresponding to the auxiliary information 4 is condition 4: the RSSI of the first cell is greater than or equal to the fourth threshold.
  • the downlink RSRP, RSRQ, SINR, and RSSI information of the cell where the UE resides may be obtained when the UE performs cell measurement and selection, or may be a direct measurement result defined by the physical layer according to the protocol. It can also be an indirect measurement result after filtering at the RRC layer.
  • the RSRP of the current UE camping cell (such as the first cell) measured by the UE is greater than or equal to the first threshold, indicating that the UE’s current camping cell or serving cell’s downlink signal strength is relatively strong, namely The camping cell or serving cell is under normal coverage.
  • the auxiliary information 1 satisfies the condition 1, the UE may determine that its capability information is used to indicate that the UE supports ROHC capability.
  • the UE measures that the RSRP of the current UE camping cell (such as the first cell) is less than the first threshold it means that the UE’s current camping cell or the downlink signal strength of the serving cell is weak, that is, the camping cell or The serving cell is in weak coverage.
  • the auxiliary information 1 does not satisfy the condition 1, the UE may determine that its capability information is used to indicate that it does not support the ROHC capability.
  • the downlink RSRQ, SINR or RSSI of the cell where the UE resides satisfies the corresponding first condition reference may be made to the above related description of the downlink RSRP of the cell where the UE resides satisfies the first condition, here No longer.
  • the values of the first threshold, the second threshold, the third threshold, and the fourth threshold may be determined according to actual use requirements, and the embodiment of the present disclosure does not limit it.
  • the UE when the auxiliary information includes multiple items of the aforementioned auxiliary information 1 to auxiliary information 4, the UE only needs to determine that any one of auxiliary information 1 to auxiliary information 4 satisfies the corresponding
  • the first condition can determine that the overall auxiliary information satisfies the overall first condition, that is, the UE can determine its capability information to indicate that the UE supports ROHC capability.
  • the UE may perform step 302b-1a in the foregoing embodiment to determine that the UE supports ROHC capability; or, the UE may perform step 302b-2a in the foregoing embodiment to determine that the UE does not support ROHC capability.
  • the above-mentioned first information may be any one of auxiliary information 1 to auxiliary information 4.
  • auxiliary information may further include at least one of the following auxiliary information 5 to auxiliary information 7.
  • the first condition may further include at least one of the following conditions 5 to 7.
  • one item of auxiliary information corresponds to one first condition.
  • the second cell is the same frequency neighboring cell of the first cell.
  • the first cell and the second cell are in the same frequency networking, that is, the first cell and the second cell use the same frequency.
  • multiple same-frequency neighboring cells may exist in the first cell, that is, multiple second cells may exist.
  • the UE may determine whether its RSRP is less than or equal to the fifth threshold for each second cell of the multiple second cells.
  • the RSRP, RSRQ, and SINR of the second cell can be obtained when the UE performs cell measurement and selection, it can also be the direct measurement result defined by the physical layer according to the protocol, or the indirect measurement result filtered at the RRC layer .
  • the RSRP of the current co-frequency neighboring cell (ie the second cell) measured by the UE is less than or equal to the fifth threshold, indicating that the signal strength of the downlink signal of the co-frequency neighboring cell is relatively strong, that is, the co-frequency neighboring cell
  • the interference intensity to the UE is relatively strong.
  • the UE can determine that its capability information is used to indicate that it supports ROHC capability.
  • the UE measured that the RSRP of the current co-frequency neighboring cell (ie the second cell) is greater than the fifth threshold, indicating that the signal strength of the downlink signal of the co-frequency neighboring cell is weak, that is, the interference strength of the co-frequency neighboring cell to the UE is relatively weak weak.
  • the UE may determine that its capability information is used to indicate that it does not support the ROHC capability.
  • the values of the fifth threshold, the sixth threshold, and the seventh threshold may be determined according to actual use requirements, and the embodiment of the present disclosure does not limit it.
  • the UE in the case where the auxiliary information includes multiple items of the aforementioned auxiliary information 5 to auxiliary information 7, the UE only needs to determine that any one of auxiliary information 5 to auxiliary information 7 satisfies the corresponding
  • the first condition can determine that the overall auxiliary information satisfies the overall first condition, that is, the UE can determine its capability information to indicate that the UE supports ROHC capability.
  • the UE may perform step 302b-1a in the foregoing embodiment to determine that the UE supports ROHC capability; or, the UE may perform step 302b-2a in the foregoing embodiment to determine that the UE does not support ROHC capability.
  • the above-mentioned first information is any one of auxiliary information 5 to auxiliary information 7.
  • the auxiliary information may further include at least one of the following auxiliary information 8 to auxiliary information 11.
  • the first condition may include at least one of the following conditions 8 to 11.
  • one item of auxiliary information corresponds to one first condition.
  • the auxiliary information 8 the geographic location information of the UE; correspondingly, the first condition corresponding to the auxiliary information 8 is condition 8: the location indicated by the geographic location information of the UE is located in a preset area.
  • the geographic location information is used to indicate the location of the UE when the ROHC communication link configured for the UE fails to transmit data.
  • the above-mentioned geographic location information may be the UE's address location information determined through satellite positioning systems (including GPS, GNSS, BDS, etc.) or other positioning technologies; other positioning technologies, including but not limited to wifi positioning, wireless communication base stations Positioning, etc.
  • the UE obtains the address location information of the UE based on the above-mentioned positioning technology, and the application layer of the UE feeds it back to the communication module of the UE.
  • the foregoing preset area may be determined by prior statistical information of the occurrence probability of low RSRP (ie weak coverage) in an area.
  • the foregoing preset area has a low RSRP (ie weak coverage) occurrence probability. Area.
  • the auxiliary information 8 satisfies the condition 8
  • the location indicated by the current UE address location information is within the preset area, indicating that the low RSRP occurrence probability of the current UE location is low, and the UE determines its capability information with Yu indicates that it supports ROHC capabilities.
  • the auxiliary information 8 does not meet the condition 8
  • the location indicated by the current UE address location information is outside the preset area, indicating that the low RSRP occurrence probability of the current UE location is high, and the UE determines its capability information Used to indicate that it does not support ROHC capability.
  • the auxiliary information 10, the PLMN identity received by the UE; correspondingly, the first condition corresponding to the auxiliary information 10 is that the condition 10 is: the PLMN identity received by the UE is the same as the preset PLMN identity.
  • the TAI, the PLMN identity, and the cell identity of the first cell received by the UE may be obtained by the UE when the ROHC communication link configured by the UE fails to transmit data. That is, these identifiers can be used to indicate the location of the UE when the ROHC communication link configured by the UE fails to transmit data.
  • the TAI ie “trackingAreaCode”
  • the PLMN identity ie PLMN identity
  • the cell identity of the first cell such as cell identity or PCI
  • SIB-1 and/or MIB this information can appear in SIB-1 and/or MIB, and its specific format in SIB-1 is:
  • the value of the "plmn-Identity" field in the specific format of the above SIB-1 is the TAI received by the UE;
  • the value of the "trackingAreaCode” field is the PLMN identity received by the UE;
  • the value of the "cellIdentity” field is Is the cell identity of the first cell received by the UE.
  • the TAI, PLMN identity, or cell identity corresponding to an area with a higher probability of occurrence of low RSRP (ie, weak coverage) may be determined according to prior statistical information of the occurrence probability of low RSRP (ie, weak coverage) in an area.
  • these TAI, PLMN identity or cell identity are respectively used as the aforementioned preset TAI, preset PLMN identity and preset cell identity.
  • the current TAI received by the UE is the same as the preset TAI, indicating that the low RSRP occurrence probability of the current UE location is low, and the UE can determine its capability information to indicate that it supports ROHC capability.
  • the auxiliary information 9 satisfies the condition 9.
  • the current TAI received by the UE is different from the preset TAI, indicating that the low RSRP occurrence probability of the current UE location is high, and the UE can determine its capability information to indicate that it does not support ROHC capability.
  • the auxiliary information 9 does not satisfy the condition 9.
  • the UE determines that one or more pieces of auxiliary information from the auxiliary information 9 to 11 are obtained.
  • the UE can finally determine its capability information to indicate that the UE supports ROHC capability.
  • auxiliary information includes the auxiliary information 8 to the auxiliary information 11
  • the UE determines that the auxiliary information 8 satisfies the condition 8, and/or, each item of the auxiliary information 9 to the auxiliary information 11 satisfies the condition 9.
  • the UE can determine its capability information to indicate that the UE supports ROHC capability.
  • the UE determines that the auxiliary information 8 does not meet the condition 8, and each item of the auxiliary information 9 to the auxiliary information 11 does not meet the corresponding conditions in the conditions 9 to 11, the UE can determine that its capability information is used to indicate the UE Does not support ROHC capability.
  • the auxiliary information when the auxiliary information includes the auxiliary information 8 to the auxiliary information 11, if the UE determines that the auxiliary information 8 satisfies the condition 8, and each item of the auxiliary information 9 to the auxiliary information 11 is separately When the corresponding conditions in Condition 9 to Condition 11 are met, the UE can determine its capability information to indicate that the UE supports ROHC capability.
  • the UE determines that the auxiliary information 8 does not meet the condition 8, and/or each item of the auxiliary information 9 to the auxiliary information 11 does not meet the corresponding conditions in the conditions 9 to 11, the UE can determine its capability information To indicate that the UE does not support ROHC capability.
  • the auxiliary information includes at least one of the auxiliary information 8 to the auxiliary information 11
  • the first The information is any item of information from auxiliary information 8 to auxiliary information 11
  • the second information is each item of information from auxiliary information 8 to auxiliary information 11.
  • the auxiliary information includes at least one item from the auxiliary information 1 to the auxiliary information 11, when the steps 302b-1a, 302b-1b, 302b-2a, or 302b-2b are performed, the first The information is any item of information from auxiliary information 8 to auxiliary information 11, and the second information is each item of information from auxiliary information 8 to auxiliary information 11.
  • the UE may determine to obtain one capability information of the UE (denoted as capability information 1) through at least one of auxiliary information 1 to auxiliary information 4, and determine to obtain the UE through at least one item of auxiliary information 5 to auxiliary information 7.
  • a capability information of the UE (denoted as capability information 2), and one capability information of the UE (denoted as capability information 3) is determined by determining at least one of auxiliary information 8 to auxiliary information 11.
  • the auxiliary information includes multiple pieces of information in the auxiliary information 1 to 11
  • the capability information 1, the capability information 2, and the capability information 3 indicates that the UE supports ROHC capability
  • the UE finally determines that the UE supports ROHC capability.
  • the UE determines that the UE supports the ROHC capability.
  • the auxiliary information includes multiple pieces of information in the aforementioned auxiliary information 1 to 11
  • the UE if each of the aforementioned capability information 1, capability information 2 and capability information 3 indicates that the UE supports ROHC capability, then The UE finally determines that the UE supports ROHC capability.
  • the UE if any one of the aforementioned capability information 1, capability information 2 and capability information 3 indicates that the UE does not have ROHC capability, the UE finally determines that the UE does not support ROHC capability.
  • the auxiliary information may further include the following auxiliary information 12 to auxiliary information 15 At least one:
  • the first condition may include at least one of the following conditions 12 to 15. Among them, one item of auxiliary information corresponds to one first condition.
  • the auxiliary information 12 the number of retransmissions of the physical layer on the ROHC communication link; correspondingly, the first condition corresponding to the auxiliary information 12 is condition 12: the number of retransmissions of the physical layer on the ROHC communication link is less than or equal to the eighth threshold.
  • the physical layer in the "physical layer on the ROHC communication link” may be the PHY on the ROHC communication link or the MAC layer on the ROHC communication link.
  • the auxiliary information 13 the number of lost packets on the physical layer on the ROHC communication link; correspondingly, the first condition corresponding to the auxiliary information 13 is condition 13: the number of lost packets on the physical layer on the ROHC communication link is less than or equal to the ninth threshold.
  • Auxiliary information 14 the number of ROHC radio bearers on the RLC layer on the ROHC communication link; correspondingly, the first condition corresponding to the auxiliary information 14 is condition 14: ROHC radio bearers on the RLC layer on the ROHC communication link The number of packets is less than or equal to the tenth threshold.
  • the ROHC radio bearer is the voice bearer.
  • Auxiliary information 15 the number of ROHC radio bearers on the PDCP layer on the ROHC communication link; correspondingly, the first condition corresponding to the auxiliary information 15 is condition 15: ROHC radio bearers on the PDCP layer on the ROHC communication link The number of packets is less than or equal to the eleventh threshold.
  • any one of the auxiliary information 12 to the auxiliary information 15 may be used for the UE to determine the communication quality of the wireless communication link currently including the ROHC radio bearer.
  • the auxiliary information 12 satisfies the condition 12, that is, the number of retransmissions of the physical layer on the ROHC communication link is less than or equal to the eighth threshold within a certain limited period of time.
  • the link communication quality of the ROHC radio bearer is good.
  • the UE can determine its capability information to indicate that it supports ROHC capability.
  • the auxiliary information 12 does not satisfy the condition 12, that is, the number of retransmissions of the physical layer on the ROHC communication link is greater than the eighth threshold, indicating that the link communication quality of the ROHC radio bearer is poor.
  • the UE can determine its capability information to indicate that it does not support ROHC capability.
  • auxiliary information 13, the auxiliary information 14, or the auxiliary information 15 meets the corresponding first condition
  • the values of the eighth threshold, the ninth threshold, the tenth threshold, and the eleventh threshold may be determined according to actual usage requirements, and the embodiments of the present disclosure are not limited.
  • the UE performs step 302b-1a, step 302b-1b, step 302b-2a or step
  • the above-mentioned first information is any item of auxiliary information 12-15
  • the second information is each item of auxiliary information 12-15.
  • the capability information of the UE determined by the UE is recorded as capability information 4.
  • auxiliary information includes the aforementioned auxiliary information 1 to auxiliary information 15
  • the UE determines that the UE supports ROHC capability if any one of the aforementioned capability information 1 to capability information 4 indicates that the UE supports ROHC capability.
  • the UE determines that the UE supports ROHC capability if each item in the foregoing capability information 1 to capability information 4 indicates that the UE does not have ROHC capability.
  • the auxiliary information includes the aforementioned auxiliary information 1 to auxiliary information 15
  • the UE if each item of the aforementioned capability information 1 to capability information 4 indicates that the UE supports ROHC capability, the UE finally determines that the UE supports ROHC capability. Conversely, if any one of the foregoing capability information 1 to capability information 4 indicates that the UE does not have ROHC capability, the UE finally determines that the UE supports ROHC capability.
  • the method for reporting capability information can be used to determine whether the UE supports ROHC capability according to one or more items of auxiliary information, so even if the UE can only obtain auxiliary information
  • the UE can also determine the capability information of the UE based on this information.
  • the UE since the UE can determine the capability information of the UE in combination with multiple pieces of information in the auxiliary information, it is beneficial to improve the accuracy of the determined capability information.
  • the UE may initiate a random access procedure.
  • the foregoing method for reporting capability information may further include steps 601 to 603 before step 303, and corresponding step 303 can be implemented through step 604:
  • Step 601 The UE sends a random access request to the access network device.
  • the aforementioned random access request includes the preamble sequence information obtained by the UE, that is, the UE initiates random access using the random access format indicated by the preamble sequence information.
  • the access network device can receive a random access request from the UE.
  • Step 602 The UE sends an RRC connection request message to the access network device.
  • the RRC connection request message is used to request the establishment of an RRC connection.
  • the access network device can receive the RRC connection request message from the UE.
  • the UE may perform the foregoing step 601.
  • the access network device can obtain the capability information of the UE through the following Embodiment 1 and Embodiment 2:
  • the reason in the RRC connection establishment request message is "Cause "Field, can be
  • the UE has a business that needs to perform data transmission
  • the RRC connection request initiated by the UE is not limited to call-related. This is because when the UE is in the unconnected state, the UE initiates a call or the network paging the UE, and the UE needs to initiate an RRC connection request, which makes the UE change from the unconnected state to the connected state, which can generate subsequent access network equipment The process of requesting the UE to report its capability information. When the UE is in the connected state, the UE initiates a call or the network paging the UE, it will not trigger the subsequent access network equipment to request the UE to report its capability information, that is, the call will not trigger the re-reporting of the UE capability. Therefore, it needs to be connected in RRC. Upon establishment, the updated UE capability information is reported.
  • the network obtains the UE context from the core network device to obtain the UE capability information
  • the UE instead of obtaining the UE capability information from the UE, the UE needs to initiate a detachment to the core network device through the access network device before initiating random access Requesting (detach) to detach the UE means requesting the core network device to release the UE; after that, the "Cause" field in the RRC connection establishment request message initiated by the UE can only be "UE attached".
  • the core network device Since the core network device will delete its stored UE context when the core network device is unattached to the UE, the re-establishment of the RRC connection request for the UE to attach to the core network device will trigger the access network device to request the UE’s capability information to reconnect The UE attaches to the core network equipment.
  • the UE may try to perform Embodiment 1 first to observe whether the network (that is, the access network device in the network) will trigger the UE capability report, and then determine whether to further perform Embodiment 2.
  • Step 603 The access network device sends first indication information to the UE.
  • the first indication information is used to instruct the UE to report the capability information of the UE to the access network device.
  • the UE may receive the foregoing first indication information from the access network device.
  • Step 604 The UE sends the capability information of the UE to the access network device according to the first indication information.
  • the first indication information instructs the UE to send the capability information of the UE.
  • the UE may request the UE's capability information from the access network device in the network. For example, when the access network device sends the first indication information to the UE, The access network device sends the capability information of the UE so that the UE can learn whether the UE supports the ROHC capability.
  • the method for reporting capability information provided by an embodiment of the present disclosure may further include step 701 before step 602 in scenario 2, specifically before step 601:
  • Step 701 When the UE is in the first state, the UE controls the UE to switch to the second state.
  • the first state is a state of being in a connected state and transmitting a preset type of service
  • the second state is a state of being in an idle state.
  • the UE controls the UE to switch to the second state, which can make the UE temporarily offline.
  • the foregoing preset type of service may be a VOLTE voice service or other services that need to be guaranteed for continuity.
  • the UE is temporarily offline, which can be divided into the following two situations:
  • the access network device When the UE is in the second state, the access network device will not trigger the UE to send capability information when the UE is in the connected state, while in the UE voice state, the UE updates the UE's capability information by detaching and attaching from the core network device It will cause the UE's VOLTE call to hang up automatically, so the UE is no longer suitable for sending the UE's capability information in the above-mentioned embodiment 2.
  • the UE when the UE sends the capability information of the UE in the above-mentioned embodiment 1, the UE is temporarily offline, enters the idle state without camping on the cell (ie idle state), and then re-establishes the RRC connection to trigger the access network
  • the device issues a UE capability report request (that is, the aforementioned first indication information), so that the access network device can obtain the UE capability information from the UE.
  • the time for the UE to be offline should be exactly equal to the set time of the T311 timer, so as to ensure that the access network equipment and the UE have a consistent understanding of the RLF process.
  • the cost of switching from the connected state to the idle state by the UE that is, re-random access after temporarily disconnecting from the network, may cause the UE to be in a silent state for about 1 second.
  • the UE can send the UE's capability information to the access network device through the above-mentioned Embodiment 1 or Embodiment 2 to report its ROHC capability to the network.
  • the UE can temporarily go offline, and after entering the idle state, the RRC connection is re-established, which triggers the access network device to issue a UE capability report request (such as the first indication information), and the UE goes offline.
  • the time should be exactly equal to the set time of the T311 timer to ensure that the network and the UE have a consistent understanding of the RLF process.
  • the UE can determine to update the capability information of the UE by detaching and attaching from the core network device, but the cost is the jitter of the data connection.
  • the foregoing step 701 may further include the step 702:
  • Step 702 When the UE is in the third state, the UE sends a detach request message to the access network device.
  • the detach request message is used to request the UE to detach from the core network device.
  • the third state is a state in which it is in an idle state or in a connected state and the preset type of service is not transmitted.
  • the above detach information is detach.
  • the access network device may receive the aforementioned detach request message from the UE, and trigger the core network device to detach the UE according to the detach request message.
  • the subsequent RRC request message of the UE can be used to request the access network device to trigger the reattachment of the UE to the core network device.
  • the UE can report to the network side in different ways according to whether it is in a connected state or a non-connected state, and whether the UE is performing a preset type of service.
  • the capability information of the UE so that the access network device can update the capability information of the UE while having a small impact on the service performed by the UE.
  • FIG. 8 shows a schematic diagram of a possible structure of a UE involved in an embodiment of the present disclosure.
  • the UE 80 includes an acquisition module 801, a determination module 802, and a sending module 803;
  • the acquisition module 801 is used to acquire preamble sequence information, which is used by the UE to access the access network equipment; and the determination module 802, It is used to determine the capability information of the UE according to the preamble sequence information obtained by the obtaining module 801, and the capability information is used to indicate whether the UE supports ROHC capability;
  • the sending module 803 is used to send the capability information determined by the determining module 802 to the access network device.
  • the determining module 802 is specifically configured to determine the capability information to indicate that the UE supports ROHC capability when the preamble sequence information is the first type of preamble sequence information.
  • the determining module 802 is specifically configured to determine the capability information of the UE according to the auxiliary information when the preamble sequence information is the second type of preamble sequence information.
  • the determining module 802 is specifically configured to determine that the capability information of the UE is used to indicate that the UE supports ROHC capability when the auxiliary information meets the first condition.
  • the auxiliary information includes at least one of the following: RSRP of the first cell, RSRQ of the first cell, SINR of the first cell, and RSSI of the first cell; where the first cell is a cell where the UE resides.
  • the first condition includes at least one of the following: RSRP of the first cell is greater than or equal to a first threshold, RSRQ of the first cell is greater than or equal to a second threshold, SINR of the first cell is greater than or equal to a third threshold, and The RSSI of a cell is greater than or equal to the fourth threshold.
  • the auxiliary information further includes at least one of the following: RSRP of the second cell, RSRQ of the second cell, and SINR of the second cell; where the second cell is a co-frequency neighboring cell of the first cell.
  • the first condition further includes at least one of the following: the RSRP of the second cell is less than or equal to the fifth threshold, the RSRQ of the second cell is less than or equal to the sixth threshold, and the SINR of the second cell is less than or equal to the seventh threshold.
  • the auxiliary information further includes at least one of the following: geographic location information of the UE, TAI received by the UE, PLMN identification received by the UE, and cell identification of the first cell received by the UE; where the geographic location information is used to indicate The location of the UE when the ROHC communication link configured by the UE fails to transmit data.
  • the first condition further includes at least one of the following: the location indicated by the geographic location information is located in a preset area, the TAI is the same as the preset TAI, the PLMN identity is the same as the preset PLMN identity, and the cell identity is the same as the preset cell identity. .
  • the auxiliary information when the UE is in a connected state and the UE is configured with an ROHC communication link, the auxiliary information further includes at least one of the following: the number of retransmissions of the physical layer on the ROHC communication link, the number of lost packets at the physical layer,
  • the radio link on the ROHC communication link controls the number of lost packets of the ROHC radio bearer on the RLC layer, and the number of lost packets of the ROHC radio bearer on the PDCP layer of the packet data convergence protocol on the ROHC communication link.
  • the first condition further includes at least one of the following: the number of retransmissions at the physical layer is less than or equal to the eighth threshold, the number of lost packets at the physical layer is less than or equal to the ninth threshold, and the number of lost packets on the ROHC radio bearer on the RLC layer Less than or equal to the tenth threshold, and the number of lost packets of the ROHC radio bearer on the PDCP layer is less than or equal to the eleventh threshold.
  • the determining module 802 is specifically configured to determine that the capability information is used to indicate that the UE supports ROHC capability when the first information satisfies the first condition corresponding to the first information, and the first information is any one of the auxiliary information. Item information.
  • the determining module 802 is specifically configured to determine that the capability information is used to indicate that the UE supports ROHC capability when the second information meets the first condition corresponding to the second information, and the second information is each item in the auxiliary information information.
  • the UE 80 further includes: a first receiving module: a sending module 803, which is also used to send an RRC connection request message to the access network device before sending the capability information to the access network device, and the RRC connection request message is used to request establishment RRC connection; the first receiving module, used to receive the first indication information from the access network equipment, the first indication information used to instruct the UE to report capability information to the access network equipment; the sending module 803, specifically used to according to the first indication information , Send capability information to the access network device.
  • a first receiving module a sending module 803, which is also used to send an RRC connection request message to the access network device before sending the capability information to the access network device, and the RRC connection request message is used to request establishment RRC connection
  • the first receiving module used to receive the first indication information from the access network equipment, the first indication information used to instruct the UE to report capability information to the access network equipment
  • the sending module 803, specifically used to according to the first indication information Send capability information to the access network device.
  • the UE 80 further includes: a switching module; the switching module is configured to control the UE to switch to the second state when the UE is in the first state before the sending module 803 sends the RRC connection request message to the access network device,
  • the first state is a state of being in a connected state and transmitting a preset type of service
  • the second state is a state of being in an idle state.
  • the sending module 803 is further configured to send a detach request message to the access network device when the UE is in the third state before sending the RRC connection request message to the access network device.
  • the detach request message is used for Request the UE to detach from the core network device; wherein, the third state is in an idle state, or in a connected state, and does not transmit a preset type of service.
  • the UE 80 also includes: a second receiving module and a configuration module; the second receiving module is configured to receive ROHC configuration information from the access network device after the sending module 803 sends capability information to the access network device, and ROHC configuration information It is determined according to the capability information; the configuration module is used to configure the communication link of the UE according to the ROHC configuration information received by the receiving module.
  • the UE provided in the embodiments of the present disclosure can implement each process implemented by the UE in the foregoing method embodiments. To avoid repetition, the specific description will not be repeated here.
  • the embodiments of the present disclosure provide a UE.
  • the UE can obtain preamble sequence information and determine the capability information of the UE based on the preamble sequence information, that is, determine whether the UE supports ROHC capability; and then send the capability information to the access network device.
  • the UE can update its ROHC capability and timely report the ROHC capability to network equipment such as access network equipment.
  • the UE can determine that it does not support the ROHC capability, so that the UE and the access network equipment are closed ROHC In order to prevent the UE and the access network equipment from turning off the ROHC and causing the RLF in the VOLTE network to appear prematurely and unable to recover, thereby reducing the probability of the UE’s VOLTE call interruption timeout and automatic hanging up.
  • the probability of random access failure in the random access format such as PRACH format 4
  • FIG. 9 shows a schematic diagram of a possible structure of an access network device provided in an embodiment of the present disclosure.
  • the access network device 90 includes: a receiving module 901; a receiving module 901 for receiving capability information from a user equipment UE, the capability information is used to indicate whether the UE supports ROHC capability, and the capability information is based on the preamble sequence If the information is determined, the preamble sequence information is used for the UE to access the access network equipment.
  • the access network device 90 further includes a sending module; a receiving module 901 is also used to receive a radio resource control RRC connection request message from the UE before receiving the capability information sent by the UE, the RRC connection request message is used to request establishment RRC connection; the sending module is used to send first indication information to the UE, and the first indication information is used to instruct the UE to report capability information to the access network device.
  • a sending module is also used to receive a radio resource control RRC connection request message from the UE before receiving the capability information sent by the UE, the RRC connection request message is used to request establishment RRC connection; the sending module is used to send first indication information to the UE, and the first indication information is used to instruct the UE to report capability information to the access network device.
  • the access network device 90 further includes: a determining module; the determining module is configured to determine the ROHC configuration information according to the capability information received by the receiving module 901 after the receiving module 901 receives the capability information sent by the UE. Configure the UE's communication link on the UE; the sending module is also used to send the ROHC configuration information determined by the determining module to the UE.
  • the access network device provided in the embodiment of the present disclosure can implement each process implemented by the access network device in the foregoing method embodiment. To avoid repetition, the specific description will not be repeated here.
  • the embodiments of the present disclosure provide an access network device, which can receive UE capability information from a UE to learn whether the UE supports ROHC capability. Among them, because the foregoing UE capability information can be determined by the UE according to the preamble sequence. In this way, as the preamble sequence information changes, the UE can update its ROHC capability and report the ROHC capability to the access network device in time.
  • the UE can determine that it does not support the ROHC capability, so that the UE and the access network equipment are closed ROHC In order to prevent the UE and the access network equipment from turning off the ROHC and causing the RLF in the VOLTE network to appear prematurely and unable to recover, thereby reducing the probability of the UE’s VOLTE call interruption timeout and automatic hanging up.
  • the probability of random access failure in the random access format such as PRACH format 4
  • the UE 100 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, and a user Input unit 107, interface unit 108, memory 109, processor 110, power supply 111 and other components.
  • a radio frequency unit 101 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, and a user Input unit 107, interface unit 108, memory 109, processor 110, power supply 111 and other components.
  • the UE structure shown in FIG. 10 does not constitute a limitation on the UE, and the UE may include more or fewer components than shown in the figure, or combine certain components, or arrange different components.
  • the UE includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted
  • the processor 110 is configured to obtain preamble sequence information, which is used by the UE to access the access network equipment; according to the preamble sequence information, determine UE capability information, which is used to indicate whether the UE supports ROHC capability ;
  • the radio frequency unit 101 is used to send the capability information determined by the processor 110 to the access network device.
  • the embodiments of the present disclosure provide a UE.
  • the UE can obtain preamble sequence information and determine the capability information of the UE based on the preamble sequence information, that is, determine whether the UE supports ROHC capability; and then send the capability information to the access network device.
  • the UE can update its ROHC capability and timely report the ROHC capability to network equipment such as access network equipment.
  • the UE can determine that it does not support the ROHC capability, so that the UE and the access network equipment are closed ROHC In order to prevent the UE and the access network equipment from turning off the ROHC and causing the RLF in the VOLTE network to appear prematurely and unable to recover, thereby reducing the probability of the UE’s VOLTE call interruption timeout and automatic hanging up.
  • the probability of random access failure in the random access format such as PRACH format 4
  • the radio frequency unit 101 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, the downlink data from the base station is received and processed by the processor 110; in addition, Uplink data is sent to the base station.
  • the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 101 can also communicate with the network and other devices through a wireless communication system.
  • the UE provides users with wireless broadband Internet access through the network module 102, such as helping users to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 103 can convert the audio data received by the radio frequency unit 101 or the network module 102 or stored in the memory 109 into audio signals and output them as sounds. Moreover, the audio output unit 103 may also provide audio output related to a specific function performed by the UE 100 (for example, call signal reception sound, message reception sound, etc.).
  • the audio output unit 103 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 104 is used to receive audio or video signals.
  • the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042, and the graphics processor 1041 is configured to monitor images of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Data is processed.
  • the processed image frame can be displayed on the display unit 106.
  • the image frame processed by the graphics processor 1041 may be stored in the memory 109 (or other storage medium) or sent via the radio frequency unit 101 or the network module 102.
  • the microphone 1042 can receive sound, and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to the mobile communication base station via the radio frequency unit 101 for output in the case of a telephone call mode.
  • the UE 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light.
  • the proximity sensor can turn off the display panel 1061 and/or when the UE 100 moves to the ear. Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when stationary, and can be used to identify UE posture (such as horizontal and vertical screen switching, related games, Magnetometer posture calibration), vibration recognition related functions (such as pedometer, percussion), etc.; sensor 105 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared Sensors, etc., will not be repeated here.
  • the display unit 106 is used to display information input by the user or information provided to the user.
  • the display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 107 may be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the UE.
  • the user input unit 107 includes a touch panel 1071 and other input devices 1072.
  • the touch panel 1071 also called a touch screen, can collect the user's touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 1071 or near the touch panel 1071. operating).
  • the touch panel 1071 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the user's touch position, and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 110, the command sent by the processor 110 is received and executed.
  • the touch panel 1071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 107 may also include other input devices 1072.
  • other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the touch panel 1071 can be overlaid on the display panel 1061.
  • the touch panel 1071 detects a touch operation on or near it, it is transmitted to the processor 110 to determine the type of the touch event.
  • the type of event provides corresponding visual output on the display panel 1061.
  • the touch panel 1071 and the display panel 1061 are used as two independent components to realize the input and output functions of the UE, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated. Realize the input and output functions of the UE, which are not specifically limited here.
  • the interface unit 108 is an interface for connecting an external device to the UE 100.
  • the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 108 may be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the UE 100 or may be used to communicate between the UE 100 and the external device. Transfer data between.
  • the memory 109 can be used to store software programs and various data.
  • the memory 109 may mainly include a program storage area and a data storage area.
  • the program storage area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data (such as audio data, phone book, etc.) created by the use of mobile phones.
  • the memory 109 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 110 is the control center of the UE. It uses various interfaces and lines to connect various parts of the entire UE. It executes by running or executing software programs and/or modules stored in the memory 109, and calling data stored in the memory 109. Various functions of the UE and processing data, so as to monitor the UE as a whole.
  • the processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, application programs, etc., and the modem The processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 110.
  • the UE 100 may also include a power source 111 (such as a battery) for supplying power to various components.
  • a power source 111 such as a battery
  • the power source 111 may be logically connected to the processor 110 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system.
  • the UE 100 includes some functional modules not shown, which will not be repeated here.
  • the embodiment of the present disclosure further provides a UE, including a processor 110, a memory 109, a computer program stored on the memory 109 and capable of running on the processor 110, and when the computer program is executed by the processor 110
  • a UE including a processor 110, a memory 109, a computer program stored on the memory 109 and capable of running on the processor 110, and when the computer program is executed by the processor 110
  • FIG. 11 it is a schematic structural diagram of another access network device provided by an embodiment of the present disclosure.
  • the access network device 110 shown in FIG. 11 includes a processor 1101, a memory 1102, a communication interface 1103, a communication bus 1104, and a processor 1105.
  • the communication interface 1103 is used to receive UE capability information from the user equipment UE.
  • the capability information is used to indicate whether the UE supports ROHC capability.
  • the capability information is determined according to the preamble sequence information.
  • the preamble sequence information is used for the UE to access Network access equipment.
  • the embodiments of the present disclosure provide an access network device, which can receive UE capability information from a UE to learn whether the UE supports ROHC capability. Among them, because the foregoing UE capability information can be determined by the UE according to the preamble sequence. In this way, as the preamble sequence information changes, the UE can update its ROHC capability and report the ROHC capability to the access network device in time.
  • the UE can determine that it does not support the ROHC capability, so that the UE and the access network equipment are closed ROHC In order to prevent the UE and the access network equipment from turning off the ROHC and causing the RLF in the VOLTE network to appear prematurely and unable to recover, thereby reducing the probability of the UE’s VOLTE call interruption timeout and automatic hanging up.
  • the probability of random access failure in the random access format such as PRACH format 4
  • the foregoing processing module may be one or more processors such as the processor 1101 and the processor 1105 shown in FIG. 11.
  • the foregoing storage module may be the memory 1102 shown in FIG. 11.
  • the forwarding module 403 may be implemented by the communication interface 1103.
  • the processor 1101 is the control center of the access network device 110, and may be a processor or a collective term for multiple processing elements.
  • the processor 1101 may be a CPU, or a specific ASIC, or may be one or more integrated circuits configured to implement the embodiments of the present disclosure, such as: one or more DSPs, or, one or more FPGAs .
  • the processor 1101 can execute various functions of the device by running or executing a software program stored in the memory 1102 and calling data stored in the memory 1102. For example, the processor 1101 may be used to determine the target path.
  • the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 11.
  • the access network device may include multiple processors, such as the processor 1101 and the processor 1105 shown in FIG. 11.
  • processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the memory 1102 may be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, Optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other media that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but Not limited to this.
  • the memory 1102 may exist independently, and is connected to the processor 1101 through a communication bus 1104.
  • the memory 1102 may also be integrated with the processor 1101.
  • the above-mentioned memory 1102 is used to store a software program for executing the solution provided by the embodiment of the present disclosure, and is controlled by the processor 1101 to execute.
  • the communication interface 1103 may include two communication interfaces, a sending interface for sending data to an external device, and a receiving interface for receiving data from the external device. That is, the access network device can use two different communication interfaces. Realize data (such as data message and protocol message) reception and data transmission.
  • the aforementioned communication bus 1104 may specifically be a PCI bus or an EISA bus.
  • the aforementioned communication bus 1104 may be divided into an address bus, a data bus, a control bus, etc., which are not limited in the embodiment of the present disclosure.
  • the structure of the access network device shown in FIG. 11 does not constitute a limitation on the access network device, and may include more or fewer components than shown in the figure, or a combination of some components, or a different component arrangement.
  • the embodiment of the present disclosure further provides an access network device, including a processor 1101, a memory 1102, a computer program stored on the memory 1102 and running on the processor 1101, and the computer program is
  • an access network device including a processor 1101, a memory 1102, a computer program stored on the memory 1102 and running on the processor 1101, and the computer program is
  • 1101 is executed, each process of the foregoing method embodiment is realized, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.
  • an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements each embodiment of the method for reporting capability information.
  • a computer-readable storage medium such as ROM, RAM, magnetic disk or optical disk, etc.

Abstract

提供一种上报能力信息的方法、设备及系统，应用于通信领域，具体应用于UE向接入网设备上报ROHC能力的过程中，以解决UE向基站发起随机接入失败，进而导致VOLTE网络中的无线通信链路无法恢复的问题。该方法包括：获取前导序列信息，该前导序列信息用于UE接入接入网设备；根据该前导序列信息，确定UE的能力信息，该能力信息用于指示UE是否支持鲁棒头压缩ROHC能力；向接入网设备发送该能力信息。

Description

上报能力信息的方法、设备及系统
相关申请的交叉引用
本申请要求于2019年01月16日提交国家知识产权局、申请号为201910041396.7、申请名称为“上报能力信息的方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开实施例涉及通信技术领域，尤其涉及一种上报能力信息的方法、设备及系统。
背景技术
在长期演进语音承载(Voice over Long-Term Evolution，VOLTE)网络中，网络设备(如基站)与用户设备(User Equipment，UE)可以采用鲁棒头压缩(Robust Header Compression，ROHC)协议传输数据。其中，在基站与UE采用ROHC协议传输数据的过程中，若VOLTE网络中的无线通信链路的通信质量变差，则可能造成基站与UE中的数据接收方接收数据失败。此时，为了保证VOLTE网络中的无线通信链路的质量，基站和UE可以将ROHC配置设置为ROHC关闭状态，进而触发网络设备与UE停止采用ROHC协议传输数据。
其中，在UE重新进行ROHC配置的情况下，UE需要重新接入其服务小区(即UE重新进行ROHC配置之前接入的小区)，即UE需要向基站发起随机接入。当UE采用PRACH format 4(PRACH format 4的前导码为preamble format 4)这一随机接入格式向基站发起随机接入时，由于采用PRACH format 4的随机接入信号抗噪声、抗干扰的能力通常较差，因此基站可能无法接收到该随机接入信号，从而使得UE向基站发起随机接入失败，进而导致VOLTE网络中的无线通信链路无法恢复。
发明内容
本公开实施例提供一种上报能力信息的方法、设备及系统，以解决UE向基站发起随机接入失败，进而导致VOLTE网络中的无线通信链路无法恢复的问题。
为了解决上述技术问题，本公开实施例是这样实现的：
第一方面，本公开实施例提供一种上报能力信息的方法，应用于用户设备UE，该方法包括：获取前导序列信息，该前导序列信息用于UE接入接入网设备；根据该前导序列信息，确定UE的能力信息，该能力信息用于指示UE是否支持鲁棒头压缩ROHC能力；向接入网设备发送该能力信息。
第二方面，本公开实施例提供一种上报能力信息的方法，应用于接入网设备，该方法包括：从用户设备UE接收能力信息，该能力信息用于指示UE是否支持鲁棒头压缩ROHC能力，该能力信息为该UE根据前导序列信息确定的，该前导序列信息用于该UE接入该接入网设备。
第三方面，本公开实施例还提供了一种用户设备UE，该UE包括：获取模块、确定模块和发送模块；获取模块，用于获取前导序列信息，该前导序列信息用于UE接入接入网 设备；确定模块，用于根据获取模块获取的该前导序列信息，确定UE的能力信息，该能力信息用于指示UE是否支持鲁棒头压缩ROHC能力；发送模块，用于向接入网设备发送确定模块确定的该能力信息。
第四方面，本公开实施例还提供了一种接入网设备，该接入网设备包括：接收模块；接收模块，用于从用户设备UE接收能力信息，该能力信息用于指示该UE是否支持鲁棒头压缩ROHC能力，该能力信息为该UE根据前导序列信息确定的，该前导序列信息用于该UE接入该接入网设备。
第五方面，本公开实施例提供了一种用户设备UE，包括处理器、存储器及存储在该存储器上并可在该处理器上运行的计算机程序，该计算机程序被该处理器执行时实现如第一方面所述的上报能力信息的方法的步骤。
第六方面，本公开实施例提供了一种接入网设备，包括处理器、存储器及存储在该存储器上并可在该处理器上运行的计算机程序，该计算机程序被该处理器执行时实现如第二方面所述的上报能力信息的方法的步骤。
第七方面，本公开实施例提供了一种通信系统，该通信系统包括如第三方面所述的用户设备UE和第四方面所述的接入网设备；或者该通信系统包括第五方面所述的UE和第六方面所述的接入网设备。
第八方面，本公开实施例提供了一种计算机可读存储介质，该计算机可读存储介质上存储计算机程序，该计算机程序被处理器执行时实现如第一方面或第二方面所述的上报能力信息的方法的步骤。
在本公开实施例中，通过获取前导序列信息，并根据该前导序列信息，可以确定UE的能力信息，即确定UE是否支持ROHC能力；再向接入网设备发送该能力信息。如此，随着前导序列信息的变化，UE可以更新其ROHC能力，并及时将该ROHC能力上报至接入网设备等网络设备。其中，在前导序列信息指示的随机接入格式(如PRACH format 4)的随机接入失败的概率较高的情况下，UE可以确定其不支持ROHC能力，使得UE和接入网设备处于关闭ROHC的状态，以避免UE和接入网设备因关闭ROHC而导致VOLTE网络中的RLF出现过早且无法恢复，进而减小UE的VOLTE通话中断超时，自动挂断的概率。
附图说明
图1为造成无线通信链路失败与恢复的事件及门限的示意图；
图2为本公开实施例提供的一种可能的通信系统的架构示意图；
图3为本公开实施例提供的上报能力信息的方法的流程示意图之一；
图4为本公开实施例提供的上报能力信息的方法的流程示意图之二；
图5为本公开实施例提供的上报能力信息的方法的流程示意图之三；
图6为本公开实施例提供的上报能力信息的方法的流程示意图之四；
图7为本公开实施例提供的上报能力信息的方法的流程示意图之五；
图8为本公开实施例提供的一种可能的UE的结构示意图；
图9为本公开实施例提供的一种可能的接入网设备的结构示意图；
图10为本公开实施例提供的一种UE的硬件结构示意图；
图11为本公开实施例提供的一种接入网设备的硬件结构示意图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开各个实施例中涉及的英文缩写注释如下：
用户设备(user equipment，UE)；
鲁棒头压缩(Robust Header Compression，ROHC)；
参考信号接收功率(Reference Signal Receiving Power，RSRP)；
参考信号接收质量(Reference Signal Receiving Quality，RSRQ)；
信号与干扰加噪声比(Signal to Interference plus Noise Ratio，SINR)；
接收信号强度指示(Received Signal Strength Indication，RSSI)；
跟踪区域标识(Tracking Area identity，TAI)；
公共陆地移动网络(Public Land Mobile Network，PLMN)；
无线资源控制(Radio Resource Control，RRC)；
分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)；
无线链路控制(Radio link Control，RLC)；
长期演进(Long Term Evolution，LTE)；
长期演进语音承载(Voice over Long-Term Evolution，VOLTE)；
物理随机接入信道(Physical Random Access Channel，PRACH)；
随机接入信道(Random Access Channel，RACH)；
物理广播信道(Physical Broadcast Channel，PBCH)；
公共控制信道(Common Control Channel，CCCH)；
物理下行共享信道(Physical Downlink Shared channel，PDSCH)；
主消息块(Master Information Block，MIB)；
系统消息块(System Information Blocks，SIB)；
端口物理层(Port Physical Layer，PHY)；
媒体介入控制(Media Access Control，MAC)；
时分双工(Time Division Duplexing，TDD)；
全球定位系统(Global Positioning System，GPS)；
全球导航卫星系统(Global Navigation Satellite System，GNSS)；
北斗卫星导航系统(BeiDou Navigation Satellite System，BDS)；
无线保真(Wireless-Fidelity，WI-FI)，也可以称为wifi；
最大时间提前量(time advanced，TA)；
物理小区标识(Physical Cell Identifier，PCI)；
互联网协议地址(Internet Protocol Address，IP)；
实时传输协议(Real-time Transport Protocol，RTP)；
机器对机器(Machine to Machine，M2M)；
增强型移动互联网(enhance Mobile Broadband，eMBB)；
超高可靠性与超低时延通信(ultra Reliable&Row Ratency Communication，uRLLC)；
海量物联网通信(massive Machine Type Communication，mMTC)；
移动性管理实体(Mobility Management Entity，MME)；
服务网关(Serving Gateway，S-GW)；
分组数据网络网关(Packet Data Network Gateway，PDN-GW)；
传输节点(Transmission and Reception Point，TRP)；
全球移动通信系统(Global Gystem for Mobile Communication，GSM)；
码分多址(Code Division Multiple Access，CDMA)；
基站收发信台(Base Transceiver Station，BTS)；
宽带码分多址(Wideband Code Division Multiple access，WCDMA)；
云无线接入网络(Cloud Radio Access Network，CRAN)；
无线接入网(Radio Access Network，RAN)；
个人通信业务(Personal Communication Service，PCS)；
会话发起协议(Session Initiation Protocol，SIP)；
无线本地环路(Wireless Local Loop，WLL)；
个人数字助理(Personal Digital Assistant，PDA)；
图形处理器(Graphics Processing Unit，GPU)；
液晶显示器(Liquid Crystal Display，LCD)；
外设部件互连标准(Peripheral Component Interconnect，PCI)；
扩展工业标准结构(Extended Industry Standard Architecture，EISA)；
有机发光二极管(Organic Light-Emitting Diode，OLED)；
只读存储器(Read-Only Memory，ROM)；
随机存取存储器(Random Access Memory，RAM)。
下面对本公开实施例中所涉及的部分术语进行解释，以方便理解：
1、ROHC
在LTE协议规范中，ROHC协议运作在PDCP层，其基本思想是利用数据包头在时间上的相关性，进行压缩编码，从而降低开销。在VOLTE话音服务中，数据包的包头相似性极高，因此ROHC协议可以显著提升数据传输的效率。其中，UE支持ROHC与否，是一种UE能力。
其中，为了能够对多种类型的信息头进行压缩处理，ROHC协议引入了Profile的概念。根据信息头的不同，ROHC协议针对每种信息头类型制定了唯一的Profile ID(即身份标识，也即identity)与之相对应，例如IP/RTP这一信息头类型的Profile ID为Profile 0x0002。
具体的，UE是否支持ROHC能力，指的是UE是否支持压缩ROHC协议中定义的每种信息头类型的能力。其中，每种信息头类型的Profile ID对应一个布尔型数据，该布尔型的数据取值为true，说明UE支持压缩处理该信息头类型的信息头；该布尔型的数据取值为false，说明UE不支持压缩处理该信息头类型的信息头。
通常，在VOLTE网络中，基站一般给UE配置ROHC，即包头压缩。但当VOLTE 网络中的无线通信链路的信道环境恶化(即无线通信链路的通信质量变差)造成上行丢包时，基站可以向UE下发RRC重配置信令，以触发UE关闭ROHC配置，并重新随机接入至基站。其中，若UE随机接入至基站失败，则造成VOLTE网络中的RLF出现过早、且无法恢复，进而导致UE的VOLTE通话中断超时，自动挂断的现象。
另外，由于ROHC涉及PDCP层的数据完整性校验。因此，为了保证网络(如网络中的接入网设备)和UE在关闭ROHC的时间点的一致性，接入网设备可以触发UE关闭ROHC。
2、PRACH格式
在LTE中，定义了PRACH format 0到PRACH format 4一共5种随机接入格式。其中，format 0～3采用839长的ZC(Zadoff-chu)序列，而format 4采用139长的ZC序列。具体的，如表1示出的随机接入前导序列长度(Random access preamble sequence length)的表格，上述PRACH format 0到PRACH format 4这5种随机接入格式的前导码(Preamble format)分别为Preamble format 0～4。
表1
Preamble format(前导码) NZC
0-3 839
4 139
其中，基站在检测RACH信号(UE随机接入过程中向基站发送的上行信号，可以称为随机接入信号)时需要进行相关运算；ZC序列长度越长，检测灵敏度越高。因此，显而易见的，采用PRACH format 4的信号抗噪声、干扰的能力，明显弱于采用其它4种随机接入前导序列的信号，一般认为PRACH format 4的检测灵敏度要差8分贝(Decibe，dB)左右，如此将可能导致基站监测不到采用PRACH format 4的RACH信号。具体的，当UE的随机接入格式配置为PRACH format 4时，相较于PRACH format 0，由于前导序列信息对应的ZC序列长度缩短，RACH资源的时域符号数目大幅减短，SINR灵敏度性能变差大约7-8dB。
3、配置ROHC的无线通信链路
其中，配置ROHC的无线通信链路中可以采用ROHC协议传输数据。如图1所示，为造成无线通信链路失败与恢复的事件及门限的示意图。
图1中各个事件的描述如下：
事件1：ROHC解包失败。其中，在基站与UE传输数据失败的情况下，基站或UE中任一方作为数据接收方，向ROHC数据包发送方发出否定应答NACK(Negative Acknowledgement)。基于此，基站和UE可以关闭ROHC。具体的，在UE执行关闭ROHC时，UE需要随机接入至基站。由于UE采用PRACH format 4发起的随机接入信号抗噪声、抗干扰的能力较差，因此基站可能无法接收到该随机接入信号，从而使得UE向基站发起随机接入失败，进而触发无线通信链路失败。随后，由于UE随机接入失败，或UE对应的小区测量无法满足S准则，因此导致VOLTE网络中的无线通信链路无法迅速恢复。
事件2：物理层同步信号接收强度弱，或上行重传较多等因素，触发物理层判决失步，进而造成VOLTE网络中无线通信链路失败。随后，由于UE对应的小区测量无 法满足S准则，因此导致VOLTE网络中无线通信链路无法迅速恢复。
事件3：UE在小区搜索中，检测到满足S准则的新的小区后，可以向该小区随机接入，以完成VOLTE网络无线通信链路恢复。
其中，事件2的触发门限(如图1示出的K2)低于事件1度触发门限(如图1示出的K1)。如此，当VOLTE网络中的无线通信链路的通信质量出现深衰落时，减少事件1的触发概率，可以使得UE相对较晚的进入RLF状态，甚至不进入RLF状态，从而减少VOLTE通话中断超时，进而自动挂断的概率。
4、UE能力上报的现有规则
在LTE网络中，UE在第一次接入网络(即UE接入基站)时需要上报UE能力(如ROHC能力)。此后，UE能力可以作为UE上下文(Context)的一种，存储在核心网设备中。当UE从脱网(idle not camped)状态(即空闲态)恢复成驻留在某小区(idle camped)的状态或建立RRC连接(RRC connected)的状态(即连接态)时，基站可以获取UE的UE能力的信息。具体的，基站可以通过以下a)或b)两种方式获取UE的UE能力的信息：
a)基站从核心网设备获取UE上下文，进而获得UE能力；
b)基站通过向UE发出能力请求，请求UE重新上报UE能力。
另外，UE可以修改自身能力，例如，对于支持到LTE Rel15的UE，其修改自身能力的具体流程包括以下步骤A和步骤B：
步骤A：UE通过向网络(如核心网设备)上报去附着消息(如detach)，暂时脱网(即使得UE处于空闲态)，此时核心网设备收到detach信令后，可以删掉其存储的UE上下文；
步骤B：UE通过发起随机接入，请求重新附着(attach)到网络(即重新附着到核心网设备)。并在附着网络时上报UE能力(如上报用于指示UE是否支持ROHC能力的能力信息)。
5、其他术语
需要说明的是，本文中的“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。“多个”是指两个或多于两个。
需要说明的是，本公开实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本公开实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本公开的说明书和权利要求书中的术语“第一”和“第二”等是用于区别不同的对象，而不是用于描述对象的特定顺序。例如，第一类前导序列信息和第二类前导序列信息等是用于区别不同的前导序列信息，而不是用于描述前导序列信息的特定顺序。
下面结合附图对本申请提供的技术方案进行介绍。
本公开实施例提供的技术方案可以应用于各种通信系统，例如，5G通信系统、未来演进系统(如LTE通信系统、VOLTE通信系统等)或者多种通信融合系统等等。 可以包括多种应用场景，例如，M2M、D2M、宏微通信、eMBB、uRLLC以及mMTC等场景。这些场景包括但不限于：UE与UE之间的通信，或网络设备与网络设备之间的通信，或网络设备与UE间的通信等场景中。本公开实施例可以应用于与VOLTE通信系统中的网络设备与UE之间的通信，或UE与UE之间的通信，或网络设备与网络设备之间的通信，或者后续演进版本通信系统相关设备之间的通信。
图2示出了本公开实施例所涉及的通信系统的一种可能的结构示意图。如图2所示，该通信系统包括至少一个核心网设备21(图2中仅示出一个)、与每个核心网设备21连接的接入网设备22(图2中仅示出一个)、以及每个接入网设备22所连接的一个或多个UE 23。
上述核心网设备21可以包括控制面设备和用户面设备。其中，控制面设备可以包括MME，用户面设备可以包括S-GW和PDN-GW等。其中，MME可以用于移动管理、会话管理、网元选择及进行用户承载信息存储等。S-GW具有会话管理、路由选择和数据转发、服务质量控制、计费以及存储信息等功能等。PDN-GW可以用于IP地址分配、会话管理、路由选择、数据转发、服务质量控制、计费、策略和计费执行等。
上述的接入网设备22可以为TRP、中继站或接入点等。接入网设备22具体为GSM或CDMA网络中的BTS，也可以是WCDMA中的NB(NodeB)，还可以是LTE中的eNB或eNodeB(evolutional NodeB)。接入网设备22还可以是CRAN场景下的无线控制器。接入网设备22还可以是5G通信系统中的网络侧设备或未来演进网络中的网络侧设备，例如5G通信系统中的基站gNG。
UE 23可以为无线UE也可以为有线UE，该无线UE可以是指向用户提供语音和/或其他业务数据连通性的设备，具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的UE或者未来演进的PLMN网络中的UE等。无线UE可以经RAN与一个或多个核心网进行通信，无线UE可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据，以及PCS电话、无绳电话、SIP话机、WLL站、PDA等设备，无线终端也可以为移动设备、UE终端、接入终端、无线通信设备、终端单元、终端站、移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、远方站、远程终端(Remote Terminal)、订户单元(Subscriber Unit)、订户站(Subscriber Station)、用户代理(User Agent)、终端装置等。作为一种实例，在本公开实施例中，图2以UE是手机为例示出。
下面结合图3所示的上报能力信息的方法的流程图对本公开实施例提供的上报能力信息的方法进行详细描述。其中，虽然在方法流程图中示出了本公开实施例提供的上报能力信息的方法的逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。例如，图3中示出的上报能力信息的方法可以包括步骤301-步骤303：
步骤301、UE获取前导序列信息，前导序列信息用于UE接入接入网设备。
其中，前导序列信息可以为指示上述PRACH format 0～PRACH format 3中的一种 的前导序列信息。
具体的，UE可以通过其接收到的系统广播，获取前导序列信息。其中，该前导序列信息即为当前UE向接入网设备发起随机接入所采用的前导序列信息。
可以理解的是，UE在执行上述步骤301之前，可以接收接入网设备(如基站)广播的系统消息。其中，该系统消息包括PBCH中传输的主系统消息MIB，以及CCCH中通过PDSCH传输的其它系统消息(SIB)，具体而言包括系统信息块1(SIB-1)、系统信息块2(SIB-2)…系统信息块N(SIB-N)等等。具体的，前导序列信息出现在SIB-2中，UE读取SIB-2，以获得当前的前导序列信息。该前导序列信息在SIB-2中的域名称为“prach-ConfigIndex”，其在SIB-2中的格式如下：
Figure PCTCN2019121713-appb-000001
示例性的，对于LTE中的TDD系统，协议定义，当“prach-ConfigIndex”取值为48-57时，意味着前导序列信息指示的随机接入格式为PRACH format 4；其它情况下，前导序列格式为PRACH format 0-3。例如，上述“prach-ConfigIndex”的取值为53，说明当前的前导序列信息指示的随机接入格式为PRACH format 4。
步骤302、UE根据前导序列信息，确定UE的能力信息，该能力信息用于指示UE是否支持ROHC能力。
可以理解的是，由于采用PRACH format 0～PRACH format 3中任一随机接入格式的随机接入信号抗噪声、抗干扰的能力较强，因此接入网设备成功接收到该随机接入信号的概率较高，从而UE采用PRACH format 0～PRACH format 3中的任一随机接入格式发起随机接入成功的概率较高。相应的，由于采用PRACH format 4的随机接入信号抗噪声、抗干扰的能力通常较差，因此接入网设备可能无法接收到该随机接入信号，从而使得UE向接入网设备发起随机接入失败，即UE采用PRACH format 4这一随机接入格式发起的随机接入成功的概率较低。
可选的，本公开实施例中，在前导序列信息指示PRACH format 0～PRACH format 3中的任意一种的情况下，UE可以确定其支持ROHC能力；即上述UE的能力信息可以用于指示UE支持ROHC能力。在前导序列信息为PRACH format 4的情况下，UE可以确定其不支持ROHC能力，即上述UE的能力信息可以用于指示UE不支持ROHC能力。
可以理解，在UE中的硬件支持ROHC算法的前提下，UE可以确定其支持ROHC 能力。
步骤303、UE向接入网设备发送UE的能力信息。
其中，在UE重新确定其ROHC能力等能力之后，便可以触发将UE能力上报至网络侧。具体的，UE可以向接入网设备发送其能力信息。
相应的，接入网设备可以从UE接收上述UE的能力信息。
可选的，接入网设备可以根据UE的能力信息，对UE进行ROHC配置，如触发UE关闭ROHC。
可以理解的是，在UE的能力信息指示UE不支持ROHC能力的情况下，UE与接入网设备等网络设备不会采用ROHC协议传输数据，即UE与接入网设备均处于关闭ROHC的状态。此时，接入网设备不会触发UE执行关闭ROHC的流程，即UE不需要重新进行ROHC配置以关闭ROHC，从而UE不需要先脱网再发起随机接入，进而避免了由UE随机接入失败导致VOLTE网络中的RLF出现过早且无法恢复，进而减少UE的VOLTE通话中断超时，自动挂断的问题。
需要说明的是，本公开实施例提供的上报能力信息的方法，可以获取前导序列信息，并根据该前导序列信息，确定UE的能力信息，即确定UE是否支持ROHC能力；再向接入网设备发送该能力信息。如此，随着前导序列信息的变化，UE可以更新其ROHC能力，并及时将该ROHC能力上报至接入网设备等网络设备。其中，在前导序列信息指示的随机接入格式(如PRACH format 4)的随机接入失败的概率较高的情况下，UE可以确定其不支持ROHC能力，使得UE和接入网设备处于关闭ROHC的状态，以避免UE和接入网设备因关闭ROHC而导致VOLTE网络中的RLF出现过早且无法恢复，进而减小UE的VOLTE通话中断超时，自动挂断的概率。
进一步的，结合图3，如图4所示，本公开实施例提供的上报能力信息的方法，在上述S303之后，还可以包括下述步骤401-步骤403：
步骤401、接入网设备根据UE的能力信息，确定ROHC配置信息。
具体的，UE向接入网设备发送UE的能力信息之后，接入网设备可以从UE接收该能力信息。
可以理解的是，UE的能力信息可以用于触发接入网设备对UE进行ROHC配置。具体的，接入网设备从UE接收能力信息之后，便可以根据能力信息生成上述ROHC配置信息，以触发UE修改ROHC配置。
具体的，在UE的能力信息指示UE支持ROHC能力时，ROHC配置信息可以用于指示UE启用ROHC。相反的，在UE的能力信息指示UE不支持ROHC能力时，ROHC配置信息可以用于指示UE关闭ROHC。
步骤402、接入网设备向UE发送ROHC配置信息。
相应的，接入网设备向UE发送ROHC配置信息之后，UE可以从UE接收该ROHC配置信息。
步骤403、UE根据ROHC配置信息，配置UE的通信链路。
其中，在ROHC配置信息指示UE启用ROHC时，UE可以采用ROHC协议与接入网设备等网络设备传输数据。具体的，UE可以配置其ROHC通信链路，以采用ROHC协议传输数据。
可以理解的是，由于基于LTE的话音传输，存在大量相似的数据包头，因此当UE发起呼叫或网络寻呼UE，进而需要建立起VOLTE连接时，网络会给出相应的话音传输承载的ROHC配置，即接入网设备可以向UE发送上述ROHC配置信息。
需要说明的是，本公开实施例提供的上报能力信息的方法中，UE可以从接入网设备接收ROHC配置信息，而ROHC配置信息是根据能力信息确定的，因此UE可以采用ROHC配置信息配置UE的通信链路符合UE的ROHC能力。如此，在UE的能力信息指示UE不支持ROHC能力时，ROHC配置信息可以指示UE关闭ROHC。从而，即使后续无线通信链路的通信质量较差，也不会发生UE重新关闭ROHC之后发起的随机接入失败的情况。
在一种可能的实现方式中，结合图3，如图5所示，本公开实施例提供的上报能力信息的方法中，上述步骤302可以通过步骤302a或步骤302b实现：
步骤302a、在前导序列信息为第一类前导序列信息的情况下，UE确定UE的能力信息用于指示UE支持ROHC能力。
可选的，上述第一类前导序列信息可以为指示上述PRACH format 0～PRACH format 3中的一种随机接入格式的前导序列信息。
步骤302b、在前导序列信息为第二类前导序列信息的情况下，UE根据辅助信息，确定UE的能力信息。
可选的，上述第二类前导序列信息可以为指示上述PRACH format 4这一随机接入格式的前导序列信息。
可选的，UE在执行上述步骤302a或步骤302b之前，可以先判断当前获取的前导序列信息是第一类前导序列信息还是第二类前导序列信息。
可以理解的是，本公开实施例中的辅助信息可以为用于指示UE所处的网络环境的信息。
其中，UE所处的网络环境较好，说明该UE可以支持ROHC能力，并通过ROHC协议成功传输数据，如成功传输通过ROHC协议压缩后的数据。相反的，UE所处的网络环境较差，说明该UE可以不支持ROHC能力，此时UE并不需要通过ROHC协议成功传输数据，以避免传输通过ROHC协议压缩后的数据发生失败。
可选的，本公开实施例提供的上报能力信息的方法，上述步骤302b可以通过步骤302b-1或步骤302b-2实现：
步骤302b-1、在辅助信息满足第一条件的情况下，UE确定UE的能力信息用于指示UE支持ROHC能力。
步骤302b-2、在辅助信息不满足第一条件的情况下，UE确定UE的能力信息用于指示UE不支持ROHC能力。
可以理解的是，辅助信息满足第一条件，说明UE所处的网络环境较好，此时UE的无线通信链路的通信质量可能较好；反之，辅助信息不满足第一条件，说明UE所处的网络环境较差，此时，UE的无线通信链路的通信质量可能较差。
可选的，UE在执行上述S302b-1或S302b-2之前，可以先判断当前获取的辅助信息是否满足第一条件。
需要说明的是，本公开实施例提供的上报能力信息的方法，在前导序列信息为第 一类前导序列信息，即前导序列信息指示的随机接入格式的随机接入失败的概率较低的情况下，UE确定其支持ROHC能力，使得UE和接入网设备处于启用ROHC的状态。此时，在通过ROHC协议提高UE和接入网设备传输数据的效率的同时，即使后续因UE和接入网设备关闭ROHC而引起UE重新发起随机接入流程，该随机接入成功概率较高，也不会发生RLF出现过早且无法恢复，进而导致UE的VOLTE通话中断超时，自动挂断的情况。另外，在前导序列信息为第二类前导序列信息，即前导序列信息指示的随机接入格式的随机接入失败的概率较高的情况下，若UE在辅助信息不满足第一条件(即UE所处的网络环境较差)，则UE确定其不支持ROHC能力，使得UE和接入网设备处于关闭ROHC的状态。进而，可以避免UE和接入网设备由于关闭ROHC而导致VOLTE网络中的RLF出现过早且无法恢复，进而减小UE的VOLTE通话中断超时，自动挂断的概率。
可选的，本公开实施例提供的上报能力信息的方法，上述步骤302b-1具体可以通过下述步骤302b-1a实现：
步骤302b-1a、在第一信息满足与第一信息对应的第一条件的情况下，UE确定UE的能力信息用于指示UE支持ROHC能力，第一信息为辅助信息中的任意一项信息。
相应的，上述步骤302b-2具体可以通过下述步骤302b-2a实现：
步骤302b-2a、在辅助信息的每项信息均不满足对应的第一条件的情况下，UE确定UE的能力信息用于指示UE不支持ROHC能力。
可选的，本公开实施例提供的上报能力信息的方法，上述步骤302b-1具体可以通过下述步骤302b-1b实现：
步骤302b-1b、在第二信息满足与第二信息对应的第一条件的情况下，UE确定UE的能力信息用于指示UE支持ROHC能力，第二信息为辅助信息中的每项信息。
相应的，上述步骤302b-2具体可以通过下述步骤302b-2b实现：
步骤302b-2b、在辅助信息的任意一项信息不满足对应的第一条件的情况下，UE确定UE的能力信息用于指示UE不支持ROHC能力。
可选的，本公开实施例提供的上报能力信息的方法可以应用于以下场景1和/或场景2中：
场景1、UE处于非连接态。
其中，UE处于非连接态可以指UE处于驻留某小区的状态。
场景2、UE处于连接态。
其中，UE处于连接态可以指UE处于接入某小区的状态。
可选的，本公开实施例的场景1和/或场景2中，辅助信息可以包括以下辅助信息1～辅助信息4中的至少一项。
进一步，可选的，本公开实施例的场景1和/或场景2中，第一条件可以包括以下条件1～条件4中的至少一项。其中，一项辅助信息对应一个第一条件。
辅助信息1、第一小区的RSRP；相应的，辅助信息1对应的第一条件为条件1：第一小区的RSRP大于或等于第一阈值。
其中，第一小区为UE的驻留小区。
可以理解的是，当前UE的网络环境可以为当前UE所处位置的网络覆盖情况。
辅助信息2、第一小区的RSRQ；相应的，辅助信息2对应的第一条件为条件2：第一小区的RSRQ大于或等于第二阈值。
辅助信息3、第一小区的SINR；相应的，辅助信息3对应的第一条件为条件3：第一小区的SINR大于或等于第三阈值。
辅助信息4、第一小区的RSSI；相应的，辅助信息4对应的第一条件为条件4：第一小区的RSSI大于或等于第四阈值。
其中，UE驻留小区(如上述第一小区)的下行RSRP、RSRQ、SINR和RSSI这些信息，可以是UE进行小区测量和选择时获得的，也可以是物理层根据协议定义的直接测量结果，还可以是在RRC层滤波后的间接测量结果。
可以理解的是，在UE测量得到当前UE驻留小区(如第一小区)的RSRP大于或等于第一阈值，说明该UE当前的驻留小区或者服务小区的下行信号的信号强度较强，即该驻留小区或者服务小区处于正常覆盖。此时，若辅助信息1满足条件1，则UE可以确定其能力信息用于指示UE支持ROHC能力。反之，UE测量得到当前UE驻留小区(如第一小区)的RSRP小于第一阈值时，说明该UE当前的驻留小区或者服务小区的下行信号的信号强度较弱，即该驻留小区或者服务小区处于弱覆盖。此时，若辅助信息1不满足条件1，则UE可以确定其能力信息用于指示其不支持ROHC能力。
类似的，本公开实施例中，对UE驻留小区的下行RSRQ、SINR或RSSI满足相应的第一条件的描述，可以参照上述对UE驻留小区的下行RSRP满足第一条件的相关描述，这里不再赘述。
具体的，本公开实施例中，第一阈值、第二阈值、第三阈值和第四阈值的取值，可以根据实际使用需求确定，本公开实施例不作限定。
可选的，本公开实施例中，在辅助信息包括上述辅助信息1～辅助信息4中的多项的情况下，UE只要判断得到辅助信息1～辅助信息4中任意一项辅助信息满足相应的第一条件，便可以确定整体的辅助信息满足整体的第一条件，即UE可以确定其能力信息用于指示UE支持ROHC能力。具体的，UE可以执行上述实施例中的步骤302b-1a，确定UE支持ROHC能力；或者，UE可以执行上述实施例中的步骤302b-2a，确定UE不支持ROHC能力。此时，上述第一信息可以为辅助信息1～辅助信息4中任意一项辅助信息。
进一步的，可选的，辅助信息还可以包括以下辅助信息5～辅助信息7中的至少一项。
进一步的，本公开实施例的场景1和/或场景2中，第一条件还可以包括以下条件5～条件7中的至少一项。其中，一项辅助信息对应一个第一条件。
辅助信息5、第二小区的RSRP；相应的，辅助信息5对应的第一条件为条件5：第二小区的RSRP小于或等于第五阈值。
其中，第二小区为第一小区的同频邻区。具体的，第一小区和第二小区处于同频组网，即第一小区和第二小区使用同一频率。
具体的，本公开实施例中，第一小区可以存在多个同频邻区，即存在多个第二小区。此时，UE针对多个第二小区中的每个第二小区可以分别判断其RSRP是否小于或等于第五阈值。
辅助信息6、第二小区的RSRQ；相应的，辅助信息6对应的第一条件为条件6：第二小区的RSRQ小于或等于第六阈值。
辅助信息7、第二小区的SINR；相应的，辅助信息7对应的第一条件为条件7：第二小区的SINR小于或等于第七阈值。
其中，上述第二小区的RSRP、RSRQ和SINR，可以是在UE进行小区测量和选择时获得的，也可以是物理层根据协议定义的直接测量结果，也可以在RRC层滤波后的间接测量结果。
可以理解的是，在UE测量得到当前同频邻区(即第二小区)的RSRP小于或等于第五阈值，说明该同频邻区的下行信号的信号强度较强，即该同频邻区对于UE的干扰强度较强。此时，若辅助信息5满足条件5，则UE可以确定其能力信息用于指示其支持ROHC能力。反之，UE测量得到当前同频邻区(即第二小区)的RSRP大于第五阈值，说明该同频邻区的下行信号的信号强度较弱，即该同频邻区对于UE的干扰强度较弱。此时，若辅助信息5不满足条件5，则UE可以确定其能力信息用于指示其不支持ROHC能力。
类似的，本公开实施例中，对第二小区的RSRQ或SINR满足相应的第一条件的描述，可以参照上述对第二小区的RSRP满足第一条件的相关描述，这里不再赘述。
具体的，本公开实施例中，第五阈值、第六阈值和第七阈值的取值，可以根据实际使用需求确定，本公开实施例不作限定。
可选的，本公开实施例中，在辅助信息包括上述辅助信息5～辅助信息7中的多项的情况下，UE只要判断得到辅助信息5～辅助信息7中任意一项辅助信息满足相应的第一条件，便可以确定整体的辅助信息满足整体的第一条件，即UE可以确定其能力信息用于指示UE支持ROHC能力。具体的，UE可以执行上述实施例中的步骤302b-1a，确定UE支持ROHC能力；或者，UE可以执行上述实施例中的步骤302b-2a，确定UE不支持ROHC能力。此时，上述第一信息为辅助信息5～辅助信息7中任意一项辅助信息。
进一步，可选的，本公开实施例的场景1和/或场景2中，辅助信息还可以包括以下辅助信息8～辅助信息11中的至少一项。
具体的，本公开实施例的场景1和/或场景2中，第一条件可以包括以下条件8～条件11中的至少一项。其中，一项辅助信息对应一个第一条件。
辅助信息8、UE的地理位置信息；相应的，辅助信息8对应的第一条件为条件8：UE的地理位置信息指示的位置位于预设区域内。
其中，地理位置信息用于指示为UE配置的ROHC通信链路传输数据失败时UE所处的位置。
可选的，上述地理位置信息可以是通过卫星定位系统(含GPS、GNSS、BDS等)或其他定位技术确定得到的UE的地址位置信息；其它定位技术，包括但不限于wifi定位，无线通信基站定位等；UE基于上述定位技术获得UE的地址位置信息，并由UE的应用层回馈到UE的通信模块。
可选的，上述预设区域可以是由一个区域内的低RSRP(即弱覆盖)出现概率的先验统计信息判断得到的，如上述预设区域为低RSRP(即弱覆盖)出现概率较低的 区域。
具体的，在辅助信息8满足条件8的情况下，当前UE的地址位置信息指示的位置处于预设区域内，说明当前UE所处位置的低RSRP出现概率为低，则UE确定其能力信息用于指示其支持ROHC能力。反之，在辅助信息8不满足条件8的情况下，当前UE的地址位置信息指示的位置处于预设区域之外，说明当前UE所处位置的低RSRP出现概率为高，则UE确定其能力信息用于指示其不支持ROHC能力。
辅助信息9、UE接收的TAI；相应的，辅助信息9对应的第一条件为条件9：UE接收的TAI与预设TAI相同。
辅助信息10、UE接收的PLMN标识；相应的，辅助信息10对应的第一条件为条件10为：UE接收的PLMN标识与预设PLMN标识相同。
辅助信息11、UE接收的第一小区的小区标识；相应的，辅助信息11对应的第一条件为条件11：UE接收的第一小区的小区标识与预设小区标识相同。
具体的，上述UE接收的TAI、PLMN标识和第一小区的小区标识可以为UE配置的ROHC通信链路传输数据失败时UE获取得到的。即这些标识可以用于指示UE配置的ROHC通信链路传输数据失败时UE所处的位置。
其中，上述UE接收的TAI(即“trackingAreaCode”)、PLMN标识(即PLMN identity)、或第一小区的小区标识(如cell identity或PCI)可以是通过SIB-1和/或MIB得到的。即这些信息可以出现在SIB-1和/或MIB中，其在SIB-1中具体的格式为：
Figure PCTCN2019121713-appb-000002
Figure PCTCN2019121713-appb-000003
其中，上述SIB-1的具体格式中的“plmn-Identity”字段的取值即为UE接收的TAI；“trackingAreaCode”字段的取值即为UE接收的PLMN标识；“cellIdentity”字段的取值即为UE接收的第一小区的小区标识。
可选的，本公开实施例中，可以根据一个区域内低RSRP(即弱覆盖)出现概率的先验统计信息，确定出低RSRP出现概率较高的区域对应的TAI、PLMN标识或小区标识。并将这些TAI、PLMN标识或小区标识分别作为上述预设TAI、预设PLMN标识和预设小区标识。
具体的，当前UE接收的TAI与预设TAI相同，说明当前UE所处位置的低RSRP出现概率为低，UE可以确定其能力信息用于指示其支持ROHC能力。此时，辅助信息9满足条件9。反之，当前UE接收的TAI与预设TAI不同，说明当前UE所处位置的低RSRP出现概率为高，UE可以确定其能力信息用于指示其不支持ROHC能力。此时，辅助信息9不满足条件9。
类似的，本公开实施例中，对UE接收的PLMN标识或接收到第一小区的小区标识满足相应的第一条件的描述，可以参照上述对UE接收的TAI满足相应的第一条件的相关描述，这里不再赘述。
可选的，本公开实施例中，在辅助信息包括上述辅助信息9～辅助信息11中的多项信息的情况下，UE判断得到辅助信息9～辅助信息11中一项或多项辅助信息分别满足相应的第一条件，便可以确定整体的辅助信息满足整体的第一条件，即UE可以最终确定其能力信息用于指示UE支持ROHC能力。
进一步，可选的，在辅助信息包括上述辅助信息8～辅助信息11情况下，若UE判断得到辅助信息8满足条件8，和/或，辅助信息9～辅助信息11中每项分别满足条件9～条件11中相应的条件，则UE可以确定其能力信息用于指示UE支持ROHC能力。
相应的，若UE判断得到辅助信息8不满足条件8，且辅助信息9～辅助信息11中每项分别不满足条件9～条件11中相应的条件，则UE可以确定其能力信息用于指示UE不支持ROHC能力。
进一步，可选的，本公开实施例中，在辅助信息包括上述辅助信息8～辅助信息11情况下，若UE判断得到辅助信息8满足条件8，且辅助信息9～辅助信息11中每项分别满足条件9～条件11中相应的条件，则UE可以确定其能力信息用于指示UE支持ROHC能力。
相应的，若UE判断得到辅助信息8不满足条件8，和/或，辅助信息9～辅助信息11中每项分别不满足条件9～条件11中相应的条件，则UE可以确定其能力信息用于 指示UE不支持ROHC能力。
另外，在辅助信息包括上述辅助信息8～辅助信息11中的至少一项的情况下，UE执行上述步骤302b-1a、步骤302b-1b、步骤302b-2a或步骤302b-2b时，上述第一信息为辅助信息8～辅助信息11中任意一项信息，第二信息为辅助信息8～辅助信息11中的每项信息。
当然，在辅助信息包括上述辅助信息1～辅助信息11中的至少一项信息的情况下，执行上述步骤302b-1a、步骤302b-1b、步骤302b-2a或步骤302b-2b时，上述第一信息为辅助信息8～辅助信息11中任意一项信息，第二信息为辅助信息8～辅助信息11中的每项信息。
示例性的，UE可以通过辅助信息1～辅助信息4中的至少一项确定得到UE的一个能力信息(记为能力信息1)、通过辅助信息5～辅助信息7中的至少一项确定得到UE的一个能力信息(记为能力信息2)，并通过辅助信息8～辅助信息11中的至少一项确定得到UE的一个能力信息(记为能力信息3)。
可选的，在辅助信息包括上述辅助信息1～辅助信息11中的多项信息的情况下，若上述能力信息1、能力信息2和能力信息3中的任意一项指示UE支持ROHC能力，则UE最终确定UE支持ROHC能力。反之，若上述能力信息1、能力信息2和能力信息3中的每项均指示UE不支持ROHC能力，则UE最终确定UE支持ROHC能力。
可选的，在辅助信息包括上述辅助信息1～辅助信息11中的多项信息的情况下，若上述能力信息1、能力信息2和能力信息3中的每项均指示UE支持ROHC能力，则UE最终确定UE支持ROHC能力。反之，若上述能力信息1、能力信息2和能力信息3中的任意一项指示UE不ROHC能力，则UE最终确定UE不支持ROHC能力。
进一步，可选的，在本公开实施例的场景2中，具体在UE处于连接态、且UE配置有ROHC通信链路的情况下，辅助信息还可以包括以下辅助信息12～辅助信息15中的至少一项：
具体的，本公开实施例的场景2中，第一条件可以包括以下条件12～条件15中的至少一项。其中，一项辅助信息对应一个第一条件。
辅助信息12、ROHC通信链路上物理层的重传次数；相应的，辅助信息12对应的第一条件为条件12：ROHC通信链路上物理层的重传次数小于或等于第八阈值。
可选的，上述“ROHC通信链路上物理层”中的物理层可以为ROHC通信链路上的PHY，或者ROHC通信链路上的MAC层。
辅助信息13、ROHC通信链路上物理层的丢包数量；相应的，辅助信息13对应的第一条件为条件13：ROHC通信链路上物理层的丢包数量小于或等于第九阈值。
辅助信息14、ROHC通信链路上的RLC层上ROHC无线承载的丢包数量；相应的，辅助信息14对应的第一条件为条件14：ROHC通信链路上的RLC层上ROHC无线承载的丢包数量小于或等于第十阈值。
其中，在VOLTE网络中，ROHC无线承载即为语音承载。
辅助信息15、ROHC通信链路上的PDCP层上ROHC无线承载的丢包数量；相应的，辅助信息15对应的第一条件为条件15：ROHC通信链路上的PDCP层上ROHC无线承载的丢包数量小于或等于第十一阈值。
需要说明的是，本公开实施例中，辅助信息12～辅助信息15中的任意一项，均可以用于UE判断当前包含ROHC无线承载的无线通信链路的通信质量。
具体的，在辅助信息包括辅助信息12的情况下，辅助信息12满足条件12，即在某一有限长的时段内，ROHC通信链路上物理层的重传次数小于或等于第八阈值，说明ROHC无线承载的链路通信质量为好。此时，UE可以确定其能力信息用于指示其支持ROHC能力。反之，辅助信息12不满足条件12，即ROHC通信链路上物理层的重传次数大于第八阈值，说明ROHC无线承载的链路通信质量为差。此时，UE可以确定其能力信息用于指示其不支持ROHC能力。
类似的，本公开实施例中，对辅助信息13、辅助信息14或辅助信息15满足相应的第一条件的描述，可以参照上述对辅助信息12满足第一条件的相关描述，这里不再赘述。
具体的，本公开实施例中，第八阈值、第九阈值、第十阈值和第十一阈值的取值，可以根据实际使用需求确定，本公开实施例不作限定。
可以理解的是，在辅助信息包括上述辅助信息12～辅助信息15中的至少一项信息的情况下，UE执行上述实施例中的步骤302b-1a、步骤302b-1b、步骤302b-2a或步骤302b-2b时，上述第一信息为辅助信息12～辅助信息15中任意一项信息，第二信息为辅助信息12～辅助信息15中的每项信息。此时，UE确定得到的UE的能力信息记为能力信息4。
进一步，可选的，在辅助信息包括上述辅助信息1～辅助信息15的情况下，若上述能力信息1～能力信息4中的任意一项指示UE支持ROHC能力，则UE最终确定UE支持ROHC能力。反之，若上述能力信息1～能力信息4中的每项均指示UE不ROHC能力，则UE最终确定UE支持ROHC能力。
可选的，在辅助信息包括上述辅助信息1～辅助信息15的情况下，若上述能力信息1～能力信息4中的每项均指示UE支持ROHC能力，则UE最终确定UE支持ROHC能力。反之，若上述能力信息1～能力信息4中的任意一项指示UE不ROHC能力，则UE最终确定UE支持ROHC能力。
需要说明的是，本公开实施例提供的上报能力信息的方法，由于根据辅助信息中的一项或多项信息，均可以用于确定UE是否支持ROHC能力，因此即使UE仅能获取得到辅助信息的部分信息，UE也可以根据这些信息确定UE的能力信息。另外，由于UE可以结合辅助信息中的多项信息确定UE的能力信息，因此有利于提高确定的能力信息的准确性。
可选的，本公开实施例提供的上报能力信息的方法，上述场景1和/或场景2中，在上述步骤303之前，UE可以发起随机接入的流程。具体的，结合图4，如图6所示，上述上报能力信息的方法，在上述步骤303之前，还可以包括步骤601-步骤603，相应的步骤303可以通过步骤604实现：
步骤601、UE向接入网设备发送随机接入请求。
其中，上述随机接入请求包括UE获取的前导序列信息，即UE采用该前导序列信息指示的随机接入格式发起随机接入。
相应的，接入网设备可以从UE接收随机接入请求。
步骤602、UE向接入网设备发送RRC连接请求消息。
其中，RRC连接请求消息用于请求建立RRC连接。
相应的，接入网设备可以从UE接收RRC连接请求消息。
具体的，UE向接入网设备发送RRC连接请求消息之前，UE可以执行上述步骤601。
具体的，本公开实施例中，接入网设备获取UE的能力信息可以通过以下实施方式1和实施方式2实现：
实施方式1：
针对接入网设备向UE获取UE的能力信息，而非向核心网设备获取UE上下文的实施方式(记为实施方式1)，UE发起随机接入后，RRC连接建立请求消息中的原因“Cause”字段，可以是
a)UE发起呼叫，
b)接收到了网络的呼叫，
c)UE有业务需要进行数据传输，
d)TA更新，
e)UE附着(attach)。
也就是说，UE发起的RRC连接请求，不局限于与呼叫相关。这是因为，在UE处于非连接态时，UE发起呼叫或网络寻呼UE，都需要UE发起RRC连接请求，使得UE从处于非连接态变到处于连接态，进而可以产生后续接入网设备请求UE上报其能力信息的流程。在UE处于连接态时下，UE发起呼叫或网络寻呼UE，不会触发后续的接入网设备请求UE上报其能力信息，即不会由呼叫触发UE能力的重新上报，因此，需要在RRC连接建立时，就上报更新了的UE的能力信息。
实施方式2：
针对网络向核心网设备获取UE上下文以获取UE的能力信息，而非向UE获取UE的能力信息的情况下，UE发起随机接入前，需要先通过接入网设备向核心网设备发起去附着请求(detach)解除UE附着，即请求核心网设备释放UE；之后，UE发起的RRC连接建立请求消息中的原因“Cause”字段，只能是“UE附着”。由于核心网设备解除UE附着时，核心网设备会删除其存储的UE上下文，因此，重新建立UE附着到核心网设备的RRC连接请求，会触发接入网设备请求UE的能力信息，以重新将UE附着到核心网设备。
另外，UE可以尝试先执行实施方式1，观察网络(即网络中的接入网设备)是否会触发UE能力上报，进而确定是否进一步执行实施方式2。
步骤603、接入网设备向UE发送第一指示信息。
其中，第一指示信息用于指示UE向接入网设备上报UE的能力信息。
相应的，UE可以从接入网设备接收上述第一指示信息。
步骤604、UE根据第一指示信息，向接入网设备发送UE的能力信息。
也就是说，UE的能力信息由第一指示信息指示UE发送。
需要说明的是，本公开实施例提供的上报能力信息的方法，UE可以在网络中的接入网设备请求UE的能力信息，如接入网设备向UE发送第一指示信息的情况下，向 接入网设备发送UE的能力信息，以使得UE可以获知UE是否支持ROHC能力。
可选的，结合图6，如图7所示，本公开实施例提供的上报能力信息的方法，在场景2中的上述步骤602之前，具体在步骤601之前还可以包括步骤701：
步骤701、在UE处于第一状态的情况下，UE控制UE切换为第二状态。
具体的，第一状态为处于连接态、且传输预设类型的业务的状态，第二状态为处于空闲态。
其中，UE控制UE切换为第二状态，可以使得UE暂时脱网。
可选的，上述预设类型的业务可以为VOLTE话音业务或其它需保证连续性的业务。
可以理解的是，UE暂时脱网，可以分以下两种情况：
a)UE处于第二状态时，由于UE处于连接态时，接入网设备不会触发UE发送能力信息，而UE话音状态下，UE通过从核心网设备detach再attach的方法更新UE的能力信息会造成UE的VOLTE通话自动挂断，因此UE不再适合采用上述实施例2的方式发送UE的能力信息。另外，UE采用上述实施例1的方式发送UE的能力信息的情况下，UE暂时脱网，进入idle且无驻留小区的状态(即空闲态)，再重新建立RRC连接，可以触发接入网设备下发UE能力上报请求(即上述第一指示信息)，进而使得接入网设备可以从UE获取UE的能力信息。其中，UE脱网的时间应刚好等于T311计时器的设定时间，以此保证接入网设备和UE对于RLF的流程有一致的认知。其中，由UE从连接态切换为空闲态，即暂时脱网后重新随机接入的代价是，可能造成UE处于1秒左右的通话无声状态。
b)UE处于连接态、且不存在预设类型的业务的情况下，则UE可以通过上述实施方式1或实施方式2向接入网设备发送UE的能力信息，以向网络上报其ROHC能力。其中，在实施方式1中，UE可以暂时脱网，进入空闲态后，再重新建立RRC连接，由此触发接入网设备下发UE能力上报请求(如第一指示信息)，UE脱网的时间应刚好等于T311计时器的设定时间，以此保证网络和UE对于RLF的流程有一致的认知。在实施方式2中，UE可以通过从核心网设备detach再attach的方法确定更新UE的能力信息，但代价是带来数据连接的抖动。
进一步的，在UE采用上述实施方式2发送UE的能力信息的情况下，上述步骤701之前还可以包括步骤702：
步骤702、在UE处于第三状态的情况下，UE向接入网设备发送去附着请求消息，去附着请求消息用于请求UE从核心网设备去附着。
其中，第三状态为处于空闲态，或者处于连接态、且未传输预设类型的业务的状态。上述去附着信息即为detach。
相应的，接入网设备可以从UE接收上述去附着请求消息，并根据该去附着请求消息触发核心网设备将UE去附着。如此，随后UE的RRC请求消息可以用于请求接入网设备触发将UE重新附着到核心网设备。
需要说明的是，本公开实施例提供的上报能力信息的方法中，由于UE可以依据其处于连接态或非连接态，以及UE是否执行预设类型的业务的状态，采用不同方式向网络侧上报UE的能力信息，以使得接入网设备可以在对UE执行的业务影响较小 的同时，更新UE的能力信息。
图8示出了本公开实施例中涉及的UE的一种可能的结构示意图。如图8所示，UE 80包括获取模块801、确定模块802和发送模块803；获取模块801，用于获取前导序列信息，该前导序列信息用于UE接入接入网设备；确定模块802，用于根据获取模块801获取的前导序列信息，确定UE的能力信息，该能力信息用于指示UE是否支持ROHC能力；发送模块803，用于向接入网设备发送确定模块802确定的能力信息。
可选的，确定模块802，具体用于在前导序列信息为第一类前导序列信息的情况下，确定能力信息用于指示UE支持ROHC能力。
可选的，确定模块802，具体用于在前导序列信息为第二类前导序列信息的情况下，根据辅助信息，确定UE的能力信息。
可选的，确定模块802，具体用于在辅助信息满足第一条件的情况下，确定UE的能力信息用于指示UE支持ROHC能力。
可选的，辅助信息包括以下至少一项：第一小区的RSRP、第一小区的RSRQ、第一小区的SINR、第一小区的RSSI；其中，第一小区为UE的驻留小区。
可选的，第一条件包括以下至少一项：第一小区的RSRP大于或等于第一阈值、第一小区的RSRQ大于或等于第二阈值、第一小区的SINR大于或等于第三阈值、第一小区的RSSI大于或等于第四阈值。
可选的，辅助信息还包括以下至少一项：第二小区的RSRP、第二小区的RSRQ、第二小区的SINR；其中，第二小区为第一小区的同频邻区。
可选的，第一条件还包括以下至少一项：第二小区的RSRP小于或等于第五阈值、第二小区的RSRQ小于或等于第六阈值、第二小区的SINR小于或等于第七阈值。
可选的，辅助信息还包括以下至少一项：UE的地理位置信息、UE接收的TAI、UE接收的PLMN标识、UE接收的第一小区的小区标识；其中，该地理位置信息用于指示为UE配置的ROHC通信链路传输数据失败时UE所处的位置。
可选的，第一条件还包括以下至少一项：地理位置信息指示的位置位于预设区域内、TAI与预设TAI相同、PLMN标识与预设PLMN标识相同、小区标识与预设小区标识相同。
可选的，在UE处于连接态、且UE配置有ROHC通信链路的情况下，辅助信息还包括以下至少一项：ROHC通信链路上物理层的重传次数、物理层的丢包数量、ROHC通信链路上的无线链路控制RLC层上ROHC无线承载的丢包数量、ROHC通信链路上的分组数据汇聚协议PDCP层上ROHC无线承载的丢包数量。
可选的，第一条件还包括以下至少一项：物理层的重传次数小于或等于第八阈值、物理层的丢包数量小于或等于第九阈值、RLC层上ROHC无线承载的丢包数量小于或等于第十阈值、PDCP层上ROHC无线承载的丢包数量小于或等于第十一阈值。
可选的，确定模块802，具体用于在第一信息满足与第一信息对应的第一条件的情况下，确定能力信息用于指示UE支持ROHC能力，第一信息为辅助信息中的任意一项信息。
可选的，确定模块802，具体用于在第二信息满足与第二信息对应的第一条件的 情况下，确定能力信息用于指示UE支持ROHC能力，第二信息为辅助信息中的每项信息。
可选的，UE 80还包括：第一接收模块：发送模块803，还用于向接入网设备发送能力信息之前，向接入网设备发送RRC连接请求消息，RRC连接请求消息用于请求建立RRC连接；第一接收模块，用于从接入网设备接收第一指示信息，第一指示信息用于指示UE向接入网设备上报能力信息；发送模块803，具体用于根据第一指示信息，向接入网设备发送能力信息。
可选的，UE 80还包括：切换模块；切换模块，用于发送模块803向接入网设备发送RRC连接请求消息之前，在UE处于第一状态的情况下，控制UE切换为第二状态，第一状态为处于连接态、且传输预设类型的业务的状态，第二状态为处于空闲态。
可选的，发送模块803，还用于向接入网设备发送RRC连接请求消息之前，在UE处于第三状态的情况下，向接入网设备发送去附着请求消息，去附着请求消息用于请求UE从核心网设备去附着；其中，第三状态为处于空闲态，或者处于连接态、且未传输预设类型的业务的状态。
可选的，UE 80还包括：第二接收模块和配置模块；第二接收模块，用于发送模块803向接入网设备发送能力信息之后，从接入网设备接收ROHC配置信息，ROHC配置信息为根据能力信息确定的；配置模块，用于根据接收模块接收的ROHC配置信息，配置UE的通信链路。
本公开实施例提供的UE能够实现上述方法实施例中UE实现的各个过程，为避免重复，具体描述此处不再赘述。
本公开实施例提供一种UE，UE可以获取前导序列信息，并根据该前导序列信息，确定UE的能力信息，即确定UE是否支持ROHC能力；再向接入网设备发送该能力信息。如此，随着前导序列信息的变化，UE可以更新其ROHC能力，并及时将该ROHC能力上报至接入网设备等网络设备。其中，在前导序列信息指示的随机接入格式(如PRACH format 4)的随机接入失败的概率较高的情况下，UE可以确定其不支持ROHC能力，使得UE和接入网设备处于关闭ROHC的状态，以避免UE和接入网设备因关闭ROHC而导致VOLTE网络中的RLF出现过早且无法恢复，进而减小UE的VOLTE通话中断超时，自动挂断的概率。
图9示出了本公开实施例中提供的接入网设备的一种可能的结构示意图。如图9所示，接入网设备90包括：接收模块901；接收模块901，用于从用户设备UE接收能力信息，该能力信息用于指示UE是否支持ROHC能力，该能力信息为根据前导序列信息确定的，该前导序列信息用于UE接入接入网设备。
可选的，接入网设备90还包括：发送模块；接收模块901，还用于从接收UE发送的能力信息之前，从UE接收无线资源控制RRC连接请求消息，RRC连接请求消息用于请求建立RRC连接；该发送模块，用于向UE发送第一指示信息，第一指示信息用于指示UE向接入网设备上报能力信息。
可选的，接入网设备90还包括：确定模块；该确定模块，用于接收模块901接收UE发送的能力信息之后，根据接收模块901接收的能力信息，确定ROHC配置信息，ROHC配置信息用于UE配置UE的通信链路；发送模块，还用于向UE发送确定模块 确定的ROHC配置信息。
本公开实施例提供的接入网设备能够实现上述方法实施例中接入网设备实现的各个过程，为避免重复，具体描述此处不再赘述。
本公开实施例提供一种接入网设备，该接入网设备可以从UE接收UE的能力信息，以获知该UE是否支持ROHC能力。其中，由于上述UE的能力信息是UE可以根据该前导序列确定的。如此，随着前导序列信息的变化，UE可以更新其ROHC能力，并及时将该ROHC能力上报至该接入网设备。其中，在前导序列信息指示的随机接入格式(如PRACH format 4)的随机接入失败的概率较高的情况下，UE可以确定其不支持ROHC能力，使得UE和接入网设备处于关闭ROHC的状态，以避免UE和接入网设备因关闭ROHC而导致VOLTE网络中的RLF出现过早且无法恢复，进而减小UE的VOLTE通话中断超时，自动挂断的概率。
图10为本公开实施例提供的一种UE的硬件结构示意图，该UE 100包括但不限于：射频单元101、网络模块102、音频输出单元103、输入单元104、传感器105、显示单元106、用户输入单元107、接口单元108、存储器109、处理器110、以及电源111等部件。本领域技术人员可以理解，图10中示出的UE结构并不构成对UE的限定，UE可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开实施例中，UE包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载UE、可穿戴设备、以及计步器等。
其中，处理器110，用于获取前导序列信息，该前导序列信息用于UE接入接入网设备；根据该前导序列信息，确定UE的能力信息，该能力信息用于指示UE是否支持ROHC能力；射频单元101，用于向接入网设备发送处理器110确定的能力信息。
本公开实施例提供一种UE，UE可以获取前导序列信息，并根据该前导序列信息，确定UE的能力信息，即确定UE是否支持ROHC能力；再向接入网设备发送该能力信息。如此，随着前导序列信息的变化，UE可以更新其ROHC能力，并及时将该ROHC能力上报至接入网设备等网络设备。其中，在前导序列信息指示的随机接入格式(如PRACH format 4)的随机接入失败的概率较高的情况下，UE可以确定其不支持ROHC能力，使得UE和接入网设备处于关闭ROHC的状态，以避免UE和接入网设备因关闭ROHC而导致VOLTE网络中的RLF出现过早且无法恢复，进而减小UE的VOLTE通话中断超时，自动挂断的概率。
应理解的是，本公开实施例中，射频单元101可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器110处理；另外，将上行的数据发送给基站。通常，射频单元101包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元101还可以通过无线通信系统与网络和其他设备通信。
UE通过网络模块102为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元103可以将射频单元101或网络模块102接收的或者在存储器109中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元103还可以提供与UE 100执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收 声音等等)。音频输出单元103包括扬声器、蜂鸣器以及受话器等。
输入单元104用于接收音频或视频信号。输入单元104可以包括图形处理器(Graphics Processing Unit，GPU)1041和麦克风1042，图形处理器1041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元106上。经图形处理器1041处理后的图像帧可以存储在存储器109(或其它存储介质)中或者经由射频单元101或网络模块102进行发送。麦克风1042可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元101发送到移动通信基站的格式输出。
UE 100还包括至少一种传感器105，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板1061的亮度，接近传感器可在UE 100移动到耳边时，关闭显示面板1061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别UE姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器105还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元106用于显示由用户输入的信息或提供给用户的信息。显示单元106可包括显示面板1061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode，OLED)等形式来配置显示面板1061。
用户输入单元107可用于接收输入的数字或字符信息，以及产生与UE的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元107包括触控面板1071以及其他输入设备1072。触控面板1071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板1071上或在触控面板1071附近的操作)。触控面板1071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器110，接收处理器110发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板1071。除了触控面板1071，用户输入单元107还可以包括其他输入设备1072。具体地，其他输入设备1072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板1071可覆盖在显示面板1061上，当触控面板1071检测到在其上或附近的触摸操作后，传送给处理器110以确定触摸事件的类型，随后处理器110根据触摸事件的类型在显示面板1061上提供相应的视觉输出。虽然在图10中，触控面板1071与显示面板1061是作为两个独立的部件来实现UE的输入和输出功能，但是在某些实施例中，可以将触控面板1071与显示面板1061集成而实现UE的输入和输出功能，具体此处不做限定。
接口单元108为外部装置与UE 100连接的接口。例如，外部装置可以包括有线或 无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元108可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到UE 100内的一个或多个元件或者可以用于在UE 100和外部装置之间传输数据。
存储器109可用于存储软件程序以及各种数据。存储器109可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器109可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器110是UE的控制中心，利用各种接口和线路连接整个UE的各个部分，通过运行或执行存储在存储器109内的软件程序和/或模块，以及调用存储在存储器109内的数据，执行UE的各种功能和处理数据，从而对UE进行整体监控。处理器110可包括一个或多个处理单元；优选的，处理器110可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器110中。
UE 100还可以包括给各个部件供电的电源111(比如电池)，优选的，电源111可以通过电源管理系统与处理器110逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，UE 100包括一些未示出的功能模块，在此不再赘述。
可选的，本公开实施例还提供一种UE，包括处理器110，存储器109，存储在存储器109上并可在所述处理器110上运行的计算机程序，该计算机程序被处理器110执行时实现上述方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
示例性的，如图11所示，为本公开实施例提供的另一种接入网设备的结构示意图。具体的，图11示出的接入网设备110包括处理器1101、存储器1102、通信接口1103、通信总线1104和处理器1105。
其中，通信接口1103用于从用户设备UE接收UE的能力信息，该能力信息用于指示UE是否支持ROHC能力，该能力信息为根据前导序列信息确定的，该前导序列信息用于UE接入接入网设备。
本公开实施例提供一种接入网设备，该接入网设备可以从UE接收UE的能力信息，以获知该UE是否支持ROHC能力。其中，由于上述UE的能力信息是UE可以根据该前导序列确定的。如此，随着前导序列信息的变化，UE可以更新其ROHC能力，并及时将该ROHC能力上报至该接入网设备。其中，在前导序列信息指示的随机接入格式(如PRACH format 4)的随机接入失败的概率较高的情况下，UE可以确定其不支持ROHC能力，使得UE和接入网设备处于关闭ROHC的状态，以避免UE和接入网设备因关闭ROHC而导致VOLTE网络中的RLF出现过早且无法恢复，进而减 小UE的VOLTE通话中断超时，自动挂断的概率。
具体的，上述处理模块可以为图11所示的处理器1101以及处理器1105等一个或多个处理器。上述存储模块可以为图11所示的存储器1102。转发模块403可以由通信接口1103实现。
其中，处理器1101是接入网设备110的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器1101可以是一个CPU，也可以是特定ASIC，或者可以是被配置成实施本公开实施例的一个或多个集成电路，如：一个或多个DSP，或，一个或者多个FPGA。
其中，处理器1101可以通过运行或执行存储在存储器1102内的软件程序，以及调用存储在存储器1102内的数据，执行设备的各种功能。例如，处理器1101可以用于确定目标路径。
在具体的实现中，作为一种实施例，处理器1101可以包括一个或多个CPU，例如图11中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，接入网设备可以包括多个处理器，例如图11中所示的处理器1101和处理器1105。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器1102可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1102可以是独立存在，通过通信总线1104与处理器1101相连接。存储器1102也可以和处理器1101集成在一起。其中，上述存储器1102用于存储执行本公开实施例提供方案的软件程序，并由处理器1101来控制执行。
通信接口1103，可以包括两个通信接口，一个用于向外部设备发送数据的发送接口和一个用于接收来自外部设备的数据的接收接口，即接入网设备可以通过两个不同的通信接口分别实现数据(如数据报文和协议报文)的接收和数据的发送。
上述通信总线1104具体可以是PCI总线或EISA总线等。上述通信总线1104可以分为地址总线、数据总线、控制总线等，本公开实施例对此不作限定。
图11中示出的接入网设备的结构并不构成对接入网设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
其中，本公开实施例提供的接入网设备110中各个模块的详细描述以及各个模块执行上述实施例中的相关方法步骤后所带来的技术效果可以参考本公开方法实施例中的相关描述，此处不再赘述。
可选的，本公开实施例还提供一种接入网设备，包括处理器1101，存储器1102，存储在存储器1102上并可在所述处理器1101上运行的计算机程序，该计算机程序被处理器1101执行时实现上述方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
可选的，本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述上报能力信息的方法的每个实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如ROM、RAM、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (27)

  1. 一种上报能力信息的方法，应用于用户设备UE，所述方法包括：
    获取前导序列信息，所述前导序列信息用于所述UE接入接入网设备；
    根据所述前导序列信息，确定所述UE的能力信息，所述能力信息用于指示所述UE是否支持鲁棒头压缩ROHC能力；
    向所述接入网设备发送所述能力信息。
  2. 根据权利要求1所述的方法，其中，所述根据所述前导序列信息，确定所述UE的能力信息，包括：
    在所述前导序列信息为第一类前导序列信息的情况下，确定所述能力信息用于指示所述UE支持ROHC能力。
  3. 根据权利要求1所述的方法，其中，所述根据所述前导序列信息，确定所述UE的能力信息，包括：
    在所述前导序列信息为第二类前导序列信息的情况下，根据辅助信息，确定所述能力信息。
  4. 根据权利要求3所述的方法，其中，所述根据辅助信息，确定所述能力信息，包括：
    在所述辅助信息满足第一条件的情况下，确定所述能力信息用于指示所述UE支持ROHC能力。
  5. 根据权利要求4所述的方法，其中，所述辅助信息包括以下至少一项：第一小区的参考信号接收功率RSRP、所述第一小区的参考信号接收质量RSRQ、所述第一小区的信号与干扰加噪声比SINR、所述第一小区的接收信号强度指示RSSI；
    其中，所述第一小区为所述UE的驻留小区。
  6. 根据权利要求5所述的方法，其中，所述第一条件包括以下至少一项：所述第一小区的RSRP大于或等于第一阈值、所述第一小区的RSRQ大于或等于第二阈值、所述第一小区的SINR大于或等于第三阈值、所述第一小区的RSSI大于或等于第四阈值。
  7. 根据权利要求4或6所述的方法，其中，所述辅助信息还包括以下至少一项：第二小区的RSRP、所述第二小区的RSRQ、所述第二小区的SINR；
    其中，所述第二小区为第一小区的同频邻区，所述第一小区为所述UE的驻留小区。
  8. 根据权利要求7所述的方法，其中，所述第一条件还包括以下至少一项：
    所述第二小区的RSRP小于或等于第五阈值、所述第二小区的RSRQ小于或等于第六阈值、所述第二小区的SINR小于或等于第七阈值。
  9. 根据权利要求4、6或8所述的方法，其中，所述辅助信息还包括以下至少一项：所述UE的地理位置信息、所述UE接收的跟踪区域标识TAI、所述UE接收的公共陆地移动网络PLMN标识、所述UE接收的第一小区的小区标识，所述第一小区为所述UE的驻留小区；
    其中，所述地理位置信息用于指示为所述UE配置的ROHC通信链路传输数据失败时所述UE所处的位置。
  10. 根据权利要求9所述的方法，其中，所述第一条件还包括以下至少一项：
    所述地理位置信息指示的位置位于预设区域内、所述TAI与预设TAI相同、所述PLMN 标识与预设PLMN标识相同、所述小区标识与预设小区标识相同。
  11. 根据权利要求4、6、8或10所述的方法，其中，在所述UE处于连接态、且所述UE配置有ROHC通信链路的情况下，所述辅助信息还包括以下至少一项：所述ROHC通信链路上物理层的重传次数、所述物理层的丢包数量、所述ROHC通信链路上的无线链路控制RLC层上ROHC无线承载的丢包数量、所述ROHC通信链路上的分组数据汇聚协议PDCP层上ROHC无线承载的丢包数量。
  12. 根据权利要求11所述的方法，其中，
    所述第一条件还包括以下至少一项：所述物理层的重传次数小于或等于第八阈值、所述物理层的丢包数量小于或等于第九阈值、所述RLC层上ROHC无线承载的丢包数量小于或等于第十阈值、所述PDCP层上ROHC无线承载的丢包数量小于或等于第十一阈值。
  13. 根据权利要求6、8、10或12所述的方法，其中，所述在所述辅助信息满足第一条件的情况下，确定所述能力信息用于指示所述UE支持ROHC能力，包括：
    在第一信息满足与所述第一信息对应的第一条件的情况下，确定所述能力信息用于指示所述UE支持ROHC能力，所述第一信息为所述辅助信息中的任意一项信息。
  14. 根据权利要求6、8、10或12所述的方法，其中，所述在所述辅助信息满足第一条件的情况下，确定所述能力信息用于指示所述UE支持ROHC能力，包括：
    在第二信息满足与所述第二信息对应的第一条件的情况下，确定所述能力信息用于指示所述UE支持ROHC能力，所述第二信息为所述辅助信息中的每项信息。
  15. 根据权利要求1或3所述的方法，其中，所述向所述接入网设备发送所述能力信息之前，所述方法还包括：
    向所述接入网设备发送无线资源控制RRC连接请求消息，所述RRC连接请求消息用于请求建立RRC连接；
    从所述接入网设备接收第一指示信息，所述第一指示信息用于指示所述UE向所述接入网设备上报所述能力信息；
    所述向所述接入网设备发送所述能力信息，包括：
    根据所述第一指示信息，向所述接入网设备发送所述能力信息。
  16. 根据权利要求15所述的方法，其中，所述向所述接入网设备发送RRC连接请求消息之前，所述方法还包括：
    在所述UE处于第一状态的情况下，控制所述UE切换为第二状态，所述第一状态为处于连接态、且传输预设类型的业务的状态，所述第二状态为处于空闲态。
  17. 根据权利要求15所述的方法，其中，所述向所述接入网设备发送RRC连接请求消息之前，所述方法还包括：
    在所述UE处于第三状态的情况下，向所述接入网设备发送去附着请求消息，所述去附着请求消息用于请求将所述UE从核心网设备去附着；
    其中，所述第三状态为处于空闲态，或者处于连接态、且未传输预设类型的业务的状态。
  18. 根据权利要求1至6中任意一项所述的方法，其中，所述向所述接入网设备发送所述能力信息之后，所述方法还包括：
    从所述接入网设备接收ROHC配置信息，所述ROHC配置信息为根据所述能力信息 确定的；
    根据所述ROHC配置信息，配置所述UE的通信链路。
  19. 一种上报能力信息的方法，应用于接入网设备，所述方法包括：
    从用户设备UE接收能力信息，所述能力信息用于指示所述UE是否支持鲁棒头压缩ROHC能力，所述能力信息为所述UE根据前导序列信息确定的，所述前导序列信息用于所述UE接入所述接入网设备。
  20. 根据权利要求19所述的方法，其中，所述从用户设备UE接收能力信息之前，所述方法还包括：
    从所述UE接收无线资源控制RRC连接请求消息，所述RRC连接请求消息用于请求建立RRC连接；
    向所述UE发送第一指示信息，所述第一指示信息用于指示所述UE向所述接入网设备上报所述能力信息。
  21. 根据权利要求19所述的方法，其中，所述从用户设备UE接收能力信息之后，所述方法还包括：
    根据所述能力信息，确定ROHC配置信息，所述ROHC配置信息用于所述UE配置所述UE的通信链路；
    向所述UE发送所述ROHC配置信息。
  22. 一种用户设备UE，包括：获取模块、确定模块和发送模块；
    所述获取模块，用于获取前导序列信息，所述前导序列信息用于所述UE接入接入网设备；
    所述确定模块，用于根据所述获取模块获取的所述前导序列信息，确定所述UE的能力信息，所述能力信息用于指示所述UE是否支持鲁棒头压缩ROHC能力；
    发送模块，用于向所述接入网设备发送所述确定模块确定的所述能力信息。
  23. 一种接入网设备，包括：接收模块；
    所述接收模块，用于从用户设备UE接收能力信息，所述能力信息用于指示所述UE是否支持鲁棒头压缩ROHC能力，所述能力信息为所述UE根据前导序列信息确定的，所述前导序列信息用于所述UE接入所述接入网设备。
  24. 一种用户设备UE，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至18中任一项所述的上报能力信息的方法的步骤。
  25. 一种接入网设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求19至21中任一项所述的上报能力信息的方法的步骤。
  26. 一种通信系统，所述通信系统包括如权利要求22所述的用户设备UE和权利要求23所述的接入网设备；或者所述通信系统包括如权利要求24所述的UE和权利要求25所述的接入网设备。
  27. 一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如权利要求1至21中任一项所述的上报能力信息的方法的步骤。
PCT/CN2019/121713 2019-01-16 2019-11-28 上报能力信息的方法、设备及系统 WO2020147436A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910041396.7A CN109862622B (zh) 2019-01-16 2019-01-16 上报能力信息的方法、设备及系统
CN201910041396.7 2019-01-16

Publications (1)

Publication Number Publication Date
WO2020147436A1 true WO2020147436A1 (zh) 2020-07-23

Family

ID=66894996

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/121713 WO2020147436A1 (zh) 2019-01-16 2019-11-28 上报能力信息的方法、设备及系统

Country Status (2)

Country Link
CN (1) CN109862622B (zh)
WO (1) WO2020147436A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109862622B (zh) * 2019-01-16 2021-02-23 维沃移动通信有限公司 上报能力信息的方法、设备及系统
CN110351804B (zh) * 2019-06-17 2021-11-12 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备
CN112887989B (zh) * 2019-11-30 2023-03-03 华为技术有限公司 基于oam的通信方法和相关设备及存储介质
CN113259076B (zh) * 2020-02-12 2022-08-05 大唐移动通信设备有限公司 一种信息传输方法、装置及设备
CN114158033B (zh) * 2020-09-07 2024-04-26 华为技术有限公司 一种网络系统和终端设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771948A (zh) * 2008-12-31 2010-07-07 鼎桥通信技术有限公司 一种mbms业务中头压缩方式的配置方法
US20150382243A1 (en) * 2006-02-22 2015-12-31 Apple Inc. Service Flow With Robust Header Compression (ROHC) In A WiMAX Wireless Network
US20160183123A1 (en) * 2014-12-17 2016-06-23 Samsung Electronics Co., Ltd. Method and apparatus for controlling header compression function of terminal in a communication system
CN107426771A (zh) * 2016-05-23 2017-12-01 中国移动通信有限公司研究院 一种数据传输方法及装置
WO2018167858A1 (ja) * 2017-03-14 2018-09-20 株式会社Ｎｔｔドコモ 無線通信装置及び無線通信方法
CN109862622A (zh) * 2019-01-16 2019-06-07 维沃移动通信有限公司 上报能力信息的方法、设备及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103533665A (zh) * 2013-06-08 2014-01-22 北京星河亮点技术股份有限公司 一种lte终端综测仪状态机的实现方法
WO2015026133A1 (en) * 2013-08-19 2015-02-26 Lg Electronics Inc. Broadcast transmitting device, broadcast receiving device, operating method of the broadcast transmitting device, and operating method of the broadcast receiving device
CN104640212B (zh) * 2013-11-11 2019-02-05 中国移动通信集团公司 一种资源分配方法及装置
EP3298849B1 (en) * 2015-05-22 2021-10-06 Telefonaktiebolaget LM Ericsson (PUBL) Classification of non-standard user equipment in wireless communication network
WO2017073336A1 (ja) * 2015-10-27 2017-05-04 ソニー株式会社 送信装置、受信装置、及び、データ処理方法
KR102047710B1 (ko) * 2016-01-07 2019-11-22 엘지전자 주식회사 사용자기기 및 데이터 전송 방법과, 네트워크 노드 및 데이터 전송 방법
US20180368181A1 (en) * 2017-06-16 2018-12-20 Lg Electronics Inc. Method and user equipment for monitoring random access response, and method and base station for transmitting random access response

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150382243A1 (en) * 2006-02-22 2015-12-31 Apple Inc. Service Flow With Robust Header Compression (ROHC) In A WiMAX Wireless Network
CN101771948A (zh) * 2008-12-31 2010-07-07 鼎桥通信技术有限公司 一种mbms业务中头压缩方式的配置方法
US20160183123A1 (en) * 2014-12-17 2016-06-23 Samsung Electronics Co., Ltd. Method and apparatus for controlling header compression function of terminal in a communication system
CN107426771A (zh) * 2016-05-23 2017-12-01 中国移动通信有限公司研究院 一种数据传输方法及装置
WO2018167858A1 (ja) * 2017-03-14 2018-09-20 株式会社Ｎｔｔドコモ 無線通信装置及び無線通信方法
CN109862622A (zh) * 2019-01-16 2019-06-07 维沃移动通信有限公司 上报能力信息的方法、设备及系统

Also Published As

Publication number Publication date
CN109862622A (zh) 2019-06-07
CN109862622B (zh) 2021-02-23

Similar Documents

Publication Publication Date Title
WO2020147436A1 (zh) 上报能力信息的方法、设备及系统
WO2020034840A1 (zh) 无线链路失败的信息处理方法、终端及网络设备
JP2021145351A (ja) デュアルｓｉｍデュアルアクティブを実装するための通信方法および端末
WO2020164516A1 (zh) 确定方法及设备
RU2769399C1 (ru) Способ реконфигурации и абонентское оборудование
US11382160B2 (en) Method of processing radio link failure, user terminal and network device
WO2021185100A1 (zh) 一种网络接入系统、方法及终端
WO2019137337A1 (zh) 小区选择方法、终端及网络设备
US11963027B2 (en) Measurement method, terminal and network side device
US11502737B2 (en) Beam failure recovery method in multi-carrier system and apparatus
US20230026021A1 (en) Relay ue determining method and device
US20220141745A1 (en) Network switching method and terminal
CN110167041B (zh) 波束失败恢复请求发送方法及用户设备
WO2022052024A1 (zh) 参数配置方法、装置、通信设备和存储介质
US20210176684A1 (en) Terminal camping method, information transmission method, terminal, and network device
WO2019242465A1 (zh) 一种资源请求方法及用户设备
WO2020038294A1 (zh) 传输方法及终端设备
CN111277998B (zh) 一种无线通信方法及终端设备
WO2021197151A1 (zh) 信息传输方法、用户终端和接入网网元
CN111615162A (zh) 一种带宽部分bwp切换方法及设备
US20220167306A1 (en) Data receiving method, data sending method, terminal, and network device
WO2020221125A1 (zh) 配置信息获取、发送方法、终端及网络侧设备
WO2021018282A1 (zh) 网络切换方法、网络设备及终端
WO2020164513A1 (zh) 一种信息处理方法、设备及系统
WO2022160199A1 (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: 19910318

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

Country of ref document: EP

Kind code of ref document: A1