Communication method and apparatus, and storage medium and program product

Abstract

The embodiments of the present application relate to the technical field of communications. Provided are a communication method and apparatus, and a storage medium and a program product, which solve the technical problems of the probability of collision during random access re-initiation and the probabilty of random access failure being high when a terminal performs random access on a network having a long SSB period. The method comprises: after a terminal sends first random access request information, if no response information to the first random access request information is detected within a random access detection backoff duration window, the terminal using a duration that is twice an SSB period or more than twice an SSB period of a current network system as the maximum backoff duration to randomly select a backoff duration for re-initiating random access, and re-initiating the random access on the basis of the randomly selected backoff duration.

Description

Communication methods, devices, storage media and software products

[0001] This application claims priority to Chinese Patent Application No. 202411818301.5, filed on December 10, 2024, entitled "Communication Method, Apparatus, Storage Medium and Program Product", 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 a communication method, apparatus, storage medium, and program product. Background Technology

[0003] During the random access process of a terminal, if multiple terminals select the same SSB within the same synchronization signal block (SSB) period, their random access request messages sent based on the random access occasion (RO) configured by the SSB may collide, leading to random access failure. After this, the multiple terminals will randomly select a backoff duration within the maximum backoff duration to re-initiate random access, and will resend the random access request message in the SSB period following that backoff duration. If at least two of the multiple terminals reselect a backoff duration within the same SSB period, their random access request messages may also collide, leading to random access failure.

[0004] The maximum backoff time currently set during random access is 960ms. However, this maximum backoff time only applies to networks with shorter SSB periods. For other networks with longer SSB periods, such as non-terrestrial networks (NTNs), this maximum backoff time is not applicable. This results in a higher probability of collisions when the terminal re-initiates random access in these networks with longer SSB periods, and a higher probability of random access failure. Summary of the Invention

[0005] This application provides a communication method, apparatus, storage medium, and program product that can reduce the probability of collisions when re-initiating random access and improve the success rate of terminal random access.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] Firstly, a communication method is provided. This method can be executed by a terminal, or by a component of the terminal, such as the terminal's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the terminal. The following description uses the method executed by a terminal as an example. The communication method includes: after sending a first random access request, if no response information for the first random access request is detected within a random access detection backoff time window, the terminal randomly selects a backoff time for re-initiating random access using the maximum backoff time, and re-initiates random access based on the randomly selected backoff time.

[0008] Based on this, in the embodiments of this application, since the maximum backoff time referenced when the terminal selects the backoff time for re-initiating random access is twice or more the SSB period of the current network system, it helps to reduce the probability that the timing of the terminal re-initiating random access is in the same SSB period as the timing of other terminals initiating random access, thereby reducing the probability of collision when the terminal initiates random access again and improving the success rate of the terminal's random access.

[0009] Furthermore, compared to the existing technology that sets the maximum rollback duration to a fixed value, the embodiments of this application can adjust the maximum rollback duration according to the SSB cycle of the network system, thereby improving the flexibility of configuring the maximum rollback duration.

[0010] In one possible implementation, the SSB period is greater than or equal to 120 milliseconds.

[0011] Since the SSB period can be longer than 120 milliseconds in an NTN network, the maximum backoff time in this embodiment can be set to twice or more than 120 milliseconds, thus adapting the maximum backoff time to the NTN network. This reduces the probability of a collision occurring again when the terminal initiates a re-random access in the NTN network, and improves the success rate of random access in the NTN network.

[0012] In one possible implementation, the maximum backoff duration is related to the values ​​of the leading backoff parameter and / or the scaling factor; wherein the value of the leading backoff parameter is greater than or equal to twice the duration of the SSB period, and / or the value of the scaling factor is an integer greater than 1.

[0013] Based on this, in this embodiment, the leading backoff parameter is set to be twice or more the duration of the SSB cycle, and a corresponding scaling factor is set. The maximum backoff duration is determined by combining the leading backoff parameter and the scaling factor, so that the maximum backoff duration in this embodiment is twice or more the duration of the SSB cycle of the network system.

[0014] In one possible implementation, the value of the leading backoff parameter includes at least one of the following: 1280 milliseconds, 1920 milliseconds, or 2560 milliseconds.

[0015] Based on this, this application can expand the existing values ​​of the preamble backoff parameter to determine the maximum backoff duration with a larger preamble backoff parameter, thereby making the determined maximum backoff duration larger. This can further reduce the probability of collisions occurring again when the terminal initiates a re-random access, and improve the success rate of terminal random access.

[0016] In one possible implementation, the scaling factor is less than or equal to 4.

[0017] Based on this, this application can further adjust the maximum backoff duration through a scaling factor to avoid a high probability of collisions during random terminal access caused by an excessively large maximum backoff duration. Simultaneously, setting the maximum value of the scaling factor to 4 can prevent an excessively long maximum backoff duration from causing high latency in random access.

[0018] In one possible implementation, the maximum backoff duration applies to the RO that sends the first random access request information; or, the maximum backoff duration applies to the RO corresponding to the SSB that sends the first random access request information.

[0019] If terminal 1 and terminal 2 collide in the first random access request (RO), and terminal 1 subsequently initiates random access in the same RO, there is still a high probability that terminal 1 and terminal 2 will collide again. In this case, if terminal 1 initiates random access based on the maximum backoff duration, it can reduce the probability of another collision when terminal 1 initiates random access again, thereby improving the success rate of terminal 1's random access.

[0020] If terminal 1 subsequently chooses to initiate random access in another RO, the probability of terminal 1 colliding with terminal 2 again is relatively low. In this case, terminal 1 does not need to initiate random access based on the maximum backoff duration. Therefore, the maximum backoff duration can be limited to the RO that sent the first random access request information, or the RO corresponding to the SSB that sent the first random access request information, without limiting the terminal to re-initiating random access requests in other ROs.

[0021] Secondly, a communication method is provided. This method can be executed by a terminal, or by a component of the terminal, such as the terminal's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the terminal. The following explanation uses the method executed by a terminal as an example. The communication method includes: the terminal sending a first random access request message on a first random access time (RO); if the terminal does not receive a response message for the first random access request message within the random access detection backoff time window, it re-initiates random access on a second RO. Wherein, if the terminal re-initiates random access twice on the same RO, the re-initiated random access must be initiated within the SSB period after the randomly selected backoff time. If the terminal re-initiates random access twice on different ROs, the re-initiated random access is not subject to the backoff time limitation.

[0022] In one possible implementation, the first RO and the second RO are different, including at least one of the following: the first RO and the second RO are ROs corresponding to different SSBs; or, the first RO and the second RO are different ROs corresponding to the same SSB.

[0023] Therefore, if a terminal re-initiates random access on different ROs corresponding to different SSBs, or on different ROs corresponding to the same SSB, the re-initiated random access by the terminal is not subject to the rollback duration limit.

[0024] In one possible implementation, the first RO and the second RO are the same, including at least one of the following: the first RO and the second RO are ROs corresponding to the same SSB; or the first RO and the second RO have the same time-frequency resources.

[0025] Therefore, if a terminal re-initiates random access on the same RO corresponding to the same SSB, or on an RO with the same time-frequency resource RO, the re-initiated random access needs to be initiated within the SSB period after the randomly selected backoff duration.

[0026] Thirdly, a communication method is provided. This method can be executed by a network device, or by a component of the network device, such as the network device's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the network device. The following description uses the execution of this method by a network device as an example. The communication method includes: the network device receiving first random access request information; the network device receiving second random access request messages; wherein the second random access request message is sent by the terminal when no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window; the first random access preamble is the random access preamble carried in the first random access request information sent by the terminal; the maximum backoff time of the second random access request information is greater than or equal to twice the duration of the synchronization signal block (SSB) period, and the SSB period is the SSB period of the network system currently performing random access.

