Random access method and apparatus, and communication system

Abstract

Embodiments of the present application provide a random access method and apparatus, and a communication system. The method comprises: a terminal device receives information used for configuring a first time domain resource and / or a second time domain resource, wherein the second time domain resource includes a second time domain resource configured to be downlink and / or a second time domain resource configured to be flexible, and the first time domain resource is different from the second time domain resource; and the terminal device uses a random access occasion (RO) overlapping the second time domain resource configured to be downlink or an RO overlapping the second time domain resource, to send a preamble.

Description

Random access methods, devices and communication systems Technical Field

[0001] This application relates to the field of communication technology. Background Technology

[0002] Random access procedures include contention-based random access (CBRA) and contention-free random access (CFRA). In contention-based random access, the terminal device (e.g., UE) selects preamble and PRACH resources from available preamble and PRACH resources configured by the network device (e.g., base station) for random access. In contention-free random access, the terminal device (e.g., UE) uses specific preamble and PRACH resources configured by the network device (e.g., base station) for random access.

[0003] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention

[0004] For different time-domain resources, the appropriate beam, corresponding uplink and downlink channel states, and power control parameters may differ due to variations in antenna configuration and channel conditions (such as interference). Furthermore, the frequency domain resources available for uplink may also differ across different time-domain resources.

[0005] For example, in traditional technologies, uplink transmission can only occur during uplink time slots in Time Division Duplex (TDD) bands. When limited or few uplink time slots are allocated, problems arise such as small uplink coverage, limited capacity, and high latency. To improve uplink capacity and coverage, and reduce uplink latency, network devices in TDD bands can operate in full-duplex mode at certain time points. For instance, at these time points, the network device simultaneously receives and transmits on different frequency domain resources within the corresponding carrier in the TDD band. This operating mode is, for example, called Subband Non-overlapping Full Duplex (SBFD), but is not limited to this. Under this operating mode, the aforementioned issues may arise such as differences in the beam, uplink and downlink channel states, power control parameters, and available frequency domain resources for uplink corresponding to different time domain resources.

[0006] For example, in order to improve network capacity, multiple antennas may be deployed in the same cell, and different antennas transmit in a time-division manner. Under this working mode, there may also be different issues such as the beam, uplink and downlink channel states, power control parameters, and frequency domain resources available for uplink corresponding to different time domain resources.

[0007] However, there is currently no solution for supporting random access when the aforementioned different time-domain resources exist.

[0008] To address at least one of the above-mentioned problems, embodiments of this application provide a random access method, apparatus, and communication system.

[0009] According to one aspect of the embodiments of this application, a random access method is provided, including:

[0010] The terminal device receives information for configuring a first time domain resource and / or a second time domain resource, wherein the second time domain resource includes a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, and the first time domain resource is different from the second time domain resource;

[0011] The terminal device uses a random access opportunity (RO) that overlaps with a second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to send a preamble.

[0012] According to another aspect of the embodiments of this application, a random access device is provided, comprising:

[0013] A receiver receives information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource;

[0014] A transmitter that uses a random access opportunity (RO) that overlaps with a second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to transmit a preamble.

[0015] According to another aspect of the embodiments of this application, a random access method is provided, including:

[0016] The network device sends information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource;

[0017] The network device uses a random access opportunity (RO) that overlaps with a second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to receive a preamble.

[0018] According to another aspect of the embodiments of this application, a random access device is provided, comprising:

[0019] A transmitter that transmits information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource;

[0020] The receiver uses a random access opportunity (RO) that overlaps with a second time-domain resource configured for downlink or a RO receive preamble that overlaps with the second time-domain resource.

[0021] According to another aspect of the embodiments of this application, a communication system is provided, including:

[0022] A network device that transmits information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource; and receives a preamble;

[0023] A terminal device receives the information for configuring a first time domain resource and / or a second time domain resource; and transmits the preamble using a random access opportunity (RO) that overlaps with the second time domain resource configured for downlink or an RO that overlaps with the second time domain resource.

[0024] One of the beneficial effects of the embodiments of this application includes: in the presence of different time-domain resources such as possible corresponding to different beams, channel states, frequency domain resources for uplink, etc., the terminal device can use a random access opportunity (RO) that overlaps with the second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to send a preamble, which can support random access in the presence of the above-mentioned different time-domain resources, increase the coverage and capacity of random access and reduce latency.

[0025] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0026] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with or replacing features in other embodiments.

[0027] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0028] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0029] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without creative effort. In the drawings:

[0030] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0031] Figure 2 is a schematic diagram of a random access method according to an embodiment of this application;

[0032] Figure 3 is an example diagram of time-domain resources according to an embodiment of this application;

[0033] Figure 4 is an example diagram of uplink available PRB according to an embodiment of this application;

[0034] Figure 5 is an example diagram of downlink available PRB according to an embodiment of this application;

[0035] Figure 6 is a schematic diagram of a random access method according to an embodiment of this application;

[0036] Figure 7 is a schematic diagram of a random access device according to an embodiment of this application;

[0037] Figure 8 is a schematic diagram of a random access device according to an embodiment of this application;

[0038] Figure 9 is a schematic diagram of a network device according to an embodiment of this application;

[0039] Figure 10 is a schematic diagram of a terminal device according to an embodiment of this application. Detailed Implementation

[0040] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0041] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0042] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly interpreted as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," the term "based on" should be understood as "at least partially based on…," and the term "related to…" should be understood as "at least partially related to…," unless the context explicitly indicates otherwise. In some embodiments, "according to," "based on," and "related to…" can be used interchangeably, but this application is not limited thereto.

[0043] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0044] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), 6G, etc., and / or other currently known or future communication protocols.

[0045] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transceiver node (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0046] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" can include some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0047] In the embodiments of this application, the term "User Equipment" (UE) refers to a device that accesses a communication network and receives network services through a network device, and can also be called "Terminal Equipment" (TE). Terminal equipment can be fixed or mobile, and can also be called a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, mobile terminal (MT), etc.

[0048] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0049] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0050] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0051] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.

[0052] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.

[0053] Additionally, uplink signals can include uplink data signals and / or uplink control signals and / or PRACH and / or SRS, etc., and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending / receiving uplink transmission on uplink resources can be understood as using that uplink resource to send / receive the uplink transmission. Downlink signals can include downlink data signals and / or downlink control signals and / or synchronization signals (SS, such as PSS / SSS) and / or broadcast channel (PBCH) and / or SSB (SS / PBCH block, including PSS, SSS, and PBCH and their DMRS) and / or CSI-RS, etc., and can also be referred to as downlink transmission (DL transmission), downlink information, or downlink channel. Sending / receiving downlink transmission on downlink resources can be understood as using that downlink resource to send / receive the downlink transmission.

[0054] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; RRC signaling may include, for example, RRC messages, such as broadcast / public RRC messages / signaling (e.g., Master Information Block (MIB), system information), dedicated RRC messages / signaling; or RRC information elements (RRC IE); or information fields (or information fields included in information fields) included in RRC messages or RRC information elements. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as MAC control elements (MAC CE). However, this application is not limited to these. The names of signaling (e.g., RRC messages, information elements IE, information fields, higher-layer parameters, etc.) used in the embodiments of this application are only examples and may be other names, which are not intended to limit the scope of this application. The '-rN' (e.g., -r17, etc.) in the higher-layer parameter names may be omitted (without causing ambiguity).

[0055] In the embodiments of this application, "multiple" refers to at least two, or two or more.

[0056] In the embodiments of this application, "predefined" refers to what is specified by the protocol or determined according to the rules specified by the protocol, and does not require additional configuration. "Configuration / instruction / providement" refers to what the network device directly or indirectly configures / instructs / provides through higher-layer signaling and / or physical layer signaling. Configuration / instruction can be achieved by introducing higher-layer parameters into the higher-layer signaling. Higher-layer parameters refer to information fields and / or information elements / information units / information cells (IE) / control elements (CE) in the higher-layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical downlink control channel or control information carried by the sequence, but is not limited to these.

[0057] In the embodiments of this application, "overlapping" includes complete / full overlap and / or partial overlap and / or at least partial overlap. "Located in" includes completely / full located in and / or partially located in and / or at least partially located in, and "located within" includes completely located within.

[0058] For ease of description, the following description uses a base station as an example of an access network device. In the following descriptions, "if…", "in the case of…", and "when…" are used interchangeably unless there is confusion. For resources in the frequency domain, "carrier" and "resource grid" are interchangeable; "subcarrier spacing configuration (μ)" and "subcarrier spacing (SCS) (Δf)" are interchangeable; "subcarrier spacing" and "numerology" are interchangeable; "resource block," "RB," and "PRB," "physical resource block," and "common resource block (CRB)" are interchangeable; "configuration / indication / providance / given" are interchangeable; "index" and "identifier (ID)" are interchangeable.

[0059] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0060] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0061] In this embodiment of the application, network device 101 and terminal devices 102 and 103 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0062] Terminal device 102 can send data to network device 101, for example, using authorized or unauthorized transmission methods. Network device 101 can receive data sent by one or more terminal devices 102 and provide feedback to terminal devices 102, such as ACK / NACK confirmation information. Based on the feedback information, terminal device 102 can confirm the end of the transmission process, or can initiate new data transmission, or can retransmit the data.

[0063] Network device 101 can send data to terminal device 102 and / or terminal device 103 using unicast, multicast, or broadcast. Terminal device 102 can receive data sent by one or more network devices (e.g., dual-connection or multi-connection) via a downlink or by terminal device 103 via a sidelink.

[0064] It is worth noting that Figure 1 shows that both terminal devices 102 and 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Both terminal devices 102 and 103 may be outside the coverage area of ​​network device 101, or one terminal device 102 may be within the coverage area of ​​network device 101 while the other terminal device 103 may be outside the coverage area of ​​network device 101.

[0065] The following describes some of the terms used in the embodiments of this application.

[0066] --Subcarrier spacing (SCS). The subcarrier spacing of a BWP is configurable, and the candidate subcarrier spacings are shown in Table 1 below. The BWP includes an integer number of PRBs using the SCS.

[0067] For uplink and downlink transmissions on a BWP, the SCS configured for a downlink BWP applies to downlink signals or channels in that DL BWP except for the SSB, and the SCS configured for an uplink BWP applies to uplink signals or channels in that UL BWP except for the PRACH.

[0068] Table 1

[0069] --PRACH preamble format (or PRACH format, or preamble format).

[0070] As shown in Table 2 below, the SCS of a PRACH is bound to its format. Therefore, if a format is configured, there is no need to specify the SCS of the PRACH separately.

[0071] Table 2

[0072] PRACH preamble formats for L RA =839 and Δf RA ∈{1.25,5}kHz.

[0073] As shown in Table 3 below, a format corresponds to multiple possible sequence lengths and SCS. Therefore, if a format is configured, its corresponding sequence length and SCS need to be indicated.

[0074] Table 3

[0075] Preamble formats for L RA ∈{139,571,1151}and Δf RA =15·2 μ kHz where μ∈{0,1,2,3,5,6}.

