CN113905452B

CN113905452B - Message sending method, message receiving method, message sending device, message receiving device and communication equipment

Info

Publication number: CN113905452B
Application number: CN202010643212.7A
Authority: CN
Inventors: 钟婷婷; 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-07-06
Filing date: 2020-07-06
Publication date: 2023-08-08
Anticipated expiration: 2040-07-06
Also published as: WO2022007786A1; CN113905452A

Abstract

The application discloses a message sending method, a message receiving device and communication equipment, and belongs to the technical field of communication. The specific implementation scheme comprises the following steps: under the condition that the terminal is in a non-RRC connection state and has the requirement of sending a target RRC message to network side equipment, initiating a random access process; after the terminal enters an RRC connection state through the random access process, the target RRC message is sent; the target RRC message is an RRC message requiring activated access stratum security. Therefore, the terminal can send the target RRC message without meeting other conditions triggering the establishment or recovery of the RRC connection, and after the RRC connection is successfully established or recovered, the terminal can send the target RRC message by initiating a random access process to enter an RRC connection state, so that the time delay is reduced.

Description

Message sending method, message receiving method, message sending device, message receiving device and communication equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a message sending method, a message receiving device and communication equipment.

Background

Currently, when there is a need for an RRC message of an access stratum security (activated AS security) to be activated to be sent to a network side device, a NON-radio resource control (Radio Resource Control, RRC) connected state (NON-RRCCONNECTED) terminal can only send the RRC message if other conditions (such as mo-data) triggering RRC connection establishment or restoration are satisfied, and after the RRC connection is successfully established or restored. Thus, the time delay when the conventional non-RRC connection state terminal transmits the RRC message is large.

Disclosure of Invention

An objective of the embodiments of the present application is to provide a message sending method, a receiving method, a device, and a communication device, so as to solve a problem that a delay is relatively large when an existing non-RRC connection state terminal sends an RRC message requiring activated AS security.

In order to solve the technical problems, the application is realized as follows:

in a first aspect, a message sending method is provided, which is applied to a terminal, and includes:

under the condition that the terminal is in a non-RRC connection state and has the requirement of sending a target RRC message to network side equipment, initiating a random access process;

after the terminal enters an RRC connection state through the random access process, the target RRC message is sent;

the target RRC message is an RRC message of the access layer security which needs to be activated.

In a second aspect, a message receiving method is provided, applied to a network side device, and includes:

receiving a target RRC message from a terminal;

the target RRC message is an RRC message of the access layer security to be activated; the target RRC message is sent after the terminal enters the RRC connection state through the random access process under the condition that the terminal is in a non-RRC connection state and the requirement of sending the target RRC message exists.

In a third aspect, there is provided a message transmitting apparatus applied to a terminal, including:

the execution module is used for initiating a random access process under the condition that the terminal is in a non-RRC connection state and the requirement of sending a target RRC message to network side equipment exists;

the first transceiver module is used for sending the target RRC message after the terminal enters an RRC connection state through the random access process;

In a fourth aspect, a message receiving apparatus is provided, which is applied to a network side device, and includes:

a second transceiver module for receiving a target RRC message from the terminal;

In a fifth aspect, there is provided a terminal comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the steps of the method according to the first aspect.

In a sixth aspect, there is provided a network side device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction when executed by the processor implementing the steps of the method according to the second aspect.

In a seventh aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect or performs the steps of the method according to the second aspect.

In an eighth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being configured to execute programs or instructions, to implement the steps of the method according to the first aspect, or to implement the steps of the method according to the second aspect.

In the embodiment of the present application, the terminal may initiate a random access procedure when in a non-RRC connected state and there is a need to send a target RRC message to the network side device, and send the target RRC message after entering the RRC connected state through the random access procedure. Therefore, the terminal can send the target RRC message without meeting other conditions triggering the establishment or recovery of the RRC connection, and after the RRC connection is successfully established or recovered, the terminal can send the target RRC message by initiating a random access process to enter an RRC connection state, so that the time delay is reduced. Furthermore, resource waste, energy consumption and the like can be avoided.

Drawings

Fig. 1 is a block diagram of a wireless communication system provided in an embodiment of the present application;

fig. 2 is a flowchart of a message sending method provided in an embodiment of the present application;

fig. 3 is a flow chart of a target RRC message transmission procedure in a specific embodiment of the present application;

fig. 4 is a schematic structural diagram of a message sending device according to an embodiment of the present application;

fig. 5 is a flowchart of a message receiving method provided in an embodiment of the present application;