[0027] In one possible implementation, the SSB period is greater than or equal to 120 milliseconds.

[0028] In one possible implementation, the maximum backoff duration is related to the values ​​of the leading backoff parameter and / or the scaling factor; wherein the value of the leading backoff parameter is greater than or equal to twice the duration of the SSB period, and / or the value of the scaling factor is an integer greater than 1.

[0029] In one possible implementation, the leading backoff parameter can be set to 1280 milliseconds, 1920 milliseconds, or 2560 milliseconds.

[0030] In one possible implementation, the scaling factor is less than or equal to 4.

[0031] In one possible implementation, the maximum backoff duration applies to the RO that sends the first random access request information; or, the maximum backoff duration applies to the RO corresponding to the SSB resource that sends the first random access request information.

[0032] Fourthly, a communication method is provided. This method can be executed by a network device, or by a component of the network device, such as the network device's processor, chip, or chip system, or by a logic module or software capable of implementing all or part of the network device. The following description uses the execution of this method by a network device as an example. The communication method includes: the network device receiving first random access request information; the network device receiving a second random access request message sent on a second RO; wherein the second random access request message is sent by the terminal when no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window; the first random access preamble is the random access preamble carried in the first random access request information; when the first RO and the second RO are the same, the second RO is outside the backoff time configured by the access network device for the random access request information; when the first RO and the second RO are different, the second RO is within the backoff time, or the second RO is outside the backoff time.

[0033] In one possible implementation, the first RO and the second RO are different, including at least one of the following: the first RO and the second RO are ROs corresponding to different SSBs; or, the first RO and the second RO are different ROs corresponding to the same SSB.

[0034] In one possible implementation, the first RO and the second RO are the same, including at least one of the following: the first RO and the second RO are ROs corresponding to the same SSB; or the first RO and the second RO have the same time-frequency resources.

[0035] Fifthly, a communication device is provided for implementing the various methods described above. This communication device can be a terminal as described in the first aspect, or a device including the terminal, or a device included in the terminal, such as a chip. Alternatively, the communication device can be a network device as described in the second aspect, or a device including the network device, or a device included in the network device, such as a chip. The communication device can be a terminal as described in the third aspect, or a device including the terminal, or a device included in the terminal, such as a chip. Alternatively, the communication device can be a network device as described in the fourth aspect, or a device including the network device, or a device included in the network device, such as a chip. The communication device includes modules, units, or means corresponding to the methods described above, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0036] In some possible designs, the communication device may include a processing module and a transceiver module. The transceiver module, also referred to as a transceiver unit, is used to implement the transmission and / or reception functions in any of the above aspects and their possible implementations. The transceiver module may consist of transceiver circuits, transceivers, transceivers, or communication interfaces. The processing module can be used to implement the processing functions in any of the above aspects and their possible implementations.

[0037] In some possible designs, the transceiver module includes a sending module and a receiving module, which are used to implement the sending and receiving functions in any of the above aspects and any possible implementation methods.

[0038] A sixth aspect provides a communication device, comprising: at least one processor; the processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the methods of any of the above aspects. The memory may be coupled to the processor, or may be independent of the processor. The communication device may be a terminal as described in the first aspect, or a device including the terminal, or a device included in the terminal, such as a chip. Alternatively, the communication device may be a network device as described in the second aspect, or a device including the network device, or a device included in the network device, such as a chip. The communication device may be a terminal as described in the third aspect, or a device including the terminal, or a device included in the terminal, such as a chip. Alternatively, the communication device may be a network device as described in the fourth aspect, or a device including the network device, or a device included in the network device, such as a chip. In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0039] In one possible implementation, the processor includes logic circuitry and input and / or output interfaces. The output interfaces are used to perform the sending action in the corresponding method, and the input interfaces are used to perform the receiving action in the corresponding method.

[0040] In one possible implementation, the communication device further includes a communication interface and a communication bus, with the processor, memory, and communication interface connected via the communication bus. The communication interface is used to perform the sending and receiving actions in the corresponding method. The communication interface can also be called a transceiver. Optionally, the communication interface includes a transmitter and a receiver; in this case, the transmitter is used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.

[0041] In some possible designs, the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete components. When the communication device is a chip, the aforementioned transmitting action / function can be understood as an output, and the aforementioned receiving action / function can be understood as an input.

[0042] In a seventh aspect, a chip is provided, the chip including a processor for implementing the functions involved in any of the foregoing aspects or any implementation thereof.

[0043] In some possible designs, the chip includes a memory for storing necessary program instructions and data.

[0044] Eighthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods of any of the above aspects or any implementation thereof.

[0045] Ninthly, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to execute any of the above aspects or any implementation thereof.

[0046] In a tenth aspect, a communication system is provided, which includes the terminal of the first aspect and the network device of the second aspect; or, the communication system includes the terminal of the third aspect and the network device of the fourth aspect.

[0047] The technical effects of any of the implementation methods in aspects two through ten can be found in the technical effects of the corresponding implementation methods in aspect one, and will not be repeated here.

[0048] It should be noted that any of the possible implementations of any of the above aspects can be combined, provided that the solutions do not contradict each other. Attached Figure Description

[0049] Figure 1 is a flowchart illustrating a random access procedure;

[0050] Figure 2 is a schematic diagram of one SSB corresponding to four ROs;

[0051] Figure 3 is a schematic diagram of the correspondence between SSB index, preamble, RO, and RA-RNTI;

[0052] Figure 4 is a schematic diagram of terminal 1 and terminal 2 randomly selecting a backoff time and re-initiating random access after a random access collision;

[0053] Figure 5 is another schematic diagram of terminal 1 and terminal 2 randomly selecting a backoff time and re-initiating random access after a random access collision;

[0054] Figure 6 is a schematic diagram of terminal 1 reselecting the optimal SSB index after a random access collision;

[0055] Figure 7 is a schematic diagram of the architecture of a mobile satellite communication system provided in this application;

[0056] Figure 8 is a flowchart illustrating a communication method provided in this application;

[0057] Figure 9 is a flowchart illustrating another communication method provided in this application;

[0058] Figure 10 is a schematic diagram of the structure of a communication device provided in this application;

[0059] Figure 11 is a schematic diagram of another communication device provided in this application;

[0060] Figure 12 is a schematic diagram of another communication device provided in this application. Detailed Implementation

[0061] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0062] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0063] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

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

[0065] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0066] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and do not limit the rollback time, nor do they require a judgment action during implementation, nor do they imply any other limitations.

[0067] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0068] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments described below do not constitute a limitation on the scope of protection of this application.

[0069] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0070] 1. NTN

[0071] NTN refers to a communication network that communicates via satellite. NTN technology provides wider coverage and higher transmission rates for wireless communication globally. It can establish a global communication network in a shorter time, enabling high-speed communication anytime, anywhere, and providing a more reliable communication infrastructure for mobile internet, the Internet of Things (IoT), and other applications. NTN technology is used in scenarios including aviation, maritime, polar regions, deserts, and other areas difficult for humans to reach, as well as providing communication support during emergencies such as natural disasters and wars. The development of NTN technology will provide more stable and reliable support for global digital construction. Compared to terrestrial communication, NTN communication has significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and no geographical limitations. It has been widely used in maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. NTN networks can be integrated with terrestrial networks, leveraging their strengths to form a seamless global integrated communication network encompassing sea, land, air, space, and ground, meeting users' ubiquitous and diverse service needs.

