WO2022228519A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2022228519A1
WO2022228519A1 PCT/CN2022/089919 CN2022089919W WO2022228519A1 WO 2022228519 A1 WO2022228519 A1 WO 2022228519A1 CN 2022089919 W CN2022089919 W CN 2022089919W WO 2022228519 A1 WO2022228519 A1 WO 2022228519A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
access node
data
scheduling
scheduling information
Prior art date
Application number
PCT/CN2022/089919
Other languages
English (en)
French (fr)
Inventor
王君
吕永霞
王婷
张立清
马江镭
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22794989.8A priority Critical patent/EP4322448A1/en
Publication of WO2022228519A1 publication Critical patent/WO2022228519A1/zh
Priority to US18/492,063 priority patent/US20240049224A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/002—Transmission of channel access control information
    • H04W74/008—Transmission of channel access control information with additional processing of random access related information at receiving side
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a communication method and apparatus.
  • a long term evolution (long term evolution, LTE) system a new radio (new radio, NR) system
  • NR new radio
  • Operators need to deploy two or more formats at the same time to meet market demands.
  • the NR standard supports multi-standard dual-link (multi radio-dual connectivity, MR-DC) communication in order to split the LTE system and the NR system.
  • MR-DC multi radio-dual connectivity
  • MR-DC does not support aggregation between multiple carriers, dynamic/real-time scheduling negotiation between different carriers, and carrier aggregation features such as cross-carrier scheduling and joint uplink control information feedback, so the communication performance is poor.
  • the present application provides a communication method and device, which are used to support aggregation of carriers of different standards, implement carrier aggregation characteristics, and improve communication performance.
  • a communication method is provided.
  • the first access node determines scheduling information, where the scheduling information is used to instruct the second access node to receive data or send data resource information; the first access node sends the data to the second access node.
  • the scheduling information the second access node receives the scheduling information; the second access node determines resource information for receiving data or sending data.
  • the standard of the first access node and the standard of the second access node may be the same or different.
  • the interconnection and intercommunication of scheduling or user data can be realized between different access nodes, thereby improving communication performance.
  • the interconnection and intercommunication between access nodes of different standards can also be realized, and the interconnection and intercommunication between access nodes of different manufacturers can also be realized, so as to realize the carrier aggregation feature and further improve the communication performance.
  • the scheduling information is dynamic scheduling information, or semi-static scheduling information.
  • the resource information scheduling can be implemented between the access nodes through dynamic scheduling or semi-static scheduling, which improves the flexibility of resource scheduling, and can implement scheduling negotiation between different carriers to improve communication performance.
  • the scheduling information includes one or more downlink control information DCI information elements, and the one or more DCI information elements are used to generate DCI, or the scheduling information includes DCI.
  • the scheduling information includes DCI.
  • the second access node may generate DCI and send the DCI to the first access node, and the first access node may also receive the DCI and send the DCI to the terminal device.
  • the first access node does not have the ability to generate DCI, it can receive the DCI generated by other access nodes (such as the second access node), and then deliver the DCI to implement resource information scheduling and improve communication performance.
  • the scheduling information includes uplink scheduling information.
  • Uplink resource information can be scheduled between access nodes to further improve communication performance.
  • the uplink scheduling information includes one or more of the following: scheduling information of a random access channel, scheduling information of a scheduling request, scheduling information of a buffer status report, or scheduling information of a channel state.
  • the access node may allocate uplink resource information to the terminal device according to the uplink scheduling information.
  • the second access node may also receive uplink information, where the uplink information includes one or more of the following: random access channel information, scheduling request, buffer status report, or channel status information;
  • the second access node sends the uplink information to the first access node, and the first access node receives the uplink information.
  • the terminal equipment can send uplink information to request the access node to allocate uplink resource information to it, and the access nodes can implement negotiation and scheduling between different carriers.
  • the first access node may send the first request information to the second access node, and the second access node receives the first request information.
  • request information where the first request information is used to request scheduling information, and the first request information includes a scheduling result; the second access node sends the scheduling information to the first access node, and the first access node receives the scheduling information the scheduling information.
  • the first access node has the scheduling capability, but when it does not have the capability to generate scheduling information, it may request the second access node to generate scheduling information, so as to implement scheduling negotiation between different carriers.
  • the second access node may send the first request information to the first access node, and then the first access node may send scheduling information to the second access node.
  • the second access node does not have the scheduling capability, or does not have the capability to generate the scheduling, it may request the first access node to send scheduling information to implement scheduling negotiation between different carriers.
  • the first access node may also send data information to the second access node, and the second access node receives data information from the first access node; the second access node The ingress node sends the data information to the terminal device.
  • the data information is downlink data information
  • the first access node as a data source node, can acquire the user's data information from the core network, and deliver it to the terminal device through the second access node.
  • the first access node may also directly deliver the data information to the terminal device.
  • the data information is user data, or a radio link control layer RLC protocol data unit PDU obtained after the first access node processes the user data, or the first access node processes the user data.
  • the second access node may also send second request information to the first access node, and the first access node receives the second request information, the second request information Used to request data information.
  • the first access node may send data information to the second access node according to the request of the second access node, so as to implement communication between different access nodes.
  • the first access node may also send logical channel information to the second access node, and the second access node receives the logical channel information, the logical channel information and the user to which the user data belongs. associated with the logical channel.
  • the second access node may determine the amount of data to send to the terminal device according to the logical channel information, thereby further improving the performance of communication.
  • the second access node may also send data information to the first access node, and the first access node receives the data information from the second access node, and sends data to the terminal device Send the data information.
  • the data information is downlink data information
  • the second access node as a data source node, can acquire the user's data information from the core network, and deliver it to the terminal device through the first access node.
  • the second access node may also directly deliver the data information to the terminal device.
  • the first access node sends the retransmission scheduling information to the second access node
  • the second access node sends the retransmission scheduling information to the second access node.
  • Retransmitted scheduling information is received.
  • the MAC entity of the first access node may send retransmission scheduling information, thereby implementing data information retransmission.
  • the optional second access node is a data source node.
  • the second access node when the data information is RV version data obtained after the second access node processes the user data, the second access node sends a new RV version data.
  • the first access node receives the new RV version data from the second access node, and sends the new RV version data to the terminal device.
  • the second access node may generate new RV version data for retransmission.
  • the optional second access node is a data source node.
  • the second access node sends feedback information of the data information to the first access node, and the first access node receives the feedback information from the second access node,
  • the feedback information is used to feed back whether the data information is successfully sent or failed.
  • the first access node can decide whether to retransmit the data information according to the feedback information, which can further improve the communication performance.
  • the MAC entity of the first access node is connected to the MAC entity of the second access node; or the MAC entity of the first access node is respectively connected to the first access node
  • the PHY entity of the node is connected with the PHY entity of the second access node.
  • the MAC1 entity of the first access node when the MAC1 entity of the first access node is connected to the MAC1 entity of the second access node, it further includes: the RLC1 entity of the first node is connected to the MAC1 entity; or The RLC1 entity of the first node is connected to the MAC1 entity and the MAC2 entity respectively; or the RLC1 entity of the first node is connected to the MAC1 entity, and the RLC2 entity of the second node is connected to the MAC2 entity .
  • a communication apparatus for implementing the above-mentioned various methods.
  • the communication device may be the access node in the first aspect, or a device including the access node, or a device included in the access node, such as a chip; or, the communication device may be the first aspect.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means may be implemented by hardware, software, or by executing corresponding software in hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • a communication device comprising: a processor and an interface circuit, where the interface circuit is configured to communicate with modules outside the communication device; the processor is configured to run a computer program or instructions to execute any one of the above-mentioned aspects Methods.
  • the communication device may be the access node in the first aspect, or a device including the access node, or a device included in the access node, such as a chip; or, the communication device may be the first aspect.
  • the interface circuit may be a code/data read/write interface circuit for receiving computer-executed instructions (the computer-executed instructions are stored in memory, may be directly read from memory, or may pass through other devices) and transmit them to the A processor to cause the processor to execute computer-executable instructions to perform the method described in any of the above aspects.
  • the communication device may be a chip or a system of chips.
  • a communication device comprising: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, execute the method according to any one of the preceding aspects according to the instruction.
  • the communication device may be the access node in the first aspect, or a device including the access node, or a device included in the access node, such as a chip; or, the communication device may be the first aspect.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium, which, when executed on a communication device, enable the communication device to perform the method described in any one of the above aspects.
  • the communication device may be the access node in the first aspect, or a device including the access node, or a device included in the access node, such as a chip; or, the communication device may be the first aspect.
  • a computer program product comprising instructions which, when executed on a communication device, enable the communication device to perform the method of any of the preceding aspects.
  • the communication device may be the access node in the first aspect, or a device including the access node, or a device included in the access node, such as a chip; or, the communication device may be the first aspect.
  • a seventh aspect provides a communication apparatus (for example, the communication apparatus may be a chip or a chip system), the communication apparatus includes a processor for implementing the functions involved in any of the above aspects.
  • the communication device further includes a memory for storing necessary program instructions and data.
  • the communication device is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.
  • a communication system in an eighth aspect, includes the first access node of the above aspect and the second access node of the above aspect.
  • the communication system further includes a terminal device.
  • FIG. 1 is a schematic diagram of a scheduling scenario
  • FIG. 2 is a schematic diagram of a sounding reference signal switching
  • FIG. 3 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another communication system provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a possible protocol layer provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a multi-standard dual-link deployment scenario
  • FIG. 7 is a schematic diagram of an interface in a protocol stack
  • FIG. 8 is a schematic diagram of a multi-standard dual-link protocol stack
  • FIG. 9 is a schematic diagram of a communication process provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a format of a buffer status report provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a protocol stack provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a protocol stack provided by an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a protocol stack provided by an embodiment of the present application.
  • 15 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • FIG. 16 is a schematic diagram of yet another communication method provided by an embodiment of the present application.
  • FIG. 17 is a schematic diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of the format of a MAC PDU provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 20 is a schematic diagram of yet another communication method provided by an embodiment of the present application.
  • FIG. 21 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • FIG. 22 is a schematic diagram of yet another communication method provided by an embodiment of the present application.
  • FIG. 23 is a schematic diagram of yet another communication method provided by an embodiment of the present application.
  • FIG. 24 is a schematic diagram of the format of another MAC PDU provided by an embodiment of the present application.
  • 25 is a schematic flowchart of a protocol stack configuration method provided by an embodiment of the present application.
  • FIG. 26 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 27 is a schematic structural diagram of still another communication apparatus provided by an embodiment of the present application.
  • the word "exemplary” is used to mean serving as an example, illustration or illustration. Any embodiment or design described in this application as "exemplary” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present a concept in a concrete way.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • Terminal equipment also known as user equipment (UE) is a device with wireless transceiver functions that access device) communicates with one or more core network (core network, CN) devices (or may also be referred to as core devices).
  • core network CN
  • core devices or may also be referred to as core devices.
  • User equipment may also be referred to as an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, user device, or the like.
  • User equipment can be deployed on land, including indoor or outdoor, handheld or vehicle; can also be deployed on water (such as ships, etc.); can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the user equipment may be a cellular phone (cellular phone), a cordless phone, a session initiation protocol (SIP) phone, a smart phone (smart phone), a mobile phone (mobile phone), a wireless local loop (WLL) station, personal digital assistant (PDA), etc.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the user equipment may also be a handheld device with a wireless communication function, a computing device or other device connected to a wireless modem, an in-vehicle device, a wearable device, a drone device, or a terminal in the Internet of Things, the Internet of Vehicles, the fifth generation Mobile communication (5th-generation, 5G) network and any form of terminal in future network, relay user equipment or terminal in future evolved PLMN, etc.
  • the relay user equipment may be, for example, a 5G home gateway (residential gateway, RG).
  • the user equipment can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, telemedicine Wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home wireless terminals, etc.
  • VR virtual reality
  • AR augmented reality
  • This embodiment of the present application does not limit the type or type of the terminal device.
  • Network equipment which refers to equipment that can provide wireless access functions for terminals.
  • the network device may support at least one wireless communication technology, such as LTE, NR, and the like.
  • Network devices are also called network nodes or nodes.
  • network devices may include access network devices (also referred to as access nodes or nodes).
  • network devices include, but are not limited to: next-generation node B (generation node B, gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC) in the 5G network, node B (node B, NB), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (transmitting point) point, TP), mobile switching center, small station, micro station, etc.
  • next-generation node B generation node B
  • eNB evolved node B
  • RNC radio network controller
  • the network device may also be a wireless controller, a centralized unit (CU), and/or a distributed unit (DU) in a cloud radio access network (CRAN) scenario, or the network device may It is a relay station, an access point, a vehicle-mounted device, a terminal, a wearable device, and a network device in future mobile communications or a network device in a future evolved public land mobile network (PLMN).
  • An access network device is also called an access node.
  • the network device may include a core network (CN) device, and the core network device includes, for example, an access and mobility management function (access and mobility management function, AMF) and the like.
  • CN core network
  • AMF access and mobility management function
  • the area covered by an access network device or a part of the access network device is called a cell.
  • CA Carrier aggregation
  • Carriers corresponding to different cells participating in carrier aggregation may be referred to as component carriers (CC).
  • the CA may include a primary component carrier (PCC) and a secondary component carrier (SCC).
  • the CA may include a primary cell (primary cell, PCell) and a secondary cell (secondary cell, SCell).
  • PCC or SCC can be one or more.
  • PCell or SCell can be one or more.
  • a CA includes, but is not limited to, at least one of the following characteristics:
  • multiple input multiple output (MIMO) layers of multiple carriers can be dynamically shared, and resource allocation can be jointly optimized.
  • CA currently supports cross-carrier scheduling of the same standard.
  • Cross-carrier scheduling is relative to self-scheduling.
  • the uplink data scheduling information and/or downlink data scheduling information of CC1 may be sent in CC1.
  • the uplink data scheduling information and/or the downlink data scheduling information of CC1 may be sent on CC2.
  • the downlink control information (DCI) of CC1 is sent in CC1
  • the DCI of CC2 is sent in CC2.
  • the DCI of CC1 can be sent in CC2, and the DCI of CC2 can be sent in CC2.
  • the DCI of CC1 is cross-carrier scheduling, and the DCI of CC2 is self-scheduling.
  • the DCI is used to indicate the related scheduling information of the physical downlink shared channel (PDSCH).
  • the DCI of CC1 and the DCI of CC2 may be sent in one DCI.
  • DCI may be carried through a physical downlink control channel (PDCCH).
  • PDCH physical downlink control channel
  • the access node can configure cross-carrier scheduling configuration information for the terminal device through radio resource control (radio resource control, RRC) signaling.
  • the cross-carrier scheduling configuration information is used to indicate self-scheduling (own) or cross-carrier scheduling (other). If cross-carrier scheduling is indicated, the cross-carrier scheduling configuration information also indicates the scheduling cell identifier (schedulingCellId) and the scheduled carrier indicator field (CIF), the CIF can be indicated by the field cif-InSchedulingCell, and cif-InSchedulingCell can occupy 3 bits.
  • the cross-carrier scheduling configuration information may be downlink control information (downlink control information, DCI).
  • Cross-carrier scheduling can balance loads, flexibly coordinate resources, and improve spectrum efficiency.
  • CA supports sounding reference signal (SRS) switching.
  • SRS can be used for uplink channel estimation and downlink beamforming.
  • TDD time division duplex
  • SRS needs to be scheduled on the SCC.
  • the SCC is a carrier without a physical uplink shared channel (PUSCH). Due to limited capabilities, terminal equipment can only send uplink signals in one cell. The terminal equipment can send uplink signals in multiple CCs through the function of SRS-CarrierSwitching. For terminal equipment with limited uplink capability, SRS fast switching between multiple uplink carriers is supported, thereby improving downlink transmission performance.
  • PUSCH physical uplink shared channel
  • the terminal device sends PUSCH on CC1 when the system frame number (system frame number, SFN) symbol number 0-10, when the switching time (Switching time) arrives, the terminal device is in the SFN number.
  • the switching time On the symbol of 13, switch to CC2 for SRS transmission, and after the switching time ends, the terminal device switches back to CC1 on the symbol of number 2 of (SFN+1) to continue to send the PUSCH.
  • the switching time in FIG. 2 lasts from symbol number 10 of SFN to symbol number 1 of (SFN+1).
  • CA supports joint uplink control information (UCI) feedback.
  • the terminal device may jointly encode the PDSCH acknowledgement/non-acknowledgement (ACK/NACK) information of multiple CCs and/or the channel state information (CSI) of multiple CCs on one CC for feedback.
  • Joint UCI feedback can reduce the overhead of uplink feedback resources, improve spectral efficiency, and improve uplink transmission performance.
  • CA uplink power control.
  • Symbol-level dynamic power sharing can be implemented among different CCs of CA.
  • the terminal device can determine the transmit power on each symbol according to the priority.
  • the transmission of the high-priority channel on the CC that satisfies the high-priority is prioritized on each symbol.
  • the priority of the CC may be that the priority of the PCC is greater than the priority of the SCC. The smaller the index (index) of the cell, the higher the priority.
  • the priority of the channel can be: physical random access channel (PRACH) of Pcell > physical uplink control channel (PUCCH) with high priority identifier / PUSCH > same priority identifier Case (PUCCH with hybrid automatic repeat request (HARQ)-ACK>PUCCH with CSI)>SRS (aperiodic SRS>semi-static SRS>periodic SRS) or PRACH on non-Pcell.
  • PRACH physical random access channel
  • Pcell physical uplink control channel
  • PUCCH physical uplink control channel
  • HARQ hybrid automatic repeat request
  • SRS aperiodic SRS>semi-static SRS>periodic SRS
  • the technical solutions of the embodiments of the present application can be applied to a mobile communication system, and can also be applied to a satellite communication system, wherein the satellite communication system can be integrated with a traditional mobile communication system.
  • the mobile communication system may be a fourth-generation (4th-generation, 4G) communication system (eg, LTE system), a 5G communication system (eg, NR system), and future mobile communication systems, or other communication systems, etc. .
  • 4G fourth-generation
  • LTE system Long Term Evolution
  • 5G communication system eg, NR system
  • future mobile communication systems or other communication systems, etc.
  • the embodiments of the present application may also be applicable to scenarios of homogeneous networks and heterogeneous networks.
  • the transmission point is not limited, for example, it can be multi-point coordinated transmission between macro base station and macro base station, micro base station and micro base station, and macro base station and micro base station.
  • the embodiments of the present application may also be applied to a frequency division duplex (frequency division duplex, FDD) system/TDD system.
  • the embodiments of the present application may also be applicable to a CU/DU separation architecture.
  • the embodiments of the present application may also be applied to a control plane/user plane (Control Plane/User Plane, CP/UP) separation architecture.
  • the embodiments of the present application may also be applicable to low frequency (such as sub 6G) scenarios, high frequency (such as above 6G) scenarios, terahertz communication scenarios, optical communication scenarios, and the like. As long as a communication system capable of realizing signal transmission is possible, it is not limited in this embodiment of the present application.
  • the communication system includes network equipment and terminal equipment. There may be one or more network devices, and one or more terminal devices.
  • the network equipment can send signals to the terminal equipment, and the terminal equipment can also send signals to the network equipment.
  • the communication system includes terminal equipment, an access network (including access network equipment) and a core network (including core network equipment).
  • the communication system may further include a data network (DN).
  • DN data network
  • Data networks can often be deployed outside operator networks, such as third-party networks.
  • the operator network may access multiple data networks, and multiple services may be deployed on the data networks, so as to provide services such as data and/or voice for terminal devices.
  • the core network is mainly responsible for the mobility management, session management and data transmission of end users.
  • the network elements in the access network include base stations.
  • the base station is responsible for the functions related to the air interface, such as the wireless link maintenance function, maintaining the wireless link with the terminal equipment, and also responsible for the protocol conversion between the wireless link data and the internet protocol (IP) data;
  • radio resource management functions including the establishment and release of radio links, scheduling and allocation of radio resources, etc.
  • mobility management functions including configuring terminals for measurement, evaluating terminal radio link quality, and deciding terminal handovers between cells Wait.
  • a base station may include user plane protocols and control plane protocols.
  • Terminal equipment may include user plane protocols and control plane protocols.
  • the terminal device can interact with the base station through the air interface.
  • each protocol layer of the terminal device can be interconnected with each protocol layer of the base station to transmit information.
  • Protocol layers include physical layer (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP) ), radio resource control layer (radio resource control, RRC), service data adaptation protocol (service data adaptation protocol, SDAP).
  • PHY physical layer
  • MAC medium access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control layer
  • service data adaptation protocol service data adaptation protocol
  • SDAP belongs to the user plane protocol layer
  • RRC belongs to the control plane protocol layer.
  • MR-DC X-radio access technology (RAT) dual connectivity
  • RAT X-radio access technology
  • DC dual connectivity
  • MR-DC includes a primary node (master node, MN) and a secondary node (secondary node, SN).
  • MN master node
  • SN secondary node
  • FIG. 6 in NR version (release, R) 15, various options (option, opt) of MR-DC are proposed for different deployment scenarios and DC evolution routes.
  • User plane connections are shown with solid lines and control plane connections are shown with dashed lines.
  • opt2 series also known as NR DC
  • both the primary node and the secondary node are NR base stations (gNB), gNB and 5G CN are connected to 5G CN, such as AMF and user plane function (UPF).
  • opt3 series also known as Evolved Universal Terrestrial Radio Access Network NR (Evolved Universal Terrestrial Radio Access Network NR, EUTRAN NR, EN)-DC
  • the master node is an LTE base station (e-eNB)
  • the secondary node is an NR base station (gNB)
  • the primary node and secondary node are connected to 4G CN, such as mobility management entity (mobility management entity, MME) and serving gateway (serving gateway, SGW).
  • MME mobility management entity
  • serving gateway serving gateway
  • opt4 series also known as New Radio Evolved Universal Terrestrial Radio Access Network (NR EUTRAN, NE)-DC
  • the primary node is gNB
  • the secondary node is e-eNB
  • the primary node and secondary node are connected to 5G CN, such as AMF and UPF .
  • opt7 series also known as New Radio Evolution (NR EUTRAN NR, NGEN)-DC
  • the primary node is e-eNB
  • the secondary node is gNB
  • the primary node and secondary node are connected to 5G CN, such as AMF and UPF.
  • Protocol stack 1 is called MR-DC with EPC, or can be the EN-DC architecture described above.
  • Protocol stack 2 is called MR-DC with 5GC and can include the aforementioned NE-DC, NGEN-DC and NR-DC architectures.
  • the interface of the protocol stack 1 ((a) in FIG. 7 ) and the interface of the protocol stack 2 ((b) in FIG. 7 ) are shown in FIG. 7 .
  • Protocol stack 1 adopts S1 and X2 interfaces
  • protocol stack 2 adopts Ng and Xn interfaces.
  • the protocol stack on the UE side is shown in FIG. 8 .
  • MN and SN have their own RRC layers, RRC1 and RRC2 respectively, and the control plane protocol stack is a complete RRC/PDCP/RLC/MAC/PHY.
  • the standard of MN is LTE
  • the standard of SN is NR.
  • the user plane protocol stack is SDAP/PDCP/RLC/MAC/PHY, and one PDCP entity is connected to the RLC/MAC/PHY of MN and SN at the same time.
  • Improve the instantaneous rate of terminal equipment such as data packets 1/3/5/... go MN, data packets 2/4/6/... go to SN
  • PDCP can also perform packet replication to improve reliability (such as data packets 1/2 /3/...go to MN, data packets 1/2/3/...go to SN at the same time).
  • MR-DC is supported in the NR standard, and subsequent NR versions are also evolved based on MR-DC.
  • X-RAT CA also known as multi-standard carrier aggregation (MR-CA)
  • MR-CA multi-standard carrier aggregation
  • MR-DC currently does not support aggregation between multiple carriers, dynamic/real-time scheduling negotiation between different carriers, and CA features such as cross-carrier scheduling and joint UCI feedback, so the communication performance is poor.
  • a communication method provided by an embodiment of the present application can also support aggregation of carriers of different standards, such as supporting MR-CA, so that access nodes can communicate with each other, thereby realizing the CA feature and improving communication performance .
  • ideal backhaul is between nodes (for example, nodes are deployed through optical fibers, or low-latency cables are deployed when nodes are co-sited), and the transmission time between nodes is short (eg, less than 1 millisecond (ms)).
  • Fig. 9 is a possible communication method provided by the embodiment of the present application.
  • the communication method can realize the communication between access nodes in the MR-CA protocol stack, and includes the following steps:
  • S901 The first access node determines scheduling information.
  • the first access node involved in the embodiment of the present application may be a scheduling node, a scheduled node or a third-party node
  • the second access node may be a scheduling node, a scheduled node or a third-party node.
  • the first access node is used as the scheduling node
  • the second access node is used as the scheduled node for description.
  • the standard of the first access node and the standard of the second access node may be the same or different.
  • the “standard” involved in the embodiments of this application may be 3G/wideband code division multiple access (WCDMA)/universal mobile telecommunications system (UMTS)/code division multiple access (code division multiple access). division multiple access, CDMA)/time division-synchronous code division multiple access (TD-SCDMA), 4G/LTE, 5G/NR, 6G, 7G and other systems and systems.
  • WCDMA wideband code division multiple access
  • UMTS universal mobile telecommunications system
  • code division multiple access code division multiple access
  • division multiple access CDMA
  • TD-SCDMA time division-synchronous code division multiple access
  • the scheduling information may be used to instruct the second access node to receive data or to transmit data resource information.
  • the scheduling information may include downlink scheduling information, and the downlink scheduling information may be used to indicate resource information for sending data, and the resource information for sending data is downlink resource information.
  • the downlink scheduling information is used to generate downlink scheduling configuration information, and the downlink scheduling configuration information can allocate downlink resource information for terminal equipment.
  • the scheduling information may include a scheduling result, and/or intermediate information (if any) used to generate downlink scheduling configuration information, and/or downlink scheduling configuration information.
  • the downlink scheduling configuration information is DCI (also called DCI format or DCI container), and the intermediate information used to generate the DCI is one or more DCI cells.
  • the DCI may be composed of one or more DCI cells, and the DCI cells may be generated from the scheduling result.
  • the scheduling information may be a scheduling result, or the scheduling information may include one or more DCI cells, or the scheduling information may include DCI.
  • the scheduling information may include uplink scheduling information, and the uplink scheduling information may be used to indicate resource information of received data, where the resource information of received data is uplink resource information.
  • the uplink scheduling information is used to generate uplink scheduling configuration information, and the uplink scheduling configuration information can allocate uplink resource information for terminal equipment.
  • the uplink scheduling information may include, but is not limited to, one or more of the following: scheduling information of random access channel (RACH), scheduling request (scheduling request, SR) scheduling information, buffer status report (buffer status report, BSR) ) of the scheduling information, or the scheduling information of the CSI.
  • the scheduling information may include a scheduling result, and/or intermediate information (if any) used to generate uplink scheduling configuration information, and/or uplink scheduling configuration information.
  • the first access node acts as a scheduling node and can generate a scheduling result.
  • the first access node may generate one or more DCI cells or generate DCIs according to the scheduling result.
  • the first access node may receive scheduling information from other access nodes (eg, the second access node). For example, the first access node sends first request information to other access nodes, where the first request information is used to request scheduling information, and other access nodes send scheduling information to the first access node.
  • the first request information optionally includes the scheduling result (eg, in the case that other access nodes cannot generate the scheduling result).
  • the first request information can be used to request the generation of DCI information elements. If the first access node does not have the ability to generate DCI information elements, the first request information Can be used to request generation of DCI.
  • the scheduling result includes but is not limited to at least one of the following information: scheduling resource information, modulation and coding strategy (modulation and coding scheme, MCS), uplink power control (transmit power control, TPC), triggered (triggered) CSI/SRS, redundancy version (redundancy version, RV), HARQ process identifier (HARQ process id), network device interface (network device interface, NDI), antenna port, etc.
  • MCS modulation and coding strategy
  • TPC transmit power control
  • triggered CSI/SRS
  • redundancy version redundancy version
  • RV redundancy version
  • HARQ process identifier HARQ process id
  • network device interface network device interface
  • NDI network device interface
  • DCI may include, but is not limited to, at least one of the following information: DCI format indication information (used to indicate uplink or downlink), carrier indicator, bandwidth part indicator, frequency domain resource allocation, and time domain resource allocation , frequency hopping indication in frequency domain, virtual resource block (VRB) to physical resource block (PRB) mapping (VRB-to-PRB mapping), physical resource block bundling size indicator (PRB bundling size indicator) ), MCS, New data indicator, Redundancy version (RV), HARQ process number (HARQ process number), HARQ timing, TPC command for scheduled PUSCH, uplink or auxiliary Uplink (supplementary uplink, SUL) indication (UL/SUL indicator), precoding information and number of layers (Precoding information and number of layers), antenna port (Antenna ports), SRS resource indicator (SRS resource indicator), SRS request (SRS) request), CSI request (CSI request), code block group (CBG) transmission information (CBG transmission information, CBGTI), phase tracking reference signal (phase-tracking reference signal, PT
  • S902 The first access node sends scheduling information to the second access node, and the second access node receives the scheduling information.
  • the first access node may interact with the second access node through the first communication manner.
  • the first communication mode supports carrier aggregation between different standards.
  • the first communication manner may communicate based on the first protocol stack.
  • the first protocol stack may be an improvement on an existing protocol stack (for example, an MR-DC protocol stack) to support the first communication mode.
  • the first protocol stack will be described in subsequent embodiments.
  • the second access node determines resource information for receiving data or sending data.
  • the second access node may determine, according to the indication of the scheduling information, resource information for the second access node to receive data or send data, that is, determine uplink resource information or downlink resource information.
  • the second access node may send, to the terminal device, resource information for the second access node to receive data or send data in a dynamic scheduling or semi-persistent scheduling manner.
  • the second access node and the terminal device may interact based on the resource information of the data received by the second access node or the resource information of the data sent by the second access node.
  • the second access node sends the resource information of the data sent by the second access node to the terminal device by means of dynamic scheduling.
  • the second access node may send DL dynamic grant (dynamic grant, DG) configuration information, where the DL DG configuration information includes resource information of the data sent by the second access node.
  • DL DG configuration information is DCI.
  • the second access node may generate DCI according to the one or more DCI information elements, and send the DCI to the terminal device. If the scheduling information includes DCI, after receiving the scheduling information, the second access node sends DCI (transparent transmission/transparent transmission) to the terminal device.
  • the second access node sends the resource information of the data sent by the second access node to the terminal device in a semi-persistent scheduling manner.
  • the second access node may send DL SPS information, or send DL CG configuration information, where the DL SPS information or DL CG configuration information includes resource information for the data sent by the second access node.
  • the second access node sends the resource information of the data received by the second access node to the terminal device in a dynamic scheduling manner.
  • the second access node may send UL DG configuration information, where the UL DG configuration information includes resource information for data received by the second access node.
  • the second access node sends the data resource information received by the second access node to the terminal device in a semi-persistent scheduling manner.
  • the second access node may send UL SPS information or UL CG configuration information, where the UL SPS information or UL CG configuration information includes resource information for sending data by the second access node.
  • the first access node may also receive other scheduling information from other nodes, and the other scheduling information may be used to indicate the first access node.
  • the access node receives data or transmits resource information of data.
  • the first access node may send, to the terminal device, resource information of the data sent or received by the first access node by means of dynamic scheduling or semi-persistent scheduling.
  • DL SPS information, DL CG configuration information, UL SPS information or UL CG configuration information may include but not limited to at least one of the following information: whether frequency hopping (frequency Hopping), cg-DMRS-Configuration, MCS table (mcs-Table), half Static or dynamic UCI configuration (uci-OnPUSCH), resource allocation type (resourceAllocation), RBG size (rbg-Size), power control selection (powerControlLoopToUse), configuration of power control parameters such as P0 and Alpha (p0-PUSCH-Alpha), conversion Precoder (transformPrecoder), number of parallel HARQ processes (nrofHARQ-Processes), number of repetitions (repK), RV version number corresponding to each repetition (repK-RV), CG time domain period (periodicity), timer duration configuration ( configuredGrantTimer), time offset (timeDomainOffset), time domain allocation (timeDomainAllocation), frequency domain allocation (frequencyDomainAllocation), antenna port (antennaPort),
  • data information including DL data information and/or UL data information, may also be exchanged between the first access node and the second access node.
  • the description is mainly based on DL data information.
  • the first access node may send data information to other access nodes (eg, the second access node).
  • the data information is data information of the other access node, for example, the data information is data information of the second access node.
  • the data information may be (unprocessed) user data.
  • the data information may be an RLC protocol data unit (protocol data unit, PDU) obtained after the first access node processes the user data.
  • the RLC entity of the first access node processes the user data to obtain the RLC. PDUs.
  • the data information may be a MAC sub (Sub) PDU obtained after the first access node processes the user data.
  • the MAC entity of the first access node adds the MAC SubPDU obtained by adding a MAC subheader (subheader) to the RLC PDU or the MAC service data unit (service data unit, SDU).
  • the data information may be the MAC PDU obtained after the first access node processes the user data.
  • the MAC entity of the first access node concatenates one or more MAC SubPDUs. Also called MAC transport block (transport block, TB).
  • the data information may be RV version data obtained after the first access node processes the user data.
  • the RV version data includes but is not limited to information such as user data and RV version number.
  • other access nodes may send second request information to the first access node, where the second request information is used to request data information.
  • the first access node may send data information to other access nodes after receiving the second request information.
  • Other access nodes may request data information from the first access node every (per) transmission time interval (transmission time interval, TTI) (per TTI). For example, other access nodes may send data information to the first access node every TTI.
  • TTI transmission time interval
  • TTI transmission time interval
  • other access nodes may send data information to the first access node every TTI.
  • the second request information Or other access nodes may request the first access node for data information scheduled by multiple TTIs, for example, other access nodes may send second request information to the first access node once, where the second request information is used to request multiple TTIs data information.
  • the second request information includes but is not limited to at least one of the following information: user identifier (UE id, such as cell-radio network temporary identifier (C-RNTI)), RV version number (the first access node can send RV version data), information for requesting MAC PDUs (the first access node can send MAC PDUs), TBS, RLC PDU size, grant information (grant info), and a list of qualified logical channel (logical channel, LCH) identifiers (LCH id list), information related to the logical channel priority (Logical Channel Prioritization, LCP) restriction (restriction).
  • UE id such as cell-radio network temporary identifier (C-RNTI)
  • RV version number the first access node can send RV version data
  • information for requesting MAC PDUs the first access node can send MAC PDUs
  • TBS RLC PDU size
  • grant information grant info
  • the information related to LCP restriction includes but is limited to at least one of the following information: sub-carrier spacing (SCS)/grant free (GF) type (type) 1, PUSCH Duration, serving cell identification (Serving Cell) id(s)), cell group id (cell group id, CG id), physical layer priority index (PHY priority index), etc.
  • SCS sub-carrier spacing
  • GF grant free
  • PUSCH Duration serving cell identification
  • Serving Cell serving Cell
  • cell group id cell group id
  • CG id cell group id
  • PHY priority index physical layer priority index
  • the first access node may also send logical channel information to the second access node, where the logical channel information is related to the LCH of the user to which the user data belongs.
  • logical channel information includes, but is not limited to, at least one of the following information: LCH priority, LCH token bucket size duration (bucket size duration, BSD) and LCH priority bit rate (prioritised bit rate, PBR), etc., where LCH's The token BSD is also known as LCH's token bucket deep.
  • the second access node can determine the amount of data to send to the terminal device according to the logical channel information, and then send the data information/user data of the data amount, which can further improve the communication performance.
  • UE-Universal Terrestrial Radio Access Network Uu
  • Uu UE-Universal Terrestrial Radio Access Network
  • the resource information for the second access node to receive data or send data includes indication information for retransmission, for example, the DCI includes indication information for retransmission.
  • the data information is user data
  • the data information is an RLC PDU obtained after the first access node processes the user data
  • the data information is a MAC SubPDU obtained after the first access node processes the user data
  • the first access node may re-send the data information to the second access node.
  • the first access node may retransmit the scheduling information.
  • the data information is RV version data obtained by the first access node processing the user data
  • the first access node may generate new RV version data and send the new RV version data to the second access node.
  • the first access node may receive data information from other access nodes (eg, a second access node).
  • the data information is data information of the first access node.
  • the data information may be (unprocessed) user data.
  • the data information may be an RLC PDU obtained after the second access node processes the user data.
  • the data information may be a MAC SubPDU obtained after the second access node processes the user data.
  • the data information may be a MAC PDU obtained after the second access node processes the user data.
  • the data information may be RV version data obtained after the second access node processes the user data.
  • the resource information for the second access node to receive data or send data includes indication information for retransmission, for example, the DCI includes indication information for retransmission.
  • the data information is user data
  • the data information is an RLC PDU obtained after the second access node processes the user data
  • the data information is a MAC SubPDU obtained after the second access node processes the user data
  • the data information is When the second access node processes the user data and obtains the MAC PDU, the first access node may resend the scheduling information to the second access node, and the second access node may resend the data information to the terminal device.
  • the second access node can generate new RV version data, send the new RV version data to the first access node, and the first access node can generate new RV version data.
  • the ingress node sends the new RV version data to the terminal device.
  • the scheduling information includes the RV version number.
  • the terminal device may report the feedback result of the data information, for example, the terminal device may send the feedback result to the second access node, indicating that the terminal device succeeds or fails in receiving the data information.
  • the second access node may send feedback information to the first access node, where the feedback information is used for reporting success or failure of sending data information. If the data information to be retransmitted is determined according to the feedback information, the processing may be performed according to the above-mentioned situation that the resource information of the second access node receiving data or sending data includes indication information for retransmission, which is not repeated here.
  • the feedback information includes, but is not limited to, at least one of the following information: RAT identifier (RAT id), frequency point identifier (Freq id), carrier identifier (CC id), cell identifier (Cell id), user identifier (UE id), ACK/NACK time-frequency domain location, HARQ process id (HARQ process id), ACK/NACK/discrete transmission (DTX) result.
  • RAT id RAT identifier
  • Freq id frequency point identifier
  • CC id carrier identifier
  • Cell id cell identifier
  • UE id user identifier
  • ACK/NACK time-frequency domain location HARQ process id
  • HARQ process id ACK/NACK/discrete transmission
  • ACK indicates that the terminal device successfully receives the data information, and the first access node and the second access node may not retransmit the data information.
  • NACK indicates that the terminal device fails to receive the data information, and the first access node and the second access node can retransmit the data.
  • DTX indicates that the feedback information of the ACK/NACK of the terminal device is not received, and at this time, the first access node and the second node may retransmit or not retransmit the data information.
  • the first access node and the second access node may also receive uplink information, where the uplink information includes at least one of the following information: random access channel information, scheduling request, buffer status report, or channel status information.
  • the random channel access information may include a time-frequency domain location of a random access preamble resource (preamble resource) and a preamble identifier (preamble id).
  • the scheduling request may include one or more of the following information: the time-frequency domain location of the scheduling request resource (at this time, the access node knows the relationship between SR and LCH(s) or LCG(s) in advance), scheduling User identifier (eg C-RNTI) corresponding to the requested resource, or logical channel identifier or logical channel group identifier (eg LCH(s)id or LCH(s)priority or LCG(s)id) corresponding to the scheduling request resource.
  • scheduling User identifier eg C-RNTI
  • logical channel identifier or logical channel group identifier eg LCH(s)id or LCH(s)priority or LCG(s)id
  • the buffer status report can include BSR original information (such as including RAT id, CC id, Cell id, UE id, LCG id and Buffer size, etc.), or BSR container (obtained by processing the BSR original information, which can be directly transparently transmitted).
  • the channel state information may include uplink channel state information and/or downlink channel state information.
  • the uplink channel state information may include at least one of the following information: RAT id, CC id, Cell id, UE id, CSI original information, and CSI container.
  • the downlink channel state information may include at least one of the following information: RAT id, CC id, Cell id, UE id, SRS measurement result, and SRS id.
  • BSR can include long form and short form. As shown in (a) of Figure 10, it is a possible BSR format (short format), BSR contains a logical channel group (logic channel group, LCG) id field, and a buffer size (Buffer Size) field , where the LCG id field is the logical channel group identifier, and the Buffer Size field is the identifier of the data size range. As shown in (b) of Figure 10, it is another possible BSR format (such as long format), the BSR contains multiple LCG id fields (such as 7 LCGs), and multiple Buffer Size fields (such as m Buffer Size field).
  • scheduling or user data can be interconnected between different access nodes, which can improve communication performance.
  • the interconnection and intercommunication between access nodes of different standards can also be realized, and the interconnection and intercommunication between access nodes of different manufacturers can also be realized, so as to realize the CA feature and further improve the communication performance.
  • the embodiment of the present application further provides a first protocol stack.
  • the first protocol stack is applicable to the network side and the terminal device side.
  • the first access node and the second access node, and the first protocol stack is MR-CA is taken as an example for description.
  • the standard of the first access node and the standard of the second access node may be the same or different.
  • one MAC entity can be connected to multiple PHY entities of different standards.
  • the SDAP entity/PDCP entity/RLC entity corresponding to the DRB and/or the logical channel (logical channel, LCH) share the same MAC entity.
  • the RRC entity/PDCP entity/RLC entity corresponding to the control plane share the same MAC entity.
  • the user plane protocol stack model on the network side is shown in (a) of Figure 11.
  • the PHY1 entity of the first access node and the PHY2 entity of the second access node are respectively connected to the MAC entity/RLC entity/PDCP entity/SDAP entity .
  • the standard of the first access node is RAT1
  • the standard of the second access node is RAT2
  • RAT1 and RAT2 may be the same or different.
  • the PHY1 entity/MAC entity/RLC entity/PDCP entity/SDAP entity may belong to the first access node, and the PHY2 entity belongs to the second access node.
  • the PHY1 entity belongs to the first access node, and the PHY2 entity/MAC entity/RLC entity/PDCP entity/SDAP entity may all belong to the second access node.
  • the PHY2 entity and the MAC entity exchange information through the inter-station interface between the first access node and the second access node, and the PHY2 entity
  • the interface between the entity and the MAC entity can be a private interface (such as PHY2 entity/PHY1 entity/MAC entity/RLC entity/PDCP entity/SDAP entity, etc. belong to the same manufacturer), or can be a standardized interface (such as PHY2 entity/ PHY1 entity/MAC entity/RLC entity/PDCP entity/SDAP entity, etc. belong to different manufacturers).
  • control plane protocol stack model on the network side is shown in (b) of Figure 11.
  • the difference between the control plane protocol stack model and the user plane protocol stack model is that the control plane protocol stack model includes the RRC entity, and the user plane protocol stack model includes the RRC entity. Including SDAP entities, the similarities will not be repeated.
  • the user plane protocol stack model and control plane protocol stack model on the terminal device side are similar to the user plane protocol stack model and control plane protocol stack model on the network side.
  • the difference is that the PHY2 entity/PHY1 entity/MAC entity/RLC entity/PDCP entity/SDAP entity in the terminal device belong to the same manufacturer, so the interface between the PHY2 entity/PHY1 entity/MAC entity can be implemented by a private interface, or can also be standardized interface implementation.
  • one MAC entity is associated with multiple PHY entities, and can be associated with one or more DRB/LCH configurations at the same time.
  • One of the DRBs is associated with one PDCP entity, and each LCH is associated with one RLC entity.
  • the first DRB may be associated with at least one LCH, that is, the first PDCP entity may be associated with multiple RLC entities.
  • PHY entities of different RATs are connected to their corresponding MAC entities.
  • the DRB and/or the LCH are connected to one MAC entity, and different MAC entities are connected to each other through an interface.
  • the SDAP entity/PDCP entity/RLC entity corresponding to the user plane share one MAC entity.
  • the control plane RRC entity/PDCP entity/RLC entity share the same MAC entity.
  • the standard of the first access node is RAT1
  • the standard of the second access node is RAT2
  • RAT1 and RAT2 may be the same or different.
  • the user plane protocol stack on the network side is shown in (a) of Figure 12.
  • the PHY1 entity of the first access node is connected to the MAC1 entity of the first access node
  • the PHY2 entity of the second access node is connected to the second access node.
  • the MAC2 entities of the nodes are connected, and the MAC1 entities and the MAC2 entities can exchange information through the inter-station interface between the first access node and the second access node.
  • the RLC entity/PDCP entity/SDAP entity connects the MAC1 entity or the MAC2 entity.
  • the PHY1 entity/MAC1 entity/RLC entity/PDCP entity/SDAP entity may belong to the first access node, and the PHY2 entity/MAC2 entity belong to the second access node.
  • the information of the PHY entity and the information of the MAC entity may be exchanged between the first access node and the second access node.
  • the interface between the MAC1 entity and the MAC2 entity may be a proprietary interface, or may be a standardized interface.
  • control plane protocol stack model on the network side is shown in (b) of Figure 12.
  • the difference between the control plane protocol stack model and the user plane protocol stack model is that the control plane protocol stack model includes the RRC entity, and the user plane protocol stack model includes the RRC entity. Including SDAP entities, the similarities will not be repeated.
  • the user plane protocol stack model and control plane protocol stack model on the terminal device side are similar to the user plane protocol stack model and control plane protocol stack model on the network side.
  • the difference is that the PHY2 entity/PHY1 entity/MAC entity/RLC entity/PDCP entity/SDAP entity in the terminal device belong to the same manufacturer, so the interface between the MAC1 entity/MAC2 entity can be implemented by a private interface, or can also be implemented by a standardized interface.
  • each MAC entity is associated with a PHY entity.
  • One MAC entity among the multiple MAC entities is associated with the configuration of one or more DRB/LCHs.
  • the network side may explicitly/implicitly configure an interface between two MAC entities to the terminal device. For this process, refer to the configuration process of the first configuration information in FIG. 14 , which will not be repeated here.
  • PHY entities of different RATs are connected to their corresponding MAC entities.
  • the DRB and/or the LCH are connected to different MAC entities, and the different MAC entities are connected to each other through an interface.
  • the SDAP entity/PDCP entity/RLC entity corresponding to the user plane shares multiple MAC entities.
  • the control plane RRC entity/PDCP entity/RLC entity share multiple MAC entities.
  • the standard of the first access node is RAT1
  • the standard of the second access node is RAT2
  • RAT1 and RAT2 may be the same or different.
  • the user plane protocol stack on the network side is shown in (a) of Figure 13.
  • the PHY1 entity of the first access node is connected to the MAC1 entity of the first access node
  • the PHY2 entity of the second access node is connected to the second access node.
  • the MAC2 entities of the nodes are connected, and the MAC1 entities and the MAC2 entities can exchange information through the inter-station interface between the first access node and the second access node.
  • the RLC entity/PDCP entity/SDAP entity connects the MAC1 entity and the MAC2 entity respectively.
  • the PHY1 entity/MAC1 entity/RLC entity/PDCP entity/SDAP entity may belong to the first access node, and the PHY2 entity/MAC2 entity belong to the second access node.
  • the information of the PHY entity, the information of the MAC entity and the information of the RLC entity may be exchanged between the first access node and the second access node.
  • the interface between the MAC1 entity and the MAC2 entity may be a private interface, or may be a standardized interface.
  • the interface between the RLC entity and the MAC2 entity may be a private interface, or may be a standardized interface.
  • control plane protocol stack model on the network side is shown in (b) of Figure 13.
  • the difference between the control plane protocol stack model and the user plane protocol stack model is that the control plane protocol stack model includes the RRC entity, while the user plane protocol stack model includes the RRC entity. Including SDAP entities, the similarities will not be repeated.
  • the user plane protocol stack model and control plane protocol stack model on the terminal device side are similar to the user plane protocol stack model and control plane protocol stack model on the network side.
  • the difference is that the PHY2 entity/PHY1 entity/MAC entity/RLC entity/PDCP entity/SDAP entity in the terminal device belong to the same manufacturer, so the interface between the MAC1 entity/MAC2 entity/RLC entity can be implemented by a private interface, or can also be standardized interface implementation.
  • each MAC entity is associated with a PHY entity.
  • Each MAC entity of the plurality of MAC entities is associated with the configuration of one or more DRB/LCHs.
  • the network side may explicitly/implicitly configure an interface between two MAC entities to the terminal device. For this process, refer to the configuration process of the first configuration information in FIG. 14 , which will not be repeated here.
  • PHY entities of different RATs are connected to their corresponding MAC entities/RLC entities.
  • the DRB and/or the LCH are connected to different MAC entities, and the different MAC entities are connected to each other through an interface.
  • the SDAP entity/PDCP entity corresponding to the user plane shares multiple MAC entities.
  • the control plane RRC entity/PDCP entity shares multiple MAC entities.
  • the standard of the first access node is RAT1, the standard of the second access node is RAT2, and RAT1 and RAT2 may be the same or different.
  • the user plane protocol stack on the network side is shown in (a) of Figure 14.
  • the PHY1 entity of the first access node is connected to the MAC1 entity of the first access node, and the MAC1 entity is connected to the RLC1 entity of the first access node.
  • the PHY2 entity of the second access node is connected to the MAC2 entity of the second access node, and the MAC2 entity is connected to the RLC2 entity of the second access node.
  • the MAC1 entity and the MAC2 entity may exchange information through the inter-station interface between the first access node and the second access node.
  • the PDCP entity/SDAP entity connects the RLC1 entity and the RLC2 entity respectively.
  • the PHY1 entity/MAC1 entity/RLC1 entity/PDCP entity/SDAP entity may belong to the first access node, and the PHY2 entity/MAC2 entity/RLC2 entity belong to the second access node.
  • the information of the PHY entity and the MAC entity may be exchanged between the first access node and the second access node.
  • the interface between the MAC1 entity and the MAC2 entity may be a private interface, or may be a standardized interface.
  • the interface between the RLC1 entity/RLC2 entity/PDCP entity may be a private interface, or may be a standardized interface.
  • control plane protocol stack model on the network side is shown in (b) of Figure 14.
  • the difference between the control plane protocol stack model and the user plane protocol stack model is that the control plane protocol stack model includes the RRC entity, and the user plane protocol stack model includes the RRC entity. Including SDAP entities, the similarities will not be repeated.
  • the user plane protocol stack model and control plane protocol stack model on the terminal device side are similar to the user plane protocol stack model and control plane protocol stack model on the network side.
  • the difference is that the PHY2 entity/PHY1 entity/MAC entity/RLC entity/PDCP entity/SDAP entity in the terminal device belong to the same manufacturer, so the interface between the MAC1 entity/MAC2 entity/RLC1 entity/RLC2 entity/PDCP entity can be implemented by a private interface , or can also be implemented using a standardized interface.
  • the network side can explicitly/implicitly configure the terminal device whether there is an interface between two MAC entities, so as to indicate whether the protocol stack model on the network side is MR-DC or MR-CA.
  • the configuration process of the first configuration information in FIG. 14 will not be repeated here.
  • the difference between the MR-CA protocol stack model shown in Fig. 14 (a) and Fig. 14 (b) and the MR-DC protocol stack model is whether there is an interface between the MAC entities.
  • the MR-CA protocol stack model there are interfaces between MAC entities, which can exchange information
  • the MR-DC protocol stack model there are interfaces between RLCs, which can exchange information.
  • the cell under the network device 1 is the primary cell (primary cell, PCell) in the CA
  • the cell under the network device 2 is the secondary cell (secondary cell, SCell) in the CA.
  • a possible scenario is a self-scheduling scenario (such as shown in FIG. 1 ).
  • the self-scheduling scenario can be divided into centralized scheduling and distributed scheduling, and the self-scheduling scenario can be divided into centralized DCI generation and distributed DCI generation.
  • the scheduling of downlink resource information by dynamic scheduling is mainly used as an example for description.
  • the processes of semi-persistent scheduling and scheduling of uplink resource information are similar, and will not be repeated here.
  • the scheduler of the PCell is on the PCell. If the scheduler of the SCell is on the PCell (the SCell does not have the scheduling capability, and the PCell is the scheduling node), it is centralized scheduling. If the scheduler of the SCell is on the SCell (the SCell has the scheduling capability, SCell is the scheduling node), it is distributed scheduling.
  • the PCell has the ability to generate DCI cells/DCI
  • the SCell does not have the ability to generate DCI cells/DCI, it is centralized DCI generation, and if the SCell has the ability to generate DCI cells/DCI, it is distributed DCI generation.
  • the network device has the scheduling capability, or the capability to generate DCI cells/DCI, and it may also be assumed that other third-party nodes have these capabilities.
  • DCI is generated for centralized scheduling and distribution.
  • step 1 the PCell (or the MAC1 entity of the PCell) generates the scheduling result of the SCell.
  • the scheduling result is used to generate DCI cell(s), which may constitute DCI.
  • the PCell has scheduling capability, and can be the above-mentioned first access node, and the SCell can be the above-mentioned second access node.
  • the PCell (or the MAC1 entity of the PCell) can send the scheduling result or the DCI information element to the SCell (or the MAC2 entity of the SCell) through the inter-station interface.
  • the PCell may send the scheduling result or the DCI information element to the SCell through the direct interface between base stations.
  • the PCell may forward the scheduling result or the DCI information element to the SCell through the third-party access node.
  • the PCell may forward the scheduling result or the DCI information element to the SCell through the core network or an operation management maintenance (operation administration maintenance, OAM) network element.
  • OAM operation administration maintenance
  • step 3 the SCell (or the MAC2 entity of the SCell) generates DCI according to the scheduling result or the DCI information element.
  • Step 4 (see 4 in (a) of FIG. 15 ), the SCell (or the MAC2 entity of the SCell) sends the DCI to the terminal device through the air interface on the carrier where the SCell is located.
  • the PCell In step 1 (see 1 in (b) of FIG. 15 ), the PCell generates the scheduling result of the SCell.
  • the PCell has scheduling capability, and can be the above-mentioned first access node, and the SCell can be the above-mentioned second access node.
  • step 2 the PCell generates the DCI of the SCell according to the scheduling result.
  • the PCell may send the DCI to the SCell through the inter-station interface.
  • Step 4 the SCell sends the DCI to the terminal device through the air interface on the carrier where the SCell is located.
  • DCI is transparent to both network device 2 and SCell, that is to say, after SCell receives DCI, it does not need to analyze which cells and cell values are included in the DCI, but can transparently transmit it to the terminal device through the air interface of the carrier where the SCell is located. the DCI.
  • step 1 the SCell generates the scheduling result of the SCell itself.
  • the SCell has scheduling capability, and can be the above-mentioned first access node, and the PCell can be the above-mentioned second access node.
  • Step 2 if the SCell does not have the ability to generate a DCI information element, the SCell sends request information to the PCell for requesting the PCell to generate a DCI information element.
  • the request information may include scheduling results (for generating DCI cells).
  • step 3 the PCell generates the DCI information element of the SCell, and sends the DCI information element to the SCell through the inter-station interface.
  • Step 4 the SCell generates DCI according to the DCI information element, and sends the DCI to the terminal device through the air interface on the carrier where the SCell is located.
  • step 1 the SCell generates the scheduling result of the SCell itself.
  • the SCell has scheduling capability, and can be the above-mentioned first access node, and the PCell can be the above-mentioned second access node.
  • Step 2 if the SCell does not have the ability to generate DCI, the SCell sends request information to the PCell for requesting the PCell to generate the DCI.
  • the request information may include a scheduling result (for generating DCI).
  • step 3 the PCell generates the DCI of the SCell, and sends the DCI to the SCell through the inter-station interface.
  • Step 4 (see 4 in (d) of FIG. 15 ), the SCell sends the DCI to the terminal device through the air interface on the carrier where the SCell is located.
  • the terminal device monitors the PDCCH information on the carrier where the SCell is located. If its own DCI is detected, the terminal device can parse the DCI, and receive user data according to the PDSCH indicated by the DCI.
  • the DCI can be generated by PCell or SCell.
  • the DCI can include information such as the time-frequency domain location and MCS of this UL Grant, and the terminal device can send uplink data once according to the configuration information of the UL DG.
  • the configuration information can include information such as the time-frequency domain location, period, and MCS of each UL Grant.
  • the terminal device can send uplink data multiple times according to the configuration information of UL SPS/CG.
  • the SCell or PCell monitors/receives/decodes uplink data on the uplink resources indicated by the UL Grant. Uplink data can be carried on PUSCH.
  • a possible scenario is the cross-carrier scheduling scenario (such as shown in Figure 1).
  • the configuration information such as DCI
  • the SCell are sent in one node (such as the PCell), which can save the transmission of configuration information. cost to come.
  • the cross-carrier scheduling scenario may include centralized scheduling and distributed scheduling, and the cross-carrier scheduling scenario includes centralized DCI generation and distributed DCI generation.
  • the protocol stack shown in FIG. 12(a) is used as an example for description.
  • step 1 the PCell (or the MAC1 entity of the PCell) generates the scheduling result of the SCell.
  • the PCell has scheduling capability, and can be the above-mentioned first access node, and the SCell can be the above-mentioned second access node.
  • step 2 the PCell (or the MAC1 entity of the PCell) generates the DCI of the SCell according to the scheduling result.
  • Step 3 the PCell sends the DCI to the terminal device through the air interface on the carrier where the PCell is located.
  • the DCI of the SCell is uniformly scheduled on the PCell, so no DCI is transmitted on the carrier where the SCell is located. And since the process of generating the scheduling result, the process of generating the DCI, and the process of sending the DCI are all performed on the PCell, the SCell does not participate, so the network device 1 and the network device 2 may not exchange information.
  • DCI generation is centrally scheduled and distributed.
  • the PCell In step 1 (see 1 in (b) of FIG. 16 ), the PCell generates the scheduling result of the SCell.
  • the PCell has scheduling capability, and can be the above-mentioned first access node, and the SCell can be the above-mentioned second access node.
  • the PCell may send the scheduling result or the DCI information element to the SCell through the inter-station interface.
  • the PCell has the scheduling capability and does not have the capability to generate DCI.
  • the PCell can obtain the DCI from other network elements other than the PCell.
  • the SCell has the capability of generating DCI, and the PCell can obtain the DCI from the SCell.
  • Step 3 the SCell generates DCI according to the scheduling result or the DCI information element.
  • the SCell can send DCI to the PCell through the inter-station interface.
  • Step 4 the PCell sends the DCI to the terminal device through the air interface on the carrier where the PCell is located.
  • the PCell may not parse the DCI, but transparently transmit the DCI to the terminal device through the air interface of the carrier where the PCell is located.
  • the SCell In step 1 (see 1 in (c) of FIG. 16 ), the SCell generates the scheduling result of the SCell itself.
  • the SCell has scheduling capability, and can be the above-mentioned first access node, and the PCell can be the above-mentioned second access node.
  • the SCell may send the scheduling result or the DCI information element to the PCell through the inter-station interface.
  • the SCell has the scheduling capability and does not have the capability to generate DCI.
  • the SCell can obtain DCI from other network elements other than the SCell.
  • the PCell has the ability to generate DCI, and the SCell can obtain the DCI from the PCell.
  • Step 3 (see 3 in (c) of FIG. 16 ), the PCell generates DCI according to the scheduling result or the DCI cell.
  • Step 4 (see 4 in (c) in FIG. 16 ), the PCell sends the DCI to the terminal device through the air interface on the carrier where the PCell is located.
  • step 1 the SCell generates the scheduling result of the SCell itself.
  • the SCell has scheduling capability, and can be the above-mentioned first access node, and the PCell can be the above-mentioned second access node.
  • Step 2 the SCell generates DCI according to the scheduling result.
  • the SCell can send DCI to the PCell through the inter-station interface.
  • the SCell can optionally combine the DCI generated by itself and the DCI of the SCell (may also include the DCI generated by other Cells), and uniformly pass the DCI on the carrier where the PCell is located.
  • the air interface sends the DCI to the terminal equipment.
  • the terminal device will receive the DCI generated by the SCell on the air interface of the carrier where the PCell is located, but the terminal device may not care whether the DCI is generated by the PCell or the SCell.
  • the terminal device can receive user data according to the PDSCH indicated by the DCI.
  • the cross-carrier scheduling scenario in (a) in FIG. 12 can be applied to (b) in FIG. 12 , (a) in FIG. 13 , (b) in FIG. 13 and (a) in FIG. 14 , the protocol stack shown in (b) in FIG. 14 , and the repeated parts will not be repeated.
  • the protocol stacks shown in (a) and (b) in FIG. 11 since there are one MAC entity and two PHY entities, the one MAC entity can generate the scheduling result and generate the DCI, and then The DCI is sent to the terminal device through the PHY1 entity or the PHY2 entity.
  • a possible scenario is a data interaction scenario, where the user's data information can be sent on the PCell and/or the SCell.
  • Data interaction scenarios can be divided into centralized scheduling and distributed scheduling, and data interaction scenarios can be divided into centralized data encapsulation and distributed data encapsulation.
  • the scheduler of the PCell is on the PCell. If the scheduler of the SCell is on the PCell (the SCell does not have the scheduling capability, and the PCell is the scheduling node), it is centralized scheduling. If the scheduler of the SCell is on the SCell (the SCell has the scheduling capability, SCell is the scheduling node), it is distributed scheduling. However, since the MAC entity of the PCell is connected with the RLC/PDCP/SDAP entity, the PCell can obtain user data, and the PCell can be regarded as a data source node.
  • the scheduling node is the same as the node that encapsulates the data, it is centralized data encapsulation; if the scheduling node is different from the node that encapsulates the data, it is distributed data encapsulation.
  • the protocol stack shown in FIG. 12(a) is used as an example for description.
  • step 1 the PCell (or the MAC1 entity of the PCell) performs data scheduling for the SCell, and generates a data scheduling result of the SCell.
  • PCell has data scheduling capability, and can be a data source node, for example, can be the above-mentioned first access node or the above-mentioned second access node.
  • step 2 the PCell (or the MAC1 entity of the PCell) can send data information to the SCell (or the MAC12 entity of the SCell) through the inter-station interface.
  • the MAC1 entity of the PCell obtains the RLC PDU (the RLC PDU includes user data) sent by the RLC entity, and the MAC1 entity can directly transparently transmit the RLC PDU to the SCell without processing it.
  • the MAC1 entity of the PCell can also process the RLC PDU, and send the processed data information to the SCell.
  • the MAC1 entity can add a MAC subheader to the RLC PDU (also called MAC SDU, or MAC CE), obtain the MAC SubPDU, and send the MAC SubPDU to the SCell.
  • the MAC1 entity can concatenate one or more MAC SubPDUs to generate a MAC PDU (also called a MAC TB), and send the MAC PDU to the SCell.
  • step 3 the SCell obtains the MAC PDU according to the data information.
  • Step 4 the SCell sends the PDSCH (the PDSCH carries user data) to the terminal device on the carrier where the SCell is located.
  • the PCell In step 1 (see 1 in (b) of FIG. 17 ), the PCell generates the data scheduling result of the SCell.
  • PCell has data scheduling capability, and may be a data source node, for example, may be the above-mentioned first access node or the above-mentioned second access node.
  • Step 2 the PCell generates the MAC PDU, and obtains the RV version data through the PHY layer processing.
  • step 3 the PCell can send the RV version data to the SCell through the inter-station interface.
  • Step 4 the SCell sends the PDSCH to the terminal device on the carrier where the SCell is located.
  • the SCell After the SCell receives the MAC PDU in step 3, it can be encoded and sent through the PHY2 entity, and no further processing is required.
  • the SCell In step 1 (see 1 in (c) of FIG. 17 ), the SCell generates the data scheduling result of the SCell itself.
  • the SCell has data scheduling capability, and can be a data source node, for example, the above-mentioned first access node or the above-mentioned second access node.
  • the SCell may send request information to the PCell through the inter-station interface for requesting user data.
  • the MAC2 entity of the SCell is not connected to the RLC entity and cannot directly obtain the RLC PDU.
  • the request information may be used to request per TTI scheduled user data, or may be used to request multiple TTI scheduled user data.
  • the request information may also include scheduling result information generated by the SCell.
  • Step 3 (see 3 in (c) of FIG. 17 ), optionally based on the scheduling result information in step 2, the PCell may send data information to the SCell through the inter-station interface.
  • step 2 shown in (a) of FIG. 17 Similarity can be seen in step 2 shown in (a) of FIG. 17 .
  • Step 4 the SCell optionally further groups packets according to the data information to obtain the MAC PDU.
  • the SCell sends the PDSCH to the terminal device on the carrier where the SCell is located.
  • the SCell In step 1 (see 1 in (d) of FIG. 17 ), the SCell generates the data scheduling result of the SCell itself.
  • the SCell has data scheduling capability and can be a data source node, such as the above-mentioned first access node or the above-mentioned second access node.
  • the SCell may send request information to the PCell through the inter-station interface for requesting user data.
  • the request information may further include scheduling result information generated by the SCell.
  • Step 3 the PCell generates the MAC PDU, and obtains the RV version data through the PHY layer processing, and can send the RV version data to the SCell through the inter-station interface.
  • Step 4 the SCell sends the PDSCH to the terminal device on the carrier where the SCell is located.
  • the MAC PDU contains multiple MAC SubPDUs.
  • the MAC PDU may be a downlink MAC PDU.
  • the MAC subPDU satisfies at least one of the following:
  • At least one MAC SubPDU includes MAC CE1, and the MAC SubPDU including MAC CE1 includes a reserved (reserved, R)/logical channel identifier (logical channel identifier, LCID) subheader and a fixed-sized (Fixed-sized) MAC CE;
  • At least one MAC SubPDU includes MAC CE2, and the MAC SubPDU including MAC CE2 includes R/format (format, F)/LCID/length (length, L) subheader and variable size (Variable-sized) MAC CE;
  • At least one MAC SubPDU contains a MAC SDU
  • the MAC SubPDU containing the MAC SDU contains the R/F/LCID/L subheader and the MAC SDU
  • At least one MAC SubPDU contains a padding field.
  • the PCell does not obtain the scheduling of the SCell, or the SCell sends the PDSCH to support the token bucket, the PCell can send the LCH information related to the user to the SCell.
  • the PCell can send the LCH information related to the user to the SCell.
  • the process of PCell determining the LCH information refer to the token bucket mechanism on Uu, which is not repeated here.
  • the MAC1 entity of the PCell is connected to the RLC1 entity of the PCell, and the user data of the PCell can be obtained to realize the function of the data source node, and the MAC2 entity of the SCell is connected to the RLC1 entity of the PCell.
  • the RLC2 entity connection of the SCell can obtain the user data of the SCell and realize the function of the data source node.
  • the one MAC entity can generate data scheduling results and generate MAC PDUs , and then send the PDSCH to the terminal device through the PHY1 entity or the PHY2 entity. The rest of the similarities will not be repeated.
  • the terminal device can receive user data in the PDSCH corresponding to each carrier of CA, and the terminal device attempts to decode the received user data. ), if the decoding is unsuccessful, the terminal device can feedback that the reception is unsuccessful this time (eg NACK).
  • a possible scenario is a distributed feedback scenario, that is, an independent UCI scenario, where UCI can carry feedback results (eg ACK/NACK).
  • the receiving node of the feedback result is the same as the transmitting node of the PDSCH.
  • the PDSCH feedback result of the carrier where the PCell is located is fed back in the PUCCH of the carrier where the PCell is located, and the PDSCH feedback result of the carrier where the SCell is located is fed back in the PUCCH of the carrier where the SCell is located.
  • the feedback result is carried in the PUCCH.
  • the protocol stack shown in FIG. 12(a) is used as an example for description.
  • the data scheduling of the PDSCH of the carrier where the SCell is located is implemented by the PCell, and the SCell transmits the PDSCH on the carrier where the SCell is located.
  • the PDCCH of the SCell may be delivered by the PCell, or may be delivered by the SCell.
  • Step 1 the SCell receives the feedback result of the SCell.
  • the SCell may receive the feedback result
  • the SCell may be the above-mentioned second access node
  • the PCell may be the above-mentioned first access node.
  • the terminal device receives the PDSCH on the carrier where the SCell is located, and sends the feedback result on the PUCCH of the SCell.
  • the SCell may send the feedback result to the PCell through the inter-station interface.
  • the PCell can determine the feedback result of which HARQ process of which terminal device is based on the feedback result.
  • the feedback result sent by the SCell to the PCell may include the following: for example, including one or more of the following information: RAT identifier (RAT id), frequency point identifier (Freq id), carrier identifier (CC id), cell identifier (Cell id), User ID (UE id), ACK/NACK time-frequency domain location, HARQ process ID (HARQ process id), ACK/NACK/discrete transmission (DTX) result.
  • the ACK/NACK time-frequency domain location and HARQ process id can be used instead.
  • SCell uses multiple processes to send data to terminal devices without waiting for the feedback result of a PDSCH, but waits for the feedback results of multiple processes in parallel, which can improve the communication rate.
  • Step 3 the PCell determines whether to perform retransmission according to the feedback result.
  • retransmission when the feedback result is ACK, retransmission may not be performed, and when the feedback result is NACK, retransmission may be performed.
  • retransmission when the feedback result is NACK, retransmission may not be performed, and it may be considered that the user data corresponding to the feedback result of NACK may be discarded, or the retransmission of the upper RLC entity/PDCP entity may be relied on to ensure the correctness of the data packet.
  • the data scheduling of the PDSCH of the carrier where the SCell is located is implemented by the SCell.
  • Step 1 the SCell receives the feedback result.
  • the SCell may receive the feedback result, and the SCell may be the above-mentioned second access node.
  • Step 2 the SCell determines whether to perform retransmission according to the feedback result.
  • the distributed feedback scenario of (a) in FIG. 12 can be applied to (b) in FIG. 12 , (a) in FIG. 13 , (b) in FIG. 13 and (a) in FIG. 14 ,
  • the protocol stack shown in (b) in FIG. 14 will not be repeated for repeated points.
  • the feedback result can be received by the PHY1 entity or the PHY2 entity, and the one The MAC entity determines whether to perform retransmission.
  • One possible scenario is a centralized feedback scenario, ie a joint UCI scenario.
  • the receiving node of the feedback result may be different from the PDSCH transmitting node.
  • the feedback result of the PDSCH of the carrier where the PCell is located is fed back in the PUCCH of the carrier where the SCell is located, and the feedback result of the PDSCH of the carrier where the SCell is located is fed back in the PUCCH of the carrier where the SCell is located.
  • the feedback result of the PDSCH of the carrier where the PCell is located is fed back in the PUCCH of the carrier where the PCell is located, and the feedback result of the PDSCH of the carrier where the SCell is located is fed back in the PUCCH of the carrier where the PCell is located.
  • the protocol stack shown in FIG. 12(a) is used as an example for description.
  • Step 1 the SCell receives the feedback result of the PCell and/or the feedback result of the SCell.
  • the SCell may receive the feedback result
  • the SCell may be the above-mentioned second access node
  • the PCell may be the above-mentioned first access node.
  • step 2 the SCell can send the feedback result to the PCell through the inter-station interface.
  • step 3 the PCell can determine whether to perform retransmission according to the feedback result.
  • the PCell can determine whether the PDSCH of the PCell is retransmitted, and/or can determine whether the PDSCH of the SCell is retransmitted.
  • Step 1 the PCell receives the feedback result of the PCell and/or the feedback result of the SCell.
  • the PCell may receive the feedback result
  • the SCell may be the foregoing second access node
  • the SCell may be the foregoing first access node.
  • step 2 the PCell can send the feedback result to the SCell through the inter-station interface.
  • step 3 the SCell can determine whether to perform retransmission according to the feedback result.
  • the SCell can determine whether the PDSCH of the PCell is retransmitted, and/or can determine whether the PDSCH of the SCell is retransmitted.
  • the centralized feedback scenario of (a) in FIG. 12 can be applied to (b) in FIG. 12 , (a) in FIG. 13 , (b) in FIG. 13 and (a) in FIG. 14 ,
  • the protocol stack shown in (b) in FIG. 14 will not be repeated for repeated points.
  • the feedback result can be received by the PHY1 entity or the PHY2 entity, and the one The MAC entity determines whether to perform retransmission.
  • One possible scenario is a data retransmission scenario. If the PCell or SCell determines that the feedback result is NACK, retransmission is performed.
  • the data retransmission scenario is similar to the data interaction scenario, which is briefly described here.
  • the data interaction scenario applies to the initial transmission scenario, and also applies to the retransmission scenario.
  • the protocol stack shown in FIG. 12(a) is used as an example for description.
  • the PCell In step 1 (see 1 in (a) of FIG. 21 ), the PCell generates the data scheduling result of the SCell.
  • PCell has data scheduling capability, and may be a data source node, for example, may be the above-mentioned first access node or the above-mentioned second access node.
  • step 2 the PCell can send data information to the SCell through the inter-station interface.
  • step 3 the SCell obtains the MAC PDU according to the data information.
  • Step 4 (see 4 in (a) in FIG. 21 ), the SCell sends the PDSCH to the terminal device on the carrier where the SCell is located.
  • the PCell In step 1 (see 1 in (b) of FIG. 21 ), the PCell generates the data scheduling result of the SCell.
  • PCell has data scheduling capability, and may be a data source node, for example, may be the above-mentioned first access node or the above-mentioned second access node.
  • step 2 the PCell generates new RV version data.
  • the PCell can generate new RV version data during retransmission.
  • step 3 the PCell can send the new RV version data to the SCell through the inter-station interface.
  • Step 4 (see 4 in (b) of FIG. 21 ), the SCell sends the new RV version data to the terminal device on the carrier where the SCell is located.
  • the SCell In step 1 (see 1 in (c) of FIG. 21 ), the SCell generates the data scheduling result of the SCell itself.
  • the SCell has data scheduling capability, and can be a data source node, for example, the above-mentioned first access node or the above-mentioned second access node.
  • Step 2 (see 2 in (c) of FIG. 21 ), optionally (only when newly transmitted), the SCell may send request information to the PCell through the inter-station interface for requesting user data.
  • the PCell may send data information to the SCell through the inter-station interface.
  • Step 4 the SCell optionally generates a MAC PDU by grouping according to the data information; or the SCell directly obtains the MAC PDU from the PCell.
  • the SCell sends the PDSCH to the terminal device on the carrier where the SCell is located.
  • the SCell In step 1 (see 1 in (d) of FIG. 21 ), the SCell generates the data scheduling result of the SCell itself.
  • the SCell has data scheduling capability, and can be a data source node, for example, the above-mentioned first access node or the above-mentioned second access node.
  • the SCell may send request information to the PCell through the inter-station interface for requesting new/different RV version data.
  • Step 3 the PCell generates new/different RV version data, and can send the new/different RV version data to the SCell through the inter-station interface.
  • Step 4 the SCell sends new/different RV version data to the terminal device on the carrier where the SCell is located.
  • the MAC1 entity of the PCell is connected to the RLC1 entity of the PCell, and the user data of the PCell can be obtained to realize the function of the data source node, and the MAC2 entity of the SCell is connected to the RLC1 entity of the PCell.
  • the RLC2 entity connection of the SCell can obtain the user data of the SCell and realize the function of the data source node.
  • the one MAC entity can generate data scheduling results and generate MAC PDUs , and then send the PDSCH to the terminal device through the PHY1 entity or the PHY2 entity. The rest of the similarities will not be repeated.
  • the receiving node of the UL request may be the same as the scheduling node.
  • the receiving node of the UL request may be different from the scheduling node.
  • the description is mainly based on the case where the receiving node of the UL request is different from the scheduling node.
  • the protocol stack shown in FIG. 12(a) is used as an example for description.
  • the receiving node of the UL request is the SCell, and the scheduling node is the PCell.
  • Step 1 the SCell receives the UL request.
  • the SCell may receive the UL request
  • the SCell may be the above-mentioned second access node
  • the PCell may be the above-mentioned first access node.
  • the SCell may send the information related to the UL request to the PCell through the inter-station interface.
  • the information related to the UL request may include UL (such as SR/BSR/RACH/DL CSI/UAI), or may include UL CSI information obtained by measuring the SRS of the terminal device by the SCell.
  • DL CSI information, UL CSI information may include, but is not limited to, at least one of the following: precoding matrix indication (PMI), rank indication (RI), layer indication (layer indicator, LI), channel quality indication ( channel quality indicator, CQI), CSI-RS resource indicator (CSI-RS resource indicator, CRI), reference signal received power (reference signal received power, RSRP), covariance matrix, channel matrix.
  • the DL CSI information and the UL CSI information can be information at cell granularity or information at beam granularity.
  • UAI is the UE assistance information reported by the UE to the network side, and may include a data model of the UE's uplink periodic service.
  • Step 3 the PCell generates a scheduling result according to the information related to UL request scheduling, and the scheduling result is used to configure uplink resource information.
  • the receiving node of the UL request is PCell, and the scheduling node is SCell.
  • Step 1 the PCell receives the UL request.
  • the PCell may receive the UL request
  • the PCell may be the above-mentioned second access node
  • the SCell may be the above-mentioned first access node.
  • the PCell may send the information related to the UL request to the SCell through the inter-station interface.
  • Step 3 the SCell generates a scheduling result according to the information related to UL request scheduling, and the scheduling result is used to configure uplink resource information.
  • the BSR contains an LCG id field and a Buffer Size field, where the LCG id field is the logical channel group identifier, and the Buffer Size field is the data size. The ID of the range.
  • the BSR includes multiple LCG id fields (eg, 7 LCGs), and multiple Buffer Size fields (eg, m Buffer Size fields).
  • the centralized feedback scenario of (a) in FIG. 12 can be applied to (b) in FIG. 12 , (a) in FIG. 13 , (b) in FIG. 13 and (a) in FIG. 14 ,
  • the protocol stack shown in (b) in FIG. 14 will not be repeated for repeated points.
  • the one MAC entity can generate the scheduling result and generate the DCI, and then The UL request is received by the PHY1 entity or the PHY2 entity, and the one MAC entity generates a scheduling result.
  • the above data interaction scenarios and data retransmission scenarios mainly describe the interaction of DL Data.
  • the UL Data sent by the terminal device may be sent to the PCell and/or the SCell.
  • the protocol stack shown in FIG. 12(a) is used as an example for description.
  • the SCell receives UL Data.
  • Step 1 the SCell receives the PUSCH, and the PUSCH carries UL Data.
  • the SCell may receive the UL Data
  • the SCell may be the above-mentioned second access node
  • the PCell may be the above-mentioned first access node.
  • step 2 the SCell can send UL Data to the PCell through the inter-station interface.
  • the SCell may send the PHY2 entity encoded UL Data to the PCell, and the UL Data may be in the form of RV version data, or may be in the form of MAC PDU. If the MAC1 entity receives the RV version data, the PHY1 entity performs soft combining on the RV version data, and forwards the soft combined data to the MAC1 entity for processing.
  • the SCell may send the UL Data processed by the MAC2 entity to the PCell, and the UL Data may be in the form of a MAC SubPDU, or may be in the form of an RLC PDU.
  • the MAC1 entity receives the RLC PDU, it can directly forward it to the RLC entity connected to the MAC1 without additional processing.
  • MAC1 receives the MAC SubPDU, it can extract the MAC subheader and identify it as a MAC SDU (if it is a MAC SDU, it can be directly forwarded as an RLC entity) or if it is identified as a MAC CE, it will be processed by MAC1 accordingly.
  • the MAC1 entity may identify the LCH id according to the LCID in the subheader corresponding to the MAC SDU, and then determine the RLC entity corresponding to the LCH id.
  • the MAC PDU contains multiple MAC SubPDUs.
  • the MAC PDU may be an uplink MAC PDU.
  • the MAC subPDU satisfies at least one of the following:
  • At least one MAC SubPDU includes MAC CE2, and the MAC SubPDU including MAC CE2 includes R/F/LCID/L subheader and Variable-sized MAC CE;
  • At least one MAC SubPDU includes MAC SDU, and the MAC SubPDU including MAC SDU includes R/F/LCID/L subheader and MAC SDU;
  • At least one MAC SubPDU contains MAC CE1, and the MAC SubPDU containing MAC CE1 contains R/LCID subheader and Fixed-sized MAC CE;
  • At least one MAC SubPDU contains the padding field.
  • the UL data interaction scenario in (a) in FIG. 12 can be applied to (b) in FIG. 12 , (a) in FIG. 13 , (b) in FIG. 13 and (a) in FIG. 14 , the protocol stack shown in (b) in FIG. 14 , and the repeated parts will not be repeated.
  • the protocol stacks shown in (a) and (b) in FIG. 11 since there are one MAC entity and two PHY entities, UL Data can be received through the PHY1 entity or the PHY2 entity, and the one The MAC entity forwards to the RLC entity/PDCP entity.
  • the embodiment of the present application also provides a configuration process of the first protocol stack, as shown in FIG. 25 , including the following steps:
  • the terminal device reports capability information.
  • the capability information is used to indicate whether the terminal device supports the MR-CA capability.
  • the capability information may be used to indicate whether the terminal device supports "cross-RAT scheduling", “cross-RAT feedback”, “cross-RAT SRS handover” and other capabilities.
  • cross-RAT scheduling refers to the DCI of one standard scheduling data of another standard (such as the above-mentioned cross-scheduling scenario)
  • cross-RAT feedback refers to the feedback of two standards being fed back on one standard (such as the above centralized feedback scenario)
  • cross-RAT SRS switching It means that the terminal device has only one transmission channel, and the terminal device transmits SRS signals of different formats on the two formats through time division.
  • the network device sends first configuration information to the terminal device, where the first configuration information is used for the first communication mode.
  • the network device may be the above-mentioned first access node or the above-mentioned second access node.
  • the optional first communication mode can completely reuse the MR-DC protocol stack configuration.
  • the first configuration information includes first indication information, where the first indication information may be used to indicate to use MR-DC communication or to use MR-CA communication.
  • the first indication information may further include the MR-DC protocol stack.
  • the first configuration information can use explicit information to indicate whether to use the first communication mode for communication, for example, 1bit information is used to indicate, when 1bit is 1, it indicates that the first communication mode is used for communication, and when 1bit is 0, it indicates that a non-first communication method is used.
  • a communication method of a communication method (such as a communication method of MR-DC) is used to communicate.
  • the first communication manner may not completely reuse the MR-DC protocol stack configuration.
  • the first configuration information may include the above-mentioned information of the first protocol stack.
  • the first configuration information adds an association relationship between two MAC entities, for example, the MAC configuration information of the first access node may include the index or identifier of the MAC entity of the second access node, and/or The MAC configuration information of the second access node may include the index or identifier of the MAC entity of the first access node, and/or a group of configurations may include the index or identifier of the MAC entity of the first access node and the second access node. The index or identity of the node's MAC entity.
  • the first configuration information adds an association relationship between a MAC entity and two PHY entities.
  • the MAC configuration information includes the index or identity of the PHY entity of the first access node, and/or the index or identity of the PHY entity of the second access node.
  • the PHY configuration information of the first access node includes an index or an identifier of a MAC entity
  • the PHY configuration information of the second access node includes an index or an identifier of the MAC entity.
  • a set of configurations includes an index or an identifier of a MAC entity, an index or an identifier of a PHY entity of a first access node, and an index or an identifier of a PHY entity of a second access node.
  • the network device may further instruct the terminal device to access other nodes, and communicate with other nodes through the first communication manner.
  • the network device may activate or deactivate other nodes, and for the activated other nodes, the terminal device communicates with the activated other nodes through the first communication manner.
  • the terminal device can send SRS on the CC of the node, report information such as CQI, detect the DCI etc. used for the node and transmitted on the node, and then implement carrier aggregation and communication processes on different systems.
  • S2504 The terminal device determines to communicate through the first communication method.
  • the methods and/or steps implemented by the access node may also be implemented by components (such as chips or circuits) that can be used for the access node, and the methods and/or steps implemented by the terminal device.
  • the steps can also be implemented by components available for the terminal device.
  • the embodiments of the present application also provide a communication device, which can be used to implement the methods described in the above-mentioned method embodiments. method.
  • the communication device 2600 includes a processing unit 2601 and a transceiver unit 2602, and the device 2600 can be used to implement the methods described in the above method embodiments.
  • the apparatus 2600 is applied to a first access node.
  • the processing unit 2601 is configured to determine scheduling information, where the scheduling information is used to instruct the second access node to receive data or send data resource information;
  • a transceiver unit 2602 configured to send the scheduling information to the second access node.
  • the scheduling information is dynamic scheduling information, or semi-static scheduling information.
  • the scheduling information includes one or more downlink control information DCI information elements, and the one or more DCI information elements are used to generate DCI, or the scheduling information includes DCI.
  • the transceiver unit 2602 is further configured to receive the DCI from the second access node; and send the DCI to the terminal device.
  • the scheduling information includes uplink scheduling information.
  • the uplink scheduling information includes one or more of the following: scheduling information of a random access channel, scheduling information of a scheduling request, scheduling information of a buffer status report, or scheduling information of a channel state.
  • the transceiver unit 2602 is further configured to receive uplink information, where the uplink information includes one or more of the following: random access channel information, scheduling request, buffer status report, or channel status information.
  • the transceiver unit 2602 is further configured to send data information to the second access node, where the data information is downlink data information.
  • the data information is user data, or a radio link control layer RLC protocol data unit PDU obtained after the first access node processes the user data, or the first access node communicates with the user
  • the transceiver unit 2602 is further configured to receive second request information before sending data information to the second access node, where the second request information is used to request data information.
  • the transceiver unit 2602 is further configured to send logical channel information to the second access node, where the logical channel information is related to the logical channel of the user to which the user data belongs.
  • the transceiver unit 2602 is further configured to receive data information from the second access node, where the data information is downlink data information; and send the data information to a terminal device.
  • the scheduling information includes indication information for retransmission.
  • the transceiver unit 2602 is further configured to, when the data information is user data, or an RLC PDU obtained after the second access node processes the user data, or a MAC obtained after the second access node processes the user data.
  • the SubPDU, or the MAC PDU obtained after the second access node processes the user data sends the retransmission scheduling information to the second access node.
  • the transceiver unit 2602 is further configured to receive new RV version data from the second access node when the data information is the RV version data obtained after the second access node processes the user data, and send the data to the second access node.
  • the terminal device sends the new RV version data.
  • the transceiver unit 2602 is further configured to receive feedback information of the data information from the second access node, where the feedback information is used to feed back whether the data information is successfully sent or failed.
  • the transceiver unit 2602 is further configured to send first request information to the second access node, where the first request information is used to request scheduling information, and the first request information includes a scheduling result; receiving the scheduling information from the second access node.
  • the MAC entity of the first access node is connected to the MAC entity of the second access node; or the MAC entity of the first access node is respectively connected to the MAC entity of the first access node.
  • the PHY entity is connected to the PHY entity of the second access node.
  • the apparatus 2600 is applied to a second access node.
  • the transceiver unit 2602 is configured to receive scheduling information, where the scheduling information is used to instruct the second access node to receive data or send data resource information;
  • the processing unit 2601 is configured to determine resource information for receiving data or sending data.
  • the scheduling information is dynamic scheduling information, or semi-static scheduling information.
  • the scheduling information includes one or more downlink control information DCI information elements, and the one or more DCI information elements are used to generate DCI, or the scheduling information includes DCI.
  • processing unit 2601 is further configured to generate the DCI
  • the transceiver unit 2602 is further configured to send the DCI to the first access node.
  • the scheduling information includes uplink scheduling information.
  • the uplink scheduling information includes one or more of the following: scheduling information of a random access channel, scheduling information of a scheduling request, scheduling information of a buffer status report, or scheduling information of a channel state.
  • the transceiver unit 2602 is further configured to receive uplink information, where the uplink information includes one or more of the following: random access channel information, scheduling request, buffer status report, or channel status information; An access node sends the uplink information.
  • the transceiver unit 2602 is further configured to receive data information from the first access node, where the data information is downlink data information; and send the data information to the terminal device.
  • the data information is user data, or a radio link control layer RLC protocol data unit PDU obtained after the first access node processes the user data, or the first access node processes the user data
  • the transceiver unit 2602 is further configured to send second request information to the first access node before receiving the data information from the first access node, where the second request information is used to request data information .
  • the transceiver unit 2602 is further configured to receive logical channel information, where the logical channel information is related to the logical channel of the user to which the user data belongs.
  • the transceiver unit 2602 is further configured to send data information to the first access node, where the data information is downlink data information.
  • the scheduling information includes indication information for retransmission.
  • the transceiver unit 2602 is further configured to, when the data information is user data, or an RLC PDU obtained after the second access node processes the user data, or a MAC obtained after the second access node processes the user data.
  • the SubPDU, or the MAC PDU obtained after the second access node processes the user data receives the retransmission scheduling information sent by the first access node.
  • the transceiver unit 2602 is further configured to send new RV version data to the first access node when the data information is RV version data obtained after the second access node processes the user data.
  • the transceiver unit 2602 is further configured to receive feedback information of data information from a terminal device, where the feedback information is used to report whether the data information is successfully sent or failed; send the feedback to the first access node information.
  • the transceiver unit 2602 is further configured to receive first request information, where the first request information is used to request scheduling information, and the first request information includes a scheduling result; send to the first access node the scheduling information.
  • the MAC entity of the first access node is connected to the MAC entity of the second access node; or the MAC entity of the first access node is respectively connected to the MAC entity of the first access node.
  • the PHY entity is connected to the PHY entity of the second access node.
  • the apparatus 2600 is applied to a terminal device.
  • the transceiver unit 2602 is configured to receive resource information of the second access node for receiving data or sending data;
  • the processing unit 2601 is configured to determine resource information of the second access node to receive data or send data.
  • the transceiver unit 2602 is specifically used for DCI from the second access node or the first access node, where the DCI includes resource information for the second access node to receive data or send data.
  • the transceiver unit 2602 is further configured to send uplink information to the first access node or the second access node, where the uplink information includes one or more of the following: random access channel information, scheduling request, buffering Status report, or channel status information.
  • the transceiver unit 2602 is further configured to receive data information from the first access node or the second access node, where the data information is downlink data information.
  • the transceiver unit 2602 is further configured to send feedback information of the data information to the first access node or the second access node, where the feedback information is used to feed back whether the data information is successfully sent or failed.
  • the MAC entity of the first access node is connected to the MAC entity of the second access node; or the MAC entity of the first access node is respectively connected to the MAC entity of the first access node.
  • the PHY entity is connected to the PHY entity of the second access node.
  • each functional unit in each embodiment of the present application It can be integrated in one processing unit, or it can exist physically alone, or two or more units can be integrated in one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .
  • FIG. 27 Another possible expression form of the communication device is shown in FIG. 27 , and the device 2700 can be used to implement the methods described in the above method embodiments.
  • the apparatus 2700 includes one or more processors 2701.
  • the processor 2701 may be a general-purpose processor or a special-purpose processor or the like.
  • it may be a baseband processor, or a central processing unit.
  • the baseband processor may be used to process communication protocols and communication data
  • the central processing unit may be used to control communication devices (eg, base stations, terminals, or chips, etc.), execute software programs, and process data of software programs.
  • the communication device may include a transceiving unit for implementing signal input (reception) and output (transmission).
  • the transceiver unit may be a transceiver, a radio frequency chip, or the like.
  • the apparatus 2700 includes one or more of the processors 2701, and the one or more processors 2701 can implement the methods described in the above-described embodiments.
  • the processor 2701 may implement other functions in addition to implementing the methods in the above-described embodiments.
  • the processor 2701 may execute instructions, so that the apparatus 2700 executes the methods described in the foregoing method embodiments.
  • the instructions may be stored in whole or in part within the processor, such as instruction 2703, or may be stored in whole or in part in a memory 2702 coupled to the processor, such as instruction 2704, or may be jointly caused by instructions 2703 and 2704.
  • the apparatus 2700 executes the methods described in the above method embodiments.
  • the communication apparatus 2700 may also include a logic circuit, and the logic circuit may implement the methods described in the foregoing method embodiments.
  • the apparatus 2700 may include one or more memories 2702 having stored thereon instructions 2704 that may be executed on the processor to cause the apparatus 2700 to perform the above-described method methods described in the examples.
  • data may also be stored in the memory.
  • Instructions and/or data may also be stored in the optional processor.
  • the one or more memories 2702 may store the corresponding relationships described in the above embodiments, or related parameters or tables involved in the above embodiments, and the like.
  • the processor and the memory can be provided separately or integrated together.
  • the apparatus 2700 may further include a transceiver 2705 and an antenna 2706 .
  • the processor 2701 may be called a processing unit, and controls the device (terminal or base station).
  • the transceiver 2705 may be referred to as a transceiver, a transceiver circuit, an input/output interface circuit, or a transceiver unit, etc., and is used to implement the transceiver function of the device through the antenna 2706 .
  • the antenna 2706 may be integrated in the transceiver 2705.
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • Embodiments of the present application further provide a computer-readable medium on which a computer program is stored, and when the computer program is executed by a computer, implements the methods described in the foregoing method embodiments.
  • Embodiments of the present application further provide a computer program product, which implements the methods described in the foregoing method embodiments when the computer program product is executed by a computer.
  • the embodiments of the present application further provide a computer program, which implements the methods described in the foregoing method embodiments when the computer program is executed on a computer.
  • An embodiment of the present application further provides a communication system, where the communication system includes a first access node and a second access node.
  • the first access node may implement the methods described in the foregoing method embodiments
  • the second access node may implement the methods described in the foregoing method embodiments.
  • the communication system may further include a terminal device.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, optical fiber, Digital Subscriber Line, DSL) or wireless (eg infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, Digital Video Disc (DVD)), or semiconductor media (eg, Solid State Drive, SSD)) etc.
  • An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is configured to execute the method described in the above method embodiments; the interface is used to communicate with modules other than the communication device, and the interface may For communication interface, input and output interface, etc.
  • the interface may be a code/data read and write interface for receiving execution instructions (stored in memory, possibly read directly from memory, or possibly via other devices) and transmitted to the processor to enable The processor runs the execution instructions to execute the methods described in the above method embodiments.
  • the above-mentioned processing device may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software
  • the processor can be a general-purpose processor, which is realized by reading the software codes stored in the memory, and the memory can be integrated in the processor, and can be located outside the processor and exist independently.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that a computer can access.
  • computer readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or be capable of carrying or storing instructions or data structures in the form of desired program code and any other medium that can be accessed by a computer. also.
  • any connection can be appropriately made into a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fusing of the pertinent medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and blu-ray disc, where disks generally reproduce data magnetically, and discs Lasers are used to optically copy data. Combinations of the above should also be included within the scope of computer-readable media.

