User plane data arrival notification method and related device

By configuring downlink SDT bearers in the base station control plane and user plane separation architecture in 5G wireless communication and providing auxiliary information, the problem of downlink small packet distinction is solved, and the interoperability problem between the base station control plane and user plane is reduced. Supports the sending of small packets.

WO2024239487A1PCT designated stage expired Publication Date: 2024-11-28CHINA TELECOM CORP LTD BEIJING RESEARCH INSTITUTE +1
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/117038
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2023-09-05
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

The existing 3GPP Rel-17 protocol cannot effectively distinguish and process downlink small data packets in the separate architecture, resulting in user plane entities being unable to distinguish Rel-17 uplink SDT and Rel-18 downlink SDT, resulting in the base station control plane and user plane. Interoperability issues.

Method used

By configuring downlink SDT-based bearers in the base station control plane and user plane separation architecture, and providing auxiliary information to the control plane entity when the downlink data packet arrives, including sending and receiving related messages and signaling, to distinguish Rel-17 uplink SDTs when the downlink data packet arrives, the Rel-17 uplink SDTs are distinguished and Rel-18 downlink SDT.

Benefits of technology

The user plane entity can correctly distinguish Rel-17 uplink SDT and Rel-18 downlink SDT, reducing the interoperability problem between the base station control plane and the user plane, and supporting the sending of small data packets in the control plane and user plane separation architecture. process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023117038_28112024_PF_FP_ABST
    Figure CN2023117038_28112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of wireless communications. Provided are a user plane data arrival notification method and a related device. The method comprises: sending a first intra-base-station request message to a base station user plane entity, the first intra-base-station request message comprising indication information for configuring at least one DRB as an SDT bearer and whether downlink SDT is supported; receiving a first intra-base-station response message, and confirming the establishment situation of the bearer requested to be configured; receiving a second intra-base-station message from the base station user plane entity, the second intra-base-station message being used for notifying a base station control plane entity of reception of terminal downlink data, and the second intra-base-station message comprising the downlink data volume of all SDT bearers of a terminal cached in the base station user plane entity; and sending to a base station separation entity a first paging message comprising an RRC paging message sent to the terminal and first auxiliary information.
Need to check novelty before this filing date? Find Prior Art

Description

User plane data arrival notification method and related equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the application with CN application number 202310574049.7 and application date May 19, 2023, and claims its priority. The disclosed content of the CN application is hereby introduced as a whole into this application. Technical Field

[0003] The present disclosure relates to the technical field of wireless communications, and in particular to a method for notifying arrival of user plane data and related equipment. Background Art

[0004] 5G (5th Generation Mobile Communication Technology) is the main technology of the next generation of wireless networks and has technical features such as support for ultra-wideband and large connections. Compared with 4G (4th Generation Mobile Communication Technology), 5G introduces an inactive state (RRC_INACTIVE). In this state, the base station / UE can choose to remain inactive without completely releasing the bearer established by RRC (Radio Resource Control) when there is no business data transmission. The SuspendConfig can be carried in the RRC Release message. The introduction of this state is used to solve the sending of small data packets and reduce the signaling overhead of the core network.

[0005] 3GPP Rel-17 introduced SDT (Small Data Transmission) for the uplink direction and defined related processes. However, unlike the uplink SDT in Release 17, Release 18 mainly focuses on the related processes triggered by SDT services in the downlink direction, that is, the process of sending small data packets in the idle state after receiving a data packet from the core network. If downlink SDT is supported according to the current SDT process of Release 17, there will be a problem that the user plane entity (CU-UP) cannot distinguish between Rel-17 uplink SDT and Rel-18 downlink SDT. In other words, the current 3GPP Rel-17 protocol cannot meet the design requirements of downlink small data packets in a separated architecture, and enhancements are needed to meet the needs of network deployment and optimization.

[0006] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to ordinary technicians in the field.

[0007] Summary of the Invention

[0008] According to a first aspect of the present disclosure, a method for notifying arrival of user plane data is provided, which is applied to a base station control plane entity of a split architecture base station, the method comprising:

[0009] Sending a first intra-base station request message to a base station user plane entity, where the first intra-base station request message includes configuring at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported;

[0010] Receiving a response message from the first base station, confirming establishment of the requested bearer configuration;

[0011] receiving a second intra-base-station message from a base station user plane entity, where the second intra-base-station message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second intra-base-station message includes an amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity;

[0012] A first paging message including first auxiliary information is sent to the base station separation entity, the first paging message also includes an RRC paging message sent to the terminal, the first auxiliary information at least includes downlink SDT indication information, and the RRC paging message at least includes downlink SDT indication information.

[0013] According to a second aspect of the present disclosure, a method for notifying arrival of user plane data is provided, which is applied to a base station control plane entity of a split architecture base station, the method comprising:

[0014] Sending a first intra-base station request message to a base station user plane entity, where the first intra-base station request message includes configuring at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported;

[0015] Receiving a response message from the first base station, confirming establishment of the requested bearer configuration;

[0016] receiving a second intra-base-station message from a base station user plane entity, where the second intra-base-station message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second intra-base-station message includes an amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity;

[0017] Sending a first paging message including first auxiliary information to the base station separation entity, where the first auxiliary information at least includes downlink SDT indication information;

[0018] If a new second base station message is received from the base station user plane entity, the transmission process of the downlink small data packet is terminated. The new second base station message is used to notify the base station control plane entity that the downlink small data packet carried by the terminal non-SDT is received. The new second base station message does not carry the cached SDT-carried downlink data packet size.

[0019] In some embodiments of the present disclosure, the request message within the first base station includes an SDT bearer list, and the SDT bearer list is used to instruct the base station user plane entity to reconfigure or create one or more DRBs as SDT bearers for the terminal.

[0020] In some embodiments of the present disclosure, the indication information of whether downlink SDT is supported is indicated by whether the SDT bearer request mode is carried to indicate whether downlink is supported at the same time; the SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode is not carried, it indicates that all SDT DRBs are configured as uplink SDT only.

[0021] In some embodiments of the present disclosure, the method further includes:

[0022] Sending a second paging message including second auxiliary information to a neighboring base station;

[0023] The second paging message includes an RRC paging message sent to the terminal; and the second auxiliary information further includes at least one of the following information:

[0024] The amount of buffered downlink data and downlink SDT indication information of all SDT bearers buffered in the user plane entity of the base station.

[0025] In some embodiments of the present disclosure, when a second intra-base station message is received from a base station user plane entity, the method further includes:

[0026] Determine whether the amount of downlink data carried by the SDT cached in the user plane entity of the base station is less than the downlink small data packet sending trigger threshold;

[0027] When the amount of the downlink small data packet is less than the trigger threshold for sending the downlink small data packet, a first paging message is sent to the base station separation entity and a second paging message is sent to a neighboring base station.

[0028] In some embodiments of the present disclosure, the base station control plane entity sends a second paging message to the neighboring base station through the Xn interface, and the RRC paging message included in the second paging message includes at least downlink SDT indication information.

[0029] In some embodiments of the present disclosure, if a high-layer signaling message is received from the core network and a second base station message from the base station user plane entity is not received at the same time, a first paging message is directly sent to the base station separation entity and / or a second paging message is sent to a neighboring base station; the second paging message directly sent to the neighboring base station does not carry the size of the cached downlink data of all SDT bearers cached in the base station user plane entity.

[0030] According to a third aspect of the present disclosure, a method for notifying arrival of user plane data is provided, which is applied to a base station user plane entity of a split architecture base station, the method comprising:

[0031] Receive a first intra-base station request message sent by a base station control plane entity, where the first intra-base station request message includes configuration or modification of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported;

[0032] Responding to the request message within the first base station, confirming the establishment of the requested bearer configuration;

[0033] After the downlink data of the SDT bearer of the terminal arrives, a second base station internal message is sent to the base station control plane entity, where the second base station internal message includes at least the amount of cached downlink data of all SDT bearers cached in the base station user plane entity.

[0034] According to a fourth aspect of the present disclosure, a method for notifying arrival of user plane data is provided, which is applied to a base station user plane entity of a separated architecture base station, the method comprising:

[0035] Receive a first intra-base station request message sent by a base station control plane entity, where the first intra-base station request message includes configuration or modification of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported;

[0036] Responding to the request message within the first base station, confirming the establishment of the requested bearer configuration;

[0037] After the downlink data of the SDT bearer of the terminal arrives, send a second intra-base station message to the base station control plane entity, where the second intra-base station message includes at least the amount of cached downlink data of all SDT bearers cached in the base station user plane entity;