[0072] 2. Random Access

[0073] Random access is the process by which a terminal sends a preamble (also called a preamble index) to a network device to request access to the network and establish a connection. As shown in Figure 1, the random access process includes:

[0074] Step 101: Select SSB on the terminal.

[0075] In some embodiments, the terminal measures the SSB sent by the network device and selects the SSB for downlink synchronization based on the measurement results.

[0076] Step 102: The terminal sends message 1 (Msg1).

[0077] Message 1 includes a preamble determined by the terminal.

[0078] In some embodiments, the terminal determines the preamble and random access occasion (RO) based on the selected SSB, and sends message 1 in the RO.

[0079] As one implementation method, the process of the terminal determining the preamble is as follows: the terminal selects an SSB from the relevant SSBs whose synchronization signal-reference signal received power (SS-RSRP) is higher than the RSRP threshold; the terminal then selects the random access preamble corresponding to the selected SSB.

[0080] As an example, the preamble is described as follows: A User Equipment (UE) is provided with an SS / PBCH block number N associated with one Random Access Channel (PRACH) opportunity, and a contention-based preamble number R associated with each SS / PBCH block for each valid PRACH opportunity, provided by the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. If N is less than 1, an SS / PBCH block is mapped to 1 / N consecutive valid PRACH opportunities, and the contention-based preamble with a consecutive index associated with the SS / PBCH block for each valid PRACH opportunity starts with preamble 0. If N is greater than or equal to 1, the contention-based preamble number R associated with the parameter preamble / N, with a consecutive index, is provided by totalNumberOfRA-Preambles and is an integer multiple of N.

[0081] As one implementation, network devices are pre-configured with RO period, maximum RO backoff duration, offset start position (referred to as RO time-frequency resource configuration), and preamble configuration. The network device can indicate the RO time-frequency resource configuration and preamble configuration for random access to the terminal via SSB. The terminal selects a preamble and RO based on the RO time-frequency resource configuration and preamble configuration indicated by the SSB, and sends the selected preamble in the selected RO.

[0082] Optionally, a mapping relationship is pre-configured between SSBs and ROs. This can be one SSB corresponding to one or more ROs, or one or more SSBs corresponding to one RO. For example, 8 SSBs correspond to 1 RO, 1 SSB corresponds to 4 ROs, or 1 SSB corresponds to 16 ROs. When one SSB corresponds to multiple ROs, the terminal can determine the RO for sending message 1 based on the preamble. The mapping relationship between SSBs and ROs can be configured by the network device. Figure 2 shows a schematic diagram of 1 SSB corresponding to 4 ROs.

[0083] Optionally, the terminal can also determine the random access radio network temporary identifier (RA-RNTI) based on the RO of message 1 and the type of uplink carrier, and transmit message 1 on the predetermined uplink carrier at the selected RO based on the RA-RNTI. The RA-RNTI may differ when the uplink carrier type is uplink (UL) or supplementary uplink (SUL).

[0084] As an example, Figure 3 illustrates the correspondence between SSB index, preamble index, RO, and RA-RNTI provided in an embodiment of this application. As shown in Figure 3, the terminal determines RO based on the SSB index and preamble, and determines RA-RNTI based on RO and UL / SUL.

[0085] Step 103: The terminal monitors whether it receives message 2 (Msg2) corresponding to message 1 within the RAR monitoring time window.

[0086] If the terminal receives message 2 corresponding to message 1, it will continue with the subsequent contention resolution mechanism to perform random access. If the terminal does not receive message 2 corresponding to message 1, it will choose to roll back the time limit and re-initiate random access.

[0087] In some embodiments, after the selected RO sends message 1, the terminal monitors for RA-RNTI scrambled message 2 (Msg2) within the corresponding random access response (RAR) time window. If the terminal detects message 2 carrying the preamble sent by the terminal within the RAR time window, it determines that message 2 was successful and continues the subsequent random access procedure. If the terminal does not detect message 2 within the RAR time window, or if the detected message 2 does not carry the preamble sent by the terminal, it re-initiates random access after waiting for the rollback period.

[0088] Step 104: If the terminal does not receive the corresponding message 2, it will resend message 1 within the SSB period after the rollback period.

[0089] In some embodiments, the terminal retransmits message 1 based on the previously selected SSB during the SSB period after the rollback duration.

[0090] As one implementation, the backoff duration waited by the terminal is a randomly selected duration between 0 and the maximum backoff duration. The maximum backoff duration is the product of the preamble backoff parameter (PREAMBLE_BACKOFF) and the scaling factor (SCALING_FACTOR_BI). Optionally, the preamble backoff parameter is carried in message 2 sent by the network device to the terminal. If message 2 does not contain a preamble backoff parameter, the maximum backoff duration is 0. The scaling factor is carried in system messages or radio resource control (RRC) signaling messages sent by the network device to the terminal. Currently, in random access processes triggered by non-radio link failure (RLF) or beam failure, the scaling factor is fixed at 1.

[0091] As an example, the values ​​for the leading backoff parameter are shown in Table 1 below:

[0092] Table 1 Values ​​of the leading backoff parameter

[0093] Taking an SSB period of 640ms and a maximum rollback time of 960ms configured for the network device as an example, the process of a terminal re-initiating random access is explained.

[0094] Figure 4 illustrates how Terminal 1 and Terminal 2 randomly select a backoff time and re-initiate random access after a random access collision. As shown in Figure 4, Terminal 1 and Terminal 2 perform SSB measurements and both select the third SSB index as the optimal SSB index. Within the first SSB period, both Terminal 1 and Terminal 2 send random access request messages based on the third SSB index, resulting in a collision between their messages. Terminal 1 and Terminal 2 select a backoff duration between 0ms and 960ms, with Terminal 1 selecting a backoff duration of 600ms and Terminal 2 selecting a backoff duration of 300ms. The current SSB period is 640ms, and the backoff durations selected by Terminal 1 and Terminal 2 are within the same period. At this point, both Terminal 1 and Terminal 2 re-initiate random access in the next SSB period following the one containing their backoff durations. In the next SSB cycle, both Terminal 1 and Terminal 2 will select the third SSB index as the optimal SSB index, and both Terminal 1 and Terminal 2 will send random access request messages based on the third SSB index in the next SSB cycle. The retransmitted random access request messages from Terminal 1 and Terminal 2 may collide again.

[0095] Figure 5 illustrates another scenario where Terminal 1 and Terminal 2 randomly select a backoff time and re-initiate random access after a random access collision. As shown in Figure 5, Terminal 1 and Terminal 2 perform SSB measurements and both select the third SSB index as the optimal SSB index. Within the first SSB period, both Terminal 1 and Terminal 2 send random access request messages based on the third SSB index. The random access request messages from Terminal 1 and Terminal 2 collide. Terminal 1 and Terminal 2 each select a backoff duration between 0 and 960ms, with Terminal 1 selecting a backoff duration of 900ms and Terminal 2 selecting a backoff duration of 300ms. The current SSB period is 640ms, and the backoff durations selected by Terminal 1 and Terminal 2 fall within different periods. At this point, both Terminal 1 and Terminal 2 re-initiate random access in the next SSB period of their respective backoff durations. Since Terminal 1 and Terminal 2 initiate random access requests at different times, even if both Terminal 1 and Terminal 2 select the third SSB index as the optimal SSB index for random access, the random access request messages sent by Terminal 1 and Terminal 2 will not collide. The retransmitted random access request messages from Terminal 1 and Terminal 2 are successful.

