WO2021203252A1 - 非激活态下的数据发送、接收方法及装置、用户设备 - Google Patents

非激活态下的数据发送、接收方法及装置、用户设备 Download PDF

Info

Publication number
WO2021203252A1
WO2021203252A1 PCT/CN2020/083607 CN2020083607W WO2021203252A1 WO 2021203252 A1 WO2021203252 A1 WO 2021203252A1 CN 2020083607 W CN2020083607 W CN 2020083607W WO 2021203252 A1 WO2021203252 A1 WO 2021203252A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrc
data
user equipment
logical channel
data transmission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/083607
Other languages
English (en)
French (fr)
Inventor
石聪
林雪
王淑坤
李海涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to EP20930318.9A priority Critical patent/EP4132205A4/en
Priority to CN202080094713.2A priority patent/CN115024018A/zh
Priority to PCT/CN2020/083607 priority patent/WO2021203252A1/zh
Publication of WO2021203252A1 publication Critical patent/WO2021203252A1/zh
Priority to US17/959,152 priority patent/US12452949B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • This application relates to the field of communications, and specifically to a method and device for sending and receiving data in an inactive state, and user equipment.
  • DRB Data Radio Bearer
  • RRC Radio Resource Control
  • DRB Data Radio Bearer
  • the data arrives irregularly, and the difference in the size of the arriving data packets is also relatively large, which is not suitable for the inactive data transmission mode.
  • the size of data packets is generally small, so it is more suitable for transmission in the inactive state.
  • User Equipment User Equipment
  • the embodiments of the present application provide a method and device for sending and receiving data in an inactive state, and a user equipment, so as to at least solve the technical problem that the UE does not support data transmission in the inactive state in the related art.
  • a data sending method in an inactive state including: a user equipment receives configuration information from a network side device, where the configuration information is used to indicate at least one logical channel of the user equipment And whether at least one of the data radio bearer DRB supports radio resource control (Radio Resource Control, referred to as RRC) inactive data transmission; when the configuration information indicates that at least one logical channel supports RRC inactive data transmission, the user The device sends the data to be sent on at least one logical channel; when the configuration information indicates that the DRB supports data transmission in the RRC inactive state, it sends the data to be sent on the logical channel associated with the DRB.
  • RRC Radio Resource Control
  • the configuration information is also used to indicate whether the user equipment supports RRC inactive data transmission; the above method further includes: when the configuration information indicates that the user equipment does not support RRC inactive data transmission, and the user equipment has data to be sent At this time, the user equipment initiates the RRC recovery process, and when the user equipment is restored to the connected state, sends the data to be sent.
  • the user equipment receiving the configuration information from the network side device includes: the user equipment receives a radio resource control RRC reconfiguration message from the network side device, and obtaining the configuration information from the RRC reconfiguration message.
  • the user equipment receiving configuration information from the network side device includes: the user equipment receiving an RRC release message from the network side device, where the RRC release message is used to release the user equipment from the RRC connected state to the RRC inactive state ; Obtain the configuration information from the RRC release message.
  • obtaining configuration information from the RRC release message includes: obtaining indication information from the release message, where the indication information is used to indicate a DRB supporting RRC inactive data transmission or a logical channel associated with the DRB.
  • the method further includes: when the configuration information indicates that at least one logical channel does not support RRC inactive data transmission, and the user equipment has data to be sent for the DRB corresponding to the at least one logical channel, the user equipment initiates an RRC recovery process, And when the user equipment is restored to the connected state, the data to be sent is sent.
  • the at least one logical channel is determined in the following manner: the user equipment determines from the logical channel set of the user equipment that there is a logical channel with the data to be sent, and uses the logical channel with the data to be sent as the at least one logical channel.
  • the user equipment sending the to-be-sent data of the at least one logical channel includes: in the RRC inactive state, the user equipment determines the multiple logical channels based on the configuration information corresponding to the multiple logical channels. Whether to support RRC inactive data transmission; when multiple logical channels support RRC inactive data transmission, the user equipment initiates RRC inactive data transmission.
  • the method further includes: judging whether the first total data amount of the data to be sent of the multiple logical channels is less than a first threshold; if the first total data amount is less than the first Threshold, the user equipment initiates data transmission in the inactive state; if the first total data volume is greater than the first threshold, the user equipment initiates an RRC recovery procedure.
  • the method further includes: when there are multiple at least one logical channel, and some of the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive data transmission, Determine the second total data volume of the data to be sent in the multiple logical channels; when the second total data volume is not greater than the second threshold, the user equipment multiplexes the data to be sent in the multiple logical channels and initiates RRC deactivation State data transmission.
  • the method further includes: The user equipment returns to the RRC connected state through the RRC recovery process by default to initiate data transmission.
  • the method further includes: The user equipment receives control signaling from the network-side device, where the control signaling is used to indicate that some of the logical channels in the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive state During data transmission, whether to support data transmission in the RRC inactive state.
  • a method for receiving data in an inactive state including: a network side device sends configuration information to a user equipment, where the configuration information is used to indicate at least one logical channel of the user equipment And whether at least one of the data radio bearer DRB supports data transmission in the RRC inactive state; when the configuration information indicates that at least one logical channel supports data transmission in the RRC inactive state, the network side device receives at least the data transmitted by the user equipment The data to be sent on a logical channel or the data to be sent on the logical channel associated with the DRB.
  • the network-side device sending configuration information to the user equipment includes: the network-side device sending an RRC reconfiguration message to the user equipment, where the RRC reconfiguration message carries the configuration information.
  • the network-side device sending configuration information to the user equipment includes: the network-side device sending an RRC release message to the user equipment, where the RRC release message is used to release the user equipment from the RRC connected state to the RRC inactive state, RRC The release message carries configuration information.
  • the configuration information includes: indication information used to indicate a DRB that supports data transmission in an RRC inactive state or a logical channel associated with the DRB.
  • a data sending device in an inactive state including: a receiving module, configured to receive configuration information from a network side device, where the configuration information is used to indicate user equipment Whether at least one of the at least one logical channel and the data radio bearer DRB supports data transmission in the RRC inactive state; the sending module is used for when the configuration information indicates that at least one logical channel supports data transmission in the RRC inactive state, Send the data to be sent on at least one logical channel; when the configuration information indicates that the DRB supports data transmission in the RRC inactive state, send the data to be sent on the logical channel associated with the DRB.
  • the configuration information is also used to indicate whether the user equipment supports RRC inactive data transmission; the sending module is also used to indicate that the user equipment does not support RRC inactive data transmission, and the user equipment has to be sent When data is being sent, the RRC recovery process is initiated, and when the user equipment is restored to the connected state, the data to be sent is sent.
  • the receiving module is further configured to receive a radio resource control RRC reconfiguration message from the network side device, and obtain configuration information from the RRC reconfiguration message.
  • the receiving module is further configured to receive an RRC release message from the network side device, where the RRC release message is used to release the user equipment from the RRC connected state to the RRC inactive state; obtain configuration information from the RRC release message .
  • the receiving module is further configured to obtain indication information from the release message, where the indication information is used to indicate a DRB supporting RRC inactive data transmission or a logical channel associated with the DRB.
  • the device further includes: a recovery module, configured to initiate RRC when the configuration information indicates that at least one logical channel does not support RRC inactive data transmission, and the user equipment has data to be sent for the DRB corresponding to the at least one logical channel Recovery process:
  • the sending module is used to send the data to be sent when the user equipment is restored to the connected state.
  • the at least one logical channel is determined in the following manner: a logical channel with data to be sent is determined from a logical channel set of a cell where the user equipment is located, and the logical channel with data to be sent is used as the at least one logical channel.
  • the sending module is also used to determine whether the multiple logical channels support the RRC inactive state based on the configuration information corresponding to the multiple logical channels in the RRC inactive state.
  • Data transmission When multiple logical channels support RRC inactive data transmission, initiate RRC inactive data transmission.
  • the device further includes: a judging module for judging whether the first total data amount of the data to be sent of the multiple logical channels is less than a first threshold; the sending module is also used for when the total data amount is less than the first threshold, Initiate data transmission in the inactive state; when the first total data amount is greater than the first threshold, initiate an RRC recovery procedure.
  • a judging module for judging whether the first total data amount of the data to be sent of the multiple logical channels is less than a first threshold
  • the sending module is also used for when the total data amount is less than the first threshold, Initiate data transmission in the inactive state; when the first total data amount is greater than the first threshold, initiate an RRC recovery procedure.
  • the device further includes: a determining module, configured to have multiple at least one logical channel, and some of the multiple logical channels support data transmission in the RRC inactive state, and the remaining logical channels do not support the RRC inactive state.
  • a determining module configured to have multiple at least one logical channel, and some of the multiple logical channels support data transmission in the RRC inactive state, and the remaining logical channels do not support the RRC inactive state.
  • the second total data volume of data to be sent in multiple logical channels is determined; the sending module is also used to transfer the data to be sent in multiple logical channels when the second total data volume is not greater than the second threshold. Perform multiplexing and initiate RRC inactive data transmission.
  • the sending module is used when there are multiple at least one logical channel, and some of the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive data transmission ,
  • the default is to restore to the RRC connected state through the RRC recovery process to initiate data transmission.
  • the receiving module is further configured to have multiple at least one logical channel, and some of the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive data transmission
  • the control signaling is used to indicate that some of the logical channels in the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive state
  • the control signaling is used to indicate that some of the logical channels in the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive state During data transmission, whether to support data transmission in the RRC inactive state.
  • a data receiving apparatus in an inactive state including: a sending module, configured to send configuration information to a user equipment, wherein the configuration information is used to indicate at least one of the user equipment Whether at least one of the logical channel and the data radio bearer DRB supports data transmission in the RRC inactive state; the receiving module is used to receive the user when the configuration information indicates that at least one logical channel supports data transmission in the RRC inactive state The data to be sent on at least one logical channel sent by the device or the data to be sent on the logical channel associated with the DRB.
  • the sending module is also used to send an RRC reconfiguration message to the user equipment, where the RRC reconfiguration is optionally used, and the sending module is also used to send an RRC release message to the user equipment, where the RRC release message is used for The user equipment is released from the RRC connected state to the RRC inactive state, and the RRC release message carries configuration information.
  • the configuration information includes: indication information used to indicate a DRB that supports data transmission in an RRC inactive state or a logical channel associated with the DRB.
  • a user equipment including: a transceiver circuit for receiving configuration information from a network side device, where the configuration information is used to indicate at least one logical channel and data of the user equipment Whether at least one of the radio bearer DRBs supports data transmission in the RRC inactive state; the processor is configured to send information about at least one logical channel when the configuration information indicates that at least one logical channel supports data transmission in the RRC inactive state Data to be sent; when the configuration information indicates that the DRB supports data transmission in the RRC inactive state, the transceiver circuit is notified to send the data to be sent on the logical channel associated with the DRB.
  • a network-side device including: a processor, configured to determine configuration information to be sent to a user equipment, where the configuration information is used to indicate at least one logical channel of the user equipment and Whether at least one of the data radio bearer DRB supports data transmission in the RRC inactive state; the transceiver circuit is used to receive the data transmitted by the user equipment when the configuration information indicates that at least one logical channel supports data transmission in the RRC inactive state Data to be sent on at least one logical channel or data to be sent on the logical channel associated with the DRB.
  • a non-volatile storage medium is provided, the non-volatile storage medium is used to store a program, and the program is executed when the program runs in a device where the non-volatile storage medium is located.
  • the above-mentioned data sending method in the inactive state.
  • a processor configured to run a program stored in a memory, and the program is configured to execute the above-mentioned data sending method in an inactive state.
  • the user equipment is used to determine whether the logical channel and/or DRB of the UE supports small data transmission based on the configuration information of the network side device. Since logical channels are often associated with different service types, the The solution in the embodiment of the present application can enable the UE to determine whether the corresponding service data can be transmitted by means of small data transmission according to the network configuration, thereby solving the technical problem of the UE not supporting the data transmission in the Inactive state in the related technology.
  • Figure 1 is a schematic diagram of a data transmission process of a control plane early data transmission (CP-EDT) according to related technologies;
  • CP-EDT control plane early data transmission
  • FIG. 2 is a schematic diagram of a user plane data transmission (UP-EDT) data transmission process according to related technologies
  • Fig. 3 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • Fig. 4 is a schematic structural diagram of a user equipment according to an embodiment of the present application.
  • Fig. 5 is a schematic structural diagram of a network side device according to an embodiment of the present application.
  • Fig. 6 is a flowchart of a data sending method in an inactive state according to an embodiment of the present application
  • Fig. 7 is a structural diagram of a data sending device in an inactive state according to an embodiment of the present application.
  • FIG. 8 is a structural diagram of another optional data sending device in an inactive state according to an embodiment of the present application.
  • Fig. 9 is a flowchart of a method for receiving data in an inactive state according to an embodiment of the present application.
  • Fig. 10 is a structural diagram of a data receiving device in an inactive state according to an embodiment of the present application.
  • One of the 3GPP R17 projects is about small data transmission optimization (RP-193252), which proposes to support the small data transmission of the UE in the RRC Inactive state.
  • the main purpose is to save power and save signaling overhead.
  • Specific project goals include:
  • RACH Random Access Channel
  • RRC_INACTIVE a new RRC state is defined, that is, the RRC_INACTIVE state. This state is different from the RRC_IDLE and RRC_ACTIVE states. in:
  • RRC_IDLE Mobility is based on cell selection and reselection, paging is initiated by the core network (Core network, referred to as CN), and the paging area is configured by the CN. There is no UE Access Stratum (AS) context on the base station side, and there is no RRC connection.
  • AS UE Access Stratum
  • RRC_INACTIVE Mobility is based on cell selection and reselection. In this state, there is a connection between CN-NR, UE AS Context exists on a certain base station, and paging is triggered by the Radio Access Network (RAN for short), based on The paging area of the RAN is managed by the RAN, and the network side knows that the location of the UE is based on the paging area level of the RAN.
  • RAN Radio Access Network
  • RRC_CONNECTED There is an RRC connection, and there is a UE AS Context between the base station and the UE.
  • the network side knows that the location of the UE is at a specific cell level, and the mobility is controlled by the network side, and unicast data can be transmitted between the UE and the base station.
  • the network side can control the switching of the UE between different states.
  • Some UE-side RRC parameters in the RRC Inactive state are configured through the RRC Release message.
  • I-RNTI is used to identify the UE inactive context of the UE on the base station side and is unique in the base station.
  • RNA RAN Notification area
  • RNA is used to control the area where the UE performs cell selection and reselection in the inactive state, and is also the paging range area for the initial paging of the RAN.
  • the RAN Paging cycle is used to calculate the paging occasion of the RAN initial paging.
  • NCC is used for the secret key used in the process of RRC connection recovery.
  • the UE When the UE moves in the RNA area, it does not need to notify the network side, and it follows the mobility behavior in the idle state, that is, the principle of cell selection and reselection.
  • the UE When the UE moves out of the paging area configured by the RAN, the UE triggers the resume RRC connection procedure, that is, the RRC resume procedure, and reacquires the paging area configured by the RAN.
  • the network side needs to transmit data to the UE, that is, when downlink data arrives, the gNB that saves the UE context will trigger all cells in the RAN paging area to send paging messages to the UE, so that the UE in the INACTIVCE state can restore the RRC connection. Perform data reception.
  • the UE in the Inactive state is configured with a RAN paging area. In this area, in order to ensure the reachability of the UE, the UE needs to perform periodic location update according to the period configured by the network. Scenarios that trigger the UE to perform RNA update include RNA-based notification area update (RAN Notification Area Update, referred to as RNAU) timer timeout or the UE moves to an area outside of RNA.
  • RNAU RNA-based notification area update
  • the RRC Inactive state defined by NR does not support the UE to transmit user plane data.
  • LTE defines the small data transmission process, that is, EDT (Early Data Transmission), which is mainly for NB-IoT UE and Emtc UE.
  • EDT Electronic Data Transmission
  • the UE can trigger EDT based on RACH.
  • EDT mainly includes user plane EDT (UP-EDT) and control plane EDT (CP-EDT).
  • CP-EDT data is mainly transmitted in NAS messages
  • UP-EDT data is mainly transmitted by multiplexing user plane data in RRC messages.
  • the network side broadcasts a maximum small data transmission size that the cell can support in a system broadcast message.
  • the UE has data transmission, if the size of the data to be transmitted is less than the maximum supported data size of the broadcast, the UE initiates the EDT process.
  • different services are reflected in different DRB configurations (different DRBs are used to transmit service types with different QoS requirements).
  • the data arrives irregularly, and the difference in the size of the arriving data packets is also relatively large, which is not suitable for the small data transmission mode in the inactive state.
  • the size of data packets is generally small, so it is more suitable for transmission in the inactive state.
  • data transmission in the inactive state is not supported.
  • the UE receives a network configuration message, which can configure whether different DRBs support small data transmission; the UE decides whether to configure the RRC Inactive according to the parameter configuration of different DRBs. Whether the state initiates small data transmission; when there is data to be sent on a certain logical channel of the UE in the RRC Inactive state, the UE determines whether the DRB supports the small data transmission in the RRC Inactive state, that is, whether an indication parameter is configured. If the logical channel supports small data transmission, the UE initiates small data transmission in the RRC Inactive state.
  • the UE initiates an RRC Resume procedure.
  • the network configuration message can be an RRC reconfiguration message in the connected state, or an RRC release message.
  • the parameter configuration of the DRB may be the configuration of the logical channel associated with it. The following is a detailed description in conjunction with the embodiments.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 300 applied in the embodiment of the present application is shown in FIG. 3.
  • the communication system 300 may include a network device 310, and the network device 310 may be a device that communicates with a user equipment 320 (or called a communication terminal or a terminal).
  • the network device 310 may provide communication coverage for a specific geographic area, and may communicate with user equipment located in the coverage area.
  • the network device 310 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • LTE Long Term Evolutional Node B, eNB or eNodeB
  • the wireless controller in the Cloud Radio Access Network (CRAN) or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device
  • the communication system 300 also includes at least one user equipment 320 located within the coverage area of the network device 310.
  • user equipment includes, but is not limited to, connection via wired lines, such as public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another user equipment device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN public switched telephone networks
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • a user equipment set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • User equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, user equipment in 5G networks, or user equipment in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • D2D device-to-device
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • Figure 3 exemplarily shows one network device and two user equipment.
  • the communication system 300 may include multiple network devices and the coverage of each network device may include other numbers of user equipment. The embodiment does not limit this.
  • the communication system 300 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.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 310 and a user equipment 320 with communication functions, and the network device 310 and the user equipment 320 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 300, such as network controllers, mobility management entities, and other network entities, which are not limited in this embodiment of the application.
  • the user equipment 320 includes but is not limited to: a transceiver circuit 400 for receiving configuration information from a network side device, where the configuration information is used to indicate at least one logic of the user equipment Whether at least one of the channel and the data radio bearer DRB supports data transmission in the RRC inactive state; the processor 402 is configured to send at least at least one logical channel when the configuration information indicates that at least one logical channel supports data transmission in the RRC inactive state. Data to be sent on a logical channel; when the configuration information indicates that the DRB supports data transmission in the RRC inactive state, the transceiver circuit 400 is notified to send the data to be sent on the logical channel associated with the DRB.
  • the user equipment may also include hardware components such as the memory 404.
  • the network side device 310 provided in the embodiment of the present application includes: a processor 500, configured to determine configuration information to be sent to the user equipment, where the configuration information is used to indicate at least one logical channel of the user equipment And whether at least one of the data radio bearer DRB supports data transmission in the RRC inactive state; the transceiver circuit 502 is configured to receive the user equipment when the configuration information indicates that at least one logical channel supports data transmission in the RRC inactive state The sent data of at least one logical channel or the data to be sent on the logical channel associated with the DRB.
  • Hardware components such as memory 504 may also be included.
  • the embodiment of the present application provides a method embodiment of a data transmission method in an inactive state. Instructions are executed in a computer system, and, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than here.
  • Fig. 6 is a data sending method in an inactive state according to an embodiment of the present application. As shown in Fig. 1, the method includes the following steps:
  • Step S602 The user equipment receives configuration information from the network side device, where the configuration information is used to indicate whether at least one of at least one logical channel and DRB of the user equipment supports RRC inactive data transmission;
  • Step S604 When the configuration information indicates that at least one logical channel supports RRC inactive data transmission, the user equipment sends at least one logical channel to send data; when the configuration information indicates that the DRB supports RRC inactive data transmission, send and Data to be sent on the logical channel associated with the DRB.
  • the configuration information is also used to indicate whether the user equipment supports RRC inactive data transmission; at this time, the configuration information indicates that the user equipment does not support RRC inactive data transmission, and the user equipment exists
  • the user equipment initiates an RRC recovery process, and when the user equipment is restored to the connected state, the data to be sent is sent.
  • the user equipment can determine whether to support data transmission in the RRC Inactive state in two situations: 1) Determine whether data transmission in the RRC Inactive state is required based on the logical channel configuration in the connected state; 2) Based on the RRC release message Configure the small data transmission DRB.
  • the user equipment receives the RRC reconfiguration message from the network side device, and obtains configuration information from the RRC reconfiguration message.
  • the user equipment receives the RRC release message from the network side device, where the RRC release message is used to release the user equipment from the RRC connected state to the RRC inactive state; obtain configuration information from the RRC release message .
  • the indication information is obtained from the release message, and the indication information is used to indicate the DRB that supports data transmission in the RRC inactive state or the logical channel associated with the DRB.
  • the user equipment When the configuration information indicates that at least one logical channel does not support data transmission in the RRC inactive state, and the user equipment has data to be sent for the DRB corresponding to the at least one logical channel, the user equipment initiates the RRC recovery process, and the user equipment returns to the connected state When, send the data to be sent.
  • the above-mentioned at least one logical channel is determined in the following manner: the user equipment determines from the logical channel set of the user equipment that there is a logical channel with data to be sent, and uses the logical channel with data to be sent as the at least one logical channel.
  • Logical channel the user equipment determines from the logical channel set of the user equipment that there is a logical channel with data to be sent, and uses the logical channel with data to be sent as the at least one logical channel.
  • the user equipment determines whether the multiple logical channels support RRC inactive data transmission based on the configuration information corresponding to the multiple logical channels; When data transmission in the RRC inactive state is supported, the user equipment initiates data transmission in the RRC inactive state.
  • the user equipment before the user equipment initiates RRC inactive data transmission, it is determined whether the first total data volume of the data to be sent of the multiple logical channels is less than the first threshold; if the first total data volume If it is less than the first threshold, the user equipment initiates data transmission in an inactive state; if the first total data volume is greater than the first threshold, the user equipment initiates an RRC recovery process.
  • the second total data volume of the data to be sent in the multiple logical channels is determined; when the second total data volume is not greater than the second threshold, the user equipment multiplexes the data to be sent in the multiple logical channels and initiates RRC Inactive data transmission.
  • the user equipment passes through by default The RRC recovery process returns to the RRC connected state to initiate data transmission.
  • the user equipment receives data from The control signaling of the network-side device, where the control signaling is used to indicate that some of the logical channels in the multiple logical channels support RRC inactive data transmission, and when the remaining logical channels do not support RRC inactive data transmission, Whether to support data transmission in the RRC inactive state.
  • the above control signaling can be configured in the RRC release message, or configured in a certain logical channel.
  • the UE is configured with different DRBs based on the network, and different DRBs are respectively associated with different logical channels; each of the different logical channels is configured with a parameter to characterize whether the data of the logical channel can be transmitted in the RRC Inactive state, for example:
  • Logical channel #1 Can be transmitted in the RRC Inactive state
  • Logical channel #2 Cannot transmit in RRC Inactive state
  • Logical channel #3 can be transmitted in the RRC Inactive state
  • the UE in the RRC Inactive state When the UE in the RRC Inactive state has data to be sent, it first determines the configuration parameters of the logical channel corresponding to the data to be sent, that is, whether the data of the logical channel is allowed to be sent in the RRC Inactive state.
  • the UE If there is data to be sent in logical channel #1, or logical channel #3, or logical channel #1 and logical channel #2, the UE initiates small data transmission based on the configuration in the RRC Inactive state.
  • the UE If there is data to be sent in logical channel #2, the UE initiates an RRC resume procedure, that is, resumes to the RRC connected state to initiate data transmission.
  • a configuration method of the foregoing logical channel is as follows: configure a "Boolean" parameter to indicate whether the logical channel can allow transmission in the RRC Inactive state.
  • the total data size of logical channel #1 and logical channel #2 does not exceed the maximum small data size indicated by the cell, and the UE multiplexes the data of logical channel #1 and logical channel #2 to transmit in the RRC Inactive state .
  • the UE uses the RRC resume procedure by default in this case, that is, resumes to the RRC connected state to initiate data transmission;
  • the network side device can configure a signaling to indicate whether the UE can transmit data in the RRC Inactive state in this case; the signaling can be configured in the RRC release message, or configured in a certain logical channel, For example, in logical channel #2.
  • the small data transmission DRB is configured through the RRC release process
  • a DRB for transmitting small data is configured in the RRC Release message at the same time, and the DRB is associated with a logical channel; for example:
  • Logical channel #1 The associated DRB is configured in the RRC connected state Logical channel #2
  • the associated DRB is configured in the RRC connected state Logical channel #3
  • the associated DRB is configured in the RRC connected state
  • the UE can initiate small data transmission in the RRC Inactive state only when there is data to be sent in logical channel #4;
  • the UE does not receive the DRB configuration when released by the network to the RRC Inactive state, the UE does not support data transmission in the RRC Inactive state;
  • the UE For other logical channels, if there is data to be sent, the UE initiates an RRC resume (resume) process, and then initiates data transmission when it is restored to the RRC connected state.
  • RRC resume resume
  • the UE When the total data size of logical channel #3 and logical channel #4 does not exceed the maximum small data size indicated by the cell, the UE multiplexes the data of logical channel #3 and logical channel #4 for transmission in the RRC Inactive state. or,
  • the UE uses the RRC resume procedure by default, that is, resumes to the RRC connected state to initiate data transmission;
  • the network can configure a signaling to indicate whether the UE can transmit data in the RRC Inactive state in this case; the signaling can be configured in the RRC release message, or configured in a certain logical channel, such as logical channel# 2 in.
  • the network side configures a DRB when the UE is released to the RRC Inactive state.
  • the DRB is used to carry small data, that is Only when the DRB has data to be sent, the UE will send small data in the RRC Inactive state.
  • An embodiment of the present application also provides a data sending device in an inactive state.
  • the device includes: a receiving module 70 for receiving configuration information from a network side device, where the configuration information is used for Indicate whether at least one of the at least one logical channel of the user equipment and the data radio bearer DRB supports data transmission in the radio resource control RRC inactive state; the sending module 72 is configured to indicate that at least one logical channel supports the RRC inactive state when the configuration information indicates During data transmission, send the data to be sent on at least one logical channel; when the configuration information indicates that the DRB supports data transmission in the RRC inactive state, send the data to be sent on the logical channel associated with the DRB.
  • the configuration information is also used to indicate whether the user equipment supports RRC inactive data transmission; the sending module is also used to indicate that the user equipment does not support RRC inactive data transmission, and the user equipment has to be sent When data is being sent, the RRC recovery process is initiated, and when the user equipment is restored to the connected state, the data to be sent is sent.
  • the receiving module 70 is further configured to receive a radio resource control RRC reconfiguration message from the network side device, and obtain configuration information from the RRC reconfiguration message.
  • the receiving module 70 is further configured to receive an RRC release message from the network side device, where the RRC release message is used to release the user equipment from the RRC connected state to the RRC inactive state; and obtain the configuration from the RRC release message information.
  • the receiving module 70 is further configured to obtain indication information from the release message, where the indication information is used to indicate a DRB supporting RRC inactive data transmission or a logical channel associated with the DRB.
  • the apparatus further includes: a recovery module 80, configured to indicate that at least one logical channel does not support RRC inactive data transmission when the configuration information indicates that the user equipment has a DRB corresponding to the at least one logical channel.
  • a recovery module 80 configured to indicate that at least one logical channel does not support RRC inactive data transmission when the configuration information indicates that the user equipment has a DRB corresponding to the at least one logical channel.
  • the RRC recovery process is initiated; the sending module 72 is used to send the data to be sent when the user equipment is restored to the connected state.
  • the at least one logical channel is determined in the following manner: a logical channel with data to be sent is determined from a logical channel set of a cell where the user equipment is located, and the logical channel with data to be sent is used as the at least one logical channel.
  • the sending module 72 is further configured to determine whether the multiple logical channels support the RRC inactive state based on the configuration information corresponding to the multiple logical channels in the RRC inactive state. Data transmission; when multiple logical channels support RRC inactive data transmission, initiate RRC inactive data transmission.
  • the above-mentioned apparatus further includes: a judging module 82, configured to judge whether the first total data amount of the data to be sent of the multiple logical channels is less than a first threshold; the sending module 72 is also configured to When the total data amount is less than the first threshold, the data transmission in the inactive state is initiated; when the first total data amount is greater than the first threshold, the RRC recovery procedure is initiated.
  • a judging module 82 configured to judge whether the first total data amount of the data to be sent of the multiple logical channels is less than a first threshold
  • the sending module 72 is also configured to When the total data amount is less than the first threshold, the data transmission in the inactive state is initiated; when the first total data amount is greater than the first threshold, the RRC recovery procedure is initiated.
  • the device further includes: a determining module 84, configured to have multiple at least one logical channel, and some of the multiple logical channels support RRC inactive data transmission, and the remaining logical channels When the channel does not support data transmission in the RRC inactive state, determine the second total data volume of the data to be sent in the multiple logical channels; the sending module 72 is also configured to increase the second total data volume when the second total data volume is not greater than the second threshold.
  • the data to be sent in the two logical channels are multiplexed, and data transmission in the RRC inactive state is initiated.
  • the sending module 72 is configured to have multiple at least one logical channel, and some of the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive data transmission At this time, the default is to restore to the RRC connected state through the RRC recovery process to initiate data transmission.
  • the receiving module 70 is further configured to have multiple at least one logical channel, and some of the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive data.
  • control signaling from the network side device is received, where the control signaling is used to indicate that some of the logical channels in the multiple logical channels support RRC inactive data transmission, and the remaining logical channels do not support RRC inactive state During data transmission, whether to support data transmission in the RRC inactive state.
  • the embodiment of the present application provides a method for receiving data in an inactive state. As shown in FIG. 9, the method includes:
  • Step S902 The network side device sends configuration information to the user equipment, where the configuration information is used to indicate whether at least one of the at least one logical channel of the user equipment and the data radio bearer DRB supports data transmission in the RRC inactive state. ;
  • Step S904 When the configuration information indicates that at least one logical channel supports RRC inactive data transmission, the network side device receives the data to be sent of the at least one logical channel or the data to be sent on the logical channel associated with the DRB from the user equipment.
  • the network-side device may receive the above-mentioned configuration information in the following ways: 1) The network-side device sends an RRC reconfiguration message to the user equipment, where the RRC reconfiguration message carries configuration information; 2) the network The side device sends an RRC release message to the user equipment, where the RRC release message is used to release the user equipment from the RRC connected state to the RRC inactive state, and the RRC release message carries configuration information.
  • the above-mentioned configuration information includes: indication information, which is used to indicate a DRB that supports data transmission in an RRC inactive state or a logical channel associated with the DRB.
  • An embodiment of the present application also provides a data receiving device in an inactive state.
  • the device is used to implement the method shown in FIG. 9. As shown in FIG. 10, the device includes:
  • the sending module 100 is configured to send configuration information to the user equipment, where the configuration information is used to indicate whether at least one of the at least one logical channel of the user equipment and the data radio bearer DRB supports data transmission in the RRC inactive state. ;
  • the receiving module 102 is configured to receive data to be sent of at least one logical channel or data to be sent on the logical channel associated with the DRB from the user equipment when the configuration information indicates that at least one logical channel supports RRC inactive data transmission
  • the sending module 100 is further configured to send an RRC reconfiguration message to the user equipment, where the RRC reconfiguration optionally, the sending module is further configured to send an RRC release message to the user equipment, where the RRC release message is used To release the user equipment from the RRC connected state to the RRC inactive state, the RRC release message carries configuration information.
  • the configuration information includes: indication information used to indicate a DRB that supports data transmission in an RRC inactive state or a logical channel associated with the DRB.
  • the embodiment of the present application provides a non-volatile storage medium, the storage medium is used to store a program, and when the program runs in the device where the non-volatile storage medium is located, the above-mentioned data transmission in the inactive state is executed. Method, or the data receiving method in the inactive state as described above.
  • a processor is provided, which is configured to run a program stored in a memory, and the program is used to execute the above-mentioned data sending method in an inactive state, or inactive The data receiving method in the state.
  • the disclosed technical content can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units may be a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or may be Integrate 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, units or modules, and may be in electrical 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 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 above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit 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 all or 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 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 method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes. .

