WO2025060090A1 - Random access channel occasion (ro) configuration method, information processing method, device, and storage medium - Google Patents

Abstract

Embodiments of the present disclosure provide an RO configuration method, an information processing method, a communication device, and a storage medium. The RO configuration method comprises: a network device configures a first-type RO on a subband full duplex (SBFD) time unit.

Description

Random access channel opportunity RO configuration method, information processing method, device and storage medium Technical Field

The present disclosure relates to the field of communication technology, and in particular to a random access channel (Radio access channel Occasion, RO) configuration method, information processing method, device and storage medium.

Background Art

There are two types of resource configuration for time division duplex (TDD): semi-static configuration and dynamic configuration. Semi-static configuration may include cell-level configuration (tdd-UL-DL-ConfigurationCommon) and user equipment (UE)-specific configuration (TDD-UL-DL-ConfigDedicated). Cell-level configuration is usually sent to the terminal through the system information block (SIB). UE-specific configuration is generally sent to the terminal using dedicated signaling of radio resource control (RRC). The terminal here can also be referred to as UE. The resource configuration of dynamic TDD can be transmitted by the physical downlink control channel (PDCCH) through the downlink control information (DCI), which can dynamically change the flexible time slot within a certain time window to a downlink (DL) time slot or an uplink (UL) time slot.

RO may be a resource used by a terminal for a random access message during a random access process. Generally, RO is configured on a UL time unit.

Summary of the invention

The embodiments of the present disclosure provide an RO configuration method, an information processing method, a communication device, and a storage medium.

According to a first aspect of an embodiment of the present disclosure, there is provided an RO configuration method, which is executed by a network device and includes: configuring a first type of RO on a subband full-duplex (SBFD) time unit.

According to a second aspect of an embodiment of the present disclosure, there is provided an information processing method executed by a terminal, the method comprising: receiving configuration information, wherein the random access channel opportunity RO indicated by the configuration information comprises a first type of RO located on a sub-band full-duplex SBFD time unit.

According to a third aspect of an embodiment of the present disclosure, there is provided an information processing method, which is executed by a new communication system, and the method may include: a network device configures a first type of RO on a sub-band full-duplex SBFD time unit and configures a second type of RO on an uplink UL time unit, and the bandwidth occupied by the SBFD time unit is less than the bandwidth occupied by the UL time unit; the network device sends configuration information of the first type of RO and configuration information of the second type of RO to a terminal; the terminal receives the configuration information of the first type of RO and the configuration information of the second type of RO; when the terminal is in an RRC connected state and has a random access requirement within a time range of a downlink DL time unit and/or a flexible time unit, the terminal selects to initiate a random access process on the first type of RO according to the configuration information of the first type of RO; the terminal has a random access requirement within a time range of a UL time unit, and selects the first type of RO or the second type of RO with the smallest time domain distance from the current moment to initiate a random access process according to the configuration information of the first type of RO and the configuration information of the second type of RO; wherein the random access response radio network temporary identifier RA-RNTI corresponding to the first type of RO is different from the RA-RNTI corresponding to the second type of RO; the RA-RATI is used to scramble the random access response in the random access process.

According to a fourth aspect of an embodiment of the present disclosure, a network device is provided, comprising: a processing module configured to configure a first type of RO on a sub-band full-duplex SBFD time unit.

According to a fifth aspect of an embodiment of the present disclosure, a terminal is provided, comprising: a receiving module configured to receive configuration information, wherein the random access channel opportunity RO indicated by the configuration information includes a first type of RO located on a sub-band full-duplex SBFD time unit.

According to a sixth aspect of an embodiment of the present disclosure, a communication device is provided, wherein the communication device includes: one or more processors; the processor is used to call instructions so that the communication device executes the method provided by any technical solution of the aforementioned first to third aspects.

According to a seventh aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the method provided in any of the first to third aspects.

The technical solution provided by the embodiment of the present disclosure can configure the first type of RO on the SDFB time unit, so that there is no need to configure all ROs on the UL time unit. On the one hand, the random access capacity of TDD can be improved. On the other hand, the terminal does not need to wait until the UL time slot to perform random access, but can initiate random access on the SBFD time unit, thereby reducing the delay of random access.

It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG1A is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

FIG1B is a schematic diagram showing a SBFD time unit according to an exemplary embodiment;

FIG1C is a schematic diagram of a process of four-step random access according to an exemplary embodiment;

FIG1D is a schematic diagram of a two-step random access process according to an exemplary embodiment;

FIG2A is a schematic flow chart of a RO configuration method according to an exemplary embodiment;

FIG2B is a schematic flow chart of a RO configuration method according to an exemplary embodiment;

FIG3A is a schematic flow chart of a RO configuration method according to an exemplary embodiment;

FIG3B is a flow chart showing a method for configuring an RO according to an exemplary embodiment;

FIG4A is a schematic flow chart of an information processing method according to an exemplary embodiment;

FIG4B is a schematic flow chart of an information processing method according to an exemplary embodiment;

FIG5A is a schematic diagram of a RO according to an exemplary embodiment;

FIG5B is a schematic diagram of a RO according to an exemplary embodiment;

FIG5C is a schematic diagram of a RO according to an exemplary embodiment;

FIG5D is a schematic diagram showing a PRACH resource according to an exemplary embodiment;

FIG6A is a schematic diagram showing the structure of a network device according to an exemplary embodiment;

FIG6B is a schematic diagram showing the structure of a terminal according to an exemplary embodiment;

FIG7A is a schematic diagram showing the structure of a communication device according to an exemplary embodiment;

FIG. 7B is a schematic structural diagram of a chip according to an exemplary embodiment.

DETAILED DESCRIPTION

The embodiments of the present disclosure provide an RO configuration method, an information processing method, a communication device, and a storage medium.

In a first aspect, an embodiment of the present disclosure provides an RO configuration method, which includes: configuring a first type of RO on a SBFD time unit.

In the above embodiment, the first type of RO is configured on the SDFB time unit, so there is no need to configure all ROs on the UL time unit. On the one hand, the random access capacity of TDD can be improved. On the other hand, the terminal does not need to wait until the UL time slot to perform random access, but can initiate random access on the SBFD time unit, thereby reducing the delay of random access.

In combination with some embodiments of the first aspect, in some embodiments, the first type of RO is used for random access of terminals in radio resource control RRC connected state.

Based on the above scheme, the first type of RO is configured for use by RRC connected terminals, so that the RRC connected terminals can achieve beam recovery, connection recovery and/or cell switching through random access of the first type of RO, so that the RRC connected terminals can be restored to a reachable state as soon as possible, thereby ensuring the continuity of the RRC connected terminals.

In combination with some embodiments of the first aspect, in some embodiments, the first type of RO is used to support the SBFD technology.

In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending RRC dedicated signaling; the RRC dedicated signaling includes configuration information of the first type RO.

In the above embodiment, the configuration information of the first type RO is sent to the terminal through RRC dedicated signaling, so that the terminal can know that the RO is the first type RO according to the RRC dedicated signaling.

In combination with some embodiments of the first aspect, in some embodiments the method further includes: sending a system message; the system message includes configuration information of the second type RO; and the second type RO is configured on an uplink time unit.

Based on the above solution, the network device will also send the configuration information of the second type RO to the terminal through the system message. The terminal can also receive the configuration information of the second type RO by receiving the system message, so that the second type RO can be used for random access later.

In combination with some embodiments of the first aspect, in some embodiments, resource locations of the second type RO and the first type RO do not overlap.

Based on the above solution, since the resource locations of the second type RO and the first type RO do not overlap, the resource locations of the first type RO and the second type RO used by the terminal do not overlap, so the conflict problem is naturally solved.

In combination with some embodiments of the first aspect, in some embodiments, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or the subframe where the second type RO is located is different from the subframe where the first type RO is located, or the wireless frame where the second type RO is located is different from the wireless frame where the first type RO is located, or the time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO.

Based on the above solution, in the embodiment of the present disclosure, the time domain positions of the first type RO and the second type RO are staggered so that the resource positions of the first type RO and the second type RO do not overlap.

In combination with some embodiments of the first aspect, in some embodiments, the resource locations of the second type RO and the first type RO overlap, and the random access response wireless network temporary identifier RA-RNTI corresponding to the second type RO is different from the random access response wireless network temporary identifier RA-RNTI corresponding to the first type RO.

Based on the above solution, the conflict between the configuration of the first type RO and the configuration of the second type RO is solved directly by distinguishing and setting the RA-RNTI.

In combination with some embodiments of the first aspect, in some embodiments, the frequency domain index of the first type of RO is different from the frequency domain index of the second type of RO.

Based on the above solution, the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO are distinguished by different frequency domain indexes, which has the characteristic of simple implementation.

In combination with some embodiments of the first aspect, in some embodiments, the frequency domain index of the second type RO is obtained by continuing to number the frequency domain index of the first type RO, or the frequency domain index of the first type RO is obtained by continuing to number the frequency domain index of the second type RO.

Based on the above scheme, by connecting the frequency domain indexes of the first type RO and the second type RO within the same time-frequency domain position range, the frequency domain index of the first type RO and the frequency domain index of the second type RO will not overlap, thereby ensuring that the RA-RNTI corresponding to the first type RO and the RA-RNTI corresponding to the second type RO can be distinguished.

In combination with some embodiments of the first aspect, in some embodiments, the system message includes: the number of first-category ROs of frequency division multiplexing.

Based on the above solution, by carrying the number of the first type ROs in frequency division multiplexing in the system message, the terminal can know the range of the frequency domain index of the first type RO, which has the characteristic of simple implementation.

In combination with some embodiments of the first aspect, in some embodiments, the RRC dedicated signaling also includes a starting index of the frequency domain index of the first type RO; the starting index of the frequency domain index is outside the index range corresponding to the frequency domain index of the second type RO.

In combination with some embodiments of the first aspect, in some embodiments, the RA-RNTI corresponding to the first type of RO is generated according to the offset, and the RA-RNTI corresponding to the second type of RO is not generated according to the offset.

In combination with some embodiments of the first aspect, in some embodiments, the RA-RNTI corresponding to the first type RO and the RA-RNTI corresponding to the second type RO are both generated based on the offset, and the offset corresponding to the first type RO is different from the offset corresponding to the second type RO.

Based on the above solution, by setting the offset, the RA-RNTI corresponding to the first type RO and the second type RO can also be different.

In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending a system message; the system message includes first configuration information, and the RO configured by the first configuration information includes a first type RO and a second type RO; the second type RO is configured on an uplink time unit.

In some embodiments, both the first type RO and the second type RO are configured by the first configuration information, that is, the first type RO and the second type RO are configured by the same set of configuration information. The first configuration information is sent by a system message, so that the network device can inform the terminal of both the first type RO and the second type RO by sending a system message, and the terminal only needs to receive the system message to know the first type RO and the second type RO.

In some embodiments, the method further includes sending first information, where the first information is at least used to determine a terminal that can use the first type of RO.

Based on the above solution, the network device sends the first information to indicate the terminals that can use the first type of RO to the terminal, thereby realizing the indication of the terminals used by the first type of RO.

In combination with some embodiments of the first aspect, in some embodiments, the first information is used for a terminal that can use the first type of RO in a downlink time and/or a flexible time of a SBFD time unit.

In combination with some embodiments of the first aspect, in some embodiments, the first information is further used to indicate a terminal that can use the RO located in the uplink time unit.

In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending second information, where the second information instructs the RRC connected terminal to perform non-contention random access CFRA.

Based on the sending of the second information in the above solution, the network device can be instructed to improve the efficiency of random access of the terminal through CFRA.

In combination with some embodiments of the first aspect, in some embodiments, the second information indicates at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in a time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in an uplink time unit.

In a second aspect, an embodiment of the present disclosure provides an information processing method, which is executed by a terminal, and includes: receiving configuration information, wherein the random access channel opportunity RO indicated by the configuration information includes a first type of RO on a SBFD time unit.

In combination with some embodiments of the second aspect, in some embodiments, the first type of RO is used for random access of terminals in radio resource control RRC connected state.

In combination with some embodiments of the second aspect, in some embodiments, the first type of RO is used for random access of terminals in RRC connected state that support SBFD technology.

In combination with some embodiments of the second aspect, in some embodiments, receiving the configuration information of the RO includes: receiving radio resource control RRC dedicated signaling, the RRC dedicated signaling includes the configuration information of the first type of RO.

In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a system message, the system message including configuration information of the second type RO; and the second type RO is configured on an uplink time unit.

In combination with some embodiments of the second aspect, in some embodiments, resource locations of the second type RO and the first type RO do not overlap.

In combination with some embodiments of the second aspect, in some embodiments, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or the subframe where the second type RO is located is different from the subframe where the first type RO is located, or the wireless frame where the second type RO is located is different from the wireless frame where the first type RO is located, or the time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO.

In combination with some embodiments of the second aspect, in some embodiments, the resource location of the second type RO overlaps with the resource location of the first type RO, and the RA-RNTI corresponding to the second type RO is different from the RA-RNTI corresponding to the first type RO.

In combination with some embodiments of the second aspect, in some embodiments, the frequency domain index of the first type of RO is different from the frequency domain index of the second type of RO.

In combination with some embodiments of the second aspect, in some embodiments, the frequency domain index of the first type RO is different from the frequency domain index of the second type RO; the frequency domain index of the second type RO is obtained by continuing to number the frequency domain index of the first type RO, or, the frequency domain index of the first type RO is obtained by continuing to number the frequency domain index of the second type RO.

In combination with some embodiments of the second aspect, in some embodiments, the system message includes: the number of first-category ROs of frequency division multiplexing.

In combination with some embodiments of the second aspect, in some embodiments, the RRC dedicated signaling also includes a starting index of the frequency domain index of the first type RO; the starting index of the frequency domain index is outside the index range corresponding to the frequency domain index of the second type RO.

