Data transmission method, storage medium, electronic device and computer program product

Abstract

Provided in an embodiment of the present application are a data transmission method, a storage medium, an electronic device and a computer program product, the data transmission method comprising: a UE sending a data transmission request to a base station, the data transmission request carrying a UE ID and a service initiation or service registration request; and the UE receives the contention resolution identifier from the base station, and performs data transmission through the special signaling radio bearer. Through the embodiment of the invention, the problem that the data transmission process in the communication network is complicated in the related technology is solved, and the effects of reducing the complexity of the data transmission process in the communication network and improving the data transmission efficiency are achieved.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a data transmission method, a storage medium, an electronic device, and a computer program product. Background Technology

[0002] 6G networks will be integrated with communication, sensing, computing, and intelligence, requiring a large number of devices to connect to the network. These IoT devices are characterized by low cost and low power consumption. If every data transmission requires entering a connected state, it will consume a lot of power and increase complexity. Although Small Data Transmission (SDT) technology was introduced in Release 17, it still requires devices to support a connected state. The UE needs to enter the connected state first, receive the RRC connection release signaling, and then enter the inactive state (configuring a dedicated bearer identifier for small data transmission). Subsequently, if the UE has uplink data to transmit, it can initiate a connection reply request in the inactive state and transmit data in the inactive state.

[0003] The normal procedure for Random Access-Small Data Transmission (RA-SDT) in the current protocol is as follows: If the User Equipment (UE) needs to enter the SDT state for the first time, it must first enter the connected state, receive the Radio Resource Control (RRC) connection release signaling, and then transition to the inactive state (configuring the dedicated bearer identifier used for small data transmission). If the UE subsequently has uplink data to transmit, it can initiate an RRC Resume Request in the inactive state and transmit data thereafter. The initial entry process for the UE into the SDT state is lengthy, and if uplink data transmission is required later, an RRC Resume Request must be initiated again, making the small data transmission process complex. Summary of the Invention

[0004] This application provides a data transmission method, storage medium, electronic device, and computer program product to at least solve the problem of complex data transmission processes in communication networks in related technologies.

[0005] According to one embodiment of this application, a data transmission method is provided, comprising: a user equipment (UE) sending a data transmission request to a base station, the data transmission request carrying a user identifier (UE ID) and a service initiation or service registration request; the UE receiving a contention resolution identifier from the base station and transmitting data via a dedicated signaling radio bearer.

[0006] According to another embodiment of this application, a data transmission method is provided, comprising: a base station receiving a data transmission request from a user equipment (UE), the data transmission request carrying a user identifier (UE ID) and a service initiation or service registration request; the base station sending a contention resolution identifier to the UE and transmitting data via a dedicated signaling radio bearer.

[0007] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0008] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0009] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0010] The above embodiments of this application provide a data transmission method in which a UE sends a data transmission request to a base station, the data transmission request carrying a UE ID and a service initiation or service registration request; the UE receives a contention resolution identifier from the base station and transmits data via a dedicated signaling radio bearer. This solves the problem of complex data transmission processes in communication networks in related technologies, achieving the effect of reducing the complexity of data transmission processes in communication networks and improving data transmission efficiency. Attached Figure Description

[0011] Figure 1 This is a hardware structure block diagram of the mobile terminal that performs the data transmission method according to the method embodiment of this application;

[0012] Figure 2 This is a flowchart of a data transmission method according to an embodiment of this application;

[0013] Figure 3 This is another flowchart of the data transmission method according to an embodiment of this application;

[0014] Figure 4 This is a flowchart illustrating the data transmission method initiated by the UE for the first data transmission service according to an embodiment of this application.

[0015] Figure 5 This is a flowchart illustrating the process of SRBx sending data to the core network according to an embodiment of this application.

[0016] Figure 6This is another flowchart illustrating the process of SRBx sending data to the core network according to an embodiment of this application.

[0017] Figure 7 This is a flowchart illustrating the data transmission method initiated by the UE for a second data transmission service according to an embodiment of this application. Detailed Implementation

