CN113905452A

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

Info

Publication number: CN113905452A
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: 2022-01-07
Anticipated expiration: 2040-07-06
Also published as: WO2022007786A1; CN113905452B

Abstract

The application discloses a message sending method, a message receiving method, a message sending device, a message receiving device and communication equipment, and belongs to the technical field of communication. The specific implementation scheme comprises the following steps: initiating a random access process under the condition that the terminal is in a non-RRC connected state and needs to send a target RRC message to network side equipment; when 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 stratum security needing to be activated. Therefore, the terminal can send the target RRC message after the RRC connection is successfully established or recovered without meeting other conditions for triggering the establishment or recovery of the RRC connection, and can send the target RRC message by initiating the random access process to enter an RRC connected state, so that the time delay is reduced.

Description

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

Technical Field

The present application belongs to the field of communication technology, and in particular, to a message sending method, a message receiving method, a device and a communication device.

Background

Currently, when there is a requirement that an access stratum security (activated AS security) RRC message that needs to be activated is sent to a network side device, a NON-Radio Resource Control (RRC) connected state (NON-RRCCONNECTED) terminal may send the RRC message only when other conditions (such AS mo-data) that trigger RRC connection establishment or recovery are satisfied and the RRC connection is successfully established or recovered. Therefore, the existing non-RRC connected terminal has a large delay when transmitting the RRC message.

Disclosure of Invention

An object of the embodiments of the present application is to provide a message sending method, a message receiving method, a device, and a communication device, so AS to solve the problem that a time delay is large when an existing non-RRC connected terminal sends an RRC message that requires activated AS security.

In order to solve the technical problem, the present application is implemented as follows:

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

initiating a random access process under the condition that the terminal is in a non-RRC connected state and needs to send a target RRC message to network side equipment;

when 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 stratum security needing to be activated.

In a second aspect, a message receiving method is provided, which is 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 stratum security needing to be activated; the target RRC message is sent after the terminal enters the RRC connection state through the random access process under the conditions that the terminal is in the non-RRC connection state and the requirement of sending the target RRC message exists.

In a third aspect, a message sending apparatus is provided, which is applied to a terminal, and includes:

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 needs to send a target RRC message to network side equipment;

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 transceiving module for receiving a target RRC message from a terminal;

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

In a sixth aspect, a network-side device is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method according to the second aspect.

In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the method according to the first aspect or implement 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 being coupled to the processor, the processor being configured to execute a program 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 this embodiment of the present application, a terminal may 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, and send the target RRC message after entering an RRC connected state through the random access procedure. Therefore, the terminal can send the target RRC message after the RRC connection is successfully established or recovered without meeting other conditions for triggering the establishment or recovery of the RRC connection, and can send the target RRC message by initiating the random access process to enter an RRC connected 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 by an embodiment of the present application;

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

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

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

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

fig. 6 is a schematic structural diagram of a message receiving apparatus 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 technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but 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 are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation)^thGeneration, 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-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, 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 a specific type of the Base Station is not limited.

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

In order to solve the problem of large time delay when the existing NON-RRC connected terminal (such AS NON-RRC connected UE) sends an RRC message requiring activated AS security, the embodiment of the present application provides a method for the NON-RRC connected UE to enter an RRC connected state (RRC connected UE) by initiating a random access procedure to send a target RRC message when the NON-RRC connected UE needs to send the RRC message requiring activated AS security to a network side device.

In this 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 activated AS security required RRC message.

1. Optionally, 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 send the target RRC message to the network side device when at least one of the following conditions is satisfied:

the terminal supports the transmission of the first transmission mode;

the network supports the transmission of the first transmission mode; such as the inclusion of a corresponding indication in the system message;

the Size of a Media Access Control Protocol Data Unit (MAC PDU) containing a target RRC message is less than or equal to the maximum Transport Block Size (TBS) supported by the terminal defined based on the terminal type;

the terminal satisfies at least one of the following: the configuration of the first transmission mode is interested, the configuration of the first transmission mode is not interested any more, and the configuration of the first transmission mode needs to be updated.

