Communication method and apparatus, and terminal and storage medium

Abstract

The present application belongs to the technical field of communications. Disclosed are a communication method and apparatus, and a terminal and a storage medium. The communication method of the embodiments in the present application comprises: a terminal sending a first object to a network-side device, wherein the first object is used for at least one of the following: indicating a feature supported by the terminal, and requesting the network-side device to use the feature supported by the terminal to communicate with the terminal.

Description

Communication methods, devices, terminals and storage media

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510464518.9, filed in China on April 14, 2025, the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] With the evolution of communication technology, future mobile communication technology will need to support more and more different types or capabilities of terminals and more services with different quality of service requirements.

[0005] Because different types or capabilities of terminals support different features, network-side devices will use different methods when communicating with terminals of different types or capabilities. However, if the network-side device is unaware of the features supported by the terminal, it cannot communicate with the terminal in the most appropriate and efficient way. Terminals also exhibit different communication characteristics before entering the connected state. How to enable the network side to identify the terminal's supported characteristics before entering the connected state is key to achieving efficient communication and is a problem that urgently needs to be solved. Summary of the Invention

[0006] This application provides a communication method, apparatus, terminal, and storage medium that enable more efficient communication.

[0007] In a first aspect, a communication method is provided, executed by a terminal, the method comprising: the terminal sending a first object to a network-side device, the first object being used for at least one of the following: indicating features supported by the terminal; requesting the network-side device to communicate with the terminal using features supported by the terminal.

[0008] In a second aspect, a communication device is provided, comprising: a transmitting module. The transmitting module is configured to transmit a first object to a network-side device, the first object being configured to: indicate features supported by the terminal; or request the network-side device to communicate with the terminal using features supported by the terminal.

[0009] Thirdly, a terminal is provided, comprising 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 described in the first aspect.

[0010] Fourthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send a first object to a network-side device, the first object being used for at least one of the following: indicating features supported by the terminal; requesting the network-side device to communicate with the terminal using features supported by the terminal.

[0011] Fifthly, 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.

[0012] A sixth aspect provides a wireless communication system, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method described in the first aspect.

[0013] In a seventh aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the steps of the method described in the first aspect.

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

[0015] In this embodiment, the terminal sends a first object to the network-side device. The first object is used for at least one of the following: indicating features supported by the terminal; and requesting the network-side device to communicate with the terminal using the features supported by the terminal. In this solution, since the terminal can indicate the features supported by the terminal to the network-side device, the network-side device can use the features supported by the terminal to communicate with the terminal, thereby achieving more efficient communication. Attached Figure Description

[0016] Figure 1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application;

[0017] Figure 2 is a flowchart illustrating one of the communication methods provided in an embodiment of this application;

[0018] Figure 3 is a second schematic flowchart of a communication method provided in an embodiment of this application;

[0019] Figure 4 is a third schematic flowchart of a communication method provided in an embodiment of this application;

[0020] Figure 5 is a fourth flowchart illustrating a communication method provided in an embodiment of this application;

[0021] Figure 6 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0022] Figure 7 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application;

[0023] Figure 8 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application. Detailed Implementation

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

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

[0026] 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 the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

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

[0028] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and 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 headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations 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), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate 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 term. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0029] 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 (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

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

[0031] To facilitate understanding of the solution in this application, the relevant technologies involved in this application will be explained below.

[0032] 1. Random Access Channel (RACH) partitioning and feature combination

[0033] With the introduction of Random Access Resource Partitioning (RACH) and Feature Combination in 3GPP Release 17, network-side devices configure specific random access resources for different features or feature combinations. This allows for the immediate identification of specific features or feature combinations via msg1. The specific feature combinations, feature priorities, and related RACH configurations are all configured to the terminal via SIB1.

[0034] The relevant RRC configuration is shown below:

[0035] 1) A Feature Combination can represent a feature combination associated with a RACH partition (i.e., an instance of a Feature Combination Preamble). NR supports the following valid features in a Feature Combination: redcap, smallData, nsag, msg3-Repetitions, msg1-Repetitions, and eRedCap. Additionally, for nsag features, a list with a maximum size of maxSliceInfo-r17 is supported, and each NSAG-ID can be a value from 0 to 255. The total size of the entire Feature Combination IE in NR is 8 bits.

[0036] 2) Feature Priorities

[0037] Different features have different priorities. The network configures priorities for different features, such as RedCap and smallData, through the featurePriorities field in System Information Block (SIB1). These priorities determine which feature combination preambles the terminal should use when a feature is mapped to multiple feature combination preambles. The smaller the value, the higher the priority. Network-side devices will not issue the same priority signal for multiple features. Network-side devices will indicate the priority for all features mapped to at least one feature combination preamble.

[0038] 3) Feature Combination Preambles

[0039] FeatureCombinationPreambles associates a set of preambles with a feature combination. For parameters that can be provided in this IE and also in RACH-ConfigCommon or MsgA-ConfigCommon: if a parameter is signaled in this IE, the terminal applies this field value when performing random access using the preamble in featureCombinationPreambles; otherwise, the terminal applies the corresponding value signaled in RACH-ConfigCommon or MsgA-ConfigCommon.

[0040] FeatureCombinationPreambles are configured in rach-ConfigCommon-r17 within AdditionalRACH-ConfigList-r17 of BWP-UplinkCommon in the System Information Block (SIB).

[0041] 2. Determination of random access resources related to Feature Combination

[0042] Traditional RACH resource determination methods are based on priority and employ iterative search to determine the final RACH resource to be used by sequentially satisfying the highest priority characteristics.

[0043] 1) Availability of random access resource sets

[0044] For each set of configured random access resources, Media Access Control (MAC) should:

[0045] If eRedCap associated with a set of random access resources is set to true, then for random access procedures where eRedCap is not applicable, that set of random access resources is considered unavailable.

[0046] If redCap is set to true for a set of random access resources, then for random access procedures where redCap is not applicable, that set of random access resources is considered unavailable.

[0047] If smallData associated with a set of random access resources is set to true: then for random access procedures that are not triggered by Mobile Originated-SDT (MO-SDT) for Random Access based SDT (RA-SDT), the set of random access resources is considered unavailable;

[0048] If an NSAG-List is configured for a set of random access resources, then that set of random access resources should be considered unavailable for the random access procedure unless the procedure is triggered for any NSAG-ID in the NSAG-List.

[0049] If msg3-Repetitions is set to true for a set of random access resources, then that set of random access resources is considered unavailable for random access procedures that are not applicable for Msg3 repetition.

[0050] If a set of random access resources is associated with msg1-Repetitions set to true, and the current random access procedure does not apply Msg1 repetition, or the set of random access resources is not associated with any number of Msg1 repetitions applicable to the current random access procedure, then the set of random access resources is considered unavailable for the current random access procedure.

[0051] If a set of random access resources is not configured with FeatureCombination, then it is assumed that the set of random access resources is not associated with any feature.

[0052] 2) Random access resource set selection based on feature priority

[0053] MAC entities should:

[0054] From the set of random access resources available for this random access procedure, identify the feature with the highest priority assigned in featurePriorities among all applicable features specified for this random access procedure.

[0055] If a single set of random access resources is identified: Select this set of random access resources;

[0056] If multiple random access resource sets are identified, and all identified random access resource sets are configured with Msg1 repeat indication and have the same featureCombination, then the random access resource set associated with the highest Msg1 repeat count is selected from the identified random access resource sets.

[0057] If multiple random access resource sets are identified, and all identified random access resource sets are not configured with Msg1 repeat indication and have the same featureCombination, then repeat this process, taking the identified random access resource sets and the feature with the highest priority among all features applicable to this random access process (other than the features already considered) as input.

[0058] If no random access resource set is identified: repeat the process, taking the previously identified available random access resource set and the features (other than those already considered) that are applicable to the current random access process and have the highest priority in featurePriorities as input.

[0059] 3) An example related to random access resource selection

[0060] The network side is configured with the following six features or combinations of features for random access resources: (1) Legacy Common, (2) RedCap, (3) RedCap+SliceX+Small Data Transmission (SDT), (4) RedCap+SDT, (5) RedCap+SliceX+msg3-Repetitions, and (6) RedCap+msg3-Repetitions. The priority of each feature decreases in the following order: redCapPriority-r17, slicePriority-r17, msg3-Repetitions-r17, and sdt-Priority-r17.

[0061] Suppose that the terminal initiates a RACH triggered by the three features RedCap+SliceX+msg3-Repetitions at a certain time. RedCap has the highest priority, so the five combinations that satisfy RedCap are searched and determined first: (2) RedCap, (3) RedCap+SliceX+SDT, (4) RedCap+SDT, (5) RedCap+SliceX+msg3-Repetitions, and (6) RedCap+msg3-Repetitions.

[0062] After continuing to search for feature combinations that satisfy SliceX from the five combinations that satisfy RedCap identified in the previous step, SliceX is selected as the highest priority feature in the next round of search. Among the five candidate combinations, (3) RedCap+SliceX+SDT and (5) RedCap+SliceX+msg3-Repetitions contain the SliceX feature.

[0063] Finally, determine the combination that satisfies the msg3-Repetitions property in (3)RedCap+SliceX+SDT and (5)RedCap+SliceX+msg3-Repetitions. The msg3-Repetitions property can be indicated in (5), so choose (5)RedCap+SliceX+msg3-Repetitions.

[0064] The above process requires a total of 13 searches to determine the final RACH resource. The more valid features in the feature combination that triggers RACH, the more feature combinations the network is configured with, the longer it takes to determine the final RACH resource, and the higher the power consumption.

[0065] 3. Terminal capability reporting method during the random access phase

[0066] 1) Feature combination method

[0067] First, the network configures dedicated random access resources for different features or combinations of features and notifies the terminal via SIB1. The terminal implicitly informs the base station by selecting a specific RACH resource from the dedicated random access resources configured by the network. Based on the RACH resource selected by the terminal, the base station can know the terminal's relevant capabilities or the features it supports.

[0068] 2) Logical Channel Identifier (LCID) method

[0069] The capability notification methods for redcap, eRedcap, PUCCH repetition of Msg4 HARQ-ACK, and their combinations can also be identified through specific proprietary LCIDs specified by CCCH / CCCH1. For example, when a RedCap terminal and a non-RedCap terminal simultaneously access an NR cell, the base station needs to be informed which terminal supports RedCap. One way to do this is to inform the base station through the LCID of Msg3 (new LCID Index 35 / 36).

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

[0071] In this embodiment, since the terminal can indicate the features it supports to the network-side device, the network-side device can use the features supported by the terminal to communicate with the terminal, thereby achieving more efficient communication.

[0072] Figure 2 is a flowchart illustrating the communication method provided in an embodiment of this application. As shown in Figure 2, the communication method may include the following step 201.

[0073] Step 201: The terminal sends the first object to the network-side device.

[0074] In the embodiments of this application, the first object described above is used for at least one of the following:

[0075] Indicates the features supported by the terminal;

[0076] The request is for the network-side device to use features supported by the terminal to communicate with the terminal.

[0077] In some embodiments of this application, the first object described above can be used to indicate all features among the features supported by the terminal, or it can be used to indicate some features among the features supported by the terminal.

[0078] In some embodiments of this application, a feature supported by the terminal may also be a combination of features, or a feature resulting from the merging of features.

