Method and apparatus for determining duplex configuration, and device

Abstract

The present application belongs to the field of communications. Disclosed are a method and apparatus for determining a duplex configuration, and a device. The method for determining a duplex configuration in the embodiments of the present application comprises: a terminal receiving random access configuration information from a network-side device, wherein the random access configuration information is used for configuring at least one of the following: a random access uplink resource, and a set of random access uplink resources; and the terminal determining a duplex configuration on the basis of the random access configuration information.

Description

Method, device and equipment for determining duplex configuration

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on November 15, 2023, with application number 202311529995.6 and titled “Method, device and apparatus for determining duplex configuration,” the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communications, and more particularly, to a method, apparatus, and device for determining a duplex configuration. Background Art

[0004] In cellular networks, half-duplex and full-duplex modes have been introduced to more flexibly utilize limited spectrum resources. In half-duplex mode, only uplink or downlink transmissions can occur at the same time, but not both simultaneously. In full-duplex mode, uplink and downlink transmissions can occur simultaneously at different frequency locations. However, determining the duplex configuration remains a challenge.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a method, apparatus, and device for determining a duplex configuration, which can determine the duplex configuration based on the configuration of a random access uplink resource or a set of random access uplink resources, can perform random access uplink transmission in a duplex mode, and can solve the problem of being unable to determine the duplex configuration.

[0007] In a first aspect, a method for determining a duplex configuration is provided, comprising:

[0008] The terminal receives random access configuration information from a network side device; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources;

[0009] The terminal determines a duplex configuration according to the random access configuration information.

[0010] In a second aspect, a method for determining a duplex configuration is provided, comprising:

[0011] The network side device sends random access configuration information to the terminal; wherein the random access configuration information is used to configure at least one of the following: random access uplink resources, a set of random access uplink resources; wherein the random access configuration information is associated with duplex configuration.

[0012] In a third aspect, a device for determining a duplex configuration is provided, including:

[0013] A transceiver unit, configured to receive random access configuration information from a network side device; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources;

[0014] A processing unit is configured to determine a duplex configuration according to the random access configuration information.

[0015] In a fourth aspect, a device for determining a duplex configuration is provided, comprising:

[0016] A transceiver unit is used to send random access configuration information to a terminal; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources; wherein the random access configuration information is associated with a duplex configuration.

[0017] In a fifth aspect, a terminal is provided, which includes a transceiver, a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0018] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface; wherein the communication interface is used to receive random access configuration information from a network side device; wherein the random access configuration information is used to configure at least one of the following: random access uplink resources, a set of random access uplink resources; and the processor is used to determine the duplex configuration based on the random access configuration information.

[0019] In the seventh aspect, a network side device is provided, which includes a transceiver, a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0020] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to send random access configuration information to the terminal; wherein the random access configuration information is used to configure at least one of the following: random access uplink resources, a set of random access uplink resources; wherein the random access configuration information is associated with the duplex configuration.

[0021] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0022] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0023] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0024] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the method for determining the duplex configuration as described in the first aspect or the second aspect.

[0025] In an embodiment of the present application, the terminal can determine the duplex configuration based on the random access configuration information, wherein the random access configuration information is used to configure at least one of the following: random access uplink resources, a set of random access uplink resources, and can perform random access uplink transmission in duplex mode, thereby improving the resource utilization of random access and reducing the delay of random access uplink transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0027] FIG1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0028] FIG2 is a schematic diagram of a full-duplex system provided by the present application.

[0029] FIG3 is a schematic diagram of another full-duplex provided by the present application.

[0030] Figure 4 is a schematic diagram of gNB full-duplex and UE full-duplex provided in this application.

[0031] FIG5 is a schematic diagram of full-duplex and guard interval (GB) provided by the present application.

[0032] FIG6 is a schematic flowchart of a method for determining a duplex configuration according to an embodiment of the present application.

[0033] FIG7 is a schematic diagram of an uplink subband and a guard interval provided according to an embodiment of the present application.

[0034] FIG8 is a schematic diagram of another uplink subband and guard interval provided according to an embodiment of the present application.

[0035] FIG9 is a schematic block diagram of a device for determining a duplex configuration according to an embodiment of the present application.

[0036] FIG10 is a schematic block diagram of a device for determining a duplex configuration according to an embodiment of the present application.

[0037] FIG11 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0038] FIG12 is a schematic diagram of the hardware structure of a terminal provided according to an embodiment of the present application.

[0039] FIG13 is a schematic block diagram of a network-side device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0041] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0042] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0043] It is worth noting that the technology described in the embodiments of the present application is not limited to the Internet of Things (IoT) system, but can also be used in other wireless communication systems, such as Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Bluetooth systems, or other systems. In the embodiments of the present application, the terms "system" and "network" are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description. However, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0044] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0045] To facilitate a better understanding of the embodiments of the present application, the random access process related to the present application is described.

[0046] The random access procedure may be a contention-based random access procedure or a non-contention-based random access procedure. The random access procedure may be a four-step random access procedure (also known as a Type-1 random access procedure) or a two-step random access procedure (also known as a Type-2 random access procedure).

[0047] In the four-step random access procedure (4-step RACH), the UE first sends message 1 (MSG.1) containing a preamble to the network. After detecting the preamble, the network sends message 2 (MSG.2) or a Random Access Response (RAR) message, which contains the preamble number detected by the network and the uplink radio resources allocated to the UE for sending message 3 (MSG.3). After receiving MSG.2, the UE confirms that at least one of the preamble numbers carried in MSG.2 matches the number of the preamble it sent. It then sends MSG.3 containing contention resolution information based on the resources indicated by the RAR. After receiving MSG.3, the network sends message 4 (MSG.4) containing contention resolution information. After receiving MSG.4, the UE confirms that the resolution information it sent in MSG.3 matches the contention resolution information it sent, completing the four-step random access procedure.

[0048] The network includes uplink grant (UL grant) information in the RAR to indicate the scheduling information of the MSG.3 Physical Uplink Shared Channel (PUSCH), and includes information such as the Random Access Preamble ID (RAPID), the Temporary Cell Radio Network Temporary Identity (TC-RNTI), and the Timing Advance (TA). If the network does not receive the MSG.3 PUSCH, it can schedule the retransmission of the MSG.3 PUSCH in the Physical Downlink Control Channel (PDCCH) scrambled by the TC-RNTI.

[0049] For the contention random access process, different UEs randomly select preambles for transmission. In this way, different UEs may select the same preamble to send on the same time-frequency radio resources (RACH opportunity (RO) resources). This situation can be understood as a UE preamble conflict. In this case, different UEs will receive the same RAR. At this time, different UEs will transmit MSG.3PUSCH according to the scheduling information in the RAR UL grant. The network decodes the PUSCH (including contention resolution information) sent by the UE on the MSG.3PUSCH scheduling resources, so the network will include the contention resolution information received in MSG.3 in MSG.4. If the contention resolution information in MSG.4 received by the UE matches the contention resolution information sent by the UE in MSG.3PUSCH, the UE considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0050] If the contention resolution is unsuccessful, the UE reselects RACH resources, performs physical random access channel (PRACH) transmission, and makes the next random access attempt.

[0051] In the two-step random access (2-step RACH) process, the first step is for the UE to send message A (MsgA) to the network. After receiving MsgA, the network sends message B (MsgB) to the UE. If the UE does not receive MsgB within a certain period of time, the UE will increment the counter that counts the number of times MsgA has been sent and resend MsgA. If the counter counts the number of times MsgA has been sent reaches a certain threshold, the UE will switch from the 2-step random access process to the 4-step random access process.

[0052] MsgA consists of the MsgA preamble and MsgA PUSCH parts. The preamble part is sent on the Ro used for 2-step RACH, and the PUSCH part is sent on the MsgA PUSCH resources associated with the MsgA preamble and Ro. MsgA PUSCH resources are a set of PUSCH resources configured for each PRACH time slot, including time-frequency resources and demodulation reference signal (DMRS) resources, and are associated with the PRACH resources within the PRACH slot.

[0053] To facilitate a better understanding of the embodiments of the present application, the duplex mode enhancement related to the present application is explained.

