Random access channel occasion (RO) configuration method, information processing method, device, and storage medium

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

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

[0002] There are two types of time division duplex (TDD) resource configuration: semi-static configuration and dynamic configuration. Semi-static configuration can 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 radio resource control (RRC) signaling. The terminal here can also be referred to as UE. Dynamic TDD resource configuration can be achieved by using the downlink control information (DCI) transmitted by the physical downlink control channel (PDCCH), 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.

[0003] RO can be a resource used by a terminal for random access messages during a random access process. Generally, RO is configured on a UL time unit.

[0004] Summary of the Invention

[0005] Embodiments of the present disclosure provide an RO configuration method, an information processing method, a communication device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a RO configuration method is provided, wherein the method is performed by a network device, and includes: configuring a first type of RO on a subband full duplex (SBFD) time unit.

[0007] According to a second aspect of an embodiment of the present disclosure, an information processing method is provided, which is executed by a terminal. The method includes: receiving configuration information, where the random access channel opportunity RO indicated by the configuration information includes a first type RO located on a sub-band full-duplex SBFD time unit.

[0008] According to a third aspect of an embodiment of the present disclosure, an information processing method is provided, which is executed by a new communication system. The method may include: a network device configuring a first type of RO on a sub-band full-duplex (SBFD) time unit and configuring a second type of RO on an uplink (UL) time unit, where the bandwidth occupied by the SBFD time unit is less than the bandwidth occupied by the UL time unit; the network device sending configuration information of the first type of RO and configuration information of the second type of RO to a terminal; the terminal receiving 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, selecting to initiate a random access process on the first type of RO according to the configuration information of the first type of RO; when the terminal has a random access requirement within a time range of a UL time unit, selecting 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; and the RA-RATI is used to scramble the random access response in the random access process.

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

[0010] 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 RO located on a sub-band full-duplex SBFD time unit.

[0011] According to the 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 to enable the communication device to execute the method provided by any technical solution of the aforementioned first to third aspects.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the method provided in any one of the first to third aspects.

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

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

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

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

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

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

[0019] FIG1D is a schematic diagram showing a two-step random access process according to an exemplary embodiment;

[0020] FIG2A is a schematic flow chart showing a method for configuring an RO according to an exemplary embodiment;

[0021] FIG2B is a schematic flow chart showing a method for configuring an RO according to an exemplary embodiment;

[0022] FIG3A is a schematic flow chart showing a method for configuring an RO according to an exemplary embodiment;

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

[0024] FIG4A is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0025] FIG4B is a flow chart showing an information processing method according to an exemplary embodiment;

[0026] FIG5A is a schematic diagram showing an RO according to an exemplary embodiment;

[0027] FIG5B is a schematic diagram showing an RO according to an exemplary embodiment;

[0028] FIG5C is a schematic diagram showing an RO according to an exemplary embodiment;

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

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

[0031] FIG6B is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0032] FIG7A is a schematic structural diagram of a communication device according to an exemplary embodiment;

[0033] FIG7B is a schematic structural diagram of a chip according to an exemplary embodiment. DETAILED DESCRIPTION

[0034] Embodiments of the present disclosure provide an RO configuration method, an information processing method, a communication device, and a storage medium.

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

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

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

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

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

[0040] 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 of RO.

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

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

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

[0044] In combination with some embodiments of the first aspect, in some embodiments, resource locations of the second-category RO and the first-category RO do not overlap.

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

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

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

[0048] 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 radio network temporary identifier RA-RNTI corresponding to the second type RO is different from the random access response radio network temporary identifier RA-RNTI corresponding to the first type RO.

[0049] 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 through the differentiated setting of RA-RNTI.

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

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

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

[0053] Based on the above solution, by integrating the frequency domain indices of the first type RO and the second type RO within the same time-frequency domain position range, the frequency domain indices of the first type RO and 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 are distinguished.

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

[0055] Based on the above solution, the number of the first type of ROs obtained by frequency division multiplexing is carried in the system message, so that the terminal can know the range of the frequency domain index of the first type of RO, which has the characteristic of simple implementation.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the RRC dedicated signaling further 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.

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

[0058] In combination with some embodiments of the first 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.

[0059] 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 made different.

[0060] 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, 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.

[0061] In some embodiments, both the first and second type ROs are configured using the same set of configuration information. The first configuration information is sent via a system message. This allows the network device to notify the terminal of both the first and second type ROs by sending a system message. The terminal only needs to receive the system message to be aware of the first and second type ROs.

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

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

[0064] In combination with some embodiments of the first aspect, in some embodiments, 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.

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

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

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

[0068] 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 on a time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on an uplink time unit.

[0069] 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, where the random access channel opportunity RO indicated by the configuration information includes a first type of RO on an SBFD time unit.

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

[0071] In combination with some embodiments of the second aspect, 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.

[0072] 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, where the RRC dedicated signaling includes the configuration information of the first type of RO.

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

[0074] In combination with some embodiments of the second aspect, in some embodiments, resource locations of the second-category RO and the first-category RO do not overlap.

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

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

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

[0078] 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; 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.

[0079] With reference to some embodiments of the second aspect, in some embodiments, the system message includes: the number of first-category ROs of frequency division multiplexing.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the RRC dedicated signaling further 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.

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

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

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

[0084] In combination with some embodiments of the second aspect, in some embodiments, 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.

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

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

[0087] 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 on a time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on an uplink time unit.

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

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

[0090] 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 to enable the communication device to execute the method described in the optional implementation of the first aspect and / or the second aspect.

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

[0092] 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, wherein a bandwidth occupied by the SBFD time unit is smaller than a bandwidth occupied by the UL time unit;

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

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

[0095] When the terminal has a random access requirement in an RRC connected state and within a time range of a downlink DL time unit and / or a flexible time unit, the terminal selects, according to the configuration information of the first type of RO, to initiate a random access procedure on a first type of RO; when the terminal has a random access requirement within a time range of a UL time unit, the terminal selects, according to the configuration information of the first type of RO and the configuration information of the second type of RO, 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 procedure;

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

[0097] Based on the above solution, RO is no longer limited to being set on UL time units. In this way, when a terminal has random access requirements within the time range of DL time units and / or F time units, it can use the first type of RO on SBFD time units to complete random access in time.

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

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

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