[0079] In some embodiments of this application, the first object mentioned above includes at least one of the following: a wake-up signal (WUS), a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), a message Msg3, a message Msg5, a message MsgA, a physical random access channel (PRACH), a first uplink channel, and a first signal.

[0080] In some embodiments of this application, the WUS mentioned above may include at least one of the following: WUS preamble, WUS PUSCH.

[0081] In some embodiments of this application, when the terminal is in an RRC idle state or an inactive state, the above-mentioned PUSCH may include any of the following: contention-based PUSCH access or CG-PUSCH transmission.

[0082] In some embodiments of this application, the first uplink channel is an uplink channel sent by the terminal to the network-side device before entering the connected state; the first signal is a signal sent by the terminal to the network-side device before entering the connected state.

[0083] In some examples, the terminal supports a feature reporting process before initiating random access. The terminal can select specific uplink channels or signal resources to report combinations of features based on SSB detection.

[0084] For example, before initiating random access, the terminal supports a Feature Combination (FC) reporting process. The terminal can select a specific FC report uplink channel or signal resource for FC reporting based on SSB detection.

[0085] In some embodiments of this application, when the first object is used to request the network-side device to communicate with the terminal using features supported by the terminal, the first object can also be used to indicate features supported by the terminal.

[0086] For example, when the first object is WUS, the first object can be used to request the network-side device to use the features supported by the terminal to communicate with the terminal. It can also indicate the features supported by the terminal through the strength information of WUS, so that after the network-side device receives the first object sent by the terminal, it can use the features supported by the terminal to communicate with the terminal.

[0087] Thus, since terminal-supported features can be reported not only through RACH resources associated with features or feature combinations, but also through WUS, PUSCH, SRS, message Msg3, message Msg5, message MsgA, PUSCH, first uplink channel, and first signal, more terminal feature reporting can be supported without increasing the search time and energy consumption of RACH resources. This allows the network to acquire more terminal capabilities and achieve more efficient communication.

[0088] In some embodiments of this application, when the first object is WUS, the features supported by the terminal are indicated by at least one of the following:

[0089] Is WUS transmission present?

[0090] WUS intensity information;

[0091] WUS's temporal location information;

[0092] WUS frequency domain location information;

[0093] WUS port information;

[0094] WUS sequence information;

[0095] WUS scrambling sequence information;

[0096] The reference signal associated with WUS;

[0097] Types of WUS;

[0098] The type of reference signal associated with WUS.

[0099] It is understandable that the terminal can use WUS transmission to indicate the features supported by the terminal to the network-side device.

[0100] In some embodiments of this application, the network-side device can determine the features supported by the terminal by judging whether WUS transmission exists.

[0101] For example: when WUS transmission is present, the terminal is indicated to support the feature of small data transmission based on RACH.

[0102] In some embodiments of this application, the strength information of the WUS mentioned above includes at least one of the following: Reference Signal Receiving Power (RSRP), Reference Signal Received Quality (RSRQ), Reference Signal Strength Indicator (RSSI), and Signal to Interference plus Noise Ratio (SINR).

[0103] In some embodiments of this application, each feature can correspond to a strength range of WUS. The network-side device can identify the features supported by the terminal based on the strength information of WUS. That is, different strength information of WUS will indicate different features supported by the terminal to the network-side device.

[0104] For example: when the RSRP value of WUS is in the range [0, 30), it indicates that the terminal supports the feature of small data transmission based on random access; when the RSRP value of WUS is in the range [30, 60), it indicates that the terminal supports the feature of small data transmission based on configuration authorization.

[0105] In some embodiments of this application, the temporal location information of the WUS includes at least one of the following: the symbol where the WUS transmission is located, the time slot where the WUS transmission is located, the subframe where the WUS transmission is located, the window where the WUS transmission is located, and the time point where the WUS transmission is located.

[0106] In some embodiments of this application, each feature can correspond to a time-domain location range of WUS. The network-side device can identify the features supported by the terminal based on the time-domain location information of WUS. That is, different time-domain location information of WUS will indicate different features supported by the terminal to the network-side device.

[0107] In some embodiments of this application, the frequency domain location information of the WUS includes at least one of the following: the resource element (RE) where the WUS transmission is located, the resource element (RB) where the WUS transmission is located, the frequency band where the WUS transmission is located, the frequency point where the WUS transmission is located, and the frequency domain window where the WUS transmission is located.

[0108] In some embodiments of this application, each feature can correspond to a frequency domain location range of WUS. The network-side device can identify the features supported by the terminal based on the frequency domain location information of WUS. That is, different frequency domain location information of WUS will indicate different features supported by the terminal to the network-side device.

[0109] In some embodiments of this application, the port information of the WUS mentioned above includes at least one of the following: port index and number of ports.

[0110] In some embodiments of this application, the port information of WUS is different, and the terminal-supported features indicated to the network-side device are also different.

[0111] In some embodiments of this application, the WUS signal itself is composed of a sequence.

[0112] In some embodiments of this application, the sequence information of the WUS mentioned above includes at least one of the following: sequence type, sequence index, sequence length, number of repetitions of the sequence, sequence format, and sequence cyclic shift.

[0113] In some embodiments of this application, the sequence information of WUS is different, and the terminal-supported features indicated to the network-side device are also different.

[0114] In some embodiments of this application, the scrambling sequence information of the WUS mentioned above includes at least one of the following: the type of scrambling sequence, the index of the scrambling sequence, the length of the scrambling sequence, the number of repetitions of the scrambling sequence, and the format of the scrambling sequence.

[0115] In some embodiments of this application, the scrambling sequence information of WUS is different, and the terminal-supported features indicated to the network-side device are also different.

[0116] In some embodiments of this application, the reference signal associated with the WUS mentioned above includes at least one of the following: a synchronization signal block (SSB) and a channel state information reference signal (CSI-RS).

[0117] In some embodiments of this application, each feature may correspond to a reference signal associated with WUS or an index of the reference signal. The network-side device can identify the features supported by the terminal based on the reference signal associated with WUS. That is, different reference signals associated with WUS indicate different features supported by the terminal to the network-side device.

[0118] In some embodiments of this application, each feature can correspond to a WUS type. The network-side device can identify the features supported by the terminal based on the type of WUS. That is, different WUS types indicate different terminal-supported features to the network-side device.

[0119] In some embodiments of this application, each feature can correspond to a type of reference signal associated with WUS. The network-side device can identify the features supported by the terminal based on the type of reference signal associated with WUS. That is, different types of reference signals associated with WUS indicate different features supported by the terminal to the network-side device.

[0120] In some embodiments of this application, the first object mentioned above is SRS;

[0121] The features supported by the terminal are indicated by at least one of the following:

[0122] Is an SRS transmission occurring?

[0123] SRS intensity information;

[0124] SRS temporal location information;

[0125] SRS frequency domain location information;

[0126] SRS port information;

[0127] SRS sequence information;

[0128] SRS transmission pattern;

[0129] The reference signal associated with SRS;

[0130] Types of SRS;

[0131] The type of reference signal associated with the SRS.

[0132] It is understandable that the terminal can use SRS to indicate the features it supports to the network-side device.

[0133] In some embodiments of this application, the network-side device can determine the features supported by the terminal by judging whether SRS is being sent.

[0134] For example, when SRS is being transmitted, the terminal is instructed to support the feature of small data transmission based on configured grant (CG).

[0135] In some embodiments of this application, the intensity information of the SRS mentioned above includes at least one of the following: RSRP, RSRQ, RSSI, SINR.

[0136] In some embodiments of this application, each feature can correspond to a strength range of SRS. The network-side device can identify the features supported by the terminal based on the SRS strength information. That is, different SRS strength information indicates different features supported by the terminal to the network-side device.

[0137] In some embodiments of this application, the time-domain location information of the SRS includes at least one of the following: the symbol where the SRS is transmitted, the time slot where the SRS is transmitted, the subframe where the SRS is transmitted, the window where the SRS is transmitted, and the time point where the SRS is transmitted.

[0138] In some embodiments of this application, each feature can correspond to a time-domain location range of SRS. The network-side device can identify the features supported by the terminal based on the time-domain location information of SRS. That is, different time-domain location information of SRS will indicate different features supported by the terminal to the network-side device.

[0139] In some embodiments of this application, the frequency domain location information of the SRS includes at least one of the following: the RE where the SRS is transmitted, the RB where the SRS is transmitted, the frequency band where the SRS is transmitted, the frequency point where the SRS is transmitted, and the frequency domain window where the SRS is transmitted.

[0140] In some embodiments of this application, each feature can correspond to a frequency domain location range of SRS. The network-side device can identify the features supported by the terminal based on the frequency domain location information of SRS. That is, different frequency domain location information of SRS will indicate different features supported by the terminal to the network-side device.

[0141] In some embodiments of this application, the port information of the SRS mentioned above includes at least one of the following: the port index and the number of ports.

[0142] In some embodiments of this application, the port information of the SRS is different, and the terminal-supported features indicated to the network-side device are also different.

[0143] In some embodiments of this application, the sequence information of the SRS may include at least one of the following: the sequence index of the SRS signal, the cyclic shift number of the SRS signal sequence, and the sequence length of the SRS signal.

[0144] In some embodiments of this application, the sequence information of the SRS is different, and the terminal-supported features indicated to the network-side device are also different.

[0145] In some embodiments of this application, each feature can correspond to a transmission mode of SRS. The network-side device can identify the features supported by the terminal based on the transmission mode of SRS. That is, different transmission modes of SRS indicate different features supported by the terminal to the network-side device.

[0146] In some embodiments of this application, the reference signal associated with the SRS mentioned above includes at least one of the following: SSB, CSI-RS.

[0147] In some embodiments of this application, each feature may correspond to a reference signal associated with an SRS or an index of a reference signal. The network-side device can identify the features supported by the terminal based on the reference signal associated with the SRS. That is, different reference signals associated with the SRS indicate different features supported by the terminal to the network-side device.

[0148] In some embodiments of this application, each feature can correspond to an SRS type. The network-side device can identify the features supported by the terminal based on the SRS type. That is, different SRS types indicate different features supported by the terminal to the network-side device.

[0149] In some embodiments of this application, each feature can correspond to a type of reference signal associated with the SRS. The network-side device can identify the features supported by the terminal based on the type of reference signal associated with the SRS. That is, different types of reference signals associated with the SRS will indicate different features supported by the terminal to the network-side device.

[0150] In some embodiments of this application, when the first object is any of the following: message Msg3, message Msg5, message MsgA PUSCH, the features supported by the terminal are indicated by at least one of the following:

[0151] Bitmap on the first object;

[0152] Information bits or fields on the first object;

[0153] The first object carries the logical channel identifier of the information;

[0154] The first object carries the information of the Enhanced Logical Channel Identifier (eLCID);

[0155] The terminal identifier carried by the first object;

[0156] Specific fields in the Radio Resource Control (RRC) message carried by the first object;

[0157] The sequence information of the demodulation reference signal (DMRS) of the first object;

[0158] The port information of the DMRS of the first object;

[0159] The scrambling sequence of the first object;

[0160] Waveform information of the first object.

[0161] In some embodiments of this application, when a bitmap with different bits exists on the first object, it is used to indicate different characteristics of the terminal. For example, when an 8-bit bitmap exists on the first object, it is used to indicate that the terminal supports the feature of on-demand paging transmission. When a 5-bit bitmap exists on the first object, it is used to indicate that the terminal supports the feature of on-demand PDCCH transmission.

