Device, method and equipment for ultra-low delay communication, and medium

Abstract

The invention discloses a device, a method, equipment and a medium for ultra-low delay communication. An exemplary terminal device may include at least one processor and at least one memory. The at least one memory may store instructions that, when executed by the at least one processor, may cause the terminal device to: receive a configuration of a particular DRB from an access network device, the configuration of the specific DRB comprises at least one of the following items: identification of the specific DRB, configuration of an SDAP layer, configuration of a PDCP layer used for the specific DRB, configuration of an RLC layer used for the specific DRB, or configuration of an MAC layer used for the specific DRB; respectively creating an SDAP layer entity, a PDCP layer entity, an RLC layer entity or an MAC layer entity according to the received configuration of the SDAP layer, the received configuration of the PDCP layer, the received configuration of the RLC layer or the received configuration of the MAC layer; and receiving scheduling information from the access network device, wherein the scheduling information indicates the identification of the specific DRB.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to an apparatus, a method, a device, and a computer readable medium for ultra-low latency communication. BACKGROUND

[0002] Ultra-reliable and low latency communication (URLLC) is one of the main features of the fifth generation of mobile communication system (5G), for example, the latency requirement in the user plane is less than 1 millisecond (ms). The beyond 5G (B5G) communication system, for example, the sixth generation of mobile communication system (6G), takes hyper reliable and low-latency communication (HRLLC) as one of the main features, and has a further more stringent requirement for the latency in the user plane, such as the requirement of latency less than 0.1 ms. The latency of data transmission mainly includes: transmission time interval (TTI), propagation time from the sending device to the receiving device, time for the physical layer of the sending device and the receiving device to encode and decode and process the data, and time for the higher protocol layer (higher than the physical layer) of the sending device and the receiving device to process the data. SUMMARY

[0003] In a first aspect, a terminal device is provided, which can include at least one processor and at least one memory. The at least one memory can store instructions that, when executed by the at least one processor, can cause the terminal device to: receive, from an access network device, a configuration of a specific data radio bearer, the configuration of the specific data radio bearer including at least one of: an identification of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; create a service data adaptation protocol layer entity, a packet data convergence protocol layer entity, a radio link control layer entity, or a medium access control layer entity, respectively, according to the received configuration of the service data adaptation protocol layer, the packet data convergence protocol layer, the radio link control layer, or the medium access control layer; and receive, from the access network device, scheduling information indicating the identification of the specific data radio bearer.

[0004] In a second aspect, an access network device is provided, which can include at least one processor and at least one memory. The at least one memory can store instructions that, when executed by the at least one processor, can cause the access network device to: determine a data quality of service flow to be mapped to a specific data radio bearer; send, to a terminal device, a configuration of the specific data radio bearer, the configuration of the specific data radio bearer including at least one of: an identification of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; and send, to the terminal device, scheduling information indicating the identification of the specific data radio bearer.

[0005] In a third aspect, a core network device is provided, which can include at least one processor and at least one memory. The at least one memory can store instructions that, when executed by the at least one processor, can cause the core network device to: send, to an access network device, a specific delay indication about a data quality of service flow according to a latency quality of service requirement of the data quality of service flow, causing the access network device to determine that the data quality of service flow is to be mapped to a specific data radio bearer.

[0006] In a fourth aspect, a method performed by a terminal device can include receiving, from an access network device, a configuration of a specific data radio bearer, the configuration of the specific data radio bearer including at least one of an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; creating a service data adaptation protocol layer entity, a packet data convergence protocol layer entity, a radio link control layer entity, or a medium access control layer entity, respectively, according to the received configuration of the service data adaptation protocol layer, the configuration of the packet data convergence protocol layer, the configuration of the radio link control layer, or the configuration of the medium access control layer; and receiving, from the access network device, scheduling information indicating the identity of the specific data radio bearer.

[0007] In a fifth aspect, a method performed by an access network device can include determining a data quality of service flow to be mapped to a specific data radio bearer; sending, to a terminal device, a configuration of the specific data radio bearer, the configuration of the specific data radio bearer including at least one of an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; and sending, to the terminal device, scheduling information indicating the identity of the specific data radio bearer.

[0008] In a sixth aspect, a method performed by a core network device can include sending, to an access network device, a specific delay indication about a data quality of service flow according to a latency quality of service requirement of the data quality of service flow, causing the access network device to determine that the data quality of service flow is to be mapped to a specific data radio bearer.

[0009] In a seventh aspect, a device as a terminal device can include: means for receiving, from an access network device, a configuration of a specific data radio bearer, the configuration of the specific data radio bearer including at least one of: an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; means for creating, according to the received configuration of the service data adaptation protocol layer, the packet data convergence protocol layer, the radio link control layer, or the medium access control layer, a service data adaptation protocol layer entity, a packet data convergence protocol layer entity, a radio link control layer entity, or a medium access control layer entity, respectively; and means for receiving, from the access network device, scheduling information, the scheduling information indicating the identity of the specific data radio bearer.

[0010] In an eighth aspect, a device as an access network device can include: means for determining a data quality of service flow to be mapped to a specific data radio bearer; means for sending, to a terminal device, a configuration of the specific data radio bearer, the configuration of the specific data radio bearer including at least one of: an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; and means for sending, to the terminal device, scheduling information, the scheduling information indicating the identity of the specific data radio bearer.

[0011] In a ninth aspect, a device as a core network device can include: means for sending, to an access network device, a specific delay indication about a data quality of service flow according to a latency quality of service requirement of the data quality of service flow, causing the access network device to determine that the data quality of service flow is to be mapped to a specific data radio bearer.

[0012] In a tenth aspect, a computer-readable storage medium is provided, which includes program instructions that, when executed by a terminal device, can cause the terminal device to: receive, from an access network device, a configuration of a specific data radio bearer, the configuration of the specific data radio bearer including at least one of: an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; create a service data adaptation protocol layer entity, a packet data convergence protocol layer entity, a radio link control layer entity, or a medium access control layer entity, respectively, according to the received configuration of the service data adaptation protocol layer, the configuration of the packet data convergence protocol layer, the configuration of the radio link control layer, or the configuration of the medium access control layer; and receive, from the access network device, scheduling information, the scheduling information indicating the identity of the specific data radio bearer.

