WO2024065215A1 - Procédé de transmission de volume de données, appareil et support de stockage lisible - Google Patents

Procédé de transmission de volume de données, appareil et support de stockage lisible Download PDF

Info

Publication number
WO2024065215A1
WO2024065215A1 PCT/CN2022/121872 CN2022121872W WO2024065215A1 WO 2024065215 A1 WO2024065215 A1 WO 2024065215A1 CN 2022121872 W CN2022121872 W CN 2022121872W WO 2024065215 A1 WO2024065215 A1 WO 2024065215A1
Authority
WO
WIPO (PCT)
Prior art keywords
type
entity
data
rlc entity
pdcp
Prior art date
Application number
PCT/CN2022/121872
Other languages
English (en)
Chinese (zh)
Inventor
李艳华
吴昱民
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280003623.7A priority Critical patent/CN116097726A/zh
Priority to PCT/CN2022/121872 priority patent/WO2024065215A1/fr
Publication of WO2024065215A1 publication Critical patent/WO2024065215A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular to a method, device and readable storage medium for sending data volume.
  • the fifth-generation (5G) wireless communication system it is necessary to support the extended reality (XR) service type.
  • XR extended reality
  • QoS Quality of Service
  • NAS non-access stratum
  • RAN radio access network
  • the present disclosure provides a method, an apparatus, and a readable storage medium for sending data volume.
  • the present disclosure provides a method for sending data volume, the method comprising:
  • a PDCP entity sends a data packet of a first service to at least one type of radio link control RLC entity
  • the PDCP entity sends a data volume of data to be transmitted to a media access control MAC entity associated with the at least one type of RLC entity.
  • the service data in the scenario of transmitting the first service data, is diverted and sent through the PDCP layer, and in combination with at least one type of diverted RLC entity, the data volume of the data to be transmitted is reported to the associated MAC entity, so as to provide an effective way to report the data volume in the XR service diversion scenario.
  • the PDCP entity sends the amount of data to be transmitted to a media access control MAC entity associated with at least one type of RLC entity, including:
  • the PDCP entity sends the data volume to the MAC entity associated with at least one RLC entity of the corresponding type according to the type of the at least one type of RLC entity.
  • the PDCP entity determines the type of the at least one type of RLC entity, including:
  • the PDCP entity determines the type of the at least one type of RLC entity according to the attribute information of the data packet, wherein each type of RLC entity is used to transmit the data packet with corresponding attribute information.
  • the PDCP entity determines the type of the at least one type of RLC entity according to the attribute information of the data packet, including:
  • the PDCP entity determines attribute information of the data packet according to a first field in the data packet
  • the PDCP entity determines the type of the at least one RLC entity according to the attribute information.
  • the attribute information of the data packet includes one of the following:
  • the priority level of the data packet is the priority level of the data packet
  • the processing level of the data packet is the processing level of the data packet.
  • the PDCP entity sending the amount of data to be transmitted to the MAC entity associated with at least one RLC entity in the corresponding type of RLC entity includes:
  • the PDCP entity determines a data amount of data to be transmitted for each type of data packet
  • the PDCP entity sends the data volume to the MAC entity associated with at least one RLC entity of the corresponding type.
  • the PDCP entity sends the amount of data to be transmitted to a media access control MAC entity of the user equipment associated with at least one RLC entity, including:
  • the PDCP entity sends the data volume to the MAC entity associated with the first RLC entity and the MAC entity associated with the second RLC entity.
  • the method further includes:
  • the MAC entity sends a buffer status report BSR to the network device according to the amount of received data.
  • the present disclosure provides a user equipment, wherein the user equipment includes: a PDCP entity.
  • the PDCP entity is configured to send the data volume of the to-be-transmitted data to the media access control MAC entity associated with the at least one type of RLC entity in a scenario where the PDCP entity sends a data packet of the first service to at least one type of RLC entity.
  • the present disclosure provides a communication device, comprising a processor and a memory; the memory is used to store a computer program; the processor is used to execute the computer program to implement the first aspect or any possible design of the first aspect.
  • the present disclosure provides a computer-readable storage medium, which stores instructions (or computer programs, programs), which, when called and executed on a computer, enable the computer to execute the above-mentioned first aspect or any possible design of the first aspect.
  • FIG1 is a schematic diagram of a communication system architecture provided by an embodiment of the present disclosure.
  • FIG2 is a schematic diagram of a protocol layer structure provided by an embodiment of the present disclosure.
  • FIG3 is a flow chart showing a method for sending a data volume and a buffer status report according to an exemplary embodiment
  • FIG4 is a flow chart showing a method for sending data volume according to an exemplary embodiment
  • FIG5 is a flow chart showing another method for sending data volume according to an exemplary embodiment
  • FIG6 is a flow chart showing another method for sending data volume according to an exemplary embodiment
  • FIG7 is a flow chart showing a method for sending a cache status report according to an exemplary embodiment
  • FIG8 is a structural diagram of a device for sending data volume according to an exemplary embodiment
  • Fig. 9 is a block diagram of a user equipment according to an exemplary embodiment.
  • first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • the words "if” and “if” as used herein may be interpreted as “at” or "when” or "in response to determination".
  • the wireless communication system 100 includes a user device 101, a radio access network (RAN) device 102 or a network device 102, and a core network (CN) device 103.
  • RAN radio access network
  • CN core network
  • the user equipment 101 can access the wireless network to obtain services of the external network (such as the Internet) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other user equipment.
  • the wireless network includes: a RAN device 102 or a network device 102, and a CN device 103, wherein the RAN device 102 is used to access the user equipment 101 to the wireless network, and the CN device 103 is used to manage the user equipment 101 and provide a gateway for communicating with the external network.
  • the number of each device in the communication system shown in FIG1 is only for illustration, and the embodiment of the present application is not limited thereto. In actual applications, the communication system may also include more user equipment, more RAN devices, and other devices.
  • the user equipment 101 is configured to support carrier aggregation and can be connected to multiple carrier components of the network device 102, including a primary carrier component and one or more secondary carrier components.
  • the CN device 103 may include: an access and mobility management function (Access and Mobility Management Function, AMF) entity, a session management function (Session Management Function, SMF), a user plane function (User Plane Function, UPF) entity, a policy and charging function (Policy and charging function, PCF) device, a network exposure function (Network Exposure Function, NEF) device, an application function (Application Function, AF) device, etc.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • Policy and charging function Policy and charging function
  • PCF Policy and charging function
  • NEF Network Exposure Function
  • Application Function Application Function
  • the application scenarios of the wireless communication system 100 include, but are not limited to, long-term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, worldwide interoperability for microwave access (WiMAX) communication system, cloud radio access network (CRAN) system, future fifth-generation (5G) system, new radio (NR) communication system or future evolved public land mobile network (PLMN) system, etc.
  • LTE long-term evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • WiMAX worldwide interoperability for microwave access
  • CDRF cloud radio access network
  • 5G fifth-generation
  • NR new radio
  • PLMN future evolved public land mobile network
  • the user equipment 101 shown above may be a terminal, an access terminal, a terminal unit, a terminal station, a mobile station (MS), a remote station, a remote terminal, a mobile terminal, a wireless communication device, a terminal agent or a terminal device, etc.
  • the user equipment 101 may have a wireless transceiver function, and it can communicate with one or more network devices of one or more communication systems (such as wireless communication) and receive network services provided by the network devices, where the network devices include but are not limited to the network device 102 shown in the figure.
  • the user equipment 101 can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network, or a terminal device in a future evolved PLMN network, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the network device 102 or RAN device 102 may specifically include a base station (BS), or include a base station and a radio resource management device for controlling the base station.
  • the network device 102 may also include a relay station (relay device), an access point, a base station in a future 5G network, a base station in a future evolved PLMN network, or an NR base station.
  • the network device 102 may be a wearable device or an in-vehicle device.
  • the network device 102 may also be a communication chip with a communication module.
  • the network device 102 includes, but is not limited to, a next-generation base station (gnodeB, gNB) in 5G, an evolved node B (evolved node B, eNB) in an LTE system, a radio network controller (radio network controller, RNC), a node B (node B, NB) in a WCDMA system, a wireless controller under a CRAN system, a base station controller (basestation controller, BSC), a base transceiver station (base transceiver station, BTS) in a GSM system or a CDMA system, a home base station (for example, home evolved nodeB, or home node B, HNB), a baseband unit (baseband unit, BBU), a transmitting point (transmitting and receiving point, TRP), a transmitting point (transmitting point, TP) or a mobile switching center, etc.
  • a next-generation base station gNB
  • eNB evolved node B
  • RNC radio network controller
  • FIG2 is a schematic diagram of a protocol layer structure according to an embodiment of the present disclosure.
  • the control plane protocol layer structure may include functions of protocol layers such as the Radio Resource Control (RRC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the Physical Layer (PHY).
  • the user plane protocol layer structure may include functions of protocol layers such as the PDCP layer, the RLC layer, the MAC layer, and the Physical Layer.
  • RAN and UPF are generally referred to as user-layer network function entities.
  • the data traffic of the user equipment can be transmitted through the packet data unit (PDU) session (Session) established between the user equipment and the application layer equipment.
  • PDU packet data unit
  • Session packet data unit
  • the transmission will pass through the two network function devices, RAN and UPF; the other parts are called control-layer network functions and entities, which are mainly responsible for authentication and authorization, registration management, session management, mobility management, and policy control, so as to achieve reliable and stable transmission of user-layer traffic.
  • FIG. 3 is a method for sending a data volume and a cache status report according to an exemplary embodiment. As shown in FIG. 3 , the method includes steps S301 to S302, specifically:
  • Step S301 in a scenario where a PDCP entity sends a first service to at least one type of radio link control RLC entity, the PDCP entity sends a data volume of data to be transmitted to a media access control MAC entity associated with at least one type of RLC entity.
  • the radio bearer RB of the first service is associated with the PDCP entity.
  • Step S302 The MAC entity sends a buffer status report BSR to the network device 102 according to the amount of received data.
  • the PDCP layer and the MAC layer are sublayers of the data link layer configured in the user equipment 101 .
  • the PDCP layer may receive a data packet of the first service from a higher layer, and perform traffic diversion according to the received data packet and send the data packet to at least one type of RLC entity.
  • the at least one type of RLC entity may be one or two types of RLC entities, and each type of RLC entity includes at least one RLC entity.
  • the first service is an XR service, which includes a real and virtual combined environment and a human-computer interaction service generated by computer technology and wearable devices.
  • XR includes augmented reality (AR), virtual reality (VR), and cloud gaming, etc.
  • one XR service RB corresponds to one PDCP entity.
  • the one PDCP entity is associated with at least one type of RLC entity. It can be understood that the PDCP layer can pre-configure the association relationship, which can be seen in the description of the following embodiment for details.
  • the amount of data to be transmitted reflects the amount of uplink data to be sent, and the UE may report a BSR to the network device 102 based on the amount of data so that the network device schedules resource blocks for the UE based on the amount of data.
  • the manner in which the PDCP layer reports the amount of data to the MAC layer is related to the manner in which the PDCP layer performs data diversion. For example, when the PDCP layer diverts data packets to two RLC entities, the amount of data sent to the MAC entities associated with the two RLC entities needs to be considered when reporting the amount of data to be transmitted.
  • the PDCP layer of the UE diverts the data of the XR service, and in combination with at least one type of RLC entity in transmission, reports the data volume of the data to be transmitted to its associated MAC entity, thereby realizing effective data volume reporting in the scenario of XR service diversion, which is beneficial for the user equipment to complete BSR reporting.
  • FIG. 4 is a method for sending data volume according to an exemplary embodiment. As shown in FIG. 4 , the method includes step S401, specifically:
  • Step S401 in a scenario where a PDCP entity sends a data packet of a first service to at least one type of radio link control RLC entity, the PDCP entity sends a data volume of data to be transmitted to a media access control MAC entity associated with at least one type of RLC entity.
  • the radio bearer RB of the first service is associated with the PDCP entity.
  • the PDCP layer may split the data of the first service received from the higher layer, and send the data to at least one type of RLC entity.
  • the first service is an XR service.
  • At least one type of RLC entity may be one type or more than one type of RLC entity, and each type of RLC entity includes at least one RLC entity.
  • the type of RLC entity is related to the service type and configuration, and data of one service type may be configured with one or two types of RLC entities. For example, for data of the first service type, a first type of RLC entity and a second type of RLC entity may be configured for it. After the type of the RLC entity is configured, it has an association relationship with the service data.
  • RLC includes three transmission modes: transparent transmission mode (TM), unacknowledged transmission mode (UM) and acknowledged transmission mode (AM). Therefore, the RLC entities included in each category of RLC entities may be TM RLC entities, UM RLC entities or AM RLC entities.
  • the target type RLC entity to which the traffic is diverted only includes one RLC entity, for example, for UM bidirectional transmission, the one RLC entity is a UM RLC entity, for UM unidirectional transmission, the one RLC entity is a UM RLC entity for each transmission direction (uplink and downlink), or for AM mode, the one RLC entity is an AM RLC entity, then PDCP delivers the data packet to this one RLC entity.
  • the PDCP layer when there is more than one type of RLC entity associated with the PDCP, the PDCP layer offloads data to the more than one type of RLC entity, which may be based on the importance or attribute information of the data packet.
  • the PDCP layer reports the amount of data to be transmitted to the MAC layer in combination with the type of the RLC entity.
  • the attribute information of the data packet may be the type, priority level, or processing level of the data packet.
  • the XR service data in the scenario of transmitting XR service data, is diverted and sent through the PDCP layer, and in combination with at least one type of diverted RLC entity, the data volume of the data to be transmitted is reported to the associated MAC entity, so as to provide an effective way to report the data volume in the XR service diversion scenario, so that the user equipment can effectively report the BSR to the network equipment.
  • FIG. 5 is a method for sending data volume according to an exemplary embodiment. As shown in FIG. 5 , the method includes steps S501 to S502, specifically:
  • Step S501 In a scenario where a PDCP entity sends a data packet of a first service to at least one type of radio link control RLC entity, the PDCP entity determines a type of at least one type of RLC entity.
  • Step S502 The PDCP entity sends the data volume of the to-be-transmitted data to the MAC entity associated with at least one RLC entity in the corresponding type of RLC entity according to the type of at least one type of RLC entity.
  • the first service is an XR service.
  • the data to be transmitted by the PDCP layer includes PDCP control data (PDCP Control PDU) and PDCP data protocol data unit (PDCP Data PDU).
  • PDCP Control PDU is the data generated by the PDCP layer
  • PDCP Data PDU is the data packet received by the PDCP layer from the upper layer.
  • PDCP control data is sent to the first RLC, which may be a primary RLC entity or a specific RLC entity specified by the network.
  • PDCP Data PDUs may be sent to more than one RLC entity, so the PDCP layer needs to combine different types of RLC entities for statistics during the statistical process.
  • the type of at least one type of RLC entity is related to the attribute information of the data packet. By knowing the type of the RLC entity, relevant information of the data packet sent to the RLC entity can be known, which facilitates the statistics of the data volume to be transmitted.
  • the PDCP layer may report the amount of data to be transmitted at at least one RLC entity according to the type of RLC entity in the offloading process.
  • the embodiment of the present disclosure provides a method for sending data volume, which is executed by the user equipment 101.
  • the method includes steps S501' to S502, specifically:
  • Step S501' in the scenario where the PDCP entity sends a data packet of the first service to at least one type of radio link control RLC entity, the PDCP entity determines the type of at least one type of RLC entity based on the attribute information of the data packet, wherein each type of RLC entity is used to transmit a data packet with corresponding attribute information.
  • Step S502 The PDCP entity sends the data volume of the to-be-transmitted data to the MAC entity associated with at least one RLC entity in the corresponding type of RLC entity according to the type of at least one type of RLC entity.
  • the first service is an XR service.
  • the attribute information of the data packet includes one of the following:
  • the priority level of the data packet is the priority level of the data packet
  • the processing level of the data packet is the processing level of the data packet.
  • the attribute information of the data packet may be used to distinguish business data of different business types.
  • the types of data packets include, for example, intra-coded picture (I frame) and predictive-frame (P frame), i.e., I frame and P frame.
  • I frame is a key frame.
  • P frame predictive-frame
  • the priority of the data packet includes, for example, high priority and low priority.
  • the type of RLC entity and the priority of the data packet, and each type of RLC entity is used to transmit a data packet of a corresponding priority level.
  • the processing level of the data packet includes, for example, a first processing level and a second processing level.
  • the data packets may also be classified by flow or sub-flow, such as the first sub-flow data packet (sub-flow1) and the second sub-flow data packet (sub-flow2).
  • the three data packet attribute information namely, the type, priority level and processing level of the data packet.
  • the I frame in the type corresponds to the high priority in the priority level and the first processing level in the processing level, indicating higher data reliability and higher importance.
  • the P frame in the type corresponds to the low priority in the priority level and the second processing level in the processing level, and is less important than the I frame.
  • the type of data packet is used as an example for description.
  • the RLC entity associated with it is a first-type RLC entity.
  • the first-type RLC entity is used to transmit the I frame data packet.
  • the first-type RLC entity includes at least one RLC entity, and the at least one RLC entity is associated with a corresponding MAC entity. Therefore, the amount of data to be transmitted of the I frame data packet is counted, and the MAC entity associated with at least one RLC entity of the first-type RLC entity is notified.
  • the RLC entity associated with it is a second type RLC entity.
  • the second type RLC entity is used to transmit the P frame data packet.
  • the second type RLC entity includes at least one RLC entity, and the at least one RLC entity is associated with a corresponding MAC entity. Therefore, the data volume of the data to be transmitted of the P frame data packet is counted, and the MAC entity associated with at least one RLC entity of the second type RLC entity is notified.
  • association between the attribute information of the data packet and the RLC entity may be pre-configured, as described in the following embodiment.
  • the RLC entity associated with the data packet is determined in combination with the attribute information of the data packet, and the data volume of the to-be-transmitted data of the RLC entity is reported in a classified manner.
  • the embodiment of the present disclosure provides a method for sending data volume, which is executed by the user equipment 101.
  • the method includes steps S501' to S502, specifically:
  • Step S501' in a scenario where the PDCP entity sends a data packet of a first service to at least one type of radio link control RLC entity, the PDCP entity determines attribute information of the data packet based on a first field in the data packet.
  • step S501 the PDCP entity determines the type of at least one type of RLC entity according to the attribute information of the data packet, wherein each type of RLC entity is used to transmit the data packet with corresponding attribute information.
  • Step S502 The PDCP entity sends the data volume of the to-be-transmitted data to the MAC entity associated with at least one RLC entity in the corresponding type of RLC entity according to the type of at least one type of RLC entity.
  • the first service is an XR service.
  • the attribute information of the data packet includes one of the following: the type of the data packet; the priority level of the data packet; and the processing level of the data packet.
  • the first field is a newly added field in the data packet PDCP Data PDU, used to indicate attribute information of the data packet.
  • the first field is a newly added field in the GPRS Tunnelling Protocol for the user plane (GTP-U) packet header at the user level, which is used to indicate the attribute information of the data packet.
  • GTP-U GPRS Tunnelling Protocol for the user plane
  • the attribute information of a data packet is described as the type of the data packet as an example, and the first field indicates that the type of the data packet is an I frame or a P frame.
  • the PDCP layer determines that the type of the data packet is an I frame according to the first field in the PDCP Data PDU, the PDCP sends the I frame data packet to the associated first type RLC entity, and counts the amount of data to be transmitted in the I frame data packet.
  • the PDCP layer determines that the type of the data packet is a P frame according to the first field in the PDCP Data PDU, the PDCP sends the P frame data packet to the associated second type RLC entity, and counts the amount of data to be transmitted in the P frame data packet.
  • the data volumes of the to-be-transmitted data can be reported to the corresponding MAC entities associated with the different RLC entities.
  • the first field is a service data unit SDU type field.
  • the service data unit type (SDU Type) field indicates that the type of data packet is I frame or P frame.
  • the first field when the first field is a first setting value, it indicates that the type of the corresponding PDCP Data PDU is an I frame.
  • the first field when the first field is a second setting value, it indicates that the type of the corresponding PDCP Data PDU is a P frame.
  • the first setting value is 101
  • the second setting value is 110.
  • the bit value of the first field is 101
  • the bit value of the first field is 110
  • the attribute information of the data packet is referenced to determine the corresponding RLC entity, thereby notifying its associated MAC entity of the amount of data to be transmitted.
  • FIG. 6 is a method for sending data volume according to an exemplary embodiment. As shown in FIG. 6 , the method includes steps S601 to S603, specifically:
  • Step S601 In a scenario where a PDCP entity sends a data packet of a first service to at least one type of radio link control RLC entity, the PDCP entity determines a type of at least one type of RLC entity.
  • Step S602 The PDCP entity determines the amount of data to be transmitted for each type of data packet.
  • Step S603 The PDCP entity sends data volume to a MAC entity associated with at least one RLC entity of the corresponding type.
  • the first service is an XR service.
  • the PDCP layer determines the type of at least one type of RLC entity according to attribute information of the data packet.
  • the first field in the data packet may indicate attribute information of the data packet, such as the type of the data packet.
  • the attribute information of the data packet includes one of the following: the type of the data packet; the priority level of the data packet; and the processing level of the data packet.
  • data volume statistics of each type of data to be transmitted are performed in combination with the correspondence between the attribute information of the data packet and the RLC entity.
  • the description is still made by taking the attribute information of the data packet as the type of the data packet as an example.
  • the first type RLC entity includes at least one RLC entity, counts the amount of data to be transmitted when the I frame data packet is sent to different RLC entities, and sends the corresponding amount of data to be transmitted to the MAC entity associated with at least one RLC entity in the first type RLC entity.
  • the second type RLC entity includes at least one RLC entity, counts the amount of data to be transmitted when the P frame data packet is sent to different RLC entities, and sends the corresponding amount of data to the MAC entity associated with at least one RLC entity in the second type RLC entity.
  • the data volume of each type of RLC entity will be reported separately to the MAC entity associated with the RLC entity.
  • the type of the data packet may be an I frame or a P frame.
  • the description is still made by taking the attribute information of the data packet as the type of the data packet as an example.
  • P-frame data packets are generally integer multiples of I-frame data packets.
  • the I-frame data packets and P-frame data packets satisfy a proportional relationship in terms of transmission rate. For example, one I-frame data packet is sent after every eight P-frame data packets are sent.
  • the I-frame data packets and P-frame data packets in the data packets received by the PDCP layer also satisfy this proportional relationship.
  • the PDCP layer counts the received I-frame data packets and includes them in the data volume of the I-frame data packets. According to the data volume of the to-be-transmitted data of the I-frame data packets, the data volume associated with the P-frame data packets can be calculated based on the proportional relationship, thereby obtaining the data volume of the two types of data packets, the I-frame data packets and the P-frame data packets.
  • the I frame data packet is sent to the associated first type RLC entity, and the P frame data packet is sent to the associated second type RLC entity.
  • the first type RLC entity and the second type RLC entity each include at least one RLC entity.
  • the PDCP layer notifies the MAC entities associated with different RLC entities according to the data volume. For example, the data volume of the I frame data packet is sent to the MAC entity associated with at least one RLC entity in the first type of RLC entity, and the data volume of the P frame data packet is sent to the MAC entity associated with at least one RLC entity in the second type of RLC entity.
  • statistics are taken on the data volume of one type of data packet, and combined with calculations, the data volume of other types of data packets is obtained, and then the corresponding associated MACs are reported respectively.
  • the type of data packet is unknown, that is, the type of service to be transmitted cannot be determined based on the type of data packet, this type of service can be transmitted to a predetermined RLC entity.
  • PDCP sends the data volume of the data to be transmitted counted by PDCP to the MAC entity associated with the RLC entity.
  • the present disclosure embodiment provides a method for sending data volume, which is performed by the user equipment 101.
  • the method includes step S401', specifically:
  • Step S401' in the scenario where the PDCP layer sends a data packet of the first service to at least one radio link control RLC entity, if the PDCP packet copy function of the radio bearer RB of the first service is activated, or if the PDCP packet copy function of the RLC entity associated with the PDCP of the RB is activated, the PDCP entity sends data to the MAC entity associated with the first RLC entity and the MAC entity associated with the second RLC entity.
  • the first RLC entity can be called a primary RLC entity, and the second RLC entity can be called a secondary RLC entity; or, the first RLC entity can be called a duplicated RLC entity, and the second RLC entity can be called a duplicate RLC entity.
  • the first RLC entity and the second RLC entity may be determined by protocol or network instruction, for example, by the order of configuration, the first configured RLC entity is the first RLC entity, and the later configured RLC entity is the second RLC entity.
  • the first RLC entity may be used by default for transmission of the PDCP layer control PDU.
  • the first service is an XR service.
  • a PDCP duplication function is configured for the RB corresponding to the XR service.
  • the PDCP layer copies and sends data packets to the first RLC entity and the second RLC entity. Therefore, the amount of data needs to be reported to the MAC entity associated with the first RLC entity and the MAC entity associated with the second RLC entity, respectively.
  • FIG. 7 is a flow chart of a method for sending a BSR according to an exemplary embodiment. As shown in FIG. 7 , the method includes step S701, specifically:
  • Step S701 The MAC entity sends a buffer status report BSR to the network device 102 according to the data volume of the to-be-transmitted data of the first service sent by the PDCP layer.
  • the first service is an XR service.
  • the MAC layer may receive data volumes reported by the PDCP layer according to the types of RLC entities.
  • the attribute information of the data packet includes one of the following: the type of the data packet; the priority level of the data packet; and the processing level of the data packet.
  • the MAC layer receives the data volume to be transmitted of at least one type of RLC entity reported by the PDCP layer based on the diversion function of the PDCP layer, so that the BSR can be reported to the network device 102 in a timely and effective manner, and a BSR reporting method is provided for this diversion scenario.
  • the RLC entity For RBs of XR services, if the RLC entity is associated with the type of data packet, the following two data volume sending methods may be included:
  • each PDCP entity of the RB is configured to be associated with N types of RLC entities.
  • the N types of RLC entities may correspond to: N UM RLC entities (bidirectional transmission), or 2N UM RLC entities (corresponding to the uplink and downlink directions respectively), or N AM RLC entities.
  • RLC entity there is one RLC entity of one type.
  • For UM bidirectional transmission there is one UM RLC entity, for UM unidirectional transmission, there is one UM RLC entity in each direction, and for AM mode, there is one AM RLC entity).
  • PDCP can determine the type of data packet according to the SDU type field of the PDCP Data PDU data packet, thereby determining the type of RLC entity associated with the data packet.
  • Each type of RLC entity may include at least one RLC entity, and each RLC entity is associated with a MAC entity.
  • PDCP sends the amount of data to be transmitted for each type of data packet to the MAC entity associated with each RLC entity associated with the type of data packet, where the amount of data does not include control data, but only includes PDCP Data PDU. Control data is generally sent to the first RLC entity.
  • a first type of RLC entity is configured for the first data packet type (I frame), and the first type of RLC entity includes one RLC entity;
  • a second type of RLC entity is configured for the second data packet type (P frame), and the second type of RLC entity includes one RLC entity.
  • one RLC entity in the first type of RLC entity is associated with a first MAC entity, and one RLC entity in the second type of RLC entity is associated with a second MAC entity.
  • the first MAC entity the amount of data to be transmitted of the first data packet type, i.e., the I frame
  • the second MAC entity the amount of data to be transmitted of the second data packet type, i.e., the P frame.
  • the control PDU of the PDCP layer can be counted and sent to the MAC entity associated with the first RLC entity, such as the MAC entity associated with the RLC entity used to transmit the I frame mentioned above.
  • the MAC entity associated with the RLC entity is notified that its PDCP layer counts the data volume of a certain type of service (excluding PDCP control PDU).
  • the MAC entity managed by the RLC entity that transmits the PDCP control PDU also needs to be notified of the data volume of the PDCP layer's control PDU.
  • each PDCP entity of the RB is configured to be associated with N types of RLC entities for traffic diversion according to service attributes.
  • each PDCP entity is associated with N types of RLC entities.
  • one of the N types of RLC entities can be configured with multiple RLC entities for RLC entity-level traffic diversion.
  • a first type of RLC entity is configured for the first service data type, and the first type of RLC entity includes an RLC entity, and the RLC entity is associated with the first MAC entity;
  • a second type of RLC entity is configured for the second service data type, and the second type of RLC entity includes two RLC entities (a second RLC entity and a third RLC entity), and the two RLC entities are respectively used for the main base station (MCG) and the secondary base station (SCG), and the two RLC entities are respectively associated with the second MAC entity and the third MAC entity.
  • split bearers can be used to transmit services with large traffic volumes, while for services with small traffic volumes, there is no need to use split bearer transmission.
  • the first MAC entity associated with the first RLC entity in the first type RLC entity is notified of the amount of data to be transmitted of the first service data type, which is: the amount of data of the first service data type counted by the PDCP layer.
  • the second MAC entity associated with the second RLC entity and the third MAC entity associated with the third RLC entity in the second type RLC are notified of the amount of data to be transmitted of the second service data type.
  • the notification process may be in accordance with the following provisions: if the total number of data packets counted by PDCP is less than a threshold, then only the second MAC entity associated with the first RLC entity may be notified of the amount of data to be transmitted of the second service data type counted by the PDCP layer; if the total number of data packets is greater than a certain threshold, then the amount of data to be transmitted of the second service data type counted by the PDCP layer is sent to the second MAC entity associated with the second RLC entity and the third MAC entity associated with the third RLC entity at the same time.
  • the control PDU of the PDCP layer can be counted and sent to the MAC entity associated with a specific RLC entity.
  • control PDU of the PDCP layer can be counted and sent to any MAC entity associated with the RLC entity. That is, in the split bearer scenario, all MAC entities need to additionally notify the data volume of the control PDU of the PDCP layer.
  • each PDCP entity of the RB is configured to be associated with N types of RLC entities for traffic diversion according to service attributes.
  • each PDCP entity is associated with N types of RLC entities.
  • a certain type of the N types of RLC entities can be configured with multiple RLC entities for PDCP packet replication.
  • a first type of RLC entity is configured for the first service data type, and the first type of RLC entity includes one RLC entity (first RLC entity), and the first RLC entity is associated with the first MAC entity;
  • a second type of RLC entity is configured for the second service data type, and the second type of RLC entity includes two RLC entities (second RLC entity and third RLC entity), and the two RLC entities are used for the main base station (MCG) and the secondary base station (SCG), respectively, and the two RLC entities are associated with the second MAC entity and the third MAC entity, respectively.
  • PDCP packet replication is configured for the second RLC entity, and the replicated packet will be sent to the third RLC entity.
  • the PDCP sends, to the first MAC entity associated with the first RLC entity, the amount of data to be transmitted of the first service data type counted by the PDCP.
  • the PDCP sends the amount of data to be transmitted of the second service data type counted by PDCP to the second MAC entity associated with the second RLC entity, and sends the amount of data to be transmitted of the second service data type counted by PDCP to the third MAC entity associated with the third RLC entity.
  • the second RLC entity can be called the primary RLC entity
  • the third RLC entity can be called the secondary RLC entity
  • the second RLC entity can be called the copied RLC entity
  • the third RLC entity can be called the copied RLC entity.
  • the master RLC entity or the replicated RLC entity, and the auxiliary RLC entity or the replicated RLC entity may be agreed upon by protocol or indicated by the network.
  • the first configured RLC entity is the master RLC entity
  • the subsequent configured RLC entity is the replicated RLC entity.
  • control PDU of the PDCP layer may be sent to a predetermined RLC entity, for example, the first RLC entity or the second RLC entity may be used by default for transmission of the PDCP layer control PDU.
  • the control PDU of the PDCP layer can count the amount of data to be transmitted and then send it to the MAC entity associated with the agreed RLC entity, such as the MAC entity associated with the RLC entity used to transmit the I frame. That is, for the MAC entity associated with the RLC entity that transmits the PDCP control PDU, it is also necessary to additionally notify the data volume of the control PDU of the PDCP layer.
  • the data packet type is not associated, such as the PDCP SDU header or GTPU header does not indicate the type of the data packet, that is, the type of the data packet cannot be determined.
  • this type of service data can be transmitted to a predetermined RLC entity.
  • PDCP sends the data volume of the data to be transmitted counted by PDCP to the MAC entity associated with the RLC entity.
  • the embodiment of the present disclosure also provides a device for sending data volume.
  • the communication device can have the function of the user equipment in the above method embodiment and is used to execute the steps performed by the user equipment in the above embodiment.
  • the function can be realized by hardware, or by software or hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the communication device 800 shown in FIG. 8 may serve as the user equipment involved in the above method embodiment, and execute the steps executed by the user equipment in the above method embodiment.
  • the communication device 800 shown in Figure 8 includes a PDCP entity 801, and the PDCP entity 801 is configured to send the data volume of data to be transmitted to the media access control MAC entity associated with at least one type of radio link control RLC entity in a scenario where a data packet of a first service is sent to at least one type of RLC entity.
  • the device 900 may include one or more of the following components: a processing component 902, a memory 904, a power component 906, a multimedia component 908, an audio component 910, an input/output (I/O) interface 912, a sensor component 914, and a communication component 916.
  • the processing component 902 generally controls the overall operation of the device 900, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 902 may include one or more processors 920 to execute instructions to complete all or part of the steps of the above-mentioned method.
  • the processing component 902 may include one or more modules to facilitate the interaction between the processing component 902 and other components.
  • the processing component 902 may include a multimedia module to facilitate the interaction between the multimedia component 908 and the processing component 902.
  • the memory 904 is configured to store various types of data to support operations on the device 900. Examples of such data include instructions for any application or method operating on the device 900, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 904 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power supply component 906 provides power to the various components of the device 900.
  • the power supply component 906 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 900.
  • the multimedia component 908 includes a screen that provides an output interface between the device 900 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
  • the multimedia component 908 includes a front camera and/or a rear camera. When the device 900 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
  • the audio component 910 is configured to output and/or input audio signals.
  • the audio component 910 includes a microphone (MIC), and when the device 900 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal can be further stored in the memory 904 or sent via the communication component 916.
  • the audio component 910 also includes a speaker for outputting audio signals.
  • I/O interface 912 provides an interface between processing component 902 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.
  • the sensor assembly 914 includes one or more sensors for providing various aspects of status assessment for the device 900.
  • the sensor assembly 914 can detect the open/closed state of the device 900, the relative positioning of components, such as the display and keypad of the device 900, and the sensor assembly 914 can also detect the position change of the device 900 or a component of the device 900, the presence or absence of user contact with the device 900, the orientation or acceleration/deceleration of the device 900, and the temperature change of the device 900.
  • the sensor assembly 914 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • the sensor assembly 914 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 914 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 916 is configured to facilitate wired or wireless communication between the device 900 and other devices.
  • the device 900 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 916 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 916 also includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the apparatus 900 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • controllers microcontrollers, microprocessors or other electronic components to perform the above method.
  • a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 904 including instructions, and the instructions can be executed by the processor 920 of the device 900 to perform the above method.
  • the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
  • the PDCP layer diverts the data of the XR service, and in combination with at least one type of RLC entity in transmission, reports the data volume to be transmitted to its associated MAC entity, thereby realizing effective data volume reporting in the scenario of XR service diversion, which is beneficial for the user equipment to complete BSR reporting.

