A DRB data transmission method and device, computer equipment and storage medium

Abstract

The present disclosure provides a DRB data transmission method and device, computer equipment and storage medium, and relates to the field of communication. In the method, a UE can selectively receive part of data of an immersive service transmitted by a downlink transmission resource matching the demand of the UE in different downlink transmission resources, or directly receive data of part of DRBs transmitted by a network device according to the receiving demand of the UE. The method can reduce network resource consumption and UE energy consumption while ensuring user experience. The network device does not need to transmit all data of the downlink immersive service to each UE, and the downlink resource consumption and base station energy consumption are also reduced.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to a DRB data transmission method, apparatus, computer equipment, and storage medium. Background Technology

[0002] Immersive communication is a communication method that uses technologies such as extended reality (XR) and holography to create an immersive and interactive experience for users, enabling them to interact more naturally and realistically with other people or the environment.

[0003] To achieve an immersive user experience, immersive communication service data needs to be sent to the data receiving end in real time. The receiving end then stores, uses, and transmits the 360-degree video. This method places high demands on the transmission rate and latency of the communication system, consuming a significant amount of bandwidth, posing a considerable challenge to wireless communication systems. Summary of the Invention

[0004] This disclosure provides at least one DRB data transmission method, apparatus, computer device, and storage medium to address the problems of large data volume, high transmission rate, and high latency requirements in immersive communication.

[0005] In a first aspect, embodiments of this disclosure provide a DRB data transmission method, applied to a user equipment (UE), comprising:

[0006] It receives data from a portion of the DRBs in multiple data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a single downlink service flow.

[0007] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0008] Receive downlink reference signal;

[0009] Channel quality measurement based on downlink reference signal;

[0010] After the detected channel quality is greater than the channel quality threshold, part of the DRB data transmitted by the Physical Downlink Shared Channel (PDSCH) corresponding to the downlink reference signal is received.

[0011] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0012] Receive the demodulation reference signal DMRS and receive part of the DRB data transmitted via the physical downlink shared channel PDSCH corresponding to DMRS.

[0013] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0014] Determine the parameters of the scrambling downlink scheduling command;

[0015] The downlink scheduling command is received according to the determined parameters of the scrambled downlink scheduling command, and the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command is also received.

[0016] In an optional implementation, the method further includes:

[0017] Report the UE's location and / or field of view (FoV) information to the network device.

[0018] In an optional implementation, the method further includes:

[0019] Receive reporting instruction information sent by network devices. The reporting instruction information is used to instruct the UE to report location and / or field of view (FoV) information.

[0020] In an optional implementation, the method further includes:

[0021] Receive at least one of the following configuration parameters:

[0022] QoS flow attribute parameters;

[0023] DRB attribute parameters;

[0024] Mapping relationship between QoS flow and DRB;

[0025] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0026] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0027] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0028] Multiple DMRS parameter configurations;

[0029] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0030] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0031] Secondly, embodiments of this disclosure also provide another DRB data transmission method, applied to a network device, including:

[0032] Mapping related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow.

[0033] Data from multiple DRBs can be transmitted based on different downlink transmission resources; or, data from a portion of multiple DRBs can be transmitted to the UE according to the UE's reception requirements.

[0034] In one alternative implementation, the different downlink transmission resources include at least one of the following:

[0035] Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

[0036] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0037] Data from different DRBs is carried by multiple Physical Downlink Shared Channels (PDSCHs), and different PDSCHs are mapped to different downlink transmission resources.

[0038] In this context, at least some data from different DRBs are not allowed to be multiplexed into the same physical layer transport block (TB); one TB is carried by one PDSCH.

[0039] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0040] Downlink reference signals are transmitted on different beam directions or different transmit-receive points (TRPs), and data from multiple DRBs are transmitted on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to the physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources, and different PDSCHs are used to carry data from multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE.

[0041] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0042] Transmit downlink reference signals in at least one beam direction or at least one transmit-receive point (TRP); receive channel quality reports detected by the UE for the downlink reference signals; and, based on the channel quality reports, transmit a portion of the DRB data in the beam direction or TRP corresponding to the downlink reference signals whose detected channel quality is greater than the channel quality threshold.

[0043] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0044] Transmit the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transport resources, and the data of the DRB carried by the PDSCH;

[0045] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0046] On at least one downlink transport resource that matches the UE's reception requirements, the corresponding demodulation reference signal DMRS and a portion of the DRB data mapped to the downlink transport resource are transmitted.

[0047] In an optional implementation, for cases where data from multiple DRBs is transmitted based on different downlink transport resources, the method further includes:

[0048] Send different downlink scheduling commands with different scrambling parameters; different downlink scheduling commands are used to schedule the Physical Downlink Shared Channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

[0049] In one optional implementation, data from a subset of multiple DRBs is sent to the UE according to the UE's reception requirements, including:

[0050] Based on the UE's position and / or field of view (FoV), send data from a portion of the multiple DRBs to the UE.

[0051] In one alternative implementation, the UE's position and / or field of view (FoV) are determined according to the following method:

[0052] A prediction algorithm is used to determine the UE's position and / or field of view (FoV); or,

[0053] Receive the location and / or field of view (FoV) information reported by the UE.

[0054] In an optional implementation, before receiving the location and / or field of view (FoV) information reported by the UE, the method further includes:

[0055] Send a reporting instruction to the UE. The reporting instruction is used to instruct the UE to report the location and / or field of view (FoV) information.

[0056] In one optional implementation, transmitting data for multiple DRBs based on different downlink transmission resources includes: transmitting data for multiple DRBs based on different downlink transmission resources via broadcast, multicast, or unicast.

[0057] or,

[0058] Based on the UE's reception requirements, data from a portion of multiple DRBs is sent to the UE, including via multicast or unicast.

[0059] In one optional implementation, it further includes:

[0060] Send at least one of the following configuration parameters:

[0061] QoS flow attribute parameters;

[0062] DRB attribute parameters;

[0063] Mapping relationship between QoS flow and DRB;

[0064] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0065] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0066] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0067] Multiple DMRS parameter configurations;

[0068] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0069] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0070] In an optional implementation, for the case of sending data for multiple DRBs based on different downlink transmission resources, the method further includes: sending configuration parameters via broadcast, multicast, or unicast; or,

[0071] For situations where data from multiple DRBs is sent to the UE based on the UE's reception requirements, the method also includes sending configuration parameters via multicast or unicast.

[0072] The configuration parameters are used by the UE to select the Physical Downlink Shared Channel (PDSCH) to receive.

[0073] Thirdly, embodiments of this disclosure also provide a DRB data transmission apparatus for a user equipment (UE), comprising:

[0074] The receiving module is used to receive data from a portion of the DRBs in multiple data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a downlink service flow.

[0075] In one optional implementation, the receiving module is specifically used for:

[0076] Receive downlink reference signal;

[0077] Channel quality measurement based on downlink reference signal;

[0078] After the detected channel quality is greater than the channel quality threshold, part of the DRB data transmitted by the Physical Downlink Shared Channel (PDSCH) corresponding to the downlink reference signal is received.

[0079] In one optional implementation, the receiving module is specifically used for:

[0080] Receive the demodulation reference signal DMRS and receive part of the DRB data transmitted via the physical downlink shared channel PDSCH corresponding to DMRS.

[0081] In one optional implementation, the receiving module is specifically used for:

[0082] Determine the parameters of the scrambling downlink scheduling command;

[0083] The downlink scheduling command is received according to the determined parameters of the scrambled downlink scheduling command, and the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command is also received.

[0084] In one optional implementation, the receiving module is further configured to:

[0085] Report the UE's location and / or field of view (FoV) information to the network device.

[0086] In one optional implementation, the receiving module is further configured to:

[0087] Receive reporting instruction information sent by network devices. The reporting instruction information is used to instruct the UE to report location and / or field of view (FoV) information.

[0088] In one optional implementation, the receiving module is further configured to:

[0089] Receive at least one of the following configuration parameters:

[0090] QoS flow attribute parameters;

[0091] DRB attribute parameters;

[0092] Mapping relationship between QoS flow and DRB;

[0093] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0094] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0095] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0096] Multiple DMRS parameter configurations;

[0097] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0098] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0099] Fourthly, embodiments of this disclosure also provide another DRB data transmission apparatus, applied to network devices, including:

[0100] The mapping module is used to map related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow.

[0101] The transmitting module is used to transmit data from multiple DRBs based on different downlink transmission resources; or, according to the UE's receiving requirements, to transmit data from a portion of multiple DRBs to the UE.

[0102] In one alternative implementation, the different downlink transmission resources include at least one of the following:

[0103] Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

[0104] In one optional implementation, the sending module is specifically used for:

[0105] Data from different DRBs is carried by multiple Physical Downlink Shared Channels (PDSCHs), and different PDSCHs are mapped to different downlink transmission resources.

[0106] In this context, at least some data from different DRBs are not allowed to be multiplexed into the same physical layer transport block (TB); one TB is carried by one PDSCH.

[0107] In one optional implementation, the sending module is specifically used for:

[0108] Downlink reference signals are transmitted on different beam directions or different transmit-receive points (TRPs), and data from multiple DRBs are transmitted on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to the physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources, and different PDSCHs are used to carry data from multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE.

[0109] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0110] Transmit downlink reference signals in at least one beam direction or at least one transmit-receive point (TRP); receive channel quality reports detected by the UE for the downlink reference signals; and, based on the channel quality reports, transmit a portion of the DRB data in the beam direction or TRP corresponding to the downlink reference signals whose detected channel quality is greater than the channel quality threshold.

[0111] In one optional implementation, the sending module is specifically used for:

[0112] Transmit the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transport resources, and the data of the DRB carried by the PDSCH;

[0113] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0114] On at least one downlink transport resource that matches the UE's reception requirements, the corresponding demodulation reference signal DMRS and a portion of the DRB data mapped to the downlink transport resource are transmitted.

[0115] In an optional implementation, for the case of transmitting data from multiple DRBs based on different downlink transmission resources, the transmitting module is further configured to:

[0116] Send different downlink scheduling commands with different scrambling parameters; different downlink scheduling commands are used to schedule the Physical Downlink Shared Channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

[0117] In one optional implementation, the sending module is specifically used for:

[0118] Based on the UE's position and / or field of view (FoV), send data from a portion of the multiple DRBs to the UE.

[0119] In one optional implementation, the device further includes a determining module for:

[0120] A prediction algorithm is used to determine the UE's position and / or field of view (FoV); or,

[0121] Receive the location and / or field of view (FoV) information reported by the UE.

[0122] In an optional implementation, before receiving the location and / or field of view (FoV) information reported by the UE, the determining module is further configured to:

[0123] Send a reporting instruction to the UE. The reporting instruction is used to instruct the UE to report the location and / or field of view (FoV) information.

[0124] In one optional implementation, the sending module is specifically used to: send data of multiple DRBs based on different downlink transmission resources via broadcast, multicast, or unicast.

[0125] or,

[0126] Based on the UE's reception requirements, data from a portion of multiple DRBs is sent to the UE, including via multicast or unicast.