fig. 6 is a schematic structural diagram of a message receiving device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a network side device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the "first" and "second" distinguished objects generally are of the type and do not limit the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/evolution of LTE (LTE-Advanced, LTE-a)) The system may also be used in other wireless communication systems such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency DivisionMultiple Access, OFDMA), single-carrier frequency division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. However, the following description describes a New air interface (NR) system for purposes of example, and NR terminology is used in much of the following description, although the techniques are also applicable to applications other than NR system applications, such as generation 6 (6 ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may also be called a terminal Device or a User Equipment (UE), and the terminal 11 may be a terminal-side Device such as a mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer) or a notebook (Personal Digital Assistant, PDA), a palm Computer, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet Device (Mobile Internet Device, MID), a Wearable Device (or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and the Wearable Device includes: a bracelet, earphone, glasses, etc. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may be a base station or a core network, wherein the base station may be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (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 transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the field, and the base station is not limited to a specific technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

To facilitate an understanding of the embodiments of the present application, the following is first described.

In order to solve the problem that the time delay is relatively large when the conventional NON-RRC connected terminal (such as the NON-RRC connected UE) sends the RRC message requiring activated AS security, the embodiment of the present application proposes a method for sending the target RRC message by initiating a random access procedure to enter an RRC connected state (RRCCONNECTED) when the NON-RRC connected UE has a need to send the RRC message requiring activated AS security to the network side device.

In the embodiment 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 mentioned in the following embodiments is an RRC message requiring activated AS security.

1. Alternatively, the target RRC message may be an RRC message related to configuration of the first transmission mode. In this case, the terminal has a need to transmit the target RRC message to the network side device in case at least one of the following is satisfied:

the terminal supports the transmission of a first transmission mode;

the network supports the transmission of a first transmission mode; for example, the system message contains a corresponding indication;

the size of the media access control protocol data unit (Media Access Control Protocol Data Unit, MAC PDU) containing the target RRC message is less than or equal to the maximum transport block size (Transport Block Size, TBS) supported by the terminal defined based on the terminal type;

The terminal satisfies at least one of the following: the configuration of the first transmission mode is of interest, no longer of interest, and the configuration of the first transmission mode needs to be updated.

It should be noted that the first transmission manner described above may be understood as a transmission manner similar to the transmission of a PUR (Preconfigured Uplink Resource ) or a preconfigured PUSCH resource for small data transmission (Small Data Transmission, SDT), and may be understood as a transmission manner of a PUR or a preconfigured PUSCH resource for SDT in some cases, which is not limited thereto. In this case, the target RRC message may be a physical layer containing side information related to the configuration of the pre-configured PUSCH resource, such as a physical request message. Taking a pre-configured PUSCH resource transmission mode of small data transmission as an example, the UE has a need to send the target RRC message to the network side device if at least one of the following is satisfied:

UE supports the transmission of a pre-configured PUSCH resource mode;

the network supports the transmission of the pre-configured PUSCH resource mode, for example, the system message contains a corresponding instruction;

the size of the MAC PDU including the target RRC message is less than or equal to the UE-type defined TBS supported by the UE maximum

The UE is interested in the configuration of the pre-configured PUSCH resources or is no longer interested in, or needs to update the configuration of the pre-configured PUSCH resources.

2. Alternatively, the target RRC message may be an RRC message related to multicast broadcast service (Multicast and Broadcast Service, MBS) Counting (Counting), such as an MBSCountingResponse message. In this case, the terminal has a need to transmit the target RRC message to the network side device in case at least one of the following is satisfied:

the terminal has MBS capability;

the network supports MBS; for example, the system message contains a corresponding indication;

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 terminal type;

the RRC layer of the terminal receives a control message (such as an MBSCountingRequest message) related to MBS counting sent by the network side equipment;

the terminal is receiving or interested in receiving at least one MBS service indicated in an MBS count related control message, such as an MBSCountingRequest message.

3. Alternatively, the target RRC message may be an MBS interest indication (Interest Indication) related RRC message, such as an MBSInterestIndication message. In this case, the terminal has a need to transmit the target RRC message to the network side device in case at least one of the following is satisfied:

The terminal has MBS capability;

the terminal receives control information related to MBS service sent by network side equipment; for example, the control information related to the MBS service may be sent through a system message or dedicated RRC signaling;

the terminal enters or leaves the service area; for example, UE-a-enters the service area (upon entering the service area), or UE-a-leaves the service area;

MBS session (session) starts or stops; for example, MBS session begins or MBS session stops;

the content of the MBS interest indication message is changed;

the cell or base station transmitting the MBS service related control information is changed.

It is to be understood that the target RRC message may be selected from the above three RRC messages, and may be selected from any RRC message requiring activated AS security, which is not limited.

The message sending method and the receiving method provided by the embodiment of the application are described in detail below through specific embodiments and application scenes thereof with reference to the accompanying drawings.

Referring to fig. 2, fig. 2 is a flowchart of a message sending method provided in an embodiment of the present invention, where the method is applied to a terminal, as shown in fig. 2, and the method includes the following steps:

step 201: and under the condition that the terminal is in a non-RRC connection state and the requirement of sending a target RRC message to network side equipment exists, initiating a random access process.

In this embodiment, the target RRC message is an RRC message requiring activated AS security. The Random Access procedure may be selected from a conventional Random Access procedure, such as a 2-step (2-step) Random Access procedure, or a 4-step (4-step) Random Access procedure.

Step 202: and after the terminal enters the RRC connection state through the random access process, sending a target RRC message.

It should be noted that, when the terminal in this embodiment enters the RRC connected state from the non-RRC connected state, the terminal may be implemented through an RRC connection establishment (RRC connection establishment, or referred to as RRCSetup) procedure, or may be implemented through an RRC connection restoration (RRC connection resume, or referred to as rrcrescene) procedure. This is explained as follows.

Case one: the terminal enters an RRC connection state through an RRC connection setup procedure, and transmits a target RRC message after entering the RRC connection state. The specific process is as follows:

1. preparation stage

Once the RRC layer of the terminal has a need to send an RRC message (target RRC message) of need activated AS security, the terminal will trigger an RRC connection setup (RRCSetup) procedure, generate an RRC setup request message, submit the RRC setup request message to the bottom layer, and trigger generation of the content of the target RRC message. It is understood that the RRC establishment request message and the target RRC message are generated in the RRC layer, where the bottom layer is a protocol layer below the RRC layer, such as packet data convergence protocol (Packet Data Convergence Protocol, PDCP), radio link control (Radio Link Control, RLC), MAC layer.

1) In the RRCSetup process, the terminal can set an establishment cause Establishmentcause value which is at least any one of the following:

(1) Multiplexing existing Establishmentcause values, such as mo-data, mo-signal, etc.;

(2) the newly set Establishmentcause value is at least any one of the following:

the newly set Establishmentcause value is irrelevant to the target RRC message, i.e. all the target RRC messages, such as MO-RRCmessage, are unified, and the Establishmentcause value is set as MO-RRCmessage; the independence of the target RRC message can be independent of the message type or form of the target RRC message, and can also be independent of the content of the target RRC message;

the newly set Establishmentcause value may be associated with a target RRC message, such as "XX configuration request message", setting Establishmentcause value to "XX configuration request message"; the related target RRC message may be related to a message type or form of the target RRC message, or may be related to content of the target RRC message.

2) In the RRCSetup procedure, the terminal may further perform at least one of:

(1) no checking of the unified access control (Unified Access Control, UAC) is performed, access attempts being directly allowed;

(2) the UAC is checked by using the set existing Access category (Access category) and/or Access identity (ies). That is, multiplexing existing Access category and/or Access identity (ies), for example, setting Access category to 7,Access identity to 0, etc.;

(3) And checking the UAC by using the set new access category and/or access identifier. I.e. the UAC check is performed using the newly set Access category and/or Access identity (ies), at least any one of the following:

the new Access category and/or Access identity (ies) are not related to the target RRC message, i.e. all target RRC messages are unified to the same value, e.g. Access category is unified to 11,Access identity to 6, etc. The independence of the target RRC message can be independent of the message type or form of the target RRC message, or independent of the content of the target RRC message.

