Communication method and apparatus, and storage medium

Abstract

The present disclosure provides a communication method and apparatus, and a storage medium. According to the present disclosure, a terminal can send, to a network device, capability information for indicating RACH operations supported by the terminal, so as to provide richer information for deploying a RACH process on an SBFD symbol, thereby reducing the complexity of the RACH process on the SBFD symbol, and improving the flexibility of the RACH process on the SBFD symbol.

Description

Communication method, device, and storage medium Technical Field

[0001] The present disclosure relates to the field of communications, and in particular to a communication method and device, and a storage medium. Background Art

[0002] Full-duplex technology plays a vital role in the communications field, enabling bidirectional communication, improving communication efficiency, reducing communication latency, and increasing spectrum utilization. In full-duplex technology, a base station can configure an uplink (UL) subband for uplink transmission within a downlink (DL) timeslot for a sub-band full-duplex (SBFD) terminal. The base station then schedules the terminal's uplink data transmission within the time-frequency range of the UL subband, enabling full-duplex communication.

[0003] Summary of the Invention

[0004] In order to clarify the implementation method of the Random Access Channel (RACH) process on the SBFD symbol, the embodiments of the present disclosure provide a communication method and apparatus, and a storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided a communication method, applied to a terminal, the method comprising:

[0006] Sending capability information to a network device, where the capability information is used to indicate a random access channel (RACH) operation supported by the terminal.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is provided, applied to a network device, the method comprising:

[0008] receiving capability information sent by a terminal, where the capability information is used to indicate RACH operations supported by the terminal;

[0009] Based on the capability information, RACH configuration is provided for the terminal, and / or an association relationship between SSB and RO is determined.

[0010] According to a third aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0011] The transceiver module is configured to send capability information to a network device, where the capability information is used to indicate a random access channel (RACH) operation supported by the terminal.

[0012] According to a fourth aspect of an embodiment of the present disclosure, a network device is provided, including:

[0013] a transceiver module, configured to receive capability information sent by a terminal, where the capability information is used to indicate RACH operations supported by the terminal;

[0014] The processing module is configured to provide RACH configuration for the terminal based on the capability information, and / or determine an association relationship between SSB and RO.

[0015] According to a fifth aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0016] one or more processors;

[0017] The terminal is used to execute the communication method described in the first aspect.

[0018] According to a sixth aspect of an embodiment of the present disclosure, a network device is provided, including:

[0019] one or more processors;

[0020] Wherein, the network device is used to execute the communication method described in the second aspect.

[0021] According to the seventh aspect of an embodiment of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the communication method described in the first aspect, and the network device is configured to implement the communication method described in the second aspect.

[0022] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method as described in any one of the first aspect or the second aspect.

[0023] In an embodiment of the present disclosure, a terminal sends capability information indicating RACH operations supported by the terminal to a network device, and the network device can receive the capability information sent by the terminal, thereby providing a corresponding RACH configuration for the terminal based on the capability information, and / or determining an association relationship between an SSB and a RO, so as to provide more abundant information for deploying a RACH process on an SBFD symbol, reduce the complexity of the RACH process on the SBFD symbol, and improve the flexibility of the RACH process on the SBFD symbol.

[0024] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0026] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0027] FIG2 is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure.

[0028] FIG3A is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0029] FIG3B is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0030] FIG4A is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure.

[0031] FIG4B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure.

[0032] FIG5A is a schematic structural diagram of a communication device 5100 proposed in an embodiment of the present disclosure.

[0033] FIG5B is a schematic structural diagram of a chip 5200 according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0035] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of at least one of the associated listed items.

[0036] It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various messages, these messages should not be limited to these terms. These terms are only used to distinguish messages of the same type from each other. For example, a first message may also be referred to as a second message, and similarly, a second message may be referred to as a first message without departing from the scope of this disclosure. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining."

[0037] The embodiments of the present disclosure provide a communication method, a device, and a storage medium.

[0038] In a first aspect, an embodiment of the present disclosure provides a communication method, applied to a terminal, the method comprising:

[0039] Sending capability information to a network device, where the capability information is used to indicate a random access channel (RACH) operation supported by the terminal.

[0040] In the above embodiment, the terminal sends capability information indicating the RACH operations supported by the terminal to the network device, so as to provide richer information for deploying the RACH process on the SBFD symbols, reduce the complexity of the RACH process on the SBFD symbols, and improve the flexibility of the RACH process on the SBFD symbols.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate at least one of the following:

[0042] Whether the terminal supports sending a physical random access channel PRACH on SBFD symbols;

[0043] whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration, where the first RACH configuration is an additional RACH configuration specifically used for an SBFD random access operation;

[0044] The terminal only supports determining a valid RO on the SBFD symbol based on a second RACH configuration, where the second RACH configuration is a traditional RACH configuration;

[0045] Whether the terminal supports repeated transmission of PRACH;

[0046] Whether the terminal supports different power parameter configurations.

[0047] In the above embodiment, by providing a variety of contents that may be indicated by the capability information, the capability information can be flexibly configured, thereby improving the flexibility of the terminal capability reporting process.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate that the terminal supports determining a valid RO on an SBFD symbol based on the first RACH configuration, and the capability information is further used to indicate at least one of the following:

[0049] The valid RO type supported by the terminal when sending PRACH;

[0050] The terminal considers the valid RO type when determining the association between the synchronization signal block SSB and RO.

[0051] In the above embodiment, by providing other possible contents that the capability information can indicate when the capability information indicates that the terminal supports determining the valid RO on the SBFD symbol based on the first RACH configuration, more possible capability information can be provided when the capability information indicates that the terminal supports determining the valid RO on the SBFD symbol based on the first RACH configuration, thereby improving the flexibility of the terminal capability reporting process, so that the terminal can report richer capability information to the network device.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate a valid RO type supported by the terminal when sending a PRACH, and the capability information is used to indicate any one of the following:

[0053] The terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration;

[0054] The terminal supports sending a PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration.

[0055] In the above embodiment, by providing the specific content that the capability information may indicate when the capability information indicates the valid RO type supported by the terminal when sending PRACH, the capability information can be flexibly configured as needed, so that the capability information can indicate the valid RO type supported by the terminal when sending PRACH, thereby improving the flexibility of the terminal capability reporting process.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate that the terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration, and the valid RO is located on an SBFD symbol or a non-SBFD symbol, or the valid RO is only located on an SBFD symbol.

[0057] In the above embodiment, by providing possible positions of valid ROs when the capability information indicates that the terminal only supports sending PRACH on the valid RO determined based on the first RACH configuration, the position of the valid RO can be flexibly selected as needed, thereby improving the flexibility of the RACH process.

[0058] In combination with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration, and the valid RO determined based on the first RACH configuration is located on an SBFD symbol or a non-SBFD symbol, or the valid RO determined based on the first RACH configuration is located only on an SBFD symbol;

[0059] The valid RO determined based on the second RACH configuration is located on the SBFD symbol or the non-SBFD symbol, or the valid RO determined based on the second RACH configuration is located only on the SBFD symbol.

[0060] In the above embodiment, by providing possible positions of valid ROs determined based on different RACH configurations when the capability information indicates that the terminal supports sending PRACH on a valid RO determined based on a first RACH configuration and a valid RO determined based on a second RACH configuration, the position of the valid RO can be flexibly selected as needed, thereby improving the flexibility of the RACH process.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate the valid RO type considered by the terminal when determining the association relationship between the synchronization signal block SSB and the RO, and for the valid RO determined according to the first RACH configuration, the capability information is used to indicate any one of the following:

[0062] Determine the association between SSB and RO based on all valid ROs;

[0063] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0064] In the above embodiment, when the capability information indicates the valid RO type to be considered when the terminal determines the association relationship between the synchronization signal block SSB and RO, the capability information indicates which valid ROs determined according to the first RACH configuration implement the association relationship between the SSB and RO and how to implement the association relationship between the SSB and RO, so that the implementation method of determining the association relationship between the SSB and RO can be selected as needed, thereby improving the flexibility of the process of determining the association relationship between the SSB and RO.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate the valid RO type considered by the terminal when determining the association relationship between the synchronization signal block SSB and the RO, and for the valid RO determined according to the second RACH configuration, the capability information is used to indicate any one of the following:

