Uplink signal sending method, resource configuration method, device, terminal, network side equipment and medium

Abstract

The invention discloses an uplink signal sending method, a resource configuration method and device, a terminal, network side equipment and a medium, and belongs to the technical field of communication, and the uplink signal sending method comprises the steps that user equipment UE sends a target uplink signal based on UE characteristics and first configuration information; wherein the first configuration information corresponds to at least one UE feature, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature; the target uplink signal is used for requesting adjustment of a downlink signal or a channel of a target cell.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an uplink signal transmission method, resource allocation method, apparatus, terminal, network-side equipment, and medium. Background Technology

[0002] In scenarios where communication networks employ energy-saving mechanisms, the design of the Wake-Up Signal (WUS) configuration is crucial for achieving efficient energy saving and cell reselection processes.

[0003] In related technologies, when a UE sends a Target Uplink (WUS) signal to request a System Information Block (SIB) from a cell, if the SIB1 of that cell explicitly prohibits that type of UE from camping, the UE's request is invalid, preventing the UE from reselecting to that cell. Alternatively, if the WUS configuration is designed to apply to multiple cells, and UEs with specific UE characteristics simultaneously send WUS requests to these cells, a cell that does not support that specific UE characteristic may incorrectly respond to a UE with that characteristic, preventing the UE from reselecting to a cell that responds to its request. This increases the number of attempts and latency during the cell reselection process, resulting in poor communication performance. Summary of the Invention

[0004] This application provides an uplink signal transmission method, resource allocation method, apparatus, terminal, network-side equipment, and medium, which can reduce the latency of downlink signals or channels requesting a target cell, thereby improving communication performance.

[0005] In a first aspect, an uplink signal transmission method is provided, executed by a terminal, the method comprising: a user equipment (UE) transmitting a target uplink signal based on UE characteristics and first configuration information; wherein the first configuration information corresponds to at least one UE characteristic, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE characteristic; the target uplink signal is used to request adjustment of downlink signals or channels of a target cell.

[0006] Secondly, a resource configuration method is provided, executed by a network-side device, the method comprising: the network-side device sending first configuration information to a UE; wherein the first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature.

[0007] Thirdly, an uplink signal transmitting apparatus is provided, the apparatus comprising: a transmitting module; the transmitting module being configured to transmit a target uplink signal based on UE characteristics and first configuration information; wherein the first configuration information corresponds to at least one UE characteristic, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE characteristic; the target uplink signal is used to request adjustment of downlink signals or channels of a target cell.

[0008] Fourthly, a resource configuration apparatus is provided, comprising: a transmitting module; the transmitting module being configured to transmit first configuration information to a user equipment (UE); wherein the first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature.

[0009] Fifthly, a communication device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0010] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0011] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send a target uplink signal based on UE characteristics and first configuration information; wherein the first configuration information corresponds to at least one UE characteristic, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE characteristic; the target uplink signal is used to request adjustment of downlink signals or channels of a target cell.

[0012] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0013] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send first configuration information to a UE; wherein the first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature.

[0014] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0015] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0016] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0017] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the uplink signal transmission method as described in the first aspect or the steps of the resource allocation method as described in the second aspect.

[0018] In this embodiment, the UE transmits a target uplink signal based on its UE type and first configuration information. This first configuration information corresponds to at least one UE type, or the first configuration information indicates at least one target uplink signal resource corresponding to at least one UE type. The target uplink signal is used to request downlink signals or channels from the target cell. Through this method, the UE can pre-determine whether the target cell supports its UE type based on the first configuration information and its own UE type. This allows the UE to transmit the target uplink signal when the target cell supports its UE type, reducing the number of attempts and latency of the UE requesting downlink signals or channels from the target cell, thereby improving communication performance. Attached Figure Description

[0019] Figure 1 A block diagram of a wireless communication system provided in an embodiment of this application;

[0020] Figure 2 A flowchart illustrating the uplink signal transmission method provided in an embodiment of this application;

[0021] Figure 3 A flowchart illustrating the resource configuration method provided in an embodiment of this application;

[0022] Figure 4A One of the schematic diagrams illustrating the correspondence between NES cells and SSBs, and the mapping relationship between the actual transmitted SSB index and SSBs, provided in the embodiments of this application;

[0023] Figure 4B The second schematic diagram illustrates the correspondence between NES cells and SSBs, as well as the mapping relationship between the actual transmitted SSB index and SSBs, provided in the embodiments of this application.

[0024] Figure 4C A schematic diagram illustrating the mapping relationship between WUS resources and SSBs provided in this application embodiment;

[0025] Figure 4D A schematic diagram illustrating the mapping of the maximum actual number of SSBs transmitted by the NES cell associated with the WUS configuration, as provided in the embodiments of this application.

[0026] Figure 5 A schematic diagram of the RO corresponding to the NES cell associated with the WUS configuration provided in this embodiment of the application;

[0027] Figure 6A One of the schematic diagrams illustrating the correspondence between NES cells and preambles provided in the embodiments of this application;

[0028] Figure 6B The second schematic diagram illustrating the correspondence between NES cells and preambles provided in the embodiments of this application;

[0029] Figure 7 A schematic diagram of the RO corresponding to the UE features supported by the NES cell associated with the WUS configuration provided in this application embodiment;

[0030] Figure 8A One of the schematic diagrams of the preamble corresponding to the UE features supported by the NES cell associated with the WUS configuration provided in the embodiments of this application;

[0031] Figure 8B A second schematic diagram of the preamble corresponding to the UE features supported by the NES cell associated with the WUS configuration provided in this application embodiment;

[0032] Figure 8C The third schematic diagram of the preamble corresponding to the UE features supported by the NES cell associated with the WUS configuration provided in this application embodiment;

[0033] Figure 9 A schematic diagram illustrating different RO resources provided in the embodiments of this application;

[0034] Figure 10 A schematic diagram illustrating different preamble resources provided for embodiments of this application;

[0035] Figure 11 This is a schematic diagram illustrating the interaction process between the Redcap UE and the NES Cell, provided in an embodiment of this application.

[0036] Figure 12 This is a schematic diagram of the structure of the uplink signal transmitting device provided in the embodiments of this application;

[0037] Figure 13 This is a schematic diagram of the structure of the resource allocation device provided in the embodiments of this application;

[0038] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0039] Figure 15 A schematic diagram of the hardware structure of the terminal provided in the embodiments of this application;

[0040] Figure 16 This is a schematic diagram of the hardware structure of the network-side device provided in an embodiment of this application. Detailed Implementation

[0041] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0042] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0043] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0044] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0045] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0046] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support Function. Support Functions (BSF), Application Functions (AF), Location Management Functions (LMF), Gateway Mobile Location Centres (GMLC), and Network Data Analytics Functions (NWDAF), etc. It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0047] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0048] The following is an explanation of the terms used in this application.

[0049] Network energy savings (NES) technology:

[0050] In existing technologies, the main idea behind network energy-saving technologies is to reduce unnecessary uplink / downlink and time / frequency / spatial domain transmissions without significantly impacting terminal services or system performance, thereby achieving network energy conservation. Cells can exchange cell on / off request information via the Xn interface. Specifically, energy-saving cells can shut down when the load is low based on implementation decisions, and then reopen the cell to provide services to terminals upon receiving a wake-up signal (WUS) from another cell. Currently, various potential network energy-saving technologies are being discussed, including time-domain energy-saving technologies (such as common signal adaptation, OD-SSB / SIB1), frequency-domain energy-saving technologies (such as anchor cells), and spatial-domain energy-saving technologies. Ultimately, in the Work Item phase, energy-saving technologies such as spatial / power domain CSI measurement reporting optimization, cell DTRX, and inter-band SSB-less SCell operation were standardized.

[0051] Random Access Radio Network Temporary Identifier (RA-RNTI):

[0052] RA-RNTI is used during random access. The base station's Medium Access Control (MAC) layer generates a Random Access Response (RAR) as a response to the Random Access Preamble (RAP) sent by the terminal. The RAR is transmitted on the Downlink Shared Channel (DL-SCH), which is ultimately mapped to the Physical Downlink Shared Channel (PDSCH). To transmit the PDSCH of the RAR(s), the gNB uses RA-RNTI to scramble the Cyclic Redundancy Check (CRC) of the Physical Downlink Control Channel (PDCCH). RA-RNTI can address multiple terminals, meaning multiple terminals may decode the same scrambled PDCCH. During random access, a terminal selects a random preamble to obtain uplink synchronization. This preamble is referenced by a random access preamble identifier (ID), and each preamble transmission is associated with a RA-RNTI.

[0053] As can be seen from the configuration of RA-RNTI, terminals that send Random Access Message 1 (MSG1) during the same Physical Random Access Channel (PRACH) occcasion will use the same RA-RNTI to listen to the PDCCH. This means that if the base station responds to one (or several) of these terminals, the other terminals will also successfully descramble the RAR MAC PDU. Conversely, if a terminal successfully descrambles the RAR MAC Protocol Data Unit (PDU), it does not mean that the terminal has successfully received a response; it is also necessary to check whether the RAR MAC PDU contains the Preamble Index corresponding to MSG1.

[0054] RA-RNTI is related to PRACH Occasion. The terminal and the base station calculate RA-RNTI according to PRACH Occasion to realize the scrambling and descrambling of Random Access Message 2 (MSG2).

[0055] In NR, RA-RNTI = 1 + s_id + 14 * t_id + 14 x 80 x f_id + 14 x 80 x 8 x ul_carrier_id. Here, s_id represents the index of the first Orthogonal Frequency Division Multiplexing (OFDM) symbol (within a PRACH Occasion), with a value from 0 to 13; t_id represents the index of the first slot of the PRACH Occasion (within a system frame), with a value from 0 to 79; f_id represents the frequency domain index of the PRACH Occasion, with the same meaning as in LTE, and a value from 0 to 8; ul_carrier_id represents the uplink carrier used by the PRACH, with a value of 0 indicating a non-Supplementary Uplink (NUL) carrier and a value of 1 indicating a Supplementary Uplink Carrier (SUL) carrier.

[0056] Specifically, a NUL carrier is a commonly used uplink carrier in communication, providing uplink transmission services within normal signal coverage areas. When a terminal communicates in an area with good signal strength, it typically uses an NUL carrier to transmit data. A SUL carrier is a carrier method introduced to address the problem of limited uplink coverage. In high-frequency communication systems such as 5G, the higher frequency leads to faster signal attenuation, resulting in limited uplink coverage distance. To extend uplink coverage, the system configures a low-frequency SUL carrier within the same cell. When a terminal is in an area with weak signal (such as the cell edge), it can use the SUL carrier for uplink transmission, thereby improving the effectiveness and reliability of uplink coverage.

[0057] The uplink signal transmission method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0058] Figure 2 This is a flowchart illustrating the uplink signal transmission method provided in an embodiment of this application, as shown below. Figure 2 As shown, the uplink signal transmission method may include the following step 201:

[0059] Step 201: The UE sends a target uplink signal based on the UE characteristics and the first configuration information.

[0060] Wherein, the first configuration information corresponds to at least one UE feature, or the first configuration information indicates at least one target uplink signal resource that corresponds to at least one UE feature; the target uplink signal is used to request the adjustment of the downlink signal or channel of the target cell.

[0061] In some embodiments of this application, the aforementioned UE features refer to the technical characteristics or functions possessed or supported by the UE; or to the UE type or category.

[0062] For example, UE features may include, but are not limited to, at least one of the following:

[0063] Communication capabilities, such as supported network standards, data transmission rates, and spectrum efficiency;

[0064] Software features: such as operating system, application support, multimedia processing capabilities, security, etc.

[0065] Special features include support for high-definition voice calls (VoLTE), wireless LAN voice calls (VoWiFi), device-to-device (D2D) communication, and the Internet of Things (IoT).

[0066] For example, the UE type may include, but is not limited to, at least one of the following:

[0067] Reduced Capability (RedCap) type;

[0068] Non-Terrestrial Network (NTN) type;

[0069] XR (AR, VR) Virtual Reality;

[0070] ATG (Air to ground);

[0071] VSAT;

[0072] nes-CellDTX-DRX;

[0073] SDT;

[0074] MBS;

[0075] Uplink coverage enhancement, etc.

[0076] It's important to note that RedCap is a new technology standard protocol introduced by 3GPP (3rd Generation Partnership Project) in the 5G Release 17 phase. It aims to provide a lightweight 5G solution for 5G application scenarios with lower requirements for speed and latency. RedCap devices fall between Enhanced Mobile Broadband (eMBB) and Low-Power Wide-Area Network (LPWAN) in terms of bandwidth, power consumption, antenna design, and cost, effectively balancing the capabilities of 5G—high bandwidth, high speed, wide connectivity, and low latency—to meet the diverse networking needs of various industries. RedCap reduces the complexity and cost of terminal equipment by decreasing bandwidth, the number of transceiver antennas, lowering data rates, and adjusting modulation methods. NTN is an important direction in the evolution of 5G technology. It refers to providing wireless communication services through non-terrestrial infrastructure such as satellites and drones. The introduction of NTN enables 5G networks to cover a wider geographical area, including remote areas, oceans, and areas inaccessible to traditional terrestrial networks. NTN-type UEs refer to UEs that can access NTN networks and utilize communication services provided by satellite or drone platforms.

[0077] It should be noted that the UE feature, or UE feature in this application embodiment, can be described as at least one of the following: UE type, UE category, UE class, etc. Among them, UE category refers to terminal capability level or terminal level, and UE category can also be abbreviated as UE Cat.

[0078] It should be noted that UE features, UE type, UE category, etc., all refer to UEs that support certain technical features, or different UE types or categories.

[0079] It should be noted that the types, features, profiles, etc. of the "devices" involved in this patent include terminal or network devices.

[0080] In some embodiments of this application, the first configuration information described above may be pre-configured.

[0081] In some embodiments of this application, the aforementioned first configuration information may be indicated by a network-side device; the first configuration information is used to indicate at least one of the following:

[0082] The identifier or identifier list of the first cell associated with the first configuration information;

[0083] The first configuration information is associated with the first cell corresponding to ssb-positionInBurst;

[0084] The UE characteristics associated with the first configuration information;

[0085] Target uplink signal feedback monitoring configuration;

[0086] Target configuration;

[0087] The maximum number of SSBs allowed for SSB mapping;

[0088] The total number of RA-Preambles used for random access;

[0089] The target time period is used to determine the time when the UE listens for the uplink signal feedback from the target.

[0090] It should be noted that SSB stands for Synchronization Signal / PBCH Block.

[0091] It should be noted that the first configuration information mentioned above can be for WUS configuration.

[0092] In this embodiment of the application, the first configuration information described above can be replaced with the first configuration.

[0093] The first cell mentioned above is a cell that allows UEs to request adjustments to downlink signals or channels.

[0094] In some embodiments of this application, the first configuration information may be associated with one or more first cells. For example, the first cell may include, but is not limited to, an energy-saving cell or a non-energy-saving cell.

[0095] In some embodiments of this application, an energy-saving cell refers to a cell that employs energy-saving technologies, such as supporting on-demand SIB1, supporting on-demand SSB, supporting cell DRX / DTX, and supporting dynamic shutdown of spatial antennas.

[0096] In some examples, the maximum number of NES cells that can be associated per WUS configuration is 2, 4, or 8.

[0097] In some examples, the identifier of the first cell can be NES_cell_id, which means that NES_cell_id represents the identifier of the NES cell associated with this WUS configuration, and the value ranges from 1 to the maximum number of NES cells that can be associated.

[0098] In some embodiments of this application, the identifier list of the first cell may include identifiers of multiple first cells associated with the first configuration information.

[0099] It should be noted that ssb-positionInBurst refers to the actual position of the SSB transmitted by the cell associated with this parameter. It is a bitmap, where each bit corresponds to an SSB index. A bit value of 1 means that the SSB of the corresponding SSB index will be transmitted normally, and a bit value of 0 means that the SSB of the corresponding SSB index will not be transmitted.

[0100] It should be noted that ssb-positionInBurst in the embodiments of this application can be replaced by the SSB bitmap actually sent in the SSB burst, the number and position of the SSBs actually sent in the SSB burst, the SSBs actually sent in the SSB burst, the number of SSBs actually sent, etc.

[0101] In some embodiments of this application, the first configuration information may be associated with one or more UE features.

[0102] For example, the WUS configuration may include capability or feature information related to specific device types or features supported by the WUS configuration, such as device category, supported technologies, or specific behavior patterns.

[0103] In some embodiments of this application, the aforementioned target uplink signal feedback monitoring configuration is used to instruct the UE to monitor and respond to uplink signal feedback. Exemplarily, the aforementioned target uplink signal feedback monitoring configuration may include, but is not limited to, information such as the monitoring time window, frequency resources, and required modulation and coding scheme, to ensure that the UE can correctly receive and respond to feedback from the base station. In some examples, the aforementioned target uplink signal feedback may be RAR.

[0104] It should be noted that the above-mentioned target uplink signal feedback can be replaced by WUS feedback.

[0105] In some embodiments of this application, the target configuration described above may include, but is not limited to, the time-frequency resource configuration for transmitting the target uplink signal.

[0106] In some embodiments of this application, the maximum number of SSBs allowed by the above-mentioned SSB mapping is used to indicate the maximum number of SSBs allowed to be mapped when SSBs of multiple cells are mapped on the same time-frequency resources.

[0107] In some embodiments of this application, the aforementioned target time period can instruct the UE to listen for uplink signal feedback from the base station within that target time period, thereby reducing the UE's listening time and power consumption, and improving the accuracy and efficiency of its feedback reception. For example, the aforementioned target time period can be a time window.

[0108] In some embodiments of this application, the target time period may be included in the first configuration information or agreed upon by a protocol.

[0109] In some embodiments of this application, the aforementioned target uplink signal can be used to request the target cell to send downlink signals or channels.

[0110] In some embodiments of this application, the aforementioned target uplink signal includes, but is not limited to, a random access request.

[0111] In some examples, the target uplink signal can be WUS.

[0112] In some examples, the target uplink signal can be a preamble sequence.

[0113] It should be noted that the above target uplink signal can be replaced by a WUS request or an on-demand SIB1 request.

[0114] In some embodiments of this application, the target cell is the cell in which the UE requests an adjustment of the downlink signal or channel; for example, the target cell may include, but is not limited to, energy-saving cells and non-energy-saving cells.