The new Access category and/or Access identity (ies) are related to the target RRC message, e.g. for "XX configuration request message", access category is set to 11,Access identity to 6, etc. The related target RRC message may be related to a message type or form of the target RRC message, or may be related to content of the target RRC message.

3) The trigger time point for the generation of the content of the target RRC message may be at least one of:

(1) triggering generation of the content of the target RRC message immediately and triggering RRC connection establishment process once the terminal has the requirement of sending the target RRC message to the network side equipment;

(2) The process of RRC connection establishment is triggered once the terminal has a need to send the target RRC message to the network side device, and the generation of the target RRC message content is triggered in the process of RRC connection establishment. Further, the triggering of the generation of the target RRC message content in RRC connection establishment may include at least one of:

at the Initiation phase (Initiation) of the RRC connection establishment procedure, triggering the generation of the content of the target RRC message;

triggering the generation of the content of the target RRC message in an operation procedure (Actions related to transmission of RRCSetupRequest message) related to the transmission of the RRC establishment request message;

triggering the generation of the content of the target RRC message after the terminal receives the RRC setup message (Reception of the RRCSetup by the UE) and before generating the content of the RRC setup complete message;

triggering the generation of the content of the target RRC message after the terminal receives the RRC establishment message and in the process of generating the content of the RRC establishment completion message;

after the terminal receives the RRC establishment message and submits the RRC establishment completion message to the bottom layer, the generation of the content of the target RRC message is immediately triggered;

And triggering the generation of the content of the target RRC message after the terminal successfully transmits the RRC establishment completion message to the network side equipment.

4) After the content in the target RRC message is generated, the terminal may store the content in the target RRC message using the first mathematical expression, or may not store the content in the target RRC message.

Further, the first mathematical expression may include at least one of: any mathematical expression of variables, arrays, structures, etc. That is, after the content of the target RRC message is generated, the terminal may store using any mathematical expression of variables, arrays, and/or structures.

Optionally, after the content in the target RRC message is generated, the terminal may further set the content in the target RRC message to be a part of the content of the RRC setup complete message, or not set the content in the target RRC message to be a part of the content of the RRC setup complete message.

5) The RRC layer of the terminal may generate an rrcsetup request message with an EstablishmentCause of the corresponding value and submit it to the bottom layer.

2. Random Access (RACH) phase

In this stage, the MAC layer of the terminal initiates a random access procedure, and submits a MAC PDU with an rrcsetup request message to the physical layer and sends to the network side device. The terminal successfully completes the RACH and receives an RRC setup (RRCSetup) message sent by the network side device, and triggers the target RRC message to be submitted to the bottom layer.

6) The trigger event of the random access procedure may be at least one of:

(1) multiplexing existing trigger events; such as Initial access from RRC _idle;

(2) the newly set trigger event is at least any one of the following:

all target RRC messages, such as MO-RRCmessage, are unified, regardless of the target RRC message. The independence of the target RRC message can be independent of the message type or form of the target RRC message, or independent of the content of the target RRC message.

Related to the target RRC message, e.g. sending a separate target RRC message as a trigger event, e.g. PUR configuration request message, MBSCountingResponse message, MBSInterestIndication message, etc. The related target RRC message may be related to a message type or form of the target RRC message, or may be related to content of the target RRC message.

7) For the point in time that triggers the target RRC message to be submitted to the underlying layer, at least one of the following may be:

(1) triggering to submit the target RRC message to the bottom layer after the terminal receives the RRC setup message (Reception of the RRCSetup by the UE) and before generating the content of the RRC setup complete message;

(2) triggering to submit the target RRC message to the bottom layer after the terminal receives the RRC establishment message and in the process of generating the content of the RRC establishment completion message;

(3) After the terminal receives the RRC establishment message and submits the RRC establishment completion message to the bottom layer, immediately triggering the target RRC message to be submitted to the bottom layer;

(4) triggering to submit the target RRC message to the bottom layer after the RRC establishment completion message is successfully sent to the network side equipment.

3. Transmission phase

In this stage, the terminal transmits an RRC setup complete message to the network side device, and transmits a target RRC message to the network side device.

Optionally, there may be at least one of the following relationships between the RRC setup complete message and the target RRC message:

(1) the content of the target RRC message is part of the content of the RRC setup complete message, and the target RRC message is sent as part of the RRC setup complete message. That is, in this case, the terminal transmits only the RRC setup complete message, and only one RRC message is transmitted to the network side device. In addition to this, the content of the target RRC message may be in the corresponding RRC message, instead of being in the RRC setup complete message, that is, the terminal sends two RRC messages to the network side device.

(2) The target RRC message and the RRC establishment completion message are multiplexed and sent in the same MAC PDU; at least any one of the following:

the RRC setup complete message is located before the target RRC message; in other words, it may be: the RRC establishment complete message is located before the MAC PDU, and the target RRC message is located after the MAC PDU;

The RRC establishment complete message is located after the target RRC message; in other words, it may be: the target RRC message is located before and the RRC setup complete message is located after the MAC PDU.

(3) The target RRC message and the RRC establishment completion message are sent in different MAC PDUs, i.e. are not multiplexed to be sent in the same MAC PDU; at least any one of the following:

the RRC establishment completion message is carried by the former MAC PDU and is sent to the network side equipment, and the target RRC message is carried by the latter MAC PDU and is sent to the network side equipment;

the RRC establishment complete message is carried by the next MAC PDU to be sent to the network side device.

And a second case: the terminal enters an RRC connection state through an RRC connection recovery process, and transmits a target RRC message after entering the RRC connection state. The specific process is as follows:

1. preparation stage

Once the RRC layer of the terminal has a need to send an RRC message (target RRC message) of need activated AS security, the terminal will trigger an RRC connection recovery (rrreport) procedure, generate an RRC recovery request or an RRC recovery request 1 message, submit the RRC recovery request or the RRC recovery request 1 message to the bottom layer, and trigger the generation of the content of the target RRC message. It will be appreciated that the RRC resume request or RRC resume request 1 message and the target RRC message are generated in the RRC layer, where the underlying layers are the protocol layers below the RRC layer, such as packet data convergence protocol (Packet Data Convergence Protocol, PDCP), radio link control (Radio Link Control, RLC), MAC layer.

1) In the rrcreseume process, the terminal may set a resume reason resumease value, which is at least any one of the following:

(1) multiplexing existing resumease values, such as mo-data, mo-signal, etc.;

