Data processing method and apparatus

Abstract

The present application provides a data processing method and apparatus. The method is applied to an inter-base station handover process, and comprises: receiving a first cache data packet, wherein a first extension head of the first cache data packet comprises first information; and determining an information position of the first information in the first extension header. In this way, by identifying the information position of the first information in the first extension header, a core network or a target base station can correctly process the first cache data packet, so that data parsing errors of the target base station caused by capability mismatch between base stations can be avoided, thereby ensuring normal transmission of user data.

Description

Data processing method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 28, 2023, with application number 202311288639.X, and priority to the Chinese patent application with the invention name “Data Processing Method and Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a data processing method and apparatus. Background Art

[0003] With the continuous development of communication technology, extended reality (XR) is one of the 5G multimedia applications that is currently being considered in the industrial field.

[0004] The 5G system forwards and processes data based on the granularity of quality of service flow (QoS flow) and guarantees its quality of service (QoS). The 5G core network (5GC) in the 5G system indicates the QoS requirements of different QoS flows to the radio access network (RAN) through the QoS profile (QoS profile). For ordinary services in the 5G system, QoS guarantees are only required at the granularity of protocol data unit (PDU), but for XR services, QoS guarantees are usually expected to be required at the granularity of PDU set (PDU set). For XR services, the base station is usually required to have the ability to process PDU set. Therefore, the base station will report its own processing capabilities for PDU set to the core network.

[0005] When inter-station handover occurs in a terminal device, how to avoid data parsing errors at the target base station caused by capability mismatch between the source base station and the target base station during the handover process has become an urgent problem to be solved.

[0006] Summary of the Invention

[0007] The present application provides a data processing method and apparatus, which can avoid target base station data parsing errors caused by mismatch in capabilities between base stations during inter-station switching, thereby ensuring normal transmission of user data.

[0008] In a first aspect, a data processing method is provided, the method being applied to an inter-station handover process, the method comprising: receiving a first buffered data packet, wherein a first extended header of the first buffered data packet includes first information, and determining an information position of the first information in the first extended header.

[0009] In the above technical solution, by identifying the information position of the first information in the first extended header, it helps the core network or the target base station to correctly process the first cached data packet, and can avoid target base station data parsing errors caused by capability mismatch between base stations, thereby ensuring normal transmission of user data.

[0010] In combination with the first aspect, in certain implementations of the first aspect, the first information includes at least one of the following relevant information of the protocol data unit PDU set: the sequence number of the PDU set, the PDU sequence number within the PDU set, the size of the PDU set, the end PDU of the PDU set, the importance of the PDU set, and the end PDU of the data burst to which the PDU set belongs.

[0011] In conjunction with the first aspect, in certain implementations of the first aspect, the first extended header includes a first field, and the first field is used to indicate a size of the first extended header. Determining an information location of the first information in the first extended header includes: parsing the first extended header and determining the size of a successfully parsed field. The information location is determined based on the size of the first extended header and the size of the successfully parsed field.

[0012] In conjunction with the first aspect, in certain implementations of the first aspect, the first extended header includes a second field, the second field includes a new user plane protocol frame, and the new user plane protocol frame includes the first information. Determining an information position of the first information in the first extended header includes: determining a position of the new user plane protocol frame as the information position.

[0013] In combination with the first aspect, in certain implementations of the first aspect, when the method is applied to a target base station in an inter-station switching process, the target base station does not have the ability to process the first information, and the method also includes: during the processing of the first cached data packet, not processing the first information based on the information location.

[0014] In the above technical solution, when the target base station does not have the ability to process the first information, for example, when the target base station does not have the ability to process the PDU set, the target base station can identify the location of the first information and ignore and not process the first information, thereby avoiding target base station data parsing errors caused by mismatching capabilities between base stations, thereby ensuring normal transmission of user data.

[0015] In conjunction with the first aspect, in certain implementations of the first aspect, when the method is applied to a core network during an inter-station handover, the method further includes: obtaining a processing capability of a target base station during the inter-station handover regarding the first information; if the target base station does not have the capability to process the first information, removing the first information from the first cached data packet based on the location of the information to determine a second cached data packet; and sending the second cached data packet to the target base station.

[0016] In the above technical solution, for NG switching, the core network first receives the first cached data packet. When the target base station does not support PDU set processing, the relevant information of the PDU set that the target base station cannot recognize can be removed in advance, thereby avoiding unexpected situations that may occur during the data parsing process of the target base station, such as packet loss or parsing errors, and thus ensuring normal data processing.

[0017] In a second aspect, a data processing method is provided, the method being applied to a target base station during an inter-station handover process. The method comprises: receiving a first handover request, the first handover request including first capability information of a terminal device regarding a protocol data unit (PDU) set or wireless resource configuration information of the terminal device related to an extended reality (XR) service. Based on the first handover request, first indication information is sent to a core network, the first indication information being used to indicate whether the target base station has a PDU set processing capability.

[0018] In the above technical solution, the target base station can determine that the terminal device has a PDU set processing requirement based on at least one of the first capability information about the terminal device for processing PDU sets or the radio resource information about the XR service carried in the first handover request. In this way, even if the source base station does not have the PDU set processing capability, the target base station can report to the core network based on this information whether it supports the PDU set processing capability, thereby enabling PDU set-based service guarantee for the terminal device.

[0019] Compared to the case where the target base station only reports its own PDU set processing capability based on the QoS parameters of the PDU set, the solution of the embodiment of the present application can better cope with the situation where the source base station does not have the PDU set processing capability but the target base station has the PDU set processing capability, thereby enabling subsequent PDU set-based service guarantees for the terminal device.

[0020] Compared to the target base station reporting its own PDU set processing capability to the core network in response to any switching request, the target base station in the solution of the present application reports its own PDU set processing capability to the core network only when the terminal device has a PDU set processing requirement, which can reduce meaningless reporting. For example, if the terminal device has no PDU set processing requirement, the target base station does not need to report its own PDU set processing capability to the core network.

[0021] In conjunction with the second aspect, in certain implementations of the second aspect, the first capability information is used to indicate at least one of the following information: the first capability information is used to indicate whether the terminal device supports a capability to identify a PDU set. The first capability information is used to indicate whether the terminal device supports a capability to process a PDU set. The first capability information is used to indicate whether the terminal device supports a capability to discard a PDU set. The first capability information is used to indicate whether the terminal device supports a capability to discard a PDU set based on its importance.

[0022] In conjunction with the second aspect, in certain implementations of the second aspect, the radio resource configuration information includes radio resource control (RRC) configuration information, where the RRC configuration information includes at least one of the following information: configuration information for a discontinuous reception period based on a rational number; configuration information for reporting remaining data time; and configuration information for reporting auxiliary information related to XR services.

[0023] With reference to the second aspect, in certain implementations of the second aspect, the first indication information is carried in a path switch request message.

[0024] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: receiving quality of service parameters of a PDU set corresponding to the XR service from the core network.

[0025] In a third aspect, a data processing device is provided, comprising a transceiver unit and a processing unit: the transceiver unit is configured to receive a first buffered data packet, wherein a first extended header of the first buffered data packet includes first information; and the processing unit is configured to determine an information location of the first information in the first extended header.

[0026] It should be understood that the technical solution corresponding to the third aspect can refer to the first aspect and will not be elaborated here.

[0027] In combination with the third aspect, in certain implementations of the third aspect, the first information includes at least one of the following relevant information of the protocol data unit PDU set: the serial number of the PDU set, the PDU sequence number within the PDU set, the size of the PDU set, the end PDU of the PDU set, the importance of the PDU set, and the end PDU of the data burst to which the PDU set belongs.

[0028] In conjunction with the third aspect, in certain implementations of the third aspect, the first extended header includes a first field, the first field being used to indicate a size of the first extended header; and the processing unit is specifically configured to: parse the first extended header, determine the size of the field that was successfully parsed, and determine the information location based on the size of the first extended header and the size of the field that was successfully parsed.

[0029] In combination with the third aspect, in certain implementations of the third aspect, the first extended header includes a second field, the second field includes a new user plane protocol frame, and the new user plane protocol frame includes the first information; the processing unit is specifically used to: determine the position of the new user plane protocol frame as the information position.

[0030] In combination with the third aspect, in certain implementations of the third aspect, when the device is a target base station in an inter-station switching process, the target base station does not have the ability to process the first information, and the processing unit is also used to: during the processing of the first cached data packet, not process the first information based on the information location.

[0031] In conjunction with the third aspect, in certain implementations of the third aspect, when the apparatus is a core network during an inter-station handover, the processing unit is further configured to: obtain a processing capability of a target base station regarding the first information during the inter-station handover; and when the target base station does not have the capability to process the first information, remove the first information from the first cached data packet based on the location of the information to determine a second cached data packet. The transceiver unit is further configured to send the second cached data packet to the target base station.