Abstract

本申请实施例提供一种通信方法及装置，用以支持不同制式的载波进行聚合，提高通信性能。该通信方法包括：第一接入节点确定调度信息，所述调度信息用于指示第二接入节点接收数据或发送数据的资源信息；所述第一接入节点向第二接入节点发送所述调度信息。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2021年04月30日提交中国国家知识产权局、申请号为202110479909.X、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种通信方法及装置。
背景技术
随着无线技术的演进，出现了不同制式的通信系统，例如长期演进(long term evolution，LTE)系统，新无线(new radio，NR)系统等。运营商需要同时部署两种或多种制式，以满足市场需求。针对运行商的部署需求，NR标准中为了LTE系统和NR系统的分流，支持多制式双链接(multi radio-dual connectivity，MR-DC)通信方式，后续NR版本也是基于MR-DC进行演进。
但是MR-DC不支持多载波间的聚合，无法支持不同载波间的动态/实时的调度协商、以及跨载波调度、联合上行控制信息反馈等载波聚合特性，因此通信性能较差。
发明内容
本申请提供一种通信方法及装置，用以支持不同制式的载波进行聚合，实现载波聚合特性，提高通信性能。
第一方面，提供一种通信方法。在该方法中，第一接入节点确定调度信息，所述调度信息用于指示第二接入节点接收数据或发送数据的资源信息；所述第一接入节点向第二接入节点发送所述调度信息，第二接入节点接收调度信息；第二接入节点确定接收数据或发送数据的资源信息。
第一接入节点的制式和第二接入节点的制式可以相同或不同。
在该方法中不同接入节点之间可以实现调度或用户数据等的互联互通，提升通信性能。并且还可以实现不同制式的接入节点之间的互联互通，也可以实现不同厂商的接入节点之间的互联互通，从而实现载波聚合特性，进一步提升通信性能。
在一种可能的设计中，调度信息为动态调度信息，或者半静态调度信息。接入节点之间可以通过动态调度或半静态调度的方式实现资源信息的调度，提高了资源调度的灵活性，并且可以实现不同载波间的调度协商，提高通信性能。
在一种可能的设计中，调度信息包括一个或多个下行控制信息DCI信元，所述一个或多个DCI信元用于生成DCI，或者所述调度信息包括DCI。支持不同载波间的动态/实时的调度协商、以及跨载波调度，提高通信性能。
在一种可能的设计中，所述第二接入节点可以生成DCI，向第一接入节点发送所述DCI，所述第一接入节点还可以接收DCI，向终端设备发送DCI。第一接入节点没有生成DCI的 能力时，可以接收其他接入节点(如第二接入节点)生成的DCI，然后下发该DCI，实现资源信息的调度，提高通信性能。
在一种可能的设计中，调度信息包括上行调度信息。接入节点之间可以对上行资源信息进行调度，进一步提高通信性能。
在一种可能的设计中，所述上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。接入节点可以根据上行调度信息，为终端设备分配上行资源信息。
在一种可能的设计中，所述第二接入节点还可以接收上行信息，所述上行信息包括以下一个或多个：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息；第二接入节点向所述第一接入节点发送所述上行信息，第一接入节点接收上行信息。终端设备可以发送上行信息，请求接入节点为其分配上行资源信息，接入节点之间可以实现不同载波间的协商调度。
在一种可能的设计中，所述第一接入节点确定调度信息时，所述第一接入节点可以向所述第二接入节点发送第一请求信息，第二接入节点接收第一请求信息，所述第一请求信息用于请求调度信息，所述第一请求信息包括调度结果；第二接入节点向第一接入节点发送所述调度信息，所述第一接入节点接收所述调度信息。第一接入节点有调度能力，没有生成调度信息的能力时，可以请求第二接入节点生成调度信息，从而实现不同载波间的调度协商。
可选的，第二接入节点可以向第一接入节点发送第一请求信息，然后第一接入节点可以向第二接入节点发送调度信息。第二接入节点不具备调度能力，或者没有生成调度的能力时，可以请求第一接入节点发送调度信息，实现不同载波间的调度协商。
在一种可能的设计中，所述第一接入节点还可以向所述第二接入节点发送数据信息，第二接入节点接收来自第一接入节点的数据信息；所述第二接入节点向终端设备发送所述数据信息。数据信息为下行数据信息，第一接入节点作为数据源节点，可以从核心网中获取到用户的数据信息，通过第二接入节点下发给终端设备。或者第一接入节点也可以直接将数据信息下发给终端设备。
可选的，所述数据信息为用户数据，或所述第一接入节点对用户数据处理后得到的无线链路控制层RLC协议数据单元PDU，或所述第一接入节点对用户数据处理后得到的媒体接入控制MAC子协议数据单元SubPDU，或者所述第一接入节点对用户数据处理后得到的MAC PDU，或者所述第一接入节点对用户数据处理后得到的冗余版本RV版本数据。
在一种可能的设计中，所述第二接入节点还可以向所述第一接入节点发送第二请求信息，所述第一接入节点接收第二请求信息，所述第二请求信息用于请求数据信息。第一接入节点可以根据第二接入节点的请求，向第二接入节点发送数据信息，实现不同接入节点之间的通信。
在一种可能的设计中，所述第一接入节点还可以向所述第二接入节点发送逻辑信道信息，第二接入节点接收逻辑信道信息，所述逻辑信道信息与用户数据所属用户的逻辑信道相关。第二接入节点可以根据逻辑信道信息确定向终端设备发送的数据量，从而进一步提高通信的性能。
在一种可能的设计中，所述第二接入节点还可以向所述第一接入节点发送数据信息，第一接入节点接收来自所述第二接入节点的数据信息，向终端设备发送所述数据信息。数 据信息为下行数据信息，第二接入节点作为数据源节点，可以从核心网中获取到用户的数据信息，通过第一接入节点下发给终端设备。或者第二接入节点也可以直接将数据信息下发给终端设备。
在一种可能的设计中，当所述数据信息为用户数据，或所述第二接入节点对用户数据处理后得到的RLC PDU，或所述第二接入节点对用户数据处理后得到的MAC SubPDU，或者所述第二接入节点对用户数据处理后得到的MAC PDU，所述第一接入节点向所述第二接入节点发送重传的调度信息，所述第二接入节点接收重传的调度信息。针对第一接入节点和第二接入节点交互数据的类型，在重传场景下，第一接入节点的MAC实体可以发送重传的调度信息，进而实现数据信息的重传。可选的第二接入节点为数据源节点。
在一种可能的设计中，当所述数据信息为所述第二接入节点对用户数据处理后得到的RV版本数据，所述第二接入节点向所述第一接入节点发送新的RV版本数据。所述第一接入节点接收来自所述第二接入节点的新的RV版本数据，向所述终端设备发送所述新的RV版本数据。针对第一接入节点和第二接入节点交互数据的类型，在重传场景下，第二接入节点可以生成新的RV版本数据进行重传。可选的第二接入节点为数据源节点。
在一种可能的设计中，所述第二接入节点向所述第一接入节点发送数据信息的反馈信息，所述第一接入节点接收来自所述第二接入节点的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败。第一接入节点可以根据反馈信息，决策是否进行数据信息的重传，可以进一步提高通信性能。
在一种可能的设计中，所述第一接入节点的MAC实体与所述第二接入节点的MAC实体连接；或者所述第一接入节点的MAC实体分别与所述第一接入节点的PHY实体和所述第二接入节点的PHY实体连接。
在一种可能的设计中，第一接入节点的MAC1实体与所述第二接入节点的MAC1实体连接时，还包括：所述第一节点的RLC1实体与所述MAC1实体连接；或者所述第一节点的RLC1实体分别与所述MAC1实体和所述MAC2实体连接；或者所述第一节点的RLC1实体与所述MAC1实体连接，所述第二节点的RLC2实体与所述MAC2实体连接。
第二方面，提供一种通信装置，用于实现上述各种方法。该通信装置可以为上述第一方面中的接入节点，或者包含上述接入节点的装置，或者上述接入节点中包含的装置，比如芯片；或者，该通信装置可以为上述第一方面中的终端设备，或者包含上述终端设备的装置，或者上述终端设备中包含的装置。所述通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第三方面，提供一种通信装置，包括：处理器和接口电路，该接口电路用于与该通信装置之外的模块通信；该处理器用于运行计算机程序或指令以执行上述任一方面所述的方法。该通信装置可以为上述第一方面中的接入节点，或者包含上述接入节点的装置，或者上述接入节点中包含的装置，比如芯片；或者，该通信装置可以为上述第一方面中的终端设备，或者包含上述终端设备的装置，或者上述终端设备中包含的装置。
或者，该接口电路可以为代码/数据读写接口电路，该接口电路用于接收计算机执行指令(计算机执行指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该处理器，以使该处理器运行计算机执行指令以执行上述任一方面所述的方法。
在一些可能的设计中，该通信装置可以为芯片或芯片系统。
第四方面，提供一种通信装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述任一方面所述的方法。该通信装置可以为上述第一方面中的接入节点，或者包含上述接入节点的装置，或者上述接入节点中包含的装置，比如芯片；或者，该通信装置可以为上述第一方面中的终端设备，或者包含上述终端设备的装置，或者上述终端设备中包含的装置。
第五方面，提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在通信装置上运行时，使得通信装置可以执行上述任一方面所述的方法。该通信装置可以为上述第一方面中的接入节点，或者包含上述接入节点的装置，或者上述接入节点中包含的装置，比如芯片；或者，该通信装置可以为上述第一方面中的终端设备，或者包含上述终端设备的装置，或者上述终端设备中包含的装置。
第六方面，提供一种包含指令的计算机程序产品，当其在通信装置上运行时，使得通信装置可以执行上述任一方面所述的方法。该通信装置可以为上述第一方面中的接入节点，或者包含上述接入节点的装置，或者上述接入节点中包含的装置，比如芯片；或者，该通信装置可以为上述第一方面中的终端设备，或者包含上述终端设备的装置，或者上述终端设备中包含的装置。
第七方面，提供一种通信装置(例如，该通信装置可以是芯片或芯片系统)，该通信装置包括处理器，用于实现上述任一方面中所涉及的功能。在一种可能的设计中，该通信装置还包括存储器，该存储器，用于保存必要的程序指令和数据。该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
第八方面，提供一种通信系统，该通信系统包括上述方面的第一接入节点和上述方面所述的第二接入节点。
可选的，通信系统还包括终端设备。
其中，第二方面至第八方面中任一种设计方式所带来的技术效果可参见上述第一方面中不同设计方式所带来的技术效果，此处不再赘述。
附图说明
图1为一种调度场景的示意图；
图2为一种探测参考信号切换的示意图；
图3为本申请实施例提供的一种通信系统的示意图；
图4为本申请实施例提供的另一种通信系统的示意图；
图5为本申请实施例提供的一种可能的协议层示意图；
图6为一种多制式双链接的部署场景示意图；
图7为一种协议栈中的接口示意图；
图8为一种多制式双链接协议栈的示意图；
图9为本申请实施例提供的一种通信过程示意图；
图10为本申请实施例提供的一种缓冲区状态报告的格式示意图；
图11为本申请实施例提供的一种协议栈的示意图；
图12为本申请实施例提供的一种协议栈的示意图；
图13为本申请实施例提供的一种协议栈的示意图；
图14为本申请实施例提供的一种协议栈的示意图；
图15为本申请实施例提供的一种通信方法的示意图；
图16为本申请实施例提供的又一种通信方法的示意图；
图17为本申请实施例提供的又一种通信方法的示意图；
图18为本申请实施例提供的一种MAC PDU的格式示意图；
图19为本申请实施例提供的又一种通信方法的示意图；
图20为本申请实施例提供的又一种通信方法的示意图；
图21为本申请实施例提供的又一种通信方法的示意图；
图22为本申请实施例提供的又一种通信方法的示意图；
图23为本申请实施例提供的又一种通信方法的示意图；
图24为本申请实施例提供的又一种MAC PDU的格式示意图；
图25为本申请实施例提供的一种协议栈配置方法的流程示意图；
图26为本申请实施例提供的一种通信装置的结构示意图；
图27为本申请实施例提供的又一种通信装置的结构示意图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以下对本申请实施例的部分用语进行解释说明，以便于本领域技术人员理解。
1)终端设备，也称用户设备(user equipment，UE)，是一种具有无线收发功能的设备，可以经无线接入网(radio access network，RAN)中的接入网设备(或者也可以称为接入设备)与一个或多个核心网(core network，CN)设备(或者也可以称为核心设备)进行通信。
用户设备也可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、用户代理或用户装置等。用户设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。用户设备可以是蜂窝电话(cellular phone)、无绳电话、会话启动协议(session initiation protocol，SIP)电话、智能电话(smart phone)、手机(mobile phone)、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)等。或者，用户设备还可以是具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、无人机设备或物联网、车联网中的终端、第五代移动通信(5th-generation，5G)网络以及未来网络中的任意形态的终端、中继 用户设备或者未来演进的PLMN中的终端等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。例如用户设备可以是虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。本申请实施例对终端设备的类型或种类等并不限定。
2)网络设备，指可以为终端提供无线接入功能的设备。其中，网络设备可以支持至少一种无线通信技术，例如LTE、NR等。网络设备也称网络节点或节点。
例如网络设备可以包括接入网设备(也称接入节点或节点)。示例的，网络设备包括但不限于：5G网络中的下一代节点B(generation nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、家庭基站(例如，home evolved node B、或home node B，HNB)、基带单元(baseband unit，BBU)、收发点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心、小站、微型站等。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)、和/或分布单元(distributed unit，DU)，或者网络设备可以为中继站、接入点、车载设备、终端、可穿戴设备以及未来移动通信中的网络设备或者未来演进的公共移动陆地网络(public land mobile network，PLMN)中的网络设备等。接入网设备也称接入节点。
又如，网络设备可以包括核心网(CN)设备，核心网设备例如包括接入和移动管理功能(access and mobility management function，AMF)等。
其中，一个接入网设备或接入网设备的一部分所覆盖的区域称为小区。
3)载波聚合(carrier aggregation，CA)，目前仅支持相同制式的载波进行聚合。例如当终端设备接入5G网络时，网络设备为终端设备配置的载波都是5G载波。当终端设备接入LTE网络时，网络设备为终端设备配置的载波都是LTE载波。
参与载波聚合的不同小区所对应的载波可以称为分量载波(component carrier，CC)。CA中可以包括主载波(primary component carrier，PCC)和辅载波(sencondary component carrier，SCC)。或者CA中可以包括主小区(primary cell，PCell)和辅小区(secondary cell，SCell)。PCC或SCC可以为一个或多个。PCell或SCell可以为一个或多个。
CA包括但不限于以下至少一个特性：
一个可能的特性，CA下可以实现多种载波的多进多出(multiple input multiple output，MIMO)层数的动态共享，并且可以联合优化资源配置。
一个可能的特性，CA目前支持相同制式的跨载波调度。跨载波调度是相对于自调度而言的。自调度场景下，CC1的上行数据调度信息和/或下行数据调度信息可以在CC1中发送。跨载波调度场景下，CC1的上行数据调度信息和/或下行数据调度信息可以在CC2上发送。例如图1所示，自调度场景下，CC1的下行控制信息(downlink control information，DCI)在CC1中发送，CC2的DCI在CC2中发送。跨载波调度场景下，CC1的DCI可以在CC2中发送，CC2的DCI可以在CC2中发送，此时CC1的DCI为跨载波调度，CC2的DCI为自调度。DCI用于指示物理下行共享信道(physical downlink shared channel，PDSCH)的相关调度信息。可选的，CC1的DCI和CC2的DCI可以在一个DCI中发送。 DCI可以通过物理下行控制信道(physical downlink control channel，PDCCH)承载。
接入节点可以通过无线资源控制(radio resource control，RRC)信令为终端设备配置跨载波调度配置信息。跨载波调度配置信息用于指示自调度(own)或者跨载波调度(other)。如果指示跨载波调度，跨载波调度配置信息还指示调度小区标识(schedulingCellId)和调度的载波指示域信息(carrier indicator field，CIF)，该CIF可以通过字段cif-InSchedulingCell指示，cif-InSchedulingCell可以占用3比特(bits)。跨载波调度配置信息可以为下行控制信息(downlink control information，DCI)。
跨载波调度可以均衡负载，灵活协调资源，提高频谱效率。
一个可能的特性，CA支持探测参考信号(sounding reference signal，SRS)切换(switching)。SRS可以用于上行信道估计和下行波束赋形。
针对时分双工(time division duplex，TDD)非对称CA的场景，例如下行载波多于上行载波，为了优化下行的调度，需要在SCC上调度SRS。其中该SCC为没有物理上行共享信道(physical uplink shared channel，PUSCH)的载波。由于能力受限，终端设备只能在一个cell发送上行信号。而终端设备通过SRS-CarrierSwitching的功能，可以在多个CC发送上行信号。针对上行能力受限的终端设备，支持多个上行载波间SRS快速切换，进而提升下行传输性能。
例如图2所示，终端设备在系统帧号(system frame number，SFN)的编号0-10的符号时，在CC1上发送PUSCH，在到达切换时间(Switching time)时，终端设备在SFN的编号13的符号上，切换到CC2上进行SRS传输，在切换时间结束后，终端设备在(SFN+1)的编号2的符号上切换回CC1上继续发送PUSCH。图2中切换时间从SFN的编号10的符号持续至(SFN+1)的编号1的符号。
一个可能的特性，CA支持联合(joint)上行控制信息(uplink control information，UCI)反馈(feedback)。终端设备可以将多个CC的PDSCH的确认/非确认(ACK/NACK)信息，和/或多个CC的信道状态信息(channel state information，CSI)联合编码在一个CC上反馈。Joint UCI feedback可以降低上行反馈资源的开销，提升频谱效率，提高上行传输性能。
一个可能的特性，CA的上行功率控制。CA的不同CC之间可以实现符号级的动态功率共享。终端设备可以根据优先级确定每个符号上的发送功率。每个符号上优先满足高优先级的CC上的高优先级的信道的传输。CC的优先级可以为PCC的优先级大于SCC的优先级。小区的索引(index)越小可以优先级越高。信道的优先级可以为：Pcell的物理随机接入信道(physiacal random access channel，PRACH)＞带有高优先级标识的物理上行控制信道(physical uplink control channel，PUCCH)/PUSCH＞优先级标识相同的情况下(PUCCH with混合自动重传请求(hybrid automatic repeat request，HARQ)-ACK>PUCCH with CSI)＞SRS(非周期SRS＞半静态SRS＞周期SRS)或非Pcell上的PRACH。
本申请中的“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请中所涉及的多个，是指两个或两个以上。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
本申请实施例的技术方案可以应用于移动通信系统，也可以应用于卫星通信系统，其中，卫星通信系统可以与传统的移动通信系统相融合。例如：移动通信系统可以为第四代移动通信(4th-generation，4G)通信系统(例如，LTE系统)，5G通信系统(例如，NR系统)，及未来的移动通信系统，或者其它通信系统等。本申请实施例也可以适用于同构网络，异构网络的场景中。在同构网络和异构网络的场景中，对于传输点不做限制，例如可以是宏基站与宏基站、微基站与微基站和宏基站与微基站间的多点协同传输。本申请实施例也可以应用于频分双工(frequency division duplex，FDD)系统/TDD系统。本申请实施例也可以适用于CU/DU分离架构。本申请实施例也可以适用于控制面/用户面(Control Plane/User Plane，CP/UP)分离架构。本申请实施例也可以适用于低频(如sub 6G)场景，高频(如6G以上)场景，太赫兹通信场景，光通信场景等。只要能够实现信号传输的通信系统均可以，在本申请实施例中不做限制。
如图3所示，为一种可能的通信系统的示意图，通信系统中包括网络设备和终端设备。网络设备可以为一个或多个，终端设备可以为一个或多个。网络设备可以向终端设备发送信号，终端设备也可以向网络设备发送信号。
如图4所示，为又一种可能的通信系统的示意图，通信系统中包括终端设备，接入网(包括接入网设备)和核心网(包括核心网设备)。可选的，通信系统中还可以包括数据网络(data network，DN)。
数据网络通常可以部署在运营商网络之外，例如第三方网络。示例的，运营商网络可以接入多个数据网络，数据网络上可部署多种业务，从而为终端设备提供数据和/或语音等服务。
核心网主要负责终端用户的移动管理，会话管理以及数据传输等。
接入网中的网元包括基站。基站负责空中接口相关的功能，例如无线链路维护功能，保持与终端设备间的无线链路，同时负责无线链路数据和网络互连协议(internet protocol，IP)数据之间的协议转换；又如无线资源管理功能，包括无线链路的建立和释放、无线资源的调度和分配等；又如移动性管理功能，包括配置终端进行测量、评估终端无线链路质量、决策终端在小区间的切换等。基站可以包括用户面(user plane)协议和控制面(control plane)协议。
终端设备可以包括用户面协议和控制面协议。终端设备可以与基站通过空口进行交互。如图5所示，终端设备的各协议层可以与基站的各协议层相互连接，进行信息的传递。协议层包括物理层(physical layer，PHY)，媒体接入控制层(medium access control，MAC)，无线链路控制层(radio link control，RLC)，分组数据汇聚协议层(packet data convergence protocol，PDCP)，无线资源控制层(radio resource control，RRC)，业务数据适配协议(service data adapation protocol，SDAP)。其中SDAP属于用户面协议层，RRC属于控制面协议层。
为了理解本申请实施例，下面对相关技术进行说明。
NR标准支持X-无线接入技术(radio access technology，RAT)双链接(dual connectivity，DC)，也即MR-DC。MR-DC包括主节点(master node，MN)和辅节点(secondary node，SN)。如图6所示，NR版本(release，R)15中针对不同的部署场景和DC演进路线，提出了MR-DC的多种选项(option，opt)。用户面连接用实线示出，控制面连接用虚线示出。
opt2系列，也称为NR DC，主节点和辅节点都为NR基站(gNB)，gNB与5G CN连 接5G CN，如AMF和用户面功能(user plane function，UPF)。opt3系列，也称演进的通用陆面无线接入网络新无线(Evolved Universal Terrestrial Radio Access Network NR，EUTRAN NR，EN)-DC，主节点为LTE基站(e-eNB)，辅节点为NR基站(gNB)，主节点和辅节点连接4G CN，如移动管理实体(mobility management entity，MME)和服务网关(serving gateway，SGW)。opt4系列，也称新无线演进的通用陆面无线接入网络(NR EUTRAN，NE)-DC，主节点为gNB，辅节点为e-eNB，主节点和辅节点连接5G CN，如AMF和UPF。opt7系列，也称新无线演进的通用陆面无线接入网络新无线(NR EUTRAN NR，NGEN)-DC，主节点为e-eNB，辅节点为gNB，主节点和辅节点连接5G CN，如AMF和UPF。
以及NR R15提供了协议栈1和协议栈2。协议栈1称为MR-DC with EPC，或者可以为上述EN-DC架构。协议栈2称为MR-DC with 5GC，可以包括上述NE-DC、NGEN-DC和NR-DC架构。图7中示出了协议栈1的接口(图7中的(a))和协议栈2的接口(图7中的(b))。协议栈1采用S1和X2接口，协议栈2采用Ng和Xn接口。
以MR-DC协议栈中的EN-DC架构为例，UE侧的协议栈如图8所示。MN和SN有各自的RRC层，分别为RRC1和RRC2，控制面协议栈为完整的RRC/PDCP/RLC/MAC/PHY。MN的制式为LTE，SN的制式为NR。针对MR-DC的分离承载(split bearer)，用户面协议栈为SDAP/PDCP/RLC/MAC/PHY，其中一个PDCP实体同时连接MN和SN的RLC/MAC/PHY，该PDCP可以进行数据分流来提升终端设备的瞬时速率(如数据包1/3/5/…走MN，数据包2/4/6/…走SN)、PDCP也可以进行包复制来提升可靠性(如数据包1/2/3/…走MN、数据包1/2/3/…同时走SN)。
NR标准中支持MR-DC，并且后续NR版本也是基于MR-DC进行演进。
而X-RAT CA(也即多制式载波聚合(multi radio-carrier aggregation，MR-CA))需要LTE基站和NR基站之间是理想backhaul(一般只有光纤才能满足该需求)，大部分国家或地区的光纤部署极其稀缺，因此X-RAT CA的实际部署概率低，因此NR标准中暂不支持MR-CA。
综上可知，目前MR-DC不支持多载波间的聚合，无法支持不同载波间的动态/实时的调度协商、以及跨载波调度、联合UCI反馈等CA特性，因此通信性能较差。
鉴于此，本申请实施例提供的一种通信方法，该通信方法也可以支持不同制式的载波进行聚合，如支持MR-CA，接入节点之间可以进行通信，从而实现CA特性，提升通信性能。本申请实施例一种可能的场景中，节点之间是理想backhaul(例如节点之间通过光纤部署，或者节点之间共站时部署有低时延线缆)，且节点之间的传输时间短(例如小于1毫秒(ms))。
本申请实施例提供的通信方法可以应用于上述图3和图4所示的通信系统中。图9为本申请实施例提供的一种可能的通信方法，该通信方法可以实现MR-CA协议栈中接入节点之间的通信，包括以下步骤：
S901：第一接入节点确定调度信息。
可以理解，本申请实施例涉及的第一接入节点可以为调度节点，被调度节点或第三方节点，第二接入节点可以为调度节点，被调度节点或第三方节点。这里以第一接入节点为调度节点，第二接入节点为被调度节点进行说明。第一接入节点的制式和第二接入节点的 制式可以相同或不同。
本申请实施例中所涉及的“制式”，可以是3G/宽带码分多址(wideband code division multiple access，WCDMA)/通用移动通信系统(universal mobile telecommunications system，UMTS)/码分多址(code division multiple access，CDMA)/时分同步码分多址(time division-synchronous code division multiple access，TD-SCDMA)、4G/LTE、5G/NR、6G、7G等任意制式及系统。
调度信息可以用于指示第二接入节点接收数据或发送数据的资源信息。
调度信息可以包括下行调度信息，下行调度信息可以用于指示发送数据的资源信息，该发送数据的资源信息为下行资源信息。下行调度信息用于生成下行调度配置信息，下行调度配置信息可以为终端设备分配下行资源信息。可选的，调度信息可以包括调度结果，和/或用于生成下行调度配置信息的中间信息(如果有的话)，和/或下行调度配置信息。例如下行调度配置信息为DCI(也称DCI format或DCI container)，用于生成DCI的中间信息为一个或多个DCI信元。其中DCI可以由一个或多个DCI信元组成，DCI信元可以由调度结果生成。调度信息可以为调度结果，或者调度信息可以包括一个或多个DCI信元，或者调度信息可以包括DCI。
调度信息可以包括上行调度信息，上行调度信息可以用于指示接收数据的资源信息，该接收数据的资源信息为上行资源信息。上行调度信息用于生成上行调度配置信息，上行调度配置信息可以为终端设备分配上行资源信息。上行调度信息可以包括但不限于以下一个或多个：随机接入信道(random access channel，RACH)的调度信息，调度请求(scheduling request，SR)调度信息，缓冲区状态报告(buffer status report，BSR)的调度信息，或CSI的调度信息。可选的，调度信息可以包括调度结果，和/或用于生成上行调度配置信息的中间信息(如果有的话)，和/或上行调度配置信息。
第一接入节点作为调度节点，可以生成调度结果。
一种可能的方式中，若调度信息包括一个或多个DCI信元或DCI，在S901中，第一接入节点可以根据调度结果，生成一个或多个DCI信元，或生成DCI。
另一种可能的方式中，在S901中，第一接入节点可以接收来自其它接入节点(如第二接入节点)的调度信息。例如第一接入节点向其它接入节点发送第一请求信息，该第一请求信息用于请求调度信息，其它接入节点向该第一接入节点发送调度信息。第一请求信息可选的包括调度结果(例如在其它接入节点不能生成调度结果的情况下)。在一些可能的情况下，若第一接入节点没有DCI信元的生成能力，第一请求信息可以用于请求生成DCI信元，若第一接入节点没有DCI的生成能力，第一请求信息可以用于请求生成DCI。
调度结果包括但不限于以下至少一个信息：调度资源信息，调制与编码策略(modulation and coding scheme，MCS)，上行功控(transmit power control，TPC)，触发(triggered)CSI/SRS，冗余版本(redundancy version，RV)，HARQ进程标识(HARQ process id)，网络设备接口(network device interface，NDI)，天线端口等。
DCI可以包括但不限于以下至少一个信息：DCI格式指示信息(用于指示上行或下行)，载波指示域(carrier indicator)，带宽部分指示(bandwidth part indicator)，频域资源分配，时域资源分配，频域跳频指示，虚拟资源块(virtual resource block，VRB)到物理资源块(physical resource block，PRB)的映射(VRB-to-PRB mapping)，物理资源块捆绑大小指示(PRB bundling size indicator)，MCS，新数据指示(New data indicator)，冗余版本 (Redundancy version,RV)，HARQ进程数(HARQ process number)，HARQ定时，传输功率控制命令(TPC command for scheduled PUSCH)，上行或辅助上行(supplementary uplink，SUL)指示(UL/SUL indicator)，预编码信息和层数(Precoding information and number of layers)，天线端口(Antenna ports)，SRS资源指示(SRS resource indicator)，SRS请求(SRS request)，CSI请求(CSI request)，码块组(code block group，CBG)传输信息(CBG transmission information，CBGTI)，相位追踪参考信号(phase-tracking reference signal，PTRS)-解调参考信号(demodulation reference signal，DMRS)关联(PTRS-DMRS association)，DMRS序列初始化(DMRS sequence initialization)，开环功控参数集合指示(Open-loop power control parameter set indication)，优先级指示(Priority indicator)，无效符号图案指示(Invalid symbol pattern indicator)，最小适用的调度偏移指示(Minimum applicable scheduling offset indicator)，辅小区休眠指示(SCell dormancy indication)，下行分配指示(Downlink assignment index)，beta偏置指示(beta_offset indicator)，UL-同步信道(synchronization channel，SCH)indicator，PUCCH资源指示(PUCCH resource indicator)，信道接入(ChannelAccess-CPext)，速率匹配指示(Rate matching indicator)，零功率信道状态信息参考信号触发(zero power channel state information-reference siganal，ZP CSI-RS trigger)，单次HARQ请求(One-shot HARQ-ACK request)，PDSCH组标识(PDSCH group index)，新的反馈指示(New feedback indicator)，请求的PDSCH组数(Number of requested PDSCH group(s))，传输配置指示(Transmission configuration indication)。
S902：第一接入节点向第二接入节点发送调度信息，第二接入节点接收该调度信息。
第一接入节点可以通过第一通信方式，与第二接入节点进行交互。该第一通信方式支持不同制式间的载波聚合。该第一通信方式可以基于第一协议栈进行通信。可选的，第一协议栈可以是对已有协议栈(例如MR-DC协议栈)进行改进，来支持第一通信方式。第一协议栈将在后续实施例中进行说明。
S903：第二接入节点确定接收数据或发送数据的资源信息。
第二接入节点可以根据调度信息的指示，确定第二接入节点接收数据或发送数据的资源信息，即确定上行资源信息或下行资源信息。
可选的，第二接入节点可以通过动态调度或半静态调度的方式，向终端设备发送该第二接入节点接收数据或发送数据的资源信息。第二接入节点和终端设备可以基于该第二接入节点接收数据的资源信息或发送数据的资源信息，进行交互。
例如第二接入节点通过动态调度的方式，向终端设备发送该第二接入节点发送数据的资源信息。第二接入节点可以发送DL动态授权(dynamic grant，DG)配置信息，DL DG配置信息包括第二接入节点发送数据的资源信息。例如DL DG配置信息为DCI。
如果调度信息包括一个或多个DCI信元，第二接入节点在接收到该调度信息后，可以根据一个或多个DCI信元，生成DCI，将该DCI发送给终端设备。如果调度信息包括DCI，第二接入节点在接收到该调度信息后，将DCI(透明发送/透传)发送给终端设备。
又如第二接入节点通过半静态调度的方式，向终端设备发送该第二接入节点发送数据的资源信息。第二接入节点可以发送DL SPS信息，或者发送DL CG配置信息，DL SPS信息或DL CG配置信息包括第二接入节点发送数据的资源信息。
又如第二接入节点通过动态调度的方式，向终端设备发送该第二接入节点接收数据的资源信息。第二接入节点可以发送UL DG配置信息，UL DG配置信息包括第二接入节点 接收数据的资源信息。
又如第二接入节点通过半静态调度的方式，向终端设备发送该第二接入节点接收数据资源信息。第二接入节点可以发送UL SPS信息或UL CG配置信息，UL SPS信息或UL CG配置信息包括第二接入节点发送数据的资源信息。
可选的，在跨载波调度场景下，或第一接入节点非调度节点的情况下，第一接入节点还可以接收来自其它节点的其它调度信息，该其它调度信息可以用于指示第一接入节点接收数据或发送数据的资源信息。第一接入节点可以通过动态调度或半静态调度的方式，向终端设备发送第一接入节点发送数据或接收数据的资源信息。
DL SPS信息，DL CG配置信息，UL SPS信息或UL CG配置信息，可以包括但不限于以下至少一个信息：是否跳频(frequencyHopping)，cg-DMRS-Configuration，MCS表格(mcs-Table)，半静态或动态UCI配置(uci-OnPUSCH)，资源分配类型(resourceAllocation)，RBG大小(rbg-Size)，功控选择(powerControlLoopToUse)，P0、Alpha等功控参数配置(p0-PUSCH-Alpha)，转换预编码器(transformPrecoder)，并行HARQ process数目(nrofHARQ-Processes)，重复次数(repK)，每次重复对应的RV版本号(repK-RV)，CG时域周期(periodicity)，定时器时长配置(configuredGrantTimer)，时间偏置(timeDomainOffset)，时间域分配(timeDomainAllocation)，频率域分配(frequencyDomainAllocation)，天线端口(antennaPort)，DMRS序列初始化(dmrs-SeqInitialization)，预编码和层数(precoding And Number Of Layers)，SRS资源标识(srs-ResourceIndicator)，MCS和传输块大小(transport block size，TBS)(mcsAndTBS)，频域调频的偏置(frequencyHoppingOffset)，路损参考索引(pathlossReferenceIndex)，PUSCH重复类型标识(pusch-RepTypeIndicator-r16)，PUSCH调频重复类型(frequencyHoppingPUSCH-RepTypeB-r16)，时间参考系统帧号(system frame number，SFN)(timeReferenceSFN-r16)。
可选的，第一接入节点和第二接入节点之间还可以交互数据信息，包括DL数据信息和/或UL数据信息。
这里主要以DL数据信息进行说明。在第一接入节点为数据源节点时，第一接入节点可以向其它接入节点(如第二接入节点)发送数据信息。该数据信息为该其它接入节点的数据信息，例如该数据信息为第二接入节点的数据信息。
数据信息可以为(未经过处理的)用户数据。或者该数据信息可以为第一接入节点对用户数据处理后得到的RLC协议数据单元(protocol data unit，PDU)，可选的，第一接入节点的RLC实体对用户数据进行处理，得到RLC PDU。或者该数据信息可以为第一接入节点对用户数据处理后得到的MAC子(Sub)PDU。可选的，第一接入节点的MAC实体对RLC PDU或MAC业务数据单元(service data unit，SDU)，添加MAC子头部(subheader)后得到的MAC SubPDU。或者该数据信息可以为第一接入节点对用户数据处理后得到的MAC PDU，可选的，第一接入节点的MAC实体将一个或多个MAC SubPDU级联后得到的MAC PDU，MAC PDU也称MAC传输块(transport block，TB)。或者该数据信息可以为第一接入节点对用户数据处理后得到的RV版本数据，可选的，RV版本数据包括但不限于用户数据和RV版本号等信息。
可选的，其它接入节点可以向第一接入节点发送第二请求信息，第二请求信息用于请 求数据信息。第一接入节点可以在接收到该第二请求信息后，向其它接入节点发送数据信息。其它接入节点可以每(per)发送时间间隔(transmission time interval，TTI)(per TTI)向第一接入节点请求数据信息，例如其它接入节点可以每隔TTI向第一接入节点发送一次第二请求信息。或者其它接入节点可以请求第一接入节点多次TTI调度的数据信息，例如其它接入节点可以向第一接入节点发送一次第二请求信息，该第二请求信息用于请求多次TTI的数据信息。
第二请求信息包括但不限于以下至少一个信息：用户标识(UE id，如小区无线网络临时标识(cell-radio network temporary identifier，C-RNTI))，RV版本号(第一接入节点可以发送RV版本数据)，用于请求MAC PDU的信息(第一接入节点可以发送MAC PDU)，TBS，RLC PDU size，授权信息(grant info)，符合条件的逻辑信道(logical channel，LCH)标识列表(LCH id list)，与逻辑信道优先级(Logical Channel Prioritization，LCP)限制(restriction)相关的信息。其中与LCP restriction相关的信息包括但限于以下至少一个信息：子载波间隔(sub-carrier spacing，SCS)/免授权(grant free，GF)类型(type)1，PUSCH Duration，服务小区标识(Serving Cell id(s))，小区组标识(cell group id，CG id)，物理层优先级索引(PHY priority index)等。
如果第二接入节点为数据传输节点，第一接入节点还可以向第二接入节点发送逻辑信道信息，逻辑信道信息与用户数据所属用户的LCH相关。例如逻辑信道信息包括但不限于以下至少一个信息：LCH priority，LCH的令牌桶大小持续时间(bucket size duration，BSD)和LCH的优先级比特率(prioritised bit rate，PBR)等，其中LCH的令牌BSD也称为LCH的令牌桶深。第二接入节点可以根据逻辑信道信息，确定向终端设备发送的数据量，然后发送该数据量的数据信息/用户数据，可以进一步提高通信性能。第一接入节点确定逻辑信道信息的过程可以参见UE-通用陆面无线接入网络(UE-Universal Terrestrial Radio Access Network，Uu)(一种接口)上令牌桶机制，此处不做赘述。
可选的，第二接入节点接收数据或发送数据的资源信息包括用于重传的指示信息，例如DCI包括用于重传的指示信息。当数据信息为用户数据，或者该数据信息为第一接入节点对用户数据处理后得到的RLC PDU，或者该数据信息为第一接入节点对用户数据处理后得到的MAC SubPDU，或者该数据信息为第一接入节点对用户数据处理后得到的MAC PDU时，第一接入节点可以重新向第二接入节点发送数据信息。可选的，第二接入节点在接收到重发的数据信息之前，第一接入节点可以重新发送调度信息。当数据信息为第一接入节点对用户数据处理后得到的RV版本数据时，第一接入节点可以生成新的RV版本数据，向第二接入节点发送该新的RV版本数据。
在第一接入节点非数据源节点(如数据传输节点)时，第一接入节点可以接收来自其它接入节点(如第二接入节点)的数据信息。该数据信息为第一接入节点的数据信息。
数据信息可以为(未经过处理)用户数据。或者该数据信息可以为第二接入节点对用户数据处理后得到的RLC PDU。或者该数据信息可以为第二接入节点对用户数据处理后得到的MAC SubPDU。或者该数据信息可以为第二接入节点对用户数据处理后得到的MAC PDU。或者该数据信息可以为第二接入节点对用户数据处理后得到的RV版本数据。
可选的，第二接入节点接收数据或发送数据的资源信息包括用于重传的指示信息，例如DCI包括用于重传的指示信息。当数据信息为用户数据，或者数据信息为第二接入节点对用户数据处理后得到的RLC PDU，或者数据信息为第二接入节点对用户数据处理后得到 的MAC SubPDU，或者该数据信息为第二接入节点对用户数据处理后得到的MAC PDU时，第一接入节点可以向第二接入节点重新发送调度信息，第二接入节点可以向终端设备重新发送数据信息。当数据信息为第二接入节点对用户数据处理后得到的RV版本数据，第二接入节点可以生成新的RV版本数据，向第一接入节点发送该新的RV版本数据，第一接入节点向终端设备发送该新的RV版本数据。
可选的，调度信息包括RV版本号。
可选的，终端设备可以上报数据信息的反馈结果，例如终端设备可以向第二接入节点发送反馈结果，表示终端设备接收数据信息成功或失败。第二接入节点可以向第一接入节点发送反馈信息，该反馈信息用于反馈数据信息发送成功或失败。若根据反馈信息确定重传数据信息，则可以按照上述第二接入节点接收数据或发送数据的资源信息包括用于重传的指示信息的情况进行处理，在此不做赘述。
示例的，反馈信息包括但不限于以下至少一个信息：RAT标识(RAT id)，频点标识(Freq id)，载波标识(CC id)，小区标识(Cell id)，用户标识(UE id)，ACK/NACK时频域位置，HARQ进程标识(HARQ process id)，ACK/NACK/不连续传输(discrete transmission，DTX)结果。可选的，ACK/NACK时频域位置和HARQ process id可以替换使用。ACK表示终端设备成功接收数据信息，第一接入节点和第二接入节点可以不重传数据信息。NACK表示终端设备未成功接收数据信息，第一接入节点和第二接入节点可以重传数据。DTX表示未接收到终端设备的ACK/NACK的反馈信息，此时第一接入节点和第二节点可以重传或者不重传数据信息。
可选的，第一接入节点和第二接入节点还可以接收上行信息，上行信息包括以下至少一个信息：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息。随机信道接入信息(RACH信息)可以包括随机接入前导资源(preamble资源)的时频域位置和前导码标识(preamble id)。调度请求(SR信息)可以包括以下信息中的一个或多个：调度请求资源的时频域位置(这时接入节点提前获知SR与LCH(s)或LCG(s)的关联关系)，调度请求资源对应的用户标识(如C-RNTI)，或调度请求资源对应的逻辑信道标识或逻辑信道组标识(如LCH(s)id或LCH(s)priority或LCG(s)id)。缓冲状态报告可以包括BSR原始信息(如包括RAT id，CC id，Cell id，UE id，LCG id和Buffer size等)，或者BSR container(对BSR原始信息处理得到，可以直接透传)。信道状态信息可以包括上行信道状态信息和/或下行信道状态信息。上行信道状态信息可以包括以下至少一个信息：RAT id，CC id，Cell id，UE id，CSI原始信息，CSI container。下行信道状态信息可以包括以下至少一个信息：RAT id，CC id，Cell id，UE id，SRS测量结果，SRS id。BSR可以包括长格式和短格式。如图10中的(a)所示，为一种可能的BSR的格式(短格式)，BSR包含一个逻辑信道组(logic channel group，LCG)id字段，和一个缓冲区大小(Buffer Size)字段，其中LCG id字段为逻辑信道组标识，Buffer Size字段为数据量大小范围的标识。如图10中的(b)所示，为另一种可能的BSR的格式(如长格式)，BSR包含多个LCG id字段(如7个LCG)，和多个Buffer Size字段(如m个Buffer Size字段)。
在本申请实施例中，不同接入节点之间可以进行调度或用户数据等的互联互通，可以提升通信性能。并且还可以实现不同制式的接入节点之间的互联互通，也可以实现不同厂商的接入节点之间的互联互通，从而实现CA特性，进一步提升通信性能。
本申请实施例还提供了第一协议栈。第一协议栈适用于网络侧和终端设备侧。以第一 接入节点和第二接入节点，第一协议栈为MR-CA为例进行说明。第一接入节点的制式和第二接入节点的制式可以相同或不同。
一种可能的MR-CA协议栈中，一个MAC实体可以连接多个不同制式的PHY实体。DRB和/或逻辑信道(logical channel，LCH)所对应的SDAP实体/PDCP实体/RLC实体共享同一个MAC实体。控制面所对应的RRC实体/PDCP实体/RLC实体共享同一个MAC实体。
网络侧的用户面协议栈模型如图11中的(a)所示，第一接入节点的PHY1实体和第二接入节点的PHY2实体分别与MAC实体/RLC实体/PDCP实体/SDAP实体连接。第一接入节点的制式为RAT1，第二接入节点的制式为RAT2，RAT1与RAT2可以相同或不同。
可选的，PHY1实体/MAC实体/RLC实体/PDCP实体/SDAP实体可以同属于第一接入节点，而PHY2实体属于第二接入节点。或者PHY1实体属于第一接入节点，而PHY2实体/MAC实体/RLC实体/PDCP实体/SDAP实体可以同属于第二接入节点。
若PHY1实体与MAC实体同属于第一接入节点，PHY2实体属于第二接入节点，PHY2实体和MAC实体通过第一接入节点和第二接入节点之间的站间接口交互信息，PHY2实体和MAC实体之间的接口可以为私有接口(如PHY2实体/PHY1实体/MAC实体/RLC实体/PDCP实体/SDAP实体等属于同一厂商的情况下)，或者可以为标准化接口(如PHY2实体/PHY1实体/MAC实体/RLC实体/PDCP实体/SDAP实体等属于不同厂商的情况下)。
网络侧的控制面协议栈模型如图11中的(b)所示，控制面协议栈模型与用户面协议栈模型的区别在于，控制面协议栈模型中包括RRC实体，用户面协议栈模型中包括SDAP实体，相似之处不做赘述。
终端设备侧的用户面协议栈模型、控制面协议栈模型，与网络侧的用户面协议栈模型、控制面协议栈模型相似。区别在于终端设备中PHY2实体/PHY1实体/MAC实体/RLC实体/PDCP实体/SDAP实体属于同一厂商，因此PHY2实体/PHY1实体/MAC实体之间的接口可以采用私有接口实现，或者也可以采用标准化接口实现。
但是对于终端设备来说，网络侧的协议栈模型中，一个MAC实体关联多个PHY实体，同时可以关联一个或多个DRB/LCH的配置。其中一个DRB关联一个PDCP实体，每个LCH关联一个RLC实体。而第一DRB可以关联至少一个LCH，即第一PDCP实体可以关联多个RLC实体。
一种可能的MR-CA协议栈中，不同RAT的PHY实体连接各自对应的MAC实体。DRB和/或LCH连接一个MAC实体，不同MAC实体之间连接，有接口进行交互。用户面所对应的SDAP实体/PDCP实体/RLC实体共享一个MAC实体。控制面RRC实体/PDCP实体/RLC实体共享同一个MAC实体。第一接入节点的制式为RAT1，第二接入节点的制式为RAT2，RAT1与RAT2可以相同或不同。
网络侧的用户面协议栈如图12中的(a)所示，第一接入节点的PHY1实体和第一接入节点的MAC1实体连接，第二接入节点的PHY2实体和第二接入节点的MAC2实体连接，MAC1实体和MAC2实体可以通过第一接入节点和第二接入节点之间的站间接口交互信息。RLC实体/PDCP实体/SDAP实体连接MAC1实体或MAC2实体。
可选的，PHY1实体/MAC1实体/RLC实体/PDCP实体/SDAP实体可以同属于第一接入节点，而PHY2实体/MAC2实体属于第二接入节点。第一接入节点和第二接入节点之间可以交互PHY实体的信息和MAC实体的信息。MAC1实体和MAC2实体之间的接口可 以为私有接口，或者可以为标准化接口。
网络侧的控制面协议栈模型如图12中的(b)所示，控制面协议栈模型与用户面协议栈模型的区别在于，控制面协议栈模型中包括RRC实体，用户面协议栈模型中包括SDAP实体，相似之处不做赘述。
终端设备侧的用户面协议栈模型、控制面协议栈模型，与网络侧的用户面协议栈模型、控制面协议栈模型相似。区别在于终端设备中PHY2实体/PHY1实体/MAC实体/RLC实体/PDCP实体/SDAP实体属于同一厂商，因此MAC1实体/MAC2实体之间的接口可以采用私有接口实现，或者也可以采用标准化接口实现。
但是对于终端设备来说，网络侧的协议栈模型中，有多个MAC实体，每个MAC实体关联一个PHY实体。多个MAC实体中的一个MAC实体关联一个或多个DRB/LCH的配置。网络侧可以显式/隐式向终端设备配置两个MAC实体之间存在接口，该过程可以参见图14中第一配置信息的配置过程，这里不再赘述。
一种可能的MR-CA协议栈中，不同RAT的PHY实体连接各自对应的MAC实体。DRB和/或LCH连接不同的MAC实体，不同MAC实体之间连接，有接口进行交互。用户面所对应的SDAP实体/PDCP实体/RLC实体共享多个MAC实体。控制面RRC实体/PDCP实体/RLC实体共享多个MAC实体。第一接入节点的制式为RAT1，第二接入节点的制式为RAT2，RAT1与RAT2可以相同或不同。
网络侧的用户面协议栈如图13中的(a)所示，第一接入节点的PHY1实体和第一接入节点的MAC1实体连接，第二接入节点的PHY2实体和第二接入节点的MAC2实体连接，MAC1实体和MAC2实体可以通过第一接入节点和第二接入节点之间的站间接口交互信息。RLC实体/PDCP实体/SDAP实体分别连接MAC1实体和MAC2实体。
可选的，PHY1实体/MAC1实体/RLC实体/PDCP实体/SDAP实体可以同属于第一接入节点，而PHY2实体/MAC2实体属于第二接入节点。第一接入节点和第二接入节点之间可以交互PHY实体的信息、MAC实体和RLC实体的信息。MAC1实体和MAC2实体之间的接口可以为私有接口，或者可以为标准化接口。RLC实体和MAC2实体之间的接口可以为私有接口，或者可以为标准化接口。
网络侧的控制面协议栈模型如图13中的(b)所示，控制面协议栈模型与用户面协议栈模型的区别在于，控制面协议栈模型中包括RRC实体，用户面协议栈模型中包括SDAP实体，相似之处不做赘述。
终端设备侧的用户面协议栈模型、控制面协议栈模型，与网络侧的用户面协议栈模型、控制面协议栈模型相似。区别在于终端设备中PHY2实体/PHY1实体/MAC实体/RLC实体/PDCP实体/SDAP实体属于同一厂商，因此MAC1实体/MAC2实体/RLC实体之间的接口可以采用私有接口实现，或者也可以采用标准化接口实现。
但是对于终端设备来说，网络侧的协议栈模型中，有多个MAC实体，每个MAC实体关联一个PHY实体。多个MAC实体中的每个MAC实体关联一个或多个DRB/LCH的配置。网络侧可以显式/隐式向终端设备配置两个MAC实体之间存在接口，该过程可以参见图14中第一配置信息的配置过程，这里不再赘述。
一种可能的MR-CA协议栈中，不同RAT的PHY实体连接各自对应的MAC实体/RLC实体。DRB和/或LCH连接不同的MAC实体，不同MAC实体之间连接，有接口进行交互。用户面所对应的SDAP实体/PDCP实体共享多个MAC实体。控制面RRC实体/PDCP 实体共享多个MAC实体。第一接入节点的制式为RAT1，第二接入节点的制式为RAT2，RAT1与RAT2可以相同或不同。
网络侧的用户面协议栈如图14中的(a)所示，第一接入节点的PHY1实体和第一接入节点的MAC1实体连接，MAC1实体与第一接入节点的RLC1实体连接。第二接入节点的PHY2实体和第二接入节点的MAC2实体连接，MAC2实体与第二接入节点的RLC2实体连接。MAC1实体和MAC2实体可以通过第一接入节点和第二接入节点之间的站间接口交互信息。PDCP实体/SDAP实体分别连接RLC1实体和RLC2实体。
可选的，PHY1实体/MAC1实体/RLC1实体/PDCP实体/SDAP实体可以同属于第一接入节点，而PHY2实体/MAC2实体/RLC2实体属于第二接入节点。第一接入节点和第二接入节点之间可以交互PHY实体的信息和MAC实体。MAC1实体和MAC2实体之间的接口可以为私有接口，或者可以为标准化接口。RLC1实体/RLC2实体/PDCP实体之间的接口可以为私有接口，或者可以为标准化接口。
网络侧的控制面协议栈模型如图14中的(b)所示，控制面协议栈模型与用户面协议栈模型的区别在于，控制面协议栈模型中包括RRC实体，用户面协议栈模型中包括SDAP实体，相似之处不做赘述。
终端设备侧的用户面协议栈模型、控制面协议栈模型，与网络侧的用户面协议栈模型、控制面协议栈模型相似。区别在于终端设备中PHY2实体/PHY1实体/MAC实体/RLC实体/PDCP实体/SDAP实体属于同一厂商，因此MAC1实体/MAC2实体/RLC1实体/RLC2实体/PDCP实体之间的接口可以采用私有接口实现，或者也可以采用标准化接口实现。
但是对于终端设备来说，网络侧可以显式/隐式向终端设备配置两个MAC实体之间是否存在接口，从而指示网络侧的协议栈模型为MR-DC还是MR-CA，该过程可以参见图14中第一配置信息的配置过程，这里不再赘述。
图14中(a)和图14中的(b)所示的MR-CA协议栈模型，与MR-DC协议栈模型的区别在于MAC实体之间是否有接口。例如MR-CA协议栈模型中MAC实体之间有接口，可以交互信息，而MR-DC协议栈模型中RLC之间有接口，可以交互信息。
下面以图12(a)所示的协议栈为例，对本申请实施例适用的不同场景进行说明。其中网络设备1下的小区为CA中的主小区(primary cell，PCell)，网络设备2下的小区为CA中的辅小区(secondary cell，SCell)。
一种可能的场景为自调度场景(例如图1所示)，自调度场景中可以分为集中调度和分布调度，自调度场景中可以分为集中DCI生成和分布DCI生成。需要说明，这里主要以通过动态调度的方式进行下行资源信息的调度为例进行说明，对于半静态调度以及调度上行资源信息的过程相似，这里不做赘述。
这里假设PCell的调度器在PCell上，若SCell的调度器在PCell上(SCell不具有调度能力，PCell为调度节点)，则为集中调度，若SCell的调度器在SCell上(SCell具有调度能力，SCell为调度节点)，则为分布调度。
假设PCell有生成DCI信元/DCI的能力，若SCell没有生成DCI信元/DCI的能力，则为集中DCI生成，若SCell有生成DCI信元/DCI的能力，则为分布DCI生成。
这里假设网络设备具有调度能力，或者生成DCI信元/DCI的能力，也可以假设其它第三方节点具有这些能力。
如图15中的(a)所示，为集中调度和分布DCI生成。
步骤1(参见图15中的(a)中的①)，PCell(或PCell的MAC1实体)生成SCell的调度结果。调度结果用于生成(一个或多个)DCI信元，(一个或多个)DCI信元可以组成DCI。PCell具有调度能力，可以为上述第一接入节点，SCell可以为上述第二接入节点。
步骤2(参见图15中的(a)中的②)，PCell(或PCell的MAC1实体)可以通过站间接口向SCell(或SCell的MAC2实体)发送调度结果，或DCI信元。例如PCell可以通过基站间直连接口向SCell发送调度结果或DCI信元。或者PCell可以通过第三方接入节点将调度结果或DCI信元，转发给SCell。或者PCell可以通过核心网或操作管理维护(operation administration maintenance，OAM)网元将调度结果或DCI信元，转发给SCell。
步骤3(参见图15中的(a)中的③)，SCell(或SCell的MAC2实体)根据调度结果或DCI信元，生成DCI。
步骤4(参见图15中的(a)中的④)，SCell(或SCell的MAC2实体)在SCell所在的载波上通过空口将DCI发送给终端设备。
如图15中的(b)所示，为集中调度和集中DCI生成。
步骤1(参见图15中的(b)中的①)，PCell生成SCell的调度结果。PCell具有调度能力，可以为上述第一接入节点，SCell可以为上述第二接入节点。
步骤2(参见图15中的(b)中的②)，PCell根据调度结果，生成SCell的DCI。
步骤3(参见图15中的(b)中的③)，PCell可以通过站间接口向SCell发送DCI。
步骤4(参见图15中的(b)中的④)，SCell在SCell所在的载波上通过空口将DCI发送给终端设备。DCI对于网络设备2和SCell都是透明的，也就是说SCell接收到DCI后，可以不解析该DCI包括哪些信元以及信元的值，而可以通过SCell所在的载波的空口向终端设备透传该DCI。
如图15中的(c)所示，为分布调度和分布DCI生成。
步骤1(参见图15中的(c)中的①)，SCell生成SCell自己的调度结果。SCell具有调度能力，可以为上述第一接入节点，PCell可以为上述第二接入节点。
步骤2(参见图15中的(c)中的②)，SCell没有生成DCI信元的能力的情况下，SCell向PCell发送请求信息，用于请求PCell生成DCI信元。该请求信息中可以包括(用于生成DCI信元的)调度结果。
步骤3(参见图15中的(c)中的③)，PCell生成SCell的DCI信元，通过站间接口向SCell发送DCI信元。
步骤4(参见图15中的(c)中的④)，SCell根据DCI信元生成DCI，在SCell所在的载波上通过空口将DCI发送给终端设备。
如图15中的(d)所示，为分布调度和集中DCI生成。
步骤1(参见图15中的(d)中的①)，SCell生成SCell自己的调度结果。SCell具有调度能力，可以为上述第一接入节点，PCell可以为上述第二接入节点。
步骤2(参见图15中的(d)中的②)，SCell没有生成DCI的能力的情况下，SCell向PCell发送请求信息，用于请求PCell生成DCI。该请求信息中可以包括(用于生成DCI的)调度结果。
步骤3(参见图15中的(d)中的③)，PCell生成SCell的DCI，通过站间接口向SCell发送DCI。
步骤4(参见图15中的(d)中的④)，SCell在SCell所在的载波上通过空口将DCI 发送给终端设备。
对于终端设备来说，终端设备会监听SCell所在的载波上的PDCCH信息。若检测到属于自己的DCI，终端设备可以解析该DCI，根据该DCI指示的PDSCH，接收用户数据。该DCI可以由PCell生成或者是SCell生成。
如果配置上行资源信息，在动态调度(UL DG)时，则DCI中可以包含本次UL Grant的时频域位置和MCS等信息，终端设备可以根据UL DG的配置信息，进行一次上行数据的发送。在半静态调度(UL SPS/CG)时，配置信息可以包含每次UL Grant的时频域位置，周期和MCS等信息，终端设备可以根据UL SPS/CG的配置信息，多次发送上行数据。SCell或PCell在UL Grant指示的上行资源上监听/接收/解码上行数据。上行数据可以承载在PUSCH。
可以理解，图12中的(a)的自调度场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈，重复之处不做赘述。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以由该1个MAC实体生成调度结果和生成DCI，然后通过PHY1实体或PHY2实体将DCI发送给终端设备。
一种可能的场景为跨载波调度场景(例如图1所示)，跨载波调度场景下PCell和SCell的配置信息(如DCI)都集中在一个节点(如PCell)发送，能够节省发送配置信息带来的开销。和自调度场景类似的，跨载波调度场景中可以包括集中调度和分布调度，跨载波调度场景中包括集中DCI生成和分布DCI生成。以图12(a)所示的协议栈为例进行说明。
如图16中的(a)所示，为集中调度和集中DCI生成。
步骤1(参见图16中的(a)中的①)，PCell(或PCell的MAC1实体)生成SCell的调度结果。PCell具有调度能力，可以为上述第一接入节点，SCell可以为上述第二接入节点。
步骤2(参见图16中的(a)中的②)，PCell(或PCell的MAC1实体)根据调度结果，生成SCell的DCI。
步骤3(参见图16中的(a)中的③)，PCell在PCell所在的载波上通过空口将DCI发送给终端设备。
SCell的DCI都统一在PCell上调度，因此SCell所在的载波上不传递DCI。以及由于生成调度结果的过程，生成DCI的过程，发送DCI的过程都集中在PCell上完成，SCell不参与，因此网络设备1和网络设备2之间可以不交互信息。
如图16中的(b)所示，集中调度和分布DCI生成。
步骤1(参见图16中的(b)中的①)，PCell生成SCell的调度结果。PCell具有调度能力，可以为上述第一接入节点，SCell可以为上述第二接入节点。
步骤2(参见图16中的(b)中的②)，PCell可以通过站间接口向SCell发送调度结果或DCI信元。
这里假设PCell有调度能力，没有生成DCI的能力。PCell可以从PCell之外的其它网元中获取DCI，例如SCell有生成DCI的能力，PCell可以从SCell中获取DCI。
步骤3(参见图16中的(b)中的③)，SCell根据调度结果或DCI信元，生成DCI。SCell可以通过站间接口向PCell发送DCI。
步骤4(参见图16中的(b)中的④)，PCell在PCell所在的载波上通过空口将DCI 发送给终端设备。PCell接收到DCI后，可以不解析该DCI，而可以通过PCell所在的载波的空口向终端设备透传该DCI。
如图16中的(c)所示，为分布调度和集中DCI生成。
步骤1(参见图16中的(c)中的①)，SCell生成SCell自己的调度结果。SCell具有调度能力，可以为上述第一接入节点，PCell可以为上述第二接入节点。
步骤2(参见图16中的(c)中的②)，SCell可以通过站间接口向PCell发送调度结果或DCI信元。
这里假设SCell有调度能力，没有生成DCI的能力。SCell可以从SCell之外的其它网元中获取DCI，例如PCell有生成DCI的能力，SCell可以从PCell中获取DCI。
步骤3(参见图16中的(c)中的③)，PCell根据调度结果或DCI信元，生成DCI。
步骤4(参见图16中的(c)中的④)，PCell在PCell所在的载波上通过空口将DCI发送给终端设备。
如图16中的(d)所示，为分布调度和分布DCI生成。
步骤1(参见图16中的(d)中的①)，SCell生成SCell自己的调度结果。SCell具有调度能力，可以为上述第一接入节点，PCell可以为上述第二接入节点。
步骤2(参见图16中的(d)中的②)，SCell根据调度结果，生成DCI。SCell可以通过站间接口向PCell发送DCI。
步骤3(参见图16中的(d)中的③)，SCell可选的可以将自身生成的DCI和SCell的DCI合并(也可以包括其它Cell生成的DCI)，统一在PCell所在的载波上通过空口将DCI发送给终端设备。
对于终端设备来说，终端设备会在PCell所在的载波的空口上接收到SCell生成的DCI，但是终端设备可以不关心DCI由PCell生成还是SCell生成。终端设备可以根据DCI指示的PDSCH，接收用户数据。
可以理解，图12中的(a)的跨载波调度场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈，重复之处不做赘述。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以由该1个MAC实体生成调度结果和生成DCI，然后通过PHY1实体或PHY2实体将DCI发送给终端设备。
一种可能的场景为数据交互场景，用户的数据信息可以在PCell和/或SCell上发送。数据交互场景中可以分为集中调度和分布调度，数据交互场景中可以分为集中数据封装和分布数据封装。
这里假设PCell的调度器在PCell上，若SCell的调度器在PCell上(SCell不具有调度能力，PCell为调度节点)，则为集中调度，若SCell的调度器在SCell上(SCell具有调度能力，SCell为调度节点)，则为分布调度。但是由于PCell的MAC实体连接有RLC/PDCP/SDAP实体，因此PCell可以获取到用户数据，PCell可以看作数据源节点。
若调度节点与封装数据的节点相同，则为集中数据封装，若调度节点与封装数据的节点不同，则为分布数据封装。以图12(a)所示的协议栈为例进行说明。
如图17中的(a)所示，为集中调度和分布数据封装。
步骤1(参见图17中的(a)中的①)，PCell(或PCell的MAC1实体)为SCell进行数据调度，生成SCell的数据调度结果。PCell具有数据调度能力，可以为数据源节点，例 如可以为上述第一接入节点或上述第二接入节点。
步骤2(参见图17中的(a)中的②)，PCell(或PCell的MAC1实体)可以通过站间接口向SCell(或SCell的MAC12实体)发送数据信息。
PCell的MAC1实体获取到RLC实体发送的RLC PDU(RLC PDU包括用户数据)，MAC1实体可以不做处理，直接将RLC PDU透传给SCell。
PCell的MAC1实体也可以对RLC PDU进行处理，将处理后得到的数据信息发送给SCell。例如MAC1实体可以对RLC PDU(也称MAC SDU，或MAC CE)增加MAC subheader，得到MAC SubPDU，将MAC SubPDU发送给SCell。又如MAC1实体可以将一个或多个MAC SubPDU级联生成MAC PDU(也称MAC TB)，将MAC PDU发送给SCell。
可选的步骤3(参见图17中的(a)中的③)，SCell根据数据信息，得到MAC PDU。
步骤4(参见图17中的(a)中的④)，SCell在SCell所在的载波上将PDSCH(该PDSCH承载有用户数据)发送给终端设备。
如图17中的(b)所示，为集中调度和集中数据封装。
步骤1(参见图17中的(b)中的①)，PCell生成SCell的数据调度结果。PCell具有数据调度能力，可以为数据源节点，例如可以为上述第一接入节点或上述第二接入节点。
步骤2(参见图17中的(b)中的②)，PCell生成MAC PDU，并经过PHY层处理得到RV版本数据。
步骤3(参见图17中的(b)中的③)，PCell可以通过站间接口向SCell发送RV版本数据。
步骤4(参见图17中的(b)中的④)，SCell在SCell所在的载波上将PDSCH发送给终端设备。
SCell在步骤3接收到MAC PDU后，可以通过PHY2实体进行编码发送即可，可以不进一步处理。
如图17中的(c)所示，为分布调度和分布数据封装。
步骤1(参见图17中的(c)中的①)，SCell生成SCell自己的数据调度结果。SCell具有数据调度能力，可以为数据源节点，例如可以为上述第一接入节点或上述第二接入节点。
步骤2(参见图17中的(c)中的②)，SCell可以通过站间接口向PCell发送请求信息，用于请求用户数据。
SCell的MAC2实体没有连接RLC实体，无法直接获取到RLC PDU。
该请求信息可以用于请求per TTI调度的用户数据，或者可以用于请求多次TTI调度的用户数据。该请求信息还可包含SCell生成的调度结果信息。
步骤3(参见图17中的(c)中的③)，可选地基于步骤2的调度结果信息，PCell可以通过站间接口向SCell发送数据信息。
相似之处可以参见图17中的(a)所示的步骤2。
步骤4(参见图17中的(c)中的④)，SCell可选的根据数据信息，可选地进一步组包，得到MAC PDU。SCell在SCell所在的载波上将PDSCH发送给终端设备。
如图17中的(d)所示，为分布调度和集中数据调度。
步骤1(参见图17中的(d)中的①)，SCell生成SCell自己的数据调度结果。SCell具有数据调度能力，可以为数据源节点，例如可以为上述第一接入节点或上述第二接入节 点。
步骤2(参见图17中的(d)中的②)，SCell可以通过站间接口向PCell发送请求信息，用于请求用户数据。
可选地、该请求信息还可包含SCell生成的调度结果信息。
步骤3(参见图17中的(d)中的③)，PCell生成MAC PDU、并经过PHY层处理得到RV版本数据，可以通过站间接口向SCell发送RV版本数据。
步骤4(参见图17中的(d)中的④)，SCell在SCell所在的载波上将PDSCH发送给终端设备。
MAC PDU的一种可能的帧结构如图18所示，MAC PDU包含多个MAC SubPDU。该MAC PDU可以为下行MAC PDU。其中MAC subPDU满足以下至少一项：
至少一个MAC SubPDU包含MAC CE1，该包含MAC CE1的MAC SubPDU中包含预留(reserved，R)/逻辑信道标识(logical channel identifier，LCID)subheader和固定尺寸(Fixed-sized)MAC CE；
至少一个MAC SubPDU包含MAC CE2，该包含MAC CE2的MAC SubPDU中包含R/格式(format，F)/LCID/长度(length，L)subheader和可变尺寸(Variable-sized)MAC CE；
至少一个MAC SubPDU包含MAC SDU，该包含MAC SDU的MAC SubPDU中包含R/F/LCID/L subheader和MAC SDU；和
至少一个MAC SubPDU包含填充(padding)字段。
在一些情况下，例如PCell没有获取到SCell的调度，或者SCell发送PDSCH支持令牌桶，PCell可以将与用户相关的LCH信息发送给SCell。PCell确定LCH信息的过程可以参见Uu上令牌桶机制，此处不做赘述。
可以理解，图12中的(a)的数据交互场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈。其中图13中的(a)和图13中的(b)中，SCell的MAC2实体与RLC实体连接，也可以获取到用户数据，实现数据源节点的功能。图14中的(a)和图14中的(b)中，PCell的MAC1实体与PCell的RLC1实体连接，可以获取到PCell自己的用户数据，实现数据源节点的功能，以及SCell的MAC2实体与SCell的RLC2实体连接，可以获取SCell自己的用户数据，实现数据源节点的功能。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以由该1个MAC实体生成数据调度结果和生成MAC PDU，然后通过PHY1实体或PHY2实体将PDSCH发送给终端设备。其余相似之处不做赘述。
在下行载波集合中，终端设备可以在CA的每个载波对应的PDSCH中接收到用户数据，终端设备对接收到的用户数据尝试解码，若解码成功，终端设备可以反馈本次接收成功(如ACK)，若解码未成功，终端设备可以反馈本次接收未成功(如NACK)。
一种可能的场景为分布反馈场景，即独立UCI场景，UCI可以承载反馈结果(如ACK/NACK)。分布反馈场景中，反馈结果的接收节点与PDSCH的发送节点相同。如图19中的(a)所示，PCell所在载波的PDSCH的反馈结果在PCell所在载波的PUCCH中反馈，SCell所在载波的PDSCH的反馈结果在SCell所在载波的PUCCH中反馈。PUCCH中承载反馈结果。以图12(a)所示的协议栈为例进行说明。
如图19中的(b)所示，为集中调度。SCell所在载波的PDSCH的数据调度由PCell 实现，SCell在SCell所在的载波上下发PDSCH。SCell的PDCCH可以由PCell下发，或者可以由SCell下发。
步骤1(参见19中的(b)中的①)，SCell接收SCell的反馈结果。SCell可以接收到反馈结果，SCell可以为上述第二接入节点，PCell为上述第一接入节点。
终端设备在SCell所在的载波上接收到PDSCH，在SCell的PUCCH上发送反馈结果。
步骤2(参见图19中的(b)中的②)，SCell可以通过站间接口向PCell发送反馈结果。
PCell可以根据反馈结果，确定是哪个终端设备的哪个HARQ process的反馈结果。SCell向PCell发送的反馈结果可以包括如下方式：例如包括以下一个或多个信息：RAT标识(RAT id)，频点标识(Freq id)，载波标识(CC id)，小区标识(Cell id)，用户标识(UE id)，ACK/NACK时频域位置，HARQ进程标识(HARQ process id)，ACK/NACK/不连续传输(discrete transmission，DTX)结果。可选的，ACK/NACK时频域位置和HARQ process id可以替换使用。SCell采用多个进程的方式给终端设备发送数据不用等待某次PDSCH的反馈结果，而是并行的等待多个进程的反馈结果，可以提升通信速率。
步骤3(参见图19中的(b)中的③)，PCell根据反馈结果，判断是否进行重传。
例如反馈结果为ACK时，可以不进行重传，反馈结果为NACK时，可以进行重传。又如，反馈结果为NACK时，可以不进行重传，可以认为反馈结果为NACK对应的用户数据可以丢弃，或者可以依赖上层RLC实体/PDCP实体的重传保证数据包的正确性。
如图19中的(c)所示，为分布调度，SCell所在载波的PDSCH的数据调度由SCell实现。
步骤1(参见图19中的(c)中的①)，SCell接收反馈结果。SCell可以接收到反馈结果，SCell可以为上述第二接入节点。
步骤2(参见图19中的(c)中的②)，SCell根据反馈结果，判断是否进行重传。
可以理解，图12中的(a)的分布反馈场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈，重复之处不做赘述。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以通过PHY1实体或PHY2实体接收反馈结果，由该1个MAC实体判断是否进行重传。
一种可能的场景为集中反馈场景，即联合UCI场景。集中反馈场景中，反馈结果的接收节点和PDSCH的发送节点可能不同。如图20中的(a)所示，PCell所在载波的PDSCH的反馈结果在SCell所在载波的PUCCH中反馈，SCell所在载波的PDSCH的反馈结果在SCell所在载波的PUCCH中反馈。或者PCell所在载波的PDSCH的反馈结果在PCell所在载波的PUCCH中反馈，SCell所在载波的PDSCH的反馈结果在PCell所在载波的PUCCH中反馈。以图12(a)所示的协议栈为例进行说明。
如图20中的(b)所示，为集中调度。
步骤1(参见图20中的(b)中的①)，SCell接收PCell的反馈结果和/或SCell的反馈结果。SCell可以接收到反馈结果，SCell可以为上述第二接入节点，PCell为上述第一接入节点。
步骤2(参见图20中的(b)中的②)，SCell可以通过站间接口向PCell发送反馈结果。
步骤3(参见图20中的(b)中的③)，PCell可以根据反馈结果，判断是否进行重传。
在步骤3中，PCell可以判断PCell的PDSCH是否进行重传，和/或可以判断SCell的 PDSCH是否进行重传。
如图20中的(c)所示，为分布调度。
步骤1(参见图20中的(c)中的①)，PCell接收PCell的反馈结果和/或SCell的反馈结果。PCell可以接收到反馈结果，SCell可以为上述第二接入节点，SCell为上述第一接入节点。
步骤2(参见图20中的(c)中的②)，PCell可以通过站间接口向SCell发送反馈结果。
步骤3(参见图20中的(c)中的③)，SCell可以根据反馈结果，判断是否进行重传。
在步骤3中，SCell可以判断PCell的PDSCH是否进行重传，和/或可以判断SCell的PDSCH是否进行重传。
可以理解，图12中的(a)的集中反馈场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈，重复之处不做赘述。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以通过PHY1实体或PHY2实体接收反馈结果，由该1个MAC实体判断是否进行重传。
一种可能的场景为数据重传场景。如果PCell或SCell确定反馈结果为NACK，进行重传。数据重传场景与数据交互场景类似，这里简单说明。数据交互场景适用于初传场景，也可以适用于重传场景。以图12(a)所示的协议栈为例进行说明。
如图21中的(a)所示，为集中调度和分布数据封装。
步骤1(参见图21中的(a)中的①)，PCell生成SCell的数据调度结果。PCell具有数据调度能力，可以为数据源节点，例如可以为上述第一接入节点或上述第二接入节点。
步骤2(参见图21中的(a)中的②)，PCell可以通过站间接口向SCell发送数据信息。
可选的步骤3(参见图21中的(a)中的③)，SCell根据数据信息，得到MAC PDU。
步骤4(参见图21中的(a)中的④)，SCell在SCell所在的载波上将PDSCH发送给终端设备。
如图21中的(b)所示，为集中调度和集中数据封装。
步骤1(参见图21中的(b)中的①)，PCell生成SCell的数据调度结果。PCell具有数据调度能力，可以为数据源节点，例如可以为上述第一接入节点或上述第二接入节点。
步骤2(参见图21中的(b)中的②)，PCell生成新的RV版本数据。
若PCell在初传时发送RV版本数据，在重传时，PCell可以生成新的RV版本数据。
步骤3(参见图21中的(b)中的③)，PCell可以通过站间接口向SCell发送新的RV版本数据。
步骤4(参见图21中的(b)中的④)，SCell在SCell所在的载波上将新的RV版本数据发送给终端设备。
如图21中的(c)所示，为分布调度和分布数据封装。
步骤1(参见图21中的(c)中的①)，SCell生成SCell自己的数据调度结果。SCell具有数据调度能力，可以为数据源节点，例如可以为上述第一接入节点或上述第二接入节点。
步骤2(参见图21中的(c)中的②)，可选地(仅当新传时)，SCell可以通过站间接口向PCell发送请求信息，用于请求用户数据。
步骤3(参见图21中的(c)中的③)，PCell可以通过站间接口向SCell发送数据信息。
步骤4(参见图21中的(c)中的④)，SCell可选的根据数据信息，组包生成MAC PDU；或SCell直接从PCell获得MAC PDU。SCell在SCell所在的载波上将PDSCH发送给终端设备。
如图21中的(d)所示，为分布调度和集中数据调度。
步骤1(参见图21中的(d)中的①)，SCell生成SCell自己的数据调度结果。SCell具有数据调度能力，可以为数据源节点，例如可以为上述第一接入节点或上述第二接入节点。
步骤2(参见图21中的(d)中的②)，SCell可以通过站间接口向PCell发送请求信息，用于请求新的/不同的RV版本数据。
步骤3(参见图21中的(d)中的③)，PCell生成新的/不同的RV版本数据，可以通过站间接口向SCell发送新的/不同的RV版本数据。
步骤4(参见图21中的(d)中的④)，SCell在SCell所在的载波上将新的/不同的RV版本数据发送给终端设备。
可以理解，图12中的(a)的数据重传场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈。其中图13中的(a)和图13中的(b)中，SCell的MAC2实体与RLC实体连接，也可以获取到用户数据，实现数据源节点的功能。图14中的(a)和图14中的(b)中，PCell的MAC1实体与PCell的RLC1实体连接，可以获取到PCell自己的用户数据，实现数据源节点的功能，以及SCell的MAC2实体与SCell的RLC2实体连接，可以获取SCell自己的用户数据，实现数据源节点的功能。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以由该1个MAC实体生成数据调度结果和生成MAC PDU，然后通过PHY1实体或PHY2实体将PDSCH发送给终端设备。其余相似之处不做赘述。
一种可能的场景为UL请求场景。可选的，UL请求的接收节点可以与调度节点相同。或者UL请求的接收节点可以与调度节点不同。这里主要以UL请求的接收节点与调度节点不同的情况进行说明。以图12(a)所示的协议栈为例进行说明。
如图22中的(a)所示，UL请求的接收节点为SCell，调度节点为PCell。
步骤1(参见图22中的(a)中的①)，SCell接收UL请求。SCell可以接收到UL请求，SCell可以为上述第二接入节点，PCell为上述第一接入节点。
步骤2(参见图22中的(a)中的②)，SCell可以通过站间接口将与UL请求相关的信息发送给PCell。
与UL请求相关的信息可以包括UL(如SR/BSR/RACH/DL CSI/UAI)，或者可以包括SCell测量终端设备的SRS得到的UL CSI信息。DL CSI信息，UL CSI信息可以包括但不限于以下至少一个：预编码矩阵指示(precoding matrix indication，PMI)、秩指示(rank indication，RI)、层指示(layer indicator，LI)、信道质量指示(channel quality indicator，CQI)、CSI-RS资源标识(CSI-RS resource indicator，CRI)、参考信号接收功率(reference signal received power，RSRP)、协方差矩阵、信道矩阵。DL CSI信息，UL CSI信息可以是cell粒度的信息或波束(beam)粒度的信息。UAI是UE上报给网络侧的UE辅助信息、可以包含UE上行周期性业务的数据模型。
步骤3(参见图22中的(a)中的③)，PCell根据与UL请求调度相关的信息，生成调度结果，该调度结果用于配置上行资源信息。
如图22中的(b)所示，UL请求的接收节点为PCell，调度节点为SCell。
步骤1(参见图22中的(b)中的①)，PCell接收UL请求。PCell可以接收到UL请求，PCell可以为上述第二接入节点，SCell为上述第一接入节点。
步骤2(参见图22中的(b)中的②)，PCell可以通过站间接口将与UL请求相关的信息发送给SCell。
步骤3(参见图22中的(b)中的③)，SCell根据与UL请求调度相关的信息，生成调度结果，该调度结果用于配置上行资源信息。
配置上行资源信息的过程可以参见自调度场景和/或跨载波调度场景，这里不做赘述。
如图22中的(a)所示，为一种可能的BSR的格式，BSR包含一个LCG id字段，和一个Buffer Size字段，其中LCG id字段为逻辑信道组标识，Buffer Size字段为数据量大小范围的标识。如图22中的(b)所示，为另一种可能的BSR的格式，BSR包含多个LCG id字段(如7个LCG)，和多个Buffer Size字段(如m个Buffer Size字段)。
可以理解，图12中的(a)的集中反馈场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈，重复之处不做赘述。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以由该1个MAC实体生成调度结果和生成DCI，然后通过PHY1实体或PHY2实体接收UL请求，由该1个MAC实体生成调度结果。
上述数据交互场景和数据重传场景中主要描述了DL Data的交互。
一种可能的UL数据交互场景中，终端设备发送的UL Data可以发送给PCell和/或SCell。以图12(a)所示的协议栈为例进行说明。
如图23所示，SCell接收到UL Data。
步骤1(参见图23中的①)，SCell接收PUSCH，PUSCH承载有UL Data。SCell可以接收到UL Data，SCell可以为上述第二接入节点，PCell为上述第一接入节点。
步骤2(参见图23中的②)，SCell可以通过站间接口向PCell发送UL Data。
可选的，SCell可以向PCell发送PHY2实体编码处理后的UL Data，UL Data可以为RV版本数据的形式，或者可以为MAC PDU的形式。MAC1实体若接收到RV版本数据，PHY1实体对RV版本数据进行软合并，将软合并后的数据转发给MAC1实体处理。
或者，SCell可以向PCell发送MAC2实体处理后的UL Data，UL Data可以为MAC SubPDU的形式，或者可以为RLC PDU的形式。MAC1实体若接收到RLC PDU，可以不进行额外处理，直接转发给MAC1连接的RLC实体。MAC1若接收到MAC SubPDU，可以提取MAC subheader，识别为MAC SDU(如果为MAC SDU，可以直接转发为RLC实体)或若识别为MAC CE、则由MAC1进行相应处理。
可选的，MAC1实体可以根据MAC SDU对应的subheader中的LCID，识别出LCH id，然后确定LCH id对应的RLC实体。
MAC PDU的一种可能的帧结构如图24所示，MAC PDU包含多个MAC SubPDU。该MAC PDU可以为上行MAC PDU。其中MAC subPDU满足以下至少一项：
至少一个MAC SubPDU包含MAC CE2，该包含MAC CE2的MAC SubPDU中包含R/F/LCID/L subheader和Variable-sized MAC CE；
至少一个MAC SubPDU包含MAC SDU，该包含MAC SDU的MAC SubPDU中包含R/F/LCID/L subheader和MAC SDU；
至少一个MAC SubPDU包含MAC CE1，该包含MAC CE1的MAC SubPDU中包含R/LCID subheader和Fixed-sized MAC CE；和
至少一个MAC SubPDU包含填充padding字段。
可以理解，图12中的(a)的UL数据交互场景，可以适用于图12中的(b)，图13中的(a)，图13中的(b)及图14中的(a)，图14中的(b)所示的协议栈，重复之处不做赘述。而图11中的(a)和图11中的(b)所示的协议栈中，由于有1个MAC实体和2个PHY实体，可以通过PHY1实体或PHY2实体接收UL Data，由该1个MAC实体向RLC实体/PDCP实体进行转发。
本申请实施例还提供第一协议栈的配置过程，如图25所示，包括以下步骤：
S2501：可选的，终端设备上报能力信息。
该能力信息用于指示终端设备是否支持MR-CA能力。
或者该能力信息可以用于指示终端设备是否支持“跨RAT调度”、“跨RAT反馈”、“跨RAT SRS切换”等能力。其中跨RAT调度指一个制式的DCI调度另一个制式的数据(例如上述跨调度场景)，跨RAT反馈指两个制式的反馈集中在一个制式上反馈(例如上述集中反馈场景)，跨RAT SRS switching指终端设备只有一个发送通道，终端设备在两个制式上通过时分方式发送不同制式的SRS信号。
S2502：网络设备向终端设备发送第一配置信息，该第一配置信息用于第一通信方式。
网络设备可以为上述第一接入节点或上述第二接入节点。
可选的第一通信方式可以完全重用MR-DC协议栈配置。该第一配置信息包括第一指示信息，该第一指示信息可以用于指示使用MR-DC通信，或者使用MR-CA通信。第一指示信息还可以包括MR-DC协议栈。第一配置信息可以采用显式信息指示是否采用第一通信方式进行通信，例如采用1bit信息进行指示，当1bit为1时，指示采用第一通信方式进行通信，1bit为0时，指示采用非第一通信方式的通信方式(如MR-DC的通信方式)进行通信。
可选的，第一通信方式可以不完全重用MR-DC协议栈配置。该第一配置信息可以包括上述第一协议栈的信息。或者该第一配置信息新增两个MAC实体之间的关联关系，例如在第一接入节点的MAC配置信息中可以包括第二接入节点的MAC实体的索引或标识，和/或在第二接入节点的MAC配置信息中可以包括第一接入节点的MAC实体的索引或标识，和/或一组配置中包括第一接入节点的MAC实体的索引或标识、以及第二接入节点的MAC实体的索引或标识。或者该第一配置信息新增一个MAC实体与两个PHY实体之间的关联关系。例如MAC配置信息包括第一接入节点的PHY实体的索引或标识，和/或第二接入节点的PHY实体的索引或标识。又如第一接入节点的PHY配置信息包括MAC实体的索引或标识，第二接入节点的PHY配置信息包括MAC实体的索引或标识。又如一组配置中包括MAC实体的索引或标识，第一接入节点的PHY实体的索引或标识，和第二接入节点的PHY实体的索引或标识。
S2503：可选的，网络设备还可以指示终端设备接入其它节点，并通过第一通信方式与其它节点通信。
可选的，网络设备可以激活或去激活其它节点，针对激活的其它节点，终端设备与激活的其它节点通过第一通信方式进行通信。当节点激活时，终端设备可以在该节点的CC上发送SRS，上报CQI等信息，检测用于该节点和在该节点上传输的DCI等，进而实现在 不同制式上的载波聚合以及通信过程。
S2504：终端设备确定通过第一通信方式进行通信。
终端设备通过第一通信方式进行通信的过程可以参见上述通信过程，这里不做赘述。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，以上各个实施例中，由接入节点实现的方法和/或步骤，也可以由可用于接入节点的部件(例如芯片或者电路)实现，由终端设备实现的方法和/或步骤，也可以由可用于终端设备的部件实现。
以上结合图9至图25详细说明了本申请实施例的通信方法，基于与上述通信方法的同一技术构思，本申请实施例还提供了一种通信装置，可用于实现上述方法实施例中描述的方法。
通信装置的一种可能的表现形式如图26所示，所述通信装置2600中包含处理单元2601和收发单元2602，装置2600可用于实现上述方法实施例中描述的方法。
在一个实施例中，装置2600应用于第一接入节点。
具体的，处理单元2601，用于确定调度信息，所述调度信息用于指示第二接入节点接收数据或发送数据的资源信息；
收发单元2602，用于向所述第二接入节点发送所述调度信息。
在一个实现方式中，调度信息为动态调度信息，或者半静态调度信息。
在一个实现方式中，调度信息包括一个或多个下行控制信息DCI信元，所述一个或多个DCI信元用于生成DCI，或者所述调度信息包括DCI。
在一个实现方式中，收发单元2602，还用于接收来自第二接入节点的所述DCI；向终端设备发送所述DCI。
在一个实现方式中，调度信息包括上行调度信息。
在一个实现方式中，上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。
在一个实现方式中，收发单元2602，还用于接收上行信息，所述上行信息包括以下一个或多个：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息。
在一个实现方式中，收发单元2602，还用于向所述第二接入节点发送数据信息，所述数据信息为下行数据信息。
在一个实现方式中，所述数据信息为用户数据，或所述第一接入节点对用户数据处理后得到的无线链路控制层RLC协议数据单元PDU，或所述第一接入节点对用户数据处理后得到的媒体接入控制MAC子协议数据单元SubPDU，或者所述第一接入节点对用户数据处理后得到的MAC PDU，或者所述第一接入节点对用户数据处理后得到的冗余版本RV版本数据。
在一个实现方式中，收发单元2602，还用于向所述第二接入节点发送数据信息之前，接收第二请求信息，所述第二请求信息用于请求数据信息。
在一个实现方式中，收发单元2602，还用于向所述第二接入节点发送逻辑信道信息，所述逻辑信道信息与用户数据所属用户的逻辑信道相关。
在一个实现方式中，收发单元2602，还用于接收来自所述第二接入节点的数据信息， 所述数据信息为下行数据信息；向终端设备发送所述数据信息。
在一个实现方式中，调度信息包括用于重传的指示信息。
收发单元2602，还用于当所述数据信息为用户数据，或所述第二接入节点对用户数据处理后得到的RLC PDU，或所述第二接入节点对用户数据处理后得到的MAC SubPDU，或者所述第二接入节点对用户数据处理后得到的MAC PDU，向所述第二接入节点发送重传的调度信息。
收发单元2602，还用于当所述数据信息为所述第二接入节点对用户数据处理后得到的RV版本数据，接收来自所述第二接入节点的新的RV版本数据，向所述终端设备发送所述新的RV版本数据。
在一个实现方式中，收发单元2602，还用于接收来自所述第二接入节点的数据信息的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败。
在一个实现方式中，收发单元2602，还用于向所述第二接入节点发送第一请求信息，所述第一请求信息用于请求调度信息，所述第一请求信息包括调度结果；接收来自所述第二接入节点的所述调度信息。
在一个实现方式中，所述第一接入节点的MAC实体与所述第二接入节点的MAC实体连接；或者所述第一接入节点的MAC实体分别与所述第一接入节点的PHY实体和所述第二接入节点的PHY实体连接。
在另一个实施例中，装置2600应用于第二接入节点。
具体的，收发单元2602，用于接收调度信息，所述调度信息用于指示第二接入节点接收数据或发送数据的资源信息；
处理单元2601，用于确定接收数据或发送数据的资源信息。
在一个实现方式中，调度信息为动态调度信息，或者半静态调度信息。
在一个实现方式中，调度信息包括一个或多个下行控制信息DCI信元，所述一个或多个DCI信元用于生成DCI，或者所述调度信息包括DCI。
在一个实现方式中，处理单元2601，还用于生成所述DCI；
收发单元2602，还用于向所述第一接入节点发送所述DCI。
在一个实现方式中，所述调度信息包括上行调度信息。
在一个实现方式中，所述上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。
在一个实现方式中，收发单元2602，还用于接收上行信息，所述上行信息包括以下一个或多个：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息；向所述第一接入节点发送所述上行信息。
在一个实现方式中，收发单元2602，还用于接收来自第一接入节点的数据信息，所述数据信息为下行数据信息；向终端设备发送所述数据信息。
在一个实现方式中，数据信息为用户数据，或所述第一接入节点对用户数据处理后得到的无线链路控制层RLC协议数据单元PDU，或所述第一接入节点对用户数据处理后得到的媒体接入控制MAC子协议数据单元SubPDU，或者所述第一接入节点对用户数据处理后得到的MAC PDU，或者所述第一接入节点对用户数据处理后得到的冗余版本RV版本数据。
在一个实现方式中，收发单元2602，还用于接收来自第一接入节点的数据信息之前， 向所述第一接入节点发送第二请求信息，所述第二请求信息用于请求数据信息。
在一个实现方式中，收发单元2602，还用于接收逻辑信道信息，所述逻辑信道信息与用户数据所属用户的逻辑信道相关。
在一个实现方式中，收发单元2602，还用于向所述第一接入节点发送数据信息，所述数据信息为下行数据信息。
在一个实现方式中，调度信息包括用于重传的指示信息。
收发单元2602，还用于当所述数据信息为用户数据，或所述第二接入节点对用户数据处理后得到的RLC PDU，或所述第二接入节点对用户数据处理后得到的MAC SubPDU，或者所述第二接入节点对用户数据处理后得到的MAC PDU，接收所述第一接入节点发送重传的调度信息。
收发单元2602，还用于当所述数据信息为所述第二接入节点对用户数据处理后得到的RV版本数据，向所述第一接入节点发送新的RV版本数据。
在一个实现方式中，收发单元2602，还用于接收来自终端设备的数据信息的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败；向所述第一接入节点发送所述反馈信息。
在一个实现方式中，收发单元2602，还用于接收第一请求信息，所述第一请求信息用于请求调度信息，所述第一请求信息包括调度结果；向所述第一接入节点发送所述调度信息。
在一个实现方式中，所述第一接入节点的MAC实体与所述第二接入节点的MAC实体连接；或者所述第一接入节点的MAC实体分别与所述第一接入节点的PHY实体和所述第二接入节点的PHY实体连接。
在又一个实施例中，装置2600应用于终端设备。
具体的，收发单元2602，用于接收第二接入节点接收数据或发送数据的资源信息；
处理单元2601，用于确定第二接入节点接收数据或发送数据的资源信息。
在一个实现方式中，收发单元2602，具体用于来自第二接入节点或第一接入节点的DCI，DCI包括第二接入节点接收数据或发送数据的资源信息。
在一个实现方式中，收发单元2602，还用于向第一接入节点或第二接入节点发送上行信息，所述上行信息包括以下一个或多个：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息。
在一个实现方式中，收发单元2602，还用于接收来自第一接入节点或第二接入节点的数据信息，所述数据信息为下行数据信息。
在一个实现方式中，收发单元2602，还用于向第一接入节点或第二接入节点发送数据信息的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败。
在一个实现方式中，所述第一接入节点的MAC实体与所述第二接入节点的MAC实体连接；或者所述第一接入节点的MAC实体分别与所述第一接入节点的PHY实体和所述第二接入节点的PHY实体连接。
需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可 以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
通信装置的另一种可能的表现形式如图27所示，装置2700可用于实现上述方法实施例中描述的方法。
所述装置2700包括一个或多个处理器2701。所述处理器2701可以是通用处理器或者专用处理器等。例如可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、终端、或芯片等)进行控制，执行软件程序，处理软件程序的数据。所述通信装置可以包括收发单元，用以实现信号的输入(接收)和输出(发送)。例如，所述收发单元可以为收发器，射频芯片等。
所述装置2700包括一个或多个所述处理器2701，所述一个或多个处理器2701可实现上述所示的实施例中描述的方法。
可选的，处理器2701除了实现上述所示的实施例的方法，还可以实现其他功能。
可选的，一种设计中，处理器2701可以执行指令，使得所述装置2700执行上述方法实施例中描述的方法。所述指令可以全部或部分存储在所述处理器内，如指令2703，也可以全部或部分存储在与所述处理器耦合的存储器2702中，如指令2704，也可以通过指令2703和2704共同使得装置2700执行上述方法实施例中描述的方法。
在又一种可能的设计中，通信装置2700也可以包括逻辑电路，所述逻辑电路可以实现前述方法实施例中描述的方法。
在又一种可能的设计中所述装置2700中可以包括一个或多个存储器2702，其上存有指令2704，所述指令可在所述处理器上被运行，使得所述装置2700执行上述方法实施例中描述的方法。可选的，所述存储器中还可以存储有数据。可选的处理器中也可以存储指令和/或数据。例如，所述一个或多个存储器2702可以存储上述实施例中所描述的对应关系，或者上述实施例中所涉及的相关的参数或表格等。所述处理器和存储器可以单独设置，也可以集成在一起。
在又一种可能的设计中，所述装置2700还可以包括收发器2705以及天线2706。所述处理器2701可以称为处理单元，对装置(终端或者基站)进行控制。所述收发器2705可以称为收发机、收发电路、输入输出接口电路或者收发单元等，用于通过天线2706实现装置的收发功能。可选的，天线2706可以集成在收发器2705中。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、 步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述方法实施例描述的方法。
本申请实施例还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述方法实施例描述的方法。
本申请实施例还提供一种计算机程序，该计算机程序在计算机上执行时实现上述方法实施例描述的方法。
本申请实施例还提供一种通信系统，所述通信系统包括第一接入节点和第二接入节点。第一接入节点可以实现上述方法实施例描述的方法，第二接入节点可以实现上述方法实施例描述的方法。
可选的，该通信系统还可以包括终端设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如，固态硬盘(Solid State Drive，SSD))等。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器，用于执行上 述方法实施例描述的方法；该接口用于与该通信装置之外的模块通信，接口可以为通信接口、输入输出接口等。或者，该接口可以为代码/数据读写接口，该接口用于接收执行指令(执行指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该处理器，以使该处理器运行执行指令以执行上述方法实施例描述的方法。
应理解，上述处理装置可以是一个芯片，所述处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，改存储器可以集成在处理器中，可以位于所述处理器之外，独立存在。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本申请所使用的，盘(Disk)和碟(disc)包括压缩 光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。

Claims (71)

  1. 一种通信方法，其特征在于，包括：
    第一接入节点确定调度信息，所述调度信息用于指示第二接入节点接收数据或发送数据的资源信息；
    所述第一接入节点向所述第二接入节点发送所述调度信息。
  2. 如权利要求1所述的方法，其特征在于，所述调度信息为动态调度信息，或者半静态调度信息。
  3. 如权利要求1或2所述的方法，其特征在于，所述调度信息包括一个或多个下行控制信息DCI信元，所述一个或多个DCI信元用于生成DCI，或者所述调度信息包括DCI。
  4. 如权利要求3所述的方法，其特征在于，还包括：
    所述第一接入节点接收来自所述第二接入节点的所述DCI；
    所述第一接入节点向终端设备发送所述DCI。
  5. 如权利要求1或2所述的方法，其特征在于，所述调度信息包括上行调度信息。
  6. 如权利要求5所述的方法，其特征在于，所述上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。
  7. 如权利要求5或6所述的方法，其特征在于，还包括：
    所述第一接入节点接收上行信息，所述上行信息包括以下一个或多个：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息。
  8. 如权利要求1-7任一项所述的方法，其特征在于，还包括：
    所述第一接入节点向所述第二接入节点发送数据信息，所述数据信息为下行数据信息。
  9. 如权利要求8所述的方法，其特征在于，所述数据信息为用户数据，或所述第一接入节点对用户数据处理后得到的无线链路控制层RLC协议数据单元PDU，或所述第一接入节点对用户数据处理后得到的媒体接入控制MAC子协议数据单元SubPDU，或者所述第一接入节点对用户数据处理后得到的MAC PDU，或者所述第一接入节点对用户数据处理后得到的冗余版本RV版本数据。
  10. 如权利要求8或9所述的方法，其特征在于，所述第一接入节点向所述第二接入节点发送数据信息之前，所述方法还包括：
    所述第一接入节点接收第二请求信息，所述第二请求信息用于请求数据信息。
  11. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    所述第一接入节点向所述第二接入节点发送逻辑信道信息，所述逻辑信道信息与用户数据所属用户的逻辑信道相关。
  12. 如权利要求1-7任一项所述的方法，其特征在于，还包括：
    所述第一接入节点接收来自所述第二接入节点的数据信息，所述数据信息为下行数据信息；
    所述第一接入节点向终端设备发送所述数据信息。
  13. 如权利要求12所述的方法，其特征在于，所述调度信息包括用于重传的指示信息；
    所述方法还包括：
    当所述数据信息为用户数据，或所述第二接入节点对用户数据处理后得到的RLC PDU， 或所述第二接入节点对用户数据处理后得到的MAC SubPDU，或者所述第二接入节点对用户数据处理后得到的MAC PDU，所述第一接入节点向所述第二接入节点发送重传的调度信息；
    当所述数据信息为所述第二接入节点对用户数据处理后得到的RV版本数据，所述第一接入节点接收来自所述第二接入节点的新的RV版本数据，向所述终端设备发送所述新的RV版本数据。
  14. 如权利要求8-13任一项所述的方法，其特征在于，还包括：
    所述第一接入节点接收来自所述第二接入节点的数据信息的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败。
  15. 如权利要求1-14任一项所述的方法，其特征在于，所述第一接入节点确定调度信息，包括：
    所述第一接入节点向所述第二接入节点发送第一请求信息，所述第一请求信息用于请求调度信息，所述第一请求信息包括调度结果；
    所述第一接入节点接收来自所述第二接入节点的所述调度信息。
  16. 如权利要求1-15任一项所述的方法，其特征在于，所述第一接入节点的MAC实体与所述第二接入节点的MAC实体连接；或者
    所述第一接入节点的MAC实体分别与所述第一接入节点的PHY实体和所述第二接入节点的PHY实体连接。
  17. 一种通信方法，其特征在于，包括：
    第二接入节点接收调度信息，所述调度信息用于指示第二接入节点接收数据或发送数据的资源信息；
    所述第二接入节点确定接收数据或发送数据的资源信息。
  18. 如权利要求17所述的方法，其特征在于，所述调度信息为动态调度信息，或者半静态调度信息。
  19. 如权利要求17或18所述的方法，其特征在于，所述调度信息包括一个或多个下行控制信息DCI信元，所述一个或多个DCI信元用于生成DCI，或者所述调度信息包括DCI。
  20. 如权利要求19所述的方法，其特征在于，还包括：
    所述第二接入节点生成所述DCI；
    所述第二接入节点向所述第一接入节点发送所述DCI。
  21. 如权利要求17或18所述的方法，其特征在于，所述调度信息包括上行调度信息。
  22. 如权利要求21所述的方法，其特征在于，所述上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。
  23. 如权利要求21或22所述的方法，其特征在于，还包括：
    所述第二接入节点接收上行信息，所述上行信息包括以下一个或多个：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息；
    所述第二接入节点向所述第一接入节点发送所述上行信息。
  24. 如权利要求17-23任一项所述的方法，其特征在于，还包括：
    所述第二接入节点接收来自第一接入节点的数据信息，所述数据信息为下行数据信息；
    所述第二接入节点向终端设备发送所述数据信息。
  25. 如权利要求24所述的方法，其特征在于，所述数据信息为用户数据，或所述第一接入节点对用户数据处理后得到的无线链路控制层RLC协议数据单元PDU，或所述第一接入节点对用户数据处理后得到的媒体接入控制MAC子协议数据单元SubPDU，或者所述第一接入节点对用户数据处理后得到的MAC PDU，或者所述第一接入节点对用户数据处理后得到的冗余版本RV版本数据。
  26. 如权利要求24或25所述的方法，其特征在于，所述第二接入节点接收来自第一接入节点的数据信息之前，还包括：
    所述第二接入节点向所述第一接入节点发送第二请求信息，所述第二请求信息用于请求数据信息。
  27. 如权利要求25所述的方法，其特征在于，所述方法还包括：
    所述第二接入节点接收逻辑信道信息，所述逻辑信道信息与用户数据所属用户的逻辑信道相关；
    所述第二接入节点根据所述逻辑信道信息，确定向所述终端设备发送的数据量。
  28. 如权利要求17-23任一项所述的方法，其特征在于，还包括：
    所述第二接入节点向所述第一接入节点发送数据信息，所述数据信息为下行数据信息。
  29. 如权利要求28所述的方法，其特征在于，所述调度信息包括用于重传的指示信息；
    所述方法还包括：
    当所述数据信息为用户数据，或所述第二接入节点对用户数据处理后得到的RLC PDU，或所述第二接入节点对用户数据处理后得到的MAC SubPDU，或者所述第二接入节点对用户数据处理后得到的MAC PDU，所述第二接入节点接收所述第一接入节点发送重传的调度信息；
    当所述数据信息为所述第二接入节点对用户数据处理后得到的RV版本数据，所述第二接入节点向所述第一接入节点发送新的RV版本数据。
  30. 如权利要求24-29任一项所述的方法，其特征在于，还包括：
    所述第二接入节点接收来自终端设备的数据信息的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败；
    所述第二接入节点向所述第一接入节点发送所述反馈信息。
  31. 如权利要求17-30任一项所述的方法，其特征在于，还包括：
    所述第二接入节点接收第一请求信息，所述第一请求信息用于请求调度信息，所述第一请求信息包括调度结果；
    所述第二接入节点向所述第一接入节点发送所述调度信息。
  32. 如权利要求17-30任一项所述的方法，其特征在于，所述第一接入节点的MAC实体与所述第二接入节点的MAC实体连接；或者
    所述第一接入节点的MAC实体分别与所述第一接入节点的PHY实体和所述第二接入节点的PHY实体连接。
  33. 一种通信装置，其特征在于，包括：
    处理单元，用于确定调度信息，所述调度信息用于指示第二接入节点接收数据或发送数据的资源信息；
    收发单元，用于向所述第二接入节点发送所述调度信息。
  34. 如权利要求33所述的装置，其特征在于，所述调度信息为动态调度信息，或者半静态调度信息。
  35. 如权利要求33或34所述的装置，其特征在于，所述调度信息包括一个或多个下行控制信息DCI信元，所述一个或多个DCI信元用于生成DCI，或者所述调度信息包括DCI。
  36. 如权利要求35所述的装置，其特征在于，所述收发单元，还用于接收来自所述第二接入节点的所述DCI，向终端设备发送所述DCI。
  37. 如权利要求33或34所述的装置，其特征在于，所述调度信息包括上行调度信息。
  38. 如权利要求37所述的装置，其特征在于，所述上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。
  39. 如权利要求37或38所述的装置，其特征在于，所述收发单元，还用于所述上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。
  40. 如权利要求33-39任一项所述的装置，其特征在于，所述收发单元，还用于向所述第二接入节点发送数据信息，所述数据信息为下行数据信息。
  41. 如权利要求40所述的装置，其特征在于，所述数据信息为用户数据，或所述通信装置对用户数据处理后得到的无线链路控制层RLC协议数据单元PDU，或所述通信装置对用户数据处理后得到的媒体接入控制MAC子协议数据单元SubPDU，或者所述通信装置对用户数据处理后得到的MAC PDU，或者所述通信装置对用户数据处理后得到的冗余版本RV版本数据。
  42. 如权利要求40或41所述的装置，其特征在于，所述收发单元，还用于向所述第二接入节点发送数据信息之前，接收第二请求信息，所述第二请求信息用于请求数据信息。
  43. 如权利要求41所述的装置，其特征在于，所述收发单元，还用于向所述第二接入节点发送逻辑信道信息，所述逻辑信道信息与用户数据所属用户的逻辑信道相关。
  44. 如权利要求33-39任一项所述的装置，其特征在于，所述收发单元，还用于接收来自所述第二接入节点的数据信息，所述数据信息为下行数据信息，向终端设备发送所述数据信息。
  45. 如权利要求44所述的装置，其特征在于，所述调度信息包括用于重传的指示信息；
    所述收发单元，还用于当所述数据信息为用户数据，或所述第二接入节点对用户数据处理后得到的RLC PDU，或所述第二接入节点对用户数据处理后得到的MAC SubPDU，或者所述第二接入节点对用户数据处理后得到的MAC PDU，向所述第二接入节点发送重传的调度信息；当所述数据信息为所述第二接入节点对用户数据处理后得到的RV版本数据，接收来自所述第二接入节点的新的RV版本数据，向所述终端设备发送所述新的RV版本数据。
  46. 如权利要求40-45任一项所述的装置，其特征在于，所述收发单元，还用于接收来自所述第二接入节点的数据信息的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败。
  47. 如权利要求33-46任一项所述的装置，其特征在于，所述收发单元，还用于向所述第二接入节点发送第一请求信息，所述第一请求信息用于请求调度信息，所述第一请求信息包括调度结果，接收来自所述第二接入节点的所述调度信息。
  48. 如权利要求33-47任一项所述的装置，其特征在于，所述通信装置的MAC实体与所述第二接入节点的MAC实体连接；或者所述通信装置的MAC实体分别与所述通信装置的PHY实体和所述第二接入节点的PHY实体连接。
  49. 一种通信装置，其特征在于，包括：
    收发单元，用于接收调度信息，所述调度信息用于指示所述通信装置接收数据或发送数据的资源信息；
    处理单元，用于确定接收数据或发送数据的资源信息。
  50. 如权利要求49所述的装置，其特征在于，所述调度信息为动态调度信息，或者半静态调度信息。
  51. 如权利要求49或50所述的装置，其特征在于，所述调度信息包括一个或多个下行控制信息DCI信元，所述一个或多个DCI信元用于生成DCI，或者所述调度信息包括DCI。
  52. 如权利要求51所述的装置，其特征在于，所述处理单元，还用于生成所述DCI；
    所述收发单元，还用于向第一接入节点发送所述DCI。
  53. 如权利要求49或50所述的装置，其特征在于，所述调度信息包括上行调度信息。
  54. 如权利要求53所述的装置，其特征在于，所述上行调度信息包括以下一个或多个：随机接入信道的调度信息，调度请求的调度信息，缓冲状态报告的调度信息，或信道状态的调度信息。
  55. 如权利要求53或54所述的装置，其特征在于，所述收发单元，还用于接收上行信息，所述上行信息包括以下一个或多个：随机接入信道信息，调度请求，缓冲状态报告，或信道状态信息，向所述第一接入节点发送所述上行信息。
  56. 如权利要求49-55任一项所述的装置，其特征在于，所述收发单元，还用于接收来自第一接入节点的数据信息，所述数据信息为下行数据信息；向终端设备发送所述数据信息。
  57. 如权利要求56所述的装置，其特征在于，所述数据信息为用户数据，或所述第一接入节点对用户数据处理后得到的无线链路控制层RLC协议数据单元PDU，或所述第一接入节点对用户数据处理后得到的媒体接入控制MAC子协议数据单元SubPDU，或者所述第一接入节点对用户数据处理后得到的MAC PDU，或者所述第一接入节点对用户数据处理后得到的冗余版本RV版本数据。
  58. 如权利要求56或57所述的装置，其特征在于，所述收发单元，还用于接收来自第一接入节点的数据信息之前，向所述第一接入节点发送第二请求信息，所述第二请求信息用于请求数据信息。
  59. 如权利要求57所述的装置，其特征在于，所述收发单元，还用于接收逻辑信道信息，所述逻辑信道信息与用户数据所属用户的逻辑信道相关；
    所述处理单元，还用于根据所述逻辑信道信息，确定向所述终端设备发送的数据量。
  60. 如权利要求49-55任一项所述的装置，其特征在于，所述处理单元，还用于向所述第一接入节点发送数据信息，所述数据信息为下行数据信息。
  61. 如权利要求60所述的装置，其特征在于，所述调度信息包括用于重传的指示信息；
    所述收发单元，还用于当所述数据信息为用户数据，或所述通信装置对用户数据处理后得到的RLC PDU，或所述通信装置对用户数据处理后得到的MAC SubPDU，或者所述通信装置对用户数据处理后得到的MAC PDU，接收所述通信装置发送重传的调度信息； 当所述数据信息为所述通信装置对用户数据处理后得到的RV版本数据，向所述第一接入节点发送新的RV版本数据。
  62. 如权利要求56-61任一项所述的装置，其特征在于，所述收发单元，还用于接收来自终端设备的数据信息的反馈信息，所述反馈信息用于反馈数据信息发送成功或失败；向所述第一接入节点发送所述反馈信息。
  63. 如权利要求49-62任一项所述的装置，其特征在于，所述收发单元，还用于接收第一请求信息，所述第一请求信息用于请求调度信息，所述第一请求信息包括调度结果，向所述第一接入节点发送所述调度信息。
  64. 如权利要求49-63任一项所述的装置，其特征在于，所述第一接入节点的MAC实体与所述通信装置的MAC实体连接；或者所述第一接入节点的MAC实体分别与所述第一接入节点的PHY实体和所述通信装置的PHY实体连接。
  65. 一种通信装置，其特征在于，所述通信装置包括：处理器；
    所述处理器，用于读取存储器中存储的计算机程序或指令，并执行所述计算机程序或指令，以使所述通信装置执行如权利要求1-16中任一项所述的方法，或者，以使所述通信装置执行如权利要求17-32中任一项所述的方法。
  66. 如权利要求65所述的装置，其特征在于，所述通信装置还包括所述存储器，所述处理器与所述存储器耦合。
  67. 一种通信装置，其特征在于，所述通信装置包括：处理器和接口电路；
    所述接口电路，用于与所述通信装置之外的模块通信；
    所述处理器用于执行计算机程序或指令，以使所述通信装置执行如权利要求1-16中任一项所述的方法，或者，以使所述通信装置执行如权利要求17-32中任一项所述的方法。
  68. 一种计算机可读存储介质，其特征在于，包括计算机程序或指令，当其在计算机上运行时，使得权利要求1-16中任意一项所述的方法被执行，或者，使得权利要求17-32中任一项所述的方法被执行。
  69. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得权利要求1-16中任意一项所述的方法被执行，或者，使得权利要求17-32中任一项所述的方法被执行。
  70. 一种通信装置，其特征在于，所述通信装置用于执行如权利要求1-16中任一项所述的方法，或者，用于执行如权利要求17-32中任一项所述的方法。
  71. 一种通信系统，其特征在于，所述通信系统包括如权利要求33-48中任一项所述的通信装置和如权利要求49-64中任一项所述的通信装置。
PCT/CN2022/089919 2021-04-30 2022-04-28 一种通信方法及装置 WO2022228519A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22794989.8A EP4322448A1 (en) 2021-04-30 2022-04-28 Communication method and apparatus
US18/492,063 US20240049224A1 (en) 2021-04-30 2023-10-23 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110479909.XA CN115276924A (zh) 2021-04-30 2021-04-30 一种通信方法及装置
CN202110479909.X 2021-04-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/492,063 Continuation US20240049224A1 (en) 2021-04-30 2023-10-23 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2022228519A1 true WO2022228519A1 (zh) 2022-11-03

Family

ID=83745951

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/089919 WO2022228519A1 (zh) 2021-04-30 2022-04-28 一种通信方法及装置

Country Status (4)

Country Link
US (1) US20240049224A1 (zh)
EP (1) EP4322448A1 (zh)
CN (1) CN115276924A (zh)
WO (1) WO2022228519A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105850214B (zh) * 2014-09-29 2019-09-03 华为技术有限公司 无线网络调度方法，接入设备及无线网络
CN110831187A (zh) * 2018-08-10 2020-02-21 成都华为技术有限公司 一种资源配置的方法及装置
US20200145967A1 (en) * 2018-11-01 2020-05-07 Comcast Cable Communications, Llc Radio Resource Allocation for Access Link
WO2020229879A1 (en) * 2019-05-15 2020-11-19 Telefonaktiebolaget Lm Ericsson (Publ) Uplink control information (uci) coordination for distributed carrier aggregation (ca) scheduling

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105850214B (zh) * 2014-09-29 2019-09-03 华为技术有限公司 无线网络调度方法，接入设备及无线网络
CN110831187A (zh) * 2018-08-10 2020-02-21 成都华为技术有限公司 一种资源配置的方法及装置
US20200145967A1 (en) * 2018-11-01 2020-05-07 Comcast Cable Communications, Llc Radio Resource Allocation for Access Link
WO2020229879A1 (en) * 2019-05-15 2020-11-19 Telefonaktiebolaget Lm Ericsson (Publ) Uplink control information (uci) coordination for distributed carrier aggregation (ca) scheduling

Also Published As

Publication number Publication date
CN115276924A (zh) 2022-11-01
EP4322448A1 (en) 2024-02-14
US20240049224A1 (en) 2024-02-08

Similar Documents

Publication Publication Date Title
US11758537B2 (en) Method and apparatus for data transmission of terminal in wireless communication system
US10631296B2 (en) Resource allocation method, apparatus, and wireless access system
US10575360B2 (en) Apparatus and method for providing multi-connection using different wireless connection technologies in wireless communication system
EP3866364A1 (en) Method for sending data, apparatus for sending data, and terminal device
US11464040B2 (en) Data transmission method and apparatus
WO2019029639A1 (zh) 通信方法和通信装置
WO2020057404A1 (zh) 发送和接收上行控制信息的方法以及通信装置
KR20110004785A (ko) 공유 무선 자원을 이용한 기지국의 상향링크 수신 방법 및 단말기의 상향링크 송신 방법
US11956816B2 (en) Method and device for determining transmission time in wireless communication system
US20180146452A1 (en) Data transmission method and related device
WO2020168577A1 (zh) 传输上行反馈信息的方法、终端设备和网络设备
US20210250944A1 (en) Method and apparatus for transmitting control information for network cooperative communication
US20220167352A1 (en) User equipment and scheduling node
WO2020114237A1 (zh) 数据传输方法与通信装置
US20220312337A1 (en) Method and device for controlling uplink transmission power for network coordination communication system
US20210337516A1 (en) Communication control method
KR20220164475A (ko) 무선 통신 시스템에서 블라인드 디코딩 기반 하향링크 채널 송수신 방법 및 장치
KR102549723B1 (ko) 무선 통신 시스템에서 디폴트 공간 파라미터 기반 송수신 방법 및 장치
WO2022228519A1 (zh) 一种通信方法及装置
WO2022228518A1 (zh) 一种通信方法及装置
CN112930694A (zh) 用于执行车辆通信的方法和装置
EP4266806A1 (en) Device and method for handling a multi-cell scheduling
JP7418522B2 (ja) 無線通信システムにおいて上りリンク送受信を行う方法及び装置
WO2023202660A1 (zh) 一种跨分布式单元du的通信方法及相关装置
JP7448684B2 (ja) 無線通信システムにおいてｐｄｓｃｈ送受信方法及び装置

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: 22794989

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022794989

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022794989

Country of ref document: EP

Effective date: 20231108

NENP Non-entry into the national phase

Ref country code: DE