WO2021147015A1

WO2021147015A1 - Method and apparatus for message transmission

Info

Publication number: WO2021147015A1
Application number: PCT/CN2020/073870
Authority: WO
Inventors: 黄曲芳; 曾清海
Original assignee: 华为技术有限公司
Priority date: 2020-01-22
Filing date: 2020-01-22
Publication date: 2021-07-29

Abstract

The present application provides a method and apparatus for message transmission. The method for message transmission comprises: a terminal device receives at least one first segmented message included in a first downlink radio resource control (RRC) message from a network device; the terminal device sends a request message to the network device to request the network device to send at least one second segmented message included in the first downlink RRC message. By means of the technical solution provided by the present application, downlink segmented messages can be sent to a terminal device in time, thereby improving the downlink oversized RRC message transmission performance.

Description

Method and device for message transmission

Technical field

This application relates to the field of communications, and more specifically, to a method and device for message transmission.

Background technique

In the 5th generation (5G) communication system, the existing protocol limits the size of data packets transmitted via the wireless interface to be less than or equal to 9000 bytes (bytes). With the development of communication technology, it may be The size of the transmitted data packet is limited to less than or equal to 65536 bytes, which means that the size of the data packet transmitted via the wireless interface may be limited to a certain threshold by the protocol. The internal modules of the network equipment and terminal equipment can restrict the transmission of data packets according to the provisions of the protocol. For example, the network equipment and terminal equipment check the data packets that need to be transmitted through the wireless interface, and report an error or stop transmission as long as the size limit is exceeded.

Since the threshold of 9000 bytes is much larger than the maximum transmission size (1500 bytes) of data packets at the Internet protocol (IP) layer and Ethernet layer, usually the data packets sent by the terminal device are transmitted through the IP layer or the Ethernet layer. , Has been segmented, the data packet transmitted to the wireless interface will not be greater than 9000 bytes. However, the RRC message generated by the radio resource control (RRC) entity on the side of the network device or the terminal device does not pass through the IP layer or when it reaches the service data adaptation protocol (SDAP) layer and starts transmission. The transmission at the Ethernet layer will not be segmented, and RRC messages with data packet sizes exceeding the threshold may appear.

For the uplink oversize RRC message, a segmentation method is adopted in the existing communication system, so that each uplink segment RRC message of the uplink oversize RRC message does not exceed the size limit. However, there is no provision for the processing of the downlink oversize RRC message, so how to segment the downlink oversize RRC message has become an urgent problem to be solved.

Summary of the invention

The present application provides a method and device for message transmission, in order to improve downlink oversize RRC message transmission performance.

In the first aspect, a method for message transmission is provided. The method for message transmission may be executed by a terminal device, or may also be executed by a chip or circuit provided in the terminal device, which is not limited in this application. For ease of description, the following takes the execution by the terminal device as an example for description.

The method for message transmission includes:

The terminal device receives at least one first segment message from the network device; the terminal device sends a request message to the network device, and the request message is used to request the network device to send at least one second segment message, where the first downlink The unlimited resource control RRC message includes the at least one first segment message and the at least one second segment message.

According to the method for message transmission provided by the embodiments of the present application, after receiving at least one first segment message corresponding to the first RRC message sent by the network device, the terminal device will promptly notify the network device that the terminal device has not received the delivery At least one second segment message corresponding to the received first RRC message enables the downlink segment message to be sent to the terminal device in time, which improves the downlink oversize RRC message transmission performance.

With reference to the first aspect, in some implementations of the first aspect, the foregoing terminal device sending a request message to the network device includes: the RRC entity of the terminal device sends a first notification message to the radio link control RLC entity of the terminal device , The first notification message is used to notify the RLC entity to send the request message to the network device; and/or the RRC entity of the terminal device sends a second notification message to the media access control MAC entity of the terminal device, and the second The notification message is used to notify the MAC entity to send the request message to the network device.

The above-mentioned terminal device sending a request message to the network device may be that the RRC entity in the terminal device sends the request message to the network device through the RLC entity in the terminal device, or the RRC entity in the terminal device sends the request message to the network device through the MAC entity in the terminal device. Send the request message to the network device. Provides a way for different terminal devices to send request messages to network devices, increasing the flexibility of the solution.

With reference to the first aspect, in some implementations of the first aspect, when the terminal device receives the first first segment message from the network device, the method further includes: the terminal device starts a timer; When the terminal device receives all the second segment messages during the timer operation, the terminal device stops the timer; when the timer expires, the terminal device does not receive all the second segment messages, the terminal device stops the timer; The terminal device determines that the reception of the first downlink RRC message fails.

The above-mentioned terminal device may start a timer when receiving the first first segment message. The timer may be preset by the terminal device or agreed between the terminal device and the network device. Not limited.

In the case that the terminal device receives all the second segment messages in the at least one second segment message during the running period of the timer, the terminal device can restart the timer or stop the timer; or the terminal device can When the timer expires, if all the second segment messages in the at least one second segment message are still not received, the terminal device can consider that the transmission of the first RRC message has failed, which can prevent the terminal device from waiting to receive the unreceived message. The second segment of the message takes too long, which affects the timeliness of the transmission of the downlink RRC message.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the terminal device sends a first duration to the network device, wherein the start time of the first duration is the timer start time, and the The termination time of the first duration is the time when the terminal device receives the last second segment message in the at least one second segment message.

Further, if the terminal device receives all the second segment messages during the above-mentioned timer operation period, in this case, the terminal device can report the first duration to the network device, so that the network device can be based on the first time period. The duration optimizes the transmission power, modulation and coding scheme (MCS) of subsequent downlink RRC messages, etc., thereby improving the transmission efficiency of downlink RRC messages.

With reference to the first aspect, in some implementations of the first aspect, before the terminal device determines that the reception of the first downlink RRC message fails, the method further includes: the RRC entity of the terminal device reports to the PDCP entity of the terminal device Send a first message, the first message is used to instruct the PDCP entity to report a second message, where the second message is a buffered message in the PDCP entity’s signaling bearer buffer; when the second message includes the at least When a part of the second segment message is part of a second segment message, the method further includes: the terminal device discards the at least one first segment message and the received part of the second segment message.

According to the method for message transmission provided in the embodiments of the present application, in the case that the terminal device has not received all the second segment information after the above-mentioned timer expires, the RRC entity of the terminal device can notify the PDCP entity of the terminal device to report The buffered message is discarded, and the second segment message reported by the PDCP entity and at least one first segment message that has been received are discarded, and it is determined that the transmission of the first downlink RRC message fails.

With reference to the first aspect, in some implementations of the first aspect, the terminal device receiving at least one first segment message from the network device includes: the terminal device receives a plurality of first segment messages from the network device, and The multiple first segment messages include at least one third segment message and at least one fourth segment message; the method further includes: the PDCP entity of the terminal device reports the at least one third segment to the RRC entity of the terminal device Message and save the at least one fourth segment message in the PDCP entity of the terminal device, where the index of the third segment message is smaller than the index of the fourth segment message, and the index of the fourth segment message is greater than The index of the second segment message.

According to the method for message transmission provided in the embodiment of the present application, the PDCP entity of the terminal device sends the first segment message with a small index to the RRC entity of the terminal device when receiving multiple first segment messages, Saving the first segment message with a large index in the PDCP entity can ensure that the multiple segment messages corresponding to the first downlink RRC message are sequentially transmitted to the RRC entity of the terminal device.

With reference to the first aspect, in some implementation manners of the first aspect, the request message includes a MAC message and/or an RLC message.

The specific form of the above request message may be multiple message types such as MAC message and/or RLC message, which can improve the flexibility of the solution.

With reference to the first aspect, in some implementations of the first aspect, before the terminal device receives at least one first segment message from the network device, the method further includes: the terminal device sends the first capability information to the network device, The first capability information is used to indicate that the terminal device supports downlink RRC message segmentation.

According to the method for message transmission provided in the embodiments of the present application, the terminal device can report whether it supports downlink RRC message segmentation capability to the network device, so that the network device can learn the capability of the terminal device, thereby improving the downlink segment RRC message transmission Probability of success.

With reference to the first aspect, in some implementations of the first aspect, the first capability information is further used to indicate that the terminal device supports uplink RRC message segmentation; or, the method further includes: the terminal device sends the first capability information to the network device. Second capability information, where the second capability information is used to indicate that the terminal device supports uplink RRC message segmentation.

The terminal device can simultaneously report whether it supports downlink RRC message segmentation and whether it supports uplink RRC message segmentation through one message; the terminal device can also report whether it supports downlink RRC message segmentation and whether it supports uplink RRC message segmentation through two different messages. Message segmentation. Provides different reporting methods to improve the flexibility of the plan. In addition, reporting whether to support downlink RRC message segmentation and whether to support uplink RRC message segmentation separately in two messages can increase the possibility of successful reporting.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the terminal device receives first indication information from the network device, where the first indication information is used to indicate that the network device supports downlink RRC messages Segmented.

According to the method for message transmission provided in the embodiments of the present application, the network device may send first indication information to the terminal device, indicating whether the network device supports downlink RRC message segmentation, so that the terminal device can learn the capabilities of the network device.

In the second aspect, a method for message transmission is provided. The method for message transmission may be executed by a network device, or may also be executed by a chip or circuit provided in the network device, which is not limited in this application. For ease of description, the following takes the execution by a network device as an example for description.

The method for message transmission includes:

The network device sends at least one first segment message to the terminal device; the network device receives a request message from the terminal device, and the request message is used to request the network device to send at least one second segment message, where the first downlink The unlimited resource control RRC message includes the at least one first segment message and the at least one second segment message.

According to the method for message transmission provided by the embodiment of the present application, after receiving at least one first segment message corresponding to the first RRC message sent by the network device, the terminal device will promptly notify the network device that the terminal device has not received the delivery At least one second segment message corresponding to the received first RRC message enables the downlink segment message to be sent to the terminal device in time, which improves the downlink oversize RRC message transmission performance.

With reference to the second aspect, in some implementations of the second aspect, the network device receives the first duration from the terminal device, wherein the start time of the first duration is the terminal device receiving the first first duration. When the message is segmented, the end time of the first duration is the time when the terminal device receives the last second segment message in the at least one second segment message.

If the terminal device receives all the second segment messages during the above-mentioned timer operation period, in this case, the terminal device can report the first duration to the network device, so that the network device knows that the terminal device receives the first first segment message. The time interval between the time of a segment message and the time of the last second segment message.