[0032] In a fourth aspect, a data processing device is provided, comprising a transceiver unit and a processing unit: the transceiver unit is configured to receive a first handover request, the first handover request including first capability information of a terminal device regarding a protocol data unit (PDU) set or wireless resource configuration information of the terminal device related to an extended reality (XR) service. The processing unit is configured to send first indication information to a core network based on the first handover request, the first indication information being configured to indicate whether a target base station has the PDU set processing capability.

[0033] It should be understood that the technical solution corresponding to the fourth aspect can refer to the second aspect and will not be elaborated here.

[0034] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the first capability information is used to indicate at least one of the following information: the first capability information is used to indicate whether the terminal device supports a capability to identify a PDU set. The first capability information is used to indicate whether the terminal device supports a capability to process a PDU set. The first capability information is used to indicate whether the terminal device supports a capability to discard a PDU set. The first capability information is used to indicate whether the terminal device supports a capability to discard a PDU set based on its importance.

[0035] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the radio resource configuration information includes radio resource control (RRC) configuration information, where the RRC configuration information includes at least one of the following: configuration information for a discontinuous reception period based on a rational number; configuration information for reporting remaining data time; and configuration information for reporting auxiliary information related to XR services.

[0036] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first indication information is carried in a path switch request message.

[0037] In combination with the fourth aspect, in certain implementations of the fourth aspect, the transceiver unit is further used to: receive quality of service parameters of a PDU set corresponding to the XR service from the core network.

[0038] In a fifth aspect, a data processing device is provided, which includes: a memory for storing programs; a processor for executing computer programs or instructions stored in the memory, and when the computer program or instructions stored in the memory are executed, the processor is used to execute the method provided in any one of the implementation modes of the first or second aspect above.

[0039] In one implementation, the apparatus is a source base station or a target base station in an inter-station handover process.

[0040] In another implementation, the device is a chip, a chip system, or a circuit in a source base station or a target base station during an inter-station handover process.

[0041] In a sixth aspect, the present application provides a processor for executing the method provided by any one of the implementation modes of the first to second aspects above. In the process of executing these methods, the process of sending the above information and obtaining / receiving the above information in the above methods can be understood as the process of the processor outputting the above information, and the process of the processor receiving the input above information. When outputting the above information, the processor outputs the above information to the interface and transmits it through the interface. After being output by the processor, the above information may also need to undergo other processing before reaching the interface. Similarly, when the processor receives the input above information, the interface obtains / receives the above information and inputs it into the processor. Furthermore, after the interface receives the above information, the above information may need to undergo other processing before being input into the processor.

[0042] For the operations involved, such as transmission, sending, and acquisition / reception, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as output and reception, input and other operations, and can also be understood as transmission, sending and receiving operations performed by radio frequency circuits and antennas. This application does not limit this.

[0043] During implementation, the processor may be a processor specifically configured to execute the methods, or may be a processor that executes computer programs or instructions in a memory to execute the methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on separate chips. The embodiments of the present application do not limit the type of memory or the configuration of the memory and the processor.

[0044] In a seventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, and the program code includes a method for executing any one of the implementations of the first to second aspects above.

[0045] In an eighth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided in any one of the implementations of the first to second aspects above.

[0046] In the ninth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface and executes the method provided in any one of the implementation methods of the first to second aspects above.

[0047] Optionally, as an implementation method, the chip may also include a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any one of the implementation methods of the first to second aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0049] FIG2 is a schematic diagram of a 5G system based on a QoS architecture provided in an embodiment of the present application;

[0050] FIG3 is a schematic diagram of a flow chart of an inter-station handover process provided by an embodiment of the present application;

[0051] FIG4 is a schematic diagram of a process for inter-station handover of an XR service provided in an embodiment of the present application;

[0052] FIG5 is a schematic diagram of a data format provided in an embodiment of the present application;

[0053] FIG6 is a flow chart of a data processing method provided in an embodiment of the present application;

[0054] FIG7 is a schematic diagram of the format of an extension header provided in an embodiment of the present application;

[0055] FIG8 is a schematic diagram of another format of an extension header provided in an embodiment of the present application;

[0056] FIG9 is a schematic diagram of an interactive flow of a data processing method provided in an embodiment of the present application;

[0057] FIG10 is a schematic diagram of a flow chart of inter-station handover of another XR service provided in an embodiment of the present application;

[0058] FIG11 is a schematic diagram of an interactive flow of another data processing method provided in an embodiment of the present application;

[0059] FIG12 is a schematic diagram of a data processing device 1200 provided in an embodiment of the present application;

[0060] FIG13 is a schematic structural diagram of a data processing device 1300 provided in an embodiment of the present application;

[0061] FIG14 is a schematic diagram of a chip system 1400 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0062] The technical solution in this application will be described below with reference to the accompanying drawings.

[0063] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Fifth Generation (5G) system or New Radio (NR), and future evolved communication systems.

[0064] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application.

[0065] As shown in Figure 1, a communication system using the solution of an embodiment of the present application may include an access network device, a terminal device, and a core network. The communication system can be used for information exchange between an access network device and a core network, or for information exchange between access network devices. For example, as shown in Figure 1, both access network device #1 and access network device #2 can communicate with the core network via an NG interface. Access network device #1 and access network device #2 can communicate directly via an Xn interface, or access network device #1 and access network device #2 can communicate indirectly via the core network via the NG interface.

[0066] Terminal equipment, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., refers to a device that provides voice and / or data connectivity to users. For example, a terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a mobile internet device (MID), a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a drone, a drone controller, etc. The embodiments of the present application do not limit the application scenarios. Terminal devices also include devices capable of sidelink communication, such as vehicle-mounted terminals, or handheld terminals capable of V2X (vehicle-to-everything) communication.

[0067] Access network equipment refers to a radio access network (RAN) node (or device) that connects a terminal to a wireless network, and can also be called a base station. For example, it can be an NR gNB, or various types of base stations such as an LTE eNB. For ease of description, the embodiments of this application uniformly refer to "access network equipment" as "base station". Among them, the NR gNB can adopt an architecture with a centralized unit (CU) and a distributed unit (DU) separated, such as base station #1 shown in Figure 1, where the CU and DU are connected via the F1 interface for message transmission; or the architecture with no separation of CU and DU can be adopted, such as base station #2 shown in Figure 1, which is not limited in this embodiment of the application. In the separate deployment scenario where the access network equipment includes a CU and a DU, the CU supports protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP); the DU mainly supports radio link control layer (RLC), media access control layer (MAC), and physical layer protocols. Normally, a terminal device maintains a data connection with only one base station at a time. In a dual connectivity (DC) scenario, a terminal device can be connected to two base stations simultaneously, one of which serves as a control anchor point, providing both control and user plane connections for the terminal, known as a primary base station, and the other, which only provides user plane connections for the terminal, known as a secondary base station. This application may or may not be applied to DC scenarios.

[0068] Core network equipment refers to the equipment in the core network (CN) that provides service support for the terminal. At present, some examples of core network equipment are: access and mobility management function (AMF) entity, session management function (SMF) entity, user plane function (UPF) entity, etc., which are not listed here one by one. Among them, the AMF entity can be responsible for the access management and mobility management of the terminal; the SMF entity can be responsible for session management, such as user session establishment, etc.; the UPF entity can be a functional entity of the user plane, mainly responsible for connecting to the external network. It should be noted that the entity in this application can also be referred to as a network element or a functional entity. For example, the AMF entity can also be referred to as an AMF network element or an AMF functional entity. For another example, the SMF entity can also be referred to as an SMF network element or an SMF functional entity, etc.

[0069] In order to facilitate understanding of the solutions of the embodiments of the present application, the technical terms involved in the embodiments of the present application will be described in detail below.

[0070] 1.PDU set

[0071] A collection of multiple data packets at the transport layer corresponds to the minimum granularity of data processing at the application layer. In some scenarios, the application layer can only correctly parse the corresponding data unit after correctly receiving all packets in a PDU set. In other scenarios, the application layer can only parse the corresponding data unit after correctly receiving a certain percentage of packets in the PDU set.

[0072] 2.XR business

[0073] Extended Reality (XR) refers to a variety of environments that combine real and virtual reality, as well as human-machine interactions, generated by computing technologies and wearable devices. XR specifically includes the following typical forms: AR, VR, and Mixed Reality (MR).

[0074] The 3rd Generation Partnership Project (3GPP) Rel-17 modeled and analyzed XR service characteristics. XR services typically generate data frames periodically at a certain frame rate. For example, an AR service with a 60fps (frames per second) frame generates 60 frames per second, or approximately every 16.67ms. A single video frame may be transmitted across multiple data packets, which may be grouped into one or more PDU sets.

[0075] 3. Quality of Service (QoS)

[0076] Quality of Service (QoS) refers to a technology used to address network latency and congestion. When network congestion occurs, data may be discarded. To meet user requirements for different QoS levels for different applications, the network must be able to allocate and schedule resources based on user needs, providing different QoS levels for different data types.

[0077] 4. QoS flow

[0078] The 5G system forwards and processes data based on the granularity of QoS flows and guarantees its QoS.