Landscapes

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

Abstract

本申请公开了一种非激活态下的数据发送、接收方法及装置、用户设备。其中，该方法包括：用户设备接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，用户设备发送至少一个逻辑信道的待发送数据；在配置信息指示DRB支持RRC非激活态的数据传输时，发送与DRB关联的逻辑信道上的待发送数据。本申请解决了相关技术中UE不支持Inactive状态下的数据传输的技术问题。

Description

非激活态下的数据发送、接收方法及装置、用户设备 技术领域
本申请涉及通信领域，具体而言，涉及一种非激活态下的数据发送、接收方法及装置、用户设备。
背景技术
在新无线(New Radio，简称为NR)场景中，在无线资源控制(Radio Resource Control，简称为RRC)非激活(Inactive)状态下是不支持数据传输的。由于业务场景更加多样，不同的业务对于在不同的数据无线承载(Data Radio Bearer，简称为DRB)配置(即不同的DRB用于传输不同QoS要求的业务类型)。有些类型的业务，数据到达并不规律，到达的数据包大小差异也比较大，并不适合于非激活态(inactive)的数据传输模式。另外一些业务类型，比如心跳包，或者一些健康监测数据，数据包的大小普遍比较小，因此更加适合在inactive状态下传输。
但是，相关技术中，用户设备(User Equipment，简称为UE)是不支持Inactive状态下的数据传输的。
针对上述的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种非激活态下的数据发送、接收方法及装置、用户设备，以至少解决相关技术中UE不支持Inactive状态下的数据传输的技术问题。
根据本申请实施例的一个方面，提供了一种非激活态下的数据发送方法，包括：用户设备接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制(Radio Resource Control，简称为RRC)非激活态的数据传输；在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输 时，用户设备发送至少一个逻辑信道的待发送数据；在配置信息指示DRB支持RRC非激活态的数据传输时，发送与DRB关联的逻辑信道上的待发送数据。
可选地，配置信息还用于指示用户设备是否支持RRC非激活态的数据传输；上述方法还包括：在配置信息指示用户设备不支持RRC非激活态的数据传输，且用户设备存在待发送数据时，用户设备发起RRC恢复流程，并在用户设备恢复到连接态时，发送待发送数据。
可选地，用户设备接收来自网络侧设备的配置信息，包括：用户设备接收来自网络侧设备的无线资源控制RRC重配置消息，从RRC重配置消息中获取配置信息。
可选地，用户设备接收来自网络侧设备的配置信息，包括：用户设备接收来自网络侧设备的RRC释放消息，其中，该RRC释放消息用于将用户设备从RRC连接态释放到RRC非激活态；从RRC释放消息中获取配置信息。
可选地，从RRC释放消息中获取配置信息，包括：从释放消息获取指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
可选地，方法还包括：在配置信息指示至少一个逻辑信道不支持RRC非激活态的数据传输，且用户设备对于至少一个逻辑信道对应的DRB存在待发送数据时，用户设备发起RRC恢复流程，并在用户设备恢复到连接态时，发送待发送数据。
可选地，至少一个逻辑信道通过以下方式确定：用户设备从用户设备的逻辑信道集合中确定存在待发送数据的逻辑信道，并将存在待发送数据的逻辑信道作为至少一个逻辑信道。
可选地，至少一个逻辑信道为多个；用户设备发送至少一个逻辑信道的待发送数据包括：在RRC非激活状态下，用户设备基于多个逻辑信道分别对应的配置信息，确定多个逻辑信道是否支持RRC非激活态的数据传输；在多个逻辑信道均支持RRC非激活态的数据传输时，用户设备发起RRC非激活态的数据传输。
可选地，用户设备发起RRC非激活态的数据传输之前，方法还包括：判断多个逻辑信道的待发送数据的第一总数据量是否小于第一阈值；如果第一总数据量小于第一阈值，则用户设备发起非激活态的数据传输；如果第一总数据量大于第一阈值，则用户设备发起RRC恢复流程。
可选地，方法还包括：在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，确定多个逻辑信道中待发送数据的第二总数据量；在第二总数据量不大于第二阈值时，用户设备将多个逻辑信道中的待发送数据进行复用，并发起RRC非激活态的数据传输。
可选地，在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，方法还包括：用户设备默认通过RRC恢复流程恢复到RRC连接态，以发起数据传输。
可选地，在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，方法还包括：用户设备接收来自网络侧设备的控制信令，其中，该控制信令用于指示在多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，是否支持在RRC非激活态进行数据传输。
根据本申请实施例的又一方面，提供了一种非激活态下的数据接收方法，包括：网络侧设备向用户设备发送配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，网络侧设备接收用户设备发送的至少一个逻辑信道的待发送数据或者DRB关联的逻辑信道上的待发送数据。
可选地，网络侧设备向用户设备发送配置信息，包括：网络侧设备向用户设备发送RRC重配置消息，其中，RRC重配置消息中携带有配置信息。
可选地，网络侧设备向用户设备发送配置信息，包括：网络侧设备向用户设备发送RRC释放消息，其中，该RRC释放消息用于将用户设备从RRC 连接态释放到RRC非激活态，RRC释放消息中携带有配置信息。
可选地，配置信息包括：指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
根据本申请实施例的又一方面，提供了一种非激活态下的数据发送装置，包括：接收模块，用于接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；发送模块，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，发送至少一个逻辑信道的待发送数据；在配置信息指示DRB支持RRC非激活态的数据传输时，发送与DRB关联的逻辑信道上的待发送数据。
可选地，配置信息还用于指示用户设备是否支持RRC非激活态的数据传输；发送模块，还用于在配置信息指示用户设备不支持RRC非激活态的数据传输，且用户设备存在待发送数据时，发起RRC恢复流程，并在用户设备恢复到连接态时，发送待发送数据。
可选地，接收模块，还用于接收来自网络侧设备的无线资源控制RRC重配置消息，从RRC重配置消息中获取配置信息。
可选地，接收模块，还用于接收来自网络侧设备的RRC释放消息，其中，该RRC释放消息用于将用户设备从RRC连接态释放到RRC非激活态；从RRC释放消息中获取配置信息。
可选地，接收模块，还用于从释放消息获取指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
可选地，装置还包括：恢复模块，用于在配置信息指示至少一个逻辑信道不支持RRC非激活态的数据传输，且用户设备对于至少一个逻辑信道对应的DRB存在待发送数据时，发起RRC恢复流程；发送模块，用于在用户设备恢复到连接态时，发送待发送数据。
可选地，至少一个逻辑信道通过以下方式确定：从用户设备所在小区的逻辑信道集合中确定存在待发送数据的逻辑信道，并将存在待发送数据的逻辑信道作为至少一个逻辑信道。
可选地，至少一个逻辑信道为多个；发送模块，还用于在RRC非激活状态下，用户设备基于多个逻辑信道分别对应的配置信息，确定多个逻辑信道是否支持RRC非激活态的数据传输；在多个逻辑信道均支持RRC非激活态的数据传输时，发起RRC非激活态的数据传输。
可选地，装置还包括：判断模块，用于判断多个逻辑信道的待发送数据的第一总数据量是否小于第一阈值；发送模块，还用于在总数据量小于第一阈值时，发起非激活态的数据传输；在第一总数据量大于第一阈值时，发起RRC恢复流程。
可选地，装置还包括：确定模块，用于在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，确定多个逻辑信道中待发送数据的第二总数据量；发送模块，还用于在第二总数据量不大于第二阈值时，将多个逻辑信道中的待发送数据进行复用，并发起RRC非激活态的数据传输。
可选地，发送模块，用于在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，默认通过RRC恢复流程恢复到RRC连接态，以发起数据传输。
可选地，接收模块，还用于在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，接收来自网络侧设备的控制信令，其中，该控制信令用于指示在多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，是否支持在RRC非激活态进行数据传输。
根据本申请实施例的再一方面，提供了一种非激活态下的数据接收装置，包括：发送模块，用于向用户设备发送配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；接收模块，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，接收用户设备 发送的至少一个逻辑信道的待发送数据或者DRB关联的逻辑信道上的待发送数据。
可选地，发送模块，还用于向用户设备发送RRC重配置消息，其中，RRC重配可选地，发送模块，还用于向用户设备发送RRC释放消息，其中，该RRC释放消息用于将用户设备从RRC连接态释放到RRC非激活态，RRC释放消息中携带有配置信息。
可选地，配置信息包括：指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
根据本申请实施例的再一方面，提供了一种用户设备，包括：收发电路，用于接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；处理器，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，发送至少一个逻辑信道的待发送数据；在配置信息指示DRB支持RRC非激活态的数据传输时，通知收发电路发送与DRB关联的逻辑信道上的待发送数据。
根据本申请实施例的再一方面，提供了一种网络侧设备，包括：处理器，用于确定向用户设备发送的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；收发电路，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，接收用户设备发送的至少一个逻辑信道的待发送数据或者DRB关联的逻辑信道上的待发送数据。
根据本申请实施例的再一方面，提供了一种非易失性存储介质，该非易失性存储介质用于存储程序，该程序在非易失性存储介质所在的设备中运行时，执行以上所述的非激活态下的数据发送方法。
根据本申请实施例的再一方面，提供了一种处理器，处理器用于运行存储在存储器中的程序，该程序用于执行以上所述的非激活态下的数据发送方法。
在本申请实施例中，采用用户设备基于网络侧设备的配置信息来确定 UE的逻辑信道和/或DRB是否支持小数据传输的方式，由于逻辑信道往往是与不同业务类型关联的，因此，采用本申请实施例中的方案可以使得UE依据网络配置决定是否可以采用小数据传输的方式传输相应的业务数据，进而解决了相关技术中UE不支持Inactive状态下的数据传输技术问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据相关技术的一种控制面早期数据传输(CP-EDT)数据的传输流程示意图；
图2是根据相关技术的一种用户面数据传输(UP-EDT)数据的传输流程示意图；
图3是根据本申请实施例的一种通信系统的结构示意图；
图4是根据本申请实施例的一种用户设备的结构示意图；
图5是根据本申请实施例的一种网络侧设备的结构示意图；
图6是根据本申请实施例的一种非激活态下的数据发送方法的流程图；
图7是根据本申请实施例的一种非激活态下的数据发送装置的结构图；
图8是根据本申请实施例的另一种可选的非激活态下的数据发送装置的结构图；
图9是根据本申请实施例的一种非激活态下的数据接收方法的流程图；
图10是根据本申请实施例的一种非激活态下的数据接收装置的结构图。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显 然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
为便于理解本申请实施例，以下将本申请实施例中涉及的一些技术内容描述如下：
3GPP R17的其中一个项目是关于小数据传输优化(RP-193252)，其中提出了需要支持UE在RRC Inactive状态下的小数据传输，主要目的是为了省电和节省信令开销，具体的项目目标包括：
1)基于随机接入信道(Random Access Channel，简称为RACH)的小数据传输优化，其中包括4-step RACH流程和2-step RACH流程；
2)基于type1 configured grant的小数据传输优化，也就是说需要在RRC Inactive状态支持Type1 CG传输。
NR协议中关于不同RRC状态及状态之间的转换：
5G网络环境中为了降低空口信令和快速恢复无线连接，快速恢复数据业务的目的，定义了一个新的RRC状态，即RRC_INACTIVE状态。这种状态有别于RRC_IDLE和RRC_ACTIVE状态。其中：
RRC_IDLE：移动性基于小区选择重选，寻呼由核心网(Core network，简称为CN)发起，寻呼区域由CN配置。基站侧不存在UE接入层(Access Stratum，简称为AS)Context，不存在RRC连接。
RRC_INACTIVE：移动性基于小区选择重选，该状态下存在CN-NR之 间的连接，UE AS Context存在某个基站上，寻呼由无线接入网(Radio Access Network，简称为RAN)触发，基于RAN的寻呼区域由RAN管理，网络侧知道UE的位置是基于RAN的寻呼区域级别的。
RRC_CONNECTED：存在RRC连接，基站和UE存在UE AS Context。网络侧知道UE的位置是具体小区级别的，移动性是网络侧控制的移动性，UE和基站之间可以传输单播数据。
网络侧可以控制UE在不同状态之间的切换，RRC Inactive状态下的一些UE侧RRC参数是通过RRC Release消息配置的其中I-RNTI用于标识UE在基站侧的UE inactive上下文，在基站内唯一。RNA(RAN Notification area)用于控制UE在inactive状态下进行小区选择重选的区域，也是RAN初始的寻呼的寻呼范围区域。RAN Paging cycle用于计算RAN初始寻呼的寻呼时机。NCC用于RRC连接恢复过程中使用的秘钥。
当UE在RNA区域内移动时不用通知网络侧，遵循空闲(idle)状态下移动性行为，即小区选择重选原则。当UE移动出RAN配置的寻呼区域时，UE触发恢复RRC连接流程，即RRC恢复程序(resume procedure)，并重新获取RAN配置的寻呼区域。当网络侧需要给该UE传输数据时，即有下行数据到达时，保存UE context的gNB会触发RAN寻呼区域内的所有小区发送寻呼消息给UE，使得INACTIVCE状态的UE能够恢复RRC连接，进行数据接收。另外，处于Inactive状态的UE，配置了RAN寻呼区域，在该区域内为了保证UE的可达性，UE需要按照网络配置的周期进行周期性位置更新。触发UE执行RNA更新的场景有基于RNA的通知区域更新(RAN Notification Area Update，简称为RNAU)定时器超时或者UE移动到RNA之外的区域。目前，NR定义的RRC Inactive状态是不支持UE传输用户面数据的。
LTE中IDLE态传输小数据优化：
LTE中定义了小数据传输的流程，也就是EDT(Early Data Transmission)，主要面向NB-IoT UE和Emtc UE。当终端发起的数据到达时，且该数据小于系统广播的一个数据门限时，UE可以基于RACH触发EDT。EDT主要包括用户面的EDT(UP-EDT)以及控制面的EDT (CP-EDT)。
其中，如图1所示，CP-EDT数据主要是通过NAS消息中传输；如图2所示，UP-EDT数据主要是将用户面数据复用在RRC消息一起传输。
在LTE协议中，对于EDT机制，网络侧在系统广播消息中广播一个该小区能够支持的最大小数据传输的大小。当UE有数据传输时，如果该待传数据的大小小于该广播的最大支持的数据大小，则UE发起EDT流程。但是，在NR场景中，由于业务场景的多样性，不同的业务体现在不同的DRB配置(不同的DRB用于传输不同QoS要求的业务类型)。有些类型的业务，数据到达并不规律，到达的数据包大小差异也比较大，并不适合于非激活态的小数据传输模式。另外一些业务类型，比如心跳包，或者一些健康监测数据，数据包的大小普遍比较小，因此更加适合在inactive状态下传输。但是，目前NR场景中，并不支持inactive状态下的数据传输。
为解决上述技术问题，本申请实施例提供了相应的解决方案，UE接收网络配置消息，该配置消息可以配置不同的DRB是否支持小数据传输；UE根据不同DRB的参数配置，来决定在RRC Inactive状态是否发起小数据传输；当处于RRC Inactive状态的UE的某一个逻辑信道存在待发送数据时，UE判断DRB是否支持RRC Inactive状态的小数据传输，即是否配置了一个指示参数。如果该逻辑信道支持小数据传输，则UE在RRC Inactive状态发起小数据传输。如果存在待发送数据的DRB不支持小数据传输，则UE发起RRC Resume流程，当网络将UE恢复到连接态，则UE可以直接发送该数据。网络配置消息可以是连接态的RRC重配置消息，也可以是RRC release消息。DRB的参数配置可以是与其关联的逻辑信道的配置。以下结合实施例详细说明。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(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)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工 (Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本申请实施例应用的通信系统300如图3所示。该通信系统300可以包括网络设备310，网络设备310可以是与用户设备320(或称为通信终端、终端)通信的设备。网络设备310可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的用户设备进行通信。可选地，该网络设备310可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统300还包括位于网络设备310覆盖范围内的至少一个用户设备320。作为在此使用的“用户设备”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一用户设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的用户设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。用户设备可以指接 入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的用户设备或者未来演进的PLMN中的用户设备等。
可选地，用户设备320之间可以进行设备到设备(Device to Device，D2D)通信。
可选地，5G系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图3示例性地示出了一个网络设备和两个用户设备，可选地，该通信系统300可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的用户设备，本申请实施例对此不做限定。
可选地，该通信系统300还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统300为例，通信设备可包括具有通信功能的网络设备310和用户设备320，网络设备310和用户设备320可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统300中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
如图4所示，本申请实施例中提供的用户设备320包括但不限于：收发电路400，用于接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；处理器402，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，发送至少一个逻辑信道的待发送数据；在配置信息指示DRB支持RRC非激活态的数据传输时，通知收发电路400发送与DRB关联的逻辑信道上的待发送数据。用户设备还可以包括存储器404等硬件组件。
如图5所示，本申请实施例中提供的网络侧设备310，包括：处理器500，用于确定向用户设备发送的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；收发电路502，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，接收用户设备发送的至少一个逻辑信道的待发送数据或者DRB关联的逻辑信道上的待发送数据。还可以包括存储器504等硬件组件。
在上述运行环境下，本申请实施例提供了一种非激活态下的数据传输方法的方法实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图6是根据本申请实施例的非激活态下的数据发送方法，如图1所示，该方法包括如下步骤：
步骤S602，用户设备接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和DRB中的至少之一是否支持RRC非激活态的数据传输；
步骤S604，在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，用户设备发送至少一个逻辑信道的待发送数据；在配置信息指示DRB支持RRC非激活态的数据传输时，发送与DRB关联的逻辑信道上的待发送数据。
在本申请的一些实施例中，配置信息还用于指示用户设备是否支持RRC非激活态的数据传输；此时，在配置信息指示用户设备不支持RRC非激活态的数据传输，且用户设备存在待发送数据时，用户设备发起RRC恢复流程，并在用户设备恢复到连接态时，发送待发送数据。
在本申请实施例中，用户设备可以两种情况确定是否支持RRC Inactive态下的数据传输：1)基于连接态逻辑信道配置判断是否需要在RRC Inactive态下进行数据传输；2)基于RRC release消息配置小数据传输DRB。
其中，对于第1)种情况，用户设备接收来自网络侧设备的RRC重配置消息，从RRC重配置消息中获取配置信息。
对于第2)种情况，：用户设备接收来自网络侧设备的RRC释放消息，其中，该RRC释放消息用于将用户设备从RRC连接态释放到RRC非激活态；从RRC释放消息中获取配置信息。其中，从释放消息获取指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
在配置信息指示至少一个逻辑信道不支持RRC非激活态的数据传输，且用户设备对于至少一个逻辑信道对应的DRB存在待发送数据时，用户设备发起RRC恢复流程，并在用户设备恢复到连接态时，发送待发送数据。
在本申请的一些实施例中，上述至少一个逻辑信道通过以下方式确定：用户设备从用户设备的逻辑信道集合中确定存在待发送数据的逻辑信道，并将存在待发送数据的逻辑信道作为至少一个逻辑信道。
在至少一个逻辑信道为多个时，在RRC非激活状态下，用户设备基于多个逻辑信道分别对应的配置信息，确定多个逻辑信道是否支持RRC非激活态的数据传输；在多个逻辑信道均支持RRC非激活态的数据传输时，用户设备发起RRC非激活态的数据传输。
其中，为了保证通信过程的可靠性，在用户设备发起RRC非激活态的数据传输之前，判断多个逻辑信道的待发送数据的第一总数据量是否小于第一阈值；如果第一总数据量小于第一阈值，则用户设备发起非激活态的数据传输；如果第一总数据量大于第一阈值，则用户设备发起RRC恢复流程。
在本申请的另一些实施例中，在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，确定多个逻辑信道中待发送数据的第二总数据量；在第二总数据量不大于第二阈值时，用户设备将多个逻辑信道中的待发送数据进行复用，并发起RRC非激活态的数据传输。
可选地，在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，用户设备默认通过RRC恢复流程恢复到RRC连接态，以发起数据传输。
可选地，在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，用户设备接收来自网络侧设备的控制信令，其中，该控制信令用于指示在多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，是否支持在RRC非激活态进行数据传输。上述控制信令可以配置在RRC release消息里面，或者配置在某一个逻辑信道中。
以下结合具体的逻辑信道对上述第1)种情况和第2)种情况进行说明。
其中，对于第1)种情况，即基于连接态逻辑信道配置判断是否需要在RRC Inactive进行小数据传输
UE基于网络配置有不同的DRB，不同的DRB分别关联不同的逻辑信道；不同的逻辑信道里面分别配置一个参数，用来表征该逻辑信道的数据是否可以允许在RRC Inactive状态传输，例如：
逻辑信道#1 可以在RRC Inactive状态传输
逻辑信道#2 不可以在RRC Inactive状态传输
逻辑信道#3 可以在RRC Inactive状态传输
处于RRC Inactive状态的UE在存在待发送数据时，先判断该待发送数据对应的逻辑信道的配置参数，即是否该逻辑信道的数据允许在RRC Inactive状态发送。
如果逻辑信道#1，或者逻辑信道#3，或者逻辑信道#1和逻辑信道#2存在待发送数据，则UE基于RRC Inactive态的配置发起小数据传输。
如果逻辑信道#2存在待发送数据，则UE发起RRC resume流程，即恢复到RRC连接态发起数据传输。
其中，上述逻辑信道的一种配置方式如下：配置一个“Boolean”参数来指示该逻辑信道是否可以允许在RRC Inactive状态下传输。
如果逻辑信道#1和逻辑信道#2都存在待发送数据，即同时存在“可以在RRC Inactive状态传输”和“不可以在RRC Inactive状态传输”的情况，UE可以基于如下方式来决定是否需要在RRC Inactive状态发送数据：
逻辑信道#1和逻辑信道#2的数据总大小不超过该小区指示的最大的小数据大小，则UE将该逻辑信道#1和逻辑信道#2的数据进行复用，以在RRC Inactive状态传输。或者，UE默认在这种情况下通过RRC resume流程，即恢复到RRC连接态发起数据传输；
其中，网络侧设备可以配置一个信令，来指示UE在这种情况下，是否可以在RRC Inactive状态下传输数据；该信令可以配置在RRC release消息里面，或者配置在某一个逻辑信道中，比如逻辑信道#2中。
基于网络侧对每个逻辑信道的配置，UE可以知道哪些逻辑信道存在待发送数据时，可以采用RRC Inactive状态下的小数据传输，也就是不用恢复到RRC连接态。
对于第2)种情况，即通过RRC release流程配置小数据传输DRB
UE收到网络侧的RRC Release消息，将该UE释放到RRC Inactive状态时，在该RRC Release消息中同时配置一个用于传输小数据的DRB，该DRB关联一个逻辑信道；比如：
逻辑信道#1 关联的DRB在RRC连接态配置
逻辑信道#2 关联的DRB在RRC连接态配置
逻辑信道#3 关联的DRB在RRC连接态配置
逻辑信道#4 关联的DRB在RRC release中配置
UE只有在逻辑信道#4存在待发送数据时，才可以在RRC Inactive状态发起小数据传输；
如果UE在被网络释放到RRC Inactive状态时，没有收到该DRB的配置，则该UE不支持在RRC Inactive状态下传输数据；
对于其他逻辑信道，如果存在待发送数据，UE发起RRC resume(恢复)流程，待恢复到RRC连接态时，再发起数据传输。
如果逻辑信道#3和逻辑信道#4都存在待发送数据，即同时存在“可以在RRC Inactive状态传输”和“不可以在RRC Inactive状态传输”的情况，UE可以基于如下方式来决定是否需要在RRC Inactive状态发送数据：
在逻辑信道#3和逻辑信道#4的数据总大小不超过该小区指示的最大的小数据大小时，UE将该逻辑信道#3和逻辑信道#4的数据复用起来在RRC Inactive状态传输。或者，
UE默认在这种情况下通过RRC resume流程，即恢复到RRC连接态发起数据传输；
网络可以配置一个信令，来指示UE在这种情况下，是否可以在RRC Inactive状态下传输数据；该信令可以配置在RRC release消息里面，或者配置在某一个逻辑信道中，比如逻辑信道#2中。
在第2)种情况下，网络侧不是配置每个逻辑信道是否可以在RRC Inactive状态下传输，而是在将该UE释放到RRC Inactive状态时配置一个DRB，该DRB用于承载小数据，即只有该DRB存在待发送数据时，UE才进行RRC Inactive状态下的小数据发送。
本申请实施例还提供了一种非激活态下的数据发送装置，如图7所示，该装置包括：接收模块70，用于接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；发送模块72，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输 时，发送至少一个逻辑信道的待发送数据；在配置信息指示DRB支持RRC非激活态的数据传输时，发送与DRB关联的逻辑信道上的待发送数据。
可选地，配置信息还用于指示用户设备是否支持RRC非激活态的数据传输；发送模块，还用于在配置信息指示用户设备不支持RRC非激活态的数据传输，且用户设备存在待发送数据时，发起RRC恢复流程，并在用户设备恢复到连接态时，发送待发送数据。
可选地，接收模块70，还用于接收来自网络侧设备的无线资源控制RRC重配置消息，从RRC重配置消息中获取配置信息。
可选地，接收模块70，还用于接收来自网络侧设备的RRC释放消息，其中，该RRC释放消息用于将用户设备从RRC连接态释放到RRC非激活态；从RRC释放消息中获取配置信息。
可选地，接收模块70，还用于从释放消息获取指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
可选地，如图8所示，装置还包括：恢复模块80，用于在配置信息指示至少一个逻辑信道不支持RRC非激活态的数据传输，且用户设备对于至少一个逻辑信道对应的DRB存在待发送数据时，发起RRC恢复流程；发送模块72，用于在用户设备恢复到连接态时，发送待发送数据。
可选地，至少一个逻辑信道通过以下方式确定：从用户设备所在小区的逻辑信道集合中确定存在待发送数据的逻辑信道，并将存在待发送数据的逻辑信道作为至少一个逻辑信道。
可选地，至少一个逻辑信道为多个；发送模块72，还用于在RRC非激活状态下，用户设备基于多个逻辑信道分别对应的配置信息，确定多个逻辑信道是否支持RRC非激活态的数据传输；在多个逻辑信道均支持RRC非激活态的数据传输时，发起RRC非激活态的数据传输。
可选地，如图8所示，上述装置还包括：判断模块82，用于判断多个逻辑信道的待发送数据的第一总数据量是否小于第一阈值；发送模块72，还用于在总数据量小于第一阈值时，发起非激活态的数据传输；在第一总数据 量大于第一阈值时，发起RRC恢复流程。
可选地，如图8所示，装置还包括：确定模块84，用于在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，确定多个逻辑信道中待发送数据的第二总数据量；发送模块72，还用于在第二总数据量不大于第二阈值时，将多个逻辑信道中的待发送数据进行复用，并发起RRC非激活态的数据传输。
可选地，发送模块72，用于在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，默认通过RRC恢复流程恢复到RRC连接态，以发起数据传输。
可选地，接收模块70，还用于在至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，接收来自网络侧设备的控制信令，其中，该控制信令用于指示在多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，是否支持在RRC非激活态进行数据传输。
本申请实施例提供了一种非激活态下的数据接收方法，如图9所示，该方法包括：
步骤S902，网络侧设备向用户设备发送配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；
步骤S904，在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，网络侧设备接收用户设备发送的至少一个逻辑信道的待发送数据或者DRB关联的逻辑信道上的待发送数据。
在本申请的一些实施例中，网络侧设备可以通过以下方式接收上述配置信息：1)网络侧设备向用户设备发送RRC重配置消息，其中，RRC重配置消息中携带有配置信息；2)网络侧设备向用户设备发送RRC释放消息，其 中，该RRC释放消息用于将用户设备从RRC连接态释放到RRC非激活态，RRC释放消息中携带有配置信息。
其中，上述配置信息包括：指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
本申请实施例还提供了一种非激活态下的数据接收装置，该装置用于实现图9所示的方法，如图10所示，该装置包括：
发送模块100，用于向用户设备发送配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；
接收模块102，用于在配置信息指示至少一个逻辑信道支持RRC非激活态的数据传输时，接收用户设备发送的至少一个逻辑信道的待发送数据或者DRB关联的逻辑信道上的待发送数据
可选地，发送模块100，还用于向用户设备发送RRC重配置消息，其中，RRC重配可选地，发送模块，还用于向用户设备发送RRC释放消息，其中，该RRC释放消息用于将用户设备从RRC连接态释放到RRC非激活态，RRC释放消息中携带有配置信息。
可选地，配置信息包括：指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与DRB关联的逻辑信道。
本申请实施例提供了一种非易失性存储介质，存储介质用于存储程序，该程序在非易失性存储介质所在的设备中运行时，执行以上所述的非激活态下的数据发送方法，或者，以上所述的非激活态下的数据接收方法。
根据本申请实施例的再一方面，提供了一种处理器，处理器用于运行存储在存储器中的程序，该程序用于执行以上所述的非激活态下的数据发送方法，或者，非激活态下的数据接收方法。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
在本申请的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，可以为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅是本申请的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。