[0076] The above illustrations illustrate some terms related to random access. This application is not limited thereto, and the above content can be combined with the following embodiments, or can be part of the embodiments of this application. In the embodiments of this application, the terms "PRACH configuration" and "RACH configuration" or "RA configuration" can be interchanged, and the term "preamble" can be interchanged with "preamble sequence," "random access preamble," "random access preamble sequence," "PRACH preamble," "RACH preamble," etc.

[0077] Furthermore, the content within parentheses is explanatory, exemplary, or optional. For example, in some embodiments, the expressions or limitations within parentheses may be included, while in other embodiments, they may be omitted. " / " indicates "and / or," and this application is not limited thereto. Various embodiments of this application will be described below with reference to the accompanying drawings. These embodiments are merely exemplary and not intended to limit the scope of this application.

[0078] First aspect of the embodiments

[0079] This application provides a random access method, which will be described from the perspective of the terminal device.

[0080] Figure 2 is a schematic diagram of a random access method according to an embodiment of this application. As shown in Figure 2, the method includes:

[0081] 201. The terminal device receives information for configuring a first time-domain resource and / or a second time-domain resource (of the cell), the second time-domain resource including a second time-domain resource configured as downlink by (first uplink / downlink configuration) and / or a second time-domain resource configured as flexible by (first uplink / downlink configuration), the first time-domain resource being different from the second time-domain resource; and

[0082] 202, the terminal device uses a (valid) random access opportunity (RO) (associated with a downlink signal (e.g., SSB or CSI-RS)) that overlaps with the second time-domain resource configured for downlink or a (valid) RO (associated with a downlink signal (e.g., SSB or CSI-RS) that overlaps with the second time-domain resource to transmit a preamble.

[0083] It is worth noting that Figure 2 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 2 above.

[0084] In some embodiments, the terminal device may be an SBFD-aware device; however, this application is not limited thereto. For example, during the initial access procedure (from RRC_IDLE to RRC_Connected state, including CBRA) and / or the random access procedure (e.g., CBRA) and / or the RRCSetupComplete message and / or in the capability information, the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE).

[0085] For example, during random access, the terminal device is indicated to be an SBFD-aware device via the RO / PRACH and / or Msg3 used to send the preamble. For instance, some ROs (first ROs) are not limited to use by SBFD-aware UEs (other UEs can also use them), while some ROs (second ROs) are limited to use by SBFD-aware devices. Therefore, when a UE uses a second RO to send the preamble / PRACH, the base station knows that the UE is an SBFD-aware device (and consequently, the subsequent Msg3 and / or RRCSetupComplete message and / or capability information may include / not include information indicating that the UE is an SBFD-aware device). For example, (when the UE uses a first RO to send the preamble / PRACH), the Msg3 and / or RRCSetupComplete message and / or capability information include information indicating that the UE is an SBFD-aware device.

[0086] For example, an SBFD-aware UE has capabilities related to SBFD operation, including one or more of the following: being able to know the SBFD configuration, such as the configuration of the first time domain resources and / or the second time domain resources and / or the first frequency domain resources and / or the second frequency domain resources described below; being able to configure transmit and receive signals according to the SBFD; and being able to transmit uplink signals on (DL)SBFD symbols.

[0087] The following describes the first time domain resources and / or the second time domain resources.

[0088] In some embodiments, for a cell or carrier, in the second time domain resources, different frequency domain resources are respectively (only) used for (network device receiving) uplink (e.g., corresponding to the first frequency domain resources and / or the third frequency domain resources described below) and (only) used for (network device transmitting) downlink (e.g., corresponding to the second frequency domain resources and / or the fourth frequency domain resources described below). For example, the network device can simultaneously receive (uplink signals) in the frequency domain resources (only) used for uplink and transmit (downlink signals) in the frequency domain resources (only) used for downlink. The first time domain resources are outside the second time domain resources. For example, in the first time domain resources, different frequency domain resources are all used for uplink or all used for downlink. That is, the frequency domain resources are not divided into frequency domain resources (only) used for uplink and (only) used for downlink, and the network device does not receive and transmit at the same time.

[0089] In some embodiments, the time-domain resource type includes a first time-domain resource and a second time-domain resource. The first and second time-domain resources also include a first symbol and a second symbol, respectively; that is, the symbol type includes a first symbol and a second symbol. For example, SBFD symbol (second symbol) and non-SBFD symbol (first symbol). However, this application is not limited to this and can also be applied to other scenarios. For example, the first and second time-domain resources can respectively refer to different time-domain resources defined in other ways. For convenience, "SBFD symbol" and "non-SBFD symbol" will be used below for description.

[0090] In some embodiments, SBFD symbols and / or non-SBFD symbols are configured for different cells / carriers.

[0091] In some embodiments, information for configuring SBFD symbols and / or non-SBFD symbols is provided by higher-level signaling.

[0092] In some embodiments, information for configuring the first time-domain resource and / or the second time-domain resource may (optionally) be present in system information (e.g., SIB1) (broadcast or transmitted via dedicated signaling), and / or in public service cell configuration, and / or in serving cell configuration, and / or in information elements for configuring random access resources.

[0093] In some embodiments, the information for configuring the first time domain resources and / or the second time domain resources and / or the information for configuring the first frequency domain resources and / or the second frequency domain resources in the system message are applied to the cell that sent the system message or the system message is for / corresponding to the cell, that is, it configures the first time domain resources and / or the second time domain resources of the cell.

[0094] In some embodiments, the information for configuring the first time domain resources and / or the second time domain resources and / or the information for configuring the first frequency domain resources and / or the second frequency domain resources in the (public) serving cell configuration are applied to the (public) serving cell configuration for / corresponding cell, that is, the configuration is of the first time domain resources and / or the second time domain resources of that cell.

[0095] In some embodiments, the information for configuring the first time-domain resources and / or the second time-domain resources and / or the information for configuring the first frequency-domain resources and / or the second frequency-domain resources in the information element for configuring random access resources are applied to the random access resources configured by the information element, or the information element (configured random access resources) is for / corresponding to a specific cell. That is, it configures the first time-domain resources and / or the second time-domain resources of that cell.

[0096] In some embodiments, the information elements for configuring random access resources include: an information element for configuring random access resources for the early UL synchronization procedure (EarlyUL-SyncConfig), and / or an information element for configuring (dedicated) random access resources for beam failure recovery (BeamFailureRecoveryConfig), and / or an information element for configuring (dedicated) random access resources for (Msg1-based) system information requests (SI-RequestConfig or SI-RequestConfigRepetition), and / or the information elements for configuring random access resources include: an information element for configuring (dedicated) random access resources for additional physical cell identifiers (RACH-ConfigTwoTA), and / or the information elements for configuring random access resources include: an information element for configuring (dedicated) random access resources for handover and / or resynchronization (RACH-ConfigDedicated).

[0097] For example, higher-layer parameters for configuring SBFD symbols may optionally exist in SIB1 and / or SIB ServingCellConfigCommonSIB IE and / or ServingCellConfigCommon IE (in which TDD-UL-DL-ConfigCommon IE is a TDD-UL-DL-Pattern IE) and / or, higher-layer parameters for configuring SBFD symbols may optionally exist in ServingCellConfig, and / or, higher-layer parameters for configuring SBFD symbols may optionally exist in ServingCellConfig IE (in which TDD-UL-DL-ConfigCommon IE is a TDD-UL-DL-Pattern IE) for configuring random access resource information elements (e.g., EarlyUL-SyncConfig).

[0098] In some embodiments, the information in the information element for configuring random access resources (e.g., EarlyUL-SyncConfig) for configuring the first time domain resources and / or the second time domain resources is configured based on the reference subcarrier spacing (SCS) of the first uplink / downlink configuration included in the information element.

[0099] In some embodiments, the terminal device determines the first time-domain resource and / or the second time-domain resource configured by the information element for configuring random access resources (e.g., EarlyUL-SyncConfig) based on the reference subcarrier spacing (SCS) of the first uplink / downlink configuration included in the information element for configuring random access resources.

[0100] In some embodiments, the cell / carrier (corresponding to the information element for configuring random access resources in system information (e.g., SIB1) / public service cell configuration / serving cell configuration / information element for configuring random access resources) can be configured with one or more (e.g., two) TDD uplink / downlink patterns in (the corresponding TDD-UL-DL-ConfigCommon in system information (e.g., SIB1) / public service cell configuration / serving cell configuration / information element for configuring random access resources). When multiple patterns are configured, different patterns may or may not have corresponding SBFD symbols, and different patterns are independently configured with corresponding SBFD symbols.

[0101] For example, for each pattern with SBFD symbols, the configured SBFD symbols are continuous within the corresponding period of the pattern. The high-level parameters for configuring SBFD symbols mentioned above include, for example, one or more parameters for configuring SBFD symbols in that period, such as: start slot index, start symbol index (in the start slot), end slot index, and end symbol index (in the end slot).

[0102] For example, the start and end slots are the first and last slots containing SBFD symbols, respectively. The start and end symbols are the first and last SBFD symbols in the start slot and the last SBFD symbol in the end slot, respectively. All symbols from the start symbol of the start slot to the end symbol of the end slot are SBFD symbols. The remaining symbols include non-SBFD symbols and / or interval symbols, or, alternatively, non-SBFD symbols. The slot index is the number of the slots included in the period, which increments by 1, for example, starting from 0 or 1. For example, when the start slot index is 0, the start slot is the first slot in the period; when the start slot index is 1, the start slot is the second slot in the period, and so on. Similarly, the symbol index is the number of the symbols within a slot. The aforementioned slots / symbols use the SCS configured in the reference subcarrier spacing field of the Common TDD Uplink / Downlink Configuration (TDD-UL-DL-Config Common) IE.

[0103] For example, each / different pattern is configured with a period independently, for example, by the corresponding ((TDD-UL-DL-Pattern)IE)dl-UL-TransmissionPeriodicity. When only one pattern is configured, the period of the SBFD symbol is the same as the period corresponding to that pattern; when multiple patterns (e.g., two) are configured, the period of the SBFD symbol is the same as the sum of the periods corresponding to all patterns.

[0104] In some embodiments, a downlink symbol is, for example, a symbol indicated as downlink by the first uplink / downlink configuration, an uplink symbol is, for example, a symbol indicated as uplink by the first uplink / downlink configuration, and a flexible symbol is, for example, a symbol that is neither indicated as downlink nor as uplink by the first uplink / downlink configuration, or a symbol indicated as flexible by the configuration. The first uplink / downlink configuration is used to provide cell-specific uplink / downlink configurations, such as tdd-UL-DL-ConfigurationCommon, or the common TDD uplink / downlink configuration (TDD-UL-DL-ConfigCommon)IE or (TDD-UL-DL-Pattern)IE, but is not limited thereto.

[0105] In some embodiments, the UE determines the DL / UL / Flexible symbol corresponding to the BWP based on the DL / UL / Flexible symbol configured according to the aforementioned reference Subcarrier Spacing (and assuming NCP). For example, it determines the DL / UL / Flexible symbol corresponding to the BWP based on the reference Subcarrier Spacing and the SCS and / or CP type (NCP or ECP) ​​of the BWP.

