WO2024093774A1 - 数据接收、信息传输方法、装置、终端及网络侧设备 - Google Patents

数据接收、信息传输方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2024093774A1
WO2024093774A1 PCT/CN2023/126679 CN2023126679W WO2024093774A1 WO 2024093774 A1 WO2024093774 A1 WO 2024093774A1 CN 2023126679 W CN2023126679 W CN 2023126679W WO 2024093774 A1 WO2024093774 A1 WO 2024093774A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
configuration
downlink
message
paging
Prior art date
Application number
PCT/CN2023/126679
Other languages
English (en)
French (fr)
Inventor
莫毅韬
刘佳敏
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2024093774A1 publication Critical patent/WO2024093774A1/zh

Links

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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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

  • the present application belongs to the field of communication technology, and specifically relates to a data receiving and information transmission method, device, terminal and network side equipment.
  • UE For Multimedia Broadcast Service (MBS) or Small Data Transmission (SDT), User Equipment (UE) needs to receive data in the connected state; if the terminal is released and enters the inactive state, if it wants to receive MBS or SDT, the UE will trigger the Radio Resource Control (RRC) recovery process, then enter the connected state, and then re-acquire the relevant configuration to receive the corresponding data.
  • RRC Radio Resource Control
  • the embodiments of the present application provide a data receiving and information transmission method, apparatus, terminal and network side equipment to solve the problem of low downlink data transmission efficiency.
  • a data receiving method comprising:
  • the terminal receives a radio resource control RRC message, where the RRC message carries configuration indication information;
  • the terminal receives downlink data in an RRC inactive state according to the configuration indication information.
  • a data receiving device which is applied to a terminal, and the device includes:
  • a first receiving module configured to receive a radio resource control RRC message, wherein the RRC message carries configuration indication information
  • the second receiving module is used to receive downlink data in the RRC inactive state according to the configuration indication information.
  • an information transmission method comprising:
  • the network side device sends a radio resource control RRC message to the terminal, wherein the RRC message carries configuration indication information, and the configuration indication information enables the terminal to receive downlink data in an RRC inactive state.
  • an information transmission device which is applied to a network side device, and the device includes:
  • the sending module is used to send a radio resource control RRC message to the terminal, wherein the RRC message carries configuration indication information, and the configuration indication information enables the terminal to receive downlink data in an RRC inactive state.
  • a terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.
  • a terminal comprising a processor and a communication interface, wherein the processor is used to receive a radio resource control RRC message, the RRC message carrying configuration indication information; and according to the configuration indication information, receiving downlink data in an RRC inactive state.
  • a network side device comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the third aspect are implemented.
  • a network side device including a processor and a communication interface, wherein the communication interface is used to send a wireless resource control RRC message to a terminal, the RRC message carries configuration indication information, and the configuration indication information enables the terminal to receive downlink data in an RRC inactive state.
  • a communication system including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the third aspect.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the method described in the first aspect or the third aspect are implemented.
  • a chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect or the third aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the steps of the method described in the first aspect or the third aspect.
  • the terminal by receiving an RRC message carrying configuration indication information and receiving downlink data in an RRC inactive state according to the configuration indication information, the terminal can receive downlink data in an RRC inactive state, thereby improving the transmission efficiency of the downlink data.
  • FIG1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG2 is a schematic diagram of a flow chart of a data receiving method according to an embodiment of the present application.
  • FIG3 is a schematic diagram of an example of an MBS terminal receiving an RRC release message or a paging message and processing the message;
  • FIG. 4 is a schematic diagram of an example of a terminal performing SDT receiving an RRC release message or a paging message and processing the message;
  • FIG5 is a schematic diagram of a flow chart of an information transmission method according to an embodiment of the present application.
  • FIG6 is a schematic diagram of a module of a data receiving device according to an embodiment of the present application.
  • FIG7 is a schematic diagram of the structure of a terminal according to an embodiment of the present application.
  • FIG8 is a schematic diagram of a module of an information transmission device according to an embodiment of the present application.
  • FIG9 is a schematic diagram of the structure of a network side device according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of the structure of a communication device according to an embodiment of the present application.
  • first, second, etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by “first” and “second” are generally of the same type, and the number of objects is not limited.
  • the first object can be one or more.
  • “and/or” in the specification and claims represents at least one of the connected objects, and the character “/" generally represents that the objects associated with each other are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR new radio
  • FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system includes a terminal 11 and a network side device 12 .
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (AR)/virtual reality (VR) device, a robot, a wearable device (Wearable Device), a vehicle user equipment (VUE), a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (a home appliance with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal computer (personal computer, PC), a teller machine or a self-service machine, a sensing service terminal, various sensors, a smart camera and other
  • the network side device 12 may include a receiving device.
  • Access network equipment or core network equipment wherein the access network equipment may also be referred to as wireless access network equipment, wireless access network (Radio Access Network, RAN), wireless access network function or wireless access network unit.
  • RAN Radio Access Network
  • Access network equipment may include base stations, wireless local area network (Wireless Local Area Network, WLAN) access points or WiFi nodes, etc., and base stations may be referred to as node B, evolved node B (Evolved Node B, eNB), access points, base transceiver stations (Base Transceiver Station, BTS), radio base stations, radio transceivers, basic service sets (Basic Service Set, BSS), extended service sets (Extended Service Set, ESS), home B nodes, home evolved B nodes, transmitting and receiving points (Transmitting Receiving Point, TRP), perception signal sending equipment, perception information receiving equipment or other appropriate terms in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary, it should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
  • MBS control information (service bearer configuration parameters, scheduling control information, etc.) is configured through RRC dedicated messages (such as RRC reconfiguration messages), and then the UE obtains the control information of the multicast service according to the RRC dedicated message to receive the MBS service.
  • the network Network, NW
  • G-RNTI group Radio Network Temporary Identity
  • TMGI service identity Temporary Mobile Group Identity
  • the UE listens to the configured G-RNTI Physical Downlink Control Channel (PDCCH) to obtain data scheduling and then receives it.
  • PDCCH Physical Downlink Control Channel
  • the NW may temporarily release the terminal in the CONNECTED state back to the INACTIVE state (because the multicast service temporarily has no data, or the NW side is temporarily short of resources).
  • the NW can carry the TMGI list through the paging message to notify the corresponding TMGI. If the UE is interested in the service corresponding to the TMGI, the UE will trigger the RRC recovery process, then enter the connected state, and then re-acquire the multicast service related configuration, and then receive the corresponding service.
  • the NW In the Long Term Evolution (LTE) system, the NW carries the MT-EDT trigger message through the paging message, and then the UE initiates the EDT process. After receiving the UE's request message (carrying the MT-EDT cause value), the NW concatenates the RRC response message with the data radio bearer (DRB) data into a protocol data unit and sends it to the UE, ultimately realizing the reception of downlink services.
  • DRB data radio bearer
  • an embodiment of the present application provides a data receiving method, including:
  • Step 201 the terminal receives a radio resource control RRC message
  • the RRC message carries configuration indication information
  • Step 202 The terminal receives downlink data in an RRC inactive state according to the configuration indication information.
  • the terminal receives an RRC message carrying configuration indication information, and receives downlink data in the RRC inactive state according to the configuration indication information, so that the terminal can receive downlink data in the RRC inactive state, avoiding the problem that the terminal can only receive downlink data after entering the RRC connected state, thereby improving the transmission efficiency of the downlink data.
  • the RRC message may be an RRC release message, a paging message, a dedicated RRC message, etc.
  • the configuration indication information includes at least one of the following:
  • A11 A first configuration, where the first configuration is used for receiving downlink data
  • the first configuration includes at least one of the following:
  • A111 public frequency resource configuration information for receiving downlink data in an inactive state
  • downlink control channel configuration information for downlink data reception in an inactive state for example, transmission configuration indicator (TCI) configuration information corresponding to PDCCH;
  • TCI transmission configuration indicator
  • downlink shared channel configuration information for receiving downlink data in an inactive state for example, TCI configuration information corresponding to a physical downlink shared channel (PDSCH)
  • PDSCH physical downlink shared channel
  • A114 semi-persistent scheduling configuration information for receiving downlink data in an inactive state
  • A115 group scheduling configuration information for receiving downlink data in an inactive state.
  • A12 first indication information, where the first indication information is used to indicate a first operation
  • the first operation includes at least one of the following:
  • the terminal needs to store the first configuration in itself to facilitate the application of the first configuration by the terminal.
  • applying the first configuration information can be understood as setting the first configuration to a valid state in the current state, that is, the terminal can use the first configuration to send and/or receive data in the current state.
  • the first configuration may be a configuration configured before the terminal receives the RRC message.
  • an optional implementation method of applying the first configuration includes: the high layer of the terminal indicates the TCI configuration information corresponding to the PDCCH and/or PDSCH to the physical layer, and the physical layer of the terminal receives downlink data in the RRC non-activated state according to the TCI configuration information.
  • the TCI configuration information may be the TCI configuration configured by the terminal before receiving the RRC release message, or may be indicated by the RRC release message. Additionally, if there is no configuration in the RRC release message, the terminal uses the TCI configuration information configured by the UE before receiving the RRC release message.
  • This situation refers to the terminal receiving small downlink data.
  • the method further includes:
  • the terminal receives a paging message, and performs a second operation when a first condition is met;
  • the second operation includes at least one of the following:
  • the terminal after the terminal triggers the RRC connection recovery process and enters the connected state, it should first be configured to receive downlink data, for example, receive multicast or groupcast downlink data.
  • the "ignore” here can be understood as the terminal not parsing the first paging group list and not processing the first paging group list; optionally, the first paging group list is included in the paging message, in which case, the first paging group list is the R17 paging group list (paging record list).
  • the terminal ignores the first paging group list after receiving the RRC release message and before receiving a deactivation indication of downlink data.
  • the terminal will only parse the terminal identifier (for example, UE-ID) in the R15 paging record list or the TMGI in the R18 paging record list.
  • the terminal identifier for example, UE-ID
  • the first condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • the terminal when the terminal is in the RRC inactive state, the terminal ignores the first paging group list.
  • the terminal joins one or more multicast sessions indicated by the mobile group identifier
  • the mobile group identifier may refer to a TMGI; this situation means that the terminal has joined a multicast session and needs to receive an MBS.
  • the terminal joins one or more multicast sessions indicated by the mobile group identifier, and the terminal may ignore the first paging group list.
  • the mobile group identifier is included in a second paging group list, the second paging group list is used to notify a second configuration change corresponding to one or more multicast sessions indicated by the mobile group identifier, and the second configuration is used to receive downlink data corresponding to the multicast session;
  • the second paging group list is included in the paging message.
  • the second paging group list is for the R18 group paging (R18 group paging) message.
  • the terminal triggers the RRC connection recovery process, that is, if the R18 paging record list contains the TMGI corresponding to the UE joining the service, the terminal triggers the RRC connection recovery process and prepares to enter the connected state; the R18 paging record list is used to notify the terminal to perform RRC connection recovery (due to configuration update and need to switch to the connected state to re-acquire the configuration, or because the NW wants the terminal to switch to the connected state to receive multicast services).
  • the RRC connection recovery process that is, if the R18 paging record list contains the TMGI corresponding to the UE joining the service, the terminal triggers the RRC connection recovery process and prepares to enter the connected state; the R18 paging record list is used to notify the terminal to perform RRC connection recovery (due to configuration update and need to switch to the connected state to re-acquire the configuration, or because the NW wants the terminal to switch to the connected state to receive multicast services).
  • the terminal is applying the first configuration to receive downlink data
  • the terminal is applying the first configuration to receive downlink data, and the terminal may ignore the first paging group list.
  • the terminal stores the first configuration
  • the terminal stores the first configuration and may ignore the first paging group list.
  • the first configuration is considered valid, and the terminal may ignore the first paging group list.
  • the paging record list of the paging message does not contain a terminal identity that matches the identity of the terminal;
  • This situation can be understood as: the terminal identity included in the paging record list of the paging message is different from the identity of the terminal.
  • the terminal triggers an RRC connection recovery process.
  • the paging message mentioned in the embodiment of the present application includes a PDCCH scrambled by a paging radio network temporary identity (Paging Radio Network Temporary Identity, P-RNTI) and paging information (paging message), and the paging information may be, for example, a PDSCH message.
  • P-RNTI paging Radio Network Temporary Identity
  • the method further includes:
  • the terminal receives a paging message, and applies the first configuration when a second condition is met;
  • the second condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • This situation can be understood as that when the terminal is in an RRC inactive state and receives a paging message, the first configuration is applied to receive downlink data.
  • the terminal joins one or more multicast sessions indicated by the mobile group identifier
  • This situation can be understood as, when the terminal joins a multicast session and receives a paging message, the first configuration is applied to receive downlink data of the multicast session.
  • the mobile group identifier is included in the first paging group list
  • This situation can be understood as, if TMGI is included in the R17 paging record list in the paging message, the terminal applies the first configuration to receive downlink data.
  • the mobile group identity is included in the first paging group list, and the indication information corresponding to the element storage position of the mobile group identity in the first paging record list indicates service activation, and the indication information is the indication information of the element corresponding to the element storage position in the second paging record list;
  • the indication information can be indicated as true or false.
  • the indication information indicates true, it indicates that the service indicated by the corresponding mobile group identifier is in an activated state; when the indication information indicates false, it indicates that the service indicated by the corresponding mobile group identifier is in an inactivated state; when the service is in an activated state, the terminal can apply the first configuration to receive downlink data of the service indicated by the mobile group identifier.
  • the terminal suspends receiving downlink data
  • the terminal suspending the reception of downlink data can be understood as: stopping all discontinuous reception (DRX) timers associated with the corresponding G-RNTI, suspending the multicast radio bearer (MRB), and keeping the value of the Packet Data Convergence Protocol (PDCP) state variable corresponding to the MRB unchanged; at the same time, the terminal continues to maintain the previously stored configuration.
  • DRX discontinuous reception
  • MRB multicast radio bearer
  • PDCP Packet Data Convergence Protocol
  • C106 The terminal receives downlink data without applying the first configuration
  • the terminal stores the first configuration
  • the terminal receives a deactivation indication of the downlink data, where the deactivation indication of the downlink data is used to instruct to stop receiving the downlink data;
  • this situation can be understood as: when the UE is receiving downlink data in an inactive state, the terminal receives a deactivation indication of the downlink data, and the terminal needs to suspend receiving the downlink data based on the deactivation indication; specifically, the lower layer of the terminal notifies the higher layer of the deactivation indication, and the higher layer suspends receiving the downlink data.
  • the paging record list of the paging message does not include a terminal identity that matches the identity of the terminal.
  • the RRC message also includes: an effective time offset of the first configuration; the effective time offset is used to indicate that the first configuration is applied at a time after the terminal receives the RRC message or the target group paging message plus the effective time offset;
  • the target group paging message is a paging message including mobile group identifiers corresponding to one or more multicast sessions joined by the terminal.
  • the method further includes:
  • the terminal ignores a third configuration in an RRC inactive state, where the third configuration is used for transmission of uplink data.
  • the third configuration may be a configuration related to hybrid automatic repeat request (HARQ) feedback and/or physical uplink control channel (PUCCH) resources; for example, PUCCH resource configuration for multicast, HARQ codebook related configuration. That is to say, the terminal will not apply the third configuration in the RRC inactive state (that is, the terminal only stores the third configuration, but ignores the application of the third configuration), and the third configuration will be applied only when the terminal returns from the RRC inactive state to the RRC connected state (for example, the TMGI corresponding to the terminal joining the service is received in the above-mentioned R18 paging record list).
  • HARQ hybrid automatic repeat request
  • PUCCH resource configuration for multicast HARQ codebook related configuration. That is to say, the terminal will not apply the third configuration in the RRC inactive state (that is, the terminal only stores the third configuration, but ignores the application of the third configuration), and the third configuration will be applied only when the terminal returns from the RRC inactive state to the RRC connected state (for example, the
  • the method further includes:
  • the terminal stops receiving the downlink data when receiving a deactivation indication of the downlink data.
  • the terminal receives downlink data by applying the first configuration
  • the terminal stores the first configuration
  • the first configuration is considered valid.
  • the terminal stopping receiving downlink data can be understood as the terminal suspending the reception of downlink data.
  • the method further includes:
  • the terminal receives a paging message, and when a paging record list in the paging message contains a terminal identity identifier that matches the identity identifier of the terminal, performs a third operation;
  • the third operation includes any one of the following:
  • ignoring the first paging group list can be understood as not interpreting the first paging group list and not processing the first paging group list.
  • ignoring the second paging group list can be understood as not interpreting the second paging group list and not processing the second paging group list.
  • a terminal may ignore the R17 paging record list and/or the R18 paging record list, or the terminal may continue to process the R17 paging record list and/or the R18 paging record list.
  • the implementation method in which the terminal receives downlink data in an RRC inactive state according to the configuration indication information includes:
  • the terminal receives a paging message, triggers a downlink small data transmission process when a third condition is met, and receives downlink small data transmission data in an RRC inactive state;
  • the third condition includes at least one of the following:
  • the measured value corresponding to the downlink path loss reference is greater than or equal to the first threshold
  • the terminal is in an RRC inactive state
  • the first indication information indicates downlink small data transmission
  • the paging record list of the paging message includes a terminal identity that matches the identity of the terminal;
  • This situation can be understood as: the terminal identity included in the paging record list of the paging message is the same as the identity of the terminal.
  • the second indication information corresponding to the terminal identity identifier that matches the terminal identity identifier and is included in the paging record list of the paging message indicates downlink small data transmission.
  • the terminal can receive downlink small data transmission in the RRC inactive state.
  • the method further includes:
  • the DRB can be a small data transmission data bearer (SDT-DB).
  • SDT-DB small data transmission data bearer
  • the terminal may maintain the value of the PDCP state variable unchanged when receiving the RRC message;
  • the paging message is sent, and when the first indication information indicates downlink small data transmission, the downlink small data transmission process is triggered, and the downlink small data transmission data is received in the RRC inactive state.
  • the method further includes:
  • the terminal receives downlink small data transmission data in an RRC inactive state after sending an uplink message using a target resource;
  • the target resource includes at least one of the following:
  • F11 a first random access resource sent by message 1 (Msg1) for a random access procedure
  • the first random access resources mentioned in the present application may include preamble resources, random access opportunity (RACH Occasion, RO) resources, etc., wherein RACH is the abbreviation of Random Access Channel.
  • the first random access resource can be used for at least one of the following processes: an initial access process, an RRC connection recovery process, and an uplink small data transmission process.
  • the second random access resources mentioned in the present application may include preamble resources, RO resources, etc.
  • the second random access resource can be used for at least one of the following processes: an initial access process, an RRC connection recovery process, and an uplink small data transmission process.
  • first configuration authorization resource and the second configuration authorization resource are used in the terminal configuration authorization process; the first configuration authorization resource and the second configuration authorization resource may be the same or different.
  • the terminal first sends an uplink message, and then receives downlink data fed back by the network side.
  • the method further includes:
  • the terminal selects the first configuration authorization resource or the second configuration authorization resource as the target resource if the fourth condition is met; and selects the first random access resource or the second random access resource as the target resource if the fourth condition is not met;
  • the fourth condition includes at least one of the following:
  • the measured value corresponding to the downlink path loss reference is greater than or equal to the second threshold
  • the second threshold is used for the uplink small data transmission process; that is, if the measurement value corresponding to the downlink path loss reference is greater than or equal to the second threshold, the terminal can choose to use the first configured authorization resource or the second configured authorization resource to send the uplink message; if the measurement value corresponding to the downlink path loss reference is less than the second threshold, the terminal can choose to use the first random access resource or the second random access resource to send the uplink message.
  • the terminal can choose to use the first configuration authorization resource or the second configuration authorization resource for Sending of uplink message; if the TA is invalid, the terminal can choose to use the first random access resource or the second random access resource to send the uplink message.
  • the first configuration authorization resource is configured
  • the terminal can choose to use the first configuration authorization resource to send an uplink message; if the first configuration authorization resource is not configured, the terminal can choose to use the first random access resource or the second random access resource to send an uplink message.
  • the second configuration authorization resource is configured
  • the terminal can choose to use the second configuration authorization resource to send an uplink message; if the second configuration authorization resource is not configured, the terminal can choose to use the first random access resource or the second random access resource to send an uplink message.
  • the measured value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the first configuration authorized resource is greater than or equal to the third threshold
  • the terminal can choose to use the first configuration authorization resource to send an uplink message; if the measurement values of all downlink reference signals among the one or more downlink reference signals corresponding to the first configuration authorization resource are less than the third threshold, the terminal can choose to use the first random access resource or the second random access resource to send an uplink message.
  • the measurement value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the second configuration authorized resources is greater than or equal to the fourth threshold.
  • the terminal can choose to use the second configuration authorization resource to send an uplink message; if the measurement values of all downlink reference signals among the one or more downlink reference signals corresponding to the second configuration authorization resource are less than the fourth threshold, the terminal can choose to use the first random access resource or the second random access resource to send an uplink message.
  • the method further includes:
  • the terminal performs a fifth operation if a fifth condition is met;
  • the fifth operation includes at least one of the following:
  • the terminal sends an uplink message using random access resources corresponding to an uplink small data transmission process based on a random access process;
  • specific random access resources will be configured for uplink small data transmission, and the terminal can send uplink messages on the random access resources corresponding to the uplink small data transmission process in the random access process.
  • the terminal sends an uplink message using the configuration authorization corresponding to the uplink small data transmission process based on the configuration authorization;
  • MAC PDU Media Access Control Protocol Data Unit
  • CCCH Common Control Channel
  • reconstruction can be understood as performing bit padding to obtain a new MAC PDU.
  • the fifth condition includes at least one of the following:
  • the terminal does not perform the initial transmission of the common control channel message
  • the Medium Access Control Protocol Data Unit (MAC PDU) containing the common control channel message is reconstructed.
  • MAC PDU Medium Access Control Protocol Data Unit
  • the terminal does not generate a MAC PDU containing a common control channel message
  • the terminal when the terminal does not generate a MAC PDU containing a common control channel message, the Medium Access Control Protocol Data Unit (MAC PDU) containing the common control channel message is reconstructed.
  • MAC PDU Medium Access Control Protocol Data Unit
  • the terminal sends an uplink message using random access resources corresponding to the uplink small data transmission process based on the random access process.
  • the terminal sends an uplink message based on the configuration authorization corresponding to the uplink small data transmission process based on configuration authorization.
  • the number of failed receptions of random access response messages is greater than or equal to A times, or the number of failed contention resolutions is greater than or equal to B times, where A and B are integers greater than or equal to 1;
  • a and B are configured by the network side device for the terminal.
  • the terminal uses the random access resources corresponding to the uplink small data transmission process based on the random access process to send an uplink message; for another example, if the number of failed contention resolution attempts is greater than or equal to B times, the terminal uses the random access resources corresponding to the uplink small data transmission process based on the random access process to send an uplink message.
  • the method further includes:
  • the terminal When sending the first common control channel message or triggering a downlink small data transmission process, the terminal starts a first timer
  • the first timer runs.
  • the method further includes:
  • the terminal When the terminal receives the first dedicated transmission channel (Dedicated Transmission Channel, DTCH) message, it restarts the first timer.
  • DTCH Dedicated Transmission Channel
  • the method further includes:
  • the terminal When the first timer times out, the terminal enters an idle state and releases the first configuration.
  • the terminal when the first timer times out, it means that the terminal can no longer perform downlink small data transmission. At this time, the terminal can release the connection and no longer apply the first configuration, thereby returning to the idle state, thereby achieving energy saving.
  • the method further includes:
  • the terminal triggers an uplink small data transmission process based on the configuration authorization, and performs a sixth operation if the sixth condition is met; and performs a seventh operation if the sixth condition is not met;
  • the sixth operation includes at least one of the following:
  • the terminal uses the initial uplink partial bandwidth (Bandwidth Part, BWP) for energy saving (reduced capability, RedCap) to perform the uplink small data transmission process based on the configuration authorization;
  • BWP Bandwidth Part
  • RedCap Reduced capability
  • the terminal monitors the physical downlink control channel using the initial downlink BWP for RedCap.
  • the seventh operation includes at least one of the following:
  • the terminal uses the initial uplink BWP to perform an uplink small data transmission process based on configuration authorization;
  • the terminal uses the initial downlink BWP to monitor a physical downlink control channel.
  • the sixth condition includes at least one of the following:
  • the terminal is a RedCap terminal
  • the terminal when the terminal is an energy-saving RedCap terminal, the terminal can use the initial uplink BWP for RedCap to perform an uplink small data transmission process based on the configuration authorization, and/or the terminal uses the initial downlink BWP for RedCap to monitor the physical downlink control channel; otherwise, the terminal uses the initial uplink BWP to perform an uplink small data transmission process based on the configuration authorization, and/or uses the initial downlink BWP to monitor the physical downlink control channel.
  • the initial uplink BWP for RedCap is configured on the selected uplink carrier
  • the terminal when the initial uplink BWP for RedCap is configured on the selected uplink carrier, the terminal can use the initial uplink BWP for RedCap to perform an uplink small data transmission process based on the configuration authorization; otherwise, the terminal uses the initial uplink BWP to perform an uplink small data transmission process based on the configuration authorization.
  • the terminal when the terminal is in the RRC inactive state, the terminal can use the initial uplink BWP for RedCap to perform an uplink small data transmission process based on the configuration authorization, and/or the terminal uses the initial downlink BWP for RedCap to monitor the physical downlink control channel; otherwise, the terminal uses the initial uplink BWP to perform an uplink small data transmission process based on the configuration authorization, and/or uses the initial downlink BWP to monitor the physical downlink control channel.
  • the terminal monitors the physical downlink control channel using the initial downlink BWP for RedCap; otherwise, the terminal monitors the physical downlink control channel using the initial downlink BWP.
  • the terminal can realize MBS data reception in the RRC inactive state, and can also realize SDT data reception.
  • the specific application of the present application is illustrated in the MBS scenario and the SDT scenario as follows.
  • the terminal receives an RRC release message, where the RRC release message carries configuration indication information, where the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation
  • a first configuration wherein the first configuration is used for receiving downlink data, in which case the first configuration is a multicast configuration for receiving downlink data;
  • the first operation includes at least one of the following:
  • the terminal stores and applies the multicast configuration (optionally, the terminal considers the multicast configuration to be valid), and performs multicast reception in the RRC inactive state according to the multicast configuration.
  • the terminal will also ignore the R17 paging record list (optionally, the R17 paging record list will be ignored after receiving the RRC release message and before receiving the deactivation indication), or the UE will only parse the terminal identifier in the R15 paging record list or the TMGI in the R17 paging record list;
  • the terminal stores the multicast configuration (optionally, the terminal considers the multicast configuration to be valid).
  • the terminal receives the RRC release message, it receives the first paging message (including the TMGI corresponding to the service to which the terminal joins) and the R17 paging record list includes the TMGI corresponding to the service to which the terminal joins (or further, the R18 paging record list corresponding to the element of the R17 paging record list where the TMGI of the terminal joining the service is located indicates that the service is activated), then according to the first configuration, multicast reception is started in the RRC non-activated state (specifically: triggering the MAC layer to perform DRX operation, indicating the TCI state to the lower layer, and initializing the Semi-Persistent Scheduling (SPS) for multicast services).
  • SPS Semi-Persistent Scheduling
  • the terminal triggers the RRC recovery process and prepares to enter the connected state; the R18 paging record list is used to notify the terminal to perform RRC connection recovery (due to configuration update and the need to switch to the connected state to re-acquire the configuration, or because the NW wants the terminal to switch to the connected state to receive multicast services).
  • the RRC release message also includes: an effective time offset of the first configuration; the terminal applies the multicast configuration only after receiving the RRC release message or a group paging message of the TMGI corresponding to the service joined by the terminal and offsetting the effective time offset.
  • the terminal ignores applying HARQ feedback and/or PUCCH resource-related configurations (for example, storing but applying PUCCH resource configurations for multicast, HARQ codebook-related configurations) when storing the configurations; the above configurations are applied only when the terminal returns from the RRC inactive state to the RRC connected state (for example, the above-mentioned R18 paging record list containing the TMGI corresponding to the terminal joining the service is received).
  • HARQ feedback and/or PUCCH resource-related configurations for example, storing but applying PUCCH resource configurations for multicast, HARQ codebook-related configurations
  • the terminal is receiving multicast in the RRC inactive state and receives a deactivation indication for multicast data reception (the indication may be per G-RNTI, per MAC, or associated with multiple G-RNTIs, and the specific association of multiple G-RNTIs is indicated by configuration)
  • the lower layer of the terminal notifies the higher layer, and the higher layer suspends multicast reception (for example, stops all DRX timers associated with the corresponding G-RNTI, suspends MRB, and keeps The value of the PDCP state variable corresponding to the MRB remains unchanged), and the previously stored configuration continues to be maintained.
  • the UE stores the multicast configuration, and) after the terminal receives the deactivation indication of multicast data reception, if it receives the first paging message (including the TMGI corresponding to the service joined by the terminal) and the R17 paging record list in the paging message includes the TMGI corresponding to the service joined by the terminal (or further, the R18 paging record list corresponding to the element of the R17 paging record list where the TMGI of the service joined by the terminal indicates that the service is activated), multicast reception starts in the RRC inactive state according to the configuration.
  • the terminal receives individual paging, it ignores the R17paging record list and the R18paging record list, or continues to process the R17paging record list and the R18paging record list.
  • R18 paging record list is divided into two parts. Part 1 is used for R17 paging record list (TMGI) + R18 activation in active state (activation in INACTIVE) (1bit indication information, enumeration type), and part 2 is TMGI list, which is only R18 disconnected state. Part 1 and part 2 belong to the choice structure. If there is only R17 paging record list, both R17 and R18 inactive terminals need to enter the RRC disconnected state to receive downlink data.
  • TMGI R17 paging record list
  • activation in INACTIVE (1bit indication information, enumeration type
  • the terminal receives a message and processes an example.
  • terminal 1 receives an RRC release message.
  • terminal 1 When receiving an R17 paging message, it applies the multicast configuration.
  • receiving a deactivation indication for multicast reception it suspends multicast reception.
  • receiving an R17 paging again it continues to receive multicast.
  • receiving an R18 paging the terminal needs to exit the inactive state and enter the connected state.
  • the terminal receives an R18 paging during multicast reception, it continues to receive multicast during the process of entering the connected state and continues to receive multicast after entering the connected state.
  • terminal 2 in FIG3 receives an RRC release message, stores and applies the multicast configuration until the multicast transmission stops.
  • terminal 3 in FIG3 receives an RRC release message, it stores and applies the multicast configuration, and performs RRC connection recovery when receiving an R18 paging.
  • the terminal receives an RRC release message, where the RRC release message carries configuration indication information, where the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation, where the first operation includes downlink small data transmission;
  • a first configuration where the first configuration is used for receiving downlink data.
  • the terminal may perform one of the following operations:
  • the downlink small data transmission process After receiving the paging message, the downlink small data transmission process is performed;
  • the triggering condition of the downlink small data transmission process includes at least one of:
  • the measured value corresponding to the downlink path loss reference is greater than or equal to the first threshold
  • the paging record list of the paging message contains a terminal identity that matches the identity of the terminal;
  • the terminal identity pair that matches the terminal identity contained in the paging record list of the paging message The corresponding second indication information indicates downlink small data transmission.
  • the terminal can use the random access resources corresponding to the uplink small data transmission process based on the random access process to send an uplink message.
  • uplink small data transmission takes precedence over downlink small data transmission.
  • the terminal uses the dedicated RO resources corresponding to the downlink small data transmission process.
  • the terminal uses the random access resources corresponding to the uplink small data transmission process based on the random access process to send an uplink message.
  • the terminal when sending the first common control channel message or triggering the downlink small data transmission process, the terminal starts a first timer.
  • the terminal When receiving the first DTCH message, the terminal restarts the first timer.
  • the terminal When the first timer times out, the terminal enters an idle state and releases the first configuration.
  • terminal 1 receives an RRC release message. When receiving an R15 paging, it does not perform SDT because the SDT triggering condition is not met. The terminal restores the RRC connection, starts the first timer when sending an RRC recovery request, executes SDT, restarts the first timer when receiving downlink data, and releases the connection after receiving the RRC release message again, and enters the idle state.
  • the content of group paging messages received by the terminals in different scenarios and the corresponding terminal processing behaviors are defined to reduce the overhead of group paging messages as much as possible and allow terminals in RRC inactive state to smoothly receive multicast service data or perform terminal state transitions.
  • the SDT terminal For terminals performing SDT, it is allowed to carry an indication of small data transmission in the RRC release message. Subsequently, the SDT terminal receives data for downlink small data transmission in the RRC inactive state based on whether the monitored paging message contains its own terminal identification information and the conditions for triggering downlink small data transmission.
  • an embodiment of the present application provides an information transmission method, including:
  • Step 501 A network-side device sends a radio resource control (RRC) message to a terminal.
  • the RRC message carries configuration indication information.
  • the configuration indication information enables the terminal to receive downlink data in an RRC inactive state.
  • the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation
  • a first configuration wherein the first configuration is a configuration for receiving downlink data
  • the first operation includes at least one of the following:
  • a data receiving device 600 As shown in FIG6 , a data receiving device 600 according to an embodiment of the present application, applied to a terminal, includes:
  • the first receiving module 601 is used to receive a radio resource control RRC message, where the RRC message carries configuration indication information;
  • the second receiving module 602 is configured to receive downlink data in an RRC inactive state according to the configuration indication information.
  • the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation
  • a first configuration wherein the first configuration is used for receiving downlink data
  • the first operation includes at least one of the following:
  • the device further comprises:
  • a first execution module configured to receive a paging message and execute a second operation when a first condition is met
  • the second operation includes at least one of the following:
  • the first paging group list being used to notify activation of one or more multicast sessions indicated by a mobile group identifier
  • the first condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • the terminal joins one or more multicast sessions indicated by a mobile group identifier
  • the mobile group identifier is included in a second paging group list, the second paging group list is used to notify a second configuration change corresponding to one or more multicast sessions indicated by the mobile group identifier, the second configuration is used to receive downlink data corresponding to the multicast session;
  • the terminal is applying the first configuration to receive downlink data
  • the terminal stores the first configuration
  • the first configuration is considered valid
  • the paging record list of the paging message does not include a terminal identity that matches the identity of the terminal.
  • the device further comprises:
  • a second execution module configured to receive a paging message, and apply the first configuration when a second condition is met
  • the second condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • the terminal joins one or more multicast sessions indicated by a mobile group identifier
  • the mobile group identifier is included in the first paging group list
  • the mobile group identity is included in the first paging group list, and the indication information corresponding to the element storage position of the mobile group identity in the first paging record list indicates service activation, and the indication information is the indication information of the element corresponding to the element storage position in the second paging record list;
  • the terminal suspends receiving downlink data
  • the terminal receives downlink data without applying the first configuration
  • the terminal stores the first configuration
  • the first configuration is considered valid
  • the terminal receives a deactivation indication of the downlink data, where the deactivation indication of the downlink data is used to instruct to stop receiving the downlink data;
  • the paging record list of the paging message does not include a terminal identity that matches the identity of the terminal.
  • the RRC message also includes: an effective time offset of the first configuration; the effective time offset is used to indicate that the first configuration is applied at a time after the terminal receives the RRC message or the target group paging message plus the effective time offset;
  • the target group paging message is a paging message including mobile group identifiers corresponding to one or more multicast sessions joined by the terminal.
  • the device further includes:
  • the third execution module is used to ignore a third configuration in an RRC inactive state, where the third configuration is used for transmission of uplink data.
  • the device further includes:
  • the fourth execution module is used to stop receiving the downlink data when receiving a deactivation indication of the downlink data during the process of receiving the downlink data in the RRC inactive state.
  • the device further includes:
  • a fifth execution module configured to receive a paging message, and execute a third operation when a paging record list in the paging message contains a terminal identity that matches the identity of the terminal;
  • the third operation includes any one of the following:
  • the second paging group list is ignored.
  • the second receiving module is used to:
  • the third condition includes at least one of the following:
  • the measured value corresponding to the downlink path loss reference is greater than or equal to the first threshold
  • the terminal is in an RRC inactive state
  • the first indication information indicates downlink small data transmission
  • a first configuration is indicated
  • the paging record list of the paging message contains a terminal identity that matches the identity of the terminal;
  • the second indication information corresponding to the terminal identity identifier matched with the terminal identity identifier contained in the paging record list of the paging message indicates downlink small data transmission.
  • the device further includes:
  • the sixth execution module is used to maintain the value of the PDCP state variable unchanged when the packet data convergence protocol PDCP entity corresponding to the data radio bearer DRB is suspended.
  • the device further includes:
  • a third receiving module is used to receive data of the downlink small data transmission in an RRC inactive state after sending an uplink message using a target resource when a downlink small data transmission process is triggered;
  • the target resource includes at least one of the following:
  • a first random access resource for sending a message 1 of a random access procedure
  • the second configuration authorization resource is used for the uplink small data transmission process.
  • the device further comprises:
  • a seventh execution module configured to, when triggering a downlink small data transmission process, select the first configuration authorization resource or the second configuration authorization resource as the target resource if the fourth condition is met; and select the first random access resource or the second random access resource as the target resource if the fourth condition is not met;
  • the fourth condition includes at least one of the following:
  • a measurement value corresponding to a downlink path loss reference is greater than or equal to a second threshold, where the second threshold is used in an uplink small data transmission process;
  • the timing advance TA is effective
  • the first configuration authorization resource is configured
  • the second configuration authorizes the resource to be configured
  • a measured value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the first configuration authorized resource is greater than or equal to a third threshold
  • a measured value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the second configuration authorized resources is greater than or equal to a fourth threshold.
  • the device further includes:
  • An eighth execution module configured to, when the downlink small data transmission process is triggered and the fifth condition is met, execute a fifth operation
  • the fifth condition includes at least one of the following:
  • the terminal does not perform initial transmission of a common control channel message
  • the terminal does not generate a media access control protocol data unit MAC PDU containing a common control channel message
  • the number of failed receptions of random access response messages is greater than or equal to A times, or the number of failed contention resolutions is greater than or equal to B times, where A and B are integers greater than or equal to 1;
  • the fifth operation includes at least one of the following:
  • the terminal sends an uplink message using random access resources corresponding to an uplink small data transmission process based on a random access process
  • the terminal sends an uplink message using the configuration authorization corresponding to the uplink small data transmission process based on the configuration authorization;
  • the device further includes:
  • a starting module used to start a first timer when sending a first common control channel message or triggering a downlink small data transmission process
  • the first timer runs.
  • the device further includes:
  • the restart module is used to restart the first timer when receiving the first dedicated transmission channel DTCH message.
  • the device further includes:
  • a release module is used to enter an idle state and release the first configuration when the first timer times out.
  • the device further includes:
  • a ninth execution module configured to trigger an uplink small data transmission process based on configuration authorization, and to execute a sixth operation if the sixth condition is met; and to execute a seventh operation if the sixth condition is not met;
  • the sixth condition includes at least one of the following:
  • the terminal is an energy-saving RedCap terminal
  • the initial uplink partial bandwidth BWP for RedCap is configured on the selected uplink carrier
  • the terminal is in an RRC inactive state
  • the initial downlink BWP for RedCap is configured
  • the sixth operation includes at least one of the following:
  • the terminal uses the initial uplink BWP for RedCap to perform an uplink small data transmission process based on configuration authorization;
  • the terminal monitors the physical downlink control channel using the initial downlink BWP for RedCap;
  • the seventh operation includes at least one of the following:
  • the terminal uses the initial uplink BWP to perform an uplink small data transmission process based on configuration authorization;
  • the terminal monitors a physical downlink control channel using the initial downlink BWP.
  • the device embodiment corresponds to the above method, and all implementation methods in the above method embodiment are The above formulas are all applicable to the embodiments of the device and can achieve the same technical effects.
  • the data receiving device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip.
  • the electronic device can be a terminal, or it can be other devices other than a terminal.
  • the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
  • the data receiving device provided in the embodiment of the present application can implement each process implemented by the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be described here.
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is used to receive a radio resource control RRC message, wherein the RRC message carries configuration indication information; and according to the configuration indication information, receiving downlink data in an RRC inactive state.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to receive a radio resource control RRC message, wherein the RRC message carries configuration indication information; and according to the configuration indication information, receiving downlink data in an RRC inactive state.
  • the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation
  • a first configuration wherein the first configuration is used for receiving downlink data
  • the first operation includes at least one of the following:
  • the processor is configured to:
  • the second operation includes at least one of the following:
  • the first paging group list being used to notify activation of one or more multicast sessions indicated by a mobile group identifier
  • the first condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • the terminal joins one or more multicast sessions indicated by a mobile group identifier
  • the mobile group identifier is included in a second paging group list, the second paging group list is used to notify a second configuration change corresponding to one or more multicast sessions indicated by the mobile group identifier, the second configuration is used to receive downlink data corresponding to the multicast session;
  • the terminal is applying the first configuration to receive downlink data
  • the terminal stores the first configuration
  • the first configuration is considered valid
  • the paging record list of the paging message does not contain a terminal identity identifier that matches the identity identifier of the terminal. knowledge.
  • the processor is further configured to:
  • the second condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • the terminal joins one or more multicast sessions indicated by a mobile group identifier
  • the mobile group identifier is included in the first paging group list
  • the mobile group identity is included in the first paging group list, and the indication information corresponding to the element storage position of the mobile group identity in the first paging record list indicates service activation, and the indication information is the indication information of the element corresponding to the element storage position in the second paging record list;
  • the terminal suspends receiving downlink data
  • the terminal receives downlink data without applying the first configuration
  • the terminal stores the first configuration
  • the first configuration is considered valid
  • the terminal receives a deactivation indication of the downlink data, where the deactivation indication of the downlink data is used to instruct to stop receiving the downlink data;
  • the paging record list of the paging message does not include a terminal identity that matches the identity of the terminal.
  • the RRC message also includes: an effective time offset of the first configuration; the effective time offset is used to indicate that the first configuration is applied at a time after the terminal receives the RRC message or the target group paging message plus the effective time offset;
  • the target group paging message is a paging message including mobile group identifiers corresponding to one or more multicast sessions joined by the terminal.
  • the processor is further configured to:
  • the third configuration is ignored in the RRC inactive state, and the third configuration is used for transmission of uplink data.
  • the communication interface is further used for:
  • the processor is further configured to:
  • the third operation includes any one of the following:
  • the second paging group list is ignored.
  • the communication interface is further used for:
  • the third condition includes at least one of the following:
  • the measured value corresponding to the downlink path loss reference is greater than or equal to the first threshold
  • the terminal is in an RRC inactive state
  • the first indication information indicates downlink small data transmission
  • a first configuration is indicated
  • the paging record list of the paging message contains a terminal identity that matches the identity of the terminal;
  • the second indication information corresponding to the terminal identity identifier matched with the terminal identity identifier contained in the paging record list of the paging message indicates downlink small data transmission.
  • the processor is further configured to:
  • the communication interface is further used to: in the case of triggering a downlink small data transmission process, after sending an uplink message using a target resource, receive data of the downlink small data transmission in an RRC inactive state;
  • the target resource includes at least one of the following:
  • the second configuration authorization resource is used for the uplink small data transmission process.
  • the processor is further configured to:
  • the fourth condition includes at least one of the following:
  • a measurement value corresponding to a downlink path loss reference is greater than or equal to a second threshold, where the second threshold is used in an uplink small data transmission process;
  • the timing advance TA is effective
  • the first configuration authorization resource is configured
  • the second configuration authorizes the resource to be configured
  • a measured value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the first configuration authorized resource is greater than or equal to a third threshold
  • a measured value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the second configuration authorized resources is greater than or equal to a fourth threshold.
  • the processor is further configured to:
  • the fifth condition includes at least one of the following:
  • the terminal does not perform initial transmission of a common control channel message
  • the terminal does not generate a media access control protocol data unit MAC PDU containing a common control channel message
  • the number of failed receptions of random access response messages is greater than or equal to A times, or the number of failed contention resolutions is greater than or equal to B times, where A and B are integers greater than or equal to 1;
  • the fifth operation includes at least one of the following:
  • the terminal sends an uplink message using random access resources corresponding to an uplink small data transmission process based on a random access process
  • the terminal sends an uplink message using the configuration authorization corresponding to the uplink small data transmission process based on the configuration authorization;
  • the processor is further configured to:
  • the first timer runs.
  • the processor is further configured to:
  • the first timer is restarted.
  • the processor is further configured to:
  • the system When the first timer times out, the system enters an idle state and releases the first configuration.
  • the processor is further configured to:
  • the sixth condition includes at least one of the following:
  • the terminal is an energy-saving RedCap terminal
  • the initial uplink partial bandwidth BWP for RedCap is configured on the selected uplink carrier
  • the terminal is in an RRC inactive state
  • the initial downlink BWP for RedCap is configured
  • the sixth operation includes at least one of the following:
  • the terminal uses the initial uplink BWP for RedCap to perform an uplink small data transmission process based on configuration authorization;
  • the terminal monitors the physical downlink control channel using the initial downlink BWP for RedCap;
  • the seventh operation includes at least one of the following:
  • the terminal uses the initial uplink BWP to perform an uplink small data transmission process based on configuration authorization;
  • the terminal monitors a physical downlink control channel using the initial downlink BWP.
  • the terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to the terminal embodiment and can achieve the same technical effect.
  • Figure 7 is a schematic diagram of the hardware structure of a terminal implementing the embodiment of the present application.
  • the terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709 and at least some of the components of a processor 710.
  • the terminal 700 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 710 through a power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system.
  • a power source such as a battery
  • the terminal structure shown in FIG7 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode.
  • the display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc.
  • the user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072.
  • the touch panel 7071 is also called a touch screen.
  • the touch panel 7071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the radio frequency unit 701 can transmit the data to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network side device.
  • the radio frequency unit 701 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
  • the memory 709 can be used to store software programs or instructions and various data.
  • the memory 709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the memory 709 may include a volatile memory or a non-volatile memory, or the memory 709 may include both volatile and non-volatile memories.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM).
  • the memory 709 in the embodiment of the present application includes but is not limited to: Limited to these and any other suitable types of memory.
  • the processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 710.
  • radio frequency unit 701 is used for:
  • a radio resource control (RRC) message is received, wherein the RRC message carries configuration indication information; and downlink data is received in an RRC inactive state according to the configuration indication information.
  • RRC radio resource control
  • the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation
  • a first configuration wherein the first configuration is used for receiving downlink data
  • the first operation includes at least one of the following:
  • processor 710 is further configured to:
  • the second operation includes at least one of the following:
  • the first paging group list being used to notify activation of one or more multicast sessions indicated by a mobile group identifier
  • the first condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • the terminal joins one or more multicast sessions indicated by a mobile group identifier
  • the mobile group identifier is included in a second paging group list, the second paging group list is used to notify a second configuration change corresponding to one or more multicast sessions indicated by the mobile group identifier, the second configuration is used to receive downlink data corresponding to the multicast session;
  • the terminal is applying the first configuration to receive downlink data
  • the terminal stores the first configuration
  • the first configuration is considered valid
  • the paging record list of the paging message does not include a terminal identity that matches the identity of the terminal.
  • processor 710 is further configured to:
  • the second condition includes at least one of the following:
  • the terminal is in an RRC inactive state
  • the terminal joins one or more multicast sessions indicated by a mobile group identifier
  • the mobile group identifier is included in the first paging group list
  • the mobile group identity is included in the first paging group list, and the indication information corresponding to the element storage position of the mobile group identity in the first paging record list indicates service activation, and the indication information is the indication information of the element corresponding to the element storage position in the second paging record list;
  • the terminal suspends receiving downlink data
  • the terminal receives downlink data without applying the first configuration
  • the terminal stores the first configuration
  • the first configuration is considered valid
  • the terminal receives a deactivation indication of the downlink data, where the deactivation indication of the downlink data is used to instruct to stop receiving the downlink data;
  • the paging record list of the paging message does not include a terminal identity that matches the identity of the terminal.
  • the RRC message also includes: an effective time offset of the first configuration; the effective time offset is used to indicate that the first configuration is applied at a time after the terminal receives the RRC message or the target group paging message plus the effective time offset;
  • the target group paging message is a paging message including mobile group identifiers corresponding to one or more multicast sessions joined by the terminal.
  • processor 710 is further configured to:
  • the third configuration is ignored in the RRC inactive state, and the third configuration is used for transmission of uplink data.
  • the radio frequency unit 701 is further used for:
  • processor 710 is further configured to:
  • the third operation includes any one of the following:
  • the second paging group list is ignored.
  • the radio frequency unit 701 is further configured to:
  • the third condition includes at least one of the following:
  • the measured value corresponding to the downlink path loss reference is greater than or equal to the first threshold
  • the terminal is in an RRC inactive state
  • the first indication information indicates downlink small data transmission
  • a first configuration is indicated
  • the paging record list of the paging message contains a terminal identity that matches the identity of the terminal;
  • the second indication information corresponding to the terminal identity identifier matched with the terminal identity identifier contained in the paging record list of the paging message indicates downlink small data transmission.
  • processor 710 is further configured to:
  • the radio frequency unit 701 is further configured to: in the case of triggering a downlink small data transmission process, after sending an uplink message using a target resource, receive downlink small data transmission data in an RRC inactive state;
  • the target resource includes at least one of the following:
  • the second configuration authorization resource is used for the uplink small data transmission process.
  • processor 710 is further configured to:
  • the fourth condition includes at least one of the following:
  • a measurement value corresponding to a downlink path loss reference is greater than or equal to a second threshold, where the second threshold is used in an uplink small data transmission process;
  • the timing advance TA is effective
  • the first configuration authorization resource is configured
  • the second configuration authorizes the resource to be configured
  • a measured value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the first configuration authorized resource is greater than or equal to a third threshold
  • a measured value of at least one downlink reference signal among the one or more downlink reference signals corresponding to the second configuration authorized resources is greater than or equal to a fourth threshold.
  • processor 710 is further configured to:
  • the fifth condition includes at least one of the following:
  • the terminal does not perform initial transmission of a common control channel message
  • the terminal does not generate a media access control protocol data unit MAC PDU containing a common control channel message
  • the number of failed receptions of random access response messages is greater than or equal to A times, or the number of failed contention resolutions is greater than or equal to B times, where A and B are integers greater than or equal to 1;
  • the fifth operation includes at least one of the following:
  • the terminal sends an uplink message using random access resources corresponding to an uplink small data transmission process based on a random access process
  • the terminal sends an uplink message using the configuration authorization corresponding to the uplink small data transmission process based on the configuration authorization;
  • processor 710 is further configured to:
  • the first timer runs.
  • processor 710 is further configured to:
  • the first timer is restarted.
  • processor 710 is further configured to:
  • the system When the first timer times out, the system enters an idle state and releases the first configuration.
  • processor 710 is further configured to:
  • the sixth condition includes at least one of the following:
  • the terminal is an energy-saving RedCap terminal
  • the initial uplink partial bandwidth BWP for RedCap is configured on the selected uplink carrier
  • the terminal is in an RRC inactive state
  • the initial downlink BWP for RedCap is configured
  • the sixth operation includes at least one of the following:
  • the terminal uses the initial uplink BWP for RedCap to perform an uplink small data transmission process based on configuration authorization;
  • the terminal monitors the physical downlink control channel using the initial downlink BWP for RedCap;
  • the seventh operation includes at least one of the following:
  • the terminal uses the initial uplink BWP to perform an uplink small data transmission process based on configuration authorization;
  • the terminal monitors a physical downlink control channel using the initial downlink BWP.
  • the embodiment of the present application further provides a terminal, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction is executed by the processor to implement the above-mentioned data receiving method.
  • a terminal including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction is executed by the processor to implement the above-mentioned data receiving method.
  • An embodiment of the present application also provides a readable storage medium, which may be volatile or non-volatile.
  • a program or instruction is stored on the computer-readable storage medium.
  • the program or instruction is executed by the processor, each process of the above-mentioned data receiving method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
  • the embodiment of the present application further provides an information transmission device 800, which is applied to a network side device, including:
  • the sending module 801 is used to send a radio resource control RRC message to a terminal, wherein the RRC message carries configuration indication information, and the configuration indication information enables the terminal to receive downlink data in an RRC inactive state.
  • the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation
  • a first configuration wherein the first configuration is a configuration for receiving downlink data
  • the first operation includes at least one of the following:
  • the device embodiment is a device corresponding to the above-mentioned method. All implementation methods in the above-mentioned method embodiment are applicable to the device embodiment and can achieve the same technical effect, which will not be repeated here.
  • An embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is used to send a radio resource control RRC message to a terminal, the RRC message carries configuration indication information, and the configuration indication information enables the terminal to receive downlink data in an RRC inactive state.
  • a network side device including a processor and a communication interface, wherein the communication interface is used to send a radio resource control RRC message to a terminal, the RRC message carries configuration indication information, and the configuration indication information enables the terminal to receive downlink data in an RRC inactive state.
  • the configuration indication information includes at least one of the following:
  • first indication information where the first indication information is used to indicate a first operation
  • a first configuration wherein the first configuration is a configuration for receiving downlink data
  • the first operation includes at least one of the following:
  • an embodiment of the present application also provides a network side device, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor.
  • a network side device including a processor, a memory, and a program or instruction stored in the memory and executable on the processor.
  • the embodiment of the present application also provides a network side device.
  • the access network device 900 includes: an antenna 901, a radio frequency device 902, a baseband device 903, a processor 904 and a memory 905.
  • the antenna 901 is connected to the radio frequency device 902.
  • the radio frequency device 902 receives information through the antenna 901 and sends the received information to the baseband device 903 for processing.
  • the baseband device 903 processes the information to be sent and sends
  • the received information is sent to the radio frequency device 902 , which processes the received information and then sends it out through the antenna 901 .
  • the method executed by the access network device in the above embodiment may be implemented in the baseband device 903, which includes a baseband processor.
  • the baseband device 903 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, one of which is, for example, a baseband processor, which is connected to the memory 905 through a bus interface to call the program in the memory 905 and execute the network device operations shown in the above method embodiment.
  • the access network device may also include a network interface 906, which is, for example, a common public radio interface (CPRI).
  • a network interface 906 which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the access network device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 905 and executable on the processor 904.
  • the processor 904 calls the instructions or programs in the memory 905 to execute the methods executed by the modules shown in Figure 8 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, which may be volatile or non-volatile.
  • a program or instruction is stored on the readable storage medium.
  • the program or instruction is executed by a processor, the various processes of the above-mentioned information transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is a processor in the access network device described in the above embodiment.
  • the readable storage medium may be non-volatile or non-transient.
  • the readable storage medium may include a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.
  • the embodiment of the present application further provides a communication device 1000, including a processor 1001 and a memory 1002, wherein the memory 1002 stores a program or instruction that can be run on the processor 1001.
  • the communication device 1000 is a terminal
  • the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned data receiving method embodiment, and can achieve the same technical effect.
  • the communication device 1000 is a network side device
  • the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data receiving method or information transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the embodiments of the present application further provide a computer program/program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned information transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the above-mentioned data receiving method, and the network side device can be used to execute the steps of the above-mentioned information transmission method.
  • the technical solution of the present application can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, computer, server, air conditioner, or network equipment, etc.) to execute the methods described in each embodiment of the present application.
  • a storage medium such as ROM/RAM, magnetic disk, optical disk
  • a terminal which can be a mobile phone, computer, server, air conditioner, or network equipment, etc.

