WO2024032503A1 - 数据处理方法、终端及网络侧设备 - Google Patents

数据处理方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2024032503A1
WO2024032503A1 PCT/CN2023/111236 CN2023111236W WO2024032503A1 WO 2024032503 A1 WO2024032503 A1 WO 2024032503A1 CN 2023111236 W CN2023111236 W CN 2023111236W WO 2024032503 A1 WO2024032503 A1 WO 2024032503A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
bsr
uplink
synchronization
triggered
Prior art date
Application number
PCT/CN2023/111236
Other languages
English (en)
French (fr)
Inventor
张艳霞
Original Assignee
维沃移动通信有限公司
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
Priority claimed from CN202210987783.1A external-priority patent/CN117676856A/zh
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2024032503A1 publication Critical patent/WO2024032503A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA

Definitions

  • This application belongs to the field of communication technology, and specifically relates to a data processing method, terminal and network side equipment.
  • NTN Non-Terrestrial Networks
  • the terminal may trigger a buffer status report (Buffer Status Report, BSR) (for example, when the terminal has uplink data arriving ), even though there are no available uplink resources to transmit the corresponding uplink data, the terminal will still trigger a series of resource application processes, such as triggering BSR, Scheduling Request (SR), Random Access Channel, RACH) etc.
  • BSR Buffer Status Report
  • RACH Random Access Channel
  • the terminal reacquires the latest valid ephemeris information
  • the uplink data arriving at the terminal may be discarded due to too long waiting time. Therefore, when uplink transmission resumes, the terminal still performs the application process for uplink resources (such as RACH, sending BSR Media Access Control (Medium Access Control, MAC) Control Element (Control Element, CE)), resulting in a waste of resources.
  • uplink resources such as RACH, sending BSR Media Access Control (Medium Access Control, MAC) Control Element (Control Element, CE)
  • Embodiments of the present application provide a data processing method, terminal and network side equipment, which can solve the problem of resource waste.
  • the first aspect provides a data processing method, which includes:
  • the terminal performs any of the following:
  • BSR is triggered
  • the BSR is triggered with a delay
  • the second aspect provides a data processing method, which includes:
  • the network side device sends configuration information to the terminal
  • the configuration information is used for the terminal to manage buffer status report BSR processing behavior during uplink out-of-synchronization.
  • a data processing device which device includes:
  • Execution module used to perform any of the following during upstream out-of-synchronization:
  • BSR is triggered
  • the BSR is triggered with a delay
  • a data processing device which device includes:
  • Sending module used to send configuration information to the terminal
  • the configuration information is used for the terminal to manage buffer status report BSR processing behavior during uplink out-of-synchronization.
  • a terminal in a fifth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor, the following implementations are implemented: The steps of the method described in one aspect.
  • a terminal including a processor and a communication interface; wherein the processor is configured to perform any of the following during uplink desynchronization:
  • BSR is triggered
  • the BSR is triggered with a delay
  • a network side device in a seventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor.
  • a network side device including a processor and a communication interface; wherein the communication interface is used to send configuration information to a terminal; wherein the configuration information is used for the terminal to manage uplink out-of-synchronization periods.
  • a ninth aspect provides a data processing system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the method described in the first aspect.
  • the network side device can be used to perform the steps of the method described in the second aspect. steps of the method described.
  • a readable storage medium In a tenth aspect, a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented as described in the first aspect. The steps of the method described in the second aspect.
  • a chip in an eleventh aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. method, or implement a method as described in the second aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement as described in the first aspect
  • the terminal performs any of the following: canceling the triggered cache status report BSR; triggering BSR when the BSR triggering condition is met; triggering the BSR when the BSR triggering condition is met. , delaying the triggering of BSR; not triggering BSR, standardizing the terminal's processing behavior of BSR during uplink out of synchronization, thus preventing the terminal from initiating unnecessary uplink resource application process after restoring uplink synchronization, and improving resource utilization.
  • Figure 1 is a schematic diagram of a wireless communication system applicable to the embodiment of the present application.
  • Figure 2 is a schematic diagram of a non-terrestrial network applicable to the embodiment of the present application.
  • FIG. 3 is one of the flow diagrams of the data processing method provided by the embodiment of the present application.
  • FIG. 4 is the second schematic flowchart of the data processing method provided by the embodiment of the present application.
  • FIG. 5 is one of the structural schematic diagrams of the data processing device provided by the embodiment of the present application.
  • Figure 6 is the second structural schematic diagram of the data processing device provided by the embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a network-side device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and “first” and “second” are intended to distinguish It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG 1 is a schematic diagram of a wireless communication system applicable to the embodiment of the present application.
  • the wireless communication system shown in Figure 1 includes a terminal 11 and a network side device 12.
  • the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • Mobile Internet Device MID
  • augmented reality augmented reality, AR
  • VR virtual reality
  • robots wearable devices
  • VUE vehicle-mounted equipment
  • PUE pedestrian terminal
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computers, PC), teller machines or self-service Terminal devices
  • wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), Smart wristbands, smart clothing, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11.
  • the network side equipment 12 may include access network equipment or core network equipment, where the access network equipment may also be called wireless access network equipment, radio access network (Radio Access Network, RAN), radio access network function or wireless access network unit.
  • Access network equipment can include base stations, WLAN access points or WiFi nodes, etc.
  • the base station can be called Node B, Evolved Node B (eNB), access point, Base Transceiver Station (BTS), radio base station , radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home B-Node, Home Evolved B-Node, Transmitting Receiving Point (TRP) or the above
  • eNB Evolved Node B
  • BTS Base Transceiver Station
  • BSS Basic Service Set
  • ESS Extended Service Set
  • TRP Transmitting Receiving Point
  • Each embodiment of the present application is aimed at that during the period when the terminal is out of synchronization in the uplink, the uplink data arriving at the terminal may be due to waiting It has been discarded after too long, and when uplink synchronization is restored, the terminal still performs the application process for uplink resources, resulting in resource waste.
  • a solution is provided to standardize the terminal's processing behavior of BSR during uplink out of synchronization. This prevents the terminal from initiating unnecessary uplink resource application processes after resuming uplink synchronization and improves resource utilization.
  • NTN Non-terrestrial networks
  • FIG. 2 is a schematic diagram of a non-terrestrial network applicable to the embodiment of the present application.
  • a typical NTN deployment scenario includes terminal 21, satellite (Satellite) (or Unmanned Aerial System platform (Unmanned Aerial System platform, UAS platform) )) 22 and Gateway (or base station) 23.
  • the terminal 21, the base station 23 and the core network equipment are all deployed on the ground, and the communication data between the terminal 21 and the base station 23 is relayed via the satellite 22 in the sky.
  • the link between the terminal 21 and the satellite 22 is called a service link
  • the link between the satellite 22 and the base station 23 is called a feeder link.
  • Satellite-based non-terrestrial communication systems Compared with terrestrial communication (Terrestrial Networks, TN) systems, satellite-based non-terrestrial communication systems have a wider coverage area. Therefore, they can be suitable for supplementary coverage in deserts, remote villages, etc. and for emergency response in natural disaster areas. Communication coverage.
  • TN Terrestrial Networks
  • the terminal needs to maintain satellite ephemeris information to facilitate operations such as uplink transmission compensation and mobility management.
  • the network side device can provide the ephemeris information of the serving cell through SIB19.
  • the terminal After the terminal receives the ephemeris information, the terminal will maintain the corresponding validity timer (T430). After the timer times out, the terminal considers that the ephemeris information corresponding to the timer is invalid, and the terminal cannot perform any uplink transmission. For example, when the T430 corresponding to the serving cell times out, the ephemeris information corresponding to the serving cell becomes invalid.
  • the terminal's Radio Resource Control (Radio Resource Control, RRC) will indicate that the MAC layer serving cell is out of synchronization in the uplink. At this time, the MAC layer will not be able to perform any uplink transmission. After reacquiring SIB19, the terminal can resume uplink transmission. For example, when the T430 corresponding to the serving cell times out, the terminal will re-obtain SIB19. When SIB19 is successfully obtained, the terminal's RRC will instruct the MAC serving cell to synchronize uplink. At this point, the MAC layer allows upload transfers to be performed.
  • RRC Radio Resource Control
  • the terminal when data arrives (for example, high-priority data arrives), the terminal triggers the BSR process to apply for uplink resources.
  • the terminal When there are no uplink resources or the uplink resources (ie, Physical Uplink Shared Channel (PUSCH) resources) are insufficient to transmit BSR, the terminal will trigger the SR process.
  • the terminal When there are no valid resources (ie, Physical Uplink Control Channel (PUCCH) resources) to transmit SR, the terminal will initiate a random access channel (Random Access Channel, RACH) process.
  • RACH Random Access Channel
  • the data processing method provided by the embodiment of this application can be applied to NTN scenarios.
  • the terminal performs any of the following: cancels the triggered cache status report BSR; triggers the BSR if the BSR triggering conditions are met; delays triggering the BSR if the BSR triggering conditions are met; does not trigger the BSR. Standardizes the terminal's BSR processing behavior during uplink out-of-synchronization, thereby preventing the terminal from initiating unnecessary uplink resource application processes after resuming uplink synchronization and improving resource utilization.
  • Figure 3 is one of the flow diagrams of the data processing method provided by the embodiment of the present application. As shown in Figure 3, the method includes step 301; wherein:
  • Step 301 During the uplink out-of-synchronization period, the terminal performs any of the following:
  • BSR is triggered
  • the BSR is triggered with a delay
  • the terminals include but are not limited to the types of terminals 11 listed above, and the network side devices include but are not limited to the types of network side devices 12 listed above.
  • the examples are not limiting.
  • the validity timer maintained by the terminal when the validity timer maintained by the terminal times out, the ephemeris information corresponding to the timer becomes invalid, and the terminal cannot perform any uplink transmission.
  • the validity timer T430 corresponding to the ephemeris information of the serving cell times out, and the terminal cannot perform any uplink transmission in the serving cell.
  • the terminal can perform any of the following:
  • the terminal may cancel all BSRs that have been triggered before the uplink out-of-synchronization, and/or cancel the BSRs that were triggered during the uplink out-of-synchronization period.
  • the BSR triggering conditions include one or more of the following:
  • BSR timer timeout includes at least one of a BSR retransmission timer and a periodic BSR timer.
  • uplink data becomes available can be understood as when the uplink data arrives
  • the terminal has no uplink transmission resources during the uplink out-of-synchronization period or regards the uplink transmission resources as unavailable resources.
  • the terminal regards the Configured Grant (CG) resource configured by the network side device or the Dynamic Grant (DG) resource scheduled by the network side device as unavailable resources), so in this
  • the terminal can trigger BSR according to the normal process; or the BSR timer maintained by the terminal times out, where the BSR timer includes at least one of the BSR retransmission timer and the periodic BSR timer, that is, in the case of the BSR timer timeout , the terminal can trigger BSR.
  • CG Configured Grant
  • DG Dynamic Grant
  • the terminal may not follow the routine The process triggers BSR, but the BSR is delayed until uplink synchronization is restored.
  • the terminal does not trigger the BSR according to the regular process, but never triggers the BSR during the uplink out-of-synchronization period.
  • the terminal is not allowed to trigger BSR regardless of whether the BSR triggering conditions in related technologies are met. Equivalently, during the uplink out-of-synchronization period, the terminal is never allowed to trigger BSR, that is, the terminal does not need to determine whether the BSR triggering conditions are met.
  • the terminal will not trigger BSR if the BSR triggering conditions in the related technology are met. Equivalently, during the uplink out-of-synchronization period, the terminal needs to determine whether the BSR triggering conditions are met. When the terminal determines that the BSR triggering conditions are met, the terminal's behavior can be not to trigger BSR.
  • the terminal performs any of the following: cancels the triggered cache status report BSR; triggers the BSR when the BSR trigger condition is met; triggers the BSR when the BSR trigger condition is met If the conditions are met, BSR is triggered with delay; BSR is not triggered. Standardizes the terminal's BSR processing behavior during uplink out-of-synchronization, thereby preventing the terminal from initiating unnecessary uplink resource application processes after resuming uplink synchronization and improving resource utilization.
  • the cancellation of the triggered BSR includes one or more of the following:
  • the terminal When obtaining the uplink out-of-synchronization indication, the terminal cancels the BSR that has been triggered before obtaining the uplink out-of-synchronization indication.
  • the terminal can trigger the BSR according to the regular process; and when the terminal obtains the uplink out-of-synchronization indication, the terminal can trigger the BSR based on the uplink out-of-synchronization indication. , cancel all BSRs that have been triggered before the upstream out-of-synchronization indication is obtained.
  • the terminal cancels the BSR triggered during the uplink out-of-synchronization period.
  • the terminal can first trigger the BSR according to the regular process, and then the terminal can cancel all BSRs triggered during the uplink out-of-synchronization period. Equivalently, during the uplink out-of-synchronization period, the terminal still performs the behavior of triggering BSR when the triggering conditions of BSR are met. In addition, in addition to performing the behavior of triggering BSR, the terminal also performs the behavior of canceling the BSR that has been triggered, thereby ensuring that when uplink synchronization is restored, the terminal does not have a waiting BSR (pending BSR), thereby preventing the terminal from resuming uplink synchronization.
  • the BSR MAC CE reporting process always needs to be performed.
  • the terminal cancels the BSR triggered during the uplink out-of-synchronization period, which may be during the uplink out-of-synchronization period and the terminal has no data waiting for transmission (for example, the amount of data waiting for transmission is 0), The terminal cancels the BSR triggered during the uplink out-of-synchronization period.
  • the terminal when the terminal is out of synchronization in the uplink and the terminal has no data waiting to be transmitted (for example, the amount of data waiting to be transmitted is 0), the terminal can cancel the triggered BSR.
  • the triggered BSR may be triggered during the uplink out-of-synchronization period, or may be triggered at other times (for example, it may be triggered at any time before the uplink out-of-synchronization period).
  • the cancellation of the triggered BSR also includes one or more of the following:
  • the terminal can trigger BSR, and BSR can trigger SR, and then the terminal can cancel the SR triggered by BSR.
  • the terminal still performs the behavior of triggering BSR when the triggering conditions of BSR are met. Since the terminal cannot perform any transmission during the uplink out-of-synchronization period, the terminal may consider that there are no available transmission resources (such as PUSCH), so the terminal may trigger SR based on the mechanism of related technologies. In this case, in addition to performing the behavior of triggering the BSR, the terminal also performs the behavior of canceling the SR that has been triggered. This avoids that the terminal does not have an SR (pending SR) in the waiting state when uplink synchronization is restored, and the terminal always needs to perform the SR process when uplink synchronization is restored.
  • SR pending SR
  • the terminal can trigger the BSR, the BSR can trigger the SR, and the SR can initiate the random access process RACH. Then the terminal can cancel all random access processes initiated by the SR during the uplink out-of-synchronization period. Equivalently, during the uplink out-of-synchronization period, the terminal still performs the behavior of triggering BSR when the triggering conditions of BSR are met. Since the terminal cannot perform any transmission during the uplink out-of-synchronization period, the terminal can consider that there are no available transmission resources (such as PUSCH), so the terminal can trigger SR based on the mechanism of related technologies.
  • the terminal can trigger the BSR based on the mechanism of related technologies.
  • the terminal may consider that there are no available SR transmission resources (such as PUCCH), so the terminal may initiate a RACH process based on the mechanism of related technologies. In this case, in addition to performing the behavior of initiating the RACH process, the terminal also performs the behavior of stopping the initiated RACH. This prevents the terminal from not initiating a RACH process when uplink synchronization is restored, and further avoids the terminal always needing to perform a RACH process when uplink synchronization is restored.
  • SR transmission resources such as PUCCH
  • the method may include one or more of the following:
  • the terminal can trigger BSR. For example, when resuming uplink synchronization, the terminal needs to first determine whether the amount of data waiting to be transmitted is zero. If the amount of data is not zero, the terminal can trigger BSR.
  • the specific application scenario may be: during the uplink out-of-synchronization period, when the BSR triggering conditions (such as uplink data arrival) are met, the terminal performs the behavior of triggering the BSR and cancels the behavior of the triggered BSR, so that the uplink synchronization is restored. There is no BSR (pending BSR) in the waiting state at the time.
  • the terminal When resuming uplink synchronization, if the terminal still has data waiting to be transmitted (such as data arriving during uplink desynchronization), when uplink synchronization is restored, has not been discarded), at this time, in order to ensure that the data can be transmitted in time, the terminal needs to trigger BSR. In addition, it should be noted that when uplink synchronization is restored, if the terminal's uplink resources are sufficient to transmit the (latest) amount of data waiting to be transmitted, the terminal does not need to trigger BSR. When resuming uplink synchronization, if the amount of data to be transmitted by the terminal is not zero and the terminal's uplink resources are insufficient to transmit the (latest) amount of data waiting to be transmitted, the terminal needs to trigger BSR.
  • the terminal can trigger BSR .
  • the specific application scenario may be: during the uplink out-of-synchronization period, when the BSR triggering conditions (such as BSR retransmission timer and/or periodic BSR timer timeout) are met, the terminal performs the triggering BSR operation and cancels the triggered BSR operation. BSR behavior, so that there is no BSR (pending BSR) in the waiting state when uplink synchronization is restored. When resuming uplink synchronization, the terminal can trigger BSR.
  • the terminal when obtaining the uplink out-of-synchronization indication, can cancel the BSR that has been triggered before obtaining the uplink out-of-synchronization indication; the terminal can cancel the BSR that was triggered during the uplink out-of-synchronization period; the terminal can Cancel the retrieval request SR triggered by BSR; the terminal can cancel the random access process initiated by SR; when uplink synchronization is restored, if the amount of data to be transmitted by the terminal is not zero, the terminal triggers BSR; when uplink synchronization is restored, In this case, if the terminal's BSR timer times out or has expired, the terminal triggers BSR, which regulates the terminal's processing of BSR during uplink desynchronization and after uplink synchronization is restored, thereby preventing the terminal from initiating unnecessary after uplink synchronization is restored.
  • the uplink resource application process improves resource utilization.
  • the method may include one or more of the following:
  • the BSR does not trigger SR.
  • the terminal can trigger the BSR according to the normal process, but the BSR does not need to trigger the SR. .
  • the SR triggered by the BSR does not initiate a random access process.
  • the terminal triggers the BSR, and the BSR triggers the SR, but the SR triggered by the BSR does not need to initiate a random access process.
  • the method may include one or more of the following:
  • the above cancellation of the BSR by the terminal that has been triggered before the uplink synchronization is restored includes canceling the BSR that has been triggered before the uplink is out of synchronization and the BSR that is triggered during the uplink out of synchronization.
  • the upstream data is discarded due to too long waiting time (for example, due to the expiration of the packet data convergence protocol (Packet Data Convergence Protocol, PDCP) discard timer (timer) corresponding to the data packet. data packet is discarded), then when uplink synchronization is restored, the terminal's (latest) amount of data to be transmitted is zero, that is, the terminal has no data to be transmitted or the (latest) amount of data to be transmitted is zero, then the terminal can cancel All BSRs triggered according to the normal process before resuming uplink synchronization.
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • the terminal can cancel all BSRs triggered during uplink synchronization.
  • upstream data arrives and the terminal triggers BSR, but the upstream data is discarded due to too long waiting time (for example, due to the Packet Data Convergence Protocol (PDCP) corresponding to the data packet being discarded) ) timer expires and the corresponding data packet is discarded)
  • PDCP Packet Data Convergence Protocol
  • the terminal's (latest) amount of data to be transmitted is zero, that is, the terminal has no data to be transmitted or the (latest) data to be transmitted If the data amount is zero, the terminal can cancel all BSRs triggered according to the normal process during the uplink out-of-synchronization period.
  • the terminal's cancellation of SRs that have been triggered before uplink synchronization is restored includes canceling all SRs that have been triggered before uplink desynchronization and SRs that were triggered during uplink desynchronization; where the SR may be an SR triggered by a BSR.
  • the terminal when uplink synchronization is restored, if the terminal has no data to be transmitted or the (latest) amount of data to be transmitted is zero, but before uplink synchronization is restored, the terminal triggers the BSR and the BSR triggers the SR, the terminal can Cancel the SR triggered by the BSR before resuming upstream synchronization.
  • the terminal while waiting for the uplink synchronization to be restored, the uplink data arrives, the terminal triggers the BSR, and the BSR triggers the SR.
  • the terminal triggers the BSR, and the BSR triggers the SR.
  • the terminal can cancel the SR triggered by the BSR during uplink synchronization.
  • the terminal's stopping of the RACH that has been triggered before resuming uplink synchronization includes: stopping the RACH that has been initiated before the uplink is out of synchronization and the RACH that is initiated during the uplink out of synchronization.
  • the RACH may be initiated by an SR, and the SR may be triggered by a BSR.
  • the terminal before resuming uplink synchronization, the terminal triggers BSR, BSR triggers SR, and SR initiates subsequent In the machine access process, when uplink synchronization is restored, if the terminal has no data to be transmitted or the (latest) amount of data to be transmitted is zero, the terminal can stop the random access process initiated by the SR before resuming uplink synchronization. .
  • the terminal triggers the BSR, the BSR triggers the SR, and the SR initiates the random access process.
  • the terminal stops the random access process initiated by the SR during the uplink out-of-synchronization period.
  • the terminal triggers the BSR, and the BSR triggers the SR.
  • the SR transmission resources ie, PUCCH resources
  • the terminal can initiate a random access process.
  • the terminal After uplink synchronization is restored, if the terminal has no uplink resources or the uplink resources are insufficient to transmit all the data to be transmitted (which can be understood as the case where the amount of data to be transmitted is not zero) or BSR MAC CE, but the terminal has available effective SR transmission resources , then the terminal can cancel the random access process initiated by the SR during uplink synchronization. Additionally, in this case, the terminal can trigger SR.
  • the terminal can trigger SR. For example, during the uplink out-of-synchronization period, when the BSR triggering conditions are met (such as when uplink data arrives), since there are no available uplink transmission resources (ie, PUSCH resources), the terminal triggers the BSR, but the BSR is not triggered. SR.
  • the terminal When uplink synchronization is restored, if the terminal has no uplink resources or the uplink resources are insufficient to transmit all the data to be transmitted (which can be understood as the case where the amount of data to be transmitted is not zero) or BSR MAC CE, but the terminal has an available valid SR Transmission resources, at this time the terminal can trigger SR.
  • the BSR does not trigger SR, or the SR triggered by the BSR does not initiate a random access process; in the case of restoring uplink synchronization, if the terminal has no pending data, the terminal can cancel the BSR that has been triggered before resuming uplink synchronization, or the terminal can cancel the BSR that was triggered during uplink synchronization, or the terminal can cancel the SR that was triggered by the BSR before resuming uplink synchronization, or the terminal can cancel the BSR that was triggered during uplink synchronization.
  • the terminal can stop the random access process initiated by the SR before resuming uplink synchronization, or the terminal can stop the random access process initiated by the SR during the uplink out of synchronization, or if the terminal has a valid SR transmission resources, the terminal cancels the random access process initiated by the SR during uplink synchronization; or if the terminal has valid SR transmission resources, the terminal triggers SR. Standardizes the terminal's handling of BSR during uplink out-of-synchronization and when uplink synchronization is restored, thereby preventing the terminal from initiating unnecessary uplink resource application processes after restoring uplink synchronization and improving resource utilization.
  • the method may include one or more of the following:
  • the terminal When uplink synchronization is restored, the terminal triggers BSR.
  • the terminal when uplink synchronization is restored, the terminal can trigger BSR; for example, when uplink synchronization is restored, the terminal can trigger BSR, that is, during the uplink out-of-synchronization period, when uplink data arrives, the terminal does not trigger BSR, but BSR is triggered when uplink synchronization is restored.
  • BSR the terminal can trigger BSR during the uplink out-of-synchronization period, when the BSR triggering conditions are met, the terminal delays triggering BSR.
  • the terminal triggers BSR. Equivalently, when uplink synchronization is restored, the terminal will trigger BSR regardless of whether there is data waiting for transmission.
  • the terminal can perform the uplink skipping (UL skipping) process if there is no data to be transmitted. That is to say, when the terminal performs the MAC multiplexing process, if the amount of data to be transmitted indicated by the conventional BSR is zero, the terminal may not transmit the BSR MAC CE on the uplink authorized resources.
  • UL skipping uplink skipping
  • the terminal can trigger BSR; for example, when uplink synchronization is restored, the terminal needs to first determine the data waiting to be transmitted. Whether the data amount is zero. If the data amount is not zero, the terminal can trigger BSR.
  • the terminal's uplink resources are sufficient to transmit the (latest) amount of data waiting to be transmitted, the terminal does not need to trigger BSR.
  • the terminal triggers BSR.
  • the terminal when uplink synchronization is restored, if the terminal's BSR timer times out or has timed out, the terminal can trigger BSR.
  • the specific application scenario may be: during the uplink out-of-synchronization period, when the BSR triggering conditions (such as BSR retransmission timer and/or periodic BSR timer timeout) are met, the terminal performs the triggering BSR operation and cancels the triggered BSR operation. BSR behavior, so that there is no BSR (pending BSR) in the waiting state when uplink synchronization is restored. When resuming uplink synchronization, the terminal can trigger BSR.
  • the BSR triggering conditions such as BSR retransmission timer and/or periodic BSR timer timeout
  • the terminal may not trigger BSR.
  • the upstream data is discarded due to too long waiting time (for example, due to the expiration of the corresponding Packet Data Convergence Protocol (PDCP) discard timer (timer) of the corresponding data packet). discarded), when uplink synchronization is restored, the terminal's (latest) amount of data to be transmitted is zero, that is, the terminal has no data to be transmitted or the (latest) amount of data to be transmitted is zero, then the terminal does not need to trigger BSR. .
  • PDCP Packet Data Convergence Protocol
  • the terminal can trigger BSR; for example, during the uplink out-of-synchronization period, the terminal's Configured Grant (CG) resources Resources are considered unavailable. After uplink synchronization is restored, the terminal's CG resources are considered available resources. Therefore, if the terminal's CG resources are insufficient to transmit all (latest) data to be transmitted, the terminal can trigger BSR.
  • BSR Configured Grant
  • the terminal may not trigger BSR; for example, during the uplink out-of-synchronization period, the terminal's CG resources are considered to be unavailable resources. After uplink synchronization is restored, the terminal's CG resources are considered available resources. Therefore, if the terminal's CG resources are sufficient to transmit all (latest) data to be transmitted, the terminal does not need to trigger BSR.
  • the terminal when uplink synchronization is restored, the terminal triggers BSR; or if the amount of data to be transmitted by the terminal is not zero, the terminal triggers BSR; or if the BSR timer of the terminal times out or has expired. timeout, the terminal triggers BSR; or if the amount of data to be transmitted by the terminal is zero, the terminal does not trigger BSR; or if the uplink resources are insufficient to transmit all the data waiting to be transmitted, the terminal triggers BSR; or if the uplink resources are sufficient to transmit all the data waiting to be transmitted. If the data is transmitted, the terminal does not trigger BSR. Standardizes the terminal's processing of BSR when uplink synchronization is restored, thereby preventing the terminal from initiating unnecessary uplink resource application processes after restoring uplink synchronization and improving resource utilization.
  • the method may include one or more of the following:
  • the terminal can trigger BSR; for example, when uplink synchronization is restored, the terminal needs to first determine the data waiting to be transmitted. Whether the data amount is zero. If the data amount is not zero, the terminal can trigger BSR.
  • the terminal may not trigger BSR; for example, when uplink synchronization is restored, the terminal needs to first determine the waiting time Whether the amount of data transmitted is zero. If the amount of data is zero, the terminal does not need to trigger BSR.
  • the terminal can trigger BSR.
  • the specific application scenario may be: during the uplink out-of-synchronization period, when the BSR triggering conditions (such as BSR retransmission timer and/or periodic BSR timer timeout) are met, the terminal performs the triggering BSR operation and cancels the triggered BSR operation. BSR behavior, so that there is no BSR (pending BSR) in the waiting state when uplink synchronization is restored.
  • the terminal can trigger BSR.
  • the terminal when uplink synchronization is restored, if the uplink resources are insufficient to transmit all data waiting for transmission, the terminal can trigger BSR.
  • the terminal When resuming uplink synchronization, if the amount of data to be transmitted by the terminal is not zero and the terminal's uplink resources are insufficient to transmit the (latest) amount of data waiting to be transmitted, the terminal needs to trigger BSR.
  • the terminal when uplink synchronization is restored, if the amount of data to be transmitted by the terminal is not zero, the terminal triggers BSR; or if the terminal's BSR timer times out or has timed out, the terminal triggers BSR; or if the uplink resources are insufficient to transmit all data waiting for transmission, the terminal triggers BSR. Standardizes the terminal's processing of BSR when uplink synchronization is restored, thereby preventing the terminal from initiating unnecessary uplink resource application processes after restoring uplink synchronization and improving resource utilization.
  • the method also includes:
  • the terminal receives configuration information sent by a network side device; wherein the configuration information is used by the terminal to manage BSR processing behavior during the uplink out-of-synchronization period.
  • the terminal may receive configuration information sent by the network side device; wherein the configuration information is used by the terminal to manage BSR processing behavior during uplink out of synchronization. After the terminal receives the configuration information sent by the network-side device, the terminal can manage the BSR processing behavior during the uplink out-of-synchronization period based on the configuration information.
  • the configuration information includes any of the following:
  • the first indication information is used to instruct the terminal to cancel the triggered BSR during the uplink out-of-synchronization period;
  • Second indication information is used to instruct the terminal to trigger BSR during the uplink out-of-synchronization period
  • the third indication information is used to instruct the terminal to delay triggering BSR during the uplink out-of-synchronization period;
  • the fourth indication information is used to instruct the terminal not to trigger BSR during the uplink out-of-synchronization period.
  • the terminal can manage the BSR processing behavior during the uplink out of synchronization based on the configuration information. For example, the terminal can cancel the BSR processing behavior during the uplink out of synchronization based on the first indication information. Triggered BSR; the terminal can trigger BSR during the uplink out-of-synchronization period based on the second indication information; the terminal can trigger the BSR during the uplink out-of-synchronization period based on the third indication information; the terminal can trigger the BSR during the uplink out-of-synchronization period based on the fourth indication information. BSR is not triggered during this period.
  • the terminal receives the configuration information sent by the network side device.
  • Information is used for the terminal to manage the BSR processing behavior during the uplink out-of-synchronization period, which enables the terminal to manage the BSR processing behavior during the uplink out-of-synchronization period based on the configuration information, thereby standardizing the terminal's BSR processing behavior when the uplink synchronization is restored. processing, thereby preventing the terminal from initiating unnecessary uplink resource application processes after resuming uplink synchronization, and improving resource utilization.
  • Figure 4 is the second schematic flowchart of the data processing method provided by the embodiment of the present application. As shown in Figure 4, the method includes step 401; wherein:
  • Step 401 The network side device sends configuration information to the terminal;
  • the configuration information is used for the terminal to manage buffer status report BSR processing behavior during uplink out-of-synchronization.
  • the ephemeris information corresponding to the timer becomes invalid, and the terminal cannot perform any uplink transmission.
  • the network side device can send configuration information to the terminal, where the configuration information is used by the terminal to manage the BSR processing behavior during uplink out of synchronization, so that after the terminal receives the configuration information sent by the network side device, the terminal can based on the configuration information , manages BSR processing behavior during upstream desynchronization.
  • the configuration information includes any of the following:
  • the first indication information is used to instruct the terminal to cancel the triggered BSR during the uplink out-of-synchronization period;
  • Second indication information is used to instruct the terminal to trigger BSR during the uplink out-of-synchronization period
  • the third indication information is used to instruct the terminal to delay triggering BSR during the uplink out-of-synchronization period;
  • the fourth indication information is used to instruct the terminal not to trigger BSR during the uplink out-of-synchronization period.
  • the terminal can manage the BSR processing behavior during the uplink out of synchronization based on the configuration information. For example, the terminal can cancel the BSR processing behavior during the uplink out of synchronization based on the first indication information. Triggered BSR; the terminal can trigger BSR during the uplink out-of-synchronization period based on the second indication information; the terminal can trigger the BSR during the uplink out-of-synchronization period based on the third indication information; the terminal can trigger the BSR during the uplink out-of-synchronization period based on the fourth indication information. BSR is not triggered during this period.
  • the network side device sends configuration information to the terminal; wherein the configuration information is used by the terminal to manage the BSR processing behavior during uplink desynchronization, so that the terminal can manage the uplink desynchronization based on the configuration information.
  • the BSR processing behavior during this period further standardizes the terminal's processing of BSR when uplink synchronization is restored, thus preventing the terminal from initiating unnecessary uplink resource application processes after restoring uplink synchronization and improving resource utilization.
  • Step 0 The terminal maintenance validity timer (T430) times out, and the terminal’s radio resource control (Radio Resource Control (RRC) indicates that the terminal's MAC layer is out of synchronization in the uplink, and the terminal's MAC layer does not perform any uplink transmission.
  • RRC Radio Resource Control
  • Step 1 the terminal may perform any of the following:
  • the terminal can cancel all BSRs that have been triggered before the uplink out-of-synchronization, and/or cancel the BSR that was triggered during the uplink out-of-synchronization period.
  • the BSR is triggered; specifically, during the uplink out-of-synchronization period, when the uplink data becomes available (can be understood as when the uplink data arrives), that is, when the uplink data arrives or The BSR timer times out, where the BSR timer includes at least one of a BSR retransmission timer and a periodic BSR timer. Since the terminal has no uplink transmission resources or regards the uplink transmission resources as unavailable resources during the uplink out-of-synchronization period, the terminal triggers BSR according to the normal process.
  • the BSR is triggered with a delay; specifically, during the uplink out-of-synchronization period, when the uplink data arrives or the BSR timer times out, the terminal does not trigger the BSR according to the regular process, but delays until BSR is triggered after uplink synchronization is restored.
  • BSR is not triggered; specifically, during the uplink out-of-synchronization period, when the uplink data arrives, the terminal does not trigger the BSR according to the regular process, but never triggers the BSR during the uplink out-of-synchronization period.
  • canceling a triggered BSR can include one or more of the following:
  • the terminal When obtaining the uplink out-of-synchronization indication, the terminal cancels the BSR that has been triggered before obtaining the uplink out-of-synchronization indication; specifically, during the uplink out-of-synchronization period, before the terminal obtains the uplink out-of-synchronization indication, due to the arrival of uplink data,
  • the terminal can trigger BSR according to the normal process; and when the terminal obtains the uplink out-of-synchronization indication, the terminal can cancel all BSRs that have been triggered before obtaining the uplink out-of-synchronization indication based on the uplink out-of-synchronization indication.
  • the terminal cancels the BSR triggered during the uplink out-of-synchronization period; specifically, during the uplink out-of-synchronization period, due to the arrival of uplink data, the terminal can trigger the BSR according to the regular process, then the terminal can cancel all BSR triggered during the uplink out-of-synchronization period. Equivalently, during the uplink out-of-synchronization period, the terminal still performs the behavior of triggering BSR when the triggering conditions of BSR are met.
  • the terminal in addition to performing the behavior of triggering BSR, the terminal also performs the behavior of canceling the BSR that has been triggered, thereby ensuring that when uplink synchronization is restored, the terminal does not have a waiting BSR (pending BSR), thereby preventing the terminal from resuming uplink synchronization.
  • the BSR MAC CE reporting process always needs to be performed.
  • the terminal can trigger the BSR, and the BSR can trigger the SR, then the terminal can cancel the SR triggered by the BSR.
  • the terminal still performs the behavior of triggering BSR when the triggering conditions of BSR are met. Since the terminal cannot perform any transmission during the uplink out-of-synchronization period, the terminal may consider that there are no available transmission resources (such as PUSCH), so the terminal may trigger SR based on the mechanism of related technologies. In this case, in addition to performing the behavior of triggering the BSR, the terminal also performs the behavior of canceling the SR that has been triggered. This avoids that the terminal does not have an SR (pending SR) in the waiting state when resuming uplink synchronization, and thus avoids that the terminal always needs to execute when resuming uplink synchronization. SR process.
  • the terminal can trigger the BSR, the BSR can trigger the SR, and the SR can initiate the random access process RACH, then the terminal can cancel all the random access procedures initiated by the SR during the uplink out-of-synchronization period.
  • Random access process initiated by SR During the uplink out-of-synchronization period, if the triggering conditions of the BSR are met, the terminal still performs the behavior of triggering the BSR. Since the terminal cannot perform any transmission during the uplink out-of-synchronization period, the terminal can consider that there are no available transmission resources (such as PUSCH), so the terminal can trigger SR based on the mechanism of related technologies.
  • the terminal may consider that there are no available SR transmission resources (such as PUCCH), so the terminal may initiate a RACH process based on the mechanism of related technologies. In this case, in addition to performing the behavior of initiating the RACH process, the terminal also performs the behavior of stopping the initiated RACH. This prevents the terminal from not initiating a RACH process when uplink synchronization is restored, and further avoids the terminal always needing to perform a RACH process when uplink synchronization is restored.
  • SR transmission resources such as PUCCH
  • the terminal When uplink synchronization is restored, if the amount of data to be transmitted by the terminal is not zero, the terminal triggers BSR; specifically, when uplink synchronization is restored, if the terminal has data to be transmitted or (the latest) data to be transmitted If the amount of data is not zero, the terminal can trigger BSR. For example, when resuming uplink synchronization, the terminal needs to first determine whether the amount of data waiting to be transmitted is zero. If the amount of data is not zero, the terminal can trigger BSR.
  • the terminal In the case of restoring uplink synchronization, if the BSR timer of the terminal times out or has timed out, the terminal triggers BSR; specifically, in the case of restoring uplink synchronization, if the BSR timer of the terminal times out or has timed out, where, The BSR timer includes at least one of a BSR retransmission timer and a periodic BSR timer, and the terminal can trigger BSR.
  • the specific application scenario may be: during the uplink out-of-synchronization period, when the BSR triggering conditions (such as BSR retransmission timer and/or periodic BSR timer timeout) are met, the terminal performs the triggering BSR operation and cancels the triggered BSR operation. BSR behavior, so that there is no BSR (pending BSR) in the waiting state when uplink synchronization is restored. When resuming uplink synchronization, the terminal can trigger BSR.
  • the BSR triggering conditions such as BSR retransmission timer and/or periodic BSR
  • the terminal when the terminal meets the BSR triggering conditions and triggers BSR, it may include one or more of the following:
  • the BSR does not trigger SR; specifically, during the uplink out-of-synchronization period, when the triggering conditions of the BSR are met, when the uplink data arrives, because the terminal has no uplink transmission resources during this period or The uplink transmission resources are regarded as unavailable resources, so the terminal can trigger BSR according to the normal process, but BSR does not need to trigger SR.
  • the SR triggered by the BSR does not initiate the random access process; specifically, during the uplink out-of-synchronization period, when the triggering conditions of the BSR are met, the terminal triggers the BSR, and the BSR triggers the SR. , but the SR triggered by the BSR does not need to initiate the random access process.
  • the uplink data is discarded due to too long waiting time (for example, the corresponding data packet is discarded due to the timeout of the PDCP discard timer corresponding to the data packet).
  • the terminal the latest ) the amount of data to be transmitted is zero, that is, the terminal has no data to be transmitted or the (latest) amount of data to be transmitted is zero, the terminal can cancel all BSRs triggered according to the normal process before resuming uplink synchronization.
  • the terminal cancels the BSR triggered during uplink synchronization; specifically, when uplink synchronization is restored, if the terminal has no data to be transmitted or (the latest ) the amount of data to be transmitted is zero, the terminal can cancel all BSRs triggered during uplink synchronization.
  • upstream data While waiting for upstream synchronization to be restored, upstream data arrives and the terminal triggers BSR, but the upstream data is discarded due to too long waiting time (for example, due to the Packet Data Convergence Protocol (PDCP) corresponding to the data packet being discarded) ) timer expires and the corresponding data packet is discarded), then when uplink synchronization is restored, the terminal's (latest) amount of data to be transmitted is zero, that is, the terminal has no data to be transmitted or the (latest) data to be transmitted If the data amount is zero, the terminal can cancel all BSRs triggered according to the normal process during the uplink out-of-synchronization period.
  • PDCP Packet Data Convergence Protocol
  • the terminal cancels the SR triggered by the BSR before uplink synchronization is restored; it should be noted that the terminal's cancellation of the SR that has been triggered before uplink synchronization is restored includes cancellation. All SRs that have been triggered before uplink desynchronization and SRs triggered during uplink desynchronization; where the SR may be an SR triggered by a BSR.
  • the terminal when uplink synchronization is restored, if the terminal has no data to be transmitted or the (latest) amount of data to be transmitted is zero, but before uplink synchronization is restored, the terminal triggers the BSR and the BSR triggers the SR, the terminal can Cancel the SR triggered by the BSR before resuming upstream synchronization.
  • RACH includes stopping RACH that has been initiated before uplink desynchronization and RACH that was initiated during uplink desynchronization.
  • the RACH may be initiated by an SR, and the SR may be triggered by a BSR.
  • the terminal before waiting to restore uplink synchronization, the terminal triggers BSR, BSR triggers SR, and SR initiates a random access process.
  • BSR triggers SR
  • SR initiates a random access process.
  • the terminal triggers the BSR, the BSR triggers the SR, and the SR initiates the random access process.
  • the terminal stops the random access process initiated by the SR during the uplink out-of-synchronization period.
  • the terminal When uplink synchronization is restored, if the terminal has valid SR transmission resources, the terminal cancels the random access process initiated by the SR during the uplink synchronization period; for example, during the uplink out-of-synchronization period, When the BSR triggering conditions are met (such as when uplink data arrives), since there are no available uplink transmission resources (ie, PUSCH resources), the terminal triggers BSR, and BSR triggers SR. Since the SR transmission resources (ie, PUCCH resources) are also considered to be unavailable resources during the uplink out-of-synchronization period, the terminal can initiate a random access process.
  • the SR transmission resources ie, PUCCH resources
  • the terminal After uplink synchronization is restored, if the terminal has no uplink resources or the uplink resources are insufficient to transmit all the data to be transmitted (which can be understood as the case where the amount of data to be transmitted is not zero) or BSR MAC CE, but the terminal has available effective SR transmission resources , then the terminal can cancel the random access process initiated by the SR during uplink synchronization. Additionally, in this case, the terminal can trigger SR.
  • the terminal When uplink synchronization is restored, if the terminal has valid SR transmission resources, the terminal triggers SR; specifically, when uplink synchronization is restored, if the terminal has no uplink resources or the uplink resources are insufficient for transmission All data to be transmitted or BSR MAC CE, but the terminal has available effective SR transmission resources, the terminal can trigger SR. For example, during the uplink out-of-synchronization period, when the BSR triggering conditions are met (such as when uplink data arrives), since there are no available uplink transmission resources (ie, PUSCH resources), the terminal triggers the BSR, but the BSR is not triggered. SR.
  • the terminal When uplink synchronization is restored, if the terminal has no uplink resources or the uplink resources are insufficient to transmit all the data to be transmitted (which can be understood as the case where the amount of data to be transmitted is not zero) or BSR MAC CE, but the terminal has an available valid SR Transmission resources, at this time the terminal can trigger SR.
  • the method may include one or more of the following:
  • the terminal triggers BSR; for example, when uplink synchronization is restored, the terminal triggers BSR. That is, during the uplink out-of-synchronization period, the terminal does not trigger BSR when uplink data arrives, but triggers BSR when uplink synchronization is restored.
  • An exemplary application scenario is: during the uplink out-of-synchronization period, when the BSR triggering conditions are met, the terminal delays triggering BSR.
  • the terminal triggers BSR. Equivalently, when uplink synchronization is restored, the terminal will trigger BSR regardless of whether there is data waiting for transmission.
  • the terminal can perform the uplink skipping (UL skipping) process if there is no data to be transmitted. That is to say, when the terminal performs the MAC multiplexing process, if the amount of data to be transmitted indicated by the conventional BSR is zero, the terminal may not transmit the BSR MAC CE on the uplink authorized resources.
  • UL skipping uplink skipping
  • the terminal triggers BSR; for example, when uplink synchronization is restored, the terminal needs to first determine the amount of data waiting to be transmitted. Whether it is zero, if the data amount is not zero, the terminal triggers BSR.
  • BSR the terminal's uplink resources are sufficient to transmit the (latest) amount of data waiting to be transmitted.
  • the terminal does not need to trigger BSR.
  • the terminal triggers BSR; specifically, in the case of restoring uplink synchronization, if the terminal's BSR timer times out or has timed out, the terminal BSR can be triggered.
  • the specific application scenario may be: during the uplink out-of-synchronization period, when the BSR triggering conditions (such as BSR retransmission timer and/or periodic BSR timer timeout) are met, the terminal performs the triggering BSR operation and cancels the triggered BSR operation. BSR behavior, so that there is no BSR (pending BSR) in the waiting state when uplink synchronization is restored. When resuming uplink synchronization, the terminal can trigger BSR.
  • the terminal When uplink synchronization is restored, if the terminal has no data to be transmitted or the amount of data waiting to be transmitted is zero, the terminal does not trigger BSR; specifically, when uplink synchronization is restored, if the terminal has no data to be transmitted Or the (latest) amount of data to be transmitted is zero, the terminal does not need to trigger BSR. For example, when resuming uplink synchronization, the terminal needs to first determine whether the amount of data waiting to be transmitted is zero. If the amount of data is zero, the terminal does not trigger BSR.
  • the terminal When uplink synchronization is restored, if the uplink resources are insufficient to transmit all data waiting for transmission, the terminal triggers BSR; for example, during the uplink out-of-synchronization period, the terminal's CG resources are considered to be unavailable resources. After synchronization, the terminal's CG resources are considered available resources. Therefore, if the CG resources are insufficient to transmit all (the latest) data to be transmitted, the terminal triggers BSR.
  • the terminal When uplink synchronization is restored, if the uplink resources are sufficient to transmit all data waiting for transmission, the terminal does not trigger BSR; for example, during the uplink out-of-synchronization period, the terminal's CG resources are considered to be unavailable resources. After synchronization, the terminal's CG resources are considered available resources. Therefore, if the CG resources are sufficient to transmit all (the latest) data to be transmitted, the terminal does not trigger BSR.
  • the terminal may also include one or more of the following:
  • the terminal When uplink synchronization is restored, if the terminal has data to be transmitted or the amount of data waiting to be transmitted is not zero, the terminal triggers BSR; for example, when uplink synchronization is restored, the terminal needs to first determine the amount of data waiting to be transmitted. Whether it is zero, if the data amount is not zero, the terminal triggers BSR.
  • the terminal When uplink synchronization is restored, if the terminal has data to be transmitted or the amount of data waiting to be transmitted is zero, the terminal does not trigger BSR; for example, when uplink synchronization is restored, the terminal needs to first determine the amount of data waiting to be transmitted. Whether it is zero, when the data amount is zero, the terminal does not trigger BSR.
  • Step 2 The terminal receives configuration information from the network side.
  • the configuration information is used to manage the BSR processing behavior of the terminal during uplink out of synchronization.
  • the configuration information includes one or more of the following:
  • the first indication information is used to instruct the terminal to trigger BSR according to the regular process during uplink out of synchronization;
  • the second indication information is used to instruct the terminal to delay triggering BSR during uplink out of synchronization
  • the third indication information is used to instruct the terminal not to trigger BSR during uplink out of synchronization.
  • the execution subject may be a data processing device.
  • a data processing device executing a data processing method is used as an example to illustrate the data processing device provided by the embodiment of the present application.
  • Figure 5 is one of the schematic structural diagrams of a data processing device provided by an embodiment of the present application. As shown in Figure 5, the data processing device 500 is applied to a terminal (for example, the data processing device 500 may include at least some modules or functions of the terminal). , or the terminal includes a data processing device 500), including:
  • Execution module 501 is used to execute any of the following during uplink desynchronization:
  • BSR is triggered
  • the BSR is triggered with a delay
  • any one of the following is performed: canceling the triggered cache status report BSR; triggering the BSR when the BSR triggering condition is met; and triggering the BSR when the BSR triggering condition is met.
  • the above-mentioned processing behavior of BSR is standardized during the uplink out-of-synchronization period, thus preventing the terminal from initiating unnecessary uplink resource application process after the uplink synchronization is restored, and improving resource utilization.
  • the cancellation of the triggered BSR includes one or more of the following:
  • the terminal When obtaining the uplink out-of-synchronization indication, the terminal cancels the BSR that has been triggered before obtaining the uplink out-of-synchronization indication;
  • the terminal cancels the BSR triggered during the uplink out-of-synchronization period.
  • the terminal cancels the BSR triggered during the uplink out-of-synchronization period, which may be during the uplink out-of-synchronization period and the terminal has no data waiting for transmission (for example, the amount of data waiting for transmission is 0), The terminal cancels the BSR triggered during the uplink out-of-synchronization period.
  • the terminal when the terminal is out of synchronization in the uplink and the terminal has no data waiting to be transmitted (for example, the amount of data waiting to be transmitted is 0), the terminal can cancel the triggered BSR.
  • the triggered BSR may be triggered during the uplink out-of-synchronization period, or may be triggered at other times (for example, it may be triggered at any time before the uplink out-of-synchronization period).
  • the cancellation of the triggered BSR also includes one or more of the following:
  • the data processing device 500 is also used for one or more of the following:
  • the data processing device 500 is configured to perform one or more of the following:
  • the BSR does not trigger SR
  • the SR triggered by the BSR does not initiate a random access process.
  • the data processing device 500 includes one or more of the following:
  • the data processing device 500 is configured to perform one or more of the following:
  • BSR is triggered
  • the data processing device 500 is configured to perform one or more of the following:
  • BSR is triggered.
  • the BSR triggering conditions include one or more of the following:
  • the BSR timer times out; wherein the BSR timer includes at least one of a BSR retransmission timer and a periodic BSR timer.
  • the data processing device 500 further includes:
  • a receiving module configured to receive configuration information sent by the network side device; wherein the configuration information is used by the terminal to manage BSR processing behavior during the uplink out of synchronization period.
  • the configuration information includes any of the following:
  • the first indication information is used to instruct the terminal to cancel the triggered BSR that has been triggered during the uplink out-of-synchronization period;
  • the second indication information is used to instruct the terminal to trigger BSR during the uplink out-of-synchronization period
  • the third indication information is used to instruct the terminal to delay triggering BSR during the uplink out-of-synchronization period;
  • the fourth indication information is used to instruct the terminal not to trigger BSR during the uplink out-of-synchronization period.
  • FIG 6 is the second structural schematic diagram of the data processing device provided by the embodiment of the present application. As shown in Figure 6, the data processing device 600 is applied to network side equipment and includes:
  • the configuration information is used for the terminal to manage buffer status report BSR processing behavior during uplink out-of-synchronization.
  • configuration information is sent to the terminal; where the configuration information is used by the terminal to manage the BSR processing behavior during the uplink out-of-synchronization period, so that the terminal can manage the BSR during the uplink out-of-synchronization period based on the configuration information.
  • the processing behavior further standardizes the terminal's processing of BSR when uplink synchronization is restored, thereby preventing the terminal from initiating unnecessary uplink resource application processes after restoring uplink synchronization and improving resource utilization.
  • the configuration information includes at least one of the following:
  • the first indication information is used to instruct the terminal to cancel the triggered BSR during the uplink out-of-synchronization period;
  • the second indication information is used to instruct the terminal to trigger BSR during the uplink out-of-synchronization period
  • the third indication information is used to instruct the terminal to delay triggering BSR during the uplink out-of-synchronization period;
  • the fourth indication information is used to instruct the terminal not to trigger BSR during the uplink out-of-synchronization period.
  • the data processing device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.
  • NAS Network Attached Storage
  • the data processing device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 3 or Figure 4, and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 700 includes a processor 701 and a memory 702.
  • the memory 702 stores programs that can run on the processor 701. or instructions.
  • the communication device 700 is a terminal, when the program or instructions are executed by the processor 701, each step of the above data processing method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 700 is a network-side device, when the program or instruction is executed by the processor 701, each step of the above-mentioned data processing method embodiment is implemented, and the same technical effect can be achieved. To avoid duplication, the details will not be described here.
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the processor is configured to perform any of the following during uplink desynchronization:
  • BSR is triggered
  • the BSR is triggered with a delay
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • Figure 8 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • the terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, and a display unit. 806. At least some components of the user input unit 807, the interface unit 808, the memory 809, the processor 810, and the like.
  • the terminal 800 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 810 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 8 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 804 may include a graphics processing unit (Graphics Processing Unit (GPU) 8041 and microphone 8042, the graphics processor 8041 processes image data of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode.
  • the display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072 . Touch panel 8071, also known as touch screen.
  • the touch panel 8071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 8072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 801 after receiving downlink data from the network side device, the radio frequency unit 801 can transmit it to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network side device.
  • the radio frequency unit 801 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 809 may be used to store software programs or instructions as well as various data.
  • the memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 809 may include volatile memory or non-volatile memory, or memory 809 may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus
  • the processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 810.
  • the processor 810 is used to perform any of the following during the uplink out-of-synchronization period:
  • BSR is triggered
  • the BSR is triggered with a delay
  • the BSR that has been triggered before the uplink out-of-synchronization indication is obtained can be canceled; the terminal can cancel the BSR triggered during the uplink out-of-synchronization period; the terminal can cancel the BSR triggering Retrieve request SR; the terminal can cancel the random access process initiated by the SR; when uplink synchronization is restored, if the amount of data to be transmitted by the terminal is not zero, the terminal triggers BSR; when uplink synchronization is restored, If the terminal's BSR timer times out or has expired, the terminal triggers BSR, which regulates the terminal's processing of BSR during uplink out of synchronization and after uplink synchronization is restored, thereby preventing the terminal from initiating unnecessary uplink resources after uplink synchronization is restored. application process and improve resource utilization.
  • Embodiments of the present application also provide a network side device, including a processor and a communication interface, wherein the communication interface is used to send configuration information to a terminal; wherein the configuration information is used for the terminal to manage uplink desynchronization during the period.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • FIG 9 is a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • the network side device 900 includes: an antenna 901, a radio frequency device 902, a baseband device 903, a processor 904 and a memory 905.
  • Antenna 901 is connected to radio frequency device 902.
  • the radio frequency device 902 receives information through the antenna 901 and sends the received information to the baseband device 903 for processing.
  • the baseband device 903 processes the information to be sent and sends it to the radio frequency device 902.
  • the radio frequency device 902 processes the received information and then sends it out through the antenna 901.
  • the method performed by the network side device in the above embodiment can be implemented in the baseband device 903, which includes a baseband processor.
  • the baseband device 903 may include, for example, at least one baseband board on which multiple chips are disposed, as shown in FIG. 9 .
  • One of the chips is, for example, a baseband processor, which is connected to the memory 905 through a bus interface to call the Program to perform the network device operations shown in the above method embodiments.
  • the network side device may also include a network interface 906, which is, for example, a common public radio interface (CPRI).
  • a network interface 906 which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 900 in this embodiment of the present invention also includes: instructions or programs stored in the memory 905 and executable on the processor 904.
  • the processor 904 calls the instructions or programs in the memory 905 to execute the instructions or programs in the memory 905 as described above in Figure 4
  • the method is shown and achieves the same technical effect. To avoid repetition, it will not be described again here.
  • Embodiments of the present application also provide a data processing system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the data processing method on the terminal side as described above.
  • the network side device can be used to perform the above steps. The steps of the data processing method on the network side device side described above.
  • Embodiments of the present application also provide a readable storage medium.
  • the readable storage medium may be volatile or non-volatile.
  • the readable storage medium stores a program or instructions. The program Or when the instructions are executed by the processor, each process of the above data processing method embodiment is implemented, and the same technical effect can be achieved, To avoid repetition, they will not be repeated here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium may be non-volatile or non-transient.
  • Readable storage media may include computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disks or optical disks.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the above data processing method embodiment. Each process can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above data processing method embodiment.
  • Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

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

Abstract

本申请公开了一种数据处理方法、终端及网络侧设备，属于通信技术领域，本申请实施例的数据处理方法包括：在上行失步期间，终端执行以下任意一项：取消已经触发的缓存状态报告BSR；在满足BSR触发条件的情况下，触发BSR；在满足BSR触发条件的情况下，延迟触发BSR；不触发BSR。

Description

数据处理方法、终端及网络侧设备
相关申请的交叉引用
本申请要求在2022年08月10日提交中国专利局、申请号为202210957929.8、名称为“数据处理方法、终端及网络侧设备”以及在2022年08月17日提交中国专利局、申请号为202210987783.1、名称为“数据处理方法、终端及网络侧设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请属于通信技术领域，具体涉及一种数据处理方法、终端及网络侧设备。
背景技术
在R17非地面网络(Non-Terrestrial Networks，NTN)场景中，当星历信息对应的有效性定时器超时，终端不能进行任何上行传输，直至获取到最新有效的星历信息。
相关技术中，在星历信息对应的有效性定时器超时至终端重新获取到最新有效的星历信息期间，终端可能会触发缓存状态报告(Buffer Status Report，BSR)(例如当终端有上行数据到达时)，此时尽管没有可用的上行资源传输对应的上行数据，终端仍会触发一系列的资源申请过程，如触发BSR、调度请求(Scheduling Request，SR)、随机接入信道(Random Access Channel，RACH)等。在上行传输恢复时，终端将会继续触发一系列的资源申请过程以申请上行资源。
然而，在终端重新获取到最新有效的星历信息期间，到达终端的上行数据可能由于等待时间过久而已被丢弃。因此，在上行传输恢复时，终端仍执行上行资源的申请过程(如RACH，发送BSR媒体接入控制(Medium Access Control，MAC)控制单元(Control Element，CE))，导致资源浪费。
发明内容
本申请实施例提供一种数据处理方法、终端及网络侧设备，能够解决资源浪费的问题。
第一方面，提供了一种数据处理方法，该方法包括：
在上行失步期间，终端执行以下任意一项：
取消已经触发的缓存状态报告BSR；
在满足BSR触发条件的情况下，触发BSR；
在满足BSR触发条件的情况下，延迟触发BSR；
不触发BSR。
第二方面，提供了一种数据处理方法，该方法包括：
网络侧设备向终端发送配置信息；
其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。
第三方面，提供了一种数据处理装置，该装置包括：
执行模块，用于在上行失步期间，执行以下任意一项：
取消已经触发的缓存状态报告BSR；
在满足BSR触发条件的情况下，触发BSR；
在满足BSR触发条件的情况下，延迟触发BSR；
不触发BSR。
第四方面，提供了一种数据处理装置，该装置包括：
发送模块，用于向终端发送配置信息；
其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口；其中，所述处理器用于在上行失步期间，执行以下任意一项：
取消已经触发的缓存状态报告BSR；
在满足BSR触发条件的情况下，触发BSR；
在满足BSR触发条件的情况下，延迟触发BSR；
不触发BSR。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口；其中，所述通信接口用于向终端发送配置信息；其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。
第九方面，提供了一种数据处理系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的方法的步骤，所述网络侧设备可用于执行如第二方面所述的方法的步骤。
第十方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
在本申请实施例中，在上行失步期间，终端通过执行以下任意一项：取消已经触发的缓存状态报告BSR；在满足BSR触发条件的情况下，触发BSR；在满足BSR触发条件的情况下，延迟触发BSR；不触发BSR，规范了在上行失步期间，终端对BSR的处理行为，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
附图说明
图1是本申请实施例可应用的无线通信系统的示意图；
图2是本申请实施例可应用的非地面网络的示意图；
图3是本申请实施例提供的数据处理方法的流程示意图之一；
图4是本申请实施例提供的数据处理方法的流程示意图之二；
图5是本申请实施例提供的数据处理装置的结构示意图之一；
图6是本申请实施例提供的数据处理装置的结构示意图之二；
图7是本申请实施例提供的通信设备的结构示意图；
图8是本申请实施例提供的终端的结构示意图；
图9是本申请实施例提供的网络侧设备的结构示意图。
具体实施例
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的通信系统，如第6代(6th Generation，6G)通信系统。
图1是本申请实施例可应用的无线通信系统的示意图，图1示出的无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(VUE)、行人终端(PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。
网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network，RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、WLAN接入点或WiFi节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的数据处理方法进行详细地说明。
本申请各实施例针对终端在上行失步期间，到达终端的上行数据可能由于等待 时间过久而已被丢弃，而在恢复上行同步时，终端仍执行上行资源的申请过程，导致资源浪费的问题，提供一种解决方法，能够规范在上行失步期间，终端对BSR的处理行为，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。为了便于更加清晰地理解本申请各实施例，首先对一些相关的技术知识进行如下介绍。
1.非地面网络(Non-terrestrial networks，NTN)简介
图2是本申请实施例可应用的非地面网络的示意图，如图2所示，典型的NTN部署场景包括终端21、卫星(Satellite)(或无人空中系统平台(Unmanned Aerial System platform，UAS platform))22和网关(Gateway)(或基站)23。在R17版本中，终端21、基站23以及核心网设备均部署在地面上，终端21和基站23之间的通信数据经由空中的卫星22进行中转。如图2所示，终端21和卫星22之间的链路称为服务链路(即service link)，卫星22和基站23之间的链路称为馈线链路(即feeder link)。
相对于地面通信(Terrestrial Networks，TN)系统，基于卫星的非地面通信系统具有更为广阔的覆盖范围，因此，可适用于对于沙漠、偏远村庄等进行补充覆盖以及适用于对自然灾害地区进行应急通信覆盖。
2.星历信息维护
NTN场景下，终端需要维护卫星的星历信息，以便于进行诸如上行传输补偿、移动性管理等操作。在R17版本中，网络侧设备可以通过SIB19提供服务小区的星历信息。终端对接收到的星历信息之后，终端会维护对应的有效性定时器(T430)，在定时器超时后，终端认为定时器对应的星历信息失效，则终端不能进行任何上行传输。示例性的，在服务小区对应的T430超时的情况下，服务小区对应的星历信息失效。终端的无线资源控制(Radio Resource Control，RRC)会指示MAC层服务小区上行失步。此时，MAC层将不能执行任何上行传输。在重新获取到SIB19后，终端可以恢复上行传输。示例性的，在服务小区对应的T430超时，终端会重新获取SIB19。在成功获取到SIB19时，终端的RRC会指示MAC服务小区上行同步。此时，MAC层允许执行上传传输。
3.上行资源处理
在相关技术的机制中，当诸如数据到达时(如高优先级数据到达)，终端会触发BSR过程以申请上行资源。当没有上行资源或上行资源(即物理上行共享信道(Physical Uplink Shared Channel，PUSCH)资源)不足以传输BSR时，终端会触发SR过程。当没有有效的资源(即物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源)传输SR时，终端会发起随机接入信道(Random Access Channel，RACH)过程。
本申请实施例提供的数据处理方法，可应用于NTN场景中，在上行失步期间， 终端执行以下任意一项：取消已经触发的缓存状态报告BSR；在满足BSR触发条件的情况下，触发BSR；在满足BSR触发条件的情况下，延迟触发BSR；不触发BSR。规范了在上行失步期间，终端对BSR的处理行为，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
图3是本申请实施例提供的数据处理方法的流程示意图之一，如图3所示，该方法包括步骤301；其中：
步骤301、在上行失步期间，终端执行以下任意一项：
取消已经触发的缓存状态报告BSR；
在满足BSR触发条件的情况下，触发BSR；
在满足BSR触发条件的情况下，延迟触发BSR；
不触发BSR。
需要说明的是，本申请实施例可应用于NTN场景中，终端包括但不限于上述所列举的终端11的类型，网络侧设备包括但不限于上述所列举的网络侧设备12的类型，本申请实施例对此并不限定。
具体地，当终端维护的有效性定时器超时，定时器对应的星历信息失效，终端不能进行任何上行传输。示例性的，与服务小区的星历信息对应的有效性定时器T430超时，终端不能在该服务小区进行任何上行传输。
实际中，在上行失步期间，终端可以执行以下任意一项：
1)取消已经触发的缓存状态报告BSR。
具体地，在上行失步期间，终端可以取消在上行失步之前已经触发的所有BSR，和/或，取消在上行失步期间触发的BSR。
2)在满足BSR触发条件的情况下，触发BSR。
可选地，所述BSR触发条件包括以下一项或多项：
a)上行数据到达；
b)BSR定时器超时；其中，所述BSR定时器包括BSR重传定时器和周期性BSR定时器中的至少一项。
具体地，在上行失步期间，在上行数据变得可用的情况下(可理解为在上行数据到达时)，由于在上行失步期间终端没有上行传输资源或者将上行传输资源视为不可用资源(如在上行失步期间，终端将网络侧设备配置的配置授权(Configured Grant，CG)资源，或网络侧设备调度的动态授权(Dynamical Grant，DG)资源视为不可用资源)，因此在该情况下终端可以按照常规流程触发BSR；或者终端维护的BSR定时器超时，其中，BSR定时器包括BSR重传定时器和周期性BSR定时器中的至少一项，即在BSR定时器超时的情况下，终端可以触发BSR。
3)在满足BSR触发条件的情况下，延迟触发BSR。
具体地，在上行数据到达时或BSR定时器超时的情况下，终端可以不按照常规 流程触发BSR，而是延迟到恢复上行同步后触发BSR。
4)不触发BSR。
具体地，在上行失步期间，在上行数据到达的情况下，终端不按照常规流程触发BSR，而是在上行失步期间始终不触发BSR。
需要说明的是，终端不触发BSR存在两种情况，其中：
1)在上行失步期间，无论相关技术中的BSR触发条件是否满足，终端不允许触发BSR。相当于，在上行失步期间，终端始终不允许触发BSR，即终端无需判断是否满足BSR触发条件。
2)在上行失步期间，在相关技术中的BSR触发条件满足的情况下，终端不会触发BSR。相当于，在上行失步期间，终端需要判断是否满足BSR触发条件，终端在判断满足BSR触发条件的情况下，终端的行为可以为不触发BSR。
本申请实施例提供的数据处理方法中，在上行失步期间，终端通过执行以下任意一项：取消已经触发的缓存状态报告BSR；在满足BSR触发条件的情况下，触发BSR；在满足BSR触发条件的情况下，延迟触发BSR；不触发BSR。规范了在上行失步期间，终端对BSR的处理行为，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
下面对本申请实施例中在上行失步期间，终端执行对BSR的处理的具体方式进行说明。
1、取消已经触发的BSR
可选地，所述取消已经触发的BSR包括以下一项或多项：
1)在获取到上行失步指示时，所述终端取消在获取到所述上行失步指示之前已经触发的BSR。
具体地，在上行失步期间，终端在获取到上行失步指示之前，由于上行数据到达，终端可以按照常规流程触发BSR；而终端在获取到上行失步指示时，终端可以基于上行失步指示，取消在获取到上行失步指示之前已经触发的所有BSR。
2)所述终端取消在所述上行失步期间触发的BSR。
具体地，在上行失步期间，由于上行数据到达，终端可以先按照常规流程触发BSR，则终端可以取消在上行失步期间触发的所有BSR。相当于，在上行失步期间，在满足BSR的触发条件的情况下，终端仍执行触发BSR的行为。此外，终端除了执行触发BSR的行为之外，终端还执行取消已经触发BSR的行为，从而保证在恢复上行同步时，终端没有处于等待状态的BSR(pending BSR)，进而避免在恢复上行同步时终端始终需要执行BSR MAC CE上报过程。
可选地，所述终端取消在所述上行失步期间触发的BSR，可以是在上行失步期间且所述终端无等待传输的数据(例如，等待传输的数据量为0)的情况下，所述终端取消在所述上行失步期间触发的BSR。
在另一种可选的实施方式中，终端可以在上行失步期间且所述终端无等待传输的数据(例如，等待传输的数据量为0)的情况下，所述终端取消已触发的BSR。需要说明的是，该已触发的BSR，可以是在上行失步期间触发的，也可以是在其他时间触发的(例如，可以是在上行失步期间之前的任意时间触发的)。
可选地，所述取消已经触发的BSR还包括以下一项或多项：
a)取消BSR触发的调取请求(Scheduling Request，SR)。
具体地，在上行同步期间，终端可以触发BSR，BSR可以触发SR，则终端可以取消BSR触发的SR。相当于，在上行失步期间，在满足BSR的触发条件的情况下，终端仍执行触发BSR的行为。由于在上行失步期间终端不能执行任何传输，则终端可认为无可用传输资源(如PUSCH)，因此终端可以基于相关技术的机制触发SR。在此情况下，终端除了执行触发BSR的行为之外，终端还执行取消已经触发SR的行为。从而避免在恢复上行同步时，终端没有处于等待状态的SR(pending SR)，进而避免在恢复上行同步时终端始终需要执行SR过程。
b)取消由SR发起的随机接入过程。
具体地，在上行同步期间，终端可以触发BSR，BSR可以触发SR，SR可以发起随机接入过程RACH，则终端可以取消在上行失步期间所有由SR发起的随机接入过程。相当于，在上行失步期间，在满足BSR的触发条件的情况下，终端仍执行触发BSR的行为。由于在上行失步期间终端不能执行任何传输，终端可认为无可用传输资源(如PUSCH)，因此终端可以基于相关技术的机制触发SR。由于在上行失步期间终端不能执行任何传输，终端可认为无可用的SR传输资源(如PUCCH)，因此终端可以基于相关技术的机制发起RACH过程。在此情况下，终端除了执行发起RACH过程的行为之外，终端还执行停止发起的RACH的行为。从而避免在恢复上行同步时，终端没有发起的RACH过程，进而避免在恢复上行同步时终端始终需要执行RACH过程。
可选地，在所述终端取消已经触发的BSR的情况下，所述方法可以包括以下一项或多项：
1)在恢复上行同步的情况下，若所述终端的待传数据量不为零，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若终端有待传的数据或者(最新的)待传数据量不为零，则终端可以触发BSR。示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量不为零的情况下，终端可以触发BSR。具体的应用场景可以是：在上行失步期间，在满足BSR触发条件(诸如上行数据到达)的情况下，终端执行了触发BSR的行为以及取消已经触发的BSR的行为，从而使得在恢复上行同步时并没有处于等待状态的BSR(pending BSR)。在恢复上行同步时，若终端仍有等待传输的数据(如上行失步期间到达的数据在恢复上行同步时 还没有被丢弃)，此时为了保证数据能及时传输，终端需触发BSR。另外，需要说明的是，在恢复上行同步时，如果终端的上行资源足以传输(最新的)等待传输的数据量，终端是无需触发BSR的。而在恢复上行同步时，如果终端的待传数据量不为零且终端的上行资源不足以传输(最新的)等待传输的数据量的情况下，终端需要触发BSR。
2)在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若终端的BSR定时器超时或者已经超时，其中，BSR定时器包括BSR重传定时器和周期性BSR定时器中的至少一项，则终端可以触发BSR。具体的应用场景可以是：在上行失步期间，在满足BSR触发条件(诸如BSR重传定时器和/或周期性BSR定时器超时)的情况下，终端执行了触发BSR操作以及取消已经触发的BSR的行为，从而使得在恢复上行同步时并没有处于等待状态的BSR(pending BSR)。在恢复上行同步时，终端可以触发BSR。
本申请实施例提供的数据处理方法中，在获取到上行失步指示时，终端可以取消在获取到上行失步指示之前已经触发的BSR；终端可以取消在上行失步期间触发的BSR；终端可以取消BSR触发的调取请求SR；终端可以取消由SR发起的随机接入过程；在恢复上行同步的情况下，若终端的待传数据量不为零，则终端触发BSR；在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则终端触发BSR，规范了在上行失步期间以及恢复上行同步后终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
2、触发BSR
可选地，在所述终端在满足BSR触发条件，触发BSR的情况下，所述方法可以包括以下一项或多项：
1)在上行失步期间，所述BSR不触发SR。
具体地，在上行失步期间，在上行数据到达时，由于在该期间终端没有上行传输资源或者将上行传输资源视为不可用资源，因此终端可以按照常规流程触发BSR，但BSR可以不触发SR。
2)在上行失步期间，由所述BSR触发的SR不发起随机接入过程。
具体地，在上行失步期间，在满足BSR的触发条件的情况下，终端触发了BSR，BSR触发了SR，但由BSR触发的SR可以不发起随机接入过程。
可选地，在所述终端触发BSR的情况下，所述方法可以包括以下一项或多项：
a)在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在恢复上行同步之前已经触发的BSR。
需要说明的是，上述的终端取消在恢复上行同步之前已经触发的BSR包括取消在上行失步之前已经触发的BSR和在上行失步期间触发的BSR。
具体地，在等待恢复上行同步期间，上行数据由于等待时间过久被丢弃(例如由于数据包对应的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)丢弃(discard)定时器(timer)超时导致对应数据包被丢弃)，则在恢复上行同步的情况下，终端(最新的)待传数据量为零，即终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在恢复上行同步之前所有按照常规流程触发的BSR。
b)在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在上行同步期间触发的BSR。
具体地，在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在上行同步期间触发的所有BSR。在等待恢复上行同步期间，上行数据到达，而终端触发了BSR，但是该上行数据由于等待时间过久被丢弃(例如由于数据包对应的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)丢弃(discard)定时器(timer)超时导致对应数据包被丢弃)，则在恢复上行同步的情况下，终端(最新的)待传数据量为零，即终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在上行失步期间所有按照常规流程触发的BSR。
c)在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在恢复上行同步之前由BSR触发的SR。
需要说明的是，终端取消在恢复上行同步之前已经触发的SR包括取消在上行失步之前已经触发的所有SR和在上行失步期间触发的SR；其中，SR可以是由BSR触发的SR。
具体地，在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，但在恢复上行同步之前，终端触发了BSR，BSR触发了SR，则终端可以取消在恢复上行同步之前由BSR触发的SR。
d)在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在上行同步期间由BSR触发的SR。
具体地，在等待恢复上行同步期间，上行数据到达，终端触发了BSR，BSR触发了SR，则在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在上行同步期间由BSR触发的SR。
e)在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端停止在恢复上行同步之前由SR发起的随机接入过程。
需要说明的是，终端停止在恢复上行同步之前已经触发的RACH包括：停止在上行失步之前已经发起的RACH和在上行失步期间发起的RACH。其中，所述的RACH可以是由SR发起，所述SR是由BSR触发的。
具体地，在恢复上行同步之前，终端触发了BSR，BSR触发了SR，SR发起随 机接入过程，则在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端可以停止在恢复上行同步之前由SR发起的随机接入过程。
f)在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端停止在上行失步期间由SR发起的随机接入过程。
具体地，在上行失步期间，上行数据到达，终端触发了BSR，BSR触发了SR，SR发起随机接入过程，则在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端停止在上行失步期间由SR发起的随机接入过程。
g)在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则所述终端取消在上行同步期间由SR发起的随机接入过程。
示例性的，在上行失步期间，在满足BSR触发条件的情况下(如在上行数据到达时)，由于无可用的上行传输资源(即PUSCH资源)，则终端触发了BSR，BSR触发了SR。由于在上行失步期间，SR传输资源(即PUCCH资源)也被认为是不可用资源，因此，终端可以发起随机接入过程。在恢复上行同步后，若终端无上行资源或者上行资源不足以传输所有待传数据(可理解为待传数据量不为零的情况下)或BSR MAC CE，但是终端有可用的有效SR传输资源，则终端可以取消在上行同步期间由SR发起的随机接入过程。额外的，在该情况下，终端可以触发SR。
h)在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则所述终端触发SR。
具体地，在恢复上行同步的情况下，若终端无上行资源或者上行资源不足以传输所有待传数据或BSR MAC CE，但是终端有可用的有效SR传输资源，则终端可以触发SR。示例性的，在上行失步期间，在满足BSR触发条件的情况下(如在上行数据到达时)，由于无可用的上行传输资源(即PUSCH资源)，则终端触发了BSR，但BSR没有触发SR。在恢复上行同步的情况下，若终端无上行资源或者上行资源不足以传输所有待传数据(可理解为待传数据量不为零的情况下)或BSR MAC CE，但是终端有可用的有效SR传输资源，此时终端可以触发SR。
本申请实施例提供的数据处理方法中，在上行失步期间，BSR不触发SR，或者由BSR触发的SR不发起随机接入过程；在在恢复上行同步的情况下，若终端没有待传的数据，则终端可以取消在恢复上行同步之前已经触发的BSR，或者终端可以取消在上行同步期间触发的BSR，或者终端可以取消在恢复上行同步之前由BSR触发的SR，或者终端可以取消在上行同步期间由BSR触发的SR，或者终端可以停止在恢复上行同步之前由SR发起的随机接入过程，或者终端可以停止在上行失步期间由SR发起的随机接入过程，或者若终端有有效的SR传输资源，则终端取消在上行同步期间由SR发起的随机接入过程；或者若终端有有效的SR传输资源，则终端触发SR。规范了在上行失步期间以及在恢复上行同步的情况下终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
3、延迟触发BSR
可选地，在所述终端在满足BSR触发条件，执行延迟触发BSR的情况下，所述方法可以包括以下一项或多项：
1)在恢复上行同步的情况下，所述终端触发BSR。
具体地，在恢复上行同步的情况下，终端可以触发BSR；示例性的，在恢复上行同步时，终端可以触发BSR，即在上行失步期间，在上行数据到达时，终端没有触发BSR，而是在恢复上行同步的情况下触发BSR。示例性的应用场景是：在上行失步期间，在满足BSR触发条件的情况下，终端延迟触发BSR。在恢复上行同步的情况下，终端触发BSR。相当于，在恢复上行同步的情况下，无论是否有等待传输的数据，终端都会触发BSR。另外需要说明的是，在该种情况下，如果触发的是常规BSR，那么在没有待传数据的情况下，终端可以执行上行跳过(UL skipping)过程。也就是说，终端在执行MAC复用过程时，如果常规BSR指示的待传数据量为零，则终端可以不在上行授权资源上传输BSR MAC CE。
2)在恢复上行同步的情况下，若所述终端的待传数据量不为零，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若终端有待传的数据或者等待传输的数据量不为零，则终端可以触发BSR；示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量不为零的情况下，终端可以触发BSR。另外需要说明的是，在恢复上行同步时，如果终端的上行资源足以传输(最新的)等待传输的数据量，终端是无需触发BSR的。而在恢复上行同步时，如果终端的待传数据量不为零且终端的上行资源不足以传输(最新的)等待传输的数据量的情况下，终端触发BSR。
3)在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若终端的BSR定时器超时或已经超时，则终端可以触发BSR。具体的应用场景可以是：在上行失步期间，在满足BSR触发条件(诸如BSR重传定时器和/或周期性BSR定时器超时)的情况下，终端执行了触发BSR操作以及取消已经触发的BSR的行为，从而使得在恢复上行同步时并没有处于等待状态的BSR(pending BSR)。在恢复上行同步时，终端可以触发BSR。
4)在恢复上行同步的情况下，若所述终端的待传数据量为零，则所述终端不触发BSR。
具体地，在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传输的数据量为零，则终端可以不触发BSR。在等待恢复上行同步期间，上行数据由于等待时间过久被丢弃(例如由于数据包对应的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)丢弃(discard)定时器(timer)超时导致对应数据包 被丢弃)，则在恢复上行同步的情况下，终端(最新的)待传数据量为零，即终端没有待传的数据或者(最新的)待传数据量为零，则终端可以不触发BSR。
5)在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则终端可以触发BSR；示例性的，在上行失步期间，终端的配置授权(Configured Grant，CG)资源被认为不可用资源，在恢复上行同步后，终端的CG资源被认为可用资源，因此，若终端的CG资源不足以传输所有(最新的)待传输的数据，则终端可以触发BSR。
6)在恢复上行同步的情况下，若上行资源足以传输所有等待传输的数据，则所述终端不触发BSR。
具体地，在恢复上行同步的情况下，若上行资源足以传输所有等待传输的数据，则终端可以不触发BSR；示例性的，在上行失步期间，终端的CG资源被认为不可用资源，在恢复上行同步后，终端的CG资源被认为可用资源，因此若终端的CG资源足以传输所有(最新的)待传的数据，则终端可以不触发BSR。
本申请实施例提供的数据处理方法中，在恢复上行同步的情况下，终端触发BSR；或者若终端的待传数据量不为零，则终端触发BSR；或者若终端的BSR定时器超时或已经超时，则终端触发BSR；或者若终端的待传数据量为零，则终端不触发BSR；或者若上行资源不足以传输所有等待传输的数据，则终端触发BSR；或者若上行资源足以传输所有等待传输的数据，则终端不触发BSR。规范了在恢复上行同步的情况下终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
4、不触发BSR
可选地，在所述终端不触发BSR的情况下，所述方法可以包括以下一项或多项：
a)在恢复上行同步的情况下，若所述终端的待传数据量不为零，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若终端有待传的数据或者等待传输的数据量不为零，则终端可以触发BSR；示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量不为零的情况下，终端可以触发BSR。
可选地，在恢复上行同步的情况下，若终端没有待传的数据或者等待传输的数据量为零，则终端可以不触发BSR；示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量为零的情况下，终端可以不触发BSR。
b)在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若终端的BSR定时器超时或已经超时，则 终端可以触发BSR。具体的应用场景可以是：在上行失步期间，在满足BSR触发条件(诸如BSR重传定时器和/或周期性BSR定时器超时)的情况下，终端执行了触发BSR操作以及取消已经触发的BSR的行为，从而使得在恢复上行同步时并没有处于等待状态的BSR(pending BSR)。在恢复上行同步时，终端可以触发BSR。
c)在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则所述终端触发BSR。
具体地，在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则终端可以触发BSR。在恢复上行同步时，如果终端的待传数据量不为零且终端的上行资源不足以传输(最新的)等待传输的数据量的情况下，终端需要触发BSR。
本申请实施例提供的数据处理方法中，在恢复上行同步的情况下，若终端的待传数据量不为零，则终端触发BSR；或者若终端的BSR定时器超时或已经超时，则终端触发BSR；或者若上行资源不足以传输所有等待传输的数据，则所述终端触发BSR。规范了在恢复上行同步的情况下终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
可选地，所述方法还包括：
所述终端接收网络侧设备发送的配置信息；其中，所述配置信息用于所述终端管理在所述上行失步期间的BSR处理行为。
具体地，终端可以接收网络侧设备发送的配置信息；其中，配置信息用于终端管理在上行失步期间的BSR处理行为。在终端接收到网络侧设备发送的配置信息之后，终端可以基于配置信息，管理在上行失步期间的BSR处理行为。
可选地，所述配置信息包括以下任意一项：
1)第一指示信息；所述第一指示信息用于指示所述终端在所述上行失步期间取消已经触发的触发BSR；
2)第二指示信息；所述第二指示信息用于指示所述终端在所述上行失步期间触发BSR；
3)第三指示信息；所述第三指示信息用于指示所述终端在所述上行失步期间延迟触发BSR；
4)第四指示信息；所述第四指示信息用于指示所述终端在所述上行失步期间不触发BSR。
实际中，在终端接收到网络侧设备发送的配置信息之后，终端可以基于配置信息，管理在上行失步期间的BSR处理行为，例如，终端可以基于第一指示信息，在上行失步期间取消已经触发的触发BSR；终端可以基于第二指示信息，在上行失步期间触发BSR；终端可以基于第三指示信息，在上行失步期间延迟触发BSR；终端可以基于第四指示信息，在上行失步期间不触发BSR。
本申请实施例提供的数据处理方法中，终端通过接收网络侧设备发送的配置信 息；其中，配置信息用于终端管理在上行失步期间的BSR处理行为，实现了终端基于配置信息管理在上行失步期间的BSR处理行为，进而规范了在恢复上行同步的情况下终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
图4是本申请实施例提供的数据处理方法的流程示意图之二，如图4所示，该方法包括步骤401；其中：
步骤401、网络侧设备向终端发送配置信息；
其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。
具体地，当终端维护的有效性定时器超时，定时器对应的星历信息失效，终端不能进行任何上行传输。
实际中，网络侧设备可以向终端发送配置信息，其中，配置信息用于终端管理在上行失步期间的BSR处理行为，使得终端在接收到网络侧设备发送的配置信息之后，终端可以基于配置信息，管理在上行失步期间的BSR处理行为。
可选地，所述配置信息包括以下任意一项：
1)第一指示信息；所述第一指示信息用于指示所述终端在所述上行失步期间取消已经触发的触发BSR；
2)第二指示信息；所述第二指示信息用于指示所述终端在所述上行失步期间触发BSR；
3)第三指示信息；所述第三指示信息用于指示所述终端在所述上行失步期间延迟触发BSR；
4)第四指示信息；所述第四指示信息用于指示所述终端在所述上行失步期间不触发BSR。
实际中，在终端接收到网络侧设备发送的配置信息之后，终端可以基于配置信息，管理在上行失步期间的BSR处理行为，例如，终端可以基于第一指示信息，在上行失步期间取消已经触发的触发BSR；终端可以基于第二指示信息，在上行失步期间触发BSR；终端可以基于第三指示信息，在上行失步期间延迟触发BSR；终端可以基于第四指示信息，在上行失步期间不触发BSR。
本申请实施例提供的数据处理方法中，网络侧设备通过向终端发送配置信息；其中，配置信息用于终端管理在上行失步期间的BSR处理行为，使得终端可以基于配置信息管理在上行失步期间的BSR处理行为，进而规范了在恢复上行同步的情况下终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
接下来通过具体的举例对本申请实施例提供的数据处理方法进行进一步说明。
步骤0，终端维护的有效性定时器(T430)超时，终端的无线资源控制(Radio  Resource Control，RRC)指示终端的MAC层上行失步，则终端的MAC层不执行任何上行传输。
步骤1，在上行失步期间，在上行数据变得可用的情况下，终端可以执行以下任意一项：
1)取消已经触发的BSR；具体地，在上行失步期间，终端可以取消在上行失步之前已经触发的所有BSR，和/或，取消在上行失步期间触发的BSR。
2)在满足BSR触发条件的情况下，触发BSR；具体地，在上行失步期间，在上行数据变得可用的情况下(可理解为在上行数据到达时)，即在上行数据到达时或者BSR定时器超时，其中，BSR定时器包括BSR重传定时器和周期性BSR定时器中的至少一项。由于在上行失步期间，终端没有上行传输资源或者将上行传输资源视为不可用资源，因此，终端按照常规流程触发BSR。
3)在满足BSR触发条件的情况下，延迟触发BSR；具体地，在上行失步期间，在上行数据到达时或BSR定时器超时的情况下，终端不是按照常规流程触发BSR，而是延迟到恢复上行同步后触发BSR。
4)不触发BSR；具体地，在上行失步期间，在上行数据到达时，终端不是按照常规流程触发BSR，而是在上行失步期间始终不触发BSR。
其中，取消已经触发的BSR可以包括以下一项或多项：
1)在获取到上行失步指示时，终端取消在获取到上行失步指示之前已经触发的BSR；具体地，在上行失步期间，终端在获取到上行失步指示之前，由于上行数据到达，终端可以按照常规流程触发BSR；而终端在获取到上行失步指示时，终端可以基于上行失步指示，取消在获取到上行失步指示之前已经触发的所有BSR。
2)终端取消在上行失步期间触发的BSR；具体地，在上行失步期间，由于上行数据到达，终端可以按照常规流程触发BSR，则终端可以取消在上行失步期间触发的所有BSR。相当于，在上行失步期间，在满足BSR的触发条件的情况下，终端仍执行触发BSR的行为。此外，终端除了执行触发BSR的行为之外，终端还执行取消已经触发BSR的行为，从而保证在恢复上行同步时，终端没有处于等待状态的BSR(pending BSR)，进而避免在恢复上行同步时终端始终需要执行BSR MAC CE上报过程。
3)取消BSR触发的调取请求SR；具体地，在上行同步期间，终端可以触发BSR，BSR可以触发SR，则终端可以取消BSR触发的SR。相当于，在上行失步期间，在满足BSR的触发条件的情况下，终端仍执行触发BSR的行为。由于在上行失步期间终端不能执行任何传输，则终端可认为无可用传输资源(如PUSCH)，因此终端可以基于相关技术的机制触发SR。在此情况下，终端除了执行触发BSR的行为之外，终端还执行取消已经触发SR的行为。从而避免在恢复上行同步时，终端没有处于等待状态的SR(pending SR)，进而避免在恢复上行同步时终端始终需要执行 SR过程。
4)取消由SR发起的随机接入过程；具体地，在上行同步期间，终端可以触发BSR，BSR可以触发SR，SR可以发起随机接入过程RACH，则终端可以取消在上行失步期间所有由SR发起的随机接入过程。在上行失步期间，在满足BSR的触发条件的情况下，终端仍执行触发BSR的行为。由于在上行失步期间终端不能执行任何传输，终端可认为无可用传输资源(如PUSCH)，因此终端可以基于相关技术的机制触发SR。由于在上行失步期间终端不能执行任何传输，终端可认为无可用的SR传输资源(如PUCCH)，因此终端可以基于相关技术的机制发起RACH过程。在此情况下，终端除了执行发起RACH过程的行为之外，终端还执行停止发起的RACH的行为。从而避免在恢复上行同步时，终端没有发起的RACH过程，进而避免在恢复上行同步时终端始终需要执行RACH过程。
5)在恢复上行同步的情况下，若终端的待传数据量不为零，则终端触发BSR；具体地，在恢复上行同步的情况下，若终端有待传的数据或者(最新的)待传数据量不为零，则终端可以触发BSR。示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量不为零的情况下，终端可以触发BSR。
6)在恢复上行同步的情况下，若终端的BSR定时器超时或已经超时，则终端触发BSR；具体地，在恢复上行同步的情况下，若终端的BSR定时器超时或者已经超时，其中，BSR定时器包括BSR重传定时器和周期性BSR定时器中的至少一项，则终端可以触发BSR。具体的应用场景可以是：在上行失步期间，在满足BSR触发条件(诸如BSR重传定时器和/或周期性BSR定时器超时)的情况下，终端执行了触发BSR操作以及取消已经触发的BSR的行为，从而使得在恢复上行同步时并没有处于等待状态的BSR(pending BSR)。在恢复上行同步时，终端可以触发BSR。
其中，在终端在满足BSR触发条件，触发BSR的情况下，可以包括以下一项或多项：
1)在上行失步期间，所述BSR不触发SR；具体地，在上行失步期间，在满足BSR的触发条件的情况下，在上行数据到达时，由于在该期间终端没有上行传输资源或者将上行传输资源视为不可用资源，因此终端可以按照常规流程触发BSR，但BSR可以不触发SR。
2)在上行失步期间，由所述BSR触发的SR不发起随机接入过程；具体地，在上行失步期间，在满足BSR的触发条件的情况下，终端触发了BSR，BSR触发了SR，但由BSR触发的SR可以不发起随机接入过程。
3)在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传的数据量为零，则终端取消在恢复上行同步之前已经触发的BSR；需要说明的是，上述的终端取消在恢复上行同步之前已经触发的BSR包括取消在上行失步之前已经触发的BSR和在上行失步期间触发的BSR。
具体地，在等待恢复上行同步期间，上行数据由于等待时间过久被丢弃(例如由于数据包对应的PDCP discard timer超时导致对应数据包被丢弃)，则在恢复上行同步的情况下，终端(最新的)待传数据量为零，即终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在恢复上行同步之前所有按照常规流程触发的BSR。
4)在恢复上行同步的情况下，若终端没有待传的数据，则终端取消在上行同步期间触发的BSR；具体地，在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在上行同步期间触发的所有BSR。在等待恢复上行同步期间，上行数据到达，而终端触发了BSR，但是该上行数据由于等待时间过久被丢弃(例如由于数据包对应的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)丢弃(discard)定时器(timer)超时导致对应数据包被丢弃)，则在恢复上行同步的情况下，终端(最新的)待传数据量为零，即终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在上行失步期间所有按照常规流程触发的BSR。
5)在恢复上行同步的情况下，若终端没有待传的数据，则终端取消在恢复上行同步之前由BSR触发的SR；需要说明的是，终端取消在恢复上行同步之前已经触发的SR包括取消在上行失步之前已经触发的所有SR和在上行失步期间触发的SR；其中，SR可以是由BSR触发的SR。
具体地，在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，但在恢复上行同步之前，终端触发了BSR，BSR触发了SR，则终端可以取消在恢复上行同步之前由BSR触发的SR。
6)在恢复上行同步的情况下，若终端没有待传的数据，则终端取消在上行同步期间由BSR触发的SR；具体地，在等待恢复上行同步期间，上行数据到达，终端触发了BSR，BSR触发了SR，则在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端可以取消在上行同步期间由BSR触发的SR。
7)在恢复上行同步的情况下，若终端没有待传的数据，则终端停止在恢复上行同步之前由SR发起的随机接入过程；需要说明的是，终端停止在恢复上行同步之前已经触发的RACH包括停止在上行失步之前已经发起的RACH和在上行失步期间发起的RACH。其中，所述的RACH可以是由SR发起，所述SR是由BSR触发的。
具体地，在等待恢复上行同步之前，终端触发了BSR，BSR触发了SR，SR发起随机接入过程，则在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端可以停止在恢复上行同步之前由SR发起的随机接入过程。
8)在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端停止在上行失步期间由SR发起的随机接入过程；
具体地，在上行失步期间，上行数据到达，终端触发了BSR，BSR触发了SR，SR发起随机接入过程，则在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传数据量为零，则终端停止在上行失步期间由SR发起的随机接入过程。
9)在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则所述终端取消在上行同步期间由SR发起的随机接入过程；示例性的，在上行失步期间，在满足BSR触发条件的情况下(如在上行数据到达时)，由于无可用的上行传输资源(即PUSCH资源)，则终端触发了BSR，BSR触发了SR。由于在上行失步期间，SR传输资源(即PUCCH资源)也被认为是不可用资源，因此，终端可以发起随机接入过程。在恢复上行同步后，若终端无上行资源或者上行资源不足以传输所有待传数据(可理解为待传数据量不为零的情况下)或BSR MAC CE，但是终端有可用的有效SR传输资源，则终端可以取消在上行同步期间由SR发起的随机接入过程。额外的，在该情况下，终端可以触发SR。
10)在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则所述终端触发SR；具体地，在恢复上行同步的情况下，若终端无上行资源或者上行资源不足以传输所有待传数据或BSR MAC CE，但是终端有可用的有效SR传输资源，则终端可以触发SR。示例性的，在上行失步期间，在满足BSR触发条件的情况下(如在上行数据到达时)，由于无可用的上行传输资源(即PUSCH资源)，则终端触发了BSR，但BSR没有触发SR。在恢复上行同步的情况下，若终端无上行资源或者上行资源不足以传输所有待传数据(可理解为待传数据量不为零的情况下)或BSR MAC CE，但是终端有可用的有效SR传输资源，此时终端可以触发SR。
其中，在终端在满足BSR触发条件，执行延迟触发BSR的情况下，所述方法可以包括以下一项或多项：
a)在恢复上行同步的情况下，终端触发BSR；示例性的，在恢复上行同步时，终端触发BSR。即在上行失步期间，在上行数据到达时，终端没有触发BSR，而是在恢复上行同步时触发BSR。示例性的应用场景是：在上行失步期间，在满足BSR触发条件的情况下，终端延迟触发BSR。在恢复上行同步的情况下，终端触发BSR。相当于，在恢复上行同步的情况下，无论是否有等待传输的数据，终端都会触发BSR。另外需要说明的是，在该种情况下，如果触发的是常规BSR，那么在没有待传数据的情况下，终端可以执行上行跳过(UL skipping)过程。也就是说，终端在执行MAC复用过程时，如果常规BSR指示的待传数据量为零，则终端可以不在上行授权资源上传输BSR MAC CE。
b)在恢复上行同步的情况下，若终端有待传的数据或者等待传输的数据量不为零，则终端触发BSR；示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量不为零的情况下，终端触发BSR。另外需要说明的是，在恢复上行同步时，如果终端的上行资源足以传输(最新的)等待传输的数据量， 终端是无需触发BSR的。而在恢复上行同步时，如果终端的待传数据量不为零且终端的上行资源不足以传输(最新的)等待传输的数据量的情况下，终端触发BSR。
c)在恢复上行同步的情况下，若终端的BSR定时器超时或已经超时，则终端触发BSR；具体地，在恢复上行同步的情况下，若终端的BSR定时器超时或已经超时，则终端可以触发BSR。具体的应用场景可以是：在上行失步期间，在满足BSR触发条件(诸如BSR重传定时器和/或周期性BSR定时器超时)的情况下，终端执行了触发BSR操作以及取消已经触发的BSR的行为，从而使得在恢复上行同步时并没有处于等待状态的BSR(pending BSR)。在恢复上行同步时，终端可以触发BSR。
d)在恢复上行同步的情况下，若终端没有待传的数据或者等待传输的数据量为零，则终端不触发BSR；具体地，在恢复上行同步的情况下，若终端没有待传的数据或者(最新的)待传输的数据量为零，则终端可以不触发BSR。示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量为零的情况下，终端不触发BSR。
e)在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则终端触发BSR；示例性的，在上行失步期间，终端的CG资源被认为不可用资源，在恢复上行同步后，终端的CG资源被认为可用资源，因此若CG资源不足以传输所有(最新的)待传的数据量，则终端触发BSR。
f)在恢复上行同步的情况下，若上行资源足以传输所有等待传输的数据，则终端不触发BSR；示例性的，在上行失步期间，终端的CG资源被认为不可用资源，在恢复上行同步后，终端的CG资源被认为可用资源，因此若CG资源足以传输所有(最新的)待传的数据量，则终端不触发BSR。
其中，在终端不触发BSR的情况下，还可以包括以下一项或多项：
1)在恢复上行同步的情况下，若终端有待传的数据或者等待传输的数据量不为零，则终端触发BSR；示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量不为零的情况下，终端触发BSR。
2)在恢复上行同步的情况下，若终端有待传的数据或者等待传输的数据量为零，则终端不触发BSR；示例性的，在恢复上行同步时，终端需要先判断等待传输的数据量是否为零，在数据量为零的情况下，终端不触发BSR。
步骤2，终端接收网络侧的配置信息，所述配置信息用于管理在上行失步期间终端的BSR处理行为。
其中，配置信息包括以下一项或多项：
1)第一指示信息，第一指示信息用于指示终端在上行失步期间按照常规流程触发BSR；
2)第二指示信息，第二指示信息用于指示终端在上行失步期间需延迟触发BSR；
3)第三指示信息，第三指示信息用于指示终端在上行失步期间不触发BSR。
本申请实施例提供的数据处理方法，执行主体可以为数据处理装置。本申请实施例中以数据处理装置执行数据处理方法为例，说明本申请实施例提供的数据处理装置。
图5是本申请实施例提供的数据处理装置的结构示意图之一，如图5所示，该数据处理装置500，应用于终端(例如，可以数据处理装置500可以包括终端的至少部分模块或功能，或者，终端包括数据处理装置500)，包括：
执行模块501，用于在上行失步期间，执行以下任意一项：
取消已经触发的缓存状态报告BSR；
在满足BSR触发条件的情况下，触发BSR；
在满足BSR触发条件的情况下，延迟触发BSR；
不触发BSR。
本申请实施例提供的数据处理装置中，在上行失步期间，通过执行以下任意一项：取消已经触发的缓存状态报告BSR；在满足BSR触发条件的情况下，触发BSR；在满足BSR触发条件的情况下，延迟触发BSR；不触发BSR，规范了在上行失步期间，通过前述对BSR的处理行为，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
可选地，所述取消已经触发的BSR包括以下一项或多项：
在获取到上行失步指示时，所述终端取消在获取到所述上行失步指示之前已经触发的BSR；
所述终端取消在所述上行失步期间触发的BSR。
可选地，所述终端取消在所述上行失步期间触发的BSR，可以是在上行失步期间且所述终端无等待传输的数据(例如，等待传输的数据量为0)的情况下，所述终端取消在所述上行失步期间触发的BSR。
在另一种可选的实施方式中，终端可以在上行失步期间且所述终端无等待传输的数据(例如，等待传输的数据量为0)的情况下，所述终端取消已触发的BSR。需要说明的是，该已触发的BSR，可以是在上行失步期间触发的，也可以是在其他时间触发的(例如，可以是在上行失步期间之前的任意时间触发的)。
可选地，所述取消已经触发的BSR还包括以下一项或多项：
取消BSR触发的调取请求SR；
取消由SR发起的随机接入过程。
可选地，在所述执行模块501执行取消已经触发的BSR的情况下，所述数据处理装置500还用于以下一项或多项：
在恢复上行同步的情况下，若所述终端的待传数据量不为零，则触发BSR；
在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则触发 BSR。
可选地，在所述终端在满足BSR触发条件，触发BSR的情况下，所述数据处理装置500用于执行以下一项或多项：
在上行失步期间，所述BSR不触发SR；
在上行失步期间，由所述BSR触发的SR不发起随机接入过程。
可选地，所述数据处理装置500包括以下一项或多项：
在恢复上行同步的情况下，若所述终端没有待传的数据，则取消在恢复上行同步之前已经触发的BSR；
在恢复上行同步的情况下，若所述终端没有待传的数据，则取消在上行同步期间触发的BSR；
在恢复上行同步的情况下，若所述终端没有待传的数据，则取消在恢复上行同步之前由BSR触发的SR；
在恢复上行同步的情况下，若所述终端没有待传的数据，则取消在上行同步期间由BSR触发的SR；
在恢复上行同步的情况下，若所述终端没有待传的数据，则停止在恢复上行同步之前由SR发起的随机接入过程；
在恢复上行同步的情况下，若所述终端没有待传的数据，则停止在上行失步期间由SR发起的随机接入过程；
在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则取消在上行同步期间由SR发起的随机接入过程；
在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则触发SR。
可选地，在所述终端在满足BSR触发条件，执行延迟触发BSR的情况下，所述数据处理装置500用于执行以下一项或多项：
在恢复上行同步的情况下，触发BSR；
在恢复上行同步的情况下，若所述终端的待传数据量不为零，则触发BSR；
在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则触发BSR；
在恢复上行同步的情况下，若所述终端的待传数据量为零，则不触发BSR；
在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则触发BSR；
在恢复上行同步的情况下，若上行资源足以传输所有等待传输的数据，则不触发BSR。
可选地，在所述终端不触发BSR的情况下，所述数据处理装置500用于执行以下一项或多项：
在恢复上行同步的情况下，若所述终端的待传数据量不为零，则触发BSR；
在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则触发BSR；
在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则触发BSR。
可选地，所述BSR触发条件包括以下一项或多项：
上行数据到达；
BSR定时器超时；其中，所述BSR定时器包括BSR重传定时器和周期性BSR定时器中的至少一项。
可选地，所述数据处理装置500还包括：
接收模块，用于接收网络侧设备发送的配置信息；其中，所述配置信息用于所述终端管理在所述上行失步期间的BSR处理行为。
可选地，所述配置信息包括以下任意一项：
第一指示信息；所述第一指示信息用于指示所述终端在所述上行失步期间取消已经触发的触发BSR；
第二指示信息；所述第二指示信息用于指示所述终端在所述上行失步期间触发BSR；
第三指示信息；所述第三指示信息用于指示所述终端在所述上行失步期间延迟触发BSR；
第四指示信息；所述第四指示信息用于指示所述终端在所述上行失步期间不触发BSR。
图6是本申请实施例提供的数据处理装置的结构示意图之二，如图6所示，该数据处理装置600，应用于网络侧设备，包括：
发送模块601，用于向终端发送配置信息；
其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。
本申请实施例提供的数据处理装置中，通过向终端发送配置信息；其中，配置信息用于终端管理在上行失步期间的BSR处理行为，使得终端可以基于配置信息管理在上行失步期间的BSR处理行为，进而规范了在恢复上行同步的情况下终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
可选地，所述配置信息包括以下至少一项：
第一指示信息；所述第一指示信息用于指示所述终端在所述上行失步期间取消已经触发的BSR；
第二指示信息；所述第二指示信息用于指示所述终端在所述上行失步期间触发BSR；
第三指示信息；所述第三指示信息用于指示所述终端在所述上行失步期间延迟触发BSR；
第四指示信息；所述第四指示信息用于指示所述终端在所述上行失步期间不触发BSR。
本申请实施例中的数据处理装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的数据处理装置能够实现图3或图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图7是本申请实施例提供的通信设备的结构示意图，如图7所示，该通信设备700，包括处理器701和存储器702，存储器702上存储有可在所述处理器701上运行的程序或指令，例如，该通信设备700为终端时，该程序或指令被处理器701执行时实现上述数据处理方法实施例的各个步骤，且能达到相同的技术效果。该通信设备700为网络侧设备时，该程序或指令被处理器701执行时实现上述数据处理方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，其中，所述处理器用于在上行失步期间，执行以下任意一项：
取消已经触发的缓存状态报告BSR；
在满足BSR触发条件的情况下，触发BSR；
在满足BSR触发条件的情况下，延迟触发BSR；
不触发BSR。
该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。
图8是本申请实施例提供的终端的结构示意图，如图8所示，该终端800包括但不限于：射频单元801、网络模块802、音频输出单元803、输入单元804、传感器805、显示单元806、用户输入单元807、接口单元808、存储器809以及处理器810等中的至少部分部件。
本领域技术人员可以理解，终端800还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器810逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图8中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元804可以包括图形处理单元(Graphics  Processing Unit，GPU)8041和麦克风8042，图形处理器8041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元806可包括显示面板8061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板8061。用户输入单元807包括触控面板8071以及其他输入设备8072中的至少一种。触控面板8071，也称为触摸屏。触控面板8071可包括触摸检测装置和触摸控制器两个部分。其他输入设备8072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元801接收来自网络侧设备的下行数据后，可以传输给处理器810进行处理；另外，射频单元801可以向网络侧设备发送上行数据。通常，射频单元801包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器809可用于存储软件程序或指令以及各种数据。存储器809可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器809可以包括易失性存储器或非易失性存储器，或者，存储器809可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器809包括但不限于这些和任意其它适合类型的存储器。
处理器810可包括一个或多个处理单元；可选的，处理器810集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器810中。
其中，处理器810，用于在上行失步期间，执行以下任意一项：
取消已经触发的缓存状态报告BSR；
在满足BSR触发条件的情况下，触发BSR；
在满足BSR触发条件的情况下，延迟触发BSR；
不触发BSR。
基于本申请实施例提供的终端，在获取到上行失步指示时，可以取消在获取到上行失步指示之前已经触发的BSR；终端可以取消在上行失步期间触发的BSR；终端可以取消BSR触发的调取请求SR；终端可以取消由SR发起的随机接入过程；在恢复上行同步的情况下，若终端的待传数据量不为零，则终端触发BSR；在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则终端触发BSR，规范了在上行失步期间以及恢复上行同步后终端对BSR的处理，进而避免在恢复上行同步后终端发起不必要的上行资源申请过程，提高资源利用率。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，其中，所述通信接口用于向终端发送配置信息；其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
图9是本申请实施例提供的网络侧设备的结构示意图，如图9所示，该网络侧设备900包括：天线901、射频装置902、基带装置903、处理器904和存储器905。天线901与射频装置902连接。在上行方向上，射频装置902通过天线901接收信息，将接收的信息发送给基带装置903进行处理。在下行方向上，基带装置903对要发送的信息进行处理，并发送给射频装置902，射频装置902对收到的信息进行处理后经过天线901发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置903中实现，该基带装置903包括基带处理器。
基带装置903例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图9所示，其中一个芯片例如为基带处理器，通过总线接口与存储器905连接，以调用存储器905中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口906，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备900还包括：存储在存储器905上并可在处理器904上运行的指令或程序，处理器904调用存储器905中的指令或程序执行如上所述图4所示方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供了一种数据处理系统，包括：终端及网络侧设备，所述终端可用于执行如上所述的终端侧的数据处理方法的步骤，所述网络侧设备可用于执行如上所述的网络侧设备侧的数据处理方法的步骤。
本申请实施例还提供一种可读存储介质，所述可读存储介质可以是以易失性的，也可以是非易失性的，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述数据处理方法实施例的各个过程，且能达到相同的技术效果， 为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，可以是非易失性的，可以是非瞬态的。可读存储介质，可以包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述数据处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述数据处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (22)

  1. 一种数据处理方法，其中，包括：
    在上行失步期间，终端执行以下任意一项：
    取消已经触发的缓存状态报告BSR；
    在满足BSR触发条件的情况下，触发BSR；
    在满足BSR触发条件的情况下，延迟触发BSR；
    不触发BSR。
  2. 根据权利要求1所述的数据处理方法，其中，所述取消已经触发的BSR包括以下一项或多项：
    在获取到上行失步指示时，所述终端取消在获取到所述上行失步指示之前已经触发的BSR；
    所述终端取消在所述上行失步期间触发的BSR。
  3. 根据权利要求1或2所述的数据处理方法，其中，所述取消已经触发的BSR还包括以下一项或多项：
    取消BSR触发的调取请求SR；
    取消由SR发起的随机接入过程。
  4. 根据权利要求2所述的数据处理方法，其中，在所述终端取消已经触发的BSR的情况下，所述方法包括以下一项或多项：
    在恢复上行同步的情况下，若所述终端的待传数据量不为零，则所述终端触发BSR；
    在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则所述终端触发BSR。
  5. 根据权利要求1所述的数据处理方法，其中，在所述终端在满足BSR触发条件，触发BSR的情况下，所述方法包括以下一项或多项：
    在上行失步期间，所述BSR不触发SR；
    在上行失步期间，由所述BSR触发的SR不发起随机接入过程。
  6. 根据权利要求1或5所述的数据处理方法，其中，所述方法包括以下一项或多项：
    在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在恢复上行同步之前已经触发的BSR；
    在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在上行同步期间触发的BSR；
    在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在恢复上行同步之前由BSR触发的SR；
    在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端取消在上 行同步期间由BSR触发的SR；
    在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端停止在恢复上行同步之前由SR发起的随机接入过程；
    在恢复上行同步的情况下，若所述终端没有待传的数据，则所述终端停止在上行失步期间由SR发起的随机接入过程；
    在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则所述终端取消在上行同步期间由SR发起的随机接入过程；
    在恢复上行同步的情况下，若所述终端有有效的SR传输资源，则所述终端触发SR。
  7. 根据权利要求1所述的数据处理方法，其中，在所述终端在满足BSR触发条件，执行延迟触发BSR的情况下，所述方法包括以下一项或多项：
    在恢复上行同步的情况下，所述终端触发BSR；
    在恢复上行同步的情况下，若所述终端的待传数据量不为零，则所述终端触发BSR；
    在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则所述终端触发BSR；
    在恢复上行同步的情况下，若所述终端的待传数据量为零，则所述终端不触发BSR；
    在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则所述终端触发BSR；
    在恢复上行同步的情况下，若上行资源足以传输所有等待传输的数据，则所述终端不触发BSR。
  8. 根据权利要求1所述的数据处理方法，其中，在所述终端不触发BSR的情况下，所述方法包括以下一项或多项：
    在恢复上行同步的情况下，若所述终端的待传数据量不为零，则所述终端触发BSR；
    在恢复上行同步的情况下，若所述终端的BSR定时器超时或已经超时，则所述终端触发BSR；
    在恢复上行同步的情况下，若上行资源不足以传输所有等待传输的数据，则所述终端触发BSR。
  9. 根据权利要求1所述的数据处理方法，其中，所述BSR触发条件包括以下一项或多项：
    上行数据到达；
    BSR定时器超时；其中，所述BSR定时器包括BSR重传定时器和周期性BSR定时器中的至少一项。
  10. 根据权利要求1至9任一项所述的数据处理方法，其中，所述方法还包括：
    所述终端接收网络侧设备发送的配置信息；其中，所述配置信息用于所述终端管理在所述上行失步期间的BSR处理行为。
  11. 根据权利要求10所述的数据处理方法，其中，所述配置信息包括以下任意一项：
    第一指示信息；所述第一指示信息用于指示所述终端在所述上行失步期间取消已经触发的触发BSR；
    第二指示信息；所述第二指示信息用于指示所述终端在所述上行失步期间触发BSR；
    第三指示信息；所述第三指示信息用于指示所述终端在所述上行失步期间延迟触发BSR；
    第四指示信息；所述第四指示信息用于指示所述终端在所述上行失步期间不触发BSR。
  12. 根据权利要求2所述的数据处理方法，其中，所述终端取消在所述上行失步期间触发的BSR，包括：
    在所述上行失步期间且所述终端无等待传输的数据的情况下，所述终端取消在所述上行失步期间触发的BSR。
  13. 一种数据处理方法，其中，包括：
    网络侧设备向终端发送配置信息；
    其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。
  14. 根据权利要求13所述的数据处理方法，其中，所述配置信息包括以下至少一项：
    第一指示信息；所述第一指示信息用于指示所述终端在所述上行失步期间取消已经触发的BSR；
    第二指示信息；所述第二指示信息用于指示所述终端在所述上行失步期间触发BSR；
    第三指示信息；所述第三指示信息用于指示所述终端在所述上行失步期间延迟触发BSR；
    第四指示信息；所述第四指示信息用于指示所述终端在所述上行失步期间不触发BSR。
  15. 一种数据处理装置，其中，包括：
    执行模块，用于在上行失步期间，执行以下任意一项：
    取消已经触发的缓存状态报告BSR；
    在满足BSR触发条件的情况下，触发BSR；
    在满足BSR触发条件的情况下，延迟触发BSR；
    不触发BSR。
  16. 一种数据处理装置，其中，包括：
    发送模块，用于向终端发送配置信息；
    其中，所述配置信息用于所述终端管理在上行失步期间的缓存状态报告BSR处理行为。
  17. 一种终端，其中，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至12任一项所述的数据处理方法的步骤。
  18. 一种网络侧设备，其中，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求13或14所述的数据处理方法的步骤。
  19. 一种可读存储介质，其中，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至12任一项所述的数据处理方法，或者实现如权利要求13或14所述的数据处理方法的步骤。
  20. 一种芯片，其中，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至12任一项所述的数据处理方法，或者实现如权利要求13或14所述的数据处理方法的步骤。
  21. 一种计算机程序产品，其中，所述程序产品被存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现如权利要求1至12任一项所述的数据处理方法，或者实现如权利要求13或14所述的数据处理方法的步骤。
  22. 一种电子设备，其中，所述电子设备被配置成用于执行如权利要求1至12任一项所述的数据处理方法，或者如权利要求13或14所述的数据处理方法的步骤。