With reference to the second aspect, in some implementations of the second aspect, the method further includes: the network device determines the power and/or modulation and coding strategy MCS for transmitting the downlink RRC message based on the first duration.

The network device can optimize the transmission power, MCS, etc. of subsequent downlink RRC messages based on the first duration, thereby improving the transmission efficiency of the downlink RRC messages.

With reference to the second aspect, in some implementations of the second aspect, the request message includes a medium access control MAC message and/or a radio link control RLC message.

With reference to the second aspect, in some implementations of the second aspect, before the network device sends at least one first segment message to the terminal device, the method further includes: the network device receives the first capability from the terminal device Information, the first capability information is used to indicate that the terminal device supports downlink RRC message segmentation.

With reference to the second aspect, in some implementations of the second aspect, the first capability information is also used to indicate that the terminal device supports uplink RRC message segmentation; or, the method further includes: the network device receives data from the terminal device The second capability information is used to indicate that the terminal device supports uplink RRC message segmentation.

With reference to the second aspect, in some implementation manners of the second aspect, the method further includes:

The network device sends first indication information to the terminal device, where the first indication information is used to indicate that the network device supports downlink RRC message segmentation.

According to the method for message transmission provided by the embodiments of the present application, the network device can send the first indication information to the terminal device, indicating whether the network device supports downlink RRC message segmentation, so that the terminal device can learn the capabilities of the network device.

In a third aspect, an apparatus for message transmission is provided. The apparatus for message transmission includes a processor, configured to implement the function of the terminal device in the method described in the first aspect.

Optionally, the apparatus for message transmission may further include a memory, which is coupled with the processor, and the processor is configured to implement the function of the terminal device in the method described in the first aspect.

In a possible implementation, the memory is used to store program instructions and data. The memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of the terminal device in the method described in the first aspect.

Optionally, the apparatus for message transmission may further include a communication interface, and the communication interface is used for the apparatus for message transmission to communicate with other devices. When the device for message transmission is a terminal device, the transceiver may be a communication interface or an input/output interface.

In a possible design, the apparatus for message transmission includes a processor and a communication interface, which are used to implement the function of the terminal device in the method described in the first aspect above, and specifically include:

The processor uses the communication interface to communicate with the outside;

The processor is used to run a computer program, so that the device implements any one of the methods described in the first aspect.

It can be understood that the exterior may be an object other than the processor, or an object other than the device.

In another implementation manner, when the device for message transmission is a chip or a chip system, the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, or pin on the chip or chip system. Or related circuits, etc. The processor can also be embodied as a processing circuit or a logic circuit.

In a fourth aspect, an apparatus for message transmission is provided. The apparatus for message transmission includes a processor for implementing the function of the network device in the method described in the second aspect.

Optionally, the apparatus for message transmission may further include a memory, which is coupled with the processor, and the processor is configured to implement the function of the network device in the method described in the second aspect.

In a possible implementation, the memory is used to store program instructions and data. The memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of the network device in the method described in the second aspect.

Optionally, the apparatus for message transmission may further include a communication interface, and the communication interface is used for the apparatus for message transmission to communicate with other devices. When the device for message transmission is a network device, the communication interface is a transceiver, an input/output interface, or a circuit.

In a possible design, the apparatus for message transmission includes: a processor and a communication interface, which are used to implement the function of the network device in the method described in the second aspect above, and specifically include:

The processor uses the communication interface to communicate with the outside;

The processor is used to run a computer program, so that the device implements any of the methods described in the second aspect.

In another possible design, the device for message transmission is a chip or a chip system. The communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

In a fifth aspect, a computer-readable storage medium is provided with a computer program stored thereon. When the computer program is executed by a communication device, the communication device realizes the first aspect and any one of the possible implementation manners of the first aspect method.

In a sixth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a communication device, the communication device enables the communication device to implement the second aspect and any of the possible implementation manners of the second aspect method.

In a seventh aspect, a computer program product containing instructions is provided, when the instructions are executed by a computer, the communication device realizes the first aspect and the method in any possible implementation manner of the first aspect.

In an eighth aspect, a computer program product containing instructions is provided, which when executed by a computer, causes a communication device to implement the second aspect and the method in any possible implementation manner of the second aspect.

In a ninth aspect, a communication system is provided, including the apparatus for message transmission shown in the third aspect and the apparatus for message transmission shown in the fourth aspect.

Description of the drawings

FIG. 1 is a schematic diagram of a system 100 applicable to the method for message transmission according to the embodiment of the present application.

Fig. 2 is a schematic diagram of a processing flow of data bearer and signaling bearer provided by the present application.

Figure 3 is a schematic diagram of an uplink oversize RRC message segmentation.

Figure 4 is a schematic diagram of a terminal device transmitting an uplink RRC message to a network device.

Fig. 5 is a schematic diagram of another terminal device transmitting an uplink RRC message to a network device.

Fig. 6 is a schematic flowchart of a method for message transmission provided by an embodiment of the present application.

FIG. 7 is a schematic diagram of transmitting a downlink RRC segment message according to an embodiment of the present application.

FIG. 8 is a schematic diagram of reporting a first duration according to an embodiment of the present application.

FIG. 9 is a schematic diagram of reporting a cached message according to an embodiment of the present application.

FIG. 10 is a schematic diagram of an apparatus 1000 for message transmission provided by the present application.

FIG. 11 is a schematic structural diagram of a terminal device 1100 applicable to an embodiment of the present application.

FIG. 12 is a schematic diagram of an apparatus 1200 for message transmission provided by the present application.

FIG. 13 is a schematic structural diagram of a network device 1300 applicable to an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below in conjunction with the accompanying drawings.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (time division duplex) , TDD), worldwide interoperability for microwave access (WiMAX) communication system, 5G system, new radio (NR), etc. The technical solution provided in this application can also be applied to future communication systems, such as the sixth-generation mobile communication system. The communication system can also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, and a device-to-device (D2D) communication system. Internet of things (IoT) communication system or other communication systems.

The terminal equipment (terminal equipment) in the embodiments of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, and a user equipment. (user equipment, UE), terminal (terminal), wireless communication equipment, user agent, or user device. The terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (personal digital assistant, PDA), with wireless communication Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminals in the public land mobile network (PLMN) that will evolve in the future Devices or terminal devices in the future Internet of Vehicles, etc., which are not limited in the embodiment of the present application.

As an example and not a limitation, in the embodiments of the present application, wearable devices can also be referred to as wearable smart devices. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, Gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets and smart jewelry for physical sign monitoring.

In addition, in the embodiments of the present application, the terminal device can also be a terminal device in the IoT system. IoT is an important part of the development of information technology in the future. Its main technical feature is to connect objects to the network through communication technology to realize man-machine Interconnection, an intelligent network of interconnection of things. In the embodiment of the present application, the IOT technology can achieve massive connections, deep coverage, and power saving of the terminal through, for example, narrowband (NB) technology.

In addition, in the embodiments of this application, the terminal equipment may also include sensors such as smart printers, train detectors, gas stations, etc. The main functions include collecting data (part of the terminal equipment), receiving control information and downlink data from network equipment, and sending electromagnetic waves. , To transmit uplink data to network equipment.

The network device in the embodiment of the present application may be any communication device with a wireless transceiving function that is used to communicate with a terminal device. The equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (Node B, NB), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point in wireless fidelity (WIFI) system (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be 5G systems, such as gNB in NR systems, or transmission points (TRP or TP), base stations in 5G systems One or a group of (including multiple antenna panels) antenna panels, or, may also be a network node constituting a gNB or transmission point, such as a baseband unit (BBU), or a distributed unit (DU).

In some deployments, the network device in the embodiment of the present application may refer to a centralized unit (CU) or a distributed unit (DU), or the network device includes a CU and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implements the functions of the RRC layer and the packet data convergence protocol (PDCP) layer. The DU is responsible for processing the physical layer protocol and real-time services, and realizes the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , Or, sent by DU+AAU. It can be understood that the network device may be a device that includes one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into network equipment in an access network (radio access network, RAN), and the CU can also be divided into network equipment in a core network (core network, CN), which is not limited in this application.

Further, the CU can also be divided into the central unit of the control plane (CU-CP) and the central unit of the user plane (CU-UP). Among them, CU-CP and CU-UP can also be deployed on different physical devices. CU-CP is responsible for the control plane function and mainly includes the RRC layer and the PDCP-C layer. The PDCP-C layer is mainly responsible for encryption and decryption of control plane data, integrity protection, and data transmission. CU-UP is responsible for the user plane function, mainly including SDAP layer and PDCP-U layer. The SDAP layer is mainly responsible for processing the data of the core network and mapping the flow to the bearer. The PDCP-U layer is mainly responsible for at least one function such as encryption and decryption of the data plane, integrity protection, header compression, serial number maintenance, and data transmission. Specifically, the CU-CP and the CU-UP are connected through a communication interface (for example, an E1 interface). CU-CP represents that a network device is connected to a core network device through a communication interface (for example, Ng interface), and is connected to a DU through a communication interface (for example, F1-C (control plane) interface). The CU-UP is connected to the DU through a communication interface (for example, an F1-U (user plane) interface).

There is another possible implementation, the PDCP-C layer is also included in the CU-UP.

It is understandable that the above protocol layer division of CU and DU, and CU-CP and CU-UP is only an example, and there may be other division methods, which are not limited in the embodiment of the present application.

The network device mentioned in the embodiment of this application may be a device including CU, or DU, or CU and DU, or control plane CU node (CU-CP node) and user plane CU node (CU-UP node), and DU The device of the node.

Network equipment and terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on airborne aircraft, balloons, and satellites. In the embodiments of the present application, the scenes in which the network equipment and the terminal equipment are located are not limited.

In the embodiment of the present application, the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software.

In addition, various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques. The term "article of manufacture" used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

To facilitate the understanding of the embodiments of the present application, first, the communication system shown in FIG. 1 is taken as an example to describe in detail the communication system applicable to the embodiments of the present application. Fig. 1 is a schematic diagram of a communication system 100 applicable to a method for message transmission according to an embodiment of the present application. As shown in FIG. 1, the communication system 100 may include at least one network device, such as the network device 110 shown in FIG. 1; the communication system 100 may also include at least one terminal device, such as the terminal device 120 shown in FIG. 1. The network device 110 and the terminal device 120 may communicate through a wireless link. Each communication device, such as the network device 110 or the terminal device 120, can be equipped with multiple antennas. For each communication device in the communication system 100, the configured multiple antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals. Therefore, the communication devices in the communication system 100, such as the network device 110 and the terminal device 120, can communicate through multi-antenna technology.

It should be understood that FIG. 1 is only a simplified schematic diagram of an example for ease of understanding. The communication system 100 may also include other network devices or other terminal devices, which are not shown in FIG. 1.

To facilitate the understanding of the embodiments of the present application, a brief description of several basic concepts involved in the embodiments of the present application will be given. It should be understood that the basic concepts introduced below are simply described by taking the basic concepts specified in the current protocol as an example, but it does not limit that the embodiments of the present application can only be applied to existing communication systems. Therefore, the standard names that appear when describing the existing communication system as an example are all functional descriptions, and the specific names are not limited.

1. Data bearer segmentation process.

As shown in FIG. 2, FIG. 2 is a schematic diagram of a processing flow of data bearer and signaling bearer provided by the present application. It can be seen from FIG. 2 that the entity in the solid-line frame represents the processing entity of data radio bearer (DRB), and the entity in the dashed-line frame represents the processing entity of signal radio bearer (SRB).

Specifically, the maximum transmission size of IP layer and Ethernet layer data packets is 1500 bytes. When the data of the terminal device is transmitted via the IP layer or the Ethernet layer, it has been segmented, and the data packet at the access layer will not be larger than 9000 bytes. However, it can be known from the processing procedures of DRB and SRB that this segmentation procedure is only for DRB. For SRB, there is no IP layer or Ethernet layer transmission, so there is no segmentation.

Further, the RRC message generated by the RRC entity on the network device or terminal device side does not pass through the IP layer or Ethernet transmission when it reaches the SDAP layer and starts transmission, so it will not be fragmented, and the data packet size may exceed the threshold. RRC news. For RRC messages exceeding the size threshold, possible processing methods include:

1) For RRC messages, the size limit is lifted. That is, there is no need to limit the size of the RRC message packet to be less than or equal to 9000 bytes when transmitting RRC messages;