[0162] In some embodiments of this application, each feature may correspond to an information bit or field on a first object. The network-side device can identify the features supported by the terminal based on the information bits or fields on the first object. That is, different information bits or fields on the first object indicate different features supported by the terminal to the network-side device.

[0163] In some embodiments of this application, each bit corresponding to the bitmap on the first object can be used to indicate a feature of the terminal. For example, when there is a specific 8-bit bitmap on the first object, each bit can correspond to a feature of the terminal, and whether the bit is 1 can indicate whether the terminal supports the feature.

[0164] In some embodiments of this application, each feature can correspond to an LCID. The network-side device can identify the features supported by the terminal based on the LCID of the information carried by the first object. That is, if the LCID of the information carried by the first object is different, the features supported by the terminal indicated to the network-side device will also be different.

[0165] In some embodiments of this application, each feature can correspond to an eLCID. The network-side device can identify the features supported by the terminal based on the eLCID of the information carried by the first object. That is, if the eLCID of the information carried by the first object is different, the features supported by the terminal indicated to the network-side device will also be different.

[0166] In some embodiments of this application, each feature can correspond to a range of terminal identifiers. The network-side device can identify the features supported by the terminal based on the terminal identifier carried by the first object. That is, different terminal identifiers carried by the first object indicate different features supported by the terminal to the network-side device.

[0167] In some embodiments of this application, the RRC message carried by the first object includes, but is not limited to, at least one of the following: RRCSetupRequest, RRCResumeRequest, RRCResumeRequest1, RRCReestablishmentRequest, and RRCSystemInfoRequest.

[0168] In some embodiments of this application, each feature may correspond to a specific field in an RRC message, and the network-side device may identify the features supported by the terminal based on the specific field in the RRC message carried by the first object.

[0169] For example, a specific field in an RRC message can be the spare field.

[0170] In some embodiments of this application, the sequence information of the DMRS of the first object is different, and the terminal-supported features indicated to the network-side device are also different.

[0171] In some embodiments of this application, the port information of the DMRS of the first object is different, and the terminal supported features indicated to the network-side device are also different.

[0172] In some embodiments of this application, the scrambling sequence of the first object is different, and the terminal-supported features indicated to the network-side device are also different.

[0173] In some embodiments of this application, the waveform information of the first object is different, and the terminal-supported features indicated to the network-side device are also different.

[0174] In some embodiments of this application, when the first object is PRACH, the features supported by the terminal are indicated by at least one of the following:

[0175] Preamble information for PRACH;

[0176] PRACH random access opportunity (RO) information;

[0177] Temporal location information of PRACH;

[0178] Frequency domain location information of PRACH;

[0179] PRACH port information;

[0180] PRACH sequence information;

[0181] The reference signal associated with PRACH;

[0182] Types of PRACH;

[0183] The type of reference signal associated with PRACH.

[0184] In some embodiments of this application, the preamble information of the PRACH mentioned above may include at least one of the following: the index of the preamble, the number of preambles, the type of preamble, and the format of the preamble.

[0185] For example, an association can be established between the index of the preamble and the features supported by the terminal, so that after receiving the PRACH, the network-side device can know the features supported by the terminal through the index of the preamble selected by the terminal for PRACH transmission.

[0186] In some embodiments of this application, the RO information of the PRACH described above may include at least one of the following: the location of the RO, the number of frequency domain ROs, the number of time domain ROs, and the mapping relationship between the ROs and the reference signal.

[0187] In some examples, a correlation can be established between the location of the RO and the features supported by the terminal, so that when the network-side device detects a PRACH sent by the terminal at a specific RO location, it can know the features supported by the terminal based on the established correlation.

[0188] In some examples, a correlation can be established between the number of frequency domain ROs and the features supported by the terminal, so that after the network-side device detects the PRACH sent by the terminal in a specific number of frequency domain ROs, it can know the features supported by the terminal based on the established correlation.

[0189] In some examples, a correlation can be established between the number of time-domain ROs and the features supported by the terminal, so that after the network-side device detects the PRACH sent by the terminal in a specific number of time-domain ROs, it can know the features supported by the terminal based on the established correlation.

[0190] In some examples, an association can be established between reference signals mapped to the RO and the features supported by the terminal, so that the network-side device can know the features supported by the terminal based on the established association after the RO detects the PRACH sent by the terminal.

[0191] It should be noted that the detailed description of the terminal-supported features indicated by the time-domain location information, frequency-domain location information, port information, sequence information, reference signal associated with the PRACH, type of PRACH, and type of reference signal associated with the PRACH can be found in the above embodiments, where the terminal-supported features are indicated by WUS, and will not be repeated here.

[0192] In the communication method provided in this application embodiment, since the terminal can indicate the features supported by the terminal to the network-side device, the network-side device can use the features supported by the terminal to communicate with the terminal, thereby achieving more efficient communication.

[0193] In some embodiments of this application, as shown in FIG2 and FIG3, the above step 201 can be specifically implemented by the following step 201a.

[0194] Step 201a: The terminal sends the first object and the second object to the network-side device.

[0195] In the embodiments of this application, the first object is used to indicate a first feature among the features supported by the terminal, and the second object is used to indicate a second feature among the features supported by the terminal.

[0196] In the embodiments of this application, the first object and the second object are different.

[0197] In some embodiments of this application, the first feature described above may be multiple features supported by the terminal, a combination of features supported by the terminal, or a merged feature. Similarly, the second feature described above may be multiple features supported by the terminal, a combination of features supported by the terminal, or a merged feature.

[0198] It is understandable that a terminal can use a combination of multiple methods to indicate multiple features supported by the terminal, or to use a combination of multiple methods to indicate a specific feature in a combination of features supported by the terminal.

[0199] In some examples, the terminal may first indicate the first characteristic (e.g., a combination of high-priority or early characteristics) via WUS, and then indicate the second characteristic via at least one of other means (e.g., PRACH or MsgA PUSCH).

[0200] In some examples, the terminal may first indicate the first characteristic (e.g., a combination of high-priority or early characteristics) via PRACH, and then indicate the second characteristic via at least one of other means (e.g., Msg3 or MsgA PUSCH).

[0201] For example, the terminal can instruct the terminal to support repeated transmissions by combining features, and then instruct the terminal to support repeated PUCCH transmissions by using Msg3 PUSCH.

[0202] In some examples, the terminal may first indicate the first characteristic (e.g., a combination of some high-priority or early characteristics) via PRACH, or MsgA and MsgA PUSCH, and then indicate the second characteristic via at least one of other means (e.g., Msg3 or Msg5).

[0203] In some examples, the terminal may first indicate the first characteristic (such as a combination of some high-priority or early characteristics) via WUS and PRACH, or WUS and MsgA or MsgA PUSCH, and then indicate the second characteristic via at least one of other means (such as Msg3 or Msg5).

[0204] In some examples, the terminal can first indicate the merged features via PRACH, and then indicate whether a specific feature in the merged features is supported via at least one of the other methods mentioned above.

[0205] In some examples, the terminal may first indicate the merged features using at least one of the other methods mentioned above, and then indicate whether a specific feature in the merged features is supported via PRACH.

[0206] For example, the terminal can first indicate that it supports repetition via WUS or SRS signals, and then report that it only supports Msg1 repetition by combining features.

[0207] In some embodiments of this application, the second object mentioned above includes at least one of the following: PRACH, WUS signal, PUSCH, SRS, message Msg3, message Msg5, message MsgA, PUSCH, first uplink channel, and first signal.

[0208] In some embodiments of this application, the transmission time of the first object described above satisfies at least one of the following:

[0209] It is located between the SSB detection time of the synchronization signal block and the PRACH transmission time;

[0210] It is located between the SSB detection time and the MsgA transmission time;

[0211] Between the WUS transmission time when SSB transmission is activated and the SSB detection time;

[0212] It occurs between the WUS transmission time requesting SSB transmission and the SSB detection time.

[0213] It is located between the SIB1 detection time and the PRACH transmission time;

[0214] It is located between the SIB1 detection time and the MsgA transmission time;

[0215] It occurs between the Other System Information (OSI) detection time and the PRACH transmission time;

[0216] It lies between the OSI detection time and the MsgA transmission time;

[0217] Between the WUS transmission time when SIB1 transmission is activated and the SIB1 reception time;

[0218] It is located between the WUS transmission time that requests SIB1 transmission and the SIB1 reception time;

[0219] It is located between the WUS transmission time when OSI transmission is activated and the SIB1 reception time;

[0220] It is located between the WUS transmission time requesting OSI transmission and the SIB1 reception time;

[0221] It is located between the SIB1 transmission time and the PRACH transmission time;

[0222] It is located between the SIB1 transmission time and the MsgA transmission time;

[0223] It lies between the paging time and the PRACH transmission time;

[0224] It lies between the paging time and the MsgA transmission time;

[0225] It occurs between the WUS transmission time when paging transmission is activated and the paging detection time;

[0226] It occurs between the WUS transmission time requesting paging transmission and the paging detection time;

[0227] Between the WUS transmission time when PRACH transmission is activated and the PRACH transmission time;

[0228] It is between the WUS transmission time when PRACH transmission is activated and the MsgA transmission time;

[0229] It occurs between the WUS transmission time requesting PRACH transmission and the PRACH transmission time.

[0230] It occurs between the WUS transmission time requesting PRACH transmission and the MsgA transmission time.

[0231] It occurs between the WUS transmission time when MsgA transmission is activated and the PRACH transmission time.

[0232] Between the WUS transmission time when MsgA transmission is activated and the MsgA transmission time;

[0233] It occurs between the WUS transmission time requesting MsgA transmission and the PRACH transmission time;

[0234] It occurs between the WUS transmission time that requests MsgA transmission and the MsgA transmission time.

[0235] Same as WUS transmission time;

[0236] It lies between the first-level SSB detection time and the second-level SSB detection time;

[0237] It occurs between the first-level SSB detection time and the WUS transmission time used to activate the second-level SSB.

[0238] In some embodiments of this application, MsgA can be MsgA PRACH, MsgA PUSCH, or MsgA PRACH and MsgA PUSCH.

[0239] In some embodiments of this application, when WUS is a WUS-A message and the WUS-A message includes a WUS preamble part and a PUSCH part (similar to the MsgA preamble part and MsgA PUSCH part included in the MsgA in the NR 2step RACH process), the first object can be carried in the WUS-A PUSCH part.

[0240] In some embodiments of this application, the WUS described above can be a signal used for at least one of the following resources: trigger SSB, SIB, OSI, PRACH, MsgA, CORESET, Paging, etc. It may contain only a sequence or a sequence and payload portion.

[0241] In some embodiments of this application, when the terminal supports two levels of SSB, the transmission time of the first object can be between the first level SSB detection time and the second level SSB detection time, or between the first level SSB detection time and the WUS transmission time used to activate the second level SSB.

[0242] It should be noted that for a detailed description of the transmission time of the second object and the FC reporting time, please refer to the relevant description of the transmission time of the first object in the above embodiments, which will not be repeated here.

[0243] In some embodiments of this application, the features supported by the terminal include at least one of the following:

[0244] RACH-based Small Data Transfer (SDT)

