Communication method, apparatus, device, and readable storage medium

Abstract

The application discloses a communication method, device, equipment and readable storage medium, and belongs to the technical field of communication. The method comprises the following steps: a terminal sends a first uplink transmission, wherein the first uplink transmission is used for requesting one of the following: system information of a first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission; wherein the system information of the first cell comprises any one of first system information and second system information, and the first system information is a subset of the second system information.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a communication method, apparatus, device, and readable storage medium. Background Technology

[0002] When a terminal sends an Uplink Wake-Up Signal (UL-WUS) to request the transmission of System Information Block (SIB) 1, if the base station successfully responds, it will send the complete SIB1. However, SIB1 contains many configuration parameters that the terminal does not need. For the network side, sending these unnecessary parameters results in significant signaling overhead. Furthermore, for terminals with small data to transmit, it is necessary to first send an UL-WUS request to send SIB1, and after receiving SIB1, send Message 1 (Msg1) to initiate RACH-based SDT. For the terminal, this requires sending both UL-WUS and Msg1 separately, resulting in significant signaling overhead. Summary of the Invention

[0003] This application provides a communication method, apparatus, device, and readable storage medium to address the problem of reducing high signaling overhead.

[0004] Firstly, a communication method is provided, including:

[0005] The terminal sends a first uplink transmission, which is used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission;

[0006] The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

[0007] Secondly, a communication method is provided, including:

[0008] The network-side device receives a first uplink transmission sent by the terminal, the first uplink transmission being used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission;

[0009] The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

[0010] Thirdly, a communication device is provided, comprising: a first transmitting unit;

[0011] The first sending unit is configured to send a first uplink transmission, the first uplink transmission being configured to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission;

[0012] The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

[0013] Fourthly, a communication device is provided for use in network-side equipment, comprising: a second transceiver unit;

[0014] The second transceiver unit is used to receive a first uplink transmission sent by the terminal, the first uplink transmission being used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission;

[0015] The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

[0016] Fifthly, a communication device is provided, the 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 or second aspect.

[0017] In a sixth aspect, a terminal is provided, the 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.

[0018] Fifthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send a first uplink transmission, the first uplink transmission being used to request one of the following: system information of a first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission; wherein the system information of the first cell includes any one of first system information and second system information, the first system information being a subset of the second system information.

[0019] In a sixth aspect, a network-side device is provided, the 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.

[0020] In a seventh aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first uplink transmission sent by a terminal, the first uplink transmission being used to request one of the following: system information of a first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission; wherein the system information of the first cell includes any one of first system information and second system information, the first system information being a subset of the second system information.

[0021] Eighthly, 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.

[0022] A ninth aspect provides a wireless communication system, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second aspect.

[0023] In a tenth 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 steps of the method as described in the first or second aspect.

[0024] Eleventhly, a computer program / program product is provided, the computer program or program product being stored in a storage medium, the computer program or program product being executed by at least one processor to perform the steps of the method as described in the first or second aspect.

[0025] In this embodiment, the terminal can request the network side to send system information of the first cell. The system information of the first cell includes either first system information or second system information, where the first system information is a subset of the second system information. This reduces the network side's overhead in sending system information by reducing the transmission of unnecessary parameters. Furthermore, the terminal can simultaneously request the network side to send the system information of the first cell, as well as message 2 or message B, reducing the signaling interaction process between the terminal and the network side. This simplifies the signaling process, reduces data transmission latency, and also reduces the signaling overhead between the terminal and the network side. Additionally, the terminal can simultaneously request the system information of the first cell and small data transmission. After receiving the system information of the first cell, the terminal does not need to send signaling to request the SDT (Signaling Delegated Data Transmission) process, further reducing the signaling interaction process between the terminal and the network side. This simplifies the signaling process, reduces data transmission latency, and also reduces the signaling overhead between the terminal and the network side. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of a communication system provided in an embodiment of this application;

[0027] Figure 2 This is a flowchart of a communication method provided in an embodiment of this application;

[0028] Figure 3 This is a flowchart of another communication method provided in an embodiment of this application;

[0029] Figure 4 This is a flowchart of the combination of RACH-based SDT and UL-WUS in Example 3;

[0030] Figure 5 This is a schematic diagram of the terminal sending Msg3 in Embodiment 4;

[0031] Figure 6 This is a structural diagram of a communication device provided in an embodiment of this application;

[0032] Figure 7 This is a structural diagram of another communication device provided in an embodiment of this application;

[0033] Figure 8 This is a structural diagram of a communication device provided in an embodiment of this application;

[0034] Figure 9 This is a structural diagram of a terminal provided in an embodiment of this application;

[0035] Figure 10 This is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

[0036] 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.

[0037] 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.

[0038] 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.

[0039] It is worth noting that the technology described in this application is 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, such as Non-Terrestrial Network (NTN) systems, Vehicle-to-Everything (V2X), Internet of Vehicles (IoV), Machine-Type Communications (MTC), Internet of Things (IoT), Machine-to-Machine (M2M), or future mobile communication systems. As a possible application scenario, NTN systems may include satellite systems. Based on satellite altitude, i.e., satellite orbital altitude, satellites can be classified into highly elliptical orbit (HEO) satellites, geosynchronous earth orbit (GEO) satellites, medium earth orbit (MEO) satellites, and low earth orbit (LEO) satellites. In addition, NTN systems may also include non-terrestrial network-side equipment (or airborne network-side equipment) such as High Altitude Platform Station (HAPS) communication systems. The non-terrestrial network-side equipment involved in this application is not limited to the examples mentioned above.

[0040] The terms "system" and "network" used in the embodiments of this application are often used interchangeably, and the described technologies can be used with respect to the systems and radio technologies mentioned above, as well as other systems and radio technologies. The following description describes a New Radio (NR) system 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) systems.th Generation 6G communication system.

[0041] To facilitate understanding of the embodiments of this application, the following technical points are introduced first:

[0042] 1) Regarding System Information (SI) and SIB1:

[0043] In 5G New Radio (NR), system information can be divided into three categories: Minimum System Information (MSI), Remaining Minimum System Information (RMSI), and Other System Information (OSI). These three categories can be further divided into one Master Information Block (MIB) and nine System Information Blocks (SIBs). The MIB is transmitted via the Broadcast Channel (BCH) and the Physical Broadcast Channel (PBCH), while the SIBs are transmitted via the Downlink Shared Channel (DL-SCH) and the Physical Downlink Shared Channel (PDSCH). The RMSI includes SIB1, and the OSI includes SIB2 through SIB9. Both the MIB and SIB1 have their own Radio Resource Control (RRC) messages.

[0044] SIB1 contains essential information for the terminal to camp on within the cell (e.g., cell selection information, Public Land Mobile Network (PLMN), Tracking Area Code (TAC), cell identifier, Radio Access Network (RAN) notification information, system information scheduling information for OSI, and serving cell information). SIB1 is transmitted via DL-SCH and PDSCH. Its change period is 160 milliseconds (ms), and it can be retransmitted within 160ms, with a variable retransmission period. The default retransmission period for SIB1 is 20ms, but the actual retransmission time depends on the network implementation. For SSB and Control Resource Set (CORESET) multiplexing mode 1 (pattern 1), the SIB1 retransmission period is 20ms; for SSB and CORESET multiplexing modes 2 / 3 (pattern 2 / 3), the SIB1 retransmission period is consistent with the SSB period. The PDSCH channel where SIB1 is located is scheduled using Downlink Control Information (DCI) format 1_0 scrambled with System Information Radio Network Temporary Identifier (SI-RNTI).

[0045] 2) Regarding Small Data Transmission (SDT):

[0046] Small data transmission is a process that allows non-connected terminals (e.g., idle and inactive) to transmit data or signaling simultaneously without transitioning to RRC connected state (RRC_CONNECTED), thus avoiding excessive signaling overhead caused by RRC state transitions and RRC connection establishment.

[0047] The key feature of the small data transmission scheme is that the terminal's current Data Radio Bearer (DRB) is in a suspended state, rather than a released state. Therefore, before sending a Resume Request message, the terminal can restore the DRB and then use RRC signaling to carry the small data. At this point, it can transmit data on the DRB, just like an RRC_CONNECTED terminal. This avoids state transitions and achieves efficient small data transmission with minimal signaling overhead.

[0048] The data to be transmitted in small data transfers is carried on a dedicated traffic channel (DTCH) and multiplexed with an uplink RRC connection resume request message before transmission. Similarly, if there is a reply downlink message, it can also be carried on the DTCH and multiplexed with a downlink RRC connection release message before transmission. Because small data transfers use DRB transmission, necessary security protections can be provided for the data, such as data encryption and integrity protection.

[0049] Small data is transmitted on the Physical Uplink Shared Channel (PUSCH) in message 3 (Msg3) during the 4-step random access (RACH) process. Small data can also be transmitted on the PUSCH in message A (MsgA) during the 2-step random access (RACH) process, or on PUSCH resources scheduled by the Configured Grant (CG) configured in the RRC inactive state. Small data transmission during the 2-step and 4-step RACH processes is referred to as RACH-based small data transmission, and small data transmission on PUSCH scheduled by the Configured Grant is referred to as Configured Grant-based small data transmission. SDT resources can be configured for RACH and Configured Grant on the Bandwidth Part (BWP). The RACH and Configured Grant resources of the SDT can be configured on the Normal Uplink (NUL) or Supplementary Uplink (SUL) carriers. When an RRC Release with a pause indication is received, the CG resources of the SDT are only valid within the UE's primary cell (PCell). The configured authorized resources are associated with one or more Synchronization Signal and PBCH blocks (SSBs). For RACH, the network can configure 2-step or 4-step random access resources for Mobile Originated SDT (MO-SDT) initiated by the mobile terminal. If a Mobile Terminated SDT (MT-SDT) procedure is initiated via RACH, the UE can only use RACH resources not configured for the SDT. Contention-Free Random Access (CFRA) does not support SDT on RACH.

