Data processing method and device, equipment, storage medium and program product

Abstract

The invention discloses a data processing method and device, equipment, a storage medium and a program product, and relates to the technical field of communication. The method comprises performing independent processing and / or joint processing on different data corresponding to the same QoS flow (410). Under the condition that different data corresponding to the same QoS flow are independently processed, the processing of the different data corresponding to the same QoS flow can be independently considered, the flexibility is higher, and different requirements of the different data are met; according to the invention, under the condition that the different data corresponding to the same QoS flow are jointly processed, the processing of the different data corresponding to the same QoS flow can be jointly considered, so that the mutual influence or association among the different data is considered, and the accuracy and rationality of the processing of the different data corresponding to the same QoS flow are improved.

Description

Data processing method, device, equipment, storage medium and program product Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a data processing method, apparatus, device, storage medium, and program product. Background Art

[0002] In related technologies, data processing is performed at the granularity of QoS (Quality of Service) flows or sessions. A set of PDUs (Protocol Data Units) of the same QoS flow or the same session granularity are processed indiscriminately, which cannot meet actual needs in special scenarios.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a data processing method, apparatus, device, storage medium, and program product. The technical solution is as follows:

[0005] According to one aspect of an embodiment of the present application, a data processing method is provided, the method comprising:

[0006] Different data corresponding to the same QoS flow are processed independently and / or jointly.

[0007] According to one aspect of an embodiment of the present application, a data processing method is provided, the method comprising:

[0008] Measurement statistics are performed on the PDU set to obtain a first result.

[0009] According to one aspect of an embodiment of the present application, a data processing device is provided, the device comprising:

[0010] The data processing module is used to independently process and / or jointly process different data corresponding to the same QoS flow.

[0011] According to one aspect of an embodiment of the present application, a data processing device is provided, the device comprising:

[0012] The measurement and statistics module is used to perform measurement and statistics on the PDU set to obtain a first result.

[0013] According to one aspect of an embodiment of the present application, a communication device is provided, comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement any of the above-mentioned data processing methods.

[0014] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to be executed by a processor to implement any of the above-mentioned data processing methods.

[0015] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement any of the above-mentioned data processing methods.

[0016] According to one aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement any of the above-mentioned data processing methods.

[0017] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0018] On the one hand, different data corresponding to the same QoS flow (such as different PDU sets) are processed independently and / or jointly. When different data corresponding to the same QoS flow are processed independently, the processing of different data corresponding to the same QoS flow can be considered separately and independently, which is more flexible and meets the different needs of different data; when different data corresponding to the same QoS flow are processed jointly, the processing of different data corresponding to the same QoS flow can be considered jointly, thereby taking into account the mutual influence or correlation between different data, and improving the accuracy and rationality of the processing of different data corresponding to the same QoS flow.

[0019] On the other hand, corresponding results are obtained by performing measurement statistics on the PDU set, thereby realizing measurement statistics with the PDU set as the granularity, which can be used for QoS monitoring and / or QoS verification at the PDU set granularity. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0021] FIG2 is a schematic diagram of data interaction based on QoS flow provided by one embodiment of the present application;

[0022] FIG3 is a schematic diagram of a wireless protocol architecture provided by an embodiment of the present application;

[0023] FIG4 is a flow chart of a data processing method provided by one embodiment of the present application;

[0024] FIG5 is a schematic diagram of PDCP protocol layer joint processing provided by an embodiment of the present application;

[0025] FIG6 is a schematic diagram of PDCP protocol layer joint processing provided by another embodiment of the present application;

[0026] FIG7 is a schematic diagram of a PDCP layer data processing method provided by an embodiment of the present application;

[0027] FIG8 is a schematic diagram of a PDCP layer data processing method provided by another embodiment of the present application;

[0028] FIG9 is a schematic diagram of a PDCP layer data processing method provided by another embodiment of the present application;

[0029] FIG10 is a schematic diagram of a PDCP layer data processing method provided in another embodiment of the present application;

[0030] FIG11 is a schematic diagram of a method for processing SDAP layer data according to another embodiment of the present application;

[0031] FIG12 is a schematic diagram of a method for processing SDAP layer data according to another embodiment of the present application;

[0032] FIG13 is a flowchart of a PDCP reconfiguration method provided by one embodiment of the present application;

[0033] FIG14 is a flowchart of a PDCP reconfiguration method provided by another embodiment of the present application;

[0034] FIG15 is a flowchart of configuring or changing the mapping relationship between QoS flows and paths provided by one embodiment of the present application;

[0035] FIG16 is a flow chart of a data processing method provided by another embodiment of the present application;

[0036] FIG17 is a block diagram of a data processing device provided by one embodiment of the present application;

[0037] FIG18 is a block diagram of a data processing device provided by another embodiment of the present application;

[0038] FIG19 is a schematic structural diagram of a communication device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0040] First, a brief introduction to the terms involved in the embodiments of this application is given:

[0041] PDU set: A PDU set consists of one or more PDUs that carry the payload of an information unit generated at the application layer. For example, the information unit is an XRM (Extended Reality and Media Services) frame or video clip. These pieces of information have the same importance requirements at the application layer. The application layer requires all PDUs in the PDU set to use the corresponding information unit. In some cases, when some PDUs are lost, the application layer can still recover some of the information units. It should be noted that the I-frames, P-frames, etc. mentioned later are just one form of representation of a PDU set.

[0042] I-frame: As an intra-coded picture, an I-frame is a complete picture that can be independently encoded and decoded like a JPG image file.

[0043] P-frame: As a predicted picture, a P-frame is not a complete frame and only contains image changes compared to the previous frame. If the reference frame is lost, the P-frame will not be decoded and displayed.

[0044] B-frames: As bidirectionally predicted pictures, B-frames contain the changes between the previous and next reference frames. The more reference frames there are, the higher the compression ratio. However, B-frames can only be decoded if both the previous and next reference frames are available.

[0045] GOP: GOP consists of a set of consecutive video frames. The first frame of GOP is I frame, and the following frames can be P frames or B frames.

[0046] For example, PDUs may be associated or dependent on each other. For example, a PDU set represents a video frame. The compression and decoding of the video frame can only be completed when all PDUs associated with the PDU set are received at the same time. Alternatively, the compression and decoding of the video frame can only be completed when instructions for some PDUs are received. In addition, different PDU sets may also be associated or dependent on each other. For example, the PDU set representing I frames has a dependency on the PDU set representing P frames, and the compression and decoding of P frames depends on I frames.

[0047] 5G network system architecture: Please refer to Figure 1. The 5G network system includes: User Equipment (3GPP's naming for mobile terminals) (User Equipment, UE), (Radio) Access Network ((R)AN), User Plane Function (UPF), Data Network (DN) and Control Plane Function.

[0048] Among them, the control plane functions include: Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF) and Unified Data Manager (UDM), Application Function (AF), Network Slice Selection Function (NSSF), and Authentication Server Function (AUSF).

[0049] Among them, the UE establishes an access layer connection with the AN through the Uu air interface, exchanges access layer messages and performs wireless data transmission. The UE establishes a non-access layer (NAS) connection with the AMF through the N1 interface and exchanges NAS messages. AMF is the mobility management function in the core network, and SMF is the session management function in the core network. In addition to managing the mobility of the UE, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. PCF is the policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, billing, etc. UPF is the user plane function in the core network, which transmits data with the external data network through the N6 interface and with the AN through the N3 interface.

[0050] The concept of QoS Flow (Quality of Service Flow) is introduced in 5G networks. After a UE accesses the 5G network through the Uu air interface, it establishes a QoS flow for data transmission under the control of the SMF. The SMF provides the base station with QoS flow configuration information for each QoS flow, including bit rate requirements, latency requirements, and bit error rate requirements. For each QoS flow, the base station schedules radio resources based on the QoS flow configuration information received from the SMF to ensure QoS requirements for the QoS flow.

[0051] In a 5G network, a QoS flow can transmit both uplink data flow (data flow sent by the UE to the peer device through the 5G network) and downlink data flow (data flow sent by the peer device to the UE through the 5G network). The peer device here refers to the peer application server or the peer UE. The latency requirements for uplink data flow and downlink data flow in a QoS flow are the same. If the latency requirements for the uplink data flow and downlink data flow of a certain service are different, they will be transmitted through different QoS flows. The latency here refers to the data transmission latency between the UE and the UPF.

[0052] Data processing in 5G networks does not consider the needs of different PDUs or PDU sets, and performs processing specific to different PDUs or PDU sets. Therefore, the needs of different PDUs or PDU sets cannot be met.

[0053] Referring to Figure 2, in a mobile communication network, one or more QoS flows must be established to transmit user-plane data. Different data flows correspond to different QoS parameters. As an important measure of communication quality, QoS parameters are typically used to indicate the characteristics of a QoS flow. These parameters include, but are not limited to, 5QI, Allocation and Retention Priority (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), Maximum Packet Loss Rate (UL, DL), End-to-End Packet Delay Budget (PDB), Access Network-Packet Delay Budget (AN-PDB), Packet Error Rate (PER), Priority Level, Averaging Window, Resource Type, Maximum Data Burst Volume (MDBV), Maximum Aggregate Bit Rate per User (UE-AMBR), and Maximum Aggregate Bit Rate per Session (Session-AMBR).

[0054] A filter (or SDF template) contains parameters that describe the characteristics of a data packet and is used to filter specific data packets bound to a specific QoS flow (i.e., the data packet-to-QoS flow mapping in Figure 2). The most commonly used filter is the IP quintuple, which consists of the source and destination IP addresses, source and destination port numbers, and protocol type.

[0055] The network-side user plane element (UPF in Figure 2) and the terminal device (UE in Figure 2) will form a filter (such as the trapezoid on the far left and the parallelogram on the far right) based on the combination of data packet characteristic parameters to filter the uplink or downlink data packets that meet the data packet characteristics transmitted on the user plane and bind them to a certain data flow.

[0056] Please refer to FIG3 , which shows a schematic diagram of a wireless protocol architecture in the related art.

[0057] SDAP (Service Data Adaptation Protocol): responsible for mapping QoS bearers to DRBs (Data Radio Bearers) according to QoS requirements.

[0058] PDCP (Packet Data Convergence Protocol): Implements IP header compression, encryption, and integrity protection. It also handles retransmission, in-order delivery, and deduplication during handover. For dual connectivity with split bearer, PDCP provides routing and replication, configuring a PDCP entity for each radio bearer on the terminal device.

[0059] RLC (Radio-Link Control): Responsible for data segmentation and retransmission. RLC provides services to PDCP in the form of RLC channels (or logical channels). Each RLC channel (corresponding to each radio bearer) is configured with an RLC entity for each terminal device.

[0060] MAC (Medium-Access Control): Responsible for logical channel multiplexing, HA ARQ retransmission, scheduling, and scheduling-related functions. Scheduling functions for uplink and downlink reside in the gNB. MAC provides services to RLC in the form of logical channels (LCHs). NR (New Radio) changes the MAC layer header structure.

[0061] PHY (Physical Layer): Responsible for encoding and decoding, modulation, demodulation, multi-antenna mapping, and other typical physical layer functions. The physical layer provides services to the MAC layer in the form of a transmission channel.

[0062] Please refer to Figure 4, which shows a flow chart of a data processing method provided by an embodiment of the present application. The method may include the following steps:

[0063] Step 410: Perform independent processing and / or joint processing on different data corresponding to the same QoS flow.

[0064] In some embodiments, independent processing of different data corresponding to the same QoS flow means that different data corresponding to the same QoS flow are processed separately, or that they are processed independently, and the processing of the different data is independent of each other and does not affect each other. For example, different data corresponding to the same QoS flow includes data 1 and data 2, and data 1 and data 2 are two or two different groups of data corresponding to the same QoS flow. Independent processing of data 1 and data 2 means that data 1 is processed independently and data 2 is processed independently, and the processing of data 1 and data 2 is differentiated, or that the processing is independent of each other and does not affect each other.

[0065] In some embodiments, different data corresponding to the same QoS flow are jointly processed, which means that the different data corresponding to the same QoS flow are jointly processed, or jointly processed, or non-independently processed. In this case, the processing of different data is jointly considered and there is mutual influence. For example, different data corresponding to the same QoS flow include data 1 and data 2, and data 1 and data 2 are two or two groups of different data corresponding to the same QoS flow. Jointly processing data 1 and data 2 means jointly processing data 1 and data 2, and the processing of data 1 and the processing of data 2 are comprehensively considered, and there is mutual influence.

[0066] In some embodiments, different data corresponding to the same QoS flow are processed independently and jointly. Since there can be multiple processes for data, some of the processes can be independently processed for different data corresponding to the same QoS flow, while some of the processes can be jointly processed for different data corresponding to the same QoS flow. For example, there can be A processing and B processing for data. The different data corresponding to the same QoS flow include data 1 and data 2, and data 1 and data 2 are two or two different groups of data corresponding to the same QoS flow. For A processing, data 1 and data 2 can be processed independently. For B processing, data 1 and data 2 can be jointly processed.