Landscapes

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

Abstract

本申请公开了一种数据接收、信息传输方法、装置、终端及网络侧设备，属于通信技术领域，本申请实施例的数据接收方法，包括：终端接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；所述终端根据所述配置指示信息，在RRC非激活态接收下行数据。

Description

数据接收、信息传输方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请主张在2022年11月04日在中国提交的中国专利申请No.202211380073.9的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种数据接收、信息传输方法、装置、终端及网络侧设备。
背景技术
针对多播广播服务(Multimedia Broadcast Service，MBS)或小数据传输(Small Data Transmission，SDT)，用户设备(User Equipment，UE)需要在连接态进行数据的接收；如果终端被释放进入非激活(INACTIVE)态，若想进行MBS或SDT接收，UE则会触发无线资源控制(Radio Resource Control，RRC)恢复过程，随后进入连接态，再重新获取相关配置，进而进行对应数据的接收，此种方式耗时较长，会导致传输效率较低。
发明内容
本申请实施例提供一种数据接收、信息传输方法、装置、终端及网络侧设备，以解决下行数据传输效率不高的问题。
第一方面，提供了一种数据接收方法，包括：
终端接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；
所述终端根据所述配置指示信息，在RRC非激活态接收下行数据。
第二方面，提供了一种数据接收装置，应用于终端，该装置包括：
第一接收模块，用于接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；
第二接收模块，用于根据所述配置指示信息，在RRC非激活态接收下行数据。
第三方面，提供了一种信息传输方法，该方法包括：
网络侧设备向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
第四方面，提供了一种信息传输装置，应用于网络侧设备，该装置包括：
发送模块，用于向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
第五方面，提供了一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；根据所述配置指示信息，在RRC非激活态接收下行数据。
第七方面，提供了一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
第九方面，提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的方法的步骤，所述网络侧设备可用于执行如第三方面所述的方法的步骤。
第十方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面或第三方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面或第三方面所述的方法的步骤。
第十三方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面或第三方面所述的方法的步骤。
在本申请实施例中，通过接收携带配置指示信息的RRC消息，并根据所述配置指示信息，在RRC非激活态接收下行数据，以此使得终端能够在RRC非激活态进行下行数据的接收，提高了下行数据的传输效率。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例的数据接收方法的流程示意图；
图3是进行MBS的终端收RRC释放消息或寻呼消息及处理的图例示意图；
图4是进行SDT的终端收RRC释放消息或寻呼消息及处理的图例示意图；
图5是本申请实施例的信息传输方法的流程示意图；
图6是本申请实施例的数据接收装置的模块示意图；
图7是本申请实施例的终端的结构示意图；
图8是本申请实施例的信息传输装置的模块示意图；
图9是本申请实施例的网络侧设备的结构示意图；
图10是本申请实施例的通信设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机、感知业务终端、各种传感器、智能相机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接 入网设备或核心网设备，其中，接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点或WiFi节点等，基站可被称为节点B、演进节点B(Evolved Node B，eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)、感知信号发送设备、感知信息接收设备或所属领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
下面先对与本申请相关的相关技术进行说明如下。
一、新空口(New Radio，NR)多播接收
MBS的控制信息(业务承载配置参数，调度控制信息等)通过RRC专用消息(例如RRC重配置消息(reconfiguration message))进行配置，随后UE根据RRC专用消息获取多播业务的控制信息接收MBS业务。具体地，网络(NetWork，NW)通过组无线网络临时标识(group Radio Network Temporary Identity，G-RNTI)来进行UE感兴趣的某个/某几个多播业务的调度(例如，配置G-RNTI、业务标识临时移动群组标识(Temporary Mobile Group Identity，TMGI)、以及调度信息之间的关联关系)。在UE侧，UE监听配置的G-RNTI物理下行控制信道(Physical Downlink Control Channel，PDCCH)获得数据调度进而进行接收。
二、多播中的组寻呼(group paging)
在NR多播传输中，NW可能会暂时性把处于连接(CONNECTED)状态的终端释放回去非激活(INACTIVE)状态(由于多播业务暂时没有了数据，或者NW侧暂时资源紧缺)。当多播业务处于激活时(有新的数据到达)或者NW的空口资源重新空闲时，NW可以通过paging消息携带TMGI列表(list)，通知对应的TMGI。如果UE对该TMGI对应的业务感兴趣，UE则会触发RRC恢复过程，随后进入连接态，再重新获取多播业务相关配置，进而进行对应业务的接收。
三、下行以终端为终点的早期数据传输(Mobile Terminated Early Data Transmission，MT-EDT)
在长期演进(Long Term Evolution，LTE)系统中，NW会通过paging消息携带MT-EDT触发消息，随后UE发起EDT过程，NW在接收到UE的请求消息(携带MT-EDT的原因值)后，把RRC响应消息串接上数据无线承载(Data Radio Bearer，DRB)数据，一并成一个协议数据单元，发送给UE，最终实现下行业务的接收。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的数据接收、信息传输方法、装置、终端及网络侧设备进行详细地说明。
如图2所示，本申请实施例提供一种数据接收方法，包括：
步骤201，终端接收无线资源控制RRC消息；
可选地，所述RRC消息中携带配置指示信息；
步骤202，所述终端根据所述配置指示信息，在RRC非激活态接收下行数据。
需要说明的是，终端通过接收携带配置指示信息的RRC消息，并根据所述配置指示信息，在RRC非激活态接收下行数据，以此使得终端能够在RRC非激活态进行下行数据的接收，避免终端进入RRC连接态后才能接收下行数据的问题，提高了下行数据的传输效率。
可选地，该RRC消息可以为RRC释放消息，也可以为寻呼消息，还可以为专用RRC消息等。
可选地，本申请的另一实施例中，所述配置指示信息包括以下至少之一：
A11、第一配置，所述第一配置用于下行数据的接收；
可选地，所述第一配置包括如下至少之一：
A111、用于非激活态进行下行数据接收的公共频率资源配置信息；
A112、用于非激活态进行下行数据接收的下行控制信道配置信息(例如，PDCCH对应的传输配置指示(Transmission Configuration Indicator，TCI)配置信息)；
A113、用于非激活态进行下行数据接收的下行共享信道配置信息(例如，物理下行共享信道(Physical Downlink Shared CHannel，PDSCH)对应的TCI配置信息)；
A114、用于非激活态进行下行数据接收的半持续调度配置信息；
A115、用于非激活态进行下行数据接收的组调度配置信息。
A12、第一指示信息，所述第一指示信息用于指示第一操作；
可选地，本申请的另一实施例中，所述第一操作包括以下至少之一：
A11、存储第一配置；
即终端在获取到第一配置后，需要将第一配置在自身进行存储，以便于终端对第一配置的应用。
A12、应用第一配置；
需要说明的是，应用第一配置信息可以理解为在当前状态下将第一配置设置为生效状态，即终端可以在当前状态下利用该第一配置进行数据的发送和/或接收。
可选地，若配置指示信息中未携带第一配置，则该第一配置可以是终端收到RRC消息前被配置的配置。
例如，在第一配置为TCI配置信息的情况下，应用第一配置的可选实现方式包括：终端的高层向物理层指示PDCCH和/或PDSCH对应的TCI配置信息，终端的物理层根据该TCI配置信息进行RRC非激活态的下行数据接收。所述TCI配置信息可以是收到RRC释放消息前终端被配置的TCI配置，也可以是由RRC释放消息指示的。额外地，如果RRC释放消息中没有配置的话，则终端使用收到RRC释放消息前UE被配置的TCI配置信息。
A13、下行小数据传输；
此种情况指的是，终端接收下行小数据。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端接收寻呼消息，在满足第一条件的情况下，执行第二操作；
可选地，所述第二操作包括以下至少一项：
B11、应用所述第一配置；
B12、触发RRC连接恢复过程；
需要说明的是，终端在触发RRC连接恢复过程进入连接态后，应该第一配置，接收下行数据，例如，接收多播或组播的下行数据。
B13、忽略第一寻呼组列表，所述第一寻呼组列表用于通知一个或多个由移动组标识指示的多播会话激活；
需要说明的是，这里的忽略可以理解为终端不解析第一寻呼组列表、不处理第一寻呼组列表；可选地，该第一寻呼组列表是包含在该寻呼消息中的，在此种情况下，该第一寻呼组列表是R17寻呼组列表(paging record list)。
进一步可选地，终端在接收到RRC释放消息之后且没有收到下行数据的去激活(deactivation)指示之前才会忽略第一寻呼组列表。
此种情况也可以理解为：终端只会解析R15 paging record list中的终端标识(例如，UE-ID)或者R18 paging record list中的TMGI。
可选地，所述第一条件包括以下至少之一：
B21、所述终端处于RRC非激活态；
例如，终端处于RRC非激活态的情况下，终端忽略第一寻呼组列表。
B22、所述终端加入了一个或多个由移动组标识指示的多播会话；
需要说明的是，该移动组标识可以指的是TMGI；此种情况指的是，终端加入了多播会话，需要进行MBS的接收。
例如，所述终端加入了一个或多个由移动组标识指示的多播会话，终端可以忽略第一寻呼组列表。
B23、移动组标识被包含在第二寻呼组列表中，所述第二寻呼组列表用于通知一个或多个由所述移动组标识指示的多播会话对应的第二配置变更，所述第二配置用于接收所述多播会话对应的下行数据；
需要说明的是，该第二寻呼组列表包含于该寻呼消息中，在此种情况下，该第二寻呼组列表是针对R18组寻呼(R18 group paging)消息的。
例如，在此种情况下，终端触发RRC连接恢复过程，也就是说，如果R18 paging record list包含了UE加入业务对应的TMGI，则终端触发RRC连接恢复过程，准备进入连接态；所述R18 paging record list用于通知终端进行RRC连接恢复(由于配置更新而需要转换到连接态重新获取配置，或者由于NW想让终端转换到连接态去接收多播业务)。
B24、所述终端正在应用所述第一配置接收下行数据；
例如，所述终端正在应用所述第一配置接收下行数据，终端可以忽略第一寻呼组列表。
B25、所述终端存储了所述第一配置；
例如，所述终端存储了所述第一配置，终端可以忽略第一寻呼组列表。
B26、所述第一配置被认为是有效的；
例如，所述第一配置被认为是有效的，终端可以忽略第一寻呼组列表。
B27、所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识；
此种情况可以理解为：所述寻呼消息的寻呼记录列表中包含的终端身份标识与所述终端的身份标识不相同。
例如，所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识，则终端触发RRC连接恢复过程。
需要说明的是，本申请实施例所说的寻呼消息包括寻呼无线网络临时标识(Paging Radio Network Temporary Identity，P-RNTI)加扰的PDCCH和寻呼信息(paging message)，该寻呼信息例如可以为PDSCH消息。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端接收寻呼消息，在满足第二条件的情况下，应用所述第一配置；
可选地，所述第二条件包括以下至少之一：
C101、所述终端处于RRC非激活态；
此种情况可以理解为，终端在处于RRC非激活态的情况下，若接收到寻呼消息，则应用第一配置进行下行数据的接收。
C102、所述终端加入了一个或多个由移动组标识指示的多播会话；
此种情况可以理解为，终端若加入了多播会话的情况下，若接收到寻呼消息，则应用第一配置进行多播会话的下行数据的接收。
C103、移动组标识被包含在第一寻呼组列表中；
此种情况可以理解为，若TMGI被包含在寻呼消息中的R17 paging record list中，则终端应用第一配置进行下行数据的接收。
C104、移动组标识被包含在第一寻呼组列表中、且所述移动组标识在所述第一寻呼记录列表中的元素存储位置对应的指示信息指示为业务激活，所述指示信息为第二寻呼记录列表中与所述元素存储位置所对应的元素的指示信息；
需要说明的是，第一寻呼组列表中会存在多个TMGI，第二寻呼记录列表中存在与第一寻呼组列表中的TMGI对应的指示信息，例如，该指示信息可以指示为true或者false，当指示信息指示为true时，表示对应的移动组标识所指示的业务为激活状态；当当指示信息指示为false时，表示对应的移动组标识所指示的业务为非激活状态；当业务为激活状态时，终端可以应用第一配置进行移动组标识所指示的业务的下行数据的接收。
C105、所述终端暂停接收下行数据；
终端暂停接收下行数据可以理解为：停止对应G-RNTI关联的所有非连续接收(Discontinuous Reception，DRX)定时器，挂起多播无线承载(multicast radio bearer，MRB)，保持MRB对应分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)状态变量的值不变；同时，终端继续保持之前存储的配置。
C106、所述终端未应用所述第一配置接收下行数据；
C107、所述终端存储了所述第一配置；
C108、所述第一配置被认为是有效；
C109、所述终端接收到所述下行数据的去激活指示，所述下行数据的去激活指示用于指示停止接收所述下行数据；
可选地，此种情况下可以理解为：UE在非激活态进行着下行数据接收的过程中，终端接收到所述下行数据的去激活指示，终端需要基于该去激活指示，暂停接收下行数据；具体的，终端的低层(lower layer)将该去激活指示通知高层(higher layer)，higher layer会暂停接收下行数据。
C110、所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
可选地，所述RRC消息中还包括：所述第一配置的生效时间偏移量；所述生效时间偏移量用于指示所述终端接收所述RRC消息或者目标组寻呼消息的时刻加上所述生效时间偏移量之后的时刻应用所述第一配置；
所述目标组寻呼消息为包含所述终端加入的一个或多个多播会话对应的移动组标识的寻呼消息。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端在RRC非激活态忽略第三配置，所述第三配置用于上行数据的传输。
例如，该第三配置可以为混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)反馈和/或物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源相关的配置；例如用于多播的PUCCH资源配置，HARQ码本相关配置。也就是说，终端在RRC非激活态不会应用第三配置(即终端仅存储第三配置，但是忽略应用第三配置)，终端重新从RRC非激活态回到RRC连接态时(例如，接收到了上述的R18 paging record list中包含终端加入业务对应的TMGI)，才应用第三配置。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端在RRC非激活态接收下行数据的过程中，在收到所述下行数据的去激活指示的情况下，停止接收所述下行数据。
需要说明的是，终端在RRC非激活态接收下行数据的过程可以理解为满足以下情况：
所述终端在应用所述第一配置接收下行数据；
所述终端存储了所述第一配置；
所述第一配置被认为是有效的。
终端停止接收下行数据可以理解为，终端暂停下行数据的接收。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端接收寻呼消息，在所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识的情况下，执行第三操作；
其中，所述第三操作包括以下任意一项：
D11、忽略第一寻呼组列表；
需要说明的是，忽略第一寻呼组列表可以理解为不解释第一寻呼组列表、不处理第一寻呼组列表。
D12、忽略第二寻呼组列表；
需要说明的是，忽略第二寻呼组列表可以理解为不解释第二寻呼组列表、不处理第二寻呼组列表。
可以理解为，终端收到R15寻呼消息，该寻呼消息中包含与终端的身份标识相同的终端身份标识，则终端可以忽略R17 paging record list和/或R18 paging record list，或者，终端也可以继续处理R17 paging record list和/或R18 paging record list。
可选地，本申请的另一实施例中，所述终端根据所述配置指示信息，在RRC非激活态接收下行数据的实现方式，包括：
所述终端接收寻呼消息，在满足第三条件的情况下，触发下行小数据传输过程，且在RRC非激活态接收下行小数据传输的数据；
其中，所述第三条件包括以下至少一项：
E11、下行路损参考对应的测量值大于或等于第一门限；
E12、所述终端处于RRC非激活态；
E13、所述第一指示信息指示下行小数据传输；
E14、第一配置被指示；
E15、所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识；
此种情况可以理解为：所述寻呼消息的寻呼记录列表中包含的终端身份标识与所述终端的身份标识相同。
E16、所述寻呼消息的寻呼记录列表中包含的与所述终端的身份标识相匹配的终端身份标识对应的第二指示信息指示下行小数据传输。
需要说明的是，终端在满足上述的E11-E16中的任一项或多项的情况下，可以在RRC非激活态进行下行小数据传输的接收。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端在挂起DRB对应的PDCP实体时，维持PDCP状态变量的值不变。
需要说明的是，可选地，该DRB可以为小数据传输数据承载(SDT-DB)。
可选地，终端可以在接收到RRC消息时，维持PDCP状态变量的值不变；在接收到 寻呼消息，且在第一指示信息指示下行小数据传输的情况下，触发下行小数据传输过程，在RRC非激活态接收下行小数据传输的数据。
可选地，本申请的另一实施例中，所述方法还包括：
在触发下行小数据传输过程的情况下，所述终端使用目标资源发送上行消息后，在RRC非激活态接收下行小数据传输的数据；
其中，所述目标资源包括以下至少之一：
F11、用于随机接入过程的消息一(Msg1)发送的第一随机接入资源；
需要说明的是，本申请中提到的第一随机接入资源可以包括前导码(preamble)资源、随机接入机会(RACH Occasion，RO)资源等，其中，RACH为随机接入(Random Access Channel)的英文缩写。
可选地，该第一随机接入资源可以用于以下过程中的至少一项：初始接入过程、RRC连接恢复过程、上行小数据传输过程。
F12、用于随机接入过程的消息A(MsgA)发送的第二随机接入资源；
需要说明的是，本申请中提到的第二随机接入资源可以包括preamble资源、RO资源等。
可选地，该第二随机接入资源可以用于以下过程中的至少一项：初始接入过程、RRC连接恢复过程、上行小数据传输过程。
F13、第一配置授权资源，所述第一配置授权资源包含在第一配置中；
F14、用于上行小数据传输过程的第二配置授权资源。
需要说明的是，该第一配置授权资源和第二配置授权资源使用于终端配置授权过程中；该第一配置授权资源和第二配置授权资源可以相同也可以不同。
也就是说，此种情况下，终端先进行上行消息的发送，进而接收网络侧反馈的下行数据。
可选地，本申请的另一实施例中，所述方法还包括：
在触发下行小数据传输过程的情况下，所述终端在满足第四条件的情况下，选择第一配置授权资源或者第二配置授权资源作为目标资源；在不满足第四条件的情况下，选择第一随机接入资源或者第二随机接入资源作为目标资源；
其中，所述第四条件包括以下至少一项：
H11、下行路损参考对应的测量值大于或等于第二门限；
需要说明的是，所述第二门限用于上行小数据传输过程；也就是说，若下行路损参考对应的测量值大于或等于第二门限，则终端可以选择使用第一配置授权资源或第二配置授权资源进行上行消息的发送；若若下行路损参考对应的测量值小于第二门限，则终端可以选择使用第一随机接入资源或者第二随机接入资源进行上行消息的发送。
H12、定时提前量(Timing Advance，TA)有效；
例如，若TA有效，则终端可以选择使用第一配置授权资源或第二配置授权资源进行 上行消息的发送；若TA无效，则终端可以选择使用第一随机接入资源或者第二随机接入资源进行上行消息的发送。
H13、所述第一配置授权资源被配置；
例如，若第一配置授权资源被配置，则终端可以选择使用第一配置授权资源进行上行消息的发送；若第一配置授权资源未被配置，则终端可以选择使用第一随机接入资源或者第二随机接入资源进行上行消息的发送。
H14、所述第二配置授权资源被配置；
例如，若第二配置授权资源被配置，则终端可以选择使用第二配置授权资源进行上行消息的发送；若第二配置授权资源未被配置，则终端可以选择使用第一随机接入资源或者第二随机接入资源进行上行消息的发送。
H15、所述第一配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第三门限；
例如，若第一配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第三门限，则终端可以选择使用第一配置授权资源进行上行消息的发送；若第一配置授权资源对应的一个或多个下行参考信号中所有的下行参考信号的测量值均小于第三门限，则终端可以选择使用第一随机接入资源或者第二随机接入资源进行上行消息的发送。
H16、所述第二配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第四门限。
例如，若第二配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第四门限，则终端可以选择使用第二配置授权资源进行上行消息的发送；若第二配置授权资源对应的一个或多个下行参考信号中所有的下行参考信号的测量值均小于第四门限，则终端可以选择使用第一随机接入资源或者第二随机接入资源进行上行消息的发送。
可选地，本申请的另一实施例中，所述方法还包括：
在触发下行小数据传输过程的情况下，所述终端在满足第五条件的情况下，执行第五操作；
可选地，所述第五操作包括以下至少一项：
J11、所述终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息；
需要说明的是，此种情况下，会为上行小数据传输配置特定的随机接入资源，终端可以在随机接入过程的上行小数据传输过程对应的随机接入资源上进行上行消息的发送。
J12、所述终端使用基于配置授权的上行小数据传输过程对应的配置授权发送上行消息；
需要说明的是，此种情况下，会为上行小数据传输配置特定的配置授权资源，终端可 以使用上行小数据传输过程对应的配置授权资源上进行上行消息的发送。
J13、对包含公共控制信道(Common Control CHannel，CCCH)消息的媒体接入控制协议数据单元(Medium Access Control Protocol Data Unit，MAC PDU)进行重构；
可选地，重构可以理解为进行比特填充(padding)得到新的MAC PDU。
其中，所述第五条件包括以下至少一项：
J21、所述终端未进行公共控制信道消息的初次传输；
例如，终端未进行公共控制信道消息的初次传输的情况下，对包含公共控制信道消息的媒体接入控制协议数据单元(Medium Access Control Protocol Data Unit，MAC PDU)进行重构。
J22、所述终端未生成包含公共控制信道消息的MAC PDU；
例如，终端未生成包含公共控制信道消息的MAC PDU的情况下，对包含公共控制信道消息的媒体接入控制协议数据单元(Medium Access Control Protocol Data Unit，MAC PDU)进行重构。
J23、存在基于随机接入过程的上行小数据传输过程的触发条件；
例如，在存在基于随机接入过程的上行小数据传输过程的触发条件的情况下，终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息。
J24、存在基于配置授权的上行小数据传输过程的触发条件；
例如，在存在基于配置授权的上行小数据传输过程的触发条件的情况下，终端基于配置授权的上行小数据传输过程对应的配置授权发送上行消息。
J25、随机接入响应消息的接收失败次数大于或等于A次，或者，竞争解决失败次数大于或等于B次，其中，A、B为大于或等于1的整数；
需要说明的是，该A和B的取值为网络侧设备为终端配置的。
例如，若随机接入响应消息的接收失败次数大于或等于A次，则终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息；再例如，若竞争解决失败次数大于或等于B次，则终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息。
可选地，本申请的另一实施例中，所述方法还包括：
在发送第一条公共控制信道消息或在触发下行小数据传输过程的情况下，所述终端启动第一定时器；
其中，在所述终端进行下行小数据传输过程期间，所述第一定时器运行。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端在收到第一条专用传输信道(Dedicated Transmission Channel，DTCH)消息的情况下，重启所述第一定时器。
可选地，本申请的另一实施例中，所述方法还包括：
在所述第一定时器超时的情况下，所述终端进入空闲态，释放所述第一配置。
也就是说，当第一定时器超时，则说明终端不能够再进行下行小数据传输，此时终端可以释放连接，不再应用第一配置，从而回到空闲态，进而实现节能。
可选地，本申请的另一实施例中，所述方法还包括：
所述终端触发基于配置授权的上行小数据传输过程，在满足第六条件的情况下，执行第六操作；在不满足第六条件的情况下，执行第七操作；
可选地，所述第六操作包括以下至少之一：
K11、所述终端使用用于节能(reduced capability，RedCap)的初始上行部分带宽(Bandwidth Part，BWP)进行基于配置授权的上行小数据传输过程；
K12、所述终端使用用于RedCap的初始下行BWP上监听物理下行控制信道。
可选地，该第七操作包括以下至少之一：
K21、所述终端使用初始上行BWP进行基于配置授权的上行小数据传输过程；
K22、所述终端使用所述初始下行BWP上监听物理下行控制信道。
具体地，所述第六条件包括以下至少之一：
K11、所述终端为RedCap终端；
也就是说，在终端为节能RedCap终端的情况下，终端能够使用用于RedCap的初始上行BWP进行基于配置授权的上行小数据传输过程，和/或终端使用用于RedCap的初始下行BWP上监听物理下行控制信道；否则，终端使用初始上行BWP进行基于配置授权的上行小数据传输过程，和/或使用所述初始下行BWP上监听物理下行控制信道。
K12、用于RedCap的初始上行BWP被配置在选择的上行载波上；
也就是说，在用于RedCap的初始上行BWP被配置在选择的上行载波上的情况下，终端能够使用用于RedCap的初始上行BWP进行基于配置授权的上行小数据传输过程；否则，终端使用初始上行BWP进行基于配置授权的上行小数据传输过程。
K13、所述终端处于RRC非激活态；
也就是说，在终端处于RRC非激活态的情况下，终端能够使用用于RedCap的初始上行BWP进行基于配置授权的上行小数据传输过程，和/或终端使用用于RedCap的初始下行BWP上监听物理下行控制信道；否则，终端使用初始上行BWP进行基于配置授权的上行小数据传输过程，和/或使用所述初始下行BWP上监听物理下行控制信道。
K14、用于RedCap的初始下行BWP被配置；
也就是说，在用于RedCap的初始下行BWP被配置的情况下，终端使用用于RedCap的初始下行BWP上监听物理下行控制信道；否则，终端使用所述初始下行BWP上监听物理下行控制信道。
需要说明的是，通过本申请实施例，终端可以实现在RRC非激活态进行MBS的数据接收，也能够实现SDT的数据接收，下面分别在MBS场景以及SDT场景下对本申请的具体应用举例说明如下。
应用情况一、MBS场景
终端接收收到RRC释放消息，该RRC释放消息中携带配置指示信息，所述配置指示信息包括以下至少一项：
第一指示信息，所述第一指示信息用于指示第一操作；
第一配置，所述第一配置用于下行数据的接收，此种情况下该第一配置为下行数据接收的多播配置；
其中，所述第一操作包括以下至少之一：
存储第一配置；
应用第一配置。
进一步地，若第一操作包括存储第一配置和应用第一配置，则终端存储并应用多播配置(可选地，终端认为多播配置有效)，根据该多播配置在RRC非激活态进行多播接收。此外，终端还会忽略R17 paging record list(可选地，在接收到RRC释放消息之后且没有收到去激活指示之前才会忽略R17 paging record list)，或者，UE只会解析R15paging record list中的终端标识或者R17 paging record list中的TMGI；
若第一操作包括存储第一配置，则终端存储多播配置(可选地，终端认为多播配置有效)。此外，在终端接收到所述RRC释放消息之后接收到第一条寻呼消息(包含终端加入业务对应的TMGI)并且R17 paging record list包括了终端加入业务对应TMGI(或者进一步的，该终端加入业务TMGI所在R17 paging record list的元素对应的R18 paging record list对应元素指示信息为业务激活)，则根据第一配置开始在RRC非激活态进行多播接收(具体为：触发MAC层进行DRX操作，指示TCI状态给lower Layer，初始化用用于多播业务的半持续调度(Semi-Persistent Scheduling，SPS))。
进一步地，如果所述R18 paging record list包含了包含终端加入业务对应的TMGI，则终端触发RRC恢复过程，准备进入连接态；所述R18 paging record list用于通知终端进行RRC连接恢复(由于配置更新而需要转换到连接态重新获取配置，或者由于NW想让终端转换到连接态去接收多播业务)。
额外地，RRC释放消息中还包括：所述第一配置的生效时间偏移量；终端在收到RRC释放消息或者有终端加入的业务对应的TMGI的组寻呼消息后偏移所述生效时间偏移量后才应用多播配置。
额外地，终端在存储配置时忽略应用HARQ反馈和/或PUCCH资源相关的配置(例如存储但应用用于多播的PUCCH资源配置，HARQ码本相关配置)；终端重新从RRC非激活态回到RRC连接态时(例如，接收到了上述的R18 paging record list中包含终端加入业务对应的TMGI)，才应用上述配置。
进一步地，若终端在RRC非激活态进行着多播接收，而且收到多播数据接收的去激活(deactivation)指示(该指示可以是per G-RNTI，或者是per MAC，或者关联多个G-RNTI，具体多个G-RNTI的关联是通过配置指示)，则终端的lower layer通知higher layer，higher layer会暂停多播接收(例如，停止对应G-RNTI关联的所有DRX定时器，挂起MRB，保 持MRB对应PDCP状态变量的值不变)，继续保持之前存储的配置。
进一步地，(如果UE存储了多播配置，而且)在终端接收到多播数据接收的去激活指示之后接收到第一条寻呼消息(包含终端加入的业务对应的TMGI)并且寻呼消息的中R17 paging record list包括了终端加入的业务对应的TMGI(或者进一步的，该终端加入业务TMGI所在R17 paging record list的元素对应的R18 paging record list对应元素指示信息为业务激活)，则根据配置开始在RRC非激活态进行多播接收。
进一步地，如果终端收到individual paging，忽略R17paging record list、R18paging record list，或者继续处理R17paging record list、R18paging record list。
需要说明的是，R18 paging record list分成两部分，part 1用于是R17paging record list(TMGI)+R18激活处于活动状态(activation in INACTIVE)(1bit指示信息，枚举类型)，part 2是TMGI list是只有R18去连接态。Part 1和part 2是共属于choice结构。如果只有R17paging record list，则R17和R18的非激活态终端都需要进入去RRC连接态才能接收下行数据。
如图3所示，为此种情况下的终端接收消息及处理示例，图3中终端1接收到RRC释放消息，在接收到R17寻呼消息时，应用多播配置，收到多播接收的去激活指示时，暂停多播接收，在之后再次接收到R17寻呼时，继续进行多播接收；在收到R18寻呼时，终端需要退出非激活态，进入连接态，额外地，如果终端在进行多播接收期间收到R18寻呼，则在进入连接态的过程中也继续进行多播接收，进入连接态后也继续多播接收。再额外地，如果终端在暂停多播接收期间收到R18寻呼，则在进入连接态后也继续进行多播接收。图3中的终端2接收到RRC释放消息，存储并应用多播配置，直至多播传输停止；图3中的终端3接收到RRC释放消息时，存储并应用多播配置，在接收到R18寻呼时，进行RRC连接恢复。
应用情况二、SDT场景
终端接收RRC释放消息，该RRC释放消息中携带配置指示信息，所述配置指示信息包括以下至少一项：
第一指示信息，所述第一指示信息用于指示第一操作，所述第一操作包括下行小数据传输；
第一配置，所述第一配置用于下行数据的接收。
终端基于该配置指示信息，可以执行如下之一：
保持DRB对应PDCP状态变量的值不变；
收到寻呼消息后进行下行小数据传输过程；
进一步地，下行小数据传输过程的触发条件包括至少之一：
下行路损参考对应的测量值大于或等于第一门限
寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识；
寻呼消息的寻呼记录列表中包含的与所述终端的身份标识相匹配的终端身份标识对 应的第二指示信息指示下行小数据传输。
额外地，如果此时存在基于随机接入过程的上行小数据传输过程的触发条件，则终端可以使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息，此时可以理解为上行小数据传输优先于下行小数据传输。
额外的，在仅满足下行小数据传输过程的触发条件的情况下，终端使用下行小数据传输过程对应的专用RO资源。
进一步地，若使用专用RO资源，随机接入响应消息的接收失败次数大于或等于A次后，且存在存在基于随机接入过程的上行小数据传输过程的触发条件，则述终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息。
进一步地，在发送第一条公共控制信道消息或在触发下行小数据传输过程的情况下，所述终端启动第一定时器。
终端在收到第一条DTCH消息的情况下，重启所述第一定时器。
在所述第一定时器超时的情况下，所述终端进入空闲态，释放所述第一配置。
如图4所示，为此种情况下的终端接收消息及处理示例，图4中终端1接收到RRC释放消息，在收到R15寻呼时，因不满足SDT触发条件，不进行SDT；终端恢复RRC连接，在发送RRC恢复请求时，启动第一定时器，执行SDT，在接收到下行数据时，重启第一定时器，再次接收到RRC释放消息后终端释放连接，进入空闲态。
需要说明的是，本申请的至少一个实施例，能够达到如下有益效果：
对于进行MBS的终端，定义终端在不同场景下接收到组寻呼消息所包含的内容以及对应的终端处理行为，尽可能减少组寻呼消息的开销，并让处于RRC非激活态的终端顺利地进行多播业务数据的接收，或者进行终端状态转换。
对于进行SDT的终端，允许在RRC释放消息中携带小数据传输的指示，随后SDT终端在RRC非激活态下根据监听到的寻呼消息是否有自己的终端的标识信息以及下行小数据传输触发的条件，进行下行小数据传输的数据接收。
如图5所示，本申请实施例提供一种信息传输方法，包括：
步骤501，网络侧设备向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
可选地，所述配置指示信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示第一操作；
第一配置，所述第一配置为用于接收下行数据的配置；
其中，第一操作包括以下至少之一：
存储第一配置；
应用第一配置；
下行小数据传输。
需要说明的是，上述实施例中所有关于网络侧设备的描述均适用于应用于网络侧设备 侧的该信息传输方法的实施例中，也能达到与之相同的技术效果，在此不再赘述。
如图6所示，本申请实施例的数据接收装置600，应用于终端，包括：
第一接收模块601，用于接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；
第二接收模块602，用于根据所述配置指示信息，在RRC非激活态接收下行数据。
可选地，所述配置指示信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示第一操作；
第一配置，所述第一配置用于下行数据的接收；
其中，所述第一操作包括以下至少之一：
存储第一配置；
应用第一配置；
下行小数据传输。
可选地，所述装置还包括：
第一执行模块，用于接收寻呼消息，在满足第一条件的情况下，执行第二操作；
其中，所述第二操作包括以下至少一项：
触发RRC连接恢复过程；
忽略第一寻呼组列表，所述第一寻呼组列表用于通知一个或多个由移动组标识指示的多播会话激活；
应用所述第一配置；
所述第一条件包括以下至少之一：
所述终端处于RRC非激活态；
所述终端加入了一个或多个由移动组标识指示的多播会话；
移动组标识被包含在第二寻呼组列表中，所述第二寻呼组列表用于通知一个或多个由所述移动组标识指示的多播会话对应的第二配置变更，所述第二配置用于接收所述多播会话对应的下行数据；
所述终端正在应用所述第一配置接收下行数据；
所述终端存储了所述第一配置；
所述第一配置被认为是有效的；
所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
可选地，所述装置还包括：
第二执行模块，用于接收寻呼消息，在满足第二条件的情况下，应用所述第一配置；
其中，所述第二条件包括以下至少之一：
所述终端处于RRC非激活态；
所述终端加入了一个或多个由移动组标识指示的多播会话；
移动组标识被包含在第一寻呼组列表中；
移动组标识被包含在第一寻呼组列表中、且所述移动组标识在所述第一寻呼记录列表中的元素存储位置对应的指示信息指示为业务激活，所述指示信息为第二寻呼记录列表中与所述元素存储位置所对应的元素的指示信息；
所述终端暂停接收下行数据；
所述终端未应用所述第一配置接收下行数据；
所述终端存储了所述第一配置；
所述第一配置被认为是有效；
所述终端接收到所述下行数据的去激活指示，所述下行数据的去激活指示用于指示停止接收所述下行数据；
所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
可选地，所述RRC消息中还包括：所述第一配置的生效时间偏移量；所述生效时间偏移量用于指示所述终端接收所述RRC消息或者目标组寻呼消息的时刻加上所述生效时间偏移量之后的时刻应用所述第一配置；
所述目标组寻呼消息为包含所述终端加入的一个或多个多播会话对应的移动组标识的寻呼消息。
可选地，所述装置，还包括：
第三执行模块，用于在RRC非激活态忽略第三配置，所述第三配置用于上行数据的传输。
可选地，所述装置，还包括：
第四执行模块，用于在RRC非激活态接收下行数据的过程中，在收到所述下行数据的去激活指示的情况下，停止接收所述下行数据。
可选地，所述装置，还包括：
第五执行模块，用于接收寻呼消息，在所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识的情况下，执行第三操作；
其中，所述第三操作包括以下任意一项：
忽略第一寻呼组列表；
忽略第二寻呼组列表。
可选地，所述第二接收模块，用于：
接收寻呼消息，在满足第三条件的情况下，触发下行小数据传输过程，且在RRC非激活态接收下行小数据传输的数据；
其中，所述第三条件包括以下至少一项：
下行路损参考对应的测量值大于或等于第一门限；
所述终端处于RRC非激活态；
所述第一指示信息指示下行小数据传输；
第一配置被指示；
所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识；
所述寻呼消息的寻呼记录列表中包含的与所述终端的身份标识相匹配的终端身份标识对应的第二指示信息指示下行小数据传输。
可选地，所述装置，还包括：
第六执行模块，用于在挂起数据无线承载DRB对应的分组数据汇聚协议PDCP实体时，维持PDCP状态变量的值不变。
可选地，所述装置，还包括：
第三接收模块，用于在触发下行小数据传输过程的情况下，使用目标资源发送上行消息后，在RRC非激活态接收下行小数据传输的数据；
其中，所述目标资源包括以下至少之一：
用于随机接入过程的消息一发送的第一随机接入资源；
用于随机接入过程的消息A发送的第二随机接入资源；
第一配置授权资源，所述第一配置授权资源包含在第一配置中；
用于上行小数据传输过程的第二配置授权资源。
可选地，所述装置还包括：
第七执行模块，用于在触发下行小数据传输过程的情况下，在满足第四条件的情况下，选择第一配置授权资源或者第二配置授权资源作为目标资源；在不满足第四条件的情况下，选择第一随机接入资源或者第二随机接入资源作为目标资源；
其中，所述第四条件包括以下至少一项：
下行路损参考对应的测量值大于或等于第二门限，所述第二门限用于上行小数据传输过程；
定时提前量TA有效；
所述第一配置授权资源被配置；
所述第二配置授权资源被配置；
所述第一配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第三门限；
所述第二配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第四门限。
可选地，所述装置，还包括：
第八执行模块，用于在触发下行小数据传输过程的情况下，在满足第五条件的情况下，执行第五操作；
其中，所述第五条件包括以下至少一项：
所述终端未进行公共控制信道消息的初次传输；
所述终端未生成包含公共控制信道消息的媒体接入控制协议数据单元MAC PDU；
存在基于随机接入过程的上行小数据传输过程的触发条件；
存在基于配置授权的上行小数据传输过程的触发条件；
随机接入响应消息的接收失败次数大于或等于A次，或者，竞争解决失败次数大于或等于B次，其中，A、B为大于或等于1的整数；
所述第五操作包括以下至少一项：
所述终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息；
所述终端使用基于配置授权的上行小数据传输过程对应的配置授权发送上行消息；
对包含公共控制信道消息的MAC PDU进行重构。
可选地，所述装置，还包括：
启动模块，用于在发送第一条公共控制信道消息或在触发下行小数据传输过程的情况下，启动第一定时器；
其中，在所述终端进行下行小数据传输过程期间，所述第一定时器运行。
可选地，所述装置，还包括：
重启模块，用于在收到第一条专用传输信道DTCH消息的情况下，重启所述第一定时器。
可选地，所述装置，还包括：
释放模块，用于在所述第一定时器超时的情况下，进入空闲态，释放所述第一配置。
可选地，所述装置，还包括：
第九执行模块，用于触发基于配置授权的上行小数据传输过程，在满足第六条件的情况下，执行第六操作；在不满足第六条件的情况下，执行第七操作；
其中，所述第六条件包括以下至少之一：
所述终端为节能RedCap终端；
用于RedCap的初始上行部分带宽BWP被配置在选择的上行载波上；
所述终端处于RRC非激活态；
用于RedCap的初始下行BWP被配置；
所述第六操作包括以下至少之一：
所述终端使用用于RedCap的初始上行BWP进行基于配置授权的上行小数据传输过程；
所述终端使用用于RedCap的初始下行BWP上监听物理下行控制信道；
所述第七操作包括以下至少之一：
所述终端使用初始上行BWP进行基于配置授权的上行小数据传输过程；
所述终端使用所述初始下行BWP上监听物理下行控制信道。
需要说明的是，该装置实施例是与上述方法对应的，上述方法实施例中的所有实现方 式均适用于该装置实施例中，也能达到相同的技术效果。
本申请实施例中的数据接收装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的数据接收装置能够实现图2的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口用于接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；根据所述配置指示信息，在RRC非激活态接收下行数据。
可选地，所述配置指示信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示第一操作；
第一配置，所述第一配置用于下行数据的接收；
其中，所述第一操作包括以下至少之一：
存储第一配置；
应用第一配置；
下行小数据传输。
可选地，所述处理器，用于：
接收寻呼消息，在满足第一条件的情况下，执行第二操作；
其中，所述第二操作包括以下至少一项：
触发RRC连接恢复过程；
忽略第一寻呼组列表，所述第一寻呼组列表用于通知一个或多个由移动组标识指示的多播会话激活；
应用所述第一配置；
所述第一条件包括以下至少之一：
所述终端处于RRC非激活态；
所述终端加入了一个或多个由移动组标识指示的多播会话；
移动组标识被包含在第二寻呼组列表中，所述第二寻呼组列表用于通知一个或多个由所述移动组标识指示的多播会话对应的第二配置变更，所述第二配置用于接收所述多播会话对应的下行数据；
所述终端正在应用所述第一配置接收下行数据；
所述终端存储了所述第一配置；
所述第一配置被认为是有效的；
所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标 识。
可选地，所述处理器还用于：
接收寻呼消息，在满足第二条件的情况下，应用所述第一配置；
其中，所述第二条件包括以下至少之一：
所述终端处于RRC非激活态；
所述终端加入了一个或多个由移动组标识指示的多播会话；
移动组标识被包含在第一寻呼组列表中；
移动组标识被包含在第一寻呼组列表中、且所述移动组标识在所述第一寻呼记录列表中的元素存储位置对应的指示信息指示为业务激活，所述指示信息为第二寻呼记录列表中与所述元素存储位置所对应的元素的指示信息；
所述终端暂停接收下行数据；
所述终端未应用所述第一配置接收下行数据；
所述终端存储了所述第一配置；
所述第一配置被认为是有效；
所述终端接收到所述下行数据的去激活指示，所述下行数据的去激活指示用于指示停止接收所述下行数据；
所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
可选地，所述RRC消息中还包括：所述第一配置的生效时间偏移量；所述生效时间偏移量用于指示所述终端接收所述RRC消息或者目标组寻呼消息的时刻加上所述生效时间偏移量之后的时刻应用所述第一配置；
所述目标组寻呼消息为包含所述终端加入的一个或多个多播会话对应的移动组标识的寻呼消息。
可选地，所述处理器还用于：
在RRC非激活态忽略第三配置，所述第三配置用于上行数据的传输。
可选地，所述通信接口还用于：
在RRC非激活态接收下行数据的过程中，在收到所述下行数据的去激活指示的情况下，停止接收所述下行数据。
可选地，所述处理器还用于：
接收寻呼消息，在所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识的情况下，执行第三操作；
其中，所述第三操作包括以下任意一项：
忽略第一寻呼组列表；
忽略第二寻呼组列表。
可选地，所述通信接口还用于：
接收寻呼消息，在满足第三条件的情况下，触发下行小数据传输过程，且在RRC非激活态接收下行小数据传输的数据；
其中，所述第三条件包括以下至少一项：
下行路损参考对应的测量值大于或等于第一门限；
所述终端处于RRC非激活态；
所述第一指示信息指示下行小数据传输；
第一配置被指示；
所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识；
所述寻呼消息的寻呼记录列表中包含的与所述终端的身份标识相匹配的终端身份标识对应的第二指示信息指示下行小数据传输。
可选地，所述处理器还用于：
在挂起数据无线承载DRB对应的分组数据汇聚协议PDCP实体时，维持PDCP状态变量的值不变。
可选地，所述通信接口还用于：在触发下行小数据传输过程的情况下，使用目标资源发送上行消息后，在RRC非激活态接收下行小数据传输的数据；
其中，所述目标资源包括以下至少之一：
用于随机接入过程的消息一发送的第一随机接入资源；
用于随机接入过程的消息A发送的第二随机接入资源；
第一配置授权资源，所述第一配置授权资源包含在第一配置中；
用于上行小数据传输过程的第二配置授权资源。
可选地，所述处理器还用于：
在触发下行小数据传输过程的情况下，在满足第四条件的情况下，选择第一配置授权资源或者第二配置授权资源作为目标资源；在不满足第四条件的情况下，选择第一随机接入资源或者第二随机接入资源作为目标资源；
其中，所述第四条件包括以下至少一项：
下行路损参考对应的测量值大于或等于第二门限，所述第二门限用于上行小数据传输过程；
定时提前量TA有效；
所述第一配置授权资源被配置；
所述第二配置授权资源被配置；
所述第一配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第三门限；
所述第二配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第四门限。
可选地，所述处理器还用于：
在触发下行小数据传输过程的情况下，在满足第五条件的情况下，执行第五操作；
其中，所述第五条件包括以下至少一项：
所述终端未进行公共控制信道消息的初次传输；
所述终端未生成包含公共控制信道消息的媒体接入控制协议数据单元MAC PDU；
存在基于随机接入过程的上行小数据传输过程的触发条件；
存在基于配置授权的上行小数据传输过程的触发条件；
随机接入响应消息的接收失败次数大于或等于A次，或者，竞争解决失败次数大于或等于B次，其中，A、B为大于或等于1的整数；
所述第五操作包括以下至少一项：
所述终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息；
所述终端使用基于配置授权的上行小数据传输过程对应的配置授权发送上行消息；
对包含公共控制信道消息的MAC PDU进行重构。
可选地，所述处理器还用于：
在发送第一条公共控制信道消息或在触发下行小数据传输过程的情况下，启动第一定时器；
其中，在所述终端进行下行小数据传输过程期间，所述第一定时器运行。
可选地，所述处理器还用于：
在收到第一条专用传输信道DTCH消息的情况下，重启所述第一定时器。
可选地，所述处理器还用于：
在所述第一定时器超时的情况下，进入空闲态，释放所述第一配置。
可选地，所述处理器还用于：
触发基于配置授权的上行小数据传输过程，在满足第六条件的情况下，执行第六操作；在不满足第六条件的情况下，执行第七操作；
其中，所述第六条件包括以下至少之一：
所述终端为节能RedCap终端；
用于RedCap的初始上行部分带宽BWP被配置在选择的上行载波上；
所述终端处于RRC非激活态；
用于RedCap的初始下行BWP被配置；
所述第六操作包括以下至少之一：
所述终端使用用于RedCap的初始上行BWP进行基于配置授权的上行小数据传输过程；
所述终端使用用于RedCap的初始下行BWP上监听物理下行控制信道；
所述第七操作包括以下至少之一：
所述终端使用初始上行BWP进行基于配置授权的上行小数据传输过程；
所述终端使用所述初始下行BWP上监听物理下行控制信道。
该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图7为实现本申请实施例的一种终端的硬件结构示意图。
该终端700包括但不限于：射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709以及处理器710等中的至少部分部件。
本领域技术人员可以理解，终端700还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元704可以包括图形处理器(Graphics Processing Unit，GPU)7041和麦克风7042，图形处理器7041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072中的至少一种。触控面板7071，也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元701接收来自接入网设备的下行数据后，可以传输给处理器710进行处理；另外，射频单元701可以向网络侧设备发送上行数据。通常，射频单元701包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器709可以包括易失性存储器或非易失性存储器，或者，存储器709可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器709包括但不 限于这些和任意其它适合类型的存储器。
处理器710可包括一个或多个处理单元；可选地，处理器710集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器710中。
其中，所述射频单元701，用于：
接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；根据所述配置指示信息，在RRC非激活态接收下行数据。
可选地，所述配置指示信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示第一操作；
第一配置，所述第一配置用于下行数据的接收；
其中，所述第一操作包括以下至少之一：
存储第一配置；
应用第一配置；
下行小数据传输。
可选地，所述处理器710，还用于：
接收寻呼消息，在满足第一条件的情况下，执行第二操作；
其中，所述第二操作包括以下至少一项：
触发RRC连接恢复过程；
忽略第一寻呼组列表，所述第一寻呼组列表用于通知一个或多个由移动组标识指示的多播会话激活；
应用所述第一配置；
所述第一条件包括以下至少之一：
所述终端处于RRC非激活态；
所述终端加入了一个或多个由移动组标识指示的多播会话；
移动组标识被包含在第二寻呼组列表中，所述第二寻呼组列表用于通知一个或多个由所述移动组标识指示的多播会话对应的第二配置变更，所述第二配置用于接收所述多播会话对应的下行数据；
所述终端正在应用所述第一配置接收下行数据；
所述终端存储了所述第一配置；
所述第一配置被认为是有效的；
所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
可选地，所述处理器710，还用于：
接收寻呼消息，在满足第二条件的情况下，应用所述第一配置；
其中，所述第二条件包括以下至少之一：
所述终端处于RRC非激活态；
所述终端加入了一个或多个由移动组标识指示的多播会话；
移动组标识被包含在第一寻呼组列表中；
移动组标识被包含在第一寻呼组列表中、且所述移动组标识在所述第一寻呼记录列表中的元素存储位置对应的指示信息指示为业务激活，所述指示信息为第二寻呼记录列表中与所述元素存储位置所对应的元素的指示信息；
所述终端暂停接收下行数据；
所述终端未应用所述第一配置接收下行数据；
所述终端存储了所述第一配置；
所述第一配置被认为是有效；
所述终端接收到所述下行数据的去激活指示，所述下行数据的去激活指示用于指示停止接收所述下行数据；
所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
可选地，所述RRC消息中还包括：所述第一配置的生效时间偏移量；所述生效时间偏移量用于指示所述终端接收所述RRC消息或者目标组寻呼消息的时刻加上所述生效时间偏移量之后的时刻应用所述第一配置；
所述目标组寻呼消息为包含所述终端加入的一个或多个多播会话对应的移动组标识的寻呼消息。
可选地，所述处理器710，还用于：
在RRC非激活态忽略第三配置，所述第三配置用于上行数据的传输。
可选地，所述射频单元701，还用于：：
在RRC非激活态接收下行数据的过程中，在收到所述下行数据的去激活指示的情况下，停止接收所述下行数据。
可选地，所述处理器710，还用于：
接收寻呼消息，在所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识的情况下，执行第三操作；
其中，所述第三操作包括以下任意一项：
忽略第一寻呼组列表；
忽略第二寻呼组列表。
可选地，所述射频单元701，还用于：
接收寻呼消息，在满足第三条件的情况下，触发下行小数据传输过程，且在RRC非激活态接收下行小数据传输的数据；
其中，所述第三条件包括以下至少一项：
下行路损参考对应的测量值大于或等于第一门限；
所述终端处于RRC非激活态；
所述第一指示信息指示下行小数据传输；
第一配置被指示；
所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识；
所述寻呼消息的寻呼记录列表中包含的与所述终端的身份标识相匹配的终端身份标识对应的第二指示信息指示下行小数据传输。
可选地，所述处理器710，还用于：
在挂起数据无线承载DRB对应的分组数据汇聚协议PDCP实体时，维持PDCP状态变量的值不变。
可选地，所述射频单元701，还用于：在触发下行小数据传输过程的情况下，使用目标资源发送上行消息后，在RRC非激活态接收下行小数据传输的数据；
其中，所述目标资源包括以下至少之一：
用于随机接入过程的消息一发送的第一随机接入资源；
用于随机接入过程的消息A发送的第二随机接入资源；
第一配置授权资源，所述第一配置授权资源包含在第一配置中；
用于上行小数据传输过程的第二配置授权资源。
可选地，所述处理器710，还用于：
在触发下行小数据传输过程的情况下，在满足第四条件的情况下，选择第一配置授权资源或者第二配置授权资源作为目标资源；在不满足第四条件的情况下，选择第一随机接入资源或者第二随机接入资源作为目标资源；
其中，所述第四条件包括以下至少一项：
下行路损参考对应的测量值大于或等于第二门限，所述第二门限用于上行小数据传输过程；
定时提前量TA有效；
所述第一配置授权资源被配置；
所述第二配置授权资源被配置；
所述第一配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第三门限；
所述第二配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第四门限。
可选地，所述处理器710，还用于：
在触发下行小数据传输过程的情况下，在满足第五条件的情况下，执行第五操作；
其中，所述第五条件包括以下至少一项：
所述终端未进行公共控制信道消息的初次传输；
所述终端未生成包含公共控制信道消息的媒体接入控制协议数据单元MAC PDU；
存在基于随机接入过程的上行小数据传输过程的触发条件；
存在基于配置授权的上行小数据传输过程的触发条件；
随机接入响应消息的接收失败次数大于或等于A次，或者，竞争解决失败次数大于或等于B次，其中，A、B为大于或等于1的整数；
所述第五操作包括以下至少一项：
所述终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息；
所述终端使用基于配置授权的上行小数据传输过程对应的配置授权发送上行消息；
对包含公共控制信道消息的MAC PDU进行重构。
可选地，所述处理器710，还用于：
在发送第一条公共控制信道消息或在触发下行小数据传输过程的情况下，启动第一定时器；
其中，在所述终端进行下行小数据传输过程期间，所述第一定时器运行。
可选地，所述处理器710，还用于：
在收到第一条专用传输信道DTCH消息的情况下，重启所述第一定时器。
可选地，所述处理器710，还用于：
在所述第一定时器超时的情况下，进入空闲态，释放所述第一配置。
可选地，所述处理器710，还用于：
触发基于配置授权的上行小数据传输过程，在满足第六条件的情况下，执行第六操作；在不满足第六条件的情况下，执行第七操作；
其中，所述第六条件包括以下至少之一：
所述终端为节能RedCap终端；
用于RedCap的初始上行部分带宽BWP被配置在选择的上行载波上；
所述终端处于RRC非激活态；
用于RedCap的初始下行BWP被配置；
所述第六操作包括以下至少之一：
所述终端使用用于RedCap的初始上行BWP进行基于配置授权的上行小数据传输过程；
所述终端使用用于RedCap的初始下行BWP上监听物理下行控制信道；
所述第七操作包括以下至少之一：
所述终端使用初始上行BWP进行基于配置授权的上行小数据传输过程；
所述终端使用所述初始下行BWP上监听物理下行控制信道。
可选地，本申请实施例还提供一种终端，包括处理器，存储器，存储在存储器上并可在所述处理器上运行的程序或指令，该程序或指令被处理器执行时实现上述的数据接收方 法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，该存储介质可以是易失的或非易失的，计算机可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述的数据接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
如图8所示，本申请实施例还提供一种信息传输装置800，应用于网络侧设备，包括：
发送模块801，用于向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
可选地，所述配置指示信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示第一操作；
第一配置，所述第一配置为用于接收下行数据的配置；
其中，第一操作包括以下至少之一：
存储第一配置；
应用第一配置；
下行小数据传输。
需要说明的是，该装置实施例是与上述方法对应的装置，上述方法实施例中的所有实现方式均适用于该装置实施例中，也能达到相同的技术效果，在此不再赘述。
本申请实施例还提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
可选地，所述配置指示信息包括以下至少之一：
第一指示信息，所述第一指示信息用于指示第一操作；
第一配置，所述第一配置为用于接收下行数据的配置；
其中，第一操作包括以下至少之一：
存储第一配置；
应用第一配置；
下行小数据传输。
可选地，本申请实施例还提供一种网络侧设备，包括处理器，存储器，存储在存储器上并可在所述处理器上运行的程序或指令，该程序或指令被处理器执行时实现上述的信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
具体地，本申请实施例还提供了一种网络侧设备。如图9所示，该接入网设备900包括：天线901、射频装置902、基带装置903、处理器904和存储器905。天线901与射频装置902连接。在上行方向上，射频装置902通过天线901接收信息，将接收的信息发送给基带装置903进行处理。在下行方向上，基带装置903对要发送的信息进行处理，并发 送给射频装置902，射频装置902对收到的信息进行处理后经过天线901发送出去。
以上实施例中接入网设备执行的方法可以在基带装置903中实现，该基带装置903包括基带处理器。
基带装置903例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图9所示，其中一个芯片例如为基带处理器，通过总线接口与存储器905连接，以调用存储器905中的程序，执行以上方法实施例中所示的网络设备操作。
该接入网设备还可以包括网络接口906，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本申请实施例的接入网设备900还包括：存储在存储器905上并可在处理器904上运行的指令或程序，处理器904调用存储器905中的指令或程序执行图8所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，该存储介质可以是易失的或非易失的，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的接入网设备中的处理器。所述可读存储介质，可以是非易失性的，也可以是非瞬态的。可读存储介质，可以包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
可选地，如图10所示，本申请实施例还提供一种通信设备1000，包括处理器1001和存储器1002，存储器1002上存储有可在所述处理器1001上运行的程序或指令，例如，该通信设备1000为终端时，该程序或指令被处理器1001执行时实现上述数据接收方法实施例的各个步骤，且能达到相同的技术效果。该通信设备1000为网络侧设备时，该程序或指令被处理器1001执行时实现上述信息传输方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述数据接收方法或信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行上述的数据接收方法的步骤，所述网络侧设备可用于执行上述的信息传输方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素， 而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (24)

  1. 一种数据接收方法，包括：
    终端接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；
    所述终端根据所述配置指示信息，在RRC非激活态接收下行数据。
  2. 根据权利要求1所述的方法，其中，所述配置指示信息包括以下至少之一：
    第一指示信息，所述第一指示信息用于指示第一操作；
    第一配置，所述第一配置用于下行数据的接收；
    其中，所述第一操作包括以下至少之一：
    存储第一配置；
    应用第一配置；
    下行小数据传输。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    所述终端接收寻呼消息，在满足第一条件的情况下，执行第二操作；
    其中，所述第二操作包括以下至少一项：
    触发RRC连接恢复过程；
    忽略第一寻呼组列表，所述第一寻呼组列表用于通知一个或多个由移动组标识指示的多播会话激活；
    应用所述第一配置；
    所述第一条件包括以下至少之一：
    所述终端处于RRC非激活态；
    所述终端加入了一个或多个由移动组标识指示的多播会话；
    移动组标识被包含在第二寻呼组列表中，所述第二寻呼组列表用于通知一个或多个由所述移动组标识指示的多播会话对应的第二配置变更，所述第二配置用于接收所述多播会话对应的下行数据；
    所述终端正在应用所述第一配置接收下行数据；
    所述终端存储了所述第一配置；
    所述第一配置被认为是有效的；
    所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
  4. 根据权利要求2所述的方法，其中，所述方法还包括：
    所述终端接收寻呼消息，在满足第二条件的情况下，应用所述第一配置；
    其中，所述第二条件包括以下至少之一：
    所述终端处于RRC非激活态；
    所述终端加入了一个或多个由移动组标识指示的多播会话；
    移动组标识被包含在第一寻呼组列表中；
    移动组标识被包含在第一寻呼组列表中、且所述移动组标识在所述第一寻呼记录列表中的元素存储位置对应的指示信息指示为业务激活，所述指示信息为第二寻呼记录列表中与所述元素存储位置所对应的元素的指示信息；
    所述终端暂停接收下行数据；
    所述终端未应用所述第一配置接收下行数据；
    所述终端存储了所述第一配置；
    所述第一配置被认为是有效；
    所述终端接收到所述下行数据的去激活指示，所述下行数据的去激活指示用于指示停止接收所述下行数据；
    所述寻呼消息的寻呼记录列表中不包含与所述终端的身份标识相匹配的终端身份标识。
  5. 根据权利要求2至4任一项所述的方法，其中，所述RRC消息中还包括：所述第一配置的生效时间偏移量；所述生效时间偏移量用于指示所述终端接收所述RRC消息或者目标组寻呼消息的时刻加上所述生效时间偏移量之后的时刻应用所述第一配置；
    所述目标组寻呼消息为包含所述终端加入的一个或多个多播会话对应的移动组标识的寻呼消息。
  6. 根据权利要求1至5任一项所述的方法，其中，还包括：
    所述终端在RRC非激活态忽略第三配置，所述第三配置用于上行数据的传输。
  7. 根据权利要求1所述的方法，其中，还包括：
    所述终端在RRC非激活态接收下行数据的过程中，在收到所述下行数据的去激活指示的情况下，停止接收所述下行数据。
  8. 根据权利要求2至4任一项所述的方法，其中，还包括：
    所述终端接收寻呼消息，在所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识的情况下，执行第三操作；
    其中，所述第三操作包括以下任意一项：
    忽略第一寻呼组列表；
    忽略第二寻呼组列表。
  9. 根据权利要求2所述的方法，其中，所述终端根据所述配置指示信息，在RRC非激活态接收下行数据，包括：
    所述终端接收寻呼消息，在满足第三条件的情况下，触发下行小数据传输过程，且在RRC非激活态接收下行小数据传输的数据；
    其中，所述第三条件包括以下至少一项：
    下行路损参考对应的测量值大于或等于第一门限；
    所述终端处于RRC非激活态；
    所述第一指示信息指示下行小数据传输；
    第一配置被指示；
    所述寻呼消息的寻呼记录列表中包含与所述终端的身份标识相匹配的终端身份标识；
    所述寻呼消息的寻呼记录列表中包含的与所述终端的身份标识相匹配的终端身份标识对应的第二指示信息指示下行小数据传输。
  10. 根据权利要求1或9所述的方法，其中，还包括：
    所述终端在挂起数据无线承载DRB对应的分组数据汇聚协议PDCP实体时，维持PDCP状态变量的值不变。
  11. 根据权利要求9所述的方法，其中，还包括：
    在触发下行小数据传输过程的情况下，所述终端使用目标资源发送上行消息后，在RRC非激活态接收下行小数据传输的数据；
    其中，所述目标资源包括以下至少之一：
    用于随机接入过程的消息一发送的第一随机接入资源；
    用于随机接入过程的消息A发送的第二随机接入资源；
    第一配置授权资源，所述第一配置授权资源包含在第一配置中；
    用于上行小数据传输过程的第二配置授权资源。
  12. 根据权利要求11所述的方法，其中，所述方法还包括：
    在触发下行小数据传输过程的情况下，所述终端在满足第四条件的情况下，选择第一配置授权资源或者第二配置授权资源作为目标资源；在不满足第四条件的情况下，选择第一随机接入资源或者第二随机接入资源作为目标资源；
    其中，所述第四条件包括以下至少一项：
    下行路损参考对应的测量值大于或等于第二门限，所述第二门限用于上行小数据传输过程；
    定时提前量TA有效；
    所述第一配置授权资源被配置；
    所述第二配置授权资源被配置；
    所述第一配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第三门限；
    所述第二配置授权资源对应的一个或多个下行参考信号中至少有一个下行参考信号的测量值大于或等于第四门限。
  13. 根据权利要求9或11所述的方法，其中，所述方法还包括：
    在触发下行小数据传输过程的情况下，所述终端在满足第五条件的情况下，执行第五操作；
    其中，所述第五条件包括以下至少一项：
    所述终端未进行公共控制信道消息的初次传输；
    所述终端未生成包含公共控制信道消息的媒体接入控制协议数据单元MAC PDU；
    存在基于随机接入过程的上行小数据传输过程的触发条件；
    存在基于配置授权的上行小数据传输过程的触发条件；
    随机接入响应消息的接收失败次数大于或等于A次，或者，竞争解决失败次数大于或等于B次，其中，A、B为大于或等于1的整数；
    所述第五操作包括以下至少一项：
    所述终端使用基于随机接入过程的上行小数据传输过程对应的随机接入资源发送上行消息；
    所述终端使用基于配置授权的上行小数据传输过程对应的配置授权发送上行消息；
    对包含公共控制信道消息的MAC PDU进行重构。
  14. 根据权利要求9所述的方法，其中，还包括：
    在发送第一条公共控制信道消息或在触发下行小数据传输过程的情况下，所述终端启动第一定时器；
    其中，在所述终端进行下行小数据传输过程期间，所述第一定时器运行。
  15. 根据权利要求14所述的方法，其中，还包括：
    所述终端在收到第一条专用传输信道DTCH消息的情况下，重启所述第一定时器。
  16. 根据权利要求14所述的方法，其中，还包括：
    在所述第一定时器超时的情况下，所述终端进入空闲态，释放所述第一配置。
  17. 根据权利要求1所述的方法，其中，还包括：
    所述终端触发基于配置授权的上行小数据传输过程，在满足第六条件的情况下，执行第六操作；在不满足第六条件的情况下，执行第七操作；
    其中，所述第六条件包括以下至少之一：
    所述终端为节能RedCap终端；
    用于RedCap的初始上行部分带宽BWP被配置在选择的上行载波上；
    所述终端处于RRC非激活态；
    用于RedCap的初始下行BWP被配置；
    所述第六操作包括以下至少之一：
    所述终端使用用于RedCap的初始上行BWP进行基于配置授权的上行小数据传输过程；
    所述终端使用用于RedCap的初始下行BWP上监听物理下行控制信道；
    所述第七操作包括以下至少之一：
    所述终端使用初始上行BWP进行基于配置授权的上行小数据传输过程；
    所述终端使用所述初始下行BWP上监听物理下行控制信道。
  18. 一种信息传输方法，包括：
    网络侧设备向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
  19. 根据权利要求18所述的方法，其中，所述配置指示信息包括以下至少之一：
    第一指示信息，所述第一指示信息用于指示第一操作；
    第一配置，所述第一配置为用于接收下行数据的配置；
    其中，第一操作包括以下至少之一：
    存储第一配置；
    应用第一配置；
    下行小数据传输。
  20. 一种数据接收装置，应用于终端，所述装置包括：
    第一接收模块，用于接收无线资源控制RRC消息，所述RRC消息中携带配置指示信息；
    第二接收模块，用于根据所述配置指示信息，在RRC非激活态接收下行数据。
  21. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至17任一项所述的数据接收方法的步骤。
  22. 一种信息传输装置，应用于网络侧设备，所述装置包括：
    发送模块，用于向终端发送无线资源控制RRC消息，所述RRC消息中携带配置指示信息，所述配置指示信息使得所述终端在RRC非激活态接收下行数据。
  23. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求18或19所述的信息传输方法的步骤。
  24. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至19任一项所述的方法的步骤。