PCT/CN2023/111236 2022-08-10 2023-08-04 数据处理方法、终端及网络侧设备 WO2024032503A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210957929 2022-08-10
CN202210957929.8 2022-08-10
CN202210987783.1 2022-08-17
CN202210987783.1A CN117676856A (zh) 2022-08-10 2022-08-17 数据处理方法、终端及网络侧设备

Publications (1)

Publication Number Publication Date
WO2024032503A1 true WO2024032503A1 (zh) 2024-02-15

Family

ID=89850823

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/111236 WO2024032503A1 (zh) 2022-08-10 2023-08-04 数据处理方法、终端及网络侧设备

Country Status (1)

Country Link
WO (1) WO2024032503A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108271270A (zh) * 2017-01-04 2018-07-10 电信科学技术研究院 一种sr/bsr触发方法和装置
WO2018141267A1 (zh) * 2017-02-04 2018-08-09 华为技术有限公司 一种缓存状态报告的触发方法、装置及系统
WO2020164599A1 (zh) * 2019-02-15 2020-08-20 华为技术有限公司 一种缓存状态报告bsr的触发方法、通信装置
WO2021031089A1 (zh) * 2019-08-19 2021-02-25 Oppo广东移动通信有限公司 资源配置的方法、终端设备和网络设备
CN113455052A (zh) * 2021-05-12 2021-09-28 北京小米移动软件有限公司 随机接入方法和装置、通信装置和计算机可读存储介质
WO2022116099A1 (zh) * 2020-12-03 2022-06-09 Oppo广东移动通信有限公司 随机接入的触发控制方法、装置、设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108271270A (zh) * 2017-01-04 2018-07-10 电信科学技术研究院 一种sr/bsr触发方法和装置
WO2018141267A1 (zh) * 2017-02-04 2018-08-09 华为技术有限公司 一种缓存状态报告的触发方法、装置及系统
WO2020164599A1 (zh) * 2019-02-15 2020-08-20 华为技术有限公司 一种缓存状态报告bsr的触发方法、通信装置
WO2021031089A1 (zh) * 2019-08-19 2021-02-25 Oppo广东移动通信有限公司 资源配置的方法、终端设备和网络设备
WO2022116099A1 (zh) * 2020-12-03 2022-06-09 Oppo广东移动通信有限公司 随机接入的触发控制方法、装置、设备及存储介质
CN113455052A (zh) * 2021-05-12 2021-09-28 北京小米移动软件有限公司 随机接入方法和装置、通信装置和计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NORTEL: "Additional triggers to facilitate practical Buffer Status reporting", 3GPP DRAFT; R2-080339-ADDITIONAL BSR TRIGGERS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sevilla, Spain; 20080107, 7 January 2008 (2008-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050138196 *

Similar Documents

Publication Publication Date Title
US20240040430A1 (en) Transmission Processing Method and Communications Device
US20240023189A1 (en) Communication Path Switching Method and Terminal
WO2024032503A1 (zh) 数据处理方法、终端及网络侧设备
CN117676856A (zh) 数据处理方法、终端及网络侧设备
WO2023093636A1 (zh) 信息上报方法、配置方法、装置、终端及网络侧设备
WO2024022353A1 (zh) 连接建立方法、终端及源网络侧设备
WO2023217007A1 (zh) 切换方法、终端及网络侧设备
WO2023179599A1 (zh) 多路径建立方法、终端及网络侧设备
WO2024007961A1 (zh) 中继控制方法、装置、终端及网络侧设备
WO2023274291A1 (zh) 传输方法、装置、设备及介质
WO2023185819A1 (zh) Pdcch监听方法、终端、网络侧设备及介质
WO2022199482A1 (zh) 上行传输的控制方法、装置及终端
WO2024027748A1 (zh) 数据传输方法及装置、终端
WO2024012302A1 (zh) 旁链路反馈处理方法、装置、终端及网络侧设备
WO2023185841A1 (zh) 中继终端的选择方法、装置、终端及存储介质
WO2023169464A1 (zh) 上行传输的方法、终端及网络侧设备
WO2024007953A1 (zh) 处理方法、设备及可读存储介质
US20240137857A1 (en) Relay selection method and apparatus, relay information transmission method and apparatus, and terminal
WO2024022439A1 (zh) 处理方法、设备及可读存储介质
WO2023202513A1 (zh) 冲突处理方法、终端及网络侧设备
WO2024094014A1 (zh) Bsr汇报方法、装置、终端及网络侧设备
WO2023116903A1 (zh) Sl信号处理方法、设备及可读存储介质
WO2023221883A1 (zh) 辅小区SCell激活方法及设备
WO2024027677A1 (zh) 处理方法、装置、终端、网络侧设备及可读存储介质
WO2023045851A1 (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: 23851724

Country of ref document: EP

Kind code of ref document: A1