[0018] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0019] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0020] In related technologies, the normal RA-SDT process is as follows: If the UE needs to enter the SDT state for the first time, it needs to first enter the connected state, receive the RRC connection release signaling, and then transition to the inactive state (configuring a dedicated bearer identifier for small data transmission). If the UE subsequently has uplink data to transmit, it can initiate an RRC Resume Request in the inactive state and transmit data there. The initial entry process for the UE into the SDT state is relatively long. If uplink data still needs to be sent later, the RRC Resume Request is re-initiated, with the following procedure:

[0021] Step 1: gNB sends the SDT common configuration (sdt-ConfigCommon) in SIB1;

[0022] Step 2: When the UE enters the inactive state, the gNB configures the SDT resources through the RRC Release message;

[0023] Step 3: When the UE needs to restore the RRC connection, determine whether an SDT procedure can be initiated based on the conditions for "SDT Initiation". Assuming that RA-SDT can be initiated after the determination, proceed to Step 4;

[0024] Step 4: The UE uses the RA-SDT resources configured in Step 1 to send msg1;

[0025] Step 5, UE receives msg2;

[0026] Step 6, the UE sends msg3 (carrying RRC Resume Request + uplink small data (UL smalldata));

[0027] Step 7: The UE receives msg4 (writes UE Contention Resolution Identity MAC CE + optional DL small data). After the contention is resolved successfully, the UE is considered to have successfully entered the SDT process and can start receiving and sending subsequent small data.

[0028] Steps 8-9: Use dynamic scheduling to transmit subsequent small data.

[0029] Step 10: The gNB sends an RRC Release message to notify the UE to end the SDT process and re-enter the INACTIVE state.

[0030] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of the mobile terminal implementing the data transmission method in the embodiments of this application. For example... Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0031] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the data transmission method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the aforementioned method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0032] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0033] This application provides a data transmission method. Figure 2 This is a flowchart of a data transmission method according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps:

[0034] In step S202, the UE sends a data transmission request to the base station. The data transmission request carries the UE ID and a service initiation or service registration request.

[0035] In this embodiment of the application, the data transmission request sent by the UE to the base station can be a data transmission request corresponding to a small data transmission. The data transmission request (CFT Request) is a newly defined RRC message. Since it does not need to carry the RRC connection establishment request message, the CFT Request carries the UE ID and the traditional initiation request message. The traditional initiation request includes a service initiation or service registration request.

[0036] In one exemplary embodiment, the data transmission request is further used to establish a dedicated signaling radio bearer, which uses a default-configured Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), or Medium Access Control (MAC).

[0037] In this embodiment of the application, the aforementioned dedicated signaling radio bearer is also used to carry out subsequent processes such as secure establishment between the base station and the UE.

[0038] In one exemplary embodiment, the data transmission request is scrambled using a first temporary radio network identifier (tempCell Radio Network Temporary Identifier, temp C-RNTI), and the radio link control corresponding to the data transmission request uses transparent TM mode.

[0039] In this embodiment of the application, before the UE sends a data transmission request to the base station, it first initiates random access to the base station.

[0040] In one exemplary embodiment, before the UE sends a data transmission request to the base station, the method further includes: the UE sending a random access request to the base station based on random access resources dedicated to data transmission; and the UE receiving a random access response from the base station, wherein the random access response carries a first temporary radio network identifier.

[0041] In step S204, the UE receives a contention resolution identifier from the base station and transmits data via a dedicated signaling radio bearer.

[0042] In one exemplary embodiment, the UE receives a contention resolution identifier from the base station, including: the UE receiving the contention resolution identifier from the base station through a Media Access Control Code Element (MAC CE).

[0043] In one exemplary embodiment, the contention resolution identifier is scrambled with a second temporary radio network identifier, and after the UE successfully contends for the contention, the second temporary radio network identifier is converted to a second radio network identifier.

[0044] In this embodiment of the application, the first temporary wireless network identifier scrambling and the second temporary wireless network identifier scrambling are the same temporary wireless network identifier scrambling, and the distinction between "first" and "second" is only made in order.

[0045] In this embodiment, the base station uses MAC CE to transmit the contention resolution result. This contention resolution result can be transmitted using a conventional UE Contention Resolution Identity MAC CE, scrambled with a second temp C-RNTI. After a successful contention, the second temp C-RNTI becomes the second C-RNTI, and subsequent air interface scrambles using this second C-RNTI.