[0038] If a small downlink data packet not carried by the SDT of the terminal is received, a new second intra-base-station message is sent to the base station control plane entity, where the new second intra-base-station message does not carry the size of the cached downlink data packet carried by the SDT.

[0039] In some embodiments of the present disclosure, the indication information of whether downlink SDT is supported is indicated by whether the SDT bearer request mode is carried; the SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode is not carried, it indicates that all SDT DRBs are only configured as uplink SDT.

[0040] In some embodiments of the present disclosure, in response to the request message within the first base station, the establishment of the requested configuration bearer is confirmed, including: configuring the relevant DRB as an SDT DRB according to the indication; when the SDT bearer request mode is carried, counting the data volume of the downlink SDT bearer, and sending it to the base station control plane entity through a message within the second base station, otherwise the data volume of the downlink SDT bearer is not counted; and sending the response message to the base station control plane entity.

[0041] In some embodiments of the present disclosure, when the SDT bearer downlink data of the terminal arrives, a second base station message is sent to the base station control plane entity, including: receiving a downlink small data packet of the terminal from the core network, caching it after adding an SDAP header; judging whether all the DRBs corresponding to the downlink small data packets belong to the SDT DRBs configured by the base station user plane entity; in the case where all the downlink small data packets belong to the SDT bearer, counting the data volume of the small data packets; judging whether the SDT bearer request mode is configured; sending a second base station message to the base station control plane entity, the second base station message including the downlink data volume of all SDT bearers of the terminal cached in the base station user plane entity.

[0042] In some embodiments of the present disclosure, when all the downlink small data packets belong to the SDT bearer, the method further includes: starting a timer according to the configuration, and the timer is configured by the network management; if only downlink small data packets carried by the SDT of the terminal continue to be received before the timer expires, the downlink small data packets continue to be cached, and the total data size of the downlink small data packets is accumulated; after the timer expires, the second base station internal message is sent to the base station control plane entity.

[0043] In some embodiments of the present disclosure, the statistical data volume of the small data packet is the statistical data packet size after adding the SDAP header.

[0044] In some embodiments of the present disclosure, after sending a second base station message to the base station control plane entity and not receiving a user context modification message sent from the base station control plane entity, the method further includes: if a small downlink data packet carried by the SDT of the terminal is received again, then continuing to send a new second base station message to the base station control plane entity, and the new second base station message includes the downlink data volume of the SDT carried newly cached in the base station user plane entity; if a small downlink data packet not carried by the SDT is received again, then continuing to send a new second base station message to the base station control plane entity, and the new second base station message does not carry the size of the cached downlink data packet carried by the SDT.

[0045] In the absence of conflict, the embodiments and features in the base station control plane entity of the present disclosure can be applied to the base station user plane entity, and vice versa.

[0046] In the absence of conflict, the embodiments of the present disclosure and the features in the embodiments may be arbitrarily combined with each other.

[0047] According to a fifth aspect of the present disclosure, a base station control plane entity of a split architecture base station is provided, including:

[0048] A message sending module, configured to send a first intra-base station request message to a base station user plane entity, where the first intra-base station request message includes configuration of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported;

[0049] A second receiving module is configured to receive a response message from the first base station and confirm the establishment of the requested bearer configuration;

[0050] a notification receiving module, configured to receive a second intra-base station message from a base station user plane entity, where the second intra-base station message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second intra-base station message includes an amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity;

[0051] The paging sending module is used to send a first paging message containing first auxiliary information to the base station separation entity, the first paging message also includes an RRC paging message sent to the terminal, the first auxiliary information at least includes downlink SDT indication information, and the RRC paging message at least includes downlink SDT indication information.

[0052] According to a sixth aspect of the present disclosure, a base station control plane entity of a split architecture base station is provided, including:

[0053] A message sending module, configured to send a first intra-base station request message to a base station user plane entity, where the first intra-base station request message includes configuration of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported;

[0054] A second receiving module is configured to receive a response message from the first base station and confirm the establishment of the requested bearer configuration;

[0055] a notification receiving module, configured to receive a second intra-base station message from a base station user plane entity, where the second intra-base station message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second intra-base station message includes an amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity;

[0056] a paging sending module, configured to send a first paging message including first auxiliary information to the base station separation entity, wherein the first paging message also includes an RRC paging message sent to the terminal, the first auxiliary information includes at least downlink SDT indication information, and the RRC paging message includes at least downlink SDT indication information;

[0057] The transmission termination module is used to terminate the transmission process of the downlink small data packet if a new second base station message is received from the base station user plane entity. The new second base station message is used to notify the base station control plane entity that the downlink small data packet carried by the terminal non-SDT is received. The new second base station message does not carry the cached SDT-carried downlink data packet size.

[0058] According to a seventh aspect of the present disclosure, a base station user plane entity of a split architecture base station is provided, including:

[0059] A message receiving module, configured to receive a first intra-base station request message sent by a base station control plane entity, where the first intra-base station request message includes information indicating whether to configure or modify at least one DRB as an SDT bearer and whether downlink SDT is supported;

[0060] A message response module, configured to respond to the request message within the first base station and confirm the establishment of the requested bearer configuration;

[0061] The notification sending module is used to send a second base station message to the base station control plane entity after the downlink data carried by the terminal's SDT arrives. The second base station message includes at least the amount of cached downlink data of all SDT bearers cached in the base station user plane entity.

[0062] According to an eighth aspect of the present disclosure, a base station user plane entity of a split architecture base station is provided, including:

[0063] A message receiving module, configured to receive a first intra-base station request message sent by a base station control plane entity, where the first intra-base station request message includes information indicating whether to configure or modify at least one DRB as an SDT bearer and whether downlink SDT is supported;

[0064] A message response module, configured to respond to the request message within the first base station and confirm the establishment of the requested bearer configuration;

[0065] A notification sending module is used to send a second base station message to the base station control plane entity after the downlink data carried by the SDT of the terminal arrives, wherein the second base station message includes at least the size of the cached downlink data of all SDT bearers cached in the base station user plane entity; and is used to send a new second base station message to the base station control plane entity if a small downlink data packet not carried by the SDT of the terminal is received, wherein the new second base station message does not carry the size of the downlink data packet carried by the cached SDT.

[0066] According to the ninth aspect of the present disclosure, a separated architecture base station is provided, comprising a base station centralized entity and a base station separated entity; the base station centralized entity comprises a base station control plane entity and a base station user plane entity; the base station control plane entity is used to implement the notification method of the arrival of user plane data as described in the first aspect or the second aspect.

[0067] According to a tenth aspect of the present disclosure, an electronic device is provided, comprising: a memory for storing instructions; and a processor for calling the instructions stored in the memory to implement the above-mentioned method for notifying the arrival of user plane data.

[0068] According to an eleventh aspect of the present disclosure, a computer-readable storage medium is provided, on which computer instructions are stored. When the computer instructions are executed by a processor, the above-mentioned method for notifying the arrival of user plane data is implemented.

[0069] According to a twelfth aspect of the present disclosure, a computer program product is provided. The computer program product stores instructions, and when the instructions are executed by a computer, the computer implements the above-mentioned method for notifying the arrival of user plane data.

[0070] According to a thirteenth aspect of the present disclosure, there is provided a chip comprising at least one processor and an interface;

[0071] An interface for providing program instructions or data to at least one processor;

[0072] At least one processor is configured to execute program instructions to implement the above-mentioned method for notifying the arrival of user plane data.

[0073] The notification method and related equipment for the arrival of user plane data provided in the embodiments of the present disclosure support the configuration of a downlink SDT bearer in an architecture where the base station control plane and user plane are separated, and support the process of providing auxiliary information to the control plane entity when a downlink data packet arrives, thereby enabling the user plane entity (CU-UP) to distinguish between Rel-17 uplink SDT and Rel-18 downlink SDT, and can reduce interoperability issues between the base station control plane and the base station user plane, and support the process of sending small data packets in an architecture where the control plane and user plane are separated.

[0074] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0076] Obviously, the drawings described below are only some embodiments of the present disclosure. A person skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0077] FIG1 shows a schematic diagram of the architecture of a 5G base station with CU / DU separation according to an embodiment of the present disclosure;

[0078] FIG2 is a schematic diagram showing a notification process of user plane data arrival in the related art;

[0079] FIG3 is a schematic diagram showing a process of a control plane notifying a user plane in the related art;

[0080] FIG4 shows a diagram of the uplink SDT signaling process in Release 17;

[0081] FIG5 shows a schematic structural diagram of a base station with a separate architecture according to an embodiment of the present disclosure;

