Method performed by a user equipment and user equipment

Abstract

The application provides a method executed by a user equipment and the user equipment. The method executed by the user equipment (UE) comprises: the UE receiving system information and / or RRC dedicated message sent by a network, wherein the system information and / or RRC dedicated message contains SIB1 request configuration; the UE initiating a random access procedure according to the SIB1 request configuration and judging the reason of triggering the random access procedure; and the UE executing the random access procedure, wherein if the reason of triggering the random access procedure is to initiate SIB1 request, the UE does not execute BWP operation; or the UE executes BWP operation except when the reason of triggering the random access procedure is to initiate SIB1 request.

Description

Technical Field

[0001] This invention relates to the field of wireless communication technology, and more specifically, to a method for network power saving performed by a user equipment and a corresponding user equipment. Background Technology

[0002] Network energy conservation helps reduce environmental impact and save operator costs. Typically, networks require random access resources to enable terminal access. Under low system load, a large or dense allocation of random resources can waste network resources. Networks can be configured with sparser random access resources and dynamically adjusted to adapt to changes in system load. For these reasons, the 3rd Generation Partnership Project (3GPP) approved the NES enhancement work item for version 19 at the RAN plenary meeting, the details of which can be found in non-patent literature: RP-242354 WID: Enhancements of network energy savings for NR. This work item includes the network ceasing periodic broadcasting of SIB1 under low system load conditions, allowing UEs to request SIB1 on demand in idle and inactive states, and triggering SIB1 broadcasting based on UE requests. Summary of the Invention

[0003] According to one aspect of the present invention, a method performed by a user equipment (UE) is provided, comprising: the UE receiving system information and / or RRC proprietary messages sent by a network, wherein the system information and / or RRC proprietary messages include an SIB1 request configuration; the UE initiating a random access procedure according to the SIB1 request configuration and determining the reason for triggering the random access procedure; and the UE executing the random access procedure, wherein if the reason for triggering the random access procedure is to initiate an SIB1 request, the UE does not perform a BWP operation; or the UE performs a BWP operation except when the reason for triggering the random access procedure is to initiate an SIB1 request.

[0004] In the above method, preferably, the method further includes: after completing the random access procedure, the UE performs an RA report determination procedure to set or determine random access public information or first random access public information.

[0005] In the above method, preferably, during the process of determining the random access public information, the content of the random access public information is set, including setting the subcarrier interval. When the purpose of triggering the random access process is to request SIB1, the UE sets the subcarrier interval in one of the following ways: - setting the subcarrier interval to the subcarrier interval of the carrier; - setting the subcarrier interval to the subcarrier interval of message 1; - setting the subcarrier interval to an arbitrary value; - replacing the field containing the subcarrier interval with a null value.

[0006] In the above method, preferably, during the process of determining the random access public information, the content of the random access public information is set, including setting the subcarrier interval of the carrier, and setting the subcarrier interval of the carrier to the subcarrier interval of the carrier included in the SIB1 request configuration.

[0007] In the above method, preferably, during the process of determining the random access public information, the content of the random access public information is set, including setting the location and bandwidth. When the purpose of triggering the random access process is to request SIB1, the UE sets the location and bandwidth in one of the following ways: setting the location and bandwidth to arbitrary values; setting the location and bandwidth to a specific value; replacing the field containing the location and bandwidth with a null value; or setting the location and bandwidth to a UE-calculated value.

[0008] In the above method, preferably, during the process of determining the random access public information, the content of the random access public information is set, including setting a carrier offset, and setting the carrier offset to the carrier offset included in the SIB1 request configuration.

[0009] In the above method, preferably, the first random access public information is OD-SIB1 random access public information or version 19 random access public information. If the first random access public information exists, the version 16 random public information is ignored by the base station.

[0010] According to another aspect of the present invention, a user equipment is provided, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the method of any one of claims 1 to 7.

[0011] Invention Effects

[0012] According to the present invention, the UE can correctly execute the random access procedure and correctly set the information in the random access report, thereby avoiding anomalies and improving the UE's service experience. Attached Figure Description

[0013] Figure 1This is a schematic diagram of method one executed by the UE according to one or more embodiments.

[0014] Figure 2 This is a schematic diagram of method two executed by the UE according to one or more embodiments.

[0015] Figure 3 This is a schematic diagram of method three executed by the UE according to one or more embodiments.

[0016] Figure 4 This is a schematic diagram of method four executed by the UE according to one or more embodiments.

[0017] Figure 5 This is a schematic diagram of method five executed by the UE according to one or more embodiments.

[0018] Figure 6 This is a schematic diagram of method six executed by the UE according to one or more embodiments.

[0019] Figure 7 This is a schematic diagram of method seven executed by the UE according to one or more embodiments.

[0020] Figure 8 This is a schematic diagram of method eight performed by the UE according to one or more embodiments.

[0021] Figure 9 This is a simplified structural block diagram of the user equipment (UE) involved in the present invention. Detailed Implementation

[0022] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present invention should not be limited to the specific embodiments described below. Furthermore, for the sake of simplicity, detailed descriptions of well-known technologies not directly related to the present invention have been omitted to prevent confusion in understanding the present invention.

[0023] The following describes some of the terms involved in this invention. For the specific meanings of these terms, please refer to the latest 3GPP standard specifications.

[0024] UE: User Equipment

[0025] NR: New Radio, next-generation wireless technology

[0026] AS: Access Stratum