[0013] In an eleventh aspect, a computer-readable storage medium is provided, which includes program instructions that, when executed by an access network device, can cause the access network device to: determine a data quality of service flow to be mapped to a specific data radio bearer; send, to a terminal device, a configuration of the specific data radio bearer, the configuration of the specific data radio bearer including at least one of: an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; and send, to the terminal device, scheduling information, the scheduling information indicating the identity of the specific data radio bearer.

[0014] In a twelfth aspect, a computer-readable storage medium is provided, which includes program instructions that, when executed by a core network device, can cause the core network device to: send, to an access network device, a specific delay indication about a data quality of service flow according to a latency quality of service requirement of the data quality of service flow, to cause the access network device to determine that the data quality of service flow is to be mapped to a specific data radio bearer. BRIEF DESCRIPTION OF DRAWINGS

[0015] FIG. 1 shows an example interaction timing diagram for implementing ultra-low latency communication according to an example embodiment of the present disclosure.

[0016] Figure 2 A flow chart of an example method 200 for ultra-low latency communication according to an example embodiment of the present disclosure is shown.

[0017] Figure 3A flowchart illustrating an exemplary method 300 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0018] Figure 4 A flowchart illustrating an exemplary method 400 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0019] Figure 5 An example block diagram of an example apparatus 500 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0020] Figure 6 An example block diagram of an example apparatus 600 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0021] Figure 7 An example block diagram of an example apparatus 700 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0022] Figure 8 An example block diagram of an example device 800 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0023] Figure 9 An example block diagram of an example device 900 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0024] Figure 10 An example block diagram of an example device 1000 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown.

[0025] The same or substantially the same elements, operations, and steps shown in the various figures may be indicated by the same reference numerals. For clarity, not every element, operation, or step is shown in every figure. Detailed Implementation

[0026] This disclosure provides an exemplary embodiment of a scheme capable of achieving ultra-low latency communication to meet the ultra-low latency requirements of B5G, including 6G, communication systems for user plane data transmission. According to an exemplary embodiment of this disclosure, the time for the protocol layers of the transmitting and receiving devices to process data can be significantly reduced, thereby reducing data transmission latency. In the transmitting and receiving devices, Layer 1 (L1) of the user plane protocol stack is the physical layer, and Layer 2 (L2) above it comprises various protocol layers, from bottom to top including the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, the Packet Data Convergence Protocol (PDCP) layer, and the Service Data Adaptation Protocol (SDAP) layer. According to an exemplary embodiment of this disclosure, the processing time of a specific data radio bearer (DRB) in the protocol layers can be shortened to achieve ultra-low latency communication.

[0027] Figure 1 illustrates an exemplary interaction timing diagram for implementing ultra-low latency communication according to an exemplary embodiment of the present disclosure. As shown in Figure 1, terminal device 110 can represent any terminal device and / or user equipment (UE) in a wireless communication network, access network device 150 can represent a network device serving terminal device 110 in a radio access network (RAN), such as a base station (BS), such as a RAN node of a next-generation node B (gNB), and core network 180 can represent a network function or device associated with access network device 150 in the core network (CN), such as an access and mobility management function (AMF) or a session management function (SMF). In some embodiments, the functions of core network 180 can be implemented by the core network device.

[0028] First, terminal device 110 can perform operation 182 through access network device 150 and core network 180 to establish a protocol data unit (PDU) session between terminal device 110 and core network 180. Through the established PDU session, one or more quality of service (QoS) flows can be transmitted. Different data QoS flows can have different QoS requirements, including latency requirements. For data QoS flows with stricter latency requirements, access network device 150 can perform operation 152 to determine which QoS flow will be mapped to a specific DRB to perform specific operations described below to reduce protocol layer processing latency.

[0029] In some embodiments, the parameters of the data QoS stream received by the access network device 150 may include a packet delay budget (PDB) for the corresponding data QoS stream. The PDB represents the upper limit requirement for the time delay of data packets in the corresponding data QoS stream (i.e., the actual transmission delay should not exceed the size of the PDB). The access network device 150 may compare the PDB of the data QoS stream with a threshold. If the PDB is lower than or not higher than the threshold, the access network device 150 may perform operation 152 to determine that the corresponding data QoS stream will be mapped to a specific DRB. In some embodiments, the threshold may be included in the parameters of the data QoS stream and sent to the access network device 150. Alternatively, in some embodiments, the threshold may be pre-configured in the access network device 150.

[0030] Alternatively or additionally, in some embodiments, the core network 180 may, based on the latency quality of service requirements of the data QoS stream, send a specific latency indication 184 to the access network device 150 for a data QoS stream that requires ultra-low latency or strict latency quality of service. The specific latency indication 184 may indicate to the access network device 150 that the data QoS stream has ultra-low latency quality of service requirements, thereby allowing the access network device 150 to perform operation 152 to determine that the data QoS stream will be mapped to a specific DRB.

[0031] Then, the access network device 150 can send a configuration 154 for a specific DRB to the terminal device 110. In some embodiments, the configuration 154 for a specific DRB can be sent via a radio resource control (RRC) message, for example, via an RRCReconfiguration message for RRC reconfiguration of the terminal device.

[0032] In some embodiments, the configuration 154 of a particular DRB may include at least one of the following: the identifier of the particular DRB, the configuration of the SDAP layer, the configuration of the PDCP layer for the particular DRB, the configuration of the RLC layer for the particular DRB, or the configuration of the MAC layer for the particular DRB.

[0033] The configuration of each of the above protocol layers can include the operating parameters of the corresponding protocol layer. Thus, after receiving the configuration 154 of a specific DRB, the terminal device 110 can perform operation 112 to create an SDAP layer entity, PDCP layer entity, RLC layer entity, or MAC layer entity according to the received SDAP layer configuration, PDCP layer configuration, RLC layer configuration, or MAC layer configuration. The above protocol layer entities can also be referred to as SDAP entity, PDCP entity, RLC entity, or MAC entity, respectively.

