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 configuring a first type of RO on a sub-band full duplex (SBFD) time unit.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method for configuring a Radio Access Channel (RO), an information processing method, a device, and a storage medium. Background Technology

[0002] Time Division Duplex (TDD) resource configuration has two types: semi-static and dynamic. 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 typically sent to the terminal via System Information Block (SIB). UE-specific configuration is generally sent to the terminal using Radio Resource Control (RRC) signaling. The terminal here can also be referred to as the UE. Dynamic TDD resource configuration can be achieved by using Downlink Control Information (DCI) transmitted via the Physical Downlink Control Channel (PDCCH) to dynamically change flexible time slots within a certain time window to downlink (DL) or uplink (UL) time slots.

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

[0004] This disclosure provides an RO configuration method, an information processing method, a communication device, and a storage medium.

[0005] According to a first aspect of the present disclosure, an RO configuration method is provided, wherein the method is performed by a network device, the method comprising: configuring a first type of RO on a Subband Full Duplex (SBFD) time unit.

[0006] According to a second aspect of the present disclosure, an information processing method is provided, executed by a terminal, the method comprising: receiving configuration information, wherein the configuration information indicates a random access channel timing (RO) including a first type of RO located on a sub-band full-duplex SBFD time unit.

[0007] According to a third aspect of the present disclosure, an information processing method is provided, executed by a novel communication system. The method may include: a network device configuring a first type of Remote Access Response (RO) on a sub-band full-duplex (SBFD) time unit and a second type of RO on an uplink UL time unit, wherein 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 the second type of RO to a terminal; the terminal receiving the configuration information of the first type of RO and the second type of RO; when the terminal has a random access requirement in RRC connected state and within the time range of the downlink DL time unit and / or flexible time unit, it initiating a random access procedure on the first type of RO based on the configuration information of the first type of RO; when the terminal has a random access requirement within the time range of the UL time unit, it initiating a random access procedure by selecting either the first type of RO or the second type of RO with the smallest time-domain distance to the current time based on the configuration information of the first type of RO and the second type of RO; wherein the random access response radio network temporary identifier (RA-RNTI) corresponding to the first type of RO is different from the RA-RNTI corresponding to the second type of RO; the RA-RNTI is used to scramble the random access response during the random access procedure.

[0008] According to a fourth aspect of the present disclosure, a network device is provided, comprising: a processing module configured to configure a first type of RO on a subband full-duplex SBFD time unit.

[0009] According to a fifth aspect of the present disclosure, a terminal is provided, comprising: a receiving module configured to receive configuration information, wherein the configuration information indicates a random access channel timing (RO) including a first type of RO located on a sub-band full-duplex SBFD time unit.

[0010] According to a sixth aspect of the present disclosure, a communication device is provided, wherein the communication device includes: one or more processors; the processors are configured to invoke instructions to cause the communication device to perform the method provided by any of the technical solutions of the first to third aspects.

[0011] According to a seventh aspect of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions that, when executed on a communication device, cause the communication device to perform the method provided by any one of the first to third aspects.

[0012] The technical solution provided in this disclosure allows the first type of RO to be configured on the SDFB time unit, thus eliminating the need to configure all ROs on the UL time unit. This improves the random access capacity of TDD and allows the terminal to initiate random access on the SBFD time unit without waiting for the UL time slot, thereby reducing the latency of random access.

[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the embodiments of this disclosure. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0015] Figure 1A This is a schematic diagram of the architecture of a communication system according to an exemplary embodiment;

[0016] Figure 1B This is a schematic diagram of an SBFD time unit according to an exemplary embodiment;

[0017] Figure 1C This is a schematic diagram illustrating a four-step random access process according to an exemplary embodiment;

[0018] Figure 1D This is a schematic diagram illustrating a two-step random access process according to an exemplary embodiment;

[0019] Figure 2A This is a flowchart illustrating an RO configuration method according to an exemplary embodiment;

[0020] Figure 2B This is a flowchart illustrating an RO configuration method according to an exemplary embodiment;

[0021] Figure 3A This is a flowchart illustrating an RO configuration method according to an exemplary embodiment;

[0022] Figure 3B This is a flowchart illustrating an RO configuration method according to an exemplary embodiment;

[0023] Figure 4A This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0024] Figure 4B This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0025] Figure 5A This is a schematic diagram of an RO according to an exemplary embodiment;

[0026] Figure 5B This is a schematic diagram of an RO according to an exemplary embodiment;

[0027] Figure 5C This is a schematic diagram of an RO according to an exemplary embodiment;

[0028] Figure 5D This is a schematic diagram illustrating a PRACH resource according to an exemplary embodiment;

[0029] Figure 6A This is a schematic diagram of the structure of a network device according to an exemplary embodiment;

[0030] Figure 6B This is a schematic diagram of the structure of a terminal according to an exemplary embodiment;

[0031] Figure 7A This is a schematic diagram of the structure of a communication device according to an exemplary embodiment;

[0032] Figure 7B This is a schematic diagram of the structure of a chip according to an exemplary embodiment. Detailed Implementation

[0033] This disclosure provides an RO configuration method, an information processing method, a communication device, and a storage medium.

[0034] In a first aspect, embodiments of this disclosure provide an RO configuration method, which includes: configuring a first type of RO on an SBFD time unit.

[0035] In the above embodiments, the first type of RO is configured on the SDFB time unit, so that all ROs do not need to be configured on the UL time unit. On the one hand, the random access capacity of TDD can be improved, and on the other hand, the terminal does not need to wait for the UL time slot to perform random access, but can initiate random access on the SBFD time unit, thereby reducing the latency of random access.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first type of RO is used for random access of Radio Resource Control (RRC) connected-state terminals.

[0037] Based on the above scheme, configuring the first type of RO for use by RRC connected state terminals allows RRC connected state terminals to achieve beam recovery, connection recovery and / or cell handover through random access of the first type of RO, enabling RRC connected state terminals to recover to the reachable state as soon as possible, thereby ensuring the continuity of RRC connected state terminals.

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

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

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

[0041] In conjunction 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 a second type of RO; the second type of RO is configured on an uplink time unit.

[0042] Based on the above scheme, the network device will also send the configuration information of the second type of RO to the terminal via system messages. The terminal can also receive the configuration information of the second type of RO via system message reception, so that it can use the second type of RO for random access in the future.

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

[0044] Based on the above solution, since the resource locations of the second type of RO and the first type of RO do not overlap, the conflict problem is naturally solved because the terminal uses the resource locations of the first type of RO and the second type of RO without overlapping.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the time slot where the second type of RO is located is different from the time slot where the first type of RO is located, or the subframe where the second type of RO is located is different from the subframe where the first type of RO is located, or the radio frame where the second type of RO is located is different from the radio frame where the first type of RO is located, or the time slot where the second type of RO is located is the same as the time slot where the first type of RO is located, and the start symbol of the second type of RO is different from the start symbol of the first type of RO.

[0046] Based on the above scheme, in this embodiment of the disclosure, the resource locations of the first type of RO and the second type of RO are staggered in the time domain, so that the resource locations of the first type of RO and the second type of RO do not overlap.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the resource locations of the second type of RO and the first type of RO overlap, and the random access response radio network temporary identifier (RA-RNTI) corresponding to the second type of RO is different from the random access response radio network temporary identifier (RA-RNTI) corresponding to the first type of RO.

[0048] Based on the above solution, the conflict between configuring the first type of RO and the second type of RO separately is resolved directly by distinguishing between RA-RNTI settings.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the frequency domain index of the first type of RO is different from that of the second type of RO.

[0050] Based on the above scheme, the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO can be distinguished by different frequency domain indexes, which has the advantage of being easy to implement.

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

[0052] Based on the above scheme, by connecting the frequency domain indices of the first type RO and the second type RO within the same time-frequency domain location range, the frequency domain indices of the first type RO and the second type RO will not overlap. Therefore, it can be ensured that the RA-RNTI corresponding to the first type RO and the RA-RNTI corresponding to the second type RO can be distinguished.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the system message includes: the number of first-type ROs in frequency division multiplexing.

[0054] Based on the above scheme, by carrying the number of first-type ROs in the frequency division multiplexing through system messages, the terminal can know the range of the frequency domain index of the first-type ROs, which has the characteristics of simple implementation.

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

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the RA-RNTI corresponding to the first type of RO is generated based on the offset, while the RA-RNTI corresponding to the second type of RO is not generated based on the offset.

[0057] In conjunction 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 and the offset corresponding to the second type of RO are different.

[0058] Based on the above scheme, by setting the offset, the RA-RNTI corresponding to the first type of RO and the second type of RO can also be different.

[0059] In conjunction 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, wherein the ROs configured by the first configuration information include a first type of RO and a second type of RO; the second type of RO is configured on an uplink time unit.

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

[0061] In some embodiments, the method further includes sending first information, which is used at least to determine a terminal capable of using a first type of RO.

[0062] Based on the above scheme, the network device sends first information to indicate to the terminal that it can use the first type of RO, thus realizing the indication of the terminal used by the first type of RO.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is used for terminals that are able to use the downlink time and / or flexible time of a first type of RO located in the SBFD time unit.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is also used to indicate a terminal that can use the RO located in the uplink time unit.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: sending second information, the second information instructing the RRC connected-state terminal to perform non-contention-based random access (CFRA).

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

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the second information indicates at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; the RO used to perform CFRA is located on the uplink time unit.

[0068] In a second aspect, embodiments of this disclosure provide an information processing method, which is executed by a terminal. The method includes: receiving configuration information, wherein the random access channel timing (RO) indicated by the configuration information includes a first type of RO on the SBFD time unit.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, the first type of RO is used for random access of connected terminals in Radio Resource Control (RRC) mode.

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

[0071] In conjunction with some embodiments of the second aspect, in some embodiments, receiving RO configuration information includes: receiving Radio Resource Control (RRC) dedicated signaling, the RRC dedicated signaling including configuration information of the first type of RO.

[0072] In conjunction 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 a second type of RO; the second type of RO is configured on an uplink time unit.

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

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the time slot where the second type of RO is located is different from the time slot where the first type of RO is located, or the subframe where the second type of RO is located is different from the subframe where the first type of RO is located, or the radio frame where the second type of RO is located is different from the radio frame where the first type of RO is located, or the time slot where the second type of RO is located is the same as the time slot where the first type of RO is located, and the start symbol of the second type of RO is different from the start symbol of the first type of RO.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the resource locations of the second type of RO overlap with those of the first type of RO, and the RA-RNTI corresponding to the second type of RO is different from the RA-RNTI corresponding to the first type of RO.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the frequency domain index of the first type of RO is different from that of the second type of RO.

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