[0245] CG-based Small Data Transmission (SDT);

[0246] Paging-based Small Data Transmission (SDT)

[0247] Paging-based uplink small data transmission (UL SDT);

[0248] Paging-based downlink small data transmission (DL SDT);

[0249] Base station side subband full duplex (SBFD);

[0250] Terminal-side sub-band full-duplex;

[0251] On-demand SSB transmission;

[0252] On-demand SIB1 transmission;

[0253] On-demand OSI transmission;

[0254] On-demand PRACH transmission;

[0255] On-demand Physical Downlink Control Channel (PDCCH) transmission;

[0256] On-demand paging transmission;

[0257] Discontinuous Reception (DRX) at the base station;

[0258] Discontinuous Transmission (DTX) at the base station;

[0259] Discontinuous reception on the terminal side;

[0260] Discontinuous transmission on the terminal side;

[0261] Cluster paging;

[0262] Non-uniform paging;

[0263] Paging alert notification;

[0264] Paging Resilient Notification;

[0265] Two-step SSB or two-level SSB;

[0266] SSB without a Physical Broadcast Channel (PBCH);

[0267] SSB consists of only the Primary Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS);

[0268] Preset cycle SSB;

[0269] Non-uniform SSB period;

[0270] SSB group-RO mapping;

[0271] PRACH-based beam training;

[0272] SRS-based beam training;

[0273] Message Msg1 is transmitted repeatedly;

[0274] Message Msg3 is transmitted repeatedly;

[0275] Message MsgA is transmitted repeatedly;

[0276] Repeated transmission of the Physical Uplink Control Channel (PUCCH);

[0277] Two-step random access (2-step RACH);

[0278] Four-step random access (4-step RACH);

[0279] Competition-based PUSCH access;

[0280] PRACH based on Orthogonal Covering Codes (OCC);

[0281] OCC-based message Msg3;

[0282] OCC-based message MsgA PUSCH;

[0283] CG PUSCH based on OCC;

[0284] WUS based on OCC;

[0285] Communication based on Artificial Intelligence (AI);

[0286] Sensing based on the random access process;

[0287] Intelligent metasurface (RIS) transport;

[0288] Low Power Wide Area (LPWA) communication;

[0289] Non-terrestrial network (NTN) communication;

[0290] Ambient IoT (AIOT) reader;

[0291] AIoT devices;

[0292] Multi-codeword PDSCH transmission;

[0293] Multi-time-domain unit (PDSCH) transmission;

[0294] Multiple-PDSCH transmission;

[0295] Rate-Splitting Multiple Access (RSMA);

[0296] Multi-User Superposition Transmission (MUST);

[0297] CSI-RS in disconnected state;

[0298] SRS in disconnected state;

[0299] Reduced Capability (Redcap);

[0300] The target waveform includes at least one of the following: downlink orthogonal time-frequency space modulation (OTFS), discrete fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM), and uplink orthogonal time-frequency space modulation (OTFS).

[0301] It should be noted that the terminal-supported features listed in the embodiments of this application do not constitute a limitation on the terminal-supported features. The terminal may also report other terminal-supported features to the network-side device, such as: full duplex (FD), cross-duplex (XDD), time division duplex (TDD), half duplex, energy saving, etc.

[0302] For example, the above TDD can also be understood as: halfduplex.

[0303] In some embodiments of this application, the above-mentioned paging-based small data transmission includes, but is not limited to, at least one of the following: paging PDCCH, PDSCH transmission directly scheduled by the Paging Physical Downlink Shared Channel (PDSCH), PUSCH transmission directly scheduled by the Paging PDSCH, early data transmission carried by the paging PDCCH, and early data transmission carried by the Paging PDSCH.

[0304] For example, the aforementioned early data transmission can be understood as: data transmission before entering the connected state.

[0305] In some embodiments of this application, when the terminal supports the aforementioned base station-side sub-band full-duplex feature, it means that the terminal supports the base station transmitting uplink data on downlink resources and transmitting downlink data on uplink resources.

[0306] In some embodiments of this application, when the terminal supports the aforementioned terminal-side sub-band full-duplex feature, it means that the terminal can simultaneously send and receive uplink and downlink data in the same time slot.

[0307] In some embodiments of this application, when the terminal supports the aforementioned on-demand SSB transmission feature, it means that the terminal is able to receive SSBs on demand.

[0308] In some embodiments of this application, when the terminal supports the aforementioned on-demand SIB1 transmission feature, it means that the terminal is able to receive SIB1 on demand.

[0309] In some embodiments of this application, when the terminal supports the aforementioned on-demand PRACH transmission feature, it means that the terminal is able to send PRACH on demand.

[0310] In some embodiments of this application, the aforementioned on-demand PRACH transmission may refer to on-demand RO resources (On-demand RO).

[0311] In some embodiments of this application, when the terminal supports the feature of configuring RO resources on demand, it means that the terminal can send data on demand at random access times.

[0312] In some embodiments of this application, the on-demand PDCCH transmission described above can be represented as a control resource set (CORESET resource) that appears or is configured on demand.

[0313] For example, the control resource set that appears or is configured on demand can be on demand CORESET#0.

[0314] In some embodiments of this application, stage-1 of the above two-stage SSB (2-stage SSB) can be a public SSB, and stage-2 can be a feature-specific SSB. All types of terminals can receive stage-1 SSB, while only some types of terminals can receive stage-2 SSB.

[0315] In some embodiments of this application, the above two steps of SSB can be LP-SS+SSB in LP-WUS case.

[0316] In some embodiments of this application, the two SSB steps described above can be wideband SSB + punctured narrowband SSB in LPWA case.

[0317] In some embodiments of this application, the features supported by the terminal include, but are not limited to, at least one of the following: SSB without PBCH, SSB with only PSS and SSS. The features supported by the terminal may also include at least one of the following: SSB with only PSS, SSB with only SSS, SSB with only PBCH, SSB with only PSS and PBCH, SSB with only SSS and PBCH, SSB without PSS, SSB without SSS, etc.

[0318] In some embodiments of this application, when the terminal supports a preset period SSB feature, it means that the terminal can detect an SSB of the preset period. This preset period can be a large period, such as 160ms, 320ms, 640ms, etc.

[0319] In some embodiments of this application, when the terminal supports the non-uniform period SSB feature, it means that the terminal is able to detect the non-uniform period SSB.

[0320] In some embodiments of this application, when the terminal supports the feature of PUCCH repetition, PUCCH repetition can be: PUCCH repetition with HARQ ACK.

[0321] In some embodiments of this application, when the terminal supports the feature of OCC-based PRACH, it means that the terminal can support OCC-based random access.

[0322] In some embodiments of this application, when the terminal supports the OCC-based message Msg3 feature, it means that the terminal is capable of supporting OCC-based message Msg3 transmission.

[0323] In some embodiments of this application, the above-mentioned AI-based communication may include at least one of the following: AI-based SSB selection, AI-based Small Data Transmission (SDT) type selection, AI-based RACH, AI-based Tracking Area (TA) determination, etc.

[0324] In some embodiments of this application, when the terminal supports the feature of an environmental IoT reader / writer, it means that the terminal supports communication with AIoT devices and base stations. The terminal can obtain information from the AIoT device and forward it to the network-side device, and can also forward information sent by the network-side device to the AIoT device.

[0325] In some embodiments of this application, when the terminal supports the characteristic of an AIoT device, it means that the terminal itself is an AIoT device and can support direct communication with the base station.

[0326] In some embodiments of this application, when the terminal supports the aforementioned multi-codeword PDSCH transmission feature, it means that the terminal supports transmitting a PDSCH through multiple spatial units, which may include, but are not limited to, multiple codewords.

[0327] For example, when the terminal supports the aforementioned multi-codeword PDSCH transmission feature, the SIB1 PDSCH supports multi-codeword or spatial multiplexing transmission.

[0328] In some embodiments of this application, the above-mentioned multi-time domain unit PDSCH transmission, namely TB processing over multiple slots (TBoMS), means that one transport block (TB) can be mapped to multiple time domain units, or in other words, the TB mapped on the multiple time domain units corresponds to one PDSCH.

[0329] In some embodiments of this application, the above-described multi-time-domain unit (PDSCH) transmission can also be referred to as cross-time-domain unit (PDSCH) transmission. When the time-domain unit is a time slot, multi-time-domain unit (PDSCH) can also be referred to as TB processing over multiple time slots.

[0330] For example, when the terminal supports the aforementioned multi-time-domain unit (PDSCH) transmission feature, the SIB1 PDSCH supports transmission across multiple slots.

[0331] In some embodiments of this application, when the terminal supports the aforementioned multi-PDSCH transmission feature, it means that the terminal supports splitting the large-size TB into multiple smaller-size TBs, with each TB corresponding to one PDSCH and each PDSCH transmitted through one timeslot, thereby enabling the transmission of the large-size first information through multi-timeslot PDSCH transmission.

[0332] For example, when the terminal supports the aforementioned multiple-PDSCH transmission feature, SIB1 supports multiple-PDSCH transmission.

[0333] In some embodiments of this application, when the terminal supports RSMA, it can indicate that the terminal supports RSMA for SDT transmission.

[0334] In some embodiments of this application, when the terminal supports the MUST feature, it can indicate that the terminal supports MUST for transmitting paging PDSCH.

[0335] In some embodiments of this application, when the terminal supports SRS in a disconnected state, it can indicate that the terminal supports the transmission of early SRS or the reception of early CSI-RS.

[0336] In some embodiments of this application, when the target waveform includes DL OTFS, it can indicate that the DL channel supports OTFS waveform during the random access phase; when the target waveform includes DL DFT-s-OFDM, it can indicate that the DL channel supports DFT-s-OFDM waveform during the random access phase; when the target waveform includes UL OTFS, it can indicate that the UL channel supports OTFS waveform during the random access phase.

[0337] In some embodiments of this application, the communication method provided in the embodiments of this application may further include the following step 301.

[0338] It should be noted that, in conjunction with Figure 2 and Figure 4, the terminal can execute the following step 301 before executing step 201.

[0339] Step 301: The terminal merges at least some of the features it supports.

[0340] It is understandable that the terminal can report the merged features to the network-side device after merging at least some of the features supported by the terminal.

[0341] In the embodiments of this application, the combined characteristics described above include at least one of the following:

[0342] Small data transfer;

[0343] Downlink small data transmission;

[0344] Mobile Terminated-SDT (MT-SDT) is a small data transfer service for called parties.

[0345] Uplink small data transmission;

[0346] Caller transmits small data;

[0347] Sub-belt full-duplex;

[0348] Full-duplex;

[0349] Energy saving;

[0350] Terminal energy saving;

[0351] Network energy saving;

[0352] On-demand transmission or on-demand transmission channels;

[0353] Downlink transmission on demand or downlink channel for transmission on demand;

[0354] On-demand uplink transmission or uplink channel for on-demand transmission;

[0355] Centralized channel configuration;

[0356] Discontinuous reception;

[0357] Discontinuous transmission;

[0358] Repeated transmission;

[0359] Early repeated transmissions;

[0360] Uplink repeated transmission;

[0361] Downlink repeated transmission;

[0362] Preset bandwidth communication;

[0363] Specific terminal type;

[0364] Specific coverage level;

[0365] Non-orthogonal transmission;

