Information transmitting apparatus and information receiving apparatus

Abstract

Embodiments of the present application provide an information transmitting apparatus and an information receiving apparatus. The information transmitting apparatus is applied to a transmission end packet data convergence protocol (PDCP) entity. The transmission end packet data convergence protocol (PDCP) entity is configured on a terminal device or a network device, and comprises: a transmission unit, which transmits first signaling to a reception end when it is considered that a PDCP sequence number (SN) gap has appeared, the first signaling comprising PDCP sequence number (SN) information of a dropped PDCP SDU.

Description

Information sending device, information receiving device Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] Support for extended reality (XR) services within 3GPP (3rd Generation Partnership Project) services and networks. XR services refer to all combined real and virtual environments and human-computer interactions enabled by computing technology and wearable devices. Application areas include, but are not limited to, entertainment, healthcare, and education. XR services can encompass representative forms such as virtual reality (VR), augmented reality (AR), and mixed reality (MR), as well as hybrid and interdisciplinary areas.

[0003] Virtual reality is a rendered version of a visual and audio scene that is presented to the viewer or user, designed to simulate the visual and auditory sensory stimulation of the real world as naturally as possible as the viewer or user moves within the limitations defined by the application. Augmented reality refers to the provision of additional information or artificially generated items or content overlaid on the user's current environment. Mixed reality is an advanced form of AR, in which some virtual elements are inserted into the physical scene to provide the illusion that these elements are part of the real scene.

[0004] A PDU Set consists of one or more Protocol Data Units (PDUs), which carry the payload of an information unit generated at the application layer, such as a frame or video slice for XR and media services. In some embodiments, the application layer requires all PDUs in a PDU Set to use the corresponding information unit. In other embodiments, when some PDUs are lost, the application layer can still recover all or part of the information unit.

[0005] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0006] Summary of the Invention

[0007] The inventors discovered that when the PDU Set Integrated Handling Information (PSIHI) of a QoS (Quality of Service) flow is configured, once a PDU in the PDU Set is clearly lost, the other PDUs in the PDU Set can be considered to have no effect on the application and can be discarded at the sending end to release wireless resources.

[0008] Discarding PDCP SDUs that have been associated with PDCP sequence numbers (SNs) creates a sequence number gap (SN gap) in the transmitted PDCP data PDUs, thereby increasing the PDCP reordering delay at the receiving PDCP entity. When discarding a PDU Set, a series of consecutive PDCP SDUs are often discarded, resulting in large sequence number gaps. Therefore, how to avoid or minimize sequence number gaps is a problem that needs to be solved.

[0009] In response to at least one of the above problems or other similar problems, embodiments of the present application provide a method and apparatus for sending and receiving information.

[0010] According to a first aspect of an embodiment of the present application, there is provided an information sending apparatus, which is applied to a transmitting-end Packet Data Convergence Protocol (PDCP) entity, wherein the transmitting-end Packet Data Convergence Protocol (PDCP) entity is configured in a terminal device or a network device, wherein the apparatus includes:

[0011] The sending unit sends a first signaling to a receiving end when it is considered that a PDCP sequence number (SN) gap occurs, wherein the first signaling includes PDCP sequence number (SN) information of the discarded PDCP SDU.

[0012] According to a second aspect of an embodiment of the present application, an information receiving apparatus is provided, which is applied to a receiving-end Packet Data Convergence Protocol (PDCP) entity, wherein the receiving-end Packet Data Convergence Protocol (PDCP) entity is configured in a network device or a terminal device, wherein the apparatus includes:

[0013] a receiving unit configured to receive a first signaling and a PDCP data PDU sent by a Packet Data Convergence Protocol (PDCP) entity at a transmitting end;

[0014] a processing unit, which adjusts a first state variable and / or a second state variable and / or a third state variable and / or a reordering window at a receiving end according to PDCP sequence number (SN) information of the discarded PDCP SDU indicated in the first signaling; and

[0015] A transmission unit that delivers the buffered PDCP SDUs to higher layers.

[0016] According to the third aspect of the embodiment of the present application, a terminal device is provided, wherein the terminal device includes the information sending device described in the embodiment of the first aspect; and / or, the terminal device includes the information receiving device described in the embodiment of the second aspect. One of the beneficial effects of the embodiment of the present application is that: when the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, it sends a first signaling to the receiving end, wherein the first signaling includes the PDCP sequence number (SN) information of the discarded PDCP SDU. Thus, by enhancing the sending end and the receiving end, the problem of sequence number gap caused by data discard is solved, the reordering delay is reduced, and the transmission performance of the XRM service is improved; through the indication of the first signaling, the problem of data discard of the PDU Set in the radio access network is solved, thereby increasing the user experience of XR and media services; in addition, by indicating the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it can also ensure the differentiated processing of the PDU Set and meet the integrated data processing requirements of the PDU Set, and better support the data transmission for the PDU Set.

[0017] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0018] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0019] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0021] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0022] FIG1 is a schematic diagram of an information sending method according to an embodiment of the present application;

[0023] FIG2 is an example diagram of the format of a PDCP control PDU as the first signaling according to an embodiment of the present application;

[0024] FIG3 is a schematic diagram of an information receiving method according to an embodiment of the present application;

[0025] FIG4 is an example diagram of the relationship between the PDCP SDU sequence number and the state variable according to an embodiment of the present application;

[0026] FIG5 is another example diagram of the relationship between the PDCP SDU sequence number and the state variable according to an embodiment of the present application;

[0027] FIG6 is a schematic diagram of an information sending device according to an embodiment of the present application;

[0028] FIG7 is a schematic diagram of an information receiving device according to an embodiment of the present application;

[0029] FIG8 is a schematic diagram of a terminal device according to an embodiment of the present application;

[0030] FIG9 is a schematic diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0031] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0032] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0033] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0034] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0035] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

[0036] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0037] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0038] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). Terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, etc.

[0039] Terminal devices may include, but are not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, and IAB-MT, etc.

[0040] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0041] Currently, 5G technology is researching key issues, solutions, and conclusions to support advanced media services, such as High Data Rate Low Latency (HDRLL) services, AR / VR / XR services, and tactile / multimodal communication services. The goals include:

[0042] 1. Enhancements to support multi-mode services, including:

[0043] - Investigate whether and how to enable applications to provide relevant tactile and multimodal data to users at similar times (e.g., audio, video, and tactile data associated with a specific time), focusing on the need for enhanced policy control (e.g., QoS policy coordination).

[0044] 2. Enhanced network exposure to support interaction between 5GS (5G system) and applications, including:

[0045] - Study whether and how to perform application synchronization and QoS (Quality of Service) policy coordination between multiple UEs or multiple QoS flows per UE, and how to interact between AF and 5GS.

[0046] - Study the exposure of 5GS QoS information (e.g., QoS capabilities) and network conditions to applications to enable fast codec / rate adaptation that helps deliver the desired QoE (e.g., helping alleviate 5GS congestion).

[0047] 3. Study whether and how to implement the following QoS and policy enhancements for XR service and media service transport, including:

[0048] -Study the traffic characteristics of media services that can improve network resource utilization and QoE (Quality of Experience).

[0049] - Enhance the QoS framework to support PDU Set granularity (e.g. video / audio frame / tile, application data unit, control information), where a PDU Set consists of PDUs with the same QoS requirements.

[0050] - Considering the different importance of PDU Sets, it supports differentiated QoS processing. For example, packets belonging to less important PDU Sets can be legally discarded to reduce resource waste.

[0051] - Whether and how to support uplink-downlink transmission coordination to meet the RTT (Round Trip Time) delay requirement between the UE and the N6 termination point of the UPF (User Plane Function).

[0052] - Potential policy enhancements to minimize jitter, focusing on demand provisioning from AF (Application Function) and extensions of PCC (policy and charging control) rules.

[0053] For uplink traffic, the NAS (non-access stratum) layer of the UE can identify information related to the PDU Set. Similar to downlink traffic, these PDU Set related information may include the PDU Set identifier, the PDU sequence number within the PDU Set, the PDU Set Importance, and optionally, the start and / or end flags of the PDU Set, the size of the PDU Set, etc. Among them, the PDU Set Importance (for example, it can be high, medium, low, or a digital expression from 0 to Nmax) indicates the importance of the PDU Set in the XRM (XR and media) service flow, or the priority, which is used by the RAN (Radio Access Network) to perform differentiated processing on the PDU Set, such as priority processing, scheduling, data discarding, etc.

[0054] When the PDU Set Integrated Handling Information (PSIHI) of a QoS (Quality of Service) flow is configured, once a PDU in the PDU Set is clearly lost, the other PDUs in the PDU Set can be considered to have no effect on the application and can be discarded at the sending end to free up radio resources.

[0055] For example, for PDU Set discard,

[0056] For PDU set discard on the terminal side, for example, for uplink traffic, a PDU Set-based discard operation can be configured for a specific DRB of the terminal device (UE). When the UE is configured, when the UE discards a PDU due to a discard timer expiration, it also discards all packets in the PDU Set to which the PDU belongs.

[0057] For PDU set discard on the network device side, for example, the base station can perform downlink PDU Set discard based on implementation, while considering at least parameters such as PDU Set Delay Budget (PSDB), PDU Set Importance (PSI), PSIHI, etc.; or, in congestion conditions, the base station can use PSI to perform PDU Set discard. At this time, for uplink traffic, dedicated downlink signaling is used to request the UE to apply a shorter discard timer for low-importance SDUs at the PDCP layer.