[0082] FIG6 shows a flow chart of a method for notifying arrival of user plane data according to an embodiment of the present disclosure;

[0083] FIG7 shows a flow chart of another method for notifying arrival of user plane data according to an embodiment of the present disclosure;

[0084] FIG8 shows a flow chart of another method for notifying the arrival of user plane data according to an embodiment of the present disclosure;

[0085] FIG9 shows a flow chart of another method for notifying the arrival of user plane data according to an embodiment of the present disclosure;

[0086] FIG10 is a schematic diagram showing a threshold determination process before sending a message within the second base station according to an embodiment of the present disclosure;

[0087] FIG11 shows a schematic diagram of a base station control plane entity of a split architecture base station according to an embodiment of the present disclosure;

[0088] FIG12 shows a schematic diagram of a base station user plane entity of a split architecture base station according to an embodiment of the present disclosure;

[0089] FIG13 shows a structural block diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0090] Example embodiments will be described more fully hereinafter with reference to the accompanying drawings.

[0091] It should be noted that example embodiments may be implemented in many forms and should not be construed as limited to the examples set forth herein.

[0092] Through research, the inventors discovered that, unlike the uplink SDT in Release 17, Release 18 primarily targets downlink SDT services. This involves sending small data packets in the idle state after receiving a data packet from the core network. If downlink SDT is supported using the current Release 17 SDT process, the user plane entity (CU-UP) would be unable to distinguish between Rel-17 uplink SDT and Rel-18 downlink SDT.

[0093] In response to the above problems, the present application discloses a notification method and related equipment for the arrival of user plane data, which can support the configuration of downlink SDT bearer in the base station control plane and user plane separation architecture, and support the process of providing auxiliary information to the control plane entity when the downlink data packet arrives, so that the user plane entity (CU-UP) can distinguish between Rel-17 uplink SDT and Rel-18 downlink SDT, and can reduce the interoperability problems between the base station control plane and the base station user plane, and support the process of sending small data packets in the control plane and user plane separation architecture.

[0094] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by practice of the present disclosure.

[0095] As a next-generation wireless network technology, 5G boasts technical features such as high bandwidth, massive connectivity, low latency, and wireless cloudification. In terms of supporting wireless cloudification, 5G has supported the separation of CU (Centralized Unit) and DU (Distributed Unit), as well as the separation of CP and UP, since Rel-15, as shown in Figure 1.

[0096] The division of CU and DU functions is distinguished by the real-time nature of the content they process. CU devices mainly include non-real-time wireless high-layer protocol stack functions, and also support the downlink of some core network functions and the deployment of edge application services, while DU devices mainly handle physical layer functions and layer 2 functions with real-time requirements. On the basis of CU / DU separation, in order to further adapt to requests from different services, the control plane (CP) and user plane (UP) can be further separated on the CU side of the access network. The separated CP and UP are decoupled from each other, interact through the standard E1 interface, and can be deployed on different physical nodes.

[0097] Due to the separation of the control and user planes, when a user-plane entity receives a data packet from the core, it must notify the control-plane entity via signaling, as shown in Figure 2. Currently, this signaling is only used to notify the arrival of a data packet and does not distinguish between different services. In addition, if any user bearer or context needs to be established or modified, the CU-CP can notify the user plane via signaling, as shown in Figure 3.

[0098] In terms of low latency, compared to 4G, 5G introduces an inactive state, namely the "RRC_INACTIVE" state. In this state, the base station / UE can choose to remain inactive without completely releasing the bearer established by RRC when there is no business data transmission. SuspendConfig can be carried in the RRCRelease message. The introduction of this state is used to solve the problem of sending small data packets and reduce the signaling overhead of the core network. When the UE is in the RRC_INACTIVE state, when the terminal receives a RAN paging or RNA update or has uplink data to send, it will trigger the suspended RRC connection recovery. Before initiating RRC connection recovery, the UE ensures that it has valid and up-to-date system information.

[0099] 3GPP Rel-17 introduced SDT for the uplink and defined related procedures. On the E1 interface, the CU-CP can configure which bearers are SDT bearers for the CU-UP through the Bearer Context Modification message or the Bearer Context Setup message.

[0100] The inventors discovered that, unlike the uplink SDT in Release 17, Release 18 primarily addresses the process triggered by the downlink transmission of small data packets. This involves sending small data packets in the idle state after receiving a data packet from the core network. If downlink SDT is supported according to the current SDT process in Release 17, the following issues arise:

[0101] CU-UP is not aware of the difference between Rel-17 SDT and Rel-18 SDT: Since the bearer itself includes both uplink and downlink parts, it is impossible to distinguish between Rel-17 uplink SDT and Rel-18 downlink SDT at the bearer level. CU-UP will behave differently for Release 17 uplink SDT and Release 18-based downlink SDT. Considering that Rel-18 downlink SDT is compatible with Rel-17 uplink SDT, CU-UP cannot distinguish the two types in the current design process.

[0102] The CU-CP is not aware of the amount of downlink SDT data received by the CU-UP and the calculation method: the current DL Data Notification message of the E1 interface does not contain any SDT indication information, so the CU-CP does not know whether a downlink SDT data packet has arrived or whether it is below the data threshold. In addition, the packet trigger threshold used in the uplink SDT process is derived from the field size of the MAC layer. If the previous method is used at this time, it cannot be accurately calculated considering the subsequent segmentation and retransmission, and the user plane entity of the base station;

[0103] There are interoperability issues between CU-CP and CU-UP when multiple data packets arrive: When multiple downlink data packets arrive at intervals and the first data packet has not yet fully triggered the SDT process, the user plane processing behavior is not clear. It may happen that the downlink data arrival is sent only once, arrives multiple times, or the SDT data indication is cancelled. Therefore, there are interoperability issues.

[0104] Based on the above requirements and reason analysis, the current 3GPP Rel-17 protocol cannot meet the design requirements of downlink small data packets in a separated architecture. New methods are needed to enhance functions to meet the needs of network deployment and optimization.

[0105] Based on the above findings of the inventors, the present disclosure supports the transmission of small data packets caused by the arrival of downlink data in a separated architecture. It provides a notification method and related equipment for the arrival of user plane data, so that the user plane entity (CU-UP) can distinguish between the Rel-17 uplink SDT and the Rel-18 downlink SDT.

[0106] According to some embodiments of the present disclosure, a method for notifying the arrival of user plane data is provided, which is applied to a base station control plane entity of a separated architecture base station, including: sending a first base station request message to the base station user plane entity, the first base station request message including configuration of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported; receiving a first base station response message to confirm the establishment of the requested configuration bearer; receiving a second base station message from the base station user plane entity, the second base station message being used to notify the base station control plane entity of the receipt of downlink data of the terminal, the second base station message including the amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity; sending a first paging message including first auxiliary information to the base station separation entity, the first auxiliary information including at least downlink SDT indication information; if a new second base station message is received from the base station user plane entity, terminating the transmission process of the downlink small data packet, the new second base station message being used to notify the base station control plane entity of the receipt of the downlink small data packet not carried by the terminal on SDT, the new second base station message not carrying the size of the downlink data packet of the cached SDT bearer.

[0107] FIG4 shows a schematic diagram of a split-architecture base station in an embodiment of the present disclosure. As shown in FIG4 , the split-architecture base station provided in the embodiment of the present disclosure includes a base station split entity 410 and a base station centralized entity 420 .

[0108] The base station centralized entity 420 includes a base station control plane entity 421 and a base station user plane entity 422, wherein the base station control plane entity 421 is used to send a first base station request message to the base station user plane entity, the first base station request message including configuring at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported; receiving a first base station response message to confirm the establishment of the requested configuration bearer; receiving a second base station message from the base station user plane entity, the second base station message being used to notify the base station control plane entity of the receipt of terminal downlink data, the second base station message including the amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity; sending a first paging message including an RRC paging message sent to the terminal and first auxiliary information to the base station separation entity, the first auxiliary information including at least downlink SDT indication information, and the RRC paging message including at least downlink SDT indication information.

[0109] In some embodiments, the indication information of whether downlink SDT is supported is expressed by whether it carries an SDT bearer request mode to indicate whether downlink SDT is supported.

[0110] The SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode is not carried, it indicates that all SDT DRBs are configured only as uplink SDT.

[0111] In some embodiments, the base station control plane entity 421 is also used to send a second paging message containing second auxiliary information to a neighboring base station; wherein the second paging message also includes an RRC paging message sent to the terminal; the second auxiliary information includes at least one of the following information: the size of the cached downlink data volume of all SDT bearers cached in the base station user plane entity, and downlink SDT indication information.

