WO2024087211A1 - 一种传输配置信息的方法、装置及可读存储介质 - Google Patents

一种传输配置信息的方法、装置及可读存储介质 Download PDF

Info

Publication number
WO2024087211A1
WO2024087211A1 PCT/CN2022/128395 CN2022128395W WO2024087211A1 WO 2024087211 A1 WO2024087211 A1 WO 2024087211A1 CN 2022128395 W CN2022128395 W CN 2022128395W WO 2024087211 A1 WO2024087211 A1 WO 2024087211A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc entity
rlc
configuration information
function
service
Prior art date
Application number
PCT/CN2022/128395
Other languages
English (en)
French (fr)
Inventor
李艳华
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2022/128395 priority Critical patent/WO2024087211A1/zh
Priority to CN202280004751.3A priority patent/CN115997464A/zh
Publication of WO2024087211A1 publication Critical patent/WO2024087211A1/zh

Links

Images

Classifications

    • 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
    • H04W74/00—Wireless channel access

Definitions

  • the present disclosure relates to the field of wireless communication technologies, and in particular to a method, device and readable storage medium for transmitting configuration information.
  • 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
  • the present disclosure provides a method, an apparatus, and a readable storage medium for transmitting configuration information.
  • the present disclosure provides a method for sending configuration information, which is performed by a network device, and the method includes:
  • Configuration information is sent to a user equipment, where the configuration information includes N types of radio link control RLC entities corresponding to a packet data convergence protocol PDCP entity in the user equipment.
  • N is the number of service types of service data
  • the configuration information is further used to configure each type of RLC entity to transmit service data of the corresponding service type.
  • the configuration information is further used to configure a default RLC entity, and the default RLC entity is used to transmit the first service.
  • each type of RLC entity includes at least one RLC entity.
  • the configuration information includes indication identifiers corresponding to the N types of RLC entities, and the indication identifiers are used to indicate whether the first function is activated for some types or all types of RLC entities.
  • the method further includes:
  • First indication information is sent to the user equipment, where the first indication information is used to indicate activation or deactivation of a first function of some types or all types of RLC entities.
  • the first function includes a service diversion function or a packet replication function.
  • the sending the first indication information to the user equipment includes:
  • An access control layer control unit MAC CE signaling is sent to the user equipment media, wherein the MAC CE signaling includes an information field for indicating the first indication information.
  • the information field includes at least one of the following: bits corresponding to all types of RLC entities, bits corresponding to each type of RLC entity, and bits corresponding to each RLC entity;
  • bit When the bit is a first value, it indicates activating the first function of the RLC entity corresponding to the bit.
  • the method further includes:
  • a notification message is received from the user equipment, where the notification message is used to indicate that the number of times that the RLC entity used for the first function retransmits the service data reaches a maximum number of retransmissions.
  • the present disclosure provides a method for receiving configuration information, which is performed by a user equipment, the method comprising:
  • the configuration information including N types of radio link control RLC entities corresponding to a packet data convergence protocol PDCP entity in the user equipment;
  • service data is sent to at least one type of RLC entity.
  • N is the number of service types of service data
  • the configuration information is further used to configure each type of RLC entity to transmit service data of the corresponding service type
  • the sending service data to at least one type of RLC entity according to the configuration information includes:
  • the service data is sent to an RLC entity of a type corresponding to the service type.
  • the configuration information is further used to configure a default RLC entity, and the default RLC entity is used to transmit the first service.
  • sending service data to at least one type of RLC entity according to the configuration information includes:
  • the service data is sent to the default RLC entity in a split manner.
  • sending service data to at least one type of RLC entity according to the configuration information includes:
  • the service data is offloaded and sent to the default RLC entity.
  • the method further includes:
  • the method further includes:
  • first indication information sent by the network device, where the first indication information is used to indicate activation or deactivation of a first function of some types or all types of RLC entities;
  • the first function includes a service diversion function or a packet replication function.
  • the receiving the first indication information sent by the network device includes:
  • Receive MAC CE signaling sent by the network device wherein the MAC CE signaling includes an information field for indicating the first indication information.
  • determining, according to the first indication information, whether some types or all types of RLC entities activate the first function includes:
  • At least one bit in the information field is a first value, it is determined that a first function of the RLC entity corresponding to the at least one bit is activated.
  • the method further includes:
  • the present disclosure provides a device for sending configuration information, which can be used to execute the steps performed by a network device in the first aspect or any possible design of the first aspect.
  • the network device can implement each function in the above methods in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • the device may include a transceiver module, wherein the transceiver module can be used to support the communication device to perform communication.
  • the transceiver module is configured to send configuration information to the user equipment, and the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entity in the user equipment.
  • the present disclosure provides a device for receiving configuration information, which may be used to execute the steps performed by a user equipment in the second aspect or any possible design of the second aspect.
  • the user equipment may implement the functions of the above methods in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • the device may include a transceiver module and a processing module coupled to each other, wherein the transceiver module can be used to support the communication device to communicate, and the processing module can be used for the communication device to perform processing operations, such as generating information/messages to be sent, or processing received signals to obtain information/messages.
  • the transceiver module can be used to support the communication device to communicate
  • the processing module can be used for the communication device to perform processing operations, such as generating information/messages to be sent, or processing received signals to obtain information/messages.
  • the transceiver module is configured to receive configuration information sent by the network device, wherein the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entity in the user equipment.
  • the processing module is configured to send service data to at least one type of RLC entity according to the configuration information.
  • 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 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 second aspect or any possible design of the second 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.
  • the present disclosure provides a computer-readable storage medium, wherein instructions (or computer programs, programs) are stored in the computer-readable storage medium, which, when called and executed on a computer, enables the computer to execute the above-mentioned second aspect or any possible design of the second 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 transmitting configuration information according to an exemplary embodiment
  • FIG4 is a flow chart showing a method for sending configuration information according to an exemplary embodiment
  • FIG5 is a flow chart showing another method for sending configuration information according to an exemplary embodiment
  • FIG6 is a schematic diagram of the structure of a MAC CE signaling information field according to an exemplary embodiment
  • FIG7 is a schematic diagram of the structure of a MAC CE signaling information domain according to another exemplary embodiment
  • FIG8 is a flow chart showing a method for receiving configuration information according to an exemplary embodiment
  • FIG9 is a structural diagram of a device for sending configuration information according to an exemplary embodiment
  • FIG10 is a structural diagram of a network device according to an exemplary embodiment
  • FIG11 is a structural diagram of a device for receiving configuration information according to an exemplary embodiment
  • Fig. 12 is a structural 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".
  • FIG1 is a schematic diagram of a wireless communication system 100 applicable to an embodiment of the present application.
  • a method for transmitting configuration information provided in an embodiment of the present disclosure can be applied to a wireless communication system 100, which may include a network device 101 and a user device 102.
  • the user device 102 is configured to support carrier aggregation and can be connected to multiple carrier components of the network device 101, including a primary carrier component and one or more secondary carrier components.
  • 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 102 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 102 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 101 shown in the figure.
  • the user equipment 102 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 101 may be an access network device (or access network point).
  • the access network device refers to a device that provides network access functions, such as a radio access network (RAN) base station, etc.
  • the network device 101 may specifically include a base station (BS), or a base station and a wireless resource management device for controlling the base station, etc.
  • the network device 101 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, etc.
  • the network device 101 may be a wearable device or a vehicle-mounted device.
  • the network device 101 may also be a communication chip with a communication module.
  • the network equipment 101 includes, but is not limited to, the next generation base station (gnodeB, gNB) in 5G, the evolved node B (evolved node B, eNB) in the LTE system, the radio network controller (radio network controller, RNC), the node B (node B, NB) in the WCDMA system, the wireless controller under the CRAN system, the base station controller (basestation controller, BSC), the base transceiver station (base transceiver station, BTS) in the GSM system or the CDMA system, the home base station (for example, home evolved nodeB, or home node B, HNB), the baseband unit (baseband unit, BBU), the transmitting and receiving point (TRP), the transmitting point (transmitting point, TP) or the mobile switching center, etc.
  • the next generation base station evolved node B, eNB
  • the radio network controller radio network controller
  • RNC radio network controller
  • node B node B
  • BTS base transcei
  • 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.
  • the present disclosure provides a method for transmitting configuration information, with reference to FIG3 , which is a method for transmitting configuration information according to an exemplary embodiment. As shown in FIG3 , the method includes steps S301 to S302, specifically:
  • Step S301 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • Step S302 The user equipment 102 sends service data to at least one type of RLC entity according to the received configuration information.
  • the network device 101 sends the configuration information by sending an RRC message.
  • the business data may be XR business data
  • the XR business data includes augmented reality (AR) business data, virtual reality (VR) business data, and cloud gaming (Cloud gaming) business data, etc.
  • AR augmented reality
  • VR virtual reality
  • Cloud gaming cloud gaming
  • N 1
  • N 2, that is, the network device 101 configures the PDCP entity of the UE to be associated with 2 types of RLC entities.
  • N is related to the type of business data.
  • the PDCP entity of the user equipment 102 receives service data sent by the network device 101 through a high layer, and diverts the service data to at least one corresponding type of RLC entity (RLC entity).
  • RLC entity RLC entity
  • the network device 101 sends configuration information to the user equipment 102 to configure N types of RLC entities associated with the PDCP entity to the user equipment 102.
  • the user equipment 102 can effectively divert service data according to the configuration information to improve the efficiency of transmitting service data.
  • the network device 101 may determine the configuration information, and the user device 102 may offload the uplink transmission data according to the configuration information.
  • the network device 101 may determine the configuration information, and inform the user device 102 of the configuration information, and the network device 101 may offload the downlink data.
  • the following only lists the scenarios in which the user device 102 offloads, but the offload methods illustrated and described in the following embodiments are also applicable to the scenarios in which the network device 101 offloads.
  • FIG. 4 is a method for sending configuration information according to an exemplary embodiment. As shown in FIG. 4 , the method includes step S401, specifically:
  • Step S401 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • the network device 101 sends the configuration information by sending an RRC message.
  • the service data may be XR service data.
  • N 1
  • N 2, that is, the network device 101 configures the PDCP entity of the UE to be associated with 2 types of RLC entities.
  • N is related to the type of business data.
  • business data can be distinguished into different business types according to different dimensions.
  • the business type classification dimensions include, but are not limited to:
  • the importance of business data means differentiating different business types of business data according to different importance.
  • the importance of business data includes high, medium and low, and the business types may include business types corresponding to high importance, business types corresponding to medium importance, and business types corresponding to low importance.
  • the importance of business data is measured or represented by numbers, such as first-level business data.
  • the attributes of the business data such as the intra-coded picture (I frame) and the predictive-frame (P frame) of the business data, are used to distinguish different business types of the business data.
  • the sub-flow (Sub Qos flow) or QoS flow to which the service data belongs For example, service data belonging to different sub-flows corresponds to different service types, or different service data belonging to the same sub-flow corresponds to different service types.
  • the priority level of business data is to distinguish different business types of business data according to different priority levels. For example, different priority levels are represented by high, medium, low or numbers, and each priority level corresponds to a business type.
  • the reliability levels of business data that is, different types of business data are distinguished according to different reliability requirements.
  • different reliability requirements are represented by high, medium, low or numbers, and each reliability requirement corresponds to a business type.
  • the purpose of the service data that is, different service types of the service data are distinguished according to the different purposes of the service data.
  • the purpose of the service data may include: PDCP control data (PDCP Control PDU) and PDCP data protocol data unit (PDCP Data PDU).
  • PDCP Control PDU PDCP Control data
  • PDCP Data PDU PDCP data protocol data unit
  • the service data may be in units of data packets or in units of data packet sets. When distinguishing in units of data packet sets, if a data packet in the data packet set is classified as the first service type, all data packets in the data packet set belong to the first service type.
  • each type of RLC entity includes at least one RLC entity.
  • each type of RLC entity includes one RLC entity.
  • the one RLC entity may have different conditions.
  • the RLC entity in unacknowledged transmission mode (UM) and the RLC entity is capable of bidirectional transmission (supporting uplink and downlink), the RLC entity is a UM RLC entity.
  • the one RLC entity refers to one RLC entity for each transmission direction, that is, the one RLC entity is an uplink UM RLC entity and a downlink UM RLC entity.
  • the RLC entity is an AM RLC entity.
  • each type of RLC entity includes multiple RLC entities. At this time, the multiple RLC entities still have different situations according to different transmission modes.
  • the multiple RLC entities include two UM RLC entities.
  • the multiple RLC entities include four UM RLC entities, including two uplink UM RLC entities and two downlink UM RLC entities.
  • the multiple RLC entities include two AM RLC entities.
  • the network device 101 sends configuration information to the user equipment 102 to configure N types of RLC entities associated with the PDCP entity to the user equipment 102.
  • the user equipment 102 can effectively divert service data according to the configuration information to improve the efficiency of transmitting service data.
  • the embodiment of the present disclosure provides a method for sending configuration information, which is performed by the network device 101.
  • the method includes step S401, specifically:
  • Step S401 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • N is the number of service types of service data
  • the configuration information is also used to configure each type of RLC entity to transmit service data of the corresponding service type.
  • the service types of service data may include: intra-coded picture (Intra-coded picture or I frame) and forward predictive coded frame (Predictive-frame, P frame), namely I frame and P frame, wherein the I frame is a key frame.
  • one type of RLC entity corresponds to a first logical channel for transmitting I frame service data; the other type of RLC entity corresponds to a second logical channel for transmitting P frame service data.
  • the service type of the service data may include: data of different flows or sub-flows, for example, first sub-flow (sub-flow1) service data and second sub-flow (sub-flow2) service data.
  • one type of RLC entity is used to transmit the first sub-stream service data
  • the other type of RLC entity is used to transmit the second sub-stream service data
  • the service type of service data may include: PDCP control data (PDCP Control PDU) and PDCP data protocol data unit (PDCP Data PDU).
  • PDCP control data is data generated by PDCP
  • PDCP data protocol data unit is a data packet received by PDCP from a higher layer.
  • the N types of RLC entities are recorded as a first type RLC entity, a second type RLC entity, ..., an Nth type RLC entity.
  • the first RLC entity or the second RLC entity may be specified by a network device or agreed upon by a protocol
  • the network device may specify or agree upon a primary RLC entity and a secondary RLC entity (RLC entity other than the primary RLC entity);
  • the default RLC entity may be specified by the network device or agreed upon by the protocol
  • the first RLC entity is used to transmit PDCP control data
  • the second RLC entity is used to transmit PDCP data protocol data units.
  • the first RLC entity is a primary RLC entity.
  • each type of RLC entity includes at least one RLC entity.
  • the network device 101 configures the number of types of RLC entities associated with the PDCP entity for the user equipment 102 according to the type of service data, and configures each type of RLC entity to transmit the corresponding type of service data.
  • the embodiment of the present disclosure provides a method for sending configuration information, which is performed by the network device 101.
  • the method includes step S401, specifically:
  • Step S401 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • the configuration information is also used to configure N types of RLC entities to belong to different master nodes or slave nodes, or to the same master node (MN) or slave node (SN), or to the same cell or different cells.
  • the N types of RLC entities are used to transmit service data of different service types.
  • the N types of RLC entities correspond to service data of N service types.
  • the MN and the SN may be used for dual connectivity (DC) of the UE.
  • DC dual connectivity
  • the UE maintains the RRC connection of the serving cell under the MN and may be configured to connect to the serving cell under the SN to improve data throughput.
  • the embodiment of the present disclosure provides a method for sending configuration information, which is performed by the network device 101.
  • the method includes step S401, specifically:
  • Step S401 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • the configuration information is also used to configure a default RLC entity, and the default RLC entity is used to transmit the first service.
  • the default RLC entity may be one type among the N types of RLC entities, or may be additionally configured outside the N types of RLC entities.
  • the default RLC entity is a primary RLC entity or other RLC entity designated by the network device.
  • the first service is service data of a specified service type, for example, the first service is PDCP control data.
  • the first service is service data for which no corresponding RLC entity is configured.
  • the user equipment 102 may deliver service data of a specified service type, or service data for which a corresponding RLC entity is not configured, to a default RLC entity according to the configuration information to implement data offloading.
  • the network device 101 configures a default RLC entity for the user equipment 102 to enable the user equipment 102 to offload data of the first service.
  • the embodiment of the present disclosure provides a method for sending configuration information, which is performed by the network device 101.
  • the method includes step S401, specifically:
  • Step S401 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • the configuration information includes indication identifiers corresponding to N types of RLC entities, and the indication identifiers are used to indicate whether the first function is activated for some types or all types of RLC entities.
  • the first function can be a service diversion function or a packet replication function.
  • the network device 101 when the configuration information does not include indication identifiers corresponding to N types of RLC entities, the network device 101 configures the configuration information, and it is considered that the N types of RLC entities in the configuration information have all activated the first function such as the service offloading function.
  • the indication identifier occupies one bit, and the N types of RLC entities can be uniformly indicated by the same bit.
  • the N types of RLC entities all activate the service offloading function.
  • the N types of RLC entities all deactivate the service offloading function.
  • the indication identifier occupies multiple bits.
  • the configuration information includes bits corresponding to each type of RLC entity to indicate whether each type of RLC entity activates the first function such as the service diversion function. When a certain type of RLC entity indicates to activate the first function, each RLC entity of the type activates the first function.
  • the RLC entity of this type when the bit corresponding to the indication identifier of any type of RLC entity is 1, the RLC entity of this type activates the first function such as the service diversion function; when the bit corresponding to the indication identifier of any type of RLC entity is 0, the RLC entity of this type deactivates the service diversion function.
  • the indicator corresponds to indicating the activation status of the first function of all types of RLC entities. For example, when the values of the multiple bits are all 1, it indicates that all types of RLC entities have activated the first function.
  • the indicator occupies multiple bits, each bit is used to indicate: activating or deactivating the first function of an RLC entity.
  • the configuration information includes bits corresponding to each RLC entity to indicate whether a single RLC entity activates the first function such as a service diversion function.
  • the RLC entity when the bit corresponding to the indication identifier of any RLC entity is 1, the RLC entity activates the first function such as the service diversion function; when the bit corresponding to the indication identifier of any RLC entity is 0, the RLC entity deactivates the first function.
  • the user equipment 102 may divert its associated service data to a default RLC entity.
  • the configuration information configures the three types of RLC entities corresponding to the PDCP entity: a first RLC entity, a second RLC entity and a third RLC entity, and configures the first RLC entity to transmit service data or control PDU of a first service type, the second RLC entity to transmit service data of a second service type, and the third RLC entity to transmit service data of a third service type.
  • first RLC entity the second RLC entity or the third RLC entity described in the embodiments of the present disclosure is only for reference and distinction, and is not a limitation on the RLC entity.
  • first RLC entity may also be named as the primary RLC entity
  • second RLC entity or the third RLC entity may also be named as the secondary RLC entity.
  • the configuration information further configures activation of the service offload function of the first RLC entity, activation of the service offload function of the second RLC entity, and deactivation of the service offload function of the third RLC entity.
  • the PDCP layer of the user equipment 102 delivers the service data or control PDU of the first service type to the first RLC entity, and delivers the service data of the second service type to the second RLC entity.
  • the user equipment 102 can deliver service data of the third service type to the default RLC entity.
  • the third RLC entity is deactivated, the corresponding service can also be diverted.
  • the network device 101 synchronously indicates in the configuration information sent down whether some or all RLC entities activate the first function such as the service diversion function, so that the user equipment 102 can know whether some or all RLC entities activate the first function such as the service diversion function according to the configuration information.
  • FIG. 5 is a method for sending configuration information according to an exemplary embodiment. As shown in FIG. 5 , the method includes steps S501 to S502, specifically:
  • Step S501 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • Step S502 The network device 101 sends first indication information to the user equipment 102, where the first indication information is used to indicate activation or deactivation of a first function of some types or all types of RLC entities.
  • steps S501 and S502 are only for illustration, for example, steps S501 and S502 may also be executed synchronously.
  • the network device 101 may send the first indication information by sending downlink control information (Downlink Control Information, DCI) or media access control layer control element (Media Access Control Control Element, MAC CE) signaling.
  • DCI Downlink Control Information
  • MAC CE Media Access Control Control Element
  • the first indication information may uniformly indicate whether the N types of RLC entities activate the first function, that is, uniformly control all types of traffic distribution RLC entities.
  • one bit is used to uniformly indicate whether the N types of RLC entities all activate the first function.
  • the first indication information corresponds to multiple bits, and each bit indicates whether a type of RLC entity activates the first function.
  • the bits corresponding to each type of RLC entity in the first indication information respectively indicate whether each type of RLC entity activates the first function such as the service offloading function.
  • each RLC entity under this type activates the first function.
  • the RLC entity of this type activates the first function such as the service diversion function; when the bit corresponding to any type of RLC entity is 0, the RLC entity of this type deactivates the service diversion function.
  • the first indication information corresponds to a plurality of bits, each bit being used to indicate: activating or deactivating the first function of each RLC entity.
  • the first indication information indicates, through the bit corresponding to each RLC entity in the first indication information, whether each diversion RLC entity activates the first function such as the service diversion function.
  • the RLC entity when the bit value corresponding to any RLC entity is 1, the RLC entity activates the first function such as the service diversion function; when the bit value corresponding to any RLC entity is 0, the RLC entity deactivates the first function.
  • the first function includes a service offloading function or a PDCP packet duplication function.
  • the network device 101 indicates whether some or all of the RLC entities activate the first function by means of dynamic indication, so that whether the RLC entities activate the first function can be adaptively adjusted.
  • the embodiment of the present disclosure provides a method for sending configuration information, which is performed by the network device 101.
  • the method includes steps S501 to S502', specifically:
  • Step S501 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • Step S502' the network device 101 sends downlink control information DCI to the user equipment 102, where the DCI includes first indication information.
  • the first indication information is used to indicate activation or deactivation of the first function of some types or all types of RLC entities.
  • the first function includes a service offloading function or a PDCP packet duplication function.
  • the network device 101 dynamically sends the first indication information through DCI, thereby dynamically configuring N types of RLC entities to activate the first function.
  • the embodiment of the present disclosure provides a method for sending configuration information, which is performed by the network device 101.
  • the method includes steps S501 to S502, specifically:
  • Step S501 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities.
  • step S502 the network device 101 sends a media access control layer control element MAC CE signaling to the user device 102, and the MAC CE signaling includes an information field for indicating the first indication information.
  • the first indication information is used to indicate one of the following: activating or deactivating the first function of some types or all types of RLC entities.
  • the information field includes at least one of the following:
  • the information field includes bits corresponding to all types of RLC entities, that is, the information field uniformly indicates whether all types of RLC entities have activated the first function through one bit.
  • the information domain includes a bit corresponding to all types of RLC entities
  • when the bit is a first value (such as 1) it indicates that all types of RLC entities have activated the first function
  • the bit when the bit is a second value (such as 0), it indicates that all types of RLC entities have deactivated the first function.
  • the activation state of the first function of any type of RLC entity is applicable to all RLC entities of that type.
  • the information field when the information field includes bits corresponding to each type of RLC entity, that is, the information field indicates whether each type of RLC entity activates the first function.
  • the information field includes bits corresponding to each type of RLC entity, where, taking three types of RLC entities as an example, the information field structure can refer to the example corresponding to FIG. 6.
  • the RLC entity of this type When the bit corresponding to any type of RLC entity is a first value (such as 1), the RLC entity of this type activates a first function such as a service diversion function. When the bit corresponding to the indication identifier of any type of RLC entity is a second value (such as 0), the RLC entity of this type deactivates the first function. When a certain type of RLC entity indicates to activate the first function, all RLC entities of this type activate the first function.
  • the information field indicates that all types of RLC entities have activated the first function.
  • the information field when the information field includes bits corresponding to each RLC entity, that is, the information field indicates whether each RLC entity activates the first function.
  • the information field includes bits corresponding to each RLC entity, where, taking three RLC entities as an example, the information field structure can refer to the example corresponding to FIG. 7 .
  • the RLC entity When the bit corresponding to any RLC entity is a first value (such as 1), the RLC entity activates a first function such as a service offloading function. When the bit corresponding to any RLC entity is a second value (such as 0), the RLC entity deactivates the first function.
  • a first value such as 1
  • a second value such as 0
  • the first function includes a service offloading function or a PDCP packet duplication function.
  • Fig. 6 illustrates an information field structure for indicating whether to activate the service offloading function. As shown in Fig. 6, the information field includes: a first part of bits and a second part of bits.
  • the first part of the bits is used to indicate the identifier (DRB ID) of the data radio bearer (DRB), assuming that the length of the first part of the bits is 5 bits.
  • DRB can correspond to service data of multiple service types, that is, it can correspond to multiple types of RLC entities.
  • the second part of bits is used to indicate whether each type of RLC entity activates the service diversion function.
  • the second part of bits is 3 bits long, and each type of RLC entity occupies 1 bit (here, it is assumed that each type of RLC entity is configured with one RLC entity), and each type of RLC is used to transmit service data of the corresponding service type.
  • the i in RLC i is the RLC entity configured for DRB for offloading.
  • MCG primary cell group
  • SCG secondary cell group
  • i represents the RLC type or RLC entity.
  • i can be 0, 1, or 2.
  • the RLC i entity When the corresponding bit value of RLC i is 1, the RLC i entity activates the service offload function; when the corresponding bit value of RLC i is 0, the RLC i entity deactivates the service offload function.
  • Fig. 7 illustrates an information field structure for indicating whether to activate the PDCP packet copy function. As shown in Fig. 7, the information field includes: a first part of bits and a second part of bits.
  • the first part of bits is used to indicate the identifier of the first RLC entity type (RLC ID), and it is assumed that the length of the first part of bits is 5 bits.
  • the second part of bits is used to indicate whether the second RLC entity activates the packet copy function. It is assumed that the second part of bits is 3 bits long.
  • the i in RLC i is configured for the second RLC entity, such as the logical channel identifier of the secondary RLC entity in ascending order in the primary cell group (MCG) and the secondary cell group (SCG), that is, i represents the index of the second RLC entity. In Figure 7, i can be 0, 1, or 2. Three RLC entities are used as an example here.
  • the first RLC entity and the second RLC entity may be RLC entities of the same type.
  • the first RLC entity may also be referred to as a duplicated RLC entity or a primary RLC entity
  • the second RLC entity may also be referred to as a duplicated RLC entity or a secondary RLC entity.
  • the RLC i entity When the corresponding bit value of RLC i is 1, the RLC i entity activates the packet copy function, and the service data of the first RLC entity can be copied and sent to the RLC i entity; when the corresponding bit value of RLC i is 0, the RLC i entity deactivates the packet copy function.
  • the configuration of whether to activate the PDCP packet replication function can be refined to the RLC entity, and the first RLC entity (or the replicated RLC entity) is configured to activate or deactivate the packet replication function of the second RLC entity (or the replicated RLC entity), providing instructions for service diversion of the user equipment 102.
  • the embodiment of the present disclosure provides a method for sending configuration information, which is performed by the network device 101.
  • the method includes steps S501 to S502-1, specifically:
  • Step S501 The network device 101 sends configuration information to the user equipment 102, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entity.
  • Step S502-1 Receive a notification message from a user equipment, where the notification message is used to indicate that the number of times that the RLC entity used for the first function retransmits service data reaches a maximum number of retransmissions.
  • step S502-1 may include: when receiving a notification message from the user equipment 102, the network device 101 sends first indication information to the user equipment 102, where the first indication information is used to indicate to deactivate a first function of the RLC entity corresponding to the notification message.
  • the first function includes a service offloading function or a PDCP packet duplication function.
  • the notification message when the notification message is received, it indicates that the number of times the RLC entity used for the first function retransmits the service data has reached the maximum number of retransmissions, which indicates that the RLC entity can no longer perform retransmissions, or that the communication status of the RLC entity may have problems or failures, and may not be suitable for offloading.
  • the network device 101 can send the first indication information in time to instruct the user equipment 102 to deactivate the first function of the RLC entity.
  • the user equipment 102 can adjust the diversion mode in time, for example, no longer send service data to the RLC entity that deactivates the first function, but send service data of the service type corresponding to the RLC entity that deactivates the first function to the default RLC entity, so as to ensure that the normal diversion of the service data of the service type can still be achieved, and the data transmission efficiency is guaranteed.
  • the user equipment 102 when the RLC entity used for the service offloading function reaches the maximum number of retransmissions, the user equipment 102 sends a notification message to the network device 101 .
  • the user equipment 102 when the RLC entity used for the packet duplication function reaches a maximum number of retransmissions, the user equipment 102 sends a notification message to the network device 101 .
  • the network device 101 may dynamically deactivate the first function of the corresponding RLC entity upon receiving a notification message from the user equipment 102 .
  • FIG. 8 is a method for receiving configuration information according to an exemplary embodiment. As shown in FIG. 8 , the method includes steps S801 to S802, specifically:
  • Step S801 The user equipment 102 receives configuration information sent by the network device 101, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • Step S802 The user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.
  • N is related to the type of business data.
  • the PDCP layer of the user equipment 102 splits the service data according to the service type, and sends the corresponding type of service data to different types of RLC entities respectively.
  • the service data may be XR service data.
  • each type of RLC entity includes at least one RLC entity.
  • each type of RLC entity includes one RLC entity.
  • the one RLC entity may have different conditions.
  • the RLC entity in unconfirmed transmission mode, when the RLC entity is capable of bidirectional transmission (supporting uplink and downlink), the RLC entity is a UM RLC entity.
  • the one RLC entity refers to one RLC entity for each transmission direction, that is, the one RLC entity is an uplink UM RLC entity and a downlink UM RLC entity.
  • the RLC entity is an AM RLC entity.
  • each type of RLC entity includes multiple RLC entities. At this time, the multiple RLC entities still have different situations according to different transmission modes.
  • the multiple RLC entities include two UM RLC entities.
  • the multiple RLC entities include four UM RLC entities, including two uplink UM RLC entities and two downlink UM RLC entities.
  • the multiple RLC entities include two AM RLC entities.
  • the PDCP entity of the user equipment 102 receives service data sent by the network device 101 through a higher layer, and sends the service data to at least one corresponding type of RLC entity.
  • the user equipment 102 obtains the N types of RLC entities associated with the PDCP entity based on the configuration information of the network device 101, so that the user equipment 102 can effectively divert the service data according to the configuration information to improve the efficiency of transmitting the service data.
  • the embodiment of the present disclosure provides a method for receiving configuration information, which is performed by the user equipment 102.
  • the method includes steps S801 to S802-1, specifically:
  • Step S801 The user equipment 102 receives configuration information sent by the network device 101, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • N is the number of service types of service data
  • the configuration information is also used to configure each type of RLC entity to transmit service data of the corresponding service type.
  • Step S802-1 The user equipment 102 sends the service data to an RLC entity of a type corresponding to the service type according to the configuration information and the service type of the service data.
  • each type of RLC entity includes at least one RLC entity.
  • the service type of the service data may include: I frame and P frame.
  • one type of RLC entity corresponds to a first logical channel and is used to transmit I frame service data; the other type of RLC entity corresponds to a second logical channel and is used to transmit P frame service data.
  • the service type of the service data may include: data of different streams or sub-streams, for example, first sub-stream service data and second sub-stream service data.
  • one type of RLC entity is used to transmit the first sub-stream service data
  • the other type of RLC entity is used to transmit the second sub-stream service data.
  • the service type of the service data may include: PDCP control data and PDCP data protocol data unit.
  • the N types of RLC entities are recorded as a first type RLC entity, a second type RLC entity, ..., an Nth type RLC entity.
  • the first RLC entity or the second RLC entity may be specified by a network device or agreed upon by a protocol
  • the network device may specify or agree upon a primary RLC entity and a secondary RLC entity (RLC entity other than the primary RLC entity);
  • the default RLC entity may be specified by the network device or agreed upon by the protocol
  • the first RLC entity is used to transmit PDCP control data
  • the second RLC entity is used to transmit PDCP data protocol data units.
  • the first RLC entity is a primary RLC entity.
  • the user equipment 102 performs effective data diversion according to the service type of the service data.
  • the embodiment of the present disclosure provides a method for receiving configuration information, which is performed by the user equipment 102.
  • the method includes steps S801 to S802-2, specifically:
  • Step S801 The user equipment 102 receives configuration information sent by the network device 101, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • the configuration information is also used to configure a default RLC entity, and the default RLC entity is used to transmit the first service.
  • Step S802-2 When the service data is the first service, the user equipment 102 sends the service data to the default RLC entity.
  • the default RLC entity may be one type among the N types of RLC entities, or may be additionally configured outside the N types of RLC entities.
  • the default RLC entity is the first RLC entity or the master RLC entity or other RLC entity designated by the network device.
  • the first service is service data of a specified service type, for example, the first service is PDCP control data.
  • the first service is service data for which no corresponding RLC entity is configured.
  • the user equipment 102 may deliver service data of a specified service type, or service data for which a corresponding RLC entity is not configured, to a default RLC entity to implement data offloading.
  • the embodiment of the present disclosure provides a method for receiving configuration information, which is performed by the user equipment 102.
  • the method includes steps S801 to S802-3, specifically:
  • Step S801 The user equipment 102 receives configuration information sent by the network device 101, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • the configuration information is also used to configure a default RLC entity, and the default RLC entity is used to transmit the first service.
  • Step S802-3 When the RLC entity corresponding to the service data deactivates the service offload function, the user equipment 102 offloads and sends the service data to the default RLC entity.
  • the user equipment 102 when the user equipment 102 receives the configuration information, it is considered that the N types of RLC entities in the configuration information have activated the service offloading function.
  • the configuration information includes indication identifiers corresponding to N types of RLC entities, and the indication identifiers are used to indicate whether the first function is activated for some or all types of RLC entities.
  • the user equipment 102 learns whether the first function is activated for N types of RLC entities according to the following step S800-11:
  • Step S800-11 The user equipment 102 determines whether to activate the service offloading function for some or all types of RLC entities according to the indication identifier in the configuration information.
  • the indication flag occupies one bit, and the same bit is used in the configuration information to uniformly indicate whether N types of RLC entities activate the first function such as the service offload function, that is, whether all types of RLC entities activate the first function.
  • the N types of RLC entities when the bit corresponding to the indication flag is 1, the N types of RLC entities all activate the service offload function. For another example, when the bit corresponding to the indication flag is 0, the N types of RLC entities all deactivate the service offload function.
  • the indication flag occupies multiple bits.
  • the configuration information includes bits corresponding to each type of RLC entity, thereby indicating whether each type of RLC entity activates the first function such as the service offloading function.
  • the RLC entity of this type activates the first function such as the service offload function; when the bit corresponding to the indication identifier of any type of RLC entity is 0, the RLC entity of this type deactivates the service offload function.
  • the RLC entity of this type deactivates the service offload function.
  • all RLC entities of this type activate the first function.
  • the indication flag corresponds to indicating the activation status of the first function of all types of RLC entities. For example, when the values of the multiple bits are all 1, it indicates that all types of RLC entities have activated the first function.
  • the indicator occupies multiple bits, and each bit is used to indicate: activating or deactivating the first function of each RLC entity.
  • the configuration information includes bits corresponding to each RLC entity to indicate whether each RLC entity activates the first function such as the service diversion function.
  • the RLC entity when the bit corresponding to the indication identifier of any RLC entity is 1, the RLC entity activates the first function such as the service diversion function; when the bit corresponding to the indication identifier of any RLC entity is 0, the RLC entity deactivates the first function.
  • the user equipment 102 determines whether to activate the first function, such as the service offloading function, for some or all types of RLC entities according to the received first indication information. This method can be referred to the description of the following embodiment.
  • the PDCP of the user equipment 102 may deliver service data of a corresponding service type to an associated RLC entity.
  • the PDCP of the user equipment 102 may deliver service data of a service type corresponding to the RLC entity to a default RLC entity, thereby still ensuring that offloading of this type of service data can be achieved.
  • the user equipment 102 obtains information based on the configuration information as to whether some or all RLC entities have activated the first function such as the service diversion function. When the service diversion function of any RLC entity is deactivated, the user equipment 102 may divert data to the default RLC entity.
  • the embodiment of the present disclosure provides a method for receiving configuration information, which is performed by the user equipment 102.
  • the method includes steps S801, S800-21, S800-22 and S802, specifically:
  • Step S801 The user equipment 102 receives configuration information sent by the network device 101, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • Step S800-21 the user equipment 102 receives first indication information sent by the network equipment 101, where the first indication information is used to indicate activation or deactivation of a first function of some types or all types of RLC entities.
  • Step S800-22 The user equipment 102 determines whether to activate the first function for some types or all types of RLC entities according to the first indication information.
  • Step S802 The user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.
  • the first indication information may uniformly indicate whether the N types of RLC entities activate the first function, that is, indicate whether all types of RLC entities activate the first function. For example, one bit is used to uniformly indicate whether all the N types of RLC entities activate the first function. When a certain type of RLC entity indicates to activate the first function, all RLC entities of the type activate the first function.
  • the first indication information indicates whether each type of RLC entity in all N types or some types of N types activates the first function. For example, each type of RLC entity has a corresponding bit, and each bit indicates whether the RLC entity of the corresponding type activates the first function. When a certain type of RLC entity indicates to activate the first function, each RLC entity under the type activates the first function.
  • the first indication information indicates whether each RLC entity activates the first function. For example, each RLC entity has a corresponding bit, and each bit indicates whether the corresponding RLC entity activates the first function.
  • the user equipment 102 receives the first indication information, which may be receiving DCI sent by the network device 101, and acquiring the first indication information in the DCI.
  • the user equipment 102 receives the first indication information, which may be a MAC CE signaling sent by the network device 101, where the MAC CE signaling includes an information field for indicating the first indication information.
  • the first indication information which may be a MAC CE signaling sent by the network device 101, where the MAC CE signaling includes an information field for indicating the first indication information.
  • the first function includes a service diversion function or a packet replication function.
  • step S802 when the first function is a service offloading function, the implementation of step S802 may refer to the following step S802-3, specifically:
  • Step S802-3 When the RLC entity corresponding to the service data deactivates the service offload function, the user equipment 102 offloads and sends the service data to the default RLC entity.
  • the user equipment 102 obtains information based on the first indication whether some or all of the RLC entities have activated the first function, so that the diversion method can be adjusted in time.
  • the embodiment of the present disclosure provides a method for receiving configuration information, which is performed by the user equipment 102.
  • the method includes steps S801, S800-21', S800-22' and S802, specifically:
  • Step S801 The user equipment 102 receives configuration information sent by the network device 101, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • Step S800-21’ the user equipment 102 receives the MAC CE signaling sent by the network equipment 101, and the MAC CE signaling includes an information field for indicating the first indication information.
  • Step S800-22' when at least one bit in the information field is a first value, the user equipment 102 determines that a first function of the RLC entity corresponding to the at least one bit is activated.
  • Step S802 The user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.
  • the information field includes at least one of the following:
  • the information field includes a bit for indicating the activation state of the first function, uniformly indicating whether all types of RLC entities activate the first function.
  • the bit when the bit is a first value (such as 1), it indicates that all types of RLC entities have activated the first function; when the bit is a second value (such as 0), it indicates that all types of RLC entities have deactivated the first function. And the activation state of the first function of any type of RLC entity is applicable to all RLC entities of that type.
  • a first value such as 1
  • a second value such as 0
  • the information field includes more than one bit for indicating the activation state of the first function, such as the information field including bits corresponding to each type of RLC entity, as shown in FIG6 .
  • the RLC entity of this type When the bit corresponding to any type of RLC entity is a first value (such as 1), the RLC entity of this type activates a first function such as a service diversion function. When the bit corresponding to the indication identifier of any type of RLC entity is a second value (such as 0), the RLC entity of this type deactivates the first function. When a certain type of RLC entity indicates to activate the first function, all RLC entities of this type activate the first function.
  • the information field includes more than one bit for indicating the activation state of the first function.
  • each RLC entity corresponds to one bit. In this case, reference may be made to FIG. 7 .
  • the RLC entity When the bit corresponding to any RLC entity is a first value (such as 1), the RLC entity activates a first function such as a service offloading function. When the bit corresponding to any RLC entity is a second value (such as 0), the RLC entity deactivates the first function.
  • a first value such as 1
  • a second value such as 0
  • the first function includes a service diversion function or a packet replication function.
  • the network device 101 dynamically indicates the first function of activating or deactivating part or all of the RLC entities through MAC CE signaling, and the user device 102 promptly obtains the activation status of the RLC entity according to the MAC CE signaling and promptly adjusts the diversion method.
  • the embodiment of the present disclosure provides a method for receiving configuration information, which is performed by the user equipment 102.
  • the method includes steps S801, S800-21, S800-22, S802 and S803, specifically:
  • Step S801 The user equipment 102 receives configuration information sent by the network device 101, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • Step S800 - 21 the user equipment 102 receives the first indication information sent by the network equipment 101 .
  • Step S800-22 The user equipment 102 determines whether to activate the first function for some types or all types of RLC entities according to the first indication information.
  • Step S802 The user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.
  • Step S803 when the number of times the RLC entity used for the first function retransmits service data reaches a maximum number of retransmissions, the user equipment 102 sends a notification message to the network device 101 .
  • the first function includes a service offloading function or a PDCP packet duplication function.
  • the user equipment 102 when the RLC entity used for the service offloading function reaches the maximum number of retransmissions, the user equipment 102 sends a notification message to the network device 101. At this time, it indicates that the RLC entity can no longer perform retransmissions, or the communication status of the RLC entity may have problems or failures, and may not be suitable for offloading.
  • the user equipment 102 when the RLC entity used for the packet duplication function reaches a maximum number of retransmissions, the user equipment 102 sends a notification message to the network device 101 .
  • the network device 101 may dynamically deactivate the first function of the corresponding RLC entity upon receiving a notification message from the user equipment 102 .
  • the user equipment 102 when the RLC entity used for the first function reaches the maximum number of retransmissions, the user equipment 102 can report to the network device 101 in a timely manner, so that the network device 101 can adjust the activation state, such as deactivating the first function of a certain RLC entity.
  • the user equipment 102 can adjust the diversion mode in a timely manner, for example, no longer send service data to the RLC entity that deactivates the first function, but send the service data of the service type corresponding to the RLC entity that deactivates the first function to the default RLC entity, so as to ensure that the normal diversion of the service data of the service type can still be achieved, and the data transmission efficiency is guaranteed.
  • the network device 101 configures the user equipment 102: the PDCP entity corresponds to N types of RLC entities, where N corresponds to the service type classification, such as the first type of service data, the second type of service data, and the Nth type of service data.
  • the service type classification such as the first type of service data, the second type of service data, and the Nth type of service data.
  • classifying service types including but not limited to: distinguishing according to the importance of service data, distinguishing according to the attributes of service data, distinguishing according to the sub-flow (Sub Qos flow) or QoS flow to which the service data belongs, distinguishing according to the priority level of service data, distinguishing according to the priority level of service data, distinguishing according to the reliability level of service data, or distinguishing according to the purpose of service data. Please refer to the description involved in the above-mentioned embodiment.
  • the network device 101 specifies the transmission RLC entity for different service types, that is, performs a diversion operation.
  • the network device 101 configures two types of RLC entities, namely, a first type RLC entity and a second type RLC entity; the two types of RLC entities correspond to: the transmission of first service type data such as I frame service data and the transmission of second service type data such as P frame service data.
  • the first type RLC entity corresponds to logical channel 1, which is used for the transmission of I frame service data
  • the second type RLC entity corresponds to logical channel 2, which is used for the transmission of P frame service data.
  • the PDCP layer when the user equipment 102 sends data in the uplink, the PDCP layer needs to deliver it to the corresponding type of transmission RLC entity transmission according to the different service types of the service data.
  • the PDCP layer may determine the service type based on each data packet and deliver it; it may also make batch determinations based on data packet sets. For example, after determining the diversion based on the service type of a data packet in the data packet set, the other data packets in the data packet set will also be delivered to the same type of transmission RLC entity transmission. In this way, there is no need to make diversion decisions for each data packet, which improves decision efficiency.
  • each type of RLC entity corresponds to at least one UM entity (supporting uplink and downlink), or at least two UM entities (supporting only uplink or downlink), or at least one AM entity.
  • the network device 101 specifies that the transmission RLC entities for different service types may belong to different MN or SN nodes, or to the same MN or SN node, or to the same cell or different cells.
  • a specified type of RLC entity (such as a first RLC entity or a main RLC entity) can transmit a specified type of service, such as a control PDU.
  • a specified type of service such as a control PDU.
  • a default RLC entity can be used for transmission, such as using the first RLC entity or the main RLC entity.
  • the service data can be transmitted in the same cell or carrier.
  • Example 1 The network device 101 is configured as follows: the first RLC entity is used for type 1 data transmission, the second RLC entity is used for type 2 data transmission, and so on.
  • Example 2 The network device 101 is configured as follows: the first RLC entity is used for type 1 data transmission and/or control PDU, the second RLC entity is used for type 2 data transmission, and the third RLC entity is used for type 3 data transmission.
  • each RLC entity is only for reference and distinction, but not for limiting the RLC entity.
  • the first RLC entity may also be called a primary RLC entity
  • the second RLC entity or the third RLC entity may also be called a secondary RLC entity.
  • the transmission status of the service offloading is configured through the network device 101 or agreed upon through a protocol, that is, whether the service offloading function is enabled, activated, or used.
  • the network device 101 performs the configuration of Example 1, and it is considered that the service diversion function is enabled or activated. That is, the high-level layer performs the configuration in Example 1, and it is considered that the service diversion function is enabled; there is no need to activate the function later.
  • the network device 101 indicates whether to enable the initial state of the service offloading function during configuration. For example, during configuration, the service offloading function of the first RLC entity (for type 1 data transmission) is enabled, and the service offloading function of the second RLC entity (for type 2 data transmission) is disabled, etc.
  • Example 1 Configuration of the network device 101: first RLC entity (for type 1 data transmission), service offloading function activated; second RLC entity (for type 2 data transmission), service offloading function activated, ...
  • Example 2 Configuration of network device 101: first RLC entity (for type 1 data transmission and/or control PDU), service diversion function activated; second RLC entity (for type 2 data transmission), service diversion function activated; third RLC entity or (for type 3 data transmission), service diversion function not activated;....
  • each RLC entity is for reference and distinction only and is not limiting.
  • the first RLC entity may also be called a primary RLC entity
  • the second RLC entity may also be called a secondary RLC entity 1
  • the third RLC entity may also be called a secondary RLC entity 2.
  • the service data associated with the RLC entity whose offload function is deactivated may be transmitted using a default RLC entity, such as using a first RLC entity or a primary RLC entity;
  • type 3 data transmission will be transmitted using the primary RLC entity.
  • the MAC CE method, the DCI method, or the RRC method may be used to dynamically activate (or enable/disable) the diversion state or the service diversion function.
  • the RRC reconfiguration message may indicate the initial state of whether the RLC entity diversion function is activated.
  • Example 1 MAC CE indicates activation/deactivation of the service offloading function.
  • the following example is given using three types of RLC entities, but is not limited to the use of more bits than in the example.
  • Figure 6 is a schematic diagram of MAC CE instructing the RLC entity to activate/deactivate the service splitting function (PDCP split).
  • the information field includes: a first part of bits and a second part of bits.
  • the first part of the bits is used to indicate the identifier (DRB ID) of the data radio bearer (DRB), assuming that the length of the first part of the bits is 5 bits.
  • DRB can correspond to service data of multiple service types, that is, it can correspond to multiple types of RLC entities.
  • the second part of the bits is used to indicate whether the service diversion function is activated for each type of RLC entity.
  • the second part of the bits is 3 bits long, and each type of RLC entity occupies 1 bit (assuming that one RLC entity is configured for each type of RLC entity).
  • Each type of RLC is used to transmit service data of the corresponding service type.
  • the i in RLC i is the RLC entity configured for diversion for DRB.
  • the logical channel identifier of the secondary RLC entity in ascending order in the main cell group (MCG) and the secondary cell group (SCG), that is, i represents the RLC type or RLC entity.
  • i can be 0, 1, or 2.
  • the RLC i entity When the corresponding bit value of RLC i is 1, the RLC i entity activates the service offload function; when the corresponding bit value of RLC i is 0, the RLC i entity deactivates the service offload function.
  • Example 2 when the maximum number of retransmissions is reached on the RLC entity used for service offloading, the network device is notified.
  • the second RLC entity will notify the base station when reaching the maximum number of retransmissions, such as sending a notification message to the base station.
  • the base station can perform subsequent actions, such as deactivating the offloading function of the RLC entity.
  • the activation indication of the service diversion function can be controlled by each diversion RLC entity (Per RLC entity) (refer to the above embodiment), or all diversion RLC entities can be uniformly controlled.
  • the network device sends an instruction to activate or deactivate the diversion function of all diversion RLC entities at the same time.
  • the network device 101 may activate the PDCP packet copy function for the RLC entity corresponding to a specific service.
  • the granularity of activating PDCP packet replication can be refined to the RLC entity, that is, several RLC entities (these several entities can be called: the RLC entity or the second RLC entity that activates packet replication, or simply referred to as the replicated RLC entity or other RLC entities other than the main RLC entity) can be configured for the RLC entity (the entity can be called: the RLC entity or the first RLC entity that activates PDCP packet replication, or simply referred to as the replicated RLC entity or the main RLC entity) for packet replication.
  • the packet duplication function of the RLC entity may be activated or deactivated.
  • Example 1 Packet replication activation and deactivation for a certain RLC entity:
  • Figure 7 is a schematic diagram of MAC CE instructing the RLC entity to activate/deactivate PDCP packet duplication.
  • the information field includes: a first part of bits and a second part of bits.
  • the first part of bits is used to indicate the identifier of the first RLC entity type (RLC ID), assuming that the length of the first part of bits is 5 bits.
  • the second part of bits is used to indicate whether the second RLC entity activates the packet copy function, assuming that the second part of bits is 3 bits long.
  • the i in RLC i is configured for the second RLC entity, such as the logical channel identifier of the secondary RLC entity in ascending order in the primary cell group (MCG) and the secondary cell group (SCG), that is, i represents the index of the second RLC entity.
  • MCG primary cell group
  • SCG secondary cell group
  • the RLC i entity When the corresponding bit value of RLC i is 1, the RLC i entity activates the packet copy function, and the service data of the first RLC entity (or the copied RLC entity) can be copied and sent to the RLC i entity; when the corresponding bit value of RLC i is 0, the RLC i entity deactivates the packet copy function.
  • the maximum number of retransmissions is reached on the second RLC entity, and the network device is notified.
  • the base station when the second RLC entity corresponding to a certain RLC entity (first RLC entity) reaches the maximum number of retransmissions, the base station will be notified, such as by sending a notification message.
  • the base station can perform subsequent actions, such as deactivating the packet duplication function of the second RLC entity.
  • the packet copy function activation indication of the shunt RLC entity can be controlled at the granularity of each RLC shunt entity, or can be controlled according to each second RLC entity corresponding to each shunt RLC entity (first RLC entity) (such as the above embodiment), or unified control is performed, for example:
  • the network device 101 uses one control instruction to simultaneously copy the activation/deactivation packet of a certain RLC shunt entity, or the network device 101 uses one control instruction to simultaneously copy the activation/deactivation packet of all RLC shunt entities.
  • the embodiment of the present disclosure also provides a device for sending configuration information, which can have the functions of the network device 101 in the above method embodiment, and can be used to execute the steps performed by the network device 101 provided by the above method embodiment.
  • the function can be implemented 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 device 900 shown in FIG9 may be used as the network device 101 involved in the above method embodiment, and execute the steps performed by the network device 101 in the above method embodiment.
  • the device 900 may include a transceiver module 901, wherein the transceiver module 901 may be used to support the communication device to communicate, and the transceiver module 901 may have a wireless communication function, for example, being able to communicate wirelessly with other communication devices through a wireless air interface.
  • the transceiver module 901 When executing the steps implemented by the network device 101, the transceiver module 901 is configured to send configuration information to the user equipment, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • the communication device When the communication device is a network device 101, its structure can also be shown in Figure 10. Take the base station as an example to illustrate the structure of the communication device.
  • the device 1000 includes a memory 1001, a processor 1002, a transceiver component 1003, and a power supply component 1006.
  • the memory 1001 is coupled to the processor 1002, and can be used to store the programs and data necessary for the communication device 1000 to implement various functions.
  • the processor 1002 is configured to support the communication device 1000 to perform the corresponding functions in the above method, and the functions can be implemented by calling the program stored in the memory 1001.
  • the transceiver component 1003 can be a wireless transceiver, which can be used to support the communication device 1000 to receive signaling and/or data through a wireless air interface, and send signaling and/or data.
  • the transceiver component 1003 may also be referred to as a transceiver unit or a communication unit.
  • the transceiver component 1003 may include a radio frequency component 1004 and one or more antennas 1005, wherein the radio frequency component 1004 may be a remote radio unit (RRU), which may be specifically used for transmission of radio frequency signals and conversion of radio frequency signals into baseband signals, and the one or more antennas 1005 may be specifically used for radiation and reception of radio frequency signals.
  • RRU remote radio unit
  • the processor 1002 can perform baseband processing on the data to be sent, and then output the baseband signal to the RF unit.
  • the RF unit performs RF processing on the baseband signal and then sends the RF signal in the form of electromagnetic waves through the antenna.
  • the RF unit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1002.
  • the processor 1002 converts the baseband signal into data and processes the data.
  • the embodiment of the present disclosure also provides a device for receiving configuration information, which may have the functions of the user equipment 102 in the above method embodiment, and may be used to execute the steps performed by the user equipment 102 provided in the above method embodiment.
  • the function may be implemented 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 device 1100 shown in FIG11 may be used as the user equipment 102 involved in the above method embodiment, and execute the steps performed by the user equipment 102 in the above method embodiment.
  • the device 1100 may include a transceiver module 1101 and a processing module 1102 coupled to each other, wherein the transceiver module 1101 may be used to support the communication device to communicate, and the transceiver module 1101 may have a wireless communication function, for example, being able to communicate wirelessly with other communication devices through a wireless air interface.
  • the processing module 1102 may be used for the communication device to perform processing operations, such as generating information/messages to be sent, or processing received signals to obtain information/messages.
  • the transceiver module 1101 When executing the steps implemented by the user equipment 102, the transceiver module 1101 is configured to receive configuration information sent by the network device, where the configuration information includes N types of radio link control RLC entities corresponding to the packet data convergence protocol PDCP entities in the user equipment.
  • the processing module 1102 is configured to send service data to at least one type of RLC entity according to the configuration information.
  • the device 1200 may be a mobile phone, a computer, a digital broadcast terminal, a message transceiver, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • the device 1200 may include one or more of the following components: a processing component 1202 , a memory 1204 , a power component 1206 , a multimedia component 1208 , an audio component 1210 , an input/output (I/O) interface 1212 , a sensor component 1214 , and a communication component 1216 .
  • a processing component 1202 a memory 1204 , a power component 1206 , a multimedia component 1208 , an audio component 1210 , an input/output (I/O) interface 1212 , a sensor component 1214 , and a communication component 1216 .
  • the processing component 1202 generally controls the overall operation of the device 1200, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 1202 may include one or more processors 1220 to execute instructions to perform all or part of the steps of the above-described method.
  • the processing component 1202 may include one or more modules to facilitate the interaction between the processing component 1202 and other components.
  • the processing component 1202 may include a multimedia module to facilitate the interaction between the multimedia component 1208 and the processing component 1202.
  • the memory 1204 is configured to store various types of data to support operations on the device 1200. Examples of such data include instructions for any application or method operating on the device 1200, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 1204 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 1206 provides power to the various components of the device 1200.
  • the power supply component 1206 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 1200.
  • the multimedia component 1208 includes a screen that provides an output interface between the device 1200 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 1208 includes a front camera and/or a rear camera. When the device 1200 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 1210 is configured to output and/or input audio signals.
  • the audio component 1210 includes a microphone (MIC), and when the device 1200 is in an operation 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 1204 or sent via the communication component 1216.
  • the audio component 1210 also includes a speaker for outputting audio signals.
  • I/O interface 1212 provides an interface between processing component 1202 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 1214 includes one or more sensors for providing various aspects of the status assessment of the device 1200.
  • the sensor assembly 1214 can detect the open/closed state of the device 1200, the relative positioning of components, such as the display and keypad of the device 1200, the sensor assembly 1214 can also detect the position change of the device 1200 or a component of the device 1200, the presence or absence of user contact with the device 1200, the orientation or acceleration/deceleration of the device 1200, and the temperature change of the device 1200.
  • the sensor assembly 1214 can include a proximity sensor configured to detect the presence of a nearby object without any physical contact.
  • the sensor assembly 1214 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1214 can also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 1216 is configured to facilitate wired or wireless communication between the device 1200 and other devices.
  • the device 1200 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 1216 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 1216 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 device 1200 can 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-mentioned methods.
  • 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-mentioned methods.
  • a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1204 including instructions, and the instructions can be executed by the processor 1220 of the device 1200 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 network device sends configuration information to the user equipment to configure the N types of RLC entities associated with the PDCP entity to the user equipment, so that the user equipment can effectively divert the service data according to the configuration information to improve the efficiency of transmitting the service data.