[0054] In 5G mobile communication systems, full-duplex technology has been enhanced to accommodate diverse scenarios and service requirements. Key 5G scenarios include enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC). These scenarios place high demands on the system for reliability, low latency, high bandwidth, and wide coverage.

[0055] In NR, configuring full-duplex operation can significantly improve the latency and coverage performance of time division duplex (TDD) systems. For example, subband non-overlapping full duplex reduces self-interference due to the non-overlapping uplink and downlink subbands, thus reducing transmission latency and enhancing coverage.

[0056] For a downlink time slot (DL slot), the network configures the downlink (DL) bandwidth part (Band Width Part, BWP) for the UE (configured by TDD uplink and downlink common configuration (tdd-UL-DL-ConfigurationCommon) or TDD uplink and downlink dedicated configuration (tdd-UL-DL-ConfigurationDedicated)), as shown in time slot 1 in Figure 2; for an uplink (UL) time slot, the network configures the UL BWP for the UE (configured by TDD uplink and downlink common configuration (tdd-UL-DL-ConfigurationCommon) or TDD uplink and downlink dedicated configuration (tdd-UL-DL-ConfigurationDedicated)), as shown in time slot 4 in Figure 3.

[0057] For a downlink timeslot (DL slot) (configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), in a full duplex scenario, as shown in Figure 2, there are the following cases:

[0058] Case 1: Configure DL BWP, such as slot 1;

[0059] Case 2: Configure DL BWP and uplink sub-band (UL sub-band), such as slot 2.

[0060] For an uplink timeslot (UL slot) (configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), in a full duplex scenario, as shown in Figure 3, there are the following cases:

[0061] Case 3: Configure UL BWP, such as slot 4;

[0062] Case 4: Configure UL BWP and downlink sub-band (DL sub-band), such as slot 5.

[0063] For sub-band full duplex (SBFD) operation, one SBFD sub-band consists of one resource block (RB) or a set of consecutive RBs with the same transmission direction.

[0064] The time unit (e.g., slot or symbol) in which the gNB uses SBFD operation may be referred to as an SBFD time unit (e.g., slot or symbol).

[0065] An exemplary duplex mode is: full-duplex on the network side, where uplink and downlink transmissions can occur simultaneously at different frequency domain locations at the same time. To avoid interference between uplink and downlink, a guard band (Guard Band) can be reserved between the frequency domain locations corresponding to different transmission directions (corresponding to duplex subbands); half-duplex on the terminal side, consistent with TDD, where only uplink or downlink transmissions can occur at the same time, not both. It is understandable that in this duplex mode, uplink and downlink transmissions on the network side at the same time can only be directed to different terminals.

[0066] Another exemplary duplex mode is: both the terminal side and the network side are full-duplex, as shown in Figure 4, that is, both the terminal side and the network side work in duplex mode. Specifically, for the terminal side and the network side, at the same time, uplink transmission (uplink, UL) and downlink transmission (downlink, DL) can be carried out simultaneously at different frequency domain positions.

[0067] For full-duplex at the UE side, a larger guard band (GB) (larger than the GB of the base station frequency division (FD)) may be required to suppress self-interference, as shown in FIG5 .

[0068] For a communication device, simultaneous UL reception and DL transmission can cause self-interference. To ensure transmission in the interfered direction, the communication device needs to have self-interference cancellation capabilities, such as reserving a guard band between the receive and transmit bands. However, this reduces UE throughput.

[0069] In order to facilitate a better understanding of the embodiments of the present application, the problems solved by the present application are explained.

[0070] At present, duplex enhancement in the 5G stage mainly considers connected UEs, and the network side supports full duplex, and the UE side supports half duplex.

[0071] In an embodiment of the present application, the duplex mode can be configured in an idle state or an inactive state, or dynamically configured during a random access phase, or configured in a connected state. Specifically, the duplex configuration can be determined based on the configuration of a random access uplink resource or a set of random access uplink resources. Random access uplink transmission can be performed in the duplex mode, thereby improving random access resource utilization and reducing random access uplink transmission latency.

[0072] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0073] FIG6 is a schematic flow chart of a method 200 for determining a duplex configuration according to an embodiment of the present application. As shown in FIG6 , the method 200 for determining a duplex configuration may include at least part of the following contents:

[0074] S210, the network side device sends random access configuration information to the terminal; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources; wherein the random access configuration information is associated with a duplex configuration;

[0075] S220, the terminal receives the random access configuration information from the network side device;

[0076] S230: The terminal determines a duplex configuration according to the random access configuration information.

[0077] It should be understood that FIG6 shows the steps or operations of the method 200 for determining a duplex configuration, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG6 .

[0078] In an embodiment of the present application, under the duplex configuration determined based on the random access configuration information, the terminal may support full-duplex or half-duplex, and the network-side device may support full-duplex or half-duplex. For example, the network-side device supports full-duplex, and the terminal supports full-duplex or half-duplex. For another example, the network-side device supports half-duplex, and the terminal supports half-duplex.

[0079] In an embodiment of the present application, the terminal can determine the duplex configuration based on the configuration of the random access uplink resource or the set of random access uplink resources. The duplex configuration is more flexible, and the duplex configuration is associated with the random access uplink resource. Random access uplink transmission can be performed in duplex mode, thereby improving the resource utilization of random access and reducing the delay of random access uplink transmission.

[0080] The duplex configuration described in the embodiments of the present application may also be referred to as at least one of the following: enhanced duplex configuration, enhanced duplex mode, cross duplex (XDD), enhanced full duplex, and enhanced full duplex mode. The embodiments of the present application are not limited thereto.

[0081] The duplex configuration described in the embodiments of the present application may refer to determining an uplink subband from a downlink time unit, or determining a downlink subband from an uplink time unit, thereby enabling downlink and uplink duplex transmission in a downlink time unit, or enabling downlink and uplink duplex transmission in an uplink time unit.

[0082] In some embodiments, the random access uplink resources configured by the random access configuration information include but are not limited to at least one of the following: uplink data shared channel resources in random access, and PRACH resources in random access.

[0083] Optionally, the random access uplink resources configured by the random access configuration information include but are not limited to at least one of the following: MsgA PUSCH resources, MsgAPRACH resources, Msg.3PUSCH resources, Msg.3PRACH resources, Msg.1 PUSCH resources, and Msg.1 PRACH resources.

[0084] Exemplarily, the uplink data sharing channel resources in random access may include but are not limited to at least one of the following: time-frequency resources of the uplink data sharing channel in random access, DMRS sequence of the uplink data sharing channel in random access, and DMRS port of the uplink data sharing channel in random access.

[0085] For example, the MsgAPUSCH resources may include but are not limited to at least one of the following: a time-frequency resource of an MsgAPUSCH, a DMRS sequence of an MsgAPUSCH, and a DMRS port of an MsgAPUSCH.

[0086] For example, the Msg.3PUSCH resources may include but are not limited to at least one of the following: the time-frequency resources of the Msg.3PUSCH, the DMRS sequence of the Msg.3PUSCH, and the DMRS port of the Msg.3PUSCH.

[0087] For example, the Msg.1 PUSCH resources may include but are not limited to at least one of the following: the time-frequency resources of the Msg.1 PUSCH, the DMRS sequence of the Msg.1 PUSCH, and the DMRS port of the Msg.1 PUSCH.

[0088] The association relationship described in the embodiment of the present application can also be called a mapping relationship, which can be an equal relationship between two signals or channel resources in a certain sense.

[0089] The MsgA PUSCH resource or MsgA PRACH resource described in the embodiments of the present application may also be referred to as MsgA resource or MsgA.

[0090] The MsgA PUSCH resource group or MsgA PRACH resource group described in the embodiments of the present application may also be referred to as an MsgA resource group or an MsgA group.

[0091] In an embodiment of the present application, the random access uplink resource configured by the random access configuration information may include: a random access uplink resource directly configured by the random access configuration information, or a random access uplink resource in a set of random access uplink resources configured by the random access configuration information.

[0092] In the embodiment of the present application, the random access uplink resources configured by the random access configuration information can be used in the idle state or the inactive state. That is, the present embodiment can support duplex configuration in the idle state or the inactive state, thereby improving resource utilization efficiency in the idle state or the inactive state.