In combination with some embodiments of the second aspect, in some embodiments, the RA-RNTI corresponding to the first type of RO is generated according to the offset, and the RA-RNTI corresponding to the second type of RO is not generated according to the offset.

In combination with some embodiments of the second aspect, in some embodiments, the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO are both generated based on the offset, and the offset corresponding to the first type of RO is different from the offset corresponding to the second type of RO.

In combination with some embodiments of the second aspect, in some embodiments, receiving configuration information includes: receiving a system message; the system message includes configuration information, and the RO configured by the configuration information includes a first type RO and a second type RO; the second type RO is configured on an uplink time unit; receiving first information; the first information is at least used to determine a terminal that can use the first type RO.

In combination with some embodiments of the second aspect, in some embodiments, the first information is used for a terminal that can use the first type of RO in a downlink time and/or a flexible time of a SBFD time unit.

In combination with some embodiments of the second aspect, in some embodiments, the first information is further used to indicate a terminal that can use the RO located in the uplink time unit.

In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving second information, the second information instructing the RRC connected state terminal to perform non-contention random access CFRA.

In combination with some embodiments of the second aspect, in some embodiments, the second information indicates at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in a time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in an uplink time unit.

In a third aspect, an embodiment of the present disclosure provides a network device, which includes: a processing module configured to configure a first type of RO on a sub-band full-duplex SBFD time unit.

In a fourth aspect, an embodiment of the present disclosure provides a terminal, which includes: a receiving module configured to receive configuration information of an RO, wherein the RO includes: a first type of RO located on a sub-band full-duplex SBFD time unit.

In a fifth aspect, an embodiment of the present disclosure provides a communication device, the communication device comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the method described in the optional implementation manner of the first aspect and/or the second aspect.

In a sixth aspect, an embodiment of the present disclosure provides an information processing method, which includes:

The network device configures a first type of RO on a sub-band full-duplex SBFD time unit and configures a second type of RO on an uplink UL time unit, and a bandwidth occupied by the SBFD time unit is smaller than a bandwidth occupied by the UL time unit;

The network device sends configuration information of the first type RO and configuration information of the second type RO to the terminal;

The terminal receives configuration information of the first RO and configuration information of the second type RO;

When the terminal has a random access requirement in the RRC connected state and within the time range of the downlink DL time unit and/or the flexible time unit, the terminal selects to initiate a random access process on the first type RO according to the configuration information of the first type RO; when the terminal has a random access requirement within the time range of the UL time unit, the terminal selects the first type RO or the second type RO with the smallest time domain distance from the current moment to initiate a random access process according to the configuration information of the first type RO and the configuration information of the second type RO;

The random access response radio network temporary identifier RA-RNTI corresponding to the first type RO is different from the RA-RNTI corresponding to the second type RO; the RA-RATI is used to scramble the random access response in the random access process.

Based on the above solution, the RO is no longer limited to be set on the UL time unit, so when the terminal has a random access requirement within the time range of the DL time unit and/or the F time unit, the first type of RO on the SBFD time unit can be used to complete the random access in time.

In a seventh aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, and when the instructions are in a communication device, When the communication device is running on the equipment, the communication device is enabled to execute the method described in the optional implementation manner of the first aspect and/or the second aspect and/or the sixth aspect.

In an eighth aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first aspect and/or the second aspect and/or the sixth aspect.

In a ninth aspect, an embodiment of the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect and/or the second aspect and/or the sixth aspect.

It is understandable that the above terminals, network devices, communication systems, program products, and computer programs are all used to execute the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods, which will not be repeated here.

The embodiments of the present disclosure provide an RO configuration method, a communication device, a communication system, and a storage medium. In some embodiments, the terms RO configuration method, communication method, information processing method, etc. can be replaced with each other, the terms information indicating device, information processing device, information transmission device, network device or terminal, etc. can be replaced with each other, and the terms communication system, information processing system, etc. can be replaced with each other.

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

In each embodiment of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and/or descriptions between the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

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

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

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

In some embodiments, the terms "at least one (at least one of), "one or more (one or more)", "a plurality of (a plurality of)", "multiple (multiple)", etc. can be used interchangeably.

In some embodiments, "at least one of A and B", "A and/or B", "A in one case, B in another case", "A in one case, B in another case", etc., may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., the above is also similar.

In some embodiments, the recording method of "A or B" may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). When there are more branches such as A, B, C, etc., the above is also similar.

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

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

In some embodiments, terms such as “…”, “determine…”, “in the case of…”, “at the time of…”, “when…”, “if…”, “if…”, etc. can be used interchangeably.

In some embodiments, the terms "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", "above" and the like can be used interchangeably, and "less than", "less than or equal to", "not greater than", "less than" and "less than" can be used interchangeably. The terms "less than,""less than or equal to,""no more than,""lowerthan,""lower than or equal to,""not higher than," and "below" are interchangeable.

In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

In some embodiments, "network" may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

In some embodiments, the terms "access network device (AN device), "radio access network device (RAN device)", "base station (BS)", "radio base station (radio base station)", "fixed station (fixed station)", "node", "access point (access point)", "transmission point (TP)", "reception point (RP)", "transmission/reception point (TRP)", "panel", "antenna panel (antenna panel)", "antenna array (antenna array)", "cell", "macro cell", "small cell (small cell)", "femto cell (femto cell)", "pico cell (pico cell)", "sector (sector)", "cell group (cell)", "serving cell", "carrier (carrier)", "component carrier (component carrier)", "bandwidth part (bandwidth part (BWP))" and so on can be used interchangeably.

In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client and the like can be used interchangeably.

In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by the communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may also be configured to have a structure that has all or part of the functions of the terminal.

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

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

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

FIG1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

As shown in Fig. 1A, a communication system 100 includes a terminal 101 and a network device 102. The network device 102 may include an access network device and a core network device.

In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, and a wireless terminal device in smart home. In some embodiments, the terminal is also called a user equipment (User Equipment, UE).

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

In some embodiments, the technical solution of the present disclosure may be applicable to the Open RAN architecture. In this case, the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

In some embodiments, the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be called a control unit (control unit). The CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.

In some embodiments, the core network device may be a device including a first network element, etc., or may be a plurality of devices or a group of devices, each including a first network element. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. A person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A, or part of the subject, but are not limited thereto. The subjects shown in FIG1A are examples, and the communication system may include all or part of the subjects in FIG1A, or may include other subjects other than FIG1A, and the number and form of the subjects are arbitrary, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, which may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.

The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the fourth generation mobile communication system (4G), the fifth generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), etc. ), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device to Device (D2D) system, Machine to Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle to-Everything (V2X), system using other RO configuration methods, next generation systems based on them, and the like. In addition, a number of systems may also be applied in combination (e.g., a combination of LTE or LTE-A and 5G, etc.).

Dynamic configuration for TDD can realize dynamic resource allocation, improve system performance and effective frequency utilization, but it may cause cross link interference (CLI).

In order to enhance UL coverage, reduce uplink latency, and increase system capacity and configuration flexibility, SBFD technology is introduced. SBFD technology allows network devices to send and receive simultaneously, and terminals to send or receive at one time point. In this way, when performing resource configuration, SBFD time units are introduced in the time domain. Multiple terminals perform uplink transmission and downlink reception respectively on non-overlapping subbands (Subband) of a single carrier of TDD. Figure 1B shows a schematic diagram of a resource configuration. In Figure 1B, there are 5 time slots, which are DL time slots, UL time slots and SBFD time slots. DL time slots are referred to as D. UL time slots are referred to as U. SBFD time slots can be used to reserve some subbands on DL frequency domain resources for uplink transmission. That is, the 2nd to 4th time slots in Figure 1B are all SBFD time slots. It is worth noting that Figure 1B is an example of an SBFD time slot. Specifically, the SBFD time slot may also be set in the UL time unit. By setting the SBFD time slot, the terminal may support uplink transmission and downlink reception simultaneously in one time unit.

According to the steps involved in random access, random access may include: four-step random access and two-step random access. According to whether random access involves contention between terminals, random access may include: contention-based random access and non-contention random access.

FIG. 1C is a flow chart showing a four-step random access, which may include:

Step 1: The terminal sends a random access preamble (Random Access Preamble).

The terminal can receive a group of SSBs and determine their reference signal received power (RSRP) according to the relationship between the synchronization signal/physical broadcast channel (PBCH) Block (SSB) configured by high-level signaling, the physical random access channel (PRACH) resources, and the random access preamble. According to RSRP and the threshold, a suitable group of SSBs for determining the random access preamble is selected; based on the selected SSBs, the corresponding relationship between SSBs and RACH resources, the range of RACH resources and random access preambles is determined; here, RACH The resources include RO. In some cases, RO may also be referred to as PRACH opportunity or PRACH resource. The terminal 101 selects a random access preamble group according to the expected message size of the message (Message, Msg) 3, and then randomly selects a random access preamble used for this random access.

Terminal 101 sets the target receiving power of the random access preamble on the network side: preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER-1)×powerRampingStep. preambleReceivedTargetPower can be the target power for the random access preamble received by the network device. powerRampingStep can be the power ramping step. DELTA_PREAMBLE is the preset offset value. PREAMBLE_POWER_RAMPING_COUNTER is the maximum number of repetitions of the random access preamble. The random access preamble corresponds to Msg1.

Step 2: The base station (e.g., gNB) sends a Random Access Response (RAR).

Determine the random access response wireless network temporary identification (RA-RNTI) according to the resource index of the PRACH that sends Msg1; calculate the RA-RNTI.

For example, RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id.

s_id is the index of the first Orthogonal Frequency Division Multiplexing (OFDM) symbol of the RO. Exemplarily, 0≤s_id<14. t_id is the index of the first time slot in the system frame where the RO is located. Exemplarily, 0≤t_id<80. t_id can be determined according to the subcarrier spacing. f_id is the frequency domain index of the RO, and exemplarily, 0≤f_id<8. ul_carrier_id indicates the UL carrier of the random access, which may include a conventional UL or a supplementary UL (SUL) carrier. For example, ul_carrier_id equals 0, indicating that the random access uses the UL carrier. ul_carrier_id equals 1, indicating that the random access uses the SUL carrier.

The UE opens the RAR time window (ra-Response Window) at the first PDCCH opportunity after sending the random access preamble and monitors the RA-RNTI-scrambled PDCCH during the time window to receive the RAR corresponding to the RA-RNTI.

If the RAR is not received within the RAR time window or the RAR corresponding to the random access preamble sent by itself is not received. That is, the RAR corresponding to the random access preamble identifier (RAPID) sent by itself is not received, power climbing is performed and msg1 is retransmitted based on the increased power. In some embodiments, whether to perform random access uplink transmission power climbing depends on whether to switch beams. For example, uplink transmission power climbing is performed without switching beams, and power climbing may not be performed when beam switching is performed.

If a RAR is received within the RAR monitoring window, if it is the first time that the RAR is received, a Media Access Control (MAC) Protocol Data Unit (PDU) is obtained from the multiplexing and assembly entity, and the MAC PDU is saved in the cache of Msg3.

Step 3: Uplink scheduled transmission (Scheduled Transmission).

If the terminal does not have a Cell-Radio Network Temporary Identifier (C-RNTI), the execution of the RACH is triggered by the Common Control Channel (CCCH), and Msg3 is a MAC PDU generated by the CCCH Service Data Unit (SDU) as input. If the terminal has C-RNTI, the UE indicates that the multiplexing and assembly entity includes a C-RNTI MAC Control Element (CE), and Msg3 is a MAC PDU generated by the C-RNTI MAC CE.

Get the MAC PDU from the Msg3 cache and transmit the MAC PDU based on the uplink grant (UL Grant) in the RAR.

After Msg3 is transmitted, the random access contention resolution timer (ra-ContentionResolutionTimer) is started and the PDCCH is monitored during the timer. If Msg3 contains C-RNTI MAC CE, the terminal monitors the PDCCH scrambled by the C-RNTI. If Msg 3 does not contain C-RNTI MAC CE, the UE monitors the PDCCH scrambled by the temporary cell radio network temporary identifier (TC-RNTI) to receive Msg4.

When Msg3 performs a hybrid automatic repeat request (HARQ) retransmission, the random access conflict resolution timer is restarted; before the random access conflict resolution timer times out or stops, the terminal will continue to monitor the PDCCH; Msg3 HARQ retransmission is scrambled and scheduled based on TC-RNTI.

Step 4: Conflict Resolution.

If Msg3 contains C-RNTI MAC CE, the terminal monitors the PDCCH scrambled by the C-RNTI. If the terminal monitors Msg3, it is considered that the conflict resolution is successful, otherwise it is considered that the conflict resolution fails.

If Msg 3 does not contain C-RNTI MAC CE, the terminal monitors the temporary C-RNTI and receives Msg 4. If Msg 4 is received and can match CCCH SDU, the conflict resolution is successful, otherwise the conflict resolution fails.

If the conflict resolution fails, the terminal performs power ramp-up or beam switching and resends Msg1 to perform four-step random access again.

FIG1D shows a flow chart of two-step random access. The two-step random access may include:

Step 0: Perform random access (RA) preamble scheduling.

Step 1: The terminal sends a random access preamble (Random Access Preamble).

The random access preamble code is carried in MsgA sent by the terminal.

Step 2: The base station sends a random access response (Random Access Response, RAR).

The random access response is carried in MsgB sent by the network device.

It is worth noting here that for two-step random access, the following formula can be used to calculate RA-RNTI:

RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2

The difference between the RA-RNTI for MsgB and the RA-RATI for Msg2 in the four-step random access is that the calculation item 14×80×8×2 is introduced.

FIG2A is an interactive schematic diagram of an RO configuration method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to an RO configuration method, which is used in a communication system 100, and the method includes:

S2101: The network device configures the RO on the SBFD time unit.