[0027] MAC: Medium Access Control

[0028] MAC CE: MAC control element

[0029] RRC: Radio Resource Control

[0030] RRC_CONNECTED: RRC connection state

[0031] RRC_INACTIVE: RRC inactive state

[0032] RRC_IDLE: RRC idle state

[0033] RAN: Radio Access Network, Wireless Access Layer

[0034] PDCCH: Physical downlink control channel

[0035] PUCCH: Physical Uplink Control Channel

[0036] PUSCH: Physical Uplink Shared Channel

[0037] PRACH: Physical Random Access Channel

[0038] PBCH: Physical broadcast channel

[0039] SFN: System Frame Number

[0040] PDU: Protocol Data Unit

[0041] SSB: SS / PBCH block, Synchronization Signal / Physical Broadcast Channel Block

[0042] CSI-RS: Channel Status Information-Reference Signal

[0043] DCI: Downlink Control Information

[0044] RNTI: Radio Network Temporary Identifier

[0045] C-RNTI: Cell RNTI, Cell RNTI

[0046] P-RNTI: Paging RNTI, Pager RNTI

[0047] RA-RNTI: Random Access RNTI

[0048] SI-RNTI: System Information RNTI

[0049] RSRP: Reference Signal Received Power

[0050] RSRQ: Reference Signal Received Quality

[0051] SpCell: Special Cell, including PCCell and PSCell.

[0052] SCell: Secondary Cell

[0053] CA: Carrier Aggregation

[0054] DC: Dual Connectivity

[0055] MCG: Master Cell Group

[0056] SCG: Secondary Cell Group

[0057] PCell: Primary Cell

[0058] PSCell: Primary SCG Cell (SCG Main Cell)

[0059] MIB: Master Information Block

[0060] DRX: Discontinuous Reception

[0061] SIB: System Information Block

[0062] gNB: the next generation Node B, next-generation base station

[0063] RLF: Radio Link Failure.

[0064] SN: Sequence Number

[0065] CN: Core Network

[0066] UL-SCH: Uplink Shared Channel

[0067] NES: Network Energy Saving

[0068] SI: System Information

[0069] L3: Layer 3

[0070] CE: control element, control unit

[0071] RAPID: Random Access Preamble Identifier

[0072] RAR: Random Access Response

[0073] WUS: wake up signal

[0074] OSI: Other System Information

[0075] PLMN: Public Land Mobile Network

[0076] BWP: Bandwidth part, partial bandwidth

[0077] PRB: Physical resource block

[0078] CRB: Common Resource Block

[0079] Point A: Common reference point for physical layer resource block grids

[0080] RB: Resource Block

[0081] In this invention, the network (or NW), base station (or gNB or eNB), and RAN can be used interchangeably. The network can be a Long Term Evolution (LTE) network, a New Radio Access Technology (NR) network, an enhanced Long Term Evolution (eLTE) network, or other networks defined in subsequent 3GPP evolution versions.

[0082] In this invention, User Equipment (UE) can refer to a device that supports network power saving, a device that supports enhanced network power saving, a device with (enhanced) network power saving capabilities, a device that supports on-demand SIB1, a device with on-demand SIB1 capabilities, a device with SIB1 request capabilities, a device that supports obtaining SIB1 by requesting SIB1, or other types of NR or LTE devices.

[0083] In this invention, "message" and "signaling" can be used interchangeably.

[0084] In this invention, the terms "feedback", "submit", "report", "send", "transmit or transport", "inform or notify", "indicate", and "provide" can be used interchangeably.

[0085] In this invention, terms such as "use", "be available / be valid", "apply", "implement", "enable", "activate", "perform", "do", and "start" can be used interchangeably.

[0086] In this invention, "trigger" and "initiate" can be used interchangeably.

[0087] In this invention, "deactivate (non-active or deactivate / deactivate)," "stop / stop," "de-enable," "exit," "invalidate," and "make unavailable / unusable" can be used interchangeably.

[0088] In this invention, "activate", "start", "enable", "use", "enter", and "wake up" can be used interchangeably.

[0089] In this invention, "activated", "available", "valid" and "available" can be used interchangeably.

[0090] In this invention, "deactivated", "unavailable", "inactive", "invalid", and "unavailable" can be used interchangeably.

[0091] In this invention, the terms "associate", "correspond", and "map" can be used interchangeably.

[0092] In this invention, receiving, detecting, monitoring, acquiring, and deriving are interchangeable.

[0093] In this invention, "time" can be time, duration, period, time period, etc.

[0094] In this invention, "physical layer" and "layer one (L1)" can be used interchangeably. "MAC layer" and "MAC entity" can also be used interchangeably. For the RRC layer, "upper layer(s)" refers to layers above the RRC layer, such as the NAS layer. For the MAC layer, "upper layer(s)" refers to layers above the MAC layer, such as the RRC layer, and "lower layer(s)" refers to layers below the MAC layer, such as the physical layer. For the physical layer, "upper layer" refers to layers above the physical layer, such as the MAC layer and / or the RRC layer.

[0095] In this invention, "not broadcasting" and "on-demand" can be used interchangeably; "broadcasting" and "not on-demand" can also be used interchangeably.

[0096] In this invention, “SIB1 request configuration”, “UL WUS configuration”, “PRACH configuration for on-demand SIB1 request” and “PRACH configuration for SIB1 request” can be used interchangeably.