[0067] In some embodiments, different data corresponds to different PDU sets. Different PDU sets corresponding to the same QoS flow are processed independently and / or jointly. For example, a first PDU set and a second PDU set corresponding to the same QoS flow are processed independently and / or jointly, where the first PDU set and the second PDU set are two different PDU sets.

[0068] In some embodiments, different data corresponds to PDU sets with different attributes. Optionally, the attributes include at least one of the following: type, importance, relevance, priority, and dependency.

[0069] In some embodiments, different data have different attributes. Optionally, the attributes include at least one of the following: type, importance, relevance, priority, and dependency.

[0070] In some embodiments, the type of the data and / or PDU set is used to distinguish different types of data and / or PDU sets, for example, which type of frame, which type of coded slice, etc. For example, whether it is an I frame or a P frame, an I coded slice or a P coded slice, etc.

[0071] In some embodiments, the importance of the above-mentioned data and / or PDU set is an indicator for measuring the importance of the data and / or PDU set. For example, importance can be divided into two different levels, such as important and unimportant; or, importance can also be divided into three or more different levels. For example, importance can be represented by an importance level value, and different importance level values ​​correspond to different degrees of importance. For example, the importance level value can include two levels, 1 and 2, or three levels, 1, 2, and 3, or four levels, 1, 2, 3, and 4, etc. This application does not limit this.

[0072] In some embodiments, the correlation of the above-mentioned data and / or PDU sets is an indicator used to measure the degree of correlation between data and / or PDU sets. For example, the correlation can be divided into two different levels, such as correlation and non-correlation; or, the correlation can also be divided into three or more different levels. For example, the correlation can be represented by a correlation level value, and different correlation level values ​​correspond to different degrees of correlation. For example, the correlation level value can include two levels, 1 and 2, or three levels, 1, 2, and 3, or four levels, 1, 2, 3, and 4, etc. This application does not limit this.

[0073] In some embodiments, the priority of the above-mentioned data and / or PDU set is an indicator for measuring the priority of the data and / or PDU set. For example, the priority can be divided into two different levels, such as priority and non-priority; or, the priority can also be divided into three or more different levels. For example, the priority can be represented by a priority value, and different priority values ​​correspond to different priority levels. For example, the priority value can include two levels, 1 and 2, or three levels, 1, 2, and 3, or four levels, 1, 2, 3, and 4, etc. This application does not limit this.

[0074] In some embodiments, the dependency of the above-mentioned data and / or PDU sets is an indicator used to measure the degree of dependency between data and / or PDU sets. For example, dependency can be divided into two different levels, such as dependency and non-dependence; or, dependency can also be divided into three or more different levels. For example, dependency can be represented by a dependency level value, and different dependency level values ​​correspond to different degrees of dependency. For example, the dependency level value can include two levels, 1 and 2, or three levels, 1, 2, and 3, or four levels, 1, 2, 3, and 4, etc. This application does not limit this.

[0075] In some embodiments, different data corresponds to different paths. A path is used to transmit data, for example, for sending and / or receiving data. In some embodiments, the path is an RB (Radio Bearer). Optionally, the RB is a DRB (Data Radio Bearer). For example, different data corresponds to different DRBs. For example, a QoS flow is mapped to different paths, such as different DRBs. For example, different data corresponding to the same QoS flow is mapped to different paths, such as different DRBs. Mapping certain data to a certain path means that the path is used to transmit (including sending and / or receiving) the data.

[0076] In some embodiments, different data corresponds to different paths, and different paths may also refer to at least one of the following: different RLCs, different logical channels, and different PDCPs.

[0077] In some embodiments, the above method is executed by a transmitting end, and the transmitting end performs independent processing and / or joint processing on different data corresponding to the same QoS flow.

[0078] In some embodiments, the sending end independently processes different data corresponding to the same QoS flow, and the independent processing includes at least one of the following: routing different data to different paths, identifying different data, and using different first functions for different data.

[0079] In some embodiments, the sending end is the SDAP layer, and the SDAP layer routes different data to different paths, including: the SDAP layer routes different data to different PDCP entities; or, the SDAP layer routes different data to different DRBs.

[0080] In some embodiments, the transmitting end is the PDCP layer, and the PDCP layer routes different data to different paths, including: the PDCP layer routes different data to different RLC entities; or, the PDCP layer routes different data to different logical channels.

[0081] In some embodiments, the transmitting end identifies different data, including at least one of the following situations 1 to 3:

[0082] Case 1: Identify different data based on the PDU set corresponding to the data;

[0083] For example, when different data refers to different PDU sets, the different data may be identified according to the PDU set to which the PDU belongs.

[0084] Case 2: Different data are identified based on the start identifier and / or end identifier of the PDU set;

[0085] For example, when different data refers to different PDU sets, different data can be identified based on the start identifier and / or end identifier of the PDU set. The start identifier of the PDU set is used to indicate the starting position of the PDU set, such as the PDU or the first PDU indicating the starting position of the PDU set, or the starting interval point of the PDU set; the end identifier of the PDU set is used to indicate the ending position of the PDU set, such as the PDU or the last PDU indicating the ending position of the PDU set, or the ending interval point of the PDU set. Alternatively, different data can be identified based on the interval identifiers between PDU sets, or different PDU sets can be distinguished.

[0086] Case 3: different data are identified according to attributes of the data, where the attributes include at least one of the following: type, importance, relevance, priority, and dependency.

[0087] For example, when different data have different attributes, the different data can be identified based on the attributes of the data. For example, when different PDU sets have different attributes, the different PDU sets can be identified based on the attributes of the PDU sets. For an introduction to the attributes, please refer to the above embodiments and will not be repeated here.

[0088] In addition, in the embodiments of the present application, data is mainly taken as a PDU set as an example. In some other embodiments, the data may also be a code slice, a video frame, or a GOP, etc. For example, different code slices corresponding to the same QoS flow are processed independently and / or jointly; or different frames (such as I frames, P frames, and B frames) corresponding to the same QoS flow are processed independently and / or jointly; or different GOPs corresponding to the same QoS flow are processed independently and / or jointly.

[0089] In some embodiments, the transmitter performs joint processing on different data corresponding to the same QoS flow, and the joint processing includes at least one of the following: using a unified SN (Sequence Number) for numbering different data, using a unified first function for different data, and further using a common buffer for different data.

[0090] The sending end uses a unified SN to number different data, which means that different data are jointly numbered. For example, data 1 and data 2 are different data. Data 1 includes data packet A, data packet B, and data packet C, and data packet D and data packet E. In the case of joint numbering, illustratively, the SN corresponding to data packet A is 1, the SN corresponding to data packet D is 2, the SN corresponding to data packet B is 3, the SN corresponding to data packet C is 4, and the SN corresponding to data packet E is 5. If independent numbering is used, illustratively, the SN corresponding to data packet A is 1, the SN corresponding to data packet B is 2, the SN corresponding to data packet C is 3, the SN corresponding to data packet D is 1, and the SN corresponding to data packet E is 2. The above examples show the difference between independent numbering and joint numbering.

[0091] In some embodiments, the transmitter uses a unified SN for numbering different PDU sets, which means that different PDU sets are jointly numbered. For example, PDU set 1 and PDU set 2 are different PDU sets, PDU set 1 includes PDU A, PDU B, and PDU C, and PDU set 2 includes PDU D and PDU E. In the case of joint numbering, illustratively, the SN corresponding to PDU A is 1, the SN corresponding to PDU B is 2, the SN corresponding to PDU D is 3, the SN corresponding to PDU C is 4, and the SN corresponding to PDU E is 5.

[0092] In some embodiments, the transmitting end uses a unified first function for different data, and the first function includes at least one of the following: an integrity protection function, an encryption function, and a header compression function. Exemplarily, a unified first function is used for different PDU sets, and the first function includes at least one of the following: an integrity protection function, an encryption function, and a header compression function.

[0093] In some embodiments, the above method is executed by a receiving end, and the receiving end performs independent processing and / or joint processing on different data corresponding to the same QoS flow.

[0094] In some embodiments, the receiving end independently processes different data corresponding to the same QoS flow, and the independent processing includes at least one of the following: receiving different data from different paths, and using different second functions for different data.

[0095] In some embodiments, the receiving end is the SDAP layer, and the SDAP layer receives different data from different paths, including: the SDAP layer receives different data from different PDCP entities; or the SDAP layer receives different data from different DRBs.

[0096] In some embodiments, the receiving end is the PDCP layer, and the PDCP layer receives different data from different paths, including: the PDCP layer receives different data from different RLC entities; or, the PDCP layer receives different data from different logical channels.

[0097] In some embodiments, the receiving end uses different second functions for different data, and the second functions include at least one of the following: integrity authentication function, decryption function, and decompression function. Exemplarily, the receiving end uses different second functions for different PDU sets, and the second functions include at least one of the following: integrity authentication function, decryption function, and decompression function.

[0098] In some embodiments, the receiving end performs joint processing on different data corresponding to the same QoS flow, and the joint processing includes at least one of the following: reordering different data according to a unified SN; using a unified second function for different data.

[0099] The receiving end reorders different data using a unified SN, which refers to joint reordering of the different data. For example, Data 1 and Data 2 are different data. Data 1 includes packets A, B, and C, while Data 2 includes packets D and E. In the case of joint reordering, the receiving end receives packet A with a SN of 1, packet B with a SN of 3, packet C with a SN of 4, packet D with a SN of 2, and packet E with a SN of 5. Reordering these packets in ascending SN order results in the following: packet A, packet D, packet B, packet C, packet E.

[0100] In some embodiments, the receiving end reorders different PDU sets according to a unified SN, which refers to joint reordering of different PDU sets. For example, PDU set 1 and PDU set 2 are different PDU sets, PDU set 1 includes PDU A, PDU B, and PDU C, and PDU set 2 includes PDU D and PDU E. In the case of joint reordering, illustratively, the SN corresponding to PDU A received by the receiving end is 1, the SN corresponding to PDU B is 2, the SN corresponding to PDU C is 4, the SN corresponding to PDU D is 3, and the SN corresponding to PDU E is 5. The result of reordering the above PDUs in ascending order of SN is as follows: PDU A, PDU B, PDU D, PDU C, PDU E.

[0101] Furthermore, in some embodiments, the receiving end delivers the data packet to the upper layer while reordering different PDU sets according to a unified SN.

[0102] In some embodiments, the receiving end uses a unified second function for different data, and the second function includes at least one of the following: an integrity authentication function, a decryption function, and a decompression function. Exemplarily, the receiving end uses a unified second function for different PDU sets, and the second function includes at least one of the following: an integrity authentication function, a decryption function, and a decompression function.

[0103] In some embodiments, the joint processing performed by the transmitting end and / or the receiving end includes at least one of the following: performing joint processing between protocol layers or entities for the joint processing of different data, and performing joint processing between protocol layers or entities for data routed to different paths. In some embodiments, the protocol layer or entity is a PDCP protocol layer or a PDCP entity; or, the protocol layer or entity is a joint protocol layer or joint entity of a corresponding PDCP protocol layer or PDCP entity.

[0104] Taking the PDCP protocol layer as an example, joint processing is performed between the PDCP protocol layer or PDCP entities, which means that the PDCP protocol layer may include multiple different PDCP entities, and joint processing is performed between these multiple different PDCP entities. For example, as shown in Figure 5, the same QoS flow corresponds to two different PDU sets, including a first PDU set and a second PDU set, and the two different PDU sets correspond to two different paths. The PDCP protocol layer includes a first PDCP entity and a second PDCP entity, and these two PDCP entities jointly process the above two different PDU sets.

[0105] In some embodiments, the joint processing is directed to a plurality of different PDCP entities, and different data corresponds to the above-mentioned different PDCP entities.

[0106] In some embodiments, the joint PDCP layer or joint PDCP entity corresponds to multiple different PDCP entities, and the different data corresponds to different PDCP entities. For example, as shown in FIG6 , the same QoS flow corresponds to two different PDU sets, including a first PDU set and a second PDU set. The two different PDU sets correspond to two different paths. Optionally, the different paths correspond to different PDCP entities. The joint PDCP layer or joint PDCP entity performs joint processing on the two different PDU sets.

[0107] In some embodiments, different PDCP entities have a binding relationship or a joint processing relationship. Joint processing is performed on multiple PDCP entities with a binding relationship or a joint processing relationship. Optionally, the binding relationship, or the joint processing relationship, and / or the joint processing PDCP entity, or the joint processing entity, is network-configured, for example, via RRC.

[0108] In some embodiments, independent processing and / or joint processing of different data are performed in the same PDCP entity. Optionally, the PDCP entity reuses a DAPS (Dual Active Protocol Stack) architecture.

[0109] The technical solution provided in the embodiments of the present application performs independent and / or joint processing on different data (such as different PDU sets) corresponding to the same QoS flow. When different data corresponding to the same QoS flow are processed independently, the processing of different data corresponding to the same QoS flow can be considered separately and independently, which is more flexible and meets the different needs of different data. When different data corresponding to the same QoS flow are processed jointly, the processing of different data corresponding to the same QoS flow can be considered jointly, thereby taking into account the mutual influence or correlation between different data, and improving the accuracy and rationality of the processing of different data corresponding to the same QoS flow.