PCT/CN2023/126679 2022-11-04 2023-10-26 数据接收、信息传输方法、装置、终端及网络侧设备 WO2024093774A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211380073.9A CN118042649A (zh) 2022-11-04 2022-11-04 数据接收、信息传输方法、装置、终端及网络侧设备
CN202211380073.9 2022-11-04

Publications (1)

Publication Number Publication Date
WO2024093774A1 true WO2024093774A1 (zh) 2024-05-10

Family

ID=90929698

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/126679 WO2024093774A1 (zh) 2022-11-04 2023-10-26 数据接收、信息传输方法、装置、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN118042649A (zh)
WO (1) WO2024093774A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111836361A (zh) * 2019-08-12 2020-10-27 维沃移动通信有限公司 数据接收方法、发送方法、终端及网络设备
CN114679919A (zh) * 2019-09-30 2022-06-28 华为技术有限公司 配置方法和装置
CN115004605A (zh) * 2020-04-08 2022-09-02 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备
CN115024018A (zh) * 2020-04-07 2022-09-06 Oppo广东移动通信有限公司 非激活态下的数据发送、接收方法及装置、用户设备
WO2022194242A1 (zh) * 2021-03-19 2022-09-22 夏普株式会社 由用户设备执行的方法以及用户设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111836361A (zh) * 2019-08-12 2020-10-27 维沃移动通信有限公司 数据接收方法、发送方法、终端及网络设备
CN114679919A (zh) * 2019-09-30 2022-06-28 华为技术有限公司 配置方法和装置
CN115024018A (zh) * 2020-04-07 2022-09-06 Oppo广东移动通信有限公司 非激活态下的数据发送、接收方法及装置、用户设备
CN115004605A (zh) * 2020-04-08 2022-09-02 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备
WO2022194242A1 (zh) * 2021-03-19 2022-09-22 夏普株式会社 由用户设备执行的方法以及用户设备