2). Compress RRC messages. That is, compress the RRC message to be transmitted so that the size of the RRC message packet is less than or equal to 9000 bytes;

3) The RRC message is segmented so that the size of each message packet of the segmented RRC message is less than or equal to 9000 bytes.

The embodiments of this application mainly focus on the segmentation of RRC messages, and the processing methods 1) and 2) will not be described in detail. At present, the communication system has determined to adopt a segmented processing method to process the uplink oversize RRC message, so that the size of each segment of the uplink oversize RRC message is less than or equal to a threshold (for example, less than or equal to 9000 bytes).

The following briefly introduces the uplink oversize RRC message segmentation method.

2. The uplink oversize RRC message segmentation method.

As shown in Fig. 3, Fig. 3 is a schematic diagram of an uplink oversize RRC message segmentation. When the RRC layer of the terminal device determines that the size of the uplink RRC message to be transmitted exceeds the threshold (for example, greater than 9000 bytes), the uplink RRC message is segmented and then transmitted to the network device.

Specifically, the terminal device first performs abstract syntax notation one (ASN.1) encoding on the uplink RRC message to obtain the encoded uplink RRC message (for example, the encoded uplink RRC message as shown in FIG. 3 is ABCDEF); Then the encoded uplink RRC message is divided into multiple segmented messages (for example, as shown in Figure 3, ABCDEF is divided into 3 segmented messages, the 3 segmented messages are ABC, DE, and F ); Finally, each segment message is transmitted to the network device separately.

As shown in Figure 4, Figure 4 is a schematic diagram of a terminal device transmitting an uplink RRC message to a network device. It can be seen from Figure 4 that after the encoded uplink RRC message is divided into multiple segmented messages, each segmented message is increased by an index (for example, as shown in Figure 4, index 0 is added to the segmented message ABC, in The index 1 is added to the segment message DE and the index 2) is added to the segment message F. The terminal device transmits each segment message with an index to the network device. Wherein, the index added for each segment message can also be called a sequence number, label, identification, etc. The specific name of the index added for each segment message is not limited in this application, and multiple RRC messages can be identified in sequence. The identifier of the segmented message can be regarded as the index of the segmented message.

It should be noted that the network device must receive all the segment messages corresponding to the uplink RRC message before it can assemble the received segment messages into a complete uplink RRC message. Therefore, in order for the network device to recognize which segment message is the last segment message, the terminal device needs to add an end identifier to the last segment message in the process of transmitting the segment message (for example, as shown in Figure 4). As shown, the end identifier is added to the segmented message F with index 2), then after the network device receives the segmented message carrying the end identifier, it determines that the segmented message is the last segmented message, which can be assembled to obtain Complete uplink RRC message.

Further, in order to ensure that the foregoing process is easy to implement, the current protocol stipulates that the terminal device cannot alternately transmit the segment messages corresponding to the two uplink oversize RRC messages. As shown in Figure 5, Figure 5 is a schematic diagram of another terminal device transmitting an uplink RRC message to a network device, where the solid line frame represents the segment message corresponding to the uplink RRC message #1, and the dashed frame represents the uplink RRC message #2 Corresponding segmented messages, where uplink RRC message #1 and uplink RRC message #2 are two different uplink oversize RRC messages.

The transmission mode shown in Figure 5 shows that the terminal device is alternately sending the segmented message corresponding to the uplink RRC message #1 to the network device (implementation blocks 0, 1, 2 and end 3 shown in the figure) correspond to the uplink RRC message #2 In the transmission scenario shown in Figure 5, the network equipment side cannot recognize that the received segment message belongs to the uplink RRC message according to the current protocol.# 1 is still the uplink RRC message #2, so that a complete uplink RRC message #1 and/or uplink RRC message #2 cannot be assembled. Therefore, in order to avoid that the network device cannot identify the uplink RRC message to which the received segment message belongs, the current protocol stipulates that the terminal device cannot alternately transmit the segment messages corresponding to the two uplink oversize RRC messages.

The foregoing description relates to the segmented message corresponding to the uplink RRC message, and the segmented message involved in this application is described in detail below.

3. Segment messages.

A certain segmented message involved in the embodiments of this application refers to a message that carries part of the content of a certain complete RRC message. The entire content of the complete RRC message can be divided into multiple parts, and the multiple parts respectively carry It is transmitted in multiple segmented messages (for example, the entire content of the uplink RRC message shown in FIG. 4 can be divided into three parts, and the three parts are carried in three segmented messages, respectively). It should be understood that a segmented message may also be called an RRC message, but for the sender, the segmented message does not need to be re-encoded, and the receiver does not need to decode the segmented message. In order to distinguish the segmented message from the complete RRC message, This segmented message can be called a special RRC message. In the embodiments of the present application, a message that carries part of the content of a complete uplink RRC message may be referred to as an uplink segment message; a message that carries a part of the content of a complete downlink RRC message is referred to as a downlink segment message.

It should be understood that, in the embodiment of the present application, the message carrying the partial content of the complete RRC message is referred to as a segmented message, which is only an example, and does not constitute any limitation on the protection scope of the present application. For example, it can also be called partial message, special RRC message, message segment, and so on.

The above introduces the uplink oversize RRC message segmentation method. The current protocol involves a downlink earthquake tsunami warning system (ETWS) message segmentation method. The following is a simple method for the ETWS message segmentation method. instruction.

4. ETWS message segmentation method.

The message size of the ETWS service may be very large, exceeding the maximum schedulable limit of the radio network temporary identity (RNTI) of the public wireless network. The network equipment can segment the ETWS message, and use the system information block type 7 , SIB7) Send each segment message of the ETWS message to the terminal device on the air interface. The process of segmenting the ETWS message by the network device is similar to the process of segmenting the uplink oversized RRC message by the terminal device described above, and will not be repeated here; for the same reason, the terminal device receives each segmented message of the ETWS message and assembles it Obtaining the complete ETWS message is similar to the foregoing network device receiving each segment message of the uplink oversize RRC message and assembles to obtain the complete uplink oversize RRC message, and will not be repeated here.

In addition, in order to facilitate the understanding of the embodiments of the present application, the following descriptions are made.

First, in this application, "used to indicate" can include both used for direct indication and used for indirect indication. When describing a certain indication information to indicate A, the indication information can directly indicate A or indirectly indicate A, but it does not mean that A must be included in the indication information.

The information indicated by the instruction information is referred to as the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed. For example, but not limited to, the information to be indicated may be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indicated indirectly by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance. For example, it is also possible to realize the indication of specific information by means of a pre-arranged order (for example, stipulated in an agreement) of various information, so as to reduce the indication overhead to a certain extent. At the same time, it can also identify the common parts of each information and give unified instructions, so as to reduce the instruction overhead caused by separately indicating the same information.

Second, in this application, the first, second, and various numerical numbers (for example, "#1", "#2") are only for easy distinction for description, and are not used to limit the scope of the embodiments of this application. For example, distinguish different RRC messages, distinguish different segmented messages, and so on.

Third, in this application, "preset" may include indication by network device signaling, or pre-defined, for example, protocol definition. Among them, "pre-defined" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate related information in the equipment (for example, including terminal equipment and network equipment). This application does not make any specific implementation methods. limited.

Fourth, the "saving" referred to in the embodiments of the present application may refer to storing in one or more memories. The one or more memories may be provided separately, or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partly provided separately, and partly integrated in a decoder, a processor, or a communication device. The type of the memory can be any form of storage medium, which is not limited in this application.

Fifth, the “protocols” involved in the embodiments of the present application may refer to standard protocols in the communication field, for example, may include LTE protocol, NR protocol, and related protocols applied to future communication systems, which are not limited in this application.

The foregoing briefly introduces the application scenarios of the method for message transmission provided by the embodiments of this application in conjunction with FIG. 1, and introduces the basic concepts that may be involved in the embodiments of this application. The implementation of this application will be described in detail below with reference to the accompanying drawings. Examples provide methods for message transmission.

It should be understood that the method for message transmission provided in the embodiment of the present application can be applied to the communication system 100 as shown in FIG. 1. The communication system may include at least one network device and at least one terminal device. Antenna technology can be used to communicate between network equipment and terminal equipment.