[0101] It is understandable that the above-mentioned 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 of the corresponding methods and will not be repeated here.

[0102] The present disclosure provides an RO configuration method, communication device, communication system, and storage medium. In some embodiments, the terms RO configuration method, communication method, and information processing method are interchangeable; the terms information indicating device, information processing device, information transmission device, network device, or terminal are interchangeable; and the terms communication system, information processing system, and so on are interchangeable.

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

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

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

[0106] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, 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 articles such as "a", "an", "the" in English are used in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

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

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

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

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

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

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

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

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

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

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

[0118] 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, etc. can be used interchangeably.

[0119] 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 communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the 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.

[0120] 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 have a structure that has all or part of the functions of the terminal.

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

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

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

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

[0125] As shown in Figure 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.

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

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

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

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

[0130] In some embodiments, the core network device may be a single device including a first network element, 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).

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

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

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

[0134] Dynamic configuration for TDD can achieve dynamic resource allocation, improve system performance and efficient frequency utilization, but it may cause cross link interference (CLI).

[0135] SBFD technology was introduced to enhance UL coverage, reduce uplink latency, and increase system capacity and configuration flexibility. SBFD technology allows network devices to transmit and receive simultaneously, while terminals transmit or receive at a single point in time. Therefore, when configuring resources, SBFD time units are introduced in the time domain. Multiple terminals perform uplink transmission and downlink reception on non-overlapping subbands of a single TDD carrier. Figure 1B shows a schematic diagram of a resource configuration. Figure 1B shows five time slots, namely, DL time slots, UL time slots, and SBFD time slots. DL time slots are designated by D. UL time slots are designated by U. SBFD time slots reserve some subbands on DL frequency domain resources for uplink transmission. That is, time slots 2 to 4 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.

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

[0137] FIG1C shows a flow chart of a four-step random access, which may include:

[0138] Step 1: The terminal sends a random access preamble.

[0139] 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) and the physical random access channel (PRACH) resources and random access preambles configured by high-level signaling. It then selects an appropriate group of SSBs for determining the random access preamble based on the RSRP and the threshold. The terminal also determines the range of RACH resources and random access preambles based on the selected SSBs and the corresponding relationship between the SSBs and RACH resources. The RACH resources here include ROs. In some cases, ROs can also be referred to as PRACH opportunities or PRACH resources. Terminal 101 selects a random access preamble group based on the expected message size of message (Msg) 3, and then randomly selects the random access preamble to be used for this random access.

[0140] Terminal 101 sets the target received power of the random access preamble on the network side: preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × powerRampingStep. preambleReceivedTargetPower may be the target power at which the network device receives the random access preamble. powerRampingStep may be the power ramping step size. 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.

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

[0142] A random access response wireless network temporary identification (RA-RNTI) is determined according to a resource index of the PRACH for sending Msg1; and the RA-RNTI is calculated.

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

[0144] 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 based on the subcarrier spacing. f_id is the frequency domain index of the RO. Exemplarily, 0≤f_id<8. ul_carrier_id indicates the UL carrier of the random access, which may include a regular UL or a supplementary UL (SUL) carrier. For example, ul_carrier_id equal to 0 indicates that the random access uses the UL carrier. ul_carrier_id equal to 1 indicates that the random access uses the SUL carrier.

[0145] The UE opens a 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.

[0146] If no RAR is received within the RAR time window or the RAR corresponding to the random access preamble sent by itself is not received. That is, if the RAR corresponding to the random access preamble identifier (RAPID) sent by itself is not received, power ramping is performed and msg1 is retransmitted based on the ramped power. In some embodiments, whether to perform uplink transmit power ramping for random access depends on whether beam switching is performed. For example, uplink transmit power ramping may be performed without beam switching, and power ramping may not be performed when beam switching is performed.

[0147] If a RAR is received within the RAR monitoring window, and 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.

[0148] Step 3: Uplink scheduled transmission (Scheduled Transmission).

[0149] If the terminal does not have a Cell-RadioNetworkTemporaryIdentifier (C-RNTI), the execution of the RACH is triggered by the Common Control Channel (CCCH). In this case, Msg3 is a MAC PDU generated with the CCCH Service Data Unit (SDU) as input. If the terminal has a C-RNTI, the UE instructs the multiplexing and assembly entity to include a C-RNTI MAC control element (CE). In this case, Msg3 is a MAC PDU generated by the C-RNTI MAC CE.

[0150] Get the MAC PDU from the Msg3 buffer and transmit the MAC PDU based on the uplink grant (UL Grant) in the RAR.

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

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

[0153] Step 4: Conflict Resolution.

[0154] If Msg3 contains a C-RNTI MAC CE, the terminal monitors the PDCCH scrambled by the C-RNTI. If the terminal monitors Msg3, it considers the conflict resolution successful; if it does not monitor Msg3, it considers the conflict resolution failed.

[0155] If Msg 3 does not include the C-RNTI MAC CE, the terminal monitors the temporary C-RNTI and receives Msg 4. If Msg 4 is received and matches the CCCH SDU, the conflict resolution is successful, otherwise the conflict resolution fails.

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

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

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

[0159] Step 1: The terminal sends a random access preamble.

[0160] The random access preamble is carried in MsgA sent by the terminal.

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

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

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

[0164] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×2

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

[0166] FIG2A is an interactive diagram illustrating 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 for a communication system 100, the method comprising:

[0167] S2101: The network device configures an RO on the SBFD time unit.

[0168] In some embodiments, the network device may be an access network device. In some embodiments, the network device configures RO on the SBFD time slot. In some embodiments, the network device configures RO on the SBFD symbol. The SBFD symbol here may include: being set in a DL time unit, being set in a flexible (Flexible, F) time unit and / or being 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.

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

[0170] 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 F time unit, so that the random access of terminals with demand in the DL time unit / or F time unit can be met in a timely manner, thereby at least reducing the random access delay of these terminals and improving the random access efficiency.

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

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

[0173] S2102: The network device sends RRC dedicated signaling.

[0174] 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 supports SBFD technology and receives the RRC dedicated signaling.