[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the system message includes: the number of first-type ROs in frequency division multiplexing.

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

[0080] In conjunction with some embodiments of the second aspect, in some embodiments, the RA-RNTI corresponding to the first type of RO is generated based on the offset, while the RA-RNTI corresponding to the second type of RO is not generated based on the offset.

[0081] In conjunction 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 and the offset corresponding to the second type of RO are different.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, receiving configuration information includes: receiving a system message; the system message includes configuration information, wherein the RO configured by the configuration information includes a first type of RO and a second type of RO; the second type of 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 of RO.

[0083] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used for terminals that are able to use the downlink time and / or flexible time of a first type of RO located in the SBFD time unit.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is also used to indicate a terminal that can use the RO located in the uplink time unit.

[0085] In some embodiments, in conjunction with the second aspect, the method further includes: receiving second information, the second information instructing the RRC connected-state terminal to perform non-contention random access (CFRA).

[0086] In conjunction with some embodiments of the second aspect, in some embodiments, the second information indicates at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; the RO used to perform CFRA is located on the uplink time unit.

[0087] Thirdly, embodiments of this disclosure provide a network device, comprising: a processing module configured to configure a first type of RO on a subband full-duplex SBFD time unit.

[0088] Fourthly, embodiments of this disclosure provide a terminal, comprising: a receiving module configured to receive configuration information of an RO, wherein the RO includes: a first type of RO located on a sub-band full-duplex SBFD time unit.

[0089] Fifthly, embodiments of this disclosure provide a communication device, the communication device including: one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform the methods described in the optional implementations of the first and / or second aspects.

[0090] Sixthly, embodiments of this disclosure provide an information processing method, comprising:

[0091] The network device is configured with a first type of RO on the subband full-duplex SBFD time unit and a second type of RO on the uplink UL time unit, wherein the bandwidth occupied by the SBFD time unit is less than the bandwidth occupied by the UL time unit;

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

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

[0094] When the terminal is in RRC connected state and has a random access requirement within the downlink DL time unit and / or flexible time unit time range, it selects the first type of RO to initiate a random access procedure based on the configuration information of the first type of RO; when the terminal has a random access requirement within the UL time unit time range, it selects the first type of RO or the second type of RO with the smallest time domain distance from the current time to initiate a random access procedure based on the configuration information of the first type of RO and the configuration information of the second type of RO.

[0095] 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-RNTI is used to scramble the random access response in the random access process.

[0096] Based on the above scheme, the RO is no longer limited to the UL time unit. Thus, when the terminal has a random access requirement within the time range of the DL time unit and / or F time unit, it can use the first type of RO on the SBFD time unit to complete the random access in a timely manner.

[0097] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the optional implementations of the first and / or second and / or sixth aspects.

[0098] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the methods described in the optional implementations of the first and / or second and / or sixth aspects.

[0099] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in optional implementations of the first and / or second and / or sixth aspects.

[0100] It is understood that the aforementioned terminals, network devices, communication systems, program products, and computer programs are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0101] This disclosure provides an RO configuration method, a communication device, a communication system, and a storage medium. In some embodiments, the terms RO configuration method, communication method, and information processing method can be used interchangeably; the terms information indicating device, information processing device, information transmission device, network device, or terminal can be used interchangeably; and the terms communication system and information processing system can be used interchangeably.

[0102] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0103] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0104] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0105] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the aforementioned," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0106] In the embodiments disclosed herein, "multiple" refers to two or more.

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

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

[0109] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0110] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0111] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

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

[0113] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “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”.

[0114] 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”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0115] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0116] 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," and "bandwidth part (BWP)" can be used interchangeably.

[0117] 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 subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0118] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0119] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0120] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0122] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0123] Figure 1A This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0124] like Figure 1A As shown, the communication system 100 includes a terminal 101 and a network device 102. The network device 102 may include access network devices and core network devices.

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

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

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

[0128] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0129] In some embodiments, the core network equipment can be a single device, including a first network element, or it can be multiple devices or a group of devices, each including a first network element. Network elements can be virtual or physical. The core network includes, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0130] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0131] The following embodiments of this disclosure can be applied to Figure 1A The communication system 100 shown, or a part thereof, but not limited to it. Figure 1A The entities shown are illustrative; a communication system may include... Figure 1A All or part of the main body, or may include Figure 1A Other entities besides the main body, the number and form of each entity are arbitrary, the connection relationship between the entities is illustrative, the entities may not be connected or may be connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0132] The embodiments disclosed herein 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), Futuregeneration radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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, systems utilizing other RO configuration methods, and next-generation systems extended from them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0133] Dynamic configuration for TDD can achieve dynamic resource allocation, improve system performance and frequency utilization, but it may introduce crosslink interference (CLI).

[0134] To enhance UL coverage, reduce uplink latency, and improve system capacity and configuration flexibility, SBFD technology was introduced. SBFD technology allows network devices to transmit and receive simultaneously, with terminals transmitting or receiving at a single point in time. This introduces SBFD time units in the time domain during resource configuration. Multiple terminals perform uplink transmission and downlink reception separately on non-overlapping subbands of a single TDD carrier. Figure 1B The diagram shown illustrates one possible resource allocation. Figure 1B The display shows five time slots: DL, UL, and SBFD. DL time slots are denoted by "D," and UL time slots by "U." SBFD time slots reserve a portion of the DL frequency domain resources for uplink transmission. Figure 1B The second to fourth time slots are all SBFD time slots. It is worth noting that: Figure 1B This is one example of an SBFD time slot. Specifically, the SBFD time slot can also be set on the UL time unit. By setting the SBFD time slot, the terminal can simultaneously support uplink transmission and downlink reception in one time unit.

[0135] Based on the steps involved in random access, random access can include: four-step random access and two-step random access. Based on whether random access involves contention between terminals, random access can include: contention-based random access and contention-free random access.

[0136] Figure 1C The diagram shows a flowchart of a four-step random access process, which may include:

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

[0138] The terminal can determine the relationship between the Synchronization Signal / physical broadcast channel (PBCH) Block (SSB), Physical Random Access Channel (PRACH) resources, and random access preamble based on the higher-layer signaling configuration. It receives a set of SSBs and determines their Reference Signal Received Power (RSRP). Based on the RSRP and a threshold, it selects a suitable set of SSBs for determining the random access preamble. Based on the selected SSBs and the correspondence between SSBs and RACH resources, it determines the range of RACH resources and random access preambles. Here, RACH resources include RO. In some cases, RO can also be referred to as PRACH timing or PRACH resources. The terminal 101 selects a random access preamble group based on the expected message size (Message, Msg) 3, and then randomly selects the random access preamble to be used for this random access.

[0139] Terminal 101 sets the target received power of the random access preamble on the network side as: preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × powerRampingStep. preambleReceivedTargetPower is the target power for the network device to receive the random access preamble. powerRampingStep is the power ramp-up 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.

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

[0141] Determine the Random Access Response wireless network temporary identification (RA-RNTI) based on the resource index of the PRACH sent for Msg1; calculate the RA-RNTI.

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

[0143] `s_id` is the index of the first Orthogonal Frequency Division Multiplexing (OFDM) symbol of the RO. For example, 0 ≤ `s_id` < 14. `t_id` is the index of the first time slot within the system frame where the RO resides. For example, 0 ≤ `t_id` < 80. `t_id` can be determined based on the subcarrier spacing. `f_id` is the frequency domain index of the RO; for example, 0 ≤ `f_id` < 8. `ul_carrier_id` indicates the UL carrier for random access, which may include a regular UL or a supplementary UL (SUL) carrier. For example, `ul_carrier_id` equal to 0 indicates that a UL carrier was used for random access. `ul_carrier_id` equal to 1 indicates that an SUL carrier was used for random access.

[0144] The UE opens the RAR time window (ra-Response Window) at the first PDCCH timing after sending the random access preamble, and listens for the RA-RNTI scrambled PDCCH during the operation of the time window in order to receive the corresponding RA-RNTI RAR.

[0145] If no RAR is received within the RAR time window, or if no RAR corresponding to the random access preamble (RAPID) sent by the sender is received (i.e., no RAR corresponding to the random access preamble identifier (RAPID) sent by the sender), then a power ramp is performed, and msg1 is retransmitted based on the ramped power. In some embodiments, whether or not a random access uplink transmit power ramp is performed depends on whether a beam is switched. For example, an uplink transmit power ramp is performed without beam switching, but not when a beam switch occurs.

[0146] If a RAR is received within the RAR monitoring window, and if it is the first time a RAR has been received, the Media Access Control (MAC) Protocol Data Unit (PDU) is obtained from the multiplexing and assembly entity and stored in the Msg3 cache.

[0147] Step 3: Scheduled Transmission based on uplink scheduling.

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

[0149] Retrieve the MAC PDU from the Msg3 cache and transmit the MAC PDU based on the uplink grant (UL Grant) in the RAR.

[0150] After Msg3 is transmitted, a random access conflict resolution timer (ra-ContentionResolutionTimer) is started, and the UE listens for the PDCCH during the timer's execution. If Msg3 contains a C-RNTI MAC CE, the terminal listens for the PDCCH scrambled with that C-RNTI. If Msg3 does not contain a C-RNTI MAC CE, the UE listens for the PDCCH scrambled with the temporary cell radio network temporary identifier (TC-RNTI) to receive Msg4.

[0151] When Msg3 performs a Hybrid Automatic Repeat Request (HARQ) retransmission, the random access conflict resolution timer is restarted. The terminal will continue to listen to the PDCCH until the random access conflict resolution timer expires or stops. Msg3 HARQ retransmission is scrambling and scheduling based on TC-RNTI.

[0152] Step 4: Conflict Resolution.

[0153] If Msg3 contains a C-RNTI MAC CE, the terminal listens for the PDCCH scrambled with that C-RNTI. If the terminal detects Msg3, it considers the conflict resolution successful; otherwise, it considers the conflict resolution unsuccessful.

[0154] If Msg 3 does not contain a C-RNTI MAC CE, the terminal listens for a 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.

[0155] If conflict resolution fails, the terminal will increase power or switch beams and retransmit Msg1 to re-perform the four-step random access.

[0156] Figure 1D The diagram shows a flowchart of a two-step random access process. This two-step random access process may include:

[0157] Step 0: Perform Random Access (RA) preamble scheduling.

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

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

[0160] Step 2: The base station sends a Random Access Response (RAR).

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

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

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

[0164] The difference between the RA-RNTI for MsgB and the RA-RATI for Msg2 in the four-step random access lies in the introduction of the computational term 14×80×8×2.

[0165] Figure 2A This is an interactive schematic diagram illustrating an RO configuration method according to an embodiment of this disclosure. For example... Figure 2A As shown, this disclosure relates to an RO configuration method for a communication system 100, the method comprising:

[0166] S2101: Network devices are configured with RO on the SBFD time unit.

[0167] 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 be: set in the DL time unit, set in the Flexible (F) time unit, and / or set in the UL time unit. In some embodiments, the sub-band corresponding to the SBFD symbol is configured on the DL time slot. Downlink reception of the terminal can be supported in the frequency domain position of the DL time slot where the SBFD symbol is not configured, and uplink transmission of the terminal can be supported on the sub-band corresponding to the SBFD symbol, enabling the terminal to simultaneously transmit uplink and receive downlink in a TDD scenario. Alternatively, the SBFD symbol is configured on the UL time slot. Uplink transmission of the terminal can be supported in the frequency domain position of the UL time slot where the SBFD symbol is not configured, and downlink reception of the terminal can be supported on the sub-band corresponding to the SBFD symbol, similarly enabling the terminal to simultaneously transmit uplink and receive downlink in a TDD scenario.