[0093] In some embodiments, the random access configuration information can be configured in an idle state or an inactive state, or the random access configuration information can be dynamically configured during the random access phase. In other words, embodiments of the present application can obtain the duplex configuration in an idle state or an inactive state or during the random access phase, making the duplex configuration more flexible and eliminating the need for additional duplex configuration signaling.

[0094] In some embodiments, the random access configuration information can also be configured in a connected state. In other words, the embodiments of the present application can obtain the duplex configuration in a connected state, which is more flexible and does not require the introduction of additional duplex configuration signaling.

[0095] In some embodiments, the above S230 may specifically include:

[0096] The terminal determines, according to the random access uplink resource in at least one downlink time unit, an uplink subband in the at least one downlink time unit;

[0097] The random access uplink resources on the at least one downlink time unit include at least one of the following: part or all of the random access uplink resources configured by the random access configuration information, and part or all of the random access uplink resources in the set of random access uplink resources configured by the random access configuration information.

[0098] This embodiment clarifies that the uplink subband on at least one downlink time unit can be determined based on the random access uplink resources on at least one downlink time unit. After the uplink subband on the at least one downlink time unit is determined, the duplex configuration on the at least one downlink time unit can be known.

[0099] In some embodiments, the downlink time unit may include but is not limited to at least one of the following: orthogonal frequency-division multiplexing (OFDM) symbol, time slot, subframe, frame, microsecond, millisecond, second, minute, hour, day, week, month.

[0100] For example, taking the random access uplink resource as the MsgA PUSCH resource and the downlink time unit as the downlink time slot (DL slot) as an example, the terminal can determine the uplink subband (uplink subband) in the downlink time slot through the MsgA PUSCH resource in the downlink time slot.

[0101] For another specific example, taking the random access uplink resource as MsgA PUSCH resource or MsgAPRACH resource and the downlink time unit as a downlink time slot (DL slot) as an example, the terminal can determine the uplink subband (uplink subband) in the downlink time slot through the MsgA PUSCH resource or MsgAPRACH resource in the downlink time slot.

[0102] In some embodiments, the terminal determines that part or all of the physical resource blocks (PRBs) occupied by the random access uplink resources on the at least one downlink time unit are uplink subbands, wherein the random access uplink resources on the at least one downlink time unit are valid.

[0103] Exemplarily, the random access uplink resource on at least one downlink time unit is valid, which can be understood as: satisfying a mapping relationship between a PRACH and the random access uplink resource on at least one downlink time unit.

[0104] For example, taking the random access uplink resource as the MsgA PUSCH resource and the downlink time unit as the downlink time slot (DL slot) as an example, in all downlink time slots where the MsgA PUSCH resource appears, the PRB occupied by the MsgA PUSCH resource is considered to be configured as an uplink subband (uplink subband), and the MsgA PUSCH resource is considered to be valid.

[0105] Specifically, for example, taking the random access uplink resource as the MsgA PUSCH resource or the MsgAPRACH resource, and the downlink time unit as the downlink time slot (DL slot) as an example, in all downlink time slots where the MsgA PUSCH resource or the MsgAPRACH resource appears, the PRB occupied by the MsgA PUSCH resource or the MsgAPRACH resource is considered to be configured as an uplink subband (uplink subband), and the MsgA PUSCH resource or the MsgAPRACH resource is considered to be valid.

[0106] For example, taking the random access uplink resource as the MsgA PUSCH resource and the downlink time unit as the downlink time slot (DL slot) as an example, as shown in Figure 7, in the downlink time slot n, part of the PRBs occupied by the MsgA PUSCH resource (PRBs excluding the guard interval) is considered to be configured as an uplink subband, and the MsgA PUSCH resource is considered to be valid.

[0107] In some embodiments, in each downlink time unit of at least one downlink time unit, part or all of the bandwidth occupied by at least one random access uplink resource adjacent to the uplink subband is used as a guard interval. Specifically, the setting of the guard interval can suppress self-interference caused by simultaneous reception and transmission.

[0108] For example, taking the random access uplink resource as MsgA PUSCH resource and the downlink time unit as a downlink time slot (DL slot), as shown in FIG7 , in downlink time slot n, the entire bandwidth occupied by a MsgA PUSCH resource adjacent to the uplink subband is the guard interval.

[0109] For example, taking the random access uplink resource as MsgA PUSCH resource and the downlink time unit as a downlink time slot (DL slot), as shown in FIG8 , in downlink time slot n, part of the bandwidth occupied by an MsgA PUSCH resource adjacent to the uplink subband is the guard interval.

[0110] In some embodiments, the above S230 may specifically include:

[0111] The terminal determines, according to the random access uplink resource in at least one uplink time unit, a downlink subband in the at least one uplink time unit;

[0112] The random access uplink resources on the at least one uplink time unit include at least one of the following: part or all of the random access uplink resources configured by the random access configuration information, and part or all of the random access uplink resources in the set of random access uplink resources configured by the random access configuration information.

[0113] This embodiment clarifies that the downlink subband on at least one uplink time unit can be determined based on the random access uplink resources on at least one uplink time unit. After the downlink subband on the at least one uplink time unit is determined, the duplex configuration on the at least one uplink time unit can be known.

[0114] In some embodiments, the uplink time unit may include but is not limited to at least one of the following: OFDM symbol, time slot, subframe, frame, microsecond, millisecond, second, minute, hour, day, week, month.

[0115] In some embodiments, the terminal determines part or all of the PRBs other than the PRBs occupied by the random access uplink resources on the at least one uplink time unit as downlink subbands, wherein the random access uplink resources on the at least one uplink time unit are valid.

[0116] In some embodiments, in each uplink time unit of the at least one uplink time unit, part or all of the bandwidth occupied by at least one random access uplink resource adjacent to the downlink subband is used as a guard interval. Specifically, the setting of the guard interval can suppress self-interference caused by simultaneous reception and transmission.

[0117] Exemplarily, the random access uplink resource on at least one uplink time unit is valid, which can be understood as: satisfying a mapping relationship between a PRACH and the random access uplink resource on at least one uplink time unit.

[0118] In some embodiments, the at least one random access uplink resource satisfies at least one of the following:

[0119] Satisfies the mapping relationship between PRACH and random access uplink resources and is not used to perform random access uplink transmission;

[0120] Satisfy the mapping relationship between PRACH and random access uplink resources, and is not used to perform random access uplink transmission when preset conditions are met;

[0121] The mapping relationship between PRACH and random access uplink resources is not satisfied.

[0122] Specifically, this embodiment clarifies the conditions that must be met by at least one random access uplink resource where the guard interval is located, which is conducive to better utilization of random access uplink resources.

[0123] It should be noted that random access uplink resources that satisfy the mapping relationship from PRACH to random access uplink resources can be considered valid; random access uplink resources that do not satisfy the mapping relationship from PRACH to random access uplink resources can be considered invalid.

[0124] For example, the random access uplink resource is an MsgA PUSCH resource, and the mapping relationship between the PRACH and the random access uplink resource may be: a mapping relationship between the PRACH and the MsgA PUSCH resource.

[0125] For another example, the random access uplink resource is a MsgAPRACH resource, and the mapping relationship between PRACH and the random access uplink resource may be: a mapping relationship between PRACH and MsgAPRACH resources.

[0126] For another example, the random access uplink resource is a MsgA PUSCH resource or a MsgAPRACH resource, and the mapping relationship between PRACH and the random access uplink resource may be a mapping relationship between PRACH and a MsgA PUSCH resource or a MsgAPRACH resource.

[0127] For another example, the random access uplink resource is a Msg.3PUSCH resource, and the mapping relationship between PRACH and the random access uplink resource may be: a mapping relationship between PRACH and Msg.3PUSCH resource.

[0128] For another example, the random access uplink resource is a Msg.3PRACH resource, and the mapping relationship between PRACH and the random access uplink resource may be: a mapping relationship between PRACH and Msg.3PRACH resource.

[0129] For another example, the random access uplink resource is a Msg.3PUSCH resource or a Msg.3PRACH resource, and the mapping relationship between PRACH and the random access uplink resource may be: a mapping relationship between PRACH and a Msg.3PUSCH resource or a Msg.3PRACH resource.