[0034] On the network side, after determining the data QoS flow to be mapped to a specific DRB, the access network device 150 can perform operation 156 to determine scheduling information 158 for data transmission related to that specific DRB. The determination of the scheduling information 158 can, for example, be performed by the MAC layer entity of the access network device 150. For instance, the RRC layer of the access network device 150 can transmit data packet information for that specific DRB to the MAC layer entity via inter-layer primitives. This data packet information may include, for example, packet size, packet period, and required packet error rate (PER). The MAC layer entity can determine the scheduling information 158 for data transmission related to that specific DRB based on the data packet information of that specific DRB.

[0035] In some embodiments, the determined scheduling information 158 may include time / frequency resources allocated for data transmission, and may also include the transmission format used for the data transmission, such as modulation and coding scheme (MCS), number of data streams / layers, reference signal pattern, etc. Furthermore, the scheduling information 158 may include an identifier for the specific DRB. The scheduling information 158 may be scheduling information for the transmission of one or more periodic data packets in the downlink (DL) or uplink (UL). The access network device 150 may send the scheduling information 158 to the terminal device 110 via RRC messages and / or physical layer control information, such as downlink control information (DCI) carried by the physical downlink control channel (PDCCH).

[0036] If the terminal device 110 already knows the DRB identifier corresponding to a specific DRB before receiving the scheduling information 158, then based on the identifier of the specific DRB included in the scheduling information 158, the terminal device 110 can determine that the DRB involved in the scheduling information 158 is the specific DRB. For example, if the configuration 154 of the specific DRB has already indicated that the DRB involved is the specific DRB, and if the DRB identifier included in the scheduling information 158 is consistent with the DRB identifier in the configuration 154 of the specific DRB, then the terminal device 110 can determine that the DRB involved in the scheduling information 158 is the specific DRB. The identifier of the specific DRB can be, for example, an identifier (ID), an index, or other equivalent that can serve an identifying function. Alternatively or additionally, the scheduling information 158 may also explicitly indicate that the DRB involved is the specific DRB.

[0037] For data related to a specific DRB in the uplink or downlink involved in the scheduling information 158, the terminal device 110 and the access network device 150 can perform operation 114 to process data related to that specific DRB. In some embodiments, when performing operation 114, the terminal device 110 and the access network device 150 have already established an RRC connection.

[0038] Figure 1B An exemplary flowchart illustrates processing performed by a transmitting device regarding a specific DRB according to an exemplary embodiment of this disclosure. In the case where the specific DRB is used for the uplink, the following processes are performed: Figure 1BThe transmitting device in the exemplary operation shown is terminal device 110, and the receiving device, i.e., access network device 150, performs the corresponding reverse operation. When a specific DRB is used for the downlink, it executes... Figure 1B The transmitting device in the exemplary operation shown is the access network device 150, and the receiving device, i.e., the terminal device 110, performs the corresponding reverse operation. Regarding... Figure 1B The description uses terminal device 110 as the transmitting device, i.e., a specific DRB used for the uplink, as an example.

[0039] Based on the scheduling information 158, such as the identifier of a specific DRB contained therein, the terminal device 110 can determine to perform a transparent operation on the data. The transparent operation may include at least one of operations 124, 130, 138, or 144 described below. Furthermore, based on the identifier of the specific DRB, the terminal device 110 can also determine which PDCP layer entity and which RLC layer entity will perform data processing associated with that specific DRB.

[0040] For the data QoS flow 120 that is determined to be mapped to a specific DRB, the SDAP layer entity 122 performs operation 124 according to the identifier of the specific DRB indicated by the scheduling information 158, maps the data QoS flow to the specific DRB 126, and passes the specific DRB 126 to the PDCP layer entity 128 corresponding to the DRB 126.

[0041] Based on scheduling information 158, such as the time / frequency resources, MCS, number of data streams / layers, reference signal patterns, etc. contained therein, the physical layer of terminal device 110 can determine the TB size (or TB size) for transmitting data according to a predefined transport block (TB) size determination method, and indicate the calculated TB size to PDCP layer entity 128 through, for example, inter-layer primitives.

[0042] For a specific DRB 126, PDCP layer entity 128 first performs operation 130, performing the processing specified by the PDCP configuration on the specific DRB 126. For example, header compression can be performed on the data of the specific DRB 126 to reduce signaling load, such as robust header compression (ROHC), and then encryption processing is performed to enhance security.

[0043] After performing the corresponding processing according to the PDCP configuration, if the PDCP protocol data unit is smaller than the TB size, the PDCP layer entity 128 can perform operation 132 to fill the PDU to the TB size, and pass the filled TB-sized PDCPPDU 134 to the corresponding RLC layer entity 136.

[0044] Figure 1C An exemplary flowchart illustrating PDU population performed by a PDCP layer entity according to an exemplary embodiment of this disclosure is shown. See also Figure 1C The data input to the PDCP layer entity 128 from a specific DRB 126 is used as a PDCP service data unit (SDU) 129. The PDCP layer entity 128 can perform operation 130 to perform processes such as ROHC and encryption on the PDCPSDU 129 according to the PDCP configuration. If the encrypted PDCP PDU is insufficient to fill the TB, the PDCP layer entity 128 can perform operation 132 to add padding bits to align with the calculated TB size, and then pass the TB-sized PDCP PDU 134 to the corresponding RLC layer entity 136.

[0045] See back Figure 1B RLC layer entity 136 performs a transparent processing operation 138 on the PDCP PDU 134, passing the PDCP PDU 134, which is also the RLC SDU, as the RLC PDU 140 to the MAC layer entity 142. The transparent processing performed by RLC layer entity 136 can be referred to as the implementation of a transparent mode (TM) for a specific DRB. For example, RLC layer entity 136 does not add a header or sub-header to the RLC SDU, and the RLC SDU and RLC PDU 140 are essentially the same.

[0046] MAC layer entity 142 can perform transparent processing operation 144 on RLC PDU 140, directly transmitting RLC PDU 140 as a MAC PDU, or TB 146, to the physical channel for physical layer signal transmission. In the transparent processing performed by MAC layer entity 142, MAC layer entity 142 does not add headers or sub-headers to RLC PDU 140, and logical channel multiplexing is not performed in the MAC layer, thus different logical channel priority processing operations are not involved. In some embodiments, hybrid automatic repeat request (HARQ) operations can be implemented in the transparent processing operation 144 performed by MAC layer entity 142 to enhance reliability. For example, considering the requirement of ultra-low latency, blind retransmission can be implemented on the same or different time resources but on different frequency resources. That is, retransmission is implemented without feedback based on acknowledgment (ACK) or negative acknowledgment (NACK). The receiving device can perform HARQ combining on these multiple transmissions to achieve frequency diversity gain and coding gain, thereby enhancing the reliability of data transmission.