It should also be understood that the embodiments shown below do not specifically limit the specific structure of the execution body of the method provided by the embodiments of the present application, as long as the program that records the code of the method provided by the embodiments of the present application can be executed according to the present application. The method provided in the application embodiment only needs to communicate. For example, the execution subject of the method provided in the embodiment of the application may be a terminal device or a network device, or a functional module in the terminal device or the network device that can call and execute the program.

In the above-mentioned uplink oversize RRC message segmentation method, the receiver is the network device, and the behavior of the network device to receive the segmented message is not clearly defined in the protocol. If the uplink oversize RRC message segmentation method is similarly applied to the downlink oversize RRC message segmentation, how to regulate the receiving behavior of the terminal device becomes an urgent problem to be solved;

In addition, in the above-mentioned ETWS message segmentation method, the segmented message is transmitted through SIB7, which is periodically transmitted. If the terminal device does not receive all the segment messages corresponding to the ETWS message, it can continue to receive SIB7 in the next cycle; if the terminal device has received all the segment messages corresponding to the ETWS message, it can start to assemble the ETWS message. However, the ETWS message segmentation method is not completely suitable for downlink oversize RRC message segmentation, because network equipment does not periodically transmit all downlink RRC messages, that is to say, for aperiodic transmission of downlink oversize RRC message The ETWS message segmentation method is not applicable.

In summary, the existing uplink oversize RRC message segmentation method and downlink ETWS message segmentation method are not suitable for all downlink oversize RRC message segmentation. In order to improve the downlink oversize RRC message transmission performance, This application provides a method and device for message transmission, which can be applied to downlink oversize RRC message segment transmission.

Hereinafter, without loss of generality, the interaction between the network device and the terminal device is taken as an example to describe in detail the method for message transmission provided in the embodiment of the present application.

Fig. 6 is a schematic flowchart of a method for message transmission provided by an embodiment of the present application. The execution subject in this flowchart includes terminal equipment and network equipment.

The method for message transmission includes at least some of the following steps.

S610: The terminal device receives at least one first segment message.

Wherein, the at least one first segment message is a part of the downlink segment messages among the multiple downlink segment messages corresponding to the first downlink RRC message.

For example, similar to the uplink oversize RRC message segmentation method shown in Figure 3, the network device first performs ASN.1 encoding on the first downlink RRC message to obtain the encoded first downlink RRC message, and the network device determines The encoded first downlink RRC message to be transmitted exceeds the transmission size specified in the protocol, and the first downlink RRC message needs to be transmitted in segments; then the network device divides the encoded first downlink RRC message into multiple Segment messages (if divided into 4 segment messages, the 4 segments are respectively marked as downlink segment message #1, downlink segment message #2, downlink segment message #3, and downlink segment message #4) Each segment message carries its own index, which is similar to the above-mentioned oversize uplink RRC message segment transmission. The last downlink segment message carries the corresponding index and end identifier; finally, the network device transmits each segment message to Terminal Equipment.

It should be understood that when the encoded first downlink RRC message to be transmitted does not exceed the transmission size specified in the protocol, the network device does not need to transmit the encoded first downlink RRC message to be transmitted in segments. Regarding how to transmit oversized downlink RRC messages, the transmission of non-oversized downlink RRC messages can refer to the regulations in the current protocol, which will not be repeated in this application.

Optionally, the at least one first segment message may include the aforementioned downlink segment message #1 and downlink segment message #2. Specifically, the downlink segment message #1 carries index 0, and the downlink segment message #2 carries index. 1. The terminal device learns that the first downlink segment message and the second downlink segment message corresponding to the first downlink RRC message are received based on the index of the received downlink segment message. The aforementioned downlink segment message #3 and downlink segment message #4 are not received;

Optionally, the at least one first segment message may include the aforementioned downlink segment message #1 and downlink segment message #3. Specifically, the downlink segment message #1 carries index 0, and the downlink segment message #3 carries index. 2. The terminal device learns that the first downlink segment message and the third downlink segment message corresponding to the first downlink RRC message are received based on the index of the received downlink segment message. The aforementioned downlink segment message #2 and downlink segment message #4 are not received.

As a possible implementation manner, the terminal device receiving at least one first segment message from the network device includes:

The terminal device receives multiple first segment messages from the network device, where the multiple first segment messages include at least one third segment message and at least one fourth segment message;

The method for message transmission also includes:

The PDCP entity of the terminal device reports at least one third segment message to the RRC entity of the terminal device;

The PDCP entity of the terminal device stores at least one fourth segment message in the PDCP entity of the terminal device,

Wherein, the index of the third segment message is smaller than the index of the fourth segment message, and the index of the fourth segment message is greater than the index of the second segment message.

That is to say, when the PDCP entity of the terminal device receives two first segment messages with discontinuous indexes, it can report the first segment message with the smaller index to the RRC entity of the terminal device, and the first segment message with the larger index can be reported to the RRC entity of the terminal device. The segmented message is stored in the PDCP entity of the terminal device; in the same way, when the PDCP entity of the terminal device receives multiple first segmented messages with non-contiguous indexes (for example, receiving indexes of 0, 1, 3, and 5 respectively) 4 first segmented messages), the first segmented message with a small index and continuous (for example, two first segmented messages with

indexes

0 and 1, respectively) can be reported to the RRC entity of the terminal device, and the The remaining first segment messages (for example, the two first segment messages with indexes 3 and 5 respectively) are stored in the PDCP entity of the terminal device.

It should be noted that, among the multiple segment messages corresponding to the first downlink RRC message in the embodiment of the present application, the one with the smallest index is the first segment message corresponding to the first downlink RRC message, and the one with the largest index is the first segment message. The last segment message corresponding to the downlink RRC message, that is, the index of the next segment message of a certain segment message is greater than the index of the segment message, and the index of the previous segment message of the segment message is less than the segment The index of the message. In order to enable the terminal device to know which segment message is the last segment message corresponding to the first downlink RRC message, the last segment message may carry an end identifier.

In the embodiment of the present application, the specific form of the end identifier carried in the last segment message corresponding to the first downlink RRC message is not limited. For example, it may be the end identifier described above; or, for example, it may be another identifier that indicates the last segmented message, such as last; or, it may also be the index for multiplexing the last segmented message, for example, The terminal device can determine that a certain downlink RRC message will not be divided into more than 100 segment messages to be delivered, and the index of the last segment message can be set to 100. When the terminal device receives a segment message with an index of 100, Make sure that this segmented message is the last segmented message.

For example, the aforementioned at least one first segment message includes the downlink segment message #1 and the downlink segment message #3, and the PDCP entity of the terminal device receives the downlink segment message #1 and the downlink segment message #3, because The index of the downlink segment message #3 is greater than the index of the downlink segment message #1, and among the downlink segment message #2 and downlink segment message #4 that are not received, the index of the downlink segment message #2 is smaller than the index of the downlink segment message #2 For the index of message #3, the PDCP entity of the terminal device can send the downlink segment message #1 to the RRC entity of the terminal device, and save the downlink segment message #3 in the SRB buffer of the PDCP entity of the terminal device.

The first downlink RRC message involved in this application can be understood as a dedicated downlink RRC message other than messages transmitted through SIBs such as ETWS. It should be noted that although the embodiment of this application mainly relates to how to transmit dedicated downlink RRC messages in segments, it does not limit that the solution for segmented transmission of messages provided by the embodiments of this application cannot be applied to message transmission via SIBs such as ETWS. .

In addition, in the embodiments of the present application, it is not limited that all downlink RRC messages need to be transmitted in segments. For example, before the terminal device receives at least one first segment message, the terminal device receives a third downlink RRC message, and the third downlink RRC message does not exceed the transmission size specified by the protocol (for example, the size of the third downlink RRC message does not exceed the size of the third downlink RRC message). More than 9000bytes), as a complete downlink RRC message for transmission.

Further, after receiving the at least one first segment message, the terminal device determines that the at least one first segment message is part of the downlink segment message among the multiple downlink segment messages corresponding to the first downlink RRC message. If all the multiple downlink segment messages corresponding to a downlink RRC message are not received (for example, at least one second segment message is not received), the terminal device may send a request message to the network device, requesting the network device to send at least one second segment message. The segment message, that is, the method flow shown in FIG. 6 further includes S620: the terminal device sends a request message to the network device.

In the embodiment of this application, the second segment message can be understood as the segment message corresponding to the first downlink RRC message that the RRC entity of the terminal device has not received; or, it can also be understood as the segment message that the RLC entity of the terminal device has not received. A segment message corresponding to a downlink RRC message.

Exemplarily, the second segmentation message is a segmentation message corresponding to the first downlink RRC message that is not received by the RRC entity of the terminal device, and the at least one second segmentation message mentioned above can be understood as being received by the RRC entity of the terminal device One or more second segment messages next to the last first segment message to be reached. For example, if at least one first segment message includes the aforementioned downlink segment message #1 and downlink segment message #3, the aforementioned at least one second segment message can be understood as downlink segment message #3, or at least one The second segment message can be understood as downlink segment message #3 and downlink segment message #4. That is to say, the terminal device can request the network device to transmit a subsequent unreceived segment message of the received segment message, or the terminal device can also request the network device to transmit the subsequent unreceived segment message of the received segment message Of multiple segmented messages.

In a possible implementation manner, the terminal device sending the request message to the network device may be that the RRC entity of the terminal device sends a notification message to the RLC entity of the terminal device, indicating that at least one second segment message has not been received, and the RLC entity sends a notification message to the network. The device sends a request message (for example, an RLC status report or other RLC messages), requesting the network device to send the at least one second segment message as soon as possible.

For example, the terminal device receiving a downlink RRC segment message is shown in FIG. 7, which is a schematic diagram of transmitting a downlink RRC segment message according to an embodiment of the present application.

It can be seen from FIG. 7 that the terminal device, as the receiver, can receive an unsegmented third downlink RRC message from the network device. In FIG. 7, message No. 1 is used to indicate the unsegmented third downlink RRC message;

Optionally, the terminal device may also receive the first downlink RRC message segmented from the network device. As shown in the figure, message No. 2 includes the first downlink RRC segment message 2A and the second downlink RRC segment message. 2B and the third downlink RRC segment message 2C.

Specifically, after the RLC entity of the terminal device receives 2A and 2C, and after submitting 2A and 2C to the PDCP entity of the terminal device, the PDCP entity of the terminal device determines that the second downlink RRC segment message has not been received, as shown in Figure 7 2B represents the second downlink RRC segment message. Then the PDCP entity of the terminal device stores 2C in the memory of the PDCP entity and waits to receive 2B.