[0168] like Figures 5A to 5C As shown, RO can be configured on the SBFD time unit.

[0169] By configuring ROs on the SBFD time unit, rather than limiting them to the UL time unit, the number of RO resources can be increased, thereby improving the system's random access capacity. On the other hand, by configuring ROs in the DL time unit and / or F time unit, the random access needs of terminals in the DL time unit and / or F time unit can be met in a timely manner, thereby at least reducing the random access latency of these terminals and improving random access efficiency.

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

[0171] In some embodiments, the first type of RO is not used for RRC idle state and / or RRC inactive state terminals. In some embodiments, the first type of RO can be used by RRC connected state terminals that support SBFD technology. For example, RRC connected state terminals need to use RO for random access when beam failure, invalid link failure, or cell handover occurs.

[0172] S2102: Network devices send RRC dedicated signaling.

[0173] In some embodiments, the RRC-specific signaling includes at least configuration information for a first type of RO. In some embodiments, an RRC-connected terminal receives the RRC-specific signaling. In some embodiments, an RRC-connected terminal supporting SBFD technology receives the RRC-specific signaling.

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

[0175] In some embodiments, the configuration information for the first type of RO can also be referred to as PRACH configuration information, which may include a PRACH configuration index, the number of ROs in frequency division multiplexing (e.g., msg1-FDM), frequency division multiplexing format information, and the frequency domain start position (msg1-FrequencyStart). The number of ROs in frequency division multiplexing differs 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 simultaneously configures four ROs using frequency division multiplexing on one symbol, then the configuration information configures a total of eight first-type ROs, but the number of ROs in frequency division multiplexing is equal to four.

[0176] Figure 5D This is a schematic diagram of a PRACH configuration. (Example) Figure 5D As shown, the sequence corresponding to the random access preamble (also called the random access sequence) can 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. The specific sequence selected from format 0 to format 3 can be determined based on the subcarrier spacing of the RO. For example, if the subcarrier spacing of the RO is 1.25 kHz, any one of format 0 to format 2 can be selected. If the subcarrier spacing of the RO is 5 kHz, format 3 can be selected. Figure 5D The configuration of the PRACH resource shown can include two parameters: msg1-FDM and msg1-FrequencyStart. msg1-FDM can be the number of frequency division multiplexers for the RO. msg1-FrequencyStart is the frequency domain start position of the RO.

[0177] S2103: Network device sends system message.

[0178] This system message may include one or more System Information Blocks (SIBs).

[0179] This system message may include configuration information for the second type of RO. The content of the configuration information for the second type of RO can be referenced from the content of the configuration information for the first type of RO, and will not be repeated here.

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

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

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

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

[0184] In some embodiments, the candidate resource locations for the first type of RO may be resource locations that can be configured with the first type of RO.

[0185] In some embodiments, the candidate resource location for the second type of RO may be a resource location that can be configured with the second type of RO.

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

[0187] like Figure 5C As shown, the frequency domain positions of the first type of RO and the second type of RO are different, thus realizing that the resource positions of the first type of RO and the second type of RO are different.

[0188] For example, the subband where the second type of RO is located is different from the subband occupied by the SBFD time unit.

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

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

[0191] Since the resource locations of Type I and Type II ROs do not overlap, the resource locations of the ROs used when sending selection message 1 or message A during random access will naturally be different. Therefore, the RA-RNTI calculated by the terminal and network device based on the resource index corresponding to the time resource location of the RO will naturally be different. Thus, the RA-RNTI of terminals using Type I and Type II ROs for random access will be naturally distinguishable, allowing for differentiation of random access responses from different terminals when sending Msg2 and MsgB. This resource index may include: the frequency domain index of the RO and / or the time domain index of the RO.

[0192] It is worth noting that the formula for calculating RA-RNTI at this time can be found in the calculation of RA-RANT for the four-step random access or two-step random access mentioned above.

[0193] In scenarios 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 can be different. For example, the first type RO and the second type RO use frequency division multiplexing and can be configured on different carriers, subcarriers or subbands.

[0194] In other embodiments, the difference in resource location between the first type of RO and the second type of RO may be mainly due to the difference in time domain location.

[0195] For example, the time slot where the second type of RO is located is different from the time slot where the first type of RO is located, or the subframe where the second type of RO is located is different from the subframe where the first type of RO is located, or the radio frame where the second type of RO is located is different from the radio frame where the first type of RO is located, or the time slot where the second type of RO is located is the same as the time slot where the first type of RO is located, and the start symbol of the second type of RO is different from the start symbol of the first type of RO.

[0196] In some embodiments, the resource locations of the first type of RO and the second type of RO may overlap. For example, overlapping resource locations can be understood as the resource locations being the same.

[0197] In some embodiments, the resource locations of the first type of RO and the second type of RO can be understood as follows: the candidate resource locations of the first type of RO and the candidate resource locations of the second type of RO may overlap. For example, overlapping candidate resource locations can be understood as the same candidate resource location. In some embodiments, the candidate resource location of the first type of RO may be a resource location that can be configured for the first type of RO. In some embodiments, the candidate resource location of the second type of RO may be a resource location that can be configured for the second type of RO.

[0198] The resource locations of the first type of RO and the second type of RO can overlap, and may include:

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

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

[0201] For example, the candidate resource locations of the first type of RO and the second type of RO can be the same, then the RA-RNTI corresponding to the second type of RO is different from the RA-RNTI corresponding to the first type of RO. The difference between the RA-RNTI corresponding to the first type of RO and the second type of RO can be distinguished by at least one of the following methods.

[0202] For example, RA-RATI can be calculated based on the frequency domain index of RO. In this case, by making the frequency domain indices of the first type of RO different from those of the second type of RO, the RA-RNTI corresponding to the first type of RO is different from the RA-RNTI corresponding to the second type of RO. That is, the frequency domain index of the RO is used to distinguish the type of RO. As 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. That is, the offset is used to distinguish the type of RO. For example, the frequency domain index of the second type of RO is obtained by continuing to number the frequency domain index of the first type of RO, or the frequency domain index of the first type of RO is obtained by continuing to number the frequency domain index of the second type of RO. In this implementation, it is equivalent to connecting the frequency domain indices of the first type of RO and the second type of RO.

[0203] For example, if there are M ROs of type I in the frequency domain, then starting from 0 or 1, the M ROs are numbered according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type I ROs. Further, after the type I ROs are numbered, the type II ROs are numbered starting from M or M+1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type II ROs. Using this method, even if the type I ROs and type II ROs are located within the same frequency domain, their frequency domain indices will obviously be different. Here, M represents the number of type I ROs in the frequency domain that are frequency-division multiplexed. As another example, if there are S ROs of type II in the frequency domain, then starting from 0 or 1, the S ROs are numbered according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type II ROs. Further, after the type II ROs are numbered, the type I ROs are numbered starting from S or S+1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type II ROs. Using this method, even if the first type of RO and the second type of RO are located within the same frequency domain, their frequency domain indices will obviously be different. Here, S represents the number of second-type ROs in the frequency division multiplexing domain. In both embodiments, the frequency domain indices of the first type of RO and the second type of RO are numbered consecutively.

[0204] In this embodiment, since the configuration information of the second type of RO is sent by system messages and the configuration information of the first type of RO is sent by RRC dedicated signaling, the system messages carry the number M of RO frequency division multiplexing for the first type of RO, or the RRC dedicated signaling carries the number S of RO frequency division multiplexing for the second type of RO. Figure 5A and Figure 5B The first type of RO shown has a frequency division multiplexing (FDM) number M equal to 2. The second type of RO has a FDM number equal to 4. Figure 5A and Figure 5B The number of frequency division multiplexers (RFDs) in the middle array is always represented by the parameter msg1-FDM. In practice, this parameter can also be MsgA-FDM. Furthermore, the starting index of the frequency domain index for the first type of RFD is different from that for the second type of RFD.

[0205] In some embodiments, the starting index of the first type of RO starts from 0, while the starting index of the second type of RO starts from a specified location on the network device or a location agreed upon by the protocol. Furthermore, the starting index of the second type of RO avoids the range of the frequency domain index of the first type of RO. Optionally, in this case, the system message may carry the starting index of the frequency domain index of the second type of RO.

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

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

[0208] Similarly, when the frequency domain index of the first type of RO is different from that of the second type of RO, the formula for calculating RA-RNTI can be found in the aforementioned calculation of RA-RANT for four-step random access or two-step random access.

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

[0210] Example 1: An offset (which can be called the first offset) is introduced into the RA-RNTI calculation formula for the first type of RO. The size of this 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 where the configuration information of the first type of RO is located.

[0211] Example 2: An offset (which can be called the second offset) is introduced into the RA-RNTI calculation formula for the second type of RO. The size of this 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.

[0212] Example 3: Different offsets can be introduced into the calculation formulas for Type I RO and Type II RO, thus achieving the same distinction between RA-RNTI for Type I RO and Type II RO. The magnitudes 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.

[0213] When using Example 1 or Example 2, only an offset needs to be introduced into the calculation of RA-RNTI for the first type of RO or the second type of RO. When using Example 3, offsets for calculating RA-RNTI are introduced for both the first type of RO and the second type of RO.

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

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

[0216] MSGB-RNTI can be RA-RNTI for two-step random access, MSG1-RA-RNTI can be RA-RANTI for four-step random access, and offset can be the offset introduced above.

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

[0218] S2104: The network device sends the second message.

[0219] In some embodiments, the network device sends RRC-specific signaling containing second information.

[0220] In some embodiments, the network device sends PDCCH signaling containing second information. This PDCCH signaling may include, but is not limited to, DCI.

[0221] In some embodiments, the second information may indicate non-contention-based random access.

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

[0223] In some embodiments, the second information may be carried in RRC-specific signaling that is different from the configuration information sent to the RO.

[0224] For example, during cell handover for an RRC connected terminal, the cell handover command can carry the second information. That is, while instructing the RRC connected terminal to perform cell handover through the cell handover command, the second information carried in the cell handover command also indicates that the RRC connected terminal uses non-contention-based random access during the random access process to the target cell.

[0225] In some embodiments, when a terminal uses beam communication, the second information is carried in the network signaling where the terminal's beam configuration or beam failure configuration is located. Thus, when an RRC-connected terminal performs beam recovery, it naturally uses non-contention-based random access for random access.

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

[0227] For example, the parameter includes, but is not limited to, at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; the RO used to perform CFRA is located on the uplink time unit.

[0228] For example, the second information indicates the range of random access preambles for CFRA, and the terminal can randomly select one within the range indicated by the second information for non-contention random access when performing CFRA.

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

[0230] The type of RO used to perform CFRA here may include, but is not limited to, the aforementioned Type I RO and / or Type II RO.

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

[0232] In some real-time examples, the RO for contention-based random access can also be a Type I RO and / or a Type II RO.

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