[0046] In one exemplary embodiment, after the UE receives a contention resolution identifier from the base station, the method further includes: determining that the terminal enters a first state, wherein the first state supports data transmission.

[0047] In one exemplary embodiment, the UE transmits data via a dedicated signaling radio bearer, including: in response to the UE initiating a data transmission service, the UE establishes a dedicated signaling radio bearer, activates radio access network security, and transmits data via the dedicated signaling radio bearer.

[0048] In this embodiment, the first state includes one of the following: idle state, inactive state, or a new RRC state. In the idle state, the UE and base station may or may not save context information; in the inactive state and the new RRC state, both the UE and base station save context information.

[0049] In this embodiment, after contention resolution, the base station and UE activate the security of the radio access network (AS) layer via the established dedicated radio signaling bearer (SRBx). After AS layer security activation, the network side and UE transmit UE service data via SRBx.

[0050] In one exemplary embodiment, after the UE transmits data via a dedicated signaling radio bearer, the process further includes the UE entering a second state corresponding to the first state, wherein the second state does not support data transmission.

[0051] In this embodiment of the application, after the first service transmission is completed, that is, after the data transmission is completed, the UE enters the second state. When the UE initiates the data transmission service again, the UE enters the first state from the second state to perform data transmission, thereby achieving the switching between performing data transmission and not performing data transmission. When not performing data transmission, power can be saved.

[0052] In one exemplary embodiment, in response to the UE re-initiating a data transmission service in the second state, the method further includes: the UE entering the first state, and, with the UE saving the context information, the UE resuming the dedicated signaling radio bearer and performing radio access network security activation, and simultaneously sending a data transmission request and at least part of the data to be transmitted to the base station through the dedicated signaling radio bearer.

[0053] In this embodiment of the application, the context information includes context information for dedicated signaling radio bearer and radio access network security activation.

[0054] In one exemplary embodiment, in response to the UE re-initiating a data transmission service in the second state, the method further includes: the UE entering a first state, and, if the UE has not saved context information, the UE establishing a dedicated signaling radio bearer based on the data transmission request and performing activation of radio access network security to send the data to be transmitted to the base station through the dedicated signaling radio bearer.

[0055] The above steps provide a data transmission method in which the UE sends a data transmission request to the base station, the request carrying the UE ID and a service initiation or registration request; the UE receives a contention resolution identifier from the base station and transmits data via a dedicated signaling radio bearer. This solves the problem of complex data transmission processes in communication networks in related technologies, achieving the effects of reducing the complexity of data transmission processes in communication networks and improving data transmission efficiency.

[0056] This application also provides a data transmission method, executed via a base station. Figure 3 This is another flowchart of the data transmission method according to an embodiment of this application, such as... Figure 3 As shown, the process includes the following steps:

[0057] In step S302, the base station receives a data transmission request from the UE, which carries the UE ID and a service initiation or service registration request.

[0058] In this embodiment of the application, the data transmission request received by the base station from the UE can be a data transmission request corresponding to a small data transmission. The data transmission request (CFT Request) is a newly defined RRC message. Since it does not need to carry the RRC connection establishment request message, the CFT Request carries the UE ID and the traditional initiation request message. The traditional initiation request includes a service initiation or service registration request.

[0059] In one exemplary embodiment, the data transmission request is further used to establish a dedicated signaling radio bearer, which uses a default-configured packet data convergence protocol, radio link control protocol, or media access control protocol.

[0060] In this embodiment of the application, the aforementioned dedicated signaling radio bearer is also used to carry out subsequent processes such as secure establishment between the base station and the UE.

[0061] In one exemplary embodiment, before the base station receives a data transmission request from the UE, the method further includes: the base station sending a paging instruction to the UE, the paging instruction carrying a first field, the first field being used to instruct the UE to perform data transmission.

[0062] In this embodiment, CFT supports both UE-triggered and network-triggered transmission. When downlink data arrives, the network informs the UE to initiate connectionless transmission via paging. A new field, the first field, is added to paging to distinguish whether connectionless transmission is triggered or traditional RRC connection establishment is initiated.

[0063] In step S304, the base station sends a contention resolution identifier to the UE and transmits data through a dedicated signaling radio bearer.