[0115] It should be noted that an energy-saving cell, or NES cell, refers to a wireless communication cell that uses energy-saving technologies or a cell that has activated energy-saving mode.

[0116] In some embodiments of this application, the aforementioned target uplink signal resources include, but are not limited to, time-frequency resources used by the UE to transmit uplink signals, random access timing (RACH Occasion, RO), etc.

[0117] In the embodiments of this application, the first configuration information or the target uplink signal resource indicated in the first configuration information corresponds to certain characteristics of the UE (such as device type, capabilities, etc.), thereby ensuring that the uplink signal resource can be effectively utilized by the UE and meet its specific communication needs.

[0118] In some embodiments of this application, the first configuration information described above configures only a single ssb-positionInBurst, and this single ssb-positionInBurst can be associated with multiple first cells.

[0119] For example, only one ssb-positionInBurst can be configured, and the ssb-positionInBurst of multiple NES cells can be consistent.

[0120] In some embodiments of this application, the first configuration information described above configures multiple ssb-positionInBursts, and each of the multiple ssb-positionInBursts is associated with a multiple first cell.

[0121] For example, a corresponding ssb-positionInBurst is configured for each NES cell, and the number of bits with 1 in the ssb-positionInBurst of each NES cell is consistent.

[0122] In some embodiments of this application, the above-mentioned target uplink signal feedback monitoring configuration includes at least one of the following:

[0123] Target uplink signal feedback search space configuration;

[0124] Target uplink signal feedback control resource set configuration.

[0125] In some examples, the target uplink signal feedback search space configuration described above can indicate the search space corresponding to the target uplink signal feedback. This configuration can include search space parameters for the target uplink signal feedback, such as the number of PDCCH candidates and the aggregation level. By configuring the target uplink signal feedback search space, the UE can accurately receive and decode the target uplink signal feedback.

[0126] In some examples, the target uplink signal feedback control resource set configuration can indicate the control resource set used to transmit the target uplink signal feedback. By configuring the control resource set, the feedback information of the target uplink signal can be transmitted to the UE efficiently and accurately, thereby ensuring the performance of the communication system.

[0127] In some embodiments of this application, the target configuration includes at least one set of configurations, each set of configurations corresponding to at least one first cell, or each set of configurations corresponding to at least one UE feature, or each set of configurations corresponding to at least one UE feature supported by at least one first cell.

[0128] In some examples, the WUS configuration may include multiple target configurations, each corresponding to one of multiple NES cells, with one target configuration corresponding to one NES cell; or the multiple target configurations may correspond to at least one UE feature, with one target configuration corresponding to one or more UE features; or the multiple target configurations may correspond to at least one UE feature supported by at least one NES cell, with one target configuration corresponding to one or more UE features supported by one or more NES cells.

[0129] It is understandable that multiple target configurations correspond one-to-one with multiple NES cells, meaning that each NES cell has an independent set of target configurations.

[0130] In some examples, the WUS configuration may include a set of target configurations, which may correspond to one or more NES cells; or a set of target configurations may correspond to one or more UE features; or a set of target configurations may correspond to at least one UE feature supported by at least one NES cell.

[0131] It is understandable that one set of target configurations corresponds to one or more NES cells, meaning that multiple NES cells share the same set of target configurations.

[0132] In some embodiments of this application, the target configuration described above may include at least one of the following:

[0133] UE characteristics associated with the target configuration;

[0134] Devices supporting specific technical features request time-frequency resource allocation for the target downlink signal or the target uplink signal, adjusting the channel.

[0135] SSB mapping related configurations;

[0136] Target uplink signal preamble sequence resource configuration;

[0137] Target uplink signal time-frequency resource allocation;

[0138] The SIB1 request period, sib1-RequestPeriod, is measured in terms of the association period.

[0139] The association period identifier ra-AssociationPeriodIndex is used to indicate the available association period among multiple association periods;

[0140] The RO mask identifier ra-ssb-OccasionMaskIndex is used to indicate the available ROs among multiple ROs associated with a single SSB;

[0141] UEs that support specific technical features can be used to request UL WUS resource configuration for SIB1, such as a separately configured Redcap UE for requesting WUS resource configuration for SIB1, i.e., SIB1-RequestResourceRedCap.

[0142] The first indication information is used to indicate whether lightweight terminals are allowed to perform same-frequency reselection;

[0143] The second indication information is used to indicate whether the first cell allows the access of a lightweight terminal.

[0144] The third instruction information is used to indicate whether the first cell allows the access of two lightweight terminals;

[0145] The fourth indication information is used to indicate whether the first cell allows access for lightweight terminals that support half-duplex frequency division duplex.

[0146] The fifth indication information is used to indicate whether the first cell allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS).

[0147] The sixth instruction information is used to indicate whether the first cell allows air-to-ground connections;

[0148] The seventh indication information is used to indicate whether the first cell allows UEs supporting the nes-CellDTX-DRX feature to access;

[0149] The eighth indication information is used to indicate whether the enhanced lightweight UE is allowed to perform same-frequency reselection;

[0150] The ninth instruction information is used to indicate whether the first cell allows access for fixed very small aperture satellite communication (VSAT) terminals;

[0151] The tenth instruction information is used to indicate whether the first cell allows the mobile VSAT terminal to access;

[0152] The eleventh instruction information is used to indicate whether the first cell allows the access of the second extended reality XR terminal;

[0153] The twelfth instruction information is used to indicate whether two XR receiving terminals are allowed to perform same-frequency reselection;

[0154] The thirteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight terminal to access;

[0155] The fourteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight receiver terminal to access;

[0156] The fifteenth indication information is used to indicate whether the first cell allows the enhanced lightweight 2D receiver terminal to access;

[0157] The sixteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the random access channel (RACH) resources of the first cell;

[0158] The seventeenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the RACH resources of the first cell used for system information requests;

[0159] The eighteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the additional RACH resources of the first cell.

[0160] In some embodiments of this application, the above-mentioned SSB mapping-related configuration includes at least one of the following:

[0161] The number of SSBs associated with each RACH timing RO;

[0162] The number of preambles associated with each SSB.

[0163] It should be noted that the number of SSBs associated with each RACH event, i.e., ssb-perRACH-Occasion, is abbreviated as SSB per RO.

[0164] It should be noted that the number of preambles associated with each SSB is called the Preamble per SSB.

[0165] In some embodiments of this application, the above-mentioned target uplink signal preamble sequence resource configuration includes at least one of the following:

[0166] Preamble root sequence;

[0167] The number of preambles associated with each SSB;

[0168] Preamble start index;

[0169] Number of preambles in the target uplink signal;

[0170] Number of preambles used for random access.

[0171] It should be noted that the preamble start index is the index used to start the preamble.

[0172] In some embodiments of this application, the target uplink signal time-frequency resource configuration includes at least one of the following:

[0173] Frequency domain timings;

[0174] Frequency domain start timing identifier;

[0175] Physical Random Access Channel (PRACH) Configuration Index;

[0176] Permissible associated period identifiers;

[0177] Allowed RO mask identifiers.

[0178] It should be noted that the frequency domain timing quantity can be replaced by the description msg1-FDM.

[0179] It is understandable that msg1-FDM is a parameter used to indicate the number of ROs in the frequency domain.

[0180] It should be noted that the frequency domain start timing identifier can be replaced with the description msg1-FrequencyStart.

[0181] It should be noted that the Physical Random Access Channel (PRACH) configuration index can be replaced with the PRACH configuration index.

[0182] It can be understood that the PRACH Configuration Index is a configuration index used to specify the specific time-domain configuration of PRACH, such as the preamble format, the number of preamble repetitions, and the transmission subframes / slots.

[0183] In some examples, the target configuration in the WUS configuration may indicate at least one of the following:

[0184] Whether RedcapUE is allowed to reselect on the same frequency, i.e., the first indication information may include intraFreqReselectionRedCap;

[0185] Whether the first cell allows 1Rx Redcap UE access, i.e. the first indication information may include cellBarredRedCap1Rx;

[0186] Whether the first cell allows 2Rx Redcap UE access, i.e. the first indication information may include cellBarredRedCap2Rx;

[0187] Whether the first cell allows half-duplex FDD RedCap UE access, i.e., the first indication information may include halfDuplexRedCap-Allowed;

[0188] Whether the first cell allows UE access that supports a specific feature, which includes at least one of small data transmission (SDT) and multi-broadcast service (MBS);

[0189] Whether the first cell allows air-to-ground connections, i.e., the first indication information may include cellBarredATG-r18;

[0190] Whether the first cell allows UEs supporting the nes-CellDTX-DRX feature to access, i.e., the first indication information may include cellBarredNES-r18;

[0191] Whether to allow enhanced lightweight UE to perform intra-frequency reselection, i.e., the first indication information may include intraFreqReselection-eRedCap-r18;

[0192] Whether the first cell allows access to fixed VSAT terminals, i.e., the first indication information may include cellBarredFixedVSAT-r18;

[0193] Whether the first cell allows mobile VSAT terminal access, i.e., the first indication information may include cellBarredMobileVSAT-r18;

[0194] Whether the first cell allows access for two XR terminals, i.e., the first indication information may include cellBarred2RxXR-r18;

[0195] Whether to allow two XR receiving terminals to perform same-frequency reselection, i.e., the first indication information may include intraFreqReselection2RxXR-r18;

[0196] Whether the first cell allows enhanced lightweight terminal access, i.e., the first indication information may include cellBarredeRedCap-r18;

[0197] Whether the first cell allows the enhanced lightweight 1 receiver terminal to access, i.e. the first indication information may include cellBarredeRedCap1Rx-r18;

[0198] Whether the first cell allows access to the enhanced lightweight 2-receiver terminal, i.e., the first indication information may include cellBarredeRedCap2Rx-r18;

[0199] Whether the time-frequency resources of the target uplink signal overlap or not with the RACH resources of the first cell, that is, whether the time-frequency resources of the target uplink signal overlap or not with the RACH resources of the first cell, that is, whether the WUS resources and the legacy RO are separate or shared.

[0200] The time-frequency resources of the target uplink signal may or may not overlap with the RACH resources used for system information requests;

[0201] The time-frequency resources of the target uplink signal overlap or do not overlap with the additional RACH resources of the first cell, that is, it indicates whether the WUS resources and the additional RO are separate or shared.

[0202] It should be noted that: Lightweight terminal is a replaceable description of Redcap UE; 1-receive lightweight terminal is a replaceable description of 1RxReduced capability UE; 2-receive lightweight terminal is a replaceable description of 2Rx Reduced capability UE; half-duplex frequency division duplex lightweight terminal is a replaceable description of half-duplex FDD RedCap UE; air-to-ground connection is a replaceable description of ATG or Air-to-ground; energy-saving cell discontinuous transmission and reception is a replaceable description of nes-CellDTX-DRX; nes-CellDTX-DRX feature is a replaceable description of nes-CellDTX-DRX feature; enhanced lightweight UE is a replaceable description of eRedcap UE; VSAT stands for Very Small Aperture Terminal; XR stands for Extended Reality.

[0203] In some embodiments of this application, the UE may send the aforementioned target uplink signal to the network-side device.

[0204] In some embodiments of this application, the network-side device described above may be a base station or a Transmit / Receive Point (TRP).

[0205] The uplink signal transmission method provided in this application embodiment involves a UE transmitting a target uplink signal based on its UE type and first configuration information. This first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE type. The target uplink signal is used to request downlink signals or channels from a target cell. Through this method, the UE can pre-determine whether a target cell supports its UE type based on the first configuration information and its own UE type. This allows the UE to transmit the target uplink signal only when the target cell supports its UE type, avoiding the increased number of attempts and latency during cell reselection caused by the UE transmitting the target uplink signal to a cell that does not support its UE type, thereby improving communication performance. It also avoids the base station transmitting unnecessary downlink signals / channels, saving power for the base station.

[0206] In some embodiments of this application, the first configuration information described above is used to indicate UE characteristics; exemplarily, step 201 described above can be implemented by step 201a.

[0207] Step 201a: If the WUS transmission conditions are met, the UE transmits the target uplink signal based on the first configuration information.

[0208] The aforementioned WUS transmission conditions include the UE's UE characteristics matching the UE characteristics associated with the first configuration information.

[0209] For example, the UE can determine the UE features supported by the target cell, and when the target cell supports its own UE features, send a target uplink signal associated with those UE features to request the target cell for downlink signals or channel adjustments. This avoids the UE waking up a base station that does not support those UE features.

[0210] In some embodiments of this application, the uplink signal transmission method provided in this application may further include the following step 202:

[0211] Step 202: The UE listens to the target uplink signal feedback scrambled by the Radio Network Temporary Identifier (RNTI) calculated by the first formula, or listens to the Physical Downlink Control Channel (PDCCH) corresponding to the target uplink signal feedback scrambled by the RNTI.

[0212] The first formula mentioned above is a formula for the newly defined Radio Access Network Temporary Identifier (RA-RNTI), and the first formula is related to the identifier of the first cell associated with the first configuration information.

[0213] In some embodiments of this application, the first formula described above includes at least a first parameter, which is the identifier of the first cell associated with the first configuration information.

[0214] For example, the first cell may include a single cell, and the first parameter may include the identifier of that single cell; or the first cell may include multiple cells, and the first parameter may include the identifiers of those multiple cells.

[0215] This application provides a new RA-RNTI formula (i.e., the first formula), which is related to the cell identifier (i.e., Cell ID). The UE can use the RAR scrambled by the new RA-RNTI to confirm whether the base station (or cell) responding to WUS is the target base station (or target cell) that it wants to wake up.

[0216] In some examples, the new RA-RNTI formula is as follows:

[0217] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×NES_cell_id

[0218] Wherein, s_id represents the index of the first OFDM symbol, specifically, the index of the first OFDM symbol in a PRACH Occasion, and its value can be 0 to 13; t_id represents the index of the first time slot of the PRACH Occasion, specifically, the index of the first time slot of the PRACH Occasion in a system frame, and its value can be 0 to 79; f_id represents the index of the PRACH Occasion in the frequency domain, with the same meaning as in LTE, and its value can be 0 to 8; ul_carrier_id represents the uplink carrier used by the PRACH, with a value of 0 representing a NUL carrier and a value of 1 representing a SUL carrier; NES_cell_id represents the identifier of the NES cell associated with this WUS configuration, and its value can be 1 to L, where L represents the maximum number of NES cells that can be associated.

[0219] For example, after the UE sends a WUS request, the UE can listen to the RAR scrambled by the RNTI calculated by the new RA-RNTI formula, and / or listen to the PDCCH corresponding to the RAR scrambled by the RNTI, based on the new RA-RNTI formula.

[0220] In this embodiment of the application, when the WUS configuration (i.e. the first configuration information) is associated with multiple NES cells (i.e. the first cell), the UE can decode the RAR or the PDCCH corresponding to the RAR based on the new RA-RNTI scrambling formula, thereby confirming whether the responding NES cell is the target NES cell (i.e. the target cell).

[0221] In some embodiments of this application, the uplink signal transmission method provided in this application may further include steps 203 and 204:

[0222] Step 203: When the UE detects the target uplink signal feedback, the UE determines whether the cell responding to the target uplink signal is the target cell based on the target uplink signal feedback.

[0223] Step 204: If the cell is not the target cell, the UE re-determines the conditions for sending the target uplink signal, or sends the target uplink signal again.

[0224] For example, taking the target uplink signal feedback as WUS feedback, after the UE sends the Preamble, it listens for WUS feedback (i.e., RAR) in commonSS and determines whether the cell responding to the WUS request is the target cell based on the WUS feedback.

[0225] In some examples, WUS resources do not distinguish between associated NES cells. The NES cell responding to the UE's WUS request sends a RAR to the UE, and the RAR carries the responding NES cell ID. The UE can determine whether the responding NES cell is the target NES cell based on the RAR. If not, the UE re-evaluates the conditions for sending WUS, or directly sends WUS again. For example, the UE can determine that the cell responding to the WUS request is the target cell when the NES cell ID carried in the RAR is the NES cell ID of the target cell.

[0226] In some examples, WUS resources do not distinguish between associated NES cells. Multiple NES cells send RARs to the UE, but only one NES cell's RAR contains both the WUS preamble ID and the NES cell ID. The RARs of the other NES cells return NACKs (i.e., no response to the UE's WUS request). The UE determines whether the responding NES cell is the target NES cell based on the RAR. If not, it re-evaluates the conditions for sending WUS, or directly resends the WUS request (i.e., the target uplink signal). For example, the UE can determine that the responding NES cell is the target cell when the NES cell ID carried in the RAR is the NES cell ID of the target cell and the WUS preamble ID carried in the RAR is the preamble ID of the WUS request.

[0227] It should be noted that steps 203 and 204 can be executed after step 201 or after step 202.

[0228] In some embodiments of this application, the uplink signal transmission method provided in this application may further include the following step 205:

[0229] Step 205: If the UE detects the target uplink signal feedback and the target uplink signal feedback carries the preamble identifier of the target uplink signal, then the UE confirms that the target uplink signal request was successful.

[0230] For example, if the UE successfully listens to the target uplink signal feedback, and the target uplink signal feedback carries the preamble identifier of the target uplink signal, then the UE confirms that the target uplink signal request was successful.

[0231] In some examples, WUS resources (e.g., different preambles) distinguish different associated NES cells. The NES cell listening to the corresponding preamble sends WUS feedback to the UE, and the WUS feedback contains the WUS preamble ID. The UE can confirm whether the SIB1 request was successful based on whether it received the RAR; or, if the UE does not receive the RAR or the preamble ID carried in the RAR is not the WUS preamble ID, the UE considers the SIB1 request to have failed, re-evaluates the conditions for sending WUS, or directly resends WUS.

[0232] In some embodiments of this application, the first configuration information described above is used to indicate a target time period; exemplarily, the uplink signal transmission method described above may further include the following step 206:

[0233] Step 206: If the UE does not receive the target uplink signal feedback within the target time period, the UE re-evaluates the conditions for sending the target uplink signal or sends the target uplink signal again.

[0234] For example, if the UE does not receive a WUS response within the target time period after sending a WUS request, it will re-evaluate the conditions for sending the WUS request or send the WUS request again.

[0235] In some embodiments of this application, the aforementioned target uplink signal feedback indicates at least one of the following:

[0236] Do not respond to the target's uplink signal request;

[0237] Responding to the target's uplink signal request;