[0097] In this invention, “SIB1 request”, “request SIB1”, “request on-demand SIB1” and “on-demand SIB1 request” can be used interchangeably.

[0098] In this invention, "NES cell", "OD-SIB1 cell", "cell using on-demand SIB1", "on-demand SIB1 cell", and "cell supporting on-demand SIB1" can be used interchangeably. "NES UE" and "OD-SIB1 UE" can be used interchangeably.

[0099] In this invention, “OD-SIB1” and “on-demand SIB1” can be used interchangeably.

[0100] In this invention, "PRACH", "RACH" and "random access" can be used interchangeably.

[0101] In this invention, “random access parameters (configuration)”, “random access resources (parameters / configuration)”, and “random access resource set (configuration)” can be used interchangeably.

[0102] It should be noted that in this specification, the two terms connected by "and", "or", or "and / or" may represent different ways of expressing the same meaning in different application scenarios. There may be a relationship of inclusion between the two terms, and they do not necessarily refer to completely different content.

[0103] The related technologies of the present invention are described below.

[0104] BWP

[0105] By utilizing bandwidth adaptation, the UE's transmit and receive bandwidths can be smaller than the cell carrier bandwidth and can be adjusted. For bandwidth adaptation, the Block Shared Resource (BWP) is a set of contiguous common resource blocks within the entire carrier bandwidth, representing a subset of the cell carrier bandwidth. The network can change the time-frequency resources of the BWP by adjusting its configuration. The BWP configuration includes: location and bandwidth, subcarrier spacing, and cyclic prefix.

[0106] `locationAndBandwidth` indicates the frequency domain location and bandwidth of the BWP, specifically the starting PRB position and the number of consecutive RBs. The starting PRB is determined by the carrier offset (offsetToCarrier) corresponding to the subcarrier spacing and the subcarrier spacing itself. The value of `locationAndBandwidth` is a numerical value calculated from the starting PRB position and the number of consecutive RBs according to a formula specified in the protocol. `offsetToCarrier` indicates the offset between Point A (the lowest subcarrier of common RB 0) and the lowest available subcarrier on the carrier, in units of the number of PRBs.

[0107] `subcarrierSpacing` indicates the subcarrier spacing used by the BWP. `cyclicPrefix` indicates whether an extended cyclic prefix is ​​used; if `cyclicPrefix` is not set, a normal cyclic prefix is ​​used.

[0108] BWP is divided into uplink BWP and downlink BWP. Uplink BWP is further divided into initial uplink BWP and normal uplink BWP, while downlink BWP is divided into initial downlink BWP and normal downlink BWP.

[0109] The network broadcasts the initial uplink BWP configuration and initial downlink BWP configuration of the cell through system information. Both the initial uplink BWP configuration and the initial downlink BWP configuration include the aforementioned BWP configuration. UEs in RRC idle state and inactive state initiate a random access procedure during the initial uplink BWP. After sending the PRACH preamble, the UE listens for / receives the RAR during the initial downlink BWP.

[0110] Random access

[0111] The network broadcasts the random access resource configuration (also known as the random access resource set) used by the cell through system information. Each random access resource set corresponds to a PRACH configuration index. Random access resources can refer to physical frequency domain resources and / or time domain resources and / or code domain resources (such as preamble) used for random access. The random access resource configuration includes parameters for some random access resources. The network can configure one or more random access resources. Random access resources can be associated with one or more features, or they can be unrelated to features. Generally, a random access resource configuration corresponds to one uplink BWP.

[0112] RACH can refer to either the Transport Channel RACH or PRACH; the distinction is not made. Random Access Parameters / Configuration refers to the radio configuration that implements random access functionality, including PRACH-related configurations.

[0113] A UE can trigger a random access procedure under various circumstances, such as initial access when transitioning from an RRC idle state or an RRC inactive state (RRC_INACTIVE) to an RRC connected state, beam recovery requests, handover (also known as synchronization reconfiguration), etc., when uplink data arrives for a UE in an RRC connected state but the uplink is out of sync, or when a UE in an RRC connected state has no available PUCCH source. After the random access procedure is triggered, the UE selects whether the initiated random access procedure is a two-step random access or a four-step random access, and whether it is a conflict-based random access (CBRA) or a conflict-free random access (CFRA), based on the network configuration and the UE's measurement results. Furthermore, the UE can fall back to a four-step random access procedure during a two-step random access, for example, when the number of times the two-step random access attempt message A is sent exceeds a configured maximum. The random access procedures described in this disclosure include, but are not limited to, the above-mentioned random access procedures.

[0114] RA report

[0115] When a UE completes a random access procedure, it adds a new entry to the random access variable (VarRA-Report) to record information about the successful or failed random access procedure. The information element recording information about a successful or failed random access procedure is called a Random Access Report (RA Report), and one or more RA Reports are recorded in the VarRA-Report. When the base station needs an RA Report, it sends a UE Information Request message to the UE, which includes an RA Report Request Indicator (ra-ReportReq) element to request the UE to report the saved RA Reports of the random access procedure. Upon receiving the UE Information Request message containing the RA Report Request Indicator, the UE includes the saved RA Reports in a UE Information Response message and sends them to the base station. The base station uses one RA Report reported by a UE as a sample. Based on a sufficient number of samples, the base station can analyze whether the current RACH performance meets the requirements and adjust the RACH parameters accordingly to improve RACH performance. Information in an RA report includes: cell information of the random access preamble being sent (global cell identifier, tracking area code or physical cell identifier and carrier frequency), random access destination information, and random access common information (i.e., ra-InformationCommon).

