Communication method, terminal, network device and storage medium

Abstract

Provided in the embodiments of the present disclosure are a communication method, a terminal, a network device, a communication system and a storage medium. The method comprises: on the basis of first-type random access channel (RACH) resource configuration information and / or second-type RACH resource configuration information, determining preamble information of a RACH occasion (RO) in the first-type RACH resource configuration information, wherein the first-type RACH resource configuration information comprises first RACH resource configuration information used for 4-step random access (RA) of a first-type terminal and / or second RACH resource configuration information used for 2-step RA of the first-type terminal, and the first-type terminal is a terminal capable of identifying the time-frequency configuration of subband full duplex (SBFD) time unit configurations. The technical solution provided in the embodiments of the present disclosure can accurately determine preamble information of an RO.

Description

Communication method, terminal, network device and storage medium Technical Field

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

[0002] In wireless communication technology, there are downlink (DL) symbols, uplink (UL) symbols, flexible (F) symbols, and subband full-duplex (SBFD) symbols. When a symbol contains both a DL subband and an UL subband in the frequency domain, it can be called an SBFD symbol. Similarly, when a time slot contains multiple symbols including at least one SBFD symbol, the time slot can be called an SBFD time slot. For SBFD time slots, terminals that can recognize SBFD symbol configurations are introduced, and correspondingly, different types of random access opportunities (RO) are introduced.

[0003] Summary of the Invention

[0004] After the introduction of SBFD timeslots, it is necessary to consider how to determine the preamble information of the RO.

[0005] The embodiments of the present disclosure disclose a communication method, a terminal, a network device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is provided, where the method is performed by a first type terminal, and the method includes:

[0007] Determine, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, preamble information of the random access opportunity RO in the first type of RACH configuration resource information;

[0008] The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

[0009] According to a second aspect of an embodiment of the present disclosure, a communication method is provided, the method being performed by a network device, the method comprising:

[0010] Determine, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, preamble information of the random access opportunity RO in the first type of RACH configuration resource information;

[0011] The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

[0012] According to a third aspect of an embodiment of the present disclosure, a communication method is provided, where the method is performed by a communication system, and the method includes:

[0013] The network device sends first information to the terminal;

[0014] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

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

[0016] The transceiver module is configured as follows:

[0017] receiving first information sent by a network device;

[0018] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

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

[0020] The transceiver module is configured as follows:

[0021] Sending first information to the terminal;

[0022] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

[0023] According to the sixth aspect of an embodiment of the present disclosure, a communication system is provided, which includes a terminal and a network device; the terminal is configured to implement any communication method implemented by the terminal, and the network device is configured to implement any communication method implemented by the network device.

[0024] According to a seventh aspect of an embodiment of the present disclosure, a terminal is provided, comprising:

[0025] one or more processors;

[0026] The terminal is used to execute any communication method implemented by the terminal.

[0027] According to an eighth aspect of an embodiment of the present disclosure, a network device is provided, wherein the network device includes:

[0028] one or more processors;

[0029] Wherein, the network device is used to implement any communication method implemented by the network device.

[0030] According to a ninth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the communication method provided by the first aspect or the second aspect.

[0031] The technical solution provided by the implementation of the present disclosure can accurately determine the leading code information of PO.

[0032] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0034] FIG1a is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0035] FIG1b is a schematic diagram showing a time-frequency resource according to an exemplary embodiment;

[0036] FIG1c is a schematic diagram showing a time-frequency resource according to an exemplary embodiment;

[0037] FIG1d is a schematic diagram showing a time-frequency resource according to an exemplary embodiment;

[0038] FIG1e is a schematic diagram showing a time-frequency resource according to an exemplary embodiment;

[0039] FIG1f is a schematic diagram showing a time-frequency resource according to an exemplary embodiment;

[0040] FIG2a is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0041] FIG3a is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0042] FIG3 b is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0043] FIG4a is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0044] FIG4b is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0045] FIG5a is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0046] FIG6a is a schematic diagram showing a time-frequency resource according to an exemplary embodiment;

[0047] FIG6b is a schematic diagram showing a time-frequency resource according to an exemplary embodiment;

[0048] FIG6c is a schematic flow chart showing a communication method according to an exemplary embodiment;

[0049] FIG7a is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0050] FIG7b is a schematic structural diagram of a network device according to an exemplary embodiment;

[0051] FIG8a is a schematic structural diagram of a UE according to an exemplary embodiment;

[0052] Fig. 8b is a schematic structural diagram of a communication device according to an exemplary embodiment. DETAILED DESCRIPTION

[0053] Embodiments of the present disclosure provide a communication method, a terminal, a network device, and a storage medium.

[0054] In a first aspect, an embodiment of the present disclosure provides a communication method, which is performed by a first type terminal, and includes:

[0055] Determine, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, preamble information of the random access opportunity RO in the first type of RACH configuration resource information;

[0056] The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

[0057] In the above embodiment, the preamble information of the random access opportunity RO in the first type RACH configuration resource information can be determined based on at least one of the first type RACH resource configuration information and the second type RACH resource configuration information. In this way, the method of determining the preamble information is more flexible.

[0058] In combination with the embodiment of the first aspect, in some embodiments, determining the preamble information of the random access opportunity RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0059] Determine, based on a first configuration parameter included in the first type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information;

[0060] Based on the first configuration parameter included in the first type of RACH resource configuration information and the second type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information is determined.

[0061] In the above embodiment, the Preamble information of the RO in the first type of RACH resource configuration information may be determined based on the first configuration parameter included in the first type of RACH resource configuration information and at least one of the second type of RACH resource configuration information. In this way, the method of determining the Preamble information is more flexible.

[0062] In combination with the embodiments of the first aspect, in some embodiments, the second type of RACH resource configuration information includes third RACH resource configuration information for 4-step RA for second type terminals and / or fourth RACH resource configuration information for 2-step RA for second type terminals, and the second type terminals are terminals that cannot recognize SBFD time-frequency configuration.

[0063] In the above embodiment, the second type of RACH resource configuration information may include at least one of the third RACH resource configuration information and the fourth RACH resource configuration information.

[0064] In conjunction with the embodiments of the first aspect, in some embodiments, the Preamble information includes at least one of the following:

[0065] A first starting preamble index, where the first starting preamble index is a starting preamble index of a first type of shared RO in the first type of RACH configuration resource information, where the first type of shared RO is a shared RO including a first type of SBFD time unit;

[0066] The first number of preambles is the number of preambles contained in the first type of shared RO associated with a synchronization signal block SSB;

[0067] A second starting Preamble index, where the second starting Preamble index is a starting Preamble index of a second type of shared RO in the first type of RACH configuration resource information, where the second type of shared RO is a shared RO that does not include a first type of SBFD time unit;

[0068] The second number of preambles is the number of preambles contained in the second type of shared RO associated with an SSB.

[0069] In the above embodiment, the preamble information may include at least one of a first starting preamble index, a first preamble quantity, a second starting preamble index, and a second preamble quantity.

[0070] In combination with the embodiment of the first aspect, in some embodiments, determining the Preamble information of the random access opportunity RO in the first type of RACH configuration resource information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0071] Based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH configuration resource information is determined.

[0072] In the above embodiment, the Preamble information of at least one of the first type shared RO and the second type shared RO may be determined based on the first type random access channel RACH resource configuration information and / or the second type RACH resource configuration information.

[0073] In combination with the embodiment of the first aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information includes:

[0074] Determining the second starting preamble index and / or the second preamble quantity based on the first configuration parameter included in the first type of RACH resource configuration information;

[0075] The first configuration parameter is used to indicate the second starting preamble index and / or the second preamble quantity.

[0076] In the above embodiment, the second starting preamble index and / or the second preamble quantity may be directly indicated by the first configuration parameter, so that the second starting preamble index and / or the second preamble quantity may be directly determined based on the first configuration parameter.

[0077] In combination with the embodiment of the first aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0078] Determine the second starting preamble index and the second preamble quantity based on the first type RACH resource configuration information and / or the second type RACH resource configuration information;

[0079] The second starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the second preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0080] In the above embodiment, the second starting preamble index and the second preamble quantity may be determined based on different methods, and the determination method is more flexible.

[0081] In combination with the embodiment of the first aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0082] Determine the Preamble information of the second type of shared RO in the first type of RACH resource configuration information based on the first condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0083] The first condition includes:

[0084] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0085] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0086] There is an intersection between the second type ROs actually used by the two RACH resources.

[0087] In the above embodiment, the Preamble information of the second type shared RO in the first type RACH resource configuration information may be determined based on whether the first condition is met and based on the first type random access channel RACH resource configuration information and / or the second type RACH resource configuration information.

[0088] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes at least one of the following:

[0089] Determine the first starting preamble index as the second starting preamble index;

[0090] Determine the first preamble quantity as the second preamble quantity.

[0091] In the above embodiment, the first starting preamble index may be the same as the second starting preamble index, and the first preamble quantity may be the same as the second preamble quantity.

[0092] In combination with the embodiment of the first aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information includes:

[0093] Determine the first starting preamble index and / or the first preamble quantity based on a first configuration parameter included in the first type RACH resource configuration information;

[0094] The first configuration parameter is used to indicate the first starting preamble index and / or the first preamble quantity.

[0095] In the above embodiment, the first starting preamble index and / or the first preamble quantity may be directly determined based on the first starting preamble index and / or the first preamble quantity indicated by the first configuration parameter included in the first type RACH resource configuration information.

[0096] In combination with the embodiment of the first aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0097] Determine the first starting preamble index and the first preamble quantity based on the first type of RACH resource configuration information and / or the second type of RACH resource configuration information;

[0098] The first starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the first preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0099] In the above embodiment, the first starting preamble index and the first preamble quantity may be determined based on different methods, and the determination method is more flexible.

[0100] In combination with the embodiment of the first aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0101] Determine the Preamble information of the first type of shared RO in the first type of RACH resource configuration information based on the second condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0102] The second condition includes:

[0103] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0104] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0105] There is an intersection between the first type ROs actually used by the two RACH resources.

[0106] In the above embodiment, the Preamble information of the first type of shared RO in the first type of RACH resource configuration information may be determined based on whether the second condition is met and based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information.

[0107] In combination with the embodiment of the first aspect, in some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0108] Determine, based on the type of the shared RO, the first condition, the second condition, the first type of random access channel RACH resource configuration information, and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information;

[0109] The first condition includes:

[0110] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0111] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0112] There is an intersection between the second type ROs actually used by the two RACH resources;

[0113] The second condition includes:

[0114] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0115] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0116] There is an intersection between the first type ROs actually used by the two RACH resources.

[0117] In the above embodiment, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information can be determined based on the shared RO type, the first condition and / or the second condition, and based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information.

[0118] In combination with the embodiments of the first aspect, in some embodiments, the first-type RACH resource configuration information is transmitted after the second-type RACH resource configuration information.

[0119] In the above embodiment, the second type of RACH resource configuration information may be identified first.

[0120] In combination with the embodiments of the first aspect, in some embodiments, the first type of RACH resource configuration information is cell-specific configuration information or terminal-specific configuration information.

[0121] In combination with the embodiments of the first aspect, in some embodiments, the first-type RACH resource configuration information is configured with ROs actually used in the first-type shared ROs and / or the second-type shared ROs.

[0122] In combination with the embodiments of the first aspect, in some embodiments, the number of Preambles contained in an SSB-associated RO in the first type of shared RO and the second type of shared RO configured with the first type of RACH resource configuration information is the same or different.

[0123] With reference to the embodiments of the first aspect, in some embodiments, the RA is contention-based random access (CBRA).

[0124] In combination with the embodiments of the first aspect, in some embodiments, the Preambles corresponding to the number of Preambles included in the RO associated with an SSB are contention-based Preambles.

[0125] In conjunction with the embodiments of the first aspect, in some embodiments, the first-type SBFD time unit is one of the following:

[0126] The time unit is configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration (TDD-UL-DL-ConfigCommon) and is also configured as a SBFD time unit.

[0127] The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit and is configured as a SBFD time unit.

[0128] In combination with the embodiments of the first aspect, in some embodiments, the second-type RACH resource configuration information is not configured in the additional RACH configuration AdditionalRACH-Config; the first-type RACH resource configuration information is not configured in AdditionalRACH-Config; the first-type RACH resource configuration information is configured in AdditionalRACH-Config; the first RACH resource configuration information is configured in AdditionalRACH-Config and the second RACH resource configuration information is not configured in AdditionalRACH-Config; the first RACH resource configuration information is not configured in AdditionalRACH-Config and the second RACH resource configuration information is configured in AdditionalRACH-Config.

