WO2024124543A1

WO2024124543A1 - Information transmission methods and apparatuses, device and storage medium

Info

Publication number: WO2024124543A1
Application number: PCT/CN2022/139651
Authority: WO
Inventors: 尤心; 林雪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-12-16
Filing date: 2022-12-16
Publication date: 2024-06-20

Abstract

The present application relates to the technical field of communications. Disclosed are information transmission methods and apparatuses, a device and a storage medium. A method is executed by a terminal, and the method comprises: sending RRC resume cause information to a network device, wherein the resume cause information is used for notifying the network device of the service type of the terminal (302).

Description

Information transmission method, device, equipment and storage medium

Technical Field

The present application relates to the field of communication technology, and in particular to an information transmission method, device, equipment and storage medium.

Background technique

Small data transmission (EDT) involves two types of small data transmission: Mobile Originated Small Data Transmission (MO-SDT) and Mobile Terminated Small Data Transmission (MT-SDT). Among them, MO-SDT is triggered by the terminal side, and MT-SDT is triggered by the network device side.

Taking the MT-SDT triggered by the network as an example, the network informs the terminal through a paging message and carries the resume cause of MT-SDT in the RRC connection recovery process to indicate that the purpose of the RRC recovery request is to trigger MT-SDT. When the terminal autonomously generates the resume cause of MT-SDT after receiving the paging message, if a new service arrives at this time, a conflict of the resume cause will occur. At present, the solution to this conflict has not been discussed.

Summary of the invention

The embodiments of the present application provide an information transmission method, apparatus, device and storage medium, and provide a solution when conflicting recovery reasons occur. The technical solution is as follows:

According to one aspect of the present application, there is provided an information transmission method, which is executed by a terminal and includes:

Sending RRC recovery reason information to the network device;

The restoration reason information is used to inform the network device of the service type of the terminal.

According to one aspect of the present application, there is provided an information transmission method, which is performed by a network device and includes:

Receiving the recovery reason information of the radio resource control RRC sent by the terminal;

According to one aspect of the present application, there is provided an information transmission device, the device comprising:

A sending module, used for sending the recovery reason information of the radio resource control RRC to the network device;

A receiving module, used for receiving the recovery reason information of the radio resource control RRC sent by the terminal;

According to one aspect of the present application, a computer device is provided, the computer device comprising a memory and a processor;

At least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the information transmission method as described above.

According to one aspect of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is used to be executed by a processor to implement the information transmission method as described above.

According to one aspect of the present application, a chip is provided, which includes a programmable logic circuit and/or program instructions, and when an electronic device equipped with the chip is running, it is used to implement the information transmission method as described above.

According to one aspect of the present application, a computer program is provided. The computer program includes computer instructions, and the computer instructions are used to implement the information transmission method as described above.

According to one aspect of the present application, a computer program product is provided. The computer program product includes computer instructions. The computer instructions are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the information transmission method as described above.

The technical solution provided by the embodiments of the present application includes at least the following beneficial effects:

A solution is provided when a conflict occurs in the recovery reason, wherein the service type of the terminal is carried in the recovery reason information so as to inform the network device of the service type, so that the terminal and the network device can perform the RRC connection recovery process based on different service types to complete the processing of the corresponding service.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

FIG1 is a schematic diagram of a MO-EDT air interface process provided by an exemplary embodiment of the present application;

FIG2 is a schematic diagram of a MO-EDT process provided by an exemplary embodiment of the present application;

FIG3 is a flow chart of an information transmission method provided by an exemplary embodiment of the present application;

FIG4 is a flow chart of an information transmission method provided by an exemplary embodiment of the present application;

FIG5 is a flow chart of an information transmission method provided by an exemplary embodiment of the present application;

FIG6 is a flow chart of an information transmission method provided by an exemplary embodiment of the present application;

FIG7 is a flow chart of an information transmission method provided by an exemplary embodiment of the present application;

FIG8 is a schematic diagram of an information transmission device provided by an exemplary embodiment of the present application;

FIG9 is a schematic diagram of an information transmission device provided by an exemplary embodiment of the present application;

FIG. 10 is a schematic diagram of the structure of a communication device provided by an exemplary embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application more clear, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

In Long Term Evolution (LTE), Small Data Transmission (EDT) has been introduced. In this process, the terminal may always remain in idle state, suspended state or inactive state to complete the transmission of small uplink and/or downlink data packets.

Schematically, EDT involves two types of small data transmission initiated by the terminal (Mobile Originated Small Data Transmission, MO-SDT) and small data transmission received by the terminal (Mobile Terminated Small Data Transmission, MT-SDT). Among them, MO-SDT is triggered by the terminal side, and MT-SDT is triggered by the network device side.

The following describes the above two SDTs:

MO-EDT is an EDT process initiated by the terminal. The network device includes the maximum number of transport blocks (Transport Block size, TB size) allowed by MO-EDT in the system broadcast message. The terminal determines the amount of data to be transmitted. If it is less than the maximum TB size of the broadcast, the terminal initiates the EDT process. Otherwise, the terminal initiates the normal connection establishment process and enters the connected state to transmit data.

FIG1 shows a schematic diagram of the MO-EDT air interface process provided by an exemplary embodiment of the present application. Among them, MO-EDT is implemented based on a random access process, and the terminal uses the uplink grant (UL grant) obtained in the random access response (Random Access Response, RAR) to transmit uplink data. The network device allocates random access resources dedicated to MO-EDT to the terminal to distinguish whether the current random access process is triggered by MO-EDT, thereby allocating a larger number of UL grants for data transmission through RAR. Subsequently, the terminal makes a Radio Resource Control (RRC) connection recovery request, and the network device releases the RRC connection to implement MO-SDT.

MT-EDT is an EDT process initiated by network equipment and implemented by the Mobile Management Entity (MME), which is the key control node for accessing the network.

FIG. 2 shows a schematic diagram of a MO-EDT process provided by an exemplary embodiment of the present application.

When the downlink data for a certain terminal reaches the Serving Gateway (S-GW), the S-GW informs the MME of the data volume information, that is, the S-GW sends the downlink data size information (DL date size info) to the MME. Subsequently, the MME instructs the network device to initiate paging to find the target terminal, and the paging message is sent to the terminal through the MME and the network device in turn. Among them, the paging message carries the downlink data size information and/or MT-SDT indication information. After receiving the paging message, the terminal confirms whether it contains the corresponding terminal identification and MT-EDT indication information; if it does, the terminal initiates the MO-EDT process to respond to the paging on the network side.

Among them, the MO-EDT initiated during the MT-EDT process is different from the MO-EDT process in the following ways:

-The terminal uses the legacy Random Access Channel (legacy RACH) resources to initiate random access, i.e., does not use the random access resources dedicated to MO-EDT;

-ResumeCause is MT-EDT, which is used to inform the network device of the purpose of the current connection establishment;

-The network device side can further determine whether to instruct the terminal to enter the connected state through the pending data indication (Pending Data Indication) sent by the core network; wherein the pending data indication is used to inform the network device whether there is further downlink data transmission demand.

In some embodiments, only one uplink/downlink data transmission is supported during the EDT process.

In the 5th Generation Mobile Communication Technology (5G) New Radio (NR) system, MO-SDT and MT-SDT are as follows:

In the 5G NR system, there are three RRC states: RRC idle state (RRC_IDLE), RRC inactive state (RRC_INACTIVE), and RRC connected state (RRC_CONNECTED). Among them, the RRC inactive state is a new state introduced by the 5G system from the perspective of energy saving. For terminals in the RRC inactive state, the radio bearer and all radio resources will be released, but the terminal side and the network device side retain the terminal access context to quickly restore the RRC connection. The network device usually keeps the terminal with infrequent data transmission in the RRC inactive state.

In some embodiments, a terminal in an RRC inactive state does not support data transmission. When uplink or downlink data arrives, the terminal needs to restore the RRC connection and be released to the RRC inactive state after the data transmission is completed. For terminals with small data volumes and low transmission frequency, such a transmission mechanism will result in unnecessary power consumption and signaling overhead.

Therefore, small data transmission technology is introduced to support the terminal to transmit a small amount of data in the RRC inactive state. For the SDT process triggered by the arrival of uplink data/signaling, namely MO-SDT, the specific triggering conditions include:

- The uplink data and/or signaling to be transmitted belongs to a radio bearer that is allowed to trigger SDT, such as a signaling radio bearer (SRB) or a data radio bearer (DRB);

-The amount of uplink data to be transmitted is less than the pre-configured data volume threshold of the network device;

- The downlink reference signal received power (Reference Signal Receiving Power/Reference Signal Received Power, RSRP) measurement result is greater than the RSRP threshold pre-configured by the network device;

-There are valid SDT resources, for example, Random Access-SDT (RA-SDT) resources and/or Configured Grant-SDT (CG-SDT) resources.

For the SDT (MT-SDT) process triggered by the network side, the research goal in the related art is to specify the support for paging-triggered SDT (MT-SDT), including:

MT-SDT triggering mechanism for UEs in RRC_INACTIVE, supporting RA-SDT and CG-SDT as the UL response;

MT-SDT procedure for initial DL data reception and subsequent UL/DL data transmissions in RRC_INACTIVE.

Schematically, after the network device triggers MT-SDT, it sends the MT-SDT indication to the terminal through a paging message, and the terminal initiates the MT-SDT process after receiving the indication. Among them, the terminal triggers the RRC resume process and carries the cause value (resume cause value) corresponding to the MT-SDT resumption reason to indicate that the purpose of the current RRC resume request of the network device is to trigger the MT-SDT process.

When the terminal autonomously generates the restoration reason of MT-SDT after receiving the paging message, if a new service arrives at this time, a restoration reason conflict will occur. Currently, the solution to this conflict has not been discussed.

FIG3 shows a flow chart of an information transmission method provided by an exemplary embodiment of the present application. The method is executed by a terminal and includes the following steps:

Step 102: Send RRC recovery reason information to the network device.

Illustratively, the restoration reason information is used to inform the network device of the service type of the terminal.

Referring to the above content, when the RRC connection recovery process is triggered, the terminal needs to report the MT-SDT recovery reason to the network device to indicate that the purpose of this RRC recovery request is to trigger MT-SDT. After the network device generates the recovery reason, there is a possibility that new services arrive, resulting in a conflict in the recovery reason.

Based on this, in order to avoid conflicts in the recovery reasons, the terminal can send RRC recovery reason information to the network device to indicate the service type of the terminal, so that the network device can clearly understand the purpose of the terminal initiating the RRC connection recovery process.

The restoration reason information carries a reason value corresponding to the restoration reason, and the reason value is used to indicate the service type of the terminal. Optionally, the service type of the terminal includes at least one of the following types:

Emergency type;

High Priority Access type;

MT-Access type;

MO-Signalling type;

MO-Data type;

MO-VoiceCall type;

MO-VideoCall type;

MO message (MO-Short Messaging Service, MO-SMS) type;

Radio Access Network-based Notification Area (RNA) update type, which can be represented as RNA-Update type;

Multimedia Priority Service (MPS) priority access type, which can be expressed as MPS-PriorityAccess type;

Modulation and Coding Scheme (MCS) priority access type, which can be expressed as MCS-PriorityAccess type;

MT-SDT type.

In some embodiments, the terminal also needs to determine restoration reason information.

The restoration reason information is determined at least according to a first restoration reason associated with the first service and a second restoration reason associated with the second service, the first restoration reason is used to indicate a service type of the first service, and the second restoration reason is used to indicate a service type of the second service. Optionally, the first restoration reason and the second restoration reason may constitute a restoration reason set. It can be understood that the terminal determines the restoration reason information based on the restoration reason set, and the restoration reason set includes at least the first restoration reason and the second restoration reason.

Optionally, the first service includes at least one of the following services: MT-SDT; MO-SDT; SDT.

Optionally, the second service includes at least one of the following services: emergency service; high priority access service; MT access service; MO signaling service; MO data service; MO voice call service; MO video call service; MO information service; MPS priority access service; MCS priority access service; RAN-based Notification Area update (RNAU) service; MO-SDT.

The service type of the second service includes at least one of the aforementioned multiple types.

In some embodiments, the service type of the emergency service is an emergency service type, and the second recovery reason associated with it can be marked as emergency. Similarly, the second recovery reason associated with the high priority access service can be marked as highPriorityAccess; the second recovery reason associated with the MT access service can be marked as MT-Access; the second recovery reason associated with the MO signaling service can be marked as MO-Signalling; the second recovery reason associated with the MO data service can be marked as MO-Data; the second recovery reason associated with the MO voice call service can be marked as MO-VoiceCall; the second recovery reason associated with the MO video call service can be marked as MO-VideoCall; the second recovery reason associated with the MO information service can be marked as MO-SMS; the second recovery reason associated with the MPS priority access service can be marked as MPS-PriorityAccess; the second recovery reason associated with the MCS priority access service can be marked as MCS-PriorityAccess; the second recovery reason associated with the RNAU service can be marked as RNA-Update; the second recovery reason associated with the MO-SDT can be marked as MT-SDT.

In some embodiments, the terminal determines the restoration reason information based on the priority of the first restoration reason and the second restoration reason. For example, if the priority of the second restoration reason is higher than the priority of the first restoration reason, the terminal generates the restoration reason information according to the second restoration reason, and the restoration reason information is used to indicate the service type corresponding to the second service.

In other embodiments, the terminal determines the recovery reason information based on the terminal implementation. The terminal implementation can be understood as the communication operator negotiating and determining the order of using the recovery reasons between different services; the terminal implementation can also be understood as the terminal determining according to its own communication needs. For example, if the importance level of the first service is higher than the importance level of the second service, the terminal generates the recovery reason information according to the first recovery reason, and the recovery reason information is used to indicate the service type corresponding to the first service.

In other embodiments, the terminal may also determine the recovery reason information based on the agreement of the communication protocol. The agreement of the communication protocol may be understood as the communication specification given by the standardization organization. For example, the first service is MT-SDT, and the second service is an emergency service. Based on the agreement in the communication protocol, the terminal generates the recovery reason information according to the recovery reason corresponding to the emergency service, and the recovery reason information is used to indicate the service type corresponding to the emergency service.