[0066] Determine the association relationship between SSB and RO according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol;

[0067] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0068] In the above embodiment, when the capability information indicates the valid RO type to be considered when the terminal determines the association relationship between the synchronization signal block SSB and RO, the capability information indicates which valid ROs determined according to the second RACH configuration implement the association relationship between the SSB and RO and how to implement the association relationship between the SSB and RO, so that the implementation method of determining the association relationship between the SSB and RO can be selected as needed, thereby improving the flexibility of the process of determining the association relationship between the SSB and RO.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the terminal does not support the first RACH configuration.

[0070] In the above embodiment, by setting the terminal not to support the first RACH configuration when the capability information indicates that the terminal only supports determining the valid RO on the SBFD symbol based on the second RACH configuration, it is clarified how the terminal handles the first RACH configuration when only supporting determining the valid RO on the SBFD symbol based on the second RACH configuration, so as to ensure that the RACH operation of the terminal matches the indication of the capability information.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the capability information is used to indicate at least one of the following:

[0072] The terminal only supports sending PRACH on a valid RO located on a non-SBFD symbol determined according to the second RACH configuration;

[0073] The terminal only supports sending PRACH on a valid RO located on a SBFD symbol determined according to the second RACH configuration;

[0074] The terminal supports sending a PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration.

[0075] In the above embodiment, by providing the specific content that the capability information may indicate when the capability information indicates that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, the capability information can be flexibly configured as needed, so that the capability information can realize the indication that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, thereby improving the flexibility of the terminal capability reporting process.

[0076] In combination with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on an SBFD symbol determined according to the second RACH configuration, and the capability information is further used to indicate any one of the following:

[0077] Determine the association between SSB and RO based on all valid ROs;

[0078] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0079] In the above embodiment, by providing other possible contents that the capability information can indicate when the capability information indicates that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration, so that when the capability information indicates that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration, more possible capability information can be provided, the flexibility of the terminal capability reporting process is improved, and the terminal can report richer capability information to the network device.

[0080] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate whether the terminal supports repeated transmission of PRACH, including:

[0081] The capability information is used to indicate whether the terminal supports repeated transmission of PRACH on valid ROs of different symbol types.

[0082] In the above embodiment, when the capability information indicates whether the terminal supports repeated transmission of PRACH, specific content that the capability information may indicate is provided, so that the behavior of the terminal when reporting whether the terminal supports repeated transmission of PRACH can be clarified.

[0083] In conjunction with some embodiments of the first aspect, in some embodiments, the capability information is used to indicate whether the terminal supports different power parameter configurations, and the capability information is used to indicate at least one of the following:

[0084] whether the terminal supports the first RACH configuration and the second RACH configuration having different power parameters;

[0085] Whether the terminal supports valid ROs located on different types of symbols corresponds to different PRACH power parameters.

[0086] In the above embodiment, by providing the specific content that the capability information may indicate when the capability information indicates whether the terminal supports different power parameter configurations, the capability information can be flexibly configured as needed, so that the capability information can indicate whether the terminal supports different power parameter configurations, thereby improving the flexibility of the terminal capability reporting process.

[0087] In combination with some embodiments of the first aspect, in some embodiments, the capability information indicates that the terminal supports that the PRACH corresponding to the valid RO located on different types of symbols has different power parameters, and the power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is the same as the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol; or

[0088] The power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is different from the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol.

[0089] In the above embodiment, by providing an optional implementation method for determining whether the power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is the same as the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol, in which the capability information indicates that the terminal supports different power parameters for the PRACH corresponding to the valid RO located on the different types of symbols, the flexibility of the power parameter configuration process is improved.

[0090] With reference to some embodiments of the first aspect, in some embodiments, the terminal capability indicated by the capability information is a mandatory terminal capability.

[0091] In the above embodiment, the terminal capability indicated by the capability information is configured as a mandatory terminal capability so that the terminal can directly support the capability indicated by the capability information, thereby eliminating the need for the terminal to additionally report the terminal capability, simplifying the interaction process and improving communication efficiency.

[0092] In a second aspect, an embodiment of the present disclosure provides a communication method, applied to a network device, comprising:

[0093] receiving capability information sent by a terminal, where the capability information is used to indicate RACH operations supported by the terminal;

[0094] Based on the capability information, RACH configuration is provided for the terminal, and / or an association relationship between SSB and RO is determined.

[0095] In the above embodiment, the network device receives capability information sent by the terminal and used to indicate the RACH operation supported by the terminal, thereby providing the terminal with corresponding RACH configuration based on the capability information, and / or determining the association relationship between SSB and RO, so as to provide more abundant information for deploying the RACH process on the SBFD symbol, reduce the complexity of the RACH process on the SBFD symbol, and improve the flexibility of the RACH process on the SBFD symbol.

[0096] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate at least one of the following:

[0097] Whether the terminal supports sending PRACH on SBFD symbols;

[0098] whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration, where the first RACH configuration is an additional RACH configuration specifically used for an SBFD random access operation;

[0099] The terminal only supports determining a valid RO on the SBFD symbol based on a second RACH configuration, where the second RACH configuration is a traditional RACH configuration;

[0100] Whether the terminal supports repeated transmission of PRACH;

[0101] Whether the terminal supports different power parameter configurations.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate that the terminal supports determining a valid RO on an SBFD symbol based on the first RACH configuration, and the capability information is further used to indicate at least one of the following:

[0103] The valid RO type supported by the terminal when sending PRACH;

[0104] The valid RO type considered when the terminal determines the association relationship between the SSB and the RO.

[0105] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate a valid RO type supported by the terminal when sending a PRACH, and the capability information is used to indicate any one of the following:

[0106] The terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration;

[0107] The terminal supports sending a PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration.

[0108] In combination with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate that the terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration, and the valid RO is located on an SBFD symbol or a non-SBFD symbol, or the valid RO is only located on an SBFD symbol.

[0109] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration, and the valid RO determined based on the first RACH configuration is located on an SBFD symbol or a non-SBFD symbol, or the valid RO determined based on the first RACH configuration is located only on an SBFD symbol;

[0110] The valid RO determined based on the second RACH configuration is located on the SBFD symbol or the non-SBFD symbol, or the valid RO determined based on the second RACH configuration is located only on the SBFD symbol.

[0111] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate the valid RO type considered by the terminal when determining the association relationship between the synchronization signal block SSB and the RO, and for the valid RO determined according to the first RACH configuration, the capability information is used to indicate any one of the following:

[0112] Determine the association between SSB and RO based on all valid ROs;

[0113] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0114] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate the valid RO type considered by the terminal when determining the association relationship between the synchronization signal block SSB and the RO, and for the valid RO determined according to the second RACH configuration, the capability information is used to indicate any one of the following:

[0115] Determine the association relationship between SSB and RO according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol;

[0116] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0117] In combination with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the terminal does not support the first RACH configuration.

[0118] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the capability information is used to indicate at least one of the following:

[0119] The terminal only supports sending PRACH on a valid RO located on a non-SBFD symbol determined according to the second RACH configuration;

[0120] The terminal only supports sending PRACH on a valid RO located on a SBFD symbol determined according to the second RACH configuration;

[0121] The terminal supports sending a PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration.

[0122] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on an SBFD symbol determined according to the second RACH configuration, and the capability information is further used to indicate any one of the following:

[0123] Determine the association between SSB and RO based on all valid ROs;

[0124] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0125] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate whether the terminal supports repeated transmission of PRACH, including:

[0126] The capability information is used to indicate whether the terminal supports repeated transmission of PRACH on valid ROs of different symbol types.

[0127] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information is used to indicate whether the terminal supports different power parameter configurations, and the capability information is used to indicate at least one of the following:

[0128] whether the terminal supports the first RACH configuration and the second RACH configuration having different power parameters;

[0129] Whether the terminal supports valid ROs located on different types of symbols corresponds to different PRACH power parameters.

[0130] In combination with some embodiments of the second aspect, in some embodiments, the capability information indicates that the terminal supports that the PRACH corresponding to the valid RO located on different types of symbols has different power parameters, and the power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is the same as the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol; or,

[0131] The power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is different from the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol.

