Information processing method, entity, network device, communication system, and storage medium

Abstract

Embodiments of the present disclosure provide an information processing method, an entity, a network device, a communication system, and a storage medium. The method comprises: a first entity receives at least one type of data packet. The data packet comprises at least one of the following: a first-type data packet, wherein the first-type data packet is associated with or belongs to a first data packet set; and a second-type data packet, wherein the second-type data packet is not associated with or does not belong to a data packet set. Thus, the first entity can obtain the first-type data packet and / or the second-type data packet, so that the first entity can further process the first-type data packet belonging to or associated with the first data packet set, and / or the first entity can further process the second-type data packet which does not belong to or is not associated with a second data packet set.

Description

Information processing method, entity, network device, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an information processing method, entity, network equipment, communication system and storage medium. Background Art

[0002] Currently, in the field of wireless communication technology, network equipment can process data packets (Packets); for example, it can send and / or discard data packets.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure need to solve the problem of processing different types of data packets.

[0005] According to a first aspect of an embodiment of the present disclosure, an information processing method is proposed, including: a first entity receives at least one type of data packet, wherein the data packet includes at least one of the following: a first type of data packet, wherein the first type of data packet is associated with or belongs to a first data packet set; a second type of data packet, wherein the second type of data packet is not associated with or does not belong to a data packet set.

[0006] According to a second aspect of an embodiment of the present disclosure, an information processing method is proposed, including: a network device sends configuration information, wherein the configuration information is used by a terminal or a Packet Data Convergence Protocol (PDCP) entity to determine the PSI level of a second type of data packet; the second type of data packet is not associated with or does not belong to a data packet set.

[0007] According to a third aspect of an embodiment of the present disclosure, a first entity is proposed, comprising: a first transceiver module, configured to receive at least one type of data packet, wherein the data packet comprises at least one of the following: a first type of data packet, wherein the first type of data packet is associated with or belongs to a first data packet set; and a second type of data packet, wherein the second type of data packet is not associated with or does not belong to a data packet set.

[0008] In the fourth aspect of the embodiments of the present disclosure, a network device is proposed, including: a second transceiver module, configured to send configuration information, wherein the configuration information is used by the terminal or PDCP entity to determine the PSI level of the second type of data packet; the second type of data packet is not associated with or does not belong to a data packet set.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a first entity is proposed, comprising: one or more processors; wherein the first entity is configured to execute an optional implementation of the first aspect.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a network device is proposed, comprising: one or more processors; wherein the above-mentioned network device is used to execute the optional implementation method of the second aspect.

[0011] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising: a first entity and a network device; wherein the first entity is configured to execute the method described in the optional implementation manner of the first aspect, and the network device is configured to execute the method described in the optional implementation manner of the second aspect.

[0012] According to the eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0013] The embodiments of the present disclosure can solve the problem of processing different types of data packets. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0015] FIG1 is a schematic structural diagram of an information processing system according to an embodiment of the present disclosure.

[0016] FIG2 is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.

[0017] FIG3A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0018] FIG3B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0019] FIG3C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0020] FIG3D is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0021] FIG3E is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0022] FIG3F is a flow chart of an information processing method according to an embodiment of the present disclosure.

[0023] FIG4A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0024] FIG4B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0025] FIG4C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0026] FIG5A is a schematic structural diagram of a first entity according to an embodiment of the present disclosure.

[0027] FIG5B is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0028] FIG6A is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0029] FIG6B is a schematic structural diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] The embodiments of the present disclosure provide an information processing method, an entity, a network device, a communication system, and a storage medium.

[0031] In a first aspect, an embodiment of the present disclosure proposes an information processing method, comprising: a first entity receives at least one type of data packet, wherein the data packet includes at least one of the following: a first type of data packet, wherein the first type of data packet is associated with or belongs to a first data packet set; a second type of data packet, wherein the second type of data packet is not associated with or does not belong to a data packet set.

[0032] In the above embodiment, the first entity can obtain the first category of data packets and / or the second category of data packets so that the first entity can perform further processing operations on the first category of data packets that belong to or are associated with the first data packet set, and / or so that the first entity can perform further processing operations on the second category of data packets that do not belong to or are not associated with the second data packet set.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining that a second type of data packet is associated with a second data packet set.

[0034] In the above embodiment, the second category data packets may be associated with a data packet set so that the data packet set contains only one second category data packet, thereby facilitating further processing operations on the second category data packets.

[0035] In combination with some embodiments of the first aspect, in some embodiments, determining that a second-class data packet is associated with a second data packet set includes at least one of the following: determining that a second-class data packet is included in a second data packet set; determining the QoS of the second-class data packet based on the Quality of Service (QoS) parameters of the second-class data packet.

[0036] In the above embodiment, the second-class data packet can be included in a second data packet set to achieve association with a data packet set. Alternatively, the QoS of the second-class data packet can be determined based on the QoS parameters of the second data packet set, thereby achieving association with a data packet set. Furthermore, association with a data packet set can be achieved in a variety of ways, adapting to a wider range of application scenarios.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the QoS of the second type of data packets is determined based on the quality of service QoS parameters of the second data packet set, including at least one of the following: determining the PDU error rate (PDU Error Rate, PSER) of the second type of data packets based on the PDU Set Error Rate (PSER) in the QoS parameters of the second data packet set; determining the PDU delay budget (PDU Delay Budget, PSDB) of the second type of data packets based on the PDU Set Delay Budget (PSDB) in the QoS parameters of the second data packet set.

[0038] In the above embodiment, the QoS (PSER and / or PSDB) of the second type of data packet can be determined by referring to the QoS parameters (such as PSER and / or PSDB) of the second data packet set, thereby associating a second type of data packet with the data packet set; and associating a second type of data packet with a data packet set can be achieved in a variety of ways, which can adapt to more application scenarios.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining a PSI level of the second category of data packets.

[0040] In the above embodiment, the first entity can clarify the PSI level of the second type of data packet, thereby facilitating subsequent packet loss operations on the second type of data.

[0041] In combination with some embodiments of the first aspect, in some embodiments, determining the PSI level of the second category data packet includes at least one of the following: determining the PSI level of the second category data packet according to a protocol agreement; determining the PSI level of the second category data packet according to a pre-defined definition; determining the PSI level of the second category data packet according to configuration information sent by a network device; wherein the configuration information is used to indicate the PSI level corresponding to at least one second category data packet.

[0042] In the above embodiment, the PSI level of the second-class data packets can be determined through various methods, such as protocol agreement, pre-definition, or network device configuration, thereby adapting to a wider range of application scenarios. Furthermore, if the PSI level of the second-class data packets is determined through protocol agreement or pre-definition, signaling overhead can be reduced. Alternatively, if the PSI level of the second-class data packets is determined through network device configuration, the network device and the terminal can still have a consistent understanding of the PSI level of the second-class data packets.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the PSI level of the second category of data packets is for one of the following: each PDCP entity; each terminal; each data packet.