[0110] In some embodiments, the technical solution of the present application can be applied to both UL (Uplink) and DL (Downlink) transmission scenarios. The sending and receiving parties are the terminal device and the access network device. For example, in the UL transmission scenario, the sending end is the terminal device and the receiving end is the access network device; in the DL transmission scenario, the sending end is the access network device and the receiving end is the terminal device.

[0111] In some embodiments, for a transmitting end (a terminal device in a UL scenario, or an access network device in a DL scenario), the transmitting end independently processes different data corresponding to the same QoS flow, including at least one of the following situations 1 to 3:

[0112] Case 1, identifying different data.

[0113] In some embodiments, each or different PDU sets are identified, or associated PDU identification is performed, or different types of PDU sets are identified, or associations or dependencies between PDU sets are identified, or the importance of different PDU sets is identified, or the priority of different PDU sets is identified.

[0114] Association means that a PDU set works alone, but works together with other PDU sets to work as a whole. Dependency means that a PDU set relies on one or more PDU sets to be decoded, used or worked, and the two work together as a whole. Importance refers to the importance of a PDU set. Priority refers to the order of a PDU set in transmission or processing requirements, or the priority difference in transmission or processing requirements. Association means that different PDU sets work alone, but work together as a whole. Dependency means that a PDU set relies on one or more other PDU sets to be decoded, used or worked, and the two work together as a whole.

[0115] In some embodiments, the SDAP layer at the sending end identifies different data.

[0116] In some embodiments, the PDCP layer at the transmitting end identifies different data, for example, the SDAP layer at the transmitting end instructs the PDCP, or the PDCP itself identifies the different data.

[0117] Case 2: Routing different data to different paths.

[0118] In some embodiments, the correspondence (or mapping relationship) between different data and different paths can be configured by the access network device. For example, when the transmitting end is a terminal device, the access network device can send signaling to the terminal device, and configure the correspondence between different data and different paths through the signaling. Optionally, the above signaling can be RRC signaling or other signaling, which is not limited in this application. For example, when the transmitting end is an access network device, the access network device can determine or configure the correspondence between different data and different paths by itself.

[0119] In some embodiments, the SDAP layer and / or the PDCP layer at the transmitting end routes different data to different paths.

[0120] In some embodiments, the SDAP layer and / or the PDCP layer at the transmitting end identifies the relationship between different data and different paths.

[0121] For the SDAP layer, the SDAP layer routes different data corresponding to the same QoS flow to different DRBs or PDCP entities, for example, identifying different data or different PDU sets based on SDAP.

[0122] For the PDCP layer, the PDCP layer routes different data corresponding to the same QoS flow to different RLC entities or logical channels. For example, the PDCP layer routes data of different DRBs of a PDCP entity to different RLC entities, or routes different data to different RLC entities.

[0123] Case 3: different first functions are used for different data, and the first function includes at least one of the following: integrity protection function, encryption function, and header compression function.

[0124] For example, different integrity protection functions and / or different encryption functions are used for multiple DRBs of a PDCP entity or different data of an RLC entity.

[0125] For example, different integrity protection functions and / or different encryption functions and / or different header compression functions are used for multiple DRBs of a PDCP entity or different data of an RLC entity.

[0126] In some embodiments, for a transmitting end (a terminal device in a UL scenario, or an access network device in a DL scenario), the transmitting end performs joint processing on different data corresponding to the same QoS flow, including at least one of the following situations 1 to 2:

[0127] Case 1: Use a unified SN for numbering different data.

[0128] For example, a unified SN is used to number multiple DRBs of a PDCP entity or different data of an RLC entity.

[0129] For example, different data of multiple associated PDCP or DRB entities are numbered using a unified SN.

[0130] Case 2: A unified first function is used for different data, and the first function includes at least one of the following: an integrity protection function, an encryption function, and a header compression function.

[0131] For example, a unified header compression function is used for multiple DRBs of a PDCP entity or different data of an RLC entity.

[0132] For example, a unified header compression function is used for different data of multiple associated PDCP or DRB entities.

[0133] In some embodiments, a PDCP entity includes a DRB, and a PDCP may correspond to one or more RLC entities. Different DRBs or RLC entities transmit different data. For example, the PDCP entity may be one or each of multiple associated PDCPs.

[0134] In some embodiments, within a DRB corresponding to a PDCP entity, different DRBs may correspond to different integrity protection functions and / or different encryption functions. Furthermore, different header compression functions may correspond to the same header compression function. For example, the PDCP entity may be one or each of multiple associated PDCPs.

[0135] In some embodiments, a PDCP entity includes more than one DRB, each corresponding to an RLC entity. Different DRBs or RLC entities transmit different data. The PDCP at the transmitting end implements the above-mentioned independent processing and / or joint processing of different data corresponding to the same QoS flow. For example, the DRBs may be two or more. The RLC entities may be two or more.

[0136] In some embodiments, a PDCP entity may correspond to more than one DRB, or to multiple RLC entities, and different DRBs or RLC entities may correspond to different integrity protection functions and / or different encryption functions. Furthermore, different header compression functions or a unified header compression function may also correspond. These functions are implemented in PDCP.

[0137] In some embodiments, the transmitting end DAPS PDCP layer functional architecture is multiplexed and the functions are implemented in PDCP.

[0138] In some embodiments, for a receiving end (an access network device in a UL scenario, or a terminal device in a DL scenario), the receiving end independently processes different data corresponding to the same QoS flow, including at least one of the following situations 1 to 2:

[0139] Case 1: receiving different data from different paths.

[0140] In some embodiments, the correspondence (or mapping relationship) between different data and different paths can be configured by the access network device. For example, when the receiving end is a terminal device, the access network device can send signaling to the terminal device to configure the correspondence between different data and different paths through the signaling. Optionally, the above-mentioned signaling can be RRC signaling or other signaling, which is not limited in this application. For example, when the receiving end is an access network device, the access network device can determine or configure the correspondence between different data and different paths by itself.

[0141] In some embodiments, the SDAP layer and / or the PDCP layer at the receiving end receives different data from different paths.

[0142] For the SDAP layer, the SDAP layer receives different data from different PDCP entities; or receives different data from different DRBs.

[0143] For the PDCP layer, the PDCP layer receives different data from different RLC entities; or receives different data from different logical channels.

[0144] Case 2: different second functions are used for different data, and the second function includes at least one of the following: integrity authentication function, decryption function, and decompression function.

[0145] For example, different integrity authentication functions and / or different decryption functions are used for multiple DRBs of a PDCP entity or different data of an RLC entity.

[0146] For example, different integrity authentication functions and / or different decryption functions are used for one PDCP entity or each PDCP entity of multiple associated PDCPs, or for one DRB or each DRB of multiple associated PDCPs.

[0147] For example, different integrity authentication functions and / or different decryption functions and / or different decompression functions are used for a PDCP entity or each PDCP entity of multiple associated PDCPs, or for a DRB or each DRB of multiple associated PDCPs.

[0148] In some embodiments, for a receiving end (an access network device in a UL scenario, or a terminal device in a DL scenario), the receiving end performs joint processing on different data corresponding to the same QoS flow, including at least one of the following situations 1 to 2:

[0149] Case 1: reorder different data according to a unified SN.

[0150] For example, the different data of multiple DRBs or RLC entities of a PDCP entity are reordered according to a unified SN. The purpose is to ensure that different data (such as different PDU sets) are delivered to the upper layer in order. Optionally, the reordering is performed using a unified SN number corresponding to the different data of multiple DRBs or RLC entities of a PDCP entity. The above reordering is implemented in PDCP.

[0151] For example, multiple associated PDCPs are reordered based on a unified SN. This is to ensure that different data (e.g., different PDU sets) are delivered to higher layers in sequence. Optionally, the reordering is performed using a unified SN number corresponding to different data of the associated PDCP entity. This reordering is implemented in the joint PDCP implementation or the joint protocol layer.

[0152] Case 2: A unified second function is used for different data, and the second function includes at least one of the following: integrity authentication function, decryption function, and decompression function.

[0153] For example, a unified decompression function is used for multiple DRBs of a PDCP entity or different data of an RLC entity.

[0154] In some embodiments, a PDCP entity includes more than one DRB, each corresponding to an RLC entity. Different data is received from different RLC entities. The PDCP at the receiving end implements the aforementioned independent processing and / or joint processing of different data corresponding to the same QoS flow. For example, the number of DRBs may be two or more. The number of RLC entities may be two or more.

[0155] For example, a unified decompression function is used for different data of multiple associated PDCP or DRB entities.

[0156] In some embodiments, a PDCP entity includes a DRB, and a PDCP may correspond to one or more RLC entities. Different DRBs or RLC entities transmit different data. For example, the PDCP entity may be one or each of multiple associated PDCPs.

[0157] In some embodiments, within a DRB corresponding to a PDCP entity, different DRBs may correspond to different integrity authentication functions and / or different decryption functions. Furthermore, different decompression functions may also correspond to a unified decompression function. For example, the PDCP entity may be one or each of multiple associated PDCPs.

[0158] In some embodiments, a PDCP entity may correspond to more than one DRB, or to multiple RLC entities, and different DRBs or RLC entities may correspond to different integrity authentication functions and / or different decryption functions. Furthermore, different decompression functions or a unified decompression function may also correspond. These functions are implemented in PDCP.

[0159] In some embodiments, the receiving-side DAPS PDCP layer functional architecture is multiplexed and the functions are implemented in PDCP.

[0160] In some embodiments, the sending end performs at least one of the following steps Step 0 to Step 2 (optionally, the order of the steps is not limited):

[0161] In Step 0, RRC configures a mapping relationship between a QoS flow and multiple paths. A QoS flow corresponds to multiple DRBs, a PDCP entity corresponds to multiple RBs, and a PDCP corresponds to multiple RLCs.

[0162] Optionally, different DRBs or PDCPs are configured with different indications (such as I / P frames), or different DRBs or PDCPs are configured with different flags (flags, such as reliable or low reliability, or important or unimportant, or different importance levels, or different reliability levels, or different priorities).

[0163] Optionally, different RLCs are configured with different indications (such as I / P frames), or different RLCs are configured with different flags (flags, such as reliable or low reliability, or important or unimportant, or different importance levels, or different reliability levels, or different priorities).

[0164] Step 1: The SDAP sending end's actions include at least one of the following actions 1 and 2:

[0165] Behavior 1: SDAP recognizes different data.

[0166] For example, in order to identify different PDU sets, SDAP knows which type of PDU set it is through higher layer information, identifies different data through the packet header of the higher layer (such as the GTP-U message of the core network), or identifies which data goes to which path through the indication in the DL SDAP packet header.

[0167] Behavior 2: SDAP routes different data and / or indicates different information of different data to the lower layer (PDCP).

[0168] For example, for an SDAP SDU of a QoS flow received from a higher layer, the transmitting SDAP entity performs at least one of the following actions: generates an SDAP PDU; distributes the PDU to the corresponding or correct lower layer path according to the mapping relationship configured by RRC; indicates different information of different data to the lower layer (PDCP), for example, the different information may be: importance, or relevance, or priority, or dependency, or frame type, or packet type, etc.

[0169] In step 2, the PDCP behavior of the transmitting end includes at least one of the following behaviors 1 to 5:

[0170] Behavior 1: When submitting a PDCP PDU to the lower layer, the transmitting PDCP entity will: if the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with the first RB (the first RB is a special-identified RB, an XR-identified RB, or a differentiated processing RB, etc.); or if the transmitting PDCP entity is associated with at least two RLC entities, and different RLC entities associated with the transmitting PDCP entity correspond to different RBs, or if the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity differentiates and processes different PDU sets or data, or the joint PDCP entity is associated with different RLC entities and transmits different PDU sets (corresponding to a QoS flow), then different PDCP PDUs are submitted to different RLC entities. Specifically, the first PDCP PDU is submitted to the first RLC entity, and the second PDCP PDU is submitted to the second RLC entity. Whether the PDCP PDU is the first or the second PDCP PDU is determined by the transmitting PDCP entity based on the SDAP indication or the SDAP routing result. The mapping relationship between the first RLC entity and the second RLC entity and the first or second PDCP PDU is configured by RRC. The PDCP PDU includes a PDCP data PDU and / or a PDCP control PDU.

[0171] Furthermore, the above-mentioned behavior 1 is not performed or is not satisfied in the case of split transmission, or the above-mentioned behavior 1 is performed when split transmission is not performed.

[0172] Behavior 2: When the transmitting PDCP entity is associated with at least two RLC entities, or the combined PDCP entity is associated with different RLC entities and transmits different PDU sets (corresponding to one QoS flow), when the MAC entity is instructed on the size / volume of the PDCP data for BSR triggering (buffer status report triggering) and buffer In the case of size (buffer size) calculation, the transmitting PDCP entity will: if the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with a first RB (the first RB is a special-identified RB, or an XR-identified RB, or a differentiated processing RB, etc.); or, if the transmitting PDCP entity is associated with at least two RLC entities, and different RLC entities associated with the transmitting PDCP entity correspond to different RBs, or, if the transmitting PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the transmitting PDCP entity, or, the joint PDCP entity is associated with different RLC entities and transmits different PDU sets (corresponding to a QoS flow), then, indicate the size / volume of the PDCP data to the MAC entity associated with the first RLC, where the first RLC is pre-configured, or network-indicated, or any one, or default, or default.