In some embodiments, the restoration reason information needs to be determined according to the triggering and arrival timing of the first service and the second service. Optionally, the restoration reason information is determined in any of the following situations (which can be understood as multiple scenarios for determining the restoration reason information):

The second service arrives before the first service is triggered;

After the first service is triggered and the first restoration reason has not yet been sent to the network device, the second service arrives;

After the first service is triggered and the first restoration reason has been sent to the network device, the second service arrives.

It can be understood that, when the RRC connection recovery process based on the first recovery reason has not been completed, the terminal can determine the recovery reason information so as to inform the network device of the service type. That is, when the first recovery reason generated according to the first service has not been sent to the network device (that is, the network device has not yet obtained the purpose of the RRC recovery request), or the first recovery reason has been sent to the network device (that is, the network device has obtained the purpose of the RRC recovery request but has not yet completed the RRC connection recovery process), if the terminal receives the second service, it can resend the recovery reason information to the network device.

According to the foregoing content, the first service and the second service include multiple types. In combination with the above scenarios, the restoration reason information can be implemented as any one of the following:

canceling the first service and confirming the first information, wherein the first information carries the second restoration reason;

Alternatively, the first service is triggered, and second information is determined, where the second information carries the first restoration reason and the second restoration reason.

It can be understood that the terminal can cancel the first service and give priority to processing the second service after restoring the RRC connection with the network device; or, the terminal can trigger the first service and carry the service types corresponding to the first service and the second service in the recovery reason information, so as to facilitate the processing of the first service and the second service after restoring the RRC connection with the network device.

Optionally, the first information includes RRC recovery request information. The RRC recovery request information can be implemented as RRCResumeRequest message or RRCResumeRequest1.

Optionally, the second information includes terminal assistance information (UE Assistance Information, UAI).

For example, the first service is MT-SDT and the second service is an emergency service. When the first service arrives, the terminal can generate the first restoration reason information according to the service type of the first service. Subsequently, the terminal can send it to the network device and perform the RRC connection restoration process to complete the processing of the first service.

In some embodiments, when the RRC connection recovery process has not been completed, there is a possibility that the second service arrives. According to the different arrival timings of the second service, two processing solutions are shown below:

The second service arrives before the first service is triggered.

Before the first resume cause information is sent, if the second service arrives, the terminal may replace the cause value in the first resume cause information with the cause value corresponding to the emergency service, that is, replace/set the resume cause value to emergency. Optionally, the terminal may also set the access category to the value corresponding to the emergency service. Before the first resume cause information is sent, it can be understood that the first resume cause information has been generated but not sent, or it can be understood that the first resume cause information has not been generated.

Referring to the above content, if the terminal triggers the MT-SDT service and carries the cause value of the emergency service in the UAI, the terminal can select the access category corresponding to the MT-SDT. Among them, the access category corresponding to the MT-SDT can reuse the value set in the relevant technology (0-9), or define some new values for it (values other than 0-9), which is not limited in this application.

The second service arrives after the first service is triggered.

Before the first restoration reason is sent, based on the arrival of the second service after the first service is triggered, the terminal can trigger the reporting of UAI, and carry the indication information that the second service has arrived in the UAI, that is, the network device is informed of the arrival of the emergency service through the UAI. Optionally, the UAI triggers the reporting after the first restoration reason information is successfully received by the network device.

In summary, the information transmission method provided in the embodiment of the present application provides a solution when the recovery reason conflicts. Specifically, the service type of the terminal is carried in the recovery reason information so as to inform the network device of the service type, so that the terminal and the network device can perform the RRC connection recovery process based on different service types to complete the processing of the corresponding service.

FIG4 is a flowchart of an information transmission method provided by an exemplary embodiment of the present application, the method is executed by a terminal, and includes the following steps:

Step 202: Receive RRC recovery reason information sent by the terminal.

The restoration reason information carries a reason value corresponding to the restoration reason, and the reason value is used to indicate the service type of the terminal. Optionally, the service type of the terminal includes at least one of the following types: emergency service type; high priority access type; MT access type; MO signaling type; MO data type; MO voice call type; MO video call type; MO information type; RNA-Update type; MPS-PriorityAccess type; MCS-PriorityAccess type; MT-SDT type.

In some embodiments, the terminal also needs to determine restoration reason information, wherein the restoration reason information is determined at least according to a first restoration reason associated with the first service and a second restoration reason associated with the second service, the first restoration reason is used to indicate the service type of the first service, and the second restoration reason is used to indicate the service type of the second service.

Optionally, the second service includes at least one of the following services: emergency service; high priority access service; MT access service; MO signaling service; MO data service; MO voice call service; MO video call service; MO information service; MPS priority access service; MCS priority access service; RNAU service; MO-SDT.

Among them, the specific process of determining the restoration reason can refer to the above content and will not be repeated here.

In some embodiments, the recovery reason information needs to be determined based on the triggering and arrival timing of the first service and the second service. Optionally, the recovery reason information is determined in any of the following situations: before the first service is triggered, the second service arrives; after the first service is triggered and the first recovery reason has not been sent to the network device, the second service arrives; after the first service is triggered and the first recovery reason has been sent to the network device, the second service arrives.

According to the foregoing content, the first service and the second service include multiple types. Combined with the above scenarios, the recovery reason information can be implemented as any one of the following: canceling the first service, determining the first information, and carrying the second recovery reason in the first information; or, triggering the first service, determining the second information, and carrying the first recovery reason and the second recovery reason in the second information.

Optionally, the first information includes RRC recovery request information, and the second information includes UAI.

FIG5 is a flowchart of an information transmission method provided by an exemplary embodiment of the present application, the method is executed by a terminal, and includes the following steps:

Step 302: The terminal sends RRC recovery reason information to the network device.

Optionally, resources used by the recovery request information include pre-configured Grant (CG) resources or random access (RA) resources.

It should be understood that in the embodiment of the present application, the steps on the terminal side can be implemented as an embodiment of the information transmission method, and the steps on the network device side can also be implemented as an embodiment of my information transmission method. The specific content can be referred to the above content and will not be repeated here.

Referring to the above content, based on the recovery reasons associated with different services, the terminal needs to first determine the recovery reason information and then send it to the network device, so as to inform the network device of the service type of the terminal, so that the network device can clearly know the purpose of the terminal initiating the RRC connection recovery process. Based on this, the network device will clearly know which service the terminal is based on to initiate the RRC connection recovery process, thereby effectively avoiding the problem of conflicting recovery reasons.

Based on FIG. 5 , FIG. 6 shows a flowchart of an information transmission method provided by an exemplary embodiment of the present application, which further includes step 3011, which is as follows:

Step 3011: The terminal determines the restoration reason information.

Illustratively, the restoration reason information is determined at least based on a first restoration reason associated with the first service and a second restoration reason associated with the second service, the first restoration reason is used to indicate a service type of the first service, and the second restoration reason is used to indicate a service type of the second service.

In some embodiments, the first restoration reason and the second restoration reason may constitute a restoration reason set. Optionally, step 3011 may be implemented as: the terminal determines restoration reason information based on the restoration reason set, and the restoration reason set includes at least the first restoration reason and the second restoration reason.

Referring to the above content, the first business and the second business include multiple types, as follows:

There are multiple implementations for the terminal to determine the restoration reason information based on the first restoration reason and the second restoration reason. Optionally, the restoration reason information is determined by at least one of the following methods:

Priority determination based on the first restoration reason and the second restoration reason;

For example, if the priority of the second restoration reason is higher than the priority of the first restoration reason, the terminal generates restoration reason information according to the second restoration reason, and the restoration reason information is used to indicate the service type corresponding to the second service.

Determined based on the terminal implementation.

Among them, terminal implementation can be understood as the communication operators negotiate and determine, and the communication operators negotiate and determine the order of use of recovery reasons between different services; terminal implementation can also be understood as the terminal determines according to its own communication needs. For example, if the importance level of the first service is higher than the importance level of the second service, the terminal generates recovery reason information according to the first recovery reason, and the recovery reason information is used to indicate the service type corresponding to the first service.

Determined based on the communication protocol.

The agreement of the communication protocol can be understood as the communication specification given by the standardization organization. For example, if the first service is MT-SDT and the second service is an emergency service, based on the agreement in the communication protocol, the terminal generates recovery reason information according to the recovery reason corresponding to the emergency service, and the recovery reason information is used to indicate the service type corresponding to the emergency service.

The second service arrives before the first service is triggered;

Referring to the above content, before sending the restoration reason information, there is a possibility that the second service arrives, such as the second service arrives before or after the first service is triggered. Based on this, according to different situations, the terminal needs to perform related processing steps.

Optionally, the information transmission method provided in the embodiment of the present application further includes:

The terminal sends UAI to the network device;

The UAI is sent when the recovery reason information is not sent and a second service arrives after the first service is triggered, and the UAI carries indication information of the arrival of the second service.

Taking the case where the first service is MT-SDT and the second service is an emergency service or MO data service as an example, the terminal may send UAI to indicate that the emergency service or MO data service has arrived. Optionally, when the recovery reason information is not sent and a burst service arrives after MT-SDT is triggered, the UAI carries the indication information of the arrival of the burst service. Optionally, when the recovery reason information is not sent and MO-SDT data (i.e., MO data) arrives after MT-SDT is triggered, the UAI carries the indication information of the arrival of the MO data service.

In some embodiments, the terminal first generates a first restoration reason associated with the first service, and before the first restoration reason is sent, the second service arrives after the first service is triggered. Based on this, the terminal reports UAI after the first restoration reason information is successfully received by the network device and triggered.

Optionally, the information transmission method provided in the embodiment of the present application further includes at least one of the following steps:

-Restore the radio bearer associated with MT-SDT;

-Resume the radio bearer associated with MO-SDT;

- Re-establish the Packet Data Convergence Protocol (PDCP) entity associated with the Radio Bearer (RB);

-Re-establish the Radio Link Control (RLC) entity associated with the RB;

- Generate new key information, the new key information is used for encryption and/or protection of data on the DRB, or the new key information is used for encryption and/or protection of signaling on the SRB;

-Continue the robust header compression (ROHC) function of DRB.

Among them, the new key information is generated based on the Network Control Center (NCC) stored in the context, and is used to implement encryption and/or integrity protection of data or signaling on DRB and SRB. Optionally, the ROHC function of continuing DRB is performed when the terminal currently accesses the cell that is the last cell providing service or the cell within the RNA range.

In some embodiments, the above steps are performed based on the second service arriving after the first service is triggered. For example, an emergency service or MO data service arrives after the MT-SDT is triggered. In the case where the second service is an MO data service, the radio bearer of the MO data does not belong to the radio bearer that allows the triggering of SDT, or the radio bearer of the MO data does not belong to the unlimited bearer of the MT-SDT that allows the triggering.

Optionally, when the restoration reason information is not sent and the second service arrives before the first service is triggered, in the information transmission method provided in the embodiment of the present application, the terminal further performs at least one of the following operations:

-Replace or set the cause value to the service type of the second service;

-Retain the service type of the first service with the cause value;

- Sending a first cause value and a second cause value, where the first cause value is a service type of the first service, and the second cause value is a service type of the second service;

- Send a new cause value, where the new cause value is the service type of the second service;

-Select to carry MO data or MT data according to a predefined priority order;

-Select to carry MO data or MT data according to the priority order indicated by the network device;

-When the resource used by the restoration cause information is a RA-SDT resource or a CG-SDT resource, the cause value is set to the service type of the second service;

- When the resource used by the restoration cause information is neither a RA-SDT resource nor a CG-SDT resource, the cause value is set to the service type of the first service.

The predefined priority order is determined according to the value of the access category. In some embodiments, the smaller the value of the access category, the higher the priority.

Taking the first service being MT-SDT and the second service being MO data as an example, the terminal may perform at least one of the following operations: replace or set the cause value to MO data; retain the cause value to MT-SDT; send the first cause value and the second cause value, the first cause value being MO data and the second cause value being MT-SDT; send a new cause value, the new cause value being SDT; choose to carry MO data or MT data according to a predefined priority order; choose to carry MO data or MT data according to the priority order indicated by the network device; when the resources used to restore the cause information are RA-SDT resources or CG-SDT resources, set the cause value to MO-SDT; when the resources used to restore the cause information are neither RA-SDT resources nor CG-SDT resources, set the cause value to MT-SDT.

In summary, in the information transmission method provided in the embodiment of the present application, the terminal can determine the recovery reason information based on at least the first recovery reason associated with the first service and the second recovery reason associated with the second service network, thereby providing an implementation scheme for resolving the conflict between the first recovery reason and the second recovery reason. It should be understood that the above embodiments all take the conflict between the first recovery reason and the second recovery reason as an example. If there is a third recovery reason associated with the third service, then similarly, the recovery reason information can be determined based on the first recovery reason, the second recovery reason and the third recovery reason, and the present application does not limit this.

Optionally, based on the difference between the triggering timing of the first service and the arrival timing of the second service, the embodiment of the present application also provides multiple optional execution steps of the terminal. For example, triggering UAI to report the indication information of the arrival of the second service, so that the network device knows that the second service has arrived, and then waits for the recovery reason information sent by the terminal.

Referring to the foregoing, the recovery request information is sent during the RRC connection recovery process. Based on this, the terminal needs to perform related operations of determining and/or sending the recovery request information based on the paging message sent by the network device. The following will describe in detail the related operations before the recovery request information is sent:

Based on FIG. 5 , FIG. 7 shows a flowchart of an information transmission method provided by an exemplary embodiment of the present application, further comprising step 3012a and step 3012b, and step 302 can be implemented as step 3021, specifically as follows;

Step 3012a: The network device sends a paging message to the terminal.

Illustratively, the paging message is used to indicate that downlink SDT data has arrived at the network device.

In some embodiments, the paging message carries the indication information of MT-SDT, which is used to instruct the terminal to restore the RRC connection. Based on this, the terminal can determine the restoration reason information according to the service type of the current service, and feed it back to the network device, so that the network device knows which service the terminal wants to perform the RRC connection restoration process based on.

Optionally, the paging message carries at least one of the following information:

Terminal identification;

MT-SDT resource configuration information;

Among them, the resource configuration information of MT-SDT includes at least one of the following information: resources used for RRC resume request (RRC resume request) or uplink feedback of downlink data; resources used for receiving downlink small data transmission (DownLink SDT, DL SDT) data.