[0064] In one exemplary embodiment, data transmission via a dedicated signaling radio bearer includes: a base station receiving transmission data from a UE via the dedicated signaling radio bearer and sending the transmission data to the core network.

[0065] In this embodiment of the application, after receiving the dedicated signaling radio bearer SRBx, the base station will further forward the data carried by SRBx to the core network.

[0066] In one exemplary embodiment, the base station transmits data to the core network, including: the base station transmits the data to the Access Mobility Function (AMF), forwards it via the AMF to the Session Management Function (SMF), and forwards it via the SMF to the User Plane Function (UPF).

[0067] In one exemplary embodiment, the base station transmits data to the core network, including: the base station transmits the data to the UPF.

[0068] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0069] This embodiment also provides a data transmission device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0070] The data transmission apparatus provided in this application embodiment can be installed in a UE, including a transmitting module and a first transmission module. The transmitting module is configured to send a data transmission request to a base station, the data transmission request carrying a UE ID and a service initiation or service registration request. The first transmission module is configured to receive a contention resolution identifier from the base station and perform data transmission via a dedicated signaling radio bearer.

[0071] The data transmission apparatus provided in this application embodiment can be located in a base station and includes a receiving module and a second transmitting module. The receiving module is configured to receive data transmission requests from a UE, the data transmission requests carrying a UE ID and a service initiation or service registration request. The second transmitting module is configured to send a contention resolution identifier to the UE and transmit data via a dedicated signaling radio bearer.

[0072] In the embodiments of this application, the above-mentioned data transmission device may also include different modules, and the naming and functional division of the modules may be selected in different ways according to the actual situation, without specific restrictions.

[0073] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0074] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0075] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0076] Embodiments of this application also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0077] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0078] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0079] In one exemplary embodiment, the computer program product described above includes a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the methods described in various embodiments of this application.

[0080] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0081] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0082] To enable those skilled in the art to better understand the technical solutions of this application, the following description is provided in conjunction with different embodiments.

[0083] Example 1

[0084] Since IoT terminals send relatively small amounts of data and the duration of data transmission is also relatively short, the data service initiation process required for IoT terminals to transmit data should be streamlined as much as possible.

[0085] Figure 4 This is a flowchart illustrating the data transmission method initiated by the UE for the first data transmission service according to an embodiment of this application. Figure 4 As shown, the process for small data transmission includes the following steps:

[0086] S1, CFT process initiated.

[0087] CFT stands for Connection Free Transmission.

[0088] S2, UE Random Access (RA) Initiation Procedure (msg1).

[0089] After receiving the SIB message sent by the network side and obtaining resource information, the UE uses the RA resource unique to CFT configured in the SIB to send a random access request to the base station.

[0090] S3, RA authorization (msg2).

[0091] The network side (base station) identifies the user as a CFT user through the specific RA resource in msg1. The base station replies to the UE with msg2 and allocates a larger Transport Block Size (TB Size) through the Uplink Grant (UL Grant) in msg2. The grant size can accommodate the request. In msg2, the base station allocates a temporary radio network identifier scrambled temp C-RNTI to the UE. Here, temp C-RNTI is the first temp C-RNTI in the above embodiment.

[0092] S4, CFT Request.

[0093] In this embodiment, the CFT Request is the data transmission request in the above embodiments.

[0094] In this embodiment, the CFT Request, or data transmission request, is a newly defined RRC message. Since it does not need to carry an RRC connection establishment request message, the CFT Request carries the UE ID and a traditional initiation request message, uses first temp C-RNTI scrambling, employs transparent TM mode for Radio Link Control (RLC), and uses SRB0 for transmission. The traditional initiation request includes service initiation or service registration requests.

[0095] In one embodiment, the CFT Request not only sends the UE ID and a conventional initiation request, but also establishes a CFT-specific SRBx connection by default.

[0096] In this embodiment of the application, the dedicated signaling radio bearer SRBx of the CFT is used to carry out processes such as the secure establishment between the subsequent Radio Access Node (RAN) and the UE.

[0097] In this embodiment of the application, compared with the conventional initiation process, the initiation request is sent from msg5 to msg3, which reduces the number of signaling messages.

[0098] S5, the competition resolution process.