[0173] Furthermore, the above-mentioned behavior 2 is not performed or is not satisfied in the case of split transmission, or the above-mentioned behavior 2 is performed when split transmission is not performed.

[0174] Behavior 3, header compression processing:

[0175] If the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with the first RB (the first RB is a special-identified RB, or an XR-identified RB, or a differentiated processing RB, etc.); or, if the transmitting PDCP entity is associated with at least two RLC entities, and different RLCs associated with the transmitting PDCP entity correspond to different RBs, or, if the transmitting PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the transmitting PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then unified header compression processing is performed.

[0176] Alternatively, if the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the transmitting PDCP entity is associated with at least two RLC entities, and different RLCs associated with the transmitting PDCP entity correspond to different RBs, or, if the transmitting PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the transmitting PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then based on the RLC entity to which the PDCP SDU is transmitted, the PDCP entity uses the header compression protocol corresponding to different RLCs or RBs (configured for different RLCs or RBs) to perform header compression processing.

[0177] Behavior 4, encryption processing:

[0178] If the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with the first RB (the first RB is a special-identified RB, or an XR-identified RB, or a differentiated processing RB, etc.); or, if the transmitting PDCP entity is associated with at least two RLC entities, and different RLCs associated with the transmitting PDCP entity correspond to different RBs, or, if the transmitting PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the transmitting PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then unified encryption processing is performed.

[0179] Alternatively, if the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the transmitting PDCP entity is associated with at least two RLC entities, and different RLCs associated with the transmitting PDCP entity correspond to different RBs, or, if the transmitting PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the transmitting PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then based on the transmitting RLC entity of the PDCP SDU, the PDCP entity uses the encryption algorithms and / or keys (configured for different RLCs or RBs) corresponding to different RLCs or RBs to perform encryption processing.

[0180] Behavior 5: Integrity protection processing:

[0181] If the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with the first RB (the first RB is a RB with a special identifier, or an RB with an XR identifier, or an RB with a differentiated processing identifier, etc.); or, if the transmitting PDCP entity is associated with at least two RLC entities, and different RLCs associated with the transmitting PDCP entity correspond to different RBs, or, if the transmitting PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the transmitting PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then unified integrity protection processing is performed.

[0182] Alternatively, if the transmitting PDCP entity is associated with at least two RLC entities, and the transmitting PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the transmitting PDCP entity is associated with at least two RLC entities, and different RLCs associated with the transmitting PDCP entity correspond to different RBs, or, if the transmitting PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the transmitting PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then based on the transmitting RLC entity of the PDCP SDU, the PDCP entity uses the integrity algorithms and / or keys (configured for different RLCs or RBs) corresponding to different RLCs or RBs to perform integrity protection processing.

[0183] In some embodiments, the receiving end performs at least one of the following steps Step 0 to Step 2 (optionally, the order of the steps is not limited):

[0184] Step 0 (optional): If the receiving end is an access network device, the access network device configures a mapping relationship between a QoS flow and multiple paths. One QoS flow corresponds to multiple DRBs, one PDCP entity corresponds to multiple RBs, and one PDCP corresponds to multiple RLCs. The access network device indicates this configuration information to the terminal device via an RRC message.

[0185] Optionally, different DRBs or PDCPs are configured with different indications (such as I / P frames), or different DRBs or PDCPs are configured with different flags (flags, such as reliable or low reliability, or important or unimportant, or different importance levels, or different reliability levels, or different priorities).

[0186] Optionally, different RLCs are configured with different indications (such as I / P frames), or different RLCs are configured with different flags (flags, such as reliable or low reliability, or important or unimportant, or different importance levels, or different reliability levels, or different priorities).

[0187] In step 1, the PDCP receiving end performs at least one of the following actions:

[0188] Behavior 1: The receiving-end PDCP entity, or the receiving-end joint PDCP entity, performs unified buffering and / or reordering on different data based on a unified SN.

[0189] Behavior 2, decompression processing:

[0190] If the receiving-end PDCP entity is associated with at least two RLC entities, and the receiving-end PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different RLCs associated with the receiving-end PDCP entity correspond to different RBs, or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the receiving-end PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then a unified decompression process is performed.

[0191] Alternatively, if the receiving-end PDCP entity is associated with at least two RLC entities, and the receiving-end PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different RLCs associated with the receiving-end PDCP entity correspond to different RBs, or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the receiving-end PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then based on the RLC entity where the PDCP SDU is received, the PDCP entity uses the header compression protocol corresponding to different RLCs or RBs (configured for different RLCs or RBs) to perform decompression processing.

[0192] Behavior 3, decryption processing:

[0193] If the receiving-end PDCP entity is associated with at least two RLC entities, and the receiving-end PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different RLCs associated with the receiving-end PDCP entity correspond to different RBs, or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the receiving-end PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then a unified decryption process is performed.

[0194] Alternatively, if the receiving-end PDCP entity is associated with at least two RLC entities, and the receiving-end PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different RLCs associated with the receiving-end PDCP entity correspond to different RBs, or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the receiving-end PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then based on the receiving RLC entity of the PDCP SDU, the PDCP entity uses the header compression protocol corresponding to different RLCs or RBs (configured for different RLCs or RBs) to perform decryption processing.

[0195] Action 4: Integrity verification (also known as integrity authentication or integrity check):

[0196] If the receiving-end PDCP entity is associated with at least two RLC entities, and the receiving-end PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different RLCs associated with the receiving-end PDCP entity correspond to different RBs, or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the receiving-end PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then a unified integrity verification process is performed.

[0197] Alternatively, if the receiving-end PDCP entity is associated with at least two RLC entities, and the receiving-end PDCP entity is associated with a first RB (the first RB is a specially identified RB, or an XR identified RB, or a differentiated processing identified RB, etc.); or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different RLCs associated with the receiving-end PDCP entity correspond to different RBs, or, if the receiving-end PDCP entity is associated with at least two RLC entities, and different PDU sets or data are differentiated and processed with the receiving-end PDCP entity, or, the joint PDCP entity is associated with different RLCs and transmits different PDU sets (corresponding to one QoS flow), then based on the receiving RLC entity of the PDCP SDU, the PDCP entity uses the header compression protocol corresponding to different RLCs or RBs (configured for different RLCs or RBs) to perform integrity verification processing.

[0198] In Step 2, SDAP receives different data corresponding to a QoS flow from the bottom layer, specifically from different DRBs.

[0199] In some embodiments, as shown in FIG7 to FIG10 , schematic diagrams of several data processing methods are exemplified.

[0200] In Figure 7, for different data corresponding to the same QoS flow (such as different PDU sets), the transmitting PDCP entity uses a unified transmitting buffer for these different data and performs unified SN numbering. The transmitting PDCP entity uses independent header compression, independent integrity protection, and independent encryption functions for these different data, and routes the above different data to different paths, such as different RLC entities. For different data corresponding to the same QoS flow (such as different PDU sets), the receiving PDCP entity uses independent decryption, independent integrity verification, and independent header decompression functions for these different data, and uses a unified receiving buffer to reorder them according to the unified SN numbering.

[0201] In Figure 8, for different data corresponding to the same QoS flow (e.g., different PDU sets), the transmitting PDCP entity uses a unified transmitting buffer for these different data and performs unified SN numbering. The transmitting PDCP entity uses independent header compression, independent integrity protection, and independent encryption functions for these different data, and routes these different data to the same path, as if they were the same RLC entity. For different data corresponding to the same QoS flow (e.g., different PDU sets), the receiving PDCP entity uses independent decryption, independent integrity checking, and independent header decompression functions for these different data, and uses a unified receiving buffer to reorder them according to the unified SN numbering.

[0202] In Figure 9, for different data corresponding to the same QoS flow (such as different PDU sets), the transmitting PDCP entity uses a unified transmitting buffer for these different data and performs unified SN numbering. The transmitting PDCP entity uses a unified header compression function, independent integrity protection function, and independent encryption function for these different data, and routes these different data to the same path, just like the same RLC entity. For different data corresponding to the same QoS flow (such as different PDU sets), the receiving PDCP entity uses independent decryption function, independent integrity check function, and unified header decompression function for these different data, and uses a unified receiving buffer to reorder them according to the unified SN numbering.

[0203] In Figure 10, for different data corresponding to the same QoS flow (such as different PDU sets), the transmitting PDCP entity uses a unified transmitting buffer for these different data and performs unified SN numbering. The transmitting PDCP entity uses independent header compression, independent integrity protection, and independent encryption functions for these different data, and routes these different data to the same path, just like the same RLC entity. For different data corresponding to the same QoS flow (such as different PDU sets), the receiving PDCP entity uses independent decryption, independent integrity checking, and independent header decompression functions for these different data, and uses a unified receiving buffer to reorder them according to the unified SN numbering.

[0204] In some embodiments, as shown in FIG11 to FIG12 , schematic diagrams of several data processing methods are exemplified.

[0205] In Figure 11, for different data corresponding to the same QoS flow (such as different PDU sets), the sending end SDAP entity routes the different data to different paths (such as different DRBs or different PDCP entities), and the receiving end SDAP entity receives different data from the above different paths.

[0206] In Figure 12, for different data corresponding to the same QoS flow (such as different PDU sets), the sending end SDAP entity identifies the PDU sets to which the different data belong, and routes the different data belonging to different PDU sets to different paths (such as different DRBs or different PDCP entities). The receiving end SDAP entity receives different data belonging to different PDU sets from the above-mentioned different paths.

[0207] In some embodiments, as shown in FIG13 , the present application further provides a PDCP reconfiguration method, or a flowchart of a joint PDCP or joint processing entity reconfiguration method. The method may include at least one of the following steps 510 and 520 .

[0208] Step 510: When a first event is configured or satisfied, the transmitting end reconfigures the PDCP layer or PDCP entity to establish a first function for at least one path; and / or, the transmitting end reconfigures the joint PDCP or joint processing entity to establish a first function for at least one path.

[0209] Step 520, when deconfiguration or release or the first event is not satisfied, the sending end reconfigures the PDCP entity of the PDCP layer, suspends or releases the first function for at least one path; and / or, the sending end reconfigures the joint PDCP or joint processing entity, suspends or releases the first function for at least one path.

[0210] In some embodiments, the transmitting end may be a terminal device or an access network device. For example, for UL, the transmitting end is a terminal device; for DL, the transmitting end is an access network device.

[0211] In some embodiments, the first function includes at least one of the following: an encryption function, an integrity protection function, and a header compression function.

[0212] In some embodiments, establishing the first function for at least one path in step 510 includes at least one of the following actions 1 to 4:

[0213] Behavior 1: establish encryption for at least one path and use the encryption algorithm and key provided by the upper layer to perform the encryption function;

[0214] Action 2: Establish integrity protection for at least one path and use the integrity protection algorithm and key provided by the upper layer to implement the integrity protection function.

[0215] Behavior 3: Establish a header compression function for at least one path and configure the header compression function using the header compression protocol provided by the upper layer.

[0216] Action 4: Establish the at least one path or the PDCP / RLC corresponding to the path.

[0217] In some embodiments, suspending or releasing the first function of at least one path in step 520 includes at least one of the following actions 1 to 4:

[0218] Behavior 1: suspending or releasing a ciphering function for at least one path, where the ciphering function corresponds to the released RLC entity, or the released path (such as an RB), or the RB or RLC entity corresponding to the first event;

[0219] Behavior 2: Suspend or release the integrity protection function for at least one path, where the integrity protection function corresponds to the released RLC entity, or the released path (such as RB), or the RB or RLC entity corresponding to the first event;

[0220] Behavior 3: Suspend or release the header compression function for at least one path, where the header compression function corresponds to the released RLC entity, or the released path (such as RB), or the RB or RLC entity corresponding to the first event.

[0221] Action 4: Suspend or release the at least one path or the PDCP / RLC corresponding to the path.

[0222] In some embodiments, a joint PDCP entity or a joint protocol entity is associated with multiple different PDCPs. Different PDCPs correspond to different RLCs or different RBs. For example, a joint PDCP or protocol layer is associated with a first and a second PDCP, where the first PDCP corresponds to a first RLC and the second PDCP corresponds to a second RLC.

[0223] In some embodiments, the PDCP layer is associated with multiple different RLC entities, and the multiple different RLC entities correspond to multiple different paths. For example, the PDCP layer is associated with a first RLC entity and a second RLC entity, and the first RLC entity and the second RLC entity are two different RLC entities; wherein the first RLC entity corresponds to one or more paths, and the second RLC entity corresponds to one or more paths, and the paths corresponding to the first RLC entity and the second RLC entity are different.