Exemplarily, the resource configuration information is a contention-free random access (CFRA) resource configuration, including a synchronization signal block index (SSB index), a preamble index, and a physical random access channel mask index (PRACH mask index). In some embodiments, the network device activates one or more groups of preconfigured resources for uplink/downlink data transmission.

· Resource type indication information of MT-SDT.

The resource type indication information of MT-SDT includes at least one of the following information: resources used for uplink feedback of RRC recovery request or downlink data; resources used for receiving DL SDT data. Exemplarily, the resource type includes RA-SDT or CG-SDT or Semi-Persistent Scheduling (SPS).

Optionally, the indication information of MT-SDT is 1-bit indication information.

Step 3012b: The terminal evaluates the triggering condition of MT-SDT.

After receiving the paging message from the network device, the terminal may evaluate the triggering condition of the MT-SDT, so as to perform subsequent operations when the triggering condition of the MT-SDT is met.

Optionally, the triggering condition of MT-SDT includes at least one of the following conditions:

The paging message carries the terminal identification and MT-SDT association information;

The system resource block (SIB) carries the SDT indication information, which is used to indicate that the serving cell supports the SDT service.

The RRC release message carries the SDT configuration;

The uplink data to be transmitted is carried by the SDT bearer.

The amount of uplink data to be transmitted meets the quantity threshold;

The channel quality of the terminal meets the quality threshold;

Timing Advance (TA) is effective;

There are valid CG-SDT resources;

· There are valid RA-SDT resources;

There are valid SPS resources.

Among them, the SDT indication information includes SDT common configuration (SDT-ConfigCommon) or MT-SDT common configuration (MT-SDT-ConfigCommon); SDT configuration is used to indicate the resources used to transmit SDT data, the threshold value of the trigger condition, the timer length, etc.; TA is effectively used to indicate the uplink timing advance of the terminal in the service cell.

Step 3021: When the triggering condition of MT-SDT is met, the terminal sends RRC recovery reason information to the network device.

According to step 3012b, the terminal may determine whether to send the recovery reason information to the network device according to the evaluation result. In some embodiments, the recovery reason information may be implemented as RRC recovery request information. For example, the recovery reason information is RRCResumeRequest message or RRCResumeRequest1.

The terminal starts a timer, and the timer is used to indicate the duration between the MT-SDT triggering and the triggering failure. It can be understood that when the terminal sends the recovery reason information to the network device, the terminal can start the timer when the MT-SDT is triggered. If the timer times out, it is considered that the MT-SDT process has failed, so as to facilitate the subsequent failure maintenance of the MT-SDT process.

In summary, the information transmission method provided in the embodiment of the present application provides the relevant operations before the recovery request information is sent. Among them, the paging message sent by the network device to the terminal carries the indication information of MT-SDT, which is used to instruct the terminal to restore the RRC connection. Optionally, after receiving the paging message, the terminal evaluates the triggering conditions of MT-SDT, and its triggering conditions are associated with the resources involved in the MT-SDT process. Subsequently, when the triggering conditions of MT-SDT are met, the terminal sends the recovery reason information to the network device to inform the network device of the service type of the terminal.

Referring to the foregoing, in order to avoid conflicts between the recovery reasons of multiple services, the terminal may determine the recovery reason information based on the recovery reasons associated with at least two services (i.e., the first service and the second service in the foregoing). Since there are multiple service types in the terminal, several exemplary embodiments are given below:

Embodiment 1: Emergency service arrives before MT-SDT is triggered.

Step 1: The terminal in the RRC_inactive state receives a paging message sent by the network side.

The paging message indicates that downlink SDT data has arrived on the current network side. Optionally, the paging message may carry MT-SDT indication information to instruct the UE to restore the RRC connection. In some embodiments, the indication information may be 1-bit indication information, and the paging message specifically includes at least one of the following:

UE identification;

MT-SDT resource configuration information;

The resource configuration information may be a resource used for sending an RRC resume request or uplink feedback of downlink data, or a resource used for receiving DL SDT data. For example, the resource configuration information is a CFRA resource configuration, including an SSB index, a preamble index, and a PRACH mask index; and/or, activating one or more groups of preconfigured resources for uplink/downlink data transmission.

· Resource type indication information of MT-SDT.

The resource type indication information may be a resource used to send an RRC resume request or uplink feedback of downlink data, or a resource used to receive DL SDT data. For example, the resource type includes RA-SDT, CG-SDT, or SPS.

Step 2: After receiving the paging message, the terminal performs the trigger condition evaluation of MT-SDT.

Optionally, the triggering conditions of MT-SDT include at least one of the following: the paging message carries the terminal identification and the MT-SDT indication; the SIB carries the SDT indication information, the SDT indication information is used to indicate that the serving cell supports the SDT service, and the SDT indication information may specifically be SDT-ConfigCommon or MT-SDT-ConfigCommon; the RRC release message carries the SDT configuration; the uplink data to be transmitted is carried by the SDT bearer; the amount of uplink data to be transmitted meets the quantity threshold; the current channel quality of the terminal meets the quality threshold; the TA is valid; there are valid CG-SDT resources or RA-SDT resources or SPS resources.

Step 3: When the triggering condition of MT-SDT is met, the UE sends first restoration reason information to the network side, and the first restoration reason information is generated based on the first service (ie, the MT-SDT service).

Optionally, the first resumption reason information includes RRC resumption request information, which can be implemented as RRCResumeRequest message or RRCResumeRequest1 in some embodiments. The first resumption reason information carries a resumption reason value (resume cause value) for triggering RRC connection resumption, that is, the cause value in the aforementioned content, which is represented by the cause value of MT-SDT in the embodiment of the present application.

Optionally, the terminal starts a first timer.

In this embodiment, if an emergency service arrives before the terminal sends the first resumption reason information, the UE replaces/sets the resume cause value to emergency, and/or the terminal sets the access category to a value corresponding to emergency.

Exemplary:

1> If the resumption of the RRC connection is triggered due to an MT-SDT:

2>If an emergency service is ongoing:

3>Select '2' as the Access Category;

3>Set the resumeCause to emergency.

It should be understood that access category "2" is only an example and does not limit the present application.

Optionally, the terminal triggers the MT-SDT service and carries the cause value of emergency in the subsequent UAI. Based on this, if the cause value of MT-SDT is carried in the UAI, the terminal can select the Access Category (0-9) corresponding to MT-SDT. Exemplarily, the Access Category corresponding to MT-SDT can reuse an existing one (such as the same "0" as MT-access), or it can be a newly defined value, that is, other access category values other than 0-9.

Embodiment 2: After MT-SDT is triggered, emergency service arrives.

Among them, steps 1-3 can refer to the above content and will not be repeated here.

In this embodiment, the resource used by the first restoration reason information is a CG resource or a RA resource.

Optionally, before sending the first restoration reason information, the UE may further perform at least one of the following actions:

Restore the radio bearers (DRB and/or SRB) associated with MT/SDT and/or MO-SDT;

Re-establish the RB-associated PDCP/RLC entity;

Generate new key information based on the NCC stored in the context for encryption and/or protection of data/signaling on DRB and SRB;