[0238] The identifier of the cell that responded to the target uplink signal request;

[0239] UE characteristics associated with the target uplink signal feedback;

[0240] Whether the first cell associated with the first configuration information allows UEs with specific characteristics to access;

[0241] Whether lightweight terminals are allowed to perform same-frequency reselection;

[0242] Does the first cell associated with the first configuration information allow access from a lightweight terminal?

[0243] Does the first cell associated with the first configuration information allow access from two lightweight terminals?

[0244] Does the first cell associated with the first configuration information allow access for lightweight terminals that support half-duplex frequency division duplex?

[0245] Whether the first cell associated with the first configuration information allows UE access that supports specific features, wherein the specific features include at least one of Small Data Transmission (SDT) and Multicast Service (MBS);

[0246] Does the first cell associated with the first configuration information allow air-to-ground connections?

[0247] Does the first cell associated with the first configuration information allow UEs supporting the nes-CellDTX-DRX feature to access?

[0248] Does the first cell associated with the first configuration information allow enhanced lightweight UEs to perform same-frequency reselection?

[0249] Does the first cell associated with the first configuration information allow access for fixed very small aperture satellite communication (VSAT) terminals?

[0250] Whether the first cell associated with the first configuration information allows mobile VSAT terminals to access;

[0251] Does the first cell associated with the first configuration information allow access for two XR terminals?

[0252] Should two Extended Reality (XR) terminals be allowed to reselect on the same frequency?

[0253] Whether the first cell associated with the first configuration information allows enhanced lightweight terminals to access;

[0254] Whether the first cell associated with the first configuration information allows the enhanced lightweight receiver terminal to access;

[0255] Does the first cell associated with the first configuration information allow enhanced lightweight 2D receiver terminals to access?

[0256] In this embodiment, the target uplink signal feedback can instruct the network-side device to respond to or not respond to the UE's WUS request, which can reduce unnecessary signal transmission and processing, thereby improving the efficiency of the entire communication system; the target uplink signal feedback can indicate the cell identifier that responds to the target uplink signal request, so that the UE can confirm whether the response comes from the target cell that the UE requested to wake up; the target uplink signal feedback can indicate whether the first cell allows access for a specific type of UE, so that the UE can confirm whether the first cell allows access for its own type of UE; the target uplink signal feedback can indicate whether the first cell allows Redcap UE intra-frequency reselection, 1Rx Redcap UE access, etc., so that the UE can confirm the system's support for Redcap devices. If not supported, the UE can re-determine the cell reselection.

[0257] In some embodiments of this application, the uplink signal transmission method provided in this application may further include the following step 207:

[0258] Step 207: The UE determines the time reference cell for sending the target uplink signal.

[0259] In some embodiments of this application, the time reference cell includes at least one of the following:

[0260] The cell configured or indicated by the network-side equipment;

[0261] The cell in which the UE receives the first configuration message;

[0262] Target residential area;

[0263] Among the first cells associated with the first configuration information, the cells that meet the signal conditions;

[0264] Among them, the signal conditions include at least one of the following: the reference signal received power RSRP is at its maximum, and the signal-to-interference-plus-noise ratio (SINR) is at its maximum.

[0265] It should be noted that the time reference cell can be replaced by the timing reference cell.

[0266] In some embodiments of this application, the time difference between multiple first cells associated with the first configuration information is less than a first threshold, which is determined based on the protection period (GP).

[0267] The subcarrier spacing (SCS) of the GP is determined based on at least one of the following:

[0268] The SCS of the UE's serving cell;

[0269] The timing of the UE transmitting the target uplink signal is referenced to the SCS of the cell.

[0270] The UE obtains the SCS of the first configured cell;

[0271] The largest SCS in the first cell associated with the first configuration information;

[0272] The smallest SCS in the first cell associated with the first configuration information.

[0273] In some embodiments of this application, the uplink signal transmission method provided in this application may further include the following step 208:

[0274] Step 208: The UE determines whether the time-frequency resources for transmitting the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information.

[0275] The first RACH resource includes at least one of the following: RACH resource of the first cell for system information request, additional RACH resource of the first cell, and RACH resource of the first cell for random access.

[0276] In some embodiments of this application, the time-frequency resources for transmitting the target uplink signal may or may not overlap with the first RACH resources of the first cell, determined based on at least one of the following:

[0277] This is explicitly indicated by the first configuration information;

[0278] Different information domains (IEs) are used to configure overlapping random access timing and non-overlapping random access timing respectively.

[0279] Implicit indication of network-side devices.

[0280] In some embodiments of this application, step 208 described above can be implemented by step 208a.

[0281] Step 208a: The UE determines, based on the first configuration information, whether the time-frequency resources for transmitting the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information.

[0282] In some embodiments of this application, the first configuration information mentioned above includes at least one of the following:

[0283] The starting preamble identifier corresponding to the first cell;

[0284] The preamble root sequence corresponding to the first cell;

[0285] The number of preambles corresponding to the first cell;

[0286] The frequency domain resource start timing identifier corresponding to the target uplink signal;

[0287] The number of frequency domain resource opportunities corresponding to the target uplink signal;

[0288] PRACH configuration index;

[0289] UE features.

[0290] Figure 3 This is a flowchart illustrating the resource configuration method provided in an embodiment of this application, as shown below. Figure 3 As shown, the resource configuration method may include the following steps 301 and 302:

[0291] Step 301: The network-side device sends the first configuration information to the user equipment (UE).

[0292] Step 302: The UE receives the first configuration information from the network-side device.

[0293] The first configuration information corresponds to at least one UE type, or the first configuration information indicates at least one target uplink signal resource that corresponds to at least one UE feature.

[0294] In some embodiments of this application, the first configuration information is used to indicate at least one of the following:

[0295] The identifier or identifier list of the first cell associated with the first configuration information;

[0296] The first configuration information is associated with the first cell corresponding to ssb-positionInBurst;

[0297] The UE characteristics associated with the first configuration information;

[0298] Target uplink signal feedback monitoring configuration;

[0299] Target configuration;

[0300] The maximum number of SSBs allowed for SSB mapping;

[0301] The target time period is used to determine the time during which the UE listens for the uplink signal feedback from the target.

[0302] The first cell is the cell that allows UEs to request adjustments to downlink signals or channels.

[0303] In some embodiments of this application, the first configuration information configures only a single ssb-positionInBurst, and a single ssb-positionInBurst is associated with multiple first cells.

[0304] In some embodiments of this application, the first configuration information configures multiple ssb-positionInBursts, and the multiple ssb-positionInBursts are associated with multiple first cells respectively.

[0305] In some embodiments of this application, the target uplink signal feedback monitoring configuration includes at least one of the following:

[0306] Target uplink signal feedback search space configuration;

[0307] Target uplink signal feedback control resource set configuration.

[0308] In some embodiments of this application, the target configuration includes at least one set of configurations, each set of configurations corresponding to at least one first cell, or each set of configurations corresponding to at least one UE feature, or each set of configurations corresponding to at least one UE feature supported by at least one first cell.

[0309] In some embodiments of this application, the target configuration includes at least one of the following:

[0310] UE characteristics associated with the target configuration;

[0311] The device that supports specific technical features requests the time-frequency resource configuration of the target downlink signal or the target uplink signal for channel adjustment; for example, when the first cell supports the redcap feature, the time-frequency resources for redcap UE to send UL-WUS can be configured in the WUS configuration, such as si-RequestConfigRedCap, and this parameter is limited to use by redcap UE.

[0312] SSB mapping related configurations;

[0313] Target uplink signal preamble sequence resource configuration;

[0314] Target uplink signal time-frequency resource allocation;

[0315] The SIB1 request period, sib1-RequestPeriod, is measured in terms of the association period.

[0316] The association period identifier ra-AssociationPeriodIndex is used to indicate the available association period among multiple association periods;

[0317] The RO mask identifier ra-ssb-OccasionMaskIndex is used to indicate the available ROs among multiple ROs associated with a single SSB;

[0318] UEs that support specific technical features can be used to request UL WUS resource configuration for SIB1, such as a separately configured Redcap UE for requesting WUS resource configuration for SIB1, i.e., SIB1-RequestResourceRedCap.

[0319] The first indication information is used to indicate whether the first cell allows lightweight terminals to perform same-frequency reselection;

[0320] The second indication information is used to indicate whether the first cell allows access for a lightweight terminal with 1 receiver;

[0321] The third instruction information is used to indicate whether the first cell allows access for two lightweight terminals;

[0322] The fourth indication information is used to indicate whether the first cell allows access for lightweight terminals that support half-duplex frequency division duplex.

[0323] The fifth indication information is used to indicate whether the first cell allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS).

[0324] The sixth instruction information is used to indicate whether the first cell allows air-to-ground connections;

[0325] The seventh indication information is used to indicate whether the first cell allows UEs that support the nes-CellDTX-DRX feature to access;

[0326] The eighth indication information is used to indicate whether enhanced lightweight UEs are allowed to perform same-frequency reselection;

[0327] The ninth instruction information is used to indicate whether the first cell allows access for fixed Very Small Aperture Satellite Communication (VSAT) terminals;

[0328] The tenth instruction information is used to indicate whether the first cell allows the mobile VSAT terminal to access;

[0329] The eleventh instruction information is used to indicate whether the first cell allows access for two Extended Reality (XR) terminals.

[0330] The twelfth instruction information is used to indicate whether two XR receiving terminals are allowed to perform same-frequency reselection;

[0331] The thirteenth instruction message is used to indicate whether the first cell allows the enhanced lightweight terminal to access;

[0332] The fourteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight receiver terminal to access;

[0333] The fifteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight 2-receiver terminal to access;

[0334] The sixteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the RACH resources of the first cell;

[0335] The seventeenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the RACH resources of the first cell used for system information requests;

[0336] The eighteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the additional RACH resources of the first cell.

[0337] In some embodiments of this application, the SSB mapping-related configuration includes at least one of the following:

[0338] The number of SSBs associated with each RACH timing RO;

[0339] The number of preambles associated with each SSB.

[0340] In some embodiments of this application, the target uplink signal preamble sequence resource configuration includes at least one of the following:

[0341] Preamble root sequence;

[0342] The number of preambles associated with each SSB;

[0343] Preamble start index;

[0344] Number of preambles in the target uplink signal;

[0345] Number of preambles used for random access.

[0346] In some embodiments of this application, the target uplink signal time-frequency resource configuration includes at least one of the following:

[0347] Frequency domain timings;

[0348] Frequency domain start timing identifier;

[0349] Physical Random Access Channel (PRACH) Configuration Index;

[0350] Permissible associated period identifiers;

[0351] Allowed RO mask identifiers.

[0352] The resource configuration method provided in this application embodiment enables the network-side device to configure at least one UE feature by corresponding to a first configuration, thereby providing a resource allocation scheme most suitable for the characteristics of the UE with at least one UE feature, and improving the speed and efficiency of data transmission.

[0353] In some embodiments of this application, the resource configuration method provided in this application may further include steps 303 and 304:

[0354] Step 303: The network-side device receives a target uplink signal from the UE. The target uplink signal is used to request downlink signals or channel adjustments from the target cell.

[0355] Step 304: The network-side device sends the target uplink signal feedback to the UE or sends the physical downlink control channel (PDCCH) corresponding to the target uplink signal feedback to the UE.

[0356] The target uplink signal feedback carries the preamble identifier of the target uplink signal.

[0357] It should be noted that steps 303 and 304 can be executed before step 301, after step 301, or simultaneously with step 301. This application embodiment does not limit this.

[0358] In some embodiments of this application, the process of the network-side device sending the target uplink signal feedback to the UE in step 304 above may include the following step 304a:

[0359] Step 304a: The network-side device sends a target uplink signal feedback to the UE, scrambled with the Radio Network Temporary Identifier RNTI calculated by the first formula.

[0360] In some embodiments of this application, the process of sending the physical downlink control channel (PDCCH) corresponding to the target uplink signal feedback to the UE in step 304 above may include the following step 304b:

[0361] Step 304b: The network-side device sends the target uplink signal scrambled by RNTI to the UE and feeds back the corresponding PDCCH;

[0362] The first formula is the formula for the newly defined Random Access Radio Network Temporary Identifier RA-RNTI, and the first formula is related to the identifier of the first cell associated with the first configuration information.

[0363] In some embodiments of this application, the first formula includes at least a first parameter, which is the identifier of the first cell associated with the first configuration information.

[0364] In some embodiments of this application, the target uplink signal feedback indicates at least one of the following:

[0365] Do not respond to the target's uplink signal request;

[0366] Responding to the target's uplink signal request;

[0367] The identifier of the cell that responded to the target uplink signal request;

[0368] UE characteristics associated with the target uplink signal feedback;

[0369] Whether the first cell associated with the first configuration information allows UEs with specific characteristics to access;

[0370] Does the first cell associated with the first configuration information allow lightweight terminals to reselect on the same frequency?

[0371] Does the first cell associated with the first configuration information allow access from a lightweight terminal?

[0372] Does the first cell associated with the first configuration information allow access from two lightweight terminals?

[0373] Does the first cell associated with the first configuration information allow access for lightweight terminals that support half-duplex frequency division duplex?

[0374] Whether the first cell associated with the first configuration information allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS);

[0375] Does the first cell associated with the first configuration information allow air-to-ground connections?

[0376] Does the first cell associated with the first configuration information allow UEs supporting the nes-CellDTX-DRX feature to access?

[0377] Does the first cell associated with the first configuration information allow enhanced lightweight UEs to perform same-frequency reselection?

[0378] Does the first cell associated with the first configuration information allow access for fixed very small aperture satellite communication (VSAT) terminals?

[0379] Whether the first cell associated with the first configuration information allows mobile VSAT terminals to access;

[0380] Does the first cell associated with the first configuration information allow access for two XR terminals?

[0381] Should two Extended Reality (XR) terminals be allowed to reselect on the same frequency?

[0382] Whether the first cell associated with the first configuration information allows enhanced lightweight terminals to access;

[0383] Whether the first cell associated with the first configuration information allows the enhanced lightweight receiver terminal to access;

[0384] Does the first cell associated with the first configuration information allow enhanced lightweight 2D receiver terminals to access?

[0385] In some embodiments of this application, the time difference between multiple first cells associated with the first configuration information is less than a first threshold, and the first threshold is determined based on the protection period (GP).

[0386] The subcarrier spacing (SCS) of the GP is determined based on at least one of the following:

[0387] The SCS of the UE's serving cell;

[0388] The timing of the UE transmitting the target uplink signal is referenced to the SCS of the cell.

[0389] The UE obtains the SCS of the first configured cell;

[0390] The largest SCS in the first cell associated with the first configuration information;

[0391] The smallest SCS in the first cell associated with the first configuration information.

[0392] In some embodiments of this application, the first configuration information includes at least one of the following:

[0393] The starting preamble identifier corresponding to the first cell;

[0394] The preamble root sequence corresponding to the first cell;

[0395] The number of preambles corresponding to the first cell;

[0396] The frequency domain resource start timing identifier corresponding to the target uplink signal;

[0397] The number of frequency domain resource opportunities corresponding to the target uplink signal;

[0398] PRACH configuration index;

[0399] UE features.

[0400] It should be noted that the explanation of this embodiment can be found in the relevant description of the UE-side method embodiment above, and will not be repeated here.

[0401] The methods provided in this application will be explained and illustrated below through specific embodiments.

[0402] Example 1: When one WUS configuration is associated with multiple NES cells, and the RO configuration and preamble (WUS) listened to by the multiple NES cells are the same, the process by which the UE confirms that the base station responding to the WUS is the target base station is as follows.

[0403] For example, the new RA-RNTI formula is as follows:

[0404] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2×NES_cell_id

[0405] Wherein, s_id represents the index of the first OFDM symbol (in a PRACH Occasion), with a value of 0 to 13; t_id represents the index of the first slot of the PRACH Occasion (in a system frame), with a value of 0 to 79; f_id represents the index of the PRACH Occasion in the frequency domain, with the same meaning as in LTE, and a value of 0 to 8; ul_carrier_id represents the uplink carrier used by the PRACH, with a value of 0 representing a NUL carrier and a value of 1 representing a SUL carrier; NES_cell_id represents the identifier of the NES cell associated with this WUS configuration, with a value of 1 to the maximum number of NES cells allowed to be associated.

[0406] In some embodiments, the maximum number of NES cells that can be associated per WUS configuration is 2, 4, or 8.

[0407] The specific implementation steps are as follows:

[0408] Step 1: The UE receives the WUS configuration, which includes at least one of the following:

[0409] The associated NES cell ID list (and the actual number of SSBs sent by multiple NES cells is consistent).

[0410] Ssb-PositioninBurst

[0411] msg1-FDM

[0412] msg1-FrequencyStart

[0413] ssb-perRACH-Occasion

[0414] preamble per SSB

[0415] preamble index

[0416] Assume this WUS configuration is associated with three NES cell IDs = 1, 2, and 3.

[0417] Step 2: If the WUS transmission conditions are met, the UE transmits WUS on the WUS resources configured in the WUS configuration and requests SIB1 of NES cell1;

[0418] Step 3: The UE listens for WUS feedback (RAR) based on the new RA-RNTI formula and NES cell id=1.

[0419] Step 4: If no WUS feedback is received within a certain period of time, the UE re-evaluates the conditions for sending WUS.

[0420] It should be noted that the main idea of ​​this embodiment is to modify the RA-RNTI formula. The new RA-RNTI formula is related to the cell ID. The UE confirms whether the base station responding to WUS is the target base station it wants to wake up based on the RAR scrambled by the new RA-RNTI.

[0421] In the embodiments of this application, when the preamble and RO resources corresponding to multiple NES cells are the same, the UE can confirm whether the base station to be woken up is the base station it wants to wake up based on the new RA-RNTI scrambled RAR, thereby improving the UE's freedom of choice.

[0422] Example 2: In this example, when one WUS configuration is associated with multiple NES cells, the SSBs of the multiple NES cells are mapped to the WUS occasion.

[0423] In some examples, a WUS configuration (with only one RACH occasion, RO resource configuration, or simply a WUS occasion, WO) applies to multiple NES cells, i.e., it is associated with a single NES cell list; the mapping relationship between SSBs and ROs of the multiple NES cells is configured by the WUS configuration, including at least one of the following:

[0424] Option 1: Multiple NES cells actually transmit the same number of SSBs.