[0366] Preset TB transfer;

[0367] Preset TB broadcast channel;

[0368] OCC transmission;

[0369] Random access transmission.

[0370] In some embodiments of this application, the above-mentioned small data transmission may include at least two of the following: RACH-based small data transmission, CG-based small data transmission, paging-based small data transmission, paging-based uplink small data transmission, and paging-based downlink small data transmission.

[0371] For example, the above-mentioned paging-based small data transmission may include at least two of the following: paging-based uplink small data transmission and paging-based downlink small data transmission.

[0372] It is understandable that a terminal can combine at least two of the following features into one: RACH-based small data transmission, CG-based small data transmission, paging-based small data transmission, paging-based uplink small data transmission, and paging-based downlink small data transmission. Then, after the network-side device receives the terminal's indication that the terminal supports small data transmission, the network-side device can know that the terminal supports at least two of the following features: RACH-based small data transmission, CG-based small data transmission, paging-based small data transmission, paging-based uplink small data transmission, and paging-based downlink small data transmission.

[0373] In some embodiments of this application, the downlink small data transmission may include at least two of the following: RACH-based small data transmission, CG-based small data transmission, and paging-based downlink small data transmission.

[0374] In some embodiments of this application, the downlink small data transmission described above can be understood as called small data transmission.

[0375] In some embodiments of this application, the aforementioned uplink small data transmission may include: paging-based uplink small data transmission.

[0376] In some embodiments of this application, the aforementioned uplink small data transmission can be understood as mainline small data transmission.

[0377] In some embodiments of this application, the aforementioned subband full-duplex may include: base station-side subband full-duplex and terminal-side subband full-duplex.

[0378] In some embodiments of this application, the full-duplex mentioned above may include at least two of the following: base station side subband full-duplex, terminal side subband full-duplex, and frequency division duplexing (FDD).

[0379] In some embodiments of this application, the full-duplex mode described above may also be referred to as XDD.

[0380] In some embodiments of this application, the above-mentioned energy saving may include: energy saving on the base station side and energy saving on the terminal side.

[0381] It is understandable that the terminal can combine all energy-saving methods on the base station side and all energy-saving methods on the terminal side into a single feature.

[0382] In some embodiments of this application, the terminal can combine all energy-saving methods on the terminal side into one feature to obtain the terminal energy-saving feature.

[0383] In some embodiments of this application, the terminal can combine all energy-saving methods on the base station side into one feature to obtain the network energy-saving feature.

[0384] In some embodiments of this application, the above-mentioned on-demand transmission may include at least two of the following:

[0385] On-demand SSB transmission;

[0386] On-demand SIB1 transmission;

[0387] On-demand OSI transmission;

[0388] On-demand PRACH transfer;

[0389] On-demand PDCCH transmission;

[0390] On-demand paging transmission.

[0391] In some embodiments of this application, the above-mentioned on-demand transmission may also be referred to as an on-demand transmission channel (On-demand Tx, i.e., OD Tx).

[0392] It is understandable that a terminal can combine at least two features from on-demand SSB transmission, on-demand SIB1 transmission, on-demand OSI transmission, on-demand PRACH transmission, on-demand PDCCH transmission, and on-demand paging transmission into one feature.

[0393] In some embodiments of this application, the above-mentioned on-demand downlink transmission may include at least two of all on-demand downlink common channels: SSB, SIB1, common SS0, OSI, WUS, Positioning Reference Signal (PRS), Phase-tracking Reference Signals (PTRS), and CSI-RS.

[0394] In some embodiments of this application, the above-mentioned on-demand downlink transmission can also be referred to as the on-demand downlink channel (On-demand DL Tx, i.e., OD DL Tx).

[0395] In some embodiments of this application, the above-mentioned on-demand uplink transmission may include at least two of all on-demand uplink common channels: PRACH, UL WUS, SRS, PUCCH, CG-PUSCH, and PTRS.

[0396] In some embodiments of this application, the above-mentioned on-demand uplink transmission can also be referred to as the on-demand uplink channel (On-demand UL Tx, i.e., OD UL Tx).

[0397] In some embodiments of this application, the channels configured in the centralized manner described above may include at least two of the common downlink channels in all centralized configurations: SSB, SIB1, common SS0, OSI, WUS, PRS, PTRS, and CSI-RS.

[0398] In some embodiments of this application, the channels in the centralized configuration described above may include at least two of the common uplink channels in all centralized configurations: PRACH, UL WUS, SRS, PUCCH, CG-PUSCH, and PTRS.

[0399] In some embodiments of this application, the above-mentioned discontinuous reception may include: discontinuous reception on the base station side and discontinuous reception on the terminal side.

[0400] In some embodiments of this application, the aforementioned discontinuous transmission may include: discontinuous transmission on the base station side and discontinuous transmission on the terminal side.

[0401] In some embodiments of this application, the above-mentioned repeated transmission may include at least two of the following: repeated transmission of message Msg1, repeated transmission of message Msg3, repeated transmission of message MsgA, and repeated transmission of PUCCH.

[0402] In some embodiments of this application, the above-mentioned repeated transmission can be understood as coverage transmission.

[0403] It is understandable that the terminal can combine at least two of the following characteristics into one characteristic: repeated transmission of message Msg1, repeated transmission of message Msg3, repeated transmission of message MsgA, and repeated transmission of PUCCH.

[0404] In some embodiments of this application, the aforementioned early retransmission may include at least two of the following: retransmission of message Msg1 in the disconnected state, retransmission of message Msg3 in the disconnected state, retransmission of message MsgA in the disconnected state, and retransmission of PUCCH in the disconnected state.

[0405] In some embodiments of this application, the above-mentioned uplink repeated transmission may include at least two of the following: repeated transmission of message Msg1, repeated transmission of message Msg3, repeated transmission of message MsgA, repeated transmission of PUCCH, repeated transmission of SRS, repeated transmission of CG PUSCH, repeated transmission of PUSCH in RACH-less process, repeated transmission of WUS, and repeated transmission of DMRS.

[0406] In some embodiments of this application, the downlink repetitive transmissions described above may include at least two of the following: SSB repetitive transmission, SIB1 repetitive transmission, CORESET repetitive transmission, PRS repetitive transmission, CSI-RS repetitive transmission, Tracking Reference Signal (TRS) repetitive transmission, PTRS repetitive transmission, paging repetitive transmission, message Msg2 repetitive transmission, message MsgB repetitive transmission, message Msg4 repetitive transmission, and WUS repetitive transmission.

[0407] In some embodiments of this application, the above-mentioned preset bandwidth communication can be low bandwidth communication, for example: communication of all channels at 3MHz is combined into one feature, and communication under other bandwidths is combined into one feature.

[0408] In some embodiments of this application, the terminal may combine features related to Low Power Wide Area (LPWA) terminals into one feature, or combine features related to Extended Reality (XR) with high speed and low latency into one feature, or combine features related to Internet of Things (IoT) or AIoT into one feature, to obtain a feature specific to the terminal type.

[0409] In some embodiments of this application, the terminal can merge communication transmission characteristics of the same coverage level into one characteristic to obtain the characteristic of a specific coverage level.

[0410] In some embodiments of this application, the terminal can combine the characteristics of non-orthogonal technologies such as MUST and RSMA into one characteristic to obtain the non-orthogonal transmission characteristic.

[0411] In some embodiments of this application, the above-mentioned non-orthogonal transmission may also be referred to as non-orthogonal multiple access (NOMA) technology.

[0412] In some embodiments of this application, the preset TB transmission or preset TB broadcast channel includes at least two of the following: multi-codeword PDSCH transmission, multi-time-domain unit PDSCH transmission, multiple PDSCH transmission, rate split multiple access (RSMA), and multi-user superimposed transmission (MUST).

[0413] In some embodiments of this application, the aforementioned preset TB transmission can be a large TB transmission.

[0414] In some embodiments of this application, the aforementioned preset TB broadcast channel can be a large TB broadcast channel.

[0415] In some embodiments of this application, the above-mentioned OCC transmission may include at least two of the following:

[0416] PRACH based on OCC;

[0417] OCC-based message Msg3;

[0418] OCC-based message MsgA PUSCH;

[0419] CG PUSCH based on OCC;

[0420] WUS based on OCC.

[0421] In some embodiments of this application, the above-described random access transmission may include at least two of the following:

[0422] Two-step random access;

[0423] Four-step random access;

[0424] Competition-based PUSCH access.

[0425] It is understandable that a terminal can combine at least two features from two-step random access, four-step random access, and contention-based PUSCH access into one feature.

[0426] In this way, since some of the features supported by the terminal can be merged before being reported, the problem of each feature receiving too few preambles, which increases the probability of terminal collisions, is avoided, while also saving the overhead of terminal feature reporting.

[0427] In some embodiments of this application, the terminal combines at least a portion of the features it supports, including at least one of the following:

[0428] Merge features related to small data transmission;

[0429] Combine the full-duplex related features of the sub-band;

[0430] Merge full-duplex related features;

[0431] Combine energy-saving features;

[0432] Combine features related to on-demand delivery;

[0433] Combine channel-related features for on-demand transmission;

[0434] Merge the centralized configuration channel-related features;

[0435] Combine features related to discontinuous reception;

[0436] Merge features related to discontinuous transmission;

[0437] Merge features related to repeated transmissions;

[0438] Combine the transmission characteristics of preset bandwidth communication;

[0439] Merge the transmission characteristics of the same terminal type;

[0440] Merge transmission characteristics with the same coverage level;

[0441] Combine the characteristics related to non-orthogonal transmission;

[0442] Merge features related to PDSCH transmission;

[0443] Merge features related to OCC transmission;

[0444] Merge features related to random access.

[0445] In some embodiments of this application, the above-mentioned merging of small data transmission related features can be achieved by merging at least two features from RACH-based small data transmission, CG-based small data transmission, paging-based uplink small data transmission, and paging-based downlink small data transmission to obtain the feature of small data transmission.

[0446] In some embodiments of this application, the above-mentioned merging of subband full-duplex related features can be achieved by merging base station-side subband full-duplex and terminal-side subband full-duplex to obtain the subband full-duplex feature.

[0447] In some embodiments of this application, the above-mentioned merging of full-duplex-related features can be achieved by merging at least two features from base station-side subband full-duplex, terminal-side subband full-duplex, and FDD to obtain the full-duplex feature.

[0448] In some embodiments of this application, the above-mentioned merging of energy-saving related features can be achieved by merging energy saving on the base station side and energy saving on the terminal side to obtain the energy-saving feature.

[0449] In some embodiments of this application, the above-mentioned merging of on-demand transmission-related features can be achieved by merging at least two features from on-demand SSB transmission, on-demand SIB1 transmission, on-demand OSI transmission, on-demand PRACH transmission, on-demand PDCCH transmission, and on-demand paging transmission to obtain the on-demand transmission feature.

[0450] In some embodiments of this application, the above-mentioned merging of features related to centralized configuration channels can be achieved by merging at least two features from all centralized configuration common downlink channels to obtain the feature of centralized configuration channel.

[0451] In some embodiments of this application, the above-mentioned merging of discontinuous reception-related features can be achieved by merging base station-side discontinuous reception and terminal-side discontinuous reception to obtain the discontinuous reception feature.