[0116] The random access common information includes: subcarrier spacing (subcarrierSpacing), location, and bandwidth (locationAndBandwidth). Based on the subcarrierSpacing and locationAndBandwidth configured in the uplink BWP (or initial uplink BWP for RRC_IDLE / RRC_INACTIVE random access procedures) corresponding to the random access resources used in the random access procedure, the subcarrierSpacing and locationAndBandwidth in the random access common information are set.

[0117] In the random access public information, subcarrierSpacing and locationAndBandwidth are mandatory fields.

[0118] System information acquisition

[0119] In NR networks, MIB and SIB1 are important system information. In order for a UE to camp on a certain cell or initiate an RRC connection in a certain cell, it needs to obtain MIB and SIB1 first, thereby obtaining the basic network parameter information for camping on or accessing that cell.

[0120] The MIB is broadcast on the PBCH, and SIB1 is broadcast on the PDSCH. To receive SIB1, the UE needs to listen to the PDCCH to obtain the scheduling information of the PDSCH carrying SIB1. The MIB contains relevant parameter information for obtaining SIB1. The MIB contains the ssb-SubcarrierOffset (SSB subcarrier offset) field, which can be used to indicate whether the cell's SIB1 is scheduled (or transmitted). This field contains 4 bits, and one or more specific values ​​of these 4 bits can indicate whether the cell's SIB1 is scheduled (or transmitted). If the cell's SIB1 is not scheduled (or transmitted), the UE considers important system information missing, the cell is barred, and cell reselection is performed; if the cell's SIB1 is scheduled (or transmitted), the UE obtains SIB1.

[0121] SIB1 contains parameter information for obtaining other SIB(s) (i.e., OSIs) besides MIB and SIB1, such as period, SI window length, and whether the OSI(s) is broadcast. If the OSI(s) is broadcast, the UE obtains the OSI(s) according to its own needs; if the OSI(s) is not broadcast, the UE sends an OSI request to the network when it needs the OSI(s), triggering the network to send the OSI(s). Specifically, the UE sends a PRACH request to the network through an OSI request configuration (including dedicated PRACH resources) to request the OSI. After receiving the OSI request, the base station sends a response to the UE. Upon receiving the response, the UE obtains the required SIB according to the SI window length.

[0122] A cell that employs (enhanced) network energy saving, or a cell that uses on-demand SIB1, or a cell whose SIB1 is not broadcast, or a cell that supports on-demand SIB1, or a cell that supports (enhanced) network energy saving, is called an on-demand SIB1 cell, or simply an OD-SIB1 cell. In this invention, OD-SIB1 cell is just an example name, and it can be other names as well.

[0123] For on-demand OSI, the OSI request configuration is included in SIB1. For on-demand SIB1, the SIB1 request configuration used to request SIB1 in the OD-SIB1 cell can be sent to the UE by other cells (e.g., neighboring cells of the OD-SIB1 cell), or the already obtained SIB1 request configuration can be updated through the system information update procedure. If a cell's own SIB1 is broadcast, and / or the cell is able to send the SIB1 request configuration of other cells (or neighboring cells) to other cells (or neighboring cells), then the cell is called Cell A. In this invention, Cell A is just an example name, and it can also be other names.

[0124] The SIB1 request configuration for requesting SIB1 (or OD-SIB1) in the OD-SIB1 cell may include a PRACH configuration for the SIB1 request, which may include, but is not limited to, a PRACH preamble(s) for the SIB1 request, PRACH resources(s) for the SIB1 request, etc. When the UE is camped in Cell A, the UE can receive the SIB1 request configuration for the OD-SIB1 cell from the system information receiving network of Cell A. When the UE reselects from Cell A to the OD-SIB1 cell, the UE initiates a random access procedure in the OD-SIB1 cell to request SIB1 using the aforementioned SIB1 request configuration. Upon receiving confirmation of the SIB1 request (i.e., receiving the RAR), the UE acquires SIB1 in the OD-SIB1 cell. Alternatively, when the UE is camped in the first OD-SIB1 cell, the UE can receive the SIB1 request configuration for the second OD-SIB1 cell from the system information receiving network of the first OD-SIB1 cell. When the UE reselects from the first OD-SIB1 cell to the second OD-SIB1 cell, the UE uses the SIB1 request configuration to initiate a random access procedure in the second OD-SIB1 cell to request SIB1. Upon receiving confirmation of the SIB1 request, the UE acquires SIB1 in the second OD-SIB1 cell.

[0125] The SIB1 request configuration does not include the initial uplink BWP configuration and / or the initial downlink BWP configuration, meaning that the RACH resources and BWPs used for the SIB1 request do not correspond. The UE triggers a random access procedure for requesting SIB1 in the OD-SIB1 cell based on the time-frequency location of the RACH resources in the SIB1 request configuration. This requires studying how to handle the original BWP operations and how to set the required fields in the RA report, such as subcarrierSpacing and locationAndBandwidth.

[0126] To address at least some of the aforementioned problems, the present invention provides a method and a user equipment (UE) that enable the UE to correctly execute random access procedures and correctly set information in the random access report, thereby preventing anomalies and improving the UE's service experience.

[0127] Example