[0044] In the above embodiment, the PSI level of the second-category data packet can be determined for each PDCP entity, each terminal, or each data packet, so that the PSI level of the second-category data packet can be determined at different granularities, which can adapt to more application scenarios. In addition, if the PSI level of each data packet is determined, a more accurate determination of the PSI level of at least one second-category data packet can be achieved; or, if the PSI level of the second-category data packet is determined for each PDCP entity, the PSI level of the second-category data packet of each data radio bearer (DRB) can be determined, thereby facilitating whether all second-category data packets received on the DRB are discarded. Or, if the PSI level of the second-category data packet is determined for each terminal, it is convenient to determine whether all second-category data packets received on the terminal are discarded.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining a timer duration corresponding to the PSI level of the second category data packet, wherein the timer duration is the duration for discarding the second category data packet.

[0046] In the above embodiment, the timing at which the second-category data packets of at least one PSI level are discarded can be clarified, thereby facilitating discarding the second-category data packets of different PSI levels at appropriate times.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the method also includes at least one of the following: discarding the second category of data packets when the timer corresponding to the PSI level of the second category of data packets expires; discarding the data packets in the same second data packet set as the second category of data when the timer corresponding to the PSI level of the second category of data packets expires.

[0048] In the above embodiment, when the timer of the PSI level of the second-class data packet expires, the corresponding second-class data packet can be discarded, or all data packets belonging to the same data packet set as the second-class data packet can be discarded, thereby reducing the sending of other data packets in the data packet set that do not need to be sent; this can save resources.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the method includes: determining a packet loss policy, wherein the packet loss policy is used to indicate that data packets are dropped when congestion occurs.

[0050] In the above embodiment, the first entity may determine a packet drop policy for at least one type of data packet when congestion occurs.

[0051] In combination with some embodiments of the first aspect, in some embodiments, determining the discard strategy includes one of the following: determining the packet loss strategy according to a protocol agreement; determining the packet loss strategy according to a pre-defined definition; determining the packet loss strategy according to first information sent by a network device; wherein the first information is used to indicate the packet loss strategy.

[0052] In the above embodiments, packet loss policies can be determined in a variety of ways, such as through protocol agreement, pre-definition, or network device configuration, thereby adapting to a wider range of application scenarios. Furthermore, if packet loss policies are determined through protocol agreement or pre-definition, signaling overhead can be reduced. Alternatively, if packet loss policies are determined through network device configuration, the network device and the terminal can maintain consistent understanding of packet loss.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the packet loss policy is used to indicate one of the following: whether to discard the second type of data packets first; or discard the data packets according to the PSI level of the data packets.

[0054] In the above embodiment, it is possible to prioritize discarding second-category packets during congestion, thereby enabling the selection of second-category packets, which are likely to be of relatively lower importance, from first-category packets and second-category packets for discarding, thereby facilitating network communication. Alternatively, packets can be discarded based on their PSI levels during congestion, thereby accurately selecting packets of relatively lower importance for discarding.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the first information is sent when the network device detects congestion.

[0056] In the above embodiment, the first entity may receive the first information sent by the network device when data packet congestion is detected, so that the first entity can promptly determine the data packets that need to be discarded according to the first information.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the first entity is a PDCP entity of the terminal.

[0058] In the above embodiment, the terminal or the PDCP entity of the terminal can implement the processing operation of the data packet.

[0059] In combination with some embodiments of the first aspect, in some embodiments, the first entity is a PDCP entity of an access network device.

[0060] In the above embodiment, the access network device (such as a base station) or the PDCP entity of the access network device can implement the processing operation on the data packet.

[0061] In a second aspect, an embodiment of the present disclosure proposes an information processing method, including: a network device sends configuration information, wherein the configuration information is used by a terminal or a PDCP entity to determine the PSI level of a second type of data packet; the second type of data packet is not associated with or does not belong to a data packet set.

[0062] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending first information to the terminal, wherein the first information is used to indicate a packet loss strategy; the packet loss strategy is used to indicate that data packets are discarded in the event of congestion.

[0063] In combination with some embodiments of the second aspect, in some embodiments, the packet loss policy is used to indicate one of the following: whether to discard the second type of data packets first; or discard the data packets according to the PSI level of the data packets.

[0064] In combination with some embodiments of the second aspect, in some embodiments, sending the first information includes: sending the first information to the terminal when congestion is detected.

[0065] In a third aspect, an embodiment of the present disclosure proposes a first entity, comprising: a first transceiver module, configured to receive at least one type of data packet, wherein the data packet comprises at least one of the following: a first type of data packet, wherein the first type of data packet is associated with or belongs to a first data packet set; a second type of data packet, wherein the second type of data packet is not associated with or does not belong to a data packet set.

[0066] In a fourth aspect, an embodiment of the present disclosure proposes a network device, comprising: a second transceiver module, configured to send configuration information, wherein the configuration information is used by a terminal or a PDCP entity to determine the PSI level of a second type of data packet; the second type of data packet does not belong to a data packet set, and / or the second type of data packet does not carry a GTP-U packet header.

[0067] In a fifth aspect, an embodiment of the present disclosure proposes a first entity, comprising: one or more processors; wherein the above-mentioned first entity is used to execute an optional implementation method of the first aspect.

[0068] In a sixth aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; wherein the above-mentioned network device is used to execute the optional implementation method of the second aspect.

[0069] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, comprising: a first entity and a network device; wherein the above-mentioned first entity is configured to execute the method described in the optional implementation manner of the first aspect, and the above-mentioned network device is configured to execute the method described in the optional implementation manner of the second aspect.

[0070] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0071] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0072] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the information processing method as described in the first aspect, the second aspect, or the optional implementation of the first and second aspects.

[0073] In an eleventh aspect, an embodiment of the present disclosure proposes a chip or a chip system; the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0074] It is understood that the aforementioned network devices, entities, terminals, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0075] The present disclosure provides an information processing method, entity, network device, communication system, and storage medium. In some embodiments, the terms information processing method and communication method are interchangeable, the terms information processing device and communication device are interchangeable, and the terms information processing system and communication system are interchangeable.

[0076] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0077] In each embodiment of the present disclosure, unless otherwise specified or provided for, the terms and / or descriptions between the embodiments are consistent and can be used interchangeably. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0078] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0079] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0080] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0081] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0082] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0083] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0084] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0085] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0086] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0087] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0088] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0089] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0090] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0091] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0092] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, it can also be called device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, language such as "uplink" and "downlink" can also be replaced by language corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0093] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0094] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0095] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0096] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0097] FIG1 is a schematic diagram showing the structure of an information processing system 100 according to an embodiment of the present disclosure. As shown in FIG1 , the information processing system 100 may include: a terminal 101 and a network device 102 .

[0098] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

[0099] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things (IOT) device or terminal, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0100] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0101] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0102] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0103] In some embodiments, the core network device may be a single device including a first network element, a second network element, etc., or may be a plurality of devices or a group of devices, each including all or part of the first network element and the second network element. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0104] It can be understood that the information processing system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0105] The following embodiments of the present disclosure may be applied to the information processing system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The information processing system may include all or a portion of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities may be arbitrary. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0106] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0107] In some embodiments, in Extended Reality (XR) services, data can be differentiated based on importance. For example, data can be divided into I-frames and P-frames. I-frames are relatively important frames, while P-frames are relatively unimportant frames. Here, the UE can use I-frame decoding, while P-frames require I-frame decoding and cannot be decoded independently.