[0452] In some embodiments of this application, the above-mentioned merging of discontinuous transmission-related features can be achieved by merging discontinuous transmission on the base station side and discontinuous transmission on the terminal side to obtain the discontinuous transmission feature.

[0453] In some embodiments of this application, the above-mentioned merging of the repeat transmission-related features can be achieved by merging at least two features among repeat transmission of message Msg1, repeat transmission of message Msg3, repeat transmission of message MsgA, and repeat transmission of PUCCH to obtain the repeat transmission feature.

[0454] In some embodiments of this application, the above-mentioned merging of the transmission characteristics of preset bandwidth communication can be used to merge the transmission characteristics of low bandwidth communication, for example, merging the communication of all channels of 3MHz into one characteristic.

[0455] In some embodiments of this application, the above-mentioned merging of transmission characteristics of the same terminal type can be to merge characteristics related to LPWA terminals into one characteristic, or to merge characteristics related to XR with high speed and low latency into one characteristic, or to merge characteristics related to IoT or AIoT into one characteristic, so as to obtain the characteristic of a specific terminal type.

[0456] In some embodiments of this application, the above-mentioned merging of non-orthogonal transmission-related features can be used to merge the features of non-orthogonal technologies such as MUST and RSMA into one feature to obtain the non-orthogonal transmission feature.

[0457] In some embodiments of this application, the above-mentioned merging of PDSCH transmission-related features can be the merging of at least two features from multi-codeword PDSCH transmission, multi-time-domain unit PDSCH transmission, multiple PDSCH transmission, rate split multiple access (RSMA), and multi-user overlay transmission (MUST) to obtain the feature of preset TB transmission or preset TB broadcast channel.

[0458] In some embodiments of this application, the above-mentioned merging of OCC transmission-related features can be achieved by merging at least two features from OCC-based PRACH, OCC-based message Msg3, OCC-based message MsgA PUSCH, OCC-based CG PUSCH, and OCC-based WUS to obtain the OCC transmission feature.

[0459] In some embodiments of this application, the above-mentioned merging of random access-related features can be the merging of at least two features from two-step random access, four-step random access, and contention-based PUSCH access to obtain the random access transmission feature.

[0460] Figure 5 is a flowchart illustrating the communication method provided in an embodiment of this application. As shown in Figure 5, the communication method may include the following steps 401 to 403.

[0461] Step 401: The terminal sends the first object to the network-side device.

[0462] Step 402: The network-side device receives the first object sent by the terminal.

[0463] Step 403: The network-side device communicates with the terminal using the features supported by the terminal.

[0464] It should be noted that the relevant explanations and beneficial effects of steps 401 to 403 above can be found in the descriptions in the above embodiments, and will not be repeated here.

[0465] It should be noted that the SSB in the embodiments of this application can also be described as any other module representing at least one of transmitting synchronization signals, and / or physical broadcast channels and other broadcast channels or their scheduling and control channels. For example, it can also be called 6G-SSB. It can also be at least one of CSI-RS, PRS, Paging, and multicast signals.

[0466] The WUS described in this invention can also be broadly defined as a signal used to wake up or activate a specific signal or channel.

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

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

[0469] The communication device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0470] Specifically, referring to Figure 6, when the communication device is a terminal or a component in a terminal, the communication device 800 includes a sending module 801 for sending a first object to a network-side device. The first object is used for at least one of the following: indicating features supported by the terminal; requesting the network-side device to use the features supported by the terminal to communicate with the terminal.

[0471] The communication device provided in this application embodiment enables more efficient communication because the terminal can indicate the features it supports to the network-side device.

[0472] In some possible implementations, the first object includes at least one of the following: WUS, PUSCH, SRS, message Msg3, message Msg5, message MsgA, PUSCH, PRACH, first uplink channel, and first signal;

[0473] The first uplink channel is the uplink channel sent by the terminal to the network-side device before entering the connected state; the first signal is the signal sent by the terminal to the network-side device before entering the connected state.

[0474] In some possible implementations, the first object is WUS;

[0475] The features supported by the terminal are indicated by at least one of the following:

[0476] Is WUS transmission present?

[0477] WUS intensity information;

[0478] WUS's temporal location information;

[0479] WUS frequency domain location information;

[0480] WUS port information;

[0481] WUS sequence information;

[0482] WUS scrambling sequence information;

[0483] The reference signal associated with WUS;

[0484] Types of WUS;

[0485] The type of reference signal associated with WUS.

[0486] In some possible implementations, the first object is SRS;

[0487] The features supported by the terminal are indicated by at least one of the following:

[0488] Is an SRS transmission occurring?

[0489] SRS intensity information;

[0490] SRS temporal location information;

[0491] SRS frequency domain location information;

[0492] SRS port information;

[0493] SRS sequence information;

[0494] SRS transmission mode;

[0495] The reference signal associated with SRS;

[0496] Types of SRS;

[0497] The type of reference signal associated with the SRS.

[0498] In some possible implementations, the first object is any of the following: message Msg3, message Msg5, message MsgA PUSCH;

[0499] The features supported by the terminal are indicated by at least one of the following:

[0500] Bitmap on the first object;

[0501] Information bits or fields on the first object;

[0502] The first object carries the LCID information;

[0503] The first object carries the information in its eLCID;

[0504] The terminal identifier carried by the first object;

[0505] Specific fields in the RRC message carried by the first object;

[0506] The sequence information of the DMRS of the first object;

[0507] The port information of the DMRS of the first object;

[0508] The scrambling sequence of the first object;

[0509] Waveform information of the first object.

[0510] In some possible implementations, the first object is PRACH;

[0511] The features supported by the terminal are indicated by at least one of the following:

[0512] Preamble information for PRACH;

[0513] RO information for PRACH;

[0514] Temporal location information of PRACH;

[0515] Frequency domain location information of PRACH;

[0516] PRACH port information;

[0517] PRACH sequence information;

[0518] The reference signal associated with PRACH;

[0519] Types of PRACH;

[0520] The type of reference signal associated with PRACH.

[0521] In some possible implementations, the terminal sends a first object to the network-side device, including:

[0522] The terminal sends the first object and the second object to the network-side device;

[0523] Wherein, the first object is used to indicate the first feature among the features supported by the terminal, and the second object is used to indicate the second feature among the features supported by the terminal.

[0524] The first object is different from the second object.

[0525] In some possible implementations, the second object includes at least one of the following: PRACH, WUS signal, PUSCH, SRS, message Msg3, message Msg5, message MsgA, PUSCH, first uplink channel, and first signal.

[0526] In some possible implementations, the sending time of the first object satisfies at least one of the following:

[0527] It lies between the SSB detection time and the PRACH transmission time;

[0528] It is located between the SSB detection time and the MsgA transmission time;

[0529] Between the WUS transmission time when SSB transmission is activated and the SSB detection time;

[0530] It occurs between the WUS transmission time requesting SSB transmission and the SSB detection time.

[0531] It is located between the SIB1 detection time and the PRACH transmission time;

[0532] It is located between the SIB1 detection time and the MsgA transmission time;

[0533] It lies between the OSI detection time and the PRACH transmission time;

[0534] It lies between the OSI detection time and the MsgA transmission time;

[0535] Between the WUS transmission time when SIB1 transmission is activated and the SIB1 reception time;

[0536] It is located between the WUS transmission time that requests SIB1 transmission and the SIB1 reception time;

[0537] It is located between the WUS transmission time when OSI transmission is activated and the SIB1 reception time;

[0538] It is located between the WUS transmission time requesting OSI transmission and the SIB1 reception time;

[0539] It is located between the SIB1 transmission time and the PRACH transmission time;

[0540] It is located between the SIB1 transmission time and the MsgA transmission time;

[0541] It lies between the paging time and the PRACH transmission time;

[0542] It lies between the paging time and the MsgA transmission time;

[0543] It occurs between the WUS transmission time when paging transmission is activated and the paging detection time;

[0544] It occurs between the WUS transmission time requesting paging transmission and the paging detection time;

[0545] Between the WUS transmission time when PRACH transmission is activated and the PRACH transmission time;

[0546] It is between the WUS transmission time when PRACH transmission is activated and the MsgA transmission time;

[0547] It occurs between the WUS transmission time requesting PRACH transmission and the PRACH transmission time.

[0548] It occurs between the WUS transmission time requesting PRACH transmission and the MsgA transmission time.

[0549] It occurs between the WUS transmission time when MsgA transmission is activated and the PRACH transmission time.

[0550] Between the WUS transmission time when MsgA transmission is activated and the MsgA transmission time;

[0551] It occurs between the WUS transmission time requesting MsgA transmission and the PRACH transmission time;

[0552] It occurs between the WUS transmission time that requests MsgA transmission and the MsgA transmission time.

[0553] Same as WUS transmission time;

[0554] It lies between the first-level SSB detection time and the second-level SSB detection time;

[0555] This occurs between the first-level SSB detection time and the WUS transmission time used to activate the second-level SSB. In some possible implementations, the terminal supports at least one of the following features:

[0556] Small data transfer based on RACH;

[0557] Small data transmission based on CG;

[0558] Small data transmission based on paging;

[0559] Uplink small data transmission based on paging;

[0560] Downlink small data transmission based on paging;

[0561] Base station side sub-band full-duplex;

[0562] Terminal-side sub-band full-duplex;

[0563] On-demand SSB transmission;

[0564] On-demand SIB1 transmission;

[0565] On-demand OSI transmission;

[0566] On-demand PRACH transfer;

[0567] On-demand PDCCH transmission;

[0568] On-demand paging transmission;

[0569] Discontinuous reception at the base station;

[0570] Discontinuous transmission at the base station;

[0571] Discontinuous reception on the terminal side;

[0572] Discontinuous transmission on the terminal side;

[0573] Gathering for paging;

[0574] Non-uniform paging;

[0575] Paging alarm notification;

[0576] Paging flexible notification;

[0577] Two-step SSB or two-level SSB;

[0578] SSB without PBCH;

[0579] SSB with only PSS and SSS;

[0580] Preset cycle SSB;

[0581] Non-uniform periodic SSB;

[0582] Mapping from SSB group to RO;

[0583] PRACH-based beam training;

[0584] SRS-based beam training;

[0585] Message Msg1 is transmitted repeatedly;

[0586] Message Msg3 is transmitted repeatedly;

[0587] Message MsgA is transmitted repeatedly;

[0588] PUCCH is transmitted repeatedly;

[0589] Two-step random access;

[0590] Four-step random access;

[0591] Competition-based PUSCH access;

[0592] PRACH based on OCC;

[0593] OCC-based message Msg3;

[0594] OCC-based message MsgA PUSCH;

[0595] CG PUSCH based on OCC;

[0596] WUS based on OCC;

[0597] AI-based communication;

[0598] Perception based on the random access process;

[0599] RIS transport;

[0600] LPWA communications;

[0601] NTN communications;

[0602] AIOT reader / writer;

[0603] AIOT devices;

[0604] Multi-codeword PDSCH transmission;

[0605] Multi-time-domain unit (PDSCH) transmission;

[0606] Multiple PDSCH transmissions;

[0607] RSMA;

[0608] MUST;

[0609] CSI-RS in disconnected state;

[0610] SRS in disconnected state;

[0611] Reduce ability;

[0612] The target waveform includes at least one of the following: downlink orthogonal time-frequency control waveform, discrete Fourier transform extended orthogonal frequency division multiplexing waveform, and uplink orthogonal time-frequency control waveform.