[0132] In conjunction with some embodiments of the second aspect, in some embodiments, the capability information sent by the terminal is not received, and the method further includes any one of the following:

[0133] detecting a PRACH sent by the terminal only on a valid RO located on a non-SBFD symbol determined based on the second RACH configuration;

[0134] Detecting a PRACH sent by the terminal only on a valid RO located on an SBFD symbol determined based on the second RACH configuration;

[0135] The PRACH sent by the terminal is detected on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol determined based on the second RACH configuration.

[0136] In the above embodiment, by providing an optional implementation method for the network device to detect the PRACH sent by the terminal when the terminal does not report capability information, the network device can flexibly choose which method to use to detect the PRACH as needed, thereby improving the flexibility of the PRACH detection process.

[0137] In conjunction with some embodiments of the second aspect, in some embodiments, detecting a PRACH sent by a terminal on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined based on the second RACH configuration, the method further includes:

[0138] Determine the association between SSB and RO based on all valid ROs;

[0139] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0140] In the above embodiment, an optional implementation method is provided for the network device to determine the association relationship between the SSB and the RO when the network device detects the PRACH sent by the terminal on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol determined based on the second RACH configuration, so that the network device can flexibly choose which method to use to implement the determination of the association relationship between the SSB and the RO as needed, thereby improving the flexibility of the SSB and RO association process.

[0141] In a third aspect, an embodiment of the present disclosure provides a terminal, including:

[0142] The transceiver module is configured to send capability information to a network device, where the capability information is used to indicate a random access channel (RACH) operation supported by the terminal.

[0143] In a fourth aspect, an embodiment of the present disclosure provides a network device, including:

[0144] a transceiver module, configured to receive capability information sent by a terminal, where the capability information is used to indicate RACH operations supported by the terminal;

[0145] The processing module is configured to provide RACH configuration for the terminal based on the capability information, and / or determine an association relationship between SSB and RO.

[0146] In a fifth aspect, an embodiment of the present disclosure provides a terminal, including:

[0147] one or more processors;

[0148] The terminal is used to execute the communication method described in the first aspect and any embodiment of the first aspect.

[0149] In a sixth aspect, an embodiment of the present disclosure provides a network device, including:

[0150] one or more processors;

[0151] The network device is used to execute the communication method described in the above-mentioned second aspect and any embodiment of the second aspect.

[0152] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, including a terminal and a network device, wherein the terminal is configured to implement the communication method described in the above-mentioned first aspect and any embodiment of the first aspect, and the network device is configured to implement the communication method described in the above-mentioned second aspect and any embodiment of the second aspect.

[0153] In an eighth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the communication method as described in the first aspect and any embodiment of the first aspect, the second aspect and any embodiment of the second aspect.

[0154] In a ninth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the communication method as described in the first aspect and any embodiment of the first aspect, the second aspect and any embodiment of the second aspect.

[0155] In a tenth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the communication method as described in the first aspect and any embodiment thereof, the second aspect and any embodiment thereof.

[0156] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0157] The present disclosure provides a communication method, device, and storage medium. In some embodiments, the terms "communication method" and "information processing method," "terminal capability reporting method," and "terminal capability definition method" are interchangeable; the terms "communication device" and "information processing device," "terminal capability reporting device," and "terminal capability definition device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0158] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0159] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0160] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0161] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0162] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0163] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0164] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0165] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0166] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0167] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0168] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0169] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0170] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0171] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0172] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0173] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0174] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0175] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0176] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0177] FIG1 is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .

[0178] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0179] In some embodiments, the network device 102 includes at least one of an access network device and a core network device.

[0180] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0181] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0182] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0183] In some embodiments, a core network device may be a single device including multiple network elements, or may be multiple devices or device groups, each including all or part of multiple network elements. A network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0184] In some embodiments, the core network device may include a first network element, such as an Access and Mobility Management Function (AMF).

[0185] In some embodiments, the first network element is used for user access management and mobility management, but is not limited thereto.

[0186] In some embodiments, the core network device may include a second network element, which is, for example, a session management function (SMF).

[0187] In some embodiments, the second network element is used for session management of the control plane and the user plane, but is not limited thereto.

[0188] In some embodiments, the core network device may include a third network element, such as a user plane function (UPF).

[0189] In some embodiments, the third network element is used for data forwarding, traffic statistics, quality of service (QoS) management, etc. on the user plane, but is not limited thereto.

[0190] In some embodiments, the core network device may include a fourth network element, which is, for example, a policy control function (PCF).

[0191] In some embodiments, the fourth network element is used to implement user control policy management, including but not limited to QoS control, service access control, etc.

[0192] In some embodiments, the core network device may include a fifth network element, where the fifth network element is, for example, a unified data management function (UDM).

[0193] In some embodiments, the fifth network element is used to implement user subscription data management, roaming control, etc., but is not limited thereto.

[0194] In some embodiments, the core network device may include a sixth network element, which is, for example, an authentication service function (AUSF).

[0195] In some embodiments, the sixth network element is used to implement user identity authentication, but is not limited thereto.

[0196] In some embodiments, each of the above network elements may be independent of the core network device.

[0197] In some embodiments, each of the above network elements may be part of a core network device.

[0198] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0199] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0200] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0201] In the related art, in order to ensure that a terminal supporting SBFD technology (i.e., an SBFD-aware UE) can send a physical random access channel (PRACH) in the UL subband on the SBFD symbol, it is necessary to clarify the RACH configuration of the terminal. Moreover, due to the different interference conditions on the SBFD symbol and the non-SBFD symbol (i.e., non-SBFD symbol), different RACH parameters may need to be configured for them.

[0202] In some embodiments, an SBFD-aware UE can identify valid random access occasions (ROs) located on SBFD symbols, and can also identify valid ROs located on non-SBFD symbols.

[0203] In some embodiments, a terminal that does not support the SBFD technology (ie, a non-SBFD-aware UE) can only identify valid ROs located on non-SBFD symbols, but cannot identify valid ROs located on SBFD symbols.

[0204] It should be noted that both SBFD-aware UE and non-SBFD-aware UE have the ability to determine the association between the synchronization signal block (SSB) and RO (that is, SSB-RO association), but the SSB-RO association determined by SBFD-aware UE and non-SBFD-aware UE are different.

[0205] In summary, due to the diversity of terminal capabilities, the RACH process on the SBFD symbol may have multiple different implementations, and different implementations have different requirements on the terminal capabilities.

[0206] In view of this, the embodiments of the present disclosure aim to provide a communication method, so that a terminal can report the relevant RACH configurations it supports according to its own capabilities, so as to provide sufficient information support for the network device to deploy the RACH process.

[0207] FIG2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0208] Step S2101: The terminal sends capability information to the network device.

[0209] In some embodiments, the terminal is a terminal with SBFD capability, that is, the terminal is an SBFD-aware UE.

[0210] In some embodiments, the capability information is used to indicate RACH operations supported by the terminal.

[0211] That is, the terminal may report to the network device the capabilities related to the RACH operations supported by the terminal.

[0212] In some embodiments, the name of the capability information is not limited, and may be, for example, "capability indication", "capability indication information", etc.

[0213] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "code element", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0214] In some embodiments, the capability information may specifically be used to indicate at least one of the following:

[0215] Whether the terminal supports sending PRACH on SBFD symbols;

[0216] whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration, where the first RACH configuration is an additional RACH configuration specifically used for an SBFD random access operation;

[0217] The terminal only supports determining the valid RO on the SBFD symbol based on the second RACH configuration, and the second RACH configuration is a traditional RACH configuration;

[0218] Whether the terminal supports repeated transmission of PRACH;

[0219] Whether the terminal supports different power parameter configurations.

[0220] In some embodiments, terms such as "symbol", "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0221] In some embodiments, the capability information is used to indicate whether the terminal supports sending PRACH on SBFD symbols, and may be used to indicate whether the terminal supports random access on SBFD symbols.

[0222] In some embodiments, the capability information is used to indicate whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration. The capability information may be used to indicate whether the terminal supports the first RACH configuration. The first RACH configuration may be an additional RACH configuration specifically used for SBFD random access operations. That is, the capability information may be used to indicate whether the terminal supports an additional RACH configuration specifically used for SBFD random access operations.