[0127] In an optional implementation, the sending module is further configured to:

[0128] Send at least one of the following configuration parameters:

[0129] QoS flow attribute parameters;

[0130] DRB attribute parameters;

[0131] Mapping relationship between QoS flow and DRB;

[0132] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0133] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0134] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0135] Multiple DMRS parameter configurations;

[0136] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0137] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0138] In an optional implementation, for the case of sending data for multiple DRBs based on different downlink transmission resources, the sending module is further configured to: send configuration parameters via broadcast, multicast, or unicast; or,

[0139] For situations where data from multiple DRBs is sent to the UE based on the UE's reception requirements, the method also includes sending configuration parameters via multicast or unicast.

[0140] The configuration parameters are used by the UE to select the Physical Downlink Shared Channel (PDSCH) to receive.

[0141] Fifthly, embodiments of this disclosure also provide a computer device deployed on a user equipment (UE), including a memory, a transceiver, and a processor:

[0142] A memory for storing computer programs; a transceiver for sending and receiving data under the control of a processor; a processor for reading the computer programs from the memory and performing the following operations:

[0143] It receives data from a portion of the DRBs in multiple data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a single downlink service flow.

[0144] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0145] Receive downlink reference signal;

[0146] Channel quality measurement based on downlink reference signal;

[0147] After the detected channel quality is greater than the channel quality threshold, part of the DRB data transmitted by the Physical Downlink Shared Channel (PDSCH) corresponding to the downlink reference signal is received.

[0148] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0149] Receive the demodulation reference signal DMRS and receive part of the DRB data transmitted via the physical downlink shared channel PDSCH corresponding to DMRS.

[0150] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0151] Determine the parameters of the scrambling downlink scheduling command;

[0152] The downlink scheduling command is received according to the determined parameters of the scrambled downlink scheduling command, and the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command is also received.

[0153] In one alternative implementation, the processor is further configured to perform:

[0154] Report the UE's location and / or field of view (FoV) information to the network device.

[0155] In one alternative implementation, the processor is further configured to perform:

[0156] Receive reporting instruction information sent by network devices. The reporting instruction information is used to instruct the UE to report location and / or field of view (FoV) information.

[0157] In one alternative implementation, the processor is further configured to perform:

[0158] Receive at least one of the following configuration parameters:

[0159] QoS flow attribute parameters;

[0160] DRB attribute parameters;

[0161] Mapping relationship between QoS flow and DRB;

[0162] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0163] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0164] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0165] Multiple DMRS parameter configurations;

[0166] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0167] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0168] Sixthly, embodiments of this disclosure also provide a computer device deployed in a network device, including a memory, a transceiver, and a processor:

[0169] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0170] Mapping related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow.

[0171] Data from multiple DRBs can be transmitted based on different downlink transmission resources; or, data from a portion of multiple DRBs can be transmitted to the UE according to the UE's reception requirements.

[0172] In one alternative implementation, the different downlink transmission resources include at least one of the following:

[0173] Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

[0174] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0175] Data from different DRBs is carried by multiple Physical Downlink Shared Channels (PDSCHs), and different PDSCHs are mapped to different downlink transmission resources.

[0176] In this context, at least some data from different DRBs are not allowed to be multiplexed into the same physical layer transport block (TB); one TB is carried by one PDSCH.

[0177] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0178] Downlink reference signals are transmitted on different beam directions or different transmit-receive points (TRPs), and data from multiple DRBs are transmitted on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to the physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources, and different PDSCHs are used to carry data from multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE.

[0179] Alternatively, based on the UE's reception requirements, send data from a subset of multiple DRBs to the UE, including:

[0180] Transmit downlink reference signals in at least one beam direction or at least one transmit-receive point (TRP); receive channel quality reports detected by the UE for the downlink reference signals; and, based on the channel quality reports, transmit a portion of the DRB data in the beam direction or TRP corresponding to the downlink reference signals whose detected channel quality is greater than the channel quality threshold.

[0181] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0182] Transmit the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transport resources, and the data of the DRB carried by the PDSCH;

[0183] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0184] On at least one downlink transport resource that matches the UE's reception requirements, the corresponding demodulation reference signal DMRS and a portion of the DRB data mapped to the downlink transport resource are transmitted.

[0185] In an alternative implementation, for the case where data for multiple DRBs is transmitted based on different downlink transport resources, the processor is further configured to perform:

[0186] Send different downlink scheduling commands with different scrambling parameters; different downlink scheduling commands are used to schedule the Physical Downlink Shared Channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

[0187] In one optional implementation, data from a subset of multiple DRBs is sent to the UE according to the UE's reception requirements, including:

[0188] Based on the UE's position and / or field of view (FoV), send data from a portion of the multiple DRBs to the UE.

[0189] In one alternative implementation, the processor is specifically used to execute:

[0190] A prediction algorithm is used to determine the UE's position and / or field of view (FoV); or,

[0191] Receive the location and / or field of view (FoV) information reported by the UE.

[0192] In one optional implementation, before receiving the location and / or field of view (FoV) information reported by the UE, the processor is further configured to perform:

[0193] Send a reporting instruction to the UE. The reporting instruction is used to instruct the UE to report the location and / or field of view (FoV) information.

[0194] In one optional implementation, transmitting data for multiple DRBs based on different downlink transmission resources includes: transmitting data for multiple DRBs based on different downlink transmission resources via broadcast, multicast, or unicast.

[0195] or,

[0196] Based on the UE's reception requirements, data from a portion of multiple DRBs is sent to the UE, including via multicast or unicast.

[0197] In one alternative implementation, the processor is further configured to perform:

[0198] Send at least one of the following configuration parameters:

[0199] QoS flow attribute parameters;

[0200] DRB attribute parameters;

[0201] Mapping relationship between QoS flow and DRB;

[0202] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0203] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0204] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0205] Multiple DMRS parameter configurations;

[0206] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0207] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0208] In an optional implementation, for cases where data from multiple DRBs is transmitted based on different downlink transport resources, the processor is further configured to: transmit configuration parameters via broadcast, multicast, or unicast; or,

[0209] For situations where data from multiple DRBs is sent to the UE based on the UE's reception requirements, the method also includes sending configuration parameters via multicast or unicast.

[0210] The configuration parameters are used by the UE to select the Physical Downlink Shared Channel (PDSCH) to receive.

[0211] In a seventh aspect, embodiments of this disclosure also provide a processor-readable storage medium storing a computer program for causing a processor to perform the steps of the DRB data transmission method as described in the first aspect or any one of the first aspects, or to perform the steps of the DRB data transmission method as described in the second aspect or any one of the second aspects.

[0212] The DRB data transmission method, apparatus, computer equipment, and storage medium provided in this disclosure allow the UE to receive only a portion of the DRB data from multiple DRBs corresponding to the downlink service flow. For example, the network device can send data from multiple DRBs based on different downlink transmission resources, or directly send data from a portion of the DRBs that meet the UE's reception requirements to the UE. Correspondingly, the UE can selectively receive a portion of the immersive service data transmitted by the downlink transmission resources that match its own needs from different downlink transmission resources, or directly receive a portion of the DRB data sent by the network device according to the UE's reception requirements. This can reduce network resource overhead (in traditional methods, the network needs to send all service data to each UE) and UE energy consumption (the downlink scheduling commands, reference signals, and the amount of downlink data received by the UE are all reduced) while ensuring user experience. The network device does not need to send all the data of the downlink immersive service to each UE, which also reduces downlink resource overhead (reduces the occupation of downlink control channels, scheduling channels, and data transmission channels) and base station energy consumption (reduces the transmission overhead of downlink signaling and transmission, as well as the monitoring of UE feedback).

[0213] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0214] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0215] Figure 1 A schematic diagram of a communication system provided by some embodiments of this disclosure is shown;

[0216] Figure 2 A flowchart of a DRB data transmission method provided by some embodiments of this disclosure is shown;

[0217] Figure 3 The illustration shows schematic diagrams of immersive business scenarios in some embodiments of this disclosure;

[0218] Figure 4 A schematic diagram showing the UE receiving partial DRB data in some embodiments of this disclosure is illustrated;

[0219] Figure 5 A flowchart of another DRB data transmission method provided by some embodiments of this disclosure is shown;

[0220] Figure 6 A flowchart of another DRB data transmission method provided by some embodiments of this disclosure is shown;

[0221] Figure 7 A flowchart of another DRB data transmission method provided by some embodiments of this disclosure is shown;

[0222] Figure 8 A flowchart of another DRB data transmission method provided by some embodiments of this disclosure is shown;

[0223] Figure 9 A flowchart of another DRB data transmission method provided by some embodiments of this disclosure is shown;

[0224] Figure 10 A flowchart of another DRB data transmission method provided by some embodiments of this disclosure is shown;

[0225] Figure 11 A schematic diagram of a DRB data transmission apparatus provided in some embodiments of this disclosure is shown;

[0226] Figure 12 A schematic diagram of another DRB data transmission apparatus provided by some embodiments of the present disclosure is shown;

[0227] Figure 13 A schematic diagram of a computer device provided by some embodiments of the present disclosure is shown;

[0228] Figure 14 A schematic diagram of another computer device provided by some embodiments of the present disclosure is shown. Detailed Implementation

[0229] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown herein can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0230] The following explanations of some terms used in the embodiments of this disclosure are provided to facilitate understanding by those skilled in the art.

[0231] In this disclosure, the term "multiple" refers to two or more objects, and other quantifiers are similar. In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0232] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0233] This disclosure provides a DRB data transmission method, apparatus, computer device, and storage medium to address the problems of large data volume, high transmission rate, and high latency requirements in immersive communication.

[0234] The method, apparatus, and computer equipment are based on the same inventive concept. Since the methods, apparatus, and computer equipment solve problems in similar ways, the implementation of the computer equipment, apparatus, and method can refer to each other, and repeated parts will not be described again.

[0235] The technical solutions provided in this application can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as the Evolved Packet Core (EPC) and the 5G Core Network (5GC).

[0236] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in 5G or 6G systems, the terminal device may be called User Equipment (UE). Wireless terminal devices can be USB storage devices, other personal computer memory devices, and dongles. They can also communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices. For example, they can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the radio access network. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablets, and Machine-type Communication (MTC) terminal devices. Wireless terminal devices can also be referred to as systems, subscriber units, subscriber stations, mobile stations, mobile devices, remote stations, access points, remote terminals, access terminals, user terminals, user agents, user devices, and wireless access devices and routers / modems that meet the limitations of this definition; however, this application does not limit the scope of the embodiments.

[0237] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, the base station may also be called an access point, or a device in the access network that communicates with wireless terminal devices through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network device involved in this application embodiment can be an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, or a Home evolved Node B (HeNB), relay node, femto, pico, network testing equipment, etc., and is not limited in this application embodiment. In some network architectures, network devices may include centralized unit (CU) nodes and distributed unit (DU) nodes, which may also be geographically separated.