[0425] In some examples, the WUS configuration includes the associated NES cell ID, as well as WUS resource configurations (including RO time-frequency resources, preamble sequence resources, SSB-RO mappings, etc.), including:

[0426] ① The actual number of SSBs sent (i.e., the number of bits with 1 in SSB-PositioninBurst). Where:

[0427] For example, only one ssb-positionInBurst can be configured, meaning that the ssb-positionInBurst of multiple NES cells is consistent;

[0428] As another example, ssb-positionInBurst can also be configured per cell, but the number of bits with 1 in ssb-positionInBurst is the same for each NES cell.

[0429] ②SSB index.

[0430] In some examples, the SSB index includes either the actual SSB index sent or all candidate SSB indices.

[0431] ③ The mapping relationship between SSB and RACH resources (included by WUS configuration or carried over from cell A configuration).

[0432] For example, the number of SSBs associated with a single RO for each NES cell associated with a WUS configuration is defined as SSB per RO. For example, SSB per RO can be configured with only one value, meaning that the SSB per RO is consistent across multiple NES cells, or it can be configured per cell.

[0433] In some examples, each WUS configuration specifies the start number and quantity of preambles associated with each SSB of the NES cell, or only an identifier (i.e., by default, each SSB corresponds to one preamble). For example, only one preamble per SSB can be configured, meaning that the preamble per SSB is consistent across multiple NES cells.

[0434] In some examples, the starting preamble index associated with the NES cell associated with each WUS configuration.

[0435] In some examples, the number of preambles associated with each NES cell associated with each WUS configuration.

[0436] Figure 4A This diagram illustrates the correspondence between multiple NES cells and SSB indices, as well as the mapping between the actual transmitted SSB index and SSB. (Example) Figure 4A As shown in (a), each NES cell corresponds to SSB index 0-SSB index 7. The SSB indexes of the NES cells mapped on each RO are the same, and the SSB configuration of each NES cell is the same as that of the RACH resource. Taking SSB per RO = 1 as an example, ... Figure 4A As shown in (b), each RO maps to multiple SSBs of NES cells. RO1 maps to SSB1 of NES cells 1 / 2 / 3, RO2 maps to SSB3 of NES cells 1 / 2 / 3, and so on.

[0437] It should be noted that SSB index0 can be abbreviated as SSB 0, and similarly, SSB index7 can be abbreviated as SSB7.

[0438] It should be noted that, Figure 4A The numbers “1” to “7” refer to SSB index 1 to SSB index 7, and similar descriptions in other attached figures have the same meaning.

[0439] Figure 4B Another schematic diagram illustrating the correspondence between SSB indices of multiple NES cells and the mapping relationship between the actual transmitted SSB index and SSB, as shown below. Figure 4B As shown in (a), the SSB indexes of the NES cells mapped on each RO are different, but the actual number of SSBs transmitted is the same, and the SSB configuration of each NES cell is the same as that of the RACH resource, that is, the SSB per RO is the same. Taking SSB per RO = 1 as an example, SSB per RO can be understood as the number of SSBs mapped by each cell on a single RO (WUS resource), that is, the number of SSBs mapped by each cell on a single RO is 1. That is, RO1 maps SSB1 / 1 / 0 of NES cells 1 / 2 / 3 respectively, and RO2 maps SSB3 / 2 / 2 of NES cells 1 / 2 / 3 respectively. Specifically, as shown in (a), the SSB indexes of the NES cells mapped on each RO are different, but the actual number of SSBs transmitted is the same, and the SSB configuration of each NES cell is the same as that of the RACH resource, that is, the SSB per RO is the same. Figure 4BAs shown in (b), each RO maps to multiple SSBs of NES cells; RO1 maps to SSB1 of NES cell 1, SSB1 of NES cell 2, and SSB0 of NES cell 3; RO2 maps to SSB3 of NES cell 1, SSB2 of NES cell 2, and SSB2 of NES cell 3; RO3 maps to SSB5 of NES cell 1, SSB3 of NES cell 2, and SSB4 of NES cell 3; RO4 maps to SSB7 of NES cell 1, SSB4 of NES cell 2, and SSB6 of NES cell 3.

[0440] In some examples, the WUS configuration only sets one SSB per RO and preamble per SSB. In this case, multiple NES cells map the same number of SSBs on a single RO, and each SSB of each cell is associated with the same number of preambles. Multiple NES cells will listen to the RACH resource and preamble. After the UE sends the preamble (WUS), multiple NES cells can negotiate with each other and send WUS feedback (RAR). The RAR may optionally contain the cell ID that responds to the WUS.

[0441] In some examples, the WUS configuration only sets up one SSB per RO (ssb-perRACH-Occasion) and preamble per SSB. At the same time, the preamble is further divided based on the NES cell ID, cell type, or UE feature / UE type supported by the cell. Multiple NES cells will listen to the RACH resource and preamble. After the UE sends the preamble (WUS), it listens for the RAR. If it does not receive the RAR, it sends the WUS again. If it receives the RAR and the RAR contains the preamble ID that sent the WUS, the UE considers the SIB1 request to be successful.

[0442] Option 2: If the actual number of SSBs sent by multiple NES cells is different, then the following Case 1 applies.

[0443] Case 1: The mapping between SSB and RO (WO) follows the mapping relationship between SSB and RO of the cell A where the UE is currently residing (SSB per RO).

[0444] Figure 4CThis is a schematic diagram illustrating the mapping relationship between WUS resources (RACH resources) and SSBs provided in this application embodiment. The mapping relationship between WUS resources (RACH resources) and SSBs is referenced to the configuration of cell A, such as... Figure 4C As shown, the mapping relationship between SSB and RO of cell A is SSB per RO = 1, that is, each RO is associated with one SSB. The mapping relationship between WUS resources and SSB is also SSB per RO = 1. However, since the number of SSBs actually sent by each NES cell is different, the number of SSBs mapped by each NES cell on WUS resources is also different.

[0445] In some examples, NES cell1, NES cell2, and NES cell3 need to listen to the same WUS time-frequency resource, which is the same time-frequency resource, but the SSBs of different NES cells are mapped on the same RO (WO).

[0446] In some examples, the WUS configuration only sets one SSB per RO and one preamble per SSB, and further divides the preamble based on the NES cell ID, cell type, or UE feature / UE type supported by the cell. After the UE sends the preamble (WUS), multiple NES cells will listen to the RACH resource and the preamble. After the UE sends the preamble (WUS), it listens to the RAR. If it does not receive the RAR, it sends the WUS again. If it receives the RAR and the RAR contains the preamble ID that sent the WUS, the UE considers the SIB1 request to be successful.

[0447] Case 2: The mapping between SSB and RO (WO) can be based on the maximum number of SSBs actually transmitted in the NES cell.

[0448] Figure 4D This is a schematic diagram illustrating the mapping of the maximum actual number of SSBs transmitted by all NES cells associated with the WUS configuration, as provided in the embodiments of this application. Figure 4D As shown, among the three associated NES cells 1 / 2 / 3, NES cell 3 actually transmits the most SSBs. WUS resources are mapped according to the number of SSBs transmitted by the NES cell with the highest actual SSB transmission count. Figure 4D Taking SSB per RO = 1 as an example, the mapping is based on the 8 SSBs of NES cell 3. For NES cell 1 and NES cell 2, the mapping is only performed at the position corresponding to the number of the SSB that is actually sent.

[0449] Case 3: WUS configuration sets the target number of SSBs (e.g., the maximum number of SSBs supported by the configuration protocol). The difference from Case 2 is that the number of SSBs mapped is configured by WUS, while the number of SSBs mapped in Case 2 is the maximum number of SSBs among all associated NES cells.

[0450] Case 4: The WUS configuration includes multiple target configurations, each of which corresponds one-to-one with a number of NES cells. Each target configuration includes at least one of the following:

[0451] Actual number of SSBs sent

[0452] Number of candidate SSBs

[0453] Mapping relationship between SSB and RO

[0454] SSB per RO

[0455] Preamble per SSB

[0456] Start Preamble Sequence Identifier

[0457] It should be noted that in this embodiment, the SSB per RO and preamble per SSB of the NES cell associated with the WUS configuration are configured independently, and the preambles of multiple NES cells are not allowed to overlap.

[0458] In some examples, the resources for transmitting WUS may completely overlap / partially overlap / completely not overlap with the legacy RACH resources of multiple NES cells, including time-frequency resources, sequence resources, etc.

[0459] Example 3: In this example, when one WUS configuration is associated with multiple NES cells, the SSBs of the multiple NES cells are not mapped to the WUS occasion.

[0460] The main idea of ​​this embodiment is that when one WUS configuration is associated with multiple NES cells, there is no mapping between the SSB and RO (WUS occasion) of the multiple NES cells.

[0461] The specific implementation steps are as follows:

[0462] Step 1: The UE receives the WUS configuration, which includes at least one of the following:

[0463] The associated NES cell ID list (and the actual number of SSBs sent by multiple NES cells is consistent).

[0464] Ssb-PositioninBurst

[0465] msg1-FDM

[0466] msg1-FrequencyStart

[0467] PRACH configuration Index

[0468] preamble start identifier

[0469] preamble quantity

[0470] It should be noted that no parameters related to SSB mapping are configured in this WUS configuration, but WUS resources and WUS preamble are configured.

[0471] Step 2: If the WUS transmission conditions are met, the UE transmits WUS on the WUS resources configured in the WUS configuration and requests SIB1 of the NES cell;

[0472] Step 3: UE listens for WUS feedback

[0473] Step 4: If no WUS feedback is received within a certain period of time, the UE re-evaluates the conditions for sending WUS.

[0474] Example 4: In this example, when one WUS configuration is associated with multiple NES cells, the network side configures different preambles or different RACH resources to distinguish different NES cells.

[0475] The main idea of ​​this embodiment is that when one WUS configuration is associated with multiple NES cells, the network side configures different preambles or different RO resources to distinguish different NES cells.

[0476] The specific implementation steps are as follows:

[0477] Step 1: The UE receives the WUS configuration, in which at least one of the following parameters is configured in multiple sets, each corresponding to a different associated NES cell:

[0478] Ssb-PositioninBurst;

[0479] msg1-FDM;

[0480] msg1-FrequencyStart;

[0481] ssb-perRACH-Occasion;

[0482] preamble per SSB;

[0483] preamble index;

[0484] PRACH configuration index;

[0485] Supported UE types / UE category / UE type;

[0486] Preamble root sequence.

[0487] Step 2: If the WUS transmission conditions are met, the UE transmits WUS based on the WUS resources configured in the WUS configuration, requesting SIB1 of the target NES cell;

[0488] Step 3: Listen for WUS feedback (RAR).

[0489] Step 4: If no WUS feedback is received within a certain period of time, the UE re-evaluates the conditions for sending WUS.

[0490] Figure 5 This is a schematic diagram of the RO corresponding to the NES cell associated with the same WUS configuration provided in the embodiments of this application, as shown below. Figure 5 As shown, the WUS location (RO) corresponding to NES Cell1, NES Cell2, NES Cell3 and NES Cell4 are different, that is, the RO corresponding to the NES cells associated with the same WUS configuration is different.

[0491] It should be noted that, Figure 5 The horizontal axis represents the time domain, and the vertical axis represents the frequency domain.

[0492] Figure 6A This is a schematic diagram illustrating the correspondence between NES cells and preambles provided in an embodiment of this application, as shown below. Figure 6A As shown, the preambles corresponding to the NES cells associated with the same WUS configuration are different (there is SSB mapping). Furthermore, the preambles corresponding to NES Cell1, NES Cell2, and NES Cell3 are different. The network-side device can configure the starting preamble identifier and the number of preambles corresponding to each associated NES cell in the WUS configuration.

[0493] It should be noted that, in Figure 6AIn this context, "Start Preamble Index" refers to the start preamble index, and "WUS preambles for SSB" refers to the WUS preambles for SSB.

[0494] Figure 6B Another schematic diagram illustrating the correspondence between NES cells and preambles provided in the embodiments of this application is shown below. Figure 6B As shown, the preambles corresponding to the NES cells associated with the same WUS configuration are different (no SSB mapping). Furthermore, the preambles corresponding to NES Cell1, NES Cell2, and NES Cell3 are different. The network-side device can configure the starting preamble identifier and the number of preambles corresponding to each associated NES cell in the WUS configuration.

[0495] It should be noted that "WUS preambles corresponding to NES cell1" refers to WUS preambles for NES cell1; and "preambles corresponding to each NES cell" refers to preambles per NES cell.

[0496] In this embodiment of the application, the UE can request the SIB1 of the base station most suitable for wake-up as needed. That is, the UE's request and the network side's response can be consistent, avoiding the situation where the UE requests NES cell A, but the response is NES cell B.

[0497] Example 5: In this example, when one WUS configuration is associated with multiple NES cells, the network side configures different preambles or different RACH resources to distinguish different NES cells that support different features.

[0498] The main idea of ​​this embodiment is that when one WUS configuration is associated with multiple NES cells, the network side configures different preambles or different RACH resources to distinguish the UE types / UE categories supported by different NES cells.

[0499] Figure 7 This is a schematic diagram of the ROs corresponding to the UE types / UE features supported by the NES cells associated with the same WUS configuration provided in the embodiments of this application, as shown in the figure. Figure 7 As shown, the ROs corresponding to the UE types / UE features supported by the same WUS configuration associated with NES cell1 to NES cell4 are different.

[0500] Figure 8AThis is a schematic diagram illustrating the preamble corresponding to the UE types / UE features supported by the NES cell associated with the same WUS configuration provided in the embodiments of this application, as shown below. Figure 8A As shown, the NES cells associated with the same WUS configuration support different preambles for UE types / UE features (due to SSB mapping). Figure 8A In WUS configuration, the starting preamble identifier and number can be configured for each feature of each associated NES cell.

[0501] It should be noted that, Figure 8A The phrase "UE feature 1 corresponding to NES cell1" refers to NES cell1 for UE feature 1.

[0502] Figure 8B Another schematic diagram of the preamble corresponding to the UE types / UE features supported by the NES cell associated with the same set of WUS configurations provided in the embodiments of this application is shown below. Figure 8B As shown, the preambles corresponding to the UE types / UE features supported by the NES cells associated with the same WUS configuration are different (no SSB mapping). Figure 8B In WUS configuration, the starting preamble identifier and number can be configured for each feature of each associated NES cell.

[0503] It should be noted that, Figure 8B The text refers to "WUS preamble index of NTN UE", which means WUS preamble for NTN UE; and "preamble of NES cell1".

[0504] For example, the network-side device can configure the preamble start identifier associated with each NES cell and the number of preambles corresponding to each supported feature, or configure the preamble start identifier associated with each NES cell and the number of supported UE features / UE types / UE categories.

[0505] Figure 8C This is another schematic diagram illustrating the preamble corresponding to the UE types / UE features supported by the NES cell associated with the same set of WUS configurations provided in the embodiments of this application, as shown below. Figure 8CAs shown, the NES cells associated with the same WUS configuration support different preambles for UE types / UE features (no SSB mapping).

[0506] It should be noted that, Figure 8C The term "preamble of NTN feature" refers to the preamble of the NTN feature.

[0507] For example, the network side can configure the preamble start identifier associated with each feature, the number of preambles corresponding to each supported feature, and the NES cell ID supporting these features, or configure the preamble start identifier associated with each NES cell and the number of supported UE features / UE types / UE categories.

[0508] Example 6: WUS configuration is per cell, and the WUS configuration indicates the applicable UE type or capability type.

[0509] The main idea of ​​this embodiment is: when WUS configuration per cell or per cell group (optionally, where cells in a cell group support at least one of the same UE feature / UE category), the WUS configuration indicates the applicable UE type or capability type.

[0510] The corresponding signaling procedure is as follows:

[0511] Step 1: The UE obtains the WUS configuration for waking up the NES cell. The WUS configuration indicates at least one of the following:

[0512] WUS Configuration ID;

[0513] Applicable UE types / list;

[0514] Including RedCap / NTN;

[0515] The UE type can be directly indicated;

[0516] Alternatively, it can indicate an index, where the mapping relationship between UE type and index can be agreed upon in advance by the protocol or configured by the network side;

[0517] Applicable UE category value; UE capability values / value list;

[0518] A list of associated cell IDs / IDs;

[0519] WUS time and frequency resource configuration;

[0520] WUS preamble sequence configuration;

[0521] Start preamble sequence number;

[0522] Number of preamble sequences;

[0523] WUS feedback listener configuration;

[0524] Step 2: Based on the WUS configuration, the UE sends a WUS request OD-SIB1 if the WUS transmission conditions are met;

[0525] Step 3: The UE receives WUS feedback.

[0526] In this embodiment, the WUS configuration directly indicates the UE features / UE capabilities / technical characteristics / device characteristics / device capabilities to which the WUS configuration applies, and the WUS configuration also includes the associated cell ID. For example, the WUS configuration directly indicates that it applies to non-redcap UEs, avoiding redcap UEs sending WUS to wake up base stations that do not support redcap UEs, which saves power for both the UE and the base station.

[0527] Example 7: The WUS configuration is shared by multiple cells (common WUS), and different preambles / ROs are configured in the WUS configuration based on different UE types.

[0528] The main idea of ​​this embodiment is: if the WUS configuration is applicable to multiple NES cells, and the multiple cells support different features, some NES cells support feature A, and some NES cells do not support feature A, the network side needs to configure multiple sets of preamble configurations associated with different features to ensure that the base station responding to WUS supports the corresponding feature, and avoid multiple base stations that do not support the corresponding feature being woken up.

[0529] The corresponding signaling procedure is as follows:

[0530] Step 1: The UE obtains the WUS configuration for waking up the NES cell. The WUS configuration indicates at least one of the following:

[0531] WUS Configuration ID;

[0532] Applicable UE types / list;

[0533] Including RedCap / NTN;

[0534] Applicable UE category value; UE capability values / value list;

[0535] A list of associated cell IDs / IDs;

[0536] Multiple WUS resource configurations.

[0537] Each WUS resource configuration corresponds one-to-one with a different UE feature / UE type, and the WUS resource configuration includes at least one of the following:

[0538] Time and frequency resource allocation;

[0539] Preamble sequence configuration;

[0540] Start preamble sequence number;

[0541] Number of preamble sequences;

[0542] Preamble root sequence;

[0543] WUS feedback listener configuration.