[0058] Discarding the PDCP SDU that has been associated with the PDCP sequence number (SN) will cause a sequence number gap (SN gap) in the sent PDCP data PDU, thereby increasing the PDCP reordering delay of the receiving PDCP entity. In addition, when discarding a PDU Set, a series of consecutive PDCP SDUs are often discarded, resulting in a large sequence number gap. Therefore, how to avoid or minimize the sequence number gap is a problem that needs to be solved. The present application considers performing sequence number (SN) reporting related operations at the PDCP (Packet Data Convergence Protocol) layer, including the triggering conditions for sending sequence number reports and the operational procedures for receiving sequence number reports.

[0059] Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application. In the following description, expressions such as "if...", "in the case of...", and "when..." have the same meaning and are interchangeable.

[0060] Embodiments of the first aspect

[0061] An embodiment of the present application provides an information sending method, which is described from the perspective of a Packet Data Convergence Protocol (PDCP) entity at the sending end.

[0062] The information sending method of the present application can be applied to terminal devices or network devices, and the present application does not impose any restrictions on this.

[0063] FIG1 is a schematic diagram of a method for sending information according to an embodiment of the present application. As shown in FIG1 , the method includes:

[0064] 101: A Packet Data Convergence Protocol (PDCP) entity at a transmitting end sends a first signaling to a receiving end when it is determined that a PDCP sequence number (SN) gap occurs, wherein the first signaling includes PDCP sequence number (SN) information of a discarded PDCP SDU.

[0065] In some embodiments, since the count (COUNT) of the PDCP SDU includes the hyperframe number (HFN) and the sequence number, the sequence number can be replaced by the COUNT. In the present invention, the sequence number (SN) and the count (COUNT) can be interchangeable.

[0066] According to an embodiment of the present application, the Packet Data Convergence Protocol (PDCP) entity at the transmitting end sends a first signaling to the receiving end when it believes that a PDCP sequence number (SN) gap has occurred, wherein the first signaling includes the PDCP sequence number (SN) information of the discarded PDCP SDU. Thus, by enhancing the transmitting end and the receiving end, the problem of sequence number gaps caused by data discard is solved, the reordering delay is reduced, and the transmission performance of the XRM service is improved; through the indication of the first signaling, the problem of data discard of the PDU Set in the wireless access network is solved, thereby increasing the user experience of XR and media services; in addition, by indicating the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it is also possible to ensure the processing of differentiated PDU Sets and meet the integrated data processing requirements of the PDU Set, thereby better supporting data transmission for the PDU Set.

[0067] In some embodiments, the expression "PDCP SDU" may be replaced by "SDU"; a "discarded PDCP SDU" is an SDU that has been associated with a PDCP sequence number.

[0068] In some embodiments, the first signaling is a PDCP Control PDU. For example, the PDCP Control PDU is used to report PDCP sequence number (SN) information of a discarded PDCP SDU. For example, the PDCP Control PDU can be called a PDCP SN report, a PDCP SN gap report, a PDCP SN notification, etc. For details about the first signaling, see the relevant content in FIG. 2 and other sections described below.

[0069] In some embodiments, the first signaling is sent by the PDCP entity that sends data on the sending end to the PDCP entity that receives data on the receiving end. For example, the sending end Packet Data Convergence Protocol (PDCP) entity can be configured on the terminal device side or the network device side, and the corresponding receiving end Packet Data Convergence Protocol (PDCP) entity can be configured on the network device side or the terminal device side. For example, for uplink traffic, the terminal device (UE) sends the first signaling to the network device when it believes that an SN gap has occurred (or detects or predicts); for downlink traffic, the network device sends the first signaling to the terminal device (UE) when it believes that an SN gap has occurred. As a result, the receiving end PDCP entity on the other end of the sending end PDCP entity will know which SDU sequence numbers have been discarded by the sending end, and therefore will not wait to receive these data, thereby avoiding reordering delays.

[0070] In some embodiments, when the terminal device is configured with a first field, the sending end Packet Data Convergence Protocol (PDCP) entity sends the first signaling to the receiving end when it believes that a PDCP sequence number (SN) gap has occurred; wherein the first field is configured through Radio Resource Control (RRC) signaling.

[0071] For example, the network device may configure a Packet Data Convergence Protocol (PDCP) entity of the UE to determine whether to support sending the first signaling. For example, the network device may add a first field, such as "snReportRequired," to a "PDCP-Config" information element (IE) in an "RRCReconfiguration" message.

[0072] For example, when the terminal device is configured with the first field and the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, the sending end Packet Data Convergence Protocol (PDCP) entity sends the first signaling to the receiving end; for example, when the terminal device is not configured with the first field, even if the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, the sending end Packet Data Convergence Protocol (PDCP) entity does not send the first signaling to the receiving end.

[0073] In some embodiments, the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, including at least one of the following: the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs; the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and a first timer is not running; the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and the number of discarded PDCP SDUs is greater than a first threshold; the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and the PDCP sequence number (SN) gap is due to a PDU group (PDU Set) discard; or, the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and the PDCP sequence number (SN) gap is due to a PDU set importance-based discard.

[0074] The following examples illustrate "a transmitting-side Packet Data Convergence Protocol (PDCP) entity deeming a PDCP sequence number (SN) gap to have occurred":

[0075] In some embodiments, the first signaling is sent when a Packet Data Convergence Protocol (PDCP) entity at the transmitting end believes that a PDCP sequence number (SN) gap occurs.

[0076] For example, as long as a PDCP SDU with a sequence number is discarded before being sent, and the sequence number cannot be re-associated with other SDUs, it means that an SN gap has occurred. Alternatively, if the SN associated with a cached SDU is higher than the SN of one or more discarded SDUs, and the discarded SDU has not been sent, the sending of the first signaling can be triggered. The PDCP SDU has not been sent yet, which may mean that the SDU has not been delivered to the lower layer (RLC, Radio Link Control layer) by the PDCP entity, or that the RLC layer has not delivered the SDU to the lower layer, that is, it is still in the RLC cache.

[0077] In some embodiments, sending the first signaling when the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred also includes: after the sending end Packet Data Convergence Protocol (PDCP) entity last sent the first signaling, at least one cached PDCP SDU is associated with a PDCP sequence number (SN) higher than the PDCP sequence number (SN) of the discarded PDCP SDU and the discarded PDCP SDU has not been sent, sending the first signaling.

[0078] In some embodiments, in combination with DRBs of different modes corresponding to the PDCP entity, when the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, sending the first signaling further includes:

[0079] For example, for an Acknowledged Mode (AM) DRB, if a buffered SDU is associated with a higher SN than the SN of one or more discarded SDUs, and the discarded SDU has not been sent or acknowledged (i.e., an indication from the lower layer that the PDCP PDU has been successfully delivered) then the sending of the first signaling may be triggered;

[0080] For example, for an Unacknowledged Mode (UM) DRB, if a buffered SDU is associated with a higher SN than the SN of one or more discarded SDUs, and the discarded SDUs have not been sent, the sending of the first signaling may be triggered.

[0081] Therefore, when the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, the first signaling is sent, which can promptly solve the problem of sequence number gap caused by data discard, reduce the reordering delay, and thus improve the transmission performance of the XRM service.

[0082] In some implementations, when a Packet Data Convergence Protocol (PDCP) entity at a transmitting end considers that a PDCP sequence number (SN) gap occurs and a first timer is not running, the first signaling is sent:

[0083] When the first timer is running, the sending end Packet Data Convergence Protocol (PDCP) entity does not send the first signaling; and when the first timer expires and the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, the sending end Packet Data Convergence Protocol (PDCP) entity sends the first signaling.

[0084] Therefore, considering that sending the first signaling every time an SN gap occurs will cause network congestion, setting the first timer can avoid frequent sending of the first signaling, reduce signaling overhead, and avoid network congestion.

[0085] In some embodiments, in the terminal device, the first timer is configured through a second field, wherein the second field is configured through Radio Resource Control (RRC) signaling.

[0086] For example, the first timer serves as a prohibit timer, which is a timer maintained by each PDCP entity. For example, the duration of the first timer can be configured by the network device, for example, by adding a new second field in the PDCP-Config IE in the RRCReconfiguration message.

[0087] For example, when a Packet Data Convergence Protocol (PDCP) entity at the transmitting end sends the first signaling, the first timer is started.

[0088] In some embodiments, the first signaling is sent when a Packet Data Convergence Protocol (PDCP) entity at the transmitting end believes that a PDCP sequence number (SN) gap occurs and the number of discarded PDCP SDUs is greater than a first threshold.

[0089] For example, when the transmitting-end Packet Data Convergence Protocol (PDCP) entity believes that the number of discarded PDCP SDUs is greater than a first threshold, for example, the first threshold is 10, the first signaling is sent.

[0090] Therefore, the sending of the first signaling is triggered only when the number of discarded SNs reaches a certain number. When there are a small number of SN gaps, there is no need to send the first signaling separately. This can avoid frequent sending of the first signaling, reduce signaling overhead, and avoid network congestion.

[0091] In some embodiments, the sending end packet data convergence protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, and the PDCP sequence number (SN) gap is due to a PDU group (PDU Set) discard; or the sending end packet data convergence protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, and the PDCP sequence number (SN) gap is due to a PDU group importance (PDU Set Importance)-based discard, and sends a first signaling.

