WO2022267800A1 - 一种数据传输方法和装置 - Google Patents

一种数据传输方法和装置 Download PDF

Info

Publication number
WO2022267800A1
WO2022267800A1 PCT/CN2022/094894 CN2022094894W WO2022267800A1 WO 2022267800 A1 WO2022267800 A1 WO 2022267800A1 CN 2022094894 W CN2022094894 W CN 2022094894W WO 2022267800 A1 WO2022267800 A1 WO 2022267800A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
network device
information
terminal device
harq process
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.)
Ceased
Application number
PCT/CN2022/094894
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP22827297.7A priority Critical patent/EP4351213A4/en
Publication of WO2022267800A1 publication Critical patent/WO2022267800A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/083—Reselecting an access point wherein at least one of the access points is a moving node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection

Definitions

  • the present application relates to the communication field, and more specifically, to a data transmission method and device.
  • the fifth generation (5th generation, 5G) system and 5G evolution network need to meet the business needs of all walks of life and provide wider service coverage.
  • the limited coverage of the current terrestrial mobile communication network can no longer satisfy people at any time, at any time.
  • satellite communication compared with traditional mobile communication systems, satellite communication has wider coverage, supports misaligned transmission links, and communication cost has nothing to do with transmission distance, and can overcome natural geographical obstacles such as oceans, deserts, and mountains.
  • satellite communication can be used as an effective supplement to the traditional network.
  • the present application provides a data transmission method and device, so that in a communication network, when a terminal device performs cell handover, the unfinished HARQ process between the terminal device and the network side can be continuous, reduce communication delay, and obtain soft combining coding gain , supporting services that require both reliability and delay.
  • the present application provides a data transmission method, the method comprising: a first terminal device and a first network device transmit first data, and the first data corresponds to a first Hybrid Automatic Repeat Request (HARQ) process;
  • HARQ Hybrid Automatic Repeat Request
  • the first terminal device switches from the first network device to the second network device, the first terminal device and the second network device transmit second data, the second data corresponding to the In the first HARQ process, the second data includes at least one of retransmission data for the first data and feedback information for the first data.
  • HARQ Hybrid Automatic Repeat Request
  • the transmission mode between the first terminal device and the first network device or the second network device may be uplink transmission or downlink transmission, which is not limited in this application. That is, the above-mentioned first data and second data may be uplink data or downlink data.
  • the first terminal device when the first terminal device is handed over from the first network device to the second network device, it means that when the first terminal device performs cell handover, although a connection is established with the second network device , but the cell handover has not been completed.
  • the terminal device when the terminal device is performing cell switching, it can continue to transmit the data of the unfinished HARQ process with the target network device of the cell switching.
  • the The above method can reduce communication delay, obtain soft combining coding gain, and support services that require both reliability and delay.
  • the first terminal device and the second network device Transmitting the second data includes: during the first period during which the first terminal device switches from the first network device to the second network device, the first terminal device and the first network device transmit the second data, wherein the first period includes the moment when the first terminal device successfully decodes the first RRC reconfiguration message used to perform the handover to the time when the second network device successfully decodes the first RRC The period between the moments of the reconfiguration complete messages.
  • the terminal device is enabled to continue to transmit data with the network device within the above first period.
  • the above method in this application shortens During the network switching process, the interruption time of user data transmission is improved, the data throughput perceived by the user is improved, and the delay perceived by the user is shortened.
  • the first terminal device and the first network device Transmitting the second data includes: during the first period during which the first terminal device switches from the first network device to the second network device, the first terminal device and the first network device transmit the second data, wherein the first period includes a period between the time when the first terminal device successfully sends the message 1MSG1 and the time when the second network device successfully decodes the first RRC reconfiguration complete message.
  • the scenario of the above method may be that when the first terminal device performs cell handover, and the received RRC reconfiguration message includes condition information, where the condition information is used to indicate that when the condition is met, the first terminal device initiates Non-contention random access to MSG1.
  • the terminal device is enabled to continue to transmit data with the network device within the above first period.
  • the above method in this application shortens During the network switching process, the interruption time of user data transmission is improved, the data throughput perceived by the user is improved, and the delay perceived by the user is shortened.
  • the method before the first terminal device transmits the second data with the second network device, the method includes: the first terminal device transfers the first medium access control layer MAC entity The data of the first HARQ process is copied to a second MAC entity, where the first MAC entity corresponds to the first network device, and the second MAC entity corresponds to the second network device.
  • the terminal device is enabled to retain the unfinished uplink HARQ process data, thereby enabling the unfinished uplink HARQ process to continue.
  • the method before the first terminal device transmits the second data with the second network device, the method includes: the first terminal device receives first indication information, and the first The instruction information is used to instruct the first terminal device to transmit the second data with the second network device.
  • the first indication information includes one or more of the following information: an identifier of the first HARQ process, an identifier of the second network device, and a first resource, where the The first resource is a resource occupied by the second data.
  • the terminal device is enabled to know more accurately the HARQ process to be continued, the destination network device, and the transmission resource corresponding to the HARQ process.
  • the first data is uplink data
  • the second data includes data on which retransmission processing is performed on the first data
  • the first data is downlink data
  • the second data includes feedback information for the first data
  • the feedback information of the first data includes an acknowledgment message ACK or a negative acknowledgment NACK.
  • the first network device or the second network device is a satellite.
  • the present application provides a data transmission method, the method includes: a first network device receives first information, and the first information is used to instruct the first terminal device to switch from the second network device to the first A network device; the first network device acquires second information, where the second information is used to indicate an unfinished first hybrid automatic repeat request (HARQ) process between the first terminal device and the second network device ; The first network device sends third information to the first terminal device according to the second information, and the third information is used to instruct the first terminal device to transmit second data with the first network device , the second data corresponds to the first HARQ process, and the second data includes at least one of data for performing retransmission processing on the first data and feedback information for the first data, wherein the first A piece of data corresponds to the first HARQ process, and the first data is data that has been transmitted between the first terminal device and the second network device.
  • HARQ hybrid automatic repeat request
  • the transmission manner between the first terminal device and the first network device or the second network device may be uplink transmission or downlink transmission, which is not limited in this application. That is, the above-mentioned first data and second data may be uplink data or downlink data.
  • the terminal device when the terminal device performs cell switching, it can continue to transmit the data of the unfinished HARQ process with the target network device of the cell switching, and at the same time, the first network device as the target network device of the cell switching can obtain the data
  • the relevant data of the HARQ process can realize the continuous HARQ process.
  • the above-mentioned method in this application can reduce the communication delay, obtain the soft combination coding gain, and support reliable Businesses that require both speed and delay.
  • the method includes: the first network device receives fourth information sent by the second network device within a first period, and the first period includes From the moment when the first radio resource control RRC reconfiguration message for the first terminal device to perform the handover is sent to when the first network device successfully decodes the first RRC reconfiguration complete message sent by the first terminal device
  • the time period between the end times of , the first time period is used for the second network device and the first terminal device to transmit third data
  • the third data includes retransmission processing on the first data
  • the fourth information is update information of the second information and corresponds to the third data.
  • the network device is enabled to continue to transmit data with the terminal device during the above first period.
  • the above method in this application can It shortens the interruption time of user data transmission during the network switching process, improves user-perceived data throughput, and shortens user-perceived delay.
  • the receiving by the first network device of the fourth information sent by the second network device within the first time period includes: the first network device at the beginning of the first time period and after receiving the fourth information sent by the second network device with a first delay.
  • the value of the first delay is 2*RTT
  • the RTT is data transmission between the first terminal device and the first network device or the second network device round-trip delay.
  • the first network device is enabled to receive the fourth information after the first time delay at the earliest, so as to avoid redundant power consumption by the first network device.
  • the method includes: the first network device receives the fifth information sent by the second network device at the end moment of receiving the fourth information and after a second time delay, the The fifth information is update information of the fourth information, the value of the second time delay is n times (0.5*RTT), and the n is a positive integer.
  • the fifth information may include information of an updated part compared to the fourth information, and may also include information of an original part of the fourth information.
  • the first network device is enabled to periodically receive the fifth information at the end of receiving the fourth information, which can ensure the timely update of the data of the unfinished HARQ process.
  • the second information includes at least one of the following information: redundancy version data of the first HARQ process, an identifier of the first HARQ process, Redundant version number.
  • the second information includes at least one of the following information: the data of the first HARQ process that the second network device has received, the Data that has been decoded by the first HARQ process.
  • the third information includes one or more of the following information: an identifier of the first HARQ process, an identifier of the first network device, and a first resource, wherein the The first resource is a resource occupied by transmitting the second data.
  • the terminal device is enabled to know more accurately the HARQ process to be continued, the destination network device, and the transmission resource corresponding to the HARQ process.
  • the second data when the first data is uplink data, the second data includes data that performs retransmission processing on the first data.
  • the second data when the first data is downlink data, the second data includes feedback information for the first data.
  • the feedback information of the first data includes an acknowledgment message ACK or a negative acknowledgment NACK.
  • the first terminal device or the second network device is a satellite.
  • the present application provides a data transmission method, the method including: a first network device and a first terminal device transmit first data, and the first data corresponds to a first hybrid automatic repeat request (HARQ) process;
  • HARQ hybrid automatic repeat request
  • the first network device sends first information to the second network device, where the first information is used to indicate the Describe the first HARQ process.
  • the transmission manner between the first terminal device and the first network device or the second network device may be uplink transmission or downlink transmission, which is not limited in this application. That is, the above-mentioned first data and second data may be uplink data or downlink data.
  • the terminal device when the terminal device performs cell handover, it can continue to transmit the data of the unfinished HARQ process with the destination network device of the cell handover. Send the relevant data of the unfinished HARQ process, so that the second network device can grasp the relevant data of the completed HARQ process, and realize the continuous HARQ process.
  • the method in this application The above method can reduce communication delay, obtain soft combining coding gain, and support services that require both reliability and delay.
  • the first information includes at least one of the following information: redundancy version data of the first HARQ process, an identifier of the first HARQ process, Redundant version number.
  • the first information includes at least one of the following information: the data of the first HARQ process that the first network device has received, the Data that has been decoded by the first HARQ process.
  • the method includes: the first network device transmits second data with the first terminal device within a first period, and the second data includes retransmitting at least one of the processed data, the feedback information for the first data, and the initial data of the second HARQ process, wherein the first period includes the A period between the moment when the device executes the handover first RRC reconfiguration message and the moment when the second network device successfully decodes the first RRC reconfiguration complete message sent by the first terminal device.
  • the network device is enabled to continue to transmit data with the terminal device during the above first period.
  • the above method in this application can It shortens the interruption time of user data transmission during the network switching process, improves user-perceived data throughput, and shortens user-perceived delay.
  • the method includes: the first network device sends the second information to the second network device at the start moment of the first period and after a first time delay, the The second information is update information of the first information.
  • the second network device is enabled to receive information at the specified time, reducing power consumption.
  • the first network device is a first satellite
  • the second network device is a second satellite
  • an inter-satellite link exists between the first network device and the second network device
  • the value of the first delay is 2*RTT1-0.5*RTT2
  • the RTT1 is a round-trip delay of data transmission between the first terminal device and the first network device or the second network device
  • the RTT2 is a round-trip time delay of data transmission between the first network device and the second network device.
  • the first network device is a first satellite
  • the second network device is a second satellite
  • the first network device and the second network device communicate through a third network device.
  • the value of the first delay is 2*RTT3-RTT4, wherein the RTT3 is a round trip of data transmission between the first terminal device and the first network device or the second network device delay, the RTT4 is the sum of the second delay and the third delay, the second delay is the delay of data transmission between the first network device and the third network device, and the third The delay is the delay of data transmission between the second network device and the third network device.
  • the first network device and the second network device are first satellites, and the value of the first time delay is 2*RTT5, where the RTT5 is the first A round-trip delay of data transmission between the terminal device and the first network device.
  • the method includes: the first network device sends third information to the second network device after a second time delay at the moment when the second information is sent, and the first network device sends the third information to the second network device.
  • the third information is the update information of the second information, and the value of the second delay is n times (0.5*RTT6), and the RTT6 is the first terminal device and the first network device or the The round-trip delay of data transmission between the second network devices, where n is a positive integer.
  • the third information may include information of an updated part compared to the second information, and may also include information of an original part of the second information.
  • the first network device is enabled to periodically send the third information at the moment when the second information is sent, which can ensure the timely update of the data of the unfinished HARQ process in the second network device.
  • a data transmission device in a fourth aspect, includes: a transceiver module, the transceiver module is used for the first terminal device and the first network device to transmit first data, the first data corresponds to the first hybrid automatic A retransmission request HARQ process; when the first terminal device is switched from the first network device to the second network device, the transceiver module is also used for the first terminal device to communicate with the second network device
  • the network device transmits second data, where the second data corresponds to the first HARQ process, where the second data includes data that performs retransmission processing on the first data, and information in feedback information for the first data at least one.
  • the transmission manner between the first terminal device and the first network device or the second network device may be uplink transmission or downlink transmission, which is not limited in this application. That is, the above-mentioned first data and second data may be uplink data or downlink data.
  • the first terminal device when the first terminal device is handed over from the first network device to the second network device, it means that when the first terminal device performs cell handover, although a connection is established with the second network device , but the cell handover has not been completed.
  • the terminal device when the terminal device is performing cell switching, it can continue to transmit the data of the unfinished HARQ process with the target network device of the cell switching.
  • the The above method can reduce communication delay, obtain soft combining coding gain, and support services that require both reliability and delay.
  • the transceiver module when the first terminal device switches from the first network device to the second network device, the transceiver module is also used for the first terminal device
  • the transmitting the second data with the second network device includes: during the first period during which the first terminal device switches from the first network device to the second network device, the transceiver module is also used for the The first terminal device transmits second data with the first network device, wherein the first period of time includes the first radio resource control RRC reconfiguration message successfully decoded by the first terminal device for performing the handover A time period between the moment and the moment when the second network device successfully decodes the first RRC reconfiguration complete message.
  • the terminal device is enabled to continue to transmit data with the network device during the above-mentioned first period.
  • the above-mentioned method in this application can It shortens the interruption time of user data transmission during the network switching process, improves user-perceived data throughput, and shortens user-perceived delay.
  • the transceiver module when the first terminal device switches from the first network device to the second network device, the transceiver module is also used for communicating with the first terminal device
  • the transmission of the second data by the first network device includes: during the first period during which the first terminal device switches from the first network device to the second network device, the transceiver module is also used for the first
  • the terminal device transmits second data with the first network device, wherein the first period includes the moment when the first terminal device successfully sends the message 1MSG1 to the time when the second network device successfully decodes the first RRC reconfiguration The time period between the moments of the messages. .
  • the scenario of the above method may be that when the first terminal device performs cell handover, and the received RRC reconfiguration message includes condition information, where the condition information is used to indicate that when the condition is met, the first terminal device initiates Non-contention random access to MSG1.
  • the terminal device is enabled to continue to transmit data with the network device within the above first period.
  • the above method in this application shortens During the network switching process, the interruption time of user data transmission is improved, the data throughput perceived by the user is improved, and the delay perceived by the user is shortened.
  • the apparatus before the first terminal device and the second network device transmit the second data, the apparatus includes: a processing module, the processing module is used for the first terminal device to The data of the first HARQ process in the first medium access control layer MAC entity is copied to the second MAC entity, wherein the first MAC entity corresponds to the first network device, and the second MAC entity corresponds to the the second network device.
  • the terminal device is enabled to retain the unfinished uplink HARQ process data, thereby enabling the unfinished uplink HARQ process to continue.
  • the transceiver module before the first terminal device transmits the second data with the second network device, the transceiver module is further configured for the first terminal device to receive first indication information, the The first indication information is used to instruct the first terminal device to transmit the second data with the second network device.
  • the first indication information includes one or more of the following information: an identifier of the first HARQ process, an identifier of the second network device, and a first resource, where the The first resource is a resource occupied by the second data.
  • the terminal device is enabled to know more accurately the HARQ process to be continued, the destination network device, and the transmission resource corresponding to the HARQ process.
  • the first data is uplink data
  • the second data includes data on which retransmission processing is performed on the first data
  • the first data is downlink data
  • the second data includes feedback information for the first data
  • the feedback information of the first data includes an acknowledgment message ACK or a negative acknowledgment NACK.
  • the first network device or the second network device is a satellite.
  • the fourth aspect and the devices in various implementation manners of the fourth aspect may be referred to as a first communication device.
  • the present application provides a data transmission device, the device comprising: a transceiver module, the transceiver module is used for a first network device to receive first information, and the first information is used to instruct the first terminal device from The second network device switches to the first network device; the transceiver module is also used for the first network device to obtain second information, and the second information is used to indicate that the first terminal device and the second An unfinished first hybrid automatic repeat request HARQ process between network devices; the transceiver module is also used for the first network device to send third information to the first terminal device according to the second information, the The third information is used to instruct the first terminal device to transmit second data with the first network device, the second data corresponds to the first HARQ process, and the second data includes retransmission of the first data At least one of the processed data and the feedback information for the first data, where the first data corresponds to the first HARQ process, and the first data is the first terminal device and the second Data that has been transferred between network devices.
  • the transmission manner between the first terminal device and the first network device or the second network device may be uplink transmission or downlink transmission, which is not limited in this application. That is, the above-mentioned first data and second data may be uplink data or downlink data.
  • the terminal device when the terminal device performs cell switching, it can continue to transmit the data of the unfinished HARQ process with the target network device of the cell switching, and at the same time, the first network device as the target network device of the cell switching can obtain the data
  • the relevant data of the HARQ process can realize the continuous HARQ process.
  • the above-mentioned method in this application can reduce the communication delay, obtain the soft combination coding gain, and support reliable Businesses that require both speed and delay.
  • the transceiver module is further configured for the first network device to receive fourth information sent by the second network device within a first period, the first period including the second From the moment when the network device sends out the first radio resource control RRC reconfiguration message for the first terminal device to perform the handover to when the first network device successfully decodes the first RRC reconfiguration message sent by the first terminal device A period between the end moments of the completion message, the first period is used for the second network device and the first terminal device to transmit third data, the third data includes retransmission of the first data At least one of processed data, feedback information for the first data, and initial data of a second HARQ process, the fourth information is update information of the second information and corresponds to the third data.
  • the network device is enabled to continue to transmit data with the terminal device during the above first period.
  • the above method in this application can It shortens the interruption time of user data transmission during the network switching process, improves user-perceived data throughput, and shortens user-perceived delay.
  • the sending and receiving module is further used for the first network device to receive the fourth information sent by the second network device within the first period of time includes: the sending and receiving module is also used for the The first network device receives the fourth information sent by the second network device at the starting moment of the first time period and after a first time delay.
  • the value of the first delay is 2*RTT
  • the RTT is data transmission between the first terminal device and the first network device or the second network device round-trip delay.
  • the first network device is enabled to receive the fourth information after the first time delay at the earliest, so as to avoid redundant power consumption by the first network device.
  • the transceiver module is further configured for the first network device to receive the fifth information sent by the second network device at the end of receiving the fourth information and after a second time delay , the fifth information is update information of the fourth information, the value of the second time delay is n times (0.5*RTT), and the n is a positive integer.
  • the fifth information may include information of an updated part compared to the fourth information, and may also include information of an original part of the fourth information.
  • the first network device is enabled to periodically receive the fifth information at the end of receiving the fourth information, which can ensure the timely update of the data of the unfinished HARQ process.
  • the second information includes at least one of the following information: redundancy version data of the first HARQ process, an identifier of the first HARQ process, Redundant version number.
  • the second information includes at least one of the following information: the data of the first HARQ process that the second network device has received, the Data that has been decoded by the first HARQ process.
  • the third information includes one or more of the following information: an identifier of the first HARQ process, an identifier of the first network device, and a first resource, wherein the The first resource is a resource occupied by transmitting the second data.
  • the terminal device is enabled to know more accurately the HARQ process to be continued, the destination network device, and the transmission resource corresponding to the HARQ process.
  • the second data when the first data is uplink data, the second data includes data that performs retransmission processing on the first data.
  • the second data when the first data is downlink data, the second data includes feedback information for the first data.
  • the feedback information of the first data includes an acknowledgment message ACK or a negative acknowledgment NACK.
  • the first terminal device or the second network device is a satellite.
  • the fifth aspect and the devices in various implementation manners of the fifth aspect may be referred to as the second communication device.
  • the present application provides a data transmission device, the device comprising: a transceiver module, the transceiver module is used for transmitting first data between a first network device and a first terminal device, and the first data corresponds to the first A hybrid automatic repeat request HARQ process; when the first terminal device switches from the first network device to the second network device, the transceiver module is also used for the first network device to send the second network device The network device sends first information, where the first information is used to indicate the first HARQ process.
  • the transmission manner between the first terminal device and the first network device or the second network device may be uplink transmission or downlink transmission, which is not limited in this application. That is, the above-mentioned first data and second data may be uplink data or downlink data.
  • the terminal device when the terminal device performs cell handover, it can continue to transmit the data of the unfinished HARQ process with the destination network device of the cell handover. Send the relevant data of the unfinished HARQ process, so that the second network device can grasp the relevant data of the completed HARQ process, and realize the continuous HARQ process.
  • the method in this application The above method can reduce communication delay, obtain soft combining coding gain, and support services that require both reliability and delay.
  • the first information includes at least one of the following information: redundancy version data of the first HARQ process, an identifier of the first HARQ process, Redundant version number.
  • the first information includes at least one of the following information: the data of the first HARQ process that the first network device has received, the Data that has been decoded by the first HARQ process.
  • the transceiver module is further used for the first network device to transmit second data with the first terminal device within a first time period, the second data includes At least one of the data for retransmission processing, the feedback information for the first data, and the initial data of the second HARQ process, wherein the first period includes the A period between the moment when a terminal device executes the first radio resource control RRC reconfiguration message of the handover and the moment when the second network device successfully decodes the first RRC reconfiguration complete message sent by the first terminal device .
  • the network device is enabled to continue to transmit data with the terminal device during the above first period.
  • the above method in this application can It shortens the interruption time of user data transmission during the network switching process, improves user-perceived data throughput, and shortens user-perceived delay.
  • the transceiver module is further configured for the first network device to send the second information to the second network device at the start moment of the first time period and after a first time delay,
  • the second information is update information of the first information.
  • the second network device is enabled to receive information at the specified time, reducing power consumption.
  • the first network device is a first satellite
  • the second network device is a second satellite
  • an inter-satellite link exists between the first network device and the second network device
  • the value of the first delay is 2*RTT1-0.5*RTT2
  • the RTT1 is a round-trip delay of data transmission between the first terminal device and the first network device or the second network device
  • the RTT2 is a round-trip time delay of data transmission between the first network device and the second network device.
  • the first network device is a first satellite
  • the second network device is a second satellite
  • the first network device and the second network device communicate through a third network device.
  • the value of the first delay is 2*RTT3-RTT4, wherein the RTT3 is a round trip of data transmission between the first terminal device and the first network device or the second network device delay, the RTT4 is the sum of the second delay and the third delay, the second delay is the delay of data transmission between the first network device and the third network device, and the third The delay is the delay of data transmission between the second network device and the third network device.
  • the first network device and the second network device are first satellites, and the value of the first time delay is 2*RTT5, where the RTT5 is the first A round-trip delay of data transmission between the terminal device and the first network device.
  • the transceiver module is further configured for the first network device to send third information to the second network device after a second time delay at the time when the first network device sends the second information, so
  • the third information is update information of the second information
  • the value of the second delay is n times (0.5*RTT6)
  • the RTT6 is the first terminal device and the first network device or A round-trip delay of data transmission between the second network devices, where n is a positive integer.
  • the third information may include information of an updated part compared to the second information, and may also include information of an original part of the second information.
  • the first network device is enabled to periodically send the third information at the moment when the second information is sent, which can ensure the timely update of the data of the unfinished HARQ process in the second network device.
  • the sixth aspect and the devices in various implementation manners of the sixth aspect may be referred to as the third communication device.
  • a communication device is provided, and the communication device may be the first communication device in the above method embodiment, or a chip provided in the communication device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions
  • the processor is coupled to the memory and the communication interface.
  • the communication device executes the methods performed by the communication device in the above method embodiments.
  • the memory and the processor may be integrated together, or may be independent devices.
  • a communication device is provided, and the communication device may be the second communication device in the above method embodiment, or a chip provided in the second communication device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions
  • the processor is coupled to the memory and the communication interface.
  • the communication device is made to execute the method performed by the second communication device in the above method embodiment. method.
  • the memory and the processor may be integrated together, or may be independent devices.
  • a communication device is provided, and the communication device may be the third communication device in the foregoing method embodiment, or a chip provided in the third communication device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions
  • the processor is coupled to the memory and the communication interface.
  • the communication device is made to execute the method performed by the third communication device in the above method embodiment. method.
  • the memory and the processor may be integrated together, or may be independent devices.
  • a computer program product comprising: computer program code, when the computer program code is executed, the method performed by the first communication device in the above aspects is executed.
  • the first communication device may be a terminal device.
  • a computer program product includes: computer program code, when the computer program code is executed, the method performed by the second communication device in the above aspects is executed.
  • the second communication device may be a network device, such as a satellite.
  • a computer program product comprising: computer program code, when the computer program code is executed, the methods performed by the third communication device in the above aspects are executed.
  • the third communication device may be a network device, such as a satellite.
  • the present application provides a chip system, where the chip system includes a processor, configured to implement the functions of the first communication device in the methods of the above aspects.
  • the chip system further includes a memory, configured to store program instructions and/or data.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the present application provides a system-on-a-chip, where the system-on-a-chip includes a processor, configured to implement the functions of the second communication device in the methods of the above aspects.
  • the chip system further includes a memory, configured to store program instructions and/or data.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the present application provides a system-on-a-chip, where the system-on-a-chip includes a processor, configured to implement the functions of the third communication device in the methods of the above aspects.
  • the chip system further includes a memory, configured to store program instructions and/or data.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method performed by the first communication device in the above aspects is realized.
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the methods performed by the second communication device in the above aspects are realized.
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the methods performed by the third communication device in the above aspects are implemented.
  • Fig. 1 is a diagram of an application scenario applicable to the embodiment of the present application.
  • Fig. 2 is a diagram of another application scenario applicable to the embodiment of the present application.
  • Fig. 3 is a diagram of another application scenario applicable to the embodiment of the present application.
  • Fig. 4 is a diagram of another application scenario applicable to the embodiment of the present application.
  • Fig. 5 is a schematic flowchart of an example of the embodiment of the present application.
  • Fig. 6 is a schematic flowchart of another example of the embodiment of the present application.
  • Fig. 7 is another schematic flowchart of the embodiment of the present application.
  • Fig. 8 is another schematic flowchart of the embodiment of the present application.
  • Fig. 9 is another schematic flowchart of the embodiment of the present application.
  • Fig. 10 is another schematic flowchart of the embodiment of the present application.
  • Fig. 11 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
  • Fig. 12 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
  • NB-IoT narrow band-internet of things
  • GSM global system of mobile communication
  • CDMA code division Multiple access
  • WCDMA wideband code division multiple access
  • general packet radio service general packet radio service, GPRS
  • long term evolution long term evolution, LTE
  • LTE frequency division duplex FDD
  • LTE time division duplex TDD
  • UMTS universal mobile telecommunications system
  • WiMAX global interconnection microwave access
  • the terminal equipment in the embodiment of the present application may also be referred to as user equipment (user equipment, UE), access terminal, terminal equipment unit (subscriber unit), terminal equipment station, mobile station, mobile station (mobile station, MS), Remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, terminal agent, or terminal device.
  • the terminal device may include various handheld devices with wireless communication functions, vehicle-mounted devices, Internet of things (internet of things, IoT) devices, wearable devices, computing devices, or other processing devices connected to a wireless modem.
  • IoT Internet of things
  • cellular phone cellular phone
  • smart phone smart phone
  • wireless data card personal digital assistant (personal digital assistant, PDA) computer
  • tablet computer wireless modem (modem)
  • handheld device handset
  • laptop computer laptop computer
  • machine type communication machine type communication
  • unmanned aerial vehicle station (station, ST) in wireless local area network (wireless local area networks, WLAN).
  • station station, ST
  • wireless local area network wireless local area networks, WLAN.
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a global system of mobile communication (GSM) system or a code division multiple access (code division multiple access, CDMA) base transceiver station (BTS), or a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolved base station (evolutional nodeB) in an LTE system , eNB or eNodeB), can also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or a satellite base station in a satellite communication system, or a network device can be a relay station, an access point , in-vehicle devices, wearable devices, and network devices in 5G networks or network devices in future evolved PLMN networks, it can also be device-to-device (D2D) communication, machine-to-machine (machine-to- The device that assumes the base station function in machine, M
  • Satellite Constellation In a satellite constellation, multiple satellites work together to provide coverage over an area greater than any single satellite can cover by itself.
  • high-orbit (geostationary earth orbit, GEO) satellite communication system also known as geostationary orbit satellite system
  • medium-orbit (medium earth orbit, MEO) satellite communication system and low-orbit (Low Earth Orbit, LEO) satellite communication system.
  • GEO geostationary earth orbit
  • MEO medium-orbit
  • LEO Low Earth Orbit
  • the giant communication constellation represented by SpaceX in the United States, the satellites in this constellation have large-capacity inter-satellite communication capabilities, which enable the satellite communication system to have more flexible network management capabilities, reduce dependence on ground networks, and enhance system communication capabilities.
  • 5G NR (or LTE) retransmission mechanism: 5G NR has multiple backhaul mechanisms, using the following three-layer protocol stack:
  • Media access control (media access control, MAC) protocol layer It implements a fast retransmission system in NR, called hybrid automatic repeat request (HARQ).
  • HARQ hybrid automatic repeat request
  • Radio link control (radio link control, RLC) protocol layer Although there is already HARQ in the MAC layer, there may still be some errors in the feedback system. So, to handle these errors, the RLC layer has a slow retransmission system, and this feedback is protected by a cyclic redundancy check (CRC). Compared with the HARQ acknowledgment mode, the transmission frequency of the RLC status report is relatively low.
  • RLC radio link control
  • Packet data convergence protocol (PDCP) protocol layer This will ensure the sequential transmission of user data, which is mainly used during handover. Because both the RLC and MAC buffers are cleared when switching is performed.
  • PDCP Packet data convergence protocol
  • MAC layer HARQ is a technology that combines FEC (forward error correction, forward error correction) and automatic repeat request (automatic repeat request, ARQ) method.
  • FEC forward error correction, forward error correction
  • ARQ automatic repeat request
  • the receiving end uses an error detection code, usually a CRC check, to detect whether the received data packet has an error. If there is no error, the receiving end will send a positive acknowledgment (ACK) to the sending end, and the sending end will send the next data packet after receiving the ACK. If an error occurs, the receiving end will discard the data packet and send a negative acknowledgment (NAK) to the sending end. After receiving the NAK, the sending end will resend the same data.
  • FEC forward error correction, forward error correction
  • ARQ automatic repeat request
  • the ARQ mechanism of the MAC layer adopts the method of discarding data packets and requesting retransmission. Although these packets cannot be decoded correctly, they still contain useful information, which is lost if discarded.
  • received erroneous data packets will be stored in a HARQ buffer (buffer), and combined with subsequent received retransmitted data packets to obtain a data packet that is more reliable than decoding alone (this process can be called as a "soft merge"). Then decode the merged data packet, if it still fails, repeat the process of "request retransmission, and then perform soft merge".
  • HARQ is divided into two types: chase combining and incremental redundancy (IR).
  • IR incremental redundancy
  • the retransmitted bit information in catch-up combining is the same as the original transmission; the retransmitted bit information in incremental redundancy does not need to be the same as the original transmission. Only IR mechanism is used in LTE and NR.
  • HARQ process uses the stop-and-wait protocol (stop-and-wait protocol) to send data.
  • stop-and-wait protocol after the sender sends a transport block (TB), it stops and waits for confirmation information.
  • TB transport block
  • each HARQ process needs to have an independent HARQ buffer at the receiving end, so as to perform soft combining on the received data.
  • HARQ process identifier uniquely specifies a HARQ process.
  • New data indicator (new data indicator, NDI): Each HARQ process will save an NDI value, which uses 1 bit to indicate whether the scheduled data is newly transmitted or retransmitted. If the NDI value of the same HARQ process has changed compared to before (NDI toggled), it means that the current transmission is the initial transmission of a new TB, otherwise (NDI not toggled) means that the current transmission is a retransmission of the same TB.
  • PUSCH physical uplink shared channel
  • the UE judges whether the PUSCH is successfully decoded by detecting whether the 5G base station (gNodeB, gNB) sends a return request (indicated by the NDI in the DCI) within a certain period of time.
  • Redundancy version (Redundancy version, RV): It is used to indicate the redundancy version used for transmission, and its value ranges from 0 to 3.
  • RRC radio resource control
  • RRC connected state mobility management the UE can be changed from the original serving cell to the target cell through handover or redirection.
  • Xn interface the interface between 5G base stations and 5G base stations, mainly used for signaling interaction such as handover.
  • NG interface The interface between the 5G base station and the 5G core network, which mainly exchanges signaling such as the non-access stratum (NAS) of the core network and user service data.
  • NAS non-access stratum
  • Access management function access and mobility management function, AMF
  • AMF access and mobility management function
  • MME mobility management entity
  • FIG. 1 is a diagram of an application scenario applicable to the embodiments of the present application.
  • Figure 1 includes satellite and terminal network elements.
  • the satellite provides communication services for the terminal equipment, and the satellite transmits downlink data to the terminal equipment, wherein the data is encoded by channel coding, and the data after channel coding is transmitted to the terminal equipment after constellation modulation; the terminal equipment transmits uplink data to the satellite, and the uplink data Channel coding can also be used for coding, and the coded data is transmitted to the satellite after constellation modulation.
  • Fig. 2 is another application scene diagram applicable to the embodiment of the present application.
  • inter-satellite communication includes communication between multiple satellites, and the traditional satellite inter-satellite link communication system can be divided into: acquisition, aiming , tracking (acquisition, pointing, tracking, APT) subsystem and communication subsystem two parts.
  • the communication subsystem is responsible for the transmission of inter-satellite information and is the main body of the inter-satellite communication system;
  • the APT system is responsible for the capture, alignment and tracking between satellites, determining the incoming wave direction of the incident signal, and adjusting the transmitted wave to aim at the receiving direction for capture. For alignment, alignment and capture are continuously adjusted throughout the communication, for tracking.
  • the existing APT systems are all optical systems.
  • the disadvantage is that the optical alignment is difficult and mechanical adjustment of the pointing is required.
  • Most of the existing communication subsystems are optical communication systems, and some microwave band systems also use a single high-gain antenna.
  • the existing APT system and communication subsystem are independent systems.
  • the disadvantage is that optical communication is easily affected by vibration, etc., and the rate is unstable; the millimeter wave frequency is low, the communication capacity is low, and the antenna needs to be mechanically adjusted.
  • a wireless communication system is usually composed of cells, and each cell includes a base station (BS), which provides communication services to multiple mobile stations (MS).
  • the base station includes a baseband unit (baseband unit, BBU) and a remote radio unit (remote radio unit, RRU).
  • BBU baseband unit
  • RRU remote radio unit
  • the BBU and RRU can be placed in different places, for example: the RRU is remote and placed in areas with high traffic volume, and the BBU is placed in the central equipment room.
  • the BBU and RRU can also be placed in the same equipment room.
  • the BBU and the RRU may also be different components under one rack.
  • FIG. 4 is another application scenario diagram applicable to the embodiment of the present application.
  • the embodiment of the present application may also be applied to the wireless screen projection architecture shown in FIG. 4 .
  • the UE's cell handover in the satellite communication system mainly comes from the high-speed movement of the satellite.
  • In-orbit service satellites can run stably on the designed orbit at high speed, and the range of cells served by each satellite will also move stably and at high speed on the ground according to the planned path. Therefore, the satellite network cells accessed by the UE will frequently and regularly switch.
  • users of satellite network services are mainly distributed outside cities and areas not covered by terrestrial cellular networks. In this type of area, there will be no complex reflections of wireless signals caused by various buildings in the city, so the channel between the UE and the satellite is composed of a line of sight (LOS) path, and its channel transfer function mainly depends on the path loss.
  • LOS line of sight
  • the measured signal strengths of the preceding and subsequent cells met by the UE meet certain decision conditions, that is, the signal strength of the previous cell is less than a certain threshold, or the signal strength of the latter cell is greater than a certain threshold.
  • the geometric distance between the UE and the preceding and following satellites is similar; in the same constellation system, the antenna system design parameters of the satellites will also be basically the same. Therefore, the channel before and after the handover of the UE is similar, and the satellite communication system has the conditions for "soft merger" .
  • the satellite communication system directly uses NR's HARQ switching processing method, directly clears the cache of the current HARQ process, and uses ARQ to re-transmit data in the next cell, because the time delay used by the ARQ transmission method in the upper layer is higher than that in the HARQ transmission in the lower layer.
  • the time delay used by the ARQ method is longer, which will increase the relatively long satellite communication delay, and the amount of data transmitted by the ARQ method is larger than that transmitted by the HARQ method.
  • the HARQ communication cannot be guaranteed.
  • the continuity of the process cannot support services that require reliability and delay at the same time, and although the satellite communication system has the conditions for "soft combining", if the cache of the current HARQ process is directly cleared, the soft combining coding gain cannot be obtained .
  • the present application provides a method 100, as shown in FIG. 5, which is a schematic flowchart of an example of an embodiment of the present application.
  • the first terminal device transmits first data with the first network device.
  • the first data corresponds to the first hybrid automatic repeat request (HARQ) process.
  • HARQ hybrid automatic repeat request
  • the transmission manner between the first terminal device and the first network device or the second network device may be uplink transmission or downlink transmission, which is not limited in this application. That is, the above-mentioned first data may be uplink data or downlink data.
  • the first terminal device transmits second data with the second network device.
  • the second data corresponds to the first HARQ process, and the second data includes at least one of data for performing retransmission processing on the first data and feedback information for the first data.
  • the first terminal device is a terminal device switched from the first network device to the second network device.
  • the above-mentioned second data may be uplink data or downlink data.
  • the manner in which the first terminal device switches from the first network device to the second network device may be that the first terminal device switches from the first network device to the second network device based on a first parameter, wherein the first parameter includes At least one of the following information:
  • the signal quality The signal quality, the location of the first terminal device, the location of the first network device, the event that triggers the handover, the timer that triggers the handover, the time when the handover is triggered, and the time when the handover is triggered.
  • the present application does not limit the manner in which the first terminal device switches from the first network device to the second network device.
  • the first terminal device in the case where the first terminal device is handed over from the first network device to the second network device, it means that the first terminal device establishes a connection with the second network device when performing a cell handover, but the cell handover does not not done.
  • the terminal device when the terminal device is performing cell switching, it can continue to transmit the data of the unfinished HARQ process with the target network device of the cell switching.
  • the The above method can reduce communication delay, obtain soft combining coding gain, and support services that require both reliability and delay.
  • the first terminal device and the first network device transmit the second data, wherein the first period It includes a time period between the time when the first terminal device successfully decodes the first RRC reconfiguration message for performing handover and the time when the second network device successfully decodes the first RRC reconfiguration complete message.
  • the terminal device is enabled to continue to transmit data with the network device during the above-mentioned first period.
  • the above-mentioned method in this application can It shortens the interruption time of user data transmission during the network switching process, improves user-perceived data throughput, and shortens user-perceived delay.
  • the first terminal device and the first network device Transmitting the second data includes: during the first period during which the first terminal device switches from the first network device to the second network device, the first terminal device and the first network device transmit the second data, wherein the first period includes a period between the time when the first terminal device successfully sends the message 1MSG1 and the time when the second network device successfully decodes the first RRC reconfiguration complete message.
  • the scenario of the above method may be that when the first terminal device performs cell handover, and the received RRC reconfiguration message includes condition information, where the condition information is used to indicate that when the condition is met, the first terminal device initiates Non-contention random access to MSG1.
  • the terminal device is enabled to continue to transmit data with the network device within the above first period.
  • the above method in this application shortens During the network switching process, the interruption time of user data transmission is improved, the data throughput perceived by the user is improved, and the delay perceived by the user is shortened.
  • the first terminal device copies the data of the first HARQ process in the first medium access control layer MAC entity to the second MAC entity, where the first MAC entity corresponds to the first network device, The second MAC entity corresponds to the second network device.
  • the terminal device is enabled to retain the unfinished uplink HARQ process data, thereby enabling the unfinished uplink HARQ process to continue.
  • the method before the first terminal device and the second network device transmit the second data, the method includes: the first terminal device receives first indication information, and the first indication information is used to indicate that the first terminal device and the second network device The second network device transmits second data.
  • the first indication information includes one or more of the following information: the identifier of the first HARQ process, the identifier of the second network device, and the first resource, where the first resource is the second data resources used.
  • the terminal device is enabled to know more accurately the HARQ process to be continued, the destination network device, and the transmission resource corresponding to the HARQ process.
  • the first data is uplink data
  • the second data includes data for performing retransmission processing on the first data
  • the first data is downlink data
  • the second data includes feedback information for the first data
  • the feedback information of the first data includes an acknowledgment message ACK or a negative acknowledgment NACK.
  • the first network device or the second network device is a satellite.
  • the method 100 will be described in detail below for different scenarios.
  • the handover between cells of the UE is actually a handover between satellites.
  • the satellites to be switched belong to the same constellation and are under the jurisdiction of the same AMF.
  • FIG. 6 is another schematic flowchart of the embodiment of the application.
  • 1 gNodeB#1 can be understood as a gNodeB, other content about "#" is explained here
  • satellite #1 and satellite #2 They form an Xn interface, belong to the same constellation, and are under the jurisdiction of the same AMF.
  • the source gNodeB#1 is the base station of the serving cell before the UE#1 performs the cell handover
  • the target gNodeB#1 is the base station of the target serving cell for the UE#1 to perform the cell handover.
  • UE#1 performs cell handover based on measurement control information #A.
  • Step a The source gNodeB#1 sends measurement control information #A to UE#1 through an RRC reconfiguration (RRC reconfiguration) message.
  • the measurement control information #A includes measurement objects (such as intra-frequency measurement, inter-frequency measurement, etc.), measurement configuration (such as objects that UE needs to measure, cell list, reporting method, measurement identifier, event parameters, etc.) and measurement gaps (GAP) configuration, etc.;
  • Step b UE#1 responds to the source gNodeB#1 through the RRC reconfiguration complete message
  • Step c UE#1 performs measurement according to the received measurement control information #A. After UE#1 measures the cell and determines that the conditions for triggering the measurement are met, it reports measurement report information #A1 to the source gNodeB#1, wherein the measurement report information #A1 includes information such as the signal quality of the measured cell;
  • Step d After receiving the measurement report information #A1, the source gNodeB#1 performs handover strategy and target cell (or frequency point) judgment according to the measurement report information #A1.
  • Step e The source gNodeB#1 sends handover request (handover request) information to the target gNodeB#1 where the selected target cell #1 is located through the Xn link, and initiates a handover request.
  • handover request handover request
  • Step f After receiving the handover request message, the target gNodeB#1 performs admission control, and allocates the UE#1 instance and transmission resources after allowing the admission.
  • Step g The target gNodeB#1 replies a handover request acknowledge (handover request acknowledge) message to the source gNodeB#1 to allow switching in. If some protocol data unit (protocol data unit, PDU) sessions (session) fail to switch in, the failed PDU session list needs to be carried in the switch request confirmation message;
  • protocol data unit protocol data unit
  • Step h The source gNodeB#1 sends an RRC reconfiguration message to UE#1, requesting UE#1 to perform handover to the target cell #1, wherein the RRC reconfiguration message may include the ID of the RRC reconfiguration target cell (RRCReconfiguration target cell ID) , new cell radio network temporary identity (new C-RNTI), security algorithm (security algorithm) and other information;
  • the RRC reconfiguration message may include the ID of the RRC reconfiguration target cell (RRCReconfiguration target cell ID) , new cell radio network temporary identity (new C-RNTI), security algorithm (security algorithm) and other information;
  • Step i The source gNodeB#1 sends the SN number of the PDCP to the target gNodeB#1 through the service node status transfer (SNstatus transfer) signaling, after which, the cached data is transmitted through the uplink (uplink) ( buffered data) and new data for user plane function (UPF).
  • uplink uplink
  • UPF new data for user plane function
  • the source gNodeB#1 sends information #B
  • the target gNodeB#1 receives information #B.
  • the information #B is used to indicate the unfinished uplink HARQ process between the source gNodeB#1 and the UE#1, and the information #B may include one or more of the following information:
  • the buffered data of all current unfinished uplink HARQ processes including at least one of the data that has been received by the source gNodeB#1 corresponding to each unfinished uplink HARQ process, and the data that has been decoded by the source gNodeB#1, exemplary Yes, the "unfinished uplink HARQ process" here refers to UE#1 sending uplink data to source gNodeB#1, but source gNodeB#1 has not fed back ACK or NACK for the uplink data, or fed back NACK, However, the retransmission data from UE#1 has not been received yet.
  • the uplink HARQ process under this condition is "unfinished uplink HARQ process", or the source gNodeB#1 feeds back NACK for the uplink data, and UE#1 needs to perform uplink data retransmission;
  • the source gNodeB#1 sends information #B so that the target gNodeB#1 can grasp the status and information of all current unfinished uplink HARQ processes, and has the ability to take over the current HARQ process.
  • UE#1 establishes a connection with the target gNodeB#1.
  • Step a UE#1 initiates a non-contention random access in the target cell where the target gNodeB#1 is located, and sends a message 1 (message1, MSG1), and the message 1 includes a random access preamble (preamble) sequence;
  • Step b The target gNodeB#1 makes a random access response and sends a message 2 (message2, MSG2);
  • Step c UE#1 sends the RRC reconfiguration complete message to the target gNodeB#1, and the air interface handover of UE#1 to the target cell #1 is completed.
  • step #A UE#1 no longer sends uplink data to the source gNodeB#1, which means that UE#1 interrupts the transmission of uplink retransmission data of the unfinished uplink HARQ process, or The transmission of the feedback data (ACK or NACK) of the unfinished downlink HARQ process is interrupted, or the transmission of the data of the new uplink HARQ process is interrupted.
  • ACK or NACK feedback data
  • the uplink data #A includes the uplink retransmission data of the unfinished uplink HARQ process, and/or the uplink retransmission data of the unfinished downlink HARQ process Feedback data (ACK or NACK).
  • the uplink data #A may also include uplink data of a new HARQ process.
  • the source gNodeB#1 After the source gNodeB#1 sends the RRC reconfiguration message to the UE#1 in step h of S210, it sends information #Bg to the target gNodeB#1 after a period of time #A, and starts sending information #Bg1 to the target gNodeB#1 periodically , Information #Bg2..., until the source gNodeB#1 receives the end marker (end marker) information sent by AMF#1.
  • information #Bg, information #Bg1, information #Bg2... are information #B updated according to uplink data #A sent by UE#1 in period #A, information #Bg, information #Bg1, information #Bg2... can The data corresponding to the updated HARQ process may be included, and the data corresponding to the unupdated HARQ process may also be included.
  • the duration #A may be predefined.
  • the value of duration #A may be (2*RTT1–0.5*RTT2), where RTT1 is the round-trip delay of signal transmission between UE#1 and source gNodeB#1 or target gNodeB#1 , RTT2 is the round-trip time delay of signal transmission between the source gNodeB#1 and the target gNodeB#1.
  • the value of the duration #A may also be greater than (2*RTT1-0.5*RTT2), for example, when UE#1 or the target gNodeB#1 has a decoding error in the period #A.
  • the value of RTT1 is 540ms.
  • the value of RTT2 is 13.2ms (in the method 200, there is inter-satellite communication between the source gNodeB#1 and the target gNodeB#1).
  • the length of the above period may be predefined.
  • the length of the period above may be n times (0.5*RTT1), where n is an integer greater than 0.
  • the above solution solves the problem that source gNodeB#1 cannot communicate with UE#
  • the status of the updated HARQ process between 1 is updated to the target gNodeB#1 in time.
  • the target gNodeB#1 sends the information #C
  • the UE#1 receives the information #C.
  • information #C includes at least one of the following information:
  • Information #C1 used to indicate whether all current uplink HARQ processes of UE#1 need to be retransmitted.
  • information #C1 may include the ID of the uplink HARQ process that needs to be retransmitted and NACK data, or does not need to be retransmitted It should be understood that the uplink HARQ process that needs to be retransmitted or the uplink HARQ process that does not need to be retransmitted here is included in all the above-mentioned unfinished uplink HARQ processes;
  • Information #C1a is used to indicate that UE#1 needs to retransmit the time-frequency resource occupied by the uplink data corresponding to the uplink HARQ process and the object to be sent is the target gNodeB#1.
  • information #C1a may include The ID of the uploaded uplink HARQ process, the corresponding time-frequency resource and the identification of the target gNodeB#1;
  • Target Cell #1 allocated by target gNodeB #1 to UE #1, which can be used for new data transmission or new HARQ process between target gNodeB #1 and UE #1 Transmission of HARQ data.
  • UE#1 After receiving the information #C, UE#1 will respond to the HARQ operation according to the instruction of the information #C sent by the target gNodeB#1 firstly. For example, for the unfinished uplink HARQ process #1, UE#1 can retransmit the uplink data of the uplink HARQ process #1 to the source gNodeB#1 on the time-frequency resource #1, or send the uplink data of the uplink HARQ process #1 to the target gNodeB#1 retransmits the uplink data of uplink HARQ process #1 on time-frequency resource #2, then UE#1 will preferentially select the latter scheme, that is, perform uplink to the target gNodeB#1 on time-frequency resource #2 Retransmission of uplink data of HARQ process #1.
  • the information #C may be included in downlink control information (downlink control information, DCI) and carried in RRC signaling.
  • DCI downlink control information
  • UE#1 sends response information #D according to information #C.
  • the response information #D includes the ID of the uplink HARQ process and corresponding ACK or NACK data.
  • the target gNodeB#1 sends the information #E, and the AMF#1 receives the information #E.
  • information #E may be a path switch request (path switch request) message.
  • the target gNodeB#1 sends a path switch request message to AMF#1 to notify UE#1 that the serving cell has been changed.
  • the path switch request message carries the target cell identifier, List of converted PDU sessions.
  • the core network updates the downlink general packet radio service tunneling protocol (GPRStunneling protocol)-U data plane, and modifies the GTP-U address on the base station side to the address of the target gNodeB#1;
  • GPRStunneling protocol downlink general packet radio service tunneling protocol
  • the target gNodeB#1 sends the information #F, and the UE#1 receives the information #F.
  • the target gNodeB#1 sends information #F to the UE#1, where the information #F is used to instruct the UE#1 to perform uplink data retransmission processing with the target gNodeB#1.
  • information #F may include at least one of the following information:
  • the ID of the uplink HARQ process that needs to perform the retransmission processing of the uplink data the identifier of the target gNodeB#1, and the time-frequency resources occupied by the retransmission processing of the uplink data.
  • Information #F can be used to further ensure the continuity of the HARQ process when UE#1 switches to target cell #1, that is, if UE#1 sends uplink retransmission data or downlink data feedback data to target cell #1 according to information #C If it fails (since in S250, UE#1 sent a response message to target cell #1, so target cell #1 knows which HARQ processes have been switched successfully and which HARQ processes have not been switched successfully), you can also continue to proceed according to information #F The completed uplink HARQ process, so as to achieve the purpose of ensuring the continuity of the HARQ process.
  • the source gNodeB#1 releases the connection with UE#1.
  • Step a AMF#1 replies a path switch request acknowledge (path switch request acknowledge) message to the target gNodeB#1. If AMF#1 indicates in the path switching request confirmation message that the core network fails to establish the PDU session, the target gNodeB#1 deletes the failed PDU session;
  • Step b The target gNodeB#1 sends a UE context release (UE context release) message to the source gNodeB#1, and the source gNodeB#1 releases the connection with UE#1 after receiving the message;
  • UE context release UE context release
  • the source gNodeB#1 can be processed in the following two ways:
  • the new uplink HARQ process is continued, and uplink data is fed back to UE#1 until the new uplink HARQ process is ended.
  • the target gNodeB#1 can send the relevant data of the HARQ process that needs to reply NACK or the state of the updated HARQ process to the target gNodeB#1. For details, please refer to the above information #B, which will not be repeated here. If it is a HARQ process that needs to reply ACK, then the source It is enough for gNodeB#1 to send the ACK data to UE#1. After receiving the data, the target gNodeB#1 can send to UE#1 whether the data needs to be retransmitted and if it needs to be retransmitted, the time-frequency resource occupied by the data, see information #C for details.
  • the target gNodeB#1 sends the measurement control information of the target cell#1 to UE#1 through an RRC reconfiguration (RRCReconfiguration) message, and UE#1 receives the new measurement control information sent by the target gNodeB#1 After measuring the control information, reply an RRC reconfiguration complete (RRCReconfigurationComplete) message.
  • RRC reconfiguration RRC reconfiguration Complete
  • This application also considers how to switch the downlink HARQ process in the scenario of method 200, as shown in method 300, wherein, for the description of source gNodeB#1, target gNodeB#1, and AMF#1, refer to the description in method 200, I won't repeat them here.
  • UE#1 performs cell handover based on measurement control information #A.
  • UE#1 copies the data of the unfinished HARQ process in the first medium access control layer MAC entity to the second MAC entity, where the first MAC entity is UE#1 and the source The MAC entity between gNodeB#1, the second MAC entity is the MAC entity between UE#1 and target gNodeB#1.
  • the target gNodeB#1 sends the information #E, and the AMF#1 receives the information #E.
  • the source gNodeB#1 releases the connection with UE#1.
  • Step a AMF#1 replies a path switch request acknowledge (path switch request acknowledge) message to the target gNodeB#1. If AMF#1 indicates in the path switching request confirmation message that the core network fails to establish the PDU session, the target gNodeB#1 deletes the failed PDU session;
  • Step b The target gNodeB#1 sends a UE context release (UE context release) message to the source gNodeB#1, and the source gNodeB#1 releases the connection with UE#1 after receiving the message;
  • UE context release UE context release
  • the source gNodeB#1 still has unfinished downlink data to be sent to UE#1, before the source gNodeB#1 releases the connection with UE#1, it can continue to send the unsent downlink data. Completed downlink data, but no new downlink data will be sent.
  • the source gNodeB#1 sends information #B1 to the target gNodeB#1.
  • the information #B1 is used to indicate the original downlink HARQ process information of the unfinished downlink HARQ process between the source gNodeB#1 and the UE#1, and the information #B1 may include one or more of the following information:
  • the redundancy version data corresponding to each unfinished downlink HARQ process, and the NACK data sent by UE#1 corresponding to each unfinished downlink HARQ process refers to the source The downlink data sent by gNodeB#1 to UE#1, but UE#1 has not fed back ACK or NACK for the downlink data, the downlink HARQ process under this condition is "unfinished downlink HARQ process", or UE#1 NACK is fed back to the downlink data, and the source gNodeB#1 is required to retransmit the downlink data;
  • Redundancy version numbers of all current unfinished downlink HARQ processes including the status of the redundancy versions of each unfinished downlink HARQ process, such as the number of times the redundancy versions of the unfinished downlink HARQ processes have been sent.
  • the source gNodeB#1 if the source gNodeB#1 receives the data from the UPF or there is unsent downlink data in the cache of the source gNodeB#1, then the source gNodeB#1 needs to send the downlink data to the target For gNodeB#1, the downlink data may be included in information #B1.
  • the source gNodeB#1 sends information #B1 so that the target gNodeB#1 can grasp the status and information of all current unfinished downlink HARQ processes, and has the ability to take over the current HARQ process.
  • the target gNodeB#1 sends the information #C3, and the UE#1 receives the information #C3.
  • the information #C3 is used to indicate that UE#1 sends the feedback data of all current unfinished downlink HARQ processes to the target gNodeB#1 and the time-frequency resource occupied by the feedback data.
  • information #C3 may include at least one of the following information:
  • the ID of the currently unfinished downlink HARQ process The ID of the currently unfinished downlink HARQ process, the time-frequency resource occupied by the feedback data corresponding to the ID of the currently unfinished downlink HARQ process, and the identifier of the target gNodeB#1.
  • the information #C3 may also be the redundant version data of the downlink data for which the target gNodeB#1 feeds back NACK data for UE#1 (that is, the downlink data for retransmission processing), and the corresponding downlink ID of the HARQ process.
  • UE#1 After receiving the information #C3, UE#1 will respond to the HARQ operation according to the indication of the information #C3 sent by the target gNodeB#1 firstly.
  • the feedback data of UE#1 for the unfinished downlink HARQ process #1 can be sent to the source gNodeB#1 on the time-frequency resource #1, or can be sent to the target gNodeB#1 on the time-frequency resource according to the instruction of information #C3
  • UE#1 will preferentially select the latter solution, that is, send feedback data to target gNodeB#1 on time-frequency resource #2.
  • UE#1 feeds back information #C3 sent by target gNodeB#1 through response information #D1.
  • the response information #D1 includes the ID of the downlink HARQ process and/or corresponding ACK or NACK data.
  • the present application also provides method 400, wherein, for the description of source gNodeB#1, target gNodeB#1, and AMF#1, refer to the description in method 200, which will not be repeated here repeat.
  • the source gNodeB#1 sends information #B1 to the target gNodeB#1.
  • UE#1 establishes a connection with the target gNodeB#1.
  • step h of S410 that is, after the source gNodeB#1 sends the RRC reconfiguration message
  • step c of S430 that is, the target gNodeB#1
  • the source gNodeB#1 no longer sends downlink data to UE#1, which means that the source gNodeB#1 interrupts the unfinished downlink HARQ process or interrupt the transmission of feedback data (ACK or NACK) of an unfinished uplink HARQ process, or interrupt the transmission of data of a new downlink HARQ process.
  • ACK or NACK feedback data
  • the source gNodeB#1 can continue to send downlink data #A to UE#1, the downlink data #A includes the downlink retransmission data of the unfinished downlink HARQ process, and/or the downlink retransmission data of the unfinished uplink HARQ process Feedback data (ACK or NACK).
  • ACK or NACK Feedback data
  • the downlink data #A may also include data of a new downlink HARQ process, for example, downlink user plane data that UPF #1 has allocated to the source gNodeB #1.
  • the source gNodeB#1 After the source gNodeB#1 sends the RRC reconfiguration message to the UE#1 in step h of S210, it sends information #B1g to the target gNodeB#1 after a period of time #A, and starts sending information #B1g1 to the target gNodeB#1 periodically , Information #B1g2..., until the source gNodeB#1 receives the end marker (end marker) information sent by AMF#1.
  • information #B1g, information #B1g1, information #B1g2... are information #B1 updated according to downlink data #A sent by UE#1 in period #B, information #B1g, information #B1g1, information #B1g2... can The data corresponding to the updated HARQ process may be included, and the data corresponding to the unupdated HARQ process may also be included.
  • the above solution solves the problem that source gNodeB#1 cannot communicate with UE#
  • the status of the updated HARQ process between 1 is updated to the target gNodeB#1 in time.
  • the target gNodeB#1 sends the information #C3, and the UE#1 receives the information #C3.
  • the source gNodeB#1 after the source gNodeB#1 sends the message #B1 to the target gNodeB#1 and before the target gNodeB#1 sends the message #C3, if the source gNodeB#1 sends a new message to UE#1 If the downlink data or new feedback data from UE#1 is received, the source gNodeB#1 needs to synchronize the generated new state with the target gNodeB#1 again.
  • the source gNodeB#1 needs to send the data of all HARQ processes corresponding to the new downlink data and the IDs of the corresponding HARQ processes to the target gNodeB#1, and for example, the source gNodeB#1 needs to receive the The new feedback data and the ID of the corresponding HARQ process are sent to the target gNodeB#1, so that the target gNodeB#1 can grasp the latest unfinished HARQ process data.
  • the target gNodeB#1 After the target gNodeB#1 receives the new HARQ process data sent by the source gNodeB#1, it can include the control information corresponding to the new HARQ process data in information #C3 and send it to UE#1. For details, refer to information #C3 , which will not be repeated here.
  • response information #D1 can refer to the method S370, which will not be repeated here.
  • the target gNodeB#1 sends the information #E, and the AMF#1 receives the information #E.
  • information #E may be a path switch request (path switch request) message.
  • the target gNodeB#1 sends a path switch request message to AMF#1 to notify UE#1 that the serving cell has been changed.
  • the path switch request message carries the target cell identifier, List of converted PDU sessions.
  • the core network updates the downlink general packet radio service tunneling protocol (GPRStunneling protocol)-U data plane, and modifies the GTP-U address on the base station side to the address of the target gNodeB#1;
  • GPRStunneling protocol downlink general packet radio service tunneling protocol
  • the target gNodeB#1 sends the information #F1, and the UE#1 receives the information #F1.
  • the target gNodeB#1 sends information #F1 to UE#1, wherein the information #F1 is used to instruct UE#1 to perform downlink data feedback with the target gNodeB#1.
  • information #F1 may include at least one of the following information:
  • the information #F1 can be used to further ensure the continuity of the HARQ process when UE#1 switches to the target cell #1, that is, if some information of the information #C received by UE#1 fails (because in S450, UE#1 sent the target cell Cell #1 sends a response message, so the target cell #1 knows which HARQ processes have switched successfully and which HARQ processes have not switched successfully), and can also continue the unfinished downlink HARQ process by sending information #F1 to ensure the continuity of the HARQ process the goal of.
  • the source gNodeB#1 releases the connection with UE#1.
  • the source gNodeB#1 if it has unfinished downlink data, it can continue to send the downlink data. After sending the downlink data, a new HARQ process is formed, but no new HARQ process is sent. The data. At this time, the relevant data of the new HARQ process needs to be sent to the target gNodeB#1 again, and the specific content of the relevant data of the new HARQ process can be referred to information #B1.
  • the source gNodeB#1 receives the data from the UPF or there is unsent downlink data in the cache of the source gNodeB#1, then the source gNodeB#1 needs to send the downlink data to the target gNodeB#1,
  • the downlink data may be included in information #B1.
  • the target gNodeB#1 sends the measurement control information of the target cell#1 to UE#1 through an RRC reconfiguration (RRCReconfiguration) message, and UE#1 receives the new measurement control information sent by the target gNodeB#1 After measuring the control information, reply with an RRC reconfiguration complete message (RRCReconfigurationComplete).
  • RRCReconfiguration RRC reconfiguration
  • the HARQ process performed by UE#1 can be continuous, and the delay of satellite communication can be enhanced advantage, gaining soft-combining coding gain.
  • the embodiment of the present application also considers that the coverage area of each satellite is a cell, and the user's cell handover is actually a handover between satellites.
  • the two satellites before and after the handover are connected to the two core networks through the NG interface, and the two core networks are under the jurisdiction of the same AMF.
  • FIG. 7 is another schematic flowchart of the embodiment of the application.
  • 1 belongs to the coverage area of satellite #1 (not shown in Figure 7) (or called source gNodeB #1 belongs to the coverage area of source cell #1), and target gNodeB #1 belongs to satellite #2 (not shown in Figure 7)
  • the coverage area of the target gNodeB#1 (or the coverage area of the target cell #1 belonging to the target gNodeB#1), the Xn interface is formed between the satellite #1 and the core network #1 (not shown in Figure 7), and the satellite #2 and the core network # 2 constitute an Xn interface, and core network #1 and core network #2 (not shown in FIG.
  • the source gNodeB#1 is a base station under the coverage of the serving cell before the UE#1 performs the cell handover
  • the target gNodeB#1 is the base station under the coverage of the target serving cell for the UE#1 to perform the cell handover.
  • UE#1 performs cell handover based on measurement control information #A.
  • Step a The source gNodeB#1 sends measurement control information #A to UE#1 through an RRC reconfiguration (RRCReconfiguration) message.
  • RRC reconfiguration RRCReconfiguration
  • Step b UE#1 responds to the source gNodeB#1 through an RRC reconfiguration complete (ReconfigurationComplete) message.
  • Step c UE#1 performs measurement according to the received measurement control information #A. After UE#1 measures the cell and determines that the conditions for triggering the measurement are met, it reports measurement report information #A1 to the source gNodeB#1, wherein the measurement report information #A1 includes information such as the signal quality of the measured cell;
  • Step d After receiving the measurement report information #A1, the source gNodeB#1 performs handover strategy and target cell (or frequency point) judgment according to the measurement report information #A1.
  • Step e The source gNodeB#1 sends a handover request (handover required) message to AMF#1 through the NG link to initiate a handover request.
  • the message includes the ID of the target gNodeB#1, the PDU session list for performing data forwarding, etc.;
  • Step f AMF#1 sends a handover request message to the target gNodeB#1 where the specified target cell #1 is located, and initiates a handover request, and the target gNodeB#1 according to the trace ID (TraceID) and subscriber profile identity (subscriber profile identity) in the message, SPID) identifies UE#1;
  • TraceID trace ID
  • SPID subscriber profile identity
  • Step g After receiving the handover request, the target gNodeB#1 performs admission control, and allocates UE#1 instances and transmission resources after admission is allowed;
  • Step h The target gNodeB#1 replies a handover required acknowledge (handover required acknowledge) message to AMF#1, allowing the handover in. If some PDU sessions fail to be switched in, the message needs to carry a list of failed PDU sessions;
  • Step i AMF#1 sends a handover command (handover command) message to the source gNodeB#1, which contains the address of the target gNodeB#1 and a list of tunnel endpoint identifiers (TEID) for forwarding, including the list that needs to be released bearer list;
  • handover command handover command
  • TEID tunnel endpoint identifiers
  • Step j The source gNodeB#1 sends an RRC reconfiguration message to the UE, requesting the UE to perform handover to the target cell#1;
  • Step k The source gNodeB#1 sends the SN number of PDCP to AMF#1 through uplink RAN status transfer (uplink RAN status transfer);
  • Step 1 AMF#1 sends the SN number of PDCP to the target gNodeB#1 through the downlink RAN status transfer (downlink RAN status transfer) message, after which, the corresponding buffer data and UPF data transmission will be carried out;
  • the source gNodeB#1 sends information #B to the target gNodeB#1 through the AMF#1.
  • the information #B is used to indicate the unfinished uplink HARQ process between the source gNodeB#1 and the UE#1, and the content of the information #B can refer to the description in the method S220, and will not be repeated here.
  • the source gNodeB#1 sends information #B so that the target gNodeB#1 can grasp the status and information of all current unfinished uplink HARQ processes, and has the ability to take over the current HARQ process.
  • UE#1 establishes a connection with the target gNodeB#1.
  • Step a UE#1 initiates a non-contention random access in the target cell #1 where the target gNodeB#1 is located, and sends a message 1 (message1, MSG1), and the message 1 includes a random access preamble (preamble) sequence;
  • Step b The target gNodeB#1 makes a random access response and sends a message 2 (message2, MSG2);
  • Step c UE#1 sends the RRC reconfiguration complete message to the target gNodeB#1, and the air interface handover of UE#1 to the target cell #1 is completed.
  • step j of S510 that is, UE#1 successfully decodes the RRC reconfiguration message sent by source gNodeB#1
  • step c of S530 that is, target gNodeB#1 successfully decodes the RRC reconfiguration completion message
  • UE#1 no longer sends uplink data to the source gNodeB#1, which means that UE#1 interrupts the transmission of the uplink retransmission data of the unfinished uplink HARQ process, or
  • the transmission of the feedback data (ACK or NACK) of the unfinished downlink HARQ process is interrupted, or the transmission of the new uplink HARQ process data is interrupted.
  • the uplink data #A includes the uplink retransmission data of the unfinished uplink HARQ process, and/or the uplink retransmission data of the unfinished downlink HARQ process Feedback data (ACK or NACK).
  • the uplink data #A may also include data of a new uplink HARQ process.
  • the source gNodeB#1 After the source gNodeB#1 sends the RRC reconfiguration message to the UE#1 in step j of S510, it sends information #Bg to the target gNodeB#1 after a duration #A1, and starts to periodically send information #Bg1 to the target gNodeB#1 , Information #Bg2..., until the source gNodeB#1 receives the end marker (end marker) information sent by AMF#1.
  • information #Bg, information #Bg1, information #Bg2... are information #B updated according to the uplink data #A sent by UE#1 in period #A1, information #Bg, information #Bg1, information #Bg2... can
  • the data corresponding to the updated HARQ process may be included, and the data corresponding to the unupdated HARQ process may also be included.
  • the duration #A1 may be predefined.
  • the value of duration #A1 may be (2*RTT3-RTT4), where RTT3 is the round-trip delay of signal transmission between UE#1 and source gNodeB#1 or target gNodeB#1, and RTT4 is the sum of the delay of the source gNodeB#1 sending the signal to the core network and the delay of the core network sending the signal to the target gNodeB#1 (in method 500, the data transmission between the source gNodeB#1 and the target gNodeB#1 needs to pass through the core network side (AMF#1)).
  • RTT3 is the round-trip delay of signal transmission between UE#1 and source gNodeB#1 or target gNodeB#1
  • RTT4 is the sum of the delay of the source gNodeB#1 sending the signal to the core network and the delay of the core network sending the signal to the target gNodeB#1 (in method 500, the data transmission between the source gNodeB#1 and the target gNode
  • the value of the duration #A1 may also be greater than (2*RTT3-RTT4), for example, when UE#1 or the target gNodeB#1 has a decoding error within the period #A1.
  • the value of RTT1 is 540ms.
  • the length of the above period may be predefined.
  • the length of the above period may be n times (0.5*RTT3), where n is an integer greater than 0.
  • the above solution solves the problem that source gNodeB#1 cannot communicate with UE#
  • the status of the updated HARQ process between 1 is updated to the target gNodeB#1 in time.
  • the target gNodeB#1 sends the information #C, and the UE#1 receives the information #C.
  • UE#1 After receiving the information #C, UE#1 will respond to the HARQ operation according to the instruction of the information #C sent by the target gNodeB#1 firstly. For example, UE#1 can retransmit the uplink data of the uplink HARQ process #1 to the source gNodeB#1 on the time-frequency resource #1 for the unfinished uplink HARQ process #1, or can send the target gNodeB#1 retransmits the uplink data of uplink HARQ process #1 on time-frequency resource #2, then UE#1 will preferentially select the latter scheme, that is, perform uplink to the target gNodeB#1 on time-frequency resource #2 Retransmission of uplink data of HARQ process #1.
  • the information #C may be downlink control information (downlink control information, DCI), carried in the RRC signaling.
  • DCI downlink control information
  • UE#1 sends response information #D according to information #C, wherein, for content of response information #D, refer to method S250, which will not be repeated here.
  • the target gNodeB#1 sends the information #E1, and the AMF#1 receives the information #E1.
  • the information #E1 may be a handover notify (handover notify) message, which is used to notify the AMF#1 that the UE#1 has accessed the target cell #1, and the NG-based handover has been completed.
  • handover notify a handover notify (handover notify) message
  • the target gNodeB#1 sends the information #F, and the UE#1 receives the information #F.
  • the target gNodeB#1 sends information #F to the UE#1, where the information #F is used to instruct the UE#1 to perform uplink data retransmission processing with the target gNodeB#1.
  • information #F refers to method 200, which will not be repeated here.
  • the source gNodeB#1 releases the connection with UE#1.
  • Step a AMF#1 sends a UE context release command (UE context release command) message to the source gNodeB#1, and the source gNodeB#1 releases the connection with UE#1 after receiving the message;
  • UE context release command UE context release command
  • the target gNodeB#1 sends the measurement control information of the new cell to UE#1 through an RRC reconfiguration (RRCReconfiguration) message, and UE#1 receives the new measurement control information sent by the target gNodeB#1 After receiving the information, reply the RRC reconfiguration complete message (RRCReconfigurationComplete).
  • RRC reconfiguration RRC reconfiguration
  • This application also considers how to switch the downlink HARQ process in the scenario of method 500, such as method 600, wherein, for the description of source gNodeB#1, target gNodeB#1, and AMF#1, refer to the description in method 500, here No longer.
  • UE#1 performs cell handover based on measurement control information #A.
  • UE#1 establishes a connection with the target gNodeB#1.
  • UE#1 copies the data of the unfinished HARQ process in the first MAC entity to the second MAC entity, where the first MAC entity is between UE#1 and the source gNodeB#1
  • the MAC entity between UE#1 and the target gNodeB#1 is the second MAC entity.
  • the target gNodeB#1 sends the information #E1, and the AMF#1 receives the information #E1.
  • the source gNodeB#1 releases the connection with UE#1.
  • Step a AMF#1 sends a UE context release command (UE context release command) message to the source gNodeB#1, and the source gNodeB#1 releases the connection with UE#1 after receiving the message;
  • UE context release command UE context release command
  • the source gNodeB#1 still has unfinished downlink data to be sent to UE#1, before the source gNodeB#1 releases the connection with UE#1, it can continue to send the unsent downlink data. Completed downlink data, but no new downlink data will be sent.
  • the source gNodeB#1 sends information #B1 to the target gNodeB#1.
  • the information #B1 is used to indicate the unfinished downlink HARQ process between the source gNodeB#1 and the UE#1, and the content of the information #B1 can refer to the method S350, which will not be repeated here.
  • the source gNodeB#1 if the source gNodeB#1 receives the data from the UPF or there is unsent downlink data in the cache of the source gNodeB#1, then the source gNodeB#1 needs to send the downlink data to the target For gNodeB#1, the downlink data may be included in information #B1.
  • the source gNodeB#1 sends information #B1 so that the target gNodeB#1 can grasp the status and information of all current unfinished downlink HARQ processes, and has the ability to take over the current HARQ process.
  • the target gNodeB#1 sends the information #C3, and the UE#1 receives the information #C3.
  • the information #C3 is used to indicate that the UE#1 sends the feedback data of all current unfinished downlink HARQ processes to the target gNodeB#1 and the time-frequency resources occupied by the feedback data.
  • information #C3 refer to method S360, which will not be repeated here.
  • UE#1 After receiving the information #C3, UE#1 will respond to the HARQ operation according to the indication of the information #C3 sent by the target gNodeB#1 firstly.
  • the feedback data of UE#1 for the unfinished downlink HARQ process #1 can be sent to the source gNodeB#1 on the time-frequency resource #1, or can be sent to the target gNodeB#1 on the time-frequency resource according to the instruction of information #C3
  • UE#1 will preferentially select the latter solution, that is, send feedback data to target gNodeB#1 on time-frequency resource #2.
  • UE#1 feeds back information #C3 sent by target gNodeB#1 through response information #D1.
  • the response information #D1 includes the ID of the downlink HARQ process and/or corresponding ACK or NACK data.
  • method 500 for downlink HARQ process switching, the present application also provides method 700.
  • source gNodeB#1, target gNodeB#1, and AMF#1 refer to the description in method 500, which will not be repeated here.
  • the source gNodeB#1 sends information #B1 to the target gNodeB#1.
  • UE#1 establishes a connection with the target gNodeB#1.
  • the source gNodeB#1 no longer sends downlink data to UE#1, which means that the source gNodeB#1 interrupts the transmission of the downlink retransmission data of the unfinished downlink HARQ process, or interrupts the unfinished uplink
  • ACK or NACK feedback data
  • the source gNodeB#1 can continue to send downlink data #A to UE#1, the downlink data #A includes the downlink retransmission data of the unfinished downlink HARQ process, and/or the downlink retransmission data of the unfinished uplink HARQ process Feedback data (ACK or NACK).
  • ACK or NACK Feedback data
  • the downlink data #A may also include data of a new downlink HARQ process, for example, downlink user plane data that UPF #1 has allocated to the source gNodeB #1.
  • the source gNodeB#1 After the source gNodeB#1 sends the RRC reconfiguration message to the UE#1 in step j of S510, it sends information #Bg to the target gNodeB#1 after a duration of #A1, and starts sending information #Bg1 to the target gNodeB#1 periodically , Information #Bg2..., until the source gNodeB#1 receives the end marker (end marker) information sent by AMF#1.
  • information #Bg, information #Bg1, information #Bg2... are information #B updated according to the uplink data #A sent by UE#1 in period #A1, information #Bg, information #Bg1, information #Bg2... can It includes data corresponding to an updated HARQ process, and may also include data corresponding to an unupdated HARQ process.
  • the above solution solves the problem that source gNodeB#1 cannot communicate with UE#
  • the status of the updated HARQ process between 1 is updated to the target gNodeB#1 in time.
  • the target gNodeB#1 sends the information #C3, and the UE#1 receives the information #C3.
  • the source gNodeB#1 after the source gNodeB#1 sends the message #B1 to the target gNodeB#1 and before the target gNodeB#1 sends the message #C3, if the source gNodeB#1 sends a new message to UE#1 If the downlink data or new feedback data from UE#1 is received, the source gNodeB#1 needs to synchronize the generated new state with the target gNodeB#1.
  • the source gNodeB#1 needs to send the data of all HARQ processes corresponding to the new downlink data and the IDs of the corresponding HARQ processes to the target gNodeB#1, and for example, the source gNodeB#1 needs to receive the The new feedback data and the ID of the corresponding HARQ process are sent to the target gNodeB#1, so that the target gNodeB#1 can grasp the latest unfinished HARQ process data.
  • the target gNodeB#1 After the target gNodeB#1 receives the new HARQ process data sent by the source gNodeB#1, it can include the control information corresponding to the new HARQ process data in information #C3 and send it to UE#1. For details, refer to information #C3 , which will not be repeated here.
  • response information #D1 can refer to the method S370, which will not be repeated here.
  • the target gNodeB#1 sends the information #E1, and the AMF#1 receives the information #E1.
  • the target gNodeB#1 sends the information #F1, and the UE#1 receives the information #F1.
  • the information #F1 is used to instruct UE#1 to perform downlink data feedback with the target gNodeB#1.
  • information #F1 refers to the method S470, which will not be repeated here.
  • the source gNodeB#1 releases the connection with UE#1.
  • the source gNodeB#1 if it has unfinished downlink data, it can continue to send the downlink data. After sending the downlink data, a new HARQ process is formed, but no new HARQ process is sent. The data. At this time, the relevant data of the new HARQ process needs to be sent to the target gNodeB#1 again, and the specific content of the relevant data of the new HARQ process can be referred to information #B1.
  • the source gNodeB#1 receives the data from the UPF or there is unsent downlink data in the cache of the source gNodeB#1, then the source gNodeB#1 needs to send the downlink data to the target gNodeB#1,
  • the downlink data may be included in information #B1.
  • the target gNodeB#1 sends the measurement control information of the new cell to UE#1 through an RRC reconfiguration (RRCReconfiguration) message, and UE#1 receives the new measurement control information sent by the target gNodeB#1 After receiving the information, reply the RRC reconfiguration complete message (RRCReconfigurationComplete).
  • RRC reconfiguration RRC reconfiguration
  • the embodiment of this application also considers that the cells before and after the handover of the UE belong to the same base station (gNodeB-DU), and the cells before and after the handover belong to the same gNodeB-DU, and the cells before and after the handover belong to the same gNodeB-CU.
  • a The multiple beams of a satellite are divided into different cells, and the inter-cell handover of users is actually the handover between different cells served by the same satellite.
  • FIG. 8 is another schematic flow chart of the embodiment of the present application.
  • Cell #1 belongs to gNodeB-DU#1 and is controlled by the same gNodeB-CU.
  • UE#1 performs cell handover based on measurement control information #A.
  • Step a gNodeB-CU#1 sends measurement control information #A to UE#1 through an RRC reconfiguration (RRC reconfiguration) message, wherein, the content of measurement control information #A refers to method 200;
  • Step b UE#1 replies the RRC reconfiguration complete (RRC reconfiguration complete) message to gNodeB-CU#1;
  • Step c UE#1 performs measurement according to the measurement control information #A, and reports the measurement report of the neighboring cell to gNodeB-CU#1;
  • Step d According to the physical cell identifier (PCI) PCI carried in the measurement report, gNodeB-CU#1 determines that the target cell #1 and the source cell #1 belong to the same base station, and starts the intra-site handover process, and the target cell #1 makes an admission decision based on the context of UE#1 in source cell #1;
  • PCI physical cell identifier
  • Step e gNodeB-CU#1 sends a UE context setup request (UE context setup request) message to gNodeB-DU#1, and applies to gNodeB-DU#1 for the resource of UE#1 as the target cell #1;
  • UE context setup request UE context setup request
  • Step f If gNodeB-DU#1 successfully allocates resources for UE#1, reply UE context setup response (UE context setup response) message to gNodeB-CU#1;
  • Step g gNodeB-CU#1 sends a UE context modification request (UE context modification request) message to gNodeB-DU#1, which is used to instruct gNodeB-DU#1 to send the instruction information to stop scheduling the L2 signaling of the source cell#1 ;
  • UE context modification request UE context modification request
  • Step h gNodeB-DU#1 replies UE context modification response (UE context modification response) message to gNodeB-CU#1;
  • the source cell #1 copies the information #B2 to the memory corresponding to the target cell #1, and both the source cell #1 and the target cell #1 are managed by gNodeB-DU#1.
  • the information #B2 is used to indicate the unfinished HARQ process between the source cell #1 and the UE #1,
  • information #B2 may include original downlink HARQ process information corresponding to each unfinished downlink HARQ process, for example, may include the following information one or more:
  • Redundancy version numbers of all currently unfinished downlink HARQ processes for example, versions of redundant data of unfinished downlink HARQ processes that have been sent.
  • information #B2 may include one or more of the following information:
  • Buffer data of all currently unfinished uplink HARQ processes including at least one of data that has been received by the source gNodeB#1 corresponding to each unfinished uplink HARQ process, and data that has been decoded by the source gNodeB#1;
  • the gNodeB-DU#1 retains the information #B2 so that the target cell #1 can grasp the status and information of all current HARQ processes, and has the ability to take over the current HARQ process.
  • Step a gNodeB-CU#1 sends an RRC reconfiguration message to UE#1, the message carries the target frequency point of the target cell #1, the PCI of the target cell #1 and the cell wireless network temporary identifier configured for UE#1 ( cellradio network temporary identity, C-RNTI) and dedicated random access preamble;
  • Step b UE#1 initiates a non-contention random access in the target cell#1, and sends a message 1 (message1, MSG1), where the message 1 includes a random access preamble sequence.
  • Step c gNodeB-DU#1 makes a random access response and sends message 2 (message2, MSG2);
  • Step d UE#1 sends RRC reconfiguration completion information to gNodeB-CU#1, and UE#1 accesses target cell #1.
  • step #A2 UE#1 no longer sends uplink data to source cell #1, which means that UE#1 interrupts the transmission of uplink retransmission data of the unfinished uplink HARQ process , or interrupt the transmission of the feedback data (ACK or NACK) of the unfinished downlink HARQ process, or interrupt the transmission of the data of the new uplink HARQ process.
  • UE#1 interrupts the transmission of uplink retransmission data of the unfinished uplink HARQ process , or interrupt the transmission of the feedback data (ACK or NACK) of the unfinished downlink HARQ process, or interrupt the transmission of the data of the new uplink HARQ process.
  • the uplink data #A includes the uplink retransmission data of the unfinished uplink HARQ process, and/or the uplink retransmission data of the unfinished downlink HARQ process Feedback data (ACK or NACK).
  • the uplink data #A may also include uplink data of a new HARQ process.
  • the application has designed the following scheme:
  • the source cell #1 copies the information #B2g to the target cell #1 after a period of time #A2, and starts periodically sending information to the target cell# 1 Send information #B2g1, information #B2g2... until the source cell #1 receives the UE context release command (UE context release command) from gNodeB-CU#1.
  • information #B2g, information #B2g1, information #B2g2... are information #B2 updated according to uplink data #A sent by UE#1 in period #A2, information #B2g, information #B2g1, information #B2g2... can The data corresponding to the updated HARQ process may be included, and the data corresponding to the unupdated HARQ process may also be included.
  • the duration #A2 may be predefined.
  • the value of duration #A2 may be (2*RTT5), where RTT5 is the round-trip delay of signal transmission between UE#1 and gNodeB-DU#1.
  • the value of RTT5 is 540ms.
  • the value of the duration #A2 may also be greater than (2*RTT5), for example, when UE#1 or the target cell #1 has a decoding error within the period #A2.
  • the length of the above period may be predefined.
  • the length of the above period may be n times (0.5*RTT5), where n is an integer greater than 0.
  • the above solution solves the problem that source cell #1 cannot communicate with UE#
  • the status of the updated HARQ process between 1 is updated to the target cell #1 in time.
  • step a of S830 that is, after gNodeB-CU#1 sends the RRC reconfiguration message
  • step d of S830 that is, gNodeB-CU#1 successfully decodes the RRC reconfiguration completion message
  • source cell #1 no longer sends downlink data to UE#1, which means that source cell #1 interrupts the transmission of downlink retransmission data of the unfinished downlink HARQ process, or interrupts the unfinished downlink HARQ process transmission of the feedback data (ACK or NACK) of the uplink HARQ process, or interrupt the transmission of new downlink HARQ process data.
  • ACK or NACK feedback data
  • the source cell #1 can continue to send downlink data #A to UE#1, the downlink data #A includes the downlink retransmission data of the unfinished downlink HARQ process, and/or the downlink retransmission data of the unfinished uplink HARQ process Feedback data (ACK or NACK).
  • the downlink data #A includes the downlink retransmission data of the unfinished downlink HARQ process, and/or the downlink retransmission data of the unfinished uplink HARQ process Feedback data (ACK or NACK).
  • the downlink data #A may also include downlink data of a new HARQ process, for example, downlink user plane data that UPF #1 has allocated to the source gNodeB #1.
  • the application has designed the following scheme:
  • the source cell #1 copies the information #B2g to the target cell #1 after a period of time #A2, and starts periodically sending information to the target cell# 1 Send information #B2g1, information #B2g2... until the source cell #1 receives the UE context release command (UE context release command) from gNodeB-CU#1.
  • information #B2g, information #B2g1, information #B2g2... are information #B2 updated according to uplink data #A sent by UE#1 in period #A2, information #B2g, information #B2g1, information #B2g2... can The data corresponding to the updated HARQ process may be included, and the data corresponding to the unupdated HARQ process may also be included.
  • the above solution solves the problem that source cell #1 cannot communicate with UE#
  • the status of the updated HARQ process between 1 is updated to the target cell #1 in time.
  • information #C4 includes at least one of the following information:
  • Information #C41 used to indicate whether all the current unfinished uplink HARQ processes of UE#1 need to be retransmitted.
  • the information #C41 may include the ID of the uplink HARQ process that needs to be retransmitted and NACK data, or does not need to be retransmitted It should be understood that the uplink HARQ process that needs to be retransmitted or the uplink HARQ process that does not need to be retransmitted here is included in all the above-mentioned unfinished uplink HARQ processes;
  • Information #C41a used to indicate at least one of the time-frequency resource occupied by the uplink data corresponding to the uplink HARQ process that UE#1 needs to retransmit, and the identity of gNodeB-DU#1.
  • the information #C41a can be Including the ID of the uplink HARQ process that needs to be retransmitted, the corresponding time-frequency resource and the identification of gNodeB-DU#1;
  • the information #C43 is used to instruct UE#1 to send feedback data of all current unfinished downlink HARQ processes to the target cell, and at least one of the time-frequency resources occupied by the feedback data.
  • information #C43 may include at least one of the following information:
  • the ID of the currently unfinished downlink HARQ process The ID of the currently unfinished downlink HARQ process, the time-frequency resource occupied by the feedback data corresponding to the ID of the currently unfinished downlink HARQ process, and the identifier of gNodeB-DU#1.
  • the information #C43 may also be the redundant version data of the downlink data for which the target cell feeds back NACK data for UE#1 (that is, the downlink data for retransmission processing), and the corresponding downlink HARQ process ID.
  • the HARQ process related to the ID of the corresponding HARQ process will respond to the HARQ operation according to the indication of the information #C4 issued by the target cell #1. For example, UE#1 can send ACK1 to source cell #1 on time-frequency resource #1, or send ACK1 to target cell #1 on time-frequency resource #2 according to information #C43, then UE#1 will give priority choose the latter solution to send ACK1, that is, send ACK1 to target cell #1 on time-frequency resource #2.
  • information #C4 may be included in DCI and carried in RRC signaling.
  • gNodeB-DU#1 needs to keep the generated new state.
  • gNodeB-DU#1 needs to keep the data of all HARQ processes corresponding to the new downlink data and the ID of the corresponding HARQ process, and for example, gNodeB-DU#1 needs to keep the new feedback received from UE#1
  • the data and the ID of the corresponding HARQ process so that the target cell #1 can grasp the data of the latest unfinished HARQ process.
  • the target cell #1 can include the control information corresponding to the new HARQ process data in information #C4 and send it to UE#1. For details, please refer to information #C4, which will not be repeated here. .
  • UE#1 sends response information #D1 according to information #C4.
  • the response information #D1 includes ACK or NACK data.
  • information #C4 includes information #C41a, then UE#1 needs to send uplink data that needs to be retransmitted on the time-frequency resource indicated by information #C41a;
  • the UE#1 needs to send the feedback data for the downlink data sent by the current source cell #1 to the UE#1 on the time-frequency resource indicated by the information #C43.
  • the information #G includes a UE context release command (UE context release command), and the source cell #1 releases the connection with the UE #1 after receiving the information #G.
  • UE context release command UE context release command
  • the source cell #1 continues to perform the new uplink HARQ process, and feeds back uplink data to the UE#1 until the new uplink HARQ process ends.
  • gNodeB-DU#1 retains the relevant data of the HARQ process that needs to reply NACK. For details, please refer to the above information #B2, which will not be repeated here. If it is a HARQ process that needs to reply ACK, then the source cell #1 will send the ACK data Just send it to UE#1. After gNodeB-DU#1 retains the data, it can send whether the data needs to be retransmitted and if it needs to be retransmitted, the time-frequency resource occupied by the target cell #1 can be sent to UE#1. For details, refer to information #C4.
  • the source cell #1 can continue to send the downlink data. After sending the downlink data, a new HARQ process is formed, but no new HARQ process is sent. downlink data.
  • gNodeB-DU#1 needs to retain the relevant data of the new HARQ process, and the specific content of the relevant data of the new HARQ process can be found in information #B2.
  • the source cell #1 receives the data sent by the UPF or there is unsent downlink data in the buffer of the source cell #1, then gNodeB-DU#1 needs to keep the unsent downlink data, So that the target cell #1 can continue to send the unsent downlink data.
  • the HARQ process performed by the UE can be continuous, and the performance of satellite communication can be strengthened. Latency advantage, obtain soft combining coding gain.
  • the embodiment of this application also considers that the cells before and after UE handover belong to the same base station (gNodeB), but belong to different gNodeB-Du.
  • multiple satellites in a satellite group are gNodeB-DU, and the ground gateway
  • the station or other satellites act as gNodeB-CU, and the inter-cell handover of the UE is actually a handover between different satellites, in which gNodeB-DU and gNodeB-CU are connected through a high-speed wireless link.
  • FIG. 9 is another schematic flowchart of the embodiment of the present application. In FIG.
  • Cell #1 belongs to source gNodeB-DU#1 and target gNodeB-DU#1 respectively, and all belong to gNodeB-CU#1 control.
  • source gNodeB-DU#1, target gNodeB-DU#1 and gNodeB-CU# 1 belong to the same base station
  • the source gNodeB-DU or the target gNodeB-DU in method 900 may correspond to one satellite, or may correspond to multiple satellites.
  • UE#1 performs cell handover based on measurement control information #A.
  • Step a gNodeB-CU#1 sends measurement control information #A to UE#1 through an RRC reconfiguration (RRC reconfiguration) message, wherein, the content of measurement control information #A refers to method 200;
  • Step b UE#1 replies the RRC reconfiguration complete (RRC reconfiguration complete) message to gNodeB-CU#1;
  • Step c UE#1 performs measurement according to the measurement control information #A, and reports the measurement report of the neighboring cell to gNodeB-CU#1;
  • Step d According to the PCI of the target cell carried in the measurement report, gNodeB-CU#1 judges that the target cell #1 and the source cell #1 belong to different DUs of the same gNodeB, and starts the inter-DU handover process in the station.
  • the target cell #1 according to The context of the source cell #1 where the UE is located makes an admission decision;
  • Step e gNodeB-CU#1 sends a UE context setup request (UE context setup request) message to the target gNodeB-DU#1, and applies to the target gNodeB-DU#1 for the resource of UE#1 for the target cell #1;
  • UE context setup request UE context setup request
  • Step f If the target gNodeB-DU#1 successfully allocates resources for UE#1, reply the UE context setup response (UE context setup response) message to gNodeB-CU#1;
  • Step g gNodeB-CU#1 sends a UE context modification request (UE context modification request) message to the target gNodeB-DU#1, which is used to instruct the source gNodeB-DU#1 to issue L2 signaling to stop scheduling the source cell#1 instructions;
  • UE context modification request UE context modification request
  • Step h Target gNodeB-DU#1 replies UE context modification response (UE context modification response) message to gNodeB-CU#1;
  • gNodeB-CU#1 sends information #B2, and target gNodeB-DU#1 receives information #B2.
  • the target gNodeB-DU#1 obtains the information #B2, so as to grasp the status and information of all current unfinished HARQ processes, and enables the target cell #1 to have the ability to take over the current HARQ process.
  • Step a gNodeB-CU#1 sends an RRC reconfiguration message to UE#1, which carries the target frequency point of target cell #1, the PCI of target cell #1, and the C-RNTI and dedicated random access preamble;
  • Step b UE#1 initiates non-contention random access in target cell #1 of target gNodeB-DU#1, and sends message 1 (message1, MSG1), message 1 includes a random access preamble sequence.
  • Step c The target gNodeB-DU#1 makes a random access response and sends a message 2 (message2, MSG2);
  • Step d UE#1 sends the RRC reconfiguration complete (RRC reconfiguration complete) message to gNodeB-CU#1, and UE#1 accesses the target cell #1;
  • step a of S930 that is, UE#1 successfully decodes the RRC reconfiguration message sent by gNodeB-CU#1) to the end of step d of S930 (that is, gNodeB-CU#1 successfully decodes the RRC reconfiguration message Complete information) during this period (can be called period #A3)
  • UE#1 no longer sends uplink data to the source gNodeB-DU#1, which means that UE#1 interrupts the uplink retransmission data of the unfinished uplink HARQ process or interrupt the transmission of the feedback data (ACK or NACK) of the unfinished downlink HARQ process, or interrupt the transmission of the data of the new uplink HARQ process.
  • ACK or NACK feedback data
  • the uplink data #A includes the uplink retransmission data of the unfinished uplink HARQ process, and/or the unfinished downlink HARQ Process feedback data (ACK or NACK).
  • the uplink data #A may also include uplink data of a new HARQ process.
  • the source gNodeB-DU#1 After the source gNodeB-DU#1 sends the RRC reconfiguration message to UE#1 in step a of S930, it sends information #B2g to the target gNodeB-DU#1 after a period of time #A3, and starts periodically Send information #B2g1, information #B2g2... to the target gNodeB-DU#1 until the source gNodeB-DU#1 receives the UE context release command (UE context release command) message from gNodeB-CU#1. Among them, information #B2g, information #B2g1, information #B2g2...
  • information #B2 updated according to the uplink data #A sent by UE#1 in period #A3, information #B2g, information #B2g1, information #B2g2... can The data corresponding to the updated HARQ process may be included, and the data corresponding to the unupdated HARQ process may also be included.
  • the source gNodeB-DU#1 sends information to the target gNodeB-DU#1 through gNodeB-CU#1, that is, the source gNodeB-DU#1 first sends information to gNodeB-CU#1, and gNodeB-CU# 1 and then forward the information to the target gNodeB-DU#1.
  • the duration #A3 may be predefined.
  • the value of duration #A3 may be (2*RTT6-RTT7), where RTT6 is the round-trip between UE#1 and source gNodeB-DU#1 or target gNodeB-DU#1 for signal transmission Delay, RTT7 is the sum of the signal transmission delay between the source gNodeB-DU#1 and gNodeB-CU and the signal transmission delay between gNodeB-CU and target gNodeB-DU#1.
  • duration #A3 may also be greater than (2*RTT6-RTT7), for example, when a decoding error occurs on UE#1 or target gNodeB-DU#1 within period #A3.
  • the value of RTT6 is 540ms.
  • the length of the above period may be predefined.
  • the length of the above period may be n times (0.5*RTT6), where n is an integer greater than 0.
  • the above solution solves the problem of the source gNodeB-DU# 1.
  • step a of S930 that is, after gNodeB-CU#1 sends the RRC reconfiguration message
  • step d of S930 that is, gNodeB-CU#1 successfully decodes the RRC reconfiguration completion message
  • the source gNodeB-DU#1 no longer sends downlink data to UE#1, which means that the source gNodeB-DU#1 interrupts the transmission of downlink retransmission data of the unfinished downlink HARQ process, Either interrupt the transmission of the feedback data (ACK or NACK) of the unfinished uplink HARQ process, or interrupt the transmission of the data of the new downlink HARQ process.
  • the source gNodeB-DU#1 can continue to send downlink data #A to UE#1, the downlink data #A includes the downlink retransmission data of the unfinished downlink HARQ process, and/or the unfinished uplink HARQ process Process feedback data (ACK or NACK).
  • ACK or NACK Process feedback data
  • the downlink data #A may also include downlink data of a new HARQ process, for example, downlink user plane data that UPF #1 has allocated to the source gNodeB-DU #1.
  • the source gNodeB-DU#1 sends information #B2g to the target gNodeB-DU#1 after a period of time #A3, and starts periodically sending the target gNodeB-DU#1 DU#1 sends information #B2g1, information #B2g2... until the source gNodeB-DU#1 receives the UE context release command (UE context release command) information sent by gNodeB-CU#1.
  • information #B2 updated according to the uplink data #A sent by UE#1 in period #A3, information #B2g, information #B2g1, information #B2g2... can The data corresponding to the updated HARQ process may be included, and the data corresponding to the unupdated HARQ process may also be included.
  • the source gNodeB-DU#1 sends information to the target gNodeB-DU#1 through gNodeB-CU#1, that is, the source gNodeB-DU#1 first sends information to gNodeB-CU#1, and gNodeB-CU# 1 and then forward the information to the target gNodeB-DU#1.
  • the above solution solves the problem of the source gNodeB-DU# 1.
  • the target gNodeB-DU#1 sends the information #C5, and the UE#1 receives the information #C5.
  • information #C5 includes at least one of the following information:
  • the information #C51 used to indicate whether all unfinished uplink HARQ processes between the current UE#1 and the source gNodeB-DU#1 need to be retransmitted.
  • the information #C51 may include the uplink HARQ processes that need to be retransmitted ID and NACK data, or the ID and ACK data of the uplink HARQ process that does not need to be retransmitted, it should be understood that the uplink HARQ process that needs to be retransmitted or the uplink HARQ process that does not need to be retransmitted here are included in all the above unfinished The uplink HARQ process;
  • Information #C51a used to indicate at least one of the time-frequency resource occupied by the uplink data corresponding to the uplink HARQ process that UE#1 needs to retransmit, and the identity of the target gNodeB-DU#1, for example, information #C51a It may include the ID of the uplink HARQ process that needs to be retransmitted, the corresponding time-frequency resource, and the identity of the target gNodeB-DU#1;
  • the information #C53 is used to instruct UE#1 to send feedback data of all current unfinished downlink HARQ processes to target cell #1, and at least one of the time-frequency resources occupied by the feedback data.
  • information #C53 may include at least one of the following information:
  • the ID of the currently unfinished downlink HARQ process The ID of the currently unfinished downlink HARQ process, the time-frequency resource occupied by the feedback data corresponding to the ID of the currently unfinished downlink HARQ process, and the identifier of the target gNodeB-DU#1.
  • the information #C53 may also be the redundant version data of the downlink data for which the target cell #1 feeds back NACK data for UE #1 (that is, the downlink data for retransmission processing), and the corresponding downlink ID of the HARQ process.
  • the HARQ process related to the ID of the corresponding HARQ process will respond to the HARQ operation according to the instruction of the information #C5 delivered by the target gNodeB-DU#1.
  • UE#1 can send ACK1 to source cell #1 on time-frequency resource #1, or send ACK1 to target cell #1 on time-frequency resource #2 according to the instruction of information #C53, then UE#1 will give priority choose the latter solution to send ACK1, that is, send ACK1 to target cell #1 on time-frequency resource #2.
  • information #C5 may be included in DCI and carried in RRC signaling.
  • source cell#1 sends new downlink data to UE#1 or receives new feedback data from UE#1 , then the source gNodeB-DU#1 needs to send the generated new state to the target gNodeB-DU#1.
  • the source gNodeB-DU#1 needs to send the data of all HARQ processes corresponding to the new downlink data and the IDs of the corresponding HARQ processes to the target gNodeB-DU#1, and for another example, the source gNodeB-DU#1 needs to send the target gNodeB-DU#1 gNodeB-DU#1 sends the received new feedback data of UE#1 and the ID of the corresponding HARQ process, so that the target cell#1 can grasp the latest unfinished HARQ process data.
  • the target gNodeB-DU#1 knows the new HARQ process data, it can include the control information corresponding to the new HARQ process data in information #C5 and send it to UE#1. For details, refer to information #C5, which will not be discussed here. Let me repeat.
  • UE#1 sends response information #D2 according to information #C5.
  • the response information #D2 includes ACK or NACK data.
  • information #C5 includes information #C51a
  • UE#1 needs to send uplink data that needs to be retransmitted on the time-frequency resource indicated by information #C51a;
  • information #C5 includes information #C53
  • UE#1 needs to send feedback data for the downlink data sent by the current source gNodeB-Du#1 to UE#1 on the time-frequency resource indicated by information #C53.
  • the information #G includes UE context release command (UE context release command) information, and the source gNodeB-DU#1 releases the connection with UE#1 after receiving the information #G.
  • UE context release command UE context release command
  • the source cell #1 continues to perform the new uplink HARQ process, and feeds back uplink data to the UE#1 until the new uplink HARQ process ends.
  • the source gNodeB-DU#1 sends the relevant data of the HARQ process that needs to reply NACK to the target gNodeB-DU#1. For the specific content, please refer to the above information #B2, which will not be repeated here. If it is a HARQ process that needs to reply ACK, then The source cell #1 only needs to send the ACK data to UE#1. After receiving the data, the target gNodeB-DU#1 can send the data to UE#1 whether the data needs to be retransmitted and if it needs to be retransmitted, the time-frequency resource occupied by the target cell #1, see information #C5 for details.
  • the source cell #1 if it has unfinished downlink data, it can continue to send the downlink data. After sending the downlink data, a new HARQ process is formed, but no new HARQ process is sent. downlink data. At this time, the source gNodeB-DU#1 needs to send the relevant data of the new HARQ process to the target gNodeB-DU#1, and the specific content of the relevant data of the new HARQ process can be found in information #B2.
  • the source gNodeB-DU#1 receives the data sent by the UPF or there is unsent downlink data in the cache of the source gNodeB-DU#1#1, then the source gNodeB-DU#1 needs to send the The unsent downlink data is sent to the target gNodeB-DU#1, so that the target cell #1 can continue to send the unsent downlink data.
  • the cells before and after UE handover can belong to different satellites, different satellites are different gNodeB-DUs, and different gNodeB-DUs are controlled by the same gNodeB-CU, and the different gNodeB-DUs and gNodeB-CUs belong to the same A base station, when the UE needs to perform inter-cell handover, enables the HARQ process performed by the UE to be continuous, strengthens the delay advantage of satellite communication, and obtains soft combining coding gain.
  • the embodiment of the present application also considers how to make the HARQ process continuous when the cell handover performed by the UE is a conditional handover (conditional handover), for example, as shown in the method 1000 in FIG. 10 .
  • Fig. 10 is another schematic flowchart of the embodiment of the present application.
  • source gNodeB#1, target gNodeB#1 and AMF please refer to the description in Fig. 6, and details will not be repeated here. Introduce as an example.
  • UE#1 performs conditional cell handover.
  • Step a The source gNodeB#1 sends measurement control information #A to UE#1 through an RRC reconfiguration (RRC reconfiguration) message.
  • the measurement control information #A includes measurement objects (such as intra-frequency measurement, inter-frequency measurement, etc.), measurement configuration (such as objects that UE needs to measure, cell list, reporting method, measurement identifier, event parameters, etc.) and measurement gaps (GAP) configuration, etc.;
  • Step b UE#1 responds to the source gNodeB#1 through the RRC reconfiguration complete message
  • Step c The source gNodeB#1 sends conditional handover request (conditional handover request) information to the target gNodeB#1 where the selected target cell #1 is located through the Xn link, and initiates a conditional handover request.
  • conditional handover request conditional handover request
  • conditional handover request information is used to indicate that the cell handover performed by UE#1 is a conditional cell handover.
  • Step d After receiving the conditional handover request message, the target gNodeB#1 performs admission control, and allocates the UE#1 instance and transmission resources after allowing the admission.
  • Step e The source gNodeB#1 sends an RRC reconfiguration message to UE#1, requesting UE#1 to perform handover to the target cell #1, wherein the RRC reconfiguration message may include the ID of the RRC reconfiguration target cell (RRCReconfiguration target cell ID) , new cell radio network temporary identity (new C-RNTI), security algorithm (security algorithm), condition #A and other information, wherein condition #A is used to indicate that when condition #A is met, UE #1 establishes a connection with target gNodeB#1, condition #A includes at least one of the following information:
  • Handover event an event that triggers UE#1 to perform cell handover, such as the event defined in the 3GPP standard document 38.331 of 5G NR, for example,
  • Event A1 The signal quality of the current serving cell begins to be better than the threshold value (threshold),
  • Event A2 The signal quality of the current serving cell begins to fall below the threshold value
  • Event A3 The signal quality of the neighbor cell begins to be better than a certain difference in the special serving cell
  • Event A4 The signal quality of the neighbor cell starts to be better than the threshold value
  • Event A5 The signal quality of the special serving cell begins to be worse than threshold 1 (threshold1) and better than threshold 2 (threshold2),
  • Event A6 The signal quality of the neighbor cell starts to be better than a certain difference in the secondary cell
  • Event B1 The neighboring cells of different radio access technology (radio access technology, RAT) start to be better than the threshold value
  • Event B2 (Event B2): The signal quality of the main cell starts to be worse than the threshold value 1 and the neighboring cells of different radio access technologies start to be better than the threshold value 2,
  • Geographical location the geographic location of UE#1 or the geographic location of source gNodeB#1,
  • Beam angle the angle of the beam between source gNodeB#1 and UE#1,
  • Timing an absolute moment, such as coordinated universal time (UTC),
  • Timer Trigger UE#1 to perform cell handover after a certain period of time
  • Step f UE#1 monitors whether the condition #A in the above conditional cell handover is satisfied for the candidate target cell.
  • the source gNodeB#1 sends information #B
  • the target gNodeB#1 receives information #B.
  • the information #B is used to indicate the unfinished uplink HARQ process between the source gNodeB#1 and the UE#1, and the specific content of the information #B refers to the method S220, which will not be repeated here.
  • the source gNodeB#1 sends information #B so that the target gNodeB#1 can grasp the status and information of all current unfinished uplink HARQ processes, and has the ability to take over the current HARQ process.
  • Step a UE#1 initiates a non-contention random access in the target cell where the target gNodeB#1 is located, and sends a message 1 (message1, MSG1), and the message 1 includes a random access preamble (preamble) sequence;
  • Step b The target gNodeB#1 makes a random access response and sends a message 2 (message2, MSG2);
  • Step c UE#1 sends the RRC reconfiguration complete message to the target gNodeB#1, and the air interface handover of UE#1 to the target cell #1 is completed.
  • the uplink data #A includes the uplink retransmission data of the unfinished uplink HARQ process, and/or the unfinished downlink HARQ process Feedback data (ACK or NACK).
  • the uplink data #A may also include uplink data of a new HARQ process.
  • the target gNodeB#1 sends the information #C
  • the UE#1 receives the information #C.
  • the target gNodeB#1 sends the information #E, and the AMF#1 receives the information #E.
  • the target gNodeB#1 sends the information #F, and the UE#1 receives the information #F.
  • the source gNodeB#1 releases the connection with UE#1.
  • Step a AMF#1 replies a path switch request acknowledge (path switch request acknowledge) message to the target gNodeB#1. If AMF#1 indicates in the path switching request confirmation message that the core network fails to establish the PDU session, the target gNodeB#1 deletes the failed PDU session;
  • Step b The target gNodeB#1 sends a UE context release (UE context release) message to the source gNodeB#1, and the source gNodeB#1 releases the connection with UE#1 after receiving the message;
  • UE context release UE context release
  • FIG. 11 and FIG. 12 are schematic structural diagrams of possible communication devices provided by the embodiments of the present application. These communication devices can implement the functions of the terminal equipment or the network equipment in the foregoing method embodiments, and therefore can also realize the beneficial effects of the foregoing method embodiments.
  • the communication device may be the communication device in method 100, or may be a module (such as a chip) applied to the communication device.
  • a communication device 1100 includes a transceiver module 1101 and a processing module 1102 .
  • the communication device 1100 may be used to implement the functions of the communication device in the method embodiment shown in FIG. 5 above.
  • the transceiver module 1101 is used to transmit the first data between the first terminal device and the first network device, and the first data corresponds to the first hybrid automatic repeat request HARQ Process: In the case that the first terminal device switches from the first network device to the second network device, the transceiver module 1101 is also used for the first terminal device to transmit second data with the second network device, and the second data corresponds to the first HARQ process , the second data includes at least one of data for retransmission processing on the first data and feedback information for the first data; the processing module 1102 is configured to determine the first data and the second data.
  • transceiver module 1101 and processing module 1102 For a more detailed description of the foregoing transceiver module 1101 and processing module 1102, reference may be made to relevant descriptions in the foregoing method embodiments, and no further description is given here.
  • a communication device 1200 includes a processor 1210 and an interface circuit 1220 .
  • the processor 1210 and the interface circuit 1220 are coupled to each other.
  • the interface circuit 1220 may be a transceiver or an input/output interface.
  • the communication device 1200 may further include a memory 1230 for storing instructions executed by the processor 1210 or storing input data required by the processor 1210 to execute the instructions or storing data generated after the processor 1210 executes the instructions.
  • the memory 1230 and the processor 1210 may be integrated together, or may be independent devices.
  • the processor 1210 is used to execute the functions of the above-mentioned processing module 1102
  • the interface circuit 1220 is used to execute the functions of the above-mentioned transceiver module 1101 .
  • the chip of the communication device realizes the function of the communication device in the above-mentioned method embodiment.
  • the communication device chip receives information from other modules (eg radio frequency module or antenna) in the communication device; or, the communication device chip sends information to other modules (eg radio frequency module or antenna) in the communication device.
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. place.
  • the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.
  • the systems and system embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is It can be located in one place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without creative effort.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory (random access memory, RAM), flash memory, read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM) , PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or known in the art any other form of storage medium.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC may be located in the access network device or the terminal device.
  • the processor and the storage medium may also exist in the access network device or the terminal device as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer program or instructions may be stored in or transmitted via a computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (solid state disk, SSD).
  • a magnetic medium such as a floppy disk, a hard disk, or a magnetic tape
  • an optical medium such as a DVD
  • it may also be a semiconductor medium such as a solid state disk (solid state disk, SSD).
  • “at least one” means one or more, and “multiple” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship; in the formulas of this application, the character “/” indicates that the contextual objects are a "division” Relationship.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种数据传输方法和装置，使能在通信网络中，终端设备在进行小区切换时，终端设备与网络侧未结束的HARQ进程能够连续，减少通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务，所述方法包括：第一终端设备与第一网络设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第二网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个。

Description

一种数据传输方法和装置
本申请要求于2021年06月24日提交中国专利局、申请号为202110705433.7、发明名称为“一种数据传输方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种数据传输方法和装置。
背景技术
在第五代(5th generation，5G)系统及5G演进网络需要满足各行各业的业务需求同时需要提供更广的业务覆盖，当前地面移动通信网络有限的覆盖能力，已经不能满足人们在任意时间、任意地点获取信息的需求；而且基于当前基于基站覆盖的模式来提供超广域的覆盖对于偏远地区、沙漠、海洋和空中等场景存在经济性和可行性方面的巨大挑战。另一方面，卫星通信相对于传统的移动通信系统，其拥有更广的覆盖范围，支持不对传输链路以及通信成本与传输距离无关，可以克服海洋，沙漠，高山等自然地理障碍等优点。为了克服传统通信网的不足，卫星通信可以作为传统网络的一个有效的补充。
在卫星通信网络中，由于卫星的高速移动，会造成用户频繁的发生小区切换，在目前的地面网络，例如5G或者长期演进(long term evolution，LTE)系统中用户发生小区间切换时，如果有未来得及反馈的混合自动重传请求(hybrid automatic repeat request，HARQ)，例如确认消息(acknowledgement，ACK)或者否定应答(negative-acknowledgement，NACK)，那么当前的HARQ进程(process)会直接被丢弃，HARQ缓存(buffer)会直接被清空。如果将该机制引入到卫星通信网络中的小区切换，会导致用户设备在不同小区间切换时HARQ进程无法连续的问题。同理，如果用户设备进行的小区切换前后的信道近似，也面临着上述问题。
发明内容
本申请提供了一种数据传输方法和装置，使能在通信网络中，终端设备在进行小区切换时，终端设备与网络侧未结束的HARQ进程能够连续，减少通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
第一方面，本申请提供了一种数据传输方法，所述方法包括：第一终端设备与第一网络设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第二网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个。
上述方式中，第一终端设备与第一网络设备或第二网络设备之间的传输方式可以是上 行传输也可以是下行传输，本申请对此不做限定。即，上述第一数据和第二数据可以是上行数据也可以是下行数据。
上述方式中的在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，表示第一终端设备在执行小区切换时，虽然与第二网络设备建立了连接，但是该小区切换并没有完成。
采用上述方式，使能终端设备在进行小区切换时，能够和小区切换的目的网络设备继续传输未结束的HARQ进程的数据，相比于目前的技术方案中清空HARQ缓存数据的方式，本申请中的上述方式能够减小通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
在一种可能的实施方式中，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第二网络设备传输第二数据包括：在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功译码用于执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
采用上述方式，使能终端设备在上述第一时段内继续和网络设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第一网络设备传输第二数据包括：在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功发送消息1MSG1的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
上述方式所处的场景可以是，当第一终端设备执行小区切换，并且接收到的RRC重配置消息中包括条件信息，其中，该条件信息用于指示当满足该条件时，第一终端设备发起非竞争的随机接入MSG1。
采用上述方式，使能终端设备在上述第一时段内继续和网络设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，在所述第一终端设备与所述第二网络设备传输第二数据之前，所述方法包括：所述第一终端设备将第一介质访问控制层MAC实体中的所述第一HARQ进程的数据复制到第二MAC实体中，其中，所述第一MAC实体对应所述第一网络设备，所述第二MAC实体对应所述第二网络设备。
采用上述方式，使能终端设备将未结束的上行HARQ进程数据保留，从而使能未结束的上行HARQ进程连续。
在一种可能的实施方式中，在所述第一终端设备与所述第二网络设备传输第二数据之 前，所述方法包括：所述第一终端设备接收第一指示信息，所述第一指示信息用于指示所述第一终端设备与所述第二网络设备传输所述第二数据。
在一种可能的实施方式中，所述第一指示信息包括以下信息的一种或多种：所述第一HARQ进程的标识、所述第二网络设备的标识、第一资源，其中，所述第一资源为所述第二数据所占用的资源。
采用上述方式，使能终端设备更精确的了解要继续进行的HARQ进程、目的网络设备以及该HARQ进程对应的传输资源。
在一种可能的实施方式中，所述第一数据为上行数据，所述第二数据包括对所述第一数据进行重传处理的数据。
在一种可能的实施方式中，所述第一数据为下行数据，所述第二数据包括针对所述第一数据的反馈信息。
在一种可能的实施方式中，所述第一数据的反馈信息包括确认消息ACK或者否认应答NACK。
在一种可能的实施方式中，所述第一网络设备或者所述第二网络设备为卫星。
当网络侧为卫星时，采用上述方式能够强化卫星通信系统的时延优势。
第二方面，本申请提供了一种数据传输方法，所述方法包括：第一网络设备接收第一信息，所述第一信息用于指示第一终端设备从第二网络设备切换到所述第一网络设备；所述第一网络设备获取第二信息，所述第二信息用于指示所述第一终端设备与所述第二网络设备之间未结束的第一混合自动重传请求HARQ进程；所述第一网络设备根据所述第二信息向所述第一终端设备发送第三信息，所述第三信息用于指示所述第一终端设备与所述第一网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个，其中，所述第一数据对应所述第一HARQ进程，所述第一数据为所述第一终端设备与所述第二网络设备之间已经传输的数据。
上述方式中，第一终端设备与第一网络设备或第二网络设备之间的传输方式可以是上行传输也可以是下行传输，本申请对此不做限定。即，上述第一数据和第二数据可以是上行数据也可以是下行数据。
采用上述方式，使能终端设备在进行小区切换时，能够和小区切换的目的网络设备继续传输未结束的HARQ进程的数据，同时，第一网络设备作为小区切换的目的网络设备能够获取未结束的HARQ进程的相关数据，从而能够实现HARQ进程连续，相比于目前的技术方案中清空HARQ缓存数据的方式，本申请中的上述方式能够减小通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
在一种可能的实施方式中，所述方法包括：所述第一网络设备在第一时段内接收所述第二网络设备发送的第四信息，所述第一时段包括所述第二网络设备发出用于所述第一终端设备执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第一网络设备成功译码所述第一终端设备发送的第一RRC重配置完成消息的结束时刻之间的时段，所述第一时段用于所述第二网络设备与所述第一终端设备传输第三数据，所述第三数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息、第二HARQ进程的初始数据中的至少一个，所述第四信息为所述第二信息的更新信息并且对应所述第三数据。
采用上述方式，使能网络设备在上述第一时段内继续和终端设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式能够缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，所述第一网络设备在第一时段内接收所述第二网络设备发送的第四信息包括：所述第一网络设备在第一时段的起始时刻并经过第一时延接收所述第二网络设备发送的第四信息。
在一种可能的实施方式中，所述第一时延的值为2*RTT，所述RTT为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延。
采用上述方式，使能第一网络设备最早经过第一时延后接收第四信息，以避免第一网络设备作多余的功耗。
在一种可能的实施方式中，所述方法包括：所述第一网络设备在接收所述第四信息的结束时刻并经过第二时延接收所述第二网络设备发送的第五信息，所述第五信息为所述第四信息的更新信息，所述第二时延的值为(0.5*RTT)的n倍，所述n为正整数。
上述方式中，第五信息可以包括相比于第四信息的更新部分的信息，还可以包括第四信息的原有部分的信息。
采用上述方式，使能第一网络设备在接收所述第四信息的结束时刻开始周期性地接收第五信息，能够保证未结束HARQ进程的数据的及时更新。
在一种可能的实施方式中，所述第二信息包括以下信息的至少一种：所述第一HARQ进程的冗余版本数据、所述第一HARQ进程的标识、所述第一HARQ进程的冗余版本号。
在一种可能的实施方式中，所述第二信息包括以下信息的至少一种：所述第二网络设备已经接收到的所述第一HARQ进程的数据、所述第二网络设备针对所述第一HARQ进程已经译码的数据。
在一种可能的实施方式中，所述第三信息包括以下信息的一种或多种：所述第一HARQ进程的标识、所述第一网络设备的标识、第一资源，其中，所述第一资源为传输所述第二数据所占用的资源。
采用上述方式，使能终端设备更精确的了解要继续进行的HARQ进程、目的网络设备以及该HARQ进程对应的传输资源。
在一种可能的实施方式中，在所述第一数据为上行数据的情况下，所述第二数据包括对第一数据进行重传处理的数据。
在一种可能的实施方式中，在所述第一数据为下行数据的情况下，所述第二数据包括针对所述第一数据的反馈信息。
在一种可能的实施方式中，所述第一数据的反馈信息包括确认消息ACK或者否认应答NACK。
在一种可能的实施方式中，所述第一终端设备或者所述第二网络设备为卫星。
当网络侧为卫星时，采用上述方式能够强化卫星通信系统的时延优势。
第三方面，本申请提供了一种数据传输方法，所述方法包括：第一网络设备与第一终端设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；在所述第一终端设备从所述第一网络设备切换至第二网络设备的情况下，所述第一网络设备向所述 第二网络设备发送第一信息，所述第一信息用于指示所述第一HARQ进程。
上述方式中，第一终端设备与第一网络设备或第二网络设备之间的传输方式可以是上行传输也可以是下行传输，本申请对此不做限定。即，上述第一数据和第二数据可以是上行数据也可以是下行数据。
采用上述方式，使能终端设备在进行小区切换时，能够和小区切换的目的网络设备继续传输未结束的HARQ进程的数据，同时，第一网络设备向小区切换的目的网络设备即第二网络设备发送未结束的HARQ进程的相关数据，从而能够使得第二网络设备掌握结束的HARQ进程的相关数据，实现HARQ进程连续，相比于目前的技术方案中清空HARQ缓存数据的方式，本申请中的上述方式能够减小通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
在一种可能的实施方式中，所述第一信息包括以下信息的至少一种：所述第一HARQ进程的冗余版本数据、所述第一HARQ进程的标识、所述第一HARQ进程的冗余版本号。
在一种可能的实施方式中，所述第一信息包括以下信息的至少一种：所述第一网络设备已经接收到的所述第一HARQ进程的数据、所述第一网络设备针对所述第一HARQ进程已经译码的数据。
在一种可能的实施方式中，所述方法包括：所述第一网络设备在第一时段内与所述第一终端设备传输第二数据，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息、第二HARQ进程的初始数据中的至少一个，其中，所述第一时段包括所述第一网络设备发出用于所述第一终端设备执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第二网络设备成功译码所述第一终端设备发送的第一RRC重配置完成消息的时刻之间的时段。
采用上述方式，使能网络设备在上述第一时段内继续和终端设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式能够缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，所述方法包括：所述第一网络设备在所述第一时段的起始时刻并经过第一时延向所述第二网络设备发送第二信息，所述第二信息为所述第一信息的更新信息。
采用上述方式，通过规定第一网络设备发送第二信息的时间，使能第二网络设备在规定的时间接收信息，减少功耗。
在一种可能的实施方式中，所述第一网络设备为第一卫星，所述第二网络设备为第二卫星，所述第一网络设备与所述第二网络设备存在星间链路，所述第一时延的值为2*RTT1-0.5*RTT2，所述RTT1为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述RTT2为所述第一网络设备与所述第二网络设备之间数据传输的往返时延。
在一种可能的实施方式中，所述第一网络设备为第一卫星，所述第二网络设备为第二卫星，所述第一网络设备与所述第二网络设备通过第三网络设备进行数据传输，所述第一时延的值为2*RTT3-RTT4，其中，所述RTT3为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述RTT4为第二时延与第三时延的和， 所述第二时延为所述第一网络设备与所述第三网络设备的数据传输的时延，所述第三时延为所述第二网络设备与所述第三网络设备的数据传输的时延。
在一种可能的实施方式中，所述第一网络设备与所述第二网络设备为第一卫星，所述第一时延的值为2*RTT5，其中，所述RTT5为所述第一终端设备与所述第一网络设备之间数据传输的往返时延。
在一种可能的实施方式中，所述方法包括：所述第一网络设备在发出所述第二信息的时刻并经过第二时延向所述第二网络设备发送第三信息，所述第三信息为所述第二信息的更新信息，所述第二时延的值为(0.5*RTT6)的n倍，所述RTT6为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述n为正整数。
上述方式中，第三信息可以包括相比于第二信息的更新部分的信息，还可以包括第二信息的原有部分的信息。
采用上述方式，使能第一网络设备在发出所述第二信息的时刻开始周期性地发送第三信息，能够保证第二网络设备中的未结束HARQ进程的数据的及时更新。
第四方面，提供了一种数据传输装置，所述装置包括：收发模块，所述收发模块用于第一终端设备与第一网络设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述收发模块还用于所述第一终端设备与所述第二网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个。
上述方式中，第一终端设备与第一网络设备或第二网络设备之间的传输方式可以是上行传输也可以是下行传输，本申请对此不做限定。即，上述第一数据和第二数据可以是上行数据也可以是下行数据。
上述方式中的在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，表示第一终端设备在执行小区切换时，虽然与第二网络设备建立了连接，但是该小区切换并没有完成。
采用上述方式，使能终端设备在进行小区切换时，能够和小区切换的目的网络设备继续传输未结束的HARQ进程的数据，相比于目前的技术方案中清空HARQ缓存数据的方式，本申请中的上述方式能够减小通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
在一种可能的实施方式中，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述收发模块还用于所述第一终端设备与所述第二网络设备传输第二数据包括：在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述收发模块还用于所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功译码用于执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
采用上述方式，使能终端设备在上述第一时段内继续和网络设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式能够缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短 了用户感知的时延。
在一种可能的实施方式中，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述收发模块还用于第一终端设备与所述第一网络设备传输第二数据包括：在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述收发模块还用于所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功发送消息1MSG1的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。。
上述方式所处的场景可以是，当第一终端设备执行小区切换，并且接收到的RRC重配置消息中包括条件信息，其中，该条件信息用于指示当满足该条件时，第一终端设备发起非竞争的随机接入MSG1。
采用上述方式，使能终端设备在上述第一时段内继续和网络设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，在所述第一终端设备与所述第二网络设备传输第二数据之前，所述装置包括：处理模块，所述处理模块用于所述第一终端设备将第一介质访问控制层MAC实体中的所述第一HARQ进程的数据复制到第二MAC实体中，其中，所述第一MAC实体对应所述第一网络设备，所述第二MAC实体对应所述第二网络设备。
采用上述方式，使能终端设备将未结束的上行HARQ进程数据保留，从而使能未结束的上行HARQ进程连续。
在一种可能的实施方式中，在所述第一终端设备与所述第二网络设备传输第二数据之前，所述收发模块还用于所述第一终端设备接收第一指示信息，所述第一指示信息用于指示所述第一终端设备与所述第二网络设备传输所述第二数据。
在一种可能的实施方式中，所述第一指示信息包括以下信息的一种或多种：所述第一HARQ进程的标识、所述第二网络设备的标识、第一资源，其中，所述第一资源为所述第二数据所占用的资源。
采用上述方式，使能终端设备更精确的了解要继续进行的HARQ进程、目的网络设备以及该HARQ进程对应的传输资源。
在一种可能的实施方式中，所述第一数据为上行数据，所述第二数据包括对所述第一数据进行重传处理的数据。
在一种可能的实施方式中，所述第一数据为下行数据，所述第二数据包括针对所述第一数据的反馈信息。
在一种可能的实施方式中，所述第一数据的反馈信息包括确认消息ACK或者否认应答NACK。
在一种可能的实施方式中，所述第一网络设备或者所述第二网络设备为卫星。
当网络侧为卫星时，采用上述方式能够强化卫星通信系统的时延优势。
第四方面以及第四方面的各个实施方式中的装置可称为第一通信装置。
第五方面，本申请提供了一种数据传输装置，所述装置包括：收发模块，所述收发模块用于第一网络设备接收第一信息，所述第一信息用于指示第一终端设备从第二网络设备 切换到所述第一网络设备；所述收发模块还用于所述第一网络设备获取第二信息，所述第二信息用于指示所述第一终端设备与所述第二网络设备之间未结束的第一混合自动重传请求HARQ进程；所述收发模块还用于所述第一网络设备根据所述第二信息向所述第一终端设备发送第三信息，所述第三信息用于指示所述第一终端设备与所述第一网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个，其中，所述第一数据对应所述第一HARQ进程，所述第一数据为所述第一终端设备与所述第二网络设备之间已经传输的数据。
上述方式中，第一终端设备与第一网络设备或第二网络设备之间的传输方式可以是上行传输也可以是下行传输，本申请对此不做限定。即，上述第一数据和第二数据可以是上行数据也可以是下行数据。
采用上述方式，使能终端设备在进行小区切换时，能够和小区切换的目的网络设备继续传输未结束的HARQ进程的数据，同时，第一网络设备作为小区切换的目的网络设备能够获取未结束的HARQ进程的相关数据，从而能够实现HARQ进程连续，相比于目前的技术方案中清空HARQ缓存数据的方式，本申请中的上述方式能够减小通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
在一种可能的实施方式中，所述收发模块还用于所述第一网络设备在第一时段内接收所述第二网络设备发送的第四信息，所述第一时段包括所述第二网络设备发出用于所述第一终端设备执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第一网络设备成功译码所述第一终端设备发送的第一RRC重配置完成消息的结束时刻之间的时段，所述第一时段用于所述第二网络设备与所述第一终端设备传输第三数据，所述第三数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息、第二HARQ进程的初始数据中的至少一个，所述第四信息为所述第二信息的更新信息并且对应所述第三数据。
采用上述方式，使能网络设备在上述第一时段内继续和终端设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式能够缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，所述收发模块还用于所述第一网络设备在第一时段内接收所述第二网络设备发送的第四信息包括：所述收发模块还用于所述第一网络设备在第一时段的起始时刻并经过第一时延接收所述第二网络设备发送的第四信息。
在一种可能的实施方式中，所述第一时延的值为2*RTT，所述RTT为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延。
采用上述方式，使能第一网络设备最早经过第一时延后接收第四信息，以避免第一网络设备作多余的功耗。
在一种可能的实施方式中，所述收发模块还用于所述第一网络设备在接收所述第四信息的结束时刻并经过第二时延接收所述第二网络设备发送的第五信息，所述第五信息为所述第四信息的更新信息，所述第二时延的值为(0.5*RTT)的n倍，所述n为正整数。
上述方式中，第五信息可以包括相比于第四信息的更新部分的信息，还可以包括第四 信息的原有部分的信息。
采用上述方式，使能第一网络设备在接收所述第四信息的结束时刻开始周期性地接收第五信息，能够保证未结束HARQ进程的数据的及时更新。
在一种可能的实施方式中，所述第二信息包括以下信息的至少一种：所述第一HARQ进程的冗余版本数据、所述第一HARQ进程的标识、所述第一HARQ进程的冗余版本号。
在一种可能的实施方式中，所述第二信息包括以下信息的至少一种：所述第二网络设备已经接收到的所述第一HARQ进程的数据、所述第二网络设备针对所述第一HARQ进程已经译码的数据。
在一种可能的实施方式中，所述第三信息包括以下信息的一种或多种：所述第一HARQ进程的标识、所述第一网络设备的标识、第一资源，其中，所述第一资源为传输所述第二数据所占用的资源。
采用上述方式，使能终端设备更精确的了解要继续进行的HARQ进程、目的网络设备以及该HARQ进程对应的传输资源。
在一种可能的实施方式中，在所述第一数据为上行数据的情况下，所述第二数据包括对第一数据进行重传处理的数据。
在一种可能的实施方式中，在所述第一数据为下行数据的情况下，所述第二数据包括针对所述第一数据的反馈信息。
在一种可能的实施方式中，所述第一数据的反馈信息包括确认消息ACK或者否认应答NACK。
在一种可能的实施方式中，所述第一终端设备或者所述第二网络设备为卫星。
当网络侧为卫星时，采用上述方式能够强化卫星通信系统的时延优势。
第五方面以及第五方面的各个实施方式中的装置可称为第二通信装置。
第六方面，本申请提供了一种数据传输装置，所述装置包括：收发模块，所述收发模块用于第一网络设备与第一终端设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；在所述第一终端设备从所述第一网络设备切换至第二网络设备的情况下，所述收发模块还用于所述第一网络设备向所述第二网络设备发送第一信息，所述第一信息用于指示所述第一HARQ进程。
上述方式中，第一终端设备与第一网络设备或第二网络设备之间的传输方式可以是上行传输也可以是下行传输，本申请对此不做限定。即，上述第一数据和第二数据可以是上行数据也可以是下行数据。
采用上述方式，使能终端设备在进行小区切换时，能够和小区切换的目的网络设备继续传输未结束的HARQ进程的数据，同时，第一网络设备向小区切换的目的网络设备即第二网络设备发送未结束的HARQ进程的相关数据，从而能够使得第二网络设备掌握结束的HARQ进程的相关数据，实现HARQ进程连续，相比于目前的技术方案中清空HARQ缓存数据的方式，本申请中的上述方式能够减小通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
在一种可能的实施方式中，所述第一信息包括以下信息的至少一种：所述第一HARQ进程的冗余版本数据、所述第一HARQ进程的标识、所述第一HARQ进程的冗余版本号。
在一种可能的实施方式中，所述第一信息包括以下信息的至少一种：所述第一网络设 备已经接收到的所述第一HARQ进程的数据、所述第一网络设备针对所述第一HARQ进程已经译码的数据。
在一种可能的实施方式中，所述收发模块还用于所述第一网络设备在第一时段内与所述第一终端设备传输第二数据，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息、第二HARQ进程的初始数据中的至少一个，其中，所述第一时段包括所述第一网络设备发出用于所述第一终端设备执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第二网络设备成功译码所述第一终端设备发送的第一RRC重配置完成消息的时刻之间的时段。
采用上述方式，使能网络设备在上述第一时段内继续和终端设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式能够缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，所述收发模块还用于所述第一网络设备在所述第一时段的起始时刻并经过第一时延向所述第二网络设备发送第二信息，所述第二信息为所述第一信息的更新信息。
采用上述方式，通过规定第一网络设备发送第二信息的时间，使能第二网络设备在规定的时间接收信息，减少功耗。
在一种可能的实施方式中，所述第一网络设备为第一卫星，所述第二网络设备为第二卫星，所述第一网络设备与所述第二网络设备存在星间链路，所述第一时延的值为2*RTT1-0.5*RTT2，所述RTT1为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述RTT2为所述第一网络设备与所述第二网络设备之间数据传输的往返时延。
在一种可能的实施方式中，所述第一网络设备为第一卫星，所述第二网络设备为第二卫星，所述第一网络设备与所述第二网络设备通过第三网络设备进行数据传输，所述第一时延的值为2*RTT3-RTT4，其中，所述RTT3为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述RTT4为第二时延与第三时延的和，所述第二时延为所述第一网络设备与所述第三网络设备的数据传输的时延，所述第三时延为所述第二网络设备与所述第三网络设备的数据传输的时延。
在一种可能的实施方式中，所述第一网络设备与所述第二网络设备为第一卫星，所述第一时延的值为2*RTT5，其中，所述RTT5为所述第一终端设备与所述第一网络设备之间数据传输的往返时延。
在一种可能的实施方式中，所述收发模块还用于所述第一网络设备在发出所述第二信息的时刻并经过第二时延向所述第二网络设备发送第三信息，所述第三信息为所述第二信息的更新信息，所述第二时延的值为(0.5*RTT6)的n倍，所述RTT6为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述n为正整数。
上述方式中，第三信息可以包括相比于第二信息的更新部分的信息，还可以包括第二信息的原有部分的信息。
采用上述方式，使能第一网络设备在发出所述第二信息的时刻开始周期性地发送第三信息，能够保证第二网络设备中的未结束HARQ进程的数据的及时更新。
第六方面以及第六方面的各个实施方式中的装置可称为第三通信装置。
第七方面，提供了一种通信装置，该通信装置可以为上述方法实施例中的第一通信装置，或者为设置在通信装置中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行所述计算机程序或指令时，使通信装置执行上述方法实施例中由通信装置所执行的方法。
示例性地，存储器和处理器可以集成在一起，也可以为独立的器件。
第八方面，提供了一种通信装置，该通信装置可以为上述方法实施例中的第二通信装置，或者为设置在第二通信装置中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行所述计算机程序或指令时，使通信装置执行上述方法实施例中由第二通信装置所执行的方法。
示例性地，存储器和处理器可以集成在一起，也可以为独立的器件。
第九方面，提供了一种通信装置，该通信装置可以为上述方法实施例中的第三通信装置，或者为设置在第三通信装置中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行所述计算机程序或指令时，使通信装置执行上述方法实施例中由第三通信装置所执行的方法。
示例性地，存储器和处理器可以集成在一起，也可以为独立的器件。
第十方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，使得上述各方面中由第一通信装置执行的方法被执行。
上述方式中，第一通信装置可以是终端设备。
第十一方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，使得上述各方面中由第二通信装置执行的方法被执行。
上述方式中，第二通信装置可以是网络设备，例如卫星。
第十二方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，使得上述各方面中由第三通信装置执行的方法被执行。
上述方式中，第三通信装置可以是网络设备，例如卫星。
第十三方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第一通信装置的功能。在一种可能的设计中，所述芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十四方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各方面的方法中第二通信装置的功能。在一种可能的设计中，所述芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十五方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于实现上述各 方面的方法中第三通信装置的功能。在一种可能的设计中，所述芯片系统还包括存储器，用于保存程序指令和/或数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十六方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第一通信装置执行的方法。
第十七方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第二通信装置执行的方法。
第十八方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第三通信装置执行的方法。
附图说明
图1是适用于本申请实施例的一例应用场景图。
图2是适用于本申请实施例的再一例应用场景图。
图3是适用于本申请实施例的又一例应用场景图。
图4是适用于本申请实施例的又一例应用场景图。
图5是本申请实施例的一例示意性流程图。
图6是本申请实施例的再一例示意性流程图。
图7是本申请实施例的又一例示意性流程图。
图8是本申请实施例的又一例示意性流程图。
图9是本申请实施例的又一例示意性流程图。
图10是本申请实施例的又一例示意性流程图。
图11是本申请的实施例提供的可能的通信装置的结构示意图。
图12是本申请的实施例提供的可能的通信装置的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：窄带物联网系统(narrow band-internet of things，NB-IoT)、全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)、卫星通信系统、未来的第六代(6th generation，6G)系统等。
本申请实施例中的终端设备，也可以称为用户设备(user equipment，UE)、接入终 端、终端设备单元(subscriber unit)、终端设备站、移动站、移动台(mobile station，MS)、远方站、远程终端、移动设备、用户终端、终端(terminal)、无线通信设备、终端设备代理或终端设备装置。终端设备可以包括各种具有无线通信功能的手持设备、车载设备、物联网(internet of things，IoT)设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备。还可以包括用户单元、蜂窝电话(cellular phone)、智能手机(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handset)、膝上型电脑(laptop computer)、机器类型通信(machine type communication，MTC)终端、无人机、无线局域网(wireless local area networks，WLAN)中的站点(station，ST)。可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站以及下一代通信系统，例如，5G网络中的终端设备或者未来演进的PLMN网络中的终端设备等。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，网络设备可以是全球移动通讯(global system of mobile communication，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(nodeB，NB)，还可以是LTE系统中的演进型基站(evolutional nodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，还可以是卫星通信系统中的卫星基站，或者网络设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的网络设备或者未来演进的PLMN网络中的网络设备，还可以是设备到设备(device-to-device，D2D)通信、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备等，本申请实施例并不限定。
需要说明的是，本申请实施例的技术方案可以适用于集中单元(central unit，CU)和分布式单元(distributed unit，DU)架构，也可以适用于控制面(control plane，CP)和(user plane，UP)分离的架构，本申请对此不做限定。
为了便于理解，以下将对本申请实施例所涉及的基本概念或技术作简单介绍。
卫星星座：在卫星星座中，多个卫星一起工作以提供比任何卫星本身可以覆盖的区域更大的覆盖范围。例如，高轨(geostationary earth orbit,GEO)卫星通信系统，也称同步轨道卫星系统；中轨(medium earth orbit,MEO)卫星通信系统和低轨(Low Earth Orbit,LEO)卫星通信系统。以美国SpaceX为代表的巨型通信星座，此星座中的卫星具有大容量的星间通信能力，使得卫星通信系统拥有更为灵活的网络管理能力，减少对地面网络的依赖，增强系统的通信能力。
5G NR(或者LTE)重传机制：5G NR有多个回传机制，采用了如下三层协议栈：
介质访问控制(media access control，MAC)协议层：它在NR中实现快速重传系统，称为混合自动重传请求(hybrid automatic repeat request，HARQ)。
无线链路层控制(radio link control，RLC)协议层：虽然MAC层中已经有了HARQ，但在反馈系统中仍可能存在一些错误。所以，为处理这些错误，RLC层有一个慢重传系统，该反馈受循环冗余校验(cyclic redundancy check，CRC)保护。与HARQ确认方式相比，RLC状态报告传递的频率相对较低。
分组数据汇聚协议(packet data convergence protocol，PDCP)协议层：这将保证用户数据的顺序传输，它主要用于切换期间。因为在执行切换时，RLC和MAC缓冲区都会被清空。
HARQ：MAC层HARQ是一种结合FEC(forward error correction，前向纠错)与自动重传请求(automatic repeat request，ARQ)方法的技术。FEC通过添加冗余信息，使得接收端能够纠正一部分错误，从而减少重传的次数。而对于FEC无法纠正的错误，接收端会通过ARQ机制请求发送端重发数据。接收端使用检错码，通常为CRC校验，来检测接收到的数据包是否出错。如果无错，则接收端会发送一个肯定的确认(ACK)给发送端，发送端收到ACK后，会接着发送下一个数据包。如果出错，则接收端会丢弃该数据包，并发送一个否定的确认(NAK)给发送端，发送端收到NAK后，会重发相同的数据。
MAC层的ARQ机制采用丢弃数据包并请求重传的方式。虽然这些数据包无法被正确解码，但其中还是包含了有用的信息，如果丢弃了，这些有用的信息就丢失了。通过使用HARQ，接收到的错误数据包会保存在一个HARQ缓存(buffer)中，并与后续接收到的重传数据包进行合并，从而得到一个比单独解码更可靠的数据包(该过程可称为“软合并”)。然后对合并后的数据包进行解码，如果还是失败，则重复“请求重传，再进行软合并”的过程。
根据重传的比特信息与原始传输是否相同，HARQ分为追赶合并(chase combining)和增量冗余(incremental redundancy，IR)两类。追赶合并中重传的比特信息与原始传输相同；增量冗余中重传的比特信息不需要与原始传输相同。LTE和NR中只使用IR机制。
HARQ进程(process)：HARQ使用停等协议(stop-and-wait protocol)来发送数据，在停等协议中，发送端发送一个传输块(transport block，TB)后，就停下来等待确认信息。其中，每个HARQ进程在接收端都需要有独立的HARQ缓存，以便对接收到的数据进行软合并。
HARQ进程标识(identitifier，ID)：唯一地指定一个HARQ进程。
新数据指示(new data indicator，NDI)：每个HARQ进程会保存一个NDI值，该值使用1比特来指示被调度的数据是新传还是重传。如果同一HARQ进程的NDI值与之前相比发生了变化(NDI toggled)，则表示当前传输是一个新的TB的初传，否则(NDI not toggled)表示当前传输是同一个TB的重传。在NR中，没有针对物理上行共享信道(physical uplink shared channel，PUSCH)显式的HARQ ACK/NAK。UE通过在一定时间内检测5G基站(gNodeB，gNB)是否发送回传请求(由DCI中的NDI指示)来判断PUSCH是否成功译码。
冗余版本(redundancy version，RV)：用于指示传输所使用的冗余版本，其取值范围为0～3。
NR中的无线资源控制(radio resource control，RRC)连接态(connected)：UE和gNodeB建立了RRC连接。
RRC连接态移动性管理：可通过切换或者重定向的方式，将UE从原服务小区变更到目标小区。
Xn接口：5G基站和5G基站之间的接口，主要用于切换等信令交互。
NG接口：5G基站和5G核心网之间接口，主要交互核心网的非接入层(non-access  stratum，NAS)等信令以及用户的业务数据。
接入管理功能(access and mobility management function，AMF)网元：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
下面对本申请实施例可以应用的系统架构或者场景进行说明，如图1至图4所示，其中，图1是适用于本申请实施例的一例应用场景图。
图1中包括卫星以及终端类型网元。所述卫星为终端设备提供通信服务，卫星向终端设备传输下行数据，其中数据采用信道编码进行编码，信道编码后的数据经过星座调制后传输给终端设备；终端设备向卫星传输上行数据，上行数据也可以采用信道编码进行编码，编码后的数据经过星座调制后传输给卫星。
图2是适用于本申请实施例的再一例应用场景图，如图2所示，星间通信包括多个卫星之间的通信，传统的卫星星间链路通信系统可以分为：捕获、瞄准、跟踪(acquisition、pointing、tracking，APT)子系统和通信子系统两大部分。通信子系统负责星间信息的传输，是星间通信系统的主体；APT系统负责卫星之间的捕获、对准和跟踪，确定入射信号的来波方向，为捕获，调整发射波瞄准接收方向，为对准，在整个通信过程中，不断调整对准和捕获，为跟踪。为了尽量减少信道中的衰减和干扰影响，同时要求具有较高的保密性和传输率，必须实时的调整APT来不断适应变化。现有的APT系统均为光学系统，缺点在于光学对准难度大，需要机械调整指向。现有的通信子系统，多数为光通信系统，也有部分微波波段的系统，多采用单个高增益天线。现有的APT系统和通信子系统为独立的系统。缺点在于光通信容易受震动等影响，速率不稳定；毫米波频率低，通信容量低，天线需要机械调整指向。
本申请实施例可以应用于5G、卫星通信等无线通信系统中，系统架构如图3所示，图3是适用于本申请实施例的又一例应用场景图。无线通信系统通常由小区组成，每个小区包含一个基站(base station，BS)，基站向多个移动台(mobile station，MS)提供通信服务。其中基站包含基带单元(baseband unit，BBU)和远端射频单元(remote radio unit，RRU)。BBU和RRU可以放置在不同的地方，例如：RRU拉远，放置于高话务量的区域，BBU放置于中心机房。BBU和RRU也可以放置在同一机房。BBU和RRU也可以为一个机架下的不同部件。
图4是适用于本申请实施例的又一例应用场景图，本申请实施例还可以应用于图4所示的无线投屏架构等。
在上述场景中，由于卫星通信系统中UE的小区切换的发生主要来源于卫星的高速移动。在轨服务卫星都能稳定在设计的轨道上高速运行，各个卫星服务的小区范围在地面上也会稳定地依照规划的路径高速移动，因此UE接入的卫星网络小区会频繁且具有规律性的切换。另一方面，卫星网络服务的用户主要分布在城市之外、地面蜂窝网络未能覆盖的区域。该类区域不会存在城市中各类建筑物对无线信号造成的复杂反射，因此UE与卫星间的信道都是由视线传输(line of sight，LOS)路径构成，其信道传递函数主要取决于路径损失。又由于UE在触发切换(handover)时，UE接收到前后小区的测量信号强度满足一定判决条件，即前一小区信号强度小于某一阈值，或后一小区信号强度大于某一阈值。在切换发生时，UE与前后卫星几何距离近似；同一个星座系统中，卫星的天线系统设计 参数也会基本一致，因此，UE切换前后的信道近似，卫星通信系统具备进行“软合并”的条件。
如果卫星通信系统直接沿用NR的HARQ切换处理方式，直接清空当前HARQ进程的缓存，在下一个小区采用ARQ方式重新进行数据的传输，由于处于高层的ARQ传输方式所用的时延比处于低层的HARQ传输方式所用的时延要长，会导致增加本就相对较长的卫星通信时延，并且，采用ARQ方式传输的数据量比HARQ方式传输的数据量要大，当发生频繁切换时，无法保证HARQ进程的连续，不能支持对可靠度和时延同时有要求的业务，并且，虽然卫星通信系统具备进行“软合并”的条件，但是如果直接清空当前HARQ进程的缓存，则不能获得软合并编码增益。
需要说明的是，本申请实施例同样可以应用在终端设备执行小区间切换前的小区和切换后的小区的信道条件相似的场景中，本申请对此并不限定。
为解决上述问题，本申请提供了方法100，如图5所示，图5是本申请实施例的一例示意性流程图。
S110，第一终端设备与第一网络设备传输第一数据。
其中，第一数据对应第一混合自动重传请求HARQ进程。
上述方式中，第一终端设备与第一网络设备或第二网络设备之间的传输方式可以是上行传输也可以是下行传输，本申请对此不做限定。即，上述第一数据可以是上行数据也可以是下行数据。
S120，第一终端设备与第二网络设备传输第二数据。
第二数据对应第一HARQ进程，第二数据包括对第一数据进行重传处理的数据、针对第一数据的反馈信息中的至少一个。
在一种可能的实施方式中，第一终端设备是从第一网络设备切换至第二网络设备的终端设备。
上述第二数据可以是上行数据也可以是下行数据。
示例性地，上述第一终端设备从第一网络设备切换至第二网络设备的方式可以是第一终端设备基于第一参数从第一网络设备切换至第二网络设备，其中，第一参数包括以下信息的至少一种：
信号质量、第一终端设备的位置、第一网络设备的位置、触发切换的事件、触发切换的定时器、触发切换的时间、触发切换的时刻。
本申请对第一终端设备从第一网络设备切换至第二网络设备的方式不作限定。
上述方式中的在第一终端设备从第一网络设备切换至第二网络设备的情况下，表示第一终端设备在执行小区切换时，虽然与第二网络设备建立了连接，但是该小区切换并没有完成。
采用上述方式，使能终端设备在进行小区切换时，能够和小区切换的目的网络设备继续传输未结束的HARQ进程的数据，相比于目前的技术方案中清空HARQ缓存数据的方式，本申请中的上述方式能够减小通信时延，获得软合并编码增益，支持对可靠度和时延同时有要求的业务。
在一种可能的实施方式中，在第一终端设备从第一网络设备切换至第二网络设备的第一时段内，第一终端设备与第一网络设备传输第二数据，其中，第一时段包括第一终端设 备成功译码用于执行切换的第一无线资源控制RRC重配置消息的时刻至第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
采用上述方式，使能终端设备在上述第一时段内继续和网络设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式能够缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第一网络设备传输第二数据包括：在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功发送消息1MSG1的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
上述方式所处的场景可以是，当第一终端设备执行小区切换，并且接收到的RRC重配置消息中包括条件信息，其中，该条件信息用于指示当满足该条件时，第一终端设备发起非竞争的随机接入MSG1。
采用上述方式，使能终端设备在上述第一时段内继续和网络设备传输数据，相比于目前技术方案中在上述第一时段内终端设备和网络设备停止传输数据，本申请中的上述方式缩短了网络切换过程中，用户数据传输的中断时间，提升用户感知的数据吞吐、缩短了用户感知的时延。
在一种可能的实施方式中，第一终端设备将第一介质访问控制层MAC实体中的第一HARQ进程的数据复制到第二MAC实体中，其中，第一MAC实体对应第一网络设备，第二MAC实体对应第二网络设备。
采用上述方式，使能终端设备将未结束的上行HARQ进程数据保留，从而使能未结束的上行HARQ进程连续。
在一种可能的实施方式中，在第一终端设备与第二网络设备传输第二数据之前，方法包括：第一终端设备接收第一指示信息，第一指示信息用于指示第一终端设备与第二网络设备传输第二数据。
在一种可能的实施方式中，第一指示信息包括以下信息的一种或多种：第一HARQ进程的标识、第二网络设备的标识、第一资源，其中，第一资源为第二数据所占用的资源。
采用上述方式，使能终端设备更精确的了解要继续进行的HARQ进程、目的网络设备以及该HARQ进程对应的传输资源。
在一种可能的实施方式中，第一数据为上行数据，第二数据包括对第一数据进行重传处理的数据。
在一种可能的实施方式中，第一数据为下行数据，第二数据包括针对第一数据的反馈信息。
在一种可能的实施方式中，第一数据的反馈信息包括确认消息ACK或者否认应答NACK。
在一种可能的实施方式中，第一网络设备或者第二网络设备为卫星。
当网络侧为卫星时，采用上述方式能够强化卫星通信系统的时延优势。
下面针对不同场景对方法100进行详细说明。
考虑到当每一颗卫星的覆盖范围是一个小区，UE发生小区间的切换实际上是卫星间的切换。卫星之间存在星间链路，构成Xn接口。并且进行切换的卫星属于同一个星座，且归属于同一个AMF管辖。
本申请考虑了在此场景下，如何进行上行HARQ进程的切换，例如，图6中的方法200所示，图6是本申请实施例的再一例示意性流程图，图6中的源gNodeB#1(gNodeB#1可以理解为一个gNodeB，其它有关“#”的内容参见此处解释)属于卫星#1(图6中未示出)的覆盖范围(或称为源gNodeB#1属于源小区#1的覆盖范围)，目标gNodeB#1属于卫星#2(图6中未示出)的覆盖范围(或称为目标gNodeB#1属于目标小区#1的覆盖范围)，卫星#1与卫星#2之间构成Xn接口，并且属于同一个星座，且归属于同一个AMF管辖。源gNodeB#1为UE#1执行小区切换前的服务小区的基站，目标gNodeB#1为UE#1执行小区切换的目的服务小区的基站。
S210中，UE#1基于测量控制信息#A执行小区切换。
具体地，可分为以下步骤：
步骤a：源gNodeB#1通过RRC重配置(RRC reconfiguration)消息向UE#1下发测量控制信息#A。其中，测量控制信息#A包括测量对象(例如，同频测量、异频测量等)、测量配置(例如，UE需要测量的对象、小区列表、报告方式、测量标识、事件参数等)和测量间隙(GAP)配置等；
步骤b：UE#1通过RRC重配置完成(reconfiguration complete)消息向源gNodeB#1做出响应；
步骤c：UE#1根据收到的测量控制信息#A执行测量。UE#1对小区进行测量并判定达到测量的触发事件的条件后，上报测量报告信息#A1给源gNodeB#1，其中，测量报告信息#A1包括所测量的小区的信号的质量等信息；
步骤d：源gNodeB#1收到测量报告信息#A1后，根据测量报告信息#A1进行切换策略和目标小区(或者频点)判决。
步骤e：源gNodeB#1通过Xn链路发送切换请求(handover request)信息给选择的目标小区#1所在的目标gNodeB#1，发起切换请求。
步骤f：目标gNodeB#1收到切换请求信息后，进行准入控制，允许准入后分配给UE#1实例和传输资源。
步骤g：目标gNodeB#1回复切换请求确认(handover request acknowledge)消息给源gNodeB#1，允许切换入。如果有部分协议数据单元(protocol data unit，PDU)会话(session)切换入失败，切换请求确认消息中需要携带失败的PDU会话列表；
步骤h：源gNodeB#1发送RRC重配置消息给UE#1，要求UE#1执行切换到目标小区#1，其中，RRC重配置消息可以包括RRC重配置目标小区的ID(RRCReconfiguration target cell ID)、新小区无线网络临时标识(new cellradio network tempory identity，new C-RNTI)、安全算法(security algorithm)等信息；
步骤i：源gNodeB#1通过业务节点状态转移(service node status transfer，SNstatus transfer)信令将PDCP的SN号发送给目标gNodeB#1，在这之后，通过上行链路(uplink)传输缓存数据(buffered data)和用户面功能(user plane function，UPF)的新数据。
S220，源gNodeB#1发送信息#B，目标gNodeB#1接收信息#B。
其中，信息#B用于指示源gNodeB#1与UE#1之间未结束的上行HARQ进程，信息#B可以包括以下信息的一种或多种：
当前所有未结束的上行HARQ进程的缓存数据，包括各个未结束的上行HARQ进程对应的源gNodeB#1已经接收到的数据、源gNodeB#1已经译码出的数据中的至少一种，示例性的，此处的“未结束的上行HARQ进程”指的是UE#1发送给源gNodeB#1上行数据，但是源gNodeB#1还没有对该上行数据进行反馈ACK或NACK，或者反馈了NACK，但是还没有收到UE#1的重传数据，该条件下的上行HARQ进程为“未结束的上行HARQ进程”，或者是源gNodeB#1对该上行数据反馈了NACK，需要UE#1进行上行数据的重传；
当前所有未结束的上行HARQ进程的ID。
源gNodeB#1通过发送信息#B，以便于目标gNodeB#1掌握当前所有未结束的上行HARQ进程的状态及信息，拥有接管当前HARQ进程的能力。
S230，UE#1与目标gNodeB#1建立连接。
具体地，包括以下步骤：
步骤a：UE#1在目标gNodeB#1所在的目标小区发起非竞争的随机接入，发送消息1(message1，MSG1)，消息1包括随机接入前导码(preamble)序列；
步骤b：目标gNodeB#1作出随机接入响应，并发送消息2(message2，MSG2)；
步骤c：UE#1发送RRC重配置完成信息给目标gNodeB#1，UE#1空口切换到目标小区#1完成。
目前，在S210的步骤h结束时刻(即UE#1成功译码源gNodeB#1发送的RRC重配置消息)一直到S230的步骤c结束时刻(即目标gNodeB#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#A)，UE#1不再向源gNodeB#1发送上行数据，意味着UE#1中断未结束的上行HARQ进程的上行重传数据的传输，或者中断未结束的下行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的上行HARQ进程的数据的传输。
针对该问题，本申请设计以下方案：
在时段#A内，UE#1可继续向源gNodeB#1发送上行数据#A，该上行数据#A包括未结束的上行HARQ进程的上行重传数据，和/或未结束的下行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述上行数据#A还可以包括新的HARQ进程的上行数据。
在上述方案中，由于UE#1与源gNodeB#1之间的HARQ进程的数据会被更新，因此源gNodeB#1与目标gNodeB#1之间需要进行更新的HARQ进程的数据的传递，对此，本申请设计了以下方案：
源gNodeB#1在S210的步骤h中向UE#1发送RRC重配置消息后，经过时长#A后向目标gNodeB#1发送信息#Bg，并开始周期性地向目标gNodeB#1发送信息#Bg1、信息#Bg2…，一直到源gNodeB#1收到了AMF#1发送的结束标记(end marker)信息。其中，信息#Bg、信息#Bg1、信息#Bg2…为根据UE#1在时段#A内发送的上行数据#A更新后的信息#B，信息#Bg、信息#Bg1、信息#Bg2…可以包括更新的HARQ进程对应的数据，也可以包括未更新的HARQ进程对应的数据。
在一种可能的实施方式中，时长#A可以是预定义的。
在一种可能的实施方式中，时长#A的值可以是(2*RTT1–0.5*RTT2)，其中，RTT1为UE#1与源gNodeB#1或目标gNodeB#1的信号传输的往返时延，RTT2是源gNodeB#1与目标gNodeB#1间的信号传输的往返时延。
需要说明的是，时长#A的值也可以大于(2*RTT1–0.5*RTT2)，例如，当在时段#A内UE#1或者目标gNodeB#1发生了译码错误时。
示例性地，RTT1的值是540ms。
示例性地，RTT2的值是13.2ms(在方法200中，源gNodeB#1与目标gNodeB#1间存在星间通信)。
在一种可能的实施方式中，上述周期的长度可以是预定义的。
在一种可能的实施方式中，上述周期的长度可以是(0.5*RTT1)的n倍，n为大于0的整数。
在UE#1与目标gNodeB#1在上述时段#A由于交互信令重复发送，目标gNodeB#1收到RRC重配置完成信息超时的情况下，上述方案解决了源gNodeB#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标gNodeB#1的问题。
S240，目标gNodeB#1发送信息#C，UE#1接收信息#C。
其中，信息#C包括以下信息的至少一种：
信息#C1，用于指示UE#1当前所有未结束的上行HARQ进程是否需要重传，示例性的，信息#C1可以包括需要重传的上行HARQ进程的ID以及NACK数据，或者不需要重传的上行HARQ进程的ID以及ACK数据，应理解，此处的需要重传的上行HARQ进程或者是不需要重传的上行HARQ进程都包含于上述所有未结束的上行HARQ进程；
信息#C1a，用于指示UE#1需要重传的上行HARQ进程所对应的上行数据所占用的时频资源以及要发送的对象为目标gNodeB#1，示例性的，信息#C1a可以包括需要重传的上行HARQ进程的ID、对应的时频资源以及目标gNodeB#1的标识；
信息#C2，用于指示目标gNodeB#1为UE#1分配的目标小区#1的资源，该资源可用于目标gNodeB#1与UE#1之间进行新的数据的传输或者新的HARQ进程的HARQ数据的传输。
UE#1接收信息#C后，会优先按照目标gNodeB#1下发的信息#C的指示来响应HARQ操作。例如，UE#1针对未结束的上行HARQ进程#1可以向源gNodeB#1在时频资源#1上进行上行HARQ进程#1的上行数据的重传，也可以按照信息#C1a的指示向目标gNodeB#1在时频资源#2上进行上行HARQ进程#1的上行数据的重传，那么UE#1会优先选择后者的方案，即向目标gNodeB#1在时频资源#2上进行上行HARQ进程#1的上行数据的重传。
在一种可能的实施方式中，信息#C可以包含于下行控制信息(downlink control information，DCI)，承载于RRC信令中。
S250，UE#1发送响应信息#D，目标gNodeB#1接收响应信息#D。
具体地，UE#1根据信息#C发送响应信息#D。
示例性的，响应信息#D包括上行HARQ进程的ID以及对应的ACK或NACK数据。
S260，目标gNodeB#1发送信息#E，AMF#1接收信息#E。
具体地，信息#E可以是路径切换请求(path switch request)消息，目标gNodeB#1向AMF#1发送路径切换请求消息通知UE#1已经改变服务小区，路径切换请求消息携带了目标小区标识、所转换的PDU会话列表。核心网收到该消息后，更新下行通用无线分组业务隧道协议(general packet radio service tunneling protocol，GPRStunneling protocol)-U数据面，将基站侧的GTP-U地址修改为目标gNodeB#1的地址；
S270，目标gNodeB#1发送信息#F，UE#1接收信息#F。
具体地，目标gNodeB#1向UE#1发送信息#F，其中，信息#F用于指示UE#1与目标gNodeB#1进行上行数据的重传处理。
其中，信息#F可以包括以下信息的至少一种：
需要进行上行数据的重传处理的上行HARQ进程的ID、目标gNodeB#1的标识、上行数据的重传处理所占用的时频资源。
信息#F可以用于进一步保证UE#1切换到目标小区#1时HARQ进程的连续，即，如果UE#1根据信息#C向目标小区#1发送上行重传数据或者发送下行数据的反馈数据失败的话(由于在S250中，UE#1向目标小区#1发了响应信息，因此目标小区#1掌握哪些HARQ进程切换成功了，哪些HARQ进程没有切换成功)，还可以根据信息#F继续未结束的上行HARQ进程，以达到保证HARQ进程连续的目的。
S280，源gNodeB#1释放与UE#1的连接。
具体地，可以分为以下步骤：
步骤a：AMF#1向目标gNodeB#1回复路径切换请求确认(path switch request acknowledge)消息。如果AMF#1在路径切换请求确认消息中指示核心网未能建立的PDU会话，则目标gNodeB#1删除未能建立的PDU会话；
步骤b：目标gNodeB#1向源gNodeB#1发送UE上下文释放(UE context release)消息，源gNodeB#1收到该消息后释放与UE#1的连接；
在一种可能的实施方式中，在源gNodeB#1发送信息#B之后，在源gNodeB#1释放与UE#1的连接之前，如果产生了新的上行HARQ进程或者更新了HARQ进程的状态，那么源gNodeB#1可以有以下两种方式的处理：
方式一
继续进行该新的上行HARQ进程，对UE#1进行上行数据的反馈，直到结束该新的上行HARQ进程。
方式二
将需要回复NACK的HARQ进程的相关数据或者更新的HARQ进程的状态发给目标gNodeB#1，具体内容可以参考上述信息#B，在此不再赘述，如果是需要回复ACK的HARQ进程，那么源gNodeB#1将ACK数据发给UE#1即可。目标gNodeB#1接收到该数据后，可以将该数据是否需要重传以及如果需要重传，所占用的时频资源发给UE#1，具体内容参见信息#C。
在一种可能的实施方式中，目标gNodeB#1通过RRC重配置(RRCReconfiguration)消息下发目标小区#1的测量控制信息给UE#1，UE#1收到目标gNodeB#1下发的新的测量控制信息后，回复RRC重配置完成(RRCReconfigurationComplete)消息。
本申请还考虑了在方法200的场景中，如何进行下行HARQ进程的切换，如方法300 所示，其中，源gNodeB#1、目标gNodeB#1、AMF#1的说明参见方法200中的说明，在此不再赘述。
S310中，UE#1基于测量控制信息#A执行小区切换。
具体的步骤可以参见方法S210，在此不再赘述。
S320，UE#1与目标gNodeB#1建立连接。
具体地步骤可以参见方法S230，在此不再赘述。
在一种可能的实施方式中，UE#1将第一介质访问控制层MAC实体中的未结束的HARQ进程的数据复制到第二MAC实体中，其中，第一MAC实体为UE#1与源gNodeB#1之间的MAC实体，第二MAC实体为UE#1与目标gNodeB#1之间的MAC实体。
S330，目标gNodeB#1发送信息#E，AMF#1接收信息#E。
具体内容参见方法S260，在此不再赘述。
S340，源gNodeB#1释放与UE#1的连接。
具体地，可以分为以下步骤：
步骤a：AMF#1向目标gNodeB#1回复路径切换请求确认(path switch request acknowledge)消息。如果AMF#1在路径切换请求确认消息中指示核心网未能建立的PDU会话，则目标gNodeB#1删除未能建立的PDU会话；
步骤b：目标gNodeB#1向源gNodeB#1发送UE上下文释放(UE context release)消息，源gNodeB#1收到该消息后释放与UE#1的连接；
在一种可能的实施方式中，如果源gNodeB#1还有未发完的下行数据需要发送给UE#1，那么在源gNodeB#1释放与UE#1的连接之前，可以继续发送该未发完的下行数据，但是不再发送新的下行数据。
S350，源gNodeB#1向目标gNodeB#1发送信息#B1。
其中，信息#B1用于指示源gNodeB#1与UE#1之间未结束的下行HARQ进程的原始下行HARQ进程信息，信息#B1可以包括以下信息的一种或多种：
各个未结束的下行HARQ进程对应的冗余版本数据，各个未结束的下行HARQ进程对应的UE#1发送的NACK数据，示例性的，此处的“未结束的下行HARQ进程”指的是源gNodeB#1向UE#1发送的下行数据，但是UE#1还没有对该下行数据进行反馈ACK或NACK，该条件下的下行HARQ进程为“未结束的下行HARQ进程”，或者是UE#1对该下行数据反馈了NACK，需要源gNodeB#1进行该下行数据的重传；
当前所有未结束的下行HARQ进程的ID；
当前所有未结束的下行HARQ进程的冗余版本号，包括各个未结束的下行HARQ进程的冗余版本的状态，例如未结束的下行HARQ进程的冗余版本已经发送的次数等。
在一种可能的实施方式中，如果源gNodeB#1收到UPF下来的数据或源gNodeB#1的缓存中还有未发过的下行数据，那么源gNodeB#1需要把该下行数据发给目标gNodeB#1，该下行数据可以包含于信息#B1中。
源gNodeB#1通过发送信息#B1，以便于目标gNodeB#1掌握当前所有未结束的下行HARQ进程的状态及信息，拥有接管当前HARQ进程的能力。
S360，目标gNodeB#1发送信息#C3，UE#1接收信息#C3。
其中，信息#C3用于指示UE#1针对当前所有未结束的下行HARQ进程的反馈数据向 目标gNodeB#1发送以及反馈数据所占的时频资源。
示例性地，信息#C3可以包括以下信息的至少一种：
当前未结束的下行HARQ进程的ID、当前未结束的下行HARQ进程的ID对应的反馈数据所占的时频资源、目标gNodeB#1的标识。
在一种可能的实施方式中，信息#C3还可以是目标gNodeB#1针对UE#1反馈了NACK数据的下行数据的冗余版本数据(即进行重传处理的下行数据)、以及对应的下行HARQ进程的ID。
UE#1接收信息#C3后，会优先按照目标gNodeB#1下发的信息#C3的指示来响应HARQ操作。例如，UE#1的针对未结束的下行HARQ进程#1的反馈数据可以向源gNodeB#1在时频资源#1上发送，也可以按照信息#C3的指示向目标gNodeB#1在时频资源#2上发送反馈数据，那么UE#1会优先选择后者的方案，即向目标gNodeB#1在时频资源#2上发送反馈数据。
S370，UE#1发送响应信息#D1，目标gNodeB#1接收响应信息#D1。
具体地，UE#1通过响应信息#D1对目标gNodeB#1发送的信息#C3作出反馈。
示例性的，响应信息#D1包括下行HARQ进程的ID和/或对应的ACK或NACK数据。
在方法200的场景中，针对下行HARQ进程的切换，本申请还提供了方法400，其中，源gNodeB#1、目标gNodeB#1、AMF#1的说明参见方法200中的说明，在此不再赘述。
S410，UE#1基于测量控制信息#A执行小区切换。
具体地步骤参见方法S210，在此不再赘述。
S420，源gNodeB#1向目标gNodeB#1发送信息#B1。
其中，信息#B1的内容参见方法S350，在此不再赘述。
S430，UE#1与目标gNodeB#1建立连接。
具体地步骤参见方法S230，在此不再赘述。
目前，在S410的步骤h(参见S210的步骤h)开始时刻(即源gNodeB#1发出RRC重配置消息后)一直到S430的步骤c(参见S230的步骤c)结束时刻(即目标gNodeB#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#B)，源gNodeB#1不再向UE#1发送下行数据，意味着源gNodeB#1中断未结束的下行HARQ进程的下行重传数据的传输，或者中断未结束的上行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的下行HARQ进程的数据的传输。
针对该问题，本申请设计以下方案：
在时段#B内，源gNodeB#1可继续向UE#1发送下行数据#A，该下行数据#A包括未结束的下行HARQ进程的下行重传数据，和/或未结束的上行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述下行数据#A还可以包括新的下行HARQ进程的数据，例如，UPF#1已经分配给源gNodeB#1的下行用户面数据。
在上述方案中，由于UE#1与源gNodeB#1之间的HARQ进程的数据会被更新，因此源gNodeB#1与目标gNodeB#1之间需要进行更新的HARQ进程的数据的传递，对此，本申请设计了以下方案：
源gNodeB#1在S210的步骤h中向UE#1发送RRC重配置消息后，经过时长#A后向 目标gNodeB#1发送信息#B1g，并开始周期性地向目标gNodeB#1发送信息#B1g1、信息#B1g2…，一直到源gNodeB#1收到了AMF#1发送的结束标记(end marker)信息。其中，信息#B1g、信息#B1g1、信息#B1g2…为根据UE#1在时段#B内发送的下行数据#A更新后的信息#B1，信息#B1g、信息#B1g1、信息#B1g2…可以包括更新的HARQ进程对应的数据，也可以包括未更新的HARQ进程对应的数据。
时长#A的内容参见方法200的说明，在此不再赘述。
上述周期的长度参见方法200的说明，在此不再赘述。
在UE#1与目标gNodeB#1在上述时段#B由于交互信令重复发送，目标gNodeB#1收到RRC重配置完成信息超时的情况下，上述方案解决了源gNodeB#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标gNodeB#1的问题。
S440，目标gNodeB#1发送信息#C3，UE#1接收信息#C3。
其中，信息#C3的内容参见方法S360，在此不再赘述。
在一种可能的实施方式中，在源gNodeB#1发送给目标gNodeB#1信息#B1之后，并在目标gNodeB#1发送信息#C3之前，如果源gNodeB#1向UE#1发送了新的下行数据或者收到了UE#1的新的反馈数据，那么源gNodeB#1需要再一次向目标gNodeB#1同步该产生的新的状态。例如，源gNodeB#1需要把该新的下行数据所对应的所有HARQ进程的数据以及对应的HARQ进程的ID发给目标gNodeB#1，又例如，源gNodeB#1需要接收到的UE#1的新的反馈数据以及对应的HARQ进程的ID发给目标gNodeB#1，以便于目标gNodeB#1掌握最新的未结束的HARQ进程的数据。目标gNodeB#1收到源gNodeB#1发送的新的HARQ进程数据后，可以将该新的HARQ进程数据对应的控制信息包含于信息#C3中，发给UE#1，具体内容参见信息#C3，在此不再赘述。
S450，UE#1发送响应信息#D1，目标gNodeB#1接收响应信息#D1。
其中，响应信息#D1可以参见方法S370，在此不再赘述。
S460，目标gNodeB#1发送信息#E，AMF#1接收信息#E。
具体地，信息#E可以是路径切换请求(path switch request)消息，目标gNodeB#1向AMF#1发送路径切换请求消息通知UE#1已经改变服务小区，路径切换请求消息携带了目标小区标识、所转换的PDU会话列表。核心网收到该消息后，更新下行通用无线分组业务隧道协议(general packet radio service tunneling protocol，GPRStunneling protocol)-U数据面，将基站侧的GTP-U地址修改为目标gNodeB#1的地址；
S470，目标gNodeB#1发送信息#F1，UE#1接收信息#F1。
具体地，目标gNodeB#1向UE#1发送信息#F1，其中，信息#F1用于指示UE#1与目标gNodeB#1进行下行数据的反馈。
其中，信息#F1可以包括以下信息的至少一种：
需要UE#1进行反馈的下行HARQ进程的ID、目标gNodeB#1的标识、反馈数据所占用的时频资源。
信息#F1可以用于进一步保证UE#1切换到目标小区#1时HARQ进程的连续，即，如果UE#1接收的信息#C有部分信息失败的话(由于在S450中，UE#1向目标小区#1发了响应信息，因此目标小区#1掌握哪些HARQ进程切换成功了，哪些HARQ进程没有切换成功)，还可以通过发送信息#F1继续未结束的下行HARQ进程，以达到保证HARQ进 程连续的目的。
S480，源gNodeB#1释放与UE#1的连接。
具体步骤可以参见方法S280，在此不再赘述。
在一种可能的实施方式中，如果源gNodeB#1有未发完的下行数据，那么可以继续下发该下行数据，发完该下行数据后，形成了新的HARQ进程，但是不再发送新的数据。此时需要把该新的HARQ进程的相关数据再次发给目标gNodeB#1，该新的HARQ进程的相关数据的具体内容可参见信息#B1。在该情况下，如果源gNodeB#1收到UPF下来的数据或源gNodeB#1的缓存中还有未发过的下行数据，那么源gNodeB#1需要把该下行数据发给目标gNodeB#1，该下行数据可以包含于信息#B1中。
在一种可能的实施方式中，目标gNodeB#1通过RRC重配置(RRCReconfiguration)消息下发目标小区#1的测量控制信息给UE#1，UE#1收到目标gNodeB#1下发的新的测量控制信息后，回复RRC重配置完成消息(RRCReconfigurationComplete)。
通过方法200、300或400，能够在多个卫星间存在Xn接口情况下，当UE#1需要进行小区间的切换时，使能UE#1进行的HARQ进程能够连续，强化卫星通信的时延优势，获得软合并编码增益。
本申请实施例还考虑了每一颗卫星的覆盖范围是一个小区，用户发生小区切换实际上是卫星间的切换。但切换前后的两颗卫星之间通过NG接口和两个核心网连接，这两个核心网属于同一个AMF管辖。
本申请考虑了在此场景下，如何进行上行HARQ进程的切换，例如，图7中的方法500所示，图7是本申请实施例的又一例示意性流程图，图7中的源gNodeB#1属于卫星#1(图7中未示出)的覆盖范围(或称为源gNodeB#1属于源小区#1的覆盖范围)，目标gNodeB#1属于卫星#2(图7中未示出)的覆盖范围(或称为目标gNodeB#1属于目标小区#1的覆盖范围)，卫星#1与核心网#1(图7中未示出)之间构成Xn接口，卫星#2与核心网#2之间构成Xn接口，核心网#1和核心网#2(图7中未示出)归属于同一个AMF管辖。源gNodeB#1为UE#1执行小区切换前的服务小区覆盖范围下的基站，目标gNodeB#1为UE#1执行小区切换的目的服务小区覆盖范围下的基站。
S510中，UE#1基于测量控制信息#A执行小区切换。
具体地，可分为以下步骤：
步骤a：源gNodeB#1通过RRC重配置(RRCReconfiguration)消息向UE#1下发测量控制信息#A。其中，测量控制信息#A参见方法200中的描述，在此不再赘述；
步骤b：UE#1通过RRC重配置完成(ReconfigurationComplete)消息向源gNodeB#1做出响应。
步骤c：UE#1根据收到的测量控制信息#A执行测量。UE#1对小区进行测量并判定达到测量的触发事件的条件后，上报测量报告信息#A1给源gNodeB#1，其中，测量报告信息#A1包括所测量的小区的信号的质量等信息；
步骤d：源gNodeB#1收到测量报告信息#A1后，根据测量报告信息#A1进行切换策略和目标小区(或者频点)判决。
步骤e：源gNodeB#1通过NG链路发送切换请求(handover required)消息给AMF#1，发起切换请求，该消息包含目标gNodeB#1的ID、执行数据转发的PDU会话列表等；
步骤f：AMF#1向指定的目标小区#1所在的目标gNodeB#1发送切换请求消息，发起切换请求，目标gNodeB#1根据消息中的跟踪标识(TraceID)、用户文件标识(subscriber profile identity，SPID)识别出UE#1；
步骤g：目标gNodeB#1收到切换请求后，进行准入控制，允许准入后分配UE#1实例和传输资源；
步骤h：目标gNodeB#1回复切换请求确认(handover required acknowledge)消息给AMF#1，允许切换入。如果有部分PDU会话切换入失败，消息中需要携带失败的PDU会话列表；
步骤i：AMF#1向源gNodeB#1发送切换命令(handover command)消息，该消息包含目标gNodeB#1的地址和用于转发的隧道端点标识符(tunnel endpoint identifier，TEID)列表，包含需要释放的承载列表；
步骤j：源gNodeB#1发送RRC重配置消息给UE，要求UE执行切换到目标小区#1；
步骤k：源gNodeB#1将PDCP的SN号通过上行RAN状态传递(uplink RAN status transfer)发送给AMF#1；
步骤l：AMF#1再通过下行RAN状态传递(downlink RAN status transfer)消息将PDCP的SN号发送给目标gNodeB#1，在这之后，还会进行相应的缓存数据和UPF的数据传输；
S520，源gNodeB#1通过AMF#1向目标gNodeB#1发送信息#B。
其中，信息#B用于指示源gNodeB#1与UE#1之间未结束的上行HARQ进程，信息#B的内容可参见方法S220中的说明，在此不再赘述。
源gNodeB#1通过发送信息#B，以便于目标gNodeB#1掌握当前所有未结束的上行HARQ进程的状态及信息，拥有接管当前HARQ进程的能力。
S530，UE#1与目标gNodeB#1建立连接。
具体地，包括以下步骤：
步骤a：UE#1在目标gNodeB#1所在的目标小区#1发起非竞争的随机接入，发送消息1(message1，MSG1)，消息1包括随机接入前导码(preamble)序列；
步骤b：目标gNodeB#1作出随机接入响应，并发送消息2(message2，MSG2)；
步骤c：UE#1发送RRC重配置完成信息给目标gNodeB#1，UE#1空口切换到目标小区#1完成。
目前，在S510的步骤j结束时刻(即UE#1成功译码源gNodeB#1发送的RRC重配置消息)一直到S530的步骤c结束时刻(即目标gNodeB#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#A1)，UE#1不再向源gNodeB#1发送上行数据，意味着UE#1中断未结束的上行HARQ进程的上行重传数据的传输，或者中断未结束的下行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的上行HARQ进程数据的传输。
针对该问题，本申请设计以下方案：
在时段#A内，UE#1可继续向源gNodeB#1发送上行数据#A，该上行数据#A包括未结束的上行HARQ进程的上行重传数据，和/或未结束的下行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述上行数据#A还可以包括新的上行HARQ进程的数据。
在上述方案中，由于UE#1与源gNodeB#1之间的HARQ进程的数据会被更新，因此源gNodeB#1与目标gNodeB#1之间需要进行更新的HARQ进程的数据的传递，对此，本申请设计了以下方案：
源gNodeB#1在S510的步骤j中向UE#1发送RRC重配置消息后，经过时长#A1后向目标gNodeB#1发送信息#Bg，并开始周期性地向目标gNodeB#1发送信息#Bg1、信息#Bg2…，一直到源gNodeB#1收到了AMF#1发送的结束标记(end marker)信息。其中，信息#Bg、信息#Bg1、信息#Bg2…为根据UE#1在时段#A1内发送的上行数据#A更新后的信息#B，信息#Bg、信息#Bg1、信息#Bg2…可以包括更新的HARQ进程对应的数据，也可以包括未更新的HARQ进程对应的数据。
在一种可能的实施方式中，时长#A1可以是预定义的。
在一种可能的实施方式中，时长#A1的值可以是(2*RTT3–RTT4)，其中，RTT3为UE#1与源gNodeB#1或目标gNodeB#1的信号传输的往返时延，RTT4是源gNodeB#1发信号到核心网的时延与核心网发信号到目标gNodeB#1的时延的和(在方法500中，源gNodeB#1与目标gNodeB#1的数据传输需要通过核心网侧(AMF#1))。
需要说明的是，时长#A1的值也可以大于(2*RTT3–RTT4)，例如，当在时段#A1内UE#1或者目标gNodeB#1发生了译码错误时。
示例性地，RTT1的值是540ms。
在一种可能的实施方式中，上述周期的长度可以是预定义的。
在一种可能的实施方式中，上述周期的长度可以是(0.5*RTT3)的n倍，n为大于0的整数。
在UE#1与目标gNodeB#1在上述时段#A1由于交互信令重复发送，目标gNodeB#1收到RRC重配置完成信息超时的情况下，上述方案解决了源gNodeB#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标gNodeB#1的问题。
S540，目标gNodeB#1发送信息#C，UE#1接收信息#C。
其中，信息#C的内容参见方法S240，在此不再赘述。
UE#1接收信息#C后，会优先按照目标gNodeB#1下发的信息#C的指示来响应HARQ操作。例如，UE#1针对未结束的上行HARQ进程#1可以向源gNodeB#1在时频资源#1上进行上行HARQ进程#1的上行数据的重传，也可以按照信息#C的指示向目标gNodeB#1在时频资源#2上进行上行HARQ进程#1的上行数据的重传，那么UE#1会优先选择后者的方案，即向目标gNodeB#1在时频资源#2上进行上行HARQ进程#1的上行数据的重传。
在一种可能的实施方式中，信息#C可以是下行控制信息(downlink control information，DCI)，承载于RRC信令中。
S550，UE#1发送响应信息#D，目标gNodeB#1接收响应信息#D。
具体地，UE#1根据信息#C发送响应信息#D，其中，响应信息#D的内容参见方法S250，在此不再赘述。
S560，目标gNodeB#1发送信息#E1，AMF#1接收信息#E1。
具体地，信息#E1可以是切换通知(handover notify)消息，用于通知AMF#1，UE#1已经接入到目标小区#1，基于NG切换已经完成。
S570，目标gNodeB#1发送信息#F，UE#1接收信息#F。
具体地，目标gNodeB#1向UE#1发送信息#F，其中，信息#F用于指示UE#1与目标gNodeB#1进行上行数据的重传处理。信息#F的内容参见方法200，在此不再赘述。
S580，源gNodeB#1释放与UE#1的连接。
具体地，可以分为以下步骤：
步骤a：AMF#1向源gNodeB#1发送UE上下文释放命令(UE context release command)消息，源gNodeB#1收到该消息后释放与UE#1的连接；
在一种可能的实施方式中，在源gNodeB#1发送信息#B之后，在源gNodeB#1释放与UE#1的连接之前，如果产生了新的上行HARQ进程，那么源gNodeB#1处理的方式参见方法S280中的方式一和方式二，在此不再赘述。
在一种可能的实施方式中，目标gNodeB#1通过RRC重配置(RRCReconfiguration)消息下发新小区的测量控制信息给UE#1，UE#1收到目标gNodeB#1下发的新的测量控制信息后，回复RRC重配置完成消息(RRCReconfigurationComplete)。
本申请还考虑了在方法500的场景中，如何进行下行HARQ进程的切换，例如方法600，其中，源gNodeB#1、目标gNodeB#1、AMF#1的说明参见方法500中的说明，在此不再赘述。
S610中，UE#1基于测量控制信息#A执行小区切换。
具体的步骤可以参见方法S510，在此不再赘述。
S620，UE#1与目标gNodeB#1建立连接。
具体地步骤可以参见方法S530，在此不再赘述。
在一种可能的实施方式中，UE#1将第一MAC实体中的未结束的HARQ进程的数据复制到第二MAC实体中，其中，第一MAC实体为UE#1与源gNodeB#1之间的MAC实体，第二MAC实体为UE#1与目标gNodeB#1之间的MAC实体。
S630，目标gNodeB#1发送信息#E1，AMF#1接收信息#E1。
具体内容参见方法S560，在此不再赘述。
S640，源gNodeB#1释放与UE#1的连接。
具体地，可以分为以下步骤：
步骤a：AMF#1向源gNodeB#1发送UE上下文释放命令(UE context release command)消息，源gNodeB#1收到该消息后释放与UE#1的连接；
在一种可能的实施方式中，如果源gNodeB#1还有未发完的下行数据需要发送给UE#1，那么在源gNodeB#1释放与UE#1的连接之前，可以继续发送该未发完的下行数据，但是不再发送新的下行数据。
S650，源gNodeB#1向目标gNodeB#1发送信息#B1。
其中，信息#B1用于指示源gNodeB#1与UE#1之间未结束的下行HARQ进程，信息#B1的内容可以参见方法S350，在此不再赘述。
在一种可能的实施方式中，如果源gNodeB#1收到UPF下来的数据或源gNodeB#1的缓存中还有未发过的下行数据，那么源gNodeB#1需要把该下行数据发给目标gNodeB#1，该下行数据可以包含于信息#B1中。
源gNodeB#1通过发送信息#B1，以便于目标gNodeB#1掌握当前所有未结束的下行HARQ进程的状态及信息，拥有接管当前HARQ进程的能力。
S660，目标gNodeB#1发送信息#C3，UE#1接收信息#C3。
其中，信息#C3用于指示UE#1针对当前所有未结束的下行HARQ进程的反馈数据向目标gNodeB#1发送以及反馈数据所占的时频资源。信息#C3的具体内容可参见方法S360，在此不再赘述。
UE#1接收信息#C3后，会优先按照目标gNodeB#1下发的信息#C3的指示来响应HARQ操作。例如，UE#1的针对未结束的下行HARQ进程#1的反馈数据可以向源gNodeB#1在时频资源#1上发送，也可以按照信息#C3的指示向目标gNodeB#1在时频资源#2上发送反馈数据，那么UE#1会优先选择后者的方案，即向目标gNodeB#1在时频资源#2上发送反馈数据。
S670，UE#1发送响应信息#D1，目标gNodeB#1接收响应信息#D1。
具体地，UE#1通过响应信息#D1对目标gNodeB#1发送的信息#C3作出反馈。
示例性的，响应信息#D1包括下行HARQ进程的ID和/或对应的ACK或NACK数据。
在方法500的场景中，针对下行HARQ进程的切换，本申请还提供了方法700，源gNodeB#1、目标gNodeB#1、AMF#1的说明参见方法500中的说明，在此不再赘述。
S710，UE#1基于测量控制信息#A执行小区切换。
具体地步骤参见方法S510，在此不再赘述。
S720，源gNodeB#1向目标gNodeB#1发送信息#B1。
其中，信息#B1的内容参见方法S350，在此不再赘述。
S730，UE#1与目标gNodeB#1建立连接。
具体的步骤参见方法S530，在此不再赘述。
目前，在S710的步骤j开始时刻(即源gNodeB#1发出RRC重配置消息后)一直到S730的步骤c结束时刻(即目标gNodeB#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#B1)，源gNodeB#1不再向UE#1发送下行数据，意味着源gNodeB#1中断未结束的下行HARQ进程的下行重传数据的传输，或者中断未结束的上行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的下行HARQ进程的数据的传输。
针对该问题，本申请设计以下方案：
在时段#B1内，源gNodeB#1可继续向UE#1发送下行数据#A，该下行数据#A包括未结束的下行HARQ进程的下行重传数据，和/或未结束的上行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述下行数据#A还可以包括新的下行HARQ进程的数据，例如，UPF#1已经分配给源gNodeB#1的下行用户面数据。
在上述方案中，由于UE#1与源gNodeB#1之间的HARQ进程的数据会被更新，因此源gNodeB#1与目标gNodeB#1之间需要进行更新的HARQ进程的数据的传递，对此，本申请设计了以下方案：
源gNodeB#1在S510的步骤j中向UE#1发出RRC重配置消息后，经过时长#A1后向目标gNodeB#1发送信息#Bg，并开始周期性地向目标gNodeB#1发送信息#Bg1、信息#Bg2…，一直到源gNodeB#1收到了AMF#1发送的结束标记(end marker)信息。其中，信息#Bg、信息#Bg1、信息#Bg2…为根据UE#1在时段#A1内发送的上行数据#A更新后的信息#B，信息#Bg、信息#Bg1、信息#Bg2…可以包括更新的HARQ进程对应的数据， 也可以包括未更新的HARQ进程对应的数据。
时长#A1参见方法500的说明，在此不再赘述。
周期的长度参见方法500的说明，在此不再赘述。
在UE#1与目标gNodeB#1在上述时段#A1由于交互信令重复发送，目标gNodeB#1收到RRC重配置完成信息超时的情况下，上述方案解决了源gNodeB#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标gNodeB#1的问题。
S740，目标gNodeB#1发送信息#C3，UE#1接收信息#C3。
其中，信息#C3的内容参见方法S360，在此不再赘述。
在一种可能的实施方式中，在源gNodeB#1发送给目标gNodeB#1信息#B1之后，并在目标gNodeB#1发送信息#C3之前，如果源gNodeB#1向UE#1发送了新的下行数据或者收到了UE#1的新的反馈数据，那么源gNodeB#1需要向目标gNodeB#1同步该产生的新的状态。例如，源gNodeB#1需要把该新的下行数据所对应的所有HARQ进程的数据以及对应的HARQ进程的ID发给目标gNodeB#1，又例如，源gNodeB#1需要接收到的UE#1的新的反馈数据以及对应的HARQ进程的ID发给目标gNodeB#1，以便于目标gNodeB#1掌握最新的未结束的HARQ进程的数据。目标gNodeB#1收到源gNodeB#1发送的新的HARQ进程数据后，可以将该新的HARQ进程数据对应的控制信息包含于信息#C3中，发给UE#1，具体内容参见信息#C3，在此不再赘述。
S750，UE#1发送响应信息#D1，目标gNodeB#1接收响应信息#D1。
其中，响应信息#D1可以参见方法S370，在此不再赘述。
S760，目标gNodeB#1发送信息#E1，AMF#1接收信息#E1。
其中，信息#E1的内容参见方法S560，在此不再赘述。
S770，目标gNodeB#1发送信息#F1，UE#1接收信息#F1。
具体地，信息#F1用于指示UE#1与目标gNodeB#1进行下行数据的反馈。信息#F1的内容参见方法S470，在此不再赘述。
S780，源gNodeB#1释放与UE#1的连接。
具体步骤可以参见方法S580，在此不再赘述。
在一种可能的实施方式中，如果源gNodeB#1有未发完的下行数据，那么可以继续下发该下行数据，发完该下行数据后，形成了新的HARQ进程，但是不再发送新的数据。此时需要把该新的HARQ进程的相关数据再次发给目标gNodeB#1，该新的HARQ进程的相关数据的具体内容可参见信息#B1。在该情况下，如果源gNodeB#1收到UPF下来的数据或源gNodeB#1的缓存中还有未发过的下行数据，那么源gNodeB#1需要把该下行数据发给目标gNodeB#1，该下行数据可以包含于信息#B1中。
在一种可能的实施方式中，目标gNodeB#1通过RRC重配置(RRCReconfiguration)消息下发新小区的测量控制信息给UE#1，UE#1收到目标gNodeB#1下发的新的测量控制信息后，回复RRC重配置完成消息(RRCReconfigurationComplete)。
通过方法500、600或700，能够在多个卫星间不存在Xn接口情况下，但仍在同一个AMF管辖的范围内并存在NG接口情况下，当UE#1需要进行小区间的切换时，使能UE#1进行的HARQ进程能够连续，强化卫星通信的时延优势，获得软合并编码增益。
本申请实施例还考虑了UE切换前后的小区属于同一个基站(gNodeB-DU)管辖，并 且前后小区归属于同一个gNodeB-DU，前后小区属于同一个gNodeB-CU控制，在此场景中，一颗卫星的多个波束划分成不同小区，用户发生的小区间切换实际上是同一颗卫星服务的不同小区间进行的切换。例如，图8中的方法800所示，图8是本申请实施例的又一例示意性流程图，图8中的UE#1切换前后的小区(切换前为源小区#1，切换后为目标小区#1)属于gNodeB-DU#1，并且属于同一个gNodeB-CU控制。
S810中，UE#1基于测量控制信息#A执行小区切换。
具体地，可分为以下步骤：
步骤a：gNodeB-CU#1通过RRC重配置(RRC reconfiguration)消息向UE#1下发测量控制信息#A，其中，测量控制信息#A的内容参见方法200；
步骤b：UE#1回复RRC重配置完成(RRC reconfiguration complete)消息给gNodeB-CU#1；
步骤c：UE#1根据测量控制信息#A执行测量，并向gNodeB-CU#1上报邻区的测量报告；
步骤d：gNodeB-CU#1根据测量报告携带的物理层小区标识(physical cell identifier，PCI)PCI，判决切换的目标小区#1与源小区#1同属一个基站，并启动站内切换流程，目标小区#1根据UE#1在源小区#1的上下文做准入判决；
步骤e：gNodeB-CU#1发送UE上下文建立请求(UE context setup request)消息给gNodeB-DU#1，向gNodeB-DU#1为目标小区#1申请给UE#1的资源；
步骤f：如果gNodeB-DU#1为UE#1分配资源成功，回复UE上下文建立响应(UE context setup response)消息给gNodeB-CU#1；
步骤g：gNodeB-CU#1发送UE上下文修改请求(UE context modification request)消息给gNodeB-DU#1，用于指示gNodeB-DU#1下发停止调度源小区#1的L2信令的指示信息；
步骤h：gNodeB-DU#1回复UE上下文修改响应(UE context modification response)消息给gNodeB-CU#1；
S820，gNodeB-DU#1保留信息#B2，即不清空信息#B2。
即，源小区#1将信息#B2拷贝到目标小区#1对应的内存中，而源小区#1和目标小区#1都由gNodeB-DU#1管辖。
其中，信息#B2用于指示源小区#1与UE#1之间未完成的HARQ进程，
当源小区#1与UE#1之间未完成的HARQ进程是下行HARQ进程，信息#B2可以包括各个未结束的下行HARQ进程对应的原始下行HARQ进程信息，示例性地，可以包括以下信息的一种或多种：
各个未结束的下行HARQ进程对应的冗余版本数据，各个未结束的下行HARQ进程对应的UE#1发送的NACK数据；
当前所有未结束的下行HARQ进程的ID；
当前所有未结束的下行HARQ进程的冗余版本号，例如未结束的下行HARQ进程的冗余数据已经发送的版本等。
当源小区#1与UE#1之间未完成的HARQ进程是上行HARQ进程，信息#B2可以包括以下信息的一种或多种：
当前所有未结束的上行HARQ进程的缓存数据，包括各个未结束的上行HARQ进程对应的源gNodeB#1已经接收到的数据、源gNodeB#1已经译码出的数据中的至少一种；
当前所有未结束的上行HARQ进程的ID。
gNodeB-DU#1通过保留信息#B2，以便于目标小区#1掌握当前所有HARQ进程的状态及信息，拥有接管当前HARQ进程的能力。
S830，UE#1与目标小区#1建立连接。
具体地，可分为以下步骤：
步骤a：gNodeB-CU#1给UE#1发送RRC重配置消息，该消息携带了目标小区#1的目标频点、目标小区#1的PCI以及给UE#1配置的小区无线网络临时标识(cellradio network tempory identity，C-RNTI)和专用随机接入前导码；
步骤b：UE#1在目标小区#1发起非竞争的随机接入，发送消息1(message1，MSG1)，消息1包括随机接入前导码序列。
步骤c：gNodeB-DU#1作出随机接入响应，并发送消息2(message2，MSG2)；
步骤d：UE#1发送RRC重配置完成信息给gNodeB-CU#1，UE#1接入到目标小区#1。
目前，在S830的步骤a结束时刻(即UE#1成功译码gNodeB-CU#1发送的RRC重配置消息)一直到S830的步骤d结束时刻(即gNodeB-CU#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#A2)，UE#1不再向源小区#1发送上行数据，意味着UE#1中断未结束的上行HARQ进程的上行重传数据的传输，或者中断未结束的下行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的上行HARQ进程的数据的传输。
针对该问题，本申请设计以下方案：
在时段#A2内，UE#1可继续向源小区#1发送上行数据#A，该上行数据#A包括未结束的上行HARQ进程的上行重传数据，和/或未结束的下行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述上行数据#A还可以包括新的HARQ进程的上行数据。
在上述方案中，由于UE#1与源小区#1之间的HARQ进程的数据会被更新，因此源小区#1需要向目标小区#1对应的内存拷贝当前需要进行更新的HARQ进程的数据，对此，本申请设计了以下方案：
源小区#1在S830的步骤a中gNodeB-CU#1向UE#1发出RRC重配置消息后，经过时长#A2后向目标小区#1拷贝信息#B2g，并开始周期性地向目标小区#1发送信息#B2g1、信息#B2g2…，一直到源小区#1收到了gNodeB-CU#1发来的UE上下文释放命令(UE context release command)。其中，信息#B2g、信息#B2g1、信息#B2g2…为根据UE#1在时段#A2内发送的上行数据#A更新后的信息#B2，信息#B2g、信息#B2g1、信息#B2g2…可以包括更新的HARQ进程对应的数据，也可以包括未更新的HARQ进程对应的数据。
在一种可能的实施方式中，时长#A2可以是预定义的。
在一种可能的实施方式中，时长#A2的值可以是(2*RTT5)，其中，RTT5为UE#1与gNodeB-DU#1的信号传输的往返时延。
示例性地，RTT5的值是540ms。
需要说明的是，时长#A2的值也可以大于(2*RTT5)，例如，当在时段#A2内UE#1 或者目标小区#1发生了译码错误时。
在一种可能的实施方式中，上述周期的长度可以是预定义的。
在一种可能的实施方式中，上述周期的长度可以是(0.5*RTT5)的n倍，n为大于0的整数。
在UE#1与目标小区#1在上述时段#A2由于交互信令重复发送，目标小区#1收到RRC重配置完成信息超时的情况下，上述方案解决了源小区#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标小区#1的问题。
目前，在S830的步骤a开始时刻(即gNodeB-CU#1发出RRC重配置消息后)一直到S830的步骤d结束时刻(即gNodeB-CU#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#B2)，源小区#1不再向UE#1发送下行数据，意味着源小区#1中断未结束的下行HARQ进程的下行重传数据的传输，或者中断未结束的上行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的下行HARQ进程数据的传输。
针对该问题，本申请设计以下方案：
在时段#B2内，源小区#1可继续向UE#1发送下行数据#A，该下行数据#A包括未结束的下行HARQ进程的下行重传数据，和/或未结束的上行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述下行数据#A还可以包括新的HARQ进程的下行数据，例如，UPF#1已经分配给源gNodeB#1的下行用户面数据。
在上述方案中，由于UE#1与源小区#1之间的HARQ进程的数据会被更新，因此源小区#1需要向目标小区#1对应的内存拷贝当前需要进行更新的HARQ进程的数据，对此，本申请设计了以下方案：
源小区#1在S830的步骤a中gNodeB-CU#1向UE#1发送RRC重配置消息后，经过时长#A2后向目标小区#1拷贝信息#B2g，并开始周期性地向目标小区#1发送信息#B2g1、信息#B2g2…，一直到源小区#1收到了gNodeB-CU#1发来的UE上下文释放命令(UE context release command)。其中，信息#B2g、信息#B2g1、信息#B2g2…为根据UE#1在时段#A2内发送的上行数据#A更新后的信息#B2，信息#B2g、信息#B2g1、信息#B2g2…可以包括更新的HARQ进程对应的数据，也可以包括未更新的HARQ进程对应的数据。
时长#A2参见上述说明，在此不再赘述。
周期的长度参见上述说明，在此不再赘述。
在UE#1与目标小区#1在上述时段#B2由于交互信令重复发送，目标小区#1收到RRC重配置完成信息超时的情况下，上述方案解决了源小区#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标小区#1的问题。
S840，gNodeB-DU#1发送信息#C4，UE#1接收信息#C4。
其中，信息#C4包括以下信息的至少一种：
信息#C41，用于指示UE#1当前所有未结束的上行HARQ进程是否需要重传，示例性的，信息#C41可以包括需要重传的上行HARQ进程的ID以及NACK数据，或者不需要重传的上行HARQ进程的ID以及ACK数据，应理解，此处的需要重传的上行HARQ进程或者是不需要重传的上行HARQ进程都包含于上述所有未结束的上行HARQ进程；
信息#C41a，用于指示UE#1需要重传的上行HARQ进程所对应的上行数据所占用的 时频资源、gNodeB-DU#1的标识中的至少一种，示例性的，信息#C41a可以包括需要重传的上行HARQ进程的ID、对应的时频资源以及gNodeB-DU#1的标识；
信息#C42，用于指示gNodeB-DU#1为UE#1分配的目标小区#1的资源，该资源可用于目标小区#1与UE#1之间进行新的上行数据或者下行数据的传输或者新的HARQ进程的HARQ数据的传输。
信息#C43，用于指示UE#1针对当前所有未结束的下行HARQ进程的反馈数据向目标小区发送、反馈数据所占的时频资源中的至少一种。示例性地，信息#C43可以包括以下信息的至少一种：
当前未结束的下行HARQ进程的ID、当前未结束的下行HARQ进程的ID对应的反馈数据所占的时频资源、gNodeB-DU#1的标识。
在一种可能的实施方式中，信息#C43还可以是目标小区针对UE#1反馈了NACK数据的下行数据的冗余版本数据(即进行重传处理的下行数据)、以及对应的下行HARQ进程的ID。
UE#1接收信息#C4后，与对应HARQ进程的ID相关的HARQ进程会优先按照目标小区#1下发的信息#C4的指示来响应HARQ操作。例如，UE#1可以向源小区#1在时频资源#1上发送ACK1，也可以按照信息#C43的指示向目标小区#1在时频资源#2上发送ACK1，那么UE#1会优先选择后者的方案来发送ACK1，即向目标小区#1在时频资源#2上发送ACK1。
在一种可能的实施方式中，信息#C4可以包含于DCI，承载于RRC信令中。
在一种可能的实施方式中，在UE#1与目标小区#1建立连接的过程中，如果源小区#1向UE#1发送了新的下行数据或者收到了UE#1的新的反馈数据，那么gNodeB-DU#1需要保留该产生的新的状态。例如，gNodeB-DU#1需要保留该新的下行数据所对应的所有HARQ进程的数据以及对应的HARQ进程的ID，又例如，gNodeB-DU#1需要保留接收到的UE#1的新的反馈数据以及对应的HARQ进程的ID，以便于目标小区#1掌握最新的未结束的HARQ进程的数据。目标小区#1获知该新的HARQ进程数据后，可以将该新的HARQ进程数据对应的控制信息包含于信息#C4中，发给UE#1，具体内容参见信息#C4，在此不再赘述。
S850，UE#1发送响应信息#D1，目标小区#1接收响应信息#D1。
具体地，UE#1根据信息#C4发送响应信息#D1。
示例性的，响应信息#D1包括ACK或NACK数据。
若信息#C4包括信息#C41a，则UE#1需要在信息#C41a指示的时频资源上发送需要重传的上行数据；
若信息#C4包括信息#C43，则UE#1需要在信息#C43指示的时频资源上发送针对当前源小区#1向UE#1发送的下行数据的反馈数据。
S860，gNodeB-CU#1发送信息#G，gNodeB-DU#1接收信息#G。
具体地，信息#G包括UE上下文释放命令(UE context release command)，源小区#1收到信息#G后释放与UE#1的连接。
在一种可能的实施方式中，在源小区#1释放与UE#1的连接之前，如果产生了新的上行HARQ进程，那么可以有以下两种方式的处理：
方式一
源小区#1继续进行该新的上行HARQ进程，对UE#1进行上行数据的反馈，直到结束该新的上行HARQ进程。
方式二
gNodeB-DU#1将需要回复NACK的HARQ进程的相关数据保留下来，具体内容可以参考上述信息#B2，在此不再赘述，如果是需要回复ACK的HARQ进程，那么源小区#1将ACK数据发给UE#1即可。gNodeB-DU#1保留该数据后，可以将该数据是否需要重传以及如果需要重传，所占用的目标小区#1的时频资源发给UE#1，具体内容参见信息#C4。
在一种可能的实施方式中，如果源小区#1有未发完的下行数据，那么可以继续下发该下行数据，发完该下行数据后，形成了新的HARQ进程，但是不再发送新的下行数据。此时gNodeB-DU#1需要保留该新的HARQ进程的相关数据，该新的HARQ进程的相关数据的具体内容可参见信息#B2。在该情况下，如果源小区#1收到UPF发下来的数据或源小区#1的缓存中还有未发过的下行数据，那么gNodeB-DU#1需要保留该未发过的下行数据，以便于目标小区#1能够继续发送该未发过的下行数据。
通过方法800，能够在UE切换前后的小区属于同一个卫星，并且不同波束属于不同小区的情况下，当UE需要进行小区间的切换时，使能UE进行的HARQ进程能够连续，强化卫星通信的时延优势，获得软合并编码增益。
本申请实施例还考虑了UE切换前后的小区属于同一个基站(gNodeB)管辖，但是属于不同的gNodeB-Du，在此场景中，一个卫星群中的多个卫星是gNodeB-DU，由地面关口站或者其它卫星充当gNodeb-CU，UE发生的小区间切换实际上是不同卫星之间的切换，其中，gNodeB-DU与gNodeB-CU通过高速无线链路连接。例如，图9中的方法900所示，图9是本申请实施例的又一例示意性流程图，图9中的UE#1切换前后的小区(切换前为源小区#1，切换后为目标小区#1)分别属于源gNodeB-DU#1和目标gNodeB-DU#1，并且都属于gNodeB-CU#1控制，同时，源gNodeB-DU#1、目标gNodeB-DU#1和gNodeB-CU#1属于同一个基站，方法900中的源gNodeB-DU或者目标gNodeB-DU可以对应一个卫星，也可以对应多个卫星。
S910中，UE#1基于测量控制信息#A执行小区切换。
具体地，可分为以下步骤：
步骤a：gNodeB-CU#1通过RRC重配置(RRC reconfiguration)消息向UE#1下发测量控制信息#A，其中，测量控制信息#A的内容参见方法200；
步骤b：UE#1回复RRC重配置完成(RRC reconfiguration complete)消息给gNodeB-CU#1；
步骤c：UE#1根据测量控制信息#A执行测量，并向gNodeB-CU#1上报邻区的测量报告；
步骤d：gNodeB-CU#1根据测量报告携带的目标小区的PCI，判决切换的目标小区#1与源小区#1同属一个gNodeB的不同DU，并启动站内跨DU切换流程，目标小区#1根据UE所在源小区#1的上下文做准入判决；
步骤e：gNodeB-CU#1发送UE上下文建立请求(UE context setup request)消息给目标gNodeB-DU#1，向目标gNodeB-DU#1为目标小区#1申请UE#1的资源；
步骤f：如果目标gNodeB-DU#1为UE#1的分配资源成功，则回复UE上下文建立响应(UE context setup response)消息给gNodeB-CU#1；
步骤g：gNodeB-CU#1发送UE上下文修改请求(UE context modification request)消息给目标gNodeB-DU#1，用于指示源gNodeB-DU#1下发停止调度源小区#1的L2信令的指示信息；
步骤h：目标gNodeB-DU#1回复UE上下文修改响应(UE context modification response)消息给gNodeB-CU#1；
S920中，gNodeB-CU#1发送信息#B2，目标gNodeB-DU#1接收信息#B2。
其中，信息#B2的内容参见方法S820，在此不再赘述。
目标gNodeB-DU#1通过获取信息#B2，以便于掌握当前所有未结束的HARQ进程的状态及信息，使能目标小区#1拥有接管当前HARQ进程的能力。
S930，UE#1与目标小区#1建立连接。
具体地，可分为以下步骤：
步骤a：gNodeB-CU#1给UE#1发送RRC重配置消息，该消息携带了目标小区#1的目标频点、目标小区#1的PCI以及给UE#1配置的C-RNTI和专用随机接入前导码；
步骤b：UE#1在目标gNodeB-DU#1的目标小区#1发起非竞争的随机接入，发送消息1(message1，MSG1)，消息1包括随机接入前导码序列。
步骤c：目标gNodeB-DU#1作出随机接入响应，并发送消息2(message2，MSG2)；
步骤d：UE#1发送RRC重配置完成(RRC reconfiguration complete)信息给gNodeB-CU#1，UE#1接入到目标小区#1；
目前，在S930的步骤a结束时刻(即UE#1成功译码gNodeB-CU#1发送的RRC重配置消息)一直到S930的步骤d结束时刻(即gNodeB-CU#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#A3)，UE#1不再向源gNodeB-DU#1发送上行数据，意味着UE#1中断未结束的上行HARQ进程的上行重传数据的传输，或者中断未结束的下行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的上行HARQ进程的数据的传输。
针对该问题，本申请设计以下方案：
在时段#A3内，UE#1可继续向源gNodeB-DU#1发送上行数据#A，该上行数据#A包括未结束的上行HARQ进程的上行重传数据，和/或未结束的下行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述上行数据#A还可以包括新的HARQ进程的上行数据。
在上述方案中，由于UE#1与源gNodeB-DU#1之间的HARQ进程的数据会被更新，因此源gNodeB-DU#1与目标gNodeB-DU#1之间需要进行更新的HARQ进程的数据的传递，对此，本申请设计了以下方案：
源gNodeB-DU#1在S930的步骤a中gNodeB-CU#1给UE#1发送RRC重配置消息后，经过时长#A3后向目标gNodeB-DU#1发送信息#B2g，并开始周期性地向目标gNodeB-DU#1发送信息#B2g1、信息#B2g2…，一直到源gNodeB-DU#1收到了gNodeB-CU#1发来的UE上下文释放命令(UE context release command)信息。其中，信息#B2g、信息#B2g1、信息#B2g2…为根据UE#1在时段#A3内发送的上行数据#A更新后 的信息#B2，信息#B2g、信息#B2g1、信息#B2g2…可以包括更新的HARQ进程对应的数据，也可以包括未更新的HARQ进程对应的数据。
需要说明的是，源gNodeB-DU#1向目标gNodeB-DU#1发送信息是通过gNodeB-CU#1的，即源gNodeB-DU#1先向gNodeB-CU#1发送信息，gNodeB-CU#1再将信息转发给目标gNodeB-DU#1。
在一种可能的实施方式中，时长#A3可以是预定义的。
在一种可能的实施方式中，时长#A3的值可以是(2*RTT6–RTT7)，其中，RTT6为UE#1与源gNodeB-DU#1或目标gNodeB-DU#1的信号传输的往返时延，RTT7是源gNodeB-DU#1和gNodeB-CU之间的信号传输的时延与gNodeB-CU和目标gNodeB-DU#1之间的信号传输的时延的和。
需要说明的是，时长#A3的值也可以大于(2*RTT6–RTT7)，例如，当在时段#A3内UE#1或者目标gNodeB-DU#1发生了译码错误时。
示例性地，RTT6的值是540ms。
在一种可能的实施方式中，上述周期的长度可以是预定义的。
在一种可能的实施方式中，上述周期的长度可以是(0.5*RTT6)的n倍，n为大于0的整数。
在UE#1与目标gNodeB-DU#1在上述时段#A由于交互信令重复发送，目标gNodeB-DU#1收到RRC重配置完成信息超时的情况下，上述方案解决了源gNodeB-DU#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标gNodeB-DU#1的问题。
目前，在S930的步骤a开始时刻(即gNodeB-CU#1发出RRC重配置消息后)一直到S930的步骤d结束时刻(即gNodeB-CU#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#B3)，源gNodeB-DU#1不再向UE#1发送下行数据，意味着源gNodeB-DU#1中断未结束的下行HARQ进程的下行重传数据的传输，或者中断未结束的上行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的下行HARQ进程的数据的传输。
针对该问题，本申请设计以下方案：
在时段#B3内，源gNodeB-DU#1可继续向UE#1发送下行数据#A，该下行数据#A包括未结束的下行HARQ进程的下行重传数据，和/或未结束的上行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述下行数据#A还可以包括新的HARQ进程的下行数据，例如，UPF#1已经分配给源gNodeB-DU#1的下行用户面数据。
在上述方案中，由于UE#1与源gNodeB-DU#1之间的HARQ进程的数据会被更新，因此源gNodeB-DU#1与目标gNodeB-DU#1之间需要进行更新的HARQ进程的数据的传递，对此，本申请设计了以下方案：
源gNodeB-DU#1在S930的步骤a中gNodeB-CU#1发出RRC重配置消息后，经过时长#A3后向目标gNodeB-DU#1发送信息#B2g，并开始周期性地向目标gNodeB-DU#1发送信息#B2g1、信息#B2g2…，一直到源gNodeB-DU#1收到了gNodeB-CU#1发来的UE上下文释放命令(UE context release command)信息。其中，信息#B2g、信息#B2g1、信息#B2g2…为根据UE#1在时段#A3内发送的上行数据#A更新后的信息#B2，信息#B2g、信 息#B2g1、信息#B2g2…可以包括更新的HARQ进程对应的数据，也可以包括未更新的HARQ进程对应的数据。
需要说明的是，源gNodeB-DU#1向目标gNodeB-DU#1发送信息是通过gNodeB-CU#1的，即源gNodeB-DU#1先向gNodeB-CU#1发送信息，gNodeB-CU#1再将信息转发给目标gNodeB-DU#1。
时长#A3参见上述说明，在此不再赘述。
周期的长度参见上述说明，在此不再赘述。
在UE#1与目标gNodeB-DU#1在上述时段#A由于交互信令重复发送，目标gNodeB-DU#1收到RRC重配置完成信息超时的情况下，上述方案解决了源gNodeB-DU#1不能将与UE#1之间更新的HARQ进程的状态及时更新给目标gNodeB-DU#1的问题。
S940，目标gNodeB-DU#1发送信息#C5，UE#1接收信息#C5。
其中，信息#C5包括以下信息的至少一种：
信息#C51，用于指示当前UE#1与源gNodeB-DU#1之间的所有未结束的上行HARQ进程是否需要重传，示例性的，信息#C51可以包括需要重传的上行HARQ进程的ID以及NACK数据，或者不需要重传的上行HARQ进程的ID以及ACK数据，应理解，此处的需要重传的上行HARQ进程或者是不需要重传的上行HARQ进程都包含于上述所有未结束的上行HARQ进程；
信息#C51a，用于指示UE#1需要重传的上行HARQ进程所对应的上行数据所占用的时频资源、目标gNodeB-DU#1的标识中的至少一种，示例性的，信息#C51a可以包括需要重传的上行HARQ进程的ID、对应的时频资源以及目标gNodeB-DU#1的标识；
信息#C52，用于指示目标gNodeB-DU#1为UE#1分配的目标小区#1的资源，该资源可用于目标小区#1与UE#1之间进行新的上行数据或者下行数据的传输或者新的HARQ进程的HARQ数据的传输。
信息#C53，用于指示UE#1针对当前所有未结束的下行HARQ进程的反馈数据向目标小区#1发送、反馈数据所占的时频资源中的至少一种。示例性地，信息#C53可以包括以下信息的至少一种：
当前未结束的下行HARQ进程的ID、当前未结束的下行HARQ进程的ID对应的反馈数据所占的时频资源、目标gNodeB-DU#1的标识。
在一种可能的实施方式中，信息#C53还可以是目标小区#1针对UE#1反馈了NACK数据的下行数据的冗余版本数据(即进行重传处理的下行数据)、以及对应的下行HARQ进程的ID。
UE#1接收信息#C5后，与对应HARQ进程的ID相关的HARQ进程会优先按照目标gNodeB-DU#1下发的信息#C5的指示来响应HARQ操作。例如，UE#1可以向源小区#1在时频资源#1上发送ACK1，也可以按照信息#C53的指示向目标小区#1在时频资源#2上发送ACK1，那么UE#1会优先选择后者的方案来发送ACK1，即向目标小区#1在时频资源#2上发送ACK1。
在一种可能的实施方式中，信息#C5可以包含于DCI，承载于RRC信令中。
在一种可能的实施方式中，在UE#1与目标小区#1建立连接的过程中，如果源小区#1向UE#1发送了新的下行数据或者收到了UE#1的新的反馈数据，那么源gNodeB-DU#1 需要向目标gNodeB-DU#1发送该产生的新的状态。例如，源gNodeB-DU#1需要向目标gNodeB-DU#1发送该新的下行数据所对应的所有HARQ进程的数据以及对应的HARQ进程的ID，又例如，源gNodeB-DU#1需要向目标gNodeB-DU#1发送接收到的UE#1的新的反馈数据以及对应的HARQ进程的ID，以便于目标小区#1掌握最新的未结束的HARQ进程的数据。目标gNodeB-DU#1获知该新的HARQ进程数据后，可以将该新的HARQ进程数据对应的控制信息包含于信息#C5中，发给UE#1，具体内容参见信息#C5，在此不再赘述。
S950，UE#1发送响应信息#D2，目标gNodeB-Du#1接收响应信息#D2。
具体地，UE#1根据信息#C5发送响应信息#D2。
示例性的，响应信息#D2包括ACK或NACK数据。
若信息#C5包括信息#C51a，则UE#1需要在信息#C51a指示的时频资源上发送需要重传的上行数据；
若信息#C5包括信息#C53，则UE#1需要在信息#C53指示的时频资源上发送针对当前源gNodeB-Du#1向UE#1发送的下行数据的反馈数据。
S960，gNodeB-CU#1发送信息#G，源gNodeB-DU#1接收信息#G。
具体地，信息#G包括UE上下文释放命令(UE context release command)信息，源gNodeB-DU#1收到信息#G后释放与UE#1的连接。
在一种可能的实施方式中，在源小区#1释放与UE#1的连接之前，如果产生了新的上行HARQ进程，那么可以有以下两种方式的处理：
方式一
源小区#1继续进行该新的上行HARQ进程，对UE#1进行上行数据的反馈，直到结束该新的上行HARQ进程。
方式二
源gNodeB-DU#1将需要回复NACK的HARQ进程的相关数据发送给目标gNodeB-DU#1，具体内容可以参考上述信息#B2，在此不再赘述，如果是需要回复ACK的HARQ进程，那么源小区#1将ACK数据发给UE#1即可。目标gNodeB-DU#1接收该数据后，可以将该数据是否需要重传以及如果需要重传，所占用的目标小区#1的时频资源发给UE#1，具体内容参见信息#C5。
在一种可能的实施方式中，如果源小区#1有未发完的下行数据，那么可以继续下发该下行数据，发完该下行数据后，形成了新的HARQ进程，但是不再发送新的下行数据。此时源gNodeB-DU#1需要将该新的HARQ进程的相关数据发送给目标gNodeB-DU#1，该新的HARQ进程的相关数据的具体内容可参见信息#B2。在该情况下，如果源gNodeB-DU#1收到UPF发下来的数据或源gNodeB-DU#1#1的缓存中还有未发过的下行数据，那么源gNodeB-DU#1需要将该未发过的下行数据发送给目标gNodeB-DU#1，以便于目标小区#1能够继续发送该未发过的下行数据。
通过方法900，能够在UE切换前后的小区属于不同卫星，不同卫星为不同的gNodeB-DU，并且不同的gNodeB-DU属于同一个gNodeB-CU控制，该不同的gNodeB-DU和gNodeB-CU属于同一个基站，当UE需要进行小区间的切换时，使能UE进行的HARQ进程能够连续，强化卫星通信的时延优势，获得软合并编码增益。
本申请实施例还考虑了UE执行的小区切换为条件性小区切换(conditional handover)时如何使HARQ进程连续，例如，图10中的方法1000所示。图10是本申请实施例的又一例示意性流程图，UE#1、源gNodeB#1、目标gNodeB#1以及AMF参见图6中的说明，在此不再赘述，下面以方法200对应的场景为例进行介绍。
S1010中，UE#1执行条件小区切换。
具体地，可分为以下步骤：
步骤a：源gNodeB#1通过RRC重配置(RRC reconfiguration)消息向UE#1下发测量控制信息#A。其中，测量控制信息#A包括测量对象(例如，同频测量、异频测量等)、测量配置(例如，UE需要测量的对象、小区列表、报告方式、测量标识、事件参数等)和测量间隙(GAP)配置等；
步骤b：UE#1通过RRC重配置完成(reconfiguration complete)消息向源gNodeB#1做出响应；
步骤c：源gNodeB#1通过Xn链路发送条件切换请求(conditional handover request)信息给选择的目标小区#1所在的目标gNodeB#1，发起条件切换请求。
其中，条件切换请求信息用于指示UE#1执行的小区切换为条件小区切换。
步骤d：目标gNodeB#1收到条件切换请求信息后，进行准入控制，允许准入后分配给UE#1实例和传输资源。
步骤e：源gNodeB#1发送RRC重配置消息给UE#1，要求UE#1执行切换到目标小区#1，其中，RRC重配置消息可以包括RRC重配置目标小区的ID(RRCReconfiguration target cell ID)、新小区无线网络临时标识(new cell radio network tempory identity，new C-RNTI)、安全算法(security algorithm)、条件#A等信息，其中，条件#A用于指示当满足条件#A时，UE#1与目标gNodeB#1建立连接，条件#A包括以下信息的至少一种：
切换事件：触发UE#1执行小区切换的事件，如5G NR的3GPP标准文件38.331当中定义的事件，例如，
事件A1(Event A1)：当前服务小区的信号质量开始优于门限值(threshold)，
事件A2(Event A2)：当前服务小区的信号质量开始差于门限值，
事件A3(Event A3)：邻居小区的信号质量开始优于特殊服务小区某一个差值，
事件A4(Event A4)：邻居小区的信号质量开始优于门限值，
事件A5(Event A5)：特殊服务小区的信号质量开始差于门限值1(threshold1)并且优于门限值2(threshold2)，
事件A6(Event A6)：邻居小区的信号质量开始优于辅小区某一个差值，
事件B1(Event B1)：不同的无线接入技术(radio access technology，RAT)的邻小区开始优于门限值，
事件B2(Event B2)：主小区的信号质量开始差于门限值1并且不同的无线接入技术的邻小区开始优于门限值2，
地理位置：UE#1的地理位置或者源gNodeB#1的地理位置，
波束角度：源gNodeB#1与UE#1之间波束的角度，
时间(time)：触发UE#1执行小区切换的时间，可以是时间偏移量，例如经过一定时间偏移量后触发UE#1执行小区切换，该时间偏移量可以是帧数等，
时刻(Timing)：绝对时刻，例如世界协调时间(coordinated universal time，UTC)，
定时器：触发UE#1在一定时间后执行小区切换；
步骤f：UE#1为候选的目标小区监控上述条件小区切换中的条件#A是否满足。
S1020，源gNodeB#1发送信息#B，目标gNodeB#1接收信息#B。
其中，信息#B用于指示源gNodeB#1与UE#1之间未结束的上行HARQ进程，信息#B的具体内容参见方法S220，在此不再赘述。
源gNodeB#1通过发送信息#B，以便于目标gNodeB#1掌握当前所有未结束的上行HARQ进程的状态及信息，拥有接管当前HARQ进程的能力。
S1030，满足条件#A后，UE#1与目标gNodeB#1建立连接。
具体地，包括以下步骤：
步骤a：UE#1在目标gNodeB#1所在的目标小区发起非竞争的随机接入，发送消息1(message1，MSG1)，消息1包括随机接入前导码(preamble)序列；
步骤b：目标gNodeB#1作出随机接入响应，并发送消息2(message2，MSG2)；
步骤c：UE#1发送RRC重配置完成信息给目标gNodeB#1，UE#1空口切换到目标小区#1完成。
目前，在条件#A满足的时刻，即UE#1开始执行小区切换的时刻(也可称为S1030的步骤a的起始时刻)，一直到S1030的步骤c的结束时刻(即目标gNodeB#1成功译码RRC重配置完成信息)的这段时间内(可称为时段#A4)，UE#1不再向源gNodeB#1发送上行数据，意味着UE#1中断未结束的上行HARQ进程的上行重传数据的传输，或者中断未结束的下行HARQ进程的反馈数据(ACK或NACK)的传输，或者中断新的上行HARQ进程的数据的传输。
针对该问题，本申请设计以下方案：
在时段#A4内，UE#1可继续向源gNodeB#1发送上行数据#A，该上行数据#A包括未结束的上行HARQ进程的上行重传数据，和/或未结束的下行HARQ进程的反馈数据(ACK或NACK)。
在一种可能的实施方式中，所述上行数据#A还可以包括新的HARQ进程的上行数据。
在上述方案中，由于UE#1与源gNodeB#1之间的HARQ进程的数据会被更新，因此源gNodeB#1与目标gNodeB#1之间需要进行更新的HARQ进程的数据的传递，更新数据的方案参见方法S230，在此不再赘述。
S1040，目标gNodeB#1发送信息#C，UE#1接收信息#C。
信息#C的内容参见方法S240，在此不再赘述。
S1050，UE#1发送响应信息#D，目标gNodeB#1接收响应信息#D。
响应信息#D的内容参见方法S250，在此不再赘述。
S1060，目标gNodeB#1发送信息#E，AMF#1接收信息#E。
信息#E的内容参见方法S260，在此不再赘述。
S1070，目标gNodeB#1发送信息#F，UE#1接收信息#F。
信息#F的内容参见方法S270，在此不再赘述。
S1080，源gNodeB#1释放与UE#1的连接。
具体地，可以分为以下步骤：
步骤a：AMF#1向目标gNodeB#1回复路径切换请求确认(path switch request acknowledge)消息。如果AMF#1在路径切换请求确认消息中指示核心网未能建立的PDU会话，则目标gNodeB#1删除未能建立的PDU会话；
步骤b：目标gNodeB#1向源gNodeB#1发送UE上下文释放(UE context release)消息，源gNodeB#1收到该消息后释放与UE#1的连接；
在一种可能的实施方式中，在源gNodeB#1发送信息#B之后，在源gNodeB#1释放与UE#1的连接之前，如果产生了新的上行HARQ进程或者更新了HARQ进程的状态，那么源gNodeB#1进行处理的方式参见方法S280，在此不再赘述。
需要说明的是上述有关于UE#1执行条件小区切换时使能HARQ进程连续的方法同样适用于方法500、方法800和方法900中的场景，在此不再赘述。
需要说明的是，以上本申请实施例中的部分信令(消息)名称采用了3GPP标准中的信令(消息)，仅仅用作举例，其含义(功能)可以与3GPP规定的含义(功能)相同也可以不同。
需要说明的是，将上述各个实施例的组合或者拆分也能获得可以解决本申请技术问题的实施例，均在本申请要保护的范围内。
图11和图12是本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以实现上述方法实施例中终端设备或网络设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请实施例中，该通信装置可以是方法100中的通信装置，还可以是应用于通信装置的模块(如芯片)。
如图11所示，通信装置1100包括收发模块1101和处理模块1102。通信装置1100可用于实现上述图5所示的方法实施例中的通信装置的功能。
通信装置1100用于实现图5方法实施例中通信装置的功能时：收发模块1101，用于第一终端设备与第一网络设备传输第一数据，第一数据对应第一混合自动重传请求HARQ进程；在第一终端设备从第一网络设备切换至第二网络设备的情况下，收发模块1101还用于第一终端设备与第二网络设备传输第二数据，第二数据对应第一HARQ进程，第二数据包括对第一数据进行重传处理的数据、针对第一数据的反馈信息中的至少一个；处理模块1102，用于确定上述第一数据和第二数据。
关于上述收发模块1101和处理模块1102更详细的描述，可参考上述方法实施例中的相关描述，在此不再说明。
如图12所示，通信装置1200包括处理器1210和接口电路1220。处理器1210和接口电路1220之间相互耦合。可以理解的是，接口电路1220可以为收发器或输入输出接口。可选的，通信装置1200还可以包括存储器1230，用于存储处理器1210执行的指令或存储处理器1210运行指令所需要的输入数据或存储处理器1210运行指令后产生的数据。
示例性地，存储器1230和处理器1210可以集成在一起，也可以为独立的器件。
当通信装置1200用于实现上述方法实施例中的方法时，处理器1210用于执行上述处理模块1102的功能，接口电路1220用于执行上述收发模块1101的功能。
当上述通信装置为应用于上述通信装置的芯片时，该通信装置的芯片实现上述方法实施例中通信装置的功能。该通信装置芯片从该通信装置中的其它模块(如射频模块或天线)接收信息；或者，该通信装置芯片向该通信装置中的其它模块(如射频模块或天线)发送 信息。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
需要说明的是，本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统或系统实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的系统及系统实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
还需要说明的是，在本文中，诸如第一、第二、“#1”、“#2”之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于接入网设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于接入网设备或终端设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存 储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，DVD；还可以是半导体介质，例如，固态硬盘(solid state disk，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。需要说明的是，本申请实施例中的步骤不一定全部都必须执行，有些是可省略的，并且也能达到类似的效果。

Claims (40)

  1. 一种数据传输方法，其特征在于，所述方法包括：
    第一终端设备与第一网络设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；
    在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第二网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个。
  2. 根据权利要求1所述的方法，其特征在于，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第二网络设备传输第二数据包括：
    在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功译码用于执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
  3. 根据权利要求1所述的方法，其特征在于，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述第一终端设备与所述第一网络设备传输第二数据包括：
    在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功发送消息1 MSG1的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，在所述第一终端设备与所述第二网络设备传输第二数据之前，所述方法包括：
    所述第一终端设备将第一介质访问控制层MAC实体中的所述第一HARQ进程的数据复制到第二MAC实体中，其中，所述第一MAC实体对应所述第一网络设备，所述第二MAC实体对应所述第二网络设备。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，在所述第一终端设备与所述第二网络设备传输第二数据之前，所述方法包括：
    所述第一终端设备接收第一指示信息，所述第一指示信息用于指示所述第一终端设备与所述第二网络设备传输所述第二数据。
  6. 根据权利要求5所述的方法，其特征在于，所述第一指示信息包括以下信息的一种或多种：
    所述第一HARQ进程的标识、所述第二网络设备的标识、第一资源，其中，所述第一资源为所述第二数据所占用的资源。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，所述第一数据为上行数据，所述第二数据包括对所述第一数据进行重传处理的数据。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述第一数据为下行数据，所述第二数据包括针对所述第一数据的反馈信息。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述第一数据的反馈信息包括确认消息ACK或者否认应答NACK。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，所述第一网络设备或者所述第二网络设备为卫星。
  11. 一种数据传输方法，其特征在于，所述方法包括：
    第一网络设备接收第一信息，所述第一信息用于指示第一终端设备从第二网络设备切换到所述第一网络设备；
    所述第一网络设备获取第二信息，所述第二信息用于指示所述第一终端设备与所述第二网络设备之间未结束的第一混合自动重传请求HARQ进程；
    所述第一网络设备根据所述第二信息向所述第一终端设备发送第三信息，所述第三信息用于指示所述第一终端设备与所述第一网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个，其中，所述第一数据对应所述第一HARQ进程，所述第一数据为所述第一终端设备与所述第二网络设备之间已经传输的数据。
  12. 根据权利要求11所述的方法，其特征在于，所述方法包括：
    所述第一网络设备在第一时段内接收所述第二网络设备发送的第四信息，所述第一时段包括所述第二网络设备发出用于所述第一终端设备执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第一网络设备成功译码所述第一终端设备发送的第一RRC重配置完成消息的结束时刻之间的时段，所述第一时段用于所述第二网络设备与所述第一终端设备传输第三数据，所述第三数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息、第二HARQ进程的初始数据中的至少一个，所述第四信息为所述第二信息的更新信息并且对应所述第三数据。
  13. 根据权利要求12所述的方法，其特征在于，所述第一网络设备在第一时段内接收所述第二网络设备发送的第四信息包括：
    所述第一网络设备在第一时段的起始时刻并经过第一时延接收所述第二网络设备发送的第四信息。
  14. 根据权利要求13所述的方法，其特征在于，所述第一时延的值为2*RTT，所述RTT为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延。
  15. 根据权利要求13或14所述的方法，其特征在于，所述方法包括：
    所述第一网络设备在接收所述第四信息的结束时刻并经过第二时延接收所述第二网络设备发送的第五信息，所述第五信息为所述第四信息的更新信息，所述第二时延的值为(0.5*RTT)的n倍，所述n为正整数。
  16. 根据权利要求11-15中任一项所述的方法，其特征在于，所述第二信息包括以下信息的至少一种：
    所述第一HARQ进程的冗余版本数据、所述第一HARQ进程的标识、所述第一HARQ进程的冗余版本号。
  17. 根据权利要求11-16中任一项所述的方法，其特征在于，所述第二信息包括以下信息的至少一种：
    所述第二网络设备已经接收到的所述第一HARQ进程的数据、所述第二网络设备针对所述第一HARQ进程已经译码的数据。
  18. 根据权利要求11-17中任一项所述的方法，其特征在于，所述第三信息包括以下信息的一种或多种：
    所述第一HARQ进程的标识、所述第一网络设备的标识、第一资源，其中，所述第一资源为传输所述第二数据所占用的资源。
  19. 根据权利要求11-18中任一项所述的方法，其特征在于，在所述第一数据为上行数据的情况下，所述第二数据包括对第一数据进行重传处理的数据。
  20. 根据权利要求11-19中任一项所述的方法，其特征在于，在所述第一数据为下行数据的情况下，所述第二数据包括针对所述第一数据的反馈信息。
  21. 根据权利要求11-20中任一项所述的方法，其特征在于，所述第一数据的反馈信息包括确认消息ACK或者否认应答NACK。
  22. 根据权利要求11-21中任一项所述的方法，其特征在于，所述第一终端设备或者所述第二网络设备为卫星。
  23. 一种数据传输方法，其特征在于，所述方法包括：
    第一网络设备与第一终端设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；
    在所述第一终端设备从所述第一网络设备切换至第二网络设备的情况下，所述第一网络设备向所述第二网络设备发送第一信息，所述第一信息用于指示所述第一HARQ进程。
  24. 根据权利要求23所述的方法，其特征在于，所述第一信息包括以下信息的至少一种：
    所述第一HARQ进程的冗余版本数据、所述第一HARQ进程的标识、所述第一HARQ进程的冗余版本号。
  25. 根据权利要求23或24所述的方法，其特征在于，所述第一信息包括以下信息的至少一种：
    所述第一网络设备已经接收到的所述第一HARQ进程的数据、所述第一网络设备针对所述第一HARQ进程已经译码的数据。
  26. 根据权利要求23-25中任一项所述的方法，其特征在于，所述方法包括：
    所述第一网络设备在第一时段内与所述第一终端设备传输第二数据，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息、第二HARQ进程的初始数据中的至少一个，其中，所述第一时段包括所述第一网络设备发出用于所述第一终端设备执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第二网络设备成功译码所述第一终端设备发送的第一RRC重配置完成消息的时刻之间的时段。
  27. 根据权利要求26所述的方法，其特征在于，所述方法包括：
    所述第一网络设备在所述第一时段的起始时刻并经过第一时延向所述第二网络设备发送第二信息，所述第二信息为所述第一信息的更新信息。
  28. 根据权利要求27所述的方法，其特征在于，所述第一网络设备为第一卫星，所 述第二网络设备为第二卫星，所述第一网络设备与所述第二网络设备存在星间链路，所述第一时延的值为2*RTT1-0.5*RTT2，所述RTT1为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述RTT2为所述第一网络设备与所述第二网络设备之间数据传输的往返时延。
  29. 根据权利要求27所述的方法，其特征在于，所述第一网络设备为第一卫星，所述第二网络设备为第二卫星，所述第一网络设备与所述第二网络设备通过第三网络设备进行数据传输，所述第一时延的值为2*RTT3-RTT4，其中，所述RTT3为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述RTT4为第二时延与第三时延的和，所述第二时延为所述第一网络设备与所述第三网络设备的数据传输的时延，所述第三时延为所述第二网络设备与所述第三网络设备的数据传输的时延。
  30. 根据权利要求27所述的方法，其特征在于，所述第一网络设备与所述第二网络设备为第一卫星，所述第一时延的值为2*RTT5，其中，所述RTT5为所述第一终端设备与所述第一网络设备之间数据传输的往返时延。
  31. 根据权利要求27-30中任一项所述的方法，其特征在于，所述方法包括：
    所述第一网络设备在发出所述第二信息的时刻并经过第二时延向所述第二网络设备发送第三信息，所述第三信息为所述第二信息的更新信息，所述第二时延的值为(0.5*RTT6)的n倍，所述RTT6为所述第一终端设备与所述第一网络设备或所述第二网络设备之间数据传输的往返时延，所述n为正整数。
  32. 一种数据传输装置，其特征在于，所述装置包括：
    收发模块，所述收发模块用于第一终端设备与第一网络设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；
    在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述收发模块还用于所述第一终端设备与所述第二网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个。
  33. 根据权利要求32所述的装置，其特征在于，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述收发模块还用于所述第一终端设备与所述第二网络设备传输第二数据包括：
    在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述收发模块还用于所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功译码用于执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
  34. 根据权利要求32所述的装置，其特征在于，所述在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的情况下，所述收发模块还用于第一终端设备与所述第一网络设备传输第二数据包括：
    在所述第一终端设备从所述第一网络设备切换至所述第二网络设备的第一时段内，所述收发模块还用于所述第一终端设备与所述第一网络设备传输第二数据，其中，所述第一时段包括所述第一终端设备成功发送消息1 MSG1的时刻至所述第二网络设备成功译码第一RRC重配置完成消息的时刻之间的时段。
  35. 一种数据传输装置，其特征在于，所述装置包括：
    收发模块，所述收发模块用于第一网络设备接收第一信息，所述第一信息用于指示第一终端设备从第二网络设备切换到所述第一网络设备；
    所述收发模块还用于所述第一网络设备获取第二信息，所述第二信息用于指示所述第一终端设备与所述第二网络设备之间未结束的第一混合自动重传请求HARQ进程；
    所述收发模块还用于所述第一网络设备根据所述第二信息向所述第一终端设备发送第三信息，所述第三信息用于指示所述第一终端设备与所述第一网络设备传输第二数据，所述第二数据对应所述第一HARQ进程，所述第二数据包括对第一数据进行重传处理的数据、针对所述第一数据的反馈信息中的至少一个，其中，所述第一数据对应所述第一HARQ进程，所述第一数据为所述第一终端设备与所述第二网络设备之间已经传输的数据。
  36. 根据权利要求35所述的装置，其特征在于，所述收发模块还用于所述第一网络设备在第一时段内接收所述第二网络设备发送的第四信息，所述第一时段包括所述第二网络设备发出用于所述第一终端设备执行所述切换的第一无线资源控制RRC重配置消息的时刻至所述第一网络设备成功译码所述第一终端设备发送的第一RRC重配置完成消息的结束时刻之间的时段，所述第一时段用于所述第二网络设备与所述第一终端设备传输第三数据，所述第三数据包括对所述第一数据进行重传处理的数据、针对所述第一数据的反馈信息、第二HARQ进程的初始数据中的至少一个，所述第四信息为所述第二信息的更新信息并且对应所述第三数据。
  37. 一种数据传输装置，其特征在于，所述装置包括：
    收发模块，所述收发模块用于第一网络设备与第一终端设备传输第一数据，所述第一数据对应第一混合自动重传请求HARQ进程；
    在所述第一终端设备从所述第一网络设备切换至第二网络设备的情况下，所述收发模块还用于所述第一网络设备向所述第二网络设备发送第一信息，所述第一信息用于指示所述第一HARQ进程。
  38. 一种用于数据传输的通信装置，其特征在于，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号传输给所述通信装置之外的其它通信装置，所述处理器用于实现如权利要求1至10或11至22或23至31中任一项所述的方法。
  39. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，当所述计算机程序被运行时，实现如权利要求1至10或11至22或23至31中任一项所述的方法。
  40. 一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被通信装置运行时，使得所述通信装置执行如权利要求1至10或11至22或23至31中任一项所述的方法。
PCT/CN2022/094894 2021-06-24 2022-05-25 一种数据传输方法和装置 Ceased WO2022267800A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22827297.7A EP4351213A4 (en) 2021-06-24 2022-05-25 METHOD AND APPARATUS FOR DATA TRANSMISSION

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110705433.7 2021-06-24
CN202110705433.7A CN115529645A (zh) 2021-06-24 2021-06-24 一种数据传输方法和装置

Publications (1)

Publication Number Publication Date
WO2022267800A1 true WO2022267800A1 (zh) 2022-12-29

Family

ID=84544088

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/094894 Ceased WO2022267800A1 (zh) 2021-06-24 2022-05-25 一种数据传输方法和装置

Country Status (3)

Country Link
EP (1) EP4351213A4 (zh)
CN (1) CN115529645A (zh)
WO (1) WO2022267800A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024156190A1 (en) * 2023-09-28 2024-08-02 Lenovo (Beijing) Limited Devices and methods of communication
WO2025010743A1 (zh) * 2023-07-13 2025-01-16 北京小米移动软件有限公司 通信处理方法及装置
CN120378064A (zh) * 2025-06-26 2025-07-25 南京控维通信科技有限公司 适用于卫星低轨hd-fdd系统的harq重传方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118679778A (zh) * 2023-01-16 2024-09-20 北京小米移动软件有限公司 信息反馈方法和装置
CN121794933A (zh) * 2023-08-24 2026-04-03 华为技术有限公司 通信方法及装置
CN121890221A (zh) * 2023-09-22 2026-04-17 中兴通讯股份有限公司 用于harq信息传输的方法、设备和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180159668A1 (en) * 2016-05-13 2018-06-07 Intel IP Corporation Systems, devices, and methods for variable rtt in harq operations
CN108141276A (zh) * 2015-10-05 2018-06-08 高通股份有限公司 在射束间切换时的harq处理
IN201817045669A (zh) * 2018-12-03 2019-02-01 Huawei Technologies Co., Ltd

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7046648B2 (en) * 2003-11-05 2006-05-16 Interdigital Technology Corporation Wireless communication method and apparatus for coordinating Node-B's and supporting enhanced uplink transmissions during handover
WO2020244739A1 (en) * 2019-06-04 2020-12-10 Telefonaktiebolaget Lm Ericsson (Publ) Transmitting a communication on a first channel or a second channel
US11509426B2 (en) * 2019-08-14 2022-11-22 Ofinno, Llc URLLC HARQ processes

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108141276A (zh) * 2015-10-05 2018-06-08 高通股份有限公司 在射束间切换时的harq处理
US20180159668A1 (en) * 2016-05-13 2018-06-07 Intel IP Corporation Systems, devices, and methods for variable rtt in harq operations
IN201817045669A (zh) * 2018-12-03 2019-02-01 Huawei Technologies Co., Ltd

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
FRAUNHOFER IIS, FRAUNHOFER HHI: "NTN NR impacts on the HARQ Operation", 3GPP DRAFT; R1-1802613_NTN_NR_IMPACTS_HARQ_V1_0, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, Greece; 20180226 - 20180302, 15 February 2018 (2018-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051396904 *
HUAWEI, HISILICON: "Discussion on HARQ enhancement for NTN", 3GPP DRAFT; R1-2005267, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. E-meeting; 20200817 - 20200828, 8 August 2020 (2020-08-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051917315 *
HUAWEI, HISILICON: "Improved HARQ retransmission", 3GPP DRAFT; R2-144937 IMPROVED HARQ RETRANSMISSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. San Francisco, USA; 20141117 - 20141121, 17 November 2014 (2014-11-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050877084 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025010743A1 (zh) * 2023-07-13 2025-01-16 北京小米移动软件有限公司 通信处理方法及装置
WO2024156190A1 (en) * 2023-09-28 2024-08-02 Lenovo (Beijing) Limited Devices and methods of communication
CN120378064A (zh) * 2025-06-26 2025-07-25 南京控维通信科技有限公司 适用于卫星低轨hd-fdd系统的harq重传方法

Also Published As

Publication number Publication date
EP4351213A1 (en) 2024-04-10
EP4351213A4 (en) 2024-11-20
CN115529645A (zh) 2022-12-27

Similar Documents

Publication Publication Date Title
US12150203B2 (en) Communication method and related product
EP4351213A1 (en) Data transmission method and apparatus
US20250385760A1 (en) Systems and methods for reliable mac ce ack/nack confirmation
US10433205B2 (en) Network node, method therein, computer program, and carrier comprising the computer program for retransmitting an RLC PDU
WO2021051388A1 (zh) 小区切换的方法和设备
CN101888675A (zh) 一种长期演进系统中跨基站切换方法及系统
CN110168983B (zh) 用于数据重传的方法和设备
CN112740806B (zh) 随机接入的方法、终端设备和网络设备
US10263895B2 (en) Data transmission method, central processing node, gateway, and base station
US20250343638A1 (en) Method and apparatus for wireless communication
US20240056901A1 (en) Method and apparatus for multicast and broadcast services
WO2017201743A1 (zh) 传输方法、基站和终端
CN116868530A (zh) 存活时间的处理方法和终端设备
CN117998476A (zh) 一种数据传输的方法和装置
WO2021051284A1 (zh) 一种上行重传处理方法、电子设备及存储介质
WO2023056844A1 (zh) 传输数据的方法和装置
WO2018098675A1 (zh) 用于数据重传的装置、方法以及通信系统
WO2025103161A1 (zh) 一种通信方法及相关设备
WO2019157680A1 (zh) 信息接收和发送方法、装置及通信系统
WO2025031366A1 (zh) 通信方法及相关装置
WO2026002163A1 (zh) 通信方法、装置及系统
WO2025060874A1 (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: 22827297

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022827297

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022827297

Country of ref document: EP

Effective date: 20231213

NENP Non-entry into the national phase

Ref country code: DE