A method, apparatus, and readable storage medium for transmitting configuration information.

Abstract

This disclosure provides a method, apparatus, and readable storage medium for transmitting configuration information. The method includes sending configuration information to a user equipment (UE), the configuration information including N types of Radio Link Control (RLC) entities corresponding to Packet Data Convergence Protocol (PDCP) entities in the UE. In this method, a network device sends configuration information to the UE to configure the N types of RLC entities associated with the PDCP entities. This allows the UE to effectively distribute service data according to the configuration information, thereby improving the efficiency of service data transmission.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, and in particular to a method, apparatus and readable storage medium for transmitting configuration information. Background Technology

[0002] In 5G wireless communication systems, extended reality (XR) services need to be supported. XR services can utilize Quality of Service (QoS) streaming for data packet transmission. During transmission, the Non-access Stratum (NAS) may not perform packet splitting, resulting in different data streams within the same QoS flow. Therefore, the data splitting problem in this XR service scenario needs to be addressed. Summary of the Invention

[0003] This disclosure provides a method, apparatus, and readable storage medium for transmitting configuration information.

[0004] In a first aspect, this disclosure provides a method for sending configuration information, executed by a network device, the method comprising:

[0005] Send configuration information to the user equipment, the configuration information including N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity in the user equipment.

[0006] In some possible implementations, N is the number of service types of service data, and the configuration information is also used to configure each type of RLC entity to transmit service data of the corresponding service type.

[0007] In some possible implementations, the configuration information is also used to configure a default RLC entity, which is used to transmit the first service.

[0008] In some possible implementations, each type of RLC entity includes at least one RLC entity.

[0009] In some possible implementations, the configuration information includes indicator identifiers corresponding to the N types of RLC entities, which are used to indicate whether some or all types of RLC entities have activated the first function.

[0010] In some possible implementations, the method further includes:

[0011] Send a first instruction message to the user equipment, the first instruction message being used to instruct the activation or deactivation of a first function of some or all types of RLC entities.

[0012] In some possible implementations, the first function includes a service offloading function or a packet replication function.

[0013] In some possible implementations, sending the first indication information to the user equipment includes:

[0014] Send downlink control information (DCI) to the user equipment, the DCI including the first indication information; or...

[0015] Send Access Control Layer Control Unit (MAC CE) signaling to the user equipment media, the MAC CE signaling including an information field for indicating the first indication information.

[0016] In some possible implementations, 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.

[0017] When the bit is at a first value, it indicates that the first function of the RLC entity corresponding to the bit is activated.

[0018] In some possible implementations, the method further includes:

[0019] The user equipment receives a notification message, which indicates that the number of times the RLC entity retransmits service data for the first function has reached the maximum number of retransmissions.

[0020] Secondly, this disclosure provides a method for receiving configuration information, executed by a user equipment, the method comprising:

[0021] Receive configuration information sent by network devices, the configuration information including N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity in the user equipment;

[0022] Based on the configuration information, service data is sent to at least one type of RLC entity.

[0023] In some possible implementations, N is the number of service types of service data, and the configuration information is also used to configure each type of RLC entity to transmit service data of the corresponding service type;

[0024] The step of sending service data to at least one type of RLC entity according to the configuration information includes:

[0025] Based on the configuration information and the service type of the service data, the service data is diverted and sent to the RLC entity corresponding to the service type.

[0026] In some possible implementations, the configuration information is also used to configure a default RLC entity, which is used to transmit the first service.

[0027] In some possible implementations, sending service data to at least one type of RLC entity according to the configuration information includes:

[0028] When the service data is the first service, the service data is sent to the default RLC entity.

[0029] In some possible implementations, sending service data to at least one type of RLC entity according to the configuration information includes:

[0030] When the RLC entity corresponding to the service data deactivates the service diversion function, the service data is diverted and sent to the default RLC entity.

[0031] In some possible implementations, the method further includes:

[0032] Based on the indication in the configuration information, determine whether some or all types of RLC entities have activated the first function.

[0033] In some possible implementations, the method further includes:

[0034] Receive first indication information sent by the network device, the first indication information being used to indicate the activation or deactivation of a first function of some or all types of RLC entities;

[0035] Based on the first instruction information, determine whether some or all types of RLC entities have activated the first function.

[0036] In some possible implementations, the first function includes a service offloading function or a packet replication function.

[0037] In some possible implementations, receiving the first indication information sent by the network device includes:

[0038] The network device receives a MAC CE signaling message, which includes an information field for indicating the first indication information.

[0039] In some possible implementations, determining whether some or all types of RLC entities activate the first function based on the first indication information includes:

[0040] When at least one bit in the information domain is a first value, the first function activation of the RLC entity corresponding to the at least one bit is determined.

[0041] In some possible implementations, the method further includes:

[0042] When the number of times the RLC entity retransmits service data for the first function reaches the maximum number of retransmissions, a notification message is sent to the network device.

[0043] Thirdly, this disclosure provides an apparatus for transmitting configuration information, which can be used to perform the steps executed by a network device in the first aspect or any possible design of the first aspect. The network device can implement the functions of the methods described above through hardware structures, software modules, or a combination of hardware structures and software modules.

[0044] When the apparatus shown in the third aspect is implemented by a software module, the apparatus may include a transceiver module, wherein the transceiver module can be used to support the communication apparatus in communicating.

[0045] When performing the steps described in the first aspect above, the transceiver module is configured to send configuration information to the user equipment, the configuration information including N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity in the user equipment.

[0046] Fourthly, this disclosure provides an apparatus for receiving configuration information, which can be used to perform the steps executed by a user equipment in the second aspect or any possible design of the second aspect. The user equipment can implement the functions of the methods described above through hardware structures, software modules, or a combination of hardware structures and software modules.

[0047] When the device shown in the fourth aspect is implemented by a software module, the device may include a transceiver module and a processing module coupled to each other. The transceiver module can be used to support the communication device to communicate, and the processing module can be used by the communication device to perform processing operations, such as generating information / messages to be sent, or processing received signals to obtain information / messages.

[0048] When performing the steps described in the second aspect above, the transceiver module is configured to receive configuration information sent by the network device, the configuration information including N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entities 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.

[0049] Fifthly, this disclosure provides a communication device, including 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.

[0050] In a sixth aspect, this disclosure provides a communication device including 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.

[0051] In a seventh aspect, this disclosure provides a computer-readable storage medium storing instructions (or computer programs, programs) that, when invoked and executed on a computer, cause the computer to perform the first aspect or any possible design of the first aspect.

[0052] Eighthly, this disclosure provides a computer-readable storage medium storing instructions (or computer programs, programs) that, when invoked and executed on a computer, cause the computer to perform the second aspect or any possible design of the second aspect.

[0053] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0054] The accompanying drawings, which are included to provide a further understanding of the embodiments of this disclosure and form part of this application, illustrate exemplary embodiments of this disclosure and, together with their descriptions, serve to explain the embodiments of this disclosure and do not constitute an improper limitation of the embodiments of this disclosure. In the drawings:

[0055] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the embodiments of the present disclosure.

[0056] Figure 1 A schematic diagram of a communication system architecture provided in an embodiment of this disclosure;

[0057] Figure 2 A schematic diagram of a protocol layer structure provided in an embodiment of this disclosure;

[0058] Figure 3 This is a flowchart illustrating a method for transmitting configuration information according to an exemplary embodiment;

[0059] Figure 4 This is a flowchart illustrating a method for sending configuration information according to an exemplary embodiment;

[0060] Figure 5 A flowchart illustrating another method for sending configuration information according to an exemplary embodiment;

[0061] Figure 6This is a schematic diagram illustrating the structure of the MAC CE signaling information field according to an exemplary embodiment;

[0062] Figure 7 This is a schematic diagram of the MAC CE signaling information field structure according to another exemplary embodiment;

[0063] Figure 8 This is a flowchart illustrating a method for receiving configuration information according to an exemplary embodiment;

[0064] Figure 9 This is a structural diagram illustrating an apparatus for sending configuration information according to an exemplary embodiment;

[0065] Figure 10 This is a structural diagram of a network device according to an exemplary embodiment;

[0066] Figure 11 This is a structural diagram illustrating an apparatus for receiving configuration information according to an exemplary embodiment;

[0067] Figure 12 This is a structural diagram of a user equipment according to an exemplary embodiment. Detailed Implementation

[0068] The embodiments of this disclosure will now be further described in conjunction with the accompanying drawings and specific implementation details.

[0069] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0070] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0071] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the words “if” and “suppose” as used herein may be interpreted as “when”, “when”, or “in response to a determination”.

[0072] Embodiments of this disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0073] Figure 1 This is a schematic diagram of a wireless communication system 100 to which this application applies. Figure 1 As shown in the embodiments of this disclosure, a method for transmitting configuration information can be applied to a wireless communication system 100, which may include a network device 101 and a user equipment 102. The user equipment 102 is configured to support carrier aggregation and can be connected to multiple carrier units of the network device 101, including a primary carrier unit and one or more secondary carrier units.

