WO2024239487A1 - 用户面数据到达的通知方法及相关设备 - Google Patents

用户面数据到达的通知方法及相关设备 Download PDF

Info

Publication number
WO2024239487A1
WO2024239487A1 PCT/CN2023/117038 CN2023117038W WO2024239487A1 WO 2024239487 A1 WO2024239487 A1 WO 2024239487A1 CN 2023117038 W CN2023117038 W CN 2023117038W WO 2024239487 A1 WO2024239487 A1 WO 2024239487A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
sdt
message
downlink
plane entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/117038
Other languages
English (en)
French (fr)
Inventor
许森
信金灿
李芳芳
张光辉
熊尚坤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd Beijing Research Institute
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd Beijing Research Institute
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd Beijing Research Institute, China Telecom Corp Ltd filed Critical China Telecom Corp Ltd Beijing Research Institute
Publication of WO2024239487A1 publication Critical patent/WO2024239487A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • 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.
  • 5G 5th Generation Mobile Communication Technology
  • 4G 4th Generation Mobile Communication Technology
  • 5G introduces an inactive state (RRC_INACTIVE), in which 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, and can carry SuspendConfig in the RRC Release message.
  • RRC_INACTIVE Radio Resource Control
  • the introduction of this state is used to solve the transmission of small data packets and reduce the signaling overhead of the core network.
  • 3GPP Rel-17 introduced SDT (Small data transmission) for the uplink direction and defined related processes.
  • Release 18 mainly refers to the related processes triggered by the SDT service in the downlink direction, that is, the process of sending small data packets in the idle state after receiving data packets from the core network.
  • the 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 whether it is the Rel-17 uplink SDT or the Rel-18 downlink SDT.
  • the current 3GPP Rel-17 protocol cannot meet the design requirements of downlink small data packets in the separation architecture, and enhancements are needed to meet the needs of network deployment and optimization.
  • a method for notifying a user plane data arrival is provided, which is applied to a separate rack.
  • a base station control plane entity of a base station is constructed, and the method includes:
  • 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 includes at least downlink SDT indication information, and the RRC paging message includes at least downlink SDT indication information.
  • a method for notifying arrival of user plane data is provided, which is applied to a base station control plane entity of a separated architecture base station, and the method includes:
  • 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;
  • 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.
  • the request message within the first base station includes an SDT bearer list
  • 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.
  • whether the downlink SDT is supported is indicated by whether the SDT bearer request mode is carried to indicate whether the 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 only all SDT DRBs are configured. SDT DRB is the uplink SDT.
  • the method further includes:
  • 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:
  • the size of the cached downlink data volume and downlink SDT indication information of all SDT bearers cached in the user plane entity of the base station is the size of the cached downlink data volume and downlink SDT indication information of all SDT bearers cached in the user plane entity of the base station.
  • the method when a second intra-base station message from a base station user plane entity is received, the method further includes:
  • a first paging message is sent to the base station separation entity and a second paging message is sent to a neighboring base station.
  • the base station control plane entity sends a second paging message to a neighboring base station through an Xn interface, and the RRC paging message included in the second paging message includes at least downlink SDT indication information.
  • 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 volume of all SDT bearers cached in the base station user plane entity.
  • a method for notifying the arrival of user plane data is provided, which is applied to a base station user plane entity of a separated architecture base station, and the method includes:
  • 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;
  • 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.
  • 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, and the method includes:
  • the downlink data of the SDT bearer of the terminal 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;
  • 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.
  • 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 configured as uplink SDT only.
  • 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 a response message to the base station control plane entity.
  • 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, and caching it after adding an SDAP header; determining whether the DRBs corresponding to the downlink small data packets all belong to the SDT DRBs configured by the base station user plane entity; in the case that all the downlink small data packets belong to the SDT bearer, counting the data volume of the small data packets; determining whether the SDT bearer request mode is configured; and 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.
  • the method when 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 downlink small data packets carried by the SDT of the terminal continue to be received before the timer expires, then 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.
  • the statistical data volume of the small data packet is the statistical data packet size after adding the SDAP header.
  • the method further includes: if a downlink small 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 downlink small 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 downlink data packet size of the cached SDT carried.
  • the embodiments and features in the base station control plane entity of the present disclosure may be applied to the base station user plane entity, and vice versa.
  • a base station control plane entity of a separated architecture base station including:
  • 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.
  • a base station control plane entity of a separated architecture base station including:
  • 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.
  • a base station user plane entity of a separated architecture base station including:
  • 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.
  • a base station user plane entity of a separated architecture base station including:
  • 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
  • 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 at least includes the size of the cached downlink data volume of all SDT-carried cached in the base station user plane entity; and if a downlink small 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 cached downlink data packet carried by the SDT.
  • a separated architecture base station 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.
  • an electronic device 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.
  • a computer-readable storage medium having a computer-readable storage medium stored thereon.
  • the computer instruction when executed by the processor, implements the above-mentioned method for notifying the arrival of user plane data.
  • a 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.
  • a chip comprising at least one processor and an interface
  • At least one processor is used to execute program instructions to implement the above-mentioned method for notifying the arrival of user plane data.
  • the notification method and related equipment for the arrival of user plane data support the configuration of a downlink SDT bearer in an architecture where the control plane and user plane of a base station are separated, and support the process of providing auxiliary information to the control plane entity when a downlink data packet arrives, so that the user plane entity (CU-UP) can distinguish between the Rel-17 uplink SDT and the Rel-18 downlink SDT, and can reduce the interoperability problems between the control plane and the user plane of the base station, and support the process of sending small data packets in an architecture where the control plane and user plane are separated.
  • CU-UP user plane entity
  • FIG1 shows a schematic diagram of the architecture of a 5G base station with CU/DU separation in an embodiment of the present disclosure
  • FIG2 is a schematic diagram showing a notification process of user plane data arrival in the related art
  • FIG3 is a schematic diagram showing a process of a control plane notifying a user plane in the related art
  • FIG. 4 shows the SDT signaling process diagram for uplink in Release 17
  • FIG5 shows a schematic structural diagram of a base station with a separation architecture according to an embodiment of the present disclosure
  • FIG6 shows a flow chart of a method for notifying the arrival of user plane data in an embodiment of the present disclosure
  • FIG7 shows a flow chart of another method for notifying the arrival of user plane data in an embodiment of the present disclosure
  • FIG8 shows a flow chart of another method for notifying the arrival of user plane data in an embodiment of the present disclosure
  • FIG9 shows a flow chart of another method for notifying the arrival of user plane data in an embodiment of the present disclosure
  • FIG10 is a schematic diagram showing a threshold determination process before sending a message within the second base station in an embodiment of the present disclosure
  • FIG11 shows a schematic diagram of a base station control plane entity of a separated architecture base station in an embodiment of the present disclosure
  • FIG12 shows a schematic diagram of a base station user plane entity of a separated architecture base station in an embodiment of the present disclosure
  • FIG. 13 shows a structural block diagram of an electronic device in an embodiment of the present disclosure.
  • the Release 18 is mainly a process triggered by the SDT service 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 the downlink SDT is supported according to the current SDT process of Release 17, there is a problem that the user plane entity (CU-UP) cannot distinguish whether it is the Rel-17 uplink SDT or the Rel-18 downlink SDT.
  • CU-UP user plane entity
  • the present application discloses a notification method and related equipment for the arrival of user plane data, which can support the configuration of a downlink SDT bearer in a base station control plane and user plane separation architecture, and support the process of providing auxiliary information to the control plane entity when a 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.
  • CU-UP user plane entity
  • 5G has technical features such as supporting large bandwidth, large connection, low latency, and wireless cloudification.
  • CU Centralized Unit
  • DU Distributed Unit
  • CP and UP have been supported since Rel-15, as shown in Figure 1.
  • CU devices mainly include non-real-time wireless high-level protocol stack functions, and also support the sinking 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.
  • DU devices mainly handle physical layer functions and layer 2 functions with real-time requirements.
  • CP control plane
  • UP user plane
  • the separated CP and UP are decoupled from each other, interact through the standard E1 interface, and can be deployed on different physical nodes.
  • the control plane entity Due to the separation of the control plane and the user plane, when the user plane entity receives a data packet from the core, it needs to notify the control plane entity through the signaling shown in Figure 2. Currently, this signaling is only used to notify that a data packet has arrived and In addition, whenever a user's bearer or context needs to be established or modified, the CU-CP can notify the user plane through the signaling shown in FIG. 3 .
  • 5G introduces an inactive state, namely the "RRC_INACTIVE" 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.
  • the SuspendConfig can be carried in the RRCRelease message. The introduction of this state is used to solve the transmission of small data packets and reduce the signaling overhead of the core network.
  • the UE 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 the RRC connection recovery, the UE ensures that there is valid and up-to-date system information.
  • 3GPP Rel-17 introduces SDT for uplink and defines related processes.
  • CU-CP can configure which bearers are SDT bearers for CU-UP through Bearer Context Modification message or Bearer Context Setup message.
  • Release 18 is mainly a process triggered by the small data packet transmission service in the downlink direction, that is, the process of sending small data packets in the idle state after receiving data packets from the core network. If the downlink SDT is supported according to the current SDT process of Release 17, the following problems will occur:
  • CU-UP is not clear about 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 whether it is Rel-17 uplink SDT or Rel-18 downlink SDT from the bearer level. CU-UP will treat the uplink SDT of Release 17 and the downlink SDT based on Release 18 differently. Considering that the downlink SDT of Rel-18 is compatible with the uplink SDT of Rel-17, CU-UP cannot distinguish which type it is in the current design process.
  • CU-CP is not clear about the amount of downlink SDT data received by CU-UP and the calculation method: the current DL Data Notification message of the E1 interface does not contain any SDT indication information, so CU-CP does not know whether there is a downlink SDT data packet arriving and whether it is below the data threshold.
  • the data 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;
  • the current 3GPP Rel-17 protocol cannot meet the design requirements of downlink small data packets in the separation architecture, and new methods are needed to enhance the functions to meet network deployment and optimization. demand.
  • the present invention supports the transmission of small data packets caused by the arrival of downlink data in a separated architecture.
  • the present invention 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.
  • CU-UP user plane entity
  • 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, comprising: 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 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 receipt of downlink data of the terminal, the second base station message including the size 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 from the base station user plane entity is received, terminating the transmission process of the downlink small data packet, the new second base station
  • FIG4 shows a schematic diagram of a separation architecture base station in an embodiment of the present disclosure.
  • the separation architecture base station provided in the embodiment of the present disclosure includes a base station separation entity 410 and a base station centralized entity 420 .
  • 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 includes configuring at least one DRB as an SDT bearer, and indication information on 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 is used to notify the base station control plane entity that the terminal downlink data is received, the second base station message includes the downlink data volume 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 at least includes downlink SDT indication information, and the RRC paging message includes at least downlink SDT indication information.
  • 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 configured as uplink SDT only.
  • 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.
  • the base station control plane entity 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.
  • the downlink small data packet sending trigger threshold 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.
  • FIG5 shows a flow chart of a method for notifying the arrival of user plane data in an embodiment of the present disclosure.
  • the method for notifying the arrival of user plane data provided in an embodiment of the present disclosure includes steps S502 - S506 .
  • the base station control plane entity sends a first base station internal request message to the base station user plane entity, where 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.
  • 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.
  • 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.
  • the base station control plane entity instructs the base station user plane entity to configure the SDT bearer list through a first base station internal request message, and may configure the SDT bearer mode.
  • the SDT bearer list indicates that one or more DRBs support both downlink small data packet transmission and uplink small data packet transmission.
  • the SDT bearer mode includes the MT-SDT mode, which can be used to support downlink small data packet transmission and/or uplink small data packet transmission.
  • the base station user plane entity 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 according to the SDT bearer list, and determines that all SDT bearers support downlink small data packet transmission according to the SDT bearer mode. When the SDT bearer mode is not carried, all SDT bearers only support uplink small data packets. After the configuration is completed, the configuration result is fed back to the base station control plane entity.
  • 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 is received, and 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.
  • the base station user plane entity 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, where the data volume is the size of the data packet after adding the SDAP header. If small data packets of the terminal are received from the core network before the timer expires, these small data packets continue to be cached and the total data volume of the small data packets is accumulated.
  • the base station user plane entity After the timer expires, the base station user plane entity notifies the base station control plane entity through a second base station internal message, wherein the second base station internal message also includes the cached downlink SDT data packet size.
  • the downlink SDT data packet is a small downlink data packet carried by the SDT.
  • 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
  • the base station user plane entity receives an SDT data packet of the terminal (i.e., a small downlink data packet carried by SDT) again
  • the base station user plane entity continues 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 does not carry the cached downlink SDT data packet size.
  • 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 the downlink SDT indication information.
  • a first paging message is sent to the base station separation entity, 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.
  • FIG7 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 FIG7 , steps S702 - S706 of the method are similar to steps S502 - S506 of the above embodiment and are not described again.
  • 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.
  • the base station control plane entity After receiving the message within the second base station or receiving the high-level signaling message sent from the core network to the user, if the base station control plane entity only receives the high-level signaling message sent from the core network, it directly sends the first paging message to The base station separation entity and/or sends a second paging message to an adjacent second base station (i.e., a neighboring base station); if a message is received from the second base station, it determines whether the size of the indicated cached downlink SDT data packet meets the downlink small data packet sending trigger threshold, and when it is less than the trigger threshold, 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.
  • the auxiliary information is carried to indicate the MT-SDT paging and the first RRC message, and the first RRC message includes the MT-SDT indication information.
  • the base station control plane entity sends a second paging message to the second base station via the Xn interface, the second paging message including at least one of MT-SDT indication information, 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.
  • FIG8 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.
  • the method for notifying the arrival of user plane data provided in an embodiment of the present disclosure includes steps S802-S806.
  • a first base station internal request message is sent to a base station user plane entity, where 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 response message is received from the first base station, confirming the establishment of the requested configuration bearer.
  • 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.
  • 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 configured as uplink SDT only.
  • a second base station message is received from the base station user plane entity, where the second base station message is used to notify the base station control plane entity that the terminal downlink data has been received, and the second base station message includes the size of the downlink data carried by all SDTs of the terminal cached in the base station user plane entity.
  • 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.
  • a first paging message is sent to the base station separation entity, 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.
  • the method further includes 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; wherein the second auxiliary information includes at least one of the following information:
  • the size of the cached downlink data volume and downlink SDT indication information of all SDT bearers cached in the user plane entity of the base station is the size of the cached downlink data volume and downlink SDT indication information of all SDT bearers cached in the user plane entity of the base station.
  • the method 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 a neighboring base station.
  • the base station control plane entity sends a second paging message to a neighboring base station through an Xn interface, and the RRC paging message included in the second paging message includes at least downlink SDT indication information.
  • the value of the downlink small data packet sending threshold can be configured by a network manager.
  • 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 does not carry the size of the cached downlink data carried by all SDTs cached in the base station user plane entity.
  • 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.
  • This embodiment mainly describes the process in which the base station control plane entity gNB-CU-CP configures the SDT bearer using Rel-18 SDT for the base station user plane entity gNB-CU-UP, and the process in which the base station user plane entity receives a separate small data packet, triggers the arrival of downlink data, and continues to trigger the arrival of downlink data after receiving a downlink data packet from the core network again after sending it.
  • the gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP, in which DRB#1 and DRB#2 carried in PDU Session#1 are set as SDT bearers, and an indication is included to configure all SDT bearer modes as MO-SDT of Rel-18.
  • the specific information element configuration of BEARER CONTEXT MODIFICATION REQUEST is shown in the following table:
  • the information elements in the PDU Session Resource To Modify List are as follows:
  • gNB-CU-UP After receiving the message, gNB-CU-UP configures DRB#1 and DRB#2 as SDT bearers, configures MT-SDT mode, and feeds back BEARER CONTEXT MODIFICATION RESPONSE.
  • gNB-CU-UP After receiving the data packets sent by the core network SMF, gNB-CU-UP determines that the DRB to which these data packets belong belongs to the SDT bearer in the buffer cached after SDAP processing, calculates the byte size including the SDAP header to be 340kbytes, and starts the timing with a time of 20ms.
  • a DL DATA NOTIFICATION message is sent to the gNB-CU-CP.
  • the specific information element is:
  • gNB-CU-CP After receiving the DL DATA NOTIFICATION message, gNB-CU-CP checks that it carries the DL SDT Buffer Size and compares it with the set threshold of 800kbytes to determine whether to trigger MT-SDT-based paging.
  • the gNB-CU-CP generates a paging message based on MT-SDT, where the paging message carries one-bit indication information MT-SDT indication.
  • gNB-CU-UP After receiving the data packet from the core network, gNB-CU-UP finds that it is still an SDT small data packet and stops sending the DL DATA NOTIFICATION message to gNB-CU-CP.
  • FIG. 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 in a separated architecture. As shown in FIG9 , the method for notifying the arrival of user plane data provided in the embodiment of the present disclosure includes steps S902-S906.
  • a first base station request message sent by a base station control plane entity is received, the first 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.
  • configuration may include reconfiguration (ie, modification) or new creation.
  • the indication information of whether downlink SDT is supported is indicated by whether the SDT bearer request mode is carried to indicate whether both downlink SDT and uplink SDT are supported simultaneously; the SDT bearer request mode indicates that all SDT DRBs support both downlink SDT and uplink SDT simultaneously. When the SDT bearer request mode is not carried, it indicates that all SDT DRBs are configured as uplink SDT only.
  • the relevant DRB is configured as an SDT DRB according to the instruction; 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.
  • a second base station internal message is sent to the base station control plane entity, and 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.
  • the method shown in Figure 9 also includes: if a small downlink data packet carried by a terminal other than 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.
  • sending a second base station internal message to the base station control plane entity includes:
  • DRB supports both downlink SDT and uplink SDT.
  • 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 cached small data packets.
  • the method when all downlink small data packets belong to the SDT bearer, the method further includes:
  • the timer is configured by the network management
  • the small data packets are buffered and the total data volume of the small data packets is accumulated;
  • a second base station internal message is sent to the base station control plane entity, where the second base station internal message includes the total data volume of the buffered small data packets.
  • 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.
  • 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 the user plane in understanding the downlink SDT trigger.
  • the method further includes:
  • a new second base station internal message is continuously sent to the base station control plane entity, where the new second base station internal message includes the cache quantity of the downlink SDT bearer newly cached in the base station user plane entity;
  • 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 downlink SDT data packet size.
  • 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.
  • 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, standing at a base station control plane entity.
  • 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 separate small data packet and triggers the arrival of downlink data.
  • the gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP.
  • the message sets DRB#1 and DRB#2 in PDU Session#1 as SDT bearers and includes an indication for configuring all SDT bearer modes to MO-SDT (uplink SDT) of Rel-18.
  • MO-SDT uplink SDT
  • the information elements in the PDU Session Resource To Modify List are as follows:
  • gNB-CU-UP After receiving the data, gNB-CU-UP configures DRB#1 and DRB#2 as SDT bearers and configures MT-SDT (downlink SDT) mode, feedback BEARER CONTEXT MODIFICATION RESPONSE.
  • gNB-CU-UP After receiving the data packets sent by the core network SMF, gNB-CU-UP determines that the DRB to which these data packets belong belongs to the SDT bearer in the buffer cached after SDAP processing, calculates the byte size including the SDAP header to be 340kbytes, and starts the timing with a time of 20ms.
  • a DL DATA NOTIFICATION message is sent to the gNB-CU-CP.
  • the specific information element is:
  • the gNB-CU-CP After receiving the DL DATA NOTIFICATION message, the gNB-CU-CP detects that it carries the DL SDT Buffer Size and compares it with the set threshold of 800 kbytes to determine whether to trigger MT-SDT-based paging.
  • the gNB-CU-CP generates a paging message based on MT-SDT, where the paging message carries one-bit indication information MT-SDT indication.
  • the gNB-CU-CP mainly sends configuration information to the gNB-DU to allow the UE to maintain the uplink CG-SDT resources in the idle state as the feedback information of the downlink SDT. After the terminal feeds back the uplink RRC Resume Request message, it triggers the SDT bearer recovery and downlink data sending process.
  • the gNB-CU-CP determines that the terminal needs to enter the inactive state, it determines that the terminal can use CG-SDT resources as a response for downlink small data packet transmission based on the user's movement speed and service characteristics, and sends a UE CONTEXT RELEASE COMMAND to the gNB-DU.
  • the specific information elements are as follows:
  • the RRC Release message includes the following:
  • the UE After receiving the gNB-DU, it determines that the UE uses the uplink CG-SDT resources as the downlink SDT response based on the CG-SDT Kept Indicator and the MT-SDT indicator, and 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.
  • gNB-DU sends the RRC Release message carried in the UE CONTEXT RELEASE COMMAND to the UE.
  • gNB-DU After gNB-DU receives the RRC Resume message sent by UE on CG-SDT, it sends the RRC MESSAGE TRANSFER through INITIAL UL.
  • 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.
  • a and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone.
  • the character "/" in this article generally indicates that the associated objects before and after are in an "or" relationship.
  • certain steps may be omitted, multiple steps may be combined into one step, and/or one step may be decomposed into multiple steps.
  • the disclosed embodiment also provides a base station control plane entity of a separated architecture base station, as described in the following embodiment. Since the principle of solving the problem in the entity embodiment is similar to that in the above method embodiment, the implementation of the entity embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.
  • FIG. 11 shows a base station control plane entity of a separated architecture base station in an embodiment of the present disclosure.
  • the base station control plane entity 1100 of the separated architecture base station includes:
  • the message sending module 1102 is configured to send a first base station internal request message to a base station user plane entity, where 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;
  • the second receiving module 1104 is used to receive a response message from the first base station to confirm the establishment of the requested configuration bearer
  • the notification receiving module 1106 is used to receive a second base station message from the base station user plane entity, where the second base station message is used to notify the base station control plane entity that the downlink data of the terminal has been received, and the second base station message includes the downlink data volume of all SDT bearers of the terminal cached in the base station user plane entity;
  • 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, and the RRC paging message at least includes downlink SDT indication information.
  • the base station control plane entity 1100 further includes a transmission termination module.
  • the transmission termination module is used to terminate the transmission process of the downlink small data packet if a new second base station internal message is received from the base station user plane entity, and the new second base station internal message is used to notify the base station control plane entity that a downlink small data packet of a non-SDT bearer of the terminal is received, and the new second base station internal message does not carry the size of the downlink data packet of the cached SDT bearer.
  • 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.
  • 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 is not carried, it indicates that all SDT DRBs are configured as uplink SDT only.
  • the base station control plane entity 1100 of the split architecture base station further includes:
  • a second paging module configured to send a second paging message including second auxiliary information to a neighboring base station, wherein the second paging message 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 and downlink SDT indication information of all SDT bearers cached in the user plane entity of the base station is the size of the cached downlink data volume and downlink SDT indication information of all SDT bearers cached in the user plane entity of the base station.
  • 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.
  • the paging sending module 1108 is used to send a second paging message to a neighboring base station through an Xn interface, and the RRC paging message included in the second paging message includes at least downlink SDT indication information.
  • the value of the downlink small data packet sending threshold is configured by a network management.
  • the paging sending module 1108 is used to receive a high-level signaling message sent from the core network. If the base station has a user plane entity, the first paging message is directly sent to the base station separation entity and/or the second paging message is sent to the neighboring base station; the second paging message directly sent to the neighboring base station does not carry the size of the cached downlink data volume of all SDT bearers cached in the base station user plane entity.
  • an embodiment of the present disclosure further provides a base station user plane entity of a separated architecture base station.
  • the base station user plane entity 1200 of the separated architecture base station includes:
  • the message receiving module 1202 is configured to receive a first base station request message sent by a base station control plane entity, where the first 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;
  • the message response module 1204 is 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 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, and 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.
  • 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.
  • 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
  • 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.
  • 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 a message within the second base station, otherwise the data volume of the downlink SDT bearer is not counted; and a response message is sent to the base station control plane entity.
  • the notification sending module 1206 is used to receive a downlink small data packet from a terminal in the core network, cache it 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 the cached downlink small data packets of all SDT bearers of the user terminal.
  • the notification sending module 1206 is used to notify that all downlink small data packets belong to the SDT bearer.
  • the timer is started according to the configuration, and the timer is configured by the network management; before the timer expires, if only the downlink SDT bearer small data packets of the terminal continue to be received, the small data packets continue to be cached, and the total data volume of the small data packets is 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.
  • counting the data volume of the small data packet is counting the size of the data packet after adding the SDAP header.
  • the notification sending module 1206 is used to continue to send 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.
  • the electronic device provided by the embodiment of the present disclosure is described below with reference to Fig. 13.
  • the electronic device 1300 shown in Fig. 13 is only an example and should not bring any limitation to the functions and application scope of the embodiment of the present disclosure.
  • FIG13 is a schematic diagram showing 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 .
  • the memory 1320 is used to store instructions.
  • 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 .
  • RAM random access memory unit
  • ROM read-only memory unit
  • 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.
  • 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.
  • the memory 1320 may store an operating system.
  • the operating system may be a real-time operating system (RTX), LINUX, UNIX, WINDOWS, or OS X.
  • RTX real-time operating system
  • LINUX LINUX
  • UNIX UNIX
  • WINDOWS WINDOWS
  • OS X OS X
  • data may also be stored in the memory 1320 .
  • the processor 1310 may read data stored in the memory 1320 , where 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.
  • the processor 1310 is configured to call the instructions stored in the memory 1320 to implement the steps of various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification.
  • the processor 1310 may execute the steps of the above method embodiment.
  • processor 1310 may be a general-purpose processor or a special-purpose 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.
  • processor 1310 may include a central processing unit (CPU) and/or a baseband processor.
  • CPU central processing unit
  • baseband processor a baseband processor
  • the processor 1310 may determine an instruction according to the priority identifier and/or function category information carried in each control instruction.
  • processor 1310 and the memory 1320 may be provided separately or integrated together.
  • the processor 1310 and the memory 1320 can be integrated on a single board or a system on chip (SOC).
  • SOC system on chip
  • the electronic device 1300 is in the form of a general-purpose computing device.
  • the electronic device 1300 may further include a bus 1330 .
  • 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 any combination of bus structures using a variety of bus structures.
  • the local bus of the structure 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 any combination of bus structures using a variety of bus structures.
  • the local bus of the structure 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 any combination of bus structures using a variety of bus structures.
  • the electronic device 1300 may also communicate with one or more external devices 1340 (e.g., keyboards, pointing devices, Bluetooth devices, 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., routers, modems, etc.). Such communication may be performed through an input/output (I/O) interface 1350.
  • I/O input/output
  • 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 .
  • networks eg, a local area network (LAN), a wide area network (WAN) and/or a public network, such as the Internet
  • LAN local area network
  • WAN wide area network
  • Internet public network
  • the network adapter 1360 communicates with other modules of the electronic device 1300 via the bus 1330 .
  • the structure illustrated in the embodiment of the present disclosure does not constitute a specific limitation on the electronic device 1300.
  • the electronic device 1300 may include more or fewer components than those shown in FIG. 13, or combine certain components, or separate certain components, or arrange the components differently.
  • the components shown in FIG. 13 may be implemented in hardware, software, or a combination of software and hardware.
  • the present disclosure also provides a computer-readable storage medium on which computer instructions are stored.
  • 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.
  • 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.
  • computer readable storage media are non-volatile storage media.
  • 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.
  • the computer-readable storage medium may include a data signal propagated in a baseband or as a part of a carrier wave, in which computer instructions (readable program codes) are carried.
  • Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • 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.
  • the embodiment of the present disclosure further provides a computer program product, which stores instructions.
  • the 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.
  • the above instructions may be program codes.
  • the program codes may be written in any combination of one or more programming languages.
  • the programming language includes object-oriented programming languages, such as Java, C++, etc., and also includes conventional procedural programming languages, such as "C" language or similar programming languages.
  • 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.
  • 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).
  • LAN local area network
  • WAN wide area network
  • the embodiment of the present disclosure also provides a chip, including at least one processor and an interface;
  • At least one processor is used to execute program instructions to implement the method for notifying the arrival of user plane data described in the above method embodiment.
  • the chip may further include a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种用户面数据到达的通知方法及相关设备，涉及无线通信技术领域。该方法包括：向基站用户面实体发送第一基站内请求消息，第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；接收到第一基站内响应消息，确认请求配置承载的建立情况；接收来自基站用户面实体的第二基站内消息，第二基站内消息用于通知基站控制面实体接收到终端下行数据，第二基站内消息中包括缓存在基站用户面实体中的终端所有SDT承载的下行数据量大小；向基站分离实体发送包含发送给终端的RRC寻呼消息和第一辅助信息的第一寻呼消息。