[0234] In some embodiments, the second information directly includes the configuration information of CFRA using RO, in which case the second information does not need to be associated with the configured RO.

[0235] In some embodiments, the second information indicates whether CFRA can use a Type 1 RO. If the second information indicates that non-contentionable random access does not use a Type 1 RO, then by default at least a Type 2 RO can be used.

[0236] In some embodiments, when the second information indicates that the CFRA uses the first type of RO, it can be considered that non-contention-based random access can use both the first type of RO and the second type of RO simultaneously.

[0237] In some embodiments, the RO used for non-contention-based random access is the RO indicated by the second information. For example, if the second information indicates that the CFRA uses a first-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses a second-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses both a first-type RO and a second-type RO, then the corresponding terminal uses both types of ROs when performing random access.

[0238] The second information indicates that the RO used by the CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type I RO. The second information indicates that the RO used by the CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type II RO.

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

[0240] S2105: Initiate random access.

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

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

[0243] In some embodiments, the RRC connected terminal selects the RO closest to the current time from the first type of RO and the second type of RO for random access.

[0244] In some embodiments, if an RRC connected terminal has a random access requirement during the time corresponding to the DL time unit and / or F time unit, it initiates random access on the first type of RO.

[0245] In some embodiments, if an RRC connected terminal supporting SBFD technology has a random access requirement during the time corresponding to the DL time unit and / or F time unit, it initiates random access on the first type of RO.

[0246] In some embodiments, if an RRC connected terminal has a random access requirement within the time period corresponding to the UL time unit, it will initiate random access on the first type RO or the second type RO.

[0247] In some embodiments, RRC connected state terminals have a need for random access during cell handover.

[0248] In some embodiments, RRC connected terminals have random access requirements when performing Beam Failure Recovery (BFR).

[0249] In some embodiments, terminals in the RRC idle state and / or RRC inactive state select the RO closest to the current time from the first type of RO and the second type of RO for random access.

[0250] In some embodiments, terminals in the RRC idle state and / or RRC inactive state select an RO from the second type of RO for random access.

[0251] In TDD scenarios, configuring the RO (Redirect Access) on the SBFD (Site-Based Functional Time Unit) instead of limiting it to the UL (Ultimate Time Unit) increases the random access capacity of the cell. Simultaneously, it reduces random access latency for terminals with random access needs near the DL (Deep Path) and / or SBFD time units, thus improving random access efficiency. For RRC (Redirect-Controlled Functional) connected-state terminals with random access needs arising from BFR (Browser-Based Function) or cell handover, it accelerates the BFR and / or cell handover rate.

[0252] Figure 2B This is an interactive schematic diagram illustrating an RO configuration method according to an embodiment of this disclosure. For example... Figure 2B As shown, this disclosure relates to an RO configuration method for a communication system 100, the method comprising:

[0253] S2201: Network devices are configured with RO on the SBFD time unit.

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

[0255] In some embodiments, the network device configures RO on the SBFD time slot.

[0256] In some embodiments, the network device is configured with RO on the SBFD symbol.

[0257] The SBFD symbol here may include: a time unit set for a sub-band in DL time, a time unit set for a sub-band in Flexible (F) time, and / or a time unit set for a sub-band in UL time.

[0258] By configuring ROs on the SBFD time unit, rather than limiting them to the UL time unit, the number of RO resources can be increased, thereby improving the system's random access capacity. On the other hand, by configuring ROs in the DL time unit and / or F time unit, the random access needs of terminals in the DL time unit and / or F time unit can be met in a timely manner, thereby at least reducing the random access latency of these terminals and improving random access efficiency.

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

[0260] In some embodiments, considering that RRC-connected terminals need to restore their RRC connection with network devices as soon as possible through random access to ensure transmission continuity and terminal reachability, the first type of RO can be used by RRC-connected terminals.

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

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

[0263] S2202: Network device sends system message.

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

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

[0266] This system message may include one or more System Information Blocks (SIBs).

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

[0268] In some embodiments, the network device may also transmit a configuration of time units, such as a configuration related to the ratio of TDD radio frames. Thus, the terminal can determine the distribution of SBFD, UL, and / or DL ​​time units in the time domain based on this configuration.

[0269] In some embodiments, Figure 5C The diagram shows the configuration of the RO.

[0270] S2203: The network device sends the first message.

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

[0272] In some embodiments, the first information may indicate terminal information that can use the first type of RO.

[0273] In some embodiments, the first information is used for terminals that are capable of using a first type of RO located in the downlink time and / or flexible time of the SBFD time unit.

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

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

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

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

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

[0279] Thus, the terminal will determine whether it can use the first type of RO based on the first information.

[0280] In some embodiments, the first information may also indicate the conditions for using a first type of RO. Thus, a terminal that meets 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 then use the first type of RO when the conditions are met.

[0281] The conditions for using a Class I RO may include, but are not limited to:

[0282] The RRC state using the first type of RO may include RRC connected state, RRC idle state and / or RRC inactive state. For example, this condition may allow terminals in the RRC connected state to use the first type of RO, while prohibiting terminals in the RRC idle state and / or RRC inactive state from using the first type of RO.

[0283] Triggering events for random access using Type I RO may include, but are not limited to: cell handover, beam failure recovery, Radio Link Failure (RLF) event for RRC connected-state terminal, and cell reselection; for example, Type I RO may be allowed for cell handover and / or beam failure recovery.

[0284] Use the time and / or spatial range of the first type of RO, etc.

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

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

[0287] For example, terminals in RRC idle state and / or RRC inactive state automatically do not use RO on SBFD time unit. However, terminals in RRC connected state will assume that they can use RO on SBFD time unit.

[0288] For example, a terminal that does not support SBFD technology will automatically not use the RO on the SBFD time unit. However, a terminal that supports SBFD technology will assume that it can use the RO on the SBFD time unit.

[0289] In some 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 the protocol, and the network device side will not send the first information.

[0290] S2204: The network device sends a second message.

[0291] In some embodiments, the network device sends RRC-specific signaling containing second information.

[0292] In some embodiments, the network device sends PDCCH signaling containing second information. This PDCCH signaling may include, but is not limited to, DCI.

[0293] In some embodiments, the second information may indicate non-contention-based random access.

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

[0295] In some embodiments, the second information may be carried in RRC-specific signaling that is different from the configuration information sent to the RO.

[0296] For example, during cell handover for an RRC connected terminal, the cell handover command can carry the second information. That is, while instructing the RRC connected terminal to perform cell handover through the cell handover command, the second information carried in the cell handover command also indicates that the RRC connected terminal uses non-contention-based random access during the random access process to the target cell.

[0297] In some embodiments, when a terminal uses beam communication, the second information is carried in the network signaling where the terminal's beam configuration or beam failure configuration is located. Thus, when an RRC-connected terminal performs beam recovery, it naturally uses non-contention-based random access for random access.

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

[0299] For example, the parameter includes, but is not limited to, at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; the RO used to perform CFRA is located on the uplink time unit.

[0300] For example, the second information indicates the range of random access preambles for CFRA, and the terminal can randomly select one within the range indicated by the second information for non-contention random access when performing CFRA.

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

[0302] The type of RO used to perform CFRA here may include, but is not limited to, the aforementioned Type I RO and / or Type II RO.

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

[0304] In some real-time examples, the RO for contention-based random access can also be a Type I RO and / or a Type II RO.

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

[0306] In some embodiments, the second information directly includes the configuration information of the CFRA using the RO, so there is no need to associate it with the configured RO.

[0307] In some embodiments, the second information indicates whether CFRA can use a Type 1 RO. If the second information indicates that non-contentionable random access does not use a Type 1 RO, then by default at least a Type 2 RO can be used.

[0308] In some embodiments, when the second information indicates that the CFRA uses the first type of RO, it can be considered that non-contention-based random access can use both the first type of RO and the second type of RO simultaneously.

[0309] In some embodiments, the RO used for non-contention-based random access is the RO indicated by the second information. For example, if the second information indicates that the CFRA uses a first-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses a second-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses both a first-type RO and a second-type RO, then the corresponding terminal uses both types of ROs when performing random access.

[0310] The second information indicates that the RO used by the CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type I RO. The second information indicates that the RO used by the CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type II RO.

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

[0312] S2205: Initiate random access.

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

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

[0315] In some embodiments, the RRC connected terminal selects the RO closest to the current time from the first type of RO and the second type of RO for random access.

[0316] In some embodiments, if an RRC connected terminal has a random access requirement during the time corresponding to the DL time unit and / or F time unit, it initiates random access on the first type of RO.

[0317] In some embodiments, if an RRC connected terminal supporting SBFD technology has a random access requirement during the time corresponding to the DL time unit and / or F time unit, it initiates random access on the first type of RO.

[0318] In some embodiments, if an RRC connected terminal has a random access requirement within the time period corresponding to the UL time unit, it will initiate random access on the first type RO or the second type RO.

[0319] In some embodiments, RRC connected state terminals have a need for random access during cell handover.

[0320] In some embodiments, RRC connected terminals have random access requirements when performing Beam Failure Recovery (BFR).

[0321] In some embodiments, terminals in the RRC idle state and / or RRC inactive state select the RO closest to the current time from the first type of RO and the second type of RO for random access.

[0322] In some embodiments, terminals in the RRC idle state and / or RRC inactive state select an RO from the second type of RO for random access.

[0323] In TDD scenarios, configuring the RO (Redirect Access) on the SBFD (Site-Based Functional Time Unit) instead of limiting it to the UL (Ultimate Time Unit) increases the random access capacity of the cell. Simultaneously, it reduces random access latency for terminals with random access needs near the DL (Deep Path) and / or SBFD time units, thus improving random access efficiency. For RRC (Redirect-Controlled Functional) connected-state terminals with random access needs arising from BFR (Browser-Based Function) or cell handover, it accelerates the BFR and / or cell handover rate.

[0324] like Figure 3A As shown in the embodiments of this disclosure, a method for configuring random access channel (RO) timing is provided and executed by a network device. The method may include:

[0325] S3101: Network devices are configured with RO on the SBFD time unit.

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

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

[0328] In some embodiments, alternative embodiments of S3101 may be found in [reference needed]. Figure 2A The relevant description of S2101 in the corresponding embodiment.

[0329] S3102: Send RRC dedicated signaling.

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

[0331] In some embodiments, alternative implementations of S3102 may refer to Figure 2A The relevant description of S2102 in the corresponding embodiment.

[0332] S3103: Send system message.

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

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

[0335] In some embodiments, alternative implementations of S3103 may refer to Figure 2A S2103 of the corresponding embodiment.

[0336] It is worth noting that, in addition to being configured on different time units, Type I and Type II RO also have the following characteristics: Figure 2A The differences described in the corresponding embodiments.

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

[0338] In other embodiments, the first type of RO and the second type of RO have the same time-frequency domain position, but the corresponding RA-RNTI are different.

[0339] There are several different methods for RA-RNTI; please refer to [link / reference needed]. Figure 2A The relevant parts of the corresponding embodiments will not be repeated here.