It should be noted that the first Transmission mode may be understood as a Transmission mode similar to a Preconfigured Uplink Resource (PUR) Transmission or a Preconfigured PUSCH Resource Transmission for Small Data Transmission (SDT), and may also be understood as a PUR Transmission mode or a Preconfigured PUSCH Resource Transmission for SDT in some cases, which is not limited to this. In this case, the target RRC message may include assistance information related to the configuration of the preconfigured PUSCH resource, such as a PURConfigurationRequest message. Taking a pre-configured PUSCH resource transmission mode for small data transmission as an example, the UE needs to send the target RRC message to the network side device when at least one of the following conditions is met:

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

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

the size of the MAC PDU containing the target RRC message is less than or equal to the maximum supported TBS of the UE defined based on the UE category

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

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

the terminal has MBS capability;

the network supports MBS; such as the inclusion of a corresponding indication in the system message;

the size of the MAC PDU containing the target RRC message is less than or equal to the maximum TBS supported by the terminal and is defined based on the terminal type;

the RRC layer of the terminal receives the MBS count related control message (e.g., MBSCountingRequest message) sent by the network side device;

the terminal is receiving or is 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 mbsinterrestindication message. In this case, the terminal has a need to send the target RRC message to the network side device when at least one of the following conditions is satisfied:

the terminal has MBS capability;

the terminal receives the control information related to the MBS service sent by the 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 a service area; for example, the first UE enters the service area (uplink entering the service area), or the first UE leaves the service area;

MBS session (session) start or stop; for example, MBS session starts 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 changes.

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

The following describes in detail a message sending method and a message receiving method according to an embodiment of the present application with reference to the accompanying drawings.

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

step 201: and under the condition that the terminal is in a non-RRC connected state and needs to send a target RRC message to network side equipment, initiating a random access process.

In this embodiment, the target RRC message is an RRC message that requires activated AS security. The Random Access procedure may be selected as 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 when the terminal enters an RRC connection state through the random access process, sending a target RRC message.

It should be noted that, when the terminal enters the RRC connected state from the non-RRC connected state, the terminal may be implemented through an RRC connection establishment (or RRC connection establishment, or RRCSetup) procedure, or may be implemented through an RRC connection resume (or RRC connection resume) procedure. This is explained below.

The first condition is as follows: the terminal enters an RRC connected state through an RRC connection establishment process and sends a target RRC message after entering the RRC connected state. The specific process is as follows:

1. preparation phase

Once the RRC layer of the terminal has a need to send an RRC message (target RRC message) requiring activated AS security, the terminal triggers an RRC connection setup (RRCSetup) procedure to generate an RRC setup request message, submits the RRC setup request message to the bottom layer, and triggers 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, and the bottom layer here is a Protocol layer below the RRC layer, such as a Packet Data Convergence Protocol (PDCP), a Radio Link Control (RLC), and a MAC layer.

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

multiplexing the existing EstableshmentCause values, such as mo-data, mo-signal and the like;

secondly, the newly set EstableshmentCause value is at least any one of the following values:

→ the newly set value of the instancementcause is irrelevant to the target RRC message, i.e. unifying all the target RRC messages, such as MO-RRCmessage, and setting the value of the instancementcause to MO-RRCmessage; the independence of the target RRC message can be the independence of the type or the form of the message of the target RRC message or the independence of the content of the target RRC message;

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

2) In the rrc setup procedure, the terminal may further perform at least one of the following:

firstly, checking of Unified Access Control (UAC) is not carried out, and an Access attempt is directly allowed;

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

checking UAC by new access type and/or access label. Namely, the UAC is checked by using the newly set Access category and/or Access identity (ies), and the UAC is at least any one of the following:

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

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

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

firstly, once a terminal has a requirement for 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 authorization process;

and triggering an RRC connection assignment process once the terminal has a requirement for sending the target RRC message to the network side equipment, and triggering generation of the target RRC message content in the RRC connection assignment process. Further, the triggering of the generation of the target RRC message content in the RRC connection establishment procedure may include at least one of:

→ in the Initiation phase (Initiation) of the RRC connection initialization procedure, triggering the generation of the content of the target RRC message;

→ in the operation procedure (Actions related to transmission of RRC setup request message) related to RRC setup request message transmission, triggering generation of the content of the target RRC message;