Description

用户面数据到达的通知方法及相关设备
相关申请的交叉引用
本申请是以CN申请号为202310574049.7，申请日为2023年5月19日的申请为基础，并主张其优先权，该CN申请的公开内容在此作为整体引入本申请中。
技术领域
本公开涉及无线通信技术领域，尤其涉及一种用户面数据到达的通知方法及相关设备。
背景技术
5G(5th Generation Mobile Communication Technology，第五代移动通信技术)作为下一代无线网络的主要技术，具有支持超宽带、大连接等技术特征。相比于4G(4th Generation Mobile Communication Technology，第四代移动通信技术)，5G中引入了非激活状态(RRC_INACTIVE)，该状态基站/UE可以选择保持不活动状态，而无需在没有业务数据传输时完全释放RRC(Radio Resource Control，无线资源控制)建立的承载，可在RRC Release消息中携带SuspendConfig。该状态的引入用于解决小数据包的发送，降低核心网的信令开销。
在3GPP Rel-17中引入了针对上行方向的SDT(Small data transmission，小数据包传输)并定义了相关的流程，但与Release17中的上行SDT不同的是，Release 18中主要是针对下行方向的SDT业务所触发的相关过程，即收到来自核心网的数据包后，在空闲态发送小数据包的过程。如果按照目前Release 17的SDT过程，支持下行SDT，那么将存在用户面实体(CU-UP)无法区分是Rel-17上行SDT还是Rel-18的下行SDT的问题，也就是说，目前的3GPPRel-17的协议都无法满足下行小数据包在分离架构中的设计需求，需要进行增强功能，以满足网络部署和优化的需求。
需要说明的是，在上述背景技术部分公开的信息仅用于加强对本公开的背景的理解，因此可以包括不构成对本领域普通技术人员已知的现有技术的信息。
发明内容
根据本公开的第一方面，提供了一种用户面数据到达的通知方法，应用于分离架 构基站的基站控制面实体，方法包括：
向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
接收到第一基站内响应消息，确认请求配置承载的建立情况；
接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一寻呼消息还包括发送给终端的RRC寻呼消息，所述第一辅助信息至少包括下行SDT指示信息，所述RRC寻呼消息中至少包括下行SDT指示信息。
根据本公开的第二方面，提供了一种用户面数据到达的通知方法，应用于分离架构基站的基站控制面实体，方法包括：
向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
接收到第一基站内响应消息，确认请求配置承载的建立情况；
接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一辅助信息至少包括下行SDT指示信息；
若接收到来自基站用户面实体的新的第二基站内消息，则终止下行小数据包的传输过程，所述新的第二基站内消息用于通知基站控制面实体接收到终端的非SDT承载的下行小数据包，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
在本公开的一些实施例中，所述第一基站内请求消息，包括SDT承载列表，所述SDT承载列表用于指示基站用户面实体为所述终端重新配置或者新建一个或者多个DRB为SDT承载。
在本公开的一些实施例中，是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否同时支持下行；SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有 SDT DRB为上行SDT。
在本公开的一些实施例中，方法还包括：
向邻基站发送包含第二辅助信息的第二寻呼消息；
其中，第二寻呼消息中包含发送给终端的RRC寻呼消息；第二辅助信息，还包括如下信息中的至少一个：
缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小、下行SDT指示信息。
在本公开的一些实施例中，在接收到来自基站用户面实体的第二基站内消息的情况下，方法还包括：
判断基站用户面实体中缓存的SDT承载的下行数据量大小是否小于下行小数据包发送触发门限；
在小于下行小数据包发送触发门限的情况下，则发送第一寻呼消息给所述基站分离实体和发送第二寻呼消息给邻基站。
在本公开的一些实施例中，所述基站控制面实体通过Xn接口向邻基站发送第二寻呼消息，所述第二寻呼消息中包含的RRC寻呼消息中至少包括下行SDT指示信息。
在本公开的一些实施例中，若收到来自核心网发送的高层信令消息且同时未收到基站用户面实体的第二基站内消息时，则直接发送第一寻呼消息给所述基站分离实体和/或发送第二寻呼消息给邻基站；直接发送给邻基站的所述第二寻呼消息中不携带缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小。
根据本公开的第三方面，提供一种用户面数据到达的通知方法，应用于分离架构基站的基站用户面实体，方法包括：
接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
响应所述第一基站内请求消息，确认请求配置承载的建立情况；
在终端的SDT承载的下行数据到达后，向所述基站控制面实体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小。
根据本公开的第四方面，提供一种用户面数据到达的通知方法，应用于分离架构基站的基站用户面实体，方法包括：
接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括 配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
响应所述第一基站内请求消息，确认请求配置承载的建立情况；
在终端的SDT承载的下行数据到达后，向所述基站控制面实体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小；
若接收到所述终端的非SDT承载的下行小数据包，则向所述基站控制面实体发送新的第二基站内消息，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
在本公开的一些实施例中，所述是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否支持下行SDT；所述SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
在本公开的一些实施例中，响应所述第一基站内请求消息，确认请求配置承载的建立情况，包括：根据指示配置相关DRB为SDT DRB；当SDT承载请求模式携带时，统计下行SDT承载的数据量大小，并通过第二基站内消息发送给基站控制面实体，否则不统计下行SDT承载的数据量大小；将响应消息发送给基站控制面实体。
在本公开的一些实施例中，当终端的SDT承载下行数据到达后，向所述基站控制面实体发送第二基站内消息，包括：接收来自核心网的终端的下行小数据包，添加SDAP包头后缓存；判断所述下行小数据包所对应的DRB是否全部属于所述基站用户面实体配置的SDT DRB；在所述下行小数据包全部属于SDT承载的情况下，统计小数据包的数据量大小；判断是否配置了SDT承载请求模式；向所述基站控制面实体发送第二基站内消息，所述第二基站内消息包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小。
在本公开的一些实施例中，在所述下行小数据包全部属于SDT承载的情况下，所述方法还包括：根据配置启动定时器，所述定时器由网管进行配置；在定时器超时前若继续仅收到所述终端的SDT承载的下行小数据包，则继续缓存所述下行小数据包，并累计所述下行小数据包的总数据量大小；在定时器超时后，则向所述基站控制面实体发送所述第二基站内消息。
在本公开的一些实施例中，所述统计小数据包的数据量为统计增加SDAP头部后的数据包大小。
在本公开的一些实施例中，在向所述基站控制面实体发送第二基站内消息后，且未收到来自所述基站控制面实体发送的用户上下文修改消息时，所述方法还包括：若再接收到的所述终端的SDT承载的下行小数据包，则继续向所述基站控制面实体发送新的第二基站内消息，所述新的第二基站内消息中包括新缓存在所述基站用户面实体中的SDT承载的下行数据量；若再接收到非SDT承载的下行小数据包，则继续向所述基站控制面实体发送新的第二基站内消息，且所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
在不冲突的情况下，本公开的基站控制面实体中的实施例和实施例中的特征可以应用到基站用户面实体中，反之亦然。
在不冲突的情况下，本公开的实施例和实施例中的特征可以任意相互组合。
根据本公开的第五方面，提供一种分离架构基站的基站控制面实体，包括：
消息发送模块，用于向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
第二接收模块，用于接收到第一基站内响应消息，确认请求配置承载的建立情况；
通知接收模块，用于接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
寻呼发送模块，用于向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一寻呼消息还包括发送给终端的RRC寻呼消息，所述第一辅助信息至少包括下行SDT指示信息，所述RRC寻呼消息中至少包括下行SDT指示信息。
根据本公开的第六方面，提供一种分离架构基站的基站控制面实体，包括：
消息发送模块，用于向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
第二接收模块，用于接收到第一基站内响应消息，确认请求配置承载的建立情况；
通知接收模块，用于接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
寻呼发送模块，用于向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一寻呼消息还包括发送给终端的RRC寻呼消息，所述第一辅助信息至少包括下行SDT指示信息，所述RRC寻呼消息中至少包括下行SDT指示信息；
终止传输模块，用于若接收到来自基站用户面实体的新的第二基站内消息，则终止下行小数据包的传输过程，所述新的第二基站内消息用于通知基站控制面实体接收到终端的非SDT承载的下行小数据包，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
根据本公开的第七方面，提供一种分离架构基站的基站用户面实体，包括：
消息接收模块，用于接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
消息响应模块，用于响应所述第一基站内请求消息，确认请求配置承载的建立情况；
通知发送模块，用于在终端的SDT承载的下行数据到达后，向所述基站控制面实体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小。
根据本公开的第八方面，提供一种分离架构基站的基站用户面实体，包括：
消息接收模块，用于接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
消息响应模块，用于响应所述第一基站内请求消息，确认请求配置承载的建立情况；
通知发送模块，用于在终端的SDT承载的下行数据到达后，向所述基站控制面实体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小；以及用于若接收到所述终端的非SDT承载的下行小数据包，则向所述基站控制面实体发送新的第二基站内消息，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
根据本公开的第九方面，提供一种分离架构基站，包括基站集中实体和基站分离实体；基站集中实体包括基站控制面实体和基站用户面实体；基站控制面实体用于实现如第一方面或第二方面所述的用户面数据到达的通知方法。
根据本公开的第十方面，提供一种电子设备，包括：存储器，用于存储指令；处理器，用于调用所述存储器中存储的指令，实现上述的用户面数据到达的通知方法。
根据本公开的第十一方面，提供一种计算机可读存储介质，其上存储有计算机指 令，所述计算机指令被处理器执行时实现上述的用户面数据到达的通知方法。
根据本公开的第十二方面，提供一种计算机程序产品，计算机程序产品存储有指令，所述指令在由计算机执行时，使得计算机实施上述的用户面数据到达的通知方法。
根据本公开的第十三方面，提供一种芯片，包括至少一个处理器和接口；
接口，用于为至少一个处理器提供程序指令或者数据；
至少一个处理器用于执行程序指令，以实现上述的用户面数据到达的通知方法。
本公开实施例所提供的用户面数据到达的通知方法及相关设备，支持在基站控制面和用户面分离架构中配置基于下行SDT承载，以及支持下行数据包到达时向控制面实体提供辅助信息的过程，从而使得用户面实体(CU-UP)能够区分Rel-17上行SDT和Rel-18的下行SDT，并且能够减少基站控制面和基站用户面之间的互操作问题，支持在控制面和用户面分离架构中发送小数据包的过程。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出本公开实施例中一种CU/DU分离的5G基站的架构示意图；
图2示出相关技术中一种用户面数据到达的通知过程示意图；
图3示出相关技术中一种控制面通知用户面的流程示意图；
图4示出Release 17针对上行的SDT信令过程图；
图5示出本公开实施例中一种分离架构基站的结构示意图；
图6示出本公开实施例中一种用户面数据到达的通知方法流程图；
图7示出本公开实施例中另一种用户面数据到达的通知方法流程图；
图8示出本公开实施例中又一种用户面数据到达的通知方法流程图；
图9示出本公开实施例中再一种用户面数据到达的通知方法流程图；
图10示出本公开实施例中发送第二基站内消息前门限判断过程示意图；
图11示出本公开实施例中一种分离架构基站的基站控制面实体示意图；
图12示出本公开实施例中一种分离架构基站的基站用户面实体示意图；
图13示出本公开实施例中一种电子设备的结构框图。
具体实施方式
下面将参考附图更全面地描述示例实施方式。
需要说明的是，示例实施方式能够以多种形式实施，不应被理解为限于在此阐述的范例。
发明人通过研究发现，与Release17中的上行SDT不同的是，Release 18中主要是针对下行方向的SDT业务所触发的相关过程，即收到来自核心网的数据包后，在空闲态发送小数据包的过程。如果按照目前Release 17的SDT过程，支持下行SDT，则存在用户面实体(CU-UP)无法区分是Rel-17上行SDT还是Rel-18的下行SDT的问题。
针对上述问题，本申请公开了一种用户面数据到达的通知方法及相关设备，可以支持在基站控制面和用户面分离架构中配置基于下行SDT承载，以及支持下行数据包到达时向控制面实体提供辅助信息的过程，从而使得用户面实体(CU-UP)能够区分Rel-17上行SDT和Rel-18的下行SDT，并且能够减少基站控制面和基站用户面之间的互操作问题，支持在控制面和用户面分离架构中发送小数据包的过程。
本公开的其他特性和优点将通过下面的详细描述变得显然，或部分地通过本公开的实践而习得。
5G作为新一代无线网络技术，具有支持大宽带、大连接、低时延、无线云化等技术特征。其中在支持无线云化方面，从Rel-15开始就支持了CU(Centralized Unit)和DU(Distributed Unit)分离，以及CP和UP分离的架构设计，如图1所示。
CU与DU功能的切分以处理内容的实时性进行区分。CU设备主要包括非实时的无线高层协议栈功能，同时也支持部分核心网功能下沉和边缘应用业务的部署，而DU设备主要处理物理层功能和实时性需求的层2功能。在CU/DU分离的基础上，为了进一步适配不同业务的请求。接入网的CU侧，还可以更进一步地将控制面(CP)和用户面(UP)再行分离。分离后的CP和UP彼此解耦，通过标准的E1接口进行交互，可部署在不同的物理节点。
由于控制面和用户面的相互分离，当在用户面实体收到来自核心的数据包时，需要通过如图2所示的信令通知控制面实体，目前该信令仅用于通知有数据包达到，并 不区分是何种业务。此外任何当用户的承载或者上下文需要进行建立或者修改时，CU-CP可通过如图3所示的信令通知用户面。
在低时延方面，相比于4G，5G中引入了非激活状态，即“RRC_INACTIVE”状态，该状态基站/UE可以选择保持不活动状态，而无需在没有业务数据传输时完全释放RRC建立的承载，可在RRCRelease消息中携带SuspendConfig。该状态的引入用于解决小数据包的发送，降低核心网的信令开销。当UE处于RRC_INACTIVE状态，当终端收到RAN寻呼或者RNA更新或者有上行数据要发送，都会触发挂起的RRC连接恢复，在发起RRC连接恢复之前，UE确保有有效的、最新的系统信息。
在3GPP Rel-17中引入了针对上行方向的SDT并定义了相关的流程。其中在E1接口中，通过Bearer Context Modification消息或者Bearer Context Setup消息，CU-CP可以为CU-UP配置哪些承载是SDT承载。
发明人发现，与Release17中的上行SDT不同的是，Release 18中主要是针对下行方向的小数据包传输业务所触发的相关过程，即收到来自核心网的数据包后，在空闲态发送小数据包的过程。如果按照目前Release 17的SDT过程，支持下行SDT，则存在如下问题：
CU-UP不清楚Rel-17SDT和Rel-18的SDT差别：由于承载本身包括了上行和下行两个部分，因此从承载层面无法区分是Rel-17上行SDT还是Rel-18的下行SDT，CU-UP对待Release 17的上行SDT和基于Release18的下行SDT的行为会有所不同，考虑到此外Rel-18的下行SDT可以兼容Rel-17的上行SDT，当前的设计过程中CU-UP无法区分是哪种类型。
CU-CP不清楚CU-UP接收到的下行SDT数据量以及计算方法：目前的E1接口的DL Data Notification消息里并不包含任何的SDT指示信息，因此CU-CP并不知道是否有下行SDT数据包到达以及是否低于数据门限，此外在上行SDT过程中采用的数据包触发门限都是来源于MAC层的字段大小，而此时如果采用之前方法，考虑到后续的分段和重传则无法准确计算，并且基站的用户面实体；
多数据包到达时CU-CP和CU-UP存在互操作问题：当多个下行数据包间隔到达且第一个数据包尚未完全触发SDT过程时未明确用户面的处理行为，可能出现仅发送一次下行数据到达，多次达到以及取消SDT数据指示等情况，因此存在互操作的问题。
基于上述需求和原因分析，目前的3GPPRel-17的协议都无法满足下行小数据包在分离架构中的设计需求，需要通过新的方式来进行增强功能，以满足网络部署和优 化的需求。
基于发明人的上述发现，支持在分离架构中下行方向数据到达而引发的小数据包传输，本公开提供了一种用户面数据到达的通知方法及相关设备，使得用户面实体(CU-UP)能够区分Rel-17上行SDT和Rel-18的下行SDT。
根据本公开一些实施例，提供了一种用户面数据到达的通知方法，应用于分离架构基站的基站控制面实体，包括：向基站用户面实体发送第一基站内请求消息，第一基站内请求消息包括配置至少一个DRB为SDT承载以及是否支持下行SDT的指示信息；接收到第一基站内响应消息，确认请求配置承载的建立情况；接收来自基站用户面实体的第二基站内消息，第二基站内消息用于通知基站控制面实体接收到终端的下行数据，第二基站内消息中包括缓存在基站用户面实体中的终端所有SDT承载的下行数据量大小；向基站分离实体发送包含第一辅助信息的第一寻呼消息，第一辅助信息至少包括下行SDT指示信息；若接收到来自基站用户面实体的新的第二基站内消息，则终止下行小数据包的传输过程，新的第二基站内消息用于通知基站控制面实体接收到终端的非SDT承载的下行小数据包，新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
图4示出本公开实施例中一种分离架构基站示意图，如图4所示，本公开实施例中提供的分离架构基站，包括基站分离实体410和基站集中实体420。
基站集中实体420包括基站控制面实体421和基站用户面实体422，其中，基站控制面实体421用于向基站用户面实体发送第一基站内请求消息，第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；接收到第一基站内响应消息，确认请求配置承载的建立情况；接收来自基站用户面实体的第二基站内消息，第二基站内消息用于通知基站控制面实体接收到终端下行数据，第二基站内消息中包括缓存在基站用户面实体中的终端所有SDT承载的下行数据量大小；向基站分离实体发送包含发送给终端的RRC寻呼消息和第一辅助信息的第一寻呼消息，第一辅助信息至少包括下行SDT指示信息，RRC寻呼消息中至少包括下行SDT指示信息。
在一些实施例中，是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否支持下行SDT。
SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
在一些实施例中，基站控制面实体421还用于向邻基站发送包含第二辅助信息的第二寻呼消息；其中，第二寻呼消息中还包含发送给终端的RRC寻呼消息；第二辅助信息，包括如下信息中的至少一个：缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小、下行SDT指示信息。
在一些实施例中，基站控制面实体在接收到来自基站用户面实体的第二基站内消息的情况下，还判断基站用户面实体中的下行SDT承载的缓存数据量大小是否小于下行小数据包发送触发门限；在小于下行小数据包发送触发门限的情况下，则发送第一寻呼消息给基站分离实体和发送第二寻呼消息给邻基站。
在一些实施例中，在小于下行小数据包发送触发门限的情况下，基站控制面实体发送给基站分离实体的第一寻呼消息包括发送给终端的RRC寻呼消息，该发送给终端的RRC寻呼消息中至少包括含下行SDT指示信息。
图5示出本公开实施例中一种用户面数据到达的通知方法流程图，如图5所示，本公开实施例中提供的用户面数据到达的通知方法包括步骤S502-S506。
在S502中，基站控制面实体向基站用户面实体发送第一基站内请求消息，第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息。
上文中是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否支持下行SDT；SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
在一些实施例中，第一基站内请求消息，包括SDT承载列表，SDT承载列表用于指示基站用户面实体为终端重新配置或者新建一个或者多个DRB为SDT承载。
在一些实施例中，基站控制面实体通过第一基站内请求消息指示基站用户面实体配置SDT承载列表，并可配置SDT承载模式。
SDT承载列表指示了一个或者多个DRB同时支持下行小数据包传输和上行小数据包传输。SDT承载模式包括MT-SDT模式，可用于支持下行小数据包传输和/或上行小数据包传输。
基站用户面实体在接收到第一基站内请求消息后，根据SDT承载列表确定哪些已经配置和/或需要新建的DRB支持SDT传输，并根据SDT承载模式确定所有SDT承载支持下行小数据包传输，当未携带SDT承载模式时则所有SDT承载仅支持上行小 数据包传输。并在配置完成后将配置结果反馈给基站控制面实体。
在S504中，基站用户面实体向基站控制面实体发送第二基站内消息，第二基站内消息用于通知基站控制面实体接收到终端下行数据，第二基站内消息中包括缓存在基站用户面实体中的终端所有SDT承载的下行数据量大小。
在一些实施例中，基站用户面实体从核心网接收到该终端的第一组下行小数据包后，确定这些小数据包全部属于SDT承载后，启动定时器，并统计小数据包的数据量，所述数据量为增加SDAP头部后的数据包大小，在定时器超时前若收到核心网的该终端的小数据包，则继续缓存这些小数据包，并累计小数据包的总数据量。
基站用户面实体在定时器超时后，通过第二基站内消息通知给基站控制面实体，其中第二基站内消息中还包括缓存的下行SDT数据包大小。下行SDT数据包即SDT承载的下行小数据包。
如图6所示，基站用户面实体在发送完针对该终端的第二基站内消息后且未收到来自基站控制面实体发送的用户上下文修改消息时，若再接收到的该终端的SDT数据包(即SDT承载的下行小数据包)时基站用户面实体则继续通过第二基站内消息发送给基站控制面实体，若再接收到非SDT承载的数据包时，则再次发送的第二基站内消息中不携带缓存的下行SDT数据包大小。
在S506中，向基站分离实体发送包含发送给终端的RRC寻呼消息和第一辅助信息的第一寻呼消息，第一辅助信息至少包括下行SDT指示信息，RRC寻呼消息中至少包含下行SDT指示信息。
向基站分离实体发送第一寻呼消息，第一寻呼消息包含发送给终端的RRC寻呼消息和第一辅助信息；第一辅助信息至少包括下行SDT指示信息，RRC寻呼消息中至少包含下行SDT指示信息。
图7示出本公开实施例中一种用户面数据到达的通知方法流程图，如图7所示，该方法的步骤S702-S706与上述实施例的S502-S506相似，在此不再赘述。
与上述实施例不同的是，图7实施例中基站控制面实体还向邻基站发送包含第二辅助信息的第二寻呼消息，第二寻呼消息中包含发送给终端的RRC寻呼消息；其中，第二辅助信息，包括如下信息中的至少一个：缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小、下行SDT指示。
基站控制面实体接收到第二基站内消息或者收到来自核心网发送给该用户高层信令消息后，若仅收到来自核心网发送的高层信令消息，则直接发送第一寻呼消息给 基站分离实体和/或发送第二寻呼消息给相邻的第二基站(即邻基站)；若收到第二基站内消息则判断指示的缓存的下行SDT数据包大小是否满足下行小数据包发送触发门限，当小于该触发门限时发送第一寻呼消息给基站分离实体和发送第二寻呼消息给相邻的基站。其中下行小数据包发送门限的具体数值由网管配置。
当基站控制面实体向基站分离实体发送第一寻呼消息时，携带辅助信息用于指示MT-SDT寻呼以及第一RRC消息，所述第一RRC消息包括MT-SDT指示信息。
基站控制面实体通过Xn接口向第二基站发送第二寻呼消息，第二寻呼消息包括MT-SDT指示信息，下行SDT数据包大小和/或信令指示信息中至少一个。所述下行SDT数据包大小为第一基站用户面实体缓存的下行SDT数据包大小。
图8示出本公开实施例中一种用户面数据到达的通知方法，应用于分离架构基站的基站控制面实体，如图8所示，本公开实施例中提供的用户面数据到达的通知方法包括步骤S802-S806。
在S802中，向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息。
在S804中，接收到第一基站内响应消息，确认请求配置承载的建立情况。
在一些实施例中，第一基站内请求消息，包括SDT承载列表，SDT承载列表用于指示基站用户面实体为终端重新配置或者新建一个或者多个DRB为SDT承载。
在一些实施例中，是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否支持下行SDT；SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
在S806中，接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小。
在S808中，向基站分离实体发送包含发送给终端的RRC寻呼消息和第一辅助信息的第一寻呼消息，所述第一辅助信息，至少包括下行SDT指示信息，所述RRC寻呼消息中至少包含了下行SDT指示信息。
向基站分离实体发送第一寻呼消息，第一寻呼消息包含发送给终端的RRC寻呼消息和第一辅助信息；第一辅助信息至少包括下行SDT指示信息，RRC寻呼消息中至少包含下行SDT指示信息。
在一些实施例中，方法还包括向邻基站发送包含第二辅助信息的第二寻呼消息，第二寻呼消息中包含发送给终端的RRC寻呼消息；其中，第二辅助信息，包括如下信息中的至少一个：
缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小、下行SDT指示信息。
在一些实施例中，在接收到来自基站用户面实体的第二基站内消息的情况下，方法还包括判断基站用户面实体中的下行SDT承载的缓存数量是否小于下行小数据包发送门限；在小于下行小数据包发送门限的情况下，则发送第一寻呼消息给基站分离实体和发送第二寻呼消息给邻基站。
在一些实施例中，基站控制面实体通过Xn接口向邻基站发送第二寻呼消息，第二寻呼消息中包含的RRC寻呼消息中至少包括下行SDT指示信息。
在一些实施例中，下行小数据包发送门限的数值可由网管配置。
在一些实施例中，若收到来自核心网发送的高层信令消息，则直接发送第一寻呼消息给基站分离实体和/或发送第二寻呼消息给邻基站，第二寻呼消息中不携带缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小。
下面通过一个具体的示例，站在基站控制面实体一侧详细描述本公开所提供的用户面数据到达的通知方法。
本实施例主要描述了基站控制面实体gNB-CU-CP给基站用户面实体gNB-CU-UP配置SDT承载采用Rel-18的SDT的过程，以及基站用户面实体接收到一个单独的小数据包，触发下行数据到达的过程，并在发送后再次从核心网收到下行数据包后，继续触发下行数据到达的过程。
gNB-CU-CP通过BEARER CONTEXT MODIFICATION REQUEST消息发送给gNB-CU-UP，其中针对PDU Session#1中携带了DRB#1和DRB#2设置为SDT承载，并且包括了一个指示信息用于配置所有的SDT承载模式为Rel-18的MO-SDT，BEARER CONTEXT MODIFICATION REQUEST具体信元配置见下表：