After the RRC entity of the terminal device receives the aforementioned 2A from the PDCP entity of the terminal device, it determines that 2A is a downlink RRC segment message, and the RRC entity of the terminal device sends a first notification message to the RLC entity of the terminal device. The message indicates that the next downlink RRC segment message corresponding to message No. 2 has not been received. After receiving the first notification message, the RLC entity of the terminal device sends an RLC status report or other RLC message to the network device side. The status report or other RLC message indicates that the second downlink RRC segment message of message No. 2 has not been received , Request the network device to resend 2B.

It should be noted that the number of RLC entities in the terminal device is not limited in the embodiment of the present application. That is to say, the terminal device may include one or more RLC entities.

When the terminal equipment includes an RLC entity, the RLC entity transmits data to the PDCP entity, and the RLC entity also receives the first notification message sent by the RRC entity, and sends an RLC status report or other RLC message to the network device side ；

When the terminal device includes multiple RLC entities (for example, including RLC entity #1 and RLC entity #2), both RLC entity #1 and RLC entity #2 can transmit data to the PDCP entity. In this case, RRC The entity cannot determine which RLC entity should deliver 2B. In order to enable the terminal device to notify the network device side to resend 2B in time, in this case, the RRC entity may send the first notification message to the RLC entity #1 and the RLC entity #2 respectively. After RLC entity #1 and RLC entity #2 receive the first notification message, they first determine whether 2B should be delivered by themselves, and then determine whether to send an RLC status report or other RLC messages:

Taking RLC entity #1 as an example, if RLC entity #1 determines that 2B should be delivered by RLC entity #1, RLC entity #1 sends an RLC status report or other RLC message to the network device side; if RLC entity #1 determines that it should not 2B is delivered by RLC entity #1, RLC entity #1 does not send RLC status reports or other RLC messages to the network device side; if RLC entity #1 cannot determine whether RLC entity #1 should deliver 2B, RLC entity #1 The network device side sends an RLC status report or other RLC messages. The steps performed by the RLC entity #2 are similar to those of the RLC entity #1, and will not be repeated here.

The above-mentioned RLC entity #1 can determine whether the RLC entity #1 should transfer 2B according to whether the index carried in the RLC PDU received by the RLC entity #1 is continuous.

Optionally, if the index carried in the RLC PDU received by the RLC entity #1 is not continuous, the RLC entity #1 may determine that the RLC entity #1 will deliver the next downlink RRC segment message. For example, if RLC entity #1 receives 2A with

index

0 and 2C with index 2, RLC entity #1 can determine that RLC entity #1 delivers 2B;

Optionally, if the index carried in the RLC PDU received by the RLC entity #1 is continuous, the RLC entity #1 cannot determine that the RLC entity #1 transmits the next downlink RRC segment message 2B. For example, the fourth downlink RRC message is divided into 4 downlink RRC segment messages, namely 4A, 4B, 4C, and 4D. RLC entity #1 receives 4A with index 0 and 4B with index 1. RLC entity #1 cannot determine that 4C with index 2 is delivered by RLC entity #1. It is possible that 4C with index 2 is transmitted via other RLC entities. .

In another possible manner, the terminal device sending the request message to the network device may be that after the RLC entity of the terminal device receives at least one first segment message, it determines that the at least one second segment message is not received, then the RLC entity sends the request message to the network The device sends a request message (for example, an RLC status report or other RLC messages), requesting the network device to send the at least one second segment message as soon as possible. In this implementation manner, it can be understood that the duration of the timer for the RLC entity to trigger the sending of the RLC status report is set to 0.

For example, a terminal device receives a downlink RRC segment message as shown in FIG. 7. After receiving 2A and 2C, the RLC entity of the terminal device determines that 2B has not received it. The RLC entity of the terminal device sends an RLC status report or other RLC message to the network device side. The status report or other RLC message indicates that the second downlink RRC segment message of message No. 2 has not been received, and requests the network device to resend 2B.

It should be noted that when the terminal device includes an RLC entity, the RLC entity transmits data to the PDCP entity, and the RLC entity also receives the request message sent by the RRC entity;

When the terminal device includes multiple RLC entities (for example, including RLC entity #1 and RLC entity #2), both RLC entity #1 and RLC entity #2 can transmit data to the PDCP entity, and RLC entity #1 and RLC entity #2 Entity #2 first determines whether 2B should be delivered by itself, and then determines whether to send a request message:

Taking RLC entity #1 as an example, if RLC entity #1 determines that RLC entity #1 should deliver 2B, RLC entity #1 sends a request message to the network device side; if RLC entity #1 determines that RLC entity #1 should not If 2B is transferred, the RLC entity #1 does not send a request message to the network device side; if the RLC entity #1 cannot determine whether the RLC entity #1 should transfer 2B, the RLC entity #1 sends a request message to the network device side. The steps performed by the RLC entity #2 are similar to those of the RLC entity #1, and will not be repeated here.

In another possible manner, the terminal device sending a request message to the network device may be that the RRC entity of the terminal device sends a notification message to the MAC entity of the terminal device, indicating that at least one second segment message has not been received, and the MAC entity sends a notification message to the network. The device sends a request message (for example, a MAC message), requesting the network device to send the at least one second segment message as soon as possible.

For example, the terminal device receives the downlink RRC segment message as shown in Figure 7. After the RRC entity of the terminal device receives the above 2A from the PDCP entity of the terminal device, it determines that the 2A is a downlink RRC segment message. The RRC entity of the terminal device Send a second notification message to the MAC entity of the terminal device.

Optionally, the second notification message indicates that the next downlink RRC segment message corresponding to message No. 2 has not been received. or,

Optionally, the second notification message indicates that 2B in the No. 2 message has not been received.

After receiving the second notification message, the MAC entity of the terminal device sends a request message (for example, a MAC message) to the MAC entity on the network device side, requesting the network device to resend 2B. Optionally, the MAC message indicates that the second downlink RRC segment message of message No. 2 has not been received; or, optionally, the MAC message carries indication information of 2B, indicating that 2B in message No. 2 has not been received ( For example, the MAC message carries index 1).

The aforementioned network device resending 2B can be understood as the network device making a hybrid automatic repeat request (HARQ) for the transmission block containing 2B.

Optionally, when the terminal device receives the first first segment message from the network device, the method for message transmission further includes:

The terminal device starts the timer;

When the terminal device receives all the second segment messages in at least one second segment message during the running period of the timer, the terminal device stops the timer; or,

When the timer expires and the terminal device does not receive all the second segment messages in the at least one second segment message, the terminal device determines that the reception of the first downlink RRC message fails.

For example, when the RRC entity of the terminal device in the method flow shown in FIG. 7 receives 2A, it starts a timer and waits to receive other downlink RRC segment messages other than 2A corresponding to message No. 2 (for example, waiting to receive the above-mentioned RRC segment message). 2B and 2C). For example, the receiving of 2A can be understood as the beginning of receiving 2A, or the complete receiving of 2A is completed, and a timer is started. Assuming that the terminal device receives 2A at time T1, and the timing duration of the timer is 10ms.

When the terminal device receives the above 2B and 2C during the running period of the timer (for example, the RRC entity of the terminal device receives 2B at time T2, and T2≤T1+10ms; the RRC entity of the terminal device receives it at time T4 2C, and T4≤T1+10ms), then the RRC entity of the terminal device notifies the PDCP entity to stop the running of the timer or restart the timer; or,

When the timer expires (T3>T1+10ms), and the RRC entity of the terminal device still does not receive the above 2B and 2C, the PDCP entity of the terminal device determines that the reception of the above message No. 2 fails.

Further, when the terminal device receives all the second segment messages in the at least one second segment message during the running period of the timer, the method for message transmission further includes:

The terminal device sends the first duration to the network device, where the start time of the first duration is the timer start time, and the end time of the first duration is the last second segment message received by the terminal device. The moment of the segmented message.

For example, as shown in FIG. 8, FIG. 8 is a schematic diagram of reporting the first duration according to an embodiment of the present application. Specifically, before the timer expires, the RRC entity of the terminal device receives all downlink RRC segment messages corresponding to message No. 2 (for example, the foregoing 2A, 2B, and 2C are received), and then the terminal device timer is stopped. The RRC entity of the terminal device may record the first duration of receiving all the downlink RRC segment messages corresponding to the message No. 2 and send the first duration to the network device.

In the embodiments of this application, the timing of the terminal device reporting the first duration is not limited. It may be the moment when the terminal device receives all the downlink segment messages corresponding to the first downlink RRC message, or the terminal device may receive multiple messages. The downlink RRC message will be reported after the first time, and the timing of reporting the first duration will not be repeated here.

For the network device, the subsequent downlink segment RRC message transmission behavior can be optimized according to the received first duration. If the first duration is relatively large (for example, greater than the preset duration threshold), the network device can subsequently transmit the downstream segment. When segmenting RRC messages, increase the transmission power, or use a lower-order MCS, etc., to enhance the robustness of transmitting downlink segmented RRC messages.

Further, when the terminal device does not receive all the second segment messages in the at least one second segment message during the running period of the timer, the method for message transmission further includes:

The RRC entity of the terminal device sends a first message to the PDCP entity of the terminal device, where the first message is used to instruct the PDCP entity to report a second message, where the second message is a buffered message in a signaling bearer buffer of the PDCP entity;

When the second message includes part of the second segment message in at least one second segment message, the method further includes:

The terminal device discards at least one first segment message and a part of the received second segment message.

When the second message includes a second downlink RRC message (a complete second downlink RRC message), the terminal device can process the second downlink RRC message. The specific processing flow is not involved in this application. You can refer to the current protocol for Provisions for the processing of downlink RRC messages.

Optionally, when the terminal device discards part of the segment message corresponding to the received first downlink RRC message (for example, part of the received at least one first segment message and the received at least one second segment message After the second segment message), the terminal device considers that the transmission of the first downlink RRC message has failed, and can initiate RRC re-establishment.

It can be understood that, before the terminal device initiates the RRC re-establishment, if the received second message includes the second downlink RRC message, the terminal device may complete the processing of the second downlink RRC message and then initiate the RRC re-establishment.

For example, as shown in FIG. 9, FIG. 9 is a schematic diagram of reporting a cached message according to an embodiment of the present application. When the timer expires, the RRC entity of the terminal device has not received all the downlink RRC segment messages corresponding to message No. 2 (for example, at least one of the above 2B and 2C has not been received), then the RRC entity of the terminal device The PDCP entity of the terminal device is notified so that the PDCP entity of the terminal device delivers all data packets (for example, the aforementioned 2C) in the corresponding SRB buffer to the RRC entity of the terminal device. The RRC entity of the terminal device corresponds to the message No. 2 received from the PDCP entity and is not received during the timer operation period (for example, the above-mentioned 2C), and the message No. 2 has been received corresponding to the Fragmented messages (for example, 2A above) are discarded.

When the SRB buffer corresponding to the PDCP entity includes other complete second downlink RRC messages, the RRC entity of the terminal device will check the RRC messages received from the PDCP entity that are not segmented (for example, as shown in Figure 9). Message No. 3) for processing.