In some embodiments, the network device may be an access network device. In some embodiments, the network device configures the RO on the SBFD time slot. In some embodiments, the network device configures the RO on the SBFD symbol. The SBFD symbol here may include: set in a DL time unit, set in a flexible (Flexible, F) time unit and/or set in a UL time unit. In some embodiments, the subband corresponding to the SBFD symbol is configured on the DL time slot, and the frequency domain position where the SBFD symbol is not configured in the DL time slot can support the downlink reception of the terminal and support the uplink transmission of the terminal on the subband corresponding to the SBFD symbol, which can realize the simultaneous uplink transmission and downlink reception of the terminal in the TDD scenario. Alternatively, the SBFD symbol is configured on the UL time slot. The frequency domain position where the SBFD symbol is not configured in the UL time slot can support the uplink transmission of the terminal, and the downlink reception of the terminal can be supported on the subband corresponding to the SBFD symbol, which can also realize the simultaneous uplink transmission and downlink reception of the terminal in the TDD scenario.

As shown in FIG. 5A to FIG. 5C , a RO may be configured on the SBFD time unit.

Since the RO is configured on the SBFD time unit instead of being limited to the UL time unit, the number of RO resources can be increased, thereby improving the random access capacity of the system. On the other hand, the RO is set in the DL time unit and/or the F time unit, so that the random access of the terminal with demand in the DL time unit/or the F time unit can be met in time, thereby at least reducing the random access delay of this part of the terminals and improving the random access efficiency.

In some embodiments, the first type of RO can be used by any terminal supporting the SBFD technology.

In some embodiments, the first type of RO is not used for RRC idle state and/or RRC inactive state terminals. In some embodiments, the first type of RO is available for terminals that support SBFD technology and are in RRC connected state. Exemplarily, a terminal in RRC connected state needs to use RO for random access when beam failure, invalid link failure or cell switching occurs.

S2102: The network device sends RRC dedicated signaling.

In some embodiments, the RRC dedicated signaling includes at least configuration information of the first type of RO. In some embodiments, the RRC connected terminal receives the RRC dedicated signaling. In some embodiments, the RRC connected terminal supporting the SBFD technology receives the RRC dedicated signaling.

In some embodiments, the configuration information of the first type of RO may include: time-frequency domain location information of the RO. Exemplarily, the time-frequency domain location information may include: the frame number of the system frame (or radio frame) configured with the RO, the subframe number, the number of subframes configured with the RO in the radio frame configured with the RO, the number of time slots configured with the RO in a subframe, the time slot number and/or the duration of the PRAC resource, etc.

In some embodiments, the configuration information of the first type of RO may also be referred to as PRACH configuration information, which may include a PRACH configuration index, the number of ROs for frequency division multiplexing (such as msg1-FDM), the format information of frequency division multiplexing, and the frequency domain starting position (msg1-FrequencyStart). The number of ROs for frequency division multiplexing is different from the number of ROs configured by the configuration information. For example, the configuration information of the first type of RO configures ROs on two symbols, and configures 4 ROs using frequency division multiplexing on one symbol. At this time, the configuration information configures a total of 8 first type ROs, but the number of ROs for frequency division multiplexing is equal to 4.

FIG5D is a schematic diagram of a PRACH configuration. As shown in FIG5D , the sequence corresponding to the random access preamble (also referred to as a random access sequence) may include a long sequence and a short sequence. The length of the long sequence is greater than the length of the short sequence. The message that sends the random access preamble is called message 1 or message A, and has formats 0 to 3. Which sequence in formats 0 to 3 is specifically selected can be determined based on the subcarrier spacing of the RO. For example, if the subcarrier spacing of the RO is 1.25kHz, any one of formats 0 to 2 can be selected. If the subcarrier spacing of the RO is 5kHz, format 3 can be selected. The configuration of the PRACH resources shown in FIG5D may include two parameters, namely msg1-FDM and msg1-FrequencyStart. msg1-FDM can be the number of frequency division multiplexing of the RO. msg1-FrequencyStart is the starting position of the frequency domain of the RO.

S2103: The network device sends a system message.

The system message may include one or more system information blocks (SIBs).

The system message may include configuration information of the second type RO. The content of the configuration information used to configure the second type RO may refer to the content of the configuration information used to configure the first type RO, which will not be described in detail here.

In some embodiments, the second type of RO is configured on a UL time unit, for example, the second type of RO is configured on a UL time slot and/or a UL symbol.

In some embodiments, all terminals in the cell can receive the system message, that is, RRC connected state terminals, RRC idle state terminals and/or RRC inactive state terminals can receive the system message.

In some embodiments, the resource locations of the first type RO and the resource locations of the second type RO do not overlap.

In some embodiments, the candidate resource locations of the first type RO and the candidate resource locations of the second type RO do not overlap.

In some embodiments, the candidate resource locations of the first-category RO may be resource locations where the first-category RO can be configured.

In some embodiments, the candidate resource locations of the second type RO may be resource locations where the second type RO can be configured.

The non-overlapping resource positions here may include: non-overlapping frequency domain positions and/or time domain configurations.

As shown in FIG5C , the frequency domain position of the first type RO is different from the frequency domain position of the second type RO, so that the resource position of the first type RO is different from the resource position of the second type RO.

Exemplarily, the subband where the second type RO is located is different from the subband occupied by the SBFD time unit.

In some embodiments, the bandwidth occupied by the SBFD time unit where the first type of RO is located is smaller than the bandwidth occupied by the time unit where the second type of RO is located.

In some embodiments, the candidate resource locations of the first type RO and the second type RO do not overlap, which may include: the first type RO and the second type RO do not overlap in the time domain, and/or the first type RO and the second type RO do not overlap in the frequency domain.

Since the resource locations of the first type RO and the second type RO do not overlap, the resource locations of the RO used when selecting message 1 or message A for random access are naturally different, and the RA-RNTI calculated by the terminal and the network device according to the resource index corresponding to the resource location of the RO is naturally different. In this way, it is obvious that the RA-RNTI of the terminal using the first type RO and the second type RO for random access will be naturally distinguished, so that the random access responses of different terminals can be naturally distinguished when sending random access Msg2 and MsgB. The resource index may include: the frequency domain index of the RO and/or the time domain index of the RO.

It is worth noting that the formula for calculating RA-RNTI at this time can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

In a scenario where the resource locations of the first type RO and the second type RO do not overlap, the frequency domain locations of the first type RO and the second type RO may be different. For example, the first type RO and the second type RO use frequency division multiplexing and may be configured on different carriers or subcarriers or subbands.

In some other embodiments, the difference in resource locations between the first type RO and the second type RO may mainly be a difference in time domain locations.

Exemplarily, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or the subframe where the second type RO is located is different from the subframe where the first type RO is located, or the wireless frame where the second type RO is located is different from the wireless frame where the first type RO is located, or the time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO.

In some embodiments, the resource location of the first type RO and the resource location of the second type RO may overlap. Exemplarily, the resource location may overlap, which may be understood as the resource location being the same.

In some embodiments, the resource location of the first type RO and the resource location of the second type RO can be understood as: the candidate resource location of the first type RO and the candidate resource location of the second type RO can overlap. Exemplarily, the candidate resource location can overlap and can be understood as the same candidate resource location. In some embodiments, the candidate resource location of the first type RO can be a resource location that can configure the first type RO. In some embodiments, the candidate resource location of the second type RO can be a resource location that can configure the second type RO.

Here, the resource location of the first type RO and the resource location of the second type RO may overlap, and may include:

The frequency domain position of the first type RO is the same as the frequency domain position of the second type RO, or the time domain position of the first type RO is the same as the time domain position of the second type RO.

Exemplarily, the subband where the second type RO is located may be the same as the subband occupied by the SBFD time unit.

Exemplarily, the candidate resource locations of the first type RO and the candidate resource locations of the second type RO may be the same, then the RA-RNTI corresponding to the second type RO is different from the RA-RNTI corresponding to the first type RO. The difference in RA-RNTI corresponding to the first type RO and the second type RO can be distinguished by at least one of the following methods.

For example, RA-RATI can be calculated based on the frequency domain index of the RO. In this case, by making the frequency domain index of the first type of RO different from the frequency domain index of the second type of RO, the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO are different. That is, the frequency domain index of the RO is used to distinguish the type of RO. For another example, when RA-RNTI is calculated based on the index corresponding to the time-frequency domain position of the RO, one or more offsets can be introduced to make the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO different. That is, the offset is used to distinguish the type of RO. Exemplarily, the frequency domain index of the second type of RO is the frequency domain index of the first type of RO. Or, the frequency domain index of the first type of RO is obtained by continuing to number the frequency domain index of the second type of RO. In this implementation manner, the frequency domain indexes of the first type of RO and the second type of RO are connected.

For example, if there are M first-class ROs in the frequency domain, then the frequency domain index of the first-class RO is obtained by numbering the M ROs from 0 or 1 according to the frequency domain position from high to low or from low to high. Further, after the first-class RO is numbered, the second-class RO is numbered from M or M+1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. In this way, even if the first-class RO and the second-class RO are located in the same frequency domain range, it is obvious that the frequency domain index of the first-class RO and the frequency domain index of the second-class RO will be different. Here, M is the number of first-class ROs frequency-division multiplexed in the frequency domain. For another example, if there are S second-class ROs in the frequency domain, then the frequency domain index of the second-class RO is obtained by numbering the S ROs from 0 or 1 according to the frequency domain position from high to low or from low to high. Further, after the second-class RO is numbered, the first-class RO is numbered from S or S+1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. In this way, even if the first type RO and the second type RO are located in the same frequency domain range, it is obvious that the frequency domain index of the first type RO and the frequency domain index of the second type RO will be different. Here, S is the number of second type ROs frequency-division multiplexed in the frequency domain. In both embodiments, the frequency domain index of the first type RO and the frequency domain index of the second type RO are consecutively numbered.

In this embodiment, since the configuration information of the second type of RO is sent by the system message and the configuration information of the first type of RO is sent by the RRC dedicated signaling, the RO frequency division multiplexing number M of the first type of RO is carried in the system message, or the RO frequency division multiplexing number S of the second type of RO is carried in the RRC dedicated signaling. As shown in Figures 5A and 5B, the frequency division multiplexing number M of the first type of RO is equal to 2. The frequency division multiplexing number of the second type of RO is equal to 4. In Figures 5A and 5B, the RO frequency division multiplexing number uses the parameter msg1-FDM. In the actual process, this parameter can also be MsgA-FDM. For another example, the starting index of the frequency domain index of the first type of RO is different from the starting index of the frequency domain index of the second type of RO.

In some embodiments, the starting index of the first type of RO starts from 0, and the starting index of the second type of RO starts from the specified position of the network device or the position agreed upon by the protocol. And the starting index of the second type of RO will avoid the range of the frequency domain index of the first type of RO. In this case, optionally, the system message can carry the starting index of the frequency domain index of the second type of RO.

In other embodiments, the starting index of the second type RO starts from 0, and the starting index of the first type RO can be specified by the network device or agreed upon by the protocol. In this case, the starting index of the first type RO will avoid the range of the frequency domain index of the second type RO. In this case, optionally, the RRC dedicated signaling can carry the starting index of the frequency domain index of the first type RO.

In this embodiment, the frequency domain index of the first type of RO and the frequency domain index of the second type of RO may be continuous or discontinuous, depending on the number of frequency division multiplexing of different types of ROs and the setting position of the starting index.

Similarly, when the frequency domain index of the first type RO is different from the frequency domain index of the second type RO, the formula for calculating the RA-RNTI value can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

In some other embodiments, the resource location of the first type RO and the resource location of the second type RO may be the same, and the frequency domain index of the first type RO and the frequency domain index of the second type RO may also be numbered from the same position. For example, the frequency domain index of the first type RO and the frequency domain index of the second type RO are both numbered from 0 or 1. In this case, in order to distinguish the RA-RNTI corresponding to the first type RO and the second type RO, one or more parameters for calculating the RA-RNTI may be introduced. In the embodiment of the present disclosure, at least one offset is introduced in the formula for calculating the RA-RNTI. The offset is used to distinguish the first type RO from the second type RO.

Example 1: An offset (which may be referred to as a first offset) is introduced into the calculation formula for the RA-RNTI of the first type of RO, and the size of the offset may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the RRC dedicated signaling where the configuration information of the first type of RO is located.

Example 2: An offset (which may be referred to as a second offset) is introduced into the calculation formula for the RA-RNTI of the second type of RO, and the size of the offset may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the system message where the configuration information of the second type of RO is located.

Example 3: Different offsets may be introduced into the calculation formulas for the first type RO and the second type RO, respectively, so that the RA-RNTI corresponding to the first type RO and the second type RO can also be distinguished. The sizes of these two offsets may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the system message or the RRC dedicated signaling, respectively.

When using Example 1 or Example 2, it is only necessary to introduce an offset into the calculation of RA-RNTI corresponding to the first type RO or the second type RO. When using Example 3, an offset for calculating RA-RNTI is introduced into the first type RO and the second type RO respectively.

For example, MSGB-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2+offset.

MSG1-RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+offset.

MSGB-RNTI may be the RA-RNTI for two-step random access, MSG1-RA-RNTI may be the RA-RNTI for four-step random access, and offset may be the offset introduced above.

The offsets for two-step random access and four-step random access for a type RO can be the same or different. The network device indicates that the two-step random access and the four-step random access for a type of RO can be selected to be the same, thereby reducing the instruction overhead of the network device.

S2105: The network device sends the second information.

In some embodiments, the network device sends RRC dedicated signaling including the second information.

In some embodiments, the network device sends a PDCCH signaling including the second information. The PDCCH signaling may include but is not limited to DCI.

In some embodiments, the second information may indicate to perform non-contention random access.

In some embodiments, the second information may instruct the RRC connected terminal to perform non-contention random access.