[0224] In some embodiments, the PDCP layer is associated with multiple different RLC entities, each of which corresponds to a path. For example, the PDCP layer is associated with a first RLC entity and a second RLC entity, the first RLC entity and the second RLC entity being two different RLC entities; wherein the first RLC entity corresponds to a first path, the second RLC entity corresponds to a second path, and the first path and the second path are different paths.

[0225] Exemplarily, the PDCP layer is associated with multiple different RLC entities, each of which corresponds to multiple different paths, or each RLC entity corresponds to one path. In other words, the PDCP layer is associated with multiple different paths. The at least one path in steps 510 and / or 520 is: all of the multiple different paths, or a portion of the multiple different paths.

[0226] For example, the PDCP layer associates a first RLC entity with a second RLC entity, and the first RLC entity and the second RLC entity are two different RLC entities; wherein the first RLC entity corresponds to a first path, the second RLC entity corresponds to a second path, and the first path and the second path are different paths. If a first function is established for one of the paths, or if the first function is suspended or released for one of the paths, it means that a path has been established, and another path is currently being added or released, that is, there is a default or existing path in the PDCP entity. If a first function is established for the first path and the second path, or if the first function is suspended or released for the first path and the second path, it means that the first function is established or released for all paths corresponding to the PDCP entity together.

[0227] In some embodiments, the first event includes at least one of the following situations 1-7:

[0228] Case 1: a QoS flow corresponds to multiple paths, or a specific QoS flow corresponds to multiple paths;

[0229] Case 2: Configure different data corresponding to QoS flows for independent processing and / or joint processing;

[0230] Case 3: Multiple paths are associated with one PDCP entity, and different paths correspond to different identifiers, including at least one of the following: a special identifier (such as I frame or P frame, or different importance, or different priority, or different dependency, or different association), an XR identifier, and a differentiated processing identifier;

[0231] Case 4: multiple PDCP layers or entities are associated with the protocol layer or entity for joint processing;

[0232] Case 5: The PDCP layer or entity is associated with multiple different RLC entities, and the PDCP layer is associated with a target path, which includes at least one of the following: a path with a special identifier, a path with an XR identifier, and a path with a differentiated processing identifier;

[0233] Case 6: The PDCP layer or entity is associated with multiple different RLC entities, and different RLC entities correspond to different paths;

[0234] In case 7, the PDCP layer or entity is associated with multiple different RLC entities, and the PDCP layer processes different data for different RLC entities.

[0235] In some embodiments, as shown in FIG14 , the present application further provides a PDCP reconfiguration method, or a flowchart of a joint PDCP or joint processing entity reconfiguration method. The method may include at least one of the following steps 610 and 620 .

[0236] Step 610: When a first event is configured or satisfied, the transmitting end PDCP layer is reconfigured, and / or the protocol layer or entity of the joint processing is reconfigured.

[0237] Step 620: When deconfiguration or release occurs or the first event is not satisfied, the PDCP layer at the transmitting end deconfigures or suspends processing, and / or the protocol layer or entity of the joint processing deconfigures or suspends processing.

[0238] In some embodiments, the transmitting end may be a terminal device or an access network device. For example, for UL, the transmitting end is a terminal device; for DL, the transmitting end is an access network device.

[0239] In some embodiments, the protocol layer or entity performing the joint processing is configured to perform the aforementioned joint processing on different data corresponding to the same QoS flow, and optionally also to perform the aforementioned independent processing on different data corresponding to the same QoS flow. Optionally, the protocol layer or entity performing the joint processing may be a PDCP layer or PDCP entity performing the joint processing.

[0240] In some embodiments, the first event includes at least one of the following situations 1-7:

[0241] Case 1: a QoS flow corresponds to multiple paths, or a specific QoS flow corresponds to multiple paths;

[0242] Case 2: Configure different data corresponding to QoS flows for independent processing and / or joint processing;

[0243] Case 3: Multiple paths are associated with one PDCP entity, and different paths correspond to different identifiers, including at least one of the following: a special identifier (such as I frame or P frame, or different importance, or different priority, or different dependency, or different association), an XR identifier, and a differentiated processing identifier;

[0244] Case 4: multiple PDCP layers or entities are associated with the protocol layer or entity for joint processing;

[0245] Case 5: The PDCP layer or entity is associated with multiple different RLC entities, and the PDCP layer is associated with a target path, which includes at least one of the following: a path with a special identifier, a path with an XR identifier, and a path with a differentiated processing identifier;

[0246] Case 6: The PDCP layer or entity is associated with multiple different RLC entities, and different RLC entities correspond to different paths;

[0247] In case 7, the PDCP layer or entity is associated with multiple different RLC entities, and the PDCP layer processes different data for different RLC entities.

[0248] The technical solutions provided in the embodiments of Figures 13 and 14 are applicable to situations where different data (such as different PDU sets, different coding slices, different frames, etc.) are mapped to the same QoS flow. The above-mentioned different data (such as different PDU sets) can be data of different importance, or data with different associations, or data with different dependencies, or data with different priorities. Through the technical solution of this embodiment, a modification of the PDCP function through PDCP reconfiguration is provided, thereby supporting the independent processing and / or joint processing of different data by PDCP as described above.

[0249] In some embodiments, as shown in FIG15 , the present application further provides a flowchart for configuring or changing the mapping relationship between QoS flows and paths. The method may include the following step 710 .

[0250] Step 710: Configure or change the mapping relationship between the QoS flow and the path, and, when the first event is configured or satisfied, perform at least one of the following actions 1 to 10:

[0251] Action 1: suspend or release the first path among the multiple paths corresponding to the QoS flow;

[0252] Action 2: suspend or release a first function of a first path among the multiple paths corresponding to the QoS flow;

[0253] Action 3: suspend or release the PDCP entity corresponding to the first path among the multiple paths corresponding to the QoS flow;

[0254] Action 4: suspend or release the RLC entity corresponding to the first path among the multiple paths corresponding to the QoS flow;

[0255] Action 5: Reset the MAC entity corresponding to the first path among the multiple paths corresponding to the QoS flow;

[0256] Behavior 6: Recover or establish a second path for the QoS flow;

[0257] Behavior 7, a first function of restoring or establishing a second path for the QoS flow;

[0258] Behavior 8: Recover or establish the PDCP entity corresponding to the second path for the QoS flow;

[0259] Behavior 9: Recover or establish the RLC entity corresponding to the second path for the QoS flow;

[0260] Behavior 10: Configure a MAC entity corresponding to the second path for the QoS flow.

[0261] In some embodiments, the first path is a default path, or a path determined based on a stored mapping relationship between a QoS flow and a path. Taking the example of multiple DRBs corresponding to the same QoS flow, the first path can be a first DRB, which can be a default DRB or a DRB determined according to the stored QoS flow to DRB mapping rule.

[0262] In some embodiments, the second path is a changed path determined based on a configured, updated, or indicated mapping relationship between a QoS flow and a path. For example, taking the case where the same QoS flow corresponds to multiple DRBs, the second path may be a second DRB, which may be a changed DRB corresponding to a configured, updated, or indicated QoS flow to DRB mapping rule.

[0263] In some embodiments, the first path is all or part of the multiple paths corresponding to the same QoS flow. Taking the case where the same QoS flow corresponds to multiple DRBs as an example, the first DRB can be one or more DRBs among the multiple DRBs. Optionally, a DRB is an additional DRB, or a DRB whose mapping relationship needs to be modified. Optionally, the multiple DRBs are all DRBs corresponding to the PDCP entity.

[0264] In some embodiments, the second path is all or part of the multiple paths corresponding to the same QoS flow. Taking the case where the same QoS flow corresponds to multiple DRBs as an example, the second DRB can be one or more DRBs among the multiple DRBs. Optionally, a DRB is an additional DRB, or a DRB whose mapping relationship needs to be modified. Optionally, the multiple DRBs are all DRBs corresponding to the PDCP entity.

[0265] In some embodiments, the first event includes at least one of the following situations 1-7:

[0266] Case 1: a QoS flow corresponds to multiple paths, or a specific QoS flow corresponds to multiple paths;

[0267] Case 2: Configure different data corresponding to QoS flows for independent processing and / or joint processing;

[0268] Case 3: Multiple paths are associated with one PDCP entity, and different paths correspond to different identifiers, including at least one of the following: a special identifier (such as I frame or P frame, or different importance, or different priority, or different dependency, or different association), an XR identifier, and a differentiated processing identifier;

[0269] Case 4: multiple PDCP layers or entities are associated with the protocol layer or entity for joint processing;

[0270] Case 5: The PDCP layer or entity is associated with multiple different RLC entities, and the PDCP layer is associated with a target path, which includes at least one of the following: a path with a special identifier, a path with an XR identifier, and a path with a differentiated processing identifier;

[0271] Case 6: The PDCP layer or entity is associated with multiple different RLC entities, and different RLC entities correspond to different paths;

[0272] In case 7, the PDCP layer or entity is associated with multiple different RLC entities, and the PDCP layer processes different data for different RLC entities.

[0273] In some embodiments, for the above-mentioned behavior 2, pausing or releasing a first function of a first path among the multiple paths corresponding to the QoS flow, the first function includes at least one of the following: an encryption function, an integrity protection function, and a header compression function. Optionally, pausing or releasing the first function of the first path among the multiple paths corresponding to the QoS flow includes at least one of the following behaviors 2-1 to 2-4:

[0274] Action 2-1: suspend or release the encryption function of the first path, where the encryption function corresponds to the released RLC entity, or the released path (such as RB), or the RB or RLC entity corresponding to the first event;

[0275] Action 2-2: suspend or release the integrity protection function of the first path, where the integrity protection function corresponds to the released RLC entity, or the released path (such as RB), or the RB or RLC entity corresponding to the first event;

[0276] Action 2-3: suspend or release the header compression function of the first path, where the header compression function corresponds to the released RLC entity, or the released path (such as RB), or the RB or RLC entity corresponding to the first event.

[0277] Action 2-4: suspend or release the first path or the PDCP / RLC corresponding to the first path, etc.

[0278] In some embodiments, for the above-mentioned behavior 7, the first function of restoring or establishing the second path for the QoS flow includes at least one of the following: an encryption function, an integrity protection function, and a header compression function. Optionally, the first function of restoring or establishing the second path for the QoS flow includes at least one of the following behaviors 7-1 to 7-4:

[0279] Behavior 7-1: Establish encryption for the second path and use the encryption algorithm and key provided by the upper layer to perform the encryption function;

[0280] Action 7-2: Establish integrity protection for the second path and implement the integrity protection using the integrity protection algorithm and key provided by the upper layer.

[0281] Behavior 7-3 establishes a header compression function for the second path and configures the header compression function using the header compression protocol provided by the upper layer.

[0282] Action 7-4: Establish the second path or the PDCP / RLC corresponding to the second path, etc.

[0283] In some embodiments, for behavior 3 above, the PDCP entity corresponding to the first path among the multiple paths corresponding to the QoS flow is first suspended or released. Furthermore, when the network indicates to suspend or release the first path among the multiple paths corresponding to the QoS flow, the terminal device then suspends or releases the first path. Alternatively, the above-described behavior of suspending or releasing the first path is performed when an SDAP end marker PDU is sent.

[0284] In some embodiments, configuring or changing the mapping relationship between QoS flows and paths includes at least one of the following situations 1-2:

[0285] Case 1: RRC configures an UL QoS flow to DRB mapping rule for a QoS flow.

[0286] Case 2, each received DL SDAP data PDU with RDI set to 1 (the RDI of each received DL SDAP data PDU is set to 1).

[0287] The technical solution of this embodiment is applicable to the situation where different data (such as different PDU sets, different coding slices, different frames, etc.) are mapped to the same QoS flow. The above-mentioned different data (such as different PDU sets) can be data of different importance, or data with different associations, or data with different dependencies, or data with different priorities. Through the technical solution of this embodiment, a method for establishing or releasing the PDCP function is given when the QoS flow and DRB mapping are configured or changed, thereby supporting the PDCP to perform the independent processing and / or joint processing described above for different data.

[0288] Please refer to Figure 16, which shows a flow chart of a data processing method provided by another embodiment of the present application. The method may include the following steps:

[0289] Step 810: perform measurement statistics on the PDU set to obtain a first result.

[0290] The applicable scenarios of this embodiment include at least one of the following scenarios 1 to 4:

[0291] Scenario 1: Applicable to QoS flows or services with QoS requirements at the PDU aggregate granularity.

[0292] Scenario 2: Based on PSDB (PDU-Set Delay Budget) and / or PSER (PDU-Set Error Rate) indication or configuration;

[0293] Scenario 3: Activate or use PDU aggregate granularity L2 (Layer 2) measurement and / or reporting;

[0294] Scenario 4 is for the case where PSDB and / or PSER measurement and / or reporting are activated or used.

[0295] In some embodiments, for PSER, the first result includes a PDU aggregate loss rate, where the PDU aggregate loss rate indicates the ratio of the number of lost PDU aggregates to the total number of sent PDU aggregates. By measuring the PDU aggregate loss rate of the Uu interface between the terminal device and the access network device, it can be used for OAM (Operation Administration and Maintenance) performance observability and / or for MDT (Minimization of drive-tests) QoS verification.