[0047] In the example above, which uses a specific DRB for the uplink, Figure 1B and Figure 1C The exemplary operation is described herein, and those skilled in the art will recognize that, when a particular DRB is used for the downlink, access network device 150 can perform the same transmission operation for the data to be transmitted. The difference from uplink transmission is that, since access network device 150 itself acts as the specific DRB configurer and data transmission scheduler, access network device 150 knows relevant information about the specific DRB and the scheduling of data, and therefore does not need to receive and perform processing regarding the specific DRB according to instructions such as scheduling information 158.

[0048] When a specific DRB is used for the downlink, terminal device 110 can determine, based on the identifier of the specific DRB indicated by scheduling information 158, that the received data has undergone transparent operations at the MAC and RLC layers of access network device 150. In other words, based on the identifier of the specific DRB contained in scheduling information 158, terminal device 110 can know that access network device 150 has performed operations on the data similar to... Figure 1B and Figure 1C The described transparent operation. According to the combination... Figure 1BThe described operation of calculating the TB size allows the physical layer of terminal device 110 to determine the TB size based on scheduling information 158. Furthermore, according to the correspondence between DRB identifiers and PDCP layer entities, terminal device 110 can determine the corresponding PDCP layer entity based on the identifier of the specific DRB indicated by scheduling information 158. Thus, after decoding the received data at the physical layer and obtaining the TB of the transmitted data, terminal device 110 can directly pass the TB to the PDCP layer entity. The PDCP layer entity can then perform subsequent operations such as removing padding bits. Those skilled in the art will recognize that, when a specific DRB is used for the uplink, access network device 150 can perform the same operation on the received data.

[0049] The transparent operation scheme of the specific DRB according to the exemplary embodiments of this disclosure is applicable to scenarios with ultra-low latency / ultra-low PDB service quality requirements, in which the retransmission mechanisms of the RLC and MAC layers are severely limited or cannot function properly. The transparent operation of the specific DRB scheme according to the exemplary embodiments of this disclosure at the RLC and / or MAC layers helps reduce the processing time of the radio protocol layer on both the transmitting and receiving devices. This is extremely important for achieving extremely low latency in 6G and later communication systems, and the specific DRB of the exemplary embodiments of this disclosure can therefore be called an extreme DRB. Furthermore, due to the simplified data processing, the specific DRB scheme provided by the exemplary embodiments of this disclosure can be applied to devices with very low complexity.

[0050] Figure 2 A flowchart illustrating an exemplary method 200 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. The exemplary method 200 can be performed by any terminal device such as the terminal device 110 described above according to an exemplary embodiment of the present disclosure.

[0051] See Figure 2 The exemplary method 200 may include operation 210, receiving configuration of a specific DRB from an access network device, the configuration of the specific DRB including at least one of the following: an identifier of the specific DRB, a configuration of the SDAP layer, a configuration of the PDCP layer for the specific DRB, a configuration of the RLC layer for the specific DRB, or a configuration of the MAC layer for the specific DRB; operation 220, creating an SDAP layer entity, a PDCP layer entity, an RLC layer entity, or a MAC layer entity respectively based on the received configuration of the SDAP layer, the PDCP layer, the RLC layer, or the MAC layer; and operation 230, receiving scheduling information from the access network device, the scheduling information indicating the identifier of the specific DRB.

[0052] In some embodiments, when the specific DRB is used for the downlink, the exemplary method 200 may include: determining, based on the identifier of the specific DRB indicated by the scheduling information, that the received data has undergone transparent operation at the RLC layer and MAC layer of the access network device; decoding the data to obtain the TB that transmitted the data; determining the corresponding PDCP layer entity based on the identifier of the specific DRB indicated by the scheduling information; and passing the TB to the PDCP layer entity.

[0053] In some embodiments, when the specific DRB is used for the uplink, the exemplary method 200 may include: determining, based on the scheduling information, to perform a transparent operation on the data, the transparent operation including any one of the following: mapping the data QoS flow to the specific DRB by an SDAP layer entity based on the identifier of the specific DRB indicated by the scheduling information, and passing the specific DRB to the corresponding PDCP layer entity; performing the processing specified by the PDCP configuration on the specific DRB by the PDCP layer entity, and if the processed PDU is less than the TB size, padding the PDU to the TB size, and passing the padded PDCP layer PDU to the corresponding RLC layer entity; passing the PDCP layer PDU as the RLC layer PDU to the MAC layer entity by the RLC layer entity; or passing the RLC layer PDU as the TB to the physical channel for transmission by the MAC layer entity.

[0054] Figure 3 A flowchart illustrating an exemplary method 300 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. The exemplary method 300 can be performed by any network device such as the access network device 150 described above according to an exemplary embodiment of the present disclosure.

[0055] See Figure 3 The exemplary method 300 may include operation 310, determining a data QoS flow to be mapped to a specific DRB; operation 320, sending the configuration of the specific DRB to a terminal device, the configuration of the specific DRB including at least one of the following: an identifier of the specific DRB, a configuration of the SDAP layer, a configuration of the PDCP layer for the specific DRB, a configuration of the RLC layer for the specific DRB, or a configuration of the MAC layer for the specific DRB; and operation 330, sending scheduling information to the terminal device, the scheduling information indicating the identifier of the specific DRB.

[0056] In some embodiments, exemplary method 300 may include: determining that the data QoS stream will be mapped to the specific DRB if the PDB of the data QoS stream is below a threshold.

[0057] In some embodiments, exemplary method 300 may include: upon receiving a specific delay indication from the core network regarding the data QoS flow, determining that the data QoS flow will be mapped to the specific DRB.

[0058] Figure 4 A flowchart illustrating an exemplary method 400 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. The exemplary method 400 can be performed by any network device that implements the functions of the core network 180 described above according to an exemplary embodiment of the present disclosure.