其中，在PDU Session Resource To Modify List里的信元如下：
gNB-CU-UP收到后配置DRB#1和DRB#2为SDT承载，并配置MT-SDT模式，反馈BEARER CONTEXT MODIFICATION RESPONSE。
gNB-CU-UP收到核心网SMF下发的数据包后，经过SDAP处理后缓存的buffer里，判断这些数据包所属的DRB属于SDT承载，计算包括SDAP头部在内的字节大小为340kbytes，并开启定时，时间为20ms。
定时器超时后，未收到该用户的其他数据包，则发送DL DATA NOTIFICATION消息给gNB-CU-CP，具体信元为：
gNB-CU-CP收到DL DATA NOTIFICATION消息后，检查到其携带了DL SDT Buffer Size，并与其设置门限800kbytes相比，确定触发基于MT-SDT的寻呼。
gNB-CU-CP生成基于MT-SDT的寻呼消息，其中寻呼消息中携带指示信息一个比特的指示信息MT-SDT indication。
gNB-CU-UP收到核心网来的数据包后，发现其仍然为SDT小数据包，则不再继续发送DL DATA NOTIFICATION消息给gNB-CU-CP。
图9示出本公开实施例中一种用户面数据到达的通知方法，应用于分离架构基站 的基站用户面实体，如图9所示，本公开实施例中提供的用户面数据到达的通知方法包括步骤S902-S906。
在S902中，接收基站控制面实体发送的第一基站内请求消息，第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息。这里，配置可以包括重新配置(即修改)或新建。
在一些实施例中，是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否同时支持下行SDT和上行SDT；SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
在S904中，响应第一基站内请求消息，确认请求配置承载的建立情况。
响应第一基站内请求消息，根据指示配置相关DRB为SDT DRB；当SDT承载请求模式携带时，统计下行SDT承载的数据量大小，并通过第二基站内消息发送给基站控制面实体，否则不统计下行SDT承载的数据量大小；响应消息发送给基站控制面实体。
在S906中，在终端的SDT承载的下行数据到达后，向基站控制面实体发送第二基站内消息，第二基站内消息中至少包括缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小。
在一些实施例中，图9所示的方法还包括：若接收到终端的非SDT承载的下行小数据包，则向基站控制面实体发送新的第二基站内消息，新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
在一些实施例中，如图10所示，在SDT承载的终端下行数据到达后，向基站控制面实体发送第二基站内消息，包括：
S1002，接收来自核心网的终端的下行小数据包，添加SDAP包头后缓存；
S1004，判断下行小数据包是否全部属于配置的SDT DRB；
S1006，在下行小数据包全部属于SDT承载的情况下，统计小数据包的数据量大小；
S1008，判断是否配置了SDT承载请求模式；
在配置了SDT承载请求模式的情况下，DRB同时支持下行SDT和上行SDT。
S1010，向基站控制面实体发送第二基站内消息，第二基站内消息包括缓存的小数据包的总数据量。
在一些实施例中，在下行小数据包全部属于SDT承载的情况下，方法还包括：
根据配置启动定时器，定时器由网管进行配置；
在定时器超时前若继续仅收到终端的下行SDT承载小数据包，则继续缓存小数据包，并累计小数据包的总数据量大小量；
在定时器超时后，则向基站控制面实体发送第二基站内消息，第二基站内消息包括缓存的小数据包的总数据量。
在一些实施例中，统计小数据包的数据量大小，包括将下行小数据包，经过SDAP处理后进行缓存；统计小数据包的数据量为统计增加SDAP头部后的数据包大小。
本公开实施例通过用户面实体传递缓存信息用于解决控制面实体是否决定触发下行SDT数据的问题，并且明确了来自用户面和核心网信令的缓存数量计算方法，从而保证了控制面和用户面对于下行SDT触发理解的一致性。
在一些实施例中，在向基站控制面实体发送第二基站内消息后，且未收到来自基站控制面实体发送的用户上下文修改消息时，方法还包括：
若再接收到的终端的SDT数据包，则继续向基站控制面实体发送新的第二基站内消息，新的第二基站内消息中包括新缓存在基站用户面实体中的下行SDT承载的缓存数量；
若再接收到非SDT承载的数据包，则继续向基站控制面实体发送新的第二基站内消息，且新的第二基站内消息中不携带缓存的下行SDT数据包大小。
本公开实施例明确了多个数据包前后到达后的处理方案，避免不同的实现方式导致的SDT缓存上报数值的差异，以方便基站MAC层更好的进行数据发送，从而减少了终端功耗。
下面通过一个具体的示例，站在基站控制面实体详细描述本公开所提供的用户面数据到达的通知方法。
本实施例主要描述了基站控制面实体gNB-CU-CP给基站用户面实体gNB-CU-UP配置SDT承载采用Rel-18的SDT的过程，以及用户面实体接收到一个单独的小数据包，触发下行数据到达的过程。
gNB-CU-CP通过BEARER CONTEXT MODIFICATION REQUEST消息发送给gNB-CU-UP，其中针对PDU Session#1中携带了DRB#1和DRB#2设置为SDT承载，并且包括了一个指示信息用于配置所有的SDT承载模式为Rel-18的MO-SDT(上行SDT)，BEARER CONTEXT MODIFICATION REQUEST具体信元配置为：
其中，在PDU Session Resource To Modify List里的信元如下：
gNB-CU-UP收到后配置DRB#1和DRB#2为SDT承载，并配置MT-SDT(下行 SDT)模式，反馈BEARER CONTEXT MODIFICATION RESPONSE。
gNB-CU-UP收到核心网SMF下发的数据包后，经过SDAP处理后缓存的buffer里，判断这些数据包所属的DRB属于SDT承载，计算包括SDAP头部在内的字节大小为340kbytes，并开启定时，时间为20ms。
定时器超时后，未收到该用户的其他数据包，则发送DL DATA NOTIFICATION消息给gNB-CU-CP，具体信元为：
gNB-CU-CP收到DL DATA NOTIFICATION消息后，检查到其携带了DL SDT  Buffer Size，并与其设置门限800kbytes相比，确定触发基于MT-SDT的寻呼。
gNB-CU-CP生成基于MT-SDT的寻呼消息，其中寻呼消息中携带指示信息一个比特的指示信息MT-SDT indication。
在一些实施例中，gNB-CU-CP主要向gNB-DU发送配置信息让UE在空闲态保持在上行的CG-SDT资源用于作为下行SDT的反馈信息的过程，终端反馈了上行的RRC Resume Request消息后，触发SDT承载恢复和下行数据发送过程。
gNB-CU-CP确定终端需要进入inactive(非激活)状态时，根据用户的运动速度和业务特性确定终端可以使用CG-SDT资源作为下行小数据包传输的响应，发送UE CONTEXT RELEASE COMMAND给gNB-DU，具体信元如下：
其中，RRC Release消息包括如下：
承载标识列表：DRB#1和DRB#2；
是否使用为上行SDT分配的专用PRACH资源：是；
下行用于SDT的专用BWP配置；
上行用于SDT的专用BWP配置；
用于CG-SDT的CS-RNTI；
使用CG-SDT的RSRP门限；
CG-SDT使用时RSRP改变限。
gNB-DU收到后根据CG-SDT Kept Indicator和MT-SDT indicator确定UE采用上行CG-SDT资源作为下行SDT响应，则保留包括CG-SDT相关资源、CS-RNTI、C-RNTI以及CG-SDT相关的RLC层配置，与SDT承载相关的F1-U连接。
gNB-DU把UE CONTEXT RELEASE COMMAND中携带的RRC Release消息发送给UE。
gNB-DU接收到UE在CG-SDT上发送的RRC Resume消息后，通过INITIAL UL RRC MESSAGE TRANSFER。
本公开实施例不涉及对于终端的影响，网络侧方案，具有良好的前向兼容性，易于网络部署和实施落地。
在本公开实施例中，术语“第一”、“第二”和“第三”仅用于描述目的，而不能理解为指示或暗示相对重要性。
本公开中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
此外，尽管在附图中以特定顺序描述了本公开中方法的各个步骤，但是，这并非要求或者暗示必须按照该特定顺序来执行这些步骤，或是必须执行全部所示的步骤才能实现期望的结果。
在一些实施例中，可以省略某些步骤，将多个步骤合并为一个步骤执行，以及/或者将一个步骤分解为多个步骤执行等。
基于同一发明构思，本公开实施例中还提供了一种分离架构基站的基站控制面实体，如下面的实施例所述。由于该实体实施例解决问题的原理与上述方法实施例相似，因此该实体实施例的实施可以参见上述方法实施例的实施，重复之处不再赘述。
图11示出本公开实施例中一种分离架构基站的基站控制面实体，如图11所示，该分离架构基站的基站控制面实体1100，包括：
消息发送模块1102，用于向基站用户面实体发送第一基站内请求消息，第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
第二接收模块1104，用于接收到第一基站内响应消息，确认请求配置承载的建立情况；
通知接收模块1106，用于接收来自基站用户面实体的第二基站内消息，第二基站内消息用于通知基站控制面实体接收到终端的下行数据，第二基站内消息中包括缓存在基站用户面实体中的终端所有SDT承载的下行数据量大小；
寻呼发送模块1108，用于向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一寻呼消息还包括发送给终端的RRC寻呼消息，第一辅助信息至少包括下行SDT指示信息，RRC寻呼消息中至少包括下行SDT指示信息。
在一些实施例中，基站控制面实体1100还包括终止传输模块。终止传输模块用于若接收到来自基站用户面实体的新的第二基站内消息，则终止下行小数据包的传输过程，新的第二基站内消息用于通知基站控制面实体接收到终端的非SDT承载的下行小数据包，新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
在一些实施例中，第一基站内请求消息，包括SDT承载列表，SDT承载列表用于指示基站用户面实体为终端重新配置或者新建一个或者多个DRB为SDT承载。
在一些实施例中，是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否支持下行SDT；
SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
在一些实施例中，该分离架构基站的基站控制面实体1100，还包括：
第二寻呼模块，用于向邻基站发送包含第二辅助信息的第二寻呼消息，第二寻呼消息中包含发送给终端的RRC寻呼消息；
其中，第二辅助信息，包括如下信息中的至少一个：
缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小、下行SDT指示信息。
在一些实施例中，寻呼发送模块1108用于在接收到来自基站用户面实体的第二基站内消息的情况下，判断基站用户面实体中缓存的SDT承载的下行数据量大小是否小于下行小数据包发送触发门限；在小于下行小数据包发送触发门限的情况下，则发送第一寻呼消息给基站分离实体和发送第二寻呼消息给邻基站。
在一些实施例中，寻呼发送模块1108用于通过Xn接口向邻基站发送第二寻呼消息，第二寻呼消息中包含的RRC寻呼消息中至少包括下行SDT指示信息。
在一些实施例中，下行小数据包发送门限的数值由网管配置。
在一些实施例中，寻呼发送模块1108用于若收到来自核心网发送的高层信令消 息，则直接发送第一寻呼消息给基站分离实体和/或发送第二寻呼消息给邻基站；直接发送给邻基站的第二寻呼消息中不携带缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小。
基于同一发明构思，本公开实施例中还提供了一种分离架构基站的基站用户面实体，如图12所示，该分离架构基站的基站用户面实体1200，包括：
消息接收模块1202，用于接收基站控制面实体发送的第一基站内请求消息，第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
消息响应模块1204，用于响应第一基站内请求消息，确认请求配置承载的建立情况；
通知发送模块1206，用于在终端的SDT承载的下行数据到达后，向基站控制面实体发送第二基站内消息，第二基站内消息中至少包括缓存在基站用户面实体中的所有SDT承载的缓存下行数据量大小。
在一些实施例中，通知发送模块1206还用于若接收到终端的非SDT承载的下行小数据包，则向基站控制面实体发送新的第二基站内消息，新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
在一些实施例中，是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否同时支持下行SDT和上行SDT；
SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
在一些实施例中，消息响应模块1204，用于根据指示配置相关DRB为SDT DRB；当SDT承载请求模式携带时，统计下行SDT承载的数据量大小，并通过第二基站内消息发送给基站控制面实体，否则不统计下行SDT承载的数据量大小；将响应消息发送给基站控制面实体。
在一些实施例中，通知发送模块1206，用于接收来自核心网的终端的下行小数据包，添加SDAP包头后缓存；判断下行小数据包所对应的DRB是否全部属于配置的SDT DRB；在下行小数据包全部属于SDT承载的情况下，统计小数据包的数据量大小；判断是否配置了SDT承载请求模式；向基站控制面实体发送第二基站内消息，第二基站内消息包括缓存的该用户终端的所有SDT承载的下行小数据包的总数据量。
在一些实施例中，通知发送模块1206，用于在下行小数据包全部属于SDT承载 的情况下，根据配置启动定时器，定时器由网管进行配置；在定时器超时前若继续仅收到终端的下行SDT承载小数据包，则继续缓存小数据包，并累计小数据包的总数据量大小量；在定时器超时后，则向基站控制面实体发送第二基站内消息，第二基站内消息包括缓存的小数据包的总数据量。
在一些实施例中，统计小数据包的数据量为统计增加SDAP头部后的数据包大小。
在一些实施例中，通知发送模块1206，用于在向基站控制面实体发送第二基站内消息后，且未收到来自基站控制面实体发送的用户上下文修改消息时，若再接收到的终端的SDT数据包，则继续向基站控制面实体发送新的第二基站内消息，新的第二基站内消息中包括新缓存在基站用户面实体中的下行SDT承载的缓存数量；若再接收到非SDT承载的数据包，则继续向基站控制面实体发送新的第二基站内消息，且新的第二基站内消息中不携带缓存的下行SDT数据包大小。
本公开中提及的“第一”、“第二”等概念仅用于对不同的装置、模块或单元进行区分，并非用于限定这些装置、模块或单元所执行的功能的顺序或者相互依存关系。
关于上述实施例中的分离架构基站的基站用户面实体和分离架构基站的基站控制面实体，其中各个模块执行操作的具体方式已经在有关用户面数据到达的通知方法的实施例中进行了详细描述，此处将不做详细阐述说明。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。
实际上，根据本公开的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
附图中所示的一些方框图是功能实体，不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
下面参照图13来描述本公开实施例提供的电子设备。图13显示的电子设备1300仅仅是一个示例，不应对本公开实施例的功能和使用范围带来任何限制。
图13示出本本公实施例提供的一种电子设备1300的架构示意图。如图13所示，该电子设备1300包括但不限于：至少一个处理器1310、至少一个存储器1320。
存储器1320，用于存储指令。
在一些实施例中，存储器1320可以包括易失性存储单元形式的可读介质，例如随机存取存储单元(RAM)13201和/或高速缓存存储单元13202，还可以进一步包括只读存储单元(ROM)13203。
在一些实施例中，存储器1320还可以包括具有一组(至少一个)程序模块13205的程序/实用工具13204，这样的程序模块13205包括但不限于：操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。
在一些实施例中，存储器1320可存储操作系统。该操作系统可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。
在一些实施例中，存储器1320中还可以存储有数据。
作为一个示例，处理器1310可以读取存储器1320中存储的数据，该数据可以与指令存储在相同的存储地址，该数据也可以与指令存储在不同的存储地址。
处理器1310，用于调用存储器1320中存储的指令，实现本说明书上述“示例性方法”部分中描述的根据本公开各种示例性实施方式的步骤。例如，所述处理器1310可以执行上述方法实施例的各步骤。
需要说明的是，上述处理器1310可以是通用处理器或者专用处理器。处理器1310可以包括一个或者一个以上处理核心，处理器1310通过运行指令执行各种功能应用以及数据处理。
在一些实施例中，处理器1310可以包括中央处理器(central processing unit，CPU)和/或基带处理器。
在一些实施例中，处理器1310可以根据各个控制指令中携带的优先级标识和/或功能类别信息确定一个指令。
本公开中，处理器1310和存储器1320可以单独设置，也可以集成在一起。
作为一个示例，处理器1310和存储器1320可以集成在单板或者系统级芯片(system on chip，SOC)上。
如图13所示，电子设备1300以通用计算设备的形式表现。电子设备1300还可以包括总线1330。
总线1330可以为表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器、外围总线、图形加速端口、处理器或者使用多种总线结构中的任意总线结 构的局域总线。
电子设备1300也可以与一个或多个外部设备1340(例如键盘、指向设备、蓝牙设备等)通信，还可与一个或者多个使得用户能与该电子设备1300交互的设备通信，和/或与使得该电子设备1300能与一个或多个其它计算设备进行通信的任何设备(例如路由器、调制解调器等等)通信。这种通信可以通过输入/输出(I/O)接口1350进行。
并且，电子设备1300还可以通过网络适配器1360与一个或者多个网络(例如局域网(LAN)，广域网(WAN)和/或公共网络，例如因特网)通信。
如图13所示，网络适配器1360通过总线1330与电子设备1300的其它模块通信。
应当明白，尽管图中未示出，可以结合电子设备1300使用其它硬件和/或软件模块，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
可以理解的是，本公开实施例示意的结构并不构成对电子设备1300的具体限定。在本公开另一些实施例中，电子设备1300可以包括比图13所示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图13所示的部件可以以硬件，软件或软件和硬件的组合实现。
本公开还提供了一种计算机可读存储介质，其上存储有计算机指令，计算机指令被处理器执行时实现上述方法实施例描述的用户面数据到达的通知方法。
本公开实施例中计算机可读存储介质，为可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的计算机指令。
作为一个示例，计算机可读存储介质是非易失性存储介质。
在一些实施例中，本公开中的计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、U盘、移动硬盘或者上述的任意合适的组合。
本公开实施例中，计算机可读存储介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机指令(可读程序代码)。
这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。
在一些示例中，计算机可读存储介质上包含的计算指令可以用任何适当的介质传输，包括但不限于无线、有线、光缆、RF等等，或者上述的任意合适的组合。
本公开实施例还提供一种计算机程序产品，计算机程序产品存储有指令，指令在由计算机执行时，使得计算机实施上述方法实施例描述的用户面数据到达的通知方法。
上述指令可以是程序代码。在具体实施时，程序代码可以由一种或多种程序设计语言的任意组合来编写。
程序设计语言包括面向对象的程序设计语言—诸如Java、C++等，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。
程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。
在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络，包括局域网(LAN)或广域网(WAN)，连接到用户计算设备，或者，可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
本公开实施例还提供了一种芯片，包括至少一个处理器和接口；
接口，用于为至少一个处理器提供程序指令或者数据；
至少一个处理器用于执行程序指令，以实现上述方法实施例描述的用户面数据到达的通知方法。
在一些实施例中，该芯片还可以包括存储器，该存储器，用于保存程序指令和数据，存储器位于处理器之内或处理器之外。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以具体实现为以下形式，即：完全的硬件实施方式、完全的软件实施方式(包括固件、微代码等)，或硬件和软件方面结合的实施方式，这里可以统称为“电路”、“模块”或“系统”。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。
本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由所附的权利要求指出。