Claims (36)

  1. 一种非激活态下的数据发送方法，包括：
    用户设备接收来自网络侧设备的配置信息，其中，该配置信息用于指示所述用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；
    在所述配置信息指示所述至少一个逻辑信道支持RRC非激活态的数据传输时，所述用户设备发送所述至少一个逻辑信道的待发送数据；在所述配置信息指示所述DRB支持RRC非激活态的数据传输时，发送与所述DRB关联的逻辑信道上的待发送数据。
  2. 根据权利要求1所述的方法，其中，所述配置信息还用于指示所述用户设备是否支持所述RRC非激活态的数据传输；所述方法还包括：
    在所述配置信息指示所述用户设备不支持RRC非激活态的数据传输，且所述用户设备存在待发送数据时，所述用户设备发起RRC恢复流程，并在所述用户设备恢复到连接态时，发送所述待发送数据。
  3. 根据权利要求1所述的方法，其中，用户设备接收来自网络侧设备的配置信息，包括：
    所述用户设备接收来自网络侧设备的无线资源控制RRC重配置消息，从所述RRC重配置消息中获取所述配置信息。
  4. 根据权利要求1所述的方法，其中，用户设备接收来自网络侧设备的配置信息，包括：
    所述用户设备接收来自所述网络侧设备的RRC释放消息，其中，该RRC释放消息用于将所述用户设备从RRC连接态释放到RRC非激活态；从所述RRC释放消息中获取所述配置信息。
  5. 根据权利要求4所述的方法，其中，从所述RRC释放消息中获取所述配置信息，包括：
    从所述释放消息获取指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与所述DRB关联的逻辑信道。
  6. 根据权利要求1所述的方法，其中，所述方法还包括：
    在所述配置信息指示所述至少一个逻辑信道不支持RRC非激活态的数据传输，且所述用户设备对于所述至少一个逻辑信道对应的DRB存在待发送数据时，所述用户设备发起RRC恢复流程，并在所述用户设备恢复到连接态时，发送所述待发送数据。
  7. 根据权利要求1所述的方法，其中，所述至少一个逻辑信道通过以下方式确定：
    所述用户设备从所述用户设备的逻辑信道集合中确定存在待发送数据的逻辑信道，并将所述存在待发送数据的逻辑信道作为所述至少一个逻辑信道。
  8. 根据权利要求7所述的方法，其中，所述至少一个逻辑信道为多个；所述用户设备发送所述至少一个逻辑信道的待发送数据包括：
    在RRC非激活状态下，所述用户设备基于多个逻辑信道分别对应的所述配置信息，确定所述多个逻辑信道是否支持RRC非激活态的数据传输；
    在所述多个逻辑信道均支持RRC非激活态的数据传输时，所述用户设备发起RRC非激活态的数据传输。
  9. 根据权利要求8所述的方法，其中，所述用户设备发起RRC非激活态的数据传输之前，所述方法还包括：
    判断所述多个逻辑信道的待发送数据的第一总数据量是否小于第一阈值；如果所述第一总数据量小于所述第一阈值，则所述用户设备发起非激活态的数据传输；如果所述第一总数据量大于所述第一阈值，则所述用户设备发起RRC恢复流程。
  10. 根据权利要求7所述的方法，其中，所述方法还包括：
    在所述至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，确定所述多个逻辑信道中待发送数据的第二总数据量；
    在所述第二总数据量不大于第二阈值时，所述用户设备将所述多个逻辑信道中的待发送数据进行复用，并发起RRC非激活态的数据传输。
  11. 根据权利要求7所述的方法，其中，在所述至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，所述方法还包括：
    所述用户设备默认通过RRC恢复流程恢复到RRC连接态，以发起数据传输。
  12. 根据权利要求7所述的方法，其中，在所述至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，所述方法还包括：
    所述用户设备接收来自所述网络侧设备的控制信令，其中，该控制信令用于指示在所述多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，是否支持在RRC非激活态进行数据传输。
  13. 一种非激活态下的数据接收方法，包括：
    网络侧设备向用户设备发送配置信息，其中，该配置信息用于指示所述用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；
    在所述配置信息指示所述至少一个逻辑信道支持RRC非激活态的数据传输时，所述网络侧设备接收所述用户设备发送的至少一个逻辑信道的待发送数据或者所述DRB关联的逻辑信道上的待发送数据。
  14. 根据权利要求13所述的方法，其中，网络侧设备向用户设备发送配置信息，包括：
    所述网络侧设备向所述用户设备发送RRC重配置消息，其中，所述RRC重配置消息中携带有所述配置信息。
  15. 根据权利要求13所述的方法，其中，网络侧设备向用户设备发送配置信息，包括：
    网络侧设备向所述用户设备发送RRC释放消息，其中，该RRC释放消息用于将所述用户设备从RRC连接态释放到RRC非激活态，所述RRC释放消息中携带有所述配置信息。
  16. 根据权利要求15所述的方法，其中，所述配置信息包括：指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与所述DRB关联的逻辑信道。
  17. 一种非激活态下的数据发送装置，包括：
    接收模块，用于接收来自网络侧设备的配置信息，其中，该配置信息用于指示用户设备的至少一个逻辑信道和数据无线承载DRB中的至少 之一是否支持无线资源控制RRC非激活态的数据传输；
    发送模块，用于在所述配置信息指示所述至少一个逻辑信道支持RRC非激活态的数据传输时，发送所述至少一个逻辑信道的待发送数据；在所述配置信息指示所述DRB支持RRC非激活态的数据传输时，发送与所述DRB关联的逻辑信道上的待发送数据。
  18. 根据权利要求17所述的装置，其中，所述配置信息还用于指示所述用户设备是否支持所述RRC非激活态的数据传输；所述发送模块，还用于在所述配置信息指示所述用户设备不支持RRC非激活态的数据传输，且所述用户设备存在待发送数据时，发起RRC恢复流程，并在所述用户设备恢复到连接态时，发送所述待发送数据。
  19. 根据权利要求17所述的装置，其中，所述接收模块，还用于接收来自网络侧设备的无线资源控制RRC重配置消息，从所述RRC重配置消息中获取所述配置信息。
  20. 根据权利要求17所述的装置，其中，所述接收模块，还用于接收来自所述网络侧设备的RRC释放消息，其中，该RRC释放消息用于将所述用户设备从RRC连接态释放到RRC非激活态；从所述RRC释放消息中获取所述配置信息。
  21. 根据权利要求20所述的装置，其中，
    所述接收模块，还用于从所述释放消息获取指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与所述DRB关联的逻辑信道。
  22. 根据权利要求17所述的装置，其中，
    所述装置还包括：恢复模块，用于在所述配置信息指示所述至少一个逻辑信道不支持RRC非激活态的数据传输，且所述用户设备对于所述至少一个逻辑信道对应的DRB存在待发送数据时，发起RRC恢复流程；
    所述发送模块，用于在所述用户设备恢复到连接态时，发送所述待发送数据。
  23. 根据权利要求17所述的装置，其中，所述至少一个逻辑信道通过以下方式确定：
    从所述用户设备所在小区的逻辑信道集合中确定存在待发送数据的逻辑信道，并将所述存在待发送数据的逻辑信道作为所述至少一个逻辑 信道。
  24. 根据权利要求23所述的装置，其中，所述至少一个逻辑信道为多个；所述发送模块，还用于在RRC非激活状态下，基于多个逻辑信道分别对应的所述配置信息，确定所述多个逻辑信道是否支持RRC非激活态的数据传输；在所述多个逻辑信道均支持RRC非激活态的数据传输时，发起RRC非激活态的数据传输。
  25. 根据权利要求24所述的装置，其中，
    所述装置还包括：判断模块，用于判断所述多个逻辑信道的待发送数据的第一总数据量是否小于第一阈值；
    所述发送模块，还用于在所述总数据量小于所述第一阈值时，发起非激活态的数据传输；在所述第一总数据量大于所述第一阈值时，发起RRC恢复流程。
  26. 根据权利要求23所述的装置，其中，
    所述装置还包括：确定模块，用于在所述至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，确定所述多个逻辑信道中待发送数据的第二总数据量；
    所述发送模块，还用于在所述第二总数据量不大于第二阈值时，将所述多个逻辑信道中的待发送数据进行复用，并发起RRC非激活态的数据传输。
  27. 根据权利要求23所述的装置，其中，所述发送模块，用于在所述至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，默认通过RRC恢复流程恢复到RRC连接态，以发起数据传输。
  28. 根据权利要求17所述的装置，其中，所述接收模块，还用于在所述至少一个逻辑信道为多个，且多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，接收来自所述网络侧设备的控制信令，其中，该控制信令用于指示在所述多个逻辑信道中的部分逻辑信道支持RRC非激活态的数据传输，其余逻辑信道不支持RRC非激活态的数据传输时，是否支持在RRC非激活态进行数据传输。
  29. 一种非激活态下的数据接收装置，包括：
    发送模块，用于向用户设备发送配置信息，其中，该配置信息用于指示所述用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；
    接收模块，用于在所述配置信息指示所述至少一个逻辑信道支持RRC非激活态的数据传输时，接收所述用户设备发送的至少一个逻辑信道的待发送数据或者所述DRB关联的逻辑信道上的待发送数据。
  30. 根据权利要求29所述的装置，其中，所述发送模块，还用于向所述用户设备发送RRC重配置消息，其中，所述RRC重配置消息中携带有所述配置信息。
  31. 根据权利要求29所述的装置，其中，所述发送模块，还用于向所述用户设备发送RRC释放消息，其中，该RRC释放消息用于将所述用户设备从RRC连接态释放到RRC非激活态，所述RRC释放消息中携带有所述配置信息。
  32. 根据权利要求31所述的装置，其中，所述配置信息包括：指示信息，该指示信息用于指示支持RRC非激活态的数据传输的DRB或者与所述DRB关联的逻辑信道。
  33. 一种用户设备，包括：
    收发电路，用于接收来自网络侧设备的配置信息，其中，该配置信息用于指示所述用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；
    处理器，用于在所述配置信息指示所述至少一个逻辑信道支持RRC非激活态的数据传输时，发送所述至少一个逻辑信道的待发送数据；在所述配置信息指示所述DRB支持RRC非激活态的数据传输时，通知所述收发电路发送与所述DRB关联的逻辑信道上的待发送数据。
  34. 一种网络侧设备，其中，包括：
    处理器，用于确定向用户设备发送的配置信息，其中，该配置信息用于指示所述用户设备的至少一个逻辑信道和数据无线承载DRB中的至少之一是否支持无线资源控制RRC非激活态的数据传输；
    收发电路，用于在所述配置信息指示所述至少一个逻辑信道支持RRC非激活态的数据传输时，接收所述用户设备发送的至少一个逻辑信道的 待发送数据或者所述DRB关联的逻辑信道上的待发送数据。
  35. 一种非易失性存储介质，所述非易失性存储介质用于存储程序，该程序在所述非易失性存储介质所在的设备中运行时，执行权利要求1-12中任意一项所述的非激活态下的数据发送方法。
  36. 一种处理器，所述处理器用于运行存储在存储器中的程序，该程序用于执行权利要求1-12中任意一项所述的非激活态下的数据发送方法。