[0130] For another example, the random access uplink resource is a Msg.1 PUSCH resource, and the mapping relationship between the PRACH and the random access uplink resource may be: a mapping relationship between the PRACH and the Msg.1 PUSCH resource.

[0131] For another example, the random access uplink resource is a Msg.1 PRACH resource, and the mapping relationship between PRACH and the random access uplink resource may be: a mapping relationship between PRACH and Msg.1 PRACH resource.

[0132] For another example, the random access uplink resource is a Msg.1 PUSCH resource or a Msg.1 PRACH resource, and the mapping relationship between PRACH and the random access uplink resource may be a mapping relationship between PRACH and a Msg.1 PUSCH resource or a Msg.1 PRACH resource.

[0133] In some embodiments, the preset condition includes but is not limited to at least one of the following:

[0134] The time domain or frequency domain interval between the random access uplink resource and the reference signal is less than or not greater than a first threshold;

[0135] There is a reference signal transmission in the remaining bandwidth outside the uplink subband;

[0136] A downlink common channel or a downlink common signal is transmitted in the remaining bandwidth outside the uplink sub-band;

[0137] There is reception of a reference signal in the remaining bandwidth outside the uplink sub-band;

[0138] A downlink common channel or a downlink common signal is received in the remaining bandwidth outside the uplink sub-band.

[0139] For example, when a preset condition is met, random access uplink transmission is not performed, thereby avoiding interference of random access uplink transmission on transmission of reference signals or downlink common channels or downlink common signals.

[0140] Exemplarily, taking the random access uplink resource as MsgA PUSCH resource and the downlink time unit as a downlink time slot (DL slot) as an example, as shown in FIG7 or FIG8 , the remaining bandwidth outside the uplink subband may include the bandwidth occupied by the guard interval and the downlink subband.

[0141] Optionally, the first threshold may be agreed upon by a protocol, or the first threshold may be configured by a network-side device.

[0142] In some embodiments, the preset condition is pre-configured by a network side instruction, or the preset condition is agreed upon by a protocol.

[0143] In some embodiments, the random access configuration information is further used to configure a guard interval on the at least one downlink time unit or the at least one uplink time unit. Specifically, the setting of the guard interval can suppress self-interference caused by simultaneous reception and transmission.

[0144] The reference signal described in the embodiments of the present application includes but is not limited to at least one of the following:

[0145] Synchronization Signal Block (SSB), Channel State Information Reference Signal (CSI-RS), MsgA, MsgA PUSCH, PRACH, Tracking Reference Signal (TRS) (TRS is a reference signal used for time-frequency resource estimation), Sounding Reference Signal (SRS).

[0146] The SSB described in the embodiment of the present application can also be called a resource block, which includes at least one of a synchronization signal, a broadcast signal, a broadcast channel (PBCH), and other system messages.

[0147] In an embodiment of the present application, in support of enhanced duplex mode, random access uplink resources may be allowed on an uplink subband of an additionally configured downlink time unit, so a new type of random access uplink resource may appear.

[0148] In some embodiments, the random access uplink resource configured by the random access configuration information includes at least one of the following types:

[0149] Random access uplink resources existing in uplink time units;

[0150] Random access uplink resources exist in time units with flexible symbols;

[0151] Random access uplink resources present in the uplink subband of the downlink time unit;

[0152] Random access uplink resources existing in an uplink subband of a downlink time unit, and no reference signal resources existing in the downlink time unit;

[0153] A random access uplink resource existing in an uplink subband of a downlink time unit, and a reference signal resource existing in the downlink time unit;

[0154] Random access uplink resources that are not in the uplink subband of the downlink time unit.

[0155] For example, taking the random access uplink resource as a MsgA PUSCH resource or a MsgAPRACH resource, the time unit as a time slot, and the reference signal as an SSB as an example, the random access uplink resource configured by the random access configuration information includes at least one of the following types:

[0156] MsgA PUSCH resources or MsgAPRACH resources present in the uplink timeslot;

[0157] MsgA PUSCH resources or MsgAPRACH resources present in time slots with flexible symbols;

[0158] MsgA PUSCH resources or MsgAPRACH resources present in the uplink subband of the downlink timeslot;

[0159] MsgA PUSCH resources or MsgAPRACH resources exist in the uplink subband of the downlink timeslot, and there are no SSB resources in the downlink timeslot;

[0160] MsgA PUSCH resources or MsgAPRACH resources present in the uplink subband of a downlink timeslot, and SSB resources present in the downlink timeslot;

[0161] MsgA PUSCH resources or MsgAPRACH resources that are not on the uplink subband of the downlink timeslot.

[0162] In some embodiments, the uplink time unit may include but is not limited to at least one of the following: OFDM symbol, time slot, subframe, frame, microsecond, millisecond, second, minute, hour, day, week, month.

[0163] In some embodiments, the set of random access uplink resources configured by the random access configuration information satisfies at least one of the following:

[0164] Including different types of random access uplink resources;

[0165] Including random access uplink resources of the same type;

[0166] Mapped to the same PRACH resource;

[0167] Mapped to different PRACH resources.

[0168] This embodiment clarifies the type of random access uplink resources in the set of random access uplink resources configured by the random access configuration information and the PRACH resources to which the set of random access uplink resources is mapped, so that the set of random access uplink resources can be configured more flexibly.

[0169] In some embodiments, the set of random access uplink resources configured by the random access configuration information is used to perform random access uplink repeated transmission. Optionally, the set of random access uplink resources configured by the random access configuration information is used for repeated transmission during a random access initial transmission, or the set of random access uplink resources configured by the random access configuration information is used for repeated transmission during a random access retransmission.

[0170] For example, taking the random access uplink resource as the MsgA PUSCH resource as an example, the set of MsgA PUSCH resources configured by the random access configuration information is used for repeated transmission of MsgA or MsgA PUSCH in the random access initial transmission process, or the set of MsgA PUSCH resources configured by the random access configuration information is used for repeated transmission of MsgA or MsgA PUSCH in the random access retransmission process.

[0171] For example, taking the random access uplink resource as an MsgA PRACH resource as an example, the set of MsgA PRACH resources configured by the random access configuration information is used for repeated transmission of MsgA or MsgA PRACH in the random access initial transmission process, or the set of MsgA PRACH resources configured by the random access configuration information is used for repeated transmission of MsgA or MsgA PRACH in the random access retransmission process.

[0172] For example, taking the random access uplink resource as an MsgA PUSCH resource or an MsgA PRACH resource as an example, the set of MsgA PUSCH resources or MsgA PRACH resources configured by the random access configuration information is used for repeated transmission of MsgA or MsgA PUSCH or MsgA PRACH in the random access initial transmission process, or the set of MsgA PRACH resources configured by the random access configuration information is used for repeated transmission of MsgA or MsgA PUSCH or MsgA PRACH in the random access retransmission process.

[0173] It should be noted that repeated transmission of MsgA or MsgA PUSCH refers to repeated transmission during each initial transmission or retransmission of MsgA or MsgA PUSCH.

[0174] In some embodiments, the random access configuration information is public configuration information, wherein the public configuration information is used to configure random access uplink resources on an uplink subband and random access uplink resources on a non-uplink subband, or the public configuration information is used to configure a set of random access uplink resources on an uplink subband and a set of random access uplink resources on a non-uplink subband. For example, the random access uplink resources on a non-uplink subband may be random access uplink resources on an uplink time unit. For another example, the random access uplink resources on a non-uplink subband may be random access uplink resources on a time unit containing flexible symbols.

[0175] For example, taking the random access uplink resource as an MsgA PUSCH resource or an MsgA PRACH resource as an example, the random access configuration information is a common MsgA resource configuration. Specifically, the same MsgA resource configuration (i.e., the common MsgA resource configuration) is used to configure two possible types of MsgA PUSCH resources or MsgA PRACH resources, namely: MsgA PUSCH resources or MsgA PRACH resources on a UL subband and MsgA PUSCH resources or MsgA PRACH resources on a non-UL subband.