Landscapes

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

Abstract

La présente divulgation concerne un procédé de transmission d'un volume de données, un appareil et un support de stockage lisible. Le procédé comprend les étapes suivantes : dans un scénario dans lequel une entité PDCP transmet des paquets de données d'un premier service à au moins un type d'entités de commande de liaison radio (RLC), l'entité PDCP transmet à une entité de commande d'accès au support (MAC) associée audit un ou à plusieurs types d'entités RLC un volume de données de données à transmettre. Dans les modes de réalisation de la présente divulgation, dans un scénario de transmission de premières données de service, une transmission de délestage de trafic des données de service est obtenue au moyen d'une couche PDCP, et, étant donné le ou les types d'entités RLC recevant des trafics délestés, le volume de données des données à transmettre est rapporté à l'entité MAC associée, fournissant ainsi un mode de rapport efficace de volumes de données dans des scénarios de délestage de trafic de service XR.
PCT/CN2022/121872 2022-09-27 2022-09-27 Procédé de transmission de volume de données, appareil et support de stockage lisible WO2024065215A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280003623.7A CN116097726A (zh) 2022-09-27 2022-09-27 发送数据量的方法、装置以及可读存储介质
PCT/CN2022/121872 WO2024065215A1 (fr) 2022-09-27 2022-09-27 Procédé de transmission de volume de données, appareil et support de stockage lisible

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/121872 WO2024065215A1 (fr) 2022-09-27 2022-09-27 Procédé de transmission de volume de données, appareil et support de stockage lisible