[0128] To distinguish it from ordinary UEs, this invention refers to a UE having at least one of the following characteristics as an NES UE. NES UE is merely an example name, and any other UE having at least one of the following characteristics can be used interchangeably with NES UE:

[0129] - Features enhanced network energy-saving capabilities;

[0130] -Supports on-demand SIB1;

[0131] - Possesses on-demand SIB1 capability;

[0132] - Has SIB1 request capability;

[0133] -Supports obtaining SIB1 by requesting SIB1.

[0134] Optionally, in this invention, the UE is an NES UE.

[0135] Figure 1 This is a schematic diagram illustrating method one executed by the UE according to one or more embodiments. The UE can execute... Figure 1 One or more steps. Figure 1 This includes steps S101 to S103.

[0136] Optionally, in step S101, the UE receives system information and / or RRC-specific messages (e.g., RRCReconfiguration messages) sent by the network. Optionally, the system information and / or RRC-specific messages include SIB1 request configurations for (adjacent) OD-SIB1 Cell(s) (the SIB1 request configurations can be one or more), or the system information and / or RRC-specific messages include the SIB1 request configurations for the cell when it (in the future) becomes an OD-SIB1 Cell. For example, the UE receives the system information and / or RRC-specific messages in Cell A, or the UE receives the system information and / or RRC-specific messages in an OD-SIB1 Cell.

[0137] Optionally, the SIB1 request configuration includes, but is not limited to: PRACH configuration (for SIB1 request), uplink carrier information (or uplink frequency information), and OD-SIB1 cell configuration.

[0138] Optionally, the uplink carrier information (or uplink frequency information) includes, but is not limited to: carrier offset (offsetToCarrier), subcarrier spacing (e.g., ULSubCarrierSpacing), and carrier bandwidth. Optionally, the OD-SIB1 cell configuration includes, but is not limited to: OD-SIB1 cell identifier and OD-SIB1 cell absolute radio frequency channel number (ARFCN).

[0139] Optionally, the carrier offset (offsetToCarrier) indicates the frequency domain offset between Point A (the lowest subcarrier of common RB 0) and the lowest available subcarrier on the carrier, in units of PRB(s). Optionally, the subcarrier spacing of the carrier (e.g., ULSubCarrierSpacing) indicates the subcarrier spacing of the carrier. Optionally, the carrier bandwidth indicates the width of the carrier in units of PRB(s).

[0140] Optionally, in step S102, the UE initiates a random access procedure based on the SIB1 request configuration and determines the reason for triggering the random access procedure. Optionally, the random access procedure is a random access procedure initiated for requesting SIB1 (or OD-SIB1), which is equivalent to initiating an SIB1 (or OD-SIB1) request procedure. Optionally, the random access procedure is initiated in the OD-SIB1 cell based on the SIB1 request configuration.

[0141] Optionally, in sub-step one, the UE (MAC entity) selects a carrier for performing the random access procedure. Optionally, the carrier indicated by the SIB1 request configuration (e.g., the carrier indicated in the uplink carrier information) is selected to perform the random access procedure.

[0142] Optionally, in sub-step two, the UE (MAC entity) determines whether to perform BWP operation based on the reason for triggering the random access procedure.

[0143] Optionally, the UE does not perform BWP operation if the random access procedure satisfies at least one of the following conditions; or the UE performs BWP operation except if the random access procedure satisfies at least one of the following conditions:

[0144] - The random access procedure is triggered to initiate a SIB1 (or OD-SIB1) request;

[0145] - The random access procedure is triggered in order to request SIB1 (or OD-SIB1).

[0146] Optionally, in sub-step three, the UE (MAC entity) selects a random access resource (for the random access procedure).

[0147] Optionally, in step S103, the UE executes the random access procedure, that is, requests SIB1 (or OD-SIB1) to execute the random access procedure.

[0148] Figure 2 This is a schematic diagram illustrating method two executed by the UE according to one or more embodiments. The UE can execute... Figure 2 One or more steps. Figure 2This includes steps S201 to S202.

[0149] Optionally, in step S201, the UE executes a random access procedure (same as step S103) and completes the random access procedure.

[0150] Optionally, the random access procedure may be successfully completed or fail. Optionally, the random access procedure is a random access procedure initiated for requesting SIB1 (or OD-SIB1), which is equivalent to initiating an SIB1 (or OD-SIB1) request procedure. Optionally, the random access procedure is initiated in the OD-SIB1 cell according to the SIB1 request configuration.

[0151] Optionally, this step is equivalent to the UE executing and completing an OD-SIB1 acquisition process. Optionally, the OD-SIB1 acquisition process can be completed successfully or fail.

[0152] Optionally, in step S202, the UE performs the RA report determination procedure to set (or determine) random access public information (e.g., ra-InformationCommon, or version 16 ra-InformationCommon).

[0153] Optionally, a new item is added to the random access report variable to record information associated with the random access procedure. Optionally, during the determination of random access common information, the content of the random access common information is set, including: subcarrier spacing (e.g., subCarrierSpacing).

[0154] Optionally, when the purpose of the random access procedure is to request SIB1 (or OD-SIB1), the UE sets the subcarrier spacing in one of the following ways:

[0155] - Set the subcarrier spacing to the subcarrier spacing of the carrier (e.g., ULSubCarrierSpacing).

[0156] - Set the subcarrier spacing to the subcarrier spacing of message 1;

[0157] - Set the subcarrier spacing to any value;

[0158] - Replace the field containing the subcarrier interval with a dummy value.