[0176] In some embodiments, the random access configuration information is two independent configuration information, wherein the two independent configuration information are used to configure the random access uplink resources on the uplink subband and the random access uplink resources on the non-uplink subband, respectively, or the two independent configuration information are used to configure the set of random access uplink resources on the uplink subband and the set of random access uplink resources on the non-uplink subband, respectively. For example, the random access uplink resources on the non-uplink subband may be random access uplink resources on an uplink time unit. For another example, the random access uplink resources on the non-uplink subband may be random access uplink resources on a time unit containing flexible symbols.

[0177] For example, if the random access uplink resource is a MsgA PUSCH resource or a MsgA PRACH resource, the random access configuration information is two independent MsgA resource configurations. Specifically, one MsgA resource configuration is used to configure the MsgA PUSCH resource or MsgA PRACH resource on the UL subband, and another MsgA resource configuration is used to configure the MsgA PUSCH resource or MsgA PRACH resource on a non-UL subband.

[0178] In some embodiments, the association relationship between the random access uplink resource configured by the random access configuration information and the PRACH satisfies at least one of the following:

[0179] At least two different random access uplink resources are independently associated with the PRACH;

[0180] At least two different types of random access uplink resources are independently associated with the PRACH;

[0181] At least two different random access uplink resources are associated with the PRACH;

[0182] At least two different types of random access uplink resources are associated with the PRACH;

[0183] Different random access uplink resources are independently associated with different PRACHs;

[0184] Different types of random access uplink resources are independently associated with different types of PRACH;

[0185] Different random access uplink resources are associated with different PRACHs;

[0186] Different types of random access uplink resources are associated with different types of PRACH;

[0187] The random access uplink resource is not associated with the PRACH that overlaps with it in the time domain.

[0188] Exemplarily, taking the random access uplink resource as an MsgA PUSCH resource as an example, at least two different random access uplink resources are independently associated with PRACH, for example, as follows: MsgA PUSCH resource 1 is associated with PRACH 0, MsgA PUSCH resource 2 is associated with PRACH 1, MsgA PUSCH resource 3 is associated with PRACH 0, and MsgA PUSCH resource 4 is associated with PRACH 1. In this example, one PRACH (such as MsgA PRACH) may be associated with at least two MsgA PUSCH resources as soon as possible, for example, some MsgA PUSCH resources are on the uplink subband (UL subband) and some MsgA PUSCH resources are in the normal uplink bandwidth (UL band). In this way, a group of MsgA PUSCH resources that are more compact in time and associated with the same PRACH can be selected, which is conducive to completing multiple MsgA PUSCH transmissions / repetitions with low latency.

[0189] Exemplarily, taking the random access uplink resource as an MsgA PUSCH resource as an example, at least two different types of random access uplink resources are independently associated with PRACH (such as MsgAPRACH), for example, as follows: the MsgA PUSCH resource configured on the uplink subband of the downlink slot and the uplink MsgA PUSCH resource on the uplink slot or flexible slot are independently associated with the MsgA PRACH resource.

[0190] Exemplarily, taking the random access uplink resource as the MsgA PUSCH resource as an example, at least two different types of random access uplink resources are independently associated with PRACH, for example, as follows: the MsgA PUSCH resource existing in the time slot with flexible symbols is associated with PRACH 0, the MsgA PUSCH resource existing in the uplink subband of the downlink time slot is associated with PRACH 1, and the MsgA PUSCH resource not in the uplink subband of the downlink time slot is associated with PRACH 3; for example, the MsgA PUSCH resource existing in the time slot with flexible symbols is associated with the odd-numbered PRACH, and the MsgA PUSCH resource existing in the uplink subband of the downlink time slot is associated with the even-numbered PRACH. In this example, a PRACH (such as MsgA PRACH) may be associated with at least two different types of MsgA PUSCH resources as soon as possible. For example, some MsgA PUSCH resources are on the uplink subband (UL subband) and some MsgA PUSCH resources are in the normal uplink bandwidth (UL band). In this way, a group of MsgA PUSCH resources that are more compact in time and associated with the same PRACH (such as MsgA PRACH) can be selected, which is conducive to completing multiple MsgA PUSCH transmissions / repetitions with low latency.

[0191] For example, taking the random access uplink resource as an MsgA PUSCH resource, at least two different random access uplink resources are associated with a PRACH (e.g., MsgAPRACH) together. For example, the following can be performed: relative to the MsgA PRACH resource, the MsgA PUSCH resource is configured, some MsgA PUSCHs are on the uplink subband of the downlink slot, and some MsgA PUSCH resources are in the normal uplink slot or the flexible slot. The PRACH (e.g., MsgAPRACH) and MsgA PUSCH association is performed in a certain order, without distinguishing which slot the MsgA PUSCH is in. The association complexity of the MsgA PRACH to the MsgA PUSCH resource can be reduced, and there is no need to distinguish between different types of MsgA PUSCH resources.

[0192] For example, taking the random access uplink resource as MsgA PUSCH resource, different random access uplink resources are independently associated with different PRACHs (such as MsgAPRACH). In this case, mapping is performed only between the MsgA PUSCH resource and the MsgA PRACH in the same MsgA.

[0193] For example, taking the random access uplink resource as MsgA PUSCH resource, different types of random access uplink resources are independently associated with different types of PRACH (such as MsgAPRACH). In this case, mapping is performed only between MsgA PUSCH resources and MsgA PRACH in the same type of MsgA.

[0194] For example, taking the random access uplink resource as MsgA PUSCH resource, different random access uplink resources are associated with different PRACHs (such as MsgAPRACH). In this case, the MsgA PUSCH resource in a certain MsgA can be mapped with the MsgA PRACH resource in another MsgA.

[0195] For example, taking the random access uplink resource as MsgA PUSCH resource, different types of random access uplink resources are associated with different types of PRACH (such as MsgAPRACH). In this case, the MsgA PUSCH resource in a certain type of MsgA can be mapped with the MsgA PRACH resource in another type of MsgA.

[0196] For example, taking the random access uplink resource as an MsgA PUSCH resource as an example, the random access uplink resource is not associated with the PRACH that overlaps with it in the time domain. For example, it can be as follows: If the MsgA PUSCH resource overlaps with a PRACH (such as MsgAPRACH) in the time domain, the MsgA PUSCH resource and the PRACH are not associated. For example, if a PRACH (such as MsgAPRACH) appears in the same OFDM symbol as an MsgA PUSCH resource on a subband, the MsgA PUSCH resource can be considered invalid. This can reduce interference with the PRACH (such as MsgAPRACH).

[0197] Therefore, in an embodiment of the present application, the terminal can determine the duplex configuration based on the configuration of the random access uplink resource or the set of random access uplink resources, without the need for separate signaling for duplex configuration. The duplex configuration is associated with the random access uplink resource, and random access uplink transmission can be performed in duplex mode, thereby improving the resource utilization of random access and reducing the delay of random access uplink transmission.

[0198] In an embodiment of the present application, flexible duplex configuration, random access uplink resource determination, and PRACH to random access uplink resource mapping can be supported in idle state (Idle) / deactivated state (Inactive), thereby reducing the delay of random access uplink transmission, and dynamically determining random access uplink resources based on random access configuration information, which can improve resource utilization to a greater extent.

[0199] The duplex configuration determination method provided in the embodiments of the present application may be performed by a duplex configuration determination device, or a processing unit within the duplex configuration determination device that is configured to perform the duplex configuration determination method. The duplex configuration determination device provided in the embodiments of the present application is described by taking the duplex configuration determination device performing the duplex configuration determination method as an example.

[0200] FIG9 shows a schematic block diagram of a device 300 for determining a duplex configuration according to an embodiment of the present application. As shown in FIG9 , the device 300 for determining a duplex configuration includes:

[0201] The transceiver unit 310 is configured to receive random access configuration information from a network-side device; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources;

[0202] The processing unit 320 is configured to determine a duplex configuration according to the random access configuration information.

[0203] In some embodiments, the processing unit 320 is specifically configured to:

[0204] determining an uplink subband on the at least one downlink time unit according to a random access uplink resource on the at least one downlink time unit;

[0205] The random access uplink resources on the at least one downlink time unit include at least one of the following: part or all of the random access uplink resources configured by the random access configuration information, and part or all of the random access uplink resources in the set of random access uplink resources configured by the random access configuration information.

