WO2024020753A1 - 数据传输方法和装置 - Google Patents

数据传输方法和装置 Download PDF

Info

Publication number
WO2024020753A1
WO2024020753A1 PCT/CN2022/107716 CN2022107716W WO2024020753A1 WO 2024020753 A1 WO2024020753 A1 WO 2024020753A1 CN 2022107716 W CN2022107716 W CN 2022107716W WO 2024020753 A1 WO2024020753 A1 WO 2024020753A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
information
terminal device
sdt
message
Prior art date
Application number
PCT/CN2022/107716
Other languages
English (en)
French (fr)
Inventor
吴昱民
Original Assignee
北京小米移动软件有限公司
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 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280002510.5A priority Critical patent/CN117796136A/zh
Priority to PCT/CN2022/107716 priority patent/WO2024020753A1/zh
Publication of WO2024020753A1 publication Critical patent/WO2024020753A1/zh

Links

Images

Classifications

    • 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 field of communication technology, and in particular, to a data transmission method and device.
  • a terminal device can send uplink information to a node serving the terminal device through SDT in a non-connected state, such as an idle state or an inactive state (IDLE/INACTIVE) (the terminal device is within the coverage range of the node). within), and receive downlink information sent by the node serving the terminal device.
  • a non-connected state such as an idle state or an inactive state (IDLE/INACTIVE) (the terminal device is within the coverage range of the node). within)
  • Terminal equipment can accurately and efficiently send and receive uplink and downlink information to avoid transmission failures and waste of resources. This is an urgent problem that needs to be solved.
  • Embodiments of the present disclosure provide a data transmission method and device, so that the first node can accurately send and receive SDT information with a terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • an embodiment of the present disclosure provides a data transmission method.
  • the method is executed by a first node.
  • the method includes: determining the information of the small data packet transmission SDT that needs to be sent and/or received, wherein the first node It is a node that cannot determine whether the terminal device in the non-connected state is within its coverage, or it is a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state; send the first message to the second node, where , the first message includes first information related to the SDT of the terminal device in a non-connected state, and the first information is used to instruct the second node to, according to the first request message after receiving the first request message of the terminal device.
  • the first information sends and/or receives the SDT information.
  • the first node determines that the small data packet needs to be sent and/or received to transmit SDT information, wherein the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage. , or a node that cannot directly transmit and receive uplink and downlink information with the terminal device in the non-connected state; send a first message to the second node, wherein the first message includes the SDT related to the terminal device in the non-connected state
  • the first information is used to instruct the second node to send and/or receive the SDT information according to the first information after receiving the first request message from the terminal device.
  • the first node can accurately and efficiently transmit and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • an embodiment of the present disclosure provides another data transmission method.
  • the method is executed by a second node.
  • the method includes: receiving a first message sent by the first node, wherein the first message includes a link in a non-connected state.
  • the first information related to the SDT of the terminal device in the state the first information is used to instruct the second node to send and/or receive the first request message according to the first information after receiving the first request message from the terminal device.
  • SDT information the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage, or a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • embodiments of the present disclosure provide a communication device that has some or all of the functions of the first node in the method described in the first aspect.
  • the functions of the communication device may include some or all of the functions in the present disclosure.
  • the functions in all the embodiments may also be used to independently implement any one embodiment of the present disclosure.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a processing module configured to determine that the small data packet needs to be sent and/or received to transmit SDT information, wherein the first node cannot be determined to be in a non-connected state. Whether the terminal device is a node within its coverage, or a node that cannot directly transmit and receive uplink and downlink information with the terminal device in a non-connected state; the transceiver module is configured to send the first message to the second node, where The first message includes first information related to the SDT of the terminal device in a non-connected state, and the first information is used to instruct the second node to proceed according to the first request message of the terminal device after receiving the first request message of the terminal device. A message is sent and/or received from the SDT.
  • embodiments of the present disclosure provide another communication device that has some or all of the functions of the second node in the method example described in the second aspect.
  • the functions of the communication device may include the functions of the second node in the present disclosure.
  • the functions in some or all of the embodiments may also be used to independently implement any one of the embodiments of the present disclosure.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may further include a storage module coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.
  • the communication device includes: a transceiver module configured to receive a first message sent by a first node, wherein the first message includes a third message related to the SDT of the terminal device in the non-connected state.
  • a piece of information, the first information is used to instruct the second node to send and/or receive the information of the SDT according to the first information after receiving the first request message from the terminal device, the first node It is a node that cannot determine whether a terminal device in a non-connected state is within its coverage, or a node that cannot directly send and receive uplink and downlink information with a terminal device in a non-connected state.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor.
  • the processor calls a computer program in a memory, it executes the method described in the second aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a communication device.
  • the device includes a processor and an interface circuit.
  • the interface circuit is used to receive code instructions and transmit them to the processor.
  • the processor is used to run the code instructions to cause the The device performs the method described in the second aspect above.
  • embodiments of the present disclosure provide a migration system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and The communication device according to the sixth aspect, or the system includes the communication device according to the seventh aspect and the communication device according to the eighth aspect, or the system includes the communication device according to the ninth aspect and the communication device according to the tenth aspect. the above-mentioned communication device.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned first node. When the instructions are executed, the first node is caused to execute the above-mentioned first aspect. method described.
  • embodiments of the present invention provide a readable storage medium for storing instructions used by the above-mentioned second node. When the instructions are executed, the second node is caused to execute the above-mentioned second aspect. Methods.
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the first aspect.
  • the present disclosure also provides a computer program product including a computer program, which when run on a computer causes the computer to execute the method described in the second aspect.
  • the present disclosure provides a chip system, which includes at least one processor and an interface for supporting the first node to implement the functions involved in the first aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the first node.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system.
  • the chip system includes at least one processor and an interface for supporting the second node to implement the functions involved in the second aspect, for example, determining or processing the functions involved in the above method. At least one of data and information.
  • the chip system further includes a memory, and the memory is used to store necessary computer programs and data for the second node.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect.
  • Figure 1 is a flow chart of a method for performing RA-SDT on a non-connected terminal device provided by an embodiment of the present disclosure
  • Figure 2 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 3 is a schematic architectural diagram of a CU-DU provided by an embodiment of the present disclosure.
  • Figure 4 is a schematic diagram of an RRC state transition provided by an embodiment of the present disclosure.
  • Figure 5 is a flow chart of a data transmission method provided by an embodiment of the present disclosure.
  • Figure 5a is a flow chart of another data transmission method provided by an embodiment of the present disclosure.
  • Figure 5b is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 6 is a flow chart of another data transmission method provided by an embodiment of the present disclosure.
  • Figure 7 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 8 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 9 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 10 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 11 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 11a is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 12 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 13 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 14 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 15 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 16 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 17 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 18 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 19 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 20 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 21 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 22 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 23 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • Figure 24 is a structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 25 is a structural diagram of another communication device provided by an embodiment of the present disclosure.
  • Figure 26 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • data can be transmitted between the terminal device and the access network device when the terminal device is in the RRC connected state (CONNECTED).
  • the data packets that terminal equipment in RRC idle state (IDLE) or RRC inactive state (INACTIVE) need to transmit are very small.
  • This type of data packets can be called small data packets (small data), and terminal equipment
  • the signaling required to enter the RRC CONNECTED state from the RRC IDLE state or the RRC INACTIVE state is even larger than small data, resulting in unnecessary power consumption and signaling overhead for the terminal device.
  • terminal equipment in the RRC IDLE state or RRCINACTIVE state can transmit small data during the random access (RA) process or transmit small data on the resources configured by the access network equipment without entering RRC CONNECTED state before transmitting small data.
  • RA random access
  • the above transmission process can be called SDT (small data transmission, small data packet transmission), in which the way the terminal device transmits small data on the resources configured by the access network device can be called CG-SDT (Configure Grant small data transmission, configuration Authorized small data packet transmission), the way the terminal device transmits small data during the random accounting process can be called RA-SDT (Random Access small data transmission).
  • SDT small data transmission, small data packet transmission
  • CG-SDT Configure Grant small data transmission, configuration Authorized small data packet transmission
  • RA-SDT Random Access small data transmission
  • the data can be sent directly to the access network device through the following methods:
  • Msg3 of the four-step random access process for initial access or 4-step RACH SDT
  • Dedicated uplink PUSCH Physical Uplink Shared Channel
  • resources configured by the access network equipment (i.e. CG (Configure Grant) or PUR (Preallocated Uplink Resource)); or CG SDT .
  • CG Physical Uplink Shared Channel
  • PUR Preallocated Uplink Resource
  • the SDT process may include an initial data sending phase and a subsequent data sending phase.
  • the initial data sending stage starting from triggering SDT initial data sending to receiving confirmation information for the initial data from the network side.
  • the confirmation information will have the following three differences compared with different SDT processes:
  • the confirmation information is the contention resolution identification of successfully received Msg4;
  • the confirmation information is the data reception success indication sent by the access network device (such as the ACK (affirmative response) information indicated by the physical layer DCI (Downlink Control Information, downlink control information).)
  • Subsequent data sending phase from receiving the acknowledgment information of the initial data from the access network device to receiving the connection release message sent by the access network device.
  • the terminal device can send and receive uplink and downlink data.
  • the terminal device will monitor the PDCCH (Physical downlink control channel, physical downlink control channel) to receive the C-RNTI (Cell Radio Network Temporary Identifier, cell wireless network temporary identifier) and perform subsequent CG-PUSCH is sent at all times.
  • the terminal device Before receiving the connection release message sent by the access network device, the terminal device will repeatedly monitor the PDCCH and then send CG-PUSCH.
  • the terminal device After the terminal device uses the CG resource to send data, it will start a feedback timer (for example, feedbackTimer) to monitor the feedback information of the access network device. If the terminal device does not receive a successful reception confirmation from the access network device during the running of the feedback timer, the terminal device retransmits data in subsequent CG resources and performs CG-SDT retransmission.
  • a feedback timer for example, feedbackTimer
  • the terminal device For uplink dynamic authorization Configured Grant, every time the terminal device sends uplink new data transmission on a HARQ process, the configured authorization timer corresponding to the HARQ process will be started. During the running of the timer, other HARQ processes cannot be scheduled. New biography.
  • Configuring the grant retransmission timer can be configured Per Configured Grant for automatic uplink retransmission.
  • the CG-RetransmissionTimer corresponding to the HARQ process will be started.
  • no uplink automatic retransmission will be performed.
  • automatic uplink retransmission is started.
  • the terminal device can send uplink data to the network side through RA-SDT or CG-SDT. If the access network equipment (Receiving gNB) receives the uplink data ) is not the last access network device (Last serving gNB) that serves the terminal device. The Receiving gNB needs to obtain the terminal device context, or part of the terminal device context, from the Last serving gNB in order to receive uplink data. Among them, Last serving gNB can decide whether to perform anchor relocation (anchor relocation). If anchor relocation is not performed (that is, without anchor relocation), the process shown in Figure 1 is executed.
  • anchor relocation anchor relocation
  • the terminal device sends RRC Resume Request and uplink (UL) SDT data and/or signaling to the Receiving gNB.
  • Receiving gNB uses I-RNTI (inactive radio network temporary identifier, inactive wireless network temporary identifier) to identify the Last serving gNB, and retrieves the terminal device context process through XnAP (Xn application protocol, Xn interface application protocol) context.
  • I-RNTI active radio network temporary identifier, inactive wireless network temporary identifier
  • XnAP Xn application protocol, Xn interface application protocol
  • the receiving gNB indicates that the end device request is an SDT interaction and may also provide SDT assistance information (i.e., single packet, multi-packet).
  • Last serving gNB decided not to relocate the terminal device context for SDT.
  • the terminal device context of the Last serving gNB transmission part including SDT-related RLC context.
  • Receiving gNB confirms receiving part of the terminal device context and provides the relevant DL TNL address when needed. After completing part of the terminal device context retrieval, the terminal device context is retained in the Last serving gNB, the RLC context related to SDT is established in the Receiving gNB, and then the UL SDT data is sent to UPF. If there is UL NAS (non-access straum, non-access straum) into the layer) PDU (protocoldata unit, protocol data unit), then deliver the UL NAS PDU to the AMF.
  • UL NAS non-access straum, non-access straum
  • PDU protocoldata unit, protocol data unit
  • the Last serving gNB responds to the Receiving gNB with a RETRIEVE UE CONTEXT FAILURE message, including an encapsulated RRCRelease message.
  • the pending configuration is included in the RRCRelease message.
  • Receiving gNB sends an RRCRelease message to the terminal device.
  • the terminal device remains in the "RRC_INACTIVE" state.
  • the network side sends downlink paging messages to allow the terminal device to initiate the connection recovery (or establishment) process in the IDLE/INACTIVE (idle state or inactive state) state. This allows the terminal device to remain in the IDLE/INACTIVE state and receive downlink data sent by the network side.
  • an embodiment of the present disclosure provides a communication system, including: core network equipment (such as 5G core network (5th generation core, 5GC) 11, evolved packet core network (evolved packet core, EPC) 12) , access network equipment (such as evolving node B (gNB) 13, evolved node B (evolved node B, eNB) 14), terminal equipment 15.
  • core network equipment such as 5G core network (5th generation core, 5GC) 11, evolved packet core network (evolved packet core, EPC) 12
  • EPC evolved packet core network
  • access network equipment such as evolving node B (gNB) 13, evolved node B (evolved node B, eNB) 14
  • terminal equipment such as 5G core network (5th generation core, 5GC) 11, evolved packet core network (evolved packet core, EPC) 12
  • gNB evolving node B
  • evolved node B evolved node B
  • Terminal equipment 15 also known as user equipment (UE), mobile station (MS), mobile terminal (MT), etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (augmentedreality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid Terminals, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • MID mobile internet devices
  • VR virtual reality
  • AR augmented reality
  • Core network equipment 11 refers to equipment in the core network (core network, CN) that provides business support for terminal equipment.
  • core network CN
  • some core network equipment includes: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, etc. , not listed here.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • the AMF entity can be responsible for access management and mobility management of terminal equipment.
  • the SMF entity can be responsible for session management, such as user session establishment, etc.
  • the UPF entity can be a functional entity on the user plane and is mainly responsible for connecting to external networks.
  • entities may also be called network elements or functional entities.
  • AMF entities may also be called AMF network elements or AMF functional entities
  • SMF entities may also be called SMF network elements or SMF functional entities.
  • the access network device 13 refers to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network, and can also be called a base station.
  • RAN nodes include: gNB, eNB, transmission reception point (TRP), radio network controller (RNC), Node B (Node B, NB), base station controller (base station controller, BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or homenode B, HNB), base band unit (base band unit, BBU), or wireless fidelity, Wi-Fi) access point (AP), etc.
  • the access network equipment may include a centralized unit (CU), a distributed unit (DU), or RAN equipment including CU and DU.
  • the RAN equipment including CU and DU separates the protocol layer from the perspective of logical functions. Some protocol layer functions are centralized controlled by the CU, and the remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • FIG. 3 it is a schematic diagram of the architecture of CU-DU.
  • CU and DU can be physically separated or deployed together.
  • CU and DU can be divided according to the protocol layer.
  • the protocol layer is a protocol layer that is only available when the access network device is connected to the 5G core network) and the packet data convergence protocol layer (PDCP), while DU is used to perform radio link control (radio link control, RLC) layer, media access control (medium access control, MAC) layer and physical (physical, PHY) layer.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • CUs and DUs can also be divided in other ways.
  • a CU or DU can be divided into functions with more protocol layers.
  • a CU or DU can also be divided into partial processing functions with a protocol layer.
  • some functions of the RLC layer and functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and functions of the protocol layer below the RLC layer are set in the DU.
  • the functions of the CU or DU can also be divided according to service types or other system requirements. For example, according to delay, functions whose processing time needs to meet the delay requirements are set in DU, and functions that do not need to meet the delay requirements are set in CU.
  • the CU may also have one or more functions of the core network.
  • One or more CUs can be set centrally or separately.
  • CU can be set up on the network side to facilitate centralized management.
  • DU can have multiple radio frequency functions, and the radio frequency functions can also be set remotely.
  • CU and DU can be set as needed in specific implementation, and the embodiments of the present disclosure do not impose any limitation on this.
  • the functions of CU can be implemented by one entity or by different functional entities.
  • the functions of CU can be further divided into control plane (CP) functions and user plane (UP) functions, that is, CU can be divided into CU-UP and CU-CP.
  • CP control plane
  • UP user plane
  • CU-CP and CU-UP can be implemented by different functional entities, or they can be implemented by the same functional entity.
  • CU-CP and CU-UP can be coupled with DU to jointly complete the functions of access network equipment.
  • CU-CP is responsible for control plane functions, mainly including RRC and PDCP-C.
  • PDCP-C is mainly responsible for encryption and decryption of control plane data, integrity protection and data transmission.
  • CU-UP is responsible for user plane functions, mainly including SDAP and PDCP-U.
  • SDAP is mainly responsible for processing data from core network equipment and mapping data flows to bearers.
  • PDCP-U is mainly responsible for data plane encryption and decryption, integrity protection, header compression, serial number maintenance and data transmission. Another possible implementation is that PDCP-C is also included in CU-UP.
  • the core network device can communicate with the CU (such as CU-UP and/or CU-CP).
  • the CU-CP can communicate with the core network device through the Ng interface on behalf of the access network device.
  • CU-UP and CU-CP can communicate, for example, through the E1 interface.
  • CU-UP and DU and CU-CP and DU can communicate.
  • CU-CP can communicate with DU through F1-C (control plane), and CU-UP can communicate with F1-U (user plane).
  • Communicate with DU can share one CU, and one DU can also be connected to multiple CUs (not shown in the figure).
  • CU and DU can communicate through interfaces (such as F1 interface).
  • both the access network device 13 and the access network device 14 can communicate with multiple terminal devices.
  • the terminal device communicating with the access network device 13 and the terminal device communicating with the access network device 14 may be the same or different.
  • the terminal device 15 shown in Figure 2 can communicate with the access network device 13 and the access network device 14 at the same time, but this only shows one possible scenario. In some scenarios, the terminal device may only communicate with the access network device 13 and the access network device 14.
  • the network device 13 or the access network device 14 communicates, and this application does not limit this.
  • Figure 2 is only a simplified schematic diagram for ease of understanding.
  • the communication system may also include other access network equipment, terminal equipment, or core network equipment, which are not shown in Figure 2 .
  • the RRC states of terminal equipment include connected state (RRC_CONNECTED), idle state (RRC_IDLE), and inactive state (RRC_INACTIVE, or the third state).
  • the RRC inactive state is a newly introduced state in which terminal equipment is connected to the 5G core network through access network equipment. This state is between the connected state and the idle state.
  • RRC_INACTIVE there is no RRC connection between the terminal device and the access network device, but the connection between the access network device and the core network device is maintained.
  • the terminal device saves all or part of the information necessary to establish/restore the connection. Therefore, in the RRC_INACTIVE state, when the terminal device needs to establish a connection, it can quickly establish or restore an RRC connection with the access network device based on the saved relevant information.
  • the terminal device When the terminal device is in the RRC_CONNECTED state, the terminal device has established links with the access network equipment and the core network. When data reaches the network, it can be directly transmitted to the terminal device; when the terminal device is in the RRC_INACTIVE state, it means that the terminal device has previously and The access network equipment and the core network have established links, but the link from the terminal equipment to the access network equipment is released. However, the access network equipment will store the context of the terminal equipment. When there is data that needs to be transmitted, the access network equipment This link can be quickly restored; when the terminal equipment is in the RRC_IDLE state, there is no link between the terminal equipment, the access network equipment, and the core network. When there is data that needs to be transmitted, it is necessary to establish a connection between the terminal equipment and the access network equipment and Core network links.
  • Figure 4 is a schematic diagram of an RRC state transition provided by an embodiment of the present disclosure.
  • the terminal device in the RRC_IDLE state, can access the access network device during the access process or access. After the network equipment is installed, the terminal equipment can perform the RRC establishment process with the access network equipment, so that the status of the terminal equipment changes from the RRC_IDLE state to the RRC_CONNECTED state.
  • the terminal device In the RRC_IDLE state, after the terminal device receives a paging message from the access network device or is triggered by the higher layer of the terminal device, the terminal device can initiate the RRC establishment process and attempt to establish an RRC connection with the access network device to enter the RRC_CONNECTED state.
  • the RRC establishment process between the terminal device and the access network device includes: the terminal device sends an RRC setup request (RRCSetupResuest) message to the access network device; after receiving the request: the access network device sends an RRC setup ( RRCSetup) message, so that the state of the terminal device can be converted to the RRC_CONNECTED state; or, the access network device sends an RRC Reject (RRRCeject) message to the terminal device, so that the terminal device continues to stay in the RRC_IDLE state.
  • RRC setup request RRCSetupResuest
  • RRC setup RRCSetup
  • RRRCeject RRC Reject
  • the access network device can release the RRC process, such as sending an RRC release (RRCRelease) message to the terminal device, so that the state of the terminal device changes from the RRC_CONNECTED state to the RRC_IDLE state or the RRC_INACTIVE state.
  • RRC_INACTIVE the terminal device can enter the RRC_IDLE state by releasing the RRC connection, or the terminal device can enter the RRC_CONNECTED state by restoring the RRC connection.
  • the access network device knows that the terminal device is within the coverage or management range of the access network device; the core network knows which access network device the terminal device is within the coverage or management range. Within the range, the core network knows through which access network device the terminal device can be located or found.
  • the terminal device can pass the RRC establishment or RRC recovery (resume) process to convert the status of the terminal device from the RRC_INACTIVE state to the RRC_CONNECTED state; the access network device can pass the RRC release process to convert the state of the terminal device from the RRC_INACTIVE state. It is RRC_IDLE state.
  • the terminal device can initiate the RRC recovery process and attempt to restore the RRC connection with the access network device to enter the RRC_CONNECTED state. .
  • the RRC recovery process between the terminal device and the access network device includes: the terminal device sends an RRC recovery request (RRCResumeResuest) message to the access network device.
  • the access network device After receiving the request: the access network device sends an RRC Establishment ( RRCSetup) message or RRC recovery (RRCResume) message, so that the state of the terminal device can be converted to the RRC_CONNECTED state; or, the access network device sends an RRC release (RRCRelease) message to the terminal device, so that the state of the terminal device can be converted from the RRC_INACTIVE state to RRC_IDLE. state; or, the access network device sends an RRC Reject message to the terminal device, so that the terminal device continues to stay in the RRC_INACTIVE state.
  • the access network device When the terminal device is in the RRC_INACTIVE state, there is no RRC connection between the terminal device and the access network device. At this time, the access network device does not know whether the terminal device is within the coverage of the access network device or whether it is within the management range of the access network device; the core network knows which access network device the terminal device is within. Within or within the management scope, the core network knows through which access network device the terminal device can be located or found.
  • the terminal device is in a non-connected state, which may be that the terminal device is in an idle state, or the terminal device is in an inactive state, or in a state other than a connected state; the terminal device is in a non-connected state.
  • the terminal device In the state, the terminal device may be in the idle state, or the terminal device may be in the inactive state, or the terminal device may be in other states other than the connected state.
  • "for indicating” may include for direct indicating and for indirect indicating.
  • the indication information When describing certain indication information as indicating A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must include A.
  • SDT data is data transmitted through the SDT mechanism, which may refer to user plane data, or may also refer to control plane signaling, such as uplink and downlink RRC messages, NAS messages and/or LPP. (LTE positioning protocol, LTE positioning protocol) messages, etc.
  • the SDT resource or the SDT configuration may be MT-SDT, CG-SDT, RA-SDT or SPS-SDT, etc.
  • Figure 5 is a flow chart of a data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the first node.
  • the method may include but is not limited to the following steps:
  • S51 Determine the small data packet that needs to be sent and/or received to transmit SDT information, where the SDT information includes data and/or signaling.
  • the first node is unable to determine whether the terminal device in the non-connected state is within its coverage. nodes, or nodes that cannot directly send and receive uplink and downlink information with terminal devices in a non-connected state.
  • the signaling of SDT includes but is not limited to Non-Access Stratum (Non-Access Stratum) NAS signaling, LTE Positioning Protocol (LTE Positioning Protocol) LPP signaling, and/or RRC signaling.
  • the data of SDT can be from the core Network user plane data and/or data that the first node itself needs to send to the terminal device.
  • the first node determines the SDT information that needs to be sent may determine the SDT data that needs to be sent, or determines the SDT signaling that needs to be sent, or determines the SDT data and signaling that needs to be sent.
  • the first node determines the SDT information that needs to be received may determine the SDT data that needs to be received, or determines the SDT signaling that needs to be received, or determines the SDT data and signaling that needs to be received.
  • the first node determines the SDT information that needs to be sent and received may determine the SDT data that needs to be sent and received, or determines the SDT signaling that needs to be sent and received, or determines the SDT data and signaling.
  • the first node receives downlink data and/or downlink signaling to the terminal device from other nodes, or the first node decides to send downlink data and/or downlink signaling to the terminal device, the first node can determine SDT information needs to be sent to the terminal device.
  • the first node determines the SDT information that needs to be sent and/or received, may determine the SDT information that needs to be sent to the terminal device in the non-connected state, and/or determines that it needs to receive the SDT information from the terminal device in the non-connected state. SDT information of the terminal device.
  • the first node may be an access network device.
  • the access network device determines the SDT information that needs to be sent and/or received, the SDT data and/or signaling that needs to be sent, and the access network device that needs to be received. SDT data and/or signaling.
  • the access network device can obtain the SDT data and/or signaling that needs to be sent from the core network node to determine the SDT data and/or signaling that needs to be sent, and the access network device can according to the SDT data and/or signaling sent by it. SDT data and/or signaling, determine whether there is SDT data and/or signaling that needs to be received.
  • the access network device can also determine the data and/or signaling of the SDT to be sent based on other information, and/or determine the data and/or signaling of the SDT to be received, which is not specifically limited in this embodiment of the disclosure.
  • the first node may be a core network node, such as: AMF (Access and Mobility Management Function, access and mobility management function), or UPF (User Plane Function, user plane function device), or SMF ( Session Management Function, session management function equipment), etc.
  • AMF Access and Mobility Management Function, access and mobility management function
  • UPF User Plane Function, user plane function device
  • SMF Session Management Function, session management function equipment
  • the core network node determines the SDT information that needs to be sent and/or received, can determine the SDT data and/or signaling that needs to be sent, and can determine the SDT data and/or signaling that needs to be received.
  • the core network node can determine the SDT data and/or signaling that needs to be sent based on its own information, and the core network node can determine whether there is any SDT data and/or signaling that needs to be received based on the SDT data and/or signaling it sends. SDT data and/or signaling.
  • the core network node can also determine the data and/or signaling of the SDT to be sent based on other information, and/or determine the data and/or signaling of the SDT to be received, which is not specifically limited in the embodiments of the present disclosure.
  • the first node may be a centralized unit CU, or a centralized unit user plane CU-UP.
  • the CU or CU-UP determines the SDT information that needs to be sent and/or received, may determine the SDT data and/or signaling that needs to be sent, and may determine the SDT data and/or signaling that needs to be received.
  • the CU or CU-UP can communicate with the core network node, obtain the data and/or signaling of the SDT that needs to be sent from the core network node, to determine the data and/or signaling of the SDT that needs to be sent, and, the CU or The CU-UP may determine whether there is data and/or signaling of the SDT that needs to be received based on the data and/or signaling of the SDT it sends.
  • the CU or CU-UP can also determine the data and/or signaling of the SDT to be sent based on other information, and/or determine the data and/or signaling of the SDT that needs to be received, and this embodiment of the disclosure does not specifically limit this.
  • S52 Send a first message to the second node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device. After requesting the message, the SDT information is sent and/or received according to the first information.
  • the first message may be a RAN Paging message sent by the first access network device to the second access network device, a Paging message sent by the CU or CU-CP to the DU, or a Paging message sent by the core network node to the access network device. information.
  • the first node may be a node that cannot determine whether the terminal device in the non-connected state is within its coverage, or the first node may be a node that cannot directly communicate with the terminal device in the non-connected state for uplink and downlink information.
  • the sending and receiving node may be a node that cannot determine whether the terminal device in the non-connected state is within its coverage, or the first node may be a node that cannot directly communicate with the terminal device in the non-connected state for uplink and downlink information.
  • the first node when the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage, the first node sends downlink information. If the terminal device in the non-connected state is within the coverage of the first node, Within, it can be ensured that the downlink information can be accurately sent to the terminal device. However, if the terminal device in the non-connected state is not within the coverage of the first node, the downlink information will not be accurately sent to the terminal device. Similarly, for uplink information sent by a terminal device in a non-connected state, if the terminal device in a non-connected state is within the coverage of the first node, it can be guaranteed that the uplink information can be accurately sent to the first node. However, if If the terminal device in the non-connected state is not within the coverage of the first node, the uplink information will not be accurately sent to the first node.
  • the first node sends a first message to the second node, where the first node may send the first message to one or more second nodes, where the first information is used to indicate that the second node receives
  • the first information is used to indicate that the second node receives
  • a second node receives the first request message of the terminal device and sends and/or receives SDT information according to the first information
  • the terminal equipment in the non-connected state transmits and receives uplink and downlink data and/or signaling, that is, it is determined that the terminal equipment in the non-connected state is within the coverage of the second node. Based on this, instruct the second node according to the first Information sending and/or receiving SDT information can accurately send and receive SDT information with terminal equipment in a non-connected state, and can avoid transmission failure and waste of resources.
  • the first node when the first node is a node that cannot directly transmit and receive uplink and downlink information with the terminal device in the non-connected state, the first node cannot send downlink information to the terminal device in the non-connected state and cannot receive the terminal device. Uplink information sent.
  • the first node sends a first message to the second node, where the first node may send the first message to one or more second nodes, where the first information is used to indicate that the second node receives
  • the first information is used to indicate that the second node receives
  • a second node receives the first request message of the terminal device and sends and/or receives SDT information according to the first information
  • the terminal equipment in the non-connected state transmits and receives uplink and downlink data and/or signaling. Based on this, instructing the second node to send and/or receive SDT information according to the first information, the terminal equipment in the non-connected state can accurately communicate with the terminal equipment in the non-connected state. Sending and receiving SDT information can avoid transmission failures and waste of resources.
  • the first node determines that the small data packet needs to be sent and/or received to transmit SDT information, where the information includes data and/or signaling, and sends the first message to the second node, where,
  • the first message includes first information related to the SDT of the terminal device in the non-connected state.
  • the first information is used to instruct the second node to send and/or receive according to the first information after receiving the first request message from the terminal device. SDT information. Therefore, the second node can send and/or receive the SDT information that the first node needs to send and/or receive based on the first information.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the first node determines that the small data packet needs to be sent and/or received to transmit SDT information, where the information includes data and/or signaling, and the first node is a terminal that cannot be determined to be in a non-connected state.
  • the device is a node within its coverage, or a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state, sends the first message to the second node, where the first message includes the link with the terminal device in the non-connected state.
  • the first information related to the SDT of the terminal device in the state is used to instruct the second node to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the first information includes at least one of the following:
  • the first node sends a first message to the second node, and the first message includes first information related to the SDT of the terminal device in a non-connected state, including part of the terminal device context information.
  • part of the terminal device context information is used to receive and send SDT information of the paged terminal device, and may include DRB (data radio bearer, data radio bearer) and/or SRB (signaling radio bearer, signaling radio bearer) used for SDT.
  • Related configuration information of the wireless bearer may include configuration information such as the transmission mode of the RLC (Radio Link Control) layer.
  • the second node may , sending downlink SDT information to the terminal device and/or receiving uplink SDT information from the terminal device, where the downlink SDT information includes downlink SDT data and/or signaling, and the uplink SDT information includes uplink SDT data and/or signaling.
  • the first node sends a first message to the second node.
  • the first message includes first information related to the SDT of the terminal device in a non-connected state, including uplink TNL (UL transport network layer, uplink transmission network layer) information.
  • uplink TNL UL transport network layer, uplink transmission network layer
  • the uplink TNL information is used to indicate the UP transport layer information, and the second node can send uplink SDT information to the first node according to the uplink TNL information, where the uplink SDT information includes uplink SDT data and/or signaling.
  • the first node sends a first message to the second node, and the first message includes first information related to SDT of the terminal device in a non-connected state, including the MT-SDT mode.
  • the second node can consider the MT-SDT method to configure SDT resources and/or for the terminal device. Or prepare SDT-related resources.
  • the first node sends a first message to the second node, and the first message includes first information related to SDT of the terminal device in a non-connected state, including the MT-SDT type.
  • the MT-SDT type can indicate whether the data or signaling transmitted by SDT this time is downlink and/or uplink, or the MT-SDT type can indicate whether the data type transmitted by SDT this time is data or signaling.
  • it can be the following four Any combination of these types is only uplink (DL-only), uplink and downlink (DL+UL), signaling (signalling) and/or data (data), etc.
  • the second node can consider the MT-SDT type as the terminal Device configuration SDT resources and/or resources related to preparing for SDT.
  • the first node sends a first message to the second node, and the first message includes first information related to the SDT of the terminal device in a non-connected state, including the uplink transmission characteristics of the terminal device.
  • the uplink transmission characteristics of the terminal device may be the data size or period of the terminal device's uplink data or signaling, for example, it may be the period and/or size of QoE report reporting or the period and/or size of the terminal device positioning information reporting.
  • the second node can consider the uplink transmission characteristics of the terminal device and allocate relevant resources and configurations of the uplink SDT to the terminal device.
  • the first node sends a first message to the second node, and the first message includes first information related to the SDT of the terminal device in a non-connected state, including the downlink transmission characteristics of the terminal device.
  • the downlink transmission characteristics of the terminal device may be the data size and/or period of the terminal device's downlink data or signaling; in other embodiments, the downlink transmission characteristics of the terminal device may refer to the downlink data or signaling. Is it single or multiple.
  • the second node may consider the downlink transmission characteristics of the terminal device and allocate relevant resources and configurations of the downlink SDT to the terminal device.
  • the second node receives the first message sent by the first node, obtains the first information in the first message, and may consider the first information to configure SDT resources for the terminal device and/or prepare SDT-related resources. , for example: establishing SDT RLC entity.
  • the first node can obtain the downlink transmission characteristics of the terminal device through packet detection and identification by itself; if The first node has a control plane function (such as a base station, SMF/AMF, gNB-CU or gNB-CU-CP).
  • the downlink transmission characteristics of the terminal device can be sent to the first node by other nodes, such as AF (Application Function) to AMF/ SMF is sent, or AMF/SMF is sent to the access network device or gNB-CU or gNB-CU-CP, or UPF is sent to the access network device or gNB-CU-UP.
  • AF Application Function
  • the first node receives a second message sent by the second node, wherein the second message is sent by the second node after receiving the first request message sent by the terminal device, and the second message includes a Second information related to SDT of the connected terminal device.
  • the second information is used to request the first node to send SDT information to the second node.
  • the first request message is the response of the terminal device to the paging of the second node.
  • the second node may consider the first message and the first information and send paging to the terminal device.
  • the terminal device if the terminal device is within the coverage of the second node, or the second node can directly send and receive uplink and downlink information with the terminal device in a non-connected state, it can send a paging to the terminal device, and the terminal device receives After the second node sends the paging, it will send a first request message in response to the paging to the second node.
  • the first request message may be a random access request and/or an RRC Resume Request.
  • it may also carry uplink SDT information.
  • the uplink SDT information includes uplink SDT data and/or or signaling.
  • the second node may send a second message to the first node, where the second message includes the SDT related to the terminal device in the non-connected state.
  • the second information is used to request the first node to send SDT information to the second node.
  • the second message may be a RETRIEVE UE CONTEXT REQUEST message sent by the second access network device to the first access network device, or an initial UL RRC message transmission sent by the DU to the CU or CU-CP.
  • (INITIAL UL RRC MESSAGE TRANSFER) message or other F1AP message or the initial UE context request (INITIAL UE CONTEXT REQUEST) message or other NGAP message sent by the access network device to the core network node.
  • the second node sends a second message to the first node to inform the first node that the terminal device in the non-connected state is within the coverage of the second node, and the second node can send the downlink SDT to the terminal device.
  • the first request message carries the uplink SDT information
  • the second message sent by the second node to the first node includes information about the terminal device in the non-connected state.
  • second information related to SDT to send uplink SDT information to the first node.
  • the second information includes at least one of the following:
  • the second node sends a second message to the first node, the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information includes the MT-SDT indication.
  • the MT-SDT indication is used to indicate that the second message is initiated due to MT-SDT.
  • the resume cause may be MT-SDT.
  • the second node sends a second message to the first node, the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information includes downlink TNL information.
  • the downlink TNL information is used to indicate the UP transport layer information, and the first node can send downlink SDT information to the second node according to the downlink TNL information, where the downlink SDT information includes downlink SDT data and/or signaling.
  • the downlink TNL information is sent in the second message, which allows the downlink SDT information to be sent to the terminal device faster.
  • the first node sends SDT information to the second node according to the second message, where the SDT information includes downlink SDT data and/or signaling.
  • the first node may send SDT information to the second node according to the second message, where the SDT information includes downlink SDT data and/or information. make.
  • the second node when the second node receives the downlink SDT data and/or signaling sent by the first node, it may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately and efficiently transmit and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the first node sends third information to the second node, where the third information includes at least one of the following:
  • the first node sends the third information to the second node, which may be sent at the same time as the first message, or before or after the first message,
  • the third information is included in the first message and/or the third message.
  • the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message.
  • the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or a message on the Xn user plane.
  • the third message may also include an identifier related to the terminal device, such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • an identifier related to the terminal device such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • the first node sends a first message to the second node.
  • the first message includes first information related to the SDT of the terminal device in the non-connected state, and also includes downlink SDT data.
  • the first node sends a first message to the second node.
  • the first message includes first information related to SDT of the terminal device in a non-connected state, and also includes signaling of downlink SDT.
  • the first node sends a first message to the second node.
  • the first message includes first information related to SDT of the terminal device in a non-connected state, and also includes data and signaling of downlink SDT.
  • the second node when the first node sends a first message to the second node, and the first message includes the first information and also includes downlink SDT data and/or signaling, the second node sends a message to the terminal according to the first information.
  • the device sends paging, and when the second node receives the first request message from the terminal device in response to paging, since the second node has received the downlink SDT information sent by the first node, it can directly send the downlink SDT information. to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the first node receives the first indication information sent by the second node, where the first indication information is used to instruct the second node to complete sending the downlink SDT data and/or signaling to the terminal device.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, it may send first indication information to the first node.
  • the first indication information is used to instruct the second node to complete sending the downlink SDT data to the terminal device. SDT data and/or signaling.
  • the first indication information includes at least one of the following:
  • the second node sends first indication information to the first node, and the first indication information may include terminal device identification information.
  • the second node sends first indication information to the first node, and the first indication information may include an indication of successful transmission to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include an indication that is not successfully sent to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include downlink (DL) TNL information.
  • DL downlink
  • the first node receives the second indication information sent by the second node, wherein the second indication information is sent by the second node after receiving the response message sent by the terminal device, and the second indication information Data and/or signaling used to indicate that the second node successfully sends downlink SDT to the terminal device.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, if the terminal device successfully receives the downlink SDT data and/or signaling sent by the second node, it may send the data to the second node.
  • the second node receives the response message sent by the terminal device, and can determine that the terminal device successfully receives the data and/or signaling of the downlink SDT.
  • the second node sends second indication information to the first node, and the second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the second indication information includes at least one of the following:
  • the second node sends second indication information to the first node, and the second indication information includes terminal device identification information.
  • the second node sends second indication information to the first node, and the second indication information includes an indication of successful transmission to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information includes an indication that is not successfully sent to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information may include DL TNL information.
  • the first indication information and/or the second indication information may be SDT delivery notification.
  • the SDT delivery notification is used to notify the first node whether the downlink SDT data and/or signaling has been sent to the terminal device.
  • the first Nodes can consider SDT delivery notification to decide whether to continue paging the terminal device.
  • the first node may determine that the transmission of the downlink SDT information has been completed, and the first node may send a request to the second node.
  • a RETRIEVE UE CONTEXT FAILURE message is sent in response to the first indication information and/or the second indication information of the second node, wherein the RETRIEVE UE CONTEXT FAILURE message includes an encapsulated RRC Release message.
  • the first node is a first access network device
  • the second node is a second access network device
  • the first access network device is the last access network device serving the terminal device
  • the second access network device is the last access network device serving the terminal device.
  • the network access device is the access network device currently serving the terminal device.
  • the first node is the first access network device, which may be the access network device that finally serves the terminal device.
  • the first access network device (the access network device that finally serves the terminal device)
  • the device sends an RRC release (RRCRelease) message to change the state of the terminal device from the connected state (RRC_CONNECTED) to the unconnected state (RRC_IDLE state or RRC_INACTIVE state).
  • RRC release RRCRelease
  • the first access network device cannot determine whether the terminal device is within its coverage at this time, that is, the first access network device
  • the access network device cannot determine whether the terminal device can receive the information it sends to the terminal device, and it cannot determine whether it can accurately receive the information sent by the terminal device.
  • the first access network device may determine the SDT information that needs to be sent and/or received, and send a first message to one or more second access network devices, where the first message includes information related to the SDT in the non-connected state.
  • the second node is a second access network device
  • the second access network device is an access network device currently serving the terminal device.
  • the second access network device can receive the first request message sent by the terminal device, It means that the terminal device in the non-connected state at this time is within the coverage of the second access network device, and the second access network device can send and receive uplink and downlink information with the terminal device in the non-connected state. Therefore, the second access network device
  • the network access device may send SDT information and/or receive SDT information according to the first information. Thus, transmission failure and waste of resources can be avoided.
  • the first access network device serves as the node that finally serves the terminal device, and the terminal device currently in the non-connected state is not within the coverage of the first access network device.
  • the first access network device cannot directly A node that sends and receives uplink and downlink information to terminal devices in a non-connected state.
  • the first access network device sends the first message to the second access network device, and the second access network device can receive the first request message sent by the terminal device, indicating that it is in a non-connected state at this time.
  • the terminal equipment is located within the coverage of the second access network equipment.
  • the second access network equipment can send and receive uplink and downlink information with the terminal equipment in the non-connected state.
  • the second access network equipment can transmit and receive uplink and downlink information according to the first information. , send SDT information and/or receive SDT information. Therefore, the first access network device that cannot determine whether the terminal device in the unconnected state is within its coverage can send and receive uplink and downlink information with the terminal device through the second access network device that currently serves the terminal device. Avoid transmission failures and waste of resources.
  • the first access network device may send the first message to one or more second access network devices.
  • the second access network device is the access network device currently serving the terminal device, that is, when the terminal device in the non-connected state is located within the coverage of the second access network device, Only the second access network device can receive the first request message sent by the terminal device in the non-connected state, that is, the first access network device can send the first message to one or more second access network devices, Only one second access network device can receive the first request message from the terminal device. Based on this, after receiving the first request message from the terminal device, the second access network device sends and/or Receive SDT information.
  • the first message is at least one of the following:
  • Some terminal devices contextually transmit messages
  • the first access network device may send the first message to the second access network device,
  • the first message may be a radio access network RAN paging message.
  • the first access network device may send the first message to the second access network device,
  • the first message may be a partial terminal device context transmission message.
  • the first access network device may send the first message to the second access network device,
  • the first message may be an Xn Application Protocol XnAP message.
  • the second message is at least one of the following:
  • the second node sends a second message to the first node, and may send a terminal device context retrieval request message to the first node.
  • the second node sends the second message to the first node, and may send a part of the terminal device context confirmation message to the first node.
  • the second node sends the second message to the first node, and may send an Xn application protocol XnAP message to the first node.
  • the terminal device when the first access network device is not the access network device that last serves the terminal device, the terminal device is supported to receive downlink data and/or send uplink data in the RRC_INACTIVE state, and the first access network device is Network equipment can also configure appropriate resources for terminal equipment based on the type and characteristics of uplink/downlink data, which can reduce unnecessary scheduling overhead, save air interface resources, and also save power for terminal equipment.
  • the first node is a core network node
  • the second node is an access network device.
  • the first node is a core network node, and the core network node cannot directly send and receive uplink and downlink information with the terminal device in a non-connected state.
  • the second node is an access network device, and the access network device can directly communicate with the terminal device in a non-connected state. Terminal equipment in a non-connected state sends and receives uplink and downlink information.
  • the core network node may determine the SDT information that needs to be sent and/or received, and send a first message to the access network device, where the first message includes a first message related to the SDT of the terminal device in a non-connected state.
  • Information the first information is used to instruct the access network device to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the access network device can receive the first request message from the terminal device, it means that the access network device can directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • core network nodes that cannot directly send and receive uplink and downlink information to non-connected terminal devices can send and receive uplink and downlink information to terminal devices through access network devices, thus avoiding transmission failures and waste of resources.
  • the core network node is at least one of the following:
  • Access and Mobility Management Function AMF Access and Mobility Management Function
  • Session management function device SMF Session management function device
  • the core network node may be an AMF.
  • the core network node may be an SMF.
  • the core network node may be a UPF.
  • the first message is at least one of the following:
  • the core network node when the first node is a core network node and the second node is an access network device, the core network node sends a first message to the access network device, and may send an NGAP message to the access network device, for example :Paging message.
  • the core network node when the first node is a core network node and the second node is an access network device, the core network node sends a first message to the access network device, and may send a message included in the user plane to the access network device. Messages in data.
  • the first node is the centralized unit user plane CU-UP
  • the second node is the centralized unit control plane CU-CP.
  • the first node is CU-UP, which cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • the second node is CU-CP, and the CU-CP can directly communicate with the terminal device in the non-connected state.
  • the connected terminal equipment sends and receives uplink and downlink information.
  • the CU-UP may determine the SDT information that needs to be sent and/or received, and send a first message to the CU-CP.
  • the first message includes the first information related to the SDT of the terminal device in the non-connected state. , the first information is used to instruct the CU-CP to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the CU-CP can receive the first request message from the terminal device, it means that the CU-CP can directly send and receive uplink and downlink information with the terminal device in the non-connected state. Therefore, the CU-UP, which cannot directly send and receive uplink and downlink information to the terminal device in the unconnected state, can send and receive uplink and downlink information to the terminal device through the CU-CP, thus avoiding transmission failure and waste of resources.
  • the first message is at least one of the following:
  • CU-UP when the first node is CU-UP and the second node is CU-CP, CU-UP sends a first message to CU-CP, and may send a downlink data notification message (DL Data) to CU-CP. Notification).
  • DL Data downlink data notification message
  • CU-UP when the first node is CU-UP and the second node is CU-CP, CU-UP sends a first message to CU-CP, and may send a bearer context modification requirement message (BEARER) to CU-CP. CONTEXT MODIFICATION REQUIRED).
  • BEARER bearer context modification requirement message
  • CU-UP when the first node is CU-UP and the second node is CU-CP, CU-UP sends the first message to CU-CP, and may send an E1 application protocol E1AP message to CU-CP.
  • the first node is the centralized unit CU or CU-CP
  • the second node is the distribution unit DU.
  • the first node is CU or CU-CP.
  • CU or CU-CP cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • the second node is DU.
  • DU can directly communicate with the terminal device in the non-connected state.
  • the connected terminal equipment sends and receives uplink and downlink information.
  • the CU or CU-CP may determine that SDT information needs to be sent and/or received, and send a first message to the DU, where the first message includes a first message related to the SDT of the terminal device in the non-connected state.
  • Information the first information is used to instruct the DU to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the DU can receive the first request message from the terminal device, it means that the DU can directly send and receive uplink and downlink information with the terminal device in the non-connected state. Therefore, a CU or CU-CP that cannot directly send and receive uplink and downlink information to the terminal device in the unconnected state can send and receive uplink and downlink information to the terminal device through the DU, thus avoiding transmission failure and waste of resources.
  • the first message is at least one of the following:
  • the CU or CU-CP when the first node is a CU or CU-CP and the second node is a DU, the CU or CU-CP sends the first message to the DU, and may send a paging message (Paging) to the DU.
  • Paging paging message
  • the CU or CU-CP when the first node is a CU or CU-CP, and the second node is a DU, the CU or CU-CP sends a first message to the DU, and may send a terminal device context modification request message (UE CONTEXT MODIFICATION REQUEST).
  • UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION REQUEST
  • the CU or CU-CP when the first node is a CU or CU-CP, and the second node is a DU, the CU or CU-CP sends a first message to the DU, and may send a terminal device context establishment request message (UE CONTEXT SETUP REQUEST).
  • UE CONTEXT SETUP REQUEST UE CONTEXT SETUP REQUEST
  • the CU or CU-CP when the first node is a CU or CU-CP and the second node is a DU, the CU or CU-CP sends the first message to the DU, and may send an F1 application protocol F1AP message to the DU.
  • the second message is at least one of the following:
  • the second node sends a second message to the first node, and the second message may be a notification message sent by SDT.
  • the second node sends a second message to the first node, and the second message may be an initial uplink (UL) RRC message transmission message.
  • UL uplink
  • the second node sends a second message to the first node, and the second message may be an F1 application protocol F1AP message.
  • the first node is the first access network device that finally serves the terminal device.
  • the terminal device currently in the non-connected state is within the coverage of the second node, and the second node is the second access network device.
  • the first access network device cannot determine whether the terminal device in the non-connected state is within its coverage.
  • 1) the first access network device can send the first message to the second access network device ( RAN paging), the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information includes at least one of the following:
  • the second access network device After receiving the RAN paging sent by the first access network device, the second access network device will send the paging to the terminal device within its coverage.
  • the terminal device will send a first request message in response to paging to the second access network device.
  • the first request message may be RA/ RRCResume Request
  • the second access network device receives the first request message sent by the terminal device, and can determine that the terminal device in the non-connected state at this time is within its coverage, and the second access network device can communicate with the terminal device
  • the second access network device sends a second message (RETRIEVE UE CONTEXT REQUEST message) to the first access network device to obtain the downlink SDT information from the first access network device, where the second The message includes second information, and the second information includes at least one of the following:
  • the first access network device sends the downlink SDT information to the second access network device according to the second information in the RETRIEVE UE CONTEXT REQUEST message sent by the second access network device.
  • the second access network device can further Downlink SDT information is sent to the terminal device.
  • the first request message sent by the terminal device to the second access network device can carry the uplink SDT information
  • the second access network device receives the first request message sent by the terminal device, and can carry the uplink SDT information. The information is sent to the first access network device.
  • the first access network device may send a RETRIEVE UE CONTEXT FAILURE message to the second access network device in response to the first An access network device, wherein the RETRIEVE UE CONTEXT FAILURE message includes an encapsulated RRC Release message.
  • the second access network device can send an RRC Release message to the terminal device. After receiving the RRC Release message, the terminal device can remain in a non-connected state.
  • the first node is the first access network device that finally serves the terminal device.
  • the terminal device currently in the non-connected state is within the coverage of the second node, and the second node is the second access network device.
  • the first access network device cannot determine whether the terminal device in the non-connected state is within its coverage.
  • 1) the first access network device can send the first message to the second access network device ( RAN paging), the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information includes at least one of the following:
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message. It can be understood that the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message. Wherein, the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or a message on the Xn user plane.
  • the third message may also include an identifier related to the terminal device, such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • an identifier related to the terminal device such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • the second access network device After receiving the RAN paging sent by the first access network device, the second access network device will send the paging to the terminal device within its coverage.
  • the terminal device will send a first request message in response to paging to the second access network device.
  • the first request message may be RA/ RRCResume Request, 4)
  • the second access network device receives the first request message sent by the terminal device, and can determine that the terminal device in the non-connected state at this time is within its coverage, and the second access network device can communicate with the terminal device To send and receive uplink and downlink information, the second access network device may send downlink SDT data and/or signaling to the terminal device.
  • the second access network device may send first indication information to the first access network device to inform the first access network device of the downlink SDT data. and/or signaling has been sent to the terminal device, or second indication information can be sent to the first access network device to inform the first access network device that the data and/or signaling of the downlink SDT has been successfully sent to the terminal. equipment.
  • the first indication information and the second indication information include DL TNL information, so that the first network device can send subsequent downlink SDT information to the terminal device through the second network device more quickly.
  • FIG. 6 is a flow chart of another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the first node.
  • the method may include but is not limited to the following steps:
  • S61 Determine the information of the small data packet that needs to be sent and/or received to transmit SDT, where the information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage. , or it is a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • S62 Send a first message to the second node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device. After requesting the message, the SDT information is sent and/or received according to the first information.
  • the first information includes at least one of the following:
  • S63 Receive a second message sent by the second node, where the second message is sent by the second node after receiving the first request message sent by the terminal device, and the second message includes an SDT with the terminal device in a non-connected state. Related second information, the second information is used to request the first node to send SDT information to the second node, and the first request message is a response of the terminal device to the paging of the second node.
  • the second node may consider the first message and the first information and send paging to the terminal device.
  • the terminal device if the terminal device is within the coverage of the second node, or the second node can directly send and receive uplink and downlink information with the terminal device in a non-connected state, it can send a paging to the terminal device, and the terminal device receives After the second node sends the paging, it will send a first request message in response to the paging to the second node.
  • the first request message may be a random access request and/or an RRC Resume Request.
  • it may also carry uplink SDT information, and the uplink SDT information includes uplink SDT data and/or signaling.
  • the second node may send a second message to the first node, where the second message includes the SDT related to the terminal device in the non-connected state.
  • the second information is used to request the first node to send SDT information to the second node.
  • the second message may be a RETRIEVE UE CONTEXT REQUEST message.
  • the second node sends a second message to the first node to inform the first node that the terminal device in the non-connected state is within the coverage of the second node, and the second node can send the downlink SDT to the terminal device.
  • the first request message carries the uplink SDT information
  • the second message sent by the second node to the first node includes information about the terminal device in the non-connected state.
  • second information related to SDT to send uplink SDT information to the first node.
  • the second information includes at least one of the following:
  • the second node sends a second message to the first node, the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information includes the MT-SDT indication.
  • the MT-SDT indication is used to indicate that the second message is initiated due to MT-SDT.
  • the resume cause may be MT-SDT.
  • the second node sends a second message to the first node, the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information includes downlink TNL information.
  • the downlink TNL information is used to indicate the UP transport layer information, and the first node can send downlink SDT information to the second node according to the downlink TNL information, where the downlink SDT information includes downlink SDT data and/or signaling.
  • S64 According to the second message, send the SDT information to the second node, where the SDT information includes downlink SDT data and/or signaling.
  • the first node may send SDT information to the second node according to the second message, where the SDT information includes downlink SDT data and/or information. make.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S61 to S63 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S51 and S52 in the embodiment of the present disclosure. , the embodiment of the present disclosure does not limit this.
  • FIG. 7 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the first node.
  • the method may include but is not limited to the following steps:
  • S71 Determine the information of the small data packet that needs to be sent and/or received to transmit SDT, where the information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage. , or it is a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • S72 Send a first message to the second node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device. After requesting the message, the SDT information is sent and/or received according to the first information.
  • the first information includes at least one of the following:
  • S73 Receive the second message sent by the second node, where the second message is sent by the second node after receiving the first request message sent by the terminal device, and the second message includes the SDT with the terminal device in the non-connected state.
  • the second information is used to request the first node to send SDT information to the second node, and the first request message is a response of the terminal device to the paging of the second node.
  • S74 According to the second message, send the SDT information to the second node, where the SDT information includes downlink SDT data and/or signaling.
  • S75 Receive the first indication information sent by the second node, where the first indication information is used to instruct the second node to complete sending the downlink SDT data and/or signaling to the terminal device.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, it may send first indication information to the first node.
  • the first indication information is used to instruct the second node to complete sending the downlink SDT data to the terminal device. SDT data and/or signaling.
  • the first indication information includes at least one of the following:
  • the second node sends first indication information to the first node, and the first indication information may include terminal device identification information.
  • the second node sends first indication information to the first node, and the first indication information may include an indication of successful transmission to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include an indication that is not successfully sent to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include DL TNL information.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S71 to S75 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S51 and S52 and/or in the embodiment of the present disclosure.
  • S61 to S63 are implemented together, and the embodiment of the present disclosure does not limit this.
  • FIG. 8 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the first node.
  • the method may include but is not limited to the following steps:
  • S81 Determine the information of the small data packet that needs to be sent and/or received to transmit SDT, where the information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage. , or it is a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • S82 Send a first message to the second node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device. After requesting the message, the SDT information is sent and/or received according to the first information.
  • the first information includes at least one of the following:
  • S83 Receive the second message sent by the second node, where the second message is sent by the second node after receiving the first request message sent by the terminal device, and the second message includes the SDT with the terminal device in the non-connected state. Related second information, the second information is used to request the first node to send SDT information to the second node, and the first request message is a response of the terminal device to the paging of the second node.
  • S84 According to the second message, send the SDT information to the second node, where the SDT information includes downlink SDT data and/or signaling.
  • S85 Receive the second indication information sent by the second node, where the second indication information is sent by the second node after receiving the response message sent by the terminal device, and the second indication information is used to indicate that the second node successfully sends the message to The terminal equipment sends data and/or signaling of downlink SDT.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, if the terminal device successfully receives the downlink SDT data and/or signaling sent by the second node, it may send the data to the second node.
  • the second node receives the response message sent by the terminal device, and can determine that the terminal device successfully receives the data and/or signaling of the downlink SDT.
  • the second node sends second indication information to the first node, and the second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the second indication information includes at least one of the following:
  • the second node sends second indication information to the first node, and the second indication information includes terminal device identification information.
  • the second node sends second indication information to the first node, and the second indication information includes an indication of successful transmission to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information includes an indication that is not successfully sent to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information may include DL TNL information.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S81 to S85 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S51 and S52 and/or in the embodiment of the present disclosure.
  • S61 to S63 are implemented together, and the embodiment of the present disclosure does not limit this.
  • FIG. 9 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the first node.
  • the method may include but is not limited to the following steps:
  • S91 Determine the information of the small data packet that needs to be sent and/or received to transmit SDT, where the information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage. , or it is a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • S92 Send a first message to the second node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device. After requesting the message, the SDT information is sent and/or received according to the first information.
  • the first information includes at least one of the following:
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message. It can be understood that the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message. Wherein, the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or a message on the Xn user plane.
  • the third message may also include an identifier related to the terminal device, such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • an identifier related to the terminal device such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • the second node when the first node sends a first message to the second node, and the first message includes the first information and also includes downlink SDT data and/or signaling, the second node sends a message to the terminal according to the first information.
  • the device sends paging, and when the second node receives the first request message from the terminal device in response to paging, since the second node has received the downlink SDT information sent by the first node, it can directly send the downlink SDT information. to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S93 Receive the first indication information sent by the second node, where the first indication information is used to instruct the second node to complete sending the downlink SDT data and/or signaling to the terminal device.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S91 to S93 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S51 and S52 in the embodiment of the present disclosure. , the embodiment of the present disclosure does not limit this.
  • Figure 10 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the first node.
  • the method may include but is not limited to the following steps:
  • S101 Determine the information of the small data packet that needs to be sent and/or received to transmit SDT, where the information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage. , or it is a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • S102 Send a first message to the second node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device. After requesting the message, the SDT information is sent and/or received according to the first information.
  • the first information includes at least one of the following:
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message. It can be understood that the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message. Wherein, the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or a message on the Xn user plane.
  • the third message may also include an identifier related to the terminal device, such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • an identifier related to the terminal device such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • the second node when the first node sends a first message to the second node, and the first message includes the first information and also includes downlink SDT data and/or signaling, the second node sends a message to the terminal according to the first information.
  • the device sends paging, and when the second node receives the first request message from the terminal device in response to paging, since the second node has received the downlink SDT information sent by the first node, it can directly send the downlink SDT information. to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S103 Receive the second indication information sent by the second node, where the second indication information is sent by the second node after receiving the response message sent by the terminal device, and the second indication information is used to indicate that the second node successfully sends the message to the terminal device.
  • the terminal equipment sends data and/or signaling of downlink SDT.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S101 to S103 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S51 and S52 in the embodiment of the present disclosure. , the embodiment of the present disclosure does not limit this.
  • Figure 11 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S111 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first message may be a RAN Paging message sent by the first access network device to the second access network device, a Paging message sent by the CU or CU-CP to the DU, or a Paging message sent by the core network node to the access network device. information.
  • the first node may be a node that cannot determine whether the terminal device in the non-connected state is within its coverage, or the first node may be a node that cannot directly communicate with the terminal device in the non-connected state for uplink and downlink information.
  • the sending and receiving node may be a node that cannot determine whether the terminal device in the non-connected state is within its coverage, or the first node may be a node that cannot directly communicate with the terminal device in the non-connected state for uplink and downlink information.
  • the first node when the first node is a node that cannot determine whether the terminal device in the non-connected state is within its coverage, the first node sends downlink information. If the terminal device in the non-connected state is within the coverage of the first node, Within, it can be ensured that the downlink information can be accurately sent to the terminal device. However, if the terminal device in the non-connected state is not within the coverage of the first node, the downlink information will not be accurately sent to the terminal device. Similarly, for uplink information sent by a terminal device in a non-connected state, if the terminal device in a non-connected state is within the coverage of the first node, it can be guaranteed that the uplink information can be accurately sent to the first node. However, if If the terminal device in the non-connected state is not within the coverage of the first node, the uplink information will not be accurately sent to the first node.
  • the first node sends a first message to the second node, where the first node may send the first message to one or more second nodes, where the first information is used to indicate that the second node receives
  • the first information is used to indicate that the second node receives
  • a second node receives the first request message of the terminal device and sends and/or receives SDT information according to the first information
  • the terminal device in the non-connected state transmits and receives uplink and downlink data, that is, it is determined that the terminal device in the non-connected state is within the coverage of the second node. Based on this, the second node is instructed to send and/or transmit according to the first information.
  • Receiving SDT information can accurately send and receive SDT information to terminal devices in a non-connected state, thus avoiding transmission failures and waste of resources.
  • the first node when the first node is a node that cannot directly transmit and receive uplink and downlink information with the terminal device in the non-connected state, the first node cannot send downlink information to the terminal device in the non-connected state and cannot receive the terminal device. Uplink information sent.
  • the first node sends a first message to the second node, where the first node may send the first message to one or more second nodes, where the first information is used to indicate that the second node receives
  • the first information is used to indicate that the second node receives
  • a second node receives the first request message of the terminal device and sends and/or receives SDT information according to the first information
  • the terminal device in the non-connected state transmits and receives uplink and downlink data.
  • the second node is instructed to send and/or receive the SDT information according to the first information, so that the terminal device in the non-connected state can accurately communicate with the terminal device in the non-connected state. Transmitting and receiving can avoid transmission failures and waste of resources.
  • the first node determines that the small data packet needs to be sent and/or received to transmit SDT information, where the information includes data and/or signaling, and sends the first message to the second node, where,
  • the first message includes first information related to the SDT of the terminal device in the non-connected state.
  • the first information is used to instruct the second node to send and/or receive according to the first information after receiving the first request message from the terminal device. SDT information. Therefore, the second node can send and/or receive the SDT information that the first node needs to send and/or receive based on the first information.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the first message is sent when the first node determines that the small data packet needs to be sent and/or received to transmit SDT information, where the information includes data and/or signaling.
  • the first node determines the SDT information that needs to be sent, may determine the SDT data that needs to be sent, or determines the SDT signaling that needs to be sent, or determines the SDT data and signaling that needs to be sent.
  • the first node determines the SDT information that needs to be received, may determine the SDT data that needs to be received, or determines the SDT signaling that needs to be received, or determines the SDT data and signaling that needs to be received.
  • the first node determines the SDT information that needs to be sent and received, may determine the SDT data that needs to be sent and received, or determines the SDT signaling that needs to be sent and received, or determines the SDT data and signaling.
  • the first node determines the SDT information that needs to be sent and/or received, may determine the SDT information that needs to be sent to the terminal device in the non-connected state, and/or determines that it needs to receive the SDT information from the terminal device in the non-connected state. SDT information of the terminal device.
  • the first node may be an access network device.
  • the access network device determines the SDT information that needs to be sent and/or received, the SDT data and/or signaling that needs to be sent, and the access network device that needs to be received. SDT data and/or signaling.
  • the access network device can obtain the SDT data and/or signaling that needs to be sent from the core network node to determine the SDT data and/or signaling that needs to be sent, and the access network device can according to the SDT data and/or signaling sent by it. SDT data and/or signaling, determine whether there is SDT data and/or signaling that needs to be received.
  • the access network device can also determine the data and/or signaling of the SDT to be sent based on other information, and/or determine the data and/or signaling of the SDT to be received, which is not specifically limited in this embodiment of the disclosure.
  • the first node may be a core network node, such as: AMF (Core Access and MobilityManagement Function, access and mobility management function), or UPF (User Plane Function, user plane function device), or SMF (Session Management Function, session management function device), etc.
  • AMF Core Access and MobilityManagement Function, access and mobility management function
  • UPF User Plane Function, user plane function device
  • SMF Session Management Function, session management function device
  • the core network node determines the SDT information that needs to be sent and/or received, can determine the SDT data and/or signaling that needs to be sent, and can determine the SDT data and/or signaling that needs to be received.
  • the core network node can determine the SDT data and/or signaling that needs to be sent based on its own information, and the core network node can determine whether there is any SDT data and/or signaling that needs to be received based on the SDT data and/or signaling it sends. SDT data and/or signaling.
  • the core network node can also determine the data and/or signaling of the SDT to be sent based on other information, and/or determine the data and/or signaling of the SDT to be received, which is not specifically limited in the embodiments of the present disclosure.
  • the first node may be a centralized unit CU, or a centralized unit user plane CU-UP.
  • the CU or CU-UP determines the SDT information that needs to be sent and/or received, may determine the SDT data and/or signaling that needs to be sent, and may determine the SDT data and/or signaling that needs to be received.
  • the CU or CU-UP can communicate with the core network node, obtain the data and/or signaling of the SDT that needs to be sent from the core network node, to determine the data and/or signaling of the SDT that needs to be sent, and, the CU or The CU-UP may determine whether there is data and/or signaling of the SDT that needs to be received based on the data and/or signaling of the SDT it sends.
  • the CU or CU-UP can also determine the data and/or signaling of the SDT to be sent based on other information, and/or determine the data and/or signaling of the SDT that needs to be received, and this embodiment of the disclosure does not specifically limit this.
  • the first node determines that the small data packet needs to be sent and/or received to transmit SDT information, where the information includes data and/or signaling, and the first node is a terminal that cannot be determined to be in a non-connected state.
  • the device is a node within its coverage, or a node that cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state, sends the first message to the second node, where the first message includes the link with the terminal device in the non-connected state.
  • the first information related to the SDT of the terminal device in the state is used to instruct the second node to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the second node receives a first request message sent by the terminal device, where the first request message is used to indicate data and/or signaling of the uplink SDT.
  • the second node receives the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate to the second node
  • SDT information is sent and/or received according to the first information, and the information includes data and/or signaling.
  • the second node when the second node receives the first request message sent by the terminal device, and the first request message is used to indicate the data and/or signaling of the uplink SDT, the second node may send the first request message to the first node according to the first information. Data and/or signaling of uplink SDT.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the second node sends paging to the terminal device according to the first message; and receives a first request message sent by the terminal device, where the first request message is a response of the terminal device to the paging of the second node.
  • the second node may consider the first message and the first information and send paging to the terminal device.
  • the terminal device if the terminal device is within the coverage of the second node, or the second node can directly send and receive uplink and downlink information with the terminal device in a non-connected state, it can send a paging to the terminal device, and the terminal device receives After the second node sends the paging, it will send a first request message in response to the paging to the second node.
  • the first request message may be a random access request and/or an RRC Resume Request.
  • the terminal device sends a first request message in response to paging to the second node.
  • the first request message may carry uplink SDT information
  • the uplink SDT information includes uplink SDT data and/or signaling.
  • the second node may send uplink SDT information to the first node and send uplink SDT data and/or signaling to the first node.
  • the second node configures SDT resources for the terminal device according to the first information.
  • the terminal device sends a first request message in response to paging to the second node.
  • the first request message may carry uplink SDT information
  • the uplink SDT information includes uplink SDT data and/or signaling.
  • the second node may configure SDT resources for the terminal device according to the first request message and the first message. This allows the second node to configure appropriate resources for the terminal device according to the type and characteristics of the uplink data, thereby reducing unnecessary scheduling overhead, saving air interface resources, and also saving power for the terminal device.
  • the first information related to SDT is released.
  • the second node receives the first message sent by the first node and sends paging to the terminal device. If it does not receive the first request message sent by the terminal device, it can be determined that the terminal device in the non-connected state is not present. It is within the coverage of the second node, or the second node cannot directly send and receive uplink and downlink information with the terminal device in a non-connected state. In this case, the second node releases the first information related to SDT.
  • the first information includes at least one of the following:
  • the first node sends a first message to the second node, and the first message includes first information related to the SDT of the terminal device in a non-connected state, including part of the terminal device context information.
  • part of the terminal device context information is used to receive and send SDT information of the paged terminal device, and may include DRB (data radio bearer, data radio bearer) and/or SRB (signaling radio bearer, signaling radio bearer) used for SDT.
  • DRB data radio bearer, data radio bearer
  • SRB signaling radio bearer
  • the second node can send downlink SDT information to the terminal device and/or receive uplink SDT information from the terminal device according to part of the terminal device context information, where,
  • the information of the downlink SDT includes the data and/or signaling of the downlink SDT
  • the information of the uplink SDT includes the data and/or signaling of the uplink SDT.
  • the first node sends a first message to the second node.
  • the first message includes first information related to the SDT of the terminal device in a non-connected state, including uplink TNL (UL transport network layer, uplink transmission network layer) information.
  • uplink TNL UL transport network layer, uplink transmission network layer
  • the uplink TNL information is used to indicate the UP transport layer information, and the second node can send uplink SDT information to the first node according to the uplink TNL information, where the uplink SDT information includes uplink SDT data and/or signaling.
  • the first node sends a first message to the second node, and the first message includes first information related to SDT of the terminal device in a non-connected state, including the MT-SDT mode.
  • the second node can consider the MT-SDT method to configure SDT resources and/or for the terminal device. Or prepare SDT-related resources.
  • the first node sends a first message to the second node, and the first message includes first information related to SDT of the terminal device in a non-connected state, including the MT-SDT type.
  • the MT-SDT type can indicate whether the data or signaling transmitted by SDT this time is downlink and/or uplink, or the MT-SDT type can indicate whether the data type transmitted by SDT this time is data or signaling.
  • it can be the following four Any combination of these types is only uplink (DL-only), uplink and downlink (DL+UL), signaling (signalling) and/or data (data), etc.
  • the second node can consider the MT-SDT type as the terminal Device configuration SDT resources and/or resources related to preparing for SDT.
  • the first node sends a first message to the second node, and the first message includes first information related to the SDT of the terminal device in a non-connected state, including the uplink transmission characteristics of the terminal device.
  • the uplink transmission characteristics of the terminal device may be the data size or period of the terminal device's uplink data or signaling. For example, it may be the period and size of the QoE report reporting or the period and size of the terminal device positioning information reporting.
  • the second node may consider The uplink transmission characteristics of the terminal equipment allocate the relevant resources and configuration of the uplink SDT to the terminal equipment.
  • the first node sends a first message to the second node, and the first message includes first information related to the SDT of the terminal device in a non-connected state, including the downlink transmission characteristics of the terminal device.
  • the downlink transmission characteristics of the terminal equipment may be the data size or period of the terminal equipment's downlink data or signaling; in other embodiments, the downlink transmission characteristics of the terminal equipment may refer to the downlink data or signaling being a single Or multiple.
  • the second node may consider the downlink transmission characteristics of the terminal device and allocate relevant resources and configurations of the downlink SDT to the terminal device.
  • the second node receives the first message sent by the first node, obtains the first information in the first message, and may consider the first information to configure SDT resources for the terminal device and/or prepare SDT-related resources. , for example: establishing SDT RLC entity.
  • the first node can obtain the downlink transmission characteristics of the terminal device through packet detection and identification by itself; if The first node has a control plane function (such as a base station, SMF/AMF, gNB-CU or gNB-CU-CP).
  • the downlink transmission characteristics of the terminal device can be sent to the first node by other nodes, such as AF (Application Function) to AMF/ SMF is sent, or AMF/SMF is sent to the access network device or gNB-CU or gNB-CU-CP, or UPF is sent to the access network device or gNB-CU-UP.
  • AF Application Function
  • the second node sends a second message to the first node, where the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information is used to request the first node to send The second node sends SDT information.
  • the second node may consider the first message and the first information and send paging to the terminal device.
  • the terminal device if the terminal device is within the coverage of the second node, or the second node can directly send and receive uplink and downlink information with the terminal device in a non-connected state, it can send a paging to the terminal device, and the terminal device receives After the second node sends the paging, it will send a first request message in response to the paging to the second node.
  • the first request message may be a random access request and/or an RRC Resume Request.
  • it may also carry uplink SDT information, and the uplink SDT information includes uplink SDT data and/or signaling.
  • the second node may send a second message to the first node, where the second message includes the SDT related to the terminal device in the non-connected state.
  • the second information is used to request the first node to send SDT information to the second node.
  • the second message may be a RETRIEVE UE CONTEXT REQUEST message.
  • the second node sends a second message to the first node to inform the first node that the terminal device in the non-connected state is within the coverage of the second node, and the second node can send the downlink SDT to the terminal device.
  • the first request message carries the uplink SDT information
  • the second message sent by the second node to the first node includes information about the terminal device in the non-connected state.
  • second information related to SDT to send uplink SDT information to the first node.
  • the second information includes at least one of the following:
  • the second node sends a second message to the first node, the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information includes the MT-SDT indication.
  • the MT-SDT indication is used to indicate that the second message is initiated due to MT-SDT.
  • the resume cause may be MT-SDT.
  • the second node sends a second message to the first node, the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information includes downlink TNL information.
  • the downlink TNL information is used to indicate the UP transport layer information, and the first node can send downlink SDT information to the second node according to the downlink TNL information, where the downlink SDT information includes downlink SDT data and/or signaling.
  • the second node receives the SDT information sent by the first node, where the SDT information is sent by the first node according to the second message, and the SDT information includes downlink SDT data and/or signaling.
  • the first node may send SDT information to the second node according to the second message, where the SDT information includes downlink SDT data and/or information. make.
  • the second node when it receives the downlink SDT data and/or signaling sent by the first node, it may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message. It can be understood that the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message. Wherein, the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or a message on the Xn user plane.
  • the third message may also include an identifier related to the terminal device, such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • an identifier related to the terminal device such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • the first node sends a first message to the second node.
  • the first message includes first information related to the SDT of the terminal device in the non-connected state, and also includes downlink SDT data.
  • the first node sends a first message to the second node.
  • the first message includes first information related to SDT of the terminal device in a non-connected state, and also includes signaling of downlink SDT.
  • the first node sends a first message to the second node.
  • the first message includes first information related to the SDT of the terminal device in the non-connected state, and also includes the data and signaling of the downlink SDT. .
  • the second node when the first node sends a first message to the second node, and the first message includes the first information and also includes downlink SDT data and/or signaling, the second node sends a message to the terminal according to the first information.
  • the device sends paging, and when the second node receives the first request message from the terminal device in response to paging, since the second node has received the downlink SDT information sent by the first node, it can directly send the downlink SDT information. to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the second node sends downlink SDT data and/or signaling to the terminal device.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • the second node sends first indication information to the first node, where the first indication information is used to instruct the second node to complete sending the downlink SDT data and/or signaling to the terminal device.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, it may send first indication information to the first node.
  • the first indication information is used to instruct the second node to complete sending the downlink SDT data to the terminal device. SDT data and/or signaling.
  • the first indication information includes at least one of the following:
  • the second node sends first indication information to the first node, and the first indication information may include terminal device identification information.
  • the second node sends first indication information to the first node, and the first indication information may include an indication of successful transmission to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include an indication that is not successfully sent to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include DL TNL information.
  • the second node receives a response message sent by the terminal device, where the response message is used to indicate that the terminal device has received the data and/or signaling of the downlink SDT.
  • the second node sends second indication information to the first node, where the second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, if the terminal device successfully receives the downlink SDT data and/or signaling sent by the second node, it may send the data to the second node.
  • the second node receives the response message sent by the terminal device, and can determine that the terminal device successfully receives the data and/or signaling of the downlink SDT.
  • the second node sends second indication information to the first node, and the second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the second indication information includes at least one of the following:
  • the second node sends second indication information to the first node, and the second indication information includes terminal device identification information.
  • the second node sends second indication information to the first node, and the second indication information includes an indication of successful transmission to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information includes an indication that is not successfully sent to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information may include DL TNL information.
  • the first indication information and/or the second indication information may be SDT delivery notification.
  • the SDT delivery notification is used to notify the first node whether the downlink SDT data and/or signaling has been sent to the terminal device.
  • the first Nodes can consider SDT delivery notification to decide whether to continue paging the terminal device.
  • the first node may determine that the transmission of the downlink SDT information has been completed, and the first node may send a request to the second node.
  • a RETRIEVE UE CONTEXT FAILURE message is sent in response to the first indication information and/or the second indication information of the second node, wherein the RETRIEVE UE CONTEXT FAILURE message includes an encapsulated RRC Release message.
  • the first node is a first access network device
  • the second node is a second access network device
  • the first access network device is the last access network device serving the terminal device
  • the second access network device is the last access network device serving the terminal device.
  • the network access device is the access network device currently serving the terminal device.
  • the first node is the first access network device, which may be the access network device that finally serves the terminal device.
  • the first access network device (the access network device that finally serves the terminal device)
  • the device sends an RRC release (RRCRelease) message to change the state of the terminal device from the connected state (RRC_CONNECTED) to the unconnected state (RRC_IDLE state or RRC_INACTIVE state).
  • RRC release RRCRelease
  • the first access network device cannot determine whether the terminal device is within its coverage at this time, that is, the first access network device
  • the access network device cannot determine whether the terminal device can receive the information it sends to the terminal device, and it cannot determine whether it can accurately receive the information sent by the terminal device.
  • the first access network device may determine the SDT information that needs to be sent and/or received, and send a first message to one or more second access network devices, where the first message includes information related to the SDT in the non-connected state.
  • the second node is a second access network device
  • the second access network device is an access network device currently serving the terminal device.
  • the second access network device can receive the first request message sent by the terminal device, It means that the terminal device in the non-connected state at this time is within the coverage of the second access network device, and the second access network device can send and receive uplink and downlink information with the terminal device in the non-connected state. Therefore, the second access network device
  • the network access device may send SDT information and/or receive SDT information according to the first information. Thus, transmission failure and waste of resources can be avoided.
  • the first access network device serves as the node that finally serves the terminal device, and the terminal device currently in the non-connected state is not within the coverage of the first access network device.
  • the first access network device cannot directly A node that sends and receives uplink and downlink information to terminal devices in a non-connected state.
  • the first access network device sends the first message to the second access network device, and the second access network device can receive the first request message sent by the terminal device, indicating that it is in a non-connected state at this time.
  • the terminal equipment is located within the coverage of the second access network equipment.
  • the second access network equipment can send and receive uplink and downlink information with the terminal equipment in the non-connected state.
  • the second access network equipment can transmit and receive uplink and downlink information according to the first information. , send SDT information and/or receive SDT information. Therefore, the first access network device that cannot determine whether the terminal device in the unconnected state is within its coverage can send and receive uplink and downlink information with the terminal device through the second access network device that currently serves the terminal device. Avoid transmission failures and waste of resources.
  • the first access network device may send the first message to one or more second access network devices.
  • the second access network device is the access network device currently serving the terminal device, that is, when the terminal device in the non-connected state is located within the coverage of the second access network device, Only the second access network device can receive the first request message sent by the terminal device in the non-connected state, that is, the first access network device can send the first message to one or more second access network devices, Only one second access network device can receive the first request message from the terminal device. Based on this, after receiving the first request message from the terminal device, the second access network device sends and/or Receive SDT information.
  • the first message is at least one of the following:
  • Some terminal devices contextually transmit messages
  • the first access network device may send the first message to the second access network device,
  • the first message may be a radio access network RAN paging message.
  • the first access network device may send the first message to the second access network device,
  • the first message may be a partial terminal device context transmission message.
  • the first access network device may send the first message to the second access network device,
  • the first message may be an Xn Application Protocol XnAP message.
  • the second message is at least one of the following:
  • the second node sends a second message to the first node, and may send a terminal device context retrieval request message to the first node.
  • the second node sends the second message to the first node, and may send a part of the terminal device context confirmation message to the first node.
  • the second node sends the second message to the first node, and may send an Xn application protocol XnAP message to the first node.
  • the terminal device when the first access network device is not the access network device that last serves the terminal device, the terminal device is supported to receive downlink data and/or send uplink data in the RRC_INACTIVE state, and the first access network device is Network equipment can also configure appropriate resources for terminal equipment based on the type and characteristics of uplink/downlink data, which can reduce unnecessary scheduling overhead, save air interface resources, and also save power for terminal equipment.
  • the first node is a core network node
  • the second node is an access network device.
  • the first node is a core network node, and the core network node cannot directly send and receive uplink and downlink information with the terminal device in a non-connected state.
  • the second node is an access network device, and the access network device can directly communicate with the terminal device in a non-connected state. Terminal equipment in a non-connected state sends and receives uplink and downlink information.
  • the core network node may determine the SDT information that needs to be sent and/or received, and send a first message to the access network device, where the first message includes a third message related to the SDT of the terminal device in the non-connected state.
  • the first information is used to instruct the access network device to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the access network device can receive the first request message from the terminal device, it means that the access network device can directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • core network nodes that cannot directly send and receive uplink and downlink information to non-connected terminal devices can send and receive uplink and downlink information to terminal devices through access network devices, thus avoiding transmission failures and waste of resources.
  • the core network node is at least one of the following:
  • Access and Mobility Management Function AMF Access and Mobility Management Function
  • Session management function device SMF Session management function device
  • the core network node may be an AMF.
  • the core network node may be an SMF.
  • the core network node may be a UPF.
  • the first message is at least one of the following:
  • the core network node when the first node is a core network node and the second node is an access network device, the core network node sends a first message to the access network device, and may send an NGAP message to the access network device, for example :Paging message.
  • the core network node when the first node is a core network node and the second node is an access network device, the core network node sends a first message to the access network device, and may send a message included in the user plane to the access network device. Messages in data.
  • the first node is the centralized unit user plane CU-UP
  • the second node is the centralized unit control plane CU-CP.
  • the first node is CU-UP, which cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • the second node is CU-CP, and the CU-CP can directly communicate with the terminal device in the non-connected state.
  • the connected terminal equipment sends and receives uplink and downlink information.
  • the CU-UP may determine that SDT information needs to be sent and/or received, and send a first message to the CU-CP, where the first message includes a first message related to the SDT of the terminal device in the non-connected state.
  • Information the first information is used to instruct the CU-CP to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the CU-CP can receive the first request message from the terminal device, it means that the CU-CP can directly send and receive uplink and downlink information with the terminal device in the non-connected state. Therefore, the CU-UP, which cannot directly send and receive uplink and downlink information to the terminal device in the unconnected state, can send and receive uplink and downlink information to the terminal device through the CU-CP, thus avoiding transmission failure and waste of resources.
  • the first message is at least one of the following:
  • CU-UP when the first node is CU-UP and the second node is CU-CP, CU-UP sends a first message to CU-CP, and may send a downlink data notification message (DL Data) to CU-CP. Notification).
  • DL Data downlink data notification message
  • CU-UP when the first node is CU-UP and the second node is CU-CP, CU-UP sends a first message to CU-CP, and may send a bearer context modification requirement message (BEARER) to CU-CP. CONTEXT MODIFICATION REQUIRED).
  • BEARER bearer context modification requirement message
  • CU-UP when the first node is CU-UP and the second node is CU-CP, CU-UP sends the first message to CU-CP, and may send an E1 application protocol E1AP message to CU-CP.
  • the first node is the centralized unit CU or CU-CP
  • the second node is the distribution unit DU.
  • the first node is CU or CU-CP.
  • CU or CU-CP cannot directly send and receive uplink and downlink information with the terminal device in the non-connected state.
  • the second node is DU.
  • DU can directly communicate with the terminal device in the non-connected state.
  • the connected terminal equipment sends and receives uplink and downlink information.
  • the CU or CU-CP may determine the SDT information that needs to be sent and/or received, and send a first message to the DU.
  • the first message includes the first information related to the SDT of the terminal device in the non-connected state. , the first information is used to instruct the DU to send and/or receive SDT information according to the first information after receiving the first request message from the terminal device.
  • the DU can receive the first request message from the terminal device, it means that the DU can directly send and receive uplink and downlink information with the terminal device in the non-connected state. Therefore, a CU or CU-CP that cannot directly send and receive uplink and downlink information to the terminal device in the unconnected state can send and receive uplink and downlink information to the terminal device through the DU, thus avoiding transmission failure and waste of resources.
  • the first message is at least one of the following:
  • the CU or CU-CP when the first node is a CU or CU-CP and the second node is a DU, the CU or CU-CP sends the first message to the DU, and may send a paging message (Paging) to the DU.
  • Paging paging message
  • the CU or CU-CP when the first node is a CU or CU-CP, and the second node is a DU, the CU or CU-CP sends a first message to the DU, and may send a terminal device context modification request message (UE CONTEXT MODIFICATION REQUEST).
  • UE CONTEXT MODIFICATION REQUEST UE CONTEXT MODIFICATION REQUEST
  • the CU or CU-CP when the first node is a CU or CU-CP, and the second node is a DU, the CU or CU-CP sends a first message to the DU, and may send a terminal device context establishment request message (UE CONTEXT SETUP REQUEST).
  • UE CONTEXT SETUP REQUEST UE CONTEXT SETUP REQUEST
  • the CU or CU-CP when the first node is a CU or CU-CP and the second node is a DU, the CU or CU-CP sends the first message to the DU, and may send an F1 application protocol F1AP message to the DU.
  • the second message is at least one of the following:
  • the second node sends a second message to the first node, and the second message may be a notification message sent by SDT.
  • the second node sends a second message to the first node, and the second message may be an initial UL RRC message transmission message.
  • the second node sends a second message to the first node, and the second message may be an F1 application protocol F1AP message.
  • the first node is the first access network device that finally serves the terminal device.
  • the terminal device currently in the non-connected state is within the coverage of the second node, and the second node is the second access network device.
  • the first access network device cannot determine whether the terminal device in the non-connected state is within its coverage.
  • 1) the first access network device can send a RAN paging to the second access network device,
  • the first message includes first information related to the SDT of the terminal device in the non-connected state.
  • the first information includes at least one of the following:
  • the second access network device After receiving the RAN paging sent by the first access network device, the second access network device will send the paging to the terminal device within its coverage.
  • the terminal device will send a first request message in response to paging to the second access network device.
  • the first request message may be RA/ RRCResume Request
  • the second access network device receives the first request message sent by the terminal device, and can determine that the terminal device in the non-connected state at this time is within its coverage, and the second access network device can communicate with the terminal device
  • the second access network device sends a second message (RETRIEVE UE CONTEXT REQUEST message) to the first access network device to obtain the downlink SDT information from the first access network device, wherein:
  • the second message includes second information, and the second information includes at least one of the following:
  • the first access network device sends a partial terminal device context transmission message (PARTIAL UE CONTEXT TRANSFER message) to the second access network device according to the second information, wherein the partial terminal device context transmission message includes at least the following: one:
  • the second access network device may configure SDT resources and/or configure and prepare SDT related configurations for the terminal device based on part of the terminal device context message.
  • the second access network device can send a partial terminal device context transmission confirmation message (PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE) to the first access network device. message) to inform the first access network device that part of the terminal device context transfer message has been received.
  • a partial terminal device context transmission confirmation message PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE
  • Figure 12 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S121 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • S122 Receive the first request message sent by the terminal device, where the first request message is used to indicate the data and/or signaling of the uplink SDT.
  • S123 Send uplink SDT data and/or signaling to the first node.
  • the second node receives the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate to the second node
  • SDT information is sent and/or received according to the first information, and the information includes data and/or signaling.
  • the second node when the second node receives the first request message sent by the terminal device, and the first request message is used to indicate the data and/or signaling of the uplink SDT, the second node may send the first request message to the first node according to the first information. Data and/or signaling of uplink SDT.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S121 to S123 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure.
  • they can be implemented in conjunction with S111 in the embodiment of the present disclosure.
  • the disclosed embodiments do not limit this.
  • Figure 13 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S131 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S132 Send paging to the terminal device according to the first message; receive a first request message sent by the terminal device, where the first request message is a response of the terminal device to the paging of the second node.
  • the second node may consider the first message and the first information and send paging to the terminal device.
  • the terminal device if the terminal device is within the coverage of the second node, or the second node can directly send and receive uplink and downlink information with the terminal device in a non-connected state, it can send a paging to the terminal device, and the terminal device receives After the second node sends the paging, it will send a first request message in response to the paging to the second node.
  • the first request message may be a random access request and/or an RRC Resume Request.
  • the terminal device sends a first request message in response to paging to the second node.
  • the first request message may carry uplink SDT information
  • the uplink SDT information includes uplink SDT data and/or signaling.
  • the second node may send uplink SDT information to the first node, and send uplink SDT data and/or signaling to the first node.
  • S131 to S132 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S121 to S121 in the embodiment of the present disclosure.
  • S123 is implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 14 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S141 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S142 Send paging to the terminal device according to the first message; receive a first request message sent by the terminal device, where the first request message is a response of the terminal device to the paging of the second node.
  • S143 Configure SDT resources for the terminal device according to the first information.
  • the terminal device sends a first request message in response to paging to the second node.
  • the first request message may carry uplink SDT information
  • the uplink SDT information includes uplink SDT data and/or signaling.
  • the second node may configure SDT resources for the terminal device according to the first request message and the first message. This allows the second node to configure appropriate resources for the terminal device based on the type and characteristics of the uplink data, thereby reducing unnecessary scheduling overhead, saving air interface resources, and also saving power for the terminal device.
  • S141 to S143 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S121 to S121 in the embodiment of the present disclosure.
  • S123 and/or S131 to S132 are implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 15 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S151 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S152 In response to not receiving the first request message sent by the terminal device, release the first information related to SDT.
  • the second node receives the first message sent by the first node and sends paging to the terminal device. If it does not receive the first request message sent by the terminal device, it can be determined that the terminal device in the non-connected state is not present. It is within the coverage of the second node, or the second node cannot directly send and receive uplink and downlink information with the terminal device in a non-connected state. In this case, the second node releases the first information related to SDT.
  • S151 to S152 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure.
  • they can be implemented in conjunction with S111 in the embodiment of the present disclosure.
  • the disclosed embodiments do not limit this.
  • Figure 16 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S161 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device. After a request message, the SDT information is sent and/or received according to the first information. The information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S162 Send paging to the terminal device according to the first message; receive a first request message sent by the terminal device, where the first request message is a response of the terminal device to the paging of the second node.
  • S163 Send a second message to the first node, where the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information is used to request the first node to send SDT information to the second node.
  • the second node may consider the first message and the first information and send paging to the terminal device.
  • the terminal device if the terminal device is within the coverage of the second node, or the second node can directly send and receive uplink and downlink information with the terminal device in a non-connected state, it can send a paging to the terminal device, and the terminal device receives After the second node sends the paging, it will send a first request message in response to the paging to the second node.
  • the first request message may be a random access request and/or an RRC Resume Request.
  • it may also carry uplink SDT information, and the uplink SDT information includes uplink SDT data and/or signaling.
  • the second node can send a second message to the first node, where the second message includes the SDT related to the terminal device in the non-connected state.
  • the second information is used to request the first node to send SDT information to the second node.
  • the second message may be a RETRIEVE UE CONTEXT REQUEST message.
  • the second node sends a second message to the first node to inform the first node that the terminal device in the non-connected state is within the coverage of the second node, and the second node can send the downlink SDT to the terminal device.
  • the first request message carries the uplink SDT information
  • the second message sent by the second node to the first node includes information about the terminal device in the non-connected state.
  • second information related to SDT to send uplink SDT information to the first node.
  • S161 to S163 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure.
  • this step In combination with S111 in the embodiment of the present disclosure, this step The disclosed embodiments do not limit this.
  • Figure 17 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S171 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S172 Send paging to the terminal device according to the first message; receive a first request message sent by the terminal device, where the first request message is a response of the terminal device to the paging of the second node.
  • S173 Send a second message to the first node, where the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information is used to request the first node to send SDT information to the second node. .
  • S174 Receive SDT information sent by the first node, where the SDT information is sent by the first node according to the second message, and the SDT information includes downlink SDT data and/or signaling.
  • the first node may send SDT information to the second node according to the second message, where the SDT information includes downlink SDT data and/or information. make.
  • the second node when it receives the downlink SDT data and/or signaling sent by the first node, it may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S171 to S174 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S161 to S161 in the embodiment of the present disclosure.
  • S163 is implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 18 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S181 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S182 Send paging to the terminal device according to the first message; receive the first request message sent by the terminal device, where the first request message is the response of the terminal device to the paging of the second node.
  • S183 Send a second message to the first node, where the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information is used to request the first node to send SDT information to the second node.
  • S184 Receive SDT information sent by the first node, where the SDT information is sent by the first node according to the second message, and the SDT information includes downlink SDT data and/or signaling.
  • S185 Send downlink SDT data and/or signaling to the terminal device.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S181 to S185 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S161 to S161 in the embodiment of the present disclosure.
  • S163 and/or S171 to S174 are implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 19 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S191 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S192 Send paging to the terminal device according to the first message; receive the first request message sent by the terminal device, where the first request message is the response of the terminal device to the paging of the second node.
  • S193 Send a second message to the first node, where the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information is used to request the first node to send SDT information to the second node.
  • S194 Receive SDT information sent by the first node, where the SDT information is sent by the first node according to the second message, and the SDT information includes downlink SDT data and/or signaling.
  • S195 Send downlink SDT data and/or signaling to the terminal device.
  • S196 Send first indication information to the first node, where the first indication information is used to instruct the second node to complete sending the downlink SDT data and/or signaling to the terminal device.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, it may send first indication information to the first node.
  • the first indication information is used to instruct the second node to complete sending the downlink SDT data to the terminal device. SDT data and/or signaling.
  • the first indication information includes at least one of the following:
  • the second node sends first indication information to the first node, and the first indication information may include terminal device identification information.
  • the second node sends first indication information to the first node, and the first indication information may include an indication of successful transmission to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include an indication that is not successfully sent to the terminal device.
  • the second node sends first indication information to the first node, and the first indication information may include DL TNL information.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S191 to S196 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S161 to S161 in the embodiment of the present disclosure.
  • S163 and/or S171 to S174 and/or S181 to S185 are implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 20 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S201 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the SDT information is sent and/or received according to the first information.
  • the information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • S202 Send paging to the terminal device according to the first message; receive a first request message sent by the terminal device, where the first request message is a response of the terminal device to the paging of the second node.
  • S203 Send a second message to the first node, where the second message includes second information related to the SDT of the terminal device in the non-connected state, and the second information is used to request the first node to send SDT information to the second node. .
  • S204 Receive SDT information sent by the first node, where the SDT information is sent by the first node according to the second message, and the SDT information includes downlink SDT data and/or signaling.
  • S205 Send downlink SDT data and/or signaling to the terminal device.
  • S206 Receive a response message sent by the terminal device, where the response message is used to indicate that the terminal device has received the data and/or signaling of the downlink SDT.
  • S207 Send second indication information to the first node, where the second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the second node after the second node sends downlink SDT data and/or signaling to the terminal device, if the terminal device successfully receives the downlink SDT data and/or signaling sent by the second node, it may send the data to the second node.
  • the second node receives the response message sent by the terminal device, and can determine that the terminal device successfully receives the data and/or signaling of the downlink SDT.
  • the second node sends second indication information to the first node, and the second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the second indication information includes at least one of the following:
  • the second node sends second indication information to the first node, and the second indication information includes terminal device identification information.
  • the second node sends second indication information to the first node, and the second indication information includes an indication of successful transmission to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information includes an indication that is not successfully sent to the terminal device.
  • the second node sends second indication information to the first node, and the second indication information may include DL TNL information.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S201 to S206 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S161 to S161 in the embodiment of the present disclosure.
  • S163 and/or S171 to S174 and/or S181 to S185 are implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 21 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S211 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the SDT information is sent and/or received according to the first information.
  • the information includes data and/or signaling.
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message. It can be understood that the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message. Wherein, the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or a message on the Xn user plane.
  • the third message may also include an identifier related to the terminal device, such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • an identifier related to the terminal device such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • S212 Send paging to the terminal device according to the first message; receive the first request message sent by the terminal device, where the first request message is the response of the terminal device to the paging of the second node.
  • S213 Send downlink SDT data and/or signaling to the terminal device.
  • the second node when the first node sends a first message to the second node, and the first message includes the first information and also includes downlink SDT data and/or signaling, the second node sends a message to the terminal according to the first information.
  • the device sends paging, and when the second node receives the first request message from the terminal device in response to paging, since the second node has received the downlink SDT information sent by the first node, it can directly send the downlink SDT information. to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S211 to S213 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S131 to S131 in the embodiment of the present disclosure.
  • S132 is implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 22 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S221 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message. It can be understood that the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message. Wherein, the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or a message on the Xn user plane.
  • the third message may also include an identifier related to the terminal device, such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • an identifier related to the terminal device such as a terminal device paging identifier UE RAN Paging Identity, which is used to indicate the terminal device corresponding to the third information included in the third message.
  • S222 Send paging to the terminal device according to the first message; receive the first request message sent by the terminal device, where the first request message is the response of the terminal device to the paging of the second node.
  • S223 Send downlink SDT data and/or signaling to the terminal device.
  • the second node when the first node sends a first message to the second node, and the first message includes the first information and also includes downlink SDT data and/or signaling, the second node sends a message to the terminal according to the first information.
  • the device sends paging, and when the second node receives the first request message from the terminal device in response to paging, since the second node has received the downlink SDT information sent by the first node, it can directly send the downlink SDT information. to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S224 Send first indication information to the first node, where the first indication information is used to instruct the second node to complete sending the downlink SDT data and/or signaling to the terminal device.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S221 to S224 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S131 to S131 in the embodiment of the present disclosure.
  • S132 and/or S211 to S213 are implemented together, and the embodiment of the present disclosure does not limit this.
  • Figure 23 is a flow chart of yet another data transmission method provided by an embodiment of the present disclosure.
  • the method is executed by the second node.
  • the method may include but is not limited to the following steps:
  • S231 Receive the first message sent by the first node, where the first message includes first information related to the SDT of the terminal device in the non-connected state, and the first information is used to indicate that the second node receives the first SDT of the terminal device.
  • the information includes data and/or signaling
  • the first node is a node that cannot determine whether the terminal device in the unconnected state is within its coverage, or It is a node that cannot directly send and receive uplink and downlink information with terminal equipment in a non-connected state.
  • the first information includes at least one of the following:
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message. It can be understood that the third information is included in the first message, and the third information is sent to the second node simultaneously with the first message. Wherein, the third information is included in the third message, and the third message may be sent simultaneously with the first message, or before or after the first message.
  • the third message may be an RRC transmission message on XnAP or an Xn user plane message.
  • the third message may also include an identifier related to the terminal device, such as the terminal device paging identifier UE RAN Paging Identity, used to indicate the terminal device corresponding to the third information included in the third message. .
  • S232 Send paging to the terminal device according to the first message; receive the first request message sent by the terminal device, where the first request message is the response of the terminal device to the paging of the second node.
  • S233 Send downlink SDT data and/or signaling to the terminal device.
  • the second node when the first node sends a first message to the second node, and the first message includes the first information and also includes downlink SDT data and/or signaling, the second node sends a message to the terminal according to the first information.
  • the device sends paging, and when the second node receives the first request message from the terminal device in response to paging, since the second node has received the downlink SDT information sent by the first node, it can directly send the downlink SDT information. to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S234 Receive a response message sent by the terminal device, where the response message is used to indicate that the terminal device has received the data and/or signaling of the downlink SDT.
  • S235 Send second indication information to the first node, where the second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the second node may send the downlink SDT data and/or signaling to the terminal device.
  • the first node can accurately send and receive SDT information with the terminal device in a non-connected state, thereby avoiding transmission failure and waste of resources.
  • S231 to S235 can be implemented alone or in combination with any other steps in the embodiment of the present disclosure, for example, in combination with S111 and/or S131 to S131 in the embodiment of the present disclosure.
  • S132 and/or S211 to S213 are implemented together, and the embodiment of the present disclosure does not limit this.
  • the methods provided by the embodiments of the present disclosure are introduced from the perspectives of the first node and the second node respectively.
  • the first node and the second node may include a hardware structure and a software module to implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • a certain function among the above functions can be executed by a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 24 is a schematic structural diagram of a communication device 1 provided by an embodiment of the present disclosure.
  • the communication device 1 shown in FIG. 24 may include a transceiver module 11 and a processing module 12.
  • the transceiver module may include a sending module and/or a receiving module.
  • the sending module is used to implement the sending function
  • the receiving module is used to implement the receiving function.
  • the transceiving module may implement the sending function and/or the receiving function.
  • Communication device 1 is the first node:
  • the communication device 1 includes: a transceiver module 11 and a processing module 12 .
  • a processing module configured to determine the information that needs to be sent and/or received to transmit SDT in small data packets, where the information includes data and/or signaling, and the first node is unable to determine whether the terminal device in the non-connected state is covered by it. Nodes within the range, or nodes that cannot directly send and receive uplink and downlink information to terminal devices in a non-connected state;
  • the transceiver module is configured to send a first message to the second node, wherein the first message includes first information related to the SDT of the terminal device in a non-connected state, and the first information is used to indicate that the second node receives the After the device sends the first request message, it sends and/or receives SDT information according to the first information.
  • the first information includes at least one of the following:
  • the transceiver module 11 is also configured to receive a second message sent by the second node, where the second message is sent by the second node after receiving the first request message sent by the terminal device.
  • the message includes second information related to the SDT of the terminal device in the non-connected state.
  • the second information is used to request the first node to send SDT information to the second node.
  • the first request message is a paging of the second node by the terminal device. the response to.
  • the second information includes at least one of the following:
  • the transceiver module 11 is further configured to send SDT information to the second node according to the second message, where the SDT information includes downlink SDT data and/or signaling.
  • the first node sends third information to the second node, and the third information includes at least one of the following:
  • the third message is included in the first message and/or the third message.
  • the third message may also include an identifier related to the terminal device.
  • the transceiver module 11 is also configured to receive the first indication information sent by the second node, where the first indication information is used to instruct the second node to complete sending the downlink SDT data and/or information to the terminal device. make.
  • the transceiver module 11 is further configured to receive second indication information sent by the second node, where the second indication information is sent by the second node after receiving a response message sent by the terminal device, The second indication information is used to indicate that the second node successfully sends downlink SDT data and/or signaling to the terminal device.
  • the first indication information and/or the second indication information includes at least one of the following:
  • the first node is a first access network device
  • the second node is a second access network device
  • the first access network device is the last access network device serving the terminal device
  • the second access network device is the last access network device serving the terminal device.
  • the network access device is the access network device currently serving the terminal device.
  • the first message is at least one of the following:
  • Some terminal devices contextually transmit messages
  • the second message is at least one of the following:
  • the first node is a core network node
  • the second node is an access network device.
  • the core network node is at least one of the following:
  • Access and Mobility Management Function AMF Access and Mobility Management Function
  • Session management function device SMF Session management function device
  • the first message is at least one of the following:
  • the first node is the centralized unit user plane CU-UP
  • the second node is the centralized unit control plane CU-CP.
  • the first message is at least one of the following:

Landscapes

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

Abstract

本公开实施例公开了一种数据传输方法和装置，可应用于通信技术领域，由第一节点执行的方法包括：确定需要发送和/或接收的小数据包传输 SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点（S51）；向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收 SDT的信息（S52）。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。

Description

数据传输方法和装置 技术领域
本公开涉及通信技术领域，尤其涉及一种数据传输方法和装置。
背景技术
相关技术中，终端设备可以在非连接态，例如：空闲态或非激活态(IDLE/INACTIVE)，通过SDT的方式将上行信息发送至服务该终端设备的节点(终端设备在该节点的覆盖范围内)，以及接收服务该终端设备的节点发送的下行信息。
但是，对于无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者，无法直接与处于非连接态的终端设备进行上下行信息的收发的节点，如何保证与处于非连接态的终端设备进行上下行信息的准确和高效收发，避免传输失败和资源的浪费，这是亟需解决的问题。
发明内容
本公开实施例提供一种数据传输方法和装置，以使第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
第一方面，本公开实施例提供一种数据传输方法，该方法由第一节点执行，该方法包括：确定需要发送和/或接收的小数据包传输SDT的信息，其中，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点；向第二节点发送第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息。
在该技术方案中，第一节点确定需要发送和/或接收的小数据包传输SDT的信息，其中，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点；向第二节点发送第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息。由此，第一节点能够准确和高效的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
第二方面，本公开实施例提供另一种数据传输方法，该方法由第二节点执行，该方法包括：接收第一节点发送的第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
第三方面，本公开实施例提供一种通信装置，该通信装置具有实现上述第一方面所述的方法中第一节点的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，所述处理模块被配置为支持通信装置执行上述方法中相应的功能。所述收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：处理模块，被配置为确定需要发送和/或接收的小数据包传输SDT的信息，其中，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点；收发模块，被配置为向第二节点发送第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息。
第四方面，本公开实施例提供另一种通信装置，该通信装置具有实现上述第二方面所述的方法示例中第二节点的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，该处理模块被配置为支持通 信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为接收第一节点发送的第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
第五方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种迁移系统，该系统包括第三方面所述的通信装置以及第四方面所述的通信装置，或者，该系统包括第五方面所述的通信装置以及第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置以及第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置以及第十方面所述的通信装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述第一节点所用的指令，当所述指令被执行时，使所述第一节点执行上述第一方面所述的方法。
第十三方面，本发明实施例提供一种可读存储介质，用于储存为上述第二节点所用的指令，当所述指令被执行时，使所述第二节点执行上述第二方面所述的方法。
第十四方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持第一节点实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存第一节点必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持第二节点实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存第二节点必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种非连接态终端设备进行RA-SDT的方法的流程图；
图2是本公开实施例提供的一种通信系统的架构示意图；
图3是本公开实施例提供的一种CU-DU的架构示意图；
图4是本公开实施例提供的一种RRC状态转变示意图；
图5是本公开实施例提供的一种数据传输方法的流程图；
图5a是本公开实施例提供的另一种数据传输方法的流程图；
图5b是本公开实施例提供的又一种数据传输方法的流程图；
图6是本公开实施例提供的另一种数据传输方法的流程图；
图7是本公开实施例提供的又一种数据传输方法的流程图；
图8是本公开实施例提供的又一种数据传输方法的流程图；
图9是本公开实施例提供的又一种数据传输方法的流程图；
图10是本公开实施例提供的又一种数据传输方法的流程图；
图11是本公开实施例提供的又一种数据传输方法的流程图；
图11a是本公开实施例提供的又一种数据传输方法的流程图；
图12是本公开实施例提供的又一种数据传输方法的流程图；
图13是本公开实施例提供的又一种数据传输方法的流程图；
图14是本公开实施例提供的又一种数据传输方法的流程图；
图15是本公开实施例提供的又一种数据传输方法的流程图；
图16是本公开实施例提供的又一种数据传输方法的流程图；
图17是本公开实施例提供的又一种数据传输方法的流程图；
图18是本公开实施例提供的又一种数据传输方法的流程图；
图19是本公开实施例提供的又一种数据传输方法的流程图；
图20是本公开实施例提供的又一种数据传输方法的流程图；
图21是本公开实施例提供的又一种数据传输方法的流程图；
图22是本公开实施例提供的又一种数据传输方法的流程图；
图23是本公开实施例提供的又一种数据传输方法的流程图；
图24是本公开实施例提供的一种通信装置的结构图；
图25是本公开实施例提供的另一种通信装置的结构图；
图26是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于理解本公开，此处对本公开实施例涉及到的部分概念作简单介绍。
1、SDT(Small Data Transmission，小数据包传输)
一般情况下，终端设备处于RRC连接态(CONNECTED)时，终端设备与接入网设备之间才能传输数据。但在一些场景下，处于RRC空闲态(IDLE)或RRC非激活态(INACTIVE)的终端设备需传输的数据包很小，可以称这类数据包为小数据包(small data)，而终端设备从RRC IDLE态或RRC INACTIVE态进入RRC CONNECTED态所需的信令甚至大于small data，从而导致终端设备不必要的功耗和信令开销。为了避免上述情况，处于RRC IDLE态或RRCINACTIVE态的终端设备可以在随机接入(random access，RA)过程中传输small data或者在接入网设备配置的资源上传输small data，而无需进入RRC CONNECTED态后再传输small data。
上述传输过程可以称为SDT(small data transmission，小数据包传输)，其中，终端设备在接入网设备配置的资源上传输small data的方式可以称为CG-SDT(Configure Grant small data transmission，配置授权小数据包传输)，终端设备在随机计入过程中传输smalldata的方式可以称为RA-SDT(Random Access small data transmission)。
根据接入网设备配置的资源，终端设备在非连接态，例如：IDLE(空闲态)或INACTIVE(非激活态)时，可以通过以下方法发送将数据直接发送给接入网设备：
1)初始接入的四步随机接入过程的Msg3(或称为4-step RACH SDT)；
2)初始接入的两步随机接入过程的MsgA(或称为2-step RACH SDT)；
3)接入网设备配置的专属上行PUSCH(Physical Uplink Shared Channel，物理上行共享信道)资源(即CG(Configure Grant)或PUR(Preallocated Uplink Resource，预先分配的上行资源))；或称为CG SDT。
SDT过程可以包括初始数据发送阶段和后续数据发送阶段。
其中，初始数据发送阶段：从触发SDT初始数据发送开始，到接收到网络侧对于该初始数据的确认信息。
其中，该确认信息对比于不同SDT过程会有以下三种不同：
(1)4-step RACH SDT：确认信息为成功接收到Msg4的竞争解决标识；
(2)2-step RACH SDT：确认信息为成功接收到MsgB的竞争解决标识；
(3)CG-SDT：确认信息为接入网设备发送的数据接收成功指示(如，物理层DCI(Downlink Control Information，下行控制信息)指示的ACK(肯定应答)信息。)
后续数据发送阶段：从接收到接入网设备对于该初始数据的确认信息，到接收到接入网设备发送的连接释放消息。在该阶段，终端设备可以进行上下行数据的收发。
CG-SDT的后续数据发送阶段，在这一过程中终端设备会监听PDCCH(Physical downlink control channel，物理下行控制信道)以接收C-RNTI(Cell Radio NetworkTemporary Identifier，小区无线网络临时标识)并在后续时刻发送CG-PUSCH，在接收到接入网设备发送的连接释放消息之前，终端设备会不断重复监听PDCCH后发送CG-PUSCH。
其中，对于接入网设备配置的CG-SDT资源，终端设备在采用了该CG资源发送了数据后，会启动反馈定时器(如，feedbackTimer)监听接入网设备的反馈信息。如果终端设备在反馈定时器运行期间没有接收到接入网设备的成功接收确认，则终端设备在后续的CG资源进行数据重传，进行CG-SDT重传。对上行动态授权Configured Grant，在每次终端设备在一个HARQ process上发送上行新数据传输后就会启动该HARQ process对应的配置授权定时器，在该定时器运行期间，该HARQ process上不能调度其它新传。配置授权重传定时器(CG-RetransmissionTimer)可以Per Configured Grant配置，用于进行上行自动重传。在每次终端设备在一个HARQ process上发送上行新传或重传后就会启动该HARQ process对应的CG-RetransmissionTimer，在该定时器运行期间，不进行上行自动重传。在该定时器停止运行后，启动上行自动重传。
终端设备在RRC空闲态(IDLE)或RRC非激活态(INACTIVE)下，可以通过RA-SDT或CG-SDT的方式将上行数据发送至网络侧，如果接收上行数据的接入网设备(Receiving gNB)不是最后服务于终端设备的接入网设备(Last serving gNB)，Receiving gNB需要向Last serving gNB获取终端设备上下文，或者部分终端设备上下文，以便接收上行数据。其中，Last serving gNB可以决定是否进行锚点重定位(anchor relocation)，若不进行anchor relocation(即without anchor relocation)，则执行如图1所示流程。
其中，1)、终端设备发送RRC Resume Request以及上行(UL)SDT的数据和/或信令给Receiving gNB。
2)、Receiving gNB使用I-RNTI(inactive radio network temporary identifier，非活动态无线网络临时标识)识别Last serving gNB，并通过XnAP(Xn application protocol，Xn接口应用协议)检索终端设备上下文过程检索终端设备上下文。接收gNB指示终端设备请求是一个SDT交互，也可以提供SDT协助信息(即，单包，多包)。
3)、Last serving gNB决定不为SDT重新定位终端设备上下文。
4)、Last serving gNB传输部分的终端设备上下文，包括SDT相关的RLC上下文。
5)、Receiving gNB确认接收部分终端设备上下文，并在需要时提供相关的DL TNL地址。完成部分终端设备上下文检索后，在Last serving gNB保留终端设备上下文，在Receiving gNB建立与SDT相关的RLC上下文，然后将UL SDT数据下发到UPF，如果有UL NAS(non-access straum，非接入层)PDU(protocoldata unit，协议数据单元)，则将UL NAS PDU下发到AMF。
6)、SDT传输完成后，Last serving gNB用RETRIEVE UE CONTEXT FAILURE消息响应Receiving gNB，包括一个封装的RRCRelease消息。RRCRelease消息中包含挂起配置。
7)、Receiving gNB向终端设备发送RRCRelease消息。
8)、终端设备保持在“RRC_INACTIVE”状态。
2、MT(Mobile Terminated，移动被叫)SDT
网络侧通过发送下行寻呼消息，让终端设备在IDLE/INACTIVE(空闲态或非激活态)状态发起连接恢复(或建立)过程。从而让终端设备保留在IDLE/INACTIVE状态，并接收网络侧下发的下行数据。
为了更好的理解本公开实施例公开的一种数据传输方法和装置，下面首先对本公开实施例适用的通信系统进行描述。
如图2所示，本公开实施例提供了一种通信系统，包括：核心网设备(例如5G核心网(5th generation core，5GC)11、演进型分组核心网(evolved packet core，EPC)12)、接入网设备(例如继续演进的节点B(gNB)13、演进型节点B(evolved node B，eNB)14)、终端设备15。
终端设备15，又称之为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是指向用户提供语音和/或数据连通性的设备。例如，具有无线连接功能的手持式设 备、车载设备等。目前，一些终端设备的举例包括：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internetdevice，MID)、可穿戴设备、虚拟现实(virtual reality，VR)设备、增强现实(augmentedreality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(selfdriving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
核心网设备11，是指为终端设备提供业务支持的核心网(core network，CN)中的设备。目前，一些核心网设备包括：接入和移动性管理功能(access and mobilitymanagement function，AMF)实体、会话管理功能(session management function，SMF)实体、用户面功能(user plane function，UPF)实体等等，此处不一一列举。其中，AMF实体可以负责终端设备的接入管理和移动性管理。SMF实体可以负责会话管理，如用户的会话建立等。UPF实体可以是用户面的功能实体，主要负责连接外部网络。需要说明的是，本公开中实体也可以称为网元或功能实体，例如，AMF实体也可以称为AMF网元或AMF功能实体，SMF实体也可以称为SMF网元或SMF功能实体等。
接入网设备13，是指将终端设备接入到无线网络的无线接入网(radio accessnetwork，RAN)节点(或设备)，又可以称为基站。目前，一些RAN节点的举例包括：gNB、eNB、传输接收点(transmission reception point，TRP)、无线网络控制器(radio networkcontroller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或homenode B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wi-Fi)接入点(access point，AP)等。另外，在一种网络结构中，接入网设备可以包括集中单元(centralized unit，CU)、或分布单元(distributed unit，DU)、或包括CU和DU的RAN设备。其中包括CU和DU的RAN设备从逻辑功能角度将协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
如图3所示，是CU-DU的架构示意图。CU和DU在物理上可以是分离的也可以部署在一起。CU和DU可以根据协议层进行划分，例如其中一种可能的划分方式是：CU用于执行无线资源控制(radio resource control，RRC)层、服务数据适配层(service data adaptationprotocol，SDAP)(本协议层是当接入网设备连接到5G核心网时才具有的协议层)、分组数据汇聚层协议层(packet data convergence protocol，PDCP)的功能，而DU用于执行无线链路控制(radio link control，RLC)层、媒体接入控制(medium access control，MAC)层以及物理(physical，PHY)层等的功能。
可以理解，上述划分仅仅是一种举例，CU和DU也可以按照其他的方式进行划分。例如可以将CU或者DU划分为具有更多协议层的功能。例如，CU或DU还可以划分为具有协议层的部分处理功能。
在一种可能的实现方式中，将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。
在另一种可能的实现方式中，还可以按照业务类型或者其他系统需求对CU或者DU的功能进行划分。例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。
在又一种可能的实现方式中，CU也可以具有核心网的一个或多个功能。一个或者多个CU可以集中设置，也可以分离设置。例如CU可以设置在网络侧方便集中管理。DU可以具有多个射频功能，也可以将射频功能拉远设置。
应理解，CU和DU的功能可以在具体实现中可以根据需要设置，本公开实施例对此不作任何限定。CU的功能可以由一个实体来实现也可以由不同的功能实体来实现。在一种方式中，CU的功能可以进一步切分为控制面(control plane，CP)功能和用户面(userplane，UP)，即CU可以分为CU-UP和CU-CP。CU-CP和CU-UP可以由不同的功能实体来实现，也可以由同一功能实体来实现。CU-CP和CU-UP可以与DU相耦合，共同完成接入网设备的功能。一种可能的方式中，CU-CP负责控制面功能，主要包含RRC和PDCP-C。PDCP-C主要负责控制面数据的加解密、完整性保护以及数据传输等。CU-UP负责用户面功能，主要包含SDAP和PDCP-U。其中SDAP主要负责将核心网设备的数据进行处理并将数据流(flow)映射到承载。PDCP-U主要负责数据面的加解密、完整性保护、头压缩、序列号维护以及数据传输等。还有一种可能的实现方式是PDCP-C也包含在CU-UP中。
核心网设备与CU(例如CU-UP和/或CU-CP)之间可以进行通信，例如，CU-CP可以代表接入网设备通过Ng接口与核心网设备进行通信。CU-UP与CU-CP之间可以进行通信，例如，通过E1接口进行通信。CU-UP与DU之间以及CU-CP与DU之间可以进行通信，例如，CU-CP可以通过F1-C(控制面)与DU进行通信，CU-UP可以通过F1-U(用户面)与DU进行通信。多个DU可以共用一个CU，一个DU也可以连接多个CU(图中未示出)。CU与DU之间可以通过接口(例如F1接口)进行通信。
在该通信系统中，接入网设备13和接入网设备14均可以与多个终端设备通信。但应理解，与接入网设备13通信的终端设备和与接入网设备14通信的终端设备可以是相同的，也可以是不同的。图2中示出的终端设备15可同时与接入网设备13和接入网设备14通信，但这仅示出了一种可能的场景，在某些场景中，终端设备可能仅与接入网设备13或接入网设备14通信，本申请对此不做限定。
应理解，图2仅为便于理解而示例的简化示意图，该通信系统中还可以包括其他接入网设备，终端设备，或者核心网设备，图2中未予以画出。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
在NR和LTE系统中，终端设备(UE)的RRC状态包括连接态(RRC_CONNECTED)、空闲态(RRC_IDLE)、非激活态(RRC_INACTIVE，或者称为第三态)。其中，RRC非激活(inactive)状态是终端设备通过接入网设备连接到5G核心网中新引入的状态，该状态介于连接态和空闲态之间。在RRC_INACTIVE状态下，终端设备与接入网设备之间没有RRC连接，但保持接入网设备与核心网设备的连接，终端设备保存有建立/恢复连接所必须的全部或部分信息。因而在RRC_INACTIVE状态下，终端设备在需要建立连接时，可以根据保存的相关信息，快速地与接入网设备建立或恢复RRC连接。
当终端设备处于RRC_CONNECTED状态时，终端设备与接入网设备以及核心网都已建立链路，当有数据到达网络时可以直接传送到终端设备；当终端设备处于RRC_INACTIVE状态时，表示终端设备之前和接入网设备以及核心网建立过链路，但是终端设备到接入网设备这一段链路被释放，但是接入网设备会存储终端设备的上下文，当有数据需要传输时，接入网设备可以快速恢复这段链路；当终端设备处于RRC_IDLE状态时，终端设备与接入网设备和核心网之间都没有链路，当有数据需要传输时，需要建立终端设备到接入网设备及核心网的链路。
示例性的，图4为本公开实施例提供的一种RRC状态转变示意图，如图4所示，在RRC_IDLE态时，终端设备可以接入接入网设备，接入过程中或接入接入网设备后终端设备可以和接入网设备进行RRC建立过程，使得终端设备的状态从RRC_IDLE态转换为RRC_CONNECTED态。在RRC_IDLE态时，终端设备从接入网设备接收到寻呼消息后或者由终端设备的高层触发后，终端设备可以发起RRC建立过程，试图和接入网设备建立RRC连接以进入RRC_CONNECTED态。
例如，终端设备和接入网设备之间的RRC建立过程包括：终端设备向接入网设备发送RRC建立请求(RRCSetupResuest)消息，接收到该请求后：接入网设备向终端设备发送RRC建立(RRCSetup)消息，使得终端设备的状态可以转换为RRC_CONNECTED态；或者，接入网设备向终端设备发送RRC拒绝(RRCReject)消息，使得终端设备继续停留在RRC_IDLE态。
终端设备是RRC_IDLE态时，没有终端设备和接入网设备之间的RRC连接。当终端设备处于RRC_CONNECTED状态时，接入网设备可以通过释放RRC过程，例如向终端设备发送RRC释放(RRCRelease)消息，使得终端设备的状态从RRC_CONNECTED态转变为RRC_IDLE状态或RRC_INACTIVE状态。当终端设备处于RRC_INACTIVE状态时，终端设备可以通过释放RRC连接而进入RRC_IDLE状态，或者，终端设备可以通过恢复RRC连接而进入RRC_CONNECTED状态。
示例性地，终端设备是RRC_CONNECTED态时，存在终端设备和接入网设备之间的RRC连接。此时，接入网设备知道该终端设备在该接入网设备的覆盖范围内或者在该接入网设备的管理范围内；核心网知道终端设备在哪个接入网设备的覆盖范围内或者管理范围内，核心网知道通过哪个接入网设备可以定位到或者找到该终端设备。
在RRC_INACTIVE时，终端设备可以通过RRC建立或RRC恢复(resume)过程，使得终端设备的状态从RRC_INACTIVE态转换为RRC_CONNECTED态；接入网设备可以通过RRC释放过程，使得终端设备的状态从RRC_INACTIVE态转换为RRC_IDLE态。在RRC_INACTIVE态时，终端设备从接入网设备接收到寻呼消息后或者由终端设备的高层触发后，终端设备可以发起RRC恢复过程，试图恢复和接入网设备间的RRC连接以进入RRC_CONNECTED态。
例如，终端设备和接入网设备之间的RRC恢复过程包括：终端设备向接入网设备发送RRC恢复请求(RRCResumeResuest)消息，接收到该请求后：接入网设备向终端设备发送RRC建立(RRCSetup)消息或者RRC恢复(RRCResume)消息，使得终端设备的状态可以转换为RRC_CONNECTED态；或者，接入网设备向终端设备发送RRC释放(RRCRelease)消息，使得终端设备的状态从RRC_INACTIVE态转换为RRC_IDLE态；或者，接入网设备向终端设备发送RRC拒绝(RRCReject)消息，使得终端设备继续停留在RRC_INACTIVE态。
终端设备是RRC_INACTIVE态时，没有终端设备和接入网设备之间的RRC连接。此时，接入网设备不知道该终端设备是否在该接入网设备的覆盖范围内或者是否在该接入网设备的管理范围内；核心 网知道终端设备在哪个接入网设备的覆盖范围内或者管理范围内，核心网知道通过哪个接入网设备可以定位到或者找到该终端设备。
需要说明的是，在本公开的全文描述中，终端设备处于非连接态，可以为终端设备处于空闲态，或者终端设备处于非激活态，或者处于其他连接态以外的状态；终端设备在非连接态下，可以为终端设备在空闲态下，或者终端设备在非激活状态下，或者终端设备在连接态以外的其他的状态下。
在本公开实施例中，“用于指示”可以包括用于直接指示和用于间接指示。当描述某一指示信息用于指示A时，可以包括该指示信息直接指示A或间接指示A，而并不代表该指示信息中一定包括有A。
在本公开实施例中，SDT的数据为通过SDT机制传输的数据，可以是指用户平面的数据，或者也可以是指控制平面的信令，例如上下行的RRC消息、NAS消息和/或LPP(LTE positioning protocol，LTE定位协议)消息等。
在本公开实施例中，SDT的资源或SDT的配置可以是MT-SDT、CG-SDT、RA-SDT或SPS-SDT等。
下面结合附图对本公开所提供的一种数据传输方法和装置进行详细地介绍。
请参见图5，图5是本公开实施例提供的一种数据传输方法的流程图。
如图5所示，该方法由第一节点执行，该方法可以包括但不限于如下步骤：
S51：确定需要发送和/或接收的小数据包传输SDT的信息，其中，SDT的信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
其中，SDT的信令包括但不限于非接入层(Non-Access Stratum)NAS信令、LTE定位协议(LTE Positioning Protocal)LPP信令、和/或RRC信令，SDT的数据可以为来自核心网用户平面的数据和/或第一节点自己需要向终端设备发送的数据。
其中，第一节点确定需要发送的SDT的信息，可以确定需要发送的SDT的数据，或者，确定需要发送的SDT的信令，或者确定需要发送的SDT的数据和信令。其中，第一节点确定需要接收的SDT的信息，可以确定需要接收的SDT的数据，或者，确定需要接收的SDT的信令，或者确定需要接收的SDT的数据和信令。其中，第一节点确定需要发送和接收的SDT的信息，可以确定需要发送和接收的SDT的数据，或者，确定需要发送和接收的SDT的信令，或者确定需要发送和接收的SDT的数据和信令。
可以理解的是，第一节点从其他节点接收到对终端设备的下行数据和/或下行信令，或者第一节点自己决定向终端设备发送下行数据和/或下行信令，第一节点可以确定需要向终端设备发送SDT的信息。
可以理解的是，第一节点确定需要发送和/或接收的SDT的信息，可以确定需要发送至处于非连接态的终端设备的SDT的信息，和/或，确定需要接收来自处于非连接态的终端设备的SDT的信息。
在一些实施例中，第一节点可以为接入网设备，接入网设备确定需要发送和/或接收的SDT的信息，可以确定需要发送的SDT的数据和/或信令，可以确定需要接收的SDT的数据和/或信令。
其中，接入网设备可以从核心网节点处获取需要发送的SDT的数据和/或信令，以确定需要发送的SDT的数据和/或信令，并且，接入网设备可以根据其发出的SDT的数据和/或信令，确定是否存在需要接收的SDT的数据和/或信令。
当然，接入网设备还可以根据其他信息确定发送的SDT的数据和/或信令，和/或确定需要接收的SDT的数据和/或信令，本公开实施例对此不作具体限制。
在另一些实施例中，第一节点可以为核心网节点，例如：AMF(Access and MobilityManagement Function，接入和移动性管理功能)，或者UPF(User Plane Function，用户面功能设备)，或者SMF(Session Management Function，会话管理功能设备)等。
其中，核心网节点确定需要发送和/或接收的SDT的信息，可以确定需要发送的SDT的数据和/或信令，可以确定需要接收的SDT的数据和/或信令。
其中，核心网节点可以根据其本身的信息，确定需要发送的SDT的数据和/或信令，并且，核心网节点可以根据其发出的SDT的数据和/或信令，确定是否存在需要接收的SDT的数据和/或信令。
当然，核心网节点还可以根据其他信息确定发送的SDT的数据和/或信令，和/或确定需要接收的SDT的数据和/或信令，本公开实施例对此不作具体限制。
在又一些实施例中，第一节点可以为集中单元CU，或者集中单元用户面CU-UP。CU或CU-UP确定需要发送和/或接收的SDT的信息，可以确定需要发送的SDT的数据和/或信令，可以确定需要接收的SDT的数据和/或信令。
其中，CU或CU-UP可以与核心网节点通信，从核心网节点处获取需要发送的SDT的数据和/或信 令，以确定需要发送的SDT的数据和/或信令，并且，CU或CU-UP可以根据其发出的SDT的数据和/或信令，确定是否存在需要接收的SDT的数据和/或信令。
当然，CU或CU-UP还可以根据其他信息确定发送的SDT的数据和/或信令，和/或确定需要接收的SDT的数据和/或信令，本公开实施例对此不作具体限制。
S52：向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，第一消息可以为第一接入网设备发送给第二接入网设备的RAN Paging消息，CU或CU-CP发送给DU的Paging消息，或者核心网节点发送给接入网设备的Paging消息。
本公开实施例中，第一节点可以为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者，第一节点可以为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
其中，在第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点的情况下，第一节点发送下行信息，若处于非连接态的终端设备在第一节点的覆盖范围内，则可以保证下行信息能够准确的发送至终端设备，但是，若处于非连接态的终端设备不在第一节点的覆盖范围内，则下行信息将无法准确的发送至终端设备。同理，对于处于非连接态的终端设备发送的上行信息，若处于非连接态的终端设备在第一节点的覆盖范围内，则可以保证上行信息能够准确的发送至第一节点，但是，若处于非连接态的终端设备不在第一节点的覆盖范围内，则上行信息将无法准确的发送至第一节点。
本公开实施例中，第一节点向第二节点发送第一消息，其中，第一节点可以向一个或多个第二节点发送第一消息，在第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息的情况下，某一个第二节点接收到终端设备的第一请求消息，则可以确定该第二节点能够与处于非连接态的终端设备进行上下行数据和/或信令的收发，也即可以确定处于非连接态的终端设备在该第二节点的覆盖范围内，基于此，指示该第二节点根据第一信息发送和/或接收SDT的信息，能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，在第一节点为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点的情况下，第一节点无法向处于非连接态的终端设备发送下行信息，也无法接收终端设备发送的上行信息。
本公开实施例中，第一节点向第二节点发送第一消息，其中，第一节点可以向一个或多个第二节点发送第一消息，在第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息的情况下，某一个第二节点接收到终端设备的第一请求消息，则可以确定该第二节点能够与处于非连接态的终端设备进行上下行数据和/或信令的收发，基于此，指示该第二节点根据第一信息发送和/或接收SDT的信息，能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
基于此，本公开实施例中，第一节点确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。从而，第二节点可以将第一节点需要发送和/或接收的SDT的信息，根据第一信息进行发送和/或接收。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
通过实施本公开实施例中，第一节点确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点，向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括部分终端设备上下文信息。
其中，部分终端设备上下文信息是用于被寻呼终端设备的SDT的信息的接收和发送的，可以包括用于SDT的DRB(data radio bearer，数据无线承载)和/或SRB(signaling radiobearer，信令无线承载)的相关配置信息，例如，可以包括RLC(Radio Link Control，无线链路控制)层的传输模式等配置信息，第二节点接收部分终端设备上下文信息后，可以根据部分终端设备上下文信息，向终端设备发送下行SDT的信息和/或从终端设备接收上行SDT的信息，其中，下行SDT的信息包括下行SDT的数据和/或信令，上行SDT的信息包括上行SDT的数据和/或信令。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括上行TNL(UL transport network layer，上行传输网络层)信息。
其中，上行TNL信息用于指示UP传输层的信息，第二节点可以根据上行TNL信息向第一节点发送上行SDT的信息，其中，上行SDT的信息包括上行SDT的数据和/或信令。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括MT-SDT方式。
其中，MT-SDT方式，例如：4-step RA-SDT、2-step RA-SDT、CG-SDT或SPS-SDT，第二节点可以考虑MT-SDT方式，为终端设备配置SDT的资源和/或准备与SDT相关的资源。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括MT-SDT类型。
其中，MT-SDT类型可以指示本次SDT传输的数据或信令是下行和/或上行，或者MT-SDT类型可以指示本次SDT传输的数据类型是数据还是信令，例如，可以是以下四种类型的任意一种组合只有上行(DL-only)、上行和下行(DL+UL)、信令(signalling)和/或数据(data)等，第二节点可以考虑MT-SDT类型，为终端设备配置SDT资源和/或与准备SDT相关的资源。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括终端设备的上行传输特性。
其中，终端设备的上行传输特性可以是终端设备上行数据或信令的数据大小或周期，例如，可以是QoE报告上报的周期和/或大小或终端设备定位信息上报的周期和/或大小，第二节点可以考虑终端设备的上行传输特性，为终端设备分配上行SDT的相关资源和配置。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括终端设备的下行传输特性。
在一些实施例中，终端设备的下行传输特性可以是终端设备下行数据或信令的数据大小和/或周期；在另一些实施例中，终端设备的下行传输特性可以是指下行数据或信令是单个还是多个。第二节点可以考虑终端设备的下行传输特性，为终端设备分配下行SDT的相关资源和配置。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
本公开实施例中，第二节点接收第一节点发送的第一消息，获取第一消息中的第一信息，可以考虑第一信息，为终端设备配置SDT资源和/或准备与SDT相关的资源，例如：建立SDT RLC实体。
在一些实施例中，如果第一节点具有用户平面功能(例如，接入网设备、UPF、gNB-CU-UP)，第一节点可以自己通过包检测识别，获取终端设备的下行传输特性；如果第一节点具有控制平面功能(例如基站、SMF/AMF、gNB-CU或gNB-CU-CP，终端设备的下行传输特性可以由其他节点发送给第一节点，例如AF(Application Function)向AMF/SMF发送，或者AMF/SMF向接入网设备或gNB-CU或gNB-CU-CP发送，或者UPF向接入网设备或gNB-CU-UP发送。
在一些实施例中，第一节点接收第二节点发送的第二消息，其中，第二消息为第二节点在接收到终端设备发送的第一请求消息后发送的，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息，第一请求消息为终端设备对于第二节点的寻呼的响应。
本公开实施例中，第二节点接收第一节点发送的第一消息之后，可以考虑第一消息和第一信息，向终端设备发送寻呼。
其中，终端设备若在第二节点的覆盖范围内，或者第二节点可以直接与处于非连接态的终端设备进行上下行信息的收发，则可以向终端设备发送寻呼，并且，终端设备接收到第二节点发送的寻呼后，会向第二节点发送响应寻呼的第一请求消息。
本公开实施例中，第一请求消息可以为随机接入请求和/或RRC恢复请求(RRC Resume Request)，可选地，也可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。
基于此，第二节点在接收到终端设备发送的响应寻呼的第一请求消息之后，可以向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求 第一节点向第二节点发送SDT的信息。
其中，第二消息可以为第二接入网设备发送给第一接入网设备的检索终端设备上下文请求(RETRIEVE UE CONTEXT REQUEST)消息，或者DU发送给CU或CU-CP的初始UL RRC消息传输(INITIAL UL RRC MESSAGE TRANSFER)消息或其他F1AP消息，或者接入网设备发送给核心网节点的初始UE上下文请求(INITIAL UE CONTEXT REQUEST)消息或其他NGAP消息。
可以理解的是，第二节点向第一节点发送第二消息，以告知第一节点，处于非连接态的终端设备在第二节点的覆盖范围内，第二节点可以向终端设备发送下行SDT的信息，或者，第二节点接收终端设备发送的第一请求消息，第一请求消息中携带上行SDT的信息，第二节点向第一节点发送的第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，以向第一节点发送上行SDT的信息。
在一些实施例中，第二信息，包括以下至少一个：
MT-SDT指示；
下行传输网络层TNL信息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息包括MT-SDT指示。
其中，MT-SDT指示，用于指示第二消息是由于MT-SDT发起的，例如可以resume cause可以是MT-SDT。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息包括下行TNL信息。
其中，下行TNL信息用于指示UP传输层的信息，第一节点可以根据下行TNL信息向第二节点发送下行SDT的信息，其中，下行SDT的信息包括下行SDT数据和/或信令。
其中，下行TNL信息在第二消息中发送，能让下行SDT的信息更快地发送给终端设备。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一节点根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
本公开实施例中，第一节点接收到第二节点发送的第二消息后，可以根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
基于此，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确和高效的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在另一些实施例中，第一节点向第二节点发送第三信息，其中，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
本公开实施例中，第一节点向第二节点发送第三信息，可以与第一消息同时发送，或者在第一消息之前或之后发送，
在一些实施例中，第三信息被包括在第一消息和/或第三消息中。
可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。
其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示第三消息中包括的第三信息所对应的终端设备。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，还包括下行SDT的数据。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，还包括下行SDT的信令。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，还包括下行SDT的数据和信令。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
可以理解的是，第一节点向第二节点发送第一消息，第一消息中包括第一信息，还包括下行SDT 的数据和/或信令的情况下，第二节点根据第一信息向终端设备发送寻呼，第二节点在接收到终端设备响应寻呼的第一请求消息的情况下，由于第二节点已经接收到第一节点发送的下行SDT的信息，可以直接将下行SDT的信息发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第一节点接收第二节点发送的第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，可以向第一节点发送第一指示信息，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第一指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
下行TNL信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括下行(DL)TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在另一些实施例中，第一节点接收第二节点发送的第二指示信息，其中，第二指示信息为第二节点在接收到终端设备发送的响应消息的情况下发送的，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，终端设备若成功接收到第二节点发送的下行SDT的数据和/或信令，可以向第二节点发送响应消息，第二节点接收到终端设备发送的响应消息，可以确定终端设备成功接收到下行SDT的数据和/或信令。
在此情况下，第二节点向第一节点发送第二指示信息，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第二指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息可以包括DL TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一指示信息和/或第二指示信息可以为SDT delivery notification，SDT delivery notification用于通知第一节点下行SDT的数据和/或信令是否已经发送给终端设备，第一节点可以考虑SDT delivery notification，决定是否继续寻呼终端设备。
在一些实施例中，第一节点在接收到第二节点发送的第一指示信息和/或第二指示信息的情况下，可以确定下行SDT的信息已经传输完成，第一节点可以向第二节点发送RETRIEVE UE CONTEXT FAILURE消息以响应第二节点的第一指示信息和/或第二指示信息，其中，RETRIEVE UE CONTEXT FAILURE消息包括一个封装的RRC Release消息。
在一些实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备，第一接入网设备为最 后一个服务于终端设备的接入网设备，第二接入网设备为当前服务于终端设备的接入网设备。
本公开实施例中，第一节点为第一接入网设备，可以为最后服务于终端设备的接入网设备，第一接入网设备(最后服务于终端设备的接入网设备)向终端设备发送RRC释放(RRCRelease)消息，使得终端设备的状态从连接态(RRC_CONNECTED)转变为非连接态(RRC_IDLE状态或RRC_INACTIVE状态)。
可以理解的是，第一接入网设备与处于非连接态的终端设备之间不存在RRC连接，第一接入网设备无法确定终端设备此时是否在其覆盖范围内，也即，第一接入网设备无法确定其向终端设备发送的信息终端设备是否能够接收到，以及也无法确定是否能够准确接收终端设备发送的信息。
在此情况下，第一接入网设备可以确定需要发送和/或接收的SDT的信息，向一个或多个第二接入网设备发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二接入网设备在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，第二节点为第二接入网设备，而第二接入网设备为当前服务于终端设备的接入网设备，第二接入网设备可以接收到终端设备发送的第一请求消息，则说明此时处于非连接态的终端设备位于第二接入网设备的覆盖范围内，第二接入网设备可以与处于非连接态的终端设备进行上下行信息的收发，从而，第二接入网设备可以根据第一信息，发送SDT的信息和/或接收SDT的信息。由此，能够避免传输失败和资源的浪费。
本公开实施例中，第一接入网设备作为最后服务终端设备的节点，并且当前处于非连接态的终端设备不在第一接入网设备的覆盖范围内，第一接入网设备为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。本公开实施例中，第一接入网设备向第二接入网设备发送第一消息，而第二接入网设备可以接收到终端设备发送的第一请求消息，说明此时处于非连接态的终端设备位于第二接入网设备的覆盖范围内，第二接入网设备可以与处于非连接态的终端设备进行上下行信息的收发，从而，第二接入网设备可以根据第一信息，发送SDT的信息和/或接收SDT的信息。由此，无法确定处于非连接态的终端设备是否在其覆盖范围内的第一接入网设备，可以通过当前服务终端设备的第二接入网设备与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
本公开实施例中，第一接入网设备可以向一个或多个第二接入网设备发送第一消息。
可以理解的是，当且仅当第二接入网设备为当前服务于终端设备的接入网设备时，也即处于非连接态的终端设备位于第二接入网设备的覆盖范围内时，第二接入网设备才能够接收到处于非连接态的终端设备发送的第一请求消息，也即，第一接入网设备可以向一个或多个第二接入网设备发送第一消息，而仅有一个第二接入网设备能够接收到终端设备的第一请求消息，基于此，第二接入网设备在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
在一些实施例中，第一消息为以下至少一个：
无线接入网RAN寻呼消息；
部分终端设备上下文传输消息；
Xn应用协议XnAP消息。
本公开实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备的情况下，第一接入网设备可以向第二接入网设备发送第一消息，第一消息可以为无线接入网RAN寻呼消息。
本公开实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备的情况下，第一接入网设备可以向第二接入网设备发送第一消息，第一消息可以为部分终端设备上下文传输消息。
本公开实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备的情况下，第一接入网设备可以向第二接入网设备发送第一消息，第一消息可以为Xn应用协议XnAP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第二消息为以下至少一个：
检索终端设备上下文请求消息；
部分终端设备上下文确认消息；
Xn应用协议XnAP消息。
本公开实施例中，第二节点向第一节点发送第二消息，可以向第一节点发送检索终端设备上下文请求消息。
本公开实施例中，第二节点向第一节点发送第二消息，可以向第一节点发送部分终端设备上下文确认消息。
本公开实施例中，第二节点向第一节点发送第二消息，可以向第一节点发送Xn应用协议XnAP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
通过实施本公开实施例，在第一接入网设备不是最后服务终端设备的接入网设备的情况下，支持终端设备在RRC_INACTIVE状态下接收下行数据和/或发送上行数据，并且第一接入网设备也可以根据上/下行数据的类型和特性为终端设备配置合适的资源，可以减少不必要的调度开销，节省了空口资源，并且也能为终端设备省电。
在一些实施例中，第一节点为核心网节点，第二节点为接入网设备。
本公开实施例中，第一节点为核心网节点，核心网节点无法直接与处于非连接态的终端设备进行上下行信息的收发，第二节点为接入网设备，接入网设备可以直接与处于非连接态的终端设备进行上下行信息的收发。
本公开实施例中，核心网节点可以确定需要发送和/或接收的SDT的信息，向接入网设备发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示接入网设备在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，接入网设备能够接收到终端设备的第一请求消息，则说明接入网设备能够直接与处于非连接态的终端设备进行上下行信息的收发。由此，无法直接与处于非连接态的终端设备进行上下行信息的收发的核心网节点，可以通过接入网设备与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，核心网节点为以下至少一个：
接入和移动性管理功能AMF；
会话管理功能设备SMF；
用户面功能设备UPF。
本公开实施例中，核心网节点可以为AMF。
本公开实施例中，核心网节点可以为SMF。
本公开实施例中，核心网节点可以为UPF。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一消息为以下至少一个：
下一代应用协议NGAP消息；
包括在用户平面数据中的消息。
本公开实施例中，第一节点为核心网节点，第二节点为接入网设备的情况下，核心网节点向接入网设备发送第一消息，可以向接入网设备发送NGAP消息，例如：Paging消息。
本公开实施例中，第一节点为核心网节点，第二节点为接入网设备的情况下，核心网节点向接入网设备发送第一消息，可以向接入网设备发送包括在用户平面数据中的消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一节点为集中单元用户面CU-UP，第二节点为集中单元控制面CU-CP。
本公开实施例中，第一节点为CU-UP，CU-UP无法直接与处于非连接态的终端设备进行上下行信息的收发，第二节点为CU-CP，CU-CP可以直接与处于非连接态的终端设备进行上下行信息的收发。
本公开实施例中，CU-UP可以确定需要发送和/或接收的SDT的信息，向CU-CP发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示CU-CP在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，CU-CP能够接收到终端设备的第一请求消息，则说明CU-CP能够直接与处于非连接态的终端设备进行上下行信息的收发。由此，无法直接与处于非连接态的终端设备进行上下行信息的收发的CU-UP，可以通过CU-CP与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第一消息为以下至少一个：
下行数据通知消息；
承载上下文修改需求消息；
E1应用协议E1AP消息。
本公开实施例中，第一节点为CU-UP，第二节点为CU-CP的情况下，CU-UP向CU-CP发送第一消息，可以向CU-CP发送下行数据通知消息(DL Data Notification)。
本公开实施例中，第一节点为CU-UP，第二节点为CU-CP的情况下，CU-UP向CU-CP发送第一消息，可以向CU-CP发送承载上下文修改需求消息(BEARER CONTEXT MODIFICATION REQUIRED)。
本公开实施例中，第一节点为CU-UP，第二节点为CU-CP的情况下，CU-UP向CU-CP发送第一消息，可以向CU-CP发送E1应用协议E1AP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一节点为集中单元CU或CU-CP，第二节点为分布单元DU。
本公开实施例中，第一节点为CU或CU-CP，CU或CU-CP无法直接与处于非连接态的终端设备进行上下行信息的收发，第二节点为DU，DU可以直接与处于非连接态的终端设备进行上下行信息的收发。
本公开实施例中，CU或CU-CP可以确定需要需要发送和/或接收的SDT的信息，向DU发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示DU在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，DU能够接收到终端设备的第一请求消息，则说明DU能够直接与处于非连接态的终端设备进行上下行信息的收发。由此，无法直接与处于非连接态的终端设备进行上下行信息的收发的CU或CU-CP，可以通过DU与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第一消息为以下至少一个：
寻呼消息；
终端设备上下文修改请求消息；
终端设备上下文建立请求消息；
F1应用协议F1AP消息。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送寻呼消息(Paging)。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送终端设备上下文修改请求消息(UE CONTEXT MODIFICATION REQUEST)。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送终端设备上下文建立请求消息(UE CONTEXT SETUP REQUEST)。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送F1应用协议F1AP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第二消息为以下至少一个：
SDT发送通知消息；
初始UL RRC消息传输消息；
F1应用协议F1AP消息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息可以为SDT发送通知消息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息可以为初始上行(UL)RRC消息传输消息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息可以为F1应用协议F1AP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
为了方便理解本公开实施例，提供一示例性实施例：
如图5a所示，第一节点为最后服务终端设备的第一接入网设备，当前处于非连接态的终端设备在第二节点的覆盖范围内，第二节点为第二接入网设备。
其中，第一接入网设备无法确定处于非连接态的终端设备是否在其覆盖范围内，在此情况下，1)第一接入网设备可以向第二接入网设备发送第一消息(RAN寻呼)，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
2)第二接入网设备接收到第一接入网设备发送的RAN寻呼之后，会向其覆盖范围内的终端设备发送寻呼。
3)若处于非连接态的终端设备在第二接入网设备的覆盖范围内，终端设备会向第二接入网设备发送响应寻呼的第一请求消息，第一请求消息可以为RA/RRCResume Request，4)第二接入网设备接收到终端设备发送的第一请求消息，可以确定此时处于非连接态的终端设备在其覆盖范围内，第二接入网设备可以与终端设备进行上下行信息的收发，第二接入网设备向第一接入网设备发送第二消息(RETRIEVE UE CONTEXT REQUEST消息)，以从第一接入网设备处获取下行SDT的信息，其中，第二消息中包括第二信息，第二信息包括以下至少一个：
MT-SDT指示；
下行传输网络层TNL信息。
5)第一接入网设备根据第二接入网设备发送的RETRIEVE UE CONTEXT REQUEST消息中的第二信息，向第二接入网设备发送下行SDT的信息，第二接入网设备可以进一步将下行SDT的信息发送至终端设备。
其中，3)终端设备向第二接入网设备发送的第一请求消息可以携带上行SDT的信息，5)第二接入网设备接收到终端设备发送的第一请求消息，可以将上行SDT的信息发送至第一接入网设备。
之后，在SDT的信息(包括上行SDT的信息和/或下行SDT的信息)传输完成后，6)第一接入网设备可以向第二接入网设备发送RETRIEVE UE CONTEXT FAILURE消息，以响应第一接入网设备，其中，RETRIEVE UE CONTEXT FAILURE消息包括一个封装的RRC Release消息。第二接入网设备接收到RETRIEVE UE CONTEXT FAILURE消息后，可以将RRC Release消息发送至终端设备，终端设备接收到RRC Release消息后，可以保持在非连接态。
需要说明的是，上述示例性实施例中的第一消息、第二消息、第一请求消息等的相关描述可以参见上述实施例中的相关描述，此处仅作为理解，不作为对本公开实施例的具体限制。
为了方便理解本公开实施例，提供另一示例性实施例：
如图5b所示，第一节点为最后服务终端设备的第一接入网设备，当前处于非连接态的终端设备在第二节点的覆盖范围内，第二节点为第二接入网设备。
其中，第一接入网设备无法确定处于非连接态的终端设备是否在其覆盖范围内，在此情况下，1)第一接入网设备可以向第二接入网设备发送第一消息(RAN寻呼)，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
其中，第三消息被包括在第一消息和/或第三消息中。可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示第三消息中包括的第三信息所对应的终端设备。
2)第二接入网设备接收到第一接入网设备发送的RAN寻呼之后，会向其覆盖范围内的终端设备发送寻呼。
3)若处于非连接态的终端设备在第二接入网设备的覆盖范围内，终端设备会向第二接入网设备发送响应寻呼的第一请求消息，第一请求消息可以为RA/RRCResume Request，4)第二接入网设备接收到终端设备发送的第一请求消息，可以确定此时处于非连接态的终端设备在其覆盖范围内，第二接入网设备可以与终端设备进行上下行信息的收发，第二接入网设备可以向终端设备发送下行SDT的数据和/或信令。5)第二接入网设备向终端设备发送下行SDT的数据和/或信令之后，可以向第一接入网设备发送第一指示信息，以告知第一接入网设备，下行SDT的数据和/或信令已经发送给终端设备，或者， 可以向第一接入网设备发送第二指示信息，以告知第一接入网设备，下行SDT的数据和/或信令已经成功发送至终端设备。
其中，可选的，所述第一指示信息和第二指示信息包括DL TNL信息，以便第一网络设备将后续的下行的SDT信息更快地通过第二网络设备发送给终端设备。
需要说明的是，上述示例性实施例中的第一消息、第二消息、第一请求消息等的相关描述可以参见上述实施例中的相关描述，此处仅作为理解，不作为对本公开实施例的具体限制。
请参见图6，图6是本公开实施例提供的另一种数据传输方法的流程图。
如图6所示，该方法由第一节点执行，该方法可以包括但不限于如下步骤：
S61：确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
S62：向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
其中，S61和S62的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S63：接收第二节点发送的第二消息，其中，第二消息为第二节点在接收到终端设备发送的第一请求消息后发送的，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息，第一请求消息为终端设备对于第二节点的寻呼的响应。
本公开实施例中，第二节点接收第一节点发送的第一消息之后，可以考虑第一消息和第一信息，向终端设备发送寻呼。
其中，终端设备若在第二节点的覆盖范围内，或者第二节点可以直接与处于非连接态的终端设备进行上下行信息的收发，则可以向终端设备发送寻呼，并且，终端设备接收到第二节点发送的寻呼后，会向第二节点发送响应寻呼的第一请求消息。
本公开实施例中，第一请求消息可以为随机接入请求和/或RRC Resume Request，可选地，也可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。
基于此，第二节点在接收到终端设备发送的响应寻呼的第一请求消息之后，可以向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。第二消息可以为RETRIEVE UE CONTEXT REQUEST消息。
可以理解的是，第二节点向第一节点发送第二消息，以告知第一节点，处于非连接态的终端设备在第二节点的覆盖范围内，第二节点可以向终端设备发送下行SDT的信息，或者，第二节点接收终端设备发送的第一请求消息，第一请求消息中携带上行SDT的信息，第二节点向第一节点发送的第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，以向第一节点发送上行SDT的信息。
在一些实施例中，第二信息，包括以下至少一个：
MT-SDT指示；
下行传输网络层TNL信息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息包括MT-SDT指示。
其中，MT-SDT指示，用于指示第二消息是由于MT-SDT发起的，例如可以resume cause可以是MT-SDT。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息包括下行TNL信息。
其中，下行TNL信息用于指示UP传输层的信息，第一节点可以根据下行TNL信息向第二节点发送下行SDT的信息，其中，下行SDT的信息包括下行SDT数据和/或信令。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施， 也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
S64：根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
本公开实施例中，第一节点接收到第二节点发送的第二消息后，可以根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S61至S63可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51和S52一起被实施，本公开实施例并不对此做出限定。
请参见图7，图7是本公开实施例提供的又一种数据传输方法的流程图。
如图7所示，该方法由第一节点执行，该方法可以包括但不限于如下步骤：
S71：确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
S72：向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S73：接收第二节点发送的第二消息，其中，第二消息为第二节点在接收到终端设备发送的第一请求消息后发送的，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息，第一请求消息为终端设备对于第二节点的寻呼的响应。
S74：根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
其中，S71至S74的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S75：接收第二节点发送的第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，可以向第一节点发送第一指示信息，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第一指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括DL TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S71至S75可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51与S52和/或S61至S63一起被实施，本公开实施例并不对此做出限定。
请参见图8，图8是本公开实施例提供的又一种数据传输方法的流程图。
如图8所示，该方法由第一节点执行，该方法可以包括但不限于如下步骤：
S81：确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
S82：向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S83：接收第二节点发送的第二消息，其中，第二消息为第二节点在接收到终端设备发送的第一请求消息后发送的，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息，第一请求消息为终端设备对于第二节点的寻呼的响应。
S84：根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
其中，S81至S84的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S85：接收第二节点发送的第二指示信息，其中，第二指示信息为第二节点在接收到终端设备发送的响应消息的情况下发送的，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，终端设备若成功接收到第二节点发送的下行SDT的数据和/或信令，可以向第二节点发送响应消息，第二节点接收到终端设备发送的响应消息，可以确定终端设备成功接收到下行SDT的数据和/或信令。
在此情况下，第二节点向第一节点发送第二指示信息，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第二指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息可以包括DL TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进 行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S81至S85可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51与S52和/或S61至S63一起被实施，本公开实施例并不对此做出限定。
请参见图9，图9是本公开实施例提供的又一种数据传输方法的流程图。
如图9所示，该方法由第一节点执行，该方法可以包括但不限于如下步骤：
S91：确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
S92：向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，S91和S92的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
其中，第三消息被包括在第一消息和/或第三消息中。可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示第三消息中包括的第三信息所对应的终端设备。
其中，第一信息和第一消息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
可以理解的是，第一节点向第二节点发送第一消息，第一消息中包括第一信息，还包括下行SDT的数据和/或信令的情况下，第二节点根据第一信息向终端设备发送寻呼，第二节点在接收到终端设备响应寻呼的第一请求消息的情况下，由于第二节点已经接收到第一节点发送的下行SDT的信息，可以直接将下行SDT的信息发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
S93：接收第二节点发送的第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
其中，S93的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S91至S93可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51与S52一起被实施，本公开实施例并不对此做出限定。
请参见图10，图10是本公开实施例提供的又一种数据传输方法的流程图。
如图10所示，该方法由第一节点执行，该方法可以包括但不限于如下步骤：
S101：确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
S102：向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，S101和S102的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
其中，第三消息被包括在第一消息和/或第三消息中。可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示第三消息中包括的第三信息所对应的终端设备。
其中，第一信息和第一消息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
可以理解的是，第一节点向第二节点发送第一消息，第一消息中包括第一信息，还包括下行SDT的数据和/或信令的情况下，第二节点根据第一信息向终端设备发送寻呼，第二节点在接收到终端设备响应寻呼的第一请求消息的情况下，由于第二节点已经接收到第一节点发送的下行SDT的信息，可以直接将下行SDT的信息发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
S103：接收第二节点发送的第二指示信息，其中，第二指示信息为第二节点在接收到终端设备发送的响应消息的情况下发送的，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
其中，S103的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S101至S103可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S51与S52一起被实施，本公开实施例并不对此做出限定。
请参见图11，图11是本公开实施例提供的又一种数据传输方法的流程图。
如图11所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S111：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
其中，第一消息可以为第一接入网设备发送给第二接入网设备的RAN Paging消息，CU或CU-CP发送给DU的Paging消息，或者核心网节点发送给接入网设备的Paging消息。
本公开实施例中，第一节点可以为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者，第一节点可以为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
其中，在第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点的情况下，第一节点发送下行信息，若处于非连接态的终端设备在第一节点的覆盖范围内，则可以保证下行信息能够准确的发送至终端设备，但是，若处于非连接态的终端设备不在第一节点的覆盖范围内，则下行信息将无法准确的发送至终端设备。同理，对于处于非连接态的终端设备发送的上行信息，若处于非连接态的终 端设备在第一节点的覆盖范围内，则可以保证上行信息能够准确的发送至第一节点，但是，若处于非连接态的终端设备不在第一节点的覆盖范围内，则上行信息将无法准确的发送至第一节点。
本公开实施例中，第一节点向第二节点发送第一消息，其中，第一节点可以向一个或多个第二节点发送第一消息，在第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息的情况下，某一个第二节点接收到终端设备的第一请求消息，则可以确定该第二节点能够与处于非连接态的终端设备进行上下行数据的收发，也即可以确定处于非连接态的终端设备在该第二节点的覆盖范围内，基于此，指示该第二节点根据第一信息发送和/或接收SDT的信息，能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，在第一节点为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点的情况下，第一节点无法向处于非连接态的终端设备发送下行信息，也无法接收终端设备发送的上行信息。
本公开实施例中，第一节点向第二节点发送第一消息，其中，第一节点可以向一个或多个第二节点发送第一消息，在第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息的情况下，某一个第二节点接收到终端设备的第一请求消息，则可以确定该第二节点能够与处于非连接态的终端设备进行上下行数据的收发，基于此，指示该第二节点根据第一信息发送和/或接收SDT的信息，能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
基于此，本公开实施例中，第一节点确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。从而，第二节点可以将第一节点需要发送和/或接收的SDT的信息，根据第一信息进行发送和/或接收。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
本公开实施例中，第一消息为第一节点确定需要发送和/或接收的小数据包传输SDT的信息的情况下发送的，其中，信息包括数据和/或信令。
其中，第一节点确定需要发送的SDT的信息，可以确定需要发送的SDT的数据，或者，确定需要发送的SDT的信令，或者确定需要发送的SDT的数据和信令。
其中，第一节点确定需要接收的SDT的信息，可以确定需要接收的SDT的数据，或者，确定需要接收的SDT的信令，或者确定需要接收的SDT的数据和信令。
其中，第一节点确定需要发送和接收的SDT的信息，可以确定需要发送和接收的SDT的数据，或者，确定需要发送和接收的SDT的信令，或者确定需要发送和接收的SDT的数据和信令。
可以理解的是，第一节点确定需要发送和/或接收的SDT的信息，可以确定需要发送至处于非连接态的终端设备的SDT的信息，和/或，确定需要接收来自处于非连接态的终端设备的SDT的信息。
在一些实施例中，第一节点可以为接入网设备，接入网设备确定需要发送和/或接收的SDT的信息，可以确定需要发送的SDT的数据和/或信令，可以确定需要接收的SDT的数据和/或信令。
其中，接入网设备可以从核心网节点处获取需要发送的SDT的数据和/或信令，以确定需要发送的SDT的数据和/或信令，并且，接入网设备可以根据其发出的SDT的数据和/或信令，确定是否存在需要接收的SDT的数据和/或信令。
当然，接入网设备还可以根据其他信息确定发送的SDT的数据和/或信令，和/或确定需要接收的SDT的数据和/或信令，本公开实施例对此不作具体限制。
在另一些实施例中，第一节点可以为核心网节点，例如：AMF(Core Access and MobilityManagement Function，接入和移动性管理功能)，或者UPF(User Plane Function，用户面功能设备)，或者SMF(Session Management Function，会话管理功能设备)等。
其中，核心网节点确定需要发送和/或接收的SDT的信息，可以确定需要发送的SDT的数据和/或信令，可以确定需要接收的SDT的数据和/或信令。
其中，核心网节点可以根据其本身的信息，确定需要发送的SDT的数据和/或信令，并且，核心网节点可以根据其发出的SDT的数据和/或信令，确定是否存在需要接收的SDT的数据和/或信令。
当然，核心网节点还可以根据其他信息确定发送的SDT的数据和/或信令，和/或确定需要接收的SDT的数据和/或信令，本公开实施例对此不作具体限制。
在又一些实施例中，第一节点可以为集中单元CU，或者集中单元用户面CU-UP。CU或CU-UP确定需要发送和/或接收的SDT的信息，可以确定需要发送的SDT的数据和/或信令，可以确定需要接收的SDT的数据和/或信令。
其中，CU或CU-UP可以与核心网节点通信，从核心网节点处获取需要发送的SDT的数据和/或信 令，以确定需要发送的SDT的数据和/或信令，并且，CU或CU-UP可以根据其发出的SDT的数据和/或信令，确定是否存在需要接收的SDT的数据和/或信令。
当然，CU或CU-UP还可以根据其他信息确定发送的SDT的数据和/或信令，和/或确定需要接收的SDT的数据和/或信令，本公开实施例对此不作具体限制。
通过实施本公开实施例中，第一节点确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点，向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第二节点接收终端设备发送的第一请求消息，其中，第一请求消息用于指示上行SDT的数据和/或信令。
本公开实施例中，第二节点接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令。
其中，第二节点在接收到终端设备发送的第一请求消息，第一请求消息用于指示上行SDT的数据和/或信令的情况下，第二节点可以根据第一信息向第一节点发送上行SDT的数据和/或信令。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第二节点根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
本公开实施例中，第二节点接收第一节点发送的第一消息之后，可以考虑第一消息和第一信息，向终端设备发送寻呼。
其中，终端设备若在第二节点的覆盖范围内，或者第二节点可以直接与处于非连接态的终端设备进行上下行信息的收发，则可以向终端设备发送寻呼，并且，终端设备接收到第二节点发送的寻呼后，会向第二节点发送响应寻呼的第一请求消息。其中，第一请求消息可以为随机接入请求和/或RRC Resume Request。
本公开实施例中，终端设备向第二节点发送响应寻呼的第一请求消息，可选地，第一请求消息可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。
在此情况下，第二节点接收到终端设备发送的第一请求消息，可以向第一节点发送上行SDT的信息，向第一节点发送上行SDT的数据和/或信令。
在一些实施例中，第二节点根据第一信息，为终端设备配置SDT资源。
本公开实施例中，终端设备向第二节点发送响应寻呼的第一请求消息，可选地，第一请求消息可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。第二节点可以根据第一请求消息，以及第一消息，为终端设备配置SDT资源。由此，可以让第二节点根据上行数据的类型和特性为终端设备配置合适的资源，可以减少不必要的调度开销，节省空口资源，并且也能为终端设备省电。
在一些实施例中，响应于未接收到终端设备发送的第一请求消息，释放SDT相关的第一信息。
本公开实施例中，第二节点接收第一节点发送的第一消息，向终端设备发送寻呼，若未接收到终端设备发送的第一请求消息，则可以确定处于非连接态的终端设备不在第二节点的覆盖范围内，或第二节点无法直接与处于非连接态的终端设备进行上下行信息的收发，在此情况下，第二节点释放SDT相关的第一信息。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括部分终端设备上下文信息。
其中，部分终端设备上下文信息是用于被寻呼终端设备的SDT的信息的接收和发送的，可以包括用于SDT的DRB(data radio bearer，数据无线承载)和/或SRB(signaling radiobearer，信令无线承载) 的相关配置信息，第二节点接收部分终端设备上下文信息后，可以根据部分终端设备上下文信息，向终端设备发送下行SDT的信息和/或从终端设备接收上行SDT的信息，其中，下行SDT的信息包括下行SDT的数据和/或信令，上行SDT的信息包括上行SDT的数据和/或信令。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括上行TNL(UL transport network layer，上行传输网络层)信息。
其中，上行TNL信息用于指示UP传输层的信息，第二节点可以根据上行TNL信息向第一节点发送上行SDT的信息，其中，上行SDT的信息包括上行SDT的数据和/或信令。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括MT-SDT方式。
其中，MT-SDT方式，例如：4-step RA-SDT、2-step RA-SDT、CG-SDT或SPS-SDT，第二节点可以考虑MT-SDT方式，为终端设备配置SDT的资源和/或准备与SDT相关的资源。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括MT-SDT类型。
其中，MT-SDT类型可以指示本次SDT传输的数据或信令是下行和/或上行，或者MT-SDT类型可以指示本次SDT传输的数据类型是数据还是信令，例如，可以是以下四种类型的任意一种组合只有上行(DL-only)、上行和下行(DL+UL)、信令(signalling)和/或数据(data)等，第二节点可以考虑MT-SDT类型，为终端设备配置SDT资源和/或与准备SDT相关的资源。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括终端设备的上行传输特性。
其中，终端设备的上行传输特性可以是终端设备上行数据或信令的数据大小或周期，例如，可以是QoE报告上报的周期和大小或终端设备定位信息上报的周期和大小，第二节点可以考虑终端设备的上行传输特性，为终端设备分配上行SDT的相关资源和配置。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，包括终端设备的下行传输特性。
在一些实施例中，终端设备的下行传输特性可以是终端设备下行数据或信令的数据大小或周期；在另一些实施例中，终端设备的下行传输特性可以是指下行数据或信令是单个还是多个。第二节点可以考虑终端设备的下行传输特性，为终端设备分配下行SDT的相关资源和配置。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
本公开实施例中，第二节点接收第一节点发送的第一消息，获取第一消息中的第一信息，可以考虑第一信息，为终端设备配置SDT资源和/或准备与SDT相关的资源，例如：建立SDT RLC实体。
在一些实施例中，如果第一节点具有用户平面功能(例如，接入网设备、UPF、gNB-CU-UP)，第一节点可以自己通过包检测识别，获取终端设备的下行传输特性；如果第一节点具有控制平面功能(例如基站、SMF/AMF、gNB-CU或gNB-CU-CP，终端设备的下行传输特性可以由其他节点发送给第一节点，例如AF(Application Function)向AMF/SMF发送，或者AMF/SMF向接入网设备或gNB-CU或gNB-CU-CP发送，或者UPF向接入网设备或gNB-CU-UP发送。
在一些实施例中，第二节点向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。
本公开实施例中，第二节点接收第一节点发送的第一消息之后，可以考虑第一消息和第一信息，向终端设备发送寻呼。
其中，终端设备若在第二节点的覆盖范围内，或者第二节点可以直接与处于非连接态的终端设备进行上下行信息的收发，则可以向终端设备发送寻呼，并且，终端设备接收到第二节点发送的寻呼后，会向第二节点发送响应寻呼的第一请求消息。
本公开实施例中，第一请求消息可以为随机接入请求和/或RRC Resume Request，可选地，也可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。
基于此，第二节点在接收到终端设备发送的响应寻呼的第一请求消息之后，可以向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。第二消息可以为RETRIEVE UE CONTEXT REQUEST消息。
可以理解的是，第二节点向第一节点发送第二消息，以告知第一节点，处于非连接态的终端设备在第二节点的覆盖范围内，第二节点可以向终端设备发送下行SDT的信息，或者，第二节点接收终端设备发送的第一请求消息，第一请求消息中携带上行SDT的信息，第二节点向第一节点发送的第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，以向第一节点发送上行SDT的信息。
在一些实施例中，第二信息，包括以下至少一个：
MT-SDT指示；
下行传输网络层TNL信息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息包括MT-SDT指示。
其中，MT-SDT指示，用于指示第二消息是由于MT-SDT发起的，例如可以resume cause可以是MT-SDT。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息包括下行TNL信息。
其中，下行TNL信息用于指示UP传输层的信息，第一节点可以根据下行TNL信息向第二节点发送下行SDT的信息，其中，下行SDT的信息包括下行SDT数据和/或信令。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第二节点接收第一节点发送的SDT的信息，其中，SDT的信息为第一节点根据第二消息发送的，SDT的信息包括下行SDT的数据和/或信令。
本公开实施例中，第一节点接收到第二节点发送的第二消息后，可以根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
基于此，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在另一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
其中，第三消息被包括在第一消息和/或第三消息中。可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示第三消息中包括的第三信息所对应的终端设备。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，还包括下行SDT的数据。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，还包括下行SDT的信令。
本公开实施例中，第一节点向第二节点发送第一消息，第一消息第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，还包括下行SDT的数据和信令。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
可以理解的是，第一节点向第二节点发送第一消息，第一消息中包括第一信息，还包括下行SDT的数据和/或信令的情况下，第二节点根据第一信息向终端设备发送寻呼，第二节点在接收到终端设备响应寻呼的第一请求消息的情况下，由于第二节点已经接收到第一节点发送的下行SDT的信息，可以直接将下行SDT的信息发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第二节点向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第二节点向第一节点发送第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，可以向第一节点发送第一指示信息，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第一指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括DL TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第二节点接收终端设备发送的响应消息，其中，响应消息用于指示终端设备接收到下行SDT的数据和/或信令。
在一些实施例中，第二节点向第一节点发送第二指示信息，其中，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，终端设备若成功接收到第二节点发送的下行SDT的数据和/或信令，可以向第二节点发送响应消息，第二节点接收到终端设备发送的响应消息，可以确定终端设备成功接收到下行SDT的数据和/或信令。
在此情况下，第二节点向第一节点发送第二指示信息，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第二指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息可以包括DL TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一指示信息和/或第二指示信息可以为SDT delivery notification，SDT delivery notification用于通知第一节点下行SDT的数据和/或信令是否已经发送给终端设备，第一节点可以考虑SDT delivery notification，决定是否继续寻呼终端设备。
在一些实施例中，第一节点在接收到第二节点发送的第一指示信息和/或第二指示信息的情况下，可以确定下行SDT的信息已经传输完成，第一节点可以向第二节点发送RETRIEVE UE CONTEXT FAILURE消息以响应第二节点的第一指示信息和/或第二指示信息，其中，RETRIEVE UE CONTEXT FAILURE消息包括一个封装的RRC Release消息。
在一些实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备，第一接入网设备为最后一个服务于终端设备的接入网设备，第二接入网设备为当前服务于终端设备的接入网设备。
本公开实施例中，第一节点为第一接入网设备，可以为最后服务于终端设备的接入网设备，第一接入网设备(最后服务于终端设备的接入网设备)向终端设备发送RRC释放(RRCRelease)消息，使得终端设备的状态从连接态(RRC_CONNECTED)转变为非连接态(RRC_IDLE状态或RRC_INACTIVE状态)。
可以理解的是，第一接入网设备与处于非连接态的终端设备之间不存在RRC连接，第一接入网设备无法确定终端设备此时是否在其覆盖范围内，也即，第一接入网设备无法确定其向终端设备发送的信息终端设备是否能够接收到，以及也无法确定是否能够准确接收终端设备发送的信息。
在此情况下，第一接入网设备可以确定需要发送和/或接收的SDT的信息，向一个或多个第二接入 网设备发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二接入网设备在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，第二节点为第二接入网设备，而第二接入网设备为当前服务于终端设备的接入网设备，第二接入网设备可以接收到终端设备发送的第一请求消息，则说明此时处于非连接态的终端设备位于第二接入网设备的覆盖范围内，第二接入网设备可以与处于非连接态的终端设备进行上下行信息的收发，从而，第二接入网设备可以根据第一信息，发送SDT的信息和/或接收SDT的信息。由此，能够避免传输失败和资源的浪费。
本公开实施例中，第一接入网设备作为最后服务终端设备的节点，并且当前处于非连接态的终端设备不在第一接入网设备的覆盖范围内，第一接入网设备为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。本公开实施例中，第一接入网设备向第二接入网设备发送第一消息，而第二接入网设备可以接收到终端设备发送的第一请求消息，说明此时处于非连接态的终端设备位于第二接入网设备的覆盖范围内，第二接入网设备可以与处于非连接态的终端设备进行上下行信息的收发，从而，第二接入网设备可以根据第一信息，发送SDT的信息和/或接收SDT的信息。由此，无法确定处于非连接态的终端设备是否在其覆盖范围内的第一接入网设备，可以通过当前服务终端设备的第二接入网设备与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
本公开实施例中，第一接入网设备可以向一个或多个第二接入网设备发送第一消息。
可以理解的是，当且仅当第二接入网设备为当前服务于终端设备的接入网设备时，也即处于非连接态的终端设备位于第二接入网设备的覆盖范围内时，第二接入网设备才能够接收到处于非连接态的终端设备发送的第一请求消息，也即，第一接入网设备可以向一个或多个第二接入网设备发送第一消息，而仅有一个第二接入网设备能够接收到终端设备的第一请求消息，基于此，第二接入网设备在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
在一些实施例中，第一消息为以下至少一个：
无线接入网RAN寻呼消息；
部分终端设备上下文传输消息；
Xn应用协议XnAP消息。
本公开实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备的情况下，第一接入网设备可以向第二接入网设备发送第一消息，第一消息可以为无线接入网RAN寻呼消息。
本公开实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备的情况下，第一接入网设备可以向第二接入网设备发送第一消息，第一消息可以为部分终端设备上下文传输消息。
本公开实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备的情况下，第一接入网设备可以向第二接入网设备发送第一消息，第一消息可以为Xn应用协议XnAP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第二消息为以下至少一个：
检索终端设备上下文请求消息；
部分终端设备上下文确认消息；
Xn应用协议XnAP消息。
本公开实施例中，第二节点向第一节点发送第二消息，可以向第一节点发送检索终端设备上下文请求消息。
本公开实施例中，第二节点向第一节点发送第二消息，可以向第一节点发送部分终端设备上下文确认消息。
本公开实施例中，第二节点向第一节点发送第二消息，可以向第一节点发送Xn应用协议XnAP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
通过实施本公开实施例，在第一接入网设备不是最后服务终端设备的接入网设备的情况下，支持终端设备在RRC_INACTIVE状态下接收下行数据和/或发送上行数据，并且第一接入网设备也可以根据上/下行数据的类型和特性为终端设备配置合适的资源，可以减少不必要的调度开销，节省了空口资源，并且也能为终端设备省电。
在一些实施例中，第一节点为核心网节点，第二节点为接入网设备。
本公开实施例中，第一节点为核心网节点，核心网节点无法直接与处于非连接态的终端设备进行上下行信息的收发，第二节点为接入网设备，接入网设备可以直接与处于非连接态的终端设备进行上下行 信息的收发。
本公开实施例中，核心网节点可以确定需要需要发送和/或接收的SDT的信息，向接入网设备发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示接入网设备在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，接入网设备能够接收到终端设备的第一请求消息，则说明接入网设备能够直接与处于非连接态的终端设备进行上下行信息的收发。由此，无法直接与处于非连接态的终端设备进行上下行信息的收发的核心网节点，可以通过接入网设备与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，核心网节点为以下至少一个：
接入和移动性管理功能AMF；
会话管理功能设备SMF；
用户面功能设备UPF。
本公开实施例中，核心网节点可以为AMF。
本公开实施例中，核心网节点可以为SMF。
本公开实施例中，核心网节点可以为UPF。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一消息为以下至少一个：
下一代应用协议NGAP消息；
包括在用户平面数据中的消息。
本公开实施例中，第一节点为核心网节点，第二节点为接入网设备的情况下，核心网节点向接入网设备发送第一消息，可以向接入网设备发送NGAP消息，例如：Paging消息。
本公开实施例中，第一节点为核心网节点，第二节点为接入网设备的情况下，核心网节点向接入网设备发送第一消息，可以向接入网设备发送包括在用户平面数据中的消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一节点为集中单元用户面CU-UP，第二节点为集中单元控制面CU-CP。
本公开实施例中，第一节点为CU-UP，CU-UP无法直接与处于非连接态的终端设备进行上下行信息的收发，第二节点为CU-CP，CU-CP可以直接与处于非连接态的终端设备进行上下行信息的收发。
本公开实施例中，CU-UP可以确定需要需要发送和/或接收的SDT的信息，向CU-CP发送第一消息，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示CU-CP在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，CU-CP能够接收到终端设备的第一请求消息，则说明CU-CP能够直接与处于非连接态的终端设备进行上下行信息的收发。由此，无法直接与处于非连接态的终端设备进行上下行信息的收发的CU-UP，可以通过CU-CP与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第一消息为以下至少一个：
下行数据通知消息；
承载上下文修改需求消息；
E1应用协议E1AP消息。
本公开实施例中，第一节点为CU-UP，第二节点为CU-CP的情况下，CU-UP向CU-CP发送第一消息，可以向CU-CP发送下行数据通知消息(DL Data Notification)。
本公开实施例中，第一节点为CU-UP，第二节点为CU-CP的情况下，CU-UP向CU-CP发送第一消息，可以向CU-CP发送承载上下文修改需求消息(BEARER CONTEXT MODIFICATION REQUIRED)。
本公开实施例中，第一节点为CU-UP，第二节点为CU-CP的情况下，CU-UP向CU-CP发送第一消息，可以向CU-CP发送E1应用协议E1AP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第一节点为集中单元CU或CU-CP，第二节点为分布单元DU。
本公开实施例中，第一节点为CU或CU-CP，CU或CU-CP无法直接与处于非连接态的终端设备进行上下行信息的收发，第二节点为DU，DU可以直接与处于非连接态的终端设备进行上下行信息的收发。
本公开实施例中，CU或CU-CP可以确定需要发送和/或接收的SDT的信息，向DU发送第一消息， 第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示DU在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
其中，DU能够接收到终端设备的第一请求消息，则说明DU能够直接与处于非连接态的终端设备进行上下行信息的收发。由此，无法直接与处于非连接态的终端设备进行上下行信息的收发的CU或CU-CP，可以通过DU与终端设备进行上下行信息的收发，能够避免传输失败和资源的浪费。
在一些实施例中，第一消息为以下至少一个：
寻呼消息；
终端设备上下文修改请求消息；
终端设备上下文建立请求消息；
F1应用协议F1AP消息。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送寻呼消息(Paging)。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送终端设备上下文修改请求消息(UE CONTEXT MODIFICATION REQUEST)。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送终端设备上下文建立请求消息(UE CONTEXT SETUP REQUEST)。
本公开实施例中，第一节点为CU或CU-CP，第二节点为DU的情况下，CU或CU-CP向DU发送第一消息，可以向DU发送F1应用协议F1AP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
在一些实施例中，第二消息为以下至少一个：
SDT发送通知消息；
初始UL RRC消息传输消息；
F1应用协议F1AP消息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息可以为SDT发送通知消息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息可以为初始UL RRC消息传输消息。
本公开实施例中，第二节点向第一节点发送第二消息，第二消息可以为F1应用协议F1AP消息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
为了方便理解本公开实施例，提供一示例性实施例：
如图11a所示，第一节点为最后服务终端设备的第一接入网设备，当前处于非连接态的终端设备在第二节点的覆盖范围内，第二节点为第二接入网设备。
其中，第一接入网设备无法确定处于非连接态的终端设备是否在其覆盖范围内，在此情况下，1)第一接入网设备可以向第二接入网设备发送RAN寻呼，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
2)第二接入网设备接收到第一接入网设备发送的RAN寻呼之后，会向其覆盖范围内的终端设备发送寻呼。
3)若处于非连接态的终端设备在第二接入网设备的覆盖范围内，终端设备会向第二接入网设备发送响应寻呼的第一请求消息，第一请求消息可以为RA/RRCResume Request，4)第二接入网设备接收到终端设备发送的第一请求消息，可以确定此时处于非连接态的终端设备在其覆盖范围内，第二接入网设备可以与终端设备进行上下行信息的收发，第二接入网设备向第一接入网设备发送第二消息(RETRIEVE UE CONTEXT REQUEST消息)，以从第一接入网设备处获取下行SDT的信息，其中，所述第二消息中包括第二信息，所述第二信息包括以下至少一个：
MT-SDT指示；
下行传输网络层TNL信息。
5)第一接入网设备根据第二信息，向第二接入网设备发送的部分终端设备上下文传输消息(PARTIAL UE CONTEXT TRANSFER消息)，其中，所述部分终端设备上下文传输消息中包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，6)第二接入网设备接收到第一接入网设备发送的部分终端设备上下文消息之后，可以根据部分终端设备上下文消息为终端设备配置SDT的资源和/或配置准备SDT的相关配置。
其中，7)第二接入网设备接收到第一接入网设备发送的部分终端设备上下文传输消息之后，可以向第一接入网设备发送部分终端设备上下文传输确认消息(PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE消息)，以告知第一接入网设备，已经接收到部分终端设备上下文传输消息。
需要说明的是，上述示例性实施例中的第一消息、第二消息、第一请求消息等的相关描述可以参见上述实施例中的相关描述，此处仅作为理解，不作为对本公开实施例的具体限制。
请参见图12，图12是本公开实施例提供的又一种数据传输方法的流程图。
如图12所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S121：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
其中，S121的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S122：接收终端设备发送的第一请求消息，其中，第一请求消息用于指示上行SDT的数据和/或信令。
S123：向第一节点发送上行SDT的数据和/或信令。
本公开实施例中，第二节点接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令。
其中，第二节点在接收到终端设备发送的第一请求消息，第一请求消息用于指示上行SDT的数据和/或信令的情况下，第二节点可以根据第一信息向第一节点发送上行SDT的数据和/或信令。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S121至S123可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
请参见图13，图13是本公开实施例提供的又一种数据传输方法的流程图。
如图13所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S131：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
其中，S131的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S132：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
本公开实施例中，第二节点接收第一节点发送的第一消息之后，可以考虑第一消息和第一信息，向终端设备发送寻呼。
其中，终端设备若在第二节点的覆盖范围内，或者第二节点可以直接与处于非连接态的终端设备进行上下行信息的收发，则可以向终端设备发送寻呼，并且，终端设备接收到第二节点发送的寻呼后，会向第二节点发送响应寻呼的第一请求消息。其中，第一请求消息可以为随机接入请求和/或RRC Resume Request。
本公开实施例中，终端设备向第二节点发送响应寻呼的第一请求消息，可选地，第一请求消息可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。
在此情况下，第二节点接收到终端设备发送的第一请求消息，可以向第一节点发送上行SDT的信息，向第一节点发送上行SDT的数据和/或信令。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S131至S132可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S121至S123一起被实施，本公开实施例并不对此做出限定。
请参见图14，图14是本公开实施例提供的又一种数据传输方法的流程图。
如图14所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S141：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S142：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
其中，S141和S142的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S143：根据第一信息，为终端设备配置SDT资源。
本公开实施例中，终端设备向第二节点发送响应寻呼的第一请求消息，可选地，第一请求消息可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。第二节点可以根据第一请求消息，以及第一消息，为终端设备配置SDT资源。由此，可以让第二节点根据上行数据的类型和特性为终端设备配置合适的资源，可以减少不必要的调度开销，节省空口资源，并且也能为终端设备省电。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S141至S143可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S121至S123和/或S131至S132一起被实施，本公开实施例并不对此做出限定。
请参见图15，图15是本公开实施例提供的又一种数据传输方法的流程图。
如图15所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S151：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
其中，S151的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S152：响应于未接收到终端设备发送的第一请求消息，释放SDT相关的第一信息。
本公开实施例中，第二节点接收第一节点发送的第一消息，向终端设备发送寻呼，若未接收到终端设备发送的第一请求消息，则可以确定处于非连接态的终端设备不在第二节点的覆盖范围内，或第二节点无法直接与处于非连接态的终端设备进行上下行信息的收发，在此情况下，第二节点释放SDT相关的第一信息。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S151至S152可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
请参见图16，图16是本公开实施例提供的又一种数据传输方法的流程图。
如图16所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S161：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S162：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
其中，S161和S162的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S163：向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。
其中，第二信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，第二节点接收第一节点发送的第一消息之后，可以考虑第一消息和第一信息，向终端设备发送寻呼。
其中，终端设备若在第二节点的覆盖范围内，或者第二节点可以直接与处于非连接态的终端设备进行上下行信息的收发，则可以向终端设备发送寻呼，并且，终端设备接收到第二节点发送的寻呼后，会向第二节点发送响应寻呼的第一请求消息。
本公开实施例中，第一请求消息可以为随机接入请求和/或RRC Resume Request，可选地，也可携带上行SDT的信息，上行SDT的信息包括上行SDT数据和/或信令。
基于此，第二节点在接收到终端设备发送的响应寻呼的第一请求消息之后，可以向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。第二消息可以为RETRIEVE UE CONTEXT REQUEST消息。
可以理解的是，第二节点向第一节点发送第二消息，以告知第一节点，处于非连接态的终端设备在第二节点的覆盖范围内，第二节点可以向终端设备发送下行SDT的信息，或者，第二节点接收终端设备发送的第一请求消息，第一请求消息中携带上行SDT的信息，第二节点向第一节点发送的第二消息中包括与处于非连接态的终端设备的SDT相关的第二信息，以向第一节点发送上行SDT的信息。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S161至S163可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
请参见图17，图17是本公开实施例提供的又一种数据传输方法的流程图。
如图17所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S171：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S172：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
S173：向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。
其中，S171至S173的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S174：接收第一节点发送的SDT的信息，其中，SDT的信息为第一节点根据第二消息发送的，SDT的信息包括下行SDT的数据和/或信令。
本公开实施例中，第一节点接收到第二节点发送的第二消息后，可以根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
基于此，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S171至S174可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S161至S163一起被实施，本公开实施例并不对此做出限定。
请参见图18，图18是本公开实施例提供的又一种数据传输方法的流程图。
如图18所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S181：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S182：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
S183：向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。
S184：接收第一节点发送的SDT的信息，其中，SDT的信息为第一节点根据第二消息发送的，SDT的信息包括下行SDT的数据和/或信令。
其中，S181至S184的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S185：向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进 行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S181至S185可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S161至S163和/或S171至S174一起被实施，本公开实施例并不对此做出限定。
请参见图19，图19是本公开实施例提供的又一种数据传输方法的流程图。
如图19所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S191：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S192：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
S193：向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。
S194：接收第一节点发送的SDT的信息，其中，SDT的信息为第一节点根据第二消息发送的，SDT的信息包括下行SDT的数据和/或信令。
S195：向终端设备发送下行SDT的数据和/或信令。
其中，S191至S195的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S196：向第一节点发送第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，可以向第一节点发送第一指示信息，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第一指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第一指示信息，第一指示信息可以包括DL TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S191至S196可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S161至S163和/或S171至S174和/或S181至S185一起被实施，本公开实施例并不对此做出限定。
请参见图20，图20是本公开实施例提供的又一种数据传输方法的流程图。
如图20所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S201：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
其中，第一信息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S202：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
S203：向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。
S204：接收第一节点发送的SDT的信息，其中，SDT的信息为第一节点根据第二消息发送的，SDT的信息包括下行SDT的数据和/或信令。
S205：向终端设备发送下行SDT的数据和/或信令。
其中，S201至S205中的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S206：接收终端设备发送的响应消息，其中，响应消息用于指示终端设备接收到下行SDT的数据和/或信令。
S207：向第一节点发送第二指示信息，其中，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
本公开实施例中，第二节点向终端设备发送下行SDT数据和/或信令后，终端设备若成功接收到第二节点发送的下行SDT的数据和/或信令，可以向第二节点发送响应消息，第二节点接收到终端设备发送的响应消息，可以确定终端设备成功接收到下行SDT的数据和/或信令。
在此情况下，第二节点向第一节点发送第二指示信息，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第二指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括终端设备标识信息。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息包括未成功发送至终端设备的指示。
本公开实施例中，第二节点向第一节点发送第二指示信息，第二指示信息可以包括DL TNL信息。
需要说明的是，上述实施例并没有穷举，仅为部分实施例的示意，并且上述实施例可以单独被实施，也可以多个进行组合被实施，上述实施例仅作为示意，不作为对本公开实施例保护范围的具体限制。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S201至S206可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S161至S163和/或S171至S174和/或S181至S185一起被实施，本公开实施例并不对此做出限定。
请参见图21，图21是本公开实施例提供的又一种数据传输方法的流程图。
如图21所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S211：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
其中，第三消息被包括在第一消息和/或第三消息中。可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示第三消息中包括的第三信息所对应的终端设备。
其中，第一信息和第一消息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S212：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
S213：向终端设备发送下行SDT的数据和/或信令。
可以理解的是，第一节点向第二节点发送第一消息，第一消息中包括第一信息，还包括下行SDT的数据和/或信令的情况下，第二节点根据第一信息向终端设备发送寻呼，第二节点在接收到终端设备响应寻呼的第一请求消息的情况下，由于第二节点已经接收到第一节点发送的下行SDT的信息，可以直接将下行SDT的信息发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S211至S213可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S131至S132一起被实施，本公开实施例并不对此做出限定。
请参见图22，图22是本公开实施例提供的又一种数据传输方法的流程图。
如图22所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S221：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
其中，第三消息被包括在第一消息和/或第三消息中。可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示第三消息中包括的第三信息所对应的终端设备。
其中，第一信息和第一消息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S222：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
S223：向终端设备发送下行SDT的数据和/或信令。
可以理解的是，第一节点向第二节点发送第一消息，第一消息中包括第一信息，还包括下行SDT的数据和/或信令的情况下，第二节点根据第一信息向终端设备发送寻呼，第二节点在接收到终端设备响应寻呼的第一请求消息的情况下，由于第二节点已经接收到第一节点发送的下行SDT的信息，可以直接将下行SDT的信息发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，S221至S223的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S224：向第一节点发送第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
其中，S224的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S221至S224可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S131至S132和/或S211至S213一起被实施，本公开实施例并不对此做出限定。
请参见图23，图23是本公开实施例提供的又一种数据传输方法的流程图。
如图23所示，该方法由第二节点执行，该方法可以包括但不限于如下步骤：
S231：接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
其中，第三消息被包括在第一消息和/或第三消息中。可以理解的是，第三信息被包括在第一消息中，第三信息与第一消息同时发送至第二节点。其中，第三信息被包括在第三消息中，第三消息可以与第一消息同时发送，或者在第一消息之前或之后发送。
其中，所述第三消息可以是XnAP上的RRC传输消息或者Xn用户平面的消息。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识，例如终端设备寻呼标识UE RAN Paging Identity，用于指示所述第三消息中包括的第三信息所对应的终端设备。
其中，第一信息和第一消息的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S232：根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
S233：向终端设备发送下行SDT的数据和/或信令。
可以理解的是，第一节点向第二节点发送第一消息，第一消息中包括第一信息，还包括下行SDT的数据和/或信令的情况下，第二节点根据第一信息向终端设备发送寻呼，第二节点在接收到终端设备响应寻呼的第一请求消息的情况下，由于第二节点已经接收到第一节点发送的下行SDT的信息，可以直接将下行SDT的信息发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
S234：接收终端设备发送的响应消息，其中，响应消息用于指示终端设备接收到下行SDT的数据和/或信令。
其中，S231至S234中的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S235：向第一节点发送第二指示信息，其中，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
其中，S235的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
本公开实施例中，第二节点在接收到第一节点发送的下行SDT的数据和/或信令的情况下，可以将下行SDT的数据和/或信令发送至终端设备。由此，第一节点能够准确的与处于非连接态的终端设备进行SDT的信息的收发，能够避免传输失败和资源的浪费。
其中，第一节点和第二节点的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，本公开实施例中，S231至S235可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111和/或S131至S132和/或S211至S213一起被实施，本公开实施例并不对此做出限定。
上述本公开提供的实施例中，分别从第一节点、第二节点的角度对本公开实施例提供的方法进行了介绍。为了实现上述本公开实施例提供的方法中的各功能，第一节点和第二节点可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图24，为本公开实施例提供的一种通信装置1的结构示意图。图24所示的通信装置1可包括收发模块11和处理模块12。收发模块可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块可以实现发送功能和/或接收功能。
通信装置1为第一节点：
该通信装置1，包括：收发模块11和处理模块12。
处理模块，被配置为确定需要发送和/或接收的小数据包传输SDT的信息，其中，信息包括数据和/或信令，第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点；
收发模块，被配置为向第二节点发送第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
移动被叫MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，收发模块11，还被配置为接收第二节点发送的第二消息，其中，第二消息为第二节点在接收到终端设备发送的第一请求消息后发送的，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息，第一请求消息为终端设备对于第二节点的寻呼的响应。
在一些实施例中，第二信息，包括以下至少一个：
MT-SDT指示；
下行传输网络层TNL信息。
在一些实施例中，收发模块11，还被配置为根据第二消息，向第二节点发送SDT的信息，其中，SDT的信息包括下行SDT的数据和/或信令。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
在一些实施例中，第三消息被包括在第一消息和/或第三消息中。
在一些实施例中，第三消息，还可以包括与终端设备相关的标识。
在一些实施例中，收发模块11，还被配置为接收第二节点发送的第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，收发模块11，还被配置为接收第二节点发送的第二指示信息，其中，第二指示信息为第二节点在接收到终端设备发送的响应消息的情况下发送的，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第一指示信息和/或第二指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
在一些实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备，第一接入网设备为最后一个服务于终端设备的接入网设备，第二接入网设备为当前服务于终端设备的接入网设备。
在一些实施例中，第一消息为以下至少一个：
无线接入网RAN寻呼消息；
部分终端设备上下文传输消息；
Xn应用协议XnAP消息。
在一些实施例中，第二消息为以下至少一个：
检索终端设备上下文请求消息；
部分终端设备上下文确认消息；
Xn应用协议XnAP消息。
在一些实施例中，第一节点为核心网节点，第二节点为接入网设备。
在一些实施例中，核心网节点为以下至少一个：
接入和移动性管理功能AMF；
会话管理功能设备SMF；
用户面功能设备UPF。
在一些实施例中，第一消息为以下至少一个：
下一代应用协议NGAP消息；
包括在用户平面数据中的消息。
在一些实施例中，第一节点为集中单元用户面CU-UP，第二节点为集中单元控制面CU-CP。
在一些实施例中，第一消息为以下至少一个：
下行数据通知消息；
承载上下文修改需求消息；
E1应用协议E1AP消息。
在一些实施例中，第一节点为集中单元CU或CU-CP，第二节点为分布单元DU。
在一些实施例中，第一消息为以下至少一个：
寻呼消息；
终端设备上下文修改请求消息；
终端设备上下文建立请求消息；
F1应用协议F1AP消息。
在一些实施例中，第二消息为以下至少一个：
SDT发送通知消息；
初始UL RRC消息传输消息；
F1应用协议F1AP消息。
通信装置1为第二节点：
该通信装置1，包括：收发模块11和处理模块12。
收发模块11，被配置为接收第一节点发送的第一消息，其中，第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，第一信息用于指示第二节点在接收到终端设备的第一请求消息后，根据第一信息发送和/或接收SDT的信息，信息包括数据和/或信令，第一节点为无法确定处于非连接态的 终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
在一些实施例中，收发模块11，还被配置为接收终端设备发送的第一请求消息，其中，第一请求消息用于指示上行SDT的数据和/或信令。
在一些实施例中，收发模块11，还被配置为根据第一消息向终端设备发送寻呼；接收终端设备发送的第一请求消息，其中，第一请求消息为终端设备对于第二节点的寻呼的响应。
在一些实施例中，处理模块12，被配置为根据第一信息，为终端设备配置SDT资源。
在一些实施例中，第一信息，包括以下至少一个：
部分终端设备上下文信息；
上行传输网络层TNL信息；
MT-SDT方式；
MT-SDT类型；
终端设备的上行传输特性；
终端设备的下行传输特性。
在一些实施例中，收发模块11，还被配置为向第一节点发送第二消息，其中，第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，第二信息用于请求第一节点向第二节点发送SDT的信息。
在一些实施例中，第二信息，包括以下至少一个：
MT-SDT指示；
下行传输网络层TNL信息。
在一些实施例中，收发模块11，还被配置为接收第一节点发送的SDT的信息，其中，SDT的信息为第一节点根据第二消息发送的，SDT的信息包括下行SDT的数据和/或信令。
在一些实施例中，第一节点向第二节点发送第三信息，第三信息，包括以下至少一个：
下行SDT的数据；
下行SDT的信令；
下行SDT的数据和信令。
在一些实施例中，第三信息被包括在第一消息和/或第三消息中。
在一些实施例中，第三消息，还包括与终端设备相关的标识。
在一些实施例中，收发模块11，还被配置为向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，收发模块11，还被配置为向第一节点发送第一指示信息，其中，第一指示信息用于指示第二节点完成向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，收发模块11，还被配置为接收终端设备发送的响应消息，其中，响应消息用于指示终端设备接收到下行SDT的数据和/或信令。
在一些实施例中，收发模块11，还被配置为向第一节点发送第二指示信息，其中，第二指示信息用于指示第二节点成功向终端设备发送下行SDT的数据和/或信令。
在一些实施例中，第一指示信息和/或第二指示信息，包括以下至少一个：
终端设备标识信息；
成功发送至终端设备的指示；
未成功发送至终端设备的指示；
DL TNL信息。
在一些实施例中，处理模块12，还被配置为响应于未接收到终端设备发送的第一请求消息，释放SDT相关的第一信息。
在一些实施例中，第一节点为第一接入网设备，第二节点为第二接入网设备，第一接入网设备为最后一个服务于终端设备的接入网设备，第二接入网设备为当前服务终端设备的接入网设备。
在一些实施例中，第一消息为以下至少一个：
无线接入网RAN寻呼消息；
部分终端设备上下文传输消息；
Xn应用协议XnAP消息。
在一些实施例中，第二消息为以下至少一个：
检索终端设备上下文请求消息；
部分终端设备上下文确认消息；
Xn应用协议XnAP消息。
在一些实施例中，第一节点为核心网节点，第二节点为接入网设备。
在一些实施例中，核心网节点为以下至少一个：
接入和移动性管理功能AMF；
会话管理功能设备SMF；
用户面功能设备UPF。
在一些实施例中，第一消息为以下至少一个：
下一代应用协议NGAP消息；
包括在用户平面数据中的消息。
在一些实施例中，第一节点为集中单元用户面CU-UP，第二节点为集中单元控制面CU-CP。
在一些实施例中，第一消息为以下至少一个：
下行数据通知消息；
承载上下文修改需求消息；
E1应用协议E1AP消息。
在一些实施例中，第一节点为集中单元CU或CU-CP，第二节点为分布单元DU。
在一些实施例中，第一消息为以下至少一个：
寻呼消息；
终端设备上下文修改请求消息；
终端设备上下文建立请求消息；
F1应用协议F1AP消息。
在一些实施例中，第二消息为以下至少一个：
SDT发送通知消息；
初始UL RRC消息传输消息；
F1应用协议F1AP消息。
关于上述实施例中的通信装置1，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开上述实施例中提供的通信装置1，与上面一些实施例中提供的数据传输方法取得相同或相似的有益效果，此处不再赘述。
请参见图25，图25是本公开实施例提供的另一种通信装置1000的结构示意图。通信装置1000可以是第一节点，也可以是第二节点，也可以是支持第一节点实现上述方法的芯片、芯片系统、或处理器等，还可以是支持第二节点实现上述方法的芯片、芯片系统、或处理器等。该通信装置1000可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以包括一个或多个处理器1001。处理器1001可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，第一节点、第二节点、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1000中还可以包括一个或多个存储器1002，其上可以存有计算机程序1004，存储器1002执行所述计算机程序1004，以使得通信装置1000执行上述方法实施例中描述的方法。可选的，所述存储器1002中还可以存储有数据。通信装置1000和存储器1002可以单独设置，也可以集成在一起。
可选的，通信装置1000还可以包括收发器1005、天线1006。收发器1005可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1005可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1000中还可以包括一个或多个接口电路1007。接口电路1007用于接收代码指令并传输至处理器1001。处理器1001运行所述代码指令以使通信装置1000执行上述方法实施例中描述的方法。
通信装置1000为第一节点：处理器1001用于执行图5中的S51；图6中的S61；图7中的S71；图8中的S81；图9中的S91；图10中的S101；收发器1005用于执行图5中的S52；图6中的S62至S64；图7中的S72至S75；图8中的S82至S85；图9中的S92至S93；图10中的S102至S103。
通信装置1000为第二节点：收发器1005用于执行图11中的S111；图12中的S121至S123；图13中的S131至S132；图14中的S141至S142；图15中的S151；图16中的S161至S163；图17中的S171至S174；图18中的S181至S185；图19中的S191至S196；图20中的S201至S207；图21中的S211至S214；图22中的S221至S225；处理器1001用于执行图14中的S143；图15中的S152。
在一种实现方式中，处理器1001中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1001可以存有计算机程序1003，计算机程序1003在处理器1001上运行，可使得通信装置1000执行上述方法实施例中描述的方法。计算机程序1003可能固化在处理器1001中，该种情况下，处理器1001可能由硬件实现。
在一种实现方式中，通信装置1000可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是第一节点或第二节点，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图25的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，请参见图26，为本公开实施例中提供的一种芯片的结构图。
芯片1100包括处理器1101和接口1103。其中，处理器1101的数量可以是一个或多个，接口1103的数量可以是多个。
对于芯片用于实现本公开实施例中第一节点的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的数据传输方法。
对于芯片用于实现本公开实施例中第二节点的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的数据传输方法。
可选的，芯片1100还包括存储器1102，存储器1102用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种数据传输系统，该系统包括前述图24实施例中作为第一节点的通信装置和作为第二节点的通信装置，或者，该系统包括前述图25实施例中作为第一节点的通信装置和作为第二节点的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以 存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (54)

  1. 一种数据传输方法，其特征在于，所述方法由第一节点执行，包括：
    确定需要发送和/或接收的小数据包传输SDT的信息，其中，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点；
    向第二节点发送第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息。
  2. 如权利要求1所述的方法，其特征在于，所述第一信息，包括以下至少一个：
    部分终端设备上下文信息；
    上行传输网络层TNL信息；
    移动被叫MT-SDT方式；
    MT-SDT类型；
    所述终端设备的上行传输特性；
    所述终端设备的下行传输特性。
  3. 如权利要求2所述的方法，其特征在于，还包括：
    接收所述第二节点发送的第二消息，其中，所述第二消息为所述第二节点在接收到所述终端设备发送的所述第一请求消息后发送的，所述第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，所述第二信息用于请求所述第一节点向所述第二节点发送所述SDT的信息，所述第一请求消息为所述终端设备对于所述第二节点的寻呼的响应。
  4. 如权利要求3所述的方法，其特征在于，所述第二信息，包括以下至少一个：
    MT-SDT指示；
    下行传输网络层TNL信息。
  5. 如权利要求3或4所述的方法，其特征在于，还包括：
    根据所述第二消息，向所述第二节点发送所述SDT的信息，其中，所述SDT的信息包括下行SDT的数据和/或信令。
  6. 如权利要求1或2所述的方法，其特征在于，还包括：
    向所述第二节点发送第三信息，其中，所述第三信息，包括以下至少一个：
    下行SDT的数据；
    下行SDT的信令；
    下行SDT的数据和信令。
  7. 如权利要求6所述的方法，其特征在于，所述第三信息被包括在所述第一消息和/或第三消息中。
  8. 如权利要求7所述的方法，其特征在于，所述第三消息，还包括与终端设备相关的标识。
  9. 如权利要求5或6所述的方法，其特征在于，还包括：
    接收所述第二节点发送的第一指示信息，其中，所述第一指示信息用于指示所述第二节点完成向所述终端设备发送所述下行SDT的数据和/或信令。
  10. 如权利要求5或6所述的方法，其特征在于，还包括：
    接收所述第二节点发送的第二指示信息，其中，所述第二指示信息为所述第二节点在接收到所述终端设备发送的响应消息的情况下发送的，所述第二指示信息用于指示所述第二节点成功向所述终端设备发送所述下行SDT的数据和/或信令。
  11. 如权利要求9或10所述的方法，其特征在于，所述第一指示信息和/或所述第二指示信息，包括以下至少一个：
    终端设备标识信息；
    成功发送至所述终端设备的指示；
    未成功发送至所述终端设备的指示；
    下行TNL信息。
  12. 如权利要求1至11中任一项所述的方法，其特征在于，所述第一节点为第一接入网设备，所述第二节点为第二接入网设备，所述第一接入网设备为最后一个服务于所述终端设备的接入网设备，所述第二接入网设备为当前服务所述终端设备的接入网设备。
  13. 如权利要求12所述的方法，其特征在于，所述第一消息为以下至少一个：
    无线接入网RAN寻呼消息；
    部分终端设备上下文传输消息；
    Xn应用协议XnAP消息。
  14. 如权利要求12所述的方法，其特征在于，所述第二消息为以下至少一个：
    检索终端设备上下文请求消息；
    部分终端设备上下文确认消息；
    Xn应用协议XnAP消息。
  15. 如权利要求1至11中任一项所述的方法，其特征在于，所述第一节点为核心网节点，所述第二节点为接入网设备。
  16. 如权利要求15所述的方法，其特征在于，所述核心网节点为以下至少一个：
    接入和移动性管理功能AMF；
    会话管理功能设备SMF；
    用户面功能设备UPF。
  17. 如权利要求15或16所述的方法，其特征在于，所述第一消息为以下至少一个：
    下一代应用协议NGAP消息；
    包括在用户平面数据中的消息。
  18. 如权利要求1至11中任一项所述的方法，其特征在于，所述第一节点为集中单元用户面CU-UP，所述第二节点为集中单元控制面CU-CP。
  19. 如权利要求18所述的方法，其特征在于，所述第一消息为以下至少一个：
    下行数据通知消息；
    承载上下文修改需求消息；
    E1应用协议E1AP消息。
  20. 如权利要求1至11中任一项所述的方法，其特征在于，所述第一节点为集中单元CU或CU-CP，所述第二节点为分布单元DU。
  21. 如权利要求20所述的方法，其特征在于，所述第一消息为以下至少一个：
    寻呼消息；
    终端设备上下文修改请求消息；
    终端设备上下文建立请求消息；
    F1应用协议F1AP消息。
  22. 如权利要求20所述的方法，其特征在于，所述第二消息为以下至少一个：
    SDT发送通知消息；
    初始上行RRC消息传输消息；
    F1应用协议F1AP消息。
  23. 一种数据传输方法，其特征在于，所述方法由第二节点执行，包括：
    接收第一节点发送的第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
  24. 如权利要求23所述的方法，其特征在于，还包括：
    接收所述终端设备发送的所述第一请求消息，其中，所述第一请求消息用于指示上行SDT的数据和/或信令。
  25. 如权利要求23所述的方法，其特征在于，还包括：
    根据所述第一消息向所述终端设备发送寻呼；
    接收所述终端设备发送的所述第一请求消息，其中，所述第一请求消息为所述终端设备对于所述第二节点的寻呼的响应。
  26. 如权利要求25所述的方法，其特征在于，还包括：
    根据所述第一信息，为所述终端设备配置SDT资源。
  27. 如权利要求25或26所述的方法，其特征在于，所述第一信息，包括以下至少一个：
    部分终端设备上下文信息；
    上行传输网络层TNL信息；
    MT-SDT方式；
    MT-SDT类型；
    所述终端设备的上行传输特性；
    所述终端设备的下行传输特性。
  28. 如权利要求27所述的方法，其特征在于，还包括：
    向所述第一节点发送第二消息，其中，所述第二消息包括与处于非连接态的终端设备的SDT相关的第二信息，所述第二信息用于请求所述第一节点向所述第二节点发送所述SDT的信息。
  29. 如权利要求28所述的方法，其特征在于，所述第二信息，包括以下至少一个：
    MT-SDT指示；
    下行传输网络层TNL信息。
  30. 如权利要求28或29所述的方法，其特征在于，还包括：
    接收所述第一节点发送的所述SDT的信息，其中，所述SDT的信息为所述第一节点根据所述第二消息发送的，所述SDT的信息包括下行SDT的数据和/或信令。
  31. 如权利要求27所述的方法，其特征在于，还包括：
    接收所述第一节点发送的第三信息，其中，所述第三信息，包括以下至少一个：
    下行SDT的数据；
    下行SDT的信令
    下行SDT的数据和信令。
  32. 如权利要求31所述的方法，其特征在于，所述第三信息被包括在所述第一消息和/或第三消息中。
  33. 如权利要求32所述的方法，其特征在于，所述第三消息，还包括与终端设备相关的标识。
  34. 如权利要求30或31所述的方法，其特征在于，还包括：
    向所述终端设备发送所述下行SDT的数据和/或信令。
  35. 如权利要求34所述的方法，其特征在于，还包括：
    向所述第一节点发送第一指示信息，其中，所述第一指示信息用于指示所述第二节点完成向所述终端设备发送所述下行SDT的数据和/或信令。
  36. 如权利要求34所述的方法，其特征在于，还包括：
    接收所述终端设备发送的响应消息，其中，所述响应消息用于指示所述终端设备接收到所述下行SDT的数据和/或信令。
  37. 如权利要求36所述的方法，其特征在于，还包括：
    向所述第一节点发送第二指示信息，其中，所述第二指示信息用于指示所述第二节点成功向所述终端设备发送所述下行SDT的数据和/或信令。
  38. 如权利要求36或37所述的方法，其特征在于，所述第一指示信息和/或所述第二指示信息，包括以下至少一个：
    终端设备标识信息；
    成功发送至所述终端设备的指示；
    未成功发送至所述终端设备的指示；
    下行TNL信息。
  39. 如权利要求25所述的方法，其特征在于，还包括：
    响应于未接收到所述终端设备发送的第一请求消息，释放所述SDT相关的所述第一信息。
  40. 如权利要求23至39中任一项所述的方法，其特征在于，所述第一节点为第一接入网设备，所述第二节点为第二接入网设备，所述第一接入网设备为最后一个服务于所述终端设备的接入网设备，所述第二接入网设备为当前服务所述终端设备的接入网设备。
  41. 如权利要求40所述的方法，其特征在于，所述第一消息为以下至少一个：
    无线接入网RAN寻呼消息；
    部分终端设备上下文传输消息；
    Xn应用协议XnAP消息。
  42. 如权利要求40所述的方法，其特征在于，所述第二消息为以下至少一个：
    检索终端设备上下文请求消息；
    部分终端设备上下文确认消息；
    Xn应用协议XnAP消息。
  43. 如权利要求23至39中任一项所述的方法，其特征在于，所述第一节点为核心网节点，所述第二节点为接入网设备。
  44. 如权利要求43所述的方法，其特征在于，所述核心网节点为以下至少一个：
    接入和移动性管理功能AMF；
    会话管理功能设备SMF；
    用户面功能设备UPF。
  45. 如权利要求43或44所述的方法，其特征在于，所述第一消息为以下至少一个：
    下一代应用协议NGAP消息；
    包括在用户平面数据中的消息。
  46. 如权利要求23至39中任一项所述的方法，其特征在于，所述第一节点为集中单元用户面CU-UP，所述第二节点为集中单元控制面CU-CP。
  47. 如权利要求46所述的方法，其特征在于，所述第一消息为以下至少一个：
    下行数据通知消息；
    承载上下文修改需求消息；
    E1应用协议E1AP消息。
  48. 如权利要求23至39中任一项所述的方法，其特征在于，所述第一节点为集中单元CU或CU-CP，所述第二节点为分布单元DU。
  49. 如权利要求48所述的方法，其特征在于，所述第一消息为以下至少一个：
    寻呼消息；
    终端设备上下文修改请求消息；
    终端设备上下文建立请求消息；
    F1应用协议F1AP消息。
  50. 如权利要求48所述的方法，其特征在于，所述第二消息为以下至少一个：
    SDT发送通知消息；
    初始上行RRC消息传输消息；
    F1应用协议F1AP消息。
  51. 一种通信装置，其特征在于，所述装置包括：
    处理模块，被配置为确定需要发送和/或接收的小数据包传输SDT的信息，其中，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点；
    收发模块，被配置为向第二节点发送第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息。
  52. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为接收第一节点发送的第一消息，其中，所述第一消息包括与处于非连接态的终端设备的SDT相关的第一信息，所述第一信息用于指示第二节点在接收到所述终端设备的第一请求消息后，根据所述第一信息发送和/或接收所述SDT的信息，所述第一节点为无法确定处于非连接态的终端设备是否在其覆盖范围内的节点，或者为无法直接与处于非连接态的终端设备进行上下行信息的收发的节点。
  53. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至22中任一项所述的方法，或所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求23至50中任一项所述的方法。
  54. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至22中任一项所述的方法被实现，或当所述指令被执行时，使如权利要求23至50中任一项所述的方法被实现。
