Information transmission method and device, equipment and storage medium

Abstract

The invention discloses an information transmission method and device, equipment and a storage medium, and relates to the technical field of communication. The method is executed by a terminal, and comprises the following steps: sending recovery reason information of RRC (Radio Resource Control) to network equipment; wherein the recovery reason information is used for informing the network device of the service type of the terminal (302).

Description

Information transmission method, device, equipment and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an information transmission method, apparatus, device and storage medium. Background Art

[0002] Small Data Transmission (EDT) involves two types of transmission: Mobile Originated Small Data Transmission (MO-SDT) and Mobile Terminated Small Data Transmission (MT-SDT). MO-SDT is triggered by the terminal, while MT-SDT is triggered by the network device.

[0003] Taking MT-SDT triggered by the network as an example, the network notifies the terminal via a paging message and carries the MT-SDT resume cause in the RRC connection recovery process, indicating that the purpose of the RRC recovery request is to trigger MT-SDT. When the terminal autonomously generates the MT-SDT resume cause after receiving the paging message, if new services arrive at this time, a resume cause conflict will occur. The resolution of this conflict has not yet been discussed.

[0004] Summary of the Invention

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

[0006] According to one aspect of the present application, a method for transmitting information is provided. The method is performed by a terminal and includes:

[0007] Sending RRC recovery reason information to the network device;

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

[0009] According to one aspect of the present application, a method for transmitting information is provided. The method is performed by a network device and includes:

[0010] Receiving the RRC recovery reason information sent by the terminal;

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

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

[0013] A sending module, configured to send recovery reason information of the radio resource control RRC to the network device;

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

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

[0016] A receiving module, configured to receive recovery reason information of the radio resource control RRC sent by the terminal;

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

[0018] According to one aspect of the present application, a computer device is provided, the computer device including a memory and a processor;

[0019] 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 described above.

[0020] 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 configured to be executed by a processor to implement the information transmission method described above.

[0021] According to one aspect of the present application, a chip is provided. 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 above-mentioned information transmission method.

[0022] 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 described above.

[0023] 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 described above.

[0024] The technical solutions provided by the embodiments of the present application include at least the following beneficial effects:

[0025] A solution is provided for conflicting recovery reasons. The recovery reason information carries the terminal's service type, informing the network device of the service type. This allows the terminal and the network device to perform an RRC connection recovery process based on different service types to complete the processing of the corresponding service. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. 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 any creative work.

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

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

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

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

[0031] FIG5 is a flowchart of an information transmission method provided by an exemplary embodiment of the present application;

[0032] FIG6 is a flowchart of an information transmission method provided by an exemplary embodiment of the present application;

[0033] FIG7 is a flowchart of an information transmission method provided by an exemplary embodiment of the present application;

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

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

[0036] FIG10 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0037] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

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

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

[0040] The following describes the two SDTs mentioned above:

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

