Information processing method and apparatus, communication device, and storage medium

Abstract

Embodiments of the present disclosure provide an information processing method and device, a communication device and a storage medium. An information processing method performed by a sending end can include: determining a radio link control (RLC) entity for sending target data according to first attribute information of the target data.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of wireless communication, and more particularly to an information processing method and apparatus, a communication device, and a storage medium. BACKGROUND

[0002] Both the access device and the user equipment (UE) are configured with a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and a physical (PHY) layer. The RLC layer is located between the PDCP layer and the MAC layer. The MAC layer is located between the RLC layer and the PHY layer.

[0003] When transmitting data, the PDCP layer forms a PDCP protocol data unit (PDU) to be transmitted; the RLC layer can be used to encapsulate the PDCP data unit into a service data unit (SDU); the MAC layer can be used to process the SDU of the RLC layer into a MAC PDU, and provide the MAC PDU to the PHY layer to convert into a transmission block (TB) for transmission.

[0004] When receiving data, the PHY layer receives the TB and submits the received TB to the MAC layer. The MAC layer converts the TB into a MAC PDU and provides it to the RLC layer, and the RLC layer assembles the MAC PDU into an SDU and submits it to the PDCP layer. The PDCP layer converts the SDU into a PDCP data unit and performs subsequent processing on the PDCP PDU. SUMMARY

[0005] The embodiments of the present disclosure provide an information processing method and apparatus, a communication device, and a storage medium.

[0006] The first aspect of the embodiments of the present disclosure provides an information processing method, which is performed by a sending end, and the method comprises:

[0007] According to first attribute information of target data to be sent, a radio link control (RLC) entity for sending the target data is determined.

[0008] The second aspect of the embodiments of the present disclosure provides an information processing method, which is performed by an access device, and the method comprises:

[0009] The first configuration information is sent to a user equipment (UE); wherein the first configuration information comprises:

[0010] identity information indicating an RLC entity sending target data;

[0011] second attribute information indicating an attribute of data that the RLC entity sending target data is capable of transmitting.

[0012] A third aspect of the embodiments of the present disclosure provides an information processing method, wherein the method is performed by a user equipment (UE), and the method comprises:

[0013] The first configuration information is received, which is sent by an access device; wherein the first configuration information comprises:

[0014] identity information indicating an RLC entity sending target data;

[0015] second attribute information indicating an attribute of data that the RLC entity sending target data is capable of transmitting.

[0016] A fourth aspect of the embodiments of the present disclosure provides an information processing apparatus, wherein the apparatus comprises:

[0017] A determining module is configured to determine, according to first attribute information of target data to be sent, an RLC entity sending the target data.

[0018] A fifth aspect of the embodiments of the present disclosure provides an information processing apparatus, wherein the apparatus comprises:

[0019] A sending module is configured to send first configuration information to a user equipment (UE); wherein the first configuration information comprises:

[0020] identity information indicating an RLC entity sending target data;

[0021] second attribute information indicating an attribute of data that the RLC entity sending target data is capable of transmitting.

[0022] A sixth aspect of the embodiments of the present disclosure provides an information processing apparatus, wherein the apparatus comprises:

[0023] A receiving module is configured to receive first configuration information sent by an access device; wherein the first configuration information comprises:

[0024] identity information indicating an RLC entity sending target data;

[0025] second attribute information indicating an attribute of data that the RLC entity sending target data is capable of transmitting.

[0026] In an embodiment seven of the present disclosure, a communication device is provided, which comprises a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being executed by the processor, wherein the processor executes the executable program to perform the information processing method according to any one of the first aspect to the third aspect.

[0027] In an embodiment eight of the present disclosure, a computer storage medium is provided, which stores an executable program; the executable program is executed by a processor to implement the information processing method according to any one of the first aspect to the third aspect.

[0028] The technical solution provided by the embodiments of the present disclosure can select the same or different RLC entities to transmit different parts of the target data according to the first attribute information of different parts of the target data, so that the part of the data with high QoS requirement can be transmitted by the RLC entity with high QoS guarantee, and the part of the data with low QoS requirement can be transmitted by the RLC entity with low QoS, thereby ensuring that the QoS requirements of different parts of the target data are better met, and reducing the congestion phenomenon caused by using the same RLC entity for data transmission.

[0029] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the embodiments of the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0030] The accompanying drawings, which are incorporated into the specification and constitute a part of the specification, illustrate the embodiments consistent with the present disclosure, and together with the specification, serve to explain the principles of the embodiments of the present disclosure.

[0031] Figure 1 is a structural schematic diagram of a wireless communication system according to an exemplary embodiment;

[0032] Figure 2A is a flowchart of an information processing method according to an exemplary embodiment;

[0033] Figure 2B is a flowchart of an information processing method according to an exemplary embodiment;

[0034] Figure 2C is a flowchart of an information processing method according to an exemplary embodiment;

[0035] Figure 2D is a flowchart of an information processing method according to an exemplary embodiment;

[0036] Figure 2E is a flowchart of an information processing method according to an exemplary embodiment;

[0037] Figure 2F This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0038] Figure 2G This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0039] Figure 2H This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0040] Figure 3A This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0041] Figure 3B This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0042] Figure 3C This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0043] Figure 4A This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0044] Figure 4B This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0045] Figure 4C This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0046] Figure 5 This is a schematic diagram of the structure of an information processing apparatus according to an exemplary embodiment;

[0047] Figure 6 This is a schematic diagram of the structure of an information processing apparatus according to an exemplary embodiment;

[0048] Figure 7 This is a schematic diagram of the structure of an information processing apparatus according to an exemplary embodiment;

[0049] Figure 8 This is a schematic diagram of the structure of a UE according to an exemplary embodiment;

[0050] Figure 9 This is a schematic diagram of the structure of a network device according to an exemplary embodiment. Detailed Implementation

[0051] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The following description is made with reference to the accompanying drawings in which like reference numerals refer to like elements, unless the context clearly shows otherwise. The following description of exemplary embodiments is not representative of all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure.

[0052] The terminology used in the present disclosure is solely for the purpose of describing particular embodiments and is not intended to limit the present disclosure. As used in the present disclosure, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms

[0053] It will be understood that, although the terms first, second, third, etc. can be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one piece of information from another. For example, a first information can also be termed a second information, and, similarly, a second information can also be termed a first information, without departing from the scope of the present disclosure. Depending on the context, the word "if" as used herein can be interpreted as meaning "when" or "if, when, or in response to determining."

[0054] Reference is made to Figure 1 , which shows a structure diagram of a wireless communication system provided by the embodiments of the present disclosure. As shown in Figure 1 , the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system can include a plurality of UEs 11 and a plurality of access devices 12. In some embodiments, the communication system can further include one or more core network devices, which are not shown in Figure 1 . The core network device includes, but is not limited to, a mobile management entity (MME) or an access management function (AMF), etc.

[0055] The UE 11 can be a device that provides voice and / or data connectivity to a user. The UE 11 can communicate with one or more core networks (CNs) via a Radio Access Network (RAN), and the UE 11 can be an Internet of Things (IoT) UE, such as a sensor device, a mobile phone (also known as a cellular telephone), and a computer with an IoT UE, e.g., which can be fixed, portable, pocketable, hand-held, computer-embedded, or in-vehicle. For example, a Station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or a user equipment (UE). Alternatively, the UE 11 can also be a device of an unmanned aerial vehicle. Alternatively, the UE 11 can also be a vehicle-mounted device, e.g., a car-mounted computer with wireless communication function, or a wireless communication device externally connected to the car-mounted computer. Alternatively, the UE 11 can also be a roadside device, e.g., a street lamp, a signal lamp, or other roadside devices with wireless communication function, etc.

[0056] The access device 12 can be a network-side device in a wireless communication system. The wireless communication system can be a 4th generation mobile communication (4G) system, also known as a Long Term Evolution (LTE) system, or the wireless communication system can also be a 5G system, also known as a new radio (NR) system or a 5G NR system. Alternatively, the wireless communication system can also be a next generation system of the 5G system. In the 5G system, the access network can be referred to as a New Generation-Radio Access Network (NG-RAN). Alternatively, the MTC system.

[0057] The access device 12 can be an evolved NodeB (eNB) used in a 4G system. Alternatively, the access device 12 can also be a base station (gNB) using a centralized and distributed architecture in a 5G system. When the access device 12 uses a centralized and distributed architecture, it usually includes a central unit (CU) and at least two distributed units (DUs). The central unit is provided with a protocol stack of a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer; and the distributed unit is provided with a physical (PHY) layer protocol stack. The specific implementation of the access device 12 is not limited in the embodiments of the present disclosure.

[0058] The access device 12 and the UE 11 can establish a wireless connection through a wireless air interface. In different embodiments, the wireless air interface is a wireless air interface based on a fourth generation mobile communication network technology (4G) standard; or the wireless air interface is a wireless air interface based on a fifth generation mobile communication network technology (5G) standard, such as a new radio (NR); or the wireless air interface can also be a wireless air interface based on a more next generation mobile communication network technology standard of 5G.

[0059] In the related art, one PDCP entity in the PDCP layer can be associated with one or more RLC entities in the RLC layer.

[0060] The PDCP entity can have a split function, and the PDCP can distribute different PDUs to different RLC entities to distribute data when implementing the split function. For example, there are a primary RLC entity and a secondary RLC entity in the plurality of RLC entities. For example, the PDU carrying control data is distributed to the primary RLC entity. The PDU of the service data can be distributed to the primary RLC entity, and part of it is distributed to the secondary RLC entity. Specifically, when the total data amount of one or more PDUs of the service data is small, the PDCP entity can distribute more PDUs to the primary RLC entity for processing, and when the total data amount of one or more PDUs of the service data is large, the PDCP entity can distribute part of the PDUs to the primary RLC entity and part of the PDUs to the secondary RLC entity, which are distributed by the primary RLC entity and the secondary RLC entity.

[0061] The PDCP layer also has a duplication function. For example, in order to ensure the reliability of data transmission, each PDU is duplicated one or more times and distributed to different RLC entities for subsequent processing.

[0062] As Figure 2AAs shown, the embodiment of the disclosure provides an information processing method, wherein the method is executed by a sending end, and the method comprises the following steps.

[0063] S1110: determining an RLC entity for transmitting the target data according to first attribute information of the target data.

[0064] The execution subject of the information processing method can be a target data sending end. Exemplarily, the target data sending end can be Figure 1 an access device as shown, or Figure 1 a UE as shown. Figure 1 The access device as shown can include various types of base stations, such as eNB and / or gNB.

[0065] Exemplarily, the UE can be any terminal with mobile communication capability. The UE can be a mobile terminal and / or a fixed terminal. The terminal can be, but is not limited to, a mobile phone, a wearable device, a vehicle-mounted terminal, a road side unit (RSU), a smart home terminal, a smart office device, an industrial sensing device, and / or a medical device, etc.

[0066] The execution subject of the information processing method can be a PDCP entity of the UE.