[0079] The 5G core network establishes one or more protocol data unit sessions (PDU sessions) for a UE. A QoS flow is a data flow with the same source and destination addresses and the same QoS requirements within a PDU session. Figure 2 is a schematic diagram of a 5G system based on a QoS architecture provided by an embodiment of the present application. As shown in Figure 2, a PDU session is established between the UE and the UPF, a radio bearer is established between the UE and the NB, and a core network tunnel is established between the NB and the UPF. The PDU session includes multiple QoS flows, including a first QoS flow, a second QoS flow, and the like.

[0080] For downlink, 5GC identifies the characteristics of the data packet, including the source Internet Protocol (IP) address, destination IP address, source port number, destination port number, and transport layer protocol number, and maps data packets with the same characteristics to the same QoS flow. It also carries a QoS flow identifier (QFI) in the packet header to identify which QoS flow the packet belongs to. For uplink, 5GC can explicitly or implicitly configure the mapping relationship between the above data packet characteristics and QoS flows to the UE, and the UE will map the uplink data to be transmitted to different QoS flows.

[0081] Data from different QoS flows is transmitted independently within the 5G system. For each QoS flow, the 5GC sends its QoS profile to the radio access network (RAN), indicating its QoS requirements, such as the packet delay budget (PDB) and packet error rate (PER). This profile represents the expected quality of service for data transmitted within the 5G system. The PDB represents the upper limit of the transmission delay between the core network and the UE. Packets that fail to transmit correctly within the PDB are considered timed out. The PER represents the upper limit of the packet error rate during QoS flow transmission, representing the percentage of packets processed by the sender but not correctly received by the receiver. Specifically, the core network and the UE can be understood as, for downlink traffic, from the core network's UPF to the UE; for uplink traffic, from the UE to the core network's UPF.

[0082] For a PDU session, the RAN establishes one or more data radio bearers (DRBs) and maps each QoS flow to these DRBs for air interface transmission. Multiple QoS flows can be mapped to a single DRB, but a single QoS flow cannot be mapped to multiple DRBs. QoS flows with the same or similar QoS requirements are typically mapped to the same DRB, providing the same QoS guarantees over the air interface.

[0083] 5. QoS parameters of PDU

[0084] The 5GC uses QoS profiles to indicate the QoS requirements of different QoS flows to the RAN. These requirements are reflected in various QoS parameters. For example, common QoS parameters include PDB and PER. The transport network should strive to ensure that service QoS requirements are met to enhance user experience.

[0085] 6. QoS parameters for PDU set

[0086] XR services typically require QoS guarantees at the PDU set level, which is determined by the encoding method used for XR services. Because a PDU set corresponds to the smallest unit of application-layer data processing, such as a video frame, for many applications, the receiving end can only successfully decode the video frame if all packets in the PDU set are correctly received. Therefore, XR services require the transmission network to provide overall QoS guarantees for the PDU set to prevent partial packet timeouts or errors within the PDU set from causing decoding failures of the entire video frame.

[0087] 3GPP R18 (Release-18) designed new QoS parameters for XR services, called PDU set QoS parameters, including PDU set delay budget (PSDB), PDU set error rate (PSER), and PDU set integrated information (PSIHI). PSDB and PSER correspond to the traditional PDB and PER, respectively. PSDB represents the upper limit of the delay from the transmission of the first data packet in the PDU set between the core network and the UE to the completion of the transmission of the last data packet in the PDU set between the core network and the UE, that is, the upper limit of the transmission delay of the PDU set between the core network and the UE. A PDU set that is not correctly transmitted in full within the PSDB is considered to have timed out. PSER represents the upper limit of the percentage of PDU sets that are not correctly transmitted during the transmission of the QoS flow, that is, the upper limit of the percentage of PDU sets that are processed by the sender but not correctly received by the receiver. PSIHI describes whether a QoS flow requires PDU set integrity. It indicates whether the application layer, when processing a PDU set, requires the receiving side to correctly receive all packets within the PDU set. This depends on the specific implementation of the application.

[0088] In one implementation, an application can only correctly decode a PDU set after correctly receiving all packets within it. In this case, the transmission network should strive to ensure that all packets within the PDU set are correctly transmitted within the delay budget. If a packet times out or is lost, the receiving application layer will not be able to process the PDU set in a timely manner, resulting in a poor user experience. If it is determined that a packet in the PDU set cannot be transmitted correctly and in a timely manner, the sender can abandon transmission of the remaining packets. Even if the remaining packets are correctly transmitted, the application cannot process them, and proactively abandoning transmission can save network resources. In another implementation, an application does not need to correctly receive all packets within a PDU set to decode the set. For example, when a PDU set has been redundantly encoded at the sender, the receiver can fully recover the PDU set data by receiving only a certain number or proportion of packets. In this case, even if some packets within the PDU set have timed out or been lost, the sender should continue to transmit the remaining packets, as they are still useful to the application layer.

[0089] Through PDU set QoS parameters, the core network requires the RAN to provide PDU set-granular QoS guarantees for PDU set-based QoS flows (such as XR services), thereby improving XR user satisfaction.

[0090] 7. PDU set related information

[0091] To provide QoS guarantees based on PDU sets, base stations need to be able to identify different PDU sets and understand some basic characteristics of PDU sets. To this end, the core network can provide base stations with relevant information about PDU sets to assist the base stations in PDU set processing.

[0092] Specifically, for a QoS flow with PDU set QoS requirements, when the core network submits the data packet of the QoS flow to the base station, it can add relevant information of the PDU set in the packet header of the data packet, which may include the following information: PDU set sequence number (PSSN) indicates the sequence number of the PDU set to which the current PDU belongs, PDU sequence number within a PDU set indicates the sequence number of the current PDU in the PDU set to which it belongs, PDU set size (PSS) indicates the sum of the sizes of all PDUs in the PDU set to which the current PDU belongs, end PDU of the PDU set indicates whether the current PDU is the last PDU in the PDU set to which it belongs (for example, a value of 1 indicates that the current PDU is the last PDU in the PDU set to which it belongs, and a value of 0 indicates that the current PDU is not the last PDU in the PDU set to which it belongs), end of data burst identifier (EDB) indicates whether the current data burst ends, and PDU set importance (PSI) indicates the PDU to which the current PDU belongs The importance of the set compared to other PDU sets in the QoS flow.

[0093] The core network may send the relevant information of the PDU set to the base station via an extension header of a general packet radio system tunneling protocol for the user plane (GTP-U).

[0094] 8. Handover

[0095] In mobile communication systems, when a UE obtains service from a 5G network, it may need to change its serving cell due to a change in location. The process of a connected UE changing its serving cell is called a handover. The handover process is controlled by the base station, which sends a handover message to instruct the UE when and which cell to switch to. The base station typically determines whether to switch and to which cell based on the signal quality of each cell.

[0096] When the source cell (i.e., the cell where the UE originally resides) and the target cell (i.e., the cell to which the UE is switching) are located in different base stations, this type of handover is called an inter-base station handover. Depending on the type of interface between the source and target base stations, this type of handover can be categorized as either Xn or NG.

[0097] FIG3 is a schematic diagram of a flow chart of an inter-station handover process provided in an embodiment of the present application.

[0098] As shown in FIG3( a ), when an Xn interface exists between the source base station and the target base station, handover based on the Xn interface can be performed.

[0099] S311, the source base station sends a handover request (HANDOVER REQUEST) #1 to the target base station.

[0100] Handover Request #1 indicates that the UE wishes to handover to the target cell. The Handover Request carries the UE's configuration requirements, such as the PDU session and QoS flows established by the UE, as well as the QoS requirements of these QoS flows.

[0101] S312: The target base station performs admission control based on the cell load, capability, etc., and determines a handover request feedback message #1.

[0102] The handover request feedback message #1 is used to indicate whether to accept the handover UE and which PDU sessions or QoS flows of the UE are accepted.

[0103] It should be understood that when the target base station agrees to handover request #1, the type of handover request feedback message #1 is a handover request acknowledgment message (HANDOVER REQUEST ACKNOWLEDGE). When the target base station disagrees with handover request #1, the type of handover request feedback message #1 is a handover preparation failure message (HANDOVER PREPARATION FAILURE).

[0104] S313: The target base station sends a handover request feedback message #1 to the source base station.

[0105] S314: If the target base station accepts the handover of the UE, the source base station sends a handover command #1 to the UE, wherein the handover command #1 is used to instruct the UE to access the target cell.

[0106] S315: The source base station no longer processes data with the UE, and sends the buffered data #1 to the target base station.

[0107] The cached data #1 is the data that is already in the source base station cache and should be sent to the UE.

[0108] S316: After receiving the instruction, the UE performs handover and successfully accesses the target cell.

[0109] S317, the terminal device and the target base station complete access to the target cell.

[0110] That is, the terminal device continues to process data in the target cell, that is, the core network sends subsequent downlink data to the UE through the target base station, and the UE's uplink data is also sent to the core network through the target base station.