In some embodiments, the second information may be carried in RRC dedicated signaling different from the configuration information of the RO.

Exemplarily, when a cell is switched for an RRC connected terminal, the second information may be carried in a cell switching command. That is, while the cell switching command instructs the RRC connected terminal to switch the cell, the second information carried in the cell switching command is used to switch the RRC connected terminal to the target cell using non-competitive random access during the random access process.

In some embodiments, the terminal uses beam communication, and the second information is carried in the network signaling where the beam configuration or beam failure configuration of the terminal communication is located. In this way, when the RRC connected terminal performs beam recovery, it naturally uses non-contention random access for random access.

In some embodiments, the second information may further include one or more non-contention random access parameters, which may be used for the non-contention random access of the terminal.

Exemplarily, the parameter includes but is not limited to at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in the time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in the uplink time unit.

Exemplarily, the second information indicates a range of random access preamble codes of CFRA, and when performing CFRA, the terminal may randomly select one within the range indicated by the second information to perform non-contention random access.

In some embodiments, the resource index of the RO may be prach-ConfigIndex and/or PRACH Mask Index, both of which can determine the resource location of the RO.

The types of RO used in performing CFRA herein may include but are not limited to the aforementioned first type RO and/or second type RO.

In some embodiments, the RO used for CFRA may include a first type RO and a second type RO, so that a terminal requiring non-contention access can find a suitable RO as quickly as possible to initiate random access when required.

In some real-time examples, the RO for contention-based random access may also be a first-type RO and/or a second-type RO.

In some embodiments: contention-based random access does not occupy the RO of non-contention random access.

In some embodiments, the second information directly includes configuration information of the RO used by the CFRA, and the second information does not need to be associated with the configured RO.

In some embodiments, the second information indicates whether the CFRA can use the first type of RO. When the second information indicates that the non-contention random access does not use the first type of RO, it is assumed that at least the second type of RO can be used.

In some embodiments, when the second information indicates that CFRA uses the first type of RO, it can be considered that the non-contention random access can use the first type of RO and the second type of RO at the same time.

In some other embodiments, the RO used for non-contention random access is the RO indicated by the second information. For example, if the second information indicates that CFRA uses the first type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the second type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the first type of RO and the second type of RO, the corresponding terminal uses the first type of RO and the second type of RO when performing random access.

The second information indicates that the RO used by CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the first type RO. The second information indicates that the RO used by CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the second type RO.

The CFRA here may be four-step random access and/or two-step random access.

S2105: Initiate random access.

In some embodiments, the random access may be the aforementioned four-step random access and/or two-step random access.

In some embodiments, the RO may be the aforementioned first type RO and/or second type RO.

In some embodiments, the RRC connected terminal selects the RO closest to the current moment from the first type RO and the second type RO for random access.

In some embodiments, if a terminal in an RRC connected state has a random access requirement within a time corresponding to a DL time unit and/or an F time unit, a random access is initiated on a first type RO.

In some embodiments, if an RRC connected terminal supporting the SBFD technology has a random access requirement within the time corresponding to the DL time unit and/or the F time unit, random access is initiated on the first type RO.

In some embodiments, if a terminal in an RRC connected state has a random access requirement within a time corresponding to a UL time unit, a random access is initiated on a first type RO or a second type RO.

In some embodiments, a terminal in RRC connected state has a requirement for random access when performing cell switching.

In some embodiments, an RRC connected terminal has a random access requirement when performing Beam Failure Recovery (BFR).

In some embodiments, a terminal in an RRC idle state and/or an RRC inactive state selects a RO closest to the current moment from the first type RO and the second type RO for random access.

In some embodiments, a terminal in an RRC idle state and/or an RRC inactive state selects an RO from the second type of RO for random access.

Since in the TDD scenario, RO is configured on the SBFD time unit, rather than being limited to RO on the UL time unit, the random access capacity of the cell can be improved, and the random access delay of the terminal with random access requirements near the DL time unit and/or SBFD time unit can be reduced, thereby improving the random access efficiency. For RRC connected terminals with random access requirements based on BFR or cell switching, the rate of BFR and/or cell switching can be accelerated.

FIG2B is an interactive schematic diagram of an RO configuration method according to an embodiment of the present disclosure. As shown in FIG2B , the embodiment of the present disclosure relates to an RO configuration method, which is used in a communication system 100, and the method includes:

S2201: The network device configures the RO on the SBFD time unit.

In some embodiments, the network device may be an access network device.

In some embodiments, the network device configures the RO on the SBFD timeslot.

In some embodiments, the network device configures the RO on the SBFD symbols.

The SBFD symbol here may include: a time unit corresponding to a part of subbands set in DL time, a time unit corresponding to a part of subbands set in flexible (Flexible, F) time, and/or a time unit corresponding to a part of subbands set in UL time.

Since the RO is configured on the SBFD time unit instead of being limited to the UL time unit, the number of RO resources can be increased, thereby improving the random access capacity of the system. On the other hand, the RO is set in the DL time unit and/or the F time unit, so that the random access of the terminal with demand in the DL time unit/or the F time unit can be met in time, thereby at least reducing the random access delay of this part of the terminals and improving the random access efficiency.

In some embodiments, the first type of RO can be used by any terminal supporting the SBFD technology.

In some embodiments, considering that the RRC connected terminal needs to restore the RRC connection with the network device as soon as possible through random access to ensure the continuity of transmission and the reachability of the terminal, the first type of RO can be used by the RRC connected terminal.

In some embodiments, the first type RO is not used for RRC idle state and/or RRC inactive state terminals.

In some embodiments, the first type of RO may be used by terminals supporting SBFD technology and in RRC connected state.

S2202: The network device sends a system message.

In some embodiments, the system message includes first configuration information.

In some embodiments, the system message may include a set of configuration information of the RO, namely, the aforementioned first configuration information.

The system message may include one or more system information blocks (SIBs).

In an embodiment, the RO indicated by the first configuration information may include a first type RO configured on a SBFD time unit and a second type RO configured on a UL time unit.

In some embodiments, the network device may also send a configuration of the time unit, for example, a configuration related to the ratio of the TDD radio frame. Thus, the terminal may determine the distribution of the SBFD, UL time unit and/or DL time unit in the time domain according to the configuration.

In some embodiments, FIG5C is a schematic diagram of the configuration of a RO.

S2303: The network device sends the first information.

In some embodiments, the network device broadcasts, multicasts, or unicasts the first information.

In some embodiments, the first information may indicate terminal information capable of using the first type of RO.

In some embodiments, the first information is for a terminal that can use a first type of RO located in a downlink time and/or a flexible time of a SBFD time unit.

In some embodiments, the SBFD time unit may be configured on an uplink time unit, a downlink time unit and/or a flexible time.

In some embodiments, the first information is also used to indicate the terminals that can use the RO located in the uplink time unit. If the first information indicates the terminals on the UL time unit, it is equivalent to indicating the terminals indicated by the first information to use the second type of RO, and the remaining terminals can use the first type of RO.

Exemplarily, the terminal information may include identification information of the terminal, a group identification of a group to which the terminal belongs, and/or type information of the terminal and/or Or attribute information. The type information indicates the type of the terminal, which may be related to the delay sensitivity of the terminal's service tolerance. The attribute information may indicate the capabilities of the terminal, etc.

In some embodiments, the first information may be a component of a system message that sends the configuration information of the RO, that is, the configuration information of the RO and the first information are carried in the same system message.

In some embodiments, the first information can be sent by multicast PDCCH or RRC dedicated signaling or MAC control element (CE) to the terminal that can use the first type RO.

In this way, the terminal will determine whether it can use the first type of RO according to the first information.

In some embodiments, the first information may also indicate a condition for using the first type of RO. In this way, a terminal that meets the condition can use the first type of RO. For example, the network device broadcasts the first information. After receiving the first information, the terminal determines the condition for using the first type of RO, so that the first type of RO can be used when the condition is met.

The conditions for using the first type of RO may include but are not limited to:

An RRC state for using the first type of RO, where the RRC state may include an RRC connected state, an RRC idle state and/or an RRC inactive state. For example, the condition may allow a terminal in an RRC connected state to use the first type of RO, while prohibiting a terminal in an RRC idle state and/or an RRC inactive state from using the first type of RO;

A triggering event for random access using the first type of RO may include, but is not limited to: cell switching, beam failure recovery, a radio link failure (RLF) event of an RRC connected terminal, and cell reselection; for example, the first type of RO may be allowed to be used for cell switching and/or beam failure recovery;

The time range and/or spatial range of the first type of RO is used.

In some embodiments, sending the first information by the network device is an optional step.

After receiving the system message, some terminals automatically ignore the RO configured on the SBFD time unit, that is, automatically avoid using the RO on the SBFD time unit.

For example, a terminal in an RRC idle state and/or an RRC inactive state automatically does not use the RO on the SBFD time unit, while a terminal in an RRC connected state considers that it can use the RO on the SBFD time unit.

For example, a terminal that does not support the SBFD technology automatically does not use the RO in the SBFD time unit, while a terminal that supports the SBFD technology considers that it can use the RO in the SBFD time unit.

In some other embodiments, which terminals can use the first type RO or which terminals are prohibited from using the first type RO can be agreed upon by a protocol, and then the network device side does not send the first information.

S2204: The network device sends second information.

In some embodiments, the network device sends RRC dedicated signaling including the second information.

In some embodiments, the network device sends a PDCCH signaling including the second information. The PDCCH signaling may include but is not limited to DCI.

In some embodiments, the second information may indicate to perform non-contention random access.

In some embodiments, the second information may instruct the RRC connected terminal to perform non-contention random access.

In some embodiments, the second information may be carried in RRC dedicated signaling different from the configuration information of the RO.

Exemplarily, when a cell is switched for an RRC connected terminal, the second information may be carried in a cell switching command. That is, while the cell switching command instructs the RRC connected terminal to switch the cell, the second information carried in the cell switching command is used to switch the RRC connected terminal to the target cell using non-competitive random access during the random access process.

In some embodiments, the terminal uses beam communication, and the second information is carried in the network signaling where the beam configuration or beam failure configuration of the terminal communication is located. In this way, when the RRC connected terminal performs beam recovery, it naturally uses non-contention random access for random access.

In some embodiments, the second information may further include one or more non-contention random access parameters, which may be used for the non-contention random access of the terminal.

Exemplarily, the parameter includes but is not limited to at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in the time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in the uplink time unit.

Exemplarily, the second information indicates a range of random access preamble codes of CFRA, and when performing CFRA, the terminal may randomly select one within the range indicated by the second information to perform non-contention random access.

In some embodiments, the resource index of the RO may be prach-ConfigIndex and/or PRACH Mask Index, both of which can determine the resource location of the RO.

The types of RO used in performing CFRA herein may include but are not limited to the aforementioned first type RO and/or second type RO.

In some embodiments, the RO used for CFRA may include a first type RO and a second type RO, so that a terminal requiring non-contention access can find a suitable RO as quickly as possible to initiate random access when required.

In some real-time examples, the RO for contention-based random access may also be a first-type RO and/or a second-type RO.

In some embodiments: contention-based random access does not occupy the RO of non-contention random access.

In some embodiments, the second information directly includes configuration information of the RO used by the CFRA, and does not need to be associated with the configured RO.

In some embodiments, the second information indicates whether the CFRA can use the first type of RO. When the second information indicates that the non-contention random access does not use the first type of RO, it is assumed that at least the second type of RO can be used.

In some embodiments, when the second information indicates that CFRA uses the first type of RO, it can be considered that the non-contention random access can use the first type of RO and the second type of RO at the same time.

In some other embodiments, the RO used for non-contention random access is the RO indicated by the second information. For example, if the second information indicates that CFRA uses the first type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the second type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the first type of RO and the second type of RO, the corresponding terminal uses the first type of RO and the second type of RO when performing random access.

The second information indicates that the RO used by CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the first type RO. The second information indicates that the RO used by CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the second type RO.

The CFRA here may be four-step random access and/or two-step random access.

S2205: Initiate random access.

In some embodiments, the random access may be the aforementioned four-step random access and/or two-step random access.

In some embodiments, the RO may be the aforementioned first type RO and/or second type RO.

In some embodiments, the RRC connected terminal selects the RO closest to the current moment from the first type RO and the second type RO for random access.

In some embodiments, if a terminal in an RRC connected state has a random access requirement within a time corresponding to a DL time unit and/or an F time unit, a random access is initiated on a first type RO.

In some embodiments, if an RRC connected terminal supporting the SBFD technology has a random access requirement within the time corresponding to the DL time unit and/or the F time unit, random access is initiated on the first type RO.

In some embodiments, if a terminal in an RRC connected state has a random access requirement within a time corresponding to a UL time unit, a random access is initiated on a first type RO or a second type RO.

In some embodiments, a terminal in RRC connected state has a requirement for random access when performing cell switching.

In some embodiments, an RRC connected terminal has a random access requirement when performing Beam Failure Recovery (BFR).

In some embodiments, a terminal in an RRC idle state and/or an RRC inactive state selects a RO closest to the current moment from the first type RO and the second type RO for random access.

In some embodiments, a terminal in an RRC idle state and/or an RRC inactive state selects an RO from the second type of RO for random access.

Since in the TDD scenario, RO is configured on the SBFD time unit, rather than being limited to RO on the UL time unit, the random access capacity of the cell can be improved, and the random access delay of the terminal with random access requirements near the DL time unit and/or SBFD time unit can be reduced, thereby improving the random access efficiency. For RRC connected terminals with random access requirements based on BFR or cell switching, the rate of BFR and/or cell switching can be accelerated.

As shown in FIG3A , an embodiment of the present disclosure provides a random access channel opportunity RO configuration method, which is executed by a network device. The method may include:

S3101: The network device configures the RO on the SBFD time unit.

In some embodiments, the network device may be an access network device.