[0206] In some embodiments, the processing unit 320 is specifically configured to:

[0207] Determine part or all of the physical resource blocks (PRBs) occupied by the random access uplink resources on the at least one downlink time unit as uplink subbands, wherein the random access uplink resources on the at least one downlink time unit are valid.

[0208] In some embodiments, in each downlink time unit of the at least one downlink time unit, part or all of the bandwidth occupied by at least one random access uplink resource adjacent to the uplink subband is a guard interval.

[0209] In some embodiments, the at least one random access uplink resource satisfies at least one of the following:

[0210] Satisfies the mapping relationship between the physical random access channel PRACH and the random access uplink resource, and is not used to perform random access uplink transmission;

[0211] Satisfy the mapping relationship between PRACH and random access uplink resources, and is not used to perform random access uplink transmission when preset conditions are met;

[0212] The mapping relationship between PRACH and random access uplink resources is not satisfied.

[0213] In some embodiments, the preset condition includes at least one of the following:

[0214] The time domain or frequency domain interval between the random access uplink resource and the reference signal is less than or not greater than a first threshold;

[0215] There is a reference signal transmission in the remaining bandwidth outside the uplink sub-band;

[0216] A downlink common channel or a downlink common signal is transmitted in the remaining bandwidth outside the uplink sub-band;

[0217] There is reception of a reference signal in the remaining bandwidth outside the uplink sub-band;

[0218] A downlink common channel or a downlink common signal is received in the remaining bandwidth outside the uplink sub-band.

[0219] In some embodiments, the random access configuration information is further used to configure a guard interval on the at least one downlink time unit.

[0220] In some embodiments, the random access uplink resource configured by the random access configuration information includes at least one of the following types:

[0221] Random access uplink resources existing in uplink time units;

[0222] Random access uplink resources that exist in time units with flexible symbols;

[0223] Random access uplink resources present in the uplink subband of the downlink time unit;

[0224] A random access uplink resource existing on an uplink subband of a downlink time unit, and no reference signal resource existing on the downlink time unit;

[0225] A random access uplink resource existing on an uplink subband of a downlink time unit, and a reference signal resource existing on the downlink time unit;

[0226] Random access uplink resources that are not in the uplink subband of the downlink time unit.

[0227] In some embodiments, the set of random access uplink resources configured by the random access configuration information satisfies at least one of the following:

[0228] Including different types of random access uplink resources;

[0229] Including random access uplink resources of the same type;

[0230] Mapped to the same PRACH resource;

[0231] Mapped to different PRACH resources.

[0232] In some embodiments, the set of random access uplink resources configured by the random access configuration information is used to perform random access uplink repeated transmission.

[0233] In some embodiments, the association relationship between the random access uplink resource configured by the random access configuration information and the PRACH satisfies at least one of the following:

[0234] At least two different random access uplink resources are independently associated with the PRACH;

[0235] At least two different types of random access uplink resources are independently associated with the PRACH;

[0236] At least two different random access uplink resources are associated with the PRACH;

[0237] At least two different types of random access uplink resources are associated with the PRACH;

[0238] Different random access uplink resources are independently associated with different PRACHs;

[0239] Different types of random access uplink resources are independently associated with different types of PRACH;

[0240] Different random access uplink resources are associated with different PRACHs;

[0241] Different types of random access uplink resources are associated with different types of PRACH;

[0242] The random access uplink resource is not associated with the PRACH that overlaps with it in the time domain.

[0243] In some embodiments, the random access configuration information is common configuration information, wherein the common configuration information is used to configure random access uplink resources on an uplink subband and random access uplink resources on a non-uplink subband, or the common configuration information is used to configure a set of random access uplink resources on an uplink subband and a set of random access uplink resources on a non-uplink subband; or,

[0244] The random access configuration information is two independent configuration information, wherein the two independent configuration information are respectively used to configure the random access uplink resources on the uplink subband and the random access uplink resources on the non-uplink subband, or the two independent configuration information are respectively used to configure the set of random access uplink resources on the uplink subband and the set of random access uplink resources on the non-uplink subband.

[0245] In some embodiments, the random access uplink resource configured by the random access configuration information includes at least one of the following:

[0246] Uplink data shared channel resources in random access, PRACH resources in random access.

[0247] In some embodiments, the transceiver unit 310 may be a communication interface or transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit 320 may be embedded in or independent of a processor of the terminal in the form of hardware.

[0248] It should be understood that the device 300 for determining the duplex configuration according to the embodiment of the present application may correspond to the terminal in the method embodiment of the present application, and the various units in the device 300 for determining the duplex configuration are respectively for implementing the corresponding processes of the terminal in the method 200 shown in Figure 6. For the sake of brevity, they will not be repeated here.

[0249] Therefore, in an embodiment of the present application, the terminal can determine the duplex configuration based on the configuration of the random access uplink resource or the set of random access uplink resources. The duplex configuration is more flexible, and the duplex configuration is associated with the random access uplink resource. It can flexibly perform random access uplink transmission in duplex mode, thereby improving the resource utilization of random access and reducing the delay of random access uplink transmission.

[0250] FIG10 shows a schematic block diagram of a device 400 for determining a duplex configuration according to an embodiment of the present application. As shown in FIG10 , the device 400 for determining a duplex configuration includes:

[0251] The transceiver unit 410 is configured to send random access configuration information to the terminal; wherein the random access configuration information is used to configure at least one of the following: random access uplink resources, a set of random access uplink resources; wherein the random access configuration information is associated with a duplex configuration.

[0252] In some embodiments, the random access configuration information is associated with a duplex configuration, including:

[0253] The random access uplink resource on at least one downlink time unit is associated with the uplink subband on the at least one downlink time unit;

[0254] The random access uplink resources on the at least one downlink time unit include at least one of the following: part or all of the random access uplink resources configured by the random access configuration information, and part or all of the random access uplink resources in the set of random access uplink resources configured by the random access configuration information.

[0255] In some embodiments, the random access uplink resource on the at least one downlink time unit is associated with the uplink subband on the at least one downlink time unit, including:

[0256] Part or all of the physical resource blocks (PRBs) occupied by the random access uplink resources on the at least one downlink time unit are uplink subbands, wherein the random access uplink resources on the at least one downlink time unit are valid.

[0257] In some embodiments, in each downlink time unit of the at least one downlink time unit, part or all of the bandwidth occupied by at least one random access uplink resource adjacent to the uplink subband is a guard interval.

[0258] In some embodiments, the at least one random access uplink resource satisfies at least one of the following:

[0259] Satisfies the mapping relationship between the physical random access channel PRACH and the random access uplink resource, and is not used to perform random access uplink transmission;

[0260] Satisfy the mapping relationship between PRACH and random access uplink resources, and is not used to perform random access uplink transmission when preset conditions are met;

[0261] The mapping relationship between PRACH and random access uplink resources is not satisfied.

[0262] In some embodiments, the preset condition includes at least one of the following:

[0263] The time domain or frequency domain interval between the random access uplink resource and the reference signal is less than or not greater than a first threshold;

[0264] There is a reference signal transmission in the remaining bandwidth outside the uplink sub-band;

[0265] A downlink common channel or a downlink common signal is transmitted in the remaining bandwidth outside the uplink sub-band;

[0266] There is reception of a reference signal in the remaining bandwidth outside the uplink sub-band;

[0267] A downlink common channel or a downlink common signal is received in the remaining bandwidth outside the uplink sub-band.

[0268] In some embodiments, the random access configuration information is further used to configure a guard interval on the at least one downlink time unit.

[0269] In some embodiments, the random access uplink resource configured by the random access configuration information includes at least one of the following types:

[0270] Random access uplink resources existing in uplink time units;

[0271] Random access uplink resources that exist in time units with flexible symbols;

[0272] Random access uplink resources present in the uplink subband of the downlink time unit;

[0273] A random access uplink resource existing on an uplink subband of a downlink time unit, and no reference signal resource existing on the downlink time unit;

[0274] A random access uplink resource existing on an uplink subband of a downlink time unit, and a reference signal resource existing on the downlink time unit;

[0275] Random access uplink resources that are not in the uplink subband of the downlink time unit.

[0276] In some embodiments, the set of random access uplink resources configured by the random access configuration information satisfies at least one of the following:

[0277] Including different types of random access uplink resources;

[0278] Including random access uplink resources of the same type;

[0279] Mapped to the same PRACH resource;

[0280] Mapped to different PRACH resources.

[0281] In some embodiments, the set of random access uplink resources configured by the random access configuration information is used to perform random access uplink repeated transmission.

[0282] In some embodiments, the association relationship between the random access uplink resource configured by the random access configuration information and the PRACH satisfies at least one of the following:

[0283] At least two different random access uplink resources are independently associated with the PRACH;

[0284] At least two different types of random access uplink resources are independently associated with the PRACH;

[0285] At least two different random access uplink resources are associated with the PRACH;

[0286] At least two different types of random access uplink resources are associated with the PRACH;

[0287] Different random access uplink resources are independently associated with different PRACHs;

[0288] Different types of random access uplink resources are independently associated with different types of PRACH;

[0289] Different random access uplink resources are associated with different PRACHs;

[0290] Different types of random access uplink resources are associated with different types of PRACH;

[0291] The random access uplink resource is not associated with the PRACH that overlaps with it in the time domain.

[0292] In some embodiments, the random access configuration information is common configuration information, wherein the common configuration information is used to configure random access uplink resources on an uplink subband and random access uplink resources on a non-uplink subband, or the common configuration information is used to configure a set of random access uplink resources on an uplink subband and a set of random access uplink resources on a non-uplink subband; or,

[0293] The random access configuration information is two independent configuration information, wherein the two independent configuration information are respectively used to configure the random access uplink resources on the uplink subband and the random access uplink resources on the non-uplink subband, or the two independent configuration information are respectively used to configure the set of random access uplink resources on the uplink subband and the set of random access uplink resources on the non-uplink subband.

[0294] In some embodiments, the random access uplink resource configured by the random access configuration information includes at least one of the following:

[0295] Uplink data shared channel resources in random access, PRACH resources in random access.

[0296] In some embodiments, the transceiver unit 410 may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.

[0297] It should be understood that the device 400 for determining the duplex configuration according to the embodiment of the present application may correspond to the network side device in the method embodiment of the present application, and the various units in the device 400 for determining the duplex configuration are respectively for implementing the corresponding processes of the network side device in the method 200 shown in Figure 6. For the sake of brevity, they will not be repeated here.

[0298] Therefore, in an embodiment of the present application, the terminal can determine the duplex configuration based on the configuration of the random access uplink resource or the set of random access uplink resources. The duplex configuration is more flexible, and the duplex configuration is associated with the random access uplink resource. It can flexibly perform random access uplink transmission in duplex mode, thereby improving the resource utilization of random access and reducing the delay of random access uplink transmission.

[0299] The device for determining the duplex configuration in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or a network-side device, or can be a device other than a terminal or a network-side device. For example, the terminal can include but is not limited to the types of the terminal 11 listed above, the network-side device can include but is not limited to the types of the network-side device 12 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiment of the present application.

[0300] The device for determining the duplex configuration provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0301] As shown in Figure 11, an embodiment of the present application further provides a communication device 500, including a processor 501 and a memory 502, wherein the memory 502 stores a program or instruction that can be run on the processor 501. For example, when the communication device 500 is a terminal, when the program or instruction is executed by the processor 501, it implements the various steps performed by the terminal in the embodiment of the method for determining the duplex configuration described above, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 500 is a network-side device, when the program or instruction is executed by the processor 501, it implements the various steps performed by the network-side device in the embodiment of the method for determining the duplex configuration described above, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0302] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps performed by the target terminal in the method embodiment shown in FIG6 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG12 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0303] The terminal 600 includes but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609 and at least some of the components of the processor 610.

[0304] Those skilled in the art will appreciate that the terminal 600 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 610 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 12 does not constitute a limitation of the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be described in detail here.

[0305] It should be understood that in an embodiment of the present application, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042, and the graphics processor 6041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes a touch panel 6071 and at least one of other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0306] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 601 may transmit the data to the processor 610 for processing. Furthermore, the radio frequency unit 601 may send uplink data to the network-side device. Typically, the radio frequency unit 601 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

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

[0308] Processor 610 may include at least one processing unit. Optionally, processor 610 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 610.

[0309] The radio frequency unit 601 is configured to receive random access configuration information from a network side device; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources;

[0310] The processor 610 is configured to determine a duplex configuration according to the random access configuration information.

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

[0312] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps performed by the network-side device in the method embodiment shown in FIG6 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects. For the sake of brevity, they are not further described here.

[0313] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 13, network-side device 700 includes an antenna 71, a radio frequency device 72, a baseband device 73, a processor 74, and a memory 75. Antenna 71 is connected to radio frequency device 72. In the uplink direction, radio frequency device 72 receives information via antenna 71 and sends the received information to baseband device 73 for processing. In the downlink direction, baseband device 73 processes the information to be transmitted and sends it to radio frequency device 72. Radio frequency device 72 processes the received information and then sends it through antenna 71.

[0314] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 73 , which includes a baseband processor.

[0315] The baseband device 73 may include, for example, at least one baseband board, on which at least two chips are provided, as shown in FIG13 , one of the chips being, for example, a baseband processor, which is connected to the memory 75 through a bus interface to call the program in the memory 75 and execute the network device operations shown in the above method embodiment.

[0316] The network side device may further include a network interface 76, which is, for example, a Common Public Radio Interface (CPRI).

[0317] Specifically, the network side device 700 of the embodiment of the present application also includes: instructions or programs stored in the memory 75 and can be run on the processor 74. The processor 74 calls the instructions or programs in the memory 75 to execute the method executed by each unit shown in Figure 10 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0318] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the embodiment of the method for determining the above-mentioned duplex configuration is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0319] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0320] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned duplex configuration determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0321] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0322] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned duplex configuration determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0323] An embodiment of the present application also provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps performed by the terminal in the method for determining the duplex configuration as described above, and the network side device can be used to execute the steps performed by the network side device in the method for determining the duplex configuration as described above.

[0324] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0325] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0326] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for determining a duplex configuration, comprising: The terminal receives random access configuration information from a network side device; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources; The terminal determines a duplex configuration according to the random access configuration information.

2. The method according to claim 1, wherein: The terminal determines the duplex configuration according to the random access configuration information, including: The terminal determines, according to the random access uplink resource on at least one downlink time unit, an uplink subband on the at least one downlink time unit; The random access uplink resources on the at least one downlink time unit include at least one of the following: part or all of the random access uplink resources configured by the random access configuration information, and part or all of the random access uplink resources in the set of random access uplink resources configured by the random access configuration information.

3. The method according to claim 2, wherein: The terminal determines, according to the random access uplink resource on at least one downlink time unit, an uplink subband on the at least one downlink time unit, including: The terminal determines part or all of physical resource blocks PRBs occupied by random access uplink resources on the at least one downlink time unit as uplink subbands, wherein the random access uplink resources on the at least one downlink time unit are valid.

4. The method according to claim 2 or 3, wherein: In each downlink time unit of the at least one downlink time unit, part or all of the bandwidth occupied by at least one random access uplink resource adjacent to the uplink subband is a guard interval.

5. The method according to claim 4, wherein: The at least one random access uplink resource satisfies at least one of the following: Satisfies the mapping relationship between the physical random access channel PRACH and the random access uplink resource, and is not used to perform random access uplink transmission; The mapping relationship between PRACH and random access uplink resources is satisfied, and when a preset condition is satisfied, the random access uplink transmission is not performed; The mapping relationship from PRACH to random access uplink resources is not satisfied.

6. The method according to claim 5, wherein: The preset condition includes at least one of the following: The time domain or frequency domain interval between the random access uplink resource and the reference signal is less than or not greater than the first threshold; There is a reference signal transmission in the remaining bandwidth outside the uplink subband; There is transmission of a downlink common channel or a downlink common signal in the remaining bandwidth outside the uplink sub-band; There is reception of a reference signal in the remaining bandwidth outside the uplink subband; The remaining bandwidth outside the uplink sub-band is used for receiving a downlink common channel or a downlink common signal.