[0613] In some possible implementations, the communication apparatus provided in this application embodiment further includes: a processing module. The processing module is used to merge at least a portion of the features supported by the terminal;

[0614] The merged characteristics include at least one of the following:

[0615] Small data transfer;

[0616] Downlink small data transmission;

[0617] Caller's small data transmission;

[0618] Uplink small data transmission;

[0619] Caller transmits small data;

[0620] Sub-belt full-duplex;

[0621] Full-duplex;

[0622] Energy saving;

[0623] Terminal energy saving;

[0624] Network energy saving;

[0625] On-demand transmission or on-demand transmission channels;

[0626] Downlink transmission on demand or downlink channel for transmission on demand;

[0627] On-demand uplink transmission or uplink channel for on-demand transmission;

[0628] Centralized channel configuration;

[0629] Discontinuous reception;

[0630] Discontinuous transmission;

[0631] Repeated transmission;

[0632] Early repeated transmissions;

[0633] Uplink repeated transmission;

[0634] Downlink repeated transmission;

[0635] Preset bandwidth communication;

[0636] Specific terminal type;

[0637] Specific coverage level;

[0638] Non-orthogonal transmission;

[0639] Preset TB transfer;

[0640] Preset TB broadcast channel;

[0641] OCC transmission;

[0642] Random access transmission.

[0643] In some possible implementations, small data transmission includes at least two of the following: RACH-based small data transmission, CG-based small data transmission, paging-based small data transmission, paging-based uplink small data transmission, and paging-based downlink small data transmission.

[0644] Among some possible implementations, downlink small data transmission includes at least two of the following: RACH-based small data transmission, CG-based small data transmission, and paging-based downlink small data transmission.

[0645] In some possible implementations, subband full-duplex includes: base station-side subband full-duplex and terminal-side subband full-duplex.

[0646] In some possible implementations, full-duplex includes at least two of the following: base station-side subband full-duplex, terminal-side subband full-duplex, and FDD.

[0647] In some possible implementations, on-demand delivery includes at least two of the following:

[0648] On-demand SSB transmission;

[0649] On-demand SIB1 transmission;

[0650] On-demand OSI transmission;

[0651] On-demand PRACH transfer;

[0652] On-demand PDCCH transmission;

[0653] On-demand paging transmission.

[0654] In some possible implementations, discontinuous reception includes: base station-side discontinuous reception and terminal-side discontinuous reception;

[0655] Discontinuous transmission includes both base station-side discontinuous transmission and terminal-side discontinuous transmission.

[0656] In some possible implementations, repeated transmission includes at least two of the following: repeated transmission of message Msg1, repeated transmission of message Msg3, repeated transmission of message MsgA, and repeated transmission of PUCCH.

[0657] In some possible implementations, the preset TB transmission or preset TB broadcast channel includes at least two of the following: multi-codeword PDSCH transmission, multi-time-domain unit PDSCH transmission, multiple PDSCH transmission, RSMA, and MUST.

[0658] In some possible implementations, OCC transmission includes at least two of the following:

[0659] PRACH based on OCC;

[0660] OCC-based message Msg3;

[0661] OCC-based message MsgA PUSCH;

[0662] CG PUSCH based on OCC;

[0663] WUS based on OCC.

[0664] In some possible implementations, random access transport includes at least two of the following:

[0665] Two-step random access;

[0666] Four-step random access;

[0667] Competition-based PUSCH access.

[0668] In some possible implementations, the terminal merges at least a portion of the features it supports, including at least one of the following:

[0669] Merge features related to small data transmission;

[0670] Combine the full-duplex related features of the sub-band;

[0671] Merge full-duplex related features;

[0672] Combine energy-saving features;

[0673] Combine features related to on-demand delivery;

[0674] Combine channel-related features for on-demand transmission;

[0675] Merge the centralized configuration channel-related features;

[0676] Combine features related to discontinuous reception;

[0677] Merge features related to discontinuous transmission;

[0678] Merge features related to repeated transmissions;

[0679] Combine the transmission characteristics of preset bandwidth communication;

[0680] Merge the transmission characteristics of the same terminal type;

[0681] Merge transmission characteristics with the same coverage level;

[0682] Combine the characteristics related to non-orthogonal transmission;

[0683] Merge features related to PDSCH transmission;

[0684] Merge features related to OCC transmission;

[0685] Merge features related to random access.

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

[0687] As shown in Figure 7, this application embodiment also provides a communication device 2000, including a processor 2001 and a memory 2002. The memory 2002 stores a program or instructions that can be executed on the processor 2001. For example, when the communication device 2000 is a terminal, when the program or instructions are executed by the processor 2001, they implement the various steps of the above-described communication method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0688] This application 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 the steps in the above method embodiments. This terminal embodiment corresponds to the above terminal-side method embodiments, and all implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be the communication device shown in FIG6. Specifically, FIG8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

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

[0690] Those skilled in the art will understand that terminal 100 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 8 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.

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

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

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

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

[0695] The radio frequency unit 101 is used to send a first object to the network-side device, wherein the first object is used for at least one of the following:

[0696] Indicates the features supported by the terminal;

[0697] The network-side device is requested to communicate with the terminal using the features supported by the terminal.

[0698] The terminal provided in this application embodiment can indicate the features it supports to the network-side device, so the network-side device can use the features supported by the terminal to communicate with the terminal, thereby achieving more efficient communication.

[0699] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above method embodiments and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0700] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0701] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. 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.

[0702] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0704] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0705] This application also provides a communication system, including a terminal and a network-side device, wherein the terminal can be used to perform the steps of the communication method described above.

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

[0707] 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 the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0708] 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, the method comprising: The terminal sends a first object to the network-side device, the first object being used for at least one of the following: Indicates the features supported by the terminal; The network-side device is requested to communicate with the terminal using the features supported by the terminal.

2. The method of claim 1, wherein, The first object includes at least one of the following: wake-up signal WUS, physical uplink shared channel PUSCH, channel sounding reference signal SRS, message Msg3, message Msg5, message MsgA PUSCH, physical random access channel PRACH, first uplink channel, and first signal; Wherein, the first uplink channel is the uplink channel sent by the terminal to the network-side device before entering the connected state; the first signal is the signal sent by the terminal to the network-side device before entering the connected state.

3. The method of claim 2, wherein, The first object is WUS; The features supported by the terminal are indicated by at least one of the following: Does the WUS transmission exist? The intensity information of the WUS; The time-domain location information of the WUS; The frequency domain location information of the WUS; The port information of the WUS; The sequence information of the WUS; The scrambling sequence information of the WUS; The reference signal associated with the WUS; The type of WUS; The type of reference signal associated with the WUS.

4. The method of claim 2, wherein, The first object is SRS; The features supported by the terminal are indicated by at least one of the following: Whether the SRS is being transmitted; The intensity information of the SRS; The time-domain location information of the SRS; The frequency domain location information of the SRS; The port information of the SRS; The sequence information of the SRS; The transmission mode of the SRS; The reference signal associated with the SRS; The type of SRS; The type of reference signal associated with the SRS.

5. The method of claim 2, wherein, The first object is any one of the following: message Msg3, message Msg5, message MsgA PUSCH; The features supported by the terminal are indicated by at least one of the following: The bitmap on the first object; Information bits or fields on the first object; The first object carries the logical channel identifier (LCID). The first object carries the enhanced logical channel identifier (eLCID). The terminal identifier carried by the first object; Specific fields in the Radio Resource Control (RRC) message carried by the first object; The sequence information of the demodulation reference signal DMRS of the first object; The DMRS port information of the first object; The scrambling sequence of the first object; Waveform information of the first object.

6. The method of claim 2, wherein, The first object is PRACH; The features supported by the terminal are indicated by at least one of the following: The preamble information of the PRACH; The random access opportunity (RO) information of the PRACH; The temporal location information of the PRACH; The frequency domain location information of the PRACH; The port information of the PRACH; The sequence information of the PRACH; The reference signal associated with the PRACH; The type of PRACH; The type of reference signal associated with the PRACH.

7. The method of claim 1 or 2, wherein, The terminal sends a first object to the network-side device, including: The terminal sends the first object and the second object to the network-side device; Wherein, the first object is used to indicate a first feature among the features supported by the terminal, and the second object is used to indicate a second feature among the features supported by the terminal; The first object is different from the second object.

8. The method according to claim 7, wherein, The second object includes at least one of the following: physical random access channel PRACH, WUS signal, PUSCH, SRS, message Msg3, message Msg5, message MsgA, PUSCH, first uplink channel, and first signal.

9. The method of claim 1, wherein, The sending time of the first object satisfies at least one of the following: It is located between the SSB detection time of the synchronization signal block and the PRACH transmission time; It is located between the SSB detection time and the MsgA transmission time; Between the WUS transmission time when SSB transmission is activated and the SSB detection time; It occurs between the WUS transmission time requesting SSB transmission and the SSB detection time. It is located between the SIB1 detection time and the PRACH transmission time; It is located between the SIB1 detection time and the MsgA transmission time; It lies between the OSI detection time of other system messages and the PRACH transmission time; It lies between the OSI detection time and the MsgA transmission time; Between the WUS transmission time when SIB1 transmission is activated and the SIB1 reception time; It is located between the WUS transmission time that requests SIB1 transmission and the SIB1 reception time; It is located between the WUS transmission time when OSI transmission is activated and the SIB1 reception time; It is located between the WUS transmission time requesting OSI transmission and the SIB1 reception time; It is located between the SIB1 transmission time and the PRACH transmission time; It is located between the SIB1 transmission time and the MsgA transmission time; It lies between the paging time and the PRACH transmission time; It lies between the paging time and the MsgA transmission time; It occurs between the WUS transmission time when paging transmission is activated and the paging detection time; It occurs between the WUS transmission time requesting paging transmission and the paging detection time; Between the WUS transmission time when PRACH transmission is activated and the PRACH transmission time; It is between the WUS transmission time when PRACH transmission is activated and the MsgA transmission time; It occurs between the WUS transmission time requesting PRACH transmission and the PRACH transmission time. It occurs between the WUS transmission time requesting PRACH transmission and the MsgA transmission time. It occurs between the WUS transmission time when MsgA transmission is activated and the PRACH transmission time. Between the WUS transmission time when MsgA transmission is activated and the MsgA transmission time; It occurs between the WUS transmission time requesting MsgA transmission and the PRACH transmission time; It occurs between the WUS transmission time that requests MsgA transmission and the MsgA transmission time. Same as WUS transmission time; It lies between the first-level SSB detection time and the second-level SSB detection time; It occurs between the first-level SSB detection time and the WUS transmission time used to activate the second-level SSB.

