Communication method, and terminal, network device, communication device and storage medium

Abstract

The present disclosure relates to a communication method, and a terminal, a network device, a communication device and a storage medium. The method comprises: a terminal executing a GNSS measurement in a measurement gap; and the terminal sending a first random access sequence to a network device, wherein the first random access sequence is used for indicating that the execution of the GNSS measurement succeeds or the execution thereof fails. By means of the solution of the present disclosure, a terminal and a network device can reach an agreement on the execution condition of a GNSS measurement performed by the terminal in a measurement gap.

Description

Communication method, terminal, network device, communication device and storage medium Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies, and in particular to a communication method, a terminal, a network device, a communication device, and a storage medium. Background Art

[0002] Global navigation satellite system (GNSS) and cellular modules are often embedded in devices such as wearables, mobile phones, laptops, and Internet of Things (IoT) devices. GNSS modules calculate the terminal's position by receiving signals from multiple satellite systems, effectively positioning the terminal. Once the terminal has acquired its position, it can perform uplink synchronization compensation.

[0003] Summary of the Invention

[0004] In satellite communications, the terminal and network equipment need to reach an agreement on how to perform GNSS measurements within a measurement gap.

[0005] Embodiments of the present disclosure provide a communication method, a terminal, a network device, a communication device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is proposed, performed by a terminal, comprising: performing GNSS measurement within a measurement gap; and sending a first random access sequence, wherein the first random access sequence is used to indicate success or failure of the GNSS measurement.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is proposed, which is performed by a network device. The method includes: receiving a first random access sequence, wherein the first random access sequence is used to indicate whether a GNSS measurement performed by a terminal in a measurement gap is successful or failed.

[0008] According to a third aspect of an embodiment of the present disclosure, a communication method is provided, performed by a communication system. The method includes: a terminal performing a GNSS measurement within a measurement gap; and the terminal sending a first random access sequence to a network device, wherein the first random access sequence is used to indicate success or failure of the GNSS measurement.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided. The terminal includes: a first processing module configured to perform GNSS measurement within a measurement gap; and a first transceiver module configured to send a first random access sequence, wherein the first random access sequence is used to indicate success or failure of the GNSS measurement.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a network device is provided, comprising: a second transceiver module configured to receive a first random access sequence, wherein the first random access sequence is used to indicate a success or failure of a GNSS measurement.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a communication device is provided. The communication device includes: one or more processors; and one or more memories for storing instructions; wherein the processor is configured to invoke the instructions so that the communication device executes the communication method according to any one of the first and second aspects.

[0012] According to a seventh aspect of the embodiments of the present disclosure, a communication system is provided, which includes a terminal and a network device, wherein the terminal is configured to implement the communication method described in the first aspect, and the network device is configured to implement the communication method described in the second aspect.

[0013] According to an eighth aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed by a processor, they perform the communication method described in the first aspect or the second aspect.

[0014] According to a ninth aspect of the embodiments of the present disclosure, a computer program or computer program product is provided. The computer program or computer program product includes code. When the instructions are executed by a processor, the communication method according to the first or second aspect is performed.

[0015] The technical solution provided by the embodiments of the present disclosure enables a terminal and a network device to reach an agreement on the execution status of the GNSS measurement of the terminal within a measurement gap.

[0016] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

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

[0019] FIG1B is a schematic diagram of a scenario of uplink and downlink alignment on a network device side according to an embodiment of the present disclosure.

[0020] FIG1C is a schematic diagram showing a scenario in which uplink and downlink are not aligned on the network device side according to an embodiment of the present disclosure.

[0021] FIG2A is a schematic diagram of a first flow chart of a communication method according to an embodiment of the present disclosure.

[0022] FIG2B is a schematic diagram of a second flow chart of a communication method according to an embodiment of the present disclosure.

[0023] FIG2C is a schematic diagram of a third flow chart of a communication method according to an embodiment of the present disclosure.

[0024] FIG2D is a fourth flow chart of a communication method according to an embodiment of the present disclosure.

[0025] FIG2E is a fifth flow chart of a communication method according to an embodiment of the present disclosure.

[0026] FIG2F is a sixth flow chart of a communication method according to an embodiment of the present disclosure.

[0027] FIG3A is a schematic diagram of a first flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.

[0028] FIG3B is a schematic diagram of a second flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.

[0029] FIG3C is a schematic diagram of a third flow chart of a method for executing communication on a terminal side according to an embodiment of the present disclosure.

[0030] FIG3D is a fourth flow chart of a method for executing communication on a terminal side according to an embodiment of the present disclosure.

[0031] FIG3E is a fifth flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.

[0032] FIG3F is a sixth flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.

[0033] FIG4A is a schematic diagram of a first flow chart of a network device side communication method according to an embodiment of the present disclosure.

[0034] FIG4B is a schematic diagram of a second flow chart of a communication method executed on a network device side according to an embodiment of the present disclosure.

[0035] FIG4C is a schematic diagram of a third flow chart of a communication method executed on a network device side according to an embodiment of the present disclosure.

[0036] FIG4D is a fourth flow chart illustrating a method for executing communication by a network device according to an embodiment of the present disclosure.

[0037] FIG4E is a fifth flow chart illustrating a communication method executed on a network device side according to an embodiment of the present disclosure.

[0038] FIG4F is a sixth flow chart of a communication method executed on a network device side according to an embodiment of the present disclosure.

[0039] FIG5A is a seventh flow chart illustrating a method for executing communication on a terminal side according to an embodiment of the present disclosure.

[0040] FIG5B is a seventh flow chart illustrating a communication method executed on a network device side according to an embodiment of the present disclosure.

[0041] FIG6 is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure.

[0042] FIG7A is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0043] FIG7B is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0044] FIG8A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.

[0045] FIG8B is a schematic structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0046] Embodiments of the present disclosure provide a communication method and terminal, a network device, a communication device, a system, and a computer-readable storage medium.

[0047] In a first aspect, embodiments of the present disclosure provide a communication method, performed by a terminal, comprising: performing GNSS measurement within a measurement gap; and sending a first random access sequence, wherein the first random access sequence is used to indicate success or failure of the GNSS measurement.

[0048] In the above embodiment, the terminal indicates whether it has successfully performed GNSS measurement within the measurement gap by sending a first random access sequence to the network device. In this way, the terminal and the network device can reach an agreement on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0049] In combination with some embodiments of the first aspect, in some embodiments, sending the first random access sequence includes: sending a first message, where the first message carries the first random access sequence, and the first message is used by the terminal to initiate a random access process.

[0050] In the above embodiment, the terminal can carry the first random access sequence through the first message in the random access process, such as msg1, to indicate to the network device whether it has successfully performed GNSS measurement within the measurement gap. In this way, the terminal and the network device can reach an agreement on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0051] In combination with some embodiments of the first aspect, in some embodiments, when the GNSS measurement is successfully executed, before sending the first random access sequence, the above method also includes: determining the first random access sequence associated with the GNSS validity period of the terminal based on the correspondence between the random access channel sequence and the GNSS validity period.

[0052] In the above embodiment, in a contention-based random access scenario, a correspondence exists between the random access sequence and the GNSS validity period. Based on this correspondence, the terminal can select an appropriate random access sequence to indicate to the network device that the terminal has successfully performed GNSS measurements within the measurement gap and determine the corresponding GNSS validity period. In this way, by sending the random access sequence once, the terminal can not only reach an agreement with the network device on the results of the terminal's GNSS measurement within the measurement gap, but also indicate the terminal's GNSS validity period to the network device and trigger the random access process, thereby reducing signaling overhead and saving terminal power consumption.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the random access sequence is used for a contention-based random access procedure of a terminal.

[0054] In combination with some embodiments of the first aspect, in some embodiments, when the GNSS measurement is successfully performed, the first random access sequence is configured by the network device for a non-contention-based random access procedure of the terminal.

[0055] In the above embodiment, in the non-contention-based random access scenario, the terminal can send a configured random access sequence to the network device, indicating to the network device that it has successfully performed GNSS measurements within the measurement gap, and simultaneously initiate a non-contention-based random access procedure. In this way, by sending the random access sequence once, the terminal can reach an agreement with the network device on the results of the terminal's GNSS measurements within the measurement gap and trigger the non-contention-based random access procedure, thereby reducing signaling overhead and saving terminal power consumption.

[0056] In combination with some embodiments of the first aspect, in some embodiments, when the GNSS measurement is successfully executed, before sending the first random access sequence, the above method also includes: obtaining at least one second random access sequence associated with the successful execution of the GNSS measurement; and determining the first random access sequence from the at least one second random access sequence.

[0057] In the above embodiment, the terminal can determine a random access sequence from at least one random access sequence successfully associated with a GNSS measurement to indicate to the network device that it has successfully performed a GNSS measurement within the measurement gap and trigger a random access procedure. In this way, by sending the random access sequence once, the terminal can both reach an agreement with the network device on the results of the terminal's GNSS measurement within the measurement gap and trigger the random access procedure, thereby reducing signaling overhead and saving terminal power consumption.

[0058] In combination with some embodiments of the first aspect, in some embodiments, the above method further includes: sending first time information, where the first time information is used to indicate a GNSS validity period of the terminal.

[0059] In the above embodiment, after the terminal indicates to the network device that it has successfully performed GNSS measurement within the measurement gap, it can also indicate its own GNSS validity period to the network device so that the network device can configure the corresponding measurement gap for the terminal according to the time information sent by the terminal to improve the efficiency of GNSS positioning.

[0060] In combination with some embodiments of the first aspect, in some embodiments, in the event that the GNSS measurement fails, before sending the first random access sequence, the above method also includes: obtaining at least one third random access sequence associated with the GNSS measurement failure; and determining the first random access sequence from the at least one third random access sequence.

[0061] In the above embodiment, the terminal can determine a random access sequence from at least one random access sequence associated with a GNSS measurement failure to indicate to the network device that the terminal failed to perform a GNSS measurement within the measurement gap. In this way, the terminal and the network device can reach a consensus on the results of the GNSS measurement performed by the terminal, avoiding information asymmetry between the terminal and the network device.

[0062] In combination with some embodiments of the first aspect, in some embodiments, when the GNSS measurement fails, the above method also includes: determining that the validity period of the GNSS currently used by the terminal has expired; entering an idle state or determining that a radio link failure (RLF) has occurred.

[0063] In combination with some embodiments of the first aspect, in some embodiments, when the GNSS measurement fails, the above method also includes: determining that the validity period of the GNSS currently used by the terminal has not expired; and maintaining a connected state until the validity period of the GNSS currently used by the terminal expires.

[0064] In a second aspect, embodiments of the present disclosure provide a communication method, performed by a network device, comprising: receiving a first random access sequence, wherein the first random access sequence is used to indicate whether a GNSS measurement performed by a terminal in a measurement gap is successful or failed.

[0065] In combination with some embodiments of the second aspect, in some embodiments, receiving the first random access sequence includes: receiving a first message, the first message carrying the first random access sequence, the first message being used by the terminal to initiate a random access process.

[0066] In combination with some embodiments of the second aspect, in some embodiments, the above method further includes: determining the GNSS validity period of the terminal associated with the first random access sequence according to the correspondence between the random access channel sequence and the GNSS validity period.

[0067] In combination with some embodiments of the second aspect, in some embodiments, the random access sequence is used for a contention-based random access procedure of the terminal.

[0068] In combination with some embodiments of the second aspect, in some embodiments, the above method also includes: sending first information, the first information is used to indicate the correspondence between the random access channel sequence and the GNSS validity period, and the correspondence is used by the terminal to determine the first random access sequence associated with the GNSS validity period.

[0069] In combination with some embodiments of the second aspect, in some embodiments, the first random access sequence is configured by the network device for a non-contention-based random access process of the terminal.

[0070] In combination with some embodiments of the second aspect, in some embodiments, the above method further includes: determining that the first random access sequence is a second random access sequence that is successfully associated with the GNSS measurement execution.

[0071] In combination with some embodiments of the second aspect, in some embodiments, the above method also includes: sending first configuration information, the first configuration information is used to indicate at least one second random access sequence that is successfully associated with the GNSS measurement execution, and the at least one second random access sequence is used by the terminal to determine the first random access sequence.

[0072] In combination with some embodiments of the second aspect, in some embodiments, the above method also includes: sending second configuration information, the second configuration information is used to indicate a fourth random access sequence associated with the random access process, and the fourth random access sequence is used by the terminal to initiate the random access process.

[0073] In combination with some embodiments of the second aspect, in some embodiments, the above method further includes: sending a second message, the second message carrying GNSS available time information, and the GNSS available time information is used to indicate the GNSS validity period of the terminal.

[0074] In combination with some embodiments of the second aspect, in some embodiments, the above method further includes: determining that the first random access sequence is a third random access sequence associated with a failure in performing GNSS measurement.

[0075] In combination with some embodiments of the second aspect, in some embodiments, the above method also includes: sending third configuration information, the third configuration information is used to indicate at least one third random access sequence associated with the failure of GNSS measurement execution, and the at least one third random access sequence is used by the terminal to determine the first random access sequence.

[0076] In a third aspect, embodiments of the present disclosure provide a communication method, performed by a communication system. The method includes: a terminal performing GNSS measurement within a measurement gap; and the terminal sending a first random access sequence to a network device, wherein the first random access sequence is used to indicate success or failure of the GNSS measurement.

[0077] In combination with some embodiments of the third aspect, in some embodiments, the terminal sends a first random access sequence to the network device, including: the terminal sends a first message to the network device, the first message carries the first random access sequence, and the first message is used by the terminal to initiate a random access process.

[0078] In combination with some embodiments of the third aspect, in some embodiments, when the GNSS measurement is successfully executed, before the terminal sends the first random access sequence to the network device, the above method also includes: the terminal determines the first random access sequence associated with the GNSS validity period of the terminal based on the correspondence between the random access channel sequence and the GNSS validity period, and the random access sequence is used for the terminal's contention-based random access process.

[0079] In combination with some embodiments of the third aspect, in some embodiments, when the GNSS measurement is successfully executed, after the terminal sends the first random access sequence to the network device, the above method also includes: the network device determines the GNSS validity period of the terminal associated with the first random access sequence based on the correspondence between the random access channel sequence and the GNSS validity period.

[0080] In combination with some embodiments of the third aspect, in some embodiments, the random access sequence is used for a contention-based random access procedure of the terminal.