[0067] Exemplarily, the target data can be one or more PDCP data units formed by a PDCP entity of a PDCP layer. The PDCP data unit can carry control data and / or service data. The PDCP data unit is carried on a radio bearer.

[0068] The PDCP data unit can include a PDCP PDU and / or a PDCP SDU. In some cases, the PDCP data unit processed by the PDCP entity can be a PDCP PDU and / or a PDCP SDU received by the PDCP layer.

[0069] Each PDCP PDU can include a header and a payload part. The header can carry first attribute information. The payload part can include control data and / or service data.

[0070] The first attribute information can be any data attribute indicating the importance of the payload part of the PDU.

[0071] Exemplarily, the first attribute information can be an importance level or a priority level indicating the importance of the payload part data of the PDCP data unit. Of course, this is only an example of the first attribute information, and the specific implementation is not limited to this example.

[0072] Different kinds of RLC entities have different QoS guarantees. Exemplarily, different kinds of RLC entities have different transmission modes, some of which support error correction function, some of which support repetition detection function, and some of which can only support transparent function.

[0073] Exemplarily, different kinds of RLC entities can be mapped to different logical channels or logical channel groups. Different logical channels or different logical channel groups have different QoS guarantees.

[0074] In one embodiment, different kinds of RLC entities can correspond to one MAC entity of the sending end MAC layer. It is worth noting that the MAC entity can encapsulate data packets from different RLC entities into MAC PDUs or MAC sub-PDUs carrying logical channel or logical channel group IDs mapped by different RLC entities.

[0075] If two PDU headers of the target data carry different importance levels, they can be distributed to different kinds of RLC entities for processing. Different kinds of RLC entities can provide different QoS guarantees for data transmission. According to the first attribute information of different PDCP data units of the target data, an RLC entity that can provide corresponding QoS guarantee is selected for data transmission, which is equivalent to selecting an RLC entity that matches the importance level of the PDU reflected by the first attribute information of each PDCP data unit in the UE for data transmission.

[0076] The data transmission of the RLC entity here can include assembling one or more PDCP data units with small data volume into one SDU, or splitting a PDU with large data volume into multiple SDUs, and performing related processing of the RLC layer such as transparent, re-encapsulation, repetition detection and / or error correction of the data according to the transmission mode of the RLC entity.

[0077] In some embodiments, the target data can be control data or service data. When the target data is control data, one or more RLC entities that can provide the required QoS of the first attribute information can be selected to transmit different parts of the control data according to different first attribute information of the control data.

[0078] In other embodiments, the target data can be service data. At this time, different parts of the target data can come from different QoS flows of the same service, or different QoS sub-flows of the same QoS flow; or data from different modalities of the same service.

[0079] Exemplarily, the video data can include I frames and P frames. Generally, the I frames can be independently coded; and the P frames need to be jointly decoded depending on the I frames or other P frames. Therefore, in order to realize successful transmission and reception of the video data, the importance of the I frames is obviously higher than that of the P frames. Thus, the importance indicated by the first attribute information in the PDU header carrying the I frames can be higher than the importance indicated by the second attribute information in the PDU header carrying the P frames. At this time, the QoS requirement of the I frames is higher than the QoS requirement of the P frames.

[0080] Exemplarily, the data of the extended reality (XR) service can include display data of a display device, voice data of a voice device, and / or sensor data such as touch sensor data, and the like. The display data, the voice data, and the sensor data belong to different modal data. The XR service can include an augmented reality (AR) service, a virtual reality (VR) service, and / or a mixed reality (MR) service. The MR service can simultaneously have the characteristics of the AR service and the VR service. Generally, different parts of the XR service data can have different QoS requirements. For example, the biometric data collected by the sensor in the XR service can be used for identity verification and / or payment verification of a user, and can have a higher QoS requirement than the voice data of the voice device.

[0081] Exemplarily, in some embodiments, the method can further include determining whether the data to be transmitted is target data of a specified service. Exemplarily, it is determined whether the data to be transmitted is service data of a specified service or service type, and if so, the data to be transmitted is the target data. The transmission of the target data needs to select a corresponding RLC entity to transmit the target data according to the first attribute information of the target data. The specified service includes but is not limited to the aforementioned XR service and / or video service.

[0082] In the embodiments of the present disclosure, different parts of the target data can be transmitted by the same or different RLC entities according to the first attribute information of the different parts of the target data. In this way, the part of the data with a high QoS requirement can be transmitted by the RLC entity with a high QoS guarantee, and the part of the data with a low QoS requirement can be transmitted by the RLC entity with a low QoS, so that the QoS requirements of different parts of the target data are better met, and the congestion phenomenon caused by using the same RLC entity to transmit the data is reduced.

[0083] In some embodiments, the UE and the access device as the sending end both acquire the first configuration information, which can be used for configuration of the RLC entity of the RLC layer of the sending end.

[0084] Exemplarily, the first configuration information can be used for the transmitting end to determine the RLC layer of the transmitting end to configure one or more RLC entities. If multiple RLC entities are configured, the first attribute information corresponding to each RLC entity can be configured or not.

[0085] The SDUs formed by different RLC entities can be mapped to different logical channels or different logical channel groups. Thus, after the MAC entity of the MAC layer receives the SDUs of different RLC entities, the MAC entity can generate a MAC PDU. One MAC PDU can include one or more MAC sub-PDUs. One MAC sub-PDU can include a subheader. The subheader can carry the logical channel identifier (LCID) or the logical channel group identifier (LCG ID) of the logical channel to which the MAC sub-PDU is mapped. The SDUs of different RLC entities can be encapsulated into different MAC sub-PDUs, thereby being mapped to different LCs and achieving QoS guarantee for data transmission of different RLC entities based on the QoS guarantee of the LCs.

[0086] In some embodiments, the first configuration information includes: identification information indicating an RLC entity to which target data is to be transmitted; and second attribute information indicating an attribute of data that the RLC entity to which the target data is to be transmitted is capable of transmitting.

[0087] Exemplarily, the first configuration information can be a list of RLC entities. The list can include identification information of the RLC entities, for example, the identification information can include a number of the RLC entities. Meanwhile, the list can also include the second attribute information in the same row as the identification information of each RLC entity.

[0088] Exemplarily, one identification information can be used to identify an RLC entity established by the RLC layer of the UE. The RLC entity indicated by the identification information can be an already established RLC entity and / or an RLC entity to be established.

[0089] The second attribute information can indicate a level of importance and / or a priority and / or any information such as a service type that characterizes the QoS requirement of the RLC entity intended (or expected) to transmit data. Exemplarily, the second attribute information can also be any information such as a level of importance and / or a priority and / or a service type.

[0090] Exemplarily, the first configuration information can include one or more fields. One field can be used to configure one RLC entity of the RLC layer of the UE. For example, different parts of one field can carry identification information of an RLC entity to be established and second attribute information.

[0091] Further exemplarily, one RLC entity can be associated to multiple second properties. Different parts of the target data can have different second properties. Namely, one RLC entity can be used to transmit target data of multiple different properties at the same time.

[0092] The first configuration information can be for RLC configuration of one kind of control data or one kind of service data. The RLC entity to be established can include one or more RLC entities, and different RLC entities can provide higher QoS guarantee. Exemplarily, the RLC entity can include a primary RLC entity and a secondary RLC entity, and the primary RLC entity can provide higher QoS guarantee than the secondary QoS entity.

[0093] In addition, the first configuration information can also be used in combination with the protocol agreement mode. For example, two RLC entities are configured, which are a first RLC entity (or referred to as a primary RLC entity) and a second RLC entity (or referred to as a secondary RLC entity), respectively used to transmit target data with importance level 1 and importance level 2. At the same time, according to the protocol agreement mode, the first RLC entity can also be used to carry control data generated by the PDCP layer itself, such as a PDCP control PDU.

[0094] The first configuration information further includes:

[0095] Mode information indicating a transmission mode of the RLC entity transmitting the target data.

[0096] The transmission mode includes a transparent mode (TM), an unacknowledged mode (UM), and / or an acknowledged mode (AM).

[0097] The transparent mode can be a transmission mode without converting a PDU into an SDU, without adding an RLC header, and without performing data discard, rearrangement, recombination, and error correction processing.

[0098] The unacknowledged mode can be a transmission mode of converting a PDU into an SDU, adding an RLC header to the SDU, and performing data discard, rearrangement, and / or recombination processing.

[0099] The acknowledged mode can be a transmission mode of converting a PDU into an SDU, adding an RLC header to the SDU, and performing data discard, rearrangement, recombination, and / or error correction processing.

[0100] The transmission modes of different RLC entities can be different. For example, an RLC entity using AM can provide higher QoS guarantee for data transmission than an RLC entity using UM. And an RLC entity using UM can provide higher QoS guarantee for data transmission than an RLC entity using TM.

[0101] In some embodiments, the first configuration information comprises one or more of:

[0102] importance level;

[0103] service type;

[0104] quality of service (QoS) flow identifier;

[0105] sub-QoS flow identifier;

[0106] priority.

[0107] In some embodiments, the first attribute information can also comprise control data generated by the PDCP layer itself. The control data can also be referred to as control signaling.

[0108] The first attribute information can be obtained in several ways. One way is to obtain it from the header of the PDCP data unit. For example, the header of each PDCP data unit can carry its own first attribute information. For example, the header of the PDCP data unit can include the importance level.

[0109] Another way is to determine the first attribute information from the transmission address of the DCP data unit. For example, for downlink transmission, the access device can associate different transmission layer addresses to different QoS flows. Then, the QoS flow ID or sub-QoS flow ID to which the PDCP data unit belongs can be obtained according to the transmission layer address.

[0110] Similarly,

[0111] When the second attribute information includes the importance level, the QoS flow ID, or the sub-QoS flow ID, the RLC entity with the second attribute information will send the PDCP data unit with the second attribute information. The service type can be represented by the type identifier information or the service identifier. The PDCP entity of the PDCP layer can send the PDCP data unit to the corresponding RLC entity according to the service type and / or service ID of the PDCP data unit to be sent to the RLC entity.

[0112] The QoS flow identifier can include, for example, the quality of service flow identifier (QoS Flow Identifier, QFI) of the 5th Generation (5G) mobile communication. Different QFI maps a set of different QoS parameters. The QoS parameters can include parameters related to transmission delay, transmission bandwidth, and / or transmission error rate.

[0113] One QoS flow can be split into different sub-QoS flows, so that different sub-QoS flows can have different sub-QoS identities. Similarly, the sub-QoS identity will be mapped with one or more QoS parameters. Thus, similarly, the sub-QoS flow can also be used by the PDCP layer of the sending end to determine the RLC entity to which the currently to-be-sent PDCP data unit is sent.

[0114] The priority can be the service priority of the data, and / or the priority of the logical channel of the transmitted data. The priority also reflects the importance and / or QoS requirement of the data.

[0115] As shown in Figure 2B The present embodiment provides an information processing method, wherein the method is performed by a UE, and the method comprises:

[0116] S1210: receiving first configuration information sent by an access device; wherein the first configuration information comprises: identification information indicating an RLC entity to which target data is sent; and second attribute information indicating an attribute of data that can be transmitted by the RLC entity to which the target data is sent.