[0059] See Figure 4 The exemplary method 400 may include operation 410, which sends a specific delay indication about the data QoS stream to an access network device based on the latency quality of service requirements of the data QoS stream, so that the access network device determines that the data QoS stream will be mapped to a specific DRB.

[0060] Figure 5 An example block diagram of an example apparatus 500 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. This example apparatus 500 may be, for example, at least a portion of any terminal device such as the terminal device 110 described above according to an exemplary embodiment of the present disclosure.

[0061] like Figure 5 As shown, the example device 500 may include at least one processor 510 and at least one memory 520, wherein the at least one memory 520 may include instructions 530, and when the instructions 530 are executed by the at least one processor 510, the example device 500 performs at least the example method 200 described above.

[0062] In some embodiments, at least one processor 510 in the example device 500 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit, or may be part of at least one hardware processor and a dedicated processor such as one developed based on a field-programmable gate array. Additionally, the at least one processor 510 may also include components not in... Figure 5 At least one other circuit or element shown in the diagram.

[0063] In some embodiments, at least one memory 520 in the example device 500 may include various forms of storage media, such as volatile and / or non-volatile memory. Volatile memory may include, but is not limited to, random access memory, cache memory, etc. Non-volatile memory may include, but is not limited to, read-only memory, hard disk, flash memory, etc. The term "non-volatile" in this disclosure, as opposed to the limitation of data storage persistence (e.g., RAM versus ROM), is a limitation concerning the medium itself (i.e., tangible rather than tactile). Furthermore, at least one memory 520 may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, apparatuses, or any combination thereof.

[0064] In addition, in some embodiments, the example device 500 may also include at least one other element, circuit or interface, such as at least one I / O interface, antenna element, etc.

[0065] In some embodiments, the circuits, components, elements, and interfaces in the example device 500 (including at least one processor 510 and at least one memory 520 as described above) may be coupled to some via any suitable connection mechanism, such as, but not limited to, buses, cross switches, wired and / or wireless lines, and the connection method may include, but is not limited to, electrical connections, magnetic connections, optical connections, electromagnetic connections, etc.

[0066] Figure 6 An example block diagram of an example apparatus 600 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. This example apparatus 600 may be, for example, at least a portion of any network device such as the access network device 150 described above according to an exemplary embodiment of the present disclosure.

[0067] like Figure 6 As shown, the example device 600 may include at least one processor 610 and at least one memory 620, wherein the at least one memory 620 may include instructions 630, and when the instructions 630 are executed by the at least one processor 610, the example device 600 performs at least the example method 300 described above.

[0068] In some embodiments, at least one processor 610 in the example device 600 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit, or may be part of at least one hardware processor and a dedicated processor such as one developed based on a field-programmable gate array. Additionally, the at least one processor 610 may also include components not in... Figure 6 At least one other circuit or element shown in the diagram.

[0069] In some embodiments, at least one memory 620 in the example device 600 may include various forms of storage media, such as volatile and / or non-volatile memory. Volatile memory may include, but is not limited to, random access memory, cache memory, etc. Non-volatile memory may include, but is not limited to, read-only memory, hard disk, flash memory, etc. The term "non-volatile" in this disclosure, as opposed to the limitation of data storage persistence (e.g., RAM versus ROM), is a limitation concerning the medium itself (i.e., tangible rather than tactile). Furthermore, at least one memory 620 may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, apparatuses, or any combination thereof.

[0070] In addition, in some embodiments, the example device 600 may also include at least one other element, circuit or interface, such as at least one I / O interface, antenna element, etc.

[0071] In some embodiments, the circuits, components, elements, and interfaces in the example device 600 (including at least one processor 610 and at least one memory 620 as described above) may be coupled to some via any suitable connection mechanism, such as, but not limited to, buses, cross switches, wired and / or wireless lines, and the connection method may include, but is not limited to, electrical connections, magnetic connections, optical connections, electromagnetic connections, etc.

[0072] Figure 7 This diagram illustrates an example block diagram of an example apparatus 700 for ultra-low latency communication according to an exemplary embodiment of the present disclosure. The example apparatus 700 may, for example, be at least a portion of any network device that implements the functions of the core network 180 described above according to an exemplary embodiment of the present disclosure.

[0073] like Figure 7 As shown, the example device 700 may include at least one processor 710 and at least one memory 720, wherein the at least one memory 720 may include instructions 730, and when the instructions 730 are executed by the at least one processor 710, the example device 700 performs at least the example method 400 described above.

[0074] In some embodiments, at least one processor 710 in the example device 700 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit, or may be part of at least one hardware processor and a dedicated processor such as one developed based on a field-programmable gate array. Additionally, the at least one processor 710 may also include components not in... Figure 7 At least one other circuit or element shown in the diagram.

[0075] In some embodiments, at least one memory 720 in the example device 700 may include various forms of storage media, such as volatile and / or non-volatile memory. Volatile memory may include, but is not limited to, random access memory, cache memory, etc. Non-volatile memory may include, but is not limited to, read-only memory, hard disk, flash memory, etc. The term "non-volatile" in this disclosure, as opposed to the limitation of data storage persistence (e.g., RAM versus ROM), is a limitation concerning the medium itself (i.e., tangible rather than tactile). Furthermore, at least one memory 720 may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, apparatuses, or any combination thereof.

[0076] In addition, in some embodiments, the example device 700 may also include at least one other element, circuit or interface, such as at least one I / O interface, antenna element, etc.

[0077] In some embodiments, the circuits, components, elements, and interfaces in the example device 700 (including at least one processor 710 and at least one memory 720 as described above) may be coupled to some via any suitable connection mechanism, such as, but not limited to, buses, cross switches, wired and / or wireless lines, and the connection method may include, but is not limited to, electrical connections, magnetic connections, optical connections, electromagnetic connections, etc.

[0078] Figure 8 An example block diagram of an example device 800 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. This example device 800 may be, for example, at least a portion of any terminal device such as the terminal device 110 described above according to an exemplary embodiment of the present disclosure.