[0092] Regarding the situation where the transmitting-end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap has occurred, and the PDCP sequence number (SN) gap is due to a PDU set (PDU Set) discard:

[0093] For example, PDU Set discard means that when the PDCP entity of the UE is configured with "pdu-SetDiscard", when the discard timer of an SDU times out, all PDCP SDUs and corresponding PDCP Data PDUs in the PDU Set to which the SDU belongs are discarded. For example, "the Packet Data Convergence Protocol (PDCP) entity at the transmitting end believes that a PDCP sequence number (SN) gap has occurred, and the PDCP sequence number (SN) gap is due to a PDU group (PDU Set) discard" means: if there is a cached SDU associated with an SN higher than the SN of one or more discarded SDUs, and the discarded SDU has not been sent, and the PDCP entity is configured with pdu-SetDiscard, and one or more discarded SDUs belong to the PDU Set, then the sending of the first signaling can be triggered.

[0094] Regarding the situation where "a Packet Data Convergence Protocol (PDCP) entity at the transmitting end considers that a PDCP Sequence Number (SN) gap has occurred, and the PDCP Sequence Number (SN) gap is due to a PDU Set Importance-based drop":

[0095] For example, in the case of PSI-based discarding, specifically, the UE's PDCP entity is configured with a second timer (discardTimerForLowImportance) (a discard timer for low importance). When the discardTimerForLowImportance of a certain SDU times out, since all the PDCP SDUs in the PDU Set to which they belong are configured with discard timers of the same length, and the time when these SDUs arrive at the PDCP layer is generally the same or very close, the entire PDU Set will also be discarded almost at the same time; then "the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, and the PDCP sequence number (SN) gap is due to a discard based on the PDU group importance (PDU Set Importance)" means: if there is a cached SDU associated with an SN that is higher than the SN of the SDU discarded due to the discardTimerForLowImportance timeout, and the discarded SDU has not yet been sent, then the sending of the first signaling can be triggered.

[0096] Therefore, for the two cases of "PDU Set discard" and "PSI-based discard", since the PDU Set is discarded, the SN gap caused by this is larger or more. When all the PDCP SDUs in a PDU Set are discarded, the first signaling is reported, which can avoid frequent sending of the first signaling, reduce signaling overhead, and avoid network congestion.

[0097] Combining the above two situations of "PDU Set discard" and "PSI-based discard":

[0098] In some embodiments, in the terminal device, when the first field is configured, the first signaling is triggered when the PDCP sequence number (SN) associated with at least one cached PDCP SDU is higher than the PDCP sequence number (SN) of the discarded PDCP SDU and the discarded PDCP SDU has not been sent, and the PDCP entity is configured with PDU group discard (pdu-SetDiscard) and the discarded PDCP SDU belongs to a PDU group (PDU Set); or, when the first field is configured, the first signaling is triggered when the PDCP sequence number (SN) associated with at least one cached PDCP SDU is higher than the PDCP sequence number (SN) of the PDCP SDU discarded due to the expiration of the second timer (discardTimerForLowImportance) and the discarded PDCP SDU has not been sent.

[0099] For example, Table 1 is an example of the corresponding enhancements in the standard:

[0100] Table 1

[0101] After clarifying the conditions for triggering the sending of the first signaling, the specific content of the first signaling is introduced below:

[0102] In some embodiments, the first signaling includes a third field and a fourth field, wherein the third field indicates a count (COUNT) value of the first SDU in the discarded PDCP SDU; wherein the fourth field is an M-bit bitmap, where M is greater than or equal to 0.

[0103] For example, the first signaling includes a third field, which indicates the COUNT value of the first SDU in the discarded SDUs, that is, the PDCP sequence number of the SDU, which may be called the first discarded count (FDC).

[0104] For example, the fourth field is a bitmap of indefinite length, such as an M-bit bitmap, where M is greater than or equal to 0, and the indefinite-length bitmap is indicated in a bitmap manner.

[0105] Figure 2 is an example diagram of the format of a PDCP control PDU as the first signaling according to an embodiment of the present application. For example, the first signaling is implemented by a PDCP control PDU, and the format of the PDCP control PDU can be seen in Figure 2.

[0106] As shown in FIG2 , the PDCP control PDU may use 0 as the D / C bit in the PDCP header to indicate that it is a control PDU, and define a new PDU type (eg, binary bit 100) to indicate that the PDU is a PDCP sequence number gap report.

[0107] For example, the third field FDC is 32 bits (4 bytes), and the fourth field Bitmap is N bytes (M bits), where the N bytes are determined according to the range of SNs that need to be reported; the length of the fourth field Bitmap can be 0, that is, the first signaling only contains one SN, which is the SN indicated by the FDC in the third field; wherein, the fourth field Bitmap indicates which SDUs are discarded and which SDUs are not discarded at the transmitting PDCP entity; wherein, the i-th bit in the fourth field Bitmap is called the i-th bit position, that is, the bit position of the first bit of the Bitmap is 1, and so on.

[0108] In some embodiments, for the i-th bit in the fourth field, where i is greater than or equal to 1 and less than or equal to M, when the bit value of the i-th bit is a first value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is not discarded; when the bit value of the i-th bit is a second value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is discarded.

[0109] For example, the first value is "0", and when the i-th bit is 0, it indicates that the PDCP SDU with a COUNT value of [(FDC+i)modulo 2^32] is not discarded; the second value is "1", and when the i-th bit is 1, it indicates that the PDCP SDU with a COUNT value of [(FDC+i)modulo 2^32] is discarded; or the first value is "1", the second value is "0", etc., and this application is not limited to this; wherein modulo is a remainder calculation.

[0110] In some embodiments, the transmitting PDCP entity generates the first signaling according to the following operations:

[0111] Setting the third field to a count value of the first PDCP SDU discarded and not transmitted after the first signaling was last sent;

[0112] In a case where there is a second PDCP SDU that is discarded and not transmitted, wherein the count (COUNT) value of the second PDCP SDU that is discarded and not transmitted is greater than the count (COUNT) value of the first PDCP SDU that is discarded and not transmitted indicated by the third field:

[0113] generating the fourth field, wherein the bit length of the fourth field is the number of sequence numbers between a PDCP SDU following the first PDCP SDU that is discarded and not transmitted and a last PDCP SDU that is discarded and not transmitted, wherein the fourth field is rounded backward to a multiple of 8; or the bit length of the fourth field is the number of sequence numbers between a PDCP SDU following the first PDCP SDU that is discarded and not transmitted and a specific PDCP SDU, wherein the specific PDCP SDU is the first PDCP SDU that makes the size of the generated PDCP control PDU equal to 9000 bytes, taking the smaller value of the two numbers;

[0114] Setting the bits in the bitmap corresponding to all discarded and unsent PDCP SDUs in the fourth field to "1", otherwise setting the bits to "0";

[0115] The first signaling is delivered to a lower layer as the first PDCP PDU to be sent through the transmitting-end Packet Data Convergence Protocol (PDCP) entity.

[0116] For example, if the sending of the first signaling is triggered, the transmitting PDCP entity needs to perform the following operations:

[0117] - Follow the instructions below to build a first signaling:

[0118] - The value of the third field is set to the COUNT value of the first SDU that was discarded and not sent after the last first signaling (if any);

[0119] - If there are more discarded SDUs with a COUNT value greater than the third field:

[0120] - a fourth field (bitmap) is allocated with a bit length equal to the number of COUNT values ​​from the first (excluding the first) discarded PDCP SDU to the last (including the last) discarded PDCP SDU, rounded down to a multiple of 8, or to a PDCP SDU (including this one) such that the size of the generated PDCP Control PDU is equal to 9000 bytes, whichever comes first;

[0121] - Set the bit in the fourth field (bitmap) corresponding to all discarded and untransmitted PDCP SDUs to "1", otherwise to "0";

[0122] -Deliver the first signaling as the first PDCP PDU to be sent to the lower layer through the transmitting PDCP entity.

[0123] For example, Table 2 is an example of the corresponding enhancements in the standard:

[0124] Table 2

[0125] Therefore, the sequence number information of the discarded SDU can be indicated through the third field and / or the fourth field, which solves the problem of sequence number gaps caused by data discard, reduces reordering delays, and thus improves the transmission performance of the XRM service.

[0126] The above embodiments are merely exemplary descriptions of the methods of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0127] According to the above embodiment, the Packet Data Convergence Protocol (PDCP) entity at the transmitting end sends a first signaling to the receiving end when it believes that a PDCP sequence number (SN) gap has occurred, wherein the first signaling includes the PDCP sequence number (SN) information of the discarded PDCP SDU. Thus, by enhancing the transmitting end and the receiving end, the problem of sequence number gaps caused by data discard is solved, the reordering delay is reduced, and the transmission performance of the XRM service is improved; through the indication of the first signaling, the problem of data discard of the PDU Set in the wireless access network is solved, thereby increasing the user experience of XR and media services; in addition, by indicating the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it is also possible to ensure the processing of differentiated PDU Sets and meet the integrated data processing requirements of the PDU Set, thereby better supporting data transmission for the PDU Set.

[0128] Embodiments of the second aspect

[0129] An embodiment of the present application provides an information receiving method, which is described from the perspective of a receiving-end Packet Data Convergence Protocol (PDCP) entity.