[0081] In combination with some embodiments of the third aspect, in some embodiments, the above method further includes: the network device sends first information to the terminal, where the first information is used to indicate the correspondence between the random access channel sequence and the GNSS validity period.

[0082] In combination with some embodiments of the third aspect, in some embodiments, when the GNSS measurement is successfully performed, the first random access sequence is configured by the network device for a non-contention-based random access process of the terminal.

[0083] In combination with some embodiments of the third aspect, in some embodiments, when the GNSS measurement is successfully executed, before the terminal sends the first random access sequence to the network device, the above method also includes: the terminal obtains at least one second random access sequence associated with the successful execution of the GNSS measurement; the terminal determines the first random access sequence from the at least one second random access sequence.

[0084] In combination with some embodiments of the third aspect, in some embodiments, after the terminal sends the first random access sequence to the network device, the above method also includes: the network device determines that the first random access sequence is a second random access sequence that is successfully associated with the GNSS measurement execution.

[0085] In combination with some embodiments of the third aspect, in some embodiments, before the terminal sends a first random access sequence to the network device, the above method also includes: the network device sends first configuration information to the terminal, and the first configuration information is used to indicate at least one second random access sequence that is successfully associated with the GNSS measurement execution.

[0086] In combination with some embodiments of the third aspect, in some embodiments, the above method also includes: the network device sends second configuration information to the terminal, the second configuration information is used to indicate a fourth random access sequence associated with the random access process, and the fourth random access sequence is used by the terminal to initiate the random access process.

[0087] In combination with some embodiments of the third aspect, in some embodiments, the above method further includes: the terminal sending first time information to the network device, where the first time information is used to indicate the GNSS validity period of the terminal.

[0088] In combination with some embodiments of the third aspect, in some embodiments, in the event that the GNSS measurement fails, before the terminal sends the first random access sequence to the network device, the above method also includes: the terminal obtains at least one third random access sequence associated with the failure of the GNSS measurement; the terminal determines the first random access sequence from the at least one third random access sequence.

[0089] In combination with some embodiments of the third aspect, in some embodiments, after the terminal sends the first random access sequence to the network device, the above method also includes: the network device determines that the first random access sequence is a third random access sequence associated with the failure of GNSS measurement execution.

[0090] In combination with some embodiments of the third aspect, in some embodiments, before the terminal sends the first random access sequence to the network device, the above method also includes: the network device sends third configuration information to the terminal, and the third configuration information is used to indicate at least one third random access sequence associated with the failure of GNSS measurement execution.

[0091] In combination with some embodiments of the third aspect, in some embodiments, when the GNSS measurement fails, the above method also includes: the terminal determines that the validity period of the GNSS currently used by the terminal has expired; the terminal enters an idle state or determines that RLF occurs.

[0092] In combination with some embodiments of the third aspect, in some embodiments, when the GNSS measurement fails, the above method also includes: the terminal determines that the validity period of the GNSS currently used by the terminal has not expired; the terminal remains in a connected state until the validity period of the GNSS currently used by the terminal expires.

[0093] In a fourth aspect, embodiments of the present disclosure provide a terminal comprising: a first processing module configured to perform GNSS measurement within a measurement gap; and a first transceiver module configured to send a first random access sequence, wherein the first random access sequence is used to indicate success or failure of the GNSS measurement.

[0094] In combination with some embodiments of the fourth aspect, in some embodiments, the first transceiver module is used to send a first message, the first message carries a first random access sequence, and the first message is used for the terminal to initiate a random access process.

[0095] In combination with some embodiments of the fourth aspect, in some embodiments, the first processing module is used to determine a first random access sequence associated with the GNSS validity period of the terminal based on the correspondence between the random access channel sequence and the GNSS validity period when the GNSS measurement is successfully performed.

[0096] In combination with some embodiments of the fourth aspect, in some embodiments, the random access sequence is used for a contention-based random access procedure of the terminal.

[0097] In combination with some embodiments of the fourth aspect, in some embodiments, when the GNSS measurement is successfully performed, the first random access sequence is configured by the network device for a non-contention-based random access process of the terminal.

[0098] In combination with some embodiments of the fourth aspect, in some embodiments, the first processing module is used to obtain at least one second random access sequence associated with the successful execution of the GNSS measurement when the GNSS measurement is successfully executed; and determine the first random access sequence from the at least one second random access sequence.

[0099] In combination with some embodiments of the fourth aspect, in some embodiments, the first transceiver module is used to send first time information, where the first time information is used to indicate the GNSS validity period of the terminal.

[0100] In combination with some embodiments of the fourth aspect, in some embodiments, the first processing module is used to obtain at least one third random access sequence associated with the failure of GNSS measurement execution when the GNSS measurement fails; and determine the first random access sequence from the at least one third random access sequence.

[0101] In combination with some embodiments of the fourth aspect, in some embodiments, the first processing module is used to determine that the validity period of the GNSS currently used by the terminal has expired when the GNSS measurement fails; enter an idle state or determine that RLF occurs.

[0102] In combination with some embodiments of the fourth aspect, in some embodiments, the first processing module is used to determine that the validity period of the GNSS currently used by the terminal has not expired when the GNSS measurement fails; and remain in a connected state until the validity period of the GNSS currently used by the terminal expires.

[0103] In a fifth aspect, embodiments of the present disclosure provide a network device, comprising: a second transceiver module configured to receive a first random access sequence, wherein the first random access sequence is used to indicate whether a GNSS measurement performed by a terminal in a measurement gap is successful or failed.

[0104] In combination with some embodiments of the fifth aspect, in some embodiments, the second transceiver module is used to receive a first message, the first message carries a first random access sequence, and the first message is used for the terminal to initiate a random access process.

[0105] In combination with some embodiments of the fifth aspect, in some embodiments, the above-mentioned network device also includes: a second processing module, used to determine the GNSS validity period of the terminal associated with the first random access sequence based on the correspondence between the random access channel sequence and the GNSS validity period, and the random access sequence is used for the contention-based random access process of the terminal.

[0106] In combination with some embodiments of the fifth aspect, in some embodiments, the above-mentioned network device also includes: a first transceiver module, used to send first information, the first information is used to indicate the correspondence between the random access channel sequence and the GNSS validity period, and the correspondence is used by the terminal to determine the first random access sequence associated with the GNSS validity period of the terminal.

[0107] In combination with some embodiments of the fifth aspect, in some embodiments, the first random access sequence is configured by a network device for a non-contention-based random access process of a terminal.

[0108] In combination with some embodiments of the fifth aspect, in some embodiments, the second processing module is further configured to determine that the first random access sequence is a second random access sequence that is successfully associated with the GNSS measurement execution.

[0109] In combination with some embodiments of the fifth aspect, in some embodiments, the above-mentioned network device also includes: a first transceiver module, used to send first configuration information, the first configuration information is used to indicate at least one second random access sequence that is successfully associated with the GNSS measurement execution, and the at least one second random access sequence is used by the terminal to determine the first random access sequence.

[0110] In combination with some embodiments of the fifth aspect, in some embodiments, the first transceiver module is also used to send second configuration information, the second configuration information is used to indicate a fourth random access sequence associated with the random access process, and the fourth random access sequence is used by the terminal to initiate a random access process.

[0111] In combination with some embodiments of the fifth aspect, in some embodiments, the second transceiver module is used to receive first time information, where the first time information is used to indicate the GNSS validity period of the terminal.

[0112] In combination with some embodiments of the fifth aspect, in some embodiments, the above-mentioned network device further includes: a second processing module, used to determine that the first random access sequence is a third random access sequence associated with the failure of GNSS measurement execution.

[0113] In combination with some embodiments of the fifth aspect, in some embodiments, the above-mentioned network device also includes: a first transceiver module, used to send third configuration information, the third configuration information is used to indicate at least one third random access sequence associated with the failure of GNSS measurement execution, and the at least one third random access sequence is used by the terminal to determine the first random access sequence.

[0114] In a sixth aspect, embodiments of the present disclosure provide a communication device. The communication device includes: one or more processors; and one or more memories for storing instructions; wherein the processor is configured to invoke the instructions so that the communication device executes the communication method according to any one of the first aspect, the second aspect, and the embodiments thereof.

[0115] In a seventh aspect, embodiments of the present disclosure provide a communication system. The communication system includes a terminal and a network device, wherein the terminal is configured to implement the communication method as described in any one of the first aspect and its embodiments, and the network device is configured to implement the communication method as described in any one of the second aspect and its embodiments.

[0116] In an eighth aspect, an embodiment of the present disclosure provides a storage medium storing instructions that, when executed on a communication device, cause the communication device to execute the communication method according to any one of the first aspect, the second aspect, and the embodiments thereof.

[0117] In a ninth aspect, an embodiment of the present disclosure proposes a computer program product. When the computer program product is executed by a communication device, the communication device executes a communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof.

[0118] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a communication device, enables the computer to execute a communication method as described in any one of the first aspect, the second aspect, and their embodiments.

[0119] It is understandable that the above-mentioned terminals, network devices, communication devices, storage media, computer program products, and computer programs are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0120] The present disclosure provides a communication method, terminal, network device, communication device, and storage medium. In some embodiments, the terms communication method, information processing method, etc. are interchangeable. The terms terminal, network device, communication device, information processing device, etc. are interchangeable. The terms communication system, information processing system, etc. are interchangeable.

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

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

[0123] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0124] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

[0126] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," and the like can be used interchangeably.

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

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

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

[0130] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

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

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

[0133] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

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

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

[0136] In some embodiments, the terms “terminal,” “terminal device,” “user equipment (UE),” “user terminal,” “mobile station (MS),” “mobile terminal (MT),” “subscriber station,” “mobile unit,” “subscriber unit,” “wireless unit,” “remote unit,” “mobile device,” “wireless device,” “wireless communication device,” “remote device,” “mobile subscriber station,” “access terminal,” “mobile terminal,” “wireless terminal,” “remote terminal,” “handset,” “user agent,” “mobile client,” “client,” and the like may be used interchangeably.

[0137] In some embodiments, the access network device, core network device, or network device can be replaced by a terminal. For example, the communication between the access network device, core network device, or network device and the terminal is replaced by communication between multiple terminals (for example, device to device).

[0138] The embodiments of the present disclosure may also be applied to structures such as device-to-device (D2D), vehicle-to-everything (V2X), etc. In this case, the terminal may also have a structure that has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" may also be replaced with terms corresponding to inter-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be replaced with side channel, and uplink, downlink, etc. may be replaced with side link.

[0139] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

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

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

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

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

[0144] As shown in Figure 1A, a communication system 100 includes a terminal 101 and a network device 102. The network device 102 may be an access network device.

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

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

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

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

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

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

[0151] The embodiments of the present disclosure can be applied to long term evolution (LTE), LTE-advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, international mobile telecommunications-advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, ultra-wideband (UWB), Bluetooth (registered trademark), public land mobile network (PLMN) networks, device-to-device (D2D) systems, machine-to-machine (M2M) systems, Internet of Things (IoT) systems, vehicle-to-everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0152] In the disclosed embodiments, the continuous emergence of new internet applications such as augmented reality (AR), virtual reality (VR), and vehicle-to-vehicle (V2V) communication has placed higher demands on wireless communication technology, driving the continuous evolution of wireless communication technology to meet these application needs. Currently, cellular mobile communication technology is in the process of evolving into a new generation of technology. A key feature of this new generation of technology is the flexible configuration that supports multiple service types. Different service types have different requirements for wireless communication technology. For example, enhanced mobile broadband (eMBB) service types primarily require high bandwidth and high speed; ultra-reliable low-latency communications (URLLC) service types primarily require high reliability and low latency; and massive machine type communications (mMTC) service types primarily require a large number of connections. Therefore, the next generation of wireless communication systems requires flexible and configurable designs to support the transmission of multiple service types.

[0153] Satellite communications are considered a key aspect of future wireless communication technology. Satellite communications refer to communications conducted by ground-based radio communication equipment using satellites as relays. Satellite communication systems consist of satellite and ground components. Satellite communications are characterized by a wide range, enabling communication between any two points within the range of the satellite's radio waves, and high reliability, as well as being less susceptible to land-based disasters.

[0154] Satellite communications, as a supplement to terrestrial communication systems, offer the following advantages: 1. Extended coverage: Satellite communications can be used to address areas where cellular communication systems are inaccessible or costly, such as oceans, deserts, and remote mountainous areas. 2. Emergency communications: In extreme situations such as disasters (e.g., earthquakes) where cellular communication infrastructure is unavailable, satellite communications can quickly establish a connection. 3. Industry applications: For example, satellite communications can be used to reduce latency in long-distance, delay-sensitive services.

[0155] It is foreseeable that in future wireless communication systems, satellite communication systems and terrestrial cellular communication systems will gradually achieve deep integration, truly realizing the intelligent connection of all things.

[0156] In the embodiment of the present disclosure, in the scenario of satellite communication, due to the long signal transmission distance between the transmitter and the receiver, data transmission takes a long time. For transmission with uplink and downlink relationship, an offset parameter (K offset ) to compensate for the transmission delay. Among them, K offset It can be applied in various operations, such as physical uplink shared channel (PUSCH) transmission scheduled by downlink control information (DCI), transmission of hybrid automatic repeat request (HARQ) feedback information, and transmission of media access control (MAC) control element (CE).

[0157] In some embodiments, propagation delay in satellite communication systems is significantly longer than that in terrestrial mobile systems, ranging from a few milliseconds to hundreds of milliseconds depending on the altitude of the satellite or airborne platform and the type of payload in the satellite communication system. Therefore, in satellite communication systems, terminals need to apply a larger timing advance (TA) value, which can result in large offsets in their downlink (DL) and uplink (UL) frame timing. Figure 1B illustrates a scenario in which a terminal applies a larger TA and the DL and UL frames of a network device (e.g., an access network device) are aligned. Figure 1C illustrates another scenario in which alignment between the DL and UL frames of the access network device is not required. The terminal applies a terminal-specific TA (e.g., a UE-specific TA) to align the DL and UL frame timing at a predetermined reference point. However, for the scenario shown in Figure 1C, additional complexity is required on the network device side to manage the corresponding scheduling timing for this scenario. Therefore, various timing relationships need to be enhanced to cope with large offsets in the timing of the terminal's DL and UL frames.