[0108] In some embodiments, a Protocol Data Unit (PDU) set is introduced; the PDU set may be composed of multiple PDUs. Optionally, all data in a PDU set must reach a higher layer to be correctly decoded; alternatively, all data in a PDU set does not need to reach a higher layer to be correctly decoded.

[0109] In some embodiments, a User Plane Function (UPF) identifies PDU sets and places information about them in a General Packet Radio Service Tunnelling Protocol for the User plane (GTP-U) header for delivery to the RAN. The UPF identifies PDU sets for downlink (DL) PDUs at the GTP-U layer via a GTP-U header extension. The UPF identifies the PDUs that belong to a PDU set and at least one of the following information for each PDU set:

[0110] PDU set sequence number (SN) (Solutions 7, 8, 9, 11, 12, 14, 19, 20, 21, 22, 23, 50, 53, 55, 56);

[0111] The start or end PDU of a PDU set (Solutions 11, 12, 15, 18, 21, 22, 55, 56);

[0112] PDU SN in PDU set (solutions 11, 20, 22, 55, 56);

[0113] Number of PDUs within a PDU set (Solutions 9, 20, 50) and / or PDU set size in bytes.

[0114] In some embodiments, some basic parameters used by the UPF to identify a PDU set may include at least one of the following: a PDU set sequence number (SN), identifiers of the start PDU and the end PDU, a PDU sequence number in the PDU set, the number of PDUs in the PDU set and the size of the PDU set (in bytes), the importance or importance level of the PDU set, and a sequence number of important PDUs in the PDU set. Optionally, the importance or importance level is used to indicate the importance of the data packet.

[0115] In some embodiments, the QoS parameters for a data packet are defined as at least one of the following: When a QoS flow is enabled with PDU set-based QoS processing by the 5GC, the PDU set QoS parameters may be provided by the Session Management Function (SMF) to the gNB as part of the QoS profile for the QoS flow:

[0116] PDU Set Delay Budget (PSDB): The time between receiving the first PDU (UPF in DL, UE in uplink (UL)) and successfully delivering the last arriving PDU of a PDU set (UE in DL, UPF in UL). A QoS flow is associated with only one PSDB for both UL and DL, and it replaces the PDU Delay Budget (PDB) when available.

[0117] PDU Set Error Rate (PSER): An upper bound on the loss rate of non-congestion related PDU sets between the RAN and the UE. For both UL and DL, a QoS flow is associated with only one PSER and, when available, it replaces the PDU Error Rate (PER). Optionally, a PDU set is considered successfully delivered only if all PDUs in the set are successfully delivered.

[0118] PDU Set Integrated Indication (PSIHI): indicates whether the application layer needs all PDUs of a PDU set to use the PDU set.

[0119] In some embodiments, in the uplink (UL) direction, the terminal's identification of information related to a PDU set is based on terminal implementation.

[0120] Alternatively, in the UL direction, the identification of PDU sets, data bursts and / or PSI levels may be left to the UE implementation.

[0121] For example, in the Packet Data Convergence Protocol (PDCP) layer, packet loss mechanisms can be used to discard packets based on their importance. This means that the terminal will discard packets based on network configuration. For a transmitting PDCP entity, if one packet in a packet set is discarded, the entire set is discarded without being sent. This reduces unnecessary air interface transmissions and conserves air interface resources.

[0122] Optionally, the Radio Resource Control (RRC) is configured to configure the UL PDU set discard indication to handle the PDU set-based discard function (ie, whether the UE discards all PDUs in the PDU set when discarding a PDU). This configuration is based on the PDCP entity.

[0123] For example, a single QoS flow may contain two types of packets: those carrying PDU header information and those without. A single QoS flow may include both PDUs marked with the PDU header extension and those without the PDU header. At this point, the terminal has no solution for how to handle packets without the PDU header at the PDCP layer.

[0124] In response to new demands such as XR services, the disclosed embodiments propose a solution for data packet processing at the PDCP layer.

[0125] FIG2 is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to an information processing method for an information processing system 100, and the method includes:

[0126] Step S2101: The first entity obtains at least one type of data packet.

[0127] In some embodiments, the first entity may be a PDCP entity. For example, the first entity may be a PDCP entity of a terminal or a PDCP entity of an access network device. Optionally, the access network device is a base station.

[0128] Optionally, the PDCP entity of the terminal may receive at least one type of data packet from a higher layer (eg, an RRC layer); or, the PDCP entity of the access network device may receive at least one type of data packet from a higher layer.

[0129] In an optional embodiment, the terminal or access network device receives at least one type of data packet. For example, the terminal or access network device receives at least one type of data packet sent by another terminal; the terminal may be a first terminal, and the other terminal may be a second terminal.

[0130] In some embodiments, the data packet includes a first data packet and / or a second type of data packet.

[0131] Optionally, the first-category data packets are associated with or belong to a first data packet set, and / or the first-category data packets carry a GTP-U header or the first-category data packets correspond to a PSI level. Optionally, the second-category data packets are not associated with or do not belong to a data packet set, and / or the second-category data packets do not carry a GTP-U header.

[0132] Optionally, the data packet may be a PDU; the data packet set may be a PDU set. For example, the first type of data packet may be a first type of PDU; the first type of data packet set may be a first type of PDU set; the second type of data packet may be a second type of PDU; and the second type of data packet set may be a second type of PDU set.

[0133] Optionally, the GTP-U header carries at least one of the following: a PDU set sequence number (SN), a start PDU identifier, an end PDU identifier, a PDU sequence number in the PDU set, the number of PDUs in the PDU set, the PDU set size (in bytes), an importance level (PSI level) of the PDU set, and an important PDU sequence number in the PDU set. The importance level of the PDU set may be the importance of the PDU set.

[0134] Optionally, the first-category data packet carrying the GTP-U header may be: the first-category data packet carries information in the GTP-U header; and the second-category data packet carrying the GTP-U header may be: the second-category data packet does not carry information in the GTP-U header. Here, the information in the GTP-U header may be information such as the importance level of the PDU set, the PDU set sequence number, the start PDU identifier, and / or the end PDU identifier in the above-mentioned embodiment.

[0135] Optionally, different first-category data packets belong to different importance levels.

[0136] In some embodiments, the name of the first type of data packet is not limited, and it can be, for example, a data packet carrying a GTU-U header, a type 1 data packet, etc.

[0137] In some embodiments, the name of the second type of data packet is not limited, and it can be, for example, a data packet that does not carry a GTU-header, a type 2 data packet, etc.

[0138] Step S2102: The first entity determines that a second type of data packet is associated with a second data packet set.

[0139] In some embodiments, the PDCP entity determines that a second type of data packet is associated with a second data packet set. For example, the PDCP entity determines that a second type of data packet is associated with the second data packet set.

[0140] In some optional embodiments, the terminal or the access network device determines that a second type of data packet is associated with a second data packet set.

[0141] Optionally, determining that a second-category data packet is associated with the second data packet set may include mapping a second-category data packet to a second data packet set.

[0142] Optionally, the first entity determines that a second-category data packet is included in a second data packet set. For example, a second-category data packet constitutes a second data packet set, that is, the second data packet set only includes one second-category data packet.