[0544] Step 2: Based on the WUS configuration, the UE sends a WUS request OD-SIB1 if the WUS transmission conditions are met;

[0545] Step 3: The UE receives WUS feedback.

[0546] The core of this embodiment is that a set of WUS configurations needs to indicate the UE type or capability type of the corresponding application. Cell A can be configured with one set of WUS configurations (this set of WUS configurations is only allowed to be used by non-redcap UEs) or multiple sets of WUS configurations (one set corresponds to the WUS resources allowed to be used by redcap UEs, and another set corresponds to the WUS resources allowed to be used by non-redcap UEs).

[0547] In some examples, each cell has two common WUS preambles: A for RedCap UEs and B for non-RedCap UEs. If an NES cell does not support RedCap UEs, it will not monitor A, or it will reject the UE's WUS request via RAR.

[0548] In some examples, the network side will configure a common WUS resource (multiple NES cells will listen to the common WUS resource). The multiple NES cells associated with the common WUS resource support different UE features, and different time-frequency RO resources or different preamble sequence resources in the common WUS resource correspond to different NES cells.

[0549] It should be noted that "common" in this application can be general, public, or shared. Common WUS resource, or common WUS resource, refers to general WUS resource or shared WUS resource.

[0550] like Figure 9 As shown, different RO resources are associated with base stations / cells that support different UE features. common WUSresource1 corresponds to the common WUS resources that the base station supporting UE feature1 needs to listen to; common WUSresource2 (preamble2 / RO2) corresponds to the common WUS resources that the base station supporting UE feature2 needs to listen to; common resource1 and common resource2 can be configured by the same WUS configuration or by different WUS configurations.

[0551] Or such as Figure 10 As shown, different preamble resources are associated with base stations / cells that support different UE features. Preamble resource 1 corresponds to the preamble resources that the base station supporting UE feature 1 needs to listen to; preamble resource 2 corresponds to the common WUS resources that the base station supporting UE feature 2 needs to listen to.

[0552] It should be noted that, Figure 10 The term "Slice 1 preambles (4-step random access)" refers to "Slice 1 preambles (4-step RA)".

[0553] "Switching 2 preambles (4-step RA for RedCap), also known as "Slice 2preambles (4-step RA for RedCap)";

[0554] "Slice 3 preambles (4-step SDT-RA)" is also known as "Slice 3 preambles (4-step SDT-RA)".

[0555] "SDT preambles for SSB1 (4-step RA)" is also known as "SDT-preambles for SSB1 (4-step RA)".

[0556] "CovEnh (4-step random access only)" is equivalent to "CovEnh (4-step RA only)".

[0557] "CF preamble" is the same as "CF preamble".

[0558] "CB preambles for SSB1 (4-step random access)" is also known as "CB-preambles for SSB1 (4-step RA)".

[0559] "CB preambles for SSB1 (2-step random access)" is also known as "CB-preambles for SSB1 (2-step RA)".

[0560] "NES preamble (for Redcap UE)" is equivalent to "NES preamble (for Redcap UE)".

[0561] "NES preamble (for non-Redcap UE)" is also known as "NES preamble (for non-Redcap UE)".

[0562] "Reserved for Msg1-based SI request"

[0563] "Group A" is equivalent to "Group A", and similarly, "Group B" is equivalent to "Group B".

[0564] The number of random access preambles for group A is "numberOfRA-PreamblesGroupA".

[0565] "CB preamble for each SSB" is also known as "CB-PreamblesPerSSB".

[0566] The total number of random access preambles is also known as "totalNumberOfRA-Preambles".

[0567] In some examples, such as Figure 11 As shown, the WUS configuration includes two common WUS preambles: one for redcap UEs (preamble1) and one for non-redcap UEs (preamble2). NES cell1 and NES cell2 are base stations supporting redcap UEs; they listen to preamble1 and provide feedback to WUS. NES cell3 and NES cell4 are base stations not supporting redcap UEs; they do not respond to UL-WUS messages sent by redcap UEs. Specifically, in... Figure 11In the process, the redcap UE sends a preamble 1 request to wake up the NES cell. Both NES cell1 and NES cell2 listen to preamble 1. After negotiation through the xn interface, NES cell1 responds to the request of the redcap UE and sends a RAR. The RAR can optionally carry the NES cell ID corresponding to the WUS, i.e., NES cell ID=1. The UE receives the RAR in the common SS and receives OD-SIB1 in NES cell1.

[0568] exist Figure 11 In this configuration, the NES cell determines whether to respond to UL-WUS based on the preamble resources or RO resources sent by the UE to WUS. Thus, for both the base station and the UE, there's no need to send and receive SIB1 to confirm whether the NES cell supports the UE's corresponding feature. The UE can determine in advance whether the NES cell associated with the WUS configuration supports the UE feature based on the indication in the WUS configuration, which is equivalent to an early indication. This saves power for both the UE and the base station, avoiding the UE only knowing whether the NES cell supports the UE feature after receiving SIB1.

[0569] Example 8: After the UE sends the common WUS, the behavior of the base station and the UE is as follows:

[0570] Case 1: WUS resources do not distinguish between different associated NES cells.

[0571] In some examples, after the UE sends the preamble, it listens for WUS feedback (RAR) on the common SS.

[0572] For example, only the responding NES cell will send back a RAR, and the RAR carries the responding NES cell ID. The UE determines whether the responding NES cell is the target NES cell based on the RAR. If not, it re-evaluates the conditions for sending WUS, or directly sends WUS again.

[0573] For example, multiple NES cells respond to RAR, and only one NES cell's RAR contains WUSpreamble ID and NES cell ID, while the RARs of the other NES cells return NACK (i.e., do not respond to the UE's WUS request). The UE determines whether the responding NES cell is the target NES cell based on the RAR. If not, it re-evaluates the conditions for sending WUS, or directly sends WUS again.

[0574] Case 2: WUS resources (such as different preambles) distinguish the associated different NES cells.

[0575] In some examples, only the NES cell listening to the corresponding preamble can provide feedback to WUS, and the WUS feedback includes the WUS preamble ID. The UE confirms whether the SIB1 request was successful based on whether it received a RAR. If it did not receive a RAR or the preamble ID carried in the RAR was not the WUS preamble ID, the UE considers the SIB1 request to have failed, and then re-evaluates the conditions for sending WUS, or directly resends WUS.

[0576] Example 9: RAR instructions, such as preamble index / WUS configuration index / UE type, inform the corresponding type of UE whether the network should respond to or not respond to the WUS signal request.

[0577] The main idea of ​​this embodiment is that when multiple WUS configurations correspond one-to-one with different UE features / UE types, the network can use the preamble index / WUS configuration index / UE type indicated by RAR to tell the corresponding type of UE whether the network should respond to or not respond to the WUS signal request information.

[0578] In some possible implementations, the network side is configured with at least one of the following:

[0579] WUS config index 1, applicable to UE feature 1;

[0580] WUS config index 2, applicable to UE feature 2;

[0581] WUS config index 3, applicable to UE feature 3;

[0582] WUS config index 4, applicable to UE feature 4;

[0583] WUS config index 5, applicable to UE feature 5;

[0584] When the UE sends a UL-WUS request SIB1, and the network sends a RAR indicating WUS index 3, the UE determines whether to respond to the request if the RAR indicates UE feature 3.

[0585] In some other possible implementations, the network side is configured with at least one of the following:

[0586] Preamble identifier range 1, applicable to UE request OD-SIB1 for UE feature 1, associated with UE feature 1.

[0587] Preamble identifier range 2, applicable to UE request OD-SIB1 for UE feature 2, associated with UE feature 2.

[0588] Preamble identifier range 3, applicable to UE feature 3, UE request OD-SIB1 associated with UE feature 3.

[0589] If the UE sends a UL-WUS request SIB1 and the network sends a RAR, and the preamble index indicated in the RAR belongs to interval 2, then the UE determines whether the RAR indicates whether the UE responds to the request for UE feature 2.

[0590] In some other possible implementations, the UE sends a UL-WUS request SIB1, the network sends a RAR, and the RAR indicates the UE type / UE feature to which the RAR applies. Then, the UE of that type determines whether the network should respond to the request based on the RAR.

[0591] In this embodiment, the network can cover as many UE types as possible when deploying and configuring WUS, and in power-saving mode, select to enable or disable NES cell based on the actual UE type requesting SIB1.

[0592] Example 10: WUS configuration indicates whether WUS resources overlap with the RACH resources of the associated NES cell.

[0593] Currently, when a UE sends a WUS to an NES cell, it listens for the corresponding RAR (WUS Feedback) sent by the NES cell. If the WUS resource and the legacy RO share resources, the MAC PDU of the RAR fed back by the network side includes MAC subPDUs for various purposes, and the order in which the UE reads the RAR needs to be enhanced accordingly. If the WUS resource and the legacy RO do not share resources, the MAC PDU of the RAR fed back by the network side may only include the MAC subPDU corresponding to the WUS, and the UE only needs to read that subPDU. In summary, the UE needs to know explicitly whether the WUS resource shares resources with the legacy RO.

[0594] In this embodiment of the application, the UE can determine whether WUS resources are shared with legacy RO resources in the following ways:

[0595] Method 1: WUS configuration explicitly indicates whether WUS resources are shared with legacy RO. For example, a 1-bit indicator indicates that the WUS resources are time-frequency resources shared with legacy RO, and a value of 1 indicates that the WUS resources are time-frequency resources independent of legacy RO.

[0596] Method 2: Configure shared ROs and separate ROs using separate IEs; one IE for shared ROs and one for separate ROs. For example, the UE can determine whether WUS resources overlap with legacy ROs based on these different IEs.

[0597] Method 3: Implicit indication.

[0598] For example, if the initial preamble is a specific value (e.g., 0), it indicates that the WUS resource is a separate RO; otherwise, it is a shared RO.

[0599] For another example, if the root sequence has a specific value, it indicates that the WUS resource is a separate RO; otherwise, it is a shared RO.

[0600] For example, if the preamble count is a specific value, it indicates that the WUS resource is a separate RO; otherwise, it is a shared RO.

[0601] For example, if msg1-FDM, msg1-FrequencyStart, and PRACH configuration Index are specific values, it indicates that the WUS resource is a separate RO; otherwise, it is a shared RO.

[0602] For example, if the UE feature / UE type is a specific type, it indicates that the WUS resource is a separate RO; otherwise, it is a shared RO.

[0603] In this embodiment, the UE can determine whether the WUS resources overlap with the legacyRACH resources of the associated NES cell based on the WUS configuration, which is beneficial for successfully reading the RAR.

[0604] Example 11:

[0605] The main idea of ​​this embodiment is that the UE can know in advance the UE features supported by the cells associated with these WUS through WUS configuration. Based on the UE feature, the UE selects appropriate resources to send WUS, allowing the base station to know which type of UE feature the UE belongs to, thus avoiding situations where a base station that does not support the UE feature responds to the UE. The solution is as follows:

[0606] The WUS configuration directly and explicitly indicates the UE feature / UE type to which the WUS configuration applies;

[0607] For example, UE feature / UE type includes, but is not limited to, at least one of the following: Redcap, eRedcap, NTN, ATG, NES, cell DRX / DTX, coverage enhancement, SDT, MBS, etc.

[0608] In the WUS configuration, Per cell indicates bar information related to different features, including at least one of the following:

[0609] intraFreqReselectionRedCap;

[0610] In some examples, the optional configuration `intraFreqReselectionRedCap` is included in the WUS configuration. If this field exists, it indicates that the cell corresponding to this WUS configuration supports Redcap. Further, if `intraFreqReselectionRedCap` is set to `allow`, it indicates support for intra-frequency reselection; if `intraFreqReselectionRedCap` is set to `Not allowed`, it indicates that intra-frequency reselection is not supported. If this field does not exist, it means that this cell does not support Redcap, meaning this WUS configuration is only applicable to non-Redcap UEs.

[0611] cellBarredRedCap1Rx;

[0612] cellBarredRedCap2Rx;

[0613] halfDuplexRedCap-Allowed;

[0614] intraFreqReselectionRedCap;

[0615] cellBarredRedCap1Rx;

[0616] cellBarredRedCap2Rx;

[0617] cellBarredATG-r18;

[0618] intraFreqReselection-eRedCap-r18;

[0619] cellBarredFixedVSAT-r18;

[0620] cellBarredMobileVSAT-r18;

[0621] cellBarred2RxXR-r18;

[0622] intraFreqReselection2RxXR-r18;

[0623] cellBarredeRedCap-r18;

[0624] cellBarredeRedCap1Rx-r18;

[0625] cellBarredeRedCap2Rx-r18.

[0626] It should be noted that the above parameters can be configured in one set, corresponding to multiple primary cells, or multiple sets can be configured, each corresponding to a different primary cell.

[0627] Example 12:

[0628] The protocol stipulates that the OD-SIB1 feature does not support / does not allow one or more of the following UE feature / UE type combinations:

[0629] Redcap;

[0630] eRedcap;

[0631] NTN;

[0632] ATG;

[0633] NES;

[0634] Cell DRX / DTX;

[0635] Enhanced coverage;

[0636] XR;

[0637] FixedVSAT;

[0638] MobileVSAT;

[0639] 2RxXR.

[0640] In the embodiment, the protocol specifies in advance that certain features do not support OD-SIB1 at all, so the WUS configuration does not need to carry the configuration related to these features, reducing configuration overhead.

[0641] Example 13: Different preamble resources distinguish UL-WUS with different priorities.

[0642] This embodiment includes the following steps:

[0643] Step 1: Configure at least two sets of preamble resources in the first configuration (including the preamble start number and the number of preambles), such as preamble resource 1 and preamble resource 2; different preamble resources correspond to different priorities of UL-WUS requests; preamble resource 1 is suitable for the scenario where the UE is camped in cell A and sends WUS, and preamble resource 2 is suitable for the scenario where the UE is camped in NES cell and sends WUS.

[0644] Step 2: When the UE is camped in cell A and meets the cell reselection condition or the WUS trigger condition, send UL WUS based on preamble resource 1;

[0645] When the UE is camped on the NES cell and the WUS triggering condition is met, UL WUS is sent based on preamble resource 2.

[0646] Step 3: When the network side receives WUS from multiple UEs at the same time, it prioritizes responding to UL-WUS based on preamble resource 1.

[0647] It should be noted that the technical consideration is that when the UE is camped in cell A, the network should respond more quickly to send SIB1. Otherwise, the UE may not have a suitable cell to camp in. Therefore, if the UE is using the preamble resources corresponding to cell A, the network side will respond with higher priority. The benefit of this technology is that it lets the network know whether to process the OD-SIB1 request of the UE camped in cell A with high priority.

[0648] Example 14: Different preamble resources distinguish different UE features.

[0649] This embodiment includes the following steps:

[0650] Step 1: Configure multiple preamble resources in the first configuration (including the preamble start number and the number of preambles), such as preamble resource 1, preamble resource 2, and preamble resource 3; different preamble resources correspond to different UE features / UE types / UE categories / technical characteristics / device characteristics; preamble resource 1 is suitable for redcap UEs, preamble resource 2 is suitable for eRedcap UEs, and preamble resource 3 is suitable for non-redcap UEs;

[0651] Step 2: The redcap UE uses preamble resource 1 to send UL-WUS;

[0652] Step 3: The network side receives the UL-WUS and determines that the UL-WUS was sent by a Redcap UE. Ultimately, only base stations that support the Redcap feature will respond to the UL-WUS.

[0653] Example 15:

[0654] On the network side, a set of UL-WUS resource configurations for requesting SIB1 UEs is independently configured in the WUS configuration. This RRC parameter is named SIB1-RequestResourceRedCap. This UL-WUS resource configuration can configure the preamble start identifier, number of preambles, SSB per RO, preamble per SSB, ra-AssociationPeriodIndex, ra-ssb-OccasionMaskIndex, sib1-RequestPeriod, ssb-perRACH-OccasionAndPreamblesPerSSB, totalNumberOfRA-Preambles, Prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, zeroCorrelationZoneConfig, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, ra-ResponseWindow, and ssb-perRACH-Occasion.

[0655] It should be noted that the SIB1 and SIB involved in the embodiments of this application can be replaced by SIB, where SIB1 is an example of SIB; SIB can be one or more of SIB1-SIBX, or a combination of more of them.

[0656] The cell in this application can be replaced with carrier, serving cell, BWP, TRP, etc.

[0657] The wake-up signal mentioned in this application can be understood as an on-demand signal request.

[0658] The transmission / adjustment of downlink channels / signals (such as SIBs) involved in this application can be understood as SIBs being transmitted from non-transmission to transmission, or from a large period to a small period, or from non-transmission to periodic transmission, etc.

[0659] The RO involved in this application can be understood as the time-frequency resource / opportunity for transmitting WUS (target uplink signal), the preamble involved in this patent can be understood as the WUS target uplink signal, and the target uplink signal feedback can be understood as RAR (Random Access Response).

[0660] The UE features, UE types, and UE categories mentioned in this application have similar meanings; they all refer to UEs that support certain technical features or different UE categories.

[0661] The types, characteristics, profiles, etc. of "devices" mentioned in this application include terminal or network devices.

[0662] In this embodiment, the UE pre-confirms whether the target cell supports the UE type based on the WUS configuration and sends a WUS that supports the UE type. This avoids the UE waking up base stations that do not support the UE type / UE feature / UE category. The network side can pre-confirm the UE type based on the WUS sent by the UE, preventing base stations that do not support the UE type / UE feature / UE category from responding to the UE's request. When the WUS configuration is associated with multiple NES cells, different preamble resources or RO resources can be associated with different NES cells to ensure that the target NES cell requested by the UE for SIB1 is consistent with the responding NES cell. When the WUS configuration is associated with multiple NES cells, the UE decodes the RAR based on the new RA-RNTI scrambling formula, which can confirm whether the responding NES cell is the target NES cell.

[0663] The uplink signal transmission method provided in this application can be executed by an uplink signal transmission device. This application uses the example of an uplink signal transmission device executing the uplink signal transmission method to illustrate the uplink signal transmission device provided in this application.

[0664] This application provides an uplink signal transmitting device. As an example, the uplink signal transmitting device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0665] The uplink signal transmitting device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0666] For details, see Figure 12 When the uplink signal transmitting device is a terminal or a component in a terminal, the uplink signal transmitting device 400 includes a transmitting module 401, which is used to transmit a target uplink signal based on UE characteristics and first configuration information; wherein the first configuration information corresponds to at least one UE characteristic, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE characteristic; the target uplink signal is used to request the adjustment of the downlink signal or channel of the target cell.