[0079] like Figure 8 As shown, the example device 800 may include: a device 810 for receiving a configuration of a specific DRB from an access network device, the configuration of the specific DRB including at least one of the following: an identifier of the specific DRB, a configuration of the SDAP layer, a configuration of the PDCP layer for the specific DRB, a configuration of the RLC layer for the specific DRB, or a configuration of the MAC layer for the specific DRB; a device 820 for creating an SDAP layer entity, a PDCP layer entity, an RLC layer entity, or a MAC layer entity respectively based on the received configuration of the SDAP layer, the PDCP layer, the RLC layer, or the MAC layer; and a device 830 for receiving scheduling information from the access network device, the scheduling information indicating the identifier of the specific DRB.

[0080] In some embodiments, when the specific DRB is used for the downlink, the example device 800 may include: means for determining, based on the identifier of the specific DRB indicated by the scheduling information, that received data has undergone transparent operation at the RLC layer and MAC layer of the access network device; means for decoding the data to obtain the TB that transmitted the data; means for determining the corresponding PDCP layer entity based on the identifier of the specific DRB indicated by the scheduling information; and means for passing the TB to the PDCP layer entity.

[0081] In some embodiments, when the specific DRB is used for the uplink, the example device 800 may include: means for determining, based on the scheduling information, to perform a transparent operation on the data, the transparent operation including any one of the following: mapping a data QoS stream to the specific DRB by an SDAP layer entity based on the identifier of the specific DRB indicated by the scheduling information, and passing the specific DRB to the corresponding PDCP layer entity; performing the processing specified by the PDCP configuration on the specific DRB by the PDCP layer entity, and if the processed PDU is less than the TB size, padding the PDU to the TB size, and passing the padded PDCP layer PDU to the corresponding RLC layer entity; passing the PDCP layer PDU as the RLC layer PDU to the MAC layer entity by the RLC layer entity; or passing the RLC layer PDU as the TB to the physical channel for transmission by the MAC layer entity.

[0082] In some embodiments, examples of the apparatus in example device 800 may include circuitry. For example, an example of apparatus 810 may include circuitry configured to perform operation 210 of example method 200, an example of apparatus 820 may include circuitry configured to perform operation 220 of example method 200, and an example of apparatus 830 may include circuitry configured to perform operation 230 of example method 200. In some embodiments, examples of the apparatus may also include software modules and other suitable functional entities. Example device 800 may further include apparatus having circuitry configured to perform example method 200. In some embodiments, examples of the apparatus may also include software modules and other suitable functional entities.

[0083] Figure 9 An example block diagram of an example device 900 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. This example device 900 may be, for example, at least a portion of any network device such as the access network device 150 described above according to an exemplary embodiment of the present disclosure.

[0084] like Figure 9As shown, the example device 900 may include: a device 910 for determining a data QoS flow to be mapped to a specific DRB; a device 920 for sending a configuration of the specific DRB to a terminal device, the configuration of the specific DRB including at least one of the following: an identifier of the specific DRB, a configuration of the SDAP layer, a configuration of the PDCP layer for the specific DRB, a configuration of the RLC layer for the specific DRB, or a configuration of the MAC layer for the specific DRB; and a device 930 for sending scheduling information to the terminal device, the scheduling information indicating the identifier of the specific DRB.

[0085] In some embodiments, if the PDB of the data QoS stream is below a threshold, it is determined that the data QoS stream will be mapped to the specific DRB.

[0086] In some embodiments, upon receiving a specific delay indication of the data QoS flow from the core network, it is determined that the data QoS flow will be mapped to the specific DRB.

[0087] In some embodiments, examples of the apparatus in example device 900 may include circuitry. For example, an example of apparatus 910 may include circuitry configured to perform operation 310 of example method 300, an example of apparatus 920 may include circuitry configured to perform operation 320 of example method 300, and an example of apparatus 930 may include circuitry configured to perform operation 330 of example method 300. In some embodiments, examples of the apparatus may also include software modules and other suitable functional entities. Example device 900 may further include apparatus having circuitry configured to perform example method 300. In some embodiments, examples of the apparatus may also include software modules and other suitable functional entities.

[0088] Figure 10 An example block diagram of an example device 1000 for ultra-low latency communication according to an exemplary embodiment of the present disclosure is shown. This example device 1000 may be, for example, at least a portion of any network device that implements the functions of the core network 180 described above according to an exemplary embodiment of the present disclosure.

[0089] like Figure 10 As shown, the example device 1000 may include: a device 1010, configured to send a specific delay indication of the data QoS flow to an access network device based on the latency quality of service requirements of the data QoS flow, so that the access network device determines that the data QoS flow will be mapped to a specific DRB.

[0090] In some embodiments, examples of the apparatus in example device 1000 may include circuitry. For example, an example of apparatus 1010 may include circuitry configured to perform operation 410 of example method 400. In some embodiments, examples of the apparatus may also include software modules and other suitable functional entities. Example device 1000 may further include apparatus having circuitry configured to perform example method 400. In some embodiments, examples of the apparatus may also include software modules and other suitable functional entities.

[0091] Exemplary embodiments of this disclosure also provide a computer-readable storage medium including program instructions that, when executed by any terminal device such as terminal device 110 according to exemplary embodiments of this disclosure, cause the terminal device to: receive configuration of a specific DRB from an access network device, the configuration of the specific DRB including at least one of: an identifier of the specific DRB, a configuration of an SDAP layer, a configuration of a PDCP layer for the specific DRB, a configuration of an RLC layer for the specific DRB, or a configuration of a MAC layer for the specific DRB; create an SDAP layer entity, a PDCP layer entity, an RLC layer entity, or a MAC layer entity respectively based on the received configuration of the SDAP layer, the PDCP layer, the RLC layer, or the MAC layer; and receive scheduling information from the access network device, the scheduling information indicating the identifier of the specific DRB.

[0092] In some embodiments, where the specific DRB is used for the downlink, the computer-readable storage medium may further include program instructions that, when executed by the terminal device, enable the terminal device to: determine, based on the identifier of the specific DRB indicated by the scheduling information, that the received data has undergone transparent operation at the RLC and MAC layers of the access network device; decode the data to obtain the TB that transmitted the data; determine the corresponding PDCP layer entity based on the identifier of the specific DRB indicated by the scheduling information; and transfer the TB to the PDCP layer entity.