[0238] See Figure 1 The diagram illustrates a communication system provided in an embodiment of this disclosure. The communication system may include network devices and terminal devices. The terminal devices may include user equipment (UE), and the network devices may include base stations. In some possible implementations, the communication system may also include a core network. The base station may include a satellite base station and / or a terrestrial base station. The base station can establish communication connections with both the core network and the UE. After the core network prepares the service data required by the UE, it can send the service data to the base station. The base station can send the service data to the UE via a wireless link or other means. During the process of sending service data to the UE, the base station can allocate channel resources, allocate wireless resources to the UE, negotiate with the UE through control plane signaling to determine when and how to transmit data, and then transmit the data to the UE through a wireless interface.

[0239] In some scenarios, communication systems can provide immersive services to the user experience (UE), such as extended reality (XR) and holographic services. XR is a general term for different types of reality, referring to all environments and human-computer interactions that combine real and virtual elements, generated by computer technology and equipment. It includes forms such as augmented reality (AR), mixed reality (MR), and virtual reality (VR). Holographic services refer to a class of services based on holographic technology, typically involving creating immersive, intuitive, and interactive experiences for users through holographic images or 3D graphics. These services, through technologies such as holographic imaging and 3D projection, allow users to see, perceive, and interact with virtual or remote objects and people in space.

[0240] In XR service scenarios, the need to display multi-dimensional environmental and interactive data requires a much larger amount of data than 2D video. In holographic service scenarios, a single image is captured from different viewpoints, layers, and angles. For the same target or scene, the presented image differs from different viewpoints, and these different presented images are composed of different image domains. A complete holographic service presentation is completed by multiple data streams from different angles.

[0241] Typically, to achieve an immersive user experience, all immersive communication service data needs to be sent to the receiving end (UE) in real time. The receiving end can store 360-degree video, and the UE provides the viewing experience to the user based on the current viewpoint (holographic service) or field of view (immersive XR). However, the above method places high demands on the transmission rate and latency of the communication system, consuming a lot of bandwidth, which poses a great challenge for wireless communication systems, especially when applied to real-time interactive scenarios such as online games, education, and healthcare.

[0242] To address this issue, this disclosure provides a DRB data transmission method to solve the problems of large data volume, high transmission rate, and high latency requirements in immersive communication.

[0243] For the sake of brevity, this article mainly focuses on... Figure 1 The technical solution is described based on the communication system shown. Based on this technical concept, those skilled in the art will be able to implement similar technical solutions based on other communication systems, which will not be elaborated in detail here. Figure 1This is merely an example and does not limit the number or type of devices included in the system. The network architecture and business scenarios described in this disclosure are for illustrating the technical solutions of this disclosure and do not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will recognize, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0244] The DRB data transmission method provided in this disclosure will be described below with reference to specific embodiments.

[0245] Example 1

[0246] See Figure 2 The above is a flowchart of a DRB data transmission method provided in an embodiment of this disclosure, the method including:

[0247] S201. The network device maps associated Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow.

[0248] In wireless communication systems, a Quality of Service (QoS) flow is the basic unit of data transmission over the air interface (the wireless channel between the base station and user equipment). It is a logical entity that transmits uplink or downlink data from the physical layer to upper-layer protocols (such as the data link layer or network layer). A QoS flow is a logical entity that allocates specific resources and quality of service within the network. Each QoS flow corresponds to a specific set of transmission requirements, such as bandwidth, latency, packet loss rate, and priority. Its purpose is to ensure that different types of service flows (such as voice, video, data, and control information) receive appropriate network resources and scheduling based on their specific QoS requirements.

[0249] The aforementioned downlink service flow typically refers to the data flow transmitted from a network device to a UE (such as a mobile phone, computer, or other access device). In this embodiment of the disclosure, a downlink service flow can refer to the data flow corresponding to a service, where the service can refer to the aforementioned immersive service, such as immersive XR or holographic service.

[0250] In one possible implementation, the downlink service flow can be decomposed into multiple service data flows, and then each service data flow can be mapped to a QoS flow. When mapping service flow data to a QoS flow, one service data flow can be mapped to one QoS flow, or multiple service data flows can be mapped to one QoS flow.

[0251] Typically, when decomposing a downlink service flow into multiple service data flows, the decomposition can be based on the characteristics of different service data within the downlink service flow.

[0252] In immersive scenarios, immersive XR ensures users see continuous visuals by leveraging the user's position and introducing the concept of Field of View (FoV). FoV is defined as the area of ​​the field of view at a given moment (with the head fixed). It is the angle of the visible light field measured from the focal point, measured in degrees. Monocular FoV is the angle of the visible light field for one eye, while binocular FoV is the combination of the fields from both eyes. The binocular horizontal field of view is approximately 200° to 220°, while the vertical field of view is approximately 135°. The central field of view of binocular FoV is approximately 60°, known as the comfort zone, which is the area most sensitive to detail, while peripheral vision is more accepting of motion. In XR, degrees of freedom (DoF) are typically used to describe the number of independent motion parameters in 3D space. For scenarios where the user's position is fixed, 3DoF (including pitch, yaw, and roll) can be used; for scenarios where the user is continuously moving, 6DoF (including pitch, yaw, roll, forward / backward, left / right, and up / down) can be used. The image displayed by the UE differs depending on the FoV (Field of View).

[0253] In holographic services, a single image is captured from different viewpoints, layers, and angles. From the viewer's perspective, depending on the viewer's position relative to the image, different domains of this set of captured images are presented to the viewer. In holographic services, the viewer's position relative to the image is similar to the FoV (Field of View) in immersive XR, where the image presented to the UE (User Equipment) varies depending on the viewer's position.

[0254] Based on the above, in immersive services, the downlink service flow can also be decomposed according to the UE's location and / or FoV to obtain multiple service flow data. In this case, one or more service data flows can correspond to the location and / or FoV of a UE.

[0255] In one possible implementation, the data can be decomposed according to the different types of data in the downlink service. For example, the service data stream of the downlink service may include visual content data stream, audio content data stream, user interaction data stream, location information and sensor data stream, control signaling data stream, etc.

[0256] In a scenario combined with a method of decomposing downlink services based on the UE's location and / or FoV, the downlink service data stream may include visual content data streams corresponding to the locations and / or FoVs of multiple UEs, audio content data streams corresponding to the locations and / or FoVs of multiple UEs, user interaction data streams corresponding to the locations and / or FoVs of multiple UEs, location information and sensor data streams corresponding to the locations and / or FoVs of multiple UEs, and control signaling data streams corresponding to the locations and / or FoVs of multiple UEs, etc.

[0257] It is worth noting that "UE location and / or FoV" here can refer to a location and / or FoV where the UE may be located, rather than specifically referring to the location and / or FoV of a particular UE.

[0258] In one possible implementation, the steps of decomposing the downlink service flow and mapping the decomposed service data flow to QoS flow can be performed by a core network device in the communication system. The core network device can be a type of network device. The core network device can decompose the downlink service flow into multiple service data flows, and the data from one or more service data flows can form a visual presentation, which can correspond to the location and / or FOV of a UE.

[0259] The aforementioned downlink service flow can correspond to multiple QoS flows. These multiple QoS flows can contain one or more sets of related QoS flows. When allocating resources to QoS flows, related QoS flows can be mapped to one or more Data Radio Bearers (DRBs).

[0260] The aforementioned related QoS flows can share the same characteristics. For example, QoS flows corresponding to the same UE location and / or FoV can be considered as a group of related QoS flows. For instance, if there is a QoS flow corresponding to a video data flow and a QoS flow corresponding to an audio data flow, and the UE locations and / or FoVs corresponding to both are the same, then they are related QoS flows.

[0261] When mapping related QoS flows to one or more DRBs, related QoS flows can be mapped to the same DRB or to multiple DRBs. Multiple DRBs mapped to related QoS flows can form a DRB group (that is, mapping related QoS flows to one DRB group).

[0262] In one possible implementation, multiple DRBs of a service data stream (i.e., a service) can be divided into different DRB groups, and multiple DRB groups can be used to transmit service data corresponding to multiple locations and / or FoVs.

[0263] DRB refers to the logical bearer channel used to transmit user data in a Radio Access Network (RAN). Each DRB provides specific transmission quality and bandwidth guarantees to carry uplink and downlink user plane data. The main function of a DRB is to carry user plane data streams, i.e., data streams from user equipment (UE) to base station (eNB / gNB) or from base station to user equipment. Each DRB is responsible for the transmission of a specific type of data stream and provides corresponding Quality of Service (QoS) guarantees.

[0264] A single DRB can carry multiple QoS flows, each representing a data flow with different quality of service requirements. Based on different QoS requirements (such as bandwidth and latency), the network allocates an appropriate DRB for each QoS flow. The DRB is the interface between the physical link layer and upper-layer protocols (such as RRC and IP layers), ensuring efficient data transmission over the wireless link. It is responsible for tasks such as data encapsulation, encryption, and scheduling. Different service types (such as voice, video, and data) may require different DRBs to guarantee their quality of service. For example, voice streams may require low-latency, high-priority DRBs, while video streams may require higher bandwidth and lower latency.

[0265] The steps described above, which map related QoS flows to one or more DRBs, can be performed by core network equipment or by base stations. The specific network equipment used can be determined based on specific requirements.

[0266] In one possible implementation, the base station can receive the correlation between QoS flows sent by the core network equipment, as well as the mapping relationship between QoS flows and the UE's location and / or FoV. The base station can use this information to map QoS flows to DRBs.

[0267] After the network device maps related QoS flows to one or more DRBs, the data from one or more DRBs (with related QoS flows) can be presented as a screen showing the location of a UE and / or the FoV.

[0268] S202. The network device sends data from multiple DRBs based on different downlink transmission resources; or, according to the UE's receiving requirements, it sends data from a portion of the multiple DRBs to the UE.

[0269] Typically, in immersive service scenarios, the UE needs to receive all downlink immersive service data (i.e., downlink service data). With the massive amount of downlink service data, it's difficult to guarantee transmission rate and latency. Research has shown that in immersive XR and holographic service scenarios, the UE can present a suitable image using only a portion of the downlink service data (such as the current UE's location and / or FoV-related data). Therefore, this disclosure embodiment transmits different DRBs or DRB groups of data using different downlink transmission resources, enabling the UE to selectively receive downlink service data according to its own reception needs, or to only send the portion of the DRB data required by the UE. This reduces UE network resource overhead and UE power consumption while ensuring user experience; the network device does not need to send all downlink immersive service data to each UE, thus also reducing downlink resource overhead and base station power consumption.

[0270] In this step, after mapping related QoS flows to one or more DRBs, the network device can send data to the UE. Since the data from one or more DRBs can present a picture corresponding to a UE's location and / or FoV, the UE can present the picture it needs to display by only receiving the data from the DRBs that match its own location and / or FoV.

[0271] When a network device sends data to a UE, it can map multiple DRBs to different downlink transmission resources and use different downlink transmission resources to send the data of these DRBs. The UE can select the appropriate downlink transmission resource to receive data according to its own reception needs.

[0272] Alternatively, network devices can directly send the required portion of the DRB data to a UE based on the UE's reception requirements.