[0667] In some embodiments of this application, the first configuration information is indicated by a network-side device, and the first configuration information is used to indicate at least one of the following:

[0668] The identifier or identifier list of the first cell associated with the first configuration information;

[0669] The first configuration information is associated with the first cell corresponding to ssb-positionInBurst;

[0670] The UE characteristics associated with the first configuration information;

[0671] Target uplink signal feedback monitoring configuration;

[0672] Target configuration;

[0673] The maximum number of SSBs allowed for SSB mapping;

[0674] The target time period is used to determine the time during which the UE listens for the uplink signal feedback from the target.

[0675] The first cell is the cell that allows UEs to request adjustments to downlink signals or channels.

[0676] In some embodiments of this application, the first configuration information configures only a single ssb-positionInBurst, and a single ssb-positionInBurst is associated with multiple first cells.

[0677] In some embodiments of this application, the first configuration information configures multiple ssb-positionInBursts, and the multiple ssb-positionInBursts are associated with multiple first cells respectively.

[0678] In some embodiments of this application, the target uplink signal feedback monitoring configuration includes at least one of the following:

[0679] Target uplink signal feedback search space configuration;

[0680] Target uplink signal feedback control resource set configuration.

[0681] In some embodiments of this application, the target configuration includes at least one set of configurations, each set of configurations corresponding to at least one first cell, or each set of configurations corresponding to at least one UE feature, or each set of configurations corresponding to at least one UE feature supported by at least one first cell.

[0682] In some embodiments of this application, the target configuration described above includes at least one of the following:

[0683] UE characteristics associated with the target configuration;

[0684] Devices supporting specific technical features request time-frequency resource allocation for the target downlink signal or the target uplink signal, adjusting the channel.

[0685] SSB mapping related configurations;

[0686] Target uplink signal preamble sequence resource configuration;

[0687] Target uplink signal time-frequency resource allocation;

[0688] The SIB1 request period, sib1-RequestPeriod, is measured in terms of the association period.

[0689] The association period identifier ra-AssociationPeriodIndex is used to indicate the available association period among multiple association periods;

[0690] The RO mask identifier ra-ssb-OccasionMaskIndex is used to indicate the available ROs among multiple ROs associated with a single SSB;

[0691] UEs that support specific technical features can be used to request UL WUS resource configuration for SIB1, such as a separately configured Redcap UE for requesting WUS resource configuration for SIB1, i.e., SIB1-RequestResourceRedCap.

[0692] The first indication information is used to indicate whether lightweight terminals are allowed to perform same-frequency reselection;

[0693] The second instruction information is used to indicate whether the first cell allows the access of a lightweight terminal.

[0694] The third instruction information is used to indicate whether the first cell allows access for two lightweight terminals;

[0695] The fourth indication information is used to indicate whether the first cell allows access for lightweight terminals that support half-duplex frequency division duplex.

[0696] The fifth indication information is used to indicate whether the first cell allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS).

[0697] The sixth instruction information is used to indicate whether the first cell allows air-to-ground connections;

[0698] The seventh indication information is used to indicate whether the first cell allows UEs that support the nes-CellDTX-DRX feature to access;

[0699] The eighth indication information is used to indicate whether enhanced lightweight UEs are allowed to perform same-frequency reselection;

[0700] The ninth instruction information is used to indicate whether the first cell allows access for fixed Very Small Aperture Satellite Communication (VSAT) terminals;

[0701] The tenth instruction information is used to indicate whether the first cell allows the mobile VSAT terminal to access;

[0702] The eleventh instruction information is used to indicate whether the first cell allows access for two Extended Reality (XR) terminals.

[0703] The twelfth instruction information is used to indicate whether two XR receiving terminals are allowed to perform same-frequency reselection;

[0704] The thirteenth instruction message is used to indicate whether the first cell allows the enhanced lightweight terminal to access;

[0705] The fourteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight receiver terminal to access;

[0706] The fifteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight 2-receiver terminal to access;

[0707] The sixteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the random access channel (RACH) resources of the first cell.

[0708] The seventeenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the RACH resources of the first cell used for system information requests;

[0709] The eighteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the additional RACH resources of the first cell.

[0710] In some embodiments of this application, the SSB mapping-related configuration includes at least one of the following:

[0711] The number of SSBs associated with each RACH timing RO;

[0712] The number of preambles associated with each SSB.

[0713] In some embodiments of this application, the target uplink signal preamble sequence resource configuration includes at least one of the following:

[0714] Preamble root sequence;

[0715] The number of preambles associated with each SSB;

[0716] Preamble start index;

[0717] Number of preambles in the target uplink signal;

[0718] Number of preambles used for random access.

[0719] In some embodiments of this application, the target uplink signal time-frequency resource configuration includes at least one of the following:

[0720] Frequency domain timings;

[0721] Frequency domain start timing identifier;

[0722] Physical Random Access Channel (PRACH) Configuration Index;

[0723] Permissible associated period identifiers;

[0724] Allowed RO mask identifiers.

[0725] In some embodiments of this application, the first configuration information is used to indicate UE characteristics; the UE sends a target uplink signal based on the UE characteristics and the first configuration information, including:

[0726] If the WUS transmission conditions are met, the UE transmits the target uplink signal based on the first configuration information;

[0727] The WUS transmission condition includes the UE's UE characteristics matching the UE characteristics associated with the first configuration information.

[0728] In some embodiments of this application, the uplink signal transmitting device may further include: a processing module, which is configured to listen to the target uplink signal feedback scrambled by the Radio Network Temporary Identifier RNTI calculated by the first formula, or to listen to the Physical Downlink Control Channel (PDCCH) corresponding to the target uplink signal feedback scrambled by the RNTI; wherein the first formula is a newly defined formula for the Random Access Radio Network Temporary Identifier RA-RNTI, and the first formula is related to the identifier of the first cell associated with the first configuration information.

[0729] In some embodiments of this application, the first formula includes at least a first parameter, which is the identifier of the first cell associated with the first configuration information.

[0730] In some embodiments of this application, the processing module is further configured to, upon detecting target uplink signal feedback, determine whether the cell responding to the target uplink signal is the target cell based on the target uplink signal feedback; if the cell is not the target cell, re-determine the conditions for sending the target uplink signal, or resend the target uplink signal.

[0731] In some embodiments of this application, the processing module is further configured to confirm that the target uplink signal request was successful if the target uplink signal feedback is detected and the target uplink signal feedback carries the preamble identifier of the target uplink signal.

[0732] In some embodiments of this application, the first configuration information is used to indicate a target time period; the processing module is also used to re-determine the conditions for sending the target uplink signal or resend the target uplink signal if no target uplink signal feedback is detected within the target time period.

[0733] In some embodiments of this application, the target uplink signal feedback indicates at least one of the following:

[0734] Do not respond to the target's uplink signal request;

[0735] Responding to the target's uplink signal request;

[0736] The identifier of the cell that responded to the target uplink signal request;

[0737] UE characteristics associated with the target uplink signal feedback;

[0738] Whether the first cell associated with the first configuration information allows UEs with specific characteristics to access;

[0739] Whether lightweight terminals are allowed to perform same-frequency reselection;

[0740] Does the first cell associated with the first configuration information allow access from a lightweight terminal?

[0741] Does the first cell associated with the first configuration information allow access from two lightweight terminals?

[0742] Does the first cell associated with the first configuration information allow access for lightweight terminals that support half-duplex frequency division duplex?

[0743] Whether the first cell associated with the first configuration information allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS);

[0744] Does the first cell associated with the first configuration information allow air-to-ground connections?

[0745] Does the first cell associated with the first configuration information allow UEs supporting the nes-CellDTX-DRX feature to access?

[0746] Does the first cell associated with the first configuration information allow enhanced lightweight UEs to perform same-frequency reselection?

[0747] Does the first cell associated with the first configuration information allow access for fixed very small aperture satellite communication (VSAT) terminals?

[0748] Whether the first cell associated with the first configuration information allows mobile VSAT terminals to access;

[0749] Does the first cell associated with the first configuration information allow access for two XR terminals?

[0750] Should two Extended Reality (XR) terminals be allowed to reselect on the same frequency?

[0751] Whether the first cell associated with the first configuration information allows enhanced lightweight terminals to access;

[0752] Whether the first cell associated with the first configuration information allows the enhanced lightweight receiver terminal to access;

[0753] Does the first cell associated with the first configuration information allow enhanced lightweight 2D receiver terminals to access?

[0754] In some embodiments of this application, the above-described processing module is further configured to determine the time reference cell for transmitting the target uplink signal;

[0755] The reference cell includes at least one of the following:

[0756] The cell configured or indicated by the network-side equipment;

[0757] The cell in which the UE receives the first configuration message;

[0758] Target residential area;

[0759] Among the first cells associated with the first configuration information, the cells that meet the signal conditions;

[0760] Among them, the signal conditions include at least one of the following: the reference signal received power RSRP is at its maximum, and the signal-to-interference-plus-noise ratio (SINR) is at its maximum.

[0761] In some embodiments of this application, the time difference between multiple first cells associated with the first configuration information is less than a first threshold, and the first threshold is determined based on the protection period (GP).

[0762] The subcarrier spacing (SCS) of the GP is determined based on at least one of the following:

[0763] The SCS of the UE's serving cell;

[0764] The timing of the UE transmitting the target uplink signal is referenced to the SCS of the cell.

[0765] The UE obtains the SCS of the first configured cell;

[0766] The largest SCS in the first cell associated with the first configuration information;

[0767] The smallest SCS in the first cell associated with the first configuration information.

[0768] In some embodiments of this application, the above-mentioned processing module is further configured to determine whether the time-frequency resources that allow the transmission of the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information. The first RACH resources include at least one of the following: RACH resources of the first cell for system information requests, additional RACH resources of the first cell, and RACH resources of the first cell for random access.

[0769] The time-frequency resources that allow the transmission of the target uplink signal to overlap or not overlap with the first RACH resources of the first cell are determined based on at least one of the following:

[0770] This is explicitly indicated by the first configuration information;

[0771] Different information domains (IEs) are used to configure overlapping random access timing and non-overlapping random access timing respectively.

[0772] Implicit indication of network-side devices.

[0773] In some embodiments of this application, the above-mentioned processing module is specifically used to determine, based on the first configuration information, whether the time-frequency resources for transmitting the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information.

[0774] In some embodiments of this application, the first configuration information includes at least one of the following:

[0775] The starting preamble identifier corresponding to the first cell;

[0776] The preamble root sequence corresponding to the first cell;

[0777] The number of preambles corresponding to the first cell;

[0778] The frequency domain resource start timing identifier corresponding to the target uplink signal;

[0779] The number of frequency domain resource opportunities corresponding to the target uplink signal;

[0780] PRACH configuration index;

[0781] UE features.

[0782] The uplink signal transmitting apparatus provided in this application transmits a target uplink signal based on a UE type and first configuration information. The first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE type. The target uplink signal is used to request a downlink signal or channel from a target cell. Through this method, the uplink signal transmitting apparatus can pre-determine whether a target cell supports its UE type based on the first configuration information and its own UE type. It can transmit the target uplink signal when the target cell supports its UE type, avoiding the increased number of attempts and latency during cell reselection caused by transmitting the target uplink signal to a cell that does not support the UE type, thereby improving communication performance.

[0783] The resource configuration method provided in this application can be executed by a resource configuration device. This application uses the example of a resource configuration device executing the resource configuration method to illustrate the resource configuration device provided in this application.

[0784] This application provides a resource allocation device. As an example, the uplink signal transmitting device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0785] The resource allocation device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0786] For details, see Figure 13 When the resource configuration device is a network-side device or a component of a network-side device, the resource configuration device 500 includes a sending module 501, which is used to send first configuration information to a user equipment (UE); wherein the first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature.

[0787] In some embodiments of this application, the first configuration information described above is used to indicate at least one of the following:

[0788] The identifier or identifier list of the first cell associated with the first configuration information;

[0789] The first configuration information is associated with the first cell corresponding to ssb-positionInBurst;

[0790] The UE characteristics associated with the first configuration information;

[0791] Target uplink signal feedback monitoring configuration;

[0792] Target configuration;

[0793] The maximum number of SSBs allowed for SSB mapping;

[0794] The target time period is used to determine the time during which the UE listens for the uplink signal feedback from the target.

[0795] The first cell is the cell that allows UEs to request adjustments to downlink signals or channels.

[0796] In some embodiments of this application, the first configuration information configures only a single ssb-positionInBurst, and a single ssb-positionInBurst is associated with multiple first cells.

[0797] In some embodiments of this application, the first configuration information configures multiple ssb-positionInBursts, and the multiple ssb-positionInBursts are associated with multiple first cells respectively.

[0798] In some embodiments of this application, the target uplink signal feedback monitoring configuration includes at least one of the following:

[0799] Target uplink signal feedback search space configuration;

[0800] Target uplink signal feedback control resource set configuration.

[0801] In some embodiments of this application, the target configuration includes at least one set of configurations, each set of configurations corresponding to at least one first cell, or each set of configurations corresponding to at least one UE feature, or each set of configurations corresponding to at least one UE feature supported by at least one first cell.

[0802] In some embodiments of this application, the target configuration includes at least one of the following:

[0803] SSB mapping related configurations;

[0804] Target uplink signal preamble sequence resource configuration;

[0805] Target uplink signal time-frequency resource allocation;

[0806] The SIB1 request period, sib1-RequestPeriod, is measured in terms of the association period.

[0807] The association period identifier ra-AssociationPeriodIndex is used to indicate the available association period among multiple association periods;

[0808] The RO mask identifier ra-ssb-OccasionMaskIndex is used to indicate the available ROs among multiple ROs associated with a single SSB;

[0809] UEs that support specific technical features can be used to request UL WUS resource configuration for SIB1, such as a separately configured Redcap UE for requesting WUS resource configuration for SIB1, i.e., SIB1-RequestResourceRedCap.

[0810] The first indication information is used to indicate whether the first cell allows lightweight terminals to perform same-frequency reselection;

[0811] The second indication information is used to indicate whether the first cell allows access for a lightweight terminal with 1 receiver;

[0812] The third instruction information is used to indicate whether the first cell allows access for two lightweight terminals;

[0813] The fourth indication information is used to indicate whether the first cell allows access for lightweight terminals that support half-duplex frequency division duplex.

[0814] The fifth indication information is used to indicate whether the first cell allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS).

[0815] The sixth instruction information is used to indicate whether the first cell allows air-to-ground connections;

[0816] The seventh indication information is used to indicate whether the first cell allows UEs that support the nes-CellDTX-DRX feature to access;

[0817] The eighth indication information is used to indicate whether enhanced lightweight UEs are allowed to perform same-frequency reselection;

[0818] The ninth instruction information is used to indicate whether the first cell allows access for fixed Very Small Aperture Satellite Communication (VSAT) terminals;

[0819] The tenth instruction information is used to indicate whether the first cell allows the mobile VSAT terminal to access;

[0820] The eleventh instruction information is used to indicate whether the first cell allows access for two Extended Reality (XR) terminals.

[0821] The twelfth instruction information is used to indicate whether two XR receiving terminals are allowed to perform same-frequency reselection;

[0822] The thirteenth instruction message is used to indicate whether the first cell allows the enhanced lightweight terminal to access;

[0823] The fourteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight receiver terminal to access;

[0824] The fifteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight 2-receiver terminal to access;

[0825] The sixteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the RACH resources of the first cell;

[0826] The seventeenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the RACH resources of the first cell used for system information requests;

[0827] The eighteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the additional RACH resources of the first cell.

[0828] In some embodiments of this application, the SSB mapping-related configuration includes at least one of the following:

[0829] The number of SSBs associated with each RACH timing RO;

[0830] The number of preambles associated with each SSB.

[0831] In some embodiments of this application, the target uplink signal preamble sequence resource configuration includes at least one of the following:

[0832] Preamble root sequence;

[0833] The number of preambles associated with each SSB;

[0834] Preamble start index;

[0835] Number of preambles in the target uplink signal;

[0836] Number of preambles used for random access.

[0837] In some embodiments of this application, the target uplink signal time-frequency resource configuration includes at least one of the following:

[0838] Frequency domain timings;

[0839] Frequency domain start timing identifier;

[0840] Physical Random Access Channel (PRACH) Configuration Index;

[0841] Permissible associated period identifiers;

[0842] Allowed RO mask identifiers.

[0843] In some embodiments of this application, the resource configuration apparatus may further include a receiving module, which is configured to receive a target uplink signal from a UE, the target uplink signal being used to request adjustment of the downlink signal or channel of a target cell; the sending module is further configured to send a target uplink signal feedback to the UE or send a physical downlink control channel (PDCCH) corresponding to the target uplink signal feedback to the UE; wherein the target uplink signal feedback carries a preamble identifier of the target uplink signal.

[0844] In some embodiments of this application, the above-mentioned sending module is specifically used to send the target uplink signal feedback scrambled by the Radio Network Temporary Identifier RNTI calculated by the first formula to the UE; or, to send the PDCCH corresponding to the target uplink signal feedback scrambled by the RNTI to the UE; wherein, the first formula is the formula for the newly defined Random Access Radio Network Temporary Identifier RA-RNTI, and the first formula is related to the identifier of the first cell associated with the first configuration information.

[0845] In some embodiments of this application, the first formula includes at least a first parameter, which is the identifier of the first cell associated with the first configuration information.

[0846] In some embodiments of this application, the target uplink signal feedback indicates at least one of the following:

[0847] Do not respond to the target's uplink signal request;

[0848] Responding to the target's uplink signal request;

[0849] The identifier of the cell that responded to the target uplink signal request;

[0850] UE characteristics associated with the target uplink signal feedback;

[0851] Whether the first cell associated with the first configuration information allows UEs with specific characteristics to access;

[0852] Does the first cell associated with the first configuration information allow lightweight terminals to reselect on the same frequency?

[0853] Does the first cell associated with the first configuration information allow access from a lightweight terminal?

[0854] Does the first cell associated with the first configuration information allow access from two lightweight terminals?

[0855] Does the first cell associated with the first configuration information allow access for lightweight terminals that support half-duplex frequency division duplex?