[0117] The access device can be any access device as shown in Figure 1 , i.e., the access device can be an eNB or a gNB.

[0118] Exemplarily, the first configuration information can be a list of RLC entities. The list can include identification information of the RLC entities, for example, the identification information can include the number of the RLC entities. Meanwhile, the list can also include the second attribute information in the same row as the identification information of each RLC entity.

[0119] Exemplarily, if the execution subject of the information processing method is a UE, the UE will receive the first configuration information from the access device.

[0120] After receiving the second configuration information, the UE can establish the corresponding RLC entity before starting the transmission of the target data, thereby facilitating the subsequent transmission of the target data.

[0121] As shown in Figure 2C The present embodiment provides an information processing method, wherein the method is performed by a sending end, and the method comprises:

[0122] S1310: obtaining first configuration information; wherein the first configuration information comprises: identification information indicating an RLC entity to which target data is sent; and second attribute information indicating an attribute of data that can be transmitted by the RLC entity to which the target data is sent.

[0123] S1320: according to the first attribute information of the target data, selecting an RLC entity corresponding to the second attribute information matching the first attribute information to send the target data.

[0124] Thus, by the acquisition of the first configuration information, the PDCP entity of the sending end PDCP layer can acquire the second attribute information of each RLC entity in the UE in advance, and then select the RLC entity receiving each PDCP data unit according to the matching of the first attribute information and the second attribute information in the PDCP data unit assembled by itself. The first attribute information can be carried in the header of the PDCP data unit.

[0125] In some embodiments, the first configuration information can be semi-statically configured or dynamically configured. If semi-statically configured, the RRC message can be used for semi-static periodic configuration. If dynamically configured, the MAC CE method can be used for activation, deactivation, enabling or disabling configuration. Generally, the change frequency of semi-static configuration is lower than that of dynamic configuration.

[0126] As shown in FIG. 13, the embodiment of the present disclosure provides an information processing method, which is executed by a sending end, and the method comprises: Figure 2D

[0127] S1410: acquiring preset information; wherein the preset information is used to update the RLC entity of the sending target data.

[0128] The sending end can also be a UE or an access device.

[0129] Exemplarily, the preset information can be any information of the shunt configuration change of the target data. That is, the preset information can be any data of the access device updating the RLC entity of the sending target data.

[0130] Exemplarily, the preset information can include shunt configuration information.

[0131] The shunt configuration information can be used to reconfigure the sending mode of the target data and / or update the sending RLC entity during shunt sending. For the target data, the reconfigured sending mode can include shunt sending and non-shunt sending.

[0132] Exemplarily, the shunt configuration information can be used to indicate that the sending mode of the target data is switched between shunt sending and non-shunt sending. If non-shunt sending, all target data is sent by one RLC entity. If shunt sending, different parts of the target data will be sent by different RLC entities due to the difference of the respective first attribute information. Therefore, it is obvious that the sending mode of the target data is switched between shunt sending and non-shunt sending, which is equivalent to updating the RLC entity of the sending target data.

[0133] Exemplarily, the shunt configuration information can also be used to indicate the update of the sending RLC entity of the target data during shunt sending. Exemplarily, the shunt configuration information can also be used to indicate the update of the sending RLC entity of the target data during shunt sending.

[0134] Exemplarily, the preset information can be reestablishment information, release information and / or deactivation information of the established RLC entity. The reestablishment information can indicate that the established RLC entity needs to be destroyed and reestablished, during the process of destroying and reestablishing, the RLC entity obviously cannot be used for sending the target data, which is equivalent to updating the RLC entity for sending the target data. The release information can be used for releasing the RLC entity, and the released RLC entity no longer needs to be reestablished.

[0135] The state of the RLC entity can include an activated state or a non-activated state of the RLC entity. The activated state can also be referred to as an activated state, and the RLC entity in the activated state can be referred to as an activated RLC entity. The non-activated state can also be referred to as an inactivated state or a deactivated state or a standby activated state. The RLC entity in the non-activated state can be referred to as an inactivated RLC entity, a standby activated RLC entity or a deactivated RLC entity.

[0136] Exemplarily, the deactivation information is to replace an RLC entity in the activated state into the deactivated state. The RLC entity in the deactivated state will suspend the transmission of the target data, thereby achieving the updating of the RLC entity for sending the target data.

[0137] Exemplarily, the preset information can be establishment information, or configuration information, or activation information of the to-be-established RLC entity.

[0138] The establishment information can be used for establishing the RLC entity, for example, the first configuration information has completed the configuration of the RLC entity, but the establishment of the RLC entity has not been completed according to the first configuration information, and the establishment of the RLC entity will be implemented after the establishment information is received.

[0139] The configuration information can be that the RLC entity to be used for transmitting the target data has not been configured.

[0140] The activation information can be used for state switching of the established RLC entity from the deactivated state to the activated state.

[0141] The preset information can be configured by an RRC message, a MAC layer message or downlink control information (DCI).

[0142] For example, the RLC entity currently used for transmitting the target data can include one or more second RLC entities, and through the acquisition of the preset information, the RLC entity for transmitting the target data can be updated to the one or more second RLC entities.

[0143] In some embodiments, the access device can update the sending RLC entity of the target data according to the change of the QoS requirement of the target data, and / or the upgrade of the service data, so that the RLC entity sending the target data is dynamically adapted to the QoS requirement of different parts of the target data.

[0144] As shown in Figure 2E The embodiments of the present disclosure provide an information processing method, which is executed by a sending end, and the method comprises:

[0145] S1510: obtaining second configuration information, wherein the second configuration information is used to reconfigure the RLC entity sending the target data.

[0146] For example, if the sending end is a UE, the second configuration information can be received from the access device. If the sending end is an access device, the second configuration information sent to the UE can be obtained from the cache of the sending end.

[0147] The second configuration information can be carried in any RRC message, MAC layer message and / or DCI sent by the access device.

[0148] For example, the second configuration information can be configured by an RRC reconfiguration message, an RRC reestablishment message or an RRC resume message.

[0149] For example, the second configuration information can be used to implement at least one of the following functions:

[0150] Stopping or starting the split function of the target data; if the split function is started, the target data is sent by using at least two RLCs;

[0151] Increasing the sending RLC entity of the target data;

[0152] Reducing the sending RLC entity of the target data;

[0153] Replacing the sending RLC entity of the target data;

[0154] Updating the second attribute information of the sending RLC entity of the target data;

[0155] Updating the transmission mode of the sending RLC entity of the target data;

[0156] Updating the logical channel or logical channel group mapped by the sending RLC entity of the target data.

[0157] In some embodiments, the second configuration information can also include a list of RLC entities. The list can include at least the identification information of the second RLC entity, and / or the second attribute information corresponding to each second RLC entity, and / or the mode information of the second RLC entity, and / or the identification information of the logical channel or logical channel group corresponding to the second RLC entity.

[0158] The second attribute information can indicate the importance level and / or priority and / or service type and / or any information characterizing the QoS requirement of the second RLC entity intended (or expected) to transmit data. Exemplarily, the second attribute information can also be any information of the importance level and / or priority and / or service type and / or the like.

[0159] Exemplarily, the second configuration information can include one or more fields. One field can be used to configure one RLC entity of the RLC layer of the UE. For example, different parts of one field can carry the identification information and the second attribute information of the RLC entity to be established.

[0160] The second configuration information further includes mode information indicating the transmission mode of the second RLC entity. The transmission mode of the second RLC entity can be AM, UM or TM.

[0161] As shown in Figure 2F The embodiments of the present disclosure provide an information processing method, which is executed by a sending end, and the method comprises:

[0162] S1610: Obtain activation information, the activation information being used to update the RLC entity of the sending target data by activating the unactivated RLC entity and / or deactivating the activated RLC entity.

[0163] In this implementation scenario, the first configuration information configures the RLC entity, but the RLC entity can not be activated or can be activated. The access device can subsequently instruct the UE or itself to switch the state of each RLC entity in the RLC layer through the activation information. The state of the RLC entity can include the activation state or the non-activation state of the RLC entity. The activation state can also be referred to as the activated state, and the RLC entity in the activated state can be referred to as the activated RLC entity. The non-activation state can also be referred to as the unactivated state or the deactivated state or the to-be-activated state. The RLC entity in the non-activation state can be referred to as the unactivated RLC entity, the to-be-activated RLC entity or the deactivated RLC entity.

[0164] The activation information can include an activation instruction and / or a deactivation instruction. The activation instruction can be used to activate one or more to-be-activated RLC entities, and the deactivation instruction can be used to deactivate one or more activated RLC entities.

[0165] Only the RLC entity in the activated state can be used for data transmission. Thus, the target data transmitting RLC entity can be dynamically updated by the activation information. In this case, the first configuration information can be a dynamically configured RRC message, and one or more RLC entities for transmitting the target data can be dynamically configured. Both the UE and the access device, when acting as the transmitting end, establish the RLC entity after obtaining the first configuration information, and update the state of the established RLC entity after receiving the activation information.

[0166] In some embodiments, the first configuration information can further include indication information for setting the initial state of each configured RLC entity. The initial state of the target data for transmission can be the activated state or the deactivated state. For example, when the first configuration information configures multiple RLC entities, the initial state of the primary RLC entity among the multiple RLC entities can be the activated state, and the initial state of the other secondary RLC entities can be the deactivated state.

[0167] As shown in FIG. 1, the embodiments of the present disclosure provide an information processing method, which is performed by a transmitting end, and the method includes: Figure 2G

[0168] S1710: in response to the target data transmitting RLC entity being changed from a first RLC entity to a second RLC entity;

[0169] S1720: performing a preset function of the target data.

[0170] The first RLC entity and the second RLC entity are different RLC entities. Here, the first RLC entity can be considered as the source RLC entity of the target data transmission, and the second RLC entity can be considered as the target RLC entity of the target data transmission.

[0171] Exemplarily, the transmitting end can determine that the target data transmitting RLC entity is updated from the first RLC entity to the second RLC entity according to any one of the aforementioned preset information.

[0172] Exemplarily, the transmitting end can also determine that the target data transmitting RLC entity is updated from the first RLC entity to the second RLC entity according to a predefined rule.

[0173] Exemplarily, the transmitting end can also determine that the target data transmitting RLC entity is updated from the first RLC entity to the second RLC entity according to a predefined rule. The transmission mode of the RLC entity before the change and the transmission mode of the RLC entity after the change can be the same or different. As an embodiment, according to the protocol agreement, only the change between different RLC entities using the same transmission mode is supported for the target data, so as to simplify the operation.

[0174] ​The predefined rule can include a protocol agreement. For example, the predefined rule implementation defines a trigger condition of the sending RLC entity update of the target data of one or more kinds of target data, and if the trigger condition is met, it is determined that the sending RLC entity of the target data is updated from the first RLC entity to the second RLC entity.

[0175] Since the target data is sent by the switching RLC entity, there can be a sending gap of the target data, and a QoS update of the target data between the first RLC entity and the second RLC entity.