[0050] 3) Regarding the triggering conditions and process of SDT transmission:

[0051] Small data transfers can be initiated by the terminal (i.e., MO-SDT) or by the network (i.e., MT-SDT).

[0052] A) Conditions for starting SDT:

[0053] Scenario 1: Recovery process initiated by the upper layer (i.e., MO-SDT):

[0054] One of the following conditions must be met:

[0055] 1) SDT configuration is configured, and SIB1 contains SDT common configuration (SDT-ConfigCommon);

[0056] 2) All uplink data to be transmitted has been mapped to the resource blocks (RBs) configured for SDT;

[0057] 3) For terminals with reduced capabilities (RedCapUE), when the specific initial downlink BWP of RedCap does not contain a cell-defined SSB (CD-SSB), it is necessary to configure the capability reduction initial BWP-SDT (ncd-SSB-RedCapInitialBWP-SDT) for non-cell-defined SSBs.

[0058] 4) The amount of uplink data to be sent in all RBs configured for SDT is less than or equal to a preset threshold;

[0059] 5) The reference signal receiving power (RSRP) for downlink path loss is higher than a preset threshold.

[0060] Scenario 2: Responding to RAN paging to initiate a recovery procedure (i.e., MT-SDT):

[0061] One of the following conditions must be met:

[0062] 1) The paging message contains an MT-SDT indication of the full RNTI for the terminal;

[0063] 2) The RSRP reference for downlink path loss is higher than the preset threshold.

[0064] B) Selection between Configured Grant Small Data Transmission (CG-SDT) and Random Access Small Data Transmission (RA-SDT).

[0065] The terminal selects between CG-SDT and RA-SDT according to the following rules:

[0066] If CG-SDT resources are configured, the Tracking Area (TA) is valid, and there is at least one SSB for CG-SDT (whose SS-RSRP is higher than the RSRP threshold): then CG-SDT is executed.

[0067] Otherwise, if RA-SDT resources are available, then RA-SDT is executed;

[0068] Otherwise, perform a conventional RA to restore the RRC connection.

[0069] 4) Regarding Msg3 transmission requirements:

[0070] There must be at least a certain time interval between the sending of Msg3 and the receiving of message 2 (Msg2). The time interval can be determined based on the Random Access Response (RAR) decoding time or the uplink preparation time.

[0071] The system information, SIB1, or SIBX mentioned in this application can be collectively referred to as SIB. Among them, SIB1 is an example of SIB; SIB can include one or more of SIB1-SIBX, or a combination of more of SIB1-SIBX, where the value of X can be any one from 1 to 10 (or higher); the above system information can be understood as system message.

[0072] The uplink wake-up signal (UL WUS) mentioned in this application can be understood as an on-demand signal request, or as a Physical Random Access Channel (PRACH) transmission, or as a preamble transmission, or as Msg1 transmission.

[0073] The Random Access Occasion (RO) involved in this application can be understood as the time-frequency resource or timing for sending the first uplink transmission. The preamble involved in this application can be understood as the first uplink transmission. The feedback information of the first uplink transmission can be understood as the random access response, or it can also be understood as the random access response for UL-WUS.

[0074] The terms UE feature, UE type, or UE category used in this application have similar meanings, all referring to UEs that support certain technical characteristics or different UE categories. These may include SDT, SUL, Reduced Capability (Redcap), Enhanced Redcap (eRedcap), Low-Power Wide-Area (LPWA), Enhanced Mobile Broadband (eMBB), NR in Unlicensed Spectrum (NRU), Extended Reality (XR), Internet of Things (IoT), Network Energy Saving (NES), Cell Discontinuous Reception (cell DRX), Discontinuous Transmission Cell (DTX), or Connected Discontinuous Reception (C-DRX), etc.

[0075] The UE type involved in this application can be understood as the type, characteristics, or profile of a "device," which includes terminal or network devices.

[0076] Figure 1 This 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.

[0077] 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 (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, 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 the embodiments of this application.

[0078] Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, radio access network unit, or satellite. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), 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.

[0079] 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.

[0080] 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).

[0081] The communication methods, apparatus, devices, and readable storage media provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0082] See Figure 2 This application provides a communication method applied to a terminal, the specific steps of which include:

[0083] Step 21: The terminal sends a first uplink transmission, which is used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission;

[0084] The system information of the first cell includes either first system information or second system information, wherein the first system information is a subset of the second system information.

[0085] In one implementation, the first uplink transmission is used to request system information of the first cell. For example, the first uplink transmission may request first system information or request second system information, thus reducing the network side's overhead in sending unnecessary parameters.

[0086] In another implementation, the first uplink transmission is used to request system information of the first cell and request random access, i.e., to request a random access message, which includes message 2 (i.e., Msg2) or message B (i.e., MsgB), and then continue the subsequent random access procedure, such as the terminal sending message 3. On the one hand, since the first uplink transmission can request the first system information or the second system information, the network side can reduce the transmission of some unnecessary parameters, thereby reducing the overhead of the network side in sending system information. On the other hand, the terminal requests message 2 or message B at the same time as requesting the system information of the first cell, so that after receiving message 2 or message B, the terminal can directly continue the subsequent random access procedure, reducing the signaling interaction process between the terminal and the network side. This not only simplifies the signaling process and reduces data transmission latency, but also reduces the signaling overhead between the terminal and the network side equipment. In another implementation, the first uplink transmission is used to request system information and small data transmission from the first cell. For example, after the terminal receives the system information and message 2 (i.e., Msg2) or message B from the first cell, if the terminal is allowed to access the first cell, the terminal sends Msg3 and carries small data through Msg3. On the one hand, since the first uplink transmission can request the first system information or the second system information, the network side can reduce the transmission of some unnecessary parameters, thereby reducing the overhead of the network side in sending system information. On the other hand, the terminal requests small data transmission at the same time as requesting the system information of the first cell. After receiving the system information of the first cell, the terminal does not need to send signaling for requesting the SDT procedure again, thereby reducing the signaling interaction process between the terminal and the network side. This not only simplifies the signaling process and reduces data transmission latency, but also reduces the signaling overhead of the terminal and network side equipment.

[0087] Optionally, the first cell may be a cell that provides system information non-periodically, or the first cell may be a cell that allows terminals to request system information on demand. That is, the network-side device associated with the first cell may send the system information of the first cell to the terminal non-periodically, or the network-side device associated with the first cell may send the system information of the first cell to the terminal according to the terminal's on-demand request.

[0088] Optionally, the first uplink transmission includes, but is not limited to, an uplink wake-up signal (ULWUS).

[0089] Optionally, the system information of the first cell includes, but is not limited to, on-demand SIBX (OD-SIBX).

[0090] Optionally, the first system information includes, but is not limited to, the first OD-SIBX.

[0091] Optionally, the second system information includes, but is not limited to, the second OD-SIBX (or broadcast OD-SIBX).

[0092] Optionally, the value of X can be any one from 1 to 10 (or higher), for example X = 1, but it is not limited to this.

[0093] In this embodiment, the terminal can request the network side to send different system information, which can reduce the overhead of the network side sending system information. On the other hand, the terminal can simultaneously request the network side to send system information and random access response message, which reduces the overhead of the UE sending a random access request (e.g., Msg1) again to obtain the random access response message.

[0094] In one embodiment of this application, the first system information includes configurations corresponding to some terminal features or some terminal types; or, the first system information does not include configurations corresponding to some optional terminal features or terminal types.

[0095] In this embodiment, the first system information can be a minimal set of configurations corresponding to terminal features or terminal types, which can reduce the overhead of sending system information.

[0096] For example, the protocol stipulates that the first system information does not contain parameters related to redcap or LPWA. For redcap UE or LPWA UE, it is necessary to send UL-WUS based on the WUS resources associated with the second system information to request the second system information to obtain the complete parameter configuration related to redcap or LPWA. The second system information is a complete SIB1, which contains the parameter set corresponding to all UE features.

[0097] For example, WUS resource 1 does not distinguish between requests for first system information and second system information. That is, based on the UL-WUS sent by WUS resource 1, the UE can only determine whether the requested information is first or second system information through the UL-WUS feedback or the system information of the first cell. After the redcap UE sends the UL-WUS, it receives the system information of the first cell. The system information of the first cell or the UL-WUS feedback indicates whether the system information of the first cell is first or second system information, or the system information of the first cell indicates which parameter sets corresponding to UE features are included in the system information of the first cell / or which parameter sets are included. If the system information of the first cell indicates that it is first system information and does not contain configuration parameters related to the redcap feature, the redcap UE can send the UL-WUS again to request the second system information based on WUS resource 2, which is dedicated to requesting the second system information, to obtain the complete SIB1 configuration. If the system information of the first cell indicates that it is a second system information and the second system information contains configurations related to the redcap UE, then the redcap UE considers that it can access the first cell; if the second system information does not contain configurations related to the redcap UE, then the redcap UE considers that it cannot access the first cell.

[0098] In one embodiment of this application, the second system information includes configurations corresponding to all terminal features or terminal types.

[0099] In this embodiment, the second system information may be a complete set of configurations corresponding to terminal features or terminal types.

[0100] In one embodiment of this application, before the terminal sends the first uplink transmission, the method further includes:

[0101] The terminal receives first configuration information;

[0102] The first configuration information includes at least one of the following:

[0103] 1) First information, which indicates whether the first cell allows or disallows the request for the first system information;

[0104] For example, the first information can be an indicator bit, where an indicator bit of 1 indicates that the first cell allows the terminal to request the first system information, while an indicator bit of 0 indicates that the first cell does not allow the terminal to request the first system information.

[0105] 2) The terminal characteristics or terminal type associated with the first system information;