[0096] The current maximum backoff duration is set for the unadjusted SSB period, which is typically 20ms, 40ms, or 60ms. The maximum possible value for the corresponding maximum backoff duration is 960ms. However, as networks evolve, the SSB period may lengthen. For example, in NTN networks, the SSB period might be extended to 120ms, 240ms, 360ms, or 640ms. If a maximum backoff duration of 960ms is used in a network system with a longer SSB period, the probability of terminals experiencing random access collisions reselecting a maximum backoff duration within the same SSB period increases. These terminals will then re-initiate random access within the same SSB period, further increasing the probability of collisions during re-initiation. The probability of a terminal failing to re-initiate random access also increases.

[0097] To address the aforementioned issues, the communication method provided in this application involves the terminal determining the maximum backoff duration for random access based on the SSB cycle of the network system currently in use, and then randomly selecting a backoff duration to re-initiate random access based on this maximum backoff duration. Since the maximum backoff duration selected in this application is compatible with the SSB cycle of the network system, the communication method provided can reduce the probability that the terminal randomly selects a backoff duration within the same SSB cycle, thereby reducing the probability of a collision occurring again when the terminal initiates a re-random access and improving the success rate of random access. Furthermore, compared to the prior art where the maximum backoff duration is typically fixed, this application can adjust the maximum backoff duration according to the SSB cycle of the network system, thus improving the flexibility of configuring the maximum backoff duration.

[0098] Furthermore, during the current random access process, there may be situations where the SSB index selected by the terminal when re-initiating random access is different from the SSB index selected during the previous random access.

[0099] Figure 6 illustrates a scenario where terminal 1 reselects the optimal SSB index after a random access collision between terminal 1 and terminal 2. As shown in Figure 6, both terminal 1 and terminal 2 selected SSB index #21 for random access. The random access collision between terminal 1 and terminal 2 caused message 1 to fail. However, due to measurement errors, the SSB index #21 selected by terminal 1 is not the optimal SSB index; the optimal index for terminal 1 is SSB index #1. After the random access failure, the terminal may re-measure the SSB and select SSB index #1 as the optimal SSB index. In the current random access scenario, even if the terminal reselects the optimal SSB index #1 within the rollback period, the terminal cannot immediately resend the random access request message on SSB index #1. Instead, it must wait until after the rollback period before resending the random access request message on SSB index #1.

[0100] However, after the terminal reselects the optimal SSB index #1, the random access of terminal 1 and terminal 2 will no longer collide. At this time, the terminal cannot send a random access request message within the rollback time, causing the terminal to miss the RO that can send a random access request message normally, which increases the latency of the terminal's random access.

[0101] To address the aforementioned issues, the communication method provided in this application involves the terminal sending a first random access request message on a first random access location (RO). If the terminal does not receive a response to the first random access request message within the random access detection backoff time window, it re-initiates random access on a second RO. Specifically, if the terminal re-initiates random access twice on the same RO, the re-initiated random access must be initiated within the SSB period after the randomly selected backoff time. If the terminal re-initiates random access twice on different ROs, the re-initiated random access is not subject to the backoff time limitation. This allows the terminal to re-initiate random access on different ROs without being limited by the backoff time, thereby preventing the terminal from missing ROs where random access request messages can occur normally and reducing the latency of the terminal's random access.

[0102] The technical solutions of this application embodiment can be used in NTN systems such as satellite communication systems, high altitude platform station (HAPS) communication, and unmanned aerial vehicles (UAVs). Examples include integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS), and ultra-dense low-Earth orbit (LEO) satellite communication systems. NTN systems can be integrated with traditional mobile communication systems. For example, the mobile communication system can be a 4th generation (4G) communication system (e.g., Long Term Evolution (LTE) system), a worldwide interoperability for microwave access (WiMAX) communication system, a 5G communication system (e.g., NR system), a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) communication system, a vehicle-to-everything (V2X) communication system, and future mobile communication systems.

[0103] The communication systems described above are merely illustrative examples, and the communication systems and scenarios applicable to this application are not limited thereto. The communication systems and scenarios provided in this application do not impose any limitations on the solutions of this application. This is hereby stated uniformly and will not be repeated below.

[0104] As one possible implementation, the communication system applicable to the present application may include at least one terminal and at least one network device. For example, terminals may communicate with each other via wired or wireless means, as may a terminal communicate with a network device, and as may a network device communicate with each other.

[0105] Optionally, the terminal can be a user-side device with wireless transceiver capabilities, or a chip or chip system embedded in that device. The terminal can also be referred to as user equipment (UE), terminal, access terminal, user unit, user station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), user terminal, wireless communication equipment, user agent, or user device, etc. For example, the terminal can be a terminal in IoT, V2X, D2D, M2M, 5G networks, or future evolved public land mobile networks (PLMNs). The terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (such as on airplanes, balloons, and satellites).

[0106] For example, a terminal can be a drone, an IoT device (e.g., a sensor, an electricity meter, a water meter, etc.), a V2X device, a station (ST) in a wireless local area network (WLAN), a satellite phone, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a smartphone, a wireless data card, a wireless modem, a machine-type communication device, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device (also known as a wearable smart device), a tablet or a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home. Wireless terminals (such as those in the home), vehicle-mounted terminals, vehicles with vehicle-to-vehicle (V2V) communication capabilities, intelligent connected vehicles, and drones with unmanned aerial vehicle (UAV) to UAV (U2U) communication capabilities, etc. Terminals can be mobile or fixed; this application does not specifically limit their location.

[0107] Optionally, the network device can be a network-side device with wireless transceiver capabilities, or it can be a chip, chip system, or module installed in the device. The network device is located in the radio access network (RAN) of the mobile communication system and is used to provide access services to terminals.

[0108] As one possible implementation, the network device can be a wireless relay node or a wireless backhaul node. For example, the network device can act as a Layer 1 relay device to regenerate physical layer signals (i.e., wireless frequency filtering, frequency conversion, and amplification processing) without having other higher protocol layers.

[0109] As another possible implementation, network equipment can perform some or all of the functions of a base station. For example, network equipment can be an evolved Node B (eNB or eNodeB) in LTE or evolved LTE-Advanced (LTE-A) systems, such as traditional macro base stations (eNBs) and micro base stations (eNBs) in heterogeneous network scenarios; or it can be a next-generation node B (gNodeB or gNB) in a 5G system; or it can be a transmission point (TP) or transmission reception point (TRP); or it can be a base station in a future evolved PLMN; or it can be one or a group of antenna panels of a base station; or it can be an access point (AP) in a wireless fidelity (WIFI) system; or it can be a device that performs network-side functions in IoT communication systems, V2X communication systems, D2D communication systems, M2M communication systems, or other communication systems; or it can be a radio controller in a cloud radio access network (CRAN) scenario. Optionally, network equipment can also be a server, wearable device, vehicle, or in-vehicle equipment, etc.

[0110] For example, the base station in the embodiments of this application may include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, access points, etc., and the embodiments of this application do not specifically limit them.

[0111] As another possible implementation, the network device may include at least one of the following: a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), a radio unit (RU), etc.

[0112] For example, the CU and DU can be configured separately or included in the same network element, such as in the baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0113] 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 an O-RAN central unit (O-CU), DU can also be called an O-RAN distributed unit (O-DU), CU-CP can also be called an O-RAN central unit control plane (O-CU-CP), CU-UP can also be called an O-RAN central unit user plane (O-CU-UP), and RU can also be called an O-RAN radio unit (O-RU). Any of the units 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 and hardware modules.