[0176] The preset function can be a data reliability ensuring function, and / or a data latency ensuring function.

[0177] The data reliability ensuring function is mainly used to ensure the transmission reliability of the data.

[0178] The data latency ensuring function is mainly used to ensure that the transmission latency of the data is within the tolerable latency range, and to reduce data timeout.

[0179] For example, if the QoS guarantee of the second RLC entity relative to the first RLC entity is improved, it means that the target data needs higher QoS guarantee, at which time, the data reliability ensuring function related to data reliability may need to be performed. If the QoS guarantee of the second RLC entity relative to the first RLC entity is reduced, more attention is paid to the transmission latency of the data, and the data latency ensuring function related to data latency may need to be performed.

[0180] In summary, through the execution of the preset function, the QoS after the update of the sending RLC entity of the target data can be met, and the QoS guarantee in the sending RLC entity update process can be realized.

[0181] For example, the second RLC entity includes:

[0182] An established RLC entity in the sending end;

[0183] And / or,

[0184] A to-be-established RLC entity in the sending end.

[0185] In some embodiments, the execution of the preset function of the target data by the second RLC entity includes:

[0186] Performing a preset operation related to the transmission mode of the second RLC entity; or,

[0187] Starting a PDCP data recovery function.

[0188] The preset operation can be related to the transmission mode of the updated second RLC entity. The transmission mode of the second RLC entity reflects the updated QoS requirement of the target data sending RLC, and therefore the preset operation according to the transmission mode of the second RLC entity can at least meet the updated QoS requirement of the target data sending RLC.

[0189] The related operation of the PDCP data recovery function can refer to the related art, and the QoS guarantee in the updating process of the target data sending RLC can be realized through the PDCP data recovery function.

[0190] The preset operation related to the transmission mode of the second RLC entity includes:

[0191] In response to the transmission mode of the second RLC entity being AM, it is determined to send the first PDCP data unit and the second PDCP data unit to the second RLC entity;

[0192] Or,

[0193] In response to the transmission mode of the second RLC entity being TM or UM, it is determined to send the second PDCP data unit to the second RLC entity;

[0194] The first PDCP data unit includes a PDCP data unit that has been sent to the first RLC entity and for which no feedback data has been received, and the second PDCP data unit includes a PDCP data unit that has not been sent to the first RLC entity.

[0195] If the transmission mode of the updated second RLC entity is AM, it means that the target data has a very high QoS requirement, and the data transmission interruption or data packet loss caused by the RLC entity update will cause the data to be unable to be decoded or the transmission to fail. Therefore, in this case, the first PDCP data unit sent by the sending end, as long as no feedback data from the receiving end has been received, can be sent again through the second RLC entity for the purpose of ensuring data reliability. The feedback data can include ACK indicating successful reception and / or NACK indicating reception failure. The PDCP layer of the receiving end sends the feedback data to the PHY layer of the sending end, and then transmits it to the PDCP layer through the MAC layer and the RLC layer. The second PDCP data unit is target data that has not been sent by the first RLC, and therefore can continue to be sent by the second RLC to ensure that the receiving end receives complete target data.

[0196] If the transmission mode of the second RLC entity is UM or TM, especially TM, it indicates that the current reliability requirement for the target data is low, and a higher transmission rate can be required. At this time, the second PDCP data unit can be directly transmitted by default using the second RLC entity, and at least the transmission of the first PDCP data unit is not performed when the preset function is executed. UM provides lower QoS guarantee in data reliability than AM. In order to reduce unnecessary data packet transmission, in the case where the transmission mode of the second RLC entity is UM, the first PDCP data unit can also not be transmitted first, and the second PDCP data unit is preferentially transmitted.

[0197] In some embodiments, the preset operation of the transmission mode of the second RLC entity is performed, including:

[0198] Triggering the receiving end to send a PDCP status report;

[0199] According to the PDCP status report, it is determined whether to send part or all of the first PDCP data unit to the second RLC entity or whether to delete the sent first PDCP data unit.

[0200] The PDCP status report indicates the PDCP data unit that the receiving end has successfully received, and / or the PDCP data unit that the receiving end fails to receive.

[0201] Exemplarily, triggering the receiving end to send a PDCP status report can include: if the transmission mode of the second RLC entity is AM, triggering the receiving end to send a PDCP status report. In this way, the PDCP entity of the sending end can send the data that needs to be continuously sent to the receiving end to the receiving end via the second RLC entity or delete the PDCP data unit that is successfully sent according to the PDCP status report of the receiving end.

[0202] In some embodiments, starting the PDCP data recovery function includes:

[0203] After starting the PDCP data recovery function, the first PDCP data unit and the second PDCP data unit are sent to the second RLC entity; wherein the first PDCP data unit includes: the PDCP data unit that has been sent to the first RLC entity and has not received feedback data; and the second PDCP data unit includes: the PDCP data unit that has not been sent to the first RLC entity.

[0204] In the embodiments of the present disclosure, the PDCP data recovery function is started if the sending RLC entity of the target data is updated. In this case, no matter the transmission mode of the second RLC entity after the update, the first PDCP data unit and the second PDCP data unit that have been sent but no feedback data is received are provided to the second RLC entity, and then sent to the receiving end after being processed by the second RLC entity.

[0205] The feedback data includes but is not limited to ACK and / or NACK.

[0206] In this way, the reliability of data sending during the replacement (i.e. update) of the RLC entity of the target data can be ensured by using the PDCP data recovery function.

[0207] As shown in FIG. 1, the embodiments of the present disclosure provide an information processing method, which is performed by a sending end, and the method comprises: Figure 2H

[0208] S1810: In response to the sending RLC entity of the target data being replaced from the first RLC entity to the second RLC entity;

[0209] S1820: In response to the second RLC entity being a to-be-established RLC entity, the second RLC entity is established.

[0210] In the embodiments of the present disclosure, the sending end is replaced to the second RLC entity based on preset information or predefined rules. If it is detected that the sending end has not established the second RLC entity, the second RLC entity needs to be established first. For example, the second RLC entity is established according to the first configuration information, the second configuration information or the predefined rules. After the establishment of the second RLC entity is completed, the second RLC entity is established before the preset function is executed, or before the use of the first RLC entity is deleted, released or re-established.

[0211] It is worth noting that when it is determined that the sending RLC entity of the target data is replaced from the first RLC entity to the second RLC entity, the use of the first RLC entity for sending data can be paused, or the use of the first RLC entity for sending data can be continued until the second RLC entity is established and can replace the first RLC entity for sending data.

[0212] ​Exemplarily, if the reliability of the second RLC entity is higher than the reliability of the first RLC entity, the data transmission of the first RLC entity can be suspended before the second RLC entity is completed to be established, so as to better guarantee the transmission reliability of the target data, when the sending RLC of the target data is determined to be replaced by the second RLC entity. Here, the reliability of the second RLC entity being higher than the reliability of the first RLC entity is embodied in one or more of the following aspects: the transmission mode of the first RLC entity is TM, and the transmission mode of the second RLC entity is AM or UM; or, the transmission mode of the first RLC entity is UM, and the transmission mode of the second RLC entity is AM; or, the bandwidth corresponding to the logical channel mapped by the first RLC entity is less than the bandwidth corresponding to the logical channel mapped by the second RLC entity, and the like.

[0213] Exemplarily, if the reliability of the second RLC entity is lower than the reliability of the first RLC entity, the data transmission of the first RLC entity can be continued before the second RLC entity is completed to be established, so as to ensure the transmission delay of the data.

[0214] In some embodiments, the method further includes releasing or reestablishing or deactivating the first RLC entity. If the first RLC entity is released, the RLC layer of the sending end will delete the first RLC entity. If the second RLC entity is reestablished, a new first RLC entity can be reestablished according to new configuration information. The transmission mode and / or the mapped logical channel of the newly established first RLC entity can be different from those of the original first RLC entity, but the identification information of the reestablished first RLC entity can remain unchanged. Of course, this is only an example, and the specific implementation is not limited to this example.

[0215] If the first RLC entity is only deactivated, it means that the first RLC entity enters a deactivated (or disabled) state in which no data is sent. Subsequently, the first RLC entity can be activated again to send data.

[0216] As shown in Figure 3A The present disclosure provides an information processing method, which is performed by an access device, and includes:

[0217] S2110: sending first configuration information to the UE; wherein the first configuration information includes: identification information indicating an RLC entity sending target data; and second attribute information indicating an attribute of data that can be transmitted by the RLC entity sending the target data.

[0218] The execution device of the information processing method can be an access device. The access device can be an access device as shown in Figure 1 The access device can specifically include an eNB and / or a gNB.

[0219] When the UE is a transmitter, the access device generates the first configuration information in advance and sends the first configuration information to the UE. For example, the access device sends the first configuration information to the UE through an RRC message. Specifically, the access device sends the first configuration information to the UE through an RRC message used in the process of switching the UE from a non-connected state to a connected state. Specifically, the access device sends the first configuration information to the UE through an RRC message used in the process of switching or reselecting the UE from another cell to the current cell.

[0220] For example, the access device sends the first configuration information to the UE through an RRC connection establishment message, an RRC connection recovery message, or a random access response message.

[0221] In some embodiments, the first configuration information can be semi-static configuration information or dynamic configuration information.

[0222] For example, the first configuration information can be a list of RLC entities. The list can include identification information of the RLC entities, for example, the identification information can include a number of the RLC entities. Meanwhile, the list can also include second attribute information in the same row as the identification information of each RLC entity.

[0223] For example, one identification information can be used to identify an RLC entity established by the RLC layer of the UE. The RLC entity indicated by the identification information can be an already established RLC entity and / or an RLC entity to be established.

[0224] The second attribute information can indicate a level of importance and / or a priority and / or any information such as a service type representing QoS requirements of the RLC entity intended (or expected) to transmit data. For example, the second attribute information can also be any information such as a level of importance and / or a priority and / or a service type.

[0225] For example, one field can be used to configure one RLC entity of the RLC layer of the UE. For example, different parts of one field can carry identification information and second attribute information of an RLC entity to be established.

[0226] The first configuration information can be for RLC configuration of one type of control data or one type of service data. The RLC entity to be established can include one or more types of RLC entities, and different types of RLC entities can provide higher QoS guarantees. For example, the RLC entities can include a primary RLC entity and a secondary RLC entity, and the primary RLC entity can provide higher QoS guarantees than the secondary QoS entity.

[0227] The first configuration information further includes:

[0228] Mode information indicating a transmission mode of the RLC entity for transmitting target data.

[0229] The transmission mode includes a transparent mode (TM), an unacknowledged mode (UM), and / or an acknowledged mode (AM).

[0230] The transparent mode can be a transmission mode without converting a PDU into an SDU, without adding an RLC header, and without performing data discard, rearrangement, recombination, error correction, and the like.

[0231] The unacknowledged mode can be a transmission mode of converting a PDU into an SDU, adding an RLC header to the SDU, and performing data discard, rearrangement, and / or recombination, and the like.