[0223] In some embodiments, the name of the first RACH configuration is not limited, and may be, for example, "additional RACH configuration", "dedicated RACH configuration", etc.

[0224] In some embodiments, the capability information is used to indicate that the terminal supports determining the valid RO on the SBFD symbol based on the first RACH configuration. The capability information can also be used to indicate the valid RO type supported by the terminal when sending PRACH, and / or, the capability information can also be used to indicate the valid RO type considered when the terminal determines the association relationship between SSB and RO (that is, SSB-RO association).

[0225] That is, if the terminal supports additional RACH configurations specifically for SBFD random access operations, the terminal may also report at least one of the following capabilities: valid RO types supported by the terminal when sending PRACH, and valid RO types considered by the terminal when determining SSB-RO association.

[0226] In some embodiments, terms such as "synchronization signal block (SSB)", "synchronization signal (SS)", "reference signal (RS)", "pilot", and "pilot signal" can be used interchangeably.

[0227] In some embodiments, the capability information is used to indicate the valid RO type supported by the terminal when sending PRACH. It can be the capability information used to indicate that the terminal only supports sending PRACH on the valid RO determined based on the first RACH configuration, or it can be the capability information used to indicate that the terminal supports sending PRACH on the valid RO determined based on the first RACH configuration and the valid RO determined based on the second RACH configuration.

[0228] That is, the capability of the valid RO types supported by the terminal when sending PRACH reported by the terminal may be that the terminal can only send PRACH on the valid RO determined based on the first RACH configuration, or it may be that the terminal can send PRACH on the valid RO determined based on the first RACH configuration and the valid RO determined based on the second RACH configuration. The introduction to the second RACH configuration will be described in detail below and will not be repeated here.

[0229] In some embodiments, the capability information is used to indicate that the terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration, the valid RO is located on SBFD symbols or non-SBFD symbols, or the valid RO is located only on SBFD symbols.

[0230] That is, when the terminal can only send PRACH on the valid RO determined based on the first RACH configuration, the valid RO can be located on the SBFD symbol or the non-SBFD symbol; or, the valid RO is only located on the SBFD symbol.

[0231] In some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration. For the valid RO determined based on the first RACH configuration, the valid RO is located on an SBFD symbol or a non-SBFD symbol, or the valid RO is only located on an SBFD symbol; for the valid RO determined based on the second RACH configuration, the valid RO is located on an SBFD symbol or a non-SBFD symbol, or the valid RO is only located on an SBFD symbol.

[0232] That is, when the terminal is able to send PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration, for the valid RO determined based on the first RACH configuration, it can be located only on the SBFD symbol, or it can be located on both the SBFD symbol and the non-SBFD symbol; for the valid RO determined based on the second RACH configuration, it can be located only on the SBFD symbol, or it can be located on both the SBFD symbol and the non-SBFD symbol.

[0233] In some embodiments, the capability information is used to indicate the valid RO type considered when the terminal determines the association relationship between the SSB and the RO. For the valid RO determined according to the first RACH configuration, the capability information can be used to indicate that the association relationship between the SSB and the RO is determined based on all valid ROs, or the capability information can be used to indicate that the association relationship between the SSB and the RO is determined based on the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol, respectively.

[0234] That is, in the case of determining a valid RO based on the first RACH configuration, when the terminal reports the valid RO type considered when determining the association relationship between the SSB and the RO, it can report its ability to determine the SSB-RO association based on all valid ROs, or it can report its ability to determine the SSB-RO association based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol respectively.

[0235] It should be noted that determining the SSB-RO association based on all valid ROs may mean determining a set of SSB-RO associations based on all valid ROs. Determining the SSB-RO associations based on valid ROs located on non-SBFD symbols and valid ROs located on SBFD symbols may mean determining a set of SSB-RO associations based on valid ROs located on non-SBFD symbols and valid ROs located on SBFD symbols.

[0236] In some embodiments, the capability information is used to indicate the valid RO type considered when the terminal determines the association relationship between the SSB and the RO. For the valid RO determined according to the second RACH configuration, the capability information can be used to indicate that the association relationship between the SSB and the RO is determined based on the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol, or the capability information can be used to indicate that the association relationship between the SSB and the RO is determined based on the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol, respectively.

[0237] That is, for the case of determining the valid RO based on the second RACH configuration, when the terminal reports the valid RO type considered when determining the association relationship between SSB and RO, it can report its ability to determine the SSB-RO association based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol, or it can report its ability to determine the SSB-RO association based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol respectively.

[0238] It should be noted that determining the SSB-RO association based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol may mean determining a set of SSB-RO associations based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol. Determining the SSB-RO association based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol may mean determining a set of SSB-RO associations based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol.

[0239] In some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on a SBFD symbol based on the second RACH configuration, that is, the terminal does not support the first RACH configuration.

[0240] The second RACH configuration may be a legacy RACH configuration, such as a RACH configuration commonly used in the industry, a RACH configuration standardized in a protocol, and so on.

[0241] In some embodiments, the name of the second RACH configuration is not limited, and may be, for example, "legacy RACH configuration", "universal RACH configuration", etc.

[0242] In some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration. The capability information may be used to indicate at least one of the following:

[0243] The terminal only supports sending PRACH on valid ROs located on non-SBFD symbols determined according to the second RACH configuration;

[0244] The terminal only supports sending PRACH on the valid RO located on the SBFD symbol determined according to the second RACH configuration;

[0245] The terminal supports sending the PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration.

[0246] That is, when the terminal only supports the valid RO on the SBFD symbol determined according to the second RACH configuration, the terminal can report that it only supports sending PRACH on the valid RO located on the non-SBFD symbol determined according to the second RACH configuration, or the terminal can report that it only supports sending PRACH on the valid RO located on the SBFD symbol determined according to the second RACH configuration, or the terminal can report that it supports sending PRACH on the valid RO located on the non-SBFD symbol determined according to the second RACH configuration and the valid RO located on the SBFD symbol.

[0247] In some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration. The capability information can also be used to indicate that the association relationship between SSB and RO is determined based on all valid ROs, or the capability information can also be used to indicate that the association relationship between SSB and RO is determined based on a valid RO located on a SBFD symbol and a valid RO located on a non-SBFD symbol.

[0248] That is, when the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration, the terminal may further report its ability to determine the SSB-RO association based on all valid ROs, or the terminal may further report its ability to determine the SSB-RO association based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol respectively.

[0249] In some embodiments, the capability information is used to indicate whether the terminal supports repeated transmission of PRACH (ie, PRACH repetition), and may be used to indicate whether the terminal supports repeated transmission of PRACH on valid ROs of different symbol types.

[0250] That is, when reporting whether it supports the PRACH repetition capability, the terminal may report whether it supports valid ROs of PRACH repetition across different symbol types.

[0251] In some embodiments, the capability information is used to indicate whether the terminal supports different (separate) power parameter configurations, and may be capability information used to indicate whether the terminal supports a first RACH configuration and a second RACH configuration having different power parameters, and / or, may be capability information used to indicate whether the terminal supports a PRACH corresponding to a valid RO located on different types of symbols having different power parameters.

[0252] That is, when reporting whether it supports different power parameter configurations, the terminal can report whether the terminal supports the first RACH configuration and the second RACH configuration having different power parameters, and can also report whether the terminal supports the PRACH corresponding to the valid RO located on different symbol types having different power parameters.

[0253] In some embodiments, the capability information indicates that the terminal supports different power parameters for the PRACH corresponding to the valid RO located on different types of symbols, and the power parameters of the PRACH corresponding to the valid RO located on the SBFD symbol are the same as the power parameters of the PRACH corresponding to the valid RO located on the non-SBFD symbol; or, the power parameters of the PRACH corresponding to the valid RO located on the SBFD symbol are different from the power parameters of the PRACH corresponding to the valid RO located on the non-SBFD symbol.

[0254] That is, when the terminal supports PRACHs corresponding to valid ROs of different symbol types having different power parameters, the valid RO located on the SBFD symbol may have polar code parameter set 1 (Polar Code Parameter Set 1, PC parameter set 1), and the valid RO located on the non-SBFD symbol may have PC parameter set 2, and PC parameter set 1 and PC parameter set 2 may be the same or different.