Landscapes

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

Abstract

本公开提供一种传输配置信息的方法、装置及可读存储介质，所述方法包括：向用户设备发送配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。本公开的方法中，网络设备向用户设备发送配置信息，以向用户设备配置PDCP实体所关联的N种RLC实体。从而用户设备可以根据配置信息对业务数据进行有效分流，以提升传输业务数据的效率。

Description

一种传输配置信息的方法、装置及可读存储介质 技术领域
本公开涉及无线通信技术领域，尤其涉及一种传输配置信息的方法、装置及可读存储介质。
背景技术
在第五代(5th-Generation，5G)无线通信系统中，需要支持扩展现实(eXtended Reality，XR)业务类型。在XR业务中，可采用服务质量(Quality of Service，QoS)流传输进行数据包传输。传输过程中，非接入层(Non-access Stratum，NAS)可能不进行数据包的分流，在同一个QoS流(Qos flow)中包含不同数据。因此，需解决此XR业务场景下的数据分流问题。
发明内容
本公开提供了一种传输配置信息的方法、装置及可读存储介质。
第一方面，本公开提供一种发送配置信息的方法，被网络设备执行，所述方法包括：
向用户设备发送配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
在一些可能的实施方式中，所述N为业务数据的业务类型数量，所述配置信息还用于配置每种类型的RLC实体传输对应业务类型的业务数据。
在一些可能的实施方式中，所述配置信息还用于配置默认RLC实体，所述默认RLC实体用于传输第一业务。
在一些可能的实施方式中，每种类型的RLC实体包括至少一个RLC实体。
在一些可能的实施方式中，所述配置信息包括所述N种类型的RLC实体对应的指示标识，所述指示标识用于指示部分类型或全部类型RLC实体是否激活第一功能。
在一些可能的实施方式中，所述方法还包括：
向所述用户设备发送第一指示信息，所述第一指示信息用于指示激活或去激活部分类型或全部类型RLC实体的第一功能。
在一些可能的实施方式中，所述第一功能包括业务分流功能或者包复制功能。
在一些可能的实施方式中，所述向所述用户设备发送第一指示信息，包括：
向用户设备发送下行控制信息DCI，所述DCI包括所述第一指示信息；或者，
向用户设备媒体发送接入控制层控制单元MAC CE信令，所述MAC CE信令包括用于指示所述第一指示信息的信息域。
在一些可能的实施方式中，所述信息域至少包含以下一种：全部类型RLC实体对应的比特位，每种类型RLC实体分别对应的比特位，每个RLC实体分别对应的比特位；
在所述比特位为第一值时，指示激活所述比特位对应的RLC实体的所述第一功能。
在一些可能的实施方式中，所述方法还包括：
接收所述用户设备的通知消息，所述通知消息用于指示用于第一功能的RLC实体重传业务数据的次数达到最大重传次数。
第二方面，本公开提供一种接收配置信息的方法，被用户设备执行，所述方法包括：
接收网络设备发送的配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体；
根据所述配置信息，向至少一种类型RLC实体发送业务数据。
在一些可能的实施方式中，所述N为业务数据的业务类型数量，所述配置信息还用于配置每种类型的RLC实体传输对应业务类型的业务数据；
所述根据所述配置信息，向至少一种类型RLC实体发送业务数据，包括：
根据所述配置信息以及所述业务数据的业务类型，向与业务类型对应类型的RLC实体分流发送所述业务数据。
在一些可能的实施方式中，所述配置信息还用于配置默认RLC实体，所述默认RLC实体用于传输第一业务。
在一些可能的实施方式中，所述根据所述配置信息，向至少一种类型RLC实体发送业务数据，包括：
在所述业务数据为第一业务时，向所述默认RLC实体分流发送所述业务数据。
在一些可能的实施方式中，所述根据所述配置信息，向至少一种类型RLC实体发送业务数据，包括：
在所述业务数据对应的RLC实体去激活业务分流功能时，向所述默认RLC实体分流发送所述业务数据。
在一些可能的实施方式中，所述方法还包括：
根据所述配置信息中的指示标识，确定部分类型或全部类型RLC实体是否激活第一功能。
在一些可能的实施方式中，所述方法还包括：
接收所述网络设备发送的第一指示信息，所述第一指示信息用于指示激活或去激活部分类型或全部类型RLC实体的第一功能；
根据所述第一指示信息，确定部分类型或全部类型RLC实体是否激活第一功能。
在一些可能的实施方式中，所述第一功能包括业务分流功能或者包复制功能。
在一些可能的实施方式中，所述接收所述网络设备发送的第一指示信息，包括：
接收所述网络设备发送的MAC CE信令，所述MAC CE信令包括用于指示所述第一指示信息的信息域。
在一些可能的实施方式中，所述根据所述第一指示信息，确定部分类型或全部类型 RLC实体是否激活第一功能，包括：
在所述信息域中至少一个比特位为第一值时，确定所述至少一个比特位对应的RLC实体的第一功能激活。
在一些可能的实施方式中，所述方法还包括：
在用于第一功能的RLC实体重传业务数据的次数达到最大重传次数时，向所述网络设备发送通知消息。
第三方面，本公开提供一种发送配置信息的装置，该装置可用于执行上述第一方面或第一方面的任一可能的设计中由网络设备执行的步骤。该网络设备可通过硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各方法中的各功能。
在通过软件模块实现第三方面所示装置时，该装置可包括收发模块，其中，收发模块可用于支持通信装置进行通信。
在执行上述第一方面所述步骤时，收发模块，被配置为向用户设备发送配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
第四方面，本公开提供一种接收配置信息的装置，该装置可用于执行上述第二方面或第二方面的任一可能的设计中由用户设备执行的步骤。该用户设备可通过硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各方法中的各功能。
在通过软件模块实现第四方面所示装置时，该装置可包括相互耦合的收发模块以及处理模块，其中，收发模块可用于支持通信装置进行通信，处理模块可用于通信装置执行处理操作，如生成需要发送的信息/消息，或对接收的信号进行处理以得到信息/消息。
在执行上述第二方面所述步骤时，收发模块，被配置为接收网络设备发送的配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。处理模块，被配置为根据所述配置信息，向至少一种类型RLC实体发送业务数据。
第五方面，本公开提供一种通信装置，包括处理器以及存储器；所述存储器用于存储计算机程序；所述处理器用于执行所述计算机程序，以实现第一方面或第一方面的任意一种可能的设计。
第六方面，本公开提供一种通信装置，包括处理器以及存储器；所述存储器用于存储计算机程序；所述处理器用于执行所述计算机程序，以实现第二方面或第二方面的任意一种可能的设计。
第七方面，本公开提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令(或称计算机程序、程序)，当其在计算机上被调用执行时，使得计算机执行上述第一方面或第一方面的任意一种可能的设计。
第八方面，本公开提供一种计算机可读存储介质，所述计算机可读存储介质中存储有 指令(或称计算机程序、程序)，当其在计算机上被调用执行时，使得计算机执行上述第二方面或第二方面的任意一种可能的设计。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处所说明的附图用来提供对本公开实施例的进一步理解，构成本申请的一部分，本公开实施例的示意性实施例及其说明用于解释本公开实施例，并不构成对本公开实施例的不当限定。在附图中：
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开实施例的实施例，并与说明书一起用于解释本公开实施例的原理。
图1为本公开实施例提供的一种通信系统架构的示意图；
图2为本公开实施例提供的一种协议层结构示意图；
图3为根据一示例性实施例示出的一种传输配置信息的方法的流程图；
图4为根据一示例性实施例示出的一种发送配置信息的方法的流程图；
图5为根据一示例性实施例示出的另一种发送配置信息的方法的流程图；
图6为根据一示例性实施例示出的MAC CE信令信息域结构示意图；
图7为根据另一示例性实施例示出的MAC CE信令信息域结构示意图；
图8为根据一示例性实施例示出的一种接收配置信息的方法的流程图；
图9为根据一示例性实施例示出的一种发送配置信息的装置的结构图；
图10为根据一示例性实施例示出的网络设备的结构图；
图11为根据一示例性实施例示出的一种接收配置信息的装置的结构图；
图12为根据一示例性实施例示出的用户设备的结构图。
具体实施方式
现结合附图和具体实施方式对本公开实施例进一步说明。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”及“若”可以被解释成为“在……时”或“当……时”或“响应于确定”。
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的要素。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。
图1为本申请实施例适用的一种无线通信系统100的示意图。如图1所示，本公开实施例提供的一种传输配置信息的方法可应用于无线通信系统100，该无线通信系统可以包括网络设备101和用户设备102。其中，用户设备102被配置为支持载波聚合，并可连接至网络设备101的多个载波单元，包括一个主载波单元以及一个或多个辅载波单元。
应理解，以上无线通信系统100既可适用于低频场景，也可适用于高频场景。无线通信系统100的应用场景包括但不限于长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统、全球互联微波接入(worldwide interoperability for micro wave access，WiMAX)通信系统、云无线接入网络(cloud radio access network，CRAN)系统、未来的第五代(5th-Generation，5G)系统、新无线(new radio，NR)通信系统或未来的演进的公共陆地移动网络(public land mobile network，PLMN)系统等。
以上所示用户设备102可以是终端(terminal)、接入终端、终端单元、终端站、移动台(mobile station，MS)、远方站、远程终端、移动终端(mobile terminal)、无线通信设备、终端代理或终端设备等。该用户设备102可具备无线收发功能，其能够与一个或多个通信系统的一个或多个网络设备进行通信(如无线通信)，并接受网络设备提供的网络服务，这里的网络设备包括但不限于图示网络设备101。
其中，用户设备102可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理personal digital assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN网络中的终端设备等。
网络设备101可以是接入网设备(或称接入网站点)。其中，接入网设备是指有提供网络接入功能的设备，如无线接入网(radio access network，RAN)基站等等。网络设备101具体可包括基站(base station，BS)，或包括基站以及用于控制基站的无线资源管理设备等。该网络设备101还可包括中继站(中继设备)、接入点以及未来5G网络中的基站、未来演进的PLMN网络中的基站或者NR基站等。网络设备101可以是可穿戴设备或车载设备。网络设备101也可以是具有通信模块的通信芯片。
比如，网络设备101包括但不限于：5G中的下一代基站(gnodeB，gNB)、LTE系统中的演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、WCDMA系统中的节点B(node B，NB)、CRAN系统下的无线控制器、基站控制器(basestation controller，BSC)、GSM系统或CDMA系统中的基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseband unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)或移动交换中心等。
网络设备101与用户设备102之间的通信遵循一定的协议层结构。图2为本公开实施例示意的一种协议层结构示意图。参考图2所示，控制面协议层结构可以包括无线资源控制(Radio Resource Control，RRC)层、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路控制(Radio Link Control，RLC)层、媒体接入控制(Media Access Control，MAC)层和物理层(Physical Layer，PHY)等协议层的功能。用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层等协议层的功能。
本公开实施例提供一种传输配置信息的方法，参照图3，图3是根据一示例性实施例示出的一种传输配置信息的方法，如图3所示，该方法包括步骤S301～S302，具体的：
步骤S301，网络设备101向用户设备102发送配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S302，用户设备102根据接收的配置信息，向至少一种类型RLC实体发送业务数据。
在一些可能的实施方式中，网络设备101通过发送RRC消息发送配置信息。
在一些可能的实施方式中，业务数据可以是XR业务数据，XR业务数据包括增强现实(Augmented Reality，AR)业务数据、虚拟现实(Virtual Reality，VR)业务数据和云游戏(Cloud gaming)业务数据等。
在一些可能的实施方式中，N≥1。例如，N＝2，即网络设备101配置UE的PDCP实体与2种类型RLC实体关联。
在一些可能的实施方式中，N与业务数据的类型相关。
在一些可能的实施方式中，用户设备102的PDCP实体通过高层接收网络设备101发送的业务数据，并将业务数据分流发送至对应的至少一种类型RLC实体(RLC entity)。
本公开实施例中，网络设备101向用户设备102发送配置信息，以向用户设备102配置PDCP实体所关联的N种RLC实体。从而用户设备102可以根据配置信息对业务数据进行有效分流，以提升传输业务数据的效率。
值得说明的是，本公开实施例中可以是网络设备101确定配置信息，用户设备102根据配置信息对上行发送数据进行分流。还可以是：网络设备101确定配置信息，并将配置信息告知用户设备102，并且网络设备101对下行数据进行分流。以下仅列举用户设备102 进行分流的场景，但下述实施例中所示例及阐述的分流方式同样适用于网络设备101进行分流的场景。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。参照图4，图4是根据一示例性实施例示出的一种发送配置信息的方法，如图4所示，该方法包括步骤S401，具体的：
步骤S401，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
在一些可能的实施方式中，网络设备101通过发送RRC消息发送配置信息。
在一些可能的实施方式中，业务数据可以是XR业务数据。
在一些可能的实施方式中，N≥1。例如，N＝2，即网络设备101配置UE的PDCP实体与2种类型RLC实体关联。
在一些可能的实施方式中，N与业务数据的类型相关。
其中，业务数据可以根据不同维度来区分不同的业务类型。
在一些实施例中，业务类型的分类维度包括，但不限于：
业务数据重要性，即按不同重要性区分业务数据的不同业务类型。例如，业务数据的重要性程度包括高中低，则业务类型可包括高重要性程度对应的业务类型，中重要性程度对应的业务类型，以及低重要性程度对应的业务类型。再例如，用数字衡量或表征业务数据的重要性程度，如第一级别的业务数据。
业务数据的属性，例如按照业务数据的帧内编码帧(Intra-coded picture或I frame)和前向预测编码帧(Predictive-frame，P frame)，区分业务数据的不同业务类型。
业务数据所属的子流(Sub Qos flow)或者QoS流。例如，属于不同子流的业务数据，对应不同业务类型，或者属于相同子流的不同业务数据对应不同业务类型。
业务数据的优先级别，即按不同优先级别区分业务数据的不同业务类型。例如，以高中低或者数字表征不同优先级别，则每种优先级别对应一种业务类型。
业务数据的可靠性级别(reliability levels)，即按不同可靠性需求区分业务数据的不同业务类型。例如，以高中低或者数字表征不同可靠性需求，每种可靠性需求对应一种业务类型。
业务数据的用途，即按业务数据的不同用途区分业务数据的不同业务类型。例如，业务数据的用途可以包括：PDCP控制数据(PDCP Control PDU)和PDCP数据协议数据单元(PDCP Data PDU)。值得说明的是，在对业务数据进行区分业务类型的过程中，业务数据可以是以数据包为单位，或者以数据包集合(set)为单位。在以数据包集合为单位进行区分时，若数据包集合中摸某个数据包划分为第一业务类型，该数据包集合内的全部数据包均属于该第一业务类型。
在一些可能的实施方式中，每种类型的RLC实体包括至少一个RLC实体。
在一示例中，在未配置复制(duplication)的场景下，每种类型的RLC实体包含一个RLC实体。根据传输模式不同，该一个RLC实体可能有不同情况。
例如，在非确认传输模式(UM)，且RLC实体能够双向传输(支持上行和下行)时，该一个RLC实体是一个UM RLC实体。
再例如，在非确认传输模式，且RLC实体单向传输(仅支持上行或下行)时，该一个RLC实体是指每个传输方向一个RLC实体，即该一个RLC实体是一个上行UM RLC实体和一个下行UM RLC实体。
再例如，在确认传输模式(AM)，该一个RLC实体是一个AM RLC实体。
在另一示例中，在配置复制的场景下，每种类型的RLC实体包含多个RLC实体。此时，根据传输模式不同，该多个RLC实体仍有不同情况。
例如，在非确认传输模式(UM)，且RLC实体能够双向传输时，该多个RLC实体包括两个UM RLC实体。
再例如，在非确认传输模式，且RLC实体单向传输时，该多个RLC实体包括四个UM RLC实体，其中，两个上行UM RLC实体和两个下行UM RLC实体。
再例如，在确认传输模式，该多个RLC实体包括两个AM RLC实体。
本公开实施例中，网络设备101向用户设备102发送配置信息，以向用户设备102配置PDCP实体所关联的N种RLC实体。从而用户设备102可以根据配置信息对业务数据进行有效分流，以提升传输业务数据的效率。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。该方法包括步骤S401，具体的：
步骤S401，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
其中，N为业务数据的业务类型数量，配置信息还用于配置每种类型的RLC实体传输对应业务类型的业务数据。
在一些可能的实施方式中，业务类型数量可以是2，则N＝2，即配置信息中配置2种类型的RLC实体，并且每种类型的RLC实体对应传输一种业务类型的业务数据。
在一些可能的实施方式中，业务数据的业务类型可以包括：帧内编码帧(Intra-coded picture或I frame)和前向预测编码帧(Predictive-frame，P frame)，即I帧和P帧，其中，I帧为关键帧。
在该实施方式中，在2种类型的RLC实体中，一种类型的RLC实体对应第一逻辑信道，用于传输I帧业务数据；另一种类型的RLC实体对应第二逻辑信道，用于传输P帧业务数据。
在一些可能的实施方式中，业务数据的业务类型可以包括：不同流或子流的数据，例如包括第一子流(sub-flow1)业务数据，第二子流(sub-flow2)业务数据。
在该实施方式中，在2种类型的RLC实体中，一种类型的RLC实体用于传输第一子 流业务数据，另一种类型的RLC实体用于传输第二子流业务数据。
在一些可能的实施方式中，业务数据的业务类型可以包括：PDCP控制数据(PDCP Control PDU)和PDCP数据协议数据单元(PDCP Data PDU)。其中，PDCP控制数据是PDCP产生的数据，PDCP数据协议数据单元是PDCP从高层接收的数据包。
此时，N种类型的RLC实体记为第一类型RLC实体，第二类型RLC实体，…，第N类型的RLC实体。
在一个实施例中，可以网络设备指定或者协议约定第一RLC实体，或第二RLC实体；
在一个实施例中，可以网络设备指定或者协议约定主RLC实体、和辅RLC实体(主RLC实体之外的RLC实体)；
在一个实施例中，可以网络设备指定或者协议约定默认RLC实体；
在该实施方式中，在N种类型的RLC实体中，第一RLC实体用于传输PDCP控制数据，第二RLC实体用于传输PDCP数据协议数据单元。
在一示例中，第一RLC实体为主RLC实体(primary RLC entity)。
在一些可能的实施方式中，每种类型的RLC实体包括至少一个RLC实体。
本公开实施例中，网络设备101根据业务数据的类型，为用户设备102配置PDCP实体所关联的RLC实体的类型数量，并配置每种类型RLC实体用于传输对应类型的业务数据。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。该方法包括步骤S401，具体的：
步骤S401，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
其中，配置信息还用于配置N种类型的RLC实体属于不同的主节点或辅节点，或者属于同一个主节点(MN)或辅节点(SN)，或者属于同一个小区或者不同小区。
在一些可能的实施方式中，该N种类型的RLC实体用于传输不同业务类型的业务数据，例如，该N种类型的RLC实体对应于N种业务类型的业务数据。
在一些可能的实施方式中，MN和SN可用于UE的双链接(Dual Connectivity，DC)。在双链接中，UE维持MN下服务小区的RRC连接，并可以被配置与SN下服务小区连接，以提升数据吞吐量。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。该方法包括步骤S401，具体的：
步骤S401，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
其中，配置信息还用于配置默认RLC实体，默认RLC实体用于传输第一业务。
在一些可能的实施方式中，默认RLC实体可以是N种类型RLC实体中的一种类型，或者是在N种类型RLC实体之外额外配置的。
在一示例中，默认RLC实体是主RLC实体或者网络设备指定的其他RLC实体。
在一些可能的实施方式中，第一业务是指定业务类型的业务数据，例如，第一业务是PDCP控制数据。
在一些可能的实施方式中，第一业务是未配置对应RLC实体的业务数据。
在一些可能的实施方式中，用户设备102根据配置信息，对指定业务类型的业务数据，或者未配置对应RLC实体的业务数据，可递交至默认RLC实体，以实现数据分流。
本公开实施例中，网络设备101为用户设备102配置默认RLC实体，以实现用户设备102对第一业务的数据分流。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。该方法包括步骤S401，具体的：
步骤S401，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
其中，配置信息包括N种类型的RLC实体对应的指示标识，指示标识用于指示部分类型或全部类型RLC实体是否激活第一功能。
其中，第一功能可以是业务分流功能或者包复制功能。
在一些可能的实施方式中，当配置信息中未包括N种类型的RLC实体对应的指示标识时，网络设备101配置了配置信息，则认为配置信息中N种类型的RLC实体均激活了第一功能如业务分流功能。
在一些可能的实施方式中，指示标识占用一个比特，该N种类型的RLC实体可通过同一个比特统一指示。
例如，该指示标识对应的比特为1时，该N种类型的RLC实体均激活业务分流功能。
再例如，该指示标识对应的比特为0时，该N种类型的RLC实体均去激活业务分流功能。
在一些可能的实施方式中，指示标识占用多个比特。配置信息中包括每种类型RLC实体分别对应的比特位，以分别指示每种类型RLC实体是否激活第一功能如业务分流功能。其中，当某种类型的RLC实体指示激活第一功能时，该类型下的各RLC实体均激活第一功能。
在一示例中，在任一类型RLC实体的指示标识对应的比特为1时，该种类型的RLC实体激活第一功能如业务分流功能；在任一类型RLC实体的指示标识对应的比特为0时，该种类型的RLC实体去激活业务分流功能。
在另一示例中，该多个比特的值均相同时，该指示标识对应指示了全部类型RLC实体第一功能的激活状态。例如，多个比特值均为1时，表明全部类型RLC实体均激活第一功能。
在一些可能的实施方式中，指示标识占用多个比特，每个比特用于指示：激活或去激活一个RLC实体的第一功能。例如，配置信息中包括每个RLC实体分别对应的比特位， 以分别指示单个RLC实体是否激活第一功能如业务分流功能。
在一示例中，在任一个RLC实体的指示标识对应的比特为1时，该RLC实体激活第一功能如业务分流功能；在任一个RLC实体的指示标识对应的比特为0时，该RLC实体去激活第一功能。
在一些可能的实施方式中，对于去激活的RLC实体，用户设备102可将其关联的业务数据向默认RLC实体分流。
为便于理解，此处列举一具体示例：
配置信息配置PDCP实体对应的三种类型的RLC实体分别为：第一RLC实体、第二RLC实体以及第三RLC实体，并配置了第一RLC实体用于传输第一业务类型的业务数据或者控制PDU，第二RLC实体用于传输第二业务类型的业务数据，第三RLC实体用于传输第三业务类型的业务数据。
值得说明的是，本公开实施例中描述的第一RLC实体、第二RLC实体或者第三RLC实体的命名方式仅用于参考和区分，而非对该RLC实体的限制。例如，第一RLC实体也可以命名为主RLC实体，第二RLC实体或者第三RLC实体也可以命名为辅RLC实体。
本示例中，配置信息还配置了第一RLC实体的业务分流功能激活，第二RLC实体的业务分流功能激活，第三RLC实体的业务分流功能去激活。
根据配置信息，用户设备102的PDCP层在业务分流过程中，将第一业务类型的业务数据或者控制PDU递交至第一RLC实体，将第二业务类型的业务数据递交至第二RLC实体。
此外，若本示例中配置信息还配置了默认RLC实体，则用户设备102可以将第三业务类型的业务数据递交至默认RLC实体。从而，在第三RLC实体去激活的场景下，也可以实现其对应业务的分流。
本公开实施例中，网络设备101在下发的配置信息中，同步指示部分或全部的RLC实体是否激活第一功能如业务分流功能，以便用户设备102根据配置信息即可获知部分或全部的RLC实体是否激活第一功能如业务分流功能。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。参照图5，图5是根据一示例性实施例示出的一种发送配置信息的方法，如图5所示，该方法包括步骤S501～S502，具体的：
步骤S501，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S502，网络设备101向用户设备102发送第一指示信息，第一指示信息用于指示激活或去激活部分类型或全部类型的RLC实体的第一功能。
其中，步骤S501和S502的顺序仅做示意，例如，步骤S501和S502还可以同步执行。
在一些可能的实施方式中，网络设备101可通过发送下行控制信息(Downlink Control  Information，DCI)或者媒体接入控制层控制单元(Media Access Control Control Element，MAC CE)信令的方式，发送第一指示信息。
在一些可能的实施方式中，第一指示信息可统一指示该N种类型的RLC实体是否激活第一功能，也就是说对全部类型的分流RLC实体进行统一控制。
例如，通过一个比特位统一指示该N种类型的RLC实体是否均激活第一功能。
在一些可能的实施方式中，第一指示信息对应多个比特，每个比特分别指示一种类型RLC实体是否激活第一功能。
例如，通过第一指示信息中每种类型RLC实体分别对应的比特位，对应指示每种类型RLC实体是否激活第一功能如业务分流功能。其中，当某种类型的RLC实体指示激活第一功能时，该类型下的各RLC实体均激活第一功能。
在一示例中，在任一类型RLC实体对应的比特为1时，该种类型的RLC实体激活第一功能如业务分流功能；在任一类型RLC实体对应的比特为0时，该种类型的RLC实体去激活业务分流功能。
在一些可能的实施方式中，第一指示信息对应多个比特，每个比特用于指示：激活或去激活每个RLC实体的第一功能。例如，通过第一指示信息中每个RLC实体分别对应的比特位，对应指示每个分流RLC实体是否激活第一功能如业务分流功能。
在一示例中，在任一个RLC实体对应的比特位值为1时，该RLC实体激活第一功能如业务分流功能；在任一个RLC实体对应的比特位值为0时，该RLC实体去激活第一功能。
在一些可能的实施方式中，第一功能包括业务分流功能或者PDCP包复制功能。
本公开实施例中，网络设备101通过动态指示的方式，指示部分或全部的RLC实体是否激活第一功能，以便可以适应性的调整RLC实体是否激活第一功能。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。该方法包括步骤S501～S502’，具体的：
步骤S501，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S502’，网络设备101向用户设备102发送下行控制信息DCI，DCI包括第一指示信息。
其中，第一指示信息用于指示激活或去激活部分类型或全部类型RLC实体的第一功能。
在一些可能的实施方式中，第一功能包括业务分流功能或者PDCP包复制功能。
本公开实施例中，网络设备101通过DCI动态下发第一指示信息，从而动态配置N种类型的RLC实体是否激活第一功能。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。该方法包括步骤S501～S502”，具体的：
步骤S501，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S502”，网络设备101向用户设备102发送媒体接入控制层控制单元MAC CE信令，MAC CE信令包括用于指示第一指示信息的信息域。
其中，第一指示信息用于指示以下一种：激活或去激活部分类型或全部类型RLC实体的第一功能。
在一些可能的实施方式中，信息域至少包含以下一种：
全部类型RLC实体对应的比特位；
每种类型RLC实体分别对应的比特位；
每个RLC实体分别对应的比特位。
在一些可能的实施方式中，信息域包含全部类型RLC实体对应的比特位，即信息域中通过一个比特统一指示全部类型RLC实体是否激活第一功能。
例如，当信息域包含全部类型RLC实体对应的一个比特位，该一个比特位为第一值(如为1)时，表示全部类型RLC实体激活了第一功能；该比特位为第二值(如为0)时，表示全部类型RLC实体去激活了第一功能。并且任一类型RLC实体第一功能的激活状态，适用于该类型下的各RLC实体。
在一些可能的实施方式中，当信息域包含每种类型RLC实体分别对应的比特位，即信息域中分别指示每种类型RLC实体是否激活第一功能。例如，信息域包含每种类型RLC实体分别对应的比特位，其中，以有3种类型RLC实体为例，其信息域结构可参考图6对应的示例。
在任一类型RLC实体对应的比特位为第一值(如为1)时，该种类型的RLC实体激活第一功能如业务分流功能。在任一类型RLC实体的指示标识对应的比特为第二值(如为0)时，该种类型的RLC实体去激活第一功能。其中，当某种类型的RLC实体指示激活第一功能时，该类型下的各RLC实体均激活第一功能。
在每个类型RLC实体对应的比特位值相同时，如均为1，则该信息域指示了全部类型RLC实体激活了第一功能。
在一些可能的实施方式中，当信息域包含每个RLC实体分别对应的比特位，即信息域中分别指示每个RLC实体是否激活第一功能。例如，信息域包含每个RLC实体分别对应的比特位，其中，以有3个RLC实体为例，其信息域结构可参考图7对应的示例。
在任一个RLC实体对应的比特位为第一值(如为1)时，该RLC实体激活第一功能如业务分流功能。在任一个RLC实体对应的比特为第二值(如为0)时，该RLC实体去激活第一功能。
在一些可能的实施方式中，第一功能包括业务分流功能或者PDCP包复制功能。
为便于理解本实施例，以下列举几个具体示例：
示例一：
图6示意了一种用于指示是否激活业务分流功能的信息域结构。如图6所示，该信息域包括：第一部分比特和第二部分比特。
其中，第一部分比特用于指示无线数据承载(Data Radio Bearer，DRB)的标识(DRB ID)，假设第一部分比特长度5比特。一个DRB可对应多种业务类型的业务数据，即可以对应多种类型的RLC实体。
第二部分比特用于指示每种类型RLC实体是否激活业务分流功能。这里以3种类型RLC实体举例，则第二部分比特长度3比特，每种类型的RLC实体占用1比特(此处假设每种类型RLC实体配置了一个RLC实体)，每种类型的RLC用于传输对应业务类型的业务数据。
其中，RLC i中的i是为DRB配置的用于分流的RLC实体。比如，在主小区组(MCG)和辅小区组(SCG)中按升序的辅RLC实体的逻辑信道标识，也即i表征RLC类型或者RLC实体。图6中i可以是0，1，2。
在RLC i对应比特值为1时，该RLC i实体激活了业务分流功能；在RLC i对应比特值为0时，该RLC i实体去激活了业务分流功能。
示例二：
图7示意了一种用于指示是否激活PDCP包复制功能的信息域结构。如图7所示，该信息域包括：第一部分比特和第二部分比特。
其中，第一部分比特用于指示第一RLC实体类型的标识(RLC ID)，假设第一部分比特长度5比特。
第二部分比特用于指示第二RLC实体是否激活包复制功能，假设第二部分比特长度3比特。其中，RLC i中的i是为第二RLC实体配置的，比如在主小区组(MCG)和辅小区组(SCG)中按升序的辅RLC实体的逻辑信道标识，也即i表征第二RLC实体的索引。图7中i可以是0，1，2。此处以3个RLC实体示例。
其中，第一RLC实体与第二RLC实体可以是属于同一种类型的RLC实体。第一RLC实体也可以称为被复制的RLC实体或者主RLC实体，第二RLC实体也可以称为复制的RLC实体或者辅RLC实体。
在RLC i对应比特值为1时，该RLC i实体激活了包复制功能，第一RLC实体的业务数据可复制发送至该RLC i实体；在RLC i对应比特值为0时，该RLC i实体去激活了包复制功能。
本示例中，是否激活PDCP包复制功能的配置，可以细化到RLC实体，为第一RLC实体(或者称被复制的RLC实体)配置激活或去激活第二RLC实体(或者称)复制RLC实体的包复制功能，为用户设备102的业务分流提供指示。
本公开实施例提供一种发送配置信息的方法，该方法被网络设备101执行。该方法包括步骤S501～S502-1，具体的：
步骤S501，网络设备101向用户设备102发送配置信息，配置信息包括分组数据汇聚 协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S502-1，接收用户设备的通知消息，通知消息用于指示用于第一功能的RLC实体重传业务数据的次数达到最大重传次数。
在一些可能的实施方式中，该步骤S502-1可以包括：在接收到用户设备102的通知消息时，网络设备101向用户设备102发送第一指示信息，第一指示信息用于指示去激活通知消息对应的RLC实体的第一功能。
在一些可能的实施方式中，第一功能包括业务分流功能或者PDCP包复制功能。
在一些可能的实施方式中，在接收到通知消息时，表明用于第一功能的RLC实体重传业务数据的次数达到最大重传次数。此时，表明该RLC实体不能再执行重传，或者该RLC实体的通信状况可能出现问题或者故障，可能不适合再用于分流。
在接收到通知消息的基础上，网络设备101可以及时发送第一指示信息，以指示用户设备102去激活该RLC实体的第一功能。从而用户设备102可以及时的调整分流方式，例如不再向该去激活第一功能的RLC实体发送业务数据，而是向默认RLC实体发送该去激活第一功能的RLC实体所对应业务类型的业务数据，以保证仍能够实现该中业务类型业务数据的正常分流，保证数据传输效率。
在一示例中，用于业务分流功能的RLC实体达到最大重传次数时，用户设备102向网络设备101发送通知消息。
在一示例中，用于包复制功能的RLC实体达到最大重传次数时，用户设备102向网络设备101发送通知消息。
本公开实施例中，网络设备101可以在接收到用户设备102的通知消息时，动态的去激活对应的RLC实体的第一功能。
本公开实施例提供一种接收配置信息的方法，该方法被用户设备102执行。参照图8，图8是根据一示例性实施例示出的一种接收配置信息的方法，如图8所示，该方法包括步骤S801～S802，具体的：
步骤S801，用户设备102接收网络设备101发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S802，用户设备102根据配置信息，向至少一种类型RLC实体发送业务数据。
在一些可能的实施方式中，N与业务数据的类型相关。
在一些可能的实施方式中，用户设备102的PDCP层根据业务类型，对业务数据分流，分别向不同类型的RLC实体发送对应类型的业务数据。
在一些可能的实施方式中，业务数据可以是XR业务数据。
在一些可能的实施方式中，每种类型的RLC实体包括至少一个RLC实体。
在一示例中，在未配置复制的场景下，每种类型的RLC实体包含一个RLC实体。根据传输模式不同，该一个RLC实体可能有不同情况。
例如，在非确认传输模式，且RLC实体能够双向传输(支持上行和下行)时，该一个RLC实体是一个UM RLC实体。
再例如，在非确认传输模式，且RLC实体单向传输(仅支持上行或下行)时，该一个RLC实体是指每个传输方向一个RLC实体，即该一个RLC实体是一个上行UM RLC实体和一个下行UM RLC实体。
再例如，在确认传输模式，该一个RLC实体是一个AM RLC实体。
在另一示例中，在配置复制的场景下，每种类型的RLC实体包含多个RLC实体。此时，根据传输模式不同，该多个RLC实体仍有不同情况。
例如，在非确认传输模式，且RLC实体能够双向传输时，该多个RLC实体包括两个UM RLC实体。
再例如，在非确认传输模式，且RLC实体单向传输时，该多个RLC实体包括四个UM RLC实体，其中，两个上行UM RLC实体和两个下行UM RLC实体。
再例如，在确认传输模式，该多个RLC实体包括两个AM RLC实体。
在一些可能的实施方式中，用户设备102的PDCP实体通过高层接收网络设备101发送的业务数据，并将业务数据分流发送至对应的至少一种类型RLC实体。
本公开实施例中，用户设备102根据网络设备101的配置信息，获知PDCP实体所关联的N种RLC实体，从而用户设备102根据配置信息可以对业务数据进行有效分流，以提升传输业务数据的效率。
本公开实施例提供一种接收配置信息的方法，该方法被用户设备102执行。该方法包括步骤S801～S802-1，具体的：
步骤S801，用户设备102接收网络设备101发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
其中，N为业务数据的业务类型数量，配置信息还用于配置每种类型的RLC实体传输对应业务类型的业务数据。
步骤S802-1，用户设备102根据配置信息以及业务数据的业务类型，向与业务类型对应类型的RLC实体分流发送业务数据。
在一些可能的实施方式中，每种类型的RLC实体包括至少一个RLC实体。
在一些可能的实施方式中，业务类型数量可以是2，则N＝2，即配置信息中配置2种类型的RLC实体，并且每种类型的RLC实体对应传输一种业务类型的业务数据。
在一些可能的实施方式中，业务数据的业务类型可以包括：I帧和P帧。
在2种类型的RLC实体中，一种类型的RLC实体对应第一逻辑信道，用于传输I帧业务数据；另一种类型的RLC实体对应第二逻辑信道，用于传输P帧业务数据。
在一些可能的实施方式中，业务数据的业务类型可以包括：不同流或子流的数据，例如包括第一子流业务数据，第二子流业务数据。
在2种类型的RLC实体中，一种类型的RLC实体用于传输第一子流业务数据，另一 种类型的RLC实体用于传输第二子流业务数据。
在一些可能的实施方式中，业务数据的业务类型可以包括：PDCP控制数据和PDCP数据协议数据单元。
此时，N种类型的RLC实体记为第一类型RLC实体，第二类型RLC实体，…，第N类型的RLC实体。
在一个实施例中，可以网络设备指定或者协议约定第一RLC实体，或第二RLC实体；
在一个实施例中，可以网络设备指定或者协议约定主RLC实体、和辅RLC实体(主RLC实体之外的RLC实体)；
在一个实施例中，可以网络设备指定或者协议约定默认RLC实体；
在该实施方式中，在N种类型的RLC实体中，第一RLC实体用于传输PDCP控制数据，第二RLC实体用于传输PDCP数据协议数据单元在一示例中，第一RLC实体为主RLC实体(primary RLC entity)。
本公开实施例中，用户设备102根据业务数据的业务类型进行有效的数据分流。
本公开实施例提供一种接收配置信息的方法，该方法被用户设备102执行。该方法包括步骤S801～S802-2，具体的：
步骤S801，用户设备102接收网络设备101发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
其中，配置信息还用于配置默认RLC实体，默认RLC实体用于传输第一业务。
步骤S802-2，在业务数据为第一业务时，用户设备102向默认RLC实体分流发送业务数据。
在一些可能的实施方式中，默认RLC实体可以是N种类型RLC实体中的一种类型，或者是在N种类型RLC实体之外额外配置的。
在一示例中，默认RLC实体是第一RLC实体或者主RLC实体或者网络设备指定的其他RLC实体。
在一些可能的实施方式中，第一业务是指定业务类型的业务数据，例如，第一业务是PDCP控制数据。
在一些可能的实施方式中，第一业务是未配置对应RLC实体的业务数据。
在一些可能的实施方式中，用户设备102对指定业务类型的业务数据，或者未配置对应RLC实体的业务数据，可递交至默认RLC实体，以实现数据分流。
本公开实施例提供一种接收配置信息的方法，该方法被用户设备102执行。该方法包括步骤S801～S802-3，具体的：
步骤S801，用户设备102接收网络设备101发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
其中，配置信息还用于配置默认RLC实体，默认RLC实体用于传输第一业务。
步骤S802-3，在业务数据对应的RLC实体去激活业务分流功能时，用户设备102向 默认RLC实体分流发送业务数据。
在一些可能的实施方式中，用户设备102接收到了配置信息，则认为配置信息中N种类型的RLC实体激活了业务分流功能。
在一些可能的实施方式中，配置信息中包括N种类型的RLC实体对应的指示标识，指示标识用于指示部分类型或全部类型RLC实体是否激活第一功能。此时，在步骤S802-3之前，用户设备102根据如下步骤S800-11，获知N种类型的RLC实体是否激活第一功能：
步骤S800-11，用户设备102根据配置信息中的指示标识，确定部分类型或全部类型RLC实体是否激活业务分流功能。
在一些可能的实施方式中，指示标识占用一个比特，配置信息中采用同一个比特统一指示N种类型RLC实体是否激活第一功能如业务分流功能，即全部类型RLC实体是否激活第一功能。
例如，该指示标识对应的比特为1时，该N种类型的RLC实体均激活业务分流功能。再例如，该指示标识对应的比特为0时，该N种类型的RLC实体均去激活业务分流功能。
在一些可能的实施方式中，指示标识占用多个比特。配置信息中包括每种类型的RLC实体分别对应的比特位，从而分别指示每种类型RLC实体是否激活第一功能如业务分流功能。
例如，在任一类型RLC实体的指示标识对应的比特为1时，该种类型的RLC实体激活第一功能如业务分流功能；在任一类型RLC实体的指示标识对应的比特为0时，该种类型的RLC实体去激活业务分流功能。其中，当某种类型的RLC实体指示激活第一功能时，该类型下的各RLC实体均激活第一功能。
再例如，该多个比特的值均相同时，该指示标识对应指示了全部类型RLC实体第一功能的激活状态。例如，多个比特值均为1时，表明全部类型RLC实体均激活第一功能。
在一些可能的实施方式中，指示标识占用多个比特，每个比特用于指示：激活或去激活每个RLC实体的第一功能。例如，配置信息中包括每个RLC实体分别对应的比特位，以分别指示每个RLC实体是否激活第一功能如业务分流功能。
在一示例中，在任一个RLC实体的指示标识对应的比特为1时，该RLC实体激活第一功能如业务分流功能；在任一个RLC实体的指示标识对应的比特为0时，该RLC实体去激活第一功能。
在一些可能的实施方式中，用户设备102根据接收的第一指示信息，确定部分类型或全部类型RLC实体是否激活第一功能，如业务分流功能。此方式可参见下述实施例的描述。
在一些可能的实施方式中，对于激活业务分流功能的RLC实体，用户设备102的PDCP可将对应业务类型的业务数据递交至关联的RLC实体。
在一些可能的实施方式中，对于去激活业务分流功能的RLC实体，用户设备102的 PDCP可将该RLC实体对应业务类型的业务数据，递交至默认RLC实体，仍保证可以实现该类型业务数据的分流。
本公开实施例中，用户设备102根据配置信息获知部分或全部的RLC实体是否激活了第一功能如业务分流功能，在任一RLC实体的业务分流功能去激活时，用户设备102可向默认RLC实体进行分流数据。
本公开实施例提供一种接收配置信息的方法，该方法被用户设备102执行。该方法包括步骤S801、S800-21、S800-22以及S802，具体的：
步骤S801，用户设备102接收网络设备101发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S800-21，用户设备102接收网络设备101发送的第一指示信息，第一指示信息用于指示激活或去激活部分类型或全部类型RLC实体的第一功能。
步骤S800-22，用户设备102根据第一指示信息，确定部分类型或全部类型RLC实体是否激活第一功能。
步骤S802，用户设备102根据配置信息，向至少一种类型RLC实体发送业务数据。
在一些可能的实施方式中，第一指示信息可统一指示该N种类型的RLC实体是否激活第一功能，即指示全部类型的RLC实体是否激活第一功能。例如，通过一个比特位统一指示该N种类型的RLC实体是否均激活第一功能。其中，当某种类型的RLC实体指示激活第一功能时，该类型下的各RLC实体均激活第一功能。
在一些可能的实施方式中，第一指示信息分别指示全部N种类型或N种类型的部分类型中每种类型RLC实体是否激活第一功能。例如，每种类型RLC实体具有对应的比特位，每个比特位指示对应类型的RLC实体是否激活第一功能。其中，当某种类型的RLC实体指示激活第一功能时，该类型下的各RLC实体均激活第一功能。
在一些可能的实施方式中，第一指示信息分别指示每个RLC实体是否激活第一功能。例如，每个RLC实体具有对应的比特位，每个比特位指示对应RLC实体是否激活第一功能。
在一些可能的实施方式中，用户设备102接收第一指示信息，可以是接收网络设备101发送的DCI，获知DCI中的第一指示信息。
在一些可能的实施方式中，用户设备102接收第一指示信息，可以是接收网络设备101发送的MAC CE信令，MAC CE信令包括用于指示第一指示信息的信息域。
在一些可能的实施方式中，第一功能包括业务分流功能或者包复制功能。
在一些可能的实施方式中，当第一功能为业务分流功能时，该步骤S802在实施过程中，可参照如下步骤S802-3，具体的：
步骤S802-3，在业务数据对应的RLC实体去激活业务分流功能时，用户设备102向默认RLC实体分流发送业务数据。
本公开实施例中，用户设备102根据第一指示信息获知部分或全部的RLC实体是否 激活了第一功能，从而可以及时调整分流方式。
本公开实施例提供一种接收配置信息的方法，该方法被用户设备102执行。该方法包括步骤S801、S800-21’、S800-22’以及S802，具体的：
步骤S801，用户设备102接收网络设备101发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S800-21’，用户设备102接收网络设备101发送的MAC CE信令，MAC CE信令包括用于指示第一指示信息的信息域。
步骤S800-22’，用户设备102在信息域中至少一个比特位为第一值时，确定至少一个比特位对应的RLC实体的第一功能激活。
步骤S802，用户设备102根据配置信息，向至少一种类型RLC实体发送业务数据。
在一些可能的实施方式中，信息域至少包含以下一种：
全部类型RLC实体对应的比特位；
每种类型RLC实体分别对应的比特位；
每个RLC实体分别对应的比特位。
在一些可能的实施方式中，信息域包括一个用于指示第一功能激活状态的比特位，统一指示全部类型RLC实体是否激活第一功能。
例如，当该一个比特位为第一值(如为1)时，表示全部类型RLC实体激活了第一功能；该比特位为第二值(如为0)时，表示全部类型RLC实体去激活了第一功能。并且任一类型RLC实体第一功能的激活状态，适用于该类型下的各RLC实体。
在一些可能的实施方式中，信息域包括大于一个的用于指示第一功能激活状态的比特位。如信息域包含每种类型RLC实体分别对应的比特位。此时可参考图6所示。
在任一类型RLC实体对应的比特位为第一值(如为1)时，该种类型的RLC实体激活第一功能如业务分流功能。在任一类型RLC实体的指示标识对应的比特为第二值(如为0)时，该种类型的RLC实体去激活第一功能。其中，当某种类型的RLC实体指示激活第一功能时，该类型下的各RLC实体均激活第一功能。
在该大于一个的比特位值相同时，如均为1，则表明激活全部类型RLC实体第一功能。
在一些可能的实施方式中，信息域包括大于一个的用于指示第一功能激活状态的比特位，例如，每个RLC实体分别对应一个比特位，此时可参考图7所示。
在任一个RLC实体对应的比特位为第一值(如为1)时，该RLC实体激活第一功能如业务分流功能。在任一个RLC实体对应的比特为第二值(如为0)时，该RLC实体去激活第一功能。
在一些可能的实施方式中，第一功能包括业务分流功能或者包复制功能。
本公开实施例中，网络设备101通过MAC CE信令动态指示激活或去激活部分或全部的RLC实体的第一功能，用户设备102根据MAC CE信令及时获知RLC实体的激活情况，及时调整分流方式。
本公开实施例提供一种接收配置信息的方法，该方法被用户设备102执行。该方法包括步骤S801、S800-21、S800-22、S802以及S803，具体的：
步骤S801，用户设备102接收网络设备101发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
步骤S800-21，用户设备102接收网络设备101发送的第一指示信息。
步骤S800-22，用户设备102根据第一指示信息，确定部分类型或全部类型RLC实体是否激活第一功能。
步骤S802，用户设备102根据配置信息，向至少一种类型RLC实体发送业务数据。
步骤S803，在用于第一功能的RLC实体重传业务数据的次数达到最大重传次数时，用户设备102向网络设备101发送通知消息。
在一些可能的实施方式中，第一功能包括业务分流功能或者PDCP包复制功能。
在一些可能的实施方式中，用于业务分流功能的RLC实体达到最大重传次数时，用户设备102向网络设备101发送通知消息。此时，表明该RLC实体不能再执行重传，或者该RLC实体的通信状况可能出现问题或者故障，可能不适合再用于分流。
在一些可能的实施方式中，用于包复制功能的RLC实体达到最大重传次数时，用户设备102向网络设备101发送通知消息。
在一些可能的实施方式中，网络设备101可以在接收到用户设备102的通知消息时，动态的去激活对应的RLC实体的第一功能。
本公开实施例中，用户设备102在用于第一功能的RLC实体达到最大重传次数时，可及时上报网络设备101，以便于网络设备101进行激活状态的调整，如去激活某RLC实体的第一功能。从而用户设备102可以及时的调整分流方式，例如不再向该去激活第一功能的RLC实体发送业务数据，而是向默认RLC实体发送该去激活第一功能的RLC实体所对应业务类型的业务数据，以保证仍能够实现该中业务类型业务数据的正常分流，保证数据传输效率。
为更好的理解本公开实施例的内容，以下列举一些具体示例：
示例一：
在特定业务(如XR业务)分流场景下，网络设备101为用户设备102配置：PDCP实体对应到N种类型的RLC实体；其中N对应业务类型分类。比如第一类型业务数据，第二类型业务数据…第N类型业务数据。
其中，对于业务类型分类可以有很多维度，包括但是不限于：根据业务数据重要性区分，根据业务数据的属性区分，根据业务数据所属的子流(Sub Qos flow)或者QoS流进行区分，根据业务数据的优先级别进行区分，根据业务数据的优先级别进行区分，根据业务数据的可靠性级别进行区分，或者根据业务数据的用途进行区分。此处可参见前述实施例中涉及的描述。
作为该示例的一种实施例，网络设备101为不同业务类型指定其传输RLC实体，即进行分流操作。比如，网络设备101配置2种类型的RLC实体，分别为第一类型RLC实体和第二类型RLC实体；该两种类型的RLC实体分别对应：第一业务类型数据比如I帧业务数据的发送和第二业务类型数据比如P帧业务数据的发送。例如，第一类型RLC实体对应逻辑信道1，用于I帧业务数据传输；第二类型RLC实体对应逻辑信道2，用于P帧业务数据传输。
作为该示例的一种实施例，用户设备102在上行发送数据时，在PDCP层需要根据业务数据的不同业务类型，投递到对应类型传输RLC实体传输。PDCP层可能是基于每个数据包进行判决其业务类型，并进行投递；也有可能以数据包集合进行批量判决。比如根据该数据包集合中一个数据包的业务类型进行判决分流后，对该数据集合中其他数据包也将投递到同一个的类型传输RLC实体传输。这样无需逐个数据包进行分流判决，提升判决效率。
作为该示例的一种实施例，每种类型的RLC实体，分别对应至少一个UM实体(支持上行和下行)，或者至少2个UM实体(仅支持上行或下行)，或者至少一个AM实体。
作为该示例的一种实施例，网络设备101为不同业务类型指定其传输RLC实体可以属于不同的MN或者SN节点，也可以属于同一个MN或者SN节点，或者也可以属于同一个小区或者不同小区。
作为该示例的一种实施例，指定类型RLC实体(如第一RLC实体或主RLC实体)可以传输指定类型业务，比如控制PDU。或者，某些业务类型没有配置RLC实体，则可以使用默认的RLC实体传输，比如使用第一RLC实体或者主RLC实体。
值得说明的是，对于复制场景，业务数据的传输可以在同一个小区或者载波。
该示例下的示范例列举如下：
例1：网络设备101配置：第一RLC实体用于类型1数据传输，第二RLC实体用于类型2数据传输，…。
例2：网络设备101配置：第一RLC实体用于类型1数据传输和/或者控制PDU，第二RLC实体用于类型2数据传输，第三RLC实体用于类型3数据传输。
其中，对于各RLC实体的命名仅供参考和区分，而非限定该RLC实体。例如，第一RLC实体也可以称为主RLC实体，第二RLC实体或第三RLC实体也可以称为辅RLC实体。
示例二：
通过网络设备101配置或者通过协议约定业务分流的传输状态，即是否使能业务分流功能，或者激活业务分流功能，或者使用业务分流功能。
作为该示例的一种实施例，网络设备101进行了示例一的配置，则认为使能或激活了业务分流功能。即，高层进行了示例一中的配置则认为使能了业务分流功能；无需后续再 进行激活该功能。
作为该示例的一种实施例，网络设备101在配置时指明是否使能业务分流功能的初始状态。比如，配置时候，第一RLC实体(用于类型1数据传输)的业务分流功能为使能，第二RLC实体(用于类型2数据传输)的业务分流功能为去使能，…。
该示例下的示范例列举如下：
例1：网络设备101配置：第一RLC实体(用于类型1数据传输)，业务分流功能激活；第二RLC实体(用于类型2数据传输)，业务分流功能激活，…。
例2：网络设备101配置：第一RLC实体(用于类型1数据传输和/或者控制PDU)，业务分流功能激活；第二RLC实体(用于类型2数据传输)，业务分流功能激活；第三RLC实体或(用于类型3数据传输)，业务分流功能不激活；…。
其中，对于各RLC实体的命名仅供参考和区分而非限定。例如，第一RLC实体也可以称为主RLC实体，第二RLC实体也可以称为辅RLC实体1，第三RLC实体也可称为辅RLC实体2。
作为该示例二的一种实施例，分流功能被去激活的RLC实体，其关联的业务数据可以使用默认的RLC实体传输，比如使用第一RLC实体或者主RLC实体；
比如以上例2中，类型3数据传输将使用主RLC实体传输。
作为该示例二的一种实施例，可以使用MAC CE方式或者DCI方式或者RRC方式进行动态的激活(或者使能/去使能)分流状态或者业务分流功能。其中，其中RRC重配置消息中可以指明RLC实体分流功能是否激活的初始状态。
例1：MAC CE指示业务分流功能的激活/去激活，以下按照3种类型RLC实体举例说明，但不限于可以采用比示例中更多的比特来指示。
图6是MAC CE指示RLC实体激活/去激活业务分流功能(PDCP split)的示意。
如图6所示，该信息域包括：第一部分比特和第二部分比特。
其中，第一部分比特用于指示无线数据承载(Data Radio Bearer，DRB)的标识(DRB ID)，假设第一部分比特长度5比特。一个DRB可对应多种业务类型的业务数据，即可以对应多种类型的RLC实体。
第二部分比特用于指示每种类型RLC实体是否激活业务分流功能。这里以3种类型RLC实体举例，则第二部分比特长度3比特，每种类型的RLC实体占用1比特(假设每种类型RLC实体配置了一个RLC实体)，每种类型的RLC用于传输对应业务类型的业务数据。RLC i中的i是为DRB配置的用于分流的RLC实体。比如，在主小区组(MCG)和辅小区组(SCG)中按升序的辅RLC实体的逻辑信道标识，也即i表征RLC类型或者RLC实体。图6中i可以是0，1，2。
在RLC i对应比特值为1时，该RLC i实体激活了业务分流功能；在RLC i对应比特值为0时，该RLC i实体去激活了业务分流功能。
作为该示例二的一种实施例，用于业务分流的RLC实体上达到最大重传次数，通知网 络设备。
比如：第二RLC实体达到最大重传次数将通知基站，如向基站发送通知消息。基站可以进行后续行为，比如去激活该RLC实体的分流功能。
值得说明的是：上述示例中，业务分流功能的激活指示可以每个分流RLC实体(Per RLC实体)控制(参考以上实施例)，也可以对全部分流RLC实体进行统一控制，例如，网络设备发送一条指令同时激活或者去激活全部分流RLC实体的分流功能。
示例三：
在示例一的基础上，网络设备101可以为特定业务对应的RLC实体激活PDCP包复制功能。
作为该示例的一种实施例：激活PDCP包复制的粒度可以细化到RLC实体，即可以为该RLC实体(该实体可以称为：被激活PDCP包复制的RLC实体或者第一RLC实体，或者简称为被复制的RLC实体，或者主RLC实体)配置若干RLC实体(该若干实体可以称为：激活包复制的RLC实体或者第二RLC实体，或者简称为复制的RLC实体或者主RLC实体之外的其他RLC实体)用于包复制。
作为该示例的一种实施例：RLC实体的包复制功能可以被激活去激活。
例1：针对某个RLC实体的包复制激活和去激活：
图7是MAC CE指示RLC实体激活/去激活PDCP包复制功(Duplication)的示意图。
如图7所示，该信息域包括：第一部分比特和第二部分比特。
其中，第一部分比特用于指示第一的RLC实体类型的标识(RLC ID)，假设第一部分比特长度5比特。
第二部分比特用于指示第二RLC实体是否激活包复制功能，假设第二部分比特长度3比特。其中，RLC i中的i是为第二的RLC实体配置的，比如在主小区组(MCG)和辅小区组(SCG)中按升序的辅RLC实体的逻辑信道标识，也即i表征第二RLC实体的索引。图7中i可以是0，1，2。
在RLC i对应比特值为1时，该RLC i实体激活了包复制功能，第一RLC实体(或称被复制的RLC实体)的业务数据可复制发送至该RLC i实体；在RLC i对应比特值为0时，该RLC i实体去激活了包复制功能。
作为该示例的一种实施例：第二RLC实体上达到最大重传次数，通知网络设备。
比如：某个RLC实体(第一RLC实体)对应的第二RLC实体达到最大重传次数将通知基站，如发送通知消息。基站可以进行后续行为，比如去激活该第二RLC实体的包复制功能。
值得说明的是：上述示例中，分流RLC实体的包复制功能激活指示可以每个RLC分流实体粒度控制、也可以按照对每个分流RLC实体(第一RLC实体)对应的每个第二RLC实体控制(如以上实施例)，或者进行统一控制，例如：
网络设备101用一条控制指令同时将某个RLC分流实体激活/去激活包复制，或者网络设备101用一条控制指令同时对所有RLC分流实体激活/去激活包复制。
基于与以上方法实施例相同的构思，本公开实施例还提供一种发送配置信息的装置，该装置可具备上述方法实施例中的网络设备101的功能，并可用于执行上述方法实施例提供的由网络设备101执行的步骤。该功能可以通过硬件实现，也可以通过软件或者硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的实现方式中，如图9所示的装置900可作为上述方法实施例所涉及的网络设备101，并执行上述方法实施例中由网络设备101执行的步骤。如图9所示，该装置900可包括收发模块901，其中，收发模块901可用于支持通信装置进行通信，收发模块901可具备无线通信功能，例如能够通过无线空口与其他通信装置进行无线通信。
在执行由网络设备101实施的步骤时，收发模块901被配置为，向用户设备发送配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
当该通信装置为网络设备101时，其结构还可如图10所示。以基站为例说明通信装置的结构。如图10所示，装置1000包括存储器1001、处理器1002、收发组件1003、电源组件1006。其中，存储器1001与处理器1002耦合，可用于保存通信装置1000实现各功能所必要的程序和数据。该处理器1002被配置为支持通信装置1000执行上述方法中相应的功能，所述功能可通过调用存储器1001存储的程序实现。收发组件1003可以是无线收发器，可用于支持通信装置1000通过无线空口进行接收信令和/或数据，以及发送信令和/或数据。收发组件1003也可被称为收发单元或通信单元，收发组件1003可包括射频组件1004以及一个或多个天线1005，其中，射频组件1004可以是远端射频单元(remote radio unit，RRU)，具体可用于射频信号的传输以及射频信号与基带信号的转换，该一个或多个天线1005具体可用于进行射频信号的辐射和接收。
当通信装置1000需要发送数据时，处理器1002可对待发送的数据进行基带处理后，输出基带信号至射频单元，射频单元将基带信号进行射频处理后将射频信号通过天线以电磁波的形式进行发送。当有数据发送到通信装置1000时，射频单元通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器1002，处理器1002将基带信号转换为数据并对该数据进行处理。
基于与以上方法实施例相同的构思，本公开实施例还提供一种接收配置信息的装置，该装置可具备上述方法实施例中的用户设备102的功能，并可用于执行上述方法实施例提供的由用户设备102执行的步骤。该功能可以通过硬件实现，也可以通过软件或者硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的实现方式中，如图11所示的装置1100可作为上述方法实施例所涉及的用户设备102，并执行上述方法实施例中由用户设备102执行的步骤。如图11所示，该装 置1100可包括相互耦合的收发模块1101和处理模块1102，其中，收发模块1101可用于支持通信装置进行通信，收发模块1101可具备无线通信功能，例如能够通过无线空口与其他通信装置进行无线通信。处理模块1102可用于通信装置执行处理操作，如生成需要发送的信息/消息，或对接收的信号进行处理以得到信息/消息。
在执行由用户设备102实施的步骤时，收发模块1101被配置为，接收网络设备发送的配置信息，配置信息包括用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
处理模块1102被配置为，根据配置信息，向至少一种类型RLC实体发送业务数据。
当该接收指示信息的装置为用户设备102时，其结构还可如图12所示。装置1200可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图12，装置1200可以包括以下一个或多个组件：处理组件1202，存储器1204，电源组件1206，多媒体组件1208，音频组件1210，输入/输出(I/O)的接口1212，传感器组件1214，以及通信组件1216。
处理组件1202通常控制装置1200的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1202可以包括一个或多个处理器1220来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1202可以包括一个或多个模块，便于处理组件1202和其他组件之间的交互。例如，处理组件1202可以包括多媒体模块，以方便多媒体组件1208和处理组件1202之间的交互。
存储器1204被配置为存储各种类型的数据以支持在设备1200的操作。这些数据的示例包括用于在装置1200上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1204可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1206为装置1200的各种组件提供电力。电源组件1206可以包括电源管理系统，一个或多个电源，及其他与为装置1200生成、管理和分配电力相关联的组件。
多媒体组件1208包括在所述装置1200和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1208包括一个前置摄像头和/或后置摄像头。当设备1200处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1210被配置为输出和/或输入音频信号。例如，音频组件1210包括一个麦克风(MIC)，当装置1200处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1204或经由通信组件1216发送。在一些实施例中，音频组件1210还包括一个扬声器，用于输出音频信号。
I/O接口1212为处理组件1202和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1214包括一个或多个传感器，用于为装置1200提供各个方面的状态评估。例如，传感器组件1214可以检测到设备1200的打开/关闭状态，组件的相对定位，例如所述组件为装置1200的显示器和小键盘，传感器组件1214还可以检测装置1200或装置1200一个组件的位置改变，用户与装置1200接触的存在或不存在，装置1200方位或加速/减速和装置1200的温度变化。传感器组件1214可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1214还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1214还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1216被配置为便于装置1200和其他设备之间有线或无线方式的通信。装置1200可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1216经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1216还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1200可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1204，上述指令可由装置1200的处理器1220执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开实施例的其它实施方案。本公开旨在涵盖本公开实施例的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开实施例的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开实施例的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开实施例并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开实施例的范围仅由所附的权利要求来限制。
工业实用性
本公开的方法中，网络设备向用户设备发送配置信息，以向用户设备配置PDCP实体所关联的N种RLC实体。从而用户设备可以根据配置信息对业务数据进行有效分流，以提升传输业务数据的效率。