In some embodiments, the network device may be various devices such as a base station.

In some embodiments, optional embodiments of S3101 may refer to the relevant description of S2101 in the corresponding embodiment of FIG. 2A .

S3102: Send RRC dedicated signaling.

In some embodiments, the RRC dedicated signaling includes configuration information of the first type RO.

In some embodiments, optional embodiments of S3102 may refer to the relevant description of S2102 of the corresponding embodiment of FIG. 2A .

S3103: Send system message.

In some embodiments, the system message includes configuration information of the second type RO.

In some embodiments, the second type RO is configured on an uplink time unit.

In some embodiments, the optional implementation of S3103 can refer to S2103 of the corresponding embodiment of FIG. 2A .

It is worth noting that, in addition to being configured in different time units, the first type RO and the second type RO also have differences as described in the corresponding embodiment of FIG. 2A .

For example, in some cases, the time-frequency domain locations of the first type RO and the second type RO are different.

In some other embodiments, the time-frequency domain positions of the first type RO and the second type RO are the same, but the corresponding RA-RNTIs are different.

There are many different specific RA-RNTI methods. For details, please refer to the relevant part of the embodiment corresponding to Figure 2A, which will not be repeated here.

Since the resource locations of the first type RO and the second type RO do not overlap, the time-frequency domain locations of the RO used when selecting message 1 or message A for random access are naturally different, and the RA-RNTI calculated by the terminal and the network device according to the time-frequency domain locations of the RO are naturally different. In this way, it is obvious that the RA-RNTIs of the terminals using the first type RO and the second type RO for random access will be naturally distinguished, so that the random access responses of different terminals can be naturally distinguished when sending random access Msg2 and MsgB subsequently.

It is worth noting that the formula for calculating RA-RNTI at this time can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

In a scenario where the resource locations of the first type RO and the second type RO do not overlap, the frequency domain locations of the first type RO and the second type RO may be different. For example, the first type RO and the second type RO use frequency division multiplexing and may be configured on different carriers or subcarriers or subbands.

In other embodiments, the resource location of the first type RO and the resource location of the second type RO are mainly reflected in: different frequency domain locations or different time domain locations.

Exemplarily, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or the subframe where the second type RO is located is different from the subframe where the first type RO is located, or the wireless frame where the second type RO is located is different from the wireless frame where the first type RO is located, or the time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO.

In some embodiments, the resource location of the first type RO and the resource location of the second type RO may overlap. Exemplarily, the candidate resource locations of the first type RO and the second type RO may be the same, then the random access response radio network temporary identifier RA-RNTI of the second type RO is different from the random access response radio network temporary identifier RA-RNTI of the first type RO. The difference in RA-RNTI corresponding to the first type RO and the second type RO can be distinguished by at least one of the following methods.

For example, RA-RATI can be calculated based on the frequency domain index of the RO. In this case, by making the frequency domain index of the first type of RO different from the frequency domain index of the second type of RO, the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO are different.

For another example, when RA-RNTI is calculated according to the index corresponding to the time-frequency domain position of the RO, one or more offsets may be introduced so that the RA-RNTI corresponding to the first type of RO is different from the RA-RNTI corresponding to the second type of RO.

Exemplarily, the frequency domain index of the second type of RO is obtained by continuing to number the frequency domain index of the first type of RO, or the frequency domain index of the first type of RO is obtained by continuing to number the frequency domain index of the second type of RO. In this implementation, it is equivalent to pulling the frequency domain indexes of the first type of RO and the second type of RO together.

For example, if there are M first-class ROs in the frequency domain, the frequency domain index of the first-class RO is obtained by numbering the M ROs from 0 or 1 according to the frequency domain position from high to low or from low to high. Further, after the first-class RO is numbered, the second-class RO is numbered from M or M+1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. In this way, even if the first-class RO and the second-class RO are located in the same frequency domain range, it is obvious that the frequency domain indexes of the first-class RO and the second-class RO will be different. Here, M is the number of the first-class ROs frequency-division multiplexed in the frequency domain.

For another example, if there are S second-class ROs in the frequency domain, then the S are numbered from 0 or 1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. Further, after the second-class RO is numbered, the first-class RO is numbered from S or S+1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. In this way, even if the first-class RO and the second-class RO are located in the same frequency domain range, it is obvious that the frequency domain indexes of the first-class RO and the second-class RO will be different. Here, S is the number of second-class ROs frequency-division multiplexed in the frequency domain.

In both embodiments, the frequency domain indexes of the first type of RO and the frequency domain indexes of the second type of RO are numbered consecutively.

In this embodiment, since the configuration information of the second type RO is sent by system message and the configuration information of the first type RO is sent by RRC dedicated signaling, the RO frequency division multiplexing number M of the first type RO is carried in the system message, or the RO frequency division multiplexing number S of the second type RO is carried in the RRC dedicated signaling.

For another example, the starting indexes of the frequency domain index of the first type RO and the frequency domain index of the second type RO are different.

In some embodiments, the starting index of the first type of RO starts from 0, and the starting index of the second type of RO starts from the specified position of the network device or the position agreed upon by the protocol. And the starting index of the second type of RO will avoid the range of the frequency domain index of the first type of RO. In this case, optionally, the system message may carry the starting index of the frequency domain index of the second type RO.

In other embodiments, the starting index of the second type RO starts from 0, and the starting index of the first type RO can be specified by the network device or agreed upon by the protocol. In this case, the starting index of the first type RO will avoid the range of the frequency domain index of the second type RO. In this case, optionally, the RRC dedicated signaling can carry the starting index of the frequency domain index of the first type RO.

In this embodiment, the frequency domain index of the first type of RO and the frequency domain index of the second type of RO may be continuous or discontinuous, depending on the number of frequency division multiplexing of different types of ROs and the setting position of the starting index.

Similarly, when the frequency domain index of the first type RO is different from the frequency domain index of the second type RO, the formula for calculating the RA-RNTI value can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

In other embodiments, the resource position of the first type RO and the resource position of the second type RO may be the same, and the frequency domain index of the first type RO and the frequency domain index of the second type RO may also start from the same position. For example, the frequency domain index of the first type RO and the frequency domain index of the second type RO are both numbered from 0 or 1. At this time, in order to distinguish the RA-RNTI corresponding to the first type RO and the second type RO, one or more parameters for calculating the RA-RNTI may be introduced.

In the embodiment of the present disclosure, at least one offset is introduced into the formula for calculating the RA-RNTI.

Example 1: An offset (which may be referred to as a first offset) is introduced into the calculation formula for the RA-RNTI of the first type of RO, and the size of the offset may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the RRC dedicated signaling where the configuration information of the first type of RO is located.

Example 2: An offset (which may be referred to as a second offset) is introduced into the calculation formula for the RA-RNTI of the second type of RO, and the size of the offset may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the system message where the configuration information of the second type of RO is located.

Example 3: Different offsets may be introduced into the calculation formulas for the first type RO and the second type RO, respectively, so that the RA-RNTI corresponding to the first type RO and the second type RO can also be distinguished. The sizes of these two offsets may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the system message or the RRC dedicated signaling, respectively.

When using Example 1 or Example 2, it is only necessary to introduce an offset into the calculation of RA-RNTI corresponding to the first type RO or the second type RO. When using Example 3, an offset for calculating RA-RNTI is introduced into the first type RO and the second type RO respectively.

For example, MSGB-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2+offset.

MSG1-RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+offset.

MSGB-RNTI may be the RA-RNTI for two-step random access, MSG1-RA-RNTI may be the RA-RNTI for four-step random access, and offset may be the offset introduced above.

The offsets for two-step random access and four-step random access for one type of RO may be the same or different. If the offset is indicated by the network device, the two-step random access and four-step random access for one type of RO may be the same, thereby reducing the instruction overhead of the network device.

S3104: The network device sends the second information.

In some embodiments, the network device sends RRC dedicated signaling including the second information.

In some embodiments, the network device sends a PDCCH signaling including the second information. The PDCCH signaling may include but is not limited to DCI.

In some embodiments, the second information may indicate to perform non-contention random access.

In some embodiments, the second information may instruct the RRC connected terminal to perform non-contention random access.

In some embodiments, the second information may be carried in RRC dedicated signaling different from the configuration information of the RO.

Exemplarily, when a cell is switched for an RRC connected terminal, the second information may be carried in a cell switching command. That is, while the cell switching command instructs the RRC connected terminal to switch the cell, the second information carried in the cell switching command is used to switch the RRC connected terminal to the target cell using non-competitive random access during the random access process.

In some embodiments, the terminal uses beam communication, and the second information is carried in the network signaling where the beam configuration or beam failure configuration of the terminal communication is located. In this way, when the RRC connected terminal performs beam recovery, it naturally uses non-contention random access for random access.

In some embodiments, the second information may further include one or more non-contention random access parameters, which may be used for the non-contention random access of the terminal.

Exemplarily, the parameter includes but is not limited to at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in the time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in the uplink time unit.

Exemplarily, the second information indicates a range of random access preamble codes of CFRA, and when performing CFRA, the terminal may randomly select one within the range indicated by the second information to perform non-contention random access.

In some embodiments, the resource index of the RO may be prach-ConfigIndex and/or PRACH Mask Index, both of which can determine the resource location of the RO.

The types of RO used in performing CFRA herein may include but are not limited to the aforementioned first type RO and/or second type RO.

In some embodiments, the RO used for CFRA may include a first type RO and a second type RO, so that a terminal requiring non-contention access can find a suitable RO as quickly as possible to initiate random access when required.

In some real-time examples, the RO for contention-based random access may also be a first-type RO and/or a second-type RO.

In some embodiments: contention-based random access does not occupy the RO of non-contention random access.

In some embodiments, the second information directly includes configuration information of the RO used by the CFRA, and does not need to be associated with the configured RO.

In some embodiments, the second information indicates whether the CFRA can use the first type of RO. When the second information indicates that the non-contention random access does not use the first type of RO, it is assumed that at least the second type of RO can be used.

In some embodiments, when the second information indicates that CFRA uses the first type of RO, it can be considered that the non-contention random access can use the first type of RO and the second type of RO at the same time.

In some other embodiments, the RO used for non-contention random access is the RO indicated by the second information. For example, if the second information indicates that CFRA uses the first type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the second type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the first type of RO and the second type of RO, the corresponding terminal uses the first type of RO and the second type of RO when performing random access.

The second information indicates that the RO used by CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the first type RO. The second information indicates that the RO used by CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the second type RO.

The CFRA here may be four-step random access and/or two-step random access.

Worth noting:

Some embodiments may include: S3101 to S3104, that is, S3105 is an optional step. At this time, the terminals that can use the first type RO and the second type RO may be agreed upon by the protocol, or indicated by the configuration information carrying the first type RO or by the system message carrying the second type RO.

Some embodiments may include: S3101 to S3102, that is, S3103-S3105 are optional steps. At this time, the network device adds a configuration of RO on the SBFD time unit, and may or may not configure RO on the UL time unit. In the case where RO is not configured on the UL time unit, it is obviously not necessary to execute S3103 to S3105. In the case where RO is configured on the UL time unit, both types of RO can be directly sent to the terminal through RRC dedicated signaling through RO, and the subsequent S3103 to S3105 can also be omitted.

As shown in FIG3B , an embodiment of the present disclosure provides a random access channel opportunity RO configuration method, which is executed by a network device. The method may include:

S3201: The network device configures the RO on the SBFD time unit.

In some embodiments, the network device may be an access network device.

In some embodiments, the network device may be various devices such as a base station.

In some embodiments, optional embodiments of S3201 may refer to the relevant description of S2201 in the corresponding embodiment of FIG. 2B .

S3202: Send system message.

In some embodiments, the system message includes first configuration information. The first configuration information is used to indicate the RO.

In some embodiments, the RO may include a first type RO configured on a SBFD time unit and/or a second type RO configured on a UL time unit.

In some embodiments, the first configuration information may be used to indicate both the first type RO and the second type RO.

The system message may include one or more system information blocks (SIBs).

The RO indicated by the first configuration information may include:

The first type of RO is configured on the SBFD time unit;

The second type of RO is configured on the UL time unit.

S3203: The network device sends the first information.

In some embodiments, the network device broadcasts, multicasts, or unicasts the first information.

In some embodiments, the first information may indicate terminal information capable of using the first type of RO.

In some embodiments, the first information is used to enable the use of the first information located in the downlink time and/or flexible time of the SBFD time unit. A type of RO terminal.

In some embodiments, the first information is also used to indicate the terminals that can use the RO located in the uplink time unit. If the first information indicates the terminals on the UL time unit, it is equivalent to indicating the terminals indicated by the first information to use the second type of RO, and the remaining terminals can use the first type of RO.

Exemplarily, the terminal information may include identification information of the terminal, a group identification of a group to which the terminal belongs, and/or type information and/or attribute information of the terminal. The type information indicates the type of the terminal, which may be related to the delay sensitivity of the terminal's service tolerance. The attribute information may indicate the capability of the terminal, etc.

In some embodiments, the first information may be a component of a system message that sends the configuration information of the RO, that is, the configuration information of the RO and the first information are carried in the same system message.

In some embodiments, the first information can be sent by multicast PDCCH or RRC dedicated signaling or MAC control element (CE) to the terminal that can use the first type RO.

In this way, the terminal will determine whether it can use the first type of RO according to the first information.

In some embodiments, the first information may also indicate a condition for using the first type of RO. In this way, a terminal that meets the condition can use the first type of RO. For example, the network device broadcasts the first information. After receiving the first information, the terminal determines the condition for using the first type of RO, so that the first type of RO can be used when the condition is met.

The conditions for using the first type of RO may include but are not limited to:

An RRC state for using the first type of RO, where the RRC state may include an RRC connected state, an RRC idle state and/or an RRC inactive state. For example, the condition may allow a terminal in an RRC connected state to use the first type of RO, while prohibiting a terminal in an RRC idle state and/or an RRC inactive state from using the first type of RO;