→ after the terminal receives the RRC establishment message (Reception of the RRC establishment by the UE) and before the content of the RRC establishment complete (RRCSetupcomplete) message is generated, triggering the generation of the content of the target RRC message;

→ in the process of generating the content of the RRC setup complete message after the terminal receives the RRC setup message, trigger the generation of the content of the target RRC 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;

→ after the terminal successfully sends the RRC setup complete message to the network side device, the generation of the content of the target RRC message is triggered.

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: variables, arrays, constructs, and the like. That is, after the content of the target RRC message is generated, the terminal may store it using any mathematical expression form, such as a variable, an array, and/or a structure.

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

5) The RRC layer of the terminal may generate an RRCsetupRequest message with the establishmencause as a 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 the MAC PDU with the RRCSetupRequest message to the physical layer and sends it to the network side device. The terminal successfully completes RACH and receives RRC establishment (RRCSetup) message sent by the network side equipment, and triggers the submission of target RRC message to the bottom layer.

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

multiplexing the existing trigger events; such as Initial access from RRC _ IDLE;

the newly set trigger event is at least any one of the following events:

→ independent of the target RRC message, i.e. unify all target RRC messages, such as MO-RRCmessage. The independence from the target RRC message can be independent from the message type or form of the target RRC message or independent from the content of the target RRC message.

→ related to the target RRC message, such as transmission of a separate target RRC message as a trigger event, such as a PUR configuration request message, an MBSCountingResponse message, an mbsinterentindication message, etc. The association with the target RRC message may be with the message type or form of the target RRC message or with the content of the target RRC message.

7) For the point in time that triggers the submission of the target RRC message to the underlay, at least one of the following may be used:

after a terminal receives an RRC establishment message (of the RRC establishment by the UE) and before the content of an RRC establishment completion (RRCSetupcomplete) message is generated, triggering and submitting a 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, triggering and submitting the target RRC message to the bottom layer;

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

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

3. Sending phase

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

Optionally, at least one of the following relationships may exist between the RRC establishment complete message and the target RRC message:

the content of the target RRC message is a part of the content of the RRC setup complete message, and the target RRC message is sent as a part of the RRC setup complete message. That is, in this case, the terminal only sends the RRC setup complete message, and only one RRC message is sent to the network side device. In addition to this, the content of the target RRC message may be in its 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.

Multiplexing a target RRC message and an RRC establishment completion message in the same MAC PDU for transmission; at least any one of the following:

the → RRC setup complete message precedes the target RRC message; in other words, it may be: the RRC establishment completion message is positioned in front of the MAC PDU, and the target RRC message is positioned behind the MAC PDU;

the → RRC setup complete message is located after the target RRC message; in other words, it may be: the target RRC message is located at the front within the MAC PDU and the RRC setup complete message is located at the back within the MAC PDU.

The target RRC message and the RRC establishment completion message are sent in different MAC PDU, namely are not multiplexed 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 sent to the network side equipment, and the target RRC message is carried by the latter MAC PDU and sent to the network side equipment;

the → target RRC message is carried by the previous MAC PDU and sent to the network side device, and the RRC setup complete message is carried by the next MAC PDU and sent to the network side device.

Case two: the terminal enters an RRC connected state through an RRC connection recovery process and sends a target RRC message after entering the RRC connected state. The specific process is as follows:

1. preparation phase

Once the RRC layer of the terminal has a need to send an RRC message (target RRC message) requiring activated AS security, the terminal triggers an RRC connection recovery (rrcrusum) procedure to generate an RRC recovery request or an RRC recovery request1 message, submits the RRC recovery request or the RRC recovery request1 message to the bottom layer, and triggers generation of the content of the target RRC message. It is understood that the RRC recovery request or the RRC recovery request1 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 a Packet Data Convergence Protocol (PDCP), a Radio Link Control (RLC), and a MAC layer.

1) In the rrcreesume process, the terminal may set a resume cause resumecuse value, which is at least any one of the following:

multiplexing the existing ResumeCalase values, such as mo-data, mo-signal and the like;

secondly, the newly set ResumeCoose value is at least any one of the following values:

→ the newly set ResumeCoose value is irrelevant to the target RRC message, i.e. unifying all target RRC messages, such as MO-RRCmessage, and setting the ResumeCoose value as MO-RRCmessage; the independence of the target RRC message can be the independence of the type or the form of the message of the target RRC message or the independence of the content of the target RRC message;

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

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

firstly, once a terminal has a requirement for 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 resume process;

and triggering an RRC connection resume process once the terminal has a requirement for sending the target RRC message to the network side equipment, and triggering generation of the content of the target RRC message in the RRC connection resume process. Further, the triggering of the generation of the target RRC message content in the RRC connection resume procedure may include at least one of:

→ in the Initiation phase (Initiation) of the RRC connection resume procedure, the generation of the content of the target RRC message is triggered;

→ in the operation procedure (Actions related to RRC recovery request or RRC recovery request1 message transmission 1 message), trigger the generation of the content of the target RRC message;

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

→ in the process of generating the content of the RRC recovery complete message after the terminal receives the RRC recovery message, trigger the generation of the content of the target RRC message;

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

→ after the terminal successfully sends the RRC recovery complete message to the network side device, the generation of the content of the target RRC message is triggered.

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

5) The RRC layer of the terminal may generate RRCResumeRequest/RRCResumeRequest1 messages with resumeues as corresponding values and submit 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 the MAC PDU with RRCResumeRequest/RRCResumeRequest1 message to the physical layer and sends it to the network side device. The terminal successfully completes RACH and receives an RRC recovery (RRCResume) message sent by the network side equipment, and triggers the submission of a target RRC message to the bottom layer.

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

multiplexing the existing trigger events; such as Transition from RRC _ INACTIVE, etc.;

the newly set trigger event is at least any one of the following events:

after a terminal receives an RRC recovery message (Reception of the RRCResu by the UE) and before the content of an RRC recovery completion (RRCResuComplete) message is generated, triggering and submitting a 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, triggering and submitting the target RRC message to the bottom layer;

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

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

3. Sending phase

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

Optionally, at least one relationship between the RRC recovery complete message and the target RRC message may be as follows:

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 transmitted as a part of the RRC recovery complete message. In other words, in this case, the terminal only sends the RRC recovery complete message, and only one RRC message is sent to the network side device. In addition to this, the content of the target RRC message may be in its 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.

Multiplexing the target RRC message and the RRC recovery completion message in the same MAC PDU for transmission; at least any one of the following:

the → RRC recovery complete message precedes the target RRC message; in other words, it may be: the RRC recovery completion message is positioned in front of the MAC PDU, and the target RRC message is positioned behind the MAC PDU;

the → RRC recovery complete message is located after the target RRC message; in other words, it may be: the target RRC message is located at the front within the MAC PDU and the RRC recovery complete message is located at the back within the MAC PDU.

The target RRC message and the RRC recovery completion message are sent in different MAC PDU, namely are not multiplexed 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 sent to the network side equipment, and the target RRC message is carried by the latter MAC PDU and sent to the network side equipment;

the → target RRC message is carried by the previous MAC PDU and sent to the network side device, and the RRC recovery complete message is carried by the next MAC PDU and sent to the network side device.

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

Example one

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

step 30: a preparation phase.

Once the RRC layer of the UE has a need to send an RRC message (target RRC message) requiring AS security, the UE triggers RRCResume procedure, generates RRCResumeRequest/RRCResumeRequest1 message and submits it to the bottom layer.

→ UAC related settings: setting the Access category to 11 and the Access identity to 0, executing the UAC and passing the UAC check, namely the Access attempt is allowed.

→ set ResumeCasse value RRCRESUMCasse is set MO-RRCmessage.

→ generation and submission of rrreesemequest/rrreesemequest 1 messages to the bottom layer: for example, the RRC layer of the UE generates RRCRESUMeRequest/RRCRESUMeRequest1 message with the ResumeHease value MO-RRCmessage, and submits the message 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 amble, to the base station gNB.

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

Step 33: the MAC layer of the UE sends the MAC PDU including the RRCRESUMeRequest/RRCRESUMeRequest1 message to the gNB via Msg 3.

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

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