Publications (1)

Publication Number Publication Date
WO2024065215A1 true WO2024065215A1 (fr) 2024-04-04

Family

ID=86197738

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/121872 WO2024065215A1 (fr) 2022-09-27 2022-09-27 Procédé de transmission de volume de données, appareil et support de stockage lisible

Country Status (2)

Country Link
CN (1) CN116097726A (fr)
WO (1) WO2024065215A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104247547A (zh) * 2012-04-20 2014-12-24 华为技术有限公司 数据分流配置方法、基站系统和用户终端
CN109150425A (zh) * 2017-06-15 2019-01-04 维沃移动通信有限公司 一种数据处理方法、移动终端及计算机可读存储介质
CN110536487A (zh) * 2018-05-25 2019-12-03 华为技术有限公司 一种数据传输方法及装置
US20200404698A1 (en) * 2018-04-03 2020-12-24 Lg Electronics Inc. Method and apparatus for transmitting signals by tm rlc entity of transmission end in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104247547A (zh) * 2012-04-20 2014-12-24 华为技术有限公司 数据分流配置方法、基站系统和用户终端
CN109150425A (zh) * 2017-06-15 2019-01-04 维沃移动通信有限公司 一种数据处理方法、移动终端及计算机可读存储介质
US20200404698A1 (en) * 2018-04-03 2020-12-24 Lg Electronics Inc. Method and apparatus for transmitting signals by tm rlc entity of transmission end in wireless communication system
CN110536487A (zh) * 2018-05-25 2019-12-03 华为技术有限公司 一种数据传输方法及装置