[0273] The aforementioned downlink transmission resources refer to the physical or logical resources in a communication network used to support the transmission of data from network base stations or the core network to terminal devices (such as mobile phones, computers, or other access devices). In wireless communication systems, resources are mainly composed of factors such as time, frequency, and power, and are typically used for data transmission, scheduling, encoding, modulation, and other operations.

[0274] In one possible implementation, the different downlink transmission resources described above may include at least one of the following:

[0275] Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

[0276] Among these, time-domain resources refer to the time periods allocated for data transmission, describing the transmission of signals at different points in time. Time-domain resource management is achieved by allocating transmission time slots or time windows. Frequency-domain resources refer to the frequency ranges allocated to different users or data streams in the spectrum. Frequency-domain resources describe the distribution and utilization of signals at different frequencies. Spatial-domain resources refer to the distribution or transmission path of wireless signals in physical space. Through multi-antenna technology, signals can be spatially allocated, thereby improving data transmission capacity and efficiency.

[0277] When a network device transmits data from multiple DRBs based on different downlink transmission resources, it can do so via broadcast, multicast, or unicast. When a network device transmits data from only a portion of multiple DRBs to a UE based on the UE's reception requirements, it can transmit the partial DRB data via multicast or unicast.

[0278] Network devices can carry data from different DRBs on multiple Physical Downlink Shared Channels (PDSCHs), with different PDSCHs mapped to different downlink transmission resources.

[0279] Specifically, data from at least some DRBs in different DRBs are not allowed to be multiplexed to the same physical layer transport block (TB), or data from at least some DRB groups in different DRB groups are not allowed to be multiplexed to the same TB; one TB is carried by one PDSCH.

[0280] The aforementioned PDSCH is a physical channel, belonging to the shared channel type, responsible for transmitting data from the base station to the UE. PDSCH resource allocation can be controlled by the base station's scheduler, which can allocate appropriate time-frequency resources based on each user's channel quality, priority, and data requirements.

[0281] In one possible implementation, some data from different DRBs can be reused in the same TB.

[0282] The aforementioned TB can refer to a basic unit of data transmission, which is a data block carried at the physical layer. In the physical layer of the wireless network, it is divided into several physical resources for actual transmission.

[0283] In some implementations, where data from at least some DRBs in different DRBs are not allowed to be reused in the same TB, the UE locations and / or FoVs corresponding to the data of these DRBs can be different. For example, data from DRBs corresponding to the same UE location and / or FoV can be reused in the same TB, while data from DRBs corresponding to different UE locations and / or FoVs cannot be reused in the same TB. As another example, where data from at least some DRB groups in different DRB groups are not allowed to be reused in the same TB, data from the same DRB group corresponding to the same UE location and / or FoV can be reused in the same TB, while data from different DRB groups corresponding to different UE locations and / or FoVs cannot be reused in the same TB.

[0284] Thus, when a UE receives a TB of data, the data it receives is the DRB data corresponding to the UE's location and / or FoV.

[0285] S203, The UE receives data from a portion of the multiple DRBs.

[0286] In this step, when the network device sends data from multiple DRBs based on different downlink transmission resources, the UE can select the downlink transmission resource that matches its reception requirements and receive the data transmitted on the selected downlink transmission resource. Alternatively, when the network device sends data from only a portion of multiple DRBs to the UE based on its reception requirements, the UE can directly receive that portion of the DRB data according to the network device's scheduling command.

[0287] In one implementation, multiple DRBs corresponding to a service can be divided into different DRB groups; the UE receiving data from a portion of the multiple DRBs can refer to the UE receiving data from one or more DRBs from the multiple DRBs, or it can refer to the UE receiving data from a portion of the multiple DRB groups.

[0288] The data from some of the multiple DRBs received by the UE can be associated with the UE's location and / or FoV. For example, the UE can selectively receive the data from some DRBs transmitted by the corresponding downlink transmission resources based on its own location and / or FoV, or it can directly receive the data from some DRBs transmitted by the network device to the UE based on the UE's location and / or FoV.

[0289] After the UE obtains data from a portion of the aforementioned DRBs, it can present service information corresponding to the UE's location and / or FoV based on that portion of the DRB data.

[0290] See Figure 3 as well as Figure 4 The figures shown are schematic diagrams of an immersive service scenario in this embodiment of the present disclosure, and schematic diagrams of the UE receiving some DRB data. Figure 3 In this scenario, the data required by UEs located in different locations and / or with FoV varies. Figure 4 In this context, the data that a UE in different locations needs to receive from certain DRBs may differ. For example, a UE in the first location or the first FoV may receive data from DRB1, DRB2, DRB3, and DRB4, while a UE in the second location or the second FoV may receive data from DRB1, DRB2, and DRB3.

[0291] Thus, through the DRB data transmission method provided in this disclosure, the UE can receive only a portion of the DRB data from multiple DRBs corresponding to the downlink service flow. For example, the network device can send data from multiple DRBs based on different downlink transmission resources, or directly send data from a portion of the DRBs that meet the UE's reception requirements to the UE. Correspondingly, the UE can selectively receive a portion of the immersive service data transmitted by the downlink transmission resources that match its own needs from different downlink transmission resources, or directly receive a portion of the DRB data sent by the network device according to the UE's reception requirements. This can reduce network resource overhead (in the traditional way, the network needs to send all service data to each UE) and UE energy consumption (the downlink scheduling commands, reference signals, and the amount of downlink data received by the UE are all reduced) while ensuring user experience. The network device does not need to send all the data of the downlink immersive service to each UE, which also reduces downlink resource overhead (reduces the occupation of downlink control channels, scheduling channels, and data transmission channels) and base station energy consumption (reduces the transmission overhead of downlink signaling and transmission, as well as the listening to UE feedback).

[0292] In the embodiments disclosed herein, various methods for sending data to the UE can be provided. The specific methods for sending data to the UE will be described below in conjunction with several embodiments.

[0293] Example 2

[0294] In this embodiment, the UE can selectively receive signals based on channel detection of the reference signal.

[0295] See Figure 5 The diagram shows a flowchart of another DRB data transmission method provided in this embodiment of the present disclosure. The method includes:

[0296] S501, the core network equipment decomposes the downlink service flow into multiple service data flows, maps the multiple service data flows to multiple QoS flows, and sends the correlation between QoS flows, as well as the mapping relationship between QoS flows and UE location and / or FoV, to the base station.

[0297] S502, The base station maps associated QoS flows to one or more data radio bearers (DRBs).

[0298] Multiple QoS flows correspond to one downlink service flow. A DRB or a group of DRBs can present service data for a location and / or FoV.

[0299] S503. The base station transmits downlink reference signals in different beam directions or different transmission receiving points (TRPs), and transmits data of multiple DRBs on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to the physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources. Different PDSCHs are used to carry data of multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE.

[0300] In this step, the base station can map multiple DRBs or DRB groups to downlink transmission resources corresponding to different beam directions or different TRPs.

[0301] The beam direction mentioned above refers to the directional direction of signals generated and transmitted using beamforming technology in wireless communication. Beamforming is a technique used in wireless communication that controls the phase and amplitude of multiple antenna elements to make signals propagate in a specific direction in space, thereby improving signal quality, enhancing signal strength, and reducing interference. The Transmission Reception Point (TRP) represents the specific location or device point at the physical layer where signal transmission and reception occur. The concept of TRP can be used to describe the antenna configuration used for data transmission and reception.

[0302] In this step, for the UE, the channel quality of downlink transmission resources corresponding to different beam directions or different TRPs varies. Generally speaking, channel quality is mainly affected by the relative position between the UE and spatial resources. The base station transmits and receives signals through antenna arrays. The type, shape, and deployment height of the antenna array all affect the signal propagation direction and coverage. The base station can use beamforming technology to adjust the beam direction of the antenna array according to the relative position of the user equipment, concentrating the signal in the direction of the target user equipment and enhancing the signal reception strength. This means that channel quality is not only related to distance, but also to the relative direction of the UE's location and whether the base station can effectively direct the beam. Even with a fixed beam direction or TRP configuration for multiple downlink transmission resources, the channel quality of each downlink transmission resource will differ. Therefore, the base station can transmit downlink reference signals to measure channel quality.

[0303] It is evident that the UE's reception requirements can be represented by the UE's location and / or FoV.

[0304] In immersive service scenarios, the data required by the UE is related to the UE's location and / or FoV. The channel quality of different downlink transmission resources is also related to the UE's location. Therefore, the data of a specific UE's location and / or FoV can be mapped to the downlink transmission resources corresponding to a specific beam direction or TRP. The UE can detect the channel quality of each downlink transmission resource, select the appropriate downlink transmission resource to receive data, and achieve directional reception of the data it needs.

[0305] To measure the channel quality of different downlink transmission resources, the base station can transmit a downlink reference signal for the downlink transmission resources. The UE can parse this downlink reference signal and use it to perform channel quality measurements to determine the channel quality of the downlink transmission resources. Once the UE detects that the channel quality is greater than a channel quality threshold, it can receive a portion of the DRB data transmitted via the PDSCH corresponding to the downlink reference signal.

[0306] In this step, different beam directions or different TRPs can correspond to different downlink reference signals. Each downlink reference signal can correspond to one or more PDSCHs. The PDSCH can be associated with the UE's location and / or FoV. Then the downlink reference signal corresponding to the PDSCH is also associated with the UE's location and / or FoV.

[0307] The base station can transmit a corresponding downlink reference signal in at least one beam direction or on at least one TRP. This downlink reference signal can be transmitted together with the corresponding PDSCH. The base station can transmit the downlink reference signal via broadcast, multicast, or unicast.

[0308] Different beam directions or different TRPs can correspond to different UE locations and / or FoVs. Corresponding PDSCHs and downlink reference signals can be transmitted on different beam directions or different TRPs. DRB data transmitted on one PDSCH can correspond to the same UE's location and / or FoV.

[0309] The aforementioned downlink reference signal can be transmitted by the base station to assist the UE in performing channel estimation, synchronization, demodulation, and other signal processing tasks. The downlink reference signal is fundamental for accurate channel estimation during communication; it provides the UE with a known signal, enabling the device to estimate and compensate for channel distortion, thereby effectively demodulating and receiving data.

[0310] The aforementioned downlink reference signals can be, for example, a synchronization signal block, a synchronization signal / physical broadcast channel block (SS / PBCH block), or a channel state information-reference signal (CSI-RS).

[0311] To enable the UE to receive data in the aforementioned manner, the base station can configure the UE by sending configuration parameters. These configuration parameters are settings assigned by the base station to the UE, ensuring the device can correctly connect and exchange data with the network. These parameters typically cover multiple aspects from the physical layer to the application layer, including radio access, resource scheduling, signaling management, and Quality of Service (QoS).

[0312] The above configuration parameters can be sent via broadcast, multicast, or unicast, and the configuration parameters may include at least one of the following:

[0313] QoS flow attribute parameters;

[0314] DRB attribute parameters;

[0315] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0316] Channel quality threshold;

[0317] Mapping relationship between QoS flow and DRB;

[0318] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV).

