WO2025065299A1 - 通信方法、终端、网络设备、通信设备及存储介质 - Google Patents

通信方法、终端、网络设备、通信设备及存储介质 Download PDF

Info

Publication number
WO2025065299A1
WO2025065299A1 PCT/CN2023/121813 CN2023121813W WO2025065299A1 WO 2025065299 A1 WO2025065299 A1 WO 2025065299A1 CN 2023121813 W CN2023121813 W CN 2023121813W WO 2025065299 A1 WO2025065299 A1 WO 2025065299A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
terminal
access sequence
gnss
network device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/121813
Other languages
English (en)
French (fr)
Inventor
朱亚军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to PCT/CN2023/121813 priority Critical patent/WO2025065299A1/zh
Priority to CN202380011345.4A priority patent/CN117546593A/zh
Publication of WO2025065299A1 publication Critical patent/WO2025065299A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular to a communication method, a terminal, a network device, a communication device and a storage medium.
  • GNSS Global navigation satellite system
  • IoT Internet of things
  • the terminal and network equipment need to agree on the execution of GNSS measurements by the terminal within the measurement gap.
  • Embodiments of the present disclosure provide a communication method, a terminal, a network device, a communication device, and a storage medium.
  • a communication method is proposed, which is performed by a terminal.
  • the method includes: performing GNSS measurement in a measurement gap; sending a first random access sequence, wherein the first random access sequence is used to indicate whether the GNSS measurement is successful or failed.
  • 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 of a terminal in a measurement gap is successful or failed.
  • a communication method is proposed, which is performed by a communication system.
  • the method includes: a terminal performs GNSS measurement in a measurement gap; the terminal sends a first random access sequence to a network device, wherein the first random access sequence is used to indicate whether the GNSS measurement is successful or failed.
  • a 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 whether the GNSS measurement is successfully performed or failed.
  • a network device includes: 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 is successfully performed or failed.
  • a communication device comprises: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the communication device executes the communication method as described in any one of the first and second aspects.
  • a communication system which comprises: a terminal and a network device, wherein the terminal is configured to implement the communication method as described in the first aspect, and the network device is configured to implement the communication method as described in the second aspect.
  • a storage medium wherein instructions are stored in the storage medium, and when the instructions are executed by a processor, the communication method described in the first aspect or the second aspect is executed.
  • a computer program or a computer program product includes codes.
  • the instructions are executed by a processor, the communication method described in the first aspect or the second aspect is executed.
  • the technical solution provided by the embodiments of the present disclosure enables the terminal and the network device to reach an agreement on the execution status of the GNSS measurement of the terminal within the measurement gap.
  • FIG1A is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure.
  • 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.
  • FIG1C is a schematic diagram of a scenario in which uplink and downlink are not aligned on the network device side according to an embodiment of the present disclosure.
  • FIG. 2A is a schematic diagram of a first flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG. 2B is a schematic diagram of a second flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG. 2C is a schematic diagram of a third flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG. 2D is a fourth flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG2E is a fifth flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG2F is a sixth flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG3A is a schematic diagram of a first flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.
  • 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.
  • FIG3C is a schematic diagram of a third flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.
  • FIG3D is a schematic diagram of a fourth flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.
  • FIG3E is a fifth flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.
  • FIG3F is a sixth flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.
  • 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.
  • 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.
  • 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.
  • FIG. 4D is a fourth flow chart of a network device executing a communication method according to an embodiment of the present disclosure.
  • FIG4E is a fifth flow chart of a communication method executed on a network device side according to an embodiment of the present disclosure.
  • FIG4F is a sixth flow chart of a communication method executed on a network device side according to an embodiment of the present disclosure.
  • FIG5A is a seventh flow chart of a communication method executed on a terminal side according to an embodiment of the present disclosure.
  • FIG5B is a seventh flow chart of a communication method executed on a network device side according to an embodiment of the present disclosure.
  • FIG. 6 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
  • FIG. 7A is a schematic diagram of a structure of a terminal according to an embodiment of the present disclosure.
  • FIG. 7B is a schematic diagram of a structure of a network device according to an embodiment of the present disclosure.
  • FIG8A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure.
  • FIG8B is a schematic diagram of a structure of a chip according to an embodiment of the present disclosure.
  • the 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.
  • an embodiment of the present disclosure provides a communication method, which is performed by a terminal.
  • the method includes: performing GNSS measurement in a measurement gap; sending a first random access sequence, wherein the first random access sequence is used to indicate whether the GNSS measurement is performed successfully or failed.
  • 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.
  • sending a first random access sequence includes: sending a first message, the first message carries the first random access sequence, and the first message is used for the terminal to initiate a random access process.
  • the terminal can use the first message in the random access process, such as msg1, to carry the first random access sequence to indicate to the network device whether it has successfully performed GNSS measurement within the measurement gap.
  • the terminal and the network device can reach an agreement on the result of the GNSS measurement performed by the corresponding terminal, thereby avoiding information asymmetry between the terminal and the network device.
  • the above method when the GNSS measurement is successfully executed, before sending the first random access sequence, 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.
  • the terminal in the contention-based random access scenario, there is a correspondence between the random access sequence and the GNSS validity period, and the terminal can select a suitable random access sequence based on the above correspondence to indicate to the network device that the terminal has successfully performed GNSS measurement in the measurement gap and determined the corresponding GNSS validity period.
  • the terminal can not only reach an agreement with the network device on the execution result of the GNSS measurement of the terminal in the measurement gap, but also indicate the GNSS validity period of the terminal to the network device and trigger the random access process, thereby reducing signaling overhead and saving terminal power consumption.
  • the above-mentioned random access sequence is used for a contention-based random access process of a terminal.
  • the first random access sequence is configured by the network device for a non-contention-based random access process of the terminal.
  • the terminal in the scenario of non-contention-based random access, can send a configured random access sequence to the network device, indicating to the network device that it has successfully performed GNSS measurement within the measurement gap, and performing a non-contention-based random access process.
  • the terminal can not only reach an agreement with the network device on the execution result of the GNSS measurement of the terminal within the measurement gap, but also trigger a non-contention-based random access process, thereby reducing signaling overhead and saving terminal power consumption.
  • the above method when the GNSS measurement is successfully executed, before sending the first random access sequence, 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.
  • the terminal can determine a random access sequence from at least one random access sequence successfully associated with the GNSS measurement execution to indicate to the network device that it has successfully performed the GNSS measurement in the measurement gap and trigger the random access process.
  • the terminal can reach an agreement with the network device on the execution result of the GNSS measurement of the terminal in the measurement gap by sending the random access sequence once, It can also trigger a random access process, thereby reducing signaling overhead and saving terminal power consumption.
  • 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.
  • the terminal 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.
  • the above method in the event of a GNSS measurement failure, before sending the first random access sequence, 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.
  • the terminal can determine a random access sequence from at least one random access sequence associated with the failure of GNSS measurement execution to indicate to the network device that it has not successfully performed GNSS measurement within the measurement gap. 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 the situation of information asymmetry between the terminal and the network device.
  • the above method 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 (radio link failure, RLF) has occurred.
  • RLF radio link failure
  • the above method when the GNSS measurement fails, 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.
  • an embodiment of the present disclosure provides a communication method, 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 of a terminal in a measurement gap is successful or failed.
  • receiving a 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.
  • 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.
  • the random access sequence is used for a contention-based random access procedure of a terminal.
  • 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.
  • the first random access sequence is configured by a network device for a non-contention-based random access process of a terminal.
  • the 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.
  • 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.
  • 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.
  • the above method also 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.
  • the method further includes: determining that the first random access sequence is a third random access sequence associated with a failure in executing a GNSS measurement.
  • 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.
  • an embodiment of the present disclosure provides a communication method, which is performed by a communication system.
  • the method includes: a terminal performs GNSS measurement in a measurement gap; the terminal sends a first random access sequence to a network device, wherein the first random access sequence is used to indicate whether the GNSS measurement is successful or failed.
  • the terminal sends a first random access sequence to a 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.
  • the above method when the GNSS measurement is successfully executed, before the terminal sends a 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.
  • the method when the GNSS measurement is successfully performed, after the terminal sends the first random access sequence to the network device, the method further includes: the network device generates a random access channel sequence according to the corresponding relationship between the random access channel sequence and the GNSS validity period. system, determining a GNSS validity period of a terminal associated with a first random access sequence.
  • the random access sequence is used for a contention-based random access procedure of a terminal.
  • the above method also includes: the network device sends first information to the terminal, and the first information is used to indicate the corresponding relationship between the random access channel sequence and the GNSS validity period.
  • the first random access sequence is configured by the network device for a non-contention-based random access process of the terminal.
  • the above method when the GNSS measurement is successfully executed, before the terminal sends a 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.
  • the method further 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.
  • the above method 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.
  • 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.
  • the above method also includes: the terminal sends first time information to the network device, and the first time information is used to indicate the GNSS validity period of the terminal.
  • the method further includes: the terminal obtains at least one third random access sequence associated with the GNSS measurement failure; the terminal determines the first random access sequence from the at least one third random access sequence.
  • the method further includes: the network device determines that the first random access sequence is a third random access sequence associated with a failure in executing a GNSS measurement.
  • the above method before the terminal sends a 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.
  • the method when the GNSS measurement fails, the method further 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.
  • the above method 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.
  • an embodiment of the present disclosure provides a terminal.
  • the terminal includes: a first processing module, configured to perform GNSS measurement in 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 whether the GNSS measurement is successful or failed.
  • 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.
  • the first processing module is used to determine a first random access sequence associated with the GNSS validity period of the terminal according to the correspondence between the random access channel sequence and the GNSS validity period when the GNSS measurement is successfully executed.
  • the random access sequence is used for a contention-based random access procedure of a terminal.
  • the first random access sequence is configured by the network device for a non-contention-based random access process of the terminal.
  • 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.
  • the first transceiver module is used to send first time information, and the first time information is used to indicate the GNSS validity period of the terminal.
  • 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.
  • 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 an RLF occurs.
  • 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.
  • an embodiment of the present disclosure provides a network device.
  • the network device includes: 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 of a terminal in a measurement gap is successful or failed.
  • 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.
  • 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 according to 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.
  • 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.
  • the first random access sequence is configured by a network device for a non-contention-based random access process of a terminal.
  • the second processing module is further used to determine that the first random access sequence is a second random access sequence that is successfully associated with the GNSS measurement execution.
  • 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.
  • 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.
  • 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.
  • the above-mentioned network device also 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.
  • 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.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes: one or more processors; one or more memories for storing instructions; wherein the processor is used to call the instructions so that the communication device executes the communication method as described in any one of the first aspect, the second aspect and the embodiments thereof.
  • an embodiment of the present disclosure provides 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.
  • an embodiment of the present disclosure provides a storage medium storing instructions.
  • the communication device executes the communication method of any one of the first aspect, the second aspect and the embodiments thereof.
  • an embodiment of the present disclosure proposes a computer program product.
  • the communication device executes a communication method as described in any one of the first aspect, the second aspect and their embodiments.
  • an embodiment of the present disclosure proposes a computer program, which, when executed on a communication device, enables a computer to execute a communication method as described in any one of the first aspect, the second aspect, and the embodiments thereof.
  • the embodiments of the present disclosure provide a communication method, a terminal, a network device, a communication device, and a storage medium.
  • the terms such as communication method and information processing method can be replaced with each other.
  • the terms such as terminal, network device, communication device, information processing device can be replaced with each other.
  • the terms such as communication system and information processing system can be replaced with each other.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily.
  • the solution after removing some steps can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged.
  • the optional implementations in a certain embodiment can be combined arbitrarily.
  • the embodiments can be combined arbitrarily. For example, some or all of the steps of different embodiments can be combined arbitrarily. For another example, a certain embodiment can be arbitrarily combined with the optional implementations of other embodiments.
  • elements expressed in the singular form such as “a”, “an”, “the”, “above”, “said”, “aforementioned”, “this”, etc., may mean “one and only one", or “one or more”, “at least one”, etc.
  • the noun after the article may be understood as a singular expression or a plural expression.
  • plurality refers to two or more.
  • the terms “at least one”, “one or more”, “a plurality of”, “multiple”, etc. can be used interchangeably.
  • "at least one of A and B", “A and/or B", “A in one case, B in another case”, “in response to one case A, in response to another case B”, etc. may include the following technical solutions according to 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); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., the above is also similar.
  • the recording method of "A or B” may include the following technical solutions according to 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).
  • A A is executed independently of B
  • B B is executed independently of A
  • execution is selected from A and B (A and B are selectively executed).
  • 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 restrictions on the position, order, priority, quantity or content of the description objects.
  • the statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes.
  • 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”
  • the "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”.
  • 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”.
  • the number of description objects is not limited by the ordinal number, and can be one or more. Taking the "first device” as an example, the number of "devices” can be one or more.
  • the objects modified by different prefixes may be the same or different. For example, if the description object is "device”, then the “first device” and the “second device” may be the same device or different devices, and their types may be the same or different. For another example, if the description object is "information”, then the "first information” and the “second information” may be the same information or different information, and their contents may be the same or different.
  • “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • 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 lower 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”, “no more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • 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.
  • network may be interpreted as devices included in the network (eg, access network devices, core network devices, etc.).
  • terminal refers to the term “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”,
  • the terms “remote terminal”, “handset”, “user agent”, “mobile client”, and “client” are used interchangeably.
  • the access network device, the core network device, or the network device may be replaced by a terminal.
  • the communication between the access network device, the core network device, or the network device and the terminal is replaced by the communication between multiple terminals (for example, device to device).
  • the embodiments of the present disclosure may also be applied to structures of a communication network (device-to-device, D2D), vehicle-to-everything (vehicle-to-everything, V2X), etc.
  • the terminal may also be configured that the terminal has all or part of the functions of the access network device.
  • terms such as "uplink” and “downlink” may also be replaced with terms corresponding to terminal-to-terminal communication (for example, "side”).
  • an uplink channel, a downlink channel, etc. may be replaced with a side channel
  • an uplink, a downlink, etc. may be replaced with a side link.
  • the terminal may be replaced by an access network device, a core network device, or a network device.
  • the access network device, the core network device, or the network device may also be configured to have a structure that has all or part of the functions of the terminal.
  • acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.
  • FIG1A is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure.
  • a communication system 100 includes a terminal 101 and a network device 102.
  • the network device 102 may be an access network device.
  • 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 (Pad), 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 to these.
  • a mobile phone a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), 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
  • 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 evolved node (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 baseband 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.
  • eNB evolved node B
  • ng-eNB next generation evolved node
  • gNB next generation node B
  • NB node B
  • the technical solution of the present disclosure may be applicable to an open radio access network (Open RAN) architecture.
  • Open RAN open radio access network
  • the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.
  • the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be called a control unit (control unit).
  • the CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.
  • 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.
  • a person of ordinary skill in the art 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.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG. 1A or some of the entities in the communication system 100, but are not limited thereto.
  • the entities shown in FIG. 1A are examples, and the communication system 100 may include all or some of the entities in FIG. 1A, or may include other entities other than FIG. 1A, and the number and form of the entities are arbitrary, and the entities may be physical or virtual, and the connection relationship between the entities is an example, and the entities may be connected or disconnected, and the connection may be in any manner, and may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.
  • LTE long term evolution
  • LTE-A LTE-advanced
  • SUPER 3G international mobile telecommunications-advanced
  • fourth generation mobile communication system (4G)
  • 5G 5G new radio
  • NR future radio access
  • RAT new radio access technology
  • NR new radio
  • NX new radio access
  • FX future generation radio access
  • GSM Global System for Mobile communications
  • CDMA2000 Code Division Mobile Broadband
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 ultra-wideband band, UWB
  • Bluetooth registered trademark
  • PLMN Public Land Mobile Network
  • PLMN Public Land Mobile Network
  • D2D Device-to-Device
  • M2M Machine-to-Machine
  • IoT Internet of Things
  • the continuous emergence of new Internet applications such as augmented reality (AR), virtual reality (VR), and vehicle-to-vehicle (V2V) has put forward higher requirements for wireless communication technology, driving the continuous evolution of wireless communication technology to meet the needs of applications.
  • cellular mobile communication technology is in the evolution stage of a new generation of technology.
  • An important feature of the new generation of technology is to support flexible configuration of multiple service types.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communications
  • mMTC massive machine type communications
  • Satellite communication refers to the communication performed by radio communication equipment on the ground using satellites as relays.
  • the satellite communication system consists of a satellite part and a ground part.
  • the characteristics of satellite communication are: a large communication range; communication can be performed between any two points as long as they are within the range covered by the radio waves emitted by the satellite; it is not easily affected by land disasters and has high reliability.
  • satellite communication has the following characteristics: 1. Extended coverage: For areas that cannot be covered by cellular communication systems or where the coverage cost is high, such as oceans, deserts, and remote mountainous areas, satellite communication can be used to solve communication problems. 2. Emergency communication: In extreme situations such as disasters (such as earthquakes) that make the cellular communication infrastructure unavailable, satellite communication can be used to quickly establish a communication connection. 3. Provide industry applications: For example, for delay-sensitive services over long distances, satellite communication can be used to reduce the delay in service transmission.
  • K offset can be introduced to compensate for the transmission delay.
  • K offset can be applied to a variety of 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).
  • PUSCH physical uplink shared channel
  • DCI downlink control information
  • HARQ hybrid automatic repeat request
  • MAC media access control control
  • the propagation delay in the satellite communication system is much longer than the propagation delay in the ground mobile system, 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 the satellite communication system, the terminal needs to apply a larger timing advance (TA) value, but it will cause a large offset in its downlink (DL) and uplink (UL) frame timing.
  • FIG. 1B shows a scenario in which the terminal applies a larger TA and the DL frame and UL frame timing of the network device (such as the access network device) are aligned.
  • FIG. 1C shows another scenario in which the DL frame and UL frame of the access network device do not need to be aligned.
  • the terminal applies a terminal-specific TA (such as a UE-specific TA) so that the DL frame and UL frame timing are aligned at a predetermined reference point.
  • a terminal-specific TA such as a UE-specific TA
  • additional complexity is required on the network device side to manage the corresponding scheduling timing of the scenario.
  • various timing relationships need to be enhanced to cope with the large offset in the timing of the DL frame and UL frame of the terminal.
  • the terminal needs to know its own location information in order to compensate for uplink synchronization.
  • the terminal can obtain its own location information through a navigation satellite system, such as a global navigation satellite system (GNSS).
  • GNSS global navigation satellite system
  • the global navigation satellite system 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), and other navigation satellite systems and their evolution systems.
  • BDS Beidou navigation satellite system
  • GPS United States' global positioning system
  • GLONASS Russia's GLONASS
  • GALILEO European Union's Galileo navigation satellite system
  • other navigation satellite systems may also be included, and the embodiments of the present disclosure do not specifically limit this.
  • the cellular module and the GNSS module are not supported to work simultaneously, but sporadic transmission can be supported.
  • the terminal can send GNSS available time information (used to indicate the GNSS validity duration) to the network device.
  • GNSS validity duration of the terminal expires, the terminal will enter the idle state.
  • the terminal after the terminal enters the IDLE state, it needs to re-acquire the GNSS validity period, which will cause unnecessary delays.
  • the network device can trigger the terminal to perform GNSS measurement in the connected state, thereby preventing the terminal from entering the IDLE state.
  • the terminal 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 time required for GNSS positioning (GNSS position fix time duration)) to the network device, so that the network device can configure a suitable measurement gap for the terminal.
  • time information required for the measurement such as GNSS positioning duration information (used to indicate the time required for GNSS positioning (GNSS position fix time duration)
  • GNSS positioning duration information used to indicate the time required for GNSS positioning (GNSS position fix time duration)
  • the measurement gap can also be described as a GNSS measurement gap (GNSS measurement gap).
  • the terminal if it 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 consistent understanding of the execution status of the GNSS measurement, thereby affecting the random access process of the terminal.
  • GNSS measurement and “GNSS positioning” are interchangeable.
  • the terms “GNSS measurement is successfully performed”, “GNSS measurement is successfully performed”, “GNSS measurement is successfully performed”, “GNSS measurement is successfully performed”, “GNSS measurement is successful”, “measurement is successful”, etc. are interchangeable.
  • the terms “GNSS measurement fails to be performed”, “GNSS measurement is not successfully performed”, “GNSS measurement is not successfully performed”, “GNSS measurement is failed”, “GNSS measurement fails”, “measurement failure”, etc. are interchangeable.
  • Fig. 2A 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.
  • the communication method of the present disclosure embodiment includes steps S2110 to S2140.
  • step S2110 the network device sends first information.
  • the terminal receives first information.
  • the first information is used to indicate a correspondence between a random access sequence and a GNSS validity period.
  • the correspondence between the random access sequence and the GNSS validity period includes at least one random access sequence. At least a portion of the random access sequences is successfully associated with the GNSS measurement execution.
  • the correspondence between the random access sequence and the GNSS validity period may be included in the random access configuration and sent.
  • the random access configuration may also be described as a physical random access channel (PRACH) configuration, such as RACH-Config.
  • PRACH physical random access channel
  • the random access configuration is used to indicate to the terminal the random access opportunity (RACH occasion, RO) resources and at least one random access sequence configured by the network device for the terminal.
  • the random access sequence may also be referred to as a random access preamble sequence, a random access preamble code, a preamble sequence, a preamble code, etc.
  • the network device may also send 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, so that the terminal may select a resource for sending a random access sequence, i.e., an RO resource, according to the correspondence between the random access configuration and the GNSS validity period.
  • a resource for sending a random access sequence i.e., an RO resource
  • RO resources can be interchangeably used with “resources corresponding to the RO”, “resources where the RO is located”, “RO location”, etc.
  • 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 master information block (MIB), system information block 1 (SIB1), and other SIB.
  • SI system information
  • MIB master information block
  • SIB1 system information block 1
  • SIB2 system information block 1
  • 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 may be understood as the correspondence between the random access sequence and the time information.
  • the time information sent by the terminal may include at least one of GNSS positioning duration information, GNSS available time information, and the like.
  • different GNSS validity periods may correspond to one or more random access sequences.
  • different GNSS validity periods may correspond to different random access sequences one by one.
  • different GNSS validity periods correspond to multiple random access sequences, which may be the same or different.
  • one GNSS validity period may correspond to one random preamble sequence, and one GNSS validity period may correspond to multiple random sequences.
  • step S2110 may be omitted.
  • 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.
  • step S2120 the network device sends second information.
  • the terminal receives second information.
  • the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.
  • the name of the second information is not limited, and it may be, for example, “trigger information”, “trigger measurement information”, “trigger positioning information”, etc.
  • the second information may be carried in a high-level instruction and sent, such as a high-level signaling may be at least one of a radio resource control (RRC) signaling, a broadcast message, a system message, a medium access control (MAC) control element (CE), a downlink control information (DCI), and a signaling carried by a physical downlink shared channel (PDSCH).
  • RRC radio resource control
  • MAC medium access control
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • the second information may also be carried in other
  • the second information is sent in other signaling, which is not specifically limited in the embodiments of the present disclosure.
  • the second information is carried in MAC CE and sent.
  • the network device triggers the terminal to perform GNSS measurement non-periodically, and the terminal can obtain GNSS positioning within the re-measurement gap.
  • the GNSS measurement may also be performed autonomously by the terminal.
  • the terminal obtains indication information from a high level and determines that the GNSS measurement can be performed autonomously.
  • the terminal determines that under certain conditions, such as not receiving a trigger instruction to trigger the GNSS measurement sent by the network side and the GNSS of the terminal is about to expire, the terminal autonomously performs the GNSS measurement.
  • the terminal may determine whether to autonomously perform GNSS measurement according to the configuration of the network.
  • the network device may configure the terminal to enable the autonomous measurement function. If enabled, the terminal may autonomously perform GNSS measurement. If disabled, the terminal may be triggered by the network device to perform GNSS measurement.
  • step S2120 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • step S2130 the terminal performs GNSS measurement in the measurement gap.
  • the terminal determines the configuration of the measurement gap in response to the second information. Then, the terminal performs GNSS measurement in the measurement gap according to the configuration of the measurement gap.
  • the configuration of the measurement gap may include the starting position of the measurement gap, the length of the measurement gap, etc.
  • the term “length of the measurement gap” may be interchangeable with “time length of the measurement gap”, “duration of the measurement gap”, “duration of the measurement gap”, “duration of the measurement gap”, etc.
  • the measurement gap may be periodic or non-periodic.
  • the measurement gap may be predefined or preconfigured, or may be configured by the network device for the terminal.
  • predefined or preconfigured may be understood as pre-specified by the protocol and pre-negotiated and configured by the terminal and the network device.
  • “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.
  • 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.
  • 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.
  • the length of the measurement gap is greater than or equal to the time required for GNSS positioning reported by the terminal.
  • the length of the measurement gap may be pre-configured by the network device to the terminal, or it may be determined by the terminal based on its own implementation.
  • the terminal may determine the length of the measurement gap based on the time information reported by the terminal.
  • the starting position of the measurement gap may also be predefined or preconfigured.
  • the starting position of the measurement gap may be the end position of the GNSS validity period, or it may be the time domain position with an interval of N time units after receiving the trigger instruction sent by the network device, or it may be 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.
  • the starting position of the measurement gap may be based on the current GNSS validity period, with a certain delay or no delay.
  • time unit can be understood as “frame”, “sub-frame”, “time slot”, “sub-time slot”, “symbol” and the like.
  • the terminal does not need to transmit or receive any channel/signal within the measurement gap before successfully performing GNSS measurements.
  • the terminal 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 has been successfully performed.
  • the terminal may execute step S2140 if the GNSS measurement in the measurement gap is successfully performed.
  • step S2140 the terminal sends a first random access sequence.
  • the network device receives a first random access sequence.
  • the terminal sends a first random access sequence after the GNSS measurement is successfully performed.
  • the first random access sequence is used to indicate that the terminal successfully performs GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the GNSS measurement of the terminal in the measurement gap is performed successfully.
  • the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.
  • the terminal queries the correspondence between the random access sequence and the GNSS validity period according to 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.
  • 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 GNSS available time information last sent by the terminal to the network device.
  • the correspondence between the random access sequence and the GNSS validity period includes at least one random access sequence. At least a portion of these random access sequences are successfully associated with the GNSS measurement execution. Then, the terminal queries the correspondence between the random access sequence and the GNSS validity period, and determines the first random access sequence corresponding to the current GNSS validity period from the random access sequence successfully associated with the GNSS measurement execution in the above correspondence.
  • a GNSS validity period may correspond to a random preamble sequence, and a GNSS The validity period may correspond to multiple random sequences.
  • preamble A and preamble C are used to indicate that the GNSS measurement is successfully executed.
  • the terminal can select a suitable 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.
  • the terminal when the terminal obtains the correspondence between the random access configuration and the GNSS validity period, it can also query the correspondence between the random access configuration and the GNSS validity period according to the time information sent by itself to the network device, such as the GNSS available time, and determine the random access configuration corresponding to the current GNSS validity period.
  • the random access configuration can indicate the first random access sequence and the first RO. At this time, the terminal sends the first random access sequence on the first RO.
  • the first random access sequence may also be used to trigger a contention-based random access process.
  • 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 according to the correspondence between the random access sequence and the GNSS validity period. Then, after the terminal successfully performs GNSS measurement within the measurement gap, the terminal determines the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period, and sends it to the network device.
  • the first random access sequence may be carried in message 1 (message 1, msg1) in the random access process and sent.
  • 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.
  • the terminal sends the first random access sequence through PRACH signaling.
  • the terminal may also send GNSS positioning duration information to indicate the time required for GNSS positioning (GNSS position fix time duration) to the network device.
  • the GNSS positioning duration information may be sent simultaneously with the first random access sequence.
  • the GNSS positioning duration information and the first random access sequence may be carried in the same message (such as msg1) and sent.
  • step S2150 the network device determines that the terminal successfully performs GNSS measurement within the measurement gap.
  • the network device after receiving the first random access sequence, continues to perform a random access procedure according to the first random access sequence.
  • step S2160 the network device determines a GNSS validity period corresponding to the first random access sequence.
  • the network device determines the GNSS validity period corresponding to the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.
  • 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.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S2110 to S2160.
  • steps S2130 and S2140 may be implemented as independent embodiments.
  • steps S2120 to S2140 may be implemented as independent embodiments.
  • steps S2110 to S2140 may be implemented as independent embodiments.
  • the combination of steps S2130 to S2150 may be implemented as an independent embodiment.
  • the combination of steps S2130 to S2160 may be implemented as an independent embodiment.
  • the combination of steps S2120 to S2150 may be implemented as an independent embodiment.
  • the combination of steps S2110 to S2150 may be implemented as an independent embodiment.
  • step S2120 to S2160 may be implemented as an independent embodiment.
  • steps S2110 to S2160 may be implemented as an independent embodiment.
  • steps S2110 to S2160 may be implemented as an independent embodiment. It should be noted that one or more steps in step S2110 to step S2160 constitute possible independent implementation examples, but are not limited thereto.
  • steps S2110 to S2160 may be exchanged in order or performed simultaneously.
  • step S2110 and step S2120 may be exchanged in order or performed simultaneously.
  • Step S2110 and steps S2120 to S2130 may be exchanged in order or performed simultaneously.
  • step S2150 and step S2160 may be exchanged in order or performed simultaneously.
  • step S2110, step S2120, and step S2160 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2120 and step S2160 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2110 and step S2120 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2110 and step S2160 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2110, step S2120 and step S2160 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • the terminal indicates the execution status of its own GNSS measurement in the measurement gap by sending a first random access sequence to the network device.
  • 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.
  • Fig. 2B 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.
  • the communication method of the embodiment of the present disclosure includes steps S2210 to S2260.
  • step S2210 the network device sends second information.
  • step S2210 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.
  • step S2220 the terminal performs GNSS measurement in the measurement gap.
  • step S2220 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.
  • the terminal may execute step S2230 if the GNSS measurement in the measurement gap is successfully performed.
  • step S2230 the terminal sends a first random access sequence.
  • the network device receives a first random access sequence.
  • the terminal sends a first random access sequence after the GNSS measurement is successfully performed.
  • the first random access sequence is used to indicate that the terminal successfully performs GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the GNSS measurement of the terminal in the measurement gap is performed successfully.
  • the first random access sequence may also be used to trigger a non-contention-based random access process.
  • the network device indicates the first random access sequence to the terminal through a random access preamble assignment (RA preamble assignment). Then, after the terminal successfully performs GNSS measurement within the measurement gap, it sends the first random access sequence to the network device.
  • the first random access sequence may be a dedicated random access preamble code.
  • the first random access sequence may be carried in msg1 during the random access process.
  • the random access process may be 4-step random access (4-step RACH) or 2-step random access (2-step RACH), and the embodiments of the present disclosure do not specifically limit this.
  • the terminal may also send GNSS positioning duration information to indicate to the network device the time required for GNSS positioning.
  • the GNSS positioning duration information may be sent simultaneously with the first random access sequence.
  • the GNSS positioning duration information and the first random access sequence may be carried in the same message (such as msg1) for sending.
  • step S2240 the network device determines that the terminal successfully performs GNSS measurement within the measurement gap.
  • the network device after receiving the first random access sequence, continues to perform a random access procedure according to the first random access sequence.
  • step S2250 the network device sends third information.
  • the terminal receives third information.
  • the third information is used to instruct the terminal to send a GNSS validity period on the first uplink resource.
  • the name of the third information is not limited, and it may be, for example, "response information”, “random access response information”, “trigger reporting information”, etc.
  • the third information may be carried in message 2 (msg2) during the random access process.
  • 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.
  • the first uplink resource is scheduled by an uplink grant.
  • the first uplink resource is used for the terminal to send a GNSS validity period.
  • the network device sends the third information after determining that the terminal successfully performs the GNSS measurement within the measurement gap.
  • step S2260 the terminal sends the first time information.
  • the network device receives first time information, where the first time information is used to indicate a GNSS validity period of the terminal.
  • the first information may be GNSS available time information.
  • the terminal sends the first time information on the first uplink resource.
  • the first uplink resource can be carried in message 3 (message 3, msg3) during the random access process.
  • the terminal sends the GNSS validity period to the network device.
  • the terminal may send the GNSS validity period once for each measurement.
  • the terminal may also send a new GNSS validity period to the network device when the length of the GNSS validity period changes.
  • the terminal may also send other information, such as GNSS positioning duration information, while sending the GNSS available time information, to indicate the time required for GNSS positioning to the network device.
  • GNSS available time information and the GNSS positioning duration information may be carried in the same message or carried in different messages and sent simultaneously.
  • the terminal may send GNSS available time information and GNSS positioning continuity information respectively.
  • the GNSS positioning continuity information may be carried in, for example, an RRC connection reestablishment complete message (RRCConnectionReestablishmentComplete or RRCConnectionReestablishmentComplete-NB) and an RRC connection reconfiguration complete message in a handover scenario (RCConnectionReconfigurationComplete for HO case).
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S2210 to S2240.
  • steps S2220 and S2230 may be implemented as independent embodiments.
  • the combination of steps S2220 to S2240 may be implemented as an independent embodiment.
  • the combination of steps S2210 to S2230 may be implemented as an independent embodiment.
  • 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.
  • step S2210 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2240 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • the terminal indicates the execution status of its own GNSS measurement in the measurement gap by sending a first random access sequence to the network device.
  • 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.
  • Fig. 2C 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 a communication system 100.
  • the communication method of the embodiment of the present disclosure includes steps S2310 to S2370.
  • step S2310 the network device sends first configuration information.
  • the terminal receives first configuration information.
  • the first configuration information is used to indicate at least one second random access sequence.
  • the second random access sequence is associated with a successful GNSS measurement execution.
  • the second random access sequence is used to indicate a successful GNSS measurement execution.
  • the network device may also provide second configuration information.
  • the terminal receives second configuration information.
  • the second configuration information is used to indicate at least one fourth random access sequence.
  • 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.
  • the terminal may obtain at least one fourth random access sequence according to predefinition or preconfiguration.
  • 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 (such as a random access configuration) and sent.
  • step S2310 may be omitted.
  • the terminal may obtain at least one second random access sequence according to a predefined or preconfigured method.
  • step S2320 the terminal performs GNSS measurement in the measurement gap.
  • step S2320 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.
  • step S2330 the terminal determines a first random access sequence.
  • the terminal may determine the first random access sequence from at least one second random access sequence.
  • 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 one of the at least one second random access sequences as the first random access sequence. In one embodiment, the terminal may randomly select one of the at least one second random access sequences as the first random access sequence. In one embodiment, the terminal may select an appropriate second random access sequence from the at least one second random access sequence as the first random access sequence according to its own implementation, such as hardware capability.
  • the terminal may select one from at least one fourth random access sequence to initiate a random access procedure.
  • step S2340 the terminal sends a first random access sequence.
  • step S2340 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.
  • step S2350 the network device determines that the first random access sequence is successfully associated with the GNSS.
  • the network device determines that the first random access sequence is one of at least one second random access sequence, and further determines that the terminal successfully performs GNSS measurement in the measurement gap.
  • the network device after receiving the first random access sequence, continues to perform a random access procedure according to the first random access sequence.
  • step S2360 the network device sends third information.
  • the terminal receives third information.
  • the third information is used to instruct the terminal to send a GNSS validity period on the first uplink resource.
  • the name of the third information is not limited, and it may be, for example, "response information”, “random access response information”, “trigger reporting information”, etc.
  • the third information may be carried in message 2 (msg2) during the random access process.
  • 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.
  • 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.
  • the network device sends the third information after determining that the terminal successfully performs the GNSS measurement within the measurement gap.
  • step S2370 the terminal sends the first time information.
  • the network device receives first time information, where the first time information is used to indicate a GNSS validity period of the terminal.
  • the terminal sends first time information on a first uplink resource to indicate GNSS available time information.
  • the first uplink resource can be carried in message 3 (message 3, msg3) during the random access process.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S2310 to S2370.
  • steps S2320 to S2340 may be implemented as independent embodiments.
  • the combination of steps S2310 to S2340 may be implemented as an independent embodiment.
  • the combination of steps S2320 to S2350 may be implemented as an independent embodiment.
  • the combination of steps S2320 to S2370 may be implemented as an independent embodiment.
  • the combination of steps S2310 to S2370 may 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.
  • 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.
  • step S2310 and step S2350 are optional, and one or more of these steps may be omitted or replaced in different 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.
  • steps S2360 to S2370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2310 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • the terminal indicates the execution status of its own GNSS measurement in the measurement gap by sending a first random access sequence to the network device.
  • 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.
  • Fig. 2D is a fourth 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.
  • the communication method of the embodiment of the present disclosure includes steps S2410 to S2440.
  • step S2410 the network device sends first information.
  • step S2410 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.
  • the first information is used to indicate a correspondence between a random access sequence and a GNSS validity period.
  • the correspondence between the random access sequence and the GNSS validity period includes at least one random access sequence (ie, at least one third random access sequence). At least a portion of these random access sequences is associated with a GNSS measurement execution failure.
  • step S2410 may be omitted.
  • 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.
  • step S2420 the network device sends second information.
  • step S2420 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.
  • step S2420 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • step S2430 the terminal performs GNSS measurement in the measurement gap.
  • step S2430 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.
  • the terminal may execute step S2440 when the GNSS measurement within the measurement gap fails.
  • step S2440 the terminal sends a first random access sequence.
  • the network device receives a first random access sequence.
  • the terminal sends a first random access sequence after the GNSS measurement fails to be performed.
  • the first random access sequence is used to indicate that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement in the measurement gap.
  • the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.
  • the terminal queries the correspondence between the random access sequence and the GNSS validity period according to 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.
  • the correspondence between the random access sequence and the GNSS validity period includes at least one random access sequence. At least a portion of these random access sequences is associated with a GNSS measurement execution failure. Then, the terminal queries the correspondence between the random access sequence and the GNSS validity period, and determines the first random access sequence corresponding to the current GNSS validity period from the random access sequence associated with the GNSS measurement execution failure in the correspondence.
  • the first random access sequence can be carried in message 1 (message 1, msg1) during the random access process.
  • the terminal sends the first random access sequence through PRACH signaling.
  • the terminal may also determine that the current GNSS validity period has not expired, and the terminal remains in a connected state until the current GNSS validity period expires. Then, the terminal enters an idle state or determines that RLF occurs.
  • 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 RLF occurs.
  • the terminal determining that RLF occurs may also be described as the terminal entering an RLF state.
  • the terminal if the terminal fails to reacquire GNSS positioning within the measurement gap, it can remain in a connected state within 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 after the GNSS measurement timer ends or determines that RLF occurs. In one embodiment, when the terminal does not have a GNSS measurement timer after the GNSS measurement gap, the terminal enters IDLE mode after the measurement gap ends or determines that RLF occurs.
  • step S2450 the network device determines that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the embodiment of FIG. 2A may be combined with the embodiment of FIG. 2D.
  • step S2110 may be combined with step S2410.
  • the correspondence between the random access sequence and the GNSS validity period includes at least one random access sequence. Some of these random access sequences are associated with successful GNSS measurement execution, and the other parts are associated with failed GNSS measurement execution.
  • step S2140 is performed. If the terminal does not successfully perform GNSS measurement in the measurement gap, steps S2440 to S2450 are performed.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S2410 to S2450.
  • steps S2430 and S2440 can be implemented as independent embodiments.
  • steps S2420 to S2440 can be implemented as independent embodiments.
  • steps S2410 to S2440 can be implemented as independent embodiments.
  • the combination of steps S2430 to S2450 can be implemented as an independent embodiment.
  • the combination of steps S2420 to S2450 can be implemented as an independent embodiment.
  • 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 be composed of a possible independent embodiment, but are not limited to this.
  • steps S2410 to S2450 may be performed in an exchanged order or simultaneously.
  • step S2410 and step S2420 may be performed in an exchanged order or simultaneously.
  • Step S2410 and steps S2420 to S2430 may be performed in an exchanged order or simultaneously.
  • step S2410 and step S2420 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2410 or step S2420 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • the terminal indicates the execution status of its own GNSS measurement in the measurement gap by sending a first random access sequence to the network device.
  • 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.
  • Fig. 2E is a fifth 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.
  • the communication method of the embodiment of the present disclosure includes steps S2510 to S2540.
  • step S2510 the network device sends second information.
  • step S2510 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.
  • step S2520 the terminal performs GNSS measurement in the measurement gap.
  • step S2520 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.
  • the terminal may execute step S2530 when the GNSS measurement fails.
  • step S2530 the terminal sends a first random access sequence.
  • the network device receives a first random access sequence.
  • the terminal sends a first random access sequence after the GNSS measurement fails to be performed.
  • the first random access sequence is used to indicate that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement in the measurement gap.
  • the first random access sequence may be carried in msg1 during the random access procedure and sent.
  • the terminal sends the first random access sequence through PRACH signaling.
  • the terminal may also determine that the current GNSS validity period has not expired, and the terminal remains in a connected state until the current GNSS validity period expires. Then, the terminal enters an idle state or determines that RLF occurs.
  • 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 RLF occurs.
  • step S2540 the network device determines that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • step S2220 if the terminal successfully performs GNSS measurement in the measurement gap, step S2230 is performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, steps S2530 to S2540 are performed.
  • the communication method involved in the embodiment of the present disclosure may include at least one of step S2510 to step S2540.
  • step S2520 and step S2530 may be implemented as independent embodiments.
  • the combination of step S2520 to step S2540 may be implemented as an independent embodiment.
  • the combination of step S2510 to step S2530 may be implemented as an independent embodiment.
  • step S2510 to step S2540 It should be noted that one or more steps in step S2510 to step S2540 may be implemented as an independent embodiment, but are not limited thereto.
  • step S2510 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • the terminal indicates the execution status of its own GNSS measurement in the measurement gap by sending a first random access sequence to the network device.
  • 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.
  • Fig. 2F is a sixth 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.
  • the communication method of the present disclosure embodiment includes steps S2610 to S2640.
  • step S2610 the network device sends third configuration information.
  • the terminal receives third configuration information.
  • the third configuration information is used to indicate at least one third random access sequence.
  • 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.
  • step S2610 may be omitted.
  • the terminal may obtain at least one third random access sequence according to a predefined or preconfigured method.
  • step S2620 the terminal performs GNSS measurement in the measurement gap.
  • step S2620 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.
  • the terminal 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.
  • the terminal autonomously performs GNSS measurements within the measurement gaps.
  • the terminal may execute step S2630 when the GNSS measurement fails.
  • step S2630 the terminal determines a first random access sequence.
  • the terminal may determine the first random access sequence from at least one third random access sequence.
  • the terminal selects a third random access sequence from at least one third random access sequence to determine 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 a suitable third random access sequence from at least one third random access sequence as the first random access sequence according to its own implementation, such as hardware capability.
  • step S2640 the terminal sends a first random access sequence.
  • step S2640 can refer to the optional method in step S2530 of Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.
  • step S2650 the network device determines that the first random access sequence fails to be associated with the GNSS.
  • 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.
  • the embodiment of FIG2C may be combined with the embodiment of FIG2F.
  • steps S2330 to S2370 are performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, steps S2630 to S2650 are performed.
  • 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 according to the execution result of the GNSS measurement. Then, after receiving the first random access sequence, the network device determines whether the terminal successfully performs the GNSS measurement within the measurement gap according to whether the first random access sequence is the second random access sequence or the third random access sequence.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S2610 to S2650.
  • steps S2620 to S2640 may be implemented as independent embodiments.
  • the combination of steps S2610 to S2640 may be implemented as an independent embodiment.
  • 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.
  • step S2610 and step S2650 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2650 is optional, and one or more of these steps may be omitted in different embodiments. Omit or replace.
  • step S2610 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • the terminal indicates the execution status of its own GNSS measurement in the measurement gap by sending a first random access sequence to the network device.
  • 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.
  • the names of information, etc. are not limited to the names recorded in the embodiments, and terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “code element”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, and “chip” can be used interchangeably.
  • terms such as “uplink”, “uplink”, “physical uplink” can be interchangeable, and terms such as “downlink”, “downlink”, “physical downlink” can be interchangeable, and terms such as “side”, “sidelink”, “side communication”, “sidelink communication”, “direct connection”, “direct link”, “direct communication”, “direct link communication” can be interchangeable.
  • DCI downlink control information
  • DL downlink
  • UL uplink
  • UL DCI uplink
  • the terms “physical downlink shared channel (PDSCH)”, “DL data” and the like can be interchangeable with each other, and the terms “physical uplink shared channel (PUSCH)”, “UL data” and the like can be interchangeable with each other.
  • radio wireless
  • RAN radio access network
  • AN access network
  • RAN-based and the like
  • terms such as “moment”, “time point”, “time”, and “time position” can be interchangeable, and terms such as “duration”, “period”, “time window”, “window”, and “time” can be interchangeable.
  • wireless access scheme and waveform may be used interchangeably.
  • frame radio frame
  • subframe slot
  • sub-slot sub-slot
  • mini-slot mini-slot
  • sub-slot sub-slot
  • mini-slot mini-slot
  • obtain can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high levels, obtaining by self-processing, autonomous implementation, etc.
  • terms such as “certain”, “preset”, “preset”, “set”, “indicated”, “some”, “any”, and “first” can be interchangeable, and "specific A”, “preset A”, “preset A”, “set A”, “indicated A”, “some A”, “any A”, and “first A” can be interpreted as A pre-defined in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., and can also be interpreted as specific A, some A, any A, or first A, etc., but is not limited to this.
  • Fig. 3A is a schematic diagram of a first flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a terminal 101 in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S3110 to S3140.
  • step S3110 a correspondence between a random access sequence and a GNSS validity period is obtained.
  • step S3110 can refer to the optional method in step S2110 of Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
  • the terminal receives first information sent by a network device, where the first information is used to indicate a corresponding relationship between a random access sequence and a GNSS validity period.
  • the terminal obtains a correspondence between a predefined or preconfigured random access sequence and a GNSS validity period.
  • step S3120 second information is obtained.
  • step S3120 can refer to the optional method in step S2120 of Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
  • the terminal receives second information sent by the network device.
  • the terminal receives second information sent by a higher layer.
  • step S3120 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • step S3130 GNSS measurement is performed within the measurement gap.
  • step S3130 can refer to the optional method in step S2130 of Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
  • step S3140 a first random access sequence is sent.
  • step S3140 can refer to the optional method in step S2140 of Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
  • the terminal sends a first random access sequence to the network device.
  • the terminal sends a first random access sequence after the GNSS measurement is successfully performed.
  • the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.
  • the first random access sequence is used by the network device to determine whether the terminal successfully performs GNSS measurement within the measurement gap.
  • 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.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S3110 to S3140.
  • steps S3130 and S3140 may be implemented as independent embodiments.
  • steps S3120 to S3140 may be implemented as independent embodiments.
  • steps S3110 to S3140 may be implemented as independent embodiments. It should be noted that one or more steps in steps S3110 to S3140 may constitute a possible independent embodiment, but are not limited thereto.
  • steps S3110 to S3140 may be performed in an exchanged order or simultaneously.
  • step S3110 and step S3120 may be performed in an exchanged order or simultaneously.
  • Step S3110 and steps S3120 to S3130 may be performed in an exchanged order or simultaneously.
  • step S3110 and step S3120 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3110 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3120 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • Fig. 3B 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.
  • the present disclosure embodiment relates to a communication method, which is used for a terminal 101 in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S3210 to S3250.
  • step S3210 second information is obtained.
  • step S3210 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.
  • the terminal receives second information sent by the network device.
  • the terminal receives second information sent by a higher layer.
  • step S3210 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • step S3220 GNSS measurement is performed within the measurement gap.
  • step S3220 can refer to the optional implementation of step S2220 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • the terminal may execute step S3230 if the GNSS measurement in the measurement gap is successfully performed.
  • step S3230 a first random access sequence is sent.
  • step S3230 can refer to the optional method in step S2230 of Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • the terminal sends a first random access sequence to the network device.
  • the terminal sends a first random access sequence after the GNSS measurement is successfully performed.
  • the first random access sequence is used by the network device to determine whether the terminal successfully performs GNSS measurement within the measurement gap.
  • 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.
  • step S3240 third information is received.
  • step S3240 can refer to the optional method in step S2250 of Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • the terminal receives third information sent by the network device.
  • step S3250 the first time information is sent.
  • step S3250 can refer to the optional method in step S2260 of Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • the terminal sends first time information to the network device.
  • the communication method involved in the embodiment of the present disclosure may include at least one of step S3210 to step S3230.
  • step S3220 and step S3230 may be implemented as independent embodiments.
  • the combination of step S3210 to step S3230 may be implemented as an independent embodiment. It should be noted that one or more steps in step S3210 to step S3230 may form a possible independent embodiment, but are not limited thereto.
  • step S3210 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • Fig. 3C is a third flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a terminal 101 in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S3310 to S3360.
  • step S3310 at least one second random access sequence is obtained.
  • step S3310 can refer to the optional method in step S2310 of Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • the terminal receives at least one second random access sequence sent by the network device.
  • the terminal obtains at least one second random access sequence that is predefined or preconfigured.
  • the terminal receives at least one fourth random access sequence sent by the network device.
  • the terminal obtains at least one fourth random access sequence that is predefined or preconfigured.
  • step S3320 GNSS measurement is performed within the measurement gap.
  • step S3320 can refer to the optional implementation of step S2320 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • step S3330 a first random access sequence is determined.
  • step S3330 can refer to the optional implementation of step S2330 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • step S3340 a first random access sequence is sent.
  • step S3340 can refer to the optional implementation of step S2340 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • the terminal sends a first random access sequence to the network device.
  • the terminal sends a first random access sequence after the GNSS measurement is successfully performed.
  • the first random access sequence is used by the network device to determine whether the terminal successfully performs GNSS measurement within the measurement gap.
  • the first random access sequence is used to trigger the network device to send third information.
  • step S3350 second information is received.
  • step S3350 can refer to the optional implementation of step S2360 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • the terminal receives second information sent by the network device.
  • step S3360 the first time information is sent.
  • step S3360 can refer to the optional implementation of step S2370 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • the terminal sends first time information to the network device.
  • the terminal sends first time information to the network device on a first uplink resource.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S3310 to S3360.
  • steps S3320 to S3340 may be implemented as independent embodiments.
  • the combination of steps S3310 to S3340 may be implemented as an independent embodiment.
  • the combination of steps S3320 to S3360 may be implemented as an independent embodiment.
  • the combination of steps S3310 to S3360 may 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.
  • step S3310, step S3360 to step S3370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3310 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • steps S3360 to S3370 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • Fig. 3D is a fourth flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a terminal 101 in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S3410 to S3440.
  • step S3410 a correspondence between a random access sequence and a GNSS validity period is obtained.
  • step S3410 can refer to the optional implementation of step S2410 in Figure 2D and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.
  • the terminal receives a correspondence between a random access sequence and a GNSS validity period sent by a network device.
  • the terminal obtains a correspondence between a predefined or preconfigured random access sequence and a GNSS validity period.
  • step S3420 second information is obtained.
  • step S3420 can refer to the optional method in step S2420 of Figure 2D, and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.
  • the terminal receives second information sent by the network device.
  • the terminal receives second information sent by a higher layer.
  • step S3420 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • step S3430 GNSS measurement is performed within the measurement gap.
  • step S3430 can refer to the optional implementation of step S2430 in Figure 2D and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.
  • the terminal may execute step S3440 when the GNSS measurement within the measurement gap fails.
  • step S3440 a first random access sequence is sent.
  • step S3440 can refer to the optional method in step S2440 of Figure 2D and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.
  • the terminal sends a first random access sequence to the network device.
  • the terminal sends a first random access sequence after the GNSS measurement fails to be performed.
  • the terminal sends the first random access sequence according to the correspondence between the random access sequence and the GNSS validity period.
  • the first random access sequence is used to indicate that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement in the measurement gap.
  • the embodiment of FIG. 3A may be combined with the embodiment of FIG. 3D.
  • step S3110 may be combined with step S3410.
  • the correspondence between the random access sequence and the GNSS validity period includes at least one random access sequence. Some of these random access sequences are associated with successful GNSS measurement execution, and the other parts are associated with failed GNSS measurement execution.
  • step S3140 may be performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, step S3440 is performed.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S3410 to S3440.
  • steps S3430 and S3440 may be implemented as independent embodiments.
  • steps S3420 to S3440 may be implemented as independent embodiments.
  • steps S3410 to S3440 may be implemented as independent embodiments. It should be noted that one or more steps in steps S3410 to S3440 may constitute a possible independent embodiment, but are not limited thereto.
  • steps S3410 to S3440 may be performed in an exchanged order or simultaneously.
  • step S3410 and step S3420 may be performed in an exchanged order or simultaneously.
  • Step S3410 and steps S3420 to S3430 may be performed in an exchanged order or simultaneously.
  • step S3410 and step S3420 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3410 or step S3420 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • Fig. 3E is a fifth flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a terminal 101 in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S3510 to S3530.
  • step S3510 second information is obtained.
  • step S3510 can refer to the optional implementation of step S2510 in Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.
  • the terminal receives second information sent by the network device.
  • the terminal receives second information sent by a higher layer.
  • step S3510 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • step S3520 GNSS measurement is performed within the measurement gap.
  • step S3520 can refer to the optional implementation of step S2520 in Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.
  • the terminal may execute step S3530 when the GNSS measurement fails.
  • step S3530 a first random access sequence is sent.
  • step S3530 can refer to the optional method in step S2530 of Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.
  • the terminal sends a first random access sequence to the network device.
  • the terminal sends a first random access sequence after the GNSS measurement fails to be performed.
  • the first random access sequence is used to indicate that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement in the measurement gap.
  • step S3230 is performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, step S3530 is performed.
  • the communication method involved in the embodiment of the present disclosure may include at least one of step S3510 to step S3530.
  • step S3520 and step S3530 may be implemented as independent embodiments.
  • the combination of step S3510 to step S3530 may be implemented as an independent embodiment. It should be noted that one or more steps in step S3510 to step S3530 may form a possible independent embodiment, but are not limited thereto.
  • step S3510 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • Fig. 3F is a sixth flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a terminal 101 in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S3610 to S3640.
  • step S3610 at least one third random access sequence is obtained.
  • step S3610 can refer to the optional implementation of step S2610 in Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.
  • 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.
  • the terminal obtains at least one third random access sequence that is predefined or preconfigured.
  • step S3620 GNSS measurement is performed within the measurement gap.
  • step S3620 can refer to the optional implementation of step S2620 in Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.
  • the terminal may execute step S3630 when the GNSS measurement fails.
  • step S3630 a first random access sequence is determined.
  • step S3630 can refer to the optional implementation of step S2630 in Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.
  • step S3640 a first random access sequence is sent.
  • step S3640 can refer to the optional method in step S2640 of Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.
  • the terminal sends a first random access sequence to the network device.
  • the terminal sends a first random access sequence after the GNSS measurement fails to be performed.
  • the first random access sequence is used to indicate that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement in the measurement gap.
  • 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.
  • the embodiment of FIG3C may be combined with the embodiment of FIG3F.
  • steps S3330 to S3340 are performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, steps S3630 to S3640 are performed.
  • 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 according to the execution result of the GNSS measurement. Then, after receiving the first random access sequence, the network device determines whether the terminal successfully performs the GNSS measurement within the measurement gap according to whether the first random access sequence is the second random access sequence or the third random access sequence.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S3610 to S3640.
  • steps S3620 to S3640 may be implemented as independent embodiments.
  • the combination of steps S3610 to S3640 may be implemented as independent embodiments. It should be noted that one or more steps in steps S3610 to S3640 may be independent embodiments, but are not limited thereto.
  • step S3610 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG4A is a first flow chart of a network device side communication method according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a network device 102, such as an access network device, in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S4110 to S4150.
  • step S4110 the first information is sent.
  • step S4110 can refer to the optional method in step S2110 of Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
  • the network device sends first information to the terminal.
  • the first information is used to indicate the corresponding relationship between the random access sequence and the GNSS validity period.
  • step S4110 may be omitted, in which case the correspondence between the random access sequence and the GNSS validity period is predefined or preconfigured.
  • step S4120 the second information is sent.
  • step S4120 can refer to the optional method in step S2120 of Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.
  • the network device sends the second information to the terminal.
  • step S4120 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.
  • step S4130 a first random access sequence is received.
  • 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.
  • the first random access sequence is used to indicate that the terminal successfully performs GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the GNSS measurement of the terminal in the measurement gap is performed successfully.
  • step S4140 it is determined whether the terminal successfully performs GNSS measurement within the measurement gap.
  • 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.
  • step S4150 a GNSS validity period corresponding to the first random access sequence is determined.
  • 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.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S4110 to S4150.
  • steps S4130 and S4140 may be implemented as independent embodiments.
  • steps S4120 to S4140 may be implemented as independent embodiments.
  • steps S4110 to S4140 may be implemented as independent embodiments.
  • the combination of steps S4130 to S4150 may be implemented as an independent embodiment.
  • the combination of steps S4120 to S4150 may be implemented as an independent embodiment.
  • the combination of steps S4110 to S4150 may be implemented as an independent embodiment. It should be noted that one or more steps in steps S4110 to S4150 may be composed of a possible independent embodiment, but are not limited to this.
  • steps S4110 to S4150 may be performed in an exchanged order or simultaneously.
  • step S4110 and step S4120 may be performed in an exchanged order or simultaneously.
  • Step S4110 and steps S4120 to S4130 may be performed in an exchanged order or simultaneously.
  • step S4150 and step S4160 may be executed in an exchanged order or simultaneously.
  • step S4110, step S4120, and step S4150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4120 and step S4150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4110 and step S4120 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4110 and step S4150 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4110, step S4120 and step S4150 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG. 4B is a schematic diagram of a second flow chart of a communication method performed by a network device side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a network device 102 in a communication system 100, such as an access network device.
  • the communication method of the present disclosure embodiment includes steps S4210 to S4230.
  • step S4210 the second information is sent.
  • 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.
  • the network device sends the second information to the terminal.
  • step S4210 may be omitted, in which case the terminal autonomously performs GNSS measurement in the measurement gap.
  • the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.
  • step S4220 a first random access sequence is received.
  • step S4220 can refer to the optional method in step S2230 of Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • the network device receives a first random access sequence sent by the terminal.
  • the first random access sequence is used to indicate that the terminal successfully performs GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the GNSS measurement of the terminal in the measurement gap is performed successfully.
  • step S4230 it is determined whether the terminal successfully performs GNSS measurement within the measurement gap.
  • step S4230 can refer to the optional implementation of step S2240 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • step S4240 the third information is sent.
  • step S3240 can refer to the optional method in step S2250 of Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • the network device sends third information to the terminal.
  • step S4250 first time information is received.
  • step S3250 can refer to the optional method in step S2260 of Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
  • the network device receives first time information sent by the terminal.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S4210 to S4230.
  • step S4220 may be implemented as an independent embodiment.
  • step S4220 and step S4230 may be implemented as independent embodiments.
  • the combination of steps S4210 to S4230 may be implemented as an independent embodiment. It should be noted that one or more steps in steps S4210 to S4230 may form a possible independent embodiment, but are not limited to this.
  • step S4210 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4230 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG4C is a third flow chart of a communication method performed by a network device side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a network device 102 in a communication system 100, such as an access network device.
  • the communication method of the present disclosure embodiment includes steps S4310 to S4350.
  • step S4310 first configuration information is sent.
  • step S4310 can refer to the optional implementation of step S2310 in FIG. 2C and the embodiment involved in FIG. 2C. Other related parts will not be elaborated here.
  • the network device sends first configuration information to the terminal to indicate at least one second random access sequence.
  • the network device may further send second configuration information to indicate at least one fourth random access sequence.
  • step S4310 may be omitted, in which case at least one second random access sequence terminal is predefined or preconfigured.
  • step S4320 a first random access sequence is received.
  • step S4320 can refer to the optional implementation of step S2340 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • the network device receives a first random access sequence sent by the terminal.
  • the first random access sequence is used to indicate that the terminal successfully performs GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the GNSS measurement of the terminal in the measurement gap is performed successfully.
  • step S4330 it is determined whether the first random access sequence is successfully associated with the GNSS.
  • step S4330 can refer to the optional implementation of step S2350 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • step S4340 the third information is sent.
  • step S4340 can refer to the optional implementation of step S2360 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • the network device sends third information to the terminal.
  • the third information is used to instruct the terminal to send a GNSS validity period on the first uplink resource.
  • step S4350 first time information is received.
  • step S4350 can refer to the optional implementation of step S2370 in Figure 2C and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.
  • the network device receives first time information sent by the terminal.
  • the network device receives first time information sent by the terminal on a first uplink resource.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S4310 to S4350.
  • step S4320 can be implemented as an independent embodiment.
  • steps S4320 to S4330 can be implemented as independent embodiments.
  • the combination of steps S4320 to S4350 can be implemented as an independent embodiment.
  • the combination of steps S4310 to S4320 can be implemented as an independent embodiment.
  • the combination of steps S4310 to S4330 can be implemented as an independent embodiment.
  • 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 be composed of a possible independent embodiment, but are not limited to this.
  • 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.
  • step S4310 and step S4330 are optional, and one or more of these steps may be omitted or replaced in different 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.
  • steps S4350 to S4360 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4310 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG4D is a fourth flow chart of a network device executing a communication method according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a network device 102 in a communication system 100, such as an access network device.
  • the communication method of the present disclosure embodiment includes steps S4410 to S4440.
  • step S4410 the correspondence between the random access sequence and the GNSS validity period is sent.
  • step S4410 can refer to the optional implementation of step S2410 in Figure 2D and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.
  • the network device sends the correspondence between the random access sequence and the GNSS validity period to the terminal.
  • step S4410 may be omitted.
  • 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.
  • step S4420 the second information is sent.
  • step S4420 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.
  • the network device sends the second information to the terminal.
  • the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.
  • step S4420 may be omitted, in which case the terminal autonomously performs GNSS measurement within the measurement gap.
  • step S4430 a first random access sequence is received.
  • step S4430 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.
  • the network device receives a first random access sequence sent by the terminal.
  • the first random access sequence is used to indicate that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement in the measurement gap.
  • step S4440 it is determined that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • step S4440 can refer to the optional implementation of step S2450 in Figure 2D and other related parts of the embodiment involved in Figure 2D, which will not be repeated here.
  • the embodiment of FIG. 4A may be combined with the embodiment of FIG. 4D.
  • step S4110 may be combined with step S4410.
  • the correspondence between the random access sequence and the GNSS validity period includes at least one random access sequence. Some of these random access sequences are associated with successful GNSS measurement execution, and the other parts are associated with failed GNSS measurement execution.
  • steps S4130 to S4150 are performed. If the terminal does not successfully perform GNSS measurement in the measurement gap, steps S4430 to S4440 are performed.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S4410 to S4440.
  • step S4430 can be implemented as an independent embodiment.
  • step S4430 and step S4440 can be implemented as independent embodiments.
  • steps S4420 to S4430 can be implemented as independent embodiments.
  • steps S4410 to S4430 can be implemented as independent embodiments.
  • the combination of steps S4420 to S4440 can be implemented as an independent embodiment.
  • 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 be composed of a possible independent embodiment, but are not limited to this.
  • steps S4410 to S4440 may be performed in an exchanged order or simultaneously.
  • step S4410 and step S4420 may be performed in an exchanged order or simultaneously.
  • Step S4410 and steps S4420 to S4430 may be performed in an exchanged order or simultaneously.
  • step S4410, step S4420, and step S4440 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4410 and step S4420 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4410 and step S4440 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4420 and step S4440 are optional, and one or more of these steps may be omitted or replaced in different 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.
  • FIG4E is a fifth flow chart of a communication method executed by a network device side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a network device 102 in a communication system 100, such as an access network device.
  • the communication method of the present disclosure embodiment includes steps S4510 to S4530.
  • step S4510 the second information is sent.
  • step S4510 can refer to the optional implementation of step S2510 in Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.
  • the network device sends the second information to the terminal.
  • the second information is used to trigger the terminal to perform GNSS measurement within the measurement gap.
  • step S4510 may be omitted, in which case the terminal autonomously performs GNSS measurement within the measurement gap.
  • step S4520 a first random access sequence is received.
  • step S4520 can refer to the optional implementation of step S2520 in Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.
  • the network device receives a first random access sequence sent by the terminal.
  • the first random access sequence is used to indicate that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • the first random access sequence is used to indicate that the terminal has failed to perform GNSS measurement in the measurement gap.
  • step S4530 it is determined that the terminal has not successfully performed GNSS measurement within the measurement gap.
  • step S4530 can refer to the optional implementation of step S2540 in Figure 2E and other related parts of the embodiment involved in Figure 2E, which will not be repeated here.
  • the embodiment of FIG4B may be combined with the embodiment of FIG4E.
  • steps S4220 to S4230 are performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, steps S4520 to S4530 are performed.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S4510 to S4530.
  • step S4520 can be implemented as an independent embodiment.
  • step S4520 and step S4530 can be implemented as independent embodiments.
  • the combination of steps S4510 to S4520 can be implemented as an independent embodiment.
  • 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 form a possible independent embodiment, but are not limited to this.
  • step S4510 and step S4530 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S4510 or step S4530 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG4F is a sixth flow chart of a communication method executed by a network device side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a network device 102 in a communication system 100, such as an access network device.
  • the communication method of the present disclosure embodiment includes steps S4610 to S4640.
  • step S4610 third configuration information is sent.
  • step S4610 can refer to the optional implementation of step S2610 in Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.
  • the network device sends third configuration information to the terminal to indicate at least one third random access sequence.
  • At least one third random access sequence is used by the terminal to determine the first random access sequence.
  • step S4610 may be omitted, in which case at least one third random access sequence is predefined or preconfigured.
  • step S4620 a first random access sequence is received.
  • step S4620 can refer to the optional method in step S2640 of Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.
  • step S4630 the network device determines that the first random access sequence fails to be associated with the GNSS.
  • step S4630 can refer to the optional method in step S2650 of Figure 2F and other related parts of the embodiment involved in Figure 2F, which will not be repeated here.
  • the embodiment of FIG4C may be combined with the embodiment of FIG4F.
  • steps S4320 to S4350 are performed. If the terminal fails to successfully perform GNSS measurement in the measurement gap, steps S4620 to S4630 are performed.
  • the terminal may obtain at least one second random access sequence and at least one third random access sequence. After the terminal performs GNSS measurement in the measurement gap, the second random access sequence or the third random access sequence may be selected as the first random access sequence according to the execution result of the GNSS measurement. Then, after receiving the first random access sequence, the network device determines whether the terminal successfully performs GNSS measurement in the measurement gap according to whether the first random access sequence is the second random access sequence or the third random access sequence.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S4610 to S4630.
  • step S4620 may be implemented as an independent embodiment.
  • steps S4620 to S4630 may be implemented as independent embodiments.
  • the combination of steps S4610 to S4620 may be implemented as an independent embodiment.
  • the combination of steps S4610 to S4630 may 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.
  • Fig. 5A is a seventh flow chart of a communication method executed by a terminal side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a terminal 101 in a communication system 100.
  • the communication method of the present disclosure embodiment includes steps S5110 to S5120.
  • step S5110 GNSS measurement is performed within the measurement gap
  • step S5110 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.
  • step S5120 a first random access sequence is sent.
  • step S5120 For optional implementations of step S5120, reference may be made 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.
  • the terminal sends a first random access sequence to the network device.
  • the terminal after the terminal successfully performs GNSS measurement in the measurement gap, it sends a first random access sequence to the network device.
  • the first random access sequence is used to indicate to the network device that the GNSS measurement is successfully performed, so that the network device can continue to perform subsequent random access procedures according to the first random access sequence.
  • the terminal after the terminal fails to perform GNSS measurement in the measurement gap, the terminal sends a first random access sequence to the network device.
  • the first random access sequence is used to indicate to the network device that the GNSS measurement execution failed, so that the network device can determine that the GNSS measurement was not successfully performed in the measurement gap according to the first random access sequence.
  • the above method may include the method described in the above communication network side and terminal side embodiments, which will not be repeated here.
  • Fig. 5B is a seventh flow chart of a communication method executed by a network device side according to an embodiment of the present disclosure.
  • the present disclosure embodiment relates to a communication method, which is used for a network device 102, such as an access network device, in a communication system 100.
  • the communication method of the present disclosure embodiment includes step S5210.
  • step S5210 a first random access sequence is received.
  • step S5210 can refer to the optional methods in 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, step S4620 of Figure 3F, and other related parts in the embodiments involved in Figures 2A to 2F and Figures 4A to 4F, which will not be repeated here.
  • the network device receives a first random access sequence sent by the terminal.
  • the network device receives a first random access sequence sent by the terminal.
  • the first random access sequence is used to indicate to the network device that the GNSS measurement is successfully performed. In this way, the network device can continue to perform subsequent random access procedures according to the first random access sequence.
  • the network device receives a first random access sequence sent by the terminal.
  • the first random access sequence is used to indicate to the network device that the GNSS measurement execution failed. In this way, the network device can determine that the GNSS measurement was not successfully performed in the measurement gap according to the first random access sequence.
  • 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.
  • Fig. 6 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Fig. 6, the embodiment of the present disclosure relates to a communication method, and the method includes steps S610 to S640.
  • step S610 the terminal receives a trigger instruction from a network device (such as a base station).
  • the trigger instruction may be a MAC CE.
  • step S620 the terminal performs GNSS measurement within the measurement gap.
  • the terminal performs GNSS measurements within a configured measurement gap.
  • the terminal determines the configuration of the measurement gap based on an indication of the configuration information or a predefined method.
  • the length of the measurement gap may be pre-configured for the terminal or determined by the terminal based on a pre-defined method (e.g., determined based on information reported by the terminal).
  • the starting position of the GNSS measurement gap is defined or pre-configured.
  • 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.
  • step S630 the terminal determines whether the GNSS measurement is successfully performed within the GNSS measurement gap
  • step S640 the terminal sends measurement success indication information or measurement failure indication information to the network device.
  • the measurement success indication information may further carry indication information of the time required for GNSS positioning.
  • step S630 may include, but is not limited to, at least one of the following situations:
  • 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.
  • the terminal determines the PRACH sequence based on the correspondence and the GNSS validity period, and initiates a random access process according to the PRACH sequence.
  • 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 a suitable PRACH sequence to perform uplink access based on the result of the GNSS measurement or its own hardware capability. In this way, when the network device receives the PRACH sequence, it determines the GNSS available time information (i.e., the first time information) of the terminal according to the PRACH sequence value.
  • the time-frequency resources for sending the above PRACH sequence are pre-configured by the network device to the target user.
  • the terminal can send the PRACH sequence in a non-contention free manner.
  • the terminal obtains the corresponding relationship between the PRACH sequence and the GNSS measurement success based on a predefined method or a method configured by a network device.
  • 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.
  • the terminal determines the PRACH sequence based on the above correspondence and the GNSS measurement result, and initiates a random access process.
  • the network device After receiving the PRACH sequence sent by the terminal, the network device determines which group of PRACH sequences the PRACH sequence sent by the terminal belongs to, thereby determining whether to schedule the terminal to send GNSS available time information, i.e., the first time information, on msg3.
  • 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.
  • step S630 may include but is not limited to the following situations:
  • the terminal is afraid to determine whether its original GNSS validity period (i.e., the current GNSS validity period) has expired. If it has not expired, the terminal remains in the connected state until the original GNSS validity period expires, the terminal enters the idle state (idle state) or determines that RLF has occurred. If it has expired, the terminal directly enters the idle state (idle state) or determines that RLF has occurred.
  • the original GNSS validity period i.e., the current GNSS validity period
  • the terminal obtains the correspondence between the PRACH sequence and the GNSS validity period based on a predefined method or a method configured by the network device. At least one PRACH sequence in the correspondence represents a GNSS measurement failure. Then, based on the correspondence, the terminal sends an indication of the GNSS measurement failure to the network device.
  • the embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods.
  • a device is also proposed, including a unit or module for implementing each step performed by a network device (such as an access network device) in any of the above methods.
  • the division of the units or modules in the above device is only a division of logical functions, which can be fully or partially integrated into one physical entity or physically separated in actual implementation.
  • the units or modules in the device can 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 instructions are stored in the memory.
  • the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the 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 inside the device or a memory outside the device.
  • ASIC central processing unit
  • the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits.
  • the hardware circuits may be understood as one or more processors; for example, in one implementation, the hardware circuits are application-specific integrated circuits (ASICs), and the functions of some or all of the above units or modules may be implemented by designing the logical relationship of the components in the circuits; for another example, in another implementation, the hardware circuits may be implemented by programmable logic devices (PLDs), and field programmable gate arrays (FPGAs) may be used as an example, which may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured by configuring the configuration files, thereby implementing the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented in the form of software called by the processor, or in the form of hardware circuits, or in the form of software called by the processor, and the remaining part may be implemented in
  • the processor is a circuit with signal processing capability.
  • the processor may be a circuit with an instruction A circuit with the ability to read and run commands, such as a CPU, a microprocessor, a graphics processing unit (GPU) (also 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.
  • 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.
  • 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.
  • NPU neural network processing unit
  • TPU tensor processing unit
  • DPU deep learning processing unit
  • FIG7A is a schematic diagram of a structure of a terminal according to an embodiment of the present disclosure.
  • the structure of the terminal 101 may be as shown in FIG7A.
  • the terminal 7100 may include: at least one of a first transceiver module 7101, a first processing module 7102, etc.
  • the first processing module 7102 is used to perform GNSS measurement within a measurement gap;
  • the first transceiver module 7101 is used to send a first random access sequence, wherein the first random access sequence is used to indicate that the GNSS measurement is successfully performed or failed.
  • the 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 will not be repeated here.
  • 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 will not be repeated here.
  • the first processing module 7102 is used to execute at least one of the other steps (for example, 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 will not be repeated here.
  • steps for example, step S2130, step S2220, step S2320, step S2330, step S2430, step S2520, step S2620 and step S2630, but not limited to these
  • FIG7B is a schematic diagram of a structure of a network device according to an embodiment of the present disclosure.
  • the structure of the network device 102 may be as shown in FIG7B.
  • the network device 7200 may include: at least one of a second transceiver module 7201, a second processing module 7202, etc.
  • the second transceiver module 7201 is used to receive a first random access sequence, wherein the first random access sequence is used to indicate that the GNSS measurement is executed successfully or failed.
  • the 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 will not be repeated here.
  • 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
  • the 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.
  • steps such as step S2150, step S2160, step S2240, step S2350, step S2450, step S2540 and step S2650, but not limited to these
  • 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.
  • the transceiver module may be interchangeable with the transceiver.
  • the processing module may include a first processing module and/or a second processing module, which may be a single module or may include multiple submodules.
  • the multiple submodules respectively execute all or part of the steps required to be executed by the processing module.
  • the processing module may be interchangeable with the processor.
  • FIG8A is a schematic diagram of a structure of a communication device according to an embodiment of the present disclosure.
  • the communication device 8100 may be a network device (e.g., an access network device), or a terminal (e.g., a user device, etc.), or a chip, a chip system, or a processor that supports the network device to implement any of the above methods, or a chip, a chip system, or a processor that supports the terminal to implement any of the above methods.
  • the communication device 8100 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • the communication device 8100 includes one or more processors 8101.
  • the processor 8101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and the communication data
  • the central processing unit may 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 the program, and process the data of the program.
  • the communication device 8100 is used to execute any of the above methods.
  • one or more processors 8101 are used to call instructions so that the communication device 8100 executes any of the above methods.
  • the communication device 8100 further includes one or more transceivers 8102.
  • the transceiver 8102 performs the communication steps such as sending and/or receiving in the above method (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 S2540, step S2550, step S2560, step S2570, step S2580, step S2590, step S2611, step S2620, step S2640, step S2651, step S2660, step S2670, step S2680, step S2690, step S2711, step S2720, step S2730, step S2740, step S2751, step S2760, step S2770, step S2780,
  • the transceiver may include a receiver and/or a transmitter, and the receiver and the transmitter may be separated or integrated together.
  • the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc. may be replaced with each other, the terms such as transmitter, transmitting unit, transmitter, transmitting circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.
  • the communication device 8100 further includes one or more memories 8103 for storing data.
  • the memories 8103 may also be outside the communication device 8100.
  • the communication device 8100 may include one or more interface circuits 8104.
  • the interface circuit 8104 is connected to the memory 8102, and the interface circuit 8104 may be used to receive data from the memory 8102 or other devices, and may be used to send data to the memory 8102 or other devices.
  • the interface circuit 8104 may read the data stored in the memory 8102 and send the data to the processor 8101.
  • the communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in 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.
  • 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 and 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, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • FIG8B is a schematic diagram of a structure of a chip according to an embodiment of the present disclosure.
  • the communication device 8100 may be a chip or a chip system
  • the chip 8200 may include one or more processors 8201.
  • the chip 8200 is configured to execute any of the above methods.
  • the chip 8200 may further include one or more interface circuits 8202.
  • the terms interface circuit, interface, transceiver pin, etc. may be interchangeable.
  • the chip 8200 further includes one or more memories 8203 for storing data.
  • all or part of the memory 8203 may be outside the chip 8200.
  • the interface circuit 8202 is connected to the memory 8203, the interface circuit 8202 may be used to receive data from the memory 8203 or other devices, and the interface circuit 8202 may be used to send data to the memory 8203 or other devices.
  • the interface circuit 8202 may read the data stored in the memory 8203 and send the data to the processor 8201.
  • the interface circuit 8202 performs at least one of the communication steps such as sending and/or receiving in the above method (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 thereto).
  • the interface circuit 8202 performs the communication steps such as sending and/or receiving in the above method, for example, means that the interface circuit 8202 performs data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device.
  • 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).
  • the embodiment of the present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 8100, the communication device 8100 executes any of the above methods.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices.
  • the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a temporary storage medium.
  • the embodiment of the present disclosure also provides a program product, and when the program product is executed by the communication device 8100, the communication device 8100 executes any of the above methods.
  • the program product is a computer program product.
  • the embodiment of the present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any of the above methods.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开涉及一种通信方法、终端、网络设备、通信设备及存储介质。该方法包括：终端在测量间隙内执行GNSS测量；终端向网络设备发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。通过本公开的方案，终端和网络设备能够对终端在测量间隙内的GNSS测量的执行情况达成一致。

Description

通信方法、终端、网络设备、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域，尤其涉及一种通信方法、终端、网络设备、通信设备及存储介质。
背景技术
全球导航卫星系统(global navigation satellite system，GNSS)模块和蜂窝(cellular)模块通常嵌入在终端中，诸如可穿戴设备、移动电话、膝上型计算机、物联网(internet of things，IoT)设备等。GNSS模块通过接收来自多个卫星系统的信号来计算终端的位置，即对终端进行定位。终端在获知自己的位置信息之后，能够进行上行同步的补偿。
发明内容
在卫星通信中，对于终端在测量间隙(measurement gap)内的GNSS测量的执行情况，终端和网络设备需要对达成一致。
本公开实施例提供了一种通信方法、终端、网络设备、通信设备及存储介质。
根据本公开实施例的第一方面，提出了一种通信方法，由终端执行。上述方法包括：在测量间隙内执行GNSS测量；发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。
根据本公开实施例的第二方面，提出了一种通信方法，由网络设备执行。上述方法包括：接收第一随机接入序列，其中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功或执行失败。
根据本公开实施例的第三方面，提出了一种通信方法，由通信系统执行。上述方法包括：终端在测量间隙内执行GNSS测量；终端向网络设备发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。
根据本公开实施例的第四方面，提出了一种终端。上述终端包括：第一处理模块，用于在测量间隙内执行GNSS测量；第一收发模块，用于发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。
根据本公开实施例的第五方面，提出了一种网络设备。上述网络设备包括：第二收发模块，用于接收第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。
根据本公开实施例的第六方面，提出了一种通信设备。上述通信设备包括：一个或多个处理器；用于存储指令的一个或者多个存储器；其中，处理器用于调用指令，以使得通信设备执行如第一方面和第二方面中任一项的通信方法。
根据本公开实施例的第七方面，提出了一种通信系统。上述通信系统包括：终端和网络设备，其中，终端被配置为实现如第一方面所述的通信方法，网络设备被配置为实现如第二方面所述的通信方法。
根据本公开实施例的第八方面，提供了一种存储介质。该存储介质存储有指令。指令在被处理器执行时执行如第一方面或第二方面所述的通信方法。
根据本公开实施例的第九方面，提供了一种计算机程序或计算机程序产品。该计算机程序或计算机程序产品包括代码。指令在被处理器执行时执行如第一方面或第二方面所述的通信方法。
本公开实施例提供的技术方案，使得终端和网络设备能够对终端在测量间隙内的GNSS测量的执行情况达成一致。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不构成对本公开实施例的限制。
附图说明
为了更清楚地说明本公开实施例中的技术方案，以下对实施例描述所需的附图进行介绍，以下附图仅仅是本公开的一些实施例，不对本公开的保护范围造成具体限制。
图1A是根据本公开实施例示出的通信系统的一种架构示意图。
图1B是根据本公开实施例示出的网络设备侧上下行对齐的一种场景示意图。
图1C是根据本公开实施例示出的网络设备侧上下行不对齐的一种场景示意图。
图2A是根据本公开实施例示出的通信方法的第一种流程示意图。
图2B是根据本公开实施例示出的通信方法的第二种流程示意图。
图2C是根据本公开实施例示出的通信方法的第三种流程示意图。
图2D是根据本公开实施例示出的通信方法的第四种流程示意图。
图2E是根据本公开实施例示出的通信方法的第五种流程示意图。
图2F是根据本公开实施例示出的通信方法的第六种流程示意图。
图3A是根据本公开实施例示出的终端侧执行通信方法的第一种流程示意图。
图3B是根据本公开实施例示出的终端侧执行通信方法的第二种流程示意图。
图3C是根据本公开实施例示出的终端侧执行通信方法的第三种流程示意图。
图3D是根据本公开实施例示出的终端侧执行通信方法的第四种流程示意图。
图3E是根据本公开实施例示出的终端侧执行通信方法的第五种流程示意图。
图3F是根据本公开实施例示出的终端侧执行通信方法的第六种流程示意图。
图4A是根据本公开实施例示出的网络设备侧通信方法的第一种流程示意图。
图4B是根据本公开实施例示出的网络设备侧执行通信方法的第二种流程示意图。
图4C是根据本公开实施例示出的网络设备侧执行通信方法的第三种流程示意图。
图4D是根据本公开实施例示出的网络设备执行通信方法的第四种流程示意图。
图4E是根据本公开实施例示出的网络设备侧执行通信方法的第五种流程示意图。
图4F是根据本公开实施例示出的网络设备侧执行通信方法的第六种流程示意图。
图5A是根据本公开实施例示出的终端侧执行通信方法的第七种流程示意图。
图5B是根据本公开实施例示出的网络设备侧执行通信方法的第七种流程示意图。
图6是根据本公开实施例示出的通信方法的一种交互示意图。
图7A是根据本公开实施例示出的终端的一种结构示意图。
图7B是根据本公开实施例示出的网络设备的一种结构示意图。
图8A是根据本公开实施例示出的通信设备的一种结构示意图。
图8B是根据本公开实施例示出的芯片的一种结构示意图。
具体实施方式
本公开实施例提供了一种通信方法及终端、网络设备、通信设备、系统、计算机可读存储介质。
第一方面，本公开实施例提出了一种通信方法，由终端执行。上述方法包括：在测量间隙内执行GNSS测量；发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。
在上述实施例中，终端通过向网络设备发送第一随机接入序列，来指示自身在测量间隙内是否成功执行GNSS测量，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
结合第一方面的一些实施例，在一些实施例中，发送第一随机接入序列，包括：发送第一消息，第一消息携带有第一随机接入序列，第一消息用于终端发起随机接入过程。
在上述实施例中，终端可以通过随机接入过程中的第一消息，如msg1携带第一随机接入序列，以向网络设备指示自身在测量间隙内是否成功执行GNSS测量，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
结合第一方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，在发送第一随机接入序列之前，上述方法还包括：根据随机接入信道序列与GNSS有效期的对应关系，确定与终端的GNSS有效期关联的第一随机接入序列。
在上述实施例中，在基于竞争的随机接入场景下，随机接入序列与GNSS有效期存在对应关系，终端可以基于上述对应关系，选择合适的随机接入序列，以向网络设备指示终端在测量间隙内成功执行GNSS测量并确定相应的GNSS有效期。如此，终端通过一次发送随机接入序列，既能够与网络设备对终端在测量间隙内的GNSS测量的执行结果达成一致，还能够向网络设备指示终端的GNSS有效期以及触发随机接入过程，从而减少信令开销，节省终端功耗。
结合第一方面的一些实施例，在一些实施例中，上述随机接入序列用于终端的基于竞争的随机接入过程。
结合第一方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，第一随机接入序列是由网络设备为终端的基于非竞争的随机接入过程配置的。
在上述实施例中，在基于非竞争的随机接入的场景下，终端可以通过向网络设备发送配置的随机接入序列，向网络设备指示自身在测量间隙内成功执行GNSS测量，并发基于非竞争的随机接入过程。如此，终端通过一次发送随机接入序列，既能够与网络设备对终端在测量间隙内的GNSS测量的执行结果达成一致，还能够触发基于非竞争的随机接入过程，从而减少信令开销，节省终端功耗。
结合第一方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，在发送第一随机接入序列之前，上述方法还包括：获得与GNSS测量执行成功关联的至少一个第二随机接入序列；从至少一个第二随机接入序列中，确定第一随机接入序列。
在上述实施例中，终端可以通过与GNSS测量执行成功关联的至少一个随机接入序列中确定一个随机接入序列，以向网络设备指示自身在测量间隙内成功执行GNSS测量，并触发随机接入过程。如此，终端通过一次发送随机接入序列，既能够与网络设备对终端在测量间隙内的GNSS测量的执行结果达成一致， 还能够触发随机接入过程，从而减少信令开销，节省终端功耗。
结合第一方面的一些实施例，在一些实施例中，上述方法还包括：发送第一时间信息，第一时间信息用于指示终端的GNSS有效期。
在上述实施例中，终端在向网络设备指示自身在测量间隙内成功执行GNSS测量之后，还可以向网络设备指示自身的GNSS有效期，以使得网络设备能够根据终端发送的时间信息为终端配置相应的测量间隙，以提高GNSS定位的效率。
结合第一方面的一些实施例，在一些实施例中，在GNSS测量执行失败的情况下，在发送第一随机接入序列之前，上述方法还包括：获得与GNSS测量执行失败关联的至少一个第三随机接入序列；从至少一个第三随机接入序列中，确定第一随机接入序列。
在上述实施例中，终端可以通过与GNSS测量执行失败关联的至少一个随机接入序列中确定一个随机接入序列，以向网络设备指示自身在测量间隙内未成功执行GNSS测量。如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
结合第一方面的一些实施例，在一些实施例中，在GNSS测量执行失败的情况下，上述方法还包括：确定终端当前使用的GNSS有效期已过期；进入空闲状态或确定发生无线链路失败(radio link failure，RLF)。
结合第一方面的一些实施例，在一些实施例中，在GNSS测量执行失败的情况下，上述方法还包括：确定终端当前使用的GNSS有效期未过期；保持处于连接状态，直至终端当前使用的GNSS有效期过期。
第二方面，本公开实施例提出了一种通信方法，由网络设备执行。上述方法包括：接收第一随机接入序列，其中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功或执行失败。
结合第二方面的一些实施例，在一些实施例中，接收第一随机接入序列，包括：接收第一消息，第一消息中携带有第一随机接入序列，第一消息用于终端发起随机接入过程。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：根据随机接入信道序列与GNSS有效期的对应关系，确定第一随机接入序列关联的终端的GNSS有效期。
结合第二方面的一些实施例，在一些实施例中，随机接入序列用于终端的基于竞争的随机接入过程。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：发送第一信息，第一信息用于指示随机接入信道序列与GNSS有效期的对应关系，该对应关系用于终端确定与GNSS有效期关联的第一随机接入序列。
结合第二方面的一些实施例，在一些实施例中，第一随机接入序列是由网络设备为终端的基于非竞争的随机接入过程配置的。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：确定第一随机接入序列为与GNSS测量执行成功关联的第二随机接入序列。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：发送第一配置信息，第一配置信息用于指示与GNSS测量执行成功关联的至少一个第二随机接入序列，至少一个第二随机接入序列用于终端确定第一随机接入序列。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：发送第二配置信息，第二配置信息用于指示与随机接入过程关联的第四随机接入序列，第四随机接入序列用于终端发起随机接入过程。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：发送第二消息，第二消息中携带有GNSS可用时间信息，GNSS可用时间信息用于指示终端的GNSS有效期。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：确定第一随机接入序列为与GNSS测量执行失败关联的第三随机接入序列。
结合第二方面的一些实施例，在一些实施例中，上述方法还包括：发送第三配置信息，第三配置信息用于指示与GNSS测量执行失败关联的至少一个第三随机接入序列，至少一个第三随机接入序列用于终端确定第一随机接入序列。
第三方面，本公开实施例提出了一种通信方法，由通信系统执行。上述方法包括：终端在测量间隙内执行GNSS测量；终端向网络设备发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。
结合第三方面的一些实施例，在一些实施例中，终端向网络设备发送第一随机接入序列，包括：终端向网络设备发送第一消息，第一消息携带有第一随机接入序列，第一消息用于终端发起随机接入过程。
结合第三方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，在终端向网络设备发送第一随机接入序列之前，上述方法还包括：终端根据随机接入信道序列与GNSS有效期的对应关系，确定与终端的GNSS有效期关联的第一随机接入序列，随机接入序列用于终端的基于竞争的随机接入过程。
结合第三方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，在终端向网络设备发送第一随机接入序列之后，上述方法还包括：网络设备根据随机接入信道序列与GNSS有效期的对应关 系，确定第一随机接入序列关联的终端的GNSS有效期。
结合第三方面的一些实施例，在一些实施例中，随机接入序列用于终端的基于竞争的随机接入过程。
结合第三方面的一些实施例，在一些实施例中，上述方法还包括：网络设备向终端发送第一信息，第一信息用于指示随机接入信道序列与GNSS有效期的对应关系。
结合第三方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，第一随机接入序列是由网络设备为终端的基于非竞争的随机接入过程配置的。
结合第三方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，在终端向网络设备发送第一随机接入序列之前，上述方法还包括：终端获得与GNSS测量执行成功关联的至少一个第二随机接入序列；终端从至少一个第二随机接入序列中，确定第一随机接入序列。
结合第三方面的一些实施例，在一些实施例中，在终端向网络设备发送第一随机接入序列之后，上述方法还包括：网络设备确定第一随机接入序列为与GNSS测量执行成功关联的第二随机接入序列。
结合第三方面的一些实施例，在一些实施例中，在终端向网络设备发送第一随机接入序列之前，上述方法还包括：网络设备向终端发送第一配置信息，第一配置信息用于指示与GNSS测量执行成功关联的至少一个第二随机接入序列。
结合第三方面的一些实施例，在一些实施例中，上述方法还包括：网络设备向终端发送第二配置信息，第二配置信息用于指示与随机接入过程关联的第四随机接入序列，第四随机接入序列用于终端发起随机接入过程。
结合第三方面的一些实施例，在一些实施例中，上述方法还包括：终端向网络设备发送第一时间信息，第一时间信息用于指示终端的GNSS有效期。
结合第三方面的一些实施例，在一些实施例中，在GNSS测量执行失败的情况下，在终端向网络设备发送第一随机接入序列之前，上述方法还包括：终端获得与GNSS测量执行失败关联的至少一个第三随机接入序列；终端从至少一个第三随机接入序列中，确定第一随机接入序列。
结合第三方面的一些实施例，在一些实施例中，在终端向网络设备发送第一随机接入序列之后，上述方法还包括：网络设备确定第一随机接入序列为与GNSS测量执行失败关联的第三随机接入序列。
结合第三方面的一些实施例，在一些实施例中，在终端向网络设备发送第一随机接入序列之前，上述方法还包括：网络设备向终端发送第三配置信息，第三配置信息用于指示与GNSS测量执行失败关联的至少一个第三随机接入序列。
结合第三方面的一些实施例，在一些实施例中，在GNSS测量执行失败的情况下，上述方法还包括：终端确定终端当前使用的GNSS有效期已过期；终端进入空闲状态或确定发生RLF。
结合第三方面的一些实施例，在一些实施例中，在GNSS测量执行失败的情况下，上述方法还包括：终端确定终端当前使用的GNSS有效期未过期；终端保持处于连接状态，直至终端当前使用的GNSS有效期过期。
第四方面，本公开实施例提出了一种终端。上述终端包括：第一处理模块，用于在测量间隙内执行GNSS测量；第一收发模块，用于发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。
结合第四方面的一些实施例，在一些实施例中，第一收发模块，用于发送第一消息，第一消息携带有第一随机接入序列，第一消息用于终端发起随机接入过程。
结合第四方面的一些实施例，在一些实施例中，第一处理模块，用于在GNSS测量执行成功的情况下，根据随机接入信道序列与GNSS有效期的对应关系，确定与终端的GNSS有效期关联的第一随机接入序列。
结合第四方面的一些实施例，在一些实施例中，随机接入序列用于终端的基于竞争的随机接入过程。
结合第四方面的一些实施例，在一些实施例中，在GNSS测量执行成功的情况下，第一随机接入序列是由网络设备为终端的基于非竞争的随机接入过程配置的。
结合第四方面的一些实施例，在一些实施例中，第一处理模块，用于在GNSS测量执行成功的情况下，获得与GNSS测量执行成功关联的至少一个第二随机接入序列；从至少一个第二随机接入序列中，确定第一随机接入序列。
结合第四方面的一些实施例，在一些实施例中，第一收发模块，用于发送第一时间信息，第一时间信息用于指示终端的GNSS有效期。
结合第四方面的一些实施例，在一些实施例中，第一处理模块，用于在GNSS测量执行失败的情况下，获得与GNSS测量执行失败关联的至少一个第三随机接入序列；从至少一个第三随机接入序列中，确定第一随机接入序列。
结合第四方面的一些实施例，在一些实施例中，第一处理模块，用于在GNSS测量执行失败的情况下，确定终端当前使用的GNSS有效期已过期；进入空闲状态或确定发生RLF。
结合第四方面的一些实施例，在一些实施例中，第一处理模块，用于在GNSS测量执行失败的情况下，确定终端当前使用的GNSS有效期未过期；保持处于连接状态，直至终端当前使用的GNSS有效期过期。
第五方面，本公开实施例提出了一种网络设备。上述网络设备包括：第二收发模块，用于接收第一随机接入序列，其中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功或执行失败。
结合第五方面的一些实施例，在一些实施例中，第二收发模块，用于接收第一消息，第一消息中携带有第一随机接入序列，第一消息用于终端发起随机接入过程。
结合第五方面的一些实施例，在一些实施例中，上述网络设备还包括：第二处理模块，用于根据随机接入信道序列与GNSS有效期的对应关系，确定第一随机接入序列关联的终端的GNSS有效期，随机接入序列用于终端的基于竞争的随机接入过程。
结合第五方面的一些实施例，在一些实施例中，上述网络设备还包括：第一收发模块，用于发送第一信息，第一信息用于指示随机接入信道序列与GNSS有效期的对应关系，该对应关系用于终端确定与终端的GNSS有效期关联的第一随机接入序列。
结合第五方面的一些实施例，在一些实施例中，第一随机接入序列是由网络设备为终端的基于非竞争的随机接入过程配置的。
结合第五方面的一些实施例，在一些实施例中，第二处理模块，还用于确定第一随机接入序列为与GNSS测量执行成功关联的第二随机接入序列。
结合第五方面的一些实施例，在一些实施例中，上述网络设备还包括：第一收发模块，用于发送第一配置信息，第一配置信息用于指示与GNSS测量执行成功关联的至少一个第二随机接入序列，至少一个第二随机接入序列用于终端确定第一随机接入序列。
结合第五方面的一些实施例，在一些实施例中，第一收发模块，还用于发送第二配置信息，第二配置信息用于指示与随机接入过程关联的第四随机接入序列，第四随机接入序列用于终端发起随机接入过程。
结合第五方面的一些实施例，在一些实施例中，第二收发模块，用于接收第一时间信息，第一时间信息用于指示终端的GNSS有效期。
结合第五方面的一些实施例，在一些实施例中，上述网络设备还包括：第二处理模块，用于确定第一随机接入序列为与GNSS测量执行失败关联的第三随机接入序列。
结合第五方面的一些实施例，在一些实施例中，上述网络设备还包括：第一收发模块，用于发送第三配置信息，第三配置信息用于指示与GNSS测量执行失败关联的至少一个第三随机接入序列，至少一个第三随机接入序列用于终端确定第一随机接入序列。
第六方面，本公开实施例提出了一种通信设备。上述通信设备包括：一个或多个处理器；用于存储指令的一个或多个存储器；其中，处理器用于调用指令以使得通信设备执行如第一方面、第二方面及其实施例中任一项的通信方法。
第七方面，本公开实施例提出了一种通信系统。上述通信系统包括：终端和网络设备，其中，终端被配置为实现如第一方面及其实施例中任一项的通信方法，网络设备被配置为实现如第二方面及其实施例任一项的通信方法。
第八方面，本公开实施例提出了一种存储介质，存储介质存储有指令。当指令在通信设备上运行时，使得通信设备执行如第一方面、第二方面及其实施例中任一项的通信方法。
第九方面，本公开实施例提出了一种计算机程序产品，上述计算机程序产品被通信设备执行时，使得上述通信设备执行如第一方面、第二方面及其实施例中任一项的通信方法。
第十方面，本公开实施例提出了一种计算机程序，当其在通信设备上运行时，使得计算机执行如第一方面、第二方面及其实施例中任一项的通信方法。
可以理解地，上述终端、网络设备、通信设备、存储介质、计算机程序产品以及计算机程序均用于执行本公开实施例所提出的方法。因此，其所能达到的有益效果可以参考对应方法中的有益效果，此处不再赘述。
本公开实施例提出了一种通信方法、终端、网络设备、通信设备及存储介质。在一些实施例中，通信方法、信息处理方法等术语可以相互替换。终端、网络设备、通信装置、信息处理装置等术语可以相互替换。通信系统、信息处理系统等术语可以相互替换。
本公开实施例并非穷举，仅为部分实施例的示意，不作为对本公开保护范围的具体限制。在不矛盾的情况下，某一实施例中的每个步骤均可以作为独立实施例来实施，且各步骤之间可以任意组合。例如，在某一实施例中去除部分步骤后的方案也可以作为独立实施例来实施，且在某一实施例中各步骤的顺序可以任意交换。另外，某一实施例中的可选实现方式可以任意组合。此外，各实施例之间可以任意组合。例如，不同实施例的部分或全部步骤可以任意组合。又例如，某一实施例可以与其他实施例的可选实现方式任意组合。
在各本公开实施例中，如果没有特殊说明以及逻辑冲突，各实施例之间的术语和/或描述具有一致性，且可以互相引用，不同实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本公开实施例中所使用的术语只是为了描述特定实施例的目的，而并非作为对本公开的限制。
在本公开实施例中，除非另有说明，以单数形式表示的元素，如“一个”、“一种”、“该”、“上述”、“所述”、“前述”、“这一”等，可以表示“一个且只有一个”，也可以表示“一个或多个”、“至少一个”等。例如，在翻译中使用如英语中的“a”、“an”、“the”等冠词(article)的情况下，冠词之后的名词可以理解为单数表达形式，也可以理解为复数表达形式。
在本公开实施例中，“多个”是指两个或两个以上。
在一些实施例中，“至少一者(至少一项、至少一个、至少之一)(at least one of)”、“一个或多个(one or more)”、“多个(a plurality of)”、“多个(multiple)”等术语可以相互替换。
在一些实施例中，“A、B中的至少一者”、“A和/或B”、“在一情况下A，在另一情况下B”、“响应于一情况A，响应于另一情况B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)；在一些实施例中A和B(A和B都被执行)。当有A、B、C等更多分支时也类似上述。
在一些实施例中，“A或B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)。当有A、B、C等更多分支时也类似上述。
本公开实施例中的“第一”、“第二”等前缀词，仅仅为了区分不同的描述对象，不对描述对象的位置、顺序、优先级、数量或内容等构成限制，对描述对象的陈述参见权利要求或实施例中上下文的描述，不应因为使用前缀词而构成多余的限制。例如，描述对象为“字段”，则“第一字段”和“第二字段”中“字段”之前的序数词并不限制“字段”之间的位置或顺序，“第一”和“第二”并不限制其修饰的“字段”是否在同一个消息中，也不限制“第一字段”和“第二字段”的先后顺序。再如，描述对象为“等级”，则“第一等级”和“第二等级”中“等级”之前的序数词并不限制“等级”之间的优先级。再如，描述对象的数量并不受序数词的限制，可以是一个或者多个，以“第一装置”为例，其中“装置”的数量可以是一个或者多个。此外，不同前缀词修饰的对象可以相同或不同，例如，描述对象为“装置”，则“第一装置”和“第二装置”可以是相同的装置或者不同的装置，其类型可以相同或不同；再如，描述对象为“信息”，则“第一信息”和“第二信息”可以是相同的信息或者不同的信息，其内容可以相同或不同。
在一些实施例中，“包括A”、“包含A”、“用于指示A”、“携带A”，可以解释为直接携带A，也可以解释为间接指示A。
在一些实施例中，“响应于……”、“响应于确定……”、“在……的情况下”、“在……时”、“当……时”、“若……”、“如果……”等术语可以相互替换。
在一些实施例中，“大于”、“大于或等于”、“不小于”、“多于”、“多于或等于”、“不少于”、“高于”、“高于或等于”、“不低于”、“以上”等术语可以相互替换，“小于”、“小于或等于”、“不大于”、“少于”、“少于或等于”、“不多于”、“低于”、“低于或等于”、“不高于”、“以下”等术语可以相互替换。
在一些实施例中，装置等可以解释为实体的、也可以解释为虚拟的，其名称不限定于实施例中所记载的名称，“装置”、“设备(equipment)”、“设备(device)”、“电路”、“网元”、“节点”、“功能”、“单元”、“部件(section)”、“系统”、“网络”、“芯片”、“芯片系统”、“实体”、“主体”等术语可以相互替换。
在一些实施例中，“网络”可以解释为网络中包含的设备(例如，接入网设备、核心网设备等)。
在一些实施例中，“接入网设备(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)”、“服务小区”、“载波(carrier)”、“分量载波(component carrier)”、“带宽部分(bandwidth part，BWP)”等术语可以相互替换。
在一些实施例中，“终端(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)”等术语可以相互替换。
在一些实施例中，接入网设备、核心网设备、或网络设备可以被替换为终端。例如，针对将接入网设备、核心网设备或网络设备以及终端间的通信替换为多个终端间的通信(例如，设备对设备
(device-to-device，D2D)、车联网(vehicle-to-everything，V2X)等)的结构，也可以应用本公开的各实施例。在该情况下，也可以设为终端具有接入网设备所具有的全部或部分功能的结构。此外，“上行”、“下行”等术语也可以被替换为与终端间通信对应的术语(例如，“侧行(side)”)。例如，上行信道、下行信道等可以被替换为侧行信道，上行链路、下行链路等可以被替换为侧行链路。
在一些实施例中，终端可以被替换为接入网设备、核心网设备、或网络设备。在该情况下，也可以设为接入网设备、核心网设备、或网络设备具有终端所具有的全部或部分功能的结构。
在一些实施例中，获取数据、信息等可以遵照所在地国家的法律法规。
在一些实施例中，可以在得到用户同意后获取数据、信息等。
此外，本公开实施例的表格中的每一元素、每一行、或每一列均可以作为独立实施例来实施，任意元素、任意行、任意列的组合也可以作为独立实施例来实施。
图1A是根据本公开实施例示出的通信系统的一种架构示意图。
如图1A所示，通信系统100包括终端101以及网络设备102。网络设备102可以为接入网设备。
在一些实施例中，终端101例如包括手机(mobile phone)、可穿戴设备、物联网设备、具备通信功能的汽车、智能汽车、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备中的至少一者，但不限于此。
在一些实施例中，接入网设备例如是将终端接入到无线网络的节点或设备，接入网设备可以包括5G通信系统中的演进节点B(evolved nodeB，eNB)、下一代演进节点(next generation eNB，ng-eNB)、下一代节点B(next generation nodeB，gNB)、节点B(node B，NB)、家庭节点B(home nodeB，HNB)、家庭演进节点B(home evolved nodeB，HeNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、基带单元(base band unit，BBU)、移动交换中心、6G通信系统中的基站、开放型基站(Open RAN)、云基站(Cloud RAN)、其他通信系统中的基站、Wi-Fi系统中的接入节点中的至少一者，但不限于此。
在一些实施例中，本公开的技术方案可适用于开放式无线接入网(Open RAN)架构，此时，本公开实施例所涉及的接入网设备间或者接入网设备内的接口可变为Open RAN的内部接口，这些内部接口之间的流程和信息交互可以通过软件或者程序实现。
在一些实施例中，接入网设备可以由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将接入网设备的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU，但不限于此。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提出的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提出的技术方案对于类似的技术问题同样适用。
下述本公开实施例可以应用于图1A所示的通信系统100、或该通信系统100中的部分主体，但不限于此。图1A所示的各主体是例示，通信系统100可以包括图1A中的全部或部分主体，也可以包括图1A以外的其他主体，各主体数量和形态为任意，各主体可以是实体的也可以是虚拟的，各主体之间的连接关系是例示，各主体之间可以不连接也可以连接，其连接可以是任意方式，可以是直接连接也可以是间接连接，可以是有线连接也可以是无线连接。
本公开各实施例可以应用于长期演进(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(注册商标))、CDMA2000、超移动宽带(Ultra Mobile Broadband，UMB)、IEEE 802.11(Wi-Fi(注册商标))、IEEE 802.16(WiMAX(注册商标))、IEEE 802.20、超宽带(ultra-wide  band，UWB)、蓝牙(Bluetooth(注册商标))、陆上公用移动通信网(Public Land Mobile Network，PLMN)网络、设备到设备(Device-to-Device，D2D)系统、机器到机器(Machine to Machine，M2M)系统、物联网(Internet of Things，IoT)系统、车联网(Vehicle-to-Everything，V2X)、利用其他通信方法的系统、基于它们而扩展的下一代系统等。此外，也可以将多个系统组合(例如，LTE或者LTE-A与5G的组合等)应用。
在本公开实施例中，新一代的增强现实(augmented Reality，AR)和虚拟现实(virtual reality，VR)、车车通信(vehicle-to-vehicle，V2V)等新型互联网应用的不断涌现对于无线通信技术提出了更高的要求，驱使无线通信技术的不断演进以满足应用的需求。当下，蜂窝移动通信技术正在处于新一代技术的演进阶段。新一代技术的一个重要特点就是要支持多种业务类型的灵活配置。由于不同的业务类型对于无线通信技术有不同的要求，如增强移动宽带(enhanced mobile broadband，eMBB)业务类型主要的要求侧重在大带宽，高速率等方面；低时延高可靠通信(ultra-reliable low-latency communications，URLLC)业务类型主要的要求侧重在较高的可靠性以及低的时延方面；海量机器类型通信(massive machine type communication，mMTC)业务类型主要的要求侧重在大的连接数方面。因此新一代的无线通信系统需要灵活和可配置的设计来支持多种业务类型的传输。
在无线通信技术中，卫星通信被认为是未来无线通信技术发展的一个重要方面。卫星通信是指地面上的无线电通信设备利用卫星作为中继而进行的通信。卫星通信系统由卫星部分和地面部分组成。卫星通信的特点是：通信范围大；只要在卫星发射的电波所覆盖的范围内，任何两点之间都可进行通信；不易受陆地灾害的影响，可靠性高。
卫星通信作为地面的通信系统的补充，具有如下特点：1、可以延伸覆盖：对于蜂窝通信系统无法覆盖或是覆盖成本较高的地区，如海洋、沙漠和偏远山区等，可以通过卫星通信来解决通信的问题。2、应急通信：在发生灾难(如，地震等)的极端情况导致蜂窝通信的基础设施不可用的条件下，使用卫星通信可以快速的建立通信连接。3、提供行业应用：比如对于长距离传输的时延敏感业务，可以通过卫星通信的方式来降低业务传输的时延。
可以预见地，在未来的无线通信系统中，卫星通信系统和陆地上的蜂窝通信系统会逐步的实现深度的融合，真正的实现万物智联。
在本公开实施例中，对于卫星通信的场景下，由于发送端与接收端存在较长的信号传输距离，导致数据传输有较大的时间。对于存在有上下行关系的传输，可以引入偏移参数(Koffset)来补偿传输时延。其中，Koffset可以应用在多种操作下，比如：下行控制信息(downlink control information，DCI)调度的物理上行共享信道(physical uplink shared channel，PUSCH)传输；混合自动重传请求(hybrid automatic repeat request，HARQ)反馈信息的传输以及媒体访问控制(media access control，MAC)控制元素(control element，CE)的传输等。
在一些实施例中，卫星通信系统中的传播延迟相比于地面移动系统中的传播延迟要长得多，根据星载或机载平台的高度和卫星通信系统中的有效载荷类型，从几毫秒到数百毫秒不等。所以，在卫星通信系统中，终端需要应用较大的定时提前(timing advance，TA)值，但是会导致其下行(downlink，DL)和上行(uplink，UL)帧定时出现较大偏移。图1B示出了一种场景，其中终端应用较大TA并且网络设备(如接入网设备)的DL帧和UL帧定时对齐。图1C示出了另一种场景，其中，接入网设备的DL帧和UL帧之间不需要对齐。终端应用终端专用TA(如UE-specific TA)使得DL帧和UL帧定时在预定参考点对齐。然而，对于图1C所示的场景，网络设备侧需要额外的复杂性来管理该场景的相应调度时序。如此，便需要增强各种时序关系(timing relationships)以应对终端的DL帧和UL帧的时序中的大偏移。
那么，在卫星通信的场景下，终端需要获知自己的位置信息，以便于进行上行同步的补偿。在一些实施例中，终端可以通过导航卫星系统，如全球导航卫星系统(global navigation satellite system，GNSS)来获取自身的位置信息。
在一些实施例中，全球导航卫星系统(GNSS)可以包括中国的北斗卫星导航系统(beidou navigation satellite system，BDS)、美国的全球定位系统(global positioning system，GPS)、俄罗斯的格洛纳斯卫星导航系统(global navigation satellite system，GLONASS)和欧盟的伽利略卫星导航系统(galileo navigation satellite system，GALILEO)等各国的导航卫星系统及其演进系统。当然，还可以包括其他导航系统，本公开实施例对此不做具体限定。
在一些实施例中，对于IoT的终端来讲，不支持蜂窝(cellular)模块和GNSS模块同时工作，可以支持偶发(sporadic)的传输。终端在获取GNSS测量结果后，可以将GNSS可用时间信息(用于指示GNSS有效期(GNSS validity duration))发送给网络设备。当终端的GNSS有效期过期后，终端会进入到空闲(IDLE)状态。
在一些实施例中，终端进入IDLE状态后，需要重新获取GNSS有效期会带来不必要的时延。因此， 网络设备可以触发终端执行连接态下的GNSS测量，从而避免终端进入到IDLE状态。
在一些实施例中，在终端进行GNSS测量之前，终端还需要向网络设备发送测量所需要的时间信息(如GNSS定位持续信息(用于指示GNSS定位所需时间(GNSS position fix time duration))，以便于网络设备为终端配置合适的测量间隙(measurement gap)。在一实施例中，测量间隙也可以被描述为GNSS测量间隙(GNSS measurement gap)。
在一些实施例中，终端若在测量间隙内成功执行了GNSS测量，便可以基于实现发起随机接入过程，然而，网络设备并不清楚终端在测量间隙内的GNSS测量是否执行成功，这导致终端和网络设备无法对GNSS测量的执行情况达成一致理解，从而影响终端的随机接入过程。
需要说明的是，术语“GNSS测量”与“GNSS定位”可以互相替换。术语“GNSS测量执行成功”、“GNSS测量成功执行”、“成功执行GNSS测量”、“GNSS测量成功”、“测量成功”等可以互相替换。术语“GNSS测量执行失败”、“GNSS测量未成功执行”、“未成功执行GNSS测量”、“GNSS测量失败”、“测量失败”等可以互相替换。
图2A是根据本公开实施例示出的通信方法的第一种流程示意图。本公开实施例涉及通信方法，用于通信系统100。如图2A所示，本公开实施例的通信方法包括步骤S2110至步骤S2140。
在步骤S2110中，网络设备发送第一信息。
在一些实施例中，终端接收第一信息。
在一些实施例中，第一信息用于指示随机接入序列与GNSS有效期的对应关系。
在一些实施例中，随机接入序列与GNSS有效期的对应关系包含有至少一个随机接入序列。这些随机接入序列中的至少一部分与GNSS测量执行成功关联。
在一些实施例中，随机接入序列与GNSS有效期的对应关系可以包含于随机接入配置中发送。随机接入配置也可以描述为物理随机接入信道(physical random access channel，PRACH)配置，如RACH-Config。随机接入配置用于向终端指示随机接入时机(RACH occasion，RO)资源以及网络设备为终端配置的至少一个随机接入序列。示例性的，随机接入序列也可以称为随机接入前导(preamble)序列、随机接入前导码、前导序列、前导码等。
在一些实施例中，网络设备还可以发送随机接入配置与GNSS有效期的对应关系。由于随机接入配置可以指示RO资源和至少一个随机接入序列，那么，随机接入配置与GNSS有效期的对应关系不仅可以指示随机接入序列与GNSS有效期的对应关系，还可以指示RO资源与GNSS有效期的对应关系，使得终端能够根据随机接入配置与GNSS有效期的对应关系，选择发送随机接入序列的资源，即RO资源。
在一些实施例中，术语“RO资源”可以与“RO对应的资源”、“RO所在资源”、“RO位置”等相互替换。
在一些实施例中，网络设备可以将随机接入序列与GNSS有效期的对应关系或随机接入配置与GNSS有效期的对应关系承载于系统信息(system information，SI)，如主信息块(master information block，MIB)、系统信息块1(system information block 1，SIB1)、其他SIB(other SIB)中发送。
在一些实施例中，GNSS有效期可以通过终端发送的时间信息来指示。相应地，随机接入序列与GNSS有效期的对应关系可以理解为随机接入序列与时间信息的对应关系。在一些实施例中，终端发送的时间信息可以包括GNSS定位持续信息、GNSS可用时间信息等至少之一。
在一些实施例中，不同的GNSS有效期可以对应于一个或者多个随机接入序列。示例性的，不同的GNSS有效期可以一一对应于不同的随机接入序列。或者，不同的GNSS有效期对应于多个随机接入序列，这些随机接入序列可以是相同的，也可以是不同的。在一些实施例中，在上述对应关系中，一个GNSS有效期可以与一个随机前导序列对应，一个GNSS有效期可以与多个随机序列对应。
在一些实施例中，步骤S2110可以被省略，此时，随机接入序列与GNSS有效期的对应关系或者随机接入配置与GNSS有效期的对应关系，可以是预定义或者预配置的。
在步骤S2120中，网络设备发送第二信息。
在一些实施例中，终端接收第二信息。
在一些实施例中，第二信息用于触发终端在测量间隙内执行GNSS测量。
在一些实施例中，第二信息的名称不做限定，其例如是“触发信息”、“触发测量信息”、“触发定位信息”等。
在一些实施例中，第二信息可以承载于高层指令中发送，如高层信令可以为无线资源控制(radio resource control，RRC)信令、广播消息、系统消息、媒体接入控制(medium access control，MAC)控制元素(control element，CE)、下行信道控制信息(downlink control information，DCI)以及物理下行共享信道(physical downlink share channel，PDSCH)携带的信令等至少之一。当然，第二信息还可以承载于其 他信令中发送，本公开实施例对此不做具体限定。示例性的，第二信息承载于MAC CE中发送。
在一些实施例中，网络设备非周期性地触发终端执行GNSS测量，终端可以重新测量间隙内获取GNSS定位。
在一些实施例中，GNSS测量也可以是终端自主执行的。示例性的，终端获得来自高层的指示信息，确定可以自主执行GNSS测量。终端判断在满足一定条件下，比如没有收到网络侧发送触发GNSS测量的触发指令，并且终端的GNSS即将过期的情况下，终端自主执行GNSS测量。
在一些实施例中，终端可以根据网络的配置，确定是否自主执行GNSS测量。在一实施例中，网络设备可以配置终端是否开启自主测量功能，若开启，则终端可以自主执行GNSS测量，若关闭，则终端可以由网络设备触发GNSS测量。
在一些实施例中，步骤S2120可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S2130中，终端在测量间隙内执行GNSS测量。
在一些实施例中，终端响应第二信息，确定测量间隙的配置。然后，终端根据测量间隙的配置，在测量间隙内执行GNSS测量。
在一些实施例中，测量间隙的配置可以包括测量间隙的起始位置、测量间隙的长度等。在一实施例中，术语“测量间隙的长度”可以与“测量间隙的时间长度”、“测量间隙的时长”、“测量间隙持续时间”、“测量间隙持续时长”等相互替换。
在一些实施例中，测量间隙可以是周期性的，也可以非周期性的。
在一些实施例中，测量间隙可以是预定义或者预配置的，也可以是网络设备为终端配置的。示例性的，“预定义或预配置的”可以理解为协议预先规定的、终端与网络设备预先协商配置的。示例性的，“网络设备为终端配置的”可以理解为网络设备基于终端向网络设备发送的时间信息确定的。在一实施例中，终端发送的时间信息可以包括GNSS定位持续信息、GNSS可用时间信息等至少之一。其中，GNSS定位持续信息用于指示GNSS定位所需时间，GNSS可用时间信息用于指示GNSS有效期。需要说明的是，上述终端发送的时间信息是终端最新向网络设备发送的，或者是终端在上一次GNSS测量结束后发送的。示例性的，测量间隙的长度大于或者等于终端最新报告的GNSS定位所需时间。
在一些实施例中，测量间隙的长度可以是网络设备预先配置给终端的，也可以是终端基于自身实现确定的。示例性的，终端可以基于终端上报的时间信息确定测量间隙的长度。在一些实施例中，测量间隙的起始位置也可以是预定义或者预配置的。示例性的，测量间隙的起始位置可以为GNSS有效期结束位置，也可以是接收到网络设备发送的触发指令后间隔N个时间单位的时域位置，还可以为终端反馈HARQ信息的位置后间隔N个时间单位的时域位置，这里，N为预定义或预配置的。或者，测量间隙的开始位置可以基于当前GNSS有效期，进行一定的延迟或无延迟。
在一些实施例中，上述“时间单位”可以理解为“帧”、“子帧”、“时隙”、“子时隙”、“符号”等。
在一些实施例中，终端在成功执行GNSS测量之前，不需要在测量间隙内发送或接收任何信道/信号。
在一些实施例中，终端在成功执行GNSS测量之后，每次向网络设备发送剩余GNSS有效期(remaining GNSS validity duration)，以向网络设备指示连接态下的GNSS测量执行成功。
在一些实施例中，终端可以在测量间隙内的GNSS测量执行成功的情况下，执行步骤S2140。
在步骤S2140中，终端发送第一随机接入序列。
在一些实施例中，网络设备接收第一随机接入序列。
在一些实施例中，终端在GNSS测量执行成功后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功。
在一些实施例中，终端根据随机接入序列与GNSS有效期的对应关系，发送第一随机接入序列。
在一些实施例中，终端根据自身发送给网络设备的时间信息，如GNSS可用时间，查询随机接入序列与GNSS有效期的对应关系，确定当前的GNSS有效期对应的第一随机接入序列。这里，当前的GNSS有效期可以理解为终端正在使用的GNSS有效期，或者终端上一次向网络设备发送的GNSS可用时间信息所指示的GNSS有效期。
在一些实施例中，随机接入序列与GNSS有效期的对应关系包含有至少一个随机接入序列。这些随机接入序列中的至少一部分与GNSS测量执行成功关联。那么，终端查询随机接入序列与GNSS有效期的对应关系，从上述对应关系中与GNSS测量执行成功关联的随机接入序列中确定当前的GNSS有效期对应的第一随机接入序列。
在一些实施例中，在上述对应关系中，一个GNSS有效期可以与一个随机前导序列对应，一个GNSS 有效期可以与多个随机序列对应。
示例性的，GNSS有效期＝T1对应于preamble A，GNSS有效期＝T2对应于preamble B，GNSS有效期＝T3对应于preamble C。其中，preamble A、preamble B和preamble C均用于指示GNSS测量执行成功。那么，终端可以根据自身的GNSS有效期＝T2，确定第一随机接入序列为preamble B。
示例性的，GNSS有效期＝T1对应于preamble A，GNSS有效期＝T2对应于preamble B，GNSS有效期＝T2对应于preamble C。其中，preamble A和preamble C用于指示GNSS测量执行成功。那么，在一些情况下，终端可以根据自身的GNSS有效期＝T1，确定第一随机接入序列为preamble A。在另一些情况下，终端可以根据自身的GNSS有效期＝T2，确定可用的随机接入序列为preamble B和preamble C。然后，终端可以根据自身实现从preamble B和preamble C中选择合适的一个，即preamble B或preamble C作为第一随机接入序列。
在一些实施例中，终端在获得随机接入配置与GNSS有效期的对应关系的情况下，还可以根据自身发送给网络设备的时间信息，如GNSS可用时间，查询随机接入配置与GNSS有效期的对应关系，确定当前的GNSS有效期对应的随机接入配置，该随机接入配置可以指示第一随机接入序列以及第一RO。此时，终端在第一RO上发送第一随机接入序列。
在一些实施例中，第一随机接入序列还可以用于触发基于竞争的随机接入过程。在一实施例中，网络设备根据随机接入序列与GNSS有效期的对应关系，向终端指示至少一个随机接入序列(可以称为基于竞争的随机接入序列)。那么，终端在测量间隙内成功执行GNSS测量后，根据随机接入序列与GNSS有效期的对应关系，确定第一随机接入序列，并向网络设备发送。
示例性的，第一随机接入序列可以承载于随机接入过程中的消息1(message 1，msg1)中发送。在一实施例中，随机接入过程可以为4步随机接入(4-step RACH)、2步随机接入(2-step RACH)，对此本公开实施例对此不做具体限定。
在一些实施例中，终端通过PRACH信令发送第一随机接入序列。
在一些实施例中，终端还可以发送GNSS定位持续时间信息，以向网络设备指示GNSS定位所需时间(GNSS position fix time duration)。在一实施例中，GNSS定位持续时间信息可以与第一随机接入序列同时发送。在一实施例中，GNSS定位持续时间信息与第一随机接入序列可以携带于同一消息(如msg1)中发送。
在步骤S2150中，网络设备确定终端在测量间隙内成功执行GNSS测量。
在一些实施例中，网络设备在接收到第一随机接入序列之后，根据第一随机接入序列，继续执行随机接入过程。
在步骤S2160中，网络设备确定第一随机接入序列对应的GNSS有效期。
在一些实施例中，网络设备根据随机接入序列与GNSS有效期的对应关系，确定第一随机接入序列对应的GNSS有效期。
在一些实施例中，网络设备侧与终端侧维护有相同的随机接入序列与GNSS有效期的对应关系，那么，网络设备在接收到第一随机接入序列之后，查询随机接入序列与GNSS有效期的对应关系，确定第一随机接入序列对应的GNSS有效期，即终端的GNSS有效期。
本公开实施例所涉及的通信方法可以包括步骤S2110至步骤S2160中的至少一者。例如，步骤S2130和步骤S2140可以作为独立实施例来实施。例如，步骤S2120至步骤S2140可以作为独立实施例来实施。例如，步骤S2110至步骤S2140可以作为独立实施例来实施。例如，步骤S2130至步骤S2150的组合可以作为独立实施例来实施。例如，步骤S2130至步骤S2160的结合可以作为独立实施例来实施。例如，步骤S2120至步骤S2150的结合可以作为独立实施例来实施。例如，步骤S2110至步骤S2150的组合可以作为独立实施例来实施。例如，步骤S2120至步骤S2160的组合可以作为独立实施例来实施。例如，步骤S2110至步骤S2160的组合可以作为独立实施例来实施。需要说明的是，步骤S2110至步骤S2160中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S2110至步骤S2160中的至少两个可以交换顺序或同步执行。例如，步骤S2110和步骤S2120可以交换顺序或同时执行。步骤S2110和步骤S2120至步骤S2130可以交换顺序或同时执行。例如，步骤S2150和步骤S2160可以交换顺序或同时执行。
在一些实施例中，步骤S2110、步骤S2120和步骤S2160是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2120和步骤S2160是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2110和步骤S2120是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2110和步骤S2160是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2110、步骤S2120和步骤S2160中之一是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在上述实施例中，终端通过向网络设备发送第一随机接入序列，来指示自身在测量间隙内GNSS测量的执行情况，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
图2B是根据本公开实施例示出的通信方法的第二种流程示意图。本公开实施例涉及通信方法，用于通信系统100。如图2B所示，本公开实施例的通信方法包括步骤S2210至步骤S2260。
在步骤S2210中，网络设备发送第二信息。
步骤S2210的可选实现方式可以参见图2A的步骤S2120的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S2220中，终端在测量间隙内执行GNSS测量。
步骤S2220的可选实现方式可以参见图2A的步骤S2130的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端可以在测量间隙内的GNSS测量执行成功的情况下，执行步骤S2230。
在步骤S2230中，终端发送第一随机接入序列。
在一些实施例中，网络设备接收第一随机接入序列。
在一些实施例中，终端在GNSS测量执行成功后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功。
在一些实施例中，第一随机接入序列还可以用于触发基于非竞争的随机接入过程。在一实施例中，网络设备通过随机接入前导分配(RA preamble assignment)向终端指示第一随机接入序列。那么，终端在测量间隙内成功执行GNSS测量后，向网络设备发送第一随机接入序列。在一实施例中，第一随机接入序列可以为专用随机接入前导码。
示例性的，第一随机接入序列可以承载于随机接入过程中的msg1中发送。在一实施例中，随机接入过程可以为4步随机接入(4-step RACH)、2步随机接入(2-step RACH)，对此本公开实施例对此不做具体限定。
在一些实施例中，终端还可以发送GNSS定位持续时间信息，以向网络设备指示GNSS定位所需时间。在一实施例中，GNSS定位持续时间信息可以与第一随机接入序列同时发送。在一实施例中，GNSS定位持续时间信息与第一随机接入序列可以携带于同一消息(如msg1)中发送。
在步骤S2240中，网络设备确定终端在测量间隙内成功执行GNSS测量。
在一些实施例中，网络设备在接收到第一随机接入序列之后，根据第一随机接入序列，继续执行随机接入过程。
在步骤S2250中，网络设备发送第三信息。
在一些实施例中，终端接收第三信息。
在一些实施例中，第三信息用于指示终端在第一上行资源上发送GNSS有效期。
在一些实施例中，第三信息的名称不做限定，其例如是“响应信息”、“随机接入响应信息”、“触发上报信息”等。
在一些实施例中，第三信息可以承载于随机接入过程中的消息2(message 2，msg2)中发送。在一实施例中，随机接入过程可以为4步随机接入(4-step RACH)、2步随机接入(2-step RACH)，对此本公开实施例对此不做具体限定。
在一些实施例中，第一上行资源为由上行授权(uplink grant)调度。第一上行资源用于终端发送GNSS有效期。
在一些实施例中，网络设备确定终端在测量间隙内成功执行GNSS测量之后，发送第三信息。
在步骤S2260中，终端发送第一时间信息。
在一些实施例中，网络设备接收第一时间信息，第一时间信息用于指示终端的GNSS有效期。
在一些实施例中，第一信息可以为GNSS可用时间信息。
在一些实施例中，终端在第一上行资源上发送第一时间信息。
在一些实施例中，第一上行资源可以承载于随机接入过程中的消息3(message 3，msg3)中发送。
在一些实施例中，终端在GNSS测量之后，向网络设备发送GNSS有效期。在一实施例中，终端可以每测量一次，便发送一次GNSS有效期。在一实施例中，终端还可以在GNSS有效期的时间长度发生改变时向网络设备发送新的GNSS有效期。
在一些实施例中，终端在发送GNSS可用时间信息的同时还可以发送其他信息，如GNSS定位持续信息，以用于以向网络设备指示GNSS定位所需时间。示例性的，GNSS可用时间信息与GNSS定位持续信息可以携带在同一消息中发送，也可以携带在不同消息中同时发送。
在一些实施例中，终端可以分别发送GNSS可用时间信息和GNSS定位持续信息。此时，GNSS定位持续信息可以携带在，如RRC连接重建完成消息(RRCConnectionReestablishmentComplete或RRCConnectionReestablishmentComplete-NB)、切换场景下的RRC连接重配置完成消息(RCConnectionReconfigurationComplete for HO case)中发送。
本公开实施例所涉及的通信方法可以包括步骤S2210至步骤S2240中的至少一者。例如，步骤S2220和步骤S2230可以作为独立实施例来实施。例如，步骤S2220至步骤S2240的组合可以作为独立实施例来实施。例如，步骤S2210至步骤S2230的结合可以作为独立实施例来实施。例如，步骤S2210至步骤S2240的结合可以作为独立实施例来实施。需要说明的是，步骤S2210至步骤S2240中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S2210是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2240是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在上述实施例中，终端通过向网络设备发送第一随机接入序列，来指示自身在测量间隙内GNSS测量的执行情况，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
图2C是根据本公开实施例示出的通信方法的第三种流程示意图。本公开实施例涉及通信方法，用于通信系统100。如图2C所示，本公开实施例的通信方法包括步骤S2310至步骤S2370。
在步骤S2310中，网络设备发送第一配置信息。
在一些实施例中，终端接收第一配置信息。
在一些实施例中，第一配置信息用于指示至少一个第二随机接入序列。在一实施例中，第二随机接入序列与GNSS测量执行成功关联。第二随机接入序列用于指示GNSS测量执行成功。
在一些实施例中，网络设备还可以第二配置信息。
在一些实施例中，终端接收第二配置信息。
在一些实施例中，第二配置信息用于指示至少一个第四随机接入序列。
在一些实施例中，第四随机接入序列与随机接入过程关联。第四随机接入序列可以用于触发随机接入过程。
在一些实施例中，终端可以根据预定义或者预配置，获得至少一个第四随机接入序列。
在一些实施例中，至少一个第二随机接入序列和至少一个第四随机接入序列可以包含在不同的信息中同时发送，可以包含在同一信息(如随机接入配置)中发送。
在一些实施例中，步骤S2310可以被省略，此时，终端可以根据预定义或者预配置，获得至少一个第二随机接入序列。
在步骤S2320中，终端在测量间隙内执行GNSS测量。
步骤S2320的可选实现方式可以参见图2A的步骤S2130的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S2330中，终端确定第一随机接入序列。
在一些实施例中，终端在测量间隙内成功执行GNSS测量后，可以从至少一个第二随机接入序列中确定第一随机接入序列。
在一些实施例中，终端从至少一个第二随机接入序列中选择一个第二随机接入序列确定为第一随机接 入序列。在一实施例中，终端可以从至少一个第二随机接入序列中随机选择一个第二随机接入序列作为第一随机接入序列。在一实施例中，终端可以从至少一个第二随机接入序列中任选一个第二随机接入序列作为第一随机接入序列。在一实施例中，终端可以根据自身实现，如硬件能力，可以从至少一个第二随机接入序列中选择合适的第二随机接入序列作为第一随机接入序列。
在一些实施例中，在不需要向网络设备指示GNSS测量的执行情况下，终端可以从至少一个第四随机接入序列中选择一个，发起随机接入过程。
在步骤S2340中，终端发送第一随机接入序列。
步骤S2340的可选实现方式可以参见图2A的步骤S2140的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S2350中，网络设备确定第一随机接入序列与GNSS执行成功关联。
在一些实施例中，网络设备在接收第一随机接入序列之后，确定第一随机接入序列为至少一个第二随机接入序列之一，进而确定终端在测量间隙内成功执行GNSS测量。
在一些实施例中，网络设备在接收到第一随机接入序列之后，根据第一随机接入序列，继续执行随机接入过程。
在步骤S2360中，网络设备发送第三信息。
在一些实施例中，终端接收第三信息。
在一些实施例中，第三信息用于指示终端在第一上行资源上发送GNSS有效期。
在一些实施例中，第三信息的名称不做限定，其例如是“响应信息”、“随机接入响应信息”、“触发上报信息”等。
在一些实施例中，第三信息可以承载于随机接入过程中的消息2(message 2，msg2)中发送。在一实施例中，随机接入过程可以为4步随机接入(4-step RACH)、2步随机接入(2-step RACH)，对此本公开实施例对此不做具体限定。
在一些实施例中，第一上行资源为由上行授权(uplink grant)调度。第一上行资源用于终端发送GNSS有效期。
在一些实施例中，网络设备确定终端在测量间隙内成功执行GNSS测量之后，发送第三信息。
在步骤S2370中，终端发送第一时间信息。
在一些实施例中，网络设备接收第一时间信息，第一时间信息用于指示终端的GNSS有效期。
在一些实施例中，终端在第一上行资源上发送第一时间信息，以指示GNSS可用时间信息。
在一些实施例中，第一上行资源可以承载于随机接入过程中的消息3(message 3，msg3)中发送。
本公开实施例所涉及的通信方法可以包括步骤S2310至步骤S2370中的至少一者。例如，步骤S2320至步骤S2340可以作为独立实施例来实施。例如，步骤S2310至步骤S2340的组合可以作为独立实施例来实施。例如，步骤S2320至步骤S2350的结合可以作为独立实施例来实施。例如，步骤S2320至步骤S2370的结合可以作为独立实施例来实施。例如，步骤S2310至步骤S2370的结合可以作为独立实施例来实施。需要说明的是，步骤S2310至步骤S2370中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S2310、步骤S2350、步骤S2360至步骤S2370是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2310、步骤S2350是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2350、步骤S2360至步骤S2370是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2360至步骤S2370是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2310是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在上述实施例中，终端通过向网络设备发送第一随机接入序列，来指示自身在测量间隙内GNSS测量的执行情况，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
图2D是根据本公开实施例示出的通信方法的第四种流程示意图。本公开实施例涉及通信方法，用于通信系统100。如图2D所示，本公开实施例的通信方法包括步骤S2410至步骤S2440。
在步骤S2410中，网络设备发送第一信息。
步骤S2410的可选实现方式可以参见图2A的步骤S2110的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，第一信息用于指示随机接入序列与GNSS有效期的对应关系。
在一些实施例中，随机接入序列与GNSS有效期的对应关系包含有至少一个随机接入序列(即至少一个第三随机接入序列)。这些随机接入序列中的至少一部分与GNSS测量执行失败关联。
在一些实施例中，步骤S2410可以被省略，此时，随机接入序列与GNSS有效期的对应关系或者随机接入配置与GNSS有效期的对应关系，可以是预定义或者预配置的。
在步骤S2420中，网络设备发送第二信息。
步骤S2420的可选实现方式可以参见图2A的步骤S2120的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，步骤S2420可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S2430中，终端在测量间隙内执行GNSS测量。
步骤S2430的可选实现方式可以参见图2A的步骤S2130的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端可以在测量间隙内的GNSS测量执行失败的情况下，执行步骤S2440。
在步骤S2440中，终端发送第一随机接入序列。
在一些实施例中，网络设备接收第一随机接入序列。
在一些实施例中，终端在GNSS测量执行失败后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行失败。
在一些实施例中，终端根据随机接入序列与GNSS有效期的对应关系，发送第一随机接入序列。
在一些实施例中，终端根据自身发送给网络设备的时间信息，如GNSS可用时间，查询随机接入序列与GNSS有效期的对应关系，确定当前的GNSS有效期对应的第一随机接入序列。
在一些实施例中，随机接入序列与GNSS有效期的对应关系包含有至少一个随机接入序列。这些随机接入序列中的至少一部分与GNSS测量执行失败关联。那么，终端查询随机接入序列与GNSS有效期的对应关系，从对应关系中与GNSS测量执行失败关联的随机接入序列中确定当前的GNSS有效期对应的第一随机接入序列。
示例性的，GNSS有效期＝T1对应于preamble A，GNSS有效期＝T2对应于preamble B，GNSS有效期＝T3对应于preamble C。其中，preamble A、preamble B和preamble C均用于指示GNSS测量执行失败。那么，终端可以根据自身的GNSS有效期＝T1，确定第一随机接入序列为preamble A。
示例性的，GNSS有效期＝T1对应于preamble A，GNSS有效期＝T3对应于preamble B，GNSS有效期＝T2对应于preamble C。其中，preamble A和preamble B用于指示GNSS测量执行失败。那么，终端可以根据自身的GNSS有效期＝T3，确定第一随机接入序列为preamble A。
在一些实施例中，第一随机接入序列可以承载于随机接入过程中的消息1(message 1，msg1)中发送。
在一些实施例中，终端通过PRACH信令发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行失败后，还可以确定当前的GNSS有效期未过期，此时，终端保持处于连接状态，直至当前的GNSS有效期过期。然后，终端进入空闲状态或确定发生RLF。
在一些实施例中，终端在GNSS测量执行失败后，还可以确定当前的GNSS有效期已过期，此时，终端进入空闲状态或确定发生RLF。
在一些实施例中，终端确定发生RLF也可以描述为终端进入RLF状态。
在一些实施例中，终端未能在测量间隙内重新获取GNSS定位，可以在测量间隙之后的GNSS测量定时器的时长内保持处于连接状态，并利用GNSS测量定时器的时长内重新获取GNSS定位。在一些实施例中，当终端在GNSS测量定时器的时长内未能重新获取GNSS定位时，终端在GNSS测量定时器结束之后进入IDLE模式或者确定发生RLF。在一实施例中，当终端在GNSS测量间隙之后没有GNSS测量定时器时，终端在测量间隙结束之后进入IDLE模式或者确定发生RLF。
在步骤S2450中，网络设备确定终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，图2A的实施例可以与图2D的实施例进行结合。示例性的，步骤S2110可以与步骤S2410进行组合。在一实施例中，随机接入序列与GNSS有效期的对应关系包含有至少一个随机接入序列。这些随机接入序列中的一部分与GNSS测量执行成功关联，另一部分与GNSS测量执行失败关联。
在一些实施例中，在步骤S2130之后，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S2140。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S2440至步骤S2450。
本公开实施例所涉及的通信方法可以包括步骤S2410至步骤S2450中的至少一者。例如，步骤S2430和步骤S2440可以作为独立实施例来实施。例如，步骤S2420至步骤S2440可以作为独立实施例来实施。例如，步骤S2410至步骤S2440可以作为独立实施例来实施。例如，步骤S2430至步骤S2450的组合可以作为独立实施例来实施。例如，步骤S2420至步骤S2450的结合可以作为独立实施例来实施。例如，步骤S2410至步骤S2450的组合可以作为独立实施例来实施。需要说明的是，步骤S2410至步骤S2450中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S2410至步骤S2450中的至少两个可以交换顺序或同步执行。例如，步骤S2410和步骤S2420可以交换顺序或同时执行。步骤S2410和步骤S2420至步骤S2430可以交换顺序或同时执行。
在一些实施例中，步骤S2410和步骤S2420是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2410或步骤S2420是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在上述实施例中，终端通过向网络设备发送第一随机接入序列，来指示自身在测量间隙内GNSS测量的执行情况，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
图2E是根据本公开实施例示出的通信方法的第五种流程示意图。本公开实施例涉及通信方法，用于通信系统100。如图2E所示，本公开实施例的通信方法包括步骤S2510至步骤S2540。
在步骤S2510中，网络设备发送第二信息。
步骤S2510的可选实现方式可以参见图2A的步骤S2120的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S2520中，终端在测量间隙内执行GNSS测量。
步骤S2520的可选实现方式可以参见图2A的步骤S2130的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端可以在GNSS测量执行失败的情况下，执行步骤S2530。
在步骤S2530中，终端发送第一随机接入序列。
在一些实施例中，网络设备接收第一随机接入序列。
在一些实施例中，终端在GNSS测量执行失败后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行失败。
在一些实施例中，第一随机接入序列可以承载于随机接入过程中的msg1中发送。
在一些实施例中，终端通过PRACH信令发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行失败后，还可以确定当前的GNSS有效期未过期，此时，终端保持处于连接状态，直至当前的GNSS有效期过期。然后，终端进入空闲状态或确定发生RLF。
在一些实施例中，终端在GNSS测量执行失败后，还可以确定当前的GNSS有效期已过期，此时，终端进入空闲状态或确定发生RLF。
在步骤S2540中，网络设备确定终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，图2B的实施例可以与图2E的实施例进行结合。示例性的，在步骤S2220之后，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S2230。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S2530至步骤S2540。
本公开实施例所涉及的通信方法可以包括步骤S2510至步骤S2540中的至少一者。例如，步骤S2520和步骤S2530可以作为独立实施例来实施。例如，步骤S2520至步骤S2540的组合可以作为独立实施例来实施。例如，步骤S2510至步骤S2530的结合可以作为独立实施例来实施。例如，步骤S2510至步骤S2540 的结合可以作为独立实施例来实施。需要说明的是，步骤S2510至步骤S2540中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S2510是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在上述实施例中，终端通过向网络设备发送第一随机接入序列，来指示自身在测量间隙内GNSS测量的执行情况，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
图2F是根据本公开实施例示出的通信方法的第六种流程示意图。本公开实施例涉及通信方法，用于通信系统100。如图2F所示，本公开实施例的通信方法包括步骤S2610至步骤S2640。
在步骤S2610中，网络设备发送第三配置信息。
在一些实施例中，终端接收第三配置信息。
在一些实施例中，第三配置信息用于指示至少一个第三随机接入序列。
在一些实施例中，第三随机接入序列与GNSS测量执行失败关联。第三随机接入序列用于指示GNSS测量执行失败。
在一些实施例中，步骤S2610可以被省略，此时，终端可以根据预定义或者预配置，获得至少一个第三随机接入序列。
在步骤S2620中，终端在测量间隙内执行GNSS测量。
步骤S2620的可选实现方式可以参见图2A的步骤S2130的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，在步骤S2620之前，终端接收网络设备发送的第二信息。那么，终端响应第二信息，在测量间隙内执行GNSS测量。
在一些实施例中，终端自主在测量间隙内执行GNSS测量。
在一些实施例中，终端可以在GNSS测量执行失败的情况下，执行步骤S2630。
在步骤S2630中，终端确定第一随机接入序列。
在一些实施例中，终端在测量间隙内未成功执行GNSS测量后，可以从至少一个第三随机接入序列中确定第一随机接入序列。
在一些实施例中，终端从至少一个第三随机接入序列中选择一个第三随机接入序列确定为第一随机接入序列。在一实施例中，终端可以从至少一个第三随机接入序列中随机选择一个第三随机接入序列作为第一随机接入序列。在一实施例中，终端可以从至少一个第三随机接入序列中任选一个第三随机接入序列作为第一随机接入序列。在一实施例中，终端可以根据自身实现，如硬件能力，可以从至少一个第三随机接入序列中选择合适的第三随机接入序列作为第一随机接入序列。
在步骤S2640中，终端发送第一随机接入序列。
步骤S2640的可选实现方式可以参见图2E的步骤S2530中的可选方式、以及图2E所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S2650中，网络设备确定第一随机接入序列与GNSS执行失败关联。
在一些实施例中，网络设备在接收第一随机接入序列之后，确定第一随机接入序列为至少一个第三随机接入序列之一，进而确定终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，图2C的实施例可以与图2F的实施例进行结合。示例性的，在步骤S2320之后，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S2330至步骤S2370。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S2630至步骤S2650。
在一些实施例中，终端可以获得至少一个第二随机接入序列和至少一个第三随机接入序列。终端在执行步骤S2130或步骤S2630之后，可以根据GNSS测量的执行结果，从选择第二随机接入序列或第三随机接入序列作为第一随机接入序列。那么，网络设备在接收到第一随机接入序列之后，根据第一随机接入序列是第二随机接入序列还是第三随机接入序列，确定终端在测量间隙内是否成功执行GNSS测量。
本公开实施例所涉及的通信方法可以包括步骤S2610至步骤S2650中的至少一者。例如，步骤S2620至步骤S2640可以作为独立实施例来实施。例如，步骤S2610至步骤S2640的组合可以作为独立实施例来实施。例如，步骤S2620至步骤S2650的结合可以作为独立实施例来实施。需要说明的是，步骤S2610至步骤S2650中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S2610和步骤S2650是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S2650是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省 略或替代。
在一些实施例中，步骤S2610是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在上述实施例中，终端通过向网络设备发送第一随机接入序列，来指示自身在测量间隙内GNSS测量的执行情况，如此，对应终端执行GNSS测量的结果，终端和网络设备能够达成一致，避免出现终端和网络设备之间信息不对称的情况。
在一些实施例中，信息等的名称不限定于实施例中所记载的名称，“信息(information)”、“消息(message)”、“信号(signal)”、“信令(signaling)”、“报告(report)”、“配置(configuration)”、“指示(indication)”、“指令(instruction)”、“命令(command)”、“信道”、“参数(parameter)”、“域”、“字段”、“符号(symbol)”、“码元(symbol)”、“码本(codebook)”、“码字(codeword)”、“码点(codepoint)”、“比特(bit)”、“数据(data)”、“程序(program)”、“码片(chip)”等术语可以相互替换。
在一些实施例中，“上行”、“上行链路”、“物理上行链路”等术语可以相互替换，“下行”、“下行链路”、“物理下行链路”等术语可以相互替换，“侧行(side)”、“侧行链路(sidelink)”、“侧行通信”、“侧行链路通信”、“直连”、“直连链路”、“直连通信”、“直连链路通信”等术语可以相互替换。
在一些实施例中，“下行链路控制信息(downlink control information，DCI)”、“下行链路(downlink，DL)分配(assignment)”、“DL DCI”、“上行链路(uplink，UL)许可(grant)”、“UL DCI”等术语可以相互替换。
在一些实施例中，“物理下行链路共享信道(physical downlink shared channel，PDSCH)”、“DL数据”等术语可以相互替换，“物理上行链路共享信道(physical uplink shared channel，PUSCH)”、“UL数据”等术语可以相互替换。
在一些实施例中，“无线(radio)”、“无线(wireless)”、“无线接入网(radio access network，RAN)”、“接入网(access network，AN)”、“基于RAN的(RAN-based)”等术语可以相互替换。
在一些实施例中，“时刻”、“时间点”、“时间”、“时间位置”等术语可以相互替换，“时长”、“时段”、“时间窗口”、“窗口”、“时间”等术语可以相互替换。
在一些实施例中，无线接入方案(wireless access scheme)、波形(waveform)等术语可以相互替换。
在一些实施例中，“帧(frame)”、“无线帧(radio frame)”、“子帧(subframe)”、“时隙(slot)”、“子时隙(sub-slot)”、“迷你时隙(mini-slot)”、“符号(symbol)”、“码元(symbol)”、“发送时间间隔(transmission time interval，TTI)”等术语可以相互替换。
在一些实施例中，“获取”、“获得”、“得到”、“接收”、“传输”、“双向传输”、“发送和/或接收”可以相互替换，其可以解释为从其他主体接收，从协议中获取，从高层获取，自身处理得到、自主实现等多种含义。
在一些实施例中，“发送”、“发射”、“上报”、“下发”、“传输”、“双向传输”、“发送和/或接收”等术语可以相互替换。
在一些实施例中，“特定(certain)”、“预定(preseted)”、“预设”、“设定”、“指示(indicated)”、“某一”、“任意”、“第一”等术语可以相互替换，“特定A”、“预定A”、“预设A”、“设定A”、“指示A”、“某一A”、“任意A”、“第一A”可以解释为在协议等中预先规定的A，也可以解释为通过设定、配置、或指示等得到的A，也可以解释为特定A、某一A、任意A、或第一A等，但不限于此。
图3A是根据本公开实施例示出的终端侧执行通信方法的第一种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的终端101。如图3A所示，本公开实施例的通信方法包括步骤S3110至步骤S3140。
在步骤S3110中，获得随机接入序列与GNSS有效期的对应关系。
步骤S3110的可选实现方式可以参见图2A的步骤S2110中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第一信息，第一信息用于指示随机接入序列与GNSS有效期的对应关系。
在一些实施例中，终端获得预定义或者预配置的随机接入序列与GNSS有效期的对应关系。
在步骤S3120中，获得第二信息。
步骤S3120的可选实现方式可以参见图2A的步骤S2120中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第二信息。
在一些实施例中，终端接收由高层发送的第二信息。
在一些实施例中，步骤S3120可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S3130中，在测量间隙内执行GNSS测量。
步骤S3130的可选实现方式可以参见图2A的步骤S2130中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S3140中，发送第一随机接入序列。
步骤S3140的可选实现方式可以参见图2A的步骤S2140中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行成功后，发送第一随机接入序列。
在一些实施例中，终端根据随机接入序列与GNSS有效期的对应关系，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于网络设备确定终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于网络设备根据第一随机接入序列，继续执行随机接入过程。
本公开实施例所涉及的通信方法可以包括步骤S3110至步骤S3140中的至少一者。例如，步骤S3130和步骤S3140可以作为独立实施例来实施。例如，步骤S3120至步骤S3140可以作为独立实施例来实施。例如，步骤S3110至步骤S3140可以作为独立实施例来实施。需要说明的是，步骤S3110至步骤S3140中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S3110至步骤S3140中的至少两个可以交换顺序或同步执行。例如，步骤S3110和步骤S3120可以交换顺序或同时执行。步骤S3110和步骤S3120至步骤S3130可以交换顺序或同时执行。
在一些实施例中，步骤S3110和步骤S3120是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3110是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3120是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图3B是根据本公开实施例示出的终端侧执行通信方法的第二种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的终端101。如图3B所示，本公开实施例的通信方法包括步骤S3210至步骤S3250。
在步骤S3210中，获得第二信息。
步骤S3210的可选实现方式可以参见图2B的步骤S2210中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第二信息。
在一些实施例中，终端接收由高层发送的第二信息。
在一些实施例中，步骤S3210可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S3220中，在测量间隙内执行GNSS测量。
步骤S3220的可选实现方式可以参见图2B的步骤S2220的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端可以在测量间隙内的GNSS测量执行成功的情况下，执行步骤S3230。
在步骤S3230中，发送第一随机接入序列。
步骤S3230的可选实现方式可以参见图2B的步骤S2230中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行成功后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于网络设备确定终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于网络设备根据第一随机接入序列，继续执行随机接入过程。
在步骤S3240中，接收第三信息。
步骤S3240的可选实现方式可以参见图2B的步骤S2250中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第三信息。
在步骤S3250中，发送第一时间信息。
步骤S3250的可选实现方式可以参见图2B的步骤S2260中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一时间信息。
本公开实施例所涉及的通信方法可以包括步骤S3210至步骤S3230中的至少一者。例如，步骤S3220和步骤S3230可以作为独立实施例来实施。例如，步骤S3210至步骤S3230的结合可以作为独立实施例来实施。需要说明的是，步骤S3210至步骤S3230中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S3210是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图3C是根据本公开实施例示出的终端侧执行通信方法的第三种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的终端101。如图3C所示，本公开实施例的通信方法包括步骤S3310至步骤S3360。
在步骤S3310中，获得至少一个第二随机接入序列。
步骤S3310的可选实现方式可以参见图2C的步骤S2310中的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的至少一个第二随机接入序列。
在一些实施例中，终端获得预定义或者预配置的至少一个第二随机接入序列。
在一些实施例中，终端接收由网络设备发送的至少一个第四随机接入序列。
在一些实施例中，终端获得预定义或者预配置的至少一个第四随机接入序列。
在步骤S3320中，在测量间隙内执行GNSS测量。
步骤S3320的可选实现方式可以参见图2C的步骤S2320的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S3330中，确定第一随机接入序列。
步骤S3330的可选实现方式可以参见图2C的步骤S2330的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S3340中，发送第一随机接入序列。
步骤S3340的可选实现方式可以参见图2C的步骤S2340的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行成功后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于网络设备确定终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于触发网络设备发送第三信息。
在步骤S3350中，接收第二信息。
步骤S3350的可选实现方式可以参见图2C的步骤S2360的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第二信息。
在步骤S3360中，发送第一时间信息。
步骤S3360的可选实现方式可以参见图2C的步骤S2370的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一时间信息。
在一些实施例中，终端在第一上行资源上向网络设备发送第一时间信息。
本公开实施例所涉及的通信方法可以包括步骤S3310至步骤S3360中的至少一者。例如，步骤S3320至步骤S3340可以作为独立实施例来实施。例如，步骤S3310至步骤S3340的组合可以作为独立实施例来实施。例如，步骤S3320至步骤S3360的结合可以作为独立实施例来实施。例如，步骤S3310至步骤S3360的结合可以作为独立实施例来实施。需要说明的是，步骤S3310至步骤S3360中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S3310、步骤S3360至步骤S3370是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3310是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3360至步骤S3370是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图3D是根据本公开实施例示出的终端侧执行通信方法的第四种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的终端101。如图3D所示，本公开实施例的通信方法包括步骤S3410至步骤S3440。
在步骤S3410中，获得随机接入序列与GNSS有效期的对应关系。
步骤S3410的可选实现方式可以参见图2D的步骤S2410的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的随机接入序列与GNSS有效期的对应关系。
在一些实施例中，终端获得预定义或者预配置的随机接入序列与GNSS有效期的对应关系。
在步骤S3420中，获得第二信息。
步骤S3420的可选实现方式可以参见图2D的步骤S2420中的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第二信息。
在一些实施例中，终端接收由高层发送的第二信息。
在一些实施例中，步骤S3420可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S3430中，在测量间隙内执行GNSS测量。
步骤S3430的可选实现方式可以参见图2D的步骤S2430的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端可以在测量间隙内的GNSS测量执行失败的情况下，执行步骤S3440。
在步骤S3440中，发送第一随机接入序列。
步骤S3440的可选实现方式可以参见图2D的步骤S2440中的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行失败后，发送第一随机接入序列。
在一些实施例中，终端根据随机接入序列与GNSS有效期的对应关系，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行失败。
在一些实施例中，图3A的实施例可以与图3D的实施例进行结合。示例性的，步骤S3110可以与步骤S3410进行组合。在一实施例中，随机接入序列与GNSS有效期的对应关系包含有至少一个随机接入序列。这些随机接入序列中的一部分与GNSS测量执行成功关联，另一部分与GNSS测量执行失败关联。
在一些实施例中，在步骤S3130之后，终端在测量间隙内成功执行GNSS测量的情况下，可以执行步骤S3140。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S3440。
本公开实施例所涉及的通信方法可以包括步骤S3410至步骤S3440中的至少一者。例如，步骤S3430和步骤S3440可以作为独立实施例来实施。例如，步骤S3420至步骤S3440可以作为独立实施例来实施。例如，步骤S3410至步骤S3440可以作为独立实施例来实施。需要说明的是，步骤S3410至步骤S3440中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S3410至步骤S3440中的至少两个可以交换顺序或同步执行。例如，步骤S3410和步骤S3420可以交换顺序或同时执行。步骤S3410和步骤S3420至步骤S3430可以交换顺序或同时执行。
在一些实施例中，步骤S3410和步骤S3420是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S3410或步骤S3420是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图3E是根据本公开实施例示出的终端侧执行通信方法的第五种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的终端101。如图3E所示，本公开实施例的通信方法包括步骤S3510至步骤S3530。
在步骤S3510中，获得第二信息。
步骤S3510的可选实现方式可以参见图2E的步骤S2510的可选方式、以及图2E所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第二信息。
在一些实施例中，终端接收由高层发送的第二信息。
在一些实施例中，步骤S3510可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S3520中，在测量间隙内执行GNSS测量。
步骤S3520的可选实现方式可以参见图2E的步骤S2520的可选方式、以及图2E所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端可以在GNSS测量执行失败的情况下，执行步骤S3530。
在步骤S3530中，发送第一随机接入序列。
步骤S3530的可选实现方式可以参见图2E的步骤S2530中的可选方式、以及图2E所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行失败后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行失败。
在一些实施例中，图3B的实施例可以与图3E的实施例进行结合。示例性的，在步骤S3220之后，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S3230。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S3530。
本公开实施例所涉及的通信方法可以包括步骤S3510至步骤S3530中的至少一者。例如，步骤S3520和步骤S3530可以作为独立实施例来实施。例如，步骤S3510至步骤S3530的结合可以作为独立实施例来实施。需要说明的是，步骤S3510至步骤S3530中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S3510是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图3F是根据本公开实施例示出的终端侧执行通信方法的第六种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的终端101。如图3F所示，本公开实施例的通信方法包括步骤S3610至步骤S3640。
在步骤S3610中，获得至少一个第三随机接入序列。
步骤S3610的可选实现方式可以参见图2F的步骤S2610的可选方式、以及图2F所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端接收由网络设备发送的第三配置信息，第三配置信息用于指示至少一个第三随机接入序列。
在一些实施例中，终端获得预定义或者预配置的至少一个第三随机接入序列。
在步骤S3620中，在测量间隙内执行GNSS测量。
步骤S3620的可选实现方式可以参见图2F的步骤S2620的可选方式、以及图2F所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端可以在GNSS测量执行失败的情况下，执行步骤S3630。
在步骤S3630中，确定第一随机接入序列。
步骤S3630的可选实现方式可以参见图2F的步骤S2630的可选方式、以及图2F所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S3640中，发送第一随机接入序列。
步骤S3640的可选实现方式可以参见图2F的步骤S2640中的可选方式、以及图2F所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一随机接入序列。
在一些实施例中，终端在GNSS测量执行失败后，发送第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行失败。
在一些实施例中，网络设备在接收第一随机接入序列之后，确定第一随机接入序列为至少一个第三随机接入序列之一，进而确定终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，图3C的实施例可以与图3F的实施例进行结合。示例性的，在步骤S3320之后，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S3330至步骤S3340。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S3630至步骤S3640。
在一些实施例中，终端可以获得至少一个第二随机接入序列和至少一个第三随机接入序列。终端在执行步骤S3320或步骤S3620之后，可以根据GNSS测量的执行结果，从选择第二随机接入序列或第三随机接入序列作为第一随机接入序列。那么，网络设备在接收到第一随机接入序列之后，根据第一随机接入序列是第二随机接入序列还是第三随机接入序列，确定终端在测量间隙内是否成功执行GNSS测量。
本公开实施例所涉及的通信方法可以包括步骤S3610至步骤S3640中的至少一者。例如，步骤S3620至步骤S3640可以作为独立实施例来实施。例如，步骤S3610至步骤S3640的组合可以作为独立实施例来实施。需要说明的是，步骤S3610至步骤S3640中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S3610是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图4A是根据本公开实施例示出的网络设备侧通信方法的第一种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的网络设备102，如接入网设备。如图4A所示，本公开实施例的通信方法包括步骤S4110至步骤S4150。
在步骤S4110中，发送第一信息。
步骤S4110的可选实现方式可以参见图2A的步骤S2110中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送第一信息。第一信息用于指示随机接入序列与GNSS有效期的对应关系。
在一些实施例中，步骤S4110可以被省略，此时，随机接入序列与GNSS有效期的对应关系是预定义或者预配置的。
在步骤S4120中，发送第二信息。
步骤S4120的可选实现方式可以参见图2A的步骤S2120中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送的第二信息。
在一些实施例中，步骤S4120可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在一些实施例中，第二信息用于触发终端在测量间隙内执行GNSS测量。
在步骤S4130中，接收第一随机接入序列。
步骤S4130的可选实现方式可以参见图2A的步骤S2140中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功。
在步骤S4140中，确定终端在测量间隙内成功执行GNSS测量。
步骤S4140的可选实现方式可以参见图2A的步骤S2150中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S4150中，确定第一随机接入序列对应的GNSS有效期。
步骤S4150的可选实现方式可以参见图2A的步骤S2160中的可选方式、以及图2A所涉及的实施例中其他关联部分，此处不再赘述。
本公开实施例所涉及的通信方法可以包括步骤S4110至步骤S4150中的至少一者。例如，步骤S4130和步骤S4140可以作为独立实施例来实施。例如，步骤S4120至步骤S4140可以作为独立实施例来实施。例如，步骤S4110至步骤S4140可以作为独立实施例来实施。例如，步骤S4130至步骤S4150的组合可以作为独立实施例来实施。例如，步骤S4120至步骤S4150的结合可以作为独立实施例来实施。例如，步骤S4110至步骤S4150的组合可以作为独立实施例来实施。需要说明的是，步骤S4110至步骤S4150中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S4110至步骤S4150中的至少两个可以交换顺序或同步执行。例如，步骤S4110和步骤S4120可以交换顺序或同时执行。步骤S4110和步骤S4120至步骤S4130可以交换顺序或同时执行。 例如，步骤S4150和步骤S4160可以交换顺序或同时执行。
在一些实施例中，步骤S4110、步骤S4120和步骤S4150是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4120和步骤S4150是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4110和步骤S4120是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4110和步骤S4150是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4110、步骤S4120和步骤S4150中之一是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图4B是根据本公开实施例示出的网络设备侧执行通信方法的第二种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的网络设备102，如接入网设备。如图4B所示，本公开实施例的通信方法包括步骤S4210至步骤S4230。
在步骤S4210中，发送第二信息。
步骤S4210的可选实现方式可以参见图2B的步骤S2210中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送的第二信息。
在一些实施例中，步骤S4210可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在一些实施例中，第二信息用于触发终端在测量间隙内执行GNSS测量。
在步骤S4220中，接收第一随机接入序列。
步骤S4220的可选实现方式可以参见图2B的步骤S2230中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备接收由终端发送的第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功。
在步骤S4230中，确定终端在测量间隙内成功执行GNSS测量。
步骤S4230的可选实现方式可以参见图2B的步骤S2240中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S4240中，发送第三信息。
步骤S3240的可选实现方式可以参见图2B的步骤S2250中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送第三信息。
在步骤S4250中，接收第一时间信息。
步骤S3250的可选实现方式可以参见图2B的步骤S2260中的可选方式、以及图2B所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备接收由终端发送的第一时间信息。
本公开实施例所涉及的通信方法可以包括步骤S4210至步骤S4230中的至少一者。例如，步骤S4220可以作为独立实施例来实施。例如，步骤S4220和步骤S4230可以作为独立实施例来实施。例如，步骤S4210至步骤S4230的结合可以作为独立实施例来实施。需要说明的是，步骤S4210至步骤S4230中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S4210是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4230是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图4C是根据本公开实施例示出的网络设备侧执行通信方法的第三种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的网络设备102，如接入网设备。如图4C所示，本公开实施例的通信方法包括步骤S4310至步骤S4350。
在步骤S4310中，发送第一配置信息。
步骤S4310的可选实现方式可以参见图2C的步骤S2310中的可选方式、以及图2C所涉及的实施例 中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送第一配置信息，以指示至少一个第二随机接入序列。
在一些实施例中，网络设备还可以发送第二配置信息，以指示至少一个第四随机接入序列。
在一些实施例中，步骤S4310可以被省略，此时，至少一个第二随机接入序列终端是预定义或者预配置的。
在步骤S4320中，接收第一随机接入序列。
步骤S4320的可选实现方式可以参见图2C的步骤S2340的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备接收由终端发送的第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功。
在步骤S4330中，确定第一随机接入序列与GNSS执行成功关联。
步骤S4330的可选实现方式可以参见图2C的步骤S2350的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S4340中，发送第三信息。
步骤S4340的可选实现方式可以参见图2C的步骤S2360的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送第三信息。
在一些实施例中，第三信息用于指示终端在第一上行资源上发送GNSS有效期。
在步骤S4350中，接收第一时间信息。
步骤S4350的可选实现方式可以参见图2C的步骤S2370的可选方式、以及图2C所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备接收由终端发送的第一时间信息。
在一些实施例中，网络设备在第一上行资源上接收由终端发送的第一时间信息。
本公开实施例所涉及的通信方法可以包括步骤S4310至步骤S4350中的至少一者。例如，步骤S4320可以作为独立实施例来实施。例如，步骤S4320至步骤S4330可以作为独立实施例来实施。例如，步骤S4320至步骤S4350的组合可以作为独立实施例来实施。例如，步骤S4310至步骤S4320的结合可以作为独立实施例来实施。例如，步骤S4310至步骤S4330的结合可以作为独立实施例来实施。例如，步骤S4310至步骤S4350的结合可以作为独立实施例来实施。需要说明的是，步骤S4310至步骤S4350中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S4310、步骤S4330、步骤S4340至步骤S4350是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4310、步骤S4330是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4330、步骤S4340至步骤S4350是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4350至步骤S4360是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4310是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图4D是根据本公开实施例示出的网络设备执行通信方法的第四种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的网络设备102，如接入网设备。如图4D所示，本公开实施例的通信方法包括步骤S4410至步骤S4440。
在步骤S4410中，发送随机接入序列与GNSS有效期的对应关系。
步骤S4410的可选实现方式可以参见图2D的步骤S2410的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送随机接入序列与GNSS有效期的对应关系。
在一些实施例中，步骤S4410可以被省略，此时，随机接入序列与GNSS有效期的对应关系或者随机接入配置与GNSS有效期的对应关系，可以是预定义或者预配置的。
在步骤S4420中，发送第二信息。
步骤S4420的可选实现方式可以参见图2D的步骤S2420的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送的第二信息。
在一些实施例中，第二信息用于触发终端在测量间隙内执行GNSS测量。
在一些实施例中，步骤S4420可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S4430中，接收第一随机接入序列。
步骤S4430的可选实现方式可以参见图2D的步骤S2440的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备接收由终端发送的第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行失败。
在步骤S4440中，确定终端在测量间隙内未成功执行GNSS测量。
步骤S4440的可选实现方式可以参见图2D的步骤S2450的可选方式、以及图2D所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，图4A的实施例可以与图4D的实施例进行结合。示例性的，步骤S4110可以与步骤S4410进行组合。在一实施例中，随机接入序列与GNSS有效期的对应关系包含有至少一个随机接入序列。这些随机接入序列中的一部分与GNSS测量执行成功关联，另一部分与GNSS测量执行失败关联。
在一些实施例中，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S4130至步骤S4150。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S4430至步骤S4440。
本公开实施例所涉及的通信方法可以包括步骤S4410至步骤S4440中的至少一者。例如，步骤S4430可以作为独立实施例来实施。例如，步骤S4430和步骤S4440可以作为独立实施例来实施。例如，步骤S4420至步骤S4430可以作为独立实施例来实施。例如，步骤S4410至步骤S4430可以作为独立实施例来实施。例如，步骤S4420至步骤S4440的组合可以作为独立实施例来实施。例如，步骤S4410至步骤S4440的组合可以作为独立实施例来实施。需要说明的是，步骤S4410至步骤S4440中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S4410至步骤S4440中的至少两个可以交换顺序或同步执行。例如，步骤S4410和步骤S4420可以交换顺序或同时执行。步骤S4410和步骤S4420至步骤S4430可以交换顺序或同时执行。
在一些实施例中，步骤S4410、步骤S4420和步骤S4440是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4410和步骤S4420是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4410和步骤S4440是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4420和步骤S4440是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4410、步骤S4420或步骤S4440是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图4E是根据本公开实施例示出的网络设备侧执行通信方法的第五种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的网络设备102，如接入网设备。如图4E所示，本公开实施例的通信方法包括步骤S4510至步骤S4530。
在步骤S4510中，发送第二信息。
步骤S4510的可选实现方式可以参见图2E的步骤S2510的可选方式、以及图2E所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送第二信息。
在一些实施例中，第二信息用于触发终端在测量间隙内执行GNSS测量。
在一些实施例中，步骤S4510可以被省略，此时，终端自主在测量间隙内执行GNSS测量。
在步骤S4520中，接收第一随机接入序列。
步骤S4520的可选实现方式可以参见图2E的步骤S2520的可选方式、以及图2E所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备接收由终端发送的第一随机接入序列。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内未成功执行GNSS测量。
在一些实施例中，第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行失败。
在步骤S4530中，确定终端在测量间隙内未成功执行GNSS测量。
步骤S4530的可选实现方式可以参见图2E的步骤S2540的可选方式、以及图2E所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，图4B的实施例可以与图4E的实施例进行结合。示例性的，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S4220至步骤S4230。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S4520至步骤S4530。
本公开实施例所涉及的通信方法可以包括步骤S4510至步骤S4530中的至少一者。例如，步骤S4520可以作为独立实施例来实施。例如，步骤S4520和步骤S4530可以作为独立实施例来实施。例如，步骤S4510至步骤S4520的组合可以作为独立实施例来实施。例如，步骤S4510至步骤S4530的组合可以作为独立实施例来实施。需要说明的是，步骤S4510至步骤S4530中的一个或多个步骤组成的可能的独立实施例，但不限于此。
在一些实施例中，步骤S4510和步骤S4530是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
在一些实施例中，步骤S4510或步骤S4530是可选的，在不同实施例中可以对这些步骤中的一个或多个步骤进行省略或替代。
图4F是根据本公开实施例示出的网络设备侧执行通信方法的第六种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的网络设备102，如接入网设备。如图4F所示，本公开实施例的通信方法包括步骤S4610至步骤S4640。
在步骤S4610中，发送第三配置信息。
步骤S4610的可选实现方式可以参见图2F的步骤S2610的可选方式、以及图2F所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备向终端发送第三配置信息，以指示至少一个第三随机接入序列。
在一些实施例中，至少一个第三随机接入序列用于终端确定第一随机接入序列。
在一些实施例中，步骤S4610可以被省略，此时，至少一个第三随机接入序列是预定义或者预配置的。
在步骤S4620中，接收第一随机接入序列。
步骤S4620的可选实现方式可以参见图2F的步骤S2640中的可选方式、以及图2F所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S4630中，网络设备确定第一随机接入序列与GNSS执行失败关联。
步骤S4630的可选实现方式可以参见图2F的步骤S2650中的可选方式、以及图2F所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，图4C的实施例可以与图4F的实施例进行结合。示例性的，终端在测量间隙内成功执行GNSS测量的情况下，执行步骤S4320至步骤S4350。终端在测量间隙内未成功执行GNSS测量的情况下，执行步骤S4620至步骤S4630。
在一些实施例中，终端可以获得至少一个第二随机接入序列和至少一个第三随机接入序列。终端在测量间隙内执行GNSS测量之后，可以根据GNSS测量的执行结果，从选择第二随机接入序列或第三随机接入序列作为第一随机接入序列。那么，网络设备在接收到第一随机接入序列之后，根据第一随机接入序列是第二随机接入序列还是第三随机接入序列，确定终端在测量间隙内是否成功执行GNSS测量。
本公开实施例所涉及的通信方法可以包括步骤S4610至步骤S4630中的至少一者。例如，步骤S4620可以作为独立实施例来实施。例如，步骤S4620至步骤S4630可以作为独立实施例来实施。例如，步骤S4610至步骤S4620的组合可以作为独立实施例来实施。例如，步骤S4610至步骤S4630的结合可以作为独立实施例来实施。需要说明的是，步骤S4610至步骤S4630中的一个或多个步骤组成的可能的独立实施例，但不限于此。
图5A是根据本公开实施例示出的终端侧执行通信方法的第七种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的终端101。如图5A所示，本公开实施例的通信方法包括步骤S5110至步骤S5120。
在步骤S5110中，在测量间隙内执行GNSS测量；
步骤S5110的可选实现方式可以参见图2A的步骤S2130、图2B的步骤S2220、图2C的步骤S2320、图2D的步骤S2430、图2E的步骤S2520、图2F的步骤S2620、图3A的步骤S3130、图3B的步骤S3220、图3C的步骤S3320、图3D的步骤S3430、图3E的步骤S3520、图3F的步骤S3620中的可选方式、以及图2A至图2F以及图3A至图3F所涉及的实施例中其他关联部分，此处不再赘述。
在步骤S5120中，发送第一随机接入序列。
步骤S5120的可选实现方式可以参见图2A的步骤S2140、图2B的步骤S2230、图2C的步骤S2340、图2D的步骤S2440、图2E的步骤S2530、图2F的步骤S2640、图3A的步骤S3140、图3B的步骤S3230、图3C的步骤S3340、图3D的步骤S3440、图3E的步骤S3530、图3F的步骤S3640中的可选方式、以及图2A至图2F以及图3A至图3F所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，终端向网络设备发送第一随机接入序列。
在一些实施例中，终端在测量间隙内成功执行GNSS测量后，向网络设备发送第一随机接入序列。此时，第一随机接入序列用于向网络设备指示GNSS测量执行成功，使得网络设备能够根据第一随接入序列，继续执行后续的随机接入过程。
在一些实施例中，终端在测量间隙内未成功执行GNSS测量后，向网络设备发送第一随机接入序列。此时，第一随机接入序列用于向网络设备指示GNSS测量执行失败，使得网络设备能够根据第一随接入序列，确定在测量间隙内未成功执行GNSS测量。
在一些实施例中，上述方法可以包括上述通信网络侧和终端侧的实施例所述的方法，此处不再赘述。
图5B是根据本公开实施例示出的网络设备侧执行通信方法的第七种流程示意图。本公开实施例涉及通信方法，用于通信系统100中的网络设备102，如接入网设备。如图5B所示，本公开实施例的通信方法包括步骤S5210。
在步骤S5210中，接收第一随机接入序列。
步骤S5210的可选实现方式可以参见图2A的步骤S2140、图2B的步骤S2230、图2C的步骤S2340、图2D的步骤S2440、图2E的步骤S2530、图2F的步骤S2640、图4A的步骤S4130、图4B的步骤S4220、图4C的步骤S4320、图4D的步骤S4430、图4E的步骤S4520、图3F的步骤S4620中的可选方式、以及图2A至图2F以及图4A至图4F所涉及的实施例中其他关联部分，此处不再赘述。
在一些实施例中，网络设备接收由终端发送的第一随机接入序列。
在一些实施例中，终端在测量间隙内成功执行GNSS测量后，网络设备接收由终端发送的第一随机接入序列。此时，第一随机接入序列用于向网络设备指示GNSS测量执行成功。如此，网络设备能够根据第一随接入序列，继续执行后续的随机接入过程。
在一些实施例中，终端在测量间隙内未成功执行GNSS测量后，网络设备接收由终端发送的第一随机接入序列。此时，第一随机接入序列用于向网络设备指示GNSS测量执行失败。如此，网络设备能够根据第一随接入序列，确定在测量间隙内未成功执行GNSS测量。
在一些实施例中，上述方法可以包括上述通信网络侧和网络设备侧的实施例所述的方法，此处不再赘述。
图6是根据本公开实施例示出的通信方法的一种交互示意图。如图6所示，本公开实施例涉及通信方法，上述方法包括步骤S610至步骤S640。
在步骤S610中，终端接收网络设备(如基站)的触发指令。其中，上述触发指令可以是MAC CE。
在步骤S620中，终端在measurement gap内执行GNSS测量。
在一些实施例中，终端在配置的measurement gap内执行GNSS测量。
在一些实施例中，在步骤S610之前，终端基于配置信息的指示或是预先定义的方法确定measurement gap的配置。
在一些实施例中，measurement gap的长度可以是预先配置给终端的或者终端基于预先定义(比如基于终端上报的信息确定)的方法确定的。在一实施例中。GNSS measurement gap的起始位置信息也可以是预 先定义或是预先配置的。示例性的。GNSS measurement gap的起始位置是GNSS有效期结束位置、接收到的网络设备发送的触发指令后间隔N个时间单位的时域位置或终端反馈HARQ位置后间隔X的时域位置。
在步骤S630中，终端确定在GNSS measurement gap内是否执行GNSS测量成功；
在步骤S640中，终端向网络设备发送测量成功指示信息或测量失败指示信息。
在一些实施例中，测量成功指示信息进一步的还可以携带GNSS定位所需时间的指示信息。
在一些实施例中，若终端在measurement gap内成功执行GNSS测量，步骤S630可以且不限于包括以下情况中的至少之一：
第一种情况(option1)，终端基于预定义的方式或网络设备配置的方式，获取PRACH序列或PRACH资源与GNSS有效期的对应关系。终端基于该对应关系以及GNSS有效期，确定PRACH序列，并根据该PRACH序列发起随机接入过程。
在一些实施例中，终端接收网络设备发送的系统信息确定PRACH序列与GNSS有效期之间的对应关系。终端基于GNSS测量的结果或自身的硬件能力选择合适的PRACH序列执行上行接入。如此，网络设备在收到该PRACH序列时，根据该PRACH序列值确定终端的GNSS可用时间信息(即第一时间信息)。
在一些实施例中，上述PRACH序列发送的时频资源是网络设备预先配置给目标用户的。此时，终端可以基于非竞争(contention free)的方式发送PRACH序列。
第二种情况(option2)，终端基于预定义的方式或网络设备配置的方式，获取PRACH序列与GNSS测量成功的对应关系。
在一些实施例中，可以将可用的PRACH序列分成两组，一组PRACH序列用于指示GNSS测量成功，另外一组PRACH序列用于正常的随机接入序列。
在一些实施例中，终端基于上述对应关系以及GNSS测量结果，确定PRACH序列，并发起随机接入过程。网络设备在接收到终端发送的PRACH序列，判断终端发送的PRACH序列属于哪一组PRACH序列，从而确定是否调度终端在msg3上发送GNSS可用时间信息，即第一时间信息。
在一些实施例中，网络设备在接收到的PRACH序列为用于指示GNSS测量成功的序列时，确定调度终端在msg3上发送GNSS有效期。此时，终端在msg3中发送第一时间信息。
在一些实施例中，若终端在measurement gap内未成功执行GNSS测量，步骤S630可以且不限于包括以下情况：
终端怕判断其原有的GNSS有效期(即当前使用的GNSS有效期)是否过期。如果没有过期，终端保持在连接态直到原有的GNSS有效期过期，终端进入到空闲状态(idle态)或确定发生RLF。如果已经过期，终端直接进入到空闲状态(idle态)或确定发生RLF。
在一些实施例中，终端基于预定义的方式或网络设备配置的方式，获取PRACH序列与GNSS有效期的对应关系。其中，该对应关系中至少有一个PRACH序列代表GNSS测量失败。那么，终端基于该对应关系，向网络设备发送GNSS测量失败的指示信息。
本公开实施例还提出用于实现以上任一方法的装置，例如，提出一装置，上述装置包括用以实现以上任一方法中终端所执行的各步骤的单元或模块。再如，还提出另一装置，包括用以实现以上任一方法中网络设备(例如接入网设备)所执行的各步骤的单元或模块。
应理解以上装置中各单元或模块的划分仅是一种逻辑功能的划分，在实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。此外，装置中的单元或模块可以以处理器调用软件的形式实现：例如装置包括处理器，处理器与存储器连接，存储器中存储有指令，处理器调用存储器中存储的指令，以实现以上任一方法或实现上述装置各单元或模块的功能，其中处理器例如为通用处理器，例如中央处理单元(central processing unit，ASIC)或微处理器，存储器为装置内的存储器或装置外的存储器。或者，装置中的单元或模块可以以硬件电路的形式实现，可以通过对硬件电路的设计实现部分或全部单元或模块的功能，上述硬件电路可以理解为一个或多个处理器；例如，在一种实现中，上述硬件电路为专用集成电路(application-specific integrated circuit，ASIC)，通过对电路内元件逻辑关系的设计，实现以上部分或全部单元或模块的功能；再如，在另一种实现中，上述硬件电路为可以通过可编程逻辑器件(programmable logic device，PLD)实现，以现场可编程门阵列(field programmable gate array，FPGA)为例，其可以包括大量逻辑门电路，通过配置文件来配置逻辑门电路之间的连接关系，从而实现以上部分或全部单元或模块的功能。以上装置的所有单元或模块可以全部通过处理器调用软件的形式实现，或全部通过硬件电路的形式实现，或部分通过处理器调用软件的形式实现，剩余部分通过硬件电路的形式实现。
在本公开实施例中，处理器是具有信号处理能力的电路，在一种实现中，处理器可以是具有指 令读取与运行能力的电路，例如CPU、微处理器、图形处理器(graphics processing unit，GPU)(也可以理解为微处理器)、或数字信号处理器(digital signal processor，DSP)等；在另一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，上述硬件电路的逻辑关系是固定的或可以重构的，例如处理器为ASIC或PLD实现的硬件电路，例如FPGA。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元或模块的功能的过程。此外，还可以是针对人工智能设计的硬件电路，其可以理解为ASIC，例如神经网络处理单元(neural network processing unit，NPU)、张量处理单元(tensor processing unit，TPU)、深度学习处理单元(deep learning processing unit，DPU)等。
图7A是根据本公开实施例示出的终端的一种结构示意图。上述终端101的结构可以如图7A所示。终端7100可以包括：第一收发模块7101、第一处理模块7102等中的至少一者。在一些实施例中，上述第一处理模块7102用于在测量间隙内执行GNSS测量；第一收发模块7101用于发送第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。可选地，上述第一收发模块7101用于执行以上任一方法中终端101执行的发送和/或接收等通信步骤(例如步骤S2110、步骤S2120、步骤S2140、步骤S2210、步骤S2230、步骤S2250、步骤S2260、步骤S2310、步骤S2340、步骤S2360、步骤S2370、步骤S2410、步骤S2420、步骤S2440、步骤S2510、步骤S2530、步骤S2610以及步骤S2640，但不限于此)中的至少一者，此处不再赘述。可选地，上述第一处理模块7102用于执行以上任一方法中终端101执行的其他步骤(例如步骤S2130、步骤S2220、步骤S2320、步骤S2330、步骤S2430、步骤S2520、步骤S2620以及步骤S2630，但不限于此)中的至少一者，此处不再赘述。
图7B是根据本公开实施例示出的网络设备的一种结构示意图。上述网络设备102的结构可以如图7B所示。网络设备7200可以包括：第二收发模块7201、第二处理模块7202等中的至少一者。在一些实施例中，第二收发模块7201用于接收第一随机接入序列，其中，第一随机接入序列用于指示GNSS测量执行成功或执行失败。可选地，上述第二收发模块7201用于执行以上任一方法中网络设备102执行的发送和/或接收等通信步骤(例如步骤S2110、步骤S2120、步骤S2140、步骤S2250、步骤S2260、步骤S2210、步骤S2230、步骤S2310、步骤S2340、步骤S2360、步骤S2370、步骤S2410、步骤S2420、步骤S2440、步骤S2510、步骤S2530、步骤S2610以及步骤S2640，但不限于此)中的至少一者，此处不再赘述。可选地，上述第二处理模块7202用于执行以上任一方法中网络设备102执行的其他步骤(例如步骤S2150、步骤S2160、步骤S2240、步骤S2350、步骤S2450、步骤S2540以及步骤S2650，但不限于此)中的至少一者，此处不再赘述。
在一些实施例中，收发模块可以包括第一收发模块和/或第二收发模块，第一收发模块和第二收发模块可以是分离的，也可以集成在一起。可选地，收发模块可以与收发器相互替换。
在一些实施例中，处理模块可以包括第一处理模块和/或第二处理模块，可以是一个模块，也可以包括多个子模块。可选地，上述多个子模块分别执行处理模块所需执行的全部或部分步骤。可选地，处理模块可以与处理器相互替换。
图8A是根据本公开实施例示出的通信设备的一种结构示意图。如图8A所示，通信设备8100可以是网络设备(例如接入网设备)，也可以是终端(例如用户设备等)，也可以是支持网络设备实现以上任一方法的芯片、芯片系统、或处理器等，还可以是支持终端实现以上任一方法的芯片、芯片系统、或处理器等。通信设备8100可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
如图8A所示，通信设备8100包括一个或多个处理器8101。处理器8101可以是通用处理器或者专用处理器等，例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行程序，处理程序的数据。可选地，通信设备8100用于执行以上任一方法。可选地，一个或多个处理器8101用于调用指令以使得通信设备8100执行以上任一方法。
在一些实施例中，通信设备8100还包括一个或多个收发器8102。在通信设备8100包括一个或多个收发器8102时，收发器8102执行上述方法中的发送和/或接收等通信步骤(例如步骤S2110、步骤S2120、步骤S2140、步骤S2210、步骤S2230、步骤S2250、步骤S2260、步骤S2310、步骤S2340、步骤S2360、步骤S2370、步骤S2410、步骤S2420、步骤S2440、步骤S2510、步骤S2530、步骤S2610以及步骤S2640，但不限于此)中的至少一者，处理器8101执行其他步骤(例如步骤S2130、步骤S2150、步骤S2160、步骤S2220、步骤S2240、步骤S2320、步骤S2330、步骤S2350、步骤S2430、步骤S2450、步骤S2520、步骤S2540、步骤S2620、步骤S2630以及步骤S2650，但不限于此)中的至少一者。在可选的实施例中，收发器可以包括接收器和/或发送器，接收器和发送器可以是分离的，也可以集成在一起。可选地，收发器、收发单元、收发机、收发电路、接口电路、接口等术语可以相互替换，发送器、发送单元、发送机、发送电路等术语可以相互替换，接收器、接收单元、接收机、接收电路等术语可以相互替换。
在一些实施例中，通信设备8100还包括用于存储数据的一个或多个存储器8103。可选地，全部或部分存储器8103也可以处于通信设备8100之外。在可选的实施例中，通信设备8100可以包括一个或多个接口电路8104。可选地，接口电路8104与存储器8102连接，接口电路8104可用于从存储器8102或其他装置接收数据，可用于向存储器8102或其他装置发送数据。例如，接口电路8104可读取存储器8102中存储的数据，并将该数据发送给处理器8101。
以上实施例描述中的通信设备8100可以是网络设备或者终端，但本公开中描述的通信设备8100的范围并不限于此，通信设备8100的结构可以不受图8A的限制。通信设备可以是独立的设备或者可以是较大设备的一部分。例如所述通信设备可以是：1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选地，上述IC集合也可以包括用于存储数据，程序的存储部件；(3)ASIC，例如调制解调器(modem)；(4)可嵌入在其他设备内的模块；(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；(6)其他等等。
图8B是根据本公开实施例示出的芯片的一种结构示意图。对于通信设备8100可以是芯片或芯片系统的情况，可以参见图8B所示的芯片8200的结构示意图，但不限于此。
在一些实施例中，芯片8200可以包括一个或多个处理器8201。芯片8200用于执行以上任一方法。
在一些实施例中，芯片8200还可以包括一个或多个接口电路8202。可选地，接口电路、接口、收发管脚等术语可以相互替换。在一些实施例中，芯片8200还包括用于存储数据的一个或多个存储器8203。可选地，全部或部分存储器8203可以处于芯片8200之外。可选地，接口电路8202与存储器8203连接，接口电路8202可以用于从存储器8203或其他装置接收数据，接口电路8202可用于向存储器8203或其他装置发送数据。例如，接口电路8202可读取存储器8203中存储的数据，并将该数据发送给处理器8201。
在一些实施例中，接口电路8202执行上述方法中的发送和/或接收等通信步骤(例如步骤S2110、步骤S2120、步骤S2140、步骤S2210、步骤S2230、步骤S2250、步骤S2260、步骤S2310、步骤S2340、步骤S2360、步骤S2370、步骤S2410、步骤S2420、步骤S2440、步骤S2510、步骤S2530、步骤S2610以及步骤S2640，但不限于此)中的至少一者。接口电路8202执行上述方法中的发送和/或接收等通信步骤例如是指：接口电路8202执行处理器8201、芯片8200、存储器8203或收发器件之间的数据交互。在一些实施例中，处理器8201执行其他步骤(例如步骤S2130、步骤S2150、步骤S2160、步骤S2220、步骤S2240、步骤S2320、步骤S2330、步骤S2350、步骤S2430、步骤S2450、步骤S2520、步骤S2540、步骤S2620、步骤S2630以及步骤S2650，但不限于此)中的至少一者。
本公开实施例还提出存储介质，上述存储介质上存储有指令，当上述指令在通信设备8100上运行时，使得通信设备8100执行以上任一方法。可选地，上述存储介质是电子存储介质。可选地，上述存储介质是计算机可读存储介质，但不限于此，其也可以是其他装置可读的存储介质。可选地，上述存储介质可以是非暂时性(non-transitory)存储介质，但不限于此，其也可以是暂时性存储介质。
本公开实施例还提出程序产品，上述程序产品被通信设备8100执行时，使得通信设备8100执行以上任一方法。可选地，上述程序产品是计算机程序产品。
本公开实施例还提出计算机程序，当其在计算机上运行时，使得计算机执行以上任一方法。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开实施例旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开实施例未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (28)

  1. 一种通信方法，所述方法包括：
    在测量间隙内执行全球导航卫星系统GNSS测量；
    发送第一随机接入序列，其中，所述第一随机接入序列用于指示所述GNSS测量执行成功或执行失败。
  2. 根据权利要求1所述的方法，其中，所述发送第一随机接入序列，包括：
    发送第一消息，所述第一消息携带有所述第一随机接入序列，所述第一消息用于发起随机接入过程。
  3. 根据权利要求1或2所述的方法，其中，在所述GNSS测量执行成功的情况下，在所述发送第一随机接入序列之前，所述方法还包括：
    根据随机接入信道序列与GNSS有效期的对应关系，确定与终端的GNSS有效期关联的所述第一随机接入序列。
  4. 根据权利要求3所述的方法，其中，所述随机接入序列用于所述终端的基于竞争的随机接入过程。
  5. 根据权利要求1或2所述的方法，其中，在所述GNSS测量执行成功的情况下，所述第一随机接入序列是由网络设备为终端的基于非竞争的随机接入过程配置的。
  6. 根据权利要求1或2所述的方法，其中，在所述GNSS测量执行成功的情况下，在所述发送第一随机接入序列之前，所述方法还包括：
    获得与所述GNSS测量执行成功关联的至少一个第二随机接入序列；
    从所述至少一个第二随机接入序列中，确定所述第一随机接入序列。
  7. 根据权利要求1至6任一项所述的方法，其中，所述方法还包括：
    发送第一时间信息，所述第一时间信息用于指示终端的GNSS有效期。
  8. 根据权利要求1或2所述的方法，其中，在所述GNSS测量执行失败的情况下，在所述发送第一随机接入序列之前，所述方法还包括：
    获得与所述GNSS测量执行失败关联的至少一个第三随机接入序列；
    从所述至少一个第三随机接入序列中，确定所述第一随机接入序列。
  9. 根据权利要求1、2或8所述的方法，其中，在所述GNSS测量执行失败的情况下，所述方法还包括：
    确定终端当前使用的GNSS有效期已过期；
    进入空闲状态或确定发生无线链路失败RLF。
  10. 根据权利要求1或2所述的方法，其中，在所述GNSS测量执行失败的情况下，所述方法还包括：
    确定终端当前使用的GNSS有效期未过期；
    保持处于连接状态，直至所述终端当前使用的GNSS有效期过期。
  11. 一种通信方法，所述方法包括：
    接收第一随机接入序列，其中，所述第一随机接入序列用于指示终端在测量间隙内的GNSS测量执行成功或执行失败。
  12. 根据权利要求11所述的方法，其中，所述接收第一随机接入序列，包括：
    接收第一消息，所述第一消息中携带有所述第一随机接入序列，所述第一消息用于发起随机接入过程。
  13. 根据权利要求11或12所述的方法，其中，所述方法还包括：
    根据随机接入信道序列与GNSS有效期的对应关系，确定所述第一随机接入序列关联的所述终端的GNSS有效期。
  14. 根据权利要求13所述的方法，其中，所述随机接入序列用于所述终端的基于竞争的随机接入过程。
  15. 根据权利要求14所述的方法，其中，所述方法还包括：
    发送第一信息，所述第一信息用于指示所述随机接入信道序列与GNSS有效期的对应关系，所述对应关系用于所述终端确定与所述终端的GNSS有效期关联的所述第一随机接入序列。
  16. 根据权利要求11或12所述的方法，其中，所述第一随机接入序列是由网络设备为所述终端的基于非竞争的随机接入过程配置的。
  17. 根据权利要求11或12所述的方法，其中，所述方法还包括：
    确定所述第一随机接入序列为与所述GNSS测量执行成功关联的第二随机接入序列。
  18. 根据权利要求17所述的方法，其中，所述方法还包括：
    发送第一配置信息，所述第一配置信息用于指示与所述GNSS测量执行成功关联的至少一个第二随机接入序列，所述至少一个第二随机接入序列用于所述终端确定所述第一随机接入序列。
  19. 根据权利要求18所述的方法，其中，所述方法还包括：
    发送第二配置信息，所述第二配置信用于指示与随机接入过程关联的第四随机接入序列，所述第四随 机接入序列用于所述终端发起随机接入过程。
  20. 根据权利要求11至19任一项所述的方法，其中，所述方法还包括：
    接收第一时间信息，所述第一时间信息用于指示所述终端的GNSS有效期。
  21. 根据权利要求11或20所述的方法，其中，所述方法还包括：
    确定所述第一随机接入序列为与所述GNSS测量执行失败关联的第三随机接入序列。
  22. 根据权利要求21所述的方法，其中，所述方法还包括：
    发送第三配置信息，所述第三配置信息用于指示与所述GNSS测量执行失败关联的至少一个第三随机接入序列，所述至少一个第三随机接入序列用于所述终端确定所述第一随机接入序列。
  23. 一种通信方法，所述方法包括：
    终端在测量间隙内执行全球导航卫星系统GNSS测量；
    所述终端向网络设备发送第一随机接入序列，其中，所述第一随机接入序列用于指示所述GNSS测量执行成功或执行失败。
  24. 一种终端，包括：
    第一处理模块，用于在测量间隙内执行全球导航卫星系统GNSS测量；
    第一收发模块，用于发送第一随机接入序列，其中，所述第一随机接入序列用于指示所述GNSS测量执行成功或执行失败。
  25. 一种网络设备，包括：
    第二收发模块，用于接收第一随机接入序列，其中，所述第一随机接入序列用于指示全球导航卫星系统GNSS测量执行成功或执行失败。
  26. 一种通信设备，包括：
    一个或多个处理器；
    用于存储指令的一个或者多个存储器；
    其中，所述处理器用于调用所述指令，以使得所述通信设备执行如权利要求1至10、11至22中任一项所述的通信方法。
  27. 一种通信系统，包括：终端和网络设备；
    其中，所述终端被配置为实现如权利要求1至10中任一项所述的通信方法；
    所述网络设备被配置为实现如权利要求11至22中任一项所述的通信方法。
  28. 一种存储介质，其中，所述存储介质存储有指令，其中，所述指令在被处理器执行时执行如权利要求1至10、11至22中任一项所述的通信方法。
PCT/CN2023/121813 2023-09-26 2023-09-26 通信方法、终端、网络设备、通信设备及存储介质 Pending WO2025065299A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/121813 WO2025065299A1 (zh) 2023-09-26 2023-09-26 通信方法、终端、网络设备、通信设备及存储介质
CN202380011345.4A CN117546593A (zh) 2023-09-26 2023-09-26 通信方法、终端、网络设备、通信设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/121813 WO2025065299A1 (zh) 2023-09-26 2023-09-26 通信方法、终端、网络设备、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2025065299A1 true WO2025065299A1 (zh) 2025-04-03

Family

ID=89796306

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/121813 Pending WO2025065299A1 (zh) 2023-09-26 2023-09-26 通信方法、终端、网络设备、通信设备及存储介质

Country Status (2)

Country Link
CN (1) CN117546593A (zh)
WO (1) WO2025065299A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113347733A (zh) * 2020-02-18 2021-09-03 维沃移动通信有限公司 随机接入过程的处理方法、终端设备及网络设备
WO2022157735A1 (en) * 2021-01-25 2022-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Measurement gaps for synchronization signal block measurement time configuration windows in non-terrestrial networks
CN116261885A (zh) * 2022-12-28 2023-06-13 北京小米移动软件有限公司 信息上报方法、装置、通信设备及存储介质
CN116438473A (zh) * 2023-02-22 2023-07-14 北京小米移动软件有限公司 Gnss测量方法、装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113347733A (zh) * 2020-02-18 2021-09-03 维沃移动通信有限公司 随机接入过程的处理方法、终端设备及网络设备
WO2022157735A1 (en) * 2021-01-25 2022-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Measurement gaps for synchronization signal block measurement time configuration windows in non-terrestrial networks
CN116261885A (zh) * 2022-12-28 2023-06-13 北京小米移动软件有限公司 信息上报方法、装置、通信设备及存储介质
CN116438473A (zh) * 2023-02-22 2023-07-14 北京小米移动软件有限公司 Gnss测量方法、装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Correction on missing GNSS support in LPPa", 3GPP DRAFT; R3-100895 CR 36455-900 GNSS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. San Francisco, USA; 20100222, 15 February 2010 (2010-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050424707 *

Also Published As

Publication number Publication date
CN117546593A (zh) 2024-02-09

Similar Documents

Publication Publication Date Title
US12328701B2 (en) Information transmission method, terminal device and network device
US20250184835A1 (en) Method for satellite handover between non-terrestrial networks, terminal device, and network device
US12309841B2 (en) Method for random access and communication device
WO2023051171A1 (zh) 卫星通信方法及装置
EP4598064A1 (en) Position measurement method, timer maintenance method, and device
WO2025000499A1 (zh) 通信方法及装置、设备、系统、存储介质
WO2025152246A1 (zh) 通信方法、终端、网络设备、系统及存储介质
WO2025065301A1 (zh) 通信方法、终端、网络设备、通信设备及存储介质
WO2025000298A1 (zh) 信息传输方法及装置、通信设备、通信系统及存储介质
US20250240760A1 (en) Measurement method and terminal device
WO2023231005A1 (zh) 无线通信的方法及装置
WO2025065299A1 (zh) 通信方法、终端、网络设备、通信设备及存储介质
US12526756B2 (en) Cell switching method, terminal device, and storage medium
WO2025138051A1 (zh) 通信方法、终端、网络设备及系统
WO2025025182A1 (zh) 用于配置定时器的方法及装置、存储介质
WO2024259706A1 (zh) 信息处理方法、终端、网络设备、通信系统、存储介质
WO2025025243A1 (zh) 失败处理方法及装置、存储介质
WO2025118111A1 (zh) 用于无线通信的方法及装置
CN121753276A (zh) 用于定位的方法、终端设备和网络设备
CN116458233B (zh) 无线通信方法、终端设备和网络设备
CN117837213B (zh) 用于无线通信的方法、终端设备以及网络设备
WO2024259662A1 (zh) 信息指示方法、终端、网络设备、通信系统及存储介质
WO2023137643A1 (zh) 重复传输请求方法、装置、设备、系统、芯片及存储介质
WO2024259633A1 (zh) 基于gnss的通信方法和装置、通信设备、通信系统及存储介质
WO2025065177A1 (zh) 用于无线通信的方法及终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23953457

Country of ref document: EP

Kind code of ref document: A1