[0106] In some embodiments, the DL / UL / Flexible symbol refers to the DL / UL / Flexible symbol configured based on the reference SubcarrierSpacing or the DL / UL / Flexible symbol corresponding to the BWP.

[0107] In some embodiments, the UE determines the SBFD / non-SBFD symbol corresponding to the BWP based on the SBFD / non-SBFD symbol configured based on the aforementioned reference Subcarrier Spacing (and assuming NCP). For example, it determines the SBFD / non-SBFD symbol corresponding to the BWP based on the reference Subcarrier Spacing and the SCS and / or CP type (NCP or ECP) ​​of the BWP.

[0108] In some embodiments, SBFD / non-SBFD symbols refer to SBFD / non-SBFD symbols configured based on reference SubcarrierSpacing or SBFD / non-SBFD symbols corresponding to BWP.

[0109] In some embodiments, the UE does not expect the CP type of the BWP to be ECP.

[0110] In some embodiments, the UE does not expect the SBFD symbols configured (as described above by the higher-layer parameters) to overlap with the uplink symbols, or if the SBFD symbols configured (as described above by the higher-layer parameters) overlap with the uplink symbols, the UE considers the SBFD symbols overlapping with the uplink symbols to be non-SBFD symbols.

[0111] In some embodiments, the SBFD symbol overlaps with the downlink symbol or the flexible symbol, or in other words, the SBFD symbol is configured within the scope of the downlink symbol and / or the flexible symbol.

[0112] In some embodiments, SBFD symbols include DL SBFD symbols and / or Flexible SBFD symbols, and non-SBFD symbols include Full-DL symbols and / or Full-Flexible symbols and / or Full-UL symbols (or UL symbols). Other representations may also be used for these symbols, and are not limited thereto.

[0113] Figure 3 is an example diagram of time-domain resources according to an embodiment of this application. As shown in Figure 3, a period (e.g., the period corresponding to a pattern) may include multiple different symbols. In this context, the SBFD symbol falls within the scope of downlink symbols and flexible symbols. An SBFD symbol overlapping with a DL symbol, or an SBFD symbol indicated as downlink by the first uplink / downlink configuration, is represented as a DL SBFD symbol. An SBFD symbol overlapping with a flexible symbol, or an SBFD symbol indicated as flexible by the first uplink / downlink configuration (i.e., an SBFD symbol not indicated as downlink (or uplink) by the first uplink / downlink configuration), is represented as a Flexible SBFD symbol. A downlink symbol not overlapping with an SBFD symbol, or a non-SBFD symbol indicated as downlink by the first uplink / downlink configuration, is represented as a Full-DL symbol. A flexible symbol not overlapping with an SBFD symbol, or a non-SBFD symbol indicated as flexible by the first uplink / downlink configuration, is represented as a Full-Flexible symbol. A UL symbol not overlapping with an SBFD symbol, or a (non-SBFD) symbol indicated as uplink by the first uplink / downlink configuration, is represented as a Full-UL symbol (assuming that a UL symbol cannot be used as an SBFD symbol, a Full-UL symbol is equivalent to a UL symbol). Figure 3 exemplarily illustrates the time-domain resources of an embodiment of this application, but is not limited thereto.

[0114] The frequency domain resources involved in the embodiments of this application are illustrated below.

[0115] The first frequency domain resources include the uplink subband (UL subband), and the second frequency domain resources include the downlink subband (DL subband). Other names may also be used, and are not limited to these. For convenience, the following descriptions will use UL subband and DL subband.

[0116] In some embodiments, the UE receives information for configuring the UL subband and DL subband. For example, the uplink subband and downlink subband each include an integer number of PRBs, and the information for configuring the UL subband and DL subband includes information indicating the corresponding starting PRB and bandwidth / size (including the number of PRBs).

[0117] In some embodiments, information for configuring the UL subband and DL subband is provided by higher-level signaling.

[0118] In some embodiments, the system information and / or the serving cell configuration and / or the information element for configuring random access resources further include information for configuring a first frequency domain resource and / or a second frequency domain resource; wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink.

[0119] For example, higher-layer parameters used to configure the DL subband may optionally exist in SIB1 (the SIB ServingCellConfigCommonSIB IE, the SIB DownlinkConfigCommonSIB IE, the SIB DownlinkFrequencyInfoDL-SIB IE, and the SCS-SpecificCarrier IE), and the inclusion relationship of the above parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > DownlinkConfigCommonSIB > FrequencyInfoDL-SIB > SCS-SpecificCarrier; and / or,

[0120] The higher-layer parameters used to configure the DL subband may optionally exist in the ServingCellConfigCommon IE (which contains the DownlinkConfigCommon IE, which contains the DownlinkFrequencyInfoDL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > DownlinkConfigCommon > FrequencyInfoDL > SCS-SpecificCarrier, and / or, optionally, in the ServingCellConfig. That is, the higher-layer parameters used to configure the DL subband may optionally exist in one or more of the above parameters.

[0121] For example, the higher-layer parameters used to configure the UL subband may optionally exist in SIB1 (the SIB ServingCellConfigCommonSIB IE, the SIB UplinkConfigCommonSIB IE, the SIB UplinkFrequencyInfoUL-SIB IE, and the SCS-SpecificCarrier IE). For instance, the inclusion relationship of these parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > UplinkConfigCommonSIB > FrequencyInfoUL-SIB > SCS-SpecificCarrier, and / or...

[0122] The higher-layer parameters used to configure the UL subband may optionally exist in the ServingCellConfigCommon IE (which contains the UplinkConfigCommon IE, which contains the UplinkFrequencyInfoUL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > UplinkConfigCommon > FrequencyInfoUL > SCS-SpecificCarrier, and / or, optionally, exist in the ServingCellConfig. That is, the higher-layer parameters used to configure the UL subband may optionally exist in one or more of the above parameters, and / or,

[0123] The higher-layer parameters used to configure the UL subband may optionally exist in the uplink frequency domain information (FrequencyInfoUL)IE (SCS-SpecificCarrier)IE) used to configure random access resource information elements (e.g., EarlyUL-SyncConfig) (SCS-SpecificCarrier)IE). For example, the inclusion relationship of the above parameters can be expressed as: EarlyUL-SyncConfig > FrequencyInfoUL > SCS-SpecificCarrier.

[0124] In some embodiments, the high-level parameters for configuring the UL subband and the high-level parameters for configuring the DL subband include one or more parameters for providing the RIV (resource indication value) and / or (the SCS corresponding to the UL / DL subband), that is, indicating the starting RB (RB) of the UL subband and the DL subband respectively based on the RIV. start ) and bandwidth (including the number of RBs, L RBs )).

[0125] For example, resource indicator values ​​can be defined as shown in Table 4 below.

[0126] Table 4

[0127] For example, for DL / UL subband: assuming the following in Table 4 In addition, the first PRB (RB) start The minimum value (0 or 1) corresponding to the PRB can be determined as follows: The first PRB is the PRB determined by the corresponding subcarrierSpacing and offsetToCarrier (configured in the corresponding SCS-Specific Carrier in FrequencyInfoDL (for DL ​​subband) / FrequencyInfoUL (for UL subband) / FrequencyInfoUL-SIB (for UL subband) / FrequencyInfoDL-SIB (for DL ​​subband)) within ServingCellConfigCommon / ServingCellConfigCommonSIB / EarlyUL-SyncConfig.

[0128] In some embodiments, within a cell, the scs-SpecificCarrierList of UL (in FrequencyInfoUL / FrequencyInfoUL-SIB) and DL (in FrequencyInfoDL / FrequencyInfoDL-SIB) may each include one or more SCS-SpecificCarrier IEs, and each SCS-SpecificCarrier IE corresponds to / includes one SCS configuration (subcarrierSpacing). That is, the scs-SpecificCarrierList of UL and DL may each include one or more SCS configurations.

[0129] For example, each SCS configuration in the UL scs-SpecificCarrierList is configured with a UL subband, or each corresponds to a UL subband, for example, each corresponds to an independent high-level parameter mentioned above for configuring the UL subband. Each SCS configuration in the DL scs-SpecificCarrierList is configured with one or more (e.g., two) DL subbands, or each corresponds to one or more DL subbands, for example, each corresponds to an independent high-level parameter mentioned above for configuring the DL subband. If an SCS configuration is configured with multiple DL subbands, the corresponding high-level parameter for configuring the DL subband includes multiple RIVs mentioned above.