Optionally, in a process that the RRC layer of the UE generates the content of the RRCResumeComplete message, triggering generation of a target RRC message (for example, an MBSCountingResponse message), and taking the content of the target RRC message as a part of the content of the RRCResumeComplete message; the RRCResumeComplete message is submitted to the bottom layer. After that, the UE sends an 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: a preparation phase.

→ set ResumeCasse value RRCRESUMCasse is set MO-RRCmessage.

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

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

Optionally, the RRC layer of the UE generates a content of the RRCResumeComplete message and submits the RRCResumeComplete message to the bottom layer; after submitting the RRCResumeComplete message to the underlying layer, generation of a target RRC message (such as an MBSCountingResponse message) is triggered immediately and submitted to the underlying layer. And then, multiplexing the RRCRESUMeComplete message and the target RRC message in one MAC PDU by the UE MAC layer, submitting the MAC PDU to the physical layer, and sending the MAC PDU to the gNB.

It should be noted that, in the message sending method provided in the embodiment of the present application, the execution main body may be a message sending apparatus, or a control module in the message sending apparatus for executing the message sending method. The message sending device provided in the embodiment of the present application will be described by taking an example in which the message sending device executes a message sending method.

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

an executing 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 executing module 41 is further configured to execute 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 request1 message, and submitting the RRC recovery request or the RRC recovery request1 message to a bottom layer;

triggering generation of content of the target RRC message.

Optionally, the message sending apparatus 40 further includes:

a setting module, configured to set an establishmencause value in the RRC connection establishment process; wherein the EstableshmentCause value is at least one of:

multiplexing the existing EstableshmentCause value;

a newly set EstableshmentCause value; wherein the newly set Establessmentause value is not related to the target RRC message, or the newly set Establessmentause value is related to the target RRC message;

or, in the RRC connection recovery process, setting a ResumeHease value; wherein the ResumeCoose value is at least one of:

multiplexing the existing resumecuse values;

the newly set resumecuse value; wherein the newly set ResumeCalase value is not related to the target RRC message or the newly set ResumeCalase value is related to the target RRC message.

Optionally, in 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:

the UAC is not checked in a unified access control mode;

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

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

Optionally, the executing module 41 is further configured to execute at least one of:

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 then triggering an RRC connection establishment process or an RRC connection recovery process;

when the terminal has a requirement of sending a target RRC message to network side equipment, triggering an RRC connection establishment process, and triggering generation of the content of the target RRC message 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, in the RRC connection establishment procedure, execute at least one of the following:

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;

after the terminal receives the RRC establishment message and before the content of the RRC establishment completion message is generated, 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, triggering the generation of the content of the target RRC message;

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

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

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

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 in the process of generating the content of the RRC recovery completion message, triggering the generation of the content of the target RRC message;

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

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

Optionally, the message sending apparatus 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 comprises at least one of:

variables, arrays, constructs.

Optionally, the executing 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;

or, the content in the target RRC message is not set as part of the content of the RRC setup complete message or the RRC recovery complete message.

Optionally, the trigger 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 triggering event is not related to the target RRC message, or the newly set triggering 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 an RRC establishment message sent by the network side 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 the RRC connection establishment procedure, the executing module 41 is further configured to execute at least one of the following:

after the terminal receives the RRC establishment message and before the content of the RRC establishment completion message is generated, triggering and submitting 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, triggering and submitting the target RRC message to a bottom layer;

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

and after the RRC establishment completion message is successfully sent to the network side equipment, triggering and submitting the target RRC message to a bottom layer.

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

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

after the terminal receives the RRC recovery message and before the content of the RRC recovery completion message is generated, triggering and submitting 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, triggering and submitting the target RRC message to a bottom layer;

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

and after the RRC recovery completion message is successfully sent to the network side equipment, triggering and submitting the target RRC message to a bottom layer.

Optionally, in the case of triggering an RRC connection establishment 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 at least one of the following relationships exists between the target RRC message and the RRC establishment completion 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 establishment complete message are sent in different MAC PDUs.

Optionally, in the case of triggering the 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 at least one of the following relationships exists 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;

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

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