[0158] Then, in the scenario of satellite communication, the terminal needs to know its own location information in order to perform uplink synchronization compensation. In some embodiments, the terminal can obtain its own location information through a navigation satellite system, such as a global navigation satellite system (GNSS).

[0159] In some embodiments, the global navigation satellite system (GNSS) may include China's Beidou Navigation Satellite System (BDS), the United States' Global Positioning System (GPS), Russia's GLONASS, and the European Union's Galileo Navigation Satellite System (GALILEO), among other navigation satellite systems and their evolutionary systems. Of course, other navigation systems may also be included, and the present disclosure does not specifically limit this.

[0160] In some embodiments, IoT terminals do not support simultaneous operation of the cellular and GNSS modules, but may support sporadic transmissions. After obtaining GNSS measurement results, the terminal may send GNSS availability information (indicating the GNSS validity duration) to the network device. When the terminal's GNSS validity duration expires, the terminal enters the idle state.

[0161] In some embodiments, after the terminal enters the IDLE state, the need to re-acquire the GNSS validity period will cause unnecessary delays. Therefore, the network device can trigger the terminal to perform GNSS measurements in the connected state to prevent the terminal from entering the IDLE state.

[0162] In some embodiments, before the terminal performs GNSS measurement, the terminal also needs to send time information required for the measurement (such as GNSS positioning duration information (used to indicate the GNSS position fix time duration)) to the network device, so that the network device can configure an appropriate measurement gap for the terminal. In one embodiment, the measurement gap can also be described as a GNSS measurement gap.

[0163] In some embodiments, if the terminal successfully performs GNSS measurement within the measurement gap, it can initiate a random access process based on the implementation. However, the network device is not clear whether the GNSS measurement of the terminal within the measurement gap is successful, which causes the terminal and the network device to be unable to reach a consensus on the execution status of the GNSS measurement, thereby affecting the random access process of the terminal.

[0164] It should be noted that the terms "GNSS measurement" and "GNSS positioning" are interchangeable. The terms "GNSS measurement successfully executed," "GNSS measurement successfully executed," "GNSS measurement successfully executed," "GNSS measurement successful," and "measurement success" are interchangeable. The terms "GNSS measurement failed to execute," "GNSS measurement unsuccessfully executed," "GNSS measurement unsuccessfully executed," "GNSS measurement failed," and "measurement failure" are interchangeable.

[0165] FIG2A is a first flow chart of a communication method according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which is used in a communication system 100. As shown in FIG2A, the communication method according to the embodiment of the present disclosure includes steps S2110 to S2140.

[0166] In step S2110, the network device sends first information.

[0167] In some embodiments, the terminal receives first information.

[0168] In some embodiments, the first information is used to indicate a correspondence between a random access sequence and a GNSS validity period.

[0169] In some embodiments, the correspondence between random access sequences and GNSS validity periods includes at least one random access sequence, and at least a portion of the random access sequences is successfully associated with GNSS measurement execution.

[0170] In some embodiments, the correspondence between the random access sequence and the GNSS validity period may be included in the random access configuration. The random access configuration may also be described as a physical random access channel (PRACH) configuration, such as RACH-Config. The random access configuration is used to indicate to the terminal the random access occasion (RACH occasion, RO) resources and at least one random access sequence configured by the network device for the terminal. Exemplarily, the random access sequence may also be referred to as a random access preamble sequence, random access preamble code, preamble sequence, preamble code, etc.

[0171] In some embodiments, the network device may further transmit a correspondence between a random access configuration and a GNSS validity period. Since the random access configuration may indicate an RO resource and at least one random access sequence, the correspondence between the random access configuration and the GNSS validity period may indicate not only a correspondence between the random access sequence and the GNSS validity period, but also a correspondence between the RO resource and the GNSS validity period. This allows the terminal to select a resource for transmitting the random access sequence, i.e., an RO resource, based on the correspondence between the random access configuration and the GNSS validity period.

[0172] In some embodiments, the term "RO resource" can be interchangeable with "resource corresponding to the RO", "resource where the RO is located", "RO location", etc.

[0173] In some embodiments, the network device may carry the correspondence between the random access sequence and the GNSS validity period or the correspondence between the random access configuration and the GNSS validity period in system information (SI), such as a master information block (MIB), system information block 1 (SIB1), or other SIBs.

[0174] In some embodiments, the GNSS validity period may be indicated by time information sent by the terminal. Accordingly, the correspondence between the random access sequence and the GNSS validity period can be understood as the correspondence between the random access sequence and time information. In some embodiments, the time information sent by the terminal may include at least one of GNSS positioning duration information and GNSS available time information.

[0175] In some embodiments, different GNSS validity periods may correspond to one or more random access sequences. For example, different GNSS validity periods may correspond one-to-one to different random access sequences. Alternatively, different GNSS validity periods may correspond to multiple random access sequences, which may be the same or different. In some embodiments, in the above correspondence, one GNSS validity period may correspond to one random preamble sequence, and one GNSS validity period may correspond to multiple random sequences.

[0176] In some embodiments, step S2110 may be omitted. In this case, the correspondence between the random access sequence and the GNSS validity period or the correspondence between the random access configuration and the GNSS validity period may be predefined or preconfigured.

[0177] In step S2120, the network device sends second information.

[0178] In some embodiments, the terminal receives the second information.

[0179] In some embodiments, the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.

[0180] In some embodiments, the name of the second information is not limited, and it can be, for example, "trigger information", "trigger measurement information", "trigger positioning information", etc.

[0181] In some embodiments, the second information may be carried in a high-level instruction and sent, such as high-level signaling, which may be at least one of radio resource control (RRC) signaling, broadcast messages, system messages, media access control (MAC) control elements (CE), downlink control information (DCI), and signaling carried by a physical downlink shared channel (PDSCH). Of course, the second information may also be carried in other signaling and sent, and the embodiments of the present disclosure do not specifically limit this. For example, the second information is carried in a MAC CE and sent.

[0182] In some embodiments, the network device triggers the terminal to perform GNSS measurement non-periodically, and the terminal can obtain GNSS positioning during the re-measurement interval.

[0183] In some embodiments, the terminal may also autonomously perform GNSS measurements. For example, the terminal receives an indication from a higher layer and determines that it can autonomously perform GNSS measurements. The terminal autonomously performs GNSS measurements if certain conditions are met, such as if it has not received a trigger instruction from the network to trigger GNSS measurements and the terminal's GNSS is about to expire.

[0184] In some embodiments, the terminal may determine whether to autonomously perform GNSS measurements based on network configuration. In one embodiment, the network device may configure the terminal to enable the autonomous measurement function. If enabled, the terminal may autonomously perform GNSS measurements. If disabled, the terminal may be triggered by the network device to perform GNSS measurements.

[0185] In some embodiments, step S2120 may be omitted. In this case, the terminal autonomously performs GNSS measurement in the measurement gap.

[0186] In step S2130 , the terminal performs GNSS measurement in the measurement gap.

[0187] In some embodiments, the terminal determines a configuration of a measurement gap in response to the second information, and then performs GNSS measurements within the measurement gap according to the configuration of the measurement gap.

[0188] In some embodiments, the configuration of the measurement gap may include a start position of the measurement gap, a length of the measurement gap, etc. In one embodiment, the term "length of the measurement gap" may be interchangeably used with "time length of the measurement gap," "duration of the measurement gap," "duration of the measurement gap," "duration of the measurement gap," etc.

[0189] In some embodiments, the measurement gap may be periodic or non-periodic.

[0190] In some embodiments, the measurement gap may be predefined or preconfigured, or may be configured by the network device for the terminal. Exemplarily, "predefined or preconfigured" may be understood as pre-specified by the protocol and pre-negotiated by the terminal and the network device. Exemplarily, "configured by the network device for the terminal" may be understood as determined by the network device based on the time information sent by the terminal to the network device. In one embodiment, the time information sent by the terminal may include at least one of GNSS positioning duration information and GNSS available time information. Among them, the GNSS positioning duration information is used to indicate the time required for GNSS positioning, and the GNSS available time information is used to indicate the validity period of GNSS. It should be noted that the time information sent by the above-mentioned terminal is the latest time information sent by the terminal to the network device, or is sent by the terminal after the last GNSS measurement is completed. Exemplarily, the length of the measurement gap is greater than or equal to the time required for GNSS positioning reported by the terminal.

[0191] In some embodiments, the length of the measurement gap may be pre-configured by the network device to the terminal, or may be determined by the terminal based on its own implementation. Exemplarily, the terminal may determine the length of the measurement gap based on the time information reported by the terminal. In some embodiments, the starting position of the measurement gap may also be predefined or preconfigured. Exemplarily, the starting position of the measurement gap may be the end position of the GNSS validity period, or the time domain position with an interval of N time units after receiving the trigger instruction sent by the network device, or the time domain position with an interval of N time units after the position of the terminal feedback HARQ information, where N is predefined or preconfigured. Alternatively, the starting position of the measurement gap may be based on the current GNSS validity period, with a certain delay or no delay.

[0192] In some embodiments, the above-mentioned "time unit" can be understood as "frame", "subframe", "time slot", "sub-time slot", "symbol", etc.

[0193] In some embodiments, the terminal does not need to transmit or receive any channel / signal within the measurement gap before successfully performing GNSS measurements.

[0194] In some embodiments, after successfully performing a GNSS measurement, the terminal sends a remaining GNSS validity duration to the network device each time to indicate to the network device that the GNSS measurement in the connected state is successfully performed.

[0195] In some embodiments, the terminal may execute step S2140 if the GNSS measurement in the measurement gap is successfully performed.

[0196] In step S2140, the terminal sends a first random access sequence.

[0197] In some embodiments, the network device receives a first random access sequence.

[0198] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement is successfully performed.

[0199] In some embodiments, the first random access sequence is used to indicate that the terminal has successfully performed GNSS measurement within the measurement gap.

[0200] In some embodiments, the first random access sequence is used to indicate to the terminal that the GNSS measurement in the measurement gap is performed successfully.

[0201] In some embodiments, the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.

[0202] In some embodiments, the terminal queries the correspondence between the random access sequence and the GNSS validity period based on the time information sent by the terminal to the network device, such as the GNSS availability time, and determines the first random access sequence corresponding to the current GNSS validity period. Here, the current GNSS validity period can be understood as the GNSS validity period currently being used by the terminal, or the GNSS validity period indicated by the last GNSS availability time information sent by the terminal to the network device.

[0203] In some embodiments, the correspondence between random access sequences and GNSS validity periods includes at least one random access sequence. At least a portion of these random access sequences is successfully associated with GNSS measurement execution. The terminal then queries the correspondence between random access sequences and GNSS validity periods and determines a first random access sequence corresponding to the current GNSS validity period from among the random access sequences in the correspondence that are successfully associated with GNSS measurement execution.

[0204] In some embodiments, in the above correspondence, one GNSS validity period may correspond to one random preamble sequence, and one GNSS validity period may correspond to multiple random sequences.

[0205] For example, GNSS validity period = T1 corresponds to preamble A, GNSS validity period = T2 corresponds to preamble B, and GNSS validity period = T3 corresponds to preamble C. Preamble A, preamble B, and preamble C are all used to indicate that the GNSS measurement was successfully executed. Therefore, the terminal can determine that the first random access sequence is preamble B based on its own GNSS validity period = T2.

[0206] Exemplarily, GNSS validity period = T1 corresponds to preamble A, GNSS validity period = T2 corresponds to preamble B, and GNSS validity period = T2 corresponds to preamble C. Preamble A and preamble C are used to indicate that the GNSS measurement is successfully executed. Then, in some cases, the terminal can determine that the first random access sequence is preamble A based on its own GNSS validity period = T1. In other cases, the terminal can determine that the available random access sequences are preamble B and preamble C based on its own GNSS validity period = T2. Then, the terminal can select an appropriate one from preamble B and preamble C according to its own implementation, that is, preamble B or preamble C as the first random access sequence.

[0207] In some embodiments, after obtaining the correspondence between the random access configuration and the GNSS validity period, the terminal may also query the correspondence between the random access configuration and the GNSS validity period based on the time information sent by the terminal to the network device, such as the GNSS available time, to determine the random access configuration corresponding to the current GNSS validity period. The random access configuration may indicate a first random access sequence and a first RO. In this case, the terminal sends the first random access sequence on the first RO.

[0208] In some embodiments, the first random access sequence may also be used to trigger a contention-based random access procedure. In one embodiment, the network device indicates at least one random access sequence (which may be referred to as a contention-based random access sequence) to the terminal based on the correspondence between the random access sequence and the GNSS validity period. After successfully performing a GNSS measurement within a measurement gap, the terminal determines the first random access sequence based on the correspondence between the random access sequence and the GNSS validity period and sends it to the network device.

[0209] Exemplarily, the first random access sequence may be carried in message 1 (msg1) during the random access process. In one embodiment, the random access process may be 4-step random access (4-step RACH) or 2-step random access (2-step RACH), which is not specifically limited in the embodiments of the present disclosure.

[0210] In some embodiments, the terminal sends the first random access sequence through PRACH signaling.

[0211] In some embodiments, the terminal may also send GNSS positioning duration information to indicate the GNSS position fix time duration to the network device. In one embodiment, the GNSS positioning duration information may be sent simultaneously with the first random access sequence. In one embodiment, the GNSS positioning duration information and the first random access sequence may be sent in the same message (e.g., msg1).

[0212] In step S2150 , the network device determines whether the terminal successfully performs GNSS measurement within the measurement gap.

[0213] In some embodiments, after receiving the first random access sequence, the network device continues to perform a random access procedure according to the first random access sequence.

[0214] In step S2160 , the network device determines a GNSS validity period corresponding to the first random access sequence.

[0215] In some embodiments, the network device determines the GNSS validity period corresponding to the first random access sequence according to a correspondence between the random access sequence and the GNSS validity period.

[0216] In some embodiments, the network device side and the terminal side maintain the same correspondence between the random access sequence and the GNSS validity period. Then, after receiving the first random access sequence, the network device queries the correspondence between the random access sequence and the GNSS validity period to determine the GNSS validity period corresponding to the first random access sequence, that is, the GNSS validity period of the terminal.