A triggering event for random access using the first type of RO may include, but is not limited to: cell switching, beam failure recovery, connection recovery, and cell reselection; for example, the first type of RO may be allowed to be used for cell switching, beam failure recovery, and/or connection recovery;

The time range and/or spatial range of the first type of RO is used.

In some embodiments, sending the first information by the network device is an optional step.

After receiving the system message, some terminals automatically ignore the RO configured on the SBFD time unit, that is, automatically avoid using the RO on the SBFD time unit.

For example, a terminal in an RRC idle state and/or an RRC inactive state automatically does not use the RO on the SBFD time unit, while a terminal in an RRC connected state considers that it can use the RO on the SBFD time unit.

For example, a terminal that does not support the SBFD technology automatically does not use the RO in the SBFD time unit, while a terminal that supports the SBFD technology considers that it can use the RO in the SBFD time unit.

In some other embodiments, which terminals can use the first type RO or which terminals are prohibited from using the first type RO can be agreed upon by a protocol, and then the network device side does not send the first information.

S3204: The network device sends the second information.

In some embodiments, the network device sends RRC dedicated signaling including the second information.

In some embodiments, the network device sends a PDCCH signaling including the second information. The PDCCH signaling may include but is not limited to DCI.

In some embodiments, the second information may indicate to perform non-contention random access.

In some embodiments, the second information may instruct the RRC connected terminal to perform non-contention random access.

In some embodiments, the second information may be carried in RRC dedicated signaling different from the configuration information of the RO.

Exemplarily, when a cell is switched for an RRC connected terminal, the second information may be carried in a cell switching command. That is, while the cell switching command instructs the RRC connected terminal to switch the cell, the second information carried in the cell switching command is used to switch the RRC connected terminal to the target cell using non-competitive random access during the random access process.

In some embodiments, the terminal uses beam communication, and the second information is carried in the network signaling where the beam configuration or beam failure configuration of the terminal communication is located. In this way, when the RRC connected terminal performs beam recovery, it naturally uses non-contention random access for random access.

In some embodiments, the second information may further include one or more non-contention random access parameters, which may be used for the non-contention random access of the terminal.

Exemplarily, the parameter includes but is not limited to at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in the time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in the uplink time unit.

Exemplarily, the second information indicates a range of random access preamble codes of CFRA, and when performing CFRA, the terminal may randomly select one within the range indicated by the second information to perform non-contention random access.

In some embodiments, the resource index of the RO may be prach-ConfigIndex and/or PRACH Mask Index, both of which can determine the resource location of the RO.

The types of RO used in performing CFRA herein may include but are not limited to the aforementioned first type RO and/or second type RO.

In some embodiments, the RO used for CFRA may include a first type RO and a second type RO, so that a terminal requiring non-contention access can find a suitable RO as quickly as possible to initiate random access when required.

In some real-time examples, the RO for contention-based random access may also be a first-type RO and/or a second-type RO.

In some embodiments: contention-based random access does not occupy the RO of non-contention random access.

In some embodiments, the second information directly includes configuration information of the RO used by the CFRA, and does not need to be associated with the configured RO.

In some embodiments, the second information indicates whether the CFRA can use the first type of RO. When the second information indicates that the non-contention random access does not use the first type of RO, it is assumed that at least the second type of RO can be used.

In some embodiments, when the second information indicates that CFRA uses the first type of RO, it can be considered that the non-contention random access can use the first type of RO and the second type of RO at the same time.

In some other embodiments, the RO used for non-contention random access is the RO indicated by the second information. For example, if the second information indicates that CFRA uses the first type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the second type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the first type of RO and the second type of RO, the corresponding terminal uses the first type of RO and the second type of RO when performing random access.

The second information indicates that the RO used by CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the first type RO. The second information indicates that the RO used by CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the second type RO.

The CFRA here may be four-step random access and/or two-step random access.

Worth noting:

Some embodiments may include: S3201 to S3102, that is, S3105 is an optional step. At this time, the terminals that can use the first type RO and the second type RO may be agreed upon by the protocol, or indicated by the configuration information carrying the first type RO or by the system message carrying the second type RO.

Some embodiments may include: S3101 to S3102, that is, S3103-S3105 are optional steps. At this time, the network device adds a configuration of RO on the SBFD time unit, and may or may not configure RO on the UL time unit. In the case where RO is not configured on the UL time unit, it is obviously not necessary to execute S3103 to S3105. In the case where RO is configured on the UL time unit, both types of RO can be directly sent to the terminal through RRC dedicated signaling through RO, and the subsequent S3103 to S3105 can also be omitted.

As shown in FIG4A , an embodiment of the present disclosure provides an information processing method, which may include:

S4101: The terminal receives configuration information of the RO.

In some embodiments, the RO may include at least a first type of RO configured on a SBFD time unit.

In some embodiments, the first type of RO is used for random access of terminals in radio resource control RRC connected state.

In some embodiments, the first type of RO is used for random access of terminals that support SBFD technology and are in RRC connected state.

In some embodiments, the terminal may receive the configuration information of the RO, including:

The terminal receives RRC dedicated signaling, where the RRC dedicated signaling includes configuration information of the first type RO, and/or,

The terminal receives a system message; the system message includes configuration information of the second type RO.

In some embodiments, the second type RO is configured on an uplink time unit.

In some embodiments, the second type of RO can be used by any type of terminal.

In some embodiments, the second type of RO may be a public RO.

In some embodiments, the first type RO and the second type RO resource locations do not overlap.

In some embodiments, the candidate resource locations of the first type RO and the second type RO do not overlap.

Since the resource locations of the first type RO and the second type RO do not overlap, the time-frequency domain locations of the RO used when selecting message 1 or message A for random access are naturally different, and the RA-RNTI calculated by the terminal and the network device according to the time-frequency domain locations of the RO are naturally different. In this way, it is obvious that the RA-RNTIs of the terminals using the first type RO and the second type RO for random access will be naturally distinguished, so that the random access responses of different terminals can be naturally distinguished when sending random access Msg2 and MsgB subsequently.

It is worth noting that the formula for calculating RA-RNTI at this time can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

In a scenario where the resource locations of the first type RO and the second type RO do not overlap, the frequency domain locations of the first type RO and the second type RO may be different. For example, the first type RO and the second type RO use frequency division multiplexing and may be configured on different carriers or subcarriers or subbands.

In some other embodiments, the time-frequency domain positions of the first type RO and the second type RO are different mainly in terms of time domain positions.

Exemplarily, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or,

The subframe where the second type RO is located is different from the subframe where the first type RO is located, or,

The radio frame where the second type RO is located is different from the radio frame where the first type RO is located, or

The time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO.

In some embodiments, the time-frequency domain positions of the first type RO and the second type RO may overlap. Exemplarily, the candidate resource positions of the first type RO and the second type RO may be the same, then the RA-RNTI corresponding to the second type RO is different from the RA-RNTI corresponding to the first type RO. The difference in the RA-RNTI corresponding to the first type RO and the second type RO can be distinguished by at least one of the following methods.

For example, RA-RATI may be calculated according to the frequency domain index of the RO. In this case, the frequency domain index of the first type of RO is different from the frequency domain index of the second type of RO, so that the RA-RNTIs corresponding to the first type of RO and the second type of RO are different.

For another example, when RA-RNTI is calculated according to the index corresponding to the time-frequency domain position of the RO, one or more offsets may be introduced so that the RA-RNTI corresponding to the first type of RO and the second type of RO are different.

Exemplarily, the frequency domain index of the second type of RO is obtained by continuing to number the frequency domain index of the first type of RO, or the frequency domain index of the first type of RO is obtained by continuing to number the frequency domain index of the second type of RO. In this implementation, it is equivalent to pulling the frequency domain indexes of the first type of RO and the second type of RO together.

For example, if there are M first-class ROs in the frequency domain, the frequency domain index of the first-class RO is obtained by numbering the M ROs from 0 or 1 according to the frequency domain position from high to low or from low to high. Further, after the first-class RO is numbered, the second-class RO is numbered from M or M+1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. In this way, even if the first-class RO and the second-class RO are located in the same frequency domain range, it is obvious that the frequency domain indexes of the first-class RO and the second-class RO will be different. Here, M is the number of the first-class ROs frequency-division multiplexed in the frequency domain.

For another example, if there are S second-class ROs in the frequency domain, then the S are numbered from 0 or 1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. Further, after the second-class RO is numbered, the first-class RO is numbered from S or S+1 according to the frequency domain position from high to low or from low to high to obtain the frequency domain index of the second-class RO. In this way, even if the first-class RO and the second-class RO are located in the same frequency domain range, it is obvious that the frequency domain indexes of the first-class RO and the second-class RO will be different. Here, S is the number of second-class ROs frequency-division multiplexed in the frequency domain.

In both embodiments, the frequency domain indexes of the first type of RO and the frequency domain indexes of the second type of RO are numbered consecutively.

In this embodiment, since the configuration information of the second type RO is sent by system message and the configuration information of the first type RO is sent by RRC dedicated signaling, the RO frequency division multiplexing number M of the first type RO is carried in the system message, or the RO frequency division multiplexing number S of the second type RO is carried in the RRC dedicated signaling.

For another example, the starting index of the frequency domain index of the first type RO is different from the starting index of the frequency domain index of the second type RO.

In some embodiments, the starting index of the first type of RO starts from 0, and the starting index of the second type of RO starts from the specified position of the network device or the position agreed upon by the protocol. And the starting index of the second type of RO will avoid the range of the frequency domain index of the first type of RO. In this case, optionally, the system message can carry the starting index of the frequency domain index of the second type of RO.

In other embodiments, the starting index of the second type RO starts from 0, and the starting index of the first type RO can be specified by the network device or agreed upon by the protocol. In this case, the starting index of the first type RO will avoid the range of the frequency domain index of the second type RO. In this case, optionally, the RRC dedicated signaling can carry the starting index of the frequency domain index of the first type RO.

In this embodiment, the frequency domain index of the first type of RO and the frequency domain index of the second type of RO may be continuous or discontinuous, depending on the number of frequency division multiplexing of different types of ROs and the setting position of the starting index.

Similarly, when the frequency domain index of the first type RO is different from the frequency domain index of the second type RO, the formula for calculating the RA-RNTI value can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

In other embodiments, the resource position of the first type RO and the resource position of the second type RO may be the same, and the frequency domain index of the first type RO and the frequency domain index of the second type RO may also start from the same position. For example, the frequency domain index of the first type RO and the frequency domain index of the second type RO are both numbered from 0 or 1. At this time, in order to distinguish the RA-RNTI corresponding to the first type RO and the second type RO, one or more parameters for calculating the RA-RNTI may be introduced.

In the embodiment of the present disclosure, at least one offset is introduced into the formula for calculating the RA-RNTI.

Example 1: An offset (which may be referred to as a first offset) is introduced into the calculation formula for the RA-RNTI of the first type of RO. The size of the offset may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the RRC dedicated signaling where the configuration information of the first type RO is located.

Example 2: An offset (which may be referred to as a second offset) is introduced into the calculation formula for the RA-RNTI of the second type of RO, and the size of the offset may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the system message where the configuration information of the second type of RO is located.

Example 3: Different offsets may be introduced into the calculation formulas for the first type RO and the second type RO, respectively, so that the RA-RNTI corresponding to the first type RO and the second type RO can also be distinguished. The sizes of these two offsets may be specified by the network device or agreed upon by the protocol. If specified by the network device, the value of the offset specified by the network device may be carried in the system message or the RRC dedicated signaling, respectively.

When using Example 1 or Example 2, it is only necessary to introduce an offset into the calculation of RA-RNTI corresponding to the first type RO or the second type RO. When using Example 3, an offset for calculating RA-RNTI is introduced into the first type RO and the second type RO respectively.

For example, MSGB-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2+offset.

MSG1-RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+offset.

MSGB-RNTI may be the RA-RNTI for two-step random access, MSG1-RA-RNTI may be the RA-RNTI for four-step random access, and offset may be the offset introduced above.

The offsets for two-step random access and four-step random access for one type of RO may be the same or different. If the offset is indicated by the network device, the two-step random access and four-step random access for one type of RO may be the same, thereby reducing the instruction overhead of the network device.

S4102: The terminal receives the second information.

In some embodiments, the second information instructs the RRC connected terminal to perform non-contention random access CFRA.

In some embodiments, the second information indicates at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in a time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in an uplink time unit.

Exemplarily, the second information indicates a range of random access preamble codes of CFRA, and when performing CFRA, the terminal may randomly select one within the range indicated by the second information to perform non-contention random access.

In some embodiments, the resource index of the RO may be prach-ConfigIndex and/or PRACH Mask Index, both of which can determine the resource location of the RO.

The types of RO used in performing CFRA herein may include but are not limited to the aforementioned first type RO and/or second type RO.

In some embodiments, the RO used for CFRA may include a first type RO and a second type RO, so that a terminal requiring non-contention access can find a suitable RO as quickly as possible to initiate random access when required.

In some real-time examples, the RO for contention-based random access may also be a first-type RO and/or a second-type RO.

In some embodiments: contention-based random access does not occupy the RO of non-contention random access.

In some embodiments, the second information directly includes configuration information of the RO used by the CFRA, and does not need to be associated with the configured RO.

In some embodiments, the second information indicates whether the CFRA can use the first type of RO. When the second information indicates that the non-contention random access does not use the first type of RO, it is assumed that at least the second type of RO can be used.

In some embodiments, when the second information indicates that CFRA uses the first type of RO, it can be considered that the non-contention random access can use the first type of RO and the second type of RO at the same time.

In some other embodiments, the RO used for non-contention random access is the RO indicated by the second information. For example, if the second information indicates that CFRA uses the first type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the second type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the first type of RO and the second type of RO, the corresponding terminal uses the first type of RO and the second type of RO when performing random access.