The message sending device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

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 (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The message sending apparatus 40 provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in fig. 2, and achieve the same technical effect, and for avoiding repetition, details are not described here again.

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, and as shown in fig. 5, 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 process may be received, and the terminal does not need to send the target RRC message until the RRC connection is successfully established or restored without meeting other conditions for triggering establishment or restoration of the RRC connection, so as to reduce the time delay. Furthermore, resource waste, energy consumption and the like can be avoided.

Optionally, before receiving the target RRC message 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;

while receiving the target RRC message from the terminal, the method further comprises the following steps:

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 as at least one of the following:

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

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

receiving an RRC recovery request or an RRC recovery request1 message sent by the terminal;

after the RRC connection with the terminal is recovered, 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 recovery complete message are multiplexed in the same MAC PDU, the MAC PDU is configured as at least one of the following:

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

the RRC recovery 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 indicating that the network supports 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 the following:

sending indication information 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 the MBS counting to the terminal.

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

sending 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 main 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 apparatus is taken as an example to execute a message receiving method, and the message receiving apparatus provided in the embodiment of the present application is described.

Referring to fig. 6, 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 a 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 the configuration of the transmission of the first transmission mode, sending indication information indicating that the network supports the transmission of the first transmission mode to the terminal;

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

or, when the target RRC message is an RRC message related to MBS interest indication, sending indication information 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 the embodiment of the present application can implement each process implemented by the method embodiment shown in fig. 5, and achieve the same technical effect, and for avoiding repetition, details are not described here again.

Optionally, as shown in fig. 7, an embodiment of the present application further provides a communication device 70, which includes a processor 71, a memory 72, and a program or an instruction stored in the memory 72 and executable on the processor 71, for example, when the communication device 70 is a terminal, the program or the instruction is executed by the processor 71 to implement the processes of the foregoing message sending method embodiment, and the same technical effect can be achieved. When the communication device 70 is a network-side device, the program or the instructions are executed by the processor 71 to implement the processes of the above-mentioned message receiving method embodiment, and the same technical effect can be achieved, and for avoiding repetition, the details are not described here again.

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

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

Those skilled in the art will appreciate that the terminal 800 may further include a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to the processor 810 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through 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 those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that in the embodiment of the present application, the input Unit 804 may include a Graphics Processing Unit (GPU) 8041 and a microphone 8042, and the Graphics Processing Unit 8041 processes image data of a still picture or a video obtained by an image capturing device (such as 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. A touch panel 8071, also referred to as a touch screen. The touch panel 8071 may include two portions of 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, and a joystick, which are not described in detail herein.

In the embodiment of the present application, the radio frequency unit 801 receives downlink data from a network side device, and then processes the downlink data to the processor 810; in addition, the uplink data is sent to the network side equipment. In general, 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.

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, an application program or instruction (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 can include a high-speed random access Memory, and can also include a nonvolatile Memory, wherein the nonvolatile Memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable PROM (EPROM), an Electrically Erasable Programmable ROM (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.

Processor 810 may include one or more processing units; alternatively, the processor 810 may integrate an application processor, which primarily handles operating systems, user interfaces, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into 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 a network side device; the target RRC message is an RRC message of the access stratum security needing 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 the embodiment of the present application can implement each process implemented by the method embodiment shown in fig. 2, and achieve the same technical effect, and for avoiding repetition, details are not described here again.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 9, the network-side device 900 includes: antenna 91, radio frequency device 92, baseband device 93. The antenna 91 is connected to a radio frequency device 92. In the uplink direction, the rf device 92 receives information via the antenna 91 and sends 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 information to the rf device 92, and the rf device 92 processes the received information and transmits the processed information through the antenna 91.

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

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

The baseband device 93 may further include a network interface 96 for exchanging information with the radio frequency device 92, for example, a Common Public Radio Interface (CPRI).

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 95 and capable of being executed on the processor 94, and the processor 94 calls the instructions or programs in the memory 95 to execute the method executed by each module shown in fig. 6, and achieve the same technical effect, and are not described herein in detail to avoid repetition.

The embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing message sending method embodiment or implements each process of the foregoing message receiving method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

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

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above message sending method embodiment or each process of the above message receiving method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

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

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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network-side device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A message sending method is applied to a terminal and is characterized by comprising the following steps:

initiating a random access process under the condition that the terminal is in a non-Radio Resource Control (RRC) connection state and a requirement for sending a target RRC message to network side equipment exists;

2. The method of claim 1, further comprising:

triggering generation of content of the target RRC message.

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

setting an establishment cause EstablementCause value;

wherein the EstableshmentCause value is at least one of:

multiplexing the existing EstableshmentCause value;

or,

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

setting a recovery reason ResumeCoose value;

wherein the ResumeCoose value is at least one of:

multiplexing the existing resumecuse values;

4. The method according to claim 2, wherein in the RRC connection establishment procedure or the RRC connection recovery procedure, the method further comprises at least one of:

the UAC is not checked in a unified access control mode;

5. The method of claim 2, wherein the triggering of the generation of the content of the target RRC message comprises at least one of:

6. The method according to claim 5, wherein the triggering the generation of the content of the target RRC message during the RRC connection setup procedure comprises at least one of:

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

or,

the triggering, in the RRC connection recovery procedure, generation of the content of the target RRC message includes at least one of:

7. The method of claim 2, further comprising:

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.

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

variables, arrays, constructs.

9. The method of claim 7, further comprising:

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

multiplexing existing trigger events;

11. The method according to claim 2, wherein in case of triggering an RRC connection establishment procedure, after the initiating a random access procedure, the method further comprises:

sending a media access control protocol data unit (MAC PDU) including the RRC establishment request message to network side equipment; successfully completing random access and receiving an RRC establishment message sent by the network side equipment; triggering and submitting the target RRC message to a bottom layer;

or,

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

sending the MAC PDU comprising the RRC recovery request or the RRC recovery request1 message to network side equipment; successfully completing random access and receiving an RRC recovery message sent by the network side equipment; and triggering the target RRC message to be submitted to the bottom layer.

12. The method of claim 11, wherein in case of triggering an RRC connection establishment procedure, the triggering a submission of the target RRC message to an underlying layer comprises at least one of:

after the RRC establishment completion message is successfully sent to the network side equipment, triggering and submitting the target RRC message to a bottom layer;

or,

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

13. The method according to claim 11, wherein in case of triggering RRC connection establishment 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 completion 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;

14. The method of claim 13, 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 complete message is located after the target RRC message;

or,

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

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

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

15. The method according to claim 1, wherein when the target RRC message is an RRC message related to configuration of the first transmission scheme, the terminal has a requirement for sending the target RRC message to a network side device when at least one of the following conditions is met:

the terminal supports transmission of a first transmission mode;

the network supports the transmission of the first transmission mode;

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

the terminal satisfies at least one of the following conditions: the configuration of the first transmission mode is interested, the configuration of the first transmission mode is not interested any more, and the configuration of the first transmission mode needs to be updated.

16. The method according to claim 1, wherein when the target RRC message is an RRC message related to MBS count, the terminal has a requirement for sending the target RRC message to the network side device when at least one of the following conditions is met:

the terminal has MBS capability;

the network supports MBS;

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

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

17. The method according to claim 1, wherein when the target RRC message is an RRC message related to MBS interest indication, the terminal has a requirement for sending the target RRC message to the network side device when at least one of the following conditions is satisfied:

the terminal has MBS capability;

the network supports MBS;

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

the terminal enters or leaves a service area;

MBS session start or stop;

the content of the MBS interest indication message is changed;

18. A message receiving method is applied to network side equipment, and is characterized by comprising the following steps:

receiving a target RRC message from a terminal;

19. The method of claim 18, wherein prior to 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;

20. The method of claim 19, 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 complete message is located after the target RRC message.

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

receiving an RRC recovery completion message sent by the terminal;

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

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

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

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

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

sending indication information indicating that the network supports MBS to the terminal;

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

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

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

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

27. A message receiving device applied to a network side device is characterized by comprising:

28. A communications device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the message sending method of any one of claims 1 to 17 or implementing the steps of the message receiving method of any one of claims 18 to 25.

29. A readable storage medium, on which a program or instructions are stored, which when executed by a processor, carry out the steps of the message sending method according to any one of claims 1 to 17, or carry out the steps of the message receiving method according to any one of claims 18 to 25.