[0232] The acknowledged mode can be a transmission mode of converting a PDU into an SDU, adding an RLC header to the SDU, and performing data discard, rearrangement, recombination, and / or error correction, and the like.

[0233] The transmission modes of different RLC entities can be different. For example, an RLC entity using the AM can provide higher QoS guarantee for data transmission than an RLC entity using the UM. An RLC entity using the UM can provide higher QoS guarantee for data transmission than an RLC entity using the TM.

[0234] In some embodiments, the first configuration information includes one or more of the following:

[0235] Importance level;

[0236] Service type;

[0237] Quality of service (QoS) flow identifier;

[0238] Sub-QoS flow identifier;

[0239] Priority.

[0240] As shown in FIG. 1, the embodiments of the present disclosure provide an information processing method, wherein the method is performed by an access device, and the method includes: Figure 3B S2210: sending first configuration information to the UE; wherein the first configuration information includes: identification information indicating an RLC entity of target data; and second attribute information indicating an attribute of data that can be transmitted by the RLC entity of the target data.

[0241] S2220: sending second configuration information, wherein the second configuration information is used to reconfigure the RLC entity of the target data.

[0242]

[0243] ​The sending the second configuration information can include sending the second configuration information to the UE, for example, broadcasting, group-casting or unicast the second configuration information to the UE.

[0244] The second configuration information can be used to implement at least one of the following functions, for example:

[0245] stopping or starting the offloading function of the target data; if the offloading function is started, using at least two RLCs to send the target data;

[0246] adding a sending RLC entity of the target data;

[0247] reducing a sending RLC entity of the target data;

[0248] replacing a sending RLC entity of the target data;

[0249] updating the second attribute information of the sending RLC entity of the target data;

[0250] updating the transmission mode of the sending RLC entity of the target data;

[0251] updating the logical channel or logical channel group mapped by the sending RLC entity of the target data.

[0252] In some embodiments, the second configuration information can also be any data sent by the access device to reconfigure the sending RLC entity of the target data. The second configuration information can be configured by an RRC reconfiguration message, an RRC reestablishment message or an RRC resume message.

[0253] The first configuration information and the second configuration information can both be semi-static configuration information and / or dynamic configuration information, for example.

[0254] In some embodiments, the second configuration information can also include a list of RLC entities. The list can include at least the identification information of the second RLC entity; and / or the second attribute information corresponding to each second RLC entity, and / or the mode information of the second RLC entity, and / or the identification information of the logical channel or logical channel group corresponding to the second RLC entity.

[0255] The second attribute information can indicate the importance level and / or priority and / or any information such as service type representing the QoS requirement of the second RLC entity intended (or expected) to transmit data. The second attribute information can also be any information such as the importance level and / or priority and / or service type, for example.

[0256] As another example, the second configuration information may include one or more fields. A field can be used to configure an RLC entity in the RLC layer of the UE. For example, different parts of a field may carry identification information and second attribute information of the RLC entity to be established.

[0257] The second configuration information also includes: mode information, indicating the transmission mode of the second RLC entity. The transmission mode of the second RLC entity can be AM, UM, or TM.

[0258] In this embodiment of the disclosure, a second configuration information can be obtained by configuring a second RLC based on the QoS requirements updated by the target data.

[0259] like Figure 3C As shown in the embodiments of this disclosure, an information processing method is provided, wherein the method is executed by an access device, and the method includes:

[0260] S2310: Send first configuration information to the UE; wherein the first configuration information includes: identification information, indicating the RLC entity that sends the target data; and second attribute information, indicating the attributes of the data that the RLC entity that sends the target data can transmit.

[0261] S2320: Send activation information, which is used to update the RLC entity sending the target data by activating an inactive RLC entity and / or deactivating an activated RLC entity.

[0262] This activation information may be carried by a MAC layer message or a DCI. For example, the MAC layer message may include, but is not limited to, a MAC CE.

[0263] For example, the first configuration information can perform initial configuration or update configuration on the RLC entity that sends the target data. In this case, the first configuration information completes the configuration of the RLC entity, and the activation of the configured RLC entity can be achieved by activation information. In specific implementation, the initial activation of the RLC entity configured by the first configuration information can also be completed by the first configuration information, or the default initial state is an active state or an inactive state.

[0264] For example, activation information can be used for state switching of an established RLC entity from a deactivated state to an activated state.

[0265] The activation information may include: activation instructions and / or deactivation instructions. Activation instructions can be used to activate one or more RLC entities to be activated, and deactivation instructions can be used to deactivate one or more activated RLC entities.

[0266] For example, sending activation information includes sending a MAC CE carrying activation information.

[0267] In some embodiments, the activation information comprises:

[0268] an activation indication for activating at least one inactivated RLC entity configured by the first configuration information;

[0269] and / or,

[0270] a deactivation indication for deactivating at least one activated RLC entity configured by the first configuration information.

[0271] In some embodiments, the access device configures the UE with an RLC entity for sending target data by the UE in uplink, and the access device, as a sending end of downlink transmission, can send the target data to the UE according to the first configuration information and one of the second configuration information and the activation information.

[0272] As shown in Figure 4A The present disclosure provides an information processing method, which is performed by a user equipment (UE), and the method comprises:

[0273] S3110: receiving first configuration information sent by an access device; wherein the first configuration information comprises: identification information indicating an RLC entity for sending target data; and second attribute information indicating an attribute of data that can be transmitted by the RLC entity for sending target data.

[0274] The information processing method can be performed by a UE. The UE can be various types of communication devices, specifically a device as shown in Figure 1 The access device can be any device in a radio access network (RAN).

[0275] When the UE is a sending end, the access device can pre-generate the first configuration information and send the first configuration information to the UE. For example, the access device can send the first configuration information to the UE through a radio resource control (RRC) message. Specifically, the access device can send the first configuration information to the UE through an RRC message used in a process of switching the UE from an unconnected state to a connected state. Specifically, the access device can send the first configuration information to the UE through an RRC message used in a process of switching or reselecting the UE from another cell to a current cell.

[0276] For example, the access device can send the first configuration information to the UE through an RRC connection setup message, an RRC connection resume message, or a random access response message.

[0277]

[0278] In some embodiments, the first configuration information can be semi-static configuration information or dynamic configuration information.

[0279] ​Exemplarily, the first configuration information can be a list of RLC entities. The list can comprise identification information of the RLC entities. For example, the identification information can comprise a number of the RLC entities. Meanwhile, the list can further comprise second attribute information in the same row as the identification information of each RLC entity.

[0280] Exemplarily, one identification information can be used to identify an RLC entity established by the RLC layer of the UE. The RLC entity indicated by the identification information can be an already established RLC entity and / or an RLC entity to be established.

[0281] The second attribute information can indicate a level of importance and / or a priority and / or any information such as a type of service, which characterizes the QoS requirement, of the data intended (or expected) to be transmitted by the RLC entity. Exemplarily, the second attribute information can also be any information such as a level of importance and / or a priority and / or a type of service.

[0282] Exemplarily, the first configuration information can comprise one or more fields. One field can be used to configure one RLC entity of the RLC layer of the UE. For example, different parts of one field can carry the identification information and the second attribute information of the RLC entity to be established.

[0283] The first configuration information can be for RLC configuration of one kind of control data or one kind of service data. The RLC entity to be established can comprise one or more RLC entities, and different kinds of RLC entities can provide higher QoS guarantee. Exemplarily, the RLC entities can comprise a primary RLC entity and a secondary RLC entity, and the primary RLC entity can provide higher QoS guarantee than the secondary QoS entity.

[0284] The first configuration information further comprises:

[0285] Mode information indicating a transmission mode of the RLC entity for transmitting the target data.

[0286] The transmission mode can comprise a transparent mode (TM), an unacknowledged mode (UM) and / or an acknowledged mode (AM).

[0287] The transparent mode can be a transmission mode without converting a PDU into a SDU, without adding an RLC header, and without performing data discard, rearrangement, reassembly and error correction processing.

[0288] The unacknowledged mode can be a transmission mode of converting a PDU into a SDU, adding an RLC header on the SDU, and performing data discard, rearrangement and / or reassembly processing.

[0289] The confirmation mode can be a transmission mode in which a PDU is converted into an SDU, an RLC header is added to the SDU, and the data is processed by discarding, rearranging, recombining, or correcting errors.

[0290] The transmission modes of different RLC entities can be different. For example, an RLC entity using AM can provide a higher QoS guarantee for data transmission than an RLC entity using UM. An RLC entity using UM can provide a higher QoS guarantee for data transmission than an RLC entity using TM.

[0291] In some embodiments, the first configuration information includes one or more of the following:

[0292] Importance level;

[0293] Service type;

[0294] Quality of service (QoS) flow identifier;

[0295] Sub-QoS flow identifier;

[0296] Priority.

[0297] As shown in FIG. 1, the embodiments of the present disclosure provide an information processing method, which is performed by a user equipment (UE), and the method includes: Figure 4B

[0298] S3210: receiving first configuration information sent by an access device; wherein the first configuration information includes: identification information indicating an RLC entity for sending target data; and second attribute information indicating an attribute of data that can be transmitted by the RLC entity for sending the target data.

[0299] S3220: receiving second configuration information, wherein the second configuration information is used to reconfigure the RLC entity for sending the target data.

[0300] The first configuration information can be initial configuration information used to initially configure the RLC entity for sending the target data. In some cases, the QoS requirement of the target data does not change or changes slightly, and the RLC entity for sending the target data does not need to be updated before the target data stops being transmitted, so the UE does not receive the second configuration information sent by the access device.

[0301] If the QoS requirement changes during the transmission of the target data, the second configuration information sent by the access device can be received.

[0302] Exemplarily, the second configuration information can be used to implement at least one of the following functions:

[0303] Stopping or starting a split function of the target data; if the split function is started, the target data is sent using at least two RLCs; ​

[0304] a transmitting RLC entity of target data is increased;

[0305] a transmitting RLC entity of target data is decreased;

[0306] a transmitting RLC entity of target data is replaced;

[0307] a second attribute information of a transmitting RLC entity of target data is updated;

[0308] a transmission mode of a transmitting RLC entity of target data is updated;

[0309] a logical channel or a logical channel group mapped by a transmitting RLC entity of target data is updated.

[0310] In some embodiments, the second configuration information can also be any data sent by the access device to reconfigure the transmitting RLC entity of target data. The second configuration information can be configured by an RRC reconfiguration message, an RRC reestablishment message or an RRC resume message.

[0311] Exemplarily, the first configuration information and the second configuration information can both be semi-static configuration information and / or dynamic configuration information.

[0312] In some embodiments, the second configuration information can also include a list of RLC entities. The list can include at least: identification information of a second RLC entity; and / or second attribute information corresponding to each second RLC entity, and / or mode information of the second RLC entity, and / or identification information of a logical channel or a logical channel group corresponding to the second RLC entity.

[0313] The second attribute information can indicate a level of importance and / or a priority and / or any information such as a service type representing QoS requirements of the second RLC entity intended (or expected) to transmit data. Exemplarily, the second attribute information can also be any information such as a level of importance and / or a priority and / or a service type.