The second information indicates that the RO used by CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the first type RO. The second information indicates that the RO used by CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the second type RO.

The CFRA here may be four-step random access and/or two-step random access.

S4103: Initiate random access.

In some embodiments, the random access may be the aforementioned four-step random access and/or two-step random access.

In some embodiments, initiating random access may include: sending Msg1 or MsgB of random access in the RO.

In some embodiments, the RO may be the aforementioned first type RO and/or second type RO.

In some embodiments, the RRC connected terminal selects the RO closest to the current moment from the first type RO and the second type RO for random access.

In some embodiments, if a terminal in an RRC connected state has a random access requirement within a time corresponding to a DL time unit and/or an F time unit, a random access is initiated on a first type RO.

In some embodiments, if an RRC connected terminal supporting the SBFD technology has a random access requirement within the time corresponding to the DL time unit and/or the F time unit, random access is initiated on the first type RO.

In some embodiments, if a terminal in an RRC connected state has a random access requirement within a time corresponding to a UL time unit, a random access is initiated on a first type RO or a second type RO.

In some embodiments, a terminal in RRC connected state has a requirement for random access when performing cell switching.

In some embodiments, an RRC connected terminal has a random access requirement when performing Beam Failure Recovery (BFR).

In some embodiments, a terminal in an RRC idle state and/or an RRC inactive state selects a RO closest to the current moment from the first type RO and the second type RO for random access.

In some embodiments, a terminal in an RRC idle state and/or an RRC inactive state selects an RO from the second type of RO for random access.

Since in the TDD scenario, RO is configured on the SBFD time unit, rather than being limited to RO on the UL time unit, the random access capacity of the cell can be improved, and the random access delay of the terminal with random access requirements near the DL time unit and/or SBFD time unit can be reduced, thereby improving the random access efficiency. For RRC connected terminals with random access requirements based on BFR or cell switching, the rate of BFR and/or cell switching can be accelerated.

It is worth noting that some embodiments may include S4101; that is, S4101 to S4103 are optional steps. At this time, for example, if the terminal receives the configuration information of the RO but has no random access requirement, then S4103 does not need to be executed. For example, the terminal receives the configuration information of the RO and can determine whether it adopts non-competitive random access according to the protocol agreement, then it does not need to receive the second information from the network device at this time.

Some embodiments may include: S4101 to S4102, that is, S4103 is an optional step. For example, if the terminal receives the configuration information of the RO but has no random access requirement, S4103 does not need to be executed.

As shown in FIG4B , the present disclosure provides an information processing method, which may include:

S4201: The terminal receives a system message.

In some embodiments, the system message includes first configuration information.

In some embodiments, the first configuration information may be used to indicate an RO. Optionally, the RO may include a first type RO and/or a second type RO.

In some embodiments, the first type of RO is configured on a SBFD time unit.

In some embodiments, the second type RO is configured on a UL time unit.

In some embodiments, the first type of RO is used for random access of terminals in radio resource control RRC connected state.

In some embodiments, the first type of RO is used for random access of terminals supporting the SBFD technology.

S4202: The terminal receives first information.

In some embodiments, the first information is at least used to determine a terminal that can use the first type of RO.

In some embodiments, the first information is used for a terminal that can use the first type of RO located in a downlink time unit and/or a flexible time unit of a SBFD time unit.

In some embodiments, the network device broadcasts, multicasts, or unicasts the first information.

In some embodiments, the first information may indicate terminal information capable of using the first type of RO.

In some embodiments, the first information is for a terminal that can use a first type of RO located in a downlink time and/or a flexible time of a SBFD time unit.

In some embodiments, the first information is also used to indicate the terminals that can use the RO located in the uplink time unit. If the first information indicates the terminals on the UL time unit, it is equivalent to indicating the terminals indicated by the first information to use the second type of RO, and the remaining terminals can use the first type of RO.

Exemplarily, the terminal information may include identification information of the terminal, a group identification of a group to which the terminal belongs, and/or type information and/or attribute information of the terminal. The type information indicates the type of the terminal, which may be related to the delay sensitivity of the terminal's service tolerance. The attribute information may indicate the capability of the terminal, etc.

In some embodiments, the first information may be a component of a system message that sends the configuration information of the RO, that is, the configuration information of the RO and the first information are carried in the same system message.

In some embodiments, the first information may be sent to the terminal that can use the first type of RO via a multicast PDCCH or RRC dedicated signaling or a MAC control element (CE).

In this way, the terminal will determine whether it can use the first type of RO according to the first information.

In some embodiments, the first information may also indicate a condition for using the first type of RO. In this way, a terminal that meets the condition can use the first type of RO. For example, the network device broadcasts the first information. After receiving the first information, the terminal determines the condition for using the first type of RO, so that the first type of RO can be used when the condition is met.

The conditions for using the first type of RO may include but are not limited to at least one of the following: the RRC state of using the first type of RO, which RRC state may include an RRC connected state, an RRC idle state and/or an RRC inactive state. For example, the condition may allow a terminal in an RRC connected state to use the first type of RO, while prohibiting terminals in an RRC idle state and/or an RRC inactive state from using the first type of RO; a triggering event for random access using the first type of RO, which may include but is not limited to: cell switching, beam failure recovery, connection recovery, cell reselection; for example, the use of the first type of RO may be allowed for cell switching, beam failure recovery and/or connection recovery; the time range and/or spatial range for using the first type of RO, etc.

In some embodiments, sending the first information by the network device is an optional step.

After receiving the system message, some terminals automatically ignore the RO configured on the SBFD time unit, that is, automatically avoid using the RO on the SBFD time unit.

For example, a terminal in an RRC idle state and/or an RRC inactive state automatically does not use the RO on the SBFD time unit, while a terminal in an RRC connected state considers that it can use the RO on the SBFD time unit.

For example, a terminal that does not support the SBFD technology automatically does not use the RO in the SBFD time unit, while a terminal that supports the SBFD technology considers that it can use the RO in the SBFD time unit.

In some other embodiments, which terminals can use the first type RO or which terminals are prohibited from using the first type RO can be agreed upon by a protocol, and then the network device side does not send the first information.

S4203: The network device sends the second information.

In some embodiments, the network device sends RRC dedicated signaling including the second information.

In some embodiments, the network device sends a PDCCH signaling including the second information. The PDCCH signaling may include but is not limited to DCI.

In some embodiments, the second information may indicate to perform non-contention random access.

In some embodiments, the second information may instruct the RRC connected terminal to perform non-contention random access.

In some embodiments, the second information may be carried in RRC dedicated signaling different from the configuration information of the RO.

Exemplarily, when a cell is switched for an RRC connected terminal, the second information may be carried in a cell switching command. That is, while the cell switching command instructs the RRC connected terminal to switch the cell, the second information carried in the cell switching command is used to switch the RRC connected terminal to the target cell using non-competitive random access during the random access process.

In some embodiments, the terminal uses beam communication, and the second information is carried in the network signaling where the beam configuration or beam failure configuration of the terminal communication is located. In this way, when the RRC connected terminal performs beam recovery, it naturally uses non-contention random access for random access.

In some embodiments, the second information may further include one or more non-contention random access parameters, which may be used for the non-contention random access of the terminal.

Exemplarily, the parameter includes but is not limited to at least one of the following: a random access preamble code used by CFRA; a resource index of the RO used by CFRA; a type of RO used by CFRA; configuration information of the RO used by CFRA; whether the RO used by CFRA is located in the time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in the uplink time unit.

Exemplarily, the second information indicates a range of random access preamble codes of CFRA, and when performing CFRA, the terminal may randomly select one within the range indicated by the second information to perform non-contention random access.

In some embodiments, the resource index of the RO may be prach-ConfigIndex and/or PRACH Mask Index, both of which can determine the resource location of the RO.

The types of RO used in performing CFRA herein may include but are not limited to the aforementioned first type RO and/or second type RO.

In some embodiments, the RO used for CFRA may include a first type RO and a second type RO, so that a terminal requiring non-contention access can find a suitable RO as quickly as possible to initiate random access when required.

In some real-time examples, the RO for contention-based random access may also be a first-type RO and/or a second-type RO.

In some embodiments: contention-based random access does not occupy the RO of non-contention random access.

In some embodiments, the second information directly includes configuration information of the RO used by the CFRA, and does not need to be associated with the configured RO.

In some embodiments, the second information indicates whether the CFRA can use the first type of RO. When the second information indicates that the non-contention random access does not use the first type of RO, it is assumed that at least the second type of RO can be used.

In some embodiments, when the second information indicates that CFRA uses the first type of RO, it can be considered that the non-contention random access can use the first type of RO and the second type of RO at the same time.

In some other embodiments, the RO used for non-contention random access is the RO indicated by the second information. For example, if the second information indicates that CFRA uses the first type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the second type of RO, the corresponding terminal uses the first type of RO when performing random access. If the second information indicates that CFRA uses the first type of RO and the second type of RO, the corresponding terminal uses the first type of RO and the second type of RO when performing random access.

The second information indicates that the RO used by CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the first type RO. The second information indicates that the RO used by CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal when CFRA is the second type RO.

The CFRA here may be four-step random access and/or two-step random access.

S4204: Initiate random access.

It is worth noting that: some embodiments may include S4201; that is, S4201 to S4204 are optional steps. At this time, for example, if the terminal receives the configuration information of the RO, but there is no random access requirement, then there is no need to execute S4103. For example, the terminal receives the configuration information of the RO and can determine whether it adopts non-competitive random access and uses the first type of RO according to the protocol agreement. In this case, there is no need to receive the second information and the first information from the network device.

Some embodiments may include: S4201 to S4202, that is, S4203 and S4204 are optional steps. For example, if the protocol stipulates or pre-configures a terminal, condition or scenario indicating non-random access, there is no need to receive the second information.

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

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

The embodiments of the present disclosure also provide a device for implementing any of the above methods, for example, a device is provided, the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods. For another example, another device is provided, including a unit or module for implementing each step performed by a network device (for example, an access network device, or a core network device, etc.) in any of the above methods.

It should be understood that the division of the units or modules in the above device is only a division of logical functions, which can be fully or partially integrated into one physical entity or physically separated in actual implementation. In addition, the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device. Alternatively, the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits. The hardware circuits may be understood as one or more processors; for example, in one implementation, the hardware circuits are application-specific integrated circuits (ASICs), and the functions of some or all of the above units or modules may be implemented by designing the logical relationship of the components in the circuits; for another example, in another implementation, the hardware circuits may be implemented by programmable logic devices (PLDs), and Field Programmable Gate Arrays (FPGAs) may be used as an example, which may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured by configuring the configuration files, thereby implementing the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented in the form of software called by the processor, or in the form of hardware circuits, or in the form of software called by the processor, and the remaining part may be implemented in the form of hardware circuits.

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

FIG6A is a network device provided by an embodiment of the present disclosure, including:

The processing module 110 is configured to configure a first type of RO on a sub-band full-duplex SBFD time unit.

In some embodiments, the network device further includes a receiving module and/or a sending module.

In some embodiments, the receiving module and/or the sending module may correspond to specific structures such as an antenna or a network interface of the terminal.

It is worth noting that the processing module of the network device can execute any step related to information processing in the RO configuration method executed by the terminal. The sending module can be used for any step related to receiving in the RO configuration method executed by the network device. The sending module can be used for any step related to sending in the RO configuration method executed by the network device.

Based on the above solution, the first type of RO is used for random access of terminals in radio resource control RRC connected state.

Based on the above solution, the first type of RO is used for random access of terminals that support SBFD technology and are in RRC connected state.

Based on the above solution, the sending module of the network device is configured to send RRC dedicated signaling; the RRC dedicated signaling includes configuration information of the first type RO.

Based on the above solution, the sending module of the network device is configured to send a system message, the system message includes the configuration information of the second type RO, and the second type RO is configured on the uplink time unit.

Based on the above solution, the resource locations of the second type RO and the first type RO do not overlap.

Based on the above scheme, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or,

The subframe where the second type RO is located is different from the subframe where the first type RO is located, or,

The radio frame where the second type RO is located is different from the radio frame where the first type RO is located, or

The time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO.

Based on the above solution, the resource location of the second type RO overlaps with the resource location of the first type RO, and the RA-RNTI corresponding to the second type RO is different from the RA-RNTI corresponding to the first type RO.

Based on the above solution, the frequency domain index of the first type RO is different from the frequency domain index of the second type RO.

Based on the above solution, the frequency domain index of the second type RO is obtained by continuing to number the frequency domain index of the first type RO, or the frequency domain index of the first type RO is obtained by continuing to number the frequency domain index of the second type RO.

Based on the above solution, the system message includes: the number of the first type of ROs in frequency division multiplexing.

Based on the above solution, the RRC dedicated signaling also includes the starting index of the frequency domain index of the first type RO; the starting index of the frequency domain index is outside the index range corresponding to the frequency domain index of the second type RO.

Based on the above solution, the RA-RNTI corresponding to the first type of RO is generated according to the offset, and the RA-RNTI corresponding to the second type of RO is not generated according to the offset.

Based on the above solution, the RA-RNTI corresponding to the first type RO and the RA-RNTI corresponding to the second type RO are both generated according to the offset, and the offset corresponding to the first type RO is different from the offset corresponding to the second type RO.

Based on the above solution, the sending module of the network device is configured to send a system message; the system message includes first configuration information, and the RO indicated by the first configuration information includes a first type RO and a second type RO; the second type RO is configured on the uplink time unit.

Based on the above solution, the sending module of the network device is configured to send first information; the first information is at least used to determine the terminal that can use the first type of RO.

Based on the above solution, the first information is used for terminals that can use the first type of RO in the downlink time and/or flexible time of the SBFD time unit.