[0130] In some embodiments, the UE does not expect the DL subband and UL subband (in the frequency domain) to overlap (for the same SCS (configuration), or the UE expects the DL subband and UL subband (in the frequency domain) not to overlap (for the same SCS (configuration)).

[0131] In some embodiments, in the second time domain resource, the first frequency domain resource and / or the third frequency domain resource (UL usable PRBs for the active UL BWP) are used for uplink and the second frequency domain resource and / or the fourth frequency domain resource (DL usable PRBs for the active DL BWP) are used for downlink, and the first time domain resource is outside the second time domain resource. For convenience, UL usable PRBs and DL usable PRBs will be used in the following description.

[0132] In some embodiments, for a UL BWP, its UL usable PRBs include / are determined as (in the SBFD symbol / corresponding to the SBFD symbol,) the intersection of (PRBs in the UL subband) and (PRBs in the uplink BWP) with (the SCS configured for the uplink BWP, or, corresponding to the SCS of the UL BWP), or, the PRBs in the intersection are referred to as UL usable PRBs.

[0133] For example, for a UL BWP, the intersection is determined based on the uplink subband corresponding to the SCS of that UL BWP. For instance, if the SCS of a UL BWP is 15kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz. If the SCS of a UL BWP is 30kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz.

[0134] In some embodiments, the third frequency domain resources (UL usable PRBs) of the (UL)BWP configured for an information element (e.g., BWP IE in EarlyUL-SyncConfig) for configuring random access resources are the intersection of the first frequency domain resources (UL subband) configured by the information element and the (UL)BWP.

[0135] In some embodiments, the information element for configuring random access resources (e.g., EarlyUL-SyncConfig) further includes information for configuring third frequency domain resources (UL usable PRBs) of the (UL)BWP configured for the information element (and excludes information for configuring the UL subband). For example, the third frequency domain resources (UL usable PRBs) of the (UL)BWP configured for the information element for configuring random access resources (e.g., BWP IE in EarlyUL-SyncConfig) are the third frequency domain resources (UL usable PRBs) configured by the information element.

[0136] In some embodiments, the UE does not expect the UL usable PRBs of the activated UL BWP and the DL usable PRBs of the activated DL BWP to overlap or their frequency domain spacing to be less than or greater than a specific value; or, the UE expects the UL usable PRBs of the activated UL BWP and the DL usable PRBs of the activated DL BWP to not overlap or their frequency domain spacing to be not less than or greater than a specific value.

[0137] In some embodiments, for a UL BWP, if the PRBs in the UL subband (configured for the SCS of the UL BWP, or corresponding to the SCS of the UL BWP) do not intersect with the PRBs in the UL BWP, or if the intersection of the PRBs in the UL subband (configured for the SCS of the UL BWP, or corresponding to the SCS of the UL BWP) and the PRBs in the UL BWP includes 0 PRBs, then the UL BWP does not have UL usable PRBs; otherwise, if there is an intersection or the intersection includes at least 1 PRB or more than 0 PRBs, the UL BWP has UL usable PRBs.

[0138] Figure 4 is an example diagram of uplink usable PRBs according to an embodiment of this application. As shown in Figure 4, the UL BWP and UL subband overlap, and the UL usable PRBs are the intersection between them. The UL subband, for example, represents the uplink subband corresponding to the SCS of the UL BWP, but this application is not limited to this.

[0139] In some embodiments, for a DL BWP, its DL usable PRBs include / are determined as (in SBFD symbols / corresponding to SBFD symbols,) the intersection of (PRBs in the DL subband) and (PRBs in the downlink BWP) with (the SCS configured for the downlink BWP, or, corresponding to the SCS of the DL BWP), or, the PRBs in the intersection are referred to as DL usable PRBs.

[0140] For example, for a DL BWP, the intersection is determined based on the downlink subband corresponding to the SCS of that DL BWP. For instance, if the SCS of a DL BWP is 15kHz, then its corresponding DL can be represented by the PRB as the intersection of the DL BWP with the corresponding downlink subband of SCS = 15kHz. If the SCS of a DL BWP is 30kHz, then its corresponding DL can be represented by the PRB as the intersection of the DL BWP with the corresponding uplink subband of SCS = 15kHz.

[0141] Figure 5 is an example diagram of downlink usable PRBs according to an embodiment of this application. As shown in Figure 5, DL BWP and DL subband overlap, and DL usable PRBs are the intersection of the two. The DL subband, for example, represents the downlink subband corresponding to the SCS of the DL BWP, but this application is not limited thereto.

[0142] The above provides an illustrative description of time and frequency resources. The following provides a further illustrative description of the embodiments of this application.

[0143] In some embodiments, the terminal device receives first information, which is used to indicate whether (whether) random access preamble transmission is permitted using a RO that overlaps with a second time-domain resource configured for downlink, and / or to indicate whether a first specific RACH configuration (RACH configuration Option 1) for a specific SBFD random access operation is enabled or not from the network side; and / or,

[0144] The terminal device receives second information, which is used to indicate whether (or) sending a random access preamble using a RO in the first time domain resource is not allowed, and / or to indicate whether (or) sending a random access preamble using a RO overlapping with the second time domain resource is allowed, and / or to indicate whether sending a random access preamble using a RO in the second time domain resource is allowed, and / or to indicate whether a second specific RACH configuration (RACH configuration Option 2) for a specific random access operation (SBFD random access operation) is enabled (indicate whether RACH configuration Option 1 for SBFD random access operation is enabled or not from the network side); and / or,

[0145] The terminal device receives third information, which indicates whether (whether) it is permissible to send a random access preamble using ROs across the second time domain resource and the first time domain resource, and / or, the third information indicates whether (whether) it is permissible to send a random access preamble using ROs that begin in the second time domain resource and end in the first time domain resource; and / or,

[0146] The terminal device receives fourth information, which instructs (the terminal device) to use ROs in the first time domain resources to send a random access preamble and / or use ROs that overlap with the second time domain resources configured for downlink to send a random access preamble and / or use ROs that overlap with the second time domain resources to send a random access preamble and / or not use ROs in the first time domain resources to send a random access preamble.

[0147] In some embodiments, the first information includes a bit. One value of the bit (e.g., 1) indicates that a random access preamble is allowed to be transmitted using a RO that overlaps with a second time-domain resource configured for downlink, and / or indicates that a first specific RACH configuration (RACH configuration Option 1) for a specific SBFD random access operation is enabled; another value of the bit (e.g., 0) indicates that a random access preamble is not allowed to be transmitted using a RO that overlaps with a second time-domain resource configured for downlink, and / or indicates that the first specific RACH configuration (RACH configuration Option 1) for a specific SBFD random access operation is disabled.

[0148] In some embodiments, the second information includes a bit. One value of the bit (e.g., 1) indicates that the random access preamble is not allowed to be transmitted using ROs in the first time domain resource, and / or indicates that the random access preamble is allowed to be transmitted using ROs that overlap with the second time domain resource, and / or indicates that a second specific RACH configuration (RACH configuration Option 2) for a specific SBFD random access operation is enabled; another value of the bit (e.g., 0) indicates that the random access preamble is allowed to be transmitted using ROs in the first time domain resource, and / or indicates that the random access preamble is not allowed to be transmitted using ROs that overlap with the second time domain resource, and / or indicates that a second specific RACH configuration (RACH configuration Option 2) for a specific SBFD random access operation is disabled.

[0149] In some embodiments, the third information includes a bit. One value of the bit (e.g., 1) indicates that a random access preamble can be sent using ROs across the second time domain resource and the first time domain resource, and / or indicates that a random access preamble can be sent using ROs that begin in the second time domain resource and end in the first time domain resource; another value of the bit (e.g., 0) indicates that a random access preamble cannot be sent using ROs across the second time domain resource and the first time domain resource, and / or indicates that a random access preamble cannot be sent using ROs that begin in the second time domain resource and end in the first time domain resource.

[0150] In some embodiments, the fourth information includes one bit or two bits.

[0151] In some embodiments, at least two of the first to fourth information are provided by the same information field (including one or two bits).

[0152] In some embodiments, at least two of the first to fourth information are provided by different information fields.

[0153] In some embodiments, the first information is applied to (contention-based and / or non-contention-based) four-step random access (4-step RACH) and two-step random access (2-step RACH).

[0154] In some embodiments, the first information is applied to (contention-based and / or non-contention-based) four-step random access (4-step RACH) but not to (contention-based and / or non-contention-based) two-step random access (2-step RACH).

[0155] In some embodiments, the first information and / or the second information and / or the third information and / or the fourth information (optionally) exist in system messages, and / or in (public) serving cell configurations, and / or in information elements for configuring random access resources.

[0156] In some embodiments, the first information and / or the second information and / or the third information may not exist simultaneously in the system message, and / or may not exist simultaneously in the (public) serving cell configuration, and / or may not exist simultaneously in the information element for configuring random access resources.

[0157] In some embodiments, when the first information exists in and / or the second information does not exist in the system message and / or the serving cell configuration and / or the information element for configuring random access resources, the third information does not exist in the system message and / or the serving cell configuration and / or the information element for configuring random access resources in the system message (where the second information does not exist).

[0158] In some embodiments, the first and / or second and / or third and / or fourth information in the (broadcast) system message:

[0159] Random access resources applied (in the cell sending the system message or in the cell to which the system message is addressed) for initial access and / or connection reconstruction and / or connection recovery and / or beam failure recovery and / or Request for Other SI and / or Scheduling Request (SR) failure and / or uplink desynchronization and / or Small Data Transmission (SDT) and / or uplink data arrival without PUCCH resources for SR and / or additional physical cell identifier (PCI), and / or

[0160] The public (cell-specific) random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the (dedicated) random access resources for beam failure recovery of the cell (BeamFailureRecoveryConfig configuration), and / or the (dedicated) random access resources for system information requests (Msg1-based) of the cell (SI-RequestConfig or SI-RequestConfigRepetition configuration), and / or the (dedicated) random access resources for additional physical cell identifiers (additional PCI) of the cell (RACH-ConfigTwoTA configuration), and / or,

[0161] Random access resources shall not be used for (dedicated) random access resources for early uplink synchronization and / or for handover and / or resynchronization and / or for beam failure recovery (of the cell) and / or for system information requests (of the cell / in the cell) and / or for additional physical cell identifiers (of the cell).

[0162] In some embodiments, the first and / or second and / or third and / or fourth information in the (public) serving cell configuration:

[0163] Random access resources applied (in the (public) serving cell configuration for) initial access and / or connection re-establishment and / or connection recovery and / or beam failure recovery and / or Request for Other SI and / or SR failure and / or uplink desynchronization and / or SDT and / or uplink data arrival without PUCCH resources for SR and / or additional physical cell identifier (PCI) and / or handover (to the cell) and / or resynchronization (to the cell), and / or,

[0164] The public (cell-specific) random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the (dedicated) random access resources for beam failure recovery of the cell (BeamFailureRecoveryConfig configuration), and / or the (dedicated) random access resources for system information requests (Msg1-based) of the cell (SI-RequestConfig or SI-RequestConfigRepetition configuration), and / or the (dedicated) random access resources for additional physical cell identifiers (additional PCI) of the cell (RACH-ConfigTwoTA configuration), and / or the (dedicated) random access resources for handover and / or resynchronization of the cell as the target cell (RACH-ConfigDedicated configuration), and / or,

[0165] Random access resources (dedicated) for early uplink synchronization (EarlyUL-SyncConfig configuration) and / or for beam failure recovery (of the cell) and / or for system information requests (of the cell / in the cell) and / or for additional physical cell identifiers (of the cell).

[0166] In some embodiments, the first and / or second and / or third and / or fourth information in the information element used to configure random access resources is applied to the (dedicated) random access resources configured by the information element.

[0167] In some embodiments, for a random access resource configured by an information element for configuring a random access resource for a specific purpose or for a (dedicated) random access resource for a specific purpose, the UE determines the allowed / disallowed ROs and / or (should) be used in the random access resource and / or determines the valid ROs (among the allowed or should be used ROs) based on first and / or second and / or third and / or fourth information applied to the random access resource.

[0168] In some embodiments, the RO overlapping with the second time-domain resource configured as downlink includes at least one downlink symbol configured (first uplink / downlink configuration).

[0169] In some embodiments, the ROs overlapping with the second time-domain resource configured as downlink include: ROs in the second time-domain resource configured as downlink, and / or ROs across the second time-domain resource configured as downlink and the second time-domain resource configured as flexible.

[0170] In some embodiments, the ROs overlapping with the second time-domain resource include: ROs in the second time-domain resource, and / or ROs spanning the second time-domain resource and the first time-domain resource, and / or ROs that begin in the second time-domain resource and end in the first time-domain resource.

[0171] In some embodiments, when the first specific RACH configuration (RACH configuration Option 1) for transmitting random access preambles and / or for a specific SBFD random access operation is enabled and / or the use of ROs that overlap with the second time-domain resources configured for downlink is enabled (for the random access resources to which the first information and / or the fourth information are applied), the ROs that overlap with the second time-domain resources configured for downlink are valid ROs if at least one or more of the following conditions are met:

[0172] The frequency domain resource of the RO is fully within the UL usable PRBs.

[0173] The time-domain resource of the RO does not overlap with the synchronization signal block (SSB).

[0174] The RO (temporal domain resource) starts at least N times after the first temporal resource configured as downlink (first uplink / downlink configuration).gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last downlink non-SBFD symbol);

[0175] The time-domain resource of the RO (originating resource) begins at least N times after the most recent SSB (preceding the RO). gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last SSB (before the RO)).

