Communication method and communication apparatus
By configuring parameters based on the association between synchronization signal blocks and preambles in the terminal device within the 5G new wireless system, the problem of network device configuration being unsuitable for the terminal communication environment is solved, and the success rate of random access is improved.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- HUAWEI TECH CO LTD
- Filing Date
- 2025-12-15
- Publication Date
- 2026-07-02
AI Technical Summary
In 5G new wireless systems, different terminals may have different communication environments, and the random access parameters configured in network devices may not be suitable, leading to a decrease in the random access performance of the terminals.
By receiving the synchronization signal block (SSB), the terminal device configures parameters based on the association between the SSB and the preamble, adapts to the communication environment, and improves random access performance.
It improves the success rate of random access for terminals and adapts terminal performance to different communication environments.
Smart Images

Figure CN2025142648_02072026_PF_FP_ABST
Abstract
Description
Communication methods and communication devices
[0001] This application claims priority to Chinese Patent Application No. 202411943316.4, filed on December 24, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communication technology, and in particular to communication methods and communication devices. Background Technology
[0003] In 5th generation (5G) new radio (NR) systems, network devices can configure parameters for random access for terminals via system information block (SIB) 1. Terminals need to initiate random access according to the parameters indicated by SIB 1.
[0004] However, different terminals may have different communication environments, and the parameters configured for random access by network devices may not be suitable for the current communication environment of the terminal. Inappropriate random access parameters may reduce the random access performance of the terminal. Summary of the Invention
[0005] This application provides a communication method and a communication device, which are beneficial to improving the random access performance of terminals.
[0006] In a first aspect, this application provides a communication method applicable to a terminal-side device, which may be a terminal, or a processor, module, chip, chip system, or functional module of the terminal for implementing the method. The method includes: receiving a first synchronization signal block (SSB); the terminal receiving first information indicating a first association relationship; and sending a random access request based on the first association relationship; wherein the first association relationship includes at least one of the following:
[0007] The association between the first preamble root index and the first SSB; or,
[0008] The relationship between the first cyclic shift offset and the first SSB; or,
[0009] The relationship between the first preamble length, the first preamble resource configuration, and the first SSB; or,
[0010] The association between the first restricted set, the first zero-related region configuration, and the first SSB; or,
[0011] The relationship between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the first SSB; or,
[0012] The relationship between the first cyclic prefix length, the first preamble resource configuration, and the first SSB.
[0013] Based on the method described in the first aspect, the network device can associate appropriate preamble configuration parameters with the first SSB according to the coverage area corresponding to the first SSB, thereby adapting to the communication environment of the terminal under the coverage area of the first SSB, thereby improving the random access performance of the terminal and thus improving the success rate of the random access of the terminal.
[0014] In one possible implementation, the first information also indicates a second association, which includes at least one of the following:
[0015] The association between the second preamble root index and the second SSB; or,
[0016] The relationship between the second cyclic shift offset and the second SSB; or,
[0017] The relationship between the second preamble length, the second preamble resource configuration, and the second SSB; or,
[0018] The association between the second restricted set, the second zero-related region configuration, and the second SSB; or,
[0019] The association between the second preamble sequence type, the second preamble length, the second preamble root index, the second cyclic shift offset, the second preamble resource configuration, and the second SSB; or,
[0020] The relationship between the second cyclic prefix length, the second preamble resource configuration, and the second SSB.
[0021] In one possible implementation, the preamble format of the second SSB association is the same as that of the first SSB association.
[0022] In one possible implementation, the preamble configuration parameters associated with the first SSB and the second SSB are different. The preamble configuration parameters include at least one of the following: preamble root index, preamble length, cyclic shift offset, restriction set, cyclic prefix length, preamble resource configuration, zero correlation region configuration, or preamble sequence type.
[0023] In one possible implementation, the first parameter of the second SSB differs from that of the first SSB. The first parameter includes one or more of the following: SSB transmit power, SSB target receive power, or SSB beamforming gain. Based on this implementation, the network device transmitting the SSB can be characterized by the first parameter. For example, the difference between the first parameter of the second SSB and the first SSB indicates that the network device used to transmit the second SSB is different from the network device used to transmit the first SSB. The coverage areas or ranges of the first and second network devices differ. By configuring different preamble configuration parameters for the first and second SSBs, it is beneficial to improve the random access performance of terminals in different communication environments.
[0024] In one possible implementation, the first information indicates a third association, which includes at least one of the following:
[0025] The association between the third preamble root index and the first SSB; or,
[0026] The relationship between the third cyclic shift offset and the first SSB; or,
[0027] The relationship between the length of the third preamble, the resource configuration of the third preamble, and the first SSB; or,
[0028] The association between the third restricted set, the third zero-related region configuration, and the first SSB; or,
[0029] The relationship between the third preamble sequence type, third preamble length, third preamble root index, third cyclic shift offset, third preamble resource configuration, and the first SSB; or,
[0030] The relationship between the length of the third cyclic prefix, the resource configuration of the third preamble, and the first SSB.
[0031] In one possible implementation, the first information indicates a first association group, which includes a first association and a third association.
[0032] In one possible implementation, the first information indicates a second association group, which includes a fourth association, the fourth association including at least one of the following:
[0033] The association between the first preamble root index and the third SSB; or,
[0034] The relationship between the first cyclic shift offset and the third SSB; or,
[0035] The relationship between the first preamble length, the first preamble resource configuration, and the third SSB; or,
[0036] The association between the first restricted set, the first zero-related region configuration, and the third SSB; or,
[0037] The relationship between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the third SSB; or,
[0038] The relationship between the length of the first cyclic prefix, the resource configuration of the first preamble, and the third SSB.
[0039] In one possible implementation, the first information also indicates the association between the first SSB and the first random access channel occasion (RO), on which the random access request is transmitted.
[0040] In one possible implementation, the first information is carried in system information block 1 (SIB1).
[0041] Secondly, this application provides a communication method that can be applied to a network-side device, which may be a network device, or a processor, module, chip, chip system, or functional module of the network device for implementing the method. The method includes: sending a first SSB; and sending first information, wherein the first information indicates the association between the first SSB and a first preamble format.
[0042] The beneficial effects of the second aspect and its possible implementation methods can be found in the description of the first aspect, and will not be repeated here.
[0043] In one possible implementation, the first information also indicates a second association, which includes at least one of the following:
[0044] The association between the second preamble root index and the second SSB; or,
[0045] The relationship between the second cyclic shift offset and the second SSB; or,
[0046] The relationship between the second preamble length, the second preamble resource configuration, and the second SSB; or,
[0047] The association between the second restricted set, the second zero-related region configuration, and the second SSB; or,
[0048] The association between the second preamble sequence type, the second preamble length, the second preamble root index, the second cyclic shift offset, the second preamble resource configuration, and the second SSB; or,
[0049] The relationship between the second cyclic prefix length, the second preamble resource configuration, and the second SSB.
[0050] In one possible implementation, the preamble format of the second SSB association is the same as that of the first SSB association.
[0051] In one possible implementation, the preamble configuration parameters associated with the first SSB and the second SSB are different. The preamble configuration parameters include at least one of the following: preamble root index, preamble length, cyclic shift offset, restriction set, cyclic prefix length, preamble resource configuration, zero correlation region configuration, or preamble sequence type.
[0052] In one possible implementation, the first parameter of the second SSB differs from that of the first SSB. The first parameter includes one or more of the following: SSB transmit power, SSB target receive power, or SSB beamforming gain. Based on this implementation, the network device transmitting the SSB can be characterized by the first parameter. For example, the difference between the first parameter of the second SSB and the first SSB indicates that the network device used to transmit the second SSB is different from the network device used to transmit the first SSB. The coverage areas or ranges of the first and second network devices differ. By configuring different preamble configuration parameters for the first and second SSBs, it is beneficial to improve the random access performance of terminals in different communication environments.
[0053] In one possible implementation, the first information indicates a third association, which includes at least one of the following:
[0054] The association between the third preamble root index and the first SSB; or,
[0055] The relationship between the third cyclic shift offset and the first SSB; or,
[0056] The relationship between the length of the third preamble, the resource configuration of the third preamble, and the first SSB; or,
[0057] The association between the third restricted set, the third zero-related region configuration, and the first SSB; or,
[0058] The relationship between the third preamble sequence type, third preamble length, third preamble root index, third cyclic shift offset, third preamble resource configuration, and the first SSB; or,
[0059] The relationship between the length of the third cyclic prefix, the resource configuration of the third preamble, and the first SSB.
[0060] In one possible implementation, the first information indicates a first association group, which includes a first association and a third association.
[0061] In one possible implementation, the first information indicates a second association group, which includes a fourth association, the fourth association including at least one of the following:
[0062] The association between the first preamble root index and the third SSB; or,
[0063] The relationship between the first cyclic shift offset and the third SSB; or,
[0064] The relationship between the first preamble length, the first preamble resource configuration, and the third SSB; or,
[0065] The association between the first restricted set, the first zero-related region configuration, and the third SSB; or,
[0066] The relationship between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the third SSB; or,
[0067] The relationship between the length of the first cyclic prefix, the resource configuration of the first preamble, and the third SSB.
[0068] In one possible implementation, the first information also indicates the association between the first SSB and the first RO, and the random access request is transmitted on the first RO.
[0069] In one possible implementation, the first information is carried in SIB1.
[0070] Thirdly, embodiments of this application provide a communication device for executing the method in any possible implementation of either the first or second aspect. The communication device includes modules for executing the method in any possible implementation of either the first or second aspect.
[0071] Fourthly, embodiments of this application provide a communication device including a processing circuit for executing a method in any possible implementation of either the first or second aspect. The processing circuit executes a program, and when the program is executed, the method described in any possible implementation of either the first or second aspect is performed.
[0072] In one possible implementation, the communication device further includes a memory for storing the program.
[0073] In one possible implementation, the memory is located outside the aforementioned communication device.
[0074] In one possible implementation, the memory is located within the aforementioned communication device.
[0075] Furthermore, the processing circuitry and memory can be integrated into a single device; that is, the processing circuitry and memory can be combined. For example, the communication device can be a chip.
[0076] In one possible implementation, the communication device further includes a transceiver circuit for receiving information (or inputting information) or sending information (or outputting information).
[0077] Fifthly, embodiments of this application provide a communication device, which includes a processing circuit and a transceiver circuit. The processing circuit can be a logic circuit, and the transceiver circuit can be an interface circuit. The logic circuit and the interface are coupled. The interface circuit is used to input and / or output information, and the logic circuit is used to execute a method of any possible implementation of either the first or second aspect.
[0078] In a sixth aspect, this application provides a communication system, including a communication device for performing the method described in the first aspect and a communication device for performing the method described in the second aspect.
[0079] In a seventh aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the method described in any possible implementation of either the first or second aspect to be executed.
[0080] Eighthly, embodiments of this application provide a computer program product that, when run on a computer, causes the method shown in any possible implementation of either the first or second aspect to be executed. Attached Figure Description
[0081] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;
[0082] Figure 2 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;
[0083] Figure 3A is a schematic diagram of a four-step random access process provided in an embodiment of this application;
[0084] Figure 3B is a schematic diagram of a two-step random access process provided in an embodiment of this application;
[0085] Figure 3C is a schematic diagram of an RRC connection establishment process provided in an embodiment of this application;
[0086] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application;
[0087] Figure 5 is a schematic diagram of a capacity network device and an anchor network device provided in an embodiment of this application;
[0088] Figure 6 is a schematic diagram of the association between preamble configuration information and RO provided in an embodiment of this application;
[0089] Figure 7A is a schematic diagram of the association between preamble configuration information and RO provided in an embodiment of this application;
[0090] Figure 7B is a schematic diagram illustrating the association between preamble configuration information and RO provided in an embodiment of this application;
[0091] Figure 7C is a schematic diagram illustrating the association between preamble configuration information and RO provided in an embodiment of this application;
[0092] Figure 7D is a schematic diagram illustrating the association between preamble configuration information and RO provided in an embodiment of this application;
[0093] Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0094] Figure 9 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0095] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation
[0096] To facilitate understanding of the technical solution of this application, the application will be further described below with reference to the accompanying drawings.
[0097] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used only to distinguish different objects and not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.
[0098] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.
[0099] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. "Or" indicates that there can be two relationships, such as only A exists and only B exists; when A and B are not mutually exclusive, it can also mean that there are three relationships, such as only A exists, only B exists, and both A and B exist simultaneously. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".
[0100] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which can include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which can include direct reception from YY via the air interface or indirect reception from YY via the air interface from other units or modules. "Send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via buses, traces, or interfaces.
[0101] In this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time. They do not require a judgment action during implementation, nor do they imply any other limitations.
[0102] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.
[0103] In this application, "instruction" may include: direct instruction, or indirect instruction, or explicit instruction, or implicit instruction.
[0104] In this application, "including" can include: direct inclusion, indirect inclusion, explicit inclusion, or implicit inclusion.
[0105] The prior art may change as the technical solutions evolve, and the technical solutions provided in this application are not limited to the prior art provided.
[0106] It should be noted that different embodiments or some steps (e.g., any one or more steps) in different embodiments of this application can be combined with each other to form new embodiments. It should also be noted that the scope of this application is not limited to including optional steps in a certain embodiment, mandatory steps in a certain embodiment, or both optional and mandatory steps in a certain embodiment.
[0107] It should be noted that, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced in each other.
[0108] It should be noted that the order of the steps in the embodiments of this application is not limited by this application.
[0109] It should be noted that the order in which different conditions are judged in the embodiments of this application is not limited by this application.
[0110] It should be noted that the terms "after" and "time" in this application do not strictly limit the specific point in time.
[0111] It should be noted that the nouns and terms used in this application are merely examples and may be other names, which are not limited in this application.
[0112] The following describes the communication system involved in the embodiments of this application.
[0113] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.
[0114] The method provided in this application can be applied between two entities in a communication system, such as one entity sending information to or receiving information sent by the other entity. In a wireless communication system, communication devices are included, and these devices can communicate wirelessly using air interface resources. Air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources; this application does not limit this. For example, the aforementioned two entities may include a network device and a terminal device, or may include a chip that can be placed in a network device and a chip that can be placed in a terminal device, etc. Of course, as standards advance, other types of entities may emerge subsequently; this application does not limit this.
[0115] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system may include at least one network device and at least one terminal device, such as terminal device 1 to terminal device 4 in Figure 1. The terminal device and the network device can communicate via an air interface Uu link or via a non-terrestrial network (NTN) link, etc. For example, terminal device 3 and terminal device 4 can communicate via a D2D sidelink, etc. The form of the terminal device shown in Figure 1 is only an example. In a specific implementation, the terminal device may also include in-vehicle equipment or in-vehicle terminals in a vehicle network. This application embodiment does not limit the specific form of the terminal device when applied to a vehicle network or the Internet.
[0116] Figure 2 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 2, the scenarios of this communication system may include at least one of scenario (a), scenario (b), scenario (c), or scenario (d). Scenario (a) is a point-to-point single connection between a network device and a terminal device; scenario (b) is a multi-hop single connection between a network device and a terminal device; scenario (c) is a point-to-point dual connectivity (DC) between a network device and a terminal device; and scenario (d) is a multi-hop dual connection between a network device and a terminal device.
[0117] Figure 1 exemplarily illustrates a network device and multiple terminal devices, and Figure 2 exemplarily illustrates single-connection and dual-connection. In specific implementations, the communication system may also include a greater number of network devices, and the coverage area of each network device may include a greater or lesser number of terminal devices; this application embodiment does not limit this. The architectures shown in Figures 1 and 2 are merely examples and do not impose limitations on the network architecture applicable to this application. Any network-side device communicating with or sensing other devices is a network architecture usable in this application.
[0118] The following provides a detailed description of terminal equipment and network equipment.
[0119] A terminal device is a device with wireless transceiver capabilities. It can communicate with RAN nodes (or wireless access devices, or network devices as described below) in a radio access network (RAN). Terminal devices can also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device, etc. In one possible implementation, the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; or it can be deployed on water, including ships; or it can be deployed in the air, such as on airplanes, balloons, or satellites. In another possible implementation, the terminal device can be a handheld device with wireless communication capabilities, a vehicle-mounted device, a wearable device, a sensor, a terminal in the Internet of Things (IoT), a terminal in the Internet of Vehicles (IoV), a drone, a terminal device in a 5G network, or any form of terminal device in a future network, etc., and this application embodiment does not limit this. In another possible implementation, the terminal device can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, or a wireless terminal in a smart home, etc.
[0120] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself; it can also be a device capable of supporting the terminal device in implementing the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In this application embodiment, the chip system can be composed of chips or can include chips and other discrete devices. For ease of description, when examples are mentioned below, the technical solutions provided in this application embodiment are described using a UE as an example.
[0121] A network device can be a device deployed in a wireless access network to provide wireless communication services to terminal devices. This network device can also be called an access network device, access equipment, or RAN device, etc. For example, a network device can be a next-generation node B (gNB), a next-generation evolved node B (ng-eNB), or a network device in future communications. A network device can be any device with wireless transceiver capabilities, including but not limited to the base stations mentioned above (including base stations deployed on satellites). This network device can also be a device with base station functionality in future communication systems. As an example, this network device can be an access node, wireless relay node, or wireless backhaul node in a wireless-fidelity (Wi-Fi) system. As another example, this network device can be a wireless controller in a cloud radio access network (CRAN) scenario. As yet another example, this network device can be a wearable device or vehicle-mounted device capable of providing wireless communication services. As yet another example, this network device can also be a small cell, a transmission reception point (TRP) (or transceiver point), etc. In systems using different wireless access technologies, the names of devices with network equipment functions may vary, and these will not be listed one by one in the embodiments of this application.
[0122] Network devices can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, a helicopter or drone can be configured to be used as a device to communicate with another network device.
[0123] In some network device deployments, the network device may include a central unit (CU) and a distributed unit (DU). For example, some protocol layer functions of the network device may be centrally controlled by the CU, while the remaining part or all of the protocol layer functions may be distributed in the DU, which is centrally controlled by the CU. In other network device deployments, the CU may be divided into a CU-control plane (CP) and a CU-user plane (UP). In still other network device deployments, the network device may also be an open radio access network (ORAN) architecture. When the network device is an ORAN architecture, it may be a functional entity or module within the ORAN. For example, the network device may be one or more of a CU, DU, or RU. In an ORAN system, the CU may also be called an open (O)-CU, the DU may also be called an O-DU, the CU-CP may also be called an O-CU-CP, and the CU-UP may also be called an O-CU-UP, etc. The network device deployment methods listed here are merely examples. As standard technologies evolve, network devices may have other deployment forms, and this application does not limit these.
[0124] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing a portion of the access network's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as an indoor baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).
[0125] RAN nodes can support one or more types of fronthaul interfaces, each corresponding to a DU and RU with different functions. If the fronthaul interface between the DU and RU is a Common Public Radio Interface (CPRI), the DU is configured to implement one or more baseband functions, and the RU is configured to implement one or more radio frequency functions. If the fronthaul interface between the DU and RU is another type of interface, relative to CPRI, it moves some downlink and / or uplink baseband functions—for example, for downlink, precoding, or one or more of inverse fast Fourier transform (IFFT) / adding a cyclic prefix (CP)—from the DU to the RU; and for uplink, digital beamforming, or one or more of fast Fourier transform (FFT) / removing CP—from the DU to the RU. In one possible implementation, this interface can be an enhanced common public radio interface (eCPRI). Under the eCPRI architecture, the partitioning methods between DU and RU are different, corresponding to different types (category, Cat) of eCPRI, such as eCPRI Cat A, B, C, D, E, F.
[0126] Taking eCPRI Cat A as an example, for downlink transmission, layer mapping is used as the dividing line. The DU is configured to implement one or more functions preceding layer mapping (i.e., coding, rate matching, scrambling, modulation, and layer mapping itself), while other functions following layer mapping (e.g., resource element (RE) mapping, digital beamforming, or IFFT / CP addition) are implemented in the RU. For uplink transmission, de-RE mapping is used as the dividing line. The DU is configured to implement one or more functions preceding de-mapping (i.e., decoding, rate matching de-matching, descrambling, demodulation, inverse discrete Fourier transform (IDFT), channel equalization, and de-RE mapping itself), while other functions following de-mapping (e.g., digital BF or FFT / CP removal) are implemented in the RU. For functional descriptions of the DU and RU corresponding to various types of eCPRI, please refer to the eCPRI protocol; they will not be elaborated here.
[0127] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.
[0128] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.
[0129] Network devices and / or terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, or software functions running on dedicated hardware or general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.
[0130] In this embodiment, the device for implementing the functions of the network device can be the network device itself; or it can be a device capable of supporting the network device in implementing the functions, such as a chip system. This device can be installed in the network device or used in conjunction with the network device.
[0131] The following explains the relevant terms used in the embodiments of this application:
[0132] I. Initial Access
[0133] Initial access refers to the process of a terminal initially connecting to the network. The main goal of initial access is to allocate necessary resources and establish a reliable communication link when the terminal first accesses or re-accesses the network. For example, as shown in Figures 3A-3C, the main steps of initial terminal access are as follows:
[0134] 301. Network devices can periodically broadcast different synchronization signal blocks (SSBs) in different communication areas, and these SSBs can be distinguished by their indices. SSBs can also be called synchronization signal and physical broadcasting channel blocks (SS / PBCH blocks). Different SSB indices represent SSBs with different beam directions, which are used to cover and serve different areas. When a terminal receives an SSB from a network device, it can determine the time-frequency resource where system information block 1 (SIB1) is located based on the SSB.
[0135] 302. The terminal receives SIB1 from the network device according to the time-frequency resources where SIB1 is located. SIB1 indicates the configuration parameters for random access, such as the time-frequency resources for the random access channel occasion (RO), the available random access preamble, and the preamble format.
[0136] The terminal can perform random access according to the configuration parameters for random access indicated by the SIB. For example, as shown in Figure 3A, the terminal can use a four-step random access method, as shown in steps a1 to a4 below:
[0137] a1. The terminal sends a random access message 1 (Msg1) to the network device on the RO selected based on SIB1. The content of Msg1 is the random access preamble selected by the terminal. The terminal sends the random access preamble to the network device to make a random access request. At the same time, the network device uses the random access preamble sent by the terminal to estimate the transmission delay between itself and the terminal so that the network device can calibrate the uplink timing.
[0138] The random access preamble, also known as the physical random access channel (PRACH) preamble, preamble signal, or simply preamble, is a short-lived Zadoff-Chu (ZC) sequence that exhibits good autocorrelation and cross-correlation properties, helping the base station accurately detect access requests.
[0139] a2. After receiving Msg1, the network device sends a random access message 2 (Msg2) to the terminal. Msg2 can also be called a random access response, which may include one or more of the following information: time alignment (TA), uplink grant (UL grant), temporary cell radio network temporary identifier (TC-RNTI), power control, and resource indications for the terminal to send random access message 3 (Msg3), etc. Msg2 may also include other information, which is not limited in this embodiment.
[0140] a3. After receiving Msg2, if the preamble indicated by the sequence number of the preamble in Msg2 is the same as the preamble in Msg1 sent by the terminal, the terminal can determine that Msg2 is a random access response for itself, and send Msg3 on the uplink channel resources indicated by Msg2. Msg3 may carry a unique user identifier.
[0141] a4. After receiving Msg3 from the terminal, the network device returns a random access message 4 (Msg4) to the successfully connected terminal. The network device includes the unique user identifier from Msg3 in Msg4 to identify the successfully connected terminal, while other unsuccessful terminals will re-initiate random access. If the unique user identifier included in Msg4 matches the unique user identifier carried in the terminal's Msg3, the terminal considers the access successful.
[0142] Terminals can also employ two-step random access to reduce access latency and signaling overhead. For example, as shown in Figure 3B, the two-step random access process can be seen in steps b1 to b2 below. Steps a1 to a4 above can also be replaced by steps b1 to b2 below.
[0143] b1. The terminal sends a random access message A (MsgA) to the network device. MsgA includes a preamble and data.
[0144] b2. The network device sends a random access message B (MsgB) to the terminal.
[0145] Of course, the random access method described above is only an example. The terminal may also use other methods to initiate random access during the initial access process. This application embodiment does not limit this.
[0146] After completing random access, the terminal can establish a radio resource control (RRC) connection with the network device, as shown in Figure 3C:
[0147] 303. The terminal sends an RRC connection request message, and the corresponding network device receives the RRC connection request message from the terminal. This RRC connection request message is used to request the establishment of an RRC connection.
[0148] 304. After the network device and the terminal have established an RRC connection, the network device sends an RRC connection confirmation message to the terminal. The RRC connection confirmation message indicates that the RRC connection has been established. After receiving the RRC connection confirmation message, the terminal can then engage in subsequent communication and data transmission with the network device.
[0149] II. Preamble Configuration Information
[0150] The preamble configuration parameters are parameters configured by the network device for use by the terminal when sending a preamble. For example, the preamble configuration information may include one or more of the following: preamble root index, preamble length, zerocorrelation zone configuration, cyclic shift (CS) offset, constraint set, cyclic prefix length, preamble resource configuration, or preamble sequence type.
[0151] The preamble root index refers to the index used to generate the preamble sequence. The preamble length refers to the length of the preamble sequence. For example, the preamble length can be 839, 139, 1151, or 571. The cyclic shift offset refers to the offset value of the cyclic shift of the preamble. The constraint set refers to the set used to restrict the available cyclic shifts; restricting the available cyclic shift offsets can be used to combat frequency offsets, and can be divided into Type A and Type B types, for example. The cyclic prefix length refers to the length of the cyclic prefix sequence of the preamble. Preamble resources refer to the time-domain and / or frequency-domain resources used to carry the preamble, also known as PRACH resources. For example, the preamble resource configuration includes one or more of the following: PRACH configuration period, the start symbol of the PRACH, the subframe number of the PRACH, the number of symbols occupied by the PRACH, etc. The zero-correlation region configuration is used to indicate the configuration of the cyclic shift offset of the preamble. The preamble sequence type refers to the sequence type of the preamble; for example, it can be a ZC sequence, an m sequence, or a Gold sequence. The type of the preamble sequence can also be other types, and this application does not limit this.
[0152] The preamble format refers to the format of the preamble code. The preamble format can be used to indicate random access configuration parameters such as preamble length, subcarrier spacing, restriction set, and cyclic prefix. The preamble format can also be used to indicate other random access parameters, but this application does not limit this.
[0153] For example, Table 1 below shows the preamble configuration parameters indicated by four preamble formats (format 0, format 1, format 2, and format 3, respectively).
[0154] Table 1
[0155] For example, Table 2 below shows the preamble configuration parameters indicated by nine preamble formats (format A1, format A2, format A3, format B1, format B2, format B3, format B4, format C0, and format C2, respectively).
[0156] Table 2
[0157] In Tables 1 and 2, L RA Indicates the preamble length, Δf RA N represents the subcarrier spacing. u This indicates the length of time the preamble occupies. This indicates the time-domain length of the cyclic prefix of the preamble. μ is used to represent different subcarrier spacing configurations, and κ equals 64.
[0158] For example, Table 3 below shows the preamble configuration parameters indicated by the random access configuration index:
[0159] Table 3
[0160] Where, n f The three elements, x, y, and y, are used together to determine the system frames occupied by the PRACH configuration period. The PRACH configuration period refers to the time interval between the start times of two PRACH resources, or the time interval between the end times of two PRACH resources. `mod` represents the modulo operation or remainder operation. For example, taking PRACH configuration index 15 as an example, with x = 2 and y = 1, then mod(n... f Since all odd numbers mod 2 = 1, therefore n fAny odd number can be used, indicating that the PRACH configuration period indicated by PRACH configuration index 16 is 2 frames long (20ms), and the starting position of each configuration period is an odd-numbered frame number. For example, taking PRACH configuration index 16 as an example, x = 1, y = 0, mod(n f x) = y, which is mod(n) f Since n(1) = 0, and any integer mod 1 equals 0, therefore n(1) = 0. f It can take any integer, which means that the PRACH configuration period indicated by PRACH configuration index 16 is 1 frame length (10ms).
[0161] Based on the above introduction regarding initial access, network devices can configure parameters for random access for terminals via broadcast SIB1. Terminals can then initiate random access based on the configuration parameters indicated by SIB1. However, since different terminals may have different communication environments, the parameters configured by the network device for random access may not be suitable for the terminal's current communication environment. Inappropriate random access parameters may degrade the terminal's random access performance.
[0162] To improve the random access performance of terminals, this application proposes a communication method that associates preamble configuration parameters with SSBs, allowing terminals to initiate random access based on this association. As shown in Figure 4, the communication method includes steps 401 to 403. This application does not limit the order in which steps 401 and 402 are executed. For example, step 401 may be executed before step 402; or step 402 may be executed before step 401; or steps 401 and 402 may be executed simultaneously.
[0163] The method shown in Figure 4 can be applied between a terminal-side device and a network-side device. The terminal-side device can be a terminal, or a processor, module, chip, chip system, or functional module implementing the method. The network-side device can be a network device, or a processor, module, chip, chip system, or functional module implementing the method. Figure 4 illustrates this using a terminal and network device as the executing entities as an example.
[0164] 401. The network device sends the first SSB.
[0165] Correspondingly, the terminal receives the first SSB.
[0166] In some possible implementations, network devices can periodically broadcast different Service Streaming Buses (SSBs) in different communication areas, and these SSBs can be distinguished by their indices. Different SSB indices represent SSBs with different beam directions, each used to cover and serve different areas. Correspondingly, when a terminal is located within the coverage area corresponding to a first SSB, it can receive that first SSB. Optionally, when a terminal is located in an overlapping area corresponding to the coverage areas of multiple SSBs, it can also receive multiple SSBs. For example, when a terminal is located in an overlapping area of the coverage areas corresponding to the first SSB and the second SSB, it can receive both the first and second SSBs.
[0167] 402. The network device sends first information, which indicates a first association.
[0168] Correspondingly, the terminal receives the first information. The first association includes at least one of the following:
[0169] (1) The association between the first preamble root index and the first SSB; or,
[0170] (2) The relationship between the first cyclic shift offset and the first SSB; or,
[0171] (3) The relationship between the length of the first preamble, the configuration of the first preamble resources, and the first SSB; or,
[0172] (4) The association between the first restricted set, the first zero-related region configuration, and the first SSB; or,
[0173] (5) The association between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the first SSB; or,
[0174] (6) The relationship between the length of the first cyclic prefix, the resource configuration of the first preamble, and the first SSB.
[0175] Optionally, the first association relationship can also be described as the association relationship between the first SSB and the first preamble configuration information. The first preamble configuration information includes at least one preamble configuration parameter. For example, the first preamble configuration information includes a first preamble root index; or, the first preamble configuration information includes a first cyclic shift offset; or, the first preamble configuration information includes a first preamble length and a first preamble resource configuration; or, the first preamble configuration information includes a first preamble sequence type, a first preamble length, a first preamble root index, a first cyclic shift offset, and a first preamble resource configuration; or, the first preamble configuration information includes a first cyclic prefix length and a first preamble resource configuration.
[0176] Optionally, the first association relationship can be any one or more of the association relationships described in (1) to (6) above and the association relationship between the first preamble configuration parameter and the first SSB. Alternatively, the first association relationship can also include the association relationship between other preamble configuration parameters and the first SSB. This application embodiment does not limit this.
[0177] In this embodiment, the SSB is associated with preamble configuration parameters, allowing the terminal to send a random access request based on the associated preamble configuration parameters. For example, this first association includes the association between the first SSB and the first preamble root index. The first information indicating the first association indicates that if the terminal initiates random access based on the first SSB, the terminal can send a random access request according to the first preamble root index associated with the first SSB. Optionally, this first information is carried on SIB1, or the first information is SIB1.
[0178] In some examples, "association" can be replaced with "correspondence" or "mapping." For example, "association relationship" can be replaced with "mapping relationship" or "correspondence relationship." As another example, the length of the first preamble associated with the first SSB can also be replaced with "the length of the first preamble corresponding to the first SSB," or "the length of the first preamble mapped from the first SSB."
[0179] In some possible implementations, the first information may also indicate multiple relationships. For example, the first information may also indicate a second relationship, which includes at least one of the following:
[0180] (1) The association between the second preamble root index and the second SSB; or,
[0181] (2) The relationship between the second cyclic shift offset and the second SSB; or,
[0182] (3) The relationship between the second preamble length, the second preamble resource configuration, and the second SSB; or,
[0183] (4) The association between the second restricted set, the second zero-related region configuration, and the second SSB; or,
[0184] (5) The relationship between the second preamble sequence type, the second preamble length, the second preamble root index, the second cyclic shift offset, the second preamble resource configuration, and the second SSB; or,
[0185] (6) The relationship between the second cyclic prefix length, the second preamble resource configuration and the second SSB.
[0186] Optionally, the second association can also be described as an association between the second SSB and the second preamble configuration information, whereby the second preamble configuration information includes at least one preamble configuration parameter. For example, the second preamble configuration information includes a second preamble root index; or, the second preamble configuration information includes a second cyclic shift offset; or, the second preamble configuration information includes a second preamble length and a second preamble resource configuration; or, the second preamble configuration information includes a second preamble sequence type, a second preamble length, a second preamble root index, a second cyclic shift offset, and a second preamble resource configuration; or, the second preamble configuration information includes a second cyclic prefix length and a second preamble resource configuration.
[0187] Optionally, the preamble configuration parameters associated with the first SSB and the second SSB are different. The preamble configuration parameters include at least one of the following: preamble root index, preamble length, cyclic shift offset, restriction set, cyclic prefix length, preamble resource configuration, zero correlation region configuration, or preamble sequence type.
[0188] The preamble configuration parameters associated with the first SSB and the second SSB are different, which can also be described as follows: the first SSB and the second SSB satisfy one or more of the following:
[0189] (1) The first preamble root index associated with the first SSB is different from the second preamble root index associated with the second SSB; or...
[0190] (2) The length of the first preamble associated with the first SSB is different from the length of the second preamble associated with the second SSB; or...
[0191] (3) The first cyclic shift offset associated with the first SSB is different from the second cyclic shift offset associated with the second SSB; or,
[0192] (4) The first restricted set associated with the first SSB is different from the second restricted set associated with the second SSB; or,
[0193] (5) The length of the first cycle prefix associated with the first SSB is different from the length of the second cycle prefix associated with the second SSB; or...
[0194] (6) The configuration of the first preamble resource associated with the first SSB is different from the configuration of the second preamble resource associated with the second SSB; or...
[0195] (7) The configuration of the first zero-related region associated with the first SSB is different from the configuration of the second zero-related region associated with the second SSB; or...
[0196] (8) The first preamble sequence type associated with the first SSB is different from the second preamble sequence type associated with the second SSB.
[0197] Alternatively, the preamble configuration parameters associated with the first SSB and the second SSB are different. This can also be described as the first preamble configuration information associated with the first SSB being different from the second preamble configuration information associated with the second SSB. The difference between the first and second preamble configuration information means that at least one of the preamble configuration parameters has a different value. In other words, the difference between the first and second preamble configuration information can include two cases: all or some of the preamble configuration parameters in the first and second preamble configuration information have different values.
[0198] For example, assume that the first preamble configuration information includes a first cyclic prefix length and a first preamble resource configuration, and the second preamble configuration information includes a second cyclic prefix length and a second preamble resource configuration. Where the values of some preamble configuration parameters differ between the first and second preamble configuration information, it means that the first and second preamble resource configurations are different, but the first and second cyclic prefix lengths are the same; or, the first and second preamble resource configurations are the same, but the first and second cyclic prefix lengths are different. Where the values of all preamble configuration parameters differ between the first and second preamble configuration information, it means that the first and second preamble resource configurations are different, and the first and second cyclic prefix lengths are also different.
[0199] Optionally, the first information can also be used to indicate the preamble format associated with the SSB. In some examples, the first information indicates the same preamble format associated with the first and second SSBs, meaning that the terminal uses the same preamble format when initiating random access based on either the first or second SSB. Alternatively, the first information indicates a preamble format that is not associated with any SSB, and the terminal uses the preamble format indicated by the first information to send the random access request when initiating random access based on any SSB.
[0200] Optionally, the network device sends a second SSB, and the corresponding terminal receives the second SSB. The network device can configure different preamble configuration parameters for the first and second SSBs to adapt to different communication environments, improve the terminal's random access performance, and thus increase the success rate of random access. For example, in areas with poor communication environment and low communication quality at the cell edge, the SSB used to cover the cell edge can be associated with a longer preamble length, a longer cyclic prefix, a lower peak-to-average power ratio (PAPR), a lower cubic metric preamble root index, or a larger cyclic shift offset to ensure the terminal's random access performance. Conversely, in areas with better communication environment and higher communication quality at the cell center, the SSB used to cover the cell center can be associated with a shorter preamble length, a shorter cyclic prefix, a higher PAPR, a higher cubic metric preamble root index, or a smaller cyclic shift offset to improve the terminal's access latency.
[0201] In some possible implementations, the network devices used to transmit the first SSB and the network devices used to transmit the second SSB are different; optionally, the network device is a transmission point. Exemplarily, embodiments of this application can be applied to user-centric and no-cell (UCNC) scenarios. UCNC refers to a user-centric network that provides user-centric wireless communication services, weakening cell boundaries so that the terminal is unaware of cell edges, thereby enabling the terminal to obtain a high-speed and low-latency experience. In a UCNC scenario, multiple network devices can be simultaneously activated to provide services to the terminal, and these multiple network devices use the same cell identifier.
[0202] Optionally, the network device that sends the first SSB is referred to as the first network device, and the network device that sends the second SSB is referred to as the second network device. The coverage areas or coverage ranges of the first network device and the second network device are different. By configuring different preamble configuration information for the first SSB and the second SSB, it is beneficial to improve the random access performance of the terminal in different communication environments.
[0203] Further optionally, the first network device is an anchor network device, or may also be referred to as an anchor transmission point (Anchor TRP), and the second network device is a capacity network device, or may also be referred to as a capacity transmission point (Capacity TRP). Alternatively, the second network device is an anchor network device, and the first network device is a capacity network device.
[0204] In some examples, anchor network devices and capacity network devices meet one or more of the following criteria:
[0205] (1) The coverage area of the anchor network device is greater than that of the capacity network device; or...
[0206] (2) Anchor network devices are used to provide network coverage, while capacity network devices are used to provide data transmission; or...
[0207] (3) The communication frequency of anchor network devices is lower than that of capacity network devices.
[0208] For example, as shown in Figure 5, the anchor network device sends SSB0 to SSB4, and the capacity network device sends SSB5 and SSB6. The preamble length associated with SSB0 to SSB4 can be configured to be greater than the preamble length associated with SSB5 and SSB6; alternatively, the PAPR corresponding to the root index of the preamble associated with SSB0 to SSB4 can be configured to be less than the PAPR corresponding to the root index of the preamble associated with SSB5 and SSB6. This allows SSB0 to SSB4 sent by the anchor network device to provide better coverage, and SSB5 and SSB6 sent by the capacity network device to provide stronger penetration capability.
[0209] Optionally, the network device transmitting the SSB can be characterized by a first parameter. For example, the first parameter of the second SSB differs from that of the first SSB, thus indicating a difference between the second and first network devices. The first parameter includes one or more of the following: SSB transmit power, SSB target receive power, or SSB beamforming gain.
[0210] The fact that the first parameter of the second SSB is different from the first parameter of the first SSB means that the transmit power of the second SSB is different from that of the first SSB, and / or the target receive power of the second SSB is different from that of the first SSB, and / or the beamforming gain of the second SSB is different from that of the first SSB.
[0211] Further optionally, the first parameter of the second SSB is different from the first parameter of the first SSB. This can be understood as the first parameter of the first network device being different from the first parameter of the second network device. For example, the SSB transmit power of the first network device is different from the SSB transmit power of the second network device; or, the SSB target receive power of the first network device is different from the SSB target receive power of the second network device; or, the beamforming gain of the SSB of the first network device is different from the beamforming gain of the SSB of the second network device.
[0212] SSB transmit power refers to the power at which a network device transmits an SSB; SSB target receive power refers to the power at which the network device expects the terminal to receive the SSB; SSB beamforming gain refers to the gain obtained in a specific direction by appropriately beamforming the SSB transmitted by the antenna. Beamforming refers to adjusting the weighting coefficients of each element in the antenna array to generate a directional beam, thereby obtaining significant array gain.
[0213] In some possible implementations, the SSB can be indicated by the index of the SSB. For example, the first association indicated by the first information includes the association between the first preamble root index and the first SSB, or it can be described as the association between the index of the first preamble root index and the index of the first SSB.
[0214] In some possible implementations, when the first information indicates the association between the SSB and the preamble configuration parameters, it can be indicated by a table, enumeration, or bitmap, etc., and the embodiments of this application do not limit this.
[0215] Optionally, the first information may indicate, individually or in combination, the association between the SSB and each preamble configuration parameter.
[0216] Individual indication refers to indicating the association relationship of each preamble configuration parameter SSB separately. Taking the first association relationship, which includes the association relationship between the first preamble length, the first preamble resource configuration, and the first SSB, as an example, individual indication means that the first information can indicate the association relationship between the first preamble length and the first SSB, as well as the association relationship between the first preamble resource configuration and the first SSB, respectively.
[0217] For example, taking the method of individually indicating by enumeration as an example, it can be represented as follows: {SSB0: preamble length 839, SSB1: preamble length 839, SSB2: preamble length 139}, {SSB0: time-frequency resource 0, SSB1: time-frequency resource 1, SSB2: time-frequency resource 2}. Alternatively, taking the method of individually indicating by table as an example, as shown in Tables 4A and 4B, according to the above examples, we can obtain that the preamble length associated with SSB at index 0 is 839, and the preamble resource associated with SSB at index 0 is time-frequency resource 0; the preamble length associated with SSB at index 1 is 839, and the preamble resource associated with SSB at index 1 is time-frequency resource 1; the preamble length associated with SSB at index 2 is 139, and the preamble resource associated with SSB at index 2 is time-frequency resource 2.
[0218] Table 4A
[0219] Table 4B
[0220] The above examples are merely illustrations. This method of individual indication can also be applied to scenarios where SSB is associated with any of the preamble configuration parameters described above in the embodiments of this application. The embodiments of this application do not limit this.
[0221] Association indication refers to indicating the association relationship between multiple preamble configuration parameters and the SSB. Taking the first association relationship, which includes the first preamble sequence type, first preamble length, first preamble root index, first cyclic shift offset, first preamble resource configuration, and first SSB, as an example, the first information can simultaneously indicate the association relationship between the first SSB and the first preamble sequence type, first preamble length, first preamble root index, first cyclic shift offset, and first preamble resource configuration.
[0222] Taking the association of indicators via a table as an example, as shown in Table 5, we can see that the SSB with index 0 is associated with a ZC sequence type, a preamble length of 839, a preamble root index of 0, a cyclic shift offset of 0, and a preamble resource configuration of 0 time-frequency resources. The SSB with index 1 is associated with an m-sequence type, a preamble length of 839, a preamble root index of 1, a cyclic shift offset of 1, and a preamble resource configuration of 1 time-frequency resource.
[0223] Table 5
[0224] In some possible implementations, the association between the SSB and the preamble configuration information can be one-to-one, one-to-many, many-to-one, or many-to-many. The following section describes these one-to-one, one-to-many, many-to-one, or many-to-many correspondences:
[0225] The one-to-one correspondence between SSB and preamble configuration information means that one SSB is associated with one preamble configuration information. In other words, the preamble configuration information includes at least one preamble configuration parameter, and the first SSB corresponds one-to-one with each of the at least one preamble configuration parameters.
[0226] For example, the first information indicates a first association. The first association is the association between the first SSB and the first preamble configuration information. The first SSB has no association with any other preamble configuration information besides the first preamble configuration information.
[0227] For example, assuming the preamble configuration information includes the preamble root index, Table 6A illustrates that the SSB and the preamble configuration information have a one-to-one correspondence, that is, the SSB and the preamble root index have a one-to-one correspondence. In this case, the SSB with index x1 is associated with the preamble root index y1, and the SSB with index x2 is associated with the preamble root index y2.
[0228] Table 6A
[0229] For example, suppose the preamble configuration information includes the preamble length and preamble resource configuration. Table 6B illustrates a one-to-one correspondence between SSBs and preamble configuration information, that is, a one-to-one correspondence between SSBs and preamble lengths, and a one-to-one correspondence between SSBs and preamble resource configurations. The SSB with index x1 is associated with the preamble length w1, and the SSB with index x1 is associated with the preamble resource configuration z1; the SSB with index x2 is associated with the preamble length w2, and the SSB with index x2 is associated with the preamble resource configuration z2.
[0230] Table 6B
[0231] II. A one-to-many correspondence between an SSB and preamble configuration information means that one SSB is associated with multiple preamble configuration information pieces, where any two of these preamble configuration information pieces are different. For example, the first information indicates a first association relationship, and the first information also indicates a third association relationship, wherein the third association relationship includes at least one of the following:
[0232] (1) The association between the root index of the third preamble and the first SSB; or,
[0233] (2) The relationship between the third cyclic shift offset and the first SSB; or,
[0234] (3) The relationship between the length of the third preamble, the resource configuration of the third preamble, and the first SSB; or,
[0235] (4) The association between the third restricted set, the third zero-related region configuration, and the first SSB; or,
[0236] (5) The relationship between the third preamble sequence type, third preamble length, third preamble root index, third cyclic shift offset, third preamble resource configuration, and the first SSB; or,
[0237] (6) The relationship between the length of the third cyclic prefix, the resource configuration of the third preamble, and the first SSB.
[0238] Optionally, the third association can also be described as the association between the first SSB and the third preamble configuration information. The third preamble configuration information includes at least one preamble configuration parameter. For example, the third preamble configuration information includes a third preamble root index; or, the third preamble configuration information includes a third cyclic shift offset; or, the third preamble configuration information includes a third preamble length and a third preamble resource configuration; or, the third preamble configuration information includes a third preamble sequence type, a third preamble length, a third preamble root index, a third cyclic shift offset, and a third preamble resource configuration; or, the third preamble configuration information includes a third cyclic prefix length and a third preamble resource configuration.
[0239] Based on the above implementation method, one SSB can be associated with multiple different preamble configuration information. The terminal can selectively choose the appropriate SSB associated with the preamble configuration information for random access, which is beneficial to improving random access performance.
[0240] Further optionally, the first SSB corresponds to the first association and the third association, and the first information indicates the first association group, which includes the first association and the third association.
[0241] Alternatively, it can be described that multiple preamble configuration information associated with an SSB can be grouped into a preamble configuration information group. For example, an SSB is associated with a preamble configuration information group, and the preamble configuration information group includes multiple preamble configuration information, with different preamble configuration information included in the group. For instance, the first information indicates a first association group, which includes the association between the first SSB and the first preamble configuration information group, and the first preamble configuration information group includes first preamble configuration information and third preamble configuration information.
[0242] For example, assuming the preamble configuration information includes the preamble root index, Table 7A illustrates a one-to-many relationship between the SSB and the preamble configuration information, i.e., a one-to-many relationship between the SSB and the preamble root index. Specifically, the SSB with index x1 is associated with the preamble root index y1, the preamble root index y2, ..., the preamble root index y... n Any preamble root index is interconnected.
[0243] Table 7A
[0244] For example, suppose the preamble configuration information includes the preamble length and preamble resource configuration. Table 7B illustrates a one-to-many relationship between the SSB and the preamble configuration information, that is, a one-to-many relationship between the SSB and the preamble length, and a one-to-many relationship between the SSB and the preamble resource configuration. Specifically, the SSB with index x1 is associated with preamble lengths w1, w2, ... w... n The preamble lengths are correlated with each other, and the SSB at index x1 is correlated with the preamble resource configurations z1, z2, ..., z1. n Any preamble resource configuration is interconnected.
[0245] Table 7B
[0246] Third, the many-to-one correspondence between SSBs and preamble configuration information means that multiple SSBs are associated with one preamble configuration information, and any two SSBs among these multiple SSBs are different. For example, the first information indicates a first association relationship, and the first information also indicates a fourth association relationship, wherein the fourth association relationship includes at least one of the following:
[0247] (1) The association between the first preamble root index and the third SSB; or,
[0248] (2) The relationship between the first cyclic shift offset and the third SSB; or,
[0249] (3) The relationship between the length of the first preamble, the resource configuration of the first preamble, and the third SSB; or,
[0250] (4) The association between the first restricted set, the first zero-related region configuration, and the third SSB; or,
[0251] (5) The association between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the third SSB; or,
[0252] (6) The relationship between the length of the first cyclic prefix, the resource configuration of the first preamble, and the third SSB.
[0253] Optionally, the third association relationship can also be described as the association relationship between the third SSB and the first preamble configuration information. The definition of the first preamble configuration information can be found in the foregoing description and will not be repeated here.
[0254] Based on the above implementation method, one preamble configuration information can be associated with multiple SSBs. SSBs with the same requirements can be merged and associated with one preamble configuration information, reducing overhead.
[0255] Further optionally, the first preamble configuration information corresponds to the first association relationship and the fourth association relationship, the first information indicates the second association relationship group, and the first association relationship group includes the first association relationship and the fourth association relationship.
[0256] Alternatively, it can be described that multiple SSBs associated with a preamble configuration information can form an SSB group. For example, a preamble configuration information is associated with an SSB group, and an SSB group includes multiple SSBs, with different SSBs included in the group. For instance, the first information indicates a second association group, which includes the association between the first preamble configuration information and the first SSB group, and the first SSB group includes a first SSB and a third SSB.
[0257] For example, assuming the preamble configuration information includes the preamble root index, Table 8A illustrates a many-to-one relationship between the SSB and the preamble configuration information, i.e., a many-to-one relationship between the SSB and the preamble root index, where the indexes are x1, x2, ... x n Any SSB in the sequence is associated with the preamble root index y1, with index x. n+1 x n+2 , ...x m The SSB of any one of them is associated with the preamble root index y1.
[0258] Table 8A
[0259] For example, suppose the preamble configuration information includes the preamble length and preamble resource configuration. Table 8B illustrates a many-to-one relationship between the SSB and the preamble configuration information, that is, a many-to-one relationship between the SSB and the preamble length, and a many-to-one relationship between the SSB and the preamble resource configuration. The indices are x1, x2, ... x n Any SSB in the sequence is correlated with the preamble length w1, and the indices are x1, x2, ... x n Each of the SSBs is associated with the preamble resource configuration z1. The index is x. n+1 x n+2 , ...x m The SSB of any one of them is correlated with the preamble length w2, and the index is x. n+1 x n+2 , ...x m Any one of the SSBs is associated with the preamble resource configuration z2.
[0260] Table 8B
[0261] IV. The many-to-many correspondence between SSBs and preamble configuration information means that multiple SSBs are associated with multiple preamble configuration information. For example, the first information indicates a first association, and the first information also indicates a third, fourth, and fifth association. The definitions of the third and fourth associations can be found in the above description and will not be repeated here. The fifth association includes at least one of the following:
[0262] (1) The association between the root index of the third preamble and the third SSB; or,
[0263] (2) The relationship between the third cyclic shift offset and the third SSB; or,
[0264] (3) The relationship between the length of the third preamble, the resource configuration of the third preamble, and the third SSB; or,
[0265] (4) The relationship between the third restricted set, the third zero-related region configuration, and the third SSB; or,
[0266] (5) The relationship between the third preamble sequence type, third preamble length, third preamble root index, third cyclic shift offset, third preamble resource configuration, and the third SSB; or,
[0267] (6) The relationship between the length of the third cyclic prefix, the resource configuration of the third preamble, and the third SSB.
[0268] Optionally, the fifth association can also be described as the association between the third SSB and the third preamble configuration information. The definition of the third preamble configuration information can be found in the foregoing description and will not be repeated here.
[0269] Alternatively, it can be described as follows: the first information indicates the association between the first SSB and the first preamble configuration information, and the association between the first SSB and the third preamble configuration information. The first information also indicates the association between the third SSB and the first preamble configuration information, and the association between the third SSB and the third preamble configuration information. That is, both the first SSB and the third SSB are associated with the first preamble configuration information and the third preamble configuration information.
[0270] Based on this implementation method, multiple SSBs can be associated with multiple different preamble configuration information. This not only allows SSBs with the same requirements to be merged and associated, but also allows the terminal to selectively choose appropriate preamble configuration information for random access, which helps to improve random access performance.
[0271] Optionally, a preamble configuration information group can be associated with an SSB group; that is, multiple preamble configuration information groups associated with an SSB group can form a preamble configuration information group, and multiple SSBs associated with a preamble configuration information group can form an SSB group. An SSB group includes multiple SSBs, and the SSBs included in an SSB group are different. For example, the first information indicates a third association group, which includes the association relationship between the first preamble configuration information group and the first SSB group. The first SSB group includes a first SSB and a third SSB, and the first preamble configuration information group includes first preamble configuration information and third preamble configuration information.
[0272] For example, assuming the preamble configuration information includes the preamble root index, Table 9A illustrates a many-to-many relationship between the SSB and the preamble configuration information, i.e., a many-to-many relationship between the SSB and the preamble root index, where the indexes are x1, x2, ... x n The SSB of any one of them is related to the preamble root index y1, preamble root index y2, ..., preamble root index y n The preamble root indices of any one of them are interconnected.
[0273] Table 9A
[0274] For example, suppose the preamble configuration information includes the preamble length and preamble resource configuration. Table 9B illustrates a many-to-many relationship between the SSB and the preamble configuration information, that is, a many-to-many correspondence between the SSB and the preamble length, and a many-to-many relationship between the SSB and the preamble resource configuration. The indices are x1, x2, ... x i The SSB of any one of them is related to the preamble length w1, preamble length w2, ..., preamble length w j The lengths of the preambles in each of the substrings are correlated. The indices are x1, x2, ... x n Any SSB and preamble resource configuration z1, preamble resource configuration z2, ... preamble resource configuration z k The preamble resource configurations of any one of them are interconnected.
[0275] Table 9B
[0276] The first information can indicate at least one set of association relationships between SSBs and preamble configuration information. Each of these association relationships is a one-to-one, one-to-many, many-to-one, or many-to-many correspondence. For example, taking a one-to-one correspondence between each SSB and preamble configuration information as an example, the first information could indicate three sets of association relationships between SSBs and preamble configuration information: the first SSB is associated with the first preamble configuration information, the second SSB is associated with the second preamble configuration information, and the third SSB is associated with the third preamble configuration information.
[0277] Alternatively, the first information can indicate the association relationships between multiple sets of SSBs and preamble configuration information, where at least two sets have different correspondences. For example, one set of SSBs and preamble configuration information has a one-to-many correspondence, while the other set has a one-to-one correspondence. For instance, the first information indicates the association relationships between two sets of SSBs and preamble configuration information: one set of SSBs and preamble configuration information is associated with the first SSB, the first preamble configuration information, and the third preamble configuration information (a one-to-many relationship); the other set of SSBs and preamble configuration information is associated with the second SSB and the second preamble configuration information (a one-to-one relationship).
[0278] 403. The terminal sends a random access request based on the first association relationship.
[0279] Correspondingly, the network device receives random access requests from the terminal.
[0280] For example, when the first association indicated by the first information includes the association between the first preamble root index and the first SSB, the terminal can initiate random access based on the first preamble root index associated with the first SSB.
[0281] For example, when the first association indicated by the first information includes the association between the first cyclic shift offset and the first SSB, the terminal can send a random access request based on the first cyclic shift offset associated with the first SSB.
[0282] For another example, when the first association indicated by the first information includes the association between the first preamble length, the first preamble resource configuration and the first SSB, the terminal sends a random access request based on the first preamble length associated with the first SSB and the first preamble resource configuration.
[0283] For another example, when the first association indicated by the first information includes the association between the first restriction set, the first zero-related area configuration, and the first SSB, the terminal can send a random access request based on the first restriction set associated with the first SSB and the first zero-related area configuration.
[0284] For example, when the first association indicated by the first information includes the association between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the first SSB, the terminal can send a random access request based on the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, and the first preamble resource configuration associated with the first SSB.
[0285] For another example, when the first association indicated by the first information includes the association between the first cyclic prefix length, the first preamble resource configuration and the first SSB, the terminal can send a random access request based on the first cyclic prefix length associated with the first SSB and the first preamble resource configuration.
[0286] Optionally, the random access request may refer to Msg1 in a four-step random access procedure, carrying a preamble; or, the random access request may refer to MsgA in a two-step random access procedure, carrying data and a preamble. This application embodiment does not limit this.
[0287] Based on this implementation, network devices can associate appropriate preamble configuration parameters with the first SSB according to the coverage area corresponding to the first SSB, thereby adapting to the communication environment of terminals within the coverage area of the first SSB, thus improving the random access performance of terminals and increasing the success rate of random access.
[0288] In some possible implementations, the terminal can receive one or more SSBs. An SSB can be associated with one or more preamble configuration information. The preamble configuration information includes at least one configuration parameter. The terminal can select a suitable SSB based on one or more of the received SSB information, its own capabilities, and its own needs, and select the preamble configuration parameter included in the preamble configuration information associated with the SSB, and send a random access request.
[0289] In some examples, the terminal receives an SSB, such as the first SSB. When the first information only indicates the first association, the first association is the association between the first SSB and the associated first preamble configuration information. In this case, the terminal can send a random access request based on the preamble configuration parameters included in the first preamble configuration information.
[0290] When the first information indicates multiple associations corresponding to the first SSB, for example, when the first information indicates a first association and a third association, the first association is the association between the first SSB and the first preamble configuration information, and the third association is the association between the first SSB and the third preamble configuration information. When the first SSB is associated with multiple preamble configuration information, the terminal can select the appropriate preamble configuration information according to its own needs.
[0291] For example, the first SSB is associated with first preamble configuration information and third preamble configuration information, and the terminal can select between the first preamble configuration information and the third preamble configuration information according to its own needs. Optionally, the own needs may include one or more of the following: the area where the terminal is located, the mobility (or speed) of the terminal, or the terminal access latency requirements.
[0292] For example, the length of the first preamble in the first preamble configuration information is longer than the length of the third preamble in the third preamble configuration information, and / or, the length of the first cyclic prefix in the first preamble configuration information is longer than the length of the third cyclic prefix in the third preamble configuration information, and / or, the PAPR of the first preamble root index in the first preamble configuration information is smaller than the PAPR of the third preamble root index in the third preamble configuration information, and / or, the length of the first cyclic shift offset in the first preamble configuration information is larger than the length of the third cyclic shift offset in the third preamble configuration information. If the terminal is located at the cell edge, or is in a fast-moving state, or the terminal has low latency requirements, the terminal may preferentially select the first preamble configuration information and send a random access request based on the preamble configuration parameters included in the first preamble configuration information to obtain better network coverage. For example, when the terminal is located in the center of the cell, or is in a low-speed moving state, or when the terminal has high latency requirements, the terminal can prioritize the third preamble configuration information and send a random access request based on the preamble configuration parameters included in the third preamble configuration information to reduce random access latency.
[0293] For example, the first SSB is associated with first preamble configuration information and third preamble configuration information. The terminal can choose between the first preamble configuration information and the third preamble configuration information based on its own capabilities. Optionally, this self-requirement may include the preamble sequence types supported by the terminal. The terminal can select the preamble configuration information corresponding to the optimal preamble sequence type based on the preamble sequence types it supports.
[0294] In some examples, a terminal can receive multiple SSBs and select one of them to send a random access request. For example, if a terminal receives a first SSB and a second SSB, it can select one of the first and second SSBs to send a random access request.
[0295] Optionally, the terminal can select one SSB from multiple SSBs based on the SSB's reference signal receiving power (RSRP) to send a random access request. More optionally, the terminal can select the SSB with the highest RSRP from the multiple SSBs to send a random access request, or the terminal can send a random access request from one SSB among those with an RSRP higher than a preset value. For example, if the terminal receives a first SSB and a second SSB, and the RSRP of the first SSB is higher than that of the second SSB, the terminal can select the first SSB to send the random access request.
[0296] Furthermore, the terminal selects one SSB from multiple SSBs, determines a preamble configuration based on one or more preamble configurations associated with the selected SSB, and sends a random access request based on the preamble configuration parameters included in the selected preamble configuration. For example, assuming the terminal selects the first SSB, and the first information indicates that the first SSB is associated with only one preamble configuration, such as the first SSB being associated with the first preamble configuration, then the terminal can send a random access request based on the preamble configuration parameters included in the first preamble configuration. If the first information indicates that the first SSB is associated with multiple preamble configurations, the terminal can select the appropriate preamble configuration according to its own needs. This implementation method can be seen in the example above and will not be repeated here.
[0297] Optionally, when a terminal needs to select one preamble configuration from multiple preamble configurations to send a random access request based on its own needs, the terminal can make a judgment based on the association between its needs and the preamble configuration. This association between the terminal's needs and the preamble configuration can be a default, a protocol-defined relationship, a relationship determined by the terminal itself, a relationship configured by the network device, or a relationship negotiated between the terminal and the network device. This embodiment does not limit this aspect.
[0298] For example, terminal requirements include mobility, and preamble configuration information includes preamble length. The relationship between mobility and preamble configuration information is shown in Table 10:
[0299] Table 10
[0300] Here, "low mobility" can refer to the terminal's moving speed being less than a first threshold, while "high mobility" can refer to the terminal's moving speed being greater than or equal to the first threshold. Alternatively, "low mobility" can refer to the terminal's moving speed being less than or equal to the first threshold, while "high mobility" can refer to the terminal's moving speed being greater than the first threshold. The terminal can select an appropriate SSB and preamble configuration information based on its own mobility. For example, if the terminal has low mobility, it can send a random access request based on the preamble configuration parameters included in the preamble configuration information associated with the SSB at index 0, namely, a preamble sequence type of ZC sequence, a preamble length of 839, a preamble root index of 0, a cyclic shift offset of 0, and a time domain resource of 0.
[0301] In some possible implementations, the first information also indicates the association between the first SSB and the first RO, with the random access request sent by the terminal being transmitted on the first RO. For example, the first information is SIB1, and the "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" field in SIB1 can indicate the association between the SSB and RO, including the association between the first SSB and the first RO. Furthermore, the "ssb-perRACH-OccasionAndCB-PreamblesPerSSB" field can also indicate the number of ROs corresponding to the SSB, and the corresponding number of contention-based preambles. The association between the SSB and RO can be a one-to-many or many-to-one correspondence.
[0302] Optionally, as shown in Figure 6, the RO associated with the preamble configuration information can be set to be the RO associated with the SSB corresponding to the preamble configuration information, thereby reducing crosstalk. For example, the first SSB is associated with the first RO, and the RO associated with the first preamble configuration information is the first RO. Further optionally, the association relationship between the preamble configuration information and the RO can be a one-to-one, one-to-many, many-to-one, or many-to-many correspondence.
[0303] In some examples, the association between preamble configuration information and RO is one-to-one, meaning that one preamble configuration piece of information is associated with one RO. Alternatively, one preamble configuration piece of information can be associated with one or more SSBs, and when one or more SSBs are associated with one RO, one preamble configuration piece of information is associated with one RO.
[0304] For example, the first SSB is associated with the first preamble configuration information, the second SSB is associated with the second preamble configuration information, and the first SSB is associated with the first RO, while the second SSB is associated with the second RO. Therefore, the first preamble configuration information is associated with the first RO, and the second preamble configuration information is associated with the second RO.
[0305] For example, as shown in Figure 7A, SSB group 1 includes SSB 0 and SSB 1, SSB group 2 includes SSB 2 and SSB 3, RO1 is associated with SSB group 1, SSB group 1 is associated with preamble configuration information 1, and correspondingly, preamble configuration information 1 is associated with RO1. RO2 is associated with SSB group 2, SSB group 2 is associated with preamble configuration information 2, and correspondingly, preamble configuration information 2 is associated with RO2.
[0306] In some examples, the association between preamble configuration information and ROs is a one-to-many correspondence, meaning that one preamble configuration piece of information is associated with multiple ROs. Alternatively, one preamble configuration piece of information can be associated with one or more SSBs, and when those one or more SSBs are associated with multiple ROs, then one preamble configuration piece of information is associated with multiple ROs.
[0307] For example, the first SSB is associated with the first preamble configuration information, and the first SSB is associated with the first RO and the third RO. Therefore, the first preamble configuration information is associated with the first RO and the third RO.
[0308] For example, as shown in Figure 7B, SSB group 1 includes SSB 0 and SSB 1, SSB group 2 includes SSB 2 and SSB 3, SSB group 3 includes SSB 4 and SSB 5, and SSB group 4 includes SSB 6 and SSB 7. RO1 is associated with SSB group 1, RO2 is associated with SSB group 2, and SSB group 1 and SSB group 2 are associated with preamble configuration information 1. Therefore, preamble configuration information 1 is associated with RO1 and RO2. RO3 is associated with SSB group 3, RO4 is associated with SSB group 4, and SSB group 3 and SSB group 4 are associated with preamble configuration information 2. Therefore, preamble configuration information 2 is associated with RO3 and RO4.
[0309] In some examples, the association between preamble configuration information and RO is a many-to-one correspondence, meaning that multiple preamble configuration information pieces are associated with one RO. Alternatively, multiple preamble configuration information pieces can be associated with one or more SSBs, and when those one or more SSBs are associated with one RO, then the multiple preamble configuration information pieces are associated with one RO.
[0310] For example, if the first SSB is associated with the first preamble configuration information, the second SSB is associated with the second preamble configuration information, and the first SSB and the second SSB are associated with the first RO, then the first preamble configuration information and the second preamble configuration information are associated with the first RO.
[0311] For example, as shown in Figure 7C, SSB group 1 includes SSB 0 and SSB 1, SSB group 2 includes SSB 2 and SSB 3, RO1 is associated with SSB group 1 and SSB group 2, SSB group 1 is associated with preamble configuration information 1, and SSB group 2 is associated with preamble configuration information 2. Therefore, preamble configuration information 1 and preamble configuration information 2 are associated with RO1.
[0312] In some examples, the association between preamble configuration information and ROs is a many-to-many correspondence, meaning that multiple preamble configuration information pieces are associated with multiple ROs. Alternatively, multiple preamble configuration information pieces can be associated with one or more SSBs, and when those one or more SSBs are associated with multiple ROs, the multiple preamble configuration information pieces are associated with those multiple ROs.
[0313] For example, if the first SSB is associated with the first preamble configuration information, the second SSB is associated with the second preamble configuration information, and the first SSB and the second SSB are associated with the first RO and the second RO, then the first preamble configuration information and the second preamble configuration information are associated with the first RO and the second RO.
[0314] For example, as shown in Figure 7D, SSB group 1 includes SSB 0 and SSB 1, SSB group 2 includes SSB 2 and SSB 3, RO1 and RO2 are associated with SSB group 1 and SSB group 2, SSB group 1 is associated with preamble configuration information 1, and SSB group 2 is associated with preamble configuration information 2. Therefore, preamble configuration information 1 and preamble configuration information 2 are associated with RO1 and RO2.
[0315] The following describes the communication device provided in the embodiments of this application.
[0316] This application divides the communication device into functional modules according to the above method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The communication device of the embodiments of this application will be described in detail below with reference to Figures 8 to 10.
[0317] Figure 8 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 8, the communication device includes a processing module 801 and a communication module 802. The communication module 802 can implement corresponding communication functions, and the processing module 801 is used to implement corresponding processing functions. For example, the communication module 802 can also be an interface, a communication interface, etc.
[0318] In this embodiment, the communication device can be used to perform the actions performed by the terminal-side device in the above method embodiment. In this case, the terminal-side device can be the terminal-side device itself or a chip or functional module configurable within the terminal-side device. The communication module 802 is used to perform the transmit / receive related operations of the terminal-side device in the above method embodiment, and the processing module 801 is used to perform the processing related operations of the terminal-side device in the above method embodiment.
[0319] In some embodiments, the communication module 802 is configured to receive a first SSB; the communication module 802 is also configured to receive first information indicating a first association; the communication module 802 is also configured to send a random access request based on the first association.
[0320] In this embodiment, the communication device can be used to perform the actions performed by the network-side device in the above method embodiment. In this case, the network-side device can be the network-side device itself or a chip or functional module configurable within the network-side device. The communication module 802 is used to perform the transmit / receive related operations of the network-side device in the above method embodiment, and the processing module 801 is used to perform the processing related operations of the network-side device in the above method embodiment.
[0321] In some embodiments, the communication module 802 is configured to send a first SSB; the communication module 802 is also configured to send first information indicating a first association relationship.
[0322] Optionally, in the above embodiments, the communication device may further include a storage module, which can be used to store instructions and / or data. The processing module 801 can read the instructions and / or data in the storage module so that the communication device can implement the aforementioned method embodiments.
[0323] The specific descriptions of the communication module and the processing module are merely examples. For the specific functions or execution steps of the communication module and the processing module, please refer to the above method embodiments, which will not be detailed here.
[0324] The communication device of the present application embodiments has been described above. The following describes possible product forms of the communication device. Any product possessing the functions of the communication device described in FIG8 above falls within the protection scope of the present application embodiments. The following description is merely illustrative and does not limit the product form of the communication device of the present application embodiments to this.
[0325] In one possible implementation, in the communication device shown in FIG8, the processing module 801 can be one or more processing circuits, and the communication module 802 can be a communication circuit. Alternatively, the communication module 802 can also be a transmitting module and / or a receiving module. The transmitting module can be a transmitting circuit, and the receiving module can be a receiving circuit. The transmitting module and the receiving module are integrated into one device, such as a communication circuit. In the embodiments of this application, the processing circuit and the communication circuit can be coupled, etc. The connection method of the processing circuit and the communication circuit is not limited in the embodiments of this application. In the process of performing the above method, the process of sending information in the above method can be the process of the processing circuit outputting the above information. When outputting the above information, the processing circuit outputs the above information to the communication circuit so that the communication circuit can transmit (or output). After the above information is output by the processing circuit, it may need to undergo other processing before reaching the communication circuit. Similarly, the process of receiving information in the above method can be the process of the processing circuit receiving the input above information. When the processing circuit receives the input information, the communication circuit receives the above information and inputs it into the processing circuit. Furthermore, after the communication circuit receives the aforementioned information, the information may need to undergo further processing before being input into the processing circuit.
[0326] Figure 9 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 9, the communication device 90 includes one or more processing circuits 920 and communication circuits 910.
[0327] In some embodiments of this application, the communication device can be used to execute the steps, methods, or functions performed by the terminal-side device described above. For example, the processing circuit 920 can be used to execute the functions or steps implemented by the processing module 801 shown in FIG8, and the communication circuit 910 can be used to execute the functions or steps implemented by the communication module 802 shown in FIG8. For a detailed description of the processing circuit 920 and the communication circuit 910, please refer to FIG8 or the method embodiments shown above, which will not be described in detail here.
[0328] In other embodiments of this application, the communication device is used to perform the steps, methods, or functions performed by the network-side device described above. For example, the processing circuit 920 can be used to perform the functions or steps implemented by the processing module 801 shown in FIG. 8, and the communication circuit 910 can be used to perform the functions or steps implemented by the communication module 802 shown in FIG. 8. Detailed descriptions of the processing circuit 920 and the communication circuit 910 can be found in FIG. 8 or the method embodiments shown above, and will not be elaborated further here.
[0329] For example, the processing circuitry may be one or more processors, or all or part of the circuitry within one or more processors. The communication circuitry may be a transceiver, an input / output circuit, or an interface circuit, etc.
[0330] For example, in various implementations of the communication device shown in FIG9, the communication circuit may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The communication circuit is also used to communicate with other devices / communication devices via a transmission medium.
[0331] Optionally, the communication device 90 may further include one or more memories 930 for storing program instructions and / or data. The memories 930 are coupled to the processing circuitry 920. The coupling in this embodiment is an indirect coupling or communication connection between communication devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between the communication devices, units, or modules. The processing circuitry 920 may operate in conjunction with the memories 930. The processing circuitry 920 may execute the program instructions stored in the memories 930. Optionally, at least one of the aforementioned memories may be included in the processing circuitry.
[0332] This application embodiment does not limit the specific connection medium between the communication circuit 910, processing circuit 920, and memory 930. In this application embodiment, the memory 930, processing circuit 920, and communication circuit 910 are connected via a bus 940 in Figure 9. The bus is represented by a thick line in Figure 9. The connection methods between other components are only for illustrative purposes and are not intended to be limiting. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 9, but this does not mean that there is only one bus or one type of bus.
[0333] In the embodiments of this application, the processing circuit may be a general-purpose processing circuit, a digital signal processing circuit, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams in the embodiments of this application. The general-purpose processing circuit may be a microprocessor circuit or any conventional processing circuit, etc. The steps of the methods in conjunction with the embodiments of this application can be directly manifested as the execution of the hardware processing circuit, or the execution of the steps by combining hardware and software modules in the processing circuit, etc.
[0334] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code in the form of instructions or data structures, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to these. The memory in this application embodiment may also be a circuit or any other communication device capable of implementing storage functions, used to store program instructions and / or data.
[0335] For example, the processing circuit 920 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 930 is mainly used to store software programs and data. The communication circuit 910 may include a control circuit and an antenna. The control circuit is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output communication devices, such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.
[0336] When the communication device is powered on, the processing circuit 920 can read the software program in the memory 930, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processing circuit 920 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processing circuit 920. The processing circuit 920 converts the baseband signal back into data and processes the data.
[0337] In another implementation, the radio frequency circuit and antenna can be set up independently of the processing circuit that performs baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna can be arranged in a remote manner, independent of the communication device.
[0338] The communication device shown in this application embodiment may have more components than those in Figure 9, and this application embodiment does not limit this. The methods performed by the processing circuit and communication circuit shown above are only examples, and the specific steps performed by the processing circuit and communication circuit can be referred to the methods described above.
[0339] In another possible implementation, in the communication device shown in Figure 8, the processing module 801 can be one or more logic circuits, and the communication module 802 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the communication module 802 may also include a transmitting module and / or a receiving module. The transmitting module may include an output interface, and the receiving module may include an input interface. The transmitting module and the receiving module are integrated into one module, such as an input / output interface.
[0340] Figure 10 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 10, the communication device includes a logic circuit 1001 and an interface circuit 1002. That is, the processing module 801 can be implemented using the logic circuit 1001, and the communication module 802 can be implemented using the interface circuit 1002. The logic circuit 1001 can be a chip, a processing circuit, an integrated circuit, or a system-on-a-chip (SoC) chip, etc., and the interface circuit 1002 can be a communication interface, an input / output interface, pins, etc. For example, the communication device in Figure 10 can be a chip, which includes the logic circuit 1001 and the interface circuit 1002.
[0341] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 1001 can be used to execute the functions or steps implemented by the processing module 801 shown in FIG8, and the interface circuit 1002 can be used to execute the functions or steps implemented by the communication module 802 shown in FIG8. For a detailed description of the logic circuit 1001 and the interface circuit 1002, please refer to FIG8 or the method embodiment shown above, which will not be detailed here.
[0342] The communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form, or it can implement the method provided in the embodiments of this application in software form, etc., and the embodiments of this application do not limit it in this way.
[0343] This application also provides a communication system, which includes a terminal-side device and a network-side device, which can be used to execute the methods in any of the foregoing embodiments.
[0344] In addition, this application also provides a computer program for implementing the operations and / or processes performed by various communication devices in the method provided in this application.
[0345] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by various communication devices in the methods provided in this application.
[0346] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by various entities in the method provided in this application to be executed.
[0347] In the embodiments provided in this application, it should be understood that the disclosed systems, communication devices, and methods can be implemented in other ways. For example, the communication device embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, communication devices, or modules, or it may be an electrical, mechanical, or other form of connection.
[0348] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.
[0349] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.
[0350] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0351] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A communication method, characterized in that, The method includes: Receive the first synchronization signal block (SSB); Receive first information, which indicates a first association relationship; A random access request is sent based on the first association relationship; The first association relationship includes at least one of the following: The association between the first preamble root index and the first SSB; or, The relationship between the first cyclic shift offset and the first SSB; or, The relationship between the first preamble length, the first preamble resource configuration, and the first SSB; or, The association between the first restricted set, the first zero-related region configuration, and the first SSB; or, The association between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the first SSB; or, The relationship between the first cyclic prefix length, the first preamble resource configuration, and the first SSB.
2. The method according to claim 1, characterized in that, The first information also indicates a second association, which includes at least one of the following: The association between the second preamble root index and the second SSB; or, The relationship between the second cyclic shift offset and the second SSB; or, The relationship between the second preamble length, the second preamble resource configuration, and the second SSB; or, The association between the second restriction set, the second zero-related region configuration, and the second SSB; or, The association between the second preamble sequence type, the second preamble length, the second preamble root index, the second cyclic shift offset, the second preamble resource configuration, and the second SSB; or, The association between the second cyclic prefix length, the second preamble resource configuration, and the second SSB.
3. The method according to claim 2, characterized in that, The preamble format associated with the second SSB is the same as that associated with the first SSB.
4. The method according to claim 2 or 3, characterized in that, The first SSB and the second SSB have different preamble configuration parameters. The preamble configuration parameters include at least one of the following: preamble root index, preamble length, cyclic shift offset, restriction set, cyclic prefix length, preamble resource configuration, zero correlation region configuration, or preamble sequence type.
5. The method according to any one of claims 2 to 4, characterized in that, The first parameter of the second SSB is different from the first parameter of the first SSB. The first parameter includes one or more of the following: SSB transmit power, SSB target receive power, or SSB beamforming gain.
6. The method according to any one of claims 1 to 5, characterized in that, The first information indicates the third association, which includes at least one of the following: The association between the third preamble root index and the first SSB; or, The relationship between the third cyclic shift offset and the first SSB; or, The relationship between the third preamble length, the third preamble resource configuration, and the first SSB; or, The association between the third restricted set, the third zero-related region configuration, and the first SSB; or, The relationship between the third preamble sequence type, the third preamble length, the third preamble root index, the third cyclic shift offset, the third preamble resource configuration, and the first SSB; or, The relationship between the third cyclic prefix length, the third preamble resource configuration, and the first SSB.
7. The method according to claim 6, characterized in that, The first information indicates a first association group, which includes the first association and the third association.
8. The method according to any one of claims 1 to 7, characterized in that, The first information indicates a second association group, which includes a fourth association, the fourth association including at least one of the following: The association between the first preamble root index and the third SSB; or, The relationship between the first cyclic shift offset and the third SSB; or, The relationship between the first preamble length, the first preamble resource configuration, and the third SSB; or, The association between the first restricted set, the first zero-related region configuration, and the third SSB; or, The association between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the third SSB; or, The association between the first cyclic prefix length, the first preamble resource configuration, and the third SSB.
9. The method according to any one of claims 1 to 8, characterized in that, The first information also indicates the association between the first SSB and the first random access channel RO, wherein the random access request is transmitted on the first RO.
10. The method according to any one of claims 1 to 9, characterized in that, The first information is carried in system information block 1.
11. A communication method, characterized in that, The method includes: Send the first synchronization signal block (SSB); Send a first message, which indicates a first association; The first association relationship includes at least one of the following: The association between the first preamble root index and the first SSB; or, The relationship between the first cyclic shift offset and the first SSB; or, The relationship between the first preamble length, the first preamble resource configuration, and the first SSB; or, The association between the first restricted set, the first zero-related region configuration, and the first SSB; or, The association between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the first SSB; or, The relationship between the first cyclic prefix length, the first preamble resource configuration, and the first SSB.
12. The method according to claim 11, characterized in that, The first information also indicates a second association, which includes at least one of the following: The association between the second preamble root index and the second SSB; or, The relationship between the second cyclic shift offset and the second SSB; or, The relationship between the second preamble length, the second preamble resource configuration, and the second SSB; or, The association between the second restriction set, the second zero-related region configuration, and the second SSB; or, The association between the second preamble sequence type, the second preamble length, the second preamble root index, the second cyclic shift offset, the second preamble resource configuration, and the second SSB; or, The association between the second cyclic prefix length, the second preamble resource configuration, and the second SSB.
13. The method according to claim 12, characterized in that, The preamble format associated with the second SSB is the same as that associated with the first SSB.
14. The method according to claim 12 or 13, characterized in that, The first SSB and the second SSB have different preamble configuration parameters. The preamble configuration parameters include at least one of the following: preamble root index, preamble length, cyclic shift offset, restriction set, cyclic prefix length, preamble resource configuration, zero correlation region configuration, or preamble sequence type.
15. The method according to any one of claims 12 to 14, characterized in that, The first parameter of the second SSB is different from the first parameter of the first SSB. The first parameter includes one or more of the following: SSB transmit power, SSB target receive power, or SSB beamforming gain.
16. The method according to any one of claims 11 to 15, characterized in that, The first information indicates a third association of the first SSB, the third association including at least one of the following: The association between the third preamble root index and the first SSB; or, The relationship between the third cyclic shift offset and the first SSB; or, The relationship between the third preamble length, the third preamble resource configuration, and the first SSB; or, The association between the third restricted set, the third zero-related region configuration, and the first SSB; or, The relationship between the third preamble sequence type, the third preamble length, the third preamble root index, the third cyclic shift offset, the third preamble resource configuration, and the first SSB; or, The relationship between the third cyclic prefix length, the third preamble resource configuration, and the first SSB.
17. The method according to claim 16, characterized in that, The first information indicates a first association group, which includes the first association and the third association.
18. The method according to any one of claims 11 to 17, characterized in that, The first information indicates a second association group, which includes a fourth association, the fourth association including at least one of the following: The association between the first preamble root index and the third SSB; or, The relationship between the first cyclic shift offset and the third SSB; or, The relationship between the first preamble length, the first preamble resource configuration, and the third SSB; or, The association between the first restricted set, the first zero-related region configuration, and the third SSB; or, The association between the first preamble sequence type, the first preamble length, the first preamble root index, the first cyclic shift offset, the first preamble resource configuration, and the third SSB; or, The association between the first cyclic prefix length, the first preamble resource configuration, and the third SSB.
19. The method according to any one of claims 11 to 18, characterized in that, The first information is carried in system information block 1.
20. A communication device, characterized in that, The apparatus includes a module or unit for performing the method according to any one of claims 1 to 10, or the apparatus includes a module or unit for performing the method according to any one of claims 11 to 19.
21. A communication device, characterized in that, The communication device includes at least one processor; wherein the at least one processor is configured to cause the communication device to perform the method of any one of claims 1 to 10, or the at least one processor is configured to cause the communication device to perform the method of any one of claims 11 to 19.
22. A communication device, characterized in that, Includes a processor for executing computer programs or instructions to cause the communication device to perform the method of any one of claims 1 to 19.
23. The communication device according to claim 22, characterized in that, It also includes a memory for storing the computer program or instructions.
24. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed, perform the method as described in any one of claims 1 to 10, or the method as described in any one of claims 11 to 19.
25. A computer program product, characterized in that, It includes computer code or computer program, which, when executed, performs the method as described in any one of claims 1 to 19.