[0255] In some embodiments, the terminal capability indicated by the capability information is a mandatory terminal capability.

[0256] That is, any of the above capabilities reported by the terminal can be used as mandatory capabilities of the SBFD-aware UE, that is, all terminals supporting SBFD operations support the above capabilities without the need for additional terminal capability reporting.

[0257] In some embodiments, the network device may receive capability information sent by the terminal.

[0258] Step S2102: The network device provides RACH configuration for the terminal based on the capability information.

[0259] In some embodiments, the network device may provide the terminal with a RACH configuration that matches the capability information based on the capability information.

[0260] In some embodiments, the network device may detect and receive PRACH on the corresponding valid RO based on the RACH configuration provided to the terminal. The method for determining the valid RO for detecting and receiving PRACH can be referred to the introduction in step S2101 and will not be repeated here.

[0261] In step S2103, the network device determines the association relationship between the SSB and the RO based on the capability information.

[0262] In some embodiments, the network device may determine the association relationship between the SSB and the RO according to the SSB-RO association determination method indicated by the capability information. The association relationship determination method between the SSB and the RO may be described in step S2101 and will not be repeated here.

[0263] In some embodiments, the terminal may not report capability information to the network device. Accordingly, if the network device does not receive the capability information sent by the terminal, the network device may detect the PRACH sent by the terminal only on the valid RO located on the non-SBFD symbol determined based on the second RACH configuration; or, the network device may detect the PRACH sent by the terminal only on the valid RO located on the SBFD symbol determined based on the second RACH configuration; or, the network device may detect the PRACH sent by the terminal on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol determined based on the second RACH configuration.

[0264] That is, when the network device does not receive the capability information reported by the terminal, the network device can only detect the preamble sequence (preamble) of the receiving terminal on the valid RO located on the non-SBFD symbol determined based on the second RACH configuration; or, the network device can detect the preamble of the receiving terminal on the valid RO located on the non-SBFD symbol and the valid RO on the SBFD symbol determined based on the second RACH configuration; or, the network device can only detect the preamble of the receiving terminal on the valid RO located on the SBFD symbol determined based on the second RACH configuration.

[0265] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0266] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0267] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0268] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0269] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0270] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2103. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, steps S2101+S2102 may be implemented as an independent embodiment, steps S2101+S2103 may be implemented as an independent embodiment, and steps S2102+S2103 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0271] In some embodiments, steps S2102 and S2103 may be executed in an interchanged order or simultaneously.

[0272] In some embodiments, steps S2102 and S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0273] In some embodiments, steps S2101 and S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0274] In some embodiments, steps S2101 and S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0275] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0276] According to the solution provided by the embodiment of the present disclosure, a terminal with SBFD capability may report at least one of the following capabilities related to RACH operation to a network device (such as a base station):

[0277] Whether the terminal supports random access on the SBFD symbol;

[0278] Whether the terminal supports an additional RACH configuration specifically for SBFD random access operation (i.e., the first RACH configuration, additional RACH configuration);

[0279] The terminal only supports determining the valid RO on the SBFD symbol based on the legacy RACH configuration (that is, the second RACH configuration);

[0280] Whether the terminal supports PRACH repetition;

[0281] Whether the terminal supports separate power parameter configuration.

[0282] In some embodiments, when a terminal reports whether it supports an additional RACH configuration specifically for SBFD random access operation (i.e., an additional RACH configuration), if the terminal supports the additional RACH configuration specifically for SBFD random access operation, the terminal may report at least one of the following capabilities:

[0283] Valid RO types supported by the terminal when sending PRACH;

[0284] The valid ROs considered by the terminal when determining the SSB-RO association.

[0285] In some embodiments, when the terminal reports the valid RO types it supports when sending PRACH, it may report any of the following capabilities:

[0286] The terminal can only send PRACH on the valid RO determined by the additional RACH configuration;

[0287] The terminal can send PRACH on valid ROs determined by additional RACH configuration and valid ROs determined by legacy RACH configuration.

[0288] In some embodiments, the terminal can only send PRACH on a valid RO determined by the additional RACH configuration. The valid RO may be located in a SBFD symbol or a non-SBFD symbol; or, the valid RO may only be located in a SBFD symbol.

[0289] In some embodiments, the terminal is able to send PRACH on the valid RO determined by the additional RACH configuration and the valid RO determined by the legacy RACH configuration. For the valid RO determined by the additional RACH configuration, it is only located at the SBFD symbol, or it can be located at the SBFD symbol and the non-SBFD symbol; for the valid RO determined by the legacy RACH configuration, it is only located at the SBFD symbol, or it can be located at the SBFD symbol and the non-SBFD symbol.

[0290] In some embodiments, when reporting the valid ROs considered when determining the SSB-RO association, for the valid ROs determined by the additional RACH configuration, the terminal may report any of the following capabilities:

[0291] The terminal determines the SSB-RO association based on all valid ROs;

[0292] The terminal determines the SSB-RO association according to the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol.

[0293] In some embodiments, when reporting the valid ROs considered when determining the SSB-RO association, for the valid ROs determined by the legacy RACH configuration, the terminal may report any one of the following capabilities:

[0294] The terminal determines the SSB-RO association based on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol determined by the legacy RACH;

[0295] The terminal determines the SSB-RO association according to the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol determined by the legacy RACH.

[0296] In some embodiments, the terminal only supports determining a valid RO on an SBFD symbol according to the legacy RACH configuration. Terminals that support this capability do not support the additional RACH configuration applied to SBFD random access.

[0297] In some embodiments, the terminal only supports determining valid ROs on SBFD symbols based on legacy RACH configuration. The terminal can report any of the following capabilities:

[0298] The terminal only supports sending PRACH on valid ROs determined on non-SBFD symbols according to the legacy RACH configuration;

[0299] The terminal only supports sending PRACH on the valid RO determined on the SBFD symbol according to the legacy RACH configuration;

[0300] The terminal supports sending PRACH on the valid RO determined on the SBFD symbol according to the legacy RACH configuration and the valid RO determined on the non-SBFD symbol according to the legacy RACH configuration.

[0301] In some embodiments, the terminal supports sending PRACH on valid ROs determined on SBFD symbols according to the legacy RACH configuration and valid ROs determined on non-SBFD symbols according to the legacy RACH configuration. Based on this capability, the terminal may further report any of the following capabilities:

[0302] The terminal determines the SSB-RO association based on all valid ROs;

[0303] The terminal determines the SSB-RO association according to the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol.

[0304] In some embodiments, the terminal reports whether it supports the capability of PRACH repetition, which may be when the terminal reports whether it supports valid ROs of PRACH repetition across different symbol types.

[0305] In some embodiments, the terminal reports whether it supports separate power parameter configuration capabilities, which may be any of the following capabilities:

[0306] Whether the terminal supports legacy RACH configuration and additional RACH configuration with different power parameters;

[0307] Whether the terminal supports that the PRACH corresponding to the valid RO located on different symbol types has different power parameters.

[0308] In some embodiments, when the terminal supports PRACHs corresponding to valid ROs located on different symbol types with different power parameters, the valid RO located on the SBFD symbol has PC parameter set1, and the valid RO located on the SBFD symbol has PC parameter set2. PC parameter set1 and PC parameter set2 can be the same or different.

[0309] In some embodiments, any of the above terminal capabilities may be used as mandatory capabilities of the SBFD UE, that is, all terminals supporting SBFD operations support the mandatory capabilities, without the need for additional terminal capability reporting.

[0310] In some embodiments, a base station supporting SBFD technology receives RACH operation-related capabilities reported by an SBFD-aware UE, configures RACH-related information for the terminal based on the terminal's related capabilities, and determines an SSB-RO association relationship. The capabilities reported by the terminal received by the base station can be found in the above embodiments and are not further described here.

[0311] In some embodiments, when the base station does not receive the terminal capabilities reported by the terminal, the base station may make any of the following assumptions, which are not limited in this patent:

[0312] The base station detects the receiving terminal's preamble only on the valid RO located on the non-SBFD symbol determined by the legacy RACH configuration; or,

[0313] The base station detects the receiving terminal's preamble only on the valid RO located on the SBFD symbol determined by the legacy RACH configuration; or,

[0314] The base station detects the preamble of the receiving terminal on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined by the legacy RACH configuration.

