Communication method, communication device, communication system, storage medium and program product
Patent Information
- Application Number
- PCT/CN2025/078649
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-21
- Publication Date
- 2026-08-27
Smart Images

Figure CN2025078649_27082026_PF_FP_ABST
Abstract
Description
Communication methods, communication equipment, communication systems, storage media and software products Technical Field
[0001] This disclosure relates to the field of wireless communication, and more particularly to a communication method, communication device, communication system, storage medium, and program product. Background Technology
[0002] In communication systems, to enable random access, the network side can configure a random access channel (RACH) for the terminal. The terminal can then perform random access based on the RACH occasion (RO) specified in the RACH configuration. Summary of the Invention
[0003] This disclosure relates to a communication method, communication device, communication system, storage medium, and program product.
[0004] According to a first aspect of the present disclosure, a communication method is provided. The method is performed by a terminal. The method includes: acquiring first information, wherein the first information includes a RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being mapped to a plurality of SSBs; wherein the second information indicates whether a second random access resource is added or removed based on the first random access resource.
[0005] According to a second aspect of the present disclosure, a communication method is provided. The method is performed by a terminal. The method includes: sending first information to the terminal, wherein the first information includes RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being mapped to a plurality of SSBs; wherein the second information indicates whether a second random access resource is added or removed based on the first random access resource.
[0006] According to a third aspect of the present disclosure, a communication device is provided. The method is performed by a network device. The communication device is used to perform the communication method as described in the first or second aspect.
[0007] According to a fourth aspect of the present disclosure, a communication system is provided. The communication system includes a terminal and a network device. The terminal is configured to perform the communication method as described in the first aspect. The network device is configured to perform the communication method as described in the second aspect.
[0008] According to a fifth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in the first or second aspect.
[0009] According to a sixth aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in the first or second aspect.
[0010] According to a seventh aspect of the present disclosure, a computer program is provided. When executed on a computer, the computer program causes the computer to perform the communication method as described in either the first or second aspect.
[0011] According to an eighth aspect of this disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method as described in either the first or second aspect.
[0012] According to embodiments of this disclosure, the utilization rate of random access resources in a communication system can be improved.
[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on 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 1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.
[0016] Figure 2A is a schematic diagram of an SBFD time unit provided according to an embodiment of the present disclosure.
[0017] Figure 2B is a schematic diagram of RO in the SBFD symbol provided according to an embodiment of the present disclosure.
[0018] Figure 2C is a schematic diagram of the RO time-frequency position provided according to an embodiment of the present disclosure.
[0019] Figures 3A to 3C are schematic diagrams illustrating the mapping relationship between SSB and RO according to embodiments of the present disclosure.
[0020] Figure 4 is a schematic diagram of PRACH repetition provided according to an embodiment of the present disclosure.
[0021] Figure 5 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.
[0022] Figure 6A is a schematic diagram of the mapping relationship between SSB and RO provided according to an embodiment of the present disclosure.
[0023] Figure 6B is a schematic diagram of the mapping relationship between SSB and RO provided according to an embodiment of the present disclosure.
[0024] Figure 7A is a schematic diagram of the mapping relationship between SSB and RO provided according to an embodiment of the present disclosure.
[0025] Figure 7B is a schematic diagram of the mapping relationship between SSB and RO provided according to an embodiment of the present disclosure.
[0026] Figure 7C is a schematic diagram of the mapping relationship between SSB and RO provided according to an embodiment of the present disclosure.
[0027] Figure 7D is a schematic diagram of the mapping relationship between SSB and RO provided according to an embodiment of the present disclosure.
[0028] Figure 8 is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.
[0029] Figure 9 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.
[0030] Figure 10 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.
[0031] Figure 11A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.
[0032] Figure 11B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation
[0033] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0034] In a first aspect, embodiments of this disclosure provide a communication method. The method is executed by a terminal. The method includes: acquiring first information, wherein the first information includes a RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being mapped to a plurality of SSBs; wherein the second information indicates whether a second random access resource is added or removed based on the first random access resource.
[0035] In conjunction with some embodiments of the first aspect, in some embodiments the first random access resource includes: RO; preamble.
[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the second random access resource includes at least one of the following: an unavailable RO in the first random access resource; an unavailable preamble in the first random access resource; an available RO outside the first random access resource; and an available preamble outside the first random access resource.
[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal does not expect there to be any remaining random access resources in the first period, and the number of remaining random access resources is less than the number of random access resources required for the mapping of multiple SSBs.
[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first cycle includes one of the following: RACH configuration cycle; association cycle; association pattern cycle; preset cycle.
[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the second information is obtained through one of the following means: protocol agreement; or receiving from a network device.
[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: determining a third random access resource within a first period based on first information; determining a mapping relationship between a plurality of SSBs and the third random access resource, wherein the plurality of SSBs are mapped on the third random access resource at least once, and the number of third random access resources is an integer multiple of the number of random access resources required for mapping the plurality of SSBs.
[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the second information indicates the addition of a second random access resource, and the third random access resource includes the first random access resource and the second random access resource, the second random access resource being within a first period.
[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the second information indicates a reduction in the second random access resource, and the third random access resource includes the random access resources in the first random access resource other than the second random access resource.
[0043] In a second aspect, embodiments of this disclosure provide a communication method. The method is executed by a terminal. The method includes: sending first information to the terminal, wherein the first information includes RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being mapped to a plurality of SSBs; wherein the second information indicates whether a second random access resource is added or removed based on the first random access resource.
[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the first random access resource includes: RO; preamble.
[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the second random access resource includes at least one of the following: an unavailable RO in the first random access resource; an unavailable preamble in the first random access resource; an available RO other than the second random access resource; and an available preamble other than the first random access resource.
[0046] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal does not expect there to be any remaining random access resources in the first cycle, and the number of remaining random access resources is less than the number of random access resources required for the mapping of multiple SSBs.
[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the first cycle includes one of the following: RACH configuration cycle; association cycle; association pattern cycle; preset cycle.
[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used by the terminal to determine the third random access resource within a first period, and the mapping relationship between the multiple SSBs and the third random access resource; wherein the multiple SSBs are mapped on the third random access resource at least once, and the number of the third random access resources is an integer multiple of the number of random access resources required for the mapping of the multiple SSBs.
[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the second information indicates the addition of a second random access resource, and the third random access resource includes the first random access resource and the second random access resource, the second random access resource being within a first period.
[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the second information indicates a reduction in the second random access resource, and the third random access resource includes the random access resources in the first random access resource other than the second random access resource.
[0051] In a third aspect, embodiments of this disclosure provide a communication method. The method is executed by a communication system. The communication system includes a terminal and a network device. The method includes: the network device sending first information to the terminal, the first information including RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being used to map to a plurality of SSBs; wherein the second information indicates whether a second random access resource is added or removed based on the first random access resource.
[0052] In a fourth aspect, embodiments of this disclosure provide a communication device. The communication device is a terminal. The communication device includes a transceiver module. The transceiver module is configured to: acquire first information, wherein the first information includes a RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being mapped to a plurality of SSBs; wherein the second information indicates whether a second random access resource is added or removed based on the first random access resource.
[0053] In conjunction with some embodiments of the fourth aspect, in some embodiments the first random access resource includes: RO; preamble.
[0054] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second random access resource includes at least one of the following: an unavailable RO in the first random access resource; an unavailable preamble in the first random access resource; an available RO other than the fourth random access resource; and an available preamble other than the first random access resource.
[0055] In conjunction with some embodiments of the fourth aspect, in some embodiments, the terminal does not expect the existence of remaining random access resources in the first cycle, and the number of remaining random access resources is less than the number of random access resources required for the mapping of multiple SSBs.
[0056] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first cycle includes one of the following: RACH configuration cycle; association cycle; association pattern cycle; preset cycle.
[0057] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information is obtained through one of the following means: protocol agreement; or receiving from a network device.
[0058] In conjunction with some embodiments of the fourth aspect, in some embodiments, the communication device further includes a processing module. The processing module is configured to: determine a third random access resource within a first period based on first information; determine a mapping relationship between a plurality of SSBs and the third random access resource, wherein the plurality of SSBs are mapped to the third random access resource at least once, and the number of third random access resources is an integer multiple of the number of random access resources required for mapping the plurality of SSBs.
[0059] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information indicates the addition of a second random access resource, and the third random access resource includes the first random access resource and the second random access resource, the second random access resource being within a first period.
[0060] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information indicates a reduction in the second random access resource, and the third random access resource includes the random access resources in the first random access resource other than the second random access resource.
[0061] In a fifth aspect, embodiments of this disclosure provide a communication device. This communication device is a network device. The communication device includes a transceiver module. The transceiver module is configured to: send first information to a terminal, wherein the first information includes RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being mapped to a plurality of SSBs; wherein the second information indicates whether a second random access resource is added or removed based on the first random access resource.
[0062] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first random access resource includes: RO; preamble.
[0063] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second random access resource includes at least one of the following: an unavailable RO in the first random access resource; an unavailable preamble in the first random access resource; an available RO other than the fifth random access resource; and an available preamble other than the first random access resource.
[0064] In conjunction with some embodiments of the fifth aspect, in some embodiments, the terminal does not expect the existence of remaining random access resources in the first cycle, the number of remaining random access resources being less than the number of random access resources required for the mapping of multiple SSBs.
[0065] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first cycle includes one of the following: RACH configuration cycle; association cycle; association pattern cycle; preset cycle.
[0066] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information is used by the terminal to determine the third random access resource within a first period, and the mapping relationship between the multiple SSBs and the third random access resource; wherein the multiple SSBs are mapped on the third random access resource at least once, and the number of the third random access resources is an integer multiple of the number of random access resources required for the mapping of the multiple SSBs.
[0067] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information indicates the addition of a second random access resource, and the third random access resource includes the first random access resource and the second random access resource, the second random access resource being within a first period.
[0068] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information indicates a reduction in the second random access resource, and the third random access resource includes the random access resources in the first random access resource other than the second random access resource.
[0069] In a sixth aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first, second, and possible embodiments thereof.
[0070] In a seventh aspect, embodiments of this disclosure provide a communication system. The communication system includes a terminal and a network device. The terminal is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The network device is configured to perform the communication method as described in any of the second aspect and its possible embodiments.
[0071] In an eighth aspect, embodiments of this disclosure provide a storage medium storing instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first, second, and possible embodiments thereof.
[0072] In a ninth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any of the first, second, and possible embodiments thereof.
[0073] In a tenth aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first, second, and possible implementations thereof.
[0074] In an eleventh aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first, second, and possible embodiments thereof.
[0075] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems 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.
[0076] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, network equipment, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.
[0077] 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.
[0078] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various 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.
[0079] 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.
[0080] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "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 or a plural expression.
[0081] In the embodiments of this disclosure, "a plurality of" means two or more.
[0082] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0083] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0084] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); 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, and C.
[0085] 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.
[0086] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0087] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0088] In some embodiments, terms such as “greater than,” “more than,” “higher than,” and “exceeding” can be used interchangeably; terms such as “greater than or equal to,” “not less than,” “more than or equal to,” “not less than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably; terms such as “less than,” “less than,” and “lower than” can be used interchangeably; and terms such as “less than or equal to,” “not greater than,” “less than or equal to,” “not more than,” “lower than or equal to,” “not higher than,” and “below” can be used interchangeably.
[0089] 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.
[0090] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0091] 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.
[0092] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0093] 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.
[0094] 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.
[0095] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0096] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0097] 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.
[0098] Figure 1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.
[0099] 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.
[0100] In some embodiments, network device 102 may include at least one of the following: access network device, core network element.
[0101] In some embodiments, the access network device is, for example, 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.
[0102] 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.
[0103] 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.
[0104] In some embodiments, the communication system 100 described above may be a 4G communication system, a 5G communication system, or a 6G communication system. It should be noted that the communication system 100 may also be other communication systems, and this disclosure does not specifically limit it.
[0105] 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 proposed 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 proposed in this disclosure are also applicable to similar technical problems.
[0106] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or some of the main components in the communication system 100, but are not limited thereto. The main components shown in FIG1 are illustrative. The communication system 100 may include all or some of the main components in FIG1, or may include other main components other than those in FIG1. The number and form of each main component are arbitrary. Each main component may be physical or virtual. The connection relationship between the main components is illustrative. The main components may not be connected or may be connected. 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.
[0107] 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), Future generation 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 communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0108] First, some concepts involved in the embodiments of this disclosure will be explained.
[0109] 1. Symbol:
[0110] The abbreviation for time-domain symbol can also be called orthogonal frequency division multiplexing (OFDM) symbol. It should be noted that time-domain symbols can also be combined with other multiple access methods, and this disclosure does not limit this. The length of the time-domain symbol can vary for different subcarrier spacings.
[0111] In some embodiments, the symbols within a time slot may include three types: downlink symbols (which can be denoted as DL symbols), uplink symbols (which can be denoted as UL symbols), and flexible symbols (which can be denoted as F symbols). Uplink symbols are used only for uplink transmission, and downlink symbols are used only for downlink transmission. Flexible symbols do not have a defined transmission direction and can be used for either uplink or downlink transmission according to control signaling instructions. In some embodiments, the symbols in a time slot may be all downlink symbols, all uplink symbols, all flexible symbols, or a mixture of multiple symbol types.
[0112] In some embodiments, the DL symbol and the F symbol may be further configured as SBFD symbols.
[0113] In some embodiments of this disclosure, a "time slot" can be understood as a time slot containing 14 OFDM symbols, a sub-slot containing 7 OFDM symbols, or a mini-slot containing 2 or 4 OFDM symbols. Of course, the "time slot" described in this disclosure may also include other numbers of OFDM symbols, and this disclosure does not specifically limit this.
[0114] 2. Sub-band:
[0115] A subband is a portion of the frequency band of a carrier, that is, one or more consecutive physical resource blocks (PRBs) in the frequency domain. In the embodiments of this disclosure, a subband can also be understood as a frequency domain resource.
[0116] 3. SBFD:
[0117] In the SBFD scheme, a carrier is divided into multiple non-overlapping subbands, and the transmission directions of different subbands can be different. That is, a carrier includes a first subband and a second subband that do not overlap, and the transmission directions of the first subband and the second subband can be different.
[0118] It should be noted that the first subband and the second subband refer to two types of subbands with different transmission directions, and do not mean that a carrier contains only two subbands. In one example, a carrier includes subband #1 and subband #2, where subband #1 and subband #2 have different transmission directions. Alternatively, a carrier includes subband #1, subband #2, and subband #3, where subband #1 and subband #3 have the same transmission direction, and subband #1 and subband #2 have different transmission directions.
[0119] 4. SBFD time unit:
[0120] The frequency resources on an SBFD time unit include two or more sub-bands with different transmission directions. In some embodiments, an SBFD time unit may include SBFD time slots, SBFD symbols, etc. Figure 2A is a schematic diagram of an SBFD time unit provided according to an embodiment of the present disclosure. In Figure 2A, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. As shown in Figure 2A, taking an SBFD time unit as an example, time slots #1, #2, and #3 are all SBFD time slots, and each time slot contains 14 SBFD symbols.
[0121] In some embodiments, the SBFD time unit is a time unit that includes at least one SBFD symbol.
[0122] In some embodiments, the SBFD time unit is a time unit in which all symbols are SBFD symbols.
[0123] In some embodiments, a guard band (GB) may also exist between the DL subband and the UL subband. The guard band isolates the DL subband and the UL subband in the frequency domain to reduce interference between the DL signals in the DL subband and the UL signals in the UL subband.
[0124] In some embodiments, in the SBFD time unit, the DL subband cannot be used for UL transmission, the UL subband can be used for uplink transmission, and the GB can be used for uplink transmission; or, the DL subband cannot be used for UL transmission, the UL subband can be used for uplink transmission, and the GB cannot be used for uplink transmission.
[0125] 6. Non-SBFD time unit:
[0126] The transmission direction is consistent across all frequency resources on non-SBFD time units. In one example, continuing to refer to Figure 2A, time slot #0 is a DL time slot, and time slot #4 is a UL time slot. The DL time slot contains 14 DL symbols, and the UL time slot contains 14 UL symbols.
[0127] In some embodiments, in an SBFD symbol, a CC includes both an uplink frequency domain range and a downlink frequency domain range. In a non-SBFD symbol, however, the frequency domain range of the entire CC is either the uplink or downlink frequency domain range. Therefore, the uplink frequency domain range in an SBFD symbol may differ from that in a non-SBFD symbol, and the downlink frequency domain range in an SBFD symbol may also differ from that in a non-SBFD symbol.
[0128] In some embodiments, a non-SBFD time unit is a time unit that includes at least one non-SBFD symbol.
[0129] In some embodiments, a non-SBFD time unit is a time unit in which all symbols are non-SBFD symbols.
[0130] In some embodiments, the uplink frequency domain range can be understood as a frequency domain range on a CC that can be used for uplink transmission, and the downlink frequency domain range can be understood as a frequency domain range on a CC that can be used for downlink transmission.
[0131] In some embodiments, in the SBFD symbol, the uplink frequency range on the uplink bandwidth part (BWP) can refer to the frequency range where the uplink BWP overlaps with the uplink frequency range on a CC.
[0132] In some embodiments, in the SBFD symbol, the uplink frequency domain range can be understood as the frequency domain range where the UL subband is located overlaps with the uplink BWP of the UE, or it can be understood as the frequency domain range where the UL subband and GB are located overlaps with the uplink BWP of the UE.
[0133] To improve uplink coverage and throughput, subband full-duplex (SBFD) is studied. In the SBFD scheme, a component carrier (CC, or simply carrier) can include multiple subbands (SBs), which can be continuous, non-overlapping frequency domain resources. These SBs can include one UL subband and at least one DL subband. Thus, UL and DL subbands may coexist within the same CC, meaning simultaneous transmission and reception can be achieved on a single CC.
[0134] 7. RO:
[0135] RO stands for Random Access Hour, which refers to the time-frequency resources occupied by a single random access operation. RO can include at least one of frequency-domain resources and time-domain resources. A terminal can transmit a random access signal on the RO to perform random access.
[0136] When the UE is in idle state, the initial access cell measures information such as the received signal strength of the SSB beam and selects the optimal SSB beam. In the direction of the optimal SSB beam, the UE transmits a PRACH signal in the RO for random access. Furthermore, in other states, the UE can also transmit a PRACH signal in the RO for random access. Random access can include contention-based random access (CBRA) and contention-free random access (CFRA). In CBRA, multiple terminals may use the same preamble sequence on the same RO. In this case, the random access signals of multiple terminals will conflict, leading to random access failure.
[0137] In some embodiments, random access (RA) can be categorized into 4-step RA and 2-step RA based on the number of steps in the random access procedure. In some embodiments, it can be categorized into CBRA and CFRA based on whether the preamble used by the UE will conflict with the preambles of other UEs. In some embodiments, in a 4-step CBRA, the UE sends Msg1 and Msg3, and the gNB sends Msg2 and Msg4. Random access is completed in 4 steps. Msg1 is the PRACH signal. In some embodiments, in a 2-step CBRA, the UE sends MsgA, and the gNB sends MsgB. Random access is completed in 2 steps. MsgA includes MsgA-PRACH and MsgA-PUSCH signals. In some embodiments, in a 4-step CFRA, the UE sends Msg1, and the gNB sends Msg2. Random access is completed in 2 steps. Msg1 is the PRACH signal. Furthermore, the gNB needs to configure the preamble used by the UE's PRACH signal in advance. In some embodiments, in a CFRA of the 2-step random access type, the UE sends MsgA, and the gNB sends MsgB. Random access is completed in two steps. MsgA includes MsgA-PRACH and MsgA-PUSCH signals. Furthermore, the gNB needs to pre-configure the preamble and PUSCH resources used by the UE's MsgA signal.
[0138] In some embodiments, the process of the UE receiving Msg2 may include: within the ra-ResponseWindow, the UE detects the DCI 1-0 scrambled with the random access-radio network temporary identifier (RA-RNTI) in the common search space (CSS) of the physical downlink control channel (PDCCH) of type 1; after demodulating the RA-RNTI scrambled DCI 1-0, the UE demodulates the random access response (RAR) carrying Msg2; the UE checks whether the random access preamble identifier (RAPID) in the RAR is consistent with the one used by the UE, and if they are consistent, it sends Msg3 using UL grant. In some embodiments, the ra-ResponseWindow does not exceed 10 milliseconds (ms). To improve UL (Msg1) coverage, support for repetition of Msg1 was implemented in Release 18.
[0139] In some embodiments, within an SBFD symbol, a terminal can transmit uplink signals on the UL subband. Therefore, configuring ROs at an SBFD symbol increases the number of ROs compared to configuring ROs only at the UL or F symbols. This allows SBFD-enabled terminals to perform random access on the ROs configured in the SBFD symbol, reducing access latency and lowering the probability of random access signal collisions between different UEs in the CBRA. In one example, Figure 2B is a schematic diagram of configuring ROs in an SBFD slot according to an embodiment of this disclosure, where the horizontal axis represents the time domain and the vertical axis represents the frequency domain. As shown in Figure 2B, within an SBFD symbol, the physical downlink share channel (PDSCH) can be transmitted on the DL subband, and the physical random access channel (PRACH) signal can be transmitted using ROs on the UL subband.
[0140] In some embodiments, the RO may include an additional RO and a legacy RO. In some embodiments, the RACH configuration used to implement the configuration of the additional RO may be referred to as the additional RACH configuration. In some embodiments, the RACH configuration used to implement the configuration of the legacy RO may be referred to as the legacy RACH configuration.
[0141] In some embodiments, the time-domain location of the RO is determined based on the parameter prach-ConfigurationIndex (PRACH configuration index) and a table used to indicate the random access configuration.
[0142] In some embodiments, prach-ConfigurationIndex can be a parameter of a higher-level configuration. In some embodiments, the value of prach-ConfigurationIndex is an integer ranging from 0 to 255.
[0143] In some embodiments, the table used to indicate the random access configuration may include the following: PRACH configuration index, preamble format, configuration period (x) of RO, position (y) of RO, subframe number, starting symbol, number of PRACH slots within a subframe, number of time-domain PRACH occasions within a PRACH slot, and PRACH duration. For example, with prach-ConfigurationIndex of 154, the preamble format is B4, the configuration period of RO is 2 frames (i.e., x=2), RO is on the odd frames of the 2 frames (y=1), RO is on subframes #2, #3, #4, #7, #8, and #9 within the odd frames, the start symbol of RO within the subframe is 0, the number of RACH slots in a subframe is 1, a PRACH slot contains 1 RO, and the length of an RO symbol is 2 symbols.
[0144] In some embodiments, the frequency domain location of the RO can be determined based on the parameters msg1-FDM and msg1-FrequencyStart. The parameter msg1-FDM indicates the number of ROs in a PRACH slot within the frequency domain. The parameter msg1-FrequencyStart indicates the starting RB in the frequency domain.
[0145] Figure 2C is a schematic diagram of the time-frequency location of ROs according to an embodiment of the present disclosure. In Figure 2C, a new valid RO refers to a valid RO on an SBFD symbol, while a conventional valid RO refers to a RO on a non-SBFD symbol. ROs are located on subframes #2, #3, #4, #7, #8, and #9. In the time domain, one PRACH slot includes one RO. Within a subframe, the symbol range of the first RO is OFDM symbol (OS) #0 to #11. In the frequency domain, one PRACH slot includes two ROs. In some embodiments, when the time-frequency location of an RO is determined, the RO is determined to be a valid RO according to certain criteria. In some embodiments, the index of a valid RO is determined according to a criterion of first the frequency domain and then the time domain.
[0146] In some embodiments, the mapping relationship between SSBs and ROs can be determined by the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. This parameter can be configured with N and R. N SSBs are associated with 1 valid RO. The number of preambles associated with each SSB in each RO is R.
[0147] Figures 3A to 3C are schematic diagrams illustrating the mapping relationship between SSB and RO according to embodiments of the present disclosure. In Figures 3A to 3C, the horizontal axis represents the symbol where the effective RO is located, and does not represent symbols that are consecutive in the time domain.
[0148] As shown in Figure 3A, under the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB configuration, N equals 4 and R equals 16. Four SSBs are mapped to one valid RO, and one SSB comprises 16 preambles. In some embodiments, the starting index of the preamble of the nth SSB in a valid RO is n×N_total / N (i.e., n×R), where N_total is the total number of preambles in a RO.
[0149] In some embodiments, SSB#0–3 are mapped to RO#0, SSB#4–7 are mapped to RO#1, and the SSB indices for other ROs can be obtained by analogy. An SSB contains 16 preambles, and the preamble indices corresponding to the four SSBs in an RO are {0–15}, {16–31}, {32–47}, and {48–63}, respectively. The time domain of RO#0–1 corresponds to OS#0–11 in time slot #2, the time domain of RO#2–3 corresponds to OS#0–11 in time slot #3, and the time domain of RO#4–5 corresponds to OS#0–11 in time slot #4.
[0150] As shown in Figure 3B, in the configuration of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, N equals 1 / 2 and R equals n64. 1 / 2 SSBs are mapped to one valid RO, that is, one SSB is mapped to two valid ROs. One SSB consists of 64 preambles, with preamble indices from 0 to 63.
[0151] In some embodiments, there are 12 valid ROs and 16 SSBs in the PRACH configuration cycle. One SSB is mapped to two valid ROs, and one SSB contains 64 preambles. SSB#0 is mapped to RO#0~1, SSB#2 is mapped to RO#2~3, and the SSB indices for other RO mappings can be obtained by analogy.
[0152] In some embodiments, all SSBs may not be mapped to a valid RO contained within a single PRACH configuration cycle. As shown in Figure 3B, there are a total of SSBs. Six SSBs can be mapped to valid ROs within one PRACH configuration cycle. Sixteen SSBs need to be mapped to valid ROs within three PRACH configuration cycles.
[0153] In some embodiments, The number of SSBs is determined based on the configuration in system information block (SIB) 1 or the parameter ssb-PositionsInBurst in the parameter ServingCellConfigCommon. Mapping each SSB to a valid RO once can be called a cycle mapping.
[0154] In some embodiments, an association period is defined. The length of the association period is N times the length of the PRACH configuration period. N is a positive integer.
[0155] In some embodiments, if after M cyclic mappings in an association cycle, the remaining ROs or preambles are insufficient for one cyclic mapping, then no SSB will be mapped to these remaining ROs or preambles. M = M1 > 1 when the valid ROs in a PRACH configuration cycle are sufficient for M1 cyclic mappings and M1 > 1; otherwise, M = 1. Here, M and M1 are both positive integers.
[0156] In some embodiments, as shown in FIG3A, the association period includes one PRACH configuration period. After one cycle mapping, RO#10 to 11 remain, so no SSB will be mapped to RO#10 to 11.
[0157] In some embodiments, as shown in FIG3B, the associated period includes 4 PRACH configuration periods. After one cycle mapping, the remaining ROs in the third PRACH configuration period are ROs #32 to 35, and the ROs in the fourth PRACH configuration period are all remaining ROs. Therefore, there will be no SSB mapped to ROs #32 to 35 or ROs in the fourth PRACH configuration period.
[0158] In some embodiments, an association pattern period is defined. In some embodiments, the association pattern period comprises N association periods. The duration of the pattern mapped between the SSB and valid ROs is less than or equal to 160 milliseconds. Here, N is a positive integer. In some embodiments, if, within a duration of 160 milliseconds, after an integer multiple of the association periods, the remaining valid ROs cannot be cyclically mapped, then no SSB will be mapped to these remaining valid ROs, and the remaining valid ROs will not be used for PRACH transmission. In some embodiments, the durations of different association periods within the N association periods can be different.
[0159] In some embodiments, as shown in Figure 3C, the durations of association periods #1, #2, and #3 are 10 milliseconds, 80 milliseconds, and 40 milliseconds, respectively. The remaining 30 milliseconds out of 160 milliseconds are insufficient for one cyclic mapping, so N=3, and SSB will not be mapped to the effective RO within the last 30 milliseconds.
[0160] In some embodiments, PRACH repetition can be introduced for the 4-step random access procedure. The network side is configured to use reference signal received power (RSRP) thresholds corresponding to 2, 4, or 8 repetitions, namely rsrp-ThresholdMsg1-RepetitionNum2-r18, rsrp-ThresholdMsg1-RepetitionNum4-r18, and rsrp-ThresholdMsg1-RepetitionNum8-r18, respectively. In some embodiments, if the RSRP threshold measured by the UE is lower than rsrp-ThresholdMsg1-RepetitionNum8-r18, 8 repetitions are used; otherwise, if the RSRP threshold measured by the UE is lower than rsrp-ThresholdMsg1-RepetitionNum4-r18, 4 repetitions are used; otherwise, if the RSRP threshold measured by the UE is lower than rsrp-ThresholdMsg1-RepetitionNum2-r18, 2 repetitions are used; otherwise, no repetition is used.
[0161] Figure 4 is a schematic diagram of a repeating PRACH according to an embodiment of the present disclosure. Figure 4 schematically illustrates a 4-time repetition, where the UE transmits PRACH on 4 consecutive valid ROs in the time domain (4 consecutive valid ROs in the time domain form an RO group).
[0162] In some embodiments, during PRACH repetition, ROs are determined to be mapped to SSBs, and ROs that are consecutively mapped to the same SSB in the time domain are grouped into RO groups. The frequency domain positions of ROs in an RO group must be the same, the ROs in the RO group must use the same transmit power, and the same preamble must be used for N repetitions.
[0163] In one example, as shown in Figure 4, each of the two SSBs is associated with a RO group. The RO group contains four time-domain contiguous ROs (mapped to the same SSB). For example, RO group #1 contains four ROs from slots #1, #2, #3, and #4.
[0164] In some embodiments, when multiple repetitions are configured, the mapping pattern between SSB and RO for different repetitions is repeated between time periods, which may contain an integer multiple of the associated pattern period.
[0165] In some embodiments, in the RACH configuration, N, representing the number of SSBs associated with a valid RO, and R, representing the number of preambles associated with SSBs in each RO, are the same.
[0166] In some cases, the number of users may vary significantly within the coverage areas of different SSBs.
[0167] Therefore, how to achieve flexible mapping between SSB and RO is a technical problem that urgently needs to be solved.
[0168] Figure 5 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 5, the communication method of this embodiment includes steps S501 to S502.
[0169] In step S501, network device 102 sends first information to terminal 101.
[0170] In some embodiments, network device 102 may send first information. In some embodiments, the first information may be sent by network device 102, but is not limited thereto, and may also be sent by other entities.
[0171] In some embodiments, terminal 101 may receive first information. In some embodiments, the first information may be received by terminal 101, but is not limited thereto, and may also be received by other entities.
[0172] In some embodiments, terminal 101 may be a terminal that supports SBFD. In some embodiments, a terminal that supports SBFD may be able to recognize SBFD configuration. In some embodiments, the terminal may be an SBFD-aware UE.
[0173] In some embodiments, terminal 101 may be a terminal that does not support SBFD. In some embodiments, a terminal that does not support SBFD cannot recognize the SBFD configuration. In some embodiments, the terminal may be a non-SBFD aware UE.
[0174] In some embodiments, the first information may be used to determine random access resources available for mapping among multiple SSBs. In some embodiments, the first information may be used to indicate the random access resources mapped to by the multiple SSBs within a first period.
[0175] In some embodiments, random access resources can be used by terminal 101 to implement random access. In some embodiments, random access resources may include at least one of the following: RO (Redirect Access Entity) and preamble. It is understood that an RO may include one or more preambles.
[0176] In some embodiments, the first information may include RACH configuration and second information. In other words, one or more preambles may constitute a RO. For example, an RO may include 32 preambles.
[0177] In some embodiments, RACH configuration can be used to determine random access resources. It should be noted that the random access resource determined based on the RACH configuration can be referred to as the first random access resource.
[0178] In some embodiments, the RACH configuration can be used by terminal 101 to determine the mapping relationship between SSBs and ROs. In some embodiments, the mapping between multiple SSBs and multiple ROs can be determined based on the RACH configuration. In some embodiments, the mapping between multiple SSBs and multiple ROs can be uniform. For example, each SSB in the multiple SSBs can be mapped to the same number of ROs. In other words, each SSB in the multiple SSBs can be associated with the same number of ROs. In some embodiments, the mapping between multiple SSBs and multiple ROs can be non-uniform. For example, each SSB in the multiple SSBs can be mapped to a different number of ROs. In other words, the number of ROs associated with each SSB in the multiple SSBs can be different. In one example, there are at least two SSBs in the multiple SSBs that are mapped to different numbers of ROs. For example, one SSB can be mapped to 1 RO, and another SSB can be mapped to 1 / 2 RO.
[0179] In some embodiments, the number of preambles contained in each RO can be the same. In a uniform case, each SSB in the plurality of SSBs can be mapped to the same number of preambles. In other words, the number of preambles associated with each SSB in the plurality of SSBs can be the same. In a non-uniform case, each SSB in the plurality of SSBs can be mapped to a different number of preambles. In other words, the number of preambles associated with each SSB in the plurality of SSBs can be different.
[0180] In some embodiments, the number of SSBs can be based on parameters. It's confirmed.
[0181] It should be noted that in the embodiments of this disclosure, "mapping" and "association" can be used interchangeably. For example, if SSB is mapped to RO, it can be understood as SSB being associated with RO. Similarly, if RO is mapped to SSB, it can be understood as RO being associated with SSB.
[0182] In some embodiments, the RACH configuration may include one of the following: a first number of preambles associated with each SSB; a second number of SSBs associated with each RO; and a third number of preambles associated with each SSB in an RO.
[0183] In some embodiments, the RACH configuration may include only a first number of preambles associated with each SSB. In this case, the RACH configuration may not include the number of SSBs associated with each RO, nor the number of preambles associated with each SSB in a RO.
[0184] In some embodiments, the first number of associated SSBs can be the same. In other words, the first number of preambles associated with each of the multiple SSBs is the same. In this case, the mapping between the multiple SSBs and the multiple ROs is uniform.
[0185] In some embodiments, the first number of associated SSBs can be different. In other words, the first number of preambles associated with each of the multiple SSBs is different. In this case, the mapping between the multiple SSBs and the multiple ROs is non-uniform.
[0186] In some embodiments, the RACH configuration may include a second number of SSBs associated with each RO and a third number of preambles associated with each SSB in a RO.
[0187] In some embodiments, the second and third numbers associated with multiple SSBs can be the same. In other words, the second number of SSBs associated with each RO can be the same, and the third number of preambles associated with each SSB in one RO can be the same. In this case, the mapping between the multiple SSBs and the multiple ROs is uniform.
[0188] In some embodiments, the second and / or third numbers associated with at least two of the multiple SSBs can be different. In other words, the second number of SSBs associated with each RO can be different among the multiple SSBs, and / or the third number of preambles associated with each SSB in one RO can be different. In this case, the mapping between the multiple SSBs and the multiple ROs is non-uniform.
[0189] In some embodiments, terminal 101 may not expect the second number of associations of multiple SSBs to all be greater than 1, and the second number of associations of multiple SSBs to be different. In this case, the RACH configuration provided by network device 102 will not configure terminal 101 in this way.
[0190] In some embodiments, terminal 101 may not expect a second number of SSB associations for a portion of the multiple SSBs to be greater than 1, and a second number of SSB associations for another portion of the SSBs to be less than or equal to 1. In this case, the RACH configuration provided by network device 102 will not configure terminal 101 in this way.
[0191] In some embodiments, terminal 101 may not expect the second number associated with any of the multiple SSBs to be greater than 1. In this case, the RACH configuration provided by network device 102 will not configure terminal 101 in this way.
[0192] In some embodiments, the RACH configuration may include range information of the preamble to which the first feature applies. In some embodiments, the first feature may be a characteristic of the preamble in the RO. For example, the first feature may be a capability characteristic of terminal 101. For example, the first feature may be used for uniform mapping or non-uniform mapping. In some embodiments, the first feature may be indicated by the parameter FeatureCombination. In some embodiments, the range information of the preamble to which the first feature applies may indicate the index range of the preamble using the feature in an RO. For example, the range information of the preamble to which the first feature applies may indicate the start index and / or end index and / or index list of the preamble. In some embodiments, the range information of the preamble to which the first feature applies may indicate the number of preambles using the feature in an RO. For example, the first feature may be CBRA, and the range information of the preamble to which the first feature applies may indicate the number of preambles used for CBRA in an RO.
[0193] In some embodiments, under uniform mapping, the index range of the preamble to which the first feature applies can be determined based on the second and third quantities. In some embodiments, for the default RACH resource, the starting index of the preamble can be 0, and the second and third quantities can be configured. In some embodiments, for the RACH resource corresponding to the parameter FeatureCombination, the starting index, the second quantity, and the third quantity of the preamble can be configured.
[0194] In some embodiments, the number of preambles in the RO to which the first characteristic applies can be determined based on a second and a third quantity. Combining the determined number of preambles with the starting index of the preambles, the index range of the preambles can be determined. In one example, the second quantity can be greater than 1, then the number of preambles in the RO to which the first characteristic applies can be the product of the second and third quantities. In another example, the second quantity can be less than or equal to 1, and the number of preambles in the RO to which the first characteristic applies can be the third quantity.
[0195] In some embodiments, the number of preambles in the RO to which the first characteristic applies can be determined based on a first quantity. Combining the determined number of preambles with the starting index of the preambles, the index range of the preambles can be determined. In one example, the first quantity can be less than or equal to the number of preambles in an RO, in which case the number of preambles in the RO to which the first characteristic applies can be the first quantity.
[0196] In some embodiments, in the case of non-uniform mapping, the index range of the preamble to which the first feature applies is not determined based on the second and third quantities. In some embodiments, for the default RACH resource, the starting index of the preamble can be 0, and the number of preambles applicable to a feature in a RO can be additionally configured through another parameter. In some embodiments, for the RACH resource corresponding to the parameter FeatureCombination, both the starting index of the preamble and the number of preambles applicable to a feature in a RO can be configured.
[0197] In some embodiments, the second information may indicate an increase or decrease in random access resources. In some embodiments, the second information may indicate an increase or decrease based on the first random access resources. Here, the increased or decreased random access resources may be referred to as the second random access resources.
[0198] In some embodiments, the second information may indicate the addition of random access resources. In one example, the second information may indicate that one or more random access resources are available. This means that the random access resource, or these random access resources, can be used to map to an SSB. In some cases, the available random access resource indicated by the second information may also be considered a valid random access resource.
[0199] In some embodiments, the second information may indicate a reduction in random access resources. In one example, the second information may indicate that one or more random access resources are unavailable. This means that the random access resource or these random access resources cannot be used to map to an SSB. In some cases, the unavailable random access resource indicated by the second information may also be considered an invalid random access resource.
[0200] In some embodiments, the second random access resource may include at least one of the following: an unavailable RO in the first random access resource, an unavailable preamble in the first random access resource, an available RO outside the first random access resource, and an available preamble outside the first random access resource.
[0201] In some embodiments, where the second information indicates a reduction in random access resources, the second random access resources may include one or more ROs. These ROs may be a subset of the ROs in the first random access resources. For example, the second information may indicate that a subset of one or more ROs in the first random access resources in the RACH configuration is unavailable.
[0202] In some embodiments, the second information may include an index of ROs. For example, if the second information indicates a reduction in random access resources, the second information may include an index of ROs in the first random access resources to indicate unavailable ROs based on the index of ROs.
[0203] In some embodiments, where the second information indicates a reduction in random access resources, the second random access resources may include one or more preambles. These preambles may be a subset of the preambles in the first random access resources. For example, if the preambles to be subtracted indicated by the second information may include preambles in one or more ROs in the RACH configuration, then the second information may indicate that these preambles are unavailable.
[0204] In some embodiments, the second information may include an index of the RO and / or an index of a preamble in the RO. For example, if the second information indicates a reduction in random access resources, the second information may include an index of the RO in the first random access resource and an index of the preamble in that RO, to indicate an unavailable preamble based on the index of the RO and the index of the preamble.
[0205] In some embodiments, where the second information indicates the addition of random access resources, the second random access resources may include one or more ROs. These ROs may be one or more ROs other than the first random access resources. For example, the second information may indicate that ROs other than one or more ROs in the RACH configuration are available during the first period.
[0206] In some embodiments, the second information may include the index and offset of the RO in the first random access resource, and the number of ROs in the second random access resource. For example, if the second information indicates an increase in random access resources, the second information may include the index and offset of the RO in the first random access resource, and the number of ROs in the second random access resource, to indicate the increased available RO.
[0207] In some embodiments, the offset may be the offset of the second random access resource relative to the first random access resource. In some embodiments, the second random access resource may include one or more ROs. In this case, the offset may include the offset of each RO in the second random access resource relative to one RO in the first random access resource.
[0208] In some embodiments, where the second information indicates the addition of random access resources, the second random access resource may include one or more preambles. These preambles may be one or more preambles other than the first random access resource. For example, the second information may indicate that preambles other than one or more ROs (and their included preambles) in the RACH configuration are available during the first period.
[0209] In some embodiments, the second information may include an index of the RO in the first random access resource and an index of the preamble. For example, if the second information indicates the addition of a random access resource, the second information may include an index of the RO in the first random access resource and an index of the preamble to indicate the preamble available in that RO.
[0210] In some embodiments, the second information may include a field that indicates an increase or decrease in random access resources through different values. For example, the field may have a first value to indicate an increase in random access resources. For example, the field may have a second value to indicate a decrease in random access resources. For example, the first value is 1 and the second value is 0. For example, the first value is 0 and the second value is 1.
[0211] It should be noted that the second information may also include other content, or the above content in the second information may also be indicated in other ways, and this disclosure does not specifically limit this.
[0212] In some embodiments, the first information may be configured at a higher level.
[0213] In some embodiments, the first information may be dynamically indicated.
[0214] In some embodiments, the first information may be carried in one or more signaling such as radio resource control (RRC), downlink control information (DCI), media access control (MAC) control element (CE), system information block 1 (SIB1).
[0215] In some embodiments, step S501 can be omitted, in which case the aforementioned first information can be pre-configured. In one example, the first information can be agreed upon by a protocol.
[0216] It should be noted that all RO involved in the embodiments disclosed herein are effective RO.
[0217] In some embodiments, whether an RO is a valid RO can be determined based on at least one of the following conditions 1 to 9. In one example, an RO may be a valid RO if it satisfies at least one of conditions 1 to 9.
[0218] In some embodiments, condition 1 is: RO is in a UL symbol. In one example, the UL symbol is a symbol configured as UL by the parameter TDD-UL-DL-ConfigCommon and not configured as an SBFD symbol.
[0219] In some embodiments, condition 2 is: in a PRACH time slot, RO is not before SSB.
[0220] In some embodiments, condition 3 is: there is at least a Ngap symbol gap between the symbol containing the previous SSB and the RO. Here, Ngap is a positive integer.
[0221] In some embodiments, condition 4 is: in the time domain, RO does not overlap with SSB on non-SBFD symbols.
[0222] In some embodiments, condition 5 is: there is at least an Ngap symbol interval between the RO and the previous DL symbol. In one example, the DL symbol is a symbol configured as DL by the parameter TDD-UL-DL-ConfigCommon and not configured as an SBFD symbol.
[0223] In some embodiments, condition 6 is: RO does not overlap with frequency ranges outside the UL subcarrier on the SBFD symbol.
[0224] In some embodiments, condition 7 is: the RO does not simultaneously contain SBFD symbols and non-SBFD symbols. In one example, a valid RO cannot span between SBFD symbols and non-SBFD symbols.
[0225] In some embodiments, condition 8 is: the RO is on an SBFD symbol. In one example, a valid RO can only be on an SBFD symbol.
[0226] In some embodiments, condition 9 is: the RO is on a non-SBFD symbol. In one example, a valid RO can only be on a non-SBFD symbol.
[0227] In some embodiments, the cell-level symbol format is configured such that whether an RO located on an SBFD symbol is a valid RO can be determined based on at least one of the following conditions 1 to 4: In one example, an RO located on an SBFD symbol can be a valid RO if it satisfies at least one of conditions 1 to 4. In another example, a valid RO located on an SBFD symbol can satisfy conditions 1 to 4 simultaneously.
[0228] In some embodiments, condition 1 is: there is at least an Ngap symbol gap between the RO and the symbol where the previous SSB is located.
[0229] In some embodiments, condition 2 is: there is at least an Ngap symbol interval between the RO and the previous DL symbol (non-SBFD symbol). In one example, the DL symbol is a symbol configured as DL by the parameter TDD-UL-DL-ConfigCommon and not configured as an SBFD symbol.
[0230] In some embodiments, condition 3 is: RO does not overlap with frequency ranges outside the UL subcarrier on the SBFD symbol.
[0231] In some embodiments, condition 4 is: the symbols where RO and SSB are located do not overlap.
[0232] In some embodiments, the cell-level symbol format is configured such that whether an RO located on a non-SBFD symbol is a valid RO can be determined according to the following condition 1 or condition 2: In one example, when an RO located on a non-SBFD symbol satisfies condition 1 or condition 2, the RO can be a valid RO.
[0233] In some embodiments, condition 1 is: RO is in a UL symbol. In one example, the UL symbol is a symbol configured as UL by the parameter TDD-UL-DL-ConfigCommon and not configured as an SBFD symbol.
[0234] In some embodiments, condition 2 is: in a PRACH time slot, RO is not before SSB, there is at least a Ngap symbol interval between RO and the symbol where the previous SSB is located, and there is at least a Ngap symbol interval between RO and the previous DL symbol (non-SBFD symbol).
[0235] In some embodiments, the cell-level symbol format is not configured, and whether an RO located on a non-SBFD symbol is a valid RO can be determined according to the following condition 1: In one example, when an RO located on a non-SBFD symbol satisfies condition 1, the RO can be a valid RO.
[0236] In some embodiments, condition 1 is: in a PRACH slot, RO is not before SSB, and RO is at least Ngap symbols away from the symbol containing the previous SSB.
[0237] In step S502, terminal 101 determines the mapping relationship.
[0238] In some embodiments, terminal 101 can determine the mapping relationship between SSB and RO based on first information. In some embodiments, terminal 101 can determine the mapping relationship between multiple SSBs and multiple ROs within a first cycle based on RACH configuration and second information.
[0239] In some embodiments, terminal 101 may employ a first approach in determining the mapping relationship between multiple SSBs and multiple ROs. In some embodiments, the first approach provides a mapping order for mapping SSBs to ROs.
[0240] In some embodiments, the first approach may include: mapping in ascending order according to the preamble index within a single RO; mapping in ascending order according to the frequency resource index for frequency division multiplexing ROs; mapping in ascending order according to the time domain resource index for time division multiplexing ROs within a physical random access channel (PRACH) slot; and mapping in ascending order according to the index for PRACH slots.
[0241] In some embodiments, the first period may include at least one of the following: a RACH configuration period, an association period, an association pattern period, and a preset period. In some embodiments, the preset period may be configured by a higher layer or obtained based on local configuration. For example, the preset period may be provided to the terminal 101 by the network device 102 via an RRC message. For example, the length of the first period may be 160 milliseconds, depending on the higher layer configuration or protocol agreement.
[0242] In some embodiments, the RACH configuration may include only a first number of preambles associated with each SSB. This type of RACH configuration may be referred to as the first configuration method. In some embodiments, the RACH configuration may include a second number of SSBs associated with each RO, and a third number of preambles associated with each SSB in a RO. This type of RACH configuration may be referred to as the second configuration method.
[0243] In some embodiments, residual preambles may exist in one or more ROs. It is understood that when multiple preambles in an RO are mapped to one or more SSBs, the number of preambles required to map the first SSB (i.e., the next SSB to be mapped) may be greater than the number of preambles in that RO that have not yet been mapped to SSBs. In this case, the preambles of these unmapped SSBs can be referred to as residual preambles.
[0244] In some embodiments, the first number of preambles associated with multiple SSBs can be different, resulting in a non-uniform mapping between the multiple SSBs and multiple ROs. Different SSBs may be associated with different numbers of preambles, meaning that after a preamble in an RO maps to one or more SSBs, the remaining preamble is insufficient to map to the next SSB. In some embodiments, the first number of preambles associated with multiple SSBs can be the same, resulting in a uniform mapping between the multiple SSBs and multiple ROs. The number of preambles associated with each SSB may exceed the number of remaining preambles in an RO, meaning that the remaining preambles in an RO (which can be understood as remaining preambles) are insufficient to map to an SSB.
[0245] In some embodiments, for the first configuration, the remaining preamble in one of the plurality of ROs is to be mapped to the first SSB in the plurality of SSBs, and the number of the remaining preamble in that RO is less than the first number associated with the first SSB, and the remaining preamble is used to map to the first SSB.
[0246] In some embodiments, terminal 101 can determine the mapping relationship between multiple SSBs and multiple ROs within a first period. After completing one or more cyclic mappings for multiple SSBs in the ROs within the first period, if the remaining ROs and / or remaining preambles in the first period are insufficient to complete one cyclic mapping of multiple SSBs, then the remaining ROs and / or remaining preambles are not used. In some embodiments, for a first configuration, if the number of remaining ROs and / or the number of remaining preambles in the multiple ROs within the first period is less than the sum of the first number associated with the multiple SSBs, then the remaining ROs and / or remaining preambles are not used.
[0247] In some embodiments, terminal 101 can determine the mapping relationship between multiple SSBs and multiple ROs within a first period. After completing one or more cyclic mappings for multiple SSBs in the ROs within the first period, if the remaining ROs and / or remaining preambles in the first period are insufficient to complete one cyclic mapping of multiple SSBs, then some or all of the remaining ROs and / or remaining preambles are used. In some embodiments, for a first configuration, if the number of remaining ROs and / or the number of remaining preambles in the multiple ROs within the first period is less than the sum of the first number associated with the multiple SSBs, at least a portion of the remaining ROs and / or remaining preambles are used to map to the multiple SSBs.
[0248] In some embodiments, the remaining RO and / or remaining preamble that are insufficient to complete one cycle mapping of multiple SSBs within the first period can be referred to as the first remaining RO / preamble. After the first remaining RO / preamble maps k (k is an integer greater than or equal to 0) SSBs, the final remaining RO and / or preamble (also referred to as the second remaining RO / preamble) is insufficient to map to a single SSB (e.g., SSB#i). In one example, the second remaining RO / preamble can be empty, meaning that the second remaining RO / preamble may not exist in the first remaining RO / preamble. In one example, the RO and / or preamble mapped to k SSBs can be referred to as the third remaining RO / preamble.
[0249] In some embodiments, the first remaining RO / preamble can be used in its entirety.
[0250] In some embodiments, the second remaining RO / preamble in the first remaining RO / preamble is not used, and the third RO / preamble in the first remaining RO / preamble is used.
[0251] Figure 6A is a schematic diagram of the mapping relationship between SSBs and ROs according to an embodiment of the present disclosure. As shown in Figure 6A, the five SSBs are SSB#0, SSB#1, SSB#2, SSB#3, and SSB#4, and each SSB is associated with 16 preambles. The first period includes RO#1, RO#2, and RO#3. One RO contains 32 preambles. In the first period, SSB#0 and SSB#1 are mapped to RO#1, SSB#2 and SSB#3 are mapped to RO#2, and SSB#4 is mapped to RO#3. The remaining preambles in the first period (i.e., the first remaining preambles) include the 16th to 31st preambles in RO#3. In one example, the 16th to 31st preambles in RO#3 may not be used. In one example, the 16th to 31st preambles in RO#3 may be used and mapped to, for example, SSB#0.
[0252] In some embodiments, the first period can be an association period. Within the association period, the mapping relationship between multiple SSBs and multiple ROs can be determined using the implementation shown in Figure 6A. In some embodiments, within the first period, the number of cyclic mappings between the multiple SSBs and multiple ROs can be greater than or equal to 1.
[0253] In some embodiments, the first period may be an associated pattern period. An associated pattern period may include one or more associated periods. When one or more cyclic mappings are completed within an associated pattern period, the remaining ROs and / or remaining preambles within the associated pattern period may be insufficient to complete one cyclic mapping. For the remaining ROs and / or remaining preambles within the associated pattern period, mapping processing can be performed in a manner similar to that described above for the first remaining RO / preamble.
[0254] In some embodiments, the first cycle may be configured at a higher level or agreed upon by the protocol. If one or more cyclic mappings are completed within the first cycle, the remaining ROs and / or remaining preambles within the first cycle may be insufficient to complete one cyclic mapping. For the remaining ROs and / or remaining preambles within the first cycle, mapping processing can be performed in a manner similar to that described above for the first remaining RO / preamble.
[0255] In some embodiments, the second number of SSBs associated with each RO can be different, and / or the third number of preambles associated with each SSB in a RO can be different, in which case the mapping between the multiple SSBs and the multiple ROs is non-uniform. In some embodiments, the second number of SSBs associated with each RO can be the same, and the third number of preambles associated with each SSB in a RO can be the same, in which case the mapping between the multiple SSBs and the multiple ROs is uniform.
[0256] In some embodiments, the second number of SSBs associated with each RO may be less than or equal to 1. In one example, the second number of multiple SSBs associated is the same, and the third number of multiple SSBs associated is the same. In one example, the second number of multiple SSBs associated is the same, and the third number of at least two of the multiple SSBs associated is different. In one example, the second number of at least two of the multiple SSBs associated is different, and the third number of multiple SSBs associated is the same. In one example, the second number of at least two of the multiple SSBs associated is different, and the third number of at least two of the multiple SSBs associated is different.
[0257] In some embodiments, where the second number of associations among multiple SSBs is less than or equal to 1, an SSB can be associated with 1 / N consecutive ROs. In other words, an SSB can be associated with at least one RO.
[0258] In some embodiments, where the second number of associations among multiple SSBs is less than or equal to 1, the third number of associations among at least two of the multiple SSBs may be different. This may result in some preambles in the RO being unused, reducing the utilization rate of preambles in the RO. For example, the RO may include 32 preambles, and the third number of associations among one or more SSBs may be equal to 16. In this case, each of these SSBs maps 16 preambles in one RO, and the remaining number of preambles is equal to 16 and unused.
[0259] In some embodiments, the second number of SSBs associated with each RO can be greater than 1. In one example, the second number of multiple SSBs associated is the same, and the third number of multiple SSBs associated is the same. In one example, the second number of multiple SSBs associated is the same, and the third number of at least two of the multiple SSBs associated is different. In one example, the second number of at least two of the multiple SSBs associated is different, and the third number of multiple SSBs associated is the same. In one example, the second number of at least two of the multiple SSBs associated is different, and the third number of at least two of the multiple SSBs associated is different.
[0260] In some embodiments, when the second number of associations of multiple SSBs is greater than 1, an SSB can be associated with 1 / N consecutive ROs. In other words, an SSB can be associated with one RO.
[0261] In some embodiments, among a plurality of SSBs, at least one SSB may be associated with a second quantity less than or equal to 1, and at least one SSB may be associated with a second quantity greater than 1. In one example, at least one SSB may be associated with a second quantity less than or equal to 1, at least one SSB may be associated with a second quantity greater than 1, and at least two SSBs may be associated with the same third quantity. In another example, at least one SSB may be associated with a second quantity less than or equal to 1, at least one SSB may be associated with a second quantity greater than 1, and at least two SSBs may be associated with different third quantities.
[0262] In some embodiments, for an SSB with a second number of associations less than or equal to 1, the SSB may be associated with 1 / N consecutive ROs. In other words, an SSB may be associated with at least one RO. In some embodiments, for an SSB with a second number of associations greater than 1, an SSB may be associated with 1 / N consecutive ROs. In other words, an SSB may be associated with one RO.
[0263] In some embodiments, terminal 101 can determine the mapping relationship between multiple SSBs and multiple ROs within a first period. After completing one or more cyclic mappings for multiple SSBs in the ROs within the first period, if the first remaining RO / preamble in the first period is insufficient to complete one cyclic mapping of multiple SSBs, then the first remaining RO / preamble may be not used, partially used, or fully used. In some embodiments, for the second configuration, within the first period, if the number of remaining ROs and / or remaining preambles in the multiple ROs is less than the sum of the preambles associated with the multiple SSBs, at least a portion of the remaining ROs and / or remaining preambles are used to map to one or more SSBs among the multiple SSBs, or are not used to map to the multiple SSBs.
[0264] In some embodiments, the SSB to be mapped by the first remaining RO / preamble can be determined in a first manner as follows: After the first remaining RO / preamble maps k (k is an integer greater than or equal to 0) of the multiple SSBs, the remaining RO and / or preamble can be referred to as the second remaining RO / preamble. The second remaining RO / preamble is insufficient to map to an SSB (e.g., SSB#i). The second remaining RO / preamble may include the second remaining RO and / or the second remaining preamble. The RO / preamble remaining after removing the second remaining RO / preamble from the first remaining RO / preamble can be referred to as the third remaining RO / preamble. The third remaining RO / preamble may include the third remaining RO and / or the third remaining preamble.
[0265] In some embodiments, both the second and third remaining RO / preambles in the first remaining RO / preamble are used. In this case, the entire first remaining RO / preamble is used.
[0266] In some embodiments, the third remaining RO / preamble in the first remaining RO / preamble is used, and the second remaining RO / preamble in the first remaining RO / preamble is not used. In this case, the first remaining RO / preamble is partially used.
[0267] In some embodiments, the first remaining RO / preamble is not used. In some embodiments, neither the second remaining RO / preamble nor the third remaining RO / preamble in the first remaining RO / preamble is used. In this case, the first remaining RO / preamble is not used.
[0268] Figure 6B is a schematic diagram of the mapping relationship between SSBs and ROs provided according to an embodiment of the present disclosure. As shown in Figure 6B, the four SSBs are SSB#0, SSB#1, SSB#2, and SSB#3. The second quantity associated with SSB#0, SSB#1, SSB#2, and SSB#3 is 1 / 2 each. In the first period, there are four ROs in the frequency domain and three ROs in the time domain. These 12 ROs are RO#0, RO#1, RO#2, RO#3, RO#4, RO#5, RO#6, RO#7, RO#8, RO#9, RO#10, and RO#11. One RO includes 32 preambles. According to the first method, SSB#0 is mapped to RO#0 and RO#1, SSB#1 is mapped to RO#2 and RO#3, SSB#2 is mapped to RO#4 and RO#5, and SSB#3 is mapped to RO#6 and RO#7. The remaining ROs in the first cycle can include RO#8, RO#9, RO#10, and RO#11, and these remaining ROs, along with their preambles, can be used. Therefore, SSB#0 maps to RO#8 and RO#9, and SSB#1 maps to RO#10 and RO#11.
[0269] In some embodiments, when at least one SSB is associated with a second number less than or equal to 1 and at least one SSB is associated with a second number greater than 1, terminal 101 may first map the SSBs associated with a second number greater than 1, and then map the SSBs associated with a second number less than or equal to 1. In some embodiments, when at least one SSB is associated with a second number less than or equal to 1 and at least one SSB is associated with a second number greater than 1, terminal 101 may first map the SSBs associated with a second number less than or equal to 1, and then map the SSBs associated with a second number greater than 1. In some embodiments, one or more SSBs with an associated second number greater than 1 may be mapped to the same RO.
[0270] In some embodiments, terminal 101 may not expect the second number of multiple SSB associations to all be greater than 1, and the second number of multiple SSB associations to be different. In one example, terminal 101 may expect the second number of multiple SSB associations to be different, and at least some of the second number of SSB associations to be less than or equal to 1. In one example, terminal 101 may expect the second number of multiple SSB associations to all be greater than 1, and the second number of multiple second SSB associations to be the same.
[0271] In some embodiments, terminal 101 may not expect a portion of the SSBs to have a second number of associations greater than 1, and another portion of the SSBs to have a second number of associations less than or equal to 1. In one example, terminal 101 may expect the second number of associations of the multiple SSBs to be greater than 1, or the second number of associations of the multiple SSBs to be less than or equal to 1.
[0272] In some embodiments, terminal 101 may not expect the second number associated with any of the plurality of SSBs to be greater than 1. In one example, terminal 101 may expect the second number associated with all of the plurality of SSBs to be less than or equal to 1.
[0273] In some embodiments, the first period may be an associated period. In some embodiments, the number of cyclic mappings between multiple SSBs and multiple ROs within the first period may be greater than or equal to 1.
[0274] In some embodiments, the first period may be an association period. Within the association period, the remaining RO and / or remaining preamble may be insufficient to complete one cycle mapping. For the remaining RO and / or remaining preamble within the association period, mapping processing can be performed in a manner similar to that described above for the first remaining RO / preamble.
[0275] In some embodiments, the first period may be an associated pattern period. An associated pattern period may include one or more associated periods. When one or more cyclic mappings are completed within an associated pattern period, the remaining ROs and / or remaining preambles within the associated pattern period may be insufficient to complete one cyclic mapping. For the remaining ROs and / or remaining preambles within the associated pattern period, mapping processing can be performed in a manner similar to that described above for the first remaining RO / preamble.
[0276] In some embodiments, if the remaining ROs and / or remaining preambles in the associated pattern cycle are insufficient to complete one cycle mapping, the remaining ROs and / or remaining preambles may be used. In some embodiments, if the remaining ROs and / or remaining preambles in the associated pattern cycle are insufficient to complete one cycle mapping, the ROs and / or remaining preambles capable of mapping a complete SSB are used, while the other remaining ROs and / or remaining preambles are not used. In some embodiments, if the remaining ROs and / or remaining preambles in the associated pattern cycle are insufficient to complete one cycle mapping, the remaining ROs and / or remaining preambles may not be used.
[0277] In some embodiments, the first cycle may be configured at a higher level or agreed upon by the protocol. If one or more cyclic mappings are completed within the first cycle, the remaining ROs and / or remaining preambles within the first cycle may be insufficient to complete one cyclic mapping. For the remaining ROs and / or remaining preambles within the first cycle, mapping processing can be performed in a manner similar to that described above for the first remaining RO / preamble.
[0278] In some embodiments, for the second configuration method, step S502 may include: determining a first quantity based on a second quantity and a third quantity; and determining the mapping relationship between multiple SSBs and multiple ROs within a first period based on the first quantity. In some embodiments, this method is applicable when at least one of the multiple SSBs is associated with a second quantity greater than 1, and at least two of the multiple SSBs are associated with different second quantities.
[0279] It should be noted that the method for determining the mapping relationship between multiple SSBs and multiple ROs in the first period based on the first quantity has been explained above and will not be repeated here.
[0280] In some embodiments, step S502 may include: determining a third random access resource based on first information; and determining a mapping relationship between a plurality of SSBs and the third random access resource.
[0281] In some embodiments, the third random access resource may be determined by terminal 101 based on RACH configuration and the second information. In one example, if the second information indicates an increase in random access resources, the third random access resource may include the first random access resource and the second random access resource. In other words, the third random access resource may be the sum of the first and second random access resources. In one example, if the second information indicates a decrease in random access resources, the third random access resource may include other random access resources in the first random access resource besides the second random access resource. In other words, the third random access resource may be the portion of the first random access resource after removing the second random access resource.
[0282] In some embodiments, the operation of terminal 101 determining the third random access resource can be implemented as follows: terminal 101 determines the first random access resource according to RACH; determines the second random access resource according to second information; and determines the third random access resource based on the first random access resource and the second random access resource.
[0283] In some embodiments, the second information may indicate a reduction in random access resources.
[0284] In some embodiments, the first random access resource may include a RO and / or a preamble. In some embodiments, the second random access resource may include a RO and / or a preamble.
[0285] In some embodiments, the second information may indicate that one or more preambles in the first random access resource are unavailable. In one example, the second information may include an index of a RO in the first random access resource and an index of a preamble to indicate that a preamble in that RO is unavailable.
[0286] Figure 7A is a schematic diagram of the mapping relationship between SSBs and ROs provided according to an embodiment of the present disclosure. As shown in Figure 7A, the five SSBs are SSB#0, SSB#1, SSB#2, SSB#3, and SSB#4, and each SSB is associated with 16 preambles. In the first period, the ROs configured by RACH include RO#1, RO#2, and RO#3. One RO contains 32 preambles. In the first period, SSB#0 and SSB#1 are mapped to RO#1, SSB#2 and SSB#3 are mapped to RO#2, and SSB#4 is mapped to RO#3. The remaining preambles in the first period include the 16th to 31st preambles in RO#3, i.e., preambles #16 to #31.
[0287] The second information indicates that preambles #16 to #31 in RO#3 are unavailable. In this case, the third random access resource includes preambles #0 to #15 in RO#1, RO#2, and RO#3. During the first cycle, SSB#0, SSB#1, SSB#2, SSB#3, and SSB#4 complete one cyclic mapping with RO#1, RO#2, and RO#3, and there are no remaining preambles.
[0288] In some embodiments, the second information may indicate that one or more ROs in the first random access resource are unavailable. In one example, the second information may include indexes of one or more ROs in the first random access resource to indicate that these ROs are unavailable.
[0289] Figure 7B is a schematic diagram of the mapping relationship between SSBs and ROs provided according to an embodiment of the present disclosure. As shown in Figure 7B, the four SSBs are SSB#0, SSB#1, SSB#2, and SSB#3. The second number associated with SSB#0, SSB#1, SSB#2, and SSB#3 is 1 / 2 each. In the first period, according to the RACH configuration, there are four ROs in the frequency domain and three ROs in the time domain. These 12 ROs are RO#0, RO#1, RO#2, RO#3, RO#4, RO#5, RO#6, RO#7, RO#8, RO#9, RO#10, and RO#11. One RO includes 32 preambles. According to the first method, SSB#0 is mapped to RO#0 and RO#1, SSB#1 is mapped to RO#2 and RO#3, SSB#2 is mapped to RO#4 and RO#5, and SSB#3 is mapped to RO#6 and RO#7. The remaining ROs in the first cycle can include RO#8, RO#9, RO#10, and RO#11, and these remaining ROs, along with their preambles, can be used.
[0290] The second information indicates that RO#8, RO#9, RO#10, and RO#11 are unavailable. In this case, the third random access resource includes RO#0, RO#1, RO#2, RO#3, RO#4, RO#5, RO#6, and RO#7. Within the first cycle, a cyclic mapping is completed between SSB#0, SSB#1, SSB#2, SSB#3, and SSB#4 and RO#0, RO#1, RO#2, RO#3, RO#4, RO#5, RO#6, and RO#7, and there are no remaining ROs.
[0291] In some embodiments, the second information may indicate the addition of random access resources.
[0292] In some embodiments, the first random access resource may include a RO and / or a preamble. In some embodiments, the second random access resource may include a RO and / or a preamble.
[0293] In some embodiments, the second information may indicate that one or more ROs other than the preamble in the first random access resource are available.
[0294] In some embodiments, the second information may indicate the addition of ROs. For example, the second information may indicate that one or more ROs are added within the first cycle, based on the ROs indicated by the RACH configuration.
[0295] Figure 7C is a schematic diagram of the mapping relationship between SSBs and ROs provided according to an embodiment of the present disclosure. As shown in Figure 7C, the five SSBs are SSB#0, SSB#1, SSB#2, SSB#3, and SSB#4. Each SSB is associated with a second quantity of 2 and a third quantity of 16; in other words, each SSB is associated with 16 preambles. The first period includes RO#1, RO#2, and RO#3. One RO contains 32 preambles. The value of the parameter msg1-FDM is 1, that is, one RO is allocated at the same time domain position. In the first period, SSB#0 and SSB#1 are mapped to RO#1, SSB#2 and SSB#3 are mapped to RO#2, and SSB#4 is mapped to RO#3. The remaining preambles in the first period (i.e., the first remaining preambles) include the 16th to 31st preambles in RO#3, and these remaining preambles can be used.
[0296] The second information indicates the addition of two ROs. For example, the second information may include at least one of the following: the index of RO#0, the offset of the added RO relative to RO#0, and the number of added ROs (i.e., 2). For example, if the added ROs can be determined by default based on RO#0, then the second information may only include the offset of the added RO relative to RO#0 and / or the number of added ROs. Based on the second information, two ROs, namely RO#4 and RO#5, can be added in the first period. In this case, the third random access resource includes RO#0 to RO#5. In the first period, SSB#0, SSB#1, SSB#2, SSB#3, SSB#4 and RO#0 to RO#5 undergo two cyclic mappings, and there are no remaining ROs.
[0297] In some embodiments, the second information may indicate an increase in RO. For example, the second information may indicate an increase in the FDM's RO based on the RO indicated by the RACH configuration during the first cycle.
[0298] Figure 7D is a schematic diagram of the mapping relationship between SSBs and ROs provided according to an embodiment of the present disclosure. As shown in Figure 7D, the four SSBs are SSB#0, SSB#1, SSB#2, and SSB#3. The second quantity associated with SSB#0, SSB#1, SSB#2, and SSB#3 is 1 / 2. The value of parameter msg1-FDM is 4, that is, four ROs are allocated in the same time domain position. In the first period, according to the RACH configuration, there are four ROs in the frequency domain and three ROs in the time domain. These 12 ROs are RO#0, RO#1, RO#2, RO#3, RO#4, RO#5, RO#6, RO#7, RO#8, RO#9, RO#10, and RO#11. One RO includes 32 preambles. According to the first method, SSB#0 is mapped to RO#0 and RO#1, SSB#1 is mapped to RO#2 and RO#3, SSB#2 is mapped to RO#4 and RO#5, and SSB#3 is mapped to RO#6 and RO#7. The remaining ROs in the first cycle may include RO#8, RO#9, RO#10, and RO#11, and these remaining ROs, along with their preambles, can be used.
[0299] The second information indicates the addition of 4 FDM ROs. Based on the second information, 4 ROs can be added within the first period, namely RO#12 to RO#15. In this case, the third random access resources include RO#0 to RO#15. Within the first period, SSB#0, SSB#1, SSB#2, SSB#3, and SSB#4 are cyclically mapped twice with RO#0 to RO#15, and there are no remaining ROs.
[0300] In some embodiments, terminal 101 may perform at least one of the following: adjusting the SSB pattern, configuring the TDD time slot structure, configuring the RO time-frequency location, and configuring the mapping criteria between SSB and RO. Through these operations, there may be an integer multiple cyclic mapping between SSB and RO within the first cycle, and there are no remaining random access resources.
[0301] In some embodiments, terminal 101 may not expect the existence of remaining random access resources in the first cycle. For example, terminal 101 may not expect the existence of remaining RO and / or remaining preamble in the first cycle.
[0302] In some embodiments, the first period may be an association period. In this case, when terminal 101 performs one or more operations such as adjusting the SSB pattern, configuring the TDD time slot structure, configuring the RO time-frequency location, and configuring the mapping criteria between SSB and RO, there are no remaining random access resources outside the association pattern period in which the association period is located, which is an integer multiple of the association period. The mapping between SSB and RO within the first period may be repeated once or multiple times within the association pattern period.
[0303] In some embodiments, terminal 101 may not expect the presence of remaining random access resources during the associated pattern period. For example, terminal 101 may not expect the presence of remaining ROs and / or remaining preambles during the associated pattern period.
[0304] In some embodiments, the first cycle can be repeated once or multiple times, and the mapping relationship between SSB and RO within the first cycle can be repeated once or multiple times.
[0305] In some embodiments, the RACH resources indicated by the RACH configuration may include ROs in SBFD symbols and ROs in non-SBFD symbols. In some embodiments, the determination of the mapping relationship between SSBs and ROs may be performed separately for ROs in SBFD symbols and ROs in non-SBFD symbols. In some embodiments, the determination of the mapping relationship between SSBs and ROs may be performed jointly for ROs in SBFD symbols and ROs in non-SBFD symbols.
[0306] Referring to Figure 3C, the mapping relationship between SSBs and ROs is determined jointly for ROs in SBFD symbols and ROs in non-SBFD symbols. The first period is the association period, and the first remaining RO / preamble within the association period is insufficient to complete one cycle mapping of multiple SSBs. The association pattern period consists of 3 association periods. The duration of the first association period is 10 milliseconds. The duration of the second association period is 80 milliseconds. The duration of the third association period is 40 milliseconds. The remaining ROs and / or remaining preambles after completing multiple cycle mappings within the association pattern period are insufficient to complete one cycle mapping. The remaining ROs and / or remaining preambles within an association period are not used.
[0307] In some embodiments, the mapping between RO and SSB in SBFD and non-SBFD symbols described above can be applied to PRACH repetition. Within each associated pattern cycle of the time period, the mapping relationship between SSB and RO can be determined using, for example, the implementation shown in Figure 8.
[0308] In some embodiments, the RACH resources in the RACH configuration may include ROs in SBFD symbols and ROs in non-SBFD symbols. In one example, for ROs in SBFD symbols, terminal 101 determines the mapping relationship between SSBs and ROs. In another example, for ROs in non-SBFD symbols, terminal 101 determines the mapping relationship between SSBs and ROs.
[0309] In some embodiments, for the set of ROs consisting of ROs in SBFD symbols and ROs in non-SBFD symbols, terminal 101 determines the mapping relationship between SSB and ROs in the RO set.
[0310] In some embodiments, the number of repetitions in a PRACH repetition can be N0, where N0 is a positive integer. In some embodiments, of the N0 repetitions, one or more repetitions are in SBFD symbols, and / or one or more repetitions are in non-SBFD symbols. In one example, repetitions in SBFD symbols and repetitions in non-SBFD symbols may have the same or different power control parameters. For example, repetitions in SBFD symbols and repetitions in non-SBFD symbols may have the same or different transmission power. In one example, the frequency domain location of the repetition in SBFD symbols and the frequency domain location of the repetition in non-SBFD symbols may be different. In one example, repetitions in SBFD symbols and repetitions in non-SBFD symbols correspond to the same FDM index in the frequency domain. For example, repetitions in SBFD symbols and repetitions in non-SBFD symbols may both be located at the same RO in the FDM in the frequency domain.
[0311] Referring again to Figure 4, of the eight ROs, RO#0 to RO#5 are located in SBFD symbols, while RO#6 and RO#7 are located in non-SBFD symbols. RO#0, RO#2, RO#4, and RO#6 are mapped to SSB#0, representing four repetitions of SSB#0. RO#1, RO#3, RO#5, and RO#7 are mapped to SSB#1, representing four repetitions of SSB#1. RO#0 to RO#5 in SBFD symbols and RO#6 and RO#7 in non-SBFD symbols can use different transmission powers. Furthermore, RO#0, RO#2, RO#4, and RO#6 are located in different frequency domains, but RO#0, RO#2, RO#4, and RO#6 all correspond to the first RO in FDM.
[0312] The communication method of this embodiment can be implemented through steps S501 to S502.
[0313] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0314] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0315] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".
[0316] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.
[0317] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".
[0318] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.
[0319] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.
[0320] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”
[0321] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.
[0322] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.
[0323] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.
[0324] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.
[0325] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transmit,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0326] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0327] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0328] In some embodiments, the terms "frequency point", "frequency", "bandwith", and "band" can be used interchangeably.
[0329] Figure 8 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 8, the method includes step S801.
[0330] In step S801, network device 102 sends first information to terminal 101.
[0331] The optional implementation of step S801 can be found in the optional implementation of step S501 in Figure 5, as well as other related parts in the embodiments involved in Figure 5, which will not be repeated here.
[0332] In some embodiments, the first information includes RACH configuration and second information.
[0333] In some embodiments, RACH configuration is used to determine a first random access resource;
[0334] In some embodiments, the RACH configuration includes: a first number of preambles associated with each SSB.
[0335] In some embodiments, the RACH configuration includes: a second number of SSBs associated with each RO, and a third number of preambles associated with each SSB in a RO.
[0336] In some embodiments, in a RACH configuration, the mapping between multiple SSBs and multiple ROs is uniform or non-uniform.
[0337] In some embodiments, the second information indicates whether to increase or decrease the second random access resource based on the first random access resource.
[0338] In some embodiments, the second information may be determined by a higher layer.
[0339] In some embodiments, the second information may be agreed upon in a protocol.
[0340] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0341] In the following, the technical solutions of the embodiments of this disclosure will be described by way of specific implementation.
[0342] In some embodiments, in RACH resource configuration and SSB-RO mapping:
[0343] In some embodiments, Scheme 1: The RACH resource is configured with the number of preambles associated with an SSB, but not with the number of ROs associated with an SSB.
[0344] In some embodiments, different SSBs are associated with the same number of preambles. In one example, the remaining ROs and preambles after the circular mapping are not used. In another example, the remaining ROs and preambles after the circular mapping are partially used. In yet another example, all the remaining ROs and preambles after the circular mapping are used. It should be noted that when the remaining ROs and preambles after the circular mapping are not used, the ROs and preambles can complete an integer number of circular mappings of the SSBs, reducing the complexity of the mapping relationship and thus reducing system complexity. Furthermore, when the remaining ROs and preambles after the circular mapping are partially or fully used, the utilization rate of the ROs and preambles can be improved, thus increasing system efficiency.
[0345] In some embodiments, scheme 1-1: within the first period, the SSB is associated with the RO in a first order, which is: the preamble in an RO is arranged in ascending order; the ROs in the frequency domain FDM are arranged in ascending order according to the frequency domain index; the ROs in a PRACH slot are arranged in ascending order according to the time domain index; and the PRACH slot index is arranged in ascending order.
[0346] In some embodiments, scheme 2: RACH resource configuration N SSBs are associated with 1 RO and one SSB is associated with R preambles in one RO.
[0347] In some embodiments, scheme 2-1: during the first cycle, SSB is mapped to RO in a first order.
[0348] In some embodiments, after K cycles of SSB-RO mapping within the first cycle, the remaining RO and preamble are insufficient to perform one cycle of SSB-RO mapping.
[0349] In some embodiments, the remaining RO and preamble may be unused, partially used, or fully used.
[0350] In some embodiments, in Scheme 1 and Scheme 2, the second information can indicate that some ROs and / or preambles in the RACH resource are unavailable or that new ROs and / or preambles are added based on the RACH resource, so that after K cyclic mappings of SSB-RO within the first cycle, there are no remaining ROs and preambles that are insufficient to perform one cyclic mapping of SSB-RO.
[0351] In some embodiments, in Scheme 1 and Scheme 2, the UE does not expect that after K cycles of SSB-RO cyclic mapping within the first period, there will be remaining RO and preamble insufficient for one cycle of SSB-RO cyclic mapping.
[0352] In some embodiments, on the terminal side: the terminal determines the mapping method of SSB and RO and / or determines the available RO and preamble by means of the following methods.
[0353] Option 1: Configure the RACH resource with a number of preambles associated with an SSB, but do not configure a number of ROs associated with an SSB.
[0354] In some embodiments, scheme 1-1: within the first period, the SSB is associated with the RO in a first order, the first order being: the preamble in an RO is arranged in ascending order; the ROs in the frequency domain FDM are arranged in ascending order according to the frequency domain index; the ROs in a PRACH slot are arranged in ascending order according to the time domain index; and the PRACH slot index is arranged in ascending order.
[0355] In some embodiments, a RACH resource is configured with a preamble index range for a feature used in a RO.
[0356] In some embodiments, after K cycles of SSB-RO mapping within the first cycle, the remaining RO and preamble are insufficient to perform one cycle of SSB-RO mapping.
[0357] In some embodiments, the remaining RO and preamble are not used, are partially used, or are used in full.
[0358] In some embodiments, the single-cycle mapping refers to mapping all configured SSBs to ROs and / or preamble once.
[0359] In some embodiments, the first period can be one of the following: RACH Config period; association period; association pattern period; or a value agreed upon by a higher-level configuration / protocol.
[0360] In some embodiments, scheme 2: RACH resource configuration N SSBs are associated with 1 RO and one SSB is associated with R preambles in one RO.
[0361] In some embodiments, scheme 2-1: during the first cycle, SSB is mapped to RO in a first order.
[0362] In some embodiments, after K cycles of SSB-RO mapping within the first cycle, the remaining RO and preamble are insufficient to perform one cycle of SSB-RO mapping.
[0363] In some embodiments, the remaining RO and preamble may be used.
[0364] In some embodiments, in Scheme 1 and Scheme 2, the second information can indicate that some ROs and / or preambles in the RACH resource are unavailable or that new ROs and / or preambles are added based on the RACH resource, so that after K cyclic mappings of SSB-RO within the first cycle, there are no remaining ROs and preambles that are insufficient to perform one cyclic mapping of SSB-RO.
[0365] In some embodiments, the second information is a predefined / high-level configuration.
[0366] In some embodiments, in Scheme 1 and Scheme 2, the UE does not expect that after K cycles of SSB-RO cyclic mapping within the first period, there will be remaining RO and preamble insufficient for one cycle of SSB-RO cyclic mapping.
[0367] In some embodiments, on the base station side: the base station side determines the mapping method of SSB and RO and / or determines the available RO and preamble by the following methods.
[0368] In some embodiments, Scheme 1: The RACH resource is configured with the number of preambles associated with an SSB, but not with the number of ROs associated with an SSB.
[0369] In some embodiments, the specific method is as described in terminal-side solution 1, and will not be repeated here.
[0370] In some embodiments, scheme 2: RACH resource configuration N SSBs are associated with 1 RO and one SSB is associated with R preambles in one RO.
[0371] In some embodiments, the specific method is as described in terminal-side solution 2, and will not be repeated here.
[0372] Example 1:
[0373] In some embodiments, Scheme 1: The RACH resource is configured with the number of preambles associated with an SSB, but not with the number of ROs associated with an SSB.
[0374] In some embodiments, scheme 1-1: within the first period, the SSB is associated with the RO in a first order, the first order being: the preamble in an RO is arranged in ascending order; the ROs in the frequency domain FDM are arranged in ascending order according to the frequency domain index; the ROs in a PRACH slot are arranged in ascending order according to the time domain index; and the PRACH slot index is arranged in ascending order.
[0375] In some embodiments, a RACH resource is configured with a preamble index range for a feature used in a RO.
[0376] In some embodiments, after K cycles of SSB-RO mapping within the first cycle, the remaining RO and preamble are insufficient to perform one cycle of SSB-RO mapping.
[0377] In some embodiments, the remaining RO and preamble are not used, are partially used, or are used in full.
[0378] In some embodiments, the single-cycle mapping refers to mapping all configured SSBs to ROs and / or preamble once.
[0379] In some embodiments, the first period can be one of the following: RACH Config period; association period; association pattern period; or a value agreed upon by a higher-level configuration / protocol.
[0380] In some embodiments, in scheme 1, the RACH resource is configured with a number of preambles associated with an SSB, but not with a number of ROs associated with an SSB. Within the first cycle, SSBs can be sequentially associated with ROs. In some embodiments, within the first cycle, SSBs are cyclically mapped to ROs.
[0381] In some embodiments, method 1-1: In some embodiments, the mapping relationship of SSB-RO within a first cycle is determined. After completing at least one cycle mapping of SSB-RO within the first cycle, the remaining RO and preamble (first remaining RO and preamble) within the first cycle are insufficient to complete one cycle mapping of SSB-RO, and the first remaining RO and preamble are not used.
[0382] In some embodiments, methods 1-2: In some embodiments, after completing at least one SSB-RO cycle mapping within a first cycle, the remaining RO and preamble (first remaining RO and preamble) within the first cycle are insufficient to complete one SSB-RO cycle mapping. The first remaining RO and preamble can be used. After the first remaining RO and preamble have mapped k (greater than or equal to 0) SSBs, there are finally remaining RO and preamble (second remaining RO and preamble) that are insufficient to map to one SSB (such as SSB#i) (the second remaining RO and preamble can be empty, i.e., there is no second remaining RO and preamble). The RO and preamble mapped to k SSBs in the first remaining RO and preamble can be called the third remaining RO and preamble.
[0383] Method 1-2-1: Use all remaining RO and preamble in the first step.
[0384] Method 1-2-2: The second remaining RO and preamble in the first remaining RO and preamble are not used, and the other RO and preamble in the first remaining RO and preamble are used (the third remaining RO and preamble are used, and the second remaining RO and preamble are not used).
[0385] In some embodiments, referring to Figure 6A, an example is as follows: There are 5 SSBs (SSB#0 / 1 / 2 / 3 / 4, with 16 preambles associated with each SSB), and one RO contains 32 preambles. After SSB#0 and SSB#1 are mapped in RO#1, RO#2 maps SSB#2 and SSB#3, and RO#3 maps SSB#4 and SSB#0. The first remaining RO and preamble are the 16th to 31st preambles in RO#3.
[0386] In some embodiments, if mode 1-1 is used, preambles 16 to 31 in RO#3 are not used.
[0387] In some embodiments, if mode 1-2 is used (where the second residual RO and preamble are empty sets, i.e., there is no second residual RO / preamble), then the 16th to 31st preambles in RO#3 can be used.
[0388] In some embodiments, the first period can be one of the following: RACH Config period; association period; association pattern period; or a value agreed upon by a higher-level configuration / protocol.
[0389] In some embodiments, the first cycle is the association period, and the mapping relationship between SSB and RO within the association period is determined according to scheme 1-1. The remaining RO and preamble (the first remaining RO and preamble) within the association period are insufficient to complete one SSB-RO cycle mapping, and the first remaining RO and preamble are used in scheme 1-1 or 1-2.
[0390] In some embodiments, the first cycle is an association pattern period, which contains K (greater than or equal to 1) association periods. After completing K SSB-RO cycle mappings within the association pattern period, the remaining RO and preamble (the first remaining RO and preamble) are insufficient to complete one SSB-RO cycle mapping. The first remaining RO and preamble determine the mapping relationship between SSB and RO according to scheme 1-1, and determine whether to use the first remaining RO and preamble using scheme 1-1 or 1-2. The mapping relationship between SSB and RO is repeated between association pattern periods.
[0391] In some embodiments, the first cycle is a value agreed upon by the higher-level configuration / protocol, such as 160ms. The mapping relationship between SSB and RO within the first cycle is determined according to scheme 1-1. The remaining RO and preamble (the first remaining RO and preamble) within the first cycle are insufficient to complete one SSB-RO cycle mapping. The first remaining RO and preamble are used in scheme 1-1 or 1-2. The mapping relationship between SSB and RO is repeated between the first cycles.
[0392] Example 2:
[0393] Option 2: RACH resource configuration: N SSBs are associated with 1 RO, and one SSB is associated with R preambles in one RO.
[0394] In some embodiments, scheme 2-1: during the first cycle, SSB is mapped to RO in a first order.
[0395] In some embodiments, after K cycles of SSB-RO mapping within the first cycle, the remaining RO and preamble (the first remaining RO and preamble) are insufficient to perform one cycle of SSB-RO mapping.
[0396] In some embodiments, the remaining RO and preamble are not used, are partially used, or are fully used. In one example, the remaining RO and preamble after the cyclic mapping are not used. In another example, the remaining RO and preamble after the cyclic mapping are partially used. In yet another example, the remaining RO and preamble after the cyclic mapping are fully used. It should be noted that when the remaining RO and preamble after the cyclic mapping are not used, the RO and preamble can complete an integer number of cyclic mappings of the SSB, reducing the complexity of the mapping relationship and thus reducing system complexity. Furthermore, when the remaining RO and preamble after the cyclic mapping are partially or fully used, the utilization rate of the RO and preamble can be improved, thereby increasing system efficiency.
[0397] In scheme 2-1, according to the SSB-RO mapping rule, the first remaining RO and preamble are determined to be mapped to SSBs: after the first remaining RO and preamble have mapped k (greater than or equal to 0) SSBs (third remaining RO and preamble), there are finally remaining ROs and preambles (second remaining RO and preamble) that are insufficient to be mapped to an SSB (such as SSB#i) (the second remaining RO and preamble can be empty, that is, there is no second remaining RO and preamble). The first remaining RO and preamble can be used in method 2-1 / method 2-2 / method 2-3.
[0398] Method 2-1: If the remaining RO and preamble are insufficient to complete one SSB-RO cycle mapping, the remaining RO and preamble are used as follows: According to the SSB-RO mapping rules, determine the SSB mapped by the first remaining RO and preamble and use it, that is, use the third remaining RO and preamble and the second remaining RO and preamble.
[0399] Method 2-2: If the remaining RO and preamble are insufficient to complete one SSB-RO cycle mapping, the RO and preamble that can be fully mapped to an SSB are used, and the other RO and preamble are not used. That is, the third remaining RO and preamble are used, and the second remaining RO and preamble are not used.
[0400] Method 2-3: If the remaining RO and preamble are insufficient to complete one SSB-RO cycle mapping, the remaining RO and preamble are not used: that is, the first remaining RO and preamble are not used.
[0401] In some embodiments, in scheme 2, it is assumed that there are 4 SSBs (SSB#0 / 1 / 2 / 3), N takes the value of 1 / 2, and in the first period, there are 4 ROs in the frequency domain direction and 3 ROs in the time domain direction. The 12 ROs are numbered RO#0 to 11 according to the frequency domain first and the time domain second.
[0402] In some embodiments, referring to Figure 6B, an example of scheme 2-1 is as follows: Following a first order, SSB#0 is mapped to RO#0 and RO#1, SSB#1 is mapped to RO#2,3, SSB#2 is mapped to RO#4,5, SSB#3 is mapped to RO#6,7, SSB#0 is mapped to RO#8,9, and SSB#1 is mapped to RO#10,11. RO#8,9,10,11 are the remaining ROs and preamble, which can be used (scheme 2-1 or scheme 2-2, where the second remaining RO and preamble are empty sets).
[0403] In some embodiments, in Scheme 1 and Scheme 2, the second information can indicate that some ROs and / or preambles in the RACH resource are invalid or that new ROs and / or preambles are added based on the RACH resource, so that no remaining ROs and preambles are available after K cyclic mappings of SSB-ROs in the first cycle. The second information is a predefined / higher-level configuration.
[0404] In some embodiments, the second information indicates that a portion of the RO and / or preamble in the RACH resource is invalid.
[0405] In some embodiments, FIG6A indicates that Preamble #16-31 in RO#3 is unavailable or invalid via second information;
[0406] In some embodiments, FIG6B indicates that RO#8,9,10,11 are unavailable or invalid via a second message.
[0407] In some embodiments, the second information indicates the addition of RO and / or preamble to the RACH resource.
[0408] In some embodiments, taking the configuration in FIG6A as an example, the second information may indicate the addition of 2 ROs in the first cycle, enabling SSB-RO to complete 2 cyclic mappings in the first cycle.
[0409] In some embodiments, taking the configuration in FIG6B as an example, the second information may indicate the addition of 4 FDM ROs in the first cycle, enabling SSB-RO to complete 2 cyclic mappings in the first cycle.
[0410] In some embodiments, the offset of the new RO relative to the existing RO and the number of new ROs can be configured.
[0411] In some embodiments, the bitmap can be configured to indicate a subframe or time slot containing the RO, and optionally, the SCS of the time slot is 60kHz.
[0412] In some embodiments, by adjusting the SSB pattern, configuring the TDD time slot structure, configuring the RO time-frequency position, and configuring the SSB-RO mapping criterion, it can be enabled that there are no remaining ROs and preambles after K cyclic mappings of SSB-RO within the first period.
[0413] In some embodiments, the first period is an association period, an association pattern period, a value agreed upon in the protocol, or a value configured by a higher layer.
[0414] In some embodiments, when the first period is an association period, the above adjustments must also ensure that there are no remaining ROs and preambles after K1 association periods are included in the association pattern period, and that the mapping relationship between SSB and RO is repeated between association pattern periods.
[0415] In some embodiments, the first cycle is a value agreed upon by the protocol or a value configured by a higher layer, and the mapping relationship between SSB and RO is repeated between the first cycles.
[0416] In some embodiments, in Scheme 1 and Scheme 2, the UE does not expect that after K cycles of SSB-RO cyclic mapping within the first period, there will be remaining RO and preamble insufficient for one cycle of SSB-RO cyclic mapping.
[0417] In some embodiments, the first period is an association period, an association pattern period, a value agreed upon in the protocol, or a value configured by a higher layer.
[0418] In some embodiments, when the first period is an association period, the UE does not expect that after K1 association periods there will be remaining ROs and preambles within the association pattern period, the mapping relationship between SSB and RO is repeated between association pattern periods.
[0419] In some embodiments, the first cycle is a value agreed upon by the protocol or a value configured by a higher layer, and the mapping relationship between SSB and RO is repeated between the first cycles.
[0420] Example 3:
[0421] In some embodiments, the RACH resource in the above scheme contains both SBFD symbols and ROs in non-SBFD symbols.
[0422] In some embodiments, the mapping relationship between SSB and RO in SBFD symbols and non-SBFD symbols is determined using the above scheme.
[0423] In some embodiments, the RO set, consisting of the RO in the SBFD symbol and the RO in the non-SBFD symbol, is used in conjunction with a scheme to determine the mapping relationship between SSB and RO.
[0424] In some embodiments, referring to Figure 3C, an example of a joint mapping is as follows: The first period is the association period. The remaining ROs and preambles (the first remaining ROs and preambles) within the association period are insufficient to complete one SSB-RO cycle mapping, and the first remaining ROs and preambles may be omitted. The first period is the association pattern period, which contains K (K=3 in the figure) association periods. After completing K SSB-RO cycle mappings within the association pattern period, the remaining ROs and preambles (the first remaining ROs and preambles) are insufficient to complete one SSB-RO cycle mapping, and the first remaining ROs and preambles may be omitted.
[0425] In some embodiments, the first remaining RO and preamble can be determined to be unused, partially used, or fully used according to method 1-1, method 1-2, method 2-1, method 2-2, and method 2-3.
[0426] In some embodiments, the above scheme can be used in PRACH with repetition, and the mapping relationship of SSB-RO within each association pattern period within a time period can be determined in the above manner.
[0427] In some embodiments, the RACH resource contains ROs in both SBFD and non-SBFD symbols.
[0428] In some embodiments, the mapping relationship between SSB and RO in SBFD symbols and non-SBFD symbols is determined using the above scheme.
[0429] In some embodiments, the RO set, consisting of the RO in the SBFD symbol and the RO in the non-SBFD symbol, is used in conjunction with a scheme to determine the mapping relationship between SSB and RO.
[0430] In some embodiments, the number of repetitions is N0, and the N0 repetitions may be partially repetitions on SBFD symbols and partially repetitions on non-SBFD symbols.
[0431] In some embodiments, repetition transmissions of SBFD symbols and non-SBFD symbols may use different power control parameters, and the corresponding transmission power may be different.
[0432] In some embodiments, the frequency domain positions of the repetitions of SBFD symbols and non-SBFD symbols may be different, but the FDM indexes are the same (e.g., the i-th RO of the FDM).
[0433] In some embodiments, referring to Figure 4, an example is as follows: ROs are numbered #0,1,2,3,4,5,6,7, and ROs #0,2,4,6 are mapped to SSB #0, corresponding to repetitions #1,2,3,4 respectively. ROs #0,2,4 are in SBFD symbols, while RO #6 is in a non-SBFD symbol, and their corresponding powers may differ. ROs #0,2,4 and RO #6 have different frequency domain positions, but both correspond to the first RO in the FDM.
[0434] In some embodiments, the ROs in the above schemes are all valid ROs.
[0435] In some embodiments, a valid RO must satisfy at least one of the following conditions:
[0436] In some embodiments, condition 5-0: RO is within the UL symbol.
[0437] In some embodiments, the UL symbol TDD-UL-DL-ConfigCommon is configured as UL and is not configured as the SBFD symbol.
[0438] In some embodiments, condition 5-1: In a PRACH slot, RO is not before SSB.
[0439] In some embodiments, condition 5-2: the symbol of the RO is at least Ngap symbols away from the symbol of the previous SSB.
[0440] In some embodiments, condition 5-3: RO does not overlap with SSB in the time domain on the non-SBFD symbol.
[0441] In some embodiments, condition 5-4: RO is at least Ngap symbols apart from the previous DL symbol.
[0442] In some embodiments, the DL symbol is TDD-UL-DL-ConfigCommon configured as DL and not configured as SBFD symbol.
[0443] In some embodiments, condition 5-5: RO does not overlap with the UL subband on the SBFD symbol.
[0444] In some embodiments, conditions 5-6: RO does not contain both SBFD and non-SBFD symbols simultaneously (i.e., a valid RO cannot span both SBFD and non-SBFD symbols).
[0445] In some embodiments, conditions 5-7: RO is on the SBFD symbol (i.e., valid RO can only be on the SBFD symbol).
[0446] In some embodiments, conditions 5-8: RO is on a non-SBFD symbol (i.e., a valid RO can only be on a non-SBFD symbol).
[0447] In some embodiments, the cell-level symbol format is configured such that RO on an SBFD symbol (F symbol or DL symbol configured as SBFD symbol) must satisfy at least one of the following conditions to be valid:
[0448] In some embodiments, the RO is at least Ngap symbols away from the symbol containing the previous SSB.
[0449] In some embodiments, the RO is separated from the previous DL (non-SBFD) symbol by at least Ngap symbols.
[0450] In some embodiments, the DL symbol is TDD-UL-DL-ConfigCommon configured as DL and not configured as SBFD symbol.
[0451] In some embodiments, the RO does not overlap with the UL subband on the SBFD symbol.
[0452] In some embodiments, the symbols for RO and SSB do not overlap.
[0453] In some embodiments, the cell-level symbol format is configured such that RO on a non-SBFD symbol must satisfy either condition 1 or condition 2 to be valid:
[0454] In some embodiments, condition 1: RO is within the UL symbol.
[0455] In some embodiments, the UL symbol TDD-UL-DL-ConfigCommon is configured as UL and is not configured as the SBFD symbol.
[0456] In some embodiments, condition 2: In a PRACH slot, RO is not before SSB, and RO is at least N gap symbols away from the symbol containing the previous SSB, and RO is at least N gap symbols away from the symbol containing the previous DL (non-SBFD).
[0457] In some embodiments, the cell-level symbol format is not configured, and the RO on a non-SBFD symbol is valid if the following conditions are met: in a PRACH slot, the RO is not before the SSB, and the RO is at least Ngap symbols away from the symbol containing the previous SSB.
[0458] Figure 9 is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. As shown in Figure 9, the communication method includes steps 1 and 2.
[0459] Step 1: Send the first message, which includes RACH resource configuration information and the second message.
[0460] In some embodiments, the second information includes at least one of the following: some ROs and / or preambles in the RACH resource are invalid; or additional ROs and / or preambles are added based on the RACH resource.
[0461] Step 2: Based on the first information, determine the available RO and preamble, and determine the mapping relationship between SSB and RO.
[0462] In some embodiments, according to scheme 1 and scheme 2, the available ROs and preambles are determined, and the mapping relationship between SSBs and ROs is determined.
[0463] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus including units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed, including units or modules for implementing the steps performed by the network device in any of the above methods.
[0464] 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.
[0465] In this embodiment, 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, microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or 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 by an application-specific integrated circuit (ASIC) or a programmable logic device, 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. Furthermore, 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), tensor processing unit (TPU), deep learning processing unit (DPU), etc.
[0466] Figure 10 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 10, the communication device 1000 may include at least one of the following: a transceiver module 1001 and a processing module 1002.
[0467] In some embodiments, the communication device 1000 may be a terminal 101. In some embodiments, the transceiver module 1001 may be configured to: acquire first information, wherein the first information includes RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being used to map to a plurality of SSBs; wherein the second information indicates adding or removing a second random access resource based on the first random access resource. Optionally, the transceiver module 1001 may be used to perform at least one of the communication steps (e.g., step S501, but not limited thereto) performed by the terminal 101 in any of the above methods, and will not be elaborated further here. Optionally, the processing module 1002 may be used to perform at least one of the other steps (e.g., step S502, but not limited thereto) performed by the terminal 101 in any of the above methods, and will not be elaborated further here.
[0468] In some embodiments, the communication device 1000 may be a network device 102. In some embodiments, the transceiver module 1001 may be configured to: send first information to a terminal, wherein the first information includes RACH configuration and second information; wherein the RACH configuration is used to determine a first random access resource, the first random access resource being used to map to a plurality of SSBs; wherein the second information indicates adding or removing a second random access resource based on the first random access resource. Optionally, the transceiver module 1001 may be used to perform at least one of the communication steps (e.g., step S501, but not limited thereto) performed by the network device 102 in any of the above methods, which will not be elaborated here.
[0469] In some embodiments, the communication device 1000 shown in FIG10 may also be implemented as a communication device.
[0470] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated together. Optionally, the transceiver module may be interchangeable with a transceiver.
[0471] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.
[0472] Figure 11A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 11100 can be a terminal (e.g., a user equipment), a network device (e.g., a core network device, an access network device), a chip, chip system, or processor that supports the terminal in implementing any of the above methods, or a chip, chip system, or processor that supports the network device in implementing any of the above methods. The communication device 11100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0473] As shown in Figure 11A, the communication device 11100 includes one or more processors 11101. The processor 11101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 11100 can be used to execute any of the above methods. Optionally, one or more processors 11101 can be used to invoke instructions to cause the communication device 11100 to execute any of the above methods.
[0474] In some embodiments, the communication device 11100 further includes one or more transceivers 11102. When the communication device 11100 includes one or more transceivers 11102, the transceivers 11102 perform at least one of the communication steps (e.g., step S501, but not limited thereto) in the above method, such as sending and / or receiving, and the processor 11101 performs at least one of other steps (e.g., step S502, but not limited thereto). In optional embodiments, the transceivers may include receivers and / or transmitters, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0475] In some embodiments, the communication device 11100 further includes one or more memories 11103 for storing data. Optionally, all or part of the memories 11103 may be located outside the communication device 11100. In optional embodiments, the communication device 11100 may include one or more interface circuits 11104. Optionally, the interface circuits 11104 are connected to the memories 11103 and can be used to receive data from the memories 11103 or other devices, and can be used to send data to the memories 11103 or other devices. For example, the interface circuits 11104 can read data stored in the memories 11103 and send the data to the processor 11101.
[0476] The communication device 11100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 11100 described in this disclosure is not limited thereto, and the structure of the communication device 11100 may not be limited by FIG11A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include 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 device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0477] Figure 11B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 11100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 11200 shown in Figure 11B, but it is not limited thereto.
[0478] Chip 11200 includes one or more processors 11201. Chip 11200 is used to perform any of the above methods.
[0479] In some embodiments, chip 11200 further includes one or more interface circuits 11202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 11200 further includes one or more memories 11203 for storing data. Optionally, all or part of the memories 11203 may be located outside of chip 11200. Optionally, interface circuit 11202 is connected to memory 11203, and interface circuit 11202 can be used to receive data from memory 11203 or other devices, and interface circuit 11202 can be used to send data to memory 11203 or other devices. For example, interface circuit 11202 can read data stored in memory 11203 and send the data to processor 11201.
[0480] In some embodiments, the interface circuit 11202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., step S501, but not limited thereto). For example, the interface circuit 11202 performing the communication steps such as sending and / or receiving in the above-described method means that the interface circuit 11202 performs data interaction between the processor 11201, the chip 11200, the memory 11203, or the transceiver device. In some embodiments, the processor 11201 performs at least one of other steps (e.g., step S502, but not limited thereto).
[0481] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0482] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 11100, cause the communication device 11100 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 is not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto; it may also be a temporary storage medium.
[0483] This disclosure also proposes a program product that, when executed by the communication device 11100, causes the communication device 11100 to perform any of the above methods. Optionally, the program product is a computer program product.
[0484] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
[0485] 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.
[0486] 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 communication method, executed by a terminal, wherein, The method includes: Obtain first information, wherein the first information includes random access channel (RACH) configuration and second information; The RACH configuration is used to determine a first random access resource, which is used to map to a plurality of synchronization signal blocks (SSBs). The second information indicates whether to add or reduce the second random access resource based on the first random access resource.
2. The method according to claim 1, wherein, The first random access resource includes: Random Access Channel Timing (RO); Preamble.
3. The method according to claim 1 or 2, wherein, The second random access resource includes at least one of the following: Unavailable ROs in the first random access resource; Unavailable preamble in the first random access resource; Available ROs other than the first random access resource; Available preambles other than the first random access resource.
4. The method according to any one of claims 1 to 3, wherein, The terminal does not expect the existence of remaining random access resources in the first period, and the number of remaining random access resources is less than the number of random access resources required for the mapping of the plurality of SSBs.
5. The method according to claim 4, wherein, The first cycle includes one of the following: RACH configuration cycle; Related cycle; Related pattern cycle; Preset cycle.
6. The method according to any one of claims 1 to 5, wherein, The second information was obtained through one of the following methods: The agreement stipulates; Received from network devices.
7. The method according to any one of claims 1 to 6, wherein, The method further includes: Based on the first information, determine the third random access resource within the first period; Determine the mapping relationship between the plurality of SSBs and the third random access resource, wherein the plurality of SSBs are mapped on the third random access resource at least once, and the number of the third random access resources is an integer multiple of the number of random access resources required for the mapping of the plurality of SSBs.
8. The method according to claim 7, wherein, The second information indicates the addition of the second random access resource, and the third random access resource includes the first random access resource and the second random access resource, with the second random access resource occurring within the first period.
9. The method according to claim 7, wherein, The second information indicates a reduction in the second random access resource, and the third random access resource includes the random access resources in the first random access resource other than the second random access resource.
10. A communication method, performed by a network device, wherein, The method includes: Send first information to the terminal, wherein the first information includes random access channel (RACH) configuration and second information; The RACH configuration is used to determine a first random access resource, which is used to map to a plurality of synchronization signal blocks (SSBs). The second information indicates whether to add or reduce the second random access resource based on the first random access resource.
11. The method according to claim 10, wherein, The first random access resource includes: Random Access Channel Timing (RO); Preamble.
12. The method according to claim 10 or 11, wherein, The second random access resource includes at least one of the following: Unavailable ROs in the first random access resource; Unavailable preamble in the first random access resource; Available ROs other than the first random access resource; Available preambles other than the first random access resource.
13. The method according to any one of claims 10 to 12, wherein, The terminal does not expect the existence of remaining random access resources in the first period, and the number of remaining random access resources is less than the number of random access resources required for the mapping of the plurality of SSBs.
14. The method according to claim 13, wherein, The first cycle includes one of the following: RACH configuration cycle; Related cycle; Related pattern cycle; Preset cycle.
15. The method according to any one of claims 10 to 14, wherein, The first information is used by the terminal to determine the third random access resource within the first period, and the mapping relationship between the plurality of SSBs and the third random access resource; The plurality of SSBs are mapped on the third random access resource at least once, and the number of the third random access resources is an integer multiple of the number of random access resources required for the mapping of the plurality of SSBs.
16. The method according to claim 15, wherein, The second information indicates the addition of the second random access resource, and the third random access resource includes the first random access resource and the second random access resource, with the second random access resource occurring within the first period.
17. The method according to claim 15, wherein, The second information indicates a reduction in the second random access resource, and the third random access resource includes the random access resources in the first random access resource other than the second random access resource.
18. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1-9 and 10-17.
19. A communication system comprising a terminal and network equipment, wherein, The terminal is configured to implement the communication method as described in any one of claims 1 to 9, and the network device is configured to implement the communication method as described in any one of claims 10 to 17.
20. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-9 and 10-17.
21. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method as described in any one of claims 1-9 and 10-17.