10. The method according to any one of claims 1 to 9, wherein, The terminal supports at least one of the following features: Small data transmission based on Random Access Channel (RACH); Small data transfer based on configuration-authorized CG; Small data transmission based on paging; Uplink small data transmission based on paging; Downlink small data transmission based on paging; Base station side sub-band full-duplex; Terminal-side sub-band full-duplex; On-demand SSB transmission; On-demand transmission of system information blocks (SIB1); On-demand OSI transmission; On-demand PRACH transfer; On-demand physical downlink control channel (PDCCH) transmission; On-demand paging transmission; Discontinuous reception at the base station; Discontinuous transmission at the base station; Discontinuous reception on the terminal side; Discontinuous transmission on the terminal side; Gathering for paging; Non-uniform paging; Paging alarm notification; Paging flexible notification; Two-step SSB or two-level SSB; SSB without a physical broadcast channel PBCH; Only the SSB of the primary synchronization signal PSS and the secondary synchronization signal SSS; Preset cycle SSB; Non-uniform periodic SSB; Mapping from SSB group to RO; PRACH-based beam training; SRS-based beam training; Message Msg1 is transmitted repeatedly; Message Msg3 is transmitted repeatedly; Message MsgA is transmitted repeatedly; Repeated transmission of the Physical Uplink Control Channel (PUCCH); Two-step random access; Four-step random access; Competition-based PUSCH access; PRACH based on orthogonal covering code OCC; OCC-based message Msg3; OCC-based message MsgA PUSCH; CG PUSCH based on OCC; WUS based on OCC; Communication based on artificial intelligence (AI); Perception based on the random access process; Intelligent metasurface RIS transport; Low-power, wide-coverage LPWA communication; Non-terrestrial network (NTN) communication; Environmental IoT AIoT reader / writer; AIOT devices; Multi-codeword PDSCH transmission; Multi-time-domain unit (PDSCH) transmission; Multiple PDSCH transmissions; Rate Split Multiple Access (RSMA); Multi-user overlay transmission MUST; Channel State Information Reference Signal (CSI-RS) in the disconnected state; SRS in disconnected state; Reduce ability; The target waveform includes at least one of the following: downlink orthogonal time-frequency control waveform, discrete Fourier transform extended orthogonal frequency division multiplexing waveform, and uplink orthogonal time-frequency control waveform.

11. The method according to any one of claims 1 to 10, wherein, The method further includes: The terminal merges at least a portion of the features it supports; The merged characteristics include at least one of the following: Small data transfer; Downlink small data transmission; The called party transmits small data. Uplink small data transmission; Caller transmits small data; Sub-belt full-duplex; Full-duplex; Energy saving; Terminal energy saving; Network energy saving; On-demand transmission or on-demand transmission channels; Downlink transmission on demand or downlink channel for transmission on demand; On-demand uplink transmission or uplink channel for on-demand transmission; Centralized channel configuration; Discontinuous reception; Discontinuous transmission; Repeated transmission; Early repeated transmissions; Uplink repeated transmission; Downlink repeated transmission; Preset bandwidth communication; Specific terminal type; Specific coverage level; Non-orthogonal transmission; Preset transfer block TB transfer; Preset TB broadcast channel; OCC transmission; Random access transmission.

12. The method of claim 11, wherein, The small data transmission includes at least two of the following: RACH-based small data transmission, CG-based small data transmission, paging-based small data transmission, paging-based uplink small data transmission, and paging-based downlink small data transmission.

13. The method of claim 11, wherein, The downlink small data transmission includes at least two of the following: RACH-based small data transmission, CG-based small data transmission, and paging-based downlink small data transmission.

14. The method according to claim 11, wherein, The subband full-duplex includes: base station-side subband full-duplex and terminal-side subband full-duplex.

15. The method of claim 11, wherein, The full-duplex includes at least two of the following: base station side subband full-duplex, terminal side subband full-duplex, and frequency division duplex (FDD).

16. The method of claim 11, wherein, The on-demand transmission includes at least two of the following: On-demand SSB transmission; On-demand SIB1 transmission; On-demand OSI transmission; On-demand PRACH transfer; On-demand PDCCH transmission; On-demand paging transmission.

17. The method of claim 11, wherein, The discontinuous reception includes: discontinuous reception on the base station side and discontinuous reception on the terminal side; The discontinuous transmission includes: discontinuous transmission on the base station side and discontinuous transmission on the terminal side.

18. The method according to claim 11, wherein, The repeated transmission includes at least two of the following: repeated transmission of message Msg1, repeated transmission of message Msg3, repeated transmission of message MsgA, and repeated transmission of PUCCH.

19. The method according to claim 11, wherein, The preset TB transmission or preset TB broadcast channel includes at least two of the following: multi-codeword PDSCH transmission, multi-time-domain unit PDSCH transmission, multiple PDSCH transmission, RSMA, and MUST.

20. The method according to claim 11, wherein, The OCC transmission includes at least two of the following: PRACH based on OCC; OCC-based message Msg3; OCC-based message MsgA PUSCH; CG PUSCH based on OCC; WUS based on OCC.

21. The method according to claim 11, wherein, The random access transmission includes at least two of the following: Two-step random access; Four-step random access; Competition-based PUSCH access.

22. The method according to claim 11, wherein, The terminal integrates at least a portion of the features it supports, including at least one of the following: Merge features related to small data transmission; Combine the full-duplex related features of the sub-band; Merge full-duplex related features; Combine energy-saving features; Combine features related to on-demand delivery; Combine channel-dependent features for on-demand transmission; Merge the centralized configuration channel-related features; Combine features related to discontinuous reception; Merge features related to discontinuous transmission; Merge features related to repeated transmissions; Combine the transmission characteristics of preset bandwidth communication; Merge the transmission characteristics of the same terminal type; Merge transmission characteristics with the same coverage level; Merge the characteristics related to non-orthogonal transmission; Merge features related to PDSCH transmission; Merge features related to OCC transmission; Merge features related to random access.

23. A communication device, the device comprising: Sending module; The sending module is configured to send a first object to a network-side device, wherein the first object is used for at least one of the following: Indicates the features supported by the terminal; The network-side device is requested to communicate with the terminal using the features supported by the terminal.

24. The apparatus according to claim 23, wherein, The first object includes at least one of the following: WUS, PUSCH, SRS, message Msg3, message Msg5, message MsgA, PUSCH, PRACH, first uplink channel, and first signal; Wherein, the first uplink channel is the uplink channel sent by the terminal to the network-side device before entering the connected state; the first signal is the signal sent by the terminal to the network-side device before entering the connected state.

25. The apparatus according to claim 23 or 24, wherein, The sending module is specifically used to send the first object and the second object to the network-side device; Wherein, the first object is used to indicate a first feature among the features supported by the terminal, and the second object is used to indicate a second feature among the features supported by the terminal; The first object is different from the second object.

26. The apparatus according to claim 23, wherein, The sending time of the first object satisfies at least one of the following: It lies between the SSB detection time and the PRACH transmission time; It is located between the SSB detection time and the MsgA transmission time; Between the WUS transmission time when SSB transmission is activated and the SSB detection time; It occurs between the WUS transmission time requesting SSB transmission and the SSB detection time. It is located between the SIB1 detection time and the PRACH transmission time; It is located between the SIB1 detection time and the MsgA transmission time; It lies between the OSI detection time and the PRACH transmission time; It lies between the OSI detection time and the MsgA transmission time; Between the WUS transmission time when SIB1 transmission is activated and the SIB1 reception time; It is located between the WUS transmission time that requests SIB1 transmission and the SIB1 reception time; It is located between the WUS transmission time when OSI transmission is activated and the SIB1 reception time; It is located between the WUS transmission time requesting OSI transmission and the SIB1 reception time; It is located between the SIB1 transmission time and the PRACH transmission time; It is located between the SIB1 transmission time and the MsgA transmission time; It lies between the paging time and the PRACH transmission time; It lies between the paging time and the MsgA transmission time; It occurs between the WUS transmission time when paging transmission is activated and the paging detection time; It occurs between the WUS transmission time requesting paging transmission and the paging detection time; Between the WUS transmission time when PRACH transmission is activated and the PRACH transmission time; It is between the WUS transmission time when PRACH transmission is activated and the MsgA transmission time; It occurs between the WUS transmission time requesting PRACH transmission and the PRACH transmission time. It occurs between the WUS transmission time requesting PRACH transmission and the MsgA transmission time. It occurs between the WUS transmission time when MsgA transmission is activated and the PRACH transmission time. Between the WUS transmission time when MsgA transmission is activated and the MsgA transmission time; It occurs between the WUS transmission time requesting MsgA transmission and the PRACH transmission time; It occurs between the WUS transmission time that requests MsgA transmission and the MsgA transmission time. Same as WUS transmission time; It lies between the first-level SSB detection time and the second-level SSB detection time; It occurs between the first-level SSB detection time and the WUS transmission time used to activate the second-level SSB.

27. The apparatus according to any one of claims 23 to 26, wherein, The terminal supports at least one of the following features: small data transmission based on RACH; Small data transmission based on CG; Small data transmission based on paging; Uplink small data transmission based on paging; Downlink small data transmission based on paging; Base station side sub-band full-duplex; Terminal-side sub-band full-duplex; On-demand SSB transmission; On-demand SIB1 transmission; On-demand OSI transmission; On-demand PRACH transfer; On-demand PDCCH transmission; On-demand paging transmission; Discontinuous reception at the base station; Discontinuous transmission at the base station; Discontinuous reception on the terminal side; Discontinuous transmission on the terminal side; Gathering for paging; Non-uniform paging; Paging alarm notification; Paging flexible notification; Two-step SSB or two-level SSB; SSB without PBCH; SSB with only PSS and SSS; Preset cycle SSB; Non-uniform SSB period; Mapping from SSB group to RO; PRACH-based beam training; SRS-based beam training; Message Msg1 is transmitted repeatedly; Message Msg3 is transmitted repeatedly; Message MsgA is transmitted repeatedly; PUCCH is transmitted repeatedly; Two-step random access; Four-step random access; Competition-based PUSCH access; PRACH based on OCC; OCC-based message Msg3; OCC-based message MsgA PUSCH; CG PUSCH based on OCC; WUS based on OCC; AI-based communication; Perception based on the random access process; RIS transport; LPWA communications; NTN communications; AIOT reader / writer; AIOT devices; Multi-codeword PDSCH transmission; Multi-time-domain unit (PDSCH) transmission; Multiple PDSCH transmissions; RSMA; MUST; CSI-RS in disconnected state; SRS in disconnected state; Reduce ability; The target waveform includes at least one of the following: downlink orthogonal time-frequency control waveform, discrete Fourier transform extended orthogonal frequency division multiplexing waveform, and uplink orthogonal time-frequency control waveform.

28. The apparatus according to any one of claims 23 to 27, wherein, The device further includes: a processing module; The processing module is used to merge at least a portion of the features supported by the terminal; The merged characteristics include at least one of the following: Small data transfer; Downlink small data transmission; Caller's small data transmission; Uplink small data transmission; Caller transmits small data; Sub-belt full-duplex; Full-duplex; Energy saving; Terminal energy saving; Network energy saving; On-demand transmission or on-demand transmission channels; Downlink transmission on demand or downlink channel for transmission on demand; On-demand uplink transmission or uplink channel for on-demand transmission; Centralized channel configuration; Discontinuous reception; Discontinuous transmission; Repeated transmission; Early repeated transmissions; Uplink repeated transmission; Downlink repeated transmission; Preset bandwidth communication; Specific terminal type; Specific coverage level; Non-orthogonal transmission; Preset TB transfer; Preset TB broadcast channel; OCC transmission; Random access transmission.

29. A terminal comprising 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 communication method as claimed in any one of claims 1 to 22.

30. A readable storage medium storing a program or instructions that, when executed by a processor, implement the communication method as described in any one of claims 1-22.

Images