[0111] As shown in (b) of Figure 3, when there is no Xn interface between the source base station and the target base station, the base stations cannot directly transmit the switching request and confirmation messages. At this time, a switching based on the NG interface is required to forward the above messages through the core network.

[0112] S321a: The source base station sends a handover request #2 to the core network. S321b: The core network sends a handover request #3 to the target base station.

[0113] Among them, the functions and effects of switching request #2, switching request #3 and switching request #1 are similar and will not be described in detail here.

[0114] S322: The target base station performs admission control based on the cell load, capability, etc., and determines the handover request feedback message #2.

[0115] Among them, the handover request feedback message #2 has similar functions to the handover request feedback message #1, and will not be described in detail here.

[0116] S323, the target base station sends a handover request feedback message #2 to the core network.

[0117] S324a, when the target base station accepts the handover UE, the core network sends a handover command #2 to the source base station. S324b, the source base station sends a handover command #3 to the terminal device.

[0118] The handover command #2 is used to instruct the source base station to continue the handover operation, and the handover command #3 is used to instruct the UE to handover to the target cell.

[0119] S325a: The source base station no longer processes data with the UE and sends the buffered data #2 to the core network. S325b: The core network sends the buffered data #2 to the target base station.

[0120] The cached data #2 is data that is already in the source base station cache and should be sent to the UE.

[0121] S326: After receiving the instruction, the UE performs handover and successfully accesses the target cell.

[0122] S327, the terminal device and the target base station complete access to the target cell.

[0123] That is, the terminal device continues to process data in the target cell, that is, the core network sends subsequent downlink data to the UE through the target base station, and the UE's uplink data is also sent to the core network through the target base station.

[0124] It should be understood that the information transmission method between the source base station and the target base station can be to realize direct communication between the source base station and the target base station through the Xn interface, or to realize indirect communication between the source base station and the target base station through the NG interface and forwarding through the core network.

[0125] At present, since XR services require QoS guarantee based on the granularity of PDU set, the corresponding base stations need to support data processing and forwarding based on PDU set. Furthermore, during downlink transmission, when the QoS flow requires QoS guarantee based on PDU set and the base station supports PDU set processing, the core network will add relevant information of PDU set to the header of each data packet when transmitting the data packet to the base station. The relevant information can be a parameter used to identify the PDU set or reflect the attributes of the PDU set. For example, the PDU set sequence number, the sequence number of the PDU in the PDU set, the PDU set size, the PDU set importance, etc., so that the base station can distinguish which PDU set different data packets belong to. If the base station does not support PDU set processing, the core network does not need to add this information. Therefore, the core network needs to know the capability information of whether the base station supports PDU set processing.

[0126] Specifically, if the base station receives a QoS profile of a QoS flow containing QoS parameters of a PDU set, the base station reports to the core network whether it supports processing the PDU set.

[0127] FIG4 is a flow chart of an inter-station handover of an XR service provided by an embodiment of the present application. Assume that the source base station in FIG4 supports processing PDU sets, and the target base station does not support processing PDU sets. The terminal device is running an XR service (for example, receiving XR video from an XR server) and expects that the data of the XR service can obtain QoS guarantees based on PDU sets. Among them, the source base station and the target base station shown in FIG4 can communicate directly through the Xn interface.

[0128] S401: The core network sends a QoS guarantee requirement of a PDU set to a source base station.

[0129] The QoS guarantee requirement may include a QoS profile of the QoS parameters of the PDU set.

[0130] S402: The source base station sends capability indication information to the core network according to the QoS configuration file. The capability indication information is used to indicate that the source base station has the capability to process PDU sets.

[0131] S403: The core network sends first XR data to the source base station, where the first XR data includes relevant information of the PDU set.

[0132] The relevant information of the PDU set may be carried in the header of the data packet in the QoS flow where the first XR data is located. The relevant information of the PDU set may include, for example, the PDU set sequence number, the sequence number of the PDU within the PDU set, the PDU set end identifier, the data burst end identifier, the PDU set size, the PDU set importance, and the end PDU of the data burst to which the PDU set belongs.

[0133] S404: The source base station processes the first XR data according to the relevant information of the PDU set.

[0134] It should be understood that the source base station identifies the relevant information of the PDU set in the first XR data to determine which PDU set the first XR data corresponds to, and provides scheduling processing based on the PDU set to ensure its PDU set QoS requirements. The relevant information of the PDU set has been described in detail above and will not be repeated here.

[0135] S405: The source base station sends the processed first XR data to the terminal device.

[0136] The terminal device is currently in the source cell of the source base station. Assuming that the terminal device moves, the terminal device expects to switch to the target cell of the target base station.

[0137] S406 : The source base station sends a handover request # 3 to the target base station. The handover request # 3 includes a QoS profile of the QoS flow where the first XR data is located, including QoS parameters of a PDU set.

[0138] S407: When the target base station does not support processing the PDU set, the target base station sends capability indication information to the core network. The capability indication information is used to indicate that the target base station does not support processing the PDU set.

[0139] It should be understood that an equivalent approach is for the target base station to send capability indication information to the core network only when it supports processing PDU sets. This capability indication information is used to indicate that the target base station supports processing PDU sets. If the target base station does not support processing PDU sets, the target base station does not send the capability indication information to the core network, and the core network can also understand that the target base station does not support processing PDU sets.

[0140] It should be understood that the core network device's knowledge of the capability indication information of the target base station helps the core network to send data to the target base station in a more targeted manner.

[0141] S408: The target base station performs admission control based on the cell load, capability, etc., and determines the handover request feedback message #3.

[0142] Among them, the handover request feedback message #3 and the handover request feedback message #1 have similar functions and are not described in detail here.

[0143] S409: The source base station sends a handover command #3 to the UE, wherein the handover command #3 is used to instruct the UE to access the target cell.

[0144] S410: The source base station no longer processes data with the UE, and sends the buffered data #3 to the target base station.

[0145] The buffered data #3 is the first XR data that has been buffered in the source base station. Therefore, the data packet header of the buffered data #3 carries relevant information of the PDU set.

[0146] S411, the terminal device and the target base station complete access to the target cell.

[0147] S412: The target base station sends a handover completion message to the core network.

[0148] S413: The core network sends second XR data to the target base station. The second XR data does not include relevant information of the PDU set.

[0149] It should be understood that since the target base station does not support processing PDU sets, data processing between the core network and the target base station reverts to the traditional PDU-based transmission method. In other words, the second XR data includes information related to the PDU, rather than information related to the PDU set.

[0150] S414: The target base station processes the second XR data according to the relevant information of the PDU.

[0151] S415: The target base station sends the processed second XR data to the terminal device.

[0152] The differences in whether base stations support processing PDU sets are mainly due to differences in base station capabilities and upgrade status in actual networks. Although the above solution has taken into account the fact that different base stations may have different capabilities to support processing PDU sets, and has designed a corresponding solution to enable the base station to notify the core network of this capability, so that the core network can reasonably decide whether to provide PDU set-based QoS guarantees for the QoS flow and whether to add PDU set-related information to the data packets in the QoS flow. However, before the target base station and the terminal device process the data, since the data originally cached in the source base station needs to be forwarded to the target base station, there may be a mismatch between the cached data and the capabilities of the target base station.

[0153] FIG5 is a schematic diagram of a data format provided in an embodiment of the present application.

[0154] As shown in Figure 5(a), since the source base station has the ability to process PDU sets, cached data #3 may include a data packet header, information related to the PDU set, and a data payload. The information related to the PDU set may be carried in an extended header in the data packet header, which may be a GPT-U header. The data payload is the information bits that the target base station needs to actually transmit to the terminal device after an inter-station handover occurs.

[0155] As shown in Figure 5(b), since the target base station does not have the ability to process PDU sets, for example, if it is an older, unupgraded base station, it can typically use the two data processing methods shown in Figure 5(b). Method 1: The target base station successfully parses the packet header, but cannot identify the relevant information about the PDU set. Therefore, the target base station will determine the entire cached data #3 as an illegal packet, resulting in unexpected operations such as packet loss. If the packet header includes relevant information about the PDU set, then when the target base station parses the packet header, there are unknown fields in the packet header. Therefore, the target base station will determine the entire cached data #3 as an illegal packet, resulting in unexpected operations such as packet loss. Method 2: The target base station parses cached data #3 using a conventional format. During the parsing process, the target base station may treat the remaining portion of the packet except the header as the data payload, which may cause the target base station to experience parsing errors.

[0156] Therefore, for a target base station that does not support PDU set processing, the relevant information of the PDU set carried in cache data #3 cannot be understood, resulting in unexpected operations such as data parsing errors or packet loss.

[0157] To address the above issues, the present invention provides a data processing method and apparatus, which will be described in detail below with reference to FIG6 to FIG14.

[0158] Figure 6 is a flow chart of a data processing method provided in an embodiment of the present application, which is applied to an inter-station handover process.

[0159] S610: Receive a first cached data packet, where a first extended header of the first cached data packet includes first information.