[0106] Optionally, the terminal features or terminal types associated with the first system information refer to the configurations corresponding to the terminal features or terminal types included in the first system information.

[0107] 3) Allows the terminal characteristics or terminal type that request the information of the first system;

[0108] For example, if the terminal characteristic allowed to request the first system information is terminal characteristic A, or the terminal type allowed to request the first system information is terminal type B, then only terminals with terminal characteristic A or terminal type B are allowed to request the first system information, while other terminals can only request the second system information.

[0109] 4) SDT Configuration (SDT-Config);

[0110] Optionally, the SDT configuration may include the SDT configuration of Redcap UE.

[0111] Optional, SDT configuration includes: SDT configuration for Redcap UE (e.g., ncd-SSB-RedCapInitialBWP-SDT);

[0112] For RedCap-enabled UEs, configuration is required when the initial RedCap-specific BWP does not contain a CD-SSB.

[0113] 5) First RNTI, the first RNTI is used to scramble the physical downlink control channel (PDCCH) of the first system information;

[0114] 6) Second RNTI, the second RNTI is used to scramble the PDCCH of the second system information;

[0115] Optionally, the second RNTI includes, but is not limited to, SI-RNTI.

[0116] In this embodiment, the PDCCH for scheduling the first system information and the second system information is scrambled by different RNTIs. When the UE requests the first system information, the first RNTI is used to detect the corresponding PDCCH. At this time, the first system information may not contain information indicating whether the system information of the first cell is the first system information or the second system information, because the first system information is scrambled by the first RNTI and will not affect the UE that expects to receive the second system information.

[0117] 7) At least one cell identifier of the first cell;

[0118] 8) At least one NR Cell Global Identifier (NCGI) of the first cell;

[0119] 9) Second information, the second information indicating whether at least one of the first cells and the second cell belong to or do not belong to the same TA;

[0120] 10) Third information, the third information indicating that at least one of the first cell and the second cell belong to or do not belong to the same Radio Access Network Notification Area (RNA);

[0121] 11) Configuration information for one or more of the first uplink transmissions;

[0122] The first configuration information is sent by the network-side device associated with the first cell.

[0123] In some embodiments, the second cell and the first cell can be the same cell, that is, the terminal obtains the first uplink transmission configuration in the first cell, requests the system information of the first cell, and message 2 or message B.

[0124] Optionally, the configuration information for the first uplink transmission includes at least one of the following:

[0125] 1) First uplink transmission configuration identifier;

[0126] 2) The first cell identifier associated with the first uplink transmission configuration;

[0127] 3) Eighth information, which indicates whether the first cell associated with the first uplink transmission configuration belongs to the same TA as the second cell;

[0128] 4) Ninth information, which indicates whether the first cell associated with the first uplink transmission configuration belongs to the same RNA as the second cell;

[0129] 5) Decision threshold for 2-step or 4-step random access;

[0130] 6) MsgA Prach configuration;

[0131] 7) MsgA PUSCH configuration;

[0132] Optionally, the MsgA PUSCH configuration can be a fixed offset relative to the preamble or the first uplink transmission, such as N symbols; optionally, N can be a first-level SSB indication or a protocol convention.

[0133] 8) Msg2 or MsgB receiver configuration;

[0134] Optionally, the Msg2 or MsgB receive configuration includes at least one of the following: listening window duration, listening start position, listening end position, search space configuration, and control resource set configuration.

[0135] 9) Meet the minimum reference signal threshold value for the first uplink transmission, for example, the SSB reference signal receive power threshold (rsrp-ThresholdSSB);

[0136] 10) Root sequence identifier, for example, PRACH root sequence index (PRACH-RootSequenceIndex);

[0137] 11) First uplink transmission subcarrier spacing, for example, Msg1 subcarrier spacing;

[0138] 12) Restricted Set Configuration (restrictedSetConfig);

[0139] 13) Uplink frequency band information, such as the frequency band list;

[0140] 14) Absolute Frequency Point A;

[0141] 15) Carrier offset (offsetToCarrier);

[0142] 16) Maximum transmit power (p-Max);

[0143] 17) Uplink subcarrier spacing (UL Subcarrier Spacing);

[0144] 18) SSB power (SS-PBCH-Block Power);

[0145] 19) Beam identifiers transmitted by the SSB, such as SSB positionInBurst;

[0146] 20) Time Division Duplex (TDD) configuration, for example, TDD uplink / downlink common configuration (tdd-UL-DL-Configuration Common);

[0147] 21) PRACH configuration identifier, for example, PRACH configuration index;

[0148] 22) The number of frequency domain ROs, for example, determined based on Msg1-FDM parameters;

[0149] 23) RO start position, for example, determined based on the Msg1 frequency start position (Msg1-Frequency Start);

[0150] 24) Zero Correlation Zone Configuration;

[0151] 25) Preamble Received Target Power;

[0152] 26) Maximum number of preamble transmissions (preamble TransMax);

[0153] 27) Power Ramping Step;

[0154] 28) RAR listener window, for example, random access response window (RA-Response Window);

[0155] 29) Configuration of the PDCCH for receiving and scheduling system information of the first cell, for example, configuration of type 0 PDCCH;

[0156] 30) Receive the configuration of the PDCCH for the scheduled RAR, for example, the configuration of Type 1 PDCCH;

[0157] 31) The number of SSBs associated with each RO (SSB-perRACH-Occasion);

[0158] 32) System information request cycle for the first cell;

[0159] 33) Preamble sequence identifier, for example, random access preamble start index (RA-PreambleStartIndex);

[0160] 34) Association periods, for example, the random access association period index (RA – Association Period Index);

[0161] 35) RO mask identifier, for example, Random Access-Synchronization Block Occasion Mask Index (RA-ssb-OccasionMask Index);

[0162] 36) Search Space Zero;

[0163] 37) Control Resource Set Zero;

[0164] 38) RAR Search Space;

[0165] 39) TA value, for example, TA offset parameter (n-TimingAdvanceOffset);

[0166] 40) SSB cycle, for example, the serving cell SSB cycle (SSB - PeriodicityServingCell);

[0167] 41) Subcarrier offset, for example, SSB subcarrier offset parameter (k-SSB)

[0168] 42) System information transmission duration of the first cell;

[0169] 43) The offset of the system information transmission start position of the first cell relative to the reference point, for example, expressed as the time window offset (offsetToTimeWindow);

[0170] 44) Point A frequency offset (offsetToPointA);

[0171] 45) Number of repetitions;

[0172] 46) The type of the first uplink transmission, for example, the type of the first uplink transmission includes, but is not limited to, at least one of the following: Msg1, Msg3, MsgA, preamble;

[0173] 47) Uplink Bandwidth Part (BWP) Configuration.

[0174] In one embodiment of this application, at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the first system information, and at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the second system information.

[0175] For example, there are two sets of first uplink transmission configurations, namely two sets of WUS configurations. One WUS configuration is configured with WUS resources for requesting first system information, that is, associated with the first system information; the other WUS configuration is configured with WUS resources for requesting second system information, that is, associated with the second system information.

[0176] In one embodiment of this application, the value of the first parameter in the configuration information of the first uplink transmission includes at least a first value and a second value. The first value is associated with the first system information, and the second value is associated with the second system information. Here, "the first value is associated with the first system information" means that the network side can determine that the terminal is requesting the first system information based on the first value. "The second value is associated with the second system information" means that the network side can determine that the terminal is requesting the second system information based on the second value.

[0177] For example, the carrier offset values ​​in the configuration information of the first uplink transmission include A1 and A2, where A1 is associated with the first system information and A2 is associated with the first system information.

[0178] For example, the preamble sequence identifier in the configuration information of the first uplink transmission includes values ​​B1 and B2, where B1 is associated with the first system information, and B2 is associated with the first system information. That is, if the preamble sequence identifier sent by the UE is B1, it indicates that the UE is requesting the first system information; if the preamble sequence identifier sent by the UE is B2, it indicates that the UE is requesting the second system information.

[0179] For example, a preamble sequence or RO resource can correspond to a request for first system information or a request for second system information, respectively.

[0180] In one embodiment of this application, after step 11, the method further includes:

[0181] The terminal receives the feedback information from the first uplink transmission;

[0182] The feedback information includes at least one of the following:

[0183] 1) The identifier of the preamble sequence corresponding to the first uplink transmission;

[0184] When the UE receives the preamble sequence identifier corresponding to the first uplink transmission, the UE considers the first uplink transmission to have been successfully sent, and the network side responds to the UE's wake-up request.

[0185] 2) Fourth information, wherein the fourth information indicates that the system information of the first cell is the first system information or the second system information;

[0186] In this embodiment, the first uplink transmission may not indicate whether the terminal is requesting the first system information or the second system information, but the feedback information indicates that the system information of the first cell sent by the network-side device is the first system information or the second system information.

[0187] 3) First RNTI, the first RNTI is used to scramble the PDCCH of the first system information;

[0188] 4) The transmission duration of system information in the first cell;

[0189] 5) Beam identifier associated with the system information of the first cell.

[0190] Optionally, the feedback information of the first uplink transmission can also be referred to as the UL-WUS feedback information.

[0191] In one embodiment of this application, the system information of the first cell indicates at least one of the following:

[0192] 1) The system information of the first cell is either the first system information or the second system information;

[0193] In this embodiment, the system information of the first cell can indicate whether the network side responds with first system information or second system information.

[0194] 2) Terminal characteristics associated with the system information of the first cell;

[0195] For example, "the terminal features associated with the system information of the first cell" means that the configuration corresponding to the terminal feature is included in the first system information.

[0196] 3) The terminal type associated with the system information of the first cell.

[0197] For example, "the terminal type associated with the system information of the first cell" means that the configuration corresponding to the terminal type is included in the first system information.

[0198] In one embodiment of this application, the first uplink transmission is used to request system information of a first cell, and the method further includes:

[0199] The terminal receives system information from the first cell.

[0200] In one embodiment of this application, the first uplink transmission is used to request system information of the first cell and message 2 or message B, or the first uplink transmission is used to request system information of the first cell and small data transmission, and the method further includes:

[0201] The terminal receives system information from the first cell, as well as message 2 or message B.

[0202] In one embodiment of this application, the terminal receives system information from the first cell, and message 2 or message B, including:

[0203] The terminal receives system information from the first cell;

[0204] The terminal receives message 2 or message B based on the system information of the first cell;

[0205] Wherein, the terminal characteristics indicated by the system information of the first cell include the terminal characteristics of the terminal, or the terminal type indicated by the system information of the first cell includes the terminal type of the terminal.

[0206] In one embodiment of this application, the method further includes:

[0207] The terminal terminates the SDT process based on the system information of the first cell;

[0208] Wherein, the terminal characteristics indicated by the system information of the first cell do not include the terminal characteristics of the terminal, or the terminal type indicated by the system information of the first cell does not include the terminal type of the terminal.

[0209] It is understandable that in some implementations, the terminal sending the first uplink transmission can be equivalent to the terminal initiating the SDT procedure. Therefore, if the terminal does not allow access in the first cell, the terminal can terminate the SDT procedure.

[0210] In one embodiment of this application, the terminal sends a first uplink transmission, including:

[0211] If the first condition is met, the terminal sends the first uplink transmission;

[0212] The first condition includes at least one of the following:

[0213] 1) The first cell and the cell in which the terminal receives the first configuration information (such as the second cell mentioned above) belong to the same TA;

[0214] 2) The first cell and the cell in which the terminal receives the first configuration information (e.g., the second cell mentioned above belong to the same RNA);

[0215] 3) The conditions for the terminal to initiate small data transmission (MO-SDT) are met;

[0216] 4) The size of the uplink data packet to be transmitted is less than or equal to the first threshold.

[0217] It should be noted that the size of the first threshold is not limited in this embodiment.

[0218] In one embodiment of this application, after receiving message 2 or message B, the method further includes:

[0219] The terminal sends message 3 (i.e., Msg3). Optionally, message 3 may carry small amounts of data.

[0220] In one implementation, after receiving message 2, the terminal sends message 3, which carries small data.

[0221] In another embodiment, after receiving message B, the terminal sends message 3, which carries small data, while message B may carry uplink scheduling.

[0222] In this embodiment, after receiving message 2 or message B, the terminal does not need to send signaling to request the SDT procedure again, thereby reducing the signaling interaction process between the terminal and the network side. This not only simplifies the signaling process and reduces data transmission latency, but also reduces the signaling overhead of the terminal and network side devices.

[0223] In one embodiment of this application, the terminal sends message 3, including:

[0224] The terminal is only allowed to send message 3 after at least the Xth time unit after the first reference point, where X is greater than or equal to 0;

[0225] The first reference point includes at least one of the following:

[0226] 1) In the Yth time unit after receiving the last time unit of the PDSCH carrying the message 2, the value of Y is determined based on at least one of the preparation time of the message 3, the processing time of the message 2, and the processing time of the system information of the first cell, and Y is greater than or equal to 0.

[0227] 2) The end position of the first window, which is used to receive system information of the first cell;

[0228] 3) The starting position of the first window;

[0229] 4) The time unit in which type 0PDCCH is received;

[0230] 5) The time unit in which the system information of the first cell is received;

[0231] 6) Receive the time unit in which the PDSCH carrying message 2 is located;

[0232] 7) The end position of the second window, which is used to receive the message 2;

[0233] 8) The starting position of the second window;

[0234] 9) The time unit in which the first uplink transmission occurs.

[0235] Optionally, message 3 may carry small amounts of data.

[0236] Optionally, time units include, but are not limited to, symbols, slots, milliseconds (ms), frames, or subframes.

[0237] For scenarios combining RACH-based SDT and UL-WUS, where the UE sends UL-WUS, receives Msg2, and sends Msg3 (which includes SDT), the overhead of sending Msg1 is reduced compared to the existing technology where the terminal first receives SIB1 and then sends Msg1 to trigger SDT.

[0238] In one embodiment of this application, the method further includes:

[0239] The terminal assumes or defaults that the minimum time interval between the first time unit and the second time unit is greater than or equal to the first time interval.

[0240] The first time unit is the last time unit in which the PDSCH carrying message 2 is received;

[0241] The second time unit is the first time unit transmitted by the Physical Uplink Shared Channel (PUSCH) authorized and scheduled by message 2;

[0242] The first time interval is determined based on at least one of the preparation time of message 3, the processing time of message 2, and the processing time of system information of the first cell.

[0243] Optionally, the preparation time for message 3 is the length of N2 time units (e.g., symbols), corresponding to the PUSCH preparation time under UECapability1.

[0244] Optionally, the processing time of message 2 is the length of N1 time units (e.g., symbols), corresponding to the PDSCH processing time when additional PDSCH DM-RS is configured under UECapability1.

[0245] Optionally, the values ​​of N1 and N2 depend on the smaller of the subcarrier spacing (SCS) configurations of PDSCH and PUSCH.

[0246] Optionally, the processing time of the system information of the first cell may include the decoding time of the system information of the first cell.

[0247] In this embodiment, the terminal can request the network side to send system information of the first cell. The system information of the first cell includes either first system information or second system information, where the first system information is a subset of the second system information. This reduces the network side's overhead in sending system information by reducing the transmission of unnecessary parameters. Furthermore, the terminal can simultaneously request the network side to send the system information of the first cell, as well as message 2 or message B, reducing the signaling interaction process between the terminal and the network side. This simplifies the signaling process, reduces data transmission latency, and also reduces the signaling overhead between the terminal and the network side. Additionally, the terminal can simultaneously request the system information of the first cell and small data transmission. After receiving the system information of the first cell, the terminal does not need to send signaling to request the SDT (Signaling Delegated Data Transmission) process, further reducing the signaling interaction process between the terminal and the network side. This simplifies the signaling process, reduces data transmission latency, and also reduces the signaling overhead between the terminal and the network side.

[0248] See Figure 3 This application provides a communication method applied to a network-side device, the specific steps of which include:

[0249] Step 31: The network-side device receives a first uplink transmission sent by the terminal, the first uplink transmission being used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission;

[0250] The system information of the first cell includes either first system information or second system information, wherein the first system information is a subset of the second system information.

[0251] In one embodiment of this application, the first system information includes configurations corresponding to some terminal features or some terminal types, the first system information does not include configurations corresponding to some optional terminal features or terminal types, or, alternatively, the second system information includes configurations corresponding to all terminal features or all terminal types.

[0252] In one embodiment of this application, before the network-side device receives the first uplink transmission sent by the terminal, the method further includes:

[0253] The network-side device sends the first configuration information to the terminal through the second cell;

[0254] The first configuration information includes at least one of the following:

[0255] 1) First information, which indicates whether the first cell allows or disallows the request for the first system information;

[0256] 2) The terminal characteristics or terminal type associated with the first system information;

[0257] 3) Allows the terminal characteristics or terminal type that request the information of the first system;

[0258] 4) SDT configuration;

[0259] 5) First RNTI, the first RNTI is used to scramble the PDCCH of the first system information;

[0260] 6) Second RNTI, the second RNTI is used to scramble the PDCCH of the second system information;

[0261] 7) At least one cell identifier of the first cell;

[0262] 8) At least one NCGI of the first cell;

[0263] 9) Second information, the second information indicating whether at least one of the first cells and the second cell belong to or do not belong to the same TA;

[0264] 10) Third information, the third information indicating that at least one of the first cells and the second cell belong to or do not belong to the same RNA;

[0265] 11) Configuration information of one or more of the first uplink transmissions.

[0266] In one embodiment of this application, at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the first system information, and at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the second system information.

[0267] or,

[0268] The first parameter in the configuration information of the first uplink transmission includes at least a first value and a second value, wherein the first value is associated with the first system information and the second value is associated with the second system information.

[0269] In one embodiment of this application, after step 31, the method further includes:

[0270] The network-side device sends the feedback information of the first uplink transmission;

[0271] The feedback information includes at least one of the following:

[0272] 1) The identifier of the preamble sequence corresponding to the first uplink transmission;

[0273] 2) Fourth information, wherein the fourth information indicates that the system information of the first cell is the first system information or the second system information;

[0274] 3) First RNTI, the first RNTI is used to scramble the PDCCH of the first system information;

[0275] 4) The transmission duration of system information in the first cell;

[0276] 5) Beam identifier associated with the system information of the first cell.

[0277] In one embodiment of this application, the system information of the first cell indicates at least one of the following:

[0278] 1) The system information of the first cell is either the first system information or the second system information;

[0279] 2) Terminal characteristics associated with the system information of the first cell;

[0280] 3) The terminal type associated with the system information of the first cell.

[0281] In one embodiment of this application, the first uplink transmission is used to request system information of a first cell, and the method further includes:

[0282] The network-side device sends the system information of the first cell.

[0283] In this embodiment, the network-side device sends first system information or requests second system information, which reduces the amount of unnecessary parameters sent by the network side and thus reduces the overhead of sending system information.

[0284] In one embodiment of this application, the first uplink transmission is used to request system information of a first cell and message 2 or message B, and the method further includes:

[0285] The network-side device sends the system information of the first cell, as well as message 2 or message B.

[0286] In this embodiment, on the one hand, since the network-side device sends the first system information or requests the second system information, the network side can reduce the sending of some unnecessary parameters, thereby reducing the overhead of the network side sending system information. On the other hand, the terminal requests message 2 or message B at the same time as requesting the system information of the first cell. Thus, after sending message 2 or message B, the network-side device can directly continue the subsequent random access procedure, reducing the signaling interaction process between the terminal and the network side. This not only simplifies the signaling process and reduces data transmission latency, but also reduces the signaling overhead of the terminal and the network-side device.

