WO2021253417A1 - 数据传输方法和网络设备 - Google Patents

数据传输方法和网络设备 Download PDF

Info

Publication number
WO2021253417A1
WO2021253417A1 PCT/CN2020/097152 CN2020097152W WO2021253417A1 WO 2021253417 A1 WO2021253417 A1 WO 2021253417A1 CN 2020097152 W CN2020097152 W CN 2020097152W WO 2021253417 A1 WO2021253417 A1 WO 2021253417A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
base station
terminal device
network device
uplink data
Prior art date
Application number
PCT/CN2020/097152
Other languages
English (en)
French (fr)
Inventor
石聪
王淑坤
李海涛
林雪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080101021.6A priority Critical patent/CN115669197A/zh
Priority to EP20940965.5A priority patent/EP4156846A4/en
Priority to PCT/CN2020/097152 priority patent/WO2021253417A1/zh
Publication of WO2021253417A1 publication Critical patent/WO2021253417A1/zh
Priority to US18/083,338 priority patent/US20230123866A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a data transmission method and network equipment.
  • the New Radio (NR) system supports small data transmission. After the target base station receives the uplink data sent by the terminal device, it needs to migrate the context of the terminal device from the anchor base station to the target base station before the target base station can send the uplink data to The core network increases the signaling overhead caused by migrating the context of terminal equipment between base stations.
  • the embodiments of the present application provide a data transmission method and network device, which can realize small data transmission without relocating the context of the terminal device.
  • a data transmission method includes:
  • the target base station sends first information to the anchor base station, where the first information includes uplink data sent by the inactive state terminal device, where the first information is transmitted in a container-bearing manner, or the first information is transmitted in a tunnel-bearing manner.
  • a data transmission method which includes:
  • the anchor base station receives the first information sent by the target base station, the first information includes uplink data sent by the inactive state terminal device, wherein the first information is transmitted through a container carrying method, or the first information is transmitted through a tunnel carrying method .
  • a network device which is used to execute the method executed by the target base station in the above-mentioned first aspect.
  • the network device includes a functional module for executing the method executed by the target base station in the first aspect described above.
  • a network device for executing the method executed by the anchor base station in the second aspect.
  • the network device includes a functional module for executing the method executed by the anchor base station in the second aspect described above.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method executed by the target base station in the first aspect described above.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method executed by the anchor base station in the second aspect described above.
  • a device for implementing the method in any one of the first aspect to the second aspect.
  • the device includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes the method in any one of the first aspect to the second aspect described above.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute the method in any one of the above-mentioned first aspect to the second aspect.
  • a computer program product including computer program instructions that cause a computer to execute the method in any one of the first aspect to the second aspect.
  • a computer program which, when run on a computer, causes the computer to execute the method in any one of the first aspect to the second aspect.
  • the target base station can forward the uplink data sent by the inactive terminal device to the anchor base station, so that the inactive terminal device can transmit the uplink data to the core network device . That is, the technical solution of the present application can realize small data transmission without migrating the context of the terminal device.
  • Fig. 1 is a schematic diagram of a communication system architecture provided by the present application.
  • Fig. 2 is a schematic diagram of a state transition of a terminal device provided by the present application.
  • Fig. 3 is a schematic diagram of a non-activated terminal device RNA provided by the present application.
  • Fig. 4 is a schematic flow chart of an RNAU with context migration provided by the present application.
  • Fig. 5 is a schematic flowchart of a context-free migration RNAU provided by the present application.
  • Fig. 6 is a schematic flowchart of a small data transmission provided by the present application.
  • Fig. 7 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • Fig. 8 is a schematic flowchart of transmitting uplink data through a container according to an embodiment of the present application.
  • Fig. 9 is a schematic flowchart of transmitting uplink data through a tunnel according to an embodiment of the present application.
  • Fig. 10 is a schematic block diagram of a network device according to an embodiment of the present application.
  • Fig. 11 is a schematic block diagram of another network device provided according to an embodiment of the present application.
  • Fig. 12 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • Fig. 13 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.
  • Fig. 14 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • evolution system of NR system LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum, NR-U) system, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, Universal Mobile Telecommunication System (UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, WiFi), the fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC machine type communication
  • V2V vehicle to vehicle
  • V2X vehicle to everything
  • the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and can also be applied to a standalone (SA) deployment.
  • CA Carrier Aggregation
  • DC Dual Connectivity
  • SA standalone
  • the communication system in the embodiment of this application can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or the communication system in the embodiment of this application can also be applied to licensed spectrum, where: Licensed spectrum can also be considered non-shared spectrum.
  • the embodiments of this application describe various embodiments in combination with network equipment and terminal equipment.
  • the terminal equipment may also be referred to as User Equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station, and remote station. Station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE User Equipment
  • the terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, and personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or in the future Terminal equipment in the evolved Public Land Mobile Network (PLMN) network.
  • STAION, ST station
  • WLAN Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • land including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • First class can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal.
  • Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, and wireless terminal equipment in smart grid , Wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which need to cooperate with other devices such as smart phones.
  • Use such as all kinds of smart bracelets and smart jewelry for physical sign monitoring.
  • the network device may be a device used to communicate with mobile devices, the network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA It can also be a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB, or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, wearable device, and NR network Network equipment or base station (gNB) or network equipment in the future evolution of the PLMN network or network equipment in the NTN network.
  • AP access point
  • BTS Base Transceiver Station
  • NodeB base station
  • Evolutional Node B, eNB, or eNodeB evolved base station
  • gNB NR network Network equipment or base station
  • the network device may have mobile characteristics, for example, the network device may be a mobile device.
  • the network equipment may be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, or a high elliptical orbit (High Elliptical Orbit, HEO). ) Satellite etc.
  • the network device may also be a base station installed in a location such as land or water.
  • the network equipment may provide services for the cell, and the terminal equipment communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network equipment ( For example, the cell corresponding to the base station.
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: Metro cell, Micro cell, and Pico cell ( Pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or called a communication terminal or a terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area.
  • Figure 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 with communication functions, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in the embodiment of the present application.
  • the "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B relation.
  • correlate can mean that there is a direct correspondence or an indirect correspondence between the two, or that there is an association relationship between the two, or indicating and being instructed, configuring and being Configuration and other relationships.
  • NR can also be deployed independently.
  • RRC Radio Resource Control
  • RRC_INACTIVE active
  • RRC_CONNECTED connected
  • RRC_IDLE mobility is cell selection and reselection based on terminal equipment, paging is initiated by the core network (Core Network, CN), and the paging area is configured by the CN.
  • Core Network Core Network
  • AS Access Stratum
  • RRC_CONNECTED state there is an RRC connection, and the base station and the terminal device have the terminal device AS context.
  • the network equipment knows that the location of the terminal equipment is of a specific cell level. Mobility is the mobility controlled by network equipment. Unicast data can be transmitted between the terminal equipment and the base station.
  • RRC_INACTIVE Mobility is the cell selection reselection based on terminal equipment, there is a connection between CN-NR, the AS context of the terminal equipment is stored on a certain base station, and paging is triggered by the Radio Access Network (RAN), based on The paging area of the RAN is managed by the RAN, and the network equipment knows that the location of the terminal equipment is based on the paging area level of the RAN.
  • RAN Radio Access Network
  • the inactive state may also be referred to as the deactivated state, which is not limited in the present application.
  • the network device can control the state transition of the terminal device.
  • the terminal device in the RRC_CONNECTED state can enter the RRC_IDLE state by releasing the RRC connection;
  • the terminal device in the RRC_IDLE state can enter the RRC_CONNECTED state by establishing an RRC connection;
  • a UE in the RRC_CONNECTED state can enter the RRC_INACTIVE state by suspending and releasing the RRC connection (Release with Suspend);
  • a UE in the RRC_INACTIVE state can enter the RRC_CONNECTED state by resuming the RRC connection, or it can enter the RRC_IDLE state by releasing the RRC connection.
  • the terminal device is in the RRC_INACTIVE state, and the terminal device autonomously returns to the idle state in the following situations:
  • start timer T319 When initiating an RRC recovery request, start timer T319, if the timer expires;
  • contention-based random access message 4 (Message4, MSG4) integrity protection verification fails;
  • Radio Access Technology RAT
  • the terminal device and at least one gNB save the AS context
  • the terminal equipment is reachable to the RAN side, and the relevant parameters are configured by the RAN;
  • RNA RAN Notification area
  • the UE moves in the RNA according to the cell selection reselection mode.
  • RNA can be specifically shown in Figure 3.
  • the terminal device does not need to notify the network side when it moves between base station 1 to base station 5, but when the terminal device moves to base station 6 Or the base station 7 needs to notify the network side.
  • the network device When the terminal device is in the RRC_INACTIVE state, the network device will configure the RRC_INACTIVE configuration parameters for the terminal device through RRC Release dedicated signaling, for example, configure RNA, which is used to control the area where the terminal device performs cell selection and reselection in the inactive state , Is also the initial paging range area of the RAN.
  • RRC Release dedicated signaling for example, configure RNA, which is used to control the area where the terminal device performs cell selection and reselection in the inactive state , Is also the initial paging range area of the RAN.
  • the terminal device When the terminal device moves in the RNA area, it does not need to notify the network side, and follows the mobility behavior in the idle state, that is, the principle of cell selection and reselection.
  • the terminal device When the terminal device moves out of the paging area configured by the RAN, the terminal device will be triggered to restore the RRC connection and reacquire the paging area configured by the RAN.
  • the terminal device When the terminal device has downlink data arriving, the gNB that maintains the connection between the RAN and the CN for the terminal device will trigger all cells in the RAN paging area to send paging messages to the terminal device, so that the terminal device in the INACTIVE state can restore the RRC connection. Perform data reception.
  • the terminal equipment in the INACTIVE state is configured with a RAN paging area. In this area, in order to ensure the reachability of the terminal equipment, the terminal equipment needs to perform periodic location update according to the network configuration cycle.
  • the scenarios that trigger the terminal device to perform the RNA update include the RAN Notification Area Update (RNAU) timer expires or the UE moves to an area outside the RNA.
  • RNAU RAN Notification Area Update
  • the anchor base station determines whether the context of the terminal device needs to be transferred to the target base station. Therefore, in general, the target base station will send the cause value (cause) carried in the terminal device initiated RRC connection recovery request message to the anchor base station during the terminal device context request process, and the anchor base station decides whether to transfer the context of the terminal device to the target base station. . For example, periodic RAN location update generally does not require context transfer.
  • RNAU with context migration is implemented in the following procedures described in S11 to S19.
  • the terminal equipment (UE) sends an RRC connection recovery request (Resume Request) to the target base station (gNB), and the RRC connection recovery request is used for RNA update;
  • the target base station sends a UE context request (RETRIEVE UE CONTEXT REQUEST) to the anchor base station (also called the last serving base station (gNB));
  • the anchor base station sends the UE context response (RETRIEVE UE CONTEXT RESPONSE) to the target base station;
  • the target base station sends a data forwarding address indication (DATA FORWARDING ADDRESS INDICATION) to the anchor base station (optional);
  • the target base station sends a path switching request to an Access and Mobility Management Function (AMF) entity;
  • AMF Access and Mobility Management Function
  • the AMF entity sends a path switching response to the target base station
  • the target base station sends an RRC release message to the terminal device
  • the target base station sends a UE context release message to the anchor base station.
  • RNAU without context migration is specifically implemented by the following procedures described in S21 to S24.
  • the terminal equipment (UE) sends an RRC connection resume request (Resume Request) to the target base station (gNB), and the RRC connection resume request is used for RNA update;
  • the target base station sends a UE context request (RETRIEVE UE CONTEXT REQUEST) to the anchor base station (also called the last serving base station (gNB));
  • the anchor base station sends the UE context extraction failure (RETRIEVE UE CONTEXT FAILURE) to the target base station;
  • the target base station sends an RRC release message to the terminal device.
  • small data transmission (early data transmission, EDT) is introduced.
  • the terminal device may always remain in the idle state or suspended state or inactive state to complete the uplink. And/or the transmission of downlink small data packets.
  • the user plane data transmission scheme can be specifically implemented in the following procedures S31 to S38.
  • the UE sends an RRC connection resume request (Resume Request) to the eNB, where the RRC connection resume request includes uplink data (ie, small data transmission) sent by the UE;
  • the eNB sends a UE context recovery request (UE CONTEXT RESUME REQUEST) to a mobility management entity (Mobility Management Entity, MME);
  • UE CONTEXT RESUME REQUEST UE context recovery request
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the MME sends a UE context recovery response (UE CONTEXT RESUME RESPONSE) to the eNB;
  • the eNB sends the uplink data sent by the UE (ie, small data transmission) to the SGW;
  • the SGW receives downlink data sent by the eNB (optional);
  • the eNB sends an RRC connection release message to the UE.
  • the RRC connection release message includes downlink data.
  • MBB Mobile Broadband
  • the context of the UE needs to be migrated first, that is, the context of the UE is migrated from the anchor base station to the target base station before the target base station can send the UE data To the core network.
  • this application introduces a method for transmitting data between base stations. Specifically, this application proposes a data transmission scheme. Without extracting the context of the terminal device, the target base station can forward the uplink data sent by the inactive terminal device to the anchor base station, so that the inactive terminal device The uplink data can be transmitted to the core network equipment. That is, the technical solution of the present application can realize small data transmission without migrating the context of the terminal device.
  • FIG. 7 is a schematic flowchart of a data transmission method 200 according to an embodiment of the present application. As shown in FIG. 7, the method 200 may include at least part of the following content:
  • the target base station sends first information to the anchor base station, where the first information includes uplink data sent by the terminal device in the inactive state, where the first information is transmitted in a container-bearing manner, or the first information is transmitted in a tunnel-bearing manner transmission;
  • the anchor base station receives the first information sent by the target base station.
  • the target base station may be the base station where the terminal device resides, or the target base station may be the base station that the terminal device is about to access.
  • the anchor base station may be a base station that stores the context information of the terminal device.
  • the uplink data is small data transmission (EDT).
  • EDT small data transmission
  • the target base station receives RRC recovery request information sent by the terminal device, where the RRC recovery request information and the uplink data are multiplexed into one transport block.
  • the terminal device in the inactive state sends RRC recovery request information to the target base station, and the RRC recovery request information is multiplexed with the uplink data into a transport block.
  • the preset condition may be configured by a network device, and the preset condition may also be agreed upon by a protocol.
  • the preset condition may be a data threshold, a logical channel priority, and so on.
  • the uplink data includes at least one of the following:
  • user plane data is data in a data radio bearer (DRB).
  • DRB data radio bearer
  • control plane data is data in signaling radio bearers (SRB).
  • SRB signaling radio bearers
  • Example 1 The first information is transmitted in a container bearing mode.
  • the first information is not visible to the anchor base station, or the first information is transparently transmitted to the anchor base station, or the anchor base station cannot interpret the content in the first information.
  • the anchor base station may forward the first information to the core network device. Since the first information is not visible to the anchor base station, the anchor base station cannot interpret the content in the first information.
  • the first information is used to request to extract the context information of the terminal device from the anchor base station (retrieve UE context request).
  • the anchor base station sends second information to the target base station, and the second information is used to indicate that the context information of the terminal device has failed to be retrieved (retrieve UE context failure), or the second information Including the context information of the terminal device.
  • the second information in a case where the second information is used to indicate that the context information of the terminal device fails to be extracted, the second information includes RRC release information, and the RRC release information is transmitted in a container-bearing manner. Further, the target base station forwards the RRC release information to the terminal device.
  • the second information includes first indication information, and the first indication information is used to indicate that the uplink data has been uploaded to the core network device.
  • Example 2 The first information is transmitted through a tunnel (Tunnel) bearer mode.
  • the first information is visible to the anchor base station, or the anchor base station can interpret the content in the first information.
  • the anchor base station may forward the uplink data to the core network device.
  • the target base station triggers the establishment of the tunnel. That is, in Example 2, the target base station needs to establish the tunnel in advance.
  • triggering the establishment of the tunnel by the target base station may specifically include:
  • the target base station sends third information to the anchor base station, where the third information includes information used to establish the tunnel and information used to indicate that the uplink data is received;
  • the anchor base station sends fourth information to the target base station, where the fourth information includes information fed back by the anchor base station for establishing the tunnel.
  • the information used to establish the tunnel may be a GPRS Tunneling Protocol (GPRS Tunneling Protocol, GTP) Tunnel.
  • GTP GPRS Tunneling Protocol
  • the third information is used to request to extract the context information of the terminal device from the anchor base station.
  • the target base station receives fifth information sent by the anchor base station, where the fifth information is used to indicate that the context information of the terminal device fails to be extracted, or the fifth information includes the terminal device's Contextual information.
  • the fifth information when the fifth information is used to indicate that the context information of the terminal device fails to be extracted, the fifth information includes RRC release information, and the RRC release information is transmitted in a container-bearing manner. Further, the target base station forwards the RRC release information to the terminal device.
  • the fifth information includes second indication information, and the second indication information is used to indicate that the uplink data has been uploaded to the core network device.
  • the core network device may be, for example, a User Plane Function (UPF) entity.
  • UPF User Plane Function
  • the target base station without extracting the context of the terminal device, the target base station can forward the uplink data sent by the inactive terminal device to the anchor base station, so that the inactive terminal device can transmit uplink data.
  • the technical solution of the present application can realize small data transmission without migrating the context of the terminal device.
  • the uplink data sent by the terminal device in the inactive state is transmitted in a container-bearing manner.
  • the inactive terminal device may specifically implement small data transmission in the following procedures described in S41 to S46.
  • the terminal device sends an RRC connection recovery request to the target base station, where the RRC connection recovery request includes uplink data (ie, small data transmission (EDT)) sent by the terminal device; optionally, the RRC connection recovery request includes Inactive Radio Network Temporary Identity (I-RNTI) and the reason for restoration;
  • RRC connection recovery request includes uplink data (ie, small data transmission (EDT)) sent by the terminal device; optionally, the RRC connection recovery request includes Inactive Radio Network Temporary Identity (I-RNTI) and the reason for restoration;
  • I-RNTI Inactive Radio Network Temporary Identity
  • the target base station sends first information to the anchor base station, where the first information is used to extract the context information of the terminal device (Retrieve UE Context Request), the first information includes uplink data sent by the terminal device, and the uplink data passes through the container ( container) bearer mode transmission;
  • the anchor base station forwards the uplink data to the UPF entity
  • the UPF entity sends downlink data to the anchor base station (optional);
  • the anchor base station sends second information to the target base station, where the second information is used to indicate the failure to extract the context information of the terminal device (Retrieve UE Context Failure); optionally, the UPF entity sends downlink data to the anchor base station
  • the second information includes the downlink data, and the downlink data is transmitted in a container-bearing manner; optionally, the second information includes first indication information, and the first indication information is used to indicate that the uplink data has been Upload to core network equipment (UPF entity);
  • the target base station sends an RRC connection release message to the terminal device; optionally, when the UPF entity sends downlink data to the anchor base station, the RRC connection release message includes the downlink data; optionally, the RRC connection release message Including I-RNTI, release reason, and network color code (NCC).
  • RRC connection release message Including I-RNTI, release reason, and network color code (NCC).
  • the uplink data sent by the terminal device in the inactive state is transmitted in a tunnel bearer manner.
  • the inactive terminal device may specifically implement small data transmission in the following procedures described in S51 to S58.
  • the terminal device (in the inactive state) sends an RRC connection recovery request to the target base station, where the RRC connection recovery request includes uplink data (ie, small data transmission (EDT)) sent by the terminal device; optionally, the RRC connection recovery request includes I-RNTI, reasons for recovery;
  • the RRC connection recovery request includes uplink data (ie, small data transmission (EDT)) sent by the terminal device; optionally, the RRC connection recovery request includes I-RNTI, reasons for recovery;
  • the target base station sends third information to the anchor base station.
  • the third information is used to extract the context information (Retrieve UE Context Request) of the terminal device.
  • the third information includes information for establishing a tunnel and for indicating that the Uplink data information;
  • the anchor base station sends fourth information to the target base station, where the fourth information includes information fed back by the anchor base station for establishing a tunnel;
  • the target base station sends first information to the anchor base station, where the first information includes uplink data sent by the inactive state terminal device, where the first information is transmitted through a tunnel bearer mode;
  • the anchor base station forwards the uplink data to the UPF entity
  • the UPF entity sends downlink data to the anchor base station (optional);
  • the anchor base station sends fifth information to the target base station, where the fifth information is used to indicate that the context information of the terminal device has failed to be extracted (Retrieve UE Context Failure); optionally, the UPF entity sends downlink data to the anchor base station
  • the fifth information includes the downlink data, and the downlink data is transmitted in a container-bearing manner; optionally, the fifth information includes second indication information, and the second indication information is used to indicate that the uplink data has been Upload to core network equipment (UPF entity);
  • UPF entity core network equipment
  • the target base station sends an RRC connection release message to the terminal device; optionally, when the UPF entity sends downlink data to the anchor base station, the RRC connection release message includes the downlink data; optionally, the RRC connection release message Including I-RNTI, release reason, NCC.
  • Fig. 10 shows a schematic block diagram of a network device 300 according to an embodiment of the present application.
  • the network device 300 is a target base station, and the network device 300 includes:
  • the communication unit 310 is configured to send first information to the anchor base station, where the first information includes uplink data sent by a terminal device in an inactive state, where the first information is transmitted in a container-bearing manner, or the first information is transmitted through a tunnel Bearer transmission.
  • the first information is used to request to extract the context information of the terminal device from the anchor base station.
  • the communication unit 310 is further configured to receive second information sent by the anchor base station, the second information is used to indicate that the context information of the terminal device fails to be extracted, or the second information includes the context of the terminal device information.
  • the second information includes radio resource control RRC release information, and the RRC release information is transmitted in a container-bearing manner;
  • the communication unit 310 is further configured to forward the RRC release information to the terminal device.
  • the second information includes first indication information, and the first indication information is used to indicate that the uplink data has been uploaded to the core network device.
  • the communication unit 310 is further configured to trigger the establishment of the tunnel.
  • the communication unit 310 is specifically configured to:
  • the third information is used to request to extract the context information of the terminal device from the anchor base station.
  • the communication unit 310 is further configured to receive fifth information sent by the anchor base station, where the fifth information is used to indicate failure to extract the context information of the terminal device, or the fifth information includes the context of the terminal device information.
  • the fifth information includes RRC release information, and the RRC release information is transmitted in a container-bearing manner;
  • the communication unit 310 is further configured to forward the RRC release information to the terminal device.
  • the fifth information includes second indication information, and the second indication information is used to indicate that the uplink data has been uploaded to the core network device.
  • the uplink data includes at least one of the following:
  • the uplink data is small data transmission EDT.
  • the communication unit 310 is further configured to receive RRC recovery request information sent by the terminal device, where the RRC recovery request information and the uplink data are multiplexed into a transmission block.
  • the aforementioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the network device 300 may correspond to the target base station in the method embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the network device 300 are to implement the method shown in FIG. 7 respectively.
  • the corresponding process of the target base station in 200 will not be repeated here.
  • FIG. 11 shows a schematic block diagram of a network device 400 according to an embodiment of the present application.
  • the network device 400 is an anchor base station, and the network device 400 includes:
  • the communication unit 410 is configured to receive first information sent by a target base station, where the first information includes uplink data sent by a terminal device in an inactive state, where the first information is transmitted in a container-bearing manner, or the first information is transmitted through a tunnel Bearer transmission.
  • the communication unit 410 is further configured to forward the first information to the core network device.
  • the first information is used to request to extract the context information of the terminal device from the anchor base station.
  • the communication unit 410 is further configured to send second information to the target base station, where the second information is used to indicate that the context information of the terminal device fails to be extracted, or the second information includes the context information of the terminal device.
  • the second information includes radio resource control RRC release information, and the RRC release information is transmitted in a container-bearing manner.
  • the second information includes first indication information, and the first indication information is used to indicate that the uplink data has been uploaded to the core network device.
  • the communication unit 410 is further configured to forward the uplink data to the core network device.
  • the communication unit 410 is further configured to receive third information sent by the target base station, where the third information includes information used to establish the tunnel and information used to indicate that the uplink data is received;
  • the communication unit 410 is further configured to send fourth information to the target base station, where the fourth information includes information fed back by the anchor base station for establishing the tunnel.
  • the third information is used to request to extract the context information of the terminal device from the anchor base station.
  • the communication unit 410 is further configured to send fifth information to the target base station, where the fifth information is used to indicate failure to extract the context information of the terminal device, or the fifth information includes the context information of the terminal device.
  • the fifth information includes RRC release information, and the RRC release information is transmitted in a container-bearing manner.
  • the fifth information includes second indication information, and the second indication information is used to indicate that the uplink data has been uploaded to the core network device.
  • the uplink data includes at least one of the following:
  • the uplink data is small data transmission EDT.
  • the aforementioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the network device 400 may correspond to the anchor base station in the method embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the network device 400 are respectively intended to realize the The corresponding process of the anchor base station in the method 200 is not repeated here for the sake of brevity.
  • FIG. 12 is a schematic structural diagram of a communication device 500 provided by an embodiment of the present application.
  • the communication device 500 shown in FIG. 12 includes a processor 510, and the processor 510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the communication device 500 may further include a memory 520.
  • the processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
  • the memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.
  • the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 530 may include a transmitter and a receiver.
  • the transceiver 530 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 500 may specifically be a network device in an embodiment of the application, and the communication device 500 may implement the corresponding process implemented by the target base station in each method of the embodiment of the application. For the sake of brevity, it will not be repeated here. .
  • the communication device 500 may specifically be a network device in an embodiment of the application, and the communication device 500 may implement the corresponding procedures implemented by the anchor base station in each method of the embodiments of the application. For the sake of brevity, it will not be omitted here Go into details.
  • Fig. 13 is a schematic structural diagram of a device according to an embodiment of the present application.
  • the apparatus 600 shown in FIG. 13 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the apparatus 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the device 600 may further include an input interface 630.
  • the processor 610 can control the input interface 630 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the device 600 may further include an output interface 640.
  • the processor 610 can control the output interface 640 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding procedures implemented by the target base station in the various methods of the embodiments of the present application.
  • the device can implement the corresponding procedures implemented by the target base station in the various methods of the embodiments of the present application.
  • the device can implement the corresponding procedures implemented by the target base station in the various methods of the embodiments of the present application.
  • the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding procedures implemented by the anchor base station in the various methods of the embodiments of the present application.
  • the device can implement the corresponding procedures implemented by the anchor base station in the various methods of the embodiments of the present application.
  • details are not described herein again.
  • the device mentioned in the embodiment of the present application may also be a chip.
  • it can be a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.
  • FIG. 14 is a schematic block diagram of a communication system 700 provided by an embodiment of the present application.
  • the communication system 700 includes a terminal device 710, a target base station 720, an anchor base station 730, and a core network device 740.
  • the terminal device 710 can be used to implement the corresponding function implemented by the terminal device in the above method
  • the target base station 720 can be used to implement the corresponding function implemented by the target base station in the above method
  • the anchor base station 730 can be used To implement the corresponding functions implemented by the anchor base station in the above method, for the sake of brevity, details are not repeated here.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the aforementioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the target base station in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the target base station in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the anchor base station in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the anchor base station in each method of the embodiment of the present application.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the target base station in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the target base station in each method of the embodiment of the present application.
  • the target base station for the sake of brevity, it is not here. Repeat it again.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the anchor base station in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the anchor base station in each method of the embodiment of the present application.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program is run on the computer, the computer is caused to execute the corresponding process implemented by the target base station in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the anchor base station in each method of the embodiment of the present application. It's concise, so I won't repeat it here.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请实施例提供了一种数据传输方法和网络设备，能够在不迁移终端设备的上下文的情况下，实现小数据传输。该数据传输方法包括：目标基站向锚点基站发送第一信息，该第一信息包括非激活态终端设备发送的上行数据，其中，该第一信息通过容器承载方式传输，或者，该第一信息通过隧道承载方式传输。

Description

数据传输方法和网络设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种数据传输方法和网络设备。
背景技术
新空口(New Radio，NR)系统支持小数据传输，目标基站接收到终端设备发送的上行数据之后，需要将终端设备的上下文从锚点基站迁移到目标基站，目标基站才能将该上行数据发送给核心网，增加了基站之间迁移终端设备的上下文所产生的信令开销。
发明内容
本申请实施例提供了一种数据传输方法和网络设备，能够在不迁移终端设备的上下文的情况下，实现小数据传输。
第一方面，提供了一种数据传输方法，该方法包括：
目标基站向锚点基站发送第一信息，该第一信息包括非激活态终端设备发送的上行数据，其中，该第一信息通过容器承载方式传输，或者，该第一信息通过隧道承载方式传输。
第二方面，提供了一种数据传输方法，该方法包括：
锚点基站接收目标基站发送的第一信息，该第一信息包括非激活态终端设备发送的上行数据，其中，该第一信息通过容器承载方式传输，或者，该第一信息通过隧道承载方式传输。
第三方面，提供了一种网络设备，用于执行上述第一方面中由目标基站执行的方法。
具体地，该网络设备包括用于执行上述第一方面中由目标基站执行的方法的功能模块。
第四方面，提供了一种网络设备，用于执行上述第二方面中由锚点基站执行的方法。
具体地，该网络设备包括用于执行上述第二方面中由锚点基站执行的方法的功能模块。
第五方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面中由目标基站执行的方法。
第六方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面中由锚点基站执行的方法。
第七方面，提供了一种装置，用于实现上述第一方面至第二方面中的任一方面中的方法。
具体地，该装置包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该装置的设备执行如上述第一方面至第二方面中的任一方面中的方法。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
通过上述技术方案，在不提取终端设备的上下文的情况下，目标基站能够将非激活态终端设备发送的上行数据转发至锚点基站，从而非激活态终端设备可以将上行数据传输至核心网设备。也即，本申请技术方案能够在不迁移终端设备的上下文的情况下，实现小数据传输。
附图说明
图1是本申请提供的一种通信系统架构的示意性图。
图2是本申请提供的一种终端设备状态转换的示意性图。
图3是本申请提供的一种非激活态终端设备RNA的示意性图。
图4是本申请提供的一种存在上下文迁移的RNAU的示意性流程图。
图5是本申请提供的一种无上下文迁移的RNAU的示意性流程图。
图6是本申请提供的一种小数据传输的示意性流程图。
图7是根据本申请实施例提供的一种数据传输方法的示意性流程图。
图8是根据本申请实施例提供的一种通过容器传输上行数据的示意性流程图。
图9是根据本申请实施例提供的一种通过隧道传输上行数据的示意性流程图。
图10是根据本申请实施例提供的一种网络设备的示意性框图。
图11是根据本申请实施例提供的另一种网络设备的示意性框图。
图12是根据本申请实施例提供的一种通信设备的示意性框图。
图13是根据本申请实施例提供的一种装置的示意性框图。
图14是根据本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。针对本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
可选地，本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是 WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备或者基站(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
应理解，在本申请实施例中，NR也可以独立部署，5G网络环境中为了降低空口信令和快速恢复无线连接，快速恢复数据业务的目的，定了一个新的无线资源控制(Radio Resource Control，RRC)状态，即RRC_INACTIVE(非激活)状态。这种状态有别于RRC_IDLE(空闲)和RRC_CONNECTED(连接)状态。
在RRC_IDLE状态下：移动性为基于终端设备的小区选择重选，寻呼由核心网(Core Network，CN)发起，寻呼区域由CN配置。基站侧不存在终端设备接入层(Access Stratum，AS)上下文，也不存在RRC连接。
在RRC_CONNECTED状态下：存在RRC连接，基站和终端设备存在终端设备AS上下文。网络设备知道终端设备的位置是具体小区级别的。移动性是网络设备控制的移动性。终端设备和基站之间可以传输单播数据。
RRC_INACTIVE：移动性为基于终端设备的小区选择重选，存在CN-NR之间的连接，终端设备AS上下文存在某个基站上，寻呼由无线接入网(Radio Access Network，RAN)触发，基于RAN的寻呼区域由RAN管理，网络设备知道终端设备的位置是基于RAN的寻呼区域级别的。
需要说明的是，在本申请实施例中，非激活态也可以称之为去激活态，本申请对此并不限定。
网络设备可以控制终端设备的状态转换，例如，如图2所示，处于RRC_CONNECTED状态下的终端设备可以通过释放RRC连接进入RRC_IDLE状态；处于RRC_IDLE状态的终端设备可以通过建立RRC连接进入RRC_CONNECTED状态；处于RRC_CONNECTED状态下的UE可以通过暂停释放(Release with Suspend)RRC连接进入RRC_INACTIVE状态；处于RRC_INACTIVE状态的UE可以通过恢复(Resume)RRC连接进入RRC_CONNECTED状态，也可以通过释放RRC连接进入 RRC_IDLE状态。
需要说明的是，终端设备处于RRC_INACTIVE状态，在如下情况终端设备自主回到idle状态：
接收到CN初始的寻呼消息时；
发起RRC恢复请求时，启动定时器T319，如果定时器超时；
基于竞争的随机接入消息4(Message4，MSG4)完整性保护验证失败时；
小区重选到其他无线接入技术(Radio Access Technology，RAT)时；
进入驻留任何小区(camp on any cell)状态。
RRC_INACTIVE状态的特征：
RAN和CN之间的连接时保持的；
终端设备和至少一个gNB保存AS上下文；
终端设备对于RAN侧来说是可达的，相关参数由RAN配置；
当终端设备在RAN配置的RAN通知区域(RAN Notification area，RNA)内移动时不需要通知网络侧(核心网设备)，但当移动出RNA时需要通知网络侧(核心网设备)；
UE在RNA内移动按照小区选择重选方式。
需要说明的是，RNA具体可以如图3所示，在如图3所示的RNA中，终端设备在基站1至基站5之间移动时不需要通知网络侧，但当终端设备移动至基站6或者基站7时需要通知网络侧。
当终端设备处于RRC_INACTIVE状态，网络设备会通过RRC Release(释放)专用信令给终端设备配置RRC_INACTIVE的配置参数，例如，配置RNA，RNA用于控制终端设备在inactive状态下进行小区选择重选的区域，也是RAN初始的寻呼范围区域。
当终端设备在RNA区域内移动时不用通知网络侧，遵循空闲(idle)状态下移动性行为，即小区选择重选原则。当终端设备移动出RAN配置的寻呼区域时，会触发终端设备恢复RRC连接并重新获取RAN配置的寻呼区域。当终端设备有下行数据到达时，为终端设备保持RAN和CN之间连接的gNB会触发RAN寻呼区域内的所有小区发送寻呼消息给终端设备，使得INACTIVE状态的终端设备能够恢复RRC连接，进行数据接收。处于INACTIVE状态的终端设备配置了RAN寻呼区域，在该区域内为了保证终端设备的可达性，终端设备需要按照网络配置的周期进行周期性位置更新。
所以触发终端设备执行RNA更新的场景有RAN通知区域更新(RAN Notification Area Update，RNAU)定时器超时或者UE移动到RNA之外的区域。
需要说明的是，当终端设备发起RRC连接恢复过程的目标基站不是锚点(anchor)基站，则锚点基站判决是否需要转移终端设备的上下文到目标基站。所以一般目标基站会将终端设备发起RRC连接恢复请求消息中携带的原因值(cause)在终端设备上下文索要过程中，发送给锚点基站，锚点基站判决是否需要转移终端设备的上下文到目标基站。例如周期性RAN位置更新一般不需要进行上下文转移。
例如，如图4所示，存在上下文迁移的RNAU具体如下S11至S19所述的流程实现。
S11.终端设备(UE)向目标基站(gNB)发送RRC连接恢复请求(Resume Request)，该RRC连接恢复请求用于RNA更新；
S12.目标基站向锚点基站(也可以称之为上一次服务的基站(Last Serving gNB))发送提取UE上下文请求(RETRIEVE UE CONTEXT REQUEST)；
S13.锚点基站向目标基站发送提取UE上下文响应(RETRIEVE UE CONTEXT RESPONSE)；
S14.将UE设置为非激活态(Send UE to INACTIVE)；
S15.目标基站向锚点基站发送数据转发地址指示(DATA FORWARDING ADDRESS INDICATION)(可选地)；
S16.目标基站向接入与移动性管理功能(Access and Mobility Management Function，AMF)实体发送路径切换请求；
S17.AMF实体向目标基站发送路径切换响应；
S18.目标基站向终端设备发送RRC释放消息；
S19.目标基站向锚点基站发送UE上下文释放消息。
又例如，如图5所示，没有上下文迁移的RNAU具体如下S21至S24所述的流程实现。
S21.终端设备(UE)向目标基站(gNB)发送RRC连接恢复请求(Resume Request)，该RRC连接恢复请求用于RNA更新；
S22.目标基站向锚点基站(也可以称之为上一次服务的基站(Last Serving gNB))发送提取UE上下文请求(RETRIEVE UE CONTEXT REQUEST)；
S23.锚点基站向目标基站发送提取UE上下文失败(RETRIEVE UE CONTEXT FAILURE)；
S24.目标基站向终端设备发送RRC释放消息。
在LTE中，引入了小数据传输(early data transmission，EDT)，在该过程中，终端设备可能始终保持在空闲(idle)状态或者挂起(suspend)状态或者非激活(inactive)状态，完成上行和/或下行小数据包的传输。例如，如图6所示，用户面数据传输方案具体可以如下S31至S38所述的流程实现。
S31.UE向eNB发送RRC连接恢复请求(Resume Request)，该RRC连接恢复请求包括UE发送的上行数据(即小数据传输)；
S32.eNB向移动性管理实体(Mobility Management Entity，MME)发送UE上下文恢复请求(UE CONTEXT RESUME REQUEST)；
S33.修改MME与服务网关(Serving Gateway，SGW)之间的承载；
S34.MME向eNB发送UE上下文恢复响应(UE CONTEXT RESUME RESPONSE)；
S35.eNB向SGW发送UE所发送的上行数据(即小数据传输)；
S36.SGW接收eNB发送的下行数据(可选地)；
S37.挂起eNB与SGW之间的流程，以及修改MME与SGW之间的承载；
S38.eNB向UE发送RRC连接释放消息，可选地，该RRC连接释放消息包括下行数据。
需要说明的是，对于小数据传输，其实UE并没有进入连接状态，就完成了小数据包的传输，这类传输与进入连接态传输移动宽带(Mobile Broadband，MBB)业务不同。
在小数据传输方案中，目标基站接收到UE发送的上行数据之后，需要先进行UE的上下文的迁移，也就是将UE的上下文从锚点基站迁移到目标基站，目标基站才能将UE的数据发送给核心网。
为了进一步提高数据传输效率，减少基站之间迁移UE的上下文所产生的信令开销，本申请引入了一种基站之间传输数据的方式。具体地，本申请提出了一种数据传输的方案，在不提取终端设备的上下文的情况下，目标基站能够将非激活态终端设备发送的上行数据转发至锚点基站，从而非激活态终端设备可以将上行数据传输至核心网设备。也即，本申请技术方案能够在不迁移终端设备的上下文的情况下，实现小数据传输。
以下通过具体实施例详述本申请的技术方案。
图7是根据本申请实施例的数据传输方法200的示意性流程图，如图7所示，该方法200可以包括如下内容中的至少部分内容：
S210，目标基站向锚点基站发送第一信息，该第一信息包括非激活态终端设备发送的上行数据，其中，该第一信息通过容器承载方式传输，或者，该第一信息通过隧道承载方式传输；
S220，该锚点基站接收该目标基站发送的该第一信息。
需要说明的是，在本申请实施例中，该终端设备处于非激活(Inactive)态，该目标基站可以是该终端设备驻留的基站，该目标基站也可以是该终端设备即将接入的基站，该锚点基站可以是保存有该终端设备的上下文信息的基站。
可选地，该上行数据为小数据传输(EDT)。
可选地，在S210之前，该目标基站接收该终端设备发送的RRC恢复请求信息，该RRC恢复请求信息与该上行数据复用一个传输块。
例如，满足一定的预设条件下，处于非激活态的终端设备向目标基站发送RRC恢复请求信息，且该RRC恢复请求信息与该上行数据复用一个传输块。
可选地，该预设条件可以是网络设备配置的，该预设条件也可以是协议约定的。例如，该预设条件可以是数据门限、逻辑信道优先级等。
可选地，在本申请实施例中，该上行数据包括以下中的至少一种：
用户面数据、控制面数据。
例如，用户面数据为数据无线承载(Data Radio Bearer，DRB)中的数据。
例如，控制面数据为信令无线承载(signaling radio bearers，SRB)中的数据。
示例1，该第一信息通过容器(container)承载方式传输。此种情况下，该第一信息对于该锚点基站不可见，或者，该第一信息透传该锚点基站，或者，该锚点基站无法解读该第一信息中的内容。
在示例1中，该锚点基站在接收到该第一信息之后，可以将该第一信息转发至核心网设备。由于该第一信息对于该锚点基站不可见，该锚点基站无法解读该第一信息中的内容。
可选地，在示例1中，该第一信息用于请求从该锚点基站提取该终端设备的上下文信息(retrieve UE context request)。
可选地，在示例1中，该锚点基站向该目标基站发送第二信息，该第二信息用于指示提取该终端设备的上下文信息失败(retrieve UE context failure)，或，该第二信息包括该终端设备的上下文信息。
可选地，在示例1中，在该第二信息用于指示提取该终端设备的上下文信息失败的情况下，该第 二信息包括RRC释放信息，且该RRC释放信息通过容器承载方式传输。进一步的，该目标基站将该RRC释放信息转发给该终端设备。
可选地，在示例1中，该第二信息包括第一指示信息，该第一指示信息用于指示已将该上行数据上传至核心网设备。
示例2，该第一信息通过隧道(Tunnel)承载方式传输。此种情况下，该第一信息对于该锚点基站可见，或者，该锚点基站可以解读该第一信息中的内容。
在示例2中，该锚点基站在接收到该第一信息之后，可以将该上行数据转发至核心网设备。
可选地，在示例2中，该目标基站触发建立该隧道。也就是说，在示例2中，该目标基站需要预先建立该隧道。
可选地，目标基站触发建立隧道具体可以包括：
该目标基站向该锚点基站发送第三信息，其中，该第三信息包括用于建立该隧道的信息和用于指示接收到该上行数据的信息；
该锚点基站向该目标基站发送第四信息，其中，该第四信息包括该锚点基站反馈的用于建立该隧道的信息。
可选地，用于建立该隧道的信息可以是GPRS隧道协议(GPRS Tunneling Protocol，GTP)Tunnel。
可选地，该第三信息用于请求从该锚点基站提取该终端设备的上下文信息。
可选地，在示例2中，该目标基站接收该锚点基站发送的第五信息，该第五信息用于指示提取该终端设备的上下文信息失败，或者，该第五信息包括该终端设备的上下文信息。
可选地，在示例2中，在该第五信息用于指示提取该终端设备的上下文信息失败的情况下，该第五信息包括RRC释放信息，且该RRC释放信息通过容器承载方式传输。进一步的，该目标基站将该RRC释放信息转发给该终端设备。
可选地，在示例2中，该第五信息包括第二指示信息，该第二指示信息用于指示已将该上行数据上传至核心网设备。
在本申请实施例中，核心网设备例如可以是用户面功能(User Plane Function，UPF)实体。
因此，在本申请实施例中，在不提取终端设备的上下文的情况下，目标基站能够将非激活态终端设备发送的上行数据转发至锚点基站，从而非激活态终端设备可以将上行数据传输至核心网设备。也即，本申请技术方案能够在不迁移终端设备的上下文的情况下，实现小数据传输。
以下通过实施例1和实施例2详述本申请的数据传输方案。
实施例1，非激活态终端设备发送的上行数据通过容器承载方式传输。具体如图8所示，非激活态终端设备具体可以如下S41至S46所述的流程实现小数据传输。
S41.终端设备(非激活态)向目标基站发送RRC连接恢复请求，该RRC连接恢复请求包括终端设备发送的上行数据(即小数据传输(EDT))；可选地，该RRC连接恢复请求包括非激活态无线网络临时标识符(Inactive Radio Network Temporary Identity，I-RNTI)、恢复原因；
S42.目标基站向锚点基站发送第一信息，该第一信息用于提取终端设备的上下文信息(Retrieve UE Context Request)，该第一信息包括终端设备发送的上行数据，该上行数据通过容器(container)承载方式传输；
S43.锚点基站向UPF实体转发该上行数据；
S44.UPF实体向锚点基站发送下行数据(可选地)；
S45.锚点基站向目标基站发送第二信息，该第二信息用于指示提取终端设备的上下文信息失败(Retrieve UE Context Failure)；可选地，在UPF实体向锚点基站发送下行数据的情况下，该第二信息包括该下行数据，该下行数据通过容器(container)承载方式传输；可选地，该第二信息包括第一指示信息，该第一指示信息用于指示已将该上行数据上传至核心网设备(UPF实体)；
S46.目标基站向终端设备发送RRC连接释放消息；可选地，在UPF实体向锚点基站发送下行数据的情况下，该RRC连接释放消息包括该下行数据；可选地，该RRC连接释放消息包括I-RNTI、释放原因、网络颜色代码(Network Color Code，NCC)。
实施例2，非激活态终端设备发送的上行数据通过隧道承载方式传输。具体如图9所示，非激活态终端设备具体可以如下S51至S58所述的流程实现小数据传输。
S51.终端设备(非激活态)向目标基站发送RRC连接恢复请求，该RRC连接恢复请求包括终端设备发送的上行数据(即小数据传输(EDT))；可选地，该RRC连接恢复请求包括I-RNTI、恢复原因；
S52.目标基站向锚点基站发送第三信息，该第三信息用于提取终端设备的上下文信息(Retrieve UE Context Request)，该第三信息包括用于建立隧道的信息和用于指示接收到该上行数据的信息；
S53.锚点基站向目标基站发送第四信息，其中，该第四信息包括锚点基站反馈的用于建立隧道的信息；
S54.目标基站向锚点基站发送第一信息，该第一信息包括非激活态终端设备发送的上行数据，其中，该第一信息通过隧道承载方式传输；
S55.锚点基站向UPF实体转发该上行数据；
S56.UPF实体向锚点基站发送下行数据(可选地)；
S57.锚点基站向目标基站发送第五信息，该第五信息用于指示提取终端设备的上下文信息失败(Retrieve UE Context Failure)；可选地，在UPF实体向锚点基站发送下行数据的情况下，该第五信息包括该下行数据，该下行数据通过容器(container)承载方式传输；可选地，该第五信息包括第二指示信息，该第二指示信息用于指示已将该上行数据上传至核心网设备(UPF实体)；
S58.目标基站向终端设备发送RRC连接释放消息；可选地，在UPF实体向锚点基站发送下行数据的情况下，该RRC连接释放消息包括该下行数据；可选地，该RRC连接释放消息包括I-RNTI、释放原因、NCC。
上文结合图7至图9，详细描述了本申请的方法实施例，下文结合图10至图14，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图10示出了根据本申请实施例的网络设备300的示意性框图。如图10所示，该网络设备300为目标基站，该网络设备300包括：
通信单元310，用于向锚点基站发送第一信息，该第一信息包括非激活态终端设备发送的上行数据，其中，该第一信息通过容器承载方式传输，或者，该第一信息通过隧道承载方式传输。
可选地，在该第一信息通过容器承载方式传输的情况下，该第一信息用于请求从该锚点基站提取该终端设备的上下文信息。
可选地，该通信单元310还用于接收该锚点基站发送的第二信息，该第二信息用于指示提取该终端设备的上下文信息失败，或者，该第二信息包括该终端设备的上下文信息。
可选地，在该第二信息用于指示提取该终端设备的上下文信息失败的情况下，该第二信息包括无线资源控制RRC释放信息，且该RRC释放信息通过容器承载方式传输；
该通信单元310还用于将该RRC释放信息转发给该终端设备。
可选地，该第二信息包括第一指示信息，该第一指示信息用于指示已将该上行数据上传至核心网设备。
可选地，在该第一信息通过隧道承载方式传输的情况下，该通信单元310还用于触发建立该隧道。
可选地，该通信单元310具体用于：
向该锚点基站发送第三信息，其中，该第三信息包括用于建立该隧道的信息和用于指示接收到该上行数据的信息；
接收该锚点基站发送的第四信息，其中，该第四信息包括该锚点基站反馈的用于建立该隧道的信息。
可选地，该第三信息用于请求从该锚点基站提取该终端设备的上下文信息。
可选地，该通信单元310还用于接收该锚点基站发送的第五信息，该第五信息用于指示提取该终端设备的上下文信息失败，或者，该第五信息包括该终端设备的上下文信息。
可选地，在该第五信息用于指示提取该终端设备的上下文信息失败的情况下，该第五信息包括RRC释放信息，且该RRC释放信息通过容器承载方式传输；
该通信单元310还用于将该RRC释放信息转发给该终端设备。
可选地，该第五信息包括第二指示信息，该第二指示信息用于指示已将该上行数据上传至核心网设备。
可选地，该上行数据包括以下中的至少一种：
用户面数据、控制面数据。
可选地，该上行数据为小数据传输EDT。
可选地，该通信单元310还用于接收该终端设备发送的RRC恢复请求信息，该RRC恢复请求信息与该上行数据复用一个传输块。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。
应理解，根据本申请实施例的网络设备300可对应于本申请方法实施例中的目标基站，并且网络设备300中的各个单元的上述和其它操作和/或功能分别为了实现图7所示方法200中目标基站的相应流程，为了简洁，在此不再赘述。
图11示出了根据本申请实施例的网络设备400的示意性框图。如图11所示，该网络设备400为锚点基站，该网络设备400包括：
通信单元410，用于接收目标基站发送的第一信息，该第一信息包括非激活态终端设备发送的上行数据，其中，该第一信息通过容器承载方式传输，或者，该第一信息通过隧道承载方式传输。
可选地，在该第一信息通过容器承载方式传输的情况下，该通信单元410还用于将该第一信息转发至核心网设备。
可选地，该第一信息用于请求从该锚点基站提取该终端设备的上下文信息。
可选地，该通信单元410还用于向该目标基站发送第二信息，该第二信息用于指示提取该终端设备的上下文信息失败，或者，该第二信息包括该终端设备的上下文信息。
可选地，在该第二信息用于指示提取该终端设备的上下文信息失败的情况下，该第二信息包括无线资源控制RRC释放信息，且该RRC释放信息通过容器承载方式传输。
可选地，该第二信息包括第一指示信息，该第一指示信息用于指示已将该上行数据上传至核心网设备。
可选地，在该第一信息通过隧道承载方式传输的情况下，该通信单元410还用于将该上行数据转发至核心网设备。
可选地，该通信单元410还用于接收该目标基站发送的第三信息，其中，该第三信息包括用于建立该隧道的信息和用于指示接收到该上行数据的信息；
该通信单元410还用于向该目标基站发送第四信息，其中，该第四信息包括该锚点基站反馈的用于建立该隧道的信息。
可选地，该第三信息用于请求从该锚点基站提取该终端设备的上下文信息。
可选地，该通信单元410还用于向该目标基站发送第五信息，该第五信息用于指示提取该终端设备的上下文信息失败，或者，该第五信息包括该终端设备的上下文信息。
可选地，在该第五信息用于指示提取该终端设备的上下文信息失败的情况下，该第五信息包括RRC释放信息，且该RRC释放信息通过容器承载方式传输。
可选地，该第五信息包括第二指示信息，该第二指示信息用于指示已将该上行数据上传至核心网设备。
可选地，该上行数据包括以下中的至少一种：
用户面数据、控制面数据。
可选地，该上行数据为小数据传输EDT。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。
应理解，根据本申请实施例的网络设备400可对应于本申请方法实施例中的锚点基站，并且网络设备400中的各个单元的上述和其它操作和/或功能分别为了实现图7所示方法200中锚点基站的相应流程，为了简洁，在此不再赘述。
图12是本申请实施例提供的一种通信设备500示意性结构图。图12所示的通信设备500包括处理器510，处理器510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图12所示，通信设备500还可以包括存储器520。其中，处理器510可以从存储器520中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器520可以是独立于处理器510的一个单独的器件，也可以集成在处理器510中。
可选地，如图12所示，通信设备500还可以包括收发器530，处理器510可以控制该收发器530与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器530可以包括发射机和接收机。收发器530还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备500具体可为本申请实施例的网络设备，并且该通信设备500可以实现本申请实施例的各个方法中由目标基站实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备500具体可为本申请实施例的网络设备，并且该通信设备500可以实现本申请实施例的各个方法中由锚点基站实现的相应流程，为了简洁，在此不再赘述。
图13是本申请实施例的装置的示意性结构图。图13所示的装置600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图13所示，装置600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，该装置600还可以包括输入接口630。其中，处理器610可以控制该输入接口630与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该装置600还可以包括输出接口640。其中，处理器610可以控制该输出接口640与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该装置可应用于本申请实施例中的网络设备，并且该装置可以实现本申请实施例的各个方法中由目标基站实现的相应流程，为了简洁，在此不再赘述。
可选地，该装置可应用于本申请实施例中的网络设备，并且该装置可以实现本申请实施例的各个方法中由锚点基站实现的相应流程，为了简洁，在此不再赘述。
可选地，本申请实施例提到的装置也可以是芯片。例如可以是系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图14是本申请实施例提供的一种通信系统700的示意性框图。如图14所示，该通信系统700包括终端设备710、目标基站720、锚点基站730和核心网设备740。
其中，该终端设备710可以用于实现上述方法中由终端设备实现的相应的功能，该目标基站720可以用于实现上述方法中由目标基站实现的相应的功能，以及该锚点基站730可以用于实现上述方法中由锚点基站实现的相应的功能，为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由目标基站实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由锚点基站实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由目标基站实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计 算机执行本申请实施例的各个方法中由锚点基站实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由目标基站实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由锚点基站实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。针对这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (66)

  1. 一种数据传输方法，其特征在于，包括：
    目标基站向锚点基站发送第一信息，所述第一信息包括非激活态终端设备发送的上行数据，其中，所述第一信息通过容器承载方式传输，或者，所述第一信息通过隧道承载方式传输。
  2. 如权利要求1所述的方法，其特征在于，在所述第一信息通过容器承载方式传输的情况下，所述第一信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    所述目标基站接收所述锚点基站发送的第二信息，所述第二信息用于指示提取所述终端设备的上下文信息失败，或者，所述第二信息包括所述终端设备的上下文信息。
  4. 如权利要求3所述的方法，其特征在于，
    在所述第二信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第二信息包括无线资源控制RRC释放信息，且所述RRC释放信息通过容器承载方式传输；
    所述方法还包括：
    所述目标基站将所述RRC释放信息转发给所述终端设备。
  5. 如权利要求3或4所述的方法，其特征在于，所述第二信息包括第一指示信息，所述第一指示信息用于指示已将所述上行数据上传至核心网设备。
  6. 如权利要求1所述的方法，其特征在于，在所述第一信息通过隧道承载方式传输的情况下，所述方法还包括：
    所述目标基站触发建立所述隧道。
  7. 如权利要求6所述的方法，其特征在于，所述目标基站触发建立所述隧道，包括：
    所述目标基站向所述锚点基站发送第三信息，其中，所述第三信息包括用于建立所述隧道的信息和用于指示接收到所述上行数据的信息；
    所述目标基站接收所述锚点基站发送的第四信息，其中，所述第四信息包括所述锚点基站反馈的用于建立所述隧道的信息。
  8. 如权利要求7所述的方法，其特征在于，所述第三信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  9. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    所述目标基站接收所述锚点基站发送的第五信息，所述第五信息用于指示提取所述终端设备的上下文信息失败，或者，所述第五信息包括所述终端设备的上下文信息。
  10. 如权利要求9所述的方法，其特征在于，
    在所述第五信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第五信息包括RRC释放信息，且所述RRC释放信息通过容器承载方式传输；
    所述方法还包括：
    所述目标基站将所述RRC释放信息转发给所述终端设备。
  11. 如权利要求9或10所述的方法，其特征在于，所述第五信息包括第二指示信息，所述第二指示信息用于指示已将所述上行数据上传至核心网设备。
  12. 如权利要求1至11中任一项所述的方法，其特征在于，
    所述上行数据包括以下中的至少一种：
    用户面数据、控制面数据。
  13. 如权利要求1至12中任一项所述的方法，其特征在于，所述上行数据为小数据传输EDT。
  14. 如权利要求1至13中任一项所述的方法，其特征在于，所述方法还包括：
    所述目标基站接收所述终端设备发送的RRC恢复请求信息，所述RRC恢复请求信息与所述上行数据复用一个传输块。
  15. 一种数据传输方法，其特征在于，包括：
    锚点基站接收目标基站发送的第一信息，所述第一信息包括非激活态终端设备发送的上行数据，其中，所述第一信息通过容器承载方式传输，或者，所述第一信息通过隧道承载方式传输。
  16. 如权利要求15所述的方法，其特征在于，在所述第一信息通过容器承载方式传输的情况下，所述方法还包括：
    所述锚点基站将所述第一信息转发至核心网设备。
  17. 如权利要求16所述的方法，其特征在于，所述第一信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  18. 如权利要求17所述的方法，其特征在于，所述方法还包括：
    所述锚点基站向所述目标基站发送第二信息，所述第二信息用于指示提取所述终端设备的上下文信息失败，或者，所述第二信息包括所述终端设备的上下文信息。
  19. 如权利要求18所述的方法，其特征在于，
    在所述第二信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第二信息包括无线资源控制RRC释放信息，且所述RRC释放信息通过容器承载方式传输。
  20. 如权利要求18或19所述的方法，其特征在于，所述第二信息包括第一指示信息，所述第一指示信息用于指示已将所述上行数据上传至核心网设备。
  21. 如权利要求15所述的方法，其特征在于，在所述第一信息通过隧道承载方式传输的情况下，所述方法还包括：
    所述锚点基站将所述上行数据转发至核心网设备。
  22. 如权利要求21所述的方法，其特征在于，所述方法还包括：
    所述锚点基站接收所述目标基站发送的第三信息，其中，所述第三信息包括用于建立所述隧道的信息和用于指示接收到所述上行数据的信息；
    所述锚点基站向所述目标基站发送第四信息，其中，所述第四信息包括所述锚点基站反馈的用于建立所述隧道的信息。
  23. 如权利要求22所述的方法，其特征在于，所述第三信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  24. 如权利要求23所述的方法，其特征在于，所述方法还包括：
    所述锚点基站向所述目标基站发送第五信息，所述第五信息用于指示提取所述终端设备的上下文信息失败，或者，所述第五信息包括所述终端设备的上下文信息。
  25. 如权利要求24所述的方法，其特征在于，
    在所述第五信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第五信息包括RRC释放信息，且所述RRC释放信息通过容器承载方式传输。
  26. 如权利要求24或25所述的方法，其特征在于，所述第五信息包括第二指示信息，所述第二指示信息用于指示已将所述上行数据上传至核心网设备。
  27. 如权利要求15至26中任一项所述的方法，其特征在于，
    所述上行数据包括以下中的至少一种：
    用户面数据、控制面数据。
  28. 如权利要求15至27中任一项所述的方法，其特征在于，所述上行数据为小数据传输EDT。
  29. 一种网络设备，其特征在于，所述网络设备为目标基站，所述网络设备包括：
    通信单元，用于向锚点基站发送第一信息，所述第一信息包括非激活态终端设备发送的上行数据，其中，所述第一信息通过容器承载方式传输，或者，所述第一信息通过隧道承载方式传输。
  30. 如权利要求29所述的网络设备，其特征在于，在所述第一信息通过容器承载方式传输的情况下，所述第一信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  31. 如权利要求30所述的网络设备，其特征在于，所述通信单元还用于接收所述锚点基站发送的第二信息，所述第二信息用于指示提取所述终端设备的上下文信息失败，或者，所述第二信息包括所述终端设备的上下文信息。
  32. 如权利要求31所述的网络设备，其特征在于，
    在所述第二信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第二信息包括无线资源控制RRC释放信息，且所述RRC释放信息通过容器承载方式传输；
    所述通信单元还用于将所述RRC释放信息转发给所述终端设备。
  33. 如权利要求31或32所述的网络设备，其特征在于，所述第二信息包括第一指示信息，所述第一指示信息用于指示已将所述上行数据上传至核心网设备。
  34. 如权利要求29所述的网络设备，其特征在于，在所述第一信息通过隧道承载方式传输的情况下，所述通信单元还用于触发建立所述隧道。
  35. 如权利要求34所述的网络设备，其特征在于，所述通信单元具体用于：
    向所述锚点基站发送第三信息，其中，所述第三信息包括用于建立所述隧道的信息和用于指示接收到所述上行数据的信息；
    接收所述锚点基站发送的第四信息，其中，所述第四信息包括所述锚点基站反馈的用于建立所述隧道的信息。
  36. 如权利要求35所述的网络设备，其特征在于，所述第三信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  37. 如权利要求36所述的网络设备，其特征在于，所述通信单元还用于接收所述锚点基站发送的第五信息，所述第五信息用于指示提取所述终端设备的上下文信息失败，或者，所述第五信息包括所述终端设备的上下文信息。
  38. 如权利要求37所述的网络设备，其特征在于，
    在所述第五信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第五信息包括RRC释放信息，且所述RRC释放信息通过容器承载方式传输；
    所述通信单元还用于将所述RRC释放信息转发给所述终端设备。
  39. 如权利要求37或38所述的网络设备，其特征在于，所述第五信息包括第二指示信息，所述第二指示信息用于指示已将所述上行数据上传至核心网设备。
  40. 如权利要求29至39中任一项所述的网络设备，其特征在于，
    所述上行数据包括以下中的至少一种：
    用户面数据、控制面数据。
  41. 如权利要求29至40中任一项所述的网络设备，其特征在于，所述上行数据为小数据传输EDT。
  42. 如权利要求29至41中任一项所述的网络设备，其特征在于，所述通信单元还用于接收所述终端设备发送的RRC恢复请求信息，所述RRC恢复请求信息与所述上行数据复用一个传输块。
  43. 一种网络设备，其特征在于，所述网络设备为锚点基站，所述网络设备包括：
    通信单元，用于接收目标基站发送的第一信息，所述第一信息包括非激活态终端设备发送的上行数据，其中，所述第一信息通过容器承载方式传输，或者，所述第一信息通过隧道承载方式传输。
  44. 如权利要求43所述的网络设备，其特征在于，在所述第一信息通过容器承载方式传输的情况下，所述通信单元还用于将所述第一信息转发至核心网设备。
  45. 如权利要求44所述的网络设备，其特征在于，所述第一信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  46. 如权利要求45所述的网络设备，其特征在于，所述通信单元还用于向所述目标基站发送第二信息，所述第二信息用于指示提取所述终端设备的上下文信息失败，或者，所述第二信息包括所述终端设备的上下文信息。
  47. 如权利要求46所述的网络设备，其特征在于，
    在所述第二信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第二信息包括无线资源控制RRC释放信息，且所述RRC释放信息通过容器承载方式传输。
  48. 如权利要求46或47所述的网络设备，其特征在于，所述第二信息包括第一指示信息，所述第一指示信息用于指示已将所述上行数据上传至核心网设备。
  49. 如权利要求43所述的网络设备，其特征在于，在所述第一信息通过隧道承载方式传输的情况下，所述通信单元还用于将所述上行数据转发至核心网设备。
  50. 如权利要求49所述的网络设备，其特征在于，
    所述通信单元还用于接收所述目标基站发送的第三信息，其中，所述第三信息包括用于建立所述隧道的信息和用于指示接收到所述上行数据的信息；
    所述通信单元还用于向所述目标基站发送第四信息，其中，所述第四信息包括所述锚点基站反馈的用于建立所述隧道的信息。
  51. 如权利要求50所述的网络设备，其特征在于，所述第三信息用于请求从所述锚点基站提取所述终端设备的上下文信息。
  52. 如权利要求51所述的网络设备，其特征在于，所述通信单元还用于向所述目标基站发送第五信息，所述第五信息用于指示提取所述终端设备的上下文信息失败，或者，所述第五信息包括所述终端设备的上下文信息。
  53. 如权利要求52所述的网络设备，其特征在于，
    在所述第五信息用于指示提取所述终端设备的上下文信息失败的情况下，所述第五信息包括RRC释放信息，且所述RRC释放信息通过容器承载方式传输。
  54. 如权利要求52或53所述的网络设备，其特征在于，所述第五信息包括第二指示信息，所述第二指示信息用于指示已将所述上行数据上传至核心网设备。
  55. 如权利要求43至54中任一项所述的网络设备，其特征在于，
    所述上行数据包括以下中的至少一种：
    用户面数据、控制面数据。
  56. 如权利要求43至55中任一项所述的网络设备，其特征在于，所述上行数据为小数据传输 EDT。
  57. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至14中任一项所述的方法。
  58. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求15至28中任一项所述的方法。
  59. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至14中任一项所述的方法。
  60. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求15至28中任一项所述的方法。
  61. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法。
  62. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求15至28中任一项所述的方法。
  63. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至14中任一项所述的方法。
  64. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求15至28中任一项所述的方法。
  65. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法。
  66. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求15至28中任一项所述的方法。
PCT/CN2020/097152 2020-06-19 2020-06-19 数据传输方法和网络设备 WO2021253417A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202080101021.6A CN115669197A (zh) 2020-06-19 2020-06-19 数据传输方法和网络设备
EP20940965.5A EP4156846A4 (en) 2020-06-19 2020-06-19 DATA TRANSMISSION METHOD AND NETWORK DEVICE
PCT/CN2020/097152 WO2021253417A1 (zh) 2020-06-19 2020-06-19 数据传输方法和网络设备
US18/083,338 US20230123866A1 (en) 2020-06-19 2022-12-16 Data transmission method and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/097152 WO2021253417A1 (zh) 2020-06-19 2020-06-19 数据传输方法和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/083,338 Continuation US20230123866A1 (en) 2020-06-19 2022-12-16 Data transmission method and network device

Publications (1)

Publication Number Publication Date
WO2021253417A1 true WO2021253417A1 (zh) 2021-12-23

Family

ID=79268984

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/097152 WO2021253417A1 (zh) 2020-06-19 2020-06-19 数据传输方法和网络设备

Country Status (4)

Country Link
US (1) US20230123866A1 (zh)
EP (1) EP4156846A4 (zh)
CN (1) CN115669197A (zh)
WO (1) WO2021253417A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108617000A (zh) * 2017-01-13 2018-10-02 中兴通讯股份有限公司 信息传输方法及装置
CN108632810A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 控制终端设备状态的方法、终端设备和网络设备
WO2019160467A1 (en) * 2018-02-14 2019-08-22 Sony Mobile Communications Inc Data routing in radio access network
CN110249703A (zh) * 2017-02-03 2019-09-17 瑞典爱立信有限公司 无上下文取得的无线电资源控制恢复
CN110622614A (zh) * 2017-02-13 2019-12-27 华为技术有限公司 用于用户设备标识和通信的系统和方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108617000A (zh) * 2017-01-13 2018-10-02 中兴通讯股份有限公司 信息传输方法及装置
CN110249703A (zh) * 2017-02-03 2019-09-17 瑞典爱立信有限公司 无上下文取得的无线电资源控制恢复
CN110622614A (zh) * 2017-02-13 2019-12-27 华为技术有限公司 用于用户设备标识和通信的系统和方法
CN108632810A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 控制终端设备状态的方法、终端设备和网络设备
WO2019160467A1 (en) * 2018-02-14 2019-08-22 Sony Mobile Communications Inc Data routing in radio access network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INC.: ""Small Data Transmission In Inactive State"", 3GPP TSG-RAN WG3 NR AD HOC MEETING, R3-170158, 12 January 2017 (2017-01-12), XP051212812 *
See also references of EP4156846A4 *

Also Published As

Publication number Publication date
EP4156846A1 (en) 2023-03-29
US20230123866A1 (en) 2023-04-20
CN115669197A (zh) 2023-01-31
EP4156846A4 (en) 2023-07-05

Similar Documents

Publication Publication Date Title
US20200252853A1 (en) Information transmission method and device
US20220124859A1 (en) Data transmission method and apparatus, and communication device
CN112136348B (zh) 更新系统信息的方法、终端设备和网络设备
EP4171162A1 (en) Data transmission method and terminal device
US20230224797A1 (en) Network access method, terminal device, and network device
WO2021258262A1 (zh) 无线通信方法、终端设备和网络设备
WO2021232617A1 (zh) 无线通信方法和终端设备
WO2022011519A1 (zh) 数据传输的方法和终端设备
WO2021226967A1 (zh) 切换的方法和设备
WO2023108454A1 (zh) 上行同步中的定时提前量维持方法、终端设备和网络设备
US20170078924A1 (en) Apparatuses and methods therein for relaying an ongoing data session
WO2021253417A1 (zh) 数据传输方法和网络设备
WO2022006719A1 (zh) 无线通信方法、终端设备和网络设备
WO2022006863A1 (zh) 无线通信方法、终端设备和网络设备
WO2021212465A1 (zh) 无线通信方法和终端设备
WO2023133794A1 (zh) 数据传输方法、终端设备和网络设备
WO2022147729A1 (zh) 功率控制的方法、终端设备和网络设备
WO2023216242A1 (zh) 连接配置方法和终端
WO2024011588A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023035187A1 (zh) 无线通信的方法及设备
WO2023184257A1 (zh) 无线通信的方法、网络设备和终端设备
WO2022099475A1 (zh) 会话管理方法、终端设备和网络设备
WO2021203439A1 (zh) 数据传输方法、终端设备和网络设备
US20230189257A1 (en) Data transmission method and terminal device
WO2022205555A1 (zh) 无线通信的方法和终端设备

Legal Events

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

Ref document number: 20940965

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020940965

Country of ref document: EP

Effective date: 20221221

NENP Non-entry into the national phase

Ref country code: DE