[0175] 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 and subframe number of the system frame (or radio frame) in which the RO is configured, the number of subframes in which the RO is configured in the radio frame in which the RO is configured, the number of time slots in which the RO is configured in a subframe, the time slot number, and / or the duration of the PRAC resource.

[0176] In some embodiments, the configuration information for 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 (e.g., msg1-FDM), the format information for 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 in the configuration information. For example, if the configuration information for the first type of RO configures ROs on two symbols and four ROs using frequency division multiplexing on one symbol, the configuration information configures a total of eight first type ROs, but the number of ROs for frequency division multiplexing is four.

[0177] Figure 5D is a schematic diagram of a PRACH configuration. As shown in Figure 5D, 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 from format 0 to format 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 resource shown in Figure 5D 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 frequency domain starting position of the RO.

[0178] S2103: The network device sends a system message.

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

[0180] The system message may include configuration information of the second type RO. The content of the configuration information for configuring the second type RO may refer to the content of the configuration information for configuring the first type RO, and will not be repeated here.

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

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

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

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

[0185] In some embodiments, the candidate resource locations of the first type RO may be resource locations where the first type RO can be configured.

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

[0187] The non-overlapping resource locations here may include: non-overlapping frequency domain locations and / or time domain configurations.

[0188] 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, thereby achieving a difference in resource position between the first type RO and the second type RO.

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

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

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

[0192] Since the resource locations of the first and second type ROs do not overlap, the resource locations of the ROs used when selecting Message 1 or Message A for random access are naturally different. Therefore, the RA-RNTIs calculated by the terminal and the network device based on the resource index corresponding to the RO's resource location are naturally different. In this way, the RA-RNTIs of terminals using the first and second type ROs for random access are 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.

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

[0194] 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 can be configured on different carriers or subcarriers or subbands.

[0195] In 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.

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

[0197] 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 overlapping may be understood as the resource location being the same.

[0198] In some embodiments, the resource locations of the first type RO and the resource locations of the second type RO can be understood as follows: the candidate resource locations of the first type RO and the candidate resource locations of the second type RO can overlap. For example, the overlapping candidate resource locations can be understood as the same candidate resource locations. In some embodiments, the candidate resource locations of the first type RO can be resource locations where the first type RO can be configured. In some embodiments, the candidate resource locations of the second type RO can be resource locations where the second type RO can be configured.

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

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

[0201] For example, the subband where the second type RO is located may be the same as the subband occupied by the SBFD time unit.

[0202] For example, the candidate resource locations of the first type RO and the candidate resource locations of the second type RO may be the same, and 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.

[0203] For example, the 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 the 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 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 embodiment, it is equivalent to combining the frequency domain indices of the first type of RO and the second type of RO.

[0204] For example, if there are M first-type ROs in the frequency domain, then the M ROs are numbered starting from 0 or 1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the first-type RO. Furthermore, after the first-type ROs are numbered, the second-type ROs are numbered starting from M or M+1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the second-type RO. Using this approach, even if the first-type ROs and the second-type ROs are located in the same frequency domain, the frequency domain index of the first-type RO and the frequency domain index of the second-type RO will obviously be different. Here, M is the number of first-type ROs frequency-division multiplexed in the frequency domain. For another example, if there are S second-type ROs in the frequency domain, then the S ROs are numbered starting from 0 or 1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the second-type RO. Furthermore, after the second-type ROs are numbered, the first-type ROs are numbered starting from S or S+1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the second-type RO. In this way, even if the first-type RO and the second-type RO are located in the same frequency domain, the frequency domain index of the first-type RO and the frequency domain index of the second-type RO will obviously be different. Here, S is the number of second-type ROs frequency-division multiplexed in the frequency domain. In both embodiments, the frequency domain indexes of the first-type RO and the second-type RO are numbered consecutively.

[0205] In this embodiment, since the configuration information for the second-type RO is sent via system messages and the configuration information for the first-type RO is sent via RRC dedicated signaling, the system message carries the frequency-division multiplexing (FDM) number M of the first-type RO, or the RRC dedicated signaling carries the frequency-division multiplexing (FDM) number S of the second-type RO. As shown in Figures 5A and 5B, the FDM number M of the first-type RO is 2. The FDM number of the second-type RO is 4. In Figures 5A and 5B, the FDM number of the RO is represented by the parameter msg1-FDM. In practice, this parameter can also be MsgA-FDM. 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.

[0206] In some embodiments, the starting index of the first type of RO starts at 0, while the starting index of the second type of RO starts at a specified location of the network device or a location agreed upon by the protocol. 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, the system message may optionally carry the starting index of the frequency domain index of the second type of RO.

[0207] In other embodiments, the starting index of the second type RO starts from 0, while 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, RRC dedicated signaling can optionally carry the starting index of the frequency domain index of the first type RO.

[0208] In this embodiment, the frequency domain indexes of the first type of RO and the frequency domain indexes 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.

[0209] 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 can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

[0210] In other embodiments, the resource locations of the first-type RO and the second-type RO may be the same, and the frequency domain indexes of the first-type RO and the second-type RO may also be numbered starting from the same position. For example, the frequency domain indexes of the first-type RO and the second-type RO may both be numbered starting from 0 or 1. In this case, to distinguish the RA-RNTIs corresponding to the first-type RO and the second-type RO, one or more parameters may be introduced to calculate the RA-RNTI. In the embodiments of the present disclosure, at least one offset is introduced into the formula for calculating the RA-RNTI. The offset is used to distinguish the first-type RO from the second-type RO.