[0114] In one possible design, devices such as CU, DU, and RU can communicate with each other through open interfaces. For example, CU-CP and DU communicate via the F1-C interface, CU-UP and DU via the F1-U interface, DU and RU via the fronthaul interface, DU and terminals via the air interface, and CU and core network devices via the NG interface. Furthermore, core network devices and network devices can connect to the Operation Administration and Maintenance (OAM) system.

[0115] In addition, O-RAN utilizes artificial intelligence (AI) technology to integrate the RAN intelligent controller into the RAN, enabling real-time monitoring, optimization, and management of the RAN. The RIC can further include non-real-time RIC (Non-RT RIC or NRT RIC) and near-real-time RIC (Near-RT RIC or nRT RIC).

[0116] Non-real-time RICs are used to implement non-real-time intelligent management of the RAN, processing non-real-time information, such as latency-insensitive data with latency in the order of seconds. They can also implement AI / machine learning (ML) including model training and updates, and guide applications / functions in near-real-time RICs based on policies. Near-real-time RICs are used to implement near-real-time intelligent management of the RAN, processing near-real-time information, such as latency-sensitive data with latency in the order of tens of milliseconds. They can also achieve near-real-time control and optimization of O-RAN modules and resources through data collection and related operations on the E2 interface.

[0117] In this embodiment, the apparatus for implementing the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing those functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, the example of a network device being used to implement the functions of a network device is provided only and does not constitute a limitation on the solutions described in this embodiment.

[0118] Optionally, the network devices in this application embodiment can be deployed on non-terrestrial platforms, such as low-altitude platforms (e.g., drones), high-altitude platforms (e.g., aircraft), or satellites. Therefore, the network devices in this application embodiment can also be referred to as non-terrestrial network devices.

[0119] For example, the satellite can be a LEO satellite, MEO satellite, GEO satellite, or non-geostationary earth orbit (NGEO) satellite, etc., without limitation. The satellite can provide communication services, navigation services, positioning services, etc., to the terminal through multiple beams. The satellite can use multiple beams to cover the service area, and different beams can communicate through one or more of the following methods: time division, frequency division, and space division.

[0120] Optionally, the satellite can operate in transparent or regenerative mode. Transparent mode, also known as bend-tube relay transmission, means that the signal only undergoes frequency conversion and amplification on the satellite; the satellite is transparent to the signal, as if it doesn't exist. Regenerative mode, also known as non-transparent (on-board access / processing) transmission, means that the satellite has some or all of the base station functions. A particular satellite may support only transparent mode, only regenerative mode, or both, and can switch between the two modes. Furthermore, the satellite can operate in staring mode or non-staring mode.

[0121] Optionally, the satellite can wirelessly communicate with ground equipment. For example, the ground equipment can be devices within the core network (CN) of an existing or future mobile communication architecture (such as the 3GPP access architecture). The core network, as the bearer network, provides the interface to the data network, offering terminals communication connectivity, authentication, management, policy control, and the ability to bear data services. The CN can further include: access and mobility management function (AMF) network elements, session management function (SMF) network elements, authentication server function (AUSF) network elements, policy control function (PCF) network elements, user plane function (UPF) network elements, and so on.

[0122] For example, a satellite can communicate wirelessly with ground equipment via an NTN gateway (or gateway station). The link between the satellite and the NTN gateway can be called a feeder link.

[0123] As a possible example, Figure 7 illustrates the architecture of a possible mobile satellite communication system to which this application applies. The system includes at least one satellite, with satellites 101, 102, and 103 used as examples in Figure 7. The satellites can provide communication and other services to terminals via multiple beams. The ellipses identifying the beams in Figure 7 can be understood as representing the coverage area of ​​the beams.

[0124] For example, satellites 101 and 102 can operate in regeneration mode, and satellite 103 can operate in transparent transmission mode. There is an inter-satellite link 01 between satellites 101 and 102, and an inter-satellite link 02 between satellites 102 and 103. Satellite 103 is connected to the ground core network equipment.

[0125] It should be noted that the satellite mentioned in the embodiments of this application may be a satellite base station, or may include an orbital receiver or repeater for relaying information, or a network-side device mounted on a satellite.

[0126] It is understood that the satellites in the embodiments of this application can be replaced with network-side equipment mounted on other flight platforms such as drones and airplanes.

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

[0128] The following description, using the communication system described above as an example, illustrates the communication method provided in the embodiments of this application through the interaction between network devices and terminals.

[0129] It should be noted that in the following embodiments of this application, the message names between various devices, the names of various parameters, or the names of various information are just examples. Other names may also be used in other embodiments, and the method provided in this application does not specifically limit them.

[0130] It is understood that in the embodiments of this application, the network device or terminal may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the various steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0131] As an example, the following embodiments use the aforementioned flight platform as a satellite, specifically satellite communication in NTN, for illustration. Of course, this method can also be applied to other scenarios in NTN, such as LAP subnetworks or HAP subnetworks, and is not specifically limited thereto.

[0132] The communication method provided in the embodiments of this application will be described below based on the above-described communication system. Referring to Figure 8, which is a flowchart of a communication method provided in an embodiment of this application, the communication method may include the following steps:

[0133] Step 801: The terminal sends a first random access request message to the network device. Correspondingly, the network device receives the first random access request message from the terminal.

[0134] In some embodiments, during random access, the terminal measures the SSBs sent by the network device to determine the optimal SSB index. Based on the system message in the SSB corresponding to the optimal SSB index, the terminal determines the preamble corresponding to that SSB; the terminal determines the RO based on the correspondence between SSBs and ROs, and the preamble. The terminal generates a first random access request message carrying the preamble and sends the first random access request message to the network device on the determined RO.

[0135] Optionally, if the network device receives the first random access request message, it generates a random access response message carrying the preamble and sends the random access response message to the terminal. If the terminal receives the random access response message and determines that it carries the preamble from the first random access request message, it determines that the first random access request message was successfully sent.

[0136] As an example, the first random access request message is Msg1 sent by the terminal to the network device during the random access process. Msg1 includes the preamble selected by the terminal. After receiving Msg1 and detecting the preamble in Msg1, the network device sends Msg2 to the terminal. Msg2 includes the aforementioned preamble and a random access response (such as RAR or RA response).

[0137] Step 802: If no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window, the terminal sends a second random access request message to the network device. The first random access preamble is the random access preamble carried in the first random access request message, and the maximum backoff time of the second random access request message is greater than or equal to twice the duration of the synchronization signal block (SSB) period. The SSB period is the SSB period of the network system currently performing random access. Correspondingly, the network device receives the second random access request message from the terminal.

[0138] In one implementation, when a terminal sends a first random access request message to a network device, multiple terminals may choose the same RO to send the first random access request message. In this case, the first random access request messages from these multiple terminals will collide, causing the first random access request message to fail to be sent. The network device will not be able to receive the first random access request message normally, nor will it be able to respond to it. The terminal will not be able to detect Msg2 carrying the preamble from the first random access request message within the random access detection fallback window. At this point, the terminal determines that the first random access request message has failed, and after waiting for the fallback period, the terminal sends a second random access request message to the network device to re-initiate random access.

[0139] In some embodiments, when a terminal determines the backoff duration, it randomly selects a backoff duration between 0 and the maximum backoff duration. In this embodiment, to address the problem that the original maximum backoff duration is inapplicable to the extended SSB period in an NTN network, a new maximum backoff duration is set based on the extended SSB period. The new maximum backoff duration is related to the length of the SSB period, for example, it is twice or more the length of the SSB period. This significantly reduces the probability that the selected backoff duration will fall within the same SSB period when a terminal sending a Msg1 collision chooses a backoff duration, and also significantly reduces the probability of a collision when the terminal retransmits Msg1, thereby improving the success rate of random re-access. Furthermore, compared to the conventionally fixed maximum backoff duration in existing technologies, this embodiment can adjust the maximum backoff duration according to the SSB period of the network system, thereby improving the flexibility of configuring the maximum backoff duration.