[0130] The information receiving method of the present application can be applied to a terminal device or a network device, and the present application does not limit this; the content that is the same as the embodiment of the first aspect will not be repeated here.

[0131] FIG3 is a schematic diagram of an information receiving method according to an embodiment of the present application. As shown in FIG3 , the method includes:

[0132] 301, a Packet Data Convergence Protocol (PDCP) entity at a receiving end receives first signaling and PDCP data PDU sent by a Packet Data Convergence Protocol (PDCP) entity at a transmitting end;

[0133] 302. A Packet Data Convergence Protocol (PDCP) entity at a receiving end adjusts a first state variable and / or a second state variable and / or a third state variable and / or a reordering window at the receiving end according to PDCP sequence number (SN) information of the discarded PDCP SDU indicated in the first signaling; and

[0134] 303. The receiving-end Packet Data Convergence Protocol (PDCP) entity transfers the buffered PDCP SDU to a higher layer.

[0135] According to the embodiments of the present application, by enhancing the transmitting and receiving ends, the problem of sequence number gaps caused by data discard is solved, the reordering delay is reduced, and the transmission performance of the XRM service is improved; by receiving the indication of the first signaling, the problem of data discard of the PDU Set in the wireless access network is solved, thereby increasing the user experience of XR and media services; in addition, by receiving the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it is also possible to ensure differentiated PDU Set processing and meet the integrated data processing requirements of the PDU Set, thereby better supporting data transmission for the PDU Set.

[0136] In some embodiments, in step 301, the process in which the receiving-end Packet Data Convergence Protocol (PDCP) entity receives the first signaling sent by the transmitting-end Packet Data Convergence Protocol (PDCP) entity corresponds to the relevant process in step 101 of the embodiment of the first aspect, and will not be repeated here; in addition, the specific content and format of the PDCP data PDU in step 301 can be referred to the prior art, and this application does not limit this.

[0137] For example, after receiving the first signaling, the receiving PDCP entity may store / record the sequence number (COUNT value) information of the discarded SDU. The receiving PDCP entity adjusts the receiving state variable and / or reordering window based on the sequence number of the SDU discarded by the transmitting end indicated in the first signaling, and the receiving PDCP entity transfers the buffered SDU to the upper layer.

[0138] In some embodiments, the first signaling includes a third field and a fourth field, wherein the third field indicates a count (COUNT) value of the first SDU in the discarded PDCP SDU; wherein the fourth field is an M-bit bitmap, where M is greater than or equal to 0.

[0139] In some embodiments, for the i-th bit in the fourth field, where i is greater than or equal to 1 and less than or equal to M, when the bit value of the i-th bit is a first value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is not discarded; when the bit value of the i-th bit is a second value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is discarded.

[0140] For example, for the specific content of the first signaling, please refer to the relevant content in Figure 2 and other places in the embodiment of the first aspect, and will not be repeated here.

[0141] For example, if the receiving end is the UE side, then this first signaling (discard report) is for downlink data and is sent by the network side; and, on the UE side, for DRB, when the first signaling is received in the downlink, the receiving end PDCP entity must consider each PDCP SDU (if any) with a bit value of 1 in the fourth field (Bitmap) or the PDCP SDU indicated by the third field as having been discarded, without waiting for these discarded SDUs (which is similar to assuming that these SDUs have been received or delivered to the upper layer), and directly deliver the stored SDUs to the upper layer in sequence.

[0142] The following is a detailed description of the content of step 302:

[0143] In some embodiments, a first state variable (RX_NEXT) indicates a count value of a next PDCP SDU expected to be received; a second state variable (RX_DELIV) indicates a count value of a first PDCP SDU that has not been delivered to a higher layer but is still waiting to be received; and a third state variable (RX_REORD) indicates a next count value of a count value associated with a PDCP data PDU that triggers a third timer (t-Reordering).

[0144] For example, according to the size relationship between the state variables RX_DELIV and RX_NEXT maintained by the existing receiving-end PDCP entity, the positions of the discarded SDUs can be divided into several cases for discussion.

[0145] FIG4 is an example diagram of the relationship between the PDCP SDU sequence number and the state variable according to an embodiment of the present application; FIG5 is another example diagram of the relationship between the PDCP SDU sequence number and the state variable according to an embodiment of the present application.

[0146] For example, Figure 4 shows the sequence numbers of the SDUs currently received and not received by the receiving end when the first signaling is received, the values ​​of the corresponding state variables, and the COUNT values ​​of the discarded SDUs indicated by the first signaling; Figure 5 shows the situation after the receiving end adjusts the state variables in the scenario of Figure 4 after receiving the first signaling.

[0147] For example, Figures 4 and 5 include SDUs with sequence numbers 0 to 7, among which SDUs with sequence numbers 1, 3, and 6 are discarded SDUs, and SDUs with sequence numbers 0 and 4 are SDUs that have been received by the receiving end; SDUs with sequence numbers 2, 5, and 7 are SDUs that have not been discarded but have not been received by the receiving end; for the discarded SDUs in Figures 4 and 5, their corresponding count (COUNT) values ​​are equal to the corresponding sequence numbers, for example, COUNT1=1, COUNT2=3, and COUNT3=6.

[0148] For example, for COUNT1, when the first command is received, RX_DELIV corresponds to COUNT1 as shown in Figure 4. After receiving the first command, as described in Figure 5, RX_DELIV needs to be increased by 1, indicating that there is no need to wait for the SDU with sequence number 1; for COUNT3, RX_NEXT corresponds to the SDU with sequence number 5 as shown in Figure 4. After receiving the first command, as described in Figure 5, RX_NEXT=7, indicating that the SDU with sequence number 6 has been discarded, then the sequence number of the next SDU expected to be received is 7; for COUNT2, when the first command is received, the current moment does not affect RX_DELIV and RX_NEXT, and it is necessary to wait until subsequent data is received. For example, if RX_DELIV=3, then RX_DELIV is increased by 1.

[0149] For example, the state variable RX_REORD is a state variable maintained by the receiving PDCP entity, indicating the next COUNT value of the COUNT value associated with the PDCP data PDU that triggers the reordering timer. It also needs to be adjusted accordingly, which will be explained in conjunction with the subsequent specific implementation methods.

[0150] Impact on the standard Taking the UE side as an example, when the first signaling (PDCP SN report) is received, the corresponding operation is performed according to the discarded sequence number indicated in the first signaling (PDCP SN report); the purpose of the operation is to take into account the discarded SDUs, submit the currently deliverable SDUs to the upper layer, and adjust the state variables.

[0151] The following examples illustrate the process of adjusting each state variable in conjunction with various implementation methods:

[0152] In some embodiments, the receiving PDCP considers that the PDCP SDU associated with each bit value of the fourth field having the second value and / or the COUNT value of the first PDCP SDU indicated by the third field has been discarded.

[0153] For example, for DRB, after receiving the first signaling (PDCP SN report) from the downlink, the receiving PDCP entity considers that each PDCP SDU (if any) with a bit value of 1 in the fourth field (Bitmap) and the PDCP SDU corresponding to the associated COUNT value equal to the FDC value of the third field has been discarded.

[0154] In some embodiments, the receiving PDCP performs the following loop operation based on the ascending order of the count value of the discarded PDCP SDUs:

[0155] In the case where the count (COUNT) value is greater than or equal to the first state variable (RX_NEXT):

[0156] Update the first state variable (RX_NEXT) to the count (COUNT) value + 1;

[0157] In the case where there is a second state variable (RX_DELIV) = the count (COUNT) value:

[0158] starting from the count value in the second state variable (RX_DELIV)=the count value, delivering all stored PDCP SDUs with consecutive count values ​​to a higher layer in ascending order of associated count values ​​after performing header decompression; and

[0159] Updating the second state variable (RX_DELIV) to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV);

[0160] When the third timer (t-Reordering) is running and the second state variable (RX_DELIV) is greater than or equal to the third state variable (RX_REORD): stop and reset the third timer (t-Reordering);

[0161] When the third timer (t-Reordering) is not running and the second state variable (RX_DELIV) is less than the third state variable (RX_REORD): the third state variable (RX_REORD) is updated to the first state variable (RX_NEXT); and the third timer (t-Reordering) is started.

[0162] For example,

[0163] - For the COUNT values ​​of discarded SDUs, perform the following loop operation in ascending order:

[0164] -If the COUNT value >= RX_NEXT:

[0165] - Update RX_NEXT to the COUNT value + 1;

[0166] - If RX_DELIV = the COUNT value:

[0167] - starting from COUNT value = RX_DELIV, deliver all stored PDCP SDUs with consecutive COUNT values ​​to higher layers in ascending order of associated COUNT values ​​after performing header decompression (if not already performed);

[0168] - Update RX_DELIV to the COUNT value of the first PDCP SDU that is not delivered to higher layers and not discarded, where COUNT > RX_DELIV (i.e. if the COUNT value is greater than the RX_DELIV before the update);

[0169] - If t-Reordering (reordering timer) is running and RX_DELIV>=RX_REORD:

[0170] - Stop and reset the reordering timer;

[0171] - If the reorder timer is not running and RX_DELIV <RX_NEXT:

[0172] - Update RX_REORD to RX_NEXT;

[0173] -Start the reorder timer.

[0174] For example, the above-mentioned "performing the following loop operation on the COUNT values ​​of discarded SDUs in ascending order" can also be replaced by a one-time step, as described below:

[0175] In some embodiments, the receiving PDCP performs the following operations based on the count value of discarded PDCP SDUs:

[0176] When the maximum value of the count (COUNT) values ​​of all discarded PDCP SDUs is greater than or equal to the first state variable (RX_NEXT): the first state variable (RX_NEXT) is updated to the maximum count (COUNT) value+1.

[0177] In some embodiments, the receiving PDCP further performs the following operations:

[0178] In the case where the second state variable (RX_DELIV) = the count (COUNT) value of any discarded PDCP SDU exists:

[0179] delivering all stored PDCP SDUs with consecutive count (COUNT) values ​​equal to the second state variable (RX_DELIV) to a higher layer in ascending order of associated count (COUNT) values ​​after performing header decompression, wherein the consecutive count (COUNT) values ​​include the count (COUNT) value of the discarded PDCP SDU; and

[0180] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to the upper layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

[0181] For example,

[0182] - If the maximum value of the COUNT of all discarded SDUs is greater than or equal to RX_NEXT:

[0183] -Update RX_NEXT to the maximum COUNT value + 1;

[0184] - If RX_DELIV = COUNT of any discarded SDUs:

[0185] - starting from COUNT value = RX_DELIV, all stored PDCP SDUs with consecutive COUNT values ​​are delivered to higher layers in ascending order of associated COUNT values ​​after header decompression (if not already performed). NOTE: When considering consecutive COUNT values, COUNT values ​​of discarded SDUs are also included;

[0186] (For example, if the stored SDU COUNT values ​​are 1, 2, 4, and 6, and the discarded SDU COUNT value is 3, then 1, 2, 3, and 4 are consecutive COUNT values, and SDUs with COUT values ​​of 1, 2, and 4 are delivered to the upper layer)

[0187] - Update RX_DELIV to the COUNT value of the first PDCP SDU that is not delivered to higher layers and not discarded, where COUNT > RX_DELIV.

[0188] (That is, if the COUNT value is greater than RX_DELIV before the update)

[0189] For example, Table 3 is an example of the corresponding enhancements in the standard:

[0190] Table 3

[0191] In some embodiments, after the state variable is adjusted, if there are still sequence numbers of discarded SDUs between RX_DELIV and RX_NEXT, that is, there is at least one COUNT value of a discarded SDU that satisfies RX_DELIV < COUNT < RX_NEXT, it means that the subsequent change of the state variable will still be affected by this sequence number, and this sequence number may still be needed in the future. That is, when receiving a PDCP Data PDU in the future, the state variable still needs to be adjusted according to the COUNT value of the discarded SDU, and the adjustment method is similar to the above method. For example, the at least one COUNT value can be saved, or the information of the first signaling can be saved, or a new variable can be defined as a boolean indicator. If it is indicated as true, it means that when receiving a PDCP Data PDU, the information of the first signaling received last time needs to be considered.

[0192] For example, when performing a data reception operation, possible operations are carried out based on the magnitude relationship of each variable and the sequence number information of the discarded SDU saved when receiving the first signaling previously.

[0193] For example, taking the UE side as an example, when receiving a PDCP data PDU from the lower layer, the following operations need to be carried out after judging that the conditions are met. The purpose of the operation is that when the current PDCP data PDU reception and processing are completed, the state variable changes. At this time, using the sequence number information of the discarded SDU, the SDUs that can be delivered currently are delivered to the upper layer. It is basically the same as the method for adjusting the state variable when receiving the first signaling previously.

[0194] In some embodiments, when the PDCP data PDU received by the receiving-end PDCP entity is not discarded, the receiving-end PDCP entity performs the following operations:

[0195] In the case where out-of-order delivery is not configured, the following cyclic operation is performed in ascending order for the count (COUNT) value of the PDCP SDU considered to be discarded in the first signaling received last time:

[0196] In the case where there is a second state variable (RX_DELIV) = this count (COUNT) value:

[0197] Starting from this count (COUNT) value in the second state variable (RX_DELIV) = this count (COUNT) value, all stored PDCP SDUs with consecutive count (COUNT) values are delivered to the upper layer in ascending order of the associated count (COUNT) value after performing header decompression;

[0198] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to the upper layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

[0199] For example, if the received PDCP data PDU is not discarded (meaning that a data PDU with the same COUNT has not been received before), the receiving PDCP entity needs to:

[0200] - If outOfOrderDelivery is not configured, the following loop operation is performed in ascending order for the COUNT value (if any) of the SDUs considered to be discarded in the last received first signaling:

[0201] - If RX_DELIV = the COUNT value:

[0202] - starting from COUNT value = RX_DELIV, deliver all stored PDCP SDUs with consecutive COUNT values ​​to higher layers in ascending order of associated COUNT values ​​after performing header decompression (if not already performed);

[0203] - Update RX_DELIV to the COUNT value of the first PDCP SDU not delivered to higher layers, where COUNT>RX_DELIV (i.e. if the COUNT value is greater than RX_DELIV before the update).

[0204] In some embodiments, when the PDCP data PDU received by the receiving PDCP entity is not discarded, the receiving PDCP entity performs the following operations:

[0205] In the absence of out-of-order delivery (outOfOrderDelivery) being configured, the following loop operation is performed in ascending order for the count value (COUNT) of the PDCP SDUs considered to be discarded in the last received first signaling:

[0206] In the case where there is a second state variable (RX_DELIV) = the count (COUNT) value:

[0207] starting from the count value in the second state variable (RX_DELIV) = the count value, delivering all stored PDCP SDUs with consecutive count values ​​to a higher layer in ascending order of associated count values ​​after performing header decompression;

[0208] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to the upper layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

[0209] For example,

[0210] - In the case that outOfOrderDelivery is not configured, if RX_DELIV = COUNT value of any discarded SDU in the first signaling received last time (if any):

[0211] - starting from COUNT value = RX_DELIV, all stored PDCP SDUs with consecutive COUNT values ​​are delivered to higher layers in ascending order of associated COUNT values ​​after header decompression (if not already performed). NOTE: When considering consecutive COUNT values, COUNT values ​​of discarded SDUs are also included;

[0212] - Update RX_DELIV to the COUNT value of the first PDCP SDU that is not delivered to higher layers and not discarded, where COUNT>RX_DELIV (i.e., if the COUNT value is greater than the RX_DELIV before the update).

[0213] In some implementations, the aforementioned enhancements can be performed only when the reordering timer (t-Reordering) is running. That is, if the reordering timer is not running, indicating that there is no reordering window, the previous first signaling will not affect the current state. The aforementioned enhancements can also be performed only by determining whether the first variable is true. Therefore, subsequent operations on the UE side can be reduced in this state, improving efficiency.

[0214] For example, Table 4 is an example of corresponding enhancements in the standard:

[0215] Table 4

[0216] The above enhancements are performed when outOfOrderDelivery is not configured. In other words, the receiving PDCP entity needs to deliver the received SDUs to higher layers on demand.

[0217] In some implementations, when the PDCP data PDU received by the receiving PDCP entity is not discarded, the receiving PDCP entity performs the following operations:

[0218] When the second state variable (RX_DELIV) = the count (COUNT) value of the received PDCP data PDUs:

[0219] starting from a COUNT value equal to the second state variable (RX_DELIV), delivering all stored PDCP SDUs with consecutive COUNT values ​​after performing header decompression to a higher layer in ascending order of associated COUNT values, wherein the consecutive COUNT values ​​include the COUNT value of the discarded SDU; and

[0220] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to the upper layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

[0221] For example, if the received PDCP data PDU is not discarded (meaning that a data PDU with the same COUNT has not been received before), the receiving PDCP entity needs to:

[0222] -If RCVD_COUNT=RX_DELIV:

[0223] - starting from COUNT value = RX_DELIV, all stored PDCP SDUs with consecutive COUNT values ​​are delivered to higher layers in ascending order of associated COUNT values ​​after header decompression (if not already performed). NOTE: When considering consecutive COUNT values, COUNT values ​​of discarded SDUs are also included;

[0224] - Update RX_DELIV to the COUNT value of the first PDCP SDU that is not delivered to higher layers and not discarded, where COUNT > RX_DELIV (i.e. if the COUNT value is greater than the RX_DELIV before the update);

[0225] RCVD_COUNT is the COUNT value of the received PDCP Data PDU; the discarded SDU is obtained based on the information in the first signaling received last time.

[0226] In addition, the behavior when the reordering timer expires also needs to be enhanced accordingly, because after the reordering timer expires, the stored SDUs need to be delivered to the upper layer and the state variables need to be updated.

[0227] In some implementations, when the third timer (t-Reordering) expires, the receiving PDCP performs the following operations:

[0228] For all stored PDCP SDUs whose COUNT values ​​are less than the third state variable (RX_REORD), and all stored PDCP SDUs with consecutive COUNT values ​​starting from the COUNT value corresponding to the third state variable (RX_REORD), after performing header decompression, the consecutive COUNT values ​​are delivered to a higher layer in ascending order of the associated COUNT values, wherein the consecutive COUNT values ​​include the COUNT value of the discarded SDU; and

[0229] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than or equal to the third state variable (RX_REORD).

[0230] For example, when the reordering timer expires, the receiving PDCP entity needs to perform the following operations:

[0231] - All stored PDCP SDUs with COUNT values ​​less than RX_REORD and all stored PDCP SDUs with consecutive COUNT values ​​starting from COUNT = RX_REORD are delivered to higher layers in ascending order of associated COUNT values ​​after performing header decompression (if not already performed). NOTE: When considering consecutive COUNT values, COUNT values ​​of discarded SDUs are also included;