[0176] In some embodiments, whether (when) sending random access preambles using ROs in the first time domain resource is not allowed and / or using ROs overlapping with the second time domain resource is allowed and / or a second specific RACH configuration (RACH configuration Option 2) for a specific random access operation (SBFD random access operation) is enabled and / or using ROs overlapping with the second time domain resource, (for the random access resource to which the second information and / or the third information and / or the fourth information are applied), the ROs in the first time domain resource are invalid ROs, and the ROs overlapping with the second time domain resource are valid ROs when (at least) one or more of the following conditions are met:

[0177] The frequency domain resource of the RO is fully within the UL usable PRBs.

[0178] The time-domain resource of the RO does not overlap with the synchronization signal block (SSB).

[0179] The RO (temporal domain resource) starts at least N times after the first temporal resource configured as downlink (first uplink / downlink configuration). gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last downlink non-SBFD symbol);

[0180] The time-domain resource of the RO (originating resource) begins at least N times after the most recent SSB (preceding the RO). gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last SSB (before the RO)).

[0181] In some embodiments, for random access resources configured for an information element (e.g., EarlyUL-SyncConfig) used to configure random access resources, the third frequency domain resources (UL usable PRBs) are uplink usable PRBs (UL usable PRBs) configured for the (UL)BWP of the information element, and / or, the first time domain resource is the first time domain resource configured for the information element, and / or, the first time domain resource configured for downlink is the first time domain resource configured for downlink by the information element (first uplink / downlink configuration), and / or, the synchronization signal block (SSB) is the SSB configured by the LTM candidate (LTM-Candidate) information element (LTM-SSB-Config-r18) where the information element is located, or the SSB configured by the LTM SSB configuration (LTM-SSB-Config-r18).

[0182] In some embodiments, for random access resources used in an early UL synchronization process, the third frequency domain resource is an uplink usable PRB (UL usable PRB) for the (UL)BWP used in the early UL synchronization process, and / or, the first time domain resource is a first time domain resource for the early UL synchronization process, and / or, the first time domain resource configured for downlink is a first time domain resource configured for downlink by a first uplink / downlink configuration for the early UL synchronization process, and / or, the synchronization signal block (SSB) is the SSB corresponding to an LTM candidate.

[0183] In some embodiments, when determining a valid PUSCH occasion (for two-step random access), the terminal device ignores or excludes (valid) ROs (in cell-specific random access resources) that overlap with the second time-domain resource configured for downlink and / or (valid) ROs that overlap with the second time-domain resource.

[0184] In other words, the validity of a PUSCH occasion is independent of the (valid) RO that overlaps with the second time-domain resource configured for downlink and / or the (valid) RO that overlaps with the second time-domain resource. For example, a PUSCH occasion that overlaps with the (valid) RO that overlaps with the second time-domain resource configured for downlink and / or the (valid) RO that overlaps with the second time-domain resource (in time-frequency) can be valid, depending on other conditions.

[0185] Table 5 is an example of an embodiment of this application.

[0186] [Revised according to Detailed Rules 26, March 2025] Table 5

[0187] In some embodiments, when the use of a RO that overlaps with a second time-domain resource configured for downlink to transmit a random access preamble and / or the first specific RACH configuration for a particular random access operation is not enabled, (for the random access resource to which the first information is applied) the RO that overlaps with a second time-domain resource configured for downlink is an invalid RO.

[0188] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0189] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0190] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the terminal device can use a random access opportunity (RO) that overlaps with the second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to send a preamble, thereby supporting random access in the presence of the aforementioned different time-domain resources, increasing the coverage and capacity of random access and reducing latency.

[0191] Second aspect of the embodiments

[0192] This application provides a random access method, which will be described from the perspective of the network device. The content that is the same as that in the first aspect of the embodiment will not be repeated.

[0193] Figure 6 is a schematic diagram of a random access method according to an embodiment of this application. As shown in Figure 6, the method includes:

[0194] 601, The network device sends information for configuring (the cell) a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured as downlink by (first uplink / downlink configuration) and / or a second time domain resource configured as flexible by (first uplink / downlink configuration), the first time domain resource being different from the second time domain resource;

[0195] 602, the network device uses a (valid) random access opportunity (RO) (associated with downlink signals (e.g., SSB or CSI-RS)) that overlaps with the second time-domain resource configured for downlink or an RO that overlaps with the second time-domain resource to receive a preamble.

[0196] It is worth noting that Figure 6 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 6 above.

[0197] In some embodiments, the information for configuring the first time-domain resources and / or the second time-domain resources may (optionally) be present in system information (e.g., SIB1) (broadcast or transmitted via dedicated signaling) and / or in the (public) serving cell configuration and / or in information elements for configuring random access resources (at least including RO).

[0198] In some embodiments, the information in the information element for configuring random access resources (e.g., EarlyUL-SyncConfig) for configuring first time-domain resources and / or second time-domain resources is configured based on the reference subcarrier spacing (SCS) of the first uplink / downlink configuration included in the information element, and / or...

[0199] The first time-domain resource and / or the second time-domain resource configured by the information element are determined based on the reference subcarrier spacing (SCS) of the first uplink / downlink configuration included in the information element for configuring random access resources.

[0200] In some embodiments, the information elements used to configure random access resources include:

[0201] The information element (EarlyUL-SyncConfig) used to configure random access resources for the early UL synchronization procedure, and / or,

[0202] Information elements used to configure (dedicated) random access resources for beam failure recovery (BeamFailureRecovery Config), and / or,

[0203] Information elements (SI-RequestConfig or SI-RequestConfigRepetition) used to configure (dedicated) random access resources for (Msg1-based) system information requests, and / or,

[0204] Information elements (RACH-ConfigTwoTA) used to configure (dedicated) random access resources for additional physical cell identifiers (PCI), and / or,

[0205] The information element (RACH-ConfigDedicated) is used to configure (dedicated) random access resources for handover and / or resynchronization.

[0206] In some embodiments, the system information and / or the serving cell configuration and / or the information element for configuring random access resources further include information for configuring a first frequency domain resource and / or a second frequency domain resource; wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink.

[0207] In some embodiments, the third frequency domain resources (UL usable PRBs) of the (UL)BWP configured for the information element (e.g., EarlyUL-SyncConfig) for configuring random access resources are the intersection of the first frequency domain resources configured by the information element and the (UL)BWP.

[0208] In some embodiments, the information for configuring the first time domain resources and / or the second time domain resources and / or the information for configuring the first frequency domain resources and / or the second frequency domain resources in the system message are applied to the cell that sent the system message or the cell to which the system message is addressed.

[0209] The information in the serving cell configuration used to configure the first time domain resources and / or the second time domain resources, and / or the information used to configure the first frequency domain resources and / or the second frequency domain resources, are applied to the cell for which the serving cell configuration is applied.

[0210] The information in the information element for configuring random access resources, namely the information for configuring the first time domain resources and / or the second time domain resources and / or the information for configuring the first frequency domain resources and / or the second frequency domain resources, is applied to the random access resources configured by the information element or to the cell to which the information element (configured random access resources) is targeted.

[0211] In some embodiments, the information element for configuring random access resources (e.g., EarlyUL-SyncConfig) further includes information for configuring third frequency domain resources (UL usable PRBs) for the (UL)BWP configured for the information element.

[0212] In some embodiments, the network device sends first information, which is used to indicate whether (whether) random access preamble transmission is permitted using a RO that overlaps with a second time-domain resource configured for downlink, and / or to indicate whether a first specific RACH configuration (RACH configuration Option 1) for a specific SBFD random access operation is enabled or not from the network side; and / or,

[0213] The network device sends a second message, which is used to indicate whether (or) sending a random access preamble using a RO in the first time domain resource is not allowed, and / or to indicate whether (or) sending a random access preamble using a RO overlapping with the second time domain resource is allowed, and / or to indicate whether sending a random access preamble using a RO in the second time domain resource is allowed, and / or to indicate whether a second specific RACH configuration (RACH configuration Option 2) for a specific random access operation (SBFD random access operation) is enabled (indicate whether RACH configuration Option 1 for SBFD random access operation is enabled or not from the network side); and / or,

[0214] The network device sends third information, which is used to indicate whether (or) it is permissible to send a random access preamble using ROs across the second time domain resource and the first time domain resource, and / or to indicate whether (or) it is permissible to send a random access preamble using ROs that begin in the second time domain resource and end in the first time domain resource; and / or,

[0215] The network device sends a fourth message, which instructs (the terminal device) to use a RO in the first time domain resource to send a random access preamble and / or use a RO that overlaps with a second time domain resource configured for downlink to send a random access preamble and / or use a RO that overlaps with a second time domain resource to send a random access preamble and / or not use a RO in the first time domain resource to send a random access preamble.

[0216] In some embodiments, the first information includes one bit, and / or the second information includes one bit, and / or the third information includes one bit, and / or the fourth information includes one bit or two bits.

[0217] In some embodiments, at least two of the first to fourth information are provided by the same information field (including one or two bits), and / or, at least two of the first to fourth information are provided by different information fields.

[0218] In some embodiments, the first information is applied to (contention-based and / or non-contention-based) four-step random access (4-step RACH) and two-step random access (2-step RACH); or,

[0219] The first information is applied to (contention-based and / or non-contention-based) four-step random access (4-step RACH) but not to (contention-based and / or non-contention-based) two-step random access (2-step RACH).

[0220] In some embodiments, the first information and / or the second information and / or the third information and / or the fourth information (optionally) exist in system messages and / or (public) serving cell configurations and / or information elements used to configure random access resources, and / or,

[0221] The first information and / or the second information and / or the third information do not simultaneously exist in the system message and / or do not simultaneously exist in the (public) serving cell configuration and / or do not simultaneously exist in the information element used to configure random access resources, and / or,

[0222] When the first information exists in and / or the second information does not exist in the system message and / or the serving cell configuration and / or the information element for configuring random access resources, the third information does not exist in the system message (where the second information does not exist) and / or the serving cell configuration and / or the information element for configuring random access resources.

[0223] In some embodiments, the first and / or second and / or third and / or fourth information in the (broadcast) system message:

[0224] Random access resources applied (in the cell sending the system message or in the cell to which the system message is addressed) for initial access and / or connection reconstruction and / or connection recovery and / or beam failure recovery and / or Request for Other SI and / or Scheduling Request (SR) failure and / or uplink desynchronization and / or Small Data Transmission (SDT) and / or uplink data arrival without PUCCH resources for SR and / or additional physical cell identifier (PCI), and / or

[0225] The public (cell-specific) random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the (dedicated) random access resources for beam failure recovery of the cell (BeamFailureRecoveryConfig configuration), and / or the (dedicated) random access resources for system information requests (Msg1-based) of the cell (SI-RequestConfig or SI-RequestConfigRepetition configuration), and / or the (dedicated) random access resources for additional physical cell identifiers (additional PCI) of the cell (RACH-ConfigTwoTA configuration), and / or,