[0319] The QoS flow attribute parameters may include one or more parameters such as QoS Flow Identifier (QFI), Bearer Type, Priority Level, Delay Class, Throughput Class, Service Level Agreement (SLA), Bearer Path Identifier, Traffic Filters, Congestion Control, Max Reserved Bandwidth, Packet Delay Budget (PDB), and Data Volume. DRB attribute parameters can include attribute parameters of a single DRB or a group of DRBs, such as DRB ID, QoS flow identifier, bearer type, bearer path identifier, quality of service parameters (such as latency, packet loss rate, throughput, priority), maximum reserved bandwidth, encryption and integrity protection, bearer scheduling and prioritization, traffic filtering rules, uplink-downlink symmetry, uplink-downlink latency requirements, service level agreement (SLA) of the bearer, and bearer path selection, among other parameters.

[0320] In one possible implementation, the mapping relationship between QoS flow and DRB, and the association relationship between DRB or logical channel or QoS flow and UE location and / or FoV can be respectively used as one of the DRB attribute parameters.

[0321] S504. The UE receives the downlink reference signal; performs channel quality measurement based on the downlink reference signal; and after the detected channel quality is greater than the channel quality threshold, receives part of the DRB data transmitted by the PDSCH corresponding to the downlink reference signal.

[0322] In this step, the UE can receive the corresponding downlink reference signal when it is able to receive the data PDSCH, and perform channel quality measurement based on the downlink reference signal. When the detected channel quality is greater than the channel quality threshold, the UE can receive part of the DRB data transmitted by the PDSCH corresponding to the downlink reference signal.

[0323] In one possible implementation, the UE may have multiple downlink reference signals, and there may be multiple downlink reference signals with channel quality greater than the channel quality threshold. The UE can select the data of the DRB transmitted by the PDSCH corresponding to the downlink reference signal with the highest channel quality.

[0324] In this way, by using different downlink reference signals to measure channel quality, the UE can select a portion of the DRB data that matches its own reception requirements.

[0325] Example 3

[0326] In this embodiment, the network device can selectively transmit based on channel detection of the reference signal.

[0327] See Figure 6 The diagram shows a flowchart of another DRB data transmission method provided in this embodiment of the present disclosure. The method includes:

[0328] S601, the core network equipment decomposes the downlink service flow into multiple service data flows, maps the multiple service data flows to multiple QoS flows, and sends the correlation between QoS flows, as well as the mapping relationship between QoS flows and UE location and / or FoV, to the base station.

[0329] S602, The base station maps QoS flows with associations to one or more data radio bearers (DRBs).

[0330] Multiple QoS flows correspond to one downlink service flow. A DRB or a group of DRBs can present service data for a location and / or FoV.

[0331] S603. The base station transmits a downlink reference signal in at least one beam direction or on at least one TRP.

[0332] In this step, one beam direction or one TRP can correspond to one or more downlink reference signals; one downlink reference signal can correspond to one or more PDSCHs. A PDSCH can be associated with the UE's location and / or FoV, and the downlink reference signal corresponding to the PDSCH is also associated with the UE's location and / or FoV.

[0333] The base station can transmit a corresponding downlink reference signal in at least one beam direction or on at least one TRP. This downlink reference signal can be transmitted together with the corresponding PDSCH.

[0334] The aforementioned downlink reference signals can be, for example, a synchronization signal block, a synchronization signal / physical broadcast channel block (SS / PBCH block), or a channel state information-reference signal (CSI-RS).

[0335] To enable the UE to receive data in the aforementioned manner, the base station can also configure the UE by sending configuration parameters. These configuration parameters can be sent via broadcast, multicast, or unicast, and may include at least one of the following:

[0336] QoS flow attribute parameters;

[0337] DRB attribute parameters;

[0338] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0339] Channel quality threshold;

[0340] Mapping relationship between QoS flow and DRB;

[0341] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV).

[0342] S604. The UE receives the downlink reference signal and performs channel quality measurement based on the downlink reference signal.

[0343] The UE can receive one or more downlink reference signals and perform channel quality measurements based on the received downlink reference signals to obtain the channel quality corresponding to the downlink reference signals. After obtaining the channel quality corresponding to the downlink reference signals, the UE can send a channel quality report of the detected downlink reference signals back to the base station. The channel quality report may indicate downlink reference signals with channel quality greater than the channel quality threshold, or the beam direction or TRP corresponding to the downlink reference signal, or the PDSCH corresponding to the downlink reference signal, or indicate the channel quality corresponding to each downlink reference signal.

[0344] S605. The base station receives the channel quality report detected by the UE for the downlink reference signal; based on the channel quality report, it transmits part of the DRB data on the beam direction or TRP corresponding to the downlink reference signal whose detected channel quality is greater than the channel quality threshold.

[0345] In this step, the base station can determine the downlink reference signal whose detected channel quality is greater than the channel quality threshold based on the UE's channel quality report, and transmit some of the DRB data from the above multiple DRBs on the beam direction or TRP corresponding to the downlink reference signal whose detected channel quality is greater than the channel quality threshold.

[0346] In one possible implementation, the base station can transmit data from a portion of the multiple DRBs on the beam direction corresponding to the downlink reference signal where the detected channel quality is greater than the channel quality threshold, or on the PDSCH corresponding to the TRP. For the data from the other DRBs besides a portion of the DRBs, the base station does not need to transmit them; it can buffer them or discard them directly.

[0347] S606. The UE receives part of the DRB data transmitted by the PDSCH corresponding to the downlink reference signal whose channel quality is greater than the channel quality threshold.

[0348] In this step, since the base station transmits part of the DRB data in the beam direction or TRP corresponding to the downlink reference signal whose detected channel quality is greater than the channel quality threshold, the UE does not need to select the PDSCH to receive and can directly receive part of the DRB data transmitted by the PDSCH corresponding to the downlink reference signal whose channel quality is greater than the channel quality threshold.

[0349] Example 4

[0350] In this embodiment, the UE selectively receives signals based on the demodulation reference signal.

[0351] See Figure 7 The diagram shows a flowchart of another DRB data transmission method provided in this embodiment of the present disclosure. The method includes:

[0352] S701, the core network equipment decomposes the downlink service flow into multiple service data flows, maps the multiple service data flows to multiple QoS flows, and sends the correlation between QoS flows, as well as the mapping relationship between QoS flows and UE location and / or FoV, to the base station.

[0353] S702, The base station maps related QoS flows to one or more data radio bearers (DRBs).

[0354] Multiple QoS flows correspond to one downlink service flow. A DRB or a group of DRBs can present service data for a location and / or FoV.

[0355] S703, the base station transmits the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transmission resources, and the DRB data carried by the PDSCH.

[0356] In this step, the base station can directly map different DRBs or DRB groups to different PDSCHs, and through the demodulation reference signals corresponding to different PDSCHs, enable the UE to select the PDSCH that meets its own reception requirements.

[0357] The aforementioned Demodulation Reference Signal (DMRS) can be transmitted along with the PDSCH. Typically, the main purpose of the DMRS is to assist the receiver (usually a base station or user equipment) in demodulating the signal and estimating the channel to ensure correct data reception. In this embodiment, different DMRSs can be associated with the UE's location and / or FoV; that is, corresponding DMRSs can be configured for different UE locations and / or FoVs. Thus, since the DMRS corresponds to the PDSCH, the UE can determine its DMRS configuration based on its own location and / or FoV, and receive the corresponding DMRS and PDSCH according to the DMRS configuration.

[0358] For example, the base station can configure corresponding demodulation reference signals for PDSCHs mapped to various downlink transmission resources, and determine the mapping relationship between the demodulation reference signals and the UE's location and / or FoV based on the mapping relationship between the PDSCH and the UE's location and / or FoV. The UE can receive the mapping relationship between the demodulation reference signals and the UE's location and / or FoV, or the UE can determine the mapping relationship between the demodulation reference signals and the UE's location and / or FoV based on a protocol or pre-configured parameters, thereby determining a PDSCH that matches the UE's own reception requirements based on the mapping relationship between the demodulation reference signals and the UE's location and / or FoV.

[0359] To enable the UE to receive data that meets its reception requirements, the base station can also send configuration parameters to the UE. Configuration parameters can be sent via broadcast, multicast, or unicast, and can include at least one of the following:

[0360] QoS flow attribute parameters;

[0361] DRB attribute parameters;

[0362] Mapping relationship between QoS flow and DRB;

[0363] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0364] Multiple DMRS parameter configurations;

[0365] The mapping relationship between different DMRS parameter configurations and the UE's position and / or field of view (FoV).

[0366] The multiple DMRS parameter configurations can include configuration parameters for each DMRS, such as DMRS type, DMRS position, number of antenna ports, DMRS sequence length, DMRS power, number of DMRS symbols, DMRS frequency domain distribution, DMRS periodicity, DMRS sequence mapping, resource element mapping, DMRS reference symbol mapping, reception threshold, resource location, etc.

[0367] S704. The UE receives the demodulation reference signal DMRS and receives part of the DRB data transmitted via the physical downlink shared channel PDSCH corresponding to the DMRS.

[0368] In this step, the UE can determine the DMRS configuration that matches its own location and / or FoV, and receive the corresponding DMRS according to the DMRS configuration, and receive part of the DRB data carried by the PDSCH corresponding to the DMRS.

[0369] Example 5

[0370] In this embodiment, the network device directly sends DMRS and corresponding DRB data according to the UE's reception requirements.

[0371] See Figure 8 The diagram shows a flowchart of another DRB data transmission method provided in this embodiment of the present disclosure. The method includes:

[0372] S801, the core network equipment decomposes the downlink service flow into multiple service data flows, maps the multiple service data flows to multiple QoS flows, and sends the correlation between QoS flows, as well as the mapping relationship between QoS flows and UE location and / or FoV, to the base station.

[0373] S802, the base station maps associated QoS flows to one or more data radio bearers (DRBs).

[0374] Multiple QoS flows correspond to one downlink service flow. A DRB or a group of DRBs can present service data for a location and / or FoV.

[0375] S803. The base station transmits the corresponding DMRS and part of the DRB mapped to the downlink transmission resource on at least one downlink transmission resource that matches the UE's reception requirements.

[0376] In this step, the base station can obtain the UE's reception requirements and determine the downlink transmission resources that match the UE's reception requirements, and then send DMRS and part of the DRB data mapped to the downlink transmission resources on the downlink transmission resources that match the UE's reception requirements.

[0377] To determine the UE's reception requirements, the base station can determine the UE's location and / or FoV. For example, the base station can send a reporting indication message to the UE, instructing the UE to report its location and / or FoV information. After receiving the reporting indication message, the UE can send its own location and / or FoV to the base station, enabling the base station to determine at least one downlink transmission resource matching the UE's reception requirements. The base station can then transmit the corresponding DMRS and a portion of the DRB mapped to the downlink transmission resource on the at least one downlink transmission resource matching the UE's reception requirements via multicast or unicast.

[0378] Alternatively, the base station may employ a predictive algorithm to determine the UE's location and / or FoV. In one possible implementation, the base station may use one or more of the following methods to estimate or predict the UE's location and / or FoV: signal measurement data, transmission models, machine learning algorithms, etc.