(2) the newly set resumease value is at least any one of the following:

the newly set resumease value is irrelevant to the target RRC message, i.e., all the target RRC messages, such as MO-RRCmessage, are unified, and the resumease value is set to MO-RRCmessage; the independence of the target RRC message can be independent of the message type or form of the target RRC message, and can also be independent of the content of the target RRC message;

the newly set resumease value may be associated with a target RRC message, such as "XX configuration request message", setting the resumease value to "XX configuration request message"; the related target RRC message may be related to a message type or form of the target RRC message, or may be related to content of the target RRC message.

2) In the rrcreseume procedure, the terminal may further perform at least one of:

(1) triggering generation of the content of the target RRC message immediately and triggering RRC connection resume process once the terminal has the requirement of sending the target RRC message to the network side equipment;

(2) The process of RRC connection resume is triggered once the terminal has a need to send the target RRC message to the network side device, and the generation of the target RRC message content is triggered in the process of RRC connection resume. Further, the triggering of the generation of the target RRC message content in RRC connection resume may include at least one of:

at the Initiation phase (Initiation) of the RRC connection resume procedure, triggering the generation of the content of the target RRC message;

triggering the generation of the content of the target RRC message in the operation process (Actions related to transmission of RRCResumeRequest or RRCResumeRequest message) related to the RRC recovery request or the RRC recovery request1 message transmission;

triggering the generation of the content of the target RRC message after the terminal receives the RRC resume message (Reception of the RRCResume by the UE) and before generating the content of the RRC resume complete (rrcresmectomplete) message;

triggering the generation of the content of the target RRC message after the terminal receives the RRC recovery message and in the process of generating the content of the RRC recovery completion message;

after receiving the RRC recovery message, the terminal submits the RRC recovery completion message to the bottom layer, and immediately triggers the generation of the content of the target RRC message;

And triggering the generation of the content of the target RRC message after the terminal successfully transmits the RRC recovery completion message to the network side equipment.

Optionally, after the content in the target RRC message is generated, the terminal may further set the content in the target RRC message to be a part of the content of the RRC restoration complete message, or not set the content in the target RRC message to be a part of the content of the RRC restoration complete message.

5) The RRC layer of the terminal may generate rrcreseumerequest/rrcreseumerequest 1 message with a resumecase of a corresponding value and submit it to the base layer.

2. Random Access (RACH) phase

In this stage, the MAC layer of the terminal initiates a random access procedure and submits a MAC PDU with rrcresemerequest/rrcresemerequest 1 message to the physical layer and sends to the network side device. The terminal successfully completes the RACH and receives an RRC resume (rrreport) message sent by the network side device, and triggers the submission of the target RRC message to the bottom layer.

6) The trigger event of the random access procedure may be at least one of:

(1) multiplexing existing trigger events; such as Transition from RRC _inactive, etc.;

(2) the newly set trigger event is at least any one of the following:

(1) triggering to submit the target RRC message to the bottom layer after the terminal receives the RRC resume message (Reception of the RRCResume by the UE) and before generating the content of the RRC resume complete (rrcresmeecomplete) message;

(2) Triggering to submit the target RRC message to the bottom layer after the terminal receives the RRC recovery message and in the process of generating the content of the RRC recovery completion message;

(3) after the terminal receives the RRC recovery message and submits the RRC recovery completion message to the bottom layer, immediately triggering the target RRC message to be submitted to the bottom layer;

(4) and triggering to submit the target RRC message to the bottom layer after the RRC recovery completion message is successfully sent to the network side equipment.

3. Transmission phase

In this stage, the terminal transmits an RRC resume complete message to the network side device, and transmits a target RRC message to the network side device.

Optionally, there may be at least one of the following relationships between the RRC resume complete message and the target RRC message:

(1) the content of the target RRC message is part of the content of the RRC resume complete message, and the target RRC message is sent as part of the RRC resume complete message. That is, in this case, the terminal transmits only the RRC restoration complete message, and only one RRC message is transmitted to the network side device. In addition to this, the content of the target RRC message may be in the corresponding RRC message, instead of being in the RRC recovery complete message, that is, the terminal sends two RRC messages to the network side device.

(2) The target RRC message and the RRC recovery completion message are multiplexed and sent in the same MAC PDU; at least any one of the following:

the RRC recovery complete message is located before the target RRC message; in other words, it may be: the RRC recovery complete message is positioned in front of the MAC PDU, and the target RRC message is positioned in back of the MAC PDU;

the RRC recovery complete message is positioned after the target RRC message; in other words, it may be: the target RRC message is located before and the RRC resume complete message is located after the MAC PDU.

(3) The target RRC message and the RRC recovery complete message are sent in different MAC PDUs, namely, are not multiplexed to be sent in the same MAC PDU; at least any one of the following:

the RRC recovery completion message is carried by the former MAC PDU and is sent to the network side equipment, and the target RRC message is carried by the latter MAC PDU and is sent to the network side equipment;

the RRC restoration complete message is carried by the next MAC PDU and sent to the network side device.

The present application is described in detail with reference to specific examples.

Example 1

In this embodiment, as shown in fig. 3, the corresponding target RRC message transmission procedure may include:

Step 30: and (5) a preparation stage.

Once the RRC layer of the UE has a need to send an RRC message (target RRC message) for the AS security, the UE will trigger the rrcreseume procedure, generate rrcreseumerequest/rrcreseumerequest 1 message and submit it to the bottom layer.

-UAC related settings: setting Access category to 11,Access identity to 0, performing UAC and checking through UAC, i.e. Access attempt is allowed.

Setting ResumeCAase value setting RRCResumeCAase to MO-RRCmessage.

The generation and submission of rrcresemerequest/rrcresemerequest 1 message to the underlying layer: for example, the RRC layer of the UE generates an RRCResumeRequest/RRCResumeRequest1 message with a ResumeAuse value of MO-RRCmessage and submits to the bottom layer.

Step 31: the MAC layer of the UE initiates a random access procedure and sends Msg1, i.e. a random access preamble, to the base station gNB.

Step 32: the gNB returns Msg2, a Random Access Response (RAR), to the UE.

Step 33: the MAC layer of the UE sends a MAC PDU including rrcresemerequest/rrcresemerequest 1 message to the gNB over Msg 3.

Step 34: the gNB returns Msg4 to the UE, which contains the RRCResume message.