[0226] Random access resources shall not be used for (dedicated) random access resources for early uplink synchronization and / or for handover and / or resynchronization and / or for beam failure recovery (of the cell) and / or for system information requests (of the cell / in the cell) and / or for additional physical cell identifiers (of the cell).

[0227] In some embodiments, the first and / or second and / or third and / or fourth information in the (public) serving cell configuration:

[0228] Random access resources applied (in the (public) serving cell configuration for) initial access and / or connection re-establishment and / or connection recovery and / or beam failure recovery and / or Request for Other SI and / or SR failure and / or uplink desynchronization and / or SDT and / or uplink data arrival without PUCCH resources for SR and / or additional physical cell identifier (PCI) and / or handover (to the cell) and / or resynchronization (to the cell), and / or,

[0229] The public (cell-specific) random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the (dedicated) random access resources for beam failure recovery of the cell (BeamFailureRecoveryConfig configuration), and / or the (dedicated) random access resources for system information requests (Msg1-based) of the cell (SI-RequestConfig or SI-RequestConfigRepetition configuration), and / or the (dedicated) random access resources for additional physical cell identifiers (additional PCI) of the cell (RACH-ConfigTwoTA configuration), and / or the (dedicated) random access resources for handover and / or resynchronization of the cell as the target cell (RACH-ConfigDedicated configuration), and / or,

[0230] Random access resources (dedicated) for early uplink synchronization (EarlyUL-SyncConfig configuration) and / or for beam failure recovery (of the cell) and / or for system information requests (of the cell / in the cell) and / or for additional physical cell identifiers (of the cell).

[0231] In some embodiments, the first and / or second and / or third and / or fourth information in the information element used to configure random access resources is applied to the (dedicated) random access resources configured by the information element.

[0232] In some embodiments, the RO overlapping with the second time-domain resource configured as downlink includes at least one downlink symbol configured (in the first uplink / downlink configuration), and / or,

[0233] ROs overlapping with a second time-domain resource configured as downlink include: ROs within the second time-domain resource configured as downlink, and / or ROs across the second time-domain resource configured as downlink and the second time-domain resource configured as flexible, and / or...

[0234] The ROs that overlap with the second time-domain resource include: ROs in the second time-domain resource, and / or ROs spanning the second time-domain resource and the first time-domain resource, and / or ROs that begin in the second time-domain resource and end in the first time-domain resource.

[0235] In some embodiments, when the first specific RACH configuration (RACH configuration Option 1) for transmitting random access preambles and / or for a specific SBFD random access operation is enabled and / or the use of ROs that overlap with the second time-domain resources configured for downlink is enabled (for the random access resources to which the first information and / or the fourth information are applied), the ROs that overlap with the second time-domain resources configured for downlink are valid ROs if at least one or more of the following conditions are met:

[0236] The frequency domain resource of the RO is fully within the UL usable PRBs.

[0237] The time-domain resource of the RO does not overlap with the synchronization signal block (SSB).

[0238] The RO (temporal domain resource) starts at least N times after the first temporal resource configured as downlink (first uplink / downlink configuration). gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last downlink non-SBFD symbol);

[0239] The time-domain resource of the RO (originating resource) begins at least N times after the most recent SSB (preceding the RO). gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last SSB (before the RO)).

[0240] In some embodiments, whether (when) sending random access preambles using ROs in the first time domain resource is not allowed and / or using ROs overlapping with the second time domain resource is allowed and / or a second specific RACH configuration (RACH configuration Option 2) for a specific random access operation (SBFD random access operation) is enabled and / or using ROs overlapping with the second time domain resource, (for the random access resource to which the second information and / or the third information and / or the fourth information are applied), the ROs in the first time domain resource are invalid ROs, and the ROs overlapping with the second time domain resource are valid ROs when (at least) one or more of the following conditions are met:

[0241] The frequency domain resource of the RO is fully within the UL usable PRBs.

[0242] The time-domain resource of the RO does not overlap with the synchronization signal block (SSB).

[0243] The RO (temporal domain resource) starts at least N times after the first temporal resource configured as downlink (first uplink / downlink configuration). gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last downlink non-SBFD symbol);

[0244] The time-domain resource of the RO (originating resource) begins at least N times after the most recent SSB (preceding the RO). gap A symbol ((Time resource of) the RO starts at least N) gap symbols after a last SSB (before the RO)).

[0245] In some embodiments, for random access resources configured for an information element (e.g., EarlyUL-SyncConfig) used to configure random access resources, the third frequency domain resources (UL usable PRBs) are uplink usable PRBs (UL usable PRBs) configured for the (UL)BWP of the information element, and / or, the first time domain resource is the first time domain resource configured for the information element, and / or, the first time domain resource configured for downlink is the first time domain resource configured for downlink by the information element (first uplink / downlink configuration), and / or, the synchronization signal block (SSB) is the SSB configured by the LTM candidate (LTM-Candidate) information element (LTM-SSB-Config-r18) where the information element is located, or the SSB configured by the LTM SSB configuration (LTM-SSB-Config-r18).

[0246] In some embodiments, for random access resources used in an early UL synchronization process, the third frequency domain resource is an uplink usable PRB (UL usable PRB) for the (UL)BWP used in the early UL synchronization process, and / or, the first time domain resource is a first time domain resource for the early UL synchronization process, and / or, the first time domain resource configured for downlink is a first time domain resource configured for downlink by a first uplink / downlink configuration for the early UL synchronization process, and / or, the synchronization signal block (SSB) is the SSB corresponding to an LTM candidate.

[0247] In some embodiments, when determining a valid PUSCH occasion (for two-step random access), the network device ignores or excludes (valid) ROs (in cell-specific random access resources) that overlap with a second time-domain resource configured for downlink and / or ROs that overlap with a second time-domain resource.

[0248] In some embodiments, when the use of a RO that overlaps with a second time-domain resource configured for downlink to transmit a random access preamble and / or the first specific RACH configuration for a particular random access operation is not enabled, (for the random access resource to which the first information is applied) the RO that overlaps with a second time-domain resource configured for downlink is an invalid RO.

[0249] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0250] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0251] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the network device can support random access in the presence of the aforementioned different time-domain resources by using a random access opportunity (RO) that overlaps with the second time-domain resource configured for downlink or a RO receiving preamble that overlaps with the second time-domain resource, thereby increasing the coverage and capacity of random access and reducing latency.

[0252] Third aspect of the embodiments

[0253] This application provides a random access device. This device may be, for example, a terminal device, or one or more components or parts configured within a terminal device; details identical to those in the first aspect of the embodiment will not be repeated.

[0254] Figure 7 is a schematic diagram of a random access device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method of the embodiment of the first aspect, its specific implementation can refer to the embodiment of the first aspect, and the contents that are the same will not be repeated. As shown in Figure 7, the random access device 700 includes: a receiver 701 and a transmitter 702; it may also include a processor 703.

[0255] Receiver 701 receives information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource;

[0256] Transmitter 702 uses a random access opportunity (RO) that overlaps with a second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to transmit a preamble.

[0257] In some embodiments, the information for configuring the first time-domain resources and / or the second time-domain resources is contained in the system information and / or the serving cell configuration and / or the information element for configuring random access resources.

[0258] In some embodiments, the information in the information element for configuring random access resources for configuring first time-domain resources and / or second time-domain resources is configured based on the reference subcarrier spacing of the first uplink / downlink configuration included in the information element, and / or,

[0259] The first time-domain resource and / or the second time-domain resource configured by the information element are determined based on the reference subcarrier spacing of the first uplink / downlink configuration included in the information element used to configure random access resources.

[0260] In some embodiments, the information elements used to configure random access resources include:

[0261] Information elements used to configure random access resources for the early uplink synchronization process, and / or,

[0262] Information elements used to configure random access resources for beam failure recovery, and / or,

[0263] Information elements used to configure random access resources for system information requests, and / or,

[0264] Information elements used to configure random access resources for additional physical cell identifiers, and / or,

[0265] Information elements used to configure random access resources for handover and / or resynchronization.

[0266] In some embodiments, the system information and / or the serving cell configuration and / or the information element for configuring random access resources further include information for configuring a first frequency domain resource and / or a second frequency domain resource; wherein, in the second time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink.

[0267] In some embodiments, the third frequency domain resource of the BWP configured for the information element for configuring random access resources is the intersection of the first frequency domain resource configured for the information element and the BWP.

[0268] In some embodiments, the information for configuring the first time domain resources and / or the second time domain resources and / or the information for configuring the first frequency domain resources and / or the second frequency domain resources in the system message are applied to the cell that sent the system message or the cell to which the system message is addressed.

[0269] The information in the serving cell configuration used to configure the first time domain resources and / or the second time domain resources, and / or the information used to configure the first frequency domain resources and / or the second frequency domain resources, are applied to the cell for which the serving cell configuration is applied.

[0270] The information in the information element for configuring random access resources, namely the information for configuring the first time domain resources and / or the second time domain resources and / or the information for configuring the first frequency domain resources and / or the second frequency domain resources, is applied to the random access resources configured by the information element or to the cell to which the information element (configured random access resources) is targeted.

[0271] In some embodiments, receiver 701 is further configured to:

[0272] Receive first information, the first information being used to indicate that a random access preamble is permitted to be transmitted using a RO that overlaps with a second time-domain resource configured for downlink, and / or, to indicate that a first specific RACH configuration for a specific random access operation is enabled; and / or,

[0273] Receive second information, the second information being used to indicate that the use of ROs in the first time domain resource is not allowed to transmit a random access preamble, and / or, to indicate that the use of ROs overlapping with the second time domain resource is allowed to transmit a random access preamble, and / or, to indicate that the use of ROs in the second time domain resource is allowed to transmit a random access preamble, and / or, to indicate that a second specific RACH configuration for a specific random access operation is enabled; and / or,

[0274] Receive third information, the third information being used to indicate that random access preambles can be transmitted using ROs across the second time domain resource and the first time domain resource, and / or, to indicate that random access preambles can be transmitted using ROs that begin in the second time domain resource and end in the first time domain resource; and / or,

[0275] Receive fourth information, the fourth information being used to instruct (the terminal device) to send a random access preamble using ROs in the first time domain resources and / or to send a random access preamble using ROs that overlap with the second time domain resources configured for downlink and / or to send a random access preamble using ROs that overlap with the second time domain resources and / or not to send a random access preamble using ROs in the first time domain resources.

[0276] In some embodiments, the first information includes one bit, and / or the second information includes one bit, and / or the third information includes one bit, and / or the fourth information includes one bit or two bits, and / or...

[0277] At least two of the first to fourth pieces of information are provided by the same information field, and / or at least two of the first to fourth pieces of information are provided by different information fields.

[0278] In some embodiments, the first information is applied to both four-step random access and two-step random access; or, the first information is applied to four-step random access but not to two-step random access.

[0279] In some embodiments, the first information and / or the second information and / or the third information and / or the fourth information exist in system messages and / or serving cell configurations and / or information elements used to configure random access resources, and / or...