[0129] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0130] receiving first information sent by a network device;

[0131] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information.

[0132] In the above embodiment, the first type of RACH resources and the second type of RACH resources may be configured through the first information.

[0133] In a second aspect, an embodiment of the present disclosure provides a communication method, which is performed by a network device and includes:

[0134] Determine, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, preamble information of the random access opportunity RO in the first type of RACH configuration resource information;

[0135] The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

[0136] In conjunction with the embodiment of the second aspect, in some embodiments, determining the preamble information of the random access opportunity RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0137] Determine, based on a first configuration parameter included in the first type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information;

[0138] Based on the first configuration parameter included in the first type of RACH resource configuration information and the second type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information is determined.

[0139] In combination with the embodiments of the second aspect, in some embodiments, the second type of RACH resource configuration information includes third RACH resource configuration information for 4-step RA for second type terminals and / or fourth RACH resource configuration information for 2-step RA for second type terminals, and the second type terminals are terminals that cannot recognize SBFD time-frequency configuration.

[0140] In conjunction with the embodiments of the second aspect, in some embodiments, the Preamble information includes at least one of the following:

[0141] A first starting preamble index, where the first starting preamble index is a starting preamble index of a first type of shared RO in the first type of RACH configuration resource information, where the first type of shared RO is a shared RO including a first type of SBFD time unit;

[0142] The first number of preambles is the number of preambles contained in the first type of shared RO associated with a synchronization signal block SSB;

[0143] A second starting Preamble index, where the second starting Preamble index is a starting Preamble index of a second type of shared RO in the first type of RACH configuration resource information, where the second type of shared RO is a shared RO that does not include a first type of SBFD time unit;

[0144] The second number of preambles is the number of preambles contained in the second type of shared RO associated with an SSB.

[0145] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the random access opportunity RO in the first type of RACH configuration resource information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0146] Based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH configuration resource information is determined.

[0147] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information includes:

[0148] Determine the second starting preamble index and / or the number of second preambles based on the first configuration parameter included in the first type of RACH resource configuration information;

[0149] The first configuration parameter is used to indicate the second starting preamble index and / or the second preamble quantity.

[0150] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0151] Determine the second starting preamble index and the second preamble quantity based on the first type RACH resource configuration information and / or the second type RACH resource configuration information;

[0152] The second starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the second preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0153] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0154] Determine the Preamble information of the second type of shared RO in the first type of RACH resource configuration information based on the type of shared RO, the first condition, and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0155] The first condition includes:

[0156] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0157] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0158] There is an intersection between the second type ROs actually used by the two RACH resources.

[0159] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes at least one of the following:

[0160] Determine the first starting preamble index as the second starting preamble index;

[0161] Determine the first preamble quantity as the second preamble quantity.

[0162] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information includes:

[0163] Determine the first starting preamble index and / or the first preamble quantity based on a first configuration parameter included in the first type RACH resource configuration information;

[0164] The first configuration parameter is used to indicate the first starting preamble index and / or the first preamble quantity.

[0165] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0166] Determine the first starting preamble index and the first preamble quantity based on the first type of RACH resource configuration information and / or the second type of RACH resource configuration information;

[0167] The first starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the first preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0168] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0169] Determine the Preamble information of the first type of shared RO in the first type of RACH resource configuration information based on the second condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0170] The second condition includes:

[0171] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0172] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0173] There is an intersection between the first type ROs actually used by the two RACH resources.

[0174] In combination with the embodiment of the second aspect, in some embodiments, determining the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0175] Determine, based on the first condition, the second condition, the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information;

[0176] The first condition includes:

[0177] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0178] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0179] There is an intersection between the second type ROs actually used by the two RACH resources;

[0180] The second condition includes:

[0181] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0182] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0183] There is an intersection between the first type ROs actually used by the two RACH resources.

[0184] In combination with the embodiments of the second aspect, in some embodiments, the first-type RACH resource configuration information is transmitted after the second-type RACH resource configuration information.

[0185] In combination with the embodiments of the second aspect, in some embodiments, the first type of RACH resource configuration information is cell-specific configuration information or terminal-specific configuration information.

[0186] In combination with the embodiments of the second aspect, in some embodiments, the first-type RACH resource configuration information is configured with ROs actually used in the first-type shared ROs and / or the second-type shared ROs.

[0187] In combination with the embodiments of the second aspect, in some embodiments, the number of Preambles contained in an SSB-associated RO in the first type of shared RO and the second type of shared RO configured with the first type of RACH resource configuration information is the same or different.

[0188] In combination with the embodiments of the second aspect, in some embodiments, the RA is contention-based random access (CBRA).

[0189] In conjunction with the embodiments of the second aspect, in some embodiments, the Preambles corresponding to the number of Preambles included in the RO associated with an SSB are contention-based Preambles.

[0190] In conjunction with the embodiments of the second aspect, in some embodiments, the first-type SBFD time unit is one of the following:

[0191] The time unit is configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration (TDD-UL-DL-ConfigCommon) and is also configured as a SBFD time unit.

[0192] The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit and is configured as a SBFD time unit.

[0193] In combination with the embodiments of the second aspect, in some embodiments, the second type of RACH resource configuration information is not configured in the additional RACH configuration AdditionalRACH-Config; the first type of RACH resource configuration information is not configured in AdditionalRACH-Config; the first type of RACH resource configuration information is configured in AdditionalRACH-Config; the first RACH resource configuration information is configured in AdditionalRACH-Config and the second RACH resource configuration information is not configured in AdditionalRACH-Config; the first RACH resource configuration information is not configured in AdditionalRACH-Config and the second RACH resource configuration information is configured in AdditionalRACH-Config.

[0194] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0195] Sending first information to the terminal;

[0196] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information.

[0197] In a third aspect, an embodiment of the present disclosure provides a communication method, which is performed by a communication system and includes:

[0198] The network device sends first information to the terminal;

[0199] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

[0200] In a fourth aspect, an embodiment of the present disclosure provides a terminal, comprising:

[0201] The transceiver module is configured as follows:

[0202] receiving first information sent by a network device;

[0203] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

[0204] In a fifth aspect, an embodiment of the present disclosure provides a network device, the network device comprising:

[0205] The transceiver module is configured as follows:

[0206] Sending first information to the terminal;

[0207] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

[0208] In the seventh aspect, an embodiment of the present disclosure provides a communication system, wherein the communication system includes a terminal and a network device, the terminal is configured to implement the communication method described in the optional implementation manner of the first aspect, and the network device is configured to implement the communication method described in the optional implementation manner of the second aspect.

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

[0210] one or more processors;

[0211] The terminal is used to execute the communication method provided by the first aspect.

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

[0213] one or more processors;

[0214] The network device is used to execute the communication method provided in the second aspect.

[0215] In a tenth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the communication method described in the optional implementation of the first and second aspects.

[0216] In an eleventh 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 method described in the optional implementation of the first and second aspects.

[0217] In a twelfth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0218] In a thirteenth 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 method described in the optional implementation of the first and second aspects above.

[0219] It is understandable that the above-mentioned terminals, storage media, program products, computer programs, chips or chip systems are all used to execute 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.

[0220] The present disclosure provides a communication method, a terminal, a network device, and a storage medium. In some embodiments, the terms communication method, information processing method, information transmission method, etc. can be used interchangeably, and the terms communication system, information processing system, etc. can be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0241] As shown in FIG. 1 a , a communication system 100 includes a terminal 101 and a network device 102 .

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

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

[0244] In some embodiments, the access network device may be, 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.

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

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

[0247] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The 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), and a Next Generation Core (NGC).

[0248] 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 provided by 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 provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0249] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1a, or a portion thereof, but are not limited thereto. The entities shown in FIG1a are illustrative only. The communication system may include all or a portion of the entities shown in FIG1a, or may include other entities other than those shown in FIG1a. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

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

[0251] To better understand the embodiments of the present disclosure, the following examples illustrate relevant scenarios:

[0252] In order to improve uplink (UL) coverage and throughput, duplex enhancement (duplex enhancement) has been studied on subband full duplex (SBFD).

[0253] In some embodiments, a carrier component (CC) is divided into multiple subbands (SBs) in the frequency domain on a downlink (DL) symbol or a flexible (F) symbol. The multiple SBs include one UL subband and at least one (e.g., one or two) DL subbands. A base station can transmit DL signals on the DL subband and simultaneously receive UL signals on the UL subband. The DL or F symbols can be configured in at least one of the following ways:

[0254] TDD-UL-DL-ConfigCommon configuration;

[0255] TDD-UL-DL-ConfigDedicated configuration;

[0256] TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated configurations; and,

[0257] Downlink control information format 2-0 (DCI format 2-0) indication.

[0258] When a symbol includes both a DL subband and a UL subband in the frequency domain, it may be called an SBFD symbol.

[0259] In some embodiments, when a time slot includes at least one SBFD symbol, the time slot may be referred to as an SBFD time slot. For example, referring to Figure 1b , time slot 0 is a DL time slot including 14 DL symbols, time slots 1 through 3 are SBFD time slots, each including 14 SBFD symbols, and time slot 4 is a UL time slot including 14 UL symbols.

[0260] In some embodiments, a DL or F symbol can be configured as SBFD via semi-static signaling, referred to as semi-SBFD. Alternatively, a DL or F symbol can be configured as SBFD via dynamic signaling, referred to as dynamic-SBFD. Furthermore, an SBFD symbol can be modified to a DL, UL, or F symbol via dynamic signaling.

[0261] In some embodiments, a guard band (GB) may exist between the DL sub-band and the UL sub-band to reduce interference between DL signals in the DL sub-band and UL signals in the UL sub-band through frequency domain isolation.

[0262] In some embodiments, in a SBFD symbol, the frequency domain range available for UL transmission may be discontinuous.

[0263] In some embodiments, GB and DL subbands are unavailable for UL transmission, and UL subbands are available for UL transmission.

[0264] In some embodiments, the DL subband is unavailable for UL transmission, and the UL subband and GB are available for UL transmission.

[0265] In some embodiments, in an SBFD symbol, the frequency domain range that can be used for UL transmission can be referred to as the UL frequency domain range, and the frequency domain range that cannot be used for UL transmission can be referred to as outside the UL frequency domain range. Based on the above analysis, it can be seen that the UL frequency domain ranges of non-SBFD symbols and SBFD symbols are different. The UL frequency domain range is the UL frequency domain range on the CC. In an SBFD symbol, the UL frequency domain range on the UL bandwidth part (BWP) refers to the frequency domain range where the BWP overlaps with the UL frequency domain range on the CC. Unless otherwise specified, the UL frequency domain range in this disclosure refers to the UL frequency domain range on the BWP.

[0266] In some embodiments, when the terminal is in the Radio Resource Control (RRC) idle state, when initially accessing a cell, the terminal will measure information such as the received signal strength of the synchronization broadcast block (SSB) beam and select the optimal SSB beam. In the direction of the optimal SSB beam, a physical random access channel (PRACH) signal is sent at the random access channel occasion (RO) for random access. In addition, in other states, the terminal may also send a PRACH signal at the RO for random access. Random access includes contention-based random access (CBRA) and contention-free random access (CFRA). In CBRA, if multiple terminals use the same preamble, random access will fail.

[0267] In some embodiments, the SSB referred to below may be the SSB selected by the UE mentioned above.

[0268] In some embodiments, as shown in Figure 1c, a UE can transmit uplink signals in UL SB during SBFD symbols. Therefore, compared to configuring ROs only in UL or F symbols, configuring ROs in SBFD symbols increases the number of ROs. SBFD-aware UEs (UEs that can recognize SBFD symbol configurations) can perform random access using ROs configured in SBFD symbols, reducing access latency and the probability of PUSCH transmission collisions between different UEs in CBRA.

[0269] In some embodiments, for legacy UEs, RACH resource configurations of 4-step RA and 2-step RA may coexist, referred to as RACH config#1 and RACH config#2. The ROs configured by RACH config#1 and RACH config#2 have the following two relationships:

[0270] Option 1: The ROs configured in RACH config #1 and RACH config #2 are located in different time / frequency domains, which can be called non-shared ROs. For example, see Figure 1d, which shows non-shared ROs for 2-step RA and 4-step RA.

[0271] Option 2: The ROs configured in RACH config #1 and RACH config #2 have the same time-frequency location, which is called a shared RO. For example, see Figure 1e (corresponding to a scenario where one SSB is mapped to four ROs (N = 1 / 4)) and Figure 1f (corresponding to a scenario where two SSBs are mapped to one RO (N = 2)), which illustrate shared ROs for 2-step RA and 4-step RA.

[0272] In some embodiments, when a 2-step RA and a 4-step RA share an RO, the starting index of the Preamble of the RO of the 2-step RA is determined according to the configuration of the 4-step RA, and the number of Preambles of the RO of the 2-step RA is determined according to the configuration.

[0273] In some embodiments, assuming that N SSBs are mapped to one RO, the total number of Preambles is In 4-step RA, one RO contains R Preambles, and in 2-step RA, one RO contains Q Preambles:

[0274] When N is less than or equal to 1, the starting index of the RO Preamble of the 2-step RA is R, and the number is Q;

[0275] When N is greater than 1, the starting index of the nth (0≤n≤N-1) SSB Preamble of an RO associated with a 2-step RA is The number is Q.

[0276] In some embodiments, when one SSB maps multiple ROs (N<1), it is also supported to share some ROs of the 4-step RA with the 2-step RACH. Specifically, the PRACH mask configured by SIB1 indicates one of the indices in Table 1 below, indicating the index of the RO shared with the 2-step RACH.

[0277] Table 1:

[0278] In some embodiments, when SBFD aware UEs and legacy UEs coexist, the following problems arise: 1. When RACH config#3 of the 4-step RA of the SBFD aware UE is a shared RO with RACH config#1 and / or RACH config#2, how to determine the preamble starting index and number of an RO in RACH config#3; when RACH config#4 of the 2-step RA of the SBFD aware UE is a shared RO with RACH config#1, RACH config#2 and / or RACH config3, how to determine the preamble starting index and number of an RO in RACH config#4.

[0279] FIG2a is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2a, the present disclosure embodiment relates to a communication method for a communication system 100, the method comprising:

[0280] Step S2101: The network device sends first information to the terminal.

[0281] In some embodiments, the terminal receives first information sent by the network device.

[0282] In some embodiments, the network device sends the first information to the first type terminal and / or the second type terminal.

[0283] In some embodiments, the first type terminal and / or the second type terminal receives the first information sent by the network device.

[0284] In some embodiments, the first type of terminal (SBFD aware UE) is a terminal that can recognize sub-band full-duplex SBFD time-frequency configuration.

[0285] In some embodiments, the second type of terminal (legacy UE) is a terminal that cannot recognize SBFD time-frequency configuration.

[0286] In some embodiments, the first information includes the first type RACH resource configuration information and / or the second type RACH resource configuration information.

[0287] In some embodiments, the first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals.

[0288] In some embodiments, the second type of RACH resource configuration information includes third RACH resource configuration information of 4-step RA for second type terminals and / or fourth RACH resource configuration information of 2-step RA for second type terminals.

[0289] Step S2102: The first type terminal or network device determines preamble information.

[0290] In some embodiments, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the random access opportunity RO in the first type of RACH configuration resource information is determined.

[0291] In some embodiments, the Preamble information of the RO in the first type of RACH resource configuration information is determined based on the first configuration parameter included in the first type of RACH resource configuration information.

[0292] In some embodiments, the Preamble information of the RO in the first type of RACH resource configuration information is determined based on the first configuration parameter included in the first type of RACH resource configuration information and the second type of RACH resource configuration information.

[0293] In some embodiments, the Preamble information includes at least one of the following:

[0294] A first starting preamble index, where the first starting preamble index is a starting preamble index of a first type of shared RO in the first type of RACH configuration resource information, where the first type of shared RO is a shared RO including a first type of SBFD time unit;

[0295] The first number of preambles is the number of preambles contained in the first type of shared RO associated with a synchronization signal block SSB;

[0296] A second starting preamble index, where the second starting preamble index is a starting preamble index of a second type of shared RO in the first type of RACH configuration resource information, and the second type of shared RO is a shared RO that does not include the first type of SBFD time unit;

[0297] The second number of preambles is the number of preambles contained in the second type of shared RO associated with an SSB.

[0298] In some embodiments, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH configuration resource information is determined based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information.

[0299] In some embodiments, four types of RACH configuration (RACH config) information may be configured, including at least one of the following:

[0300] RACH config#1 of a 4-step random access (RA) configuration for a second type of terminal (e.g., a legacy UE);

[0301] RACH config#2 for a 2-step random access (2-step RA) configuration for a second type of terminal;

[0302] RACH config#3 of a 4-step random access configuration for a first type of terminal (e.g., SBFD aware UE);

[0303] RACH config#4 of the 2-step random access configuration for the first type of terminals.

[0304] In some embodiments, the RACH configuration configured for a first type of terminal may be referred to as first-type RACH configuration information in this disclosure; the RACH configuration configured for a second type of terminal may be referred to as second-type RACH configuration information in this disclosure. In this disclosure, RACH config #3 may be referred to as first RACH resource configuration information, RACH config #4 may be referred to as second RACH resource configuration information, RACH config #1 may be referred to as third RACH resource configuration information, and RACH config #2 may be referred to as fourth RACH resource configuration information.

[0305] In some embodiments, at least two of the above four RACH configurations are configured in the network, including at least one of RACH config #3 and RACH config #4.

[0306] In some embodiments, configuring at least two RACH resources (corresponding to two RACH configs) may satisfy the first condition, where the first condition includes: two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; the second-type ROs (legacy ROs) of the two RACH resources are located at the same time domain and frequency domain positions; and the second-type ROs actually used in the two RACH resources overlap.

[0307] In some embodiments, configuring at least two RACH resources (corresponding to two RACH configurations) may satisfy the second condition, where the second condition includes: two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; the time domain and frequency domain positions of the first-type ROs (additional ROs) of the two RACH resources are the same; and there is an intersection between the first-type ROs actually used in the two RACH resources.

[0308] In some embodiments, the starting preamble of the second type of shared legacy RO in RACH config#3 and / or RACH config#4 and the number (or quantity) of preambles included in an SSB-associated RO are determined based on other RACH resource configuration information or newly added configuration parameters.

[0309] In some embodiments, for RACH config #3, at least one of RACH config #1 and RACH config #2 may be other RACH resource configuration information; for RACH config #4, at least one of RACH config #1, RACH config #2, and RACH config #3 may be other RACH resource configuration information. The other RACH resource configuration information may be first-type RACH resource configuration information and / or second-type RACH resource configuration information.

[0310] In some embodiments, the newly added configuration parameter (corresponding to the first configuration parameter) may be a configuration parameter in RACH config#3 and / or RACH config#4.

[0311] In some embodiments, the second starting preamble index and / or the second preamble quantity is determined based on a first configuration parameter included in the first type RACH resource configuration information; wherein the first configuration parameter is used to indicate the second starting preamble index and / or the second preamble quantity.

[0312] In some embodiments, the starting preamble index of the shared legacy RO and the number of preambles included in the shared legacy RO associated with an SSB are configured in RACH config#3 and / or RACH config#4.

[0313] In some embodiments, a new configuration parameter may be configured in RACH config#3 and / or RACH config#4, where the new configuration parameter is used to indicate the starting preamble index of the configured shared legacy RO and the number of preambles included in a shared legacy RO associated with an SSB.

[0314] In some embodiments, the second starting preamble index and the second preamble quantity are determined based on the first type RACH resource configuration information and / or the second type RACH resource configuration information;

[0315] In some embodiments, the second starting preamble index is determined based on the first type RACH resource configuration information and / or the second type RACH resource configuration information, and the second preamble quantity is determined based on a first configuration parameter included in the first type RACH resource configuration information.

[0316] In some embodiments, the starting preamble of the shared legacy RO in RACH config#3 and / or RACH config#4 is determined according to other RACH resource configuration information.

[0317] In some embodiments, the number of preambles included in an SSB-associated RO in a shared legacy RO in RACH config #3 and / or RACH config #4 is determined based on other RACH resource configuration information or newly added configuration parameters.

[0318] In some embodiments, based on a first condition and first-type random access channel RACH resource configuration information and / or second-type RACH resource configuration information, the Preamble information of the second-type shared RO in the first-type RACH resource configuration information is determined; wherein the first condition includes: two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; the time domain and frequency domain positions of the second-type ROs of the two RACH resources are the same; and there is an intersection between the second-type ROs actually used by the two RACH resources.

[0319] For example, the total number of Preambles is The SSB corresponding to a valid RO in RACH config#1, RACH config#2, RACH config#3, and RACH config#4 contains R, Q, R_2, and Q_2 preambles (if configured), respectively. N SSBs are associated with one valid RO.

[0320] For example, the starting preamble index of the shared legacy RO in RACH config #3 and the number of preambles contained in the shared legacy RO associated with an SSB are:

[0321] In some embodiments, the starting preamble is:

[0322] Option 1: When N is less than 1, the starting preamble index is R_3+Q_3; when N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0323] In some embodiments, the number of preambles is:

[0324] Option 1:

[0325] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be R_2, and not more than

[0326] In some embodiments, when RACH config#1 and RACH config#3 meet the first condition, R_3 takes the value of R, otherwise R_3 takes the value of 0.

[0327] In some embodiments, when RACH config#2 and RACH config#3 meet the first condition, Q_3 takes the value of Q, otherwise Q_3 takes the value of 0.

[0328] For example, the starting preamble index of the shared legacy RO in RACH config #4 and the number of preambles contained in the shared legacy RO associated with an SSB are:

[0329] In some embodiments, the starting preamble is:

[0330] Option 1: When N is less than 1, the starting preamble index is R_3+Q_3+R_4; when N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0331] In some embodiments, the number of preambles contained in an RO associated with an SSB is:

[0332] Option 1:

[0333] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be Q_2, and not more than

[0334] In some embodiments, when RACH config#1 and RACH config#4 meet the first condition, R_3 takes the value of R, otherwise R_3 takes the value of 0.

[0335] In some embodiments, when RACH config#2 and RACH config#4 meet the first condition, Q_3 takes the value of Q, otherwise Q_3 takes the value of 0.

[0336] In some embodiments, when RACH config#3 and RACH config#4 meet the first condition, R_4 takes the value of R_2; otherwise, R_4 takes the value of 0.

[0337] In some embodiments, the starting preamble of the first type of shared additional RO in RACH config#3 and / or RACH config#4 and the number of preambles included in an SSB-associated RO are determined according to other RACH resource configuration information or newly added configuration parameters.

[0338] In some embodiments, the first starting preamble index is determined to be the second starting preamble index.

[0339] In some embodiments, the first preamble number is determined to be the second preamble number.

[0340] In some embodiments, the starting Preamble of the shared additional RO is the same as the starting Preamble of the legacy shared RO, and the number of Preambles included in an SSB-associated RO is the same as the number of Preambles in the legacy shared RO.

[0341] In some embodiments, the first starting preamble index and / or the first preamble quantity are determined based on a first configuration parameter included in the first type RACH resource configuration information; wherein the first configuration parameter is used to indicate the first starting preamble index and / or the first preamble quantity.

[0342] In some embodiments, the starting preamble index of the shared additional RO and the number of preambles included in the shared additional RO associated with an SSB are configured in RACH config#3 and / or RACH config#4.

[0343] In some embodiments, the first starting preamble index and the first preamble quantity are determined based on the first type of RACH resource configuration information and / or the second type of RACH resource configuration information.

[0344] In some embodiments, the first starting preamble index is determined based on the first type RACH resource configuration information and / or the second type RACH resource configuration information, and the first preamble quantity is determined based on a first configuration parameter included in the first type RACH resource configuration information.

[0345] In some embodiments, a new configuration parameter may be configured in RACH config#3 and / or RACH config#4, where the new configuration parameter is used to indicate a starting preamble index of a configured shared additional RO and the number of preambles included in a shared additional RO associated with an SSB.

[0346] In some embodiments, according to RACH config#3, the starting preamble of the shared additional RO in RACH config#3 is determined, and the number of preambles included in an SSB-associated RO in the shared additional RO is determined.