As a possible implementation manner, before the terminal device receives the at least one first segment message from the network device, the method for transmitting the message further includes:

The terminal device sends the first capability information to the network device, where the first capability information is used to indicate that the terminal device supports downlink RRC message segmentation.

That is, the method flow shown in FIG. 6 further includes S611: the terminal device sends the first capability information to the network device.

The first capability information is used to indicate whether the terminal device supports downlink RRC message segmentation. Specifically, the first capability information may be referred to as a third message, which indicates the capability of the terminal device. It should be understood that the embodiments of this application mainly relate to the manner of downlink RRC message segmentation, so the first message can be understood as notifying the network device that the terminal device supports downlink RRC message segmentation (it is understandable that if the terminal device does not support downlink RRC message segmentation) Paragraph, the subsequent process cannot reflect the improvement points of this application relative to the prior art), the following takes the terminal device to support downlink RRC message segmentation as an example for description. However, the embodiment of the present application does not limit that the first capability information can only be used to indicate that the terminal device supports downlink RRC message segmentation.

As a possible implementation manner, the first capability information is used to notify the network device whether the terminal device supports uplink RRC message segmentation;

As another possible implementation manner, the first capability information is used to notify the network device whether the terminal device supports downlink RRC message segmentation;

As another possible implementation manner, the first capability information is used to notify the network device whether the terminal device supports uplink RRC message segmentation and whether it supports downlink RRC message segmentation.

When the first capability information indicates whether the terminal device supports uplink RRC message segmentation and whether it supports downlink RRC message segmentation, the two capability information (whether it supports uplink RRC message segmentation, whether it supports downlink RRC message segmentation) It can be carried in the same message or reported separately.

For example, the above-mentioned first capability information is a report message, which also carries two capability information of whether the terminal device supports uplink RRC message segmentation and whether it supports downlink RRC message segmentation; or,