[0093] In some embodiments, when the specific DRB is used for the uplink, the computer-readable storage medium may further include program instructions that, when executed by the terminal device, enable the terminal device to: determine, based on the scheduling information, perform a transparent operation on the data, the transparent operation including any one of the following: mapping the data QoS stream to the specific DRB by an SDAP layer entity based on the identifier of the specific DRB indicated by the scheduling information, and passing the specific DRB to the corresponding PDCP layer entity; performing the processing specified by the PDCP configuration on the specific DRB by the PDCP layer entity, and if the processed PDU is smaller than the TB size, padding the PDU to the TB size, and passing the padded PDCP layer PDU to the corresponding RLC layer entity; passing the PDCP layer PDU as the RLC layer PDU to the MAC layer entity by the RLC layer entity; or passing the RLC layer PDU as the TB to the physical channel for transmission by the MAC layer entity.

[0094] Exemplary embodiments of this disclosure also provide a computer-readable storage medium including program instructions that, when executed by any network device such as the access network device 150 described above according to exemplary embodiments of this disclosure, enable the network device to: determine a data QoS flow to be mapped to a specific DRB; send a configuration of the specific DRB to a terminal device, the configuration of the specific DRB including at least one of: an identifier of the specific DRB, a configuration of the SDAP layer, a configuration of the PDCP layer for the specific DRB, a configuration of the RLC layer for the specific DRB, or a configuration of the MAC layer for the specific DRB; and send scheduling information to the terminal device, the scheduling information indicating the identifier of the specific DRB.

[0095] In some embodiments, if the PDB of the data QoS stream is below a threshold, it is determined that the data QoS stream will be mapped to the specific DRB.

[0096] In some embodiments, upon receiving a specific delay indication of the data QoS flow from the core network, it is determined that the data QoS flow will be mapped to the specific DRB.

[0097] An exemplary embodiment of this disclosure also provides a computer-readable storage medium including program instructions that, when executed by any network device implementing the functions of the core network 180 according to an exemplary embodiment of this disclosure, cause the network device to: send a specific delay indication of the data QoS stream to an access network device based on the latency quality of service requirements of the data QoS stream, causing the access network device to determine that the data QoS stream will be mapped to a specific DRB.

[0098] It should be understood that the apparatus according to the embodiments of this disclosure is not limited to the examples described above. The modules in the illustrated example apparatuses can be connected or coupled together in any suitable manner, and the arrows between the modules are only used to indicate the direction of data or signals of interest, but do not indicate that the direction of data or signals between modules can only be in the direction of the arrows.

[0099] The phrases “at least one of the following: <two or more listed elements>” and “at least one of <two or more listed elements>” and similar expressions in this disclosure, wherein the two or more listed elements are connected by “and” or “or”, mean at least one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0100] In this document, the term "terminal device" refers to any end device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, VoIP phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc.

[0101] In addition to the methods and apparatus described above, embodiments of this disclosure may also be computer program products comprising instructions that, when executed by a processor, cause the processor to perform the steps in the example methods described above.

[0102] The computer program product can be written in any combination of one or more programming languages ​​to perform operations of the exemplary embodiments of this disclosure. These programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0103] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0104] The basic principles of this disclosure have been described above in conjunction with embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0105] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0106] Furthermore, in the apparatus, devices, and methods disclosed herein, the components or steps can be disassembled and / or recombined. Such disassembly and / or recombination should be considered equivalent solutions to this disclosure.

[0107] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0108] The above description has been given for illustrative and descriptive purposes and is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

[0109] The following are some abbreviations or acronyms that may be used in this disclosure and its accompanying drawings:

[0110] 5G fifth-generation mobile communication system

[0111] B5G Post-5G

[0112] 6G sixth-generation mobile communication system

[0113] ACK confirmation

[0114] AMF Access and Mobility Management Functions

[0115] BS base station

[0116] CN Core Network

[0117] DCI Downlink Control Information

[0118] DL downlink

[0119] DRB data radio bearer

[0120] gNB Next Generation Node B

[0121] HARQ Hybrid Automatic Repeat Request

[0122] HRLLC Ultra-Reliable Low-Latency Communication

[0123] ID identifier

[0124] L1 Floor 1

[0125] L2 Floor 2

[0126] MAC Media Access Control

[0127] MCS modulation and coding methods

[0128] NACK denies

[0129] PDB Packet Delay Budget

[0130] PDCCH (Physical Downlink Control Channel)

[0131] PDCP (Packet Data Convergence Protocol)

[0132] PDU Protocol Data Unit

[0133] PER (Grouping Error Rate)

[0134] QoS (Quality of Service)

[0135] RAN (Radio Access Network)

[0136] RLC Wireless Link Control

[0137] ROHC Robust Head Compressor

[0138] RRC (Radio Resource Control)

[0139] SDAP Service Data Adaptation Protocol

[0140] SDU Service Data Unit

[0141] SMF Session Management Function

[0142] TB transfer block

[0143] TM Transparent Mode

[0144] TTI Transmission Time Interval

[0145] UE User Equipment

[0146] UL uplink

[0147] URLLC (URLLC) is a high-reliability, low-latency communication protocol.

Claims

1. A terminal device, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to perform: receiving, from an access network device, a configuration of a specific data radio bearer, the configuration of the specific data radio bearer comprising at least one of an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; creating a service data adaptation protocol layer entity, a packet data convergence protocol layer entity, a radio link control layer entity, or a medium access control layer entity, respectively, according to the received configuration of the service data adaptation protocol layer, the packet data convergence protocol layer, the radio link control layer, or the medium access control layer; and receiving, from the access network device, scheduling information indicating an identity of the specific data radio bearer.

2. The terminal device of claim 1, wherein, in a case where the specific data radio bearer is for downlink, the instructions that, when executed by the at least one processor, cause the terminal device to perform: determining, according to the identity of the specific data radio bearer indicated by the scheduling information, that data received has undergone a transparent operation at a radio link control layer and a medium access control layer of the access network device; decoding the data to obtain a transport block that transports the data; determining, according to the identity of the specific data radio bearer indicated by the scheduling information, a corresponding packet data convergence protocol layer entity; and delivering the transport block to the packet data convergence protocol layer entity.