[0140] In some embodiments, the SSB period is greater than or equal to 120 milliseconds. For example, in an NTN network, the SSB period may be extended to 120 milliseconds or more, such as 240 milliseconds, 360 milliseconds, 640 milliseconds, etc. In this embodiment, the maximum backoff duration can be determined based on the SSB period of the network system to which the terminal randomly accesses. For example, when the SSB period is 120 milliseconds, the terminal sets the maximum backoff duration to 240 milliseconds or more. As another example, when the SSB period is 640 milliseconds, the terminal sets the maximum backoff duration to 1280 milliseconds or more. Thus, when a terminal experiencing a Msg1 collision selects a backoff duration, it will have a higher probability of choosing a backoff duration located in a different SSB period.

[0141] In some embodiments, the maximum backoff duration is related to the values ​​of the leading backoff parameter and / or the scaling factor. Specifically, the leading backoff parameter is greater than or equal to twice the duration of the SSB period, and / or the scaling factor is an integer greater than 1. Thus, in this embodiment, the leading backoff parameter is set to be twice or more the duration of the SSB period, and a corresponding scaling factor is set. The maximum backoff duration is determined by combining the leading backoff parameter and the scaling factor, thereby ensuring that the maximum backoff duration in this embodiment is twice or more the duration of the SSB period of the network system.

[0142] As an example, the maximum backoff duration is the leading backoff parameter. In this case, the value of the leading backoff parameter is greater than or equal to twice the duration of the SSB period, and correspondingly, the maximum backoff duration is also greater than or equal to twice the duration of the SSB period.

[0143] As another example, the maximum backoff duration is the product of the leading backoff parameter and the scaling factor. For instance, with a scaling factor of 2 and a leading backoff parameter of 3 times the SSB period, the maximum backoff duration is 6 times the SSB period.

[0144] It should be noted that, in the embodiments of this application, in scenarios of initial terminal access, handover, or reselection, the terminal can also determine the maximum backoff duration based on the scaling factor, thereby lengthening the maximum backoff duration and further increasing the probability that the backoff duration selected by the colliding terminal falls within different SSB cycles. For example, when determining the maximum backoff duration in an NTN network, it is agreed to determine the maximum backoff duration according to the scaling factor configured in the system message.

[0145] Optionally, the scaling factor is an integer greater than or equal to 1. The specific value of the scaling factor can be determined by the value of the corresponding bit in the system message. For example, if the scaling factor occupies two bits in the system message, the scaling factor is 1 when both bits are "00"; 2 when both bits are "01"; 3 when both bits are "10"; and 4 when both bits are "11". It is understood that network devices can also indicate the scaling factor value to the terminal in other ways, and this application does not limit this.

[0146] In some embodiments, this application may further extend the preamble backoff parameter to determine the maximum backoff duration with a larger preamble backoff parameter, thereby making the determined maximum backoff duration larger. This can further reduce the probability of a collision occurring again when the terminal initiates a re-random access, and improve the success rate of the terminal's random access. For example, in this application, the value of the preamble backoff parameter is extended to include at least one of the following: 1280 milliseconds, 1920 milliseconds, or 2760 milliseconds.

[0147] As an example, the values ​​of the expanded leading backoff parameter are shown in Table 2 below:

[0148] Table 2 shows the values ​​of the expanded leading backoff parameters.

[0149] In some embodiments, the maximum backoff duration applies to the RO that sends the first random access request information; or, the maximum backoff duration applies to the RO corresponding to the SSB that sends the first random access request information.

[0150] As an example, if Terminal 1 and Terminal 2 collide in the RO that sent the first random access request information, and Terminal 1 subsequently initiates random access in that RO, there is still a high probability that Terminal 1 and Terminal 2 will collide again. In this case, Terminal 1 initiating random access based on the maximum backoff duration can reduce the probability of another collision when Terminal 1 initiates random access again, thus increasing the success rate of Terminal 1's random access. If Terminal 1 subsequently chooses to initiate random access in another RO, the probability of Terminal 1 colliding with Terminal 2 again is relatively small. In this case, Terminal 1 does not need to initiate random access based on the maximum backoff duration. Therefore, the maximum backoff duration can be applied only to the RO that sent the first random access request information, or the RO corresponding to the SSB that sent the first random access request information, without limiting the terminal to re-initiating random access requests in other ROs.

[0151] To address the issue of significant latency in random access caused by a terminal re-initiating random access with a different SSB index than during the previous random access process, this application also provides a communication method to reduce latency during the terminal's random access process, as shown in Figure 9. This method specifically includes:

[0152] Step 901: The terminal sends a first random access request to the network device from the first RO. Correspondingly, the network device receives the first random access request from the terminal.

[0153] The specific implementation of step 901 can be referred to step 801 above, and will not be repeated here.

[0154] Step 902: If the terminal does not receive a response to the first random access request within the random access detection backoff time window, it re-initiates random access on the second RO. If the terminal re-initiates random access twice on the same RO, the re-initiated random access must be initiated within the SSB period after the randomly selected backoff time. If the terminal re-initiates random access twice on different ROs, the re-initiated random access is not limited by the backoff time and can arbitrarily choose the backoff time based on current network requirements.

[0155] In one implementation, if the terminal does not receive a response message after sending the first random access request, it indicates that the first random access request has failed to be sent. In this case, the terminal needs to wait for the rollback period before re-initiating random access. However, if the terminal reselects the optimal SSB after the first random access request fails, the terminal can directly re-initiate random access based on the newly selected optimal SSB without waiting for the rollback period.

[0156] It should be noted that there is a correspondence between SSB and RO. Therefore, after the terminal reselects an SSB, the RO for which the terminal sends the random access request information will also be different from before. Thus, the terminal can determine the applicable scope of the fallback time at the RO level. For example, the terminal's fallback time only applies to the same RO. If the RO for which the terminal resends the random access request message is the same as the RO for the previous random access request message, the terminal re-initiates random access based on the fallback time. If the RO for which the terminal resends the random access request message is different from the RO for the previous random access request message, the terminal can directly re-initiate random access without waiting for the fallback time.

[0157] As an example, referring to Figure 6 above, both Terminal 1 and Terminal 2 selected SSB index #21 for random access. A random access collision occurred between Terminal 1 and Terminal 2, causing message 1 to fail. However, due to measurement errors, SSB index #21 selected by Terminal 1 is not the optimal SSB index; the optimal index for Terminal 1 is SSB index #1. After the random access failure, the terminal re-measures the SSB and selects SSB index #1 as the optimal SSB index. In this case, the terminal can directly redetermine the preamble and RO based on SSB index #1 and send message 1 based on the redetermined preamble on the redetermined RO, without waiting for the backoff time before re-initiating random access.

[0158] In some embodiments, the first RO and the second RO are different, including at least one of the following: the first RO and the second RO are ROs corresponding to different SSBs; or, the first RO and the second RO are different ROs corresponding to the same SSB. In other words, if the terminal re-initiates random access on ROs corresponding to different SSBs, the re-initiated random access is not subject to the rollback duration limit, and the rollback duration can be arbitrarily selected based on the current network requirements. Alternatively, if the terminal re-initiates random access on different ROs corresponding to the same SSB, the re-initiated random access is not subject to the rollback duration limit, and the rollback duration can be arbitrarily selected based on the current network requirements.