The above-mentioned first capability information is a collective term for multiple messages (for example, the first capability information includes first capability information #1 and first capability information #2), where the first capability information #1 carries whether the terminal device supports uplink The capability information of RRC message segmentation, the first capability information #2 carries capability information of whether the terminal device supports downlink RRC message segmentation, the first capability information #1 and the first capability information #2 are respectively sent by the terminal device to the network device .

Exemplarily, the terminal device separately reporting whether the terminal device supports uplink RRC message segmentation and whether it supports downlink RRC message segmentation may be: the terminal device reports whether the terminal device supports uplink through the second capability information (for example, an RRC connection establishment complete message) For the capability information of the RRC message segmentation, the method flow shown in FIG. 6 further includes S612: the terminal device sends the second capability information to the network device.

It should be noted that when the terminal device supports uplink RRC message segmentation and whether it supports downlink RRC message segmentation, the two capability information is carried in different messages and reported to the network device, it can be understood as the terminal device sending to the network device The first capability information itself needs to be segmented (for example, the size of the first capability information exceeds the threshold), if the first capability information also carries the capability information of whether the terminal device supports uplink RRC message segmentation, and the terminal device Whether to support the capability information of the downlink RRC message segmentation may cause the network device to fail to accurately learn the capability of the terminal device.

Further, the terminal device in the embodiment of the present application can learn whether the network device has RRC message segmentation capability information. That is, the process shown in FIG. 6 also includes S613: the network device sends the first indication information to the terminal device. The first indication information is used to indicate that the network device supports downlink RRC message segmentation.

It should be noted that the network device involved in the application supporting downlink RRC message segmentation can be understood as the network device supporting downlink dedicated RRC message segmentation in addition to broadcast messages (for example, ETWS).

As a possible implementation, when the network device sends a segmented message such as SIB7 to the terminal device, the terminal device learns that the network device supports downlink RRC message segmentation;

As another possible implementation manner, the SIB sent by the network device to the terminal device carries first indication information, and the first indication information is used to indicate whether the network device has the capability of downlink RRC message segmentation;

As another possible implementation manner, the network device sends first indication information to the terminal device, where the first support information is used to indicate whether the network device has the capability of downlink RRC message segmentation.

It should be understood that the foregoing possible implementations for the terminal equipment to obtain the capability information of the network device are only examples, and do not constitute any limitation to the protection scope of this application. In the embodiments of this application, how the terminal equipment obtains the capability information of the network device is not not limited.

In the case where the protocol stipulates that the terminal device completes the processing of an RRC message within a certain period of time (for example, 80ms), in the embodiment of this application, when the terminal device receives one of the multiple downlink RRC segment messages corresponding to a certain downlink RRC message When at least one second segment message is not successfully transmitted in time, the terminal device promptly informs the network device to retransmit the at least one second segment message, so that the downlink RRC segment message is transmitted to the terminal device as soon as possible, and the terminal device is within a certain period of time. Multiple downlink RRC segment messages corresponding to a certain downlink RRC message are received, and the processing of the downlink RRC message is completed.

It should be understood that the terminal device and/or the network device in the foregoing method embodiments may perform some or all of the steps in the embodiments. These steps or operations are only examples. The embodiments of the present application may also include performing other operations or variations of various operations. .

It should also be understood that, in the various embodiments of the present application, if there is no special description and logical conflicts, the terms and/or descriptions between different embodiments can be consistent and can be mutually cited. The technologies in different embodiments Features can be combined to form new embodiments according to their inherent logical relationships.

The method for message transmission provided by the embodiment of the present application is described in detail above with reference to Figs. 6-9, and the apparatus for message transmission provided by the embodiment of the present application is described in detail below with reference to Figs. 10-13.

Refer to FIG. 10, which is a schematic diagram of an apparatus 1000 for message transmission provided in the present application. As shown in FIG. 10, the device 1000 includes a processing unit 1010, a receiving unit 1020, a first sending unit 1030, a second sending unit 1040, a third sending unit 1050, and a storage unit 1060.

The receiving unit 1020 is configured to receive at least one first segment message from a network device.

The first sending unit 1030 is configured to send a request message to the network device, where the request message is used to request the network device to send at least one second segment message;

Wherein, the first downlink unlimited resource control RRC message includes the at least one first segment message and the at least one second segment message.

Exemplarily, when the receiving unit receives the first first segment message from the network device, the apparatus further includes:

The processing unit 1010 is used to start a timer;

When the receiving unit 1020 receives all the second segment messages during the running period of the timer, the processing unit 1010 stops the timer or restarts the timer;

When the timer expires and the receiving unit 1020 does not receive all the second segment messages, the processing unit 1010 determines that the reception of the first downlink RRC message fails.

Exemplarily, the first sending unit 1030 is further configured to send a first duration to the network device, wherein the start time of the first duration is the start time of the timer, and the end time of the first duration is the receiving time. The moment when the unit receives the last second segment message in the at least one second segment message.

Exemplarily, before the processing unit 1010 determines that the reception of the first downlink RRC message fails, the apparatus further includes:

The second sending unit 1040 provided in the RRC entity of the device is configured to send a first message to the PDCP entity of the device, where the first message is used to instruct the PDCP entity to report a second message, where the second message is The signaling of the PDCP entity bears the buffered message in the buffer;

When the second message includes part of the second segment message in the at least one second segment message, the processing unit is further configured to discard the at least one first segment message and the received part of the second segment message information.

Exemplarily, the receiving unit 1020 receiving at least one first segment message from a network device includes:

The receiving unit 1020 receives multiple first segment messages from the network device, where the multiple first segment messages include at least one third segment message and at least one fourth segment message;

The device also includes:

The third sending unit 1050 provided in the PDCP entity of the device is configured to report the at least one third segment message to the RRC entity of the device;

The storage unit 1060 provided in the PDCP entity of the device is configured to store the at least one fourth segment message in the PDCP entity,

Exemplarily, before the receiving unit 1020 receives at least one first segment message from the network device, the first sending unit 1030 is further configured to send first capability information to the network device, where the first capability information is used for Indicates that the device supports downlink RRC message segmentation.

Exemplarily, the first sending unit 1030 is further configured to send second capability information to the network device, where the second capability information is used to indicate that the device supports uplink RRC message segmentation.

Exemplarily, the receiving unit 1020 is further configured to receive first indication information from the network device, where the first indication information is used to indicate that the network device supports downlink RRC message segmentation.

The device 1000 corresponds to the terminal device in the method embodiment, and the device 1000 may be the terminal device in the method embodiment, or a chip or functional module inside the terminal device in the method embodiment. The corresponding units of the apparatus 1000 are used to execute the corresponding steps executed by the terminal device in the method embodiments shown in FIGS. 6-9.

Wherein, the processing unit 510 in the apparatus 500 is configured to execute the steps related to the processing corresponding to the terminal device in the method embodiment. For example, step S430 of determining the target cell in FIG. 4 is performed.

The receiving unit 1020 in the apparatus 1000 executes the steps of receiving by the terminal device in the method embodiment. For example, perform step S610 of receiving the first segment message sent by the network device in FIG. 6, perform step S613 of receiving the first indication information sent by the network device in FIG. 6, and perform the step S613 of receiving the first message sent by the network device in FIG. Steps, perform the steps of receiving 2A, 2C sent by the network device in Figure 7, perform the steps of receiving the message No. 1 sent by the network device in Figure 8, perform the

steps

2A, 2C, and 2B sent by the network device in Figure 8, execution diagram Step 9 receives the message No. 1 sent by the network device, and executes the step of receiving message Nos. 2A, 2C, 2B, and 3 sent by the network device in FIG. 9.

The first sending unit 1030 in the apparatus 1000 is configured to perform the steps of sending by the terminal device, for example, perform step S620 of sending a request message to the network device in FIG. 6, and perform step S611 of sending the first capability information to the network device in FIG. Execute step S612 in FIG. 6 of sending the second capability information to the network device.

The second sending unit 1040 in the apparatus 1000 is configured to perform the step of sending the RRC entity in the terminal device, for example, perform the step of sending the first notification message to the RLC entity of the network device in FIG. 7, and perform the step of sending the first notification message to the network device in FIG. The step of sending the second notification message by the MAC entity, and the step of sending the first message to the PDCP entity of the network device in FIG. 9 are performed.

The third sending unit 1050 in the apparatus 1000 is configured to execute the step of sending the PDCP entity in the terminal device, for example, execute the step of sending 2A to the RRC entity of the network device in FIG. 7 and execute the step of sending the RRC entity to the network device in FIG. 8 The steps of sending 2A, the steps of sending 2B, 2C to the RRC entity of the network device in Figure 8, the steps of sending 2A to the RRC entity of the network device in Figure 9, and the sending of 2C to the RRC entity of the network device in Figure 8, The steps of message 3.

The storage unit 1060 in the device 1000 is used to perform the steps of storing the PDCP entity in the terminal device, for example, performing the steps of storing 2C in FIG. 7, performing the steps of storing 2C in FIG. 8, and performing the steps of storing 2C in FIG. 9.

It should be understood that for the terminal device as a whole, the above-mentioned first sending unit 1030, second sending unit 1040, and third sending unit 1050 may be collectively referred to as sending units, that is, the sending unit in the terminal device in this application includes the first sending unit. The unit 1030, the second sending unit 1040, and the third sending unit 1050 are three components.

The receiving unit 1020 and the sending unit may constitute a transceiver unit, and have the functions of receiving and sending at the same time. Wherein, the processing unit 1010 may be at least one processor. The sending unit may be a transmitter or an interface circuit, and the receiving unit 1020 may be a receiver or an interface circuit. The receiver and transmitter can be integrated to form a transceiver or interface circuit.

Optionally, the device 1000 may further include a storage unit including the aforementioned storage unit 1060 for storing data and/or signaling. The processing unit 1010, the sending unit, and the receiving unit 1020 may interact or couple with the storage unit. For example, reading or calling the data and/or signaling in the storage unit, so that the method of the above-mentioned embodiment is executed.

Each of the above units can exist independently, or can be fully or partially integrated.

Referring to FIG. 11, FIG. 11 is a schematic structural diagram of a terminal device 1100 applicable to an embodiment of the present application. The terminal device 1100 can be applied to the system shown in FIG. 1. For ease of description, FIG. 11 only shows the main components of the terminal device. As shown in FIG. 11, the terminal device 1100 includes a processor, a memory, a control circuit, an antenna, and an input and output device. The processor is used to control the antenna and the input and output devices to send and receive signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory to execute the corresponding method executed by the terminal device in the method for registration proposed in this application. Process and/or operation. I won't repeat them here.

Those skilled in the art can understand that, for ease of description, FIG. 11 only shows a memory and a processor. In an actual terminal device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in the embodiment of the present application.

Refer to FIG. 12, which is a schematic diagram of an apparatus 1200 for message transmission provided in the present application. As shown in FIG. 12, the apparatus 1200 includes a receiving unit 1210, a sending unit 1220, and a processing unit 1230.

The sending unit 1220 is configured to send at least one first segment message to the terminal device;

The receiving unit 1210 is configured to receive a request message from the terminal device, where the request message is used to request the network device to send at least one second segment message,

Exemplarily, the receiving unit 1210 is further configured to receive a first duration from the terminal device, where the start time of the first duration is the moment when the terminal device receives the first first segment message. The termination time of the first duration is the time when the terminal device receives the last second segment message in the at least one second segment message.

Exemplarily, the device further includes:

The processing unit 1230 is configured to determine the power and/or modulation and coding strategy MCS for transmitting the downlink RRC message based on the first duration.

Exemplarily, before the sending unit 1220 sends at least one first segment message to the terminal device, the receiving unit 1210 is further configured to receive first capability information from the terminal device, where the first capability information is used to indicate the The terminal equipment supports downlink RRC message segmentation.

Exemplarily, the receiving unit 1210 is further configured to receive second capability information from the terminal device, where the second capability information is used to indicate that the terminal device supports uplink RRC message segmentation.

Exemplarily, the sending unit 1220 is further configured to send first indication information to the terminal device, where the first indication information is used to indicate that the network device supports downlink RRC message segmentation.

The apparatus 1200 corresponds to the network device in the method embodiment, and the device 1200 may be the network device in the method embodiment, or a chip or functional module inside the network device in the method embodiment. The corresponding unit of the apparatus 1200 is used to execute the corresponding steps executed by the network device in the method embodiments shown in FIGS. 6-9.

The sending unit 1220 in the apparatus 1200 executes the steps sent by the network device in the method embodiment, for example, executes step S610 of sending the first segment message to the terminal device in FIG. 6, and executes the step S610 of sending the first instruction information to the terminal device in FIG. Step S613, perform the steps of sending message No. 1 to the terminal device in FIG. 7, perform the steps of sending

message

2A and 2C to the terminal device in FIG. 7, perform the step of sending message No. 1 to the terminal device in FIG. 8, and perform the step of sending message No. 1 to the terminal device in FIG. 8. The terminal device sends 2A, 2C, 2B steps, executes the steps of sending message No. 1 to the terminal device in FIG. 9, and executes the steps of sending

message

2A, 2C, 2B, and 3 to the terminal device in FIG. 9.

The receiving unit 1210 in the apparatus 1200 is configured to perform the steps of receiving by the network device. For example, perform step S620 of receiving a request message sent by a terminal device in FIG. 6, perform step S611 of receiving first capability information sent by a terminal device in FIG. 6, and perform step S612 of receiving second capability information sent by a terminal device in FIG. .

The apparatus 1200 may further include a processing unit 1230, configured to perform corresponding processing-related steps within the network device.

The receiving unit 1210 and the sending unit 1220 may constitute a transceiver unit, and have the functions of receiving and sending at the same time. The processing unit 1230 may be at least one processor. The sending unit 1220 may be a transmitter or an interface circuit. The receiving unit 1210 may be a receiver or an interface circuit. The receiver and transmitter can be integrated to form a transceiver or interface circuit.

Optionally, the device 1200 may further include a storage unit for storing data and/or signaling. The processing unit 1230, the sending unit 1220, and the receiving unit 1210 may interact or couple with the storage unit, for example, read or call the storage unit. Data and/or signaling to enable the method of the above-mentioned embodiment to be executed.

Referring to FIG. 13, FIG. 13 is a schematic structural diagram of a network device 1300 applicable to an embodiment of the present application, which can be used to implement the function of the network device in the above-mentioned paging method. Can be a schematic diagram of the structure of a network device.

In a possible manner, for example, in some implementations in a 5G communication system, the network device 1300 may include CU, DU, and AAU. Compared with the network device in the LTE communication system, the network device consists of one or more radio frequency units, such as For the remote radio unit (RRU) and one or more baseband units (BBU):

The non-real-time part of the original BBU will be divided and redefined as CU, which is responsible for processing non-real-time protocols and services. Part of the physical layer processing functions of the BBU are merged with the original RRU and passive antennas into AAU, and the remaining functions of the BBU are redefined as DU. Responsible for handling physical layer protocols and real-time services. In short, CU and DU are distinguished by the real-time nature of processing content, and AAU is a combination of RRU and antenna.

CU, DU, and AAU can be separated or co-located. Therefore, there will be multiple network deployment forms. One possible deployment form is consistent with traditional 4G network equipment. CU and DU share hardware deployment. It should be understood that FIG. 13 is only an example, and does not limit the scope of protection of this application. For example, the deployment form may also be DU deployment in a 5G BBU computer room, CU centralized deployment or DU centralized deployment, and CU higher-level centralized deployment.

The AAU 801 that can implement the transceiving function is called the transceiving unit 1301, which corresponds to the transmitting unit 1220 in FIG. 12. Optionally, the transceiver unit 1301 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 13011 and a radio frequency unit 13012. Optionally, the transceiver unit 1301 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter or transmitting circuit). The CU and DU 1302 that can implement internal processing functions are referred to as a processing unit 1302. Optionally, the processing unit 1302 may control network devices, etc., and may be referred to as a controller. The AAU 1301, the CU and the DU 1302 may be physically set together, or may be physically separated.

In addition, the network device is not limited to the form shown in FIG. 13, and may also be in other forms: for example, including BBU and ARU, or including BBU and AAU; it may also be CPE or other forms, which is not limited by this application.

It should be understood that the network device 1300 shown in FIG. 13 can implement the functions of the network device involved in the method embodiments in FIGS. 6-9. The operations and/or functions of each unit in the network device 1300 are respectively for implementing the corresponding processes executed by the network device in the method embodiment of the present application. In order to avoid repetition, detailed descriptions are appropriately omitted here. The structure of the network device illustrated in FIG. 13 is only a possible form, and should not constitute any limitation in the embodiment of the present application. This application does not exclude the possibility of other types of network equipment structures that may appear in the future.

The embodiment of the present application also provides a communication system, which includes the aforementioned terminal device and network device.

The present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium. When the instructions run on a computer, the computer executes the above-mentioned method shown in FIG. 6 to FIG. 9. The terminal device The various steps performed.

This application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium. When the instructions run on a computer, the computer executes the network device in the method shown in FIGS. 6-9. The various steps performed.

This application also provides a computer program product containing instructions. When the computer program product runs on a computer, the computer executes the steps performed by the terminal device in the method shown in FIGS. 6-9.

This application also provides a computer program product containing instructions. When the computer program product runs on a computer, the computer executes the steps performed by the network device in the method shown in FIGS. 6-9.

The application also provides a chip including a processor. The processor is used to read and run the computer program stored in the memory to execute the corresponding operation and/or process executed by the terminal device in the method for message transmission provided in this application. Optionally, the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used to read and execute the computer program in the memory. Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive processed data and/or information, and the processor obtains the data and/or information from the communication interface, and processes the data and/or information. The communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip. The processor may also be embodied as a processing circuit or a logic circuit.

The application also provides a chip including a processor. The processor is used to read and run the computer program stored in the memory to execute the corresponding operation and/or process performed by the network device in the method for message transmission provided in this application. Optionally, the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used to read and execute the computer program in the memory. Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive processed data and/or information, and the processor obtains the data and/or information from the communication interface, and processes the data and/or information. The communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip. The processor may also be embodied as a processing circuit or a logic circuit.