·Continue the ROHC function of DRB. Optionally, if the cell currently accessed by the UE is the last serving cell or the cell currently accessed by the UE is within the range of RNA, continue the ROHC function of SRB.

If an emergency service arrives at this time, the terminal triggers UE Assistance Information reporting. Furthermore, the UE carries the indication information of the arrival of emergency service in UE Assistance Information. Optionally, the UE triggers UAI reporting after RRCResumeRequest or RRCResumeRequest1 is successfully received by the network.

Exemplary:

1> if transmission of the UEAssistanceInformation message is initiated to indicate availability of emergency service:

2> Include the nonSDT-DataIndication/Emergency in the UAI message

/emergency in the UEAssistanceInformation message);

2> include and set the resumeCause to emergency.

Embodiment 3: MO-data arrives before MT-SDT is triggered.

In this embodiment, before the terminal sends the first restoration reason information, if MO-data arrives, the terminal may perform at least one of the following actions:

Replace/set resume cause value to MO-data;

Keep resume cause as MT-SDT;

Send two resume causes: MO-data+MT-SDT;

Send new resume cause: SDT service (including MO and MT SDT);

Choose to carry MO-data or MT-data in a predefined or network-indicated priority order;

Optionally, the predefined priority can be determined based on the size of the access category, that is, the smaller the access category value, the higher the priority.

If the selected resource is a RA-SDT or CG-SDT resource, set resume cause to MO-SDT, otherwise set it to MT-SDT.

Optionally, if the cause value of MT-SDT is carried, the terminal can select the Access Category (0-9) corresponding to MT-SDT. Specifically, the Access Category corresponding to MT-SDT can reuse the existing one (for example, the same "0" as MT-access) or a newly defined value.

Similarly, if the cause value of MO-SDT is carried, the terminal can select the Access Category (0-9) corresponding to MO-SDT. Specifically, the Access Category corresponding to MO-SDT can reuse the existing one (for example, "7" which is the same as MO-DATA, or "3, 4, 5, 6, 9" which is the same as other MO services) or a newly defined value.

Optionally, the value of access category can be based on upper-layer instructions.

Embodiment 4: MO-data arrives after MT-SDT is triggered.

Re-establish the RB-associated PDCP/RLC entity;

Continue the ROHC function of DRB.

Optionally, if MO-data service arrives at this time, and the radio bearer of MO-data does not belong to the radio bearer allowed to trigger SDT or does not belong to the radio bearer allowed to trigger MT-SDT, the terminal triggers UE Assistance Information reporting. Furthermore, the UE carries the indication information of the arrival of MO-data service in UEAssistanceInformation.

Exemplary:

1> if transmission of the UEAssistanceInformation message is initiated to indicate availability of data mapped to radio bearers not configured for SDT:

2> include the nonSDT-DataIndication in the UEAssistanceInformation message;

2> include and set the resumeCause according to the information received from the upper layers, if provided.

It should be understood that the above embodiments are only illustrative examples and do not limit the present application. The first service and the second service may also be implemented as other services in the above content, and their implementation methods are also within the protection scope of the present application.

The following is an embodiment of the device of the present application. For details not described in detail in the embodiment of the device, reference can be made to the corresponding records in the above method embodiment, and they will not be repeated herein.

FIG8 shows a schematic diagram of an information transmission device provided by an exemplary embodiment of the present application, the device comprising:

The sending module 810 is used to send RRC recovery reason information to the network device;

Optionally, the recovery reason information carries a reason value corresponding to the recovery reason, and the reason value is used to indicate at least one of the following service types of the terminal: emergency service type; high priority access type; MT access type; MO signaling type; MO data type; MO voice call type; MO video call type; MO information type; RNA update type; MPS priority access type; MCS priority access type; MT-SDT type.

Optionally, the device also includes a determination module 820, which is used to determine recovery reason information; wherein the recovery reason information is determined at least based on a first recovery reason associated with the first business and a second recovery reason associated with the second business, the first recovery reason is used to indicate the business type of the first business, and the second recovery reason is used to indicate the business type of the second business.

Optionally, the recovery reason information is determined by at least one of the following methods: based on the priority of the first recovery reason and the second recovery reason; based on terminal implementation; based on the agreement of the communication protocol.

Optionally, the recovery reason information is determined in any of the following situations: the second service arrives before the first service is triggered; the second service arrives after the first service is triggered and the first recovery reason has not yet been sent to the network device; the second service arrives after the first service is triggered and the first recovery reason has been sent to the network device.

Optionally, the determination module 820 is used to cancel the first service, determine the first information, and carry the second restoration reason; or trigger the first service, determine the second information, and carry the first restoration reason and the second restoration reason.

Optionally, the first information includes RRC recovery request information.

Optionally, the second information includes UAI.

Optionally, the sending module 810 is further used to send UAI; wherein, UAI is sent when the recovery reason information is not sent and a second service arrives after the first service is triggered, and the UAI carries indication information of the arrival of the second service.

Optionally, the device also includes a processing module 830, which is used to perform at least one of the following steps: restoring the wireless bearer associated with MT-SDT; restoring the wireless bearer associated with MO-SDT; reconstructing the PDCP entity associated with RB; reconstructing the RLC entity associated with RB; generating new key information, the new key information is used for encryption and/or protection of data on DRB, or the new key information is used for encryption and/or protection of signaling on SRB; and continuing the ROHC function of DRB.

Optionally, the processing module 830 is also used to perform at least one of the following operations when the recovery reason information is not sent and a second service arrives before the first service is triggered: replace or set the reason value to the service type of the second service; retain the reason value to the service type of the first service; send the first reason value and the second reason value, the first reason value is the service type of the first service, and the second reason value is the service type of the second service; send a new reason value, the new reason value is the service type of the second service; choose to carry MO data or MT data according to a predefined priority order; choose to carry MO data or MT data according to the priority order indicated by the network device; when the resources used by the recovery reason information are RA-SDT resources or CG-SDT resources, set the reason value to the service type of the second service; when the resources used by the recovery reason information are neither RA-SDT resources nor CG-SDT resources, set the reason value to the service type of the first service.

Optionally, the apparatus further includes a receiving module 840, configured to receive a paging message sent by a network device; wherein the paging message is used to indicate that downlink SDT data has arrived at the network device.

Optionally, the paging message carries indication information of MT-SDT, where the indication information is used to instruct the terminal to restore the RRC connection.

Optionally, the paging message carries at least one of the following information: terminal identification; resource configuration information of MT-SDT; and resource type indication information of MT-SDT.

Optionally, the processing module 830 is further configured to evaluate the triggering condition of MT-SDT.

Optionally, the triggering conditions of MT-SDT include at least one of the following conditions: the paging message carries the terminal identification and MT-SDT association information; the SIB carries SDT indication information, and the SDT indication information is used to indicate that the serving cell supports SDT service; the RRC release message carries the SDT configuration; the uplink data to be transmitted is carried by SDT; the amount of uplink data to be transmitted meets the quantity threshold; the channel quality of the terminal meets the quality threshold; the TA is valid; there are valid CG-SDT resources; there are valid RA-SDT resources; there are valid SPS resources.

Optionally, the SDT indication information includes SDT common configuration or MT-SDT common configuration.