[0160] Among them, the first information may include at least one of the following relevant information of the PDU set: the serial number of the PDU set, the PDU sequence number within the PDU set, the size of the PDU set, the end PDU of the PDU set, the importance of the PDU set, and the end PDU of the data burst to which the PDU set belongs.

[0161] S620: Determine the information position of the first information in the first extended header.

[0162] As a possible implementation, the first extended header includes a first field, the first field being used to indicate the size of the first extended header. The first extended header is parsed. The target base station determines the size of the field for which parsing is successful. The information location is determined based on the size of the first extended header and the size of the field for which parsing is successful. This will be described in detail below with reference to FIG7.

[0163] As a possible implementation, the first extension header includes a second field, the second field includes a new user plane protocol frame, and the new user plane protocol frame includes the first information. The target base station determines the location of the new user plane protocol frame as the information location. The following will be described in detail with reference to FIG8

[0164] In the above technical solution, by identifying the information position of the first information in the first extended header, it helps the core network or the target base station to correctly process the first cached data packet, and can avoid target base station data parsing errors caused by capability mismatch between base stations, thereby ensuring normal transmission of user data.

[0165] Optionally, in S630, during the processing of the first cached data packet, the first information is not processed according to the information location.

[0166] It should be understood that the target base station in the inter-station handover may execute S630. Specifically, after not processing the first information, the target base station may continue to process the first buffered data packet. For example, the target base station may continue to parse the next extension header. In another example, the target base station may continue to process the data payload.

[0167] In the above technical solution, when the target base station does not have the ability to process the first information, for example, when the target base station does not have the ability to process the PDU set, the target base station can identify the location of the first information and ignore and not process the first information, thereby avoiding target base station data parsing errors caused by mismatching capabilities between base stations, thereby ensuring normal transmission of user data.

[0168] Optionally, in S640, when the target base station does not have the capability to process the first information, the first information in the first cached data packet is removed according to the information location to determine the second cached data packet.

[0169] It should be understood that when the type of inter-station handover is NG handover, the core network may execute S640 .

[0170] Specifically, the core network obtains the processing capability of the target base station regarding the first information during the inter-station handover process; sends a second buffered data packet to the target base station

[0171] Figure 7 is a schematic diagram of the format of an extension header provided in an embodiment of the present application. As shown in Figure 7, the header of the first cached data packet includes N extension headers, where N is a positive integer. The first extension header can be any one of the N extension headers. The structure of the nth extension header is described in detail below at step S620. The following detailed description takes the example of the first information including information related to the PDU set.

[0172] As shown in FIG7 , the nth extended header includes an extended header length #n field, an extended header content #n field, and a next extended header type #n field in sequence.

[0173] It should be understood that the Extended Header Length #n field is used to indicate the number of bytes occupied by the nth extended header. Assuming that the nth extended header occupies M bytes, where M is a positive integer greater than 2, the Extended Header Length #n field occupies 1 byte, the Next Extended Header Type #n field occupies 1 byte, and the Extended Header Content #n field occupies M-2 bytes. That is, the Extended Header Length #n field includes the first byte, the Extended Header Content #n field includes bytes 2 to M-1, and the Next Extended Header Type #n field includes the Mth byte.

[0174] It should also be understood that the extended header content #n field includes a first user plane protocol frame, and the first user plane protocol frame includes related information of a first PDU type and a PDU set, wherein the first PDU type is used to indicate the type of the first user plane protocol frame.

[0175] The embodiment of the present application does not limit the number of first user plane protocol frames, which can be one or more. Therefore, relevant information of the PDU SET can be added to one or more first user plane protocol frames. In addition, the embodiment of the present application does not limit the type of the first user plane protocol frame. For example, for the Xn interface, the first user plane protocol frame includes three first PDU type values: 0, 1, and 2.

[0176] It should also be understood that the Next Extension Header Type #n field is used to indicate the type of the (n+1)th extension header. For example, for an Xn interface, the type of the (n+1)th extension header is a RAN container used for exchanging data information on the Xn interface. For another example, for an NG interface, the type of the (n+1)th extension header is a PDU session container used for exchanging data information on the NG interface. For another example, when there are no other extension headers following the nth extension header, the value of the Next Extension Header Type #n field may be 0.

[0177] In a possible implementation of S620, taking the example of the first information including the relevant information of the PDU set, the information location of the relevant information of the PDU set may be determined specifically through the following steps.

[0178] S1. The target base station parses the fields in the first extended header in sequence, and determines the size of the first extended header according to the first field of the first extended header.

[0179] It should be understood that the first field may also be referred to as an extended header length field.

[0180] S2. The target base station parses the second field and determines the size of the field that is successfully parsed.

[0181] It should be understood that the second field may also be referred to as an extended header content field.

[0182] S3. Determine the information position of the relevant information of the PDU set in the first extension header according to the size of the first extension header and the size of the field determined to be successfully parsed.

[0183] Specifically, assuming the size of the first extended header is M bytes, S1 determines that the size of the first extended header is M bytes, the first field corresponds to the first byte, the second field corresponds to the second to the M-1 bytes, and the third field corresponds to the M-1 byte. The third field can also be called the next extended header type field. S2 determines that the size of the successfully parsed field is P bytes, that is, the second to the 2+P-1 bytes of the second field are the portion successfully parsed by the target base station, where P≤M-2 and P is a positive integer. S3 determines that the relevant information of the PDU SET is located in the corresponding 2+P to M-1 bytes.

[0184] For example, if S1 determines that the size of the first extended header is 10 bytes, the first field corresponds to the first byte, the second field corresponds to bytes 2 to 9, and the third field corresponds to byte 10. S2 determines that the size of the successfully parsed field is 6 bytes, meaning that bytes 2 to 7 of the second field are the portion successfully parsed by the target base station. S3 determines that the relevant information for the PDU SET is located in bytes 8 to 9.

[0185] Figure 8 is a schematic diagram of another extended header format provided by an embodiment of the present application. As shown in Figure 8, the data packet header of the first cached data packet includes N extended headers, where N is a positive integer. The first extended header can be any one of the N extended headers. The structure of the nth extended header is described in detail below at step S620. The following detailed description takes the example of the first information including relevant information about the PDU set.

[0186] As shown in Figure 8, the nth extension header includes, in sequence, an extension header length #n field, an extension header content #n field, and a next extension header type #n field. It should be understood that the difference between the nth extension header in Figure 8 and the nth extension header in Figure 7 is that the extension header content #n of the nth extension header in Figure 8 includes a second user plane protocol frame, which is a new user plane protocol frame. The second user plane protocol frame includes information related to a second PDU type and a PDU set. The second PDU type is used to indicate the type of the second user plane protocol frame.

[0187] Among them, the new user plane protocol frame can be indicated by a new PDU type. For example, for the Xn interface, the type of the first user plane protocol frame includes three types of first PDU type values: 0, 1, and 2. The new user plane protocol frame can be indicated by the value corresponding to the new PDU type. For example, the value of the second PDU type can be 3. It should be understood that the new user plane protocol frame type is for the capabilities of the target base station. In one possible implementation, the new user plane protocol frame type is a protocol frame type that is not defined in the protocol version followed by the target base station. In another possible implementation, the new user plane protocol frame type is a protocol frame type that the target base station does not support processing.

[0188] Among them, the detailed explanation of other fields in the nth extension header can be referred to Figure 7, which will not be repeated here.

[0189] For another possible implementation of S620, taking the example where the first information includes relevant information of the PDU set, the information location of the relevant information of the PDU set may be determined specifically through the following steps.

[0190] S1. The target base station parses the fields in the first extended header in sequence, and determines the size of the first extended header according to the first field of the first extended header.

[0191] It should be understood that the first field may also be referred to as an extended header length field.

[0192] S2. The target base station parses the second field and determines that the second PDU type in the second field indicates that the second field is a new user plane protocol frame.

[0193] It should be understood that the second field may also be referred to as an extended header content field.

[0194] Exemplarily, for the Xn interface, the target base station parses the second field and determines that the value of the second PDU type is 3. Since for the user plane protocol frame of the Xn interface, the corresponding first PDU type has three values ​​0, 1, and 2, therefore, when the target base station identifies that the value of the second PDU type is 3, it can be determined that the second field includes a new user plane protocol frame.

[0195] It should be understood that the new user plane protocol frame type is specific to the capabilities of the target base station. In one possible implementation, the new user plane protocol frame type is a protocol frame type that is not defined in the protocol version followed by the target base station. In another possible implementation, the new user plane protocol frame type is a protocol frame type that the target base station does not support or process.

[0196] S3: Determine the location of the new user plane protocol frame as the information location.

[0197] Specifically, assuming that the size of the first extension header is M bytes, S1 determines that the size of the first extension header is M bytes, the first field corresponds to the first byte, the second field corresponds to the second byte to the M-1th byte, and the third field corresponds to the Mth byte. The third field can also be called the next extension header type field. S2 determines that the new user plane protocol frame corresponds to the second byte to the M-1th byte. S3 determines that the relevant information of the PDU set is located in the corresponding second byte to the M-1th byte.