[0217] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2110 to S2160. For example, steps S2130 and S2140 can be implemented as independent embodiments. For example, steps S2120 to S2140 can be implemented as independent embodiments. For example, steps S2110 to S2140 can be implemented as independent embodiments. For example, the combination of steps S2130 to S2150 can be implemented as an independent embodiment. For example, the combination of steps S2130 to S2160 can be implemented as an independent embodiment. For example, the combination of steps S2120 to S2150 can be implemented as an independent embodiment. For example, the combination of steps S2110 to S2150 can be implemented as an independent embodiment. For example, the combination of steps S2120 to S2160 can be implemented as an independent embodiment. For example, the combination of steps S2110 to S2160 can be implemented as an independent embodiment. It should be noted that one or more steps from step S2110 to step S2160 may constitute an independent embodiment, but are not limited thereto.

[0218] In some embodiments, at least two of steps S2110 to S2160 may be performed in a swapped order or simultaneously. For example, step S2110 and step S2120 may be performed in a swapped order or simultaneously. Step S2110 and steps S2120 to S2130 may be performed in a swapped order or simultaneously. For example, step S2150 and step S2160 may be performed in a swapped order or simultaneously.

[0219] In some embodiments, step S2110, step S2120, and step S2160 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0220] In some embodiments, step S2120 and step S2160 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0221] In some embodiments, step S2110 and step S2120 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0222] In some embodiments, step S2110 and step S2160 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0223] In some embodiments, one of step S2110, step S2120, and step S2160 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0224] In the above embodiment, the terminal indicates the execution status of its own GNSS measurement within the measurement gap by sending a first random access sequence to the network device. In this way, the terminal and the network device can reach a consensus on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0225] FIG2B is a second flow chart of a communication method according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which is used in a communication system 100. As shown in FIG2B , the communication method according to the embodiment of the present disclosure includes steps S2210 to S2260.

[0226] In step S2210, the network device sends second information.

[0227] The optional implementation of step S2210 can refer to the optional implementation of step S2120 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0228] In step S2220, the terminal performs GNSS measurement in the measurement gap.

[0229] The optional implementation of step S2220 can refer to the optional implementation of step S2130 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0230] In some embodiments, the terminal may execute step S2230 if the GNSS measurement in the measurement gap is successfully performed.

[0231] In step S2230, the terminal sends a first random access sequence.

[0232] In some embodiments, the network device receives a first random access sequence.

[0233] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement is successfully performed.

[0234] In some embodiments, the first random access sequence is used to indicate that the terminal has successfully performed GNSS measurement within the measurement gap.

[0235] In some embodiments, the first random access sequence is used to indicate to the terminal that the GNSS measurement in the measurement gap is performed successfully.

[0236] In some embodiments, the first random access sequence can also be used to trigger a non-contention-based random access procedure. In one embodiment, the network device indicates the first random access sequence to the terminal via a random access preamble assignment (RA preamble assignment). Then, after successfully performing a GNSS measurement within a measurement gap, the terminal sends the first random access sequence to the network device. In one embodiment, the first random access sequence can be a dedicated random access preamble.

[0237] Exemplarily, the first random access sequence may be carried in msg1 during the random access process. In one embodiment, the random access process may be 4-step random access (4-step RACH) or 2-step random access (2-step RACH), which is not specifically limited in the embodiment of the present disclosure.

[0238] In some embodiments, the terminal may also send GNSS positioning duration information to indicate to the network device the time required for GNSS positioning. In one embodiment, the GNSS positioning duration information may be sent simultaneously with the first random access sequence. In one embodiment, the GNSS positioning duration information and the first random access sequence may be sent in the same message (e.g., msg1).

[0239] In step S2240 , the network device determines whether the terminal successfully performs GNSS measurement within the measurement gap.

[0240] In some embodiments, after receiving the first random access sequence, the network device continues to perform a random access procedure according to the first random access sequence.

[0241] In step S2250, the network device sends third information.

[0242] In some embodiments, the terminal receives third information.

[0243] In some embodiments, the third information is used to instruct the terminal to send a GNSS validity period on the first uplink resource.

[0244] In some embodiments, the name of the third information is not limited, and it can be, for example, "response information", "random access response information", "trigger reporting information", etc.

[0245] In some embodiments, the third information may be carried in message 2 (msg2) during the random access process. In one embodiment, the random access process may be 4-step random access (4-step RACH) or 2-step random access (2-step RACH), which is not specifically limited in the embodiments of the present disclosure.

[0246] In some embodiments, the first uplink resource is scheduled by an uplink grant. The first uplink resource is used by the terminal to send a GNSS validity period.

[0247] In some embodiments, the network device sends the third information after determining that the terminal successfully performs GNSS measurement within the measurement gap.

[0248] In step S2260, the terminal sends the first time information.

[0249] In some embodiments, the network device receives first time information, where the first time information is used to indicate a GNSS validity period of the terminal.

[0250] In some embodiments, the first information may be GNSS available time information.

[0251] In some embodiments, the terminal sends the first time information on the first uplink resource.

[0252] In some embodiments, the first uplink resource may be carried in message 3 (msg3) during a random access process.

[0253] In some embodiments, after performing a GNSS measurement, the terminal sends the GNSS validity period to the network device. In one embodiment, the terminal may send the GNSS validity period once per measurement. In one embodiment, the terminal may also send a new GNSS validity period to the network device when the length of the GNSS validity period changes.

[0254] In some embodiments, the terminal may also send other information, such as GNSS positioning duration information, at the same time as sending the GNSS available time information, to indicate to the network device the time required for GNSS positioning. For example, the GNSS available time information and the GNSS positioning duration information may be sent in the same message or in different messages.

[0255] In some embodiments, the terminal may separately send GNSS available time information and GNSS positioning persistence information. In this case, the GNSS positioning persistence information may be carried in, for example, an RRC connection reestablishment complete message (RRCConnectionReestablishmentComplete or RRCConnectionReestablishmentComplete-NB) or an RRC connection reconfiguration complete message (RCConnectionReconfigurationComplete for HO case).

[0256] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2210 to S2240. For example, step S2220 and step S2230 may be implemented as independent embodiments. For example, the combination of steps S2220 to S2240 may be implemented as an independent embodiment. For example, the combination of steps S2210 to S2230 may be implemented as an independent embodiment. For example, the combination of steps S2210 to S2240 may be implemented as an independent embodiment. It should be noted that one or more steps in steps S2210 to S2240 may form a possible independent embodiment, but are not limited to this.

[0257] In some embodiments, step S2210 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0258] In some embodiments, step S2240 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0259] In the above embodiment, the terminal indicates the execution status of its own GNSS measurement within the measurement gap by sending a first random access sequence to the network device. In this way, the terminal and the network device can reach a consensus on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0260] FIG2C is a third flow chart of a communication method according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which is used in the communication system 100. As shown in FIG2C, the communication method according to the embodiment of the present disclosure includes steps S2310 to S2370.

[0261] In step S2310, the network device sends first configuration information.

[0262] In some embodiments, the terminal receives first configuration information.

[0263] In some embodiments, the first configuration information is used to indicate at least one second random access sequence. In one embodiment, the second random access sequence is associated with a successful GNSS measurement. The second random access sequence is used to indicate a successful GNSS measurement.

[0264] In some embodiments, the network device may further include second configuration information.

[0265] In some embodiments, the terminal receives second configuration information.

[0266] In some embodiments, the second configuration information is used to indicate at least one fourth random access sequence.

[0267] In some embodiments, the fourth random access sequence is associated with a random access procedure. The fourth random access sequence may be used to trigger the random access procedure.

[0268] In some embodiments, the terminal may obtain at least one fourth random access sequence according to predefinition or preconfiguration.

[0269] In some embodiments, at least one second random access sequence and at least one fourth random access sequence may be included in different information and sent simultaneously, or may be included in the same information (eg, random access configuration) and sent.

[0270] In some embodiments, step S2310 may be omitted. In this case, the terminal may obtain at least one second random access sequence according to a predefined or preconfigured method.

[0271] In step S2320, the terminal performs GNSS measurement in the measurement gap.

[0272] The optional implementation of step S2320 can refer to the optional implementation of step S2130 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0273] In step S2330, the terminal determines a first random access sequence.

[0274] In some embodiments, after successfully performing GNSS measurement within a measurement gap, the terminal may determine the first random access sequence from at least one second random access sequence.

[0275] In some embodiments, the terminal selects a second random access sequence from at least one second random access sequence as the first random access sequence. In one embodiment, the terminal may randomly select a second random access sequence from at least one second random access sequence as the first random access sequence. In one embodiment, the terminal may select an appropriate second random access sequence from at least one second random access sequence as the first random access sequence based on its own implementation, such as hardware capabilities.

[0276] In some embodiments, without indicating to the network device the execution of the GNSS measurement, the terminal may select one from at least one fourth random access sequence to initiate a random access procedure.

[0277] In step S2340, the terminal sends a first random access sequence.

[0278] The optional implementation of step S2340 can refer to the optional implementation of step S2140 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0279] In step S2350 , the network device determines whether the first random access sequence is successfully associated with the GNSS.

[0280] In some embodiments, after receiving the first random access sequence, the network device determines that the first random access sequence is one of the at least one second random access sequence, and further determines that the terminal successfully performs GNSS measurement in the measurement gap.

[0281] In some embodiments, after receiving the first random access sequence, the network device continues to perform a random access procedure according to the first random access sequence.

[0282] In step S2360, the network device sends third information.

[0283] In some embodiments, the terminal receives third information.

[0284] In some embodiments, the third information is used to instruct the terminal to send a GNSS validity period on the first uplink resource.

[0285] In some embodiments, the name of the third information is not limited, and it can be, for example, "response information", "random access response information", "trigger reporting information", etc.

[0286] In some embodiments, the third information may be carried in message 2 (msg2) during the random access process. In one embodiment, the random access process may be 4-step random access (4-step RACH) or 2-step random access (2-step RACH), which is not specifically limited in the embodiments of the present disclosure.

[0287] In some embodiments, the first uplink resource is scheduled by an uplink grant. The first uplink resource is used by the terminal to send a GNSS validity period.

[0288] In some embodiments, the network device sends the third information after determining that the terminal successfully performs GNSS measurement within the measurement gap.

[0289] In step S2370, the terminal sends the first time information.

[0290] In some embodiments, the network device receives first time information, where the first time information is used to indicate a GNSS validity period of the terminal.

[0291] In some embodiments, the terminal sends first time information on a first uplink resource to indicate GNSS available time information.

[0292] In some embodiments, the first uplink resource may be carried in message 3 (msg3) during a random access process.

[0293] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2310 to S2370. For example, steps S2320 to S2340 can be implemented as independent embodiments. For example, the combination of steps S2310 to S2340 can be implemented as an independent embodiment. For example, the combination of steps S2320 to S2350 can be implemented as an independent embodiment. For example, the combination of steps S2320 to S2370 can be implemented as an independent embodiment. For example, the combination of steps S2310 to S2370 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S2310 to S2370 may form a possible independent embodiment, but are not limited to this.

[0294] In some embodiments, step S2310, step S2350, and step S2360 to step S2370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0295] In some embodiments, step S2310 and step S2350 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0296] In some embodiments, step S2350, step S2360 to step S2370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0297] In some embodiments, steps S2360 to S2370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0298] In some embodiments, step S2310 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0299] In the above embodiment, the terminal indicates the execution status of its own GNSS measurement within the measurement gap by sending a first random access sequence to the network device. In this way, the terminal and the network device can reach a consensus on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0300] FIG2D is a fourth flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is used in the communication system 100. As shown in FIG2D , the communication method according to the embodiment of the present disclosure includes steps S2410 to S2440.

[0301] In step S2410, the network device sends first information.

[0302] The optional implementation of step S2410 can refer to the optional implementation of step S2110 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0303] In some embodiments, the first information is used to indicate a correspondence between a random access sequence and a GNSS validity period.

[0304] In some embodiments, the correspondence between random access sequences and GNSS validity periods includes at least one random access sequence (ie, at least one third random access sequence), and at least a portion of these random access sequences is associated with GNSS measurement execution failure.

[0305] In some embodiments, step S2410 may be omitted. In this case, the correspondence between the random access sequence and the GNSS validity period or the correspondence between the random access configuration and the GNSS validity period may be predefined or preconfigured.

[0306] In step S2420, the network device sends second information.

[0307] The optional implementation of step S2420 can refer to the optional implementation of step S2120 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0308] In some embodiments, step S2420 may be omitted. In this case, the terminal autonomously performs GNSS measurement in the measurement gap.

[0309] In step S2430 , the terminal performs GNSS measurement in the measurement gap.

[0310] The optional implementation of step S2430 can refer to the optional implementation of step S2130 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0311] In some embodiments, the terminal may execute step S2440 when the GNSS measurement within the measurement gap fails.

[0312] In step S2440, the terminal sends a first random access sequence.

[0313] In some embodiments, the network device receives a first random access sequence.

[0314] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement fails.

[0315] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0316] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0317] In some embodiments, the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.

[0318] In some embodiments, the terminal queries the correspondence between the random access sequence and the GNSS validity period based on the time information sent by the terminal to the network device, such as the GNSS available time, and determines the first random access sequence corresponding to the current GNSS validity period.

[0319] In some embodiments, the correspondence between random access sequences and GNSS validity periods includes at least one random access sequence. At least a portion of these random access sequences is associated with GNSS measurement failures. The terminal then queries the correspondence between random access sequences and GNSS validity periods and determines a first random access sequence corresponding to the current GNSS validity period from among the random access sequences associated with GNSS measurement failures in the correspondence.

[0320] For example, GNSS validity period = T1 corresponds to preamble A, GNSS validity period = T2 corresponds to preamble B, and GNSS validity period = T3 corresponds to preamble C. Preamble A, preamble B, and preamble C are all used to indicate a GNSS measurement failure. Therefore, the terminal can determine that the first random access sequence is preamble A based on its own GNSS validity period = T1.

[0321] For example, GNSS validity period T1 corresponds to preamble A, GNSS validity period T3 corresponds to preamble B, and GNSS validity period T2 corresponds to preamble C. Preamble A and preamble B are used to indicate GNSS measurement failure. Then, the terminal can determine that the first random access sequence is preamble A based on its own GNSS validity period T3.

[0322] In some embodiments, the first random access sequence may be carried in message 1 (message 1, msg1) during a random access procedure and sent.

[0323] In some embodiments, the terminal sends the first random access sequence through PRACH signaling.

[0324] In some embodiments, after the GNSS measurement fails, the terminal may also determine that the current GNSS validity period has not expired. In this case, the terminal remains in a connected state until the current GNSS validity period expires. The terminal then enters an idle state or determines that RLF occurs.