[0314] Exemplarily, the second configuration information can include one or more fields. One field can be used to configure one RLC entity of the RLC layer of the UE. For example, different parts of one field can carry identification information and second attribute information of the RLC entity to be established.

[0315] The second configuration information further includes mode information indicating a transmission mode of the second RLC entity. The transmission mode of the second RLC entity can be AM, UM or TM.

[0316] In the embodiments of the present disclosure, the second RLC entity can be configured to obtain the second configuration information according to the updated QoS requirement of the target data.

[0317] AsFigure 4C As shown, the embodiment of the present disclosure provides an information processing method, wherein the method is performed by a user equipment (UE), and the method comprises:

[0318] S3310: receiving first configuration information sent by an access device; wherein the first configuration information comprises: identification information indicating an RLC entity for sending target data; and second attribute information indicating an attribute of data that can be transmitted by the RLC entity for sending target data.

[0319] S3320: receiving activation information for updating the RLC entity for sending target data by activating an inactivated RLC entity and / or deactivating an activated RLC entity.

[0320] The activation information can be carried by a MAC layer message or DCI. Illustratively, the MAC layer message can include, but is not limited to, a MAC CE.

[0321] Illustratively, the first configuration information can perform initial configuration or update configuration on the RLC entity for sending target data. In this case, the first configuration information completes the configuration of the RLC entity, and the activation of the configured RLC entity can be realized by the activation information. In a specific implementation process, the initial activation of the RLC entity configured by the first configuration information can also be completed by the first configuration information, or the default initial state is an activated state or an inactivated state.

[0322] Illustratively, the activation information can be used for state switching of an established RLC entity from a deactivated state to an activated state.

[0323] The activation information can include an activation indication and / or a deactivation indication. The activation indication can be used to activate one or more RLC entities to be activated, and the deactivation indication can be used to deactivate one or more activated RLC entities.

[0324] The embodiment provides an information processing method related to the function of splitting according to data attributes of the PDCP layer, which can include:

[0325] In a specific service splitting scenario, a network configures a PDCP entity to correspond to N RLC entities; wherein N corresponds to service type classification. The specific service can include, but is not limited to, an XR service. N is any positive integer. Different RLC entities provide different QoS guarantees.

[0326] As an embodiment, the PDCP layer specifies its transmission RLC entities for different service types, such as, configuring a list (first field) for RLC entities transmission for each of the two service types. Namely, the list type can be configured with different or same types of RLC entities for different service types. In addition, the control data of the PDCP layer, such as the PDCP PDU carrying control data, will be transmitted from the agreed or access device specified RLC entity.

[0327] In some embodiments, it is assumed that the first RLC entity is used for type 1 data transmission, and the second RLC entity is used for type 2 data transmission.

[0328] The classification dimension of the service type can include one or more of the following:

[0329] The importance of the data, the service type, the Qos flow ID or sub Qos flow ID, the priority level, and the like.

[0330] As an embodiment, the RLC entities associated with the same PDCP entity can be of the same RLC transmission mode or different RLC transmission modes. Here, the RLC transmission mode can be the transmission mode of the RLC entity.

[0331] As an embodiment, for a radio bearer (Radio Bearer, RB), its PDCP layer is configured or enabled differently for the split function and the PDCP duplication function according to the attributes. Here, the attributes include but are not limited to the service attributes and / or data attributes of the target data. The service attributes can be embodied by the service identifier, the service type, and / or the QoS parameters of the service. The data attributes can be embodied by the data type, and / or the dependency or relationship between different data. As an embodiment, the first field and the second field (MoreThanTwoRLC-DRB) are not configured at the same time. Here, the first field is used to configure the split function of the PDCP based on the attributes; the second field is used to configure the PDCP duplication function.

[0332] In some embodiments, the PDCP split function and the PDCP duplication function according to the service attributes can be enabled at the same time. When the split function is enabled, PDCP data units of different importance levels or different service attributes can be sent through different types of RLC entities. Exemplarily, for data of high importance level, it can be sent based on the duplication function in different RLC entities, while for unimportant data, it is not necessary to send it in multiple RLC entities.

[0333] As an embodiment, for a radio bearer (RB), the PDCP layer is configured with the split function according to the traffic property and the split function according to the traffic volume size at different time, or is not configured with the split function according to the traffic property and the split function according to the traffic volume size at different time.

[0334] As an embodiment, the first field and the third field (MoreThanOneRLC) are not configured at the same time. The third field is used to configure the split function of the PDCP layer according to the traffic volume (or data volume). If the third field configures the split function of the PDCP layer based on the data volume, the PDCP layer uses different RLC entities to transmit data when the data volume reaches a threshold value.

[0335] In some embodiments, the split function of the PDCP according to the property and the split function of the PDCP layer according to the traffic volume size can be started at the same time. That is, for data in a certain scenario, the data can be split according to the property, and at the same time, the data can be split according to the size of the data volume. For example, the split data can be based on the master cell group (MCG) and the secondary cell group (SCG). The master cell group includes at least a master cell. In some scenarios, the master cell group will also include one or more other cells in addition to the master cell. The secondary cell includes one or more secondary cells. The logical channels mapped by different RLC entities can belong to the same cell group or different cell groups. For example, the logical channel mapped by the primary RLC entity can belong to the master cell group, and the logical channel mapped by the secondary RLC entity can belong to the secondary cell group.

[0336] In some embodiments, for a type of service data, two RLC entities are configured respectively, which are a first RLC entity and a second RLC entity, and the first RLC entity can be used for type 1 data transmission and the second RLC entity can be used for type 2 data transmission. The transmission mode of the first RLC entity and the second RLC entity is configured as UM or AM. Exemplarily, the transmission mode of the first RLC entity is configured as UM, and the transmission mode of the second RLC entity can be configured as AM.

[0337] Example 2: For a type of service data, two RLC entities are configured respectively, which are a first RLC entity and a second RLC entity, and the first RLC entity can be used for type 1 data transmission and the second RLC entity can be used for type 2 data transmission. The transmission mode of the first RLC entity and the second RLC entity is configured as TM, UM or AM.

[0338] In some embodiments, the network device configures or changes the configuration of the service split by using the RRC message.

[0339] As an embodiment; the transmission channel of the specific data type is switched from the first RLC entity to the second RLC entity. The specific data can include but not limited to the service data of the aforementioned specified services. At this time, the second RLC entity can be an old RLC entity that has been established or a new RLC entity that needs to be re-established.

[0340] As an embodiment; the change of service split also includes switching from split transmission to non-split transmission according to the transmission mode of the data. For example, by disabling or deactivating the configuration information of split transmission, the transmission mode of the data is switched from split transmission to non-split transmission. That is, back to the original transmission mode without splitting according to the service type. For example, by enabling or activating the configuration information of split transmission, the transmission mode of the data is switched from non-split transmission to split transmission. That is, back to the original transmission mode without splitting according to the service type.

[0341] As an embodiment; when the service split configuration is changed, the preset function of data processing is accompanied.

[0342] When the preset function is executed, an example of the behavior of the UE can be as follows:

[0343] If the transmission mode used by the DRB or the RLC entity of the current data to be transmitted is AM, from the data units transmitted on the original RLC entity and not yet received a successful transmission confirmation, starting from the first data unit not yet received a successful transmission confirmation, retransmit on the new target RLC entity or transmit in sequence on the new target RLC entity the data units that have associated serial numbers (SNs) but have not yet been transmitted on the original RLC entity.

[0344] Illustratively, the PDCP layer transmits a PDCP data unit to the RLC layer, and the counter performs counting once. The counting value (COUNT Value) can be used as the aforementioned SN. That is, the PDCP entity has transmitted a PDCP data unit to the RLC entity, and the PDCP data unit has associated SNs. In this way, the sending end can retransmit on the new target RLC entity or transmit in sequence on the new target RLC entity the PDCP data units that have been transmitted on the original RLC entity but have not yet received a successful transmission confirmation or retransmit the data units that have associated SNs but have not yet been transmitted on the original RLC entity.

[0345] When the preset function is executed, another example of the behavior of the UE can be as follows:

[0346] If the transmission mode used by the DRB or RLC entity of the current data to be transmitted is UM, for all PDCP SDUs that have been processed by PDCP but have not been submitted to the lower layer, the PDCP SDUs that have not been transmitted are transmitted to the target RLC entity in ascending order of the sequence number (SN) of the PDCP SDU corresponding to the count value of the counter. The data is continued to be transmitted by the target RLC entity.

[0347] As an embodiment; when the service split configuration is changed, the execution of the preset function of data processing is accompanied.

[0348] The process can be a PDCP data recovery process. For example, due to the change of the service split configuration, at least one RLC entity can not be able to continue transmission, at this time, the PDCP entity can retransmit through the available RLC entity after the change according to the feedback data of the RLC entity transmitting data and the PDCP data unit that has not received an acknowledgement character (ACK), to ensure the reliability of the data.

[0349] Another example of the behavior of the UE when executing the preset function can be as follows:

[0350] For data with a transmission mode of AM, when the upper layer requests the PDCP layer to recover the data of the radio bearer, the PDCP entity will retransmit the PDCP data unit that has been sent before and has not received an indication of successful data delivery.

[0351] The upper layer here includes but is not limited to: Service Data Adaptation Protocol (SDAP).

[0352] The above PDCP data unit can be a PDCP data PDU or a PDCP SDU. The PDCP data PDU can be referred to as PDCP PDU.

[0353] Further: the access device can carry the indication of the terminal performing the preset function in the RRC message of changing the service split configuration at the same time, for example, the access device sends an indication message indicating the terminal to perform a PDCP data recovery process.

[0354] In some embodiments, the transmitting RLC entity of the data is switched from the first RLC entity to the newly established second RLC entity for transmission, and the first RLC entity will be re-established or released or cannot continue to transmit the originally split data, then the foregoing preset function can be realized through one or more of the following operations:

[0355] Start the PDCP data recovery function;

[0356] establishing a second RLC entity;

[0357] the MAC entity associated with the first RLC entity will be reconfigured,

[0358] the MAC entity associated with the second RLC entity will be established or reconfigured,

[0359] if the first RLC entity and the second RLC entity share one MAC entity, the MAC entity will be reconfigured.

[0360] In some embodiments, the sending RLC entity switches from the first RLC entity to the second RLC entity, and the first RLC entity will be re-established or released or cannot continue to transmit the originally split data, and the foregoing preset functions can be implemented by one or more of the following operations.

[0361] The execution of the preset functions can include at least one of the following operations:

[0362] PDCP data recovery;

[0363] the MAC entity associated with the first RLC entity will be reconfigured;

[0364] the MAC entity associated with the second RLC entity will have no action, i.e., no subsequent operation will be performed;

[0365] if the first RLC entity and the second RLC entity share one MAC entity, the MAC entity will be reconfigured.

[0366] In some embodiments, the RRC message configures the first RLC entity for type 1 data transmission and the second RLC entity for type 2 data transmission. After a period of time, the access device reconfigures the first RLC entity by a new RRC message to be used for type 1 data transmission and type 2 data transmission, i.e., the original second RLC entity is deleted, at which time the PDCP data recovery operation needs to be performed. The purpose is to retransmit the data originally transmitted on the second RLC entity and not confirmed to be received by the receiving end.