[0340] Since the locations of the first type of RO and the second type of RO do not overlap, the time-frequency domain locations of the ROs used when sending selection message 1 or message A during random access will naturally be different. Consequently, the RA-RNTI calculated by the terminal and the network device based on the time-frequency domain locations of the ROs will also be different. Thus, the RA-RNTI of terminals using the first type of RO and the second type of RO for random access will obviously be distinguishable. Therefore, when sending Msg2 and MsgB for random access, the random access responses of different terminals can be distinguished.

[0341] It is worth noting that the formula for calculating RA-RNTI at this time can be found in the calculation of RA-RANT for the four-step random access or two-step random access mentioned above.

[0342] In scenarios 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 can be different. For example, the first type RO and the second type RO use frequency division multiplexing and can be configured on different carriers, subcarriers or subbands.

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

[0344] For example, the time slot where the second type of RO is located is different from the time slot where the first type of RO is located, or the subframe where the second type of RO is located is different from the subframe where the first type of RO is located, or the radio frame where the second type of RO is located is different from the radio frame where the first type of RO is located, or the time slot where the second type of RO is located is the same as the time slot where the first type of RO is located, and the start symbol of the second type of RO is different from the start symbol of the first type of RO.

[0345] In some embodiments, the resource locations of the first type of Remote Access Response (RO) and the second type of RO may overlap. For example, the candidate resource locations of the first type of RO and the second type of RO may be the same, in which case the Random Access Response Radio Network Temporary Identifier (RA-RNTI) of the second type of RO and the Random Access Response Radio Network Temporary Identifier (RA-RNTI) of the first type of RO will be different. The difference in the RA-RNTIs corresponding to the first type of RO and the second type of RO can be distinguished by at least one of the following methods.

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

[0347] For example, when RA-RNTI is calculated based on the index corresponding to the time-frequency domain position of RO, the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO can be made different by introducing one or more offsets.

[0348] For example, the frequency domain index of the second type of RO is obtained by continuing to number the frequency domain index of the first type of RO, or the frequency domain index of the first type of RO is obtained by continuing to number the frequency domain index of the second type of RO. In this implementation, it is equivalent to connecting the frequency domain indices of the first type of RO and the second type of RO.

[0349] For example, if there are M ROs of type I in the frequency domain, they are numbered starting from 0 or 1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type I ROs. Further, after the type I ROs are numbered, the type II ROs are numbered starting from M or M+1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type II ROs. Using this method, even if the type I ROs and type II ROs are located within the same frequency domain, their frequency domain indices will obviously be different. Here, M represents the number of type I ROs in the frequency division multiplexing domain.

[0350] For example, if there are S type ROs of the second category in the frequency domain, then the S ROs are numbered starting from 0 or 1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the second category ROs. Further, after the second category ROs are numbered, the first category ROs are numbered starting from S or S+1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the second category ROs. Using this method, even if the first and second category ROs are located within the same frequency domain, their frequency domain indices will obviously be different. Here, S represents the number of second category ROs in the frequency domain that are frequency-division multiplexed.

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

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

[0353] For example, the starting index of the frequency domain index of the first type of RO is different from that of the frequency domain index of the second type of RO.

[0354] In some embodiments, the starting index of the first type of RO starts from 0, while the starting index of the second type of RO starts from a specified location on the network device or a location agreed upon by the protocol. Furthermore, the starting index of the second type of RO avoids the range of the frequency domain index of the first type of RO. Optionally, in this case, the system message may carry the starting index of the frequency domain index of the second type of RO.

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

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

[0357] Similarly, when the frequency domain index of the first type of RO is different from that of the second type of RO, the formula for calculating RA-RNTI can be found in the aforementioned calculation of RA-RANT for four-step random access or two-step random access.

[0358] In other embodiments, the resource locations of the first type of RO and the second type of RO may be the same, and the frequency domain indexes of the first type of RO and the second type of RO may also start from the same position. For example, the frequency domain indexes of the first type of RO and the second type of RO may both start from 0 or 1. In this case, in order to distinguish the RA-RNTI corresponding to the first type of RO and the second type of RO, one or more parameters for calculating the RA-RNTI can be introduced.

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

[0360] Example 1: An offset (which can be called the first offset) is introduced into the RA-RNTI calculation formula for the first type of RO. The size of this 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 where the configuration information of the first type of RO is located.

[0361] Example 2: An offset (which can be called the second offset) is introduced into the RA-RNTI calculation formula for the second type of RO. The size of this 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.

[0362] Example 3: Different offsets can be introduced into the calculation formulas for Type I RO and Type II RO, thus achieving the same distinction between RA-RNTI for Type I RO and Type II RO. The magnitudes 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.

[0363] When using Example 1 or Example 2, only an offset needs to be introduced into the calculation of RA-RNTI for the first type of RO or the second type of RO. When using Example 3, offsets for calculating RA-RNTI are introduced for both the first type of RO and the second type of RO.

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

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

[0366] MSGB-RNTI can be RA-RNTI for two-step random access, MSG1-RA-RNTI can be RA-RANTI for four-step random access, and offset can be the offset introduced above.

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

[0368] S3104: The network device sends a second message.

[0369] In some embodiments, the network device sends RRC-specific signaling containing second information.

[0370] In some embodiments, the network device sends PDCCH signaling containing second information. This PDCCH signaling may include, but is not limited to, DCI.

[0371] In some embodiments, the second information may indicate non-contention-based random access.

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

[0373] In some embodiments, the second information may be carried in RRC-specific signaling that is different from the configuration information sent to the RO.

[0374] For example, during cell handover for an RRC connected terminal, the cell handover command can carry the second information. That is, while instructing the RRC connected terminal to perform cell handover through the cell handover command, the second information carried in the cell handover command also indicates that the RRC connected terminal uses non-contention-based random access during the random access process to the target cell.

[0375] In some embodiments, when a terminal uses beam communication, the second information is carried in the network signaling where the terminal's beam configuration or beam failure configuration is located. Thus, when an RRC-connected terminal performs beam recovery, it naturally uses non-contention-based random access for random access.

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

[0377] For example, the parameter includes, but is not limited to, at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; the RO used to perform CFRA is located on the uplink time unit.

[0378] For example, the second information indicates the range of random access preambles for CFRA, and the terminal can randomly select one within the range indicated by the second information for non-contention random access when performing CFRA.

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

[0380] The type of RO used to perform CFRA here may include, but is not limited to, the aforementioned Type I RO and / or Type II RO.

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

[0382] In some real-time examples, the RO for contention-based random access can also be a Type I RO and / or a Type II RO.

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

[0384] In some embodiments, the second information directly includes the configuration information of the CFRA using the RO, so there is no need to associate it with the configured RO.

[0385] In some embodiments, the second information indicates whether CFRA can use a Type 1 RO. If the second information indicates that non-contentionable random access does not use a Type 1 RO, then by default at least a Type 2 RO can be used.

[0386] In some embodiments, when the second information indicates that the CFRA uses the first type of RO, it can be considered that non-contention-based random access can use both the first type of RO and the second type of RO simultaneously.

[0387] In some embodiments, the RO used for non-contention-based random access is the RO indicated by the second information. For example, if the second information indicates that the CFRA uses a first-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses a second-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses both a first-type RO and a second-type RO, then the corresponding terminal uses both types of ROs when performing random access.

[0388] The second information indicates that the RO used by the CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type I RO. The second information indicates that the RO used by the CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type II RO.

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

[0390] It is worth noting that:

[0391] Some embodiments may include steps S3101 to S3103, i.e., S3104 is an optional step. In this case, the terminal capable of using the first type of RO and the second type of RO may be determined by a protocol, or indicated by configuration information carrying the first type of RO or by a system message carrying the second type of RO.

[0392] Some embodiments may include steps S3101 to S3102, i.e., steps S3103-S3104 are optional. In this case, the network device adds a RO configuration on the SBFD time unit, and may or may not configure a RO on the UL time unit. If no RO is configured on the UL time unit, steps S3103 to S3104 are obviously unnecessary. If a RO is configured on the UL time unit, both types of ROs can be directly sent to the terminal via RRC dedicated signaling, in which case subsequent steps S3103 to S3104 can also be omitted.

[0393] like Figure 3B As shown in the embodiments of this disclosure, a method for configuring random access channel (RO) timing is provided and executed by a network device. The method may include:

[0394] S3201: Network devices are configured with RO on the SBFD time unit.

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

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

[0397] In some embodiments, alternative implementations of S3201 may refer to Figure 2B The relevant description of S2201 in the corresponding embodiment.

[0398] S3202: Send system message.

[0399] In some embodiments, the system message includes first configuration information. This first configuration information is used to indicate the RO (Redirect Resource).

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

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

[0402] This system message may include one or more System Information Blocks (SIBs).

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

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

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

[0406] S3203: The network device sends the first message.

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

[0408] In some embodiments, the first information may indicate terminal information that can use the first type of RO.

[0409] In some embodiments, the first information is used for terminals that are capable of using a first type of RO located in the downlink time and / or flexible time of the SBFD time unit.

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

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

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

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

[0414] Thus, the terminal will determine whether it can use the first type of RO based on the first information.

[0415] In some embodiments, the first information may also indicate the conditions for using a first type of RO. Thus, a terminal that meets 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 then use the first type of RO when the conditions are met.

[0416] The conditions for using a Class I RO may include, but are not limited to:

[0417] The RRC state using the first type of RO may include RRC connected state, RRC idle state and / or RRC inactive state. For example, this condition may allow terminals in the RRC connected state to use the first type of RO, while prohibiting terminals in the RRC idle state and / or RRC inactive state from using the first type of RO.

[0418] Triggering events for random access using Type I RO may include, but are not limited to: cell handover, beam failure recovery, connection recovery, and cell reselection; for example, Type I RO may be permitted for cell handover, beam failure recovery, and / or connection recovery.

[0419] Use the time and / or spatial range of the first type of RO, etc.

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

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

[0422] For example, terminals in RRC idle state and / or RRC inactive state automatically do not use RO on SBFD time unit. However, terminals in RRC connected state will assume that they can use RO on SBFD time unit.

[0423] For example, a terminal that does not support SBFD technology will automatically not use the RO on the SBFD time unit. However, a terminal that supports SBFD technology will assume that it can use the RO on the SBFD time unit.

[0424] In some 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 the protocol, and the network device side will not send the first information.

[0425] S3204: The network device sends the second message.

[0426] In some embodiments, the network device sends RRC-specific signaling containing second information.

[0427] In some embodiments, the network device sends PDCCH signaling containing second information. This PDCCH signaling may include, but is not limited to, DCI.

[0428] In some embodiments, the second information may indicate non-contention-based random access.

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

[0430] In some embodiments, the second information may be carried in RRC-specific signaling that is different from the configuration information sent to the RO.

[0431] For example, during cell handover for an RRC connected terminal, the cell handover command can carry the second information. That is, while instructing the RRC connected terminal to perform cell handover through the cell handover command, the second information carried in the cell handover command also indicates that the RRC connected terminal uses non-contention-based random access during the random access process to the target cell.