Step 35: the UE sends an RRCResumeComplete message to the gNB.

Optionally, in the process of generating the content of the rrcruumecomplete message by the RRC layer of the UE, triggering generation of a target RRC message (such as an MBSCountingResponse message), and taking the content of the target RRC message as a part of the content of the rrcruumecomplete message; the rrcrumeCommple message is submitted to the bottom layer. The UE then sends a RRCResumeComplete message to the gNB.

Example two

In the second embodiment, as shown in fig. 3, the corresponding target RRC message sending procedure may include:

step 30: and (5) a preparation stage.

Setting ResumeCAase value setting RRCResumeCAase to MO-RRCmessage.

Step 32: the gNB returns Msg2, a Random Access Response (RAR), to the UE.

Step 34: the gNB returns Msg4 to the UE, which contains the RRCResume message.

Step 35: the UE sends an RRCResumeComplete message to the gNB.

Optionally, the RRC layer of the UE generates the content of the rrcruumecomplete message and submits the rrcruumecomplete message to the bottom layer; immediately after submitting the rrcruxecm response message to the base layer, the generation of a target RRC message (such as an MBSCountingResponse message) is triggered and the target RRC message is submitted to the base layer. And then, the UE MAC layer multiplexes the RRCResumeCommple message and the target RRC message in one MAC PDU, submits the multiplexed message to the physical layer and sends the multiplexed message to the gNB.

It should be noted that, in the message sending method provided in the embodiment of the present application, the execution body may be a message sending device, or a control module in the message sending device for executing the message sending method. In the embodiment of the present application, a message sending device executes a message sending method as an example, and a message sending device provided in the embodiment of the present application is described.

Referring to fig. 4, fig. 4 is a schematic structural diagram of a message sending device according to an embodiment of the present invention, which is applied to a terminal. As shown in fig. 4, the message transmitting apparatus 40 includes:

an execution module 41, configured to initiate a random access procedure 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;

A first transceiver module 42, configured to send the target RRC message after the terminal enters an RRC connected state through the random access procedure;

Optionally, the execution module 41 is further configured to perform the following:

triggering an RRC connection establishment process, generating an RRC establishment request message, and submitting the RRC establishment request message to a bottom layer; or triggering an RRC connection recovery process, generating an RRC recovery request or an RRC recovery request 1 message, and submitting the RRC recovery request or the RRC recovery request 1 message to the bottom layer;

triggering the generation of the content of the target RRC message.

Optionally, the message sending device 40 further includes:

a setting module, configured to set an EstablishmentCause value in the RRC connection establishment procedure; wherein the Establishmentcause value is at least one of:

multiplexing the existing EstablishmentCause value;

a newly set Establishmentcause value; wherein the newly set Establishmentcause value is independent of the target RRC message, or the newly set Establishmentcause value is related to the target RRC message;

Or, in the RRC connection recovery procedure, setting a resumease value; wherein the resumease value is at least one of:

multiplexing existing resumease values;

a newly set resumease value; wherein the newly set resumease value is independent of the target RRC message or the newly set resumease value is related to the target RRC message.

Optionally, during the RRC connection establishment procedure or the RRC connection recovery procedure, the executing module 41 is further configured to execute at least one of the following:

checking of the unified access control UAC is not performed;

checking UAC by using the set existing access category and/or access identifier;

checking UAC by using the set new access category and/or access identifier; wherein the newly set access category and/or access identity is not related to the target RRC message, or the newly set access category and/or access identity is related to the target RRC message.

Optionally, the execution module 41 is further configured to perform at least one of the following:

when the terminal has the requirement of sending a target RRC message to network side equipment, immediately triggering the generation of the content of the target RRC message, and then triggering an RRC connection establishment process or an RRC connection recovery process;

Triggering an RRC connection establishment process when the terminal has a requirement of sending a target RRC message to network side equipment, and triggering generation of target RRC message content in the RRC connection establishment process; or triggering the RRC connection recovery process, and triggering the generation of the target RRC message content in the RRC connection recovery process.

Optionally, the executing module 41 is further configured to execute at least one of the following during the RRC connection establishment procedure:

triggering the generation of the content of the target RRC message at the initiation stage of the RRC connection establishment process;

triggering the generation of the content of the target RRC message in the operation process related to the transmission of the RRC establishment request message;

triggering the generation of the content of the target RRC message after the terminal receives the RRC establishment message and before the content of the RRC establishment completion message is generated;

after the terminal receives the RRC establishment message and submits the RRC establishment completion message to the bottom layer, the terminal immediately triggers the generation of the content of the target RRC message;

and triggering the generation of the content of the target RRC message after the terminal successfully sends the RRC establishment completion message to the network side equipment.

Optionally, the executing module 41 is further configured to execute at least one of the following during the RRC connection recovery procedure:

triggering the generation of the content of the target RRC message at the initiation stage of the RRC connection recovery process;

triggering the generation of the content of the target RRC message in the operation process related to the transmission of the RRC recovery request message;

triggering the generation of the content of the target RRC message after the terminal receives the RRC recovery message and before the content of the RRC recovery completion message is generated;

after the terminal receives the RRC recovery message and submits the RRC recovery completion message to the bottom layer, the terminal immediately triggers the generation of the content of the target RRC message;

Optionally, the message sending device 40 further includes:

and the storage module is used for storing the content in the target RRC message by using a first mathematical expression form after the content in the target RRC message is generated, or not storing the content in the target RRC message.

Optionally, the first mathematical expression includes at least one of:

variables, arrays, structures.

Optionally, the execution module 41 is further configured to:

setting the content in the target RRC message as a part of the content of an RRC establishment completion message or an RRC recovery completion message;

alternatively, the content in the target RRC message is not set to be part of the content of the RRC setup complete message or the RRC resume complete message.

Optionally, the triggering event of the random access procedure is at least one of the following:

multiplexing existing trigger events;

a newly set trigger event; wherein the newly set trigger event is independent of the target RRC message, or the newly set trigger event is related to the target RRC message.

Optionally, the first transceiver module 42 is further configured to: under the condition of triggering an RRC connection establishment process, sending the MAC PDU comprising the RRC establishment request message to network side equipment; successfully completing random access and receiving RRC establishment information sent by the network equipment;

the execution module 41 is further configured to: triggering the target RRC message to be submitted to the bottom layer.

Optionally, in case of triggering an RRC connection setup procedure, the executing module 41 is further configured to execute at least one of the following:

Triggering to submit the target RRC message to a bottom layer after the terminal receives the RRC establishment message and before generating the content of the RRC establishment completion message;

triggering to submit the target RRC message to a bottom layer after the terminal receives the RRC establishment message and in the process of generating the content of the RRC establishment completion message;

after the terminal receives the RRC establishment message and submits the RRC establishment completion message to the bottom layer, immediately triggering the target RRC message to be submitted to the bottom layer;

triggering to submit the target RRC message to the bottom layer after the RRC establishment completion message is successfully sent to the network side equipment.

Optionally, the first transceiver module 42 is further configured to: under the condition of triggering an RRC connection recovery process, sending the MAC PDU comprising the RRC recovery request or the RRC recovery request 1 message to network side equipment; successfully completing random access and receiving RRC recovery information sent by the network equipment;

Optionally, in case of triggering an RRC connection recovery procedure, the executing module 41 is further configured to execute at least one of the following:

triggering to submit the target RRC message to a bottom layer after the terminal receives the RRC recovery message and before generating the content of the RRC recovery completion message;

Triggering to submit the target RRC message to a bottom layer after the terminal receives the RRC recovery message and in the process of generating the content of the RRC recovery completion message;

after the terminal receives the RRC recovery message and submits the RRC recovery completion message to the bottom layer, immediately triggering the target RRC message to be submitted to the bottom layer;

and triggering the target RRC message to be submitted to the bottom layer after the RRC recovery completion message is successfully sent to the network side equipment.

Optionally, in case of triggering an RRC connection setup procedure, the first transceiver module 42 is further configured to: sending an RRC establishment completion message and a target RRC message to the network side equipment;

wherein, there is at least one relation between the target RRC message and the RRC setup complete message:

the content of the target RRC message is a part of the content of the RRC establishment completion message, and the target RRC message is sent as a part of the RRC establishment completion message;

the target RRC message and the RRC establishment completion message are multiplexed and sent in the same MAC PDU;

the target RRC message and the RRC setup complete message are sent in different MAC PDUs.

Optionally, in case of triggering an RRC connection recovery procedure, the first transceiver module 42 is further configured to: sending an RRC recovery completion message and a target RRC message to the network side equipment;

Wherein, there is at least one relation between the target RRC message and the RRC recovery complete message:

the content of the target RRC message is a part of the content of the RRC recovery complete message, and the target RRC message is sent as a part of the RRC recovery complete message;

multiplexing the target RRC message and the RRC recovery completion message to be sent in the same MAC PDU;

the target RRC message and the RRC resume complete message are sent in different MAC PDUs.

The message sending device in the embodiment of the application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device may be a mobile terminal or a non-mobile terminal. By way of example, mobile terminals may include, but are not limited to, the types of terminals 11 listed above, and non-mobile terminals may be servers, network attached storage (Network Attached Storage, NAS), personal computers (personal computer, PCs), televisions (TVs), teller machines, self-service machines, etc., and embodiments of the present application are not limited in detail.

The message sending device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

The message sending device 40 provided in this embodiment of the present application can implement each process implemented by the method embodiment shown in fig. 2, and achieve the same technical effects, and for avoiding repetition, a detailed description is omitted herein.

Referring to fig. 5, fig. 5 is a flowchart of a message receiving method according to an embodiment of the present invention, where the method is applied to a network side device, as shown in fig. 5, and the method includes the following steps:

step 501: receiving a target RRC message from a terminal;

In this embodiment, the target RRC message sent by the non-RRC connected terminal after entering the RRC connected state through the random access procedure may be received, without requiring that the terminal can send the target RRC message after the RRC connection is successfully established or restored under other conditions triggering the RRC connection establishment or restoration. Furthermore, resource waste, energy consumption and the like can be avoided.

Optionally, before the target RRC message is received from the terminal, the method further includes:

Receiving an RRC establishment request message sent by the terminal;

after establishing RRC connection with the terminal, sending an RRC establishment message to the terminal;

the method further includes, while the slave terminal receives the target RRC message:

receiving an RRC establishment completion message sent by the terminal;

Optionally, when the target RRC message and the RRC establishment complete message are multiplexed in the same MAC PDU, the MAC PDU is configured to at least one of the following:

the RRC establishment complete message is located before the target RRC message;

the RRC setup complete message is located after the target RRC message.

Receiving an RRC recovery request or an RRC recovery request 1 message sent by the terminal;

after recovering the RRC connection with the terminal, sending an RRC recovery message to the terminal;

receiving an RRC recovery completion message sent by the terminal;

Optionally, when the target RRC message and the RRC restoration complete message are multiplexed in the same MAC PDU, the MAC PDU is configured to at least one of the following:

the RRC recovery complete message is located before the target RRC message;

the RRC resume complete message is located after the target RRC message.

Optionally, when the target RRC message is an RRC message related to configuration of the first transmission mode, the method further includes:

And sending indication information for indicating the network to support the transmission of the first transmission mode to the terminal.

Optionally, when the target RRC message is an MBS count related RRC message, the method further includes at least one of:

transmitting indication information for indicating that the network supports MBS to the terminal; for example, the indication information may be transmitted through system information;

and sending the control message related to MBS counting to the terminal.

Optionally, when the target RRC message is an RRC message related to MBS interest indication, the method further includes at least one of:

transmitting control information related to MBS service to the terminal; for example, the control information may be transmitted through a system message or dedicated RRC signaling.

It should be noted that, in the message receiving method provided in the embodiment of the present application, the execution body may be a message receiving apparatus, or a control module in the message receiving apparatus for executing the message receiving method. In the embodiment of the present application, a message receiving device executes a message receiving method as an example, and the message receiving device provided in the embodiment of the present application is described.

Fig. 6 is a schematic structural diagram of a message receiving apparatus according to an embodiment of the present invention, which is applied to a network device. As shown in fig. 6, the message receiving apparatus 60 includes:

a second transceiving module 61 for receiving a target RRC message from the terminal;

Optionally, the second transceiver module 61 is further configured to:

receiving an RRC establishment request message sent by the terminal;

receiving an RRC establishment completion message sent by the terminal;

Optionally, the second transceiver module 61 is further configured to:

receiving an RRC recovery completion message sent by the terminal;

Optionally, the second transceiver module 61 is further configured to:

when the target RRC message is an RRC message related to configuration of transmission of the first transmission mode, sending indication information for indicating that the network supports the transmission of the first transmission mode to the terminal;

or when the target RRC message is an RRC message related to MBS counting, sending indication information for indicating that the network supports MBS to the terminal, and/or sending a control message related to MBS counting to the terminal;

Or when the target RRC message is an RRC message related to MBS interest indication, sending indication information for indicating that the network supports MBS to the terminal, and/or sending control information related to MBS service to the terminal.

The message receiving apparatus 60 provided in this embodiment of the present application can implement each process implemented by the method embodiment shown in fig. 5, and achieve the same technical effects, and for avoiding repetition, a detailed description is omitted herein.

Optionally, as shown in fig. 7, the embodiment of the present application further provides a communication device 70, including a processor 71, a memory 72, and a program or an instruction stored in the memory 72 and capable of running on the processor 71, where, for example, the communication device 70 is a terminal, the program or the instruction is executed by the processor 71 to implement each process of the foregoing embodiment of the message sending method, and achieve the same technical effects. When the communication device 70 is a network side device, the program or the instruction when executed by the processor 71 implements the respective processes of the above-described message receiving method embodiment, and the same technical effects can be achieved, and for avoiding repetition, a detailed description is omitted herein.

Fig. 8 is a schematic hardware structure of a terminal implementing an embodiment of the present application.

The terminal 800 includes, but is not limited to: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

Those skilled in the art will appreciate that the terminal 800 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 810 by a power management system for performing functions such as managing charging, discharging, and power consumption by the power management system. The terminal structure shown in fig. 8 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine certain components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 804 may include a graphics processor (Graphics Processing Unit, GPU) 8041 and a microphone 8042, with the graphics processor 8041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 807 includes a touch panel 8071 and other input devices 8072. Touch panel 8071, also referred to as a touch screen. The touch panel 8071 may include two parts, a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In this embodiment, after receiving downlink data from a network side device, the radio frequency unit 801 processes the downlink data with the processor 810; in addition, the uplink data is sent to the network side equipment. In general, the radio frequency unit 801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 809 may be used to store software programs or instructions and various data. The memory 809 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 809 may include a high-speed random access Memory, and may also include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable EPROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.

The processor 810 may include one or more processing units; alternatively, the processor 810 may integrate an application processor that primarily processes operating systems, user interfaces, and applications or instructions, etc., with a modem processor that primarily processes wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 810.

The processor 810 is configured to initiate a random access procedure when the terminal 800 is in a non-RRC connected state and there is a need to send a target RRC message to the network side device; the target RRC message is an RRC message of the access layer security to be activated;

a radio frequency unit 801, configured to send the target RRC message after the terminal 800 enters the RRC connected state through the random access procedure.

The terminal 800 provided in this embodiment of the present application can implement each process implemented by the method embodiment shown in fig. 2, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.

Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 9, the network side device 900 includes: an antenna 91, a radio frequency device 92, a baseband device 93. The antenna 91 is connected to a radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information via the antenna 91, and transmits the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes information to be transmitted, and transmits the processed information to the radio frequency device 92, and the radio frequency device 92 processes the received information and transmits the processed information through the antenna 91.

The above-described band processing means may be located in the baseband apparatus 93, and the method performed by the network-side device in the above embodiment may be implemented in the baseband apparatus 93, and the baseband apparatus 93 includes a processor 94 and a memory 95.

The baseband device 93 may, for example, include at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 9, where one chip, for example, a processor 94, is connected to the memory 95, so as to call a program in the memory 95 to perform the network side device operation shown in the above method embodiment.

The baseband device 93 may also include a network interface 96 for interacting with the radio frequency device 92, such as a common public radio interface (common public radio interface, CPRI for short).

Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 95 and executable on the processor 94, the processor 94 invokes the instructions or programs in the memory 95 to perform the methods performed by the modules shown in fig. 6 and achieve the same technical effects, and are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and the program or the instruction when executed by a processor implements each process of the foregoing message sending method embodiment, or implements each process of the foregoing message receiving method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

The embodiment of the application further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, implement each process of the foregoing embodiment of the message sending method, or implement each process of the foregoing embodiment of the message receiving method, and achieve the same technical effect, so that repetition is avoided, and no further description is given here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network side device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A message sending method applied to a terminal, comprising:

initiating a random access process when the terminal is in a non-Radio Resource Control (RRC) connection state and there is a need to send a target RRC message to network side equipment;

the target RRC message is an RRC message of the access layer security to be activated;

the method further comprises any one of the following:

when the terminal has a requirement of sending a target RRC message to network side equipment, immediately triggering the generation of the content of the target RRC message, and executing any one of the following steps: triggering an RRC connection establishment process, generating an RRC establishment request message, and submitting the RRC establishment request message to a bottom layer; triggering an RRC connection recovery process, generating an RRC recovery request message or an RRC recovery request 1 message, and submitting the RRC recovery request message or the RRC recovery request 1 message to a bottom layer;

when the terminal has a need of sending a target RRC message to the network side equipment, any one of the following is executed: triggering an RRC connection establishment process, generating an RRC establishment request message, submitting the RRC establishment request message to a bottom layer, and triggering the generation of the content of the target RRC message in the RRC connection establishment process; triggering an RRC connection recovery process, generating an RRC recovery request message or an RRC recovery request 1 message, submitting the RRC recovery request message or the RRC recovery request 1 message to a bottom layer, and triggering the generation of the content of the target RRC message in the RRC connection recovery process.

2. The method according to claim 1, wherein during the RRC connection setup procedure, the method further comprises:

setting an establishment cause Establishmentcause value;

wherein the Establishmentcause value is at least one of:

multiplexing the existing EstablishmentCause value;

or alternatively, the process may be performed,

in the RRC connection recovery procedure, the method further includes:

setting a resumption reason resumease value;

wherein the resumease value is at least one of:

multiplexing existing resumease values;

3. The method according to claim 1, wherein during the RRC connection setup procedure or the RRC connection recovery procedure, the method further comprises at least one of:

checking of the unified access control UAC is not performed;

checking UAC by using the newly set access category and/or access identifier; wherein the newly set access category and/or access identity is not related to the target RRC message, or the newly set access category and/or access identity is related to the target RRC message.

4. The method according to claim 1, wherein triggering the generation of the content of the target RRC message during RRC connection establishment includes at least one of:

Triggering the generation of the content of the target RRC message after the terminal successfully sends the RRC establishment completion message to the network side equipment;

or alternatively, the process may be performed,

the triggering the generation of the content of the target RRC message during the RRC connection recovery process includes at least one of:

5. The method according to claim 1, wherein the method further comprises:

After the content in the target RRC message is generated, the content in the target RRC message is stored by using a first mathematical expression form, or the content in the target RRC message is not stored.

6. The method of claim 5, wherein the first mathematical expression comprises at least one of:

variables, arrays, structures.

7. The method of claim 5, wherein the method further comprises:

8. The method of claim 1, wherein the trigger event of the random access procedure is at least one of:

multiplexing existing trigger events;

9. The method according to claim 1, wherein, in case of triggering an RRC connection setup procedure, after the initiating of the random access procedure, the method further comprises:

Transmitting a media access control protocol data unit (MAC PDU) comprising the RRC establishment request message to network side equipment; successfully completing random access and receiving RRC establishment information sent by the network equipment; triggering the target RRC message to be submitted to the bottom layer;

or alternatively, the process may be performed,

in case of triggering an RRC connection recovery procedure, after the initiating a random access procedure, the method further comprises:

transmitting the MAC PDU comprising the RRC restoration request message or the RRC restoration request 1 message to network side equipment; successfully completing random access and receiving RRC recovery information sent by the network equipment; and triggering the submitting of the target RRC message to an underlying layer.

10. The method according to claim 9, wherein in case of triggering an RRC connection setup procedure, the triggering submits the target RRC message to an underlying layer, comprising at least one of:

triggering to submit the target RRC message to the bottom layer after the RRC establishment completion message is successfully sent to the network side equipment;

or alternatively, the process may be performed,

in the event that an RRC connection recovery procedure is triggered, the triggering submits the target RRC message to an underlying layer, including at least one of:

11. The method according to claim 1, wherein in case of triggering an RRC connection setup procedure, the method further comprises:

Sending an RRC establishment completion message and a target RRC message to the network side equipment;

the target RRC message and the RRC establishment complete message are sent in different MAC PDUs;

alternatively, in case of triggering the RRC connection recovery procedure, the method further includes:

sending an RRC recovery completion message and a target RRC message to the network side equipment;

12. The method of claim 11, wherein when the target RRC message and the RRC setup complete message are multiplexed in the same MAC PDU, the MAC PDU is configured to be at least one of:

the RRC establishment completion message is located after the target RRC message;

or alternatively, the process may be performed,

when the target RRC message and the RRC recovery complete message are multiplexed in the same MAC PDU, the MAC PDU is constructed as at least one of the following:

the RRC recovery complete message is located before the target RRC message;

the RRC resume complete message is located after the target RRC message.

13. The method of claim 1, wherein when the target RRC message is an RRC message related to configuration of the first transmission mode, the terminal has a need to send the target RRC message to the network side device if at least one of:

the terminal supports the transmission of a first transmission mode;

the network supports the transmission of a first transmission mode;

the size of a media access control protocol data unit (MAC PDU) containing the target RRC message is smaller than or equal to the maximum Transport Block Size (TBS) supported by the terminal based on the terminal type definition;

14. The method of claim 1, wherein the terminal has a need to send the target RRC message to the network side device when at least one of the following is satisfied when the target RRC message is an RRC message related to multicast broadcast service MBS count:

the terminal has MBS capability;

the network supports MBS;

the RRC layer of the terminal receives the control message related to MBS counting sent by the network equipment;

the terminal is receiving or interested in receiving at least one MBS service indicated in the MBS counting related control message.

15. The method of claim 1, wherein the terminal has a need to send the target RRC message to the network side device when at least one of the following is satisfied when the target RRC message is an RRC message related to the MBS interest indication:

the terminal has MBS capability;

The network supports MBS;

the terminal receives control information related to MBS service sent by network side equipment;

the terminal enters or leaves a service area;

MBS session starts or stops;

the content of the MBS interest indication message is changed;

16. 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 of the access layer security to be activated; the target RRC message is sent after the terminal enters an RRC connection state through a random access process under the condition that the terminal is in a non-RRC connection state and the requirement of sending the target RRC message exists;

the content generation of the target RRC message is triggered immediately when the terminal has a need of sending the target RRC message to the network side equipment, and before triggering an RRC connection establishment process or an RRC connection recovery process; alternatively, the content generation of the target RRC message is triggered during an RRC connection establishment procedure or an RRC connection recovery procedure.

17. The method of claim 16, wherein prior to the receiving the target RRC message from the terminal, the method further comprises:

receiving an RRC establishment request message sent by the terminal;

receiving an RRC establishment completion message sent by the terminal;

18. The method of claim 17, wherein when the target RRC message and the RRC setup complete message are multiplexed in the same MAC PDU, the MAC PDU is configured to be at least one of:

The RRC setup complete message is located after the target RRC message.

19. The method of claim 16, wherein prior to the receiving the target RRC message from the terminal, the method further comprises:

receiving an RRC restoration request message or an RRC restoration request 1 message sent by the terminal;

receiving an RRC recovery completion message sent by the terminal;

20. The method of claim 19, wherein when the target RRC message and the RRC restoration complete message are multiplexed in the same MAC PDU, the MAC PDU is configured to at least one of:

The RRC recovery complete message is located before the target RRC message;

the RRC resume complete message is located after the target RRC message.

21. The method of claim 16, wherein when the target RRC message is a configuration related RRC message of the first transmission mode, the method further comprises:

22. The method of claim 16, wherein when the target RRC message is an MBS count related RRC message, the method further comprises at least one of:

transmitting indication information for indicating that the network supports MBS to the terminal;

and sending the control message related to MBS counting to the terminal.

23. The method of claim 16, wherein when the target RRC message is an MBS interest indication related RRC message, the method further comprises at least one of:

and sending control information related to MBS service to the terminal.

24. A message transmission apparatus applied to a terminal, comprising:

the execution module is further configured to:

25. A message receiving apparatus applied to a network side device, comprising:

26. A communication device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the messaging method of any of claims 1 to 15 or the steps of the message receiving method of any of claims 16 to 23.

27. A readable storage medium, characterized in that the readable storage medium stores thereon a program or instructions, which when executed by a processor, implements the steps of the message sending method according to any of claims 1 to 15 or the steps of the message receiving method according to any of claims 16 to 23.