[0367] In some embodiments, the access device will trigger the receiving end to report the PDCP status report when changing the service split configuration. If the access device configures the receiving end to report the PDCP status report, the sending end can receive the PDCP status report sent by the opposite end device (i.e., the receiving end), and perform the data transmission reliability related operation according to the PDCP status report.

[0368] In addition to configuring or changing the configuration of service offloading using RRC messages on access devices, the MACCE method can be used to more dynamically activate or deactivate the offloading status.

[0369] As one embodiment, the access device first configures service offloading using RRC messages. While configuring the RLC entity, it can also specify the initial state of the offloading RLC entity. That is, the initial state can include either an active state or a deactivated state. The active state can also be called an enabled state. The deactivated state can also be called a disabled state.

[0370] When a specific RLC entity's service is deactivated by using MAC CE, the RLC entity is not rebuilt, and the MAC layer's HARQ buffer will not be cleared. At this point, the deactivated data packets will be discarded based on the received PDCP instruction. For example, the RLC entity discards the deactivated data packets.

[0371] Data packets that fail to be transmitted to the MAC address need to be discarded, but data packets that have already been delivered to the MAC address cannot be deleted, so the HARQ buffer is not cleared.

[0372] The above-mentioned preset functions can also be used when dynamically activating or deactivating traffic splitting via MAC CE. Because the deactivated RLC entity can no longer transmit specific types of data, it is necessary to continue transmitting unacknowledged or delayed data packets on a new RLC entity.

[0373] like Figure 5 As shown, this disclosure provides an information processing apparatus, wherein the apparatus includes:

[0374] The determination module 110 is configured to determine the Radio Link Control (RLC) entity for transmitting target data based on the first attribute information of the target data to be transmitted.

[0375] The information processing device may be a transmitter. The transmitter may be a UE or an access device.

[0376] In some embodiments, the information processing apparatus may further include a storage module. This storage module is connected to the determination module 110 and is used to store any information required during the execution of the Radio Link Control (RLC) entity for transmitting target data, based on first attribute information of the target data to be transmitted.

[0377] In some embodiments, the determining module 110 may be a program module, which, after being executed by the processor, can perform the above operations.

[0378] In some embodiments, the determining module 110 can be a hardware module; the hardware module includes but is not limited to a central processing unit (CPU) and / or a microprocessor.

[0379] In some other embodiments, the determining module 110 can be a hardware module; the hardware module includes but is not limited to an application-specific integrated circuit (ASIC).

[0380] In some embodiments, the apparatus further includes:

[0381] The obtaining module is configured to obtain first configuration information before determining the RLC entity that transmits the target data.

[0382] The first configuration information includes:

[0383] The identification information indicates the RLC entity that transmits the target data.

[0384] The second attribute information indicates an attribute of data that the RLC entity that transmits the target data is capable of transmitting.

[0385] In some embodiments, the determining module 110 is configured to select, according to the first attribute information of the target data, the RLC entity corresponding to the second attribute information that matches the first attribute information to transmit the target data.

[0386] It can be understood that the first configuration information further includes:

[0387] The mode information indicates a transmission mode of the RLC entity that transmits the target data.

[0388] The transmission mode includes a transparent mode (TM), an unacknowledged mode (UM) and / or an acknowledged mode (AM).

[0389] It can be understood that the first configuration information includes one or more of the following:

[0390] An importance level;

[0391] A service type;

[0392] A quality of service (QoS) flow identifier;

[0393] A sub-QoS flow identifier;

[0394] A priority.

[0395] It can be understood that the method further includes:

[0396] Obtaining preset information; the preset information is used to update the RLC entity that transmits the target data.

[0397] It can be understood that the preset information includes at least one of the following:

[0398] second configuration information, wherein the second configuration information is used to reconfigure the RLC entity sending the target data;

[0399] activation information, used to update the RLC entity sending the target data by activating the inactivated RLC entity and / or deactivating the activated RLC entity.

[0400] It can be understood that the apparatus further comprises:

[0401] a replacement module configured to replace the sending RLC entity of the target data from the first RLC entity to the second RLC entity in response;

[0402] an execution module configured to execute a preset function of the target data.

[0403] It can be understood that the second RLC entity comprises:

[0404] an established RLC entity;

[0405] and / or,

[0406] a to-be-established RLC entity.

[0407] It can be understood that the execution module is configured to execute a preset operation of a transmission mode of the second RLC entity; or, start a PDCP data recovery function.

[0408] It can be understood that the execution of the preset operation of the transmission mode of the second RLC entity comprises:

[0409] in response to the transmission mode of the second RLC entity being AM, determining to send a first PDCP data unit and a second PDCP data unit to the second RLC entity;

[0410] or,

[0411] in response to the transmission mode of the second RLC entity being TM or UM, determining to send the second PDCP data unit to the second RLC entity;

[0412] wherein the first PDCP data unit comprises a PDCP data unit that has been sent to the first RLC entity and has not yet received feedback data; and the second PDCP data unit comprises a PDCP data unit that has not yet been sent to the first RLC entity.

[0413] It can be understood that the start of the PDCP data recovery function comprises:

[0414] After starting the PDCP data recovery function, the first PDCP data unit and the second PDCP data unit are sent to the second RLC entity; wherein the first PDCP data unit includes: a PDCP data unit that has been sent to the first RLC entity and for which no feedback data has been received; and the second PDCP data unit includes: a PDCP data unit that has not been sent to the first RLC entity.

[0415] It can be understood that the apparatus further includes:

[0416] The establishing module is configured to establish the second RLC entity in response to the second RLC entity being a to-be-established RLC entity.

[0417] As shown in Figure 6 The present disclosure provides an information processing apparatus, wherein the apparatus includes:

[0418] The sending module 210 is configured to send first configuration information to a user equipment (UE); wherein the first configuration information includes:

[0419] The identification information indicates an RLC entity that sends target data;

[0420] The second attribute information indicates an attribute of data that the RLC entity that sends the target data is capable of transmitting.

[0421] The information processing apparatus can be an access device.

[0422] In some embodiments, the sending module 210 can be a program module, which, after being executed by a processor, can implement the above operations.

[0423] In other embodiments, the sending module 210 can be a soft and hard combined module; the soft and hard combined module can include: a programmable array. The programmable array includes but is not limited to a field programmable array and / or a complex programmable array.

[0424] In still other embodiments, the sending module 210 can be a pure hardware module; the pure hardware module includes but is not limited to an application specific integrated circuit.

[0425] It can be understood that the first configuration information further includes:

[0426] The mode information indicates a transmission mode of the RLC entity that sends the target data;

[0427] The transmission mode includes: a transparent mode (TM), an unacknowledged mode (UM), and / or an acknowledged mode (AM).

[0428] It can be understood that the first configuration information includes one or more of the following:

[0429] An importance level;

[0430] Business type;

[0431] Quality of Service (QoS) flow identifier;

[0432] Sub-QoS flow identifier;

[0433] Priority.

[0434] In some embodiments, the sending module 210 is further configured to send second configuration information, wherein the second configuration information is used to reconfigure the RLC entity for sending target data.

[0435] In some embodiments, the sending module 210 is further configured to send activation information, which is used to update the RLC entity for sending target data by activating inactive RLC entities and / or deactivating activated RLC entities.

[0436] In some embodiments, the sending module 210 sends a Media Access Control (MAC) control unit CE carrying activation information.

[0437] Understandably, activation information includes:

[0438] An activation instruction is used to activate at least one inactive RLC entity configured by the first configuration information;

[0439] And / or,

[0440] A deactivation instruction is used to deactivate at least one activated RLC entity configured by the first configuration information.

[0441] like Figure 7 As shown, this disclosure provides an information processing apparatus, wherein the apparatus includes:

[0442] The receiving module 310 is configured to receive first configuration information sent by the access device; wherein the first configuration information includes:

[0443] Identification information, indicating the RLC entity sending the target data;

[0444] The second attribute information indicates the attributes of the data that the RLC entity sending the target data is capable of transmitting.

[0445] The information processing device can be a UE.

[0446] In some embodiments, the receiving module 310 may be a program module, which, after being executed by the processor, can perform the above operations.

[0447] In some embodiments, the receiving module 310 can be a software module; the software module can include, but is not limited to, a browser, an applet, and / or an application.

[0448] In some embodiments, the receiving module 310 can be a hardware module; the hardware module can include, but is not limited to, a processor, a microprocessor, a microcomputer, a microcontrol unit, a programmable logic unit, and / or a field programmable gate array.

[0449] It can be understood that the first configuration information further includes:

[0450] mode information, indicating a transmission mode of the RLC entity that transmits the target data;

[0451] The transmission mode includes: a transparent mode TM, an unacknowledged mode UM, and / or an acknowledged mode AM.

[0452] In some embodiments, the first configuration information includes one or more of the following:

[0453] an importance level;

[0454] a service type;

[0455] a quality of service QoS flow identifier;

[0456] a sub-QoS flow identifier;

[0457] a priority.

[0458] In some embodiments, the receiving module 310 is further configured to receive second configuration information, wherein the second configuration information is used to reconfigure the RLC entity that transmits the target data.

[0459] In some embodiments, the receiving module 310 is further configured to receive activation information, which is used to update the RLC entity that transmits the target data by activating an inactivated RLC entity and / or deactivating an activated RLC entity.

[0460] The embodiments of the present disclosure provide a communication device, which includes:

[0461] a memory for storing processor-executable instructions;

[0462] a processor connected with the memory respectively;

[0463] The processor is configured to execute the information processing method provided in any of the foregoing technical solutions. The communication device can include the UE and / or the access device described above.

[0464] The processor can include various types of storage media, which is a non-transitory computer storage medium and can continue to store information thereon after the communication device is powered off.

[0465] The processor can connect to memory via a bus or similar means to read executable programs stored in memory, for example... Figures 2A to 2H , Figures 3A to 3C or Figures 4A to 4B At least one of the methods shown.

[0466] Figure 8 This is a block diagram illustrating a UE 800 according to an exemplary embodiment. For example, the UE 800 may be a mobile phone, computer, digital broadcast user equipment, messaging transceiver, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0467] Reference Figure 8 The UE 800 may include one or more of the following components: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input / output (I / O) interface 812, sensor component 814, and communication component 816.

[0468] Processing component 802 typically controls the overall operation of UE 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to generate all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0469] Memory 804 is configured to store various types of data to support operation on UE 800. Examples of this data include instructions for any application or method operating on UE 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 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.

[0470] Power supply component 806 provides power to various components of UE 800. Power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to UE 800.

[0471] The multimedia component 808 includes a screen providing an output interface between the UE 800 and a user. In some embodiments, the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense a touch, slide, and gesture on the touch panel. The touch sensor can not only sense a boundary of a touching or sliding action, but also detect duration and pressure related to the touching or sliding action. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the UE 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front and rear camera can be a fixed optical lens system or have a focal length and optical zooming capability.