[0432] In some embodiments, when a terminal uses beam communication, the second information is carried in the network signaling where the terminal's beam configuration or beam failure configuration is located. Thus, when an RRC-connected terminal performs beam recovery, it naturally uses non-contention-based random access for random access.

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

[0434] For example, the parameter includes, but is not limited to, at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; the RO used to perform CFRA is located on the uplink time unit.

[0435] For example, the second information indicates the range of random access preambles for CFRA, and the terminal can randomly select one within the range indicated by the second information for non-contention random access when performing CFRA.

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

[0437] The type of RO used to perform CFRA here may include, but is not limited to, the aforementioned Type I RO and / or Type II RO.

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

[0439] In some real-time examples, the RO for contention-based random access can also be a Type I RO and / or a Type II RO.

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

[0441] In some embodiments, the second information directly includes the configuration information of the CFRA using the RO, so there is no need to associate it with the configured RO.

[0442] In some embodiments, the second information indicates whether CFRA can use a Type 1 RO. If the second information indicates that non-contentionable random access does not use a Type 1 RO, then by default at least a Type 2 RO can be used.

[0443] In some embodiments, when the second information indicates that the CFRA uses the first type of RO, it can be considered that non-contention-based random access can use both the first type of RO and the second type of RO simultaneously.

[0444] In some embodiments, the RO used for non-contention-based random access is the RO indicated by the second information. For example, if the second information indicates that the CFRA uses a first-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses a second-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses both a first-type RO and a second-type RO, then the corresponding terminal uses both types of ROs when performing random access.

[0445] The second information indicates that the RO used by the CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type I RO. The second information indicates that the RO used by the CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type II RO.

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

[0447] It is worth noting that:

[0448] Some embodiments may include steps S3101 to S3102, i.e., S3104 is an optional step. In this case, the terminal capable of using the first type of RO and the second type of RO may be determined by a protocol, or indicated by configuration information carrying the first type of RO or by system messages carrying the second type of RO.

[0449] Some embodiments may include steps S3101 to S3102, i.e., steps S3103-S3104 are optional. In this case, the network device adds a RO configuration on the SBFD time unit, and may or may not configure a RO on the UL time unit. If no RO is configured on the UL time unit, steps S3103 to S3104 are obviously unnecessary. If a RO is configured on the UL time unit, both types of ROs can be directly sent to the terminal via RRC dedicated signaling, in which case subsequent steps S3103 to S3104 can also be omitted.

[0450] like Figure 4A As shown in the embodiments of this disclosure, an information processing method is provided, which may include:

[0451] S4101: The terminal receives the configuration information from the RO.

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

[0453] In some embodiments, the first type of RO is used for random access of connected terminals in Radio Resource Control (RRC) mode.

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

[0455] In some embodiments, the configuration information received by the terminal from the RO may include:

[0456] The terminal receives RRC dedicated signaling, which includes configuration information for the first type of RO, and / or...

[0457] The terminal receives system messages; the system messages include configuration information for the second type of RO.

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

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

[0460] In some embodiments, the second type of RO can also be referred to as the public RO.

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

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

[0463] Since the locations of the first type of RO and the second type of RO do not overlap, the time-frequency domain locations of the ROs used when sending selection message 1 or message A during random access will naturally be different. Consequently, the RA-RNTI calculated by the terminal and the network device based on the time-frequency domain locations of the ROs will also be different. Thus, the RA-RNTI of terminals using the first type of RO and the second type of RO for random access will obviously be distinguishable. Therefore, when sending Msg2 and MsgB for random access, the random access responses of different terminals can be distinguished.

[0464] It is worth noting that the formula for calculating RA-RNTI at this time can be found in the calculation of RA-RANT for the four-step random access or two-step random access mentioned above.

[0465] In scenarios 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 can be different. For example, the first type RO and the second type RO use frequency division multiplexing and can be configured on different carriers, subcarriers or subbands.

[0466] In other embodiments, the difference in the time-frequency domain position between the first type of RO and the second type of RO is mainly due to their different time-domain positions.

[0467] For example, the time slot where the second type of RO is located is different from the time slot where the first type of RO is located, or,

[0468] The subframe containing the second type of RO is different from the subframe containing the first type of RO, or...

[0469] The radio frame containing the second type of RO is different from the radio frame containing the first type of RO, or

[0470] The second type of RO is located in the same time slot as the first type of RO, and the start symbol of the second type of RO is different from that of the first type of RO.

[0471] In some embodiments, the time-frequency domain locations of the first type of RO and the second type of RO may overlap. For example, the candidate resource locations of the first type of RO and the second type of RO may be the same, in which case the RA-RNTI corresponding to the second type of RO and the RA-RNTI corresponding to the first type of RO will be different. The difference in the RA-RNTI corresponding to the first type of RO and the second type of RO can be distinguished by at least one of the following methods.

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

[0473] For example, when RA-RNTI is calculated based on the index corresponding to the time-frequency domain position of RO, the RA-RNTI corresponding to the first type of RO and the second type of RO can be different by introducing one or more offsets.

[0474] For example, the frequency domain index of the second type of RO is obtained by continuing to number the frequency domain index of the first type of RO, or the frequency domain index of the first type of RO is obtained by continuing to number the frequency domain index of the second type of RO. In this implementation, it is equivalent to connecting the frequency domain indices of the first type of RO and the second type of RO.

[0475] For example, if there are M ROs of type I in the frequency domain, they are numbered starting from 0 or 1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type I ROs. Further, after the type I ROs are numbered, the type II ROs are numbered starting from M or M+1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the type II ROs. Using this method, even if the type I ROs and type II ROs are located within the same frequency domain, their frequency domain indices will obviously be different. Here, M represents the number of type I ROs in the frequency division multiplexing domain.

[0476] For example, if there are S type ROs of the second category in the frequency domain, then the S ROs are numbered starting from 0 or 1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the second category ROs. Further, after the second category ROs are numbered, the first category ROs are numbered starting from S or S+1 according to their frequency domain position from high to low or low to high to obtain the frequency domain index of the second category ROs. Using this method, even if the first and second category ROs are located within the same frequency domain, their frequency domain indices will obviously be different. Here, S represents the number of second category ROs in the frequency domain that are frequency-division multiplexed.

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

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

[0479] For example, the starting index of the frequency domain index of the first type of RO is different from that of the frequency domain index of the second type of RO.

[0480] In some embodiments, the starting index of the first type of RO starts from 0, while the starting index of the second type of RO starts from a specified location on the network device or a location agreed upon by the protocol. Furthermore, the starting index of the second type of RO avoids the range of the frequency domain index of the first type of RO. Optionally, in this case, the system message may carry the starting index of the frequency domain index of the second type of RO.

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

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

[0483] Similarly, when the frequency domain index of the first type of RO is different from that of the second type of RO, the formula for calculating RA-RNTI can be found in the aforementioned calculation of RA-RANT for four-step random access or two-step random access.

[0484] In other embodiments, the resource locations of the first type of RO and the second type of RO may be the same, and the frequency domain indexes of the first type of RO and the second type of RO may also start from the same position. For example, the frequency domain indexes of the first type of RO and the second type of RO may both start from 0 or 1. In this case, in order to distinguish the RA-RNTI corresponding to the first type of RO and the second type of RO, one or more parameters for calculating the RA-RNTI can be introduced.

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

[0486] Example 1: An offset (which can be called the first offset) is introduced into the RA-RNTI calculation formula for the first type of RO. The size of this 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 where the configuration information of the first type of RO is located.

[0487] Example 2: An offset (which can be called the second offset) is introduced into the RA-RNTI calculation formula for the second type of RO. The size of this 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.

[0488] Example 3: Different offsets can be introduced into the calculation formulas for Type I RO and Type II RO, thus achieving the same distinction between RA-RNTI for Type I RO and Type II RO. The magnitudes 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.

[0489] When using Example 1 or Example 2, only an offset needs to be introduced into the calculation of RA-RNTI for the first type of RO or the second type of RO. When using Example 3, offsets for calculating RA-RNTI are introduced for both the first type of RO and the second type of RO.

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

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

[0492] MSGB-RNTI can be RA-RNTI for two-step random access, MSG1-RA-RNTI can be RA-RANTI for four-step random access, and offset can be the offset introduced above.

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

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

[0495] In some embodiments, the second information instructs the RRC connected-state terminal to perform non-contention-based random access (CFRA).

[0496] In some embodiments, the second information indicates at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; or the RO used to perform CFRA is located on the uplink time unit.

[0497] For example, the second information indicates the range of random access preambles for CFRA, and the terminal can randomly select one within the range indicated by the second information for non-contention random access when performing CFRA.

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

[0499] The type of RO used to perform CFRA here may include, but is not limited to, the aforementioned Type I RO and / or Type II RO.

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

[0501] In some real-time examples, the RO for contention-based random access can also be a Type I RO and / or a Type II RO.

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

[0503] In some embodiments, the second information directly includes the configuration information of the CFRA using the RO, so there is no need to associate it with the configured RO.

[0504] In some embodiments, the second information indicates whether CFRA can use a Type 1 RO. If the second information indicates that non-contentionable random access does not use a Type 1 RO, then by default at least a Type 2 RO can be used.

[0505] In some embodiments, when the second information indicates that the CFRA uses the first type of RO, it can be considered that non-contention-based random access can use both the first type of RO and the second type of RO simultaneously.

[0506] In some embodiments, the RO used for non-contention-based random access is the RO indicated by the second information. For example, if the second information indicates that the CFRA uses a first-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses a second-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses both a first-type RO and a second-type RO, then the corresponding terminal uses both types of ROs when performing random access.

[0507] The second information indicates that the RO used by the CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type I RO. The second information indicates that the RO used by the CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type II RO.

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

[0509] S4103: Initiate random access.

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

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

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

[0513] In some embodiments, the RRC connected terminal selects the RO closest to the current time from the first type of RO and the second type of RO for random access.

[0514] In some embodiments, if an RRC connected terminal has a random access requirement during the time corresponding to the DL time unit and / or F time unit, it initiates random access on the first type of RO.

[0515] In some embodiments, if an RRC connected terminal supporting SBFD technology has a random access requirement during the time corresponding to the DL time unit and / or F time unit, it initiates random access on the first type of RO.

[0516] In some embodiments, if an RRC connected terminal has a random access requirement within the time period corresponding to the UL time unit, it will initiate random access on the first type RO or the second type RO.

[0517] In some embodiments, RRC connected state terminals have a need for random access during cell handover.

[0518] In some embodiments, RRC connected terminals have random access requirements when performing Beam Failure Recovery (BFR).

[0519] In some embodiments, terminals in the RRC idle state and / or RRC inactive state select the RO closest to the current time from the first type of RO and the second type of RO for random access.

[0520] In some embodiments, terminals in the RRC idle state and / or RRC inactive state select an RO from the second type of RO for random access.