[0112] In some embodiments, when the base station control plane entity receives a second base station message from the base station user plane entity, it also determines whether the size of the cached data carried by the downlink SDT in the base station user plane entity is less than the downlink small data packet sending trigger threshold; if it is less than the downlink small data packet sending trigger threshold, it sends a first paging message to the base station separation entity and sends a second paging message to the neighboring base station.

[0113] In some embodiments, when the downlink small data packet sending trigger threshold is less than the first paging message sent by the base station control plane entity to the base station separation entity includes an RRC paging message sent to the terminal, and the RRC paging message sent to the terminal includes at least downlink SDT indication information.

[0114] FIG5 shows a flow chart of a method for notifying the arrival of user plane data in an embodiment of the present disclosure. As shown in FIG5 , the method for notifying the arrival of user plane data provided in an embodiment of the present disclosure includes steps S502 - S506 .

[0115] In S502, the base station control plane entity sends a first intra-base station request message to the base station user plane entity. The first intra-base station request message includes configuration of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported.

[0116] The indication information of whether downlink SDT is supported in the above text is indicated by whether the SDT bearer request mode is carried. The SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode is not carried, it indicates that all SDT DRBs are configured as uplink SDT only.

[0117] In some embodiments, the request message within the first base station includes an SDT bearer list, where the SDT bearer list is used to instruct the base station user plane entity to reconfigure or create one or more DRBs as SDT bearers for the terminal.

[0118] In some embodiments, the base station control plane entity instructs the base station user plane entity to configure the SDT bearer list through a first intra-base station request message, and may configure the SDT bearer mode.

[0119] The SDT bearer list indicates one or more DRBs that support both downlink and uplink small data packet transmission. The SDT bearer mode includes the MT-SDT mode, which can be used to support downlink and / or uplink small data packet transmission.

[0120] After receiving the request message within the first base station, the base station user plane entity determines which DRBs that have been configured and / or need to be newly created support SDT transmission based on the SDT bearer list, and determines that all SDT bearers support downlink small data packet transmission based on the SDT bearer mode. If the SDT bearer mode is not carried, all SDT bearers only support uplink small data packet transmission. After the configuration is completed, the configuration result is fed back to the base station control plane entity.

[0121] In S504, the base station user plane entity sends a second base station internal message to the base station control plane entity. The second base station internal message is used to notify the base station control plane entity that the terminal downlink data has been received. The second base station internal message includes the amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity.

[0122] In some embodiments, after the base station user plane entity receives the first group of downlink small data packets of the terminal from the core network, it determines that these small data packets all belong to the SDT bearer, starts the timer, and counts the data volume of the small data packets. The data volume is the data packet size after adding the SDAP header. If the small data packets of the terminal are received from the core network before the timer expires, these small data packets will continue to be cached and the total data volume of the small data packets will be accumulated.

[0123] After the timer expires, the base station user plane entity notifies the base station control plane entity via a second base station internal message, wherein the second base station internal message also includes the size of the cached downlink SDT data packet. The downlink SDT data packet is a small downlink data packet carried by the SDT.

[0124] As shown in Figure 6, after the base station user plane entity sends the second base station message for the terminal and does not receive the user context modification message sent by the base station control plane entity, if the base station user plane entity receives the SDT data packet of the terminal (that is, the downlink small data packet carried by SDT) again, the base station user plane entity will continue to send it to the base station control plane entity through the second base station message. If a data packet not carried by SDT is received again, the second base station message sent again will not carry the cached downlink SDT data packet size.

[0125] In S506, a first paging message including an RRC paging message sent to the terminal and first auxiliary information is sent to the base station separation entity, the first auxiliary information at least includes downlink SDT indication information, and the RRC paging message at least includes downlink SDT indication information.

[0126] A first paging message is sent to the base station separation entity, where the first paging message includes an RRC paging message sent to the terminal and first auxiliary information; the first auxiliary information includes at least downlink SDT indication information, and the RRC paging message includes at least downlink SDT indication information.

[0127] FIG7 shows a flow chart of a method for notifying arrival of user plane data in an embodiment of the present disclosure. As shown in FIG7 , steps S702 - S706 of the method are similar to steps S502 - S506 of the above embodiment and are not described again here.

[0128] Different from the above embodiment, in the embodiment of Figure 7, the base station control plane entity also sends a second paging message containing second auxiliary information to the neighboring base station, and the second paging message includes an RRC paging message sent to the terminal; wherein the second auxiliary information includes at least one of the following information: the size of the cached downlink data volume of all SDT bearers cached in the base station user plane entity and the downlink SDT indication.

[0129] After the base station control plane entity receives a message within the second base station or a high-level signaling message sent to the user from the core network, if it only receives a high-level signaling message sent from the core network, it directly sends a first paging message to the base station separation entity and / or sends a second paging message to the adjacent second base station (i.e., the neighboring base station); if it receives a message within the second base station, it determines whether the indicated cached downlink SDT data packet size meets the downlink small data packet sending trigger threshold. If it is less than the trigger threshold, it sends a first paging message to the base station separation entity and sends a second paging message to the adjacent base station. The specific value of the downlink small data packet sending threshold is configured by the network management.

[0130] When the base station control plane entity sends the first paging message to the base station separation entity, the auxiliary information is carried to indicate MT-SDT paging and the first RRC message, where the first RRC message includes MT-SDT indication information.

[0131] The base station control plane entity sends a second paging message to the second base station via the Xn interface, where the second paging message includes at least one of MT-SDT indication information, a downlink SDT data packet size, and / or signaling indication information. The downlink SDT data packet size is the downlink SDT data packet size cached by the first base station user plane entity.

[0132] Figure 8 shows a method for notifying the arrival of user plane data in an embodiment of the present disclosure, which is applied to a base station control plane entity of a separated architecture base station. As shown in Figure 8, the method for notifying the arrival of user plane data provided in an embodiment of the present disclosure includes steps S802-S806.

[0133] In S802, a first intra-base station request message is sent to a base station user plane entity, where the first intra-base station request message includes configuration of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported.

[0134] In S804, a response message is received from the first base station, confirming the establishment of the requested bearer configuration.

[0135] In some embodiments, the request message within the first base station includes an SDT bearer list, where the SDT bearer list is used to instruct the base station user plane entity to reconfigure or create one or more DRBs as SDT bearers for the terminal.

[0136] In some embodiments, the indication information of whether downlink SDT is supported is indicated by whether the SDT bearer request mode is carried; the SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode is not carried, it indicates that only all SDT DRBs are configured as uplink SDT.

[0137] In S806, a second base station message is received from the base station user plane entity. The second base station message is used to notify the base station control plane entity that the terminal downlink data has been received. The second base station message includes the amount of downlink data carried by all SDTs of the terminal cached in the base station user plane entity.

[0138] In S808, a first paging message including an RRC paging message sent to the terminal and first auxiliary information is sent to the base station separation entity, wherein the first auxiliary information at least includes downlink SDT indication information, and the RRC paging message at least includes downlink SDT indication information.

[0139] A first paging message is sent to the base station separation entity, where the first paging message includes an RRC paging message sent to the terminal and first auxiliary information; the first auxiliary information includes at least downlink SDT indication information, and the RRC paging message includes at least downlink SDT indication information.

[0140] In some embodiments, the method further includes sending a second paging message including second auxiliary information to the neighboring base station, where the second paging message includes an RRC paging message sent to the terminal; wherein the second auxiliary information includes at least one of the following information:

[0141] The amount of buffered downlink data and downlink SDT indication information of all SDT bearers buffered in the user plane entity of the base station.

[0142] In some embodiments, when a second base station message is received from a base station user plane entity, the method also includes determining whether the cache quantity of the downlink SDT bearer in the base station user plane entity is less than the downlink small data packet sending threshold; if it is less than the downlink small data packet sending threshold, a first paging message is sent to the base station separation entity and a second paging message is sent to the neighboring base station.

[0143] In some embodiments, the base station control plane entity sends a second paging message to the neighboring base station through the Xn interface, and the RRC paging message included in the second paging message includes at least downlink SDT indication information.

[0144] In some embodiments, the value of the downlink small data packet sending threshold can be configured by a network administrator.

[0145] In some embodiments, if a high-level signaling message is received from the core network, a first paging message is directly sent to the base station separation entity and / or a second paging message is sent to the neighboring base station. The second paging message does not carry the size of the cached downlink data of all SDT bearers cached in the base station user plane entity.

[0146] The following describes in detail the method for notifying the arrival of user plane data provided by the present disclosure by taking a specific example as an example, standing at the side of the base station control plane entity.

[0147] This embodiment mainly describes the process in which the base station control plane entity gNB-CU-CP configures the base station user plane entity gNB-CU-UP with an SDT bearer using Rel-18 SDT, and the process in which the base station user plane entity receives a single small data packet, triggering the arrival of downlink data, and then receives another downlink data packet from the core network after sending it, further triggering the arrival of downlink data.

[0148] The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. The message sets DRB#1 and DRB#2 carried in PDU Session#1 as SDT bearers and includes an indication for configuring all SDT bearers to use MO-SDT mode in Rel-18. The BEARER CONTEXT MODIFICATION REQUEST information element configuration is shown in the following table:

[0149] The information elements in the PDU Session Resource To Modify List are as follows:

[0150] After receiving the message, the gNB-CU-UP configures DRB#1 and DRB#2 as SDT bearers, configures the MT-SDT mode, and returns a BEARER CONTEXT MODIFICATION RESPONSE response.

[0151] After receiving data packets from the core network SMF, the gNB-CU-UP processes the SDAP header and caches the data packets. It then determines that the DRB to which these data packets belong belongs to an SDT bearer. It calculates the byte size, including the SDAP header, to be 340 kbytes and starts a timer with a duration of 20 ms.

[0152] After the timer expires and no other data packets are received from the user, a DL DATA NOTIFICATION message is sent to the gNB-CU-CP. The specific information elements are:

[0153] After receiving the DL DATA NOTIFICATION message, the gNB-CU-CP checks the DL SDT Buffer Size carried in it and compares it with the set threshold of 800 kbytes to trigger MT-SDT-based paging.

[0154] The gNB-CU-CP generates a paging message based on MT-SDT, where the paging message carries a one-bit MT-SDT indication.

[0155] After receiving the data packet from the core network, the gNB-CU-UP finds that it is still an SDT small data packet and stops sending the DL DATA NOTIFICATION message to the gNB-CU-CP.

[0156] Figure 9 shows a method for notifying the arrival of user plane data in an embodiment of the present disclosure, which is applied to a base station user plane entity of a separated architecture base station. As shown in Figure 9, the method for notifying the arrival of user plane data provided in an embodiment of the present disclosure includes steps S902-S906.

[0157] In S902, a first intra-base station request message sent by a base station control plane entity is received, the first intra-base station request message including configuration or modification of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported. Here, configuration may include reconfiguration (ie, modification) or new creation.

[0158] In some embodiments, the indication information of whether downlink SDT is supported is indicated by whether the SDT bearer request mode is carried to indicate whether downlink SDT and uplink SDT are supported at the same time; the SDT bearer request mode indicates that all SDT DRBs support downlink SDT and uplink SDT at the same time. When the SDT bearer request mode is not carried, it indicates that only all SDT DRBs are configured as uplink SDT.

[0159] In S904, the first base station responds to the request message within the first base station and confirms the establishment of the requested bearer configuration.

[0160] In response to the request message within the first base station, the relevant DRB is configured as an SDT DRB according to the indication; when the SDT bearer request mode is carried, the data volume of the downlink SDT bearer is counted and sent to the base station control plane entity through the message within the second base station, otherwise the data volume of the downlink SDT bearer is not counted; the response message is sent to the base station control plane entity.

[0161] In S906, after the downlink data of the SDT bearer of the terminal arrives, a second base station internal message is sent to the base station control plane entity, where the second base station internal message includes at least the amount of buffered downlink data of all SDT bearers buffered in the base station user plane entity.

[0162] In some embodiments, the method shown in Figure 9 also includes: if a small downlink data packet carried by a terminal other than the SDT is received, a new second base station message is sent to the base station control plane entity, and the new second base station message does not carry the cached SDT-carried downlink data packet size.

[0163] In some embodiments, as shown in FIG10 , after the terminal downlink data carried by the SDT arrives, sending a second intra-base station message to the base station control plane entity includes:

[0164] S1002, receiving a small downlink data packet from a terminal in the core network, adding an SDAP header, and buffering the packet;

[0165] S1004, determining whether all downlink small data packets belong to the configured SDT DRBs;

[0166] S1006, when all downlink small data packets belong to the SDT bearer, counting the data volume of the small data packets;

[0167] S1008, determining whether the SDT bearer request mode is configured;

[0168] When the SDT bearer request mode is configured, DRB supports both downlink SDT and uplink SDT.

[0169] S1010: Send a second intra-base station message to a base station control plane entity, where the second intra-base station message includes a total data volume of buffered small data packets.

[0170] In some embodiments, when all downlink small data packets belong to the SDT bearer, the method further includes:

[0171] Start the timer according to the configuration. The timer is configured by the network management;

[0172] If only small data packets carrying downlink SDT data from the terminal are received before the timer expires, the small data packets will continue to be buffered and the total data volume of the small data packets will be accumulated;

[0173] After the timer times out, a second intra-base-station message is sent to the base station control plane entity, where the second intra-base-station message includes the total data volume of the buffered small data packets.

[0174] In some embodiments, counting the data volume of the small data packet includes caching the downlink small data packet after SDAP processing; counting the data volume of the small data packet is counting the size of the data packet after adding the SDAP header.

[0175] The disclosed embodiment transmits cache information through the user plane entity to solve the problem of whether the control plane entity decides to trigger downlink SDT data, and clarifies the method for calculating the cache quantity from the user plane and core network signaling, thereby ensuring the consistency of the control plane and user plane's understanding of the downlink SDT trigger.

[0176] In some embodiments, after sending the second intra-base station message to the base station control plane entity, and when no user context modification message sent by the base station control plane entity is received, the method further includes:

[0177] If the SDT data packet of the terminal is received again, a new second base station internal message is sent to the base station control plane entity, where the new second base station internal message includes the number of downlink SDT bearers newly cached in the base station user plane entity;

[0178] If a data packet not carried by the SDT is received again, a new second intra-base-station message is continuously sent to the base station control plane entity, and the new second intra-base-station message does not carry the cached downlink SDT data packet size.

[0179] The disclosed embodiment clarifies the processing scheme after multiple data packets arrive one after another, avoiding the difference in SDT cache reporting values ​​caused by different implementation methods, so as to facilitate the base station MAC layer to better send data, thereby reducing terminal power consumption.

[0180] The following describes in detail the method for notifying the arrival of user plane data provided by the present disclosure by means of a specific example at a base station control plane entity.

[0181] This embodiment mainly describes the process in which the base station control plane entity gNB-CU-CP configures the base station user plane entity gNB-CU-UP with an SDT bearer using Rel-18 SDT, and the process in which the user plane entity receives a single small data packet, triggering the arrival of downlink data.

[0182] The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. The message sets DRB#1 and DRB#2 carried in PDU Session#1 as SDT bearers and includes an indication to configure all SDT bearers to Rel-18 MO-SDT (uplink SDT). The BEARER CONTEXT MODIFICATION REQUEST information elements are as follows:

[0183] The information elements in the PDU Session Resource To Modify List are as follows:

[0184] After receiving the message, the gNB-CU-UP configures DRB#1 and DRB#2 as SDT bearers, configures MT-SDT (downlink SDT) mode, and returns a BEARER CONTEXT MODIFICATION RESPONSE message.

[0185] After receiving data packets from the core network SMF, the gNB-CU-UP processes the SDAP header and caches the data packets. It then determines that the DRB to which these data packets belong belongs to an SDT bearer. It calculates the byte size, including the SDAP header, to be 340 kbytes and starts a timer with a duration of 20 ms.

[0186] After the timer expires and no other data packets are received from the user, a DL DATA NOTIFICATION message is sent to the gNB-CU-CP. The specific information elements are:

[0187] After receiving the DL DATA NOTIFICATION message, the gNB-CU-CP checks the DL SDT Buffer Size carried in it and compares it with the set threshold of 800 kbytes to trigger MT-SDT-based paging.

[0188] The gNB-CU-CP generates a paging message based on MT-SDT, where the paging message carries a one-bit MT-SDT indication.

[0189] In some embodiments, the gNB-CU-CP primarily sends configuration information to the gNB-DU to enable the UE to maintain uplink CG-SDT resources in idle state for use as downlink SDT feedback information. After the UE responds with an uplink RRC Resume Request message, the SDT bearer resumption and downlink data transmission process is triggered.

[0190] When the gNB-CU-CP determines that the UE needs to enter the inactive state, it determines, based on the user's movement speed and service characteristics, that the UE can use CG-SDT resources as a response for downlink small data packet transmission. It then sends a UE CONTEXT RELEASE COMMAND to the gNB-DU. The specific information elements are as follows:

[0191] The RRC Release message includes the following:

[0192] Bearer identification list: DRB#1 and DRB#2;

[0193] Whether to use the dedicated PRACH resources allocated for uplink SDT: Yes;

[0194] Dedicated BWP configuration for downlink SDT;

[0195] Dedicated BWP configuration for SDT in uplink;

[0196] CS-RNTI for CG-SDT;

[0197] Use the RSRP threshold of CG-SDT;

[0198] RSRP change limit when CG-SDT is used.

[0199] After receiving the gNB-DU, the gNB-DU determines that the UE uses uplink CG-SDT resources as a downlink SDT response based on the CG-SDT Keep Indicator and the MT-SDT indicator. The gNB-DU retains the CG-SDT-related resources, CS-RNTI, C-RNTI, CG-SDT-related RLC layer configuration, and the F1-U connection related to the SDT bearer.

[0200] The gNB-DU sends the RRC Release message carried in the UE CONTEXT RELEASE COMMAND to the UE.

[0201] After the gNB-DU receives the RRC Resume message sent by the UE on the CG-SDT, it transmits the message via the INITIAL UL RRC MESSAGE TRANSFER.

[0202] The embodiments of the present disclosure do not involve any impact on the terminal. The network-side solution has good forward compatibility and is easy to deploy and implement on the network.

[0203] In the embodiments of the present disclosure, the terms “first,” “second,” and “third” are used for descriptive purposes only and should not be understood as indicating or implying relative importance.

[0204] In this disclosure, the term "and / or" simply describes an association relationship between related objects, indicating that three possible relationships exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0205] Furthermore, although the steps of the methods of the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in this particular order, or that all illustrated steps must be performed to achieve desired results.

[0206] In some embodiments, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0207] Based on the same inventive concept, the embodiments of the present disclosure also provide a base station control plane entity for a split-architecture base station, as described in the following embodiments. Since the principles for solving the problem in this entity embodiment are similar to those in the above-mentioned method embodiment, the implementation of this entity embodiment can refer to the implementation of the above-mentioned method embodiment, and the repeated parts will not be repeated.

[0208] FIG11 shows a base station control plane entity of a split-architecture base station according to an embodiment of the present disclosure. As shown in FIG11 , the base station control plane entity 1100 of the split-architecture base station includes:

[0209] A message sending module 1102 is configured to send a first intra-base station request message to a base station user plane entity, where the first intra-base station request message includes information indicating whether to configure at least one DRB as an SDT bearer and whether to support downlink SDT;

[0210] The second receiving module 1104 is configured to receive a response message from the first base station to confirm establishment of the requested bearer configuration;

[0211] The notification receiving module 1106 is configured to receive a second intra-base station message from the base station user plane entity, where the second intra-base station message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second intra-base station message includes the amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity;

[0212] The paging sending module 1108 is used to send a first paging message containing first auxiliary information to the base station separation entity. The first paging message also includes an RRC paging message sent to the terminal. The first auxiliary information at least includes downlink SDT indication information. The RRC paging message at least includes downlink SDT indication information.

[0213] In some embodiments, the base station control plane entity 1100 further includes a transmission termination module. The transmission termination module is configured to terminate the transmission process of the downlink small data packet upon receiving a new second intra-base station message from the base station user plane entity, wherein the new second intra-base station message is used to notify the base station control plane entity of the receipt of a downlink small data packet not carried by the terminal in an SDT bearer, and the new second intra-base station message does not carry the size of the cached downlink data packet carried in an SDT bearer.

[0214] In some embodiments, the request message within the first base station includes an SDT bearer list, where the SDT bearer list is used to instruct the base station user plane entity to reconfigure or create one or more DRBs as SDT bearers for the terminal.

[0215] In some embodiments, the indication information of whether downlink SDT is supported indicates whether downlink SDT is supported by whether the SDT bearer request mode is carried;

[0216] The SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode is not carried, it indicates that all SDT DRBs are configured only as uplink SDT.

[0217] In some embodiments, the base station control plane entity 1100 of the split architecture base station further includes:

[0218] A second paging module is configured to send a second paging message including second auxiliary information to a neighboring base station, where the second paging message includes an RRC paging message sent to the terminal;

[0219] The second auxiliary information includes at least one of the following information:

[0220] The amount of buffered downlink data and downlink SDT indication information of all SDT bearers buffered in the user plane entity of the base station.

[0221] In some embodiments, the paging sending module 1108 is used to determine whether the amount of downlink data carried by the SDT cached in the base station user plane entity is less than the downlink small data packet sending trigger threshold when receiving a second base station message from the base station user plane entity; if it is less than the downlink small data packet sending trigger threshold, a first paging message is sent to the base station separation entity and a second paging message is sent to the neighboring base station.

[0222] In some embodiments, the paging sending module 1108 is configured to send a second paging message to a neighboring base station via an Xn interface, where the RRC paging message included in the second paging message includes at least downlink SDT indication information.

[0223] In some embodiments, the value of the downlink small data packet sending threshold is configured by a network administrator.

[0224] In some embodiments, the paging sending module 1108 is used to directly send a first paging message to the base station separation entity and / or send a second paging message to the neighboring base station if a high-layer signaling message is received from the core network; the second paging message directly sent to the neighboring base station does not carry the size of the cached downlink data of all SDT bearers cached in the base station user plane entity.

[0225] Based on the same inventive concept, an embodiment of the present disclosure further provides a base station user plane entity of a split architecture base station. As shown in FIG12 , the base station user plane entity 1200 of the split architecture base station includes:

[0226] The message receiving module 1202 is configured to receive a first intra-base station request message sent by a base station control plane entity, where the first intra-base station request message includes information indicating whether to configure or modify at least one DRB as an SDT bearer and whether downlink SDT is supported;

[0227] The message response module 1204 is configured to respond to the request message within the first base station and confirm the establishment of the requested bearer configuration;

[0228] The notification sending module 1206 is used to send a second base station internal message to the base station control plane entity after the downlink data of the terminal's SDT bearer arrives. The second base station internal message includes at least the amount of cached downlink data of all SDT bearers cached in the base station user plane entity.

[0229] In some embodiments, the notification sending module 1206 is also used to send a new second base station message to the base station control plane entity if a small downlink data packet not carried by the terminal on the SDT is received. The new second base station message does not carry the size of the cached downlink data packet carried by the SDT.

[0230] In some embodiments, the indication information of whether downlink SDT is supported indicates whether both downlink SDT and uplink SDT are supported by carrying an SDT bearer request mode;

[0231] The SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode is not carried, it indicates that all SDT DRBs are configured only as uplink SDT.

[0232] In some embodiments, the message response module 1204 is used to configure the relevant DRB as an SDT DRB according to the indication; when the SDT bearer request mode is carried, the data volume of the downlink SDT bearer is counted and sent to the base station control plane entity through the message within the second base station, otherwise the data volume of the downlink SDT bearer is not counted; and the response message is sent to the base station control plane entity.

[0233] In some embodiments, the notification sending module 1206 is used to receive downlink small data packets from the terminal in the core network, cache them after adding an SDAP header; determine whether all the DRBs corresponding to the downlink small data packets belong to the configured SDT DRBs; when all the downlink small data packets belong to the SDT bearer, count the data volume of the small data packets; determine whether the SDT bearer request mode is configured; and send a second base station message to the base station control plane entity, the second base station message including the total data volume of all cached downlink small data packets of the SDT bearers of the user terminal.

[0234] In some embodiments, the notification sending module 1206 is used to start a timer according to the configuration when all downlink small data packets belong to the SDT bearer, and the timer is configured by the network management; if only downlink SDT bearer small data packets of the terminal continue to be received before the timer expires, the small data packets will continue to be cached and the total data volume of the small data packets will be accumulated; after the timer expires, a second base station message is sent to the base station control plane entity, and the second base station message includes the total data volume of the cached small data packets.

[0235] In some embodiments, counting the data volume of the small data packet is counting the size of the data packet after adding the SDAP header.

[0236] In some embodiments, the notification sending module 1206 is used to continue sending a new second base station message to the base station control plane entity after sending a second base station message to the base station control plane entity and not receiving a user context modification message sent from the base station control plane entity, if an SDT data packet of the terminal is received again, the new second base station message includes the cache number of downlink SDT bearers newly cached in the base station user plane entity; if a non-SDT bearer data packet is received again, the new second base station message is continued to be sent to the base station control plane entity, and the new second base station message does not carry the cached downlink SDT data packet size.

[0237] The concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0238] Regarding the base station user plane entity of the separated architecture base station and the base station control plane entity of the separated architecture base station in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the notification method for the arrival of user plane data, and will not be elaborated here.

[0239] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, such division is not mandatory.

[0240] In fact, according to the embodiment of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0241] Some of the blocks shown in the accompanying drawings are functional entities that do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0242] The electronic device provided by an embodiment of the present disclosure is described below with reference to Figure 13. The electronic device 1300 shown in Figure 13 is merely an example and should not limit the functions and scope of use of the embodiment of the present disclosure.

[0243] FIG13 shows a schematic diagram of the architecture of an electronic device 1300 provided by an embodiment of the present disclosure. As shown in FIG13 , the electronic device 1300 includes but is not limited to: at least one processor 1310 and at least one memory 1320 .

[0244] The memory 1320 is used to store instructions.

[0245] In some embodiments, the memory 1320 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 13201 and / or a cache memory unit 13202 , and may further include a read-only memory unit (ROM) 13203 .

[0246] In some embodiments, the memory 1320 may also include a program / utility 13204 having a set (at least one) of program modules 13205, such program modules 13205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0247] In some embodiments, the memory 1320 may store an operating system, which may be a real-time operating system (RTX), LINUX, UNIX, WINDOWS, or OS X.

[0248] In some embodiments, data may also be stored in the memory 1320 .

[0249] As an example, the processor 1310 may read data stored in the memory 1320 . The data may be stored at the same storage address as the instruction, or the data may be stored at a different storage address than the instruction.

[0250] The processor 1310 is configured to call instructions stored in the memory 1320 to implement the steps of various exemplary embodiments of the present disclosure described in the "Exemplary Method" section above. For example, the processor 1310 may execute the steps of the aforementioned method embodiments.

[0251] It should be noted that the processor 1310 may be a general-purpose processor or a dedicated processor. The processor 1310 may include one or more processing cores, and the processor 1310 executes various functional applications and data processing by running instructions.

[0252] In some embodiments, the processor 1310 may include a central processing unit (CPU) and / or a baseband processor.

[0253] In some embodiments, the processor 1310 may determine an instruction based on the priority identifier and / or function category information carried in each control instruction.

[0254] In the present disclosure, the processor 1310 and the memory 1320 may be provided separately or integrated together.

[0255] As an example, the processor 1310 and the memory 1320 may be integrated on a single board or a system on chip (SOC).

[0256] 13 , the electronic device 1300 is implemented as a general-purpose computing device and may further include a bus 1330 .

[0257] The bus 1330 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures.

[0258] The electronic device 1300 may also communicate with one or more external devices 1340 (e.g., a keyboard, a pointing device, a Bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 1300, and / or any device that enables the electronic device 1300 to communicate with one or more other computing devices (e.g., a router, a modem, etc.). Such communication may occur through an input / output (I / O) interface 1350.

[0259] Furthermore, the electronic device 1300 can also communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through the network adapter 1360 .

[0260] As shown in FIG. 13 , the network adapter 1360 communicates with other modules of the electronic device 1300 through the bus 1330 .

[0261] It should be understood that although not shown in the figures, other hardware and / or software modules may be used in conjunction with the electronic device 1300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0262] It should be understood that the structures illustrated in the embodiments of the present disclosure do not constitute a specific limitation on the electronic device 1300. In other embodiments of the present disclosure, the electronic device 1300 may include more or fewer components than those shown in FIG13, or may combine or separate certain components, or may have different component arrangements. The components shown in FIG13 may be implemented in hardware, software, or a combination of software and hardware.

[0263] The present disclosure further provides a computer-readable storage medium having computer instructions stored thereon. When the computer instructions are executed by a processor, the method for notifying the arrival of user plane data described in the above method embodiment is implemented.

[0264] The computer-readable storage medium in the embodiments of the present disclosure is a computer instruction that can be sent, propagated or transmitted for use by or in conjunction with an instruction execution system, apparatus or device.

[0265] As an example, computer readable storage media are non-volatile storage media.

[0266] In some embodiments, more specific examples of computer-readable storage media in the present disclosure may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, a USB flash drive, a mobile hard disk, or any suitable combination of the foregoing.

[0267] In the embodiments of the present disclosure, the computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer instructions (readable program codes).

[0268] Such a propagated data signal may take any of a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof.

[0269] In some examples, computing instructions contained on a computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0270] The embodiments of the present disclosure further provide a computer program product, which stores instructions. When the instructions are executed by a computer, the computer implements the method for notifying the arrival of user plane data described in the above method embodiment.

[0271] The above instructions may be program codes. In specific implementation, the program codes may be written in any combination of one or more programming languages.

[0272] Programming languages ​​include object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages.

[0273] The program code may execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server.

[0274] Where a remote computing device is involved, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0275] The embodiment of the present disclosure further provides a chip, comprising at least one processor and an interface;

[0276] An interface for providing program instructions or data to at least one processor;

[0277] At least one processor is configured to execute program instructions to implement the method for notifying the arrival of user plane data described in the above method embodiment.

[0278] In some embodiments, the chip may further include a memory for storing program instructions and data, and the memory may be located inside or outside the processor.

[0279] Those skilled in the art will appreciate that all or part of the steps for implementing the above embodiments may be implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software, which may be collectively referred to herein as a "circuit," "module," or "system."

[0280] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein.

[0281] This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the appended claims.

Claims

1. A method for notifying arrival of user plane data, characterized in that: Applied to a base station control plane entity of a split architecture base station, the method comprising: Sending a first base station intra-request message to a base station user plane entity, where the first base station intra-request message includes configuring at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported; Receiving a response message from the first base station, confirming establishment of the requested configuration bearer; receiving a second base station internal message from a base station user plane entity, where the second base station internal message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second base station internal message includes the amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity; A first paging message including first auxiliary information is sent to a base station separation entity, wherein the first paging message also includes an RRC paging message sent to a terminal, the first auxiliary information at least includes downlink SDT indication information, and the RRC paging message at least includes downlink SDT indication information.

2. A method for notifying arrival of user plane data, characterized in that: Applied to a base station control plane entity of a split architecture base station, the method comprising: Sending a first base station intra-request message to a base station user plane entity, where the first base station intra-request message includes configuring at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported; Receiving a response message from the first base station, confirming establishment of the requested configuration bearer; receiving a second base station internal message from a base station user plane entity, where the second base station internal message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second base station internal message includes the amount of downlink data of all SDT bearers of the terminal cached in the base station user plane entity; Sending a first paging message including first auxiliary information to the base station separation entity, where the first auxiliary information at least includes downlink SDT indication information; If a new second base station message is received from the base station user plane entity, the transmission process of the downlink small data packet is terminated. The new second base station message is used to notify the base station control plane entity that the downlink small data packet carried by the terminal non-SDT is received. The new second base station message does not carry the cached SDT-carried downlink data packet size.

3. The method according to claim 1 or 2, characterized in that: The first base station internal request message includes an SDT bearer list, and the SDT bearer list is used to instruct the base station user plane entity to reconfigure or create one or more DRBs as SDT bearers for the terminal.

4. The method according to any one of claims 1 to 3, characterized in that The indication information of whether downlink SDT is supported indicates whether downlink SDT is supported by whether the SDT bearer request mode is carried; The SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode does not carry, it indicates that all SDT DRBs are configured as uplink SDT only.

5. The method according to claim 1 or 2, characterized in that: The method further comprises: Sending a second paging message including second auxiliary information to a neighboring base station, where the second paging message includes an RRC paging message sent to the terminal; The second auxiliary information further includes at least one of the following information: The cached downlink data volume and downlink SDT indication information of all SDT bearers cached in the user plane entity of the base station.

6. The method according to claim 5, characterized in that In case a second intra-base station message from a base station user plane entity is received, the method further comprises: Determine whether the amount of downlink data carried by the SDT cached in the user plane entity of the base station is less than a downlink small data packet sending trigger threshold; When the amount of the downlink small data packet is less than the trigger threshold for sending the downlink small data packet, the first paging message is sent to the base station separation entity and the second paging message is sent to a neighboring base station.

7. The method according to claim 6, characterized in that The base station control plane entity sends a second paging message to the neighboring base station through the Xn interface, and the RRC paging message included in the second paging message includes at least downlink SDT indication information.

8. The method according to claim 6, characterized in that The value of the downlink small data packet sending trigger threshold is configured by the network management.

9. The method according to any one of claims 5 to 8, characterized in that: If a high-layer signaling message sent from the core network is received and a second base station internal message of the base station user plane entity is not received at the same time, directly sending a first paging message to the base station separation entity and / or sending a second paging message to a neighboring base station; The second paging message directly sent to the neighboring base station does not carry the size of the buffered downlink data volume of all SDT bearers buffered in the user plane entity of the base station.