Also Published As

Publication number Publication date
CN116097726A (zh) 2023-05-09

Similar Documents

Publication Publication Date Title
WO2019056308A1 (fr) Procédé de mise en œuvre, dispositif, équipement utilisateur et station de base pour une mise à jour de zone de localisation
WO2021179130A1 (fr) Procédé et dispositif de traitement de communication
US20220216957A1 (en) Method and device for carrier aggregation, communication apparatus, and storage medium
WO2018201921A1 (fr) Procédé et dispositif de communication
AU2021308253A1 (en) Communication method and communication apparatus
WO2021217595A1 (fr) Procédé et dispositif de traitement de transmission de données, appareil de communication et support de stockage
WO2018214062A1 (fr) Procédé et dispositif d'émission d'un message de gestion des ressources radioélectriques
WO2024065215A1 (fr) Procédé de transmission de volume de données, appareil et support de stockage lisible
WO2022198389A1 (fr) Procédé et appareil de configuration de liaison latérale, dispositif de communication, et support de stockage
WO2022147662A1 (fr) Procédé et appareil de planification d'intervalle de mesure, dispositif de communication et support de stockage
WO2022021271A1 (fr) Procédé et appareil de commutation de faisceau, et dispositif de réseau, terminal et support d'enregistrement
WO2021227081A1 (fr) Procédé et dispositif de transfert de service, appareil de communication et support de stockage
WO2024065207A1 (fr) Procédé et appareil d'envoi de données et support de stockage lisible
WO2024087211A1 (fr) Procédé et appareil de transmission d'informations de configuration, et support de stockage lisible
WO2024130509A1 (fr) Procédé et appareil de transmission d'informations, dispositif de communication et support de stockage
WO2024130563A1 (fr) Procédé et appareil de gestion de qos, dispositif de communication et support de stockage
WO2022213330A1 (fr) Procédé et appareil de transmission d'informations, dispositif de communication et support de stockage
WO2023122916A1 (fr) Appareil et procédé de traitement d'informations, dispositif de communication et support de stockage
WO2023133860A1 (fr) Appareil et procédé de transmission d'informations, dispositif de communication, et support de stockage
WO2022077400A1 (fr) Procédé et appareil pour déterminer la participation à un service, dispositif d'élément de réseau et support d'enregistrement
WO2022198589A1 (fr) Procédé et appareil de réduction d'interférence, et dispositif de communication et support de stockage
WO2023241445A1 (fr) Procédés de traitement de retard temporel d'ensemble de paquets de données, appareil et dispositif de communication
WO2022257910A1 (fr) Procédé et appareil de contrôle de qos
WO2022205475A1 (fr) Procédé et appareil de configuration pour estimation de canal conjoint, et dispositif et support de stockage
WO2024103375A1 (fr) Procédé et appareil de traitement d'informations, et dispositif de communication et support de stockage

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

Country of ref document: EP

Kind code of ref document: A1