WO2022007785A1 - 消息发送方法、接收方法、装置及通信设备 - Google Patents

消息发送方法、接收方法、装置及通信设备 Download PDF

Info

Publication number
WO2022007785A1
WO2022007785A1 PCT/CN2021/104705 CN2021104705W WO2022007785A1 WO 2022007785 A1 WO2022007785 A1 WO 2022007785A1 CN 2021104705 W CN2021104705 W CN 2021104705W WO 2022007785 A1 WO2022007785 A1 WO 2022007785A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
rrc
transmission
target
terminal
Prior art date
Application number
PCT/CN2021/104705
Other languages
English (en)
French (fr)
Inventor
钟婷婷
吴昱民
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to JP2022580816A priority Critical patent/JP2023532700A/ja
Priority to EP21838450.1A priority patent/EP4178310A4/en
Publication of WO2022007785A1 publication Critical patent/WO2022007785A1/zh
Priority to US18/149,228 priority patent/US20230156851A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application belongs to the field of communication technologies, and specifically relates to a message sending method, a receiving method, an apparatus, and a communication device.
  • RRC radio resource control
  • NON-RRC CONNECTED non-radio resource control
  • the RRC message can be sent only after other conditions for triggering the establishment or recovery of the RRC connection are satisfied and the RRC connection is successfully established or recovered. Therefore, the delay when the existing non-RRC connected state terminal sends the RRC message is relatively large.
  • the purpose of the embodiments of the present application is to provide a message sending method, receiving method, apparatus and communication device, so as to solve the problem that the existing non-RRC connection state terminal has a relatively large delay when sending an RRC message requiring activated AS security.
  • the present disclosure provides a message sending method, applied to a terminal, including:
  • the terminal In the case that the terminal is in the non-radio resource control RRC connected state and there is a need to send the target RRC message to the network side device, send the target RRC message in the non-RRC connected state;
  • the target RRC message is an RRC message of access stratum security that needs to be activated.
  • the present disclosure provides a message receiving method, applied to a network side device, including:
  • the target RRC message is an RRC message of access stratum security that needs to be activated; the target RRC message is when the terminal is in a non-RRC connected state and needs to send the target RRC message, in the Sent in non-RRC connected state.
  • the present disclosure provides a message sending apparatus, applied to a terminal, including:
  • the first sending module is configured to send the target RRC message in the non-RRC connected state when the terminal is in the non-RRC connected state and there is a need to send the target RRC message to the network side device:
  • the target RRC message is an RRC message of access stratum security that needs to be activated.
  • the present disclosure provides a message receiving apparatus, which is applied to a network side device, including:
  • a receiving module configured to receive the target RRC message from the terminal
  • the target RRC message is an RRC message of access stratum security that needs to be activated; the target RRC message is when the terminal is in a non-RRC connected state and needs to send the target RRC message, in the Sent in non-RRC connected state.
  • a terminal in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • the present disclosure provides a network-side device, the network-side device includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, the program or instruction being The processor, when executed, implements the steps of the method as described in the second aspect.
  • the present disclosure provides a readable storage medium, on which a program or an instruction is stored, and when the program or instruction is executed by a processor, implements the steps of the method according to the first aspect, or The steps of implementing the method of the second aspect.
  • the present disclosure provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used for running a program or an instruction, and the implementation is as described in the first aspect The steps of the method, or the steps of implementing the method according to the second aspect.
  • the terminal may send the target RRC message in the non-RRC connected state when it is in the non-RRC connected state and needs to send the target RRC message to the network side device, and the target RRC message needs to be activated.
  • RRC messages for access layer security. Therefore, the terminal can send the target RRC message only after other conditions for triggering the establishment or recovery of the RRC connection are satisfied and the RRC connection is successfully established or recovered, and the terminal can directly send the target RRC message in the non-RRC connection state, thereby reducing the time extension. Further, resource waste, energy consumption and the like can be avoided.
  • FIG. 1 is a block diagram of a wireless communication system provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a target RRC message sending process in Embodiment 1 of the present application.
  • FIG. 5 is a flowchart of a target RRC message sending process in Embodiment 3 of the present application.
  • FIG. 6 is a schematic structural diagram of a message sending apparatus provided by an embodiment of the present application.
  • FIG. 7 is a flowchart of a message receiving method provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a message receiving apparatus provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/” generally indicates that the associated objects are in an “or” relationship.
  • a and/or B means "A alone, B alone, and both A and B are present", and "at least one of A and B” also means "A alone, B alone, and both A and B” B exists in all three cases.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • 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
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the description below, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6 th Generation, 6G) communication system.
  • 6th generation 6 th Generation, 6G
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and 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 computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • PDA Personal Digital Assistant
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • the embodiment of the present application proposes that the NON-RRCCONNECTED UE needs to send an activated AS when there is an AS.
  • the method of sending the RRC message directly in the NON-RRCCONNECTED state when the RRC message of security is required by the network side device.
  • the RRC message requiring activated AS security may be referred to as a target RRC message. That is to say, the target RRC message mentioned in the following embodiments is an RRC message that needs to activate AS security.
  • the target RRC message may be an RRC message related to the configuration of the first transmission mode.
  • the terminal needs to send the target RRC message to the network side device:
  • the terminal supports transmission in the first transmission mode
  • the network supports the transmission of the first transmission mode; for example, the system message contains a corresponding indication;
  • the size of the media access control protocol data unit (Media Access Control Protocol Data Unit, MAC PDU) containing the target RRC message is less than or equal to the maximum transport block size (Transport Block Size, TBS) supported by the terminal defined based on the terminal type;
  • TBS Transport Block Size
  • the terminal satisfies at least one of the following: interested in the configuration of the first transmission mode, no longer interested in the configuration of the first transmission mode, and needs to update the configuration of the first transmission mode.
  • the above-mentioned first transmission mode can be understood as a transmission mode similar to PUR (Preconfigured Uplink Resource, preconfigured uplink resource) transmission or preconfigured PUSCH resource transmission of small data transmission (Small Data Transmission, SDT). , in some cases, it can also be understood as the PUR transmission mode or the SDT pre-configured PUSCH resource transmission mode, which is not limited.
  • the target RRC message may contain auxiliary information related to the configuration of the preconfigured PUSCH resources, such as a PURConfigurationRequest message. Taking the pre-configured PUSCH resource transmission mode for small data transmission as an example, the UE needs to send the target RRC message to the network side device under the condition that at least one of the following is satisfied:
  • the UE supports transmission in the way of pre-configured PUSCH resources
  • the network supports the transmission of the pre-configured PUSCH resource mode, such as the corresponding indication is included in the system message;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the maximum supported TBS of the UE defined based on the UE type
  • the UE is interested in the configuration of the preconfigured PUSCH resources, or is no longer interested, or needs to update the configuration of the preconfigured PUSCH resources.
  • the target RRC message may be an RRC message related to Multicast and Broadcast Service (MBS) counting (Counting), such as an MBSCountingResponse message.
  • MBS Multicast and Broadcast Service
  • the terminal needs to send the target RRC message to the network side device:
  • the terminal has MBS capability
  • the network supports MBS; for example, the corresponding indication is included in the system message;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the maximum TBS supported by the terminal defined based on the terminal type;
  • the RRC layer of the terminal receives the MBS counting-related control message (such as the MBSCountingRequest message) sent by the network side device;
  • the terminal is receiving or is interested in receiving at least one MBS service indicated in a control message related to MBS counting (eg, an MBSCountingRequest message).
  • a control message related to MBS counting eg, an MBSCountingRequest message.
  • the target RRC message may be an RRC message related to an MBS interest indication (Interest Indication), such as an MBSInterestIndication message.
  • MBSInterestIndication MBS interest indication
  • the terminal needs to send the target RRC message to the network side device:
  • the terminal has MBS capability
  • the network supports MBS; for example, the corresponding indication is included in the system message;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the maximum TBS supported by the terminal defined based on the terminal type;
  • the terminal receives the control information related to the MBS service sent by the network side device; for example, the control information related to the MBS service can be sent through a system message or dedicated RRC signaling;
  • the terminal enters or leaves the service area; for example, as soon as the UE enters the service area, or as soon as the UE leaves the service area;
  • MBS session starts or stops; for example, when the MBS session starts, or when the MBS session stops;
  • the cell or base station that transmits the control information related to the MBS service changes.
  • the target RRC message can also be any other RRC message that needs to activate AS security, which is not limited.
  • FIG. 2 is a flowchart of a method for sending a message provided by an embodiment of the present invention. The method is applied to a terminal. As shown in FIG. 2, the method includes the following steps:
  • Step 201 When the terminal is in a non-RRC connected state and there is a need to send a target RRC message to a network side device, send the target RRC message in a non-RRC connected state.
  • the target RRC message is an RRC message that needs to activate AS security.
  • the terminal may send the target RRC message in the non-RRC connected state when it is in the non-RRC connected state and there is a need to send the target RRC message to the network side device. Therefore, the terminal can send the target RRC message only after other conditions for triggering the establishment or recovery of the RRC connection are satisfied and the RRC connection is successfully established or recovered, and the terminal can directly send the target RRC message in the non-RRC connection state, thereby reducing the time extension. Further, resource waste, energy consumption and the like can be avoided.
  • the terminal may send the target RRC message in the non-RRC connection state by means of an RRC connection resume (RRC connection resume) process.
  • RRC connection resume RRC connection resume
  • the terminal may also trigger the RRC connection recovery process, generate an RRC recovery request or RRC recovery request 1 (RRCResumeRequest/RRCResumeRequest1) message, and submit the RRCResumeRequest/RRCResumeRequest1 message to the bottom layer; trigger the target RRC The generation (or generation) of the content of the message, and triggers the submission of the target RRC message to the underlying layer.
  • the RRCResumeRequest/RRCResumeRequest1 message and the target RRC message are generated in the RRC layer, and the bottom layer here is the protocol layer below the RRC layer, such as Packet Data Convergence Protocol (PDCP), Radio Link Control (Radio Link Control, RLC), MAC layer.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC layer MAC layer
  • the terminal may further set the value of the restoration cause ResumeCause.
  • the ResumeCause value can be at least one of the following:
  • the newly set ResumeCause value may be independent of the target RRC message, that is, unify all target RRC messages, such as MO-RRCmessage, and set the ResumeCause value to MO-RRCmessage.
  • the irrelevance to the target RRC message may be irrelevant to the message type or form of the target RRC message, or may be irrelevant to the content of the target RRC message.
  • the newly set ResumeCause value may be related to the target RRC message, such as "XX configuration request message", and the ResumeCause value is set to "XX configuration request message".
  • the target RRC message related may be related to the message type or form of the target RRC message, or related to the content of the target RRC message.
  • the terminal may also perform at least one of the following:
  • UAC check is performed by using the existing set access category (Access category) and/or access identity (Access identity(ies)). That is to reuse the existing Access category and/or Access identity(ies), for example, set the Access category to 7, Access identity to 0, etc.
  • UAC is checked by using the new set access category and/or access identity. That is to use the newly set Access category and/or Access identity(ies) to check the UAC.
  • the new Access category and/or Access identity(ies) may be independent of the target RRC message, that is, unify all the target RRC messages to the same value, for example, uniformly set the Access category to 11 and the Access identity to 6, etc. .
  • the irrelevance to the target RRC message may be irrelevant to the message type or form of the target RRC message, or may be irrelevant to the content of the target RRC message.
  • the new Access category and/or Access identities(ies) may be related to the target RRC message, for example, for "XX configuration request message", set the Access category to 11 and the Access identity to 6, etc.
  • the target RRC message related may be related to the message type or form of the target RRC message, or related to the content of the target RRC message.
  • the triggering situation for the generation of the content of the target RRC message may include at least one of the following:
  • the triggering situation at this time may include at least one of the following:
  • the triggering condition of submitting the target RRC message to the bottom layer it may include at least one of the following:
  • the terminal may use the first mathematical expression to store the content in the target RRC message, or not store the content in the target RRC message.
  • the above-mentioned first mathematical expression form may include at least one of the following: any mathematical expression form such as variables, arrays, and structures. That is to say, after the content of the target RRC message is generated, the terminal can store it in any mathematical expression such as a variable, an array, and/or a structure.
  • the target RRC message and the RRC recovery request or the RRC recovery request 1 message may be multiplexed in the same MAC PDU and sent to the network side device.
  • the composition of the MAC PDU can be at least one of the following:
  • the RRC Recovery Request or RRC Recovery Request 1 message precedes the target RRC message
  • the RRC Recovery Request or RRC Recovery Request 1 message follows the target RRC message.
  • the target RRC message sent by the terminal in the non-RRC connected state may be, but not limited to, sent through a random access procedure, transmission in the first transmission mode, or transmission in the second transmission mode.
  • the random access process may be a traditional random access process, such as a 2-step (2-step) random access process or a 4-step (4-step) random access process.
  • the transmission of the first transmission and the transmission of the second transmission involve completely different content.
  • the first transmission mode can be understood as a transmission mode similar to the pre-configured PUSCH resource transmission of PUR transmission or small data transmission (Small Data Transmission, SDT), and can also be understood as a PUR transmission mode or SDT in some cases.
  • the pre-configured PUSCH resource transmission mode can be understood as a transmission mode similar to the pre-configured PUSCH resource transmission of PUR transmission or small data transmission (Small Data Transmission, SDT), and can also be understood as a PUR transmission mode or SDT in some cases.
  • the second transmission mode can be understood as a transmission mode similar to Early Data Transmission (EDT) or RACH-based transmission of small data transmission, and can also be understood as EDT transmission mode or RACH for small data transmission in some cases -based transport method.
  • EDT Early Data Transmission
  • RACH-based transmission of small data transmission can also be understood as EDT transmission mode or RACH for small data transmission in some cases -based transport method.
  • the transmission in the first transmission mode is PUR transmission, pre-configured PUSCH resource transmission of SDT, or transmission similar to PUR, transmission of pre-configured PUSCH resources similar to SDT, and the like.
  • the transmission in the second transmission mode is, for example, EDT, RACH-based transmission similar to EDT, small data transmission, or RACH-based transmission similar to small data transmission.
  • Scheme 1 The UE completes the sending of the target RRC message through the traditional random access process (such as NR 2-step/4-step RACH).
  • the UE will trigger the RRC connection resume process, generate the RRCResumeRequest/RRCResumeRequest1 message and submit it to the bottom layer, trigger the generation of the content of the target RRC message, and trigger the submission of the target RRC message to the bottom layer.
  • the UE can set the ResumeCause value, at least one of the following:
  • ⁇ It has nothing to do with the target RRC message, that is, unify all the target RRC messages, such as MO-RRCmessage, and set the ResumeCause value to MO-RRCmessage;
  • the UE can perform at least any of the following:
  • ⁇ It has nothing to do with the target RRC message, that is, unify all the target RRC messages to the same value, for example, set the Access category to 11 and the Access identity to 6;
  • ⁇ It is related to the target RRC message. For example, if it is "XX configuration request message", set the Access category to 11 and the Access identity to 6.
  • the trigger time point for the generation of the target RRC message is at least any one of the following:
  • the UE needs to send the target RRC message to the network side device, it immediately triggers the generation of the content of the target RRC message;
  • the UE first triggers the RRC connection resume process, and then triggers the generation of the content of the target RRC message in the RRC connection resume process; and at least one of the following:
  • the UE triggers the generation of the content of the target RRC message in the Initiation of the RRC connection resume process
  • the UE may store the content of the target RRC message as a variable, an array and/or a structure or any other mathematical expression, or not store it.
  • the trigger time point when the target RRC message is submitted to the bottom layer at least one of the following:
  • RRC recovery request or RRC recovery request 1 message transmission related operation process immediately trigger the submission of the target RRC message to the bottom layer
  • the MAC layer of the UE initiates the random access process, and submits a MAC PDU with both RRCResumeRequest/RRCResumeRequest1 and the target RRC message to the bottom layer and sends it to the network side device.
  • the trigger event of random access is at least any one of the following:
  • ⁇ It has nothing to do with the target RRC message, that is, unify all the target RRC messages, such as MO-RRCmessage;
  • ⁇ It is related to the target RRC message, for example, the sending of a single target RRC message is used as a trigger event, such as "XX configuration request message" and so on.
  • RAR Random Access Response
  • MsgA physical uplink shared channel Physical Uplink Shared.
  • Channel PUSCH
  • synchronization signal block Synchronization Signal and PBCH block, SSB
  • Physical Downlink Control Channel Physical Downlink Control Channel, PDCCH
  • the target RRC message and the RRCResumeRequest/RRCResumeRequest1 message are multiplexed in the same MAC PDU and sent to the network side device, at least any of the following:
  • the RRCesumeRequest/RRCResumeRequest1 message is located before the target RRC message; in other words, the RRCesumeRequest/RRCResumeRequest1 message can be located in the front of the MAC PDU, and the target RRC message is located in the back of the MAC PDU;
  • the RRCesumeRequest/RRCResumeRequest1 message is located after the target RRC message; in other words, it can be: the target RRC message is in front of the MAC PDU, and the RRCResumeRequest/RRCResumeRequest1 message is in the back of the MAC PDU.
  • Solution 2 The UE completes the sending of the target RRC message through transmission in the first transmission mode (such as PUR transmission, PUR-like transmission, etc.).
  • the RRC layer of the UE will request the RRC connection resumption and initiate the transmission of the first transmission mode (such as PUR transmission), triggering
  • the RRCResume process generates an RRCResumeRequest/RRCResumeRequest1 message and submits it to the bottom layer, triggers the generation of the content of the target RRC message, and triggers the submission of the target RRC message to the bottom layer.
  • the initiation condition of the transmission of the first transmission mode may be at least one of the following:
  • the UE requests RRC connection recovery at the RRC layer; the value of RRCResumeCause is at least any of the following:
  • the UE supports the transmission of the first transmission mode
  • the network supports the transmission of the first transmission mode, for example, the corresponding indication is included in the system message;
  • the UE has a valid configuration of the first transmission mode
  • nextHopChainingCount value is provided by the suspendConfig in the latest (ie last) RRCRelease message
  • the size of the MAC PDU containing the target RRC message is less than or equal to the TBS defined in the configuration of the first transmission mode.
  • the initiation condition of PUR transmission is at least any one of the following:
  • the UE requests RRC connection recovery at the RRC layer
  • ⁇ UE has a valid PUR configuration
  • the UE has a stored nextHopChainingCount value; and this nextHopChainingCount value is provided by the suspendConfig in the latest RRCRelease message;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the TBS defined in the PUR configuration.
  • the UE can set the ResumeCause value, and its value is consistent with the value specifically selected above.
  • the UE can perform at least any of the following:
  • ⁇ It has nothing to do with the target RRC message, that is, unify all the target RRC messages to the same value, for example, set the Access category to 11 and the Access identity to 6;
  • ⁇ It is related to the target RRC message. For example, if it is "XX configuration request message", set the Access category to 11 and the Access identity to 6.
  • the RRC layer can be triggered to instruct the bottom layer to use the transmission of the first transmission mode and send the uplink grant corresponding to the transmission of the first transmission mode to the bottom layer.
  • the specific time point is at least any of the following:
  • the RRC layer After submitting the RRC recovery request or RRC recovery request 1 message to the bottom layer in the operation process related to the transmission of the RRC recovery request or RRC recovery request 1 message, the RRC layer is immediately triggered to instruct the bottom layer to use the first transmission mode and send the first transmission The uplink grant corresponding to the mode of transmission is given to the bottom layer.
  • the UE may perform at least one of the following:
  • the RRC layer After submitting the RRC recovery request or RRC recovery request 1 message to the bottom layer during the operation related to the transmission of the RRC recovery request or RRC recovery request 1 message, the RRC layer is immediately triggered to instruct the bottom layer to use PUR transmission and send the corresponding uplink grant to the PUR transmission. bottom layer.
  • the trigger time point for the generation of the target RRC message is at least any one of the following:
  • the UE RRC layer needs to send the target RRC message to the network side device, it immediately triggers the generation of the content of the target RRC message;
  • the UE first requests the RRC resumption and initiates the transmission of the first transmission mode (such as PUR transmission), triggering the RRC connection resume process, and then in the RRC connection resume process. Trigger the generation of the content of the target RRC message; and at least one of the following:
  • the UE triggers the generation of the content of the target RRC message in the Initiation of the RRC connection resume process
  • the UE may store the content of the target RRC message as a variable, an array and/or a structure or any other mathematical expression, or not store it.
  • the trigger time point when the target RRC message is submitted to the bottom layer at least one of the following:
  • RRC recovery request or RRC recovery request 1 message transmission related operation process immediately trigger the submission of the target RRC message to the bottom layer
  • the MAC layer of the UE submits a MAC PDU with both RRCResumeRequest/RRCResumeRequest1 and the target RRC message to the bottom layer (such as the physical layer), and then sends it to the network side device.
  • the target RRC message and the RRCResumeRequest/RRCResumeRequest1 message are multiplexed in the same MAC PDU and sent to the network-side device, at least one of the following:
  • the RRCResumeRequest/RRCResumeRequest1 message is located before the target RRC message; in other words, the RRCResumeRequest/RRCResumeRequest1 message can be in the front of the MAC PDU, and the target RRC message is in the back of the MAC PDU;
  • the RRCResumeRequest/RRCResumeRequest1 message is located after the target RRC message; in other words, the target RRC message can be in the front of the MAC PDU, and the RRCResumeRequest/RRCResumeRequest1 message is in the back of the MAC PDU.
  • Solution 3 The UE completes the sending of the target RRC message through transmission in the second transmission mode (eg, similar to SDT, similar to EDT, etc.).
  • the RRC layer of the UE will request the RRC connection resumption and initiate the transmission of the second transmission mode (such as SDT-like, EDT-like etc.), trigger the RRCResume process, generate the RRCResumeRequest/RRCResumeRequest1 message and submit it to the bottom layer, trigger the generation of the content of the target RRC message, and trigger the submission of the target RRC message to the bottom layer.
  • the second transmission mode such as SDT-like, EDT-like etc.
  • the initiation condition of the transmission of the second transmission mode may be at least one of the following:
  • the UE requests RRC connection recovery at the RRC layer; the value of RRCResumeCause is at least any of the following:
  • the UE supports the transmission of the second transmission mode
  • the network supports the transmission of the second transmission mode, for example, the system message contains the corresponding indication
  • nextHopChainingCount value is provided by the suspendConfig in the latest (ie last) RRCRelease message
  • ⁇ All parameters related to the transmission of the second transmission mode are configured in the system information obtained by the UE;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the TBS defined in the configuration of the second transmission mode.
  • the initiation condition of EDT is at least any one of the following:
  • the UE requests RRC connection recovery at the RRC layer
  • ⁇ UE supports EDT
  • the network supports EDT, for example, the corresponding indication is included in the system message
  • nextHopChainingCount value is provided by the suspendConfig in the latest (ie last) RRCRelease message
  • ⁇ All parameters related to EDT are configured in the system information obtained by the UE, such as edt-parameter;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the TBS defined in the EDT configuration, such as edt-TBS.
  • the UE can set the ResumeCause value, and its value is consistent with the value specifically selected above.
  • the UE can perform at least any of the following:
  • ⁇ It has nothing to do with the target RRC message, that is, unify all the target RRC messages to the same value, for example, set the Access category to 11 and the Access identity to 6;
  • ⁇ It is related to the target RRC message. For example, if it is "XX configuration request message", set the Access category to 11 and the Access identity to 6.
  • the UE RRC layer can be triggered to configure the bottom layer for transmission using the second transmission mode.
  • the specific time point is at least any of the following:
  • ⁇ immediately trigger the RRC layer to configure the bottom layer for transmission using the second transmission mode after the recovery of SRB1 in the operation process related to the transmission of the RRC recovery request or the RRC recovery request 1 message;
  • the RRC layer After submitting the RRC recovery request or RRC recovery request 1 message to the bottom layer in the operation process related to the transmission of the RRC recovery request or the RRC recovery request 1 message, the RRC layer is immediately triggered to configure the bottom layer for transmission using the second transmission mode.
  • the UE may perform at least one of the following:
  • the RRC layer After submitting the RRC recovery request or RRC recovery request 1 message to the bottom layer in the operation process related to the transmission of the RRC recovery request or the RRC recovery request 1 message, the RRC layer is immediately triggered to configure the bottom layer to use the EDT.
  • the trigger time point for the generation of the target RRC message is at least any one of the following:
  • the UE RRC layer needs to send the target RRC message to the network side device, it immediately triggers the generation of the content of the target RRC message;
  • the UE first requests the RRC resumption and initiates the transmission of the second transmission mode (such as SDT, EDT, etc.), triggering the RRC connection resume process, and then in the RRC
  • the second transmission mode such as SDT, EDT, etc.
  • the UE triggers the generation of the content of the target RRC message in the Initiation of the RRC connection resume process
  • the UE may store the content of the target RRC message as a variable, an array and/or a structure or any other mathematical expression, or not store it.
  • the trigger time point when the target RRC message is submitted to the bottom layer at least one of the following:
  • RRC recovery request or RRC recovery request 1 message transmission related operation process immediately trigger the submission of the target RRC message to the bottom layer
  • the MAC layer of the UE submits a MAC PDU with both RRCResumeRequest/RRCResumeRequest1 and the target RRC message to the bottom layer (such as the physical layer), and then sends it to the network side device.
  • the target RRC message and the RRCResumeRequest/RRCResumeRequest1 message are multiplexed in the same MAC PDU and sent to the network-side device, at least one of the following:
  • the RCResumeRequest/RRCResumeRequest1 message is located before the target RRC message; in other words, the RRCResumeRequest/RRCResumeRequest1 message can be located in the front of the MAC PDU, and the target RRC message is located in the back of the MAC PDU;
  • the RRCResumeRequest/RRCResumeRequest1 message is located after the target RRC message; in other words, the target RRC message can be in the front of the MAC PDU, and the RRCResumeRequest/RRCResumeRequest1 message is in the back of the MAC PDU.
  • the target RRC message is an MBSCountingResponse message, and the target RRC message is sent through a random access procedure.
  • the corresponding target RRC message sending process may include:
  • Step 30 Preparation phase.
  • the UE After the RRC layer of the UE receives the MBSCountingRequest message, if the UE is receiving or is interested in receiving the MBS service indicated in the MBSCountingRequest message, the UE will need to send the MBSCountingResponse message to the network side device. The UE will trigger the RRCResume process, generate the RRCResumeRequest/RRCResumeRequest1 message and submit it to the bottom layer, and generate the MBSCountingResponse message and submit it to the bottom layer.
  • UAC related settings Set the Access category to 11, Access identity to 0, execute UAC and pass the UAC check, that is, the access attempt is allowed.
  • ⁇ Set ResumeCause value Set RRCResumeCause to MO-RRCmessage.
  • the RRCResumeRequest/RRCResumeRequest1 message is generated and submitted to the bottom layer: For example, the RRC layer of the UE generates the RRCResumeRequest/RRCResumeRequest1 message whose ResumeCause value is MO-RRCmessage, and submits it to the bottom layer.
  • the generation and submission of the MBSCountingResponse message to the bottom layer For example, when RRCResumeRequest/RRCResumeRequest1 is submitted to the bottom layer, the generation and submission of the MBSCountingResponse message to the bottom layer are immediately triggered.
  • Step 31 The MAC layer of the UE initiates a random access process, and sends Msg1, that is, a random access pilot, to the base station gNB.
  • Step 32 The gNB returns Msg2, that is, a random access response (RAR) to the UE.
  • RAR random access response
  • Step 33 The MAC layer of the UE sends a MAC PDU including the RRCResumeRequest/RRCResumeRequest1 message and the MBSCountingResponse message to the gNB through Msg3.
  • Step 34 The gNB returns Msg4 to the UE, which contains the RRCRelease message.
  • the target RRC message is a PURConfigurationRequest message, and the target RRC message is sent through PUR transmission.
  • the corresponding target RRC message sending process may include:
  • Step 40 Preparation phase.
  • the UE has valid PUR resources.
  • the UE When the UE is no longer interested in the PUR configuration, the UE will need to send a PURConfigurationRequest message to the network side device.
  • the RRC layer of the UE will request the RRC resumption and initiate the transmission of the PUR, trigger the RRCResume process, generate the RRCResumeRequest/RRCResumeRequest1 message and submit it to the bottom layer, and generate the PURConfigurationRequest message and submit it to the bottom layer.
  • UAC related settings same as MO-data, that is, set the Access category to 7 and the Access identity to 0, execute UAC and pass the UAC check, that is, the access attempt is allowed.
  • the RRCResumeRequest/RRCResumeRequest1 message is generated and submitted to the bottom layer: For example, the RRC layer of the UE generates the RRCResumeRequest/RRCResumeRequest1 message with the ResumeCause value of MO-data, and submits it to the bottom layer.
  • the generation and submission of the PURConfigurationRequest message to the bottom layer For example, when RRCResumeRequest/RRCResumeRequest1 is submitted to the bottom layer, the generation and submission of the PURConfigurationRequest message to the bottom layer are immediately triggered.
  • Step 41 The UE sends the RRCResumeRequest/RRCResumeRequest1 message and the PURConfigurationRequest message to the gNB.
  • the MAC layer of the UE performs PUR transmission, submits a MAC PDU containing both the RRCResumeRequest/RRCResumeRequest1 message and the PURConfigurationRequest message to the physical layer, and sends it to the gNB.
  • Step 42 The gNB sends a RRCRelease message to the UE.
  • the target RRC message is an MBSCountingResponse message, and the target RRC message is sent through the EDT.
  • the corresponding target RRC message sending process may include:
  • Step 50 Preparation phase.
  • the RRC layer of the UE After the RRC layer of the UE receives the MBSCountingRequest message, if the UE is receiving or is interested in receiving the MBS service indicated in the MBSCountingRequest message, the UE will need to send the MBSCountingResponse message to the network side device.
  • the RRC layer of the UE will request the RRC resumption and initiate the EDT, trigger the RRCResume process, generate the RRCResumeRequest/RRCResumeRequest1 message and submit it to the bottom layer, and generate the PURConfigurationRequest message and submit it to the bottom layer.
  • UAC related settings Set the Access category to 11, Access identity to 0, execute UAC and pass the UAC check, that is, the access attempt is allowed.
  • ⁇ Set ResumeCause value Set RRCResumeCause to MO-RRCmessage.
  • the RRCResumeRequest/RRCResumeRequest1 message is generated and submitted to the bottom layer: For example, the RRC layer of the UE generates the RRCResumeRequest/RRCResumeRequest1 message whose ResumeCause value is MO-RRCmessage, and submits it to the bottom layer.
  • the generation and submission of the MBSCountingResponse message to the bottom layer For example, when RRCResumeRequest/RRCResumeRequest1 is submitted to the bottom layer, the generation and submission of the MBSCountingResponse message to the bottom layer are immediately triggered.
  • Step 51 The UE sends the RRCResumeRequest/RRCResumeRequest1 message and the MBSCountingResponse message to the gNB.
  • the MAC layer of the UE performs EDT, submits a MAC PDU including both the RRCResumeRequest/RRCResumeRequest1 message and the MBSCountingResponse message to the physical layer, and sends it to the gNB.
  • Step 52 The gNB sends a RRCRelease message to the UE.
  • the execution body may be a message sending apparatus, or a control module in the message sending apparatus for executing the message sending method.
  • the message sending device provided by the embodiment of the present application is described by taking a message sending device executing a message sending method as an example.
  • FIG. 6 is a schematic structural diagram of a message sending apparatus provided by an embodiment of the present invention, which is applied to a terminal.
  • the message sending device 60 includes:
  • the first sending module 61 is configured to send the target RRC message in a non-RRC connected state when the terminal is in a non-RRC connected state and there is a need to send a target RRC message to a network side device; the target RRC message The message is an RRC message of access stratum security that needs to be activated.
  • the message sending apparatus 60 further includes:
  • the first execution module is used to execute the following:
  • the message sending apparatus 60 further includes:
  • the ResumeCause value is at least one of the following:
  • the newly set ResumeCause value wherein, the newly set ResumeCause value has nothing to do with the target RRC message, or the newly set ResumeCause value is related to the target RRC message.
  • the message sending apparatus 60 further includes:
  • the second execution module is configured to execute at least one of the following:
  • UAC is checked by using the set new access class and/or access identifier; wherein, the new access class and/or access identifier is irrelevant to the target RRC message, or the new access The class and/or access identity are related to the target RRC message.
  • the first execution module is specifically configured to execute at least one of the following:
  • the generation of the content of the target RRC message is triggered during the RRC connection recovery process.
  • the first execution module is specifically configured to execute at least one of the following:
  • the generation of the content of the target RRC message is triggered immediately.
  • the first execution module is specifically configured to execute at least one of the following:
  • the submission of the target RRC message to the bottom layer is triggered immediately.
  • the message sending apparatus 60 further includes:
  • a storage module configured to store the content in the target RRC message by using a first mathematical expression form after the content in the target RRC message is generated, or not store the content in the target RRC message.
  • the first mathematical expression includes at least one of the following:
  • the first sending module 61 is specifically configured to:
  • the target RRC message and the RRC recovery request or the RRC recovery request 1 message are multiplexed in the same MAC PDU and sent to the network side device.
  • the MAC PDU is composed of at least one of the following:
  • the RRC recovery request or RRC recovery request 1 message is located before the target RRC message;
  • the RRC Recovery Request or RRC Recovery Request 1 message follows the target RRC message.
  • the first execution module is also used for:
  • the random access procedure is initiated at the MAC layer.
  • the trigger event of the random access process is at least one of the following:
  • a newly set trigger event wherein the newly set trigger event is not related to the target RRC message, or the newly set trigger event is related to the target RRC message.
  • the configuration of resources and parameters in the random access process is at least one of the following:
  • Part of the existing configuration is reused, and part is configured separately.
  • the first execution module is also used for:
  • the transmission of the first transmission mode is performed at the MAC layer.
  • the initiation condition of the transmission in the first transmission mode is at least one of the following:
  • the RRC layer requests RRC connection recovery
  • the terminal supports transmission in the first transmission mode
  • the network supports the transmission of the first transmission mode
  • the terminal has a valid configuration of the first transmission mode
  • the terminal has a valid timing adjustment value
  • the terminal has a stored nextHopChainingCount value, and the nextHopChainingCount value is provided by the suspendConfig in the latest RRC release message;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the transport block size TBS defined in the configuration of the first transport mode.
  • the first execution module is also used for:
  • the RRC layer is triggered to instruct the bottom layer to use the transmission of the first transmission mode and send the uplink grant corresponding to the transmission of the first transmission mode to the bottom layer.
  • the first execution module is specifically configured to execute at least one of the following:
  • the RRC layer Before restoring SRB1 in the operation process related to the transmission of the RRC recovery request or the RRC recovery request 1 message, the RRC layer is triggered to instruct the bottom layer to use the transmission of the first transmission mode and the uplink grant corresponding to the transmission of the first transmission mode is sent to the bottom layer;
  • the RRC layer is immediately triggered to instruct the bottom layer to use the transmission of the first transmission mode and send the uplink grant corresponding to the transmission of the first transmission mode to the bottom layer;
  • the RRC layer After submitting the RRC recovery request or RRC recovery request 1 message to the bottom layer in the operation process related to the transmission of the RRC recovery request or the RRC recovery request 1 message, the RRC layer is immediately triggered to instruct the bottom layer to use the first transmission mode for transmission and send The uplink grant corresponding to the transmission of the first transmission mode is given to the bottom layer.
  • the first execution module is also used for:
  • the transmission of the second transmission mode is performed at the MAC layer.
  • the initiation condition of the transmission of the second transmission mode is at least one of the following:
  • the terminal supports the transmission of the second transmission mode
  • the network supports the transmission of the second transmission mode
  • the terminal has a stored nextHopChainingCount value, and the nextHopChainingCount value is provided by the suspendConfig in the latest RRC release message;
  • All parameters related to the transmission of the second transmission mode are configured in the system information obtained by the terminal;
  • the size of the MAC PDU containing the target RRC message is less than or equal to the transport block size TBS defined in the configuration of the transmission of the second transport mode.
  • the first execution module is also used for:
  • Trigger the RRC layer to configure the bottom layer for transmission using the second transmission mode which is at least one of the following:
  • the RRC layer is immediately triggered to configure the bottom layer for transmission using the second transmission mode
  • the RRC layer After submitting the RRC recovery request or the RRC recovery request 1 message to the bottom layer in the operation process related to the transmission of the RRC recovery request or the RRC recovery request 1 message, the RRC layer is immediately triggered to configure the bottom layer for transmission using the second transmission mode.
  • the terminal needs to send the target RRC message to the network side device:
  • the terminal supports transmission in the first transmission mode
  • the network supports the transmission of the first transmission mode
  • the size of the MAC PDU containing the target RRC message is less than or equal to the maximum transport block size TBS supported by the terminal defined based on the terminal type;
  • the terminal satisfies at least one of the following: interested in the configuration of the first transmission mode, no longer interested in the configuration of the first transmission mode, and needs to update the configuration of the first transmission mode.
  • the terminal needs to send the target RRC message to the network side device under the condition that at least one of the following is satisfied:
  • the terminal has MBS capability
  • the network supports MBS
  • the size of the MAC PDU containing the target RRC message is less than or equal to the maximum TBS supported by the terminal defined based on the terminal type;
  • the RRC layer of the terminal receives the control message related to the MBS count sent by the network side device;
  • the terminal is receiving or is interested in receiving at least one MBS service indicated in the control message related to the MBS count.
  • the terminal needs to send the target RRC message to the network side device:
  • the terminal has MBS capability
  • the network supports MBS
  • the size of the MAC PDU containing the target RRC message is less than or equal to the maximum TBS supported by the terminal defined based on the terminal type;
  • the terminal receives the control information related to the MBS service sent by the network side device;
  • the terminal enters or leaves the service area
  • MBS session starts or stops
  • the cell or base station that transmits the control information related to the MBS service changes.
  • the message sending apparatus in this embodiment of the present application may be an apparatus, and may also be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the message sending apparatus in this embodiment of the present application may be an apparatus having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the message sending apparatus 60 provided in this embodiment of the present application can implement each process implemented by the method embodiment shown in FIG. 2 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • FIG. 7 is a flowchart of a message receiving method provided by an embodiment of the present invention. The method is applied to a network side device. As shown in FIG. 7, the method includes the following steps:
  • Step 701 Receive the target RRC message from the terminal.
  • the target RRC message is an RRC message of access stratum security that needs to be activated; the target RRC message is when the terminal is in a non-RRC connected state and needs to send the target RRC message, in the Sent in non-RRC connected state.
  • the receiving terminal can directly send the target RRC message in the non-RRC connection state, and it is not required that the terminal can send the target RRC message only after other conditions for triggering the establishment or recovery of the RRC connection are satisfied and the RRC connection is successfully established or recovered, Thereby reducing the delay. Further, resource waste, energy consumption and the like can be avoided.
  • the above process of receiving the target RRC message from the terminal may include:
  • the target RRC message is received from the terminal through the MAC PDU; wherein, the target RRC message and the RRC recovery request or the RRC recovery request 1 message are multiplexed in the MAC PDU.
  • the method further includes:
  • the method further includes at least one of the following:
  • a control message related to the MBS count is sent to the terminal.
  • the method further includes at least one of the following:
  • indication information indicating that the network supports MBS to the terminal may be sent through system information
  • the control information related to the MBS service is sent to the terminal; for example, the control information may be sent through a system message or dedicated RRC signaling.
  • the execution body may be a message receiving apparatus, or a control module in the message receiving apparatus for executing the message receiving method.
  • the message receiving device provided by the embodiment of the present application is described by taking a message receiving device executing a message receiving method as an example.
  • FIG. 8 is a schematic structural diagram of a message receiving apparatus provided by an embodiment of the present invention, which is applied to a network side device. As shown in Figure 8, the message receiving apparatus 80 includes:
  • a receiving module 81 configured to receive the target RRC message from the terminal
  • the target RRC message is an RRC message of access stratum security that needs to be activated; the target RRC message is when the terminal is in a non-RRC connected state and needs to send the target RRC message, in the Sent in non-RRC connected state.
  • the receiving module 81 is further configured to: receive the target RRC message from the terminal through a MAC PDU; the MAC PDU is multiplexed with the target RRC message and the RRC recovery request or RRC recovery request 1 message.
  • the message receiving apparatus 80 further includes:
  • a second sending module configured to send, to the terminal, indication information indicating that the network supports the transmission of the first transmission mode when the target RRC message is an RRC message related to the transmission of the first transmission mode;
  • the target RRC message is an RRC message related to MBS counting
  • the target RRC message is an RRC message related to the MBS interest indication
  • the indication information indicating that the network supports MBS is sent to the terminal, and/or the control information related to the MBS service is sent to the terminal.
  • the message receiving apparatus 80 provided in this embodiment of the present application can implement each process implemented by the method embodiment shown in FIG. 7 , and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 90, including a processor 91, a memory 92, a program or instruction stored in the memory 92 and executable on the processor 91, for example,
  • a communication device 90 including a processor 91, a memory 92, a program or instruction stored in the memory 92 and executable on the processor 91, for example.
  • the communication device 90 is a terminal, when the program or instruction is executed by the processor 91, each process of the above-mentioned embodiment of the message sending method can be realized, and the same technical effect can be achieved.
  • the communication device 90 is a network-side device, when the program or instruction is executed by the processor 91, each process of the above-mentioned embodiment of the message receiving method can be achieved, and the same technical effect can be achieved.
  • FIG. 10 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 100 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110 and other components .
  • the terminal 100 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 110 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 10 does not constitute a limitation on the terminal, and the terminal may include more or less components than the one shown, or some components may be combined, or different components are arranged, which will not be repeated here.
  • the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 107 includes a touch panel 1071 and other input devices 1072 .
  • the touch panel 1071 is also called a touch screen.
  • the touch panel 1071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which are not described herein again.
  • the radio frequency unit 101 receives the downlink data from the network side device, and then processes it to the processor 110; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 109 may be used to store software programs or instructions as well as various data.
  • the memory 109 may mainly include a storage program or instruction area and a storage data area, wherein the stored program or instruction 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.) and the like.
  • the memory 109 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 110 may include one or more processing units; optionally, the processor 110 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 110 .
  • the radio frequency unit 101 is used to send the target RRC message in the non-RRC connection state when the terminal 100 is in the non-RRC connection state and there is a need to send the target RRC message to the network side device; the target RRC message is required Activated RRC messages for access stratum security.
  • the terminal 100 provided in this embodiment of the present application can implement each process implemented by the method embodiment shown in FIG. 2 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • the network side device 110 includes: an antenna 111 , a radio frequency device 112 , and a baseband device 113 .
  • the antenna 111 is connected to the radio frequency device 112 .
  • the radio frequency device 112 receives information through the antenna 111, and sends the received information to the baseband device 113 for processing.
  • the baseband device 113 processes the information to be sent and sends it to the radio frequency device 112
  • the radio frequency device 112 processes the received information and sends it out through the antenna 111 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 113 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 113 .
  • the baseband apparatus 113 includes a processor 114 and a memory 115 .
  • the baseband device 113 may include, for example, at least one baseband board on which multiple chips are arranged, as shown in FIG. 11 , one of the chips is, for example, the processor 114 , which is connected to the memory 115 to call the program in the memory 115 to execute
  • the network-side device shown in the above method embodiments operates.
  • the baseband device 113 may further include a network interface 116 for exchanging information with the radio frequency device 112, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in this embodiment of the present invention further includes: an instruction or program stored in the memory 115 and executable on the processor 114 , and the processor 114 invokes the instruction or program in the memory 115 to execute each instruction or program shown in FIG. 8 .
  • the method implemented by the module achieves the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing method for sending a message is implemented, or the foregoing message is implemented.
  • a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing method for sending a message is implemented, or the foregoing message is implemented
  • Each process of the embodiment of the receiving method can achieve the same technical effect. In order to avoid repetition, details are not repeated here.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • ROM computer read-only memory
  • RAM random access memory
  • magnetic disk or an optical disk and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the above message sending method embodiments
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is configured to run a program or an instruction to implement the above message sending method embodiments
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network side device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

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

Abstract

本申请公开了一种消息发送方法、接收方法、装置及通信设备，属于通信技术领域。具体实现方案包括：在终端处于非RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送目标RRC消息；该目标RRC消息为需要激活的接入层安全的RRC消息。由此，终端可以不需要在其他触发RRC连接建立或恢复的条件满足下，且RRC连接成功建立或恢复之后才能发送目标RRC消息，而可以在非RRC连接态直接发送目标RRC消息，从而减少时延。

Description

消息发送方法、接收方法、装置及通信设备
相关申请的交叉引用
本申请主张在2020年7月6日在中国提交的中国专利申请No.202010643208.0的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种消息发送方法、接收方法、装置及通信设备。
背景技术
目前，非无线资源控制(Radio Resource Control，RRC)连接态(NON-RRC CONNECTED)终端在有需要激活的接入层安全(activated AS security)的RRC消息发送给网络侧设备的需求时，仅能在其他触发RRC连接建立或恢复的条件满足下，且RRC连接成功建立或恢复之后，才能发送该RRC消息。由此，现有的非RRC连接态终端发送该RRC消息时的时延较大。
发明内容
本申请实施例的目的是提供一种消息发送方法、接收方法、装置及通信设备，以解决现有的非RRC连接态终端发送需activated AS security的RRC消息时的时延较大的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，本公开提供了一种消息发送方法，应用于终端，包括：
在所述终端处于非无线资源控制RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送所述目标RRC消息；
其中，所述目标RRC消息为需要激活的接入层安全的RRC消息。
第二方面，本公开提供了一种消息接收方法，应用于网络侧设备，包括：
从终端接收目标RRC消息；
其中，所述目标RRC消息为需要激活的接入层安全的RRC消息；所述 目标RRC消息是所述终端在处于非RRC连接态，且有发送所述目标RRC消息的需求的情况下，在非RRC连接态发送的。
第三方面，本公开提供了一种消息发送装置，应用于终端，包括：
第一发送模块，用于在所述终端处于非RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非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是本申请实施例一中的目标RRC消息发送过程的流程图；
图4是本申请实施例二中的目标RRC消息发送过程的流程图；
图5是本申请实施例三中的目标RRC消息发送过程的流程图；
图6是本申请实施例提供的一种消息发送装置的结构示意图；
图7是本申请实施例提供的一种消息接收方法的流程图；
图8是本申请实施例提供的一种消息接收装置的结构示意图；
图9是本申请实施例提供的一种通信设备的结构示意图；
图10是本申请实施例提供的一种终端的结构示意图；
图11是本申请实施例提供的一种网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。例如，“A和/或B”，表示“单独A，单独B，以及A和B都存在”三种情况，“A和B中的至少一个”也表示“单独A，单独B，以及A和B都存在”三种情况。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(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代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
为了便于理解本申请实施例，首先说明以下内容。
为了解决现有的非RRC连接态终端(如NON-RRCCONNECTED UE)发送需activated AS security的RRC消息时的时延较大的问题，本申请实施例提出了NON-RRCCONNECTED UE在有发送需activated AS security的RRC消息给网络侧设备的需求时，可以直接在NON-RRCCONNECTED态来发送该RRC消息的方法。
本申请实施例中，该需activated AS security的RRC消息可称为目标RRC消息。也就是说，下述实施例中提及的目标RRC消息为需activated AS security的RRC消息。
1、可选的，目标RRC消息可为第一传输方式的配置相关的RRC消息。此情况下，在满足以下至少一项的情况下，终端有发送目标RRC消息给网络侧设备的需求：
终端支持第一传输方式的传输；
网络支持第一传输方式的传输；比如系统消息中包含对应的指示；
包含目标RRC消息的媒体接入控制协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)的尺寸小于或等于，基于终端种类定义的终端支持的最大传输块尺寸(Transport Block Size，TBS)；
终端满足以下至少一项：对第一传输方式的配置感兴趣、不再对第一传输方式的配置感兴趣、需要更新第一传输方式的配置。
需指出的，上述的第一传输方式可理解为与PUR(Preconfigured Uplink Resource，预配置的上行链路资源)传输或者小数据传输(Small Data Transmission，SDT)的预配置PUSCH资源传输类似的传输方式，某些情况下也可理解为PUR传输方式或者SDT的预配置PUSCH资源传输方式，对此不进行限制。此情况下，目标RRC消息可为包含与预配置的PUSCH资源的配置相关的辅助信息，比如PURConfigurationRequest消息。以小数据传输的预配置PUSCH资源传输方式为例，在满足以下至少一项的情况下，UE有发送该目标RRC消息给网络侧设备的需求：
UE支持预配置PUSCH资源方式的传输；
网络支持预配置PUSCH资源方式的传输，比如系统消息中包含对应的 指示；
包含目标RRC消息的MAC PDU的尺寸小于或等于，基于UE种类定义的UE最大支持的TBS
UE对预配置PUSCH资源的配置感兴趣，或者不再感兴趣，或者需要更新预配置PUSCH资源的配置。
2、可选的，目标RRC消息可为多播广播业务(Multicast and Broadcast Service，MBS)计数(Counting)相关的RRC消息，比如MBSCountingResponse消息。此情况下，在满足以下至少一项的情况下，终端有发送目标RRC消息给网络侧设备的需求：
终端具有MBS能力；
网络支持MBS；比如系统消息中包含对应的指示；
包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大TBS；
终端的RRC层接收到网络侧设备发送的MBS计数相关的控制消息(如MBSCountingRequest消息)；
终端正在接收或者感兴趣接收MBS计数相关的控制消息(如MBSCountingRequest消息)中指示的至少一个MBS业务。
3、可选的，目标RRC消息可为MBS兴趣指示(Interest Indication)相关的RRC消息，比如MBSInterestIndication消息。此情况下，在满足以下至少一项的情况下，终端有发送目标RRC消息给网络侧设备的需求：
终端具有MBS能力；
网络支持MBS；比如系统消息中包含对应的指示；
包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大TBS；
终端接收了网络侧设备发送的MBS业务相关的控制信息；比如，该MBS业务相关的控制信息可通过系统消息或者专用RRC信令发送；
终端进入或离开服务区域；比如，UE一进入服务区域(upon entering the service area)，或者UE一离开服务区域；
MBS会话(session)开始或停止；比如，MBS session一开始，或者MBS  session一停止；
MBS兴趣指示消息的内容发生改变；
发送MBS业务相关控制信息的小区或基站发生改变。
可理解的，目标RRC消息除了可选为上述三种RRC消息之后，还可选为其他任何需activated AS security的RRC消息，对此不进行限制。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的消息发送方法和接收方法进行详细地说明。
请参见图2，图2是本发明实施例提供的一种消息发送方法的流程图，该方法应用于终端，如图2所示，该方法包括如下步骤：
步骤201：在终端处于非RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送该目标RRC消息。
本实施例中，该目标RRC消息为需activated AS security的RRC消息。
在本申请实施例中，终端可以在处于非RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送目标RRC消息。由此，终端可以不需要在其他触发RRC连接建立或恢复的条件满足下，且RRC连接成功建立或恢复之后才能发送目标RRC消息，而可以在非RRC连接态直接发送目标RRC消息，从而减少时延。进一步的，还可避免资源浪费、能耗等。
本申请实施例中，终端可以借助RRC连接恢复(RRC connection resume)过程来在非RRC连接态发送目标RRC消息。可选的，在发送目标RRC消息之前，终端还可以触发RRC连接恢复过程，生成RRC恢复请求或RRC恢复请求1(RRCResumeRequest/RRCResumeRequest1)消息，并将该RRCResumeRequest/RRCResumeRequest1消息提交给底层；触发目标RRC消息的内容的生成(或称为产生)，并触发将目标RRC消息提交给底层。可理解的，该RRCResumeRequest/RRCResumeRequest1消息和目标RRC消息在RRC层中生成，此处的底层为RRC层的下面的协议层，如分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)、无线链路控制(Radio Link Control，RLC)、MAC层。
可选的，在RRC连接恢复过程中，终端还可以设置恢复原因ResumeCause 值。该ResumeCause值可为以下至少一种：
复用现有的ResumeCause值；比如mo-data,mo-signal等；
新设置的ResumeCause值。
一种实施方式，该新设置的ResumeCause值可以与目标RRC消息无关，即统一所有的目标RRC消息，比如MO-RRCmessage，设置ResumeCause值为MO-RRCmessage。该与目标RRC消息无关可以是与目标RRC消息的消息类型或形式无关，也可以是与目标RRC消息的内容无关。
另一种实施方式，该新设置的ResumeCause值可以与目标RRC消息有关，比如“XX配置请求消息”，设置ResumeCause值为“XX配置请求消息”。该与目标RRC消息有关可以是与目标RRC消息的消息类型或形式有关，也可以是与目标RRC消息的内容有关。
可选的，在RRC连接恢复过程中，终端还可以执行以下至少一项：
1)不进行统一接入控制(Unified Access Control，UAC)的检查，接入尝试直接被允许。
2)利用设置的现有的接入类别(Access category)和/或接入标识(Access identity(ies))进行UAC的检查。即复用现有的Access category和/或Access identity(ies)，比如设置Access category为7，Access identity为0等。
3)利用设置的新的接入类别和/或接入标识进行UAC的检查。即使用新设置的Access category and/or Access identity(ies)进行UAC的检查。
一种实施方式，该新的Access category和/或Access identity(ies)可以与目标RRC消息无关，即统一所有的目标RRC消息为相同的值，比如统一设置Access category为11，Access identity为6等。该与目标RRC消息无关可以是与目标RRC消息的消息类型或形式无关，也可以是与目标RRC消息的内容无关。
另一种实施方式，该新的Access category和/或Access identity(ies)可以与目标RRC消息有关，比如对于“XX配置请求消息”，设置Access category为11，Access identity为6等。该与目标RRC消息有关可以是与目标RRC消息的消息类型或形式有关，也可以是与目标RRC消息的内容有关。
可选的，对于目标RRC消息的内容的生成的触发情况，可以包括以下至 少一项：
1)当终端有发送目标RRC消息给网络侧设备的需求时，立即触发目标RRC消息的内容的生成；
2)在RRC连接恢复过程中触发目标RRC消息的内容的生成。即一旦终端有发送目标RRC消息给网络侧设备的需求时，终端先触发RRC connection resume过程，再在RRC connection resume过程中触发目标RRC消息的内容的生成。此时的触发情况可包括以下至少一项：
①在RRC连接恢复过程的发起阶段(Initiation)，触发目标RRC消息的内容的生成；
②在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程(Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message)中的恢复SRB1前，触发目标RRC消息的内容的生成；
③在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程(Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message)中的恢复SRB1后，立即触发目标RRC消息的内容的生成；
④在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程(Actions related to transmission of RRCResumeRequest or RRCResumeRequest1message)中的提交RRC恢复请求或RRC恢复请求1消息给底层后，立即触发目标RRC消息的内容的生成。
可选的，对于将目标RRC消息提交给底层的触发情况，可以包括以下至少一项：
1)在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程(Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message)中的恢复SRB1后，立即触发将目标RRC消息提交给底层；
2)在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程(Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message)中的提交RRC恢复请求或RRC恢复请求1消息给底层后，立即触发将目标RRC消息提交给底层。
可选的，在目标RRC消息中的内容生成后，终端可以利用第一数学表达 形式对目标RRC消息中的内容进行存储，或者，不对目标RRC消息中的内容进行存储。
进一步的，上述的第一数学表达形式可以包括以下至少一项：变量、数组、结构体等任何数学表达形式。也就是说，当目标RRC消息的内容产生后，终端可以利用变量、数组、和/或结构体等任何数学表达形式进行存储。
可选的，终端在发送目标RRC消息时，可以将目标RRC消息以及RRC恢复请求或RRC恢复请求1消息，复用在同一个MAC PDU中发送给网络侧设备。进一步的该MAC PDU的构成可以为以下至少一种：
RRC恢复请求或RRC恢复请求1消息位于目标RRC消息之前；
RRC恢复请求或RRC恢复请求1消息位于目标RRC消息之后。
需指出的，对于终端在非RRC连接态发送目标RRC消息，可以是但不限于通过随机接入过程、第一传输方式的传输、或者第二传输方式的传输等来发送的。其中，该随机接入过程可为传统的随机接入过程，比如2步(2-step)随机接入过程，或者4步(4-step)随机接入过程。该第一传输方式的传输和第二传输方式的传输涉及完全不同的内容。更具体的，该第一传输方式可理解为与PUR传输或者小数据传输(Small Data Transmission，SDT)的预配置PUSCH资源传输类似的传输方式，某些情况下也可理解为PUR传输方式或者SDT的预配置PUSCH资源传输方式。该第二传输方式可理解为与早期数据传输(Early Data Transmission，EDT)或者小数据传输的RACH-based传输类似的传输方式，某些情况下也可理解为EDT传输方式或者小数据传输的RACH-based传输方式。比如，该第一传输方式的传输为PUR传输、SDT的预配置PUSCH资源传输，或者类似PUR传输、类似SDT的预配置PUSCH资源传输等。该第二传输方式的的传输比如为EDT、类似EDT、小数据传输的RACH-based传输、或者类似小数据传输的RACH-based传输等。
下面结合不同的方案对目标RRC消息的发送进行详细说明。
方案一：UE通过传统的随机接入过程(比如NR 2-step/4-step RACH)来完成目标RRC消息的发送。
1、准备阶段
在准备阶段中，UE将触发RRC connection resume过程，生成 RRCResumeRequest/RRCResumeRequest1消息并将之提交给底层，触发目标RRC消息的内容的生成，并触发将目标RRC消息提交给底层。
1)RRCResume过程中，UE可以设置ResumeCause值，至少为以下任意一种：
①复用现有的ResumeCause值，比如mo-data,mo-signal等；
②使用设置的新的ResumeCause值，至少为以下任意一种：
→与目标RRC消息无关，即统一所有的目标RRC消息，比如MO-RRCmessage，设置ResumeCause值为MO-RRCmessage；
→与目标RRC消息有关，比如“XX配置请求消息”，设置ResumeCause值为“XX配置请求消息”。
2)RRCResume过程中，UE至少可执行以下任意一项：
①不进行UAC的检查，接入尝试直接被允许；
②复用现有的Access category和/或Access identity(ies)进行UAC的检查；比如设置Access category为7，Access identity为0等；
③使用设置的新的Access category和/或Access identity(ies)进行UAC的检查，至少为以下任意一种：
→与目标RRC消息无关，即统一所有的目标RRC消息为相同的值，比如统一设置为Access category为11，Access identity为6；
→与目标RRC消息有关，比如若为“XX配置请求消息”，设置Access category为11，Access identity为6。
3)目标RRC消息生成的触发时间点，至少为以下任意一种：
①一旦UE有发送目标RRC消息给网络侧设备的需求时，立即触发目标RRC消息的内容的生成；
②一旦UE有发送目标RRC消息给网络侧设备的需求时，UE先触发RRC connection resume过程，再在RRC connection resume过程中触发目标RRC消息的内容的生成；且至少为以下任意一种：
→UE在RRC connection resume过程的Initiation中，触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中 的恢复SRB1前，触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1后，立即触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的提交RRCResumeRequest/RRCResumeRequest1消息给底层后，立即触发目标RRC消息的内容的生成。
4)当目标RRC消息的内容产生后，UE可以将目标RRC消息的内容存为一个变量、数组和/或结构体等任何数学表达形式，或者，不进行存储。
5)目标RRC消息提交给底层的触发时间点，至少为以下任意一种：
①在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1后，立即触发将目标RRC消息提交给底层；
②在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的提交RRCResumeRequest/RRCResumeRequest1消息给底层后，立即触发将目标RRC消息提交给底层。
2、随机接入(RACH)阶段
在RACH阶段中，UE的MAC层发起随机接入过程，并将同时带有RRCResumeRequest/RRCResumeRequest1和目标RRC消息的一个MAC PDU提交给底层后发送给网络侧设备。
6)随机接入的触发事件至少为以下任意一种：
①复用现有的触发事件，比如Transition from RRC_INACTIVE等；
②使用新设置的触发事件，至少为以下任意一种：
→与目标RRC消息无关，即统一所有的目标RRC消息，比如MO-RRCmessage；
→与目标RRC消息有关，比如将某一单独的目标RRC消息的发送作为触发事件，比如“XX配置请求消息”等。
7)随机接入过程中所有的资源和参数的配置，比如前导码preamble、PRACH资源、随机接入响应(Random Access Response，RAR)中的上行授权UL grant、MsgA物理上行共享信道(Physical Uplink Shared Channel，PUSCH)资源、同步信号块(Synchronization Signal and PBCH block，SSB)资源、物 理下行控制信道(Physical Downlink Control Channel，PDCCH)搜索空间等等，至少为以下任意一种：
①全部单独配置；比如，所有资源和参数的配置，全部单独配置；
②全部复用现有的配置；比如，所有资源和参数的配置，全部复用(即共享)现有的配置；
③部分复用现有的配置，部分单独配置。
8)目标RRC消息和RRCResumeRequest/RRCResumeRequest1消息复用在同一个MAC PDU里发送给网络侧设备，至少为以下任意一种：
→RCResumeRequest/RRCResumeRequest1消息位于目标RRC消息之前；换句话说，可以是RCResumeRequest/RRCResumeRequest1消息处在MAC PDU内的前面，目标RRC消息处在MAC PDU内的后面；
→RCResumeRequest/RRCResumeRequest1消息位于目标RRC消息之后；换句话说，可以是：目标RRC消息处在MAC PDU内的前面，RRCResumeRequest/RRCResumeRequest1消息处在MAC PDU内的后面。
方案二：UE通过第一传输方式的传输(比如PUR传输、类似PUR传输等)来完成目标RRC消息的发送。
1、准备阶段
一旦UE的RRC层有发送需activated AS security的RRC消息(目标RRC消息)的需求时，UE的RRC层将请求RRC连接恢复(resumption)并发起第一传输方式的传输(如PUR传输)，触发RRCResume过程，生成RRCResumeRequest/RRCResumeRequest1消息并将之提交给底层，触发目标RRC消息的内容的生成，并触发将目标RRC消息提交给底层。
1)第一传输方式的传输的发起条件可为以下至少一种：
→UE在RRC层请求RRC连接恢复；RRCResumeCause的值至少为以下任意一种：
①复用现有的ResumeCause值，比如mo-data,mo-signal等；
②使用设置的新的ResumeCause值，至少为以下任意一种：
Ⅰ与目标RRC消息无关，即统一所有的目标RRC消息，比如MO-RRCmessage，设置ResumeCause值为MO-RRCmessage；
Ⅱ与目标RRC消息有关，比如“XX配置请求消息”，设置ResumeCause值为“XX配置请求消息”。
→UE支持第一传输方式的传输；
→网络支持第一传输方式的传输，比如系统消息中包含对应的指示；
→UE有一个有效的第一传输方式的配置；
→UE有一个有效的定时调整timing alignment值；
→UE有一个存储的nextHopChainingCount值，并且这个nextHopChainingCount值是由最新一次(即上一次)RRCRelease消息中的suspendConfig提供的；
→包含目标RRC消息的MAC PDU的尺寸小于或等于，第一传输方式的配置中定义的TBS。
一种实施方式中，以第一传输方式的传输为PUR传输为例，PUR传输的发起条件至少为以下任意一种：
→UE在RRC层请求RRC连接恢复；
→UE支持PUR的传输；
→网络支持PUR的传输；
→UE有一个有效的PUR配置；
→UE有一个有效的定时timing alignment值；
→UE有一个存储的nextHopChainingCount值；并且这个nextHopChainingCount值是由最新一次RRCRelease消息中的suspendConfig提供的；
→包含目标RRC消息的MAC PDU的尺寸小于或等于，PUR配置中定义的TBS。
2)RRCResume过程中，UE可以设置ResumeCause值，其值与上文中具体选择的值保持一致。
3)RRCResume过程中，UE至少可执行以下任意一项：
①不进行UAC的检查，接入尝试直接被允许；
②复用现有的Access category和/或Access identity(ies)进行UAC的检查；比如设置Access category为7，Access identity为0等；
③使用设置的新的Access category和/或Access identity(ies)进行UAC的检查，至少为以下任意一种：
→与目标RRC消息无关，即统一所有的目标RRC消息为相同的值，比如统一设置为Access category为11，Access identity为6；
→与目标RRC消息有关，比如若为“XX配置请求消息”，设置Access category为11，Access identity为6。
4)此阶段中，可触发RRC层指示底层使用第一传输方式的传输并发送第一传输方式的传输对应的上行授权给底层。具体的时间点至少为以下任意一种：
→在第一传输方式的传输的发起条件满足后，立即触发RRC层指示底层使用第一传输方式的传输并发送第一传输方式的传输对应的上行授权给底层；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程(Actions related to transmission of RRCResumeRequest or RRCResumeRequest1message)中的恢复SRB1前，触发RRC层指示底层使用第一传输方式的传输并发送第一传输方式的传输对应的上行授权给底层；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层指示底层使用第一传输方式的传输并发送第一传输方式的传输对应的上行授权给底层；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层指示底层使用第一传输方式的传输并发送第一传输方式的传输对应的上行授权给底层。
一种实施方式中，以第一传输方式的传输为PUR传输为例，UE可以执行以下至少一项：
→在PUR传输的发起条件满足后，立即触发RRC层指示底层使用PUR传输并发送PUR传输对应的上行授权给底层；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1前，触发RRC层指示底层使用PUR传输并发送PUR传输对应的 上行授权给底层；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层指示底层使用PUR传输并发送PUR传输对应的上行授权给底层；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层指示底层使用PUR传输并发送PUR传输对应的上行授权给底层。
5)目标RRC消息生成的触发时间点，至少为以下任意一种：
①一旦UE RRC层有发送目标RRC消息给网络侧设备的需求时，立即触发目标RRC消息的内容的生成；
②一旦UE RRC层有发送目标RRC消息给网络侧设备的需求时，UE先请求RRC resumption并发起第一传输方式的传输(如PUR传输)，触发RRC connection resume过程，再在RRC connection resume过程中触发目标RRC消息的内容的生成；且至少为以下任意一种：
→UE在RRC connection resume过程的Initiation中，触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1前，触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1后，立即触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的提交RRCResumeRequest/RRCResumeRequest1消息给底层后，立即触发目标RRC消息的内容的生成。
6)当目标RRC消息的内容产生后，UE可以将目标RRC消息的内容存为一个变量、数组和/或结构体等任何数学表达形式，或者，不进行存储。
7)目标RRC消息提交给底层的触发时间点，至少为以下任意一种：
①在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1后，立即触发将目标RRC消息提交给底层；
②在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中 的提交RRCResumeRequest/RRCResumeRequest1消息给底层后，立即触发将目标RRC消息提交给底层。
2、消息发送阶段
此阶段中，UE的MAC层将同时带有RRCResumeRequest/RRCResumeRequest1和目标RRC消息的一个MAC PDU提交给底层(如物理层)，之后发送给网络侧设备。
可选的，目标RRC消息和RRCResumeRequest/RRCResumeRequest1消息复用在同一个MAC PDU里发送给网络侧设备，至少为以下任意一种：
→RCResumeRequest/RRCResumeRequest1消息位于目标RRC消息之前；换句话说，可以是RRCResumeRequest/RRCResumeRequest1消息处在MAC PDU内的前面，目标RRC消息处在MAC PDU内的后面；
→RCResumeRequest/RRCResumeRequest1消息位于目标RRC消息之后；换句话说，可以是目标RRC消息处在MAC PDU内的前面，RRCResumeRequest/RRCResumeRequest1消息处在MAC PDU内的后面。
方案三：UE通过第二传输方式的传输(比如类似SDT、类似EDT等)来完成目标RRC消息的发送。
1、准备阶段
一旦UE的RRC层有发送需activated AS security的RRC消息(目标RRC消息)的需求时，UE的RRC层将请求RRC连接恢复(resumption)并发起第二传输方式的传输(如类似SDT、类似EDT等)，触发RRCResume过程，生成RRCResumeRequest/RRCResumeRequest1消息并将之提交给底层，触发目标RRC消息的内容的生成，并触发将目标RRC消息提交给底层。
1)第二传输方式的传输的发起条件可为以下至少一种：
→UE在RRC层请求RRC连接恢复；RRCResumeCause的值至少为以下任意一种：
①复用现有的ResumeCause值，比如mo-data,mo-signal等；
②使用设置的新的ResumeCause值，至少为以下任意一种：
Ⅰ与目标RRC消息无关，即统一所有的目标RRC消息，比如MO-RRCmessage，设置ResumeCause值为MO-RRCmessage；
Ⅱ与目标RRC消息有关，比如“XX配置请求消息”，设置ResumeCause值为“XX配置请求消息”。
→UE支持第二传输方式的传输；
→网络支持第二传输方式的传输，比如系统消息中包含对应的指示；
→UE有一个存储的nextHopChainingCount值，并且这个nextHopChainingCount值是由最新一次(即上一次)RRCRelease消息中的suspendConfig提供的；
→UE获取的系统信息中配置了第二传输方式的传输相关的所有参数；
→包含目标RRC消息的MAC PDU的尺寸小于或等于，第二传输方式的配置中定义的TBS。
一种实施方式中，以第二传输方式的传输为EDT为例，EDT的发起条件至少为以下任意一种：
→UE在RRC层请求RRC连接恢复；
→UE支持EDT；
→网络支持EDT，比如系统消息中包含对应的指示；
→UE有一个存储的nextHopChainingCount值，并且这个nextHopChainingCount值是由最新一次(即上一次)RRCRelease消息中的suspendConfig提供的；
→UE获取的系统信息中配置了EDT相关的所有参数，比如edt-parameter；
→包含所述目标RRC消息的MAC PDU的尺寸小于或等于，EDT配置中定义的TBS，比如edt-TBS。
2)RRCResume过程中，UE可以设置ResumeCause值，其值与上文中具体选择的值保持一致。
3)RRCResume过程中，UE至少可执行以下任意一项：
①不进行UAC的检查，接入尝试直接被允许；
②复用现有的Access category和/或Access identity(ies)进行UAC的检查；比如设置Access category为7，Access identity为0等；
③使用设置的新的Access category和/或Access identity(ies)进行UAC 的检查，至少为以下任意一种：
→与目标RRC消息无关，即统一所有的目标RRC消息为相同的值，比如统一设置为Access category为11，Access identity为6；
→与目标RRC消息有关，比如若为“XX配置请求消息”，设置Access category为11，Access identity为6。
4)此阶段中，可触发UE RRC层配置底层使用第二传输方式的传输。具体的时间点至少为以下任意一种：
→在第二传输方式的传输的发起条件满足后，立即触发RRC层配置底层使用第二传输方式的传输；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1前，触发RRC层配置底层使用第二传输方式的传输；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层配置底层使用第二传输方式的传输；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层配置底层使用第二传输方式的传输。
一种实施方式中，以第二传输方式的传输为EDT传输为例，UE可以执行以下至少一项：
→在EDT的发起条件满足后，立即触发RRC层配置底层使用EDT；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1前，触发RRC层配置底层使用EDT；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层配置底层使用EDT；
→在RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层配置底层使用EDT。
5)目标RRC消息生成的触发时间点，至少为以下任意一种：
①一旦UE RRC层有发送目标RRC消息给网络侧设备的需求时，立即触发目标RRC消息的内容的生成；
②一旦UE RRC层有发送目标RRC消息给网络侧设备的需求时，UE先请求RRC resumption并发起第二传输方式的传输(如类似SDT、类似EDT等)，触发RRC connection resume过程，再在RRC connection resume过程中触发目标RRC消息的内容的生成；且至少为以下任意一种：
→UE在RRC connection resume过程的Initiation中，触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1前，触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1后，立即触发目标RRC消息的内容的生成；
→在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的提交RRCResumeRequest/RRCResumeRequest1消息给底层后，立即触发目标RRC消息的内容的生成。
6)当目标RRC消息的内容产生后，UE可以将目标RRC消息的内容存为一个变量、数组和/或结构体等任何数学表达形式，或者，不进行存储。
7)目标RRC消息提交给底层的触发时间点，至少为以下任意一种：
①在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的恢复SRB1后，立即触发将目标RRC消息提交给底层；
②在“RRC恢复请求或RRC恢复请求1消息传输相关的操作过程”中的提交RRCResumeRequest/RRCResumeRequest1消息给底层后，立即触发将目标RRC消息提交给底层。
2、消息发送阶段
此阶段中，UE的MAC层将同时带有RRCResumeRequest/RRCResumeRequest1和目标RRC消息的一个MAC PDU提交给底层(如物理层)，之后发送给网络侧设备。
可选的，目标RRC消息和RRCResumeRequest/RRCResumeRequest1消息复用在同一个MAC PDU里发送给网络侧设备，至少为以下任意一种：
→RCResumeRequest/RRCResumeRequest1消息位于目标RRC消息之前；换句话说，可以是RRCResumeRequest/RRCResumeRequest1消息处在 MAC PDU内的前面，目标RRC消息处在MAC PDU内的后面；
→RCResumeRequest/RRCResumeRequest1消息位于目标RRC消息之后；换句话说，可以是目标RRC消息处在MAC PDU内的前面，RRCResumeRequest/RRCResumeRequest1消息处在MAC PDU内的后面。
下面结合具体的实施例对本申请进行详细说明。
实施例一
此实施例一中，目标RRC消息为MBSCountingResponse消息，通过随机接入过程来发送目标RRC消息。
如图3所示，对应的目标RRC消息发送过程可包括：
步骤30：准备阶段。
UE的RRC层收到MBSCountingRequest消息后，如果UE正在接收或感兴趣接收MBSCountingRequest消息中的指示的MBS业务，UE将有发送MBSCountingResponse消息给网络侧设备的需求。UE将触发RRCResume过程，产生RRCResumeRequest/RRCResumeRequest1消息并提交给底层，产生MBSCountingResponse消息并提交给底层。
→UAC相关设置：设置Access category为11，Access identity为0，执行UAC并通过UAC检查，即接入尝试被允许。
→设置ResumeCause值:设置RRCResumeCause为MO-RRCmessage。
→RRCResumeRequest/RRCResumeRequest1消息的产生和提交给底层：比如，UE的RRC层产生ResumeCause值为MO-RRCmessage的RRCResumeRequest/RRCResumeRequest1消息，并提交给底层。
→MBSCountingResponse消息的产生和提交给底层:比如，当RRCResumeRequest/RRCResumeRequest1提交给底层后，立即触发MBSCountingResponse消息的产生和提交给底层。
步骤31：UE的MAC层发起随机接入过程，向基站gNB发送Msg1，即随机接入导码。
步骤32：gNB向UE返回Msg2，即随机接入响应(RAR)。
步骤33：UE的MAC层将同时包括RRCResumeRequest/RRCResumeRequest1消息和MBSCountingResponse消息 的一个MAC PDU通过Msg3发送给gNB。
步骤34：gNB向UE返回Msg4，该消息中包含RRCRelease消息。
实施例二
此实施例二中，目标RRC消息为PURConfigurationRequest消息，通过PUR传输来发送目标RRC消息。
如图4所示，对应的目标RRC消息发送过程可包括：
步骤40：准备阶段。
UE具有有效的PUR资源。当UE不再感兴趣PUR配置后，UE将有发送PURConfigurationRequest消息给网络侧设备的需求。UE的RRC层将请求RRC resumption并发起PUR的传输，触发RRCResume过程，产生RRCResumeRequest/RRCResumeRequest1消息并提交给底层，产生PURConfigurationRequest消息并提交给底层。
→UAC相关设置：与MO-data相同，即设置Access category为7，Access identity为0，执行UAC并通过UAC检查，即接入尝试被允许。
→设置ResumeCause值:与MO-data相同，设置RRCResumeCause值为MO-data。
→RRCResumeRequest/RRCResumeRequest1消息的产生和提交给底层：比如，UE的RRC层产生ResumeCause值为MO-data的RRCResumeRequest/RRCResumeRequest1消息，并提交给底层。
→PURConfigurationRequest消息的产生和提交给底层：比如，当RRCResumeRequest/RRCResumeRequest1提交给底层后，立即触发PURConfigurationRequest消息的产生和提交给底层。
步骤41：UE向gNB发送RRCResumeRequest/RRCResumeRequest1消息和PURConfigurationRequest消息。
可选的，UE的MAC层执行PUR传输，将同时包含RRCResumeRequest/RRCResumeRequest1消息和PURConfigurationRequest消息的一个MAC PDU提交给物理层，并发送给gNB。
步骤42：gNB向UE发送RRCRelease消息。
实施例三
此实施例三中，目标RRC消息为MBSCountingResponse消息，通过EDT来发送目标RRC消息。
如图5所示，对应的目标RRC消息发送过程可包括：
步骤50：准备阶段。
UE的RRC层收到MBSCountingRequest消息后，如果UE正在接收或感兴趣接收MBSCountingRequest消息中的指示的MBS业务，UE将有发送MBSCountingResponse消息给网络侧设备的需求。UE的RRC层将请求RRC resumption并发起EDT，触发RRCResume过程，产生RRCResumeRequest/RRCResumeRequest1消息并提交给底层，产生PURConfigurationRequest消息并提交给底层。
→UAC相关设置：设置Access category为11，Access identity为0，执行UAC并通过UAC检查，即接入尝试被允许。
→设置ResumeCause值:设置RRCResumeCause为MO-RRCmessage。
→RRCResumeRequest/RRCResumeRequest1消息的产生和提交给底层：比如，UE的RRC层产生ResumeCause值为MO-RRCmessage的RRCResumeRequest/RRCResumeRequest1消息，并提交给底层。
→MBSCountingResponse消息的产生和提交给底层:比如，当RRCResumeRequest/RRCResumeRequest1提交给底层后，立即触发MBSCountingResponse消息的产生和提交给底层。
步骤51：UE向gNB发送RRCResumeRequest/RRCResumeRequest1消息和MBSCountingResponse消息。
可选的，UE的MAC层执行EDT，将同时包括RRCResumeRequest/RRCResumeRequest1消息和MBSCountingResponse消息的一个MAC PDU提交给物理层，并发送给gNB。
步骤52：gNB向UE发送RRCRelease消息。
需要说明的是，本申请实施例提供的消息发送方法，执行主体可以为消息发送装置，或者，该消息发送装置中的用于执行消息发送方法的控制模块。本申请实施例中以消息发送装置执行消息发送方法为例，说明本申请实施例提供的消息发送装置。
请参见图6，图6是本发明实施例提供的一种消息发送装置的结构示意图，应用于终端。如图6所示，该消息发送装置60包括：
第一发送模块61，用于在所述终端处于非RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送所述目标RRC消息；所述目标RRC消息为需要激活的接入层安全的RRC消息。
可选的，该消息发送装置60还包括：
第一执行模块，用于执行以下内容：
触发RRC连接恢复过程，生成RRC恢复请求或RRC恢复请求1消息，并将所述RRC恢复请求或RRC恢复请求1消息提交给底层；
触发所述目标RRC消息的内容的生成，并触发将所述目标RRC消息提交给底层。
可选的，该消息发送装置60还包括：
设置模块，用于设置ResumeCause值；
其中，所述ResumeCause值为以下至少一种：
复用现有的ResumeCause值；
新设置的ResumeCause值；其中，所述新设置的ResumeCause值与所述目标RRC消息无关，或者，所述新设置的ResumeCause值与所述目标RRC消息有关。
可选的，该消息发送装置60还包括：
第二执行模块，用于执行以下至少一项：
不进行统一接入控制UAC的检查；
利用设置的现有的接入类别和/或接入标识进行UAC的检查；
利用设置的新的接入类别和/或接入标识进行UAC的检查；其中，所述新的接入类别和/或接入标识与所述目标RRC消息无关，或者，所述新的接入类别和/或接入标识与所述目标RRC消息有关。
可选的，所述第一执行模块具体用于执行以下至少一项：
当所述终端有发送目标RRC消息给网络侧设备的需求时，立即触发所述目标RRC消息的内容的生成；
在所述RRC连接恢复过程中触发所述目标RRC消息的内容的生成。
可选的，所述第一执行模块具体用于执行以下至少一项：
在所述RRC连接恢复过程的发起阶段，触发所述目标RRC消息的内容的生成；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复信令无线承载SRB1前，触发所述目标RRC消息的内容的生成；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发所述目标RRC消息的内容的生成；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发所述目标RRC消息的内容的生成。
可选的，所述第一执行模块具体用于执行以下至少一项：
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发将所述目标RRC消息提交给底层；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发将所述目标RRC消息提交给底层。
可选的，该消息发送装置60还包括：
存储模块，用于在所述目标RRC消息中的内容生成后，利用第一数学表达形式对所述目标RRC消息中的内容进行存储，或者，不对所述目标RRC消息中的内容进行存储。
可选的，所述第一数学表达形式包括以下至少一项：
变量、数组、结构体。
可选的，所述第一发送模块61具体用于：
将所述目标RRC消息以及所述RRC恢复请求或RRC恢复请求1消息，复用在同一个MAC PDU中发送给网络侧设备。
可选的，所述MAC PDU的构成为以下至少一种：
所述RRC恢复请求或RRC恢复请求1消息位于所述目标RRC消息之前；
所述RRC恢复请求或RRC恢复请求1消息位于所述目标RRC消息之 后。
可选的，所述第一执行模块还用于：
在MAC层发起随机接入过程。
可选的，所述随机接入过程的触发事件为以下至少一种：
复用现有的触发事件；
新设置的触发事件；其中，所述新设置的触发事件与所述目标RRC消息无关，或者，所述新设置的触发事件与所述目标RRC消息有关。
可选的，所述随机接入过程中的资源和参数的配置情况为以下至少一种：
全部单独配置；
全部复用现有的配置；
部分复用现有的配置，部分单独配置。
可选的，所述第一执行模块还用于：
在RRC层请求RRC连接恢复，并发起第一传输方式的传输；
在MAC层执行第一传输方式的传输。
可选的，所述第一传输方式的传输的发起条件为以下至少一种：
RRC层请求RRC连接恢复；
所述终端支持第一传输方式的传输；
网络支持第一传输方式的传输；
所述终端有一个有效的第一传输方式的配置；
所述终端有一个有效的定时调整值；
所述终端有一个存储的nextHopChainingCount值，且所述nextHopChainingCount值是由最新一次RRC释放消息中的suspendConfig提供的；
包含所述目标RRC消息的MAC PDU的尺寸小于或等于，第一传输方式的配置中定义的传输块尺寸TBS。
可选的，所述第一执行模块还用于：
触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层。
可选的，所述第一执行模块具体用于执行以下至少一项：
在第一传输方式的传输的发起条件满足后，立即触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1前，触发RRC层指示底层使用第一传输方式的传输并所述发送第一传输方式的传输对应的上行授权给底层；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层。
可选的，所述第一执行模块还用于：
在RRC层请求RRC连接恢复，并发起第二传输方式的传输；
在MAC层执行第二传输方式的传输。
可选的，所述第二传输方式的传输的发起条件为以下至少一种：
在RRC层请求RRC连接恢复；
所述终端支持第二传输方式的传输；
网络支持第二传输方式的传输；
所述终端有一个存储的nextHopChainingCount值，且所述nextHopChainingCount值是由最新一次RRC释放消息中的suspendConfig提供的；
所述终端获取的系统信息中配置了第二传输方式的传输相关的所有参数；
包含所述目标RRC消息的MAC PDU的尺寸小于或等于，第二传输方式的传输的配置中定义的传输块尺寸TBS。
可选的，所述第一执行模块还用于：
触发RRC层配置底层使用第二传输方式的传输，且为以下至少一种：
在第二传输方式的传输的发起条件满足后，立即触发RRC层配置底层使 用第二传输方式的传输；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1前，触发RRC层配置底层使用第二传输方式的传输；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层配置底层使用第二传输方式的传输；
在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层配置底层使用第二传输方式的传输。
可选的，所述目标RRC消息为第一传输方式的配置相关的RRC消息时，在满足以下至少一项的情况下，所述终端有发送目标RRC消息给网络侧设备的需求：
所述终端支持第一传输方式的传输；
网络支持第一传输方式的传输；
包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大传输块尺寸TBS；
所述终端满足以下至少一项：对第一传输方式的配置感兴趣、不再对第一传输方式的配置感兴趣、需要更新第一传输方式的配置。
可选的，所述目标RRC消息为多播广播业务MBS计数相关的RRC消息时，在满足以下至少一项的情况下，所述终端有发送目标RRC消息给网络侧设备的需求：
所述终端具有MBS能力；
网络支持MBS；
包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大TBS；
所述终端的RRC层接收到网络侧设备发送的MBS计数相关的控制消息；
所述终端正在接收或者感兴趣接收MBS计数相关的控制消息中指示的至少一个MBS业务。
可选的，所述目标RRC消息为MBS兴趣指示相关的RRC消息时，在满足以下至少一项的情况下，所述终端有发送目标RRC消息给网络侧设备的需 求：
所述终端具有MBS能力；
网络支持MBS；
包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大TBS；
所述终端接收了网络侧设备发送的MBS业务相关的控制信息；
所述终端进入或离开服务区域；
MBS会话开始或停止；
MBS兴趣指示消息的内容发生改变；
发送MBS业务相关控制信息的小区或基站发生改变。
本申请实施例中的消息发送装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的消息发送装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的消息发送装置60能够实现图2所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图7，图7是本发明实施例提供的一种消息接收方法的流程图，该方法应用于网络侧设备，如图7所示，该方法包括如下步骤：
步骤701：从终端接收目标RRC消息。
其中，所述目标RRC消息为需要激活的接入层安全的RRC消息；所述目标RRC消息是所述终端在处于非RRC连接态，且有发送所述目标RRC消息的需求的情况下，在非RRC连接态发送的。
本实施例中，可以接收终端在非RRC连接态直接发送目标RRC消息，而不需要终端在其他触发RRC连接建立或恢复的条件满足下，且RRC连接 成功建立或恢复之后才能发送目标RRC消息，从而减少时延。进一步的，还可以避免资源浪费、能耗等。
可选的，上述从终端接收目标RRC消息的过程可包括：
通过MAC PDU从终端接收目标RRC消息；其中，所述MAC PDU中复用有所述目标RRC消息以及RRC恢复请求或RRC恢复请求1消息。
可选的，所述目标RRC消息为第一传输方式的传输的配置相关的RRC消息时，所述方法还包括：
向所述终端发送指示网络支持第一传输方式的传输的指示信息。
可选的，所述目标RRC消息为MBS计数相关的RRC消息时，所述方法还包括以下至少一项：
向所述终端发送指示网络支持MBS的指示信息；
向所述终端发送MBS计数相关的控制消息。
可选的，所述目标RRC消息为MBS兴趣指示相关的RRC消息时，所述方法还包括以下至少一项：
向所述终端发送指示网络支持MBS的指示信息；比如，可通过系统信息发送该指示信息；
向所述终端发送MBS业务相关的控制信息；比如，可通过系统消息或者专用RRC信令发送该控制信息。
需要说明的是，本申请实施例提供的消息接收方法，执行主体可以为消息接收装置，或者，该消息接收装置中的用于执行消息接收方法的控制模块。本申请实施例中以消息接收装置执行消息接收方法为例，说明本申请实施例提供的消息接收装置。
请参见图8，图8是本发明实施例提供的一种消息接收装置的结构示意图，应用于网络侧设备。如图8所示，该消息接收装置80包括：
接收模块81，用于从终端接收目标RRC消息；
其中，所述目标RRC消息为需要激活的接入层安全的RRC消息；所述目标RRC消息是所述终端在处于非RRC连接态，且有发送所述目标RRC消息的需求的情况下，在非RRC连接态发送的。
可选的，该接收模块81还用于：通过MAC PDU从所述终端接收所述目 标RRC消息；所述MAC PDU中复用有所述目标RRC消息以及RRC恢复请求或RRC恢复请求1消息。
可选的，该消息接收装置80还包括：
第二发送模块，用于当所述目标RRC消息为第一传输方式的传输的配置相关的RRC消息时，向所述终端发送指示网络支持第一传输方式的传输的指示信息；
或者，当所述目标RRC消息为MBS计数相关的RRC消息时，向所述终端发送指示网络支持MBS的指示信息，和/或向所述终端发送MBS计数相关的控制消息；
或者，当所述目标RRC消息为MBS兴趣指示相关的RRC消息时，向所述终端发送指示网络支持MBS的指示信息，和/或向所述终端发送MBS业务相关的控制信息。
本申请实施例提供的消息接收装置80能够实现图7所示方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图9所示，本申请实施例还提供一种通信设备90，包括处理器91，存储器92，存储在存储器92上并可在处理器91上运行的程序或指令，例如，该通信设备90为终端时，该程序或指令被处理器91执行时实现上述消息发送方法实施例的各个过程，且能达到相同的技术效果。该通信设备90为网络侧设备时，该程序或指令被处理器91执行时实现上述消息接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图10为实现本申请实施例的一种终端的硬件结构示意图。
该终端100包括但不限于：射频单元101、网络模块102、音频输出单元103、输入单元104、传感器105、显示单元106、用户输入单元107、接口单元108、存储器109、以及处理器110等部件。
本领域技术人员可以理解，终端100还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器110逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图10中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或 者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元104可以包括图形处理器(Graphics Processing Unit，GPU)1041和麦克风1042，图形处理器1041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元106可包括显示面板1061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板1061。用户输入单元107包括触控面板1071以及其他输入设备1072。触控面板1071，也称为触摸屏。触控面板1071可包括触摸检测装置和触摸控制器两个部分。其他输入设备1072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元101将来自网络侧设备的下行数据接收后，给处理器110处理；另外，将上行的数据发送给网络侧设备。通常，射频单元101包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器109可用于存储软件程序或指令以及各种数据。存储器109可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器109可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器110可包括一个或多个处理单元；可选的，处理器110可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器110中。
其中，射频单元101，用于在终端100处于非RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送该目标 RRC消息；该目标RRC消息为需要激活的接入层安全的RRC消息。
本申请实施例提供的终端100能够实现图2所示方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
具体地，本申请实施例还提供了一种网络侧设备。如图11所示，该网络侧设备110包括：天线111、射频装置112、基带装置113。天线111与射频装置112连接。在上行方向上，射频装置112通过天线111接收信息，将接收的信息发送给基带装置113进行处理。在下行方向上，基带装置113对要发送的信息进行处理，并发送给射频装置112，射频装置112对收到的信息进行处理后经过天线111发送出去。
上述频带处理装置可以位于基带装置113中，以上实施例中网络侧设备执行的方法可以在基带装置113中实现，该基带装置113包括处理器114和存储器115。
基带装置113例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图11所示，其中一个芯片例如为处理器114，与存储器115连接，以调用存储器115中的程序，执行以上方法实施例中所示的网络侧设备操作。
该基带装置113还可以包括网络接口116，用于与射频装置112交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器115上并可在处理器114上运行的指令或程序，处理器114调用存储器115中的指令或程序执行图8中所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述消息发送方法实施例的各个过程，或者实现上述消息接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述消息发送方法实施例的各个过程，或者实现上述消息接收方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络侧设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (36)

  1. 一种消息发送方法，应用于终端，包括：
    在所述终端处于非无线资源控制RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送所述目标RRC消息；
    其中，所述目标RRC消息为需要激活的接入层安全的RRC消息。
  2. 根据权利要求1所述的方法，其中，在发送所述目标RRC消息之前，所述方法还包括：
    触发RRC连接恢复过程，生成RRC恢复请求或RRC恢复请求1消息，并将所述RRC恢复请求或RRC恢复请求1消息提交给底层；
    触发所述目标RRC消息的内容的生成，并触发将所述目标RRC消息提交给底层。
  3. 根据权利要求2所述的方法，其中，在所述RRC连接恢复过程中，所述方法还包括：
    设置恢复原因ResumeCause值；
    其中，所述ResumeCause值为以下至少一种：
    复用现有的ResumeCause值；
    新设置的ResumeCause值；其中，所述新设置的ResumeCause值与所述目标RRC消息无关，或者，所述新设置的ResumeCause值与所述目标RRC消息有关。
  4. 根据权利要求2所述的方法，其中，在所述RRC连接恢复过程中，所述方法还包括以下至少一项：
    不进行统一接入控制UAC的检查；
    利用设置的现有的接入类别和/或接入标识进行UAC的检查；
    利用设置的新的接入类别和/或接入标识进行UAC的检查；其中，所述新的接入类别和/或接入标识与所述目标RRC消息无关，或者，所述新的接入类别和/或接入标识与所述目标RRC消息有关。
  5. 根据权利要求2所述的方法，其中，所述触发所述目标RRC消息的内容的生成，包括以下至少一项：
    当所述终端有发送目标RRC消息给网络侧设备的需求时，立即触发所述目标RRC消息的内容的生成；
    在所述RRC连接恢复过程中触发所述目标RRC消息的内容的生成。
  6. 根据权利要求5所述的方法，其中，所述在所述RRC连接恢复过程中触发所述目标RRC消息的内容的生成，包括以下至少一项：
    在所述RRC连接恢复过程的发起阶段，触发所述目标RRC消息的内容的生成；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复信令无线承载SRB1前，触发所述目标RRC消息的内容的生成；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发所述目标RRC消息的内容的生成；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发所述目标RRC消息的内容的生成。
  7. 根据权利要求2所述的方法，其中，所述触发将所述目标RRC消息提交给底层，包括以下至少一项：
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发将所述目标RRC消息提交给底层；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发将所述目标RRC消息提交给底层。
  8. 根据权利要求2所述的方法，其中，所述方法还包括：
    在所述目标RRC消息中的内容生成后，利用第一数学表达形式对所述目标RRC消息中的内容进行存储，或者，不对所述目标RRC消息中的内容进行存储。
  9. 根据权利要求8所述的方法，其中，所述第一数学表达形式包括以下至少一项：
    变量、数组、结构体。
  10. 根据权利要求2所述的方法，其中，所述发送所述目标RRC消息， 包括：
    将所述目标RRC消息以及所述RRC恢复请求或RRC恢复请求1消息，复用在同一个媒体接入控制协议数据单元MAC PDU中发送给网络侧设备。
  11. 根据权利要求10所述的方法，其中，所述MAC PDU的构成为以下至少一种：
    所述RRC恢复请求或RRC恢复请求1消息位于所述目标RRC消息之前；
    所述RRC恢复请求或RRC恢复请求1消息位于所述目标RRC消息之后。
  12. 根据权利要求2或10所述的方法，其中，所述发送所述目标RRC消息之前，所述方法还包括：
    在MAC层发起随机接入过程。
  13. 根据权利要求12所述的方法，其中，所述随机接入过程的触发事件为以下至少一种：
    复用现有的触发事件；
    新设置的触发事件；其中，所述新设置的触发事件与所述目标RRC消息无关，或者，所述新设置的触发事件与所述目标RRC消息有关。
  14. 根据权利要求12所述的方法，其中，所述随机接入过程中的资源和参数的配置情况为以下至少一种：
    全部单独配置；
    全部复用现有的配置；
    部分复用现有的配置，部分单独配置。
  15. 根据权利要求2或10所述的方法，其中，在发送所述目标RRC消息之前，所述方法还包括：
    在RRC层请求RRC连接恢复，并发起第一传输方式的传输；
    在MAC层执行第一传输方式的传输。
  16. 根据权利要求15所述的方法，其中，所述第一传输方式的传输的发起条件为以下至少一种：
    RRC层请求RRC连接恢复；
    所述终端支持第一传输方式的传输；
    网络支持第一传输方式的传输；
    所述终端有一个有效的第一传输方式的配置；
    所述终端有一个有效的定时调整值；
    所述终端有一个存储的nextHopChainingCount值，且所述nextHopChainingCount值是由最新一次RRC释放消息中的suspendConfig提供的；
    包含所述目标RRC消息的MAC PDU的尺寸小于或等于，第一传输方式的配置中定义的传输块尺寸TBS。
  17. 根据权利要求15所述的方法，其中，所述方法还包括：
    触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层。
  18. 根据权利要求17所述的方法，其中，所述触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层，包括以下至少一种：
    在第一传输方式的传输的发起条件满足后，立即触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1前，触发RRC层指示底层使用第一传输方式的传输并所述发送第一传输方式的传输对应的上行授权给底层；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层指示底层使用第一传输方式的传输并发送所述第一传输方式的传输对应的上行授权给底层。
  19. 根据权利要求2或10所述的方法，其中，在发送所述目标RRC消 息之前，所述方法还包括：
    在RRC层请求RRC连接恢复，并发起第二传输方式的传输；
    在MAC层执行第二传输方式的传输。
  20. 根据权利要求19所述的方法，其中，所述第二传输方式的传输的发起条件为以下至少一种：
    在RRC层请求RRC连接恢复；
    所述终端支持第二传输方式的传输；
    网络支持第二传输方式的传输；
    所述终端有一个存储的nextHopChainingCount值，且所述nextHopChainingCount值是由最新一次RRC释放消息中的suspendConfig提供的；
    所述终端获取的系统信息中配置了第二传输方式的传输相关的所有参数；
    包含所述目标RRC消息的MAC PDU的尺寸小于或等于，第二传输方式的传输的配置中定义的传输块尺寸TBS。
  21. 根据权利要求19所述的方法，其中，所述方法还包括：
    触发RRC层配置底层使用第二传输方式的传输，且为以下至少一种：
    在第二传输方式的传输的发起条件满足后，立即触发RRC层配置底层使用第二传输方式的传输；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1前，触发RRC层配置底层使用第二传输方式的传输；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的恢复SRB1后，立即触发RRC层配置底层使用第二传输方式的传输；
    在所述RRC恢复请求或RRC恢复请求1消息传输相关的操作过程中的提交所述RRC恢复请求或RRC恢复请求1消息给底层后，立即触发RRC层配置底层使用第二传输方式的传输。
  22. 根据权利要求1所述的方法，其中，所述目标RRC消息为第一传输方式的配置相关的RRC消息时，在满足以下至少一项的情况下，所述终端有发送目标RRC消息给网络侧设备的需求：
    所述终端支持第一传输方式的传输；
    网络支持第一传输方式的传输；
    包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大传输块尺寸TBS；
    所述终端满足以下至少一项：对第一传输方式的配置感兴趣、不再对第一传输方式的配置感兴趣、需要更新第一传输方式的配置。
  23. 根据权利要求1所述的方法，其中，所述目标RRC消息为多播广播业务MBS计数相关的RRC消息时，在满足以下至少一项的情况下，所述终端有发送目标RRC消息给网络侧设备的需求：
    所述终端具有MBS能力；
    网络支持MBS；
    包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大TBS；
    所述终端的RRC层接收到网络侧设备发送的MBS计数相关的控制消息；
    所述终端正在接收或者感兴趣接收MBS计数相关的控制消息中指示的至少一个MBS业务。
  24. 根据权利要求1所述的方法，其中，所述目标RRC消息为MBS兴趣指示相关的RRC消息时，在满足以下至少一项的情况下，所述终端有发送目标RRC消息给网络侧设备的需求：
    所述终端具有MBS能力；
    网络支持MBS；
    包含目标RRC消息的MAC PDU的尺寸小于或等于，基于终端种类定义的终端支持的最大TBS；
    所述终端接收了网络侧设备发送的MBS业务相关的控制信息；
    所述终端进入或离开服务区域；
    MBS会话开始或停止；
    MBS兴趣指示消息的内容发生改变；
    发送MBS业务相关控制信息的小区或基站发生改变。
  25. 一种消息接收方法，应用于网络侧设备，包括：
    从终端接收目标RRC消息；
    其中，所述目标RRC消息为需要激活的接入层安全的RRC消息；所述目标RRC消息是所述终端在处于非RRC连接态，且有发送所述目标RRC消息的需求的情况下，在非RRC连接态发送的。
  26. 根据权利要求25所述的方法，其中，所述从终端接收目标RRC消息，包括：
    通过MAC PDU从所述终端接收所述目标RRC消息；
    其中，所述MAC PDU中复用有所述目标RRC消息以及RRC恢复请求或RRC恢复请求1消息。
  27. 根据权利要求25所述的方法，其中，所述目标RRC消息为第一传输方式的传输的配置相关的RRC消息时，所述方法还包括：
    向所述终端发送指示网络支持第一传输方式的传输的指示信息。
  28. 根据权利要求25所述的方法，其中，所述目标RRC消息为MBS计数相关的RRC消息时，所述方法还包括以下至少一项：
    向所述终端发送指示网络支持MBS的指示信息；
    向所述终端发送MBS计数相关的控制消息。
  29. 根据权利要求25所述的方法，其中，所述目标RRC消息为MBS兴趣指示相关的RRC消息时，所述方法还包括以下至少一项：
    向所述终端发送指示网络支持MBS的指示信息；
    向所述终端发送MBS业务相关的控制信息。
  30. 一种消息发送装置，应用于终端，包括：
    第一发送模块，用于在所述终端处于非RRC连接态，且有发送目标RRC消息给网络侧设备的需求的情况下，在非RRC连接态发送所述目标RRC消息；
    其中，所述目标RRC消息为需要激活的接入层安全的RRC消息。
  31. 一种消息接收装置，应用于网络侧设备，包括：
    接收模块，用于从终端接收目标RRC消息；
    其中，所述目标RRC消息为需要激活的接入层安全的RRC消息；所述目标RRC消息是所述终端在处于非RRC连接态，且有发送所述目标RRC消息的需求的情况下，在非RRC连接态发送的。
  32. 一种通信设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求1至24任一项所述的消息发送方法的步骤，或者实现如权利要求25至29任一项所述的消息接收方法的步骤。
  33. 一种可读存储介质，所述可读存储介质上存储程序或指令，其中，所述程序或指令被处理器执行时实现如权利要求1至24任一项所述的消息发送方法的步骤，或者实现如权利要求25至29任一项所述的消息接收方法的步骤。
  34. 一种芯片，包括处理器和通信接口，其中，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至24任一项所述的消息发送方法的步骤，或者实现如权利要求25至29任一项所述的消息接收方法的步骤。
  35. 一种计算机程序产品，其中，所述程序产品被存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现如权利要求1至24任一项所述的消息发送方法的步骤，或者实现如权利要求25至29任一项所述的消息接收方法的步骤。
  36. 一种通信设备，其中，所述通信设备被配置为执行如权利要求1至24任一项所述的消息发送方法的步骤，或者实现如权利要求25至29任一项所述的消息接收方法的步骤。
PCT/CN2021/104705 2020-07-06 2021-07-06 消息发送方法、接收方法、装置及通信设备 WO2022007785A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2022580816A JP2023532700A (ja) 2020-07-06 2021-07-06 メッセージ送信方法、受信方法、装置及び通信機器
EP21838450.1A EP4178310A4 (en) 2020-07-06 2021-07-06 METHOD AND DEVICE FOR SENDING MESSAGES, METHOD AND DEVICE FOR RECEIVING MESSAGES AND COMMUNICATION DEVICE
US18/149,228 US20230156851A1 (en) 2020-07-06 2023-01-03 Message sending method and apparatus, message receiving method and apparatus, and communication device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010643208.0 2020-07-06
CN202010643208.0A CN113905457B (zh) 2020-07-06 2020-07-06 消息发送方法、接收方法、装置及通信设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/149,228 Continuation US20230156851A1 (en) 2020-07-06 2023-01-03 Message sending method and apparatus, message receiving method and apparatus, and communication device

Publications (1)

Publication Number Publication Date
WO2022007785A1 true WO2022007785A1 (zh) 2022-01-13

Family

ID=79186811

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/104705 WO2022007785A1 (zh) 2020-07-06 2021-07-06 消息发送方法、接收方法、装置及通信设备

Country Status (5)

Country Link
US (1) US20230156851A1 (zh)
EP (1) EP4178310A4 (zh)
JP (1) JP2023532700A (zh)
CN (1) CN113905457B (zh)
WO (1) WO2022007785A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109936878A (zh) * 2017-12-18 2019-06-25 华为技术有限公司 一种触发状态恢复的方法以及终端设备
CN110856276A (zh) * 2019-11-15 2020-02-28 展讯通信（上海）有限公司 非连接态ue的数据传输、接收方法及装置、终端、基站
WO2020069103A1 (en) * 2018-09-27 2020-04-02 Intel Corporation System and methods for enabling dl-edt

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11553550B2 (en) * 2018-07-04 2023-01-10 Lg Electronics Inc. Method and apparatus for supporting security in RRC inactive state in wireless communication system
JP2022501842A (ja) * 2018-08-17 2022-01-06 オッポ広東移動通信有限公司Guangdong Oppo Mobile Telecommunications Corp., Ltd. 情報伝送方法、装置及び通信デバイス
PL3677089T3 (pl) * 2018-09-25 2021-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Żądanie wznowienia z następującym po nim zwolnieniem i przekierowaniem
WO2020092415A1 (en) * 2018-11-01 2020-05-07 Intel Corporation Transmission, retransmission, and hybrid automatic repeat request (harq) for preconfigured uplink resource (pur) in idle mode

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109936878A (zh) * 2017-12-18 2019-06-25 华为技术有限公司 一种触发状态恢复的方法以及终端设备
WO2020069103A1 (en) * 2018-09-27 2020-04-02 Intel Corporation System and methods for enabling dl-edt
CN110856276A (zh) * 2019-11-15 2020-02-28 展讯通信（上海）有限公司 非连接态ue的数据传输、接收方法及装置、终端、基站

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Handling fallback issues in EDT", 3GPP DRAFT; R2-1807522 FALLBACK IN EDT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Busan, Republic of Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051443892 *
See also references of EP4178310A4 *

Also Published As

Publication number Publication date
EP4178310A4 (en) 2023-12-13
CN113905457A (zh) 2022-01-07
EP4178310A1 (en) 2023-05-10
CN113905457B (zh) 2023-08-08
US20230156851A1 (en) 2023-05-18
JP2023532700A (ja) 2023-07-31

Similar Documents

Publication Publication Date Title
WO2022068790A1 (zh) 执行目标操作的方法、装置和终端设备
WO2022042752A1 (zh) 物理下行控制信道的监听方法、装置和设备
WO2022033531A1 (zh) 传输系统消息的方法、终端设备和网络设备
WO2022017359A1 (zh) 直接通信启动控制方法及相关设备
WO2022037489A1 (zh) 非连续接收的处理方法、装置、终端及网络侧设备
WO2022033549A1 (zh) 无线资源控制连接建立方法、装置、终端及网络侧设备
WO2022022488A1 (zh) 传输辅助信息的方法、终端设备和网络设备
WO2022017360A1 (zh) 直接通信启动控制方法及相关设备
WO2022007786A1 (zh) 消息发送方法、接收方法、装置及通信设备
US20230180303A1 (en) Uplink timing advance value processing method, apparatus, and terminal
US20230109276A1 (en) Access procedure processing method, apparatus and communications device
WO2022068679A1 (zh) 广播多播业务的拥塞控制方法、装置和设备
WO2022184101A1 (zh) 间隙gap处理方法、装置、设备及存储介质
WO2022007785A1 (zh) 消息发送方法、接收方法、装置及通信设备
WO2022068813A1 (zh) 拥塞控制方法、装置、终端及网络侧设备
WO2022033429A1 (zh) 数据发送处理方法、资源配置方法及相关设备
WO2022148431A1 (zh) 非连续接收drx配置切换的方法、装置及终端
WO2021239075A1 (zh) 下行数据的处理方法、装置及终端
WO2022017481A1 (zh) 业务传输资源的更新方法、终端及网络侧设备
WO2022083630A1 (zh) 寻呼方法、装置、终端、网络侧设备及可读存储介质
WO2022161313A1 (zh) 连接保持方法、装置及电子设备
US20230262794A1 (en) Method for establishing connected state, terminal, core network function, and access network device
WO2022194177A1 (zh) 监听控制方法及相关设备
WO2022237677A1 (zh) 随机接入的处理方法、装置及终端
WO2022068752A1 (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: 21838450

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022580816

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021838450

Country of ref document: EP

Effective date: 20230206