[0287] In one embodiment of this application, the first uplink transmission is used to request system information and small data transmission from a first cell, and the method further includes:

[0288] The network-side device sends the system information of the first cell, as well as message 2 or message B;

[0289] The network-side device receives message 3 sent by the terminal, and message 3 carries small data.

[0290] In this embodiment, on the one hand, since the network-side device sends the first system information or requests the second system information, the network side can reduce the transmission of some unnecessary parameters, thereby reducing the overhead of the network side in sending system information. On the other hand, after the terminal receives the system information (such as SIB1) and message 2 of the first cell, if the terminal is allowed to access the first cell, the network-side device can receive Msg3 sent by the terminal. Msg3 carries small data, so the terminal does not need to send the signaling request for SDT procedure after receiving the system information of the first cell, thereby reducing the signaling interaction process between the terminal and the network side. This not only simplifies the signaling process and reduces data transmission latency, but also reduces the signaling overhead of the terminal and the network-side device.

[0291] The following describes the implementation method of this application, taking as an example that the first uplink transmission is UL-WUS, the first cell is an NES cell, the system information of the first cell is OD-SIB1, the first system information is the first OD-SIB1, and the second system information is the second OD-SIB1.

[0292] Example 1: The UE requests the first OD-SIB1 or the second OD-SIB1 as needed. The OD-SIB1 carries indication information to indicate the first OD-SIB1 or the second OD-SIB1.

[0293] In this embodiment, different UL-WUS requests are for different types of OD-SIB1. One type is the first OD-SIB1 (minimum set), which optionally carries fifth information indicating the UE features supported by the first cell that sent the fifth information (e.g., SDT or Redcap), or indicating which UE features' corresponding configurations are carried in the first OD-SIB1, such as SDT configuration or Redcap configuration. The second type is the second OD-SIB1 (complete set), which carries the configurations corresponding to all UE features. When the UE sends the corresponding UL-WUS, the network side sends the second OD-SIB1 based on the correspondence. The differentiation method can be to distinguish different UL-WUS by different RO or preamble intervals; or, the UL-WUS does not differentiate, but the RAR (UL-WUS feedback information) indicates whether the network side sends the first OD-SIB1 or the second OD-SIB1.

[0294] The process for the UE to receive OD-SIB1 in this embodiment is as follows:

[0295] Step 1: The UE receives the first configuration information;

[0296] Optionally, the first configuration information includes at least one of the following:

[0297] 1) First information, the first information indicating whether the NES cell allows or disallows the request for the first OD-SIB1;

[0298] 2) The UE feature or UE type associated with the first OD-SIB1;

[0299] That is, "UE feature or UE type associated with the first OD-SIB1" refers to the configurations corresponding to which UE features or UE types are included in the first OD-SIB1.

[0300] 3) The NES cell allows requests for the first OD-SIB1 UE feature or UE type;

[0301] That is, "the NES cell allows requests for the first OD-SIB1 UE feature or UE type" means that the NES cell only allows requests for the first OD-SIB1 if the UE feature or UE type is specified; otherwise, it can only request the second OD-SIB1.

[0302] 4) SDT configuration;

[0303] 5) First RNTI, the first RNTI is used to scramble the PDCCH of the first OD-SIB1;

[0304] 6) The second RNTI is used to scramble the PDCCH of the second OD-SIB1;

[0305] 7) The cell identifier of at least one NES cell;

[0306] That is, the WUS resource configured in the first configuration information is used to request the transmission of OD-SIB1 of which NES cell.

[0307] 8) NCGI of at least one NES cell;

[0308] That is, the NCGI of the NES cell associated with the first configuration information;

[0309] 9) Second information, the second information indicating that at least one NES cell and the second cell belong to the same TA, or indicating that at least one NES cell and the second cell do not belong to the same TA;

[0310] For example, the second information indicates whether at least one NES cell associated with the first cell belongs to the same TA as the second cell;

[0311] 10) Third information, the third information indicating that at least one NES cell and the second cell belong to the same RNA, or at least one NES cell and the transmitting first cell do not belong to the same RNA;

[0312] For example, the third information indicates whether the multiple NES cells associated with the first cell belong to the same RNA as the second cell;

[0313] 11) Configuration information for one or more UL-WUS systems;

[0314] The first configuration information is sent by the network-side device associated with the second cell.

[0315] Optionally, the UL-WUS configuration information includes at least one of the following:

[0316] 1) UL-WUS configuration identifier;

[0317] 2) The NES cell identifier associated with the UL-WUS configuration;

[0318] 3) The eighth information indicates whether the NES cell associated with the UL-WUS configuration belongs to the same TA as the second cell;

[0319] 4) Ninth Information: The ninth information indicates whether the NES cell associated with the UL-WUS configuration belongs to the same RNA as the second cell;

[0320] 5) Decision threshold for 2-step or 4-step random access;

[0321] 6) MsgA Prach configuration;

[0322] 7) MsgA PUSCH configuration;

[0323] 8) Msg2 or MsgB receiver configuration;

[0324] 9) Meet the minimum reference signal threshold value for UL-WUS transmission, for example, the SSB reference signal received power threshold (rsrp-ThresholdSSB);

[0325] 10) Root sequence identifier;

[0326] 11) UL-WUS subcarrier spacing;

[0327] 12) Restricted set configuration;

[0328] 13) Uplink frequency band information;

[0329] 14) Absolute frequency point A;

[0330] 15) Carrier offset;

[0331] 16) Maximum transmission power;

[0332] 17) Uplink subcarrier spacing;

[0333] 18) SSB power;

[0334] 19) Beam identifier transmitted by the SSB;

[0335] 20) TDD configuration, such as TDD uplink / downlink common configuration;

[0336] 21) PRACH configuration identifier;

[0337] 22) Number of frequency domain ROs;

[0338] 23) RO starting position;

[0339] 24) Zero-related domain configuration;

[0340] 25) Preamble target received power;

[0341] 26) Maximum number of times the preamble can be sent;

[0342] 27) Power boost step size;

[0343] 28) RAR listener window;

[0344] 29) Receive the configuration of the PDCCH for scheduling SIB1;

[0345] 30) Receive the configuration of the PDCCH for the scheduled RAR;

[0346] 31) The number of SSBs associated with each RO;

[0347] 32) SIB1 Request Period;

[0348] 33) Preamble sequence identifier;

[0349] 34) Related cycle;

[0350] 35) RO mask identifier;

[0351] 36) Search space 0;

[0352] 37) Control resource set 0;

[0353] 38) RAR search space;

[0354] 39) TA value;

[0355] 40) SSB cycle;

[0356] 41) Subcarrier offset)

[0357] 42) SIB transmission duration, for example, OD-SIB1 duration;

[0358] 43) The offset of the starting position of SIB1 transmission relative to the reference point, for example, expressed as the time window offset (offsetToTimeWindow);

[0359] 44) Point A frequency offset;

[0360] 45) Number of repetitions;

[0361] 46) Types of UL-WUS, for example, the types of UL-WUS include, but are not limited to, at least one of the following: Msg1, Msg3, MsgA, preamble;

[0362] 47) BWP configuration.

[0363] The number of UL-WUS configuration information can be multiple. For example, one UL-WUS configuration information is associated with the first OD-SIB1, and another UL-WUS configuration information is associated with the second OD-SIB1; or, one UL-WUS configuration information is associated with the request SIB1, and another UL-WUS configuration information is associated with the request SIB1+SDT transmission.

[0364] Alternatively, some parameters in the UL-WUS configuration information can be configured with multiple values, each associated with the first OD-SIB1 and the second OD-SIB1 respectively. For example, the preamble sequence identifier can be configured with two values, each associated with the first OD-SIB1 and the second OD-SIB1 respectively. For example, the RO start position can be configured with two values, each associated with the first OD-SIB1 and the second OD-SIB1 respectively, meaning that different RO resources are used to request the first OD-SIB1 and the second OD-SIB1 respectively. Alternatively, the preamble interval (WUS sequence identifier interval) can be associated with requesting SIB1 transmission and with requesting SIB1 transmission + SDT transmission respectively.

[0365] In this embodiment, the functions of different UL-WUS can be distinguished based on preamble or RO resources. The functions of UL-WUS include at least one of the following: requesting the first OD-SIB1, requesting the second OD-SIB1, requesting the first OD-SIB1+SDT transmission, requesting the second OD-SIB1+SDT transmission, etc.

[0366] Step 2: The UE sends UL-WUS and receives feedback information from UL-WUS;

[0367] Optionally, UL-WUS feedback information indicates at least one of the following:

[0368] 1) The identifier of the preamble sequence corresponding to UL-WUS;

[0369] 2) Fourth information, which indicates whether OD-SIB1 is the first OD-SIB1 or the second OD-SIB1;

[0370] 3) The first RNTI is used to scramble the PDCCH of the first OD-SIB1;

[0371] 4) Transmission duration of OD-SIB1;

[0372] 5) Beam identifier associated with OD-SIB1.

[0373] Optionally, OD-SIB1 indicates at least one of the following:

[0374] 1) The OD-SIB1 is either the first OD-SIB1 or the second OD-SIB1;

[0375] 2) UE features associated with OD-SIB1;

[0376] 3) UE type associated with OD-SIB1.

[0377] Step 3: The UE receives OD-SIB1, which includes at least one of a first OD-SIB1 and a second OD-SIB1, wherein the OD-SIB1 may optionally carry fifth information.

[0378] Optionally, the fifth piece of information includes at least one of the following:

[0379] 1) Sixth information, the sixth information indicating that the OD-SIB1 is a first OD-SIB1 or a second OD-SIB1;

[0380] 2) Seventh information, which indicates which UE features or UE types the OD-SIB1 carries in its configuration.