Also Published As

Publication number Publication date
CN118042649A (zh) 2024-05-14

Similar Documents

Publication Publication Date Title
US20240224326A1 (en) Consistent LBT Failure Processing Method, and Terminal and Network-Side Device
WO2022042752A1 (zh) 物理下行控制信道的监听方法、装置和设备
WO2023030189A1 (zh) 监听方法、唤醒信号传输方法、装置、终端及网络侧设备
US20240129893A1 (en) Positioning measurement method, positioning configuration method, apparatus, and communication device
WO2022237615A1 (zh) 寻呼检测、处理方法、装置及通信设备
WO2022148431A1 (zh) 非连续接收drx配置切换的方法、装置及终端
WO2023093692A1 (zh) 监听寻呼提前指示的方法、装置、终端及网络侧设备
WO2024093774A1 (zh) 数据接收、信息传输方法、装置、终端及网络侧设备
WO2022184101A1 (zh) 间隙gap处理方法、装置、设备及存储介质
WO2022127850A1 (zh) Pdcch监听方法、终端和网络侧设备
WO2022063232A1 (zh) 确定终端行为的方法、指示终端行为的方法及装置
CN117377040A (zh) 唤醒信号监听方法、装置、电子设备、网络设备及介质
WO2023093629A1 (zh) 终端行为控制方法、终端及网络侧设备
WO2022143975A1 (zh) 搜索空间组切换方法和设备
CN115022815B (zh) 多播业务的接收方法、装置及电子设备
WO2022206648A1 (zh) 侧链路非连续接收的实现方法、装置及终端
WO2023169397A1 (zh) 非连续接收drx参数配置方法、装置、终端及网络侧设备
WO2023143413A1 (zh) 同步信号块接收方法、同步信号块发送方法及相关设备
US20230354471A1 (en) Search space group switching method and apparatus
WO2021258962A1 (zh) 数据下发方法、设备和存储介质
WO2023217092A1 (zh) 监听方法、装置、终端、网络侧设备及可读存储介质
WO2023179792A1 (zh) 反向散射通信的方法、装置及设备
WO2022022637A1 (zh) 寻呼消息的监听方法及装置、终端和可读存储介质
WO2022194177A1 (zh) 监听控制方法及相关设备
WO2023143550A1 (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: 23884706

Country of ref document: EP

Kind code of ref document: A1