[0159] Optionally, the subcarrier spacing indicates the subcarrier spacing of the carrier corresponding to the random access procedure (the random access resource used).

[0160] Optionally, the carrier refers to the carrier corresponding to the random access procedure (the random access resource used). Optionally, the subcarrier spacing of the carrier is the subcarrier spacing of the carrier included in the SIB1 request configuration in step S101.

[0161] Optionally, message 1 is message 1 sent by the random access procedure, and message 1 is the random access preamble.

[0162] Optionally, the null value means that the field is not used in the current protocol version, and the base station ignores the received value.

[0163] Figure 3 This is a schematic diagram illustrating method three executed by the UE according to one or more embodiments. The UE can execute... Figure 3 One or more steps. Figure 3 This includes steps S301 to S302.

[0164] Optionally, steps S301 and S201 are the same.

[0165] Optionally, in step S302, the UE performs the RA report determination process to set (or determine) random access public information (e.g., ra-InformationCommon).

[0166] Optionally, a new item is added to the random access report variable to record information associated with the random access procedure. Optionally, during the determination of random access common information, the content of the random access common information is set, including: the subcarrier spacing of the carrier (e.g., ULSubCarrierSpacing).

[0167] Optionally, the purpose of triggering the random access procedure is to request SIB1 (or OD-SIB1) to set the subcarrier spacing of the carrier.

[0168] Optionally, the subcarrier spacing of the carrier indicates the subcarrier spacing of the carrier corresponding to the random access procedure (the random access resource used).

[0169] Optionally, the carrier refers to the carrier corresponding to the random access procedure (the random access resource used). Optionally, the subcarrier spacing of the carrier is set to the subcarrier spacing of the carrier included in the SIB1 request configuration in step S101.

[0170] Figure 4 This is a schematic diagram illustrating method four executed by the UE according to one or more embodiments. The UE can execute... Figure 4 One or more steps. Figure 4 This includes steps S401 to S402.

[0171] Optionally, steps S401 and S201 are the same.

[0172] Optionally, in step S402, the UE performs the RA report determination procedure to set (or determine) random access public information (e.g., ra-InformationCommon).

[0173] Optionally, a new item can be added to the random access report variable to record information associated with the random access procedure. Optionally, during the determination of random access public information, the content of the random access public information can be set, including: location and bandwidth (e.g., locationAndBandwidth).

[0174] Optionally, when the purpose of the random access procedure is to request SIB1 (or OD-SIB1), the UE sets the location and bandwidth in one of the following ways:

[0175] - Set the location and bandwidth to any value;

[0176] - Set the location and bandwidth to a specific value, such as 37950;

[0177] - Replace the fields containing the location and bandwidth with dummy values.

[0178] - Set the location and bandwidth as the UE calculation values.

[0179] Optionally, the null value means that the field is not used in the current protocol version, and the base station ignores the received value.

[0180] Optionally, the location and bandwidth indicate the location and bandwidth corresponding to the random access procedure (the random access resources used).

[0181] Optionally, the UE calculated value is a value calculated by the UE according to the carrier offset (e.g., offsetToCarrier), and / or the subcarrier spacing of the carrier, and / or the carrier bandwidth, using a formula specified in the protocol. Optionally, the UE calculated value should be understood as a resource indication value. Optionally, the formula specified in the protocol is the formula used by the base station to calculate the location and bandwidth in the BWP configuration described in the relevant technical section.

[0182] Optionally, the carrier offset is the carrier offset included in the SIB1 request configuration in step S101, the carrier bandwidth is the carrier bandwidth included in the SIB1 request configuration in step S101, and the subcarrier spacing of the carrier is the subcarrier spacing of the carrier included in the SIB1 request configuration in step S101.

[0183] Figure 5This is a schematic diagram illustrating method five executed by the UE according to one or more embodiments. The UE can execute... Figure 5 One or more steps. Figure 5 This includes steps S501 to S502.

[0184] Optionally, steps S501 and S201 are the same.

[0185] Optionally, in step S502, the UE performs the RA report determination process to set (or determine) random access public information (e.g., ra-InformationCommon).

[0186] Optionally, a new item is added to the random access report variable to record information associated with the random access procedure. Optionally, during the determination of random access common information, the content of the random access common information is set, including: carrier offset (offsetToCarrier).

[0187] Optionally, when the purpose of the random access procedure is to request SIB1 (or OD-SIB1), the carrier offset is set.

[0188] Optionally, the carrier offset refers to the frequency domain offset between Point A (the lowest subcarrier of common RB 0) and the lowest available subcarrier on the carrier, in units of PRB(s). Optionally, the carrier offset indicates the carrier offset of the carrier corresponding to the random access procedure (the random access resources used).

[0189] Optionally, the carrier refers to the carrier corresponding to the random access procedure (the random access resource used). Optionally, the carrier offset is set to the carrier offset included in the SIB1 request configuration in step S101.

[0190] Figure 6 This is a schematic diagram illustrating method six executed by the UE according to one or more embodiments. The UE can execute... Figure 6 One or more steps. Figure 6 This includes steps S601 to S602.

[0191] Optionally, steps S601 and S201 are the same.

[0192] Optionally, in step S602, the UE performs the RA report determination process to set (or determine) the first random access public information.