[0074] It should be understood that the wireless communication system 100 described above is applicable to both low-frequency and high-frequency scenarios. Application scenarios for the wireless communication system 100 include, but are not limited to, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, worldwide interoperability for microwave access (WiMAX) communication systems, cloud radio access network (CRAN) systems, future 5th-generation (5G) systems, new radio (NR) communication systems, or future evolved public land mobile network (PLMN) systems.

[0075] The user equipment 102 shown above can be a terminal, access terminal, terminal unit, terminal station, mobile station (MS), remote station, remote terminal, mobile terminal, wireless communication device, terminal agent, or terminal equipment, etc. This user equipment 102 may have wireless transceiver capabilities, enabling it to communicate (e.g., wirelessly) with one or more network devices in one or more communication systems and receive network services provided by the network devices. These network devices include, but are not limited to, the network device 101 shown in the figure.

[0076] User equipment 102 may be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in a future 5G network or terminal device in a future evolved PLMN network, etc.

[0077] Network device 101 can be an access network device (or access site). Access network device refers to equipment that provides network access functionality, such as a radio access network (RAN) base station. Specifically, network device 101 may include a base station (BS), or a base station and radio resource management equipment used to control the base station. Network device 101 may also include relay stations (relay equipment), access points, and base stations in future 5G networks, base stations in future evolved PLMN networks, or NR base stations. Network device 101 can be a wearable device or an in-vehicle device. Network device 101 can also be a communication chip with a communication module.

[0078] For example, network equipment 101 includes, but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (eNB) in LTE systems, radio network controllers (RNC), node B (NB) in WCDMA systems, radio controllers and base station controllers (BSC) in CRAN systems, base transceiver stations (BTS) in GSM or CDMA systems, home base stations (e.g., home evolved nodeB, or home node B, HNB), baseband units (BBU), transmitting and receiving points (TRP), transmitting points (TP), or mobile switching centers, etc.

[0079] The communication between network device 101 and user equipment 102 follows a certain protocol layer structure. Figure 2 This is a schematic diagram illustrating a protocol layer structure according to an embodiment of this disclosure. (Reference) Figure 2 As shown, the control plane protocol layer structure can include the functions of protocol layers such as Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer (PHY). The user plane protocol layer structure can include the functions of protocol layers such as PDCP, RLC, MAC, and Physical Layer.

[0080] This disclosure provides a method for transmitting configuration information, referring to... Figure 3 , Figure 3 This is a method for transmitting configuration information according to an exemplary embodiment, such as... Figure 3 As shown, the method includes steps S301 to S302, specifically:

[0081] In step S301, network device 101 sends configuration information to user equipment 102. 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.

[0082] In step S302, the user equipment 102 sends service data to at least one type of RLC entity based on the received configuration information.

[0083] In some possible implementations, network device 101 sends configuration information by sending RRC messages.

[0084] In some possible implementations, the business data can be XR business data, including augmented reality (AR) business data, virtual reality (VR) business data, and cloud gaming business data, etc.

[0085] In some possible implementations, N ≥ 1. For example, N = 2, meaning that network device 101 configures the UE's PDCP entity to be associated with two types of RLC entities.

[0086] In some possible implementations, N is related to the type of business data.

[0087] In some possible implementations, the PDCP entity of user equipment 102 receives service data sent by network device 101 through a higher layer and offloads the service data to at least one corresponding type of RLC entity.

[0088] In this embodiment of the disclosure, network device 101 sends configuration information to user equipment 102 to configure N types of RLC entities associated with the PDCP entity. This allows user equipment 102 to effectively distribute service data according to the configuration information, thereby improving the efficiency of service data transmission.

[0089] It is worth noting that in this embodiment, network device 101 may determine the configuration information, and user equipment 102 may perform uplink data offloading based on the configuration information. Alternatively, network device 101 may determine the configuration information, inform user equipment 102 of the configuration information, and then perform downlink data offloading. The following only lists the scenario where user equipment 102 performs offloading, but the offloading methods exemplified and described in the following embodiments are also applicable to the scenario where network device 101 performs offloading.

[0090] This disclosure provides a method for sending configuration information, which is executed by a network device 101. (Refer to...) Figure 4 , Figure 4 This is a method for sending configuration information according to an exemplary embodiment, such as... Figure 4 As shown, the method includes step S401, specifically:

[0091] In step S401, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0092] In some possible implementations, network device 101 sends configuration information by sending RRC messages.

[0093] In some possible implementations, the business data may be XR business data.

[0094] In some possible implementations, N ≥ 1. For example, N = 2, meaning that network device 101 configures the UE's PDCP entity to be associated with two types of RLC entities.

[0095] In some possible implementations, N is related to the type of business data.

[0096] Among them, business data can be used to distinguish different business types based on different dimensions.

[0097] In some embodiments, the classification dimensions of business types include, but are not limited to:

[0098] Business data importance refers to classifying business data into different business types based on varying degrees of importance. For example, if the importance of business data is categorized as high, medium, and low, then the business types could include those corresponding to high importance, medium importance, and low importance. Another example is using numbers to measure or characterize the importance of business data, such as first-level business data.

[0099] The attributes of business data, such as the intra-coded picture (Iframe) and predictive-coded frame (P frame) of business data, can be used to distinguish different business types of business data.

[0100] The sub-flow or QoS flow to which the service data belongs. For example, service data belonging to different sub-flows correspond to different service types, or different service data belonging to the same sub-flow correspond to different service types.

[0101] The priority level of business data refers to distinguishing different business types based on different priority levels. For example, different priority levels can be represented by high, medium, and low, or by numbers, with each priority level corresponding to a business type.

[0102] The reliability levels of business data refer to the different business types of business data based on varying reliability requirements. For example, different reliability requirements can be represented by high, medium, and low, or numerically, with each reliability requirement corresponding to a specific business type.

[0103] The purpose of business data refers to distinguishing different business types based on their intended use. For example, business data can be categorized as PDCP control PDUs and PDCP data PDUs. It's worth noting that business data can be categorized by data packet or by set. When categorizing by set, if a data packet within a set is classified as a first business type, all data packets within that set belong to that first business type.

[0104] In some possible implementations, each type of RLC entity includes at least one RLC entity.

[0105] In one example, in a scenario where duplication is not configured, each type of RLC entity contains one RLC entity. This single RLC entity may vary depending on the transport mode.

[0106] For example, in unacknowledged transmission mode (UM) and when an RLC entity is capable of bidirectional transmission (supporting uplink and downlink), an RLC entity is a UM RLC entity.

[0107] For example, in unacknowledged transmission mode, and when RLC entities are transmitted unidirectionally (supporting only uplink or downlink), one RLC entity refers to one RLC entity for each transmission direction, that is, one RLC entity is one uplink UM RLC entity and one downlink UM RLC entity.

[0108] For example, in Acknowledgment Transport Mode (AM), an RLC entity is an AM RLC entity.

[0109] In another example, in a scenario where replication is configured, each type of RLC entity contains multiple RLC entities. In this case, these multiple RLC entities still exhibit different characteristics depending on the transport mode.

[0110] For example, in unacknowledged transmission mode (UM) and when RLC entities are capable of bidirectional transmission, the plurality of RLC entities includes two UM RLC entities.

[0111] For example, in unacknowledged transmission mode, and when the RLC entities are transmitted unidirectionally, the multiple RLC entities include four UMRLC entities, of which two are uplink UM RLC entities and two are downlink UM RLC entities.

[0112] For example, in the confirmed transmission mode, the multiple RLC entities include two AM RLC entities.

[0113] In this embodiment of the disclosure, network device 101 sends configuration information to user equipment 102 to configure N types of RLC entities associated with the PDCP entity. This allows user equipment 102 to effectively distribute service data according to the configuration information, thereby improving the efficiency of service data transmission.

[0114] This disclosure provides a method for sending configuration information, which is executed by a network device 101. The method includes step S401, specifically:

[0115] In step S401, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0116] Where N is the number of service types of service data, and the configuration information is also used to configure each type of RLC entity to transmit the corresponding service data.

[0117] In some possible implementations, the number of service types can be 2, then N=2, that is, the configuration information configures 2 types of RLC entities, and each type of RLC entity corresponds to the transmission of service data of one service type.

[0118] In some possible implementations, the service type of the service data may include: intra-coded picture (I frame) and predictive-coded frame (P frame), i.e., I frame and P frame, where I frame is key frame.

[0119] In this embodiment, among the two types of RLC entities, one type of RLC entity corresponds to the first logical channel and is used to transmit I-frame service data; the other type of RLC entity corresponds to the second logical channel and is used to transmit P-frame service data.

[0120] In some possible implementations, the business type of the business data may include data from different streams or sub-streams, such as business data from a first sub-flow (sub-flow1) and business data from a second sub-flow (sub-flow2).

[0121] In this embodiment, among the two types of RLC entities, one type of RLC entity is used to transmit the first sub-stream service data, and the other type of RLC entity is used to transmit the second sub-stream service data.