Based on the above solution, the first information is also used to indicate the terminal that can use the RO located in the uplink time unit.

Based on the above solution, the sending module of the network device is configured to send second information, where the second information instructs the RRC connected terminal to perform non-contention random access CFRA.

Based on the above scheme, the second information indicates at least one of the following: the random access preamble code used by CFRA; the resource index of the RO used by CFRA; the type of RO used by CFRA; the configuration information of the RO used by CFRA; whether the RO used by CFRA is located in the time unit of SBFD; the RO used by CFRA is located in SBFD; the RO used by CFRA is located in the uplink time unit.

FIG6B is a schematic diagram of the structure of a terminal provided in an embodiment of the present disclosure. As shown in FIG7B , the master node includes:

The receiving module 120 is configured to receive configuration information, where the RO indicated by the configuration information includes a first type of RO located in a SBFD time unit.

In some embodiments, the receiving module and the sending module may correspond to specific structures such as an antenna or a network interface of the terminal.

Optionally, the terminal further includes a storage module and/or a processing module, and the storage module may be configured to store information. The processing module may be configured to execute steps related to information processing in the information processing method executed by the terminal.

Based on the above solution, the first type of RO is used for random access of terminals in radio resource control RRC connected state.

Based on the above solution, the receiving module is configured to receive radio resource control RRC dedicated signaling, where the RRC dedicated signaling includes configuration information of the first type of RO.

Based on the above solution, the receiving module of the terminal is further configured to receive a system message, which includes configuration information of the second type RO; the second type RO is configured on the uplink time unit.

Based on the above solution, the resource locations of the second type RO and the first type RO do not overlap.

Based on the above scheme, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or,

The subframe where the second type RO is located is different from the subframe where the first type RO is located, or,

The radio frame where the second type RO is located is different from the radio frame where the first type RO is located, or

The time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO.

Based on the above solution, the resource location of the second type RO overlaps with the resource location of the first type RO, and the RA-RNTI corresponding to the second type RO is different from the RA-RNTI corresponding to the first type RO.

Based on the above solution, RA-RNTI is generated according to the frequency domain index; the frequency domain index of the first type RO is different from the frequency domain index of the second type RO.

Based on the above solution, the frequency domain index of the first type of RO is different from the frequency domain index of the second type of RO;

The frequency domain index of the second type of RO is obtained by continuing to number the frequency domain index of the first type of RO, or the frequency domain index of the first type of RO is obtained by continuing to number the frequency domain index of the second type of RO.

Based on the above solution, the system message includes: the number of the first type of ROs in frequency division multiplexing.

Based on the above solution, the RRC dedicated signaling also includes the starting index of the frequency domain index of the first type RO; the starting index of the frequency domain index is outside the index range corresponding to the frequency domain index of the second type RO.

Based on the above solution, the RA-RNTI corresponding to the first type of RO is generated according to the offset, and the RA-RNTI corresponding to the second type of RO is not generated according to the offset.

Based on the above solution, the RA-RNTI corresponding to the first type RO and the RA-RNTI corresponding to the second type RO are both generated according to the offset, and the offset corresponding to the first type RO is different from the offset corresponding to the second type RO.

Based on the above solution, configuration information is received, including:

receiving a system message; the system message includes first configuration information, the RO indicated by the first configuration information includes a first type RO and a second type RO; the second type RO is configured on an uplink time unit;

Receive first information; the first information is at least used to determine a terminal that can use the first type of RO.

Based on the above solution, the first information is used for terminals that can use the first type of RO in the downlink time and/or flexible time of the SBFD time unit.

Based on the above solution, the first information is also used to indicate the terminal that can use the RO located in the uplink time unit.

Based on the above solution, the receiving module of the terminal is configured to receive second information, where the second information instructs the RRC connected terminal to perform non-contention random access CFRA.

Based on the above solution, the second information indicates at least one of the following:

Implement the random access preamble used by CFRA;

The resource index of the RO used to execute CFRA;

The type of RO used to perform CFRA;

Execute the configuration information of the RO used by CFRA;

Whether the RO used to perform CFRA is located on the time unit of SBFD;

The RO used to perform CFRA is located in SBFD;

The RO used to perform CFRA is located in the uplink time unit.

An embodiment of the present disclosure further provides a communication device, which may include: one or more processors; wherein the processor is used to call instructions so that the communication device executes a method that can be implemented in any of the aforementioned embodiments.

7A and/or 7B, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memory 8102 may also be outside the communication device 8100.

The communication device may be the aforementioned terminal and network device. In some embodiments, the network device may be a primary node and/or an auxiliary node.

In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101. implement.

In some embodiments, the transceiver may include a receiver and a transmitter, and the receiver and the transmitter may be separate or integrated. Optionally, the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, etc. may be replaced with each other, the terms such as transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.

Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuit 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

7B is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure. In the case where the communication device 8100 may be a chip or a chip system, reference may be made to the schematic diagram of the structure of the chip 8200 shown in FIG. 7B , but the present invention is not limited thereto.

The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above RO configuration methods.

In some embodiments, the chip 8200 further includes one or more interface circuits 8202, which are connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and the interface circuit 8202 can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read the instructions stored in the memory 8203 and send the instructions to the processor 8201. Optionally, the terms such as interface circuit, interface, transceiver pin, and transceiver can be replaced with each other.

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

The present disclosure also provides a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 8100, the communication device 8100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but it can also be a storage medium readable by other devices. Optionally, the storage medium can be a non-transitory storage medium, but it can also be a temporary storage medium.

The present disclosure also provides a program product, and when the program product is executed by the communication device 8100, the communication device 8100 executes any one of the above RO configuration methods. Optionally, the program product is a computer program product.

The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above RO configuration methods.

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

It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims (42)

A method for configuring a random access channel opportunity RO, wherein the method is performed by a network device, and the method comprises: The first type of RO is configured on the sub-band full-duplex SBFD time unit. The method according to claim 1, wherein the first type RO is used for random access of terminals in radio resource control RRC connected state. The method according to claim 2, wherein the first type of RO is used to support random access of SBFD technology. The method according to any one of claims 1 to 3, wherein the method further comprises: sending RRC dedicated signaling; the RRC dedicated signaling includes configuration information of the first type RO. The method according to any one of claims 1 to 4, wherein the method further comprises: sending a system message, wherein the system message comprises configuration information of the second type RO, and the second type RO is configured on an uplink time unit. The method according to claim 5, wherein the resource location of the second type RO and the resource location of the first type RO do not overlap. The method according to claim 6, wherein the time slot where the second type RO is located is different from the time slot where the first type RO is located, or the subframe where the second type RO is located is different from the subframe where the first type RO is located, or the wireless frame where the second type RO is located is different from the wireless frame where the first type RO is located, or the time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO. The method according to claim 5, wherein the resource locations of the second type RO and the first type RO overlap, and the random access response radio network temporary identifier RA-RNTI of the second type RO is different from the random access response radio network temporary identifier RA-RNTI of the first type RO. The method according to claim 8, wherein the frequency domain index of the first type RO is different from the frequency domain index of the second type RO. The method according to claim 9, wherein the frequency domain index of the second type RO is obtained by continuing to number the frequency domain index of the first type RO, or the frequency domain index of the first type RO is obtained by continuing to number the frequency domain index of the second type RO. The method according to claim 10, wherein the system message includes: the number of the first type of ROs that are frequency-division multiplexed. The method according to claim 9, wherein the RRC dedicated signaling also includes a starting index of the frequency domain index of the first type RO; the starting index of the frequency domain index is outside the index range corresponding to the frequency domain index of the second type RO. The method according to claim 8, wherein the RA-RNTI corresponding to the first type RO is generated according to the offset, and the RA-RNTI corresponding to the second type RO is not generated according to the offset. The method according to claim 8, wherein the RA-RNTI corresponding to the first type RO and the RA-RNTI corresponding to the second type RO are both generated according to an offset, and the offset corresponding to the first type RO and the offset corresponding to the second type RO are different. The method according to any one of claims 1 to 3, wherein the method further comprises: Sending a system message; the system message includes first configuration information, the RO configured by the first configuration information includes the first type RO and the second type RO; the second type RO is configured on an uplink time unit; Sending first information; the first information is at least used to determine a terminal that can use the first type of RO. The method according to claim 15, wherein the first information is used for terminals that can use the first type of RO within the downlink time and/or flexible time of the SBFD time unit. The method according to claim 16, wherein the first information is also used to indicate a terminal that can use the RO located in the uplink time unit. The method according to any one of claims 1 to 17, wherein the method further comprises: sending second information, wherein the second information instructs the RRC connected terminal to perform non-contention random access CFRA. The method according to claim 18, wherein the second information indicates at least one of the following: a random access preamble code used by the CFRA; a resource index of the RO used by the CFRA; a type of the RO used by the CFRA; configuration information of the RO used by the CFRA; whether the RO used by the CFRA is located in a time unit of SBFD; the RO used by the CFRA is located in SBFD; the RO used by the CFRA is located in an uplink time unit. An information processing method is executed by a terminal, and the method comprises: receiving configuration information, wherein the random access channel opportunity RO indicated by the configuration information comprises a first type of RO located on a sub-band full-duplex SBFD time unit. The method according to claim 20, wherein the first type RO is used for random access of terminals in radio resource control RRC connected state. The method according to claim 20 or 21, wherein the configuration information indicating the first type RO is carried in the wireless resource Controls RRC dedicated signaling. The method according to any one of claims 20 to 22, wherein the method further comprises: receiving a system message, wherein the system message comprises configuration information of the second type RO; and the second type RO is configured on an uplink time unit. The method according to claim 23, wherein the resource location of the second type RO and the resource location of the first type RO do not overlap. The method according to claim 24, wherein the time slot where the second type RO is located is different from the time slot where the first type RO is located, or the subframe where the second type RO is located is different from the subframe where the first type RO is located, or the wireless frame where the second type RO is located is different from the wireless frame where the first type RO is located, or the time slot where the second type RO is located is the same as the time slot where the first type RO is located, and the starting symbol of the second type RO is different from the starting symbol of the first type RO. The method according to claim 24, wherein the resource locations of the second type RO and the first type RO overlap, and the random access response radio network temporary identifier RA-RNTI of the second type RO and the first type RO are different. The method according to claim 26, wherein the frequency domain index of the first type RO is different from the frequency domain index of the second type RO. The method according to claim 27, wherein the frequency domain index of the first type RO is different from the frequency domain index of the second type RO; the frequency domain index of the second type RO is obtained by continuing to number the frequency domain index of the first type RO, or the frequency domain index of the first type RO is obtained by continuing to number the frequency domain index of the second type RO. The method according to claim 28, wherein the system message includes: the number of the first type of ROs that are frequency-division multiplexed. The method according to claim 27, wherein the RRC dedicated signaling also includes a starting index of the frequency domain index of the first type RO; the starting index of the frequency domain index is outside the index range corresponding to the frequency domain index of the second type RO. The method according to claim 26, wherein the RA-RNTI corresponding to the first type RO is generated according to the offset, and the RA-RNTI corresponding to the second type RO is not generated according to the offset. The method according to claim 26, wherein the RA-RNTI corresponding to the first type RO and the RA-RNTI corresponding to the second type RO are both generated according to an offset, and the offset corresponding to the first type RO and the offset corresponding to the second type RO are different. The method according to claim 20 or 21, wherein the receiving configuration information comprises: receiving a system message; the system message includes first configuration information, the RO configured by the first configuration information includes the first type RO and the second type RO; the second type RO is configured on an uplink time unit; Receive first information; the first information is at least used to determine a terminal that can use the first type of RO. The method according to claim 33, wherein the first information is used for terminals that can use the first type of RO within the downlink time and/or flexible time of the SBFD time unit. The method according to claim 34, wherein the first information is also used to indicate a terminal that can use the RO located in the uplink time unit. The method according to any one of claims 20 to 35, wherein the method further comprises: Second information is received, where the second information instructs the RRC connected terminal to perform non-contention random access CFRA. The method according to claim 36, wherein the second information indicates at least one of the following: a random access preamble code used by the CFRA; a resource index of the RO used by the CFRA; a type of the RO used by the CFRA; configuration information of the RO used by the CFRA; whether the RO used by the CFRA is located on a time unit of SBFD; the RO used by the CFRA is located on SBFD; the RO used by the CFRA is located on an uplink time unit. A network device, comprising: The processing module is configured to configure a first type of RO on a sub-band full-duplex SBFD time unit. A terminal, comprising: The receiving module is configured to receive configuration information, wherein the random access channel opportunity RO indicated by the configuration information includes a first type of RO located in a sub-band full-duplex SBFD time unit. A communication device, wherein the communication device comprises: one or more processors; The processor is used to call instructions so that the communication device executes the method described in any one of claims 1 to 19 and/or claims 20 to 37. A storage medium, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the method according to any one of claims 1 to 19 and/or claims 20 to 37. An information processing method, comprising: The network device configures the first type of RO on the sub-band full-duplex SBFD time unit and configures the second type on the uplink UL time unit RO, the bandwidth occupied by the SBFD time unit is smaller than the bandwidth occupied by the UL time unit; The network device sends configuration information of the first type RO and configuration information of the second type RO to the terminal; The terminal receives configuration information of the first RO and configuration information of the second type RO; When the terminal has a random access requirement in the RRC connected state and within the time range of the downlink DL time unit and/or the flexible time unit, the terminal selects to initiate a random access process on the first type RO according to the configuration information of the first type RO; when the terminal has a random access requirement within the time range of the UL time unit, the terminal selects the first type RO or the second type RO with the smallest time domain distance from the current moment to initiate a random access process according to the configuration information of the first type RO and the configuration information of the second type RO; The random access response radio network temporary identifier RA-RNTI corresponding to the first type RO is different from the RA-RNTI corresponding to the second type RO; the RA-RATI is used to scramble the random access response in the random access process.