[0325] In some embodiments, after the GNSS measurement fails, the terminal may also determine that the current GNSS validity period has expired. At this time, the terminal enters an idle state or determines that an RLF occurs.

[0326] In some embodiments, the terminal determining that an RLF occurs may also be described as the terminal entering an RLF state.

[0327] In some embodiments, if the terminal fails to reacquire GNSS positioning within a measurement gap, it may remain in a connected state for the duration of the GNSS measurement timer after the measurement gap and reacquire GNSS positioning within the duration of the GNSS measurement timer. In some embodiments, when the terminal fails to reacquire GNSS positioning within the duration of the GNSS measurement timer, the terminal enters IDLE mode or determines that RLF has occurred after the GNSS measurement timer expires. In one embodiment, when the terminal does not have a GNSS measurement timer after the GNSS measurement gap, the terminal enters IDLE mode or determines that RLF has occurred after the measurement gap expires.

[0328] In step S2450 , the network device determines that the terminal has not successfully performed GNSS measurement within the measurement gap.

[0329] In some embodiments, the embodiment of FIG. 2A may be combined with the embodiment of FIG. 2D . For example, step S2110 may be combined with step S2410. In one embodiment, the correspondence between random access sequences and GNSS validity periods includes at least one random access sequence. Some of these random access sequences are associated with successful GNSS measurement execution, while others are associated with failed GNSS measurement execution.

[0330] In some embodiments, after step S2130, if the terminal successfully performs GNSS measurement in the measurement gap, step S2140 is performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, steps S2440 to S2450 are performed.

[0331] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2410 to S2450. For example, steps S2430 and S2440 can be implemented as independent embodiments. For example, steps S2420 to S2440 can be implemented as independent embodiments. For example, steps S2410 to S2440 can be implemented as independent embodiments. For example, the combination of steps S2430 to S2450 can be implemented as an independent embodiment. For example, the combination of steps S2420 to S2450 can be implemented as an independent embodiment. For example, the combination of steps S2410 to S2450 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S2410 to S2450 may form a possible independent embodiment, but are not limited to this.

[0332] In some embodiments, at least two of steps S2410 to S2450 may be performed in an interchangeable order or simultaneously. For example, step S2410 and step S2420 may be performed in an interchangeable order or simultaneously. Step S2410 and steps S2420 to S2430 may be performed in an interchangeable order or simultaneously.

[0333] In some embodiments, step S2410 and step S2420 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0334] In some embodiments, step S2410 or step S2420 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0335] In the above embodiment, the terminal indicates the execution status of its own GNSS measurement within the measurement gap by sending a first random access sequence to the network device. In this way, the terminal and the network device can reach a consensus on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0336] FIG2E is a fifth flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is used in the communication system 100. As shown in FIG2E, the communication method according to the embodiment of the present disclosure includes steps S2510 to S2540.

[0337] In step S2510, the network device sends second information.

[0338] The optional implementation of step S2510 can refer to the optional implementation of step S2120 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0339] In step S2520, the terminal performs GNSS measurement in the measurement gap.

[0340] The optional implementation of step S2520 can refer to the optional implementation of step S2130 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0341] In some embodiments, the terminal may execute step S2530 when the GNSS measurement fails.

[0342] In step S2530, the terminal sends a first random access sequence.

[0343] In some embodiments, the network device receives a first random access sequence.

[0344] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement fails.

[0345] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0346] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0347] In some embodiments, the first random access sequence may be carried in msg1 during the random access procedure and sent.

[0348] In some embodiments, the terminal sends the first random access sequence through PRACH signaling.

[0349] In some embodiments, after the GNSS measurement fails, the terminal may also determine that the current GNSS validity period has not expired. In this case, the terminal remains in a connected state until the current GNSS validity period expires. The terminal then enters an idle state or determines that RLF occurs.

[0350] In some embodiments, after the GNSS measurement fails, the terminal may also determine that the current GNSS validity period has expired. At this time, the terminal enters an idle state or determines that an RLF occurs.

[0351] In step S2540 , the network device determines that the terminal has not successfully performed GNSS measurement within the measurement gap.

[0352] In some embodiments, the embodiment of FIG2B may be combined with the embodiment of FIG2E . For example, after step S2220, if the terminal successfully performs GNSS measurement within the measurement gap, step S2230 is performed. If the terminal fails to successfully perform GNSS measurement within the measurement gap, steps S2530 to S2540 are performed.

[0353] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2510 to S2540. For example, steps S2520 and S2530 may be implemented as independent embodiments. For example, the combination of steps S2520 to S2540 may be implemented as an independent embodiment. For example, the combination of steps S2510 to S2530 may be implemented as an independent embodiment. For example, the combination of steps S2510 to S2540 may be implemented as an independent embodiment. It should be noted that one or more steps from steps S2510 to S2540 may form a possible independent embodiment, but are not limited to this.

[0354] In some embodiments, step S2510 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0355] In the above embodiment, the terminal indicates the execution status of its own GNSS measurement within the measurement gap by sending a first random access sequence to the network device. In this way, the terminal and the network device can reach a consensus on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0356] FIG2F is a sixth flow chart of a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is used in the communication system 100. As shown in FIG2F, the communication method according to the embodiment of the present disclosure includes steps S2610 to S2640.

[0357] In step S2610, the network device sends third configuration information.

[0358] In some embodiments, the terminal receives third configuration information.

[0359] In some embodiments, the third configuration information is used to indicate at least one third random access sequence.

[0360] In some embodiments, the third random access sequence is associated with a GNSS measurement execution failure. The third random access sequence is used to indicate a GNSS measurement execution failure.

[0361] In some embodiments, step S2610 may be omitted. In this case, the terminal may obtain at least one third random access sequence according to a predefined or preconfigured method.

[0362] In step S2620, the terminal performs GNSS measurement in the measurement gap.

[0363] The optional implementation of step S2620 can refer to the optional implementation of step S2130 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0364] In some embodiments, before step S2620, the terminal receives second information sent by the network device. Then, the terminal responds to the second information and performs GNSS measurement in the measurement gap.

[0365] In some embodiments, the terminal autonomously performs GNSS measurements during the measurement gaps.

[0366] In some embodiments, the terminal may execute step S2630 when the GNSS measurement fails.

[0367] In step S2630, the terminal determines a first random access sequence.

[0368] In some embodiments, after the terminal fails to successfully perform GNSS measurement within a measurement gap, the terminal may determine the first random access sequence from at least one third random access sequence.

[0369] In some embodiments, the terminal selects a third random access sequence from at least one third random access sequence as the first random access sequence. In one embodiment, the terminal may randomly select a third random access sequence from at least one third random access sequence as the first random access sequence. In one embodiment, the terminal may select any third random access sequence from at least one third random access sequence as the first random access sequence. In one embodiment, the terminal may select an appropriate third random access sequence from at least one third random access sequence as the first random access sequence based on its own implementation, such as hardware capabilities.

[0370] In step S2640, the terminal sends a first random access sequence.

[0371] The optional implementation of step S2640 can refer to the optional implementation of step S2530 in Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.

[0372] In step S2650 , the network device determines that the first random access sequence fails to be associated with the GNSS.

[0373] In some embodiments, after receiving the first random access sequence, the network device determines that the first random access sequence is one of at least one third random access sequence, and further determines that the terminal fails to perform GNSS measurement in the measurement gap.

[0374] In some embodiments, the embodiment of FIG2C may be combined with the embodiment of FIG2F . For example, after step S2320, if the terminal successfully performs GNSS measurement within the measurement gap, steps S2330 to S2370 are performed. If the terminal fails to successfully perform GNSS measurement within the measurement gap, steps S2630 to S2650 are performed.

[0375] In some embodiments, the terminal may obtain at least one second random access sequence and at least one third random access sequence. After executing step S2130 or step S2630, the terminal may select the second random access sequence or the third random access sequence as the first random access sequence based on the result of the GNSS measurement. Then, after receiving the first random access sequence, the network device determines whether the terminal successfully performs GNSS measurement within the measurement gap based on whether the first random access sequence is the second random access sequence or the third random access sequence.

[0376] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2610 to S2650. For example, steps S2620 to S2640 may be implemented as independent embodiments. For example, the combination of steps S2610 to S2640 may be implemented as an independent embodiment. For example, the combination of steps S2620 to S2650 may be implemented as an independent embodiment. It should be noted that one or more steps in steps S2610 to S2650 may form a possible independent embodiment, but are not limited to this.

[0377] In some embodiments, step S2610 and step S2650 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0378] In some embodiments, step S2650 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0379] In some embodiments, step S2610 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0380] In the above embodiment, the terminal indicates the execution status of its own GNSS measurement within the measurement gap by sending a first random access sequence to the network device. In this way, the terminal and the network device can reach a consensus on the result of the GNSS measurement performed by the corresponding terminal, avoiding information asymmetry between the terminal and the network device.

[0381] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0382] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0383] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0384] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" may be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" may be used interchangeably.

[0385] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0386] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0387] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0388] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0389] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0390] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0391] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0392] FIG3A is a schematic diagram illustrating a first flow chart of a communication method executed by a terminal according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is used by a terminal 101 in a communication system 100. As shown in FIG3A , the communication method of this embodiment of the present disclosure includes steps S3110 to S3140.

[0393] In step S3110, a correspondence between a random access sequence and a GNSS validity period is obtained.

[0394] The optional implementation of step S3110 can refer to the optional implementation of step S2110 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0395] In some embodiments, the terminal receives first information sent by the network device, where the first information is used to indicate a correspondence between a random access sequence and a GNSS validity period.

[0396] In some embodiments, the terminal obtains a correspondence between a predefined or preconfigured random access sequence and a GNSS validity period.

[0397] In step S3120, second information is obtained.

[0398] The optional implementation of step S3120 can refer to the optional implementation of step S2120 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0399] In some embodiments, the terminal receives second information sent by the network device.

[0400] In some embodiments, the terminal receives second information sent by a higher layer.

[0401] In some embodiments, step S3120 may be omitted. In this case, the terminal autonomously performs GNSS measurement in the measurement gap.

[0402] In step S3130 , GNSS measurement is performed within the measurement gap.

[0403] The optional implementation of step S3130 can refer to the optional implementation of step S2130 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0404] In step S3140, a first random access sequence is sent.

[0405] The optional implementation of step S3140 can refer to the optional implementation of step S2140 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0406] In some embodiments, the terminal sends a first random access sequence to the network device.

[0407] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement is successfully performed.

[0408] In some embodiments, the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.

[0409] In some embodiments, the first random access sequence is used by the network device to determine whether the terminal successfully performs GNSS measurement within the measurement gap.

[0410] In some embodiments, the first random access sequence is used by the network device to continue to perform a random access procedure according to the first random access sequence.

[0411] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3110 to S3140. For example, steps S3130 and S3140 may be implemented as independent embodiments. For example, steps S3120 to S3140 may be implemented as independent embodiments. For example, steps S3110 to S3140 may be implemented as independent embodiments. It should be noted that one or more of steps S3110 to S3140 may constitute a possible independent embodiment, but are not limited to this.

[0412] In some embodiments, at least two of steps S3110 to S3140 may be performed in a swapped order or simultaneously. For example, step S3110 and step S3120 may be performed in a swapped order or simultaneously. Step S3110 and steps S3120 to S3130 may be performed in a swapped order or simultaneously.

[0413] In some embodiments, step S3110 and step S3120 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0414] In some embodiments, step S3110 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0415] In some embodiments, step S3120 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0416] FIG3B is a second flow diagram illustrating a terminal-side communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for terminal 101 in communication system 100. As shown in FIG3B , the communication method of this embodiment of the present disclosure includes steps S3210 to S3250.

[0417] In step S3210, the second information is obtained.

[0418] The optional implementation of step S3210 can refer to the optional implementation of step S2210 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0419] In some embodiments, the terminal receives second information sent by the network device.

[0420] In some embodiments, the terminal receives second information sent by a higher layer.

[0421] In some embodiments, step S3210 may be omitted. In this case, the terminal autonomously performs GNSS measurement in the measurement gap.

[0422] In step S3220, GNSS measurement is performed within the measurement gap.

[0423] The optional implementation of step S3220 can refer to the optional implementation of step S2220 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0424] In some embodiments, the terminal may execute step S3230 if the GNSS measurement in the measurement gap is successfully performed.

[0425] In step S3230, a first random access sequence is sent.

[0426] The optional implementation of step S3230 can refer to the optional implementation of step S2230 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0427] In some embodiments, the terminal sends a first random access sequence to the network device.

[0428] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement is successfully performed.

[0429] In some embodiments, the first random access sequence is used by the network device to determine whether the terminal successfully performs GNSS measurement within the measurement gap.

[0430] In some embodiments, the first random access sequence is used by the network device to continue to perform a random access procedure according to the first random access sequence.

[0431] In step S3240, third information is received.

[0432] The optional implementation of step S3240 can refer to the optional implementation of step S2250 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0433] In some embodiments, the terminal receives third information sent by the network device.

[0434] In step S3250, the first time information is sent.

[0435] The optional implementation of step S3250 can refer to the optional implementation of step S2260 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0436] In some embodiments, the terminal sends first time information to the network device.

[0437] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3210 to S3230. For example, steps S3220 and S3230 may be implemented as independent embodiments. For example, the combination of steps S3210 to S3230 may be implemented as an independent embodiment. It should be noted that one or more of steps S3210 to S3230 may constitute a possible independent embodiment, but is not limited to this.

[0438] In some embodiments, step S3210 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0439] FIG3C is a third flow diagram illustrating a communication method executed by a terminal according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for terminal 101 in communication system 100. As shown in FIG3C , the communication method of this embodiment of the present disclosure includes steps S3310 to S3360.

[0440] In step S3310, at least one second random access sequence is obtained.

[0441] The optional implementation of step S3310 can refer to the optional implementation of step S2310 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.

[0442] In some embodiments, the terminal receives at least one second random access sequence sent by the network device.

[0443] In some embodiments, the terminal obtains at least one predefined or preconfigured second random access sequence.

[0444] In some embodiments, the terminal receives at least one fourth random access sequence sent by the network device.

[0445] In some embodiments, the terminal obtains at least one predefined or preconfigured fourth random access sequence.

[0446] In step S3320, GNSS measurement is performed within the measurement gap.

[0447] The optional implementation of step S3320 can refer to the optional implementation of step S2320 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0448] In step S3330, a first random access sequence is determined.