[0159] In some embodiments, the first RO and the second RO are identical, including at least one of the following: the first RO and the second RO are ROs corresponding to the same SSB; or the first RO and the second RO have the same time-frequency resources. In other words, if the terminal re-initiates random access on the RO corresponding to the same SSB, the re-initiated random access needs to be initiated within the SSB period after the randomly selected backoff duration. Alternatively, if the terminal re-initiates random access on an RO with the same time-frequency resources, the re-initiated random access needs to be initiated within the SSB period after the randomly selected backoff duration.

[0160] It is understood that, in the above embodiments, the methods and / or steps implemented by the terminal can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the terminal; similarly, the methods and / or steps implemented by the network device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the network device. The chip system can be composed of chips, or it can include chips and other discrete devices.

[0161] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0162] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0163] For example, Figure 10 is a schematic diagram of a communication device 1000 provided in an embodiment of this application. The communication device 1000 includes a transceiver module 1002. Optionally, it includes a processing module 1001. The transceiver module 1002, also known as a transceiver unit, is used to implement transceiver functions. For example, it can be a transceiver circuit, a transceiver, a transceiver device, or a communication interface.

[0164] Taking the communication device 1000 as a terminal in the above method embodiment, or a device containing the above terminal, or a component that can be used in the terminal as an example, then: the transceiver module 1002 is used to send a first random access request message; the processing module 1001 is used to instruct the transceiver module 1002 to send a second random access request message if no random access response message corresponding to the first random preamble is detected within the random access detection backoff time window, wherein the first random access preamble is the random access preamble carried in the first random access request message, and the maximum backoff time of the second random access request message is greater than or equal to twice the duration of the synchronization signal block (SSB) period, wherein the SSB period is the SSB period of the network system currently accessing the network.

[0165] In one possible implementation, the SSB period is greater than or equal to 120 milliseconds.

[0166] In one possible implementation, the maximum backoff duration is related to the value of the leading backoff parameter and / or the scaling factor; wherein the value of the leading backoff parameter is greater than or equal to twice the duration of the SSB period, and / or the value of the scaling factor is an integer greater than 1.

[0167] In one possible implementation, the value of the leading backoff parameter includes at least one of the following: 1280 milliseconds, 1002 milliseconds, or 2760 milliseconds.

[0168] In one possible implementation, the scaling factor is less than or equal to 4.

[0169] In one possible implementation, the maximum backoff duration is applicable to the RO that sends the first random access request information; or, the maximum backoff duration is applicable to the RO corresponding to the SSB that sends the first random access request information.

[0170] Taking the communication device 1000 as a terminal in the above method embodiment, or a device containing the above terminal, or a component that can be used in a terminal, as an example: the transceiver module 1002 is used to send a first random access request message on the first random access time RO. The processing module 1001 is used to instruct the transceiver module 1002 to send a second random access request message on the second RO if no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window, wherein the first random access preamble is the random access preamble carried in the first random access request message; wherein, when the first RO and the second RO are the same, the second RO is located outside the backoff time of the random access request message configured by the access network device; when the first RO and the second RO are different, the second RO is located within the backoff time, or the second RO is located outside the backoff time.

[0171] In one possible implementation, the first RO and the second RO are different, including at least one of the following: the first RO and the second RO are ROs corresponding to different SSBs; or, the first RO and the second RO are different ROs corresponding to the same SSB.

[0172] In one possible implementation, the first RO and the second RO are the same, including at least one of the following: the first RO and the second RO are ROs corresponding to the same SSB; or the first RO and the second RO have the same time-frequency resources.

[0173] Taking the communication device 1000 as a network device in the above method embodiment, or a device containing the above network device, or a component that can be used in a network device as an example, then: the transceiver module 1002 is used to receive a first random access request information; the transceiver module 1002 is also used to receive a second random access request message; wherein, the second random access request message is sent by the terminal when no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window; the first random access preamble is the random access preamble carried in the first random access request information sent by the terminal, and the maximum backoff time of the second random access request information is greater than or equal to twice the duration of the synchronization signal block (SSB) period, wherein the SSB period is the SSB period of the network system currently accessing the network.

[0174] In one possible implementation, the SSB period is greater than or equal to 120 milliseconds.

[0175] In one possible implementation, the maximum backoff duration is related to the value of the leading backoff parameter and / or the scaling factor; wherein the value of the leading backoff parameter is greater than or equal to twice the duration of the SSB period, and / or the value of the scaling factor is an integer greater than 1.

[0176] In one possible implementation, the value of the leading backoff parameter is 1280 milliseconds, 1920 milliseconds, or 2760 milliseconds.

[0177] In one possible implementation, the scaling factor is less than or equal to 4.

[0178] In one possible implementation, the maximum backoff duration is applicable to the RO that sent the first random access request information; or, the maximum backoff duration is applicable to the RO corresponding to the SSB resource that sent the first random access request information.

[0179] Taking the communication device 1000 as a network device in the above method embodiment, or a device containing the above network device, or a component that can be used in a network device as an example, then: the transceiver module 1002 is used to receive first random access request information; the transceiver module 1002 is also used to receive a second random access request message sent on the second RO; wherein, the second random access request message is sent by the terminal when no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window; the first random access preamble is the random access preamble carried in the first random access request information; when the first RO and the second RO are the same, the second RO is located outside the backoff time of the random access request information configured by the access network device; when the first RO and the second RO are different, the second RO is located within the backoff time, or the second RO is located outside the backoff time.

[0180] In one possible implementation, the first RO and the second RO are different, including at least one of the following: the first RO and the second RO are ROs corresponding to different SSBs; or, the first RO and the second RO are different ROs corresponding to the same SSB.

[0181] In one possible implementation, the first RO and the second RO are the same, including at least one of the following: the first RO and the second RO are ROs corresponding to the same SSB; or the first RO and the second RO have the same time-frequency resources.

[0182] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0183] Optionally, the communication device 1000 may further include a storage module 1003, which may be used to store instructions and / or data, and the processing module 1001 may read the instructions and / or data in the storage module 1003.

[0184] In this application, the communication device 1000 can be presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0185] Alternatively, the modules in the communication device 1000 can be implemented in software, hardware, or a combination of both. When any of the above modules are implemented in software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a system-on-chip (SoC) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes the software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0186] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a general-purpose central processing unit (CPU), microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0187] In some embodiments, when the communication device 1000 in FIG10 is a chip or chip system, the function / implementation process of the transceiver module 1002 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1001 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0188] Since the communication device 1000 provided in this embodiment can execute the above method, the technical effects it can obtain can be referred to the above method embodiment, and will not be repeated here.

[0189] As a possible product form, the terminal or network device described in the embodiments of this application can also be implemented using one or more FPGAs, PLDs, controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0190] As another possible product form, the terminal or network device described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, refer to FIG11, which is a schematic diagram of the structure of a communication device 1100 provided in an embodiment of this application. The communication device 1100 includes a processor 1101 and a transceiver 1102. The communication device 1100 can be a terminal, or a chip or chip system therein; or, the communication device 1100 can be a network device, or a chip or chip system therein. FIG11 only shows the main components of the communication device 1100. In addition to the processor 1101 and transceiver 1102, the communication device may further include a memory 1103 and input / output devices (not shown in the figure).

[0191] Optionally, the processor 1101 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 1103 is mainly used to store software programs and data. The transceiver 1102 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0192] Optionally, the processor 1101, transceiver 1102, and memory 1103 can be connected via a communication bus.

[0193] When the communication device is powered on, the processor 1101 can read the software program in the memory 1103, 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 processor 1101 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes 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 processor 1101. The processor 1101 converts the baseband signal into data and processes the data.