[0347] In some embodiments, RACH config#3 includes a newly added configuration parameter, where the newly added configuration parameter is used to indicate the number of preambles included in an RO associated with an SSB in a shared additional RO.

[0348] In some embodiments, the starting preamble of the shared additional RO in RACH config#4 is determined according to other RACH resource configuration information, and the number of preambles included in an SSB-associated RO in the shared additional RO in RACH config#4 is determined according to other RACH resource configurations or newly added parameter configurations.

[0349] In some embodiments, based on the second condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO in the first type of RACH resource configuration information is determined; wherein the second condition includes: two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first type of RACH resource configuration information or a resource configured by the second type of RACH resource configuration information; the time domain and frequency domain positions of the first type ROs of the two RACH resources are the same; and there is an intersection between the first type ROs actually used by the two RACH resources.

[0350] For example, the total number of Preambles is In RACH config #3 and RACH config #4, the SSB corresponding to a valid RO contains R_2_2 and Q_2_2 preambles respectively (if configured), and N SSBs are associated with 1 valid RO.

[0351] For example, the starting preamble index of the shared additional RO in RACH config #3 and the number of preambles contained in the shared additional RO associated with one SSB are:

[0352] In some embodiments, the starting preamble is:

[0353] Option 1: When N is less than 1, the starting preamble index is 0; when N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0354] In some embodiments, the number of preambles is:

[0355] Option 1:

[0356] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be R_2_2, and not more than

[0357] For example, the starting preamble index of the shared additional RO in RACH config #4 and the number of preambles contained in the shared additional RO associated with an SSB are:

[0358] In some embodiments, the starting preamble is:

[0359] Option 1: When N is less than 1, the starting preamble index is R_4_2; when N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0360] In some embodiments, the number of preambles contained in an RO associated with an SSB is:

[0361] Option 1:

[0362] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be Q_2_2, and not more than

[0363] In some embodiments, when RACH config#3 and RACH config#4 meet the second condition, R_4_2 takes the value of R_2_2; otherwise, R_4_2 takes the value of 0.

[0364] In some embodiments, the starting preamble of the first shared RO in RACH config#3 and / or RACH config#4 is determined based on other RACH resource configuration information, and the number of preambles included in an SSB-associated RO in the first shared RO in RACH config#3 and / or RACH config#4 is determined based on other RACH resource configuration information or newly added configuration parameters.

[0365] In some embodiments, the first shared RO is a shared legacy RO and / or a shared additional RO.

[0366] In some embodiments, based on the type of shared RO, the first condition, the second condition, the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information is determined; wherein the first condition includes: two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first type of RACH resource configuration information or a resource configured by the second type of RACH resource configuration information; the second type ROs of the two RACH resources are located at the same time domain and frequency domain positions; the second type ROs actually used by the two RACH resources have an intersection; the second condition includes: two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first type of RACH resource configuration information or a resource configured by the second type of RACH resource configuration information; the first type ROs of the two RACH resources are located at the same time domain and frequency domain positions; and the first type ROs actually used by the two RACH resources have an intersection.

[0367] In some embodiments, the fifth RACH resource is one of RACH config #3 and RACH config #4.

[0368] In some embodiments, the total number of Preambles is N SSBs are associated with 1 valid RO.

[0369] In some embodiments, the first shared RO is a shared legacy RO, only one of RACH config#3 and RACH config#4 or RACH config#3 and RACH config#4 do not meet the first condition, and any RACH resource configuration in other RACH resource configuration information and the fifth RACH resource meet the first condition (corresponding to Option 1).

[0370] In some embodiments, the first shared RO is a shared additional RO, only one of RACH config#3 and RACH config#4 or RACH config#3 and RACH config#4 do not meet the second condition, and any RACH resource configuration in other RACH resource configuration information and the fifth RACH resource meet the second condition (corresponding to Option 2).

[0371] Exemplarily, for Option 1 and / or Option 2, the starting preamble index of the first shared RO in the fifth RACH resource and the number of preambles contained in the first shared RO associated with one SSB are:

[0372] In some embodiments, the starting preamble is:

[0373] Option 1: When N is less than 1, the starting preamble index is X_2; when N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0374] In some embodiments, the number of preambles is:

[0375] Option 1:

[0376] Option 2: Configure the number of preambles contained in the first shared RO of an SSB association to be P_5, and not more than

[0377] In some embodiments, X_2 refers to the sum of the number of Preambles contained in the SSBs corresponding to the valid ROs in other RACH resource configuration information.

[0378] In some embodiments, the fifth RACH resource is one of RACH config#3 and RACH config#4, the sixth RACH resource is another RACH resource in RACH config#3 and RACH config#4 except the fifth RACH resource, and the total number of preambles is N SSBs are associated with 1 valid RO.

[0379] In some embodiments, the first shared RO is a shared legacy RO, RACH config#3 and RACH config#4 meet the first condition, and any RACH resource configuration in other RACH resource configurations and RACH config#3 meet the first condition (Option 1).

[0380] In some embodiments, the first shared RO is a shared additional RO, RACH config#3 and RACH config#4 meet the second condition, and any RACH resource configuration in other RACH resource configurations and RACH config#3 meet the second condition (Option 2).

[0381] In some embodiments, in Option 1 and / or Option 2, scheme 1-1, scheme 1-2, scheme 2-1, scheme 2-2 or scheme 2-3 is used to determine the starting preamble index of the first shared RO in the fifth RACH resource and the number of preambles P_5_2 contained in the first shared RO associated with an SSB.

[0382] In some embodiments, in Option 1 and / or Option 2, the starting preamble index of the first shared RO in the sixth RACH resource and the number of preambles included in the first shared RO associated with one SSB are:

[0383] In some embodiments, the starting preamble is:

[0384] Option 1: When N is less than 1, the starting preamble index is Y_2+P_5_2; when N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0385] In some embodiments, the number of preambles is:

[0386] Option 1:

[0387] Option 2: Configure the number of preambles contained in the first shared RO of an SSB association to be P_6_2, and not more than

[0388] In some embodiments, Y_2 refers to the sum of the number of Preambles contained in the SSBs corresponding to the valid ROs in other RACH resource configuration information.

[0389] In some embodiments, the other RACH resource configurations include RACH resources configured in RACH config#1, RACH config#2 and / or AdditionalRACH-Config.

[0390] In some embodiments, RACH config#3 and / or RACH config#4 need to be configured after the existing RRC configuration to avoid affecting the interpretation of the existing RRC configuration by legacy UEs.

[0391] In some embodiments, the first type of RACH resource configuration information is transmitted after the second type of RACH resource configuration information.

[0392] In some embodiments, RACH config#3 and / or RACH config#4 may be a Cell-specific configuration or a UE-specific configuration.

[0393] In some embodiments, the first type RACH resource configuration information is configured with an RO actually used in the first type shared RO and / or the second type shared RO.

[0394] In some embodiments, in RACH config#3 and / or RACH config#4, the RO actually used in the Shared legacy RO and / or Shared additional RO is configured, such as using SharedRO-MaskIndex to configure a subset of the Shared legacy RO and / or Shared additional RO.

[0395] In some embodiments, the number of Preambles contained in an SSB-associated RO in the first type of shared RO and the second type of shared RO configured with the first type of RACH resource configuration information is the same or different.

[0396] In some embodiments, in RACH config #3 and / or RACH config #4, the number of preambles contained in an RO associated with an SSB in a Shared legacy RO and a Shared additional RO is the same or different.

[0397] In some embodiments, when the number of Preambles is different, the Preamble contained in an SSB-associated RO in the Shared additional RO is the union of set 1 and set 2; wherein, set 1 includes: the Preamble contained in an SSB-associated RO of the SBFD aware UE in the Shared legacy RO; set 2 includes: the Preamble contained in an SSB-associated RO of the legacy UE in the Shared legacy RO.

[0398] In some embodiments, the first type of SBFD time unit is one of the following:

[0399] The time unit is configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration (TDD-UL-DL-ConfigCommon) and is also configured as a SBFD time unit.

[0400] The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit and is configured as a SBFD time unit.

[0401] In some embodiments, the first type of SBFD time unit is one of the following:

[0402] A time unit configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration TDD-UL-DL-ConfigCommon and a time unit configured as an SBFD time unit by the first information;

[0403] The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit, and is configured by the first information as a SBFD time unit.

[0404] In some embodiments, the additional RO and legacy RO are used as defined below:

[0405] The additional RO refers to an RO that includes at least one first-category SBFD symbol, and the legacy RO refers to an RO that does not include the first-category SBFD symbol.

[0406] In some embodiments, the first type of SBFD symbols refers to symbols configured with TDD-UL-DL-ConfigCommon as a DL time unit and configured as SBFD.

[0407] In some embodiments, the first type of SBFD symbols refers to symbols configured as DL time units or flexible time units in TDD-UL-DL-ConfigCommon and configured as SBFD.

[0408] In some embodiments, the random access is CBRA.

[0409] In some embodiments, a Preamble in the number of Preambles included in an RO associated with an SSB is a contention based Preamble.

[0410] In some embodiments, the second-type RACH resource configuration information is not configured in the additional RACH configuration AdditionalRACH-Config; the first-type RACH resource configuration information is not configured in the AdditionalRACH-Config; the first-type RACH resource configuration information is configured in the AdditionalRACH-Config; the first RACH resource configuration information is configured in the AdditionalRACH-Config and the second RACH resource configuration information is not configured in the AdditionalRACH-Config; the first RACH resource configuration information is not configured in the AdditionalRACH-Config and the second RACH resource configuration information is configured in the AdditionalRACH-Config.

[0411] In some embodiments, RACH config#1 and RACH config#2 are not configured in AdditionalRACH-Config.

[0412] In some embodiments, RACH config #3 and RACH config #4 are not configured in AdditionalRACH-Config.

[0413] In some embodiments, RACH config #3 and RACH config #4 are configured in AdditionalRACH-Config.

[0414] In some embodiments, RACH config#3 is not configured in AdditionalRACH-Config, and RACH config#4 is configured in AdditionalRACH-Config.

[0415] In some embodiments, RACH config #3 is configured in AdditionalRACH-Config, and RACH config #4 is not configured in AdditionalRACH-Config.

[0416] In some embodiments, the term "information" can be interchangeable with terms such as "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "field", and "data".

[0417] In some embodiments, the term "send" can be interchangeable with terms such as "transmit", "report", and "transmit".

[0418] The information indication method involved in the embodiments of the present disclosure may include at least one of steps S2101 and S2102. For example, step S2101 may be implemented as an independent embodiment, and step S2102 may be implemented as an independent embodiment, but the present disclosure is not limited thereto. The different steps may be performed in a different order if they do not conflict, and this is not a limitation here.

[0419] Figure 3a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3a, the communication method according to the embodiment of the present disclosure is executed by a terminal, and the method includes:

[0420] Step S3101: The first type of terminal receives first information.

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

[0422] Step S3102: The first type terminal determines preamble information.

[0423] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0424] The information indication method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, and step S3102 may be implemented as an independent embodiment, but the present disclosure is not limited thereto. The different steps may be performed in a different order if they do not conflict, and this is not a limitation here.

[0425] Figure 3b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3b, the embodiment of the present disclosure relates to a communication method, which is executed by a terminal and includes:

[0426] Step S3201: Determine the preamble information of the random access opportunity RO in the first type of RACH configuration resource information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0427] The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

[0428] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0429] In some embodiments, determining the preamble information of the random access opportunity RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0430] Determine, based on a first configuration parameter included in the first type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information;

[0431] Based on the first configuration parameter included in the first type of RACH resource configuration information and the second type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information is determined.

[0432] In some embodiments, the second type of RACH resource configuration information includes third RACH resource configuration information of 4-step RA for second type terminals and / or fourth RACH resource configuration information of 2-step RA for second type terminals, and the second type terminals are terminals that cannot recognize SBFD time-frequency configuration.

[0433] In some embodiments, the Preamble information includes at least one of the following:

[0434] A first starting preamble index, where the first starting preamble index is a starting preamble index of a first type of shared RO in the first type of RACH configuration resource information, where the first type of shared RO is a shared RO including a first type of SBFD time unit;

[0435] The first number of preambles is the number of preambles contained in the first type of shared RO associated with a synchronization signal block SSB;

[0436] A second starting Preamble index, where the second starting Preamble index is a starting Preamble index of a second type of shared RO in the first type of RACH configuration resource information, where the second type of shared RO is a shared RO that does not include a first type of SBFD time unit;