[0280] The first information and / or the second information and / or the third information do not simultaneously exist in the system message and / or do not simultaneously exist in the serving cell configuration and / or do not simultaneously exist in the information element used to configure random access resources, and / or,

[0281] When the first information exists in and / or the second information does not exist in the system message and / or the serving cell configuration and / or the information element for configuring random access resources, the third information does not exist in the system message (where the second information does not exist) and / or the serving cell configuration and / or the information element for configuring random access resources.

[0282] In some embodiments, the first and / or second and / or third and / or fourth information in the system message:

[0283] Applied to random access resources for initial access and / or connection reconstruction and / or connection recovery and / or beam failure recovery and / or system information request and / or scheduling request failure and / or uplink desynchronization and / or small data transmission and / or uplink data arrival without PUCCH resources for SR and / or additional physical cell identifier, and / or,

[0284] The public random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the random access resources for beam failure recovery of the cell, and / or the random access resources for system information requests of the cell, and / or the random access resources for the additional physical cell identifier of the cell, and / or,

[0285] Random access resources for early uplink synchronization and / or for handover and / or resynchronization and / or for beam failure recovery (of the cell) and / or for system information requests (of the cell / in the cell) and / or for additional physical cell identifiers (of the cell) shall not be applied.

[0286] In some embodiments, the first and / or second and / or third and / or fourth information in the serving cell configuration:

[0287] Random access resources applied to initial access and / or connection reconstruction and / or connection recovery and / or beam failure recovery and / or system information request and / or SR failure and / or uplink desynchronization and / or SDT and / or uplink data arrival without PUCCH resources for SR and / or additional physical cell identifier and / or handover and / or resynchronization, and / or

[0288] The public random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the random access resources for beam failure recovery of the cell, and / or the random access resources for system information requests of the cell, and / or the random access resources for the cell with an additional physical cell identifier, and / or the random access resources for handover and / or resynchronization of the cell as the target cell, and / or,

[0289] Random access resources for early uplink synchronization and / or for beam failure recovery (of the cell) and / or for system information requests (of the cell / in the cell) and / or for additional physical cell identifiers (of the cell) shall not be applied.

[0290] In some embodiments, the first and / or second and / or third and / or fourth information in the information element used to configure random access resources is applied to the random access resources configured by the information element.

[0291] In some embodiments, the RO overlapping with the second time-domain resource configured as downlink includes at least one configured downlink symbol, and / or,

[0292] ROs overlapping with a second time-domain resource configured as downlink include: ROs within the second time-domain resource configured as downlink, and / or ROs across the second time-domain resource configured as downlink and the second time-domain resource configured as flexible, and / or...

[0293] The ROs that overlap with the second time-domain resource include: ROs in the second time-domain resource, and / or ROs spanning the second time-domain resource and the first time-domain resource, and / or ROs that begin in the second time-domain resource and end in the first time-domain resource.

[0294] In some embodiments, it is permissible to use a RO that overlaps with a second time-domain resource configured for downlink to transmit a random access preamble and / or a first specific RACH configuration for a particular random access operation is enabled and / or a RO that overlaps with a second time-domain resource configured for downlink is used. A RO that overlaps with a second time-domain resource configured for downlink is a valid RO if one or more of the following conditions are met:

[0295] The RO is in the third frequency domain resource;

[0296] The RO and the synchronization signal block do not overlap;

[0297] The RO begins at least N times after the first time-domain resource configured for downlink. gap One symbol;

[0298] The RO begins at least N days after the synchronization signal block. gap A symbol.

[0299] In some embodiments, if the use of ROs in a first time domain resource is not permitted to transmit random access preambles and / or the use of ROs overlapping with second time domain resources is permitted and / or a second specific RACH configuration for a specific random access operation is enabled and / or the use of ROs overlapping with second time domain resources is permitted, the ROs in the first time domain resource are invalid ROs, and the ROs overlapping with second time domain resources are valid ROs when one or more of the following conditions are met:

[0300] The RO is in the third frequency domain resource;

[0301] The RO and the synchronization signal block do not overlap;

[0302] The RO begins at least N times after the first time-domain resource configured for downlink. gap One symbol;

[0303] The RO begins at least N days after the synchronization signal block. gap A symbol.

[0304] In some embodiments, for the random access resources configured for the information element used to configure random access resources, the third frequency domain resource is an uplink available PRB for the BWP configured for the information element, and / or, the first time domain resource is a first time domain resource configured for the information element, and / or, the first time domain resource configured for downlink is a first time domain resource configured for downlink by the information element, and / or, the synchronization signal block is an SSB configured by the LTM candidate information element where the information element is located or an SSB configured by the LTM SSB configuration.

[0305] In some embodiments, ROs that overlap with a second time-domain resource configured for downlink and / or ROs that overlap with a second time-domain resource are ignored or excluded when determining a valid PUSCH opportunity.

[0306] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The random access device 700 in this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0307] Furthermore, for simplicity, Figure 7 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0308] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0309] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the terminal device can use a random access opportunity (RO) that overlaps with the second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to send a preamble, thereby supporting random access in the presence of the aforementioned different time-domain resources, increasing the coverage and capacity of random access and reducing latency.

[0310] Fourth aspect of the embodiment

[0311] This application provides a random access device. This device may be, for example, a network device, or one or more components or parts configured within a network device; details identical to those in the second aspect of the embodiment will not be repeated.

[0312] Figure 8 is a schematic diagram of a random access device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method of the embodiment of the second aspect, its specific implementation can refer to the embodiment of the second aspect, and the contents that are the same will not be repeated. As shown in Figure 8, the random access device 800 includes: a transmitter 801 and a receiver 802; it may also include a processor 803.

[0313] Transmitter 801 transmits information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource;

[0314] Receiver 802 uses a random access opportunity (RO) that overlaps with a second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to receive a preamble.

[0315] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The random access device 800 in this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0316] Furthermore, for simplicity, Figure 8 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0317] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0318] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the network device can support random access in the presence of the aforementioned different time-domain resources by using a random access opportunity (RO) that overlaps with the second time-domain resource configured for downlink or a RO receiving preamble that overlaps with the second time-domain resource, thereby increasing the coverage and capacity of random access and reducing latency.

[0319] Fifth aspect of the embodiment

[0320] This application also provides a communication system, which can be referred to FIG1. ​​The contents that are the same as those in the embodiments of the first to fourth aspects will not be repeated.

[0321] In some embodiments, the communication system 100 may include at least:

[0322] A network device that transmits information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource; and receives a preamble;

[0323] A terminal device receives the information for configuring a first time domain resource and / or a second time domain resource; and transmits the preamble using a random access opportunity (RO) that overlaps with the second time domain resource configured for downlink or an RO that overlaps with the second time domain resource.

[0324] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0325] Figure 9 is a schematic diagram of the network device according to an embodiment of this application. As shown in Figure 9, the network device 900 may include: a processor 910 (e.g., a central processing unit CPU) and a memory 920; the memory 920 is coupled to the processor 910. The memory 920 can store various data; in addition, it also stores an information processing program 930, and executes the program 930 under the control of the processor 910.

[0326] For example, processor 910 can be configured to execute a program to implement the method as described in the embodiments of the second aspect.

[0327] In addition, as shown in Figure 9, the network device 900 may also include a transceiver 940 and an antenna 950, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that the network device 900 does not necessarily have to include all the components shown in Figure 9; in addition, the network device 900 may also include components not shown in Figure 9, which can be referred to in the prior art.

[0328] This application also provides a terminal device, but the application is not limited to this and may also include other devices.

[0329] Figure 10 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 10, the terminal device 1000 may include a processor 1010 and a memory 1020; the memory 1020 stores data and programs and is coupled to the processor 1010. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0330] For example, processor 1010 can be configured to execute a program to implement the method as described in the embodiment of the first aspect.

[0331] As shown in Figure 10, the terminal device 1000 may further include: a communication module 1030, an input device 1040, a display 1050, and a power supply 1060. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 1000 does not necessarily include all the components shown in Figure 10; these components are not essential. Furthermore, the terminal device 1000 may also include components not shown in Figure 10, which can be referred to in the prior art.

[0332] This application also provides a computer-readable program, wherein when the program is executed in a network device, the program causes the computer to perform the method described in the second aspect of the embodiment in the network device.

[0333] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a network device to perform the methods described in the second aspect of the embodiments.

[0334] This application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program causes the computer to perform the method described in the first aspect of the embodiment in the terminal device.

[0335] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a terminal device to perform the method described in the first aspect of the embodiments.

[0336] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. Logic components include, for example, field-programmable logic devices (FPGAs), microprocessors, and processors used in computers. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, and flash memory.

[0337] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0338] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0339] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0340] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0341] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0342] 1. A random access method, comprising:

[0343] The terminal device receives information for configuring (cell) first time domain resources and / or second time domain resources, the second time domain resources including second time domain resources configured as downlink by (first uplink / downlink configuration) and / or second time domain resources configured as flexible by (first uplink / downlink configuration), the first time domain resources being different from the second time domain resources;

[0344] The terminal device uses a (valid) random access opportunity (RO) (associated with downlink signals (e.g., SSB or CSI-RS)) that overlaps with the second time-domain resource configured for downlink, or an RO that overlaps with the second time-domain resource to send a preamble.

[0345] 2. A random access method, comprising:

[0346] The network device sends information for configuring (the cell) first time domain resources and / or second time domain resources, the second time domain resources including second time domain resources configured as downlink by (first uplink / downlink configuration) and / or second time domain resources configured as flexible by (first uplink / downlink configuration), the first time domain resources being different from the second time domain resources;

[0347] The network device uses a (valid) random access opportunity (RO) (associated with downlink signals (e.g., SSB or CSI-RS)) that overlaps with the second time-domain resource configured for downlink, or an RO that overlaps with the second time-domain resource to receive a preamble.

[0348] 3. The method according to Appendix 2, wherein the method further comprises:

[0349] The network device sends first information, which is used to indicate whether (whether) random access preamble transmission is permitted using a RO that overlaps with a second time-domain resource configured for downlink, and / or to indicate whether a first specific RACH configuration (RACH configuration Option 1) for a specific SBFD random access operation is enabled or not from the network side; and / or,

[0350] The network device sends a second message, which is used to indicate whether (or) sending a random access preamble using a RO in the first time domain resource is not allowed, and / or to indicate whether (or) sending a random access preamble using a RO overlapping with the second time domain resource is allowed, and / or to indicate whether sending a random access preamble using a RO in the second time domain resource is allowed, and / or to indicate whether a second specific RACH configuration (RACH configuration Option 2) for a specific SBFD random access operation is enabled (indicate whether RACH configuration Option 1 for SBFD random access operation is enabled or not from the network side); and / or,

[0351] The network device sends third information, which is used to indicate whether (or) it is permissible to send a random access preamble using ROs across the second time domain resource and the first time domain resource, and / or to indicate whether (or) it is permissible to send a random access preamble using ROs that begin in the second time domain resource and end in the first time domain resource; and / or,