3. The terminal device of claim 1, wherein, in a case where the specific data radio bearer is for uplink, the instructions that, when executed by the at least one processor, cause the terminal device to perform: determining, according to the scheduling information, to perform a transparent operation on data, the transparent operation comprising any one of: mapping, by a service data adaptation protocol layer entity, a data quality of service flow to the specific data radio bearer according to the identity of the specific data radio bearer indicated by the scheduling information, and delivering the specific data radio bearer to a corresponding packet data convergence protocol layer entity; performing, by the packet data convergence protocol layer entity, a process specified by the configuration of the packet data convergence protocol for the specific data radio bearer, and in a case where a protocol data unit after the process is less than a transport block size, padding the protocol data unit of the packet data convergence protocol layer to the transport block size, and delivering the padded protocol data unit of the packet data convergence protocol layer to a corresponding radio link control layer entity; delivering, by the radio link control layer entity, the protocol data unit of the packet data convergence protocol layer to the medium access control layer entity as a protocol data unit of the radio link control layer; or delivering, by the medium access control layer entity, the protocol data unit of the radio link control layer to a physical channel as a transport block for transmission.

4. An access network device, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the access network device to perform: determining that a data quality of service flow is to be mapped to a particular data radio bearer; sending, to a terminal device, a configuration of the particular data radio bearer, the configuration of the particular data radio bearer comprising at least one of an identification of the particular data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the particular data radio bearer, a configuration of a radio link control layer for the particular data radio bearer, or a configuration of a medium access control layer for the particular data radio bearer; and sending, to the terminal device, scheduling information indicating the identification of the particular data radio bearer. the instructions that, when executed by the at least one processor, cause the terminal device to perform:

5. The access network device of claim 4, wherein, determining that the data quality of service flow is to be mapped to the particular data radio bearer in a case that a packet delay budget of the data quality of service flow is below a threshold. the instructions that, when executed by the at least one processor, cause the terminal device to perform:

6. The access network device of claim 4, wherein, determining that the data quality of service flow is to be mapped to the particular data radio bearer in a case that a particular delay indication regarding the data quality of service flow is received from a core network.

7. A core network device, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the core network device to perform: sending, to an access network device, a particular delay indication regarding a data quality of service flow according to a latency quality of service requirement of the data quality of service flow, causing the access network device to determine that the data quality of service flow is to be mapped to a particular data radio bearer.

8. A method performed by a terminal device, comprising: receiving, from an access network device, a configuration of a particular data radio bearer, the configuration of the particular data radio bearer comprising at least one of an identification of the particular data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the particular data radio bearer, a configuration of a radio link control layer for the particular data radio bearer, or a configuration of a medium access control layer for the particular data radio bearer; creating a service data adaptation protocol layer entity, a packet data convergence protocol layer entity, a radio link control layer entity, or a medium access control layer entity according to the received configuration of the service data adaptation protocol layer, the packet data convergence protocol layer, the radio link control layer, or the medium access control layer, respectively; and receiving, from the access network device, scheduling information indicating the identification of the particular data radio bearer. in a case that the particular data radio bearer is for downlink, the method comprising:

9. The method of claim 8, wherein, ​ determining, according to the identity of the specific data radio bearer indicated by the scheduling information, that the received data has undergone a transparent operation at a radio link control layer and a medium access control layer of the access network device; decoding the data to obtain a transport block that carries the data; determining, according to the identity of the specific data radio bearer indicated by the scheduling information, a corresponding packet data convergence protocol layer entity; and delivering the transport block to the packet data convergence protocol layer entity.

10. The method of claim 8, wherein, In a case where the specific data radio bearer is used for uplink, the method comprises: determining, according to the scheduling information, that a transparent operation is performed on data, the transparent operation comprising any one of the following: mapping, by a service data adaptation protocol layer entity, a data quality of service flow to the specific data radio bearer according to the identity of the specific data radio bearer indicated by the scheduling information, and delivering the specific data radio bearer to a corresponding packet data convergence protocol layer entity; performing, by the packet data convergence protocol layer entity, a process specified by a configuration of the packet data convergence protocol on the specific data radio bearer, in a case where a protocol data unit after the process is smaller than a transport block size, padding the protocol data unit of the packet data convergence protocol layer to the transport block size, and delivering the padded protocol data unit of the packet data convergence protocol layer to a corresponding radio link control layer entity; delivering, by the radio link control layer entity, the protocol data unit of the packet data convergence protocol layer to the medium access control layer entity as a protocol data unit of the radio link control layer; or delivering, by the medium access control layer entity, the protocol data unit of the radio link control layer to a physical channel as a transport block for transmission.

11. A method performed by an access network device, comprising: determining a data quality of service flow that is to be mapped to a specific data radio bearer; sending, to a terminal device, a configuration of the specific data radio bearer, the configuration of the specific data radio bearer comprising at least one of the following: an identity of the specific data radio bearer, a configuration of a service data adaptation protocol layer, a configuration of a packet data convergence protocol layer for the specific data radio bearer, a configuration of a radio link control layer for the specific data radio bearer, or a configuration of a medium access control layer for the specific data radio bearer; and sending, to the terminal device, scheduling information, the scheduling information indicating the identity of the specific data radio bearer.

12. The method of claim 11, comprising: determining that the data quality of service flow is to be mapped to the specific data radio bearer in a case where a packet delay budget of the data quality of service flow is lower than a threshold.

13. The method of claim 11, comprising: determining that the data quality of service flow is to be mapped to the specific data radio bearer in a case where a specific delay indication about the data quality of service flow is received from a core network.

14. A method performed by a core network device, comprising: ​ According to a latency quality of service requirement of a data quality of service flow, a specific delay indication about the data quality of service flow is sent to an access network device, and the access network device is caused to determine that the data quality of service flow is to be mapped to a specific data radio bearer.

15. A device as a terminal device, comprising means for performing the method of any one of claims 8 to 10.

16. A device as an access network device, comprising means for performing the method of any one of claims 11 to 13.

17. A device as a core network device, comprising means for performing the method of claim 14.

18. A computer readable storage medium comprising program instructions that, when executed by a terminal device, cause the terminal device to perform the method of any one of claims 8 to 10.

19. A computer readable storage medium comprising program instructions that, when executed by an access network device, cause the access network device to perform the method of any one of claims 11 to 13.

20. A computer readable storage medium comprising program instructions that, when executed by a core network device, cause the core network device to perform the method of claim 14.

Images