[0315] In some embodiments, when the base station detects the preamble of the receiving terminal on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined by the legacy RACH configuration, the SSB-RO association is determined according to any of the following methods:

[0316] The terminal determines the SSB-RO association relationship based on all valid ROs;

[0317] The terminal determines the SSB-RO association according to the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol.

[0318] FIG3A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a communication method, which includes:

[0319] Step S3101: Send capability information.

[0320] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0321] In some embodiments, the terminal sends capability information to the network device, but is not limited thereto and may also send capability information to other entities.

[0322] In some embodiments, the capability information is used to indicate RACH operations supported by the terminal.

[0323] In some embodiments, the capability information is used to indicate at least one of the following:

[0324] Whether the terminal supports sending PRACH on SBFD symbols;

[0325] whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration, where the first RACH configuration is an additional RACH configuration specifically used for an SBFD random access operation;

[0326] The terminal only supports determining the valid RO on the SBFD symbol based on the second RACH configuration, and the second RACH configuration is a traditional RACH configuration;

[0327] Whether the terminal supports repeated transmission of PRACH;

[0328] Whether the terminal supports different power parameter configurations.

[0329] In some embodiments, the capability information is used to indicate that the terminal supports determining a valid RO on an SBFD symbol based on the first RACH configuration, and the capability information is further used to indicate at least one of the following:

[0330] Valid RO types supported by the terminal when sending PRACH;

[0331] The valid RO type considered by the terminal when determining the association relationship between SSB and RO.

[0332] In some embodiments, the capability information is used to indicate a valid RO type supported by the terminal when sending a PRACH. The capability information is used to indicate any of the following:

[0333] The terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration;

[0334] The terminal supports sending the PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration.

[0335] In some embodiments, the capability information is used to indicate that the terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration, the valid RO is located on SBFD symbols or non-SBFD symbols, or the valid RO is located only on SBFD symbols.

[0336] In some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration, the valid RO determined based on the first RACH configuration is located on an SBFD symbol or a non-SBFD symbol, or the valid RO determined based on the first RACH configuration is located only on an SBFD symbol;

[0337] The valid RO determined based on the second RACH configuration is located on the SBFD symbol or the non-SBFD symbol, or the valid RO determined based on the second RACH configuration is located only on the SBFD symbol.

[0338] In some embodiments, the capability information is used to indicate the valid RO type considered when the terminal determines the association relationship between the SSB and the RO. For the valid RO determined according to the first RACH configuration, the capability information is used to indicate any one of the following:

[0339] Determine the association between SSB and RO based on all valid ROs;

[0340] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0341] In some embodiments, the capability information is used to indicate a valid RO type considered when the terminal determines the association relationship between the SSB and the RO. For a valid RO determined according to the second RACH configuration, the capability information is used to indicate any one of the following:

[0342] Determine the association relationship between SSB and RO according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol;

[0343] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0344] In some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on a SBFD symbol based on the second RACH configuration, and the terminal does not support the first RACH configuration.

[0345] In some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the capability information is used to indicate at least one of the following:

[0346] The terminal only supports sending PRACH on valid ROs located on non-SBFD symbols determined according to the second RACH configuration;

[0347] The terminal only supports sending PRACH on the valid RO located on the SBFD symbol determined according to the second RACH configuration;

[0348] The terminal supports sending the PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration.

[0349] In some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration, and the capability information is further used to indicate any one of the following:

[0350] Determine the association between SSB and RO based on all valid ROs;

[0351] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0352] In some embodiments, the capability information is used to indicate whether the terminal supports repeated transmission of PRACH, including: the capability information is used to indicate whether the terminal supports repeated transmission of PRACH on valid ROs of different symbol types.

[0353] In some embodiments, the capability information is used to indicate whether the terminal supports different power parameter configurations, and the capability information is used to indicate at least one of the following:

[0354] whether the terminal supports the first RACH configuration and the second RACH configuration having different power parameters;

[0355] Whether the terminal supports valid ROs located on different types of symbols corresponds to different PRACH power parameters.

[0356] In some embodiments, the capability information indicates that the terminal supports different power parameters for the PRACH corresponding to the valid RO located on different types of symbols, and the power parameters of the PRACH corresponding to the valid RO located on the SBFD symbol are the same as the power parameters of the PRACH corresponding to the valid RO located on the non-SBFD symbol; or, the power parameters of the PRACH corresponding to the valid RO located on the SBFD symbol are different from the power parameters of the PRACH corresponding to the valid RO located on the non-SBFD symbol.

[0357] In some embodiments, the terminal capabilities indicated by the capability information are mandatory terminal capabilities.

[0358] The communication method involved in the embodiment of the present disclosure may include at least step S3101, and step S3101 may be implemented as an independent embodiment, but is not limited thereto.

[0359] FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a communication method, which includes:

[0360] Step S3201, obtaining capability information.

[0361] Optional implementations of step S3201 can be found in step S2101 of FIG. 2 , optional implementations of step S3101 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0362] In some embodiments, the network device receives capability information sent by the terminal, but is not limited thereto and may also receive capability information sent by other entities.

[0363] In some embodiments, the network device obtains capability information specified by the protocol.

[0364] In some embodiments, the network device obtains capability information from upper layer(s).

[0365] In some embodiments, the network device performs processing to obtain the capability information.

[0366] In some embodiments, step S3101 is omitted, and the network device autonomously implements the function indicated by the capability information, or the above function is default or acquiescent.

[0367] In some embodiments, the capability information is used to indicate RACH operations supported by the terminal.

[0368] In some embodiments, the capability information is used to indicate at least one of the following:

[0369] Whether the terminal supports sending PRACH on SBFD symbols;

[0370] whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration, where the first RACH configuration is an additional RACH configuration specifically used for an SBFD random access operation;

[0371] The terminal only supports determining the valid RO on the SBFD symbol based on the second RACH configuration, and the second RACH configuration is a traditional RACH configuration;

[0372] Whether the terminal supports repeated transmission of PRACH;

[0373] Whether the terminal supports different power parameter configurations.

[0374] In some embodiments, the capability information is used to indicate that the terminal supports determining a valid RO on an SBFD symbol based on the first RACH configuration, and the capability information is further used to indicate at least one of the following:

[0375] Valid RO types supported by the terminal when sending PRACH;

[0376] The valid RO type considered by the terminal when determining the association relationship between SSB and RO.

[0377] In some embodiments, the capability information is used to indicate a valid RO type supported by the terminal when sending a PRACH. The capability information is used to indicate any of the following:

[0378] The terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration;

[0379] The terminal supports sending the PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration.

[0380] In some embodiments, the capability information is used to indicate that the terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration, the valid RO is located on SBFD symbols or non-SBFD symbols, or the valid RO is located only on SBFD symbols.

[0381] In some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration, the valid RO determined based on the first RACH configuration is located on an SBFD symbol or a non-SBFD symbol, or the valid RO determined based on the first RACH configuration is located only on an SBFD symbol;

[0382] The valid RO determined based on the second RACH configuration is located on the SBFD symbol or the non-SBFD symbol, or the valid RO determined based on the second RACH configuration is located only on the SBFD symbol.

[0383] In some embodiments, the capability information is used to indicate the valid RO type considered when the terminal determines the association relationship between the SSB and the RO. For the valid RO determined according to the first RACH configuration, the capability information is used to indicate any one of the following:

[0384] Determine the association between SSB and RO based on all valid ROs;

[0385] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0386] In some embodiments, the capability information is used to indicate a valid RO type considered when the terminal determines the association relationship between the SSB and the RO. For a valid RO determined according to the second RACH configuration, the capability information is used to indicate any one of the following:

[0387] Determine the association relationship between SSB and RO according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol;

[0388] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0389] In some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on a SBFD symbol based on the second RACH configuration, and the terminal does not support the first RACH configuration.

[0390] In some embodiments, the capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the capability information is used to indicate at least one of the following:

[0391] The terminal only supports sending PRACH on valid ROs located on non-SBFD symbols determined according to the second RACH configuration;

[0392] The terminal only supports sending PRACH on the valid RO located on the SBFD symbol determined according to the second RACH configuration;

[0393] The terminal supports sending the PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration.