[0856] Whether the first cell associated with the first configuration information allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS);

[0857] Does the first cell associated with the first configuration information allow air-to-ground connections?

[0858] Does the first cell associated with the first configuration information allow UEs supporting the nes-CellDTX-DRX feature to access?

[0859] Does the first cell associated with the first configuration information allow enhanced lightweight UEs to perform same-frequency reselection?

[0860] Does the first cell associated with the first configuration information allow access for fixed very small aperture satellite communication (VSAT) terminals?

[0861] Whether the first cell associated with the first configuration information allows mobile VSAT terminals to access;

[0862] Does the first cell associated with the first configuration information allow access for two XR terminals?

[0863] Should two Extended Reality (XR) terminals be allowed to reselect on the same frequency?

[0864] Whether the first cell associated with the first configuration information allows enhanced lightweight terminals to access;

[0865] Whether the first cell associated with the first configuration information allows the enhanced lightweight receiver terminal to access;

[0866] Does the first cell associated with the first configuration information allow enhanced lightweight 2D receiver terminals to access?

[0867] In some embodiments of this application, the time difference between multiple first cells associated with the first configuration information is less than a first threshold, and the first threshold is determined based on the protection period (GP).

[0868] The subcarrier spacing (SCS) of the GP is determined based on at least one of the following:

[0869] The SCS of the UE's serving cell;

[0870] The timing of the UE transmitting the target uplink signal is referenced to the SCS of the cell.

[0871] The UE obtains the SCS of the first configured cell;

[0872] The largest SCS in the first cell associated with the first configuration information;

[0873] The smallest SCS in the first cell associated with the first configuration information.

[0874] In some embodiments of this application, the first configuration information includes at least one of the following:

[0875] The starting preamble identifier corresponding to the first cell;

[0876] The preamble root sequence corresponding to the first cell;

[0877] The number of preambles corresponding to the first cell;

[0878] The frequency domain resource start timing identifier corresponding to the target uplink signal;

[0879] The number of frequency domain resource opportunities corresponding to the target uplink signal;

[0880] PRACH configuration index;

[0881] UE features.

[0882] The resource configuration apparatus provided in this application embodiment can configure the UE features by corresponding to a first configuration for at least one UE feature, thereby providing the most suitable resource allocation scheme for the UE with at least one UE feature, and improving the speed and efficiency of data transmission.

[0883] The uplink signal transmitting device provided in this application embodiment can implement the various processes implemented in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0884] like Figure 14 As shown, this application embodiment also provides a communication device 600, including a processor 601 and a memory 602. The memory 602 stores programs or instructions that can run on the processor 601. For example, when the communication device 600 is a terminal, the program or instructions executed by the processor 601 implement the various steps of the above-described uplink signal transmission method embodiment and achieve the same technical effect. When the communication device 600 is a network-side device, the program or instructions executed by the processor 601 implement the various steps of the above-described resource allocation method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0885] This application also provides a terminal (UE) including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment of the UE described above. This terminal embodiment corresponds to the terminal-side method embodiment described above. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 12 The uplink signal transmitting device shown. Specifically, Figure 15A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0886] The terminal 100 includes, but is not limited to, at least some of the following components: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0887] Those skilled in the art will understand that the terminal 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 15 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0888] It should be understood that, in this embodiment, the input unit 104 may include a graphics processor 1041 and a microphone 1042. The graphics processor 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 107 includes a touch panel 1071 and at least one of other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0889] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 101 can transmit it to the processor 110 for processing; in addition, the radio frequency unit 101 can send uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0890] The memory 109 can be used to store software programs or instructions, as well as various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0891] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0892] The radio frequency unit 101 is used to transmit a target uplink signal based on UE characteristics and first configuration information; wherein the first configuration information corresponds to at least one UE characteristic, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE characteristic; the target uplink signal is used to request adjustment of the downlink signal or channel of the target cell.

[0893] In some embodiments of this application, the first configuration information is indicated by a network-side device, and the first configuration information is used to indicate at least one of the following:

[0894] The identifier or identifier list of the first cell associated with the first configuration information;

[0895] The first configuration information is associated with the first cell corresponding to ssb-positionInBurst;

[0896] The UE characteristics associated with the first configuration information;

[0897] Target uplink signal feedback monitoring configuration;

[0898] Target configuration;

[0899] The maximum number of SSBs allowed for SSB mapping;

[0900] The target time period is used to determine the time during which the UE listens for the uplink signal feedback from the target.

[0901] The first cell is the cell that allows UEs to request adjustments to downlink signals or channels.

[0902] In some embodiments of this application, the first configuration information configures only a single ssb-positionInBurst, and a single ssb-positionInBurst is associated with multiple first cells.

[0903] In some embodiments of this application, the first configuration information configures multiple ssb-positionInBursts, and the multiple ssb-positionInBursts are associated with multiple first cells respectively.

[0904] In some embodiments of this application, the target uplink signal feedback monitoring configuration includes at least one of the following:

[0905] Target uplink signal feedback search space configuration;

[0906] Target uplink signal feedback control resource set configuration.

[0907] In some embodiments of this application, the target configuration includes at least one set of configurations, each set of configurations corresponding to at least one first cell, or each set of configurations corresponding to at least one UE feature, or each set of configurations corresponding to at least one UE feature supported by at least one first cell.

[0908] In some embodiments of this application, the target configuration described above includes at least one of the following:

[0909] UE characteristics associated with the target configuration;

[0910] Devices supporting specific technical features request time-frequency resource allocation for the target downlink signal or the target uplink signal, adjusting the channel.

[0911] SSB mapping related configurations;

[0912] Target uplink signal preamble sequence resource configuration;

[0913] Target uplink signal time-frequency resource allocation;

[0914] The SIB1 request period, sib1-RequestPeriod, is measured in terms of the association period.

[0915] The association period identifier ra-AssociationPeriodIndex is used to indicate the available association period among multiple association periods;

[0916] The RO mask identifier ra-ssb-OccasionMaskIndex is used to indicate the available ROs among multiple ROs associated with a single SSB;

[0917] UEs that support specific technical features can be used to request UL WUS resource configuration for SIB1, such as a separately configured Redcap UE for requesting WUS resource configuration for SIB1, i.e., SIB1-RequestResourceRedCap.

[0918] The first indication information is used to indicate whether lightweight terminals are allowed to perform same-frequency reselection;

[0919] The second instruction information is used to indicate whether the first cell allows the access of a lightweight terminal.

[0920] The third instruction information is used to indicate whether the first cell allows access for two lightweight terminals;

[0921] The fourth indication information is used to indicate whether the first cell allows access for lightweight terminals that support half-duplex frequency division duplex.

[0922] The fifth indication information is used to indicate whether the first cell allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS).

[0923] The sixth instruction information is used to indicate whether the first cell allows air-to-ground connections;

[0924] The seventh indication information is used to indicate whether the first cell allows UEs that support the nes-CellDTX-DRX feature to access;

[0925] The eighth indication information is used to indicate whether enhanced lightweight UEs are allowed to perform same-frequency reselection;

[0926] The ninth instruction information is used to indicate whether the first cell allows access for fixed Very Small Aperture Satellite Communication (VSAT) terminals;

[0927] The tenth instruction information is used to indicate whether the first cell allows the mobile VSAT terminal to access;

[0928] The eleventh instruction information is used to indicate whether the first cell allows access for two Extended Reality (XR) terminals.

[0929] The twelfth instruction information is used to indicate whether two XR receiving terminals are allowed to perform same-frequency reselection;

[0930] The thirteenth instruction message is used to indicate whether the first cell allows the enhanced lightweight terminal to access;

[0931] The fourteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight receiver terminal to access;

[0932] The fifteenth instruction information is used to indicate whether the first cell allows the enhanced lightweight 2-receiver terminal to access;

[0933] The sixteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the random access channel (RACH) resources of the first cell.

[0934] The seventeenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the RACH resources of the first cell used for system information requests;

[0935] The eighteenth indication information is used to indicate whether the time-frequency resources of the target uplink signal overlap or do not overlap with the additional RACH resources of the first cell.

[0936] In some embodiments of this application, the SSB mapping-related configuration includes at least one of the following:

[0937] The number of SSBs associated with each RACH timing RO;

[0938] The number of preambles associated with each SSB.

[0939] In some embodiments of this application, the target uplink signal preamble sequence resource configuration includes at least one of the following:

[0940] Preamble root sequence;

[0941] The number of preambles associated with each SSB;

[0942] Preamble start index;

[0943] Number of preambles in the target uplink signal;

[0944] Number of preambles used for random access.

[0945] In some embodiments of this application, the target uplink signal time-frequency resource configuration includes at least one of the following:

[0946] Frequency domain timings;

[0947] Frequency domain start timing identifier;

[0948] Physical Random Access Channel (PRACH) Configuration Index;

[0949] Permissible associated period identifiers;

[0950] Allowed RO mask identifiers.

[0951] In some embodiments of this application, the first configuration information is used to indicate UE characteristics; the UE sends a target uplink signal based on the UE characteristics and the first configuration information, including:

[0952] If the WUS transmission conditions are met, the UE transmits the target uplink signal based on the first configuration information;

[0953] The WUS transmission condition includes the UE's UE characteristics matching the UE characteristics associated with the first configuration information.

[0954] In some embodiments of this application, the uplink signal transmitting device may further include: a processor 110, which is configured to listen to the target uplink signal feedback scrambled by the Radio Network Temporary Identifier RNTI calculated by the first formula, or to listen to the Physical Downlink Control Channel (PDCCH) corresponding to the target uplink signal feedback scrambled by the RNTI; wherein, the first formula is a newly defined formula for the Random Access Radio Network Temporary Identifier RA-RNTI, and the first formula is related to the identifier of the first cell associated with the first configuration information.

[0955] In some embodiments of this application, the first formula includes at least a first parameter, which is the identifier of the first cell associated with the first configuration information.

[0956] In some embodiments of this application, the processor 110 is further configured to, upon detecting target uplink signal feedback, determine whether the cell responding to the target uplink signal is the target cell based on the target uplink signal feedback; if the cell is not the target cell, re-determine the conditions for sending the target uplink signal, or resend the target uplink signal.

[0957] In some embodiments of this application, the processor 110 is further configured to confirm that the target uplink signal request was successful if it detects a target uplink signal feedback and the target uplink signal feedback carries a preamble identifier of the target uplink signal.

[0958] In some embodiments of this application, the first configuration information is used to indicate a target time period; the processor 110 is also used to re-determine the conditions for sending the target uplink signal or resend the target uplink signal if no target uplink signal feedback is detected within the target time period.

[0959] In some embodiments of this application, the target uplink signal feedback indicates at least one of the following:

[0960] Do not respond to the target's uplink signal request;

[0961] Responding to the target's uplink signal request;

[0962] The identifier of the cell that responded to the target uplink signal request;

[0963] UE characteristics associated with the target uplink signal feedback;

[0964] Whether the first cell associated with the first configuration information allows UEs with specific characteristics to access;

[0965] Whether lightweight terminals are allowed to perform same-frequency reselection;

[0966] Does the first cell associated with the first configuration information allow access from a lightweight terminal?

[0967] Does the first cell associated with the first configuration information allow access from two lightweight terminals?

[0968] Does the first cell associated with the first configuration information allow access for lightweight terminals that support half-duplex frequency division duplex?

[0969] Whether the first cell associated with the first configuration information allows UE access that supports specific features, including at least one of Small Data Transmission (SDT) and Multicast Service (MBS);

[0970] Does the first cell associated with the first configuration information allow air-to-ground connections?

[0971] Does the first cell associated with the first configuration information allow UEs supporting the nes-CellDTX-DRX feature to access?

[0972] Does the first cell associated with the first configuration information allow enhanced lightweight UEs to perform same-frequency reselection?

[0973] Does the first cell associated with the first configuration information allow access for fixed very small aperture satellite communication (VSAT) terminals?

[0974] Whether the first cell associated with the first configuration information allows mobile VSAT terminals to access;

[0975] Does the first cell associated with the first configuration information allow access for two XR terminals?

[0976] Should two Extended Reality (XR) terminals be allowed to reselect on the same frequency?

[0977] Whether the first cell associated with the first configuration information allows enhanced lightweight terminals to access;

[0978] Whether the first cell associated with the first configuration information allows the enhanced lightweight receiver terminal to access;

[0979] Does the first cell associated with the first configuration information allow access for enhanced lightweight 2D receiver terminals?

[0980] In some embodiments of this application, the processor 110 is further configured to determine the time reference cell for transmitting the target uplink signal;

[0981] The reference cell includes at least one of the following:

[0982] The cell configured or indicated by the network-side equipment;

[0983] The cell in which the UE receives the first configuration message;

[0984] Target residential area;

[0985] Among the first cells associated with the first configuration information, the cells that meet the signal conditions;

[0986] Among them, the signal conditions include at least one of the following: the reference signal received power RSRP is at its maximum, and the signal-to-interference-plus-noise ratio (SINR) is at its maximum.

[0987] In some embodiments of this application, the time difference between multiple first cells associated with the first configuration information is less than a first threshold, and the first threshold is determined based on the protection period (GP).

[0988] The subcarrier spacing (SCS) of the GP is determined based on at least one of the following:

[0989] The SCS of the UE's serving cell;

[0990] The timing of the UE transmitting the target uplink signal is referenced to the SCS of the cell.

[0991] The UE obtains the SCS of the first configured cell;

[0992] The largest SCS in the first cell associated with the first configuration information;

[0993] The smallest SCS in the first cell associated with the first configuration information.

[0994] In some embodiments of this application, the processor 110 is further configured to determine whether the time-frequency resources that allow the transmission of the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information. The first RACH resources include at least one of the following: RACH resources of the first cell for system information requests, additional RACH resources of the first cell, and RACH resources of the first cell for random access.

[0995] The time-frequency resources that allow the transmission of the target uplink signal to overlap or not overlap with the first RACH resources of the first cell are determined based on at least one of the following:

[0996] This is explicitly indicated by the first configuration information;

[0997] Different information domains (IEs) are used to configure overlapping random access timing and non-overlapping random access timing respectively.

[0998] Implicit indication of network-side devices.

[0999] In some embodiments of this application, the processor 110 is specifically configured to determine, based on the first configuration information, whether the time-frequency resources for transmitting the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information.

[1000] In some embodiments of this application, the first configuration information includes at least one of the following:

[1001] The starting preamble identifier corresponding to the first cell;

[1002] The preamble root sequence corresponding to the first cell;

[1003] The number of preambles corresponding to the first cell;

[1004] The frequency domain resource start timing identifier corresponding to the target uplink signal;

[1005] The number of frequency domain resource opportunities corresponding to the target uplink signal;

[1006] PRACH configuration index;

[1007] UE features.

[1008] The terminal provided in this application embodiment transmits a target uplink signal based on a terminal type and first configuration information. The first configuration information corresponds to at least one terminal type, or the at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE type. The target uplink signal is used to request a downlink signal or channel from a target cell. Through this method, the uplink signal transmitting device can determine in advance whether the target cell supports its terminal type based on the first configuration information and its own terminal type. It can transmit the target uplink signal when the target cell supports its terminal type, avoiding the increase in the number of attempts and latency during cell reselection caused by sending the target uplink signal to a cell that does not support the terminal type, thereby improving communication performance.

[1009] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.

[1010] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment of the network-side device. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[1011] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 13 The resource allocation device shown. (For example...) Figure 16 As shown, the network-side device 30 includes: an antenna 31, a radio frequency (RF) device 32, a baseband device 33, a processor 34, and a memory 35. The antenna 31 is connected to the RF device 32. In the uplink direction, the RF device 32 receives information through the antenna 31 and transmits the received information to the baseband device 33 for processing. In the downlink direction, the baseband device 33 processes the information to be transmitted and sends it to the RF device 32. The RF device 32 processes the received information and transmits it through the antenna 31.

[1012] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 33, which includes a baseband processor.

[1013] Baseband device 33 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 3 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 35 via a bus interface to call the program in the memory 35 and execute the network device operation shown in the above method embodiment.

[1014] The network-side device may also include a network interface 36, such as a Common Public Radio Interface (CPRI).

[1015] Specifically, the network-side device 300 in this embodiment further includes: instructions or programs stored in memory 35 and executable on processor 34, wherein processor 34 calls the instructions or programs in memory 35 to execute. Figure 13 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[1016] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the above-described uplink signal transmission method or the various processes of the above-described resource configuration method embodiments, and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[1017] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[1018] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the above-described uplink signal transmission method or to implement the various processes of the above-described resource configuration method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[1019] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[1020] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the above-described uplink signal transmission method or the various processes of the above-described resource configuration method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[1021] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the uplink signal transmission method described above, and the network-side device can be used to perform the steps of the resource configuration method described above.

[1022] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[1023] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[1024] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. An uplink signal transmission method, characterized by, The method comprises: A user equipment (UE) sends a target uplink signal based on UE features and first configuration information; The first configuration information corresponds to at least one UE feature, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature; the target uplink signal is used to request adjustment of a downlink signal or channel of a target cell.

2. The method of claim 1, wherein, The first configuration information is indicated by a network side device, and the first configuration information is used to indicate at least one of the following: An identity or identity list of a first cell associated with the first configuration information; An ssb-positionInBurst corresponding to the first cell associated with the first configuration information; UE features associated with the first configuration information; Target uplink signal feedback monitoring configuration; Target configuration; A maximum number of SSBs allowed by SSB mapping; A target time period used to determine a time at which the UE monitors target uplink signal feedback; The first cell is a cell that allows the UE to request adjustment of a downlink signal or channel.

3. The method of claim 2, wherein, The first configuration information only configures a single ssb-positionInBurst, and the single ssb-positionInBurst is associated with multiple first cells; Or, the first configuration information configures multiple ssb-positionInBursts, and the multiple ssb-positionInBursts are respectively associated with multiple first cells.

4. The method of claim 3, wherein, The target uplink signal feedback monitoring configuration comprises at least one of the following: Target uplink signal feedback search space configuration; Target uplink signal feedback control resource set configuration.

5. The method of claim 2, wherein, The target configuration comprises at least one set of configurations, and each set of configurations corresponds to at least one first cell, or each set of configurations corresponds to at least one UE feature, or each set of configurations corresponds to at least one UE feature supported by at least one first cell.