[0194] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0195] In some embodiments, those skilled in the art will recognize that the above-described communication device 1000 can take the form of the communication device 1100 shown in FIG11 in terms of hardware implementation.

[0196] As an example, the functions / implementation of the processing module 1001 and transceiver module 1002 in FIG10 can be implemented by the processor 1101 in the communication device 1100 shown in FIG11 calling computer execution instructions stored in memory 1103. Alternatively, the functions / implementation of the processing module 1001 in FIG10 can be implemented by the processor 1101 in the communication device 1100 shown in FIG11 calling computer execution instructions stored in memory 1103, and the functions / implementation of the transceiver module 1002 in FIG10 can be implemented by the transceiver 1102 in the communication device 1100 shown in FIG11.

[0197] As another possible product form, the terminal or network device in this application may adopt the composition structure shown in FIG12, or include the components shown in FIG12. FIG12 is a schematic diagram of the composition of a communication device 1200 provided in this application. The communication device 1200 may be a network device or a module, chip or system-on-a-chip in a network device; or the communication device 1200 may be a terminal or a module, chip or system-on-a-chip in a terminal.

[0198] As shown in Figure 12, the communication device 1200 includes at least one processor 1201 and at least one communication interface (Figure 12 is merely an example illustrating the inclusion of a communication interface 1204 and a processor 1201). Optionally, the communication device 1200 may also include a communication bus 1202 and a memory 1203.

[0199] Processor 1201 may be a CPU, a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 1201 may also be other devices with processing functions, such as circuits, devices, one or more integrated circuits or software modules for controlling the execution of the program of this application, without limitation.

[0200] The communication bus 1202 is used to connect different components in the communication device 1200, enabling communication between them. The communication bus 1202 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 12, but this does not indicate that there is only one bus or one type of bus.

[0201] The communication interface 1204 is used for communicating with other devices or communication networks. For example, the communication interface 1204 can be a module, circuit, transceiver, or any device capable of communication, such as an Ethernet interface, RAN interface, WLAN interface, transceiver, pin, bus, interface circuit, or transceiver circuit. Optionally, the communication interface 1204 can also be an input / output interface located within the processor 1201, used to implement signal input and signal output for the processor.

[0202] The memory 1203 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.

[0203] For example, memory 1203 may be read-only memory (ROM) or other types of static storage devices capable of storing static information and / or instructions; it may also be random access memory (RAM) or other types of dynamic storage devices capable of storing information and / or instructions; it may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0204] It should be noted that the memory 1203 can exist independently of the processor 1201, or it can be integrated with the processor 1201. The memory 1203 can be located inside or outside the communication device 1200, without limitation.

[0205] The memory stores the computer execution instructions involved in the implementation of the solution provided in this solution, and the processor controls the execution of these instructions. The processor executes the computer execution instructions stored in the memory to implement the method provided in this solution. Alternatively, in this solution, the processor may execute the processing-related functions of the method provided below, and the communication interface is responsible for communicating with other devices or communication networks; this solution does not specifically limit this aspect.

[0206] Optionally, the computer execution instructions in this solution can also be referred to as application code, and this solution does not specifically limit this.

[0207] As an optional implementation, the communication device 1200 may also include an output device 1205 and an input device 1206. The output device 1205 communicates with the processor 1201 and can display information in various ways. For example, the output device 1205 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1206 communicates with the processor 1201 and can receive user input in various ways. For example, the input device 1206 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0208] In some embodiments, those skilled in the art will recognize that the communication device 1000 shown in FIG10 can take the form of the communication device 1200 shown in FIG12 in terms of hardware implementation.

[0209] As an example, the functions / implementation of the processing module 1001 and transceiver module 1002 in Figure 10 can be implemented by the processor 1201 in the communication device 1200 shown in Figure 12 calling computer execution instructions stored in the memory 1203. Alternatively, the functions / implementation of the processing module 1001 in Figure 10 can be implemented by the processor 1201 in the communication device 1200 shown in Figure 12 calling computer execution instructions stored in the memory 1203, and the functions / implementation of the transceiver module 1002 in Figure 10 can be implemented by the communication interface 1204 in the communication device 1200 shown in Figure 12.

[0210] It should be noted that the structure shown in Figure 12 does not constitute a specific limitation on the network device. For example, in other embodiments of this application, the network device may include more or fewer components than shown in the figure, or combine some components, or split some components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0211] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0212] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0213] As one possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0214] As one possible implementation, the communication device further includes a communication interface for communicating with modules outside the communication device. For example, the processor can be coupled to memory via the communication interface, causing the methods in any of the above method embodiments to be executed when the processor executes a computer program or instructions in the memory.

[0215] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0216] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0217] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0218] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0219] It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0220] The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. The components shown as units may or may not be physical units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0221] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0222] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

[0223] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0224] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, include: Send the first random access request information; If no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window, a second random access request message is sent. The first random access preamble is the random access preamble carried in the first random access request message. The maximum backoff time of the second random access request message is greater than or equal to twice the duration of the synchronization signal block (SSB) period, where the SSB period is the SSB period of the network system currently accessing the random access.

2. The method according to claim 1, characterized in that, The SSB period is greater than or equal to 120 milliseconds.

3. The method according to any one of claims 1-2, characterized in that, The maximum rollback duration is related to the values ​​of the leading rollback parameter and / or scaling factor; Wherein, the value of the leading backoff parameter is greater than or equal to twice the duration of the SSB period, and / or, the value of the scaling factor is an integer greater than 1.

4. The method according to claim 3, characterized in that, The value of the leading backoff parameter includes at least one of the following: 1280 milliseconds, 1920 milliseconds, or 2760 milliseconds.

5. The method according to claim 3 or 4, characterized in that, The scaling factor is less than or equal to 4.

6. The method according to any one of claims 1-5, characterized in that, The maximum backoff duration applies to the RO that sends the first random access request information; or, the maximum backoff duration applies to the RO corresponding to the SSB that sends the first random access request information.

7. A communication method, characterized in that, include: Send the first random access request information at the first random access opportunity (RO); If no random access response information corresponding to the first random preamble is detected within the random access detection backoff time window, a second random access request message is sent on the second RO, where the first random access preamble is the random access preamble carried in the first random access request information; wherein, when the first RO and the second RO are the same, the second RO is located outside the backoff time of the random access request information configured by the access network device; When the first RO and the second RO are different, the second RO is located within the rollback duration, or the second RO is located outside the rollback duration.

8. The method according to claim 7, characterized in that, The first RO and the second RO differ in that they include at least one of the following: The first RO and the second RO are ROs corresponding to different SSBs; Alternatively, the first RO and the second RO may be different ROs corresponding to the same SSB.

9. The method according to claim 7, characterized in that, The first RO and the second RO are the same, including at least one of the following: The first RO and the second RO are ROs corresponding to the same SSB; Alternatively, the first RO and the second RO may have the same time-frequency resources.

10. A communication device, characterized in that, include: A functional unit for performing the method as described in any one of claims 1-9; wherein the action performed by the functional unit is implemented by hardware or by hardware executing corresponding software.

11. A communication device, characterized in that, include: processor; The processor is connected to a memory for storing computer execution instructions, and the processor executes the computer execution instructions stored in the memory to enable the communication device to implement the method as described in any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-9.

13. A chip, characterized in that, The chip includes a processor; the processor is connected to a memory for storing computer execution instructions, and the processor executes the computer execution instructions stored in the memory to enable the communication device to implement the method as described in any one of claims 1-9.

14. A computer program product containing instructions, characterized in that, When it is operated on a communication device, it causes the communication device to perform the method as described in any one of claims 1-9.

Images