[0143] Exemplarily, the first entity modifies the data format of the second-category data packet to form a second data packet set. For example, the first entity sets a GTP-U header for a second-category data packet to generate a second data packet set including the content of the second-category data packet and the GTP-U header.

[0144] Exemplarily, the first entity generates a second data packet set; the first entity includes the second type of data packets in the second data packet set.

[0145] Exemplarily, the first entity determines a data packet set obtained by the first entity as a second data packet set, and includes the second type of data packets in the second data packet set.

[0146] Optionally, the first entity determines the QoS of the second type of data packets based on the QoS parameters of the second data packet set. Here, the QoS processing of the second type of data packets is performed according to the QoS parameters in the second data packet set. Here, the second data packet set has been configured with the corresponding QoS.

[0147] Exemplarily, the first entity determines the PER of the second type of data packets based on the PSER in the QoS parameters of the second data packet set. For example, if the PSER in the QoS parameters of the second data packet set is a first value, then the bit error rate or PER required by the QoS of the second type of data packets is the first value.

[0148] Exemplarily, the first entity determines the PSB of the second type of data packets based on the PDSB in the QoS parameters of the second data packet set. For example, if the PSDB in the QoS parameters of the second data packet set is a second value, then the QoS required delay or PSB of the second type of data packets is the second value.

[0149] Exemplarily, the second category data packets are associated with the first data packet set, and the second category data packets determine their own QoS according to the QoS parameters of the second category data packets.

[0150] Optionally, the first entity determines the QoS of the second type of data packets based on QoS parameters of other data packet sets; the other data packet sets are data packet sets received by the first entity or data packet sets other than the second data set.

[0151] Optionally, the first entity determines the QoS of the second category of data packets based on QoS parameters in the QoS flow.

[0152] Step S2103: The network device sends configuration information to the first entity.

[0153] In some embodiments, the terminal or the PDCP entity of the terminal receives configuration information sent by the network device.

[0154] In some embodiments, the configuration information is used to indicate a PSI level corresponding to at least one second-category data packet. For example, the configuration information indicates at least one of the following: the PSI level corresponding to the first second-category data packet is a first PSI level, the PSI level corresponding to the second second-category data packet is a second PSI level, and the PSI level corresponding to the third second-category data packet is a third PSI level; wherein the first PSI level is more important than the second PSI level, and the second PSI level is more important than the third PSI level.

[0155] In some embodiments, the configuration information is used by the terminal or the PDCP entity to determine the PSI level of the second category data packets.

[0156] In some embodiments, the configuration information includes: at least one second-category data packet and a PSI level corresponding to the second-category data packet.

[0157] In some embodiments, the name of the configuration information is not limited, and it can be, for example, PSI level indication information.

[0158] Step S2104: The first entity determines the PSI level of the second type of data packets.

[0159] In some embodiments, the PDCP entity determines the PSI level for the second category packets.

[0160] In some optional embodiments, the terminal or the access network device determines the PSI level of the second type of data packets.

[0161] In some embodiments, the first entity determines the PSI level for the second-category data packets based on a protocol agreement. Optionally, the protocol may be a wireless communication protocol. For example, the protocol may be a wireless communication standard protocol. Alternatively, the protocol may be a protocol negotiated between the terminal and the base station. Optionally, the protocol may specify a PSI level corresponding to at least one second-category data packet.

[0162] In some embodiments, the first entity determines the PSI level of the second category data packets according to a predefined method. Optionally, the predefined method may include: before determining the PSI level of the second category data packets, the first entity predefines at least one PSI level corresponding to the second category data packets.

[0163] In some embodiments, the first entity determines the PSI level of the second type of data packets based on configuration information.

[0164] Optionally, the first entity receives configuration information sent by the network device, where the configuration information includes a PSI level corresponding to at least one second-category data packet; the first entity may determine the PSI level of the second-category data packet based on the configuration information.

[0165] Optionally, the first entity may determine the PSI level of the second-category data packet by using a specific value agreed upon in a protocol, predefined, or in configuration information sent by the network device. For example, if the specific value is a first value, such as "1," the PSI level of the second-category data packet may be determined to be the first PSI level.

[0166] Optionally, the PSI level may include at least one level. For example, the PSI level may include a first PSI level, a second PSI level, and / or a third PSI level; wherein the first PSI level is more important than the second PSI level, and the second PSI level is more important than the third PSI level. For another example, the PSI level may include a PSI level of highest importance, a PSI level of second highest importance, and / or a PSI level of lowest importance, etc.

[0167] In some embodiments, the PSI level of the second type of data packets is for at least one of the following: each PDCP entity, each terminal, and each data packet. Here, for each PDCP entity can be for each DRB.

[0168] Optionally, different PSI levels may be set for different PDCP entities or DRBs. Here, different PDCP entities or DRBs may transmit data packets of different types or different importance, so different PSI levels are set for different PDCP entities or DRBs.

[0169] Optionally, the PDCP entity of the access network device determines the PSI level of the second category data packets for each PDCP entity, each terminal, or each data packet.

[0170] Optionally, the PDCP entity of the terminal determines the PSI level of the second-category data packets of its own PDCP, or determines the PSI level of the second-category data packets received by the terminal, or determines the PSI level of each second-category data packet. For example, the terminal determines the PSI level of the second-category data packets received by the terminal based on the terminal identifier.

[0171] Step S2105: The first entity determines a timer duration corresponding to the PSI level of the second-category data packet. Optionally, the first entity determines different timer durations for different PSI levels of the second-category data packets.

[0172] In some embodiments, the PDCP entity determines a timer duration for the PSI level of the second category packets.

[0173] In some optional embodiments, the terminal or the access network device determines the timer duration of the PSI level of the second type of data packets.

[0174] Optionally, the timer duration is the duration for discarding the second type of data packets. For example, the timer duration may be the first duration.

[0175] In some embodiments, the first entity determines the timer duration of the PSI level of the second type of data packets based on the timer duration corresponding to the different PSI levels of the first data packets.

[0176] In some embodiments, the first entity determines whether to perform packet loss processing on a data packet according to a timer duration of a corresponding PSI level.

[0177] Optionally, if the first entity determines to configure a packet loss policy or a packet loss mechanism for the data packet, it determines to perform packet loss processing on the data packet according to the timer duration of the corresponding PSI level.

[0178] Optionally, determining whether to perform packet loss processing on a data packet according to the timer duration of the corresponding PSI level includes: when the timer duration of the PSI level corresponding to the data packet is reached, determining to discard the data packet and / or discarding other data packets in the unified data packet set associated with the data packet.

[0179] Optionally, determining whether to perform packet loss processing on a data packet according to a timer duration corresponding to a PSI level includes: determining whether to perform packet loss processing on a first-category data packet according to a timer duration corresponding to a PSI level, and / or determining whether to perform packet loss processing on a second-category data packet according to a timer duration corresponding to a PSI level. Exemplarily, if the timer duration corresponding to a data packet at a PSI level expires, the data packet and other data packets in the same data packet set as the data packet are discarded; the data packet may include a first-category data packet and / or a second-category data packet.

[0180] Optionally, determining to perform packet loss processing on the second category data according to the timer duration of the corresponding PSI level includes: determining to drop the second category data packet when the timer duration of the PSI level is reached.

