WO2023236213A1 - 通信方法、终端设备及网络设备 - Google Patents

通信方法、终端设备及网络设备 Download PDF

Info

Publication number
WO2023236213A1
WO2023236213A1 PCT/CN2022/098251 CN2022098251W WO2023236213A1 WO 2023236213 A1 WO2023236213 A1 WO 2023236213A1 CN 2022098251 W CN2022098251 W CN 2022098251W WO 2023236213 A1 WO2023236213 A1 WO 2023236213A1
Authority
WO
WIPO (PCT)
Prior art keywords
trp
terminal device
serving cell
network device
uplink
Prior art date
Application number
PCT/CN2022/098251
Other languages
English (en)
French (fr)
Inventor
尤心
林雪
曹建飞
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/098251 priority Critical patent/WO2023236213A1/zh
Publication of WO2023236213A1 publication Critical patent/WO2023236213A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • the present application relates to the field of communication technology, and more specifically, to a communication method, terminal equipment and network equipment.
  • Timing advance is configured at the granularity of the serving cell.
  • TRP transmitting and receiving point
  • This application provides a communication method, terminal equipment and network equipment. Each aspect involved in this application is introduced below.
  • a communication method including: when the timing advance TA of the first transmission point TRP is invalid, the terminal device performs one or more of the following operations: the TA based on the second TRP communicates with the Second TRP communication; restore the TA of the first TRP to be valid, wherein the TA of the second TRP is valid, and the first TRP and the second TRP belong to a serving cell of the terminal device.
  • a second aspect provides a communication method, including: when the timing advance TA of the first transmission point TRP is invalid, the network device performs one or more of the following operations: communicating with the terminal device based on the TA of the second TRP ; Restore the TA of the first TRP to be valid, wherein the TA of the second TRP is valid, and the first TRP and the second TRP belong to a serving cell of the terminal device.
  • a terminal device including: when the timing advance TA of the first transmission point TRP is invalid, a processing unit performs one or more of the following operations: TA based on the second TRP and the Second TRP communication; restore the TA of the first TRP to be valid, wherein the TA of the second TRP is valid, and the first TRP and the second TRP belong to a serving cell of the terminal device .
  • the fourth aspect provides a network device, including: when the timing advance TA of the first transmission point TRP is invalid, a processing unit performs one or more of the following operations: TA and terminal equipment based on the second TRP Communication; restoring the TA of the first TRP to be valid, wherein the TA of the second TRP is valid, and the first TRP and the second TRP belong to a serving cell of the terminal device.
  • a terminal including a processor, a memory, and a communication interface.
  • the memory is used to store one or more computer programs.
  • the processor is used to call the computer program in the memory, so that the terminal device Perform some or all of the steps of the method of the first aspect.
  • a sixth aspect provides a network device, including a processor, a memory, and a communication interface.
  • the memory is used to store one or more computer programs.
  • the processor is used to call the computer program in the memory so that the network The device performs some or all of the steps of the method of the second aspect.
  • embodiments of the present application provide a communication system, which includes the above-mentioned terminal and/or network device.
  • the system may also include other devices that interact with the terminal or network device in the solution provided by the embodiments of this application.
  • embodiments of the present application provide a computer-readable storage medium that stores a computer program, and the computer program causes a terminal to perform some or all of the steps in the methods of the above aspects.
  • embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause the terminal to execute each of the above. Some or all of the steps in a method.
  • the computer program product can be a software installation package.
  • embodiments of the present application provide a chip, which includes a memory and a processor.
  • the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.
  • TA is configured with TRP as the granularity.
  • the terminal device can communicate with the second TRP based on the TA of the second TRP in the serving cell; and/or restore the The TA of the first TRP is valid to ensure that communication between the terminal device and the serving cell can continue.
  • 1A to 1C are system architecture diagrams of a communication system to which embodiments of the present application can be applied.
  • Figure 2 shows the format of the MAC CE carrying TAC.
  • Figure 3 shows the format of the MAC CE carrying TAC.
  • Figure 4 shows the format of a MAC RAR carrying TAC.
  • Figure 5 is a schematic diagram of a multi-TRP scenario applicable to the embodiment of the present application.
  • Figure 6 is a flow chart of the communication method according to the embodiment of the present application.
  • Figure 7 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • Figure 8 is a schematic diagram of a network device according to an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of the device according to the embodiment of the present application.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE-A advanced long term evolution
  • NR new radio
  • evolution system of NR system LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to on unlicensed spectrum) unlicensed spectrum (NR-U) system, NTN system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), wireless fidelity (wireless fidelity, WiFi), fifth-generation communications (5th-generation, 5G) system or other communication systems, such as future communication systems, such as the sixth generation mobile communication system, and satellite communication systems.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE-A advanced long term evolution
  • new radio new radio
  • NR evolution system of
  • D2D device to device
  • M2M machine to machine
  • MTC machine type Communication
  • V2V vehicle to vehicle
  • V2X vehicle to everything
  • CA carrier aggregation
  • DC dual connectivity
  • SA standalone
  • the communication system in the embodiment of the present application can be applied to the unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or the communication system in the embodiment of the present application can also be applied to the licensed spectrum, where the licensed spectrum can also be Considered dedicated spectrum.
  • NTN systems can be applied to NTN systems and also to terrestrial communication networks (terrestrial networks, TN) systems.
  • TN systems include NR-based NTN systems and IoT-based NTN systems.
  • the embodiments of this application describe various embodiments in combination with network equipment and terminal equipment.
  • the terminal equipment may also be called user equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station (mobile station). station, MS), mobile terminal (mobile Terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.
  • the terminal device may be a station (STATION, ST) in WLAN, a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, or a wireless local loop (wireless local loop).
  • WLL station
  • PDA personal digital assistant
  • handheld device with wireless communication capabilities computing device or other processing device connected to a wireless modem
  • vehicle-mounted device wearable device
  • next-generation communication system such as NR network terminal equipment in the public land mobile network (public land mobile network, PLMN) network that will evolve in the future.
  • PLMN public land mobile network
  • a terminal device may refer to a device that provides voice and/or data connectivity to users, and may be used to connect people, things, and machines, such as handheld devices, vehicle-mounted devices, etc. with wireless connection functions.
  • the terminal device in the embodiment of the present application can be a mobile phone (mobile phone), a tablet computer (Pad), a notebook computer, a handheld computer, a mobile internet device (mobile internet device, MID), a wearable device, a virtual reality (virtual reality, VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, smart Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc.
  • VR virtual reality
  • AR augmented reality
  • the terminal device can be used to act as a base station.
  • terminal devices may act as a scheduling entity that provides sidelink signals between terminal devices in V2X or D2D, etc.
  • terminal devices may act as a scheduling entity that provides sidelink signals between terminal devices in V2X or D2D, etc.
  • terminal devices may act as a scheduling entity that provides sidelink signals between terminal devices in V2X or D2D, etc.
  • cell phones and cars use sidelink signals to communicate with each other.
  • Cell phones and smart home devices communicate between each other without having to relay communication signals through base stations.
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites). superior).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, or an augmented reality (AR) terminal.
  • Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.
  • the terminal equipment involved in the embodiments of this application may also be called terminal, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station , remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE agent or UE device, etc.
  • Terminal equipment can also be fixed or mobile.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the network device in the embodiment of the present application may be a device used to communicate with a terminal device.
  • the network device may also be called an access network device or a wireless access network device.
  • the network device may be a base station.
  • the network device in the embodiment of this application may refer to a radio access network (radio access network, RAN) node (or device) that connects the terminal device to the wireless network.
  • radio access network radio access network, RAN node (or device) that connects the terminal device to the wireless network.
  • the base station can broadly cover various names as follows, or be replaced with the following names, such as: Node B (NodeB), evolved base station (evolved NodeB, eNB), next generation base station (next generation NodeB, gNB), relay station, Access point, transmission point (transmitting and receiving point, TRP), transmitting point (TP), main station MeNB, secondary station SeNB, multi-standard wireless (MSR) node, home base station, network controller, access node , wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (active antenna unit) , AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning node, etc.
  • NodeB Node B
  • eNB evolved base station
  • next generation NodeB next generation NodeB, gNB
  • relay station Access point
  • transmission point transmission point
  • the base station may be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.
  • a base station may also refer to a communication module, modem or chip used in the aforementioned equipment or devices.
  • the base station can also be a mobile switching center and a device that undertakes base station functions in device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communications, and in 6G networks.
  • Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • Base stations can be fixed or mobile.
  • a helicopter or drone may be configured to act as a mobile base station, and one or more cells may move based on the mobile base station's location.
  • a helicopter or drone may be configured to serve as a device that communicates with another base station.
  • the network device in the embodiment of this application may refer to a CU or a DU, or the network device includes a CU and a DU.
  • gNB can also include AAU.
  • Network equipment and terminal equipment can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky. In the embodiments of this application, the scenarios in which network devices and terminal devices are located are not limited.
  • the network device may have mobile characteristics, for example, the network device may be a mobile device.
  • network equipment may be satellites or balloon stations.
  • the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite ) satellite, etc.
  • the network device may also be a base station installed on land, water, or other locations.
  • network equipment can provide services for a cell, and terminal equipment communicates with the network equipment through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell.
  • the cell can be a network equipment ( For example, a cell corresponding to a base station).
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: urban cell (metro cell), micro cell (micro cell), pico cell ( Pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission services.
  • FIG. 1A is a schematic architectural diagram of a communication system provided by an embodiment of the present application.
  • the communication system 100 may include a network device 110 , and the network device 110 may be a device that communicates with a terminal device 120 (also known as a communication terminal or terminal).
  • the network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within the coverage area.
  • Figure 1A exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and other numbers of terminals may be included within the coverage of each network device.
  • Equipment the embodiments of this application do not limit this.
  • FIG. 1B is an architectural schematic diagram of another communication system provided by an embodiment of the present application.
  • a terminal device 1101 and a satellite 1102. Wireless communication can be performed between the terminal device 1101 and the satellite 1102.
  • the network formed between the terminal device 1101 and the satellite 1102 may also be called NTN.
  • the satellite 1102 may have the function of a base station, and the terminal device 1101 and the satellite 1102 may communicate directly.
  • the satellite 1102 can be called a network device.
  • the communication system may include multiple network devices 1102, and the coverage of each network device 1102 may include other numbers of terminal devices, which is not limited in the embodiments of the present application.
  • FIG. 1C is an architectural schematic diagram of another communication system provided by an embodiment of the present application.
  • Figure 1C which includes a terminal device 1201, a satellite 1202 and a base station 1203.
  • Wireless communication can be performed between the terminal device 1201 and the satellite 1202, and communication can be performed between the satellite 1202 and the base station 1203.
  • the network formed between the terminal device 1201, the satellite 1202 and the base station 1203 may also be called NTN.
  • the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be relayed through the satellite 1202 .
  • the base station 1203 can be called a network device.
  • the communication system may include multiple network devices 1203, and the coverage of each network device 1203 may include other numbers of terminal devices, which is not limited in the embodiments of the present application.
  • Figures 1A to 1C are only used as examples to illustrate the systems to which this application is applicable.
  • the methods shown in the embodiments of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc. , the embodiments of this application do not specifically limit this.
  • the wireless communication system shown in Figures 1A-1C may also include a mobility management entity (mobility management entity, MME), access and mobility management function (AMF) and other network entities, which are not limited in the embodiments of this application.
  • MME mobility management entity
  • AMF access and mobility management function
  • the communication device may include a network device 110 and a terminal device 120 with communication functions.
  • the network device 110 and the terminal device 120 may be the specific devices described above, which will not be described again here.
  • the communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in the embodiments of this application.
  • the "instruction” mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.
  • correlate can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.
  • Configuration in the embodiment of this application may include configuring through at least one of system messages, radio resource control (radio resource control, RRC) signaling, and media access control element (MAC CE) .
  • RRC radio resource control
  • MAC CE media access control element
  • predefined or “preset” can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices).
  • predefined can refer to what is defined in the protocol.
  • the "protocol or standard” may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this. .
  • TA is usually used for uplink transmission, which can mean that the system frame in which the terminal device sends uplink data must be a certain amount of time earlier than the corresponding downlink frame.
  • the terminal equipment's timing advance is based on the terminal equipment receiving the first symbol of the downlink channel or the time slot in which the channel is located as the downlink reference, and transmitting in advance on this basis.
  • terminal equipment can support different carriers (also known as "serving cells"). Different carriers can have different TAs, therefore, the concept of timing advance group (TAG) is introduced.
  • TAG timing advance group
  • a TAG may include TAs of one or more serving cells.
  • a TAG containing a special cell (Spcell) can be called a primary timing advance group (PTAG).
  • PTAG primary timing advance group
  • other TAGs besides PTAG can be called a secondary timing advance group (secondary timing advance group).
  • STAG secondary timing advance group
  • Spcell can include a primary cell (primary cell, PCell) or a primary secondary cell (primary secondary cell, PSCell).
  • TAG Timing advance group
  • RRC configuration can include TAG configuration (represented by "TAG-Config"), TAG information (represented by “TAG”), TAG identification (represented by “TAG-Id”) and TA timer (represented by "timeAlignmentTimer”) .
  • the TAG configuration may include a release list (represented by "tag-ToReleaseList”) and a TAG addition list (represented by "tag-ToAddModList”).
  • TAG information may include the identification of the TAG (represented by "tag-Id”) and the TA timer (represented by "timeAlignmentTimer”).
  • the corresponding duration of the TA timer can be listed in enumeration, including ⁇ 500ms, 750ms, 1280ms, 1920ms, 2560ms, 5120ms, 10240ms, infinite ⁇ .
  • the validity of the TA can be maintained through the TA timer. That is to say, when the terminal device receives the information indicating the TA sent by the network device (for example, the TA command (TA command, TAC) below), the terminal device can Start or restart the TA timer. When the TA timer has not expired, the TA maintained by the TA timer is valid, and the terminal device can communicate with the network device based on the TA. On the contrary, when the TA timer times out, the TA maintained by the TA timer becomes invalid (or invalid). At this time, the terminal device can no longer communicate with the network device based on the TA.
  • a CG may include multiple serving cells, and each serving cell will be assigned a TAG identifier.
  • the TAG information may include the TAG identifier and the TA timer. That is to say, the TA timer included in the TAG configuration is used to maintain the validity of the TA in the TAG indicated by the TAG identifier. At this time, for convenience of description, the TA timer may be said to be associated with the TAG below.
  • each serving cell can be pre-configured with an N TA,offset .
  • N TA can provide differential adjustment by the MAC CE of the network device, that is, this TA adjustment (also called “new TA”, expressed as ) is the previous TA (also known as “old TA”, expressed as ) based on, adjusted forward or backward in time.
  • This TA adjustment also called “new TA”, expressed as
  • the previous TA also known as “old TA”
  • T A is determined based on TAC.
  • the granularity of the TA adjustment may be TAG.
  • FIG. 2 shows the format of a media access control element (MAC CE) carrying TAC.
  • the MAC CE may include a TAG identification (TAG ID) field and a TAC field.
  • TAG ID TAG identification
  • TAC TAG index value
  • TA TA (0,1,2...63)
  • the length of this field can be 6 bits.
  • the TA adjustment method can be adjusted based on the absolute value of TA (also called “absolute TA”), that is, there is no need to consider the previous TA adjustment value.
  • the network device can adjust it through Absolute MAC CE (Absolute MAC CE). ) or the payload of RAR MAC directly gives an absolute TA represented by "N ⁇ TA ".
  • the value range of absolute TA can be from 0 to 3846.
  • the above-mentioned absolute TA and T A acquisition methods occur during the random access process.
  • the acquired TA is suitable for the TAG corresponding to the target cell of the random access. Therefore, the signaling carrying TAC may not contain TAG- ID.
  • the absolute MAC CE can be used in the two-step random access process, and the two-step random access can be initiated to SpCell. Therefore, the absolute MAC CE is applicable to the PTAG corresponding to the MAC entity, that is, the PTAG contains SpCell.
  • Figure 3 shows the format of the MAC CE carrying TAC.
  • the length of the MAC CE can be 2 bytes, which is 16 bits.
  • MAC CE can include the TAC field, which can occupy 12 bits. This field is used to indicate the TA index value of the time adjustment amount applied by the MAC entity.
  • the remaining 4 bits in MAC CE can be used as reserved bits (indicated by "R") and can be set to 0.
  • FIG 4 shows the format of the MAC random access response (random access response RAR) carrying TAC.
  • the length of MAC RAR can be 7 bytes, which is 56 bits.
  • the TAC field can be included, and the TAC field can occupy 7 bits. This field is used to indicate the TA index value of the time adjustment amount applied by the MAC entity.
  • the remaining 1 bit in Oct 1 can be used as a reserved bit (indicated by "R") and can be set to 0.
  • the TAC field can continue to be included, and the TAC field can occupy 5 bits.
  • the remaining 3 bits in Oct 2 can carry the uplink grant (UL Grant).
  • the uplink grant (UL Grant) can continue to be carried.
  • the temporary cell-radio network temporary identifier (cell-radio network temporary identifier, C-RNTI) can continue to be carried.
  • each TRP can schedule its PDSCH transmission through its own DCI. That is, TRP1 can schedule the transmission of the physical downlink shared channel (PDSCH) 1 through the downlink control information (DCI) carried by the physical downlink control channel (PDCCH) 1, and TRP2 can schedule the transmission through the physical downlink shared channel (PDSCH) 1.
  • DCI downlink control information
  • PDCCH2 Physical downlink shared channel
  • each TRP may also schedule its own PUSCH transmission.
  • TRP1 can schedule the transmission of PUSCH1 through the DCI carried by PDCCH1
  • TRP2 can schedule the transmission of PUSCH2 through the DCI carried by PDCCH2.
  • CORESET can be grouped by its corresponding RRC parameter "Control Resource Collection Pool Index (CORESETPoolIndex)", that is, the control resource collection with a CORESETPoolIndex of "0" can be grouped into one group, corresponding to TRP1.
  • the control resource collection whose CORESETPoolIndex is "1” can be divided into one group, corresponding to TRP2.
  • CORESETPoolIndex can be set to "0" by default.
  • the reference point of the terminal device's timing advance is calculated from the downstream reception time point.
  • the terminal device can still use one of the two TRPs as a reference point for downlink reception to adjust the TA.
  • the terminal device can still use one of the two TRPs as a reference point for downlink reception to adjust the TA.
  • the terminal device can configure a specific TRP as a reference point for downlink reception. This premise based on a single downlink reference point may be that the terminal device has only one set of downlink reception timelines, which depends on the capabilities of the terminal device.
  • two TRPs can correspond to different downlink reference points, so the two TA values indicated by the network device are adjusted according to their respective reference points.
  • the repeated transmission of uplink PUCCH/PUSCH based on multiple TRPs is supported, with the purpose of enhancing uplink coverage and transmission reliability.
  • the terminal equipment needs to send physical uplink control channel (PUCCH)/physical uplink shared channel (PUSCH) carrying the same content to different TRPs.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • the current standard only supports repeated transmission of PUSCH based on sDCI, using a TA with timing advance to sequentially send PUSCH to different TRPs.
  • PUSCH repeated transmission based on mDCI since there may not be an ideal enough backhaul as a connection between multiple TRPs, independent scheduling of terminal equipment by multiple TRPs may cause different PUSCH/PUCCHs to overlap in time.
  • the channel sounding reference signal resource set indicator (sounding reference signal resource set indicator) field can be used in the uplink scheduling DCI, and 1 or 2 SRS resource sets can be indicated through the SRS resource set indicator field, which points to the Transmission of 1 or 2 TRPs, and the uplink transmission of sTRP or mTRP can be dynamically adjusted.
  • the first SRS resource set (1st SRS resource set) and the second SRS resource set (2nd SRS resource set) can be used to characterize the first TRP and the second TRP respectively. Therefore, in this embodiment of the present application, the identity of the TRP can also be determined based on the SRS resource set identity.
  • the identifier of the TRP may be an SRS resource set identifier.
  • PUSCH/PUCCH/SRS (whether transmitted towards one TRP or aimed at two TRPs) can use the same TA value.
  • TAG corresponds to one serving cell.
  • This method of configuring TA with the serving cell as the granularity may be too rough, which may still cause interference when the terminal device communicates with the TRP based on the TA corresponding to the serving cell to which the TRP belongs.
  • a serving cell includes multiple TRPs
  • different TRPs may have different distances from the terminal equipment.
  • the terminal equipment still sends uplink signals to multiple TRPs in the serving cell based on the TA corresponding to the serving cell, This may cause interference to remain after the uplink signal reaches the TRP.
  • embodiments of the present application provide a TA configuration method with TRP as the granularity, so that different TRPs can have their own TAs, which helps to reduce interference generated when the terminal device communicates with the TRP.
  • this TA configuration method with TRP as the granularity when the TA of a certain TRP in the serving cell (hereinafter referred to as the "first TRP") fails, the behavior of the terminal equipment is not standardized, which may cause the terminal equipment and Network devices have inconsistent understanding and cannot communicate properly.
  • embodiments of the present application provide a communication method, which helps to standardize the behavior of the terminal device, so as to improve the success rate of communication between the terminal device and the network device.
  • the communication method according to the embodiment of the present application will be introduced below with reference to FIG. 6 .
  • the communication method shown in Figure 6 includes step S610.
  • step S610 if the TA of the first TRP is invalid, the terminal device performs operation 1 and/or operation 2.
  • the TA of the first TRP can be maintained by a TA timer. Therefore, the invalidity of the TA of the first TRP can be understood to mean that the TA timer corresponding to the TA of the first TRP has expired.
  • the TA maintained by the TA timer is configured at the TRP granularity.
  • the TA timer can be the timer associated with the TAG introduced above (represented by "timeAlignmentTimer").
  • the TAG can be associated with one or more TRPs.
  • TA with TRP as the granularity is indicated by TAG.
  • the above-mentioned TA timer may also be a new timer, which is not limited in the embodiment of the present application.
  • Operation 1 above may include restoring the TA of the first TRP.
  • the terminal device can communicate with the first TRP based on the valid TA.
  • the terminal device can send uplink data to the first TRP based on the valid TA.
  • the above-mentioned restoration of the TA of the first TRP may include restarting or starting the TA timer of the TA that maintains the first TRP.
  • the terminal device may start or restart the TA timer according to the first information, where the first information is used to indicate the TA of the first TRP.
  • the first information is used to indicate the TA of the first TRP.
  • the first information may be carried, for example, in a MAC protocol data unit (PDU), (for example, MAC CE, MAC RAR, etc.) or DCI.
  • PDU MAC protocol data unit
  • MAC CE for example, MAC CE, MAC RAR, etc.
  • DCI DCI
  • the above terminal device starts or restarts the TA timer according to the first information, which may include starting or restarting the TA timer when the terminal device receives the first information.
  • receiving the first information by the terminal device can be used as a trigger condition for starting or restarting the TA timer.
  • the TA indicated in the first information may be applied as the TA of the first TRP.
  • the above operation 2 may include communicating with the second TRP based on the TA of the second TRP.
  • the terminal device may send the first uplink data through the uplink resource of the second TRP.
  • the terminal device may receive downlink data sent by the second TRP.
  • the second TRP may belong to the same serving cell as the first TRP, and the TA of the second TRP is valid.
  • the fact that the TA of the second TRP is valid can be understood to mean that the TA timer corresponding to the TA of the second TRP has not expired.
  • the terminal device when the TA of the first TRP is invalid, it is stipulated that the terminal device can perform the above operation 1 and/or operation 2, which helps to improve the success rate of communication between the terminal device and the network device.
  • the network device when the terminal device performs the above operation 1 and/or operation 2, correspondingly, the network device also performs the above operation 1 and/or operation 2.
  • the network device may be the second TRP or the first TRP.
  • the following takes the terminal device performing operation 1 or operation 2 as an example to introduce the communication method of the embodiment of the present application in combination with Embodiment 1 and Embodiment 2 respectively.
  • Embodiment 1 Terminal device performs operation 1
  • the terminal device can restore the TA of the first TRP through a random access procedure.
  • the random access process can be triggered by a network device or by a terminal device. The following uses two random access processes as examples to introduce the method of restoring the TA of the first TRP in the embodiment of the present application.
  • the network equipment and terminal equipment since the network equipment and terminal equipment maintain TA timers synchronously, when the TA timer of the TA maintaining the first TRP in the terminal equipment times out, the network equipment maintains the TA timer.
  • the TA timer of a TRP's TA also times out.
  • the network device can restore the TA timer of the TA that maintains the first TRP by triggering the random access process.
  • the network device can trigger the random access process by sending a PDCCH command to the terminal device. Wherein, while triggering the random access process, the network device may also instruct the terminal device to initiate the random access process for the first TRP.
  • the network device can instruct the terminal device to initiate the random access process for the first TRP.
  • the network device can implicitly indicate to the terminal device the random access process for the first TRP. Initiate the random access process. For example, when different resources used for the random access process correspond to different TRPs, the network device may instruct the terminal device to initiate the random access process for the first TRP by indicating to the terminal device the resources corresponding to the first TRP for initiating the random access process. Random access process.
  • the network device may indicate to the terminal device in a display manner to initiate a random access process for the first TRP.
  • the network device may instruct the terminal device to initiate the random access process for the first TRP through resource indication information of the resources of the random access process, where the resource indication information may carry the indication information of the first TRP.
  • the network device may send a trigger indication to the terminal device to trigger the random access process of the terminal device, where the trigger indication may carry resource indication information and indicate the first TRP .
  • the above indication information of the first TRP may be the identification of the first TRP, where the identification of the first TRP may be, for example, "CORSETPollIndex".
  • the TRP may also be identified through other information, such as a reference signal set (for example, an SRS resource set) or a TRP index, which is not limited in the embodiment of the present application.
  • the above-mentioned resources used for random access may be resources used to transmit message 1 (msg1, or "preamble") in the four-step random access process.
  • the above-mentioned resources used for random access may also be resources used to transmit message A (msgA) in the two-step random access process.
  • the resources may be one or more of time domain resources, frequency domain resources or code domain resources. For example, different TRPs can be distinguished by preamble, or different TRPs can be distinguished by different random access channel opportunities (RO).
  • the network device when the TA of the first TRP fails, can directly trigger the random access process.
  • the network device when the TA of the first TRP fails, can also trigger the random access process when the first condition is met.
  • the first condition includes one or more of the following: the network device is waiting to send downlink information; the network device is expecting to communicate with the terminal device through the first TRP.
  • the network device expecting to communicate with the terminal device through the first TRP may include the network device expecting to receive uplink data sent by the terminal device through the first TRP.
  • the terminal device can restore the TA timer of the TA maintaining the first TRP by triggering a random access process.
  • the network device can be notified that the random access process is initiated for the first TRP.
  • notification methods There are many notification methods. The embodiments of the present application do not limit this.
  • the terminal device can use the resources corresponding to the first TRP for initiating the random access process to initiate the random access process.
  • the network device may determine that the random access process triggered by the terminal device is for the first TRP based on the resources used by the terminal device to initiate the random access process.
  • the above-mentioned resources used for random access may be resources used to transmit message 1 (msg1, or "preamble") in the four-step random access process.
  • the above-mentioned resources used for random access may also be resources used to transmit message A (msgA) in the two-step random access process.
  • the resources may be one or more of time domain resources, frequency domain resources or code domain resources. For example, different TRPs can be distinguished by preamble, or different TRPs can be distinguished by different random access channel opportunities (RO).
  • the terminal device when the TA of the first TRP fails, the terminal device can directly trigger the random access process.
  • the terminal device when the TA of the first TRP fails, the terminal device can also trigger the random access process if the second condition is met.
  • the second condition may include that the terminal device has second uplink data arriving. In other words, the second condition includes arrival of the second uplink data and the terminal device is in an uplink out-of-synchronization state.
  • the second uplink data includes one or more of the following: a logical channel or data radio bearer (DRB) transmitting the second uplink data associated with the first TRP; packet data convergence protocol (packet data convergence) protocol (PDCP) layer and/or radio link control protocol (radio link control, RLC) layer; data to be transmitted in the hybrid automatic repeat request (HARQ) buffer; SR Or data associated with buffer status reporting (BSR); PUCCH to be transmitted.
  • DRB logical channel or data radio bearer
  • the data to be transmitted in the above PDCP layer and/or RLC layer may include at least one of the following: PDCP protocol data unit (PDU), PDCP SDU, RLC PDU, RLC SDU.
  • PDU may include control PDU, for example
  • SDU may include control SDU, for example.
  • the above-mentioned PUCCH to be transmitted may include, for example, scheduling request (scheduling request, SR), HARQ feedback, channel state information (channel state information, CSI), etc.
  • the data to be transmitted in the HARQ buffer may include, for example, data to be newly transmitted or data to be retransmitted.
  • the above describes the method of restoring the TA of the first TRP.
  • the following describes the conditions under which the TA of the first TRP can be restored in the embodiment of the present application (also called the "third condition"). It should be noted that in this embodiment of the present application, when the TA of the first TRP fails, the operation of restoring the TA of the first TRP can be directly performed. Of course, the TA operation of restoring the first TRP can also be performed when the third condition is met.
  • the above third condition may include one or more of the following: the network device schedules the uplink resources of the first TRP for the terminal device; the serving cell supports (or is configured) repeated transmission; the TA of all TRPs in the serving cell invalid.
  • the terminal device can perform the operation of restoring the TA of the first TRP so as to send uplink data to the network device through the uplink resources of the first TRP (for example, , PUSCH). That is to say, if the terminal device is currently unable to determine which TRP the data to be transmitted is to be sent, the terminal device can wait for the scheduling information of the network device (for example, downlink control information (DCI)). If the scheduling information is the terminal If the device schedules the uplink resources of the first TRP, the terminal device can first restore the TA of the first TRP, and then perform uplink transmission based on the uplink resources indicated by the scheduling information.
  • DCI downlink control information
  • the above scheduling information may be requested by the terminal device through the SR.
  • the above scheduling information may also be sent independently by the network device, which is not limited in the embodiment of the present application.
  • the resources for example, PUCCH resources
  • the network device can determine based on the resources used by the SR that the uplink resources requested by the terminal device are the uplink resources of the first TRP.
  • the network device can Schedule uplink resources of the first TRP for the terminal device.
  • the SR of TRP1 may be associated with the PUCCH resource of TRP2. If the TA of TRP1 is invalid, the terminal device can trigger an SR. Since the SR is associated with the PUCCH resource of TRP2 where the TA is valid, the network device can learn that TRP1 has transmission requirements after receiving the SR, and the TA of TRP1 needs to be restored. .
  • the serving cell requires the same data to be transmitted through multiple TRPs. Therefore, if the serving cell is configured with repeated transmission, it means that the same data needs to be transmitted through multiple TRPs. At this time, the first TRP can be restored TA so that subsequent repeated transmissions can be made through the first TRP and other TRPs (for example, the second TRP).
  • the serving cell's support for repeated transmission can be determined based on one or more of the following: the serving cell is configured with PUCCH/PUSCH repeated transmission; the serving cell's PUCCH transmission is associated with multiple spatial relationship information (spatial relationship info); the serving cell The SRS of the cell is associated with multiple resource sets; and the PDCCH transmission or PDSCH transmission of the serving cell is associated with multiple transmission configuration indication (TCI state).
  • the serving cell is configured with PUCCH/PUSCH repeated transmission
  • the serving cell's PUCCH transmission is associated with multiple spatial relationship information (spatial relationship info)
  • the serving cell The SRS of the cell is associated with multiple resource sets
  • the PDCCH transmission or PDSCH transmission of the serving cell is associated with multiple transmission configuration indication (TCI state).
  • the serving cell SRS when the serving cell SRS is associated with multiple resource sets, the serving cell can be instructed to support repeated transmission of uplink PUCCH/PUSCH.
  • the PDCCH transmission or PDSCH transmission of the serving cell is associated with multiple TCI states, and/or the PUCCH transmission of the serving cell is associated with multiple spatial relationship information.
  • This association method usually exists in the serving cell that supports repeated transmission. Therefore, based on the above correlation method, it can be determined that the serving cell supports repeated transmission.
  • the terminal device may choose to restore the TA of a certain TRP in the serving cell (for example, the TA of the first TRP).
  • the terminal device can notify the network device.
  • the terminal device may carry indication information in message 3 (msg3) in the 4-step random access process to indicate that the TAs of all TRPs in the serving cell are invalid.
  • the terminal device may carry indication information in the message A (msgA) in the 2-step random access process to indicate that the TA of all TRPs in the serving cell is invalid.
  • Embodiment 2 Terminal device performs operation 2
  • the terminal device can directly communicate with the second TRP, which helps to reduce the delay required by the terminal device to receive or send data.
  • the terminal device can use the uplink resources of the second TRP to send the first uplink data based on the TA of the second TRP.
  • the uplink resource of the second TRP may be configured by the network device for the terminal device through a configured grant (CG).
  • CG configured grant
  • the above-mentioned uplink resources of the second TRP can also be dynamically scheduled by the network device for the terminal device through dynamic grant (DG).
  • the terminal device can directly use this type of uplink resource transmission.
  • the first upstream data can be configured by RRC through high-level signaling (for example, IE ConfiguredGrantConfig), which is not limited in the embodiments of this application.
  • the terminal device can use this type of uplink resource for transmission.
  • the uplink resources configured with authorization type 2 (type 2) can be activated and deactivated by DCI instructions. That is to say, the parameters required to configure the uplink resources configured with authorization type 2 can be configured by IE ConfiguredGrantConfig. , but the configured uplink resources can only be used when activated by DCI.
  • the terminal device can request network device scheduling by triggering the SR and/or BSR process. uplink resources for transmission.
  • the SR resources for example, PUCCH resources
  • the network device can determine based on the resources used by the SR that the uplink resources requested by the terminal device are the uplink resources of the second TRP.
  • the network device can Schedule uplink resources of the second TRP for the terminal device.
  • the above SR can also be used to indicate to the network device that the TA of the first TRP needs to be restored. That is, the SR may be used to indicate that the TA of the first TRP is invalid and data is to be transmitted.
  • the SR of the first TRP can be associated with the PUCCH resources of the second TRP. If the TA of the first TRP is invalid, the terminal device can trigger the SR. Since the SR is associated with the PUCCH resources of the second TRP with a valid TA, the network After receiving the SR, the device can learn that the first TRP has transmission requirements and the TA of the first TRP needs to be restored.
  • the terminal device may trigger the SR, and in response to the SR, the network device may send Scheduling information, accordingly, the terminal device can determine the TRP for uplink transmission based on the scheduling information sent by the network device. Assume that the network device schedules the uplink resources of the second TRP for the terminal device, then the terminal device can use the uplink resources of the second TRP for uplink transmission.
  • the resources of the SR for example, PUCCH resources
  • the terminal device may be independent of the TRP
  • the terminal device may trigger the SR, and in response to the SR, the network device may send Scheduling information, accordingly, the terminal device can determine the TRP for uplink transmission based on the scheduling information sent by the network device. Assume that the network device schedules the uplink resources of the second TRP for the terminal device, then the terminal device can use the uplink resources of the second TRP for uplink transmission.
  • the conditions for triggering SR in the embodiment of the present application may be based on the triggering conditions of SR stipulated in the current protocol.
  • the conditions for triggering SR may also be conditions introduced in future protocols. This is not the case in the embodiment of the present application. limited.
  • the terminal device can directly use the uplink resource to transmit the first uplink data.
  • the network device can dynamically configure the uplink resources of the second TRP for the terminal device through DCI. Accordingly, the terminal device can generate an uplink data packet (for example, MAC PDU) based on the dynamically configured uplink resource, and submit the data packet to the lower layer (for example, the physical layer).
  • an uplink data packet for example, MAC PDU
  • the terminal device can request the network device to schedule the uplink by triggering the SR and/or BSR process. resources are transferred. If the terminal device triggers the SR process, the SR resources (for example, PUCCH resources) sent by the terminal device can be associated with the TRP, and different TRPs can be associated with different resources. That is to say, when the terminal device uses the resources corresponding to the second TRP to send the SR, the network device can determine based on the resources used by the SR that the uplink resources requested by the terminal device are the uplink resources of the second TRP. Correspondingly, the network device can Schedule uplink resources of the second TRP for the terminal device.
  • the SR resources for example, PUCCH resources
  • the above SR can also be used to indicate to the network device that the TA of the first TRP needs to be restored. That is, the SR may be used to indicate that the TA of the first TRP is invalid and data is to be transmitted.
  • the SR of the first TRP can be associated with the PUCCH resources of the second TRP. If the TA of the first TRP is invalid, the terminal device can trigger the SR. Since the SR is associated with the PUCCH resources of the second TRP with a valid TA, the network After receiving the SR, the device can learn that the first TRP has transmission requirements and the TA of the first TRP needs to be restored. Correspondingly, the network device may schedule the uplink resources of the first TRP for the terminal device.
  • the embodiment of the present application also provides operations that the terminal device can perform (also called “target operations") when the TA of the first TRP fails, and operations performed on those objects.
  • targets operations also called “target operations”
  • the target operation when the TA of the first TRP fails, the target operation is triggered.
  • the target operation includes one or more of the following operations: clearing the hybrid automatic repeat request (HARQ) buffer; notifying the Radio Resource Control (Radio Resource Control, RRC) to release uplink resources (wherein, the uplink Resources may include, for example, PUCCH, SRS, cell group (CG), PUSCH and semi-persistent scheduling (SPS), etc.); maintain timing advance absolute value; initiate random access process; and effectively through TA TRP retransmits the data in the HARQ buffer.
  • the terminal device may not perform the above target operation.
  • the serving cell is configured with mTRP
  • the TA of the first TRP fails, at this time, there may be a valid TA of the TRP in the serving cell. Therefore, the valid TRP of the TA can be retransmitted in the HARQ buffer. data, so that the terminal device can not perform any target operations.
  • the above target operation may also include one or more operations specified in the existing protocol. For example, it may include one or more of the following operations: clearing the configured downlink allocation and uplink authorization. ; Clear PUSCH resources used for semi-static CSI reporting; Treat all running TA timers as expired.
  • the objects targeted by the above target operations may be different.
  • the target operation is directed to one or more of the following objects: all serving cells of the terminal device; one or more The TRP associated with the TAG; and the serving cell where the TRP associated with one or more TAGs is located.
  • all serving cells of the terminal device may be all serving cells to which the terminal device establishes connections, or may include all serving cells in the serving cell list of the terminal device, or may also include all services communicating with the terminal device.
  • the embodiment of this application does not limit this.
  • the target operation may include clearing the HARQ buffer (buffer) associated with the TRPs included in the one or more TAGs.
  • the target operation can include clearing The HARQ buffer corresponding to the HARQ process associated with the TRP included in the one or more TAGs.
  • each serving cell may have one HARQ entity, and the HARQ processes in the HARQ entity may be divided into multiple groups, where multiple groups are associated with multiple TRPs.
  • the above target operation may include clearing the HARQ buffer corresponding to the HARQ process in the group associated with the TRP included in one or more TAGs.
  • the target operation includes notifying RRC to release uplink resources.
  • the above target operation may include notifying the RRC to release the uplink resources corresponding to the TRPs associated with one or more TAGs.
  • TAG mentioned above may be PTAG or STAG, which is not limited in the embodiments of the present application.
  • the target operation is directed to one or more of the following objects: all serving cells of the terminal device; the TRP; and the serving cell where the TRP is located.
  • the target operation may include clearing the HARQ buffer associated with the TRP.
  • each TRP in the serving cell can have a HARQ entity, and the HARQ processes in each HARQ entity can belong to different TRPs.
  • the above target operation can include clearing The HARQ buffer corresponding to the HARQ process associated with the above TRP.
  • each serving cell may have one HARQ entity, and the HARQ processes in the HARQ entity may be divided into multiple groups, where multiple groups are associated with multiple TRPs.
  • the above target operation may include clearing the HARQ buffer corresponding to the HARQ process in the group associated with the TRP.
  • the target operation includes notifying RRC to release uplink resources.
  • the above target operation may include notifying the RRC to release the uplink resources corresponding to the TRP.
  • TAG mentioned above may be PTAG or STAG, which is not limited in the embodiments of the present application.
  • the terminal device may not perform any target operation (for example, release the uplink resources of the first TRP).
  • the timer for the TA validity of a TRP is usually maintained at the MAC layer.
  • the lower layer for example, the physical layer
  • the MAC layer of the terminal device may send first indication information to the lower layer, and the first indication information is used to indicate that the TA of the first TRP is invalid. That is, when the TA of the first TRP is invalid and the uplink resources of the first TRP have not been released, the MAC layer sends the first indication information to the lower layer of the MAC. Correspondingly, after the TA of the first TRP is restored to be valid, the MAC layer may also send second indication information to the lower layer, and the second indication information is used to indicate that the TA of the first TRP is valid.
  • the MAC layer may not transmit the first indication information.
  • the MAC layer can send the first indication information regardless of whether the terminal device performs the target operation. The embodiments of the present application do not limit this.
  • Figure 7 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device shown in Figure 7 includes a processing unit 710.
  • the processing unit 710 is configured to perform one or more of the following operations: communicate with the second TRP based on the TA of the second TRP; restore the first The TA of one TRP is valid, wherein the TA of the second TRP is valid, and the first TRP and the second TRP belong to a serving cell of the terminal device.
  • restoring the TA of the first TRP to be valid includes restoring the TA of the first TRP to be valid through a random access process.
  • the random access process is triggered by a network device or the terminal device.
  • the random access process is triggered by the network device, wherein the first condition includes one or more of the following: the network device Downlink information is to be sent; the network device expects to communicate with the terminal device through the first TRP.
  • the random access process is triggered by the terminal device, wherein the second condition includes that the terminal device has second uplink data arriving.
  • the second uplink data includes one or more of the following: a logical channel or data radio bearer DRB for transmitting the second uplink data associated with the first TRP; Packet Data Convergence Protocol PDCP Data to be transmitted in the layer and/or radio link layer control protocol RLC layer; data to be transmitted in the hybrid automatic repeat request HARQ buffer; data associated with the scheduling request SR or buffer status report BSR; the physical uplink to be transmitted channel control channel PUCCH.
  • a logical channel or data radio bearer DRB for transmitting the second uplink data associated with the first TRP
  • Packet Data Convergence Protocol PDCP Data to be transmitted in the layer and/or radio link layer control protocol RLC layer
  • data to be transmitted in the hybrid automatic repeat request HARQ buffer data associated with the scheduling request SR or buffer status report BSR
  • the physical uplink to be transmitted channel control channel PUCCH the physical uplink to be transmitted channel control channel PUCCH.
  • the terminal device restores the TA of the first TRP, wherein the third condition includes the following: One or more: the network device schedules the uplink resources of the first TRP for the terminal device; the serving cell supports repeated transmission; the TA of all TRPs in the serving cell is invalid.
  • the serving cell supporting repeated transmission includes one or more of the following: the serving cell is configured with physical uplink shared channel PUSCH repeated transmission; the serving cell's PUCCH transmission is associated with multiple spatial relationship information; the channel sounding reference signal SRS of the serving cell is associated with multiple resource sets; and the PDCCH transmission or PDSCH transmission of the serving cell is associated with multiple transmission configuration indication TCI states.
  • the TA based on the second TRP communicates with the second TRP, including the TA based on the second TRP sending the first uplink data to the second TRP, transmitting the first
  • the uplink resources of the second TRP of an uplink data include one or more of the following: uplink resources configured in configuration authorization type 1; uplink resources activated in uplink resources configured in configuration authorization type 2; based on Dynamically grant scheduled uplink resources; through the uplink resources requested by the SR, the SR resources used by the SR are associated with the second TRP.
  • the terminal device when the TA of the first TRP is invalid, the terminal device further includes: a sending unit configured to send the first TRP to the lower layer of the MAC through the media access control MAC layer. Indication information, the first indication information is used to indicate that the TA of the first TRP is invalid.
  • the sending unit is further configured to send a message to the MAC layer through the MAC layer when the TA of the first TRP is invalid and the uplink resources of the first TRP have not been released.
  • the lower layer of the MAC sends the first indication information.
  • FIG 8 is a schematic diagram of a network device according to an embodiment of the present application.
  • the network device 800 shown in Figure 8 includes: a processing unit 810.
  • the processing unit 810 When the timing advance TA of the first transmission point TRP is invalid, the processing unit 810 performs one or more of the following operations: communicates with the terminal device based on the TA of the second TRP; restores the TA of the first TRP to Valid, wherein the TA of the second TRP is valid, and the first TRP and the second TRP belong to a serving cell of the terminal device.
  • the network device restoring the TA of the first TRP to be valid includes the network device restoring the TA of the first TRP to be valid through a random access process.
  • the random access process is triggered by the network device or the terminal device.
  • the random access process is triggered by the network device, wherein the first condition includes one or more of the following: the network device Downlink information is to be sent; the network device expects to communicate with the terminal device through the first TRP.
  • the random access process is triggered by the terminal device, wherein the second condition includes that the terminal device has second uplink data arriving.
  • the second uplink data includes one or more of the following: a logical channel or data radio bearer DRB for transmitting the second uplink data associated with the first TRP; Packet Data Convergence Protocol PDCP Data to be transmitted in the layer and/or RLC layer; data to be transmitted in the hybrid automatic repeat request HARQ buffer; data associated with the scheduling request SR or buffer status report BSR; the physical uplink control channel PUCCH to be transmitted.
  • a logical channel or data radio bearer DRB for transmitting the second uplink data associated with the first TRP
  • Packet Data Convergence Protocol PDCP Data to be transmitted in the layer and/or RLC layer
  • data to be transmitted in the hybrid automatic repeat request HARQ buffer data to be transmitted in the hybrid automatic repeat request HARQ buffer
  • data associated with the scheduling request SR or buffer status report BSR the physical uplink control channel PUCCH to be transmitted.
  • the terminal device restores the TA of the first TRP, wherein the third condition includes the following: One or more: the network device schedules the uplink resources of the first TRP for the terminal device; the serving cell supports repeated transmission; the TA of all TRPs in the serving cell is invalid.
  • the serving cell supporting repeated transmission includes one or more of the following: the serving cell is configured with physical uplink shared channel PUSCH repeated transmission; the serving cell's PUCCH transmission is associated with multiple spatial relationship information; the channel sounding reference signal SRS of the serving cell is associated with multiple resource sets; and the PDCCH transmission or PDSCH transmission of the serving cell is associated with multiple transmission configuration indication TCI states.
  • the TA based on the second TRP communicates with the terminal device, including the TA based on the second TRP receiving the first uplink data sent by the terminal device, wherein transmitting the
  • the uplink resources of the second TRP of the first uplink data include one or more of the following: uplink resources configured in configuration authorization type 1; uplink resources activated in uplink resources configured in configuration authorization type 2; Uplink resources scheduled based on dynamic grant; through the uplink resources requested by the SR, the SR resources used by the SR are associated with the second TRP.
  • the processing unit 710 may be a processor 910.
  • the terminal device 700 may also include a transceiver 930 and a memory 920, as specifically shown in Figure 9.
  • the processing unit 810 may be a processor 910.
  • the network device 800 may also include a transceiver 930 and a memory 920, as specifically shown in Figure 9.
  • Figure 9 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the dashed line in Figure 9 indicates that the unit or module is optional.
  • the device 900 can be used to implement the method described in the above method embodiment.
  • Device 900 may be a chip, terminal device or network device.
  • Apparatus 900 may include one or more processors 910.
  • the processor 910 can support the device 900 to implement the method described in the foregoing method embodiments.
  • the processor 910 may be a general-purpose processor or a special-purpose processor.
  • the processor may be a central processing unit (CPU).
  • the processor can also be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or an off-the-shelf programmable gate array (FPGA) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • Apparatus 900 may also include one or more memories 920.
  • the memory 920 stores a program, which can be executed by the processor 910, so that the processor 910 executes the method described in the foregoing method embodiment.
  • the memory 920 may be independent of the processor 910 or integrated in the processor 910 .
  • Apparatus 900 may also include a transceiver 930.
  • Processor 910 may communicate with other devices or chips through transceiver 930.
  • the processor 910 can transmit and receive data with other devices or chips through the transceiver 930 .
  • An embodiment of the present application also provides a computer-readable storage medium for storing a program.
  • the computer-readable storage medium can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • An embodiment of the present application also provides a computer program product.
  • the computer program product includes a program.
  • the computer program product can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • An embodiment of the present application also provides a computer program.
  • the computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • the "instruction" mentioned may be a direct instruction, an indirect instruction, or an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean determining B only based on A.
  • B can also be determined based on A and/or other information.
  • the term "correspondence” can mean that there is a direct correspondence or indirect correspondence between the two, or it can also mean that there is an association between the two, or it can also mean indicating and being instructed, configuring and being configured, etc. relation.
  • predefinition or “preconfiguration” can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices).
  • devices for example, including terminal devices and network devices.
  • predefined can refer to what is defined in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be determined by the implementation process of the embodiments of the present application. constitute any limitation.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVD)) or semiconductor media (e.g., solid state disks (SSD) )wait.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., digital video discs (DVD)
  • semiconductor media e.g., solid state disks (SSD)