[0122] In some possible implementations, the service type of the 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, while PDCP data protocol data unit is a data packet received by PDCP from a higher layer.

[0123] At this point, the N types of RLC entities are denoted as the first type RLC entity, the second type RLC entity, ..., the Nth type RLC entity.

[0124] In one embodiment, the network device may specify or the protocol may agree on a first RLC entity or a second RLC entity;

[0125] In one embodiment, the network device may specify or the protocol may define a primary RLC entity and a secondary RLC entity (an RLC entity other than the primary RLC entity);

[0126] In one embodiment, the network device may specify or the protocol may agree on a default RLC entity;

[0127] In this embodiment, among the N types of RLC entities, the first RLC entity is used to transmit PDCP control data, and the second RLC entity is used to transmit PDCP data protocol data units.

[0128] In one example, the first RLC entity is the primary RLC entity.

[0129] In some possible implementations, each type of RLC entity includes at least one RLC entity.

[0130] In this embodiment of the disclosure, network device 101 configures the number of types of RLC entities associated with PDCP entities for 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.

[0131] This disclosure provides a method for sending configuration information, which is executed by a network device 101. The method includes step S401, specifically:

[0132] In step S401, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0133] 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.

[0134] In some possible implementations, the N types of RLC entities are used to transmit service data of different service types. For example, the N types of RLC entities correspond to service data of N service types.

[0135] In some possible implementations, the MN and SN can be used for dual connectivity (DC) of the UE. In dual connectivity, the UE maintains the RRC connection of the serving cell under the MN and can be configured to connect to the serving cell under the SN to improve data throughput.

[0136] This disclosure provides a method for sending configuration information, which is executed by a network device 101. The method includes step S401, specifically:

[0137] In step S401, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0138] The configuration information is also used to configure the default RLC entity, which is used to transmit the first service.

[0139] In some possible implementations, the default RLC entity can be one of the N types of RLC entities, or it can be configured in addition to the N types of RLC entities.

[0140] In one example, the default RLC entity is either the primary RLC entity or another RLC entity specified by the network device.

[0141] In some possible implementations, the first service is service data of a specified service type, for example, the first service is PDCP control data.

[0142] In some possible implementations, the first service is service data for which no corresponding RLC entity is configured.

[0143] In some possible implementations, user equipment 102 may submit service data of a specified service type, or service data for which no corresponding RLC entity is configured, to the default RLC entity according to the configuration information, so as to achieve data diversion.

[0144] In this embodiment of the disclosure, network device 101 configures a default RLC entity for user equipment 102 to enable data offloading of the first service by user equipment 102.

[0145] This disclosure provides a method for sending configuration information, which is executed by a network device 101. The method includes step S401, specifically:

[0146] In step S401, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0147] The configuration information includes indicator identifiers corresponding to N types of RLC entities. These indicator identifiers are used to indicate whether some or all types of RLC entities have activated the first function.

[0148] The first function can be either a business diversion function or a package replication function.

[0149] In some possible implementations, if the network device 101 has configured the configuration information but does not include the indication identifiers corresponding to the N types of RLC entities in the configuration information, it is assumed that the first function, such as the service offloading function, has been activated for all N types of RLC entities in the configuration information.

[0150] In some possible implementations, the indicator identifier occupies one bit, and the N types of RLC entities can be uniformly indicated by the same bit.

[0151] For example, when the bit corresponding to the indicator is 1, all N types of RLC entities activate the service diversion function.

[0152] For example, when the bit corresponding to the indicator is 0, all N types of RLC entities will deactivate the service diversion function.

[0153] In some possible implementations, the indicator occupies multiple bits. The configuration information includes bits corresponding to each type of RLC entity to indicate whether each type of RLC entity activates a first function, such as a traffic offloading function. Specifically, when an RLC entity of a certain type indicates activation of the first function, all RLC entities under that type activate the first function.

[0154] In one example, when the bit corresponding to the indicator of any type of RLC entity is 1, the RLC entity of that type activates a first function such as traffic offloading; when the bit corresponding to the indicator of any type of RLC entity is 0, the RLC entity of that type deactivates the traffic offloading function.

[0155] In another example, when all the bits have the same value, the indicator corresponds to the activation status of the first function of all types of RLC entities. For example, when all the bits are 1, it indicates that the first function is activated for all types of RLC entities.

[0156] In some possible implementations, the indicator occupies multiple bits, each bit indicating whether a first function of an RLC entity is activated or deactivated. For example, the configuration information includes bits corresponding to each RLC entity to indicate whether a single RLC entity has activated a first function such as traffic offloading.

[0157] In one example, when the bit corresponding to the indicator of any RLC entity is 1, the RLC entity activates a first function, such as a traffic offloading function; when the bit corresponding to the indicator of any RLC entity is 0, the RLC entity deactivates the first function.

[0158] In some possible implementations, for a deactivated RLC entity, user equipment 102 may offload its associated service data to the default RLC entity.

[0159] To facilitate understanding, a specific example is provided here:

[0160] The configuration information specifies three types of RLC entities corresponding to the PDCP entity: the first RLC entity, the second RLC entity, and the third RLC entity. The first RLC entity is configured to transmit service data or control PDUs of the first service type, the second RLC entity is configured to transmit service data of the second service type, and the third RLC entity is configured to transmit service data of the third service type.

[0161] It is worth noting that the naming conventions for the first RLC entity, second RLC entity, or third RLC entity described in the embodiments of this disclosure are for reference and distinction only, and are not intended to limit the RLC entity. For example, the first RLC entity can also be named the main RLC entity, and the second or third RLC entity can also be named the auxiliary RLC entity.

[0162] In this example, the configuration information also configures the activation of the service offloading function for the first RLC entity, the activation of the service offloading function for the second RLC entity, and the deactivation of the service offloading function for the third RLC entity.

[0163] According to the configuration information, during the service offloading process, the PDCP layer of user equipment 102 submits the service data or control PDU of the first service type to the first RLC entity, and submits the service data of the second service type to the second RLC entity.

[0164] Furthermore, if a default RLC entity is also configured in this example, user equipment 102 can submit the service data of the third service type to the default RLC entity. Therefore, even when the third RLC entity is deactivated, the corresponding service can still be routed.

[0165] In this embodiment of the disclosure, the network device 101 synchronously indicates in the configuration information it sends whether some or all of the RLC entities have activated the first function, such as the service offloading function, so that the user equipment 102 can know whether some or all of the RLC entities have activated the first function, such as the service offloading function, based on the configuration information.

[0166] This disclosure provides a method for sending configuration information, which is executed by a network device 101. (Refer to...) Figure 5 , Figure 5 This is a method for sending configuration information according to an exemplary embodiment, such as... Figure 5 As shown, the method includes steps S501 to S502, specifically:

[0167] In step S501, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0168] In step S502, network device 101 sends first indication information to user equipment 102. The first indication information is used to indicate the activation or deactivation of a first function of some or all types of RLC entities.

[0169] The order of steps S501 and S502 is for illustrative purposes only. For example, steps S501 and S502 can also be executed simultaneously.

[0170] In some possible implementations, network device 101 may send the first indication information by sending downlink control information (DCI) or media access control element (MAC CE) signaling.

[0171] In some possible implementations, the first indication information can uniformly indicate whether the N types of RLC entities activate the first function, that is, to uniformly control all types of offloading RLC entities.

[0172] For example, a single bit can be used to uniformly indicate whether all N types of RLC entities have activated the first function.

[0173] In some possible implementations, the first indication information corresponds to multiple bits, each bit indicating whether a type of RLC entity has activated the first function.

[0174] For example, the bits corresponding to each type of RLC entity in the first indication information indicate whether each type of RLC entity has activated a first function, such as service routing. Specifically, when an RLC entity of a certain type indicates activation of the first function, all RLC entities of that type activate the first function.

[0175] In one example, when the bit corresponding to any type of RLC entity is 1, the RLC entity of that type activates the first function, such as the traffic splitting function; when the bit corresponding to any type of RLC entity is 0, the RLC entity of that type deactivates the traffic splitting function.

[0176] In some possible implementations, the first indication information corresponds to multiple bits, each bit indicating whether a first function of each RLC entity is activated or deactivated. For example, the bits corresponding to each RLC entity in the first indication information can be used to indicate whether each traffic splitting RLC entity has activated a first function, such as a traffic splitting function.

[0177] In one example, when the bit value corresponding to any RLC entity is 1, the RLC entity activates a first function, such as a traffic offloading function; when the bit value corresponding to any RLC entity is 0, the RLC entity deactivates the first function.

[0178] In some possible implementations, the first function includes a traffic offloading function or a PDCP package copying function.

[0179] In this embodiment of the disclosure, network device 101 indicates whether some or all RLC entities activate the first function through dynamic indication, so as to adaptively adjust whether the RLC entities activate the first function.

[0180] This disclosure provides a method for sending configuration information, which is executed by a network device 101. The method includes steps S501 to S502', specifically:

[0181] In step S501, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0182] In step S502', network device 101 sends downlink control information (DCI) to user equipment 102, and the DCI includes first indication information.