PCT/CN2020/083607 2020-04-07 2020-04-07 非激活态下的数据发送、接收方法及装置、用户设备 Ceased WO2021203252A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20930318.9A EP4132205A4 (en) 2020-04-07 2020-04-07 METHOD AND DEVICE FOR TRANSMITTING AND RECEIVING DATA IN IDLE STATE AND USER DEVICE
CN202080094713.2A CN115024018A (zh) 2020-04-07 2020-04-07 非激活态下的数据发送、接收方法及装置、用户设备
PCT/CN2020/083607 WO2021203252A1 (zh) 2020-04-07 2020-04-07 非激活态下的数据发送、接收方法及装置、用户设备
US17/959,152 US12452949B2 (en) 2020-04-07 2022-10-03 Method and device for transmitting and receiving data in inactive state, and user equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/083607 WO2021203252A1 (zh) 2020-04-07 2020-04-07 非激活态下的数据发送、接收方法及装置、用户设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/959,152 Continuation US12452949B2 (en) 2020-04-07 2022-10-03 Method and device for transmitting and receiving data in inactive state, and user equipment

Publications (1)

Publication Number Publication Date
WO2021203252A1 true WO2021203252A1 (zh) 2021-10-14

Family

ID=78022467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/083607 Ceased WO2021203252A1 (zh) 2020-04-07 2020-04-07 非激活态下的数据发送、接收方法及装置、用户设备