[0449] The optional implementation of step S3330 can refer to the optional implementation of step S2330 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0450] In step S3340, a first random access sequence is sent.

[0451] The optional implementation of step S3340 can refer to the optional implementation of step S2340 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0452] In some embodiments, the terminal sends a first random access sequence to the network device.

[0453] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement is successfully performed.

[0454] In some embodiments, the first random access sequence is used by the network device to determine whether the terminal successfully performs GNSS measurement within the measurement gap.

[0455] In some embodiments, the first random access sequence is used to trigger the network device to send third information.

[0456] In step S3350, second information is received.

[0457] The optional implementation of step S3350 can refer to the optional implementation of step S2360 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0458] In some embodiments, the terminal receives second information sent by the network device.

[0459] In step S3360, the first time information is sent.

[0460] The optional implementation of step S3360 can refer to the optional implementation of step S2370 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0461] In some embodiments, the terminal sends first time information to the network device.

[0462] In some embodiments, the terminal sends first time information to the network device on a first uplink resource.

[0463] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3310 to S3360. For example, steps S3320 to S3340 can be implemented as independent embodiments. For example, the combination of steps S3310 to S3340 can be implemented as an independent embodiment. For example, the combination of steps S3320 to S3360 can be implemented as an independent embodiment. For example, the combination of steps S3310 to S3360 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S3310 to S3360 may form a possible independent embodiment, but are not limited to this.

[0464] In some embodiments, step S3310, step S3360 to step S3370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0465] In some embodiments, step S3310 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0466] In some embodiments, steps S3360 to S3370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0467] FIG3D is a fourth flow diagram illustrating a communication method executed by a terminal according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for terminal 101 in communication system 100. As shown in FIG3D , the communication method of this embodiment of the present disclosure includes steps S3410 to S3440.

[0468] In step S3410, a correspondence between a random access sequence and a GNSS validity period is obtained.

[0469] The optional implementation of step S3410 can refer to the optional implementation of step S2410 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0470] In some embodiments, the terminal receives a correspondence between a random access sequence and a GNSS validity period sent by a network device.

[0471] In some embodiments, the terminal obtains a correspondence between a predefined or preconfigured random access sequence and a GNSS validity period.

[0472] In step S3420, second information is obtained.

[0473] The optional implementation of step S3420 can refer to the optional implementation of step S2420 in Figure 2D and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.

[0474] In some embodiments, the terminal receives second information sent by the network device.

[0475] In some embodiments, the terminal receives second information sent by a higher layer.

[0476] In some embodiments, step S3420 may be omitted. In this case, the terminal autonomously performs GNSS measurement in the measurement gap.

[0477] In step S3430 , GNSS measurement is performed within the measurement gap.

[0478] The optional implementation of step S3430 can refer to the optional implementation of step S2430 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0479] In some embodiments, the terminal may execute step S3440 when the GNSS measurement within the measurement gap fails.

[0480] In step S3440, a first random access sequence is sent.

[0481] The optional implementation of step S3440 can refer to the optional implementation of step S2440 in Figure 2D and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.

[0482] In some embodiments, the terminal sends a first random access sequence to the network device.

[0483] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement fails.

[0484] In some embodiments, the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.

[0485] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0486] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0487] In some embodiments, the embodiment of FIG. 3A may be combined with the embodiment of FIG. 3D . For example, step S3110 may be combined with step S3410. In one embodiment, the correspondence between random access sequences and GNSS validity periods includes at least one random access sequence. Some of these random access sequences are associated with successful GNSS measurement execution, while others are associated with failed GNSS measurement execution.

[0488] In some embodiments, after step S3130, if the terminal successfully performs GNSS measurement in the measurement gap, step S3140 may be performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, step S3440 may be performed.

[0489] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3410 to S3440. For example, steps S3430 and S3440 may be implemented as independent embodiments. For example, steps S3420 to S3440 may be implemented as independent embodiments. For example, steps S3410 to S3440 may be implemented as independent embodiments. It should be noted that one or more of steps S3410 to S3440 may constitute a possible independent embodiment, but are not limited to this.

[0490] In some embodiments, at least two of steps S3410 to S3440 may be performed in a swapped order or simultaneously. For example, step S3410 and step S3420 may be performed in a swapped order or simultaneously. Step S3410 and steps S3420 to S3430 may be performed in a swapped order or simultaneously.

[0491] In some embodiments, step S3410 and step S3420 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0492] In some embodiments, step S3410 or step S3420 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0493] FIG3E is a fifth flow diagram illustrating a communication method executed by a terminal according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is used by terminal 101 in communication system 100. As shown in FIG3E , the communication method of this embodiment of the present disclosure includes steps S3510 to S3530.

[0494] In step S3510, second information is obtained.

[0495] The optional implementation of step S3510 can refer to the optional implementation of step S2510 in Figure 2E and other related parts in the embodiment involved in Figure 2E, which will not be repeated here.

[0496] In some embodiments, the terminal receives second information sent by the network device.

[0497] In some embodiments, the terminal receives second information sent by a higher layer.

[0498] In some embodiments, step S3510 may be omitted. In this case, the terminal autonomously performs GNSS measurement within the measurement gap.

[0499] In step S3520, GNSS measurement is performed within the measurement gap.

[0500] The optional implementation of step S3520 can refer to the optional implementation of step S2520 in Figure 2E and other related parts in the embodiment involved in Figure 2E, which will not be repeated here.

[0501] In some embodiments, the terminal may execute step S3530 when the GNSS measurement fails.

[0502] In step S3530, a first random access sequence is sent.

[0503] The optional implementation of step S3530 can refer to the optional implementation of step S2530 in Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.

[0504] In some embodiments, the terminal sends a first random access sequence to the network device.

[0505] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement fails.

[0506] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0507] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0508] In some embodiments, the embodiment of FIG3B may be combined with the embodiment of FIG3E . For example, after step S3220, if the terminal successfully performs GNSS measurement within the measurement gap, step S3230 is performed. If the terminal fails to successfully perform GNSS measurement within the measurement gap, step S3530 is performed.

[0509] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3510 to S3530. For example, steps S3520 and S3530 may be implemented as independent embodiments. For example, the combination of steps S3510 to S3530 may be implemented as an independent embodiment. It should be noted that one or more of steps S3510 to S3530 may constitute a possible independent embodiment, but is not limited to this.

[0510] In some embodiments, step S3510 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0511] FIG3F is a sixth flow diagram illustrating a communication method executed by a terminal according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for terminal 101 in communication system 100. As shown in FIG3F , the communication method of this embodiment of the present disclosure includes steps S3610 to S3640.

[0512] In step S3610, at least one third random access sequence is obtained.

[0513] The optional implementation of step S3610 can refer to the optional implementation of step S2610 in Figure 2F and other related parts in the embodiment involved in Figure 2F, which will not be repeated here.

[0514] In some embodiments, the terminal receives third configuration information sent by the network device, where the third configuration information is used to indicate at least one third random access sequence.

[0515] In some embodiments, the terminal obtains at least one predefined or preconfigured third random access sequence.

[0516] In step S3620, GNSS measurement is performed within the measurement gap.

[0517] The optional implementation of step S3620 can refer to the optional implementation of step S2620 in Figure 2F and other related parts in the embodiment involved in Figure 2F, which will not be repeated here.

[0518] In some embodiments, the terminal may execute step S3630 when the GNSS measurement fails.

[0519] In step S3630, a first random access sequence is determined.

[0520] The optional implementation of step S3630 can refer to the optional implementation of step S2630 in Figure 2F and other related parts in the embodiment involved in Figure 2F, which will not be repeated here.

[0521] In step S3640, a first random access sequence is sent.

[0522] The optional implementation of step S3640 can refer to the optional implementation of step S2640 in Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.

[0523] In some embodiments, the terminal sends a first random access sequence to the network device.

[0524] In some embodiments, the terminal sends the first random access sequence after the GNSS measurement fails.

[0525] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0526] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0527] In some embodiments, after receiving the first random access sequence, the network device determines that the first random access sequence is one of at least one third random access sequence, and further determines that the terminal fails to perform GNSS measurement in the measurement gap.

[0528] In some embodiments, the embodiment of FIG3C may be combined with the embodiment of FIG3F . For example, after step S3320, if the terminal successfully performs GNSS measurement within the measurement gap, steps S3330 to S3340 are performed. If the terminal fails to successfully perform GNSS measurement within the measurement gap, steps S3630 to S3640 are performed.

[0529] In some embodiments, the terminal may obtain at least one second random access sequence and at least one third random access sequence. After executing step S3320 or step S3620, the terminal may select the second random access sequence or the third random access sequence as the first random access sequence based on the result of the GNSS measurement. Then, after receiving the first random access sequence, the network device determines whether the terminal successfully performs GNSS measurement within the measurement gap based on whether the first random access sequence is the second random access sequence or the third random access sequence.

[0530] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3610 to S3640. For example, steps S3620 to S3640 may be implemented as independent embodiments. For example, a combination of steps S3610 to S3640 may be implemented as an independent embodiment. It should be noted that one or more of steps S3610 to S3640 may form an independent embodiment, but are not limited to this.

[0531] In some embodiments, step S3610 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0532] Figure 4A is a schematic diagram illustrating a first flow chart of a network device-side communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for use with a network device 102, such as an access network device, in a communication system 100. As shown in Figure 4A , the communication method of this embodiment of the present disclosure includes steps S4110 to S4150.

[0533] In step S4110, the first information is sent.

[0534] The optional implementation of step S4110 can refer to the optional implementation of step S2110 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0535] In some embodiments, the network device sends first information to the terminal. The first information is used to indicate a correspondence between a random access sequence and a GNSS validity period.

[0536] In some embodiments, step S4110 may be omitted. In this case, the correspondence between the random access sequence and the GNSS validity period is predefined or preconfigured.

[0537] In step S4120, the second information is sent.

[0538] The optional implementation of step S4120 can refer to the optional implementation of step S2120 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0539] In some embodiments, the network device sends the second information to the terminal.

[0540] In some embodiments, step S4120 may be omitted. In this case, the terminal autonomously performs GNSS measurement within the measurement gap.

[0541] In some embodiments, the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.

[0542] In step S4130, a first random access sequence is received.

[0543] The optional implementation of step S4130 can refer to the optional implementation of step S2140 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0544] In some embodiments, the first random access sequence is used to indicate that the terminal has successfully performed GNSS measurement within the measurement gap.

[0545] In some embodiments, the first random access sequence is used to indicate to the terminal that the GNSS measurement in the measurement gap is performed successfully.

[0546] In step S4140 , it is determined whether the terminal successfully performs GNSS measurement within the measurement gap.

[0547] The optional implementation of step S4140 can refer to the optional implementation of step S2150 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0548] In step S4150, the GNSS validity period corresponding to the first random access sequence is determined.

[0549] The optional implementation of step S4150 can refer to the optional implementation of step S2160 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0550] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4110 to S4150. For example, steps S4130 and S4140 can be implemented as independent embodiments. For example, steps S4120 to S4140 can be implemented as independent embodiments. For example, steps S4110 to S4140 can be implemented as independent embodiments. For example, the combination of steps S4130 to S4150 can be implemented as an independent embodiment. For example, the combination of steps S4120 to S4150 can be implemented as an independent embodiment. For example, the combination of steps S4110 to S4150 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S4110 to S4150 may constitute a possible independent embodiment, but are not limited to this.

[0551] In some embodiments, at least two of steps S4110 to S4150 may be performed in a swapped order or simultaneously. For example, step S4110 and step S4120 may be performed in a swapped order or simultaneously. Step S4110 and steps S4120 to S4130 may be performed in a swapped order or simultaneously. For example, step S4150 and step S4160 may be performed in a swapped order or simultaneously.

[0552] In some embodiments, step S4110, step S4120, and step S4150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0553] In some embodiments, step S4120 and step S4150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0554] In some embodiments, step S4110 and step S4120 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0555] In some embodiments, step S4110 and step S4150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0556] In some embodiments, one of step S4110, step S4120, and step S4150 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0557] Figure 4B is a schematic diagram illustrating a second flow chart of a communication method executed on a network device according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for use with network device 102, such as an access network device, in communication system 100. As shown in Figure 4B , the communication method of this embodiment of the present disclosure includes steps S4210 to S4230.

[0558] In step S4210, the second information is sent.

[0559] The optional implementation of step S4210 can refer to the optional implementation of step S2210 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0560] In some embodiments, the network device sends the second information to the terminal.

[0561] In some embodiments, step S4210 may be omitted. In this case, the terminal autonomously performs GNSS measurement within the measurement gap.

[0562] In some embodiments, the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.

[0563] In step S4220, a first random access sequence is received.

[0564] The optional implementation of step S4220 can refer to the optional implementation of step S2230 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0565] In some embodiments, the network device receives a first random access sequence sent by the terminal.

[0566] In some embodiments, the first random access sequence is used to indicate that the terminal has successfully performed GNSS measurement within the measurement gap.

[0567] In some embodiments, the first random access sequence is used to indicate to the terminal that the GNSS measurement in the measurement gap is performed successfully.

[0568] In step S4230, it is determined whether the terminal successfully performs GNSS measurement within the measurement gap.

[0569] The optional implementation of step S4230 can refer to the optional implementation of step S2240 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0570] In step S4240, the third information is sent.

[0571] The optional implementation of step S3240 can refer to the optional implementation of step S2250 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

[0572] In some embodiments, the network device sends third information to the terminal.

[0573] In step S4250, first time information is received.

[0574] The optional implementation of step S3250 can refer to the optional implementation of step S2260 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0575] In some embodiments, the network device receives first time information sent by the terminal.

[0576] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4210 to S4230. For example, step S4220 may be implemented as an independent embodiment. For example, step S4220 and step S4230 may be implemented as independent embodiments. For example, the combination of steps S4210 to S4230 may be implemented as an independent embodiment. It should be noted that one or more steps from steps S4210 to S4230 may constitute a possible independent embodiment, but are not limited to this.

[0577] In some embodiments, step S4210 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0578] In some embodiments, step S4230 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0579] Figure 4C is a schematic diagram illustrating a third flow chart of a communication method executed on a network device according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for use with network device 102, such as an access network device, in communication system 100. As shown in Figure 4C , the communication method of this embodiment of the present disclosure includes steps S4310 to S4350.

[0580] In step S4310, first configuration information is sent.