[0211] Example 1: An offset (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 can 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 can be carried in the RRC dedicated signaling containing the configuration information of the first type of RO.

[0212] Example 2: An offset (referred to as a second offset) is introduced into the calculation formula for the RA-RNTI of the second type of RO. The size of the offset can 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 can be carried in the system message containing the configuration information of the second type of RO.

[0213] Example 3: Different offsets can be introduced into the calculation formulas for Type 1 and Type 2 ROs, respectively, thereby enabling the distinction of the RA-RNTIs corresponding to Type 1 and Type 2 ROs. The values ​​of these two offsets can be specified by the network device or agreed upon by the protocol. If specified by the network device, the values ​​of the offsets specified by the network device can be carried in system messages or RRC dedicated signaling.

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

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

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

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

[0218] The offsets for two-step random access and four-step random access for a type of RO can 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 a type of RO can be the same, thereby reducing the instruction overhead of the network device.

[0219] S2105: The network device sends the second information.

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

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

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

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

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

[0225] Exemplarily, when a terminal in an RRC connected state switches a cell, the second information may be carried in the cell switching command. That is, while the cell switching command instructs the terminal in the RRC connected state to switch the cell, the second information carried in the cell switching command also instructs the terminal in the RRC connected state to use non-contention random access during the random access process of switching to the target cell.

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

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

[0228] 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 on the time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on the uplink time unit.

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

[0230] In some embodiments, the resource index of the RO may be prach-ConfigIndex and / or PRACH Mask Index, and these indexes may determine the resource location of the RO.

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

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

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

[0234] In some embodiments, contention-based random access does not occupy the RO of non-contention random access.

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

[0236] In some embodiments, the second information indicates whether the CFRA can use the first type of RO. If the second information indicates that the non-contention random access does not use the first type of RO, then at least the second type of RO can be used by default.

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

[0238] In some other embodiments, the RO used for non-contention random access is an 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 both the first type of RO and the second type of RO when performing random access.

[0239] 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 during 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 during CFRA is the second type RO.

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

[0241] S2105: Initiate random access.

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

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

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

[0245] 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, random access is initiated on a first type RO.

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

[0247] 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, random access is initiated on a first-type RO or a second-type RO.

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

[0249] In some embodiments, a terminal in an RRC connected state has a random access requirement when performing beam failure recovery (BFR).

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

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

[0252] In TDD scenarios, RO is configured on SBFD time units, rather than being limited to UL time units. This improves the random access capacity of the cell and reduces the random access delay for terminals with random access requirements near DL time units and / or SBFD time units, improving random access efficiency. For RRC-connected terminals with random access requirements based on BFR or cell handover, the BFR and / or cell handover rates can be accelerated.

[0253] FIG2B is an interactive diagram illustrating 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 for a communication system 100, and the method includes:

[0254] S2201: The network device configures an RO on the SBFD time unit.

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

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

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

[0258] The SBFD symbols herein may include: time units corresponding to some subbands set in DL time, time units corresponding to some subbands set in flexible (Flexible, F) time, and / or time units corresponding to some subbands set in UL time.

[0259] 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 F time unit, so that the random access of terminals with demand in the DL time unit / or F time unit can be met in a timely manner, thereby at least reducing the random access delay of these terminals and improving the random access efficiency.

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

[0261] 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 transmission continuity and terminal reachability, the first type of RO can be used by the RRC connected terminal.

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

[0263] In some embodiments, the first type of RO may be used by terminals that support SBFD technology and are in RRC connected state.

[0264] S2202: The network device sends a system message.

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

[0266] In some embodiments, the system message may include a set of configuration information of the RO, ie, the aforementioned first configuration information.

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

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

[0269] 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, so that the terminal can determine the distribution of SBFD, UL time units and / or DL ​​time units in the time domain based on the configuration.

[0270] In some embodiments, FIG5C shows a schematic diagram of the configuration of an RO.

[0271] S2303: The network device sends the first information.

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

[0273] In some embodiments, the first information may indicate information of terminals capable of using the first type of RO.

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

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

[0276] In some embodiments, the first information is further used to indicate terminals that can use the RO in the uplink time unit. If the first information indicates terminals that can use the RO in the UL time unit, it is equivalent to indicating terminals that the first information indicates can use the second type of RO. At this time, the remaining terminals can all use the first type of RO.

[0277] For example, the terminal information may include terminal identification information, a group identifier of the terminal's group, and / or terminal type information and / or attribute information. The type information indicates the terminal type, which may be related to the delay sensitivity tolerated by the terminal's service. The attribute information may indicate the terminal's capabilities, etc.

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

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

[0280] In this way, the terminal determines whether it can use the first type of RO according to the first information.

[0281] In some embodiments, the first information may also indicate conditions for using the first type of RO. Thus, terminals that meet the conditions can use the first type of RO. For example, a network device broadcasts the first information. After receiving the first information, the terminal determines the conditions for using the first type of RO and can use the first type of RO if the conditions are met.

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

[0283] 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 the RRC connected state to use the first type of RO, while prohibiting a terminal in the RRC idle state and / or the RRC inactive state from using the first type of RO;

[0284] A triggering event for using the first type of RO for random access 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 for cell switching and / or beam failure recovery.

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

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

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

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

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

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

[0291] S2204: The network device sends the second information.

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

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

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

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

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

[0297] Exemplarily, when a terminal in an RRC connected state switches a cell, the second information may be carried in the cell switching command. That is, while the cell switching command instructs the terminal in the RRC connected state to switch the cell, the second information carried in the cell switching command also instructs the terminal in the RRC connected state to use non-contention random access during the random access process of switching to the target cell.

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

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

[0300] 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 on the time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on the uplink time unit.

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

[0302] In some embodiments, the resource index of the RO may be prach-ConfigIndex and / or PRACH Mask Index, and these indexes may determine the resource location of the RO.

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

[0304] 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 necessary.

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

[0306] In some embodiments, contention-based random access does not occupy the RO of non-contention random access.

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

[0308] In some embodiments, the second information indicates whether the CFRA can use the first type of RO. If the second information indicates that the non-contention random access does not use the first type of RO, then at least the second type of RO can be used by default.

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

[0310] In some other embodiments, the RO used for non-contention random access is an 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 both the first type of RO and the second type of RO when performing random access.

[0311] 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 during 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 during CFRA is the second type RO.

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

[0313] S2205: Initiate random access.

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

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

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

[0317] 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, random access is initiated on a first type RO.

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

[0319] 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, random access is initiated on a first-type RO or a second-type RO.

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

[0321] In some embodiments, a terminal in an RRC connected state has a random access requirement when performing beam failure recovery (BFR).

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

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

[0324] In TDD scenarios, RO is configured on SBFD time units, rather than being limited to UL time units. This improves the random access capacity of the cell and reduces the random access delay for terminals with random access requirements near DL time units and / or SBFD time units, improving random access efficiency. For RRC-connected terminals with random access requirements based on BFR or cell handover, the BFR and / or cell handover rates can be accelerated.

[0325] As shown in FIG3A , an embodiment of the present disclosure provides a method for configuring a random access channel opportunity (RO), which is executed by a network device. The method may include:

[0326] S3101: The network device configures an RO on the SBFD time unit.

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

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

[0329] In some embodiments, optional embodiments of S3101 can refer to the relevant description of S2101 in the corresponding embodiment of Figure 2A.

[0330] S3102: Send RRC dedicated signaling.

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

[0332] In some embodiments, optional embodiments of S3102 can refer to the relevant description of S2102 in the corresponding embodiment of Figure 2A.

[0333] S3103: Send system message.

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

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

[0336] In some embodiments, optional implementations of S3103 may refer to S2103 in the corresponding embodiment of FIG. 2A .

[0337] 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 the differences described in the corresponding embodiment of FIG. 2A .

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

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

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

[0341] 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 sending during random access are naturally different, and the RA-RNTIs calculated by the terminal and the network device based on 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.

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

[0343] 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 can be configured on different carriers or subcarriers or subbands.

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

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

[0346] In some embodiments, the resource locations of the first type RO and the resource locations of the second type RO may overlap. For example, the candidate resource locations of the first type RO and the second type RO may be the same, and the random access response radio network temporary identifier (RA-RNTI) of the second type RO may be different from the random access response radio network temporary identifier (RA-RNTI) of 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.

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

[0348] 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 different from the RA-RNTI corresponding to the second type of RO.

[0349] 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 embodiment, the frequency domain indexes of the first type of RO and the second type of RO are combined.

[0350] For example, if there are M first-type ROs in the frequency domain, then the M ROs are numbered starting from 0 or 1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the first-type RO. Furthermore, after the first-type ROs are numbered, the second-type ROs are numbered starting from M or M+1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the second-type RO. Using this approach, even if the first-type RO and the second-type RO are located in the same frequency domain, their frequency domain indexes will obviously be different. Here, M is the number of first-type ROs frequency-division multiplexed in the frequency domain.

[0351] For another example, if there are S second-type ROs in the frequency domain, then the S are numbered starting from 0 or 1 according to their frequency domain positions from high to low or from low to high to obtain the frequency domain index of the second-type RO. Furthermore, after the second-type ROs are numbered, the first-type ROs are numbered starting from S or S+1 according to their frequency domain positions from high to low or from low to high to obtain the frequency domain index of the second-type RO. Using this method, even if the first-type RO and the second-type RO are located in the same frequency domain range, the frequency domain indexes of the first-type RO and the second-type RO will obviously be different. Here, S is the number of second-type ROs frequency-division multiplexed in the frequency domain.

[0352] In both embodiments, the frequency domain indexes of the first type of ROs and the frequency domain indexes of the second type of ROs are numbered consecutively.

[0353] In this embodiment, since the configuration information of the second type of RO is sent by system message and the configuration information of the first type of RO is sent by 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.

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

[0355] In some embodiments, the starting index of the first type of RO starts at 0, while the starting index of the second type of RO starts at a specified location of the network device or a location agreed upon by the protocol. 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, the system message may optionally carry the starting index of the frequency domain index of the second type of RO.

[0356] In other embodiments, the starting index of the second type RO starts from 0, while 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, RRC dedicated signaling can optionally carry the starting index of the frequency domain index of the first type RO.

[0357] In this embodiment, the frequency domain indexes of the first type of RO and the frequency domain indexes 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.

[0358] 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 can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

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

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

[0361] Example 1: An offset (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 can 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 can be carried in the RRC dedicated signaling containing the configuration information of the first type of RO.

[0362] Example 2: An offset (referred to as a second offset) is introduced into the calculation formula for the RA-RNTI of the second type of RO. The size of the offset can 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 can be carried in the system message containing the configuration information of the second type of RO.

[0363] Example 3: Different offsets can be introduced into the calculation formulas for Type 1 and Type 2 ROs, respectively, thereby enabling the distinction of the RA-RNTIs corresponding to Type 1 and Type 2 ROs. The values ​​of these two offsets can be specified by the network device or agreed upon by the protocol. If specified by the network device, the values ​​of the offsets specified by the network device can be carried in system messages or RRC dedicated signaling.

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

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

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

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

[0368] The offsets for two-step random access and four-step random access for a type of RO can 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 a type of RO can be the same, thereby reducing the instruction overhead of the network device.

[0369] S3104: The network device sends the second information.

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

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

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

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

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

[0375] Exemplarily, when a terminal in an RRC connected state switches a cell, the second information may be carried in the cell switching command. That is, while the cell switching command instructs the terminal in the RRC connected state to switch the cell, the second information carried in the cell switching command also instructs the terminal in the RRC connected state to use non-contention random access during the random access process of switching to the target cell.

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

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

[0378] 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 on the time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on the uplink time unit.

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

[0380] In some embodiments, the resource index of the RO may be prach-ConfigIndex and / or PRACH Mask Index, and these indexes may determine the resource location of the RO.

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

[0382] 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 necessary.

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

[0384] In some embodiments, contention-based random access does not occupy the RO of non-contention random access.

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

[0386] In some embodiments, the second information indicates whether the CFRA can use the first type of RO. If the second information indicates that the non-contention random access does not use the first type of RO, then at least the second type of RO can be used by default.

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

[0388] In some other embodiments, the RO used for non-contention random access is an 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 both the first type of RO and the second type of RO when performing random access.

[0389] 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 during 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 during CFRA is the second type RO.

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

[0391] It is worth noting that:

[0392] 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 can be agreed upon by the protocol, or indicated by the configuration information carrying the first type RO or the system message carrying the second type RO.

[0393] Some embodiments may include: S3101 to S3102, i.e., S3103-S3105 are optional steps. In this case, the network device configures an RO in the SBFD time unit, and may or may not configure an RO in the UL time unit. If an RO is not configured in the UL time unit, S3103 to S3105 are obviously not necessary. If an RO is configured in the UL time unit, both types of ROs can be directly sent to the terminal via RRC dedicated signaling, and the subsequent S3103 to S3105 can be omitted.

[0394] As shown in FIG3B , an embodiment of the present disclosure provides a method for configuring a random access channel opportunity (RO), which is executed by a network device. The method may include:

[0395] S3201: The network device configures an RO on the SBFD time unit.

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

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

[0398] In some embodiments, optional embodiments of S3201 can refer to the relevant description of S2201 in the corresponding embodiment of Figure 2B.

[0399] S3202: Send system message.

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

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

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

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

[0404] The RO indicated by the first configuration information may include:

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

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

[0407] S3203: The network device sends the first information.

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

[0409] In some embodiments, the first information may indicate information of terminals capable of using the first type of RO.

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

[0411] In some embodiments, the first information is further used to indicate terminals that can use the RO in the uplink time unit. If the first information indicates terminals that can use the RO in the UL time unit, it is equivalent to indicating terminals that the first information indicates can use the second type of RO. At this time, the remaining terminals can all use the first type of RO.

[0412] For example, the terminal information may include the terminal's identification information, the group identification of the terminal's group, and / or the terminal's type information and / or attribute information. The type information indicates the terminal's type, which may be related to the terminal's service's latency sensitivity tolerance. The attribute information may indicate the terminal's capabilities, etc.

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

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

[0415] In this way, the terminal determines whether it can use the first type of RO according to the first information.

[0416] In some embodiments, the first information may also indicate conditions for using the first type of RO. Thus, terminals that meet the conditions can use the first type of RO. For example, a network device broadcasts the first information. After receiving the first information, the terminal determines the conditions for using the first type of RO and can use the first type of RO if the conditions are met.

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

[0418] 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 the RRC connected state to use the first type of RO, while prohibiting a terminal in the RRC idle state and / or the RRC inactive state from using the first type of RO;

[0419] A triggering event for using the first type of RO for random access 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 for cell switching, beam failure recovery, and / or connection recovery.

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

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

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

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

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

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

[0426] S3204: The network device sends the second information.

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

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

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

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

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

[0432] Exemplarily, when a terminal in an RRC connected state switches a cell, the second information may be carried in the cell switching command. That is, while the cell switching command instructs the terminal in the RRC connected state to switch the cell, the second information carried in the cell switching command also instructs the terminal in the RRC connected state to use non-contention random access during the random access process of switching to the target cell.

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

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

[0435] 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 on the time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on the uplink time unit.

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

[0437] In some embodiments, the resource index of the RO may be prach-ConfigIndex and / or PRACH Mask Index, and these indexes may determine the resource location of the RO.

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

[0439] 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 necessary.

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

[0441] In some embodiments, contention-based random access does not occupy the RO of non-contention random access.

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

[0443] In some embodiments, the second information indicates whether the CFRA can use the first type of RO. If the second information indicates that the non-contention random access does not use the first type of RO, then at least the second type of RO can be used by default.

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

[0445] In some other embodiments, the RO used for non-contention random access is an 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 both the first type of RO and the second type of RO when performing random access.

[0446] 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 during 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 during CFRA is the second type RO.

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

[0448] It is worth noting that:

[0449] 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 can be agreed upon by the protocol, or indicated by the configuration information carrying the first type RO or the system message carrying the second type RO.

[0450] Some embodiments may include: S3101 to S3102, i.e., S3103-S3105 are optional steps. In this case, the network device configures an RO in the SBFD time unit, and may or may not configure an RO in the UL time unit. If an RO is not configured in the UL time unit, S3103 to S3105 are obviously not necessary. If an RO is configured in the UL time unit, both types of ROs can be directly sent to the terminal via RRC dedicated signaling, and the subsequent S3103 to S3105 can be omitted.

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

[0452] S4101: The terminal receives configuration information of the RO.

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

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

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

[0456] In some embodiments, the terminal receiving the RO configuration information may include:

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

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

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

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

[0461] In some embodiments, the second type of RO may be called a public RO.

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

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

[0464] 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 sending during random access are naturally different, and the RA-RNTIs calculated by the terminal and the network device based on 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.

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

[0466] 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 can be configured on different carriers or subcarriers or subbands.

[0467] In some other embodiments, the difference between the time-frequency domain positions of the first type RO and the second type RO is mainly the difference in the time domain positions.

[0468] 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,

[0469] The subframe where the second type of RO is located is different from the subframe where the first type of RO is located, or,

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

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

[0472] In some embodiments, the time-frequency domain locations of the first and second type ROs may overlap. For example, the candidate resource locations of the first and second type ROs may be the same, but 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-RNTIs corresponding to the first and second type ROs can be distinguished by at least one of the following methods.

[0473] 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 second type of RO are different.

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

[0475] 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 embodiment, the frequency domain indexes of the first type of RO and the second type of RO are combined.

[0476] For example, if there are M first-type ROs in the frequency domain, then the M ROs are numbered starting from 0 or 1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the first-type RO. Furthermore, after the first-type ROs are numbered, the second-type ROs are numbered starting from M or M+1 according to their frequency domain positions, either from high to low or from low to high, to obtain the frequency domain index of the second-type RO. Using this approach, even if the first-type RO and the second-type RO are located in the same frequency domain, their frequency domain indexes will obviously be different. Here, M is the number of first-type ROs frequency-division multiplexed in the frequency domain.

[0477] For another example, if there are S second-type ROs in the frequency domain, then the S are numbered starting from 0 or 1 according to their frequency domain positions from high to low or from low to high to obtain the frequency domain index of the second-type RO. Furthermore, after the second-type ROs are numbered, the first-type ROs are numbered starting from S or S+1 according to their frequency domain positions from high to low or from low to high to obtain the frequency domain index of the second-type RO. Using this method, even if the first-type RO and the second-type RO are located in the same frequency domain range, the frequency domain indexes of the first-type RO and the second-type RO will obviously be different. Here, S is the number of second-type ROs frequency-division multiplexed in the frequency domain.

[0478] In both embodiments, the frequency domain indexes of the first type of ROs and the frequency domain indexes of the second type of ROs are numbered consecutively.

[0479] In this embodiment, since the configuration information of the second type of RO is sent by system message and the configuration information of the first type of RO is sent by 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.

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

[0481] In some embodiments, the starting index of the first type of RO starts at 0, while the starting index of the second type of RO starts at a specified location of the network device or a location agreed upon by the protocol. 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, the system message may optionally carry the starting index of the frequency domain index of the second type of RO.

[0482] In other embodiments, the starting index of the second type RO starts from 0, while 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, RRC dedicated signaling can optionally carry the starting index of the frequency domain index of the first type RO.

[0483] In this embodiment, the frequency domain indexes of the first type of RO and the frequency domain indexes 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.

[0484] 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 can refer to the calculation of RA-RANT in the aforementioned four-step random access or two-step random access.

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

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

[0487] Example 1: An offset (referred to as a first offset) is introduced into the calculation formula for the RA-RNTI of a first-type RO. The offset value 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 included in the RRC dedicated signaling containing the configuration information for the first-type RO.

[0488] Example 2: An offset (referred to as a second offset) is introduced into the calculation formula for the RA-RNTI of the second type of RO. The size of the offset can 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 can be carried in the system message containing the configuration information of the second type of RO.

[0489] Example 3: Different offsets can be introduced into the calculation formulas for Type 1 and Type 2 ROs, respectively, thereby enabling the distinction of the RA-RNTIs corresponding to Type 1 and Type 2 ROs. The values ​​of these two offsets can be specified by the network device or agreed upon by the protocol. If specified by the network device, the values ​​of the offsets specified by the network device can be carried in system messages or RRC dedicated signaling.

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

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

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

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

[0494] The offsets for two-step random access and four-step random access for a type of RO can 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 a type of RO can be the same, thereby reducing the instruction overhead of the network device.

[0495] S4102: The terminal receives the second information.

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

[0497] 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 on a time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on an uplink time unit.

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

[0499] In some embodiments, the resource index of the RO may be prach-ConfigIndex and / or PRACH Mask Index, and these indexes may determine the resource location of the RO.

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

[0501] 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 necessary.

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

[0503] In some embodiments, contention-based random access does not occupy the RO of non-contention random access.

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

[0505] In some embodiments, the second information indicates whether the CFRA can use the first type of RO. If the second information indicates that the non-contention random access does not use the first type of RO, then at least the second type of RO can be used by default.

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

[0507] In some other embodiments, the RO used for non-contention random access is an 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 both the first type of RO and the second type of RO when performing random access.

[0508] 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 during 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 during CFRA is the second type RO.

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

[0510] S4103: Initiate random access.

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

[0512] In some embodiments, initiating random access may include: sending Msg1 or MsgB of random access at the RO.

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

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

[0515] 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, random access is initiated on a first type RO.

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

[0517] 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, random access is initiated on a first-type RO or a second-type RO.

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

[0519] In some embodiments, a terminal in an RRC connected state has a random access requirement when performing beam failure recovery (BFR).

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

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

[0522] In TDD scenarios, RO is configured on SBFD time units, rather than being limited to UL time units. This improves the random access capacity of the cell and reduces the random access delay for terminals with random access requirements near DL time units and / or SBFD time units, improving random access efficiency. For RRC-connected terminals with random access requirements based on BFR or cell handover, the BFR and / or cell handover rates can be accelerated.

[0523] It is worth noting that some embodiments may include S4101; that is, S4101 to S4103 are optional steps. In this case, for example, if the terminal receives RO configuration information but does not require random access, S4103 does not need to be executed. For example, after receiving the RO configuration information, the terminal can determine whether to use non-contention random access according to the protocol. In this case, it is not necessary to receive the second information from the network device.

[0524] 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, it is not necessary to execute S4103.

[0525] As shown in FIG4B , an embodiment of the present disclosure provides an information processing method, which may include:

[0526] S4201: The terminal receives a system message.

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

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

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

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

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

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

[0533] S4202: The terminal receives first information.

[0534] In some embodiments, the first information is at least used to determine terminals that can use the first type of RO.

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

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

[0537] In some embodiments, the first information may indicate information of terminals capable of using the first type of RO.

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

[0539] In some embodiments, the first information is further used to indicate terminals that can use the RO in the uplink time unit. If the first information indicates terminals that use the UL time unit, it is equivalent to indicating terminals that the first information indicates use of the second type of RO. At this time, the remaining terminals can all use the first type of RO.

[0540] For example, the terminal information may include the terminal's identification information, the group identification of the terminal's group, and / or the terminal's type information and / or attribute information. The type information indicates the terminal's type, which may be related to the terminal's service's latency sensitivity tolerance. The attribute information may indicate the terminal's capabilities, etc.

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

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

[0543] In this way, the terminal determines whether it can use the first type of RO according to the first information.

[0544] In some embodiments, the first information may also indicate conditions for using the first type of RO. Thus, terminals that meet the conditions can use the first type of RO. For example, a network device broadcasts the first information. After receiving the first information, the terminal determines the conditions for using the first type of RO and can use the first type of RO if the conditions are met.

[0545] 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 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, 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.

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

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

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

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

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

[0551] S4203: The network device sends the second information.

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

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

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

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

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

[0557] Exemplarily, when a terminal in an RRC connected state switches a cell, the second information may be carried in the cell switching command. That is, while the cell switching command instructs the terminal in the RRC connected state to switch the cell, the second information carried in the cell switching command also instructs the terminal in the RRC connected state to use non-contention random access during the random access process of switching to the target cell.

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

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

[0560] 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 on the time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on the uplink time unit.

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

[0562] In some embodiments, the resource index of the RO may be prach-ConfigIndex and / or PRACH Mask Index, and these indexes may determine the resource location of the RO.

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

[0564] 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 necessary.

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

[0566] In some embodiments, contention-based random access does not occupy the RO of non-contention random access.

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

[0568] In some embodiments, the second information indicates whether the CFRA can use the first type of RO. If the second information indicates that the non-contention random access does not use the first type of RO, then at least the second type of RO can be used by default.

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

[0570] In some other embodiments, the RO used for non-contention random access is an 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 both the first type of RO and the second type of RO when performing random access.

[0571] 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 during 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 during CFRA is the second type RO.

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

[0573] S4204: Initiate random access.

[0574] It is worth noting that some embodiments may include S4201; that is, S4201 to S4204 are optional steps. In this case, for example, if the terminal receives RO configuration information but does not require random access, S4103 does not need to be executed. For example, if the terminal receives RO configuration information and can determine whether it uses non-contention random access and the first type of RO according to the protocol, then it does not need to receive the second information and the first information from the network device.

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

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

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

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

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

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

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

[0582] The processing module 110 is configured to configure a first type of RO in a sub-band full-duplex (SBFD) time unit.

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

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

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

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

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

[0588] 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 of RO.

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

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

[0591] Based on the above solution, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or,

[0592] The subframe where the second type of RO is located is different from the subframe where the first type of RO is located, or,

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

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

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

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

[0597] Based on the above solution, 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.

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

[0599] Based on the above solution, the RRC dedicated signaling further 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.

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

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

[0602] 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 ROs indicated by the first configuration information include first-type ROs and second-type ROs; the second-type ROs are configured on the uplink time unit.

[0603] 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 terminals that can use the first type of RO.

[0604] Based on the above solution, 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.

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

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

[0607] 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 the RO used by CFRA; the configuration information of the RO used by CFRA; whether the RO used by CFRA is located on the time unit of SBFD; the RO used by CFRA is located on SBFD; the RO used by CFRA is located on the uplink time unit.

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

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

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

[0611] Optionally, the terminal further includes a storage module and / or a processing module, wherein 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.

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

[0613] 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 RO.

[0614] 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 an uplink time unit.

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

[0616] Based on the above solution, the time slot where the second type RO is located is different from the time slot where the first type RO is located, or,

[0617] The subframe where the second type of RO is located is different from the subframe where the first type of RO is located, or,

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

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

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

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

[0622] 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;

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

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

[0625] Based on the above solution, the RRC dedicated signaling further 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.

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

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

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

[0629] 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;

[0630] First information is received; the first information is at least used to determine a terminal that can use the first type of RO.

[0631] Based on the above solution, 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.

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

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

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

[0635] Execute the random access preamble used by CFRA;

[0636] The resource index of the RO used to execute CFRA;

[0637] The type of RO used to perform CFRA;

[0638] Execute the configuration information of the RO used by CFRA;

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

[0640] The RO used to perform CFRA is located in SBFD;

[0641] The RO used to perform CFRA is located on the uplink time unit.

[0642] 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 to enable the communication device to execute a method that can be implemented in any of the aforementioned embodiments.

[0643] 7A and / or 7B , the communication device 8100 further includes one or more memories 8102 for storing instructions. Alternatively, all or part of the memories 8102 may be located outside the communication device 8100.

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

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

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

[0647] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 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 circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0648] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 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, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0649] 7B is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG7B , but the present disclosure is not limited thereto.

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

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

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

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

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

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

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