[0181] Optionally, the first entity discards the second category data packet when the timer corresponding to the PSI level of the second category data packet times out.

[0182] Optionally, determining that second-category data should be discarded according to a timer duration corresponding to the PSI level includes: determining that data packets in the same second data packet set as the second-category data packets are discarded when the timer duration expires. For example, a second data packet set includes: second-category data packet A, second-category data packet B, and second-category data packet C; when the terminal determines that second-category data packet A needs to be discarded, second-category data packets B and second-category data packets C in the second data packet set are also discarded.

[0183] Optionally, when the timer duration corresponding to the PSI level of the second category data packet times out, the first entity discards the data packets in the same data packet set as the second category data packet.

[0184] Step S2106: The network device sends first information to the first entity.

[0185] In some embodiments, the network device sends first information to the terminal when congestion is detected.

[0186] In some embodiments, the terminal or the PDCP entity of the terminal receives first information sent by the network device. Optionally, the first information is sent by the network device when congestion is detected.

[0187] In some embodiments, the first information is used to indicate a packet loss policy and / or to indicate discarding of a data packet.

[0188] Optionally, the packet loss policy is a packet loss policy for when congestion occurs, or the packet loss policy is used to instruct to drop data packets when congestion occurs.

[0189] Optionally, the packet loss policy is used to indicate whether to give priority to discarding the second type of data packets. Exemplarily, if the packet loss policy carries first indication information, it is used to indicate that the second type of data packets should be discarded first; or if the packet loss policy carries second indication information, it is used to indicate that the second type of data packets should not be discarded first.

[0190] Optionally, the packet loss policy is used to instruct to drop a data packet according to a PSI level of the data packet. The data packet may include a first-category data packet and / or a second-category data packet.

[0191] In some embodiments, the name of the first information is not limited, and it can be, for example, packet loss policy information, packet loss indication information, etc.

[0192] Step S2107: The first entity determines a packet loss strategy.

[0193] In some embodiments, the terminal or a PDCP entity of the terminal determines the packet loss policy.

[0194] In some embodiments, the first entity determines a packet loss policy according to a protocol agreement.

[0195] Optionally, the protocol may be a wireless communication protocol, for example, a wireless communication standard protocol.

[0196] Optionally, the protocol may be a protocol negotiated between the terminal and the base station.

[0197] Optionally, the protocol stipulates whether to preferentially discard the second type of data packets.

[0198] Optionally, the protocol stipulates that packets are discarded based on their PSI levels. For example, the packets include first-category packets and second-category packets; the first-category packets correspond to a first PSI level, and the second-category packets correspond to a second PSI level; the first PSI level is more important than the second PSI level; and the terminal or the PDCP entity of the terminal determines to discard the second-category packets.

[0199] In some embodiments, the first entity determines a packet loss policy according to a predefined policy.

[0200] Optionally, it is predefined whether to preferentially discard the second type of data packets.

[0201] Optionally, it is predefined to discard data packets according to the PSI level of the data packets.

[0202] In some embodiments, the first entity determines a packet loss strategy based on the first information.

[0203] Optionally, the first entity determines to discard the data packets first according to the priority discarding of the second category of data packets indicated by the first information.

[0204] Optionally, the first entity discards the data packet according to the PSI level of the data packet indicated by the first information, and determines to discard the data packet according to the PSI level of the data packet.

[0205] In some embodiments, the name of the first information is not limited, and it can be, for example, packet loss policy information, packet loss indication information, etc.

[0206] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0207] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0208] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0209] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0210] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0211] The information processing method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2101 can be implemented as an independent embodiment; step S2102 can be implemented as an independent embodiment; step S2103 can be implemented as an independent embodiment; step S2103 can be implemented as an independent embodiment; step S2105 can be implemented as an independent embodiment; step S2106 can be implemented as an independent embodiment; step S2107 can be implemented as an independent embodiment; step S2101 and step S2102 can be implemented as independent embodiments; the combination of step S2101, step S2102 and step S2103 can be implemented as an independent embodiment. The steps of step S2101 to step S2104 can be implemented as an independent embodiment; the combination of step S2101 to step S2105 can be implemented as an independent embodiment; the combination of step S2106 and step S2107 can be implemented as an independent embodiment; the combination of step S2101 to step S2105 and step S2106 can be implemented as an independent embodiment; the combination of step S2101 to step S2107 can be implemented as an independent embodiment.

[0212] In some embodiments, step S2101 and step S2103 may be exchanged in order or executed simultaneously, step S2103 and step S2105 may be exchanged in order or executed simultaneously, and step S2105 and step S2106 may be exchanged in order or executed simultaneously.

[0213] In some embodiments, steps S2102 to S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0214] In some embodiments, step S2101 and step S2103 to step S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0215] In some embodiments, steps S2101 to S2102 and steps S2104 to S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0216] In some embodiments, steps S2101 to S2103 and steps S2105 to S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0217] In some embodiments, steps S2101 to S2104 and steps S2106 to S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0218] In some embodiments, steps S2101 to S2106 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0219] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information processing method, which is executed by a first entity and includes:

[0220] Optionally, the first entity may be a terminal, a PDCP entity of a terminal, an access network device, or a PDCP entity of an access network device.

[0221] Step S3101: Acquire at least one type of data packet.

[0222] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0223] In some embodiments, the first entity obtains at least one type of data packet sent by the terminal, but is not limited thereto, and may also receive at least one type of data packet sent by other entities.

[0224] In some embodiments, the first entity obtains at least one type of data packet specified by the protocol.

[0225] In some embodiments, the first entity obtains at least one type of data packet from an upper layer(s). For example, the first entity obtains at least one type of data packet from an RRC layer.

[0226] In some embodiments, the first entity performs processing to obtain at least one type of data packet.

[0227] In some embodiments, step S3101 is omitted, and the terminal autonomously implements the functions indicated by at least one type of data packet, or the above functions are default or acquiescent.

[0228] Step S3102: Determine whether a second type of data packet is associated with a second data packet set.

[0229] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0230] Step S3103, obtain configuration information.

[0231] The optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0232] In some embodiments, the first entity obtains configuration information sent by the network device, but is not limited thereto and may also receive configuration information sent by other entities.

[0233] In some embodiments, the first entity obtains configuration information specified by the protocol.

[0234] In some embodiments, the first entity obtains configuration information from upper layer(s).

[0235] In some embodiments, the first entity performs processing to obtain the configuration information.

[0236] In some embodiments, step S3103 is omitted, and the terminal autonomously implements the functions indicated by the configuration information, or the above functions are default or acquiescent.

[0237] Step S3104: Determine the PSI level of the second type of data packets.

[0238] The optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0239] Step S3105: Determine the timer duration of the PSI level of the second type of data packets.

[0240] The optional implementation of step S3105 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0241] Step S3106, obtaining first information.

[0242] The optional implementation of step S3106 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0243] In some embodiments, the first entity obtains the first information sent by the network device, but is not limited thereto and may also receive the first information sent by other entities.

[0244] In some embodiments, the first entity obtains first information specified by the protocol.

[0245] In some embodiments, the first entity obtains the first information from an upper layer(s).

[0246] In some embodiments, the first entity performs processing to obtain the first information.