[0099] The network side uses MAC CE to send the contention result. This contention resolution result can be sent using the traditional UEContention Resolution Identity MAC CE, scrambled with temp C-RNTI. After a successful contention, tempC-RNTI becomes C-RNTI, and subsequent air interfaces use this C-RNTI for scrambling. Here, temp C-RNTI is the second temp C-RNTI in the above embodiment, and C-RNTI is the second C-RNTI in the above embodiment.

[0100] S10. After the contention is resolved, the network side and the UE activate the security of the Access Stratum (AS) layer through the established default SRBx.

[0101] After AS layer security activation is completed, the network side and UE transmit UE service data through SRBx. In this embodiment, SRBx is defined as a special type of SRB. After receiving SRBx, the base station will further forward the data carried by SRBx to the core network.

[0102] It should be noted that, in this embodiment, as Figure 4 As shown, steps S6 to S9 are omitted; steps S6 to S9 are standard steps.

[0103] Figure 5 This is a flowchart illustrating the process of SRBx sending data to the core network according to an embodiment of this application. Figure 5 As shown, SRBx is further delivered to AMF, then forwarded by AMF to SMF, and then forwarded by SMF to UPF.

[0104] Figure 6 This is another flowchart illustrating the process of SRBx sending data to the core network according to an embodiment of this application, as follows: Figure 6 As shown, the data carried by SRBx can be directly delivered from the base station to the UPF, and the UPF parses the data packet to obtain the UE's data.

[0105] In this embodiment, since no connection is established over the air interface, the UE does not need to send an RRC setup request signaling, and the base station does not need to reply with an RRC setup message, thus reducing the number of signaling messages. After the UE's capabilities and security are established, following the conventional procedure, the base station sends an RRC reconfiguration message to the UE and establishes the relevant parameters of the DRB through the RRC reconfiguration message (some parameters use default values), thus simplifying the configuration.

[0106] In this embodiment, CFT supports both UE-triggered and network-triggered transmission. When downlink data arrives, the network informs the UE to initiate connectionless transmission via paging. A new field, the first field, is added to paging to distinguish whether connectionless transmission is triggered or traditional RRC connection establishment is initiated.

[0107] It should be noted that the data transmission method provided in this application embodiment is not only applicable to CFT small data transmission, but can also be used in conventional random access procedures.

[0108] Example 2

[0109] In this embodiment, the scenario where the UE initiates data transmission service again is described.

[0110] Figure 7 This is a flowchart illustrating the data transmission method initiated by the UE for a second data transmission service according to an embodiment of this application. Figure 7 As shown, the process for small data transmission includes the following steps:

[0111] S1, CFT process initiated.

[0112] CFT stands for Connection Free Transmission.

[0113] S2, UE Random Access (RA) Initiation Procedure (msg1).

[0114] After receiving the SIB message sent by the network side and obtaining resource information, the UE uses the RA resource unique to CFT configured in the SIB to send a random access request to the base station.

[0115] S3, RA authorization (msg2).

[0116] The network side (base station) identifies the user as a CFT user through the specific RA resource in msg1. The base station replies to the UE with msg2 and allocates a larger Transport Block Size (TB Size) through the Uplink Grant (UL Grant) in msg2. The grant size can accommodate the request. In msg2, the base station allocates a temporary radio network identifier scrambled temp C-RNTI to the UE. Here, temp C-RNTI is the first temp C-RNTI in the above embodiment.

[0117] S4. Data transmission for data transmission services that are carried out again through a dedicated signaling radio bearer based on the state of the UE's data transmission.

[0118] The RRC state (i.e., the first state in the above embodiments) in which the UE transmits data in this application can be an idle state, an inactive state, or a new RRC state. Before the UE initiates a data transmission request for the first time, the UE is in an idle state:

[0119] In one embodiment, in response to the UE's RRC state being idle during data transmission, after contention resolution is completed and both the UE and the network side establish a dedicated signaling radio bearer for data transmission, the UE state becomes idle-ready-to-transmit data state. After the UE finishes transmitting data, the UE transitions from the idle-ready-to-transmit data state to the idle state.

[0120] In one embodiment, in response to the UE being in an inactive RRC state during data transmission, after contention resolution is completed and both the UE and the network side have established a dedicated signaling radio bearer for data transmission, the UE state becomes inactive-ready-to-transmit data state. After the UE finishes transmitting data, the UE transitions from the inactive-ready-to-transmit data state to the inactive state.