[0296] In some embodiments, the measurement statistics of the PDU aggregate loss rate meet at least one of the following conditions 1 to 5:

[0297] Case 1: The PDU set loss rate is measured and counted at the Uu port.

[0298] Case 2: The PDU aggregate loss rate is obtained by RLC layer measurement statistics;

[0299] Case 3: The PDU aggregate loss rate is measured and counted for each path (e.g., per DRB) of each terminal device (e.g., per UE);

[0300] Case 4: The PDU aggregate loss rate is measured and counted for the downlink;

[0301] In case 5, the PDU aggregate loss rate is obtained by measuring and counting the access network equipment.

[0302] In some embodiments, for the downlink of the Uu interface, the definition of the PDU aggregate loss rate of each DRB of each UE is as shown in the following Table 1:

[0303] Table 1: Definition for PDU set Uu Loss Rate in the DL per DRB per UE

[0304] (Definition of the PDU aggregate loss rate for each DRB per UE for the Uu downlink)

[0305]

[0306] NOTE 1: PDU set packet loss is expected to be upper bounded by the PSER (PDU-set error rate, as defined in TS 23.501) of the DRB. The statistical accuracy of an individual PDU set loss rate measurement result is dependent on how many PDU sets or packets have been received, and thus the time for the measurement.

[0307] NOTE 2: The granularity for PDU set loss rate measurement is per DRB per UE.

[0308] Table 2: Parameter description for PDU set Uu Loss Rate in the DL per DRB per UE

[0309] (Parameter description of the PDU aggregate loss rate of each DRB per UE for the downlink of the Uu interface)

[0310]

[0311] In some embodiments, for PSDB, the first result includes: PDU set delay, where the PDU set delay is used to indicate an average delay in processing PDUs in the PDU set.

[0312] In some embodiments, the measurement statistics of the PDU aggregate delay meet at least one of the following conditions 1 to 4:

[0313] Case 1: PDU aggregate delay includes access network delay and / or core network delay;

[0314] Case 2: PDU aggregate delay is measured and counted for each path of each terminal device;

[0315] Case 3: PDU aggregation delay is measured and counted for the downlink;

[0316] In case 4, the PDU aggregation delay is measured and counted for the uplink.

[0317] Exemplarily, the measurement statistics of the PDU aggregate delay of the downlink are performed for each terminal device and each path.

[0318] Exemplarily, the measurement statistics of the uplink PDU aggregate delay are performed for each terminal device and each path.

[0319] In some embodiments, the measurement statistics of uplink PDU aggregate delay include at least one of the following examples 1 to 5. Example 1 is performed by the terminal device, and examples 2 to 5 are performed by the access network device.

[0320] Example 1: The PDU aggregation delay is the queuing delay of the PDU aggregation at the PDCP layer of the transmitting end, and the queuing delay is obtained by measuring and counting the PDCP layer of the transmitting end.

[0321] Optionally, for UL, the terminal device measures the queuing delay of the PDU set at the PDCP layer. The purpose of this measurement is to be used for QoS monitoring and / or QoS verification of MDT.

[0322] In some embodiments, configuration and / or reporting of queuing delay measurement includes at least one of the following:

[0323] 1. Configure the delay configuration information corresponding to the PDU set. The delay configuration information is used to indicate the measurement and / or reporting of the queuing delay corresponding to the PDU set. Exemplarily, configure the delay value config of the PDU set. The delay value config is the delay configuration information.

[0324] 2. The delay configuration information corresponding to the PDU set is included in the reporting configuration information; illustratively, the delay value config of the PDU set is included in ReportConfigNR.

[0325] 3. The reporting configuration information including the delay configuration information corresponding to the PDU set is included in the measurement configuration information; illustratively, ReportConfigNR including the delay value config corresponding to the PDU set is included in MeasConfig.

[0326] 4. The delay configuration information corresponding to the PDU set configuration indicates that the reporting type of the queuing delay is periodic reporting; illustratively, the reporting type of the delay value config of the PDU set is periodic reporting, which can be further included in PeriodicalReportConfig.

[0327] 5. The queuing delay corresponding to the PDU set is included in the measurement result and reported; illustratively, the delay value (queuing delay) of the PDU set is included in the MeasResults report.

[0328] 6. The measurement results include the queuing delay corresponding to the PDU set of one or more paths; for example, MeasResults includes the delay value of the PDU set of one or more DRBs. For example:

[0329]

[0330] 7. The delay configuration information corresponding to the PDU set includes configuration information for one or more paths; illustratively, the delay value config of the PDU set may include configuration for one or more DRBs. For example, it is used to indicate the DRB IDs used by the UE to provide results of UL PDCP PDU set Delay value per DRB measurement (DRB ID used by the UE to provide measurement results of the UL PDCP PDU set delay value per DRB for each DRB). For example:

[0331] UL-PduSetDelayValueConfig::= SEQUENCE{

[0332] delay-DRBlist SEQUENCE(SIZE(1..maxDRB))OF DRB-Identity

[0333] }

[0334] In some embodiments, the above 2 satisfies at least one of the following:

[0335] 2-1. The reporting configuration information has a corresponding reporting configuration identifier; illustratively, ReportConfigNR has a corresponding ReportConfigId.

[0336] 2-2. The reporting configuration identifier corresponds to the measurement identifier; for example, ReportConfigId corresponds to a MeasId.

[0337] 2-3. The measurement identifier is associated with the measurement result corresponding to the measurement configuration information; illustratively, MeasId is associated with MeasResults, which is used to report the measurement result of MeasConfig.

[0338] In some embodiments, for the uplink, the average delay of the UL PDU set for each DRB of each UE (ie, the above-mentioned queuing delay) is defined as shown in Table 3 below:

[0339] Table 3: Definition for UL PDCP PDU set Average Delay per DRB per UE

[0340] (Definition of the average delay of the UL PDCP PDU aggregate per DRB per UE)

[0341]

[0342]

[0343] Table 4: Parameter description for UL PDCP PDU set Average Delay per DRB per UE

[0344] (Parameter description of the average delay of the UL PDCP PDU aggregate for each DRB of each UE)

[0345]

[0346] Example 2: The PDU aggregate delay is the air interface transmission delay of the PDU aggregate, which is obtained by measuring and counting the air interface transmission delay at the MAC layer of the receiving end.

[0347] Optionally, for UL, the air interface transmission delay of the PDU set is measured by the access network device at the MAC layer. The measurement is used for at least one of the following: OAM performance observability, QoS monitoring, and MDT QoS verification.

[0348] In some embodiments, the measurement configuration and / or reporting of air interface transmission delay includes at least one of the following:

[0349] 1. Measure the air interface transmission delay for each path of each terminal device;

[0350] 2. The MAC layer performs the measurement;

[0351] 3. The measurement is the transmission time of the grant corresponding to the transmission of a PDU set. The transmission time of the grant corresponding to the transmission of a PDU set refers to the average time (arithmetic mean) required to successfully receive a transport block at the UL transmission time specified in a scheduling grant for a PDU set;

[0352] 4. The authorization for which the measurement is targeted is that corresponding to the first packet, the last packet, or all packets of the PDU set.

[0353] Example 3: The PDU aggregation delay is the processing delay of the PDU aggregation at the RLC layer of the receiving end, and the processing delay is obtained by measuring and statistics of the RLC layer of the receiving end.

[0354] Optionally, for the UL, the access network equipment measures the processing delay of the PDU set at the RLC layer. This measurement is used for at least one of the following: OAM performance observability, QoS monitoring, and MDT QoS verification. Optionally, the measurement is performed by the RLC layer.

[0355] In some embodiments, for the uplink, the average RLC PDU aggregate delay for each DRB of each UE (that is, the processing delay of the above PDU aggregate at the RLC layer of the receiving end) is defined as shown in Table 5 below:

[0356] Table 5: Definition for Average RLC PDU set delay in the UL per DRB per UE

[0357] (Definition of average RLC PDU aggregate delay per DRB per UE for UL)

[0358]

[0359]

[0360] Table 6: Parameter description for Average RLC packet delay in the UL per DRB per UE

[0361] (For UL, parameter description of average RLC PDU aggregate delay per DRB per UE)

[0362]

[0363] Example 4: The PDU aggregation delay is the reordering delay of the PDU aggregation at the PDCP layer of the receiving end, and the reordering delay is obtained by measuring and statistics of the PDCP layer of the receiving end.

[0364] Optionally, for the UL, the access network equipment measures the reordering delay of the PDU aggregate at the PDCP layer. This measurement is used for at least one of the following: OAM performance observability, QoS monitoring, and QoS verification of MDT. Optionally, the measurement is performed by the PDCP layer.

[0365] In some embodiments, for the uplink, the average PDCP reordering delay for each DRB of each UE (that is, the reordering delay of the above-mentioned PDU set at the PDCP layer of the receiving end) is defined as shown in Table 7 below:

[0366] Table 7: Definition for Average PDCP re-ordering delay in the UL per DRB per UE

[0367] (Definition of average PDCP reordering delay per DRB per UE for UL)

[0368]

[0369] Table 8: Parameter description for Average PDCP re-ordering delay in the UL per DRB per UE

[0370] (For UL, parameter description of average PDCP reordering delay per DRB per UE)

[0371]

[0372]

[0373] Example 5: The PDU aggregate delay for uplink on the F1-U interface uses the same metric as the PDU aggregate delay for downlink on the F1-U interface.

[0374] The technical solution provided by this embodiment realizes measurement statistics with PDU sets as the granularity, and can be used for QoS monitoring and / or QoS verification at the granularity of PDU sets.

[0375] In some embodiments, energy consumption has become a significant component of operators' operating costs. According to reports from relevant organizations, mobile network energy costs account for approximately 23% of operators' total costs. Most energy consumption comes from radio access networks, particularly active antenna units (AAUs), while data centers and fiber optic transmission account for only a smaller share. Power consumption consists of two components: dynamic consumption (e.g., consumption during data transmission / reception) and static consumption (e.g., consumption to maintain the operation of necessary radio access equipment, even when there is no ongoing data transmission / reception).

[0376] Therefore, energy conservation research for networks and UEs should not only evaluate the potential network energy savings but also assess and balance the impact on network and user performance. For example, the research should not significantly impact certain KPIs (Key Performance Indicators), such as spectrum efficiency, capacity, user perceived throughput (UPT), latency, UE power consumption, complexity, handover performance, call drop rate, and initial access performance.

[0377] In the related art, some solutions are mainly provided for UE energy saving, but little consideration is given to network energy saving.

[0378] In some embodiments, when the access network device or cell is in the first state, the terminal device sends or receives signals or data according to the instructions of the access network device.

[0379] Optionally, the first state includes at least one of the following: a closed state and a power-saving state, wherein the closed state refers to a state in which no service is provided or a power-off state.

[0380] Optionally, the indication is sent by the access network device to the terminal device via an RRC message, DCI, or MAC CE. The above RRC message may be system information or a dedicated RRC message.

[0381] Optionally, the indication information is for a cell (cell), a terminal group (UE-group), or a terminal (UE).

[0382] Optionally, if it is UE-group common, the indication indicates the UE-group identifier and / or cell identifier.

[0383] Optionally, if it is cell-specific, the indication indicates a cell identifier.

[0384] Optionally, if it is UE-specific, the indication carries a UE identifier, or a UE-specific RNTI (such as C-RNTI) is used.

[0385] Optionally, the indication information indicates one of the following (the following is only an example and may also be in other forms, used to indicate which specific signaling or channels are transmitted or not transmitted):

[0386] 1: Common signaling, such as at least one of SSB, SIB, and Cell-specific RS;

[0387] 2: Common signaling + UE-specific information (UE-specific info), such as RS and / or data;

[0388] 3: Common signaling + UE-specific RS;

[0389] 4: Common signaling + UE-specific data transmission;

[0390] 5: UE-specific information;

[0391] 6: Common signaling + UE-specific information + RACH;

[0392] 7: Common signaling + UE-specific RS + RACH;

[0393] 8: Public signaling + UE-specific data transmission + RACH;

[0394] 9: UE-specific information + RACH;

[0395] 10: Common signaling + RACH.

[0396] Optionally, the terminal device determines which signals or data can be transmitted based on the indication information, and / or transmits the indicated signals or data.

[0397] In some embodiments, an access network device sends an indication message to a terminal device, the indication message being used to instruct or configure the terminal device to report auxiliary information. Optionally, the indication message is a SIB message. Optionally, the indication message is cell-specific or UE-group common. Optionally, the UE auxiliary information is used to report energy-saving related information. Specifically, it includes at least one of the following:

[0398] 1. If the UE-group is common, the above indication information indicates the UE-group identifier and / or cell identifier;

[0399] 2. If it is cell-specific, the cell identifier is indicated in the above indication information;

[0400] 3. The UE auxiliary information reporting indication or configuration includes at least one of the following: a reporting type, a reporting prohibition duration or timer, and a reporting enable / disable indication. The reporting type indicates the auxiliary information content reported by the UE (e.g., service information, recommended configuration information, mobility information, UE buffer information, etc.).