[0379] In this embodiment, the base station can also send configuration parameters. The method of sending configuration parameters can be found in the relevant content of Embodiment 4, and will not be repeated here.

[0380] S804. The UE receives the demodulation reference signal DMRS and receives part of the DRB data transmitted via the physical downlink shared channel PDSCH corresponding to the DMRS.

[0381] In this step, the UE can directly receive the data of part of the DRB transmitted by the DMRS and the PDSCH corresponding to the DMRS sent by the base station, without the UE needing to select the DMRS and the PDSCH corresponding to the DMRS.

[0382] Example 6

[0383] In this embodiment, downlink scheduling commands based on parameter scrambling are selectively received.

[0384] See Figure 9 The diagram shows a flowchart of another DRB data transmission method provided in this embodiment of the present disclosure. The method includes:

[0385] S901, the core network equipment decomposes the downlink service flow into multiple service data flows, maps the multiple service data flows to multiple QoS flows, and sends the correlation between QoS flows, as well as the mapping relationship between QoS flows and UE location and / or FoV, to the base station.

[0386] S902, the base station maps related QoS flows to one or more data radio bearers (DRBs).

[0387] Multiple QoS flows correspond to one downlink service flow. A DRB or a group of DRBs can present service data for a location and / or FoV.

[0388] S903. The base station sends different downlink scheduling commands with different scrambling parameters; the different downlink scheduling commands are used to schedule the physical downlink shared channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

[0389] In this step, the base station can map different parameters to the UE's location and / or FoV, and map the parameters to different downlink scheduling commands, using the parameters to scramble the corresponding downlink scheduling commands. The downlink scheduling commands can be used to schedule PDSCHs carrying data in different DRBs (or DRB groups) transmitted on different downlink transmission resources. The parameters corresponding to the downlink scheduling commands and the DRBs can be associated with the UE's location and / or FoV. In one possible implementation, the UE's location and / or FoV corresponding to the parameters of the downlink scheduling command can be the same as the UE's location and / or FoV corresponding to the PDSCH of the downlink scheduling command.

[0390] The parameters mentioned above can be Radio Network Temporary Identifiers (RNTIs), which are temporary identifiers used to identify and distinguish different UEs or service data streams. By scrambling different downlink scheduling commands using different RNTIs, the UE can determine the corresponding RNTI based on its own location and / or FoV, and thus determine the downlink scheduling command to be executed.

[0391] In one possible implementation, the base station can send different downlink scheduling commands scrambled with different parameters using broadcast, multicast, or unicast methods.

[0392] The base station can send at least one of the following configuration parameters via broadcast, multicast, or unicast:

[0393] QoS flow attribute parameters;

[0394] DRB attribute parameters;

[0395] The parameters corresponding to different DRBs or DRB groups, and the mapping relationship between different parameters and positions and / or FoV;

[0396] Mapping relationship between QoS flow and DRB;

[0397] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0398] S904, the UE determines the parameters of the scrambling downlink scheduling command; and receives the downlink scheduling command according to the determined parameters of the scrambling downlink scheduling command, and receives the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command.

[0399] In this step, the UE can receive downlink scheduling commands sent by one or more base stations, and use its own location and / or FoV, as well as the scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV, to determine one or more downlink scheduling commands that match its own reception requirements, and receive the data transmitted by the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command.

[0400] In one possible implementation, the base station can also acquire the UE's reception requirements and, based on those requirements, directly send a downlink scheduling command matching the UE's reception requirements to the UE. This downlink scheduling command can be scrambled using parameters corresponding to the UE's location and / or FoV, and the data (DRB data) transmitted via the PDSCH scheduled by the downlink scheduling command is associated with the UE's location and / or FoV. The base station can send data from multiple DRBs to the UE via multicast or unicast, based on the UE's reception requirements. For details on how the base station acquires the UE's reception requirements in this step, please refer to the relevant content in Embodiment 5.

[0401] Example 7

[0402] In this embodiment, the network device selectively transmits based on the UE's location and / or FoV.

[0403] See Figure 10 The diagram shows a flowchart of another DRB data transmission method provided in this embodiment of the present disclosure. The method includes:

[0404] S1001, the core network equipment decomposes the downlink service flow into multiple service data flows, maps the multiple service data flows to multiple QoS flows, and sends the correlation between QoS flows, as well as the mapping relationship between QoS flows and UE location and / or FoV, to the base station.

[0405] S1002, The base station maps QoS flows with associations to one or more data radio bearers (DRBs).

[0406] Multiple QoS flows correspond to one downlink service flow. A DRB or a group of DRBs can present service data for a location and / or FoV.

[0407] S1003. The base station sends data from a portion of multiple DRBs to the UE based on the UE's location and / or field of view (FoV).

[0408] In this step, the base station can determine the location and / or FoV of the UE that needs to receive data. Based on the UE's location and / or FoV, it selects a suitable portion of the DRB data, maps it to the corresponding PDSCH, and uses the PDSCH to send the aforementioned portion of the DRB data to the UE. For example, the base station can send a downlink scheduling instruction to the UE, which can directly instruct the UE to receive the data transmitted on the corresponding PDSCH.

[0409] In one possible implementation, the base station can receive the UE's location and / or FoV transmitted by the UE, or determine the UE's location and / or FoV using a prediction algorithm. The base station can send reporting indication information to the UE, which can be used to instruct the UE to report its location and / or FoV information. For details on the specific method by which the base station determines the UE's location and / or FoV, please refer to the relevant content in Embodiment 5.

[0410] In this step, the base station can send data from a portion of multiple DRBs to the UE via multicast or unicast, according to the UE's reception requirements.

[0411] In this implementation, in order for the UE to select the PDSCH to receive, the base station can also send configuration parameters via multicast or unicast. The configuration parameters may include at least one of the following:

[0412] QoS flow attribute parameters;

[0413] DRB attribute parameters;

[0414] Mapping relationship between QoS flow and DRB;

[0415] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV).

[0416] S1004. The UE receives data sent by the network device (base station) and uses the received data as part of the DRB data.

[0417] In this step, the UE does not need to select the PDSCH to receive. It can directly receive the data transmitted on the PDSCH indicated by the base station and directly use the received data as part of the data of the multiple DRBs mentioned above, and use this part of the DRB for screen display.

[0418] Corresponding to the DRB data transmission method described above, this disclosure also provides a DRB data transmission apparatus. See [link to previous document]. Figure 11 The diagram shown is a schematic representation of a DRB data transmission apparatus provided in an embodiment of this disclosure. This apparatus can be applied to a User Equipment (UE) and may include:

[0419] The receiving module 1110 is used to receive data from a portion of the DRBs in a plurality of data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a downlink service flow.

[0420] In one optional implementation, the receiving module 1110 is specifically used for:

[0421] Receive downlink reference signal;

[0422] Channel quality measurement based on downlink reference signal;

[0423] After the detected channel quality is greater than the channel quality threshold, part of the DRB data transmitted by the Physical Downlink Shared Channel (PDSCH) corresponding to the downlink reference signal is received.

[0424] In one optional implementation, the receiving module 1110 is specifically used for:

[0425] Receive the demodulation reference signal DMRS and receive part of the DRB data transmitted via the physical downlink shared channel PDSCH corresponding to DMRS.

[0426] In one optional implementation, the receiving module 1110 is specifically used for:

[0427] Determine the parameters of the scrambling downlink scheduling command;

[0428] The downlink scheduling command is received according to the determined parameters of the scrambled downlink scheduling command, and the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command is also received.

[0429] In an optional implementation, the receiving module 1110 is further configured to:

[0430] Report the UE's location and / or field of view (FoV) information to the network device.

[0431] In an optional implementation, the receiving module 1110 is further configured to:

[0432] Receive reporting instruction information sent by network devices. The reporting instruction information is used to instruct the UE to report location and / or field of view (FoV) information.

[0433] In an optional implementation, the receiving module 1110 is further configured to:

[0434] Receive at least one of the following configuration parameters:

[0435] QoS flow attribute parameters;

[0436] DRB attribute parameters;

[0437] Mapping relationship between QoS flow and DRB;

[0438] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0439] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0440] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0441] Multiple DMRS parameter configurations;

[0442] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0443] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0444] See Figure 12 The diagram shown is a schematic representation of another DRB data transmission apparatus provided in this disclosure. This apparatus can be applied to network devices and may include:

[0445] The mapping module 1210 is used to map related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); wherein multiple QoS flows correspond to one downlink service flow.

[0446] The transmitting module 1220 is used to transmit data from multiple DRBs based on different downlink transmission resources; or, according to the UE's receiving requirements, to transmit data from a portion of the multiple DRBs to the UE.

[0447] In one alternative implementation, the different downlink transmission resources include at least one of the following:

[0448] Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

[0449] In one optional implementation, the sending module 1220 is specifically used for:

[0450] Data from different DRBs is carried by multiple Physical Downlink Shared Channels (PDSCHs), and different PDSCHs are mapped to different downlink transmission resources.

[0451] In this context, at least some data from different DRBs are not allowed to be multiplexed into the same physical layer transport block (TB); one TB is carried by one PDSCH.

[0452] In one optional implementation, the sending module 1220 is specifically used for:

[0453] Downlink reference signals are transmitted on different beam directions or different transmit-receive points (TRPs), and data from multiple DRBs are transmitted on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to the physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources, and different PDSCHs are used to carry data from multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE.

[0454] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0455] Transmit downlink reference signals in at least one beam direction or at least one transmit-receive point (TRP); receive channel quality reports detected by the UE for the downlink reference signals; and, based on the channel quality reports, transmit a portion of the DRB data in the beam direction or TRP corresponding to the downlink reference signals whose detected channel quality is greater than the channel quality threshold.

[0456] In one optional implementation, the sending module 1220 is specifically used for:

[0457] Transmit the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transport resources, and the data of the DRB carried by the PDSCH;

[0458] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0459] On at least one downlink transport resource that matches the UE's reception requirements, the corresponding demodulation reference signal DMRS and a portion of the DRB data mapped to the downlink transport resource are transmitted.

[0460] In an optional implementation, for the case of transmitting data from multiple DRBs based on different downlink transmission resources, the transmitting module 1220 is further configured to:

[0461] Send different downlink scheduling commands with different scrambling parameters; different downlink scheduling commands are used to schedule the Physical Downlink Shared Channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

[0462] In one optional implementation, the sending module 1220 is specifically used for:

[0463] Based on the UE's position and / or field of view (FoV), send data from a portion of the multiple DRBs to the UE.

[0464] In one optional implementation, the device further includes a determining module for:

[0465] A prediction algorithm is used to determine the UE's position and / or field of view (FoV); or,

[0466] Receive the location and / or field of view (FoV) information reported by the UE.

[0467] In an optional implementation, before receiving the location and / or field of view (FoV) information reported by the UE, the determining module is further configured to:

[0468] Send a reporting instruction to the UE. The reporting instruction is used to instruct the UE to report the location and / or field of view (FoV) information.