[0121] In this embodiment, when the UE enters an inactive state, the UE restores the dedicated signaling radio bearer and performs radio access network security activation, simultaneously sending data transmission requests and data to be transmitted to the base station through the dedicated signaling radio bearer. Figure 7 As shown, the UE simultaneously sends a data transmission request (CFT Request) and transmitted data (UL data).

[0122] In one embodiment, in response to the UE's data transmission being in a new RRC state, after contention resolution is completed and both the UE and the network side have established a dedicated signaling radio bearer for data transmission, the UE state becomes the new RRC_transmittable data state. After the UE finishes transmitting data, the UE transitions from the inactive_transmittable data state to the new RRC state.

[0123] In this embodiment of the application, when the UE enters a new RRC state, the UE restores the dedicated signaling radio bearer and performs radio access network security activation, simultaneously sending data transmission requests and data to be transmitted to the base station through the dedicated signaling radio bearer. Figure 7 As shown, the UE simultaneously sends a data transmission request (CFT Request) and transmitted data (UL data).

[0124] In one embodiment, if the UE supports saving its context information after data transmission, then upon the next service initiation, the saved context information is directly used to restore the established dedicated signaling radio bearer and perform AS activation security. If the UE does not support saving its context information after data transmission, then upon the next service initiation, the UE needs to re-establish the dedicated signaling radio bearer.

[0125] In the embodiments of this application, the idle_data-transmittable state allows the UE to save or not save context information after data transmission ends; the inactive_data-transmittable state allows the UE to save context information after data transmission ends; and the new RRC state_data-transmittable state allows the UE to save context information after data transmission ends.

[0126] In this embodiment, after the UE data transmission is completed, if both the network side and the UE support saving the UE context information, the UE context information includes at least the context information of the dedicated signaling radio bearer and the radio access network security activation. When the UE needs to initiate service transmission again, the UE restores the dedicated signaling radio bearer and performs radio access network security activation through the saved context, and simultaneously sends a data transmission request and the data to be transmitted to the base station through the dedicated signaling radio bearer. Figure 7 As shown, the UE simultaneously sends a data transmission request (CFT Request) and transmitted data (UL data).

[0127] S5. The base station sends a Contention Resolution Identifier (MAC CE) to the UE.

[0128] like Figure 7 As shown, because the UE sent a data transmission request (CFT Request) to the base station in S4, the base station will also send a contention resolution identifier (MAC CE) to the UE in S5. Unlike when the UE initiates a data transmission service again corresponding to the UE state, this is not the first time the base station has sent the MAC CE to the UE.

[0129] like Figure 7 As shown, after S5, the transmission process of uplink and downlink data is also involved. Because there is a lot of data transmission between the UE and the base station, although the UE sends a data transmission request (CFTRequest) and transmission data (UL data) to the base station at the same time in S4, it cannot send all the transmission data through S4. Therefore, data transmission needs to continue in the following steps.

[0130] It should be noted that msg1, msg2, ... msg5 in the embodiments of this application are commonly used message representation forms in the field of communication, and their specific contents will not be described in detail here.

[0131] In summary, this application provides a data transmission method that, compared to SDT, simplifies the initial service initiation process for the UE: by receiving the SIB, receiving the Radio Resource Control Reconfiguration (RRC Reconfiguration) message, sending the CFT Request, activating AS security, and receiving the RRC Reconfiguration message, small data packets can be transmitted, and the service initiation process can be resumed by simply sending the CFT Request.

[0132] In this embodiment, the CFT registration and initiation process differs from the conventional process in the following ways: First, the CFT registration / initiation process may not establish an RRC connection (SRB1), thus eliminating the need to transmit RRC Setup Request, RRC Setup, or RRC Setup Complete signaling, thereby simplifying it to CFT Request or MAC CE. In this embodiment, the CFT Request, as a new type of RRC signaling, directly carries the registration request or service request and the UE ID, and establishes a dedicated control plane connection for CFT by default. Second, it is not necessary to release and store SDT-specific data through the RRC connection. Third, data is transmitted using SRBx, without needing to configure DRB bearer transmission via RRCReconfiguration.