Optionally, the sending module 810 is used to send recovery reason information to the network device when the triggering condition of MT-SDT is met.

Optionally, the processing module 830 is further used to start a timer, where the timer is used to indicate the duration between MT-SDT triggering and triggering failure.

Optionally, resources used for the recovery reason information include CG resources or R resources.

FIG9 shows a schematic diagram of an information transmission device provided by an exemplary embodiment of the present application, the device comprising:

The receiving module 910 is used to receive the restoration reason information of the radio resource control RRC sent by the terminal;

Optionally, the restoration reason information is determined by the terminal based on at least a first restoration reason associated with the first service and a second restoration reason associated with the second service, the first restoration reason is used to indicate a service type of the first service, and the second restoration reason is used to indicate a service type of the second service.

Optionally, the first information includes RRC recovery request information.

Optionally, the second information includes UAI.

Optionally, the receiving module 910 is further used to receive UAI; wherein, UAI is sent when the recovery reason information is not sent and a second service arrives after the first service is triggered, and the UAI carries indication information of the arrival of the second service.

Optionally, the apparatus further includes a sending module 920, configured to send a paging message to the terminal; wherein the paging message is used to indicate that downlink SDT data has arrived at the network device.

Optionally, the recovery reason information is sent when the triggering condition of MT-SDT is met.

Optionally, resources used for the recovery reason information include CG resources or RA resources.

FIG10 shows a schematic diagram of the structure of a communication device (terminal or network device) provided by an exemplary embodiment of the present application. The communication device includes: a processor 1001 , a receiver 1002 , a transmitter 1003 , a memory 1004 and a bus 1005 .

The processor 1001 includes one or more processing cores. The processor 1001 executes various functional applications and information processing by running software programs and modules.

The receiver 1002 and the transmitter 1003 may be implemented as a communication component, which may be a communication chip.

The memory 1004 is connected to the processor 1001 via a bus 1005 .

The memory 1004 may be used to store at least one instruction, and the processor 1001 may be used to execute the at least one instruction to implement each step of the information transmission method mentioned in the above method embodiment.

In addition, memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, programmable read-only memory (PROM).

The present application also provides a terminal, which includes a memory and a processor; the memory stores at least one program code, and the program code is loaded and executed by the processor to implement the aforementioned information transmission method.

The present application also provides a network device, which includes a memory and a processor; at least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the aforementioned information transmission method.

The present application also provides a computer-readable storage medium, in which a computer program is stored. The computer program is used to be executed by a processor to implement the aforementioned information transmission method.

The present application also provides a chip, which includes a programmable logic circuit and/or program instructions, and is used to implement the aforementioned information transmission method when an electronic device equipped with the chip is running.

The present application also provides a computer program, which includes computer instructions, and the computer instructions are used to implement the aforementioned information transmission method.

The present application also provides a computer program product, which includes computer instructions. The computer instructions are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the aforementioned information transmission method.

The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

An information transmission method, characterized in that the method is executed by a terminal, and the method comprises:

Sending RRC recovery reason information to the network device;

The restoration reason information is used to inform the network device of the service type of the terminal.
The method according to claim 1, characterized in that the restoration reason information carries a reason value corresponding to the restoration reason, and the reason value is used to indicate at least one of the following service types of the terminal:

Type of emergency business;

High priority access type;

An MT access type received by the terminal;

The MO signaling type initiated by the terminal;

MO data type;

MO voice call type;

MO video call type;

MO information type;

Notification area RNA update type based on radio access network;

Multimedia Priority Service MPS priority access type;

Modulation and coding scheme MCS priority access type;

The terminal receives a small data transmission of type MT-SDT.
The method according to claim 1 or 2, characterized in that the method further comprises:

Determining the restoration reason information;

The restoration reason information is determined at least based on a first restoration reason associated with the first service and a second restoration reason associated with the second service, wherein the first restoration reason is used to indicate a service type of the first service, and the second restoration reason is used to indicate a service type of the second service.
The method according to claim 3, characterized in that the restoration reason information is determined by at least one of the following methods:

Determining based on the priority of the first restoration reason and the second restoration reason;

Determined based on terminal implementation;

Determined based on the agreement of the communication protocol.
The method according to claim 3, characterized in that the restoration reason information is determined in any of the following situations:

Before the first service is triggered, the second service arrives;

After the first service is triggered and the first restoration reason has not yet been sent to the network device, the second service arrives;

After the first service is triggered and the first restoration reason has been sent to the network device, the second service arrives.
The method according to any one of claims 3 to 5, characterized in that the determining the restoration reason information comprises:

canceling the first service and determining first information, wherein the first information carries the second restoration reason;

Alternatively, the first service is triggered and second information is determined, where the second information carries the first restoration reason and the second restoration reason.
The method according to claim 6, characterized in that

The first information includes radio resource control RRC resumption request information.
The method according to claim 6, characterized in that

The second information includes terminal assistance information UAI.
The method according to any one of claims 3 to 5, characterized in that the first service includes at least one of the following services:

Small data transmission MT-SDT received by the terminal;

Small data transmission MO-SDT initiated by the terminal;

Small data transmission SDT
The method according to any one of claims 3 to 5, characterized in that the second service includes at least one of the following services:

Emergency business;

High priority access services;

MT access service received by the terminal;

MO signaling service initiated by the terminal;

MO data service;

MO voice call service;

MO video call service;

MO information service;

Multimedia Priority Service MPS priority access service;

Modulation and coding scheme MCS priority access service;

Notification area update RNAU service based on wireless access network;

The terminal initiates a small data transmission MO-SDT.
The method according to any one of claims 1 to 10, characterized in that the method further comprises:

Send terminal auxiliary information UAI;

The UAI is sent when the restoration reason information is not sent and a second service arrives after the first service is triggered, and the UAI carries indication information of the arrival of the second service.
The method according to any one of claims 1 to 10, characterized in that the method further comprises at least one of the following steps:

Restoring a radio bearer associated with a small data transmission MT-SDT received by the terminal;

Restoring the radio bearer associated with the small data transmission MO-SDT initiated by the terminal;

Reestablishing a packet data convergence protocol PDCP entity associated with a radio bearer RB;

Reestablishing a radio link control RLC entity associated with the RB;

Generate new key information, where the new key information is used for encryption and/or security of data on a data resource carrying a DRB, or the new key information is used for encryption and/or security of signaling on a signaling resource carrying an SRB;

Continue the robust header compression ROHC function of the DRB.
The method according to any one of claims 1 to 10, characterized in that the method further comprises:

If the restoration reason information is not sent and a second service arrives before the first service is triggered, perform at least one of the following operations:

Replace or set the cause value to the service type of the second service;

Retain the cause value as the service type of the first service;

Send a first cause value and a second cause value, where the first cause value is a service type of the first service, and the second cause value is a service type of the second service;

Sending a new cause value, where the new cause value is a service type of the second service;

Selecting, according to a predefined priority order, data MO data carrying small data transmission initiated by the terminal or data MT data carrying small data transmission received by the terminal;

Selecting to carry the MO data or the MT data according to the priority order indicated by the network device;

When the resource used by the recovery reason information is a random access small data transmission RA-SDT resource or a preconfigured small data transmission CG-SDT resource, setting the reason value to the service type of the second service;