[0401] 4. The UE reports the assistance information using a UL RRC message according to the UE assistance information reporting instruction or configuration indicated by the instruction information. Optionally, the UL RRC message may be a UE assistance information message (eg, a UEAssistanceInformation message).

[0402] 5. The UE reports the energy-saving auxiliary information and / or starts the energy-saving auxiliary information reporting timer in at least one of the following situations (optionally, the energy-saving auxiliary information can be reported only when the timer is not running):

[0403] If the UE has not sent relevant assistance information (e.g., UEAssistanceInformation message) since being configured to report; or if the current value is different from the value indicated in the last transmission of relevant assistance information (e.g., UEAssistanceInformation message).

[0404] 6. The energy-saving information includes at least one of the following: service information, recommended configuration information, mobility information, UE buffer information, etc.

[0405] Solution 3: If the UE is a UE that supports network energy saving, or the access network device instructs the UE to perform UE energy saving operations, in the case of BWP switching, or in the case of BWP deactivation, the UE suspends the CG (Configured Grant) type 2 and / or SPS associated with the BWP before the switching, the deactivated BWP, or the inactive BWP. Optionally, on the activated BWP or the BWP after the switching, the UE can perform reporting or feedback for the BWP before the switching, the deactivated BWP, or the inactive BWP, such as reporting confirmation MAC CE and / or Multiple Entry Configured Grant confirmation MAC CE for the BWP before the switching, the deactivated BWP, or the inactive BWP.

[0406] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0407] Please refer to Figure 17, which shows a block diagram of a data processing device provided by one embodiment of the present application. The device has the functions of implementing the above-mentioned method examples. The functions can be implemented by hardware or by hardware executing corresponding software. The device can be a network device or can be installed in a network device. As shown in Figure 17, the device 170 can include: a data processing module 171.

[0408] The data processing module 171 is configured to independently process and / or jointly process different data corresponding to the same QoS flow.

[0409] In some embodiments, the different data correspond to different paths.

[0410] In some embodiments, when the network device is a transmitting end, the independent processing includes at least one of the following:

[0411] routing the different data to different paths;

[0412] identifying the different data;

[0413] Different first functions are used for the different data.

[0414] In some embodiments, the sending end is an SDAP layer, and routing the different data to different paths includes: routing the different data to different PDCP entities; or routing the different data to different DRBs.

[0415] In some embodiments, the transmitting end is a PDCP layer, and routing the different data to different paths includes: routing the different data to different radio link control RLC entities; or routing the different data to different logical channels.

[0416] In some embodiments, identifying the different data includes at least one of the following:

[0417] Identifying the different data according to a protocol data unit (PDU) set corresponding to the data;

[0418] Identifying the different data according to a start identifier and / or an end identifier of the PDU set;

[0419] The different data are identified according to attributes of the data, where the attributes include at least one of the following: type, importance, relevance, priority, and dependency.

[0420] In some embodiments, when the network device is a transmitting end, the joint processing includes at least one of the following: using a unified sequence number SN for numbering the different data; using a unified first function for the different data.

[0421] In some embodiments, when the network device is a receiving end, the independent processing includes at least one of the following: receiving the different data from different paths; and using different second functions for the different data.

[0422] In some embodiments, the receiving end is an SDAP layer, and the receiving of the different data from different paths includes: receiving the different data from different PDCP entities; or receiving the different data from different DRBs.

[0423] In some embodiments, the receiving end is a PDCP layer, and the receiving of the different data from different paths includes: receiving the different data from different RLC entities; or receiving the different data from different logical channels.

[0424] In some embodiments, when the network device is a receiving end, the joint processing includes at least one of the following: reordering the different data according to a unified SN; and using a unified second function for the different data.

[0425] In some embodiments, the joint processing includes at least one of the following: performing joint processing between protocol layers or entities for the joint processing of the different data; performing joint processing between protocol layers or entities for data routed to different paths.

[0426] In some embodiments, the protocol layer or entity is a PDCP protocol layer or a PDCP entity; or, the protocol layer or entity is a joint protocol layer or a joint entity corresponding to the PDCP protocol layer or PDCP entity.

[0427] In some embodiments, the joint processing is performed by the transmitting end and / or the receiving end.

[0428] In some embodiments, when the network device is a transmitting end, as shown in FIG17 , the apparatus 170 further includes: a reconfiguration module 172 .

[0429] The reconfiguration module 172 is used to reconfigure the PDCP layer or PDCP entity to establish the first function for at least one path when the first event is configured or satisfied; and / or, reconfigure the joint PDCP or joint processing entity to establish the first function for at least one path; and / or, when the first event is deconfigured or released or not satisfied, reconfigure the PDCP entity of the PDCP layer to suspend or release the first function for at least one path; and / or, reconfigure the joint PDCP or joint processing entity to suspend or release the first function for at least one path.

[0430] And / or, the reconfiguration module 172 is used to reconfigure the PDCP layer of the transmitting end and / or reconfigure the protocol layer or entity of the joint processing when the first event is configured or satisfied; and / or, when the PDCP layer of the transmitting end is deconfigured or released or the first event is not satisfied, and / or, the protocol layer or entity of the joint processing is deconfigured or suspended.

[0431] In some embodiments, the PDCP layer is associated with multiple different RLC entities, each of which corresponds to multiple different paths; or the PDCP layer is associated with multiple different RLC entities, each of which corresponds to one path. The at least one path is: all of the multiple different paths, or some of the multiple different paths.

[0432] In some embodiments, the data processing module 171 is further configured to configure or change the mapping relationship between the QoS flow and the path, and, when the first event is configured or satisfied, perform at least one of the following actions:

[0433] pausing or releasing a first path among the multiple paths corresponding to the QoS flow;

[0434] pausing or releasing a first function of a first path among the multiple paths corresponding to the QoS flow;

[0435] suspending or releasing a PDCP entity corresponding to a first path among multiple paths corresponding to the QoS flow;

[0436] pausing or releasing an RLC entity corresponding to a first path among multiple paths corresponding to the QoS flow;

[0437] Resetting a MAC entity corresponding to a first path among multiple paths corresponding to the QoS flow;

[0438] Restoring or establishing a second path for the QoS flow;

[0439] a first function of restoring or establishing a second path for the QoS flow;

[0440] Restoring or establishing a PDCP entity corresponding to a second path for the QoS flow;

[0441] Restoring or establishing an RLC entity corresponding to a second path for the QoS flow;

[0442] A MAC entity corresponding to the second path is configured for the QoS flow.

[0443] In some embodiments, the first path is a default path, or a path determined based on a stored mapping relationship between the QoS flow and the path; and / or, the second path is a changed path determined based on a configured, updated or indicated mapping relationship between the QoS flow and the path.

[0444] In some embodiments, the first path is all or part of a plurality of paths corresponding to the QoS flow; and / or the second path is all or part of a plurality of paths corresponding to the QoS flow.

[0445] In some embodiments, the first event includes at least one of the following:

[0446] One QoS flow corresponds to multiple paths, or a specific QoS flow corresponds to multiple paths;

[0447] Configure different data corresponding to QoS flows for independent processing and / or joint processing;

[0448] Multiple paths are associated with one PDCP entity, and different paths correspond to different identifiers, where the identifier includes at least one of the following: a special identifier, an extended reality (XR) identifier, and a differentiated processing identifier;

[0449] A protocol layer or entity associated with multiple PDCP layers or entities for joint processing;

[0450] The PDCP layer or entity is associated with a plurality of different RLC entities, and the PDCP layer is associated with a target path, the target path including at least one of the following: a path with a special identifier, a path with an XR identifier, and a path with a differentiated processing identifier;

[0451] The PDCP layer or entity is associated with multiple different RLC entities, and the different RLC entities correspond to different paths;

[0452] The PDCP layer or entity is associated with a plurality of different RLC entities, and the PDCP layer processes the different data differently for the different RLC entities.

[0453] In some embodiments, the joint processing is for multiple different PDCP entities, and the different data corresponds to the different PDCP entities; or, the joint PDCP layer or the joint PDCP entity corresponds to multiple different PDCP entities, and the different data corresponds to the different PDCP entities.

[0454] In some embodiments, the different PDCP entities have a binding relationship or a joint processing relationship.

[0455] In some embodiments, independent processing and / or joint processing of the different data are performed in the same PDCP entity.

[0456] In some embodiments, the PDCP entity reuses the DAPS architecture.

[0457] In some embodiments, the first function includes at least one of the following: an integrity protection function, an encryption function, and a header compression function.

[0458] In some embodiments, the second function includes at least one of the following: an integrity authentication function, a decryption function, and a decompression function.

[0459] In some embodiments, the path is RB.

[0460] In some embodiments, the different data correspond to different PDU sets, or the different data correspond to PDU sets with different attributes.

[0461] In some embodiments, the different data have different attributes, and the attributes include at least one of the following: type, importance, relevance, priority, and dependency.

[0462] Please refer to Figure 18, which shows a block diagram of a data processing device provided by another embodiment of the present application. This device has the functions of implementing the above-mentioned method examples. These functions can be implemented by hardware or by hardware executing corresponding software. This device can be a network device or can be installed in a network device. As shown in Figure 18, the device 180 can include: a measurement statistics module 181.

[0463] The measurement and statistics module 181 is configured to perform measurement and statistics on a PDU set to obtain a first result.

[0464] In some embodiments, the first result includes: a PDU set loss rate, where the PDU set loss rate is used to indicate the ratio of the number of lost PDU sets to the total number of sent PDU sets.

[0465] In some embodiments, the measurement statistics of the PDU aggregate loss rate meet at least one of the following conditions:

[0466] The PDU set loss rate is measured and counted for the Uu interface.

[0467] The PDU aggregate loss rate is obtained by measuring and counting the radio link control RLC layer;

[0468] The PDU aggregate loss rate is measured and counted for each path of each terminal device;

[0469] The PDU aggregate loss rate is measured and counted for a downlink;

[0470] The PDU aggregate loss rate is obtained by measurement and statistics of access network equipment.

[0471] In some embodiments, the first result includes: a PDU set delay, where the PDU set delay is used to indicate an average delay in processing PDUs in the PDU set.

[0472] In some embodiments, the measurement statistics of the PDU aggregate delay meet at least one of the following conditions:

[0473] The PDU aggregate delay includes the delay of the access network part and / or the delay of the core network part;

[0474] The PDU aggregate delay is measured and counted for each path of each terminal device;

[0475] The PDU aggregate delay is measured and counted for the downlink;

[0476] The PDU aggregate delay is measured and counted for uplink.

[0477] In some embodiments, the PDU aggregation delay is a queuing delay of the PDU aggregation at a Packet Data Convergence Protocol (PDCP) layer at the transmitting end, and the queuing delay is obtained by measuring and statistically analyzing the PDCP layer at the transmitting end.

[0478] In some embodiments, the measurement configuration and / or reporting of the queuing delay includes at least one of the following:

[0479] Delay configuration information corresponding to the PDU set is configured, where the delay configuration information is used to indicate measurement and / or reporting of a queuing delay corresponding to the PDU set;

[0480] The delay configuration information corresponding to the PDU set is included in the reporting configuration information;

[0481] Reporting configuration information including delay configuration information corresponding to the PDU set, included in the measurement configuration information;

[0482] The delay configuration information corresponding to the PDU set configuration indicates that the reporting type of the queuing delay is periodic reporting;

[0483] The queuing delay corresponding to the PDU set is included in the measurement result report;

[0484] The measurement results include the queuing delay corresponding to the PDU set of one or more paths;

[0485] The delay configuration information corresponding to the PDU set includes configuration information for one or more paths.

[0486] In some embodiments, the method satisfies at least one of the following:

[0487] The reporting configuration information has a corresponding reporting configuration identifier;

[0488] The reporting configuration identifier corresponds to the measurement identifier;

[0489] The measurement identifier is associated with the measurement result corresponding to the measurement configuration information.

[0490] In some embodiments, the PDU aggregate delay is an air interface transmission delay of the PDU aggregate, and the air interface transmission delay is obtained by measuring and counting the media access control MAC layer of the receiving end.

[0491] In some embodiments, the PDU set delay is a processing delay of the PDU set at the RLC layer of the receiving end, and the processing delay is obtained by measuring and statistics of the RLC layer of the receiving end.

[0492] In some embodiments, the PDU set delay is a reordering delay of the PDU set at the PDCP layer of the receiving end, and the reordering delay is obtained by measuring and statistics of the PDCP layer of the receiving end.

[0493] In some embodiments, the PDU aggregate delay for uplink on the F1-U interface and the PDU aggregate delay for downlink on the F1-U interface use the same metric.

[0494] It should be noted that, when the device provided in the above embodiment realizes its function, it only uses the division of the above-mentioned functional modules as an example. In actual application, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0495] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0496] Figure 19 shows a schematic structural diagram of a communication device (terminal device or access network device) provided by an exemplary embodiment of the present application. The communication device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104 and a bus 105.