[0469] In one optional implementation, the sending module 1220 is specifically used to: send data of multiple DRBs based on different downlink transmission resources by means of broadcast, multicast, or unicast.

[0470] or,

[0471] Based on the UE's reception requirements, data from a portion of multiple DRBs is sent to the UE, including via multicast or unicast.

[0472] In an optional implementation, the sending module 1220 is further configured to:

[0473] Send at least one of the following configuration parameters:

[0474] QoS flow attribute parameters;

[0475] DRB attribute parameters;

[0476] Mapping relationship between QoS flow and DRB;

[0477] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0478] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0479] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0480] Multiple DMRS parameter configurations;

[0481] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0482] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0483] In an optional implementation, for the case of sending data for multiple DRBs based on different downlink transmission resources, the sending module 1220 is further configured to: send configuration parameters via broadcast, multicast, or unicast; or,

[0484] For situations where data from multiple DRBs is sent to the UE based on the UE's reception requirements, the method also includes sending configuration parameters via multicast or unicast.

[0485] The configuration parameters are used by the UE to select the Physical Downlink Shared Channel (PDSCH) to receive.

[0486] Corresponding to the DRB data transmission method described above, this disclosure also provides a computer device. See also... Figure 13 The diagram shown is a schematic representation of a computer device provided in an embodiment of this disclosure. This computer device can be deployed on a user equipment (UE) and may include:

[0487] The memory 1310 is used to store computer programs; the transceiver 1320 is used to receive and send data under the control of the processor 1330. The processor 1330 and the memory 1310 can also be physically separated.

[0488] Among them, Figure 13 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1330) and memory (memory 1310). The bus architecture can also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1320 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 1330 is responsible for managing the bus architecture and general processing, and the memory 1310 can store data used by the processor 1330 during operation.

[0489] The processor 1330 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0490] Processor 1330 executes any of the methods provided in this disclosure embodiment according to the obtained executable instructions by calling a computer program stored in memory 1310, for example:

[0491] It receives data from a portion of the DRBs in multiple data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a single downlink service flow.

[0492] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0493] Receive downlink reference signal;

[0494] Channel quality measurement based on downlink reference signal;

[0495] After the detected channel quality is greater than the channel quality threshold, part of the DRB data transmitted by the Physical Downlink Shared Channel (PDSCH) corresponding to the downlink reference signal is received.

[0496] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0497] Receive the demodulation reference signal DMRS and receive part of the DRB data transmitted via the physical downlink shared channel PDSCH corresponding to DMRS.

[0498] In one optional implementation, receiving data from a portion of multiple data radio bearers (DRBs) includes:

[0499] Determine the parameters of the scrambling downlink scheduling command;

[0500] The downlink scheduling command is received according to the determined parameters of the scrambled downlink scheduling command, and the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command is also received.

[0501] In an alternative implementation, the processor 1330 is further configured to perform:

[0502] Report the UE's location and / or field of view (FoV) information to the network device.

[0503] In an alternative implementation, the processor 1330 is further configured to perform:

[0504] Receive reporting instruction information sent by network devices. The reporting instruction information is used to instruct the UE to report location and / or field of view (FoV) information.

[0505] In an alternative implementation, the processor 1330 is further configured to perform:

[0506] Receive at least one of the following configuration parameters:

[0507] QoS flow attribute parameters;

[0508] DRB attribute parameters;

[0509] Mapping relationship between QoS flow and DRB;

[0510] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0511] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0512] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0513] Multiple DMRS parameter configurations;

[0514] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0515] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0516] See Figure 14 The diagram shown is a schematic representation of another computer device provided in an embodiment of this disclosure. This computer device can be deployed on a network device and may include:

[0517] The memory 1410 is used to store computer programs; the transceiver 1420 is used to receive and send data under the control of the processor 1430. The processor 1430 and the memory 1410 can also be physically separated.

[0518] Among them, Figure 14In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1430) and memory (memory 1410). The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1420 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 1430 is responsible for managing the bus architecture and general processing, and the memory 1410 can store data used by the processor 1430 during operation.

[0519] The processor 1430 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0520] Processor 1430 executes any of the methods provided in this disclosure embodiment according to the obtained executable instructions by calling a computer program stored in memory 1410, for example:

[0521] Mapping related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow.

[0522] Data from multiple DRBs can be transmitted based on different downlink transmission resources; or, data from a portion of multiple DRBs can be transmitted to the UE according to the UE's reception requirements.

[0523] In one alternative implementation, the different downlink transmission resources include at least one of the following:

[0524] Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

[0525] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0526] Data from different DRBs is carried by multiple Physical Downlink Shared Channels (PDSCHs), and different PDSCHs are mapped to different downlink transmission resources.

[0527] In this context, at least some data from different DRBs are not allowed to be multiplexed into the same physical layer transport block (TB); one TB is carried by one PDSCH.

[0528] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0529] Downlink reference signals are transmitted on different beam directions or different transmit-receive points (TRPs), and data from multiple DRBs are transmitted on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to the physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources, and different PDSCHs are used to carry data from multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE.

[0530] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0531] Transmit downlink reference signals in at least one beam direction or at least one transmit-receive point (TRP); receive channel quality reports detected by the UE for the downlink reference signals; and, based on the channel quality reports, transmit a portion of the DRB data in the beam direction or TRP corresponding to the downlink reference signals whose detected channel quality is greater than the channel quality threshold.

[0532] In one optional implementation, data from multiple DRBs is transmitted based on different downlink transport resources, including:

[0533] Transmit the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transport resources, and the data of the DRB carried by the PDSCH;

[0534] Alternatively, based on the UE's reception requirements, send data from a portion of multiple DRBs to the UE, including:

[0535] On at least one downlink transport resource that matches the UE's reception requirements, the corresponding demodulation reference signal DMRS and a portion of the DRB data mapped to the downlink transport resource are transmitted.

[0536] In an alternative implementation, for the case where data for multiple DRBs is transmitted based on different downlink transport resources, the processor 1430 is further configured to perform:

[0537] Send different downlink scheduling commands with different scrambling parameters; different downlink scheduling commands are used to schedule the Physical Downlink Shared Channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

[0538] In one optional implementation, data from a subset of multiple DRBs is sent to the UE according to the UE's reception requirements, including:

[0539] Based on the UE's position and / or field of view (FoV), send data from a portion of the multiple DRBs to the UE.

[0540] In one alternative implementation, the processor 1430 is specifically configured to perform:

[0541] A prediction algorithm is used to determine the UE's position and / or field of view (FoV); or,

[0542] Receive the location and / or field of view (FoV) information reported by the UE.

[0543] In an optional implementation, before receiving the location and / or field of view (FoV) information reported by the UE, the processor 1430 is further configured to perform:

[0544] Send a reporting instruction to the UE. The reporting instruction is used to instruct the UE to report the location and / or field of view (FoV) information.

[0545] In one optional implementation, transmitting data for multiple DRBs based on different downlink transmission resources includes: transmitting data for multiple DRBs based on different downlink transmission resources via broadcast, multicast, or unicast.

[0546] or,

[0547] Based on the UE's reception requirements, data from a portion of multiple DRBs is sent to the UE, including via multicast or unicast.

[0548] In an alternative implementation, the processor 1430 is further configured to perform:

[0549] Send at least one of the following configuration parameters:

[0550] QoS flow attribute parameters;

[0551] DRB attribute parameters;

[0552] Mapping relationship between QoS flow and DRB;

[0553] The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV);

[0554] Downlink reference signal configuration information corresponding to different beam directions or different TRPs;

[0555] Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold.

[0556] Multiple DMRS parameter configurations;

[0557] Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV);

[0558] The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

[0559] In an optional implementation, for the case where data from multiple DRBs is transmitted based on different downlink transport resources, the processor 1430 is further configured to: transmit configuration parameters via broadcast, multicast, or unicast; or,

[0560] For situations where data from multiple DRBs is sent to the UE based on the UE's reception requirements, the method also includes sending configuration parameters via multicast or unicast.

[0561] The configuration parameters are used by the UE to select the Physical Downlink Shared Channel (PDSCH) to receive.

[0562] It should be noted that the division of units (or modules) in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0563] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0564] It should be noted that the apparatus or device provided in this disclosure can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0565] On the other hand, embodiments of this disclosure also provide a processor-readable storage medium storing a computer program for causing a computer to execute the DRB data transmission method provided in the above embodiments.

[0566] It should be noted that the processor-readable storage medium provided in this embodiment can implement all the method steps implemented in the above method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0567] Processor-readable storage media can be any available medium or data storage device that a computer can access, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0568] This disclosure also provides a computer program product that, when invoked by a computer, causes the computer to execute the steps of the DRB data transmission method described above.

[0569] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0570] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0571] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0572] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0573] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A DRB data transmission method, characterized in that, Applied to User Equipment (UE), including: It receives data from a portion of the DRBs in multiple data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a single downlink service flow.

2. The method according to claim 1, characterized in that, The receiving of data from a portion of the multiple data radio bearers (DRBs) includes: Receive downlink reference signal; Channel quality measurements are performed based on the downlink reference signal; After the detected channel quality is greater than the channel quality threshold, the data of the portion of the DRB transmitted by the Physical Downlink Shared Channel (PDSCH) corresponding to the downlink reference signal is received.

3. The method according to claim 1, characterized in that, The receiving of data from a portion of the multiple data radio bearers (DRBs) includes: Receive the demodulation reference signal DMRS and receive the data of the portion of the DRB transmitted via the physical downlink shared channel PDSCH corresponding to the DMRS.

4. The method according to claim 1, characterized in that, The receiving of data from a portion of the multiple data radio bearers (DRBs) includes: Determine the parameters of the scrambling downlink scheduling command; The downlink scheduling command is received according to the determined parameters of the scrambled downlink scheduling command, and the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command is received.

5. The method according to claim 1, characterized in that, Also includes: The location and / or field of view (FoV) information of the UE are reported to the network device.

6. The method according to claim 5, characterized in that, Also includes: The UE receives a reporting instruction message sent by the network device, the reporting instruction message being used to instruct the UE to report location and / or field of view (FoV) information.

7. The method according to claim 1, characterized in that, Also includes: Receive at least one of the following configuration parameters: QoS flow attribute parameters; DRB attribute parameters; Mapping relationship between QoS flow and DRB; The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV); Downlink reference signal configuration information corresponding to different beam directions or different TRPs; Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold; Multiple DMRS parameter configurations; Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV); The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

8. A DRB data transmission method, characterized in that, Applied to network devices, including: Mapping related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow. Data from multiple DRBs can be transmitted based on different downlink transmission resources; or, data from a portion of multiple DRBs can be transmitted to the UE according to the UE's reception requirements.

9. The method according to claim 8, characterized in that, The different downlink transmission resources include at least one of the following: Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

10. The method according to claim 8, characterized in that, The transmission of data from multiple DRBs based on different downlink transmission resources includes: Data from different DRBs is carried by multiple Physical Downlink Shared Channels (PDSCHs), and different PDSCHs are mapped to different downlink transmission resources. In this context, at least some data from different DRBs are not allowed to be multiplexed into the same physical layer transport block (TB); one TB is carried by one PDSCH.