[0437] The second number of preambles is the number of preambles contained in the second type of shared RO associated with an SSB.

[0438] In some embodiments, determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the random access opportunity RO in the first type of RACH configuration resource information includes:

[0439] Based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH configuration resource information is determined.

[0440] In some embodiments, determining, based on the first type of random access channel RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes:

[0441] Determine the second starting preamble index and / or the number of second preambles based on the first configuration parameter included in the first type of RACH resource configuration information;

[0442] The first configuration parameter is used to indicate the second starting preamble index and / or the second preamble quantity.

[0443] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0444] Determine the second starting preamble index and the second preamble quantity based on the first type RACH resource configuration information and / or the second type RACH resource configuration information;

[0445] The second starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the second preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0446] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0447] Determine the Preamble information of the second type of shared RO in the first type of RACH resource configuration information based on the first condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0448] The first condition includes: two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first type of RACH resource configuration information or a resource configured by the second type of RACH resource configuration information;

[0449] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0450] There is an intersection between the second type ROs actually used by the two RACH resources.

[0451] In some embodiments, the method further comprises at least one of the following:

[0452] Determine the first starting preamble index as the second starting preamble index;

[0453] Determine the first preamble quantity as the second preamble quantity.

[0454] In some embodiments, determining, based on the first type of random access channel RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes:

[0455] Determine the first starting preamble index and / or the first preamble quantity based on a first configuration parameter included in the first type RACH resource configuration information;

[0456] The first configuration parameter is used to indicate the first starting preamble index and / or the first preamble quantity.

[0457] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0458] Determine the first starting preamble index and the first preamble quantity based on the first type of RACH resource configuration information and / or the second type of RACH resource configuration information;

[0459] The first starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the first preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0460] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0461] Determine the Preamble information of the first type of shared RO in the first type of RACH resource configuration information based on the second condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0462] The second condition includes:

[0463] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0464] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0465] There is an intersection between the first type ROs actually used by the two RACH resources.

[0466] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0467] Determine, based on the type of the shared RO, the first condition, the second condition, the first type of random access channel RACH resource configuration information, and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information;

[0468] The first condition includes:

[0469] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0470] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0471] There is an intersection between the second type ROs actually used by the two RACH resources;

[0472] The second condition includes:

[0473] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0474] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0475] There is an intersection between the first type ROs actually used by the two RACH resources.

[0476] In some embodiments, the first type of RACH resource configuration information is transmitted after the second type of RACH resource configuration information.

[0477] In some embodiments, the first type of RACH resource configuration information is cell-specific configuration information or terminal-specific configuration information.

[0478] In some embodiments, the first type RACH resource configuration information is configured with an RO actually used in the first type shared RO and / or the second type shared RO.

[0479] In some embodiments, the number of Preambles contained in an SSB-associated RO in the first type of shared RO and the second type of shared RO configured with the first type of RACH resource configuration information is the same or different.

[0480] In some embodiments, the RA is contention-based random access (CBRA).

[0481] In some embodiments, the number of preambles included in the RO associated with an SSB corresponds to a contention-based preamble.

[0482] In some embodiments, the first type of SBFD time unit is one of the following:

[0483] The time unit is configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration (TDD-UL-DL-ConfigCommon) and is also configured as a SBFD time unit.

[0484] The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit and is configured as a SBFD time unit.

[0485] In some embodiments, the second-type RACH resource configuration information is not configured in the additional RACH configuration AdditionalRACH-Config; the first-type RACH resource configuration information is not configured in the AdditionalRACH-Config; the first-type RACH resource configuration information is configured in the AdditionalRACH-Config; the first RACH resource configuration information is configured in the AdditionalRACH-Config and the second RACH resource configuration information is not configured in the AdditionalRACH-Config; the first RACH resource configuration information is not configured in the AdditionalRACH-Config and the second RACH resource configuration information is configured in the AdditionalRACH-Config.

[0486] In some embodiments, the method further comprises:

[0487] receiving first information sent by a network device;

[0488] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information.

[0489] Figure 4a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4a, the communication method according to the embodiment of the present disclosure is executed by a network device, and the method includes:

[0490] Step S4101: The network device sends first information to the terminal.

[0491] In some embodiments, the optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0492] Step S4102: The network device determines the preamble information.

[0493] In some embodiments, the optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0494] The information indication method involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment, and step S4102 may be implemented as an independent embodiment, but the present disclosure is not limited thereto. The different steps may be performed in a different order if they do not conflict, and this is not a limitation here.

[0495] Figure 4b is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 4b, the embodiment of the present disclosure relates to a communication method, which is executed by a network device, and the method includes:

[0496] Step S4201: Determine the preamble information of the random access opportunity RO in the first type of RACH configuration resource information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0497] The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

[0498] In some embodiments, the optional implementation of step S4201 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0499] In some embodiments, determining the preamble information of the random access opportunity RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0500] Determine, based on a first configuration parameter included in the first type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information;

[0501] Based on the first configuration parameter included in the first type of RACH resource configuration information and the second type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information is determined.

[0502] In some embodiments, the second type of RACH resource configuration information includes third RACH resource configuration information of 4-step RA for second type terminals and / or fourth RACH resource configuration information of 2-step RA for second type terminals, and the second type terminals are terminals that cannot recognize SBFD time-frequency configuration.

[0503] In some embodiments, the Preamble information includes at least one of the following:

[0504] A first starting preamble index, where the first starting preamble index is a starting preamble index of a first type of shared RO in the first type of RACH configuration resource information, where the first type of shared RO is a shared RO including a first type of SBFD time unit;

[0505] The first number of preambles is the number of preambles contained in the first type of shared RO associated with a synchronization signal block SSB;

[0506] A second starting Preamble index, where the second starting Preamble index is a starting Preamble index of a second type of shared RO in the first type of RACH configuration resource information, where the second type of shared RO is a shared RO that does not include a first type of SBFD time unit;

[0507] The second number of preambles is the number of preambles contained in the second type of shared RO associated with an SSB.

[0508] In some embodiments, determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the random access opportunity RO in the first type of RACH configuration resource information includes:

[0509] Based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH configuration resource information is determined.

[0510] In some embodiments, determining, based on the first type of random access channel RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes:

[0511] Determine the second starting preamble index and / or the number of second preambles based on the first configuration parameter included in the first type of RACH resource configuration information;

[0512] The first configuration parameter is used to indicate the second starting preamble index and / or the second preamble quantity.

[0513] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0514] Determine the second starting preamble index and the second preamble quantity based on the first type RACH resource configuration information and / or the second type RACH resource configuration information;

[0515] The second starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the second preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0516] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0517] Determine the Preamble information of the second type of shared RO in the first type of RACH resource configuration information based on the type of shared RO, the first condition, and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0518] The first condition includes:

[0519] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0520] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0521] There is an intersection between the second type ROs actually used by the two RACH resources.

[0522] In some embodiments, the method further comprises at least one of the following:

[0523] Determine the first starting preamble index as the second starting preamble index;

[0524] Determine the first preamble quantity as the second preamble quantity.

[0525] In some embodiments, determining, based on the first type of random access channel RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes:

[0526] Determine the first starting preamble index and / or the first preamble quantity based on a first configuration parameter included in the first type RACH resource configuration information;

[0527] The first configuration parameter is used to indicate the first starting preamble index and / or the first preamble quantity.

[0528] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes one of the following:

[0529] Determine the first starting preamble index and the first preamble quantity based on the first type of RACH resource configuration information and / or the second type of RACH resource configuration information;

[0530] The first starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the first preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

[0531] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0532] Determine the Preamble information of the first type of shared RO in the first type of RACH resource configuration information based on the second condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information;

[0533] The second condition includes:

[0534] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0535] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0536] There is an intersection between the first type ROs actually used by the two RACH resources.

[0537] In some embodiments, determining the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information includes:

[0538] Determine, based on the first condition, the second condition, the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information;

[0539] The first condition includes:

[0540] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0541] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0542] There is an intersection between the second type ROs actually used by the two RACH resources;

[0543] The second condition includes:

[0544] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information;

[0545] The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0546] There is an intersection between the first type ROs actually used by the two RACH resources.

[0547] In some embodiments, the first type of RACH resource configuration information is transmitted after the second type of RACH resource configuration information.

[0548] In some embodiments, the first type of RACH resource configuration information is cell-specific configuration information or terminal-specific configuration information.

[0549] In some embodiments, the first type RACH resource configuration information is configured with an RO actually used in the first type shared RO and / or the second type shared RO.

[0550] In some embodiments, the number of Preambles contained in an SSB-associated RO in the first type of shared RO and the second type of shared RO configured with the first type of RACH resource configuration information is the same or different.

[0551] In some embodiments, the RA is contention-based random access (CBRA).

[0552] In some embodiments, the number of preambles included in the RO associated with an SSB corresponds to a contention-based preamble.

[0553] In some embodiments, the first type of SBFD time unit is one of the following:

[0554] The time unit is configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration (TDD-UL-DL-ConfigCommon) and is also configured as a SBFD time unit.

[0555] The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit and is configured as a SBFD time unit.

[0556] In some embodiments, the second-type RACH resource configuration information is not configured in the additional RACH configuration AdditionalRACH-Config; the first-type RACH resource configuration information is not configured in the AdditionalRACH-Config; the first-type RACH resource configuration information is configured in the AdditionalRACH-Config; the first RACH resource configuration information is configured in the AdditionalRACH-Config and the second RACH resource configuration information is not configured in the AdditionalRACH-Config; the first RACH resource configuration information is not configured in the AdditionalRACH-Config and the second RACH resource configuration information is configured in the AdditionalRACH-Config.

[0557] In some embodiments, the method further comprises:

[0558] Sending first information to the terminal;

[0559] The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information.

[0560] Figure 5a is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 5a, the embodiment of the present disclosure relates to a communication method, which is executed by a communication system. The method includes:

[0561] Step S5101: The network device sends first information to the terminal.

[0562] In some embodiments, the first information includes the first type of RACH resource configuration information and / or the second type of RACH resource configuration information; the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information is used to determine the preamble information of the random access opportunity RO in the first type of RACH configuration resource information; the first type of RACH resource configuration information includes first RACH resource configuration information of 4-step random access RA for a first type of terminal and / or second RACH resource configuration information of 2-step RA for a first type of terminal, and the first type of terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

[0563] In some embodiments, optional implementations of step S5101 may refer to the optional implementations of the steps in FIG. 2 a and other related parts in the embodiment involved in FIG. 2 a , and will not be described in detail here.

[0564] In order to better understand the embodiments of the present disclosure, the technical solution of the present disclosure is further described below through five exemplary embodiments:

[0565] Example 1:

[0566] In some embodiments, the SBFD aware UE terminal (corresponding to the first type of terminal) determines the starting preamble index (corresponding to the second starting preamble index) of a shared legacy RO (corresponding to the second type of shared RO) and the number of preambles contained in a shared legacy RO associated with an SSB (corresponding to the second preamble number).

[0567] In some embodiments, two or more of the following four RACH configurations exist in the network, including at least one of RACH configuration #3 and RACH configuration #4:

[0568] RACH config #1 for 4-step RA of legacy UEs;

[0569] RACH config #2 for 2-step RA of legacy UEs;

[0570] RACH config #3 for 4-step RA of SBFD aware UE;

[0571] RACH config#4 for 2-step RA of SBFD aware UE.

[0572] In some embodiments, the first condition includes:

[0573] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource (first RACH resource configuration information for four-step random access RA for first-type terminals, corresponding to RACH config#3, and / or second RACH resource configuration information for two-step RA for first-type terminals, corresponding to RACH config#4) configuration information or a resource configured by the second-type RACH resource (first RACH resource configuration information for four-step random access RA for second-type terminals, corresponding to RACH config#1 and / or second RACH resource configuration information for two-step RA for second-type terminals, corresponding to RACH config#2);

[0574] The second type ROs (corresponding to legacy ROs) of the two RACH resources are located at the same time domain and frequency domain positions;

[0575] There is an intersection between the second type ROs actually used by the two RACH resources.

[0576] In some embodiments, Solution 1: Determine the starting preamble of the shared legacy RO in RACH config#3 and / or RACH config#4 and the number of preambles included in an SSB-associated RO based on other RACH resource configurations or newly added parameter configurations.

[0577] In some embodiments, scheme 1-1: configure the starting preamble index of the shared legacy RO and the number of preambles included in the shared legacy RO associated with an SSB in RACH config#3 and / or RACH config#4.

[0578] In some embodiments, scheme 1-2: according to other RACH resource configurations, determine the starting preamble of the shared legacy RO in RACH config#3 and / or RACH config#4, and determine the number of preambles included in an SSB-associated RO in the shared legacy RO in RACH config#3 and / or RACH config#4 according to other RACH resource configurations or newly added parameter configurations.

[0579] For example, the total number of Preambles is The SSB corresponding to a valid RO in RACH config#1, RACH config#2, RACH config#3 and RACH config#4 contains R, Q, R_2 and Q_2 preambles respectively, and N SSBs are associated with one valid RO.

[0580] For example, the starting preamble index of the shared legacy RO in RACH config #3 and the number of preambles contained in the shared legacy RO associated with an SSB are:

[0581] For example, the starting Preamble is:

[0582] Option 1: When N is less than 1, the starting preamble index is R_3+Q_3. When N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0583] For example, the number of preambles is:

[0584] Option 1:

[0585] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be R_2, and not more than

[0586] Exemplarily, when RACH config#1 and RACH config#3 meet the first condition, R_3 takes the value R; otherwise, R_3 takes the value 0.

[0587] Exemplarily, when RACH config#2 and RACH config#3 meet the first condition, Q_3 takes the value Q; otherwise, Q_3 takes the value 0.

[0588] For example, the starting preamble index of the shared legacy RO in RACH config #4 and the number of preambles contained in the shared legacy RO associated with an SSB are:

[0589] For example, the starting Preamble is:

[0590] Option 1: When N is less than 1, the starting preamble index is R_3+Q_3+R_4. When N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0591] For example, the number of preambles contained in an RO associated with an SSB is:

[0592] Option 1:

[0593] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be Q_2, and not more than

[0594] In some embodiments, when RACH config#1 and RACH config#4 meet the first condition, R_3 takes the value R, otherwise R_3 takes the value 0.

[0595] In some embodiments, when RACH config #2 and RACH config #4 meet the first condition, Q_3 takes the value Q, otherwise Q_3 takes the value 0.

[0596] In some embodiments, when RACH config#3 and RACH config#4 meet the first condition, R_4 takes the value R_2; otherwise, R_4 takes the value 0.

[0597] In solution 1-1, directly adding parameter configuration can avoid the overly complicated method of determining the starting preamble index of the shared legacy RO in RACH config#3 and / or RACH config#4 and the number of preambles contained in the shared legacy RO associated with an SSB.

[0598] In schemes 1-2, determining the starting preamble index of the shared legacy RO in RACH config#3 and / or RACH config#4 based on other RACH resource configurations can reduce signaling overhead. Determining the number of preambles contained in a shared legacy RO associated with an SSB in RACH config#3 and / or RACH config#4 based on other RACH resource configurations can reduce signaling overhead. Directly configuring the number of preambles contained in a shared legacy RO associated with an SSB can simplify the process of confirming the number of preambles.

[0599] In solution 1-2, when RACH config#3 and RACH config#4 meet the first condition, the number of preambles contained in the shared legacy RO associated with an SSB in RACH config#3 needs to be explicitly configured, that is, using Option 2.

[0600] In some embodiments, referring to FIG6a , a configuration diagram of solution 1-2 is as follows:

[0601] There are two SSBs, N = 2, that is, two SSBs are mapped to one RO, and RACH config #1, RACH config #2, RACH config #3, and RACH config #4 all meet the first condition. The SSB corresponding to a valid RO in RACH config #1, RACH config #2, RACH config #3, and RACH config #4 contains R, Q, R_2, and Q_2 preambles, respectively.

[0602] For example, the starting preamble index of the shared legacy RO in RACH config #3 and the number of preambles contained in the shared legacy RO associated with an SSB are:

[0603] For example, the starting Preamble is:

[0604] Option 1: The starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0605] For example, the number of preambles is:

[0606] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be R_2, and not more than

[0607] For example, the starting preamble index of the shared legacy RO in RACH config #4 and the number of preambles contained in the shared legacy RO associated with an SSB are:

[0608] For example, the starting Preamble is:

[0609] For example, Option 1: The starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0610] For example, the number of preambles contained in an RO associated with an SSB is:

[0611] Option 2: Configure the number of preambles contained in a shared legacy RO associated with an SSB to be Q_2, and not more than

[0612] Example 2

[0613] In some embodiments, the SBFD aware UE terminal determines the starting preamble index of the shared additional RO and the number of preambles contained in the shared additional RO associated with an SSB.

[0614] In some embodiments, two or more of the following four RACH configurations exist in the network, including at least one of RACH configuration #3 and RACH configuration #4:

[0615] RACH config #1 for 4-step RA of legacy UEs;

[0616] RACH config #2 for 2-step RA of legacy UEs;

[0617] RACH config #3 for 4-step RA of SBFD aware UE;

[0618] RACH config#4 for 2-step RA of SBFD aware UE.

[0619] In some embodiments, the first condition includes:

[0620] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource (first RACH resource configuration information for four-step random access RA for first-type terminals, corresponding to RACH config#3, and / or second RACH resource configuration information for two-step RA for first-type terminals, corresponding to RACH config#4) configuration information or a resource configured by the second-type RACH resource (first RACH resource configuration information for four-step random access RA for second-type terminals, corresponding to RACH config#1, and / or second RACH resource configuration information for two-step RA for second-type terminals, corresponding to RACH config#2);

[0621] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0622] There is an intersection between the second type ROs actually used by the two RACH resources.

[0623] In some embodiments, the second condition includes:

[0624] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource (first RACH resource configuration information for four-step random access RA for first-type terminals, corresponding to RACH config#3, and / or second RACH resource configuration information for two-step RA for first-type terminals, corresponding to RACH config#4) configuration information or a resource configured by the second-type RACH resource (first RACH resource configuration information for four-step random access RA for second-type terminals, corresponding to RACH config#1 and / or second RACH resource configuration information for two-step RA for second-type terminals, corresponding to RACH config#2);

[0625] The first type ROs (corresponding to additional ROs) of the two RACH resources are located at the same time domain and frequency domain positions;

[0626] There is an intersection between the first type ROs actually used by the two RACH resources.

[0627] In some embodiments, solution 2: determining the starting preamble of the shared additional RO in RACH config#3 and / or RACH config#4 and the number of preambles included in an SSB-associated RO based on other RACH resource configurations or newly added parameter configurations.

[0628] In some embodiments, in solution 2-1: the starting preamble of the shared additional RO, the number of preambles included in an SSB-associated RO is the same as that of the legacy shared RO.

[0629] In some embodiments, the starting preamble of the shared legacy RO and the number of preambles contained in an SSB-associated RO are determined according to solution 1-1 or 1-2.

[0630] In some embodiments, scheme 2-2: configure the starting preamble index of the shared additional RO and the number of preambles included in the shared additional RO associated with one SSB in RACH config#3 and / or RACH config#4.

[0631] In some embodiments, scheme 2-3: according to the configuration parameters of RACH config#3 or the protocol default, determine the starting preamble of the shared additional RO in RACH config#3, and determine the number of preambles contained in the RO associated with an SSB in the shared additional RO; according to other RACH resource configurations, determine the starting preamble of the shared additional RO in RACH config#4, and determine the number of preambles contained in the RO associated with an SSB in the shared additional RO in RACH config#4 according to other RACH resource configurations or newly added parameter configurations.

[0632] For example, the total number of Preambles is In RACH config #3 and RACH config #4, the SSB corresponding to a valid RO contains R_2 and Q_2 preambles respectively, and N SSBs are associated with one valid RO.

[0633] For example, the starting preamble index of the shared additional RO in RACH config #3 and the number of preambles contained in the shared additional RO associated with one SSB are:

[0634] For example, the starting Preamble is:

[0635] Option 1: When N is less than 1, the starting preamble index is 0. When N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0636] For example, the number of preambles is:

[0637] Option 1:

[0638] Option 2: Configure the number of preambles contained in the shared additional RO associated with an SSB to be R_2, and not more than

[0639] For example, the starting preamble index of the shared additional RO in RACH config #4 and the number of preambles contained in the shared additional RO associated with one SSB are R_2:

[0640] For example, the starting Preamble is:

[0641] Option 1: When N is less than 1, the starting preamble index is R_4. When N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0642] For example, the number of preambles contained in an RO associated with an SSB is:

[0643] Option 1:

[0644] Option 2: Configure the number of preambles contained in the shared additional RO associated with an SSB to be Q_2, and not more than

[0645] Exemplarily, when RACH config #3 and RACH config #4 meet the second condition, R_4 takes the value R_2; otherwise, R_4 takes the value 0.

[0646] In some embodiments, in scheme 2-1, the starting Preamble of the shared additional RO and the number of Preambles contained in the RO associated with an SSB are the same as the shared additional RO. The starting Preamble of the shared additional RO and the number of Preambles contained in the RO associated with an SSB are determined according to scheme 1-1 or 1-2. For details, please refer to the description in example 1.

[0647] In solution 2-2, directly adding parameter configuration can avoid the overly complicated method of determining the starting preamble index of the shared additional RO in RACH config#3 and / or RACH config#4 and the number of preambles contained in the shared additional RO associated with an SSB.

[0648] In options 2 and 3, the configuration parameters or protocol defaults in RACH config #3 determine the starting preamble index of the shared additional RO in RACH config #3 and the number of preambles contained in the shared additional RO associated with an SSB, which can reduce signaling overhead. Based on other RACH resource configurations, the starting preamble index of the shared additional RO in RACH config #4 and the number of preambles contained in the shared additional RO associated with an SSB can also reduce signaling overhead. Directly configuring the number of preambles contained in the shared additional RO associated with an SSB can simplify the process of confirming the number of preambles.

[0649] In solution 2-3, when RACH config#3 and RACH config#4 meet the first condition, the number of preambles contained in the shared additional RO associated with an SSB in RACH config#3 needs to be explicitly configured, that is, using Option 2.

[0650] In some embodiments, please refer to 1f again, a configuration diagram of scheme 2-3 is as follows:

[0651] There are 2 SSBs, N=2, that is, 2 SSBs are mapped to 1 RO, and RACH config#3 and RACH config#4 meet the first condition. The SSB corresponding to a valid RO in RACH config#3 and RACH config#4 contains R_2 and Q_2 preambles respectively.

[0652] For example, the starting preamble index of the shared additional RO in RACH config #3 and the number of preambles contained in the shared additional RO associated with an SSB are:

[0653] For example, the starting Preamble is:

[0654] Option 1: The starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0655] For example, the number of preambles is:

[0656] Option 2: Configure the number of preambles contained in the shared additional RO associated with an SSB to be R_2, and not more than

[0657] For example, the starting preamble index of the shared additional RO in RACH config #4 and the number of preambles contained in the shared additional RO associated with an SSB are:

[0658] For example, the starting Preamble is:

[0659] Option 1: The starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0660] For example, the number of preambles contained in an RO associated with an SSB is:

[0661] Option 2: Configure the number of preambles contained in the shared additional RO associated with an SSB to be Q_2, and not more than

[0662] Example 3

[0663] In some embodiments, the SBFD aware UE terminal determines the starting preamble index of the shared additional RO and the number of preambles contained in the shared additional RO associated with an SSB.

[0664] In some embodiments, two or more of the following four RACH configurations exist in the network, including at least one of RACH configuration #3 and RACH configuration #4:

[0665] RACH config #1 for 4-step RA of legacy UEs;

[0666] RACH config #2 for 2-step RA of legacy UEs;

[0667] RACH config #3 for 4-step RA of SBFD aware UE;

[0668] RACH config#4 for 2-step RA of SBFD aware UE.

[0669] In some embodiments, the first condition includes:

[0670] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource (first RACH resource configuration information for four-step random access RA for first-type terminals, corresponding to RACH config#3, and / or second RACH resource configuration information for two-step RA for first-type terminals, corresponding to RACH config#4) configuration information or a resource configured by the second-type RACH resource (first RACH resource configuration information for four-step random access RA for second-type terminals, corresponding to RACH config#1 and / or second RACH resource configuration information for two-step RA for second-type terminals, corresponding to RACH config#2);

[0671] The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions;

[0672] There is an intersection between the second type ROs actually used by the two RACH resources.

[0673] In some embodiments, the second condition includes:

[0674] Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource (first RACH resource configuration information for four-step random access RA for first-type terminals, corresponding to RACH config#3, and / or second RACH resource configuration information for two-step RA for first-type terminals, corresponding to RACH config#4) configuration information or a resource configured by the second-type RACH resource (first RACH resource configuration information for four-step random access RA for second-type terminals, corresponding to RACH config#1 and / or second RACH resource configuration information for two-step RA for second-type terminals, corresponding to RACH config#2);

[0675] The first type ROs (corresponding to additional ROs) of the two RACH resources are located at the same time domain and frequency domain positions;

[0676] There is an intersection between the first type ROs actually used by the two RACH resources.

[0677] In some embodiments, Solution 3: Determine a starting preamble of a first shared RO in RACH config#3 and / or RACH config#4 based on other RACH resource configurations, and determine the number of preambles included in an SSB-associated RO in the first shared RO in RACH config#3 and / or RACH config#4 based on other RACH resource configurations or newly added parameter configurations. The first shared RO is a shared legacy RO and / or a shared additional RO.

[0678] In some embodiments, scheme 3-1: the fifth RACH resource is one of RACH config#3 and RACH config#4. The total number of preambles is N SSBs are associated with 1 valid RO.

[0679] Option 1: The first shared RO is a shared legacy RO, only one of RACH config #3 and RACH config #4 or RACH config #3 and RACH config #4 do not meet the first condition, and any RACH resource configuration in other RACH resource configurations and the fifth RACH resource meet the first condition.

[0680] Option 2: The first shared RO is a shared additional RO, only one of RACH config #3 and RACH config #4 or RACH config #3 and RACH config #4 do not meet the second condition, and any RACH resource configuration in other RACH resource configurations and the fifth RACH resource meet the second condition.

[0681] In Option 1 and / or Option 2:

[0682] Exemplarily, the starting preamble index of the first shared RO in the fifth RACH resource and the number of preambles contained in the first shared RO associated with one SSB are:

[0683] For example, the starting Preamble is:

[0684] Option 1: When N is less than 1, the starting preamble index is X_2. When N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0685] For example, the number of preambles is:

[0686] Option 1:

[0687] Option 2: Configure the number of preambles contained in the first shared RO of an SSB association to be P_5, and not more than

[0688] Exemplarily, X_2 refers to the sum of the number of Preambles contained in the SSBs corresponding to the valid ROs in other RACH resource configurations.

[0689] In some embodiments, scheme 3-2: the fifth RACH resource is one of RACH config#3 and RACH config#4, the sixth RACH resource is another RACH resource of RACH config#3 and RACH config#4 except the fifth RACH resource, and the total number of preambles is N SSBs are associated with 1 valid RO.

[0690] Option 1: The first shared RO is a shared legacy RO, RACH config#3 and RACH config#4 meet the first condition, and any RACH resource configuration in other RACH resource configurations and RACH config#3 meet the first condition.

[0691] Option 2: The first shared RO is a shared additional RO, RACH config#3 and RACH config#4 meet the second condition, and any RACH resource configuration in other RACH resource configurations and RACH config#3 meet the second condition.

[0692] In Option 1 and / or Option 2,

[0693] Exemplarily, scheme 1-1 or scheme 1-2 or scheme 2-1 or scheme 2-2 or scheme 2-3 is used to determine the starting preamble index of the first shared RO in the fifth RACH resource and the number of preambles P_5_2 contained in the first shared RO associated with one SSB.

[0694] Exemplarily, the starting preamble index of the first shared RO in the sixth RACH resource and the number of preambles contained in the first shared RO associated with one SSB are:

[0695] For example, the starting Preamble is:

[0696] Option 1: When N is less than 1, the starting preamble index is Y_2+P_5_2. When N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0697] For example, the number of preambles is:

[0698] Option 1:

[0699] Option 2: Configure the number of preambles contained in the first shared RO of an SSB association to be P_6_2, and not more than

[0700] Exemplarily, Y_2 refers to the sum of the number of Preambles contained in the SSBs corresponding to the valid ROs in other RACH resource configurations.

[0701] Exemplarily, the other RACH resource configurations include RACH resources configured in RACH config#1, RACH config#2 and / or AdditionalRACH-Config.

[0702] In solution 3-1, the starting preamble index of the shared legacy RO and / or shared additional RO in RACH config#3 or RACH config#4 is determined based on other RACH resource configurations. The number of preambles contained in the shared legacy RO and / or shared additional RO associated with an SSB in RACH config#3 or RACH config#4 is determined based on other RACH resource configurations or newly added configurations, which can reduce a certain amount of signaling overhead.

[0703] In solution 3-2, the starting preamble index of the shared legacy RO and / or shared additional RO in RACH config #3 is determined according to solution 1-1, 1-2, 2-1, 2-2, or 2-3, and the number of preambles contained in the shared legacy RO and / or shared additional RO associated with an SSB in RACH config #3 is determined. Its advantages and disadvantages can be found in Example 1 and Example 2.

[0704] Based on other RACH resource configurations, determine the starting preamble index of the shared legacy RO and / or shared additional RO in RACH config #4. Based on other RACH resource configurations or newly added configurations, determine the number of preambles contained in the shared legacy RO and / or shared additional RO associated with an SSB in RACH config #4, which can reduce certain signaling overhead.

[0705] In some embodiments, referring to FIG6b , a configuration diagram of solution 3-2 is as follows:

[0706] There are two SSBs, N=2, that is, two SSBs are mapped to one RO, and the other RACH resource configurations, RACH config#3 and RACH config#4, all meet the first condition. The first shared RO is a legacy shared RO, the fifth RACH resource is RACH config#3, and the sixth RACH resource is RACH config#4.

[0707] Exemplarily, the number of Preambles included in the first shared RO is P_5_2.

[0708] Exemplarily, the sum of the number of Preambles contained in the SSBs corresponding to the valid ROs in other RACH resource configurations is Y_2.

[0709] For example, the starting preamble index of the first shared RO in RACH config #4 and the number of preambles contained in the first shared RO associated with an SSB are:

[0710] For example, the starting Preamble is:

[0711] Option 1: When N is less than 1, the starting preamble index is Y_2+P_5_2. When N is greater than or equal to 1, the starting preamble index of the nth SSB (0≤n≤N-1) among N SSBs is

[0712] For example, the number of preambles is:

[0713] Option 2: Configure the number of preambles contained in the first shared RO of an SSB association to be P_6_2, and not more than

[0714] Example 4

[0715] In some embodiments, in RACH config#3 and / or RACH config#4, the RO actually used in the Shared legacy RO and / or Shared additional RO is configured, such as using SharedRO-MaskIndex to configure a subset of the Shared legacy RO and / or Shared additional RO.

[0716] In some embodiments, in RACH config #3 and / or RACH config #4, the number of preambles contained in an RO associated with an SSB in a Shared legacy RO and a Shared additional RO is the same or different.

[0717] For example, when the number of preambles is different, the preambles contained in an SSB-associated RO in the Shared additional RO are the union of set 1 and set 2.

[0718] Exemplarily, set 1 includes: the Preamble contained in an SSB-associated RO of the SBFD aware UE in the Shared legacy RO.

[0719] Exemplarily, set 2 includes: the Preamble contained in an RO associated with an SSB in the Shared legacy RO of the legacy UE.

[0720] In some embodiments, the additional RO and legacy RO are used as defined below:

[0721] Additional RO refers to an RO that includes at least one first-class SBFD symbol, and legacy RO refers to an RO that does not include the first-class SBFD symbol;

[0722] Option 1: The first type of SBFD symbol refers to the symbol configured as a DL time unit in TDD-UL-DL-ConfigCommon and configured as SBFD;

[0723] Option 2: The first type of SBFD symbol refers to the symbol configured as DL time unit or flexible time unit in TDD-UL-DL-ConfigCommon and configured as SBFD

[0724] In some embodiments, the disclosed embodiments may be used in a CBRA.

[0725] In some embodiments, the Preamble in the number of Preambles included in the RO associated with an SSB is a contention based Preamble.

[0726] In some embodiments, RACH config#1 for 4-step RA of legacy UE (RACH config#1 for 4-step random access of second type terminals) and RACH config#2 for 2-step RA of legacy UE (RACH config#2 for 2-step random access of second type terminals) are not configured in AdditionalRACH-Config.

[0727] In some embodiments, RACH config#3 for 4-step RA of SBFD aware UE (RACH config#3 for 4-step random access of first type terminal) and RACH config#4 for 2-step RA of SBFD aware UE (RACH config#4 for 2-step random access of first type terminal) are not configured in AdditionalRACH-Config.

[0728] In some embodiments, RACH config#3 for 4-step RA of SBFD aware UE and RACH config#4 for 2-step RA of SBFD aware UE are configured in AdditionalRACH-Config.

[0729] In some embodiments, RACH config#3 for 4-step RA of SBFD aware UE is not configured in AdditionalRACH-Config, and RACH config#4 for 2-step RA of SBFD aware UE is configured in AdditionalRACH-Config.

[0730] In some embodiments, RACH config#3 for 4-step RA of SBFD aware UE is configured in AdditionalRACH-Config, and RACH config#4 for 2-step RA of SBFD aware UE is not configured in AdditionalRACH-Config.

[0731] Example 5

[0732] Referring to FIG. 6 c , a communication method is provided, the method comprising:

[0733] Step S6101: Receive first information, which configures the time-frequency position of RO, the time domain position of SSB, and the mapping relationship between SSB and valid RO.

[0734] In some embodiments, the first information includes RACH resource configuration information of an SBFD aware UE or RACH resource configuration information of an SBFD aware UE and a legacy UE.

[0735] Step S6102: Determine the SSBs associated with the valid RO and the preamble used by each SSB based on the first information.

[0736] In some embodiments, according to Solution 1 and Solution 2, the SBFD aware UE determines the RO and Preamble associated with the SSB.

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

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

[0739] The disclosed embodiments address passive IoT terminals. Different terminal types and capacitor sizes can affect the terminal's data transmission capabilities and the intervals between data transmissions. The disclosed embodiments define the terminal's data transmission capabilities and report them to the network, assisting the network in effectively triggering the terminal to report data.

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

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

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

[0743] Figure 7a is a schematic diagram of the structure of a terminal 7100 according to an embodiment of the present disclosure. As shown in Figure 7a, terminal 7100 may include at least one of a transceiver module 7101 and a processing module 7102. Optionally, transceiver module 7101 is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by terminal 7100 in any of the above methods, which are not further described here. Optionally, processing module 7102 is configured to perform at least one of the other steps performed by terminal 7100 in any of the above methods, which are not further described here.

[0744] Figure 7b is a schematic diagram of the structure of a network device 7200 according to an embodiment of the present disclosure. As shown in Figure 7b, network device 7200 may include at least one of a transceiver module 7201 and a processing module 7202. Optionally, transceiver module 7201 is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by network device 7200 in any of the above methods, which are not further described here. Optionally, processing module 7202 is configured to perform at least one of the other steps performed by network device 7200 in any of the above methods, which are not further described here.

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

[0746] Figure 8a is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 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 8100 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.

[0747] As shown in Figure 8a, the communication device 8100 includes one or more processors 8101. The processor 8101 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, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

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

[0749] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 8101 performs at least one of the other steps.

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

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

[0752] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8a. 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.

[0753] FIG8b is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 8200 shown in FIG8b, but the present disclosure is not limited thereto.

[0754] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

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

[0756] In some embodiments, the interface circuit 8202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S3101, but not limited thereto), and the processor 8201 executes at least one of the other steps.

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

[0758] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0759] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 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 temporary storage medium.

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

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

Claims

1. A communication method, characterized in that: The method is performed by a first type terminal, and the method includes: Determine, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, preamble information of the random access opportunity RO in the first type of RACH configuration resource information; The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

2. The method according to claim 1, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the random access opportunity RO in the first type of RACH resource configuration information includes one of the following: Determine, based on a first configuration parameter included in the first type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information; Based on the first configuration parameter included in the first type of RACH resource configuration information and the second type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information is determined.

3. The method according to claim 1 or 2, characterized in that The second type of RACH resource configuration information includes third RACH resource configuration information of 4-step RA for second type terminals and / or fourth RACH resource configuration information of 2-step RA for second type terminals. The second type terminals are terminals that cannot recognize SBFD time-frequency configuration.