[0198] For example, assuming the size of the first extension header is 10 bytes, S1 determines that the size of the first extension header is 10 bytes, the first field corresponds to the first byte, the second field corresponds to bytes 2 to 9, and the third field corresponds to the tenth byte. The third field can also be called the next extension header type field. S2 determines that the new user plane protocol frame corresponds to bytes 2 to 9. S3 determines that the relevant information of the PDU set is located in the corresponding bytes 2 to 9.

[0199] It should be understood that the first buffered data packet including the first extension header in the format of Figures 7 and 8 can be directly transmitted through the Xn interface between the source base station and the target base station via S315 of Figure 3(a). Alternatively, the first buffered data packet including the first extension header in the format of Figures 7 and 8 can also be transmitted through the NG interface between the source base station and the core network and the NG interface between the core network and the target base station via S325a and S325b of Figure 3(b).

[0200] For the indirect communication between the source base station and the target base station achieved by forwarding via the core network through the NG interface, further improvements may be made to S325a and S325b in FIG. 3( b ).

[0201] Figure 9 is a schematic diagram of the interaction flow of a data processing method provided by an embodiment of the present application. The following is an example of the first information including relevant information of the PDU set. The interaction schematic diagram shown in Figure 9 takes the source base station, target base station and core network in the NG switching process as the execution subjects of the interaction schematic as an example to illustrate the corresponding method, but the present application does not limit the execution subjects of the interaction schematic. For example, the source base station in Figure 9 can also be a chip, chip system or processor that supports the source base station to implement the corresponding method, or a logic module or software that can implement all or part of the functions of the source base station. The target base station in Figure 9 can also be a chip, chip system or processor that supports the target base station to implement the corresponding method, or a logic module or software that can implement all or part of the functions of the target base station. The core network in Figure 9 can also be a chip, chip system or processor that supports the core network to implement the corresponding method, or a logic module or software that can implement all or part of the functions of the core network.

[0202] S901: A source base station sends a first buffered data packet to a core network, where the first buffered data packet includes relevant information of a PDU set.

[0203] It should be understood that the first cached data packet sent by the source base station to the core network can be transmitted through one or more of AMF, SMF and UPF, and the embodiment of the present application does not limit this.

[0204] S902: The core network obtains the PDU set processing capability of the target base station.

[0205] As a possible implementation manner, if the target base station has sent the target base station's processing capability regarding the PDU set to the core network, the core network may directly obtain the target base station's processing capability regarding the PDU set from the storage device.

[0206] As a possible implementation manner, if the core network does not know the processing capability of the target base station regarding the PDU set in advance, the core network may send query information to the target base station to obtain the processing capability of the target base station regarding the PDU set.

[0207] As a possible implementation method, if the core network does not know the target base station's processing capability of the PDU set in advance, after the target base station passes S321b shown in Figure 3 (b), that is, after the target base station receives the switching request #3, the target base station feeds back its own processing capability of the PDU set to the core network.

[0208] S903: When the target base station does not have the PDU set processing capability, remove the PDU set related information in the first buffered data packet to determine a second buffered data packet.

[0209] As a possible implementation method, when the format of the first extended header in the first cache data packet is as shown in Figure 7 or Figure 8, the core network can locate and remove the relevant information of the PDU set in the first extended header of the first cache data packet by determining the position of the relevant information of the PDU set in Figure 7 or Figure 8 in the first extended header.

[0210] As a possible implementation manner, the core network can correctly parse out the relevant information of the PDU set, and the core network can directly remove the relevant information of the PDU set from the first cached data packet.

[0211] S904: The core network sends a second buffered data packet to the target base station.

[0212] In the above technical solution, for NG switching, the core network first receives the first cached data packet. When the target base station does not support PDU set processing, the relevant information of the PDU set that the target base station cannot recognize can be removed in advance, thereby avoiding unexpected situations that may occur during the data parsing process of the target base station, such as packet loss or parsing errors, and thus ensuring normal data processing.

[0213] During the inter-station handover process, the base station capabilities do not match. In addition to the situation where the source base station has the PDU set processing capability and the target base station does not have the PDU set processing capability, there is also the situation where the source base station does not have the PDU set processing capability and the target base station has the PDU set processing capability.

[0214] Figure 10 is a flow chart of another inter-station handover process for an XR service provided by an embodiment of the present application. Assume that the source base station in Figure 10 does not support processing PDU sets, the target base station supports processing PDU sets, and the terminal device is running an XR service (for example, receiving XR video from an XR server) and expects that the data of the XR service can obtain QoS guarantees based on PDU sets. Among them, the source base station and the target base station shown in Figure 10 can communicate directly through the Xn interface.

[0215] S1001: The core network sends a QoS guarantee requirement of a PDU set to a source base station.

[0216] The QoS guarantee requirement may include a QoS profile of the QoS parameters of the PDU set.

[0217] S1002: The source base station sends capability indication information to the core network according to the QoS configuration file. The capability indication information is used to indicate that the source base station does not have the PDU set processing capability.

[0218] S1003 : The core network sends third XR data to the source base station, where the third XR data does not include relevant information of the PDU set.

[0219] S1004: The source base station processes the third XR data based on the relevant information of the PDU.

[0220] S1005: The source base station sends the processed third XR data to the terminal device.

[0221] The terminal device is currently in the source cell of the source base station. Assuming that the terminal device moves, the terminal device expects to switch to the target cell of the target base station.

[0222] S1006 : The source base station sends a handover request # 4 to the target base station. The handover request # 4 includes the QoS profile of the QoS flow where the third XR data is located, but does not include the QoS parameters of the PDU set.

[0223] It should be understood that after receiving the handover request #4, the target base station usually does not proactively send its own processing capability of the PDU set to the core network because the QoS parameters of the PDU set are not included.

[0224] The following steps are for the target base station not to feed back any information about its own processing capability of the PDU set to the core network because it does not recognize any QoS parameters of the PDU set in the handover request #4. That is, the following steps are not the steps executed in S1007.

[0225] S1008: The target base station performs admission control based on the cell load, capability, etc., and determines the handover request feedback message #4.

[0226] Among them, the handover request feedback message #4 and the handover request feedback message #1 have similar functions and are not described in detail here.

[0227] S1009: The source base station sends a handover command #4 to the UE, wherein the handover command #4 is used to instruct the UE to access the target cell.

[0228] S1010: The source base station no longer processes data with the UE, and sends the buffered data #4 to the target base station.

[0229] The buffered data #4 is the third XR data that has been buffered in the source base station. Therefore, the data packet header of the buffered data #4 does not carry the relevant information of the PDU set.

[0230] S1011, the terminal device and the target base station complete access to the target cell.

[0231] S1012: The target base station sends a handover completion message to the core network.

[0232] S1013: The core network sends fourth XR data to the target base station. The fourth XR data does not include relevant information of the PDU set.

[0233] It should be understood that since the core network does not know whether the target base station supports processing PDU set, the data transmission between the core network and the target base station is the traditional PDU-based transmission method. That is, the fourth XR data includes relevant information about the PDU, rather than relevant information about the PDU set. The terminal device expects that the data of the XR service can obtain QoS guarantee based on the PDU set. Even if the target base station has the processing capability of the PDU set, since the core network does not provide any PDU set QoS parameters and / or PDU set related information in the fourth XR data, the target base station cannot provide the terminal device with PDU set-based services, that is, the terminal device's PDU set guarantee requirements can never be met.

[0234] S1014: The target base station processes the fourth XR data according to the relevant information of the PDU.

[0235] S1015: The target base station sends the processed fourth XR data to the terminal device.

[0236] Optionally, after receiving the handover request #4, the target base station may also execute S1007, where the target base station sends capability indication information to the core network, where the capability indication information is used to indicate whether the target base station supports processing the PDU set.

[0237] In this case, after receiving the handover request #4, the target base station reports its own processing capabilities for the PDU set to the core network. In other words, the target base station needs to respond to each handover request, even if the terminal device being handed over does not have any requirements based on PDU set processing, and even if the terminal device may not be performing any XR-related services. As a result, in many cases, it is meaningless for the target base station to report support information to the core network. Instead, it will increase the burden of signaling interaction between the base station and the core network and reduce network efficiency. In the current actual network, the number of terminal devices related to non-XR services far exceeds that of XR-related terminal devices, and handovers always occur frequently. If the above solution is adopted, the base station will generate and send a large amount of useless information to the core network.

[0238] To address the above issues, Figure 11 is a schematic diagram of an interaction flow of another data processing method provided by an embodiment of the present application. In Figure 11, the source base station does not have the PDU set processing capability, while the target base station has the PDU set processing capability.

[0239] S1101a, the source base station obtains the first capability information of the terminal device regarding the PDU set.

[0240] It should be understood that after the terminal device accesses the source base station, the terminal device sends the first capability information to the source base station.