[0521] In TDD scenarios, configuring the RO (Redirect Access) on the SBFD (Site-Based Functional Time Unit) instead of limiting it to the UL (Ultimate Time Unit) increases the random access capacity of the cell. Simultaneously, it reduces random access latency for terminals with random access needs near the DL (Deep Path) and / or SBFD time units, thus improving random access efficiency. For RRC (Redirect-Controlled Functional) connected-state terminals with random access needs arising from BFR (Browser-Based Function) or cell handover, it accelerates the BFR and / or cell handover rate.

[0522] 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 the configuration information of the RO but has no random access requirement, then S4103 does not need to be executed. For example, if the terminal receives the configuration information of the RO and can determine whether it should use non-contention random access according to the protocol, then it does not need to receive the second information from the network device.

[0523] Some embodiments may include steps S4101 to S4102, meaning S4103 is an optional step. For example, if the terminal receives configuration information from the RO but has no random access requirement, then step S4103 does not need to be executed.

[0524] like Figure 4B As shown in the embodiments of this disclosure, an information processing method is provided, which may include:

[0525] S4201: Terminal receives system messages.

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

[0527] In some embodiments, the first configuration information can be used to indicate the RO. Optionally, the RO may include a first type of RO and / or a second type of RO.

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

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

[0530] In some embodiments, the first type of RO is used for random access of connected terminals in Radio Resource Control (RRC) mode.

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

[0532] S4202: The terminal receives the first information.

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

[0534] In some embodiments, the first information is used for terminals that are capable of using a first type of RO located on the downlink time unit and / or flexible time unit of the SBFD time unit.

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

[0536] In some embodiments, the first information may indicate terminal information that can use the first type of RO.

[0537] In some embodiments, the first information is used for terminals that are capable of using a first type of RO located in the downlink time and / or flexible time of the SBFD time unit.

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

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

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

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

[0542] Thus, the terminal will determine whether it can use the first type of RO based on the first information.

[0543] In some embodiments, the first information may also indicate the conditions for using a first type of RO. Thus, a terminal that meets 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 then use the first type of RO when the conditions are met.

[0544] 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 may include RRC connected state, RRC idle state and / or RRC inactive state. For example, the condition may allow terminals in the RRC connected state to use the first type of RO, while prohibiting terminals in the RRC idle state and / or RRC inactive state from using the first type of RO; the triggering event for random access using the first type of RO, which may include, but is not limited to: cell handover, beam failure recovery, connection recovery, cell reselection; for example, the use of the first type of RO may be allowed for cell handover, beam failure recovery and / or connection recovery; the time range and / or spatial range for using the first type of RO, etc.

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

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

[0547] For example, terminals in RRC idle state and / or RRC inactive state automatically do not use RO on SBFD time unit. However, terminals in RRC connected state will assume that they can use RO on SBFD time unit.

[0548] For example, a terminal that does not support SBFD technology will automatically not use the RO on the SBFD time unit. However, a terminal that supports SBFD technology will assume that it can use the RO on the SBFD time unit.

[0549] In some 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 the protocol, and the network device side will not send the first information.

[0550] S4203: The network device sends the second message.

[0551] In some embodiments, the network device sends RRC-specific signaling containing second information.

[0552] In some embodiments, the network device sends PDCCH signaling containing second information. This PDCCH signaling may include, but is not limited to, DCI.

[0553] In some embodiments, the second information may indicate non-contention-based random access.

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

[0555] In some embodiments, the second information may be carried in RRC-specific signaling that is different from the configuration information sent to the RO.

[0556] For example, during cell handover for an RRC connected terminal, the cell handover command can carry the second information. That is, while instructing the RRC connected terminal to perform cell handover through the cell handover command, the second information carried in the cell handover command also indicates that the RRC connected terminal uses non-contention-based random access during the random access process to the target cell.

[0557] In some embodiments, when a terminal uses beam communication, the second information is carried in the network signaling where the terminal's beam configuration or beam failure configuration is located. Thus, when an RRC-connected terminal performs beam recovery, it naturally uses non-contention-based random access for random access.

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

[0559] For example, the parameter includes, but is not limited to, at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; the RO used to perform CFRA is located on the SBFD; the RO used to perform CFRA is located on the uplink time unit.

[0560] For example, the second information indicates the range of random access preambles for CFRA, and the terminal can randomly select one within the range indicated by the second information for non-contention random access when performing CFRA.

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

[0562] The type of RO used to perform CFRA here may include, but is not limited to, the aforementioned Type I RO and / or Type II RO.

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

[0564] In some real-time examples, the RO for contention-based random access can also be a Type I RO and / or a Type II RO.

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

[0566] In some embodiments, the second information directly includes the configuration information of the CFRA using the RO, so there is no need to associate it with the configured RO.

[0567] In some embodiments, the second information indicates whether CFRA can use a Type 1 RO. If the second information indicates that non-contentionable random access does not use a Type 1 RO, then by default at least a Type 2 RO can be used.

[0568] In some embodiments, when the second information indicates that the CFRA uses the first type of RO, it can be considered that non-contention-based random access can use both the first type of RO and the second type of RO simultaneously.

[0569] In some embodiments, the RO used for non-contention-based random access is the RO indicated by the second information. For example, if the second information indicates that the CFRA uses a first-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses a second-type RO, then the corresponding terminal uses the first-type RO when performing random access. If the second information indicates that the CFRA uses both a first-type RO and a second-type RO, then the corresponding terminal uses both types of ROs when performing random access.

[0570] The second information indicates that the RO used by the CFRA is located in the SBFD time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type I RO. The second information indicates that the RO used by the CFRA is located in the uplink time unit, which is equivalent to indicating that the RO used by the terminal during CFRA is a Type II RO.

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

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

[0573] Some embodiments may include steps S4201 to S4202, i.e., S4203 is an optional step. For example, if the protocol specifies or pre-configures an indication of a non-random access terminal, condition, or scenario, then receiving the second information is unnecessary.

[0574] In the embodiments disclosed herein, 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 in other embodiments.

[0575] In the embodiments disclosed herein, 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 in other embodiments.

[0576] This disclosure also provides apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, or a core network device) in any of the above methods.

[0577] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0578] In this disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a type of microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit 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.

[0579] Figure 6A This disclosure provides a network device comprising:

[0580] Processing module 110 is configured to configure a first type of RO on the sub-band full-duplex SBFD time unit.

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

[0582] In some embodiments, the receiving module and / or transmitting module may correspond to specific structures such as the terminal's antenna or network interface.

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

[0584] Based on the above scheme, the first type of RO is used for random access of RRC connected terminals.

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

[0586] Based on the above scheme, the network device's sending module is configured to send RRC dedicated signaling; the RRC dedicated signaling includes configuration information for the first type of RO.

[0587] Based on the above scheme, the network device's sending module is configured to send system messages, which include configuration information for the second type of RO, and the second type of RO is configured on the uplink time unit.

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

[0589] Based on the above scheme, the time slot where the second type of RO is located is different from the time slot where the first type of RO is located, or...

[0590] The subframe containing the second type of RO is different from the subframe containing the first type of RO, or...

[0591] The radio frame containing the second type of RO is different from the radio frame containing the first type of RO, or

[0592] The second type of RO is located in the same time slot as the first type of RO, and the start symbol of the second type of RO is different from that of the first type of RO.

[0593] Based on the above scheme, the resource locations of the second type of RO overlap with those of the first type of RO, and the RA-RNTI corresponding to the second type of RO is different from that corresponding to the first type of RO.

[0594] Based on the above scheme, the frequency domain index of the first type of RO is different from that of the second type of RO.

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

[0596] Based on the above scheme, the system message includes: the number of the first type of RO in frequency division multiplexing.

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

[0598] Based on the above scheme, the RA-RNTI corresponding to the first type of RO is generated based on the offset, while the RA-RNTI corresponding to the second type of RO is not generated based on the offset.

[0599] Based on the above scheme, 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 and the offset corresponding to the second type of RO are different.

[0600] Based on the above scheme, the sending module of the network device is configured to send system messages; the system messages include 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.

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

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

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

[0604] Based on the above scheme, the network device's sending module is configured to send second information, which instructs the RRC connected state terminal to perform non-contention random access (CFRA).

[0605] Based on the above scheme, the second information indicates at least one of the following: the random access preamble used to perform CFRA; the resource index of the RO used to perform CFRA; the type of the RO used to perform CFRA; the configuration information of the RO used to perform CFRA; whether the RO used to perform CFRA is located on the SBFD time unit; whether the RO used to perform CFRA is located on the SBFD; or whether the RO used to perform CFRA is located on the uplink time unit.

[0606] Figure 6B This is a schematic diagram of the structure of the terminal provided in an embodiment of this disclosure. For example... Figure 6B As shown, the master node includes:

[0607] The receiving module 120 is configured to receive configuration information, wherein the configuration information indicates that the ROs include a first type of RO located on the SBFD time unit.

[0608] In some embodiments, the receiving module and the transmitting module may correspond to specific structures such as the terminal's antenna or network interface.

[0609] Optionally, the terminal further includes a storage module and / or a processing module, the storage module being configured for information storage. The processing module being configured to execute information processing-related steps in an information processing method performed by the terminal.

[0610] Based on the above scheme, the first type of RO is used for random access of RRC connected terminals.

[0611] Based on the above scheme, the receiving module is configured to receive Radio Resource Control (RRC) dedicated signaling, which includes configuration information for the first type of RO.

[0612] Based on the above scheme, the terminal's receiving module is also configured to receive system messages, which include configuration information of the second type of RO; the second type of RO is configured on the uplink time unit.

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

[0614] Based on the above scheme, the time slot where the second type of RO is located is different from the time slot where the first type of RO is located, or...

[0615] The subframe containing the second type of RO is different from the subframe containing the first type of RO, or...

[0616] The radio frame containing the second type of RO is different from the radio frame containing the first type of RO, or

[0617] The second type of RO is located in the same time slot as the first type of RO, and the start symbol of the second type of RO is different from that of the first type of RO.

[0618] Based on the above scheme, the resource locations of the second type of RO overlap with those of the first type of RO, and the RA-RNTI corresponding to the second type of RO is different from that corresponding to the first type of RO.

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

[0620] Based on the above scheme, the frequency domain index of the first type of RO is different from that of the second type of RO;

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

[0622] Based on the above scheme, the system message includes: the number of the first type of RO in frequency division multiplexing.

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

[0624] Based on the above scheme, the RA-RNTI corresponding to the first type of RO is generated based on the offset, while the RA-RNTI corresponding to the second type of RO is not generated based on the offset.

[0625] Based on the above scheme, 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 and the offset corresponding to the second type of RO are different.

[0626] Based on the above scheme, configuration information is received, including:

[0627] Receive system messages; the system messages include first configuration information, 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;

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

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

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

[0631] Based on the above scheme, the terminal's receiving module is configured to receive second information, which instructs the RRC connected state terminal to perform non-contention random access (CFRA).

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

[0633] The random access preamble used to execute CFRA;

[0634] The resource indexes of the RO used to execute CFRA;

[0635] The type of RO used to execute CFRA;

[0636] Configuration information for the RO used to execute CFRA;

[0637] Is the RO used to perform CFRA located in the time unit of SBFD?

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

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