[0042] Figure 1 shows a schematic diagram of the MO-EDT air interface process provided by an exemplary embodiment of the present application. 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 (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.

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

[0044] FIG2 shows a schematic diagram of a MO-EDT process provided by an exemplary embodiment of the present application.

[0045] Among them, 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 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 included, the terminal initiates the MO-EDT process to respond to the paging on the network side.

[0046] The MO-EDT initiated during the MT-EDT process differs from the MO-EDT process in the following ways:

[0047] - The terminal initiates random access using legacy Random Access Channel (legacy RACH) resources, i.e., it does not use random access resources dedicated to MO-EDT;

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

[0049] -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.

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

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

[0052] In the 5G NR system, there are three RRC states: RRC Idle (RRC_IDLE), RRC Inactive (RRC_INACTIVE), and RRC Connected (RRC_CONNECTED). The RRC Inactive state is a new state introduced in the 5G system for energy conservation. For terminals in the RRC Inactive state, the radio bearer and all radio resources are released, but the terminal and network equipment retain the terminal access context to quickly restore the RRC connection. Network equipment typically keeps terminals with infrequent data transmission in the RRC Inactive state.

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

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

[0055] - The uplink data and / or signaling to be transmitted belongs to a radio bearer that allows triggering SDT, such as a signaling radio bearer (SRB) or a data radio bearer (DRB);

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

[0057] The downlink Reference Signal Received Power (RSRP) measurement result is greater than the RSRP threshold pre-configured by the network device.

[0058] - There are valid SDT resources, such as Random Access-SDT (RA-SDT) resources and / or Configured Grant-SDT (CG-SDT) resources.

[0059] 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:

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

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

[0062] Schematically, after the network device triggers MT-SDT, it sends an MT-SDT indication to the terminal via a paging message. After receiving the indication, the terminal initiates the MT-SDT process. The terminal triggers the RRC resume process and carries the cause value corresponding to the MT-SDT resume reason (resume cause value) to indicate to the network device that the purpose of the current RRC resume request is to trigger the MT-SDT process.

[0063] When a terminal autonomously generates a restoration reason for MT-SDT after receiving a 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.

[0064] FIG3 shows 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:

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

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

[0067] As mentioned above, when triggering the RRC connection recovery process, 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 will arrive, causing a conflict in the recovery reason.

[0068] 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.

[0069] The restoration reason information carries a reason value corresponding to the restoration reason, which 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:

[0070] Emergency type;

[0071] High Priority Access type;

[0072] MT-Access type;

[0073] MO signaling type;

[0074] MO-Data type;

[0075] MO-VoiceCall type;

[0076] MO-VideoCall type;

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

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

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

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

[0081] MT-SDT type.

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

[0083] The restoration reason information is determined based on at least a first restoration reason associated with the first service and a second restoration reason associated with the second service, where the first restoration reason indicates the service type of the first service, and the second restoration reason indicates the 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, where the restoration reason set includes at least the first restoration reason and the second restoration reason.

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

[0085] 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.

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

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

[0088] 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 based on the second restoration reason, and the restoration reason information is used to indicate the service type corresponding to the second service.

[0089] In other embodiments, the terminal determines the restoration reason information based on terminal implementation. Terminal implementation can be understood as a communication operator negotiating and determining the order in which restoration reasons are used for different services. Terminal implementation can also be understood as a terminal determining the restoration reason information based on its own communication needs. For example, if the importance level of a first service is higher than that of a second service, the terminal generates restoration reason information based on the first restoration reason. The restoration reason information is used to indicate the service type corresponding to the first service.

[0090] In other embodiments, the terminal may also determine the restoration reason information based on the provisions of the communication protocol. The provisions of the communication protocol may be understood as communication specifications provided by a standardization organization. For example, if the first service is MT-SDT and the second service is an emergency service, based on the provisions of the communication protocol, the terminal may generate restoration reason information based on the restoration reason corresponding to the emergency service. This restoration reason information is used to indicate the service type corresponding to the emergency service.

[0091] In some embodiments, the restoration reason information needs to be determined based on 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):

[0092] The second service arrives before the first service is triggered;

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

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