[0472] The audio component 810 is configured to output and / or input an audio signal. For example, the audio component 810 includes a microphone (MIC) configured to receive an external audio signal when the UE 800 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting an audio signal.

[0473] The I / O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which can be a keypad, a click wheel, buttons, and the like. The buttons can include, but are not limited to, a home button, a volume button, a start button, and a lock button.

[0474] The sensor component 814 includes one or more sensors to provide various state assessments for the UE 800. For example, the sensor component 814 can detect an open / closed state of the UE 800, relative positioning of components, such as a display and a keypad of the UE 800, a change in position of the UE 800 or a component of the UE 800, presence or absence of user contact with the UE 800, a change in orientation or acceleration / deceleration of the UE 800, and a temperature change of the UE 800. The sensor component 814 can include a proximity sensor configured to detect presence of an object within a proximity of the UE 800 without any physical touch. The sensor component 814 can also include a light sensor, such as a CMOS or CCD image sensor, for use in an imaging application. In some embodiments, the sensor component 814 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0475] The communication component 816 is configured to facilitate wired or wireless communication between the UE 800 and other devices. The UE 800 can access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) techniques, Infrared Data Association (IrDA) techniques, Ultra-WideBand (UWB) techniques, Bluetooth (BT) techniques, and other techniques.

[0476] In an exemplary embodiment, the UE 800 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, or other electronic elements, for performing the above-described methods.

[0477] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions, such as the memory 804 including instructions, is also provided, which can be executed by the processor 820 of the UE 800 to generate the above-described methods. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disc, and an optical data storage device, etc.

[0478] As shown in Figure 9 , an embodiment of the present disclosure shows a structure of a network device. Referring to Figure 9 , the network device 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932, for storing instructions, such as an application program, executable by the processing component 922. The application program stored in the memory 932 can include one or more than one module each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute the instructions to perform any method of the aforementioned application in the access device, such as at least one of the methods shown in Figures 2A to 2H 、 Figures 3A to 3C or Figures 4A to 4B .

[0479] The network device 900 can also include a power supply component 1926 configured to perform power management for the network device 900, a wired or wireless network interface 950 configured to connect the network device 900 to a network, and an input / output (I / O) interface 958. The network device 900 can operate on an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0480] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the features disclosed herein. It is intended that the present disclosure cover any and all variations of the embodiments of the present disclosure comprising features of the disclosure disclosed herein and including variations and modifications thereof in accordance with the principles of the disclosure and including adaptations to a specific use or implementation of the present disclosure. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the embodiments of the present disclosure being indicated by the following claims.

[0481] It is to be understood that the embodiments of the present disclosure are not limited to the precise structures as has been described herein and as shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the present disclosure. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An information processing method, wherein, The method, executed by the sending end, includes: Based on the first attribute information and / or data volume of the target data to be transmitted, a Radio Link Control (RLC) entity for transmitting the target data is determined; the first attribute information is used to indicate the Quality of Service (QoS) requirements of different parts of the target data; wherein, the RLC entity includes a primary RLC entity and a secondary RLC entity; Before determining the RLC entity that transmits the target data, the method further includes: obtaining first configuration information; wherein the first configuration information includes at least one of the following: identification information, indicating the RLC entity that sends the target data; and second attribute information, indicating the attributes of the data that the RLC entity that sends the target data can transmit.

2. The method according to claim 1, wherein, The step of determining the Radio Link Control (RLC) entity for transmitting the target data based on the first attribute information of the target data to be transmitted includes: Based on the first attribute information of the target data, select the RLC entity corresponding to the second attribute information that matches the first attribute information to transmit the target data.

3. The method according to claim 1, wherein, The first configuration information also includes: Mode information, indicating the transmission mode of the RLC entity sending the target data; The transmission modes include: transparent transmission mode TM, unacknowledged mode UM, and / or acknowledged mode AM.

4. The method according to any one of claims 1 to 3, wherein, The first configuration information includes one or more of the following; Importance level; Business type; Quality of Service (QoS) flow identifier; Sub-QoS flow identifier; Priority.

5. The method according to claim 1, wherein, The method further includes: Obtain preset information; wherein, the preset information is used to update the RLC entity that sends the target data.

6. The method according to claim 5, wherein, The preset information includes at least one of the following: The second configuration information is used to reconfigure the RLC entity that sends the target data; Activation information is used to update the RLC entity that sends the target data by activating an inactive RLC entity and / or deactivating an activated RLC entity.

7. The method according to claim 5, wherein, The method further includes: In response to the transmission of the target data, the RLC entity is changed from the first RLC entity to the second RLC entity; Perform the preset function of the target data.

8. The method according to claim 7, wherein, The second RLC entity includes: RLC entity has been established; And / or, RLC entity to be created.

9. The method according to claim 7 or 8, wherein, The preset function for executing the target data includes: Perform the preset operation of the transmission mode with the second RLC entity; or, Activate the PDCP data recovery function.

10. The method according to claim 9, wherein, The preset operation of performing the transmission mode with the second RLC entity includes: In response to the transmission mode of the second RLC entity being AM, it is determined that a first PDCP data unit and a second PDCP data unit will be sent to the second RLC entity; or, In response to the transmission mode of the second RLC entity being TM or UM, it is determined that a second PDCP data unit will be sent to the second RLC entity; The first PDCP data unit includes a PDCP data unit that has been sent to the first RLC entity but has not yet received feedback data; the second PDCP data unit includes a PDCP data unit that has not yet been sent to the first RLC entity.

11. The method according to claim 9, wherein, The activation of the PDCP data recovery function includes: After activating the PDCP data recovery function, a first PDCP data unit and a second PDCP data unit are sent to the second RLC entity; wherein, the first PDCP data unit includes: a PDCP data unit that has been sent to the first RLC entity but has not yet received feedback data; the second PDCP data unit includes: a PDCP data unit that has not yet been sent to the first RLC entity.

12. The method according to claim 7, wherein, The method further includes: In response to the second RLC entity being an RLC entity to be established, the second RLC entity is established.

13. An information processing method, wherein, Performed by the access device, the method includes: Send first configuration information to the user equipment (UE); wherein the first configuration information includes at least one of the following: identification information, indicating the RLC entity that sends the target data; and second attribute information, indicating the attributes of the data that the RLC entity that sends the target data can transmit. The method further includes: Based on the first attribute information and / or data volume of the target data, an RLC entity for sending the target data is determined; the first attribute information is used to indicate the QoS requirements of different parts of the target data; wherein, the RLC entity includes a primary RLC entity and a secondary RLC entity.

14. The method according to claim 13, wherein, The first configuration information also includes: Mode information, indicating the transmission mode of the RLC entity sending the target data; The transmission modes include: transparent transmission mode TM, unacknowledged mode UM, and / or acknowledged mode AM.

15. The method according to claim 13 or 14, wherein, The first configuration information includes one or more of the following; Importance level; Business type; Quality of Service (QoS) flow identifier; Sub-QoS flow identifier; Priority.

16. The method according to claim 13, wherein, The method further includes: Send second configuration information, wherein the second configuration information is used to reconfigure the RLC entity that sends the target data.

17. The method according to claim 13, wherein, The method further includes: Send activation information, which is used to update the RLC entity sending the target data by activating an inactive RLC entity and / or deactivating an activated RLC entity.

18. The method according to claim 17, wherein, The sending of activation information includes: The Media Access Control (MAC) unit CE carrying the activation information is sent.

19. The method according to claim 17 or 18, wherein, The activation information includes: An activation instruction is provided to activate at least one inactive RLC entity configured by the first configuration information. And / or, A deactivation instruction is used to deactivate at least one activated RLC entity configured by the first configuration information.

20. An information processing method, wherein, Performed by a user equipment (UE), the method includes: The system receives first configuration information sent by an access device; wherein the first configuration information includes at least one of the following: identification information, indicating the RLC entity that sends the target data; and second attribute information, indicating the attributes of the data that the RLC entity that sends the target data can transmit. The method further includes: Based on the first attribute information and / or data volume of the target data, an RLC entity for sending the target data is determined; the first attribute information is used to indicate the QoS requirements of different parts of the target data; wherein, the RLC entity includes a primary RLC entity and a secondary RLC entity.

21. The method according to claim 20, wherein, The first configuration information also includes: Mode information, indicating the transmission mode of the RLC entity sending the target data; The transmission modes include: transparent transmission mode TM, unacknowledged mode UM, and / or acknowledged mode AM.

22. The method according to claim 20 or 21, wherein, The first configuration information includes one or more of the following; Importance level; Business type; Quality of Service (QoS) flow identifier; Sub-QoS flow identifier; Priority.

23. The method of claim 20, wherein, The method further includes: Receive second configuration information, wherein the second configuration information is used to reconfigure the RLC entity that sends the target data.

24. The method of claim 20, wherein, The method further includes: Receive activation information to update the RLC entity sending the target data by activating inactive RLC entities and / or deactivating activated RLC entities.

25. An information processing apparatus, wherein, The device includes: The determination module is configured to determine the Radio Link Control (RLC) entity for transmitting the target data based on first attribute information and / or data volume of the target data to be transmitted; the first attribute information is used to indicate the Quality of Service (QoS) requirements of different parts of the target data; wherein the RLC entity includes a primary RLC entity and a secondary RLC entity. The device further includes: an acquisition module configured to acquire first configuration information; wherein the first configuration information includes at least one of the following: identification information indicating the RLC entity that sends the target data; and second attribute information indicating the attributes of the data that the RLC entity that sends the target data can transmit.

26. An information processing apparatus, wherein, The device includes: The transmitting module is configured to transmit first configuration information to a user equipment (UE); wherein the first configuration information includes at least one of the following: identification information indicating an RLC entity that transmits target data; and second attribute information indicating the attributes of the data that the RLC entity that transmits the target data can transmit. The determination module is configured to determine the RLC entity that sends the target data based on the first attribute information and / or the data volume of the target data; the first attribute information is used to indicate the QoS requirements of different parts of the target data; wherein the RLC entity includes a primary RLC entity and a secondary RLC entity.

27. An information processing apparatus, wherein, The device includes: The receiving module is configured to receive first configuration information sent by the access device; wherein the first configuration information includes at least one of the following: identification information, indicating the RLC entity that sends the target data; and second attribute information, indicating the attributes of the data that the RLC entity that sends the target data can transmit. The determination module is configured to determine the RLC entity that sends the target data based on the first attribute information and / or the data volume of the target data; the first attribute information is used to indicate the QoS requirements of different parts of the target data; wherein the RLC entity includes a primary RLC entity and a secondary RLC entity.

28. A communication device comprising a processor, a transceiver, a memory, and an executable program stored in the memory and executable by the processor, wherein, When the processor runs the executable program, it performs the method provided as claimed in any one of claims 1 to 12, 13 to 19, or 20 to 24.

29. A computer storage medium storing an executable program; the executable program, when executed by a processor, is capable of implementing the method provided in any one of claims 1 to 12, 13 to 19, or 20 to 24.

Images