Claims (27)

  1. 一种发送配置信息的方法，被网络设备执行，所述方法包括：
    向用户设备发送配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
  2. 如权利要求1所述的方法，其中，所述N为业务数据的业务类型数量，所述配置信息还用于配置每种类型的RLC实体传输对应业务类型的业务数据。
  3. 如权利要求1所述的方法，其中，所述配置信息还用于配置默认RLC实体，所述默认RLC实体用于传输第一业务。
  4. 如权利要求1至3任一项所述的方法，其中，每种类型的RLC实体包括至少一个RLC实体。
  5. 如权利要求1所述的方法，其中，所述配置信息包括所述N种类型的RLC实体对应的指示标识，所述指示标识用于指示部分类型或全部类型RLC实体是否激活第一功能。
  6. 如权利要求1所述的方法，其中，所述方法还包括：
    向所述用户设备发送第一指示信息，所述第一指示信息用于指示激活或去激活部分类型或全部类型RLC实体的第一功能。
  7. 如权利要求5或6所述的方法，其中，所述第一功能包括业务分流功能或者包复制功能。
  8. 如权利要求6或7所述的方法，其中，所述向所述用户设备发送第一指示信息，包括：
    向用户设备发送下行控制信息DCI，所述DCI包括所述第一指示信息；或者，
    向用户设备媒体发送接入控制层控制单元MAC CE信令，所述MAC CE信令包括用于指示所述第一指示信息的信息域。
  9. 如权利要求8所述的方法，其中，
    所述信息域至少包含以下一种：全部类型RLC实体对应的比特位，每种类型RLC实体分别对应的比特位，每个RLC实体分别对应的比特位；
    在所述比特位为第一值时，指示激活所述比特位对应的RLC实体的所述第一功能。
  10. 如权利要求5至7任一项所述的方法，其中，所述方法还包括：
    接收所述用户设备的通知消息，所述通知消息用于指示用于第一功能的RLC实体重传业务数据的次数达到最大重传次数。
  11. 一种接收配置信息的方法，被用户设备执行，所述方法包括：
    接收网络设备发送的配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体；
    根据所述配置信息，向至少一种类型RLC实体发送业务数据。
  12. 如权利要求11所述的方法，其中，所述N为业务数据的业务类型数量，所述配 置信息还用于配置每种类型的RLC实体传输对应业务类型的业务数据；
    所述根据所述配置信息，向至少一种类型RLC实体发送业务数据，包括：
    根据所述配置信息以及所述业务数据的业务类型，向与业务类型对应类型的RLC实体分流发送所述业务数据。
  13. 如权利要求11所述的方法，其中，所述配置信息还用于配置默认RLC实体，所述默认RLC实体用于传输第一业务。
  14. 如权利要求13所述的方法，其中，所述根据所述配置信息，向至少一种类型RLC实体发送业务数据，包括：
    在所述业务数据为第一业务时，向所述默认RLC实体分流发送所述业务数据。
  15. 如权利要求13所述的方法，其中，所述根据所述配置信息，向至少一种类型RLC实体发送业务数据，包括：
    在所述业务数据对应的RLC实体去激活业务分流功能时，向所述默认RLC实体分流发送所述业务数据。
  16. 如权利要求15所述的方法，其中，所述方法还包括：
    根据所述配置信息中的指示标识，确定部分类型或全部类型RLC实体是否激活第一功能。
  17. 如权利要求11至16任一项所述的方法，其中，所述方法还包括：
    接收所述网络设备发送的第一指示信息，所述第一指示信息用于指示激活或去激活部分类型或全部类型RLC实体的第一功能；
    根据所述第一指示信息，确定所述部分类型或全部类型RLC实体是否激活第一功能。
  18. 如权利要求17所述的方法，其中，所述第一功能包括业务分流功能或者包复制功能。
  19. 如权利要求17所述的方法，其中，所述接收所述网络设备发送的第一指示信息，包括：
    接收所述网络设备发送的MAC CE信令，所述MAC CE信令包括用于指示所述第一指示信息的信息域。
  20. 如权利要求19所述的方法，其中，所述根据所述第一指示信息，确定所述部分类型或全部类型RLC实体是否激活第一功能，包括：
    在所述信息域中至少一个比特位为第一值时，确定所述至少一个比特位对应的RLC实体的第一功能激活。
  21. 如权利要求17所述的方法，其中，所述方法还包括：
    在用于第一功能的RLC实体重传业务数据的次数达到最大重传次数时，向所述网络设备发送通知消息。
  22. 一种发送配置信息的装置，被配置于网络设备，所述装置包括：
    收发模块，用于向用户设备发送配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体。
  23. 一种接收配置信息的装置，被配置于用户设备，所述装置包括：
    收发模块，用于接收网络设备发送的配置信息，所述配置信息包括所述用户设备中分组数据汇聚协议PDCP实体对应的N种类型的无线链路控制RLC实体；
    处理模块，用于根据所述配置信息，向至少一种类型RLC实体发送业务数据。
  24. 一种通信装置，包括处理器以及存储器，其中，
    所述存储器用于存储计算机程序；
    所述处理器用于执行所述计算机程序，以实现如权利要求1-10中任一项所述的方法。
  25. 一种通信装置，包括处理器以及存储器，其中，
    所述存储器用于存储计算机程序；
    所述处理器用于执行所述计算机程序，以实现如权利要求11-21中任一项所述的方法。
  26. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述指令在计算机上被调用执行时，使得所述计算机执行如权利要求1-10中任一项所述的方法。
  27. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述指令在计算机上被调用执行时，使得所述计算机执行如权利要求11-21中任一项所述的方法。
PCT/CN2022/128395 2022-10-28 2022-10-28 一种传输配置信息的方法、装置及可读存储介质 WO2024087211A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/128395 WO2024087211A1 (zh) 2022-10-28 2022-10-28 一种传输配置信息的方法、装置及可读存储介质
CN202280004751.3A CN115997464A (zh) 2022-10-28 2022-10-28 一种传输配置信息的方法、装置及可读存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/128395 WO2024087211A1 (zh) 2022-10-28 2022-10-28 一种传输配置信息的方法、装置及可读存储介质

Publications (1)

Publication Number Publication Date
WO2024087211A1 true WO2024087211A1 (zh) 2024-05-02

Family

ID=85993912

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/128395 WO2024087211A1 (zh) 2022-10-28 2022-10-28 一种传输配置信息的方法、装置及可读存储介质

Country Status (2)

Country Link
CN (1) CN115997464A (zh)
WO (1) WO2024087211A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103782569A (zh) * 2013-07-15 2014-05-07 华为技术有限公司 数据处理装置和方法
CN111435845A (zh) * 2019-01-11 2020-07-21 华为技术有限公司 通信方法和通信装置
US20210297901A1 (en) * 2018-12-11 2021-09-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method, terminal device and network device
CN113766571A (zh) * 2019-01-16 2021-12-07 Oppo广东移动通信有限公司 数据传输的方法和通信设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103782569A (zh) * 2013-07-15 2014-05-07 华为技术有限公司 数据处理装置和方法
US20210297901A1 (en) * 2018-12-11 2021-09-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method, terminal device and network device
CN111435845A (zh) * 2019-01-11 2020-07-21 华为技术有限公司 通信方法和通信装置
CN113766571A (zh) * 2019-01-16 2021-12-07 Oppo广东移动通信有限公司 数据传输的方法和通信设备

Also Published As

Publication number Publication date
CN115997464A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
US20230007714A1 (en) Method for wireless communication, and communication device
EP4104461A1 (en) Methods of delivery mode switch for multicast and broadcast service in a 5g network
WO2023122920A1 (zh) 一种上报或接收用户设备能力的方法、装置及可读存储介质
AU2021308253A1 (en) Communication method and communication apparatus
WO2023151093A1 (zh) 一种传输终端能力的方法、装置及可读存储介质
WO2023201730A1 (zh) 一种传输用户设备能力的方法、装置及可读存储介质
WO2024087211A1 (zh) 一种传输配置信息的方法、装置及可读存储介质
WO2023019553A1 (zh) 一种传输时频资源配置信息的方法、装置及可读存储介质
WO2024092451A1 (zh) 一种传输指示信息的方法、装置及可读存储介质
WO2024065215A1 (zh) 发送数据量的方法、装置以及可读存储介质
WO2024000196A1 (zh) 一种传输辅助信息的方法、装置以及可读存储介质
WO2024145917A1 (zh) 一种传输能力信息的方法、装置以及可读存储介质
WO2024108402A1 (zh) 一种传输能力信息的方法、装置及可读存储介质
WO2024113121A1 (zh) 一种下行传输方法、装置及可读存储介质
WO2024077495A1 (zh) 一种传输能力信息的方法、装置以及可读存储介质
WO2023178489A1 (zh) 一种传输能力信息的方法、装置及存储介质
WO2024145922A1 (zh) 一种传输能力信息的方法、装置以及可读存储介质
WO2022052122A1 (zh) 资源配置方法、装置、通信设备和存储介质
WO2023151102A1 (zh) 一种监测下行带宽部分的方法、装置及可读存储介质
WO2023130396A1 (zh) 一种监听方法、装置及可读存储介质
WO2024020798A1 (zh) 一种传输下行信道的方法、装置、设备以及可读存储介质
WO2023245503A1 (zh) 一种监听方法、发送方法、装置、设备以及可读存储介质
WO2022047713A1 (zh) 通信方法、装置、通信设备和存储介质
WO2022246709A1 (zh) 一种传输用户设备能力的方法、装置及存储介质
WO2024007338A1 (zh) 一种传输指示信息的方法、装置以及可读存储介质

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

Country of ref document: EP

Kind code of ref document: A1