Country Status (4)

Country Link
US (1) US12452949B2 (zh)
EP (1) EP4132205A4 (zh)
CN (1) CN115024018A (zh)
WO (1) WO2021203252A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230156571A1 (en) * 2020-08-06 2023-05-18 Apple Inc. Base station access control techniques for inactive direct transmission
US20240008130A1 (en) * 2021-03-16 2024-01-04 Ofinno, Llc Small Data Transmission
WO2024138295A1 (zh) * 2022-12-26 2024-07-04 Oppo广东移动通信有限公司 用于传输数据的方法、终端设备以及网络设备
US12439471B2 (en) 2020-08-06 2025-10-07 Apple Inc. Access control of user equipments for inactive direct transmissions

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116210339A (zh) * 2020-07-14 2023-06-02 三星电子株式会社 无线通信系统中在rrc_inactive状态下处理小数据传输的方法和装置
US20240023192A1 (en) * 2020-12-07 2024-01-18 Lenovo (Singapore) Pte. Ltd. Lch configuration for small data transmission
CA3214157A1 (en) * 2021-03-30 2022-10-06 Jussi-Pekka Koskinen Methods and apparatuses for controlling small data transmission on uplink
CN115276930A (zh) * 2021-04-30 2022-11-01 北京三星通信技术研究有限公司 一种信息传输方法和设备
CN118042649A (zh) * 2022-11-04 2024-05-14 维沃移动通信有限公司 数据接收、信息传输方法、装置、终端及网络侧设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106714315A (zh) * 2017-01-13 2017-05-24 北京小米移动软件有限公司 信息反馈方法、装置、基站和用户设备
CN107635271A (zh) * 2016-07-18 2018-01-26 电信科学技术研究院 一种传输数据的方法和设备
CN108184214A (zh) * 2016-12-08 2018-06-19 中兴通讯股份有限公司 一种确定数据发送方式的方法及装置
US20180192426A1 (en) * 2017-01-05 2018-07-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system
US20180270889A1 (en) * 2017-03-17 2018-09-20 Huawei Technologies Co., Ltd. Method and apparatus for uplink data transmission using multiple radio access technologies

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109716856A (zh) * 2016-08-10 2019-05-03 Idac控股公司 轻连接和自主移动性
WO2018084589A1 (ko) * 2016-11-03 2018-05-11 엘지전자 주식회사 무선 베어러의 일시 중단 여부를 결정하는 방법 및 장치
KR102298454B1 (ko) * 2017-07-18 2021-09-06 삼성전자 주식회사 차세대 이동 통신 시스템에서 효율적으로 데이터를 분할하는 방법 및 장치
US10397833B2 (en) * 2017-07-27 2019-08-27 Lg Electronics Inc. Method and apparatus for performing EDT
US20190175471A1 (en) * 2017-12-08 2019-06-13 Colgate-Palmolive Company Personal Care Composition
CN112470546B (zh) * 2018-09-28 2023-08-29 Lg 电子株式会社 无线通信系统中确定是在随机接入还是配置的许可上执行传输的方法和装置
WO2020087280A1 (en) * 2018-10-30 2020-05-07 Qualcomm Incorporated Configurations for small data transmission
WO2020034560A1 (en) * 2019-01-04 2020-02-20 Zte Corporation Methods, apparatus and systems for data transmission in a power efficient state
CN113498152A (zh) * 2020-04-01 2021-10-12 夏普株式会社 由用户设备执行的方法以及用户设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107635271A (zh) * 2016-07-18 2018-01-26 电信科学技术研究院 一种传输数据的方法和设备
CN108184214A (zh) * 2016-12-08 2018-06-19 中兴通讯股份有限公司 一种确定数据发送方式的方法及装置
US20180192426A1 (en) * 2017-01-05 2018-07-05 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system
CN106714315A (zh) * 2017-01-13 2017-05-24 北京小米移动软件有限公司 信息反馈方法、装置、基站和用户设备
US20180270889A1 (en) * 2017-03-17 2018-09-20 Huawei Technologies Co., Ltd. Method and apparatus for uplink data transmission using multiple radio access technologies

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
OPPO: "Discussion on Data transmission in ?InactiveState", 3GPP DRAFT; R2-167479_DATA TRANSMISSION IN INACTIVE STATE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20161114 - 20161118, 13 November 2016 (2016-11-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051177395 *
See also references of EP4132205A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230156571A1 (en) * 2020-08-06 2023-05-18 Apple Inc. Base station access control techniques for inactive direct transmission
US12302219B2 (en) * 2020-08-06 2025-05-13 Apple Inc. Base station access control techniques for inactive direct transmission
US12439471B2 (en) 2020-08-06 2025-10-07 Apple Inc. Access control of user equipments for inactive direct transmissions
US20240008130A1 (en) * 2021-03-16 2024-01-04 Ofinno, Llc Small Data Transmission
WO2024138295A1 (zh) * 2022-12-26 2024-07-04 Oppo广东移动通信有限公司 用于传输数据的方法、终端设备以及网络设备

Also Published As

Publication number Publication date
EP4132205A4 (en) 2023-05-10
US20230038013A1 (en) 2023-02-09
CN115024018A (zh) 2022-09-06
EP4132205A1 (en) 2023-02-08
US12452949B2 (en) 2025-10-21

Similar Documents

Publication Publication Date Title
US12452949B2 (en) Method and device for transmitting and receiving data in inactive state, and user equipment
US20230020533A1 (en) Data transmission method, terminal device, and non-transitory computer-readable storage medium
WO2019196783A1 (en) Handling qos flow without a mapping data radio bearer
US20220124859A1 (en) Data transmission method and apparatus, and communication device
US12192955B2 (en) Wireless communication method, terminal device, access network device and core network device to be switched from a first network to a second network
EP3972346B1 (en) Link switching method and communication device
CN111787525A (zh) 一种信息传输方法及装置、通信设备
US12532307B2 (en) Small data transmission method and apparatus, and terminal device
US12063697B2 (en) Data transmission method and apparatus, and terminal
EP3861794A1 (en) Method and apparatus for determining whether to transmit network slice selection assistance information
US11805563B2 (en) Wireless communication method and base station
EP3952596A1 (en) Information transmission method and apparatus, and network device
JP7213950B2 (ja) 情報構成方法および装置、端末、ネットワーク機器
WO2013177768A1 (zh) 多流传输的配置方法、基站、无线网络控制器和用户设备
TW202205896A (zh) 通信方法及通信裝置
US10070370B1 (en) Apparatus, systems and methods for initiating a cell selection
KR20210068403A (ko) 정보 전송 방법, 장치, 단말기 및 네트워크 디바이스
WO2020056587A1 (zh) 一种切换处理方法、终端设备及网络设备
KR102571050B1 (ko) 타이머를 기반으로 하는 처리 방법, 단말 장치 및 네트워크 장치
CN116074847A (zh) 一种信号传输方法及装置、终端设备
US20260032559A1 (en) Multi-path communication method and apparatus
WO2026006990A1 (zh) 无线通信方法、终端设备和网络设备
WO2025148009A1 (zh) 无线通信方法、终端设备和网络设备
WO2022110048A1 (zh) 一种信息指示方法及装置、终端设备、网络设备
WO2022067470A1 (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: 20930318

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020930318

Country of ref document: EP

Effective date: 20221028