[0193] Optionally, the first random access common information is: OD-SIB1 random access common information (e.g., ra-InformationCommon-SIB1), or version 19 random access common information (e.g., ra-InformationCommon-r19). Optionally, the first random access common information is used to provide information about the random access procedure (or random access attempt) triggered for requesting SIB1 (or OD-SIB1).

[0194] Optionally, a new item is added to the random access report variable to record information associated with the random access procedure. Optionally, the first random access public information is set during the process of determining the first random access public information.

[0195] Optionally, when the purpose of triggering the random access procedure is to request SIB1 (or OD-SIB1) to set the first random access public information.

[0196] Optionally, if the first random access public information exists, the version 16 random public information is ignored by the (base station).

[0197] Optionally, when the random access procedure is triggered for the purpose of requesting SIB1 (or OD-SIB1), or when the random access procedure is triggered for the purpose of requesting (or OD-SIB1), the version 16 random public information is ignored by the (base station), and / or the first random access public information exists (or is required to exist); otherwise, the first random access public information does not exist.

[0198] Figure 7 This is a schematic diagram illustrating method seven executed by the UE according to one or more embodiments. The UE can execute... Figure 7 One or more steps. Figure 7 This includes steps S701 to S704.

[0199] Optionally, in step S701, the UE receives system information and / or RRC-specific messages (e.g., RRCReconfiguration messages) sent by the network. Optionally, the system information and / or RRC-specific messages include first indication information. Optionally, the first indication information is used to indicate at least one of the following:

[0200] -Whether the UE is allowed (or can) select the OD-SIB1 cell when initiating an RRC connection re-establishment;

[0201] -Whether the UE is allowed (or may) initiate (or enable) a SIB1 request procedure (or initiate a random access procedure triggered to request SIB1 / OD-SIB1) in the OD-SIB1 cell when initiating an RRC connection re-establishment.

[0202] Optionally, selecting OD-SIB1 cell means selecting OD-SIB1 cell during the cell selection process when initiating RRC connection re-establishment.

[0203] Optionally, in step S702, the UE initiates an RRC connection reconstruction procedure.

[0204] Optionally, when the UE detects a radio link failure in the MCG, or when the RRC connection reconfiguration fails, the UE initiates an RRC connection reconstruction procedure.

[0205] Optionally, the UE performs cell selection.

[0206] Optionally, during the cell selection process, the UE determines the first indication, whether to select the OD-SIB1 cell, and / or whether to initiate the SIB1 request process when the OD-SIB1 cell is selected.

[0207] Optionally, the UE may select OD-SIB1 cell during cell selection if at least one of the following conditions is met, i.e., the UE normally performs the cell selection procedure:

[0208] -The system information and / or RRC proprietary message contains the first indication;

[0209] - The first indication is set to TRUE;

[0210] - The first indication indicates that the UE is allowed to select the OD-SIB1 cell when initiating an RRC connection re-establishment.

[0211] Optionally, the UE excludes the OD-SIB1 cell during the cell selection process if at least one of the following conditions is met:

[0212] - The system information and / or RRC proprietary message does not contain the first indication;

[0213] - The first indication is set to FALSE;

[0214] - The first indication indicates that the UE is not allowed to select the OD-SIB1 cell when initiating RRC connection re-establishment.

[0215] Optionally, (optionally, when the UE selects cell OD-SIB1 during cell selection) at least one of the following conditions is determined:

[0216] -The system information and / or RRC proprietary message contains the first indication;

[0217] - The first indication is set to TRUE;

[0218] - The first instruction allows the UE to initiate (or enable) a SIB1 request procedure (or initiate a random access procedure triggered to request SIB1 / OD-SIB1) in the OD-SIB1 cell when initiating an RRC connection re-establishment.

[0219] - The UE has a (valid) SIB1 request configuration for the OD-SIB1 cell.

[0220] Optionally, if at least one of the above conditions is met, the UE initiates (or enables) the SIB1 request procedure (or initiates a random access procedure triggered to request SIB1 / OD-SIB1).

[0221] Optionally, the SIB1 request procedure (or the random access procedure triggered for requesting SIB1 / OD-SIB1) is initiated in the OD-SIB1 cell, which is the OD-SIB1 cell selected in the cell selection process during the RRC connection reconstruction procedure.

[0222] Optionally, in step S703, the UE obtains system information from the selected cell and determines whether the selected cell is a suitable cell based on the configuration information in the system information.

[0223] Optionally, in step S704, the UE initiates the transmission of an RRC Reestablishment Request message. Optionally, the UE initiates the transmission of the RRC Reestablishment Request message in the selected appropriate cell.

[0224] Figure 8 This is a schematic diagram of method eight executed by the UE according to one or more embodiments. The UE can execute... Figure 8 One or more steps. Figure 8 This includes steps S801 to S802.

[0225] Optionally, in step S801, the UE receives system information and / or RRC-specific messages (e.g., RRCReconfiguration message or RRCRelease message) sent by the network.

[0226] Optionally, the system information includes at least one of the following configuration parameters:

[0227] -Cell reselection priority;

[0228] -NES cell reselection priority;

[0229] Optionally, cell reselection priority and / or NES cell reselection priority may be included in the same system information or in different system information. Optionally, cell reselection priority and / or NES cell reselection priority may correspond to a frequency, that is, the network is configured with cell reselection priority and / or NES cell reselection priority for one or more frequencies.

[0230] Optionally, the RRC proprietary message includes at least one of the following configuration parameters:

[0231] - NR frequency priority list (FreqPriorityListNR);