[0640] This disclosure also provides a communication device, which may include one or more processors; wherein the processors are configured to invoke instructions to cause the communication device to perform the methods that can be implemented in any of the foregoing embodiments.

[0641] In some embodiments, such as Figure 7A and / or Figure 7B As shown, the communication device 8100 also includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

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

[0643] 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 transceivers 8103, and other steps are performed by the processor 8101.

[0644] 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, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

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

[0646] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in this disclosure is not limited thereto, and the structure of the communication device 8100 may vary. Figure 7AThe limitations. Communication equipment can be a standalone device or part of a larger device. For example, communication equipment can be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components 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, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle-mounted device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0647] Figure 7B This is a schematic diagram of the structure of chip 8200 provided in an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to... Figure 7B The diagram shown is a schematic of the structure of chip 8200, but it is not limited to this.

[0648] Chip 8200 includes one or more processors 8201, which are used to invoke instructions to cause chip 8200 to execute any of the above RO configuration methods.

[0649] In some embodiments, chip 8200 further includes one or more interface circuits 8202 connected to memory 8203. Interface circuits 8202 can be used to receive signals from memory 8203 or other devices, and can also 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 those instructions to processor 8201. Optionally, terms such as interface circuit, interface, transceiver pin, and transceiver can be used interchangeably.

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

[0651] This disclosure also provides a storage medium storing instructions that, when executed on a communication device 8100, cause the communication device 8100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but it can also be a storage medium readable by other devices. Optionally, the storage medium can be a non-transitory storage medium, but it can also be a temporary storage medium.

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

[0653] This disclosure also provides a computer program that, when run on a computer, causes the computer to perform any of the above RO configuration methods.

[0654] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0655] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for configuring random access channel timing (RO), wherein, Performed by a network device, the method includes: A system message is sent to the terminal, the system message being used to configure a first type of RO on the sub-band full-duplex SBFD time unit and a second type of RO on the uplink time unit; wherein, whether the frequency domain index of the first type of RO and the frequency domain index of the second type of RO are continuous is determined based on the number of frequency division multiplexing of different types of RO and the setting position of the starting index of different types of RO; the conditions for using the first type of RO include at least one of the following: the RRC state of the terminal using the first type of RO, the triggering event for random access using the first type of RO, the time range for using the first type of RO, and the spatial range for using the first type of RO; The terminal determines the RO for random access based on at least one of the following in the first type of RO and the second type of RO: When the terminal is in RRC connected state, the RO closest to the current time among the first type RO and the second type RO is used for random access; When the terminal is in RRC connection state and there is a need for random access during the time corresponding to the downlink time unit and / or flexible time unit, the first type of RO is used for random access; When the terminal is in RRC connection state and there is a random access requirement within the time corresponding to the uplink time unit, the first type RO or the second type RO is used for random access. When the terminal is in the RRC idle state and / or the RRC inactive state, the RO closest to the current time in the first type of RO and the second type of RO is used for random access; When the terminal is in RRC idle state and / or RRC inactive state, the second type of RO is used for random access.

2. The method according to claim 1, wherein, The method further includes: sending RRC dedicated signaling; the RRC dedicated signaling includes configuration information of the first type of RO and the starting index of the frequency domain index of the first type of RO; the starting index of the frequency domain index is located outside the index range corresponding to the frequency domain index of the second type of RO.

3. The method according to claim 1, wherein, The resource locations of the second type of RO do not overlap with those of the first type of RO.

4. The method according to claim 1, wherein, The second type of RO and the first type of RO have overlapping resource locations, and the random access response radio network temporary identifier (RA-RNTI) of the second type of RO is different from that of the first type of RO.

5. The method according to claim 4, wherein, The frequency domain index of the first type of RO is different from that of the second type of RO.

6. The method according to claim 5, wherein, 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.

7. The method according to claim 1, wherein, The system message includes: the number of the first type of ROs in frequency division multiplexing.

8. The method according to claim 4, wherein, The RA-RNTI corresponding to the first type of RO is generated based on the offset, while the RA-RNTI corresponding to the second type of RO is not generated based on the offset.

9. The method according to claim 4, wherein, Both the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO are generated based on the offset, and the offsets corresponding to the first type of RO and the second type of RO are different.

10. The method according to any one of claims 1 to 9, wherein, The method further includes: Send first information; the first information is used to determine at least one of the following: a terminal that can use the first type of RO, or a terminal that can use the second type of RO.

11. The method according to claim 1, wherein, The method further includes: Send a second message, which instructs the RRC connected-state terminal to perform non-contention-based random access (CFRA). The second information further indicates at least one of the following: the random access preamble used to execute the CFRA; the resource index of the RO used to execute the CFRA; the type of the RO used to execute the CFRA; the configuration information of the RO used to execute the CFRA; whether the RO used to execute the CFRA is located on the SBFD time unit; the RO used to execute the CFRA is located on the SBFD; or the RO used to execute the CFRA is located on the uplink time unit.

12. An information processing method, wherein, The method, executed by a terminal, includes: The system message sent by the network device is used to configure a first type of RO on the sub-band full-duplex SBFD time unit and a second type of RO on the uplink time unit; wherein, whether the frequency domain index of the first type of RO and the frequency domain index of the second type of RO are continuous is determined based on the number of frequency division multiplexing of different types of RO and the setting position of the starting index of different types of RO; the conditions for using the first type of RO include at least one of the following: the RRC state of the terminal using the first type of RO, the triggering event for random access using the first type of RO, the time range for using the first type of RO, and the spatial range for using the first type of RO; Initiating random access on a Type I or Type II RO, including at least one of the following: RRC connected terminals randomly connect to the RO closest to the current time from the first type of RO and the second type of RO. When an RRC connected terminal has a random access requirement during the time corresponding to the downlink time unit and / or flexible time unit, it initiates random access on the first type of RO. When an RRC connected terminal has a random access requirement within the time corresponding to the uplink time unit, it initiates random access on a Type I RO or a Type II RO. Terminals in the RRC idle state and / or RRC inactive state select the RO closest to the current time from the first type of RO and the second type of RO for random access; Terminals in the RRC idle state and / or RRC inactive state select an RO from the second type of RO for random access.

13. The method according to claim 12, wherein, The method further includes: receiving RRC dedicated signaling; the RRC dedicated signaling includes configuration information of the first type of RO and the starting index of the frequency domain index of the first type of RO; the starting index of the frequency domain index is located outside the index range corresponding to the frequency domain index of the second type of RO.

14. The method according to claim 12, wherein, The resource locations of the second type of RO do not overlap with those of the first type of RO.

15. The method according to claim 12, wherein, The resource locations of the second type of RO and the first type of RO overlap, and the random access response radio network temporary identifiers (RA-RNTI) of the second type of RO and the first type of RO are different.

16. The method according to claim 15, wherein, The frequency domain index of the first type of RO is different from that of the second type of RO.

17. The method according to claim 16, wherein, The frequency domain index of the first type of RO is different from that 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.

18. The method according to claim 12, wherein, The system message includes: the number of the first type of ROs in frequency division multiplexing.

19. The method according to claim 15, wherein, The RA-RNTI corresponding to the first type of RO is generated based on the offset, while the RA-RNTI corresponding to the second type of RO is not generated based on the offset.

20. The method of claim 15, wherein, Both the RA-RNTI corresponding to the first type of RO and the RA-RNTI corresponding to the second type of RO are generated based on the offset, and the offset corresponding to the first type of RO and the offset corresponding to the second type of RO are different.

21. The method according to any one of claims 12 to 20, wherein, The method further includes: Receive first information; the first information is used to determine at least one of the following: a terminal that can use the first type of RO, or a terminal that can use the second type of RO.

22. The method according to claim 21, wherein, The method further includes: Receive the second information, which instructs the RRC connected state terminal to perform non-contention random access (CFRA); The second information further indicates at least one of the following: the random access preamble used to execute the CFRA; the resource index of the RO used to execute the CFRA; the type of the RO used to execute the CFRA; the configuration information of the RO used to execute the CFRA; whether the RO used to execute the CFRA is located on the SBFD time unit; the RO used to execute the CFRA is located on the SBFD; or the RO used to execute the CFRA is located on the uplink time unit.

23. A network device, wherein, include: The processing module is configured to send a system message to the terminal. The system message is used to configure a first type of RO on the sub-band full-duplex SBFD time unit and a second type of RO on the uplink time unit. The continuity of the frequency domain index of the first type of RO and the frequency domain index of the second type of RO is determined based on the number of frequency division multiplexing of different types of RO and the setting position of the starting index of different types of RO. The conditions for using the first type of RO include at least one of the following: the RRC state of the terminal using the first type of RO, the trigger event for random access using the first type of RO, the time range for using the first type of RO, and the spatial range for using the first type of RO. The terminal determines the RO for random access based on at least one of the following in the first type of RO and the second type of RO: When the terminal is in RRC connected state, the RO closest to the current time among the first type RO and the second type RO is used for random access; When the terminal is in RRC connection state and there is a need for random access during the time corresponding to the downlink time unit and / or flexible time unit, the first type of RO is used for random access; When the terminal is in RRC connection state and there is a random access requirement within the time corresponding to the uplink time unit, the first type RO or the second type RO is used for random access. When the terminal is in the RRC idle state and / or the RRC inactive state, the RO closest to the current time in the first type of RO and the second type of RO is used for random access; When the terminal is in RRC idle state and / or RRC inactive state, the second type of RO is used for random access.

24. A terminal, wherein, include: The receiving module is configured to receive system messages sent by the network device. These system messages are used to configure a first type of Remote Access Regulator (RO) on a sub-band full-duplex (SBFD) time unit and a second type of RO on an uplink time unit. Whether the frequency domain indexes of the first type of RO and the second type of RO are consecutive is determined based on the number of frequency division multiplexing operations of different types of ROs and the setting position of the starting indexes of different types of ROs. The conditions for using a first type of RO include at least one of the following: the RRC state of the terminal using the first type of RO, a trigger event for random access using the first type of RO, a time range for using the first type of RO, and a spatial range for using the first type of RO. Initiating random access on a Type I or Type II RO, including at least one of the following: RRC connected terminals randomly connect to the RO closest to the current time from the first type of RO and the second type of RO. When an RRC connected terminal has a random access requirement during the time corresponding to the downlink time unit and / or flexible time unit, it initiates random access on the first type of RO. When an RRC connected terminal has a random access requirement within the time corresponding to the uplink time unit, it initiates random access on a Type I RO or a Type II RO. Terminals in the RRC idle state and / or RRC inactive state select the RO closest to the current time from the first type of RO and the second type of RO for random access; Terminals in the RRC idle state and / or RRC inactive state select an RO from the second type of RO for random access.

25. A communication device, wherein, The communication device includes: One or more processors; The processor is configured to invoke instructions to cause the communication device to perform the method according to any one of claims 1 to 11 and / or claims 12 to 22.

26. A storage medium, wherein, The storage medium stores instructions that, when executed on a communication device, cause the communication device to perform the method described in any one of claims 1 to 11 and / or claims 12 to 22.

Images