WO2021129568A1 - 由用户设备执行的随机接入报告方法和用户设备 - Google Patents

由用户设备执行的随机接入报告方法和用户设备 Download PDF

Info

Publication number
WO2021129568A1
WO2021129568A1 PCT/CN2020/137981 CN2020137981W WO2021129568A1 WO 2021129568 A1 WO2021129568 A1 WO 2021129568A1 CN 2020137981 W CN2020137981 W CN 2020137981W WO 2021129568 A1 WO2021129568 A1 WO 2021129568A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
rach
report
scenario
rrc
Prior art date
Application number
PCT/CN2020/137981
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 WO2021129568A1 publication Critical patent/WO2021129568A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/002Transmission of channel access control information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0833Random access procedures, e.g. with 4-step access

Definitions

  • the present disclosure relates to the field of wireless communication technology, and more specifically, the present disclosure relates to a user equipment, a base station, and related methods.
  • network optimization can achieve the purpose of optimizing network performance.
  • data collection and data analysis are performed on existing deployed and operating networks to find out the reasons that affect network quality, and network performance is improved by modifying the configured network parameters, adjusting the network structure, and deploying equipment.
  • SON Self-configuration and Self-Optimization Network
  • the network side can configure the UE to perform measurement for SON.
  • the SON function includes many aspects, such as the Automatic Neighbour Relation Function (ANR), which is used to reduce the burden on the operator’s neighbor cell management, and the Mobile Load Balancing function (MLB, Mobility Load), which is used to balance the responsibility of different cells. Balancing), Mobility Robustness Optimization (MRO) for optimizing mobile performance, random access channel optimization for optimizing random access channel parameters, and radio link failure for optimizing coverage and MRO Report function, etc.
  • ANR Automatic Neighbour Relation Function
  • MLB Mobile Load Balancing function
  • MRO Mobility Robustness Optimization
  • random access channel optimization for optimizing random access channel parameters
  • radio link failure for optimizing coverage and MRO Report function
  • NR New Radio
  • LTE Long Term Evolution
  • the present disclosure aims to realize the random access channel performance in the SON function in the NR network and the coverage optimization problem caused by the random access problem, and further, solve the problem of how to more accurately feed back the random access process information to the network side .
  • the purpose of the present disclosure is to provide a random access report method executed by a user equipment and a user equipment, which can implement more refined RACH reports in a conditional switching scenario, so that the network side can make updates based on the detailed information in the RACH report. Accurate adjustment of RACH parameters can improve RACH performance and coverage performance.
  • a random access report method executed by a user equipment, including: triggering and executing a random access procedure in a random access trigger scenario; and sending a random access report to the network side.
  • the random access scenario identifier in the RACH report is set as a conditional handover.
  • the random access scenario identifier set as the conditional handover may indicate that the corresponding random access process uses the random access configuration during the conditional handover.
  • variable may include multiple items, and each item is associated with a RACH report corresponding to a random access procedure performed by the user equipment.
  • the random access scenario identifier in the associated RACH report is set as a conditional handover.
  • the RACH report may be included in a radio resource control RRC message and sent to the network side.
  • the included random access scenario identifier in the RACH report may be set as a conditional handover.
  • a user equipment including: a processor; and a memory storing instructions; wherein the instructions execute the above method when run by the processor.
  • a more refined RACH report in a conditional switching scenario can be realized, so that the network side can perform RACH parameters more accurately based on the detailed information in the RACH report Adjustments can improve RACH performance and coverage performance.
  • Figure 1 shows the process of contention-based random access to CBRA
  • Figure 2 shows the process of non-competition-based random access to CFRA
  • Figure 3 shows a schematic diagram of the flow of conditional switching
  • Fig. 4 shows a flowchart of a random access report method executed by a user equipment according to an embodiment of the present disclosure.
  • Fig. 5 shows a block diagram of a user equipment according to an embodiment of the present disclosure.
  • the base station in this disclosure can be any type of base station, including Node B, enhanced base station eNB, 5G communication system base station gNB, or micro base station, pico base station, macro base station, home base station, etc.; the cell can also be any of the above
  • the cell under the type of base station, the cell can also be a beam, a transmission point (TRP), and a base station can also be a central unit (gNB-Central Unit, gNB-CU) or a distributed unit (gNB- Distributed Unit, gNB-DU).
  • gNB-Central Unit gNB-CU
  • gNB- Distributed Unit gNB- Distributed Unit
  • LTE system is also used to refer to 5G and subsequent LTE systems (such as eLTE systems, or LTE systems that can be connected to a 5G core network) ), and LTE can be replaced by Evolved Universal Terrestrial Radio Access (E-UTRA) or E-UTRAN.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • handover refers to the change of the primary cell (Primary Cell, PCell) initiated by the network side. It includes the change of the primary cell between cells and the change of the primary cell within the cell, that is, the primary cell of the UE is changed from the source cell to The target cell, where the source cell and the target cell may be the same cell or different cells.
  • the source cell is also referred to as a source base station, and may also be a source beam (beam) or a source transmission point (TRP), and the target cell may also be referred to as a target base station, or it may be a target beam or a target transmission point.
  • the source cell refers to the cell that is connected to serve the UE before the handover process is initiated, that is, the cell from which the UE receives the RRC message containing the handover command.
  • the target cell refers to the cell that the UE connects to and serves the UE after the handover process is successfully completed, or the cell indicated by the target cell identifier included in the handover command, and the cell that the UE accesses when the handover is received.
  • the handover command described in the present disclosure is used to trigger the UE to perform handover.
  • it is an RRC reconfiguration message containing a synchronization reconfiguration (Reconfigurationwithsync) information element.
  • MCG master cell group
  • the RRC reconfiguration message of the reconfiguration (Reconfigurationwithsync) information element At this time, handover can also be referred to as synchronous reconfiguration.
  • the synchronization reconfiguration information element or the mobile control information information element contains the configuration information of the target cell, such as the target cell identity, the target cell frequency, the common configuration of the target cell, such as system information, and the random information used by the UE to access the target cell Access configuration, UE's security parameter configuration in the target cell, UE's radio bearer configuration in the target cell, etc.
  • Different embodiments can also work in combination, for example, the same variables/parameters/nouns in different embodiments are explained in the same way.
  • the RRC reconfiguration message in the present disclosure is equivalent to the RRC connection reconfiguration message; similarly, the response message RRC reconfiguration complete message is equivalent to the RRC connection reconfiguration complete message.
  • the handover command is equivalent to the RRC message containing the handover command, and refers to the RRC message or the configuration in the RRC message that triggers the UE to perform the handover.
  • Switch configuration refers to all or part of the configuration in the switch command. Cancel, release, delete, empty and clear can be replaced. Execution, use and application can be replaced. Configuration and reconfiguration can be replaced. Monitor and detect can be replaced. The conditional switching command and the conditional switching configuration can be replaced.
  • Physical random access channel resource Physical Random Access Channel (PRACH) resource.
  • PRACH Physical Random Access Channel
  • the base station broadcasts the physical random access channel parameter configuration used by the cell through the system information.
  • the physical random access channel resource PRACH resource may refer to physical frequency resources and/or time domain resources and/or codes used for random access. Domain resources (such as preamble).
  • Random Access Channel Random Access Channel, RACH.
  • RACH refers to the channel used to send the random access preamble.
  • RACH can refer to either the transport channel RACH or the physical random access channel PRACH, without distinction.
  • RACH parameter/configuration refers to the wireless configuration that implements the random access function, including PRACH related configuration, such as the maximum number of preamble transmissions, power boost parameters, random access response receiving window size, MAC contention resolution timer configuration, PRACH time-frequency resource configuration , Message 1 (i.e.
  • preamble subcarrier spacing, used to indicate the number of synchronization channel blocks (Synchronization Signal Block, SSB) corresponding to each RACH occasion (RACH occasion, RO) and the contention-based random preamble corresponding to each SSB
  • SSB Synchronization Signal Block
  • RACH occasion RO
  • contention-based random preamble corresponding to each SSB
  • the configuration of the number of preambles (configured by the ssb-perRACH-OccasionAndCB-PreamblesPerSSB information element), backoff parameters (in the scalingFactorBI information element), etc.
  • CBRA contention-based random access
  • CFRA contention Free Random Access
  • the CBRA process is shown in Figure 1. It is divided into four steps: the first step is for the UE to send message 1 (i.e. random access preamble) to the base station; the second step: the UE receives the message 2 (i.e. random access preamble) from the base station. Access response Random Access Response (RAR); Step 3: The UE sends message 3 (uplink transmission scheduled by the uplink grant in message 2).
  • RAR Access response Random Access Response
  • Message 3 is generally used to send the UE identity to the base station for wireless Resource control (Radio Resource Control, RRC) RRC messages for connection establishment/resumption/re-establishment, UE contention resolution identifiers for random access contention resolution, etc., in the early data transmission, can also include user plane data; step 4 : UE receives message 4 from the base station (that is, a message for contention resolution).
  • RRC Radio Resource Control
  • the PRACH resource used in CBRA is shared by many UEs.
  • the first step the UE sends the message 1 (ie random access preamble) to the base station; the second step: the UE receives the message 2 (ie random access preamble) from the base station.
  • Access Response Random Access Response (RAR) After successfully receiving Message 2 associated with Message 1, the UE considers that the CFRA process has been successfully completed.
  • the base station In CFRA, the base station generally allocates dedicated PRACH resources such as preamble (referred to as step 0 in Figure 2) for the UE in advance, so there is no competition.
  • a two-step random access process is being introduced in the current NR. Combine the first and third steps in the above four-step random access process and send the message A in the same step.
  • message A contains a random access preamble and the subsequent associated PUSCH load.
  • the content of the PUSCH load is the same as that contained in message 3. It can include RRC messages, user plane data, MAC control elements, such as cache status. Report and UE identification, etc.
  • the second step and the fourth step are combined into the same step called message B.
  • Message B is the response to message A in the two-step random access process, and its content is similar to the content of message 2 and message 4 above, and it can include a response for contention resolution (contention resolution identifier, random access preamble identifier) , UE identity, etc.), fallback indication, backoff indication, time advance command, uplink grant, and may also include a response RRC message corresponding to the RRC message contained in the response message A, etc.
  • the two-step random access process can shorten the time delay of random access.
  • two-step random access uses a different random access resource configuration than four-step random access.
  • the UE can fall back to the four-step random access process during two-step random access, for example, when it receives a fallback random access response (fallback Random Access Response, fallback RAR) from the network side, or when the two-step random access When the number of times of sending access attempt message A exceeds a configured maximum number of times, etc.
  • fallback RAR fallback Random Access Response
  • the random access procedure described in the present disclosure includes but is not limited to the above-mentioned random access procedure.
  • the UE can trigger the random access procedure in many situations.
  • the 3GPP protocol specification document 38.300 lists the trigger scenarios of the random access process, including: initial access performed from the RRC idle state to the RRC connected state, and the RRC inactive state (RRC inactive) to the RRC connected state.
  • the execution process, the RRC connection re-establishment process, the handover when the uplink data arrives in the RRC connected state and the uplink synchronization state of the UE is not synchronized, and the uplink data arrives in the RRC connected state and the UE has no available physical resources for scheduling requests.
  • the process performed from the RRC inactive to the RRC connected state also includes the process in which the UE remains in the RRC inactive after the RRC inactive performs data transmission and does not finally enter the RRC connected state (for example, for small data transmission).
  • the base station will issue a UEinformationRequest message to the UE, which contains a RACH report request indication (rach-reportreq information element), which is used to request the UE to report the RACH report of the random access process.
  • the UE After receiving the UEinformationRequest message containing the indication, the UE includes the RACH report in the UEinformationReponse message and reports it to the base station.
  • the base station uses the RACH report reported by a UE as a sample. Based on enough samples, the base station can analyze whether the current RACH performance meets the demand, and adjust the RACH parameters according to the demand to improve the RACH performance.
  • the base station issues a UEinformationRequest message to the UE, which contains a connection establishment failure report request indication (connEstFailReportReq information element), which is used to request the UE to report the saved connection establishment failure information.
  • the UE After receiving the UEinformationRequest message containing the indication, the UE includes the connection establishment failure report (connEstFailReport information element, referred to as the CEF report in this disclosure) in the UEinformationReponse message and reports it to the base station. If the random access process is performed during the connection establishment process , Then the CEF report will contain information about the random access process.
  • the base station sends a UEinformationRequest message to the UE, which contains a radio link failure report request indication (rlf-ReportReq information element), which is used to request the UE to report the saved radio link failure (Radio Link Failure (RLF) report information.
  • rlf-ReportReq information element radio link failure report request indication
  • the UE After receiving the UEinformationRequest message containing the indication, the UE includes the saved RLF report (rlf-Report information element) in the UEinformationReponse message and reports it to the base station. If a random access process is performed during the RLF process (for example, the RLF is triggered due to a random access failure), then the RLF report will contain information about the random access process.
  • the random access procedure information contained in the CEF report and the RLF report is sometimes also referred to as RACH failure information.
  • RACH information the random access process information contained in the RACH report, CEF report, and RLF report can be collectively referred to as RACH information.
  • CEF report, RLF report and RACH report can be collectively referred to as RACH report.
  • the CEF report can refer to the RRC connection establishment failure report, the RRC connection recovery failure report, and the RRC connection reestablishment failure report; that is to say, the CEF report in this disclosure can be applied to the failure of the RRC connection establishment process, RRC Information when the connection recovery process fails or the RRC connection re-establishment process fails.
  • the RACH report mainly contains two pieces of information about the random access process.
  • One is the number of preamble transmissions (number of preamblesent), which is used to indicate the number of random access preambles sent during the random access process.
  • the RACH parameters that can be adjusted by the base station may include RACH resource configuration, random access preamble division (such as dedicated preamble, group A and group B preamble group division), RACH backoff (backoff) parameters, RACH transmission power control parameters, and so on.
  • the network optimization structure of the NR system follows the above-mentioned framework in LTE, and combines the characteristics of NR to make enhancements, such as beam characteristics.
  • the current RACH report content used in NR includes: the reference downlink frequency information associated with the random access process (such as the absolute frequency of Point A, sub-carrier spacing, bandwidth location information locationAndBandwidth), one or more pairs of random access used The RACH information of each beam corresponding to the incoming resource.
  • the RACH information of each beam includes the beam index value, the number of RACH transmissions attempted on the beam (that is, the number of transmissions of the random access preamble corresponding to the beam), and the random access attempt corresponding to the beam Chronological Order information (the information element rachAttemptChronologicalOrder identified in the form of a bitmap, the leftmost bit corresponds to the first RA attempt, the second bit corresponds to the second RA attempt, and so on , The rightmost bit corresponds to the maximum number of RA attempts supported by the system. If the Nth bit is set to 1, it indicates that the corresponding Nth RA attempt corresponds to the beam associated with the beam index value) and One or more RACH information corresponding to each random access attempt made on the random access resource.
  • the RACH information corresponding to each random access attempt specifically includes the indication information of whether random access competition is detected and the reference signal reception strength of the corresponding beam on the random access resource used by the random access attempt.
  • Received Power (RSRP) indicates whether it is higher than a configured threshold.
  • the RACH report in the NR also includes instructions for indicating whether the uplink carrier associated with the random access is a normal uplink carrier (UL) or a supplementary uplink carrier (SUL).
  • the base station may configure different RACH parameters for different scenarios.
  • the conclusion at the RAN2#108 meeting is to include an identifier in the RACH report .
  • the identifier is used to identify the triggering scene or the triggering reason of the random access process.
  • the UE only reports the RACH information of the most recent successful random access process.
  • the UE is allowed to store up to 8 RACH reports. After the UE enters the RRC idle or inactive state, it still saves the previously generated RACH report. The UE can send the saved RACH report to the network side after entering the connected state again.
  • Fig. 3 is a schematic diagram showing the flow of condition switching.
  • conditional handover a relatively conservative measurement report threshold is set so that the base station obtains the measurement result in advance, and performs handover preparation in advance based on the measurement result and the selected target base station, so that the base station can perform handover conditions under real handover conditions (relative to the conservative Before the measurement report threshold is met, the handover command RRC message containing the CHO candidate cell and the corresponding CHO execution condition is issued to the UE in advance.
  • the RRC message (such as the RRC connection reconfiguration message) supports the inclusion of more than one CHO candidate cell and the CHO configuration corresponding to each CHO candidate cell (that is, the configuration included in the RRC connection reconfiguration message configured by the candidate target cell) and CHO execution conditions.
  • the UE After the UE receives the conditional handover command, it does not immediately perform the handover, but saves the received CHO configuration (that is, the configuration included in the RRC reconfiguration message configured by the target cell), and according to the handover command message carried
  • the CHO execution condition corresponding to the CHO candidate cell starts to monitor the link quality of the source cell or the link quality of the target cell to evaluate whether the CHO execution condition is met.
  • the CHO execution condition may be a measurement event, for example, the condition is measurement event A3 (the signal quality of the neighboring cell is better than the serving cell for a period of time by more than an offset).
  • the neighboring cell corresponds to the CHO candidate target cell.
  • One CHO candidate cell can correspond to one or more than one CHO execution conditions.
  • This disclosure mainly proposes a solution to the problem of how the UE performs RACH report reporting. Furthermore, in order to support more refined RACH reporting but at the same time save signaling overhead, how to set the random access trigger scenario identifier in the RACH report and how to set it in the UE How to deal with the random access report corresponding to an incomplete random access process in the case of supporting storing multiple RACH reports is a concern of this disclosure.
  • the following embodiments of the present disclosure provide specific implementations for this problem.
  • the base station can obtain more accurate RACH information on the premise of saving signaling overhead, and thus based on the accuracy in the RACH information report. Information can be used to adjust RACH parameters more accurately to improve RACH performance and coverage performance.
  • Fig. 4 shows a flowchart of a random access report method performed by a user equipment UE according to an embodiment of the present disclosure.
  • the random access report method performed by the user equipment UE of the present disclosure includes: step S401 and step S402.
  • step S401 the UE triggers and executes a random access procedure in a random access trigger scenario.
  • step S402 the UE sends a RACH report corresponding to the random access process to the network side, and the RACH report includes a random access scenario identifier for identifying the random access trigger scenario.
  • the random access trigger scenario is a conditional handover scenario.
  • the RACH report sent to the network side includes a random access scenario identifier for identifying the random access trigger scenario, and it is clear that the random access trigger scenario is a conditional switching scenario. Therefore, a more refined RACH report in a conditional handover scenario can be realized, so that the network side can adjust RACH parameters more accurately based on the refined information in the RACH report, thereby improving RACH performance and coverage performance.
  • This embodiment provides a method for setting the random access process trigger scenario identifier in the RACH report.
  • trigger scenarios for the random access process
  • a straightforward way is to set different information elements/code points for each trigger scene to identify, in the form of enumeration type or bitmap, each value in the enumeration type or each bitmap Each bit corresponds to a trigger scene.
  • this method needs to use more bits, which increases the signaling overhead.
  • the network side does not need to obtain such accurate information to distinguish each trigger scenario, which is unnecessary for the network side. of.
  • the random access trigger scenario is as described above, including the following:
  • Scenario 1 Initial access performed from the RRC idle state to the RRC connected state. For example, the random access process triggered by the RRC connection establishment process.
  • Scenario 2 Transition from the RRC inactive state (RRC inactive) to the RRC connected state and executed, for example, the random access process triggered by the RRC connection recovery process.
  • this scenario also includes the random access process performed in the RRC inactive state, but after the random access process ends, it does not enter the RRC connected state but remains in the RRC inactive state, such as performing small data packets through random access.
  • the process of sending (early data transmission).
  • Scenario 3 RRC connection re-establishment process.
  • the RRC re-establishment process for restoring the link connection is triggered to trigger the random access process to the re-established cell.
  • Scenario 4 When uplink data arrives in the RRC connected state and the uplink synchronization state of the UE is out of synchronization. This scenario occurs at the MAC layer.
  • Scenario 5 When uplink data arrives in the RRC connected state and the UE does not have available physical uplink control channel resources for scheduling requests. This scenario occurs at the MAC layer.
  • Scenario 6 System information (other system information other than the main system information block and system information block 1 that are not broadcast by the on-demand cell) request; for example, the system information request process based on message 3, the UE through random access Message 3 in the incoming process sends the system information request RRC message to the network side;
  • Scenario 7 Scheduling Request (SR) transmission reaches the maximum number of transmissions (that is, the scheduling request fails). This scenario occurs at the MAC layer.
  • SR Scheduling Request
  • Scene 8 Switch. The process of changing the primary cell or primary and secondary cell is usually accompanied by an update of security parameters.
  • Scenario 9 Synchronous reconfiguration request triggered by RRC, such as used to update the security parameters of the cell
  • Scenario 10 It is used to establish uplink time alignment of the secondary cell Scell.
  • the base station triggers the random access process for obtaining the uplink time alignment by sending a physical downlink control channel command (Physical Downlink Control CHannel order, PDCCH order) including RA resource allocation to the UE.
  • a physical downlink control channel command Physical Downlink Control CHannel order, PDCCH order
  • Scenario 11 When downlink data arrives in the RRC connected state and the uplink synchronization state of the UE at this time is out of synchronization, etc. Generally, the base station triggers the random access process for obtaining the uplink time alignment by sending the PDCCH order including the RA resource allocation to the UE.
  • Scenario 12 Beam failure recovery process. This scenario occurs at the MAC layer. It is used to report the beam failure to the network side when the beam fails to restore the beam transmission.
  • the UE sets the random access scenario identifier in the RACH report according to the following method:
  • the UE sets the random access scenario identifier as "initial access"
  • the UE sets the random access scenario identifier as "handover"
  • the UE sets the random access scenario identifier as "PDCCH initiated"
  • the UE sets the random access scenario identifier as "beam failure recovery”.
  • the foregoing manner does not limit the name of the foregoing random access scenario identifier, and other names may also be used.
  • the UE sets the random access scenario identifier as "uplink time alignment initiated by the network side", or the UE sets the random access scenario identifier as "other" to distinguish it from other scenarios.
  • the UE sets the random access scenario identifier in the RACH report according to the following method:
  • the UE sets the random access scenario identifier as "initial access"
  • the UE sets the random access scenario identifier as "handover"
  • the UE sets the random access scenario identifier to "other";
  • the UE sets the random access scenario identifier as "beam failure recovery”.
  • the UE sets the random access scenario identifier in the RACH report according to the following method:
  • the UE sets the random access scenario identifier as "initial access"
  • the UE sets the random access scenario identifier as "Handover"; otherwise, if the random access process is used in scenario 8 and the RRC message used to trigger the handover does not include random access dedicated configuration (used to allocate dedicated random access resources), the UE sets The random access scenario is identified as "initial access”.
  • the UE sets the random access scenario identifier to "other"; alternatively, if the random access process is used in scenarios 9-11 and is used to allocate random access
  • the UE sets the random access scenario identifier to "other"; otherwise, if the random access process is used for scenario 9 ⁇
  • the UE sets the random access scene identifier as "initial access”.
  • the UE sets the random access scenario identifier as "beam failure recovery”.
  • the foregoing method does not limit the name of the foregoing random access scenario identifier, and other names can also be used, as described above.
  • the random access scenario identifier "initial access” is used to indicate that the random access process uses the same random access configuration as the random access process performed during initial access. Preferably, it refers to the random access configuration carried in the system information broadcast by the serving cell.
  • the random access scenario identifier "other" can be used to identify that the random access process is a random access process other than the handover or RRC synchronization reconfiguration process initiated by the network side.
  • the random access trigger scenario identifier is set as described above.
  • the UE when the UE saves the RACH report corresponding to the random access process or is described as including an item corresponding to a random access process in the RACH report, the random access trigger scenario identifier is set as described above.
  • the UE when the UE generates an RRC message (UE information response) containing the RACH report, it sets the random access scenario identifier corresponding to the RACH report in the message as described above.
  • the operation of setting the random access scenario identifier is performed at the UE RRC layer.
  • for some random access scenarios such as random access scenarios 4, 5, 7, 10, 11, etc., are initiated at the MAC layer.
  • the MAC layer indicates to the RRC layer the initiated random access location.
  • the corresponding random access trigger scenario Preferably, the MAC layer indicates the information to the RRC layer after a random access process is completed; alternatively, the MAC layer indicates the information to the RRC layer when a random access process is initiated.
  • the UE can maintain a variable (such as VarRACH-report) to save multiple RACH reports.
  • the variable contains multiple entries, and each project is associated with The RACH report corresponding to a random access procedure performed by the UE.
  • the RACH report in this embodiment can also be described as one item in the RACH report.
  • Random access configuration refers to random access parameter configuration or random access resource configuration.
  • This embodiment proposes a method for storing and reporting RACH reports executed on the UE.
  • the UE does not include information about an unfinished random access process in the RACH report, so that the network side excludes the samples corresponding to the unfinished random access process during network parameter optimization, so that the network parameters are optimized more acurrate.
  • the network side excludes the samples corresponding to the unfinished random access process during network parameter optimization, so that the network parameters are optimized more acurrate.
  • an unfinished random access process which is also called an ongoing random access process.
  • Case 1 When receiving an RRC message containing the information element (set to true) for the RACH report request from the network side, the UE prepares to return the RRC message for response to the network side, and at this time, there is an ongoing message in the MAC layer. Random access process performed. That is to say, when the UE reports the RACH report, the MAC layer has an ongoing random access process, which is in the unfinished stage.
  • the information element used to request the UE to report the RACH information/report may be the rach-ReportReq information element or the rlf-ReportReq information element or the connEstFailReportReq information element as described above;
  • the RRC message containing the information element used for the RACH report request is UEinformationrequest message, and the response message is a UEinformationresponse message.
  • Case 2 When the MAC entity is performing a random access process A, if another random access process B is triggered at this time, the UE can stop the random access process A being performed and start to perform the random access process B. At this time, the random access process A can be referred to as a suspended incomplete random access process.
  • Case 3 When the MAC entity is reset, the UE will stop the ongoing random access process at the MAC layer. Resetting the MAC entity is generally triggered by the RRC layer, such as during the initialization phase of the RRC connection re-establishment process, or when the UE receives an RRCrelease message to release the RRC connection.
  • the UE does not include the RACH information corresponding to an uncompleted random access process in the UE variables used to save the RACH report, and can be implemented as follows: if the UE supports saving the RACH report, when a random access process is completed, The UE performs one or more of the following operations:
  • Operation 1 Include an item in the UE variable VarRACH-Report.
  • the UE variable is used to save the RACH report.
  • the included item corresponds to the completed random access procedure.
  • Operation 2 Set the RACH information in the RACH report according to the information corresponding to the random access obtained from the MAC layer, including one or more of the following: set the absoluteFrequencyPointA information element as the reference resource block associated with the random access process ( Resource Block (RB) absolute frequency; set the random access trigger scenario identifier according to the random access trigger scenario, and each beam index corresponding to the used random access resource includes the following parameters: set beam index value Is the index value of the beam; set the numerOfPreambleSentOnSSB information element to the number of RACH attempts attempted on the beam; set rachAttemptChronologicalOrder to support the chronological order of the RACH attempts corresponding to the beam index; for each random access Try, according to the chronological order of random access attempts, if contention occurs (that is, the contention is not resolved successfully), set the contentionDetected information element to "True", otherwise set the contentionDetected information element to "false”; if a random access attempt If the beam RSRP of the beam corresponding to the used random access
  • the beam is a synchronization signal physical broadcast signal block (Synchronization Signal/Physical Broadcast Channel block, SS/PBCH block) or a channel state indication reference signal (Channel State Information Reference Signal, CSI-RS).
  • SS/PBCH block Synchronization Signal/Physical Broadcast Channel block
  • CSI-RS Channel State Information Reference Signal
  • the aforementioned beam index is SSB-index
  • the number of RACH attempts information element is numberOfPreambleSentOnSSB
  • the threshold value is the information element rsrp-ThresholdSSB.
  • the above beam index is CSI-RS index
  • the number of RACH attempts information element may be expressed as numberOfPreambleSentOnCsi-rs, and the corresponding threshold value is the information element rsrp-ThresholdCSI-RS.
  • a random access process When a random access process is completed, it is also described as when the RRC layer receives a random access process completion indication from a lower layer (MAC layer).
  • the completion of the random access process may be the successful completion of the random access process, or the failure of the random access process.
  • an assumption is that the RRC layer can learn the start of a random access process, and the RRC layer can learn the start of the random access process from the MAC layer.
  • This embodiment proposes another RACH report storage and reporting method executed on the UE.
  • This embodiment has the same scenario and purpose as the second embodiment.
  • the UE does not include the RACH information corresponding to an unfinished random access process in the UE variable used to save the RACH report, which can be implemented as follows: If the UE supports the saving of the RACH report, the RRC layer When receiving the RACH information corresponding to the preamble of a random access attempt in a random access process, the UE performs the following operations:
  • the UE variable VarRACH-Report does not contain an item for the random access process, then include an item for the random access process in the UE variable VarRACH-Report, and set the corresponding RACH report according to the received RACH information Otherwise, if the UE variable VarRACH-Report already contains an item of the random access procedure, set the information element in the corresponding RACH report according to the received RACH information.
  • the UE variable is used to store the RACH report, and the included item corresponds to the random access procedure.
  • the UE sets the information elements in the corresponding RACH report according to the received RACH information, as described in operation 2 in embodiment 2.
  • This embodiment is different from Embodiment 2 in that, for the RACH information corresponding to an unfinished random access procedure, the RRC layer includes and saves the RACH information for each RACH attempt from the lower layer.
  • the RACH report and when the UE is sending or reporting a RACH report, if one or more of the saved RACH reports correspond to an incomplete random access process, the UE will not include it in the UEinformationresponse and report it To the network side.
  • the UE may delete the RACH report corresponding to the incomplete random access procedure when performing the sending or reporting of the RACH report.
  • the RACH report deleted here refers to at least the random access process A referred to in case 2 in embodiment 2 or the random access process described in case 3, that is, the random access process that was previously suspended, but
  • the UE executes the sending or reporting of the RACH report, the random access procedure has been terminated and is not in the ongoing stage.
  • the RRC layer receives an indication from the MAC layer that the ongoing random access process is not completed ( abortion) information, the RRC layer deletes the corresponding RACH report item based on the indication, that is, when Case 2 or Case 3 occurs, the MAC layer indicates to the RRC layer that the current random access process is not completed.
  • an assumption is that the RRC layer can learn the start of a random access process, and the RRC layer can learn the start of the random access process from the MAC layer.
  • This embodiment proposes another RACH report storage and reporting method executed on the UE. Different from Embodiment 2 and Embodiment 3, when the UE reports the RACH report, if there is a RACH report corresponding to an uncompleted random access process in the saved RACH report, the UE still reports it to the network side, and The network side decides whether to use the RACH report as a sample for network parameter optimization.
  • the UE is implemented as follows:
  • the UE If the UE supports saving RACH reports, when a random access procedure is completed, the UE performs one or more of the following operations:
  • Operation 1 Include an item in the UE variable VarRACH-Report.
  • the UE variable is used to save the RACH report.
  • the included item corresponds to the completed random access procedure.
  • Operation 2 Same as operation 2 in embodiment 2.
  • the UE When the UE receives the RRC message containing the indication for requesting the UE to report the RACH report, if there is currently an ongoing random access procedure that has not yet been completed, the UE performs one or more of the following operations:
  • Operation 3 Include an item in the UE variable VarRACH-Report.
  • the UE variable is used to save the RACH report.
  • the included item corresponds to the ongoing random access procedure.
  • Operation 4 Include one or more RACH reports stored in the UE variable VarRACH-Report in the response RRC message.
  • the response RRC message includes the RACH report corresponding to the ongoing random access process, wherein the RACH information setting in the RACH report is the same as operation 2.
  • Operation 6 Include an indication information in the corresponding RACH report, and the indication information is used to inform the network that the corresponding RACH report is for an incomplete random access process.
  • Operation 7 Send the response RRC message including the RACH report to the network side.
  • This embodiment proposes a RACH report management method.
  • the UE when the UE includes an item corresponding to the just completed or ongoing random access procedure in the UE variable VarRACH-Report used to save the RACH report, if the RACH in the UE variable at this time The data of the reported item exceeds the maximum number supported by the UE, and the UE deletes the oldest one or more items in the saved RACH report, so as to save the new RACH report item. Alternatively, the UE deletes the RACH report item corresponding to the incomplete random access procedure in the saved RACH report.
  • the unfinished random access process is as in case 2 and case 3 in embodiment 2.
  • This embodiment proposes a RACH reporting method in a conditional handover scenario.
  • the network side can know that the corresponding RACH report is for conditional handover, and can be distinguished from the RACH reports in other triggering scenarios, so as to correspond to the conditional handover based on this
  • the switching parameters are adjusted and configured.
  • Step 1 The UE triggers and executes the conditional switching process.
  • the conditional handover process the UE performs a random access process to the target cell.
  • Step 2 If the UE supports the RACH report, the UE sets the random access scenario identifier in the RACH report as conditional handover.
  • the random access scenario identifier is used to indicate the trigger scenario (or trigger reason, trigger type, trigger purpose, etc.) of the random access process corresponding to the RACH report as described above. That is to say, the UE includes an indication information in the RACH report, which is used to indicate that the RACH report is for a random access process performed in a conditional handover process.
  • the RACH report refers to the random access process performed during the conditional switching process in step 1.
  • the UE can maintain a variable (such as VarRACH-report) to save multiple RACH reports.
  • the variable contains multiple entries, and each project is associated with The RACH report corresponding to a random access procedure performed by the UE.
  • the RACH report in this embodiment can also be described as one item in the RACH report.
  • the random access scenario identifier in the RACH report is set as conditional handover.
  • the UE when generating or setting the RRC message containing the RACH report to be sent to the network side, the UE sets the random access scenario identifier in the corresponding RACH report as the conditional handover.
  • the NR system supports both a four-step random access process and a two-step random access process. Taking into account the different resources used by these two types of random access, the network side needs to distinguish whether the RACH report obtained from the UE is for which type of random access, that is, for four-step random access or for two-step random access. , In order to adjust and optimize the corresponding parameters.
  • This embodiment provides a RACH reporting method in a two-step random access scenario.
  • the UE RRC layer obtains the random access type used by the random access attempt from the MAC layer, and combines it It is included in the corresponding RACH report to inform the network side, so that the network side can distinguish whether the RACH report is for two-step random access or four-step random access.
  • Step 1 The MAC layer executes the random access process, and sets the value of the random access type variable RA_TYPE to "2-stepRA" or "4-stepRA” according to whether the triggered random access process is two-step or four-step. For example, if the random access process is initiated by the PDCCH order and the ra-PreambleIndex provided in the PDCCH to indicate the random access preamble is not "0b000000” or the random access process is triggered by a system information request and is used If the random access resource requested by the system information is provided by the RRC message, the UE sets the RA_TYPE to "4-stepRA"; if the threshold parameter rsrp-ThresholdSSB-2stepCBRA for determining whether to use two-step random access is configured, and the following The RSRP referenced by the path loss is above the configured threshold parameter or the BandWidth Part (BWP) selected by the UE for the random access process is only configured with two-step random access resources but not four-step
  • Step 2 The MAC layer indicates the random access type to the RRC layer.
  • the random access type is the value of the variable RA_TYPE.
  • the MAC layer indicates to the RRC layer the random access type corresponding to the random access preamble transmission before each time the random access preamble transmission process is executed.
  • the MAC layer indicates the random access type to the RRC layer during the initialization phase of the random access process and when the random access type changes in the subsequent random access process.
  • the MAC layer randomly accesses one or more (such as 2-stepRA, 4-stepRA or 2-stepRA-to-4-stepRA) corresponding to the random access process The type is indicated to the RRC layer.
  • Step 3 When the RRC layer saves the RACH report, that is, when setting the UE variable VarRACH-report, it sets the random access type information element to the value of the random access type obtained from the MAC layer.
  • the random access type information element is included for each random access attempt (such as the transmission of each random access preamble); alternatively, the random access type information element is for the entire random access attempt. Included in the access process.
  • the RRC layer sets the value of the random access type information element to the value obtained from the MAC layer when receiving the report RACH report request from the network side to report the RACH report to the network side.
  • the RACH report reported to the network side is included in the RRC message of the UE information response.
  • FIG. 5 is a block diagram showing a user equipment 50 according to an embodiment of the present disclosure.
  • the user equipment 50 includes a processor 510 and a memory 520.
  • the processor 510 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 520 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories.
  • the memory 520 stores program instructions. When the instruction is run by the processor 510, it can execute the random access report method in the user equipment described in detail in the present disclosure.
  • the program running on the device may be a program that causes the computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU).
  • the program or the information processed by the program can be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • the program for realizing the functions of the various embodiments of the present disclosure may be recorded on a computer-readable recording medium.
  • Corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute these programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium storing a program dynamically for a short period of time, or any other recording medium readable by a computer.
  • circuits for example, single-chip or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification can include general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • the general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuit can be a digital circuit or an analog circuit. In the case of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.
  • present disclosure is not limited to the above-mentioned embodiments. Although various examples of the embodiment have been described, the present disclosure is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

本公开提供一种由用户设备执行的随机接入报告方法和用户设备。由用户设备执行的随机接入报告方法,包括:在随机接入触发场景下触发并执行随机接入过程;以及向网络侧发送与所述随机接入过程对应的随机接入信道RACH报告,该RACH报告中包含用于标识所述随机接入触发场景的随机接入场景标识,所述随机接入触发场景是条件切换场景。由此,能够实现条件切换场景下的更精细化的RACH报告,从而能够提升RACH性能和覆盖性能。

Description

由用户设备执行的随机接入报告方法和用户设备 技术领域
本公开涉及无线通信技术领域,更具体地,本公开涉及一种用户设备、基站和相关方法。
背景技术
无线网络中通过网络优化可以达到优化网络性能的目的。一般对现有已部署和运行的网络进行数据采集和数据分析等手段,找出影响网络质量的原因,并且通过修改所配置的网络参数、调整网络结构和部署的设备等手段来提升网络性能。对于自配置和自优化网络(Self-configuration and Self-Optimization Network,SON),指的是基于用户设备和/或基站的测量/性能测量来自动调节网络的过程。网络侧可以配置UE执行用于SON的测量。SON功能包含很多方面,如用于降低运行商的邻区管理负担的自动邻区关系功能(ANR,Automatic Neighbour Relation Function)、用于均衡不同小区之间负责的移动负载均衡功能(MLB,Mobility Load Balancing),用于优化移动性能的移动鲁棒性优化功能(MRO,Mobility Robustness Optimization)、用于优化随机接入信道参数的随机接入信道优化功能和用于优化覆盖以及MRO的无线链路失败报告功能等。
2018年6月,在第三代合作伙伴计划(3rd Generation Partnership Project:3GPP)RAN#80次全会上,一个关于新无线技术(NR,New Radio)和长期演进系统(Long Term Evolution,LTE)进一步增强的新工作项目(参见RP-182105:Study on RAN-centric Data Collection and Utilization for LTE and NR)获得批准。这个研究项目的目标之一就是在NR网络中实现SON的功能,包括ANR、随机接入信道性能以及用于覆盖优化的连接失败报告等。
本公开旨在实现NR网络中SON功能中的随机接入信道性能和由于随机接入问题而导致的覆盖优化问题,更进一步地,解决如何更精确地向网络侧反馈随机接入过程信息的问题。
发明内容
本公开的目的在于,提供一种由用户设备执行的随机接入报告方法以及用户设备,能够实现条件切换场景下的更精细化的RACH报告,使得网络侧能够基于RACH报告中的精细信息来更准确地进行RACH参数调整,从而能够提升RACH性能和覆盖性能。
根据本公开的第一方面,提供了一种由用户设备执行的随机接入报告方法,包括:在随机接入触发场景下触发并执行随机接入过程;以及向网络侧发送与所述随机接入过程对应的随机接入信道RACH报告,该RACH报告中包含用于标识所述随机接入触发场景的随机接入场景标识,所述随机接入触发场景是条件切换场景。
在上述方法中,可以是,将所述RACH报告中的所述随机接入场景标识设置为条件切换。
在上述方法中,可以是,设置为条件切换的所述随机接入场景标识表示对应的随机接入过程使用了条件切换时的随机接入配置。
在上述方法中,可以是,通过用于保存RACH报告的变量来保存多个RACH报告。
在上述方法中,可以是,所述变量中包含多个项目,每一个项目关联到所述用户设备执行的一个随机接入过程所对应的RACH报告。
在上述方法中,可以是,在所述随机接入过程完成时或发起时,向所述变量中加入一个对应于该随机接入过程的RACH报告项。
在上述方法中,可以是,在向所述变量中加入所述RACH报告项时,将所关联的RACH报告中的随机接入场景标识设置为条件切换。
在上述方法中,可以是,将所述RACH报告包含在无线资源控制RRC消息中发送给网络侧。
在上述方法中,可以是,在生成或设置所述RRC消息时,将所包含的所述RACH报告中的随机接入场景标识设置为条件切换。
根据本公开的第二方面,提供了一种用户设备,包括:处理器;以及存储器,存储有指令;其中,所述指令在由所述处理器运行时执行上述方法。
发明效果
根据本公开的由用户设备执行的随机接入报告方法以及用户设备,能够实现条件切换场景下的更精细化的RACH报告,使得网络侧能够基于RACH报告中的精细信息来更准确地进行RACH参数调整,从而能够提升RACH性能和覆盖性能。
附图说明
通过下文结合附图的详细描述,本公开的上述和其它特征将会变得更加明显,其中:
图1示出了基于竞争的随机接入CBRA的过程;
图2示出了基于非竞争的随机接入CFRA的过程;
图3示出了条件切换的流程的示意图;
图4示出了根据本公开实施例的由用户设备执行的随机接入报告方法的流程图。
图5示出了根据本公开实施例的用户设备的框图。
具体实施方式
根据结合附图对本公开示例性实施例的以下详细描述,本公开的其它方面、优势和突出特征对于本领域技术人员将变得显而易见。
在本公开中,术语“包括”和“含有”及其派生词意为包括而非限制;术语“或”是包含性的,意为和/或。
在本说明书中,下述用于描述本公开原理的各种实施例只是说明,不应该以任何方式解释为限制公开的范围。参照附图的下述描述用于帮助全面理解由权利要求及其等同物限定的本公开的示例性实施例。下述描述包括多种具体细节来帮助理解,但这些细节应认为仅仅是示例性的。因此,本领域普通技术人员应认识到,在不背离本公开的范围和精神的情况下,可以对本文中描述的实施例进行多种改变和修改。此外,为了清楚和简洁起见,省略了公知功能和结构的描述。此外,贯穿附图,相同参考数字用于相似功能和操作。
下文以NR/LTE移动通信系统作为示例应用环境,具体描述了根据本 公开的多个实施方式。然而,需要指出的是,本公开不限于以下实施方式,而是可适用于更多其它的无线通信系统,如连接到5G核心网的LTE系统等。
本公开中的基站可以是任何类型基站,包含Node B、增强基站eNB,也可以是5G通信系统基站gNB、或者微基站、微微基站、宏基站、家庭基站等;所述小区也可以是上述任何类型基站下的小区,小区也可以是光束(beam)、传输点(Transmission point,TRP),基站也可以是组成基站的中心单元(gNB-Central Unit,gNB-CU)或分布式单元(gNB-Distributed Unit,gNB-DU)。若无特殊说明,在本公开中,小区和基站的概念可以互相替换;LTE系统也用于指代5G及其之后的LTE系统(如称为eLTE系统,或者可以连接到5G核心网的LTE系统),同时LTE可以用演进的通用陆地无线接入(Evolved Universal Terrestrial Radio Access,E-UTRA)或演进的通用陆地无线接入网E-UTRAN来替换。在本公开中,切换指的是网络侧发起的主小区(Primary Cell,PCell)的变更,包含小区间的主小区变更也包含小区内的主小区变更,即UE的主小区从源小区变更为目标小区,其中源小区和目标小区可以是同一个小区也可以是不同的小区,在此过程中,用于接入层安全的秘钥或安全算法也可随之更新。源小区也称为源基站,也可以是源光束(beam)、源传输点(Transmission point,TRP),目标小区也可称为目标基站,也可以是目标光束、目标传输点。源小区指的是切换过程发起之前所连接的为UE服务的小区即UE从之接收包含切换命令的RRC消息的小区。目标小区指的是切换过程成功完成之后UE所连接的为UE服务的小区,或者说是切换命令中所包含的目标小区标识所指示的小区、UE收到执行切换时所接入的小区。本公开所述切换命令用于触发UE执行切换,在NR系统中是包含同步重配置(Reconfigurationwithsync)信息元素的RRC重配置消息,更进一步地,是包含用于主小区组(Master Cell Group,MCG)的同步重配置(Reconfigurationwithsync)信息元素的RRC重配置消息。此时,切换也可称为同步重配置。在LTE系统中是包含移动控制信息(MobilityControlInformation)信息元素的RRC连接重配置消息。其中,所述同步重配置信息元素或移动控制信息信息元素包含目标小区的配置信息,例如目标小区标识、目标小区频率、目标小区的公共配置如系统信息、UE接入到目标小区所使用的随机接入配置、UE在目标小区的安全参数配置、 UE在目标小区的无线承载配置等。不同的实施例之间也可以结合工作,比如不同实施例中相同的变量/参数/名词的做相同解释。为便于描述,本公开中RRC重配置消息和RRC连接重配置消息等同;同理,其响应消息RRC重配置完成消息和RRC连接重配置完成消息等同。切换命令和包含切换命令的RRC消息等同,指触发UE执行切换的RRC消息或RRC消息中的配置。切换配置指切换命令中的全部或部分配置。取消、释放、删除、清空和清除等可以替换。执行、使用和应用可替换。配置和重配置可以替换。监测(monitor)和检测(detect)可替换。条件切换命令和条件切换配置可替换。
下面先对本公开涉及到的一些现有概念和机制进行说明。值得注意的是,在下文的描述中的一些命名仅是实例说明性的,而不是限制性的,也可以作其他命名。
物理随机接入信道资源:Physical Random Access Channel(PRACH)resource。基站通过系统信息广播小区所使用的物理随机接入信道参数配置,本公开中,物理随机接入信道资源PRACH resource可以指用于随机接入的物理频率资源和/或时域资源和/或码域资源(如preamble)。
随机接入信道:Random Access Channel,RACH。指用于发送随机接入前导的信道,本公开中,RACH既可以指传输信道RACH,也可以指物理随机接入信道PRACH,不作区分。RACH参数/配置指实现随机接入功能的无线配置,包括PRACH的相关配置,比如前导最大发送次数、功率抬升参数、随机接入响应接收窗大小、MAC竞争解决定时器配置、PRACH时频资源配置、消息1(即preamble)子载波间隔、用于指示每个RACH时机(RACH occasion,RO)对应的同步信道块(Synchronization Signal Block,SSB)个数信息和每个SSB对应的基于竞争的随机前导preamble个数的配置(由ssb-perRACH-OccasionAndCB-PreamblesPerSSB信息元素配置)、退避参数(scalingFactorBI信息元素中)等。
随机接入RA过程:
现有NR/LTE机制中,随机接入过程有两种:基于竞争的随机接入(Contention Based Random Access,CBRA)和基于非竞争的随机接入(即 无竞争随机接入(Contention Free Random Access,CFRA))。CBRA的过程如图1所示,分为四个步骤:第一步,用于UE向基站发送消息1(即随机接入前导preamble);第二步:UE接收来自基站的消息2(即随机接入响应Random Access Response,RAR);第三步:UE发送消息3(由消息2中的上行许可uplink grant所调度的上行传输),消息3中一般用于向基站发送UE标识、用于无线资源控制(Radio Resource Control,RRC)连接建立/恢复/重建立的RRC消息、用于随机接入竞争解决的UE竞争解决标识等,在早期数据传输中,也可包含用户面数据;第四步:UE接收来自基站的消息4(即用于竞争解决的消息)。CBRA中所使用的PRACH资源是很多UE共用的,当UE完成CBRA的随机接入上述四个步骤且竞争解决成功后,随机接入过程成功完成。CFRA的过程如图2所示,分为两个步骤:第一步:用于UE向基站发送消息1(即随机接入前导preamble);第二步:UE接收来自基站的消息2(即随机接入响应Random Access Response,RAR)。成功接收消息1关联的消息2后,UE认为CFRA过程成功完成。CFRA一般由基站预先为UE分配专用的PRACH资源如preamble(图2中称为第0步),所以没有竞争存在。当前的NR中正在引入两步随机接入过程。将上述四步随机接入过程中的第一步和第三步合并在同一个步骤发送称消息A。也就是消息A包含一个随机接入前导和随后关联的PUSCH负载,PUSCH负载的内容和消息3中所包含的内容一致,其中可以包含RRC消息,也可以是用户面数据、MAC控制元素如缓存状态报告和UE标识等。第二步和第四步合并成同一个步骤称消息B。消息B是两步随机接入过程中对消息A的响应,它所包含的内容与上述消息2和消息4的内容相似,可包括用于竞争解决的响应(竞争解决标识、随机接入前导标识、UE标识等)、回退(fallback)指示、退避(backoff)指示、时间提前命令、上行许可,也可以包括用于响应消息A中包含的RRC消息对应的响应RRC消息等。相比四步随机接入,两步随机接入过程能够缩短随机接入的时延。通常两步随机接入采用和四步随机接入不同的随机接入资源配置。UE可以在两步随机接入时回退到四步随机接入的过程,比如当收到网络侧发来的回退随机接入响应(fallback Random Access Response,fallbackRAR)时,或者当两步随机接入尝试消息A的发送次数超过一个配置的最大次数时等。本公开所 述随机接入过程包含但不限于上述随机接入过程。
UE在多种情况下可以触发随机接入过程。3GPP协议规范文档38.300中列出了随机接入过程的触发场景,包含:从RRC空闲态转入RRC连接态而执行的初始接入、从RRC不活动态(RRC inactive)转入到RRC连接态而执行过程、RRC连接重建立过程、切换、在RRC连接态时上行数据到达而UE的上行同步状态为不同步时、在RRC连接态时上行数据到达而UE没有用于调度请求的可用的物理上行控制信道资源时、调度请求发送到达最大发送次数(即调度请求失败)、RRC触发的同步重配置请求、系统信息(基于请求的小区没有广播的除主系统信息块和系统信息块1之外的其他系统信息)请求、用于辅小区Scell的上行时间对齐的建立、波束失败恢复过程和处于RRC连接态时有下行数据到达而此时UE的上行同步状态为不同步时等。此处从RRC inactive转入到RRC连接态而执行的过程也包括了UE在RRC inactive执行数据发送后又保持在RRC inactive而并未最终进入RRC连接态的过程(如用于小数据传输)。
RACH报告:
在LTE系统中,对SON功能中的RACH性能,基站会下发UEinformationRequest消息给UE,其中包含RACH报告请求指示(rach-reportreq信息元素),用于请求UE上报随机接入过程的RACH报告。收到包含该指示的UEinformationRequest消息后,UE将RACH报告包含在UEinformationReponse消息中报告给基站。基站将一个UE上报的RACH报告作为一个样本。基于足够多的多个样本,基站可以分析当前RACH性能是否满足需求,并按照需求调整RACH参数,来提升RACH性能。类似的,对于SON功能中的覆盖性能,基站下发UEinformationRequest消息给UE,其中包含连接建立失败报告请求指示(connEstFailReportReq信息元素),用于请求UE上报所保存的连接建立失败信息。收到包含该指示的UEinformationRequest消息后,UE将连接建立失败报告(connEstFailReport信息元素,本公开中称CEF报告)包含在UEinformationReponse消息中报告给基站,若所述连接建立过程中执行了随机接入过程,那么CEF报告中会包含对该随机接入过程的信息。对于SON功能中的移动鲁棒性性能,基站下发UEinformationRequest消息给UE,其中包含无线链路失败报告请求 指示(rlf-ReportReq信息元素),用于请求UE上报所保存的无线链路失败(Radio Link Failure,RLF)报告信息。收到包含该指示的UEinformationRequest消息后,UE将所保存的RLF报告(rlf-Report信息元素)包含在UEinformationReponse消息中报告给基站。若所述RLF过程中执行了随机接入过程(如RLF是由于随机接入失败而触发的),那么RLF报告中会包含对该随机接入过程的信息。
为便于描述,本公开中,包含在CEF报告和RLF报告中的随机接入过程信息有时也称为RACH失败信息。若如无特殊说明,包含在RACH报告、CEF报告和RLF报告中的随机接入过程信息都可统称为RACH信息。基于此描述,CEF报告、RLF报告和RACH报告可统称为RACH报告。所述CEF报告可以指RRC连接建立失败报告,也可以指RRC连接恢复失败报告,还可以指RRC连接重建立失败报告;也就是说本公开中的CEF报告可以应用于RRC连接建立过程失败、RRC连接恢复过程失败或RRC连接重建立过程失败的情况下的信息。
在LTE中,RACH报告中主要包含两个关于随机接入过程的信息,一个是随机接入前导发送次数(numberofpreamblesent),用于指示在随机接入过程中,随机接入前导发送的次数,对应于MAC层的PREAMBLE_TRANSMISSION_COUNTER计数值;另一个是竞争检测指示(contentiondetected),用于指示对至少一个发送的随机接入前导是否检测到竞争。基站可以调整的RACH参数可以包括RACH资源配置、随机接入前导划分(如划分为专用前导、A组和B组的前导分组划分)、RACH回退(backoff)参数、RACH发送功率控制参数等。
NR系统的网络优化结构沿用了LTE中的上述框架,并结合NR的特性做了增强,如波束特性等。目前NR中已采用的RACH报告内容包含:随机接入过程所关联的参考下行频率信息(如Point A的绝对频率、子载波间隔、带宽位置信息locationAndBandwidth),一个或多个对所使用的随机接入资源所对应的每波束的RACH信息。每一个波束的RACH信息包括波束索引值、在该波束上所尝试的RACH发送的个数(即该波束上所对应的随机接入前导preamble的发送次数)、该波束所对应的随机接入尝试的时间顺序(Chronological Order)信息(用一个比特位图的形式来标识的信息元素 rachAttemptChronologicalOrder,最左边的比特对应于第一次RA尝试,第二个比特对应于第二次RA尝试,以此类推,最右边的比特对应于系统所支持的最大次数的RA尝试。若第N个比特置为1,则指示对应的第N次RA尝试是对应于所述波束索引值所关联的波束的)和一个或多个的在随机接入资源上所作的每一次随机接入尝试所对应的RACH信息。每一次随机接入尝试所对应的RACH信息具体包括了是否检测到了随机接入竞争的指示信息和该随机接入尝试所使用的随机接入资源上所对应的波束的参考信号接收强度(Reference Signal Received Power,RSRP)是否高于一个配置的门限值的指示信息。此外NR中的RACH报告还包括用于指示随机接入所关联的上行载波是正常上行载波(UL)还是补充上行载波(supplementary UpLink,SUL)。
考虑到NR中有更多的随机接入触发场景,基站可能为不同的场景配置不同的RACH参数,为了更精细化RACH参数优化,RAN2#108次会议上的结论是在RACH报告中包含一个标识,所述标识用于标识随机接入过程触发的场景或者触发原因。不同于LTE中UE仅上报最近一次成功的随机接入过程的RACH信息,NR中允许UE保存至多8个RACH报告。UE在进入到RRC idle或inactive状态后,仍保存之前生成的RACH报告。UE可在再次进入连接态后将所保存的RACH报告发送给网络侧。
基于条件的切换:
在传统切换过程中,一种导致切换失败而造成较长时间数据传输中断的原因是切换命令下发的不及时导致的切换命令接收失败。对于该问题,Release 16引入了条件切换(conditional handover,CHO)。图3是表示条件切换的流程的示意图。在条件切换中,设置相对保守的测量报告门限,使得基站提前获取测量结果,并根据测量结果和选定的目标基站提前执行切换准备,这样基站可以在真正的切换条件(相对于所述保守的测量报告门限)满足之前,提前将包含CHO候选小区和相对应的CHO执行条件的切换命令RRC消息下发给UE。所述RRC消息(如RRC连接重配置消息)中支持包含多于一个的CHO候选小区以及每一个CHO候选小区对应的CHO配置(即候选目标小区所配置RRC连接重配置消息所包含的配置)和CHO执行条件。UE收到条件切换命令后,并不会立即执行切换,而是保 存所接收到的CHO配置(即目标小区所配置的RRC重配置消息中所包含的配置),并根据切换命令消息中携带的CHO候选小区对应的CHO执行条件开始监测源小区的链路质量或目标小区的链路质量以评估CHO执行条件是否满足。只有当监测到所配置的一个或多个CHO执行条件满足时,UE才开始根据所保存的CHO配置执行切换,接入到目标小区。CHO执行条件可以是一个测量事件,比如所述条件是测量事件A3(在持续一段时间内邻小区比服务小区信号质量好过一个偏移量)。所述邻小区对应CHO候选目标小区。一个CHO候选小区可以对应一个或多于一个CHO执行条件。当对一个候选小区配置了多个CHO执行条件时,只有当所有CHO执行条件都满足时,UE才开始执行对应的切换。一般来说,目前3GPP标准规范36.331和38.331(参见5.5.4章节)定义的所有测量事件,如A1~A5,都可作为CHO执行条件包含在CHO切换命令中。
本公开主要就UE如何进行RACH报告上报的问题提出解决方法,更进一步地,为了支持更精细化的RACH报告但同时节省信令开销,如何设置RACH报告中的随机接入触发场景标识以及在UE支持保存多个RACH报告的情况下如何处理一个未完成的随机接入过程对应的随机接入报告的问题是本公开所关注的问题。本公开下述实施例就该问题给出具体的实施方式,通过本公开所述解决方法,基站可以在节省信令开销的前提下获取更为精确的RACH信息,从而基于RACH信息报告中的精确信息更准确地进行RACH参数调整,提升RACH性能和覆盖性能。
图4示出了根据本公开实施例的由用户设备UE执行的随机接入报告方法的流程图。
如图4所示,本公开的用户设备UE执行的随机接入报告方法包括:步骤S401和步骤S402。在步骤S401中,UE在随机接入触发场景下触发并执行随机接入过程。在步骤S402中,UE向网络侧发送与所述随机接入过程对应的RACH报告,该RACH报告中包含用于标识所述随机接入触发场景的随机接入场景标识。并且,所述随机接入触发场景是条件切换场景。
根据上述方法,在向网络侧发送的RACH报告中包含用于标识随机接入触发场景的随机接入场景标识,并且明确了随机接入触发场景是条件切 换场景。因此能够实现条件切换场景下的更精细化的RACH报告,使得网络侧能够基于RACH报告中的精细信息来更准确地进行RACH参数调整,从而能够提升RACH性能和覆盖性能。
实施例1
本实施例给出了一种RACH报告中设置随机接入过程触发场景标识的方法。如前所述,随机接入过程的触发场景有十几种,在后续版本中,还可能引入更多的触发场景。一种直接的方式是为每一种触发场景设置不同的信息元素/码点来标识,采用枚举类型或比特位图的形式,枚举类型中的每一个值或比特位图中的每一个比特分别对应一个触发场景。但这种方法需要使用较多的比特,使得信令开销增大,从另一方面,网络侧并不需要获取如此精确的信息来区分每一种触发场景,这对网络侧来说是不必要的。下述方法中,从所使用的随机接入配置的角度出发,若不同的触发场景使用相同的随机接入配置,则这些触发场景共享同一个触发场景标识,通过这种方式来减少RACH报告中随机接入的比特位数,从而降低信令开销。
该实施例在UE上执行。所述随机接入触发场景如前所述,包含下述:
场景1:从RRC空闲态转入RRC连接态而执行的初始接入。例如RRC连接建立过程所触发的随机接入过程。
场景2:从RRC不活动态(RRC inactive)转入到RRC连接态而执行的,例如RRC连接恢复过程所触发的随机接入过程。此外,该场景还包括在RRC inactive态执行的随机接入过程但在随机接入过程结束后并不进入到RRC连接态而是保持在RRC inactive态的情况,比如通过随机接入进行小数据包发送(早期数据传输)的过程。
场景3:RRC连接重建立过程。通常在MCG链路失败、切换失败、RRC重配置失败或安全完整性校验失败的情况下而触发的用于恢复链路连接的RRC重建立过程中触发向重建立小区的随机接入过程。
场景4:在RRC连接态时上行数据到达而UE的上行同步状态为不同步时。该场景在MAC层发生。
场景5:在RRC连接态时上行数据到达而UE没有用于调度请求的可用的物理上行控制信道资源时。该场景在MAC层发生。
场景6:系统信息(基于请求(on demand)的小区没有广播的除主系 统信息块和系统信息块1之外的其他系统信息)请求;如基于消息3的系统信息请求过程,UE通过随机接入过程中的消息3将系统信息请求RRC消息发送给网络侧;
场景7:调度请求(Scheduling Request,SR)发送到达最大发送次数(即调度请求失败)。该场景在MAC层发生。
场景8:切换。变更主小区或主辅小区的过程,通常伴随安全参数的更新。
场景9:RRC触发的同步重配置请求,如用于更新小区的安全参数
场景10:用于辅小区Scell的上行时间对齐的建立。通常基站通过向UE下发包含RA资源分配的物理下行控制信道命令(Physical Downlink Control CHannel order,PDCCH order)的方式触发用于获取上行时间对齐量的随机接入过程。
场景11:处于RRC连接态时有下行数据到达而此时UE的上行同步状态为不同步时等。通常基站通过向UE下发包含RA资源分配的PDCCH order的方式触发用于获取上行时间对齐量的随机接入过程。
场景12:波束失败恢复过程。该场景在MAC层发生。用于在波束失败时向网络侧报告发生了波束失败以恢复波束传输。
在一种方式1中,UE按照下述方法来设置RACH报告中的随机接入场景标识:
若随机接入过程是用于场景1~7,则UE设置随机接入场景标识为“初始接入”;
若随机接入过程是用于场景8~9的,则UE设置随机接入场景标识为“切换”;
若随机接入过程是用于场景10~11的,则UE设置随机接入场景标识为“PDCCH发起”;
若随机接入过程是用于场景12的,则UE设置随机接入场景标识为“波束失败恢复”。
上述方式中并不限定上述随机接入场景标识的名称,也可以做其他命名。例如上述用于场景10~11时,UE设置随机接入场景标识为“网络侧发起的上行时间对齐”,或者UE设置随机接入场景标识为“其他”,以与其他场景做区分。
在另一种方式2中,UE按照下述方法来设置RACH报告中的随机接入场景标识:
若随机接入过程是用于场景1~7,则UE设置随机接入场景标识为“初始接入”;
若随机接入过程是用于场景8的,则UE设置随机接入场景标识为“切换”;
若随机接入过程是用于场景9~11的,则UE设置随机接入场景标识为“其他”;
若随机接入过程是用于场景12的,则UE设置随机接入场景标识为“波束失败恢复”。
上述方式中并不限定上述随机接入场景标识的名称,也可以做其他命名,同前面所述。
在又一个方式3中,UE按照下述方法来设置RACH报告中的随机接入场景标识:
若随机接入过程是用于场景1~7,则UE设置随机接入场景标识为“初始接入”;
若随机接入过程是用于场景8且所述用于触发切换的RRC消息中包含了随机接入专用配置(用于分配专用的随机接入资源)的,则UE设置随机接入场景标识为“切换”;否则,若随机接入过程是用于场景8且所述用于触发切换的RRC消息中未包含随机接入专用配置(用于分配专用的随机接入资源)的,则UE设置随机接入场景标识为“初始接入”。
若随机接入过程是用于场景9~11的,则UE设置随机接入场景标识为“其他”;备选地,若随机接入过程是用于场景9~11的且用于分配随机接入资源的PDCCH命令中的随机接入前导索引(ra-PreambleIndex信息元素)的值不是0b000000时,UE设置随机接入场景标识为“其他”;否则,若随机接入过程是用于场景9~11的且用于分配随机接入资源的PDCCH命令中的随机接入前导索引(ra-PreambleIndex信息元素)的值是0b000000时,UE设置随机接入场景标识为“初始接入”。
若随机接入过程是用于场景12的,则UE设置随机接入场景标识为“波束失败恢复”。
上述方式中并不限定上述随机接入场景标识的名称,也可以做其他命 名,同前面所述。随机接入场景标识“初始接入”用于表示所述随机接入过程使用和初始接入时执行的随机接入过程相同的随机接入配置。优选地,指通过服务小区广播的携带在系统信息中的随机接入配置。随机接入场景标识“其他”可用于标识所述随机接入过程是由网络侧发起的除切换或RRC同步重配置过程之外的其他随机接入过程。
优选地,UE在保存所述随机接入过程对应的RACH报告或者描述为在RACH报告中包含一个对应于一个随机接入过程的项时,按照上述来设置所述随机接入触发场景标识。备选地,UE在生成包含RACH报告的RRC消息(UEinformationresponse)时,按照上述来设置所述消息中的RACH报告所对应的随机接入场景标识。所述设置随机接入场景标识的操作在UE RRC层执行。可选地,对于一些随机接入场景如随机接入场景4、5、7、10、11等是在MAC层发起的,在这些场景下,MAC层向RRC层指示所发起的随机接入所对应的随机接入触发场景。优选地,MAC层在一个随机接入过程完成后向RRC层指示所述信息;备选地,MAC层在一个随机接入过程发起时向RRC层指示所述信息。
在UE支持保存多个RACH报告的情况下,UE可以通过维护一个变量(如称VarRACH-report)来保存多个RACH报告,此次该变量中包含多个项目(entry),每一个项目关联到UE执行的一个随机接入过程所对应RACH报告。此时本实施例中所述RACH报告也可以描述为RACH报告中的一项。
触发场景、触发类型、触发原因在本公开中是可互换的。随机接入配置指的是随机接入参数配置或随机接入资源配置。
实施例2
本实施例提出了一种在UE上执行的RACH报告保存和上报方法。在该实施例中,UE在RACH报告中不包含一个未完成的随机接入过程的信息,使得网络侧在网络参数优化时将未完成的随机接入过程对应的样本排除,从而使得网络参数优化更准确。例如在下列情况下,UE在向网络侧执行RACH上报时会有一个未完成的随机接入过程,也称正在进行的随机接入过程。
情况1:当收到来自网络侧的包含用于RACH报告请求的信息元素(设置为ture)的RRC消息时,UE准备向网络侧返回用于响应的RRC消息, 而此时MAC层有一个正在进行的随机接入过程。也就是说,在UE上报RACH报告时,MAC层有一个正在进行的随机接入过程,该过程处于未完成阶段。其中,用于请求UE上报RACH信息/报告的信息元素如前所述可以是rach-ReportReq信息元素或rlf-ReportReq信息元素或connEstFailReportReq信息元素;所述包含用于RACH报告请求信息元素的RRC消息是UEinformationrequest消息,所述响应消息是UEinformationresponse消息。
情况2:当MAC实体正在执行一个随机接入过程A时,若此时有另一个随机接入过程B触发,UE可以停止正在执行的随机接入过程A,而开始执行随机接入过程B。此时随机接入过程A可称为一个被中止的未完成的随机接入过程。
情况3:当重置MAC实体时,UE会停止MAC层正在进行的随机接入过程。重置MAC实体一般由RRC层触发,如在RRC连接重建立过程的初始化阶段,或UE收到RRCrelease消息释放RRC连接时等。
UE不将一个未完成的随机接入过程对应的RACH信息包含在用于保存RACH报告的UE变量中可以按下述方法实施:若UE支持保存RACH报告,则当一个随机接入过程完成时,UE执行下述操作中的一种或多种:
操作1:在UE变量VarRACH-Report中包含一个项。所述UE变量用于保存RACH报告。所述包含的一个项对应于所述完成的随机接入过程。
操作2:依据从MAC层获取的随机接入对应的信息来设置RACH报告中的RACH信息,包括下述一个或多个:设置absoluteFrequencyPointA信息元素为所述随机接入过程所关联的参考资源块(Resource Block,RB)的绝对频率;按照所述随机接入触发场景来设置随机接入触发场景标识,对所使用的随机接入资源对应的每个波束索引,包含下述参数:设置波束索引值为所述波束的索引值;设置numerOfPreambleSentOnSSB信息元素为在该波束上所尝试的RACH尝试的次数;设置rachAttemptChronologicalOrder用于支持所述波束索引所对应的RACH尝试的时间先后顺序;对每一个随机接入尝试,按照随机接入尝试的时间先后顺序,若发生了竞争(即竞争解决未成功),则设置contentionDetected信息元素为“True”,否则设置contentionDetected信息元素为“false”;若一个随机接入尝试所使用的随机接入资源对应的波束的波束RSRP在所配置的一个门限值 rsrp-ThresholdSSB以上,则设置ssbRSRPQualityIndicator信息元素为“Ture”,否则设置为“false”。
在上述RACH报告中,所述波束是同步信号物理广播信号块(Synchronization Signal/Physical Broadcast Channel block,SS/PBCH block)或信道状态指示参考信号(Channel State Information Reference Signal,CSI-RS)。当波束是SSB/PBCH块时,上述波束索引为SSB-index,RACH尝试次数信息元素为numberOfPreambleSentOnSSB,门限值为信息元素rsrp-ThresholdSSB。备选地,当波束用CSI-RS表征时,上述波束索引是CSI-RS index,RACH尝试次数信息元素可以表示为numberOfPreambleSentOnCsi-rs,对应门限值为信息元素rsrp-ThresholdCSI-RS。
所述当一个随机接入过程完成时,也描述为当RRC层收到来自低层(MAC层)的随机接入过程完成指示时。所述随机接入过程完成可以是随机接入过程成功完成,也可以是随机接入过程失败完成。在该实施例中,一种假设是RRC层可以获知一个随机接入过程的开始,RRC层获知随机接入过程的开始可以是从MAC层获知的。
实施例3
本实施例提出了另一种在UE上执行的RACH报告保存和上报方法。该实施例与实施例2场景和目的相同。
在该实施例中,UE不将一个未完成的随机接入过程对应的RACH信息包含在用于保存RACH报告的UE变量中可以按下述方法实施:若UE支持保存RACH报告,则当RRC层收到一个随机接入过程中的一个随机接入尝试preamble对应的RACH信息时,UE执行下述操作:
若UE变量VarRACH-Report中未包含对于该随机接入过程的一个项,则在UE变量VarRACH-Report中为该随机接入过程包含一个项,并根据所收到的RACH信息设置对应的RACH报告中的信息元素;否则,若UE变量VarRACH-Report中已包含该随机接入过程的一个项,则根据收到的RACH信息设置对应的RACH报告中的信息元素。
所述UE变量用于保存RACH报告,所述包含的一个项对应于该随机接入过程。UE根据收到的RACH信息设置对应的RACH报告中的信息元 素,如实施例2中操作2所述。
该实施例不同于实施例2之处在于,对于一个未完成的随机接入过程对应的RACH信息,RRC层在收到来自低层的每一个RACH尝试的RACH信息时就将所述信息包含并保存在RACH报告中,而在UE执行RACH报告的发送或上报时,若所保存的一个或多个RACH报告对应的是一个未完成的随机接入过程,则UE不会将其包含在UEinformationresponse中上报给网络侧。可选地,UE可以在执行RACH报告的发送或上报时,删除对应于未完成的随机接入过程的RACH报告。优选地,这里删除的RACH报告至少指的是实施例2中情况2所指的随机接入过程A或情况3中所述随机接入过程,也就是之前被中止的随机接入过程,但在UE执行RACH报告的发送或上报时该随机接入过程已终止,不处于正在进行阶段。。在另一种UE删除未完成随机接入过程对应的RACH报告的方式中,当发生情况2或情况3时,RRC层收到来自MAC层的指示所述正在进行的随机接入过程未完成(abortion)的信息时,RRC层基于该指示删除对应的RACH报告项,也就是说当发生情况2或情况3时,MAC层向RRC层指示当前的随机接入过程未完成。在该实施例中,一种假设是RRC层可以获知一个随机接入过程的开始,RRC层获知随机接入过程的开始可以是从MAC层获知的。
实施例4
本实施例提出了另一种在UE上执行的RACH报告保存和上报方法。与实施例2和实施例3不同,UE在RACH报告上报时,若其保存的RACH报告中有对应于一个未完成的随机接入过程的RACH报告,则UE依然将其上报给网络侧,由网络侧来决定是否将所述RACH报告作为网络参数优化的样本。
在该实施例中,UE按如下实施:
若UE支持保存RACH报告,则当一个随机接入过程完成时,UE执行下述操作中的一种或多种:
操作1:在UE变量VarRACH-Report中包含一个项。所述UE变量用于保存RACH报告。所述包含的一个项对应于所述完成的随机接入过程。
操作2:同实施例2中操作2。
当UE接收到包含用于请求UE上报RACH报告的指示的RRC消息时,若当前有正在进行的尚未完成的随机接入过程,则UE执行下述操作的一种或多种:
操作3:在UE变量VarRACH-Report中包含一个项。所述UE变量用于保存RACH报告。所述包含的这个项对应于所述正在进行的随机接入过程。
操作4:将UE变量VarRACH-Report中所保存的一项或多项RACH报告包含在响应RRC消息中。
操作5:在响应RRC消息中包含所述正在进行的随机接入过程对应的RACH报告,其中RACH报告中的RACH信息设置同操作2。
操作6:在对应的RACH报告中包含一个指示信息,所述指示信息用于告知网络侧所对应的RACH报告是对一个未完成的随机接入过程的。
操作7:将包含RACH报告的响应RRC消息发送给网络侧。
实施例5
本实施例提出了一种RACH报告的管理方法。
在一种方式中,当UE在用于保存RACH报告的UE变量VarRACH-Report中包含一个对应于刚刚完成的或正在进行的随机接入过程的项时,若此时所述UE变量中的RACH报告的项的数据超过UE所支持的最大的数目,则UE删除所保存的RACH报告中的最旧的一项或多项,以便保存新的RACH报告项。备选地,UE删除所保存的RACH报告中对应于未完成的随机接入过程的RACH报告项。所述未完成的随机接入过程如实施例2中情况2和情况3。
实施例6
本实施例提出了一种条件切换场景下的RACH报告方法。通过设置RACH报告中的随机接入触发场景标识为条件切换,使得网络侧可以获知所对应的RACH报告是对于条件切换的,可以区分于其他触发场景下的RACH报告,从而基于此对条件切换对应的切换参数进行调整和配置。
步骤1:UE触发并执行条件切换过程。在所述条件切换过程中,UE执行向目标小区的随机接入过程。
步骤2:若UE支持RACH报告,则UE设置RACH报告中的随机接入场景标识为条件切换。所述随机接入场景标识如前所述用于指示所述RACH报告所对应的随机接入过程的触发场景(或称触发原因、触发类型、触发目的等)。也就是说UE在RACH报告中包含一个指示信息,用于指示所述RACH报告是对于一个条件切换过程中所执行的随机接入过程的。所述RACH报告指的是步骤1中执行条件切换过程中所执行的随机接入过程。
在UE支持保存多个RACH报告的情况下,UE可以通过维护一个变量(如称VarRACH-report)来保存多个RACH报告,此次该变量中包含多个项目(entry),每一个项目关联到UE执行的一个随机接入过程所对应RACH报告。此时本实施例中所述RACH报告也可以描述为RACH报告中的一项。
优选地,所述UE在向保存RACH报告的UE变量中加入一个RACH报告项时,设置RACH报告中的随机接入场景标识为条件切换。备选地,所述UE在生成或设置向网络侧发送的包含RACH报告的RRC消息时,将对应的RACH报告中的随机接入场景标识设置为条件切换。
实施例7
如前所述,NR系统中同时支持基于四步的随机接入过程和基于两步的随机接入过程。考虑到这两种随机接入类型所使用的资源不同,网络侧需要区分从UE获取的RACH报告是对于哪种随机接入类型的即是对于四步随机接入的还是两步随机接入的,以便对相应的参数进行调整和优化。本实施例给出了一种两步随机接入场景下的RACH报告方法,通过该实施例所述方法,UE RRC层从MAC层获取随机接入尝试所使用的随机接入类型,并将其包含在对应的RACH报告中告知网络侧,以便网络侧区分所述RACH报告是对于两步随机接入的还是四步随机接入的。
步骤1:MAC层执行随机接入过程,并根据所触发的随机接入过程是两步还是四步设置其随机接入类型变量RA_TYPE的值为“2-stepRA”或“4-stepRA”。比如,若随机接入过程是由PDCCH order所发起的且PDCCH中所提供的用于指示随机接入前导的ra-PreambleIndex不是“0b000000”或随机接入过程是由于系统信息请求所触发的且用于系统信息请求的随机接入资源是由RRC消息提供的,那UE设置RA_TYPE为“4-stepRA”;若配置了用于确定是否采用两步随机接入的门限参数 rsrp-ThresholdSSB-2stepCBRA且下行路损参考的RSRP在所配置的该门限参数以上或UE所选择的用于随机接入过程的带宽部分(BandWidth Part,BWP)仅配置了两步随机接入资源而未配置四步随机接入资源,那么UE设置RA_TYPE为“2-stepRA”,否则UE设置RA_TYPE为“4-stepRA”。所述UE设置该随机接入变量的细节可参见3GPP协议规范38.321或RAN2会议文档R2-1914798,此处不赘述。
步骤2:MAC层将随机接入类型指示给RRC层。所述随机接入类型为所述变量RA_TYPE的值。优选地,MAC层在每次执行随机接入前导发送过程前将所述随机接入前导发送所对应的随机接入类型指示给RRC层。备选地,MAC层在随机接入过程初始化阶段以及在随后的随机接入过程中随机接入类型变更时,将随机接入类型指示给RRC层。或者,MAC层在随机接入过程完成时,将该随机接入过程所对应的所用的一个或多个(如2-stepRA,4-stepRA或者2-stepRA-to-4-stepRA)随机接入类型指示给RRC层。
步骤3:RRC层在保存RACH报告,即设置UE变量VarRACH-report时,将随机接入类型信息元素设置为从MAC层获取的随机接入类型的值。优选地,所述随机接入类型信息元素是对每个随机接入尝试(如每个随机接入前导的发送)所包含的;备选地,所述随机接入类型信息元素是对整个随机接入过程所包含的。在另一种实现方式中,RRC层在收到网络侧的上报RACH报告请求向网络侧上报RACH报告时,设置所述随机接入类型信息元素的值为从MAC层获取的值。所述向网络侧上报的RACH报告包含在UEinformationresponse的RRC消息中。
图5是表示根据本公开实施例的用户设备50的框图。如图5所示,该用户设备50包括处理器510和存储器520。处理器510例如可以包括微处理器、微控制器、嵌入式处理器等。存储器520例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器520上存储有程序指令。该指令在由处理器510运行时,可以执行本公开详细描述的用户设备中的上述随机接入报告方法。
运行在根据本公开的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统,可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如,单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器,也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路,也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下,本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外,本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例,但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备,如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上,已经参考附图对本公开的实施例进行了详细描述。但是,具体的结构并不局限于上述实施例,本公开也包括不偏离本公开主旨的任何设计改动。另外,可以在权利要求的范围内对本公开进行多种改动,通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外,上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备执行的随机接入报告方法,包括:
    在随机接入触发场景下触发并执行随机接入过程;以及
    向网络侧发送与所述随机接入过程对应的随机接入信道RACH报告,该RACH报告中包含用于标识所述随机接入触发场景的随机接入场景标识,
    所述随机接入触发场景是条件切换场景。
  2. 根据权利要求1所述的随机接入报告方法,其中,
    将所述RACH报告中的所述随机接入场景标识设置为条件切换。
  3. 根据权利要求2所述的随机接入报告方法,其中,
    设置为条件切换的所述随机接入场景标识表示对应的随机接入过程使用了条件切换时的随机接入配置。
  4. 根据权利要求1至3中任一项所述的随机接入报告方法,其中,
    通过用于保存RACH报告的变量来保存多个RACH报告。
  5. 根据权利要求4所述的随机接入报告方法,其中,
    所述变量中包含多个项目,每一个项目关联到所述用户设备执行的一个随机接入过程所对应的RACH报告。
  6. 根据权利要求5所述的随机接入报告方法,其中,
    在所述随机接入过程完成时或发起时,向所述变量中加入一个对应于该随机接入过程的RACH报告项。
  7. 根据权利要求6所述的随机接入报告方法,其中,
    在向所述变量中加入所述RACH报告项时,将所关联的RACH报告中的随机接入场景标识设置为条件切换。
  8. 根据权利要求1至3中任一项所述的随机接入报告方法,其中,
    将所述RACH报告包含在无线资源控制RRC消息中发送给网络侧。
  9. 根据权利要求8所述的随机接入报告方法,其中,
    在生成或设置所述RRC消息时,将所包含的所述RACH报告中的随机接入场景标识设置为条件切换。
  10. 一种用户设备,包括:
    处理器;以及
    存储器,存储有指令;
    其中,所述指令在由所述处理器运行时执行根据权利要求1至9中任一项所述的随机接入报告方法。
PCT/CN2020/137981 2019-12-27 2020-12-21 由用户设备执行的随机接入报告方法和用户设备 WO2021129568A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911388537.9A CN113055906A (zh) 2019-12-27 2019-12-27 由用户设备执行的随机接入报告方法和用户设备
CN201911388537.9 2019-12-27

Publications (1)

Publication Number Publication Date
WO2021129568A1 true WO2021129568A1 (zh) 2021-07-01

Family

ID=76507675

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/137981 WO2021129568A1 (zh) 2019-12-27 2020-12-21 由用户设备执行的随机接入报告方法和用户设备

Country Status (2)

Country Link
CN (1) CN113055906A (zh)
WO (1) WO2021129568A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102342145A (zh) * 2009-03-20 2012-02-01 瑞典爱立信有限公司 用于监控随机接入信道的方法和装置
CN105580427A (zh) * 2013-07-31 2016-05-11 松下电器(美国)知识产权公司 移动通信系统中的切换过程
US20180324864A1 (en) * 2017-05-05 2018-11-08 Motorola Mobility Llc Method and apparatus for transmitting a rach preamble on a wireless network
CN109392117A (zh) * 2017-08-10 2019-02-26 普天信息技术有限公司 一种正交频分复用系统中调度请求配置方法
CN110431892A (zh) * 2017-03-11 2019-11-08 高通股份有限公司 取决于参数集的随机接入时序

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102342145A (zh) * 2009-03-20 2012-02-01 瑞典爱立信有限公司 用于监控随机接入信道的方法和装置
CN105580427A (zh) * 2013-07-31 2016-05-11 松下电器(美国)知识产权公司 移动通信系统中的切换过程
CN110431892A (zh) * 2017-03-11 2019-11-08 高通股份有限公司 取决于参数集的随机接入时序
US20180324864A1 (en) * 2017-05-05 2018-11-08 Motorola Mobility Llc Method and apparatus for transmitting a rach preamble on a wireless network
CN109392117A (zh) * 2017-08-10 2019-02-26 普天信息技术有限公司 一种正交频分复用系统中调度请求配置方法

Also Published As

Publication number Publication date
CN113055906A (zh) 2021-06-29

Similar Documents

Publication Publication Date Title
EP3562208B1 (en) User mobility method and device
WO2021129567A1 (zh) 由用户设备执行的随机接入报告方法和用户设备
US20230362808A1 (en) Mobile communication system, originating base station, candidate base station, and mobile terminal
EP3817443B1 (en) Method executed by user equipment, and user equipment
CN108243469B (zh) 用户移动性方法和设备
US20120250498A1 (en) Failure Event Report Correlation for Distributed RAN Self-Organization
EP4216597A1 (en) Radio link failure reporting method and user equipment
JP7221976B2 (ja) 改善された優先順位付けされるランダムアクセスに関与するユーザ機器および基地局
US20220078875A1 (en) Method and apparatus for timer control for rrc connection resume procedure in a wireless communication system
WO2022206668A1 (zh) 随机接入信息上报方法和用户设备
WO2020249007A1 (zh) 由用户设备执行的信息报告方法及用户设备
WO2023125649A1 (zh) 连接建立失败报告方法和用户设备
WO2022194041A1 (zh) 随机接入报告方法和用户设备
WO2021129568A1 (zh) 由用户设备执行的随机接入报告方法和用户设备
WO2022022444A1 (zh) 由用户设备执行的方法以及用户设备
WO2024114732A1 (zh) 随机接入报告方法和用户设备
WO2024027704A1 (zh) 切换信息报告方法以及用户设备
WO2023246765A1 (zh) 由用户设备执行的方法及用户设备
WO2024002239A1 (zh) 由用户设备执行的方法及用户设备
WO2024208199A1 (zh) 指示功率参数的方法、确定传输功率的方法及用户设备
WO2024149065A1 (zh) 由用户设备执行的方法及用户设备
WO2024067624A1 (zh) 信息报告方法以及用户设备
WO2024094056A1 (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: 20907068

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

Country of ref document: EP

Kind code of ref document: A1