[0657] It should be understood that the present invention is not limited to the exact construction 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

1. A method for configuring a random access channel opportunity RO, wherein: Executed by a network device, the method includes: The first type of RO is configured on the sub-band full-duplex SBFD time unit.

2. The method according to claim 1, wherein: The first type of RO is used for random access of terminals in radio resource control RRC connection state.

3. The method according to claim 2, wherein: The first type of RO is used to support random access of the SBFD technology.

4. The method according to any one of claims 1 to 3, wherein: The method further includes: sending RRC dedicated signaling; the RRC dedicated signaling includes configuration information of the first type RO.

5. The method according to any one of claims 1 to 4, wherein: The method further includes: sending a system message, wherein the system message includes configuration information of the second type RO, and the second type RO is configured on an uplink time unit.

6. The method according to claim 5, wherein: The resource location of the second type RO does not overlap with the resource location of the first type RO.

7. 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.

8. The method according to claim 5, wherein: The resource locations of the second type RO and the first type RO overlap, and a random access response radio network temporary identifier RA-RNTI of the second type RO is different from a random access response radio network temporary identifier RA-RNTI of the first type RO.

9. 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.

10. 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.

11. The method according to claim 10, wherein: The system message includes: the number of the first type of ROs that are frequency-division multiplexed.