[0095] It can be understood that, in the case where the RRC connection recovery process based on the first recovery reason has not been completed, the terminal can determine the recovery reason information in order to inform the network device of the service type. That is, in the case where the first recovery reason generated based on the first service has not been sent to the network device (i.e., 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 (i.e., 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.

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

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

[0098] 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.

[0099] 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.

[0100] Optionally, the first information includes RRC recovery request information, wherein the RRC recovery request information can be implemented as RRCResumeRequest message or RRCResumeRequest1.

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

[0102] For example, if the first service is MT-SDT and the second service is an emergency service, when the first service arrives, the terminal can generate first restoration reason information based on the service type of the first service. The terminal can then send this information to the network device and perform the RRC connection restoration process to complete the processing of the first service.

[0103] In some embodiments, when the RRC connection recovery process has not yet been completed, there is a possibility that a second service may arrive. Depending on the timing of the second service arrival, two processing solutions are shown below:

[0104] The second service arrives before the first service is triggered.

[0105] If a second service arrives before the first resume cause message is sent, the terminal may replace the cause value in the first resume cause message with the cause value corresponding to the emergency service, i.e., 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 message is sent, it can be understood that the first resume cause message has been generated but not sent, or it can also be understood that the first resume cause message has not been generated.

[0106] With reference to the foregoing, if the terminal triggers the MT-SDT service and carries an emergency service cause value in the UAI, the terminal may select the access category corresponding to the MT-SDT. The access category corresponding to the MT-SDT may reuse the values ​​set in the related art (0-9) or may define new values ​​(other than 0-9), which is not limited in this application.

[0107] The second service arrives after the first service is triggered.

[0108] Before the first restoration reason is sent, if the second service arrives after the first service is triggered, the terminal may trigger the reporting of the UAI, and include an indication of the arrival of the second service in the UAI. In other words, the UAI notifies the network device of the arrival of the emergency service. Optionally, the UAI is triggered after the first restoration reason information is successfully received by the network device.

[0109] In summary, the information transmission method provided in the embodiments of the present application provides a solution for conflicting recovery reasons. Specifically, the recovery reason information carries the terminal's service type, so as to inform the network device of the service type, thereby enabling the terminal and the network device to perform the RRC connection recovery process based on different service types to complete the processing of the corresponding service.

[0110] 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:

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

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

[0113] The restoration reason information carries a reason value corresponding to the restoration reason, which 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; Mobile Equipment Access type; Mobile Equipment Signaling type; Mobile Equipment Data type; Mobile Equipment Voice Call type; Mobile Equipment Video Call type; Mobile Equipment Information type; RNA-Update type; MPS-PriorityAccess type; MCS-PriorityAccess type; or Mobile Equipment SDT type.

[0114] In some embodiments, the terminal further needs to determine restoration reason information, where the restoration reason information is determined based on at least a first restoration reason associated with the first service and a second restoration reason associated with the second service, where the first restoration reason indicates a service type of the first service and the second restoration reason indicates a service type of the second service.

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

[0116] 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.

[0117] The specific process of determining the restoration reason can be referred to the above content and will not be repeated here.

[0118] In some embodiments, the restoration reason information needs to be determined based on 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: the second service arrives 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; and the second service arrives after the first service is triggered and the first restoration reason has been sent to the network device.

[0119] According to the above content, the first business and the second business include multiple types. Combined with the above scenarios, the recovery reason information can be implemented as any one of the following: canceling the first business, determining the first information, and the first information carries the second recovery reason; or, triggering the first business, determining the second information, and the second information carries the first recovery reason and the second recovery reason.

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

[0121] In summary, the information transmission method provided in the embodiments of the present application provides a solution for conflicting recovery reasons. Specifically, the recovery reason information carries the terminal's service type, so as to inform the network device of the service type, thereby enabling the terminal and the network device to perform the RRC connection recovery process based on different service types to complete the processing of the corresponding service.

[0122] 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:

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

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

[0125] The restoration reason information carries a reason value corresponding to the restoration reason, which 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; Mobile Equipment Access type; Mobile Equipment Signaling type; Mobile Equipment Data type; Mobile Equipment Voice Call type; Mobile Equipment Video Call type; Mobile Equipment Information type; RNA-Update type; MPS-PriorityAccess type; MCS-PriorityAccess type; or Mobile Equipment SDT type.

[0126] In some embodiments, the terminal further needs to determine restoration reason information, where the restoration reason information is determined based on at least a first restoration reason associated with the first service and a second restoration reason associated with the second service, where the first restoration reason indicates a service type of the first service and the second restoration reason indicates a service type of the second service.

[0127] The specific process of determining the restoration reason can be referred to the above content and will not be repeated here.

[0128] In some embodiments, the restoration reason information needs to be determined based on 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: the second service arrives 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; and the second service arrives after the first service is triggered and the first restoration reason has been sent to the network device.

[0129] According to the above content, the first business and the second business include multiple types. Combined with the above scenarios, the recovery reason information can be implemented as any one of the following: canceling the first business, determining the first information, and the first information carries the second recovery reason; or, triggering the first business, determining the second information, and the second information carries the first recovery reason and the second recovery reason.

[0130] Optionally, the resources used by the recovery request information include configured grant (CG) resources or random access (RA) resources.

[0131] 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.

[0132] In summary, the information transmission method provided in the embodiments of the present application provides a solution for conflicting recovery reasons. Specifically, the recovery reason information carries the terminal's service type, so as to inform the network device of the service type, thereby enabling the terminal and the network device to perform the RRC connection recovery process based on different service types to complete the processing of the corresponding service.

[0133] As previously mentioned, 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. This will inform the network device of the terminal's service type, allowing the network device to clearly understand 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 using to initiate the RRC connection recovery process, effectively avoiding the problem of conflicting recovery reasons.

[0134] Based on FIG5 , FIG6 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:

[0135] Step 3011: The terminal determines the restoration reason information.

[0136] Illustratively, the restoration reason information is determined 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 being used to indicate a service type of the first service, and the second restoration reason being used to indicate a service type of the second service.

[0137] 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, where the restoration reason set includes at least the first restoration reason and the second restoration reason.

[0138] With reference to the above content, the first business and the second business include multiple types, as follows:

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

[0140] 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.

[0141] 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:

[0142] Prioritization based on the first and second restoration reasons;

[0143] 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, where the restoration reason information is used to indicate the service type corresponding to the second service.

[0144] Determined based on terminal implementation.

[0145] Among them, terminal implementation can be understood as the communication operator's negotiation and determination, which determines the order of use of recovery reasons between different services; terminal implementation can also be understood as the terminal's determination based on 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 based on the first recovery reason, and the recovery reason information is used to indicate the service type corresponding to the first service.

[0146] Determined based on the communication protocol.

[0147] The communication protocol agreement can be understood as the communication specifications set by a 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 based on the recovery reason corresponding to the emergency service. This recovery reason information is used to indicate the service type corresponding to the emergency service.

[0148] In some embodiments, the restoration reason information needs to be determined based on 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):

[0149] The second service arrives before the first service is triggered;

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

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

[0152] It can be understood that, in the case where the RRC connection recovery process based on the first recovery reason has not been completed, the terminal can determine the recovery reason information in order to inform the network device of the service type. That is, in the case where the first recovery reason generated based on the first service has not been sent to the network device (i.e., 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 (i.e., 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.

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

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

[0155] 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.

[0156] 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.

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

[0158] With reference 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 additional related processing steps.

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

[0160] The terminal sends UAI to the network device;

[0161] 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.

[0162] 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 burst service arrival. 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 MO data service arrival.

[0163] 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 the UAI after the first restoration reason information is successfully received by the network device and triggered.

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

[0165] -Restore the radio bearer associated with MT-SDT;

[0166] -Restore the radio bearer associated with MO-SDT;

[0167] - Reestablishing the Packet Data Convergence Protocol (PDCP) entity associated with the Radio Bearer (RB);

[0168] -Reestablishing the Radio Link Control (RLC) entity associated with the RB;

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

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

[0171] 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 the DRB and SRB. Optionally, the ROHC function of continuing the DRB is performed when the terminal's current access cell is the last cell providing service or a cell within the range of the RNA.

[0172] In some embodiments, the above steps are performed based on the arrival of a second service after the first service is triggered. For example, an emergency service or an MO data service arrives after the MT-SDT is triggered. If the second service is an MO data service, the radio bearer for the MO data service is not a radio bearer that allows triggering SDT, or the radio bearer for the MO data service is not an unlimited bearer that allows triggering MT-SDT.

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

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

[0175] -Retain the service type of the first service with the cause value;

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

[0177] - Send a new cause value, the new cause value is the service type of the second service;

[0178] -Select to carry MO data or MT data according to the predefined priority order;

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

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

[0181] - In a case where the resource used by the restoration cause information is neither an RA-SDT resource nor a CG-SDT resource, the cause value is set to the service type of the first service.

[0182] 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.

[0183] 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: replacing or setting the cause value to MO data; retaining the cause value to MT-SDT; sending a first cause value and a second cause value, the first cause value being MO data and the second cause value being MT-SDT; sending a new cause value, the new cause value being SDT; selecting to carry MO data or MT data according to a predefined priority order; selecting to carry MO data or MT data according to a priority order indicated by the network device; when the resources used to restore the cause information are RA-SDT resources or CG-SDT resources, setting the cause value to MO-SDT; when the resources used to restore the cause information are neither RA-SDT resources nor CG-SDT resources, setting the cause value to MT-SDT.

[0184] 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 a 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 this application does not limit this.

[0185] 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 further provides multiple optional execution steps for the terminal. For example, triggering the UAI to report the indication information of the arrival of the second service so that the network device is aware of the arrival of the second service and thus waits for the recovery reason information sent by the terminal.

[0186] As mentioned above, the recovery request information is sent during the RRC connection recovery process. Based on this, the terminal needs to perform related operations such as 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:

[0187] Based on FIG5 , FIG7 shows a flowchart of an information transmission method provided by an exemplary embodiment of the present application, further comprising steps 3012a and 3012b, and step 302 can be implemented as step 3021, as follows;

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

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

[0190] In some embodiments, the paging message carries MT-SDT indication information, which is used to instruct the terminal to restore the RRC connection. Based on this, the terminal can determine the restoration reason information based on the service type of the current service and feedback it to the network device so that the network device can clearly understand which service the terminal wishes to perform the RRC connection restoration process based on.

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

[0192] Terminal identification;

[0193] MT-SDT resource configuration information;

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

[0195] 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 sets of preconfigured resources for uplink / downlink data transmission.

[0196] MT-SDT resource type indication information.

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

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

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

[0200] 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 if the triggering condition of the MT-SDT is met.

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

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

[0203] The System Information Block (SIB) carries SDT indication information, which is used to indicate that the serving cell supports the SDT service.

[0204] The RRC release message carries the SDT configuration;

[0205] Uplink data to be transmitted is carried by the SDT bearer.

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

[0207] The terminal's channel quality meets the quality threshold;

[0208] Timing Advance (TA) is effective;

[0209] There are valid CG-SDT resources;

[0210] · There are valid RA-SDT resources;

[0211] There are valid SPS resources.

[0212] 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 serving cell.

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

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

[0215] According to step 3012b, the terminal may determine whether to send a restoration reason message to the network device based on the evaluation result. In some embodiments, the restoration reason message may be implemented as an RRC restoration request message. For example, the restoration reason message may be RRCResumeRequest message or RRCResumeRequest1.

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

[0217] The terminal starts a timer to indicate the duration between MT-SDT triggering and trigger failure. This means that when the terminal sends a recovery reason message to the network device, it can start the timer upon triggering MT-SDT. If the timer expires, the MT-SDT process is considered failed, facilitating subsequent MT-SDT failure maintenance.

[0218] 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.

[0219] 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 MT-SDT indication information, 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 recovery reason information to the network device to inform the network device of the service type of the terminal.

[0220] With reference to the foregoing, to avoid conflicts between the restoration reasons of multiple services, the terminal may determine the restoration reason information based on the restoration reasons associated with at least two services (i.e., the first service and the second service in the foregoing). Since the terminal has multiple service types, several exemplary embodiments are given below:

[0221] Example 1: Emergency service arrives before MT-SDT is triggered.

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

[0223] 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:

[0224] UE identification;

[0225] MT-SDT resource configuration information;

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

[0227] MT-SDT resource type indication information.

[0228] 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.

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

[0230] Optionally, the triggering conditions of MT-SDT include at least one of the following: the paging message carries a terminal identifier and an MT-SDT indication; the SIB carries SDT indication information, and the SDT indication information is used to indicate that the serving cell supports the SDT service, and the SDT indication information can 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.

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

[0232] Optionally, the first resumption cause information includes RRC resumption request information, which in some embodiments can be implemented as RRCResumeRequest message or RRCResumeRequest1. The first resumption cause information carries a resumption cause value (resume cause value) that triggers 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.

[0233] Optionally, the terminal starts a first timer.

[0234] In this embodiment, if 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.

[0235] Exemplary:

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

[0237] 2> If an emergency service is ongoing:

[0238] 3> Select '2' as the Access Category;

[0239] 3> Set the resumeCause to emergency.

[0240] It should be understood that access category "2" is only an example and does not limit this application.

[0241] Optionally, the terminal triggers the MT-SDT service and carries the emergency cause value in the subsequent UAI. Based on this, if the UAI carries the MT-SDT cause value, the terminal can select the Access Category (0-9) corresponding to MT-SDT. For example, the Access Category corresponding to MT-SDT can reuse an existing one (such as "0," the same as MT-access) or a newly defined value, i.e., an Access Category value other than 0-9.

[0242] Example 2: Emergency service arrives after MT-SDT is triggered.

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

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

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

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

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

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

[0249] Restore MT / SDT and / or MO-SDT associated radio bearers (DRB and / or SRB);

[0250] Re-establishing the RB-associated PDCP / RLC entity;

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

[0252] ·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.

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

[0254] Exemplary:

[0255] 1> If transmission of the UEAssistanceInformation message is initiated to indicate availability of emergency service:

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

[0257] / emergency in the UEAssistanceInformation message);

[0258] 2> Include and set the resumeCause to emergency.

[0259] Example 3: MO-data arrives before MT-SDT is triggered.

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

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

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

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

[0264] 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:

[0265] Replace / set resume cause value to MO-data;

[0266] Keep resume cause as MT-SDT;

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

[0268] Send a new resume cause: SDT service (including MO and MT SDT);

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

[0270] Optionally, the predefined priority may be determined according to the size of the access category, that is, the smaller the access category value, the higher the priority.

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

[0272] 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 (such as the same "0" as MT-access) or a newly defined value.

[0273] 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 be a reused existing one (such as "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.

[0274] Optionally, the value of the access category can be based on upper layer indications.

[0275] Example 4: MO-data arrives after MT-SDT is triggered.

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

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

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

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

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

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

[0282] Restore MT / SDT and / or MO-SDT associated radio bearers (DRB and / or SRB);

[0283] Re-establishing the RB-associated PDCP / RLC entity;

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

[0285] Continue the ROHC function of DRB.

[0286] Optionally, if MO-data traffic arrives at this time, and the radio bearer for MO-data traffic is not a radio bearer that allows triggering SDT or a radio bearer that allows triggering MT-SDT, the terminal triggers UE Assistance Information reporting. Furthermore, the UE carries information indicating the arrival of MO-data traffic in the UEAssistanceInformation.

[0287] Exemplary:

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

[0289] 2> Include the nonSDT-DataIndication in the UEAssistanceInformation message;

[0290] 2> Include and set the resumeCause according to the information received from the upper layers, if provided.

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

[0292] 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 no further details will be given herein.

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

[0294] The sending module 810 is configured to send RRC recovery reason information to the network device;

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

[0296] 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.

[0297] Optionally, the device also includes a determination module 820 for determining 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.

[0298] Optionally, the restoration reason information is determined in at least one of the following ways: based on the priority of the first restoration reason and the second restoration reason; based on terminal implementation; based on the agreement of the communication protocol.

[0299] 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.

[0300] Optionally, the determination module 820 is configured to cancel the first service, determine the first information, and carry the second restoration reason in the first information; or trigger the first service, determine the second information, and carry the first restoration reason and the second restoration reason in the second information.

[0301] Optionally, the first information includes RRC recovery request information.

[0302] Optionally, the second information includes UAI.

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

[0304] 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.

[0305] Optionally, the sending module 810 is further configured to send UAI; wherein, 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.

[0306] 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; continuing the ROHC function of DRB.

[0307] 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; 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 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.

[0308] 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.

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

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

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

[0312] 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.

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

[0314] Optionally, the sending module 810 is configured to send restoration reason information to the network device when the triggering condition of the MT-SDT is met.

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

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

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

[0318] The receiving module 910 is configured to receive radio resource control (RRC) recovery reason information sent by the terminal;

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

[0320] 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.

[0321] 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, where 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.

[0322] Optionally, the restoration reason information is determined in at least one of the following ways: based on the priority of the first restoration reason and the second restoration reason; based on terminal implementation; based on the agreement of the communication protocol.

[0323] 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.

[0324] Optionally, the determination module 820 is configured to cancel the first service, determine the first information, and carry the second restoration reason in the first information; or trigger the first service, determine the second information, and carry the first restoration reason and the second restoration reason in the second information.

[0325] Optionally, the first information includes RRC recovery request information.

[0326] Optionally, the second information includes UAI.

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

[0328] 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.

[0329] Optionally, the sending module 810 is further configured to send UAI; wherein, 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.

[0330] 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.

[0331] 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.

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

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

[0334] Optionally, the restoration reason information is sent when the triggering condition of MT-SDT is met.

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

[0336] FIG10 shows a schematic structural diagram 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 .

[0337] 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.

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

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

[0340] 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 the various steps of the information transmission method mentioned in the above method embodiment.

[0341] In addition, the memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. The volatile or non-volatile storage device includes but is not limited to: a magnetic disk or an optical disk, an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a static random access memory (SRAM), a read-only memory (ROM), a magnetic memory, a flash memory, and a programmable read-only memory (PROM).

[0342] 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.

[0343] The present application also provides a network device, 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.

[0344] 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.

[0345] 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.

[0346] 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.

[0347] 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.

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

Claims

1. An information transmission method, characterized in that: The method 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.

2. The method according to claim 1, characterized in that The restoration reason information carries a reason value corresponding to the restoration reason, where 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; 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 small data transmission type received by the terminal is MT-SDT.

3. 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.

4. 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.

5. 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.

6. The method according to any one of claims 3 to 5, characterized in that: The determining of the restoration reason information includes: canceling the first service and determining first information, where 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.

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

8. The method according to claim 6, characterized in that The second information includes terminal assistance information UAI.

9. 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 10. 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 business; 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.

11. 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.

12. 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 the Packet Data Convergence Protocol (PDCP) entity associated with the 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 encrypting and / or securing data on a data resource bearer DRB, or the new key information is used for encrypting and / or securing signaling on a signaling resource bearer SRB; Continue the robust header compression ROHC function of DRB.

13. 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 the service type of the first service, and the second cause value is the service type of the second service; Sending a new cause value, where the new cause value is the service type of the second service; Selecting, according to a predefined priority order, MO data carrying the small data transmission initiated by the terminal or MT data carrying the 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 restoration reason information is a random access small data transmission RA-SDT resource or a preconfigured small data transmission CG-SDT resource, setting the cause 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.

14. 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.

15. 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.

16. 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 the small data transmission MT-SDT received by the terminal; The resource type indication information of the MT-SDT.

17. 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.

18. The method according to claim 17, characterized in that The triggering condition of the MT-SDT includes at least one of the following conditions: The paging message carries the terminal identifier and the MT-SDT association information; The system resource block SIB carries SDT indication information, and 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; Timed ahead 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.

19. The method according to claim 18, characterized in that The SDT indication information includes SDT common configuration or MT-SDT common configuration.

20. The method according to claim 17, wherein The sending of the radio resource control RRC recovery reason information to the network device includes: When the triggering condition of the MT-SDT is met, the restoration reason information is sent to the network device.

21. 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 small data transmission MT-SDT received by the terminal.

22. 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.

23. An information transmission method, characterized in that: The method is performed by a network device, and includes: Receiving the RRC recovery reason information sent by the terminal; The restoration reason information is used to inform the network device of the service type of the terminal.

24. The method according to claim 23, wherein The restoration reason information carries a reason value corresponding to the restoration reason, where 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; 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 small data transmission type received by the terminal is MT-SDT.

25. The method according to claim 23 or 24, characterized in that The restoration reason information is determined by the terminal based on at least 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.

26. 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.

27. 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.

28. 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.

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

30. The method according to claim 28, wherein The second information includes terminal assistance information UAI.

31. 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 32. 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 business; 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.

33. The method according to any one of claims 23 to 32, characterized in that The method further comprises: Receive 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.

34. 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.

35. The method according to claim 34, wherein 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.

36. The method according to claim 34, wherein The paging message carries at least one of the following information: Terminal identification; Resource configuration information of the small data transmission MT-SDT received by the terminal; The resource type indication information of the MT-SDT.

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

38. The method according to any one of claims 23 to 37, characterized in that The resources used by the restoration reason information include pre-configured CG resources or random access RA resources.

39. An information transmission device, characterized in that: The device comprises: A sending module, configured to send 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.

40. An information transmission device, characterized in that: The device comprises: A receiving module, configured to receive 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.

41. A terminal, characterized in that: The terminal 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 information transmission method according to any one of claims 1 to 22.

42. A network device, characterized in that: The network device 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 information transmission method according to any one of claims 23 to 38.

43. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which is used to be executed by a processor to implement the information transmission method according to any one of claims 1 to 38.

44. 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, is used to implement the information transmission method according to any one of claims 1 to 38.

45. A computer program, characterized in that The computer program includes computer instructions, and the computer instructions are used to implement the information transmission method according to any one of claims 1 to 38.

46. ​​A computer program product, characterized in that The computer program product includes computer instructions, which 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 according to any one of claims 1 to 38.

Images