6. The method according to any one of claims 2 to 5, characterized in that, The target configuration comprises at least one of the following: UE features associated with the target configuration; Time-frequency resource configuration of a target uplink signal requested by a device supporting a specific technical feature to request adjustment of a target downlink signal or channel; SSB mapping related configuration; Target uplink signal preamble sequence resource configuration; Target uplink signal time-frequency resource configuration; Period requested by a system information block (SIB1); Associated period identity; Random access occasion (RO) mask identity; Uplink (UL) wake-up signal (WUS) resource configuration of SIB1 requested by a UE supporting a specific technical feature; First indication information used to indicate whether a light terminal is allowed to perform inter-frequency reselection; Second indication information used to indicate whether the first cell allows access of a 1st light terminal; Third indication information used to indicate whether the first cell allows access of a 2nd light terminal; Fourth indication information used to indicate whether the first cell allows access of a light terminal supporting half-duplex frequency division duplexing; Fifth indication information, used for indicating whether the first cell allows access of a UE supporting a specific feature, the specific feature including at least one of small data transmission (SDT) and multicast service (MBS); Sixth indication information, used for indicating whether the first cell allows an air-to-ground connection; Seventh indication information, used for indicating whether the first cell allows access of a UE supporting a nes-CellDTX-DRX feature; Eighth indication information, used for indicating whether an enhanced light UE is allowed to perform intra-frequency reselection; Ninth indication information, used for indicating whether the first cell allows access of a fixed very small aperture terminal (VSAT) terminal; Tenth indication information, used for indicating whether the first cell allows access of a mobile VSAT terminal; Eleventh indication information, used for indicating whether the first cell allows access of a 2-receiver extended reality (XR) terminal; Twelfth indication information, used for indicating whether a 2-receiver XR terminal is allowed to perform intra-frequency reselection; Thirteenth indication information, used for indicating whether the first cell allows access of an enhanced light terminal; Fourteenth indication information, used for indicating whether the first cell allows access of an enhanced light 1-receiver terminal; Fifteenth indication information, used for indicating whether the first cell allows access of an enhanced light 2-receiver terminal; Sixteenth indication information, used for indicating whether time-frequency resources of the target uplink signal overlap or do not overlap with random access channel (RACH) resources of the first cell; Seventeenth indication information, used for indicating whether time-frequency resources of the target uplink signal overlap or do not overlap with RACH resources used for system information request of the first cell; Eighteenth indication information, used for indicating whether time-frequency resources of the target uplink signal overlap or do not overlap with additional RACH resources of the first cell.

7. The method of claim 6, wherein, The SSB mapping related configuration includes at least one of the following: A number of SSBs associated with each RACH occasion (RO); A number of preambles associated with each SSB.

8. The method of claim 6, wherein, The target uplink signal preamble sequence resource configuration includes at least one of the following: A preamble root sequence; A number of preambles associated with each SSB; A preamble starting index; A number of preambles of the target uplink signal; A number of preambles used for random access.

9. The method of claim 6, wherein, The target uplink signal time-frequency resource configuration includes at least one of the following: A number of frequency domain occasions; A frequency domain starting occasion identifier; A physical random access channel (PRACH) configuration index; An associated period identifier allowed to be used; An RO mask identifier allowed to be used.

10. The method according to any one of claims 1 to 9, characterized in that, The first configuration information is used for indicating a UE feature; The UE sends a target uplink signal based on the UE feature and the first configuration information, including: The UE sends a target uplink signal based on the first configuration information in a case where a WUS sending condition is met; The WUS sending condition comprises matching of a UE feature of the UE and a UE feature associated with the first configuration information.

11. The method according to any one of claims 1 to 10, characterized in that, The method further comprises: The UE listens to target uplink signal feedback scrambled by a radio network temporary identifier (RNTI) calculated by a first formula, or listens to a physical downlink control channel (PDCCH) corresponding to the target uplink signal feedback scrambled by the RNTI. The first formula is a newly defined random access radio network temporary identifier (RA-RNTI) formula, and the first formula is related to an identity of a first cell associated with the first configuration information.

12. The method of claim 11, wherein, The first formula comprises at least a first parameter, which is the identity of the first cell associated with the first configuration information.

13. The method according to any one of claims 1 to 12, characterized in that, The method further comprises: In a case where the UE listens to the target uplink signal feedback, the UE determines whether a cell responding to the target uplink signal is the target cell based on the target uplink signal feedback; If the cell is not the target cell, the UE rejudges a condition for sending the target uplink signal or sends the target uplink signal again.

14. The method according to any one of claims 1 to 13, characterized in that, The method further comprises: If the UE listens to the target uplink signal feedback and a preamble identity of the target uplink signal is carried in the target uplink signal feedback, the UE confirms that the target uplink signal request is successful.

15. The method according to any one of claims 1 to 14, characterized in that, The first configuration information is used to indicate the target time period; the method further comprises: If the UE does not listen to the target uplink signal feedback within the target time period, the UE rejudges the condition for sending the target uplink signal or sends the target uplink signal again.

16. The method according to any one of claims 11 to 15, characterized in that, The target uplink signal feedback indicates at least one of the following: No response to the request of the target uplink signal; Response to the request of the target uplink signal; Identity of a cell responding to the request of the target uplink signal; UE feature associated with the target uplink signal feedback; Whether the first cell associated with the first configuration information allows access of a UE with a specific feature; Whether a light terminal is allowed to perform intra-frequency reselection; Whether the first cell associated with the first configuration information allows access of a one-receiver light terminal; Whether the first cell associated with the first configuration information allows access of a two-receiver light terminal; Whether the first cell associated with the first configuration information allows access of a light terminal supporting half-duplex frequency-division duplexing; Whether the first cell associated with the first configuration information allows access of a UE supporting a specific feature, the specific feature comprising at least one of small data transmission (SDT) and multicast service (MBS); Whether the first cell associated with the first configuration information allows access of an air-to-ground terminal; Whether the first cell associated with the first configuration information allows access of a UE supporting nes-CellDTX-DRX feature Whether the first cell associated with the first configuration information allows intra-frequency reselection of an enhanced light terminal; Whether the first cell associated with the first configuration information allows access of a fixed very small aperture terminal (VSAT) terminal; Whether the first cell associated with the first configuration information allows access of a mobile VSAT terminal; whether the first cell associated with the first configuration information allows a 2-receiver extended reality (XR) terminal to access; whether the 2-receiver extended reality (XR) terminal is allowed to perform in-coverage reselection; whether the first cell associated with the first configuration information allows an enhanced lightweight terminal to access; whether the first cell associated with the first configuration information allows an enhanced lightweight 1-receiver terminal to access; whether the first cell associated with the first configuration information allows an enhanced lightweight 2-receiver terminal to access.

17. The method according to any one of claims 1 to 16, characterized in that, The method further comprises: The UE determines a time reference cell for sending the target uplink signal; The reference cell comprises at least one of: A cell configured or indicated by a network-side device; A cell that receives the first configuration message by the UE; The target cell; A cell in the first cell associated with the first configuration information that satisfies a signal condition; The signal condition comprises at least one of:

18. The method of any one of claims 1 to 17, wherein, Maximum reference signal received power (RSRP), and maximum signal-to-interference-plus-noise ratio (SINR). A time difference between a plurality of first cells associated with the first configuration information is less than a first threshold, and the first threshold is determined based on a guard period (GP); A subcarrier spacing (SCS) of the GP is determined based on at least one of: An SCS of a serving cell of the UE; An SCS of a time reference cell for the UE to send the target uplink signal; An SCS of a cell that the UE acquires a first configuration from; A maximum SCS in the first cell associated with the first configuration information; 19. The method of any one of claims 1 to 18, wherein, A minimum SCS in the first cell associated with the first configuration information. The method further comprises: The UE determines whether time-frequency resources allowed to send the target uplink signal overlap or do not overlap with first random access channel (RACH) resources of the first cell associated with the first configuration information, the first RACH resources comprising at least one of: RACH resources of the first cell for system information request, additional RACH resources of the first cell, and RACH resources of the first cell for random access; The determination of whether the time-frequency resources allowed to send the target uplink signal overlap or do not overlap with the first RACH resources of the first cell is based on at least one of: Explicit indication by the first configuration information; Different information elements (IEs) for respectively configuring overlapping and non-overlapping random access occasions; 20. The method of claim 19, wherein, Implicit indication by a network-side device. The determination by the UE of whether the time-frequency resources allowed to send the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information comprises:

21. The method of any one of claims 1 to 20, wherein, The UE determines, according to the first configuration information, whether the time-frequency resources allowed to send the target uplink signal overlap or do not overlap with the first RACH resources of the first cell associated with the first configuration information. The first configuration information comprises at least one of: A starting preamble identifier corresponding to the first cell; A preamble root sequence corresponding to the first cell; A number of preambles corresponding to the first cell; A frequency domain resource starting occasion identifier corresponding to the target uplink signal; A number of frequency domain resource occasions corresponding to the target uplink signal; A PRACH configuration index; 22. A resource configuration method, comprising: UE features. The method comprises: The network-side device sends first configuration information to a user equipment (UE); The first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature.

23. The method of claim 22, wherein, The first configuration information is used to indicate at least one of the following: An identity or a list of identities of a first cell associated with the first configuration information; An ssb-positionInBurst corresponding to the first cell associated with the first configuration information; A UE feature associated with the first configuration information; Target uplink signal feedback monitoring configuration; Target configuration; A maximum number of SSBs allowed for SSB mapping; A target time period used to determine a time for the UE to monitor target uplink signal feedback; The first cell is a cell that allows a UE to request adjustment of a downlink signal or channel.

24. The method of claim 23, wherein, The first configuration information only configures a single ssb-positionInBurst, and the single ssb-positionInBurst is associated with multiple first cells. Alternatively, the first configuration information configures multiple ssb-positionInBursts, and the multiple ssb-positionInBursts are respectively associated with multiple first cells.

25. The method of claim 23 or 24, wherein, The target configuration includes at least one of the following: A UE feature associated with the target configuration; A time-frequency resource configuration of a target uplink signal requested by a device supporting a specific technical feature to request adjustment of a target downlink signal or channel; SSB mapping related configuration; Target uplink signal preamble sequence resource configuration; Target uplink signal time-frequency resource configuration; A periodicity requested by SIB1; An associated periodicity identity; An RO mask identity; UL WUS resource configuration of SIB1 requested by a UE supporting a specific technical feature; First indication information used to indicate whether a light terminal is allowed to perform intra-frequency reselection in the first cell; Second indication information used to indicate whether a 1-receiver light terminal is allowed to access in the first cell; Third indication information used to indicate whether a 2-receiver light terminal is allowed to access in the first cell; Fourth indication information used to indicate whether a light terminal supporting half-duplex frequency-division duplex is allowed to access in the first cell; Fifth indication information used to indicate whether a UE supporting a specific feature is allowed to access in the first cell, the specific feature including at least one of small data transmission (SDT) and multicast service (MBS); Sixth indication information used to indicate whether an air-to-ground connection is allowed in the first cell; Seventh indication information used to indicate whether a UE supporting a nes-CellDTX-DRX feature is allowed to access in the first cell; Eighth indication information used to indicate whether an enhanced light UE is allowed to perform intra-frequency reselection; Ninth indication information used to indicate whether a fixed very small aperture terminal satellite (VSAT) terminal is allowed to access in the first cell; Tenth indication information, used for indicating whether the first cell allows mobile VSAT terminal access; Eleventh indication information, used for indicating whether the first cell allows 2-receiver extended reality (XR) terminal access; Twelfth indication information, used for indicating whether 2-receiver XR terminal is allowed to perform intra-frequency reselection; Thirteenth indication information, used for indicating whether the first cell allows enhanced lightweight terminal access; Fourteenth indication information, used for indicating whether the first cell allows 1-receiver enhanced lightweight terminal access; Fifteenth indication information, used for indicating whether the first cell allows 2-receiver enhanced lightweight terminal access; Sixteenth indication information, used for indicating whether the time-frequency resource of the target uplink signal overlaps or does not overlap with the RACH resource of the first cell; Seventeenth indication information, used for indicating whether the time-frequency resource of the target uplink signal overlaps or does not overlap with the RACH resource used for system information request of the first cell; Eighteenth indication information, used for indicating whether the time-frequency resource of the target uplink signal overlaps or does not overlap with the additional RACH resource of the first cell.

26. The method of any one of claims 22-25, wherein, The method further comprises: The network-side device receives a target uplink signal from the UE, the target uplink signal being used for requesting adjustment of a downlink signal or channel of a target cell; The network-side device sends a target uplink signal feedback to the UE or sends a physical downlink control channel (PDCCH) corresponding to the target uplink signal feedback to the UE; The preamble identifier of the target uplink signal is carried in the target uplink signal feedback.

27. The method of claim 26, wherein, The network-side device sends a target uplink signal feedback scrambled by a radio network temporary identifier (RNTI) calculated by a first formula to the UE; The network-side device sends a PDCCH corresponding to the target uplink signal feedback scrambled by the RNTI to the UE; The first formula is a newly defined random access radio network temporary identifier (RA-RNTI) formula, and the first formula is related to the identifier of the first cell associated with the first configuration information. The target uplink signal feedback indicates at least one of the following: Not responding to the request of the target uplink signal; 28. The method of claim 26 or 27, wherein, Responding to the request of the target uplink signal; The identifier of the cell responding to the request of the target uplink signal; The UE feature associated with the target uplink signal feedback; Whether the first cell associated with the first configuration information allows access of a UE with a specific feature; Whether the first cell associated with the first configuration information allows intra-frequency reselection of a lightweight terminal; Whether the first cell associated with the first configuration information allows 1-receiver lightweight terminal access; Whether the first cell associated with the first configuration information allows 2-receiver lightweight terminal access; ​ ​ whether the first cell associated with the first configuration information allows a half-duplex frequency-division duplexing (HD-FDD) light terminal to access; whether the first cell associated with the first configuration information allows a UE supporting a specific feature to access, the specific feature including at least one of a small data transmission (SDT) and a multicast service (MBS); whether the first cell associated with the first configuration information allows an air-ground connection; whether the first cell associated with the first configuration information allows a UE supporting a nes-CellDTX-DRX feature to access; whether the first cell associated with the first configuration information allows an enhanced light UE to perform an intra-frequency reselection; whether the first cell associated with the first configuration information allows a fixed very small aperture terminal (VSAT) to access; whether the first cell associated with the first configuration information allows a mobile VSAT to access; whether the first cell associated with the first configuration information allows a 2-receiver (2RX) extended reality (XR) terminal to access; whether the 2RX XR terminal is allowed to perform an intra-frequency reselection; whether the first cell associated with the first configuration information allows an enhanced light terminal to access; whether the first cell associated with the first configuration information allows an enhanced light 1-receiver (1RX) terminal to access; 29. The method of any one of claims 22-28, wherein, whether the first cell associated with the first configuration information allows an enhanced light 2RX terminal to access. a time difference between a plurality of first cells associated with the first configuration information is less than a first threshold, the first threshold being determined based on a guard period (GP); a subcarrier spacing (SCS) of the GP is determined based on at least one of the following: a SCS of a serving cell of the UE; a SCS of a time reference cell in which the UE transmits the target uplink signal; a SCS of a cell in which the UE acquires the first configuration; a maximum SCS of the first cells associated with the first configuration information; 30. An uplink signal transmitting apparatus, characterized by comprising: a minimum SCS of the first cells associated with the first configuration information. The apparatus comprises a sending module. The sending module is configured to send a target uplink signal based on a UE feature and the first configuration information.

31. The apparatus of claim 30, wherein, The first configuration information corresponds to at least one UE feature, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature; the target uplink signal is used to request an adjustment of a downlink signal or channel of a target cell. The apparatus further comprises a processing module. The processing module is configured to listen to a target uplink signal feedback scrambled by a radio network temporary identifier (RNTI) calculated by a first formula, or a physical downlink control channel (PDCCH) corresponding to the target uplink signal feedback scrambled by the RNTI.

32. The apparatus of claim 30 or 31, wherein, The first formula is a newly defined random access RNTI (RA-RNTI) formula, and the first formula is related to an identity of a first cell associated with the first configuration information. The processing module is configured to: in a case where the target uplink signal feedback is listened to, determine, based on the target uplink signal feedback, whether a cell responding to the target uplink signal is the target cell; 33. The apparatus of any one of claims 30-32, wherein, if the cell is not the target cell, re-determine a condition for sending the target uplink signal, or send the target uplink signal again. The processing module is configured to: If the target uplink signal feedback is monitored and the preamble identifier of the target uplink signal is carried in the target uplink signal feedback, it is confirmed that the target uplink signal request is successful.

34. The apparatus of any one of claims 30-33, wherein, The first configuration information is used to indicate the target time period; the processing module is used to rejudge the condition of sending the target uplink signal or resend the target uplink signal if the target uplink signal feedback is not monitored in the target time period.

35. A resource configuration apparatus, comprising: The apparatus comprises a sending module; The sending module is used to send first configuration information to a user equipment (UE); The first configuration information corresponds to at least one UE type, or at least one target uplink signal resource indicated by the first configuration information corresponds to at least one UE feature.

36. The device of claim 35, wherein, The apparatus comprises a receiving module; The receiving module is used to receive a target uplink signal from the UE, and the target uplink signal is used to request adjustment of a downlink signal or channel of a target cell; The sending module is further used to send target uplink signal feedback to the UE or send a physical downlink control channel (PDCCH) corresponding to the target uplink signal feedback to the UE; The preamble identifier of the target uplink signal is carried in the target uplink signal feedback.

37. The device of claim 37, wherein, The sending module is specifically used to send target uplink signal feedback scrambled by a radio network temporary identifier (RNTI) calculated by a first formula to the UE; The sending module is specifically used to send a PDCCH corresponding to the target uplink signal feedback scrambled by the RNTI to the UE; The first formula is a newly defined random access radio network temporary identifier (RA-RNTI) formula, and the first formula is related to the identifier of a first cell associated with the first configuration information.

38. A terminal, characterized by A processor and a memory are included, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the uplink signal sending method in any one of claims 1 to 21.

39. A network-side device, comprising: A processor and a memory are included, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the resource configuration method in any one of claims 22 to 29.

40. A readable storage medium characterized by, The readable storage medium stores programs or instructions, and the programs or instructions are executed by the processor to implement the uplink signal sending method in any one of claims 1 to 21 or implement the steps of the resource configuration method in any one of claims 22 to 29.

Images