[0581] The optional implementation of step S4310 can refer to the optional implementation of step S2310 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.

[0582] In some embodiments, the network device sends first configuration information to the terminal to indicate at least one second random access sequence.

[0583] In some embodiments, the network device may further send second configuration information to indicate at least one fourth random access sequence.

[0584] In some embodiments, step S4310 may be omitted, in which case at least one second random access sequence terminal is predefined or preconfigured.

[0585] In step S4320, a first random access sequence is received.

[0586] The optional implementation of step S4320 can refer to the optional implementation of step S2340 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0587] In some embodiments, the network device receives a first random access sequence sent by the terminal.

[0588] In some embodiments, the first random access sequence is used to indicate that the terminal has successfully performed GNSS measurement within the measurement gap.

[0589] In some embodiments, the first random access sequence is used to indicate to the terminal that the GNSS measurement in the measurement gap is performed successfully.

[0590] In step S4330, it is determined whether the first random access sequence is successfully associated with the GNSS.

[0591] The optional implementation of step S4330 can refer to the optional implementation of step S2350 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0592] In step S4340, the third information is sent.

[0593] The optional implementation of step S4340 can refer to the optional implementation of step S2360 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0594] In some embodiments, the network device sends third information to the terminal.

[0595] In some embodiments, the third information is used to instruct the terminal to send a GNSS validity period on the first uplink resource.

[0596] In step S4350, first time information is received.

[0597] The optional implementation of step S4350 can refer to the optional implementation of step S2370 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

[0598] In some embodiments, the network device receives first time information sent by the terminal.

[0599] In some embodiments, the network device receives first time information sent by the terminal on a first uplink resource.

[0600] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4310 to S4350. For example, step S4320 can be implemented as an independent embodiment. For example, steps S4320 to S4330 can be implemented as independent embodiments. For example, the combination of steps S4320 to S4350 can be implemented as an independent embodiment. For example, the combination of steps S4310 to S4320 can be implemented as an independent embodiment. For example, the combination of steps S4310 to S4330 can be implemented as an independent embodiment. For example, the combination of steps S4310 to S4350 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S4310 to S4350 may form a possible independent embodiment, but are not limited to this.

[0601] In some embodiments, step S4310, step S4330, and step S4340 to step S4350 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0602] In some embodiments, step S4310 and step S4330 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0603] In some embodiments, step S4330, step S4340 to step S4350 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0604] In some embodiments, steps S4350 to S4360 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0605] In some embodiments, step S4310 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0606] Figure 4D is a fourth flow diagram illustrating a network device executing a communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for use with network device 102, such as an access network device, in communication system 100. As shown in Figure 4D, the communication method according to this embodiment of the present disclosure includes steps S4410 to S4440.

[0607] In step S4410, the correspondence between the random access sequence and the GNSS validity period is sent.

[0608] The optional implementation of step S4410 can refer to the optional implementation of step S2410 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0609] In some embodiments, the network device sends the correspondence between the random access sequence and the GNSS validity period to the terminal.

[0610] In some embodiments, step S4410 may be omitted. In this case, the correspondence between the random access sequence and the GNSS validity period or the correspondence between the random access configuration and the GNSS validity period may be predefined or preconfigured.

[0611] In step S4420, the second information is sent.

[0612] The optional implementation of step S4420 can refer to the optional implementation of step S2420 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0613] In some embodiments, the network device sends the second information to the terminal.

[0614] In some embodiments, the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.

[0615] In some embodiments, step S4420 may be omitted. In this case, the terminal autonomously performs GNSS measurement within the measurement gap.

[0616] In step S4430, a first random access sequence is received.

[0617] The optional implementation of step S4430 can refer to the optional implementation of step S2440 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0618] In some embodiments, the network device receives a first random access sequence sent by the terminal.

[0619] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0620] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0621] In step S4440, it is determined that the terminal has not successfully performed GNSS measurement within the measurement gap.

[0622] The optional implementation of step S4440 can refer to the optional implementation of step S2450 in Figure 2D and other related parts in the embodiment involved in Figure 2D, which will not be repeated here.

[0623] In some embodiments, the embodiment of FIG. 4A may be combined with the embodiment of FIG. 4D . For example, step S4110 may be combined with step S4410. In one embodiment, the correspondence between random access sequences and GNSS validity periods includes at least one random access sequence. Some of these random access sequences are associated with successful GNSS measurement execution, while others are associated with failed GNSS measurement execution.

[0624] In some embodiments, if the terminal successfully performs GNSS measurement in the measurement gap, steps S4130 to S4150 are performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, steps S4430 to S4440 are performed.

[0625] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4410 to S4440. For example, step S4430 can be implemented as an independent embodiment. For example, step S4430 and step S4440 can be implemented as independent embodiments. For example, steps S4420 to S4430 can be implemented as independent embodiments. For example, steps S4410 to S4430 can be implemented as independent embodiments. For example, the combination of steps S4420 to S4440 can be implemented as an independent embodiment. For example, the combination of steps S4410 to S4440 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S4410 to S4440 may constitute a possible independent embodiment, but are not limited to this.

[0626] In some embodiments, at least two of steps S4410 to S4440 may be performed in an order swapped or simultaneously. For example, step S4410 and step S4420 may be performed in an order swapped or simultaneously. Step S4410 and steps S4420 to S4430 may be performed in an order swapped or simultaneously.

[0627] In some embodiments, step S4410, step S4420, and step S4440 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0628] In some embodiments, step S4410 and step S4420 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0629] In some embodiments, step S4410 and step S4440 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0630] In some embodiments, step S4420 and step S4440 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0631] In some embodiments, step S4410, step S4420 or step S4440 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0632] Figure 4E is a fifth flow diagram illustrating a communication method executed on a network device according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for use with network device 102, such as an access network device, in communication system 100. As shown in Figure 4E , the communication method of this embodiment of the present disclosure includes steps S4510 to S4530.

[0633] In step S4510, the second information is sent.

[0634] The optional implementation of step S4510 can refer to the optional implementation of step S2510 in Figure 2E and other related parts in the embodiment involved in Figure 2E, which will not be repeated here.

[0635] In some embodiments, the network device sends the second information to the terminal.

[0636] In some embodiments, the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.

[0637] In some embodiments, step S4510 may be omitted. In this case, the terminal autonomously performs GNSS measurement within the measurement gap.

[0638] In step S4520, a first random access sequence is received.

[0639] The optional implementation of step S4520 can refer to the optional implementation of step S2520 in Figure 2E and other related parts in the embodiment involved in Figure 2E, which will not be repeated here.

[0640] In some embodiments, the network device receives a first random access sequence sent by the terminal.

[0641] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0642] In some embodiments, the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement within the measurement gap.

[0643] In step S4530, it is determined that the terminal has not successfully performed GNSS measurement within the measurement gap.

[0644] The optional implementation of step S4530 can refer to the optional implementation of step S2540 in Figure 2E and other related parts in the embodiment involved in Figure 2E, which will not be repeated here.

[0645] In some embodiments, the embodiment of FIG4B may be combined with the embodiment of FIG4E . For example, if the terminal successfully performs GNSS measurement within the measurement gap, steps S4220 to S4230 are performed. If the terminal fails to successfully perform GNSS measurement within the measurement gap, steps S4520 to S4530 are performed.

[0646] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4510 to S4530. For example, step S4520 can be implemented as an independent embodiment. For example, step S4520 and step S4530 can be implemented as independent embodiments. For example, the combination of steps S4510 to S4520 can be implemented as an independent embodiment. For example, the combination of steps S4510 to S4530 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S4510 to S4530 may constitute a possible independent embodiment, but are not limited to this.

[0647] In some embodiments, step S4510 and step S4530 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0648] In some embodiments, step S4510 or step S4530 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0649] Figure 4F is a sixth flow diagram illustrating a communication method executed on a network device according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for use with network device 102, such as an access network device, in communication system 100. As shown in Figure 4F, the communication method of this embodiment of the present disclosure includes steps S4610 to S4640.

[0650] In step S4610, the third configuration information is sent.

[0651] The optional implementation of step S4610 can refer to the optional implementation of step S2610 in Figure 2F and other related parts in the embodiment involved in Figure 2F, which will not be repeated here.

[0652] In some embodiments, the network device sends third configuration information to the terminal to indicate at least one third random access sequence.

[0653] In some embodiments, at least one third random access sequence is used by the terminal to determine the first random access sequence.

[0654] In some embodiments, step S4610 may be omitted, in which case at least one third random access sequence is predefined or preconfigured.

[0655] In step S4620, a first random access sequence is received.

[0656] The optional implementation of step S4620 can refer to the optional implementation of step S2640 in Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.

[0657] In step S4630, the network device determines that the first random access sequence fails to be associated with the GNSS.

[0658] The optional implementation of step S4630 can refer to the optional implementation of step S2650 in Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.

[0659] In some embodiments, the embodiment of FIG4C may be combined with the embodiment of FIG4F . For example, if the terminal successfully performs GNSS measurement within the measurement gap, steps S4320 to S4350 are performed. If the terminal fails to successfully perform GNSS measurement within the measurement gap, steps S4620 to S4630 are performed.

[0660] In some embodiments, the terminal may obtain at least one second random access sequence and at least one third random access sequence. After performing GNSS measurement within the measurement gap, the terminal may select the second random access sequence or the third random access sequence as the first random access sequence based on the result of the GNSS measurement. Then, after receiving the first random access sequence, the network device determines whether the terminal successfully performed GNSS measurement within the measurement gap based on whether the first random access sequence is the second random access sequence or the third random access sequence.

[0661] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4610 to S4630. For example, step S4620 can be implemented as an independent embodiment. For example, steps S4620 to S4630 can be implemented as independent embodiments. For example, the combination of steps S4610 to S4620 can be implemented as an independent embodiment. For example, the combination of steps S4610 to S4630 can be implemented as an independent embodiment. It should be noted that one or more steps in steps S4610 to S4630 may form a possible independent embodiment, but are not limited to this.

[0662] FIG5A is a seventh flow diagram illustrating a terminal-side communication method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for terminal 101 in communication system 100. As shown in FIG5A , the communication method of this embodiment of the present disclosure includes steps S5110 to S5120.

[0663] In step S5110, GNSS measurement is performed within the measurement gap;

[0664] For optional implementation methods of step S5110, please refer to step S2130 of Figure 2A, step S2220 of Figure 2B, step S2320 of Figure 2C, step S2430 of Figure 2D, step S2520 of Figure 2E, step S2620 of Figure 2F, step S3130 of Figure 3A, step S3220 of Figure 3B, step S3320 of Figure 3C, step S3430 of Figure 3D, step S3520 of Figure 3E, and step S3620 of Figure 3F, as well as other related parts in the embodiments involved in Figures 2A to 2F and Figures 3A to 3F, which will not be repeated here.

[0665] In step S5120, a first random access sequence is sent.

[0666] For optional implementation methods of step S5120, please refer to step S2140 of Figure 2A, step S2230 of Figure 2B, step S2340 of Figure 2C, step S2440 of Figure 2D, step S2530 of Figure 2E, step S2640 of Figure 2F, step S3140 of Figure 3A, step S3230 of Figure 3B, step S3340 of Figure 3C, step S3440 of Figure 3D, step S3530 of Figure 3E, and step S3640 of Figure 3F, as well as other related parts in the embodiments involved in Figures 2A to 2F and Figures 3A to 3F, which will not be repeated here.

[0667] In some embodiments, the terminal sends a first random access sequence to the network device.

[0668] In some embodiments, after the terminal successfully performs GNSS measurement within the measurement gap, the terminal sends a first random access sequence to the network device. In this case, the first random access sequence is used to indicate to the network device that the GNSS measurement was successfully performed, so that the network device can continue to perform subsequent random access procedures according to the first random access sequence.

[0669] In some embodiments, after the terminal fails to perform a GNSS measurement within a measurement gap, the terminal sends a first random access sequence to the network device. In this case, the first random access sequence is used to indicate to the network device that the GNSS measurement has failed, so that the network device can determine that the GNSS measurement has not been successfully performed within the measurement gap based on the first random access sequence.

[0670] In some embodiments, the above method may include the method described in the above embodiments on the communication network side and the terminal side, which will not be repeated here.

[0671] FIG5B is a seventh flow diagram illustrating a communication method executed on a network device according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method for use with a network device 102, such as an access network device, in a communication system 100. As shown in FIG5B , the communication method according to this embodiment of the present disclosure includes step S5210.

[0672] In step S5210, a first random access sequence is received.

[0673] For optional implementation methods of step S5210, please refer to step S2140 of Figure 2A, step S2230 of Figure 2B, step S2340 of Figure 2C, step S2440 of Figure 2D, step S2530 of Figure 2E, step S2640 of Figure 2F, step S4130 of Figure 4A, step S4220 of Figure 4B, step S4320 of Figure 4C, step S4430 of Figure 4D, step S4520 of Figure 4E, and step S4620 of Figure 3F, as well as other related parts in the embodiments involved in Figures 2A to 2F and Figures 4A to 4F, which will not be repeated here.

[0674] In some embodiments, the network device receives a first random access sequence sent by the terminal.

[0675] In some embodiments, after a terminal successfully performs a GNSS measurement within a measurement gap, a network device receives a first random access sequence sent by the terminal. The first random access sequence indicates to the network device that the GNSS measurement was successful. The network device can then continue to perform subsequent random access procedures based on the first random access sequence.

[0676] In some embodiments, after a terminal fails to perform a GNSS measurement within a measurement gap, the network device receives a first random access sequence sent by the terminal. In this case, the first random access sequence is used to indicate to the network device that the GNSS measurement failed. In this manner, the network device can determine, based on the first random access sequence, that the GNSS measurement failed within the measurement gap.

[0677] In some embodiments, the above method may include the method described in the above embodiments on the communication network side and the network device side, which will not be repeated here.

[0678] Figure 6 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 6, the embodiment of the present disclosure relates to a communication method, which includes steps S610 to S640.

[0679] In step S610, the terminal receives a trigger instruction from a network device (such as a base station), wherein the trigger instruction may be a MAC CE.

[0680] In step S620 , the terminal performs GNSS measurement within the measurement gap.

[0681] In some embodiments, the terminal performs GNSS measurements within a configured measurement gap.

[0682] In some embodiments, before step S610 , the terminal determines the configuration of the measurement gap based on an instruction in the configuration information or a predefined method.