[0232] - A NES frequency priority list (e.g., FreqPriorityListNES), or a proprietary NES frequency priority list (e.g., FreqPriorityListDedicatedNES).

[0233] - (Proprietary) Cell reselection priority;

[0234] - (Proprietary) NES cell reselection priority.

[0235] Optionally, the (proprietary) cell reselection priority is included in the NR frequency priority list (FreqPriorityListNR), and the (proprietary) NES cell reselection priority is included in the NES frequency priority list or a proprietary NES frequency priority list. Optionally, the (proprietary) cell reselection priority included in the NES frequency priority list or a proprietary NES frequency priority list is (or equivalent to, or considered as) the (proprietary) NES cell reselection priority.

[0236] Optionally, the cell reselection priority indicates the absolute priority of the frequency, used in the cell reselection process. The NES cell reselection priority indicates the absolute priority of the frequency for the NES UE, or the absolute priority of the frequency where an NES cell exists, used in the cell reselection process.

[0237] Optionally, in step S802, the UE determines how to apply the configuration parameters from step S801 to perform a cell reselection assessment.

[0238] Optionally, if an NES frequency priority list or a proprietary NES frequency priority list is configured, the UE will only consider the frequencies indicated in the NES frequency priority list or the proprietary NES frequency priority list for cell reselection.

[0239] Optionally, if a frequency does not have a (proprietary) NES cell reselection priority, the lowest priority value is used. Optionally, the lowest priority value is lower than any priority value configured in the network.

[0240] Unless otherwise specified, the order of judgments and operations in this embodiment is irrelevant; that is, the order of judgments and operations can be interchanged.

[0241] Figure 9 This is a simplified structural block diagram of the user equipment (UE) involved in this invention. Figure 9 As shown, the user equipment UE900 includes a processor 901 and a memory 902. The processor 901 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 902 may include, for example, volatile memory (such as random access memory, RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Program instructions are stored on the memory 902. When executed by the processor 901, these instructions can perform the methods described in detail herein, executed by the user equipment.

[0242] The program running on the device according to the invention can be a program that enables the computer to perform the functions of embodiments of the invention by controlling the 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.

[0243] Programs used to implement the functions of the various embodiments of the present invention can be recorded on a computer-readable recording medium. The corresponding functions can be implemented by causing a computer system to read and execute the programs recorded on the recording medium. The term "computer system" here can refer to a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices). "Computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-time dynamic storage program recording medium, or any other computer-readable recording medium.

[0244] Various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., monolithic or multi-chip integrated circuits). Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. A general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuits may be digital circuits or analog circuits. In cases where advancements in semiconductor technology have led to new integrated circuit technologies that replace existing integrated circuits, one or more embodiments of the present invention may also be implemented using these new integrated circuit technologies.

[0245] Furthermore, the present invention is not limited to the embodiments described above. Although various examples of the embodiments have been described, the present invention is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0246] As described above, embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and the present invention also includes any design modifications that do not depart from the spirit of the invention. Furthermore, various modifications can be made to the present invention within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. In addition, components with the same effects described in the above embodiments can be substituted for each other.

Claims

1. A method executed by a user equipment (UE), comprising: The UE receives system information and / or RRC proprietary messages sent by the network, wherein the system information and / or RRC proprietary messages include SIB1 request configuration; The UE initiates a random access procedure according to the SIB1 request configuration and determines the reason for triggering the random access procedure; and The UE executes the random access procedure. If the random access procedure is triggered to initiate an SIB1 request, the UE does not perform a BWP operation; or the UE performs a BWP operation except when the random access procedure is triggered to initiate an SIB1 request.

2. The method according to claim 1, wherein, The method further includes: After completing the random access procedure, the UE executes the RA report determination procedure to set or determine random access common information or first random access common information.

3. The method according to claim 2, wherein, In determining the random access public information, the content of the random access public information is set, including setting the subcarrier interval. When the random access procedure is triggered with the purpose of requesting SIB1, the UE sets the subcarrier spacing in one of the following ways: - Set the subcarrier spacing to the subcarrier spacing of the carrier; - Set the subcarrier spacing to the subcarrier spacing of message 1; - Set the subcarrier spacing to any value; - Replace the field containing the subcarrier interval with an empty value.

4. The method according to claim 2, wherein, In determining the random access public information, the content of the random access public information is set, including setting the subcarrier interval of the carrier. The subcarrier spacing of the carrier is set to the subcarrier spacing of the carrier included in the SIB1 request configuration.

5. The method according to claim 2, wherein, In determining the public random access information, the content of the public random access information is set, including setting the location and bandwidth. When the random access procedure is triggered with the purpose of requesting SIB1, the UE sets the location and bandwidth in one of the following ways: - Set the location and bandwidth to any value; - Set the location and bandwidth to a specific value; - Replace the fields containing the location and bandwidth with empty values; - Set the location and bandwidth as the UE calculation values.

6. The method according to claim 2, wherein, In determining the random access public information, the content of the random access public information is set, including setting the carrier offset. The carrier offset is set to the carrier offset included in the SIB1 request configuration.

7. The method according to claim 2, wherein, The first random access public information is either OD-SIB1 random access public information or version 19 random access public information. If the first random access public information exists, the version 16 random public information is ignored by the base station.

8. A user equipment, comprising: processor; as well as Memory, which stores instructions The instructions, when executed by the processor, perform the method of any one of claims 1 to 7.

Images