[0497] Processor 101 includes one or more processing cores. Processor 101 executes various functional applications and information processing by running software programs and modules. Receiver 102 and transmitter 103 can be implemented as a communication component, which can be a communication chip. Memory 104 is connected to processor 101 via bus 105. Memory 104 can be used to store computer programs, which processor 101 executes to implement the various steps in the above-described method embodiments.

[0498] In addition, the memory 104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).

[0499] In some embodiments, a computer-readable storage medium is further provided, in which a computer program is stored. The computer program is configured to be executed by a processor to implement the various steps in the above method embodiments.

[0500] In some embodiments, a chip is further provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the various steps in the above method embodiments.

[0501] In some embodiments, a computer program product is also provided, which includes computer instructions stored in a computer-readable storage medium. The processor reads and executes the computer instructions from the computer-readable storage medium to implement the various steps in the above method embodiments.

[0502] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0503] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0504] In some embodiments of the present application, "predefined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

[0505] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, for example, it may include an LTE protocol, a NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0506] In this document, "plurality" refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0507] The term “less than” mentioned herein may be understood as less than, or may also be understood as less than or equal to; the term “greater than” mentioned herein may be understood as greater than, or may also be understood as greater than or equal to.

[0508] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[0509] In addition, the embodiments provided herein may be arbitrarily combined to form new embodiments, which are all within the scope of protection of this application.

[0510] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0511] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A data processing method, characterized in that: The method comprises: Different data corresponding to the same quality of service (QoS) flow are processed independently and / or jointly.

2. The method according to claim 1, characterized in that The different data correspond to different paths.

3. The method according to claim 1 or 2, characterized in that The method is performed by a sending end, and the independent processing includes at least one of the following: routing the different data to different paths; identifying the different data; Different first functions are used for the different data.

4. The method according to claim 3, characterized in that The sending end is a service data adaptation protocol (SDAP) layer, and routing the different data to different paths includes: Routing the different data to different Packet Data Convergence Protocol (PDCP) entities; or, The different data are routed to different data radio bearers (DRBs).

5. The method according to claim 3, characterized in that The transmitting end is a PDCP layer, and routing the different data to different paths includes: Routing the different data to different radio link control RLC entities; or, The different data are routed to different logical channels.

6. The method according to claim 3, characterized in that The identifying of the different data includes at least one of the following: Identifying the different data according to a protocol data unit (PDU) set corresponding to the data; Identifying the different data according to a start identifier and / or an end identifier of the PDU set; The different data are identified according to attributes of the data, where the attributes include at least one of the following: type, importance, relevance, priority, and dependency.

7. The method according to any one of claims 1 to 6, characterized in that The method is performed by a transmitting end, and the joint processing includes at least one of the following: The different data are numbered using a unified serial number SN; A unified first function is used for the different data.

8. The method according to any one of claims 1 to 7, characterized in that The method is performed by a receiving end, and the independent processing includes at least one of the following: receiving the different data from different paths; Different second functions are used for the different data.

9. The method according to claim 8, characterized in that The receiving end is an SDAP layer, and the receiving of the different data from different paths includes: receiving the different data from different PDCP entities; or, The different data are received from different DRBs.

10. The method according to claim 8, characterized in that The receiving end is a PDCP layer, and the receiving the different data from different paths includes: receiving the different data from different RLC entities; or, The different data are received from different logical channels.

11. The method according to any one of claims 1 to 10, characterized in that The method is performed by a receiving end, and the joint processing includes at least one of the following: Reordering the different data according to a unified SN; A unified second function is used for the different data.

12. The method according to any one of claims 1 to 11, characterized in that The combined treatment includes at least one of the following: The joint processing of the different data is performed between protocol layers or entities; Joint processing between protocol layers or entities is performed on the data routed to different paths.

13. The method according to claim 12, characterized in that The protocol layer or entity is a PDCP protocol layer or a PDCP entity; or, The protocol layer or entity is a joint protocol layer or joint entity corresponding to the PDCP protocol layer or PDCP entity.

14. The method according to claim 12 or 13, characterized in that The joint processing is performed by a transmitting end and / or a receiving end.

15. The method according to any one of claims 1 to 14, characterized in that The method is performed by a sending end, and the method further includes: When a first event is configured or satisfied, reconfigure the PDCP layer or PDCP entity to establish a first function for at least one path; and / or reconfigure the joint PDCP or joint processing entity to establish the first function for at least one path; and / or, When deconfiguration or release or the first event is not satisfied, reconfigure the PDCP entity of the PDCP layer to suspend or release the first function for at least one path; and / or reconfigure the joint PDCP or joint processing entity to suspend or release the first function for at least one path.

16. The method according to any one of claims 1 to 15, characterized in that When a first event is configured or satisfied, the transmitting end PDCP layer is reconfigured, and / or the protocol layer or entity of the joint processing is reconfigured; and / or, In case of deconfiguration or release or failure to satisfy the first event, the PDCP layer at the transmitting end deconfigures or suspends processing, and / or the protocol layer or entity of the joint processing deconfigures or suspends processing.

17. The method according to claim 15 or 16, characterized in that The PDCP layer is associated with a plurality of different RLC entities, and the plurality of different RLC entities correspond to a plurality of different paths; or the PDCP layer is associated with a plurality of different RLC entities, and each RLC entity corresponds to a path; The at least one path is: all paths among the multiple different paths, or part of the paths among the multiple different paths.

18. The method according to any one of claims 1 to 17, characterized in that The method further comprises: The mapping relationship between the QoS flow and the path is configured or changed, and, when the first event is configured or satisfied, at least one of the following actions is performed: pausing or releasing a first path among the multiple paths corresponding to the QoS flow; pausing or releasing a first function of a first path among the multiple paths corresponding to the QoS flow; suspending or releasing a PDCP entity corresponding to a first path among multiple paths corresponding to the QoS flow; pausing or releasing an RLC entity corresponding to a first path among multiple paths corresponding to the QoS flow; Resetting a media access control (MAC) entity corresponding to a first path among multiple paths corresponding to the QoS flow; Restoring or establishing a second path for the QoS flow; a first function of restoring or establishing a second path for the QoS flow; Restoring or establishing a PDCP entity corresponding to a second path for the QoS flow; Restoring or establishing an RLC entity corresponding to a second path for the QoS flow; A MAC entity corresponding to the second path is configured for the QoS flow.

19. The method according to claim 18, characterized in that The first path is a default path, or a path determined according to a stored mapping relationship between the QoS flow and the path; and / or, The second path is a changed path determined according to a configured, updated or indicated mapping relationship between the QoS flow and the path.

20. The method according to claim 18 or 19, characterized in that The first path is all or part of the multiple paths corresponding to the QoS flow; and / or, The second path is all or part of the multiple paths corresponding to the QoS flow.

21. The method according to any one of claims 15 to 20, characterized in that The first event includes at least one of the following: One QoS flow corresponds to multiple paths, or a specific QoS flow corresponds to multiple paths; Configure different data corresponding to QoS flows for independent processing and / or joint processing; Multiple paths are associated with one PDCP entity, and different paths correspond to different identifiers, where the identifier includes at least one of the following: a special identifier, an extended reality (XR) identifier, and a differentiated processing identifier; A protocol layer or entity associated with multiple PDCP layers or entities for joint processing; The PDCP layer or entity is associated with a plurality of different RLC entities, and the PDCP layer is associated with a target path, the target path including at least one of the following: a path with a special identifier, a path with an XR identifier, and a path with a differentiated processing identifier; The PDCP layer or entity is associated with multiple different RLC entities, and the different RLC entities correspond to different paths; The PDCP layer or entity is associated with a plurality of different RLC entities, and the PDCP layer processes the different data differently for the different RLC entities.

22. The method according to any one of claims 1 to 21, characterized in that The joint processing is for a plurality of different PDCP entities, and the different data corresponds to the different PDCP entities; or, the joint PDCP layer or the joint PDCP entity corresponds to a plurality of different PDCP entities, and the different data corresponds to the different PDCP entities.

23. The method according to claim 22, characterized in that The different PDCP entities have a binding relationship, or a joint processing relationship.

24. The method according to any one of claims 1 to 23, characterized in that Independent processing and / or joint processing of the different data are performed in the same PDCP entity.

25. The method according to claim 24, characterized in that The PDCP entity multiplexes a dual-active protocol stack DAPS architecture.

26. The method according to any one of claims 3, 7, 15 and 18, characterized in that The first function includes at least one of the following: an integrity protection function, an encryption function, and a header compression function.

27. The method according to claim 8 or 11, characterized in that The second function includes at least one of the following: an integrity authentication function, a decryption function, and a decompression function.

28. The method according to any one of claims 2 to 6, 8 to 10 and 12 to 21, characterized in that The path is a radio bearer RB.

29. The method according to any one of claims 1 to 28, characterized in that The different data correspond to different PDU sets, or the different data correspond to PDU sets with different attributes.

30. The method according to any one of claims 1 to 29, characterized in that The different data have different attributes, and the attributes include at least one of the following: type, importance, relevance, priority, and dependency.

31. A data processing method, characterized in that: The method comprises: Measurement statistics are performed on a protocol data unit (PDU) set to obtain a first result.

32. The method according to claim 31, characterized in that The first result includes: a PDU set loss rate, where the PDU set loss rate is used to indicate the ratio of the number of lost PDU sets to the total number of sent PDU sets.

33. The method according to claim 32, characterized in that The measurement statistics of the PDU aggregate loss rate meet at least one of the following conditions: Measure and calculate the PDU set loss rate at the Uu port; The PDU aggregate loss rate is obtained by measuring and counting the radio link control RLC layer; The PDU aggregate loss rate is measured and counted for each path of each terminal device; The PDU aggregate loss rate is measured and counted for a downlink; The PDU aggregate loss rate is obtained by measurement and statistics of access network equipment.

34. The method according to any one of claims 31 to 33, characterized in that The first result includes: a PDU set delay, where the PDU set delay is used to indicate an average delay in processing PDUs in the PDU set.

35. The method according to claim 34, wherein The measurement statistics of the PDU aggregate delay meet at least one of the following conditions: The PDU aggregate delay includes the delay of the access network part and / or the delay of the core network part; The PDU aggregate delay is measured and counted for each path of each terminal device; The PDU aggregate delay is measured and counted for the downlink; The PDU aggregate delay is measured and counted for uplink.

36. The method according to claim 34, wherein The PDU aggregation delay is a queuing delay of the PDU aggregation at a Packet Data Convergence Protocol (PDCP) layer at a transmitting end, and the queuing delay is obtained by measuring and statistically analyzing the PDCP layer at the transmitting end.

37. The method according to claim 36, wherein The configuration and / or reporting of the queuing delay measurement includes at least one of the following: Delay configuration information corresponding to the PDU set is configured, where the delay configuration information is used to indicate measurement and / or reporting of a queuing delay corresponding to the PDU set; The delay configuration information corresponding to the PDU set is included in the reporting configuration information; Reporting configuration information including delay configuration information corresponding to the PDU set, included in the measurement configuration information; The delay configuration information corresponding to the PDU set configuration indicates that the reporting type of the queuing delay is periodic reporting; The queuing delay corresponding to the PDU set is included in the measurement result report; The measurement results include the queuing delay corresponding to the PDU set of one or more paths; The delay configuration information corresponding to the PDU set includes configuration information for one or more paths.

38. The method according to claim 37, wherein The method satisfies at least one of the following: The reporting configuration information has a corresponding reporting configuration identifier; The reporting configuration identifier corresponds to the measurement identifier; The measurement identifier is associated with the measurement result corresponding to the measurement configuration information.

39. The method according to claim 34, wherein The PDU aggregate delay is the air interface transmission delay of the PDU aggregate, and the air interface transmission delay is obtained by measuring and counting the media access control MAC layer of the receiving end.

40. The method according to claim 34, wherein The PDU aggregate delay is a processing delay of the PDU aggregate at the RLC layer of the receiving end, and the processing delay is obtained by measuring and counting the RLC layer of the receiving end.

41. The method according to claim 34, wherein The PDU aggregate delay is a reordering delay of the PDU aggregate at the PDCP layer of the receiving end, and the reordering delay is obtained by measuring and counting the PDCP layer of the receiving end.

42. The method according to claim 34, wherein The PDU aggregate delay for the uplink on the F1-U interface and the PDU aggregate delay for the downlink on the F1-U interface use the same metric.

43. A data processing device, characterized in that: The device comprises: The data processing module is used to independently process and / or jointly process different data corresponding to the same quality of service QoS flow.

44. A data processing device, characterized in that The device comprises: The measurement and statistics module is used to perform measurement and statistics on a protocol data unit (PDU) set to obtain a first result.

45. A communication device, characterized in that The communication device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 1 to 30, or implements the method according to any one of claims 31 to 42.

46. ​​A computer-readable storage medium, characterized in that The storage medium stores a computer program, which is used to be executed by a processor to implement the method according to any one of claims 1 to 30, or to implement the method according to any one of claims 31 to 42.

47. A chip, characterized in that: The chip includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the method according to any one of claims 1 to 30, or to implement the method according to any one of claims 31 to 42.

48. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the method according to any one of claims 1 to 30, or to implement the method according to any one of claims 31 to 42.

Images