[0247] In some embodiments, step S3106 is omitted, and the terminal autonomously implements the function indicated by the first information, or the above function is default or by default.

[0248] Step S3107: Determine the packet loss strategy.

[0249] The optional implementation of step S3107 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0250] The information processing method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3107. For example, step S3101 can be implemented as an independent embodiment; step S3102 can be implemented as an independent embodiment; step S3103 can be implemented as an independent embodiment; step S3103 can be implemented as an independent embodiment; step S3105 can be implemented as an independent embodiment; step S3106 can be implemented as an independent embodiment; step S3107 can be implemented as an independent embodiment; step S3101 and step S3102 can be implemented as independent embodiments; the combination of step S3101, step S3102 and step S3103 can be implemented as an independent embodiment. The steps of step S3101 to step S3104 can be implemented as an independent embodiment; the combination of step S3101 to step S3105 can be implemented as an independent embodiment; the combination of step S3106 and step S3107 can be implemented as an independent embodiment; the combination of step S3101 to step S3105 and step S3106 can be implemented as an independent embodiment; the combination of step S3101 to step S3107 can be implemented as an independent embodiment.

[0251] In some embodiments, step S3101 and step S3103 may be exchanged in order or executed simultaneously, step S3103 and step S3105 may be exchanged in order or executed simultaneously, and step S3105 and step S3106 may be exchanged in order or executed simultaneously.

[0252] In some embodiments, steps S3102 to S3107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0253] In some embodiments, step S3101 and step S3103 to step S3107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0254] In some embodiments, steps S3101 to S3102 and steps S3104 to S3107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0255] In some embodiments, steps S3101 to S3103 and steps S3105 to S3107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0256] In some embodiments, steps S3101 to S3104 and steps S3106 to S3107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0257] In some embodiments, steps S3101 to S3106 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0258] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to an information processing method, which is executed by a first entity and includes:

[0259] Step S3201: Acquire at least one type of data packet.

[0260] The optional implementation of step S3201 can be found in step S2101 in FIG. 2 , or the optional implementation of step S3101 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0261] In some embodiments, the data packet includes at least one of the following:

[0262] A first category data packet, wherein the first category data packet is associated with or belongs to a first data packet set, and / or the first category data packet carries a GTP-U header or the first category data packet corresponds to a PSI level;

[0263] The second type of data packet is not associated with or does not belong to a data packet set, and / or the second type of data packet does not carry a GTP-U header.

[0264] In some embodiments, the method further comprises: determining that a second type of data packet is associated with a second data packet set.

[0265] In some embodiments, determining that a second-class data packet is associated with a second data packet set includes at least one of the following: determining that a second-class data packet is included in a second data packet set; and determining the QoS of the second-class data packet based on the QoS parameters of the second data packet set.

[0266] In some embodiments, the QoS of the second type of data packets is determined based on the QoS parameters of the second data packet set, including at least one of the following: determining the PER of the second type of data packets based on the PSER in the QoS parameters of the second data packet set; determining the PSB of the second type of data packets based on the PDSB in the QoS parameters of the second data packet set.

[0267] In some embodiments, the method further comprises determining a PSI level for the second type of data packets.

[0268] In some embodiments, determining the PSI level of the second category data packet includes at least one of the following: determining the PSI level of the second category data packet according to a protocol agreement; determining the PSI level of the second category data packet according to a pre-defined definition; determining the PSI level of the second category data packet according to configuration information sent by a network device; wherein the configuration information is used to indicate the PSI level corresponding to at least one second category data packet.

[0269] In some embodiments, the PSI level for the second category packets is for one of: per PDCP entity, per terminal, and per packet.

[0270] In some embodiments, the method further includes: determining a timer duration corresponding to the PSI level of the second category data packets, wherein the timer duration is a duration for discarding the second category data packets.

[0271] In some embodiments, the second-category data packet is determined to be dropped according to a timer duration corresponding to the PSI level. Optionally, the first entity configures a packet drop policy or packet drop mechanism for the data packet, determining that the data packet and other data packets in the same data packet set as the data packet are dropped when the timer duration corresponding to the PSI level of the data packet expires.

[0272] In some embodiments, the method also includes at least one of the following: discarding the second type of data packet when the timer corresponding to the PSI level of the second type of data packet expires; discarding the data packet in the same second data packet set as the second type of data packet when the timer corresponding to the PSI level of the second type of data packet expires.

[0273] In some embodiments, the method includes determining a packet loss policy, wherein the packet loss policy is configured to drop data packets when congestion is indicated.

[0274] In some embodiments, determining the discarding strategy includes one of the following: determining the packet loss strategy according to a protocol agreement; determining the packet loss strategy according to a pre-defined definition; determining the packet loss strategy according to first information sent by a network device; wherein the first information is used to indicate the packet loss strategy.

[0275] In some embodiments, the packet drop policy is used to indicate one of the following: whether to preferentially drop the second category of data packets; or to drop data packets according to the PSI level of the data packets.

[0276] In some embodiments, the first information is sent by the network device when congestion is detected.

[0277] In some embodiments, the first entity includes one of the following: a PDCP entity of a terminal, or a PDCP entity of an access network device.

[0278] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0279] FIG3C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to an information processing method, which is executed by a first entity and includes:

[0280] Step S3301: Determine whether a second-category data packet is associated with a data packet set.

[0281] The optional implementation of step S3301 can be found in step S2102 in FIG. 2 , or the optional implementation of step S3102 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0282] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0283] FIG3D is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3D , the present disclosure embodiment relates to an information processing method, which is executed by a first entity and includes:

[0284] Step S3401: Determine the PSI level of the second type of data packets.

[0285] The optional implementation of step S3401 can be found in step S2104 in FIG. 2 , or the optional implementation of step S3104 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0286] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0287] FIG3E is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3E , the present disclosure embodiment relates to an information processing method, which is executed by a first entity and includes:

[0288] Step S3501: Determine the timer duration of the PSI level of the second type of data packets.

[0289] The optional implementation of step S3501 can be found in step S2105 in FIG. 2 , or the optional implementation of step S3105 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0290] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0291] FIG3F is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3F , the present disclosure embodiment relates to an information processing method, which is executed by a first entity and includes:

[0292] Step S3601: Determine the packet loss strategy.

[0293] The optional implementation of step S3601 can be found in step S2107 in FIG. 2 , or the optional implementation of step S3107 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0294] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0295] FIG4A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to an information processing method, which is executed by a network device. The method includes:

[0296] Step S4101, sending configuration information.

[0297] The optional implementation of step S4101 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0298] In some embodiments, the network device sends configuration information to the terminal, but is not limited thereto and may also send configuration information to other entities.

[0299] Optionally, the network device sends configuration information to the terminal or the PDCP entity of the terminal.

[0300] Step S4102, sending the first information.

[0301] The optional implementation of step S4102 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0302] In some embodiments, the network device sends the first information to the terminal, but is not limited thereto, and the first information may also be sent to other entities.

[0303] Optionally, the network device sends the first information to the terminal or the PDCP entity of the terminal.

[0304] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment; step S4102 may be implemented as an independent embodiment; or a combination of step S4101 and step S4102 may be implemented as an independent embodiment.

[0305] In some embodiments, step S4101 and step S4102 may be executed in an interchangeable order or simultaneously.