[0241] Among them, the first capability information can be used to indicate at least one of the following information: the first capability information is used to indicate whether the terminal device supports the ability to identify the PDU set; the first capability information is used to indicate whether the terminal device supports the ability to process the PDU set; the first capability information is used to indicate whether the terminal device supports the ability to discard the PDU set; the first capability information is used to indicate whether the terminal device supports the ability to discard the PDU set based on the importance of the PDU set.

[0242] Optionally, the source base station may also obtain second capability information of the terminal device regarding the XR service.

[0243] It should be understood that after the terminal device accesses the source base station, the terminal device sends the second capability information to the source base station.

[0244] The second capability information may be used to indicate at least one of the following information: the second capability information is used to indicate whether the terminal device supports the capability information of reporting auxiliary information related to XR services, for example, the auxiliary information may include burst arrival time or jitter range, etc. The second capability information is used to indicate whether the terminal device supports the capability information of reporting remaining data time, and the second capability information is used to indicate whether the terminal device supports the capability information of discontinuous reception cycle based on rational numbers.

[0245] It should be understood that the source base station can also obtain other capability information related to XR services or PDU set processing, and the embodiments of the present application are not limited to this.

[0246] S1101b, the source base station obtains the wireless resource configuration information of the terminal device regarding the XR service.

[0247] It should be understood that although the source base station does not support PDU set processing, the source base station may still support other XR service-related functions. Therefore, the source base station will send wireless resource configuration information about the XR service to the terminal device.

[0248] The radio resource configuration information may be other radio resource configuration information such as radio resource control (RRC) configuration information. The RRC configuration information may be at least one of the following configuration information: configuration information for a discontinuous reception period based on a rational number; configuration information for reporting remaining data time; and configuration information for reporting auxiliary information related to XR services. For example, the auxiliary information may include a burst arrival time or a jitter range.

[0249] It should be understood that the source base station can also obtain other configuration information related to XR services or PDU set processing, and the embodiments of the present application are not limited to this.

[0250] S1102: The source base station sends a first handover request to the target base station, where the first handover request includes first capability information or radio resource configuration information.

[0251] Optionally, the first handover request may further include first capability information and radio resource configuration information.

[0252] Optionally, the first switching request may further include second capability information.

[0253] S1103: The target base station sends first indication information to the core network according to the first handover request. The first indication information is used to indicate whether the target base station has a PDU set processing capability.

[0254] It should be understood that since the source base station does not support PDU set processing, the QoS parameters of the PDU set are not included in the first switching request. The target base station can still determine that the terminal device may have PDU set processing requirements based on at least one of the first capability information, wireless resource configuration information and second capability information included in the first switching request.

[0255] Likewise, if the first switching request does not include at least one of the first capability information, the wireless resource configuration information, and the second capability information, the target base station may determine that the terminal device has no processing requirements for the PDU set.

[0256] For example, the first capability information is the terminal device's processing capability regarding the PDU set. The target base station can determine, based on the first capability information, that the terminal device during the inter-station switching process has a PDU set processing requirement.

[0257] For example, the second capability information and the wireless resource configuration information are both related to the XR service of the terminal device. Although the source base station does not support processing PDU sets, the source base station can support the functions of other XR services. The XR service may need to process PDU sets. Therefore, the target base station can determine that the terminal device has PDU set processing requirements based on the second capability information and / or wireless resource configuration information.

[0258] As a possible implementation manner, the first indication information may be carried in a path switch request message (path switch request).

[0259] Optionally, in S1104 , when the target base station has the capability to process the PDU set, the core network sends the quality of service (QoS) parameters of the PDU set corresponding to the XR service to the target base station.

[0260] Optionally, when the core network sends a data packet for the XR service to the target base station, the data packet for the XR service may further include relevant information of the PDU set.

[0261] In the above technical solution, the target base station can determine that the terminal device has a PDU set processing requirement based on at least one of the first capability information about the terminal device for processing PDU sets or the radio resource information about the XR service carried in the first handover request. In this way, even if the source base station does not have the PDU set processing capability, the target base station can report to the core network based on this information whether it supports the PDU set processing capability, thereby enabling PDU set-based service guarantee for the terminal device.

[0262] Compared to the case where the target base station only reports its own PDU set processing capability based on the QoS parameters of the PDU set, the solution of the embodiment of the present application can better cope with the situation where the source base station does not have the PDU set processing capability but the target base station has the PDU set processing capability, thereby enabling subsequent PDU set-based service guarantees for the terminal device.

[0263] Compared to the target base station reporting its own PDU set processing capability to the core network in response to any switching request, the target base station in the solution of the present application reports its own PDU set processing capability to the core network only when the terminal device has a PDU set processing requirement, which can reduce meaningless reporting. For example, if the terminal device has no PDU set processing requirement, the target base station does not need to report its own PDU set processing capability to the core network.

[0264] It should be understood that the core network shown in FIG9 can obtain whether the target base station has the PDU set processing capability in the manner shown in FIG11 .

[0265] The data processing method provided by the embodiment of the present application is described in detail above with reference to Figures 6 to 11. It is understood that in order to implement the above functions, it includes hardware structures and / or software modules corresponding to executing each function.

[0266] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for specific applications, but such implementation should not be considered to be beyond the scope of this application.

[0267] The data processing device provided in the embodiments of the present application is described in detail below with reference to Figures 12 to 14. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment above. For the sake of brevity, some contents are not repeated here.

[0268] Figure 12 is a schematic diagram of a data processing device 1200 provided in an embodiment of the present application. The device 1200 may include a processing unit 1220, which is used to perform data processing. The device 1200 may also include a transceiver unit 1210, which may implement corresponding communication functions. The transceiver unit 1210 may also be referred to as a communication interface or a communication unit or an interface unit. It should be understood that for the operations such as sending and receiving involved in this application, if there is no special explanation, or if it does not conflict with its actual function or internal logic in the relevant description, it can be more generally understood as operations such as output and input, rather than sending and receiving operations directly performed by the radio frequency circuit and antenna.

[0269] Optionally, the device 1200 may further include a storage unit, which may be used to store instructions and / or data. The processing unit 1220 may read the instructions and / or data in the storage unit so that the device implements the aforementioned method embodiment.

[0270] The device 1200 can be used to execute the actions performed by the source base station in the above method embodiment. In this case, the device 1200 can be a communication device or a component that can be configured in a communication device. The transceiver unit 1210 is used to execute the transceiver-related operations on the communication device side in the above method embodiment, and the processing unit 1220 is used to execute the processing-related operations of the source base station in the above method embodiment.

[0271] As a design, the apparatus 1200 is configured to execute the actions performed by the target base station or core network during the inter-station handover process in the method embodiments shown in Figures 6 to 9 above. The execution entity may be a chip, chip system, or processor that supports the target base station or core network in implementing the corresponding method, or a logic module or software that can implement all or part of the functions of the target base station or core network.

[0272] Specifically, the transceiver unit 1210 is configured to receive a first cached data packet, where a first extended header of the first cached data packet includes first information.

[0273] The processing unit 1220 is configured to determine an information position of the first information in the first extended header.

[0274] For details not described in detail, please refer to the above method embodiment.

[0275] As a design, the data processing device 1200 is used to execute the actions performed by the target base station in the method embodiment shown in Figure 11 above. The execution subject can be a chip, chip system, or processor that supports the target base station in implementing the corresponding method, or it can be a logic module or software that can implement all or part of the functions of the target base station.

[0276] Specifically, the transceiver unit 1210 is configured to receive a first handover request, where the first handover request includes first capability information of a terminal device regarding a protocol data unit (PDU) set or wireless resource configuration information of the terminal device related to an extended reality (XR) service. The processing unit 1220 is configured to send first indication information to the core network based on the first handover request, where the first indication information is used to indicate whether the target base station has the PDU set processing capability.

[0277] For details not described in detail, please refer to the above method embodiment.

[0278] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0279] The processing unit 1220 in the above embodiment may be implemented by at least one processor or processor-related circuits. The transceiver unit 1210 may be implemented by a transceiver or transceiver-related circuits. The storage unit may be implemented by at least one memory.

[0280] FIG13 is a schematic structural diagram of a data processing device 1300 provided in an embodiment of the present application.

[0281] As shown in Figure 13, an embodiment of the present application further provides a data processing device 1300. The device 1300 includes a processor 1310, which is coupled to a memory 1320. The memory 1320 is used to store computer programs or instructions and / or data. The processor 1310 is used to execute the computer programs or instructions and / or data stored in the memory 1320, so that the method in the above method embodiment is executed.

[0282] Optionally, the device 1300 includes one or more processors 1310.

[0283] Optionally, as shown in FIG13 , the device 1300 may further include a memory 1320 .

[0284] Optionally, the memory 1320 included in the device 1300 may be one or more.

[0285] Optionally, the memory 1320 may be integrated with the processor 1310 or provided separately.

[0286] Optionally, as shown in Figure 13, the apparatus 1300 may further include a transceiver 1330, which is configured to receive and / or transmit signals. For example, the processor 1310 is configured to control the transceiver 1330 to receive and / or transmit signals.