[0394] In some embodiments, the capability information is used to indicate that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration, and the capability information is further used to indicate any one of the following:

[0395] Determine the association between SSB and RO based on all valid ROs;

[0396] The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

[0397] In some embodiments, the capability information is used to indicate whether the terminal supports repeated transmission of PRACH, including: the capability information is used to indicate whether the terminal supports repeated transmission of PRACH on valid ROs of different symbol types.

[0398] In some embodiments, the capability information is used to indicate whether the terminal supports different power parameter configurations, and the capability information is used to indicate at least one of the following:

[0399] whether the terminal supports the first RACH configuration and the second RACH configuration having different power parameters;

[0400] Whether the terminal supports valid ROs located on different types of symbols corresponds to different PRACH power parameters.

[0401] In some embodiments, the capability information indicates that the terminal supports different power parameters for the PRACH corresponding to the valid RO located on different types of symbols, and the power parameters of the PRACH corresponding to the valid RO located on the SBFD symbol are the same as the power parameters of the PRACH corresponding to the valid RO located on the non-SBFD symbol; or, the power parameters of the PRACH corresponding to the valid RO located on the SBFD symbol are different from the power parameters of the PRACH corresponding to the valid RO located on the non-SBFD symbol.

[0402] Step S3202: Provide RACH configuration for the terminal based on the capability information.

[0403] The optional implementation of step S3202 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0404] Step S3203: Determine the association relationship between the SSB and the RO based on the capability information.

[0405] The optional implementation of step S3203 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0406] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step S3201 can be implemented as an independent embodiment, step S3202 can be implemented as an independent embodiment, step S3203 can be implemented as an independent embodiment, steps S3201+S3202 can be implemented as an independent embodiment, steps S3201+S3203 can be implemented as an independent embodiment, and steps S3202+S3203 can be implemented as an independent embodiment, but are not limited thereto.

[0407] In some embodiments, steps S3202 and S3203 may be executed in an interchanged order or simultaneously.

[0408] In some embodiments, steps S3202 and S3203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0409] In some embodiments, steps S3201 and S3203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0410] In some embodiments, steps S3201 and S3202 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0411] In an embodiment of the present disclosure, step S3201 may be combined with step S3101 of FIG. 3A .

[0412] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0413] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0414] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0415] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0416] Figure 4A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 4A, terminal 4100 may include at least: a transceiver module 4101. In some embodiments, the transceiver module 4101 is configured to send capability information to a network device, where the capability information indicates the random access channel (RACH) operations supported by the terminal. Optionally, the transceiver module 4101 is configured to perform at least one of the communication steps (such as sending and / or receiving) performed by the terminal in any of the above methods (e.g., step S2101, but not limited thereto), which will not be further described here.

[0417] In some embodiments, the terminal 4100 may further include a processing module. Optionally, the processing module is configured to execute at least one of the other steps executed by the terminal in any of the above methods, which will not be described in detail here.

[0418] Figure 4B is a schematic diagram of the structure of the network device proposed in an embodiment of the present disclosure. As shown in Figure 4B, the network device 4200 may include: at least one of a transceiver module 4201 and a processing module 4202. In some embodiments, the transceiver module 4201 is configured to receive capability information sent by the terminal, where the capability information is used to indicate the RACH operation supported by the terminal; the processing module 4202 is configured to provide the terminal with RACH configuration based on the capability information, and / or determine the association relationship between SSB and RO. Optionally, the transceiver module 4201 is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods (for example, step S2101, but not limited thereto), and the processing module 4202 is used to perform at least one of the other steps (for example, step S2102, step S2103, but not limited thereto) performed by the network device in any of the above methods, which will not be repeated here.

[0419] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0420] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0421] Figure 5A is a schematic diagram of the structure of a communication device 5100 proposed in an embodiment of the present disclosure. Communication device 5100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 5100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0422] As shown in Figure 5A, the communication device 5100 includes one or more processors 5101. The processor 5101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 5100 is used to perform any of the above methods.

[0423] In some embodiments, the communication device 5100 further includes one or more memories 5102 for storing instructions. Optionally, all or part of the memories 5102 may be located outside the communication device 5100.

[0424] In some embodiments, the communication device 5100 further includes one or more transceivers 5103. When the communication device 5100 includes one or more transceivers 5103, the transceiver 5103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, but not limited thereto), and the processor 5101 performs at least one of the other steps (for example, step S2102, step S2103, but not limited thereto).

[0425] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0426] In some embodiments, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102. The interface circuit 5104 may be configured to receive signals from the memory 5102 or other devices, and may be configured to send signals to the memory 5102 or other devices. For example, the interface circuit 5104 may read instructions stored in the memory 5102 and send the instructions to the processor 5101.

[0427] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in the present disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited to FIG. 5A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0428] 5B is a schematic diagram of the structure of a chip 5200 according to an embodiment of the present disclosure. If the communication device 5100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 5200 shown in FIG5B , but the present disclosure is not limited thereto.

[0429] The chip 5200 includes one or more processors 5201 , and the chip 5200 is configured to execute any of the above methods.

[0430] In some embodiments, the chip 5200 further includes one or more interface circuits 5202. Optionally, the interface circuit 5202 is connected to the memory 5203. The interface circuit 5202 can be used to receive signals from the memory 5203 or other devices, and can be used to send signals to the memory 5203 or other devices. For example, the interface circuit 5202 can read instructions stored in the memory 5203 and send the instructions to the processor 5201.

[0431] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, but not limited to this), and the processor 5201 performs at least one of the other steps (for example, step S2102, step S2103, but not limited to this).

[0432] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0433] In some embodiments, the chip 5200 further includes one or more memories 5203 for storing instructions. Alternatively, all or part of the memories 5203 may be located outside the chip 5200.

[0434] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 5100, causes the communication device 5100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0435] The present disclosure also provides a program product, which, when executed by the communication device 5100, enables the communication device 5100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0436] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0437] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0438] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A communication method, characterized in that: Applied to a terminal, the method includes: Sending capability information to a network device, where the capability information is used to indicate a random access channel (RACH) operation supported by the terminal.

2. The method according to claim 1, characterized in that The capability information is used to indicate at least one of the following: Whether the terminal supports sending a physical random access channel PRACH on SBFD symbols; whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration, where the first RACH configuration is an additional RACH configuration specifically used for an SBFD random access operation; The terminal only supports determining a valid RO on the SBFD symbol based on a second RACH configuration, where the second RACH configuration is a traditional RACH configuration; Whether the terminal supports repeated transmission of PRACH; Whether the terminal supports different power parameter configurations.

3. The method according to claim 2, characterized in that The capability information is used to indicate that the terminal supports determining a valid RO on an SBFD symbol based on the first RACH configuration, and the capability information is further used to indicate at least one of the following: The valid RO type supported by the terminal when sending PRACH; The terminal considers the valid RO type when determining the association between the synchronization signal block SSB and RO.

4. The method according to claim 3, characterized in that The capability information is used to indicate a valid RO type supported by the terminal when sending a PRACH. The capability information is used to indicate any one of the following: The terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration; The terminal supports sending a PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration.

5. The method according to claim 4, characterized in that The capability information is used to indicate that the terminal supports sending PRACH only on a valid RO determined based on the first RACH configuration, where the valid RO is located on an SBFD symbol or a non-SBFD symbol, or the valid RO is located only on an SBFD symbol.

6. The method according to claim 4, characterized in that The capability information is used to indicate that the terminal supports sending PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration, where the valid RO determined based on the first RACH configuration is located on an SBFD symbol or a non-SBFD symbol, or the valid RO determined based on the first RACH configuration is located only on an SBFD symbol; The valid RO determined based on the second RACH configuration is located on the SBFD symbol or the non-SBFD symbol, or the valid RO determined based on the second RACH configuration is located only on the SBFD symbol.

7. The method according to any one of claims 3 to 6, characterized in that The capability information is used to indicate a valid RO type considered by the terminal when determining an association relationship between a synchronization signal block (SSB) and an RO. For a valid RO determined according to the first RACH configuration, the capability information is used to indicate any one of the following: Determine the association between SSB and RO based on all valid ROs; The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