In a case where the resource used by the restoration reason information is neither the RA-SDT resource nor the CG-SDT resource, the reason value is set to the service type of the first service.
The method according to any one of claims 1 to 10, characterized in that the method further comprises:

Receiving a paging message sent by the network device;

The paging message is used to indicate that downlink small data transmission (SDT) data has arrived at the network device.
The method according to claim 14, characterized in that

The paging message carries indication information of small data transmission MT-SDT received by the terminal, and the indication information is used to instruct the terminal to restore the RRC connection.
The method according to claim 14, characterized in that the paging message carries at least one of the following information:

Terminal identification;

Resource configuration information of a small data transmission MT-SDT received by the terminal;

The resource type indication information of the MT-SDT.
The method according to any one of claims 14 to 16, characterized in that the method further comprises:

Evaluate the triggering condition of the small data transmission MT-SDT received by the terminal.
The method according to claim 17, wherein the triggering condition of the MT-SDT comprises at least one of the following conditions:

The paging message carries the terminal identification and the MT-SDT association information;

The system resource block SIB carries SDT indication information, where the SDT indication information is used to indicate that the serving cell supports the SDT service;

The RRC release message carries the SDT configuration;

The uplink data to be transmitted is carried by SDT;

The amount of the uplink data to be transmitted meets the quantity threshold;

The channel quality of the terminal meets the quality threshold;

Timing advance TA is effective;

There are valid pre-configured small data transmission CG-SDT resources;

There are effective random access small data transmission RA-SDT resources;

There are effective semi-persistent scheduling SPS resources.
The method according to claim 18, characterized in that

The SDT indication information includes SDT common configuration or MT-SDT common configuration.
The method according to claim 17, characterized in that the sending of the recovery reason information of the radio resource control RRC to the network device comprises:

When the triggering condition of the MT-SDT is met, the restoration reason information is sent to the network device.
The method according to any one of claims 1 to 20, characterized in that the method further comprises:

A timer is started, where the timer is used to indicate the duration between the triggering and the failure of the triggering of the small data transmission MT-SDT received by the terminal.
The method according to any one of claims 1 to 20, characterized in that

The resources used by the recovery reason information include pre-configured CG resources or random access R resources.
An information transmission method, characterized in that the method is performed by a network device, and the method comprises:

Receiving the recovery reason information of the radio resource control RRC sent by the terminal;

The restoration reason information is used to inform the network device of the service type of the terminal.
The method according to claim 23, characterized in that the restoration reason information carries a reason value corresponding to the restoration reason, and the reason value is used to indicate at least one of the following service types of the terminal:

Type of emergency business;

High priority access type;

An MT access type received by the terminal;

The MO signaling type initiated by the terminal;

MO data type;

MO voice call type;

MO video call type;

MO information type;

Notification area RNA update type based on radio access network;

Multimedia Priority Service MPS priority access type;

Modulation and coding scheme MCS priority access type;

The terminal receives a small data transmission of type MT-SDT.
The method according to claim 23 or 24, characterized in that

The restoration reason information is determined by the terminal at least based on a first restoration reason associated with a first service and a second restoration reason associated with a second service, wherein the first restoration reason is used to indicate a service type of the first service, and the second restoration reason is used to indicate a service type of the second service.
The method according to claim 25, characterized in that the restoration reason information is determined by at least one of the following methods:

Determining based on the priority of the first restoration reason and the second restoration reason;

Determined based on terminal implementation;

Determined based on the agreement of the communication protocol.
The method according to claim 25, characterized in that the restoration reason information is determined in any of the following situations:

Before the first service is triggered, the second service arrives;

After the first service is triggered and the first restoration reason has not yet been sent to the network device, the second service arrives;

After the first service is triggered and the first restoration reason has been sent to the network device, the second service arrives.
The method according to any one of claims 25 to 27, characterized in that

The restoration reason information is first information, and the first information carries the second restoration reason;

Alternatively, the restoration reason information is second information, and the second information carries the first restoration reason and the second restoration reason.
The method according to claim 28, characterized in that

The first information includes radio resource control RRC resumption request information.
The method according to claim 28, characterized in that

The second information includes terminal assistance information UAI.
The method according to any one of claims 25 to 27, characterized in that the first service includes at least one of the following services:

Small data transmission MT-SDT received by the terminal;

Small data transmission MO-SDT initiated by the terminal;

Small data transmission SDT
The method according to any one of claims 25 to 27, characterized in that the second service includes at least one of the following services:

Emergency business;

High priority access services;

MT access service received by the terminal;

MO signaling service initiated by the terminal;

MO data service;

MO voice call service;

MO video call service;

MO information service;

Multimedia Priority Service MPS priority access service;

Modulation and coding scheme MCS priority access service;

Notification area update RNAU service based on wireless access network;

The terminal initiates a small data transmission MO-SDT.
The method according to any one of claims 23 to 32, characterized in that the method further comprises:

Receiving terminal auxiliary information UAI;

The UAI is sent when the restoration reason information is not sent and a second service arrives after the first service is triggered, and the UAI carries indication information of the arrival of the second service.
The method according to any one of claims 23 to 32, characterized in that the method further comprises:

Sending a paging message to the terminal;

The paging message is used to indicate that downlink small data transmission (SDT) data has arrived at the network device.
The method according to claim 34, characterized in that

The paging message carries indication information of small data transmission MT-SDT received by the terminal, and the indication information is used to instruct the terminal to restore the RRC connection.
The method according to claim 34, characterized in that the paging message carries at least one of the following information:

Terminal identification;

Resource configuration information of a small data transmission MT-SDT received by the terminal;

The resource type indication information of the MT-SDT.
The method according to any one of claims 34 to 36, characterized in that

The restoration reason information is sent when a trigger condition of a small data transmission MT-SDT received by the terminal is met.
The method according to any one of claims 23 to 37, characterized in that

The resources used by the recovery reason information include pre-configured CG resources or random access RA resources.
An information transmission device, characterized in that the device comprises:

A sending module, used for sending the recovery reason information of the radio resource control RRC to the network device;

The restoration reason information is used to inform the network device of the service type of the terminal.
An information transmission device, characterized in that the device comprises:

A receiving module, used for receiving the recovery reason information of the radio resource control RRC sent by the terminal;

The restoration reason information is used to inform the network device of the service type of the terminal.
A terminal, characterized in that the terminal comprises a memory and a processor;

At least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the information transmission method according to any one of claims 1 to 22.
A network device, characterized in that the network device comprises a memory and a processor;

At least one program code is stored in the memory, and the program code is loaded and executed by the processor to implement the information transmission method as described in any one of claims 23 to 38.
A computer-readable storage medium, characterized in that a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the information transmission method as described in any one of claims 1 to 38.
A chip, characterized in that the chip includes a programmable logic circuit and/or program instructions, and when an electronic device equipped with the chip is running, it is used to implement the information transmission method as described in any one of claims 1 to 38.
A computer program, characterized in that the computer program includes computer instructions, and the computer instructions are used to implement the information transmission method as described in any one of claims 1 to 38.
A computer program product, characterized in that the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and a processor reads and executes the computer instructions from the computer-readable storage medium to implement the information transmission method as described in any one of claims 1 to 38.