[0287] As a solution, the device 1300 is used to implement the operations performed by the source base station, the target base station or the core network in the above method embodiment.

[0288] For example, the processor 1310 is used to implement the processing-related operations performed by the source base station, target base station or core network in the above method embodiment, and the transceiver 1330 is used to implement the transceiver-related operations performed by the source base station, target base station or core network in the above method embodiment.

[0289] FIG14 is a schematic diagram of a chip system 1400 provided in an embodiment of the present application, as shown in FIG14 . The chip system 1400 (or it may also be referred to as a processing system) includes a logic circuit 1410 and an input / output interface 1420. The logic circuit is used to couple with the input interface and transmit data parameters through the input / output interface to execute the method in the above method embodiment. The device in which the chip system 1400 is installed can implement the method and function of the embodiment of the present application. For example, the logic circuit 1410 can be a processing circuit in the chip system 1400, which controls the device in which the chip system 1400 is installed. It can also be coupled to a storage unit and call instructions in the storage unit so that the device can implement the method and function of the embodiment of the present application. The input / output interface 1420 can be an input / output circuit in the chip system 1400, which outputs information processed by the chip system 1400, or inputs data or signaling information to be processed into the chip system 1400 for processing.

[0290] As a solution, the chip system 1400 is used to implement the operations performed by the data processing device (such as the source base station, the target base station or the core network) in the above method embodiments.

[0291] For example, the logic circuit 1410 is used to implement the processing-related operations performed by the source base station, target base station or core network in the above method embodiment, and the input / output interface 1420 is used to implement the sending and receiving-related operations performed by the source base station, target base station or core network in the above method embodiment.

[0292] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the method executed by a data processing device (such as a source base station, a target base station or a core network) in the above method embodiment.

[0293] For example, when the computer program is executed by a computer, the computer can implement the method performed by the data processing device (such as the source base station, the target base station or the core network) in the above method embodiment.

[0294] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method performed by a data processing device (such as a source base station, a target base station, or a core network) in the above method embodiment.

[0295] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0296] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0297] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0298] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0299] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0300] Those skilled in the art will appreciate that the units and steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of protection of this application.

[0301] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0302] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to implement the solutions provided in this application based on actual needs.

[0303] In addition, each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist physically separately, or two or more units may be integrated into one unit.

[0304] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium may include, but is not limited to, various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0305] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A data processing method, characterized in that: The method is applied to an inter-station handover process, comprising: receiving a first cache data packet, wherein a first extension header of the first cache data packet includes first information; An information position of the first information in the first extended header is determined.

2. The method according to claim 1, characterized in that The first information includes at least one of the following related information of the protocol data unit PDU set: the sequence number of the PDU set, the PDU sequence number within the PDU set, the size of the PDU set, the end PDU of the PDU set, the importance of the PDU set, and the end PDU of the data burst to which the PDU set belongs.

3. The method according to claim 1 or 2, characterized in that: The first extension header includes a first field, where the first field is used to indicate a size of the first extension header; Determining the information position of the first information in the first extension header includes: Parsing the first extension header to determine the size of the field that is parsed successfully; The information position is determined according to the size of the first extension header and the size of the successfully parsed field.

4. The method according to claim 1 or 2, characterized in that: The first extended header includes a second field, the second field includes a new user plane protocol frame, and the new user plane protocol frame includes the first information; Determining the information position of the first information in the first extension header includes: The position of the new user plane protocol frame is determined as the information position.

5. The method according to any one of claims 1 to 4, characterized in that: When the method is applied to a target base station in an inter-station handover process, the target base station does not have the ability to process the first information, and the method further includes: During the processing of the first cache data packet, the first information is not processed according to the information position.

6. The method according to any one of claims 1 to 4, characterized in that: When the method is applied to a core network in an inter-station handover process, the method further includes: Acquire a processing capability of a target base station regarding the first information during the inter-station handover; When the target base station does not have the ability to process the first information, removing the first information from the first cached data packet according to the information position to determine a second cached data packet; Send the second cached data packet to the target base station.

7. A data processing method, characterized in that: The method is applied to a target base station during an inter-station handover process, and includes: Receive a first switching request, where the first switching request includes first capability information of a terminal device regarding a protocol data unit (PDU) set or wireless resource configuration information of the terminal device related to an extended reality (XR) service; According to the first switching request, first indication information is sent to the core network, where the first indication information is used to indicate whether the target base station has a PDU set processing capability.

8. The method according to claim 7, characterized in that The first capability information is used to indicate at least one of the following information: The first capability information is used to indicate whether the terminal device supports the identification capability of the PDU set; The first capability information is used to indicate whether the terminal device supports the processing capability of the PDU set; The first capability information is used to indicate whether the terminal device supports the discard capability of the PDU set; The first capability information is used to indicate whether the terminal device supports the capability of discarding the PDU set based on the importance of the PDU set.

9. The method according to claim 7, characterized in that: The radio resource configuration information includes radio resource control (RRC) configuration information, and the RRC configuration information includes at least one of the following information: Configuration information of discontinuous reception cycles based on rational numbers; Configuration information for reporting remaining data time; Configuration information for reporting auxiliary information related to the XR service.

10. The method according to any one of claims 7 to 9, characterized in that: The first indication information is carried in a path switching request message.

11. The method according to any one of claims 7 to 10, characterized in that: The method further comprises: Receive the quality of service parameters of the PDU set corresponding to the XR service from the core network.

12. A data processing device, characterized in that: The device comprises a transceiver unit and a processing unit: The transceiver unit is used to receive a first cache data packet, wherein a first extension header of the first cache data packet includes first information; The processing unit is used to determine an information position of the first information in the first extended header.

13. The device according to claim 12, characterized in that The first information includes at least one of the following related information of the protocol data unit PDU set: the sequence number of the PDU set, the PDU sequence number within the PDU set, the size of the PDU set, the end PDU of the PDU set, the importance of the PDU set, and the end PDU of the data burst to which the PDU set belongs.

14. The device according to claim 12 or 13, characterized in that The first extension header includes a first field, where the first field is used to indicate a size of the first extension header; The processing unit is specifically used for: Parsing the first extension header to determine the size of the field that is parsed successfully; The information position is determined according to the size of the first extension header and the size of the successfully parsed field.

15. The device according to claim 12 or 13, characterized in that The first extended header includes a second field, the second field includes a new user plane protocol frame, and the new user plane protocol frame includes the first information; The processing unit is specifically used for: The position of the new user plane protocol frame is determined as the information position.

16. The device according to any one of claims 12 to 15, characterized in that When the device is a target base station in an inter-station handover process, the target base station does not have the ability to process the first information, and the processing unit is further used to: During the processing of the first cache data packet, the first information is not processed according to the information position.

17. The device according to any one of claims 12 to 15, characterized in that When the device is a core network in an inter-station handover process, the processing unit is further configured to: Acquire a processing capability of a target base station regarding the first information during the inter-station handover; When the target base station does not have the ability to process the first information, removing the first information from the first cached data packet according to the information position to determine a second cached data packet; The transceiver unit is further configured to send the second cached data packet to the target base station.

18. A data processing device, characterized in that: The device comprises a transceiver unit and a processing unit: The transceiver unit is used to receive a first switching request, where the first switching request includes first capability information of a terminal device regarding a protocol data unit PDU set or wireless resource configuration information of the terminal device related to an extended reality XR service; The processing unit is used to send first indication information to the core network according to the first switching request, where the first indication information is used to indicate whether the target base station has a PDU set processing capability.

19. The device according to claim 18, characterized in that The first capability information is used to indicate at least one of the following information: The first capability information is used to indicate whether the terminal device supports the identification capability of the PDU set; The first capability information is used to indicate whether the terminal device supports the processing capability of the PDU set; The first capability information is used to indicate whether the terminal device supports the discard capability of the PDU set; The first capability information is used to indicate whether the terminal device supports the capability of discarding the PDU set based on the importance of the PDU set.

20. The device according to claim 18, characterized in that The radio resource configuration information includes radio resource control (RRC) configuration information, and the RRC configuration information includes at least one of the following information: Configuration information of discontinuous reception cycles based on rational numbers; Configuration information for reporting remaining data time; Configuration information for reporting auxiliary information related to the XR service.

21. The device according to any one of claims 18 to 20, characterized in that The first indication information is carried in a path switching request message.

22. The device according to any one of claims 18 to 21, characterized in that The transceiver unit is also used for: Receive the quality of service parameters of the PDU set corresponding to the XR service from the core network.

23. A data processing device, characterized in that: The device comprises a processor, the processor is coupled to a memory, the memory is used to store a computer program or instruction, and the processor is used to execute the computer program or instruction in the memory, so that the device performs the method according to any one of claims 1 to 11.

24. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 11.

25. A chip, characterized in that: The chip is coupled to a memory and is used to read and execute program instructions stored in the memory to implement the method according to any one of claims 1 to 11.

Images