8. The method according to any one of claims 3 to 6, characterized in that The capability information is used to indicate a valid RO type considered by the terminal when determining an association relationship between a synchronization signal block (SSB) and an RO. For a valid RO determined according to the second RACH configuration, the capability information is used to indicate any one of the following: Determine the association relationship between SSB and RO according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol; The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

9. The method according to any one of claims 2 to 8, characterized in that The capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the terminal does not support the first RACH configuration.

10. The method according to claim 9, characterized in that The capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the capability information is used to indicate at least one of the following: The terminal only supports sending PRACH on a valid RO located on a non-SBFD symbol determined according to the second RACH configuration; The terminal only supports sending PRACH on a valid RO located on a SBFD symbol determined according to the second RACH configuration; The terminal supports sending a PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration.

11. The method according to claim 10, characterized in that The capability information is used to indicate that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration, and the capability information is further used to indicate any one of the following: Determine the association between SSB and RO based on all valid ROs; The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

12. The method according to any one of claims 2 to 11, characterized in that The capability information is used to indicate whether the terminal supports repeated transmission of PRACH, including: The capability information is used to indicate whether the terminal supports repeated transmission of PRACH on valid ROs of different symbol types.

13. The method according to any one of claims 2 to 12, characterized in that The capability information is used to indicate whether the terminal supports different power parameter configurations, and the capability information is used to indicate at least one of the following: whether the terminal supports the first RACH configuration and the second RACH configuration having different power parameters; Whether the terminal supports valid ROs located on different types of symbols corresponds to different PRACH power parameters.

14. The method according to claim 13, characterized in that The capability information indicates that the terminal supports that the PRACH corresponding to the valid RO located on different types of symbols has different power parameters, and the power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is the same as the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol; or The power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is different from the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol.

15. The method according to any one of claims 1 to 14, characterized in that The terminal capabilities indicated by the capability information are mandatory terminal capabilities.

16. A communication method, characterized in that: Applied to a network device, the method includes: receiving capability information sent by a terminal, where the capability information is used to indicate RACH operations supported by the terminal; Based on the capability information, RACH configuration is provided for the terminal, and / or an association relationship between SSB and RO is determined.

17. The method according to claim 16, characterized in that The capability information is used to indicate at least one of the following: Whether the terminal supports sending PRACH on SBFD symbols; whether the terminal supports determining a valid RO on an SBFD symbol based on a first RACH configuration, where the first RACH configuration is an additional RACH configuration specifically used for an SBFD random access operation; The terminal only supports determining a valid RO on the SBFD symbol based on the second RACH configuration, the second RACH configuration is the traditional RACH configuration; Whether the terminal supports repeated transmission of PRACH; Whether the terminal supports different power parameter configurations.

18. The method according to claim 17, characterized in that The capability information is used to indicate that the terminal supports determining a valid RO on an SBFD symbol based on the first RACH configuration, and the capability information is further used to indicate at least one of the following: The valid RO type supported by the terminal when sending PRACH; The valid RO type considered when the terminal determines the association relationship between the SSB and the RO.

19. The method according to claim 18, characterized in that The capability information is used to indicate a valid RO type supported by the terminal when sending a PRACH. The capability information is used to indicate any one of the following: The terminal only supports sending PRACH on a valid RO determined based on the first RACH configuration; The terminal supports sending a PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration.

20. The method according to claim 19, characterized in that The capability information is used to indicate that the terminal supports sending PRACH only on a valid RO determined based on the first RACH configuration, where the valid RO is located on an SBFD symbol or a non-SBFD symbol, or the valid RO is located only on an SBFD symbol.

21. The method according to claim 19, wherein The capability information is used to indicate that the terminal supports sending PRACH on a valid RO determined based on the first RACH configuration and a valid RO determined based on the second RACH configuration, where the valid RO determined based on the first RACH configuration is located on an SBFD symbol or a non-SBFD symbol, or the valid RO determined based on the first RACH configuration is located only on an SBFD symbol; The valid RO determined based on the second RACH configuration is located on the SBFD symbol or the non-SBFD symbol, or the valid RO determined based on the second RACH configuration is located only on the SBFD symbol.

22. The method according to any one of claims 18 to 21, characterized in that The capability information is used to indicate a valid RO type considered by the terminal when determining an association relationship between a synchronization signal block (SSB) and an RO. For a valid RO determined according to the first RACH configuration, the capability information is used to indicate any one of the following: Determine the association between SSB and RO based on all valid ROs; The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

23. The method according to any one of claims 18 to 21, characterized in that The capability information is used to indicate a valid RO type considered by the terminal when determining an association relationship between a synchronization signal block (SSB) and an RO. For a valid RO determined according to the second RACH configuration, the capability information is used to indicate any one of the following: Determine the association relationship between SSB and RO according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol; The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

24. The method according to any one of claims 17 to 23, characterized in that The capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the terminal does not support the first RACH configuration.

25. The method according to claim 24, characterized in that The capability information is used to indicate that the terminal only supports determining a valid RO on an SBFD symbol based on the second RACH configuration, and the capability information is used to indicate at least one of the following: The terminal only supports sending PRACH on a valid RO located on a non-SBFD symbol determined according to the second RACH configuration; The terminal only supports sending PRACH on a valid RO located on a SBFD symbol determined according to the second RACH configuration; The terminal supports sending a PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration.

26. The method according to claim 25, characterized in that The capability information is used to indicate that the terminal supports sending PRACH on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined according to the second RACH configuration, and the capability information is further used to indicate any one of the following: Determine the association between SSB and RO based on all valid ROs; The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

27. The method according to any one of claims 17 to 26, characterized in that The capability information is used to indicate whether the terminal supports repeated transmission of PRACH, including: The capability information is used to indicate whether the terminal supports repeated transmission of PRACH on valid ROs of different symbol types.

28. The method according to any one of claims 17 to 27, characterized in that The capability information is used to indicate whether the terminal supports different power parameter configurations, and the capability information is used to indicate at least one of the following: whether the terminal supports the first RACH configuration and the second RACH configuration having different power parameters; Whether the terminal supports valid ROs located on different types of symbols corresponds to different PRACH power parameters.

29. The method according to claim 28, characterized in that The capability information indicates that the terminal supports that the PRACH corresponding to the valid RO located on different types of symbols has different power parameters, and the power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is the same as the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol; or The power parameter of the PRACH corresponding to the valid RO located on the SBFD symbol is different from the power parameter of the PRACH corresponding to the valid RO located on the non-SBFD symbol.

30. The method according to any one of claims 16 to 29, characterized in that If the capability information sent by the terminal is not received, the method further includes any one of the following: detecting a PRACH sent by the terminal only on a valid RO located on a non-SBFD symbol determined based on the second RACH configuration; Detecting a PRACH sent by the terminal only on a valid RO located on an SBFD symbol determined based on the second RACH configuration; The PRACH sent by the terminal is detected on the valid RO located on the non-SBFD symbol and the valid RO located on the SBFD symbol determined based on the second RACH configuration.

31. The method according to claim 30, wherein Detecting a PRACH sent by the terminal on a valid RO located on a non-SBFD symbol and a valid RO located on a SBFD symbol determined based on the second RACH configuration, the method further comprising: Determine the association between SSB and RO based on all valid ROs; The association relationship between the SSB and the RO is determined according to the valid RO located on the SBFD symbol and the valid RO located on the non-SBFD symbol.

32. A terminal, characterized in that: include: The transceiver module is configured to send capability information to a network device, where the capability information is used to indicate a random access channel (RACH) operation supported by the terminal.

33. A network device, characterized in that: include: a transceiver module, configured to receive capability information sent by a terminal, where the capability information is used to indicate RACH operations supported by the terminal; The processing module is configured to provide RACH configuration for the terminal based on the capability information, and / or determine an association relationship between SSB and RO.

34. A terminal, characterized in that: include: one or more processors; The terminal is used to execute the communication method according to any one of claims 1 to 15.

35. A network device, characterized in that: include: one or more processors; The network device is used to execute the communication method according to any one of claims 16 to 31.

36. A communication system, characterized in that: The invention comprises a terminal and a network device, wherein the terminal is configured to implement the communication method according to any one of claims 1 to 15, and the network device is configured to implement the communication method according to any one of claims 16 to 31.

37. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1 to 15 or 16 to 31.

Images