Message sending method, receiving method, device and communication device

Abstract

This application discloses a message sending method, a receiving method, an apparatus, and a communication device, which belong to the technical field of communication. A specific implementation method includes, when a terminal is in an unconnected RRC state and there is a need to send a target RRC message to a network side device, sending the target RRC message in the unconnected RRC state, where the target RRC message is an RRC message that requires activated access stratum security. This allows the terminal to directly send the target RRC message in the unconnected RRC state without waiting until other conditions that trigger the establishment or resumption of an RRC connection are met and the establishment or resumption of an RRC connection is successful, thereby reducing delay.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to China Patent Application No. 202010643208.0, filed in China on July 6, 2020, the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the technical field of communications, and in particular to a message sending method, a message receiving method, an apparatus and a communication device. [Background technology]

[0003] Currently, when a terminal in a non-RRC connected state needs to transmit an RRC message requiring activated access stratum security to a network side device, the terminal can transmit the RRC message only after other conditions for triggering the establishment or resumption of an RRC connection are met and the establishment or resumption of an RRC connection is successful, which causes a large delay in transmitting the RRC message in a conventional non-RRC connected state terminal. Summary of the Invention [Problem to be solved by the invention]

[0004] The objective of the embodiments of the present application is to provide a message transmission method, a receiving method, an apparatus and a communication device to solve the problem of large delay when a conventional non-RRC connected terminal transmits an RRC message requiring activated AS security. [Means for solving the problem]

[0005] In order to solve the above technical problems, the present application is realized as follows.

[0006] In a first aspect, the present disclosure provides a message sending method applied to a terminal, comprising: When the terminal is in a non-radio resource control (RRC) connected state and there is a need to transmit a target RRC message to a network side device, transmitting the target RRC message in a non-RRC connected state; The method for transmitting a message is provided, wherein the target RRC message is an RRC message that requires activated access stratum security.

[0007] In a second aspect, the present disclosure provides a message receiving method applied to a network side device, comprising: receiving a target RRC message from a terminal; The target RRC message is an RRC message that requires activated access stratum security, and the target RRC message is transmitted in a non-RRC connected state when the terminal is in a non-RRC connected state and there is a need to transmit the target RRC message.

[0008] In a third aspect, the present disclosure provides a message sending device applied to a terminal, comprising: A first transmission module is provided for transmitting a 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 transmit a target RRC message to a network side device; The target RRC message is an RRC message that requires activated access stratum security.

[0009] In a fourth aspect, the present disclosure provides a message receiving device applied to a network side device, A receiving module for receiving a target RRC message from a terminal, The target RRC message is an RRC message that requires activated access stratum security, and the target RRC message is transmitted in a non-RRC connected state when the terminal is in a non-RRC connected state and there is a demand to transmit the target RRC message.

[0010] In a fifth aspect, there is provided a terminal comprising a processor, a memory, and a program or command stored in the memory and executable on the processor, the program or command causing, when executed by the processor, to realize steps of the method according to the first aspect.

[0011] In a sixth aspect, the present disclosure provides a network side device comprising a processor, a memory, and a program or command stored in the memory and executable on the processor, the program or command causing, when executed by the processor, the steps of the method according to the second aspect to be realized.

[0012] In a seventh aspect, the present disclosure provides a readable storage medium having stored thereon a program or command, which, when executed by a processor, causes the steps of the method of the first aspect to be performed or causes the steps of the method of the second aspect to be performed.

[0013] In an eighth aspect, the present disclosure provides a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor executing a program or command to implement steps of the method of the first aspect or to be used to implement steps of the method of the second aspect. Effect of the Invention

[0014] In an embodiment of the present application, when the terminal is in a non-RRC connected state and has a need to send a target RRC message to a network side device, the terminal can send the target RRC message in a non-RRC connected state, and the target RRC message is an RRC message that requires activated access stratum security. This allows the terminal to directly send the target RRC message in a non-RRC connected state without waiting until other conditions that trigger the establishment or resumption of an RRC connection are met and the establishment or resumption of an RRC connection is successful, thereby reducing delay. Furthermore, resource waste, energy consumption, etc. can also be avoided. [Brief description of the drawings]

[0015] [Figure 1] 1 is a block diagram of a wireless communication system provided in an embodiment of the present application. [Diagram 2] 1 is a flowchart of a message sending method provided in an embodiment of the present application; [Diagram 3] 4 is a flowchart of a target RRC message sending process in Example 1 of the present application; [Figure 4] 11 is a flowchart of a target RRC message sending process in Example 2 of the present application; [Diagram 5] 11 is a flowchart of a target RRC message sending process in Example 3 of the present application; [Figure 6] FIG. 2 is a structural schematic diagram of a message sending device provided in an embodiment of the present application; [Figure 7] 4 is a flowchart of a message receiving method provided in an embodiment of the present application; [Figure 8] FIG. 2 is a structural schematic diagram of a message receiving device provided in an embodiment of the present application; [Figure 9] FIG. 2 is a structural schematic diagram of a communication device provided in an embodiment of the present application; [Figure 10] FIG. 2 is a structural schematic diagram of a terminal provided in an embodiment of the present application; [Figure 11] FIG. 2 is a structural schematic diagram of a network side device provided in an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] In the following, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application. Of course, the described embodiments are only a part of the embodiments of the present application, and are not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without any creative effort shall fall within the scope of protection of the present application.

[0017] The terms "first", "second", and the like in the specification and claims of the present application are not intended to describe a particular order or sequence, but are intended to distinguish between similar objects. It should be understood that the terms used in this way may be substituted for each other in appropriate cases so that the embodiments of the present application can be carried out in an order other than that shown or described herein, and the objects distinguished by "first" and "second" are usually of one type, and the number of objects is not limited, for example, the first object may be one or more. In the specification and claims, "and / or" indicates at least one of the connected objects, and the symbol " / " generally indicates that the related objects before and after are in an "or" relationship. For example, "A and / or B" indicates three cases: "only A exists, only B exists, and both A and B exist," and "at least one of A and B" also indicates three cases: "only A exists, only B exists, and both A and B exist."

[0018] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and may also be used in other wireless communication systems such as 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), and other systems. The terms "system" and "network" in the embodiments of the present application may generally be used interchangeably, and the techniques described may be used in other systems and radio technologies as well as the systems and radio technologies mentioned above. However, in the following description, for illustrative purposes, a New Radio (NR) system is described, and NR terminology is used in most of the following description, however, these techniques are applicable to systems other than NR systems, for example, 6th generation (6G) systems. th It is also applicable to 6G (Generation, 6G) communication systems.

[0019] FIG. 1 shows a block diagram of a wireless communication system to which the embodiment 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 be called a terminal device or a user terminal (User Equipment, UE), and may be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer also called a notebook computer, a personal digital assistant (PDA), a personal digital assistant, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device, a vehicle user equipment (VUE), a pedestrian user equipment (PUE), etc., and the wearable device includes a wristband, an earphone, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side equipment 12 may be a base station or a core network, and the base station may be called 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 (BSS), an extended service set (ESS), a Node B, an evolved Node B (eNB), a home Node B, a home evolved Node B, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or any other suitable term in the field, and the base station is not limited to a specific technical term as long as the same technical effect can be achieved. It should be noted that in the embodiment of the present application, a base station in an NR system is merely taken as an example, and the specific type of the base station is not limited.

[0020] In order to facilitate understanding of the embodiments of the present application, the following will first be described.

[0021] In order to solve the problem of long delays when a conventional non-RRC connected UE (e.g., NON-RRC CONNECTED UE) transmits an RRC message requiring activated AS security, an embodiment of the present application proposes a method in which, when a NON-RRC CONNECTED UE needs to transmit an RRC message requiring activated AS security to a network side device, the NON-RRC CONNECTED UE directly transmits the RRC message in the NON-RRC CONNECTED state.

[0022] In the embodiments of the present application, the RRC message requiring activated AS security may be referred to as a target RRC message, that is, the target RRC message referred to in the following embodiments is an RRC message requiring activated AS security.

[0023] 1. Optionally, the target RRC message may be an RRC message related to the configuration of a first transmission mode, in which case, when at least one of the following is satisfied, the terminal needs to send the target RRC message to the network side device: The terminal supports transmission according to the first transmission method. The network supports transmission according to the first transmission method, for example, the system message includes a corresponding instruction. The size of the Media Access Control Protocol Data Unit (MAC PDU) containing the target RRC message is less than or equal to the maximum Transport Block Size (TBS) supported by the terminal, which is defined based on the terminal type. The terminal satisfies at least one of the following: the terminal is interested in the deployment of the first transmission scheme; the terminal is no longer interested in the deployment of the first transmission scheme; and the terminal needs to update the deployment of the first transmission scheme.

[0024] It should be noted that the first transmission scheme may be understood as a transmission scheme similar to PUR (Preconfigured Uplink Resource) transmission or pre-configured PUSCH resource transmission of small data transmission (SDT), and may be understood as a PUR transmission scheme or a pre-configured PUSCH resource transmission scheme of SDT in some cases, but is not limited thereto. In this case, the target RRC message may include auxiliary information regarding the configuration of pre-configured PUSCH resources, such as a PURConfigurationRequest message. Taking the pre-configured PUSCH resource transmission scheme of small data transmission as an example, when at least one of the following is satisfied, the UE needs to send a target RRC message to a network side device. The UE supports transmission via pre-configured PUSCH resource scheme. The network supports transmission via pre-arranged PUSCH resource scheme, for example, the system message includes a corresponding instruction. The size of the MAC PDU containing the target RRC message is less than or equal to the maximum TBS supported by the UE, which is defined based on the UE type. The UE may be interested in the placement of pre-configured PUSCH resources, may no longer be interested in it, or may need to update the placement of pre-configured PUSCH resources.

[0025] 2. Optionally, the target RRC message may be an RRC message related to Multicast and Broadcast Service (MBS) counting, such as an MBSCountingResponse message. In this case, when at least one of the following is satisfied, 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, system messages contain corresponding instructions. The size of the MAC PDU including the target RRC message is less than or equal to the maximum TBS supported by the terminal, which is defined based on the terminal type. The RRC layer of the terminal receives a control message regarding MBS counting (eg, an MBSCountingRequest message) sent from a 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).

[0026] 3. Optionally, the target RRC message may be an RRC message related to MBS Interest Indication, such as an MBSInterestIndication message, in which case, when at least one of the following is satisfied, 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, by including instructions corresponding to system messages. The size of the MAC PDU including the target RRC message is less than or equal to the maximum TBS supported by the terminal, which is defined based on the terminal type. The terminal receives control information related to the MBS service transmitted from the network side device. For example, the control information related to the MBS service may be transmitted by a system message or dedicated RRC signaling. The terminal enters or leaves the service area, for example, immediately upon entering the service area or immediately upon leaving the service area. An MBS session has started or stopped, e.g., immediately after an MBS session has started or immediately after an MBS session has stopped. The content of the MBS Interest Indication message has been changed. The cell or base station that transmits control information for the MBS service has changed.

[0027] It should be noted that the target RRC message may be selected as any other RRC message that requires activated AS security in addition to the above three types of RRC messages, and there is no limitation thereon.

[0028] Hereinafter, the message sending and receiving methods provided in the embodiments of the present application will be described in detail with reference to specific embodiments and application scenarios with reference to the accompanying drawings.

[0029] Please refer to FIG. 2, which is a flowchart of a message sending method provided in an embodiment of the present invention. The method is applied to a terminal, and as shown in FIG. 2, the method includes the following steps:

[0030] In step 201, when the terminal is in a non-RRC connected state and there is a need to transmit a target RRC message to a network side device, the target RRC message is transmitted in the non-RRC connected state.

[0031] In this embodiment, the target RRC message is an RRC message that requires activated AS security.

[0032] In the embodiment of the present application, when the terminal is in a non-RRC connected state and has a need to transmit a target RRC message to a network side device, the terminal can transmit the target RRC message in a non-RRC connected state. This allows the terminal to directly transmit the target RRC message in a non-RRC connected state without waiting until other conditions for triggering the establishment or resumption of an RRC connection are met and the establishment or resumption of an RRC connection is successful, thereby reducing delay. In addition, it can also avoid resource waste, energy consumption, etc.

[0033] In an embodiment of the present application, the terminal can transmit a target RRC message in a non-RRC connected state by an RRC connection resume process. Optionally, before transmitting the target RRC message, the terminal can trigger an RRC connection resume process, generate an RRC resume request or RRC resume request 1 (RRCResumeRequest / RRCResumeRequest1) message, submit the RRCResumeRequest / RRCResumeRequest1 message to a lower layer, and trigger the generation (also called production) of the content of the target RRC message and the submission of the target RRC message to a lower layer. It can be understood that the RRCResumeRequest / RRCResumeRequest1 message and the target RRC message are generated in an RRC layer, where the lower layer is, for example, a Packet Data Convergence Protocol (PDCP), a Radio Link Control (RLC), a MAC layer, etc., in a protocol layer below the RRC layer.

[0034] Optionally, in the RRC connection resumption process, the terminal may set a resume cause ResumeCause value, which may be at least one of a multiplexing of a first ResumeCause value, such as mo-data, mo-signal, etc., and a second ResumeCause value.

[0035] In one embodiment, the second ResumeCause value may be independent of the target RRC message, i.e., all target RRC messages are unified, for example, for MO-RRC message, the ResumeCause value is set to MO-RRC message. Independent of the target RRC message may be independent of the message type or format of the target RRC message, or independent of the content of the target RRC message.

[0036] In another embodiment, the second ResumeCause value may be related to the target RRC message. For example, for "XX configuration request message", the ResumeCause value is set to "XX configuration request message". The relationship with the target RRC message may be related to the message type or format of the target RRC message, or may be related to the content of the target RRC message.

[0037] Optionally, in the RRC connection resumption process, the terminal may further perform at least one of the following 1), 2), and 3). 1) No Unified Access Control (UAC) checks are performed and the access attempt is directly allowed. 2) Check the UAC using the existing access category first access category (Access category) and / or access identity(ies), i.e., multiplex the first access category and / or access identity(ies), e.g., Access category is 7 and Access identity is 0. 3) Check the UAC using the second access category and / or access identity(ies), i.e., check the UAC using the second Access category and / or Access identity(ies).

[0038] In one embodiment, the second Access category and / or Access identity(ies) may be independent of the target RRC message, i.e., all target RRC messages are unified to the same value, for example, Access category is unified to 11 and Access identity is unified to 6. Being independent of the target RRC message may be independent of the message type or format of the target RRC message, or may be independent of the content of the target RRC message.

[0039] In another embodiment, the second Access category and / or Access identity(ies) may be related to the target RRC message. For example, for an "XX Configuration Request Message", the Access category is set to 11 and the Access identity is set to 6. The relationship to the target RRC message may be related to the message type or format of the target RRC message, or may be related to the content of the target RRC message.

[0040] Optionally, triggering the generation of the content of the target RRC message may include at least one of the following: 1) When there is a demand for sending a target RRC message to a network side device, the terminal immediately triggers the generation of the content of the target RRC message. 2) In the RRC connection resume process, trigger the generation of the target RRC message content. That is, when the terminal needs to send the target RRC message to the network side device, the terminal first triggers the RRC connection resume process, and then triggers the generation of the target RRC message content in the RRC connection resume process. In the case of 2), the trigger may include at least one of the following (1), (2), (3), and (4). (1) At the initiation stage of the RRC connection resumption process, triggering the generation of the target RRC message content. (2) Triggering the generation of the target RRC message contents before SRB1 resumption in the action process related to transmission of RRC Resume Request or RRC Resume Request 1 message (Actions related to transmission of RRCResumeRequest or RRCResumeRequest1 message). (3) Immediately trigger the generation of the target RRC message content after SRB1 resume in the action process related to transmission of RRC Resume Request or RRC Resume Request 1 message. (4) Immediately triggering the generation of the target RRC message content after submission of the RRC Resume Request or RRC Resume Request 1 message to lower layers in the Actions related to transmission of the RRC Resume Request or RRC Resume Request 1 message.

[0041] Optionally, triggering the submission of the target RRC message to the lower layer may include at least one of the following 1) and 2). 1) Immediately trigger the submission of the target RRC message to lower layers after SRB1 resume with actions related to transmission of RRC ResumeRequest or RRCResumeRequest1 message. 2) In the action process related to transmission of the RRC Resume Request or RRC Resume Request 1 message, immediately trigger the submission of the target RRC message to the lower layers after the submission of the RRC Resume Request or RRC Resume Request 1 message to the lower layers.

[0042] Optionally, after the content in the target RRC message is generated, the terminal may store the content in the target RRC message in the first format, or may not store the content in the target RRC message.

[0043] Furthermore, the first format may include at least one of any formats, such as a variable, an array, a structure, etc. That is, after the content of the target RRC message is generated, the terminal may store the content in any format, such as a variable, an array, and / or a structure.

[0044] Alternatively, when transmitting a target RRC message, the terminal may multiplex the target RRC message and the RRC Resume Request or RRC Resume Request 1 message into the same MAC PDU and transmit the multiplexed message to the network side device. Furthermore, the configuration of the MAC PDU may be at least one of: the RRC Resume Request or RRC Resume Request 1 message is before the target RRC message; and the RRC Resume Request or RRC Resume Request 1 message is after the target RRC message.

[0045] It should be noted that the terminal transmits the target RRC message in a non-RRC connected state may be, but is not limited to, a random access process, a transmission according to a first transmission scheme, or a transmission according to a second transmission scheme. The random access process may be a conventional random access process, such as a two-step random access process or a four-step random access process. The transmission according to the first transmission scheme and the transmission according to the second transmission scheme involve completely different contents. More specifically, the first transmission scheme may be understood as a transmission scheme similar to a pre-arranged PUSCH resource transmission of a PUR transmission or a small data transmission (SDT), and may be understood as a pre-arranged PUSCH resource transmission scheme of a PUR transmission scheme or a SDT, depending on the case. The second transmission scheme may be understood as a transmission scheme similar to a RACH-based transmission of an early data transmission (EDT) or a small data transmission, and may be understood as an EDT transmission scheme or a RACH-based transmission scheme of a small data transmission, depending on the case. For example, the transmission according to the first transmission scheme may be PUR transmission, SDT pre-arranged PUSCH resource transmission, or transmission similar to PUR transmission or SDT pre-arranged PUSCH resource transmission, etc. The transmission according to the second transmission scheme may be EDT, transmission similar to EDT, RACH-based transmission of small data transmission, or transmission similar to RACH-based transmission of small data transmission, etc.

[0046] In the following, the sending of the target RRC message will be described in detail according to different implementation means.

[0047] In implementation 1, the UE completes the transmission of the target RRC message through a conventional random access process (e.g., NR 2-step / 4-step RACH).

[0048] 1. Preparation stage In the preparation phase, the UE triggers an RRC connection resume process, generates and submits an RRCResumeRequest / RRCResumeRequest1 message to lower layers, triggers the generation of the content of a target RRC message, and triggers the submission of the target RRC message to lower layers.

[0049] 1) In the RRCResume process, the UE may set a ResumeCause value, which is at least one of the following: (1) Multiplexing of the first ResumeCause value, e.g., mo-data, mo-signal, etc. (2) Use a second ResumeCause value that satisfies at least one of the following: → It is unrelated to the target RRC message, that is, all target RRC messages are unified, for example, in the case of MO-RRC message, the ResumeCause value is set to MO-RRC message. → Related to the target RRC message. For example, for "XX configuration request message", set the ResumeCause value to "XX configuration request message".

[0050] 2) In the RRCResume process, the UE may perform at least one of the following: (1) No UAC check is performed and the access attempt is allowed. (2) First, the Access category and / or Access identity(ies) are multiplexed to check the UAC, for example, Access category 7 and Access identity 0. (3) A second Access category and / or Access identity(ies) is used to check the UAC, and at least one of the following is satisfied: → It is unrelated to the target RRC message. That is, all target RRC messages are unified to the same value, for example, Access category is unified to 11, and Access identity is unified to 6. → Related to the target RRC message. For example, for an "XX configuration request message", set Access category to 11 and Access identity to 6.

[0051] 3) The time to trigger generation of the target RRC message corresponds to at least one of the following: (1) When the UE has a demand to transmit a target RRC message to a network side device, it immediately triggers the generation of the content of the target RRC message. (2) When the UE needs to send a target RRC message to a network side device, the UE first triggers an RRC connection resume process, and then triggers the generation of content of the target RRC message in the RRC connection resume process, which is at least one of the following: →The UE triggers the generation of the target RRC message content at the Initiation of the RRC connection resume process. Trigger the generation of the target RRC message content before SRB1 resumption in →"Action process for transmitting RRC Resume Request or RRC Resume Request 1 message". After SRB1 resumption in →"Action process for transmitting RRC Resume Request or RRC Resume Request 1 message", immediately trigger the generation of the target RRC message content. After the submission of the RRCResumeRequest / RRCResumeRequest1 message to lower layers in →"Action process for transmitting an RRC Resume Request or RRC Resume Request 1 message", it immediately triggers the generation of the target RRC message content.

[0052] 4) After the content of the target RRC message is generated, the UE may or may not store the content of the target RRC message in any format, such as a variable, an array and / or a structure.

[0053] 5) The time to trigger the submission of the target RRC message to the lower layer is at least one of the following: (1) Immediately trigger the submission of the target RRC message to lower layers after SRB1 resumption in the "Action Process for Transmission of an RRC Resumption Request or an RRC Resumption Request 1 Message". (2) Immediately trigger the submission of the target RRC message to lower layers after the submission of the RRCResumeRequest / RRCResumeRequest1 message to lower layers in the "Action Process for Transmission of an RRC Resume Request or RRC Resume Request 1 Message".

[0054] 2. Random Access (RACH) Phase In the RACH phase, the MAC layer of the UE initiates a random access process and submits one MAC PDU carrying both the RRCResumeRequest / RRCResumeRequest1 and the target RRC message to the lower layer, which then transmits it to the network side device.

[0055] 6) A random access trigger event corresponds to at least one of the following: (1) Multiplexing of the first trigger event, such as Transition from RRC_INACTIVE. (2) A second trigger event is used, which is at least one of the following: → It is independent of the target RRC message, i.e., all target RRC messages, e.g., MO-RRC message, are unified. →Related to a target RRC message. For example, the transmission of a single target RRC message such as an “XX configuration request message” is a trigger event.

[0056] 7) The allocation of all resources and parameters in the random access process, such as the preamble, PRACH resource, UL grant in the Random Access Response (RAR), MsgA Physical Uplink Shared Channel (PUSCH) resource, Synchronization Signal and PBCH block (SSB) resource, Physical Downlink Control Channel (PDCCH) search space, etc., falls under at least one of the following: (1) Allocate everything individually. For example, allocate all resources and parameters individually. (2) All configurations are multiplexed from the first configuration. For example, all configurations of resources and parameters are multiplexed from (i.e., shared with) the first configuration. (3) Some of the first arrangement will be multiplexed, and some will be arranged separately.

[0057] 8) Multiplexing a target RRC message and an RRCResumeRequest / RRCResumeRequest1 message into the same MAC PDU and transmitting the message to a network side device satisfies at least one of the following conditions: → The RCCresumeRequest / RRCResumeRequest1 message is before the target RRC message. In other words, the RCCresumeRequest / RRCResumeRequest1 message may be at the front in the MAC PDU and the target RRC message may be at the back in the MAC PDU. → The RCResumeRequest / RRCResumeRequest1 message is after the target RRC message. In other words, the target RRC message can be at the front in the MAC PDU and the RRCResumeRequest / RRCResumeRequest1 message can be at the back in the MAC PDU.

[0058] In implementation method 2, the UE completes the transmission of the target RRC message through a transmission in a first transmission manner (eg, a PUR transmission, a transmission similar to a PUR transmission, etc.).

[0059] 1. Preparation stage When the RRC layer of the UE needs to send an RRC message (target RRC message) that requires activated AS security, the RRC layer of the UE requests RRC connection resumption to initiate transmission using the first transmission method (e.g., PUR transmission), triggers the RRCResume process, generates and submits an RRCResumeRequest / RRCResumeRequest1 message to lower layers, triggers the generation of the content of the target RRC message, and triggers the submission of the target RRC message to lower layers.

[0060] 1) The start condition for transmission in the first transmission method may be any one of the following: → The UE requests RRC connection resumption in the RRC layer. The value of RRCResumeCause satisfies at least one of the following (1) or (2). (1) Multiplexing of the first ResumeCause value, e.g., mo-data, mo-signal, etc. (2) A second ResumeCause value is used, which corresponds to at least one of I and II below. I. It is unrelated to the target RRC message, that is, all the target RRC messages are unified, for example, for the MO-RRC message, the ResumeCause value is set to the MO-RRC message. II. Related to the target RRC message. For example, for the "XX configuration request message", set the ResumeCause value to "XX configuration request message". →The UE supports transmission using the first transmission method. →The network supports transmission according to the first transmission method, for example, the system message includes a corresponding instruction. →The UE has a valid first transmission scheme configuration. →The UE has a valid timing alignment value. →The UE has a stored nextHopChainingCount value, and this nextHopChainingCount value is the one provided by the suspendConfig in the latest (i.e., previous) RRCRelease message. → The size of the MAC PDU including the target RRC message is less than or equal to the TBS defined in the configuration of the first transmission method.

[0061] In one embodiment, taking the transmission according to the first transmission mode as an example, a PUR transmission is started under the condition that at least one of the following conditions is satisfied: →The UE requests RRC connection resumption in the RRC layer. →The UE supports the transmission of PUR. →The network supports the transmission of PUR. →The UE has a valid PUR configuration. →The UE has a valid timing alignment value. →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.

[0062] 2) In the RRCResume process, the UE can set a ResumeCause value, which is consistent with the value specifically selected above.

[0063] 3) In the RRCResume process, the UE may perform at least one of the following: (1) No UAC check is performed and the access attempt is allowed. (2) First, the Access category and / or Access identity(ies) are multiplexed to check the UAC, for example, Access category 7 and Access identity 0. (3) A second Access category and / or Access identity(ies) is used to check the UAC, and at least one of the following is satisfied: → It is unrelated to the target RRC message. That is, all target RRC messages are unified to the same value, for example, Access category is unified to 11, and Access identity is unified to 6. → Related to the target RRC message. For example, for an "XX configuration request message", set Access category to 11 and Access identity to 6.

[0064] 4) At this stage, the RRC layer may be triggered to instruct the lower layer to use the transmission according to the first transmission method, and to send an uplink grant corresponding to the transmission according to the first transmission method to the lower layer. The specific time point corresponds to at least one of the following: →When the conditions for starting transmission using the first transmission method are met, the RRC layer is immediately triggered to instruct the lower layer to use transmission using the first transmission method and to send an uplink grant corresponding to transmission using the first transmission method to the lower layer. →Before resuming SRB1 in the action process related to transmission of RRC Resume Request or RRCResumeRequest1 message, instruct the lower layer to use transmission via the first transmission method, and trigger the RRC layer to send an uplink grant corresponding to the transmission via the first transmission method to the lower layer. →After SRB1 resumption in the operation process for transmitting an RRC resumption request or an RRC resumption request 1 message, instruct the lower layer to use transmission via the first transmission method, and immediately trigger the RRC layer to send an uplink grant corresponding to transmission via the first transmission method to the lower layer. →In the operation process for transmitting an RRC Restart Request or an RRC Restart Request 1 message, after submitting the RRC Restart Request or the RRC Restart Request 1 message to the lower layer, instruct the lower layer to use transmission via the first transmission method, and immediately trigger the RRC layer to send an uplink grant corresponding to the transmission via the first transmission method to the lower layer.

[0065] In one embodiment, taking the transmission according to the first transmission mode as an example of PUR transmission, the UE may perform at least one of the following: →When the start condition for PUR transmission is met, instruct the lower layer to use PUR transmission, and immediately trigger the RRC layer to send an uplink grant corresponding to the PUR transmission to the lower layer. →Before SRB1 resumption in the operation process for transmitting an RRC Restart Request or RRC Restart Request 1 message, instruct the lower layer to use PUR transmission and trigger the RRC layer to send an uplink grant corresponding to the PUR transmission to the lower layer. →After SRB1 resumption in the operation process for transmitting an RRC Restart Request or RRC Restart Request 1 message, instruct the lower layer to use PUR transmission, and immediately trigger the RRC layer to send an uplink grant corresponding to the PUR transmission to the lower layer. →In the operation process for transmitting an RRC Resume Request or an RRC Resume Request 1 message, after submitting the RRC Resume Request or RRC Resume Request 1 message to the lower layer, instruct the lower layer to use PUR transmission and immediately trigger the RRC layer to send an uplink grant corresponding to the PUR transmission to the lower layer.

[0066] 5) The time to trigger generation of the target RRC message corresponds to at least one of the following: (1) When the UE RRC layer has a demand to send a target RRC message to a network side device, it immediately triggers the generation of the content of the target RRC message. (2) When the UE RRC layer has a need to send a target RRC message to a network side device, the UE first requests an RRC resumption to start transmission in a first transmission manner (such as PUR transmission), triggers an RRC connection resume process, and then triggers the generation of the content of the target RRC message in the RRC connection resume process, which at least corresponds to one of the following: →The UE triggers the generation of the target RRC message content at the Initiation of the RRC connection resume process. Trigger the generation of the target RRC message content before SRB1 resumption in →"Action process for transmitting RRC Resume Request or RRC Resume Request 1 message". After SRB1 resumption in →"Action process for transmitting RRC Resume Request or RRC Resume Request 1 message", immediately trigger the generation of the target RRC message content. After the submission of the RRCResumeRequest / RRCResumeRequest1 message to lower layers in →"Action process for transmitting an RRC Resume Request or RRC Resume Request 1 message", it immediately triggers the generation of the target RRC message content.

[0067] 6) After the content of the target RRC message is generated, the UE may or may not store the content of the target RRC message in any format, such as a variable, an array, and / or a structure.

[0068] 7) The time to trigger the submission of the target RRC message to the lower layer is at least one of the following: (1) Immediately trigger the submission of the target RRC message to lower layers after SRB1 resumption in the "Action Process for Transmission of an RRC Resumption Request or an RRC Resumption Request 1 Message". (2) Immediately trigger the submission of the target RRC message to lower layers after the submission of the RRCResumeRequest / RRCResumeRequest1 message to lower layers in the "Action Process for Transmission of an RRC Resume Request or RRC Resume Request 1 Message".

[0069] 2. Message sending stage At this stage, the MAC layer of the UE submits one MAC PDU carrying both the RRCResumeRequest / RRCResumeRequest1 and the target RRC message to the lower layer (eg, the physical layer), which then transmits it to the network side equipment.

[0070] Alternatively, multiplexing the target RRC message and the RRCResumeRequest / RRCResumeRequest1 message into the same MAC PDU and sending the same to the network side device corresponds to at least one of the following: → The RCResumeRequest / RRCResumeRequest1 message is before the target RRC message. In other words, the RRCResumeRequest / RRCResumeRequest1 message can be at the front in the MAC PDU and the target RRC message can be at the back in the MAC PDU. → The RCResumeRequest / RRCResumeRequest1 message is after the target RRC message. In other words, the target RRC message can be at the front in the MAC PDU and the RRCResumeRequest / RRCResumeRequest1 message can be at the back in the MAC PDU.

[0071] In implementation means 3, the UE completes the transmission of the target RRC message by transmitting in a second transmission manner (eg, SDT-like transmission, EDT-like transmission, etc.).

[0072] 1. Preparation stage When the RRC layer of the UE needs to send an RRC message (target RRC message) that requires activated AS security, the RRC layer of the UE requests RRC connection resumption to initiate transmission using a second transmission method (e.g., transmission similar to SDT, transmission similar to EDT, etc.), triggers the RRCResume process, generates and submits an RRCResumeRequest / RRCResumeRequest1 message to lower layers, triggers the generation of the content of the target RRC message, and triggers the submission of the target RRC message to lower layers.

[0073] 1) The start condition for transmission by the second transmission may be at least one of the following: → The UE requests RRC connection resumption in the RRC layer. The value of RRCResumeCause satisfies at least one of the following (1) or (2). (1) Multiplexing of the first ResumeCause value, e.g., mo-data, mo-signal, etc. (2) A second ResumeCause value is used, which corresponds to at least one of I and II below. I. It is unrelated to the target RRC message, that is, all the target RRC messages are unified, for example, for the MO-RRC message, the ResumeCause value is set to the MO-RRC message. II. Related to the target RRC message. For example, for the "XX configuration request message", set the ResumeCause value to "XX configuration request message". →The UE supports transmission using the second transmission method. →The network supports transmission via the second transmission method, for example, the system message includes a corresponding instruction. →The UE has a stored nextHopChainingCount value, and this nextHopChainingCount value is the one provided by the suspendConfig in the latest (i.e., previous) RRCRelease message. →All parameters related to transmission using the second transmission method are placed in the system information acquired by the UE. → The size of the MAC PDU including the target RRC message is less than or equal to the TBS defined in the configuration of the second transmission scheme.

[0074] In one embodiment, taking the transmission according to the second transmission mode as an example, the start condition of the EDT is at least one of the following: →The UE requests RRC connection resumption in the RRC layer. →UE supports EDT. → The network supports EDT, i.e. system messages contain corresponding instructions. →The UE has a stored nextHopChainingCount value, and this nextHopChainingCount value is the one provided by the suspendConfig in the latest (i.e., previous) RRCRelease message. →The system information acquired by the UE includes all parameters related to EDT, such as edt-parameter. → The size of the MAC PDU including the target RRC message is equal to or smaller than the TBS defined in the EDT configuration, such as edt-TBS.

[0075] 2) In the RRCResume process, the UE can set a ResumeCause value, which is consistent with the value specifically selected above.

[0076] 3) In the RRCResume process, the UE may perform at least one of the following: (1) No UAC check is performed and the access attempt is allowed. (2) First, the Access category and / or Access identity(ies) are multiplexed to check the UAC, for example, Access category 7 and Access identity 0. (3) A second Access category and / or Access identity(ies) is used to check the UAC, and at least one of the following is satisfied: → It is unrelated to the target RRC message. That is, all target RRC messages are unified to the same value, for example, Access category is unified to 11, and Access identity is unified to 6. → Related to the target RRC message. For example, for an "XX configuration request message", set Access category to 11 and Access identity to 6.

[0077] 4) At this stage, the UE RRC layer may be triggered to configure lower layers to use the second transmission method for transmission, the specific time point being at least one of the following: →When the conditions for starting transmission via the second transmission method are met, immediately trigger the RRC layer to configure the lower layers to use transmission via the second transmission method. →Trigger the RRC layer to configure the lower layers to use transmission via the second transmission method before SRB1 resumption in the operation process for transmission of the RRC Restart Request or RRC Restart Request 1 message. →After SRB1 resumption in the operation process for transmitting an RRC Restart Request or RRC Restart Request 1 message, immediately trigger the RRC layer to configure the lower layers to use transmission via the second transmission method. →In the operation process for transmitting an RRC Restart Request or an RRC Restart Request 1 message, after submitting the RRC Restart Request or the RRC Restart Request 1 message to the lower layer, immediately trigger the RRC layer to configure the lower layer to use transmission via the second transmission method.

[0078] In one embodiment, for example, the transmission according to the second transmission mode is EDT transmission, the UE may perform at least one of the following: →When the EDT start condition is met, it immediately triggers the RRC layer to configure the lower layers to use EDT. →Trigger the RRC layer to configure the lower layers to use EDT before SRB1 resumption in the operation process related to the transmission of the RRC Restart Request or RRC Restart Request 1 message. →After SRB1 resumes in the action process for transmitting an RRC resume request or RRC resume request 1 message, immediately trigger the RRC layer to configure the lower layers to use EDT. → In the operation process for transmitting the RRC Resume Request or RRC Resume Request 1 message, after submission of the RRC Resume Request or RRC Resume Request 1 message to the lower layers, immediately trigger the RRC layer to configure the lower layers to use EDT.

[0079] 5) The time to trigger generation of the target RRC message corresponds to at least one of the following: (1) When the UE RRC layer has a demand to send a target RRC message to a network side device, it immediately triggers the generation of the content of the target RRC message. (2) When the UE RRC layer has a need to send a target RRC message to a network side device, the UE first requests an RRC resumption to start transmission according to a second transmission mode (for example, SDT-like transmission, EDT-like transmission, etc.), triggers an RRC connection resume process, and then triggers the generation of the target RRC message content in the RRC connection resume process, which is at least one of the following: →The UE triggers the generation of the target RRC message content at the Initiation of the RRC connection resume process. Trigger the generation of the target RRC message content before SRB1 resumption in →"Action process for transmitting RRC Resume Request or RRC Resume Request 1 message". After SRB1 resumption in →"Action process for transmitting RRC Resume Request or RRC Resume Request 1 message", immediately trigger the generation of the target RRC message content. After the submission of the RRCResumeRequest / RRCResumeRequest1 message to lower layers in →"Action process for transmitting an RRC Resume Request or an RRC Resume Request 1 message", it immediately triggers the generation of the target RRC message content.

[0080] 6) After the content of the target RRC message is generated, the UE may or may not store the content of the target RRC message in any format, such as a variable, an array, and / or a structure.

[0081] 7) The time to trigger the submission of the target RRC message to the lower layer is at least one of the following: (1) Immediately trigger the submission of the target RRC message to lower layers after SRB1 resumption in the "Action Process for Transmission of an RRC Resumption Request or an RRC Resumption Request 1 Message". (2) Immediately trigger the submission of the target RRC message to lower layers after the submission of the RRCResumeRequest / RRCResumeRequest1 message to lower layers in the "Action Process for Transmission of an RRC Resume Request or RRC Resume Request 1 Message".

[0082] 2. Message sending stage At this stage, the MAC layer of the UE submits one MAC PDU carrying both the RRCResumeRequest / RRCResumeRequest1 and the target RRC message to the lower layer (eg, physical layer), which then transmits it to the network side equipment.

[0083] Alternatively, multiplexing the target RRC message and the RRCResumeRequest / RRCResumeRequest1 message into the same MAC PDU and sending the same to the network side device corresponds to at least one of the following: → The RCResumeRequest / RRCResumeRequest1 message is before the target RRC message. In other words, the RRCResumeRequest / RRCResumeRequest1 message can be at the front in the MAC PDU and the target RRC message can be at the back in the MAC PDU. → The RCResumeRequest / RRCResumeRequest1 message is after the target RRC message. In other words, the target RRC message can be at the front in the MAC PDU and the RRCResumeRequest / RRCResumeRequest1 message can be at the back in the MAC PDU.

[0084] The present invention will now be described in more detail with reference to specific examples. Example 1

[0085] In this embodiment 1, the target RRC message is an MBSCountingResponse message, and the target RRC message is sent through a random access process.

[0086] As shown in FIG. 3, the corresponding target RRC message sending process may include the following steps:

[0087] Step 30 is a preparation step.

[0088] After the RRC layer of the UE receives the MBSCountingRequest message, if the UE is receiving or interested in receiving the MBS service indicated in the MBSCountingRequest message, the UE needs to send an MBSCountingResponse message to the network side device. The UE triggers the RRCResume process, generates and submits an RRCResumeRequest / RRCResumeRequest1 message to the lower layer, and generates and submits an MBSCountingResponse message to the lower layer.

[0089] →For UAC-related settings, set Access category to 11 and Access identity to 0, run UAC, and if the UAC check is passed, the access attempt will be allowed.

[0090] →To set the ResumeCause value, set RRCResumeCause in the MO-RRC message.

[0091] Regarding the generation of an RRCResumeRequest / RRCResumeRequest1 message and submission to a lower layer, for example, the RRC layer of the UE generates an RRCResumeRequest / RRCResumeRequest1 message whose ResumeCause value is MO-RRCmessage and submits it to a lower layer.

[0092] Regarding the generation of an MBSCountingResponse message and its submission to a lower layer, for example, after an RRCResumeRequest / RRCResumeRequest1 is submitted to a lower layer, the generation of an MBSCountingResponse message and its submission to a lower layer is immediately triggered.

[0093] In step 31, the MAC layer of the UE initiates the random access process and sends Msg1, ie a random access amble, to the base station gNB.

[0094] In step 32, the gNB returns Msg2, i.e., a random access response (RAR), to the UE.

[0095] In step 33, the MAC layer of the UE sends one MAC PDU containing both the RRCResumeRequest / RRCResumeRequest1 message and the MBSCountingResponse message to the gNB via Msg3.

[0096] In step 34, the gNB returns Msg4 to the UE, which includes the RRCRelease message. Example 2

[0097] In this embodiment 2, the target RRC message is a PURConfigurationRequest message, and the target RRC message is sent by a PUR transmission.

[0098] As shown in FIG. 4, the corresponding target RRC message sending process may include the following steps:

[0099] Step 40 is a preparation step.

[0100] The UE has a valid PUR resource. After the UE is no longer interested in PUR configuration, the UE needs to send a PURConfigurationRequest message to the network side device. The RRC layer of the UE requests RRC resumption to start the transmission of PUR, triggers the RRCResume process, generates and submits an RRCResumeRequest / RRCResumeRequest1 message to the lower layer, and generates and submits a PURConfigurationRequest message to the lower layer.

[0101] → The related settings for UAC are the same as those for MO-data, i.e., set Access category to 7 and Access identity to 0, run UAC, and if the UAC check is passed, the access attempt will be allowed.

[0102] →The setting of the ResumeCause value is the same as for MO-data, and the RRCResumeCause value is set in MO-data.

[0103] Regarding the generation of an RRCResumeRequest / RRCResumeRequest1 message and submission to a lower layer, for example, the RRC layer of the UE generates an RRCResumeRequest / RRCResumeRequest1 message whose ResumeCause value is MO-data and submits it to a lower layer.

[0104] Regarding the generation and submission of a PURConfigurationRequest message to a lower layer, for example, after RRCResumeRequest / RRCResumeRequest1 is submitted to a lower layer, the generation and submission of a PURConfigurationRequest message to a lower layer is immediately triggered.

[0105] In step 41, the UE sends a RRCResumeRequest / RRCResumeRequest1 message and a PURConfigurationRequest message to the gNB.

[0106] Alternatively, the MAC layer of the UE performs a PUR transmission and submits one MAC PDU including both the RRCResumeRequest / RRCResumeRequest1 message and the PURConfigurationRequest message to the physical layer to send to the gNB.

[0107] In step 42, the gNB sends a RRCRelease message to the UE. Example 3

[0108] In this embodiment 3, the target RRC message is an MBSCountingResponse message, and the target RRC message is sent through the EDT.

[0109] As shown in FIG. 5, the corresponding target RRC message sending process may include the following steps:

[0110] Step 50 is a preparation step.

[0111] After the UE RRC layer receives the MBSCountingRequest message, if the UE is receiving or interested in receiving the MBS service indicated in the MBSCountingRequest message, the UE needs to send an MBSCountingResponse message to the network side device. The UE RRC layer requests RRC resumption to start EDT, triggers the RRCResume process, generates and submits an RRCResumeRequest / RRCResumeRequest1 message to the lower layer, and generates and submits a PURConfigurationRequest message to the lower layer.

[0112] →For UAC-related settings, set Access category to 11 and Access identity to 0, run UAC, and if the UAC check is passed, the access attempt will be allowed.

[0113] →To set the ResumeCause value, set RRCResumeCause in the MO-RRC message.

[0114] Regarding the generation of an RRCResumeRequest / RRCResumeRequest1 message and submission to a lower layer, for example, the RRC layer of the UE generates an RRCResumeRequest / RRCResumeRequest1 message whose ResumeCause value is MO-RRCmessage and submits it to a lower layer.

[0115] Regarding the generation of an MBSCountingResponse message and its submission to a lower layer, for example, after an RRCResumeRequest / RRCResumeRequest1 is submitted to a lower layer, the generation of an MBSCountingResponse message and its submission to a lower layer is immediately triggered.

[0116] In step 51, the UE sends an RRCResumeRequest / RRCResumeRequest1 message and an MBSCountingResponse message to the gNB.

[0117] Alternatively, the MAC layer of the UE performs EDT and submits one MAC PDU containing both the RRCResumeRequest / RRCResumeRequest1 message and the MBSCountingResponse message to the physical layer to send to the gNB.

[0118] In step 52, the gNB sends a RRCRelease message to the UE.

[0119] It should be noted that the execution entity of the message sending method provided in the embodiment of the present application may be a message sending device, or may be a control module for executing the message sending method in the message sending device. In the embodiment of the present application, the message sending device provided in the embodiment of the present application will be described by taking the message sending device executing the message sending method as an example.

[0120] Please refer to Fig. 6, which is a structural schematic diagram of a message sending device provided in an embodiment of the present invention, and the device is applied to a terminal. As shown in Fig. 6, the message sending device 60 includes: a first sending module 61, for sending a 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, and the target RRC message is an RRC message that requires activated access stratum security.

[0121] Optionally, the message sending device 60 further includes a first execution module for performing the steps of triggering an RRC connection resumption process, generating an RRC resumption request or an RRC resumption request 1 message, and submitting the RRC resumption request or the RRC resumption request 1 message to a lower layer, and triggering the generation of content of the target RRC message, and triggering the submission of the target RRC message to a lower layer.

[0122] Optionally, the message sending device 60 further includes a setting module for setting a ResumeCause value, wherein the ResumeCause value is at least one of a multiplexing of a first ResumeCause value and a second ResumeCause value, wherein the second ResumeCause value is unrelated to the target RRC message or the second ResumeCause value is related to the target RRC message.

[0123] Optionally, the message sending device 60 further comprises a second execution module for performing at least one of the steps of deciding not to check the unified access control UAC, checking the UAC using an existing access category first access category and / or access identifier, and checking the UAC using a second access category and / or access identifier, wherein the second access category and / or access identifier is unrelated to the target RRC message or the second access category and / or access identifier is related to the target RRC message.

[0124] Optionally, the first execution module is specifically used for performing at least one of the following steps: immediately triggering the generation of content of the target RRC message when the terminal needs to send a target RRC message to a network side device; and triggering the generation of content of the target RRC message in the RRC connection resumption process.

[0125] Optionally, the first execution module is specifically used for performing at least one of the following steps: triggering generation of content of the target RRC message at a starting phase of the RRC connection resumption process; triggering generation of content of the target RRC message before resumption of signaling radio bearer SRB1 in an operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message; immediately triggering generation of content of the target RRC message after resumption of SRB1 in an operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message; and immediately triggering generation of content of the target RRC message after submission of the RRC Restart Request or RRC Restart Request 1 message to a lower layer in an operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message.

[0126] Optionally, the first execution module is specifically used for performing at least one of the following steps: immediately triggering the submission of the target RRC message to a lower layer after SRB1 resumption in an operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message; and immediately triggering the submission of the target RRC message to a lower layer after the submission of the RRC Restart Request or RRC Restart Request 1 message to a lower layer in an operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message.

[0127] Optionally, the message sending device 60 further includes a storage module for storing the content in the target RRC message in a first format after the content in the target RRC message is generated, or for not storing the content in the target RRC message.

[0128] Optionally, the first format includes at least one of a variable, an array, and a structure.

[0129] Optionally, the first sending module 61 is specifically used for multiplexing the target RRC message and the RRC Resume Request or RRC Resume Request 1 message into the same MAC PDU and sending it to a network side device.

[0130] Optionally, the MAC PDU configuration is at least one of: the RRC Restart Request or RRC Restart Request 1 message is before the Target RRC message; and the RRC Restart Request or RRC Restart Request 1 message is after the Target RRC message.

[0131] Optionally, the first execution module is further used to initiate a random access process in a MAC layer.

[0132] Optionally, the trigger event of the random access process is at least one of a multiplexing of a first trigger event and a second trigger event, where the second trigger event is unrelated to the target RRC message or the second trigger event is related to the target RRC message.

[0133] Optionally, the configuration of resources and parameters in the random access process is at least one of: all configured separately; all multiplexed from the first configuration; some multiplexed from the first configuration and some configured separately.

[0134] Optionally, the first execution module is further used for requesting an RRC connection resumption in an RRC layer, initiating transmission in the first transmission scheme, and performing transmission in the first transmission scheme in a MAC layer.

[0135] Optionally, the start condition for transmission via the first transmission scheme is at least one of: an RRC layer requests RRC connection resumption; the terminal supports transmission via the first transmission scheme; a network supports transmission via the first transmission scheme; the terminal has a valid configuration of the first transmission scheme; the terminal has a valid timing adjustment value; the terminal has a stored nextHopChainingCount value, and the nextHopChainingCount value is provided by suspendConfig in a latest RRC release message; and a size of a MAC PDU including the target RRC message is less than or equal to a transport block size TBS defined in the configuration of the first transmission scheme.

[0136] Optionally, the first execution module is further used to instruct a lower layer to use transmission in a first transmission method and trigger an RRC layer to send an uplink grant corresponding to the transmission in the first transmission method to the lower layer.

[0137] Optionally, the first execution module specifically includes the steps of: when a start condition for transmission by a first transmission method is met, instructing a lower layer to use transmission by a first transmission method and immediately triggering an RRC layer to send an uplink grant corresponding to the transmission by the first transmission method to a lower layer; before SRB1 resumption in an operation process related to the transmission of the RRC resume request or RRC resume request 1 message, instructing a lower layer to use transmission by the first transmission method and triggering an RRC layer to send an uplink grant corresponding to the transmission by the first transmission method to a lower layer; and triggering an RRC layer to send an uplink grant corresponding to the transmission by the first transmission method to a lower layer before SRB1 resumption in an operation process related to the transmission of the RRC resume request or RRC resume request 1 message. and after submission of the RRC Restart Request or RRC Restart Request 1 message to a lower layer in an operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message, instructing a lower layer to use transmission by the first transmission scheme and immediately triggering the RRC layer to send an uplink grant corresponding to the transmission by the first transmission scheme to the lower layer.

[0138] Optionally, the first execution module is further used for requesting an RRC connection resumption in an RRC layer, initiating transmission in a second transmission scheme, and performing transmission in the second transmission scheme in a MAC layer.

[0139] Optionally, the start condition for transmission via the second transmission scheme is at least one of: requesting RRC connection resumption in an RRC layer; the terminal supporting transmission via the second transmission scheme; the network supporting transmission via the second transmission scheme; the terminal having a stored nextHopChainingCount value, and the nextHopChainingCount value is provided by suspendConfig in a latest RRC Release message; all parameters related to transmission via the second transmission scheme are configured in system information acquired by the terminal; and a size of a MAC PDU including the target RRC message is less than or equal to a transport block size TBS defined in the configuration of transmission via the second transmission scheme.

[0140] Optionally, the first execution module is further used to trigger the RRC layer to configure the lower layers to use transmission via the second transmission scheme, and the triggering is at least one of the following steps when a start condition for transmission via the second transmission scheme is met: immediately triggering the RRC layer to configure the lower layers to use transmission via the second transmission scheme; before SRB1 resumption in the operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message, immediately triggering the RRC layer to configure the lower layers to use transmission via the second transmission scheme; after SRB1 resumption in the operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message, immediately triggering the RRC layer to configure the lower layers to use transmission via the second transmission scheme; and after submission of the RRC Restart Request or RRC Restart Request 1 message to the lower layers in the operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message, immediately triggering the RRC layer to configure the lower layers to use transmission via the second transmission scheme.

[0141] Alternatively, when the target RRC message is an RRC message regarding the configuration of a first transmission scheme, there is a demand for the terminal to transmit the target RRC message to a network side device if at least one of the following is satisfied: the terminal supports transmission via the first transmission scheme; the network supports transmission via the first transmission scheme; the size of a MAC PDU including the target RRC message is equal to or smaller than a maximum transport block size TBS supported by the terminal defined based on the type of the terminal; the terminal is interested in the configuration of the first transmission scheme; the terminal is no longer interested in the configuration of the first transmission scheme; and the configuration of the first transmission scheme needs to be updated.

[0142] Optionally, when the target RRC message is an RRC message related to a multicast broadcast service MBS count, the terminal needs to transmit the target RRC message to a network side device if at least one of the following is satisfied: the terminal has MBS capability; the network supports MBS; the size of the MAC PDU including the target RRC message is less than or equal to the maximum TBS supported by the terminal defined based on the type of the terminal; the RRC layer of the terminal has received a control message related to an MBS count transmitted from a network side device; and the terminal is receiving or is interested in receiving at least one MBS service indicated in the control message related to an MBS count.

[0143] Alternatively, when the target RRC message is an RRC message related to an MBS interest indication, the terminal needs to transmit the target RRC message to a network side device if at least one of the following is satisfied: the terminal has MBS capability; the network supports MBS; the size of the MAC PDU including the target RRC message is less than or equal to the maximum TBS supported by the terminal defined based on the type of the terminal; the terminal receives control information related to an MBS service transmitted from a network side device; the terminal enters or leaves a service area; an MBS session is started or stopped; the content of an MBS interest indication message has changed; and the cell or base station transmitting the control information related to the MBS service has changed.

[0144] The message sending device in the embodiment of the present application may be a device, or may be a component, integrated circuit, or chip in a terminal. The device may be a mobile terminal or a non-mobile terminal. Exemplarily, 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 (PC), a television (TV), an automated teller machine or a kiosk terminal, etc., and is not specifically limited in the embodiment of the present application.

[0145] The message sending device in the embodiment of the present application may be a device having an operating system, which may be the Android operating system, the ios operating system, or other possible operating systems, and is not specifically limited in the embodiment of the present invention.

[0146] The message sending device 60 provided in the embodiment of the present application can realize each process realized in the method embodiment shown in Figure 2, and can achieve the same technical effect. In order to avoid duplication, detailed description will be omitted here.

[0147] Please refer to FIG. 7, which is a flowchart of a message receiving method provided in an embodiment of the present invention. The method is applied to a network side device, and as shown in FIG. 7, the method includes the following steps:

[0148] In step 701, a target RRC message is received from a terminal.

[0149] The target RRC message is an RRC message that requires activated access stratum security, and the target RRC message was sent in a non-RRC connected state when the terminal is in a non-RRC connected state and there is a need to send the target RRC message.

[0150] In this embodiment, the terminal can receive the target RRC message directly sent by the terminal in a non-RRC connected state without waiting until other conditions for triggering the establishment or resumption of the RRC connection are met and the RRC connection is successfully established or resumed, thereby reducing delays, and also avoiding resource waste, energy consumption, etc.

[0151] Optionally, the process of receiving a target RRC message from the terminal may include receiving the target RRC message from the terminal by a MAC PDU, in which the target RRC message and an RRC Resume Request or an RRC Resume Request 1 message are multiplexed.

[0152] Optionally, when the target RRC message is an RRC message regarding the configuration of transmission via a first transmission method, the method further includes a step of sending indication information to the terminal indicating that the network supports transmission via the first transmission method.

[0153] Optionally, when the target RRC message is an RRC message related to an MBS count, the method further includes at least one of the steps of sending indication information to the terminal indicating that the network supports MBS, and sending a control message related to an MBS count to the terminal.

[0154] Optionally, when the target RRC message is an RRC message related to an MBS interest indication, the method further includes at least one of the following: The network sends indication information to the terminal indicating that the network supports MBS, for example, the indication information can be sent through system information. Send control information related to the MBS service to the terminal, for example, the control information may be sent via a system message or dedicated RRC signaling.

[0155] It should be noted that the execution subject of the message receiving method provided in the embodiment of the present application may be a message receiving device, or may be a control module for executing the message receiving method in the message receiving device. In the embodiment of the present application, the message receiving device provided in the embodiment of the present application will be described by taking the message receiving device executing the message receiving method as an example.

[0156] Please refer to Fig. 8, which is a structural schematic diagram of a message receiving device provided in an embodiment of the present invention. The device is applied to a network side device. As shown in Fig. 8, the message receiving device 80 includes: a receiving module 81 for receiving a target RRC message from a terminal, the target RRC message is an RRC message that requires activated access stratum security, and the target RRC message is sent in a non-RRC connected state when the terminal is in a non-RRC connected state and there is a need to send the target RRC message.

[0157] Optionally, the receiving module 81 is further used for receiving the target RRC message from the terminal by MAC PDU, in which the target RRC message and an RRC Resume Request or an RRC Resume Request 1 message are multiplexed.

[0158] Optionally, the message receiving device 80 further includes a second sending module, which is used to send, when the target RRC message is an RRC message related to the configuration of transmission according to the first transmission method, indication information indicating that the network supports transmission according to the first transmission method to the terminal, or to send, when the target RRC message is an RRC message related to an MBS count, indication information indicating that the network supports MBS to the terminal and / or to send, when the target RRC message is an RRC message related to an MBS interest indication, indication information indicating that the network supports MBS to the terminal and / or to send, when the target RRC message is an RRC message related to an MBS interest indication, indication information indicating that the network supports MBS to the terminal and / or to send, when the target RRC message is an RRC message related to an MBS interest indication, control information related to an MBS service to the terminal.

[0159] The message receiving device 80 provided in the embodiment of the present application can implement each process implemented in the method embodiment shown in Figure 7, and achieve the same technical effects. To avoid duplication, detailed descriptions will be omitted here.

[0160] Optionally, as shown in Fig. 9, the embodiment of the present application further provides a communication device 90. The communication device 90 includes a processor 91, a memory 92, and a program or command stored in the memory 92 and executable on the processor 91. For example, when the communication device is a terminal, the process of the embodiment of the message sending method is realized when the program or command is executed by the processor 91, and the same technical effect can be achieved. When the communication device is a network side device, the process of the embodiment of the message receiving method is realized when the program or command is executed by the processor 91, and the same technical effect can be achieved. To avoid duplication, detailed description is omitted here.

[0161] FIG. 10 is a schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0162] The terminal 100 includes components such as, but 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, and a processor 110.

[0163] Those skilled in the art can understand that the terminal 100 may further include a power source (e.g., a battery) for supplying power to each component, and the power source may be logically connected to the processor 110 by a power management system, and the power management system may further realize functions such as charge / discharge management and power consumption management. The terminal structure shown in FIG. 10 does not limit the terminal, and the terminal may include more or fewer components than those shown, or a combination of some components, or a different component configuration, and detailed description thereof will be omitted here.

[0164] It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processing unit (GPU) 1041 for processing image data of still or video captured by an image capture device (e.g., a camera) in a video capture mode or an image capture mode, and a microphone 1042. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. 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 and may include two parts: a touch detection device and a touch controller. The other input devices 1072 may include, but are not limited to, a physical keyboard, a function button (e.g., a volume control button, a switch button, etc.), a trackball, a mouse, and an operation lever, and detailed description thereof will be omitted here.

[0165] In the embodiment of the present application, the high frequency unit 101 receives downlink data from the network side device, processes the data in the processor 110, and transmits uplink data to the network side device. Typically, the high frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a receiver-transmitter, a coupler, a low-noise amplifier, a duplexer, etc.

[0166] The memory 109 can be used to store software programs or commands and various data. The memory 109 may mainly include a program or command storage area capable of storing an operating system, an application program or command required for at least one function (e.g., a sound playback function, an image playback function, etc.), and a data storage area. The memory 109 may also include a high-speed random access memory, and may further include a non-volatile memory, which may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage device.

[0167] The processor 110 may include one or more processing units, and may optionally integrate an application processor, such as an operating system, a user interface, and applications and commands, and a modem processor, such as a baseband processor, that mainly handles wireless communications, in the processor 110. It is understood that the modem processor may not be integrated into the processor 110.

[0168] The radio frequency unit 101 is used to transmit a target RRC message in a non-RRC connected state when the terminal 100 is in a non-RRC connected state and there is a need to transmit the target RRC message to a network side device, the target RRC message being an RRC message that requires activated access stratum security.

[0169] The terminal 100 provided in the embodiment of the present application can implement each process implemented in the method embodiment shown in Figure 2, and achieve the same technical effect. To avoid duplication, detailed description will be omitted here.

[0170] Specifically, the embodiment of the present application further provides a network side device. As shown in Fig. 11, 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. In the uplink direction, the radio frequency device 112 receives information through the antenna 111 and transmits the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and transmits it to the radio frequency device 112, and the radio frequency device 112 processes the received information and transmits it through the antenna 111.

[0171] The above-mentioned bandwidth processing device may be located in a baseband device 113 , and the methods performed by the network side equipment in the above-mentioned embodiments may be implemented in the baseband device 113 , which comprises a processor 114 and a memory 115 .

[0172] The baseband device 113 may, for example, include at least one baseband board on which multiple chips are installed, and as shown in FIG. 11, one of the chips is, for example, a processor 114 connected to a memory 115 and calling up a program in the memory 115 to execute the operations of the network side equipment shown in the above method embodiments.

[0173] The baseband device 113 may further comprise a network interface 116 for interacting with the radio frequency device 112, the interface being, for example, a common public radio interface (CPRI).

[0174] Specifically, the network side device of the embodiment of the present invention further includes a command or program stored in memory 115 and executable on processor 114, and processor 114 can call the command or program in memory 115 to execute the method executed by each module shown in Fig. 8 to achieve the same technical effect. To avoid duplication, detailed description will be omitted here.

[0175] The embodiment of the present application further provides a readable storage medium, which stores a program or command, and when the program or command is executed by a processor, each process of the embodiment of the message sending method is realized, or each process of the embodiment of the message receiving method is realized, so as to achieve the same technical effect. In order to avoid repetition, detailed description is omitted here.

[0176] The readable storage medium includes a computer readable storage medium such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0177] The embodiment of the present application further provides a chip, which includes a processor and a communication interface, and the communication interface and the processor are coupled together, and the processor executes a program or command to realize each process of the embodiment of the message sending method or to realize each process of the embodiment of the message receiving method, so as to achieve the same technical effect. In order to avoid duplication, detailed description is omitted here.

[0178] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, system on chips, or the like.

[0179] It should be noted that in this specification, the terms "comprise", "consist of" or any other variations are intended to include a non-exclusive inclusion, whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly stated or inherent to such process, method, article, or apparatus. Unless otherwise specified, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. It should also be noted that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions substantially simultaneously or in the reverse order depending on such functions, for example, the described method may be performed in a different order than described, and various steps may be added, omitted, or combined. Also, features described with reference to any example may be combined in other examples.

[0180] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be realized in the form of a combination of software and a necessary common hardware platform, and of course, they can be realized by hardware, but in many cases the former is a more preferred embodiment. Based on this view, the technical solution of the present application can be substantially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes a number of commands that cause a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0181] Although the examples of the present application have been described above with reference to the drawings, the present application is not limited to the above-mentioned specific embodiments, which are merely illustrative and not limiting. Based on the suggestions of the present application, many forms that a person skilled in the art can make without departing from the spirit of the present application and the scope of protection of the claims are all within the scope of protection of the present application.

Claims

1. A message transmission method applied to a terminal, comprising: When the terminal is in a non-radio resource control (RRC) connected state and there is a need to transmit a target RRC message to a network side device, transmitting the target RRC message in a non-RRC connected state; the target RRC message is an RRC message that requires activated access stratum security; before transmitting the target RRC message, triggering an RRC connection resumption process, generating an RRC resumption request or an RRC resumption request 1 message, and submitting the RRC resumption request or the RRC resumption request 1 message to a lower layer; triggering generation of content of the target RRC message and triggering submission of the target RRC message to a lower layer; Triggering the generation of content of the target RRC message comprises: when the terminal needs to send a target RRC message to a network side device, immediately triggering the generation of the content of the target RRC message; triggering generation of content of the target RRC message in the RRC connection resumption process.

2. In the RRC connection resumption process, The method further includes the step of setting a resume cause ResumeCause value; The ResumeCause value is multiplexing the first ResumeCause value; and a second ResumeCause value; and The second ResumeCause value is unrelated to the target RRC message, or the second ResumeCause value is related to the target RRC message; In the RRC connection resumption process, determining not to perform a unified access control (UAC) check; checking the UAC using an existing access category, a first access category, and / or an access identifier; and checking the UAC using a second access category and / or access identifier; The method of claim 1 , wherein the second access category and / or access identifier is unrelated to the target RRC message, or the second access category and / or access identifier is related to the target RRC message.

3. The step of triggering generation of content of the target RRC message in the RRC connection resumption process includes: triggering the generation of the target RRC message content at the start of the RRC connection resumption process; triggering generation of the target RRC message content before resumption of the signaling radio bearer SRB1 in the operation process for transmission of the RRC Restart Request or RRC Restart Request 1 message; immediately triggering the generation of the target RRC message content after SRB1 resumption in the operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message; and immediately triggering generation of content of the target RRC message after submission of the RRC Restart Request or RRC Restart Request 1 message to a lower layer in an operational process for transmission of the RRC Restart Request or RRC Restart Request 1 message.

4. storing the content in the target RRC message in a first format after the content in the target RRC message is generated, or not storing the content in the target RRC message. Further comprising: The method of claim 1 , wherein the first format comprises at least one of a variable, an array, and a structure.

5. Prior to the step of transmitting the target RRC message The method further includes the step of initiating a random access process at a MAC layer; The trigger event of the random access process is: multiplexing the first trigger event; a second trigger event; The second triggering event is unrelated to the target RRC message, or the second triggering event is related to the target RRC message; The resource and parameter configuration in the random access process includes: All placed separately, multiplexing all first configurations; 2. The method of claim 1, further comprising at least one of: a) multiplexing the first arrangement; and b) individually configuring the first arrangement.

6. before transmitting the target RRC message, requesting an RRC connection resumption in an RRC layer and starting transmission in a first transmission method; The method of claim 1 , further comprising: performing transmission according to the first transmission scheme at a MAC layer.

7. The method further includes the step of instructing a lower layer to use a transmission in a first transmission method and triggering an RRC layer to transmit an uplink grant corresponding to the transmission in the first transmission method to the lower layer; The step of instructing a lower layer to use transmission in a first transmission scheme and triggering an RRC layer to transmit an uplink grant corresponding to the transmission in the first transmission scheme to the lower layer, when a start condition for transmission by a first transmission method is satisfied, immediately triggering an RRC layer to instruct a lower layer to use the transmission by the first transmission method and to send an uplink grant corresponding to the transmission by the first transmission method to a lower layer; triggering an RRC layer to instruct a lower layer to use transmission in a first transmission scheme before resuming an SRB1 in an operation process related to the transmission of the RRC restart request or RRC restart request 1 message, and to send an uplink grant corresponding to the transmission in the first transmission scheme to the lower layer; immediately triggering the RRC layer to instruct a lower layer to use transmission in a first transmission scheme after SRB1 resumption in the operation process for transmitting the RRC resumption request or RRC resumption request 1 message, and to send an uplink grant corresponding to the transmission in the first transmission scheme to the lower layer; and immediately triggering the RRC layer to instruct the lower layer to use transmission in a first transmission scheme and to send an uplink grant corresponding to the transmission in the first transmission scheme to the lower layer after submitting the RRC Restart Request or RRC Restart Request 1 message to the lower layer in an operation process for transmitting the RRC Restart Request or RRC Restart Request 1 message.

8. before transmitting the target RRC message, requesting an RRC connection resumption in an RRC layer and starting transmission in a second transmission mode; The method of claim 1 , further comprising: performing transmission in the second transmission scheme at a MAC layer.

9. Triggering an RRC layer to configure a lower layer to use transmission in a second transmission scheme, the step including: immediately triggering the RRC layer to configure lower layers to use transmission in the second transmission method when a condition for starting transmission in the second transmission method is met; triggering an RRC layer to configure lower layers to use transmission according to a second transmission scheme before resuming SRB1 in the operation process related to the transmission of the RRC Restart Request or RRC Restart Request 1 message; immediately triggering the RRC layer to configure lower layers to use transmission according to a second transmission scheme after SRB1 resumption in the operation process related to the transmission of the RRC Restart Request or RRC Restart Request 1 message; and immediately triggering the RRC layer after submission of the RRC Restart Request or RRC Restart Request 1 message to the lower layers in an operation process for transmission of the RRC Restart Request or RRC Restart Request 1 message to configure the lower layers to use transmission with a second transmission scheme.

10. When the target RRC message is an RRC message related to the configuration of a first transmission scheme, The terminal supports transmission in a first transmission mode; the network supporting transmission in the first transmission scheme; The size of the MAC PDU including the target RRC message is less than or equal to a maximum transport block size (TBS) supported by the terminal, which is defined based on the terminal type; The terminal satisfies at least one of the following: the terminal is interested in the configuration of the first transmission scheme; the terminal is no longer interested in the configuration of the first transmission scheme; and the terminal needs to update the configuration of the first transmission scheme; If at least one of the following conditions is met, the terminal needs to send a target RRC message to the network side equipment; or When the target RRC message is an RRC message related to a Multicast Broadcast Service (MBS) count, The terminal has MBS capability; and The network supports MBS; The size of the MAC PDU including the target RRC message is equal to or smaller than the maximum TBS supported by the terminal, which is defined based on the terminal type; and The RRC layer of the terminal receives a control message regarding MBS count sent from a network side device; the terminal is receiving or is interested in receiving at least one MBS service indicated in the control message relating to MBS counting; If at least one of the following conditions is met, the terminal needs to send a target RRC message to the network side equipment; or When the target RRC message is an RRC message related to an MBS interest indication, The terminal has MBS capability; and The network supports MBS; The size of the MAC PDU including the target RRC message is equal to or smaller than the maximum TBS supported by the terminal, which is defined based on the terminal type; and The terminal receives control information related to the MBS service transmitted from a network side device; and the terminal has entered or left a service area; and That an MBS session has started or stopped; The content of the MBS Interest Indication message has been changed; and A cell or base station that transmits control information related to the MBS service has been changed; and The method according to claim 1 , wherein the terminal needs to send a target RRC message to a network side equipment when at least one of the following is satisfied:

11. A communication device comprising a processor, a memory, and a program or command stored in the memory and executable on the processor, the program or command implementing the steps of the message sending method according to any one of claims 1 to 10 when executed by the processor.

Images