11. The method according to claim 8, characterized in that, The transmission of data from multiple DRBs based on different downlink transmission resources includes: Downlink reference signals are transmitted on different beam directions or different transmit-receive points (TRPs), and data of the multiple DRBs are transmitted on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources, and different PDSCHs are used to carry the data of the multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE. Alternatively, the step of sending data from a subset of multiple DRBs to the UE according to the UE's reception requirements includes: A downlink reference signal is transmitted in at least one beam direction or at least one transmit-receive point (TRP); a channel quality report detected by the UE for the downlink reference signal is received; and based on the channel quality report, a portion of the DRB data is transmitted in the beam direction or TRP corresponding to the downlink reference signal whose detected channel quality is greater than the channel quality threshold.

12. The method according to claim 8, characterized in that, The transmission of data from multiple DRBs based on different downlink transmission resources includes: Transmit the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transport resources, and the data of the DRB carried by the PDSCH; Alternatively, the step of sending data from a subset of multiple DRBs to the UE according to the UE's reception requirements includes: On at least one downlink transport resource that matches the UE's reception requirements, a corresponding demodulation reference signal (DMRS) and data mapped to a portion of the DRB of the downlink transport resource are transmitted.

13. The method according to claim 8, characterized in that, For cases where data from multiple DRBs are transmitted based on different downlink transport resources, the method further includes: Send different downlink scheduling commands with different scrambling parameters; different downlink scheduling commands are used to schedule the Physical Downlink Shared Channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

14. The method according to claim 8, characterized in that, The step of sending data from a portion of multiple DRBs to the UE according to the UE's reception requirements includes: Based on the UE's position and / or field of view (FoV), data from a portion of the multiple DRBs is sent to the UE.

15. The method according to claim 14, characterized in that, The UE's position and / or field of view (FoV) are determined as follows: A prediction algorithm is used to determine the UE's position and / or field of view (FoV); or, Receive the position and / or field of view (FoV) information reported by the UE.

16. The method according to claim 15, characterized in that, Before receiving the position and / or field of view (FoV) information reported by the UE, the method further includes: Send a reporting instruction message to the UE, the reporting instruction message being used to instruct the UE to report location and / or field of view (FoV) information.

17. The method according to claim 8, characterized in that, The transmission of multiple DRB data based on different downlink transmission resources includes: transmitting multiple DRB data based on different downlink transmission resources through broadcast, multicast, or unicast methods. or, Based on the UE's reception requirements, data from a portion of multiple DRBs is sent to the UE, including via multicast or unicast.

18. The method according to claim 8, characterized in that, Also includes: Send at least one of the following configuration parameters: QoS flow attribute parameters; DRB attribute parameters; Mapping relationship between QoS flow and DRB; The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV); Downlink reference signal configuration information corresponding to different beam directions or different TRPs; Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold; Multiple DMRS parameter configurations; Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV); The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

19. The method according to claim 8, characterized in that, For scenarios where data from multiple DRBs is transmitted based on different downlink transmission resources, the method further includes: transmitting configuration parameters via broadcast, multicast, or unicast; or, For situations where data from multiple DRBs is sent to the UE based on the UE's reception requirements, the method also includes sending configuration parameters via multicast or unicast. The configuration parameters are used by the UE to select the Physical Downlink Shared Channel (PDSCH) to receive.

20. A computer device, characterized in that, Deployed in user equipment (UE), including memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: It receives data from a portion of the DRBs in multiple data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a single downlink service flow.

21. The device according to claim 20, characterized in that, The receiving of data from a portion of the multiple data radio bearers (DRBs) includes: Receive downlink reference signal; Channel quality measurements are performed based on the downlink reference signal; After the detected channel quality is greater than the channel quality threshold, the data of the portion of the DRB transmitted by the Physical Downlink Shared Channel (PDSCH) corresponding to the downlink reference signal is received.

22. The device according to claim 20, characterized in that, The receiving of data from a portion of the multiple data radio bearers (DRBs) includes: Receive the demodulation reference signal DMRS and receive the data of the portion of the DRB transmitted via the physical downlink shared channel PDSCH corresponding to the DMRS.

23. The device according to claim 20, characterized in that, The receiving of data from a portion of the multiple data radio bearers (DRBs) includes: Determine the parameters of the scrambling downlink scheduling command; The downlink scheduling command is received according to the determined parameters of the scrambled downlink scheduling command, and the data transmitted on the Physical Downlink Shared Channel (PDSCH) scheduled by the downlink scheduling command is received.

24. The device according to claim 20, characterized in that, The processor is also used to perform: The location and / or field of view (FoV) information of the UE are reported to the network device.

25. The device according to claim 24, characterized in that, The processor is also used to perform: The UE receives a reporting instruction message sent by the network device, the reporting instruction message being used to instruct the UE to report location and / or field of view (FoV) information.

26. The device according to claim 20, characterized in that, The processor is also used to perform: Receive at least one of the following configuration parameters: QoS flow attribute parameters; DRB attribute parameters; Mapping relationship between QoS flow and DRB; The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV); Downlink reference signal configuration information corresponding to different beam directions or different TRPs; Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold; Multiple DMRS parameter configurations; Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV); The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

27. A computer device, characterized in that, Deployed in network devices, including storage, transceivers, and processors: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor. Processor, configured to read the computer program in the memory and perform the following operations: Mapping related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow. Data from multiple DRBs can be transmitted based on different downlink transmission resources; or, data from a portion of multiple DRBs can be transmitted to the UE according to the UE's reception requirements.

28. The device according to claim 27, characterized in that, The different downlink transmission resources include at least one of the following: Different time-domain resources, different frequency-domain resources, and different spatial-domain resources.

29. The device according to claim 27, characterized in that, The transmission of data from multiple DRBs based on different downlink transmission resources includes: Data from different DRBs is carried by multiple Physical Downlink Shared Channels (PDSCHs), and different PDSCHs are mapped to different downlink transmission resources. In this context, at least some data from different DRBs are not allowed to be multiplexed into the same physical layer transport block (TB); one TB is carried by one PDSCH.

30. The device according to claim 27, characterized in that, The transmission of data from multiple DRBs based on different downlink transmission resources includes: Downlink reference signals are transmitted on different beam directions or different transmit-receive points (TRPs), and data of the multiple DRBs are transmitted on the downlink transmission resources corresponding to the different downlink reference signals. The downlink reference signals correspond to physical downlink shared channels (PDSCHs) mapped to different downlink transmission resources, and different PDSCHs are used to carry the data of the multiple DRBs. The downlink reference signals are used for channel quality measurement, and the results of the channel quality measurement are used to select the PDSCH to be received by the UE. Alternatively, the step of sending data from a portion of multiple DRBs to the UE according to the UE's reception requirements includes: A downlink reference signal is transmitted in at least one beam direction or at least one transmit-receive point (TRP); a channel quality report detected by the UE for the downlink reference signal is received; and based on the channel quality report, a portion of the DRB data is transmitted in the beam direction or TRP corresponding to the downlink reference signal whose detected channel quality is greater than the channel quality threshold.

31. The device according to claim 27, characterized in that, The transmission of data from multiple DRBs based on different downlink transmission resources includes: Transmit the demodulation reference signal DMRS corresponding to the PDSCH mapped to different downlink transport resources, and the data of the DRB carried by the PDSCH; Alternatively, the step of sending data from a subset of multiple DRBs to the UE according to the UE's reception requirements includes: On at least one downlink transport resource that matches the UE's reception requirements, a corresponding demodulation reference signal (DMRS) and data mapped to a portion of the DRB of the downlink transport resource are transmitted.

32. The device according to claim 27, characterized in that, For cases where data from multiple DRBs is transmitted based on different downlink transport resources, the processor is also used to perform: Send different downlink scheduling commands with different scrambling parameters; different downlink scheduling commands are used to schedule the Physical Downlink Shared Channel (PDSCH) carrying different DRB data transmitted on different downlink transmission resources.

33. The device according to claim 27, characterized in that, The step of sending data from a portion of multiple DRBs to the UE according to the UE's reception requirements includes: Based on the UE's position and / or field of view (FoV), data from a portion of the multiple DRBs is sent to the UE.

34. The device according to claim 33, characterized in that, The processor is specifically used to execute: A prediction algorithm is used to determine the UE's position and / or field of view (FoV); or, Receive the position and / or field of view (FoV) information reported by the UE.

35. The device according to claim 34, characterized in that, Before receiving the position and / or field of view (FoV) information reported by the UE, the processor is also configured to perform: Send a reporting instruction message to the UE, the reporting instruction message being used to instruct the UE to report location and / or field of view (FoV) information.

36. The device according to claim 27, characterized in that, The transmission of multiple DRB data based on different downlink transmission resources includes: transmitting multiple DRB data based on different downlink transmission resources through broadcast, multicast, or unicast methods. or, Based on the UE's reception requirements, data from a portion of multiple DRBs is sent to the UE, including via multicast or unicast.

37. The device according to claim 27, characterized in that, The processor is also used to perform: Send at least one of the following configuration parameters: QoS flow attribute parameters; DRB attribute parameters; Mapping relationship between QoS flow and DRB; The correlation between DRB or logical channel or QoS flow and UE location and / or field of view (FoV); Downlink reference signal configuration information corresponding to different beam directions or different TRPs; Channel quality threshold; the channel quality threshold is used by the UE to select downlink transmission resources whose corresponding channel quality measurement results are higher than the channel quality threshold; Multiple DMRS parameter configurations; Mapping relationship between different DMRS parameter configurations and UE position and / or field of view (FoV); The scrambling code parameters of the scrambling scheduling commands corresponding to different DRBs, and the mapping relationship between the scrambling code parameters of different scheduling commands and the UE's location and / or FoV.

38. The device according to claim 27, characterized in that, For scenarios where data from multiple DRBs is transmitted based on different downlink transport resources, the processor is also configured to: transmit configuration parameters via broadcast, multicast, or unicast; or, For situations where data from multiple DRBs is sent to the UE based on the UE's reception requirements, the method also includes sending configuration parameters via multicast or unicast. The configuration parameters are used by the UE to select the Physical Downlink Shared Channel (PDSCH) to receive.

39. A DRB data transmission device, characterized in that, For user equipment (UE), including: The receiving module is used to receive data from a portion of the DRBs in multiple data radio bearers (DRBs); wherein one or more DRBs correspond to a set of associated Quality of Service (QoS) flows, and multiple QoS flows correspond to a downlink service flow.

40. A DRB data transmission device, characterized in that, For use in network devices, including: The mapping module is used to map related Quality of Service (QoS) flows to one or more Data Radio Bearers (DRBs); where multiple QoS flows correspond to one downlink service flow. The transmitting module is used to transmit data from multiple DRBs based on different downlink transmission resources; or, according to the UE's receiving requirements, to transmit data from a portion of multiple DRBs to the UE.

41. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a program for causing the processor to perform the method according to any one of claims 1 to 7, or the method according to any one of claims 8 to 19.

Images