[0306] In some embodiments, step S4101 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0307] In some embodiments, step S4102 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0308] FIG4B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to an information processing method, which is executed by a network device and includes:

[0309] Step S4201, sending configuration information.

[0310] The optional implementation of step S4201 can be found in step S2103 in FIG. 2 , or the optional implementation of step S4101 in FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0311] In some embodiments, the configuration information is used by a terminal or a Packet Data Convergence Protocol (PDCP) entity to determine a protocol data unit set importance (PSI) level of a second type of data packet; the second type of data packet is not associated with or does not belong to a data packet set.

[0312] Optionally, the second type of data packet does not carry a GTP-U header.

[0313] In some embodiments, the method further includes: sending first information to the terminal, wherein the first information is used to indicate a packet loss policy; the packet loss policy is used to indicate discarding data packets. Optionally, the packet loss policy is used to indicate discarding data packets in the event of congestion.

[0314] In some embodiments, the packet drop policy is used to indicate one of the following: whether to preferentially drop the second category of data packets; or to drop data packets according to the PSI level of the data packets.

[0315] In some embodiments, sending the first information includes: sending the first information to the terminal when congestion is detected.

[0316] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0317] FIG4C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to an information processing method, which is executed by a network device. The method includes:

[0318] Step S4301, sending the first information.

[0319] The optional implementation of step S4301 can be found in step S2106 in FIG. 2 , or the optional implementation of step S4102 in FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0320] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0321] The present disclosure relates to an information processing method, which includes:

[0322] In some embodiments, a data processing mechanism of a PDCP entity is protected. Optionally, the data processing mechanism may be a mechanism for processing data packets.

[0323] Optionally, a PDCP entity will receive at least two different types of data packets from a higher layer; namely, type 1 data packets and type 2 data packets.

[0324] Optionally, a type 1 data packet is associated with or belongs to a PDU set (e.g., a first PDU set), or the terminal can identify that the type 1 data packet belongs to a PDU set; and / or, the type 1 data packet carries an extension header, such as GTP-U header information (header extensions), or the type 1 datagram belongs to a different PSI level.

[0325] Optionally, the terminal may identify that the data packet of type 2 does not belong to or is not associated with a PDU set (eg, the second PDU set); and / or, the data packet of type 2 does not carry an extension header, such as GTP-U header information.

[0326] Optionally, the Type 1 data packet may be the first type of data packet in the previous embodiment; the Type 2 data packet may be the second type of data packet in the previous embodiment; and the GTP-U header information may be the information in the GTP-U header or the GTP U header in the previous embodiment. Optionally, the PDCP entity may be a PDCP entity of a terminal or a DPCP entity of an access network device.

[0327] In some embodiments, the PDCP entity considers that a Type 2 data packet is associated with a data packet set (eg, a second PDU set).

[0328] Optionally, data packets of type 2 constitute a data packet set (eg, a second PDU set), but the data packet set only includes one data packet.

[0329] Alternatively, if the network device configures a packet set-based discard mechanism for the PDCP entity, when the discard timer expires, the packet or other packets in the same packet set associated with the packet are discarded. However, since there is only one packet in the data set, discarding the packet is sufficient.

[0330] Optionally, QoS processing for Type 2 packets will be performed according to the QoS parameters set for packets in the QoS flow. Specifically, for Type 2 packets, their QoS required bit errors will be processed according to the PSER of the QoS flow, and / or their delays will be processed according to the PSDB of the QoS flow. Here, Type 1 and Type 2 packets belong to the same QoS flow. Currently, the parameters for the same QoS flow are set as a single set, meaning that QoS parameters are set for each QoS flow. Thus, Type 1 and Type 2 packets are processed according to the QoS parameters of the same QoS flow.

[0331] Optionally, if QoS parameters for PDU sets are subsequently introduced, the QoS processing for Type 2 packets will be processed according to the QoS parameters of the second packet set; that is, for the Type 2 packets, the bit errors required by their QoS requirements will be processed according to the PSER of the second PDU set, and / or the delays will be processed according to the PSDB of the second PDU set. In this way, Type 1 and Type 2 packets are processed according to different QoS parameters.

[0332] In some embodiments, the PDCP entity sets the PSI level for type 2 data packets or their associated second PDU sets in accordance with one of the following principles: the PSI level for type 2 data packets or their associated second PDU sets is set in accordance with the protocol agreed value, or in accordance with a predefined value or a network configuration value.

[0333] Optionally, the agreed value may be the highest PSI level, i.e., the highest level of importance; or the agreed value may be the lowest PSI level, i.e., the lowest level of importance;

[0334] In some embodiments, the network device may pre-notify the PDCP entity of the terminal of the PSI level setting for a Type 2 packet or its associated second PDU set. In this way, the PSI level setting for the Type 2 packet or its associated second PDU set may be configured by the network device.

[0335] Optionally, the network device configuration PSI level value is 1.

[0336] Optionally, the granularity of the network device configuration may be per (Per) PDCP entity (ie, per Data Radio Bearer (DRB) configuration) or per UE configuration; ie, all DRBs are configured according to the same network device configuration. The UE may be a terminal.

[0337] In some embodiments, after the PDCP entity sets the PSI level for type 2 data packets according to the above principles, packet loss processing is performed on type 2 data packets or their associated second PDU sets according to the corresponding PSI level drop timer.

[0338] Optionally, a PDCP data packet may be a service data unit (SDU) or a PDU; depending on the importance level of its data packet set, if a packet loss timer (e.g., discardTimer) associated with the importance level of its data packet times out, the data packet is discarded or other data packets in the same data packet set associated with the data packet are discarded.

[0339] In some embodiments, the network device may inform the PDCP entity of the terminal of a policy to discard type 2 packets in case of congestion.

[0340] Optionally, the network device may notify the PDCP entity of the terminal of a policy of preferentially discarding type 2 data packets in the event of congestion.

[0341] Optionally, the network device may notify the PDCP entity of the terminal of the PSI level of the Type 2 packet when it is necessary to discard the packet during congestion; for example, treat the Type 2 packet as having the lowest importance level, i.e., discard it first; or treat the Type 2 packet as having the highest importance level, i.e., not discard it first.

[0342] Optionally, the network device may notify the terminal to discard data packets when congestion is detected; and at the same time inform the PDCP entity of the terminal of the policy of discarding type 2 data packets when congestion occurs.

[0343] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, and may also be arbitrarily combined with the optional implementations of other embodiments.

[0344] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0345] It should be understood that the division of the various units in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, the memory stores computer instructions, and the processor calls the computer instructions stored in the memory to implement any of the above methods or implement the functions of the various units of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors. For example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units are realized by designing the logical relationship of the components in the circuit. For another example, in another implementation, the above-mentioned hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0346] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0347] Figure 5A is a schematic structural diagram of the first entity provided in an embodiment of the present disclosure. As shown in Figure 5A, the first entity 5100 includes: a first transceiver module 5101. In some embodiments, the first transceiver module 5101 is configured to receive at least one type of data packet. Optionally, the above-mentioned first transceiver module 5101 is used to perform at least one of the steps of receiving and / or sending (such as step S2101, step S2103 and / or step S2106, but not limited to these) performed by the first entity in any of the above methods, which will not be repeated here. Optionally, the first entity 5100 also includes a first processing module; the first processing module is used to perform at least one of the steps of processing (such as step S2102, step S2104, step S2105 and / or step S2107, etc.) performed by the first entity in any of the above methods, which will not be repeated here.