[0232] - Update RX_DELIV to the COUNT value of the first PDCP SDU that is not delivered to higher layers and not discarded, where COUNT >= RX_REORD.

[0233] This solves the problem of sequence number gaps, reduces reordering delays at the receiving end, and improves service performance.

[0234] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0235] It is worth noting that FIG3 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG3 above.

[0236] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0237] According to the above embodiment, by enhancing the transmitting end and the receiving end, the problem of sequence number gaps caused by data discard is solved, the reordering delay is reduced, and the transmission performance of the XRM service is improved; by receiving the indication of the first signaling, the problem of data discard of the PDU Set in the wireless access network is solved, thereby increasing the user experience of XR and media services; in addition, by receiving the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it is also possible to ensure differentiated PDU Set processing and meet the integrated data processing requirements of the PDU Set, thereby better supporting data transmission for the PDU Set.

[0238] Embodiments of the third aspect

[0239] An embodiment of the present application provides an information sending device, which is applied to a transmitting-end Packet Data Convergence Protocol (PDCP) entity, which is configured in a terminal device or a network device.

[0240] FIG6 is a schematic diagram of an information transmission device according to an embodiment of the present application. The device may be, for example, a terminal device or a network device, or may be one or more components or assemblies configured in the terminal device or network device. Since the principle of solving the problem of the device is the same as that of the method shown in FIG1 of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method shown in FIG1 of the embodiment of the first aspect, and the same content will not be repeated here.

[0241] As shown in FIG6 , the information sending device 600 includes:

[0242] The sending unit 601 sends a first signaling to a receiving end when it is considered that a PDCP sequence number (SN) gap occurs, wherein the first signaling includes PDCP sequence number (SN) information of the discarded PDCP SDU.

[0243] According to the above embodiment, the Packet Data Convergence Protocol (PDCP) entity at the transmitting end sends a first signaling to the receiving end when it believes that a PDCP sequence number (SN) gap has occurred, wherein the first signaling includes the PDCP sequence number (SN) information of the discarded PDCP SDU. Thus, by enhancing the transmitting end and the receiving end, the problem of sequence number gaps caused by data discard is solved, the reordering delay is reduced, and the transmission performance of the XRM service is improved; through the indication of the first signaling, the problem of data discard of the PDU Set in the wireless access network is solved, thereby increasing the user experience of XR and media services; in addition, by indicating the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it is also possible to ensure the processing of differentiated PDU Sets and meet the integrated data processing requirements of the PDU Set, thereby better supporting data transmission for the PDU Set.

[0244] In some embodiments, the sending unit 601 believes that a PDCP sequence number (SN) gap occurs, including at least one of the following: the sending end packet data convergence protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs; the sending end packet data convergence protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and the first timer is not running; the sending end packet data convergence protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and the number of discarded PDCP SDUs is greater than a first threshold; the sending end packet data convergence protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and the PDCP sequence number (SN) gap is due to a PDU group (PDU Set) discard; or, the sending end packet data convergence protocol (PDCP) entity believes that a PDCP sequence number (SN) gap occurs, and the PDCP sequence number (SN) gap is due to a PDU group importance (PDU Set Importance)-based discard.

[0245] In some embodiments, the transmitting-end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs, including: after the transmitting-end Packet Data Convergence Protocol (PDCP) entity last sent the first signaling, the PDCP sequence number (SN) associated with at least one buffered PDCP SDU is higher than the PDCP sequence number (SN) of the discarded PDCP SDU and the discarded PDCP SDU has not yet been sent.

[0246] In some embodiments, when the first timer is running, the sending unit 601 does not send the first signaling; and when the first timer expires and the sending end Packet Data Convergence Protocol (PDCP) entity believes that a PDCP sequence number (SN) gap has occurred, the sending unit 601 sends the first signaling.

[0247] In some embodiments, in the terminal device, the first timer is configured through a second field, wherein the second field is configured through Radio Resource Control (RRC) signaling.

[0248] In some embodiments, when the terminal device is configured with a first field, the sending unit 601 sends the first signaling to the receiving end when it is believed that a PDCP sequence number (SN) gap occurs; wherein the first field is configured through radio resource control (RRC) signaling.

[0249] In some embodiments, when the first field is configured, the sending unit 601 is triggered to send the first signaling when the PDCP sequence number (SN) associated with at least one cached PDCP SDU is higher than the PDCP sequence number (SN) of the discarded PDCP SDU and the discarded PDCP SDU has not been sent, and the PDCP entity is configured with PDU group discard (pdu-SetDiscard) and the discarded PDCP SDU belongs to a PDU group (PDU Set); or, when the first field is configured, the sending unit 601 is triggered to send the first signaling when the PDCP sequence number (SN) associated with at least one cached PDCP SDU is higher than the PDCP sequence number (SN) of the PDCP SDU discarded due to the expiration of the second timer (discardTimerForLowImportance) and the discarded PDCP SDU has not been sent.

[0250] In some embodiments, the first signaling includes a third field and a fourth field, wherein the third field indicates a count (COUNT) value of the first SDU in the discarded PDCP SDU; wherein the fourth field is an M-bit bitmap, where M is greater than or equal to 0.

[0251] In some embodiments, for the i-th bit in the fourth field, where i is greater than or equal to 1 and less than or equal to M, when the bit value of the i-th bit is a first value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is not discarded; when the bit value of the i-th bit is a second value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is discarded.

[0252] In some embodiments, the information sending apparatus 600 further includes: a generating unit (not shown), which generates the first signaling as follows:

[0253] The third field is set to a count (COUNT) value of the first PDCP SDU discarded and not transmitted after the last first signaling is sent;

[0254] In case of a second PDCP SDU that is discarded and not transmitted, wherein the COUNT value of the second PDCP SDU that is discarded and not transmitted is greater than the COUNT value of the first PDCP SDU that is discarded and not transmitted indicated by the third field:

[0255] generating the fourth field, wherein the bit length of the fourth field is the number of sequence numbers between the PDCP SDU following the first PDCP SDU that is discarded and not transmitted and the last PDCP SDU that is discarded and not transmitted, wherein the fourth field is rounded up to a multiple of 8; or the bit length of the fourth field is the number of sequence numbers between the PDCP SDU following the first PDCP SDU that is discarded and not transmitted and a specific PDCP SDU, wherein the specific PDCP SDU is the first PDCP SDU that makes the size of the generated PDCP control PDU equal to 9000 bytes, whichever is smaller.

[0256] The bits in the bitmap corresponding to all discarded and untransmitted PDCP SDUs in the fourth field are set to "1", otherwise set to "0";

[0257] The first signaling is delivered to the lower layer through the transmitting-end Packet Data Convergence Protocol (PDCP) entity as the first PDCP PDU to be sent.

[0258] The embodiment of the present application further provides an information receiving device, which is applied to a receiving-end Packet Data Convergence Protocol (PDCP) entity, which is configured in a terminal device or a network device.

[0259] FIG7 is a schematic diagram of an information receiving device according to an embodiment of the present application. The device may be, for example, a terminal device or a network device, or may be one or more components or assemblies configured in the terminal device or the network device. Since the principle of solving the problem of the device is the same as that of the method shown in FIG3 of the embodiment of the second aspect, its specific implementation can refer to the implementation of the method shown in FIG3 of the embodiment of the second aspect, and the same content will not be repeated here.

[0260] As shown in FIG7 , the information receiving device 700 includes:

[0261] A receiving unit 701 receives a first signaling and a PDCP data PDU sent by a Packet Data Convergence Protocol (PDCP) entity at a transmitting end;

[0262] a processing unit 702, which adjusts the first state variable and / or the second state variable and / or the third state variable and / or the reordering window of the receiving end according to the PDCP sequence number (SN) information of the discarded PDCP SDU indicated in the first signaling; and

[0263] The transmission unit 703 transmits the buffered PDCP SDU to a higher layer.

[0264] According to the embodiments of the present application, by enhancing the transmitting and receiving ends, the problem of sequence number gaps caused by data discard is solved, the reordering delay is reduced, and the transmission performance of the XRM service is improved; by receiving the indication of the first signaling, the problem of data discard of the PDU Set in the wireless access network is solved, thereby increasing the user experience of XR and media services; in addition, by receiving the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it is also possible to ensure differentiated PDU Set processing and meet the integrated data processing requirements of the PDU Set, thereby better supporting data transmission for the PDU Set.

[0265] In the above embodiment, the relevant content of the first signaling has been explained in the previous embodiment and will not be repeated here.

[0266] In some embodiments, the first signaling includes a third field and a fourth field, wherein the third field indicates a count (COUNT) value of the first SDU in the discarded PDCP SDU; wherein the fourth field is an M-bit bitmap, where M is greater than or equal to 0.

[0267] In some embodiments, for the i-th bit in the fourth field, where i is greater than or equal to 1 and less than or equal to M,

[0268] When the bit value of the i-th bit is a first value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is not discarded; when the bit value of the i-th bit is a second value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is discarded.

[0269] In some embodiments, the processing unit 702 considers that the PDCP SDU associated with each bit value of the fourth field being the second value and / or the COUNT value of the first PDCP SDU indicated by the third field has been discarded.

[0270] In some embodiments, the processing unit 702 performs the following operations based on the count value of the discarded PDCP SDU:

[0271] When the maximum value of the count (COUNT) values ​​of all discarded PDCP SDUs is greater than or equal to the first state variable (RX_NEXT): the first state variable (RX_NEXT) is updated to the maximum count (COUNT) value+1.

[0272] In some embodiments, the processing unit 702 further performs the following operations:

[0273] In the case where the second state variable (RX_DELIV) = the count (COUNT) value of any discarded PDCP SDU exists:

[0274] delivering all stored PDCP SDUs with consecutive count (COUNT) values ​​equal to the second state variable (RX_DELIV) to a higher layer in ascending order of associated count (COUNT) values ​​after performing header decompression, wherein the consecutive count (COUNT) values ​​include the count (COUNT) value of the discarded PDCP SDU; and

[0275] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to the upper layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

[0276] In some embodiments, when the PDCP data PDU received by the receiving-end PDCP entity is not discarded, the processing unit 702 performs the following operations:

[0277] When the second state variable (RX_DELIV) = the count (COUNT) value of the received PDCP data PDUs:

[0278] starting from a COUNT value equal to the second state variable (RX_DELIV), delivering all stored PDCP SDUs with consecutive COUNT values ​​after performing header decompression to a higher layer in ascending order of associated COUNT values, wherein the consecutive COUNT values ​​include the COUNT value of the discarded SDU; and

[0279] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to the upper layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

[0280] In some embodiments, when the third timer (t-Reordering) times out, the processing unit 792 performs the following operations:

[0281] For all stored PDCP SDUs whose COUNT values ​​are less than the third state variable (RX_REORD), and all stored PDCP SDUs with consecutive COUNT values ​​starting from the COUNT value corresponding to the third state variable (RX_REORD), after performing header decompression, the consecutive COUNT values ​​are delivered to a higher layer in ascending order of the associated COUNT values, wherein the consecutive COUNT values ​​include the COUNT value of the discarded SDU; and

[0282] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than or equal to the third state variable (RX_REORD).

[0283] In some embodiments, the first state variable (RX_NEXT) indicates a count (COUNT) value of a next PDCP SDU expected to be received; the second state variable (RX_DELIV) indicates a count (COUNT) value of a first PDCP SDU that has not been delivered to a higher layer but is still waiting to be received; and the third state variable (RX_REORD) indicates a next count (COUNT) value of a count (COUNT) value associated with a PDCP data PDU that triggers a third timer (t-Reordering).

[0284] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The apparatuses 600 and 700 of the embodiments of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0285] In addition, for the sake of simplicity, Figures 6 and 7 only illustrate the connection relationships or signal paths between various components or modules. However, those skilled in the art should be aware that various related technologies such as bus connections can be used. The above-mentioned components or modules can be implemented using hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0286] According to the device of the embodiment of the present application, the problem of discarding PDU Set data in the wireless access network is solved through the indication of the first signaling, thereby improving the user experience of XR and media services; in addition, by indicating the PDCP sequence number (SN) information of the specific discarded PDCP SDU, it is also possible to ensure differentiated PDU Set processing and meet the integrated data processing requirements of PDU Set, thereby better supporting data transmission for PDU Set.

[0287] Embodiments of the fourth aspect

[0288] An embodiment of the present application provides a communication system, including a terminal device and a network device. The terminal device is configured to execute the method shown in FIG1 of the embodiment of the first aspect or the method shown in FIG3 of the embodiment of the second aspect. Accordingly, the network device is configured to execute the method shown in FIG3 of the embodiment of the second aspect or the method shown in FIG1 of the embodiment of the first aspect. The behavior of the terminal device and the network device has been described in detail in the embodiments of the first and second aspects, and the content thereof is incorporated herein and will not be repeated here.

[0289] An embodiment of the present application also provides a terminal device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method described in Figure 1 of the embodiment of the first aspect or the method described in Figure 3 of the embodiment of the second aspect.

[0290] Figure 8 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 8 , terminal device 800 may include a processor 810 and a memory 820. Memory 820 stores data and programs and is coupled to processor 810. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0291] For example, the processor 810 may be configured to execute a program to implement the method described in FIG. 1 in the embodiment of the first aspect or the method described in FIG. 3 in the embodiment of the second aspect.

[0292] As shown in Figure 8 , the terminal device 800 may further include: a communication module 830, an input unit 840, a display 850, and a power supply 860. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 800 does not necessarily include all of the components shown in Figure 8 , and these components are not essential. Furthermore, the terminal device 800 may also include components not shown in Figure 8 , for which reference may be made to the prior art.

[0293] An embodiment of the present application also provides a network device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method described in Figure 1 of the embodiment of the first aspect or the method described in Figure 3 of the embodiment of the second aspect.

[0294] Figure 9 is a schematic diagram of a network device according to an embodiment of the present application. As shown in Figure 9, network device 900 may include a central processing unit (CPU) 910 and a memory 920; the memory 920 is coupled to the CPU 910. The memory 920 may store various data and information processing programs, which are executed under the control of the CPU 910 to receive various information sent by terminal devices and send various information to the terminal devices.

[0295] For example, the processor 910 may be configured to execute a program to implement the method described in FIG. 1 in the embodiment of the first aspect or the method described in FIG. 3 in the embodiment of the second aspect.

[0296] In addition, as shown in Figure 9, network device 900 may also include: a transceiver 930 and an antenna 940; wherein, the functions of these components are similar to those in the prior art and are not described here in detail. It is worth noting that network device 900 does not necessarily include all the components shown in Figure 9; in addition, network device 900 may also include components not shown in Figure 9, and reference may be made to the prior art for details.

[0297] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program enables the computer to execute the method described in Figure 1 of the embodiment of the first aspect or the method described in Figure 3 of the embodiment of the second aspect in the terminal device.

[0298] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in FIG. 1 of the embodiment of the first aspect or the method described in FIG. 3 of the embodiment of the second aspect in a terminal device.

[0299] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a network device, the program enables a computer to execute the method described in FIG1 of the embodiment of the first aspect or the method described in FIG3 of the embodiment of the second aspect in the network device.

[0300] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in FIG. 1 of the embodiment of the first aspect or the method described in FIG. 3 of the embodiment of the second aspect in a network device.

[0301] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0302] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0303] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0304] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0305] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0306] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0307] 1. A method for sending information, applied to a terminal device or a network device, wherein the method comprises:

[0308] A Packet Data Convergence Protocol (PDCP) entity at the transmitting end sends a first signaling to the receiving end when it is believed that a PDCP sequence number (SN) gap occurs, wherein the first signaling includes PDCP sequence number (SN) information of the discarded PDCP SDU.

[0309] 2. A method for receiving information, applied to a network device or a terminal device, wherein the method comprises:

[0310] A receiving-end PDCP entity receives a first signaling and a PDCP data PDU sent by a transmitting-end Packet Data Convergence Protocol (PDCP) entity;

[0311] The receiving-end PDCP entity adjusts a first state variable and / or a second state variable and / or a third state variable and / or a reordering window at the receiving end according to the PDCP sequence number (SN) information of the discarded PDCP SDU indicated in the first signaling; and

[0312] The receiving-end PDCP entity delivers the buffered PDCP SDU to a higher layer.

[0313] 3. The method according to Note 2, wherein the first signaling includes a third field and a fourth field, wherein the third field indicates the count (COUNT) value of the first SDU in the discarded PDCP SDU; wherein the fourth field is an M-bit bitmap, wherein M is greater than or equal to 0.

[0314] 4. The method according to Note 3, for the i-th bit in the fourth field, where i is greater than or equal to 1 and less than or equal to M,

[0315] When the bit value of the i-th bit is a first value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is not discarded; when the bit value of the i-th bit is a second value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is discarded.

[0316] 5. The method according to Supplement 4, wherein the method further comprises:

[0317] The receiving-end PDCP entity considers that a PDCP SDU having each bit value of the second value in the fourth field and / or a PDCP SDU associated with a count (COUNT) value of the first PDCP SDU indicated by the third field has been discarded.

[0318] 6. The method according to Note 5, wherein the method further comprises: the receiving PDCP entity performing the following loop operation based on the ascending order of the count value of the discarded PDCP SDUs:

[0319] In the case where the count (COUNT) value is greater than or equal to the first state variable (RX_NEXT):

[0320] Update the first state variable (RX_NEXT) to the count (COUNT) value + 1;

[0321] In the case where there is a second state variable (RX_DELIV) = the count (COUNT) value:

[0322] starting from the count value in the second state variable (RX_DELIV)=the count value, delivering all stored PDCP SDUs with consecutive count values ​​to a higher layer in ascending order of associated count values ​​after performing header decompression; and

[0323] Updating the second state variable (RX_DELIV) to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV);

[0324] When the third timer (t-Reordering) is running and the second state variable (RX_DELIV) is greater than or equal to the third state variable (RX_REORD): stopping and resetting the third timer (t-Reordering);

[0325] When the third timer (t-Reordering) is not running and the second state variable (RX_DELIV) is less than the third state variable (RX_REORD): the third state variable (RX_REORD) is updated to the first state variable (RX_NEXT); and the third timer (t-Reordering) is started.

[0326] 7. The method according to Note 5, wherein the method further comprises, when the PDCP data PDU received by the receiving PDCP entity is not discarded, the receiving PDCP entity performing the following operations:

[0327] In the case that out-of-order delivery (outOfOrderDelivery) is not configured, the following loop operation is performed in ascending order for the count (COUNT) value of the PDCP SDUs considered to be discarded in the first signaling received last time:

[0328] In the case where there is a second state variable (RX_DELIV) = the count (COUNT) value:

[0329] starting from the count value in the second state variable (RX_DELIV) = the count value, delivering all stored PDCP SDUs with consecutive count values ​​to a higher layer in ascending order of associated count values ​​after performing header decompression;

[0330] The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

[0331] 8. The method according to Note 7, wherein a third timer (t-Reordering) is running.

[0332] 9. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the information sending method as described in Note 1.

[0333] 10. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the information receiving method as described in any one of Notes 2 to 8.

Claims

1. An information sending device, applied to a transmitting-end Packet Data Convergence Protocol (PDCP) entity, wherein the transmitting-end Packet Data Convergence Protocol (PDCP) entity is configured in a terminal device or a network device, wherein: The device comprises: The sending unit sends a first signaling to a receiving end when it is considered that a PDCP sequence number (SN) gap occurs, wherein the first signaling includes PDCP sequence number (SN) information of the discarded PDCP SDU.

2. The device according to claim 1, wherein The sending unit considers that a PDCP sequence number (SN) gap occurs, including at least one of the following: The transmitting end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs; The transmitting end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs and the first timer is not running; The transmitting-end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs, and the number of the discarded PDCP SDUs is greater than a first threshold; The transmitting end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs, and the PDCP sequence number (SN) gap is caused by a PDU set (PDU Set) discard; or, The transmitting end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs, and the PDCP sequence number (SN) gap is caused by discarding based on PDU set importance.

3. The device according to claim 2, wherein The transmitting-end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs, including: After the transmitting end Packet Data Convergence Protocol (PDCP) entity last sent the first signaling, a PDCP sequence number (SN) associated with at least one buffered PDCP SDU is higher than the PDCP sequence number (SN) of the discarded PDCP SDU and the discarded PDCP SDU has not yet been sent.

4. The device according to claim 2, wherein When the first timer is running, the sending unit does not send the first signaling; and When the first timer times out and the transmitting-end Packet Data Convergence Protocol (PDCP) entity considers that a PDCP sequence number (SN) gap occurs, the sending unit sends the first signaling.

5. The device according to claim 4, wherein In the terminal device, the first timer is configured through a second field, wherein the second field is configured through Radio Resource Control (RRC) signaling.

6. The device according to claim 2, wherein When the terminal device is configured with a first field, the sending unit sends the first signaling to the receiving end when it is believed that a PDCP sequence number (SN) gap occurs; wherein the first field is configured through radio resource control (RRC) signaling.

7. The device according to claim 6, wherein When the first field is configured, the sending unit is triggered to send the first signaling when the PDCP sequence number (SN) associated with at least one cached PDCP SDU is higher than the PDCP sequence number (SN) of the discarded PDCP SDU and the discarded PDCP SDU has not been sent, and the PDCP entity is configured with PDU group discard (pdu-SetDiscard) and the discarded PDCP SDU belongs to a PDU group (PDU Set); or, when the first field is configured, the sending unit is triggered to send the first signaling when the PDCP sequence number (SN) associated with at least one cached PDCP SDU is higher than the PDCP sequence number (SN) of the PDCP SDU discarded due to the expiration of the second timer (discardTimerForLowImportance) and the discarded PDCP SDU has not been sent.

8. The device according to claim 1, wherein The first signaling is a PDCP control PDU, including a third field and a fourth field, wherein the third field indicates the count (COUNT) value of the first SDU in the discarded PDCP SDU; wherein the fourth field is an M-bit bitmap, where M is greater than or equal to 0.

9. The device according to claim 8, wherein For the i-th bit in the fourth field, where i is greater than or equal to 1 and less than or equal to M, When the bit value of the i-th bit is a first value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is not discarded; when the bit value of the i-th bit is a second value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is discarded.

10. The device according to claim 9, wherein The apparatus further includes: a generating unit, which generates the first signaling as follows: Setting the third field to a count value of the first PDCP SDU discarded and not transmitted after the first signaling was last sent; In a case where there is a second PDCP SDU that is discarded and not transmitted, wherein the count (COUNT) value of the second PDCP SDU that is discarded and not transmitted is greater than the count (COUNT) value of the first PDCP SDU that is discarded and not transmitted indicated by the third field: generating the fourth field, wherein the bit length of the fourth field is the number of sequence numbers between a PDCP SDU following the first PDCP SDU that is discarded and not transmitted and a last PDCP SDU that is discarded and not transmitted, wherein the fourth field is rounded backward to a multiple of 8; or the bit length of the fourth field is the number of sequence numbers between a PDCP SDU following the first PDCP SDU that is discarded and not transmitted and a specific PDCP SDU, wherein the specific PDCP SDU is the first PDCP SDU that makes the size of the generated PDCP control PDU equal to 9000 bytes, taking the smaller value of the two numbers; Setting the bits in the bitmap corresponding to all discarded and untransmitted PDCP SDUs in the fourth field to "1"; otherwise, setting the bits to "0"; The first signaling is delivered to a lower layer as the first PDCP PDU to be sent through the transmitting-end Packet Data Convergence Protocol (PDCP) entity.

11. An information receiving device, applied to a receiving-end Packet Data Convergence Protocol (PDCP) entity, wherein the receiving-end Packet Data Convergence Protocol (PDCP) entity is configured in a network device or a terminal device, wherein: The device comprises: a receiving unit configured to receive a first signaling and a PDCP data PDU sent by a Packet Data Convergence Protocol (PDCP) entity at a transmitting end; a processing unit, which adjusts a first state variable and / or a second state variable and / or a third state variable and / or a reordering window at a receiving end according to PDCP sequence number (SN) information of the discarded PDCP SDU indicated in the first signaling; and A transmission unit that delivers the buffered PDCP SDUs to higher layers.

12. The device according to claim 11, wherein The first signaling includes a third field and a fourth field, wherein the third field indicates a count (COUNT) value of the first SDU in the discarded PDCP SDU; wherein the fourth field is an M-bit bitmap, where M is greater than or equal to 0.

13. The device according to claim 12, wherein For the i-th bit in the fourth field, where i is greater than or equal to 1 and less than or equal to N, When the bit value of the i-th bit is a first value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is not discarded; when the bit value of the i-th bit is a second value, it indicates that the PDCP SDU with a count (COUNT) value of [(the count (COUNT) value of the first discarded SDU + i) modulo 2^32] is discarded.

14. The device according to claim 13, wherein The processing unit considers that a PDCP SDU associated with each bit value of the fourth field having the second value and / or a PDCP SDU having a count (COUNT) value of the first PDCP SDU indicated by the third field has been discarded.

15. The device according to claim 14, wherein The processing unit performs the following operations based on the count value of the discarded PDCP SDU: When the maximum value of the count (COUNT) values ​​of all the discarded PDCP SDUs is greater than or equal to the first state variable (RX_NEXT): updating the first state variable (RX_NEXT) to the maximum count (COUNT) value+1.

16. The device according to claim 15, wherein The processing unit further performs the following operations: In the case where there is a second state variable (RX_DELIV) = a count (COUNT) value of any one of the discarded PDCP SDUs: delivering all stored PDCP SDUs with consecutive count values ​​equal to the second state variable (RX_DELIV) to a higher layer in ascending order of associated count values ​​after performing header decompression, wherein the consecutive count values ​​include the count value of the discarded PDCP SDU; and The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

17. The device according to claim 14, wherein In a case where the PDCP data PDU received by the receiving-end PDCP entity is not discarded, the processing unit performs the following operations: In the case where the second state variable (RX_DELIV) = the count (COUNT) value of the received PDCP data PDUs: Starting from the count value equal to the second state variable (RX_DELIV), all stored delivering the stored PDCP SDUs with a continuity count (COUNT) value to a higher layer in ascending order of the associated count (COUNT) value after performing header decompression, wherein the continuity count (COUNT) value includes the count (COUNT) value of the discarded SDU; and The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than the second state variable (RX_DELIV).

18. The device according to claim 14, wherein When the third timer (t-Reordering) times out, the processing unit performs the following operations: For all stored PDCP SDUs whose COUNT values ​​are less than the third state variable (RX_REORD), and all stored PDCP SDUs with consecutive COUNT values ​​starting from the COUNT value corresponding to the third state variable (RX_REORD), after performing header decompression, deliver them to higher layers in ascending order of the associated COUNT values, wherein the consecutive COUNT values ​​include the COUNT value of the discarded SDU; and The second state variable (RX_DELIV) is updated to a count (COUNT) value of the first PDCP SDU that is not delivered to a higher layer and is not discarded, wherein the count (COUNT) value is greater than or equal to the third state variable (RX_REORD).

19. The device according to claim 15, wherein The first state variable (RX_NEXT) indicates a count (COUNT) value of a next PDCP SDU expected to be received; The second state variable (RX_DELIV) indicates a count (COUNT) value of the first PDCP SDU that has not been delivered to the upper layer but is still waiting to be received; The third state variable (RX_REORD) indicates a next count (COUNT) value of a count (COUNT) value associated with the PDCP data PDU that triggers the third timer (t-Reordering).

20. A terminal device, wherein: The terminal device includes the information sending device according to any one of claims 1 to 10; and / or the terminal device includes the information receiving device according to any one of claims 11 to 19.

Images