Claims (26)

  1. 一种用户面数据到达的通知方法，其特征在于，应用于分离架构基站的基站控制面实体，所述方法包括：
    向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    接收到第一基站内响应消息，确认请求配置承载的建立情况；
    接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
    向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一寻呼消息还包括发送给终端的RRC寻呼消息，所述第一辅助信息至少包括下行SDT指示信息，所述RRC寻呼消息中至少包括含下行SDT指示信息。
  2. 一种用户面数据到达的通知方法，其特征在于，应用于分离架构基站的基站控制面实体，所述方法包括：
    向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    接收到第一基站内响应消息，确认请求配置承载的建立情况；
    接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
    向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一辅助信息至少包括下行SDT指示信息；
    若接收到来自基站用户面实体的新的第二基站内消息，则终止下行小数据包的传输过程，所述新的第二基站内消息用于通知基站控制面实体接收到终端的非SDT承载的下行小数据包，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一基站内请求消息，包括SDT承载列表，所述SDT承载列表用于指示基站用户面实体为所述终端重新配置或者新建一个或者多个DRB为SDT承载。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述是否支持下行SDT 的指示信息，通过是否携带SDT承载请求模式来表示是否支持下行SDT；
    所述SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
  5. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    向邻基站发送包含第二辅助信息的第二寻呼消息，所述第二寻呼消息中包含发送给终端的RRC寻呼消息；
    所述第二辅助信息，还包括如下信息中的至少一个：
    缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小、下行SDT指示信息。
  6. 根据权利要求5所述的方法，其特征在于，在接收到来自基站用户面实体的第二基站内消息的情况下，所述方法还包括：
    判断所述基站用户面实体中缓存的SDT承载的下行数据量大小是否小于下行小数据包发送触发门限；
    在小于下行小数据包发送触发门限的情况下，则发送所述第一寻呼消息给所述基站分离实体和发送所述第二寻呼消息给邻基站。
  7. 根据权利要求6所述的方法，其特征在于，所述基站控制面实体通过Xn接口向邻基站发送第二寻呼消息，所述第二寻呼消息中包含的RRC寻呼消息中至少包括下行SDT指示信息。
  8. 根据权利要求6所述的方法，其特征在于，所述下行小数据包发送触发门限的数值由网管配置。
  9. 根据权利要求5-8中任一项所述的方法，其特征在于，若收到来自核心网发送的高层信令消息且同时未收到基站用户面实体的第二基站内消息时，则直接发送第一寻呼消息给所述基站分离实体和/或发送第二寻呼消息给邻基站；
    直接发送给邻基站的所述第二寻呼消息中不携带缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小。
  10. 一种用户面数据到达的通知方法，其特征在于，应用于分离架构基站的基站用户面实体，所述方法包括：
    接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    响应所述第一基站内请求消息，确认请求配置承载的建立情况；
    在终端的SDT承载的下行数据到达后，向所述基站控制面实体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小。
  11. 一种用户面数据到达的通知方法，其特征在于，应用于分离架构基站的基站用户面实体，所述方法包括：
    接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    响应所述第一基站内请求消息，确认请求配置承载的建立情况；
    在终端的SDT承载的下行数据到达后，向所述基站控制面实体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小；
    若接收到所述终端的非SDT承载的下行小数据包，则向所述基站控制面实体发送新的第二基站内消息，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
  12. 根据权利要求10或11所述的方法，其特征在于，所述是否支持下行SDT的指示信息，通过是否携带SDT承载请求模式来表示是否支持下行SDT；
    所述SDT承载请求模式指示了所有的SDT DRB同时支持下行SDT和上行SDT，当SDT承载请求模式不携带时，指示了仅配置所有SDT DRB为上行SDT。
  13. 根据权利要求12所述的方法，其特征在于，响应所述第一基站内请求消息，确认请求配置承载的建立情况，包括：
    根据指示配置相关DRB为SDT DRB；
    当SDT承载请求模式携带时，统计下行SDT承载的数据量大小，并通过第二基站内消息发送给基站控制面实体，否则不统计下行SDT承载的数据量大小；
    将响应消息发送给基站控制面实体。
  14. 根据权利要求12所述的方法，其特征在于，当终端的SDT承载下行数据到达后，向所述基站控制面实体发送第二基站内消息，包括：
    接收来自核心网的终端的下行小数据包，添加SDAP包头后缓存；
    判断所述下行小数据包所对应的DRB是否全部属于所述基站用户面实体配置的SDT DRB；
    在所述下行小数据包全部属于SDT承载的情况下，统计小数据包的数据量大小；
    判断是否配置了SDT承载请求模式；
    向所述基站控制面实体发送第二基站内消息，所述第二基站内消息包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小。
  15. 根据权利要求14所述的方法，其特征在于，在所述下行小数据包全部属于SDT承载的情况下，所述方法还包括：
    根据配置启动定时器，所述定时器由网管进行配置；
    在定时器超时前若继续仅收到所述终端的SDT承载的下行小数据包，则继续缓存所述下行小数据包，并累计所述下行小数据包的总数据量大小；
    在定时器超时后，则向所述基站控制面实体发送所述第二基站内消息。
  16. 根据权利要求14所述的方法，其特征在于，所述统计小数据包的数据量为统计增加SDAP头部后的数据包大小。
  17. 根据权利要求10或11所述的方法，其特征在于，在向所述基站控制面实体发送第二基站内消息后，且未收到来自所述基站控制面实体发送的用户上下文修改消息时，所述方法还包括：
    若再接收到的所述终端的SDT承载的下行小数据包，则继续向所述基站控制面实体发送新的第二基站内消息，所述新的第二基站内消息中包括新缓存在所述基站用户面实体中的SDT承载的下行数据量；
    若再接收到非SDT承载的下行小数据包，则继续向所述基站控制面实体发送新的第二基站内消息，且所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
  18. 一种分离架构基站的基站控制面实体，其特征在于，包括：
    消息发送模块，用于向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    第二接收模块，用于接收到第一基站内响应消息，确认请求配置承载的建立情况；
    通知接收模块，用于接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
    寻呼发送模块，用于向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一寻呼消息还包括发送给终端的RRC寻呼消息，所述第一辅助信息至少包括下行SDT指示信息，所述RRC寻呼消息中至少包括下行SDT指示信息。
  19. 一种分离架构基站的基站控制面实体，其特征在于，包括：
    消息发送模块，用于向基站用户面实体发送第一基站内请求消息，所述第一基站内请求消息包括配置至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    第二接收模块，用于接收到第一基站内响应消息，确认请求配置承载的建立情况；
    通知接收模块，用于接收来自基站用户面实体的第二基站内消息，所述第二基站内消息用于通知基站控制面实体接收到终端的下行数据，所述第二基站内消息中包括缓存在所述基站用户面实体中的所述终端所有SDT承载的下行数据量大小；
    寻呼发送模块，用于向基站分离实体发送包含第一辅助信息的第一寻呼消息，所述第一寻呼消息还包括发送给终端的RRC寻呼消息，所述第一辅助信息至少包括下行SDT指示信息，所述RRC寻呼消息中至少包括下行SDT指示信息；
    终止传输模块，用于若接收到来自基站用户面实体的新的第二基站内消息，则终止下行小数据包的传输过程，所述新的第二基站内消息用于通知基站控制面实体接收到终端的非SDT承载的下行小数据包，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
  20. 一种分离架构基站的基站用户面实体，其特征在于，包括：
    消息接收模块，用于接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    消息响应模块，用于响应所述第一基站内请求消息，确认请求配置承载的建立情况；
    通知发送模块，用于在终端的SDT承载的下行数据到达后，向所述基站控制面实体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小。
  21. 一种分离架构基站的基站用户面实体，其特征在于，包括：
    消息接收模块，用于接收基站控制面实体发送的第一基站内请求消息，所述第一基站内请求消息包括配置或者修改至少一个DRB为SDT承载，以及是否支持下行SDT的指示信息；
    消息响应模块，用于响应所述第一基站内请求消息，确认请求配置承载的建立情况；
    通知发送模块，用于在终端的SDT承载的下行数据到达后，向所述基站控制面实 体发送第二基站内消息，所述第二基站内消息中至少包括缓存在所述基站用户面实体中的所有SDT承载的缓存下行数据量大小；以及用于若接收到所述终端的非SDT承载的下行小数据包，则向所述基站控制面实体发送新的第二基站内消息，所述新的第二基站内消息中不携带缓存的SDT承载的下行数据包大小。
  22. 一种分离架构基站，其特征在于，包括：
    基站分离实体；
    基站集中实体，所述基站集中实体包括基站控制面实体和基站用户面实体；所述基站控制面实体用于实现如权利要求1-9任一项所述的用户面数据到达的通知方法。
  23. 一种电子设备，其特征在于，包括：
    存储器，用于存储指令；
    处理器，用于调用所述存储器中存储的指令，实现如权利要求1-17任一项所述的用户面数据到达的通知方法。
  24. 一种计算机可读存储介质，其上存储有计算机指令，其特征在于，所述计算机指令被处理器执行时实现权利要求1-17中任意一项所述的用户面数据到达的通知方法。
  25. 一种计算机程序产品，其特征在于，所述计算机程序产品存储有指令，所述指令在由计算机执行时，使得所述计算机实施权利要求1-17中任意一项所述的用户面数据到达的通知方法。
  26. 一种芯片，其特征在于，包括至少一个处理器和接口；
    所述接口，用于为所述至少一个处理器提供程序指令或者数据；
    所述至少一个处理器用于执行所述程序指令，以实现如权利要求1-17中任一项所述的用户面数据到达的通知方法。