[0352] The network device sends a fourth message, which instructs (the terminal device) to use a RO in the first time domain resource to send a random access preamble and / or use a RO that overlaps with a second time domain resource configured for downlink to send a random access preamble and / or use a RO that overlaps with a second time domain resource to send a random access preamble and / or not use a RO in the first time domain resource to send a random access preamble.

[0353] 4. The method according to Appendix 2, wherein the information element for configuring random access resources (e.g., EarlyUL-SyncConfig) further includes information for configuring third frequency domain resources (UL usable PRBs) of the (UL)BWP configured for the information element.

[0354] 5. The method according to Appendix 2, wherein, for random access resources used in the early UL synchronization process, the third frequency domain resource is an uplink usable PRB for the (UL)BWP used in the early UL synchronization process, and / or, the first time domain resource is a first time domain resource for the early UL synchronization process, and / or, the first time domain resource configured for downlink is a first time domain resource configured for downlink by a first uplink / downlink configuration for the early UL synchronization process, and / or, the synchronization signal block (SSB) is the SSB corresponding to an LTM candidate.

[0355] 6. The method according to Appendix 2, wherein, (when) the use of ROs that overlap with the second time-domain resources configured for downlink to transmit random access preambles and / or the first specific RACH configuration for a specific random access operation is not enabled, (for the random access resources to which the first information is applied,) the ROs that overlap with the second time-domain resources configured for downlink are invalid ROs.

[0356] 7. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the random access method as described in Appendix 1.

[0357] 8. A network device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the random access method as described in any one of Appendices 2 to 6.

[0358] 9. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the random access method as described in Appendix 1.

[0359] 10. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform the random access method as described in any one of Appendices 2 to 6.

Claims

1. A random access apparatus, comprising: a receiver that receives information for configuring first time domain resources and / or second time domain resources, the second time domain resources comprising second time domain resources configured as downlink and / or second time domain resources configured as flexible, the first time domain resources being different from the second time domain resources; a transmitter that transmits a preamble using a RO that overlaps with the second time domain resources configured as downlink or a RO that overlaps with the second time domain resources.

2. The apparatus of claim 1, wherein, The information for configuring first time domain resources and / or second time domain resources is present in system information and / or in a common serving cell configuration and / or in a serving cell configuration and / or in an information element for configuring random access resources. 3.The apparatus according to claim 2, wherein The information for configuring first time domain resources and / or second time domain resources in the information element for configuring random access resources configures the first time domain resources and / or the second time domain resources based on a reference subcarrier spacing of a first uplink-downlink configuration included in the information element, and / or The first time domain resources and / or the second time domain resources configured by the information element are determined according to a reference subcarrier spacing of a first uplink-downlink configuration included in the information element for configuring random access resources.

4. The apparatus of claim 1, wherein, The information element for configuring random access resources comprises: an information element for configuring random access resources for an early uplink synchronization procedure, and / or an information element for configuring random access resources for a beam failure recovery, and / or an information element for configuring random access resources for a system information request, and / or an information element for configuring random access resources for an additional physical cell identity, and / or an information element for configuring random access resources for a handover and / or a resynchronization.

5. The apparatus of claim 2, wherein, The system information and / or the serving cell configuration and / or the information element for configuring random access resources further comprises information for configuring first frequency domain resources and / or second frequency domain resources; wherein in the second time domain resources, the first frequency domain resources are for uplink and the second frequency domain resources are for downlink.

6. The apparatus of claim 5, wherein, A third frequency domain resource of a BWP configured by the information element for configuring random access resources is an intersection of the first frequency domain resources configured by the information element and the BWP. 7.The apparatus according to claim 5, wherein The information for configuring first time domain resources and / or second time domain resources in the system message and / or the information for configuring first frequency domain resources and / or second frequency domain resources applies to a cell that transmits the system message or a cell that the system message is for, The information for configuring first time domain resources and / or second time domain resources in the serving cell configuration and / or the information for configuring first frequency domain resources and / or second frequency domain resources applies to a serving cell that the serving cell configuration is for, The information for configuring the first time domain resource and / or the second time domain resource and / or the information for configuring the first frequency domain resource and / or the second frequency domain resource in the information element for configuring random access resources applies to the random access resources configured by the information element or the cell for which the information element (configured random access resources) is targeting.

8. The apparatus of claim 1, wherein, The receiver is further configured to: receive first information indicating that it is allowed to transmit a random access preamble using ROs overlapping with a second time domain resource configured as downlink, and / or, indicating that a first specific RACH configuration for a specific random access operation is enabled; and / or, receive second information indicating that it is not allowed to transmit a random access preamble using ROs in the first time domain resource, and / or, indicating that it is allowed to transmit a random access preamble using ROs overlapping with the second time domain resource, and / or, indicating that it is allowed to transmit a random access preamble using ROs in the second time domain resource, and / or, indicating that a second specific RACH configuration for a specific random access operation is enabled; and / or, receive third information indicating that it is allowed to transmit a random access preamble using ROs across the second time domain resource and the first time domain resource, and / or, indicating that it is allowed to transmit a random access preamble using ROs starting in the second time domain resource and ending in the first time domain resource; and / or, receive fourth information indicating to transmit a random access preamble using ROs in the first time domain resource and / or using ROs overlapping with a second time domain resource configured as downlink and / or using ROs overlapping with the second time domain resource and / or not using ROs in the first time domain resource.

9. The apparatus of claim 8, wherein, The first information comprises one bit, and / or, the second information comprises one bit, and / or, the third information comprises one bit, and / or, the fourth information comprises one bit or two bits, and / or, At least two of the first information to the fourth information are provided by the same information field, and / or, at least two of the first information to the fourth information are provided by different information fields. 10.The apparatus according to claim 8, wherein The first information applies to four-step random access and two-step random access; or, The first information applies to four-step random access and does not apply to two-step random access. 11.The apparatus according to claim 8, wherein The first information and / or the second information and / or the third information and / or the fourth information are present in a system message and / or a serving cell configuration and / or an information element for configuring random access resources, and / or, The first information and / or the second information and / or the third information are not present in the system message and / or the serving cell configuration and / or the information element for configuring random access resources at the same time, and / or, The first information and / or the second information and / or the third information and / or the fourth information are not present in the system message and / or the serving cell configuration and / or the information element at the same time, and / or, The third information does not exist in the system message and / or the serving cell configuration and / or the information element for configuring random access resources when the first information exists and / or the second information does not exist in the system message and / or the serving cell configuration and / or the information element for configuring random access resources.

12. The apparatus of claim 11, wherein, The first and / or second and / or third and / or fourth information in the system message: Applied to random access resources for initial access and / or connection reconstruction and / or connection recovery and / or beam failure recovery and / or system information request and / or scheduling request failure and / or uplink desynchronization and / or small data transmission and / or uplink data arrival without a scheduling request, and / or additional physical cell identifiers, and / or The public random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the random access resources for beam failure recovery of the cell, and / or the random access resources for system information requests of the cell, and / or the random access resources for the additional physical cell identifier of the cell, and / or, Random access resources that are not used for early uplink synchronization and / or for handover and / or resynchronization and / or for beam failure recovery and / or for system information requests and / or for additional physical cell identifiers.

13. The apparatus of claim 11, wherein, The first and / or second and / or third and / or fourth information in the serving cell configuration: Applied to PUCCH resources and / or additional physical cell identifiers and / or handover and / or resynchronization for initial access and / or connection reconstruction and / or connection recovery and / or beam failure recovery and / or system information request and / or scheduling request failure and / or uplink desynchronization and / or small data transmission and / or uplink data arrival without a scheduling request and / or random access resources for handover and / or resynchronization, and / or The public random access resources applied to the cell sending the system message or the cell to which the system message is addressed, and / or the random access resources for beam failure recovery of the cell, and / or the random access resources for system information requests of the cell, and / or the random access resources for the cell with an additional physical cell identifier, and / or the random access resources for handover and / or resynchronization of the cell as the target cell, and / or, Random access resources that are not intended for early uplink synchronization and / or for beam failure recovery and / or for system information requests and / or for additional physical cell identifiers should not be used.

14. The apparatus according to claim 11, wherein, The first and / or second and / or third and / or fourth information in the information element used to configure random access resources is applied to the random access resources configured by the information element.

15. The apparatus according to claim 1, wherein, The RO overlapping with the second time-domain resource configured as downlink includes at least one configured downlink symbol, and / or, ROs overlapping with a second time-domain resource configured as downlink include: ROs within the second time-domain resource configured as downlink, and / or ROs across the second time-domain resource configured as downlink and the second time-domain resource configured as flexible, and / or... The ROs that overlap with the second time-domain resource include: ROs in the second time-domain resource, and / or ROs spanning the second time-domain resource and the first time-domain resource, and / or ROs that begin in the second time-domain resource and end in the first time-domain resource.

16. The apparatus according to claim 1, wherein, Allowing the use of ROs that overlap with second time-domain resources configured for downlink to transmit random access preambles and / or a first specific RACH configuration for a specific random access operation is enabled and / or the use of ROs that overlap with second time-domain resources configured for downlink is a valid RO if one or more of the following conditions are met: The RO is in the third frequency domain resource; The RO and the synchronization signal block do not overlap; The RO starts at least N gap symbols after a first time domain resource configured as downlink; The RO starts at least N gap symbols after a synchronization signal block; And / or, If the use of a RO in the first time domain resource is not permitted to transmit a random access preamble and / or the use of a RO overlapping with a second time domain resource is permitted and / or a second specific RACH configuration for a specific random access operation is enabled and / or a RO overlapping with a second time domain resource is used, the RO in the first time domain resource is an invalid RO, and the RO overlapping with a second time domain resource is a valid RO if one or more of the following conditions are met: The RO is in the third frequency domain resource; The RO and the synchronization signal block do not overlap; The RO starts at least N gap symbols after a first time domain resource configured as downlink; The RO starts at least N gap symbols after a synchronization signal block.

17. The apparatus of claim 16, wherein, For the random access resources configured for the information element used to configure random access resources, the third frequency domain resource is the uplink available PRB for the BWP configured for the information element, and / or, the first time domain resource is the first time domain resource configured for the information element, and / or, the first time domain resource configured for downlink is the first time domain resource configured for downlink by the information element, and / or, the synchronization signal block is the SSB configured by the LTM candidate information element where the information element is located or the SSB configured by the LTM SSB configuration.

18. The apparatus of claim 16, wherein, When determining a valid PUSCH opportunity, ignore or exclude ROs that overlap with the second time-domain resource configured for downlink and / or ROs that overlap with the second time-domain resource.

19. A random access device, comprising: A transmitter that transmits information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource; The receiver uses a RO that overlaps with a second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource to receive a preamble.

20. A communication system, comprising: A network device that transmits information for configuring a first time domain resource and / or a second time domain resource, the second time domain resource including a second time domain resource configured for downlink and / or a second time domain resource configured for flexibility, the first time domain resource being different from the second time domain resource; and receives a random access preamble; The terminal device receives the information for configuring the first time domain resources and / or the second time domain resources; The preamble is transmitted using a RO that overlaps with a second time-domain resource configured for downlink or a RO that overlaps with the second time-domain resource.

Images