PCT/CN2022/107716 2022-07-25 2022-07-25 数据传输方法和装置 WO2024020753A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280002510.5A CN117796136A (zh) 2022-07-25 2022-07-25 数据传输方法和装置
PCT/CN2022/107716 WO2024020753A1 (zh) 2022-07-25 2022-07-25 数据传输方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/107716 WO2024020753A1 (zh) 2022-07-25 2022-07-25 数据传输方法和装置

Publications (1)

Publication Number Publication Date
WO2024020753A1 true WO2024020753A1 (zh) 2024-02-01

Family

ID=89704876

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/107716 WO2024020753A1 (zh) 2022-07-25 2022-07-25 数据传输方法和装置

Country Status (2)

Country Link
CN (1) CN117796136A (zh)
WO (1) WO2024020753A1 (zh)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757556A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种数据传输方法及装置
WO2021157895A1 (en) * 2020-02-07 2021-08-12 Lg Electronics Inc. Method and apparatus for small data transmission in rrc inactive state in mr-dc
US20220061121A1 (en) * 2019-03-19 2022-02-24 Apple Inc. Signaling for inactive small data transmission without path switching
WO2022133763A1 (en) * 2020-12-23 2022-06-30 Zte Corporation A method for small data transmission
CN114727414A (zh) * 2021-01-04 2022-07-08 华为技术有限公司 数据传输方法及相关装置
CN114745788A (zh) * 2021-01-08 2022-07-12 北京三星通信技术研究有限公司 信息传输方法、装置、电子设备及存储介质
CN114765817A (zh) * 2021-01-14 2022-07-19 大唐移动通信设备有限公司 数据传输控制方法和装置
WO2022151279A1 (en) * 2021-01-14 2022-07-21 Zte Corporation Method, device and computer program product for wireless communication

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220061121A1 (en) * 2019-03-19 2022-02-24 Apple Inc. Signaling for inactive small data transmission without path switching
CN111757556A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种数据传输方法及装置
WO2021157895A1 (en) * 2020-02-07 2021-08-12 Lg Electronics Inc. Method and apparatus for small data transmission in rrc inactive state in mr-dc
WO2022133763A1 (en) * 2020-12-23 2022-06-30 Zte Corporation A method for small data transmission
CN114727414A (zh) * 2021-01-04 2022-07-08 华为技术有限公司 数据传输方法及相关装置
CN114745788A (zh) * 2021-01-08 2022-07-12 北京三星通信技术研究有限公司 信息传输方法、装置、电子设备及存储介质
CN114765817A (zh) * 2021-01-14 2022-07-19 大唐移动通信设备有限公司 数据传输控制方法和装置
WO2022151279A1 (en) * 2021-01-14 2022-07-21 Zte Corporation Method, device and computer program product for wireless communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Introduction of SDT", 3GPP DRAFT; R2-2204234, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20220221 - 20220303, 12 March 2022 (2022-03-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052131437 *