PCT/CN2023/117038 2023-05-19 2023-09-05 用户面数据到达的通知方法及相关设备 Ceased WO2024239487A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310574049.7A CN118433739A (zh) 2023-05-19 2023-05-19 用户面数据到达的通知方法及相关设备
CN202310574049.7 2023-05-19

Publications (1)

Publication Number Publication Date
WO2024239487A1 true WO2024239487A1 (zh) 2024-11-28

Family

ID=92333841

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/117038 Ceased WO2024239487A1 (zh) 2023-05-19 2023-09-05 用户面数据到达的通知方法及相关设备

Country Status (2)

Country Link
CN (1) CN118433739A (zh)
WO (1) WO2024239487A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021027821A1 (zh) * 2019-08-13 2021-02-18 维沃移动通信有限公司 Sdt处理方法、设备及系统
WO2022192124A1 (en) * 2021-03-08 2022-09-15 Idac Holdings, Inc. Methods, architectures, apparatuses and systems for downlink small data transmission (dl sdt) and reception in inactive radio access network (ran) state
US20230156702A1 (en) * 2021-11-18 2023-05-18 Electronics And Telecommunications Research Institute Method and apparatus for downlink small data transmission operation in mobile communication system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4233413B1 (en) * 2020-10-21 2025-12-24 Ofinno, LLC Paging for small data transmission
KR20220091341A (ko) * 2020-12-23 2022-06-30 삼성전자주식회사 무선 통신 시스템에서 스몰 데이터 전송을 지원하기 위한 방법 및 장치
EP4115696A4 (en) * 2021-05-19 2023-09-27 ZTE Corporation METHOD, APPARATUS AND COMPUTER PROGRAM PRODUCT FOR WIRELESS COMMUNICATION
CN115706980A (zh) * 2021-08-10 2023-02-17 中国电信股份有限公司 锚点确定方法、基站、终端、设备及计算机可读存储介质
CN116017557A (zh) * 2021-10-22 2023-04-25 大唐移动通信设备有限公司 数据传输方法、装置及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021027821A1 (zh) * 2019-08-13 2021-02-18 维沃移动通信有限公司 Sdt处理方法、设备及系统
WO2022192124A1 (en) * 2021-03-08 2022-09-15 Idac Holdings, Inc. Methods, architectures, apparatuses and systems for downlink small data transmission (dl sdt) and reception in inactive radio access network (ran) state
US20230156702A1 (en) * 2021-11-18 2023-05-18 Electronics And Telecommunications Research Institute Method and apparatus for downlink small data transmission operation in mobile communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "DL non-SDT data and signalling arrival during SDT procedure", 3GPP DRAFT; R3-215321, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20211101 - 20211111, 22 October 2021 (2021-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052068303 *

Also Published As

Publication number Publication date
CN118433739A (zh) 2024-08-02

Similar Documents

Publication Publication Date Title
CN110557786B (zh) 一种无线承载建立、业务流的监测方法及装置
CN106576279B (zh) 多通信制式传输方法及装置
CN111432440A (zh) 实现业务连续性的方法、装置及系统
WO2021032131A1 (zh) 一种用户面信息上报方法及装置
WO2018171791A1 (zh) 数据传输方法、接入网设备、终端及通信系统
CN103581885A (zh) 用户设备辅助信息上报方法、装置和系统
WO2017091994A1 (zh) 数据发送方法、装置和终端
KR20200088441A (ko) 요청 프로세싱 방법 및 대응하는 엔티티
WO2023185952A1 (zh) Mbs的处理方法、发送装置及接收装置
WO2021081875A1 (zh) Rrc连接状态控制方法、装置及存储介质
CN110324857B (zh) 一种业务质量数据流的处理方法和装置
CN114846774B (zh) 一种通信方法及装置
CN108809510B (zh) 一种数据传输的处理方法和装置
WO2023221755A1 (zh) Bsr触发和上报方法、资源分配方法及装置
WO2021008263A1 (zh) 数据传输方法、装置及系统
JP2024541064A (ja) 指示方法、データ伝送方法、通信ノードおよび記憶媒体
CN106576382B (zh) 一种终端、基站、系统及传输应用数据的方法
CN115696490A (zh) 局域网通信方法、装置、终端、电子设备和存储介质
CN108391325A (zh) 管理无线连接的方法、装置及终端
CN108200639A (zh) 业务数据的发送方法、装置及终端
WO2024239487A1 (zh) 用户面数据到达的通知方法及相关设备
CN112243296A (zh) 辅小区激活方法及装置
WO2023179019A1 (zh) 支持低时延业务的用户面配置方法、系统、基站及介质
CN117356141A (zh) 用于小数据传输的方法、设备和系统
TWI719359B (zh) 異質網路聚合啟動方法與相關的行動通訊基地台裝置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23938156

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE