WO2024082361A1 - Procédé et appareil de transmission de données - Google Patents

Procédé et appareil de transmission de données Download PDF

Info

Publication number
WO2024082361A1
WO2024082361A1 PCT/CN2022/131431 CN2022131431W WO2024082361A1 WO 2024082361 A1 WO2024082361 A1 WO 2024082361A1 CN 2022131431 W CN2022131431 W CN 2022131431W WO 2024082361 A1 WO2024082361 A1 WO 2024082361A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu set
pdu
type
drb
information
Prior art date
Application number
PCT/CN2022/131431
Other languages
English (en)
Inventor
Mingzeng Dai
Xiaoying Xu
Haiyan Luo
Shuigen Yang
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2022/131431 priority Critical patent/WO2024082361A1/fr
Publication of WO2024082361A1 publication Critical patent/WO2024082361A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • Embodiments of the present application generally relate to wireless communication technology, especially to a method and apparatus of data transmission, e.g., data transmission supporting data radio bearer (DRB) with different protocol data unit (PDU) set types.
  • DRB data transmission supporting data radio bearer
  • PDU protocol data unit
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, and so on.
  • Wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power) .
  • Examples of wireless communication systems may include fourth generation (4G) systems such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-APro systems, and fifth generation (5G) system (5GS) which may also be referred to as new radio (NR) systems.
  • 4G systems such as long term evolution (LTE) systems, LTE-advanced (LTE-A) systems, or LTE-APro systems
  • 5G system (5GS) which may also be referred to as new radio (NR) systems.
  • extended reality including augmented reality (AR) and virtual reality (VR) , as well as cloud gaming (CG)
  • CG cloud gaming
  • 3GPP 3 rd generation partnership program
  • QoS quality of service
  • PDUs packets belonging to less important PDU set (s) differently to reduce the resource wasting.
  • Possible solutions are mapping PDU sets with different importance associated with the same traffic, e.g., XR service into one DRB, which can support reordering in PDCP layer among different PDU sets.
  • XR service into one DRB
  • One objective of the embodiments of the present application is to provide a technical solution of data transmission, e.g., a method and apparatus of data transmission for XR services or the like over F1 interface, wherein PDU sets with different PDU set types belonging to the same XR service or the like can be mapped into the same DRB.
  • a central unit (CU) of a RAN node e.g., a gNB-CU, which includes: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: determine to apply a first bearer type of a DRB to transmit a plurality of PDU set types; and transmit, to a distributed unit (DU) of the RAN node, an indication of the first bearer type of the DRB, and PDU set type information associated with the plurality of PDU set types; wherein, the first bearer type of the DRB is served by a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • DU distributed unit
  • each F1-U tunnel corresponds to a PDU set type.
  • the processor is further configured to: transmit, to the DU, uplink transport network layer (TNL) information for each F1-U tunnel of each PDU set type; and receive, from the DU, downlink TNL information for each F1-U tunnel of each PDU set type, wherein, the uplink TNL information for each F1-U tunnel of each PDU set type includes first uplink TNL information for one PDU set type and second uplink TNL information for each of remaining PDU set types, and the downlink TNL information for each F1-U tunnel of each PDU set type includes first downlink TNL information for the one PDU set type and second downlink TNL information for each of the remaining PDU set types.
  • TNL transport network layer
  • the CU further includes a CU control plane (CP) and a CU user plane (UP) coupled to the CU CP, and wherein, the CU CP is configured to: determine the first bearer type for the DRB, and transmit the indication of the first bearer type of the DRB and the PDU set type information to both the DU and the CU UP.
  • CP CU control plane
  • UP CU user plane
  • the CU UP is configured to: receive the indication of the first bearer type of the DRB and the PDU set type information from the CU CP; allocate uplink TNL information for each F1-U tunnel of each PDU set type based on the indication of the first bearer type of the DRB and the PDU set type information; transmit the uplink TNL information for each F1-U tunnel of each PDU set type to the CU CP; and receive downlink TNL information for each F1-U tunnel of each PDU set type forwarded by the CU CP that is received from the DU.
  • the CU CP is further configured to: receive uplink TNL information for each F1-U tunnel of each PDU set type from the CU CP; transmit the received uplink TNL information for each F1-U tunnel of each PDU set type to the DU; receive downlink TNL information for each F1-U tunnel of each PDU set type from the DU; and transmit the downlink TNL information for each F1-U tunnel of each PDU set type to the CU UP.
  • the processor is configured to: in the case of a plurality of PDU sets with the plurality of PDU set types belonging to a traffic from a core network, map the plurality of PDU sets to the DRB in a service data adaptation protocol (SDAP) entity, and send packet data convergence protocol (PDCP) PDUs of the plurality of PDU sets to different F1-U tunnels correspondingly; and in the case of a plurality of PDU sets with the plurality of PDU set types belonging to a traffic from a user equipment, receive PDCP PDUs of the plurality of PDU sets via different F1-U tunnels.
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • the processor is configured to receive flow control information corresponding to each PDU set type from the DU.
  • the flow control information indicates at least one of the following information: a highest PDCP PDU sequence number successfully delivered in sequence to a user equipment of a PDU set type; a highest PDCP PDU sequence number transmitted to lower layers of a PDU set type; or a desired buffer size for the PDU set type of the DRB.
  • the flow control information is indicated in a downlink data delivery status frame with a PDU set type indication.
  • the plurality of PDU set types have different importance.
  • each radio link control (RLC) entity corresponds to each logical channel.
  • a DU of a RAN node e.g., a gNB-DU
  • a transceiver e.g., a transceiver
  • a processor coupled to the transceiver, wherein the processor is configured to: receive, from a CU of the RAN node, a PDU set type information associated with a plurality of PDU set types; determine a first bearer type of a DRB for a plurality of PDU set types; and transmit, to the CU, an indication of the first bearer type of the DRB; wherein the first bearer type of the DRB is associated with a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • each F1-U tunnel corresponds to a PDU set type.
  • the processor is further configured to: receive, from the CU, uplink TNL information for each F1-U tunnel of each PDU set type; and transmit, to the CU, downlink TNL information for each F1-U tunnel of each PDU set type, wherein, the uplink TNL information for each F1-U tunnel of each PDU set type includes first uplink TNL information for one PDU set type and second uplink TNL information for each of remaining PDU set types, and the downlink TNL information for each F1-U tunnel of each PDU set type includes first downlink TNL information for the one PDU set type and second downlink TNL information for each of the remaining PDU set types.
  • the downlink TNL information for each F1-U tunnel of each PDU set type is transmitted with the indication indicating that the certain bearer type is applied for the DRB or after receiving the uplink TNL information for each F1-U tunnel of each PDU set type.
  • the first uplink TNL information is received with the PDU set type information or after transmitting the indication of the first bearer type of the DRB, and the second uplink TNL information is received after transmitting the indication of the first bearer type of the DRB.
  • the first downlink TNL information is transmitted with the indication of the first bearer type of the DRB
  • the second downlink TNL information is transmitted also with the indication of the first bearer type of the DRB is applied for the DRB or after receiving the second uplink TNL information.
  • the CU further includes a CU CP and a CU UP coupled to the CU CP, and wherein, the uplink TNL information for each F1-U tunnel of each PDU set type is received from the CU CP and the downlink TNL information for each F1-U tunnel of each PDU set type is transmitted to the CU CP.
  • the processor is further configured to: allocate different logical channel identities for the plurality of PDU set types based on the PDU set type information; and transmit logical channel information indicating the different logical channel identities to the CU with the indication of the first bearer type of the DRB.
  • the processor is configured to: in the case of a plurality of PDU sets with the plurality of PDU set types belonging to a traffic from a core network, receive PDCP PDUs of the plurality of PDU sets from different F1-U tunnels correspondingly; and in the case of a plurality of PDU sets with the plurality of PDU set types belonging to a traffic from a user equipment, transmit PDCP PDUs of the plurality of PDU sets identified to different F1-U tunnels.
  • the CU further includes a CU CP and a CU UP coupled to the CU CP, wherein, the PDU set type information is received from the CU CP and the indication of the first bearer type of the DRB is transmitted to the CU CP.
  • the processor is configured to transmit flow control information corresponding to each PDU set type to the CU.
  • a DU of a RAN node e.g., a gNB-DU
  • a transceiver e.g., a transceiver
  • a processor coupled to the transceiver, wherein the processor is configured to: receive, from a CU of the RAN node, an indication of a first bearer type of a DRB and PDU set type information associated with different PDU set types, wherein, the first bearer type of the DRB is served by a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types; and allocate different logical channels for different PDU set types based on the indication of the first bearer type of the DRB and the PDU set type information.
  • Some yet other embodiments of the present application also provide a CU of a RAN node, e.g., a gNB-CU, which includes: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: transmit, to a DU of the RAN node, PDU set type information associated with a plurality of PDU set types; and receive, from the DU, an indication of a first bearer type of a DRB; wherein the first bearer type of the DRB is associated with a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • a CU of a RAN node e.g., a gNB-CU, which includes: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: transmit, to a DU of the RAN node, PDU set type information associated with a plurality of PDU set types; and receive
  • embodiments of the present application provide a technical solution of data transmission, wherein PDU sets with different PDU set types of the same traffic, e.g., of the same XR services can be mapped into the same DRB. Issues on how to support configuration and data transmission of the same DRB carrying different PDU set types over F1 interface are solved. Accordingly, the present application can facilitate and improve the implementation of NR.
  • FIG. 1 illustrates a wireless communication system according to some embodiments of the present application.
  • FIG. 2 is a schematic diagram illustrating an internal structure of a RAN node according to some embodiments of the present application.
  • FIG. 3 is a schematic diagram illustrating an internal structure of a RAN node according to some other embodiments of the present application.
  • FIG. 4 illustrates a schematic diagram of an internal structure of a RAN node for data transmission of an exemplary new type DRB according to some embodiments of the present application.
  • FIG. 5 illustrates a schematic diagram of an internal structure of a RAN node for data transmission of an exemplary new type DRB according to some other embodiments of the present application.
  • FIG. 6 is a flow chart illustrating a method of data transmission in Scenario 1 according to some embodiments of the present application.
  • FIG. 7 is a flow chart illustrating a method of data transmission in Scenario 1 according to some other embodiments of the present application.
  • FIG. 8 is a flow chart illustrating a method of data transmission in Scenario 2 according to some embodiments of the present application.
  • FIG. 9 is a flow chart illustrating a method of data transmission in Scenario 2 according to some other embodiments of the present application.
  • FIG. 10 is a flow chart illustrating a method of data transmission in Scenario 1 according to some yet embodiments of the present application.
  • FIG. 11 illustrates a block diagram of an apparatus of data transmission according to some embodiments of the present application.
  • FIG. 12 illustrates a block diagram of an apparatus of data transmission according to some other embodiments of the present application.
  • FIG. 1 illustrates a schematic diagram of an exemplary wireless communication system 100 according to some embodiments of the present application.
  • the wireless communication system 100 includes at least one base station (BS) 101 and at least one UE 102.
  • the wireless communication system 100 includes one BS 101 and two terminal device 102 (e.g., a first UE 102a and a second UE 102b) for illustrative purpose.
  • BS base station
  • terminal device 102 e.g., a first UE 102a and a second UE 102b
  • FIG. 1 a specific number of BSs and terminal devices are illustrated in FIG. 1 for simplicity, it is contemplated that the wireless communication system 100 may include more or less BSs and terminal devices in some other embodiments of the present application.
  • the wireless communication system 100 is compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the BS 101 may communicate with a core network (CN) node (not shown) , e.g., a mobility management entity (MME) or a serving gateway (S-GW) , an authentication and mobility management function (AMF) or a user plane function (UPF) etc. via an interface.
  • CN core network
  • MME mobility management entity
  • S-GW serving gateway
  • AMF authentication and mobility management function
  • UPF user plane function
  • a BS also be referred to as an access point, an access terminal, a base, a macro cell, a node-B, an enhanced node B (eNB) , a gNB, a home node-B, a relay node, or a device, or described using other terminology used in the art.
  • a BS may also refer to as a RAN node.
  • Each BS may serve a number of UE(s) within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • Neighbor BSs may communicate with each other as necessary, e.g., during a handover procedure for a UE.
  • the terminal device (or remote apparatus) 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • the terminal device may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the terminal device may include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the terminal device may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • UE is used exemplarily as a classical terminal device for illustrating the terminal device, it should be understood as any type terminal device.
  • FIG. 2 is a schematic diagram illustrating an internal structure of a RAN node, e.g., a BS according to some embodiments of the present application.
  • the internal structure of a RAN node may be split into a CU 200 and at least one DU 202 (e.g., two DUs shown in FIG. 2) .
  • a RAN node e.g., BS 101
  • DU 202 e.g., two DUs shown in FIG. 2
  • FIG. 2 a specific number of DUs 202 are depicted in FIG. 2, it is contemplated that any number of DUs 202 may be included in the BS.
  • the CU 200 e.g., a CU of a gNB (gNB CU, or gNB-CU) and DU 202 e.g., a DU of a gNB (gNB DU, or gNB-DU) are connected with each other by an interface called F1 as specified in 3GPP standard documents.
  • the RRC layer functionality, SDAP functionality, and the PDCP layer functionality are located in the CU 200.
  • the RLC layer functionality, MAC layer functionality, and the PHY layer functionality are located in the DU 202.
  • the CU may be separated into a CU CP unit (also referred to as “CU CP” or “CU-CP” ) and at least one CU UP unit (or also referred to as “CU UP” or “CU-UP” ) .
  • FIG. 3 is a schematic diagram illustrating an internal structure of a BS 300 according to some other embodiments of the present application.
  • the CU of the BS 300 may be separated into a CU-CP unit 310 and at least one CU-UP 312.
  • the CU-CP unit 310 and each CU-UP unit 312 may be connected with each other by an interface called E1 as specified in 3GPP standard documents.
  • the CU-CP unit 310 and the DU 33 of the BS 300 are connected by an interface called F1-C as specified in 3GPP documents.
  • Each CU-UP unit 312 and the DU 33 are connected by an interface called F1-U as specified in 3GPP standard documents.
  • a PDU set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XR management services, as used in TR 26.926) .
  • all PDUs in a PDU set are needed by the application layer to use the corresponding information unit.
  • the application layer can still recover part (s) or all of the information unit (s) .
  • PDU sets There are various types of PDU sets. For example, different types of PDU sets can carry different contents, such as intra-coded pictures (also referred to as "I-frame” ) , predictive coded pictures (also referred to as “P-frame” ) , B-predictive coded pictures (also referred to "B-frame” ) . In another example, different types of PDU sets may have different importance or different priority levels.
  • a PDU set may be characterized by a notion of “importance” indicating how important the PDU set (e.g., a video frame) is for an application. For example, an important PDU set may be an I-Frame, while a less important PDU set may be a P-Frame.
  • mapping different types of PDU sets to one DRB is needed, and the DRB may be configured with different RLC entities (e.g., at least two) , whose logical channels (LCH) shave different priorities.
  • RLC entities e.g., at least two
  • LCH logical channels
  • a new type hereafter, referred to a new DRB type or a new bearer type
  • the DRB is served by a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • the DRB is served by one SDAP entity (or SDAP functionality, SDAP function etc. ) and one PDCP entity (or PDCP functionality, PDCP function etc. ) , but will be served by different (e.g., at least two) RLC entities (or RLC functionalities, RLC functions etc. ) and different logical channels, each RLC entity and logical channel corresponding to a PDU set type.
  • a DRB with the new DRB type or new bearer type is also called a new DRB or a new type DRB for simplicity.
  • the new type DRB is served by one cell or one cell group in a single DU of a RAN node, e.g., a gNB-DU, while the split bearer in dual connectivity is served by different cell groups on different gNB-DUs.
  • a RAN node e.g., a gNB-DU
  • the split bearer in dual connectivity is served by different cell groups on different gNB-DUs.
  • the data transmission and configuration procedures over F1 interface are different from dual connectivity. Accordingly, issues on how to support configuration and data transmission of the new type DRB over F1 interface should be solved, which include but not limited to the following:
  • embodiments of the present application propose a technical solution of data transmission, e.g., for data transmission of the new type DRB of XR services.
  • whether to apply the new bearer type of a DRB (or, whether to apply the new bearer type for a DRB, or whether the new bearer type or legacy bearer type is used for the DRB, or similar) to transmit a plurality of PDU sets types is determined or decided by one of a CU and a DU (any one of DUs coupled to the CU) within a RAN node.
  • an indication indicating that the certain bearer type is applied for the DRB (or indication of the certain bearer type of the DRB or similar) is transmitted to the other one of the CU and DU.
  • whether to apply the new bearer type for a DRB is decided by a CU, e.g., a gNB-CU (Scenario 1) .
  • An exemplary method of data transmission in Scenario 1 includes: determining to apply a certain bearer type (e.g., the new bearer type or new DRB type as stated above) of a DRB to transmit a plurality of PDU set types.
  • the certain bearer type of the DRB is served by a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • the plurality of PDU set types have different importance.
  • Each RLC entity corresponds to each logical channel.
  • the method further includes transmitting to a DU coupled to the CU, an indication of the first bearer type of the DRB, and PDU set type information associated with different PDU set types.
  • whether to apply the new bearer type of a DRB is decided by a DU, e.g., a gNB-DU (Scenario 2) .
  • An exemplary method of data transmission in Scenario 2 includes: receiving, from a CU coupled to the DU, PDU set type information associated with different PDU set types; and determining to apply a certain bearer type (e.g., the new bearer type or new DRB type as stated above) of the DRB for a plurality of PDU set types, wherein, the certain bearer type of the DRB is associated with a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • the method also includes transmitting, to the CU, an indication of the first bearer type of the DRB.
  • an exemplary F1-U tunnel means a general packet radio service (GPRS) tunnel protocol user plane (GTP-U) tunnel for data transmission over F1 interface, wherein, the GTP-U tunnel is usually identified by a GTP-U tunnel endpoint identifier (TEID) .
  • GPRS general packet radio service
  • GTP-U tunnel protocol user plane
  • FIG. 4 illustrates a schematic diagram of an internal structure of a RAN node for data transmission of an exemplary new type DRB according to some embodiments of the present application, wherein a plurality of F1-U tunnels are provided for the new type DRB.
  • a RAN node 400 e.g., a gNB may be split into a CU 410, e.g., a gNB-CU and at least one DU 420 (herein, only one DU, e.g., a gNB-DU is shown for simplicity) .
  • PDU set type 1 (or type 1) , e.g., important PDU set (s)
  • PDU set type 2 (or type 2) , e.g., less important (or unimportant) PDU set(s)
  • F1-U tunnels between the gNB-CU 410 and gNB-DU 420 each corresponding to a PDU set type.
  • a first F1-U tunnel 401a corresponds to PDU set type 1
  • a second F1-U tunnel 401b corresponds to PDU set type 2.
  • the gNB-CU 410 will map the different PDU sets into one DRB in one SDAP entity, that is, the SDAP entity is common for different PDU set types.
  • the gNB-CU 410 After processing by one PDCP entity, the gNB-CU 410 will send the PDCP PDUs of PDU Set 1 to the gNB-DU 420 via the first F1-U tunnel 401s and send the PDCP PDUs of PDU Set 2 to the gNB-DU 420 via the second F1-U tunnel 401b correspondingly.
  • the gNB-DU 420 will identify the PDU sets with different types according to the different F1-U tunnels and map the received PDCP PDUs to the corresponding RLC entity and logical channel for transmitting the data to UE (not shown) .
  • PDCP PDUs of PDU Set 1 received from the first F1-U tunnel 401a will be mapped to the first RLC entity 421a and the first logical channel with logical channel identity (LCID) 1
  • PDCP PDUs of PDU Set 2 received from the second F1-U tunnel 401b will be mapped to the second RLC entity 421b and the second logical channel with LCID 2.
  • LCID logical channel identity
  • the F1-U tunnel is common to all PDU set types, and can also be referred to as a common F1-U tunnel.
  • FIG. 5 illustrates a schematic diagram of an internal structure of a RAN node for data transmission of an exemplary new type DRB according to some other embodiments of the present application, wherein only one F1-U tunnel is provided for the new type DRB.
  • a RAN node 500 e.g., a gNB may be split into a CU 510, e.g., a gNB-CU and at least one DU 520 (herein, only one DU, e.g., a gNB-DU is shown for simplicity) .
  • PDU set type 1 or type 1
  • PDU set type 2 or type 2
  • the gNB-CU 510 will map the PDU sets with different types into one DRB in one SDAP entity. After processing by one PDCP entity, the gNB-CU 510 will send the PDCP PDUs of PDU Set 1 and the PDCP PDUs of PDU Set 2 via the only one F1-U tunnel 501 to the gNB-DU 520.
  • the gNB-DU 520 will identify the different types of PDU sets according to specific PDU set type indication, which may be included in the header of the common F1-U tunnel, e.g., PDU set 1 being type1, or PDU set 2 being type 2 etc. Then, the gNB-DU 520 will map the received PDCP PDUs of different PDU sets to the corresponding RLC entities and logical channels for transmitting the data to UE (not shown) . For example, PDCP PDUs of PDU Set 1 will be mapped to the first RLC entity 521a and the first logical channel identified by LCID 1 and PDCP PDUs of PDU Set 2 will be mapped to the second RLC entity 521b and the second logical channel identified by LCID 2.
  • FIG. 6 is a flow chart illustrating a method of data transmission in Scenario 1 according to some embodiments of the present application, wherein a plurality of F1-U tunnels are provided for a new type DRB.
  • the method is illustrated in a system level between the CU of the RAN node, e.g., a gNB-CU and a DU coupled to the CU, e.g., a gNB-DU
  • the method implemented in the CU and the DU can be separately implemented and/or incorporated by other apparatus with the like functions.
  • the gNB-CU may decide to apply a certain bearer type to a DRB in step 601 in some cases, e.g., in response to related information from the CN.
  • the certain bearer type is the new bearer type or new DRB type as stated above.
  • Exemplary related information may be QoS flow information or QoS parameters of PDU sets from the CN.
  • the related information from the CN may indicate that two (or more) different types of PDU sets, which may be carried by different QoS flows, i.e., using different QoS flows for different priority level PDU sets.
  • the gNB-CU may decide to map the two QoS flows to the new type DRB, so that the DRB is served by one SDAP layer, one PDCP layer, and at least two RLC entities and logical channels, each RLC entity and logical channel corresponding to a PDU set type.
  • the gNB-CU sends DRB to be setup information, e.g., DRB to Be Setup information element (IE) to a gNB-DU coupled to the gNB-CU for setup of the new type DRB.
  • the DRB to be setup information may be included in a UE CONTEXT SETUP REQUEST message or UE CONTEXT MODIFICATION REQUEST message or the like.
  • Exemplary DRB to be setup information may include an indication indicating that the certain bearer type of the DRB is applied (hereafter, also referred to as "new bearer type indication" or "new type DRB indication” or similar) .
  • the new bearer type indication is an explicit indication or implicit indication used to indicate that the DRB to be setup is a new type DRB.
  • the exemplary DRB to be setup information may also include PDU set type information, indicating different PDU set types carried by the DRB in various manners.
  • PDU set type information may indicate: PDU set type 1 and PDU set type 2, wherein, PDU set type 1 indicates PDU set (s) with high importance, and PDU set type 2 indicates PDU set (s) with less importance; while another exemplary PDU set type information may indicate: PDU set (s) with high importance, PDU set (s) with less importance or the like.
  • the PDU set type indicating high importance is defined as primary PDU set, while the PDU set type indicating less importance is called as secondary PDU set, and thus yet another exemplary PDU set type information may indicate: primary PDU set and secondary PDU set.
  • the gNB-CU may also transmit uplink (UL) TNL information for each F1-U tunnel of each PDU set type to the gNB-DU, which may also be included in the DRB to be setup information.
  • the UL TNL information for each F1-U tunnel of each PDU set type includes first UL TNL information for one PDU set type of the different PDU set types and second UL TNL information for each of remaining PDU set types.
  • the UL TNL information for each F1-U tunnel of each PDU set types also includes each UL TNL information for each PDU set type of the different PDU set types.
  • the UL TNL information for each F1-U tunnel of each PDU set type includes the UL TNL information for F1-U tunnel of the PDU set type indicating high importance and the UL TNL information for F1-U tunnel of the PDU set type indicating less importance.
  • the gNB-CU may separately transmit the UL TNL information for a corresponding F1-U tunnel of a PDU set type, for example, separately transmitting the first UL TNL information and the second UL TNL information to the gNB-DU.
  • the corresponding UL TNL information is the CU endpoint of the corresponding F1-U tunnel for delivery of UL PDU sets, which may contain a transport layer address (e.g., internet protocol (IP) address) and a GTP TEID.
  • IP internet protocol
  • the gNB-DU After receiving the new bearer type indication, the gNB-DU will be aware that the new type DRB is to be setup. The gNB-DU will allocate related parameters for the new bearer type DRB in step 605. For example, considering two PDU set types, the gNB-DU allocates two RLC entities and two logical channels (or LCIDs) for the new type DRB, each RLC entity and logical channel (or, LCID) is for a corresponding PDU set type. The modes of the RLC entities and the priorities of the logical channels will be configured according to the PDU set type information.
  • the gNB-DU may allocate RLC-acknowledge mode (AM) and high priority logical channel for the PDU set type indicating high importance, while allocate RLC-unacknowledged mode (UM) and low priority logical channel for the PDU set type indicating less importance.
  • AM RLC-acknowledge mode
  • UM RLC-unacknowledged mode
  • the gNB-DU will also allocate or determine downlink (DL) TNL information for each F1-U tunnel of each PDU set type.
  • the DL TNL information for each F1-U tunnel of each PDU set type includes first DL TNL information for one PDU set type of the different PDU set types and second DL TNL information for each of remaining PDU set types.
  • the DL TNL information for each F1-U tunnel of each PDU set types also includes each DL TNL information for each PDU set type of the different PDU set types.
  • the DL TNL information for each F1-U tunnel of each PDU set type may include: the DL TNL information for the PDU set type indicating high importance and the DL TNL information for the PDU set type indicating less importance.
  • the corresponding DL TNL information is the DU endpoint of the corresponding F1-U tunnel for delivery of DL PDU sets, which may contain a transport layer address (e.g., an IP address) and a GTP TEID.
  • the gNB-DU will transmit DRB to setup information, e.g., DRB to Setup IE to the gNB-CU in step 607.
  • the DL TNL information for each F1-U tunnel of each PDU set type may be included in the DRB to setup information to the gNB-CU in step 607.
  • the DRB to setup information may be included in a UE CONTEXT SETUP RESPONSE message in response to the UE CONTEXT SETUP REQUEST message, or in a UE CONTEXT MODIFICATION RESPONSE message in response to the UE CONTEXT MODIFICATION REQUEST message.
  • the gNB-DU may separately transmit the DL TNL information for a corresponding F1-U tunnel of a PDU set type, for example, separately transmitting the first DL TNL information and the second DL TNL information to the gNB-CU.
  • the gNB-CU will map the plurality of PDU sets to the setup DRB in the SDAP entity. After processing by the PDCP entity, the gNB-CU sends PDCP PDUs of the plurality of PDU sets to the gNB-DU via different F1-U tunnels correspondingly.
  • a traffic e.g., XR services
  • the gNB-CU will send the PDCP PDUs of PDU Set 1 via F1-U tunnel 1 to the gNB-DU while send PDCP PDUs of PDU Set 2 via F1-U tunnel 2 to the gNB-DU.
  • the gNB-DU will identify the PDU sets with different types according to the F1-U tunnels and map the received PDCP PDUs to the corresponding RLC entity and logical channel for transmitting data to corresponding UE.
  • the gNB-DU transmits PDCP PDUs of the plurality of PDU sets to the gNB-CU via different F1-U tunnels.
  • a traffic e.g., XR services
  • the gNB-DU will send the PDCP PDUs of PDU Set 1, e.g., identified by LCID 1 via F1-U tunnel 1 to the gNB-CU while sends PDCP PDUs of PDU Set 2, e.g., identified by LCID 2 via F1-U tunnel 2 to the gNB-CU.
  • FIG. 7 is a flow chart illustrating a method of data transmission in Scenario 1 according to some other embodiments of the present application, wherein a plurality of F1-U tunnels are provided for the new type DRB.
  • the CU of a RAN node e.g., a gNB-CU is separated into a CU-CP and at least one CU-UP coupled to the CU-CP (only one is illustrated as an example) .
  • the method is illustrated in a system level between the CU of the RAN node e.g., a gNB-CU and a DU coupled to the CU, e.g., a gNB-DU
  • persons skilled in the art should understand that the method implemented in the CU and the DU can be separately implemented and/or incorporated by other apparatus with the like functions.
  • the CU-CP will determine whether to apply the new bearer type for a DRB in step 701. For example, the CU-CP may decide to apply the new bearer type for the DRB in response to QoS flow information or QoS parameters of PDU sets from the CN.
  • the CU-CP will send a new bearer type indication to the CU-UP over E1 interface, e.g., included in DRB to Be Setup IE or the like, via a BEARER CONTEXT SETUP REQUEST message.
  • the CU-CP may also transmit PDU set type information indicating different PDU set types carried by the DRB to the CU-UP, e.g., also included in the DRB to Be Setup IE or the like.
  • the CU-UP After receiving the new bearer type indication and PDU set type information, the CU-UP will allocate UL TNL information for each F1-U tunnel of each PDU set type as stated in FIG. 6. The CU-UP will send the UL TNL information for each F1-U tunnel of each PDU set type to the CU-CP in step 703b, e.g., via a BEARER CONTEXT SETUP RESPONSE message in response to the BEARER CONTEXT SETUP REQUEST message.
  • step 705 the CU-CP will transmit DRB to be setup information, e.g., DRB to Be Setup IE to the DU, which is identical or similar to step 603.
  • the DU will allocate parameters for the new bearer type DRB in step 707.
  • the DU will also allocate DL TNL information for each F1-U tunnel of each PDU set type.
  • the DU will transmit DRB to setup information, e.g., DRB to Setup IE to the CU-CP in step 709, and the DL TNL information for each F1-U tunnel of each PDU set type may also be included in the DRB to setup information.
  • setup information e.g., DRB to Setup IE to the CU-CP in step 709
  • the DL TNL information for each F1-U tunnel of each PDU set type may also be included in the DRB to setup information.
  • the CU-CP After receiving the DL TNL information for each F1-U tunnel of each PDU set type from the DU, the CU-CP will transmit it to the CU-UP in step 711, e.g., via a BEARER CONTEXT MODIFY REQUEST message.
  • the CU-UP will map the different types of PDU sets to one DRB in SDAP entity. After processing by one PDCP entity, the CU-UP will send PDCP PDUs of the plurality of PDU sets to the DU via different F1-U tunnels correspondingly.
  • a traffic e.g., XR services
  • the CU-UP will send the PDCP PDUs of PDU Set 1 via F1-U tunnel 1 to the DU while send PDCP PDUs of PDU Set 2 via F1-U tunnel 2 to the DU.
  • the DU will identify the PDU sets with different types according to the F1-U tunnels and map the received PDCP PDUs to the corresponding RLC entity and logical channel for transmitting data to corresponding UE.
  • the DU In the case of receiving a plurality of PDU sets with the different PDU set types belonging to a traffic (e.g., XR services) from a UE, the DU will transmit PDCP PDUs of the plurality of PDU sets to the CU-UP via different F1-U tunnels.
  • a traffic e.g., XR services
  • the gNB-DU will send the PDCP PDUs of PDU Set 1, e.g., identified by LCID 1 via F1-U tunnel 1 to the CU-UP while send PDCP PDUs of PDU Set 2, e.g., identified by LCID 2 via F1-U tunnel 2 to the CU-UP.
  • FIG. 8 is a flow chart illustrating a method of data transmission in Scenario 2 according to some embodiments of the present application, wherein a plurality of F1-U tunnels are provided for a new type DRB.
  • the method is illustrated in a system level between the CU of the RAN node, e.g., a gNB-CU and a DU coupled to the CU, e.g., a gNB-DU
  • the method implemented in the CU and the DU can be separately implemented and/or incorporated by other apparatus with the like functions.
  • the gNB-CU will send DRB to be setup information, e.g., DRB to Be Setup IE to a gNB-DU coupled to the gNB-CU in step 801.
  • the DRB to be setup information may be included in a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message or the like.
  • the DRB to be setup information may include PDU set type information indicating different PDU set types carried by the DRB.
  • exemplary PDU set type information may indicate: PDU set type 1 and PDU set type 2, wherein, PDU set type 1 indicates PDU set (s) with high importance, and PDU set type 2 indicates PDU set (s) with less importance.
  • exemplary PDU set type information may indicate: PDU set (s) with high importance, PDU set (s) with less importance or the like.
  • the PDU set type indicating high importance is defined as primary PDU set, while the PDU set type indicating less importance is called as secondary PDU set, and thus exemplary PDU set type information may indicate: primary PDU set and secondary PDU set.
  • the gNB-DU After receiving the PDU set type information from the gNB-CU, e.g., indicated in the DRB to be setup information, the gNB-DU will decide whether to apply the new bearer type for the DRB according to the PDU set type information in step 803.
  • the gNB-DU will allocate related parameters for the new type DRB similar to step 605. For example, considering two PDU set types, the gNB-DU allocates two RLC entities and two logical channels (or LCID) for the new type DRB, each RLC entity and logical channel (or LCID) is for a corresponding PDU set type. The modes of the RLC entities and the priorities of the logical channels will be configured according to the PDU set type information. For example, the gNB-DU may allocate RLC-AM and high priority logical channel for the PDU set type indicating high importance, while allocate RLC-UM and low priority logical channel for the PDU set type indicating less importance.
  • the gNB-DU will transmit DRB to setup information, e.g., DRB to Setup IE for the new DRB setup to the gNB-CU.
  • the DRB to setup information may be included in a UE CONTEXT SETUP RESPONSE message or a UE CONTEXT MODIFICATION RESPONSE message or the like.
  • Exemplary DRB to setup information may include a new bearer type indication in an explicit or implicit manner.
  • the exemplary DRB to setup information may also include allocated LCID for each PDU set type.
  • the gNB-CU After receiving the new bearer type indication from the gNB-DU, the gNB-CU will trigger an F1-U tunnel setup for the new type DRB.
  • the gNB-CU will send the UL TNL information for each F1-U tunnel of each PDU set type to the gNB-DU, e.g., via a UE CONTEXT MODIFICATION REQUEST message.
  • the UL TNL information for each F1-U tunnel of each PDU set type includes the UL TNL information for the PDU set type indicating high importance and the UL TNL information for the PDU set type indicating less importance.
  • the gNB-CU may also include the LCIDs, each LCID corresponding to each UL TNL information used for a F1-U tunnel of a corresponding PDU set type.
  • the UL TNL information for a corresponding PDU set type may be identified in other manners, e.g., directly indicating the specific PDU set type for which the UL TNL information is used.
  • the UL TNL information for each F1-U tunnel of each PDU set type may be transmitted in other manners besides the above illustrated manner.
  • the gNB-CU may separately transmit first UL TNL information for one PDU set type of the different PDU set types and second UL TNL information for each of remaining PDU set types to the gNB-DU.
  • the first UL TNL information may be transmitted with the PDU set type information, and the second UL TNL information may be transmitted after receiving the new bearer type indication.
  • the gNB-CU may transmit the first UL TNL information in the DRB to be setup information in step 801 as legacy, and after receiving the new bearer type indication, the gNB-CU will transmit the second UL TNL information to the gNB-DU in step 807.
  • the gNB-DU may indicate to gNB-CU that the first UL TNL information is used for which PDU set type in the setup 805.
  • the gNB-DU will provide DL TNL information for each F1-U tunnel of each PDU set type to the gNB-CU, e.g., via a UE CONTEXT MODIFICATION RESPONSE message.
  • the DL TNL information for each F1-U tunnel of each PDU set type may include: the DL TNL information for the PDU set type indicating high importance and the DL TNL information for the PDU set type indicating less importance.
  • the gNB-CU may also include the LCIDs, each LCID corresponding to each DL TNL information used for a corresponding PDU set type.
  • the DL TNL information for a corresponding PDU set type may be identified in other manners, e.g., directly indicating the specific PDU set type for which the DL TNL information is used.
  • the DL TNL information for each F1-U tunnel of each PDU set type may be transmitted in other manners.
  • the gNB-DU may transmit the DL TNL information for each F1-U tunnel of each PDU set type with the new bearer type indication to the gNB-CU in step 805.
  • the gNB-DU may separately transmit first DL TNL information for one PDU set type of the different PDU set types and second DL TNL information for each of remaining PDU set types to the gNB-DU.
  • the first DL TNL information is transmitted with the new indication
  • the second DL TNL information is transmitted after receiving the second UL TNL information.
  • the gNB-DU may transmit the first DL TNL information in the DRB to setup information in step 805 as legacy, and after receiving the UL TNL information for each F1-U tunnel of each PDU set type or after separately receiving the second UL TNL information, the gNB-DU will transmit the second DL TNL information to the gNB-CU in step 809.
  • step 811 After the new type DRB is setup, data transmission will be performed over the F1 interface in the step 811, which is similar to step 609 and thus will not repeat.
  • FIG. 9 is a flow chart illustrating a method of data transmission in Scenario 2 according to some other embodiments of the present application, wherein a plurality of F1-U tunnels are provided for the new type DRB.
  • the CU of a RAN node e.g., a gNB-CU is separated into a CU-CP and at least one CU-UP coupled to the CU-CP (only one is illustrated as an example) .
  • the method is illustrated in a system level between the CU of the RAN node e.g., a gNB-CU and a DU coupled to the CU, e.g., a gNB-DU
  • persons skilled in the art should understand that the method implemented in the CU and the DU can be separately implemented and/or incorporated by other apparatus with the like functions.
  • steps 901, 901 and 905 are identical or similar to steps 801, 803 and 805 in FIG. 8
  • steps 909 and 911 are identical or similar to steps 807 and 809
  • step 915 is identical or similar to step 811, and thus will not repeat.
  • communication between the CU-CP and CU-UP it will be illustrated in the following.
  • the CU-CP will send the new bearer type indication to the CU-UP over E1 interface, e.g., included in DRB to Be Setup IE or the like, via a BEARER CONTEXT SETUP REQUEST message.
  • the CU-CP may also transmit PDU set type information indicating different PDU set types carried by the DRB to the CU-UP, e.g., also included in the DRB to Be Setup IE or the like.
  • the CU-CP may transmit the PDU set type information to the CU-UP before receiving the new bearer type indication.
  • the CU-CP may also send the LCIDs to the CU-UP.
  • the CU-CP will also transmit he DL TNL information for each F1-U tunnel of each PDU set type or only the first DL TNL information to the CU-UP.
  • the CU-UP After receiving the new bearer type indication, the CU-UP will allocate UL TNL information for each F1-U tunnel of each PDU set type similar to that stated in FIG. 6, which may be based on the PDU set type information or LCIDs etc.
  • the CU-UP will send the UL TNL information for each F1-U tunnel of each PDU set type to the CU-CP in step 907b, e.g., via a BEARER CONTEXT SETUP RESPONSE message.
  • the CU-CP may request first UL TNL information as legacy before step 901 so that the first UL TNL information can be transmitted in DRB to be setup information in step 901. Accordingly, the CU-UP may only send the second UL TNL information to the CU-CP in step 907b.
  • the CU-CP After receiving the DL TNL information for each F1-U tunnel of each PDU set type from the DU in step 911, the CU-CP will transmit the DL TNL information for each F1-U tunnel of each PDU set type to the CU-UP in step 913.
  • the CU-UP may only receive the second DL TNL information in step 911, and will send only the second DL TNL information to the CU-UP.
  • FIG. 10 is a flow chart illustrating a method of data transmission in Scenario 1 according to some yet other embodiments of the present application, wherein there is only one F1-U tunnel between the CU and DU corresponding to all the different PDU set types.
  • the method is illustrated in a system level between the CU of the RAN node, e.g., a gNB-CU and a DU coupled to the CU, e.g., a gNB-DU
  • the method implemented in the CU and the DU can be separately implemented and/or incorporated by other apparatus with the like functions.
  • the gNB-CU may decide to apply a new bearer type of a DRB in step 1001 in some cases, e.g., in response to QoS flow information or QoS parameters of PDU sets from the CN.
  • the gNB-CU will send DRB to be setup information, e.g., DRB to Be Setup IE to a gNB-DU coupled to the gNB-CU for setup of the new type DRB.
  • the DRB to be setup information may be included in a UE CONTEXT SETUP REQUEST message or UE CONTEXT MODIFICATION REQUEST message or the like.
  • Exemplary DRB to be setup information may include a new bearer type indication indicating that the new bearer type is applied for the DRB.
  • the exemplary DRB to be setup information may also include PDU set type information, indicating different PDU set types carried by the DRB in various manners.
  • the UL TNL information for the F1-U tunnel to the gNB-DU may also be included in the DRB to be setup information.
  • the gNB-DU After receiving the new bearer type indication, the gNB-DU will be aware that the new type DRB is to be setup.
  • the gNB-DU will allocate related parameters for the new bearer type DRB in step 1005. For example, considering two PDU set types, the gNB-DU allocates two RLC entities and two logical channels (or LCIDs) for the new type DRB, each RLC entity and logical channel (or, LCID) is for a corresponding PDU set type.
  • the modes of the RLC entities and the priorities of the logical channels will be configured according to the PDU set type information.
  • the gNB-DU will also allocate or determine DL TNL information for the F1-U tunnel.
  • the gNB-DU will transmit DRB to setup information, e.g., DRB to Setup IE to the gNB-CU in step 1007.
  • DRB to setup information e.g., DRB to Setup IE
  • the DL TNL information for each F1-U tunnel of each PDU set type may be included in the DRB to setup information.
  • the gNB-CU will map the plurality of PDU sets to the setup DRB in the SDAP entity.
  • the gNB-CU After processing by the PDCP entity, the gNB-CU will send PDCP PDUs of the plurality of PDU sets to the gNB-DU via the only one F1-U tunnel.
  • the gNB-DU will identify the different types of PDU sets according to specific PDU set type indication, which may be included in the header of the common F1-U tunnel. Then, the gNB-DU will map the received PDCP PDUs of PDU sets with different types to the corresponding RLC entities and logical channels for transmitting the data to UE.
  • the gNB-DU will transmit PDCP PDUs of the plurality of PDU sets to the gNB-CU via the only one F1-U tunnels.
  • the flow control information is provided by NR user plane protocol data which is conveyed by GTP-U protocol means, more specifically, by means of the "NR RAN Container" GTP-U extension header as defined in TS 29.281.
  • the flow control information for each PDU set type indicates at least one of the following information: a highest PDCP PDU sequence number successfully delivered in sequence to a UE of a PDU set type; a highest PDCP PDU sequence number transmitted to lower layers of a PDU set type; or a desired buffer size for the PDU set type of the DRB.
  • the flow control information for the new type DRB is indicated in a downlink data delivery status frame with a PDU set type indication, wherein the PDU set type indicates a specific PDU set type, e.g., PDU set type 1 indicating high importance or PDU set type 2 indicating low importance.
  • the flow control information for the new type DRB is provided in a new frame of the NR user plane protocol with a PDU set type indication, wherein the PDU set type indicates a specific PDU set type.
  • flow control information for different PDU set types is provided by different frames of the NR user plane protocol, e.g. the flow control information of PDU set type 1 is provided by frame 1, while the flow control information of PDU set type 2 is provided by frame 2.
  • Table 1 shown below illustrates an exemplary downlink data delivery status frame with a PDU set type indication (hereafter, new downlink data delivery status frame) .
  • the new downlink data delivery status frame includes: "PDU set type indication” with one bit, "desired buffer size for the indicated PDU set type” with one byte; "highest successfully delivered PDCP sequence number for the indicated PDU set type” with one byte; and "highest transmitted PDCP sequence number for the indicated PDU set type” with one byte.
  • all flow control information for different PDU set types carried by a new type DRB can be included in the same downlink data delivery status frame, wherein a plurality of PDU set types can be indicated by the PDU set type indication with one or more bits. For example, two bits can be used for the PDU set type indication, value "00" means PDU set type 1, value "01” means PDU set type 2, and value "10" means both the PDU set type 1 and PDU set type 2.
  • Another related fields associated with each indicated PDU set types e.g., at least one of "desired buffer size for the indicated PDU set type” ; "highest successfully delivered PDCP sequence number for the indicated PDU set type” ; and "highest transmitted PDCP sequence number for the indicated PDU set type” etc. can be further included in sequence in the downlink data delivery status frame similar to those illustrated in Table 1.
  • the gNB-DU when feeding back the flow control information to the gNB-CU, the gNB-DU may only considers the transmission status of one PDU set type, e.g., the PDU set type indicating high importance.
  • FIG. 11 is a block diagram of an apparatus of data transmission according to some embodiments of the present application.
  • the apparatus 1100 may include at least one non-transitory computer-readable medium 1101, at least one receiving circuitry 1102, at least one transmitting circuitry 1104, and at least one processor 1106 coupled to the non-transitory computer-readable medium 1101, the receiving circuitry 1102 and the transmitting circuitry 1104.
  • the apparatus 1100 may be a CU or DU configured to perform a method illustrated in the above or the like.
  • the receiving circuitry 1102 and the transmitting circuitry 1104 can be combined into a single device, such as a transceiver.
  • the processor 1106 may be a central processing unit (CPU) , a digital signaling processing (DSP) , a microprocessor etc.
  • the apparatus 1100 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 1101 may have stored thereon computer-executable instructions to cause the processor 1106 to implement the method with respect to the CU or DU as described above.
  • the computer-executable instructions when executed, cause the processor 1106 interacting with receiving circuitry 1102 and transmitting circuitry 1104, so as to perform the steps with respect to a CU or DU as depicted above.
  • FIG. 12 illustrates a block diagram of an apparatus 1200 of data transmission according to some other embodiments of the present application.
  • the apparatus 1200 e.g., a CU or DU may include at least one processor 1202 and at least one transceiver 1204.
  • the transceiver 1204 may include at least one separate receiving circuitry 1206 and transmitting circuitry 1208, or at least one integrated receiving circuitry 1206 and transmitting circuitry 1208.
  • the at least one processor 1202 may be a CPU, a DSP, a microprocessor etc.
  • the processor may be configured to: determine to apply a first bearer type of a DRB to transmit a plurality of PDU set types; and transmit, to a DU of the RAN node, an indication of the first bearer type of the DRB, and PDU set type information associated with different PDU set types; wherein, the first bearer type of the DRB is served by a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • the processor may be configured to: transmit, to a DU of the RAN node, PDU set type information associated with a plurality of PDU set types; and receive, from the DU, an indication of a first bearer type of a DRB; wherein the first bearer type of the DRB is associated with a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • the processor may be configured to: receive, from a CU of the RAN node, PDU set type information associated with a plurality of PDU set types; determine to apply a first bearer type of a DRB for a plurality of PDU set types; and transmit, to the CU, an indication of the first bearer type of the DRB; wherein the first bearer type of the DRB is associated with a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types.
  • the processor may be configured to: receive, from a CU of the RAN node, an indication of a first bearer type of a DRB and PDU set type information associated with different PDU set types, wherein, the first bearer type of the DRB is served by a plurality of logical channels, and each logical channel is for transmitting a respective one of the PDU set types; and allocate different logical channels for different PDU set types based on the indication of the first bearer type of the DRB and the PDU set type information.
  • the method according to embodiments of the present application can also be implemented on a programmed processor.
  • the controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device capable of implementing the flowcharts shown in the figures may be used to implement the processor functions of this application.
  • an embodiment of the present application provides an apparatus including a processor and a memory. Computer programmable instructions for implementing a method stored in the memory, and the processor is configured to perform the computer programmable instructions to implement the method.
  • the method may be a method as stated above or other method according to an embodiment of the present application.
  • An alternative embodiment preferably implements the methods according to embodiments of the present application in a non-transitory, computer-readable storage medium storing computer programmable instructions.
  • the instructions are preferably executed by computer-executable components preferably integrated with a network security system.
  • the non-transitory, computer-readable storage medium may be stored on any suitable computer readable media such as random access memory (RAMs) , read only memory (ROMs) , flash memory, electrically erasable programmable read only memory (EEPROMs) , optical storage devices (compact disc (CD) or digital video disc (DVD) ) , hard drives, floppy drives, or any suitable device.
  • the computer-executable component is preferably a processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device.
  • an embodiment of the present application provides a non-transitory, computer-readable storage medium having computer programmable instructions stored therein.
  • the computer programmable instructions are configured to implement a method as stated above or other method according to an embodiment

Landscapes

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

Abstract

Des modes de réalisation de la présente demande concernent un procédé et un appareil de transmission de données. Un procédé donné à titre d'exemple consiste à : déterminer s'il convient d'appliquer un premier type de support d'un DRB pour transmettre une pluralité de types d'ensemble de PDU, p. ex. par une CU ; et transmettre, à une DU couplée à la CU, une indication du premier type de support du DRB, et des informations de type d'ensemble de PDU associées à différents types d'ensemble de PDU ; le premier type de support du DRB étant desservi par une pluralité de canaux logiques, et chaque canal logique étant destiné à transmettre un type respectif des types d'ensemble de PDU.
PCT/CN2022/131431 2022-11-11 2022-11-11 Procédé et appareil de transmission de données WO2024082361A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/131431 WO2024082361A1 (fr) 2022-11-11 2022-11-11 Procédé et appareil de transmission de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/131431 WO2024082361A1 (fr) 2022-11-11 2022-11-11 Procédé et appareil de transmission de données

Publications (1)

Publication Number Publication Date
WO2024082361A1 true WO2024082361A1 (fr) 2024-04-25

Family

ID=90736698

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/131431 WO2024082361A1 (fr) 2022-11-11 2022-11-11 Procédé et appareil de transmission de données

Country Status (1)

Country Link
WO (1) WO2024082361A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020030154A1 (fr) * 2018-08-10 2020-02-13 华为技术有限公司 Procédé et dispositif de notification, et système de communication
CN111757347A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 确定承载类型的方法和通信装置
WO2022010287A1 (fr) * 2020-07-10 2022-01-13 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception de signaux dans un système de communication sans fil

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020030154A1 (fr) * 2018-08-10 2020-02-13 华为技术有限公司 Procédé et dispositif de notification, et système de communication
CN111757347A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 确定承载类型的方法和通信装置
WO2022010287A1 (fr) * 2020-07-10 2022-01-13 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception de signaux dans un système de communication sans fil

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on XR enhancements for NR (Release 18)", 3GPP TR 38.835, no. V0.3.1, 4 November 2022 (2022-11-04), pages 1 - 19, XP052211717 *
LIANHAI WU, LENOVO: "Discussion on PDU sets and data burst awareness in RAN", 3GPP TSG-RAN WG2 MEETING #120, R2-2212039, 4 November 2022 (2022-11-04), XP052216128 *

Similar Documents

Publication Publication Date Title
US10972935B2 (en) Method for performing reflective quality of service (QoS) in wireless communication system and a device therefor
KR102265907B1 (ko) 무선 통신 시스템에서 서비스 품질 (QoS) 구조 기반으로 상향링크 패킷을 전송하는 방법 및 이를 위한 장치
US12021954B2 (en) Method and device for sending and receiving data packet, and data packet transmission system
US10680967B2 (en) Method for handling state variables of a PDCP entity in wireless communication system and a device therefor
US10721754B2 (en) Data transmission method and apparatus
US11064557B2 (en) Method and device for establishing radio resource control connection
US11343703B2 (en) Method for performing reflective quality of service in wireless communication system and a device therefor
KR20190017663A (ko) 무선 통신 시스템에서의 um rlc 엔터티와 관련된 pdcp 엔터티의 재구성을 위한 방법 및 그 장치
CN110476451B (zh) 在无线通信系统中基于服务质量(qos)框架发送无损数据分组的方法及其装置
CN110352610B (zh) 在无线通信系统中发送tcp ack分组的方法及其装置
US11968565B2 (en) User plane information reporting method and apparatus
CN108337633B (zh) 数据分流配置方法、基站系统和用户终端
CN111263416A (zh) 切换的方法和设备
WO2018127018A1 (fr) Procédé et dispositif de communication à liaisons multiples, et terminal
US20230116578A1 (en) Data transmission method and apparatus
US20240031870A1 (en) Media data transmission method and communication apparatus
US20230141231A1 (en) Mobile Edge Computing Processing Method and Related Device
CN111757347B (zh) 确定承载类型的方法和通信装置
US20230254729A1 (en) Migration method and apparatus for iab-node
WO2024082361A1 (fr) Procédé et appareil de transmission de données
US20220191951A1 (en) Method and apparatus for establishing radio bearer
US20240236619A1 (en) Method and apparatus for multicast and broadcast services
WO2024087585A9 (fr) Procédé et appareil de transmission de données utilisant des temporisateurs de rejet d'ensemble d'unités de données de protocole
WO2022041127A1 (fr) Procédé et appareil de services de multidiffusion et de radiodiffusion
US20240031065A1 (en) Communication method and communication apparatus

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22962540

Country of ref document: EP

Kind code of ref document: A1