The above-mentioned chip can also be replaced with a chip system, which will not be repeated here.

The terms "including" and "having" and any variations of them in this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to clearly listed Instead, those steps or units listed may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual conditions to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .

In addition, the term "and/or" in this application is only an association relationship that describes associated objects, which means that there can be three types of relationships, for example, A and/or B, which can mean that A alone exists, and both A and B exist. , There are three cases of B alone. In addition, the character "/" in this document generally means that the associated objects before and after are in an "or" relationship; the term "at least one" in this application can mean "one" and "two or more", for example, A At least one of, B and C can mean: A alone exists, B alone exists, C alone exists, A and B exist alone, A and C exist at the same time, C and B exist at the same time, A and B and C exist at the same time, this Seven situations.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for message transmission, characterized in that it comprises:

The terminal device receives at least one first segment message from the network device;

Sending, by the terminal device, a request message to the network device, where the request message is used to request the network device to send at least one second segment message,

The first downlink unlimited resource control RRC message includes the at least one first segment message and the at least one second segment message.
The method according to claim 1, wherein the sending of a request message by the terminal device to the network device comprises:

The RRC entity of the terminal device sends a first notification message to the radio link control RLC entity of the terminal device, where the first notification message is used to notify the RLC entity to send the request message to the network device;

and / or,

The RRC entity of the terminal device sends a second notification message to the media access control MAC entity of the terminal device, where the second notification message is used to notify the MAC entity to send the request message to the network device.
The method according to claim 1 or 2, wherein when the terminal device receives the first first segment message from the network device, the method further comprises:

The terminal device starts a timer;

When the terminal device receives all the second segment messages during the running period of the timer, the terminal device stops the timer;

When the timer expires and the terminal device does not receive all the second segment messages, the terminal device determines that the reception of the first downlink RRC message fails.
The method according to claim 3, wherein before the terminal device determines that the reception of the first downlink RRC message fails, the method further comprises:

The RRC entity of the terminal device sends a first message to the packet data convergence layer protocol PDCP entity of the terminal device, where the first message is used to instruct the PDCP entity to report a second message, where the second message is The signaling of the PDCP entity bears the buffered message in the buffer;

When the second message includes part of the second segment message in the at least one second segment message, the method further includes:

The terminal device discards the at least one first segment message and the part of the second segment message.
The method of claim 3, wherein the method further comprises:

The terminal device sends a first duration to the network device, where the start moment of the first duration is the timer start moment, and the end moment of the first duration is the terminal device receiving the The time of the last second segment message in at least one second segment message.
The method according to any one of claims 1 to 5, wherein the terminal device receiving at least one first segment message from a network device comprises:

Receiving, by the terminal device, a plurality of first segment messages from the network device, the plurality of first segment messages including at least one third segment message and at least one fourth segment message;

The method also includes:

The packet data convergence layer protocol PDCP entity of the terminal device reports the at least one third segment message to the RRC entity of the terminal device and saves the at least one fourth segment message in the PDCP entity of the terminal device middle,

Wherein, the index of the third segment message is smaller than the index of the fourth segment message, and the index of the fourth segment message is greater than the index of the second segment message.
The method according to any one of claims 1-6, wherein the request message comprises a medium access control MAC message and/or a radio link control RLC message.
7. The method according to any one of claims 1-7, wherein before the terminal device receives at least one first segment message from a network device, the method further comprises:

The terminal device sends first capability information to the network device, where the first capability information is used to indicate that the terminal device supports downlink RRC message segmentation.
The method according to claim 8, wherein the first capability information is further used to indicate that the terminal device supports uplink RRC message segmentation;

or,

The method also includes:

The terminal device sends second capability information to the network device, where the second capability information is used to indicate that the terminal device supports uplink RRC message segmentation.
9. The method according to any one of claims 1-9, wherein the method further comprises:

The terminal device receives first indication information from the network device, where the first indication information is used to indicate that the network device supports downlink RRC message segmentation.
A method for message transmission, characterized in that it comprises:

The network device sends at least one first segment message to the terminal device;

Receiving, by the network device, a request message from the terminal device, the request message being used to request the network device to send at least one second segment message,

The first downlink unlimited resource control RRC message includes the at least one first segment message and the at least one second segment message.
The method of claim 11, wherein the method further comprises:

The network device receives the first time length from the terminal device, where the start time of the first time length is the time when the terminal device receives the first first segment message, and the first time length is The termination time is the time when the terminal device receives the last second segment message in the at least one second segment message.
The method according to claim 11 or 12, wherein the request message comprises a medium access control MAC message and/or a radio link control RLC message.
The method according to any one of claims 10-13, wherein before the network device sends at least one first segment message to the terminal device, the method further comprises:

The network device receives first capability information from the terminal device, where the first capability information is used to indicate that the terminal device supports downlink RRC message segmentation.
The method according to claim 14, wherein the first capability information is further used to indicate that the terminal device supports uplink RRC message segmentation;

or,

The method also includes:

The network device receives second capability information from the terminal device, where the second capability information is used to indicate that the terminal device supports uplink RRC message segmentation.
The method according to any one of claims 11-15, wherein the method further comprises:

The network device sends first indication information to the terminal device, where the first indication information is used to indicate that the network device supports downlink RRC message segmentation.
A device for message transmission, characterized in that it comprises:

A receiving unit, configured to receive at least one first segment message from a network device;

The first sending unit is configured to send a request message to the network device, where the request message is used to request the network device to send at least one second segment message,

The first downlink unlimited resource control RRC message includes the at least one first segment message and the at least one second segment message.
The apparatus according to claim 17, wherein the first sending unit sending a request message to the network device comprises:

The second sending unit provided in the RRC entity of the device is configured to send a first notification message to the radio link control RLC entity provided in the device, and the first notification message is used to notify the RLC entity provided in the device. The entity sends the request message to the network device;

and / or,

The second sending unit sends a second notification message to the media access control MAC entity provided in the device, and the second notification message is used to notify the MAC entity provided in the MAC entity to send the request message to the network device .
The apparatus according to claim 18, wherein when the receiving unit receives the first first segment message from the network device, the apparatus further comprises:

The processing unit is used to start the timer;

When the receiving unit receives all the second segment messages during the running period of the timer, the processing unit stops the timer;

When the timer expires and the receiving unit does not receive all the second segment messages, the processing unit determines that the reception of the first downlink RRC message fails.
The apparatus according to claim 19, wherein before the processing unit determines that the reception of the first downlink RRC message fails, the apparatus further comprises:

The second sending unit set in the RRC entity of the device is configured to send a first message to the PDCP entity of the device, and the first message is used to instruct the PDCP entity to report the second message, wherein the The second message is a buffer message in the signaling bearer buffer of the PDCP entity;

When the second message includes part of the second segment message in the at least one second segment message, the processing unit is further configured to discard the at least one first segment message and the part of the first segment message. Two-segment message.
The apparatus according to claim 20, wherein the first sending unit is further configured to send a first duration to the network device, wherein the start time of the first duration is the start of the timer Time, the termination time of the first duration is the time when the receiving unit receives the last second segment message in the at least one second segment message.
The apparatus according to any one of claims 17-21, wherein the receiving unit receiving at least one first segment message from a network device comprises:

The receiving unit receives multiple first segment messages from the network device, where the multiple first segment messages include at least one third segment message and at least one fourth segment message;

The device also includes:

A third sending unit set in the PDCP entity of the device, configured to report the at least one third segment message to the RRC entity of the device;

A storage unit set in the PDCP entity of the device, configured to store the at least one fourth segment message in the PDCP entity,

Wherein, the index of the third segment message is smaller than the index of the fourth segment message, and the index of the fourth segment message is greater than the index of the second segment message.
The apparatus according to any one of claims 17-22, wherein the request message comprises a MAC message and/or an RLC message.
The apparatus according to any one of claims 17-23, wherein before the receiving unit receives at least one first segment message from a network device, the first sending unit is further configured to send The network device sends first capability information, where the first capability information is used to indicate that the apparatus supports downlink RRC message segmentation.
The device according to claim 24, wherein the first capability information is further used to indicate that the device supports uplink RRC message segmentation;

or,

The first sending unit is further configured to send second capability information to the network device, where the second capability information is used to indicate that the device supports uplink RRC message segmentation.
The apparatus according to any one of claims 17-25, wherein the receiving unit is further configured to receive first indication information from the network device, and the first indication information is used to indicate the The network equipment supports downlink RRC message segmentation.
A device for message transmission, characterized in that it comprises:

A sending unit, configured to send at least one first segment message to a terminal device;

A receiving unit, configured to receive a request message from the terminal device, where the request message is used to request the network device to send at least one second segment message,

The first downlink unlimited resource control RRC message includes the at least one first segment message and the at least one second segment message.
The apparatus according to claim 27, wherein the receiving unit is further configured to receive a first duration from the terminal device, wherein the start time of the first duration is the time received by the terminal device The moment of the first first segment message, and the end time of the first duration is the moment when the terminal device receives the last second segment message in the at least one second segment message.
The apparatus according to claim 27 or 28, wherein the request message comprises a medium access control (MAC) message and/or a radio link control (RLC) message.
The apparatus according to any one of claims 27-29, wherein before the sending unit sends at least one first segment message to the terminal device, the receiving unit is further configured to receive The first capability information of the device, where the first capability information is used to indicate that the terminal device supports downlink RRC message segmentation.
The apparatus according to claim 30, wherein the first capability information is further used to indicate that the terminal device supports uplink RRC message segmentation;

or,

The receiving unit is further configured to receive second capability information from the terminal device, where the second capability information is used to indicate that the terminal device supports uplink RRC message segmentation.
The apparatus according to any one of claims 27-31, wherein the sending unit is further configured to send first indication information to the terminal device, and the first indication information is used to indicate the network The device supports downlink RRC message segmentation.
A communication device, characterized in that it comprises:

A memory, the memory is used to store a computer program;

Transceiver, the transceiver is used to perform the transceiving step;

A processor, configured to call and run the computer program from the memory, so that the communication device executes the method according to any one of claims 1-16.
A computer-readable storage medium, comprising: the computer-readable medium stores a computer program; when the computer program is run on a computer, the computer executes any one of claims 1-16 method.
A communication system, characterized in that it comprises:

The device for message transmission according to any one of claims 17-26 and the device for message transmission according to any one of claims 27-32.