12. 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.

13. 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.

14. 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 is different from the offset corresponding to the second type RO.

15. 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.

16. The method according to claim 15, wherein: The first information is used for a terminal that can use a first type of RO in a downlink time and / or a flexible time of the SBFD time unit.

17. 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.

18. The method according to any one of claims 1 to 17, wherein: The method further includes: sending second information, wherein the second information instructs the RRC connected terminal to perform non-contention random access CFRA.

19. 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.

20. An information processing method, wherein: The method is performed 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 located in a sub-band full-duplex SBFD time unit.

21. The method according to claim 20, wherein: The first type of RO is used for random access of terminals in radio resource control RRC connection state.

22. The method according to claim 20 or 21, wherein: The configuration information indicating the first type of RO is carried in the radio resource control RRC dedicated signaling.

23. The method according to any one of claims 20 to 22, wherein: The method further includes: receiving a system message, wherein the system message includes configuration information of a second type of RO; and the second type of RO is configured in an uplink time unit.

24. The method according to claim 23, wherein: The resource location of the second type RO does not overlap with the resource location of the first type RO.

25. 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.

26. 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 identifiers RA-RNTI of the second type RO and the first type RO are different.

27. 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.

28. 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.

29. The method according to claim 28, wherein: The system message includes: the number of the first type of ROs that are frequency-division multiplexed.

30. The method of 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.

31. The method of 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.

32. The method of 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 is different from the offset corresponding to the second type RO.

33. The method according to claim 20 or 21, wherein: The receiving configuration information includes: 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.

34. The method of claim 33, wherein: The first information is used for a terminal that can use a first type of RO in a downlink time and / or a flexible time of the SBFD time unit.

35. The method of claim 34, wherein: The first information is also used to indicate a terminal that can use the RO located in the uplink time unit.

36. 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.

37. The method of 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 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.

38. A network device, wherein: include: The processing module is configured to configure a first type of RO on a sub-band full-duplex SBFD time unit.

39. A terminal, wherein: include: 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.

40. 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.

41. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on the communication device, the communication device executes the method according to any one of claims 1 to 19 and / or claims 20 to 37.

42. An information processing method, wherein: include: 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.

Images