[0683] In some embodiments, the length of the measurement gap may be pre-configured for the terminal or determined by the terminal based on a predefined method (e.g., determined based on information reported by the terminal). In one embodiment, the starting position information of the GNSS measurement gap may also be pre-defined or pre-configured. For example, the starting position of the GNSS measurement gap is the end position of the GNSS validity period, the time domain position N time units after the trigger instruction sent by the received network device, or the time domain position X time units after the terminal feedback HARQ position.

[0684] In step S630 , the terminal determines whether the GNSS measurement is successfully performed within the GNSS measurement gap;

[0685] In step S640, the terminal sends measurement success indication information or measurement failure indication information to the network device.

[0686] In some embodiments, the measurement success indication information may further carry indication information of the time required for GNSS positioning.

[0687] In some embodiments, if the terminal successfully performs GNSS measurement within the measurement gap, step S630 may include, but is not limited to, at least one of the following situations:

[0688] In the first case (option 1), the terminal obtains the correspondence between the PRACH sequence or PRACH resource and the GNSS validity period based on a predefined method or a network device configuration method. Based on this correspondence and the GNSS validity period, the terminal determines the PRACH sequence and initiates a random access procedure based on the PRACH sequence.

[0689] In some embodiments, the terminal receives system information sent by the network device to determine the correspondence between the PRACH sequence and the GNSS validity period. The terminal selects an appropriate PRACH sequence for uplink access based on the GNSS measurement results or its own hardware capabilities. Thus, upon receiving the PRACH sequence, the network device determines the terminal's GNSS available time information (i.e., the first time information) based on the PRACH sequence value.

[0690] In some embodiments, the time-frequency resources for transmitting the PRACH sequence are pre-configured by the network device to the target user. In this case, the terminal can transmit the PRACH sequence in a contention-free manner.

[0691] In the second case (option 2), the terminal obtains the correspondence between the PRACH sequence and the GNSS measurement success based on a predefined method or a method configured by a network device.

[0692] In some embodiments, available PRACH sequences may be divided into two groups, one group of PRACH sequences is used to indicate a successful GNSS measurement, and the other group of PRACH sequences is used for normal random access sequences.

[0693] In some embodiments, the terminal determines a PRACH sequence based on the above-mentioned correspondence and GNSS measurement results, and initiates a random access procedure. Upon receiving the PRACH sequence sent by the terminal, the network device determines to which group of PRACH sequences the PRACH sequence sent by the terminal belongs, thereby determining whether to schedule the terminal to send GNSS available time information, i.e., the first time information, on msg3.

[0694] In some embodiments, when the received PRACH sequence is a sequence for indicating a successful GNSS measurement, the network device determines to schedule the terminal to send a GNSS validity period in msg3. At this time, the terminal sends the first time information in msg3.

[0695] In some embodiments, if the terminal fails to successfully perform GNSS measurement within the measurement gap, step S630 may include, but is not limited to, the following situations:

[0696] The terminal determines whether its original GNSS validity period (i.e., the current GNSS validity period) has expired. If not, the terminal remains in the connected state until the original GNSS validity period expires, the terminal enters the idle state, or determines that a Relative Local Flow (RLF) has occurred. If it has expired, the terminal directly enters the idle state or determines that a Relative Local Flow (RLF) has occurred.

[0697] In some embodiments, the terminal obtains a correspondence between PRACH sequences and GNSS validity periods based on a predefined method or a method configured by a network device. At least one PRACH sequence in the correspondence indicates a GNSS measurement failure. Based on the correspondence, the terminal sends an indication of the GNSS measurement failure to the network device.

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

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

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

[0701] Figure 7A is a schematic diagram of the structure of a terminal according to an embodiment of the present disclosure. The structure of the terminal 101 may be as shown in Figure 7A. Terminal 7100 may include at least one of a first transceiver module 7101 and a first processing module 7102. In some embodiments, the first processing module 7102 is configured to perform GNSS measurements within a measurement gap; the first transceiver module 7101 is configured to send a first random access sequence, where the first random access sequence is used to indicate the success or failure of the GNSS measurement. Optionally, the above-mentioned first transceiver module 7101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (for example, step S2110, step S2120, step S2140, step S2210, step S2230, step S2250, step S2260, step S2310, step S2340, step S2360, step S2370, step S2410, step S2420, step S2440, step S2510, step S2530, step S2610 and step S2640, but not limited to these), which are not repeated here. Optionally, the above-mentioned first processing module 7102 is used to execute at least one of the other steps (such as step S2130, step S2220, step S2320, step S2330, step S2430, step S2520, step S2620 and step S2630, but not limited to these) performed by the terminal 101 in any of the above methods, which are not repeated here.

[0702] Figure 7B is a schematic diagram illustrating the structure of a network device according to an embodiment of the present disclosure. The structure of the network device 102 described above may be as shown in Figure 7B. Network device 7200 may include at least one of a second transceiver module 7201 and a second processing module 7202. In some embodiments, second transceiver module 7201 is configured to receive a first random access sequence, where the first random access sequence is used to indicate the success or failure of a GNSS measurement. Optionally, the above-mentioned second transceiver module 7201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the network device 102 in any of the above methods (for example, step S2110, step S2120, step S2140, step S2250, step S2260, step S2210, step S2230, step S2310, step S2340, step S2360, step S2370, step S2410, step S2420, step S2440, step S2510, step S2530, step S2610 and step S2640, but not limited to these), which are not repeated here. Optionally, the above-mentioned second processing module 7202 is used to execute at least one of the other steps (such as step S2150, step S2160, step S2240, step S2350, step S2450, step S2540 and step S2650, but not limited to these) performed by the network device 102 in any of the above methods, which are not repeated here.

[0703] In some embodiments, the transceiver module may include a first transceiver module and / or a second transceiver module, and the first transceiver module and the second transceiver module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0704] In some embodiments, the processing module may include a first processing module and / or a second processing module, which may be a single module or include multiple submodules. Optionally, the multiple submodules each execute all or part of the steps required to be executed by the processing module. Optionally, the processing module and the processor may be interchangeable.

[0705] Figure 8A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. As shown in Figure 8A, the communication device 8100 can be a network device (such as an access network device), or a terminal (such as a user device, etc.), or a chip, chip system, or processor that supports the network device to implement any of the above methods, or a chip, chip system, or processor that supports the terminal to implement any of the above methods. The communication device 8100 can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0706] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0707] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs the communication steps such as sending and / or receiving in the above method (e.g., step S2110, step S2120, step S2140, step S2210, step S2230, step S2250, step S2260, step S2310, step S2340, step S2360, step S2370, step S2410, step S2420, step S2440, step S2510, step S2530, step S2540, step S2550, step S2560, step S2570, step S2580, step S2590, step S2610, step S2620, step S2640, step S26510, step S2660, step S2670, step S2680, step S2690, step S2711, step S2712, step S2714, step S2715, step S2716, step S2717, step S2718, step S2720, step S2721 0, step S2610, and step S2640, but not limited thereto), the processor 8101 executes at least one of the other steps (e.g., step S2130, step S2150, step S2160, step S2220, step S2240, step S2320, step S2330, step S2350, step S2430, step S2450, step S2520, step S2540, step S2620, step S2630, and step S2650, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0708] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Alternatively, all or part of the memories 8103 may be located outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memory 8102 and may be configured to receive data from the memory 8102 or other devices, or to send data to the memory 8102 or other devices. For example, the interface circuits 8104 may read data stored in the memory 8102 and send the data to the processor 8101.

[0709] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0710] FIG8B is a schematic diagram of a chip structure according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the chip structure 8200 shown in FIG8B , but the present invention is not limited thereto.

[0711] In some embodiments, the chip 8200 may include one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

[0712] In some embodiments, chip 8200 may further include one or more interface circuits 8202. Alternatively, terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 8200 may further include one or more memories 8203 for storing data. Alternatively, all or part of memory 8203 may be located external to chip 8200. Optionally, interface circuit 8202 is connected to memory 8203 and may be configured to receive data from memory 8203 or other devices, or to send data to memory 8203 or other devices. For example, interface circuit 8202 may read data stored in memory 8203 and send the data to processor 8201.

[0713] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2110, step S2120, step S2140, step S2210, step S2230, step S2250, step S2260, step S2310, step S2340, step S2360, step S2370, step S2410, step S2420, step S2440, step S2510, step S2530, step S2610, and step S2640, but not limited thereto). The interface circuit 8202 performing the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 8202 performs data exchange between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps (for example, step S2130, step S2150, step S2160, step S2220, step S2240, step S2320, step S2330, step S2350, step S2430, step S2450, step S2520, step S2540, step S2620, step S2630 and step S2650, but not limited to these).

[0714] The embodiments of the present disclosure further provide a storage medium having instructions stored thereon. When the instructions are executed on the communication device 8100, the communication device 8100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

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

[0716] The embodiments of the present disclosure also provide a computer program, which, when executed on a computer, enables the computer to execute any one of the above methods.

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

[0718] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A communication method, the method comprising: Performing GNSS measurements during measurement gaps; A first random access sequence is sent, wherein the first random access sequence is used to indicate whether the GNSS measurement is successfully performed or failed.

2. The method according to claim 1, wherein: The sending of the first random access sequence includes: A first message is sent, where the first message carries the first random access sequence, and the first message is used to initiate a random access process.

3. The method according to claim 1 or 2, wherein: In the case where the GNSS measurement is successfully performed, before sending the first random access sequence, the method further includes: According to the correspondence between the random access channel sequence and the GNSS validity period, the first random access sequence associated with the GNSS validity period of the terminal is determined.

4. The method according to claim 3, wherein: The random access sequence is used for a contention-based random access procedure of the terminal.

5. The method according to claim 1 or 2, wherein: In a case where the GNSS measurement is successfully performed, the first random access sequence is configured by the network device for a non-contention-based random access procedure of the terminal.

6. The method according to claim 1 or 2, wherein: In the case where the GNSS measurement is successfully performed, before sending the first random access sequence, the method further includes: Obtaining at least one second random access sequence successfully associated with the GNSS measurement execution; The first random access sequence is determined from the at least one second random access sequence.

7. The method according to any one of claims 1 to 6, wherein: The method further comprises: The first time information is sent, where the first time information is used to indicate a GNSS validity period of the terminal.

8. The method according to claim 1 or 2, wherein: In the case where the GNSS measurement fails to be performed, before sending the first random access sequence, the method further includes: Obtaining at least one third random access sequence associated with the failure to perform the GNSS measurement; The first random access sequence is determined from the at least one third random access sequence.

9. The method according to claim 1, 2 or 8, wherein: In the case where the GNSS measurement fails to be performed, the method further includes: Determine that the validity period of the GNSS currently used by the terminal has expired; Entering the idle state or determining that a radio link failure RLF occurs.

10. The method according to claim 1 or 2, wherein: In the case where the GNSS measurement fails to be performed, the method further includes: Make sure that the validity period of the GNSS currently used by the terminal has not expired; The connection state is maintained until the validity period of the GNSS currently used by the terminal expires.

11. A communication method, the method comprising: A first random access sequence is received, where the first random access sequence is used to indicate whether a GNSS measurement of a terminal in a measurement gap is performed successfully or failed.

12. The method according to claim 11, wherein: The receiving a first random access sequence includes: A first message is received, where the first message carries the first random access sequence, and the first message is used to initiate a random access process.

13. The method according to claim 11 or 12, wherein: The method further comprises: The GNSS validity period of the terminal associated with the first random access sequence is determined according to the correspondence between the random access channel sequence and the GNSS validity period.

14. The method according to claim 13, wherein: The random access sequence is used for a contention-based random access procedure of the terminal.

15. The method according to claim 14, wherein: The method further comprises: Sending first information, where the first information is used to indicate a correspondence between the random access channel sequence and the GNSS validity period, and the correspondence is used by the terminal to determine the first random access sequence associated with the GNSS validity period of the terminal.

16. The method according to claim 11 or 12, wherein: The first random access sequence is configured by a network device for a non-contention-based random access process of the terminal.

17. The method according to claim 11 or 12, wherein: The method further comprises: The first random access sequence is determined to be a second random access sequence successfully associated with the GNSS measurement execution.

18. The method according to claim 17, wherein: The method further comprises: First configuration information is sent, where the first configuration information is used to indicate at least one second random access sequence successfully associated with the GNSS measurement execution, and the at least one second random access sequence is used by the terminal to determine the first random access sequence.

19. The method according to claim 18, wherein: The method further comprises: Sending second configuration information, where the second configuration information is used to indicate a fourth random access sequence associated with a random access procedure, where the fourth random access sequence The terminal access sequence is used for the terminal to initiate a random access process.

20. The method according to any one of claims 11 to 19, wherein: The method further comprises: First time information is received, where the first time information is used to indicate a GNSS validity period of the terminal.

21. The method according to claim 11 or 20, wherein: The method further comprises: The first random access sequence is determined to be a third random access sequence associated with the failure to perform the GNSS measurement.

22. The method according to claim 21, wherein: The method further comprises: Sending third configuration information, where the third configuration information is used to indicate at least one third random access sequence associated with the failure to perform the GNSS measurement, and the at least one third random access sequence is used by the terminal to determine the first random access sequence.

23. A communication method, the method comprising: The terminal performs a global navigation satellite system GNSS measurement during the measurement interval; The terminal sends a first random access sequence to a network device, wherein the first random access sequence is used to indicate that the GNSS measurement is executed successfully or failed.

24. A terminal, comprising: A first processing module, configured to perform a global navigation satellite system GNSS measurement within a measurement gap; The first transceiver module is used to send a first random access sequence, wherein the first random access sequence is used to indicate that the GNSS measurement is executed successfully or failed.

25. A network device comprising: The second transceiver module is used to receive a first random access sequence, wherein the first random access sequence is used to indicate a success or failure in the execution of a global navigation satellite system GNSS measurement.

26. A communication device comprising: one or more processors; one or more memories for storing instructions; The processor is used to call the instruction so that the communication device executes the communication method as described in any one of claims 1 to 10 and 11 to 22.

27. A communication system comprising: Terminals and network equipment; The terminal is configured to implement the communication method according to any one of claims 1 to 10; The network device is configured to implement the communication method according to any one of claims 11 to 22.

28. A storage medium, wherein: The storage medium stores instructions, wherein the instructions, when executed by a processor, perform the communication method according to any one of claims 1 to 10 and 11 to 22.

Images