4. The method according to any one of claims 1 to 3, characterized in that The Preamble information includes at least one of the following: A first starting preamble index, where the first starting preamble index is a starting preamble index of a first type of shared RO in the first type of RACH configuration resource information, where the first type of shared RO is a shared RO including a first type of SBFD time unit; The first number of preambles is the number of preambles contained in the first type of shared RO associated with a synchronization signal block SSB; A second starting Preamble index, where the second starting Preamble index is a starting Preamble index of a second type of shared RO in the first type of RACH configuration resource information, where the second type of shared RO is a shared RO that does not include a first type of SBFD time unit; The second number of preambles is the number of preambles contained in the second type of shared RO associated with an SSB.

5. The method according to claim 1, wherein The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, preamble information of the random access opportunity RO in the first type of RACH configuration resource information includes: Based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH configuration resource information is determined.

6. The method according to claim 5, characterized in that The determining, based on the first type of random access channel RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the second starting preamble index and / or the number of second preambles based on the first configuration parameter included in the first type of RACH resource configuration information; The first configuration parameter is used to indicate the second starting preamble index and / or the second preamble quantity.

7. The method according to claim 5, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes one of the following: Determine the second starting preamble index and the second preamble quantity based on the first type RACH resource configuration information and / or the second type RACH resource configuration information; The second starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the second preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

8. The method according to claim 7, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the Preamble information of the second type of shared RO in the first type of RACH resource configuration information based on the first condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information; The first condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the second type ROs actually used by the two RACH resources.

9. The method according to any one of claims 5 to 8, characterized in that The method further comprises at least one of the following: Determine the first starting preamble index as the second starting preamble index; Determine the first preamble quantity as the second preamble quantity.

10. The method according to claim 5, characterized in that The determining, based on the first type of random access channel RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the first starting preamble index and / or the first preamble quantity based on a first configuration parameter included in the first type RACH resource configuration information; The first configuration parameter is used to indicate the first starting preamble index and / or the first preamble quantity.

11. The method according to claim 5, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes one of the following: The first starting point is determined based on the first type RACH resource configuration information and / or the second type RACH resource configuration information. Preamble index and the number of the first preambles; The first starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the first preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

12. The method according to claim 5, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the Preamble information of the first type of shared RO in the first type of RACH resource configuration information based on the second condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information; The second condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the first type ROs actually used by the two RACH resources.

13. The method according to claim 5, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine, based on the type of the shared RO, the first condition, the second condition, the first type of random access channel RACH resource configuration information, and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information; The first condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the second type ROs actually used by the two RACH resources; The second condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the first type ROs actually used by the two RACH resources.

14. The method according to any one of claims 1 to 13, characterized in that The first type of RACH resource configuration information is transmitted after the second type of RACH resource configuration information.

15. The method according to claim 14, characterized in that The first type of RACH resource configuration information is cell-specific configuration information or terminal-specific configuration information.

16. The method according to any one of claims 1 to 13, characterized in that The first type RACH resource configuration information is configured with an RO actually used in the first type shared RO and / or the second type shared RO.

17. The method according to any one of claims 1 to 13, characterized in that The number of Preambles contained in an SSB-associated RO in the first type shared RO and the second type shared RO configured with the first type RACH resource configuration information is the same or different.

18. The method according to any one of claims 1 to 13, characterized in that The RA is contention-based random access (CBRA).

19. The method according to any one of claims 1 to 13, characterized in that The number of preambles included in the RO associated with an SSB corresponds to the contention-based preamble.

20. The method according to any one of claims 1 to 13, characterized in that The first type of SBFD time unit is one of the following: The time unit is configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration (TDD-UL-DL-ConfigCommon) and is also configured as a SBFD time unit. The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit and is configured as a SBFD time unit.

21. The method according to any one of claims 1 to 13, characterized in that The second type of RACH resource configuration information is not configured in the additional RACH configuration AdditionalRACH-Config; the first type of RACH resource configuration information is not configured in AdditionalRACH-Config; the first type of RACH resource configuration information is configured in AdditionalRACH-Config; the first RACH resource configuration information is configured in AdditionalRACH-Config and the second RACH resource configuration information is not configured in AdditionalRACH-Config; the first RACH resource configuration information is not configured in AdditionalRACH-Config and the second RACH resource configuration information is configured in AdditionalRACH-Config.

22. The method according to any one of claims 1 to 21, characterized in that The method further comprises: receiving first information sent by a network device; The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information.

23. A communication method, characterized in that: The method is performed by a network device, and includes: Determine, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, preamble information of the random access opportunity RO in the first type of RACH configuration resource information; The first type of RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for first type terminals and / or second RACH resource configuration information for 2-step RA for first type terminals, and the first type terminals are terminals that can identify sub-band full-duplex SBFD time-frequency configuration.

24. The method according to claim 23, wherein The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the random access opportunity RO in the first type of RACH resource configuration information includes one of the following: Determine the first type of RACH resource configuration information based on the first configuration parameter included in the first type of RACH resource configuration information Preamble information of RO; Based on the first configuration parameter included in the first type of RACH resource configuration information and the second type of RACH resource configuration information, the Preamble information of the RO in the first type of RACH resource configuration information is determined.

25. The method according to claim 23 or 24, characterized in that The second type of RACH resource configuration information includes third RACH resource configuration information of 4-step RA for second type terminals and / or fourth RACH resource configuration information of 2-step RA for second type terminals. The second type terminals are terminals that cannot recognize SBFD time-frequency configuration.

26. The method according to any one of claims 23 to 25, characterized in that The Preamble information includes at least one of the following: A first starting preamble index, where the first starting preamble index is a starting preamble index of a first type of shared RO in the first type of RACH configuration resource information, where the first type of shared RO is a shared RO including a first type of SBFD time unit; The first number of preambles is the number of preambles contained in the first type of shared RO associated with a synchronization signal block SSB; A second starting Preamble index, where the second starting Preamble index is a starting Preamble index of a second type of shared RO in the first type of RACH configuration resource information, where the second type of shared RO is a shared RO that does not include a first type of SBFD time unit; The second number of preambles is the number of preambles contained in the second type of shared RO associated with an SSB.

27. The method according to claim 23, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the random access opportunity RO in the first type of RACH configuration resource information includes: Based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH configuration resource information is determined.

28. The method according to claim 27, characterized in that The determining, based on the first type of random access channel RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the second starting preamble index and / or the number of second preambles based on the first configuration parameter included in the first type of RACH resource configuration information; The first configuration parameter is used to indicate the second starting preamble index and / or the second preamble quantity.

29. The method according to claim 27, characterized in that The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes one of the following: Determine the second starting preamble index and the second preamble quantity based on the first type RACH resource configuration information and / or the second type RACH resource configuration information; Determine the second starting Preamble index based on the first type RACH resource configuration information and / or the second type RACH resource configuration information, and determine the second starting Preamble index based on the first configuration parameter included in the first type RACH resource configuration information. Number of preambles.

30. The method according to claim 29, wherein The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the Preamble information of the second type of shared RO in the first type of RACH resource configuration information based on the type of shared RO, the first condition, and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information; The first condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the second type ROs actually used by the two RACH resources.

31. The method according to any one of claims 27 to 30, characterized in that The method further comprises at least one of the following: Determine the first starting preamble index as the second starting preamble index; Determine the first preamble quantity as the second preamble quantity.

32. The method according to claim 27, wherein The determining, based on the first type of random access channel RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the first starting preamble index and / or the first preamble quantity based on a first configuration parameter included in the first type RACH resource configuration information; The first configuration parameter is used to indicate the first starting preamble index and / or the first preamble quantity.

33. The method according to claim 27, wherein The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes one of the following: Determine the first starting preamble index and the first preamble quantity based on the first type of RACH resource configuration information and / or the second type of RACH resource configuration information; The first starting preamble index is determined based on the first-type RACH resource configuration information and / or the second-type RACH resource configuration information, and the first preamble quantity is determined based on a first configuration parameter included in the first-type RACH resource configuration information.

34. The method according to claim 27, wherein The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine the Preamble information of the first type of shared RO in the first type of RACH resource configuration information based on the second condition and the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information; The second condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the first type ROs actually used by the two RACH resources.

35. The method according to claim 27, wherein The determining, based on the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the Preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information includes: Determine, based on the first condition, the second condition, the first type of random access channel RACH resource configuration information and / or the second type of RACH resource configuration information, the preamble information of the first type of shared RO and / or the second type of shared RO in the first type of RACH resource configuration information; The first condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The second type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the second type ROs actually used by the two RACH resources; The second condition includes: Two RACH resources are configured for the terminal, and any one of the two RACH resources is a resource configured by the first-type RACH resource configuration information or a resource configured by the second-type RACH resource configuration information; The first type ROs of the two RACH resources are located at the same time domain and frequency domain positions; There is an intersection between the first type ROs actually used by the two RACH resources.

36. The method according to any one of claims 23 to 35, characterized in that The first type of RACH resource configuration information is transmitted after the second type of RACH resource configuration information.

37. The method according to claim 36, wherein The first type of RACH resource configuration information is cell-specific configuration information or terminal-specific configuration information.

38. The method according to any one of claims 23 to 35, characterized in that The first type RACH resource configuration information is configured with an RO actually used in the first type shared RO and / or the second type shared RO.

39. The method according to any one of claims 23 to 35, characterized in that The number of Preambles contained in an SSB-associated RO in the first type shared RO and the second type shared RO configured with the first type RACH resource configuration information is the same or different.

40. The method according to any one of claims 23 to 35, characterized in that The RA is contention-based random access (CBRA).

41. The method according to any one of claims 23 to 35, characterized in that The number of preambles included in the RO associated with an SSB corresponds to the contention-based preamble.

42. The method according to any one of claims 23 to 35, characterized in that The first type of SBFD time unit is one of the following: The time unit is configured as a downlink (DL) time unit by the time division duplex (TDD) uplink and downlink common configuration (TDD-UL-DL-ConfigCommon) and is also configured as a SBFD time unit. The time unit is configured by TDD-UL-DL-ConfigCommon as a DL time unit or a flexible time unit and is configured as a SBFD time unit.

43. The method according to any one of claims 23 to 36, characterized in that The second type of RACH resource configuration information is not configured in the additional RACH configuration AdditionalRACH-Config; the first type of RACH resource configuration information is not configured in AdditionalRACH-Config; the first type of RACH resource configuration information is configured in AdditionalRACH-Config; the first RACH resource configuration information is configured in AdditionalRACH-Config and the second RACH resource configuration information is not configured in AdditionalRACH-Config; the first RACH resource configuration information is not configured in AdditionalRACH-Config and the second RACH resource configuration information is configured in AdditionalRACH-Config.

44. The method according to any one of claims 23 to 43, characterized in that The method further comprises: Sending first information to the terminal; The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information.

45. A communication method, characterized in that: The method is performed by a communication system, and includes: The network device sends first information to the terminal; The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

46. ​​A terminal, characterized in that The terminal includes: The transceiver module is configured as follows: receiving first information sent by a network device; The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

47. A network device, characterized in that The network equipment includes: The transceiver module is configured as follows: Sending first information to the terminal; The first information includes the first-type RACH resource configuration information and / or the second-type RACH resource configuration information; the first-type random access channel RACH resource configuration information and / or the second-type RACH resource configuration information are used to determine the preamble information of the random access opportunity RO in the first-type RACH configuration resource information; the first-type RACH resource configuration information includes first RACH resource configuration information for 4-step random access RA for a first-type terminal and / or second RACH resource configuration information for 2-step RA for a first-type terminal, and the first-type terminal is a terminal that can identify sub-band full-duplex SBFD time-frequency configuration.

48. A communication system, characterized in that The communication system includes a terminal and a network device; the terminal is configured to implement the communication method according to any one of claims 1 to 22, and the network device is configured to implement the communication method according to any one of claims 23 to 44.

49. A terminal, characterized in that: The terminal includes: one or more processors; The terminal is configured to execute the communication method according to any one of claims 1 to 22.

50. A network device, wherein: The network equipment includes: one or more processors; The network device is used to execute the communication method according to any one of claims 23 to 44.

51. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on the communication device, the communication device executes the communication method according to any one of claims 1 to 22 and / or claims 23 to 44.

Images