Landscapes

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

Abstract

提供了一种通信方法、终端设备和网络设备。该方法包括：在第一传输点TRP的定时提前TA无效的情况下，终端设备执行以下操作中的一种或多种：基于第二TRP的TA与所述第二TRP通信；恢复所述第一TRP的TA为有效，其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。以TRP为粒度配置TA，当服务小区的第一TRP的TA失效后，终端设备可以基于服务小区中第二TRP的TA与第二TRP通信；和/或恢复所述第一TRP的所述TA为有效，以保证终端设备与服务小区之间可以继续通信。

Description

通信方法、终端设备及网络设备 技术领域
本申请涉及通信技术领域，并且更为具体地，涉及一种通信方法、终端设备及网络设备。
背景技术
传统的定时提前(timing advance，TA)是以服务小区为粒度配置的，当服务小区的TA失效后，终端设备无法再与服务小区中的传输点(transmitting and receiving point，TRP)通信。
发明内容
本申请提供一种通信方法、终端设备和网络设备。下面对本申请涉及的各个方面进行介绍。
第一方面，提供了一种通信方法，包括：在第一传输点TRP的定时提前TA无效的情况下，终端设备执行以下操作中的一种或多种：基于第二TRP的TA与所述第二TRP通信；恢复所述第一TRP的TA为有效，其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
第二方面，提供一种通信方法，包括：在第一传输点TRP的定时提前TA无效的情况下，网络设备执行以下操作中的一种或多种：基于第二TRP的TA与终端设备通信；恢复所述第一TRP的TA为有效，其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
第三方面，提供一种终端设备，包括：在第一传输点TRP的定时提前TA无效的情况下，处理单元，执行以下操作中的一种或多种：基于第二TRP的TA与所述第二TRP通信；恢复所述第一TRP的所述TA为有效，其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
第四方面，提供一种网络设备，包括：在第一传输点TRP的定时提前TA无效的情况下，处理单元，执行以下操作中的一种或多种：基于第二TRP的TA与终端设备通信；恢复所述第一TRP的所述TA为有效，其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
第五方面，提供一种终端，包括处理器、存储器以及通信接口，所述存储器用于存储一个或多个计算机程序，所述处理器用于调用所述存储器中的计算机程序，使得所述终端设备执行第一方面的方法中的部分或全部步骤。
第六方面，提供一种网络设备，包括处理器、存储器、通信接口，所述存储器用于存储一个或多个计算机程序，所述处理器用于调用所述存储器中的计算机程序，使得所述网络设备执行第二方面的方法中的部分或全部步骤。
第七方面，本申请实施例提供了一种通信系统，该系统包括上述的终端和/或网络设备。在另一种可能的设计中，该系统还可以包括本申请实施例提供的方案中与该终端或网络设备进行交互的其他设备。
第八方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序使得终端执行上述各个方面的方法中的部分或全部步骤。
第九方面，本申请实施例提供了一种计算机程序产品，其中，所述计算机程序产品包括存储了计算机程序的非瞬时性计算机可读存储介质，所述计算机程序可操作来使终端执行上述各个方面的方法中的部分或全部步骤。在一些实现方式中，该计算机程序产品可以为一个软件安装包。
第十方面，本申请实施例提供了一种芯片，该芯片包括存储器和处理器，处理器可以从存储器中调用并运行计算机程序，以实现上述各个方面的方法中所描述的部分或全部步骤。
在本申请实施例中，以TRP为粒度配置TA，当服务小区的第一TRP的TA失效后，终端设备可以基于服务小区中第二TRP的TA与第二TRP通信；和/或恢复所述第一TRP的所述TA为有效，以保证终端设备与服务小区之间可以继续通信。
附图说明
图1A～图1C是可应用本申请实施例的通信系统的系统架构图。
图2示出了承载TAC的MAC CE的格式。
图3示出了承载TAC的MAC CE的格式。
图4示出了承载TAC的MAC RAR的格式。
图5是本申请实施例适用的多TRP场景的示意图。
图6是本申请实施例的通信方法的流程图。
图7是本申请实施例的终端设备的示意图。
图8是本申请实施例的网络设备的示意图。
图9是本申请实施例的装置的示意性结构图。
具体实施方式
通信系统架构
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、先进的长期演进(advanced long term evolution，LTE-A)系统、新无线(new radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、NTN系统、通用移动通信系统(universal mobile telecommunication system，UMTS)、无线局域网(wireless local area networks，WLAN)、无线保真(wireless fidelity，WiFi)、第五代通信(5th-generation，5G)系统或其他通信系统，例如未来的通信系统，如第六代移动通信系统，又如卫星通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现。然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(device to device，D2D)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，车辆间(vehicle to vehicle，V2V)通信，或车联网(vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
本申请实施例中的通信系统可以应用于载波聚合(carrier aggregation，CA)场景，也可以应用于双连接(dual connectivity，DC)场景，还可以应用于独立(standalone，SA)布网场景。
本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是专用频谱。
本申请实施例可应用于NTN系统，也可应用于地面通信网络(terrestrial networks，TN)系统。作为示例而非限定，NTN系统包括基于NR的NTN系统和基于IoT的NTN系统。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、移动终端(mobile Terminal，MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
在本申请实施例中，终端设备可以是WLAN中的站点(STATION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(public land mobile network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以是指向用户提供语音和/或数据连通性的设备，可以用于连接人、物和机，例如具有无线连接功能的手持式设备、车载设备等。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。可选地，终端设备可以用于充当基站。例如，终端设备可以充当调度实体，其在V2X或D2D等中的终端设备之间提供侧行链路信号。比如，蜂窝电话和汽车利用侧行链路信号彼此通信。蜂窝电话和智能家居设备之间通信，而无需通过基站中继通信信号。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的 电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。本申请实施例所涉及的终端设备还可以称为终端、用户设备(user equipment，UE)、接入终端设备、车载终端、工业控制终端、UE单元、UE站、移动站、移动台、远方站、远程终端设备、移动设备、UE终端设备、无线通信设备、UE代理或UE装置等。终端设备也可以是固定的或者移动的。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备也可以称为接入网设备或无线接入网设备，如网络设备可以是基站。本申请实施例中的网络设备可以是指将终端设备接入到无线网络的无线接入网(radio access network，RAN)节点(或设备)。基站可以广义的覆盖如下中的各种名称，或与如下名称进行替换，比如：节点B(NodeB)、演进型基站(evolved NodeB，eNB)、下一代基站(next generation NodeB，gNB)、中继站、接入点、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、主站MeNB、辅站SeNB、多制式无线(MSR)节点、家庭基站、网络控制器、接入节点、无线节点、接入点(access piont，AP)、传输节点、收发节点、基带单元(base band unit，BBU)、射频拉远单元(remote radio unit，RRU)、有源天线单元(active antenna unit，AAU)、射频头(remote radio head，RRH)、中心单元(central unit，CU)、分布式单元(distributed unit，DU)、定位节点等。基站可以是宏基站、微基站、中继节点、施主节点或类似物，或其组合。基站还可以指用于设置于前述设备或装置内的通信模块、调制解调器或芯片。基站还可以是移动交换中心以及设备到设备D2D、车辆外联(vehicle-to-everything，V2X)、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备、6G网络中的网络侧设备、未来的通信系统中承担基站功能的设备等。基站可以支持相同或不同接入技术的网络。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
基站可以是固定的，也可以是移动的。例如，直升机或无人机可以被配置成充当移动基站，一个或多个小区可以根据该移动基站的位置移动。在其他示例中，直升机或无人机可以被配置成用作与另一基站通信的设备。
在一些部署中，本申请实施例中的网络设备可以是指CU或者DU，或者，网络设备包括CU和DU。gNB还可以包括AAU。
网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和卫星上。本申请实施例中对网络设备和终端设备所处的场景不做限定。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。在本申请一些实施例中，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。在本申请一些实施例中，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小区(metro cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
示例性地，图1A为本申请实施例提供的一种通信系统的架构示意图。如图1A所示，通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。
图1A示例性地示出了一个网络设备和两个终端设备，在本申请一些实施例中，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对 此不做限定。
示例性地，图1B为本申请实施例提供的另一种通信系统的架构示意图。请参见图1B，包括终端设备1101和卫星1102，终端设备1101和卫星1102之间可以进行无线通信。终端设备1101和卫星1102之间所形成的网络还可以称为NTN。在图1B所示的通信系统的架构中，卫星1102可以具有基站的功能，终端设备1101和卫星1102之间可以直接通信。在系统架构下，可以将卫星1102称为网络设备。在本申请一些实施例中，通信系统中可以包括多个网络设备1102，并且每个网络设备1102的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
示例性地，图1C为本申请实施例提供的另一种通信系统的架构示意图。请参见图1C，包括终端设备1201、卫星1202和基站1203，终端设备1201和卫星1202之间可以进行无线通信，卫星1202与基站1203之间可以通信。终端设备1201、卫星1202和基站1203之间所形成的网络还可以称为NTN。在图1C所示的通信系统的架构中，卫星1202可以不具有基站的功能，终端设备1201和基站1203之间的通信需要通过卫星1202的中转。在该种系统架构下，可以将基站1203称为网络设备。在本申请一些实施例中，通信系统中可以包括多个网络设备1203，并且每个网络设备1203的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
需要说明的是，图1A-图1C只是以示例的形式示意本申请所适用的系统，当然，本申请实施例所示的方法还可以适用于其它系统，例如，5G通信系统、LTE通信系统等，本申请实施例对此不作具体限定。
在本申请一些实施例中，图1A-图1C所示的无线通信系统还可以包括移动性管理实体(mobility management entity，MME)、接入与移动性管理功能(access and mobility management function，AMF)等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1A示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中的“配置”可以包括通过系统消息、无线资源控制(radio resource control，RRC)信令和媒体接入控制单元(media access control control element，MAC CE)中的至少一种来配置。
在本申请一些实施例中，"预定义的"或"预设的"可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义的可以是指协议中定义的。
在本申请一些实施例中，所述"协议或者标准"可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
为了便于理解，先对本申请实施例涉及的一些相关技术知识进行介绍。以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
定时提前(Timing Advance，TA)
TA通常用于上行传输，可以指终端设备发送上行数据的系统帧相比对应的下行帧要提前一定的时间。例如，终端设备的定时提前是以终端设备收到下行信道或信道所在的时隙的第一个符号为下行参考，在此基础上进行提前发射。
以载波聚合场景为例，终端设备可以支持不同的载波(又称“服务小区”)。不同的载波可以具有不同的TA，因此，引入了定时提前组(timing advance group，TAG)的概念。通常，一个TAG可以包括的一个或多个服务小区的TA。对于包含特殊小区(special cell，Spcell)的TAG可以称为主定时提前组(primary timing advance group，PTAG)，相应地，除了PTAG之外的其他TAG可以称为辅定时提前组(secondary timing advance group，STAG)。其中，Spcell可以包括主小区(primary cell，PCell)或主辅小区(primary secondary cell，PSCell)。
当前的通信标准中(包括NR、3GPP Rel.17等)规定，在一个小区组(cell group，CG)中，终端设备可以被配置最多4个定时提前组(timing advance group，TAG)。用于配置TAG的RRC配置可以表示为：
Figure PCTCN2022098251-appb-000001
一般，RRC配置可以包括TAG配置(用“TAG-Config”表示)、TAG信息(用“TAG”表示)、TAG标识(用“TAG-Id”表示)以及TA定时器(用“timeAlignmentTimer”表示)。其中，TAG配置可以包括释放列表(用“tag-ToReleaseList”表示)以及TAG添加列表(用“tag-ToAddModList”表示)。TAG信息可以包括TAG的标识(用“tag-Id”表示)以及TA定时器(用“timeAlignmentTimer”表示)。TA定时器对应的时长可以以列举的方式列出，包括{500ms,750ms,1280ms,1920ms,2560ms,5120ms,10240ms,无穷}。
通常，TA的有效性可以通过TA定时器来维护，也就是说，当终端设备收到网络设备发送的指示TA的信息(例如，下文的TA命令(TA command，TAC))后，终端设备可以启动或者重启TA定时器。当TA定时器未超时，则TA定时器维护的TA有效，终端设备可以基于TA与网络设备进行通信。相反地，当TA定时器超时，则TA定时器维护的TA失效(或者说无效)，此时，终端设备不能再基于TA与网络设备进行通信。
需要说明的是，一个CG可以包括多个服务小区，且每一个服务小区都会被分配一个TAG的标识。
如上文介绍，TAG信息中可以包含TAG的标识以及TA定时器，也就是说，TAG配置中包括的TA定时器用于维护上述TAG的标识指示的TAG中的TA的有效性。此时，为了便于描述，下文可以称该TA定时器与TAG关联。
下文介绍TA的计算方式。
在一些实现方式中，TA可以通过公式(N TA+N TA，offset)×T c计算，其中，N TA，offset表示定时提前偏移(TA offset)，N TA表示TA调整量，T c表示通信系统(例如，NR系统)中最小时间单位，通常，T c＝1/(4096×480kHz)。
通常，在一个CG中，每一个服务小区都可以预先配置一个N TA，offset。另外，N TA可以由网络设备的MAC CE来提供差分式的调整，即本次TA调整(又称“new TA”，表示为
Figure PCTCN2022098251-appb-000002
)是以上次TA(又称“old TA”，表示为
Figure PCTCN2022098251-appb-000003
)为基础，在时间上向前或向后调整的。调整的计算公式如下：
Figure PCTCN2022098251-appb-000004
或者说，
Figure PCTCN2022098251-appb-000005
是收到TA命令(TA command，TAC)之前使用的TA调整量，
Figure PCTCN2022098251-appb-000006
是收到TAC后更新后的TA调整量。其中，T A是根据TAC确定的。另外，该TA调整的粒度可以为TAG。
图2示出了承载TAC的媒体接入控制控制单元(media access control control element，MAC CE)的格式。参见图2，MAC CE可以包括TAG的标识(TAG ID)字段以及TAC字段。通常，TAG ID字段长度可以为2比特，并且包含SpCell的TAG的标识为0。TAC字段用于指示TA索引值TA(0,1,2…63)，用于控制MAC实体必须应用的定时调整量(如TS 38.213[6]中规定的)。该字段的长度可以为6比特。
在另一些实现方式中，TA调整方式可以是以TA的绝对值(又称“绝对TA”)为基础调整，即不需要考虑之前的TA调整值，网络设备可以通过绝对MAC CE(Absolute MAC CE)或RAR MAC的载荷(payload)直接给出一个绝对TA用“N` TA”表示。通常，绝对TA的取值范围可以是0到3846，相 应地，TA可以通过公式：N` TA＝T A×16×64×2 μ计算，其中，T A是根据TAC确定的。
在一些场景中，上述绝对TA以及T A的获取方式发生在随机接入过程中，所获取的TA适用于随机接入的目标小区对应的TAG，因此，承载TAC的信令可以不包含TAG-ID。例如，绝对MAC CE可以用于两步随机接入过程，且两步随机接入可以向SpCell发起，因此，绝对MAC CE适用于该MAC实体所对应的PTAG，即该PTAG包含SpCell。
图3示出了承载TAC的MAC CE的格式。参见图3，MAC CE的长度可以为2字节，即16比特。MAC CE可以包括TAC字段，TAC字段可以占用12比特。该字段用于指示MAC实体应用的时间调整量的TA索引值。另外，MAC CE中剩余的4比特可以作为保留位(用“R”表示)，可以置0。
图4示出了承载TAC的MAC随机接入响应(random access response RAR)的格式。参见图4，MAC RAR的长度可以为7字节，即56比特。在第一字节(用“Oct 1”表示)中，可以包括TAC字段，TAC字段可以占用7比特。该字段用于指示MAC实体应用的时间调整量的TA索引值。Oct 1中剩余的1比特可以作为保留位(用“R”表示)，可以置0。
在第二字节(用“Oct 2”表示)中，可以继续包括TAC字段，TAC字段可以占用5比特。Oct 2中剩余的3比特可以承载上行授权(UL Grant)。
在第三字节到第五字节(用“Oct 3～5”表示)中，可以继续承载上行授权(UL Grant)。在第六字节到第七字节(用“Oct 6～7”表示)中，可以继续承载临时小区无线网络临时标识(cell-radio network temporary identifier，C-RNTI)。
多TRP(multi-TRP，mTRP)场景的调度
参见图5，在多DCT-多TRP(Multiple DCI-Multi-TRP，mDCI-mTRP)的场景下，每个TRP可以通过各自的DCI来调度其PDSCH传输。即，TRP1可以通过物理下行控制信道(physical downlink control channel，PDCCH)1承载的下行控制信息(downlink control information，DCI)调度物理下行共享信道(physical downlink shared channel，PDSCH)1的传输，TRP2可以通过PDCCH2承载的DCI调度PDSCH2的传输。
申请人认为，在后续协议的演进过程中，每个TRP也可能调度各自的PUSCH传输。继续参见图5，即TRP1可以通过PDCCH1承载的DCI调度PUSCH1的传输，TRP2可以通过PDCCH2承载的DCI调度PUSCH2的传输。
需要说明的是，mDCI-mTRP的场景中，对于DCI的需求量较大且各个TRP进行独立的调度，因此增加了DCI所关联的控制资源集合(control resource set，CORESET)的数量。在一些实现方式中，可以将CORESET通过它对应的RRC参数“控制资源集合池索引(CORESETPoolIndex)”进行分组，即CORESETPoolIndex为“0”的控制资源集合可以分为一组，对应TRP1。CORESETPoolIndex为“1”的控制资源集合可以分为一组，对应TRP2。另外，当网络设备没有为控制资源集合配置CORESETPoolIndex的时候，可以默认CORESETPoolIndex为“0”。
另外，如果终端设备工作在一个TRP(sTRP)的模式下，那么终端设备的定时提前的参考点是以下行接收时间点算起。在mTRP的场景下，终端设备仍可以使用两个TRP中的一个作为下行接收的参考点来调整TA。比如使用CORESETPoolIndex为0的TRP作为下行接收的参考点。或者网络设备可以配置的某一个特定的TRP作为下行接收的参考点。这种，基于单一下行参考点的前提可以是终端设备仅有一套下行的接收时间线，即取决于终端设备的能力。
当然，对于能力较强的终端设备来说，也可以使用两个不同的下行接收参考点。继续参见图5，两个TRP可以对应不同下行参考点，那么网络设备指示的两个TA值则是根据各自的参考点来进行调整。
上行多TRP操作
在目前通信协议(例如，3GPP Rel.17)中，支持了基于多TRP的上行PUCCH/PUSCH的重复(repetition)传输，其目的是增强上行的覆盖和传输的可靠性。终端设备需要向不同的TRP发送承载相同内容的物理上行控制信道(physical uplink control channel，PUCCH)/物理上行共享信道(physical uplink shared channel，PUSCH)。对于PUSCH的重复传输而言，目前的标准中仅支持基于sDCI的PUSCH重复传输，使用一个定时提前的TA来顺序发送PUSCH到不同的TRP。对于基于mDCI的PUSCH重复传输，由于多个TRP之间可能没有足够理想的回程线路(backhaul)作为连接，多个TRP对终端设备的独立调度有可能引起不同PUSCH/PUCCH在时间上的重叠。
对sDCI的mPUSCH传输，可以在上行调度DCI中使用信道探测参考信号资源集指示(sounding reference signal resource set indicator)域，并通过SRS资源集指示域指示1个或2个SRS资源集，它指向对1个或2个TRP的传输，且可以动态地调整sTRP或mTRP的上行传输。
目前，可以使用第一SRS资源集(1st SRS resource set)和第二SRS资源集(2nd SRS resource set)来分别表征第一TRP和第二TRP。因此，在本申请实施例中，TRP的标识也可以基于SRS资源集标识 确定。例如，TRP的标识可以为SRS资源集标识。
另外，对于上行的信道和信号的定时提前来说，PUSCH/PUCCH/SRS(不管是朝向一个TRP发射，还是对准两个TRP发射)都可以使用同一个TA值。
如上文所述，传统的TA是以TAG为粒度进行定时提前的调整的，并且一个TAG对应一个服务小区。这种以服务小区为粒度配置TA的方式可能过于粗糙，导致终端设备基于TRP所属服务小区对应的TA与TRP通信时，可能依然会产生干扰。
例如，若一个服务小区包括多个TRP时，不同的TRP可能与终端设备之间的距离不同，此时，如果终端设备依然基于服务小区对应的TA向服务小区内的多个TRP发送上行信号，这可能导致上行信号到达TRP之后依然存在干扰。
因此，为了避免上述问题，本申请实施例提供一种以TRP为粒度的TA配置方式，如此不同的TRP可以具有各自的TA，有助于降低终端设备与TRP进行通信时产生的干扰。然而，在这种以TRP为粒度的TA配置方式下，当服务小区中的某一个TRP(下文称“第一TRP”)的TA失效后，并没有规范终端设备的行为，可能导致终端设备和网络设备的理解不一致，无法进行正常通信。
因此，为了避免上述问题，本申请实施例提供了一种通信方法，有助于规范终端设备的行为，以提高终端设备与网络设备通信的成功率。下文结合图6介绍本申请实施例的通信方法。图6所示的通信方法包括步骤S610。
在步骤S610中，在第一TRP的TA无效的情况下，终端设备执行操作1和/或操作2。
如上文介绍，在一些实现方式中，第一TRP的TA可以由TA定时器维护，因此，第一TRP的TA无效可以理解为，第一TRP的TA对应的TA定时器超时。
需要说明的是，TA定时器维护的TA是以TRP为粒度配置的。在一些实现方式中，TA定时器可以是上文中介绍的与TAG关联的定时器(用“timeAlignmentTimer”表示)，此时，TAG可以关联一个或多个TRP。或者说，上述情况下，以TRP为粒度的TA是通过TAG指示的。如此，便可以获知TA定时器维护哪个TRP的TA。当然，在本申请实施例中，上述TA定时器还可以是新的定时器，本申请实施例对此不作限定。
上述操作1可以包括恢复第一TRP的TA。相应地，若第一TRP的TA被恢复为有效TA后，终端设备可以基于有效的TA与第一TRP通信。或者说，终端设备可以基于有效的TA向第一TRP发送上行数据。
如上文所述，第一TRP的TA的有效性可以通过TA定时器维护，因此，上述恢复第一TRP的TA可以包括重启或启动维护第一TRP的TA的TA定时器。
在一些实现方式中，终端设备可以根据第一信息启动或重启TA定时器，其中，第一信息用于指示第一TRP的TA。当TA定时器被启动或重启之后，TA定时器维护的第一TRP的TA为有效。第一信息例如可以承载于MAC协议数据单元(protocol data unit，PDU)，(例如，MAC CE、MAC RAR等等)或DCI中。
需要说明的是，上述终端设备根据第一信息启动或者重启TA定时器，可以包括，终端设备收到第一信息时，启动或重启TA定时器。或者说，终端设备接收第一信息可以作为启动或重启TA定时器的触发条件。相应地，在终端设备接收到第一信息后，可以应用第一信息中指示的TA作为第一TRP的TA。
上述操作2可以包括基于第二TRP的TA与第二TRP进行通信。例如，终端设备可以通过第二TRP的上行资源发送第一上行数据。又例如，终端设备可以接收第二TRP发送的下行数据。
其中，第二TRP可以与第一TRP属于相同的服务小区，且第二TRP的TA有效。在一些实现方式中，第二TRP的TA有效可以理解为第二TRP的TA对应的TA定时器未超时。
在本申请实施例中，在第一TRP的TA无效的情况下，规定了终端设备可以执行上述操作1和/或操作2，有助于提高终端设备与网络设备通信的成功率。
需要说明的是，终端设备在执行上述操作1和/或操作2时，相应地，网络设备也执行上述操作1和/或操作2。其中，网络设备可以是第二TRP或第一TRP。
下文以终端设备执行操作1或操作2为例，分别结合实施例1和实施例2介绍本申请实施例的通信方法。
实施例1：终端设备执行操作1
在一些实现方式中，终端设备可以通过随机接入过程恢复第一TRP的TA。其中，随机接入过程可以网络设备触发的，也可以是由终端设备触发的。下文分别以两种随机接入过程为例，介绍本申请实施例中恢复第一TRP的TA的方法。
以网络设备触发的随机接入流程为例，由于网络设备与终端设备关于TA定时器的维护是同步的， 当终端设备中维护第一TRP的TA的TA定时器超时后，网络设备维护的第一TRP的TA的TA定时器也超时。此时，网络设备可以通过触发随机接入流程来恢复维护第一TRP的TA的TA定时器。
在一些实现方式中，网络设备可以通过向终端设备发送PDCCH命令来触发随机接入过程。其中，网络设备在触发随机接入过程的同时，还可以指示终端设备针对第一TRP发起随机接入过程。
网络设备指示终端设备针对第一TRP发起随机接入过程的方式有很多种，本申请实施例对此不作限定，在一些实现方式中，网络设备可以隐示的方式向终端设备指示针对第一TRP发起随机接入过程。例如，当用于随机接入过程的不同资源对应不同的TRP时，网络设备可以通过向终端设备指示第一TRP对应的用于发起随机接入过程的资源，来指示终端设备针对第一TRP发起随机接入过程。
在另一些实现方式中，网络设备可以显示的方式向终端设备指示针对第一TRP发起随机接入过程。例如，网络设备可以通过随机接入过程的资源的资源指示信息，来指示终端设备针对第一TRP发起随机接入过程，其中，资源指示信息可以携带第一TRP的指示信息。例如，在网络设备触发随机接入过程的情况下，网络设备可以向终端设备发送触发指示，以触发终端设备的随机接入过程，其中，触发指示中可以携带资源指示信息，并指示第一TRP。
上述第一TRP的指示信息可以第一TRP的标识，其中第一TRP的标识例如可以是“CORSETPollIndex”。当然，在本申请实施例中，也可以通过其他信息来标识TRP，例如，参考信号集合(例如，SRS资源集合)或者TRP索引，本申请实施例对此不作限定。
需要说明的是，上述用于随机接入的资源可以是在4步随机接入过程中，传输消息1(msg1，或者称“前导码”)所使用的资源。当然，上述用于随机接入的资源还可以是在2步随机接入过程中，传输消息A(msgA)所使用的资源。其中，资源可以是时域资源、频域资源或码域资源中的一种或多种。例如，可以通过前导码(preamble)来区分不同的TRP，或者，可以通过不同的随机接入信道机会(random access channel occasion，RO)来区分不同的TRP。
在本申请实施例中，当第一TRP的TA失效后，网络设备可以直接触发随机接入过程。当然，当第一TRP的TA失效后，网络设备还可以在满足第一条件的情况下触发随机接入过程。其中，第一条件包括以下一种或多种：网络设备有待发送下行信息；网络设备期待通过第一TRP与终端设备通信。其中，网络设备期待通过第一TRP与终端设备通信可以包括网络设备期待通过第一TRP接收终端设备发送的上行数据。
以终端设备触发的随机接入过程为例。当终端设备中维护第一TRP的TA的TA定时器超时后，终端设备可以通过触发随机接入流程来恢复维护第一TRP的TA的TA定时器。
在终端设备触发随机接入的过程中，可以告知网络设备该随机接入流程是针对第一TRP发起的，其告知方式有很多种，本申请实施例对此不作限定，例如，当用于随机接入过程的不同资源对应不同的TRP时，终端设备可以利用第一TRP对应的用于发起随机接入过程的资源，来发起随机接入过程。相应地，网络设备可以基于终端设备发起随机接入过程使用的资源，确定终端设备触发的随机接入过程是针对第一TRP的。
需要说明的是，上述用于随机接入的资源可以是在4步随机接入过程中，传输消息1(msg1，或者称“前导码”)所使用的资源。当然，上述用于随机接入的资源还可以是在2步随机接入过程中，传输消息A(msgA)所使用的资源。其中，资源可以是时域资源、频域资源或码域资源中的一种或多种。例如，可以通过前导码(preamble)来区分不同的TRP，或者，可以通过不同的随机接入信道机会(random access channel occasion，RO)来区分不同的TRP。
在本申请实施例中，当第一TRP的TA失效后，终端设备可以直接触发随机接入过程。当然，当第一TRP的TA失效后，终端设备还可以在满足第二条件的情况下触发随机接入过程。其中，第二条件可以包括终端设备有第二上行数据到达。或者说，第二条件包括第二上行数据到达，且终端设备处于上行失步状态。
在一些实现方式中，第二上行数据包括以下一种或多种：传输第二上行数据的逻辑信道或数据无线承载(data radio bearer，DRB)关联第一TRP；分组数据汇聚协议(packet data convergence protocol，PDCP)层和/或无线链路层控制协议(radio link control，RLC)层中的待传输数据；混合自动重传请求(hybrid automatic repeat request，HARQ)缓冲器中待传输的数据；SR或缓存状态报告(buffer status reporting，BSR)关联的数据；待传输的PUCCH。
上述PDCP层和/或RLC层中的待传输数据可以包括以下的至少一种：PDCP协议数据单元(protocol data unit，PDU),PDCP SDU，RLC PDU，RLC SDU。其中，PDU例如可以包括control PDU，SDU例如可以包括control SDU。
上述待传输的PUCCH例如可以包括调度请求(scheduling request，SR)，HARQ反馈，信道状态信息(channel state information，CSI)等。
上述HARQ缓冲器中待传输的数据例如可以包括待新传的数据，或者待重传的数据。
上文介绍了恢复第一TRP的TA的方法，下文介绍本申请实施例中可以恢复第一TRP的TA的条件(又称“第三条件”)。需要说明的是，在本申请实施例中，当第一TRP的TA失效后，可以直接执行恢复第一TRP的TA的操作。当然，也可以在满足第三条件的情况下执行恢复第一TRP的TA操作。
在一些实现方式中，上述第三条件可以包括以下一种或多种：网络设备为终端设备调度第一TRP的上行资源；服务小区支持(或者说配置)重复传输；服务小区内全部TRP的TA无效。
若第三条件包括网络设备为终端设备调度第一TRP的上行资源，此时，终端设备可以执行恢复第一TRP的TA的操作，以便通过第一TRP的上行资源向网络设备发送上行数据(例如，PUSCH)。也就是说，若终端设备当前无法判断待传输的数据要发往哪个TRP时，终端设备可以等待网络设备的调度信息(例如，下行控制信息(downlink control information，DCI))，若调度信息为终端设备调度第一TRP的上行资源，那么终端设备可以先恢复第一TRP的TA，然后基于调度信息指示的上行资源进行上行传输。
需要说明的是，上述调度信息可以是由终端设备通过SR所请求的，当然，上述调度信息也可以是网络设备自主发送的，本申请实施例对此不作限定。若上述调度信息是由终端设备发送SR所请求的，终端设备发送的SR的资源(例如，PUCCH资源)可以与TRP关联，不同的TRP可以关联不同的资源。也即是说，当终端设备使用第一TRP对应的资源发送SR时，网络设备可以基于SR使用的资源，确定终端设备所请求的上行资源是第一TRP的上行资源，相应地，网络设备可以为终端设备调度第一TRP的上行资源。
举例来说，在服务小区中，TRP1的SR可以关联TRP2的PUCCH资源。若TRP1的TA无效，终端设备可以触发SR，由于该SR关联的是TA有效的TRP2的PUCCH资源，这样网络设备在收到SR后，便可以获知TRP1有传输需求，且TRP1的TA需要被恢复。
如上文介绍，服务小区内的重复传输需要通过多个TRP传输相同的数据，因此，若服务小区配置了重复传输，意味着需要通过多个TRP传输相同的数据，此时，可以恢复第一TRP的TA，以便后续可以通过第一TRP以及其他TRP(例如，第二TRP)进行重复传输。
在一些实现方式中，服务小区支持重复传输可以基于以下一种或多种确定：服务小区配置了PUCCH/PUSCH重复传输；服务小区的PUCCH传输关联了多个空间关系信息(spatial relation info)；服务小区的SRS关联了多个资源集；以及服务小区的PDCCH传输或者PDSCH传输关联了多个传输配置指示状态(transmission configuration indication，TCI state)。
基于上文关于上行多TRP操作的介绍，服务小区SRS关联了多个资源集时，可以指示服务小区支持上行PUCCH/PUSCH的重复传输。
在一些场景中，服务小区的PDCCH传输或者PDSCH传输关联了多个TCI状态，和/或服务小区的PUCCH传输关联了多个空间关系信息，这种关联方式通常存在于支持重复传输的服务小区，因此，可以基于上述关联方式，确定服务小区支持重复传输。
若第三条件包括服务小区内全部TRP的TA无效，此时，终端设备可以选择恢复服务小区中的某一个TRP的TA(例如，第一TRP的TA)。
在一些实现方式中，若服务小区内全部TRP的TA无效，终端设备可以告知网络设备。例如，终端设备可以在4步随机接入过程中的消息3(msg3)中携带指示信息以指示服务小区内全部TRP的TA无效。又例如，终端设备可以在2步随机接入过程中的消息A(msgA)中携带指示信息以指示服务小区内全部TRP的TA无效。
实施例2：终端设备执行操作2
若第一TRP的TA无效，且第二TRP的TA有效，终端设备可以直接与第二TRP的通信，有助于减少终端设备接收或发送数据所需的时延。
如上文介绍，在一些场景中，终端设备可以基于第二TRP的TA，使用第二TRP的上行资源发送第一上行数据。其中，第二TRP的上行资源可以是网络设备通过配置授权(configured grant，CG)为终端设备配置的。当然，上述第二TRP的上行资源还可以是网络设备通过动态授权(dynamic grant，DG)为终端设备动态调度的。
以第二TRP的上行资源包括基于CG配置的资源为例，若上述第二TRP的上行资源是通过配置授权类型1(type 1)配置的上行资源，终端设备可以直接使用该类型的上行资源传输第一上行数据。在一些实现方式中，上述配置授权类型1的上行资源可以由RRC通过高层信令进行配置(例如，IE ConfiguredGrantConfig)，本申请实施例对此不作限定。
若上述第二TRP的上行资源是通过配置授权类型2(type 2)配置的上行资源，则在第二TRP的上行资源为激活的上行资源的情况下，终端设备可以使用该类型的上行资源传输第一上行数据。在一些实 现方式中，配置授权类型2(type 2)配置的上行资源可以由DCI进行指示激活和去激活，也即是说，配置授权类型2配置的上行资源需要的参数可以由IE ConfiguredGrantConfig进行配置，但是配置后的上行资源需要由DCI激活时才可以使用。
需要说明的是，在一些场景中，通过配置授权类型2配置的第二TRP的上行资源中，没有激活的上行资源，此时，终端设备可以通过触发SR和/或BSR流程，请求网络设备调度上行资源进行传输。若终端设备触发SR流程，终端设备发送的SR的资源(例如，PUCCH资源)可以与TRP关联，不同的TRP可以关联不同的资源。也即是说，当终端设备使用第二TRP关联的资源发送SR时，网络设备可以基于SR使用的资源，确定终端设备所请求的上行资源是第二TRP的上行资源，相应地，网络设备可以为终端设备调度第二TRP的上行资源。
在一些场景中，上述SR还可以用于向网络设备指示需要恢复第一TRP的TA。也即是说，SR可以用于指示第一TRP的TA无效且有待传输数据。举例来说，第一TRP的SR可以关联第二TRP的PUCCH资源，若第一TRP的TA无效，终端设备可以触发SR，由于该SR关联的是TA有效的第二TRP的PUCCH资源，这样网络设备收到SR后，便可以获知第一TRP有传输需求，且第一TRP的TA需要被恢复。
相反地，若终端设备发送的SR的资源(例如，PUCCH资源)可以与TRP无关，当终端设备有待传输的上行数据时，终端设备可以触发SR，响应于该SR，网络设备可以向终端设备发送调度信息，相应地，终端设备可以基于网络设备的发送的调度信息，确定进行上行传输的TRP。假设网络设备为终端设备调度第二TRP的上行资源，那么终端设备可以使用第二TRP的上行资源进行上行传输。
需要说明的是，本申请实施例中触发SR的条件可以是基于目前协议规定的SR的触发条件，当然，触发SR的条件还可以是未来协议中引入的条件，本申请实施例对此不做限定。
以第二TRP的上行资源包括基于DG配置的资源为例，若终端设备有基于DG配置的第二TRP的上行资源可用，那么终端设备可以直接使用该上行资源传输第一上行数据。在一些实现方式中，网络设备可以通过DCI为终端设备动态配置第二TRP的上行资源。相应地，终端设备可以基于该动态配置的上行资源生成上行数据包(例如，MAC PDU)，并将该数据包递交给低层(例如，物理层)。
若对于终端设备而言，第二TRP没有可用的上行资源(包括CG配置的上行资源和DG配置的上行资源)，此时，终端设备可以通过触发SR和/或BSR流程，请求网络设备调度上行资源进行传输。若终端设备触发SR流程，终端设备发送的SR的资源(例如，PUCCH资源)可以与TRP关联，不同的TRP可以关联不同的资源。也即是说，当终端设备使用第二TRP对应的资源发送SR时，网络设备可以基于SR使用的资源，确定终端设备所请求的上行资源是第二TRP的上行资源，相应地，网络设备可以为终端设备调度第二TRP的上行资源。
在一些场景中，上述SR还可以用于向网络设备指示需要恢复第一TRP的TA。也即是说，SR可以用于指示第一TRP的TA无效且有待传输数据。举例来说，第一TRP的SR可以关联第二TRP的PUCCH资源，若第一TRP的TA无效，终端设备可以触发SR，由于该SR关联的是TA有效的第二TRP的PUCCH资源，这样网络设备收到SR后，便可以获知第一TRP有传输需求，且第一TRP的TA需要被恢复。相应地，网络设备可以为终端设备调度第一TRP的上行资源。
在本申请实施例中还提供了当第一TRP的TA失效后，终端设备可以执行的操作(又称“目标操作”)，以及针对那些对象来执行操作。下文先介绍终端设备可以执行的操作。
在一些实现方式中，当第一TRP的TA失效后，则目标操作被触发。其中，目标操作包括以下操作中的一种或多种：清空混合自动重传请求(hybrid automatic repeat request，HARQ)缓冲器；通知无线资源控制(Radio Resource Control，RRC)释放上行资源(其中，上行资源例如可以包括PUCCH，SRS，小区组(cell group，CG)，PUSCH以及半静态调度(semi-persistent scheduling，SPS)等)；维护定时提前绝对值；发起随机接入流程；以及通过TA有效的TRP重传HARQ缓冲器中的数据。当然，在另一些实现方式中，当第一TRP的TA失效后，终端设备也可以不执行上述目标操作。
在一些场景中(例如，服务小区配置了mTRP)，当第一TRP的TA失效，此时，服务小区中可能还有TRP的TA有效，因此，可以通过TA有效的TRP重传HARQ缓冲器中的数据，如此，终端设备可以不执行任何目标操作。
需要说明的是，上述目标操作还可以包括现有协议中规定的一种或多种操作，例如，可以包括以下操作的一种或多种：清除已配置的下行链路分配和上行链路授权；清除用于半静态CSI报告的PUSCH资源；将所有运行的TA定时器视为过期。
在不同的场景中，上述目标操作针对的对象可以不同。在一些实现方式，若基于TAG指示TA的方式中，TAG可以关联一个或多个TRP的TA，则目标操作针对以下对象中的一种或多种：终端设备的全部服务小区；一个或多个TAG关联的TRP；以及一个或多个TAG关联的TRP所在的服务小区。
其中，终端设备的全部服务小区可以是终端设备建立连接的全部服务小区，或者说，可以是包括终端设备的服务小区列表中的全部服务小区，或者说，还可以包含与终端设备通信的全部服务小区，本申请实施例对此不作限定。
若上述目标操作针对的对象包括一个或多个TAG关联的TRP，且目标操作可以包括清空上述一个或多个TAG包括的TRP所关联的HARQ缓冲器(buffer)。例如，对于配置了多个TRP的服务小区，在服务小区中每个TRP都可以有一个HARQ实体，并且每个HARQ实体中的HARQ进程可以属于不同TRP的，此时，上述目标操作可以包括清空上述一个或多个TAG包括的TRP所关联的HARQ进程对应的HARQ缓冲器。
又例如，对于配置了多个TRP的服务小区，每个服务小区可以有一个HARQ实体，该HARQ实体中的HARQ进程可以被分为多个组，其中多个组关联多个TRP。此时，上述目标操作可以包括清空一个或多个TAG包括的TRP所关联的组中的HARQ进程对应的HARQ缓冲器。
若上述目标操作针对的对象包括一个或多个TAG关联的TRP，且目标操作包括通知RRC释放上行资源。通常，对于配置了多个TRP的服务小区，该服务小区中的每个TRP可以配置相应的上行资源，因此，上述目标操作可以包括通知RRC释放一个或多个TAG关联的TRP对应的上行资源。
需要说明的是，上文中的TAG可以是PTAG或STAG，本申请实施例对此不作限定。
在另一些实现方式中，当网络设备直接指示TRP的TA，则目标操作针对以下对象中的一种或多种：终端设备的全部服务小区；该TRP；以及该TRP所在的服务小区。
当上述目标操作针对的对象包括TRP，且目标操作可以包括清空TRP所关联的HARQ缓冲器(buffer)。例如，对于配置了多个TRP的服务小区，在服务小区中每个TRP都可以有一个HARQ实体，并且每个HARQ实体中的HARQ进程可以属于不同TRP的，此时，上述目标操作可以包括清空上述TRP所关联的HARQ进程对应的HARQ缓冲器。
又例如，对于配置了多个TRP的服务小区，每个服务小区可以有一个HARQ实体，该HARQ实体中的HARQ进程可以被分为多个组，其中多个组关联多个TRP。此时，上述目标操作可以包括清空TRP所关联的组中的HARQ进程对应的HARQ缓冲器。
若上述目标操作针对的对象包括TRP，且目标操作包括通知RRC释放上行资源。通常，对于配置了多个TRP的服务小区，该服务小区中的每个TRP可以配置相应的上行资源，因此，上述目标操作可以包括通知RRC释放该TRP对应的上行资源。
需要说明的是，上文中的TAG可以是PTAG或STAG，本申请实施例对此不作限定。
基于上文介绍的目标操作可知，在一些情况下，当第一TRP的TA失效后，终端设备可能不会执行任何目标操作(例如，释放第一TRP的上行资源)，此时，由于维护第一TRP的TA有效性的定时器通常在MAC层维护，低层(例如，物理层)可能无法获知第一TRP的TA失效，因此，可能继续向第一TRP发送上行数据，导致通信失败。
因此，为了避免上述问题，可以在第一TRP的TA无效的情况下，终端设备的MAC层可以向低层发送第一指示信息，第一指示信息用于指示第一TRP的TA无效。即，在第一TRP的TA无效，且第一TRP的上行资源未被释放的情况下，MAC层向MAC的低层发送第一指示信息。相应地，在恢复第一TRP的TA有效后，MAC层也可以向低层发送第二指示信息，第二指示信息用于指示第一TRP的TA有效。
在另一些情况下，当第一TRP的TA失效后，若终端设备执行了目标操作(例如，释放第一TRP的上行资源)，此时，低层即使不知道第一TRP的TA无效，但由于第一TRP的上行资源被释放，低层也不会在向第一TRP发送上行数据了。因此，为了减少传输第一指示信息占用的资源，此时，MAC层可以不传输第一指示信息。当然，在本申请实施例中，无论终端设备是否执行目标操作，MAC层都可以发送第一指示信息。本申请实施例对此不作限定。
上文结合图1至图6，详细描述了本申请的方法实施例，下面结合图7至图9，详细描述本申请的装置实施例。应理解，方法实施例的描述与装置实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图7是本申请实施例的终端设备的示意图，图7所示的终端设备包括：处理单元710。
在第一传输点TRP的定时提前TA无效的情况下，处理单元710，用于执行以下操作中的一种或多种：基于第二TRP的TA与所述第二TRP通信；恢复所述第一TRP的TA为有效，其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
在一种可能的实现方式中，所述恢复第一TRP的TA为有效包括通过随机接入过程恢复所述第一TRP的TA为有效。
在一种可能的实现方式中，所述随机接入过程是由网络设备或所述终端设备触发的。
在一种可能的实现方式中，在满足第一条件的情况下，所述随机接入过程由所述网络设备触发，其中，所述第一条件包括以下一种或多种：所述网络设备有待发送下行信息；所述网络设备期待通过所述第一TRP与所述终端设备通信。
在一种可能的实现方式中，在满足第二条件的情况下，所述随机接入过程由所述终端设备触发，其中，所述第二条件包括所述终端设备有第二上行数据到达。
在一种可能的实现方式中，所述第二上行数据包括以下一种或多种：传输所述第二上行数据的逻辑信道或数据无线承载DRB关联所述第一TRP；分组数据汇聚协议PDCP层和/或无线链路层控制协议RLC层中的待传输数据；混合自动重传请求HARQ缓冲器中待传输的数据；调度请求SR或缓冲状态报告BSR关联的数据；待传输的物理上行链路控制信道PUCCH。
在一种可能的实现方式中，在所述第一TRP的TA无效且满足第三条件的情况下，所述终端设备恢复所述第一TRP的TA，其中，所述第三条件包括以下一种或多种：所述网络设备为所述终端设备调度所述第一TRP的上行资源；所述服务小区支持重复传输；所述服务小区内全部TRP的TA无效。
在一种可能的实现方式中，所述服务小区支持重复传输包括以下一种或多种：所述服务小区配置了物理上行链路共享信道PUSCH重复传输；所述服务小区的PUCCH传输关联了多个空间关系信息；所述服务小区的信道探测参考信号SRS关联了多个资源集；以及所述服务小区的PDCCH传输或者PDSCH传输关联了多个传输配置指示TCI状态。
在一种可能的实现方式中，所述基于第二TRP的TA与所述第二TRP通信，包括基于所述第二TRP的TA向所述第二TRP发送第一上行数据，传输所述第一上行数据的所述第二TRP的上行资源包括以下一种或多种：配置授权的配置授权类型1配置的上行资源；配置授权的配置授权类型2配置的上行资源中激活的上行资源；基于动态授权调度的上行资源；通过SR所请求的上行资源，所述SR使用的SR资源与所述第二TRP关联。
在一种可能的实现方式中，在所述第一TRP的TA无效的情况下，所述终端设备还包括：发送单元，用于通过媒体接入控制MAC层向所述MAC的低层发送第一指示信息，所述第一指示信息用于指示所述第一TRP的TA无效。
在一种可能的实现方式中，所述发送单元，还用于在所述第一TRP的TA无效，且所述第一TRP的上行资源未被释放的情况下，通过所述MAC层向所述MAC的低层发送所述第一指示信息。
图8是本申请实施例的网络设备的示意图，图8所示的网络设备800包括：处理单元810。
在第一传输点TRP的定时提前TA无效的情况下，处理单元810，执行以下操作中的一种或多种：基于第二TRP的TA与终端设备通信；恢复所述第一TRP的TA为有效，其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
在一种可能的实现方式中，所述网络设备恢复第一TRP的TA为有效包括所述网络设备通过随机接入过程恢复所述第一TRP的TA为有效。
在一种可能的实现方式中，所述随机接入过程是由所述网络设备或所述终端设备触发的。
在一种可能的实现方式中，在满足第一条件的情况下，所述随机接入过程由所述网络设备触发，其中，所述第一条件包括以下一种或多种：所述网络设备有待发送下行信息；所述网络设备期待通过所述第一TRP与所述终端设备通信。
在一种可能的实现方式中，在满足第二条件的情况下，所述随机接入过程由所述终端设备触发，其中，所述第二条件包括所述终端设备有第二上行数据到达。
在一种可能的实现方式中，所述第二上行数据包括以下一种或多种：传输所述第二上行数据的逻辑信道或数据无线承载DRB关联所述第一TRP；分组数据汇聚协议PDCP层和/或RLC层中的待传输数据；混合自动重传请求HARQ缓冲器中待传输的数据；调度请求SR或缓冲状态报告BSR关联的数据；待传输的物理上行链路控制信道PUCCH。
在一种可能的实现方式中，在所述第一TRP的TA无效且满足第三条件的情况下，所述终端设备恢复所述第一TRP的TA，其中，所述第三条件包括以下一种或多种：所述网络设备为所述终端设备调度所述第一TRP的上行资源；所述服务小区支持重复传输；所述服务小区内全部TRP的TA无效。
在一种可能的实现方式中，所述服务小区支持重复传输包括以下一种或多种：所述服务小区配置了物理上行链路共享信道PUSCH重复传输；所述服务小区的PUCCH传输关联了多个空间关系信息；所述服务小区的信道探测参考信号SRS关联了多个资源集；以及所述服务小区的PDCCH传输或者PDSCH传输关联了多个传输配置指示TCI状态。
在一种可能的实现方式中，所述基于第二TRP的TA与所述终端设备通信，包括基于所述第二TRP的TA接收所述终端设备发送的第一上行数据，其中，传输所述第一上行数据的所述第二TRP的上行资源包括以下一种或多种：配置授权的配置授权类型1配置的上行资源；配置授权的配置授权类型2配 置的上行资源中激活的上行资源；基于动态授权调度的上行资源；通过SR所请求的上行资源，所述SR使用的SR资源与所述第二TRP关联。
在可选的实施例中，所述处理单元710可以为处理器910。终端设备700还可以包括收发器930和存储器920，具体如图9所示。
在可选的实施例中，所述处理单元810可以为处理器910。网络设备800还可以包括收发器930和存储器920，具体如图9所示。
图9是本申请实施例的通信装置的示意性结构图。图9中的虚线表示该单元或模块为可选的。该装置900可用于实现上述方法实施例中描述的方法。装置900可以是芯片、终端设备或网络设备。
装置900可以包括一个或多个处理器910。该处理器910可支持装置900实现前文方法实施例所描述的方法。该处理器910可以是通用处理器或者专用处理器。例如，该处理器可以为中央处理单元(central processing unit，CPU)。或者，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
装置900还可以包括一个或多个存储器920。存储器920上存储有程序，该程序可以被处理器910执行，使得处理器910执行前文方法实施例所描述的方法。存储器920可以独立于处理器910也可以集成在处理器910中。
装置900还可以包括收发器930。处理器910可以通过收发器930与其他设备或芯片进行通信。例如，处理器910可以通过收发器930与其他设备或芯片进行数据收发。
本申请实施例还提供一种计算机可读存储介质，用于存储程序。该计算机可读存储介质可应用于本申请实施例提供的终端或网络设备中，并且该程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
本申请实施例还提供一种计算机程序产品。该计算机程序产品包括程序。该计算机程序产品可应用于本申请实施例提供的终端或网络设备中，并且该程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
本申请实施例还提供一种计算机程序。该计算机程序可应用于本申请实施例提供的终端或网络设备中，并且该计算机程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
应理解，本申请中术语“系统”和“网络”可以被可互换使用。另外，本申请使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。本申请的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。
在本申请的实施例中，提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在本申请实施例中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，“预定义”或“预配置”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
本申请实施例中，所述“协议”可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
本申请实施例中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以 是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够读取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital video disc，DVD))或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (47)

  1. 一种通信方法，其特征在于，包括：
    在第一传输点TRP的定时提前TA无效的情况下，终端设备执行以下操作中的一种或多种：
    基于第二TRP的TA与所述第二TRP通信；
    恢复所述第一TRP的所述TA为有效，
    其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备恢复第一TRP的TA为有效包括所述终端设备通过随机接入过程恢复所述第一TRP的TA为有效。
  3. 根据权利要求2所述的方法，其特征在于，所述随机接入过程是由网络设备或所述终端设备触发的。
  4. 根据权利要求3所述的方法，其特征在于，在满足第一条件的情况下，所述随机接入过程由所述网络设备触发，其中，所述第一条件包括以下一种或多种：
    所述网络设备有待发送下行信息；
    所述网络设备期待通过所述第一TRP与所述终端设备通信。
  5. 根据权利要求3所述的方法，其特征在于，在满足第二条件的情况下，所述随机接入过程由所述终端设备触发，其中，所述第二条件包括所述终端设备有第二上行数据到达。
  6. 根据权利要求5所述的方法，其特征在于，所述第二上行数据包括以下一种或多种：
    传输所述第二上行数据的逻辑信道或数据无线承载DRB关联所述第一TRP；
    分组数据汇聚协议PDCP层和/或无线链路层控制协议RLC层中的待传输数据；
    混合自动重传请求HARQ缓冲器中待传输的数据；
    调度请求SR或缓冲状态报告BSR关联的数据；
    待传输的物理上行链路控制信道PUCCH。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，在所述第一TRP的TA无效且满足第三条件的情况下，所述终端设备恢复所述第一TRP的TA，其中，所述第三条件包括以下一种或多种：
    所述网络设备为所述终端设备调度所述第一TRP的上行资源；
    所述服务小区支持重复传输；
    所述服务小区内全部TRP的TA无效。
  8. 根据权利要求7所述的方法，其特征在于，所述服务小区支持重复传输包括以下一种或多种：
    所述服务小区配置了物理上行链路共享信道PUSCH重复传输；
    所述服务小区的PUCCH传输关联了多个空间关系信息；
    所述服务小区的信道探测参考信号SRS关联了多个资源集；以及
    所述服务小区的PDCCH传输或者PDSCH传输关联了多个传输配置指示TCI状态。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述基于第二TRP的TA与所述第二TRP通信，包括基于所述第二TRP的TA向所述第二TRP发送第一上行数据，
    传输所述第一上行数据的所述第二TRP的上行资源包括以下一种或多种：
    配置授权的配置授权类型1配置的上行资源；
    配置授权的配置授权类型2配置的上行资源中激活的上行资源；
    基于动态授权调度的上行资源；
    通过SR所请求的上行资源，所述SR使用的SR资源与所述第二TRP关联。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，在所述第一TRP的TA无效的情况下，所述方法还包括：
    所述终端设备的媒体接入控制MAC层向所述MAC的低层发送第一指示信息，所述第一指示信息用于指示所述第一TRP的TA无效。
  11. 根据权利要求10所述的方法，其特征在于，所述终端设备的MAC层向所述MAC的低层发送第一指示信息，包括：
    在所述第一TRP的TA无效，且所述第一TRP的上行资源未被释放的情况下，所述MAC层向所述MAC的低层发送所述第一指示信息。
  12. 一种通信方法，其特征在于，包括：
    在第一传输点TRP的定时提前TA无效的情况下，网络设备执行以下操作中的一种或多种：
    基于第二TRP的TA与终端设备通信；
    恢复所述第一TRP的所述TA为有效，
    其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
  13. 根据权利要求12所述的方法，其特征在于，所述网络设备恢复第一TRP的TA为有效包括所述网络设备通过随机接入过程恢复所述第一TRP的TA为有效。
  14. 根据权利要求13所述的方法，其特征在于，所述随机接入过程是由所述网络设备或所述终端设备触发的。
  15. 根据权利要求14所述的方法，其特征在于，在满足第一条件的情况下，所述随机接入过程由所述网络设备触发，其中，所述第一条件包括以下一种或多种：
    所述网络设备有待发送下行信息；
    所述网络设备期待通过所述第一TRP与所述终端设备通信。
  16. 根据权利要求14所述的方法，其特征在于，在满足第二条件的情况下，所述随机接入过程由所述终端设备触发，其中，所述第二条件包括所述终端设备有第二上行数据到达。
  17. 根据权利要求16所述的方法，其特征在于，所述第二上行数据包括以下一种或多种：
    传输所述第二上行数据的逻辑信道或数据无线承载DRB关联所述第一TRP；
    分组数据汇聚协议PDCP层和/或RLC层中的待传输数据；
    混合自动重传请求HARQ缓冲器中待传输的数据；
    调度请求SR或缓冲状态报告BSR关联的数据；
    待传输的物理上行链路控制信道PUCCH。
  18. 根据权利要求12-17中任一项所述的方法，其特征在于，在所述第一TRP的TA无效且满足第三条件的情况下，所述终端设备恢复所述第一TRP的TA，其中，所述第三条件包括以下一种或多种：
    所述网络设备为所述终端设备调度所述第一TRP的上行资源；
    所述服务小区支持重复传输；
    所述服务小区内全部TRP的TA无效。
  19. 根据权利要求18所述的方法，其特征在于，所述服务小区支持重复传输包括以下一种或多种：
    所述服务小区配置了物理上行链路共享信道PUSCH重复传输；
    所述服务小区的PUCCH传输关联了多个空间关系信息；
    所述服务小区的信道探测参考信号SRS关联了多个资源集；以及
    所述服务小区的PDCCH传输或者PDSCH传输关联了多个传输配置指示TCI状态。
  20. 根据权利要求12-19中任一项所述的方法，其特征在于，所述基于第二TRP的TA与所述终端设备通信，包括基于所述第二TRP的TA接收所述终端设备发送的第一上行数据，其中，传输所述第一上行数据的所述第二TRP的上行资源包括以下一种或多种：
    配置授权的配置授权类型1配置的上行资源；
    配置授权的配置授权类型2配置的上行资源中激活的上行资源；
    基于动态授权调度的上行资源；
    通过SR所请求的上行资源，所述SR使用的SR资源与所述第二TRP关联。
  21. 一种终端设备，其特征在于，包括：
    在第一传输点TRP的定时提前TA无效的情况下，处理单元，执行以下操作中的一种或多种：
    基于第二TRP的TA与所述第二TRP通信；
    恢复所述第一TRP的所述TA为有效，
    其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
  22. 根据权利要求21所述的终端设备，其特征在于，所述恢复第一TRP的TA为有效包括通过随机接入过程恢复所述第一TRP的TA为有效。
  23. 根据权利要求22所述的终端设备，其特征在于，所述随机接入过程是由网络设备或所述终端设备触发的。
  24. 根据权利要求23所述的终端设备，其特征在于，在满足第一条件的情况下，所述随机接入过程由所述网络设备触发，其中，所述第一条件包括以下一种或多种：
    所述网络设备有待发送下行信息；
    所述网络设备期待通过所述第一TRP与所述终端设备通信。
  25. 根据权利要求23所述的终端设备，其特征在于，在满足第二条件的情况下，所述随机接入过程由所述终端设备触发，其中，所述第二条件包括所述终端设备有第二上行数据到达。
  26. 根据权利要求25所述的终端设备，其特征在于，所述第二上行数据包括以下一种或多种：
    传输所述第二上行数据的逻辑信道或数据无线承载DRB关联所述第一TRP；
    分组数据汇聚协议PDCP层和/或无线链路层控制协议RLC层中的待传输数据；
    混合自动重传请求HARQ缓冲器中待传输的数据；
    调度请求SR或缓冲状态报告BSR关联的数据；
    待传输的物理上行链路控制信道PUCCH。
  27. 根据权利要求21-26中任一项所述的终端设备，其特征在于，在所述第一TRP的TA无效且满足第三条件的情况下，所述终端设备恢复所述第一TRP的TA，其中，所述第三条件包括以下一种或多种：
    所述网络设备为所述终端设备调度所述第一TRP的上行资源；
    所述服务小区支持重复传输；
    所述服务小区内全部TRP的TA无效。
  28. 根据权利要求27所述的终端设备，其特征在于，所述服务小区支持重复传输包括以下一种或多种：
    所述服务小区配置了物理上行链路共享信道PUSCH重复传输；
    所述服务小区的PUCCH传输关联了多个空间关系信息；
    所述服务小区的信道探测参考信号SRS关联了多个资源集；以及
    所述服务小区的PDCCH传输或者PDSCH传输关联了多个传输配置指示TCI状态。
  29. 根据权利要求21-28中任一项所述的终端设备，其特征在于，所述基于第二TRP的TA与所述第二TRP通信，包括基于所述第二TRP的TA向所述第二TRP发送第一上行数据，
    传输所述第一上行数据的所述第二TRP的上行资源包括以下一种或多种：
    配置授权的配置授权类型1配置的上行资源；
    配置授权的配置授权类型2配置的上行资源中激活的上行资源；
    基于动态授权调度的上行资源；
    通过SR所请求的上行资源，所述SR使用的SR资源与所述第二TRP关联。
  30. 根据权利要求21-29中任一项所述的终端设备，其特征在于，在所述第一TRP的TA无效的情况下，所述终端设备还包括：
    发送单元，用于通过媒体接入控制MAC层向所述MAC的低层发送第一指示信息，所述第一指示信息用于指示所述第一TRP的TA无效。
  31. 根据权利要求30所述的终端设备，其特征在于，所述发送单元，还用于：
    在所述第一TRP的TA无效，且所述第一TRP的上行资源未被释放的情况下，通过所述MAC层向所述MAC的低层发送所述第一指示信息。
  32. 一种网络设备，其特征在于，包括：
    在第一传输点TRP的定时提前TA无效的情况下，处理单元，执行以下操作中的一种或多种：
    基于第二TRP的TA与终端设备通信；
    恢复所述第一TRP的所述TA为有效，
    其中，所述第二TRP的TA有效，且所述第一TRP与所述第二TRP属于所述终端设备的一个服务小区。
  33. 根据权利要求32所述的网络设备，其特征在于，所述网络设备恢复第一TRP的TA为有效包括所述网络设备通过随机接入过程恢复所述第一TRP的TA为有效。
  34. 根据权利要求33所述的网络设备，其特征在于，所述随机接入过程是由所述网络设备或所述终端设备触发的。
  35. 根据权利要求34所述的网络设备，其特征在于，在满足第一条件的情况下，所述随机接入过程由所述网络设备触发，其中，所述第一条件包括以下一种或多种：
    所述网络设备有待发送下行信息；
    所述网络设备期待通过所述第一TRP与所述终端设备通信。
  36. 根据权利要求34所述的网络设备，其特征在于，在满足第二条件的情况下，所述随机接入过程由所述终端设备触发，其中，所述第二条件包括所述终端设备有第二上行数据到达。
  37. 根据权利要求36所述的网络设备，其特征在于，所述第二上行数据包括以下一种或多种：
    传输所述第二上行数据的逻辑信道或数据无线承载DRB关联所述第一TRP；
    分组数据汇聚协议PDCP层和/或RLC层中的待传输数据；
    混合自动重传请求HARQ缓冲器中待传输的数据；
    调度请求SR或缓冲状态报告BSR关联的数据；
    待传输的物理上行链路控制信道PUCCH。
  38. 根据权利要求32-37中任一项所述的网络设备，其特征在于，在所述第一TRP的TA无效且满足第三条件的情况下，所述终端设备恢复所述第一TRP的TA，其中，所述第三条件包括以下一种或多种：
    所述网络设备为所述终端设备调度所述第一TRP的上行资源；
    所述服务小区支持重复传输；
    所述服务小区内全部TRP的TA无效。
  39. 根据权利要求38所述的网络设备，其特征在于，所述服务小区支持重复传输包括以下一种或多种：
    所述服务小区配置了物理上行链路共享信道PUSCH重复传输；
    所述服务小区的PUCCH传输关联了多个空间关系信息；
    所述服务小区的信道探测参考信号SRS关联了多个资源集；以及
    所述服务小区的PDCCH传输或者PDSCH传输关联了多个传输配置指示TCI状态。
  40. 根据权利要求32-39中任一项所述的网络设备，其特征在于，所述基于第二TRP的TA与所述终端设备通信，包括基于所述第二TRP的TA接收所述终端设备发送的第一上行数据，其中，传输所述第一上行数据的所述第二TRP的上行资源包括以下一种或多种：
    配置授权的配置授权类型1配置的上行资源；
    配置授权的配置授权类型2配置的上行资源中激活的上行资源；
    基于动态授权调度的上行资源；
    通过SR所请求的上行资源，所述SR使用的SR资源与所述第二TRP关联。
  41. 一种终端设备，其特征在于，包括收发器、存储器和处理器，所述存储器用于存储程序，所述处理器用于调用所述存储器中的程序，以通过所述收发器收发信息，以使所述终端执行如权利要求1-12中任一项所述的方法。
  42. 一种网络设备，其特征在于，包括存储器和处理器，所述存储器用于存储程序，所述处理器用于调用所述存储器中的程序，以通过所述收发器收发信息，以使所述网络设备执行如权利要求13-20中任一项所述的方法。
  43. 一种装置，其特征在于，包括处理器，用于从存储器中调用程序，以使所述装置执行如权利要求1-20中任一项所述的方法。
  44. 一种芯片，其特征在于，包括处理器，用于从存储器调用程序，使得安装有所述芯片的设备执行如权利要求1-20中任一项所述的方法。
  45. 一种计算机可读存储介质，其特征在于，其上存储有程序，所述程序使得计算机执行如权利要求1-20中任一项所述的方法。
  46. 一种计算机程序产品，其特征在于，包括程序，所述程序使得计算机执行如权利要求1-20中任一项所述的方法。
  47. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1-20中任一项所述的方法。
PCT/CN2022/098251 2022-06-10 2022-06-10 通信方法、终端设备及网络设备 WO2023236213A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/098251 WO2023236213A1 (zh) 2022-06-10 2022-06-10 通信方法、终端设备及网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/098251 WO2023236213A1 (zh) 2022-06-10 2022-06-10 通信方法、终端设备及网络设备

Publications (1)

Publication Number Publication Date
WO2023236213A1 true WO2023236213A1 (zh) 2023-12-14

Family

ID=89117468

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/098251 WO2023236213A1 (zh) 2022-06-10 2022-06-10 通信方法、终端设备及网络设备

Country Status (1)

Country Link
WO (1) WO2023236213A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107105496A (zh) * 2016-02-19 2017-08-29 电信科学技术研究院 一种获取、返回上行定时提前量的方法及装置、系统
US20180198665A1 (en) * 2017-01-06 2018-07-12 Asustek Computer Inc. Method and apparatus for handling ul timing asynchronism in a wireless communication system
CN110536471A (zh) * 2019-03-28 2019-12-03 中兴通讯股份有限公司 传输控制方法、装置、终端、基站、通信系统及存储介质
CN111108783A (zh) * 2017-11-03 2020-05-05 华为技术有限公司 时间提前值的管理

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107105496A (zh) * 2016-02-19 2017-08-29 电信科学技术研究院 一种获取、返回上行定时提前量的方法及装置、系统
US20180198665A1 (en) * 2017-01-06 2018-07-12 Asustek Computer Inc. Method and apparatus for handling ul timing asynchronism in a wireless communication system
CN111108783A (zh) * 2017-11-03 2020-05-05 华为技术有限公司 时间提前值的管理
CN110536471A (zh) * 2019-03-28 2019-12-03 中兴通讯股份有限公司 传输控制方法、装置、终端、基站、通信系统及存储介质

Similar Documents

Publication Publication Date Title
JP7067635B2 (ja) 無線端末、無線局、及びこれらの方法
JP6842586B2 (ja) Ｕｅ装置のための方法、ｕｅ装置、基地局、及びプロセッサ
WO2021168661A1 (zh) 信息传输方法、终端设备和网络设备
WO2022067547A1 (zh) 无线通信方法、终端设备和网络设备
US20240334359A1 (en) Method for timing advance maintenance in uplink synchronization, terminal device, and chip
CN116192337A (zh) 无线通信的方法及装置
US20220070926A1 (en) Communication control method and user equipment
US20220124824A1 (en) Method for random access and communication device
WO2024016358A1 (zh) 用于无线通信的方法、终端设备和网络设备
WO2020020352A1 (zh) 随机接入方法、终端设备和网络设备
WO2023236213A1 (zh) 通信方法、终端设备及网络设备
WO2022067614A1 (zh) 无线通信方法、终端设备和网络设备
WO2022183406A1 (zh) 传输数据信道的方法、终端设备和网络设备
WO2022141332A1 (zh) 一种通信方法及装置
WO2023236217A1 (zh) 通信方法、终端设备及网络设备
WO2023077321A1 (zh) 通信方法及终端设备
WO2022133675A1 (zh) 无线通信方法和终端设备
WO2023039811A1 (zh) 通信方法及通信装置
US20240259904A1 (en) Wireless communication method, terminal device, and network device
WO2023130467A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023019437A1 (zh) 通信方法及通信装置
WO2024174059A1 (zh) 用于侧行通信的方法、终端设备及网络设备
WO2023010459A1 (zh) 无线通信的方法、终端设备和网络设备
WO2024098212A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023050335A1 (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: 22945354

Country of ref document: EP

Kind code of ref document: A1