[0133] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A data transmission method, characterized in that, include: The user equipment (UE) sends a data transmission request to the base station. The data transmission request carries the user identifier (UE ID) and a service initiation or service registration request. The UE receives a contention resolution identifier from the base station and transmits data via a dedicated signaling radio bearer.

2. The method according to claim 1, characterized in that, in, The data transmission request is also used to establish the dedicated signaling radio bearer, which uses a default-configured packet data aggregation protocol, radio link control protocol, or media access control protocol.

3. The method according to claim 1, characterized in that, in, The data transmission request is scrambled using a first temporary radio network identifier, and the radio link control corresponding to the data transmission request uses the transparent TM mode.

4. The method according to claim 3, characterized in that, Before the UE sends a data transmission request to the base station, the method further includes: The UE sends a random access request to the base station based on the random access resources dedicated to data transmission; The UE receives a random access response from the base station, the random access response carrying the first temporary radio network identifier.

5. The method according to claim 1, characterized in that, The UE receives a contention resolution identifier from the base station, including: The UE receives the contention resolution identifier from the base station via the Media Access Control Element (MAC CE).

6. The method according to claim 5, characterized in that, in, The contention resolution identifier is scrambled with a second temporary radio network identifier. After the UE successfully competes, the second temporary radio network identifier is converted to a second radio network identifier.

7. The method according to claim 5, characterized in that, After the UE receives the contention resolution identifier from the base station, the method further includes: The terminal is determined to have entered a first state, wherein the first state supports data transmission.

8. The method according to claim 7, characterized in that, The UE transmits data via a dedicated signaling radio bearer, including: In response to the UE initiating a data transmission service, the UE establishes the dedicated signaling radio bearer, activates radio access network security, and transmits data through the dedicated signaling radio bearer.

9. The method according to claim 8, characterized in that, After the UE transmits data via the dedicated signaling radio bearer, the method further includes: The UE enters a second state corresponding to the first state, wherein the second state does not support data transmission.

10. The method according to claim 9, characterized in that, In response to the UE re-initiating a data transmission service in the second state, the method further includes: When the UE enters the first state, and with the UE having saved the context information, the UE restores the dedicated signaling radio bearer and performs radio access network security activation, and simultaneously sends the data transmission request and at least part of the data to be transmitted to the base station through the dedicated signaling radio bearer.

11. The method according to claim 9, characterized in that, In response to the UE re-initiating a data transmission service in the second state, the method further includes: The UE enters the first state, and if the UE has not saved the context information, the UE establishes the dedicated signaling radio bearer based on the data transmission request and performs activation of radio access network security to send the data to be transmitted to the base station through the dedicated signaling radio bearer.

12. A data transmission method, characterized in that, include: The base station receives a data transmission request from a user equipment (UE), the data transmission request carrying a user identifier (UE ID) and a service initiation or service registration request; The base station sends a contention resolution identifier to the UE and transmits data via a dedicated signaling radio bearer.

13. The method according to claim 12, characterized in that, in, The data transmission request is also used to establish the dedicated signaling radio bearer, which uses a default-configured packet data aggregation protocol, radio link control protocol, or media access control protocol.

14. The method according to claim 12, characterized in that, Before the base station receives a data transmission request from the user equipment (UE), the method further includes: The base station sends a paging command to the UE, the paging command carrying a first field, the first field being used to instruct the UE to perform data transmission.

15. The method according to claim 12, characterized in that, The data transmission via dedicated signaling radio bearer includes: The base station receives transmission data from the UE through the dedicated signaling radio bearer and sends the transmission data to the core network.

16. The method according to claim 15, characterized in that, The base station sends the transmitted data to the core network, including: The base station sends the transmitted data to the Access Mobility Function (AMF), which then forwards it to the Session Management Function (SMF), and the SMF forwards it to the User Plane Function (UPF).

17. The method according to claim 15, characterized in that, The base station sends the transmitted data to the core network, including: The base station sends the transmitted data to the UPF.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 11, or implements the steps of the method described in any one of claims 12 to 17.

19. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 11, or the steps of the method described in any one of claims 12 to 17.

20. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 11, or the steps of the method described in any one of claims 12 to 17.

Images