7. The method according to any one of claims 2 to 6, wherein: The random access configuration information is also used to configure a protection interval on the at least one downlink time unit.

8. The method according to any one of claims 1 to 7, wherein: The random access uplink resource configured by the random access configuration information includes at least one of the following types: Random access uplink resources existing in uplink time units; Random access uplink resources existing in time units with flexible symbols; A random access uplink resource present in an uplink subband of a downlink time unit; A random access uplink resource existing in an uplink subband of a downlink time unit, and no reference signal resource exists in the downlink time unit; A random access uplink resource existing on an uplink subband of a downlink time unit, and a reference signal resource existing on the downlink time unit; Random access uplink resources that are not in the uplink subband of the downlink time unit.

9. The method according to any one of claims 1 to 8, wherein: The set of random access uplink resources configured by the random access configuration information satisfies at least one of the following: Including different types of random access uplink resources; including random access uplink resources of the same type; Mapped to the same PRACH resource; Mapped to different PRACH resources.

10. The method according to claim 9, wherein: The set of random access uplink resources configured by the random access configuration information is used to perform random access uplink repeated transmission.

11. The method according to any one of claims 1 to 10, wherein: The association relationship between the random access uplink resource configured by the random access configuration information and the PRACH satisfies at least one of the following: At least two different random access uplink resources are independently associated with the PRACH; At least two different types of random access uplink resources are independently associated with the PRACH; At least two different random access uplink resources are associated with the PRACH; At least two different types of random access uplink resources are associated with the PRACH; Different random access uplink resources are independently associated with different PRACHs; Different types of random access uplink resources are independently associated with different types of PRACH; Different random access uplink resources are associated with different PRACHs; Different types of random access uplink resources are associated with different types of PRACH; The random access uplink resource is not associated with the PRACH that overlaps with it in the time domain.

12. The method according to any one of claims 1 to 11, wherein: The random access configuration information is a common configuration information, wherein the common configuration information is used to configure the random access uplink resources on the uplink subband and the random access uplink resources on the non-uplink subband, or the common configuration information is used to configure the set of random access uplink resources on the uplink subband and the set of random access uplink resources on the non-uplink subband; or, The random access configuration information is two independent configuration information, wherein the two independent configuration information are respectively used to configure the random access uplink resources on the uplink subband and the random access uplink resources on the non-uplink subband, or the two independent configuration information are respectively used to configure the set of random access uplink resources on the uplink subband and the set of random access uplink resources on the non-uplink subband.

13. The method according to any one of claims 1 to 12, wherein: The random access uplink resource configured by the random access configuration information includes at least one of the following: Uplink data shared channel resources in random access, PRACH resources in random access.

14. A method for determining a duplex configuration, comprising: The network side device sends random access configuration information to the terminal; wherein the random access configuration information is used to configure at least one of the following: random access uplink resources, a set of random access uplink resources; wherein the random access configuration information is associated with the duplex configuration.

15. The method according to claim 14, wherein: The random access configuration information is associated with the duplex configuration, including: The random access uplink resource on at least one downlink time unit is associated with an uplink subband on the at least one downlink time unit; The random access uplink resources on the at least one downlink time unit include at least one of the following: part or all of the random access uplink resources configured by the random access configuration information, and part or all of the random access uplink resources in the set of random access uplink resources configured by the random access configuration information.

16. The method according to claim 15, wherein: The random access uplink resource on the at least one downlink time unit is associated with the uplink subband on the at least one downlink time unit, including: Part or all of the physical resource blocks PRBs occupied by the random access uplink resources on the at least one downlink time unit are uplink subbands, wherein the random access uplink resources on the at least one downlink time unit are valid.

17. The method according to claim 15 or 16, wherein: In each downlink time unit of the at least one downlink time unit, part or all of the bandwidth occupied by at least one random access uplink resource adjacent to the uplink subband is a guard interval.

18. The method according to claim 17, wherein: The at least one random access uplink resource satisfies at least one of the following: Satisfies the mapping relationship between the physical random access channel PRACH and the random access uplink resource, and is not used to perform random access uplink transmission; The mapping relationship between PRACH and random access uplink resources is satisfied, and when a preset condition is satisfied, the random access uplink transmission is not performed; The mapping relationship from PRACH to random access uplink resources is not satisfied.

19. The method according to claim 18, wherein: The preset condition includes at least one of the following: The time domain or frequency domain interval between the random access uplink resource and the reference signal is less than or not greater than the first threshold; There is a reference signal transmission in the remaining bandwidth outside the uplink subband; There is transmission of a downlink common channel or a downlink common signal in the remaining bandwidth outside the uplink sub-band; There is reception of a reference signal in the remaining bandwidth outside the uplink subband; The remaining bandwidth outside the uplink sub-band is used for receiving a downlink common channel or a downlink common signal.

20. The method according to any one of claims 15 to 19, wherein: The random access configuration information is also used to configure a protection interval on the at least one downlink time unit.

21. The method according to any one of claims 14 to 20, wherein: The random access uplink resource configured by the random access configuration information includes at least one of the following types: Random access uplink resources existing in uplink time units; Random access uplink resources existing in time units with flexible symbols; A random access uplink resource present in an uplink subband of a downlink time unit; A random access uplink resource existing in an uplink subband of a downlink time unit, and no reference signal resource exists in the downlink time unit; A random access uplink resource existing on an uplink subband of a downlink time unit, and a reference signal resource existing on the downlink time unit; Random access uplink resources that are not in the uplink subband of the downlink time unit.

22. The method according to any one of claims 14 to 21, wherein: The set of random access uplink resources configured by the random access configuration information satisfies at least one of the following: Including different types of random access uplink resources; including random access uplink resources of the same type; Mapped to the same PRACH resource; Mapped to different PRACH resources.

23. The method according to claim 22, wherein: The set of random access uplink resources configured by the random access configuration information is used to perform random access uplink repeated transmission.

24. The method according to any one of claims 14 to 23, wherein: The association relationship between the random access uplink resource configured by the random access configuration information and the PRACH satisfies at least one of the following: At least two different random access uplink resources are independently associated with the PRACH; At least two different types of random access uplink resources are independently associated with the PRACH; At least two different random access uplink resources are associated with the PRACH; At least two different types of random access uplink resources are associated with the PRACH; Different random access uplink resources are independently associated with different PRACHs; Different types of random access uplink resources are independently associated with different types of PRACH; Different random access uplink resources are associated with different PRACHs; Different types of random access uplink resources are associated with different types of PRACH; The random access uplink resource is not associated with the PRACH that overlaps with it in the time domain.

25. The method according to any one of claims 14 to 24, wherein: The random access configuration information is a common configuration information, wherein the common configuration information is used to configure the random access uplink resources on the uplink subband and the random access uplink resources on the non-uplink subband, or the common configuration information is used to configure the set of random access uplink resources on the uplink subband and the set of random access uplink resources on the non-uplink subband; or, The random access configuration information is two independent configuration information, wherein the two independent configuration information are respectively used to configure the random access uplink resources on the uplink subband and the random access uplink resources on the non-uplink subband, or the two independent configuration information are respectively used to configure the set of random access uplink resources on the uplink subband and the set of random access uplink resources on the non-uplink subband.

26. The method according to any one of claims 14 to 25, wherein: The random access uplink resource configured by the random access configuration information includes at least one of the following: Uplink data shared channel resources in random access, PRACH resources in random access.

27. A device for determining a duplex configuration, comprising: A transceiver unit, configured to receive random access configuration information from a network side device; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources; A processing unit is used to determine a duplex configuration according to the random access configuration information.

28. A device for determining a duplex configuration, comprising: A transceiver unit, used for sending random access configuration information to a terminal; wherein the random access configuration information is used to configure at least one of the following: a random access uplink resource, a set of random access uplink resources; wherein the random access configuration information is associated with a duplex configuration.

29. A terminal comprising a transceiver, a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method for determining the duplex configuration as described in any one of claims 1 to 13 are implemented.

30. A network side device, comprising a transceiver, a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method for determining the duplex configuration as described in any one of claims 14 to 26 are implemented.

31. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the method for determining a duplex configuration as described in any one of claims 1 to 13, or implements the steps of the method for determining a duplex configuration as described in any one of claims 14 to 26.

Images