Also Published As

Publication number Publication date
CN117796136A (zh) 2024-03-29

Similar Documents

Publication Publication Date Title
WO2022233063A1 (zh) 接入失败处理方法、装置、终端设备和存储介质
WO2023028962A1 (zh) 一种信息传输方法和装置
US11202333B2 (en) Layer 2 processing method, central unit and distributed unit
WO2022233064A1 (zh) 一种释放远端终端设备的方法及其装置
WO2019242756A1 (zh) 通信方法及装置
EP4017042A1 (en) Communication method and communication device
JP7467597B2 (ja) 通信方法、ｓｌｒｂ確立方法、および通信装置
WO2019192458A1 (zh) 通信方法和装置
US11259362B2 (en) Method for repeatedly transmitting data and device
WO2024020753A1 (zh) 数据传输方法和装置
WO2022120519A1 (zh) 部分带宽处理方法及装置
WO2024060143A1 (zh) 一种上报方法/装置/设备及存储介质
WO2023130321A1 (zh) 一种数据压缩方法和装置
WO2023102689A1 (zh) 一种基于四步随机接入的第三条消息重复的覆盖增强方法
WO2023245451A1 (zh) 随机接入方法和装置
WO2024000208A1 (zh) 一种定时提前报告tar的触发方法、装置、设备及存储介质
WO2023230971A1 (zh) 一种多prach传输方法及其装置
WO2023245453A1 (zh) 一种消息传输方法/装置/设备及存储介质
WO2023206575A1 (zh) 一种跨基站小区的配置方法及其装置
WO2023236061A1 (zh) 一种失败恢复方法及其装置
WO2022222012A1 (zh) 寻呼处理方法及其装置
WO2024031272A1 (zh) 一种上报方法、装置、设备及存储介质
WO2024000207A1 (zh) 一种定时提前报告tar的触发方法、装置、设备及存储介质
WO2024000205A1 (zh) 传输控制方法及其装置
WO2023201529A1 (zh) 资源配置方法及装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280002510.5

Country of ref document: CN

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

Ref document number: 22952220

Country of ref document: EP

Kind code of ref document: A1