[0183] The first indication information is used to indicate the activation or deactivation of a first function of some or all types of RLC entities.

[0184] In some possible implementations, the first function includes a traffic offloading function or a PDCP package copying function.

[0185] In this embodiment of the disclosure, network device 101 dynamically sends first instruction information through DCI, thereby dynamically configuring whether N types of RLC entities activate the first function.

[0186] This disclosure provides a method for sending configuration information, which is executed by a network device 101. The method includes steps S501 to S502”, specifically:

[0187] In step S501, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0188] In step S502, network device 101 sends a Media Access Control Layer Control Unit (MAC CE) signaling message to user equipment 102. The MAC CE signaling message includes an information field for indicating first indication information.

[0189] The first instruction information is used to indicate one of the following: activating or deactivating a first function of some or all types of RLC entities.

[0190] In some possible implementations, the information field includes at least one of the following:

[0191] Bits corresponding to all types of RLC entities;

[0192] The bits corresponding to each type of RLC entity;

[0193] The bits corresponding to each RLC entity.

[0194] In some possible implementations, the information field contains bits corresponding to all types of RLC entities, that is, the information field uses a single bit to uniformly indicate whether all types of RLC entities have activated the first function.

[0195] For example, when the information field contains a bit corresponding to all types of RLC entities, if this bit has a first value (e.g., 1), it indicates that all types of RLC entities have activated the first function; if this bit has a second value (e.g., 0), it indicates that all types of RLC entities have deactivated the first function. Furthermore, the activation status of the first function of any type of RLC entity applies to all RLC entities under that type.

[0196] In some possible implementations, the information field contains bits corresponding to each type of RLC entity, meaning the information field indicates whether each type of RLC entity activates the first function. For example, the information field contains bits corresponding to each type of RLC entity. Taking a scenario with three types of RLC entities as an example, the information field structure can be referenced. Figure 6 Corresponding example.

[0197] When the bit corresponding to any type of RLC entity is a first value (e.g., 1), the RLC entity of that type activates a first function, such as traffic offloading. When the bit corresponding to the indicator of any type of RLC entity is a second value (e.g., 0), the RLC entity of that type deactivates the first function. When an RLC entity of a certain type indicates activation of the first function, all RLC entities under that type activate the first function.

[0198] When the bit values ​​corresponding to each type of RLC entity are the same, such as all being 1, this information field indicates that the first function has been activated for all types of RLC entities.

[0199] In some possible implementations, the information field contains bits corresponding to each RLC entity, indicating whether each RLC entity has activated the first function. For example, if the information field contains bits corresponding to each RLC entity, and there are three RLC entities, the information field structure can be referenced. Figure 7 Corresponding example.

[0200] When the bit corresponding to any RLC entity is a first value (e.g., 1), the RLC entity activates a first function, such as traffic offloading. When the bit corresponding to any RLC entity is a second value (e.g., 0), the RLC entity deactivates the first function.

[0201] In some possible implementations, the first function includes a traffic offloading function or a PDCP package copying function.

[0202] To facilitate understanding of this embodiment, several specific examples are listed below:

[0203] Example 1:

[0204] Figure 6 This illustrates an information domain structure used to indicate whether the service routing function is activated. For example... Figure 6 As shown, the information field includes: a first part of bits and a second part of bits.

[0205] The first part of the bits is used to indicate the identifier (DRB ID) of the Data Radio Bearer (DRB), and is assumed to be 5 bits long. One DRB can correspond to service data of multiple service types, that is, it can correspond to multiple types of RLC entities.

[0206] The second part of the bits is used to indicate whether each type of RLC entity has activated the service offloading function. Taking three types of RLC entities as an example, the second part of the bits is 3 bits long, with each type of RLC entity occupying 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.

[0207] Among them, RLC i In this context, 'i' represents the RLC entity configured for traffic offloading in the DRB. For example, it is the logical channel identifier of the secondary RLC entities in ascending order within the primary cell group (MCG) and secondary cell group (SCG), i.e., 'i' represents the RLC type or RLC entity. Figure 6 In this case, i can be 0, 1, or 2.

[0208] In RLC i When the corresponding bit value is 1, this RLC i The entity activated the business offloading function; in RLC i When the corresponding bit value is 0, this RLC i The entity deactivated the business diversion function.

[0209] Example 2:

[0210] Figure 7 This illustrates an information field structure used to indicate whether the PDCP packet replication function is activated. For example... Figure 7 As shown, the information field includes: a first part of bits and a second part of bits.

[0211] The first part of the bits is used to indicate the identifier (RLC ID) of the first RLC entity type, and it is assumed that the length of the first part of the bits is 5 bits.

[0212] The second part of the bits is used to indicate whether the second RLC entity has activated the packet replication function; assuming the second part of the bits is 3 bits long, RLC... i The 'i' in the code 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 secondary cell group (SCG). In other words, 'i' represents the index of the second RLC entity. Figure 7 In this case, i can be 0, 1, or 2. This example uses three RLC entities.

[0213] The first RLC entity and the second RLC entity can be RLC entities of the same type. The first RLC entity can also be called the replicated RLC entity or the primary RLC entity, and the second RLC entity can also be called the replicated RLC entity or the secondary RLC entity.

[0214] In RLC i When the corresponding bit value is 1, this RLC i The entity has activated the packet replication function, and the business data of the first RLC entity can be replicated and sent to this RLC. i Entity; in RLC i When the corresponding bit value is 0, this RLC i The entity has deactivated the package copy function.

[0215] In this example, the configuration for whether to activate the PDCP packet replication function can be refined to the RLC entity. The first RLC entity (or the RLC entity being replicated) can be configured to activate or deactivate the packet replication function of the second RLC entity (or the replicating RLC entity), providing an indication for the service offloading of user equipment 102.

[0216] This disclosure provides a method for sending configuration information, which is executed by a network device 101. The method includes steps S501 to S502-1, specifically:

[0217] In step S501, network device 101 sends configuration information to user equipment 102. The configuration information includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entity.

[0218] Step S502-1: Receive a notification message from the user equipment. The notification message indicates that the number of times the RLC entity retransmits service data for the first function has reached the maximum number of retransmissions.

[0219] In some possible implementations, step S502-1 may include: upon receiving a notification message from user equipment 102, network device 101 sends first indication information to user equipment 102, the first indication information being used to instruct the deactivation of a first function of the RLC entity corresponding to the notification message.

[0220] In some possible implementations, the first function includes a traffic offloading function or a PDCP package copying function.

[0221] In some possible implementations, upon receiving a notification message, it indicates that the RLC entity used for the first function has reached its maximum retransmission limit for retransmissions of service data. This suggests that the RLC entity can no longer perform retransmissions, or that the RLC entity's communication status may be problematic or faulty, making it unsuitable for further traffic offloading.

[0222] Upon receiving the notification message, network device 101 can promptly send a first instruction message to instruct user equipment 102 to activate the first function of the RLC entity. This allows user equipment 102 to adjust the traffic splitting method in a timely manner. For example, it can stop sending service data to the RLC entity whose first function has been deactivated, and instead send service data of the service type corresponding to the deactivated RLC entity to the default RLC entity. This ensures that the normal splitting of service data of that service type can still be achieved, guaranteeing data transmission efficiency.

[0223] In one example, when the RLC entity used for traffic offloading reaches the maximum number of retransmissions, user equipment 102 sends a notification message to network equipment 101.

[0224] In one example, when the RLC entity used for packet replication reaches the maximum number of retransmissions, user equipment 102 sends a notification message to network device 101.

[0225] In this embodiment of the disclosure, network device 101 can dynamically deactivate the first function of the corresponding RLC entity when it receives a notification message from user equipment 102.

[0226] This disclosure provides a method for receiving configuration information, which is executed by a user equipment 102. (Refer to...) Figure 8 , Figure 8 This is a method for receiving configuration information according to an exemplary embodiment, such as... Figure 8 As shown, the method includes steps S801 to S802, specifically:

[0227] In step S801, user equipment 102 receives configuration information sent by network device 101. 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.

[0228] In step S802, user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.

[0229] In some possible implementations, N is related to the type of business data.

[0230] In some possible implementations, the PDCP layer of user equipment 102 splits service data according to service type and sends the corresponding type of service data to different types of RLC entities.

[0231] In some possible implementations, the business data may be XR business data.

[0232] In some possible implementations, each type of RLC entity includes at least one RLC entity.

[0233] In one example, in a scenario where replication is not configured, each type of RLC entity contains one RLC entity. This single RLC entity may vary depending on the transport mode.

[0234] For example, in unacknowledged transmission mode, and when an RLC entity is capable of bidirectional transmission (supporting uplink and downlink), an RLC entity is a UM RLC entity.

[0235] For example, in unacknowledged transmission mode, and when RLC entities are transmitted unidirectionally (supporting only uplink or downlink), one RLC entity refers to one RLC entity for each transmission direction, that is, one RLC entity is one uplink UM RLC entity and one downlink UM RLC entity.

[0236] For example, in the confirmed transmission mode, this RLC entity is an AM RLC entity.

[0237] In another example, in a scenario where replication is configured, each type of RLC entity contains multiple RLC entities. In this case, these multiple RLC entities still exhibit different characteristics depending on the transport mode.

[0238] For example, in unacknowledged transmission mode, and when the RLC entities are capable of bidirectional transmission, the plurality of RLC entities includes two UMRLC entities.

[0239] For example, in unacknowledged transmission mode, and when the RLC entities are transmitted unidirectionally, the multiple RLC entities include four UMRLC entities, of which two are uplink UM RLC entities and two are downlink UM RLC entities.

[0240] For example, in the confirmed transmission mode, the multiple RLC entities include two AM RLC entities.

[0241] In some possible implementations, the PDCP entity of user equipment 102 receives service data sent by network device 101 through a higher layer and offloads the service data to at least one corresponding type of RLC entity.

[0242] In this embodiment of the disclosure, the user equipment 102 learns the N types of RLC entities associated with the PDCP entity based on the configuration information of the network device 101. Thus, the user equipment 102 can effectively distribute service data according to the configuration information to improve the efficiency of transmitting service data.

[0243] This disclosure provides a method for receiving configuration information, which is executed by a user equipment 102. The method includes steps S801 to S802-1, specifically:

[0244] In step S801, user equipment 102 receives configuration information sent by network device 101. 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.

[0245] Where N is the number of service types of service data, and the configuration information is also used to configure each type of RLC entity to transmit the corresponding service data.

[0246] Step S802-1: User equipment 102 sends service data to the RLC entity of the corresponding service type according to the configuration information and the service type of the service data.

[0247] In some possible implementations, each type of RLC entity includes at least one RLC entity.

[0248] In some possible implementations, the number of service types can be 2, then N=2, that is, the configuration information configures 2 types of RLC entities, and each type of RLC entity corresponds to the transmission of service data of one service type.

[0249] In some possible implementations, the service type of the service data may include I-frames and P-frames.

[0250] In the two types of RLC entities, one type of RLC entity corresponds to the first logical channel and is used to transmit I-frame service data; the other type of RLC entity corresponds to the second logical channel and is used to transmit P-frame service data.

[0251] In some possible implementations, the business type of the business data may include: data from different streams or sub-streams, such as first sub-stream business data and second sub-stream business data.

[0252] Of the two types of RLC entities, one type is used to transmit the first substream service data, and the other type is used to transmit the second substream service data.

[0253] In some possible implementations, the service type of the service data may include: PDCP control data and PDCP data protocol data units.

[0254] At this point, the N types of RLC entities are denoted as the first type RLC entity, the second type RLC entity, ..., the Nth type RLC entity.

[0255] In one embodiment, the network device may specify or the protocol may agree on a first RLC entity or a second RLC entity;

[0256] In one embodiment, the network device may specify or the protocol may define a primary RLC entity and a secondary RLC entity (an RLC entity other than the primary RLC entity);

[0257] In one embodiment, the network device may specify or the protocol may agree on a default RLC entity;

[0258] In this implementation, among the N types of RLC entities, the first RLC entity is used to transmit PDCP control data, and the second RLC entity is used to transmit PDCP data protocol data units. In one example, the first RLC entity is the primary RLC entity.

[0259] In this embodiment of the disclosure, the user equipment 102 performs effective data diversion according to the service type of the service data.

[0260] This disclosure provides a method for receiving configuration information, which is executed by user equipment 102. The method includes steps S801 to S802-2, specifically:

[0261] In step S801, user equipment 102 receives configuration information sent by network device 101. 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.

[0262] The configuration information is also used to configure the default RLC entity, which is used to transmit the first service.

[0263] Step S802-2: When the service data is the first service, the user equipment 102 sends the service data to the default RLC entity.

[0264] In some possible implementations, the default RLC entity can be one of the N types of RLC entities, or it can be configured in addition to the N types of RLC entities.

[0265] In one example, the default RLC entity is the first RLC entity, the primary RLC entity, or another RLC entity specified by the network device.

[0266] In some possible implementations, the first service is service data of a specified service type, for example, the first service is PDCP control data.

[0267] In some possible implementations, the first service is service data for which no corresponding RLC entity is configured.

[0268] In some possible implementations, user equipment 102 may submit service data of a specified service type, or service data for which no corresponding RLC entity is configured, to the default RLC entity to achieve data offloading.

[0269] This disclosure provides a method for receiving configuration information, which is executed by user equipment 102. The method includes steps S801 to S802-3, specifically:

[0270] In step S801, user equipment 102 receives configuration information sent by network device 101. 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.

[0271] The configuration information is also used to configure the default RLC entity, which is used to transmit the first service.

[0272] In step S802-3, when the RLC entity corresponding to the service data deactivates the service diversion function, the user equipment 102 diverts and sends the service data to the default RLC entity.

[0273] In some possible implementations, if user equipment 102 receives configuration information, it assumes that the N types of RLC entities in the configuration information have activated the service offloading function.

[0274] In some possible implementations, the configuration information includes indicator identifiers corresponding to N types of RLC entities. These indicator identifiers are used to indicate whether some or all types of RLC entities have activated the first function. In this case, before step S802-3, the user equipment 102 determines whether the N types of RLC entities have activated the first function according to the following steps S800-11:

[0275] In step S800-11, user equipment 102 determines whether some or all types of RLC entities have activated the service offloading function based on the indication identifier in the configuration information.

[0276] In some possible implementations, the indicator occupies one bit, and the same bit is used in the configuration information to uniformly indicate whether N types of RLC entities have activated the first function, such as the service diversion function, that is, whether all types of RLC entities have activated the first function.

[0277] For example, when the bit corresponding to the indicator is 1, all N types of RLC entities activate the service offloading function. As another example, when the bit corresponding to the indicator is 0, all N types of RLC entities deactivate the service offloading function.

[0278] In some possible implementations, the indicator occupies multiple bits. The configuration information includes bits corresponding to each type of RLC entity, thereby indicating whether each type of RLC entity has activated a primary function such as traffic offloading.

[0279] For example, when the bit corresponding to the indicator of any type of RLC entity is 1, the RLC entity of that type activates the first function, such as the traffic offloading function; when the bit corresponding to the indicator of any type of RLC entity is 0, the RLC entity of that type deactivates the traffic offloading function. When an RLC entity of a certain type indicates that the first function is activated, all RLC entities under that type activate the first function.

[0280] For example, when all the values ​​of these bits are the same, the indicator corresponds to the activation status of the first function of all types of RLC entities. For instance, when all the bit values ​​are 1, it indicates that the first function of all types of RLC entities is activated.

[0281] In some possible implementations, the indicator occupies multiple bits, each bit indicating whether a first function of each RLC entity is activated or deactivated. For example, the configuration information includes bits corresponding to each RLC entity to indicate whether each RLC entity has activated a first function such as traffic offloading.

[0282] In one example, when the bit corresponding to the indicator of any RLC entity is 1, the RLC entity activates a first function, such as a traffic offloading function; when the bit corresponding to the indicator of any RLC entity is 0, the RLC entity deactivates the first function.

[0283] In some possible implementations, user equipment 102 determines, based on the received first indication information, whether some or all types of RLC entities have activated a first function, such as a traffic offloading function. This can be seen in the description of the following embodiments.

[0284] In some possible implementations, for an RLC entity that has activated the service offloading function, the PDCP of user equipment 102 can deliver service data of the corresponding service type to the associated RLC entity.

[0285] In some possible implementations, for an RLC entity whose service offloading function is deactivated, the PDCP of user equipment 102 can submit the service data of the corresponding service type of the RLC entity to the default RLC entity, while still ensuring that the offloading of this type of service data can be achieved.

[0286] In this embodiment of the disclosure, the user equipment 102 learns from the configuration information whether some or all of the RLC entities have activated the first function, such as the service offloading function. When the service offloading function of any RLC entity is deactivated, the user equipment 102 can offload data to the default RLC entity.

[0287] This disclosure provides a method for receiving configuration information, which is executed by a user equipment 102. The method includes steps S801, S800-21, S800-22, and S802, specifically:

[0288] In step S801, user equipment 102 receives configuration information sent by network device 101. 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.

[0289] In step S800-21, user equipment 102 receives first indication information sent by network device 101. The first indication information is used to indicate the activation or deactivation of a first function of some or all types of RLC entities.

[0290] In step S800-22, the user equipment 102 determines, based on the first instruction information, whether some or all types of RLC entities have activated the first function.

[0291] In step S802, user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.

[0292] In some possible implementations, the first indication information can uniformly indicate whether the first function is activated for all N types of RLC entities, that is, indicate whether the first function is activated for all types of RLC entities. For example, a single bit can be used to uniformly indicate whether all N types of RLC entities are activated for the first function. Specifically, when a certain type of RLC entity indicates that the first function is activated, all RLC entities of that type are activated for the first function.

[0293] In some possible implementations, the first indication information indicates whether each type of RLC entity in all N types or a subset of N types has activated 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 has activated the first function. Wherein, when an RLC entity of a certain type indicates activation of the first function, all RLC entities under that type activate the first function.

[0294] In some possible implementations, the first indication information indicates whether each RLC entity has activated the first function. For example, each RLC entity has a corresponding bit, and each bit indicates whether the corresponding RLC entity has activated the first function.

[0295] In some possible implementations, the user equipment 102 receives the first indication information, which may be by receiving the DCI sent by the network device 101 and obtaining the first indication information in the DCI.

[0296] In some possible implementations, the user equipment 102 receives the first indication information, which may be receiving MAC CE signaling sent by the network device 101. The MAC CE signaling includes an information field for indicating the first indication information.

[0297] In some possible implementations, the first function includes a traffic offloading function or a packet replication function.

[0298] In some possible implementations, when the first function is a service offloading function, step S802 can be implemented with reference to the following steps S802-3, specifically:

[0299] In step S802-3, when the RLC entity corresponding to the service data deactivates the service diversion function, the user equipment 102 diverts and sends the service data to the default RLC entity.

[0300] In this embodiment of the disclosure, the user equipment 102 learns from the first instruction information whether some or all of the RLC entities have activated the first function, so that it can adjust the traffic splitting method in a timely manner.

[0301] This disclosure provides a method for receiving configuration information, which is executed by a user equipment 102. The method includes steps S801, S800-21', S800-22', and S802, specifically:

[0302] In step S801, user equipment 102 receives configuration information sent by network device 101. 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.

[0303] In step S800-21', user equipment 102 receives MAC CE signaling sent by network device 101. The MAC CE signaling includes an information field for indicating first indication information.

[0304] In step S800-22', when at least one bit in the information field is a first value, the user equipment 102 determines that the first function of the RLC entity corresponding to at least one bit is activated.

[0305] In step S802, user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.

[0306] In some possible implementations, the information field includes at least one of the following:

[0307] Bits corresponding to all types of RLC entities;

[0308] The bits corresponding to each type of RLC entity;

[0309] The bits corresponding to each RLC entity.

[0310] In some possible implementations, the information field includes a bit for indicating the activation status of the first function, uniformly indicating whether the first function is activated for all types of RLC entities.

[0311] For example, when a bit is at the first value (e.g., 1), it indicates that the first function is activated for all types of RLC entities; when the bit is at the second value (e.g., 0), it indicates that the first function is deactivated for all types of RLC entities. Furthermore, the activation status of the first function for any type of RLC entity applies to all RLC entities under that type.

[0312] In some possible implementations, the information field includes more than one bit indicating the first functional activation state. For example, the information field may contain bits corresponding to each type of RLC entity. In this case, refer to... Figure 6 As shown.

[0313] When the bit corresponding to any type of RLC entity is a first value (e.g., 1), the RLC entity of that type activates a first function, such as traffic offloading. When the bit corresponding to the indicator of any type of RLC entity is a second value (e.g., 0), the RLC entity of that type deactivates the first function. When an RLC entity of a certain type indicates activation of the first function, all RLC entities under that type activate the first function.

[0314] If more than one bit value is the same, such as all being 1, it indicates that the first function of all types of RLC entities is activated.

[0315] In some possible implementations, the information field includes more than one bit for indicating the first functional activation state; for example, one bit corresponds to each RLC entity. (Refer to...) Figure 7 As shown.

[0316] When the bit corresponding to any RLC entity is a first value (e.g., 1), the RLC entity activates a first function, such as traffic offloading. When the bit corresponding to any RLC entity is a second value (e.g., 0), the RLC entity deactivates the first function.

[0317] In some possible implementations, the first function includes a traffic offloading function or a packet replication function.

[0318] In this embodiment of the disclosure, network device 101 dynamically instructs the activation or deactivation of some or all of the first functions of RLC entities through MAC CE signaling, and user equipment 102 promptly learns the activation status of RLC entities based on MAC CE signaling and adjusts the traffic splitting method accordingly.

[0319] This disclosure provides a method for receiving configuration information, which is executed by a user equipment 102. The method includes steps S801, S800-21, S800-22, S802, and S803, specifically:

[0320] In step S801, user equipment 102 receives configuration information sent by network device 101. 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.

[0321] In step S800-21, user equipment 102 receives the first instruction information sent by network device 101.

[0322] In step S800-22, the user equipment 102 determines, based on the first instruction information, whether some or all types of RLC entities have activated the first function.

[0323] In step S802, user equipment 102 sends service data to at least one type of RLC entity according to the configuration information.

[0324] In step S803, when the number of times the RLC entity retransmits service data for the first function reaches the maximum number of retransmissions, the user equipment 102 sends a notification message to the network device 101.

[0325] In some possible implementations, the first function includes a traffic offloading function or a PDCP package copying function.

[0326] In some possible implementations, when the RLC entity used for traffic offloading reaches its maximum retransmission count, user equipment 102 sends a notification message to network device 101. This indicates that the RLC entity can no longer perform retransmissions, or that the RLC entity's communication status may be problematic or faulty, making it unsuitable for traffic offloading.

[0327] In some possible implementations, when the RLC entity used for packet replication reaches the maximum number of retransmissions, user equipment 102 sends a notification message to network device 101.

[0328] In some possible implementations, network device 101 may dynamically deactivate the first function of the corresponding RLC entity when it receives a notification message from user equipment 102.

[0329] In this embodiment of the disclosure, when the RLC entity used for the first function reaches the maximum number of retransmissions, the user equipment 102 can promptly report to the network device 101 so that the network device 101 can adjust the activation status, such as deactivating the first function of a certain RLC entity. Thus, the user equipment 102 can promptly adjust the traffic splitting method, for example, no longer sending service data to the deactivated RLC entity, but instead sending service data of the service type corresponding to the deactivated RLC entity to the default RLC entity, to ensure that the normal splitting of service data of that service type can still be achieved, thus guaranteeing data transmission efficiency.

[0330] To better understand the content of the embodiments of this disclosure, some specific examples are listed below:

[0331] Example 1:

[0332] In specific service offloading scenarios (such as XR services), network device 101 configures user equipment 102 to map PDCP entities to N types of RLC entities, where N corresponds to the service type classification. For example, the first type of service data, the second type of service data, and so on up to the Nth type of service data.

[0333] The classification of business types can have many dimensions, including but not limited to: distinguishing based on the importance of business data, distinguishing based on the attributes of business data, distinguishing based on the sub-QOS flow or QoS flow to which the business data belongs, distinguishing based on the priority level of business data, distinguishing based on the reliability level of business data, or distinguishing based on the purpose of business data. See the descriptions in the foregoing embodiments for further details.

[0334] As one embodiment of this example, network device 101 assigns its transmission RLC entity to different service types, i.e., performs traffic splitting. For example, network device 101 configures two types of RLC entities, namely a first type RLC entity and a second type RLC entity; these 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, respectively. For example, the first type RLC entity corresponds to logical channel 1 for I-frame service data transmission; the second type RLC entity corresponds to logical channel 2 for P-frame service data transmission.

[0335] As one embodiment of this example, when user equipment 102 transmits data uplink, the PDCP layer needs to deliver the data to the corresponding type-transmission RLC entity based on the different service types of the service data. The PDCP layer may determine the service type of each data packet and then deliver it accordingly; alternatively, it may make batch decisions based on a set of data packets. For example, after determining the service type of one data packet in the set and routing it accordingly, other data packets in that set will also be delivered to the same type-transmission RLC entity. This eliminates the need for routing decisions on a data packet-by-data packet basis, improving decision efficiency.

[0336] As one embodiment of this example, each type of RLC entity corresponds to at least one UM entity (supporting both uplink and downlink), or at least two UM entities (supporting only uplink or downlink), or at least one AM entity.

[0337] As one embodiment of this example, network device 101 specifies that the transmission RLC entity for different service types can belong to different MN or SN nodes, or to the same MN or SN node, or to the same cell or different cells.

[0338] As one embodiment of this example, 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. Alternatively, if no RLC entity is configured for certain service types, the default RLC entity can be used for transmission, such as the first RLC entity or the main RLC entity.

[0339] It is worth noting that, for replication scenarios, the transmission of business data can be within the same cell or on the same carrier.

[0340] The following are examples of this example:

[0341] Example 1: Network device 101 configuration: The first RLC entity is used for type 1 data transmission, the second RLC entity is used for type 2 data transmission, ...

[0342] Example 2: Network device 101 configuration: 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.

[0343] The naming of each RLC entity is for reference and distinction only, and is not intended to limit the RLC entity. For example, the first RLC entity can also be called the main RLC entity, and the second or third RLC entity can also be called the auxiliary RLC entity.

[0344] Example 2:

[0345] The transmission status of service offloading is configured through network device 101 or agreed upon through the protocol, i.e., whether the service offloading function is enabled, activated, or used.

[0346] As one embodiment of this example, if network device 101 performs the configuration of Example 1, then the service offloading function is considered enabled or activated. That is, if the higher layer performs the configuration in Example 1, then the service offloading function is considered enabled; no further activation of the function is required.

[0347] As one embodiment of this example, network device 101 specifies the initial state of whether to enable 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, the service offloading function of the second RLC entity (for type 2 data transmission) is disabled, and so on.

[0348] The following are examples of this example:

[0349] Example 1: Network device 101 configuration: First RLC entity (for type 1 data transmission), service offloading function activated; Second RLC entity (for type 2 data transmission), service offloading function activated, ...

[0350] Example 2: Network device 101 configuration: First RLC entity (for type 1 data transmission and / or control PDU), service offloading function activated; Second RLC entity (for type 2 data transmission), service offloading function activated; Third RLC entity OR (for type 3 data transmission), service offloading function deactivated; ...

[0351] The naming of each RLC entity is for reference and distinction only, not for limitation. For example, the first RLC entity can also be called the main RLC entity, the second RLC entity can also be called auxiliary RLC entity 1, and the third RLC entity can also be called auxiliary RLC entity 2.

[0352] As an embodiment of this second example, the service data associated with the RLC entity whose traffic splitting function is deactivated can be transmitted using the default RLC entity, such as the first RLC entity or the main RLC entity.

[0353] For example, in Example 2 above, Type 3 data transmission will use the main RLC entity transmission.

[0354] As one embodiment of this Example 2, the MAC CE method, DCI method, or RRC method can be used to dynamically activate (or enable / disable) the traffic offloading status or service offloading function. The RRC reconfiguration message can specify the initial state of whether the RLC entity offloading function is activated.

[0355] Example 1: MAC CE indicates the activation / deactivation of the service offloading function. The following examples illustrate the three types of RLC entities, but it is not limited to using more bits than in the examples.

[0356] Figure 6 This is a diagram illustrating how MAC CE instructs RLC entities to activate / deactivate the PDCP split function.

[0357] like Figure 6 As shown, the information field includes: a first part of bits and a second part of bits.

[0358] The first part of the bits is used to indicate the identifier (DRB ID) of the Data Radio Bearer (DRB), and is assumed to be 5 bits long. One DRB can correspond to service data of multiple service types, that is, it can correspond to multiple types of RLC entities.

[0359] The second part of the bits is used to indicate whether each type of RLC entity has activated the service offloading function. Taking three types of RLC entities as an example, the second part of the bits is 3 bits long, with each type of RLC entity occupying 1 bit (assuming one RLC entity is configured for each type). Each type of RLC is used to transmit service data for the corresponding service type. i In this context, 'i' represents the RLC entity configured for traffic offloading in the DRB. For example, it is the logical channel identifier of the secondary RLC entities in ascending order within the primary cell group (MCG) and secondary cell group (SCG), i.e., 'i' represents the RLC type or RLC entity. Figure 6 In this case, i can be 0, 1, or 2.

[0360] In RLC i When the corresponding bit value is 1, this RLC i The entity activated the business offloading function; in RLC i When the corresponding bit value is 0, this RLC i The entity deactivated the business diversion function.

[0361] As one embodiment of this second example, the network device is notified when the maximum number of retransmissions is reached on the RLC entity used for traffic offloading.

[0362] For example, when the second RLC entity reaches the maximum retransmission count, it will notify the base station, such as by sending a notification message to the base station. The base station can then take subsequent actions, such as deactivating the offloading function for that RLC entity.

[0363] It is worth noting that in the above example, the activation indication of the service offloading function can be controlled by each offloading RLC entity (PerRLC entity) (refer to the above embodiment), or it can be uniformly controlled for all offloading RLC entities. For example, the network device sends a command to activate or deactivate the offloading function of all offloading RLC entities at the same time.

[0364] Example 3:

[0365] Based on Example 1, network device 101 can activate the PDCP packet replication function for the RLC entity corresponding to a specific service.

[0366] As one embodiment of this example: the granularity of activating PDCP packet replication can be refined to the RLC entity, that is, several RLC entities (which can be referred to as: the RLC entity whose PDCP packet replication is activated, or the first RLC entity, or simply the replicated RLC entity, or the main RLC entity) can be configured for packet replication.

[0367] As one embodiment of this example: the package copying function of the RLC entity can be activated or deactivated.

[0368] Example 1: Packet copy activation and deactivation for a specific RLC entity:

[0369] Figure 7 This is a diagram illustrating how MAC CE instructs RLC entities to activate / deactivate PDCP packet duplication.

[0370] like Figure 7 As shown, the information field includes: a first part of bits and a second part of bits.

[0371] The first part of the bits is used to indicate the identifier (RLC ID) of the first RLC entity type, and it is assumed that the length of the first part of the bits is 5 bits.

[0372] The second part of the bits is used to indicate whether the second RLC entity has activated the packet replication function; assuming the second part of the bits is 3 bits long, RLC... i The 'i' in the code 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 secondary cell group (SCG). In other words, 'i' represents the index of the second RLC entity. Figure 7 In this case, i can be 0, 1, or 2.

[0373] In RLC i When the corresponding bit value is 1, this RLCi When an entity activates the packet replication function, the business data of the first RLC entity (or the replicated RLC entity) can be replicated and sent to that RLC. i Entity; in RLC i When the corresponding bit value is 0, this RLC i The entity has deactivated the package copy function.

[0374] As one embodiment of this example: the network device is notified when the maximum number of retransmissions is reached on the second RLC entity.

[0375] For example, if the second RLC entity corresponding to a certain RLC entity (the first RLC entity) reaches the maximum retransmission count, it will notify the base station, such as by sending a notification message. The base station can then take subsequent actions, such as deactivating the packet replication function of that second RLC entity.

[0376] It is worth noting that in the above examples, the packet replication function activation indication of the split RLC entity can be controlled at the granular level of each RLC split entity, or it can be controlled according to each second RLC entity corresponding to each split RLC entity (as in the above embodiments), or it can be uniformly controlled, for example:

[0377] Network device 101 can use a single control command to simultaneously copy the activation / deactivation packet of a certain RLC offloading entity, or network device 101 can use a single control command to simultaneously copy the activation / deactivation packet of all RLC offloading entities.

[0378] Based on the same concept as the above method embodiments, this disclosure also provides an apparatus for sending configuration information. This apparatus may possess the functions of the network device 101 in the above method embodiments and can be used to execute the steps performed by the network device 101 provided in the above method embodiments. This function can be implemented in hardware, or in software, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0379] In one possible implementation, such as Figure 9 The apparatus 900 shown can serve as the network device 101 involved in the above method embodiments, and perform the steps executed by the network device 101 in the above method embodiments. For example... Figure 9 As shown, the device 900 may include a transceiver module 901, wherein the transceiver module 901 can be used to support the communication device to communicate, and the transceiver module 901 may have wireless communication function, such as being able to communicate wirelessly with other communication devices through a wireless air interface.

[0380] When performing the steps implemented by network device 101, transceiver module 901 is configured to send configuration information to user equipment, the configuration information including N types of Radio Link Control (RLC) entities corresponding to Packet Data Convergence Protocol (PDCP) entities in user equipment.

[0381] When the communication device is a network device 101, its structure can also be as follows: Figure 10 As shown. The structure of a communication device is illustrated using a base station as an example. (As shown...) Figure 10 As shown, 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 its various functions. The processor 1002 is configured to support the communication device 1000 in performing the corresponding functions in the above-described methods, which can be implemented by calling the programs stored in the memory 1001. The transceiver component 1003 can be a wireless transceiver, used to support the communication device 1000 in receiving signaling and / or data, and transmitting signaling and / or data via a wireless air interface. The transceiver component 1003 can 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. The radio frequency component 1004 can be a remote radio unit (RRU), specifically used for transmitting radio frequency signals and converting radio frequency signals to baseband signals. The one or more antennas 1005 are specifically used for radiating and receiving radio frequency signals.

[0382] When the communication device 1000 needs to send data, the processor 1002 performs baseband processing on the data to be sent and outputs a baseband signal to the radio frequency (RF) unit. The RF unit then performs RF processing on the baseband signal and transmits the RF signal as electromagnetic waves through an antenna. When data is sent to the communication device 1000, 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 back into data and processes the data.

[0383] Based on the same concept as the above method embodiments, this disclosure also provides an apparatus for receiving configuration information. This apparatus may possess the functions of the user equipment 102 in the above method embodiments and can be used to execute the steps performed by the user equipment 102 provided in the above method embodiments. This function can be implemented in hardware, or in software, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above function.

[0384] In one possible implementation, such as Figure 11The device 1100 shown can serve as the user equipment 102 involved in the above method embodiments, and perform the steps executed by the user equipment 102 in the above method embodiments. For example... Figure 11 As shown, the device 1100 may include a transceiver module 1101 and a processing module 1102 coupled to each other. The transceiver module 1101 can be used to support communication between the communication device and other communication devices. The transceiver module 1101 may have wireless communication capabilities, such as the ability to communicate wirelessly with other communication devices via a wireless air interface. The processing module 1102 can be used by the communication device to perform processing operations, such as generating information / messages to be sent, or processing received signals to obtain information / messages.