[0348] Figure 5B is a schematic diagram of the structure of a network device provided in an embodiment of the present disclosure. As shown in Figure 5B, network device 5200 includes a second transceiver module 5201. In some embodiments, the second transceiver module 5201 is configured to send configuration information. Optionally, the second transceiver module 5201 is configured to perform at least one of the receiving and / or sending steps (such as, but not limited to, steps S2103 and / or S2106) performed by the network device in any of the above methods, which will not be further described here.

[0349] Figure 6A is a schematic diagram of the structure of a communication device 6100 provided in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., an access network device, a core network device), a first entity (e.g., a terminal, an access network device, or a PDCP entity), etc., or a chip, chip system, or processor that supports a network device in implementing any of the above methods, or a chip, chip system, or processor that supports a terminal in implementing any of the above methods. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0350] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 6101 is used to call instructions to enable the communication device 6100 to perform any of the above methods.

[0351] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing instructions. Optionally, all or part of the memories 6102 may be located outside the communication device 6100.

[0352] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceiver 6103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 6101 performs at least one of the other steps.

[0353] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0354] Optionally, the communication device 6100 further includes one or more interface circuits 6104, which are connected to the memory 6102. The interface circuits 6104 can be used to receive signals from the memory 6102 or other devices, and can be used to send signals to the memory 6102 or other devices. For example, the interface circuits 6104 can read instructions stored in the memory 6102 and send the instructions to the processor 6101.

[0355] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data, computer programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0356] 6B is a schematic diagram of the structure of a chip 6200 provided in an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.

[0357] The chip 6200 includes one or more processors 6201 , and the chip 6200 is configured to execute any of the above methods.

[0358] In some embodiments, the chip 6200 further includes one or more interface circuits 6202, which are connected to the memory 6203. The interface circuits 6202 can be used to receive signals from the memory 6203 or other devices, and can be used to send signals to the memory 6203 or other devices. For example, the interface circuits 6202 can read instructions stored in the memory 6203 and send the instructions to the processor 6201.

[0359] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 6201 performs at least one of the other steps.

[0360] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0361] In some embodiments, the chip 6200 further includes one or more memories 6203 for storing instructions. Alternatively, all or part of the memories 6203 may be located outside the chip 6200.

[0362] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0363] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0364] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. An information processing method, characterized in that: The method comprises: The first entity receives at least one type of data packet, wherein the data packet includes at least one of the following: a first type of data packet, wherein the first type of data packet is associated with or belongs to a first data packet set, The second type of data packets, wherein the second type of data packets are not associated with or do not belong to a data packet set.

2. The method according to claim 1, characterized in that The method further includes: determining that a second-category data packet is associated with a second data packet set.

3. The method according to claim 2, characterized in that The determining that a second-category data packet is associated with a second data packet set comprises at least one of the following: determining that a data packet of the second category is included in a set of the second data packets; Based on the quality of service (QoS) parameter of the second data packet set, the QoS of the second category of data packets is determined.

4. The method according to claim 3, characterized in that The determining the QoS of the second type of data packets based on the quality of service QoS parameter of the second data packet set includes at least one of the following: Determine a PDU error rate PER of the second type of data packets based on a PDU set error rate PSER in the QoS parameters of the second data packet set; Based on the PDU set delay budget PDSB in the QoS parameters of the second data packet set, the PDU delay budget PSB of the second type of data packets is determined.

5. The method according to any one of claims 1 to 4, characterized in that: The method further includes determining a protocol data unit set importance (PSI) level of the second type of data packets.

6. The method according to claim 5, characterized in that The determining of the PSI level of the protocol data unit set of the second type of data packet comprises: The PSI level of the second-category data packet is determined according to configuration information sent by the network device; wherein the configuration information is used to indicate the PSI level corresponding to at least one second-category data packet.

7. The method according to claim 5 or 6, characterized in that: The PSI level of the second category of packets is for one of: Each PDCP entity; Each terminal; Each packet.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Determine a timer duration corresponding to the PSI level of the second type of data packets, wherein the timer duration is a duration for discarding the second type of data packets.

9. The method according to claim 8, characterized in that: The method further comprises at least one of: When the timer duration corresponding to the PSI level of the second-category data packet times out, discarding the second-category data packet; When the timer duration corresponding to the PSI level of the second category data packet expires, the data packets in the same second data packet set as the second category data packets are discarded.

10. The method according to any one of claims 1 to 9, characterized in that: The method comprises: A packet loss strategy is determined, wherein the packet loss strategy is used to indicate that the data packet is dropped when congestion occurs.

11. The method according to claim 10, characterized in that The packet loss policy is used to indicate one of the following: Whether to discard the second type of data packets preferentially; The data packets are discarded according to the PSI level of the data packets.

12. The method according to any one of claims 1 to 11, characterized in that: The first entity is: a Packet Data Convergence Protocol PDCP entity of the terminal.

13. The method according to claim 1 or 2, characterized in that: The first entity is a PDCP entity of an access network device.

14. An information processing method, characterized in that: The method comprises: The network device sends configuration information, wherein the configuration information is used by a terminal or a packet data convergence protocol PDCP entity to determine a protocol data unit set importance (PSI) level of a second type of data packet; the second type of data packet is not associated with or does not belong to a data packet set.

15. The method according to claim 14, characterized in that The method further comprises: Sending first information to the terminal, wherein the first information is used to indicate a packet loss strategy, and the packet loss strategy is used to indicate that a data packet is dropped when congested.

16. The method according to claim 15, characterized in that The packet loss policy is used to indicate one of the following: Whether to discard the second type of data packets preferentially; The data packets are discarded according to the PSI level of the data packets.

17. The method according to claim 14 or 15, characterized in that The sending of the first information includes: When congestion is detected, the first information is sent to the terminal.

18. A first entity, characterized in that: include: The first transceiver module is configured to receive at least one type of data packet, wherein the data packet includes at least one of the following: A first type of data packet, wherein the first type of data packet is associated with or belongs to a first data packet set; The second type of data packets, wherein the second type of data packets are not associated with or do not belong to a data packet set.

19. A network device, characterized in that: include: The second transceiver module is configured to send configuration information, wherein the configuration information is used by a terminal or a packet data convergence protocol PDCP entity to determine a protocol data unit set importance (PSI) level of a second type of data packet; the second type of data packet is not associated with or does not belong to a data packet set.

20. A first entity, characterized in that: include: one or more processors; The first entity is used to execute the information processing method according to any one of claims 1 to 13.

21. A network device, characterized in that: include: one or more processors; Wherein, the network device is used to execute the information processing method described in any one of claims 14 to 17.

22. A communication system, characterized in that: include: A first entity and a network device; wherein the first entity is configured to implement the information processing method according to any one of claims 1 to 13, and the network device is configured to implement the information processing method according to any one of claims 14 to 17.

23. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device is caused to execute the information processing method according to any one of claims 1 to 13 or claims 14 to 17.

Images