[0381] Step 4: The UE decodes OD-SIB1. If the NES cell does not allow the UE to access, the UE terminates the SDT procedure.

[0382] Optionally, the NES cell does not allow the UE to access the cell if: the terminal characteristics indicated by OD-SIB1 do not include the terminal characteristics of the terminal, or the terminal type indicated by OD-SIB1 does not include the terminal type of the terminal, or after the UE decodes OD-SIB1, it finds that the terminal type indicated by OD-SIB1 as not allowing access to the NES cell is the terminal type of the terminal.

[0383] In this embodiment, compared to OD-SIB1 which continuously sends the entire set of SIB1, the overhead of sending SIB1 is saved. For UEs that do not support certain terminal features, the UE is spared from receiving the configuration corresponding to these terminal features.

[0384] This embodiment does not limit the OD-SIB1 scenario, that is, it does not limit whether the UE obtains the UL-WUS configuration from the first cell or from the NES cell, nor does it limit whether the UL-WUS is sent in the first cell or in the NES cell.

[0385] Example 2: Two types of OD-SIB1 are scrambled by different RNTIs.

[0386] In this embodiment, the PDCCHs of scheduling the first OD-SIB1 and the second OD-SIB1 are scrambled by different RNTIs. The first OD-SIB1 is scrambled by the first RNTI, and the PDCCH of scheduling the second OD-SIB1 is scrambled by the second RNTI (e.g., SI-RNTI). When the UE requests the first OD-SIB1, the first RNTI is used to detect the corresponding PDCCH. At this time, the first OD-SIB1 may not contain the fifth information because the first OD-SIB1 is scrambled by the first RNTI, which will not affect the UE receiving the broadcast OD-SIB1.

[0387] Specifically, for example, the protocol stipulates that the PDCCH for scheduling the first OD-SIB1 is scrambled by the first RNTI, and the PDCCH for scheduling the second OD-SIB1 (broadcast OD-SIB1) is scrambled by the second RNTI.

[0388] 1) For a UE receiving broadcast OD-SIB1, the corresponding PDCCH is detected according to the second RNTI, and the second OD-SIB1 is received;

[0389] 2) For a UE requesting the first OD-SIB1, the first OD-SIB1 is received according to the PDCCH corresponding to the first RNTI detection.

[0390] In this embodiment, by scrambling different OD-SIB1s with different RNTIs, it is possible to prevent UEs in the cell that are expected to receive broadcast OD-SIB1 (second OD-SIB1) from receiving first OD-SIB1 triggered by other UEs, thereby avoiding the mistaken belief that the network side does not allow UEs with certain terminal features to access the network and reducing the impact on these UEs.

[0391] Example 3: Combination of RACH-based SDT and UL-WUS.

[0392] In this embodiment, for the process combining RACH-based SDT and UL-WUS, the UE sends Msg1 to request SIB1+Msg2. If access to the NES cell is allowed, the UE sends Msg3 PUSCH carrying SDT and directly transmits small data in the NES cell.

[0393] See Figure 5 The specific steps of the process combining RACH-based SDT and UL-WUS are as follows:

[0394] Step 1: The UE receives the first configuration information from the first message;

[0395] Step 2: The UE sends UL-WUS to the NES cell;

[0396] Step 3: The UE receives RAR+SIB1 from the NES cell;

[0397] Step 4: The UE sends an RRC connection restoration request to the NES cell;

[0398] Step 5: The NES cell sends a request to the first cell to obtain the UE context;

[0399] Step 6: The first cell sends a UE context acquisition response to the NES cell;

[0400] Step 7: The NES cell decides to continue small data transmission in the RRC inactive state.

[0401] In this embodiment, the first cell indicates whether the NES cell and the first cell belong to the same TA or RNA; or, the first configuration information sent by the first cell carries the cell ID of the NES cell and NCGI (20-30 bits), and the UE determines whether the first cell and the NES cell belong to the same RNA or TA; or, the protocol stipulates that the NES cells configured by the first cell belong to the same RNA or TA by default; or, the network side does not indicate, the UE directly receives OD-SIB1, and if it finds that SIB1 indicates that the first cell and the NES cell do not belong to the same RNA or TA, then the UE terminates the SDT procedure.

[0402] In this embodiment, the purpose of indicating whether they belong to the same RNA or TA is to help the UE determine whether small data transmission can be performed. If they do not belong to the same RNA or TA, the NES cell cannot send a request to the first cell to obtain the UE context, that is, it cannot perform subsequent small data transmission.

[0403] In related technologies, the UE first obtains SIB1 and then sends Msg1 to initiate the RACH-based SDT procedure. However, in this embodiment, UL-WUS is directly used as Msg1 to trigger the RACH-based SDT, saving the transmission overhead of Msg1.

[0404] Example 4: Combination of RACH-based SDT and WUS.

[0405] In this embodiment, for the process combining RACH-based SDT and UL-WUS, the transmission of Msg3 carrying the RRC Resume Request needs to be based on the OS-SIB1 transmission window as a reference point before the Msg3 is transmitted. The reason is that the UE needs to ensure that SIB1 is decrypted and that the cell allows camping / access before it can continue to transmit Msg3 and proceed with the subsequent SDT process.

[0406] To ensure that the UE decides whether to send or not send Msg3 only after receiving OD-SIB1, at least one of the following methods can be agreed upon in the protocol:

[0407] Method 1: The UE will assume that the minimum time interval between the last symbol of the PDSCH carrying RAR and the first symbol of the PUSCH transmission scheduled by the Random Access Response Grant (RAR grant) is greater than or equal to N. T,1 +N T,2 +A(ms), where A represents the processing time of SIB1. This A can be determined based on the SIB1 decoding time, and for example, A may be 0.5ms or more.

[0408] N T,1 It is the length of N1 time units (e.g., symbols), corresponding to the PDSCH processing time when additional PDSCH DM-RS is configured under UE Capability 1 (e.g., the processing time of message 2).

[0409] N T,2 It is the length of N2 time units (e.g., symbols), corresponding to the PUSCH preparation time under UE Capability 1 (e.g., the preparation time of message 3).

[0410] The values ​​of N1 and N2 depend on the smaller of the subcarrier spacing (SCS) configurations of PDSCH and PUSCH.

[0411] Method 2: Now the protocol predefines N T1 and N T2 Since SIB1 reception is not taken into account, a new Msg3 timing table can be defined.

[0412] Table 1: Msg3 timing: Minimum time between RAR and PUSCH.

[0413] μ <![CDATA[N1]]> <![CDATA[N T1 (ms)]]> <![CDATA[N2]]> <![CDATA[N T2 ]]> <![CDATA[Minimum time(ms)=N T1 + NT2 +0.5]]> 0 14 2 10 1.4 3.9 1 13 1 12 0.8 2.3 2 20 0.6 23 0.8 1.9 3 24 0.4 36 0.6 1.5

[0414] By expanding N T1 and N T2 By adjusting the value, the time interval between the transmission of Msg3 and Msg2 is increased to ensure the reception of SIB1.

[0415] Method 3: The UE is only allowed to send Msg3 at least X time units after the first reference point, where X is greater than or equal to 0;

[0416] The first reference point includes at least one of the following:

[0417] 1) After receiving the last time unit carrying Msg2, at time N T,1 +N T,2 +A(ms);

[0418] 2) For the ending position of the OD-SIB1 window (i.e., the first window), see [link / reference]. Figure 5 ;

[0419] 3) The starting position of the OD-SIB1 window;

[0420] 4) The time unit in which Type 0PDCCH is received;

[0421] 5) The time unit in which SIB1 receives the data;

[0422] 6) Receive the time unit containing the PDSCH carrying the RAR;

[0423] 7) The end position of the RAR window (i.e., the second window);

[0424] 8) The starting position of the RAR window;

[0425] 9) The time unit in which UL-WUS is located.

[0426] For scenarios combining RACH-based SDT and UL-WUS, where the UE sends UL-WUS, receives Msg2, and sends Msg3 (which includes SDT), the overhead of sending Msg1 is reduced compared to the existing technology where the terminal first receives SIB1 and then sends Msg1 to trigger SDT.

[0427] See Figure 6 An embodiment of this application provides a communication device applied to a terminal. The device 60 includes: a first transmitting unit 61;

[0428] The first sending unit 61 is used to send a first uplink transmission, the first uplink transmission being used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission;

[0429] The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

[0430] In one embodiment of this application, the first system information includes configurations corresponding to some terminal features or some terminal types; or, the first system information does not include configurations corresponding to some optional terminal features or terminal types; or, the second system information includes configurations corresponding to all terminal features or all terminal types.

[0431] In one embodiment of this application, the first sending unit 61 is further configured to receive first configuration information;

[0432] The first configuration information includes at least one of the following:

[0433] The first information indicates whether the first cell allows or disallows the request for the first system information;

[0434] The terminal characteristics or terminal type associated with the first system information;

[0435] The first cell allows terminal characteristics or terminal types that request information from the first system;

[0436] Small data transfer SDT configuration;

[0437] First Radio Network Temporary Identifier (RNTI), the first RNTI is used to scramble and schedule the Physical Downlink Control Information (PDCCH) of the first system information;

[0438] The second RNTI is used to scramble the PDCCH of the second system information;

[0439] At least one cell identifier of the first cell;

[0440] At least one NR cell global identifier (NCGI) of the first cell;

[0441] The second information indicates whether at least one of the first cells and the second cell belong to or do not belong to the same tracking area (TA);

[0442] The third information indicates that at least one of the first cell and the second cell belong to or do not belong to the same radio access network notification area (RNA).

[0443] One or more configuration information of the first uplink transmission;

[0444] The first configuration information is sent by the network-side device associated with the first cell.

[0445] In one embodiment of this application, at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the first system information, and at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the second system information.

[0446] or,

[0447] The first parameter in the configuration information of the first uplink transmission includes at least a first value and a second value, wherein the first value is associated with the first system information and the second value is associated with the second system information.

[0448] In one embodiment of this application, the first sending unit 61 is further configured to receive feedback information from the first uplink transmission;

[0449] The feedback information includes at least one of the following:

[0450] The identifier of the preamble sequence corresponding to the first uplink transmission;

[0451] The fourth information indicates that the system information of the first cell is either the first system information or the second system information;

[0452] The first RNTI is used to scramble the PDCCH of the first system information;

[0453] The transmission duration of system information in the first cell;

[0454] The beam identifier associated with the system information of the first cell.

[0455] In one embodiment of this application, the system information of the first cell indicates at least one of the following:

[0456] The system information of the first cell is either the first system information or the second system information;

[0457] The terminal characteristics associated with the system information of the first cell;

[0458] The terminal type associated with the system information of the first cell.

[0459] In one embodiment of this application, the first transmitting unit 61 is further configured to receive system information of the first cell.

[0460] In one embodiment of this application, the first sending unit 61 is further configured to receive system information of the first cell, as well as message 2 or message B.

[0461] In one embodiment of this application, the first sending unit 61 is further configured to receive system information of the first cell; and receive message 2 or message B according to the system information of the first cell;

[0462] Wherein, the terminal characteristics indicated by the system information of the first cell include the terminal characteristics of the terminal, or the terminal type indicated by the system information of the first cell includes the terminal type of the terminal.

[0463] In one embodiment of this application, the first sending unit 61 is further configured to terminate the SDT process based on the system information of the first cell;

[0464] Wherein, the terminal characteristics indicated by the system information of the first cell do not include the terminal characteristics of the terminal, or the terminal type indicated by the system information of the first cell does not include the terminal type of the terminal.

[0465] In one embodiment of this application, the first sending unit 61 is further configured to send the first uplink transmission when a first condition is met;

[0466] The first condition includes at least one of the following:

[0467] The first cell and the cell in which the terminal receives the first configuration information belong to the same TA;

[0468] The first cell and the cell in which the terminal receives the first configuration information belong to the same RNA;

[0469] The conditions for the terminal to initiate MO-SDT small data transmission are met;

[0470] The size of the uplink data packet to be transmitted is less than or equal to the first threshold.

[0471] In one embodiment of this application, the first sending unit 61 is further configured to send message 3 after receiving message 2.

[0472] In one embodiment of this application, the first sending unit 61 is further configured to allow the sending of message 3 only after at least the Xth time unit after the first reference point, where X is greater than or equal to 0;

[0473] The first reference point includes at least one of the following:

[0474] In the Yth time unit after receiving the last time unit of the PDSCH carrying the message 2, the value of Y is determined based on at least one of the preparation time of the message 3, the processing time of the message 2, and the processing time of the system information of the first cell, and Y is greater than or equal to 0.

[0475] The first window is located at the end of the first window, which is used to receive system information from the first cell.

[0476] The starting position of the first window;

[0477] The time unit in which type 0PDCCH is received;

[0478] The time unit in which the system information is received in the first cell;

[0479] The time unit in which the PDSCH carrying message 2 is received;

[0480] The end position of the second window, which is used to receive the message 2;

[0481] The starting position of the second window;

[0482] The time unit in which the first uplink transmission occurs.

[0483] In one embodiment of this application, the first sending unit 61 is further configured to assume or default that the minimum time interval between the first time unit and the second time unit is greater than or equal to the first time interval;

[0484] The first time unit is the last time unit in which the PDSCH carrying message 2 is received;

[0485] The second time unit is the first time unit transmitted by the Physical Uplink Shared Channel (PUSCH) authorized and scheduled by message 2;

[0486] The first time interval is determined based on at least one of the preparation time of message 3, the processing time of message 2, and the processing time of system information of the first cell.

[0487] The apparatus provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0488] See Figure 7 An embodiment of this application provides a communication device applied to a network-side device. The device 70 includes a second transceiver unit 71.

[0489] The second transceiver unit 71 is used to receive a first uplink transmission sent by the terminal, the first uplink transmission being used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission.

[0490] The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

[0491] In one embodiment of this application, the first system information includes configurations corresponding to some terminal features or some terminal types, the first system information does not include configurations corresponding to some optional terminal features or terminal types, or, alternatively, the second system information includes configurations corresponding to all terminal features or all terminal types.

[0492] In one embodiment of this application, the second transceiver unit 71 is further configured to send first configuration information to the terminal via a second cell;

[0493] The first configuration information includes at least one of the following:

[0494] The first information indicates whether the first cell allows or disallows the request for the first system information;

[0495] The terminal characteristics or terminal type associated with the first system information;

[0496] Terminal characteristics or terminal type that are allowed to request the first system information;

[0497] SDT configuration;

[0498] The first RNTI is used to scramble and schedule the physical downlink control information (PDCCH) of the first system information.

[0499] The second RNTI is used to scramble the PDCCH of the second system information;

[0500] At least one cell identifier of the first cell;

[0501] At least one NCGI of the first cell;

[0502] The second information indicates whether at least one of the first cells and the second cell belong to or do not belong to the same TA;

[0503] The third information indicates that at least one of the first cells and the second cell belong to or do not belong to the same RNA;

[0504] Configuration information for one or more of the first uplink transmissions.

[0505] In one embodiment of this application, at least a portion of the configuration information of the first uplink transmission is associated with the first system information, and at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the second system information.

[0506] or,

[0507] The first parameter in the configuration information of the first uplink transmission includes at least a first value and a second value, wherein the first value is associated with the first system information and the second value is associated with the second system information.

[0508] In one embodiment of this application, the second transceiver unit 71 is further configured to send feedback information of the first uplink transmission;

[0509] The feedback information includes at least one of the following:

[0510] The identifier of the preamble sequence corresponding to the first uplink transmission;

[0511] The fourth information indicates that the system information of the first cell is either the first system information or the second system information;

[0512] The first RNTI is used to scramble the PDCCH of the first system information;

[0513] The transmission duration of system information in the first cell;

[0514] The beam identifier associated with the system information of the first cell.

[0515] In one embodiment of this application, the system information of the first cell indicates at least one of the following:

[0516] The system information of the first cell is either the first system information or the second system information;

[0517] The terminal characteristics associated with the system information of the first cell;

[0518] The terminal type associated with the system information of the first cell.

[0519] In one embodiment of this application, the second transceiver unit 71 is further configured to transmit the system information.

[0520] In one embodiment of this application, the second transceiver unit 71 is further configured to transmit the system information, as well as message 2 or message B.

[0521] The apparatus provided in this application embodiment can achieve... Figure 3 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0522] like Figure 8 As shown, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the above-mentioned... Figure 2 The various steps of the illustrated method embodiment can achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the above-described steps. Figure 3The steps of the method embodiment shown are the same and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0523] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 2 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 6 The communication processing device shown.

[0524] Specifically, Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0525] The terminal 900 includes, but is not limited to, at least some of the following components: radio frequency unit 901, network module 902, audio output unit 903, input unit 904, sensor 905, display unit 906, user input unit 907, interface unit 908, memory 909, and processor 910.

[0526] Those skilled in the art will understand that the terminal 900 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 910 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 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.

[0527] It should be understood that, in this embodiment, the input unit 904 may include a graphics processor 9041 and a microphone 9042. The graphics processor 9041 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 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

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

[0529] The memory 909 can be used to store software programs or instructions, as well as various data. The memory 909 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 909 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 909 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0530] Processor 910 may include one or more processing units; optionally, processor 910 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 910.

[0531] It is understood that the implementation process of each implementation method mentioned in this embodiment can be referred to Figure 2The relevant descriptions of the method embodiments shown herein, which achieve the same or corresponding technical effects, will not be repeated here to avoid duplication.

[0532] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 3 The steps of the method embodiment shown are illustrated. 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 can achieve the same technical effect.

[0533] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 7 The communication processing device shown. (For example...) Figure 10 As shown, the network-side device 1000 includes: an antenna 1001, a radio frequency (RF) device 1002, a baseband device 1003, a processor 1004, and a memory 1005. The antenna 1001 is connected to the RF device 1002. In the uplink direction, the RF device 1002 receives information through the antenna 1001 and transmits the received information to the baseband device 1003 for processing. In the downlink direction, the baseband device 1003 processes the information to be transmitted and sends it to the RF device 1002. The RF device 1002 processes the received information and transmits it through the antenna 1001.

[0534] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1003, which includes a baseband processor.

[0535] The baseband device 1003 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 10 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1005 via a bus interface to call the program in the memory 1005 and execute the network device operation shown in the above method embodiment.

[0536] The network-side device may also include a network interface 1006, such as a Common Public Radio Interface (CPRI).

[0537] Specifically, the network-side device 1000 in this application embodiment further includes: instructions or programs stored in memory 1005 and executable on processor 1004, wherein processor 1004 calls the instructions or programs in memory 1005 to execute. Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0538] It is understood that the implementation process of each implementation method mentioned in this embodiment can be referred to Figure 3 The relevant descriptions of the method embodiments shown herein, which achieve the same or corresponding technical effects, will not be repeated here to avoid duplication.

[0539] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figure 2 or Figure 3 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0540] 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.

[0541] This application embodiment also provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the above. Figure 2 or Figure 3 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0542] 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.

[0543] This application embodiment 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. Figure 2 or Figure 3 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0544] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the functions provided in this application. Figure 2 The steps of the method shown can be performed by the network-side device as provided in the embodiments of this application. Figure 3 The steps of the method shown.

[0545] 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.

[0546] 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 one or more instructions to cause a terminal or network-side device to execute the methods described in the various embodiments of this application.

[0547] 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. A communication method, characterized in that, include: The terminal sends a first uplink transmission, which is used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission; The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

2. The method according to claim 1, characterized in that, The first system information includes configurations corresponding to some terminal features or some terminal types; or, the first system information does not include configurations corresponding to some optional terminal features or terminal types; or, the second system information includes configurations corresponding to all terminal features or all terminal types.

3. The method according to claim 1, characterized in that, Before the terminal sends the first uplink transmission, the method further includes: The terminal receives first configuration information; The first configuration information includes at least one of the following: The first information indicates whether the first cell allows or disallows the request for the first system information; The terminal characteristics or terminal type associated with the first system information; Terminal characteristics or terminal type that are allowed to request the first system information; Small data transfer SDT configuration; First Radio Network Temporary Identifier (RNTI), the first RNTI is used to scramble and schedule the Physical Downlink Control Information (PDCCH) of the first system information; The second RNTI is used to scramble the PDCCH of the second system information; At least one cell identifier of the first cell; At least one NR cell global identifier (NCGI) of the first cell; The second information indicates whether at least one of the first cells and the second cell belong to or do not belong to the same tracking area (TA); The third information indicates that at least one of the first cell and the second cell belong to or do not belong to the same radio access network notification area (RNA). One or more configuration information of the first uplink transmission; The first configuration information is sent by the network-side device associated with the second cell.

4. The method according to claim 3, characterized in that, At least a portion of the configuration information of the plurality of first uplink transmissions is associated with the first system information, and at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the second system information. or, The first parameter in the configuration information of the first uplink transmission includes at least a first value and a second value, wherein the first value is associated with the first system information and the second value is associated with the second system information.

5. The method according to claim 1, characterized in that, The method further includes: The terminal receives the feedback information from the first uplink transmission; The feedback information includes at least one of the following: The identifier of the preamble sequence corresponding to the first uplink transmission; The fourth information indicates that the system information of the first cell is either the first system information or the second system information; The first RNTI is used to scramble the PDCCH of the first system information; The transmission duration of system information in the first cell; The beam identifier associated with the system information of the first cell.

6. The method according to claim 1, characterized in that, The system information of the first cell indicates at least one of the following: The system information of the first cell is either the first system information or the second system information; The terminal characteristics associated with the system information of the first cell; The terminal type associated with the system information of the first cell.

7. The method according to claim 1, characterized in that, The method further includes: The terminal receives system information from the first cell.

8. The method according to claim 1, characterized in that, The method further includes: The terminal receives system information from the first cell, as well as message 2 or message B.

9. The method according to claim 8, characterized in that, The terminal receives system information from the first cell, as well as message 2 or message B, including: The terminal receives system information from the first cell; The terminal receives message 2 or message B based on the system information of the first cell; Wherein, the terminal characteristics indicated by the system information of the first cell include the terminal characteristics of the terminal, or the terminal type indicated by the system information of the first cell includes the terminal type of the terminal.

10. The method according to claim 7 or 8, characterized in that, The method further includes: The terminal terminates the SDT process based on the system information of the first cell; Wherein, the terminal characteristics indicated by the system information of the first cell do not include the terminal characteristics of the terminal, or the terminal type indicated by the system information of the first cell does not include the terminal type of the terminal.

11. The method according to claim 1 or 3, characterized in that, The terminal sends a first uplink transmission, including: If the first condition is met, the terminal sends the first uplink transmission; The first condition includes at least one of the following: The first cell and the cell in which the terminal receives the first configuration information belong to the same TA; The first cell and the cell in which the terminal receives the first configuration information belong to the same RNA; The conditions for the terminal to initiate MO-SDT small data transmission are met; The size of the uplink data packet to be transmitted is less than or equal to the first threshold.

12. The method according to claim 8 or 9, characterized in that, After receiving message 2 or message B, the method further includes: The terminal is only allowed to send message 3 after at least the Xth time unit after the first reference point, where X is greater than or equal to 0; The first reference point includes at least one of the following: In the Yth time unit after receiving the last time unit of the Physical Downlink Shared Channel (PDSCH) carrying message 2, the value of Y is determined based on at least one of the preparation time of message 3, the processing time of message 2, and the processing time of system information of the first cell, and Y is greater than or equal to 0. The first window is located at the end of the first window, which is used to receive system information from the first cell. The starting position of the first window; The time unit in which type 0PDCCH is received; The time unit in which the system information is received in the first cell; The time unit in which the PDSCH carrying message 2 is received; The end position of the second window, which is used to receive the message 2; The starting position of the second window; The time unit in which the first uplink transmission occurs.

13. The method according to claim 12, characterized in that, Message 3 contains small data.

14. The method according to claim 12, characterized in that, The method further includes: The terminal assumes or defaults that the minimum time interval between the first time unit and the second time unit is greater than or equal to the first time interval. The first time unit is the last time unit in which the PDSCH carrying message 2 is received; The second time unit is the first time unit transmitted by the Physical Uplink Shared Channel (PUSCH) authorized and scheduled by message 2; The first time interval is determined based on at least one of the preparation time of message 3, the processing time of message 2, and the processing time of system information of the first cell.

15. A communication method, characterized in that, include: The network-side device receives a first uplink transmission sent by the terminal, the first uplink transmission being used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission; The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

16. The method according to claim 15, characterized in that, The first system information includes configurations corresponding to some terminal features or some terminal types. The first system information does not include configurations corresponding to some optional terminal features or terminal types. Alternatively, the second system information includes configurations corresponding to all terminal features or all terminal types.

17. The method according to claim 15, characterized in that, Before the network-side device receives the first uplink transmission sent by the terminal, the method further includes: The network-side device sends the first configuration information to the terminal through the second cell; The first configuration information includes at least one of the following: The first information indicates whether the first cell allows or disallows the request for the first system information; The terminal characteristics or terminal type associated with the first system information; Terminal characteristics or terminal type that are allowed to request the first system information; SDT configuration; The first RNTI is used to scramble and schedule the physical downlink control information (PDCCH) of the first system information. The second RNTI is used to scramble the PDCCH of the second system information; At least one cell identifier of the first cell; At least one NCGI of the first cell; The second information indicates whether at least one of the first cells and the second cell belong to or do not belong to the same TA; The third information indicates that at least one of the first cells and the second cell belong to or do not belong to the same RNA; Configuration information for one or more of the first uplink transmissions.

18. The method according to claim 17, characterized in that, At least a portion of the configuration information of the plurality of first uplink transmissions is associated with the first system information, and at least a portion of the configuration information of the plurality of first uplink transmissions is associated with the second system information. or, The first parameter in the configuration information of the first uplink transmission has at least a first value and a second value. The first value indicates that the configuration information of the first uplink transmission is associated with the first system information, and the second value indicates that the configuration information of the first uplink transmission is associated with the second system information.

19. The method according to claim 15, characterized in that, The method further includes: The network-side device sends the feedback information of the first uplink transmission; The feedback information includes at least one of the following: The identifier of the preamble sequence corresponding to the first uplink transmission; The fourth information indicates that the system information of the first cell is either the first system information or the second system information; The first RNTI is used to scramble the PDCCH of the first system information; The transmission duration of system information in the first cell; The beam identifier associated with the system information of the first cell.

20. The method according to claim 15, characterized in that, The system information of the first cell indicates at least one of the following: The system information of the first cell is either the first system information or the second system information; The terminal characteristics associated with the system information of the first cell; The terminal type associated with the system information of the first cell.

21. The method according to claim 15, characterized in that, The first uplink transmission is used to request system information of the first cell, and the method further includes: The network-side device sends the system information of the first cell.

22. The method according to claim 15, characterized in that, The first uplink transmission is used to request system information of the first cell, and message 2 or message B, and the method further includes: The network-side device sends the system information of the first cell, as well as message 2 or message B.

23. A communication device, characterized in that, include: First transmitting unit; The first sending unit is configured to send a first uplink transmission, the first uplink transmission being configured to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission; The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

24. The apparatus according to claim 23, characterized in that, The first sending unit is also used to receive first configuration information; The first configuration information includes at least one of the following: The first information indicates whether the first cell allows or disallows the request for the first system information; The terminal characteristics or terminal type associated with the first system information; Terminal characteristics or terminal type that are allowed to request the first system information; SDT configuration; The first RNTI is used to scramble the PDCCH of the first system information; The second RNTI is used to scramble the PDCCH of the second system information; At least one cell identifier of the first cell; At least one NCGI of the first cell; The second information indicates whether at least one of the first cells and the second cell belong to or do not belong to the same TA; The third information indicates that at least one of the first cells and the second cell belong to or do not belong to the same RNA; One or more configuration information of the first uplink transmission; The first configuration information is sent by the network-side device associated with the first cell.

25. A communication device applied to network-side equipment, characterized in that, include: Second transceiver unit; The second transceiver unit is used to receive a first uplink transmission sent by the terminal, the first uplink transmission being used to request one of the following: system information of the first cell; system information of the first cell and message 2 or message B; system information of the first cell and small data transmission; The system information of the first cell includes either the first system information or the second system information, wherein the first system information is a subset of the second system information.

26. The apparatus according to claim 25, characterized in that, The second transceiver unit is also used to send first configuration information to the terminal through the second cell; The first configuration information includes at least one of the following: The first information indicates whether the first cell allows or disallows the request for the first system information; The terminal characteristics or terminal type associated with the first system information; Terminal characteristics or terminal type that are allowed to request the first system information; SDT configuration; The first RNTI is used to scramble the PDCCH of the first system information; The second RNTI is used to scramble the PDCCH of the second system information; At least one cell identifier of the first cell; At least one NCGI of the first cell; The second information indicates whether at least one of the first cells and the second cell belong to or do not belong to the same TA; The third information indicates that at least one of the first cells and the second cell belong to or do not belong to the same RNA; Configuration information for one or more of the first uplink transmissions.

27. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 14.

28. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 15 to 22.

29. A chip, characterized in that, The chip includes a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the steps of the method as described in any one of claims 1 to 22.

Images