[0385] When performing the steps implemented by user equipment 102, transceiver module 1101 is configured to receive configuration information sent by network device, the configuration information including N types of Radio Link Control (RLC) entities corresponding to Packet Data Convergence Protocol (PDCP) entities in user equipment.

[0386] The processing module 1102 is configured to send service data to at least one type of RLC entity according to configuration information.

[0387] When the device receiving the instruction information is user equipment 102, its structure can also be as follows: Figure 12 As shown. Device 1200 can be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0388] Reference Figure 12 The device 1200 may include one or more of the following components: a processing component 1202, a memory 1204, a power supply 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.

[0389] Processing component 1202 typically controls the overall operation of device 1200, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1202 may include one or more processors 1220 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 1202 may include one or more modules to facilitate interaction between processing component 1202 and other components. For example, processing component 1202 may include a multimedia module to facilitate interaction between multimedia component 1208 and processing component 1202.

[0390] Memory 1204 is configured to store various types of data to support the operation of device 1200. Examples of such data include instructions for any application or method operating on device 1200, contact data, phonebook data, messages, pictures, videos, etc. 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 storage, flash memory, magnetic disk, or optical disk.

[0391] Power supply component 1206 provides power to various components of device 1200. 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 to device 1200.

[0392] Multimedia component 1208 includes a screen that provides an output interface between the device 1200 and the user. In some embodiments, 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 touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 1208 includes a front-facing camera and / or a rear-facing camera. When the device 1200 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0393] Audio component 1210 is configured to output and / or input audio signals. For example, audio component 1210 includes a microphone (MIC) configured to receive external audio signals when device 1200 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1204 or transmitted via communication component 1216. In some embodiments, audio component 1210 also includes a speaker for outputting audio signals.

[0394] 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 buttons, volume buttons, power buttons, and lock buttons.

[0395] Sensor assembly 1214 includes one or more sensors for providing status assessments of various aspects of device 1200. For example, sensor assembly 1214 may detect the on / off state of device 1200, the relative positioning of components such as the display and keypad of device 1200, changes in the position of device 1200 or a component of device 1200, the presence or absence of user contact with device 1200, the orientation or acceleration / deceleration of device 1200, and temperature changes of device 1200. Sensor assembly 1214 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1214 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1214 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0396] Communication component 1216 is configured to facilitate wired or wireless communication between device 1200 and other devices. Device 1200 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 1216 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1216 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0397] In an exemplary embodiment, the apparatus 1200 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0398] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1204 including instructions, which can be executed by a processor 1220 of the device 1200 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0399] Other embodiments of the present disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the embodiments of this disclosure that follow the general principles of the embodiments of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the embodiments of this disclosure are indicated by the following claims.

[0400] It should be understood that the embodiments disclosed herein are not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from their scope. The scope of the embodiments disclosed herein is limited only by the appended claims.

[0401] Industrial applicability

[0402] In the method disclosed herein, the network device sends configuration information to the user equipment to configure the N types of RLC entities associated with the PDCP entity. This allows the user equipment to effectively offload service data based on the configuration information, thereby improving the efficiency of service data transmission.

Claims

1. A method for sending configuration information, executed by a network device, the method comprising: The configuration information is sent to the user equipment, which includes N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entities in the user equipment; where N is the number of service types of service data, and the configuration information is also used to configure each type of RLC entity to transmit service data of the corresponding service type. The configuration information includes indication identifiers corresponding to the N types of RLC entities, the indication identifiers being used to indicate whether some or all types of RLC entities have activated the first function; and / or, sending first indication information to the user equipment, the first indication information being used to indicate whether to activate or deactivate the first function of some or all types of RLC entities; The business type of the business data is determined based on at least one of the following classification dimensions: importance of business data, attributes of business data, priority level of business data, reliability level of business data, and purpose of business data.

2. The method as described in claim 1, wherein, The configuration information is also used to configure a default RLC entity, which is used to transmit the first service.

3. The method as described in any one of claims 1 to 2, wherein, Each type of RLC entity includes at least one RLC entity.

4. The method of claim 1, wherein, The first function includes business diversion or package replication.

5. The method as described in claim 1 or 4, wherein, Sending the first indication information to the user equipment includes: Send downlink control information (DCI) to the user equipment, the DCI including the first indication information; or... Send Access Control Layer Control Unit (MAC CE) signaling to the user equipment media, the MAC CE signaling including an information field for indicating the first indication information.

6. The method of claim 5, wherein, 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. When the bit is at a first value, it indicates that the first function of the RLC entity corresponding to the bit is activated.

7. The method of claim 1, wherein, The method further includes: The user equipment receives a notification message, which indicates that the number of times the RLC entity retransmits service data for the first function has reached the maximum number of retransmissions.

8. A method for receiving configuration information, executed by a user equipment, the method comprising: Receive configuration information sent by the network device, the configuration information including N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entities in the user equipment; determine whether some or all types of RLC entities activate the first function based on the indication identifier in the configuration information; and / or, Receive first indication information sent by the network device, the first indication information being used to indicate the activation or deactivation of a first function of some or all types of RLC entities; determine whether the first function of the some or all types of RLC entities is activated based on the first indication information; According to the configuration information, service data is sent to at least one type of RLC entity, where N is the number of service types of the service data, and the configuration information is also used to configure each type of RLC entity to transmit service data of the corresponding service type. The step of sending service data to at least one type of RLC entity according to the configuration information includes: Based on the configuration information and the service type of the service data, the service data is diverted and sent to the RLC entity of the type corresponding to the service type. The business type of the business data is determined based on at least one of the following classification dimensions: importance of business data, attributes of business data, priority level of business data, reliability level of business data, and purpose of business data.

9. The method of claim 8, wherein, The configuration information is also used to configure a default RLC entity, which is used to transmit the first service.

10. The method of claim 9, wherein, The step of sending service data to at least one type of RLC entity according to the configuration information includes: When the service data is the first service, the service data is sent to the default RLC entity.

11. The method of claim 9, wherein, The step of sending service data to at least one type of RLC entity according to the configuration information includes: When the RLC entity corresponding to the service data deactivates the service diversion function, the service data is diverted and sent to the default RLC entity.

12. The method of claim 9, wherein, The first function includes business diversion or package replication.

13. The method of claim 9, wherein, The receipt of the first indication information sent by the network device includes: The network device receives a MAC CE signaling message, which includes an information field for indicating the first indication information.

14. The method of claim 13, wherein, The step of determining whether the partial or all types of RLC entities have activated the first function based on the first indication information includes: When at least one bit in the information domain is a first value, the first function activation of the RLC entity corresponding to the at least one bit is determined.

15. The method of claim 9, wherein, The method further includes: When the number of times the RLC entity retransmits service data for the first function reaches the maximum number of retransmissions, a notification message is sent to the network device.

16. An apparatus for transmitting configuration information, configured in a network device, the apparatus comprising: The transceiver module is used to send configuration information to the user equipment. 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; where 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 configuration information includes indicator identifiers corresponding to the N types of RLC entities, and the indicator identifiers are used to indicate whether some or all types of RLC entities activate a first function; and / or, The device is further configured to: send a first indication message to the user equipment, the first indication message being used to indicate the activation or deactivation of a first function of some or all types of RLC entities; The business type of the business data is determined based on at least one of the following classification dimensions: importance of business data, attributes of business data, priority level of business data, reliability level of business data, and purpose of business data.

17. An apparatus for receiving configuration information, configured in a user equipment, the apparatus comprising: The transceiver module is used to receive configuration information sent by the network device, the configuration information including N types of Radio Link Control (RLC) entities corresponding to the Packet Data Convergence Protocol (PDCP) entities in the user equipment; the device is further used to: determine whether some or all types of RLC entities are activated for a first function based on the indication identifier in the configuration information; and / or, The device is further configured to: receive first indication information sent by the network device, the first indication information being used to indicate the activation or deactivation of a first function of some or all types of RLC entities; and determine, based on the first indication information, whether the first function of the some or all types of RLC entities is activated. The processing module is configured to send service data to at least one type of RLC entity according to the configuration information, wherein N is the number of service types of the service data, and the configuration information is also configured to configure each type of RLC entity to transmit service data of the corresponding service type; The device is further configured to: based on the configuration information and the service type of the service data, distribute and send the service data to an RLC entity of the type corresponding to the service type; The business type of the business data is determined based on at least one of the following classification dimensions: importance of business data, attributes of business data, priority level of business data, reliability level of business data, and purpose of business data.

18. A communication device, comprising a processor and a memory, wherein, The memory is used to store computer programs; The processor is used to execute the computer program to implement the method as described in any one of claims 1-7.

19. A communication device, comprising a processor and a memory, wherein, The memory is used to store computer programs; The processor is used to execute the computer program to implement the method as described in any one of claims 8-15.

20. A computer-readable storage medium storing instructions that, when invoked and executed on a computer, cause the computer to perform the method as described in any one of claims 1-7.

21. A computer-readable storage medium storing instructions that, when invoked and executed on a computer, cause the computer to perform the method as described in any one of claims 8-15.

Images