10. A method for notifying arrival of user plane data, characterized in that: Applied to a base station user plane entity of a split architecture base station, the method comprises: Receiving a first intra-base station request message sent by a base station control plane entity, where the first intra-base station request message includes configuration or modification of at least one DRB as an SDT bearer, and indication information of whether downlink SDT is supported; Responding to the first base station internal request message, confirming establishment of the requested configuration bearer; After the downlink data of the SDT bearer of the terminal arrives, a second base station internal message is sent to the base station control plane entity, wherein the second base station internal message at least includes the size of the cached downlink data amount of all SDT bearers cached in the base station user plane entity.

11. A method for notifying arrival of user plane data, characterized in that: Applied to a base station user plane entity of a split architecture base station, the method comprises: Receiving a first intra-base station request message sent by a base station control plane entity, where the first intra-base station request message includes configuration or modification of at least one DRB as an SDT bearer, and indication information of whether downlink SDT is supported; Responding to the first base station internal request message, confirming establishment of the requested configuration bearer; After the downlink data of the SDT bearer of the terminal arrives, send a second base station internal message to the base station control plane entity, wherein the second base station internal message includes at least the amount of cached downlink data of all SDT bearers cached in the base station user plane entity; If a small downlink data packet not carried by the SDT of the terminal is received, a new second intra-base station message is sent to the base station control plane entity, wherein the new second intra-base station message does not carry the size of the cached downlink data packet carried by the SDT.

12. The method according to claim 10 or 11, characterized in that: The indication information of whether downlink SDT is supported indicates whether downlink SDT is supported by whether the SDT bearer request mode is carried; The SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT. When the SDT bearer request mode does not carry, it indicates that all SDT DRBs are configured as uplink SDT only.

13. The method according to claim 12, characterized in that Responding to the first base station internal request message, confirming establishment of the requested configuration bearer, including: Configure the relevant DRB as SDT DRB according to the instruction; When the SDT bearer request mode is used, the data volume of the downlink SDT bearer is counted and sent to the base station control plane entity through the second base station internal message; otherwise, the data volume of the downlink SDT bearer is not counted; The response message is sent to the base station control plane entity.

14. The method according to claim 12, characterized in that When the SDT bearer downlink data of the terminal arrives, sending a second base station internal message to the base station control plane entity includes: Receive small downlink data packets from the terminal of the core network, add SDAP packet header and cache; Determine whether all the DRBs corresponding to the downlink small data packets belong to the SDT DRBs configured by the base station user plane entity; In the case where all the downlink small data packets belong to the SDT bearer, counting the data volume of the small data packets; Determine whether the SDT bearer request mode is configured; A second base station internal message is sent to the base station control plane entity, where the second base station internal message includes the downlink data volume of all SDT bearers of the terminal cached in the base station user plane entity.

15. The method according to claim 14, characterized in that In the case where all the downlink small data packets belong to the SDT bearer, the method further includes: Starting a timer according to a configuration, wherein the timer is configured by a network management; If only the downlink small data packet carried by the SDT of the terminal continues to be received before the timer expires, the downlink small data packet continues to be cached, and the total data volume of the downlink small data packet is accumulated; After the timer times out, the second base station internal message is sent to the base station control plane entity.

16. The method according to claim 14, characterized in that The statistical data volume of the small data packet is the size of the data packet after the SDAP header is added.

17. The method according to claim 10 or 11, characterized in that: After sending the second intra-base station message to the base station control plane entity, when no user context modification message sent by the base station control plane entity is received, the method further includes: If a downlink small data packet carried by the SDT of the terminal is received again, a new second base station internal message is continued to be sent to the base station control plane entity, wherein the new second base station internal message includes the downlink data volume of the SDT carried by the new cache in the base station user plane entity; If a non-SDT-bearing downlink small data packet is received again, a new second base station internal message continues to be sent to the base station control plane entity, and the new second base station internal message does not carry the cached SDT-bearing downlink data packet size.

18. A base station control plane entity of a separated architecture base station, characterized in that: include: A message sending module, configured to send a first base station internal request message to a base station user plane entity, wherein the first base station internal request message includes configuration of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported; A second receiving module is used to receive a response message from the first base station to confirm the establishment of the requested configuration bearer; a notification receiving module, configured to receive a second base station internal message from a base station user plane entity, wherein the second base station internal message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second base station internal message includes the size of downlink data carried by all SDTs of the terminal cached in the base station user plane entity; The paging sending module is used to send a first paging message containing first auxiliary information to the base station separation entity, the first paging message also includes an RRC paging message sent to the terminal, the first auxiliary information at least includes downlink SDT indication information, and the RRC paging message at least includes downlink SDT indication information.

19. A base station control plane entity of a separated architecture base station, characterized in that: include: A message sending module, configured to send a first base station internal request message to a base station user plane entity, wherein the first base station internal request message includes configuration of at least one DRB as an SDT bearer and indication information of whether downlink SDT is supported; A second receiving module is used to receive a response message from the first base station to confirm the establishment of the requested configuration bearer; a notification receiving module, configured to receive a second base station internal message from a base station user plane entity, wherein the second base station internal message is used to notify the base station control plane entity that downlink data of the terminal has been received, and the second base station internal message includes the size of downlink data carried by all SDTs of the terminal cached in the base station user plane entity; A paging sending module, configured to send a first paging message including first auxiliary information to a base station separation entity, wherein the first paging message further includes an RRC paging message sent to a terminal, the first auxiliary information at least includes downlink SDT indication information, and the RRC paging message at least includes downlink SDT indication information; A transmission termination module is used to terminate the transmission process of the downlink small data packet if a new second base station message is received from the base station user plane entity. The new second base station message is used to notify the base station control plane entity that the downlink small data packet carried by the terminal non-SDT is received. The new second base station message does not carry the cached SDT-carried downlink data packet size.

20. A base station user plane entity of a separated architecture base station, characterized in that: include: A message receiving module, configured to receive a first base station internal request message sent by a base station control plane entity, wherein the first base station internal request message includes configuration or modification of at least one DRB as an SDT bearer, and indication information of whether downlink SDT is supported; A message response module, used to respond to the request message within the first base station and confirm the establishment of the requested configuration bearer; The notification sending module is used to send a second base station message to the base station control plane entity after the downlink data carried by the terminal's SDT arrives, wherein the second base station message at least includes the size of the cached downlink data volume of all SDT bearers cached in the base station user plane entity.

21. A base station user plane entity of a separated architecture base station, characterized in that: include: A message receiving module, configured to receive a first base station internal request message sent by a base station control plane entity, wherein the first base station internal request message includes configuration or modification of at least one DRB as an SDT bearer, and indication information of whether downlink SDT is supported; A message response module, used to respond to the request message within the first base station and confirm the establishment of the requested configuration bearer; Notification sending module, used for sending a notification to the base station control plane after the downlink data carried by the SDT of the terminal arrives. The second base station internal message includes at least the size of the buffered downlink data volume of all SDT bearers buffered in the user plane entity of the base station; And if a small downlink data packet not carried by the SDT of the terminal is received, a new second base station message is sent to the base station control plane entity, wherein the new second base station message does not carry the size of the downlink data packet carried by the cached SDT.

22. A split architecture base station, characterized in that: include: Base station separation entity; A base station centralized entity, wherein the base station centralized entity includes a base station control plane entity and a base station user plane entity; the base station control plane entity is used to implement the notification method for the arrival of user plane data as described in any one of claims 1-9.

23. An electronic device, characterized in that: include: A memory for storing instructions; A processor, configured to call instructions stored in the memory to implement the method for notifying the arrival of user plane data as described in any one of claims 1 to 17.

24. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed by the processor, the method for notifying the arrival of user plane data as described in any one of claims 1-17 is implemented.

25. A computer program product, characterized in that The computer program product stores instructions, and when the instructions are executed by a computer, the computer implements the method for notifying the arrival of user plane data as described in any one of claims 1 to 17.

26. A chip, characterized in that: comprising at least one processor and an interface; The interface is used to provide program instructions or data to the at least one processor; The at least one processor is used to execute the program instructions to implement the method for notifying the arrival of user plane data as described in any one of claims 1-17.

Citation Information

Patent Citations

  • Method and apparatus for downlink small data transmission operation in mobile communication system

    US20230156702A1

  • SDT processing method, device and system

    WO2021027821A1

  • Methods, architectures, apparatuses and systems for downlink small data transmission (DL SDT) and reception in inactive radio access network (RAN) state

    WO2022192124A1